cvoip solutions disaster recovery procedures-cvm12-nn10450-900_06.02

Carrier VoIP

Nortel Carrier Voice over IPSolutions Disaster RecoveryProceduresRelease: (I)CVM12Document Revision: 06.02

www.nortel.com

NN10450-900.

Carrier VoIPRelease: (I)CVM12Publication: NN10450-900Document release date: 3 October 2008

Copyright © 2008 Nortel NetworksAll Rights Reserved.

Printed in Canada, the United States of America, and the United KingdomLEGAL NOTICE

While the information in this document is believed to be accurate and reliable, except as otherwise expresslyagreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OFANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document aresubject to change without notice.

Nortel, the Nortel logo, Business Made Simple and the Globemark are trademarks of Nortel.

All other trademarks are the property of their respective owners.

.

3.

ContentsNew in this release 9Features 9Other changes 9

Introduction 11

Disaster recovery fundamentals 13

Disaster recovery configuration 55

Preparation for disaster recovery 57Recovering the SPFS system if updisk daemon dies 58Installing the DDMS 59Installing optional software on a Core and Billing Manager 64Installing the OM Data Delivery application 68Installing the Passport Log Streamer application 71Installing the SBA and AFT software packages 73Installing the GR740PT application server 74Configuring RTB for a billing stream 76SBRM core access 81Configuring core access for SBRM through the Nortel Communication Server

2000 Core Manager 84Creating the backup user ID on the core for SBRM 86Applying software packages on a Core and Billing Manager using the CBMMTC

interface 88Cloning the image of the active node to the inactive node 91Installing the Backup Restore Manager software 94Configuring SSH between the backup restore manager servers 96Configuring SBA backup volumes on the core 102Starting or stopping the automated synchronous backup restore manager

service 107Invoking the network-level backup (SBRM-bkmgr) through telnet 110Invoking the device-level backup (DBRM-bkmgr) through telnet 115Backing up an XA-Core office image from disk to tape 119Backing up Call Agent 126Backing up the SST 129

Carrier VoIPNortel Carrier Voice over IP Solutions Disaster Recovery Procedures

NN10450-900 06.023 October 2008

Copyright © 2008 Nortel Networks

.

4

Rescheduling backup time 132Backing up security related files manually 134Saving the Ethernet Routing Switch 8600 boot configuration file 136Configuring the automated synchronous backup restore manager service 138Configuring Automated INI file backup on a Media Server 2000 node 142Changing SNMP community string passwords 145Backing up INI files for all nodes 147Displaying Media Server 2010 current node configuration 148Backing up the APS-specific Oracle database and application files 150Using the command line interface to perform backups 153Performing a backup of Oracle/MySQL data on an SPFS-based server 156Backing up UAS configuration files 160Performing a manual backup of the Policy Controller database 162Performing a backup of file systems on an SPFS-based server 164Taking a full IEMS backup 169Backing up an SPFS-based security client 171Backing up a Multiservice Switch or Media Gateway device 172Performing a backup operation 178Creating system image backup tapes (S-tapes) manually 181Displaying actions a user is authorized to perform 193Logging in to the Nortel CS 2000 Core Manager 195Preparation for SBA installation and configuration 197Configuring SBA backup volumes on a billing stream 220Accessing the MATE 222Administration: Creating Disaster Recovery Floppy Disks 224Power-On and boot a Policy Controller unit 225Viewing the operational status of the NCGL platform 226Viewing the operational status of the SIP Gateway application 228Verifying synchronization status 232Booting the XA-Core from a Reset Terminal 233Resetting the Ethernet Routing Switch 8600 using a saved configuration file 236Restoring a Call Agent 237Restoring Session Server Trunks 240Restoring a database to a Session Server unit 241Restoring audio files to a UAS node 242Restoring audio files to a Media Server 2000 Series node 243Restoring the APS-specific Oracle database and application files 244Restoring a Multiservice Switch or Media Gateway device 247Performing a full system restore 253Restoring a system configuration from a data snapshot 254Restoring Core Element Manager data 260Restoring the central security server 262Performing a full restore of the software from S-tape 265Performing a partial restore of the software from S-tape 270


NN10450-900 06.023 October 2008


.

5

Recovering backup files from lost backup volumes 275Restoring the Oracle/MySQL data on an SPFS-based server 277Clearing the MATE alarm 281Stopping the SAM21 Manager server application 282Stopping the SESM server application 284Stopping the NPM server application 286Stopping the APS server application 288Starting the APS server application 290Starting the SESM server application 293Starting the SAM21 Manager server application 295Starting the NPM server application 297Performing a full system restore on an SPFS-based server 299High-availability configuration (two servers) 302Locking a GWC card 305Locking the Call Agent 308Installing the remote backup server 310Scheduling automatic backups on the remote server 315Viewing configuration information for remote server backups 318Performing a manual backup of the target server 320Viewing logs from a remote backup 322Initiating a recovery back to the cluster 323Initiating a switch over to the remote backup server 325Disabling Ethernet Routing Switch 8600 WAN Edge routing 327Disabling and re-enabling the router ports on the Ethernet Routing Switch

8600 329

Network power down 331Powering down an MG 9000 device 335Powering down the IPmedia 2000 shelves 337Powering down the SAM16 shelves 338Powering down a Border Control Point 339Powering down the MCS servers 340Powering down the MDM workstation 341Powering down an SPM device 342Powering down a Media Gateway/Multiservice Switch 7400 345Powering down a Media Gateway/Multiservice Switch 15000 346Powering down a USP 347Powering down the SAMF frame 348Powering down the Call Control Frame 350SAM21 Shelf Controller security and administration fundamentals 352Powering down the Border Control Point Manager 355Powering down a Netra 240 server 356Powering down the SDM 357Powering down a Ethernet Routing Switch 8600 358


NN10450-900 06.023 October 2008


.

6

Shutting down the IEMS server 359Powering down the XA-Core 360Performing a partial power down of the MG 9000 363Performing a partial power down of the Media Gateway/Multiservice Switch

15000 364Performing a partial power down of the USP 368Performing a partial power down of the Ethernet Routing Switch 8600 369Performing a partial power down of the Netra 240 server 370Performing a partial power down of the XA-Core 371

Network power up 375Powering up the XA-Core 380Powering up the Message Switch 396Powering up the Enhanced Network 399Powering up an Ethernet Routing Switch 8600 401Powering up the Link Peripheral Processors 402Powering up the SDM 405Powering up a Netra 240 server 406Powering up the Border Control Point Manager 407Powering up the SAMF frame 408Powering up the Call Control Frame 410Powering up a USP 412Powering up a Media Gateway/Multiservice Switch 15000 414Powering up a Media Gateway/Multiservice Switch 7400 415Powering up the MDM workstation 417Powering up an SPM device 418Powering up the MCS servers 420Powering up a Border Control Point 424Powering up the IPmedia 2000 shelves 425Powering up the SAM16 shelves 426Powering up an MG 9000 device 427Restoring certificates and Pre-shared Keys for IPSec 432Restoring the MG 9000 manager system 436Restoring files from a DVD-RW 437Reloading or restarting a SAM21 Shelf Controller 440Restarting or rebooting a GWC card 441Performing a partial power up of the Netra 240 server 443

Disaster recovery maintenance 445Performing a partial power down recovery of the USP 447Performing a partial power down recovery of the XA-Core 448Performing a partial power down recovery of the Ethernet Routing Switch

8600 451Performing a partial power down recovery of the Media Gateway/Multiservice

Switch 15000 452


NN10450-900 06.023 October 2008


.

7

Performing a partial power down recovery of the SPM 453

Disaster recovery power up 455Unlocking the Call Agent 456Unlocking a GWC card 457

Reference 461


NN10450-900 06.023 October 2008


.

8


NN10450-900 06.023 October 2008


.

9.

New in this releaseThe following sections detail what is new in Nortel Carrier Voice over IPSolutions Disaster Recovery Procedures ((NN10450-900)) for softwareRelease (I)CVM12.

• “Features” (page 9)

• “Other changes” (page 9)

FeaturesThere were no feature changes made to this document.

Other changesThere are no other changes in this document.


NN10450-900 06.023 October 2008


.

10 New in this release


NN10450-900 06.023 October 2008


.

11.

IntroductionThis document provides an overview of the Disaster Recovery process forCarrier VoIP solutions. A disaster is defined as one of the following events:

• fire

• flood

• lightning storm

• explosion

• tornado

• earthquake

• hurricane

• terrorism

• any other incident causing damage beyond normal repair totelecommunications facilities

Use this document to restore communication capability within the affectedcentral office or network.

Navigation• “Disaster recovery fundamentals” (page 13)

• “Disaster recovery configuration” (page 55)

• “Preparation for disaster recovery” (page 57)

• “Network power down” (page 331)

• “Network power up” (page 375)

• “Disaster recovery maintenance” (page 445)

• “Disaster recovery power up” (page 455)

• “Reference” (page 461)


NN10450-900 06.023 October 2008


.

12 Introduction


NN10450-900 06.023 October 2008


.

13.

Disaster recovery fundamentalsThis chapter describes disaster recovery basics specific to the NortelCarrier VoIP solutions.

Navigation• “Power conservation” (page 14)

• “Backup and restore” (page 15)

• “Synchronized Backup Manager fundamentals” (page 15)

• “Sequence of events to run the Synchronized Backup Manager” (page17)

• “Hardware and software requirements” (page 18)

• “Requirements and restrictions” (page 19)

• “CNM network element backup” (page 21)

• “Administration: OAMP workstation backup” (page 22)

• “Restoring Multiservice Switch or Media Gateway service data” (page23)

• “Operational Measurement Delivery ” (page 24)

• “Geographical survivability” (page 30)

• “Site failure in a geographic survivable configuration” (page 32)

• “Fresh pre-install of CBM 850 cold u0” (page 32)

• “Maintaining sites in a geographic survivable configuration” (page 33)

• “Geographical survivability impacts to CS 2000-Compact” (page 33)

• “Protocols BGP and OSPF activation” (page 41)

• “USP mated pairs” (page 42)

• “SSL geographic survivability” (page 47)

• “Geographic survivability limitations and restrictions” (page 49)

• “Real Time Billing fundamentals” (page 50)


NN10450-900 06.023 October 2008


.

14 Disaster recovery fundamentals

Power conservationYou can partially power down several components to conserve power butkeep the network in an operational state. Power conservation procedurestypically involve powering down inactive or spare units, or keeping onlya certain set of hardware or cards active. The following table lists thecomponents and types of power procedures.

Table 1Power procedures

Component or network element Full Partial

XA-Core X X

Ethernet Routing Switch 8600 X X

SDM (CS 2000 Core Manager) X

Netra™ 240 X X

Border Control Point X

Services Application Module Frame X

Call Control Frame X

USP X X

Media Gateway/Multiservice Switch 15000 X X

Media Gateway/Multiservice Switch 7480 X

MDM X

SPM X X

MCS X

Border Control Point Manager X

Media Server 2000 Series X

UAS X

MG 9000 X X

When you perform a partial power down for a component, you must followthe corresponding partial power down recovery procedure. Do not use apartial power down recovery procedure to recover from a full power downsituation. Conversely, do not use a full power down recovery procedure torecover from a partial power down situation.

ATTENTIONPerform a recovery from a partial power down of the MG 9000 by using thesame procedure as recovery from a full power down.


NN10450-900 06.023 October 2008


.

Synchronized Backup Manager fundamentals 15

Backup and restorePerform backup and restore operations for CVoIP solutions at thecomponent level. Perform the operations on the components at differentintervals during periods of low service activity. Do not make provisioning orconfiguration changes during the backup and restore window.

Back up all related devices in the solution during the same window oftime. You cannot make changes to any related devices during this perioduntil all backups are complete or those changes are not captured as partof the coordinated backup and are lost in case of the need to restore thesystem. For example, the CS 2000, CS 2000 GWC Manager, and MG9000 Manager all share line service data and you must back them up inthe same window.

You must restore all related devices together to return the system to aknown state. You cannot make changes to the system until the restorationis complete or the changes result in data mismatches.

Synchronized Backup Manager fundamentalsThroughout this document, the backup and restore functionality deliveredunder this feature is referred to in the following three distinct ways:

• Synchronous Backup Restore Manager (SBRM) is a network backuputility that is installed in the /opt/bkresmgr/nbm directory. The SBRMcontrols and synchronizes the activities related to backup across otherdevices that contain related backup software. The SBRM is invokedfrom the IEMS Backup Manager.

• Device Backup Restore Manger (DBRM) refers specifically to thedevice-level backup software that is installed in the /opt/bkresmgr/cbmdirectory. The DBRM is controlled by the SBRM and it is notrecommended running the DBRM directly from a CLUI interface. Thereare few exceptions and they are specified explicitly in this document ifit requires to be run at DBRM level.

WARNING:Status commands executed at the DBRM cli may be idleeven if a NBM (network backup) is in progress. To ensure that nobackup is in progress when required to backup at DBRM level, pleasecheck the status of both NBM and DBRM.

• Backup Restore Manager is a generic term encompassing both SBRMand DBRM functionality that refers to the software that is common toboth.

The SBRM provides a centralized mechanism that you use to initiate asynchronous backup for the core components of the CVoIP Call Server.This capability reduces the possibility of error caused by manual backupprocedures on the various component platforms spread across the CallServer solution.


NN10450-900 06.023 October 2008


.


From Release (I)SN08, the Backup Manager provides synchronouscentralized control of the backup functionality resident within the followingCall Server components:

• CS 2000 Management Tools (CSMT) server

• MG 9000 Manager (MG9K) server

• Supernode Data Manager (SDM)/Core Billing Manager (CBM) server.The software on the SDM/CBM only allows control of the XACore/3PCbackup. Backup Restore Manager does not back up SDM/CBM data.

• Integrated Element Management System (IEMS) server

ATTENTIONThe IEMS can reside with the CSMT (and other applications) on the CSMTserver.

From the IEMS GUI, the user launches the network backup utility (SBRM)command line interface and initiates a backup for CVoIP Call Servercomponents. The network backup utility (SBRM) receives the userrequest, and initiates a backup command sequence (using CLI commandsover SSH) to execute a synchronous device-level backup of the CVoIPCall Server components. Once the backup is complete, the backup filesare stored locally on each component.

The following figure shows a high-level functional overview of the SBRM.

Figure 1High-level functional overview of the SBRM


NN10450-900 06.023 October 2008


.

Sequence of events to run the Synchronized Backup Manager 17

Sequence of events to run the Synchronized Backup ManagerThe component for which the SBRM is installed, SDM or the Core andBilling Manager, determines the sequence of events.

Installation and configuration of SBRM on the SDMInstallation and configuration of SBRM on the SDM requires execution ofthe following procedures in the order given:

• "Installing and configuring the Backup Restore Manager application onthe CS 2000 Core Manager" in Nortel Carrier Voice over IP Upgradeand Patches ( (NN10440-450)) .

• “SBRM core access” (page 81)

• “Configuring SSH between the backup restore manager servers” (page96)

• “Configuring core access for SBRM through the Nortel CommunicationServer 2000 Core Manager” (page 84)

• “Creating the backup user ID on the core for SBRM” (page 86)

• “Configuring the automated synchronous backup restore managerservice” (page 138)

• “Common procedures for all components” (page 17)

Installation and configuration of SBRM on the Core and BillingManager

Installation and configuration of SBRM on the Core and Billing Managerrequires execution of the following procedures in the order given:

• "Installing and configuring the Backup Restore Manager application onthe CS 2000 Core Manager" in Nortel Carrier Voice over IP Upgradeand Patches ( (NN10440-450)) .

• “Creating the backup user ID on the core for SBRM” (page 86)

• “Configuring SSH between the backup restore manager servers” (page96)


• “Common procedures for all components” (page 17)

Common procedures for all componentsThe following procedures are required to configure the SBRM on allcomponents and are executed in the order given.


NN10450-900 06.023 October 2008


.


To configure SSH between the backup manager restore servers (if notalready completed), see the procedure, “Configuring SSH between thebackup restore manager servers” (page 96).

The following procedures provide additional information about the SBRM:

• To configure automated execution of backups, see the procedure,“Configuring the automated synchronous backup restore managerservice” (page 138).

• To control the automated execution of backups, see the procedure,“Starting or stopping the automated synchronous backup restoremanager service” (page 107).

To configure the IEMS to support the SBRM, see the following documents:

• To add the SBRM to the IEMS using the Java Web Start Client or theWeb Client, see Nortel IEMS Configuration ( (NN10330-511)) .

• To launch the CLI for the SBRM using the IEMS Java Web Start Client,see Nortel IEMS Fundamentals ( (NN10329-111)) . You cannot launchthe SBRM using the IEMS Web Client.

Invoke a network backup (where several components are backed upat once) from the IEMS Backup Manager. In rare instances, it can benecessary to run various portions of the backup process on individualcomponents or servers. This capability is implemented as a CLUIinterface.

Execution of a backup at the component-level

ATTENTIONRun a backup at the component-level only in rare circumstances. Take care tokeep the SBRM and the DBRM in sync.

Invoke the CLUI interface to perform a backup at the component-level bylogging on to the appropriate component using a Telnet session. See theprocedure, “Invoking the network-level backup (SBRM-bkmgr) throughtelnet” (page 110).

Hardware and software requirementsBackup Restore Manager functionality requires that the appropriatesoftware is resident and configured in all platforms which requiresynchronized imaging. The Backup Restore Manager software is includedin various platform software packages, including the SPFS and SDM.SPFS Backup Restore Manager functionality is used for integration of CallServer Management Tools (CSMT), the Media Gateway 9000 ElementManager (MG9KEM), the IEMS, and the CBM. The software on theSDM/CBM only allows control of the XACore/3PC backup. Backup RestoreManager does not back up SDM/CBM data.


NN10450-900 06.023 October 2008


.

Requirements and restrictions 19

Requirements and restrictionsThe following requirements and restrictions apply to Synchronized BackupManager functionality from (I)SN08:

• All platforms requiring Backup Manager software functionality must beJava compatible and must provide a resident Java runtime system.

• The SBRM software does not support restoration of generatedsynchronized backup images. You must follow existing manual restoreprocedures to utilize the backup images produced by the BackupRestore Manager.

• The Backup Restore Manager system does not perform automaticspooling of backup data or image files to secure or redundant servers.You must manage your secure server archiving capabilities. TheBackup Restore Manager system publishes data or image files inpredetermined and configurable directories on various servers:

— SPSF Platform data/image file location: /data/bkresmgr/backup

— XACore/3PC data/image file location: Configurable

• Backup of program store and associated patches is not part of thefunctionality associated with Synchronous Backup Restore Manager.If you need to completely restore a server or component, you mustreinstall your applications and reapply the associated patches.

• The backup abort command can require manual cleanup or removalof some backup files. You receive notification at abort commandcompletion.

• You cannot run the backup process while certain constructive ordestructive system audits are in progress, for example, SESM CS2000 Data Integrity Audit. In general, if you attempt a backup whilethese audits are in progress, the backup attempt is rejected. However,some constructive or destructive audits are postponed when a backuprequest is received, for example, MG9KEM Network Element Audit.The architecture of the system in question determines the appropriatebehavior. In general, any system rejections of the backup requestresult in an appropriate message displayed to the Synchronous BackupRestore Manager client user.

• No system-wide coordination between Synchronous Backup RestoreManager and other applications, for example, Upgrade Manager,CS 2000 Audits, and CM dump scheduling, is delivered. You mustmanually manage all application activity interdependencies. Forexample, you must stop scheduled activities such as audits duringsystem backup. Also, you must cancel automated CM image dumpsbecause the Synchronous Backup Restore Manager drives the dumpwithin a synchronized system-wide backup window.


NN10450-900 06.023 October 2008


.


• APS and NPM queries are not allowed during backup. This limitationis due to the application shut down during backup. Active clients areinformed of the application shutdown.

• Nortel does not recommend that you backup the MG 9000 EM inisolation due to the CSMT platform data dependency. The MG 9000EM database is hosted on the CSMT server.

• Synchronous Backup Restore Manager user authorization only controlsthe launch of the CLI. CLI command-specific authorization is notprovided, therefore only users authorized to launch the SynchronousBackup Restore Manager CLI can perform query commands at theSynchronous Backup Restore Manager CLI.

• The software on the SDM/CBM only allows control of the XACore/3PCbackup. Backup Restore Manager does not back up SDM/CBM data.

During the backup, use of the various GUI and command line provisioninginterfaces is restricted from attempting the following actions which result inconfiguration and provisioning data changes:

• Add, delete, or update GWCs at the Call Server Management Tools(CSMT) GUI or OSSGate interface.

• Add, delete, or update line service at the CSMT OSSGate interface.

• Manually invoke (or run by using the scheduler) the various audits atthe CSMT GUI.

• Add, delete, or update objects in the IEMS topology by using the IEMSclient.

• Add or modify collection jobs by using the IEMS client.

• Use the Runtime Administration interface at the IEMS client to performOSS configuration.

• Use the Security Administration interface at the Integrated client to addor delete users, groups, or operations.

• Use the Security Administration interface at the IEMS client to changea user password.

• Add, delete, or update trunks or carriers by using the CSMT.

• Node provisioning or deprovisioning by using the SAM21Manager.

• ATM connection set provisioning or deprovisioning by using the SAM21Manager.


NN10450-900 06.023 October 2008


.

CNM network element backup 21

CNM network element backupThe Network Element Backup application provides a user-friendly solutionto backup the network element system and configuration data. Some ofthe key features of this application include:

• A single operational user interface for on-demand or scheduledbackups.

• Automatic discovery of network elements.

• Consolidated view of backup configurations and the status ofsupported network elements.

• Policy-based backup for each type of network element.

• Multiple simultaneous backups.

• A framework to support additional network elements.

• The status of backup jobs can be monitored during any phase of thebackup.

Network elements can include:

• networking devices

• element managers

• network management servers

Some network element backup images are stored at the network element(native storage). Some network element backups are stored on the localnetwork management server (central storage). Some network elementbackup images can be stored on either native storage or central storage.

The Network Element Backup application launches and controls thebackup process but some pre-backup and post-backup tasks must beperformed manually (for example, inserting a tape in a tape drive beforethe backup and removing the tape from the tape drive after the backup). Ifthe backup process requires tasks to be performed manually, an overviewof these tasks is provided in the backup description for the networkelement and task details are provided in this document. Network ElementBackup software is delivered with default backup parameters for eachsupported network element. You must update these backup parametersfor any customizations applied to your network elements. Some backupparameters apply to all instances of that network element type, while otherbackup parameters apply only to selected instances of a network element.

For more information, see CDMA Network Manager Administration --Network Element Backup (NN20000-344) .


NN10450-900 06.023 October 2008


.


Administration: OAMP workstation backupYou can perform two types of backup on your OAMP workstation, manualand automatic. Perform manual backups from the desktop by manuallyinitializing the backup process. Perform automatic backups according tothe settings defined in the tape drive application.

ATTENTIONNortel recommends that you use the automatic backups to ensure that the datathat is stored on the tapes is up-to-date.

The OAMP workstation is equipped with a tape drive, software tosupport tape backup, and five blank data tapes. These tapes provideapproximately one month of backups to be kept on-site.

ATTENTIONNortel recommends that you label the tapes to indicate the OAMP workstationassociated with the backups to ensure that any recovery operations areperformed from the correct tape.

Backup scheduleCreate a schedule for your automatic backups to ensure up-to-datestorage of the system configuration of your OAMP workstation.

ATTENTIONNortel recommends that you perform a full system backup once a week andmodified (differential) backups once a day.

Manual backupNortel recommends that you perform a manual backup of your OAMPworkstation after initial installation.

To perform a manual backup of the system configuration for your OAMPworkstation, see the documentation provided with your Colorado or Veritassoftware.

Automatic backup configurationThere are two types of automatic backup, full system backup and modified(differential) system backup.

The full system backup saves all of the files contained in the hard disk onyour OAMP workstation.

The modified (differential) system backup saves only the files on the harddisk that have been modified since the last full system backup.


NN10450-900 06.023 October 2008


.

Restoring Multiservice Switch or Media Gateway service data 23

ATTENTIONWhen you use automatic backup, you must leave your OAMP workstation turnedon with Windows running and ensure that there is a tape in the tape drive.

The initial installation of your system configures the tape drive applicationto perform an automatic full-system backup once a week, every Saturdayat 1:00 a.m. However, you can modify the settings in the tape driveapplication.

ATTENTIONIf you do not change the default setting for automatic full system backup, you willneed to change the tape every Friday.

ATTENTIONFor automatic backups to work, the tape drive scheduler icon must be activein the notification box in the taskbar with the automated daily backups optionenabled. Your OAMP workstation must remain on with Windows active and atape must be in the tape drive.

Verify the current modified system backup settingsThere is a tape drive configuration file associated with the modified systembackup. To verify that the current settings in the configuration file matchesthe system requirements, see the tape drive documentation provided withthe OAMP workstation.

View the current automatic backup scheduleTo view the current settings for automatic backup in the tape driveapplication, see the tape drive documentation provided with the OAMPworkstation.

Restoring Multiservice Switch or Media Gateway service dataThis section describes using Service Data Backup and Restore to restorebacked up service data from the backup site to the Multiservice Switch7400/15000 or Media Gateway 7400/15000.

The Service Data Backup and Restore tools provide the following threetypes of restore:

• A full restore restores all backed up service data to the selecteddevices.

• An incremental restore restores service data based on a specifieddate. Like the full restore, you can perform an incremental restore oneither one or multiple devices.

• A selective restore restores specific service data that you select. Likethe full restore, you can perform a selective restore on either one ormultiple devices.


NN10450-900 06.023 October 2008


.


ATTENTIONNortel does not recommend that an active file (current view) be restored on aMultiservice Switch 7400/15000 or Media Gateway 7400/15000. When yourestore the current view, you may overwrite the existing current view withdifferent content. This action will cause an outage of the Backup and Restoretool.

Operational Measurement DeliveryThe Operational Measurement Delivery (OMD) application collectscustomer-defined operational measurement (OM) data from the DMSswitch, and stores the data in OM report files on the core manager incomma-separated value (CSV) format. Configure the OMD applicationusing the OM user interface (OMUI).

An OM report file is a collection of OM groups that are monitored atselected reporting intervals. Secure File Transfer (SFT) or File TransferProtocol (FTP) sends OM report files from the core manager to anoperations support system (OSS). A data browser such as a spreadsheetprogram provides access to the contents of the files.

Report elementsReport elements define the content of OM report files, and combinecontent of related OM groups for monitoring and analysis. A reportelement contains a user-defined report element name, a reporting intervalfor a report element (five minutes, or the office transfer period of 15 or 30minutes), and names of the OM groups and registers.

Subtraction profilesThe subtraction profile determines the change in the value of an OM groupregister between five-minute OM reports, as defined in a report element.The subtraction profile applies only after the reporting interval is set to fiveminutes. The following table lists the types of subtraction profiles.

Table 2Subtraction profiles

Type Description

Single A single register represents a running total

Double Two registers (base and extension) represent a running total

Non-subtraction

Subtraction is not performed on selected registers


NN10450-900 06.023 October 2008


.

Operational Measurement Delivery 25

Data collection schedulesA data collection schedule defines start and stop times for OM reportcollection. The collecting interval determines how often in the time periodan OM report collection occurs. The data is collected to the same reportfile for schedules with collecting intervals after midnight. The followingtable lists the data collection schedule types.

Table 3Data collection schedule repetition types

Repetition Schedule information

Daily Daily start and stop time. Format: hhmm, where hh = hour (00 to 24), andmm = minute (00 or 30). Specifies only a single time period; for multiple timeperiods in the same day, you must define multiple schedules.

Weekly Weekly start and stop time. Values: Sunday, Monday, Tuesday, Wednesday,Thursday, Friday, and Saturday. Format: hhmm; multiple days can bespecified in same schedule.

Monthly Monthly start and stop time. Values:1 to 31. Format: hhmm; multiple days canbe specified in the same schedule.

File rotation schedulesFile rotation schedules specify when to rotate report files. File rotationcloses an open report file and moves it to the /omdata/closedNotSentdirectory on the core manager. Each file rotation schedule contains

• a user-defined file rotation schedule name

• a repetition rate for the rotation schedule based on either the numberof report records collected or the number of hours to collect records

• a schedule that defines the time to rotate the report file

The data collection and file rotation schedules operate independently ofeach other. If a file rotation schedule event occurs during a scheduleddata collection period, the file rotation schedule closes and rotates the OMreport file, and a new OM report file with the same name is opened. Thenew file starts collecting immediately and continues until the end of thecollection period. The open OM report file remains in the /omdata/opendirectory until the file rotation schedule closes it and rotates it to the/omdata/closedNotSent directory.

File transfer destinationsFile transfer destinations define remote downstream destinations of OMreport files. Each destination entry contains

• a user-defined file transfer destination name

• the valid IP address of a remote destination host (xxx.xxx.xxx.xxx)


NN10450-900 06.023 October 2008


.


• the FTP port address of the remote host (default: 21)

• the remote host logon ID and password

The core manager does not authenticate the IP and port addresses or thelogon ID and password.

An invalid destination causes the file transfer to fail. After a file fails totransfer, log entries are written to the customer log file at /var/adm/custlog.The file is not re-sent, and the report file must be transferred manuallyusing either the OMFTP command, SFT or standard FTP.

File transfer schedulesFile transfer schedules specify when to transfer OM report filesdownstream. Each file transfer schedule contains a

• user-defined file transfer schedule name

• repetition rate for the transfer schedule

• schedule defining when to transfer the report file (if using a repetitionrate)

• remote file transfer destination host system (<16 destinations/schedule)

• destination storage directory for each defined transfer destination

The files are transferred downstream using FTP, and move from the/omdata/closedNotSent directory to the /omdata/closedSent directory.If a scheduled file transfer fails, a log is raised and the report file thatcould not be transferred moves to the /omdata/closedSent directory. TheOMDD keeps track of the destination to which the report file could not betransferred. Then, at the next scheduled file transfer, the OMDD attemptsto send the report file to the destination again. The OMDD will repeat thisactivity until one of the following situations occurs:

• the file is transferred successfully

• the file exceeds the retention period for the closedNotSent directory

• the file gets deleted during an audit because the omdata filesystemusage has exceeded the allowable limit

• the file is deleted by the omdelete utility

Report registrationsA report registration links information from the report element andschedules for data collection, file rotation and file transfer to collect OMdata. The user can create up to 32 report registrations. After a reportregistration has been created, it can be deleted but not modified. Each


NN10450-900 06.023 October 2008


.


report registration contains user-defined names for the report registration,report elements and each schedule type. The schedules become activeimmediately after the creation of the report registration.

An OM report file opened by the data collection schedule in the/omdata/open directory uses the name of the report registration as partof the OM report file name. Linking a file transfer schedule into a reportregistration provides regular and automatic transfers of OM report files toremote downstream destinations. Unless you link a file transfer scheduleto a report registration, you must manually transfer your OM report filesdownstream.

Report registration limitThe report registration limit is the maximum number of report registrationsthat can be configured on a core manager without affecting processingperformance. The number of report registrations range from 1 to 32(default value: 32). To set the limit, use the Set Report Registration Limitoption from the OMUI main menu.

File retention periodsA cleanup of OM report files that have been sent downstreamautomatically occurs every night at midnight (00:00 or 24:00). Files in the/omdata/closedSent directory are deleted at an interval based on the fileretention period defined in the OMUI (range: 1 to 14 days). The defaultinterval is set to 7 days at OMD installation. Unsent OM report files olderthan 32 days in the /omdata/closedNotSent directory are deleted. This32-day default value is read from a configuration file set up after the coremanager is commissioned.

OMD data collection capacityCollection of more than 10,000 tuples reduces core manager performanceand the retention period for OM report files. To determine the numberof tuples in an OM group, either monitor the OM group and count thetuples in the report file or use the OMSHOW command from the MAP(maintenance and administration position) on the DMS switch. Usethe formulas in the following table to calculate the limit for OMD datacollection.


NN10450-900 06.023 October 2008


.


Table 4Formulas for calculating the limit for OMD data collection

OMD data capacity transfer type Formula

5- and 15-minute x+ y/3 = n <= 10,000 tuples(without loss of data)

5- and 30-minute x+ z/6 = n <= 10,000 tuples(without loss of data)

where

x = the number of OM tuples collected every 5 minutesy = the number of OM tuples collected every 15 minutesz = the number of OM tuples collected every 30 minutesn < 10,000 tuples

The following table lists the current OMD data collection capacity.

Table 5OMD maximum data collection capacity

Transfer type Capacity (number of tuples)

5-minute 6000

15-minute 12,000

30-minute 24,000

OM report file namingReport files are named according to the report registration name, filecreation date and time, name of the switch generating the OMs, andreporting interval. See the following example file name and explanation.

OM report file contentsTuple information for an OM group can be viewed in CSV format fromthe OM report file on the core manager, and by entering the OMSHOWcommand on the MAP. The following table shows an OM report file.


NN10450-900 06.023 October 2008


.


Table 6Contents of an OM report file

DateTime

Switch Names

GroupName Key/Info Field

Reg1 Name

Reg1Value

Reg2 Name

Reg2Value

Reg31Name

Reg31Value

2/23/00 3:35:00

250U TRK ISU_GWC.2W.0.0 AOF 0 ANF 0

2/23/00 3:35:00

250U TRK ESADGTR.OG.0.0 AOF 0 ANF 0

2/23/00 3:35:00

250U TRK HSET.OG.3.0 AOF 0 ANF 0

2/23/00 3:35:00

250U TRK JACK.OG.2.0 AOF 0 ANF 0

2/23/00 3:35:00

250U TRK LTU.OG.2.0 AOF 0 ANF 0

2/23/00 3:35:00

250U TRK MONTALK.OG.0.0 AOF 0 ANF 0

2/23/00 3:35:00

250U TRK OCKT.OG.0.0 AOF 0 ANF 0

AuditsThe OM report files are stored in the omdata filesystem. This filesystemis audited every 30 minutes for the amount of usage. To ensure that theomdata filesystem usage does not reach 100% at any time, the systemperforms the following actions:

• After the filesystem usage reaches 60%, Major trouble log SDM338is raised indicating that OM report files will be deleted at the time ofthe next audit, if usage exceeds 90%. Then, if usage exceeds 90%at the time of the next audit log SDM639 is raised indicating all reportfiles in the closedSent directory will be deleted, and the report files aredeleted.

• If omdata filesystem usage does not fall below 80% after deletionof all report files in the closedSent directory, report files from theclosedNotSent directory will be deleted, starting from the oldest file,until the usage is at 80% or less. As each report file is deleted from theclosedNotSent directory, log SDM631, which describes the action, israised.


NN10450-900 06.023 October 2008


.


Geographical survivabilityGeographic survivability is the distribution of components across ageographic area to ensure services continue in the event of a disaster. Adisaster can include fire, flood, tropical storm, or act of terrorism.

The following figure shows the topology for CS 2000 - Compact supportfor geographic survivability.

Figure 2Geographic survivability topology

The CS 2000 - Compact supports geographic survivability through thefailover and sparing functionality of individual nodes. The configurationfor the CS 2000 Management Tools (CMT) and Integrated ElementManagement System (IEMS) servers and the Core and Billing Manager(CBM) 850 is as follows:

• Site A is configured with the CMT and IEMS high-availability (HA)server pairs

• Site B is configured with the CBM 850 HA server pairs (referred to asCBM 850 HA u0 and u1)

• Site A is configured with an additional CBM in to be used in the eventof disaster at Site B (referred to as CBM 850 standby u0)

• Site B is configured with an additional server for the CMT and IEMSin the event of disaster at Site A


NN10450-900 06.023 October 2008


.

Geographical survivability 31

For a communication server, geographic survivability requires thatredundant components (other than OAM components) reside at differentsites (referred to as Site A and Site B).

For OAM components, the Automatic Backup and Accelerated restorefeature (known as remote backup) remotely backs up all data on the targetunit. This provides a standby backup system ready to provide serviceshould the primary system or cluster be unavailable for an extended periodof time (for example, catastrophic site loss). The remote backup canassume the identity of the target system with data and files accurate tothe last sync and will be located at a different site from the target system.Remote backup performs the backup with a TCP/IP connection, and storesan exact copy on the standby server which can be quickly and remotelyactivated. This remote backup copies all files in each file system markedfor backup using the same behavior as a full system backup.

A remote backup configuration tool is provided to set the necessaryparameters for backup to automatically occur from one to four times aday. This tool also provides a facility for manually initiating a backup andmonitoring its progress. The standby server has an identical copy of filesfrom the last backup, so it can become the primary system by changingthe boot pointer and rebooting. When the primary site becomes available,the remote backup feature can be reused to transfer current systemconfiguration back to the primary site and system.

CAUTIONIf configuration, provisioning, patching or other “write”-typeoperations occurred since the last remote backup, the remotebackup system can be out of sync compared to the data innetwork elements and/or the primary OAM system.

When initiating a switchover to a remote backup OAM server,do not execute configuration, provisioning, patching or other“write”-type operations through the remote backup OAM systemuntil out-of-sync conditions are cleared.

Take actions before initiating the switchover to a remotebackup OAM server (that is, response to a geographic or otherprolonged outage of the primary OAM system) to halt or prevent“write”-type operations by OSSs and operations personnel untilan in-sync status is achieved.

If a site outage is imminent (for example, threatening severeweather conditions), consider precautionary preparations todiscontinue “write”-type operations. Make manual backups tothe remote backup OAM servers to ensure data synchronizationof the remote OAM server before performing a switchover.


NN10450-900 06.023 October 2008


.


Apply similar precautions when initiating a recovery back to theprimary cluster. In this more controlled scenario, discontinue“write”-type operations before initiating this procedure

Site failure in a geographic survivable configurationThere are two scenarios for recovery of a geographic survivable networkconfiguration:

• “Site A failure” (page 32)

• “Site B failure” (page 32)

Site A failureA loss of Site A would include a loss of the CMT and IEMS servers. Thisloss would result in the following losses of functionality:

• all OAM&P functions of the CMT and IEMS, including GUI access,element management, alarms, and non-Core logs

• access to the CS 2000-Compact Core Manager on the CBM 850

The responsive action in this scenario is to initiate a switchover to thestandby CMT and IEMS servers at Site B.

Site B failureA loss of Site B would include a loss of the CBM 850 servers. This losswould result in the following losses of functionality:

• transfer of billing records from the Core to the CBM 850

• billing records resident in the CBM 850 that had not been offloadedto an OSS

• ability to receive scheduled Core OMs and logs (resulting in thembeing discarded)

• access to the CS 2000-Compact Core Manager

• backup bootp load repository

The responsive action in this scenario is to initiate a switchover to thestandby CMT and IEMS servers at Site A.

Fresh pre-install of CBM 850 cold u0To reduce the duration of downtime during an outage, it is recommendedthat the CBM 850 cold u0 be pre-installed. Contact your next level ofsupport for this task.


NN10450-900 06.023 October 2008


.

Geographical survivability impacts to CS 2000-Compact 33

Maintaining sites in a geographic survivable configurationThe following procedures contain information for OA&M auto backup andaccelerated restore capability:

• “Installing the remote backup server” (page 310)

• “Scheduling automatic backups on the remote server” (page 315)

• “Viewing configuration information for remote server backups” (page318)

• “Performing a manual backup of the target server” (page 320)

• “Initiating a recovery back to the cluster” (page 323)

• “Initiating a switch over to the remote backup server” (page 325)

• “Disabling Ethernet Routing Switch 8600 WAN Edge routing” (page327)

• “Disabling and re-enabling the router ports on the Ethernet RoutingSwitch 8600” (page 329)

Geographical survivability impacts to CS 2000-CompactThe Geographic Survivability feature allows services to continue in theevent of a natural or man-made disaster. A sub-panel to the Call AgentCard View Provisioning panel (tab) allows you to enable or disablethe feature. The following figure shows an example configuration withGeographic Survivability enabled.


NN10450-900 06.023 October 2008


.


Figure 3Call Agent Card View Provisioning panel: Geographic Survivability enabled

Failure scenariosThe following table provides summaries of system responses duringvarious failure scenarios when Geographical Survivability is enabled. Thescenarios assume redundant configurations are located in two separatesites.


NN10450-900 06.023 October 2008


.


Table 7Failure system response summaries

Scenario Response

Ethernet Routing Switch8600 failure at one site

At the site with the failed routing switch:• All nodes lose mate connectivity by using Ethernet.

• The Call Agent loses WAN backup connectivity.

• FC or GigE call data sync link remains up until the Call Agentresets.

• The Call Agent resets itself approximately 1 minute after losingnetwork connectivity and tries to boot from the network. The CallAgent keeps trying to boot until the network recovers and theboot is successful.

• The Call Agent detects IST loss, but cannot disable EthernetRouting Switch 8600 routing.

• USPc detects isolation and takes down SS7 links at the site withthe Ethernet Routing Switch 8600 failure.

• USP mated pair configurations:

— Mated pairs connected to pair of gateway POP EthernetRouting Switch 8600s:No impact to both USPs from a failure.

— Mated pairs split across a CS-LAN site (each connected tothe Ethernet Routing Switch 8600 of local CS 2000 CS-LAN):For CS 2000 - Compacts that share the same CS-LAN,the USP detects isolation and takes down its SS7 links.An Ethernet Routing Switch 8600 failure does not impactUSP mated pair behavior in other CS 2000 - Compactconfigurations.

— Mated pairs split across a CS-LAN site (each connected toone Ethernet Routing Switch 8600 connected to an edgesite):No impact from a failure.

At the site with the in-service routing switch:• The Call Agent remains active if it is already active. No outage

occurs. If the Call Agent was not active, it takes activity within2 seconds.

• SOS goes through a warm or restart (approximately 20 secondsfor the NTRX51HZ card with the MCPN905 processor and 30seconds for the NTRX51GZ card with the MPCN765 processor).

• Other nodes go active and follow the Call Agent example afterlosing mate connectivity.


NN10450-900 06.023 October 2008


.


Scenario Response

• If Site B has the in-service router, the standby CMT servermust be brought into service. (See the following ATTENTIONstatement.)

• If Site A has the in-service router, the standby CBM must bebrought into service. (See the following ATTENTION statement.)

ATTENTIONConsider using this option based on the estimated time to recoverthe fault or failure of the CS LAN versus time and effort to bring upthe cold standby system and recover the HA pair afterward.

For example, if the time to recover the CS LAN is estimated to be10 hours, consider if it is worth activating the cold standby CMTserver or CBM.

See procedure Initiating a switchover to the remote backup server.

Optical frame failure atone site

At the site with the failed optical frame:• All nodes lose mate connectivity by using Ethernet.

• Call Agent FC or GigE call data link connectivity is lost.

• WAN backup remains up.

• The active Call Agent remains active, but without sync. Nooutage occurs.The remainder of this scenario assumes the active Call Agentis at this site.

• If not already active, expect other nodes co-located with theactive Call Agent to become active after losing mate connectivity.If not already inactive, expect other nodes co-located withthe inactive Call Agent to become inactive after losing mateconnectivity. (Done without mate connectivity.)


— Mated pairs connected to pair of gateway POP EthernetRouting Switch 8600s:No impact to both USPs from a failure.

— Mated pairs split across a CS-LAN site (each connected tothe Ethernet Routing Switch 8600 of local CS 2000 CS-LAN):For CS2K-1, only the USP at the active side providesservice. For CS2K-2, both USPs provide service, but over apacket network. There are no impacts to other CS 2000s.

— Mated pairs split across a CS-LAN site (each connected toone Ethernet Routing Switch 8600 connected to an edgesite):No impact from a failure.

At the site with the in-service optical frame:• The inactive Call Agent detects IST loss. For an Ethernet

Routing Switch 8600 CS LAN using OSPF, the Call Agent


NN10450-900 06.023 October 2008


.


Scenario Response

disables OSPF. For an Ethernet Routing Switch 8600 CS LANusing Border Gateway Protocol (BGP) or for a third-party CSLAN using either OSPF or BGP, execute manual action todisable routing at the site with the inactive Call Agent.See section Disabling Border Gateway Protocol (BGP) forinstructions of disabling and enabling BGP.See section Enabling protocols BGP and OSPF.

• Other nodes become inactive and follow the Call Agent exampleafter losing mate connectivity. (Done without mate connectivity.)

• USPc detects isolation from the active Call Agent, and takesdown SS7 links at the site with the inactive USP.

• If Site B has the failed optical frame, the standby CBM must bebrought into service at Site A. (See the following ATTENTIONstatement.)

• If Site A has the failed optical frame, the standby CMT must bebrought into service at Site B. (See the following ATTENTIONstatement.)

ATTENTIONConsider using this option based on the estimated time to recoverthe fault or failure of the CS LAN versus time and effort to bring upthe cold standby system and recover the HA pair afterward.

For example, if the time to recover the CS LAN is estimated to be10 hours, consider if it is worth activating the cold standby CMTserver or CBM.

See procedure Initiating a switchover to the remote backup server.

One site is destroyed in acatastrophic event

At the site that is destroyed:• There is no activity.

• The SS7 network takes down the links to the destroyed building.


— Mated pair connected to pair of gateway POP EthernetRouting Switch 8600s:No impact occurs to either USP as they are located indifferent sites from a failure.

— Mated pair split across a CS-LAN site (each connected to theEthernet Routing Switch 8600 of local CS 2000 CS-LAN):The SS7 network takes down all links to the destroyed site.

— Mated pair split across a CS-LAN site (each connected toone Ethernet Routing Switch 8600 connected to an edgesite):If the USPs are located at the same site where the failureoccurred, the SS7 network takes down all links at the


NN10450-900 06.023 October 2008


.


Scenario Response

destroyed site. Otherwise, no impact occurs to either USPfrom the failure.

At the site that is not destroyed:• All nodes lose mate connectivity.

• The Call Agent loses all mate connectivity, including the backupWAN link, and drops sync.

• If the Call Agent is active, it remains active. No outage occurs. Ifthe Call Agent is not active, it takes activity within 2 seconds.

• If the Call Agent is inactive, it takes activity within 2 secondsfollowed by a warm or SOS restart (approximately 20 secondsfor the NTRX51HZ card with the MCPN905 processor, and 30seconds for the NTRX51GZ card with the MCPN765 processor).

• Other nodes go active, and follow the Call Agent example afterlosing mate connectivity.

• If Site B was destroyed, initiate a switchover to the standby CBMat Site A. (See procedure Initiating a switch over to the remotebackup server.

• If Site A was destroyed, initiate a switchover to the standby CMTat Site B. (See procedure Initiating a switch over to the remotebackup server.

Active Call Agent cardfails at one site

At the site with the failed Call Agent:• All nodes at the site can communicate with their mates.

At the site with the mate Call Agent:• All nodes in the site can communicate with their mates.

• The (inactive) Call Agent detects loss of connectivity with themate, detects local and WAN connectivity, takes activity, andrestarts the SOS.

• Other nodes experience disconnection from the SOS forapproximately 20 seconds for the NTRX51HZ card with theMCPN905 processor, and 30 seconds for the NTRX51GZ cardwith the MCPN765 processor (normal restart behavior)

Inactive Call Agent cardfails at one site

At the site with the failed inactive Call Agent:• All nodes in the site can communicate with their mates.

At the site with the mate Call Agent:


NN10450-900 06.023 October 2008


.


Scenario Response

• All nodes in the site can communicate with their mates.

• The (active) Call Agent detects loss of connectivity with the mate,detects local and WAN connectivity, and stays active.

• No SWACT or restart is required.

Recovery fromisolation split brain(Active/Inactive)

At both sites:• After the Call Agents can communicate with their mates, they

recognize that both are active. The Call Agent that was inactivebacks down, leaving the other Call Agent active. The fallout is toforce Unit 0 active and Unit 1 inactive.

• Other nodes can communicate with their mates, negotiateactivity, and resume normal operations.

System impact of failuresFailures could cause the following system impacts:

• When negotiating activity, the Call Agent preference is always toremain on the same side, if that side supports activity.

• If failover of the Call Agent is necessary, the Call Agent switchesactivity in less than 2 seconds. When the Callp Application performs arestart, call processing is interrupted for approximately 20 seconds forthe NTRX51HZ card with the MCPN905 processor, and 30 secondsfor the NTRX51GZ card with the MCPN765 processor (normal restartbehavior). Failovers of other Callp nodes follow the Call Agent failoverwithin 2 seconds.

• In Enterprise-only configurations where the solution contains MessageController (MC) cards connected to Message Switches (MS), ENETand TDM peripherals, the MC and MS cards are co-located in one ofthe main geographically redundant sites.

• During site isolation, when determining the appropriate master site,preference is given to the site that contains the MC cards. Thisassumes that the site is able to take activity. If necessary, activity isswitched to this side during the activity negotiation.

Recovery scenariosThe following table provides a summary of system responses duringrecovery.


NN10450-900 06.023 October 2008


.


Table 8Recovery system response summary

Scenario Response

Recovery fromisolation split brain(Active/Inactive)

• When Call Agents can communicate with their mates, theyrecognize that both are active. The Call Agent that was inactivebefore the failure backs down, leaving the other Call Agentactive. The fallout is to force Unit 0 active, and Unit 1 inactive.

• Other nodes can communicate with their mates, negotiate activityand resume normal operations.

General recoverybehavior

All elements:• continually monitor connections with their mates, and with

other network elements with which they normally communicate.When connectivity is not present, they continue to monitor theconnections for restored connectivity. (The elements continuemonitoring regardless of their activity state.)

• negotiate activity and services when connectivity recovers, andresume normal operations.


— Mated pair connected to pair of gateway POP EthernetRouting Switch 8600s:No impact to USP mated pair.

— Mated pair split across a CS-LAN site (each connected to theEthernet Routing Switch 8600 of local CS 2000 CS-LAN):USP mated pair does not negotiate activity during recovery.This is a result of USP mated pair operating in a load sharingmode; both are active during normal conditions.

— Mated pair split across a CS-LAN site (each connected toone Ethernet Routing Switch 8600 connected to an edgesite):No impact from a failure.

System impact of recoveryRecovery could cause the following system impacts:

• When negotiating activity, the Call Agent preference is always toleave activity on the same side. When recovering to a full systemconfiguration, activity remains on the same unit, without impact.

• During recovery from a split system (caused by incorrect messagerouting), node activity resolves in a few seconds. Call processing couldrequire up to 15 minutes to recover completely.

• If an inactive call agent is not in service when the IST goes down,OSPF on the Ethernet Routing Switch 8600 is not disabled on thesite of the inactive call agent, potentially resulting in failed calls due tomisdirected messages. This condition can occur on site recovery after


NN10450-900 06.023 October 2008


.

Protocols BGP and OSPF activation 41

the Ethernet Routing Switch 8600 returns to service and the opticalring is still recovering. In the event that this outage occurs, manuallydisable OSPF on the Ethernet Routing Switch 8600 or disconnect thelinks to the WAN on the site of the inactive call agent until it returns toits operational state.

Protocols BGP and OSPF activationThis section applies only to CS-LAN routers configured with EthernetRouting Switch 8600s in which BGP is the default routing protocol.

Protocols OSPF and BGP serve as an interdomain protocols to distributerouting information between endpoints in an Geographic Survivabilityconfiguration.

Recall that the CS-LAN consists of dual Ethernet Routing Switch 8600srunning as layer 2/3 switches. For redundancy, a pair of upstream routersmust be deployed on the Core network edge as the entrance to theCS-LAN.

Nortel supports a square CS-LAN topology configuration, in which eachEthernet Routing Switch 8600 is connected to one of two upstreamrouters. The following figure shows an example of the Ethernet RoutingSwitch 8600s configured for Geographic Survivability in a square topology.

Figure 4Ethernet Routing Switch 8600s configuration

In this example, each Ethernet Routing Switch 8600 includes two BGPneighbors. One BGP neighbor is the eBGP peer to the wide area network(WAN) Core router. The other BGP neighbor is the iBGP peer to itsEthernet Routing Switch 8600 mate.


NN10450-900 06.023 October 2008


.


The BGP functionality also supports the following features:

• can be used with both MCPN 905 and MCPN 765 type Call Agentcards

• selection of either BGP or OSFP as the protocol during GeographicSurvivability installation

• script setgeoconfig supports either BGP or OSPF input

• Call Control Agent (CCA) sends control commands (Disable/EnableBGP or OSPF) to the Ethernet Routing Switch 8600 based on protocolselection during installation

• Inactive CCA triggers command BGP disable command to the EthernetRouting Switch 8600 when optical connectivity is lost between twosites. When recovering optical connectivity, the inactive CCA triggerscommand BGP enable to the Ethernet Routing Switch 8600.

• Existing routing protocol disable or enable event log is used with thecorresponding OSPF or BGP protocol.

USP mated pairsTo support Geographic Survivability, a mated pairs of USPs can beconfigured with up to six CS 2000 - Compact call servers. Nortel supportsthe following USP mated pair configurations in a Geographic Survivabilitydeployment:

• mated pair of USPs connect to a pair of gateway POP EthernetRouting Switch 8600s, which is co-located with the CS-LAN or in aremote site from the CS 2000 or CS 2000 - Compact

• mated pair of USPs are split across a CS-LAN site, whereby eachUSP connects to an Ethernet Routing Switch 8600 in a local CS-LANconfiguration

• mated pair of USPs are split across a CS-LAN site and each connectsto a single Ethernet Routing Switch 8600, which also is connected toan edge site

For details on mated USP pairs, see NTP Nortel Universal Signaling PointConfiguration ( (NN10093-511)) .

Mated pair connected to a pair of gateway POP Ethernet RoutingSwitch 8600s

While configuration also applies to a non-Geographic Survivabilityenvironment, in a Geographic Survivability environment, the Cores canshare the same optical ring providing the distance is close. The matedUSP pair is co-located and connect to two Ethernet Routing Switch 8600s,which also connect to a POP gateway.


NN10450-900 06.023 October 2008


.

USP mated pairs 43

The following figure shows an example of this configuration.

Figure 5Mated pairs connected to a pair of gateway POP Ethernet Routing Switch8600s

The following conditions apply to this configuration:

• Two RTC cards cross-connect to two Ethernet Routing Switch 8600son each USP.

• Dedicated pairs of IPS7 cards serving as inter-USP mated linkscross-connect to two Ethernet Routing Switch 8600s on each USP.The mated link transfers SSNM messages. (The mated link transferstraffic during some failure conditions.)

• Other IPS7 card pairs dedicated to CS 2000 Cores connect to localEthernet Routing Switch 8600 on each USP.

• All the CS 2000s share SS7 cards or have dedicated SS7 cards.

• Only ABS stand-alone servers can be used.

• Two ABS servers are co-located with two USP pairs and connected totwo Ethernet Routing Switch 8600s.

• Both USP pairs are connected to only one IEMS server.

Mated pair of USPs split across a CS-LAN site (each connected to theEthernet Routing Switch 8600 in a local CS 2000 CS-LAN)

In this configuration, a mated pair of USPs are split across a CS-LAN site,whereby each USP connects to an Ethernet Routing Switch 8600 in a localCS-LAN configuration.


NN10450-900 06.023 October 2008


.


The following figure shows an example of this configuration.

Figure 6Mated USP pair split across a CS-LAN site (each connected to the EthernetRouting Switch 8600 of local CS 2000 CS-LAN)

The following conditions apply to this configuration:

• Two RTC cards connect to different Ethernet switch boards on eachmated USP pair.

• Dedicated pairs of IPS7 cards serving as inter-USP mated linkscross-connect to two Ethernet Routing Switch 8600s on each USP.The mated link transfers SSNM messages. (The mated link transferstraffic during some failure conditions.)

• Other IPS7 cards dedicated to CS 2000 Cores connect to localEthernet Routing Switch 8600 on each USP.

• All the CS 2000s share SS7 cards or have dedicated SS7 cards.

• The CBM and CMT can be used as an ABS server for mated USPpairs.

• An ABS server is co-located with one half of CS2Kc-1.

• Two UPS pairs connect to one IEMS server.

Mated pair of USPs split across a CS-LAN site (each connected to asingle Ethernet Routing Switch 8600)

In this configuration, a mated pair of USPs are split across a CS-LAN site.Each pair connects to a single Ethernet Routing Switch 8600, which alsocould be connected to an edge site.


NN10450-900 06.023 October 2008


.

USP mated pairs 45

The following figures show examples of this configuration. Both figuresreflect connections for RTC and IPS7 cards.

Figure 7Mated USP pair split across a CS-LAN site (each connected to a singleEthernet Routing Switch 8600)

The following figure shows the same configuration but with the EthernetRouting Switch 8600 connected to an edge site.

Figure 8Mated USP pair split across a CS-LAN site (each connected to a singleEthernet Routing Switch 8600, which connects to an edge site)


NN10450-900 06.023 October 2008


.


VLAN assignmentAll USP mated pair configurations support the following VLANs:

• Both RTC cards of USP A are assigned to OAM_USP_A_VLAN.

• Both RTC cards of USP B are assigned to OAM_USP_B_VLAN.

• IPS7 cards serving as mated links on USP A are assigned toCallP_USP_A_Mate VLAN.

• IPS7 cards serving as mated links on USP B are assigned toCallP_USP_B_Mate VLAN.

• IPS7 cards dedicated to CS2Kc-1 on USP A are assigned toCallP_USP_A_CS2K1.

• IPS7 cards dedicated to CS2Kc-1 on USP B are assigned toCallP_USP_B_CS2K1.

• IPS7 cards dedicated to CS2Kc-2 on USP A are assigned toCallP_USP_A_CS2K2.

• IPS7 cards dedicated to CS2Kc-2 on USP B are assigned toCallP_USP_B_CS2K2.

Limitations and restrictionsThe following limitations and restrictions apply to this USP configuration.

• Customers must guarantee a secure connection between the USP andthe remote CS 2000 - Compact.

• For USPs to communicate with remote CS 2000 - Compacts over theCore network, the CCA, 3PC or XA-Core HIOPs must be advertisedin the carrier’s network, although they have been configured in thecall processing private VLAN. To reach the USPs, the VLAN must beadvertised outside of the Ethernet Routing Switch 8600 CS-LAN. Otherdevices that have been provisioned in the same VLAN (for example,STORM-IA) can be exposed.

• To reduce the risk of DoS attack, provide new filtering rules andnew traffic limitation rules on the GW-POP. For example, the newfiltering rules on the GW-POP must accept traffic to the USP only if itemanated from the GWC.

• If IPsec is enabled, apply the following filtering rules to implement theGW-POP firewall.

— Discard all traffic to the CCA except traffic from the GWC subnets.

— Discard all non-ESP or non-IKE traffic (UDP traffic to and from port500).


NN10450-900 06.023 October 2008


.

SSL geographic survivability 47

• Ensure that USP mated pair-specific VLANs are not disabled during aring outage because the USPs are not split across the ring as in othergeographic-configured VLANs.

• Nortel recommends that mated USPs installations not exceed 120 kmsfrom the CS-LAN.

SSL geographic survivabilityBefore CVM11, SSL components supported network interface failure,whereby they could detect when all network interfaces connecting themto the LAN had failed. When Session Server Lines (SSL) componentsdetected a network isolation condition, they ensured that an isolatedcomponent did not remove activity from its mate when the isolationcondition was repaired. This behavior mirrors fault tolerant behaviorfor a component that detects itself to be in the non-surviving site of aGeographic Survivable configuration. The affected components arecompletely isolated from the rest of the network while call processingcontinues.

SSL components detect themselves network isolated under the followingconditions:

• the Geo mode is enabled in the CS 2000 Call Agent window

• no active CS 2000 Compact Call Agent exists when an SSL SystemManager or Session Manager starts

The SSL component should detect the isolation before it attemptsactivation. The component shuts itself down and waits until there is anactive CS 2000 Compact Call Agent present before it restarts itself.

Non-surviving site network interface isolationSSL Geographic Survivability supports a geographic distribution ofredundant SSL components across a second site to preserve callprocessing, billing and element management functions in case of a failureisolating one of the sites. In addition, call capacities do not degradefrom the failure of one of the sites. Network requirements and facilitiesinterconnecting the two sites is efficient and cost effective.

SSL components that detect themselves to be in a non-surviving site of aGeographically Survivable configuration behave as if they do when theydetect a network interface failure. That is, they consider themselves to benetwork isolated.

This feature introduces a mechanism to detect the condition of anon-surviving site of a Geographically Survivable configuration. Detectingnetwork isolation of a non-surviving site of a Geographically Survivable


NN10450-900 06.023 October 2008


.


configuration is based on the reachability of the active IP address of theCS 2000 Call Agent. Internet Control Message Protocol (ICMP) echorequest (ping) messages are sent to the active IP address of the CS2000 Compact Call Agent. SSL components that detect this IP address"unreachable" consider themselves to be in the non-surviving site (thatis, network isolated).

See NTP SSL Configuration (NN10023-511) for details on how to enableor disable pinging on the active IP address of the CS 2000 Call Agent.

Network isolation detection for a non-active network element instance(NEI)

When a non-active NEI detects itself to be network isolated, it shuts itselfdown and waits for the network isolation condition to clear before restartingitself.

This action avoids a dual-active scenario when a stand-by NEI detectsitself to be network isolated (whereby its mate is active) before falselydetecting its active mate as failed. In this case, it also shuts itself down.The NEI restarts itself when the network isolation condition is cleared. Thismeasure prevents the active mate from having to decide if it should cedeactivity.

Network isolation detection for an active NEIAn active NEI does not deactivate itself unless it detects that its mate isalso active. Thus, an active NEI remains active when it detects itself tobe network isolated.

SST geographic survivabilityGeographic survivability is a mechanism that allows the continuationof service during and after a catastrophic event such as fire, flood,tropical storm, or an act of terrorism at a call server site. Thus, the keycomponents of the system must be geographically distributed betweenlocations that are some distance apart, interconnected over a fault-tolerantnetwork. In the event that the components at one site are lost, the systemwill survive under the control of the components at the other site.

In a geographically survivable configuration, the SST is configured acrosstwo sites. If the SST at one site loses connectivity, the SST at other sitetakes over the activity and is able to process the new calls.

In a geographically survivable configuration

• the deployment of split session-server pairs is supported

• the SST maintains 99.999 % availability for Callp


NN10450-900 06.023 October 2008


.

Geographic survivability limitations and restrictions 49

• the time for fail-over is equivalent, on the same order of magnitude, tothe fail-over time for a non-geographically survivable configuration

• stable calls and billing are maintained during a fail-over

Geographic survivability limitations and restrictionsThe following limitations and restrictions apply to the GeographicSurvivability feature:

• The physical distance between active and standby sites is limited to120 KM/75 miles.

• Each site must have a single Ethernet Routing Switch 8600 with dualswitch fabric and CPU blades or third-party equivalent.

• Synchronization of data between two CCA blades over GigE linksapplies to the CS 2100 market with reduced capabilities. Thisconfiguration applies just to Enterprise solutions.

• In Enterprise hybrid configurations (with TDM equipment homed atone site), the TDM equipment is not geographically redundant. Indetermining the master site, preference is given to the TDM side onlywhen either side can support Callp. If necessary, perform a SWACT tothe TDM side to allow Callp on that side.

• Because the Call Agent interacts with the Ethernet Routing Switch8600, the feature requires that each site have only one routing switchand IST links configured between sites. Dual Ethernet Routing Switch8600s at each site and SMLT links between sites are not supported.Interactions between the Call Agent and the CS LAN are supported toprevent split brain scenarios (by disabling OSPF) when the EthernetRouting Switch 8600s are used for the CS LAN. Upgrades fromprevious releases in an Enterprise geographic survivable configuration(which have dual Ethernet Routing Switch 8600’s at each site) requirethat the dual Ethernet Routing Switch 8600s be migrated to a singleEthernet Routing Switch 8600 site.

• When a total loss of communication between sites occurs (that is, allthree master links are down), the two Call Agents cannot negotiateactivity decision. The decision is based on connectivity check fromeach site the WAN network.

— While unlikely, it could be possible to have an active/active (splitbrain) scenario, or an inactive/inactive scenario (no processing).

— The WAN backup path mitigates the risk of optical ring failure. TheWAN connection check helps resolve activity when the backup pathis down.


NN10450-900 06.023 October 2008


.


• CS 2000 - Compact supports only a single time zone setting. If the twophysical sites are in different time zones, Nortel recommends that thetime zone be set to either GMT or the time zone of one of the sites.

• Both Session Server units of a pair are located at the same site. Foroffices with Message Controllers, Nortel recommends that the SessionServers be located at the same site as the TDM components.

• For maximum redundancy, the WAN backup path must be configuredseparately from the optical network, as follows:

— special vlans configured on Ethernet Routing Switch 8600 forbackup path use only

— vlans route over the WAN network instead of over the optical ring

— vlans are not disabled with OSPF disable

— alarm generated for lack of connectivity

• Gateways and services node components of CS 2000 - Compact aresingle units, and are not geographically redundant. Where the nodesare located and how they are connected to the network affects whetherthey survive a failure. Although the same nodes are supported inconfigurations with and without Geographic Survivability, there is nochange in configuration or connection in the configuration with theGeographic Survivability configuration.

CAUTIONLine data integrity audit impacts the maintenance actions suchas GWC status and GWC swact. At times, the bearer networkcannot be retrieved from the core due to the bearer networktimeout, as it is design intent.

Real Time Billing fundamentalsReal Time Billing (RTB) allows billing records to be available for transferfrom the core manager 30 seconds after the time the billing records aregenerated. RTB downloads a small group of records to the DIRP billing fileat the downstream destination as they are added to the open billing fileon the core manager. RTB uses file transfer protocol (FTP) or OpenSSHfor secure file transfer protocol (SFTP) through an Ethernet connection todeliver billing records.

ATTENTIONOutbound file transfer using FTP requires the downstream system to be runningan FTP server that complies with RFC 959. In particular, for Real-Time Billing,the FTP server must support the "APPE" (Append) message.


NN10450-900 06.023 October 2008


.

Real Time Billing fundamentals 51

TerminologyTo understand how the SBA processes and routes the billing records itreceives for RTB, the following terminology must be understood:

• Stream - A stream, or billing stream, can be conceptualized as apipeline through which billing records received from the core pass.For each stream component that exists on the core, a correspondingstream component exists on the core manager. Billing records createdby calls pass through the stream from their point of origination on thecore to the core manager, where they are stored on disk.

• Sub-stream - A stream is further divided into Primary and Recoverysub-streams. The Primary sub-stream handles the current recordsbeing sent by the core. The Recovery sub-stream is only activeafter the SBA is unable to transfer records from the core to the coremanager and temporarily stores the records on the core. When thecore is once again able to re-establish the connection to the coremanager, the stored records are sent to the core manager in aRecovery sub-stream while, concurrently, the current records are sentin the Primary sub-stream.

• Active file state - When records are written to a file that is open onthe core manager, the file name on the core manager is prefixed withan "A", which means "active". When a billing file’s content is beingwritten to a file on a downstream processor, the name of the file on thedownstream processor is also prefixed with an "A".

• Unprocessed file state - After the file on the core manager receivesall of its billing records, the file is closed and the name of the file isprefixed with a "U", which means "unprocessed". In the same manner,after the file content has been transferred to a downstream processor,the file receiving this content on the downstream processor is alsoprefixed with a "U".

• Processed file state - When a billing file on the core manager is closedand its content has been received by all designated downstreamdestinations, the file is then eligible for removal in order to free up diskspace. The file name prefix then changes from "U" to "P", meaning"processed".

SBA file transfer subsystemThe SBA file transfer system uses a schedule tuple for scheduled filetransfers. This schedule tuple is specified by stream name, file format,and destination. For each tuple, different file transfer parameters can bespecified, such as start time, stop time, and file transfer interval. Therecan be only one tuple for each combination of stream, file format, anddestination.


NN10450-900 06.023 October 2008


.


The tuple contains a field indicating whether it is active. Scheduled filetransfers occur only when the tuple is active. An interval setting in theschedule tuple determines how often SBA checks to see whether there areunprocessed files waiting to be sent downstream. When this interval isexceeded, the files are transferred downstream.

Real Time Billing file transferThe RTB rts (return to service) command, which is issued from the billingmaintenance interface (billmtc), is used to initiate the transfer of openbilling files to the downstream customer site. The command specifies thestream, file format, and destination. RTB uses the appropriate fields in theschedule tuple corresponding to this stream. RTB attempts to transferrecords to the active billing file at the primary destination IP addressof the downstream destination specified in the schedule tuple. For theprocedure used to perform this command, see "Returning RTB streaminstance to service" in Nortel Core and Billing Manager 850 Accounting ((NN10363-811)) .

While RTB is transferring an open file, on the downstream processor thefile name is prefixed with an "A" indicating an open, "active" file. Whenthe file transfer is complete, the file prefix on the downstream processor ischanged to a "U", the same file prefix used when scheduled file transferssucceed.

When RTB is in service (InSV), the RTB Bsy (busy) command stops thecurrent open file transfer by first closing the current open file on the coremanager, sending the remainder of the file downstream, and then closingthe FTP connection with the downstream processor. The procedureused for querying the current operational state of RTB is "Querying thestatus of RTB for a billing stream" in Nortel Core and Billing Manager 850Accounting ( (NN10363-811)) .

The schedule tuple must be active for a stream in order for the streamto be processed. When the two file transfer applications, scheduledtransfer and Real Time Billing, are configured both must acknowledge anunprocessed file ("U" file prefix) before the file can become processed("P" file prefix). Thus, after RTB transfers a file, the file state will remain"unprocessed" until the next scheduled transfer event. When that transferevent occurs, the scheduler examines all unprocessed files and treatsthem according to whether they have already been transferred by RTB.The files that have not been transferred by RTB are transferred and movedto the "processed" file state after a successful transfer. The files that havebeen transferred by RTB are moved directly to the "processed" file statewithout retransmission.

Nortel suggests to set the Outbound File Transfer active status to ’Yes’when configuring Real Time Billing.


NN10450-900 06.023 October 2008


.

Real Time Billing fundamentals 53

Connection managementIn normal operation, open files transferred by Real Time Billing are sentonly to the Primary IP destination specified in the schedule tuple for eachdestination. If a problem occurs with that destination and open file transferfails, the current file is closed. RTB will be tried again on the next openfiles based on the RTB MIB value RTBMaxConsecutiveFailures. After allfile transfers allowed by the RTBMaxConsecutiveFailures RTB MIB valuehave been attempted, a critical alarm is raised, a log is issued, and RTB ismoved to the SYSB state. In this state, open file transfer is not active.

The retry behavior of RTB differs from that of a scheduled transfer. Inthe case of a scheduled transfer the primary address is tried first, and ifit fails, attempts to re-transmit the file are repeated until the number ofretries is exhausted. The retry attempts alternate between the primary andalternate destinations indicated in the schedule tuple. In the case of anRTB transfer, however, RTB will not attempt to re-transmit the file sincethat impacts the ability to send current records. Thus, RTB closes the fileand retries transfer on the next file opened. In addition, unlike scheduledtransfer, RTB only uses the primary destination.

When RTB closes billing files, it cannot send the billing files downstream.The billing files are, however, automatically transferred from the coremanager during the next scheduled transfer when the schedule tupleis active. The billing files can also be transferred manually. For theprocedure used to transfer the billing files manually, see "Sending billingfiles from disk" in Nortel Core and Billing Manager 850 Accounting ((NN10363-811)) .

Manual intervention is required to restore RTB when it is in the SYSBstate. The problem can often be attributed to a network connection thatis no longer functioning properly. The RTB IPTest command can beused to "ping" the primary downstream address indicated in the scheduletuple to determine this. A SYSB state may also occur if the protocol hasbeen changed in the schedule tuple to something other than the requiredprotocol for RTB. When the problem that forced RTB into the SYSB stateis resolved, the RTB Bsy and Rts commands can be used to bring RTBinto service.

AlarmsFor information about RTB alarms, refer to Nortel Core and BillingManager 850 Fault Management ( (NN10351-911)) .


NN10450-900 06.023 October 2008


.



NN10450-900 06.023 October 2008


.

55.

Disaster recovery configurationThis chapter provides the tasks for disaster recovery for the Nortel CarrierVoIP solutions.

Disaster recovery configuration tasksThis work flow shows you the sequence of tasks you perform to configurean end-to-end disaster recovery. To link to any task, go to “Disasterrecovery configuration task navigation” (page 56).


NN10450-900 06.023 October 2008


.

56 Disaster recovery configuration

Figure 9Disaster recovery configuration tasks

Disaster recovery configuration task navigation• “Disaster recovery configuration” (page 55)

• “Preparation for disaster recovery” (page 57)

• “Network power down” (page 331)

• “Network power up” (page 375)

• “Disaster recovery power up” (page 455)

• “Device audits” (page 473)


NN10450-900 06.023 October 2008


.

57.

Preparation for disaster recoveryThis chapter provides the procedures for preparing for disaster recovery ofthe Nortel Carrier VoIP solutions.

Navigation

• “Recovering the SPFS system if updisk daemon dies” (page 58)

• “Installing optional software on a Core and Billing Manager” (page 64)

• “Installing the Passport Log Streamer application” (page 71)

• “Installing the DDMS” (page 59)

• “Installing the OM Data Delivery application” (page 68)

• “Installing the SBA and AFT software packages” (page 73)

• “Installing the GR740PT application server” (page 74)


NN10450-900 06.023 October 2008


.

58 Preparation for disaster recovery

Recovering the SPFS system if updisk daemon dies

Use this procedure if an updisk daemon fails or one of the datasets goesdown on either the active or inactive node.

Procedure stepsOn the node displaying the updisk daemon or dataset failure

Step Action

1 Enter StopCluster

2 Enter StartCluster

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 59

Installing the DDMS

Install the DDMS application.

After Enhanced Password Control is in effect on the CM or Core, theDDMS software has the ability to manage automatic password changingon the CBM and the CM, before passwords expire. It is not necessary tomanually change any of the passwords for the SDM01-SDM04 user IDs onthe CBM or CM. After the DDMS software is returned to service, it readsthe tables, ofcopt and ofceng, on the CM to determine whether EnhancedPassword Control is in effect. If Enhanced Password Control is in effect,the DDMS software reads the password lifetime value and automaticallychanges the passwords one day before they expire.

Prerequisites• For a successful installation of DDMS, verify that the Log Delivery

Service application is in service.

• If you make manual changes to the password lifetime value, or if youturn the Enhanced Password Control off or on, you must synchronizethese changes with the DDMS software by performing a bsy or rtsof the DDMS application. If you change any of the SDM01-SDM04passwords manually, you must apply the same password changes inthe DDMS configuration file.

Procedure steps

Step Action

1 At your workstation, at the CLI prompt on the core, configure theEnhanced Password Control for the SDM01 user ID:

permit sdm01 <sdm01_pswd> 4 10000 english all

ATTENTIONIf Enhanced Password Control is in effect on the CM, the passwordmust be at least six characters in length.

2 Configure Enhanced Password Control for the SDM02 user ID:


3 Configure Enhanced Password Control for the SDM03 user ID:


4 Set Enhanced Password Control for the SDM04 user ID:



NN10450-900 06.023 October 2008


.


5 Create the first required logical volume for the DDMS application:

makelv /cbmdata/00/osscomms 16

6 Set the access privileges of the first logical volume for the DDMSapplication:

chmod 755 /cbmdata/00/osscomms

7 Set the ownership privileges of the first logical volume for theDDMS application:

chown maint:maint /cbmdata/00/osscomms

8 Create the second required logical volume for the DDMSapplication:

makelv /cbmdata/00/ossaps 112

9 Set the access privileges of the second logical volume for theDDMS application:

chmod 755 /cbmdata/00/ossaps

10 Set the ownership privileges of the second logical volume for theDDMS application:

chown maint:maint /cbmdata/00/ossaps

11 Create the third required logical volume for the DDMSapplication:

makelv /cbmdata/00/ossapslog 112

12 Set the access privileges of the third logical volume for theDDMS application:

chmod 755 /cbmdata/00/ossapslog

13 Set the ownership privileges of the third logical volume for theDDMS application:

chown maint:maint /cbmdata/00/ossapslog

14 Apply the two software application packages, OSSand Application Svcs and OSS Comms Svcs . Specify/cdrom/cdrom/applications/cbm/packages as the source directorywhen you perform that procedure.

15 You are prompted automatically to configure the OSS CommsSvcs package.

ATTENTIONThe OSS and Application Svcs package does not requireconfiguration.

16 If you are prompted automatically to configure the OSS CommsSvcs package then go to 29

OR


NN10450-900 06.023 October 2008


.

Procedure steps 61

If you are not prompted automatically to configure the OSSComms Svcs continue with the next step.

17 Access the configuration level of the maintenance interface:

cbmmtc config

18 In the list of applications, locate the OSS Comms Svcsapplication and record its application number (located next to thenames of the applications). Select the application:

select <application number>

In response to the command, the OSS Comms Svcs applicationis highlighted on the cbmmtc config screen.

19 Invoke the configuration of the OSS Comms Svcs application:

config

20 When prompted to enter the logroute tool, as shown in thefollowing figure, press Enter:Figure 10DDMS logroute tool banner

The Logroute Main Menu appears.

21 Select the Device List menu

1

The Device List Menu screen appears.

22 Select 1 to display the Device List screen.

23 If the list includes device /cbmdata/00/logs/ossaps/ossapslogthen continue with the next step.

OR

If the list does not include device /cbmdata/00/logs/ossaps/ossapslog skip the next step.

24 Press the Enter key. .

25 Begin to add a new device:

2

26 Select a file device:


NN10450-900 06.023 October 2008


.


3

Example Response:

Enter file name ==> /data/logs/

27 Complete the path name:

ossaps/ossapslog

Routing for the DDMS is now set up.

28 When prompted, enter STD log format (from the rangedisplayed).

29 When prompted, set the ECORE option to ON.

30 Select addrep:

a

31 Enter the log identifier:

DDMS

32 When prompted to enter more log routing details, enter

N

33 Save the new device:

y

Response:

Save completed -- press return to continue

34 Press the Enter key and return to the Add Device screen.

35 Return to the Device List Menu screen:

5

36 Return to the main menu screen:

6

37 Exit logroute:

6

The CM User Setup screen appears and the required CM users,SDM01-SDM04, for DDMS are added to the DDMS configurationfile. The passwords for these users are the same as thoseentered in step 1.

ATTENTIONThe user IDs and passwords are not case sensitive. You can changethem after this installation is complete.

38 Add a new user for each of the required user IDs:

1


NN10450-900 06.023 October 2008


.

Variable definitions 63

39 When prompted, enter the user name (for example, sdm01).

40 When prompted enter the password.

ATTENTIONThe first entry of a user name and password generates the followingmessage: Error: file not valid. You can ignore this message.

41 If applicable, continue to add other user names and passwordsat the prompt, otherwise continue with the next step.

42 Exit the CM User Setup screen:

0

The DDMS Clients Configuration screen appears.

43 Add a new DDMS client.

1

ATTENTIONThe DDMS clients are the CS 2000 Management Tools servers withthe SESM load.

44 When prompted, enter the IP address for each of the CS 2000Management Tools servers and press the Enter key, after eachentry. If the CS 2000 Management Tools server is a clusterconfiguration, add the IP address of both the active and inactiveunits.

45 After you have entered all the IP addresses, type

done

46 Exit the DDMS clients configuration screen:

0

--End--

Variable definitionsVariable Value

<sdm0n_pswd> The CM password for user (SDM01,SDM02,SDM03,SDM04)

<application number> The number associated with the OSS CommsSvcs application, that you noted


NN10450-900 06.023 October 2008


.


Installing optional software on a Core and BillingManager

Install optional software on a Core and Billing Manager (CBM).

Refer to the “Job aid” (page 66) for a listing of the optional softwarepackages (filesets) that can be installed with this procedure.

ATTENTIONThis procedure must be performed on a pre-cloned system. If the procedure isnot performed on a pre-cloned system, clone the image of the active node to theinactive node of the cluster after the software package has been installed andconfigured, and after the active node has been made patch-current.

Procedure stepsAt your workstation

Step Action

1 Open a connection to the active node of the CBM using SSH andlog on as the root user:

ssh -l root <ip_address>

2 Enter the password for the root user.

3 To install the DDMS application, perform steps 1 and 5 only in“Installing the DDMS” (page 59).

4 Go to step 18.

5 To install the OMDD application then perform step 1 only, in“Installing the OM Data Delivery application” (page 68).

6 Go to step 18.

7 To install the log delivery service application, perform “Installingthe Passport Log Streamer application” (page 71).

8 Go to step 24.

9 To install the SBA or AFT applications, perform “Installing theSBA and AFT software packages” (page 73) .

10 Go to step 24.

11 To install the GR740PT application server, perform “Installing theGR740PT application server” (page 74).

12 Go to step 24.

13 To install the FTP proxy application, refer to Nortel Coreand Billing Manager 850 Administration and Security ((NN10358-611)) .


NN10450-900 06.023 October 2008


.


14 Go to step 17.

15 To install the Backup Restore Manager software, perform“Installing the Backup Restore Manager software” (page 94), andthen go to step 17.

16 Go to step 24.

17 To apply any other optional software application, perform“Applying software packages on a Core and Billing Managerusing the CBMMTC interface” (page 88).

18 If required, return to step 3 to continue applying new softwareapplications.

19 Ensure that you create all required logical volumes for theapplications that you are install before you continue.

20 If you created any logical volumes, reboot the CBM:

init 6

21 If required, complete installation of the DDMS application byperforming the remaining steps of “Installing the DDMS” (page59), starting with step 14.

22 Go to step 24.

23 If required, complete the installation of the OMDD applicationby performing the remaining steps of “Installing the OM DataDelivery application” (page 68), starting with step 2.

24 Ensure that your CBMs are patch-current. For patchingprocedures, see Nortel ATM/IP Solution-level Administration andSecurity ( (NN10402-600)) .

25 Clone the active node image to the inactive node by performingthe procedure, “Cloning the image of the active node to theinactive node” (page 91).

26 If applicable, return to the higher level task flow or procedure thatdirected you to this procedure.

27 This procedure is complete.

--End--


<ip_address> IP address of the active node of the CBMcluster.


NN10450-900 06.023 October 2008


.


Job aidThe following table lists filesets (applications) that the CBM0090 loadincludes. The table shows which filesets are included with the CBM atthe time of installation (Base) and which filesets are optional that you caninstall.

Table 9Filesets available for the Core and Billing Manager

Fileset Description Type

SDM_BASE.version_20.81.0.0 Load lineup information Base

CBM_SETUP CBM installation and upgrade tool;available only on CD

Base

NT_SIM.tools Patching tools Base

SDM_ACE SDM ACE distribution Optional

SDM_AFT.DMS500 SBA automatic file transfer Optional

SDM_BASE.base Platform base Base

SDM_BASE.comm Platform maintenance common Base

SDM_BASE.gdd Generic data delivery Base

SDM_BASE.logs.client Log Delivery Service client Optional

SDM_BASE.logs Log Delivery Service Base

SDM_BASE.mtce Platform maintenance Base

SDM_BASE.omsl OM Access Service Base

SDM_BASE.tasl Table Access Service Base

SDM_BMI.bmi Base Maintenance Interface Optional

SDM_DDMS_ossaps OSS and Application Svcs Optional

SDM_DDMS_osscomms OSS Comms Svcs Optional

SDM_BASE.util Platform Utilities Base

SDM_DEBUG.tools SDM/CBM Debug Helper Tools Base

SDM_DMA.dma DMS Maintenance Application Optional

SDM_FTP.proxy FTP Proxy Optional

SDM_GR740PT.gr740pt GR740 Pass Through Optional

SDM_LOGS.mdm Passport Log Streamer Optional

SDM_OMDD.omdd OM Delivery Optional

SDM_REACHTHRU.rttl1 Reach Through SPM Optional

SDM_SBA.DMS500 SDM Billing Application Optional

ATTENTIONBase = included with the CBM


NN10450-900 06.023 October 2008


.

Job aid 67

Table 9Filesets available for the Core and Billing Manager (cont’d.)

Fileset Description Type

SDM_SCFT.scft SSH Core File Transfer Optional

SDM_CLP.clp CBM LI Proxy Optional

SDM_CLP.clp CBM LI Proxy Optional

NTbkupmgr Succession Provisioning Data SynchManager

Optional

NTdtsv CEM DMS Data Server Optional

NTprxy CEM Telnet Ftp Handler Optional

NTsaf CEM Store and Forward Optional

NTbulk CEM Bulk Formatter Base

ATTENTIONBase = included with the CBM


NN10450-900 06.023 October 2008


.


Installing the OM Data Delivery application

Use this procedure to install and configure the OM Data Deliveryapplication on the CBM cluster.

Prerequisites• OM Access Service and Table Access Service application filesets must

be installed and in service on the core manager.

• For the wireless market, the Nortel support group must increase thebuffer size within the OM Access Service to 2.5 MB to accommodatethe amount of data transferred by the front end for a transfer periodof every 30 minutes.


Step Action

1 Create the following logical volume (directory for a file system)required for the OMDD software package you are installing:

makelv /cbmdata/00/omdata 1008

2 Apply the SDM_OMDD.omdd software package located in the/cdrom/cdrom/applications/cbm/packages directory (refer toApplying software packages on a Core and Billing Managerusing the CBMMTC interface for further information).

ATTENTIONYou must specify the CD-ROM directory /cdrom/cdrom/applications/cbm/packages as the source directory path when performing theapplying software packages procedure.

3 Enter cbmmtc config to access CBM maintenance interfaceconfig:

4 Enter config <n> to configure OM Data Delivery

The system indicates that the Tuple Number option is inactiveand prompts you to determine whether you want to activate it.

ATTENTIONThe Tuple Number option allows you to activate or disable a tuplenumber so that it can be included in a CSV file with other OMinformation.

5 Enter y to activate or n to disable the tuple number.

The system prompts you to confirm whether the MultiserviceData Manager (MDM) and core manager are integrated.


NN10450-900 06.023 October 2008


.

Procedure steps 69

6 To indicate that the MDM is connected to the core manager forcollecting Passport 15000 performance measurement data, type

y

7 When prompted, enter the IP address of the first MDM you wantto connect.

8 When prompted, enter the hostname of the first MDM.

9 When prompted, enter the IP address of the second (alternate)MDM you want to connect.

10 When prompted, enter the hostname of the second MDM.

11 When prompted, enter the port for 5-minute performance PM(performance measurement) data. The default port is 1646.

12 When prompted, enter the port for 30-minute PM data. Thedefault port is 1647.

You are prompted as to whether you want to use customconnection retry settings. In case of connection failure, OMDDwill try connecting to the MDMs, alternatively.

13 Enter y to use custom retry settings.

14 Go to step 16.

15 Enter n to use the default retry settings.

16 Go to step 19.

17 To configure the custom retry settings, enter a numeric value (inseconds) for the first connection retry interval.

ATTENTIONValues higher than 300 seconds are not recommended as they canadversely affect recovery time.

18 Enter the number of retry attempts for the first retry interval.

19 Enter a numeric value (in seconds) for the second connectionretry interval.

20 Enter the number of retry attempts for the second connectionretry interval.

21 Enter a numeric value (in seconds) for the third connection retryinterval.

22 To confirm (save) the configuration data, entery, otherwiseentern to reenter all of the configuration data.

23 The system indicates that the configuration is complete.

Press the Enter key.

24 The system indicates that the changes will take place after theOM Data Delivery application is restarted.

Press the Enter key to restart the OM Data Delivery application.


NN10450-900 06.023 October 2008


.


25 Exit the maintenance interface by typing:

quit all


--End--


NN10450-900 06.023 October 2008


.

Procedure steps 71

Installing the Passport Log Streamer application

Use this procedure to install and configure the Passport Log Streamerapplication on the CBM cluster.

For full operation, the log delivery application requires installation of thefollowing application filesets:

• Log delivery service (base software)

• Log delivery service client (optional software)

• Generic Data Delivery (base software)

• Passport Log Streamer, if the core manager needs to communicatewith the Multiservice Data Manager (MDM) for fault data. (optionalsoftware)

Prerequisites• Ensure that no disk faults exist on the core manager.

• Remove any restrictions for the configured MDM ports from all firewallsbetween the MDM and the CBM to ensure that the Passport LogStreamer can communicate with the configured MDMs and collect logs.


Step Action

1 Perform the procedure to apply the SDM_LOGS.mdm_21.39.9.0.pkg software package located in the/cdrom/cdrom/applications/cbm/packages directory (refer toApplying software packages on a Core and Billing Managerusing the CBMMTC interface for further information). Becauseyou use the CD-ROM to install the application, specify/cdrom/cdrom/applications/cbm/packages as the directory path ofthe source directory when you perform that procedure.

2 When prompted, enter the IP address for the first MDM node.

3 When prompted, enter the IP address for the second MDM node.

4 When prompted, enter the port number configured for thepserver application on the first MDM node.

5 When prompted, enter the port number configured for thepserver application on the second MDM node.


NN10450-900 06.023 October 2008


.


6 When prompted, type n to indicate that you do not want toreceive MDM logs.

7 When prompted, type n to indicate that you do not want tospecify Passport 15000 log filters.

8 When prompted, type n to indicate that you do not want tospecify Ethernet Routing Switch 8600 log filters.

9 When prompted, enter y to confirm the configuration data.

10 Place the log delivery service application and the Passport LogStreamer application into service by accessing the Application(Appl) level of the CBM maintenance interface:

appl

11 Busy the application filesets:

bsy <fileset_number> <fileset_number>

12 Return the application filesets to service:

rts <fileset_number> <fileset_number>

After the application filesets are in service, the system retrievesany current log records. To view or store the log records, seeNortel Core and Billing Manager 850 Fault Management ((NN10351-911)) .

13 Exit the CBM maintenance interface:

quit all


--End--


<fileset_number> The number next to each of the applicationfilesets.


NN10450-900 06.023 October 2008


.

Procedure steps 73

Installing the SBA and AFT software packages

Use this procedure to install the SuperNode Billing Application (SBA) andAutomatic File Transfer (AFT) software packages on the CBM cluster.

Procedure stepsAt your workstations

Step Action

1 Using the procedure “Applying software packages on a Coreand Billing Manager using the CBMMTC interface” (page 88),apply the SBA and AFT software packages located in the/cdrom/cdrom/applications/cbm/packages directory.

2 Create the necessary logical volumes (directories for filesystems) required for the SBA using procedure "Adding a logicalvolume through the command line" in Nortel Core and BillingManager 850 Accounting ( (NN10363-811)) .

3 Configure the SBA for operation (refer to Nortel Core and BillingManager 850 Accounting ( (NN10363-811)) for the appropriateprocedures).

4 Configure AFT for operation (refer to Nortel Core and BillingManager 850 Accounting ( (NN10363-811)) . for the appropriateprocedures).


--End--


NN10450-900 06.023 October 2008


.


Installing the GR740PT application server

Use this procedure install the GR740PT application server.

Prerequisites• The settings for office parameters eadas_dc_interface and

eadas_nm_interface in table OFCVAR, and the settings for the EADASSOCs (OAM00005 and OAM00006) are correct for your configuration.

• OAM00004 for EADAS/DC is ON and that office parameterseadas_mpc_and_link and netminder_mpc_and_link are appropriatelydatafilled in table OFCVAR when BX25 connectivity is required.


Step Action

1 Using the procedure “Applying software packages on a Coreand Billing Manager using the CBMMTC interface” (page88), apply the GR740PT software package located in the/cdrom/cdrom/applications/cbm/packages directory.

You are prompted to enter the mode of security.

2 If you are not configuring GR740PT in non-secure mode doselect 1. Non-secure.

3 If you are configuring GR740PT in local secure mode do select2. Local (SSH) security.


--End--

Job aidThe following table lists the supported configurations for EADAS GR740PTapplication server:

Table 10CM EADAS TCP/IP configurations

Supported configurations

Setting for eadas_dc_interface

Setting for eadas_nm_interface

SOC OAM00005

SOC OAM00006

DC and NM over BX25 X25 N/A ON IDLE

DC and NM over TCP/IP TCP_IP N/A ON IDLE


NN10450-900 06.023 October 2008


.

Job aid 75

Table 10CM EADAS TCP/IP configurations (cont’d.)

Supported configurations

Setting for eadas_dc_interface

Setting for eadas_nm_interface

SOC OAM00005

SOC OAM00006

DC and Netminder overBX25

X25 X25 IDLE ON

DC over BX25 andNetminder over TCP/IP

X25 TCP_IP IDLE ON

DC over TCP/IP andNetminder over BX25

TCP_IP X25 IDLE ON

DC and Netminder overTCP/IP

TCP_IP TCP_IP IDLE ON

The following table lists the channel assignments for EADAS. Note that DCEADAS channels 1, 2, and 3 support TR-740/746 compliant header andmessage. NM EADAS channels 1, 2, and 3 support SR3942 and TR746 toNetminder:

Table 11EADAS channel assignments

Description Service name TCP port MTS offset

DC EADAS lc 1 DC_EADAS_LOG_CHAN1 9550 234



NM EADAS lc 1 NM_EADAS_LOG_CHAN1 9553 237




NN10450-900 06.023 October 2008


.


Configuring RTB for a billing stream

Use this procedure to perform the following real time billing (RTB)functions:

• add RTB to a billing stream

• change the RTB configuration for a billing stream

• delete RTB from a billing stream

PrerequisitesThis procedure has the following prerequisites:

• Configure the billing stream. Perform the procedure "Configuring abilling stream on the core manager" in Nortel Core and Billing Manager850 Accounting ( (NN10363-811)) . RTB requires outbound file transferand DIRP file format.

• Configure outbound file transfer for the stream. Perform the procedureConfiguring the outbound file transfer schedule" in Nortel Core andBilling Manager 850 Accounting ( (NN10363-811)) . RTB supportsReal-time File Transfer Protocol Wrapper (RFTPW), Real-timeKey-based Secure File Transfer (RKSFT), and Real-time Secure FileTransfer Protocol (RSFTP) protocols.

This procedure requires the following information:

• maximum number of retry attempts after RTB fails to transfer a billingfile before RTB raises a critical alarm

• directory location on the data processing and management system(downstream OSS) of the RTB test file and partial file

You must be a user in a role group authorized to perform accounting-manage actions.

Procedure stepsATTENTIONInstructions for entering commands in the following procedure do not show theprompting symbol, such as #, >, or $, displayed by the system through a GUIor on a command line.

Configuring RTB for a billing stream


NN10450-900 06.023 October 2008


.

Procedure steps 77

At any workstation or console

Step Action

1 Log into the core manager as a user authorized to performaccounting-manage actions (refer to Nortel CS 2000 CoreManager Administration and Security ( (NN10170-611)) forinformation on how to log on to the core manager).

2 Access the BILLMTC interface:

billmtc

3 Access the schedule level:

schedule

4 Display and verify the schedule tuple:

list <stream_name>

Verify the following fields:

• File_Format_Type: DIRP

• Protocol: RFTPW

• Active: No

Before configuring RTB ensure that the fields contain the valuesshown in this list.

For secure file transfer, you may choose SFTPW or RSFTP(password-based user authentication) or RKSFT (key-based userauthentication).

5 Access the RTB level:

rtb

6 Access the CONFRTB level:

confrtb

7 To add RTB to a billing stream, go to step 10.

8 To change the RTB configuration for a billing stream, go to step21.

9 To delete RTB from a billing stream, go to step 33.

10 Add RTB to a billing stream:

add <stream_name> <file_format> <destination>

11

ATTENTIONIf auto recovery is turned on, do not configure multiple RTBdestinations with the same Test File Location or Partial File Locationon the DPMS.


NN10450-900 06.023 October 2008


.


Enter the desired maximum retry attempts before RTB raises acritical alarm, and press the Enter key.

The default value is 3.

12 Enter the directory on the DPMS where the RTB test file willreside and press the Enter key.

The default directory is the Remote_Storage_Directory asconfigured in the Schedule tuple for this stream.

13 Enter the directory on the DPMS where the RTB remote partialfile resides, and press the Enter key.


Example response:

You entered:RTB Max Consecutive Failures: 5RTB Remote Test File Location: /sba/autorecRTB Partial File Location: /sba/autorec

Commit? [Save] {Save Edit Abort}:

14 If the displayed values are not correct, go to step 16.

15 If the displayed values are correct, go to step 17.

16 Edit and correct the displayed values:

edit

17 Save the information you entered:

save

18 Activate the schedule tuple for the stream by performing"Configuring the outbound file transfer schedule" in Nortel Coreand Billing Manager 850 Accounting ( (NN10363-811)) .

19 To add RTB to another billing stream, go to step 10.

20 If you do not want to add RTB to another billing stream, go tostep 37.

21 Before performing this step, ensure the RTB schedule tuple isin the OFFL state.

Change the RTB configuration for a billing stream:

change <stream_name> <file_format> <destination>

22

ATTENTIONIf auto recovery is turned on, do not configure multiple RTBdestinations with the same Test File Location or Partial File Locationon the DPMS.


NN10450-900 06.023 October 2008


.

Procedure steps 79

Enter the desired maximum retry attempts before RTB raises acritical alarm, and press the Enter key.

The default value is 3.

23 Enter the directory on the DPMS where the RTB test file resides,and press the Enter key.


24 Enter the directory on the DPMS where the RTB remote partialfile resides, and press the Enter key.


Example response:

You entered:RTB Max Consecutive Failures: 5RTB Remote Test File Location: /sba/autorecRTB Partial File Location: /sba/autorec

Commit? [Save] {Save Edit Abort}:

25 If the displayed values are not correct, go to step 27.

26 If the displayed values are correct, go to step 28.

27 Edit and correct the displayed values:

edit

28 Save the information you entered:

save

29 Activate the schedule tuple for the stream by performing"Configuring the outbound file transfer schedule" in Nortel Coreand Billing Manager 850 Accounting ( (NN10363-811)) .

30 To change the RTB configuration on another billing stream, goto step 21.

31 If you do not want to change the RTB configuration on anotherbilling stream, go to step 37.

32 Deactivate the schedule tuple for the stream by performing"Configuring the outbound file transfer schedule" in Nortel Coreand Billing Manager 850 Accounting ( (NN10363-811)) .

33 Before performing this step, ensure the RTB schedule tuple isin the OFFL state.

Delete the RTB configuration from a billing stream:

delete <stream_name> <file_format> <destination>

34 Confirm the delete command:

y


NN10450-900 06.023 October 2008


.


35 To delete RTB from another billing stream, go to step 33.

36 Quit the BILLMTC interface:

quit all

--End--


<stream_name> Specifies the name of the configuredbilling stream

<file_format> Specifies the file format of theconfigured billing stream

<destination> Specifies the billing file transferdestination


NN10450-900 06.023 October 2008


.

SBRM core access configuration procedures 81

SBRM core access

This chapter shows a task flow and the procedures required to configureaccess to the core for the Synchronous Backup Restore Manager (SBRM).

SBRM core access configuration proceduresThis task flow shows you the sequence of procedures you perform toconfigure core access for the Synchronous Backup Restore Manager(SBRM). To link to any procedure, click on the procedure in the navigationlist.

Figure 11SBRM core access configuration procedures


NN10450-900 06.023 October 2008


.


Configuration of SBRM core access navigation

• “Configuring the bkmgrusr user ID and password to enablecommunication between the DBRM and SBRM” (page 82)


Configuring the bkmgrusr user ID and password to enablecommunication between the DBRM and SBRM

Use this procedure to configure the bkmgrusr user ID and passwordin order for the Synchronous Backup Restore Manager (SBRM) tocommunicate with the Device Backup Restore Manager (DBRM) on theCommunication Server 2000 Core Manager.

This procedure applies only to the Communication Server 2000 CoreManager running on an AIX platform. The procedure does not apply to theCore and Billing Manager (CBM) running on an SPFS-based server.

Prerequisites

• You must be a user authorized to perform config-admin actions.

• For information on how to log on to the Communication Server 2000Core Manager and how to display actions a user is authorized toperform, see Logging in to the CS 2000 Core Manager and Displayingactions a user is authorized to perform in Nortel CS 2000 CoreManager Administration and Security ( (NN10170-611)) .

Procedure steps

Step Action

1 At your workstation, log onto the Communication Server 2000Core Manager on which the DBRM is installed as a userauthorized to perform config-admin actions.

2 Create the bkmgrusr user, typemkuser bkmgrusr

3 Create these groups: emsmtc, emsadm, and emsrw, typemkgroup emsmtcmkgroup emsadmmkgroup emsrw

4 Add the bkmgrusr user to the primary group (maint) and tosecondary groups, type (on one single line)chuser pgrp=maint groups=emsmtc,emsadm,emsrw


NN10450-900 06.023 October 2008


.

Configuring the bkmgrusr user ID and password to enable communication between the DBRM andSBRM 83

home=/export/home/bkmgrusr admin=trueshell=/bin/ksh bkmgrusr

When you type this command, make sure that you typed a spacebetween emsrw and home, and between ksh and bkmgrusr.

5 Confirm that the bkmgrusr user was added to the requiredgroups, typegroups bkmgrusr

The system displays the groups to which bkmgrusr user belongs.

6 Set the password for the bkmgrusr user, typepasswd bkmgrusr

The bkmgrusr user is disabled until this step is performed.

7 Log off from the Communication Server 2000 Core Manager.

8 Log on to Communication Server 2000 Core Manager as thebkmgrusr.

When prompted, change the password for the bkmgrusr user.

9 Change to the home directory and create the .ssh directory, typecd /export/home/bkmgrusrmkdir .sshchmod 700 .ssh

--End--


NN10450-900 06.023 October 2008


.


Configuring core access for SBRM through theNortel Communication Server 2000 Core Manager

Use this procedure to configure access to the core for the SynchronousBackup Restore Manager (SBRM). You must perform this procedure toenable the SBRM to automatically backup a core image.

Perform this procedure every time that core user password expires orchanges. This ensures that the password you set in this procedurematches that set for the user on the core.

Prerequisites• Perform “Configuring the bkmgrusr user ID and password to enable

communication between the DBRM and SBRM” (page 82) before youperform this procedure for the first time.

• You must be a user authorized to perform config-admin actions.

• You must know the user name and password that were configured toenable core access in “Configuring the bkmgrusr user ID and passwordto enable communication between the DBRM and SBRM” (page 82).

• For information on how to log on to the Communication Server 2000Core Manager and how to display actions a user is authorized toperform, see Logging in to the CS 2000 Core Manager and Displayinginformation about a user or role group in Nortel CS 2000 CoreManager Administration and Security ( (NN10170-611)) .

Procedure steps

Step Action

1 At the Nortel Communication Server 2000 Core Manager, logonto the core manager with the logon ID and password for a userauthorized to perform config-admin actions.

2 If you want to perform this procedure through the commandline, at the command line prompt, change the directory to thedirectory containing appropriate configuration script, typecd /opt/nortel/bkresmgr/cbm/scriptssee

If you want to perform this procedure through SDMMTC (SDMmaintenance interface), run the configuration script, type./bkmgr_config.shthen go to step 5.

3 Access the config level of the SDM maintenance interface, type# sdmmtc config


NN10450-900 06.023 October 2008


.

Procedure steps 85

4 From the list of filesets, select the Succession ProvisioningData Sync Manager fileset (Backup Restore Manager fileset,SDM_BKM.bkm), and typeconfig

5 As the configuration script runs, you are prompted for the username.

Type the user name enabled to access the core in “Configuringthe bkmgrusr user ID and password to enable communicationbetween the DBRM and SBRM” (page 82).

6 You are prompted for the password. Type the password that wasset up through the procedure, “Configuring the bkmgrusr userID and password to enable communication between the DBRMand SBRM” (page 82).

7 You are prompted for the logical volume where the backup is tobe stored.

This is the device on which the core image dump will be stored.make sure that this device has sufficient space for the backupfile.

8 You are prompted for the core type, xa-Core or Compact. Thesoftware uses this information to determine if the core will havea message switch load.

--End--


NN10450-900 06.023 October 2008


.


Creating the backup user ID on the core for SBRM

Use this procedure to create the user ID on the core to enable theoperation of the Synchronous Backup Restore Manager (SBRM).

The types of operations this user are can performed are:

• set dump_restore_in_progress field in ofcstd table

• start image dump

• ability to run itocci command set

Perform this procedure before you perform “Configuring core access forSBRM through the Nortel Communication Server 2000 Core Manager”(page 84).

Procedure steps

Step Action

1 At the CI prompt on the core, typepermit <backupuser> <backupuser_pswd> 4 10000english all

2 If Enhanced Password Control is in effect on the CM and afterthe user is permitted on the switch, log onto the core manuallywith this user first. The core will prompt you to change thepassword at the first logon after the logon is permitted. Changethe password and then perform the procedure, “Configuring coreaccess for SBRM through the Nortel Communication Server2000 Core Manager” (page 84) using the <backupuser> user youhave created and the changed password.

If Enhanced Password Control is in effect on the CM, thepassword must be at least six characters in length.

The SBRM does not have the ability to manage passwords.Therefore, you must re-run the configuration script in“Configuring core access for SBRM through the NortelCommunication Server 2000 Core Manager” (page 84) to ensurethe password for the <backupuser> user.

--End--


<all> The privilege setting.


NN10450-900 06.023 October 2008


.


Variable Value

<backupuser> The user name that will be used bySBRM to log on to the core.

Maximum length is 16 characters.

<backupuser_pswd> The password for the <backupuser>user you are creating.

Maximum length is 16 characters.

<english> The language setting.

<4> The priority.

<10000> The stack size.


NN10450-900 06.023 October 2008


.


Applying software packages on a Core and BillingManager using the CBMMTC interface

Use this procedure to install optional software packages on CBM clusternodes.

Procedure stepsATTENTIONInstructions for entering commands in this procedure do not show the promptingsymbol, such as #, >, or $, displayed by the system through a GUI or on acommand line.

At your workstation

Step Action

1 In the command line prompt, enter cbmmtc apply to access theapply level of the cbm maintenance interface

The system displays the apply level screen of the cbmmaintenance interface, which shows a list of the packages (up to12 software packages are displayed at a time), if any exist, in thedefault source directory.

2 To exit the CBM maintenance interface, type no and go to step13.

3 If the CBM software is on a CD-ROM, insert the CD-ROM intothe CD drive if it is not already present in the drive.

4 At the command line located at the bottom of the cbmmtc userinterface screen, type:

source <source_directory_name>

Use /cdrom/cdrom/applications/cbm/packages as the<source_directory_name> if the software is on a CD-ROM.

The system displays the apply level screen of the cbmmaintenance interface, which shows a list of all packages in thesource directory that you specified.

5 Locate the packages to be applied from the displayed list andtake note of their numbers (located next to the names of thepackages). Select the packages that you have decided to apply:

select <package number> ... <package number>

The packages you selected are highlighted on the cbmmtc applyscreen.

6 To apply the selected packages:

apply


NN10450-900 06.023 October 2008


.


7 If there is a prerequisite package for the package(s) youhave selected to apply on the system, the system SWIM toolautomatically selects and applies the prerequisite packageunless the package is currently selected to be applied.

The system prompts if you want to continue with applying theselected packages.

8 If you do not want to continue the package application, type noand go to step 13.

9 Type yes in response to the prompt.

The status of each package application appears on the cbmmtcapply screen.

10 When the application is completed, the installed packages willappear in the list that displays when you enter the cbmmtcpackages level. Verify that the status of the new packagesindicates Applied under the Status column.

ATTENTIONIt is important that packages installed on the system not be leftwith a Partial status. If any package installed application fails orotherwise shows a Partial status, contact your next level of supportfor assistance.

11 Go to step 13.

12 Type no in response to the prompt.

13 Exit from the cbm maintenance interface:

quit all


--End--


<source_directory_name> The full pathname of the directory containing thepackage that you want to apply. Because youare using a CD-ROM for the installation, specify/cdrom/cdrom/applications/cbm/packages as thesource_directory_name

<package number> The number associated with a package, thatyou noted. Each package number is separatedby preceding and succeeding spaces.


NN10450-900 06.023 October 2008


.


Job aidExample

To select the Reach Through SPM application, which is number 6, andOM Delivery, which is number 11 in the sample screen display shown inthe previous figure, enter

select 6 11

To de-select any packages that you selected, re-enter the selectcommand for the packages you want to de-select. The highlighting on thepackages that you de-select will be removed.


NN10450-900 06.023 October 2008


.

Procedure steps 91

Cloning the image of the active node to the inactivenode

Use this procedure to clone an active node image onto the inactive node ofa CBM cluster.


At your workstation

Step Action

1 Start the cloning process by typing

startb

and press the Enter key.

2 If the system prompts you for the Ethernet address, go to step 4.

3 If the system indicates it is using Ethernet address<EthernetAddress>, record the IP address and go to step 9.

4 At the console connected to the inactive node, log on to theinactive node through the console using the root user ID andpassword.

5 If the system is not already at the OK prompt, bring the systemto the OK prompt:

init 0

6 At the OK prompt, display the Ethernet address of the inactivenode:

OK banner

Example response:

Sun Fire V240, No keyboardCopyright 1998-2002 Sun Microsystems, Inc. Allrights reserved. OpenBoot 4.8.0.build_04, 2048 MBmemory installed, Serial #52964131. Ethernet address0:3:ba:28:2b:23, Host ID: 83282b23.

7 Record the Ethernet address that is displayed.

8 At your workstation (session connected to Active node), enter theEthernet address of the inactive node you recorded in step 6.


NN10450-900 06.023 October 2008


.


9 If the system prompts you to enter the command: boot net -image, go to step 11.

10 If the system does not prompt you to enter the command: bootnet - image, to step 12.

11 At the console connected to the inactive node, boot the inactivenode from the image of the active node by typing:

OK boot net - image


ATTENTIONThere must be a space after the dash.

Example response:

SC Alert: Host System has ResetSun Fire V240, No KeyboardCopyright 1998-2002 Sun Microsystems, Inc. Allrights reserved. OpenBoot 4.8.0.build_04, 2048 MBmemory installed, Serial #52964131. Ethernet address0:3:ba:28:2b:23, Host ID: 83282b23.

Rebooting with command: boot net - image...SC Alert: Host System has Reset

12 At your workstation (session connected to the Active node),monitor the progress of the cloning from the active node. Cloningthe inactive node takes approximately one hour to complete.

Example response:


NN10450-900 06.023 October 2008


.

Procedure steps 93

Waiting for network response fromunit1-priv0...received network response from unit1-priv0...Waiting for unit1-priv0 to clone data...waiting...1waiting...2waiting...3unit1-priv0 is cloning: /export/d2...Verifying cluster status of unit1-priv0waiting for cluster filesystem status to become normal.Deleted snapshot 0.Deleted snapshot 1.Deleted snapshot 2.Deleted snapshot 3.d99: Soft Partition is cleared

--End--


NN10450-900 06.023 October 2008


.


Installing the Backup Restore Manager software

Use this procedure to install the Backup Restore Manager software. TheBackup Restore Manager application functionality requires the appropriatesoftware resident and configured on platforms that require synchronizedimaging. Although no Core and Billing Manager 850 data is backed upthrough the Backup Restore Manager, the Backup Restore Managersoftware must be installed on the CBM to allow control of the XA-core and3PC (Compact) backup.


Step Action

1 At the CI prompt on the core, enter the following command:

permit <backupuser> <backupuser_pswd> 4 10000 englishall

ATTENTIONIf Enhanced Password Control is in effect on the CM, the passwordmust be at least six characters in length.

ATTENTIONIf Enhanced Password Control is in effect on the CM and after theuser is permitted on the switch, log in to the core manually with thisuser first. The core will prompt you to change the password at thefirst logon after the logon is permitted. Change the password andthen perform step 1.

The SBRM does not have the ability to manage passwords.Therefore, you must rerun the configuration script in step 4.

2 At your workstation, apply the software application package,NTbkupmgr . Specify /cdrom/cdrom/applications/cbm/packagesas the source directory when you perform that procedure.

3 When the installation is complete, exit from the cbmmtc.

4 At the command line prompt, change directory to the directorycontaining configuration script:

cd /opt/nortel/bkresmgr/cbm/scripts

5 Run the configuration script:

./bkmgr_config.sh


NN10450-900 06.023 October 2008


.


6 You are first prompted for the user name. The user name is thatused to log in to the core to initiate an image dump. The scriptrestricts the user name to a maximum of 16 characters. The username entered must first be enabled on the core in step 1

7 You are prompted for the user name you entered in step 6.

8 You are first prompted for the password. The configuration scriptrestricts the password to a maximum of 16 characters. Use thepassword set up in step 1

9 You are prompted for the logical volume where the backup is tobe stored. This is the device on which the core image dump willbe stored.

ATTENTIONVerify that this device has enough space to store the backup.

10 You are prompted for the core type, either XA-core or Compact.

ATTENTIONThis information is needed in order for the software to know whetherthe core will also have a Message Switch load.

--End--


<backupuser> The user name for the core, that is up to 16characters in length, that will be used by SBRMfor logon

<backupuser_pswd> The password for the <backupuser> user youare creating, which can be up to 16 charactersin length 4 is the priority


NN10450-900 06.023 October 2008


.


Configuring SSH between the backup restoremanager servers

Configure Secure Shell (SSH) between the backup restore managerservers to set up SSH between the Integrated Element Managementsystem (IEMS) server where the synchronous backup restore manager(SBRM) software and the SPFS-based servers where the device backuprestore manager (DBRM) software is installed.

Throughout the remainder of this procedure, the IEMS server will bereferred to as the SBRM server and the SPFS-based servers will bereferred to as the DBRM servers.

SSH provides authentication and secure communications over insecurechannels.

This procedure contains the steps to generate the SSH key pair on theSBRM server and transfer the key pair to each DBRM server and the SDMplatform in the network. It also contains the steps to transfer an existingSSH key pair from the SBRM server to new or existing DBRM servers andthe SDM platform in the network.

Prerequisites• You need the root user ID and password for the SBRM server.

• You need the password for the bkmgrusr on the DBRM servers totransfer the SSH key pair.

The bkmgrusr is created on the DBRM server when SPFS is installed.

• You need the root password for the DBRM server when the DBRMserver is a two-server configuration, to synchronize the SSH databetween the two servers.

ATTENTIONEnsure provisioning activities must not be in progress or scheduled to take placeduring this procedure.


Step Action

1 Log in to the SBRM server

> telnet <server>.


NN10450-900 06.023 October 2008


.

Procedure steps 97

In a two-server configuration, log in to the Active side using itsphysical IP address.

2 When prompted, enter your user ID and password.

3 Change to the root user

$ su -

4 When prompted, enter the root password.

5 Change directory to the location of the backup restore managerconfiguration script

# cd /opt/bkresmgr/admin/bin

6 Run the backup restore manager configuration script

# ./configure

For an example, see “Job aid” (page 99).

7 Enter the number next to the ‘Backup Restore Manager SSHsetup’ option in the menu.


8 If you are configuring SSH for the first time, or changing the SSHkey pair then, go to 10.

9 If you are transferring an existing SSH key to Device BackupRestore Manager servers then, go to 27.

10 Enter the number next to the ‘Generate SSH key and transfer toDevice Backup Restore Manager servers’ option in the menu.


11 When prompted, confirm you want to continue by typing:

y


12 When prompted, press Enter to accept the default location andfilename ‘/export/home/bkmgrusr/.ssh/id_rsa’ for the key.

If the default location and filename is not provided, enter/export/home/bkmgrusr/.ssh/id_rsa.

If the location and filename ‘/export/home/bkmgrusr/ .ssh/id_rsa’already exists and you wish to overwrite, enter y. Otherwise,enter n.


13 When prompted, enter y to confirm you want to transfer the SSHkey pair.


14 When prompted, enter the hostname or IP address of a DBRMserver in your network.


NN10450-900 06.023 October 2008


.



15 When prompted, enter the number next to the platform type ofthe DBRM server.

The SPFS platform type is for servers hosting the CS 2000Management Tools, MG 9000 Manager and Core and BillingManager (CBM). The SDM platform type is an AIX platformcontaining core management software.


16 When prompted, enter yes to confirm you want to continueconnecting.

Warning: Permanently added ’comp5iems (45.123.456.98)’(RSA) to the list of known hosts.

Password:

17 When prompted, enter the password for the bkmgrusr on theDBRM server.


18 When prompted, enter y if the DBRM server is a two-serverconfiguration (HA), otherwise, enter n.

19 If you have entered y (yes) then go to 21.

20 If you have entered n (no) then go to 25.

21 When prompted, enter y if you want to manually synchronize theSSH data, otherwise, enter n.

ATTENTIONThe DBRM server root user password is required to complete thissection.

22 If you have entered y (yes) then go to step 24.

23 If you have entered n (no) then go to step 25.

24 When prompted, enter the root password for the DBRM server.


25 When prompted, indicate that you want to transfer the SSHkey pair to the DBRM installation on the SBRM server in yournetwork.

The SBRM always makes a SSH connection to the DBRMresiding on the local server so that the local IEMS application isnotified of the synchronized backup by way of SBRM to DBRMmessaging.

26 Enter the number next to the "Transfer existing SSH key toDevice Backup Restore Manager servers" option in the menu.

For example, see “Job aid” (page 99).


NN10450-900 06.023 October 2008


.

Job aid 99

27 When prompted, confirm you want to transfer the SSH key pairby typing:

y

This returns you to step 14.


28 Enter x to exit the ‘Backup Restore Manager SSH setup’ levelby typing:

29 Enter x to exit the ‘Backup Restore Manager Configuration’ level.

--End--


<server> IP address or host name of the IEMS serverwhere the SBRM software is installed.

Job aidTable 12Example responses to procedure steps

Step Example response

6 Backup Restore Manager Configuration1 - Backup Restore Manager SSH Setup2 - Automated Synchronous Backup RestoreManager ServiceX - exitselect - [X, 1-2]

7 SSH Setup for Synchronous Backup Restore Manager1 - Generate SSH key and transfer to DeviceBackup Restore Manager servers2 - Transfer existing SSH key to DeviceBackup Restore Manager serversX - exitselect - [X, 1-2]

10 Generate SSH key for Synchronous Backup Restore Manager and transferto Device Backup Restore Manager servers.WARNING: Running this script will generate a new SSH key for thebkmgrusr.This new SSH key must be transferred to all existing and new DeviceBackup Restore Manager servers.Do you want to continue? [y/n]:


NN10450-900 06.023 October 2008


.



11 Generating SSH key for bkmgrusr.Sun Microsystems Inc. SunOS 5.9 GenericMay 2002Generating public/private rsa key pair.Enter file in which to save the key(/export/home/bkmgrusr/.ssh/id_rsa):

12 Your identification has been saved in /export/home/bkmgrusr/.ssh/id_rsa.Your public key has been saved in /export/home/bkmgrusr/.ssh/id_rsa.pub.The key fingerprint is:33:99:17:f0:ac:2a:3a:86:a9:d9:76:65:e6:70:4b:6:8 bkmgrusr@comp5iemsSynchronizing files IF clustered nodeTransfer existing SSH key to Device Backup Restore Manager serversWARNING: You must have the password for the bkmgrusr on the DeviceBackup Restore Manager server to transfer the SSH key.Do you want to transfer the SSH key? [y/n]:

13 Setting up to transfer SSH key to DBRM server.Enter hostname or IP address of DBRM server to transfer the SSH keyto:

14 Platform type of DBRM server to transfer SSH key to:1 - SPFS2 - SDMEnter platform type of DBRM server to transfer SSH key to [1-2]:

15 Sun Microsystems Inc. SunOS 5.9 GenericMay 2002The authenticity of host ’comp5iems (45.123.456.98)’ can’t beestablished.RSA key fingerprint isff:eb:a8:87:14:d0:82:28:5c:43:70:5a:ab:af:e6:fdAre you sure you want to continue connecting (yes/no)?:

17 Transfer of SSH key to <server> complete.Is DBRM <server> a High Availability (HA) server? [y/n]:

22 WARNING: On HA DBRM servers, SSH setup is notcomplete unless one of the following steps isperformed.a) The HA DBRM server <servername> is cloned.b) The SSH data on HA DBRM <servername> ismanually synched.WARNING: Choosing this option requires theroot password for <servername>Do you want to manually synchronize the SSH data on DBRM <servername>now [y/n]

25 Synchronization of SSH data on DBRM <servername> complete.


NN10450-900 06.023 October 2008


.

Job aid 101


27 Transfer existing SSH key to Device Backup Restore Manager serversWARNING: You must have the password for the bkmgrusr on the DeviceBackup Restore Manager server to transfer the SSH key.Do you want to transfer the SSH key? [y/n]:

28 Setting up to transfer SSH key to DBRM server.Enter hostname or IP address of DBRM server to transfer the SSH keyto:


NN10450-900 06.023 October 2008


.


Configuring SBA backup volumes on the core

Configure backup volumes on IOP, 3PC, DDU, or SLM disks on the corefor a billing stream.

The maximum number of volumes that you can configure for a billingstream is 69, or the maximum number supported by the underlyinghardware, whichever is less per stream.

The Table 13 "Disk drive backup volumes" (page 105) lists the disk drivebackup volumes that you can configure for the BRISC and XA-coreplatforms.

Prerequisites• You must configure additional backup storage to prevent a temporary

problem that forces the SBA into long-term backup mode.

The billing stream is aware that the replaced volumes exist, andrecovers files from both the swapped-out and swapped-in sets ofvolumes as part of the recovery process.

The billing stream loses track of swapped-out volumes when aswitch of activity (SwAct) or a restart is performed on the DMS orCommunication Server 2000 prior to the completion of the recoveryof the files.

• There is a risk of losing some billing records when you reconfigure orswap-out backup volumes of a stream that is in backup mode duringthe transition process.

• During an emergency situation (outage), you must allow time for therecovery process to finish before you attempt to swap out an activebackup volume. If you do not allow time for the recovery process tofinish, the billing stream does not recognize the swapped-out volumes.

If you are using or migrating to a XAC16 system, your backup volumesmust be on IOP volumes. If your current backup volumes are on SLMor DDU volumes and you are running a previous release, you mustmigrate to IOP volumes before upgrading to this release.

ATTENTIONEnsure the size for backup volumes is sufficient. The absolute minimum sizefor backup volumes is 30MB.


NN10450-900 06.023 October 2008


.

Procedure steps 103

Procedure steps

Step Action

1 At your system, write down the dms_disk_space value recordedin Table 20 "Disk space requirements" (page 208) (answer 31),which shows the amount of disk space required for the backupvolumes.

2 Determine the amount of disk space of each disk type in yoursystem to be used for storing the backup volumes. Divide thevalue recorded in step 1 by the maximum volume size supportedfor the appropriate disk types for your system, obtained fromthe table Table 14 "Metrics on various disk types " (page 106).Record these values.

3 Ensure that the backup volumes can fit on the disks in yoursystem. Compare the values recorded in step 2 with themaximum number of volumes supported for the disk types inyour system, obtained from the table in the previous step.

If the number of volumes obtained in the previous step is lessthan or equal to the maximum number allowed, go to step 4.

OR

If the number of volumes obtained in the previous step is greaterthan the maximum number allowed, contact the next level ofsupport.

4 Post the billing stream by typing:

mapci;mtc;appl;sdmbil;post <stream_name>

5 Obtain information about the existing backup volumes for thebilling stream :

conf view <stream_name>

SBA does not support the configuration of more than one billingstream at a time from multiple workstations. The last billingstream that is configured is the one that is saved.

The system displays the name of each backup volume in thestream. Record each backup volume name for future reference.

6 Quit out of the MAPCI level :

quit all

7 Display and record the size of a volume and its number of freeblocks:

diskut;lv <volume name>

8 Repeat the previous step for each volume name that yourecorded in step 2.


NN10450-900 06.023 October 2008


.


9 If you are configuring an IOP disk drive backup volume,create an alphanumeric name, consisting of a maximum oftwelve characters, for each of the new backup volumes thatyou determined in “Calculation of core manager Disk SpaceRequirements” (page 209). Record each of these names forfuture reference.

IOP volume names on the IOP disks can be up to twelvealphanumeric characters in length, with the first four charactersreserved for the disk prefix.

OR

Create a twelve-character, alphanumeric name for each of thenew backup volumes. Record each of these names for futurereference.

3PC volume names on the 3PC disks can be up to twelvealphanumeric characters in length, with the first four charactersreserved for the disk prefix.

ATTENTIONLogical volumes must be configured evenly across the disks.

10 Access the disk administration level:

diskadm <disk prefix>

11 Determine the free disk space:

dd

12 Note the following example, which is a response to the commandperformed in step 8, choosing the F02L disk name.

13 Determine the size of the largest free segment.

If the size of the largest free segment is greater than or equal tothe maximum allowable volume size for the disk type, go to thenext step.

OR

If the size of the largest free segment is less than the maximumallowable volume size for the disk type contact your next level ofsupport before proceeding with this procedure.


NN10450-900 06.023 October 2008


.

Job aid 105

14 Create a new logical volume :

cv <volume> <size> ftfs For an example to create a newlogical volume, see "Example" (page 106) .

15 Exit the disk administration level at the prompt by typing:

quit

16 Repeat this procedure until all new logical volumes have beencreated.

17 Exit to the command prompt:

quit all

18 Exit back to the command prompt :

quit all

You must alert all operating company personnel who areassociated with the system. Provide the names of the old andnew backup volumes and the procedure you used to swap thevolumes. They must be made aware of that any RESTARTs orSwActs that occur before the billing stream returns to normalmode can cause a loss of billing records.

Also, it is imperative that the mode of the billing stream mustbe closely monitored to ensure that it returns to normal modewithout an intervening RESTART or SwAct.

--End--


<disk prefix> One of the prefixes assigned to the two disks; for example, F02Lor F17D.

<size> The size of the volume.

<stream_name> The name of the billing stream.

<volume> The backup volume name.

Job aidThe following table lists the backup volumes for the various platforms.

Table 13Disk drive backup volumes

Platform Backup volume(s)

BRISC DDU or SLM


NN10450-900 06.023 October 2008


.


Table 13Disk drive backup volumes (cont’d.)

Platform Backup volume(s)

XA-core (for releases prior to SDM16 or CS2E03) DDU or IOP

XA-core (for SDM16 or CS2E0 and higher) IOP

The following table provides metrics on various disk types that can beused in this procedure.

Table 14Metrics on various disk types

Disk type Maximumdisks percore

Maximumvolumes perdevice

Maximumvolumesconfigurablefor SBA

Maximumvolume size

IOP 2 32 64 2GB

3PC 2 32 64 2GB

DDU 10 32 69 64MB

SLM 2 32 64

The following example shows how the user can create a new logicalvolume.

Example

cv AMA8 50 ftfs

This entry prompts the system to create the logical volume F17LAMA8,consisting of 50 Mbyte (102400 512-byte blocks) of available disk space.


NN10450-900 06.023 October 2008


.

Procedure steps 107

Starting or stopping the automated synchronousbackup restore manager service

Use this procedure to start or stop the automated synchronous backuprestore manager (SBRM) service on the SPFS-based server where theSBRM software is installed.

Prerequisites• You need the root user ID and password for the SPFS-based server

where the SBRM software is installed.

ATTENTIONEnsure provisioning activities must not be in progress or scheduled to take placeduring this procedure.

Procedure steps

Step Action

1

ATTENTIONIn a two-server configuration, log in to the Active side using itsphysical IP address.

Log on to the SBRM server

> telnet <server>



$ su - root


5 Change directory to where the backup restore managerconfiguration script is located



# ./configure


7 Enter the number next to the ‘Automated Synchronous BackupRestore Manager Service’ option in the menu.



NN10450-900 06.023 October 2008


.


8 If you want to start the automated SBRM service then go to step10.

9 If you want to stop the automated SBRM service then go to step12.

10 To start the SBRM service enter the number next to the ‘Startthe Automated Synchronous Backup Restore Manager Service’option in the menu.


11 Enter y to confirm you want to start the SBRM service.

y

For an example, see “Job aid” (page 108). Go to step 14

12 To stop the SBRM service enter the number next to the ‘Stopthe Automated Synchronous Backup Restore Manager Service’option in the menu.


13 Enter y to confirm you want to stop the SBRM service.


14 Enter x to exit the ‘Automated Synchronous Backup RestoreManager Service’ level by typing

15 Enter x to exit the ‘Backup Restore Manager Configuration’ levelby typing

--End--


server IP address or host name of the IEMS serverwhere the SBRM software is installed.

Job aidStep Example response

6 Backup Restore Manager Configuration1 - Backup Restore Manager SSH Setup2 - Automated Synchronous Backup Restore Manager ServiceX - exitselect - [X, 1-2]


NN10450-900 06.023 October 2008


.

Job aid 109

7 Automated Synchronous Backup Restore Manager Service1 - Configure Automated Synchronous BackupRestore Manager Service2 - Start the Automated Synchronous BackupRestore Manager Service3 - Stop the Automated Synchronous BackupRestore Manager Service4 - View the Automated Synchronous BackupRestore Manager Service ConfigurationX - exitselect - [X, 1-4]

10 Start the Automated Synchronous Backup Restore Manager ServiceWARNING: Running this script will start the Automated SynchronousBackup Restore Manager ServiceStarting the service does not initiate a backup until the day andtime configured.Do you want to continue? - [y/n]:

11 Registering with SERVMAN.Starting the Automated Synchronous Backup Restore Manager Service.Starting AUTO_BACKUP_MANAGER through servstart AUTO_BACKUP_MANAGER Started

13 Stop the Automated Synchronous Backup Restore Manager ServiceWARNING: Running this script will stop the Automated SynchronousBackup Restore Manager ServiceStopping the service does not abort a backup in progress.Do you want to continue? - [y/n]:

14 Stopping the Automated Synchronous Backup Restore Manager Service.Stopping group using servstop AUTO_BACKUP_MANAGER StoppedDeregistering with SERVMAN


NN10450-900 06.023 October 2008


.


Invoking the network-level backup (SBRM-bkmgr)through telnet

Use this procedure to run a network backup (SBRM-bkmgr) on an IEMSserver using CLUI.

The network backup (SBRM-bkmgr) script is installed under the/bkresmgr/nbm directory. The bkmgr should be invoked from this directoryto control and synchronize the activities related to backup across othermanaged devices which contain device-level backup software.

Perform this procedure at your workstation.

PrerequisitesYou need the root user ID and password for the IEMS server.

Procedure steps

Step Action

1 Log in to the IEMS server by entering the following command:

> telnet <server>


3 Change to the root user by entering:

$ su -


5 Change the directory to where the network backup managerscript (SBRM-bkmgr) is located by entering:

#cd /opt/nortel/bkresmgr/nbm

6 Start the network backup manager by entering:

bkmgr> <command>

--End--


NN10450-900 06.023 October 2008


.

Example of invoking the network-level backup (SBRM-bkmgr) through telnet 111


<server> The IP address of the IEMS server.

<command> Any one of the following commands:

• backup abort

• backup auto

• backup full

• query history

• query inventory

• query status

• quit or exit

or any of the following commands to perform astep by step backup for debugging:

• activatenew

• dumpdata

• precheck

• startprov

• stopprov

• verify

Example of invoking the network-level backup (SBRM-bkmgr)through telnet

Example of invoking the network-level backup (SBRM-bkmgr) throughtelnet# cd /opt/bkresmgr/nbm# ./bkmgrbkmgr> backup fullBeginning step: precheckCompleted step: precheckBeginning step: stopprovCompleted step: stopprovBeginning step: dumpdataError during step: dumpdata*** Component wcars2yx ****** Component DB ***Failed to create backup files


NN10450-900 06.023 October 2008


.


bkmgr>bkmgr> query statusCurrent State: dumpdataProcess Status: idle

*** Component wcars2yx ***Step dumpdata for wcars2yx is failed.Current State: dumpdataProcess Status: idle

*** Component DB ***Step dumpdata for DB is failed.*** Component IS ***Step dumpdata for IS is complete.*** Component NPM ***Step dumpdata for NPM is complete.*** Component CEM ***Step dumpdata for CEM is complete.*** Component IEMS ***Step dumpdata for IEMS is complete.

bkmgr>bkmgr> query historyLast backup failed at Wed May 21 08:51:31 EDT 2008.*** Component wcars2yx ****** Component DB ***Failed to create backup filesbkmgr>

bkmgr> backup abortBeginning step: rollbackCompleted step: rollbackCleaning up subcomponents...bkmgr> query statusCurrent State: No backup in progress.Process Status: idle

bkmgr> query historyLast backup failed at Wed May 21 08:51:31 EDT 2008.*** Component wcars2yx ****** Component DB ***Failed to create backup filesbkmgr>


NN10450-900 06.023 October 2008


.

Procedure job aid 113

Example of invoking the network-level backup (SBRM-bkmgr) throughtelnetbkmgr> backup autoBeginning step: precheckCompleted step: precheckBeginning step: stopprovCompleted step: stopprovBeginning step: dumpdataError during step: dumpdataAuto backup failed.*** Component wcars2yx ****** Component DB ***Failed to create backup filesRestarting provisioning...Beginning step: rollbackCompleted step: rollbackbkmgr>bkmgr> query statusCurrent State: No backup in progress.Process Status: idlebkmgr>

Procedure job aidDuring a complete backup of all devices/components, the SBRM networkbackup manager performs the following steps:

• ‘precheck’: performs a precheck of all devices/components.

• ‘stopprov’: locks the provisioning session of all devices/components.

• ‘dumpdata’: performs a backup of all devices/components.

• ‘verify’: verifies the backup data of all devices/components.

• ‘startprov’: unlocks the provisioning sessions of all devices/components.

• ‘activatenew’: finalizes the backup data (move data to differentdirectory/volume, …) for all devices/components.

To perform a complete backup, you can use one of the following 2commands provided by the SBRM-bkmgr:

• ’backup full’: performs a complete backup of all devices/components. Ifa failure is encountered, the process stops at completion of the failedstep, and you will need to abort or perform manual actions to recoverfrom the failure.

• ’backup auto’: performs a complete backup of all devices/components.If a failure is encountered, the process restores the provisioningsession if it has been stopped.


NN10450-900 06.023 October 2008


.


To recover from a failure, use the ‘backup abort’ command.

• ’backup abort’: aborts a backup after completion of the current step.The provisioning session will be unlocked if it has been locked by thebackup process.

To perform a query, you can use one of the following three commands:

• ‘query status’: displays the status of the backup at a high level.

• ‘query history’: displays information about the most recent backup.

• ‘query inventory’: displays the components/devices available forbackup.


NN10450-900 06.023 October 2008


.

Procedure steps 115

Invoking the device-level backup (DBRM-bkmgr)through telnet

Use this procedure to run device-level backup on an SPFS-based server.

The device-level backup (DBRM-bkmgr) is installed under/opt/bkresmgr/cbm directory. It is not recommended to run the DBRMdirectly from a CLUI interface, it should be controlled by the DBRM-bkmgr.In rare instances, it may be necessary to run various portions of thebackup process on the device directly.

Perform this procedure at your workstation.

PrerequisitesYou need the root user ID and password for the SPFS-based server.

Procedure steps

Step Action

1 Log in to the SPFS-based server by entering:

> telnet <server>


3 Change to the root user by entering:

$ su -


5 Change the directory to where device-level backup managerscript (DBRM-bkmgr) is located by entering:

#cd /opt/nortel/bkresmgr/cbm

6 Start the backup manager by entering:

bkmgr> <command>

--End--


NN10450-900 06.023 October 2008


.



<server> The IP address of the server.

<command> Any one of the following commands:

• backup abort

• backup auto

• backup full

• query history

• query inventory

• query status

• quit or exit

or any of the following commands to perform astep by step backup for debugging:

• activatenew

• dumpdata

• precheck

• startprov

• stopprov

• verify

Example of invoking the device-level backup (DBRM-bkmgr)through telnet

Example of invoking the device-level backup (DBRM-bkmgr) throughtelnetbkmgr> backup fullRC=fail~reason=*** Component DBFailed to create backup files

bkmgr> query historyRC=success~status=Last backup failed at Thu May 22 08:28:28EDT 2008.*** Component wcars2yx*** Component DBFailed to create backup filesbkmgr>

bkmgr> query statusRC=success~status= Current State: dumpdataProcess Status: idle


NN10450-900 06.023 October 2008


.

Procedure job aid 117

*** Component DB ***Step dumpdata for DB is failed.*** Component IS ***Step dumpdata for IS is complete.*** Component NPM ***Step dumpdata for NPM is complete.*** Component CEM ***Step dumpdata for CEM is complete.*** Component IEMS ***Step dumpdata for IEMS is complete.

bkmgr>

bkmgr> backup abortRC=successbkmgr> query statusRC=success~status= Current State: No backup in progress.Process Status: idlebkmgr>

Procedure job aidDuring a complete backup of all devices/components, the device-levelbackup manager performs the following steps:

• ‘precheck’: performs a precheck of all devices/components.

• ‘stopprov’: locks the provisioning session of all devices/components.

• ‘dumpdata’: performs a backup of all devices/components.

• ‘verify’: verifies the backup data of all devices/components.

• ‘startprov’: unlocks the provisioning sessions of all devices/components.

• ‘activatenew’: finalizes the backup data (move data to differentdirectory/volume, …) for all devices/components.

To perform a complete backup, you can use one of the following twocommands provided by the DBRM-bkmgr:

• ’backup full’: performs a complete backup of all devices/components. Ifa failure is encountered, the process stops at completion of the failedstep, and you will need to abort or perform manual actions to recoverfrom the failure.

• ’backup auto’: performs a complete backup of all devices/components.If a failure is encountered, the process restores the provisioningsession if it has been stopped.

To recover from a failure, use the ‘backup abort’ command.


NN10450-900 06.023 October 2008


.


• ’backup abort’: aborts a backup after completion of the current step.The provisioning session will be unlocked if it has been locked by thebackup process.

To perform a query, you can use one of the following three commands:

• ‘query status’: displays the status of the backup and shows the currentstate of the backup (that is, precheck, stopprov, dumpdata…).

• ‘query history’: displays information about the most recent backup.

• ‘query inventory’: displays the components available for backup.

It is recommended that you use the “query status” and “query history”commands to verify the backup result. You should use the “backup abort”command to unlock the provisioning session if the backup failed.


NN10450-900 06.023 October 2008


.

Procedure steps 119

Backing up an XA-Core office image from disk totape

Use this procedure to back up an eXtended Architecture Core (XA-Core)office image by copying the office image files from a disk to a digital audiotape (DAT) cartridge in an XA-Core shelf.

Perform this procedure each week or as indicated in the routinemaintenance schedule for your office.

Procedure steps

Step Action

1 Access the MAP CI level display

>QUIT ALL

2 Access the image table of contents (ITOC) user interfaceX

>ITOCCI


3

ATTENTIONThe example of a MAP response identifies the autoload registered(ALR) image file by an asterisk (*) in the ALR column. Each imagefile has an index number at the beginning of the tuple line. The ALRimage in the example of a MAP response has an index number of0. The XA-Core selects the ALR image file first to boot the switch. Ifthe ALR image file does not boot the switch then the XA-Core selectsthe next image file. The next image file is by sequence of the indexnumber from the top of the table.

To list the boot file for the XA-Core in ITOC

>LISTBOOTFILE XA


4 To list the boot file for the message switch (MS) in ITOC, type

>LISTBOOTFILE MS


5 Determine if the XA-Core and MS have image files that areautoload registered (ALR). The examples of a MAP response forsteps 3 and 4 in the Job aid identify the ALR image files by anasterisk (*) in the ALR column.

6 If the image files are ALR then, go to step 8.


NN10450-900 06.023 October 2008


.


7 If the image files are not ALR then, go to step 29.

8

ATTENTIONIn the example of a MAP response for step 3 in the Job aid, the nameof the office image file for XA-Core is IMG0517CY_CM. Image fileIMG0517CY_CM is ALR. Image file IMG0517CY_CM is in volumeF02LIMAGE.

ATTENTIONIn the example of a MAP response for step 4 in the Job aid, the nameof the office image file for the MS is IMG0517CY_MS. Image fileIMG0517CY_MS is ALR. Image file IMG0517CY_MS is in volumeF02LIMAGE.

Record the names of the office image files for XA-Core and MSthat are ALR. Also record the volume name that has these officeimage files. The ALR image file is the file that you copy to theXA-Core tape.

9 Quit the ITOCCI user interface

>QUIT

10 At the shelf;

WARNINGStatic electricity damageWear a wrist strap connected to the wrist-strapgrounding point of the frame supervisory panel (FSP)when you handle the tape and packlet. The use ofthe wrist strap protects the packlets against damagecaused by electrostatic discharge (ESD).

Determine from office records or office personnel if the DATtape drive is clean. See the XA-Core procedure ‘How toclean the XA-Core tape drive’ in the Nortel XA-Core Fault andPerformance Management ( (297-8991-510)) .

11 Get a tape cartridge that has the approval of Nortel. Determinethe tape planned for a backup of an office image. Determine thetape to use from the office records or from office personnel.

12 Make sure the tape write protection is at the position that permitsrecording (closed). The tape write protection is an entrance onone side of the tape that has a sliding door. The sliding door isopen for write protection and closed to allow a write to the tape.


NN10450-900 06.023 October 2008


.

Procedure steps 121

13 Insert the DAT tape cartridge into the XA-Core tape driveand close the drive door. The XA-Core tape drive is in theinput/output processor (IOP) card of the XA-Core shelf.

14

CAUTIONFile of tape lost when formattedIf the tape had files, the formatting of the tape losesthe files. Make sure the tape has no files that youroffice needs.

Access the MAP disk utility

>DISKUT

.


15 Load the tape into the MAP disk utility

>INSERTTAPE snnp TAPE WRITELABEL label_name


16 Confirm the command

>YES


17

ATTENTIONA volume can have more files listed by command LISTVOLS thanby command LISTFL in the MAP disk utility. The difference in thenumber of files between the commands is because of directory filesnot displayed by command LISTFL.

To list the files in the volume that contains the office image, enter

>LISTFL vol_name

.


18 Begin the disk to tape backup process. To create a backup copyof the XA-Core image file, type:

>BACKUP FILE file_name snnp TAPE

.


19 If the command is successful, got step 21.

20 If the command is not successful, go to step 29.


NN10450-900 06.023 October 2008


.


21 Create a backup copy of the MS image fileX

>BACKUP FILE file_name snnp TAPE


22 If the command is successful, go to step 24.

23 If the command is not successful, go to step 29.

24 Check the backup copies of the image files on the tapeX

>LISTFL snnp TAPE


25 Eject the tape from the MAP disk utility after the backupprocedure completes

>EJECTTAPE snnp TAPE


26 Exit the MAP disk utility and return to the MAP CI level

>QUIT


27 Remove the tape cartridge from the tape drive.

WARNINGStatic electricity damageWear a wrist strap connected to the wrist-strapgrounding point of the frame supervisory panel (FSP)when you handle the tape and packlet. The use ofthe wrist strap protects the packlets against damagecaused by electrostatic discharge (ESD).

Set the tape write protection to the position that does not permitrecording (open). The tape write protection is an entrance onone side of the tape that has a sliding door. The sliding door isopen for write protection and closed to allow a write to the tape.

28 Store the tape cartridge according to office procedure.

29 For additional help, contact the next level of support.

--End--


NN10450-900 06.023 October 2008


.

Job aid 123


<label_name> The alphanumeric name of the tape label thatrecords the data. The name can be up to 32characters long. If blank spaces are in thelabel name then enclose the label name withquotation marks.

<nn> The number of the slot position on the XA-Coreshelf for the IOP that has the tape device.

<p> The upper (U) or lower (L) packlet position ofthe IOP that has the tape device.

<s> The front (F) or rear (R) shelf position of theinput output processor (IOP) that has the tapedevice.

<vol_name> The name of the disk volume that contains theoffice image files.


2 ITOC User Interface is now active.ITOCCI:

3 Image table Of Contents for XA :A Registered Generic Device FileL Date Time NameR MM/DD/YYYY HH:MM:SS-- - -------------------- -------------- -----0 * 05/17/1999 19:26:29 F02LIMAGEIMG0517CY_CM

4 Image Table of Contents for MS :A Registered Generic Device FileL Date Time NameR MM/DD/YYYY HH:MM:SS-- - -------------------- -------------- -----0 * 05/17/1999 19:26:29 F02LIMAGEIMG0517CY_MS

14 Disk utility is now active.DISKUT:


NN10450-900 06.023 October 2008


.



15 >INSERTTAPE F02UTAPE WRITELABEL IMAGE_1

Example of a MAP response

***** WARNING *****Writing the label IMAGE_1 to tape volumeF02UTAPE on node CM will destroy all filesstored on this tape volume.Do you want to continue?Please confirm ("YES", "Y", "NO", or "N")

16 The INSERT operation may take up to 5 minutes to tension the tape.A tape is now available to user on unit 0, node CM.Name IMAGE_1 has been written to the tape label.

17 >LISTFL F02LIMAGE


File information for volume F02LIMAGE:{NOTE: 1 BLOCK = 512 BYTES }---------------------------------------FILE NAME O R I O O V FILE MAXNUM OF FILE LASTR E T P L L CODE RECRECORDS SIZE MODIFYG C O E D D LENIN IN DATEC N FILEBLOCKS----------------------------------------------IMG0517CY_MS I F Y 0 10207542 15360 990517IMG0517CY_CM I F Y 0 1020165180 329728 990517

18 FTFS file IMG0517CY_CM on disk volume F02LIMAGE on node CM backed upas file IMG0517CY_CM on tape device F02UTAPE on node CM.

21 FTFS file IMG0517CY_MS on disk volume F02LIMAGE on node CM backup upas file IMG0517CY_MS on tape device F02UTAPE on node CM.


NN10450-900 06.023 October 2008


.

Job aid 125


24 >LISTFL F02UTAPE


File information for tape volume F02UTAPE, nodeCM:{Note: 1 BLOCK = 512 BYTES}---------------------------------------------CREATE ORG FILE V FILE NUM OF REC FILE NAMEDATE TYPE CODE L SIZE IN RECORDS LEND BLOCKS IN FILE----------------------------------------------990520 IMAG 0 329070 165180 1020 IMG0517CY_CM990520 IMAG 0 15026 7542 1020 IMG0517CY_MS

25 The EJECT operation may take up to 5 minutes to position the tape tothe beginning.Rewind of tape F02UTAPE, unit 0, on node CM is completed.This tape device is not available to the user now.


NN10450-900 06.023 October 2008


.


Backing up Call Agent

Perform a Call Agent backup to make a backup of the call processingapplication. Images to be backed up are created either manually withthe DUMP command, or automatically scheduled with entries in tableIMAGEDEV and IMGSCHED.

The Call Agent uses two software loads. The first software load includesthe platform software such as the operating system and system utilities.The second software load provides the call processing application.

Procedure steps

Step Action

1 At the map, list the available images. The image with theasterisk in the ALR column identifies the image that is set to AutoLoad Record and is the image to backup.

2 At the Call Agent Manager, log on to the inactive Call Agent andchange directory to the location of the image.

cd /3PC/sd0x/imagex

3

ATTENTIONDo not modify files at this level. Any modification to files must becompleted through the MAP.

Open a file transfer protocol (FTP) session to the CommunicationServer 2000 Core Manager and transfer the file.


NN10450-900 06.023 October 2008


.


4 At the SDM, insert a DAT cassette.

5

ATTENTIONUse the rvf argument to append to the tape. After the backupcompletes, optionally verify the integrity of the backup by using tartvf /dev/rmt0 to view the contents of the tape.

At the Communication Server 2000 Core Manager, verify thatthe size of the transferred file is the same as in step 2 and copythe file to tape.

6 Use the rm command to erase the oldest image so the volumedoes not fill up.

--End--


</3PC> Prefixed in all cases.


NN10450-900 06.023 October 2008


.


Variable Value

<sd0x/> Taken from the first four characters in theGeneric Device name.

<imagex/> Taken from the remaining characters in theGeneric Device name.


NN10450-900 06.023 October 2008


.

Procedure steps 129

Backing up the SST

Use his procedure to perform a manual backup of the SST or to changethe backup time.

By default, the unit performs a backup of the database and critical filesevery day at 1:00 AM. see “Rescheduling backup time” (page 132) to alterthe schedule.

The contents of the backup are stored locally on each unit in the/data/bkresmgr/backup directory in tape archive (tar) format.

For more information, see "Performing a rollback of Session Server Trunkssoftware" in (NN10440-450).

Prerequisites• Suspend all SIP Gateway application provisioning activities during

the time of the database backup to ensure that an accurate andcomplete copy of the active unit database is created. Call processingis not affected and there is no enforcement in the database to preventprovisioning.

Procedure steps

Step Action

1 At the NCGL CLI or IEMS client, log on to the ACTIVE unit andchange to the root user.

2 Start the backup

/opt/apps/db_install/sd/bkup_ngss.sh

The following output is printed to the screen and the backup isrecorded to /data/bckresmgr/backup.


NN10450-900 06.023 October 2008


.


Figure 12bkup_ngss.sh response

The backup filename is located in /data/bkresmgr/backup andis identified by hostname, date, and time as indicated in thefollowing example:

Example Response:unit0.backupfile.2005-04-12_17-10.tgz


NN10450-900 06.023 October 2008


.

Procedure steps 131

3 For security purposes, ensure that a copy of the backup file istransferred to a secure location.

Use the scp command to make a secure copy of the backup fileto a secure, remote server on your network. This server shouldbe continuously available for cases where a restoration of theunit become necessary, such as during an upgrade rollback.

4 If security related files are being backed up, refer to “Backing upsecurity related files manually” (page 134).

5 Repeat this procedure on the second unit.

--End--


NN10450-900 06.023 October 2008


.


Rescheduling backup time

Each unit performs an automatic backup at 1:00 AM daily. Use thefollowing procedure to change the schedule.

Procedure stepsAt the NCGL CLI or IEMS client

Step Action

1 Log onto the unit and change to the root user.

2 Remove the existing backup schedule from the crontab

/opt/apps/db_install/sd/uninstallBkres.sh

3 Edit the backup schedule file

vi /opt/apps/db_install/sd/backup.cron

The file is opened for editing.

4 Modify the first five fields (indicated by "0 1 * * *" in the example).The fields are identified in order from left to right:

• minute -- the minute of the hour that the command will run,values are 0 to 59

• hour -- the hour of the day the command will run, values are0 to 23 with 0 being midnight

• day -- the day of the month the command will run, values are1 to 31, an asterisk indicates to run the command all days

• month -- the month of the year the command will run, valuesare 0 to 12, an asterisk indicates to run the command allmonths

• weekday -- the day of the week that the command will run,values are 0 to 6, with 0 being Sunday, an asterisk indicatesto run the command all weekdays

Do not modify the sixth field (/opt/.../bkup_ngss.sh).

When done, write and quit the file.

5 Install the new schedule in the crontab

/opt/apps/db_install/sd/installBkres.sh


NN10450-900 06.023 October 2008


.

Procedure steps 133

6 After the scheduled time, verify that a backup file is created inthe /data/bkresmgr/backup directory and that it is created atthe new time, not the previously scheduled time.

7 Repeat this procedure on the second unit.

--End--


NN10450-900 06.023 October 2008


.


Backing up security related files manually

The automatic backup does not backup the certificate.keystore or key files.This guards against loss or theft of the backup which would compromisethe key without the operating company personnel knowing about thebreach.

Copy the following files to a safe location:

• /opt/base/share/ssl/certificate.keystore

• /opt/base/share/ssl/gen_cert.txt

• /opt/base/share/ssl/server.crt

• /opt/base/share/ssl/server.key

• /opt/base/share/ssl/trusted.crt

• /opt/base/synch_local/common/etc/ssh/ssh_host_dsa_key

• /opt/base/synch_local/common/etc/ssh/ssh_host_key

• /opt/base/synch_local/common/etc/ssh/ssh_host_rsa_key

Procedure steps

Step Action

1 At the NCGL CLI or IEMS client, log on to either unit (usually theunit where the latest version of security certificates are stored),and change to root user.

2 Navigate to the /opt/base/share/ssl directory:

cd /opt/base/share/ssl

3 Create a new directory to store backup copies of the certificatefiles:

mkdir <SNxx_ddmmyyyy>

4 Copy the certificates to the newly created backup directory:

cp * <SNxx_ddmmyyyy>

ATTENTIONCompleting this step ensures that you have valid backup copies ofthe security certificates for restoring in case of an upgrade abort orrollback or for disaster recovery purposes.

5


NN10450-900 06.023 October 2008


.


ATTENTIONIf you want to make backup copies of the security certificates to aremote server then do ensure that the remote host that will store thesecurity related files is secure, that the host is unavailable to generalusers, and offers restricted access to personnel with security relatedresponsibilities.

Secure copy the files to the remote server:

cd <SNxx_ddmmyyyy>scp *<user>@<remote_server>:</path>

The files are copied to the remote server.

--End--


<SNxx_ddmmyyyy> is the name of the new directory based onthe currently installed release of the systemsoftware (for example SN08) and the currentdate in the format ddmmyyyy

<user> is a valid user ID on the remote server

<remote_server> is the IP address of the remote server

<path> is where the file will be located on the remoteserver


NN10450-900 06.023 October 2008


.


Saving the Ethernet Routing Switch 8600 bootconfiguration file

Use the Boot Monitor CLI to save the Ethernet Routing Switch 8600configuration file. You must have access to the Boot Monitor CLI througha direct connection to the switch or a Telnet connection. For moreinformation about accessing the Boot Monitor CLI, see ’Managing theEthernet Routing Switch 8000 Series Switch Using the Command LineInterface Release 3.2,’ 313194-*.

ATTENTIONYou must be directly connected to the switch to initiate a Boot Monitor session.You can connect using a Telnet connection only if the Boot Monitor CLI isalready active.

Procedure steps

Step Action

1

ATTENTIONTo save a file to the standby CPU, you must enable TFTP on thestandby CPU. To enable TFTP, enter flags tftpd true in the BootMonitor CLI or config bootconfig flags tftpd true in the Run-Time CLI.

At the Boot Monitor CLI, issue the save command

monitor# save <save_type> [file <value>] [verbose][standby <value>] [backup <value>]

--End--


backup <value> Saves the specified file name and identifies thefile as a backup file.Example

save config file ralph.cfg backup 2

file <value> A filename in one of the following formats:• [a.b.c.d]: <file>

• /pcmcia/<file>

• /flash/<file>


NN10450-900 06.023 October 2008


.


Variable Value

<save_type> Specifies what to save. Possible values for thisparameter are config, bootconfig, log, and trace.

standby <value> Saves the specified file name to the standbyCPU (currently not supported).

verbose Saves default and current configuration. If youomit this parameter, only parameters you havechanged are saved.


NN10450-900 06.023 October 2008


.


Configuring the automated synchronous backuprestore manager service

Use this procedure to configure the automated synchronous backuprestore manager (SBRM) service on the SPFS-based server where theSBRM software is installed, for automated execution of backups. Youcan configure the SBRM service to execute backups on a weekly or dailybasis.

Prerequisites• You need the root user ID and password for the SPFS-based server

where the SBRM software is installed.


Step Action

1 Log on to the SBRM server

> telnet <server>

In a two-server configuration, log in to the Active side using itsphysical IP address.



$ su -


5 Change to the directory where the backup restore managerconfiguration script is located



# ./configure


7 Enter the number next to the ‘Automated Synchronous BackupRestore Manager Service’ option in the menu.


8 Enter the number next to the ‘View the Automated SynchronousBackup Restore Manager Service Configuration’ option in themenu to view the configuration settings..


NN10450-900 06.023 October 2008


.



9 If you want to change the configuration settings of the SBRMservice then go to step 11.

10 If you do not want to change the configuration settings of theSBRM service then go to step 19.

11 To change the configuration settings, enter the number nextto the ‘Configure Automated Synchronous Backup RestoreManager Service’ option in the menu.


12 When prompted, enter the number next to daily or weekly.


13 If you select weekly then go to step 15.

14 If you select daily the go to step 16.

15 When prompted, enter the number next to the day of the weekon which you want the backup to execute, or press the Enter keyto accept the default value.

16 When prompted, enter the time of day at which you want thebackup to execute, or press the Enter key to accept the default.


17 If you want to start the automated SBRM service now, perform“Starting or stopping the automated synchronous backup restoremanager service” (page 107).

18 If you do not want to start the automated SBRM service nowthen go to step 11.

19 Enter x to exit the ‘Automated Synchronous Backup RestoreManager Service’ level.

20 Enter x to exit the ‘Backup Restore Manager Configuration’ level.

--End--


<server> IP address or host name of the IEMS serverwhere the SBRM software is installed.


NN10450-900 06.023 October 2008


.



6 Backup Restore Manager Configuration1 - Backup Restore Manager SSH Setup2 - Automated Synchronous Backup Restore Manager ServiceX - exitselect - [X, 1-2]

7 Automated Synchronous Backup Restore Manager Service1 - Configure Automated Synchronous Backup Restore Manager Service2 - Start the Automated Synchronous Backup Restore Manager Service3 - Stop the Automated Synchronous Backup Restore Manager Service4 - View the Automated Synchronous Backup Restore Manager ServiceConfigurationX - exitselect - [X, 1-4]

8 The Automated Synchronous Backup Restore Manager Service is notrunningAutomated Synchronous Backup Restore Manager Service ConfigurationSettingsBackup Enabled : NBackup Day : SUNDAYBackup Hour : 24

11 Automated Synchronous Backup Restore Manager Service ConfigurationConfiguring the Automated Synchronous Backup Restore Manager Servicedoes not START the service. Return to the previous menu and select’Start the Automated Synchronous Backup Restore Manager Service’ tostart the service.Do you want the backup to run 1.daily or 2.weekly [1/2] :

12 Example response if daily is selected:

Hour to run the Synchronous Backup Restore Manager based on 24 hourclock:Example 1 is 1 AM, 12 is noon, and 24 is midnight.This is the hour on the <DAY> the Synchronous Backup Restore Managerwill execute a full backup.Enter hour to run the Synchronous Backup Restore Manager (default:24)Example response if weekly is selected:

Day of the week to run the Synchronous Backup Restore Manager:This is day of the week the Synchronous Backup Restore Manager willexecute a full backup.1 - MONDAY2 - TUESDAY3 - WEDNESDAY4 - THURSDAY5 - FRIDAY


NN10450-900 06.023 October 2008


.

Job aid 141

6 - SATURDAY7 - SUNDAYEnter day of week to run the Synchronous Backup Restore Manager(default: SUNDAY):

16 Automated Synchronous Backup Restore Manager Service Configurationcomplete.Configuring the Automated Synchronous Backup Restore Manager Servicedoes not START the service. Return to the previous menu and select’Start the Automated Synchronous Backup Restore Manager Service’ tostart the service.


NN10450-900 06.023 October 2008


.


Configuring Automated INI file backup on a MediaServer 2000 node

Use this procedure to configure automated INI file backups from the IEMSGUI main window.

The automated INI file backup configuration settings apply to all nodes.Therefore, changing the settings on one node affects all nodes.

Refer to the NN10329-111 to log into the IEMS GUI.

Procedure steps

Step Action

1 Select Applications -> IEMS -> Network Elements (refer to thefigure below).

2 Select the Media Server 2000 series node.

3 Right click the Media Server 2000 series node and selectConfigure MS2000 Automated INI Backup from the pop-upmenu. The Automated INI File Backup Configuration pop-upmenu displays.


NN10450-900 06.023 October 2008


.

Job aid 143

4 Click on the Enable Automated INI file backup box.

The Middle portion of the pop-up window changes from gray toblack. If the Weekly radio button is selected, the days of theweek listed at the bottom of the screen are black as well.


NN10450-900 06.023 October 2008


.


5 Enter a start time for the backup.

6 Click the radio button for either daily or weekly automatedbackups.

7 If the weekly radio button is selected, click the boxes of theday(s) of the week for which you want the backup to occur.

8 Click on the OK button to complete the automatic INI backupconfiguration.

--End--


NN10450-900 06.023 October 2008


.

Job aid 145

Changing SNMP community string passwords

Use this procedure to change SNMP community string passwords for aMedia Server 2000 series node from the IEMS GUI main window. Bydefault, the read and read-write SNMP community strings are public andprivate, respectively. Enter these into the IEMS GUI when adding orchanging the community string passwords.

Refer to the NN10329-111 to log into the IEMS GUI.

Procedure steps

Step Action

1 Select Applications -> IEMS -> Network Elements (refer to thefigure below).

2 Select the Media Server 2000 series node icon.

3 Right click the Media Server 2000 series node icon and selectthe Config and Maintenance Tool from the pop-up menu.


NN10450-900 06.023 October 2008


.


4 Select the Password Management tab.

5 Select the SNMP tab from the Password Management screen.

6 Enter the passwords for the read or write community strings.

7 Click the Change Read String or Change Write String buttonto complete the password change.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 147

Backing up INI files for all nodes

Use this procedure to back up the INI files for all nodes.

This procedure pertains to both the Media Server 2010 and the MediaServer 2020. The sample screens in this procedure show a Media Server2010.

Prerequisites• You must be member of the succssn and emsadm groups.

Procedure steps

Step Action

1 At the Windows desktop interface

Open a Telnet connection to the CS 2000 Management Tool.

2 Log on with the appropriate user name.

3 Invoke the MS 2000 Series CLUI

/opt/nortel/NTsesm/bin/ms2000.sh

4 When prompted, enter the appropriate user name and password.

The Media Server 2000 Series CLUI Main Menu is displayed.

5 Enter the number for the Back up the INI files for all nodesmenu option.

Sample response

Backup of .ini for node 172.17.40.230 completed andcopied to SDMPress <enter> to continue

6 Press Enter.

The Media Server 2000 Series CLUI Main Menu appears.

7 Enter x to exit the menu.

8 Enterexit to end the Telnet session.

--End--


NN10450-900 06.023 October 2008


.


Displaying Media Server 2010 current nodeconfiguration

Use this procedure to display the current configuration of the Media Server2010 node.

Prerequisites• You must be member of the succssn and emsadm groups.

Procedure steps

Step Action

1 At the Windows desktop interface

Open a Telnet connection to the CS 2000 Management Tool.

2 Log in with the appropriate user name.

3 Invoke the MS 2000 Series CLUI

/opt/nortel/NTsesm/bin/ms2000.sh

4 When prompted, enter the appropriate user name and password.

The Media Server 2000 Series CLUI Main Menu is displayed.

5 Enter the number to select the Node Maintenance andConfiguration menu option.

6 When prompted, enter the IP address of the Media Server node.

The Main Menu is displayed.

7 Enter the number to select the Configuration Menu, menuoption.

The Main Menu is displayed.

8 Enter the number to select theDisplay this nodes currentconfiguration menu option.

The current configuration data for the selected node is displayed.

9 Press Enter.

The Main Configuration Menu is displayed.

10 Follow the prompts to return to the Media Server 2000 SeriesCLUI Main Menu.

11 Enter x to exit the Media Server 2000 Series CLUI Main Menu.


NN10450-900 06.023 October 2008


.

Procedure steps 149

12 Enter exit to close the Telnet session.

--End--


NN10450-900 06.023 October 2008


.


Backing up the APS-specific Oracle database andapplication files

To ensure successful recovery from a system problem that causesdatabase file corruption, it is recommended that you periodically back upthe database files that support operation of the APS. These files include:

• Oracle database files

• Root database files

• non-Root database files

To back up these files, use the following procedures:

• “Performing a backup of Oracle/MySQL data on an SPFS-basedserver” (page 156) to back up the Oracle database. This utility runsautomatically each day at 1 a.m. and backs up the database to a 4mmDAT tape. The utility can also be run manually to back up the databaseto a disk file.

• “Performing a backup of file systems on an SPFS-based server” (page164)to back up the UNIX file system, including all of the "Root" and"non-Root" database files.

Instructions for performing these procedures are found in NN10409-500.

Two APS-specific utilities enable you to back up selected files,when only files required for APS operation must be restored. The"ips_export_db.sh" utility backs up the APS Oracle database. The"backup_appl_data.sh" utility backs up only the non-Root application files,"/audio_files," "PROV_data," "/user_audio_files," and Root application file,"/etc/inet/hosts." Both of these utilities can only be run manually.

This procedure enables you to perform a complete manual backupof the APS-specific Oracle database files and application files. It isrecommended that this procedure be performed once for each week.

Procedure stepsIn a telnet connection to the APS server

Step Action

1 Open an xterm window, and log on using the "maint" logon andpassword.

2 Become the "root" user by entering:

su - root


NN10450-900 06.023 October 2008


.

Procedure steps 151

3 Start the backup

ips_export_db.sh -diskonly

The system displays a log of the backup activity.

4 List the content of the tape on the terminal screen to verify thebackup by entering the following commands:

cd /audio_files/aps_db_backup

ls -l

A listing of the backed-up files displays. Look in this list for "dmp"files.

more README

A timestamp displays, which should show the time and date ofthis backup.

ATTENTIONAt this point, you have completed the disk-only portion of the backup.Continue with the next step to complete the backup of the applicationfiles. The application files are backed up on tape.

5 Insert a write-enabled (white or grey tab is moved to the rightwhere it can be seen) DAT tape into the 4mm DAT drive on theAPS server. Rewind the tape

mt -f /dev/rmt/0c rewind

6 Start a backup of the application file systems on a single tape:

/usr/ntdb/uas/scripts/backup_appl_data.sh

The system displays a log of the backup activity.

7 Rewind the backup tape


8

List the content of the tape on the terminal screen to verify thatthe backup was successful

tar tvf /dev/rmt/0c | more

9 Eject the backup tape, label it, and move the write-enable tabto the "read-only" position (white or grey tab is moved to theleft where it cannot be seen), to prevent the data on the tapefrom being accidentally over-written. Store the tape for use later.Insert another write-enabled DAT tape into the drive to be used


NN10450-900 06.023 October 2008


.


for the automatic Oracle system back up that runs daily at 1:00a.m.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 153

Using the command line interface to performbackups

You can use the command line to perform full, incremental, or selectivebackups. You can perform multiple backups on multiple devices in a singlecommand. You have the option of obtaining the backup information from afile.

To display online help for this command, use the -h option on thecommand line.

Prerequisites• Before you perform a backup, you need to start up the Backup

Controller and Providers.

Procedure steps

Step Action

1 Enter the following command as one continuous command

/opt/MagellanNMS/bin/nsbck[-full <devtype> <devname> <devaddr> <id> <pw>][-incr <devtype> <devname> <devaddr> <id> <pw>][-view <viewname> <devtype> <devname> <devaddr><id> <pw>][-cdir <backup_dir_path> [-f<backup_info_file>][-chost <controller_address>][-nolog] | [-log [<logfile>]][-nc <#_concurrent_connections>]

2 The service data backup files have the following namingconvention:

./<devtype>/<devname>/<timestamp>.<dataset>/ \<datafiles...>

ATTENTIONThe period (.) represents the SNMP Devices Backup and Restoreroot directory.

--End--


NN10450-900 06.023 October 2008


.



<backup_info_file> the name of the file containing backupinformation. Each line in the file has the sameformat as the -full, incr, or -view options.

cdir The backup directory used for this backupoperation.

<controller_address> the address of the Controller and has the formathost[:port]

<datafiles...> The names of one or more files that are backedup.

<datatset> the dataset name.

<devaddr> the IP address of the device and has the formatn.n.n.n.

<devname> the name of the device.

<devtype> The device type (PP4400, or PP4460)

<id> is the user ID for a Passport and the READcommunity string for a Passport 4400/4460.

<logfile> the name of the file to which output messagesgo. If not specified, the messages go to the filembrbackup.log on the current directory (wherethe tool runs).

<pw> the user password for a Passport and theWRITE community string for a Passport4400/4460.

<timestamp> has the format yyyymmddhhmmss

<view> indicates a selective backup.

<viewname> the name of the view file for a selective backup.

<#_concurrent_connections> the number of concurrent backups.

-chost indicates the remote Controller to be used inplace of the Controller running on the local host.

-f indicates that the backup information is obtainedfrom a file.

full indicates a full backup.

-incr indicates an incremental backup.

-log indicates that output messages go tostdout/stderr or to a log file. The default isstdout/stderr.


NN10450-900 06.023 October 2008


.


Variable Value

-nc indicates the number of concurrent backupsto be performed. By default, SNMP DevicesBackup tries to back up 5 different devicesconcurrently. This parameter is useful when youare backing up a large number of devices.

-nolog indicates that output messages are to bediscarded.


NN10450-900 06.023 October 2008


.


Performing a backup of Oracle/MySQL data on anSPFS-based server

Perform the following to execute a backup of Oracle/MySQL data on aSPFS-based server (Sun Netra 240).

The server can be hosting one or more of the following components:

• Multiservice Data Manager (MDM)

• Communication Server Management Tools

• Integrated Element Management System (IEMS)

• Audio Provisioning Server (APS)

• Media Gateway (MG) 9000 Manager

• Network Patch Manager (NPM)

• Core and Billing Manager (CBM)

An Oracle/MySQL data backup is not required when the SPFS-basedserver is hosting the CBM or the MG 9000 Manager.

If the SPFS-based server is hosting the IEMS, it is highly recommendedto purge the IEMS event and performance data prior to executing thedata backup. This reduces the size of the space used by the IEMS, andtherefore, reduces the backup time, and possibility of a backup failure. Thepurge capability is only available in (I)SN07 onward.

For more information, see "Configuring dark office backups on anSPFS-based server" in Nortel ATM/IP Solution-level Configuration ((NN10409-500)) .

ATTENTIONIt is recommended that provisioning activities be put on hold during the time ofthe data backup.

Prerequisites• For a Sun Netra 240, you need one or more blank DVDs to store the

data.

• The backup utility limits the storage to 4GB on a DVD-R or DVD-RW.

• If you are using a new DVD-RW or want to reuse a DVD-RW byerasing the contents, perform procedure ‘Preparing a DVD-RW foruse’ in Nortel ATM/IP Solution-level Administration and Security ((NN10402-600))


NN10450-900 06.023 October 2008


.

Procedure steps 157

ATTENTIONThe database must be in sync with the Communication Server 2000 and theMG 9000 Manager (if present). Therefore, ensure you have the appropriateimage of both before you proceed. Performing a restore from the Oracle/MySQLdatabase alone can cause data mismatches at the Communication Server 2000and the MG 9000 Manager (if present).

Procedure stepsATTENTIONIn a two-sever configuration, execute this procedure on the Active server.

Step Action

1 At the server, insert the blank DVD into the drive. In a two-serverconfiguration, insert the blank DVD into the drive of the Activeserver.

2 At your workstation, log on to the server by typing

> telnet <server>



4 Change to the root user by typing

$ su -



6 If the server is hosting the IEMS, and you want to purge theevent and performance data, go to step 7, otherwise, go to step10

7

ATTENTIONThis step stops the IEMS server. Ensure it is acceptable at this timeto stop the IEMS server application.

Stop the IEMS server

# servstop IEMS

8 Run the script to purge the data

# /opt/nortel/iems/current/bin/purgeTempData.sh

9 Start the IEMS server

# servstart IEMS

10 Back up the data


NN10450-900 06.023 October 2008


.


$ /opt/nortel/sspfs/bks/bkdata

Example response:

[12/30/06:17:35:03] cs2k0bd:/> /opt/sspfs/bks/bkdataBackup behavior is set to 1 ...*** Note: 8X or higher DVD-RW media may result in a lowersuccess rate. ****** DVD will be ejected after the backup is complete ***Do you wish to continue the backup (yes or no)? [yes] yes

11 Reinsert the backup DVD into the drive.

12 List the content of the DVD

# tar tvf /cdrom/*bkdata*/*.tar

Example response:

-rw-rw-rw- 0/1 1874917 Mar 2 10:17 2005 opt/oracle.dmp.gz-rw-rw-rw- 0/1 1007616 Mar 2 10:17 2005 opt/critdata.cpio

Example response for server which hosts MySQL:-rw-rw-rw- 0/1 1874917 Mar 2 10:16 2005 opt/oracle.dmp.gz-rw-rw-rw- 0/1 1007616 Mar 2 10:16 2005 opt/critdata.c

-rw-rw-rw- 0/1 1874917 Mar 2 10:16 2005 opt/mysql.dmp.gz

When a DVD backup spans more than one disk, all the DVDswith the exception of the last one produce a file error duringthe verification process. This error message does not interferewith the backup process but can reappear several times as thebackup spans multiple disks.

13 Go to the root directory

# cd /

14 Eject the DVD

# eject cdrom

If the DVD drive tray does not open after you have determinedthat the DVD drive is not busy and is not being read from orwritten to, enter the following commands in the order listed:

# /etc/init.d/volmgt stop

Then press the eject button located on the front of the DVDdrive.

# /etc/init.d/volmgt start

15 Remove the DVD from the drive, label it, and store it in a safeplace.


NN10450-900 06.023 October 2008


.


16 To restore the data from DVD, refer to the procedure "Restoringthe oracle data on an SPFS-based server" in Nortel ATM/IPSolution-level Administration and Security ( (NN10402-600)) .

--End--


<server> IP address or hostname of the SPFS-basedserver on which you want to perform thebackup. In a two-server configuration, enter thephysical IP address of the active server.


NN10450-900 06.023 October 2008


.


Backing up UAS configuration files

Back up UAS configuration files to support the operation of the UAS.

For more information about UAS configuration files, see “Job aid” (page161).

Procedure stepsATTENTIONAt the time of installation, the UAS is configured to automatically back upconfiguration files each day at 2:00 am. If an APS node is configured in thenetwork, all UAS nodes in the network can be backed up to the APS node. Ifan APS node is not configured in the network, the configuration files for UASnodes in the network can be backed up to a remote UNIX server instead. Thisprocedure enables you to set up automatic backup to a remote server.

At the Windows desktop interface

Step Action

1 Open the command interface, select Start -> Run then type cmdin the displayed window.

2 Open a telnet session to the remote UNIX server and log in asthe Root user.

3 Enter the following commands to create a new backup directory

cd /;mkdir /opt;chmod 777 opt

cd /opt;

mkdir uas;chmod 777 uas

cd uas;

mkdir uas_conf_backup;chmod 777uas_conf_backup

cd /

cd /opt/uas/uas_conf_backup

4

ATTENTIONThe commands from this point forward are specific to a Sun Solarissystem only.

Configure NFS to share the "/opt/uas" filesystem and start theNFS server

echo "share -F nfs /opt/uas" >>/etc/dfs/dfstab


NN10450-900 06.023 October 2008


.

Job aid 161

/etc/init.d/nfs.server start

5 Create a user logon called "Administrator" that does not require apassword:

/usr/sbin/useradd -d/export/home/Administrator -g 1 -s /bin/ksh -m -u 1002Administrator 2> /dev/null

passwd -d Administrator 2> /dev/null

6 At the local system console, enter the IP address of the remoteserver in the "Backup Storage IP" field of the Local ConfigurationInterface GUI screen, using the procedure "Modifyingconfiguration parameters through the Local ConfigurationInterface GUI" in the document (NN10095-511), entitled "UASConfiguration Management."

--End--

Job aidBack up UAS configuration files are stored in configuration files. Theconfiguration files include:

• uas.conf - containing configuration parameters that support the functionof the UAS, including CG6000C card settings, Call Agent definition,APS hostname definition, network element settings, and conferencingservice state definition

• ugw.conf - containing trunk configuration information for PRI Solutions

• snmpd.cnf - containing parameters that support the SNMP function,including management station address, SNMP user names, communitynames, and trap version

• hosts - containing parameters that support the function of the APS,including APS hostname and IP address

• atmhard.con - containing ATM bearer interface settings that link a localport ATM address to a particular ATM interface port

• atmconn.con - containing ATM bearer connections settings that providethe UAS with a remote gateway’s name and ATM address

• mainsa.conf - containing Main Subagent program settings specifyingthe kinds of error and log messages to be sent to the managementstation

• atmSvcProfile.con - containing data on Switched Virtual Channel (SVC)traffic parameters associated with AAL2 SVCs

• atmhardloop.con - containing information associated with the loopbackof SVCs


NN10450-900 06.023 October 2008


.


Performing a manual backup of the Policy Controllerdatabase

Perform a manual backup of the policy controller database to make regularbackup copies of the database or as a precautionary activity beforestarting any type of upgrade to the Policy Controller application. Thisprocedure may be used as a standalone task or as part of a higher levelupgrade activity.

ATTENTIONIf you perform provisioning changes during this procedure, it can lead todatabase corruption and possible system outages. To ensure that you createan accurate and complete copy of the active unit database, verify that allprovisioning changes are stopped before continuing this procedure.

PrerequisitesATTENTIONThe Policy Controller database and the CS 2000 database must always be insync. CS 2000 core images, CS 2000 GWC Manager Oracle database backups,and the Policy Controller application backups must always be maintained insync for emergency recovery. To ensure they are in sync, perform images andbackups at the same time.

Procedure steps

Step Action

1 Log on to the active Policy Controller unit and change to the rootuser.

2 Change directory to the database directory by typing

# cd /opt/apps/database/solid/dbfiles

3

ATTENTIONIf other backup copies of the database exist with the same filename,you have the option of deleting those files or putting the backup copyinto the backup directory under a new file name.

Put a copy of the database for the active unit in the backupdirectory by typing

# cp solid.db /opt/apps/database/solid/backup


NN10450-900 06.023 October 2008


.

Job aid 163

#cp solid.db /opt/apps/database/solid/backup/solid.db.backup1

--End--

Job aidFor security purposes, ensure that a backup copy of the database file istransferred to a secure location.

Use the UNIX scp command to make a secure copy of the backupdatabase file to a secure, remote server on your network. This servershould be continuously available for cases where a restoration of thePolicy Controller application database become necessary, such as duringan upgrade rollback. A root password for the remote server may berequired.


NN10450-900 06.023 October 2008


.


Performing a backup of file systems on anSPFS-based server

Perform the following to execute a backup of the file systems on aSPFS-based server (Sun Netra 240).


• Communication Server 2000 Management Tools




• Network Patch Manager

• Core Billing Manager (CBM)

Prerequisites• For Sun Netra 240, use one or more blank DVD-R or DVD-RW disks

to store the data. The backup utility limits the storage to 4 GB on aDVD-R and DVD-RW.

If you are using a new DVD-RW, or want to reuse a used DVD-RWand need to erase the contents, complete procedure "Preparing aDVD-RW for use" in Nortel ATM/IP Solution-level Administration andSecurity ( (NN10402-600)) .

• For Nortel Core and Billing Manager 850, you must be a user in a rolegroup authorized to perform config-admin actions.

• For Nortel Core and Billing Manager 850, you must obtainnon-restricted shell access.

Procedure stepsATTENTIONIn a two-sever configuration, execute this procedure on the Active server.

Step Action

1 Insert the blank DVD into the drive. In a two-server configuration,insert the blank DVD into the Active server.

2 Log on to the server by typing

> telnet <server>


NN10450-900 06.023 October 2008


.

Procedure steps 165

and pressing the Enter key.



$ su -


5 When prompted, enter the root password

In a two-server configuration, ensure you are on the activeserver by typing ubmstat. If ClusterIndicatorSTBY is displayedin the response, which indicates you are on the inactive server,log off of that server and log on to the other server through telnetusing the physical IP address of the other unit. The responsemust display ClusterIndicatorACT, which indicates you are onthe active server

6 Back up the file systems by typing

# /opt/nortel/sspfs/bks/bkfullsys


When using a DVD, the system will prompt you to insert anotherblank disk if more than one is needed.

7 When prompted, continue the backup by typing

yes


Example response

Backup completed. Please verify the data on the DVDusing the cli command - select option for "Other", then"bklist"Note: This action does not include backup data insidethe Oracle Database.Finish time: Thur Jan 4 11:03:46 HKT 2007.cleaning up filesA backup of oracle data is recommended at this time.On a SPFS based server only hosting the CBM or MG 9000Manager this is not required.Do you want to perform a backup of oracle data?

Type "yes" to continue with oracle backup or "no" to skip:

ATTENTIONIf you need to abort an in-progress backup, press Ctrl+c and wait forconfirmation that the backup has been aborted.

8 When prompted, backup the Oracle database by typing

yes



NN10450-900 06.023 October 2008


.


9 Insert the backup DVD into the drive. If the backup resides onmultiple DVDs, insert the first backup DVD.

10 Access the command line interface by typing

# cli


11 Enter the number next to the Other option.

Example response

Other1 - Log Rotation2 - copylogs (Logviewer - Capture Various Logs ForDebugging Purposes)3 - logextractor (Logviewer - Extracting compressed logfiles captured by c...)4 - logbrowser (Logviewer - Browse logs on the system)5 - logviewer utility cleanup (Logviewer - Clean up spaceuse by Logviewer ...)6 - capt_rtes (Capture run-time environment fordebugging)7 - free_disk_space (Free Some Disk Space)8 - sun_explorer (Execute the Sun Explorer Data GatheringTool)9 - mount_image (Mount A Generic Iso Image To The SSPFSunit)10 - umount_image (Un-Mount A Generic Iso Image From TheSSPFS Unit)11 - bklist (List DVD backup archive)12 - validate_pam_conf (Validate and/or fix modulepointers in /etc/pam.conf...)

13 - set_disk_quota (Set maximum disk space allowed for auser)

12 List the content of the DVD by entering the number next to thebklist option.

Example response

=== Executing "bklist"cdrin0: no media15:34:24 NOTE: Please insert DVD volume 1, hit enter tocontinue, X to exit

If the content resides on multiple DVDs, the system will promptyou to insert each DVD.

Example response-r-xr-xr-x 0/2 209596 2002-03-14 09:29 usr/dt/bin/dtcalc-r-xr-xr-x 0/2 738032 2002-03-14 09:49 usr/dt/bin/dtcm17:49:30 NOTE: End of volume


NN10450-900 06.023 October 2008


.

Procedure steps 167

17:49:30 NOTE: Ejecting DVD..17:49:36 NOTE: Checking DVDcdrom0: no mediaPlease insert the next volume disk and hit x <enter> toabort:17:52:56 NOTE: Waiting for DVD to mount-r-xr-xr-x 0/2 103616 2002-03-14 09:49 usr/dt/bin/dtcm_delete

-r-xr-xr-x 0/2 644920 2003-06-19 02:38 usr/dt/bin/dtfile

13 When prompted, press the Enter key to execute the command.

When the command has completed successfully, you will see asystem response.

Example response

-rw-r--r-- 0/1 600 2007-02-09 16:27 .disk_conf/fslist.out17:59:11 NOTE: Backup Verification Passed17:59:11 NOTE: gtar command exited with:017:59:11 NOTE: End of backup archive listing

==== "bklist" execution completed

14 Ensure you are at the root directory level by typing

# cd /


15 Eject the DVD by typing

# eject


If the disk drive tray will not open after you have determined thatthe disk drive is not busy and is not being read from or written to,enter the following commands:



Then, retry the eject cdrom command previously shown andpress the Enter key.

16 Remove the DVD from the drive, label it, and store it in a safeplace. The label should include the date of backup, disk numberof backup, host name, and unit number.

17 If the backup resides on multiple DVDs then insert the nextbackup DVD in the disk drive and go to step 15.

--End--


NN10450-900 06.023 October 2008


.



<server> The IP address or host name of theSPFS-based server on which you areperforming the backup. In a two-serverconfiguration, enter the physical IP address ofthe active server.


NN10450-900 06.023 October 2008


.

Procedure steps 169

Taking a full IEMS backup

Backup the IEMS software which includes the following:

• A backup of the oracle database

• A backup of the servman critical system files

• A backup of the central security database and files

ATTENTIONEnsure that there is enough space in the /data partition for each of thesebackups before continuing.

Prerequisites• The user must have root user privileges to perform this procedure.

Procedure steps

Step Action

1 At your workstation establish a connection to the IEMS serverthrough Telnet or SSH, using the host name or IP address of theserver.

In a two-server configuration, establish the connection to theactive server using the physical IP address of the active server,and ensure you are on the active server using the ubmstatcommand.

For detailed steps, refer to .

2 Log on using the root user ID and password.

3 Select your next step.

If Do

this server is hosting the CMTand IEMS

the next step

this server is only hosting theIEMS

step 6

4 Verify the status of the SESM server application by entering:

servman query -status -group SESMService

5 If necessary, start the SESM server application by entering:

servstart SESMService

6 Enter the backup manager utility by entering:


NN10450-900 06.023 October 2008


.


/opt/bkresmgr/cbm/bkmgr

7 Start the backup by entering:

backup full

8 Select your next step.

If the response is Do

RC=success step 11

RC=fail <reason> step 9 and step 10

9 Unlock the provisioning session by entering:

backup abort

10 Contact your next level of support.

11 Exit the backup manager utility by entering:

quit

The Security Services configuration settings and data are backedup to the following file:

/data/bkresmgr/<date><time>backupSS2.0<host_name>.tar

--End--


NN10450-900 06.023 October 2008


.


Backing up an SPFS-based security client

Backup an SPFS-based security client to obtain a list of the files that willbe backed up from the client machine.

To enable backup and restore of the security client, the files to be backedup are registered with servman during installation. The files backed updepend on the packages installed.

Prerequisites• You must have root user privileges to perform this procedure.

Procedure steps

Step Action

1 At your workstation, open A telnet session to the server by typing

> telnet <server>



su - root


5 Enter the following command:

cat etc/critdata.conf

The system returns a list of all non-oracle data files that will bebacked up from the client machine.

6 Use the Synchronous Backup Restore Manager (SBRM) tobackup the central security client data. When SBRM is run, all ofthe SPFS data, including the security client data and oracle data,is backed up. For details, see .

--End--


<server> IP address or host name of the server whereIEMS resides.


NN10450-900 06.023 October 2008


.


Backing up a Multiservice Switch or Media Gatewaydevice

This section describes using Service Data Backup and Restore to performa basic back up of service data.

Backup copies only the configuration data of the Multiservice Switch7400/15000 or Media Gateway 7400/15000. The service data views thatmake up the configuration data are found on the Multiservice Switch7400/15000 or Media Gateway 7400/15000 disk in a set of files inindividual directories under the directory /provisioning. Backup also copiesthe special files that are found under the directory /provisioning/netsentry.

Service Data Backup and Restore provide three types of backup.

• A full backup copies all service data on the selected device or devices.

• An incremental backup copies only service data changed or createdsince the last backup. Like the full backup, you can perform anincremental backup on either one or multiple devices.

• A selective backup copies specific service data that you select. Youcan perform a selective backup on either one or multiple devices.

The following information applies to using the Service Data Backup andRestore tool to backup Multiservice Switch 7400/15000 or Media Gateway7400/15000 nodes:

• “Adding Multiservice Switch 7400/15000 or Media Gateway7400/15000 devices to the backup list” (page 173)

• “Removing Multiservice Switch 7400/15000 or Media Gateway7400/15000 devices from the backup list” (page 173)

• “Viewing the Multiservice Switch 7400/15000 or Media Gateway7400/15000 backup repository” (page 174)

• “Defining a specific userid and password for a Multiservice Switch7400/15000 or Media Gateway 7400/15000 in the backup list” (page174)

• “Changing the Default User Authentication” (page 175)

• “Performing a full backup for a Multiservice Switch 7400/15000 orMedia Gateway 7400/15000 device” (page 175)

• “Performing a selective backup for a Multiservice Switch 7400/15000 orMedia Gateway 7400/15000 device” (page 176)


NN10450-900 06.023 October 2008


.

Removing Multiservice Switch 7400/15000 or Media Gateway 7400/15000 devices from the backuplist 173

Adding Multiservice Switch 7400/15000 or Media Gateway7400/15000 devices to the backup list

Use this procedure to add devices to the list of devices that you wish tobackup.

Procedure steps

Step Action

1 Open the Backup and Restore window. From the MDM window,select Configuration->Passport Devices->Administration->Passport Service Data Backup/Restore.

2 Select the Backup Configuration tab.

3 Select Add to launch the Add Devices Dialog.

4 From the left pane, select a group of devices or expand thegroup and use the Ctrl key to select multiple devices within agroup.

5 From the drop down list, in the right pane, select a backup mode(Incremental or Full).

6 If a specific userid and password is required for the device, enterthe values in the user ID and Password fields and uncheck theUse default checkbox.

7 If you wish to use the default userid and password, click the Usedefaultcheckbox.

8 Click OK.

The devices are displayed in the Device List.


--End--

Removing Multiservice Switch 7400/15000 or Media Gateway7400/15000 devices from the backup list

Use this procedure to remove devices from the list of devices that youwish to backup.

Procedure steps


NN10450-900 06.023 October 2008


.


Step Action



3 In the Device List, select the devices you wish to remove.

4 Click Remove.

5 In the confirmation dialog, select Yes to confirm or No to cancelthe removal.


--End--

Viewing the Multiservice Switch 7400/15000 or Media Gateway7400/15000 backup repository

If the backup server is running locally, use the following procedure to viewall the backup files in the backup repository.

Procedure steps

Step Action

1 Telnet into the remote workstation with the appropriate useridand password.

2 Navigate to the repository directory.

3 Use Unix directory commands to view the contents of the backuprepository.


--End--

Defining a specific userid and password for a Multiservice Switch7400/15000 or Media Gateway 7400/15000 in the backup list

A specific userid and password can be defined when you add the node tothe node list or you can set it later using the following procedure.

Procedure steps


NN10450-900 06.023 October 2008


.

Performing a full backup for a Multiservice Switch 7400/15000 or Media Gateway 7400/15000device 175

Step Action



3 Select a node in the Device List section.

4 In the Device Details section, in the Authentication tab, entera userid and password.

5 Clear the Use defaultcheckbox.


--End--

Changing the Default User AuthenticationUse the following procedure to define a default userid and password whichis used for all node access unless overridden by a specific userid andpassword for the node.

Procedure steps

Step Action


2 Select Options ->Set default authentication.

3 Enter the userid and password in the appropriate fields.

4 Click OK.

The new userid and password are used on the next nodeaccess.


--End--

Performing a full backup for a Multiservice Switch 7400/15000 orMedia Gateway 7400/15000 device

Use this procedure to perform a complete system backup of a MultiserviceSwitch 7400/15000 or Media Gateway 7400/15000 device.


NN10450-900 06.023 October 2008


.


Procedure steps

Step Action





5 Click in the Mode title and selectFull from the drop-down list.

6 Click Backup.

The progress of the backup is displayed in the Messages area.If the backup is unsuccessful, an error dialog is displayed thatspecifies the device and the reason for the failure.

Note: To cancel a backup in progress click Cancel.


--End--

Performing a selective backup for a Multiservice Switch 7400/15000or Media Gateway 7400/15000 device

Use the following procedure to backup only a single specified file to therepository.

Procedure steps

Step Action






NN10450-900 06.023 October 2008


.

Performing a selective backup for a Multiservice Switch 7400/15000 or Media Gateway 7400/15000device 177

5 Select a device from the Devices list.

6 In the Mode title, select Selective from the drop-down list.

The Configuration column in the table is enabled.

7 Click in the Configuration cell to display a pull-down list thatdisplays all the available views on the Multiservice Switch7400/15000 or Media Gateway 7400/15000.

Note: This step may take a few seconds to completebecause the application must access the Multiservice Switch7400/15000 or Media Gateway 7400/15000 and list all theviews names.

8 Click Backup.

The progress of the backup is displayed in the Status area. Ifthe backup is unsuccessful, an error dialog is displayed thatspecifies the device and the reason for the failure.

Note: To cancel a backup in progress click Cancel.


--End--


NN10450-900 06.023 October 2008


.


Performing a backup operation

Perform this procedure to execute a backup operation. If you change theexternal IP address of an Real-time Controller (RTC) system node in yoursystem (or perform any other data provision changes on your system),you should immediately perform a backup operation and delete any datasnapshots that were made before you changed the IP address. Thisensures proper communication with your OAMP workstations.

Procedure stepsAt the OAMP workstation

Step Action

1 Click Administration>backup.

2 Enter a description of the data snapshot in the snapshot-description box. You can enter up to 32 characters.

3 Click the corresponding check box to activate the transfersnapshot to alternate boot server

Nortel recommends that you enable this option. If you don’tselect this option, a warning dialog box appears. Click Yes tocontinue.

4 Click the corresponding checkbox to activate the set as activesnapshot on alternate boot server

Nortel recommends that you enable this option. If you don’tselect this option, a warning dialog box appears. Click Yes tocontinue.

5 Click the corresponding checkbox to activate the delete oldestsnapshot on alternate boot server if maximum reached (16)

6 Click the corresponding checkbox to activate the delete oldestsnapshot on rtc if maximum reached (5)

7 Click Create to create the data snapshot. This can take severalminutes, depending on system activity.

8 Click Close to close the Backup Active RTC window and returnto the Administration window.

9 If you selected transfer snapshot to alternate boot server onalt boot server, go to step 15.

10 Select Administration>file-manager. The File Manager windowappears.

11 Select the active RTC system node from the Destination list inthe right window pane.


NN10450-900 06.023 October 2008


.

Job aid 179

12 Select the new data snapshot from the Snapshot box in theDestination portion of the window. Make note of the timestamp ofthe data snapshot.

13 Copy the snapshot to your alternate boot server by clicking <--.An hourglass appears while the data snapshot is copied. Theboxes in the Source portion (left window) of the window areupdated with the information for the copied data snapshot whenthe copy operation is complete.

These files are large and can take several minutes to copy froman RTC system node to your alternate boot server.

14 When the file is transferred, click Close.

15 Update the Alternate Boot Snapshot using the ABS Settings ABSwindow:

16 Open the Alternate Boot Server (ABS) ConfigurationManager window by clicking ABS Settings on theAdministration>alternate-boot-server window.

17 Select an alternate snapshot by clicking the arrow button.

18 Click Modify to save your changes and close the window.

19 Your backup is complete.

--End--

Job aidThe same backup procedure may be performed through the CLI.

Admin backup create syntax"snapshot-description" abs-transfer-option abs-active-optionrtc-delete-oldest-option abs-delete-oldest-option

where:snapshot-description can be up to 32 characters and the other four optionsare set by entering either y (for enabled) or n (for disabled).

See “Performing a backup operation” (page 178) for option descriptions.

The following example creates a snapshot named my snapshot, transfers itto the ABS and sets it as active. It also deletes the oldest snapshot on thertc or abs, if the maximum number of snapshots is reached on either:

admin backup create "my snapshot" y y y y

The following table lists CLI return codes.


NN10450-900 06.023 October 2008


.


Table 15CLI return codes

Rcode Rcode text

0x40100001 snapshot-description must be string, length (1 - 32), noadditional character filter

0x40100002 rtc-delete-oldest-option must be string, length (1 - 1),boolean (Y, y, N, n)

0x40100003 abs-transfer-option must be string, length (1 - 1),boolean (Y, y, N, n)

0x40100004 abs-active-option must be string, length (1 - 1), boolean(Y, y, N, n)

0x40100005 abs-delete-oldest-option must be string, length (1 - 1),boolean (Y, y, N, n)

0x80100001 missing snapshot-description

0x80100002 insufficient disk space on rtc

0x80100003 maximum number of snapshots reached on rtc

0x80100004 maximum number of snapshots reached on abs

0x80100005 unable to delete oldest snapshot on rtc

0x80100006 unable to delete oldest snapshot on abs

0x80100007 unable to transfer snapshot to abs

0x80100008 unable to set snapshot as active on abs

0x80100009 unable to connect to abs, run abs test for details

0x8010000A invalid combination of command options


NN10450-900 06.023 October 2008


.

Prerequisites 181

Creating system image backup tapes (S-tapes)manually

Use this procedure to create a system backup image manually.

Create a system image backup tape (S-tape) manually.

ATTENTIONIf you want to schedule automatic system image backups, see SDM Securityand Administration document.

The system image includes the following:

• boot (startup) files

• AIX operating system

• system configuration data

• SDM CS 2000 Core Manager software

PrerequisitesATTENTIONThis procedure must be performed ONLY from a local console by a trained AIXsystem administrator with root user privileges.

ATTENTIONAll volume groups on the SDM CS 2000 Core Manager must be fully mirrored(Mirrored) before performing this procedure. If not, an error message isdisplayed.

ATTENTIONIf your system includes the SuperNode Billing Application (SBA), you must usetape drive DAT0 to perform this procedure.

ATTENTIONThe files under the /data file system are temporary files only, and are excludedfrom system image backup.

Perform a system image backup after the following events:

• initial installation and commissioning of the SDM CS 2000 CoreManager

• changes to the configuration of disks or logical volumes


NN10450-900 06.023 October 2008


.


• installation of a new version of SDM CS 2000 Core Manager platformsoftware

• installation of new hardware

• changes or upgrades to existing hardware

A system image backup takes a minimum of 10 minutes to complete,depending on the size of your file systems.

Recommended tapesTo complete this procedure, use one of the digital audio tape (DAT) drivetapes approved by Nortel.

The brands approved by Nortel are: Hewlett Packard (HP), Maxell,Verbatim, Imation.

The tape lengths approved by Nortel are:

• 90-meter (90M)

• 125-meter (125M)

• 120-meter (120M)

The 125M tape is approved for UMFIOs only, assuming that your systemis equipped with DDS3-capable devices to read the content of the tape.

Procedure stepsThe following flowchart provides an overview of the procedure. Use theinstructions in the procedure that follows the flowchart to perform theprocedure.


NN10450-900 06.023 October 2008


.

Procedure steps 183

Figure 13Summary of creating system image backup tapes (S-tapes)


NN10450-900 06.023 October 2008


.


Creating system image backup tapes (S-tapes)At the local VT100 console

Step Action

1 Log on to the SDM CS 2000 Core Manager as the root user.

2 Access the maintenance interface:


NN10450-900 06.023 October 2008


.

Procedure steps 185

# sdmmtc

3

CAUTIONSystem mirroring must be MIRROREDYou cannot perform this procedure until disk mirroringof all volume groups is Mirrored. If necessary, contactthe personnel responsible for your next level ofsupport. When disk mirroring is Mirrored, continuethis procedure.

Access the storage menu level:

> storage

Example response:

Volume Group StatusFree(MB)rootvg Mirrored 608

Logical Volume Location Size(MB)%full/threshold 1 / rootvg 2025/ 802 /usr rootvg 192 85/ 903 /var rootvg 64 11/ 804 /tmp rootvg 24 6/ 905 /home rootvg 300 4/ 706 /sdm rootvg 300 44/ 90Logical volumes showing: 1 to 6 of 6

4 If the disks are "Mirrored" then go to step 6

5 If the disks are not "Mirrored" then contact next level of support

6 Access the administration (Admin) menu level of the RMI:

> admin

7 Access the System Image Backup and Restore Menu:

> backup

Example response:

Currently there is a backup running on bnode73.Pleaseexecute yours later.Exiting . . .

ATTENTIONIf another operator attempts to use the Backup and Restore utilitywhen it is in use, an error message is displayed.

8 From the System Image Backup and Restore Menu, selectCreate a System Image on Tape (S-tape):

> 2


NN10450-900 06.023 October 2008


.


After you select option 2, you are prompted to select the tapedrive.

Example response:

Select the tape drive you wish to use:

Enter 0 to return to previous menuEnter 1 for tape drive DAT0 in Main Chassis-Slot 2Enter 2 for tape drive DAT1 in Main Chassis-Slot 13( 0, 1 or 2 ) ==>

ATTENTIONUse tape drive DAT0 (option 1) if your system also includes SBA.

9 Select the tape drive to use:

> <n>

ATTENTIONIf your system includes SBA, and you wish to use tape drive DAT1(option 2), the following message is displayed:

Example response:

You have selected DAT 1. This is the default DAT drivefor the Billing application, and may currently be in usefor the emergency storage of billing records.If you continue to use DAT 1, make sure that the correcttape is in the drive, and that billing records will not belost during the backup restore operation.Do you wish to continue with DAT 1? ( y | n )

If you wish to continue using DAT1 then do enter ypress the Enter key

If you do not wish to use DAT1 then do enter npress the Enter key

The system prompts you to return to the System Image Backupand Restore Menu if you do not wish to use DAT1.

After you select the tape drive, you are prompted to insert a tapein the drive you have selected.

Example response:Please insert a 4mm DAT tape into the tape drive DAT0.

Caution:This action will overwrite the content on the insertedtape.Do you want to proceed? ( y | n )==>

At the SDMCS 2000 Core Manager10


NN10450-900 06.023 October 2008


.

Procedure steps 187

CAUTIONSystem image backup tapeCreating a system image overwrites the contentsof the inserted tape. Ensure that you are usingthe correct tape before starting the system imagebackup. If your system includes SBA and you areusing DAT1, ensure that the tape drive does notcontain an SBA tape.

Ensure that the appropriate SDM CS 2000 Core Manager tapedrive contains a 4-mm digital audio tape (DAT) either 90 m or120 m long. This tape will be designated as the system imagebackup tape (S-tape).

ATTENTIONFor the complete list of approved tapes, see the “Recommendedtapes” (page 182).

At the local console11 When you are certain you are using the correct tape, enter:

> y

12 Read the system message to determine if there is enough roomon the temporary directory for the system image backup toproceed.

ATTENTIONIf there is not enough room on the temporary directory, an errormessage appears.

Example response:

Rewinding the tape...The /tmp directory is not big enough.Trying to expand /tmp by 6600KB...Failed to expand the /tmp directory because there isn’tenough free disk space left on the rootvg.Please erase some files under /tmp directory to create atleast 6600KB for the full system image backup.

Enter any key and return to exit ==>

13 If there is enough disk space then do step 14

14 If there is not enough disk space then do step 11

15 Erase enough files from the temporary directory to create therequired amount of disk space specified in the error message:

> rm -rf /tmp/<filenames>


NN10450-900 06.023 October 2008


.


ATTENTIONIf you have trouble erasing files from the temporary directory to freeup disk space, contact the personnel responsible for your next levelof support.

16 Execute the system image backup again.

The system image backup begins.

Example response:

Rewinding the tape...Starting the system image backup on bnode73.The backup takes a minimum of 10 minutes, depending on thesize of your file systems.When the backup is complete, you will be asked to removethe tape from the tape drive.

System image backup is in progress ...

ATTENTIONThis backup process takes approximately 10 minutes to complete,depending on the amount of data stored on the disk.

17 Read the system message.

18 If the backup is successfully completed then do step 16

19 If the backup fails then do contact your next level of support

20 The system informs you if the backup is successful. When thebackup is complete, the system prompts you to remove the tapeand label it as an S-tape.

Example response:

The tape backup started on Wed Oct 16 08:21:15 EDT 1997completed successfully on Wed Oct 16 08:37:37 EDT 1997.A log file /tmp/s-tape.log has been created.Please remove the backup tape from the tape drive.Label the tape as shown below and store it in a safe place.System Image Tape (S-tape)The Machine Node Id: bnode73Date: Wed Oct 16 08:37:37 EDT 1997

Eject the S-tape from the tape drive? ( y | n )==>

21 Determine if you wish to eject the S-tape. Enter

• y to eject the tape, or

• n if you do not wish to eject the tape, and wish to list itscontents.

If you wish to list the S-tape then do step 28


NN10450-900 06.023 October 2008


.

Procedure steps 189

If you protect and label the tape then do step 16

If you eject the tape, the screen displays "Tape ejected." belowthe information displayed in step 14. You are then prompted toreturn to the System Image Backup and Restore Main Menu.

Response:

Tape ejected.

Would you like to return to the previous menu? ( y | n)

22 Place the write-protected tab of the S-tape in the open position,to prevent accidental erasure.

23 When you are ready for the system to return to the SystemImage Backup and Restore Main Menu, enter

> y

24 Determine if the backup is successful.

The system informs you if the system image backup issuccessful, as shown in the response in step 14. You may alsowish to view the s-tape.log file or list the files on the S-tape.

25 If you wish to view the s-tape.log file then do step 19

26 If you wish to list the S-tape then do step 28

27 If the backup is successful then do step 38

28 If the backup fails then do contact your next level of support

29 Exit the System Image Backup and Restore Main Menu:

> 0

30 Exit the RMI:

> quit all

31 Access the s-tape.log file:

# cd /tmp

32 Scroll through the file:

# more s-tape.log

This screen informs you that the system image backup wascompleted successfully.

Example response:

bosboot: Boot image is 5881 512 byte blocks.0+1 records in.1+0 records out.Backing up the system.............................................................0512 038 mksysb: Backup Completed Successfully.


NN10450-900 06.023 October 2008


.


The S-tape backup started on Wed Oct 16 09:24:07 EDT 1997completed successfully on Wed Oct 16 09:36:03 EDT 1997

33 Determine if you wish to list the S-tape.

34 If you wish to list the S-tape then do step 24

35 If you do not wish to list the S-tape then do step 40.

36 Return to the login directory:

# cd

37 Access the RMI:

# sdmmtc

38 Access the administration (Admin) menu level of the RMI:

> admin

39 Access the System Image Backup and Restore Menu:

> backup

40 From the System Image Backup and Restore Menu, select ListContents of the System Image Tape (S-tape):

> 3

41 After you select option 3, you are prompted to select the tapedrive.

Example response:

Select a tape drive you wish to use:

Enter 0 to return to previous menuEnter 1 for tape drive DAT0 in Main Chassis-Slot 2Enter 2 for tape drive DAT1 in Main Chassis-Slot 13( 0, 1 or 2 ) ==>


42 Select the tape drive:

> <n>

Example response:

You have selected DAT 1. This is the default DAT drivefor the Billing application, and may currently be in usefor the emergency storage of billing records.If you continue to use DAT 1, make sure that the correcttape is in the drive, and that billing records will not belost during the backup restore operation.

Do you wish to continue with DAT 1? ( y | n )


NN10450-900 06.023 October 2008


.

Procedure steps 191

If you do not wish to use DAT1, the system prompts you toreturn to the System Image Backup and Restore Menu.

43 If you wish to continue using DAT1 then enter

y

44 If you wish to not continue then enter

n

ATTENTIONIf your system includes SBA, and you still wish to use DAT1 (option2), the following message is displayed:

45 After you select the tape drive, you are prompted to insert theS-tape into the tape drive that you selected in step 30.

Example response:

Please insert your System Image Backup tape (S-tape)into the tape drive DAT0 and allow at least 5 minutes tocomplete the listing.A log file will be saved in /tmp/s-tape.toc.

Are you ready to proceed? ( y | n )

At the SDM CS 2000 Core Manager46 Insert the S-tape into the tape drive.

ATTENTIONWait until the tape drive stabilizes (yellow LED is off) before youproceed.

At the local VT100 terminal47 When you are ready to continue this procedure, enter:

> y

48 The contents of the S-tape are displayed. When the listing iscomplete, the system prompts you to return to the System ImageBackup and Restore Menu.

Example response:

Would you like to return to the previous menu? ( y | n )

49 Return to the System Image Backup and Restore Menu:

> y

At the CS 2000 Core Manager50 If you have not already done so, remove the S-tape from the

tape drive by pressing the eject button on the tape drive.

51 Label the tape according to your office practices, and store it in asafe location.

52 If you ejected an SBA tape, reinsert the tape.


NN10450-900 06.023 October 2008


.


At the local VT100 terminal53 Exit the System Image Backup and Restore Menu,:

> 0

ATTENTIONIf you wish to exit the RMI, enter QUIT ALL.

--End--


<n> is the option (1 or 2) for the tape drive you wishto use


NN10450-900 06.023 October 2008


.

Procedure steps 193

Displaying actions a user is authorized to perform

Display the actions a user in a particular role group is authorized toperform.

Prerequisites• You must be authorized to perform security-view actions.

Procedure steps

Step Action

1 At the local or remote VT100 console

Log into the core manager as a user authorized to performsecurity-view actions.

2 Access the maintenance interface, type

sdmmtc

3 Access the Admin level, type

admin

4 Access the User level, type

user

A list of users and authorization groups is displayed.

5 Display the actions a user in a particular role group is authorizedto perform, type

dispgrpr <group> act

Sample response for the secadm group

Authorized actions for secadmsecurity-adminsecurity-managesecurity-view

6 Exit the maintenance interface, type

quit all

--End--


NN10450-900 06.023 October 2008


.



<group> Value can be: maint, secadm, or emsadm

Job aidRole groups allow you to group individual users according to the task eachuser has to complete. The following table lists the standard actions foreach role group in a standalone system.

Role group Standard action

emsadm Authorized to perform these actions:

fault-view, fault-manage, fault-admin,accounting-admin, config-view,config-manage, config-admin,accounting-view, accounting-manage,accounting-admin, performance-view,performance-manage, performance-admin

Gr740Oss Authorized to perform these actions:

performance-manage

maint Authorized to perform these actions:

fault-view, fault-manage, config-view,config-manage, accounting-view, accounting-manage, performance-view,performance-manage

passthru No authorized actions.

root (user) Authorized to perform all actions.

secadm Authorized to perform these actions:

security-view, security-manage,security-admin


NN10450-900 06.023 October 2008


.

Procedure steps 195

Logging in to the Nortel CS 2000 Core Manager

Use this procedure in a standalone system to log in to the Nortel CS 2000Core Manager.

For a complete description of logon methods, see Nortel CS 2000 CoreManager Basics, (NN10018-111).

Prerequisites• You must be a user authorized to perform actions associated with the

procedure.

• It is recommended that you log in to the CS 2000 Core Manger throughSSH (secure shell) using a password.

Procedure stepsAt the local or remote VT100 console

Step Action

1 Log in to the CS 2000 Core Manager using one of the followingcommands for SSH access:

ssh <userID>@<IPaddress | hostname>

or

ssh -l <userID> <IPaddress | hostname>

Example response:

Don_secu’s Password:

2 Enter your password.

3 Access a user interface, for example, access the maintenanceinterface:

sdmmtc

4 Exit the maintenance interface:

quit all

--End--


NN10450-900 06.023 October 2008


.



<userID> is your user ID

<IPaddress> is the IP address of the CS 2000 Core Manager

<hostname> is the host name for the CS 2000 Core Manager


NN10450-900 06.023 October 2008


.

General stream information 197

Preparation for SBA installation and configuration

The majority of procedures in this document require you to fill out thesequestionnaires. Check the prerequisites of each procedure to determine ifyou require information from this section.

General stream informationThe following table contains a list of questions that concern general streaminformation. Record your answers in the spaces provided.

Table 16General stream information

# Question Explanation Answer

1 What is the name of thisstream?

stream_nameThe stream name on the SBA must matchthe stream name on the DMS Switch.

This name must match a stream name inthe CM table CRSFMT.

Type: string

Range: 1 to 4 characters

Example: AMA

Example: GCDR

(not case sensitive)

2 Enter total traffic rateat engineered capacity(ENGCAP) in million BHCAfor the total billing trafficrate including the data andvoice requirements.

See the rest of this section for moreinformation.

3 Enter Number of retentiondays

The number of days for storing the billingfiles in the file system and within thefile system capacity for the current newstream.


NN10450-900 06.023 October 2008


.


Table 16General stream information (cont’d.)


4 What is the associatedstream name?

associated_streamThis question applies only to filterstreams.

The associated stream name parameterspecifies the name of the associated CMbilling stream.

Type: string


Example: AMA, OCC


5 What is the name of theFilter Criteria file?

filter_criteria_fileThis question applies only to filterstreams.

Enter the filter criteria file name thatcontains the expression to be applied forthe filtered stream.

Type: string


(case sensitive)

6 What is the record formatof this stream?

record_formatThe stream record format on the SBAmust match the record format of the DMSSwitch stream.

The only record formats supported by thisproduct and release are

• BC (Bellcore AMA format)

• SMDR (Station Message DetailRecording)

• CDR300

• CDR250


NN10450-900 06.023 October 2008


.




Type: enumeration

Range: BC, SMDR, CDR300, CDR250


7 What is the file format ofthis stream?

file_formatThis is the format of the billing files thatSBA creates on the core manager.

Type: enumeration

Range: DNS, DIRP(not case sensitive)

8 What is the name of thelogical volume on the coremanager for storing thebilling files for this stream?

logical_volume_nameThe logical volume is the name of thedirectory where the billing files are storedfor this stream.

Type: stringRange: 1 to 255 characters

9 Will file transfers for thisstream be initiated by

• SBA (outbound)

• the downstreamdestination (inbound)

file_transfer_modeBilling files always move from SBA tothe downstream destination, but the filetransfers can be initiated by

• SBA (outbound)

• the downstream destination (inbound)

If Outbound is chosen, the SBA must beconfigured with additional file transferinformation. The outbound file transferquestionnaires must be completed.

If Inbound is chosen, the outbound filetransfer questionnaires are not needed.

Type: enumerationRange: Inbound, OutboundDefault: Outbound(not case sensitive)


NN10450-900 06.023 October 2008


.




10 What is the desired statefor the stream?

sba_stream_stateThe stream state controls where therecords are sent.

• ON: records are sent only to the SBA

• OFF: records are sent only to anexisting DIRP system

• BOTH: records are sent to both SBAand to an existing DIRP system

The BOTH state is intended for startupverification of SBA processing againstDIRP processing. Extended use ofthe BOTH state can result in SBAperformance problems.

A system generating more than 175000CDRs per hour does not support BOTH orOFF mode.

Type: enumerationRange: On, Off, Both(not case sensitive)

11 Do you want the filesrenamed with close date?

files_renamed_with_ close_dateThis question applies only if the file formatis DIRP.

Type: BooleanRange: Yes, NoDefault: No(not case sensitive)

12 Do you want to resetDIRP sequence numberat midnight?

This question appears onlywhen you answer No to thequestion, "Do you want thefiles renamed with closedate?"

Reset_DIRP_sequence_number _at_midnightThis parameter enables resetting theDIRP sequence number to zero aftermidnight, before opening a new billing file.



NN10450-900 06.023 October 2008


.




13 Do you want the filesclosed for file transfer andwritetape?

files_closed_on_file_ transferThis question applies only if the file formatis DIRP.


14 Do you want DIRP blocksclosed based on time(applicable only for DIRPfile format)?

This question appears onlywhen file_type=DIRP andrecord_format=BAF orCDR250.

DIRP_blocks_closed_ based_on_timeThis parameter specifies whether theDIRP blocks are to be closed after adefined elapsed time.

SBA block flushing does not supportcustomized DIRP file formats that donot allow hex AA padding at the end ofa block. This type of DIRP file expectsCDRs to be of equal size, and eachblock ends with a special event record.Therefore, GSP and MCI CDR DIRP filesare not supported.

It is recommended that block flushing beused with real-time transfer mechanismssuch as Real-Time Billing (RTB).


15 File DIRP block closuretime limit (in seconds)

This question appearsonly when you answerYes to DIRP_ blocks_closed_base d_on_time(question 13)

DIRP_block_closure_ time_limitThis parameter specifies the maximumamount of time in seconds that a DIRPblock is kept open before it is closed.

Type: IntegerRange: 1 through 120Default: 1


NN10450-900 06.023 October 2008


.


This section contains a series of questionnaires that you must completebefore you configure the SuperNode Billing Application (SBA) on the coremanager for the first time.

The following table contains a list of questions concerning general streaminformation. Record your answers in the spaces provided.

Table 17General stream information


1 What is the name of thisstream?

stream_nameThe stream name on the SBA must matchthe stream name on the DMS Switch.

This name must match a stream name inthe CM table CRSFMT.

Type: string

Range: 1 to 4 characters.


2 What is the desired diskutilization?

desired_disk_utilizationThe percentage of disk utilization thatshould be maintained under normalconditions. The billing application willattempt to keep the disk utilization for thevolume containing this billing data.

Type: integerRange: 10–90

3 Will file transfers for thisstream be initiated by

• SBA (Outbound), or

• the downstreamdestination (Inbound)

file_transfer_modeBilling files always move from SBA tothe downstream destination, but the filetransfers can be initiated by

• SBA (this is called outbound) or

• the downstream destination (this iscalled inbound)

If Outbound is chosen, the SBA must beconfigured with additional file transferinformation. The outbound file transferquestionnaires must be completed.


NN10450-900 06.023 October 2008


.




If Inbound is chosen, the outbound filetransfer questionnaires are not needed.

Type: enumerationRange: Inbound, OutboundDefault: Outbound(not case sensitive)

4 What is the file format ofthis stream?

file_formatThis is the format of the billing files thatSBA creates on the core manager.

Type: enumerationRange: DIRP(not case sensitive)

5 Do you want the file tobe rotated on a regularschedule

Value: Yes or No

6 What do you want theprimary file rotationschedule to be?

file_rotation_schedule1. Rotates files every 24 hours daily (thatis, close files at midnight each day)

2. Rotates files every 12 hours daily (thatis, close files at noon and midnight eachday)

3. Rotates files every 6 hours daily (thatis, close files at 6 am, noon, 6 pm andmidnight each day)

4. Rotates files every hour on the hourdaily (that is, close files at 1 am, 2 am, 3am, daily etc.)

Type: integerRange: 1–4

7 Do you want file sequencenumber to be reset atmidnight?

Value: Yes or No

8 Do you want to close thefile on record criteria?

The number of records, or size in bytes.


NN10450-900 06.023 October 2008


.


AMADNS filename and header valuesThe following table contains a list of configuration questions concerningAMADNS filename and header values. The values selected are used inthe headers and names of the AMADNS files that SBA creates for thisstream. Record your answers in the spaces provided.

The source component id and type are not configured per stream and theirvalues will be used by every enabled AMADNS stream on this SBA.

Table 18AMADNS filename and header values


16 What is the destinationcomponent ID for thisstream?

destination_idType: String

Range: 0000 to 4095Default: 0002

17 What is the destinationcomponent type for thisstream?

destination_typeType: String


18 What is the sourcecomponent id for this SBA?

source_idType: String


19 What is the sourcecomponent type for thisSBA?

source_typeType: String


20 What is the standard filetype for this stream?

standard_file_typeType: Number

Range: 1, 6 to 31Default: 1 (BC), 11 (SMDR)

21 What is the error file typefor this stream?

error_file_typeType: Number

Range: 1, 6 to 31Default: 2 (BC), 12 (SMDR)


NN10450-900 06.023 October 2008


.

File closure limits 205

File closure limitsThe following table contains a list of configuration questions concerninglimits that control automatic closing of billing files by SBA. Note that thefirst of these settings that are reached, triggers the closing of the file.Record your answers in the spaces provided.

Table 19File closure limits


22 Do you want the files forthis stream to close after adefined elapsed time?

close_on_timerThis controls if SBA closes billing filesbased on how long the files have beenopen.

If the answer is Yes, SBA leaves a fileopen no longer than the value specified inquestion #22.

If the answer is No, skip question #22 andgo to question #23.


23 What is the maximum timethat a file can be open forthis stream?

file_open_time_limitThis controls the maximum time SBAkeeps a file open. It is enabled only if Yesis the answer to question #21.

If the answer to question #21 is Yes, enterthe maximum time that a file can be openfor this stream, then go to question #25.

If the answer to question #21 is No, skipthis question and go to question #23.

Type: numberUnits: minutesRange: 5 to 10080Default: 10080


NN10450-900 06.023 October 2008


.


Table 19File closure limits (cont’d.)


24 Do you want Files closedat scheduled intervals frommidnight?

file_closed_at_scheduled_i ntervals_from_midnightThe response to this prompt determinesif SBA closes billing files at scheduledintervals calculated relative to midnight.

If the answer to this question is Yes,you are prompted to choose options, asshown in question #24.

If the answer is No, skip question #24 andgo on to question #25.


25 What is the scheduled fileclosure time option for thisStream?

scheduled_file_closure_tim e_optionChoose a time in response to a prompt todetermine when a billing file is closed, ifyou answer Yes to question #23. Ignorethis question if the answer to question #23is No.

Options:1) Close billing files every 24 hours2) Close billing files every 12 hours3) Close billing files every 6 hours4) Close billing files every 2 hours5) Close billing files every hour6) Close billing files every 30 minutes7) Close billing files every 15 minutes8) Close billing files every 10 minutes9) Close billing files every 5 minutesType: numberRange: 1 through 9Default: 5


NN10450-900 06.023 October 2008


.

File closure limits 207



26 What is the maximumnumber of recordsgenerated each day forthis stream?

records_per_dayThis is used to calculate the maximumnumber of

• records per file, and

• bytes per file

Type: numberUnits: Records per day

27 What is the maximum sizeof a record?

bytes_per_recordThis is used to calculate a value for themaximum number of bytes per file.

Type: numberUnits: Bytes per recordRange: none

28 What is the maximumnumber of records perbilling file for this stream?

records_per_fileThis controls the maximum number ofrecords a billing file can contain beforeSBA automatically closes the file.

The recommended value based on atarget of 300 files a day will be calculatedand provided as the default value, if theaverage number of records per day is oneor more.

Type: numberUnits: records per fileRange: BC 10000 to 50000016384 00SMDR 1000 to 5000001638400

29 What is the maximumnumber of bytes per billingfile for this stream?

bytes_per_fileThis controls the maximum size (in bytes)of a billing file before SBA automaticallycloses it.

A recommended value is calculated withthe following formula:

Records per day * average record size /300 = Bytes per file


NN10450-900 06.023 October 2008


.




Type: numberUnits: bytes per fileRange: BC:1000000 to 104857600SMDR: 100000 to 104857600

30 What is the average recordsize? (not applicable if thenumber of records per dayis 0)

average_record_sizeThis parameter specifies the maximumsize of a record. The default value is 80,but depends on the record type and therecord size as defined on the CM.

This prompt appears when the Numberof records per day parameter is set to avalue other than zero (0)

Disk space requirementsThe following table contains a list of configuration questions related to coremanager and DMS-switch disk space required by the SBA. Record youranswers in the spaces provided.

Disk space sizing requirements are calculated using the DMS switch valuebillable Busy Hour Call Attempts (BBHCA). This value is the total numberof billing-record-generating calls that are processed within the busiest onehour window of a typical 24-hour day.

For information on the BBHCA estimation factor and its use in calculatingrequired disk space, see “Calculation of core manager Disk SpaceRequirements” (page 209) and “Calculation of Disk Space Requirements”(page 210).

Table 20Disk space requirements


31 How much disk spaceon the core manager isneeded for the billing filesfor this stream?

logical_volume_sizeIf the core manager is unable to send thebilling files to the downstream processor,they accumulate on the core managerdisk space. The allocated disk space mustbe capable of holding at least 5 days ofSBA billing files.


NN10450-900 06.023 October 2008


.

Disk space requirements 209


The formula for calculating SBA-requireddisk space on the core manager isdescribed in “Calculation of core managerDisk Space Requirements” (page 209).

Type: numberUnits: MbytesRange: NADefault: noneSpace is allocated in 16 Mb increments.

32 How much disk space isneeded for backup of billingrecords on the DMS Switchfor this stream?

dms_disk_spaceIf the DMS switch is unable to send thebilling records to the core manager, theyare backed up to the DMS disk space.The allocated DMS disk space must becapable of holding at least a one dayaccumulation of SBA billing records.

The formula for calculating SBA-requireddisk space on the DMS switch isdescribed in “Calculation of Disk SpaceRequirements” (page 210).

Type: numberUnits: MbytesRange: NADefault: none

Calculation of core manager Disk Space RequirementsThe formula for calculating megabytes of disk space needed for SBAbilling streams is:

BBHCA * ALCR * 10 hours * CRRD ---------------------------------------------------/ disk utilization 1048576

• BBHCA (Billable busy hour call attempts), multiplied by the ALCR

• ALCR (average length of a call record in bytes), multiplied by

• 10 hours, multiplied by

• • CRRD (Call-record retention days), divided by

• 1048576 (the number of bytes in a megabyte), divided by

• the desired disk utilization.


NN10450-900 06.023 October 2008


.


For this calculation, the desired disk utilization is a percentage that isexpressed as a decimal from 0.1 and 0.9.

This formula must be applied to each billing stream with the total of allstreams representing the total megabytes of disk space required.

The maximum number of files to hold billing records for a billing stream is15,000. The maximum number of files in closedSent directory is 4,000.

The calculation of 10 hours multiplied by BBHCA is an experience-basedfactor that can be used to estimate 24 hours of call traffic. If you know thatthe stream has a high BBHCA for more or less than 10 hours per day,increase or decrease the hours value.

Calculation ExampleAssumptions:

• BBHCA = 150000

• Average length of call records = 85 bytes

• Call retention days = 10

• Desired disk utilization = 0.6 (60%)

Calculation:150000*85*10*10/1048576/.6=2026 Megabytes (2 Gbytes)

Calculation of Disk Space RequirementsRegardless of the volume size determined in this procedure, VSE userscannot configure a backup volume size greater than 2GB. For non-VSEusers, the maximum volume size that can be configured is limited to thesize of the physical disk.

BBHCA * ALCR * 10 hours * CRRD

• BBHCA (Billable busy hour call attempts) multiplied by

• ALCR (Average length of a call record in bytes), multiplied by

• 10 hours, multiplied by

• CRRD (Call-record retention days)

This formula must be applied to each billing stream with the total of allstreams representing the total DMS Switch disk space required.

The calculation of 10 hours multiplied by BBHCA is an experience-basedfactor that can be used to estimate 24 hours of call traffic. If you know thatthe stream has a high BBHCA for more or less than 10 hours per day,increase or decrease the hours value.


NN10450-900 06.023 October 2008


.

Outbound file transfer destinations 211

Calculation ExampleAssumptions:

• BBHCA = 150000

• Average length of call records = 85 bytes

• Call retention days = 2

Calculation:150000*85*10*2/(1024*1024) = 243 Mbytes of disk space

Outbound file transfer destinationsThe following table contains a list of stream configuration questionsrelating to transferring files from SBA to one or more destinations. Thistable requires specific configuration information for the destinations,IP addresses, user IDs, passwords, and directories. The SBA usesthis configuration information to log on , and to transfer the files to thedownstream destination. Record your answers in the spaces provided.

The downstream destination (billing server) must comply with the followingFTP commands and successful return codes, in order for the destinationto successfully receive billing files:

FTP states/commands Return Codes

OPENUSERPASSTYPESTRUCWDSTORCLOSERNTOQUIT

220230230200200, 250250226, 200, 250, 150221250221

Table 21Outbound file transfers


33 What is the destination totransfer the billing files?

destinationThe combination of the values for streamname, file format type, and destinationacts as the key to the schedule tuple.

The destination cannot contain unprintablecharacters or blanks.


NN10450-900 06.023 October 2008


.



Type: numeric StringRange: 1 to 15 charactersDefault: noneExample: Eventure

34 Which protocol is to beused to transfer billing filesfrom the SBA?

protocolFTPW uses the File Transfer Protocol

RFTPW (real time file transfer protocolwrapper) is used for the Real-Time Billing(RTB) application. RFTPW is supportedonly if the RTB application is configured.

SFTPW (secure file transfer protocolwrapper) provides secure outbound filetransfer using the OpenSSH SFTP client.SFTPW is supported only if OpenSSH isinstalled on the Core Manager.

RSFTP (password-based userauthentication) used for secure Real-TimeBilling application when configured withOpenSSH SFTP client on the CoreManager.

The initial host key acceptance of thedownstream processor must be performedmanually before the SFTP is used totransfer files. This must be performed foreach downstream destination.

KSFTP (key-based secure file transferprotocol wrapper) provides secureoutbound file transfer with public keyauthentication, using the OpenSSHSFTP client. KSFTP is supported onlyif OpenSSH is installed on the CoreManager.

RKSFT (key-based authentication) usedfor secure Real-Time Billing applicationwhen configured with OpenSSH SFTPclient on the Core Manager.


NN10450-900 06.023 October 2008


.



sendtape does not support SFTPW/RSFTP.

Type: enumerationRange: FTPW, RFTPW, SFTPW, RSFTP,KSFTP , RKSFT,Default: FTPW(not case sensitive)

35 What is the IP address ofthe primary destination forthis stream?

primary_destinationThe primary destination is the IP addressthat the SBA logs on to, and transfers thebilling files.

Type: IP AddressRange: 0.0.0.0 to 255.255.255.25 5Example: 47.202.35.189

36 What is the port for theprimary destination?

primary_portThe primary port number is associatedwith the primary IP address.

Type: numericRange: SFTPW, RSFTP, KSFTP, orRKSFT: 22, 1025 to 65535Default: 22, for SFTPW, RSFTP, KSFTP,or RKSFTSFTPW or RSFTPExample: 22

FTPW or RFTPW: 21, 1025 to 65535Default 21, for FTPW or RFTPWExample: 22

37 What is the IP address ofthe alternate destination forthis stream?

alternate_destinationThe alternate destination is the IP addressthat the SBA logs into and transfers thebilling files if SBA encounters problems inconnecting to the primary destination.

If there is no alternate destination, makethis entry identical to the primary IPaddress.

Type: IP AddressRange: 0.0.0.0 to 255.255.255.25 5Example: 47.202.35.189


NN10450-900 06.023 October 2008


.



38 What is the Port for thealternate destination?

alternate_portThe alternate port number is associatedwith the alternate IP address.

Type: numeric

Range:

SFTPW or RSFTP: 22, 1025 to 65535

Default: 22 for SFTPW or RSFTP

SFTPW, RSFTP , KSFTP, or RKSFT: 22,1025, 65535

FTPW or RFTPW: 21, 1025 to 65535

Default: 21 for FTPW or RFTPW

Default: 22 for SFTPW, RSFTP, KSFTP,or RKSFT

Example: 22

FTPW or RFTPW: 21, 1025 to 65535

Default 21, for FTPW or RFTPW

39 What is the logon for thedownstream destination forthis stream?

remote_loginThe SBA user ID needed to log on to thedownstream destination, and to transferthe billing files.

Type: stringRange: 1 to 20 alphanumeric charactersDefault: noneExample: amadns (case sensitive)


NN10450-900 06.023 October 2008


.



40 What is the password forthe logon ID in question 24for this stream?

remote_passwordThis is the SBA password used to log onto the downstream destination to transferthe billing files.

Type: stringRange: 1 to 20 alphanumeric charactersDefault: noneExample: abracadabra (case sensitive)

The prompt for this entry is notgenerated if the RKSFT/KSFTPRSFTP(real-time/key-based file transferauthentication) protocol is selected)

41 What is the directorypath on the downstreamdestination where thetransferred billing files areto be stored?

remote_storage_ directoryThis is the full path to the directory on thedownstream destination to which SBAtransfers billing files.

If this value is a period (.), the SBA FTPclient does not issue a change workingdirectory (CWD) command when a filetransfer occurs.

Type: stringRange: 1 to 255 charactersExample: /users/amadns/billing (casesensitive)

42 What is the desired fieldseparator character for thisstream?

field_separatorThis is a single character that the SBAuses to separate the components of billingfile names when they are transferred tothe downstream destination.

If the downstream destination is a UNIXsystem, the recommended field separatoris a period (.); this results in a file namesuch as 020001.030002.00001.01.2.

If the downstream destination is a systemthat does not allow more than one period(.) in the filename, the recommendedfield separator is an underscore (_);this results in a file name such as020001_030002_00001_01_2.


NN10450-900 06.023 October 2008


.



Type: characterRange: any printable characterDefault: . (period)(case sensitive)

43 What is the desiredfilename extension forthis stream?

file_extensionThe filename extension is a shortcharacter string that SBA appends tothe billing file names when it transfersthem to the downstream destination. Theextension can be set as a part of the‘schedule add’ command by providing avalue to the following prompt:

File extension can have between 0and 3 characters. Enter ’Blank’for no file extension. PressEnter to accept ’Blank’. EnterFile_Extension:

Nortel does not recommend the use ofthe .gz file extension when you configurethe outbound file transfer schedule.Use of the .gz extension can make itdifficult for you to distinguish betweencompressed and uncompressed files onthe downstream system.

Outbound file transfer protocolThe following table contains a list of configuration questions relating totransferring files from SBA to the downstream destination. This tablerequires specific configuration limits information to control how the SBAreacts when it encounters problems in connecting to the downstreamdestination. Record your answers in the spaces provided.


NN10450-900 06.023 October 2008


.

Outbound file transfer schedule 217

Table 22Outbound file transfer protocol


44 What is the maximumnumber of times SBAattempts to complete afailed session with thedownstream destination forthis stream?

protocol_max_retriesType: numberRange: 0 to 10Default: 3

45 After a session for thisstream fails, what is themaximum time in secondsthat SBA must wait beforeattempting re-connectionto the downstreamdestination?

protocol_retry_wait _timeType: numberUnits: secondsRange: 1 to 60Default: 1

Outbound file transfer scheduleThe following table contains a list of stream configuration questionsrelating to transferring files from SBA to the downstream destination. Thistable specifically addresses configuration information concerning whenSBA initiates a connection to the downstream destination to transfer billingfiles. Record your answers in the spaces provided.

Table 23Outbound file transfer schedule


46 Are scheduled file transfersto the downstreamdestination required forthis stream?

schedule_activeDetermines if SBA automaticallyinitiates file transfers to the downstreamdestination.

If set to Yes, SBA automatically transfersfiles to the downstream destination at thetimes defined by the answers to questions46, 47 and 48.

If this value is set to No, manual filetransfers can be made using the sendfilecommand.

Type: BooleanRange: Yes, NoDefault: NoIf No, use 0:00 for Answers 46 and 47 and120 for Answer 48.


NN10450-900 06.023 October 2008


.


Table 23Outbound file transfer schedule (cont’d.)


47 When should SBA startinitiating file transfers tothe downstream destinationeach day?

schedule_start_timeDetermines the time of day when SBAstarts file transfers to the downstreamdestination. See the examples followingthis table for more information.

Type: Time of DayUnits: hh:mmRange: 00:00 to 23:59Default: none

48 When should SBA stopinitiating file transfers tothe downstream destinationeach day?

schedule_stop_timeDetermines the time of day when SBAends file transfers to the downstreamdestination. See the examples followingthis table for more information.

Type: Time of DayUnits: hh:mmRange: 00:00 to 23:59Default: none

49 Within the daily timewindow defined inquestions 46 and 47,how often should theSBA transfer files to thedownstream destination?

schedule_intervalThis specifies the interval, in minutes, atwhich SBA is to initiate billing file transfersto the downstream destination. Thisinterval is only active during the window oftime specified by the start time (question46) and stop time (question 47). See theexamples following this table for moreinformation.

Type: NumberUnits: MinutesRange: 5 to 1440Default: 120

The following are some examples that show different answers to questionsfor the start time (question 46), stop time (question 47), and the interval(question 48) and the resulting SBA file transfer times.

If your start time and stop time are identical, then SBA is setup forcontinuous outbound file transfer.


NN10450-900 06.023 October 2008


.

Outbound file transfer schedule 219

StartTime

StopTime

Interval SBA Actions Resulting Transfers

0:00 0:00 240 The SBA transfers files everyfour hours, at the beginningof the hour, starting atmidnight.

The SBA initiates file transfers at 12:00midnight, 4:00 am, 8:00 am, 12:00noon, 4:00 pm and 8:00 pm

22:10 2:00 30 The SBA transfers files everythirty minutes at 10 minutesand 40 minutes after thehour, between 10:10 pm and2 am.

The SBA initiates file transfers at 10:10pm, 10:40 pm, 11:10 pm, 11:40 pm,12:10 am, 12:40 am, 1:10 am and 1:40am

3:15 3:15 300 The SBA transfers files everyfive hours at 15 minutes afterthe hour, starting at 3:15 am.

SBA initiates file transfers at 3:15 am,8:15 am, 1:15 pm, 6:15 pm and 11:15pm.


NN10450-900 06.023 October 2008


.


Configuring SBA backup volumes on a billingstream

Add new SBA backup volumes to a billing stream, or remove SBA backupvolumes from a billing stream.

Procedure steps

Step Action

1 At the MAP

Access the billing level, type

mapci;mtc;appl;sdmbil

2 To add volumes, type

addvol <stream_name> <volume1> ... <volume5>

Repeat this step to add as required.

ExampleCommand to add five volumes

addvol AMA S00DAMA1 S01DAMA2 S00DAMA3S01DAMA4 S00DAMA5

3 To remove volumes, type

remvol <stream_name> <volume1> ... <volume5>

Repeat this step as required.

ExampleCommand to remove five volumes

remvol AMA S00DAMA1 S01DAMA2 S00DAMA3S01DAMA4 S00DAMA5

--End--


NN10450-900 06.023 October 2008


.



<stream_name> The name of the billing stream to which to addthe volume.

<volume1> ... <volume5> The volume name.

You can add, or remove, a maximum of fivevolumes at one time. Separate each entry witha space.


NN10450-900 06.023 October 2008


.


Accessing the MATE

Use this procedure to access the MATE.

Prerequisites• You must have the root user ID and password to log on to the server.

• You may log on to the server as root or emsadmin.

Procedure stepsInstructions for entering commands in the following procedure do not showthe prompting symbol, such as #, >, or $, displayed by the system througha GUI or on a command line.

At the workstation UNIX prompt or VT-100 terminal prompt:

Step Action

1 Log onto the CBM.

2 Get the current hostname by entering:

GetCurrentHostName

Example response:

<CBM hostname>-<unit0 / unit1>

3 Access the Report Registration Menu:

If the hostname returned in step 2 contains "unit0" then theMATE hostname is "unit1"

If the hostname returned in step 2 contains "unit1" then theMATE hostname is "unit0"

4 Determine if the MATE is running by entering:

ping <mate hostname>

The <mate hostname> is the one determined in step 3.

5 If the MATE is not Active, you must access the MATE through alocal VT100 terminal. Go to step 7.

6 Access the MATE using SSH by typing:

ssh root@ <mate hostname>

You can log on to the MATE without a password. To exit theMATE, type > exit to return to the local system.


NN10450-900 06.023 October 2008


.

Procedure steps 223

7 This procedure is complete

--End--


NN10450-900 06.023 October 2008


.


Administration: Creating Disaster Recovery FloppyDisks

The disaster recovery operation is used when it is necessary to restorethe programs and data stored on your OAM&P workstation. The disasterrecovery operation depends on the use of disaster recovery floppy disks.You can use the tape drive application to create the two disaster recoveryfloppy disks required to perform the disaster recovery operation.

To create the disaster recovery floppy disks, perform the following steps:

Procedure stepsAt the OAM&P workstation

Step Action

1 Label two formatted floppy disks as Disaster Recovery Disk 1and Disaster Recovery Disk 2.

2 Insert Disaster Recovery Disk 1 into the A: drive in your OAM&Pworkstation and follow the directions.

ATTENTIONThe disaster recovery floppy disk creation process does not formatthe disks for you, but it does erase all of the data on the disks.Ensure that you have copied important data from the disks beforeproceeding.

ATTENTIONFor more information about creating disaster recovery disks, see thetape drive documentation provided with the OAM&P workstation.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 225

Power-On and boot a Policy Controller unit

This procedure is used to power on a Policy Controller unit that has beeninstalled as a replacement, or was shutdown for any other reason.

This procedure may be used as a standalone task or as part of a higherlevel activity such as part of a dead office recovery activity or softwareupgrade activity.

Prerequisites• If the unit was a replacement unit recently installed, ensure that all

power cabling connections have been properly installed and securedat the rear of the chassis and SAM-F frame.

Procedure stepsAt the front panel of the Policy Controller unit

Step Action

1 If necessary, power on the Policy Controller using the mainpower switch located on the front panel.

2 If desired, at the Policy Controller console, monitor the bootprogress of the unit.

--End--


NN10450-900 06.023 October 2008


.


Viewing the operational status of the NCGL platform

View the operational status of the Nortel Carrier-grade Linux (NCGL)platform to view the service status of the hardware and NCGL operatingsystem using the CS 2000 NCGL Platform Manager.

This procedure provides instructions to determine the service status of theSST NCGL platform only.

Although you can accomplish some activities described in this procedureusing the CS 2000 Session Server Manager, they are described insteadusing the more complete CS 2000 NGCL Platform Manager.

ATTENTIONThis procedure does not describe how to view customer logs or alarms. Fordetailed instructions about viewing customer logs or alarms, see Nortel SessionServer Trunks Fault Management ( (NN10332-911)) .

Procedure stepsAt the CS 2000 NCGL Platform Manager or IEMS client

Step Action

1 At the Communication Server 2000 Session Server Launchpoint, click the Carrier VoIP Communication Server 2000NCGL Platform Manager link.The Platform Main Page menu appears.

2

ATTENTIONThe platform (System) Information page does not updateautomatically. Click the System Information link to update it.

Review the System Information page.

3 Review the Node Maintenance page.

The Node Maintenance page refreshes every 45 seconds.

4 Review the System Status page.

The Chassis Information section.

5 Review the Network Connectivity page.

The Network Connectivity page refreshes every 45 seconds.


NN10450-900 06.023 October 2008


.

Procedure steps 227

Figure 14Crossover and LAN Ethernet cable connections for SST units

6 Review the Disk Services page.

The Disk Services page does not update automatically. Click theDisk Services link to update it.

7 Review the Services page.

The Services page does not update automatically. Click theServices link to update it.

8 Review the Administration page.

The Administration page does not update automatically. Clickthe link to update it.

9 To logout from the CS 2000 NCGL Platform Manager, clickLogout.

--End--


NN10450-900 06.023 October 2008


.


Viewing the operational status of the SIP Gatewayapplication

Use the following procedure to view the service status of the SIP Gatewayapplication.

Procedure stepsAt the CS 2000 Session Server Manager or IEMS client

Step Action

1 At the Communication Server 2000 Session Server Launchpoint, click the Carrier VoIP Communication Server 2000Session Server Manager.

2 Click to open the Session Server, Maintenance, Applicationfolder.

3 Click the SIP Gateway link.

4 Monitor the status of the SIP Gateway application.


NN10450-900 06.023 October 2008


.

Procedure steps 229

The view refreshes according to the value shown in the box atthe bottom of the status section.

5 To increase or decrease the refresh rate, select a different valueand click Refresh Rate.

6 Optionally, you can perform the following service affectingactions:

• Lock the SIP Gateway application

• Unlock the SIP Gateway application

• Suspend the SIP Gateway application

• Unsuspend the SIP Gateway application

• Cold SwAct the SIP Gateway application


NN10450-900 06.023 October 2008


.


7 To view the number of active calls currently handled by theapplication, and the synchronization status of the units, clickQueryInfo.

--End--

Job aidThe following table provides a description of the Node Status fields.

Table 24Node status field descriptions

Field Description

Unit Connection Status Bar Indicates which unit in the node the CS 2000 SessionServer Manager is connected to.

Unit Number Identifies the two units in the node, labeled 0 and 1.

Activity State Indicates which unit is active and which isinactive (standby). Acts as an indirect indicatorof fault-tolerant status; when both units havean Operational status of enabled, the node isfault-tolerant.

Operational State Indicates the service status of each unit, enabled ordisabled.

The following table provides a description of the SIP Gateway applicationStatus fields.

Table 25SIP Gateway application Status field descriptions

Field Indication

Administrative State Locked, Unlocked, or ShuttingDown

Operational State Enabled or Disabled

Procedural Status Terminating or -

Control Status Suspended or -

Use the following table to interpret the SIP Gateway area’s CCITTX.731-style and related DMS-style status indicators.


NN10450-900 06.023 October 2008


.

Job aid 231

Table 26SIP Gateway Maintenance field descriptions and interpretation of service states

AdministrativeState

OperationalState

ProceduralStatus

Control Status DMS styleService States

Locked Disabled in-service Suspended Offline (OFFL)

Locked Enabled in-service in-service Manual Busy(MANB)

Locked Enabled Terminating in-service Manual BusyTransitioning(MANBP)

Unlocked Enabled in-service in-service In Service(INSV)

Unlocked Disabled in-service in-service System Busy(SYSB)

Shutting Down Enabled in-service in-service Going out ofservice(INSVD)

(-) indicates a status of in-service


NN10450-900 06.023 October 2008


.


Verifying synchronization status

Verify synchronization status to determine the synchronization status ofthe two units.

Procedure steps

Step Action

1 At the Communication Server 2000 Session Server Manageror IEMS client, select Communication Server 2000 SessionServer Manager from the launch point menu.

2 Select Session Server > Maintenance > Application > SIPGateway from the left side menu:

3 At the bottom of the SIP Gateway Maintenance panel, locate andclick the QueryInfo button.

4 The synchronization status of the units is displayed at the bottomof the query results panel.

If the units are not in sync, check for alarm conditions.

5 If applicable, return to the higher level task flow or procedure thatdirected you to this procedure.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 233

Booting the XA-Core from a Reset Terminal

Boot the XA-Core from a Reset Terminal to charge the XA-Core from areset terminal display.

ATTENTIONBooting the switch causes the switch to drop all calls.

ATTENTIONAn image loads from a small computer systems interface (SCSI) device. TheSCSI device can be in a disk or a digital audio tape (DAT).

CAUTIONCall your next level of supportContact your next level of support before performing thisprocedure.

CAUTIONExtended service interruptionA longer recovery time occurs for a switch boot from tape thana switch boot from disk.

To minimize recovery time, boot from disk.

CAUTIONExtended service interruptionLog on procedures can vary depending on your officeconfiguration.

If you need additional help, contact your next level of support.

Procedure steps

Step Action

1 See the office records and determine the name of the XA-Corerecording device that contains the last office image file.

ATTENTIONThe XA-Core recording device is a disk drive or a tape drive for adigital audio tape (DAT). Record the name of the XA-Core device.

2 At the XA-Core shelf make sure that the disk drive or the tapedrive that you recorded in step 1 is in-service.

ATTENTIONThe device is in-service when the green light-emitting diode (LED)is on (illuminated).

3 If the device is not in service, contact your next level of support.


NN10450-900 06.023 October 2008


.


4 If the device is in service, at the XA-Core reset terminal overridethe XA-Core reset terminal by typing:

>\OVERRIDE

Example of a reset terminal response

NOW IN SERVICE AFFECTING MODE

5 Boot the XA-Core by typing:

>\BOOT <nn> <s> <p>

Example Response:

>\BOOT 4 F L

Example of system response:

Warning: Boot command will take it out of service.Please confirm ("YES", "Y", "NO", or "N")

Type Y to confirm the command.

6 Monitor the reset terminal display to determine if the switch hasbooted.

ATTENTIONThe reset terminal displays a response to indicate a boot in progress.The response also displays diagnostic messages and alphanumericaddresses. When the switch has completely booted, a promptappears on the display.

One possible example of a reset terminal response

CI:>Another possible example of a reset terminal response

FWCI>

7 If the response is a prompt then go to step 9.

At the MAP terminal

8 If the response has no prompt after approximately 15 minutesthen contact your next level of support.

9 Press the <BREAK> key to determine if you have to log in.

ATTENTIONThe log on message indicates that you have to manually log in. Anautomatic log in can occur if the office parameters have automaticlog in.


Please Login.


NN10450-900 06.023 October 2008


.


10 If log in is not automatic then go to step 11.

11 if the log in is automatic then go to step 15.

12 Login to the MAP terminal by typing:

>LOGIN


Enter User Name

13 Enter your user name by typing:

><user_name>


Enter Password

14 Enter the password by typing:

><password>


SuperNode_1 Logged in on 1997/01/15 at 20:37:17

15 Access the MS Clock level of the MAP display by typing:

>MAPCI;MTC;MS;CLOCK

16 Synchronize the clocks by typing:

>SYNC

17 If the MAP response is not a successful completion, contact yournext level of support.

--End--


<nn> The slot number parameter value to indicate thenumber of the physical shelf slot - 0 to 18.

<p> The position parameter value that indicates theIOP bay - either upper (u) or lower (l).

<password> The name of the password for the account.

<s> The side parameter value to indicate the circuitpack or packlet location in the physical shelf -front (f) or rear (r).

<user_name> The name of the user for the account.


NN10450-900 06.023 October 2008


.


Resetting the Ethernet Routing Switch 8600 using asaved configuration file

The Ethernet Routing Switch 8600 boot command allows you to reset orreboot the system using a saved configuration file.

ATTENTIONYou must be directly connected to the switch to initiate a Boot Monitor session.You can only connect using a Telnet connection if the Boot Monitor CLI isalready active.

Prerequisites• You must have access to the Boot Monitor CLI through a direct

connection to the switch or a Telnet connection. For more informationabout accessing the Boot Monitor CLI, see "Managing the EthernetRouting Switch 8000 Series Switch" using the Command Line InterfaceRelease 3.2,’ 313194-*.

Procedure steps

Step Action

1 At the Boot Monitor CLI issue the boot command by typing

monitor# boot [<file>] [config <value>]

--End--


<file> software image device and file name inthe format [a.b.c.d:]<file> | /pcmcia/<file>| /flash/<file>. The file name, includingthe directory structure, can be up to 1024characters.

config <value> software configuration device and file namein the format [a.b.c.d:]<file> | /pcmcia/<file>| /flash/<file>. The file name, includingthe directory structure, can be up to 1024characters.


NN10450-900 06.023 October 2008


.

Procedure step 237

Restoring a Call Agent

Restore a Call Agent to restore an archived call processing applicationimage from tape.

CAUTIONPossible service interruptionDo not use this procedure when in an emergency situation withno stable call processing application image.

If in a situation without a restartable image, contact NortelGlobal Network Product Support (GNPS) immediate. Attemptingto use this method without a valid call processing applicationimage could fail due to constant resets on the Call Agent.

Procedure step

Step Action

1 Insert the DAT cassette with the image to restore.

2 Restore the image from tape. This step requires root privilege.


3 At the Call Agent Manager log on to the inactive Call Agent andchange directory to the location in which to restore the image.Verify that enough disk space exists to hold the image.


4 Open a file transfer protocol (FTP) session to the CommunicationServer 2000 Core Manager, and transfer the image. It may benecessary to become the super user to transfer the file.


5 At the MAP enter the DISKUT level and use the IMPORTcommand to make the image available to the call processingapplication.


If additional space is needed to import the image, the IMPORTcommand offers to expand the volume.

6 Set the image in the Image Table of Contents (ITOC).


7 The restored image is now available for booting.

--End--


NN10450-900 06.023 October 2008


.


Job aidFigure 15DAT cassette

Figure 16Disk space

Figure 17File transfer


NN10450-900 06.023 October 2008


.

Job aid 239

Figure 18DISKUT level

Figure 19User interface


NN10450-900 06.023 October 2008


.


Restoring Session Server Trunks

Restore Session Server Trunks (SST) to restore a backup copy of criticalfiles to an active unit.

CAUTIONPossible service disruptionPerforming a restore of the SIP Gateway application database tothe active unit is a service affecting activity and can cause datamismatches at the Communication server 2000.

Prerequisites• You must have secure file transfer access, such as scp, to the unit

from a remote host if the backup file is stored on a remote host.

• Backups are also stored locally on each unit in directory/data/bkresmgr/backup.

CAUTIONBoth units must be free of any Session Server Manager patchesbefore the database is restored. This is accomplished byreinstalling the current version of the SIP Gateway applicationsoftware (performed in step 1 below). It is not necessary toremove NCGL patches.

Procedure steps

Step Action

1 For detailed steps for this procedure, see Nortel Carrier Voiceover IP Network Upgrades and Patches (NN10440-450).

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 241

Restoring a database to a Session Server unit

Restore a SIP Gateway application database from a backup copy to theactive Session Server units.

Perform this procedure part of a high-level fault management activity forrestoring a backup copy over a corrupted version of the database, or aspart of a high level upgrade activity from Nortel Session Server Upgrades,(NN10349-461).

ATTENTIONService affectingPerform this procedure on the active unit only. Restoring the SIP Gatewayapplication database to the active unit affects service and can cause datamismatches at the CS 2000 call server.

Prerequisites• Back up the Session Server Trunk before you perform this procedure.

Procedure steps

Step Action

1 At the Session Server CLI or IEMS client

Log on to the active Session Server to which you will restore thedatabase.

2 Change to the root user.

3 Change directories, type

$ cd /opt/apps/database/solid_install

4 Run the database restore script, type

$ ./restorebackup.sh

--End--


NN10450-900 06.023 October 2008


.


Restoring audio files to a UAS node

In the event that a re-installation of a UAS node is required due to anerror condition, audio files must be restored to the unit when it becomesoperational. This procedure allows you to enable audio provisioning to thenode and to specify which audio files are to be restored to it.

ATTENTIONFor more information about re-installation of a UAS node, contact your Nortelservice representative.

Procedure steps

Step Action

1 After the re-installation of the UAS node has been completed,determine whether you want to enable provisioning of the nodeoccur during the next audio distribution cycle or immediately.

2 If you want to enable provisioning of the node to occur during thenext audio distribution cycle, go to step 4.

3 If you want audio provisioning of the node to occur immediately,go to step 5.

4 Perform "Enabling provisioning of a UAS node" in the document(NN10095-511), entitled "UAS Configuration Management," inyour UAS document suite.

ATTENTIONProvisioning of the node will begin during the next audio distributioncycle. The distribution cycle occurs once for each hour.

5 Perform "Provisioning a UAS node" in the document(NN10095-511), entitled "UAS Configuration Management," inyour UAS document suite.

ATTENTIONProvisioning of the node will begin immediately although as muchas a five-minute delay may occur before actual provisioning activitybegins.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 243

Restoring audio files to a Media Server 2000 Seriesnode

In the event that a re-installation of a Media Server 2000 Series node isrequired due to an error condition, audio files must be restored to the unitwhen it becomes operational. This procedure allows you to enable audioprovisioning to the node and to specify which audio files are to be restoredto it.

ATTENTIONFor more information about re-installation of a Media Server 2000 Series node,contact your Nortel service representative.

Procedure steps

Step Action

1 After the re-installation of the Media Server 2000 Series nodehas been completed, determine whether you want to enableprovisioning of the node occur during the next audio distributioncycle or immediately.

2 If you want to enable provisioning of the node to occur during thenext audio distribution cycle then go to step 4.

3 If you want audio provisioning of the node to occur immediatelythen go to step 5.

4 Perform the "Enabling provisioning of a Media Server 2000Series node" (see the Media Server 2000 Series ConfigurationManagement document).

ATTENTIONProvisioning of the node will begin during the next audio distributioncycle. The distribution cycle occurs once for each hour.

5 Perform the procedure "Provisioning a Media Server 2000Series node" (see the Media Server 2000 Series ConfigurationManagement document).

ATTENTIONProvisioning of the node will begin immediately although as muchas a five-minute delay may occur before actual provisioning activitybegins.

--End--


NN10450-900 06.023 October 2008


.


Restoring the APS-specific Oracle database andapplication files

This procedure enables you to restore the APS-specific Oracle databaseand application files (/PROV_data, /audio_files, and /user_audio_files).

The Server Platform Foundation Software (SPFS) base software providesutilities that enable you to restore these files. The "rsimpora" utility restoresthe APS Oracle database files. The "ufsrestore" utility restores the UNIXfile system, including all of the "Root" and "Non-Root" APS database files.The instructions for performing these backup procedures are found in theATM/IP Configuration document (NN10276-500).

In addition to these two utilities, two additional APS utilities and proceduresenable you to restore selected files when only the files required forAPS operation must be restored. The "ips_export_db.sh -restore" utilityrestores only the APS Oracle database. A procedure that utilizes the UNIX"tar" command enables you to restore the non-Root files, "/audio_files,""/PROV_data," "/user_audiofiles," and Root file, "/etc/inet/hosts."

Procedure steps

Step Action

1 Open an xterm window and log in using the "maint" logon andpassword.

2 Become the "root" user by entering

su - root

3 If you want to restore Oracle database files from tape then go tostep 5.

4 If you want to restore Oracle database files from disk then go tostep 10.

5 Insert the appropriate "ORACLE" backup tape into the DDS-3tape drive.

6 Rewind the backup tape by performing the following command


7 Start the restoration of the APS Oracle database from the tapeby entering the following command

ips_export_db.sh -t /dev/rmt/0c -restore

ATTENTIONThis command is entered on a single line.


NN10450-900 06.023 October 2008


.

Procedure steps 245

Messages logging the progress of the restoration display on thescreen. When you are prompted about continuing the restorationeven if the current database will be destroyed, enter "y" (yes).

8 After the restoration of the Oracle database is complete, rewindthe backup tape by performing the following command


9 Eject the backup tape and store it for possible use later. Go tostep 11.

10 Start the restoration of the APS Oracle database from the disk byentering the following command

ips_export_db.sh -diskonly -restore

ATTENTIONThis command is entered on a single line.

Messages logging the progress of the restoration display on thescreen. When you are prompted about continuing the restorationeven if the current database will be destroyed, enter "y" (yes).

11 Insert the appropriate "application file" backup tape into theDDS-3 tape drive.

12 Change directory to the root directory by typing

cd /

13 Rewind the backup tape by performing the following command


14 Restore the application files (/PROV_data, /audio_files, and/user_audio_files) by entering the following command

tar xvf /dev/rmt/0c

15 When the restoration of the application files completes, removethe tape from the tape drive and store for possible use later.Insert another write-enabled DAT tape into the drive to be usedfor the automatic Oracle system back up that runs daily at 1:00a.m.

16 Verify that the application files have been restored by enteringthe following commands

cd /PROV_data

ls -l

The files should display on the screen.

cd /user_audio_files

ls -l


NN10450-900 06.023 October 2008


.



cd /audio_files

ls -l


--End--


NN10450-900 06.023 October 2008


.

Procedure steps 247

Restoring a Multiservice Switch or Media Gatewaydevice

This section describes using Service Data Backup and Restore to restorebacked up service data from the backup site to the Multiservice Switch7400/15000 or Media Gateway 7400/15000.

The Service Data Backup and Restore tools provide three types of restore:

• A full restore restores all backed up service data to the selected deviceor devices.

• An incremental restore restores service data based on a specifieddate. Like the full restore, you can perform an incremental restore oneither one or multiple devices.

• A selective restore restores specific service data that you select. Likethe full restore, you can perform a selective restore on either one ormultiple devices.

ATTENTIONIt is not recommended that an active file (current view) be restored on aMultiservice Switch 7400/15000 or Media Gateway 7400/15000. When yourestore the current view, you may overwrite the existing current view withdifferent content. This action will cause an outage of the Backup and Restoretool.

The following information applies to using the Service Data Backup andRestore tool to perform a restore for Multiservice Switch 7400/15000 orMedia Gateway 7400/15000 nodes:

• “Adding Multiservice Switch 7400/15000 or Media Gateway7400/15000 devices to the restore list” (page 248)

• “Removing Multiservice Switch 7400/15000 or Media Gateway7400/15000 devices from the restore list” (page 248)

• “Defining a specific userid and password for a Multiservice Switch7400/15000 or Media Gateway 7400/15000 in the backup list” (page174)

• “Performing a full restore for a Multiservice Switch 7400/15000 orMedia Gateway 7400/15000 device” (page 249)

• “Performing an incremental restore for a Multiservice Switch7400/15000 or Media Gateway 7400/15000 device” (page250)“Performing a selective restore for a Multiservice Switch7400/15000 or Media Gateway 7400/15000 device” (page 251)

• “Activating the restored Multiservice Switch or Media Gateway data”(page 252)


NN10450-900 06.023 October 2008


.


Adding Multiservice Switch 7400/15000 or Media Gateway7400/15000 devices to the restore list

Use this procedure to add devices to the list of devices that you wish torestore.

Procedure steps

Step Action


2 Select the Restore Configuration tab.



5 From the drop down list, in the right pane, select a restore mode(Incremental or Full).

6 If a specific userid and password is required for the device, enterthe values in the user ID and Password fields and uncheck theUse default checkbox.

7 If you wish to use the default userid and password, click the Usedefaultcheckbox.

8 Click OK.


--End--

Removing Multiservice Switch 7400/15000 or Media Gateway7400/15000 devices from the restore list

Use this procedure to remove devices from the list of devices that youwish to restore.

Procedure steps

Step Action



NN10450-900 06.023 October 2008


.

Performing a full restore for a Multiservice Switch 7400/15000 or Media Gateway 7400/15000device 249


3 In the Device List, select the devices you wish to remove.

4 Click Remove.

5 In the confirmation dialog, select Yes to confirm or No to cancelthe removal.


--End--

Defining a specific userid and password for a Multiservice Switch7400/15000 or Media Gateway 7400/15000 in the restore list

A specific userid and password can be defined when you add the device tothe restore list or you can set it later using the following procedure.

Procedure steps

Step Action



3 Select a device in the Device List section.

4 In the Device Details section, in the Authentication tab, entera userid and password.

5 Clear the Use default checkbox.


--End--

Performing a full restore for a Multiservice Switch 7400/15000 orMedia Gateway 7400/15000 device

Use this procedure to perform a complete system restore of a MultiserviceSwitch 7400/15000 or Media Gateway 7400/15000 device.

Procedure steps


NN10450-900 06.023 October 2008


.


Step Action





5 Click in the Mode title and selectFull from the drop-down list.

6 Click Restore.

7 Activate the restored data by executing the procedure “Activatingthe restored Multiservice Switch or Media Gateway data” (page252).


--End--

Performing an incremental restore for a Multiservice Switch7400/15000 or Media Gateway 7400/15000 device

Use the following procedure to copy files, based on a specific date, fromthe repository back to the Multiservice Switch 7400/15000 or MediaGateway 7400/15000.

Procedure steps

Step Action






6 In the Mode title, select Incremental from the drop-down list.

7 Define a date in the Date column (For example July 4, 2008)


NN10450-900 06.023 October 2008


.

Performing a selective restore for a Multiservice Switch 7400/15000 or Media Gateway 7400/15000device 251

8 Click Restore.

All files with a date and time earlier than the specified date arerestored.



--End--

Performing a selective restore for a Multiservice Switch 7400/15000or Media Gateway 7400/15000 device

Use the following procedure to copy a specific file from the repository backto the Multiservice Switch 7400/15000 or Media Gateway 7400/15000.

Procedure steps

Step Action






6 In the Mode title, select Selective from the drop-down list.

The Configuration column in the table is enabled.

7 Click in the Configuration cell to display a pull-down list thatdisplays all the available views on the Multiservice Switch7400/15000 or Media Gateway 7400/15000.

Note: This step may take a few seconds to completebecause the application must access the Multiservice Switch7400/15000 or Media Gateway 7400/15000 and list all theviews names.

8 Click Restore.


NN10450-900 06.023 October 2008


.




--End--

Activating the restored Multiservice Switch or Media Gateway dataRestore restores the backup configuration data onto the MultiserviceSwitch 7400/15000 or Media Gateway 7400/15000 disk. After a successfulrestore, perform the following procedure to activate the restored data.

Step Action

1 Establish a telnet session to the Multiservice Switch 7400/15000or Media Gateway 7400/15000.

2 Download to the Multiservice Switch 7400/15000 or MediaGateway 7400/15000 any required application software missingfrom the Multiservice Switch 7400/15000 or Media Gateway7400/15000 disk.

3 Enter provisioning mode.

4 Activate the restored view and confirm the activation

5 If required, commit the activated view.


--End--


NN10450-900 06.023 October 2008


.

Activating the restored Multiservice Switch or Media Gateway data 253

Performing a full system restore

Restore system configuration from a backup.

Typical uses of this operation are in the event of one or more of thefollowing:

• An emergency situation requires restoration of system configurationfrom a stored data snapshot.

• You use the file manager function to ensure that there are copies ofthe data snapshot to be restored on both RTC system nodes.

• You make the data snapshot the boot snapshot for both RTC systemnodes.

• You deactivate the linksets and change the path state of theapplication server process (ASP) paths to Down for your system, asappropriate.

• You perform a complete office recovery (COR) on your system, whichmeans that you unseat the RTC system nodes, turn off both powerswitches on the shelf, reseat the RTC system nodes, and then restorepower. Your stored data snapshot is now the running data snapshot.

The following procedures must be executed in the order given to restoredata snapshots stored on your alternate boot server or on the RTC systemnodes.

• “Restoring a system configuration from a data snapshot” (page 254)

• Procedure 2 “Performing a restore operation from a backup CD-RW”(page 257)

CAUTIONRisk of service lossPerforming a COR on your system is service affecting. Nortelrecommends that you do this during off-peak hours and that youensure that a mated system is available.

CAUTIONRisk of service lossDo not power down the shelf when the SCSI disk light on theRTC system node is on. To do so could cause a disk failure.

CAUTIONRisk of equipment damageWear wrist straps, and use standard antistatic precautions.


NN10450-900 06.023 October 2008


.


Restoring a system configuration from a datasnapshot

Use the procedures in this section to restore a system configuration from adata snapshot stored on your alternate boot server.

Procedure stepsAt the OAMP workstation

Step Action

1 Click Administration>file-manager.

on the inactive RTC (slot15).2 If the RTC system node is not locked, click Lock.

3 If the RTC system node is not offline, click Offline.

4 Make note of which RTC system node is the active RTC systemnode. This information is required later in the procedure.

To execute a system COR5 Ensure that the LED is off for the SCSI Disk Drive associated

with this RTC system node before unseating the mission card.

Unseating the RTC card stops the write and read access to theSCSI card to avoid SCSI failure.

6 Unseat the mission card on the inactive RTC by pressingoutward on the top and bottom latches of the mission card torelease it from the Communications Application Module (CAM)shelf.

7 Grasp the top and bottom latches of the mission card and gentlypull it to disconnect it from the associated TM. Do not remove themission card from the CAM shelf.

8 Repeat steps 2 and 3 for the RTC mission card for the activeRTC system node.

9 Turn off both the A and B power switches on the rear of thecontrol CAM shelf of your system.

10 Reseat the RTC mission card for an RTC system by. gentlysliding the mission card back into place. Apply pressure to thefaceplate until you feel resistance.

11 Snap the top and bottom latches of the mission card inward,toward one another. Two audible clicks can be heard when themission card is seated properly.

12 Repeat steps 5 through 7 for the RTC mission card for the otherRTC system node.


NN10450-900 06.023 October 2008


.

Procedure steps 255

13 Return power to the shelf. To do this, turn on both the A andB power switches on the rear of the control CAM shelf of yoursystem.

System start up can take several minutes, depending on theconfiguration of your system.

To view system node status14 Click Configuration>platform>node.

15 Click the Graphical View tab.

16 Confirm that all system nodes are enabled (green status light).

Note: Nortel recommends that you do not attempt anyprovisioning changes until all system nodes recover.If the GUIfails to log in when it is reestablishing the connection, the bootsnapshot may not contain the current user’s user-account.Provide another valid user-account that is configured in thesnapshot.

17 Log into your system.

18 Open the RTC system node administration tab forthe RTC system node in slot 12. To do this, clickConfiguration>platform>node.

19 Click the Graphical view tab, and select slot 12.

If the table is opened before the GUI reconnects to the RTC,the old data is displayed. After the GUI reconnects to the RTC,reload the table.

20 If the data snapshot descriptions match, proceed to step 17. Ifthe snapshot descriptions do not match, return to step 10 andattempt the procedure again. If the procedure has failed twice inrow, contact your next level of support.

For the current active snapshot the snapshot-date andsnapshot-version fields are empty.

21 Update the system time settings in the Set Date/Time window,click Administration> Set Date/Time.

Note: This step is not required if simple network time protocol(SNTP) is enabled for this system.

22 This procedure is complete

--End--

Use the following procedure to perform a restore backup from a backuptape


NN10450-900 06.023 October 2008


.


Procedure 1Performing a restore operationATTENTIONThis procedure can overwrite existing data files on your workstation. Make sureyou have a current data backup before you begin this procedure.

At the Windows-based OAMP workstation

Step Action

1 Insert the tape containing the data that you want to restore.

2 Double-click the Backup Exec icon on the desktop if you arerunning a Veritas program or the Colorado Backup II icon if youare running a Colorado program.

3 Select Restore files using the Restore Wizard.

4 Click Ok.

5 Click Next.

6 Select from media in the device.

7 Click Next.

The system loads the information from the backup tape.

8 Select the backup date and time for the data that you want torestore.

9 Click Ok.

The system loads the information from the backup tape.

10 Click the + button on the tree control to expand the tree box nextto the C: drive. Select any directories that you want to restore.

11 Click Next.

12 Click Next a second time.

13 Select Always replace the file on my computer.

14 Click Start.

The system restores the backup data.

15 Click Ok.

16 The data restore procedure is complete.

--End--

ATTENTIONThis procedure can overwrite existing USP data files on your workstation. Makesure you have a current data backup before you begin this procedure.


NN10450-900 06.023 October 2008


.

Procedure steps 257

Before performing this procedure, ensure that the ABS is installed in theworkstation.

The root privilege is required to perform this procedure.

Procedure 2Performing a restore operation from a backup CD-RWAt the Solaris-based OAMP workstation

Step Action

1 Remove the current USP data by entering the followingcommand at the prompt:

rm -Rf <USP data directory>

Examplerm -Rf /opt/usp/ntssgusp/abs/sites

2 Insert the CD-RW containing the USP data that you want torestore into the CD-ROM drive.

3 Go to the partition where the ABS is installed by entering thefollowing:

cd <partition>

Examplecd /

The ABS is installed in the root partition by default.

4 Restore the USP data by entering the following command:

ufsrestore xf /<cdrom directory>/<dumped filename>

where

<cdrom directory> is the directory where theCD-ROM is mounted.

Exampleufsrestore xf /cdrom/cdrom0/usp_data_20051115.dmp

The ABS is installed in the root partition by default.

The following is displayed; enter what is in bold text whenprompted:

You have not read any volumes yet. Unless you know whichvolume your file(s) are on you should start with the last volumeand work towards the first.

5 Enter "1" in response to the promp as shown:

Specify next volume #:


NN10450-900 06.023 October 2008


.


1

If the data files are large, it can take several minutes to restorethe data.

6 Enter "n" in response to the promp as shown:

set owner mode for ’.’?[yn]

n


Directories already exist, set modes anyway? [yn]

n

8 Return to the root directory by entering the following command:

cd /

9 Restore the DHCP configuration data by entering the followingcommand:

ufsrestore xf /<cdrom directory>/<dumped filename>

where

<cdrom directory> is the directory where theCD-ROM is mounted.

Exampleufsrestore xf /cdrom/cdrom0/dhcp_20051115.dmp

The following is displayed; enter what is in bold text whenprompted:

You have not read any volumes yet. Unless you know whichvolume your file(s) are on you should start with the last volumeand work towards the first.

10 Enter "1" in response to the promp as shown:

Specify next volume #:

1

If the data files are large, it can take several minutes to restorethe data.


set owner mode for ’.’?[yn]

n


Directories already exist, set modes anyway? [yn]


NN10450-900 06.023 October 2008


.

Procedure steps 259

n

13 Copy the NFS configuration file back by entering the following:

cp /<cdrom directory>/dfstab /etc/dfs/dfstab

Examplecp /cdrom/cdrom0/dfstab /etc/dfs/dfstab

14 Restart the NFS server by entering the following commands:

/etc/init.d/nfs.server stop

/etc/init.d/nfs.server start

15 Remove the CD-RW from the CD-ROM drive and return it to itsregular storage location.


--End--


NN10450-900 06.023 October 2008


.


Restoring Core Element Manager data

Restore Core Element Manager (CEM) data to backup the CEM.

Perform this backup procedure through the Synchronous backup restoremanager (SBRM). For more information, see .

The information needed by the Core Element Manager to restore data islocated in /opt/nortel/cem/data/coreEMS/configBackup.

Prerequisites• The user must have root user privileges to perform this procedure.

Procedure steps

Step Action

1 At your workstation, open a Telnet session to the server, type

> telnet <server>


3 Change to the root user, type

$ su -


5 Make sure that the /opt/nortel/cem/data/coreEMS/configBackupdirectory contains the following files, type # ls /opt/nortel/data/coreEMS/configBackup

• data_dir

• ldapConfig.tar

• nodes.tar

• server

6 Make sure that CEM is not running, type

# servquery -status -group CEM

Example response

CEM server STOPPED

7 If the CEM server is running, stop the CEM server, type

# servstop CEM

Example response


NN10450-900 06.023 October 2008


.


CEM server successfully stopped

8 Run the restore script, type

#/opt/nortel/cem/data/coreEMS/nodes/server/bin/postRestore.sh

--End--


<server> The IP address or host name of the serverwhere IEMS resides.


NN10450-900 06.023 October 2008


.


Restoring the central security server

Restore the central security server to restore the security server from abackup file.

ATTENTIONSSL uses certificates to ensure security. Certificates from one server cannot beused on another server. If you want to take a back up file from an SSL serverand restore it to a different server, see , after you complete the restore. Run ascript to set up IS authentication, session, and policy traffic to operate underSSL.

The servers in the same high availability cluster can use the same SSLcertificate.

If the restored IS SSL certificate is expired, see after you complete the restore.

Prerequisites• You must have a backup tar file.

• You must have root user privileges to perform this procedure.

Procedure steps

Step Action

1 At your workstation, open A Telnet session to the server, type

telnet <server>

If you are upgrading the active server, Telnet to the activeserver. If you are upgrading the inactive server, Telnet to theinactive server.


3 Change to the root user, type

su - root


5 Stop the security services, type # servstop RADSVR and pressEnter.

6 Type # servstop IS and press Enter.

7 Type # servstop WEBSERVICES and press Enter.

8 List the available security server backup files and determine thebackup file to be restored by typing


NN10450-900 06.023 October 2008


.

Procedure steps 263

# ls /data/bkresmgr

and press Enter.

Note the name of the security server backup file you intend torestore. You will need this information in a later step.

9 List the available security server backup files and determine thebackup file to be restored by typing

# ls /data/bkresmgr

and press Enter.

The format of the security server backup files are<data><time>backupSS2.0<host_name>.tar

The name of the security server backup file you intend to restore.

10 Change directories, type

# cd /opt/nortel/applications/security/current_s1isext/swmgmt/bin

11 Create a backup of the nsswitch.conf file, type

# cp /etc/nsswitch.conf /etc/nsswitch.conf.<DATE>

Record the name of the nsswitch.conf.<DATE> file. This file isrequired after the restore operation.

12 Disable SAML, type

# cp /etc/nsswitch.conf.files /etc/nsswitch.conf

13 Perform the restore operation, type

# ./brr_security.sh -restore /data/bkresmgr/<date><time>backupSS2.0<host_name>.tar

14 Restart the security services, type # servstart and pressEnter.

15 Type WEBSERVICES and press Enter.

16 Type # servstart IS and press Enter.

17 Type # servstart RADSVR

18 Enable SAML by typing

# cp /etc/nsswitch.conf.<DATE> /etc/nsswitch.confand press Enter.

19 If you restored the back up image from a different server with adifferent certificate, or if the restored certificate is expired, see toreplace the invalid or expired certificate on the IEMS server.

20 Clone the active server to the inactive server. For details, seeClone the active server to the inactive server. For details, see .


NN10450-900 06.023 October 2008


.


21 Clone the active server to the inactive server. For details, see .

--End--


<DATE> The backup file created or should be restored.

<date><time> The backup file to be restored.

<host_name>.tar The name of the security server backup file youintend to restore.

<server> The IP address or host name of the serverwhere IEMS resides.


NN10450-900 06.023 October 2008


.

Procedure steps 265

Performing a full restore of the software from S-tape

Restore the core manager software load from the system image backuptape (S-tape).

Prerequisites• You must be a trained AIX system administrator who has root user

privileges to the core manager.

• You must mirror all volume groups on the core manager before youperform this procedure. If you perform this procedure when diskmirroring is not at the Mirrored state, the system displays an errormessage.

• If your system includes the SuperNode Billing Application (SBA), youmust use tape drive DAT0 to perform this procedure.

Procedure steps

Step Action

1 At the local VT100 console

Log into the SDM CS 2000 Core Manager as a root user.

2 Access the maintenance interface, type

# sdmmtc

3 Determine if the core manager maintenance interface isavailable.

If core manager maintenance interface is available, go to thenext step.

If core manager maintenance interface is not available, go tostep 10.

4 Access the administration level, type

admin.

5 Perform a full restore of the core manager, type restore

Sample responseSelect the tape drive you want torestore from, or type Abort to abort:Enter 0 for the tape drive in the main chassis slot2.Enter 1 for the tape drive in the main chassis slot3.

6 Type the number for the tape drive to use.


NN10450-900 06.023 October 2008


.


To use the tape drive in slot 2, type 0

To use the tape drive in slot 13, type

1

Sample responseInsert the backup-tape into the tapedrive in the main chassis slot 2. When completedpress [Enter] to start the restore.

7 When prompted, type

y

Sample response Insert the backup-tape into the tapedrive in the main chassis slot 2. When completedpress [Enter] to start the restore.

8 Insert the backup S-tape into the specified tape drive.

Wait until the tape drive stabilizes (yellow LED is off) before youproceed.

9 Press Enter to start the restore process. Go to step 16.

10 At the core manager

The core manager maintenance interface is not available (step2), make sure that one of the core manager tape drives (slot 2 or13 in the main chassis) contains the system image backup tape(S-tape).

Use tape drive DAT0 (option to perform a full restore from anS-tape) if your system also includes SBA.

At the Modular Supervisory Panel

11 Reboot the core manager.

If the prompt is available at a local VT100 console, reboot thecore manager, type shutdown -Fr.

If the prompt is not available, reboot the core manager by turningthe power off, then on. Use the MSP breaker that supplies powerto the core manager to turn the power off and on.

At the local VT100 console

12 When the system COLD Start message appears, interrupt theboot process. Interrupt the process by press Esc twice.

The system takes about 4 minutes to initialize.

Proceed according to he system prompt.

13 If the prompt is FX-Bug and you are in a menu, type the numberto select Go to System Debugger.

Go to step 15.

14 If the prompt is FX-Diag, Switch the directory to FX-Bug, type

> sd


NN10450-900 06.023 October 2008


.

Procedure steps 267

15 View the input/output devices on the core manager to verify theaddress of the tape drive from the FX-Bug prompt, type

Fx-Bug> ioi

16 If the FX-Bug prompt appears (response from step 12), type

Fx-Bug> pboot <address_for_Archive_Python>

Valid choices are:

pboot 1 50 if the tape drive is located in slot 2

pboot 6 50 if the tape drive is located in slot 13

Wait for the system to reboot. This takes approximately 4minutes.

17 After the system reboots, you are prompted to define the consolesetting and the language setting.

Define the console setting, type 1. The system does not echoyour entry.

In case of any failures, contact your next level of support.

18 To select the language setting, type 1.

The Welcome to Base Operating System Installation andMaintenance menu appears.

19 Type the number to select the Change/Show InstallationSettings and Install menu option.

The System Backup Installation and Settings menu appears.

Sample response

System Backup Installation and SettingsEither type 0 and press Enter to install with thecurrent settings, or type the number of the settingyou want to change and press Enter.Setting: CurrentChoice(s):1 Disk(s) where you want to install hdisk0...Use Maps No2 Shrink File System No>>> 0 Install with the settings listed above.

The elipses (...) under Current Choice(s) indicates that morethan one disk is currently in use.

20 The default disk hdisk0, which is located in slot 2 of the mainchassis. If your core manager contains one disk drive in eachdomain of the main chassis, accept the default setting. If youhave additional disk drives, you may wish to change the settings.

21 If you want to accept the default setting, go to step 27.

If you want to change the setting, type


NN10450-900 06.023 October 2008


.


> 1

The Change Disk(s) Where You Want to Install menu appears,with a list of all the available disks on which you can install thesystem backup image. The >>> symbols identify the currentlyselected disks.

22 You must install the system backup on one disk in each domainto achieve fault-tolerant operation. Valid choices in responseto the prompt in the Change Disk(s) Where You Want toInstall menu are, are hdisk0 and hdisk5. The rootvg disks forinstallation must have location codes

c1-f2-00-0 for domain 0

c1-f13-00-0 for domain 1

23 Type the number to select one or more disks, and press Enter.

To undo a disk you selected, type the number again and pressEnter.

After you select the disk, the System Backup Installation andSettings menu appears.

24 At the prompt. type

0 and return to step 20.

25 To accept the default setting (step 21), type

0

The restore process begins, and takes at least 30 minutesto complete. The progress monitor shows the approximatepercentage of the tasks completed, and the elapsed time.

If an error message appears at the end of the restore process,datavg did not import successfully. Contact the next level ofsupport.

If you are performing this procedure as part of removing an I/Oexpansion chassis (Upgrades, (NTRX50EC)) you must manuallyreboot the system. At the FX-bug> prompt, type pboot 1 0.

At the core manager

26 Remove the S-tape from the tape drive and store it in a securelocation.

At the local or remote terminal

27 Log in to the core manager as a root user, press Enter when yousee the TERM=(vt100) prompt.

28 Start the core manager maintenance interface, type # sdmmtc

29 Access the storage level, type

> storage

30 Determine the mirror status of the disks.


NN10450-900 06.023 October 2008


.

Procedure steps 269

ATTENTIONIf the status of the disks is Integrating or Not Mirrored, stopthis procedure. You cannot continue until the status is Mirrored. Ifnecessary, contact your next level of support.

31 Access the LAN level, type

> lan

32 Check the state of DCE.

Sample response

DCE State: SysB

33 Access the application (APPL) level to check the state of anyDCE-based applications, type

> appl

Sample response

# Application State1 Table Access Service .2 Log Delivery Service .3 OM Access Service .4 Secure File Transfer Fail5 Enhanced Terminal Access Fail6 Exception Reporting FailApplications showing 1 to 6 of 6

ATTENTIONDCE and DCE-based applications can fail if the key tab files restoredfrom tape contain obsolete keys.

34 If the DCE state is SysB at the LAN menu level of the RMI(response from step 32), and the logs indicate an error with thesecurity client service in DCE, restore the service.

35 If the state of some DCE-based applications Fail (responsefrom step 32), try to restore them by busying (BSY) and returningto service (RTS) the applications from the SDM APPL level.

36 If that , restore them by performing the procedure to addthe application server to the DCE cell in the ConfigurationManagement document.

37 You must create a new system image backup tape.

--End--


NN10450-900 06.023 October 2008


.


Performing a partial restore of the software fromS-tape

Perform a partial restore of the software from S-tape to restore individualfiles or sets of files from the system image backup tape (S-tape).

Prerequisites• You must be a user authorized to perform fault-admin actions.

CAUTIONPossible loss of dataUse this procedure at the discretion of the system administrator.

Perform a partial restore only if you are familiar with the files, and knowexactly which files are to be restored. If you restore the wrong files, youmay inadvertently corrupt core manager software.

ATTENTIONThis procedure must be performed by a trained AIX system administratorauthorized to perform fault-admin actions.

ATTENTIONAll volume groups on the core manager must be fully mirrored (Mirrored) beforeperforming this procedure. If you attempt to perform this procedure when diskmirroring is not Mirrored, an error message is displayed on the screen.

ATTENTIONIf your system includes the SuperNode Billing Application (SBA), use tape driveDAT0 to perform this procedure.

ATTENTIONInstructions for entering commands in the following procedure do not show theprompting symbol, such as #, >, or $, displayed by the system through a GUIor on a command line.

Procedure steps

Step Action

1 At the core manager insert the S-tape into the tape drive youselected.



NN10450-900 06.023 October 2008


.

Procedure steps 271

2 At the local or remote VT100 console when you are ready tocontinue this procedure, enter:

y

The contents of the S-tape are listed on the screen. When thelisting is complete, the system prompts you to return to theSystem Image Backup and Restore Menu.

Example response:

Would you like to return to the previous menu?( y | n )


y

4 If you are listing the contents of the tape to verify that the file hasbeen restored then go to step 14.

5 If you are listing the contents of the tape to verify the file name ordirectory that you wish to restore go to step 6.

6 From the System Image Backup and Restore Menu, select"Restore Files from the System Image Tape (S-tape)":

4

7 After you select option 4, you are prompted to select the tapedrive.

Example response:

Select a tape drive you wish to use:

Enter 0 to return to previous menuEnter 1 for tape drive DAT0 in MainChassis-Slot 2Enter 2 for tape drive DAT1 in MainChassis-Slot 13( 0, 1 or 2 ) ==>


8 Enter the number for the tape drive you want to use (1 or 2).

ATTENTIONIf your system includes SBA, and you still wish to use tape driveDAT1 (option 2), the following message is displayed:

Example response:

You have selected DAT 1. This is the default DAT drivefor the Billing application, and may currently be in usefor the emergency storage of billing records.


NN10450-900 06.023 October 2008


.


If you continue to use DAT 1, make sure that the correcttape is in the drive, and that billing records will not belost during the backup/restore operation.

Do you wish to continue with DAT 1? ( y | n )

• if you wish to continue using DAT1, enter y

• I If you do not wish to use DAT1, enter n

The system prompts you to return to the System Image Backupand Restore Menu if you do not wish to use DAT1.

9 After you select the tape drive, you are prompted to insert theS-tape into the appropriate tape drive. A warning is displayedadvising that this procedure must only be completed by qualifiedcore manager system administrators. The warning also advisesthat files and directories must be entered exactly as they appearin the file listing. Insert the S-tape in the appropriate tape drive.


Example response:

Are you ready to enter the name of the file or directory?( y | n )

10 Continue this procedure:

y

Example response:

Enter the name of the directory or file that you wish torestore as./<your-full-path>/<your-file-or-directory>.Note: Tape processing may take a few minutes tocomplete. A log file /tmp/s-tape.restore will becreated.

==>

11 Enter the full path name of the directory or file that you wish torestore, exactly as shown in the file listing, including "/" at thebeginning.

ATTENTIONA log file /tmp/s-tape.restore is created when the restore iscompleted.

ATTENTIONAn error message is displayed if the restore is unsuccessful. If thisoccurs, go to step 25.


NN10450-900 06.023 October 2008


.

Procedure steps 273

12 During the restore process, the screen does not display anyadditional information. When the file restore is complete, the fileyou have restored is displayed. The system then prompts you toreturn to the System Image Backup and Restore Menu.

Example response:

Would you like to return to the previous menu? ( y | n )

ATTENTIONIf the restore has failed, an error message is displayed before theprompt, advising you to list the contents of the tape, and perform theprocedure again.


y

14 Determine if the restore was successful. The system displaysthe file that you have restored. You may also wish to view thes-tape.restore file or list the files on the S-tape.

15 If the restore is successful then go to step 25.

16 If the restore failed then contact your next level of support

17 If you wish to view the s-tape.restore file then go to step 18.

18 Exit the System Image Backup and Restore Menu:

0

19 Exit the maintenance interface:

quit all

20 Access the s-tape.restore file:

cd /tmp

21 Scroll through the file:

more s-tape.restore

22 Continue pressing the Enter key until the files that you haverestored, and the date of the restore, are displayed.

23 If successful then go to step 26.

24 If failed then go to contact your next level of support.

25 Exit the System Image Backup and Restore Menu:

0

ATTENTIONIf you then wish to exit the maintenance interface, type quit all andpress the Enter key.


NN10450-900 06.023 October 2008


.


26 At the core manager remove the S-tape and store it in a secureplace.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 275

Recovering backup files from lost backup volumes

Recover backup files from lost backup volumes swaps back old volumesas the primary backup volumes.

You must recover backup files from lost backup volumes if the SBA cannottrack backed up files when the SWACT and RESTART processes occurwhen you perform procedure "Configuring SBA backup volumes" in theAccounting document.

Prerequisites• You must have the names of the swapped out volumes.

For more information see, "Configuring SBA backup volumes on thecore" in the Accounting document.

Procedure steps

Step Action

1 Post the billing stream.

> mapci;mtc;appl;sdmbil;post <stream_name>

2 Quit back to the appl;sdmbil level.

> quit

3 Confirm that the names of the billing stream’s existing backupvolumes are the swapped in volumes you created earlier.

> conf view <stream_name>

ATTENTIONSBA does not support the configuration of more than one billingstream at a time from multiple workstations. The last billing streamthat is configured is the one that is saved.

4 Read the notes you made when you performed the procedure,"Configuring SBA backup volumes on the core" in the Accountingdocument, to confirm that the backup volumes that you listed instep 3 are the backup volumes you created with that procedure.

5 If the backup volume names are the backup volume namesconfigured when you performed the procedure then continue withstep 7.

6 If the backup volume names are not the backup volume namesconfigured when you performed the procedure then determineif someone else reconfigured the backup volumes before youcontinue with step 7.


NN10450-900 06.023 October 2008


.


7 Access the billing level.

> mapci;appl;sdmbil

8 Configure the billing stream of the logical volumes you createdwhen you performed the procedure, "Configuring SBA backupvolumes on the core" in the Accounting document.

> addvol <stream_name> <volume1> ... <volume5>

Example Response:

To add five volumes, the command is:

addvol AMA S00DAMA S01DAMA S02DAMA S03DAMAS04DAMA

Repeat this step until all of the volumes have been added to thestream.

9 Exit back to the command prompt.

> quit all

ATTENTIONThe non-empty backup volumes are automatically detected bythe SBA audits. In addition, the SBA places the billing stream intorecovery mode and the volumes from the original backup volumes aresent to the core manager.

ATTENTIONYou must provide, to all operating company personnel who work onthe core, the names of the old and new backup volumes and theprocedure you used to swap the volumes. They must be made awarethat any restarts or switch of activity (SwAct) that occur before thebilling stream returns to normal mode can cause a serious loss ofbilling records.

The mode of the billing stream must be closely monitored to ensurethat it returns to normal mode without an intervening RESTART orSwAct.

--End--


<stream_name> Name of the billing stream.

<volume5> Volume name. Up to five volumes (with eachentry separated by a space) can be added atone time.


NN10450-900 06.023 October 2008


.

Procedure steps 277

Restoring the Oracle/MySQL data on an SPFS-basedserver

Restore the Oracle/MySQL data from a backup DVD on a Server PlatformFoundation Software (SPFS)-based server, Sun Netra 240). Also use thisprocedure to restore the data that was automatically backed up to a file onthe server by the backup restore manager.



• Core and Billing Manager (CBM)

• Communication server 2000 Management Tools

• Communication server 2000 SAM21 Manager





Although the MDM, MG 9000 Manager and CBM do not host a database,this restore procedure still applies to these components as it can be usedto recover other critical files.

Prerequisites• You need the DVD on which you backed up the Oracle/MySQL data. If

the data was backed up by the backup restore manager, you need thename of the file located in directory /data/bkresmgr/backup.

Procedure steps

Step Action

1 Insert the DVD on which you backed up the Oracle/MySQL data,into the drive.

2 Log on to the server.

> telnet <server>

Press the Enter key.



NN10450-900 06.023 October 2008


.



$ su -



6 Verify the permissions on the restore log directory (bkslog).

# ls -alrt /var/opt/nortel


Example response:

total 22lrwxrwxrwx 1 root succssn 28 Dec 22 2003 gwc ->/net/47.141.126.131//swd/gwc

drwxrwxr-x 4 root other 512 Dec 22 2003 .drwxr-xr-x 7 root sys 512 Sep 10 12:41 ..drwxr-xr-x 2 oracle oinstall 512 Dec 8 15:58 dbdrwxrwxrwt 2 root other 6656 Dec 15 19:56 bkslog

7 If the permissions of bkslog are drwxrwxrwt then go to step 10

8 If the permissions of bkslog are not drwxrwxrwt, then change thepermissions of bkslog.

# chmod 1777 /var/opt/nortel/bkslog


9 Determine if server applications have been stopped.

# servquery -status all


10 If not already done, stop the server applications that run on theserver.

11 For Communication server 2000 Management Tools serverapplications see Stopping the SESM server application, Stoppingthe SAM21 Manager server application, Stopping the APS serverapplication, Nortel ATM/IP Solution-level Administration andSecurity ( (NN10402-600)) , .

12 For MG 9000 Manager and mid-tier server application see NortelMG 9000 Fault Management ( (NN10074-911)) , Nortel MG 9000Administration and Security ( (NN10162-611)) .

13 For IEMS server application see Stopping the NPM serverapplication, Nortel IEMS Administration and Security ((NN10336-611)) .

14 Verify the permissions, owner and group of /data/oradata bytyping:

#ls -l /data


NN10450-900 06.023 October 2008


.

Procedure steps 279


Example response:

drwxr-xr-x 7 oracle oinstall 512 Oct 16 18:13 oradata

15 Restore the database from backup DVD.

$ /opt/nortel/sspfs/bks/rsdata


Example response:

Done patching databaseDATABASE re-started successfullyRestoring critical files from opt/critdata.cpio2384 blocks!! WARNING !! Restoring /etc/passwd, /etc/shadow or/etc/group files could cause problems with respect topasswords, file’s ownership. Do you want to restorethese files (y/n):[y]n

16 The DVD should eject automatically. Remove the DVD from thedrive and proceed to the next step.

17 Restore the database from the backup file.

$ /opt/nortel/sspfs/bks/rsdata -f /data/bkresmgr/backup/<filename>

and press the enter key.

18 If an alarm appears, or the database did not restore properly,contact Nortel. Otherwise, continue with the next step.

19 If no alarm appears, and you do not need to restore thecertificate, continue with the next step.

20 If no alarm appears, and you need to restore the certificate,determine if WebPKProxy is configured.

# ls /data/pkclient/certificates


21 If the files CA1_Cert.pem, CA2_Cert.pem, and TRUSTED_Cert.pem do not exist, continue with the next step.

22 If the three files listed in step 17 are associated with thismachine, reconfigure the WebPKProxy as follows.

23 From the CLI, select Configuration ---> Security Services,Configuration ---> PKManager Certificate, Installation --->install_certs (Install Certificates supplied by PKManager).

24 Wait for the script to complete. Verify that no errors aredisplayed.


NN10450-900 06.023 October 2008


.


25 From the CLI, select Configuration ---> Security Services,Configuration ---> WebPKProxy/PKClient, Configuration--->register_pkclient.

26 Enter the host name of the Certificate Manager.

27 The Certificate Manager box must be fully functional for this stepto succeed.

Wait for the script to complete. Verify that no errors aredisplayed.

28 Start the server applications that run on the server.

If one or more applications do not start, contact Nortel forassistance.

If the files /etc/passwd, /etc/group were backed-up previously,the process prompts the following warning message:

WARNING !! Restoring /etc/passwd, /etc/shadow or/etc/group files could cause problems with respect topasswords, file’s ownership. Do you want to restorethese files (y/n):[y]

Select:n - No, if you have changed some passwords, added/changednew users/groups since the last backup.y - Yes, otherwise.

29 For Communication server 2000 Management Tools serverapplications see Starting the SESM server application, Startingthe SAM21 Manager server application, Starting the APS serverapplication, Nortel ATM/IP Solution-level Administration andSecurity ( (NN10402-600))

30 For MG 9000 Manager and mid-tier server applications seeNortel MG 9000 Fault Management ( (NN10074-911)) , NortelMG 9000 Administration and Security ( (NN10162-611)) .

31 For IEMS server application see “Starting the NPM serverapplication” (page 297) Nortel IEMS Administration and Security( (NN10336-611)) : "Starting the IEMS server or changing theIEMS server mode to standby."

--End--


<filename>

The name of the backup file created by the backup restoremanager.


NN10450-900 06.023 October 2008


.

Procedure steps 281

Clearing the MATE alarm

Use this procedure to clear the MATE alarm.

Procedure stepsAt the workstation UNIX prompt or VT-100 terminal prompt:

Step Action

1 Log in to the CBM using the root or emsadmin user ID andpassword.

2 Start the cbmmtc tool by typing:

# cbmmtc

Check the MATE column on the banner. If the state is not "."(dot), this indicates the presence of an alarm.

3 Access the MATE by performing the procedure “Accessing theMATE” (page 222).

4 Clear the alarms by performing the procedure “Clearing theMATE alarm” (page 281).

5 Check to see if all fault conditions have now cleared.

querycbm flt

6 Log out of the MATE.

--End--


NN10450-900 06.023 October 2008


.


Stopping the SAM21 Manager server application

Stop the SAM21 Manager server application to end the SAM21 Managerserver application on the SPFS-based server that is hosting theCommunication Server 2000 Management Tools.

Procedure steps

Step Action

1 At your workstation, establish a logon session to the server,using one of the following methods

In a two-server configuration, log in to the active server using thephysical IP address of the active server, and ensure you are onthe active server using the ubmstat command.

2 Verify the status of the SAM21 Manager server application bytyping:

# servman query -status -group SAM21EM


3 If SAM21EM is running continue with the next step and ifSAM21EM is not running then you have completed thisprocedure.

4 Stop the SAM21EM server application by typing:

# servstop SAM21EM


5 Verify the SAM21EM server application stopped by typing:



Example response:

# servman query -status -group SAM21EMExecuting: /opt/servman/bin/servquery -status -groupSAM21EMSAM21EM===============================

Executing : /opt/nortel/sam21em/bin/healthSuccession SAM21 Element Manager version: SAM21EM_10_039_0Current status of the Succession SAM21 Element Manager:SNMP Access Gateway is not running.SAM21 Element Manager Server is not running.


NN10450-900 06.023 October 2008


.

Procedure steps 283

6 If applicable, return to the high level task or procedure thatdirected you to this procedure.

--End--


NN10450-900 06.023 October 2008


.


Stopping the SESM server application

Stop the Succession Element and Subelement Manager (SESM)server application to end the SESM server application on the CS 2000Management Tools server.

Prerequisites• You must be logged in to the active server as the root user using telnet

(unsecure) or ssh (secure).

Procedure stepsATTENTIONIn a two-server configuration, you must perform this procedure on the activeserver.

Step Action

1 Ensure you are logged in to the active server.

ubmstat

If the server response is ClusterIndicatorACTthen you areon the active server.

If the server response is ClusterIndicatorSTBY then youare on the inactive server. You must be logged in to the activeserver.

2 Verify the status of the SESM server application by typing:

# servman query -status -group SESMService

3 If SESM service is running then continue with step 4 and ifSESM service is not running then you have completed thisprocedure.

4 Stop the SESM server application by typing:

# servstop SESMService


5 Wait approximately 3 to 5 minutes before you proceed to thenext step to allow the SESM server application to stop.

6 To verify the SESM services stopped by typing:



Example response:


NN10450-900 06.023 October 2008


.

Procedure steps 285

CS2K Management Tools are not running

7 Verify the SESM applications stopped by typing:

# ptmctl status

and pressing the Enter key

Example response:

SESM STATUS -------------------------COMPONENT STATUS--------- ------Proxy Agent NOT RUNNINGRMI Regisry NOT RUNNINGSnmpfactory NOT RUNNINGMI2 Server NOT RUNNINGCurrent number of SESM processes running: 0 (of 4)

SESM APPLICATION STATUS: No Applications are ready


--End--


NN10450-900 06.023 October 2008


.


Stopping the NPM server application

Use this procedure to stop the Network Patch Manager (NPM) serverapplication on a Server Platform Foundation Software (SPFS)-basedserver.

Prerequisites• You need root user privileges to perform this procedure.

• It is recommended that all users exit the NPM CLUI and GUI beforestopping the NPM server application.

Procedure stepsATTENTIONIn a two-server configuration, perform the steps that follow on the Active server.

Step Action

1 At your workstation, to log in to the server type

> telnet <server>


In a two-server configuration, enter the physical IP address ofthe Active server (unit 0 or unit 1).


3 Change to the root user by typing:

$ su - root



In a two-server configuration, ensure you are on the Activeserver by typing ubmstat. If ClusterIndicatorSTBY is displayedin the response, which indicates you are on the Inactive server,log out of that server and log in to the other server through telnetusing the physical IP address of the other unit. The responsemust display ClusterIndicatorACT, which indicates you are onthe Active server.

5 Verify the status of the NPM server application by typing:

# servman query -status -group NPM



NN10450-900 06.023 October 2008


.


6 If the NPM server application is running then continue step7 and if the NPM server application is not running then you havecompleted this procedure.

7 Stop the NPM server application by typing:

# servstop NPM


8 Verify the NPM server application is no longer running by typing:



Example response

NPM===========================Executing: /op/NTnpm/.HA_NPM_status

NPMServer is not running

--End--


<server> IP address or host name of the SPFS-basedserver where the NPM server applicationresides.


NN10450-900 06.023 October 2008


.


Stopping the APS server application

Stop the APS server application to end the APS server application on theServer Platform Foundation Software (SPFS)-based server.

The APS resides on the same server as the Communication S 2000Management Tools software (CS2M).

Prerequisites• Before performing this procedure, verify that the APS server application

is running. Enter:# servman query -status -group APS

• You must have root user privileges to perform this procedure.


Step Action

1 At your workstation to log in to the server type

> telnet <server>





$ su - root



In a two-server configuration, ensure you are on the Activeserver by typing ubmstat. If ClusterIndicatorSTBY is displayedin the response, which indicates you are on the Inactive server,log out of that server and log in to the other server through telnetusing the physical IP address of the other unit. The responsemust display ClusterIndicatorACT, which indicates you are onthe Active server.

5 Stop the APS server application by typing:

# servstop APS


NN10450-900 06.023 October 2008


.



6 Verify the APS server application stopped by typing:

# servman query -status -group APS


Example response

Executing : /opt/servman/bin/servquery -status -groupAPSAPS======================================Executing : /usr/ntdb/uas/scripts/apsHealth.kshOracle Instance is DOWNOracle Listener is DOWN.PROBLEM: Oracle is not running.

The APS requires ORACLE to be up.

--End--


<server> IP address or host name of the SPFS-basedserver where the APS resides.


NN10450-900 06.023 October 2008


.


Starting the APS server application

Starting the APS server application to begin the APS server applicationon the Server Platform Foundation Software (SPFS)-based server wherethe APS resides.

The APS resides on the same server as the Communication Server 2000Management Tools software (CS2M).


Step Action

1 At your workstation, log on to the server by typing:

> telnet <server>





$ su - root



In a two-server configuration, ensure you are on the Activeserver by typing ubmstat. If ClusterIndicatorSTBY is displayedin the response, which indicates you are on the Inactive server,log off of that server and log on to the other server through telnetusing the physical IP address of the other unit. The responsemust display ClusterIndicatorACT, which indicates you are onthe Active server.

5 Verify the status of the APS server application by typing:



6 If APS server is not running then continue the next step and ifAPS server is running then you have completed this procedure.

7 Start the APS server application by typing:

# servstart APS


NN10450-900 06.023 October 2008


.

Procedure steps 291


8 Verify the APS server application started by typing



Example response:

APS===============================Executing : /usr/ntdb/uas/scripts/apsHealth.kshOracle Listener and DB appear are up.APS server processes:APS PID files are on the filesystem.-rw-rw-rw- 1 root other 6 Jan 25 06:00 /opt/uas/aps/scripts/runAdmanager.pid-rw-rw-rw- 1 root other 6 Jan 27 03:06 /opt/uas/aps/scripts/runAlertHandler.pid-rw-rw-rw- 1 root other 6 Jan 24 22:56 /opt/uas/aps/scripts/runApsDbServer.pid-rw-rw-rw- 1 root other 6 Jan 24 22:56 /opt/uas/aps/scripts/runDbServer.pid-rw-rw-rw- 1 root other 6 Jan 24 22:56 /opt/uas/aps/scripts/runFileUpload.pid-rw-rw-rw- 1 root other 6 Jan 24 22:56 /opt/uas/aps/scripts/runHeartbeat.pid-rw-rw-rw- 1 root other 6 Jan 24 22:56 /opt/uas/aps/scripts/SnmpAgent.pidChecking process: /opt/uas/aps/scripts/runApsDbServer.pidThe ’runApsDBServer’ process, PID: 15012 is ACTIVE andRUNNING.Checking process: /opt/uas/aps/scripts/runDbServer.pid The ’runDBServer’ process, PID: 14456 is ACTIVE andRUNNING.Checking process: /opt/uas/aps/scripts/runFileUpload.pid The ’runFileUpload’ process, PID: 14826 is ACTIVEand RUNNING.Checking process: /opt/uas/aps/scripts/runAdmanager.pid The ’ADmanager’ process, PID: 23018 is ACTIVE andRUNNING.Checking process: /opt/uas/aps/scripts/runHeartbeat.pid The ’Heartbeatmon’ process, PID: 15403 is ACTIVE andRUNNING.Checking process: /opt/uas/aps/scripts/SnmpAgent.pidThe ’SnmpAgent’ process, PID: 14271 is ACTIVE andRUNNING.


NN10450-900 06.023 October 2008


.


APS is up and running.

--End--


<server> IP address or host name of the SPFS-basedserver where the APS resides.


NN10450-900 06.023 October 2008


.

Procedure steps 293

Starting the SESM server application

Start the Succession Element and Subelement Manager (SESM) serverapplication to begin the SESM server application on the SPFS-basedserver.

Procedure steps

Step Action

1 At your workstation, establish a connection to the server that ishosting the CS 2000 Management Tools through telnet or SSH,and log on using the root user ID and password.

In a two-server configuration, log on to the active server usingthe physical IP address of the active server, and ensure you areon the active server using the ubmstat command.

2 Verify the status of the SESM server application by typing:



3 If the response indicates not running then go to step 4 and if theresponse indicates running then go to step 7.

4 Start the SESM server application by typing:

# servstart SESMService


5 Wait approximately 3 to 5 minutes before you proceed to thenext step to allow the SESM server application to start.

6 To Verify the SESM server application started verify the SESMservices started by typing:



Example response:

CS2K Management Tools are running

7 Verify the SESM applications started by typing:

# ptmctl status


Example response:

SESM STATUS -------------------------


NN10450-900 06.023 October 2008


.


COMPONENT STATUS--------- ------

Proxy Agent RUNNINGRMI Regisry RUNNINGSnmpfactory RUNNINGMI2 Server RUNNINGCurrent number of SESM processes running: 4 (of 4)

SESM APPLICATION STATUS: All Applications Ready

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 295

Starting the SAM21 Manager server application

Start the SAM21 Manager server application to begin the SAM21Manager server application on the SPFS-based server that is hosting theCommunication Server Management Tools.

Procedure steps

Step Action

1 At your workstation, establish a connection to the server that ishosting the Communication Server Management Tools throughTelnet or SSH, and log on using the root user ID and password.

In a two-server configuration, log on to the active server usingthe physical IP address of the active server, and ensure you areon the active server using the ubmstat command.

2 Verify the status of the SAM21 Manager server application bytyping:



3 If SAM21EM is not running then continue the next step and if theSAM21EM is running then you have completed this procedure.

4 Start the SAM21EM server application by typing:

# servstart SAM21EM


5 Verify the SAM21EM server application started by typing:



Example response:

Executing: /opt/servman/bin/servquery -status -groupSAM21EMSAM21EM===============================Executing : /opt/nortel/sam21em/bin/healthSuccession SAM21 Element Manager version: SAM21EM_9_020_0

Current status of the Succession SAM21 Element Manager:SNMP Access Gateway is running.SAM21 Element Manager Server is running.


NN10450-900 06.023 October 2008


.



--End--


NN10450-900 06.023 October 2008


.

Procedure steps 297

Starting the NPM server application

Start the Network Patch Manager (NPM) server application to beginthe NPM server application on a Server Platform Foundation Software(SPFS)-based server.

Prerequisites• You need root user privileges to perform this procedure, and CORBA

must be running in order for the NPM to come up.

Procedure stepsATTENTIONIn a two-server configuration, perform the steps that follow on the active server.

Step Action

1 At your workstation, log on to the server by typing:

> telnet <server>





$ su - root



In a two-server configuration, ensure you are on the Activeserver by typing ubmstat. If ClusterIndicatorSTBY is displayed inthe response, which indicates you are on the Inactive server, logout of that server and log on to the other server through telnetusing the physical IP address of the other unit. The responsemust display ClusterIndicatorACT, which indicates you are onthe active server.

5 Verify the status of the NPM server application by typing:



6 If the NPM server application is not running then continue thenext step and if the NPM server application is running then youhave completed this procedure.


NN10450-900 06.023 October 2008


.


7 Start the NPM server application by typing:

# servstart NPM


8 Verify the NPM server application is running by typing:



Example response:

Executing: /opt/servman/bin/servquery -status -groupNPMNPM===============================Executing : /opt/NTnpm/.HA_NPM_status

The NpmServer is running

--End--


<server> IP address or host name of the SPFS-basedserver where the NPM server applicationresides.


NN10450-900 06.023 October 2008


.


Performing a full system restore on an SPFS-basedserver

Use this procedure to perform a full system restore from backup media ona Server Platform Foundation Software (SPFS)-based server (Sun Netra240).

A full system restore consists of reverting to the previous release of SPFS,restoring the file systems, and restoring the system data.

ATTENTIONAfter performing a full system restore on IEMS you must also perform asubsequent central server restore. See "Restoring the Central Security Server"in Nortel IEMS Administration and Security ( (NN10336-611)) .






• Core Billing Manager (CBM)


Restoring the oracle data is not applicable to the CBM as it does not usean oracle database.

ATTENTIONSystem logs indicating application and database errors will be generated untilthe file systems and oracle data are restored on the system using this procedureand procedure Restoring the Oracle/MySQL data on an SPFS-based server.No database errors will be generated on the CBM as it does not use an oracledatabase.

ATTENTIONSystem logs indicating application and database errors will be generated untilthe file systems and oracle data are restored on the system using this procedureand procedure Restoring the Oracle/MySQL data on an SPFS-based server.No database errors will be generated on the CBM as it does not use an oracledatabase.


NN10450-900 06.023 October 2008


.


Prerequisites• you need SPFS CD disk #1 or SPFS DVD for the release you are

reverting to

• you need the DVD on which you backed up the file systems

• you need the DVD on which you backed up the system data

ATTENTIONThe recovery must be performed on the system where the backup was created.Recovery cannot be performed on a different system.

Procedure stepsATTENTIONFor MDM and other components that use a simplex configuration with no oracledatabase, complete ONLY steps 1-8. If the additional steps are executed, errorswill occur.

Simplex configuration

Step Action

1 At the server console, log in to the server through the console(port A) using the root user ID and password.

2 Bring the system to the OK prompt by typing:

# init 0

3 Insert SPFS CD disk#1 or SPFS DVD into the drive.

4 At the OK prompt, restore the system by typing:

OK boot cdrom - restore

5 When prompted, accept the software license restrictions bytyping:

ok


The system reboots.

If restoring from DVD, you will be prompted to insert Volume1 of the backup DVD into the drive. Insert the DVD on whichyou backed up the file systems. During the restore process, thesystem will prompt you for additional Volumes if more than oneDVD was used during the backup of file systems.

The restore process can take several hours to completedepending on the number and size of the files that are beingrestored.


NN10450-900 06.023 October 2008


.

Procedure steps 301

Although it can appear as if the system is hanging at times, donot interrupt the restore process. If you suspect an issue with therestore process, please contact your next level of support.

6 Eject the backup DVD from the drive.

7 Ensure you are at the root directory level by typing:

# cd /

8 Eject the DVD by typing:

# eject cdrom

If the DVD drive tray will not open after you have determined thatthe DVD drive is not busy and is not being read from or writtento, enter the following commands:




9 Remove the backup CD or DVD from the drive.

10 If the SPFS-based server is hosting the CBM then do step 12.

11 If the server is hosting anything else then you have completedthis procedure.

12 List the oracle groups by typing:

# groups oracle

13 If the output is install data dba or install dba data then do step16.

14 If the output is otherwise then do step 15.

15 Correct the oracle groups by typing:

# usermod -g oinstall -G data,dba oracle


16 Restore the oracle data using procedure Restoring theOracle/MySQL data on an SPFS-based server.

17 Reboot the server by typing:

# init 6

18 Restore the central security server.

For more information, see "Restoring the Central SecurityServer" in Nortel IEMS Administration and Security ((NN10336-611)) .

--End--


NN10450-900 06.023 October 2008


.


High-availability configuration (two servers)

Use this procedure for high-availability configuration (two servers).

Procedure stepsATTENTIONThe recovery must be performed on the same unit where the backup wascreated.

Step Action

1 At the console connected to the inactive node, log in to theinactive node through the console (port A) using the root userID and password.


# init 0

3 At the console connected to the active node, log in to the activenode through the console (port A) using the root user ID andpassword.


# init 0

5 Insert SPFS CD disk#1 or SPFS DVD into the drive.

6 At the OK prompt, restore the system by typing:

OK boot cdrom - restore

7 When prompted, accept the software license restrictions bytyping:

ok

The system reboots.

8 When prompted, insert Volume 1 of the DVD on which youbacked up the file systems into the drive.

During the restore process, the system will prompt you foradditional Volumes if more than one DVD was used during thebackup of file systems.

The restore process can take several hours to completedepending on the number and size of the files that are beingrestored.

Although it can appear as if the system is hanging at times,please do not interrupt the restore process. If you suspect anissue with the restore process, contact your next level of support.

9 Ensure you are at the root directory level by typing:


NN10450-900 06.023 October 2008


.

Procedure steps 303

# cd /

10 Eject the DVD by typing:

# eject cdrom

If the DVD drive tray will not open after you have determined thatthe DVD drive is not busy and is not being read from or writtento, enter the following commands:




11 Remove the backup DVD from the drive.

Remove the backup CD or DVD from the drive.

12 Ensure the replicated file systems on the newly restored unit areactive.

# cd /opt/nortel/sspfs/ha

./ActivateNode

The output from execution of the ActivateNode script is asfollows, and the user must enter Y to the prompt:

This procedure may cause data loss. Are you sure you wantto proceed? [Y/N]

13 Confirm the prompt.

Y

Executing irrevocable procedure udactive.....

14 Execute the following command to confirm that all replicated filesystems are active.

# udstat

/audio_files: ACTIVE repair DOWN dirty/data: ACTIVE repair DOWN dirty/data_ordata (/data/ordata): ACTIVE repair DOWN dirty/user_audio_files: ACTIVE repair DOWN dirty

Contact your next level of support if any of the file systems showSTANDBY as the state.

15 Use the following steps to determine your next step.

16 If the SPFS-based server is hosting the CBM then do step 21.

17 List the oracle groups by typing:


NN10450-900 06.023 October 2008


.


# groups oracle

18 If the output is install data dba or nstall dba data then go to step20.

19 Correct the oracle groups by typing:

# usermod -g oinstall -G data,dba oracle

20 Restore the data using procedure Restoring the Oracle/MySQLdata on an SPFS-based server.

After the data restore is complete, execute step 17 of thisprocedure.

21 Reboot the server by typing:

# init 6

22 Restore the central security server.

See "Restoring the Central Security Server" in Nortel IEMSAdministration and Security ( (NN10336-611)) .

23 Ensure the node is active by typing:

# cd /opt/nortel/sspfs/ha

# ./ActivateNode

The output from execution of the ActivateNode script is asfollows, and the user must enter Y to the prompt:

This procedure may cause data loss. Are you sure you wantto proceed? [Y/N]

24 Confirm the prompt.

Y

Executing irrevocable procedure udactive.....

25 Re-image the inactive node using the active node’s image. Ifrequired, see the procedure Cloning the image of the active nodeto the inactive node of a Core and Billing Manager cluster.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 305

Locking a GWC card

Use this procedure to lock a single GWC card, stopping the services,applications, and platform software running on the GWC card.

Use this procedure:

• when you are removing the card from service

• along with procedure “Unlocking a GWC card” (page 457) to reboot aGWC and force a software download

• as part of fault clearing activity to determine if a problem is temporaryor persistent

• when you apply or remove a patch to the GWC software using theNetwork Patch Manager (NPM) and create a new GWC softwareimage on the CS 2000 Core Manager

• when you are removing a GWC node from the CS 2000 GWC Managerdatabase

• when you are replacing or upgrading hardware

Prerequisites• If the card that you want to lock is active, switch call processing to its

mate card in the node. The switch places the card in standby mode. Ifrequired, follow procedure "Invoking a manual protection switch (warmSWACT)" in Nortel Gateway Controller Administration and Security( (NN10213-611)) .

• When the card is in standby mode, disable (busy) services on the card.Follow procedure "Disabling (Busy) GWC card services" in NortelGateway Controller Administration and Security ( (NN10213-611)) .

Procedure stepsAt the CS 2000 GWC Manager client

Step Action

1 At the CS 2000 Management Tools window, click the GatewayController folder from the Device Types directory tree in the farleft frame.

2 From the Contents of: GatewayController frame, select the GWCnode that contains the card you want to lock.


NN10450-900 06.023 October 2008


.


3 Select the Maintenance tab to display maintenance informationabout the node.

4 Click the Card View button for the card you want to lock.

5 At the CS 2000 SAM21 Manager client in the card view, selectthe States tab, then click the Lock button to lock the card.

6 Observe the system response in the History window.


NN10450-900 06.023 October 2008


.

Procedure steps 307

The card is locked when you see the text "Application lockedsuccessfully" in the History display. The lock icon (circled in thefollowing figure) should also be present on the card graphic atthe left of the screen:

7 If necessary, repeat this procedure for the next GWC card in thenode.

--End--


NN10450-900 06.023 October 2008


.


Locking the Call Agent

Use this procedure to Lock the Call Agent.

CAUTIONPossible service interruptionDo not lock the active Call Agent.

Procedure stepsAt the CS 2000 SAM21 Manager client

Step Action

1 From the Shelf View, right click on the card and select Lock fromthe context menu.

Lock is also available from the States tab of the Card Viewwindow.

2 Do not confirm a lock warning. The warning is only available forthe active Call Agent. Wait for the lock icon to appear on theselected card.

--End--


NN10450-900 06.023 October 2008


.

Job aid 309

Job aidThe CS 2000 SAM21 Manager client responds to an active Call Agent lockwith the prompt show in Figure 20 "Call Agent lock warning" (page 309).Do not click Yes. The inactive Call Agent is located in the other CS 2000SAM21 Manager shelf and a lock request does not provide a prompt whenthe Call Agent is inactive.

Figure 20Call Agent lock warning


NN10450-900 06.023 October 2008


.


Installing the remote backup server

Use this procedure to install the remote backup server for GeographicSurvivability. Backing up the remote server provides a standby backupsystem which is ready to provide service if the primary system isunavailable for an extended period of time. The remote server can assumethe identity of the primary server with data and files accurate to the lastsynchronization.

This procedure applies only to DVD installations.

Prerequisites• Collect the following information beforehand to ensure that you have

the information ready for input for this procedure. Also acquire the rootuser ID and password.

ATTENTIONAlso gather this information prior to an upgrade.

System variable Actual value Description

Hostname

IP address Remote backup server

Netmask

Router Default gateway IP

Unit 0 IP address IP of primary cluster unit 0

Daily backup (up to four) Format =

where

MM minutes (00 - 59)

DNS domain

IP address DNS server(s)

DNS search domain(s)

Timezone Timezone = Timezone (# echo$TZ)

SPFS serial number Located on label on back ofSPFS

DNS variables apply only when a DNS server has been configured.

Procedure stepsInstalling the remote backup server on a Geographic Survivability standbyserver


NN10450-900 06.023 October 2008


.

Procedure steps 311

At your workstation or the remote server console

Step Action

1 To log in using ssh, type:

ssh -l root <server>

press the Enter key. Go to step 5.

2 To log in using telnet, type:

telnet

and press the Enter key. Go to step 5.

3 Log in to the remote server through the console (port A)and when prompted, enter the root or emsadm user ID andpassword.

4 Bring the system to the {0} OK prompt by typing:

# init 0

5 Enter the following command to verify that the auto-boot optionis set to true.

{0} ok printenv auto-boot?

If it is set to false, enter the following command.

{0} ok setenv auto-boot?=true

6 Insert the SPFS0** DVD into the DVD drive on the remotebackup unit.

where

** refers to the release (for example, 091 forSN09.1)

7 Install the remote backup server for Geographic Survivability.

{0} OK boot cdrom - rbackup


NN10450-900 06.023 October 2008


.


Example responses

{{0} ok boot cdrom - rbackupBoot device: /pci@1e,600000/ide@d/cdrom@0,0:f Fileand args: -rSunOS Release 5.8 Version Generic_108528-18 64-bitCopyright 1983-2001 Sun Microsystems, Inc. Allrights reserved.Hardware watchdog enabledConfiguring /dev and /devicesUsing RPC Bootparams for network configurationinformation.Skipping interface bge3Skipping interface bge2Skipping interface bge1Skipping interface bge0/This CD contains software that under the terms of yourlicense agreement with Nortel Networks is licensedfor use only on Nortel Networks OAM&P servers. Type"ok" to acknowledge this restriction on your useof the software. Any other input will halt theinstallation of this software.

Type "ok" to acknowledge this restriction on your useof the software.

Any other input will halt the installation of thissoftware.

8 Type OK and press Enter to acknowledge restriction on youruse of the software.

Searching for configuration file(s)...

9 Enter the serial number located in the rear view of the SPFS andpress Enter.

*** REMOTE Backup INSTALL ***Begin entering installation informationPlease select a server profile for this systemrbackup: Remote Automatic Backup standby systemEnter the server profile for this system:

( rbackup )

10 Select the rbackup server profile for the system.

Installing with server profile "Remote Automatic Backupstandby system"

Install can proceed with factory default values fornetwork configuration or you may specify the networkconfiguration now.


NN10450-900 06.023 October 2008


.

Procedure steps 313

Use factory default network configuration: [yes] no

11 Enter No to not select the default settings. The N240 servermust be connected to the network and must have access to thedefault gateway. This allows you to enter the server’s settingsfor the installation.

12 Enter site-specific information in response to the followingprompts. (See the information entered in the table at thebeginning of this procedure.)

Enter the hostname for this system.Enter the IP address for <hostname>.Enter the subnet mask for this network.Enter the IP address for this network’s router.Enter the timezone for this system [US/Eastern].

The default timezone is US/Eastern. Enter ? for a list ofsupported time zones.

Will this system use DNS? [yes]

Enter yes or no. If you answer yes, you are prompted for theDNS domain name, name server IP addresses, and the searchdomains. You can enter several name servers and searchdomains. Enter a blank line to stop the entry.

13 Click OK to accept current settings.

The installation of the DVD takes approximately 60 minutes. Ifnecessary, press Enter to redisplay the login prompt on screenafter the following message displays:

NOTE:NOTE: SSPFS Installation is now completed.NOTE:

HostName> console login:

14 Log in to the server using the root user ID and password. (At thispoint, the root password has been reset to "root.")

15 Remove the SPFS DVD from the server. If necessary, enter

eject cdrom

16 Enter the command line interface (CLI) tool.

cli

17 Enter the number next to the Configuration option in the menu.

18 Enter the number next to the Succession Element Configurationoption in the menu.

19 Enter the number next to the PSE Application Configurationoption in the menu.

20 Enter the number next to the Configure PSE option in the menu.


NN10450-900 06.023 October 2008


.


21 Enter the primary/cluster IP address of CS 2000 ManagementTools server. This is the address of the NPM server.

22 Enter Y to confirm the IP address.

Ignore the following error message if it displays.

Can’t configure PSE on remote backup unit to enable NPM

23 Enter X to exit each level until you have exited from the cli tool.

24 Start the PSE server.

# pse start

25 Verify that the server has started. If the server does not start,contact your next level of support.

# pse status

26 If an SPFS MNCL CD is to be installed, see the documentationincluded with the CD for complete installation instructions.

27 Enter NPM on the CS 2000 Management Tools server and followpatching procedures to apply all relevant patches.

28 To forward SNMP traps on the server to the IEMS, perform theprocedure "Configuring the destination for SNMP traps" in NortelATM/IP Solution-level Configuration ( (NN10409-500)) .

--End--


<server> Name of the N240 server.


NN10450-900 06.023 October 2008


.

Procedure steps 315

Scheduling automatic backups on the remote server

Use this procedure to schedule automatic backups on the remote sever.Backing up the primary server provides a standby backup system whichis ready to provide service if the primary system is unavailable for anextended period of time. The remote server can assume the identity of theprimary server with data and files accurate to the last synchronization.

ATTENTIONThis procedure is for use with Geographic Survivability only.

Procedure steps

Step Action

1 Determine how to log in to the Sun Netra 240 (N240) server thatis installed as the remote backup server.

2 To log in using SSH, type:

ssh -l root (server>


3 To log in using Telnet, type:

telnet <server>



5 Start the command line interface tool by entering:

cli


The system displays the Configuration menu.

7 Enter the number next to the Remote Backup option in themenu.

Response:

Remote Backup Configuration1 - rbackup_display (Display Remote Backup Configuration)2-rbackup_config (Remote Backup Configuration)3-rbackup_exec (Execute Remote Backup Now)4 - rbackup_cancel (Cancel Running Remote Backup)

X-exit

8 Select


NN10450-900 06.023 October 2008


.


2-rbackup_config (Remote Backup Configuration)

The system responds with the IP address of the primary serverthat is currently configured as the remote server, and the timesthat are currently configured for automatic backups.

9 Enter the unit 0 IP address of the primary server to be backedup.

<nnn.nnn.nnn.nnn> is alive

10 If the system prompts you to accept the ssh key Enter yes. Goto step 13.

11 If the system does not prompt you to accept the ssh key then goto step 13.

12 Enter the first time for a daily backup to occur.

You can configure up to four times for daily backup to occur.

Response:

Enter a time for a daily backup to occur (HH:MM):

Response:

Enter a second time for a daily backup to occur (HH:MM) orenter "x" to stop provisioning backup times:

13 If you want to enter another time for a remote backup to occurenter a second time for a daily backup to occur. Go to step 16.

14 If you do not want to enter another time for a remote backup tooccur enter x. Go to step 20.

15 If you want to enter another time for a remote backup to occur,enter a third time for a daily backup to occur. Go to step 18.

16 If you do not want to enter another time for a remote backup tooccur enter x.

17 If you want to enter another time for remote backup to occurenter a fourth time for a daily backup to occur. Go to step 20.

18 If you do not want to enter another time for a remote backup tooccur enter x.

19 Enter a bandwidth limit in KB/s ( 0 means no limit ) [0]:

20 To commit changers go to step 24.

21 To exit enter quit.

22 To re-enter setting enter anything other than ok or quit.

23 Enter

ok

=== "rbackup_config"completed successfully


NN10450-900 06.023 October 2008


.


24 Exit the Remote Backup Configuration level.

x

--End--


<nnn.nnn.nnn.nnn> IP address that you entered.


HH HH is hours. Valid values are 00 to 23.

MM MM is minutes. Valid values are 00 to 59.


NN10450-900 06.023 October 2008


.


Viewing configuration information for remote serverbackups

Use this procedure to view configuration information for remote serverbackups. The system displays the IP address of the target system and thetimes in which automatic backups of the target system will occur.


Procedure steps

Step Action

1 Log in to the Sun Netra 240 (N240) server that is installed as theremote backup server.




3 To log in using telnet, type:

telnet <server>



5 Start the command line interface tool by entering:

cli

The system responds by displaying a menu.




Response:

Remote Backup Configuration1-rbackup_display (Display Remote Backup Configuration)2-rbackup_config (Remote Backup Configuration)3-rbackup_exec (Execute Remote Backup Now)4 - rbackup_cancel (Cancel Running Remote Backup)

X-exit

8 Select


NN10450-900 06.023 October 2008


.


1-rbackup_display (Display Remote Backup Configuration)

Response:Current settings:Target system is: <nnn.nnn.nnn.nnn>

Back up times are: <Time 1>...<Time n>

9 Exit the Remote Backup Configuration level by typing:

x

--End--


server Name of the N240 server.

<nnn.nnn.nnn.nnn> IP address of the remote server.

<Time 1>...<Time n> Set of times at which automated backups occur.


NN10450-900 06.023 October 2008


.


Performing a manual backup of the target server

Performing a manual backup of the target server. Backing up the primaryserver provides a standby backup system which is ready to provide serviceif the primary system is unavailable for an extended period of time. Theremote server can assume the identity of the primary server with systemconfiguration data and files accurate to the last synchronization.


Procedure steps

Step Action





3 If you want to log in using telnet, enter:

telnet <server>



5 Start the command line interface tool.

cli

The system responds by displaying a menu.




Remote Backup Configuration1-rbackup_display (Display Remote Backup Configuration)2-rbackup_config (Remote Backup Configuration)3-rbackup_exec (Execute Remote Backup Now)4 - rbackup_cancel (Cancel Running Remote Backup)

X-exit

8 Select

3-rbackup_exec (Execute Remote Backup Now)


NN10450-900 06.023 October 2008


.


9 An automatic backup is made.

Pressing 4 during execution of the backup halts the process andperforms necessary clean-up operations.

10 Exit the Remote Backup Configuration level.

x

--End--




NN10450-900 06.023 October 2008


.


Viewing logs from a remote backup

View logs from a remote backup created during automatic and manualbackups of the remote server.

Procedure steps

Step Action


2 To log in using SSH, enter:



3 To log in using Telnet, enter:

telnet <server>


4 To log in to the remote server console then go to step 5.

5 Enter:

less /var/adm/messages

The system responds by displaying the contents of the log file.

--End--




NN10450-900 06.023 October 2008


.

Procedure steps 323

Initiating a recovery back to the cluster

Use this procedure to initiate a recovery back to the cluster.

Prerequisites• If the server was previously a CBM and contains billing files not already

sent to a downstream billing server, using the cluster server, copythese files to a downstream server before performing this procedure.Otherwise these files and the billing records will be lost. Contact nextlevel of support for assistance.

• Both cluster units 0 and 1 must be in the firmware mode. (Entercommand init 0 to perform this action)

• In this procedure, unit0 server of the cluster is used as a remotebackup server. Use the same hostname and IP address that was usedto configure the remote backup server.

WARNINGIf both the remote backup unit and the high-availability (HA)pair are in service after a switch command, both units vie fordominance. This conflict results in a loss of communication tothe core.

Procedure steps

Step Action

1 Follow procedure “Installing the remote backup server” (page310).

Use only one automated schedule and make sure to select atime that will not be invoked shortly.

2 Follow procedure “Performing a manual backup of the targetserver” (page 320).

3 Bring down the machine currently active by following procedure‘Two-server (cluster) configuration’ in Shutting down anSPFS-based server in .

4 Follow procedure “Initiating a switch over to the remote backupserver” (page 325) to bring the services back to unit0 of thecluster.

5 Follow procedure ‘Cloning the image of one server in a cluster tothe other server’ in the document .

6 If the server was previously a CBM and contains billing files notalready sent to a down-stream billing server, use the remotebackup server to copy these to a downstream server before


NN10450-900 06.023 October 2008


.


performing “Installing the remote backup server” (page 310).Otherwise these files and the billing records are lost. Contactnext level of support for assistance.

7 Reinstall the backup server following procedure “Installing theremote backup server” (page 310).

8 Reconfigure the backup server following procedure “Schedulingautomatic backups on the remote server” (page 315).

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 325

Initiating a switch over to the remote backup server

Use this procedure to initiate a switch over to the remote backup server.

ATTENTIONWhen completed, this procedure reboots the remote backup server as the unit0of the cluster.

Prerequisites• Prior to starting this procedure, shut down the Cluster machine.

• The user must be logged in as the root or emsadm user to initiate theswitch command.

• For more information, see the section Two-server (cluster)configuration in Shutting down an SPFS-based server in documentNortel ATM/IP Solution-level Fault Management ( (NN10408-900)) , ,and .

CAUTIONIf configuration, provisioning, patching or other “write”-typeoperations occurred since the last remote backup, the remotebackup system can be out of sync compared to the data innetwork elements and/or the primary OAM system.

Take actions before initiating the switchover to a remotebackup OAM server (that is, response to a geographic or otherprolonged outage of the primary OAM system) to halt or prevent“write”-type operations by OSSs and operations personnel untilan in-sync status is achieved.

When initiating a switchover to a remote backup OAM server,do not execute configuration, provisioning, patching or other“write”-type operations through the remote backup OAM systemuntil out-of-sync conditions are cleared.

Procedure steps

Step Action

1 Log in to the server by typing

> telnet <server>




su - root


NN10450-900 06.023 October 2008


.



5 Invoke the switch by typing:

$ /opt/sspfs/rbks/switch

6 When ready, indicate you want to proceed by typing:

OK

--End--


<server> IP address or host name of the SPFS-basedremote backup server.


NN10450-900 06.023 October 2008


.

Procedure steps 327

Disabling Ethernet Routing Switch 8600 WAN Edgerouting

ATTENTIONPerform this procedure immediately after a site failure occurs to limit effects toCall Processing.

This procedure is required to workaround a deficiency in the architecturewhen the active in-service and SYSB (out of service) GWC sendmessages to a gateway provisioned off the GWC causing mismatches inthe gateway resulting in loss of call processing.

This procedure will impact every element sitting off the ERS 8600.

There are two options for this procedure. The first option will disable alldynamic routing on the chassis and no traffic will be able to leave or enterthe VLANs configured on that chassis when using Open Shortest PathFirst (OSPF). Static routes and Local communication is still possible.

The second option will disable the WAN Edge Interface. All traffic, whetherthrough dynamic or static routes will not be able to leave or enter thechassis.

Procedure stepsAt the Ethernet Routing Switch 8600 Workstation

Step Action

1 To use option 1, go to step 3

2 To use option 2, go to step 5

3 Disable OSPF by typing

#config ip ospf disable



5 Identify the WAN Edge VLAN ID by typing

#show vlan info basic


Example response


NN10450-900 06.023 October 2008


.


6 Identify the ports used for WAN Edge connectivity by typing

#show vlan info ports <vlan_id>


Example response

7 Disable the ports used for WAN Edge connecitvity by typing

#config ethernet <port_range_1> state disable


...

#config ethernet <port_range_n> state disable


--End--


<vlan_id> is the VLAN ID obtained in step 4

<port_range_1> is a range of ports used for WAN Edge


NN10450-900 06.023 October 2008


.

Procedure steps 329

Disabling and re-enabling the router ports on theEthernet Routing Switch 8600

Use this procedure when a failure occurs, such that Sites A and B areisolated from each other, to disable and re-enable the Ethernet RoutingSwitch 8600 router ports that are connected to the GWC in the inactivesite.

Prerequisites• You must know the list of router ports connected to the GWCs.

Procedure steps

Step Action

1 At the Ethernet Routing Switch 8600 Workstation, confirm whichsite has the active Call Agent.

2 Confirm that the GWCs in the active site are active.

3 Disable the ports to the GWC units on the inactive site by typing:



...

#config ethernet <port_range_n> state disable


4 If you disabled OSPF in the procedure Disabling EthernetRouting Switch 8600 WAN Edge routing on page 205, re-enableit by typing:

#config ip ospf enable


5 If you disabled the ports used for WAN Edge connectivity,re-enable those ports by typing:

#config ethernet <port_range_1> state enable


...

#config ethernet <port_range_n> state enable


6 Check the time by typing:


NN10450-900 06.023 October 2008


.


#date


Example response

local time: THU MAR 31 17:32:57 2005 EST

hardware time: THU MAR 31 22:32:57 2005 UTC

7 Allow at least one minute to pass to ensure that internal GWCaudits set the units to inactive.

8 Check the time by typing:

#date


Example response

local time: THU MAR 31 17:33:59 2005 EST

hardware time: THU MAR 31 22:33:59 2005 UTC

9 If the inactive building is accessible, perform steps 10 through 12to verify the inactive GWC units have gone inactive.

10 Connect the terminal to the console port on the GWC.

11 Enter PMDEBUG and perform the ’T’, ’N’, and ’A’ commands.

12 Confirm that the state is inactive. if not, repeat steps 3 through8 on those ports.

13 Re-enable the ports to the GWC units in the inactive site bytyping



...

#config ethernet <port_range_n> state enable


--End--


<port_range> is a range of ports connected to the GWC(example: 3/1-3/48)


NN10450-900 06.023 October 2008


.

331.

Network power downThis chapter highlights the sequence of steps necessary to power down allof the network elements in the office. Not all network elements coveredin this section apply to your office.

Prerequisites

• The network elements should be backed up before powering down iftime permits.

Network power down task flow

This task flow shows you the sequence of procedures you perform topower down the network.


NN10450-900 06.023 October 2008


.

332 Network power down

Figure 21Powering down the network procedures - Part 1


NN10450-900 06.023 October 2008


.


Figure 22Powering down the network procedures - Part 2

Network power down navigation:

• “Powering down an MG 9000 device” (page 335)

• “Powering down the IPmedia 2000 shelves” (page 337)

• “Powering down the SAM16 shelves” (page 338)

• “Powering down a Border Control Point” (page 339)


NN10450-900 06.023 October 2008


.


• “Powering down the MCS servers” (page 340)

• “Powering down the MDM workstation” (page 341)

• “Powering down an SPM device” (page 342)

• “Powering down a Media Gateway/Multiservice Switch 7400” (page345)

• “Powering down a Media Gateway/Multiservice Switch 15000” (page346)

• “Powering down a USP” (page 347)

• “Powering down the SAMF frame” (page 348)

• “Powering down the Call Control Frame” (page 350)

• “SAM21 Shelf Controller security and administration fundamentals”(page 352)

• “Powering down the Border Control Point Manager” (page 355)

• “Powering down the Border Control Point Manager” (page 355)

• “Powering down a Netra 240 server” (page 356)

• “Powering down the SDM” (page 357)

• “Powering down a Ethernet Routing Switch 8600” (page 358)

• “Powering down the XA-Core” (page 360)

• “Shutting down the IEMS server” (page 359)

• “Performing a partial power down of the MG 9000” (page 363)

• “Performing a partial power down of the Media Gateway/MultiserviceSwitch 15000” (page 364)

• “Performing a partial power down of the USP” (page 368)

• “Performing a partial power down of the Ethernet Routing Switch 8600”(page 369)

• “Performing a partial power down of the Netra 240 server” (page 370)

• “Performing a partial power down of the XA-Core” (page 371)


NN10450-900 06.023 October 2008


.

Job aid 335

Powering down an MG 9000 device

This procedure details the sequence of steps necessary to power downMedia Gateway 9000 (MG 9000).

Prerequisites• The optimal power threshold should be 43.7 volts. The minimum is

42.5 volts.

Procedure steps

Step Action

1

ATTENTIONIt is recommended to only unseat the fuses to allow for rapidrestoration.

At the MG 9000 frame, remove the CE (SB) fuses from theframe.See “Job aid” (page 335) to identify the fuse locations.

2 Remove the TB fuses from the frame.

3 Remove the CU fuses from the frame.

--End--

Job aidThe following figure identifies the fuse locations.


NN10450-900 06.023 October 2008


.


Figure 23MG 9000 frame


NN10450-900 06.023 October 2008


.

Procedure steps 337

Powering down the IPmedia 2000 shelves

Power down the IPmedia 2000 shelves that house the MS 2000 seriesdevices and the Packet Media Anchor. The IPmedia 2000 shelves residein either a SAMF frame or CCF, depending on whether or not your solutionuses the CS 2000 or CS 2000-Compact.

Procedure steps

Step Action

1 At the CCF or SAMF frame, open the front door of theCCF/SAMF frame.

2 At the EBIP at the top of the frame, turn the breaker associatedthe Media Server to the OFF position.

--End--


NN10450-900 06.023 October 2008


.


Powering down the SAM16 shelves

The SAM16 shelves reside in either a SAMF frame or CCF, depending onwhether or not your solution uses the CS 2000 or CS 2000-Compact.

Procedure steps

Step Action


2 At the EBIP at the top of the frame, turn the breakers associatedthe SAM16 to the OFF position.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 339

Powering down a Border Control Point

Use the following procedure to power down a Border Control Point. TheBorder Control Point shelves are powered from either a PDU or EBIPlocated at the top of the frame depending on if the frame is AC or DCpowered.

Procedure steps

Step Action

1 At the frame housing the Border Control Point, power down theshelf by switching the breaker on the back of the chassis to theOFF position.

2 For AC powered shelves, push the rocker located on the topof the AC outlet to apply power to the chassis. It should beswitched to the "0" position.

3 For DC powered shelves, switch the circuit breakers at theEBIP that provide power to the shelf being powered to theOFF position. The breaker will have the ’0’ side (bottom) of thebreaker depressed.

--End--


NN10450-900 06.023 October 2008


.


Powering down the MCS servers

Use the following procedure to power down the MCS servers.

Procedure steps

Step Action

1 At the frame housing the MCS servers, power down the MCSservers by turning off the circuit breakers that provide power tothe servers.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 341

Powering down the MDM workstation

Use the following procedure to power down the MDM Sun FireTM V480workstation.

Prerequisites• It is recommended that you shut down the MDM workstation while on

battery power.

Procedure steps

Step Action

1 At the workstation terminal window, enter the followingcommands to shut down it:

# /bin/sync

# /bin/sync

# /sbin/init 0

--End--


NN10450-900 06.023 October 2008


.


Powering down an SPM device

Use this procedure to power down an Spectrum Peripheral Module(SPM) device, Media Gateway 4000 (MG 4000), Interworking SpectrumPeripheral Module (IW-SPM), or Dynamic Packet Trunking SpectrumPeripheral Module (DPT-SPM).

Prerequisites• MG 4000s may or may not be located at the same location as the Call

Server and therefore power conservation may or may not need to beconsidered separately from the core location.

Procedure steps

Step Action

1

ATTENTIONThis procedure is not necessary for the IW-SPM or DPT-SPM.

At the MAP terminal, post and busy the trunks for the SPM orMG 4000 to be powered down at the TTP level.

>MAPCI;MTC;TRKS;TTP;POST D SPM <spm_no>;BSY ALL

2

ATTENTIONThis procedure is not necessary for the IW-SPM or DPT-SPM.

Busy all the trunks in the PRADCH level.

>PRADCH;POST AD SPM <spm_no>; BSY all

3 Access the carrier level.

>QUIT ALL;MAPCI;MTC;TRKS;CARRIER

4 Post and busy the DS1P carriers.

POST SPM <spm_no> DS1P; BSY ALL

5

ATTENTIONThe VT15P and DS3P carriers may not both exist.

Post and busy the VT15P carriers.

POST SPM <spm_no> VT15P; BSY ALL


NN10450-900 06.023 October 2008


.

Procedure steps 343

6

ATTENTIONThe VT15P and DS3P carriers may not both exist.

Post and busy the DS3P carriers.

POST SPM <spm_no> DS3P; BSY ALL

7 Post and busy the STS1P carriers.

POST SPM <spm_no> STS1P; BSY ALL

8

ATTENTIONThis step only applies to an MG 4000 or IW-SPM.

Post and busy the STS3cp carriers.

POST SPM <spm_no> STS3cp; BSY ALL

9 Post and busy the STS3L carriers.

POST SPM <spm_no> STS3L; BSY ALL

10 Post and busy the OC3s carriers.

POST SPM <spm_no> OC3s; BSY ALL

11 Access the PM level.

>QUIT ALL;MAPCI;MTC;PM;POST SPM <spm_no>

12 Select and BSY the inactive RMs.

>SELECT <rm_type> <inactive_rm_number>; BSY

13 Select and BSY FORCE the active RMs.

>SELECT <rm_type> <active_rm_number>; BSY FORCE

14 Select and BSY the inactive CEM.

>SELECT CEM <inactive_cem_number>; BSY

15 Select and BSY FORCE the active CEM.

>SELECT CEM <active_cem_number>;BSY FORCE

16 Power down the SIM cards using the switch on the front. Thenpull the fuses from the PCIU.

17 Unseat hardware as required to avoid water damage and shorts.

--End--


NN10450-900 06.023 October 2008


.



<spm_no> is the number of the SPM/MG 4000/IW-SPM/DPT-SPM

<rm_type> is the type of RM to select (OC3, DSP, andVSP)

<inactive_rm_number> is the number of the inactive RM

<inactive_cem_number> is the number of the inactive CEM


NN10450-900 06.023 October 2008


.

Procedure steps 345

Powering down a Media Gateway/MultiserviceSwitch 7400

Use the following procedure to power down the Media Gateway/Multiservice Switch 7400.

Prerequisites• Ensure recent provisioning changes are committed.

Procedure steps

Step Action

1

WARNINGIf primary power to the shelf assembly is on, neverset the individual power supply switches to thestandby position. This can cause an overload to theon-line power supply.

ATTENTIONThe front panel LED of each power supply remains lit forapproximately 2 minutes after the power supply loses power.

At the chassis, turn off the circuit breakers for the outlets thatsupply power to your switch.

2 After a couple of minutes, verify the LEDs for the power supplies,cooling unit, and each processor card faceplate are off.

--End--


NN10450-900 06.023 October 2008


.


Powering down a Media Gateway/MultiserviceSwitch 15000

Use the following procedure to power down the Media Gateway/Multiservice Switch 15000.

Prerequisites• Recent provisioning changes need to be committed.

Procedure steps

Step Action

1 At the chassis, breaker interface panels (BIPs) are located at thetop of the chassis. Power down all five breakers simultaneouslyon each BIP, starting at the left.

2 Shut off the BIPs in the following order:

ATTENTIONThis action shuts down the upper shelf.

• BIP B2

• BIP A2

ATTENTIONThis action shuts down the lower shelf.

• BIP B1

• BIP A1

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 347

Powering down a USP

Use the following procedure to power down a Universal SignalingProcessor (USP).

Prerequisites• The USP backup data should be up-to- date. No datafill changes

should be made between the final data snapshot and the poweringdown of the USP.

• All users need to be logged out of the USP GUI and CLI.

Procedure steps

Step Action

1

CAUTIONThe following steps will take the USP out of service.In a redundant network configuration, the USP’smated STP will handle traffic after the USP ispowered down.

End office isolation will occur if the USP is configuredas a Signaling Gateway.

ATTENTIONThe USP bulk-input feature and the CLI can be used to automatethese tasks in the event there are a large number of links in question(see the "Bulk Data Input of System-db Tables" section of the USPCLI Interface Specification Manual)

Inhibit and deactivate all links.

2 At the USP Manager, ensure that the LEDs on slot 13 and slot16 front panel cards are not lit, and immediately turn off the A/BPower buttons on the control shelf.

3 Turn off the A/B Power buttons located on the backside of eachextension shelf.

4 In the event that access to the USP is not available, it will benecessary to disconnect the power source that feeds the USP.

--End--


NN10450-900 06.023 October 2008


.


Powering down the SAMF frame

Use the following procedure to power down the SAMF frame. This involveslocking all cards and the SAM21 shelf and powering down the SessionServer unit and Policy Controller unit.

Procedure steps

Step Action

1 At the Session Server unit, perform procedure Lock the SIPgateway application on the active Session Server unit.

2 Perform procedure Suspend the SIP gateway application on theactive Session Server unit.

3

ATTENTIONThe state of the SIP Gateway application is saved when the unitis powered off. When the unit is powered up, the SIP Gatewayapplication initializes in the same state in which it was powered down.

Perform procedure Halt (shutdown) a Session Server unit on theinactive Session Server unit.

4 Perform procedure Power-Off a Session Server unit on theinactive Session Server unit.

5


Perform procedure Halt (shutdown) a Session Server unit on theactive Session Server unit.

6 Perform procedure Power-Off a Session Server unit on the activeSession Server unit.

7 At the Policy Controller Unit, perform procedure Halt (shutdown)a Policy Controller unit on the inactive Policy Controller unit.

8 Perform procedure Power-Off a Policy Controller unit on theinactive Policy Controller unit.

9 Perform procedure Halt (shutdown) a Policy Controller unit onthe active Policy Controller unit.

10 Perform procedure Power-Off a Policy Controller unit on theactive Policy Controller unit.

11 Lock all active GWC cards.


NN10450-900 06.023 October 2008


.

Procedure steps 349

12 At the CS 2000 GWC Manager, lock all inactive GWC cards.

13 At the CS 2000 SAM21 Manager, lock any inactive cards otherthan the SC cards.

14 Lock any active cards other than the SC cards.

15 Lock the inactive SC card.

16 Lock the active SC card.

17 At the SAMF frame, power down the SAMF frame BIP breakers.At the top of the cabinet, turn off the breakers that supply powerto the two SAM21 shelves and the Session Server (if equipped).

--End--


NN10450-900 06.023 October 2008


.


Powering down the Call Control Frame

Use the following procedure to power down the Call Control Frame (CCF).

Procedure steps

Step Action

1 At the Session Server unit, perform procedure Lock the SIPgateway application on page 66 on the active Session Serverunit.

2 Perform procedure Suspend the SIP gateway application onpage 68 on the active Session Server unit.

3


Perform procedure Halt (shutdown) a Session Server unit onpage 58 on the inactive Session Server unit.

4 Perform procedure Power-Off a Session Server unit on page 71on the inactive Session Server unit.

5


Perform procedure Halt (shutdown) a Session Server unit onpage 58 on the active Session Server unit.

6 Perform procedure Power-Off a Session Server unit on page 71on the active Session Server unit.

7 At the CS 2000 GWC Manager, lock all inactive GWC cards.

8 Lock all active GWC cards.

9 At the CS 2000 SAM21 Manager, lock the inactive USP-lite card.

10 Lock the active USP-lite card.

11 Lock the inactive Compact Call Agent (CCA) card.

12 Lock the active CCA card.

13 At the front panel of the STORM SAM-XTS units, if your CCF isequipped with SAM-XTS units, disconnect the power to each


NN10450-900 06.023 October 2008


.

Job aid 351

unit using the main power switch located on the front panel. Forfigure, see “Job aid” (page 351).

14 At the CCF, power down the CCF BIP breakers. At the top of thecabinet, turn off the breakers that supply power to the SessionServer, the two SAM21 shelves, and the Storm SAM-XTS unitsor Storm Disk Array.

--End--

Job aidThe following figure helps you to power down the Call Control Frame.


NN10450-900 06.023 October 2008


.


SAM21 Shelf Controller security and administrationfundamentals

This section contains conceptual information related to the SAM21 ShelfController (SC) administration and security.

Navigation• “Security and administration strategy” (page 352)

• “Tools and utilities” (page 352)

• “User administration” (page 352)

• “Device administration” (page 353)

Security and administration strategySecurity for the SAM21 SCs is implemented according to the items in thefollowing list:

• physical security of the client workstation

• physical security of the SAM21 shelf

• security mechanisms available through the client workstation operatingsystem

• SAM21 SCs only allow login connections from the CS 2000 CoreManager, the host that provides the CS 2000 Management Tools, andthe mate SAM21 SC.

Tools and utilitiesThere are no tools or utilities for security. The CS 2000 SAM21 Managerclient is the interface for administration of the SAM21 SCs.

If a Card View window is opened and a task or maintenance is completed,close the window rather than minimize the window. Memory consumptionis kept to a minimum, but several unused and open Card View windowscan consume memory on the CS 2000 SAM21 Manager client workstation.

User administrationThe SAM21 SCs do not implement any custom security features. The CS2000 SAM21 Manager client authenticates users when the application isstarted.


NN10450-900 06.023 October 2008


.

Device administration 353

Adding a userThe SAM21 SCs do not provide user administration. The CS 2000SAM21 Manager provides authentication, but not user administration. Forprocedures on how to add a user to the CS 2000 SAM21 Manager clientworkstation, contact your system administrator or refer to the operatingsystem reference documentation.

Setting privilegesThe SAM21 SCs and the CS 2000 SAM21 Manager client do notimplement user privilege administration.

Removing a userTo prevent user access to the CS 2000 SAM21 Manager client, contactyour system administrator to disable the user account on the workstation.

Device administrationAdministration of the SAM21 CSs is done through the CS 2000 SAM21Manager client. This section lists the administration tasks that you canperform.

Unlocking a SAM21 Shelf ControllerUnlock a SAM21 SC from the Shelf View. Right-click on the SAM21 ShelfController and from the menu, select Unlock.

Locking a SAM21 Shelf ControllerLock a SAM21 SC from the Shelf View. Right-click on the SAM21 ShelfController and from the menu, select Lock.


NN10450-900 06.023 October 2008


.


Only lock a circuit pack that is in service. If a SAM21 SC is unlockedand then re-locked before the SAM21 SC boots, flash memory can becorrupted and require a replacement SAM21 SC. Check that a SAM21 SCis Unlocked and Enabled from the Status tab of the Card View window.

Invoking manual protection switchComplete this task from the Shelf View. Right-click on the SAM21 ShelfController and from the menu, select Swact.

Swact is available on the active SAM21 SC only.

Replacing air filtersReplace the three air filters from the front of the fan sleds on the SAM21shelf with part number A0828397. This part number includes three airfilters. Replace these air filters every 10 000 hours. When performing thereplacement, replace one air filter at a time and do not leave a fan notinserted for more than one minute.


NN10450-900 06.023 October 2008


.

Procedure steps 355

Powering down the Border Control Point Manager

Use the following procedure to power down the Border Control PointManager. The Border Control Point Manager is installed on a Sun Netra™240 (N240).

Prerequisites• You must have the root user password for N240.

• You must have the IP addresses for N240.

Procedure steps

Step Action

1 At the N240 server, Telnet or SSH into the server and logon asthe root user.

2 Enter

#init 0

to shutdown the server and to close the Telnet or SSHconnection.

3 At this point, the server can be turned off at the circuit breakers.

--End--


NN10450-900 06.023 October 2008


.


Powering down a Netra 240 server

Use the following procedure to power down a Netra™ 240 server.

Prerequisites• You must have the root user password for the N240 server.

• If you are shutting down the N240s, you need IP addresses for boththe active and inactive units.

Procedure steps

Step Action

1 At the N240 server, Telnet or SSH into the inactive server andlogon as the root user.

2 Type

#init 0

The server shuts down gracefully and the Telnet or SSHconnection is closed.

3 Telnet or SSH into the active server and log in as the root user.

4 Type

#init 0

The server shuts down gracefully and the Telnet or SSHconnection is closed.

5 Turn off both servers at the circuit breakers.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 357

Powering down the SDM

Use the following procedure to power down the SuperNode Data Manager(SDM) that houses the CS 2000 Core Manager.

Procedure steps

Step Action

1 At the VT100 terminal, login as the root user.

2 Shutdown the SDM by typing

# Shutdown -f

.

3 Wait for the system to display the following:

Halt Completed

4 At the SDM frame, turn off the two breakers at the top of theSDM frame.

--End--


NN10450-900 06.023 October 2008


.


Powering down a Ethernet Routing Switch 8600

Use the following procedure to power down the Ethernet Routing Switch8600.

Procedure steps

Step Action

1 At the Ethernet Routing Switch 8600 frame, If you have an8010co Chassis unit and an optional breaker interface panel(BIP) installed, set the BIP circuit breakers to the off position.

See Installing the Breaker Interface Panel for the 8010coChassis, 312755-E.

2 Turn the power supply switch to the off position. See “Job aid”(page 358) for figure.

3 Disable the incoming power from the DC inpt power source. Youmay need to switch a circuit breaker or turn off the DC inputpower source.

--End--

Job aidFigure 24Turning the power supply switch to the off position


NN10450-900 06.023 October 2008


.

Procedure steps 359

Shutting down the IEMS server

The IEMS server shutdown process shuts down all the subprocesses andreleases all the system resources. You must perform this procedure tocorrectly shutdown all the processes to ensure that the system does notleave any operation incomplete, and that the database information is in aconsistent state.

Prerequisites• The shutdown process checks for the authenticity and the permissions

of the user who invokes operation. You must be authorized to performthis procedure.

Procedure steps

Step Action

1 Stop all the schedulers.

2 Notify the registered shutdown observers.

3 Shut down all the subprocesses (sub-modules), which executespecific tasks.

4 Disconnect all database connections.

5 If it was started by IEMS, shut down the web server .

6 Exit (the main process).

To shut down the IEMS server, kill the related Java applicationshell, press Ctrl+C.

The shutdown process checks for the authenticity and thepermissions of the user invoking the shutdown operation, and isallowed only if the user has the proper permissions.

Shutting down the IEMS server from the command line7 To shutdown the server using the servman command, start the

command line interface and type

/opt/servman/bin/servstop IEMS

System response

Stopping group using servstopThe I-EMS Server on host "192.168.4.176" wassuccessfully shutdownIEMS Stopped

--End--


NN10450-900 06.023 October 2008


.


Powering down the XA-Core

Use this procedure to power down a DMS switch as follows:

• in the event of an emergency, for example, flooding or fire

• to protect equipment if the available functioning voltage at the powerdistribution center (PDC) falls below -43.75 V dc

• when instructed by the next level of support

Procedure stepsCAUTIONThis procedure results in a complete loss of subscriberservice. Nortel recommends that before you perform thisprocedure, you should contact emergency Technical AssistanceServices (ETAS) of Nortel or contact your next level of support.

Step Action

1 During emergency shutdown of the switch, at your currentlocation, notify network management personnel of the impendingservice interruption.

2 Notify emergency services (police, fire, ambulance) of theimpending service interruption.

3 If the switch must be shut down immediately due to dangerousenvironmental conditions then go to step 5.

4 If there is time (one half hour or more) to shut down the switch inan orderly fashion then go to step 7.

5

ATTENTIONTurning off the switch in this manner should be done only if absolutelynecessary, as current arcing may occur.

Turn off the power to the power distribution centers (PDCs) bydisconnecting the power feeds at the power room.

6 You have completed the procedure.

7 Using office records, identify the peripheral modules that hostemergency services (such as fire, police, and ambulance), sothat these peripherals can be shut off last.


NN10450-900 06.023 October 2008


.

Procedure steps 361

8

ATTENTIONOlder peripheral modules, such as line modules and digital carriermodules, use universal tone receivers resident in maintenance trunkmodules.

Turn off the power converter for each maintenance trunkmodule shelf, except those identified in step 7 as essential foremergency service lines.

9 Turn off the inverters for all MAPs and printers, except theoperator MAP and one printer.

10 Turn off the power converters on all digital trunk controllers andtrunk modules, except those identified in step 7 as essential foremergency service communications.

11 Turn off the power converters on each line module shelf, exceptthose identified in step 7 as hosting emergency service lines.

12 Turn off the power converters on all line concentrating modules,except those identified in step 7 as hosting emergency servicelines.

13 Turn off the power converters on all line group controllersand line trunk controllers, except those identified in step 7 asessential for emergency service communications.

14 Turn off the power on all remaining peripheral modules, leavingessential service peripheral modules until last.

15

ATTENTIONTo power down the ENET and the LPP, unseat and then reseat thepower converters.

Turn off the power for the network modules, link peripheralprocessor, and input/output controllers (IOCs).

16 Turn off the power for all remaining devices, including theinverter that supplies the operator MAP, and any externalprinters, tape drives, or disk drives.

17 Turn off the power for the XA-Core. Power down both SIMcards in the XA-Core. In each SIM card you must turn off threebreakers.

18 Turn off the power for the message switch. Power down oneplane by turning off the power converters. Power down thesecond plane by unseating and then reseating the powerconverters.


NN10450-900 06.023 October 2008


.


19 Turn off the power to the power distribution centers (PDCs) bydiscontinuing the A and B feeds at the power room.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 363

Performing a partial power down of the MG 9000

This procedure is used to perform a partial power down of an MG 9000.

Procedure steps

Step Action

1 At the MG 9000 Manager, determine the inactive Supercore, ITP,and ITX cards.

2 Lock each inactive card using the MG 9000 Manager.

3 Take the cards offline using the MG 9000 Manager.

4 After the cards are offline, they can be manually unseated.

--End--


NN10450-900 06.023 October 2008


.


Performing a partial power down of the MediaGateway/Multiservice Switch 15000

Use this procedure to perform a partial power down of a MediaGateway/Multiservice Switch 15000 and to move the services from a selectset of cards to another set of cards. Then it powers down the select set ofcards as well as any cards that host the standby ports.

The following slots on each of the two shelves will remain powered up:

• 0

• 3

• 4

• 7

• 8

• 11

• 12

• 15

The high level steps of this procedure include the following activities:

• ensuring that the LAPS ports are active on the powered-up cards andinactive on powered-down cards

• ensuring the active PBG port is on a powered-up card

• ensuring the PBG port that connects to the SAM21 shelf controller isactive

• ensuring the correct DS3 card remains active

• switching off selected power breakers

Procedure steps

Step Action

1 Ensure that the active lines are on the cards to remain poweredup by typing

> d laps/* nearEndRxActiveLine, workingLine,protectionLine

.


NN10450-900 06.023 October 2008


.

Procedure steps 365

2 If there are any LAPS ports on a card that will be powered down,a protection switch needs to be performed.

To switch from the protection line to the working line, type

> switch -protectionworking laps/x

To switch from the working line to the protection line, typ

> switch -workingtoprotectioon laps/y

3 One of the HIOPs on the XA-Core may be powered down forpower conservation reasons. Determine which PBG port theHIOP corresponds to by typing

> d pbg/* working line


4 Determine which PBGs are connected to the XA-Core by typing

>d atmif/* remoteatmif

5 Match the PBG port number with the AtmIf number.

6 Display the Sonet ports to determine whether the remote-endHIOP cards are still in service by typing

>d lp/10 sonet/3 operational

followed by typing

>d lp/11 sonet/0 operational

7 Determine the states of the losAlarm and rxAisAlarm.

If the losAlarm is On, then the corresponding HIOP card islikely powered down. If the rxAisAlarm is On, the HIOP card isprobably locked.

8 Verify that this HIOP card is selected to be powered down forpower conservation. The other Sonet port should have no alarmsraised under the operational group.

9 Select AtmIFs with matching instance numbers. For example, ifpbg/1100 and 1003 are provisioned, type

>d atmif/1100 vcc/* vcd tm atmService Category

>d atmif/1003 vcc/* vcd tm atmService Category

10 Determine which PBG port is active by displaying thecorresponding AtmIf vcc traffic counts. Type

>d atmif/X vcc/Y txcell, rxcell

11 The active PBG port will have incrementing txcell and rxcellcounts. Ensure that the active PGB port’s workingLine is on oneof the cards that will remain in-service (0, 3, 4, 7, 8, 11, 12, or15).


NN10450-900 06.023 October 2008


.


12 If the PVG port’s workingLine is not on one of the cards thatwill remain in-service, perform a Swact of the SAM21 ShelfController.

13 Verify that the other PBG port to this SAM21 shelf now hasincrementing txcell and rxcell counts.

14 For a 4pDS3Ch or 12pDS3 card pair in slots 14 and 15, type

>d -p lp/14 activeCard, mainCard, spareCard Lp/14

15 Ensure that the active card is in the set of cards that will remainin-service. If not, switch Lp activity by typing

>switch lp/14

.

16 Ensure that the activeCard from step 14 matches the MG9000 equipment that will remain in-service during the powerconservation activity. If not, the MG 9000 equipment that ispowered down will need to be switched.

17 Manually switch off the following breakers on the upper shelf:

• B2.2

• B2.5

• A2.2

• A2.5

18 Manually switch off the following breakers on the lower shelf:

• B1.2

• B1.5

• A1.2

• A1.5

--End--


activeCard Shelf Card/14

mainCard Shelf Card/14

spareCard Shelf Card/15

Job aidExample response


NN10450-900 06.023 October 2008


.

Job aid 367

Pbg/*+=====+--------------------+----------------------------------------| Pbg | working |Response+=====+--------------------+----------------------------------------| 1003|Lp/10 Sonet/3 || 1100|Lp/11 Sonet/0 |


NN10450-900 06.023 October 2008


.


Performing a partial power down of the USP

Use this procedure to perform a partial power down of a USP.

Procedure steps

Step Action

1 At the USP frame, unseat the front panel and back panel CCcards in Slot 18, beginning with the CC Slot 18 card on each ofthe extension shelves.

2 Unseat the front panel and back panel CC card in Slot 18 on theControl shelf.

3 Open the RTC system node provisioning and maintenancewindow.

4 Click on the System Mgmt item on the main menu to open theSystem Configuration window.

5 Click on the icon for the control CAM shelf to open theshelf_name window.

6 Click on the icon for an RTC system node.

An operational-state of enabled indicates that the card isin-service. An activity state of inactive indicates that theassociated card is the inactive RTC.

7 At the USP frame, ensure the LEDs on the slot 13 and 16 frontpanel cards are not lit.

8 Unseat the inactive RTC card identified in step 6, its associatedSCSI (front panel), and the associated cards on the back panel.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 369

Performing a partial power down of the EthernetRouting Switch 8600

Use this procedure to perform a partial power down of an Ethernet RoutingSwitch 8600.

Procedure steps

Step Action

1 At the chassis, each chassis has its own BIP circuit breaker.Set the BIP circuit breaker to the off position to work in simplexmode.

2 Turn one of the three DC power supplies off. This will leave 2DC power supplies to support the remaining chassis.

--End--


NN10450-900 06.023 October 2008


.


Performing a partial power down of the Netra 240server

Use this procedure to perform a partial power down of the N240 servers.The N240 servers are commissioned with one active and one inactive unit.This procedure shuts down the inactive unit.

Prerequisites• You must have the root user password for the N240.

• You must have the IP address for the inactive unit.

Procedure steps

Step Action

1 At the N240 server, Telnet or SSH into the inactive server andlogon as the root user.

2 Type

#init 0

to shutdown the server and to close the Telnet or SSHconnection.

3 At this point, the inactive server can be turned off at the circuitbreaker.

--End--


NN10450-900 06.023 October 2008


.

Prerequisites 371

Performing a partial power down of the XA-Core

Use this procedure to maintain emergency backup power for a DMSSuperNode or a DMS SuperNode SE switch. Use this procedure when theswitch has an eXtended Architecture Core (XA-Core) configuration.

This procedure reduces the loss from emergency batteries to a minimumby closure of power to equipment in stages. The equipment shutdown isnot necessary to maintain subscriber service. Equipment shutdown is inmoving up order based on its effect on switch reliability. The equipmentshutdown begins with less required equipment, such as spare printers, andends with more required equipment.

Prerequisites• Take into consideration the configuration and condition of your switch.

Also take into consideration the expected period of the power outage,and the quantity of reserve power available. Continue as follows:

ATTENTIONIf you receive a warning message for a loss of service if you busy a planeor unit, do not continue. Clear the problem that can cause a loss of servicebefore you busy the plane or unit. Also you can leave both planes or unitsof that subsystem in service.

• Complete the number of steps of this procedure as your set ofconditions needs. For example, if you expect power to restore, youcan decide to leave important systems to operate in a duplex mode.The message switch (MS) is an example of a system that can have aduplex mode. Equally for reliability, you can decide to leave both unitsin service on peripheral modules required for emergency service lines.

• This procedure requires a condition when this procedure instructs youto busy down one plane or unit of a system. The condition is that themate plane or unit you leave in service, is fault free and can operatenormally.

• When possible, take the same plane or unit out of service on eachsubsystem (for example, ENET plane 0, LIM unit 0, MS 0). This actiondecreases the possible result of error and reduces recovery time.


NN10450-900 06.023 October 2008


.


Procedure stepsCAUTIONPotential service interruption or extended outageNortel recommends that you call Emergency TechnicalAssistance Services (ETAS) of Nortel. Also call your next levelof support before you perform this procedure.

CAUTIONPotential loss of service or extended outageThis procedure is only for conservation of emergency backuppower. Do not use this procedure or sections for equipmentmaintenance purposes.

Step Action

1 At your current location, use office records to identify and recordthe power converters that supply the MAPs and printers for theswitch.

2 Turn the power off on all power converters identified in step1. Do not turn the power off for the power converters whichsupplies the operator’s MAP and one printer connected to IOC 0.

3 At the MAP terminal, to confirm that an office image is availableto reload the switch if a total turn off of power becomesnecessary, type:

>AUTODUMP STATUS

.


4 If an office image is available then go to step 7.

5 If an office image is not available then go to step 6.

6 Record the office image. Perform the procedure, "How to recordan XA-Core office image on a disk" in this document. Return tothis step when you complete the procedure to record the officeimage.

7

ATTENTIONCards that have an effect on service include digitone receiver cards(NT2X48), centralized automatic message accounting (CAMA) cards(NT2X66), and digital recorded announcement machine (DRAM)cards.

Turn off power for all maintenance trunk modules (MTM) in theoffice. Do not turn power off if the MTM contains cards that havean effect on service. To turn off power perform the procedure,


NN10450-900 06.023 October 2008


.

Procedure steps 373

"Emergency shutdown of maintenance trunk modules" inRecovery Procedures () , 297-8021-545.

8 Turn off power for one of the line module controllers (LMC)(NT2X14 shelf) in each double-bay line module (LM) pair in theoffice. To turn off the power, perform the procedure, "Emergencyshutdown of one half of a line module pair" in RecoveryProcedures () , 297-8021-545.

9 Turn off power for one unit of all line concentrating modules(LCM) in the office. To turn off the power, perform the procedure,"Emergency shutdown of one unit of LCMs" in RecoveryProcedures () , 297-8021-545.

10 Turn off power for one unit of all line group controllers (LGC),line trunk controllers (LTC), and digital trunk controllers (DTC)in the office. To turn off the power, perform the procedure,"Emergency shutdown of one LGC, LTC, and DTC unit" inRecovery Procedures () , 297-8021-545.

11 Turn off power for one plane of all network shelves in the office.

12 For ENET, perform the procedure, "Emergency shutdown ofone enhanced network plane" in Recovery Procedures () ,297-8021-545.

13 For JNET, perform the procedure, "Emergency shutdown ofone junctored network plane" in Recovery Procedures () ,297-8021-545.

14 If you removed power from a complete network frame in steps 12or 13, turn off power for the cooling fans for the frame. To turnoff power, remove the correct power fuses from the PDC.

15 Busy and power down one local message switch in the linkperipheral processor (LPP). Perform the procedure, "Emergencyshutdown of one LIM unit on each LPP" in Recovery Procedures() , 297-8021-545.

16 Turn off power for one unit of all CCS7 message switch andbuffers (MSB7) in the office. To turn off power, perform theprocedure, "Emergency shutdown of one unit of MSB7s" inRecovery Procedures () , 297-8021-545.

17 Turn off power for one message switch (MS) plane. To turnoff power, perform the procedure, "Emergency shutdown ofone DMS SuperNode MS plane" in Recovery Procedures () ,297-8021-545.

18 If your office has a remote oscillator shelf (NT3X9507), busy theclock related to the MS number. The MS number is for the MSthat you turned off power in step 17. To busy the clock, perform


NN10450-900 06.023 October 2008


.


the procedure, "Emergency shutdown of one remote ascillatorshelf plane" in Recovery Procedures () , 297-8021-545.

--End--

Job aidExample of a MAP response:

Successful Image: 990215_CMTaken: 1999/03/17 21:47:32:04.138 WED.On Volume: F17LIMAGESuccessful Image: 990215_MSTaken: 1999/03/17 21:47:32:04:138 WED.On Volume: F17LIMAGESCHEDULED-Image Dump is ON.Next scheduled dump is MONDAY at 22:30 hours.Next image to be dumped on F02LIMAGE.


NN10450-900 06.023 October 2008


.

375.

Network power upThis chapter describes restarting the network for the Nortel Carrier VoIPsolutions.

Network power up task flow

This task flow shows you the sequence of procedures you perform topower up the network.


NN10450-900 06.023 October 2008


.

376 Network power up

Figure 25Powering up the network procedures - Part 1


NN10450-900 06.023 October 2008


.

Job aid 377



NN10450-900 06.023 October 2008


.



Network power up procedure navigation

• “Powering up the XA-Core” (page 380)

• “Powering up the Message Switch” (page 396)

• “Powering up the Enhanced Network” (page 399)

• “Powering up an Ethernet Routing Switch 8600” (page 401)

• “Powering up the Link Peripheral Processors” (page 402)

• “Powering up the SDM” (page 405)

• “Powering up a Netra 240 server” (page 406)

• “Powering up the Border Control Point Manager” (page 407)

• “Powering up the SAMF frame” (page 408)

• “Powering up the Call Control Frame” (page 410)

• “Powering up a USP” (page 412)

• “Powering up a Media Gateway/Multiservice Switch 15000” (page 414)


NN10450-900 06.023 October 2008


.

Job aid 379

• “Powering up a Media Gateway/Multiservice Switch 7400” (page 415)

• “Powering up the MDM workstation” (page 417)

• “Powering up an SPM device” (page 418)

• “Powering up the MCS servers” (page 420)

• “Powering up a Border Control Point” (page 424)

• “Powering up the IPmedia 2000 shelves” (page 425)

• “Powering up the SAM16 shelves” (page 426)

• “Powering up an MG 9000 device” (page 427)

• “Restoring certificates and Pre-shared Keys for IPSec” (page 432)

• “Restoring the MG 9000 manager system” (page 436)

• “Restoring files from a DVD-RW” (page 437)

• “Reloading or restarting a SAM21 Shelf Controller” (page 440)

• “Restarting or rebooting a GWC card” (page 441)

• “Performing a partial power up of the Netra 240 server” (page 443)


NN10450-900 06.023 October 2008


.


Powering up the XA-Core

Use this procedure to power up a dead switch that has an eXtendedArchitecture Core (XA-Core). The switch can be a DMS SuperNode orSuperNode SE switch. The switch is dead if the complete switch is withoutpower. The power loss results from a loss or interruption of A and B dcpower feeds to the power distribution center (PDC).

Procedure stepsCAUTIONCall ETAS or your next level of supportIn the event of a dead system, call the Emergency TechnicalAssistance Services (ETAS) of Nortel. Also call your next levelof support before you perform this procedure.

DANGERRisk of electrocutionDo not touch the cabinet wiring. Connections with unshieldedcabinet wiring can result in electric shock. Only qualified powermaintenance personnel can perform the voltage measurementsin step 3.

Step Action

1 At the PDC, when possible after detection of the power outage,remove all the fuse holders for the line concentrating equipment(LCE) talk batteries, trunk module equipment (TME) talk batteriesand PDC filter fuses from the correct PDCs

ATTENTIONThe location of the fuse holders in the fuse panel can vary, dependingon your office configuration. For help in locating the fuse holders, seethe fuse assignment diagram for your office. Also call your next levelof support to help you locate the fuses.

2 If the switch power is -48 V dc then go to step 4.

3 If the switch power is -60 V dc then go to step 8.

4 Continue when you know of restored power at the power plantfor your office. Power maintenance personnel must check forrestored power at each PDC. At the rear of each PDC, measurethe dc voltage across the A feed bus and the battery return plate.Repeat the dc voltage measurement for the B feed bus. Power iscorrect when the voltage on each feed is -48 V dc.


NN10450-900 06.023 October 2008


.

Procedure steps 381

ATTENTIONPower can be at a nominal potential of -48 V dc. Under conditionsthat are not normal, the operating voltage can range from -43.75 V dcto -55.8 V dc. A not normal condition is a commercial power failure

5 If the switch has power retrieval then go to step 11.

6 If the switch has no power retrieval then go to step 10.

7 Continue when you know of restored power at the power plantfor your office. Request power maintenance personnel to checkfor restored power at each PDC. At the rear of each PDC,measure the dc voltage across the A feed bus and the batteryreturn plate. Repeat the dc voltage measurement for the B feedbus. Power is correct when the voltage on each feed is -60 V dc.

ATTENTIONPower can be at a nominal potential of -60 V dc. Under conditionsthat are not normal, the operating voltage can range from -57.4 V dcto -67.7 V dc. A not normal condition is a commercial power failure.

8 If power has power retrieval then go to step 11.

9 If power has no power retrieval then go to step 10.

10 At the power room, for help in restoring power to the PDC, callthe personnel responsible for maintenance of power at your site.

When power restores to the PDC, return to this point.

11 At the PDC, inspect the alarm indication fuses for the XA-Coreand the network cabinets.

12 If there are blown fuses, go to step 14.

13 If there are no blown fuses, go to step 22.

14 Replace the blown cartridge fuse in the rear of the fuse holder.Make sure that the amperage of the replacement cartridge fusematches the amperage marked on the PDC.

15 Remove the blown alarm-indication fuse from the front of thefuse holder.

16 Re-insert the fuse holder, with the alarm-indication fuseremoved, into the PDC.

17 Get an alarm-indication fuse for replacement.

18 Insert the alarm-indication fuse that is for replacement into thefuse holder.

19 If the replacement fuse is not successful and blows repeatedly,go to step 21.

20 If the replacement fuse is successful, go to step 22.

21 Call your next level of support for help.


NN10450-900 06.023 October 2008


.


Continue when you complete replacement of all blown fuses andrestored power to the XA-Core and network cabinets.

22 If a second person is available to help in the recovery, continuethis procedure with two sets of tasks. Request the secondperson to restore power from the pdc to the peripheral moduleframes. The second person restores power by use of step 82through step 97 of this procedure. While the second personrestores power, you recover the core and network by completionof step 23 through step 65. If one person is available, recoverthe core and network first.

23 If the switch has a remote oscillator shelf, go to step 25.

24 If the switch does not have a remote oscillator shelf, go to step26.

25 At the remote oscillator shelf, turn on the power converters forthe shelf.

26 At the XA-Core cabinet, determine if the switch is a SuperNodeswitch or a SuperNode SE switch.

27 If the switch is a SuperNode switch then go to step 29.

28 If the switch is a SuperNode SE switch then go to step 32.

29 Turn on circuit breakers for shelf interface module (SIM) A. Turnon the three switches for circuit breakers A1, A2, and A3. TheSIM A card is in slot 3R of the XA-Core shelf.

30 Turn on circuit breakers for shelf interface module (SIM) B. Turnon the three switches for circuit breakers B1, B2, and B3. TheSIM B card is in slot 16R of the XA-Core shelf. Go to step 33.

31 Turn on circuit breakers for shelf interface module (SIM) A. Turnon the two switches for circuit breakers A1 and A2. The SIM Acard is in slot 3R of the XA-Core shelf.

32 Turn on circuit breakers for shelf interface module (SIM) B. Turnon the two switches for circuit breakers B1 and B2. The SIM Bcard is in slot 16R of the XA-Core shelf.

33 If all the power converters do not have power, go to step 35.

34 If all the power converters have power, go to step 37.

35 To power up the frame perform the procedure, "Clearing anExt FSP DPCC cabinet major alarm" in Alarm Clearing andPerformance Monitoring Procedures, 297-8001-543 (NorthAmerican market) or 297-9051-543 (International market).

When you completed the procedure, return to this point.

36 Go to step 27.

37 At the XA-Core reset terminal, monitor the XA-Core resetterminal to determine if the switch has booted.


NN10450-900 06.023 October 2008


.

Procedure steps 383

When the switch boots, the XA-Core reset terminal displaysa response to indicate a boot in progress. The response alsodisplays different diagnostic messages and alphanumericaddresses. When the switch has completely booted, an A1appears on the RTIF display.

38 If the response has an A1 then go to step 40.

39 If the response has no A1 after approximately 15 min then goto step 180.

40 At the MAP terminal, see the Caution statement.

CAUTIONExtended service interruptionThe exact log on procedure can vary, depending onyour office configuration. If you need additional help,call the personnel responsible for the next level ofsupport.

Determine if you have to log on.

ATTENTIONThe log on message indicates that you have to manually log on. Anautomatic log on can occur if the office parameters have automaticlog on.


Please Login.

41 If the log on is not automatic, then go to step 43.

42 If the log on is automatic, then go to step 47.

43 Press the break key.


?

44 Log on to the MAP terminal.

>LOGIN


Enter User Name

45 Enter the user name.

>user_name


Enter Password

46 Enter the password.


NN10450-900 06.023 October 2008


.


>password


SuperNode1 Logged in on 1997/01/15 at 20:37:17

CAUTIONAll customers must follow the sequence ofsteps set out in this procedureDo not interrupt this procedure at this point to clearan alarm. If a TOD critical alarm appears under theAPPL level in the alarm banner, and if the systemuses Network Time Protocol (NTP), you mustcomplete all steps in the sequence shown. You willclear the TOD critical alarm by completing step 58.(For information on NTP, see step 58.)

47 To turn on priority, type:

>PRIORITY ON



>Pref

48 Determine if the system time is correct.

>TIME


Time is 14:55:50

49 If the system time is not correct then go to step 51.

50 If the system time is correct, then go to step 53.

51 Enter the correct time (by use of the 24 hour clock).

>SETTIME hh mm


Warning: There is an automated TOD clock changerequest scheduled on:1997/10/15 at 1:00 (see table DSTTABLE).Do you want to proceed with this request?Please confirm ("YES", "Y", "NO", or "N")

52 Confirm the command.

>YES


Time is 20:40:00 on WED 1997/10/15.


NN10450-900 06.023 October 2008


.

Procedure steps 385

53 Determine if the system date is correct.

54 If the system date is not correct, then go to step 56.

55 If the system date is correct, then go to step 58.

56 Enter the correct date.

>SETDATE dd mm yyyy


Warning: There is an automated TOD clock changerequestscheduled on:1997/10/15 at 1:00 (see table DSTTABLE).Do you want to proceed with this request?Please confirm ("YES", "Y", "NO", or "N")

57 Confirm the command.

>YES


Date is WED. 15/OCT/1997 00:00:00

58 If the system uses Network Time Protocol (NTP) as the timingreference, and if a TOD critical alarm appears under the APPLlevel in the alarm banner, perform the procedure titled "Howto check and adjust the XA-Core TOD" in the Nortel XA-CoreFault and Performance Management ( (297-8991-510)) . Byperforming that procedure, you will clear the TOD critical alarm.Return to this point when finished.

ATTENTIONIn the German market only, switches can use Network Time Protocol(NTP) as the timing reference for the time-of-day clock. The systemuses Network Time Protocol if the value of the SNTP_CLIENT officeparameter in table OFCENG has been set to Y. For information aboutthe office parameter, see the section titled "XA-Core data schemaoverview" in the Nortel XA-Core Reference Manual ( (297-8991-810)).

59 At the MAP terminal, access the NET level of the MAP display.

>NET


NET

11111 11111 2222222222 33Plane 01234 56789 01234 56789 0123456789 010 00001 0000JNET


NN10450-900 06.023 October 2008


.


60 Manually busy the network module for return to service.

>BSY plane_no pair_no

61 Return the network module to service.

>RTS plane_no pair_no

62 Repeat step 60 and step 61 for each JNET shelf.

When all JNET shelves recover, continue this procedure.

63 Determine if there are additional input output controller (IOC)and maintenance and administration position (MAP) terminalsto recover.

64 If recovery of additional IOCs and MAP terminals is notcomplete, then go to step 66.

65 If recovery of additional IOCs and MAP terminals is complete,then go to step 79.

66 Restore power to all remaining power inverters in the office.

67 At the IOC, locate the IOC for recovery.

68 If recovery is for an IOC, then go to step 70.

69 If recovery is for an IOM, then go to step 74.

70 Turn on the power converters on the IOC.

ATTENTIONThe version of IOC determines if the IOC has one or two powerconverters.

71 While you press the reset button on one of the IOC powerconverters, lift the related circuit breaker to turn on the FSP.

72 Release the reset button.

73 Repeat step 67 through step 72 for each IOC for recovery.

74 Access the input output device (IOD) level of the MAP display.

>IOD

75 Access the IOC level of the MAP display for the IOC forrecovery.

>BSY ioc_no

76 Return the IOC or IOM to service.

>RTS ioc_no

77 Repeat step 75 and step 76 for each IOC or IOM for recovery.

78 Log on to additional MAP terminals as required.

ATTENTIONStep 44 through step 46 describe how to log on to the MAP terminal.


NN10450-900 06.023 October 2008


.

Procedure steps 387

79 At the PDC, step 80 through step 104 describe how to restorepower from the PDC to Series I and Series II peripheral moduleframes.

80 If the PDC power to the PM frames does not restore correctly,then go to step 82.

81 If the PDC power to the PM frames restores correctly, then goto step 105.

82 Get a 100-W, 120-V light bulb installed into a socket thathas pigtail leads or tool number T000655 (CPC numberNTA0600512), that has a fuse holder-style connector instead ofpigtail leads for easier insertion

83

WARNINGPossible equipment damage or extendedservice interruptionUse correct fuses. When you return fuses to thePDC, make sure that the amperage of the fusesis correct. The fuse amperage must match theamperage marked on the PDC.

At the first empty fuse slot in the PDC, connect the leads of thecapacitor charging tool. Connect the leads across the contactsfor the fuse holder until the lamp decreases brightness. If youuse a charging tool with a fuse holder-style connector, insertthe connector into the slot. Insert the connector until the lampdecreases brightness.

84 Remove the capacitor charging tool and immediately insert againthe correct fuse holder into the slot.

85 Repeat steps 83 and step 84 for the LCE talk battery, TME talkbattery, and PDC filter fuse holders you removed.

86 Determine if any alarm-indicating fuses blew.

ATTENTIONThe fuse alarm-indicator lamp lights when an alarm-indicating fuseblows.

87 If no alarm-indicating fuses have blown, then go to step 89.

88 If any alarm-indicating fuses have blown, then go to step 180.

89 Locate a fuse holder with a blown alarm-indicating fuse.

ATTENTIONYou can replace blown fuses in any order.

90 The cartridge fuse in the fuse holder has blown. Remove thefuse holder from the PDC.


NN10450-900 06.023 October 2008


.


91 Replace the blown cartridge fuse in the rear of the fuse holder.Make sure that the amperage of the replacement cartridge fusematches the amperage marked on the PDC.

92 Remove the blown alarm-indicating fuse from the front of thefuse holder.

93 Insert again the fuse holder, with the alarm-indicating fuseremoved, into the PDC.

94 Get a replacement alarm-indicating fuse.

95 Insert the replacement alarm-indicating fuse into the fuse holder.

96 Determine if the alarm-indicating fuse blows.

ATTENTIONThe fuse alarm indicator lamp lights when an alarm-indicating fuseblows.

97 If the alarm-indicating fuse is not blown, then go to step 99.

98 If the alarm-indicating fuse is blown, then go to step 89.

99 Determine if you replaced all the blown alarm-indicating fuses.

100 If you have replaced all the blown alarm-indicating fuses thengo to step 102.

101 If you have not replaced all the blown alarm-indicating fuses thengo to step 89.

102 Determine if the fuse alarm indicator lamp lit.

103 If the fuse alarm indicator lamp is not lit, then go to step 105.

104 If the fuse alarm indicator lamp is lit , then go to step 180.

105 At the PM frames, select a peripheral module (PM) frame topower up.

ATTENTIONThe PM frames can power up in any order.

106 Locate the frame supervisory panel (FSP) and the powerconverters on the frame.

107 Determine if the FSP for the frame has fuses or circuit breakers.

108 If the FSP has fuses, then go to step 110.

109 If the FSP has circuit breakers, then go to step 124.

110 Determine if the power converters have Power Reset buttons orPower Reset switches.

111 If the power converters have power Reset buttons, then go tostep 113.

112 If the power converters have power Reset switches, then go tostep 117.


NN10450-900 06.023 October 2008


.

Procedure steps 389

113 To turn on each power converter press and hold its Power Resetbutton for 2 s.

ATTENTIONThe Converter Fail light goes off when the power converter turns on.

114 Determine if all the power converters turn on correctly, indicatedby all the Converter Fail lights going off.

115 If all the Converter Fail lights are off, then go to step 127.

116 If all the Converter Fail lights are not off, then go to step 130.

117 To turn on each power converter pull out the power switch andtoggle it to the Power Reset position.


118 Determine if all the power converters turns on correctly, indicatedby all the Converter Fail lights are off.



121 Turn on each power converter by toggle the circuit breaker to theON position.

122 Press and hold the Power Reset button for 2 s.

123 Release the circuit breaker and the Power Reset button.


124 Determine if all the power converters turn on correctly, indicatedby all the CONVERTER FAIL lights are off.



127 Determine if all PM frames turn on.

128 If all the PM frames turn on yes, then go to step 136.

129 If all the PM frames turn on no, then go to step 130.

130 Determine if an attempt was made to power up the remainingPM frames.

131 If power up has not been attempted, then go to step 133.

132 If power up has been tried and failed, then go to step 135.

133 Power up the next PM frame.

134 Go to step 106.

135 To power up the remaining PM frames perform the correctprocedures in Alarm Clearing and Performance Monitoring


NN10450-900 06.023 October 2008


.


Procedures () , 297-8001-543 (North American market) or297-9051-543 (International market).

136 At the MAP terminal, access the SRSTATUS level of the MAPdisplay.

>MAPCI;MTC;SRSTATUS


SRSTATUS0 Quit OVERALL STATUS Pend: 0% Inprg: 0%Comp: 100% Fail: 0%2 View_ View: SYSTEM14:08:303 List_ Pend InPrg Comp Fail PendInPrg Comp Fail4 MS 0 0 2 0 IOD5 5 30 25 NET 0 0 6 0 Other21 3 13 36 SER1 0 41 0 07 SER2 0 39 0 08 SER3 0 0 37 0910 MTC:11 STATUS:

137 From the MAP display, determine the recovery status of theSeries I and II PMs.

ATTENTIONSeries I PM recovery status displays to the right of the word "SER1"in the MAP display. Series II PM recovery status displays to the rightof the word "SER2" in the MAP display. Recovery status can be oneof pending, in progress, complete, or failed.

138 If the recovery status is not zero, then go to step 140.

139 If the recovery status is zero, then go to step 142.

140 Determine from office records or other office personnel whichPMs to manually recover first.

141 To manually recover the PMs in the required order, performthe correct alarm clearing procedures in Alarm Clearing andPerformance Monitoring Procedures () , 297-8001-543 (NorthAmerican market) or 297-9051-543 (International market).

142


NN10450-900 06.023 October 2008


.

Procedure steps 391

CAUTIONLoss of billing dataDifferent billing systems than automatic messageaccounting (AMA) or additional billing system, canbe in your office configuration. Call your next level ofsupport to determine if other billing systems are inyour office, and if you require recovery action.

Access the device independent recording package (DIRP) levelof the MAP.

>IOD;DIRP

143 Determine the state of the recording volumes for the billingsystem.

>QUERY subsystem ALL


SSNAME SSNO SEQNO ROTATES POOLNO PARLPOOL EMERGENCYAMA 0 1 6 9 62 ***YES***REGULARFILE(S) STATE VOLUME RECCOUNT BLOCK E V V_B VLID FNUM FRN#ACTIVE NONEgSTANDBY1 NONEPARALLELFILE STATE VOLUME BLOCK E V V_B VLIDNUM FRN#NONEREGULAR VOLUME(S)VOL# VOLNAME STATE IOC CARD VOL FSEG ROOMVLID FILESREGULAR SPACE

144 If the state of the recording volumes for the billing system hasno volumes allocated, as indicated by the word NONE under thestate header on the MAP display, then go to step 150.

145 If the state of the recording volumes for the billing system hasany volume is IN ERROR, as indicated under the REGULARVOLUME(S) header on the MAP display, then go to step 147.

146 If the state of the recording volumes for the billing system hasall volumes are READY, as indicated under the REGULARVOLUME(S) header on the MAP display then go to step 151.

ATTENTIONDifferent billing systems than automatic message accounting (AMA)or additional billing system, can be in your office configuration. Callyour next level of support to determine if other billing systems are inyour office, and if you require recovery action.

147 Reset any volumes that are IN ERROR.


NN10450-900 06.023 October 2008


.


>RSETVOL vol_name

148 If the volumes reset passed, then go to step 151.

149 If the volumes reset failed, then go to step 180.

150 Perform the procedure, "Allocating recording volumes inthe DIRP utility" in Routine Maintenance Procedures () ,297-8001-546 (North American market) or 297-9051-546(International market). When you complete the procedure, returnto this point.

151 Determine the state of the DLOG recording volumes.

>QUERY DLOG ALL


SSNAME SSNO SEQNO ROTATES POOLNO PARLPOOL EMERGENCYDLOG 2 1 102 10 NONE ****YES***.REGULARFILE(S) STATE VOLUME RECCOUNT BLOCK E V V_B VLID FNUM FRN#ACTIVE AVAIL S01DDLOG 6 6 0 22 NO 8447 0013 204DSTANDBY1 AVAIL S00DDLOG 0 0 0 23 NO 84080014 309B.REGULAR VOLUME(S)VOL# VOLNAME STATE IOC CARD VOL FSEG ROOMVLID FILES22 S01DDLOG READY N/A N/A 7 5 188447 A23 S00DDLOG READY N/A N/A 8 4 188408 S1REGULAR SPACEVOL# VOLNAME STATE SEGS EXP UNEXP TOTAL22 S01DDLOG READY 5 13 0 1823 S00DDLOG READY 4 14 0 18

152 If the state of DLOG recording volumes is no allocated volumes,as indicated by the word NONE under the state header on theMAP display, then go to step 158.

153 If the state of DLOG recording volumes is any volume is INERROR, as indicated under the REGULAR VOLUME(S) headeron the MAP display then go to step 155.

154 If the state of DLOG recording volumes is all volumes areREADY, as indicated under the REGULAR VOLUME(S) headeron the MAP display then go to step 159.


NN10450-900 06.023 October 2008


.

Procedure steps 393

ATTENTIONDifferent billing systems than automatic message accounting (AMA)or additional billing system, can be in your office configuration. Callyour next level of support to determine if other billing systems are inyour office, and if you require recovery action.

155 Reset any volumes that are IN ERROR.

>RSETVOL vol_name

156 If the volumes reset passed, then go to

157 If the volumes reset failed, then go to step 180.

158 Perform the procedure, "Allocating recording volumes inthe DIRP utility" in Routine Maintenance Procedures () ,297-8001-546 (North American market) or 297-9051-546(International market). When you complete the procedure, returnto this point.

159 Determine from your next level of support if you need to recoverother DIRP systems (for example, JF, OM).

160 If you need to recover other DIRP systems, then go to step 162.

161 If you do not need to recover other DIRP systems, then go tostep 168.

162 Perform the correct procedures in Alarm Clearing andPerformance Monitoring Procedures () , 297-8001-543 (NorthAmerican market) or 297-9051-543 (International market). Whenyou complete the procedures, return to this point.

163 Determine if DIRP logs generated.

>LOGUTIL;OPEN DIRP

164 If DIRP log generated a yes, then go to step 166.

165 If DIRP log generated a no, then go to step 168.

166 See the Log Report Reference Manual () , 297-8001-840 (NorthAmerican market) or 297-9051-840 (International market), andtake the correct action.

When you complete the log report activities, return to this point.

167 Turn off priority.

>PRIORITY OFF

168 Access the SRSTATUS level of the MAP display.

>MAPCI;MTC;SRSTATUS



NN10450-900 06.023 October 2008


.



169 Determine the status of the switch recovery.

170 If the status of the switch recovery is any Series III PMs thatfailed recovery, then go to step 174.

171 If the status of the switch recovery is any Series I or II PMs thatfailed recovery, then go to step 176.

172 If the status of the switch recovery is any IODs or other devicesand services that failed recovery, then go to step 179.

173 If the status of the switch recovery is that the system hascompletely recovered, then you have completed the procedure.

174 Manually recover the PMs. For more information, see RecoveryProcedures, 297-8001-545 (North American market) or297-9051-545 (International market).

When you complete the procedure, return to this point.

175 Go to step 168.

176 Determine from office records or other office personnel whichPMs you can recover first.

177 To manually recover the PMs in the required order performthe correct alarm clearing procedures in Alarm Clearing andPerformance Monitoring Procedures () , 297-8001-543 (NorthAmerican market) or 297-9051-543 (International market).


178 Go to step 168.

179 To manually recover IODs and other devices and services,perform the correct procedure in this document. Also you cansee your site-related operating procedures.


NN10450-900 06.023 October 2008


.

Procedure steps 395

180 For additional help, call the personnel responsible for the nextlevel of support.

--End--


NN10450-900 06.023 October 2008


.


Powering up the Message Switch

Use this procedure to power up the Message Switch (MS) when recoveringfrom a power outage.

Procedure steps

Step Action

1 At the XA-Core frame, locate the NT9X31 and NT9X30 powerconverters for message switch 0 (MS 0) in slots 33F and 36F onthe MS 0 shelf.

2 Turn on the NT9X31 and NT9X30 power converters in slots 33Fand 36F of the MS 0 shelf at the same time. Lift and release thepower switches located on the faceplates of the converters.

3 Locate the NT9X31 and NT9X30 power converters for MS 0 inslots 1F and 4F on the MS 0 shelf.


5 Locate the NT9X31 and NT9X30 power converters for messageswitch 1 (MS 1) in slots 33F and 36F on the MS 1 shelf.


7 Locate the NT9X31 and NT9X30 power converters for MS 1 inslots 1F and 4F on the MS 01shelf.


9 At the MAP terminal, access the SRSTATUS level of the MAP.

>MAPCI;MTC;SRSTATUS



NN10450-900 06.023 October 2008


.

Procedure steps 397


10 Determine the recovery status of the MSs.

ATTENTIONMS recovery status displays to the right of the word "MS" in the MAPdisplay. Recovery status for each MS can be one of pending, inprogress, complete, or failed.

11 If the recovery status is MS failed recovery then go to step 20.

12 If the recovery status is MS continues to have pending recoverythen go to step 14

13 If the recovery status is a status other than failed or pendingrecovery then go to step 15

14 Wait until both MSs are either in recovery development or havecompleted recovery.

If neither MS indicates pending recovery, go to step 10.

15 Access the MS Clock level of the MAP display.

>MAPCI;MTC;MS;CLOCK

16 Synchronize the clocks.

>SYNC

17 If the SYNC command is successful then go this procedure iscomplete

18 If the SYNC command is failed then continue.

19 Record the reason for synchronization failure, as shown in theMAP response. Repeat the try to synchronize the MS clockslater, after networks and PMs are in service.


NN10450-900 06.023 October 2008


.


20 For additional help, call the personnel responsible for the nextlevel of support.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 399

Powering up the Enhanced Network

Use this procedure to manually power up the enhanced network (ENET) inthe event of a power failure.

Procedure steps

Step Action

1 At the ENET frames, locate the NT9X31 power converters inslots 1F and 33F on the ENET shelves.

2 To turn on the NT9X31 power converters lift and release thepower switches located on the faceplates of the converters.

3 Locate the NT9X30 power converters in slots 4F and 36F on theENET shelves.

4 Turn on the NT9X30 power converters lift and release the powerswitches located on the faceplates of the converters.

5 Determine if all the converters have power. Power is indicated byall the Converter Off lights going off.

6 If all the power converters have not power then go to step 8.

7 If all the power converters have power then go to step 9.

8 Power up the ENET frame. Perform procedure, "Clearing an ExtFSP DPCC cabinet major alarm" in the document, Alarm andPerformance Monitoring Procedures () , 297-8021-543.


9 At the MAP terminal, access the SRSTATUS level of the MAPdisplay.:

>MAPCI;MTC;SRSTATUS



NN10450-900 06.023 October 2008


.



10 From the MAP display, determine the recovery status of thenetwork.

ATTENTIONNetwork recovery status displays to the right of the word "NET" in theMAP display. Recovery status can be one of pending, in progress,complete, or failed.

11 If the status of any network element is failed then go to step 16

12 If the status of any network element is pending then go to step14

13 If the status of any network element is any other status then thisprocedure is complete.

14 Continue when there are no network elements that continue tobe pending recovery.

15 Go to step 10.

16 Manually recover the ENET. Perform procedure "Recovering theEnhanced Network" in Recovery Procedures () , 297-8021-545.

17 Go to step 9.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 401

Powering up an Ethernet Routing Switch 8600

Use this procedure to power up a Ethernet Routing Switch 8600.

Procedure steps

Step Action

1 At the Ethernet Routing Switch 8600 frame, turn the DC inputpower source on or reset the power source circuit breaker toprovide power to the power supply.

2 Turn the power supply switch for all three DC power supplies tothe on position.

ATTENTIONYou must turn on two of the power supply units within 2 seconds ofeach other. If you wait longer to turn on the second power supply,one of the power supplies could shut down. To correct this condition,turn off both power supplies, wait at least 30 seconds, and then turnon both power supplies again within 2 seconds.

--End--


NN10450-900 06.023 October 2008


.


Powering up the Link Peripheral Processors

Use this procedure to power up the Link Peripheral Processors (LPP) orfiberized LPPs (FLPPs) in the event of a power failure.

ATTENTIONThroughout this procedure, LPP is used to refer to both the LPP and FLPP.

Procedure steps

Step Action

1 If PDC has not power restored to the LPPs then go to step 3

2 If PDC has power restored to the LPPs then go to step 7.

3 If there are blown PDC fuses supplying the LPP,then go to step5.

4 If there are novisible blown fuses then go to step 6.

5 Replace the blown fuses.

ATTENTIONIf fuses blow repeatedly, call your next level of support for help.

When PDC power restores to the LPPs, continue this procedureat step 7.

6 Call the personnel responsible for maintaining power at your site,or see your next level of support for help.

When PDC power restores to the LPPs, continue this procedure.

7 Locate the LPPs for recovery.

8 At the LPP cabinet, release the locking levers and gently unseatthe NT9X74 cards on the link interface shelves(LIS). Refer to

9 Toggle the switch on each NT9X30/NTDX16 power convertercards on the link interface module (LIM) unit shelf.

10 Re-toggle the switch on each NT9X30/NTDX16 power convertercards on the link interface module (LIM) unit shelf.

11 If all of the cards did not turn on the power correctly, go to step13.

All of the CONVERTER OFF lights go off when the power turnson correctly.

12 If all of the cards turned on the power correctly, go to step 15.

All of the CONVERTER OFF lights go off when the power turnson correctly.


NN10450-900 06.023 October 2008


.

Procedure steps 403

13 To power up the frame, perform the procedure "Clearing andExt FSP LPP cabinet major alarm" in Alarm Clearing andPerformance Monitoring Procedures (297-8991-543) for NorthAmerican markets or (297-9051-543) for International markets.

14 Go to step 8.

15 Slide each of the NT9X74 cards back into it’s slot.

16 Gently push on the upper and lower edges of the faceplate ofeach card until the card is locked into the shelf.

17 Close the locking levers on each card.

18 Repeat steps 5 through 17 for each LPP in your office. Continuethis procedure when power has been restored to all LPPs.

19 Access the SRSTATUS of the MAP display>MAPCI;MTC;SRSTATUS

SRSTATUS0 Quit OVERALL STATUS Pend: 0% Inprg: 0% Comp: 100%Fail: 0%2 View_ View: SYSTEM14:08:303 List_ Pend InPrg Comp Fail Pend InPrg Comp Fail4 MS 0 0 2 0 IOD 5 5 30 25 NET 0 0 6 0 Other 21 3 13 36 SER1 0 41 0 07 SER2 0 39 0 08 SER3 0 37 0 0910 MTC:11 STATUS:

20 If the recovery status of the Series III PMs is not zero, go to step22.

ATTENTIONSeries III PM recovery status displays to the right of the word "SER3"(line 8) in the MAP display. Recovery status can be pending, inprogress, complete or failed.

21 If the recovery status of the Series III PMs is zero, this procedureis complete.

22 To manually recover the PMs, perform the procedure"Recovering Link Peripheral Processors" in RecoveryProcedures, (297-8021-545).

--End--


NN10450-900 06.023 October 2008


.


Job aidCard Slot position

NT9X74 7F, 32F

NT9X30 4F, 36F

NTDX16 1F, 4F, 33F, 36F


NN10450-900 06.023 October 2008


.

Procedure steps 405

Powering up the SDM

Use this procedure to power up the SuperNode Data Manager (SDM) thathouses the Communication Server 2000 Core Manager.

Procedure steps

Step Action

1 At the SDM frame, turn on the two top breakers at the top of theSDM frame.

2 Wait a few moments until the green lights on each card aresteady.

3 At the VT100 terminal, log on as root and type

# sdmmtc

4 Verify that all hardware is in service.

5 Verify that rootvg and datavg logical volumes are mirrored at thestorage level.

ATTENTIONThere will likely be alarms at the connection and application levels.The general status of the SDM will be in-service trouble (IsTb).

--End--


NN10450-900 06.023 October 2008


.


Powering up a Netra 240 server

Use this procedure to power up a Netra 240 server. Powering up the N240server supplies power for the following applications:

• IEMS

• Core and Billing Manager

• Communication Server 2000 Management Tools applications

• MG 9000 Manager

Procedure steps

Step Action

1 At the SDM frame, turn on the circuit breakers to bring theduplex N240 servers into service.

2 To help with recovery, turn the power on to what was the activeserver first. If there is no record of this, turn on the Unit 0 serverbefore the Unit 1 server.

After power is restored, the servers recover on their own.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 407

Powering up the Border Control Point Manager

Use this procedure to power up the Border Control Point Manager. TheBorder Control Point Manager is installed on a Sun Netra™ 240 (N240).

Procedure steps

Step Action

1 At the frame housing the Border Control Point Manager, for DCpowered shelves, switch the circuit breakers at the EBIP thatprovide power to the servers being powered to the ON position.The breaker will have the ’|’ side (top) of the breaker depressed.

ATTENTIONThe DC powered N240 does not have a Power ON/OFF switch andcan only be powered ON/OFF from the breaker at the EBIP.

2 For AC powered shelves, push the rocker located on the topof the AC outlet to apply power to the servers. It should beswitched to the "|" position.

3 After the breakers are switched ON at the power source, powerup the servers by switching the breakers on the back of thechassis to the ON position.

4 Verify the system is powered up correctly by observing the LEDson the front of the N240.

--End--


NN10450-900 06.023 October 2008


.


Powering up the SAMF frame

Use this procedure to power up the SAMF frame. Powering up the SAMFframe allows the SAM21 hardware cards, the Policy Controller unit, andthe Session Server unit to return to service.

Procedure steps

Step Action

1 At the SAMF frame, power up the SAMF BIP breakers. At thetop of the cabinet, turn on the breakers that supply power to thetwo SAM21 shelves and the Session Server (if equipped).

2 At the Communication Server 2000 SAM21 Manager, ifnecessary, unlock the previously active Shelf Controller (SC).

See “Unlocking a SAM21 Shelf Controller” (page 353).

3 If necessary, unlock the previously inactive SC.


4 If necessary, unlock any remaining locked cards on the SAM21other than the GWC cards.

5 At the Communication Server 2000 GWC Manager, if necessary,unlock all previously active GWC cards.

See “Unlocking a GWC card” (page 457).

6 If necessary, unlock all previously inactive GWC cards.


7 At the Policy Controller unit, determine which physical or logicalunit you want to become active and power that unit up first byexecuting procedure Power-On and boot a Policy Controller unit..

8 After the active unit has begun call processing, power up themate unit by executing procedure Power-On and boot a PolicyController unit..

9 At the Session Server unit, determine which physical or logicalunit you want to become active and power that unit up first byexecuting procedure Power-On and boot a Session Server unit..

10 Log onto the active unit to monitor the status of the SIP Gatewayapplication using procedure View the operational status of theSIP Gateway application.. Verify that the Administrative stateof the SIP Gateway application becomes Unlocked and theOperational state becomes Enabled.

If the active unit comes up in any state other thanUnlocked:Enabled, see Nortel Session Server TrunksAdministration and Security ( (NN10346-611)) ,


NN10450-900 06.023 October 2008


.

Procedure steps 409

11 Complete one or both of the following procedures:Unsuspend theSIP gateway application

OR

Unlock the SIP gateway application

12 After the active unit has begun call processing, power up themate unit by executing procedure Power-On and boot a SessionServer unit..

13 From the active unit, verify that the SIP Gateway applicationdatabases on the both units have synchronized using procedureVerify synchronization status of Session Server units.

14 Monitor the system for an appropriate period according to yoursite guidelines.

If you experience problems with call processing, seeNortel Session Server Trunks Administration and Security ((NN10346-611)) ,

15 Perform the following procedures in order: Invoke a maintenanceSwAct of the Session Server platform

AND

Inhibit a system SwAct (Jam)

16 Contact your next level of support or Nortel GNPS for furtherassistance.

--End--


NN10450-900 06.023 October 2008


.


Powering up the Call Control Frame

Use this procedure to power up the Call Control Frame (CCF). Poweringup the CCF allows the SAM21 hardware cards and the STORM disk arrayto return to service.

Procedure steps

Step Action

1 At the CCF, determine the configuration of your CCF.

2 If the CCF configuration includes a STORM disk array and twoSTORM cards in the Call Agent shelf then go to step 4.

3 If the CCF configuration includes two STORM SAM-XTS unitsthen go to step 5.

4 Power up the CCF BIP breakers. At the top of the cabinet, turnon the breakers that supply power to the STORM disk array andthe two SAM21 shelves.

Go to step 8.

5 Power up the CCF BIP breakers. At the top of the cabinet, turnon the breakers that supply power to the two SAM21 shelvesand the STORM SAM-XTS units.

6 At the front panel of the STORM SAM-XTS units, if necessary,power on the STORM SAM-XTS units using the main powerswitch located on the front panel.

7 At the console, monitor the boot progress of the unit until bootingis complete.

8 At the Communication Server 2000 SAM21 Manager, ifnecessary, unlock the previously active Shelf Controller (SC).



NN10450-900 06.023 October 2008


.

Procedure steps 411

9 If necessary, unlock the previously inactive SC.


10 If necessary, unlock the previously active Compact Call Agent(CCA) card.

See “Unlocking the Call Agent” (page 456).

11 If necessary, unlock the previously inactive CCA card.

See “Unlocking the Call Agent” (page 456).

12 If necessary, unlock the previously active USP-lite card.

13 If necessary, unlock the previously inactive USP-lite card.

14 If necessary, unlock any remaining locked cards on the SAM21other than the GWC cards.

15 At the Communication Server 2000 GWC Manager, if necessary,unlock all previously active GWC cards.


16 If necessary, unlock all previously inactive GWC cards.


--End--


NN10450-900 06.023 October 2008


.


Powering up a USP

Use this procedure to power up a Universal Signaling Processor (USP).The shelf uses the USP RTC-12 to initially get back into service.

Prerequisites• The Communication Server 2000 Core and USP ABS server must be

in-service.

Procedure steps

Step Action

1 At the USP shelf, ensure all cards are seated in the USP shelfwith the exception of the RTC-15 (slot 15) front panel card onthe Control shelf.

2 Power up both A/B buttons on the control and extension shelves.

3 RTC-12 should SCSI boot and it should come into service within1-2 minutes of being powered up.

4 At the USP Manager, after RTC-12 is up, use the USP Managerto uninhibit and activate all links, where applicable. SeeConfiguring Links.

5 Verify logs and alarms to ensure no unexpected problems andperform test calls.

6 Verify that all cards on all shelves are up and running with theexception of RTC-15.

7 Ensure that the System Date/Time is set to the current localtime, if not using SNTP. See Administration: Date and Time.

8 At the USP frame, after all cards are up and properly running,reseat RTC-15. RTC-15 should SCSI boot and perform adatabase synchronization with RTC-12. RTC-15 should comeinto service in approximately 5-7 minutes.

9 At the USP Manager, verify that RTC-15 is in-service andinactive.

10 Verify logs and alarms again to ensure no unexpected orundesired events and perform test calls.

11 Verify that the USP can communicate with the ABS. From theUSP Manager main menu, click on the Administration button andselect ABS Settings.

12 Select the Test button to initiate a series of tests to ensure theUSP can properly communicate with the ABS.


NN10450-900 06.023 October 2008


.

Procedure steps 413

13 Check the USP logs for the test results. Troubleshoot ABSconnectivity in the event that the tests fail.

ATTENTIONTo assist with troubleshooting, the Logs message includes the natureof the test failure.

14 Take a snapshot of the USP, and copy the snapshot to the ABSusing the File Manager.

15 Using the ABS CM GUI, modify the site information to point tothe new snapshot.

--End--


NN10450-900 06.023 October 2008


.


Powering up a Media Gateway/Multiservice Switch15000

Use this procedure to power up a Media Gateway/Multiservice Switch15000 when it is necessary to power up a Media Gateway/MultiserviceSwitch 15000.

Procedure steps

Step Action

1 At the chassis, locate the breaker interface panels (BIP). All theBIPs are at the top of the chassis.

ATTENTIONIf the CP card or its disk becomes unserviceable, the backup-upprovisioning data and software are downloaded from the MDMbackup copy and SDS site, respectively.

2 Switch the breakers on all the BIPs to the ON position. Thesystem should come up on its own.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 415

Powering up a Media Gateway/Multiservice Switch7400

Use this procedure to power up a Media Gateway/Multiservice Switch7400.

Prerequisites• All power supply switches must be in the standby position.

Procedure steps

Step Action

1 At the chassis, disengage all processor cards from the backplaneof the shelf.

2 Engage the minimum number of processor cards required, basedon the number of power supplies in the shelf.

3 If you have one power supply, engage a CP in slot 0 and at leastone FP.

Do not engage more than seven FPs. Ensure that all otherprocessors are disengaged.

4 If you have two power supplies, engage at least one CP and twoFPs. Or, engage two CPs and at least one FP.

5 Turn on the circuit breakers for the outlets that supply power toyour switch.

6 Verify that the LEDs on all power supplies are red.

7 Apply power to one of the power supplies by setting its powerswitch to the on position. Verify that the power supply LED isgreen.

Normal operation is not guaranteed if there are no processorcards in the shelf. If you have not installed any processor cardsbefore you switch on a power supply, the system does notsupply power to the shelf and the power supply LED remainsred.

8 Verify that the cooling unit LED is green and is operational. Youshould be able to hear the fans start to rotate.

9 If necessary, apply power to a second and third power supplyby setting their power switches to the on position. Verify that theLED for each power supply is green.


NN10450-900 06.023 October 2008


.


If you install eight or more FPs, you must use a second powersupply. If your system contains fewer than eight FPs, the systemuses the second power supply for redundancy.

10 If necessary, engage the remaining processor cards.

11 Verify the LED color on each FP in appropriate.

12 Verify that the appropriate LEDs are illuminated on terminationpanels.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 417

Powering up the MDM workstation

Use this procedure to power up the MDM Sun FireTM V480 workstation.

ATTENTIONIf your MDM is an N240 server, see the procedure "Powering up a Netra 240server."

Prerequisites• An MDM user account is required.

Procedure steps

Step Action

1 At the workstation, switch the workstation on.

2 After the workstation has started, log on with an MDM useraccount and ensure that the MDM toolset is available.

--End--


NN10450-900 06.023 October 2008


.


Powering up an SPM device

Use this procedure to power up a Spectrum Peripheral Module (SPM),Media Gateway 4000 (MG 4000), Interworking Spectrum PeripheralModule (IW-SPM), or Dynamic Packet Trunking Spectrum PeripheralModule (DPT-SPM).

Procedure steps

Step Action

1 At the MAP terminal, restore power to the frame and re-insertthe fuses.

2 Reseat the SIM cards if they were unseated and turn them onone at a time using the switches on the front.

3 Reseat any unseated cards in the shelves.

4 Post the SPM/MG 4000/IW-SPM/DPT-SPM.

>MAPCI;MTC;PM;POST SPM <spm_no>

5 Select and RTS the CEMs.

>SELECT CEM ALL;BSY ALL; LOADMOD ALL;RTS ALL

6 Select and RTS the SRM, OC3 RMs, ATM RMs, and/or GEMRMs.

>QUIT;SELECT <rm_type> ALL;BSY ALL;LOADMOD ALL;RTS ALL

ATTENTIONTo RTS the ATM, use the BSY FORCE and RTS FORCE commands.

7 Bring the carriers into service.

>QUIT ALL;MAPCI;MTC;TRKS;CARRIER;POST SPM <spm_no>;BSYALL;RTS ALL

8 Post and recover the trunks on the SPM at the TTP level. (Pressthe Enter key after each of the following commands.)

>QUIT ALL;MAPCI;MTC;TRKS;TTP;PRADCH;POST AD SPM<spm_no>;BSY ALL;RTS ALL

>QUIT ALL;MAPCI;MTC;TRKS;TTP;POST D SPM <spm_no>;BSYALL;RTS ALL

9 Return to the PM level and post the SPM.

>QUIT ALL;MAPCI;MTC;PM;POST SPM <spm_no>

10 Select and RTS the remaining RMs.


NN10450-900 06.023 October 2008


.


>SELECT <rm_type> ALL;BSY ALL;LOADMOD ALL;RTS ALL

--End--


<spm_no> The number of the SPM/MG 4000/IW-SPM/DPT-SPM.

<rm_type> This is either SRM, OC3, ATM, or GEM.


NN10450-900 06.023 October 2008


.


Powering up the MCS servers

Use this procedure to power up the eight MCS servers. The databaseserver should be brought into service before any other servers. If otherservers come up first, restart the management server.

Procedure steps

Step Action

1

ATTENTIONThe following shows the preferred order, which is not the way thesystem comes up if all servers are powered on at the same time.

At the frame housing the MCS servers, power on the databaseserver by turning on the circuit breakers that provide power tothe servers. It takes from 5 to 8 minutes for the server to bootand load Oracle.

2 After the DBSvr powers on, telnet to the box and run a spotcheck to make sure it is ready.

3 Make sure Oracle is loaded. The best way is to telnet tothe database. Type: sqlplus and fill in the username andpassword (in other words, log on as user, not root). If Oracle isrunning, you should receive the SQL> command prompt. Typequit to exit from sqlplus.

4 Verify that the snmp service is running on the database box.Type: ps -ef | grep snmp. You should see three snmpprocesses:

/usr/local/sbin/snmpd -f udp:161/bin/sh/opt/app/oracle/product/9.2.0/bin/dbsnmpwd

/opt/app/oracle/product/9.2.0/bin/dbsnmp

The snmp processes are not critical to getting the system up.However, if any of the snmp processes are not running, you willnot be able to see accurate reporting of this box on the SystemManagement Console.

5 To stop or start oracle, telnet to the database as sysadmin andthen su to root. Go to the following directory: /etc/init.d.The stop command is ./dbora stop. The start command is./dbora start. These commands will severely affect service.

6 Verify that the SysMgr processes on the MgmtSvr/AcctMgr boxare running to control the MCS components from the System


NN10450-900 06.023 October 2008


.

Procedure steps 421

Management Console. Telnet to the MgmtSvr/AcctMgr box asnortel.

7 Make sure that the SysMgr processes are running bytypingmeinit -p. You should see three processes running. Ifany of these processes are not running, you will not be able tolaunch the System Management Console:

Rel2.0 NTme_pids mgmtsvr mgmtsvr.3Rel2.0 NTme_pids tsscma tsscma.5

Rel2.0 NTme_pids tssfpma tssfpma.6

8 To stop or start the SysMgr, go to the following directory: IMS/mgmtsvr/bin/mgmtsvr/ and type: ./MgmtSvrShutdown.pl.This will kill any (or all) of the SysMgr processes.

9 To start the SysMgr, stay in the same directory and type:MgmtSvrConfigSetup.pl. This will try to start all threeprocesses. You will see a messages on the telnet sessionthat say something like "starting tsscma waiting 30seconds." The tssfpma process will start next, followed by themgmtsvr processes.

10 If you want to watch the SysMgr startup logs, afterperforming step 3b above, go to the following directory:/var/Rel2.0/mgmtsvr. Then type: tail -fmgmtsvr.3.log.

11 Verify that the snmp process is running on the MgmtSvr/AcctMgrbox by typing ps -ef | grep snmp.

You should see one process running:/usr/local/sbin/snmpd -f udp:161. If this process isnot running or you get an alarm from the System ManagementConsole that there is a problem with the MgmtSvr/AcctMgr’ssnmp, then kill the process. The process will automaticallyrestart in about 30 seconds.

12 Restart the AcctMgr process. If any of the components sendan alarm in the System Management Console indicating thatthe component cannot communicate with the primary or backupCAM, then again restart the AcctMgr process. Right click on theAccounting component in the System Management Console andselect Restart. Confirm the request. A progress box will popup and then disappear when the restart has begun. While theAccounting module is rebooting, the other MCS component willthrow alarms to the System Management Console, but those willgo away when the Acct component is fully operational.

13 Now verify the state of the other machines and the MCScomponents on them. Launch the System Management Consoleas you normally would. Expand the navigation tree fully so thateach component is fully exposed.


NN10450-900 06.023 October 2008


.


14 Restart the AppSvr. If the clients are having troublecommunicating with the AppSvr, then restart the AppSvr. Rightclick on the AppSvr component in the System ManagementConsole and select Restart. Confirm the request. You shouldsee a progress window and it disappears after the restarthas begun. To view AppSvr startup logs, telnet to the AppSvrbox (we recommend that you telnet as nortel) and go to thefollowing directory: /var/Rel2.0/appsvr. Type: tail -fappsvr.0.log.

15 Verify that the AppSvr’s snmp process is running. This step isthe same as step 3e above.

16 Restart the IPCM. If the i2004 phones are not responding toclient registers, the hollow blinking icons in the i2004 display,then restart the IPCM component. Right click on the IPCMcomponent in the System Management Console and selectRestart. Confirm the request. You see a progress window thatwill disappear after the restart has begun. To view IPCM startuplogs, telnet to the IPCM box (recommend as nortel) and go tothe following directory: /var/Rel2.0/esm. Type: tail -fesm.1.log.

17 Verify that the IPCM’s snmp process is running. This step is thesame as step 3e above. Most likely, the Provisioning Moduleand the WebClient Module are deployed on the same box as theIPCM. Therefore, you only need to verify the snmp service onthe box once.

18 Restart the Provisioning component. The best way to see ifthe Provisioning Module is behaving properly is to log on tothe ProvClient. Launch a web browser to the IP address ofthe box where the Provisioning Module is deployed, such ashttp:192.168.0.10/prov. Log on as admin/admin and attemptany of the List options in the navigation tree, for example, ListDevices or List Users. If the browser doesn’t respond properly,then restart the Provisioning Module by right clicking on theProvisioning component in the System Management Consoleand select Restart. Confirm the request.

19 Restart the WebClientMgr component. Log on to the PersonalAgent through your browser, such as http://192.168.0.10/pa.Log on as a subscriber, such as [email protected],and enter the subscriber’s password. The Personal Agentshould appear for that subscriber. If it does not, or the interfacedoes not seem to respond correctly, restart the ProvisioningModule described in step 4e above. (If you’ve already restartedit once and the ProvClient interface seems ok, but the PersonalAgent interface is still not working correctly, it is probably aconfiguration issue.


NN10450-900 06.023 October 2008


.

Procedure steps 423

20 Launch the WebClient GUI from inside a subscriber’s PersonalAgent page. Attempt to log on to the WebClient when theSystem Management Console completes loading.

--End--


NN10450-900 06.023 October 2008


.


Powering up a Border Control Point

Use this procedure to power up the Border Control Point. The BorderControl Point shelves are powered from either a PDU or EBIP located atthe top of the frame depending on if the frame is AC or DC powered.

Procedure stepsAt the Ethernet Routing Switch 8600 Workstation

Step Action

1 At the frame housing the Border Control Point, for DC poweredshelves, switch the circuit breakers at the EBIP that providepower to the shelf being powered to the ON position. Thebreaker will have the ’1’ side (top) of the breaker depressed.

2 For AC powered shelves, push the rocker located on the topof the AC outlet to apply power to the chassis. It should beswitched to the "|" position.

3 After the breaker is switched ON at the power source, power upthe shelf by switching the breaker on the back of the chassis tothe ON position.

4 Observe the System, Power/Fan, Slot (filled) and Host CardLEDs as the unit is being powered. After power on is complete,they should all have a steady green color.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 425

Powering up the IPmedia 2000 shelves

Use this procedure to power up the IPmedia 2000 shelves that house theMS 2000 series devices and the Packet Media Anchor. The IPmedia 2000shelves reside in either a SAMF frame or CCF, depending on whether ornot your solution uses the Communication Server 2000 or CommunicationServer 2000-Compact.

Procedure steps

Step Action


2 At the EBIP at the top of the frame, turn the breaker associatedthe Media Server to the ON position.

3 Ensure that the Green Power LED on the front of the NortelMedia Server 2000 is on (right hand side of the card).

After 1 to 2 minutes, the Green LED on the left hand side of thecard lights.

4 Verify the status of the LEDs on the front of the Nortel MediaServer 2000

.

5 Red Fail LED is off (left hand side of the board).

6 ACT LED is on (left hand side of the board).

ATTENTIONIt may take up to 60 seconds for the ACT LED to light up.

7 Blue LED does not remain on (right hand side of the board).

8 PWR LED is on (right hand side of the board).

9 Both Ethernet Link LEDs are on (middle of the board).

ATTENTIONThe Ethernet LEDs are Green when indicating a connection, andOrange when indicating activity.

ATTENTIONCheck the Media Server 2000 to make sure it is set to an unlockedstate.

--End--


NN10450-900 06.023 October 2008


.


Powering up the SAM16 shelves

Use this procedure to power up the SAM16 shelves that house the UASdevices. The SAM16 shelves reside in either a SAMF frame or CCF,depending on whether or not your solution uses the Communication Server2000 or Communication Server 2000-Compact.

Procedure steps

Step Action


2 At the EBIP at the top of the frame, turn the breakers associatedthe SAM16 to the ON position.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 427

Powering up an MG 9000 device

Use this procedure to power up the MG 9000 device.

Procedure steps

Step Action

1 At the Subnet View of the MG 9000 Manager, select the MG9000 to be re-commissioned. A warning window indicating thatyour connection to the gateway is down may appear. This willnot block the saving of services information.

2 Save a copy of the MG 9000 Manager SLoA provisioning data asfollows (you’ll be re-entering this data later):

3 To Save the SLoA services provisioning data, at the Frame(Element) view, select the "Save SLOA services" option from theActions menu.

An acknowledgment window appears in response to this request.The acknowledgment window contains the name of the two files(with .html and .text suffixes) where your data had been storedon the MG 9000 Manager.

4 Record the file name provided in the Save acknowledgementwindow for later use.

5 Save a copy of the MG 9000 Manager PLoA provisioning data asfollows (you’ll be re-entering this data later):


NN10450-900 06.023 October 2008


.


6 To save the PLoA services provisioning data, at the Frame(Element) view, select the "Save PLOA services" option from theActions menu.

An acknowledgment window appears in response to this request.The acknowledgment window contains the name of the fileswhere your data had been stored on the MG 9000 Manager.

7 Record the file name provided in the Save acknowledgementwindow for later use.

8 Obtain the IP address of the MG 9000 Manager server(not the mid-tier or client). At the Subnet View, selectConfiguration->View/Modify NE Properties from the menu bar.

9 Record the IP address in the MG 9000 Manager IP Addressfield.


NN10450-900 06.023 October 2008


.

Procedure steps 429

10 FTP to the address recorded in step 5 and copy the files in the/tmp directory to a secure location, such as your desktop orpermanent server before proceeding.


NN10450-900 06.023 October 2008


.


11 At the MG 9000 frame, power up the shelves in the frame byreinstalling the fuse modules on the IBIP. Restore all fuses left toright in the frame.

12 Connect a laptop PC to the active DCC card and launch the localcraft interface (LCI).

13 Wait for the restart to complete and for all cards initialize,typically takes 5 minutes. The Administrative State of allcommon cards will be Locked.

14 From the LCI, Unlock the active DCC OC-3/DS1 IMA card byselecting the Admin. State Unlock radio button. Wait for thestatus at the LCI to change to Enabled, Online, and Unlocked.

15 From the LCI continue to unlock the common cards in thefollowing order until all are unlocked and online:

• active ITX

• active ITP

• OC-3 carriers on the active OC-3 DCC card

• inactive DCC

• inactive ITX

• inactive ITP

• OC-3 carriers on the inactive OC-3 DCC card


NN10450-900 06.023 October 2008


.

Procedure steps 431

• DS1 cards (if provisioned)

• ABI cards (if provisioned)

16 Initiate rediscovery by sending a cold start trap from the LCI.

17 At the MG 9000 Manager, monitor the MG 9000 network elementand wait until the discovery process is complete.

18 Wait for the network element to show it is operational, thencheck for dial tone.

--End--


NN10450-900 06.023 October 2008


.


Restoring certificates and Pre-shared Keys forIPSec

Use this procedure to ensure that the current version of the certificatesand/or Pre-shared Keys is restored using the backup images of the CVoIPdevices. Apache/Tomcat web services and IPSec use these certificates tosecure and authenticate call processing traffic. Pre-shared Keys are usedto secure and authenticate call processing traffic.

Prerequisites• Perform regular full system backups and critical data backups

according to corporate policy. This measure ensures that the currentbackup version is restored, and that a disaster recovery process isexecuted quickly without additional outages.

• Ensure that the next level of support is available for assistance duringthe recovery process.

• Have immediate access to the Certificate Manager.

• Restore the Oracle data on the Communication Server 2000Management Tools. Also perform this restore procedure for all otherSPFS-based servers, including the MDM and MG 9000 Manager. Formore information, see Nortel Carrier Voice over IP Disaster RecoveryProcedures ((NN10450-900)) .

Procedure steps

Step Action

1 Reinstall the WEBPKPROXY certificate for the CertificateManager.

2 Launch the Certificate Manager GUI.

3 Unmanage and delete all WEBPKPROXY certificates.

4 Clean up directory /data/NTPkmgr/cert/export on the device onwhich the Certificate Manager resides by deleting all files in thisdirectory.

>rm -f /data/NTPkmgr/cert/export/*

Do not delete the directory. Delete only the files within it.

5 Recreate and re-install all WEBPKPROXY certificates. This stepensures that directory /data/pkclient/certificates is cleaned upon each management system. In addition, this step re-enables


NN10450-900 06.023 October 2008


.

Procedure steps 433

communication between the Certificate Manager and followingcomponents:

• the Communication Server 2000 Management Tools server

• the MG 9000 Manager system

• the MDM

6 Check that call processing traffic between each GatewayController (GWC) and the MG 9000 is not affected. Ensure thatthe connection between the GWC and the media gateways isstill enabled.

7

CAUTIONCheck the list of all certificates in the CertificateManager. Ensure that each MG 9000 displays thesame certificate serial number as the ones listed inthe Certificate Manager.

Do not rely on the displayed information in the VMG,as communication between the manager and themedia gateways can be compromised.

An outage can occur if the Certificate Authority serialnumbers between the GWC and the media gatewaysdo not match. Contact your next level of support toresolve this conflict.

See procedure “Viewing certificate using Certificate Manager”in NTP NN10453-100, “Nortel Carrier VoIP Security ServiceImplementation Guide,” for details.

8 Contact your next level of support within the next off-peakmaintenance window to assist you with performing the followingtasks:

• to download the certificates to the network element

• to busy and return to service the inactive GWC node

• to perform a warm SWACT

• to revoke the certificate for the MG 9000 VMG or the MG15000 that this GWC control(s)

• to busy and return to service the newly active side to clearany GWC307 alarms

• manually download all certificates on the MG 9000 VMG

9 During the next available maintenance window, ensure that allGateway Controller alarms and all network gateway alarms arecleared.

10 Launch the MG 9000 Manager web-based GUI.


NN10450-900 06.023 October 2008


.


11 From the Subnet View, select Configuration > View/Modify NEProperties

The NE Properties View displays.

12 Display the Properties menu of each MG 9000 node to verify thatthe Push and Pull Certificates match.

13 Click on the NE Security tab.

The NE Security View displays.

14 Compare the serial numbers in fields Last Pulled Certificateand Last Pushed Certificates against their Certificate Managercounterparts.

If the serial numbers differ, click the Download Certificates buttonto match the pushed and pulled certificates. Then click theRefresh button.

15 From the menu bar, select Services > Switched Lines ServicesManager.

The Switched Lines Services Manager displays.

16 Select the VMG for which security is to be provisioned.

17 Click the GW Security Config tab for each GWC card with acertificate.

The GW Security Config screen displays.

18 Compare the serial numbers in fields Last Pulled Certificateand Last Pushed Certificates against their Certificate Managercounterparts.

If the serial numbers differ, click the Download Certificates buttonto match the pushed and pulled certificates. Then click theRefresh button.

19 Verify that the call processing traffic between each GWC andmedia gateway has not been affected.

20 Perform a full system backup on all management systems andnetwork gateways.

--End--


NN10450-900 06.023 October 2008


.

Job aid 435

Job aidThis procedure applies to IEMS, Gateway Controller (GWC),Communication Server 2000 Management Tools, GWC Manager, MDM,MG 15000 and MG 9000 Manager in CVoIP IP Disaster Recovery and IPSecurity applications. Therefore, see the appropriate NTPs when directedas follows:

• Nortel CVoIP IPSec Service Configuration ( (NN10453-100)) for usewith WEBPKPROXY certificates for the Certificate Manager

• Nortel Carrier VoIP Disaster Recovery Procedures ((NN10450-900))for details and procedures for scheduled system backups. (SeePrerequistes.)

If Pre-shared Keys are used for authenticating call processing trafficusing IPSec, verify that the following conditions exists after a systemrecovery:

— All Gateway Controller alarms and network gateway alarms arecleared. Connectivity exists between all Gateway Controllers andnetwork gateways.

— All pre-shared key data is correct according to current provisioning.

• Nortel Carrier Voice over IP Fault Management Logs ReferenceVolume 2 ( (NN10275-909v2)) for details on alarm CMT301

• Nortel Gateway Controller Fault Management ( (NN10202-911)) fordetails on alarm GWC307

When backing up devices that use certificates provided by theIEMS/Certificate Manager and/or Pre-shared Keys for IPSec, always notethe versions of the data in the back-up image of the device.

Due to the timing sensitivity of the certificates, a potential conflict canoccur during restore between the version of the certificate in the back-upimage versus the version of the certificate provided by the CertificateManager.

If the restored data has expired or is not current, call processing trafficthat is secured and/or authenticated using IPSec can be affected. Thiscondition can result in additional outages.


NN10450-900 06.023 October 2008


.


Restoring the MG 9000 manager system

Use this procedure to restore the MG 9000 manager system whencertificates provided by the Certificate Manager are used in an office.

Procedure steps

Step Action

1 Unmanage and delete the WEBPKPROXY certificates for theMG 9000 manager system. Performing this step disables allcommunication between the Certificate Manager and the MG9000 manager system.

See Nortel CVoIP IPSec Service Configuration ( (NN10453-100))for details.

2 Recreate and re-install the WEBPKPROXY certificates for theMG 9000 manager system only, generate the WEBPKPROXYcertificate using the IP address and FQDN of the MG 9000manager system. This step is required for cleaning up the/data/pkclient/certificates directory on each management system.


3 Install the WEBPKPROXY certificate for the MG 9000 managersystem only.


4 Register the WEBPKPROXY certificate for the MG 9000manager system only. This step is required to re-enablecommunication between the Certificate Manager and the MG9000 Manager System.


5 Revoke all MG 9000 NE certificates and verify delivery of all MG9000 certificates.


6 Perform a full system backup on all management systems andnetwork gateways

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 437

Restoring files from a DVD-RW

Use this procedure to restore files from a DVD-RW to restore office imagesfrom a digital video disk read write optical disk (DVD-RW). Do not restorean image and overwrite one with the same name.

To restore a volume from DVD-RW, contact Nortel support personnel.Perform this procedure when required by your office.

Understanding of the IMPORT command in DISKUT, SCANF for listingvolumes, and the CBF, LBF, and SBF commands in ITOCCI is required.The IP addresses of the STORM units are needed. Use the mountcommand from a Call Agent card to determine the addresses.

Procedure steps

Step Action

1 At the Communication server Management Tools server insertthe DVD-RW into the DVD tray. If the Communication serverManagement Tools server is a pair of Sun Microsystems Netra™240s, put the DVD in the unit with the USER LED lit.Volume management software on the Communication serverManagement Tools server operating system mounts the DVD-RW.

2 List the contents:

$ ls -as /cdrom/cdrom0

The contents of the DVD are printed.

3 Change directory to the DVD-RW:

$ cd /cdrom/cdrom0

4 At the MAP enter the DISKADM level and busy the volumes tocopy:

> DISKADM <sd0x>; BSY <volname>

> QUIT

The BSY command fails if applications have open files on anyvolume for the device. A busied disk may affect data recordingor retrieval for applications. Consider to RTS the volume as soonas possible or convenient after copying the files.

If applications are active and writing to the volume, determine ifthe application can ROTATE the disk writing activity to a backupvolume. If unsure, contact your next level of support.

5 At a Communication server Management Tools server terminalsecure copy the files from the DVD-RW on the Communication


NN10450-900 06.023 October 2008


.


server Management Tools server to one STORage Management(STORM) unit:

$ scp <image_files>¡ root@<stormip>:</path_to_files>¡±

Example

Copy an office image named S040210135002_CM toSD00IMAGE1:

$ scp S040210135002_CM"root@<stormip>:/nfsserv/3pc/cs/sd00/image1"

ATTENTIONThe first time this command is issued, the secure copy programprovides a prompt to exchange keys. Confirm the exchange with a"y."

The secure copy program provides a progress indicator during thecopy. Wait for the copy to complete and the $ prompt to return.

6 At the MAP enter the DISKADM level and RTS the volume:

> DISKADM <sd0x>; RTS <volname>

> QUIT

7 Enter the DISKUT level and IMPORT the image files:

> DISKUT; IMPORT SD00IMAGE1

> QUIT

The status of the IMPORT command is printed.

8 List the contents of the volume so the file can be added to theImage Table of Contents (ITOC) in the next step:

> SCANF SD00IMAGE1

The contents of the volume are printed.

9 Enter ITOCCI and register the image in the ITOC:

> ITOCCI

> SBF CM S040210135002_CM <itoc_pos> <alr_flag>


NN10450-900 06.023 October 2008


.


ATTENTIONTo determine if a free position is available, use the LBF CM command.If all positions are used, clear the file in position 15. Determine whichvolume the position 15 is on, use SCANF to list that volume, and thenuse the CBF CM FILE <image_name> command.

10 At a Communication server Management Tools server terminalunmount the DVD-RW, eject it, and exit from root privilege:

$ eject cdrom

11 At the Communication server Management Tools server removethe DVD-RW from the tray and close the tray.

12 Store the DVD-RW according to office procedure.

--End--


<alr_flag> If this image should be booted for the nextrestart, specify ALR. Otherwise, leave the fieldblank.

<image_files> The file name for a single image file, or awildcard expression such as "*_CM"

<itoc_pos> An integer between 0 and 15, and is a freeposition in the ITOC.

</path_to_files> The absolute path to the files on theSTORM unit to place the files such as/nfsserv/3pc/cs/sd00/image1

<sd0x> SD00 or SD01

<stormip> The IP Address of the STORM unit such as172.18.96.6

<volname> The name of the volume such as TEMP


NN10450-900 06.023 October 2008


.


Reloading or restarting a SAM21 Shelf Controller

Use this procedure to reload or restart a SAM21 Shelf Controller (SC).

Procedure steps

Step Action

1 From the Shelf View, right-click on the card and select Lock.

2 Wait for the lock icon to appear on the selected card and theother SAM21 SC to indicate that it is in simplex (alarm 2C on theother SAM21 SC).

3 Right-click on the card again and select Unlock.

The card resets, downloads software, and reboots.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 441

Restarting or rebooting a GWC card

Restart a GWC card to stop all software processes on the GWC card,perform a hardware reset, and reload the GWC card software from theCore and Billing Manager (CBM). Reboot a GWC card and force a GWCto download and execute a software load from the Communication server2000 Core Manager or CBM.

Prerequisites• To reduce the risk of service interruption, first busy the GWC

applications on specific GWC nodes using the Communication server2000 GWC Manager.

For more information, see Nortel Gateway Controller Administrationand Security ( (NN10213-611)) .

Procedure steps

Step Action

1 At the Communication server 2000 SAM21 Manager client fromthe Shelf View, right-click the GWC card you want to reboot andselect Card View.


NN10450-900 06.023 October 2008


.


2 At the Card View, select the States tab.

3 Click the Lock button to lock the card.

4 Wait until the Card Status is Locked and the History windowindicates that: Application locked successfully.

5 Click the Unlock button.

6 Monitor the reboot process. Wait until the Card Status changesto Unlocked and the History window indicates Bootloadedsuccessfully.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 443

Performing a partial power up of the Netra 240server

Use this procedure to perform a partial power down recovery of the N240servers. The N240 servers are commissioned with one active and oneinactive unit. In a partial power down, the inactive unit is powered down,while the active unit remains powered up. This procedure powers up theinactive unit.

Prerequisites• You must have the root user password for the N240.

• You need to IP address for the inactive unit.

Procedure steps

Step Action

1 At the N240 server, the N240 server is inactive.

2 Turn on the circuit breakers. The server should recover on itsown and start syncing with the active server.

--End--


NN10450-900 06.023 October 2008


.



NN10450-900 06.023 October 2008


.

445.

Disaster recovery maintenanceThis chapter describes how to maintain the Disaster recovery proceduresfor the Nortel Carrier VoIP solutions.

The following network elements are covered by this section:

• XA-Core

• 3rd Party Core

• Message Switch

• ENET

• Ethernet Routing Switch 8600

• LPP

• SDM, Communication server 2000 Core Manager, or Core and BillingManager

• IEMS

• Communication server 2000 Management Tools

• MG 9000 Manager

• Border Control Point Manager

• SAM21 shelf and cards

• CICM

• USP

• Media Gateway 15000/7400 or Multiservice Switch 15000/7400

• MDM workstation

• SPM, MG 4000, IW-SPM, DPT-SPM

• MCS servers

• Border Control Point

• MS 2000 Series or UAS


NN10450-900 06.023 October 2008


.

446 Disaster recovery maintenance

• Packet Media Anchor

• MG 9000

Navigation

• “Performing a partial power down recovery of the USP” (page 447)

• “Performing a partial power down recovery of the XA-Core” (page 448)

• “Performing a partial power down recovery of the Ethernet RoutingSwitch 8600” (page 451)

• “Performing a partial power down recovery of the MediaGateway/Multiservice Switch 15000” (page 452)

• “Performing a partial power down recovery of the SPM” (page 453)


NN10450-900 06.023 October 2008


.

Procedure steps 447

Performing a partial power down recovery of theUSP

This procedure is used to perform a partial power down recovery of a USP.

Procedure steps

Step Action

1 At the USP frame reseat the front panel and back panel CC cardin Slot 18 on the Control shelf.

2 Reseat the front panel and back panel CC cards in Slot 18,beginning with the CC Slot 18 card on each of the extensionshelves.

3 Reseat the inactive RTC.

The inactive RTC should SCSI boot and perform a databasesynchronization with the active RTC. It should come into servicein approximately 5-7 minutes.

4 At the USP Manager verify the reseated RTC is in-service andinactive.

5 Verify logs and alarms to ensure there were no unexpected orundesired events.

6 Perform test calls.

--End--


NN10450-900 06.023 October 2008


.


Performing a partial power down recovery of theXA-Core

Use this procedure to return to normal operation an extended ArchitectureCore (XA-Core) configuration of a switch. The switch is a DMS SuperNodeor a DMS SuperNode SE switch. Use this procedure after havingperformed all parts of the procedure "Emergency power conservationshutdown" to maintain emergency backup power. The procedure"Emergency power conservation shutdown" follows an extendedcommercial power outage.

This procedure describes equipment recovery in decreasing order basedon its effect on system reliability. The equipment restoration begins withmore required equipment and ends with less required equipment suchas maintenance trunk modules. The configuration of your office andthe requirements of your operating company, can change the order ofequipment restoration. The return of elements of the switch to service canbe in an different order.

Procedure stepsWARNINGPotential extended equipment outageNortel recommends that you perform this procedure underthe supervision of Emergency Technical Assistance Services(ETAS) of Nortel. Also call your next level of support before youperform this procedure.

CAUTIONPotential loss of service or extended outageThis procedure is only to restore normal operation after theperformance of measures for emergency power conservation.Do not use this procedure or parts of this procedure forequipment maintenance purposes.

Step Action

1 At your current location use office records to identify and recordthe power converters which supply the MAPs and printers of theswitch.

2 Restore power to all the power converters identified in step 1thatsupply power to the MAPs and printers of the switch.

3 At the MAP restore power to one side of the remote oscillatorshelf (NT3X9507), If you turned off power to save emergencybackup power. To restore power, perform the procedure


NN10450-900 06.023 October 2008


.

Procedure steps 449

"Restoring the remote oscillator shelf to duplex operation" inRecovery Procedures () , 297-8021-545.

4 Restore power to one message switch (MS) shelf if you turnedoff power to save emergency backup power. To restore power,perform the procedure "Restoring the MS duplex operation" inRecovery Procedures () , 297-8021-545.

5 Restore power to one unit of the CCS7 message switch andbuffer (MSB7) if you turned off power to save emergency backuppower. To restore power, perform the procedure "Restoringthe MSB7 to duplex operation" in Recovery Procedures () ,297-8021-545.

6 Restore power to one link interface module (LIM) unit on one ormore link peripheral processors (LPP) if you turned off power tosave emergency backup power. To restore power, perform theprocedure "Restoring LPP LIMs to duplex operation" in RecoveryProcedures () , 297-8021-545.

7 If you removed power from one or more network frames, restorepower to the changed frames at the power distribution center(PDC).

8 Restore power to one or more junctored network (JNET)shelves if you turned off power to save emergency backuppower. To restore power, perform the procedure "Restoring thejunctored network to duplex operation" in Recovery Procedures,297-8021-545.

9 Restore power to one or more enhanced network (ENET)shelves if you turned off power to save emergency backuppower. To restore power, perform the procedure "Restoring theenhanced network to duplex operation" in Recovery Procedures() , 297-8021-545.

10 Restore power to one or more units of a line group controller(LGC), line trunk controller (LTC), or digital trunk controller(DTC). Restore power if you turned off power to save emergencybackup power. To restore power, perform the procedure"Restoring LGCs, LTCs, and DTCs to duplex operation" inRecovery Procedures () , 297-8021-545.

11 Restore power to one or more units of a line concentratingmodule (LCM) if you turned off power to save emergencybackup power. To restore power, perform the procedure"Restoring LCMs to duplex operation" in Recovery Procedures() , 297-8021-545.

12 Restore power to one or more line modules (LM) if you turnedoff power to save emergency backup power. To restore power,perform the procedure "Restoring line modules to duplexoperation" in Recovery Procedures () , 297-8021-545.


NN10450-900 06.023 October 2008


.


13 Restore power to one or more maintenance trunk modules(MTM) if you turned off power to save emergency backuppower. To restore power, perform the procedure "Returningmaintenance trunk modules to service" in Recovery Procedures() , 297-8021-545.

14 To clear any alarms on the MAP display, perform the correctalarm clearing procedure. The correct alarm clearing procedureis in this document or in the Alarm and Performance MonitoringProcedures () , 297-8021-543.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 451

Performing a partial power down recovery of theEthernet Routing Switch 8600

This procedure is used to perform a partial power down recovery of anEthernet Routing Switch 8600.

Procedure steps

Step Action

1 At the chassis turn the DC input power source on, or reset thepower source circuit breaker to provide power to the powersupply.

2 Turn the power supply switch to the on position.

--End--


NN10450-900 06.023 October 2008


.


Performing a partial power down recovery of theMedia Gateway/Multiservice Switch 15000

This procedure is used to perform a partial power down recovery of aMedia Gateway/Multiservice Switch 15000.

Procedure steps

Step Action

1 At the frame manually switch on the following breakers on thelower shelf:

• A1.5

• A1.2

• B1.5

• B1.2

2 Manually switch on the following breakers on the upper shelf:

• A2.5

• A2.2

• B2.5

• B2.2

3 The system should recover and come up on its own.

--End--


NN10450-900 06.023 October 2008


.


Performing a partial power down recovery of theSPM

This procedure is used to perform a recovery of a partial power down ofa DMS-SPM, MG 4000, IW-SPM, or DPT-SPM. In this procedure, SPMrefers to the completed family of SPM devices unless otherwise noted.

Procedure steps

Step Action

1 At the MAP post the SPM to recover by typing:

>POST SPM <spm_no>


2 Manually reseat the inactive CEM.

3 Post, busy, and return the inactive CEM to service by typing:

>POST CEM <inactive_cem>; BSY; RTS


4 Manually reseat each RM.

5 Select, busy, and return each inactive resource module toservice by typing:

>POST <rm_type> ALL; BSY ALL; RTS ALL


6 Perform step 5 for each RM type.

--End--


rm_type is SRM, OC3, ATM, GEM, DSP, VSP, ALM, orDLC

spm_no is the number of the SPM to be powered down


NN10450-900 06.023 October 2008


.



NN10450-900 06.023 October 2008


.

455.

Disaster recovery power upThis chapter describes how to power up the disaster recovery proceduresfor the Nortel Carrier VoIP solutions.

Navigation

• “Unlocking the Call Agent” (page 456)

• “Unlocking a GWC card” (page 457)


NN10450-900 06.023 October 2008


.

456 Disaster recovery power up

Unlocking the Call Agent

Use this procedure to unlock the call agent.

Procedure steps

Step Action

1 At the Communication server 2000 SAM21 Manager client fromthe Shelf View, right click on the card and select Unlock from thecontext menu.

Unlock is also available from the States tab of the Card Viewwindow.

The card resets, downloads software, and reboots.

2 Wait for the lock icon to disappear.

Do not perform any patching activities on the Call Agent until tenminutes have passed.

--End--


NN10450-900 06.023 October 2008


.

Procedure steps 457

Unlocking a GWC card

Use this procedure to initiate a reboot of the GWC card causing the card todownload its software from the Communication server 2000 Core Managerand to restart its call processing services and applications software.

Use this procedure:

• after replacing a GWC card

• as part of a fault clearing activity

• when a new software load is available

• when you complete reprovisioning a GWC card or GWC node (a nodeis made up of unit 0 and unit 1 GWC cards) and you want the card ornode to use the new provisioning values

• when you applied or removed a patch to the GWC software using theNetwork Patch Manager (NPM) and saved a new GWC software imageto the Communication server 2000 Core Manager

Prerequisites• The card must be locked.

• If IP addresses for the card that you want to unlock and its mate arenot contiguous, you cannot unlock the card. You must correct theseaddresses using procedure "Manually re-provisioning GWC cards"in Nortel Gateway Controller Configuration ( (NN10205-511)) beforeattempting to unlock the card.

• If the GWC hardware does not support the service profile assigned tothe GWC node, the unlock process fails and the system generatesthe CMT305 critical alarm. For the description of each profile and itshardware requirement, see Nortel Gateway Controller Configuration( (NN10205-511)) .

Procedure steps

Step Action

1 At the Communication server 2000 GWC Manager client at theCommunication server 2000 Management Tools window, clickthe Gateway Controller folder from the Device Types directorytree in the far left frame.

2 From the Contents of: GatewayController frame, select the GWCnode that contains the card you want to unlock.


NN10450-900 06.023 October 2008


.


3 Select the Maintenance tab to display maintenance informationabout the node.

4 Click the Card View button for the card you want to unlock. TheCommunication server 2000 SAM21 Manager opens.

If a card is locked, all fields display the value <unknown>.

5 At the Communication server 2000 SAM21 Manager in the cardview, select the States tab, then click the Unlock button tounlock the card.

If you want to display the status of all cards in the shelf, selectShelf View from the View menu.

If the IP addresses for the selected card and its mate are notcontiguous, the system displays the following error message:


NN10450-900 06.023 October 2008


.

Procedure steps 459

Follow procedure "Manually re-provisioning GWC cards" inNortel Gateway Controller Configuration ( (NN10205-511)) tocorrect these addresses, then repeat this procedure.

If the GWC service profile and the GWC hardware are notcompatible, the unlock operation fails and the system generatesthe CMT305 critical alarm. For the description of the alarmand the required action, see Nortel Carrier Voice over IP FaultManagement Logs Reference Volume 2 ( (NN10275-909v2)) .

6 Observe the system response in the History window.

The card is unlocked when you see the text Application unlockedsuccessfully .

7 If required, repeat this procedure for the next GWC card until allthe GWC cards have been unlocked and brought into service.Each GWC node has two cards.

--End--


NN10450-900 06.023 October 2008


.



NN10450-900 06.023 October 2008


.

461.

ReferenceThe reference chapter describes information about the disaster recoverysolutions.

Disaster recovery preparationThe section gives you referential information on how and when to havethe data backup of the components.

Backup operationsThere are two types of backup operations for components of CVoIPsolutions: service data backup and fileset level backup.

Perform service data backups once on each day during a period of lowactivity. Table 27 "Service data backup components" (page 461) listscomponents that are typically backed up using a service data backup.

ATTENTION• Point 1—Service data from the SAM21, GWC, and MG 9000 is not backed

up locally. This data is backed up at the manager. The manager is backedup to DVD using CS 2000 Core Manager or Core and Billing Manager (CBM)or CS 2000 Management Tools procedures.

• Point 2—Service data from the IW SPM and MG 4000 is automaticallybacked up when the CS 2000 is backed up.

• Point 3—Perform MDM backups by copying the files to tape or an off-productstorage system through UNIX commands or CRON jobs.

• The script purgeTempData.sh in the /opt/nortel/iems/current/bin directorypurges all event, alarm, and performance data from the IEMS database.After you purge the data you cannot retrieve it. The purge deletes all events,alarms, and performance data. To reduce the time taken to backup orrestore, you must stop the IEMS server and execute the purgeTempData.shscript to purge the events, alarms, and performance data from the database.

Table 27Service data backup components

Component Procedure (s)

NETWORK INTELLIGENCE


NN10450-900 06.023 October 2008


.

462 Reference

Table 27Service data backup components (cont’d.)


CS 2000 “Backing up an XA-Core office image from disk to tape” (page 119)

Call Agent “Backing up Call Agent” (page 126)

SAM21 none (See "Point 1" (page 461) )

GWC none (See "Point 1" (page 461) )

Session Server “Backing up the SST” (page 129)

Policy Controller “Performing a manual backup of the Policy Controller database” (page 162)

Ethernet RoutingSwitch 8600

“Saving the Ethernet Routing Switch 8600 boot configuration file” (page 136)

UAS “Backing up UAS configuration files” (page 160)

MS 2000 Series For the following MS 2000 Series procedures, see Nortel Media Server 2000Series Configuration ( (NN10340-511))Displaying the MS 2000 Series node configuration:[***Configuring Automated INI file backup on a Media Server 2000 node][***Changing the SNMP community string passwords][***Changing the SNMP community string password for a Media Server 2020node]Backing up all MS 2000 Series node INI files:[***Backing up INI files for all nodes]Configuring the MS 2000 Series CLUI tool:[***Displaying Media Server 2010 node current configuration][***Displaying Media Server 2020 node current configuration]

APS “Backing up the APS-specific Oracle database and application files” (page150)

USP

Real-timeTransportProtocol (RTP)Media Portal

RTP Media Portal Basics () (NN10367-111)

CICM CICM Security and Administration () (NN10252-611)

CORE NETWORK

MultiserviceSwitch or MediaGateway devices

“Restoring Multiservice Switch or Media Gateway service data” (page 23)

GATEWAYS

MG 15000

MG 9000 none (See "Point 1" (page 461) )

MG 4000 none (See "Point 2" (page 461) )

IW SPM none (See "Point 2" (page 461) )


NN10450-900 06.023 October 2008


.

Disaster recovery preparation 463

Table 27Service data backup components (cont’d.)


NETWORK MANAGEMENT

CS 2000 CoreManager

Starting or stopping the automated synchronous backup restore managerservice in Nortel ATM/IP Solution-level Administration and Security ((NN10402-600))

Core ElementManager

“Starting or stopping the automated synchronous backup restore managerservice” (page 107)“Performing a backup of Oracle/MySQL data on anSPFS-based server” (page 156)

CS 2000ManagementTools

“Performing a backup of Oracle/MySQL data on an SPFS-based server” (page156)“Performing a backup of file systems on an SPFS-based server” (page 164)Starting or stopping the automated synchronous backup restore managerservice in Nortel ATM/IP Solution-level Administration and Security ((NN10402-600))

Integrated Element ManagementSystem

“Starting or stopping the automated synchronous backup restore managerservice” (page 107)

“Performing a backup of Oracle/MySQL data on an SPFS-based server” (page156)

IEMS centralizedsecurity server

“Taking a full IEMS backup” (page 169)

MG 9000Manager

“Performing a backup of file systems on an SPFS-based server” (page 164)

“Starting or stopping the automated synchronous backup restore managerservice” (page 107)

MDM Backing up an SPFS-based security clientPerforming a backup of oracle data on an SPFS-based serverPerforming a backup of file systems on an SPFS-based serverStarting or stopping the automated synchronous backup restore managerservice

Fileset level backups back up the software and configuration data. Performthis type of backup after hardware changes, software updates or patches,or major configurations. You must perform a fileset backup before a majorupgrade. Table 28 "Fileset level backup components" (page 463) providesa list of components with fileset level backup procedures.

Table 28Fileset level backup components

Component Procedures

Network intelligence


NN10450-900 06.023 October 2008


.

464 Reference

Table 28Fileset level backup components (cont’d.)

Component Procedures

GWC Create a backup of the GWC load file in Nortel CarrierVoice over IP Upgrade and Patches ( (NN10440-450)) .

USP Administration: USP Manual Backup

Gateways

Multiservice Switch or MediaGateway devices

“Restoring Multiservice Switch or Media Gateway servicedata” (page 23)

Network management

CS 2000 Core Manager orCore andBilling Manager (CBM)

Creating system image backup tapes (S-tapes) manuallyConfiguring SBA backup volumes on the coreStarting or stopping the automated synchronous backuprestore manager service. Performing a backup of filesystems on an SPFS-based server. Configuring SBAbackup volumes on a billing stream.“Performing a backup of file systems on an SPFS-basedserver” (page 164)Configuring SBA backup volumes on the core

Frequency of backup operationsTable 29 "Component backup frequency" (page 464) lists each componentalong with how often Nortel recommends that you perform backupoperations.

ATTENTION• Point 1—Service data from the SAM21, GWC, and MG 9000 is not backed

up locally. The data is backed up at the manager. The manager is backed upto DVD using CS 2000 Core Manager or Core and Billing Manager (CBM) orCS 2000 Management Tools procedures.

• Point 2—Service data from the IW SPM and MG 4000 is automaticallybacked up when the CS 2000is backed up.

Table 29Component backup frequency

Component Backup Frequency

Network Intelligence

CS 2000MSCServer 1000XA-Core

Weekly

Call Agent Weekly


NN10450-900 06.023 October 2008


.

Disaster recovery preparation 465

Table 29Component backup frequency (cont’d.)

Component Backup Frequency

SAM21 See "Point 1" (page 464)

GWC See "Point 1" (page 464)

Session Server Weekly

CS 2000 CS LAN Full backup - monthly, and prior to all migrations and patch operations andconfiguration changes

UAS Daily

MS 2000 Series Daily

APS Daily

RTP Media Portal Daily

CICM Daily

USP Full system backup - once a week. Modified (differential) backup - once a day

Core network

Multiserviceswitches

Full backup - monthly, and prior to all migrations and patch operations

Gateways

MG 9000 See "Point 1" (page 464)

MG 4000 See "Point 2" (page 464)

IW SPM See "Point 2" (page 464)

Network management

CS 2000ManagementTools

Daily

MG 9000Manager

Daily

IEMS Daily

Nortel MDM Daily

Storage and maintenance of CDs and DVDsFollow these guidelines for the proper storage and maintenance of CDsand DVDs:

• Store CDs and DVDs at a temperature between 5 and 25 �C and ahumidity level between 10% and 80%.

• Do not touch the surface of a CD or DVD with your hands and do notmark the surface with a pencil, pen, or marker.

• Use a cotton cloth or disk cleaning kit to clean CDs and DVDs.


NN10450-900 06.023 October 2008


.

466 Reference

ATTENTIONIf checksum errors occur, perform a visible inspection of the disk to check forscratches or damage. If no scratches are visible, clean the disk using a cottoncloth or disk cleaning kit and retry.

Operational status of the NCGL platformTable 30 "System information page fields" (page 466) lists informationabout System information page fields.

Table 30System information page fields

Field Description

Unit Unit number in the node that you are logged on to.

Activity Activity of the unit (either active or standby).

Jam Indicates if the inactive unit is Jammed. The value isyes only if you are logged on to the inactive unit. Fromthe active unit, the status is no, but a JInact alarmindicates the inactive is Jammed.

State Indicates if the node is operating in duplex(fault-tolerant) mode or simplex mode (the standby unitis off-line).

Connectivity State of the network links on the node.

Host Name Name of the unit (not node).

Date System date as maintained by the network timeprotocol (NTP) server.

Time since last reboot Indicates the amount of time that elapsed since the unitwas last rebooted.

System Power-OnTime

Recorded system time that the unit has been poweredup.

System booted from Indicates whether the unit is currently booted from thehard drive or DVD-ROM drive.

Last restart cause Indicates any event that forced a platform reboot(manual or system generated).

Last power eventcause

Indicates any event that affected the power supplysubsystem of the unit chassis.

Current version Installed version of the NCGL platform software.

Platform IP Address Unit IP address.

Platform EM Client IPAddress

IP address of the client web browser. When aweb proxy is used, the IP address of the machineperforming the proxy is displayed.


NN10450-900 06.023 October 2008


.

Operational status of the NCGL platform 467

Table 30System information page fields (cont’d.)

Field Description

Server Location Physical location of the unit.

Host Name Name of the unit.

Table 31 "Node maintenance page fields" (page 467) lists informationabout Node maintenance page fields.

Table 31Node maintenance page fields

Field Description

Operation State Indicates the operational state of the NCGLsoftware.

Activity Indicates the activity state of the platformsoftware.

Jam State Indicates if the inactive unit is Jammed.

Maintenance Actions (activeunit only)

Maintenance page for performing SWACT andto Jam. See the maintenance and manual coldSWACT procedures in this document.

Table 32 "Chassis information page fields" (page 467) lists informationabout Chassis information page fields.

Table 32Chassis information page fields

Field Description

Chassis information: Self Test Status of the self test performed on theplatform at bootup.

Chassis information: ChassisSubsystems

Status of the platform hardware subsystemsincluding the memory, CPU, all drives, networkconnection, power supplies, cooling and otherI/O connections.

CPU Information: loadaverage

Indicates the 1, 5 and 15 minute load averagesfor the CPU utilization.

CPU Information: loadaverage threshold values

Indicates the 1 minute CPU load averageutilization threshold value. When the setthreshold value is exceeded, the appropriateminor, major or critical alarm is raised.

Chassis Utilization: Utilizationaverage

Indicates the 5, 20, and 30 minute CPUutilization average. When the threshold valueis exceeded, an alarm is raised.


NN10450-900 06.023 October 2008


.

468 Reference

Table 32Chassis information page fields (cont’d.)

Field Description

Chassis Utilization: alarmthreshold values

Indicates the 5, 20, and 30 minute CPUutilization average threshold value. When theset threshold value is exceeded, an alarm israised.

Process Information: Numberof Processes

Total number of processes (non-threaded) thatare running on the SST Platform.

Process Information: Numberof zombie processes

Number of defunct or terminated NCGLzombie processes.

A zombie process is a process that has terminated either because it has beenkilled by a signal or because it has called an exit() and whose parent processhas not yet received notification of its termination. A zombie process existssolely as a process table entry and consumes no other resources.

Process Information-zombie:minor alarm threshold value

Maximum number of zombie processesallowed to be run by the CPU before a minoralarm is raised indicating that the set thresholdhas been exceeded.

Process Information-zombie:major alarm threshold value

Maximum number of zombie processesallowed to be run by the CPU before a majoralarm is raised indicating that the set thresholdhas been exceeded.

Process Information-zombie:critical alarm threshold value

Maximum number of zombie processesallowed to be run by the CPU before a criticalalarm is raised indicating that the set thresholdhas been exceeded.

Memory Information: TotalMemory (MB)

Total amount of RAM installed on the motherboard of each SST unit. Both units must havethe same amount.

Memory Information: FreeMemory (MB)

Amount of memory available unallocated foruse.

Memory Information: Availablememory (MB)

Amount of memory available for programs.

Memory Information: minoralarm threshold value

Indicates the threshold amount of availablememory (in Mbytes) that the system must dropbelow before a minor alarm is raised.

Memory Information: majoralarm threshold value

Indicates the threshold amount of availablememory (in Mbytes) that the system must dropbelow before a major alarm is raised.

Memory Information: criticalalarm threshold value

Indicates the threshold amount of availablememory (in Mbytes) that the system must dropbelow before a critical alarm is raised.


NN10450-900 06.023 October 2008


.


Table 33 "Network connectivity page fields" (page 469) lists informationabout Network connectivity page fields.

Table 33Network connectivity page fields

Field Description

Unit 0,1 Links Indicates which Ethernet IP links are installed onthe units (each unit has two links).

Unit 0,1 Status Status of the Ethernet links.

Unit 0,1 Activity Activity status of the Ethernet links, either activeor inactive.

Unit 0,1 Maintenance Indicates the maintenance actions that can beperformed on the Ethernet links, either Lock,Unlock or Swlink.

Unit 0,1 PTP Links status Status of the PTP links between both units in thenode.

Unit IP Network IP address of the SST unit.

Active IP IP address of the local (active) SST unit.

Inactive IP IP address of the mate (inactive) SST unit.

Port 0 IP IP address of the active or inactive Ethernet port0.

Port 1 IP IP address of the active or inactive Ethernet port1.

PTP IP IP address of the active or inactive PTP link.

Table 34 "Disk Services page fields" (page 469) lists information aboutDisk Services page fields.

Table 34Disk Services page fields

Field Description

RAID Array Status: Name Indicates the name of each RAID-1 array in thesystem.

RAID Array Status: Size (GB) Indicates the size of the partition in Gigabytes.

RAID Array Status: State Indicates a high level state for the array:- ".": indicates the array is functioning normally.- Missing: a disk was removed from the array.- Failed: a disk in the array has failed andneeds to be replaced.- Rebuilding: the array is in the process ofrebuilding to a fault-tolerant mode.


NN10450-900 06.023 October 2008


.

470 Reference

Table 34Disk Services page fields (cont’d.)

Field Description

RAID Array Status: Disk 0 Service status of disk 0.

RAID Array Status: Disk 1 Service status of disk 1.

RAID Array Status: Status Indicates the status of the array. Values are:- The array is operating normally- Missing- Failed- Rebuild

Disk Maintenance: DiskNumber

Indicates the disk number in the array, 0, or 1.

Disk Maintenance: Disk Size(GB)

Total capacity of the disk drive in Gigabytes.

Disk Maintenance: Disk State Installation state of the disk.

Disk Maintenance: Disk Action Indicates whether a hard disk can be insertedinto the RAID array.

Filesystem Information:Monitor

Indicates the status of individual filesystems onthe disk array.

Filesystem Information:Filesystem Name

Indicates the name of the filesystem onthe disk array. Some filesystem names arereserved.

Filesystem Information: TestResults

Indicates the results of any tests run on thefilesystems. Tests are run approximatelyevery 10 minutes to verify that all of the basicfilesystem operations are working on each ofthe filesystems.

Filesystem Information: TotalSpace (MB)

Total amount of disk space (in MB) allocatedfor this filesystem.

Filesystem Information: TotalSpace Used (MB)

Total amount of disk space (in MB) in use onthis file system.

Filesystem Information: TotalSpace Used (%)

Total amount of disk space (in %) in use onthis file system.

Filesystem Information: TotalSpace Available (MB)

Percentage of total disk space (in MB) free foruse on this filesystem.

Filesystem Information: TotalSpace Available (%)

Amount of disk space (in %) available for useby platform processes and applications.

Filesystem Information: MinorAlarm Threshold (%)

maximum amount of disk space (in %) thatcan be used before a minor alarm is raisedindicating that the set threshold has beenexceeded.


NN10450-900 06.023 October 2008


.


Table 34Disk Services page fields (cont’d.)

Field Description

Filesystem Information: MajorAlarm Threshold (%)

Maximum amount of disk space (in %) thatcan be used before a major alarm is raisedindicating that the set threshold has beenexceeded.

Filesystem Information:Critical Alarm Threshold (%)

Maximum amount of disk space (in %) thatcan be used before a critical alarm is raisedindicating that the set threshold has beenexceeded.

Volume Group Information:Volume Group Name

Name of the volume group in the array.

Volume Group Information:Volume Group Size (GB)

Total size of the volume group in the array.

Volume Group Information:Total Space Allocated (GB)

Amount of volume group space, in Gigabytes,currently allocated to filesystems.

Volume Group Information:Total Space Allocated (%)

Amount of volume group space (in %) currentlyallocated to filesystems.

Volume Group Information:Total Space Available (GB)

Amount of unallocated volume group space, inGigabytes, available for filesystems.

Volume Group Information:Total Space Available (%)

Amount of unallocated volume group space (in%) available for filesystems.

Table 35 "Services page fields" (page 471) lists information about Servicespage fields.

Table 35Services page fields

Field Description

Network Services:Number of Active CommandLine Sessions

Number of command line interface (CLI)sessions (both remote and local) on the unit

Network Services:Number of Clients with ActiveWeb Sessions

Number of clients running one or more webGUI sessions

NTP Information:Server1 - Server 3

IP address of up to three Network TimeProtocol (NTP) servers in the network, and thestatus of the connection

NTP Information:Total Number of Servers

Number of NTP servers registered with theCS-LAN network


NN10450-900 06.023 October 2008


.

472 Reference

Table 35Services page fields (cont’d.)

Field Description

NTP Information:Accessible Servers

Number of NTP servers accessible to the SST

NTP Information:Synchronized Servers

Number of NTP servers to which the unit issynchronized

Table 36 "Administration page fields" (page 472) lists information aboutAdministration page fields.

Table 36Administration page fields

Field Description

Bootload Management:Bootload

Load ID for the NCGL platform software load

Bootload Management:Maintenance

Indicates if the Bootload is the default. Youcan choose a new default bootload if there ismore than one load available. Additional loadscan come from maintenance releases.

Software Upgrade: Protocol File transfer protocol or source location for theplatform software upgrade: FTP, AnonymousFTP, HTTP, HTTPS, Local File, or LocalCDROM

Software Upgrade: Login ID If a logon ID is required to access the upgradeplatform load from another server in thenetwork, a logon ID can be entered here.

Software Upgrade: Password If a password is required to access theupgrade platform load from another server inthe network, a password can be entered here.

Software Upgrade: IP Address If it is required to access the upgrade platformload from another server in the network, an IPaddress can be entered here.

Software Upgrade: File The target upgrade load path and filename isentered here.

Software Upgrade:ActionUpgrade button

The Upgrade button initiates a platform NCGLupgrade.

Server Maintenance (activeand inactive units)

Used to execute the Reboot, Halt,Rebootmate, and Haltmate functions.These are service affecting commands.


NN10450-900 06.023 October 2008


.

Nsbck command line options 473

Device auditsAfter a dead office recovery, several data mismatches may be presentin the network. An audit must be performed to clear up these datamismatches. Table 37 "Device audit procedures" (page 473) lists the auditprocedures available for each component and where those proceduresare located.

Table 37Device audit procedures

Component Procedures available Location

CS 2000 CoreManager orCore and BillingManager

Performing a system audit Nortel CS 2000 Core Manager FaultManagement ( (NN10082-911))

GWC Perform a GWC line data integrityauditPerform a GWC trunk data integrityauditPerform a CS 2000 data integrity auditPerform a GWC V5.2 data integrityaudit

Nortel Gateway Controller FaultManagement ( (NN10202-911))

MG 9000 Performing an audit of the MG 9000provisioning data

Nortel MG 9000 Configuration ((NN10096-511))

Nsbck command line optionsTo display online help for this command, use the -h option on thecommand line.

Step Action

1 Enter the following command as one continuous command:

/opt/MagellanNMS/bin/nsbck [-full <devtype><devname> <devaddr> <id> <pw>] [-incr <devtype><devname> <devaddr> <id> <pw>] [-view <viewname><devtype> <devname> <devaddr> <id> <pw>] [-cdir<backup_dir_path> [-f <backup_info_file] [-chost<controller_address>] [-nolog] [-log <logfile>]][-nc <#_concurrent_connections>]

where

-full indicates a full backup-incr indicates an incremental backup.-view indicates a selective backup.devtype is the name of the device type, such as

PASSPORT.devname is the name of the device.


NN10450-900 06.023 October 2008


.

474 Reference

devaddr is the IP address of the device and hasthe format n.n.n.n. id is the userID for aPassport and the READ community string for aPassport 4400/4460.

pw is the user password for a Passport and theWRITE community string for a Passport4400/4460.

viewname is the name of the view file for aselective backup. -cdir is the backupdirectory used for this backup operation.-f indicates that the backup information isobtained from a file.

backup_info_file is the name of the filecontaining backup information. Each linein the file has the same format as the -full,incr, or -view options.

-chost indicates the remote Controller to be usedin place of the Controller running on thelocal host.

controller_address is the address of theController and has the format host[:port]

-nolog indicates that output messages arediscarded.

-log indicates that output messages go tostdout/stderr or to a log file. The defaultis stdout/stderr.

logfile is the name of the file to which outputmessages go. If not specified, the messagesgo to the file mbrbackup.log in the currentdirectory (where the tool runs).

-nc indicates the number of concurrent backupsto be performed. By default, SNMP DevicesBackup tries to back up 5 different devicesconcurrently. This parameter is usefulwhen you are backing up a large number ofdevices.

#_concurrent_connections is the number ofconcurrent backups.

--End--

Backup file naming conventionThe service data backup files have the following naming convention:


NN10450-900 06.023 October 2008


.

Backup file naming convention 475

./<devtype>/<devname>/timestamp>.<dataset>/\<datafiles.

..>

Note: The period (.) represents the SNMP Devices Backup andRestore root directory.

where

devtype is the device type (PP4400, or PP4460).devname is the device nametimestamp has the format yyyymmddhhmmssdataset is the dataset name.datafiles... are the names of one or more files that

are backed up.

Note: The period (.) represents the SNMP Devices Backup andRestore root directory.


NN10450-900 06.023 October 2008


.

476 Reference


NN10450-900 06.023 October 2008


.

Carrier VoIP

Nortel Carrier Voice over IP Solutions Disaster RecoveryProceduresCopyright © 2008 Nortel NetworksAll Rights Reserved.

Printed in Canada, the United States of America, and the United KingdomRelease: (I)CVM12Publication: NN10450-900Document revision: 06.02Document release date: 3 October 2008

To provide feedback or to report a problem in this document, go to www.nortel.com/documentfeedback.

www.nortel.comLEGAL NOTICE

While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writingNORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESSOR IMPLIED. The information and/or products described in this document are subject to change without notice.

Nortel, the Nortel logo, Business Made Simple and the Globemark are trademarks of Nortel.

All other trademarks are the property of their respective owners.

cvoip solutions disaster recovery procedures-cvm12-nn10450-900_06.02

Documents