2 Database Management Procedures

Chapter 2, Database Management Procedures, describes the different options for managing the database, such as backing up data and copying database tables from one disk to another, and provides procedures for tasks associated with database applications.

2.1 Introduction

This chapter contains procedures for creating database backups or backups of the system data, and restoring the database or system data. The term “database” refers to all data that can be administered by the user including shelves, cards, links, routes, global title translation tables, and gateway screening tables. The term “system data” refers to data that cannot be administered by the user including maintenance software and generic program loads (GPLs).

These procedures are to be used as they are presented in this chapter. If these procedures are not followed, and a database backup or restore is attempted, a system failure could result.

The procedures shown in this chapter use a variety of commands. If more information on these commands is needed, go to Commands User's Guide to find the necessary information.

The database management procedures are used to perform these functions:

  • Verifying the database
  • Backing up the database
    • on the fixed disk
    • to the removable media.
    • to the FTP server
  • Restoring the database
    • from the backup partition of the fixed disk
    • from the removable media.
    • from the FTP server
  • Repairing the database
  • Copying the database from the active to the standby fixed disk
  • Backing up system data to the removable media
  • Restoring system data from a removable media
  • Formatting the fixed disk of the standby TDM
  • Formatting the removable media.

The procedures for performing database backups to the FTP server and restoring the database from the FTP server are in Remote Database Backup and Restore Procedures.

The procedures in this chapter refer to the Maintenance and Administration Subsystem Processor (MASP), Terminal Disk Module (TDM) and the Maintenance Disk and Alarm Card (MDAL), and E5-MCAP cards.

The TDM is associated with a specific E5-MCAP card. For example, the TDM in location 1114 is associated with the E5-MCAP card in location 1113 and the combination of these two cards is designated as MASP A. The TDM in location 1116 is associated with the E5-MCAP card in location 1115 and the combination of these two cards designated as MASP B. When MASP A is active, the E5-MCAP card in location 1113 and TDM in location 1114 are active. When MASP A is standby, the E5-MCAP card in location 1113 and TDM in location 1114 are standby. One MASP is always active and the other MASP is always standby.

To determine which MASP is active, enter the rept-stat-db command, the rept-stat-card command.

The output of the rept-stat-db command shows which MASP is active with the indicator (ACTV) following the TDM card location. The indicator (STDBY) following the TDM card location shows which MASP is standby.

The output of the rept-stat-card command shows which MASP is active with the entry ACTIVE in the SST field for the E5-MCAP card. The entry STANDBY in the SST field for the E5-MCAP card shows which MASP is standby.

The database commands, such as rept-stat-db, refer to the TDM because the TDM contains the fixed disk drive for the MASP.

Refer to Maintenance and Administration Subsystem for more information about the Maintenance and Administration Subsystem.

Refer to Hardware Guide for more information about the cards that make up the Maintenance and Administration Subsystem.

2.2 Removable USB Drive

Purpose:
This section is referenced in this manual by many procedures requiring the use of the removable USB thumb disk in the E5-MASP card. The procedures found in this section are recommended procedures for handling the removable USB drive in the E5-MASP card.
Requirements:
None

Procedure - Remove USB Drive

  1. Verify that the removable USB drive is locked in position and in use.

    The removable drive latch (SW1) is in the LOCKED position and the Removable Media Status LED on the E5-MASP is Off. Refer to Figure 2-1.

    Figure 2-1 Removable USB Drive LOCKED

    img/870-2903-xx_e5-masp_removable_drive_latch_locked.jpg
  2. Move SW1 from the LOCKED to the unlocked position and wait for the LED to indicate a steady blue state. See Figure 2-2.

    When SW1 is transitioned from locked to unlocked, the LED will flash blue to indicate the drive is unlocked and in process of shutting down.

    Caution:

    Removal of the drive prior to the LED indicating steady blue could result in drive corruption.

    Figure 2-2 Removable USB Drive UNLOCKED

    img/870-2903-xx_e5-masp_removable_drive_latch_unlocked.jpg
  3. When the LED indicates a steady blue state, the removable USB drive can be safely removed. The LED is off when the USB drive is fully ejected from the drive media.
    The USB drive can now be removed from the drive media.
  4. Lift the access door up, swing it past the detent position so that the door remains open on its own.
  5. Grasp the pull tab of the slide and pull the slide out slowly until it stops (it travels about a half inch).

    Caution:

    The full travel of the slide is less than an inch, do not try to pull the assembly to expose the full length of the thumb drive as this is beyond the slide’s designed travel.
  6. The USB drive is disengaged and can be taken from the inject eject assembly.
  7. Insert a USB drive into the inject-eject assembly.
  8. Grasp the pull tab of the slide and push the slide in slowly until you feel the USB drive is seated in its slot (it travels about a half inch).
  9. Close the access door.
  10. Move SW1 from the unlocked to the LOCKED position.

    When SW1 is transitioned from unlocked to locked, the LED will flash blue to indicate the drive is locked and in process of coming online.

  11. When the LED turns Off, the removable USB drive is ready for use.

2.3 Verifying the Database

Verifying the database means to check the operational status of the database. The rept-stat-db command is used to check the operational status of the database. The rept-stat-db command has three optional parameters that can be used with it, display, loc, and db.

The display parameter can use four values: brief (the default value), except, all, and version. The value for the loc parameter is the card location of the card, based on the GPL assigned to the card, whose database you wish to verify. These card locations are shown in Hardware Reference . The db parameter specifies which database to display: stp (the EAGLE databases), mps (the MPS databases) and all (both STP and MPS databases).

The operational status of the database is shown by the indicator C. This indicator shows whether the database is coherent. Coherency is an indication of whether the update to the database was successful. Each database has a coherency indicator. When an update is attempted, the coherency indicator is set to “incoherent” before the actual update is executed. When the update has been successfully completed, the coherency indicator is changed to coherent. If the update is not successful, the coherency indicator is not changed. If the coherency indicator is incoherent, this could be an indication of possible internal coherency problems when a restart is executed (for example, an index table was updated, but the corresponding data storage table was not modified).

For more information about the rept-stat-db command, refer to the rept-stat-db command description in Commands User's Guide.

Checking the Status of the Database

To check the operational status of the database:

  1. At the prompt, enter the rept-stat-db command.
  2. The output of the rept-stat-db command shows the current operational status of the EAGLE’s distributed databases.
  3. If the database is coherent, the database has no problems. The procedure is completed.

If any MPS/ELAP/EPAP database is not coherent, find the conditions shown in the output of the rept-stat-db command. Then refer to either ELAP Administration and LNP Feature Activation Guide or EPAP Administration Guide, and perform the database recovery procedures described in the RTDB / Maintenance menus.

If any STP database is not coherent, find the conditions shown in the output of the rept-stat-db command in this list and execute the appropriate command.

  • If the current partition of both fixed disks are coherent and the backup partition of the either fixed disk is not coherent, as shown in this output example, use the chg-db:action=backup:dest=fixed command. For more information, refer to Making a Backup of the Database on the Fixed Disk.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> NOT OK <<
            TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
            C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  Y       35 DIFF LEVEL             N       45 INCOHERENT
    FD CRNT  Y      106                        Y      106           
            MDAL 1117
             - --------
    RD BKUP  -    -         -        -
    

    If the E5-MASP is being used, this is an example of the rept-stat-db output.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> NOT OK <<
            TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
            C   LEVEL    TIME LAST BACKUP     C   LEVEL    TIME LAST BACKUP
            - -------- ---------------------- - -------- ----------------------
    FD BKUP Y       36 DIFF LEVEL             N       45 INCOHERENT
    FD CRNT Y      106                        Y       106
            MCAP 1113                         MCAP 1115
            - --------                        - --------
    RD BKUP Y       36 09-02-19 09:27:17 GMT  Y       36 09-02-19 09:27:17 GMT
    USB BKP -    -         -        -         Y        3 09-02-07 01:11:22 GMT
    

    The chg-db:action=backup:dest=fixed command is also used to backup the current database on both fixed disks to the backup partition of both fixed disks.

  • If the current partition of the active fixed disk is coherent and the database on the removable cartridge is not coherent, as shown in this output example, use the chg-db:action=backup:dest=remove command. For more information, refer to Making a Backup of the Database to the Removable Media.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> NOT OK <<
            TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  Y       35 09-02-01 10:19:18 GMT  Y       35 09-02-01 10:19:18 GMT
    FD CRNT  Y      106                        Y      106 
            MDAL 1117
             - --------
    RD BKUP  N      106 INCOHERENT
    

    If the E5-MASP is being used, this is an example of the rept-stat-db output.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> NOT OK <<
            TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
            C   LEVEL    TIME LAST BACKUP     C   LEVEL    TIME LAST BACKUP
            - -------- ---------------------- - -------- ----------------------
    FD BKUP Y       35 09-02-01 10:19:18 GMT  Y       35 09-02-01 10:19:18 GMT
    FD CRNT Y      106                        Y       106
            MCAP 1113                         MCAP 1115
            - --------                        - --------
    RD BKUP N      106 INCOHERENT             N      106 INCOHERENT
    USB BKP -    -         -        -         Y        3 09-02-01 01:11:22 GMT
    

    The chg-db:action=backup:dest=remove command is also used to backup the current database on both fixed disks to the removable cartridge.

  • If the backup partition of both fixed disks are coherent and the current partition of both fixed disks are not coherent, use the chg-db:action=restore:src=fixed command. For more information, refer to Restoring the Database from the Backup Partition of the Fixed Disk. This condition is shown in this example output of the rept-stat-db command.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> NOT OK <<
            TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  Y       35 09-02-01 10:19:18 GMT  Y       35 09-02-01 10:19:18 GMT
    FD CRNT  Y       35 DIFF LEVEL             N       68 INCOHERENT
             MDAL 1117
             - --------
    RD BKUP  -    -         -        -
    

    If the E5-MASP is being used, this is an example of the rept-stat-db output.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> NOT OK <<
            TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
            C   LEVEL    TIME LAST BACKUP     C   LEVEL    TIME LAST BACKUP
            - -------- ---------------------- - -------- ----------------------
    FD BKUP  Y       35 09-02-01 10:19:18 GMT  Y       35 09-02-01 10:19:18 GMT
    FD CRNT  Y       35 DIFF LEVEL             N       68 INCOHERENT
            MCAP 1113                         MCAP 1115
            - --------                        - --------
    RD BKUP Y       36 09-02-01 09:27:17 GMT  Y       36 09-02-01 09:27:17 GMT
    USB BKP -    -         -        -         Y        3 09-02-01 01:11:22 GMT
    
  • If the database on the removable cartridge is coherent and the current partition of the both fixed disks are not coherent, use the chg-db:action=restore:src=remove command. For more information, refer to Restoring the Database from the Removable Media. This condition is shown in this example output of the rept-stat-db command.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> NOT OK <<
            TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  Y       35 009-02-01 10:19:18 GMT  Y       35 09-02-01 10:19:18 GMT
    FD CRNT  Y      106 DIFF LEVEL             N       93 INCOHERENT
             MDAL 1117
             - --------
    RD BKUP  Y      106 09-01-31 14:29:03 GMT
    

    If the E5-MASP is being used, this is an example of the rept-stat-db output.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> NOT OK <<
            TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
            C   LEVEL    TIME LAST BACKUP     C   LEVEL    TIME LAST BACKUP
            - -------- ---------------------- - -------- ----------------------
    FD BKUP  Y       35 09-02-01 10:19:18 GMT  Y       35 09-02-01 10:19:18 GMT
    FD CRNT  Y      106 DIFF LEVEL             N       93 INCOHERENT
            MCAP 1113                         MCAP 1115
            - --------                        - --------
    RD BKUP Y      106 09-01-31 14:29:03 GMT  Y      106 09-01-31 14:29:03 GMT
    USB BKP -    -         -        -         Y        3 09-01-15 01:11:22 GMT
    
  • If the backup and current partitions on the active fixed disks are coherent and the backup and current partitions on the standby fixed disks are not coherent, use the chg-db:action=repair command. For more information, refer to Repairing the Database. This condition is shown in this example output of the rept-stat-db command.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> NOT OK <<
            TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  N       35 INCOHERENT             Y       55 DIFF LEVEL           
    FD CRNT  N      106 INCOHERENT             Y       55 DIFF LEVEL           
             MDAL 1117
             - --------
    RD BKUP  -    -         -        -
    

    If the E5-MASP is being used, this is an example of the rept-stat-db output.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> NOT OK <<
            TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
            C   LEVEL    TIME LAST BACKUP     C   LEVEL    TIME LAST BACKUP
            - -------- ---------------------- - -------- ----------------------
    FD BKUP  N       35 INCOHERENT             Y       55 DIFF LEVEL           
    FD CRNT  N      106 INCOHERENT             Y       55 DIFF LEVEL 
            MCAP 1113                         MCAP 1115
            - --------                        - --------
    RD BKUP Y      106 09-01-31 14:29:03 GMT  Y      106 09-01-31 14:29:03 GMT
    USB BKP -    -         -        -         Y        3 09-01-15 01:11:22 GMT
    

If, after executing the appropriate change database command, the database is still not coherent, contact the Customer Care Center. Refer to My Oracle Support (MOS) for the contact information.

2.4 Backing Up the Database Locally

The backup procedures should be performed according to the preventive maintenance procedures in Chapter 2, “Preventive Maintenance,” of Maintenance Guide. The procedures copy the current database to either the inactive (backup) partition on the fixed disk or to the removable media. To backup a database, the chg-db command uses these parameters.

:action=backup – the operation to perform on the database, a backup of the current database

:dest – the destination of the backup operation.
  • fixed – the backup partition of the fixed disk.
  • remove – the removable media for E5-based control cards installed in the EAGLE.

The database can also be backed up to the FTP server. Perform the procedure Making a Backup of the Database to the FTP Server to backup the database to the FTP server.

2.4.1 Making a Backup of the Database on the Fixed Disk

This procedure is used to make a backup of the database on the fixed disk using the chg-db command with action=backup and dest=fixed parameters.

The databases in the current partitions of both MASPs (FD CRNT) must be coherent. For more information on verifying the database, refer to Verifying the Database.

  1. Verify that the databases in the current partitions of both MASPs (FDCRNT) are coherent using the rept-stat-db command.

    This is an example of the possible output.

    
    rlghncxa03w 06-10-01 16:07:48 GMT  EAGLE5 36.0.0
    DATABASE STATUS: >> OK <<
            TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  Y       35 04-06-01 10:19:18 GMT  Y       35 04-06-01 10:19:18 GMT
    FD CRNT  Y      106                        Y      106           
             MDAL 1117
             - --------
    RD BKUP  Y      106 04-05-31 14:29:03 GMT
    

    If E5-based control cards are installed in the EAGLE, this is an example of the possible output.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> OK <<
            TDM 1114 ( STDBY )                 TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP Y        35 09-02-19 10:19:18 GMT  Y       35 09-02-19 10:19:18 GMT
    FD CRNT Y       106                        Y      106
            MCAP 1113                         MCAP 1115
            - --------                        - --------
    RD BKUP -    -         -        -         Y      106 09-02-08 14:29:03 GMT
    USB BKP -    -         -        -         Y        3 09-02-07 01:11:22 GMT
    
  2. Enter the chg-db:action=backup:dest=fixed command.

    This command can take up to 30 minutes to execute, depending on other system activity that is in progress when this command is entered. The action of this command is shown in Figure 2-3.

    Note:

    If this command takes more than 60 minutes to execute, contact My Oracle Support (MOS).

    Figure 2-3 Backup Action on the Fixed Disk

    img/t_backup_db_fixed_disk_db_mgt_procedure_dbadmin_sys_mgt-fig1.jpg

    During command execution, these messages appear (the active MASP is displayed first):

    
    BACKUP (FIXED) : MASP A - Backup starts on active MASP.
    BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
    BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
    BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.
    
  3. Verify that the databases of both MASPs are coherent using the rept-stat-db command.

    This is an example of the possible output.

    
    rlghncxa03w 06-10-01 16:07:48 GMT  EAGLE5 36.0.0
    DATABASE STATUS: >> OK <<
            TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  Y      106 04-06-01 16:09:17 GMT  Y      106 04-06-01 16:09:17 GMT
    FD CRNT  Y      106                        Y      106           
             MDAL 1117
             - --------
    RD BKUP  Y      106 04-05-31 14:29:03 GMT
    

    If E5-based control cards are installed in the EAGLE, this is an example of the possible output.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> OK <<
            TDM 1114 ( STDBY )                 TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP Y       106 09-03-01 16:09:18 GMT  Y      106 09-03-01 16:09:18 GMT
    FD CRNT Y       106                        Y      106
            MCAP 1113                         MCAP 1115
            - --------                        - --------
    RD BKUP -    -         -        -         Y      106 09-02-08 14:29:03 GMT
    USB BKP -    -         -        -         Y        3 09-02-07 01:11:22 GMT
    

Figure 2-4 Making a Backup of the Database on the Fixed Disk



2.4.2 Making a Backup of the Database to the Removable Media

This procedure is used to make a backup of the database to the removable media using the chg-db command with the action=backup and dest=remove parameters. The dest=usb parameter is also used for making backup to the USB drive in the flush-mounted USB port.

The database in the current partition of the active MASP (FD CRNT) must be coherent. For more information on verifying the database, refer to Verifying the Database.

Formatting blank removable media for E5-based control cards that are installed in the EAGLE is required. If the removable media is not formatted, perform Formatting Removable Media to format the media.

  1. Verify that the database in the current partition of the active MASP (FDCRNT) is coherent using the rept-stat-db command.

    This is an example of the possible output.

    
    rlghncxa03w 06-10-13 16:07:48 GMT  EAGLE5 45.0.0
    DATABASE STATUS: >> OK <<
            E5TDM 1114 ( STDBY)                 E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  Y       35 04-06-01 10:19:18 GMT  Y       35 04-06-01 10:19:18 GMT
    FD CRNT  Y      106                        Y      106           
             E5MDAL 1117
             - --------
    RD BKUP  -    -         -        -
    

    The following is an example of the possible output.

    
    rlghncxa03w 06-03-13 16:07:48 GMT  EAGLE5 45.0.0
    DATABASE STATUS: >> OK <<
            E5TDM 1114 ( STDBY )                 E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP Y        35 09-02-19 10:19:18 GMT  Y       35 09-02-19 10:19:18 GMT
    FD CRNT Y       106                        Y      106
            E5MCAP 1113                         E5MCAP 1115
            - --------                        - --------
    RD BKUP -    -         -        -         -    -         -        - 
    USB BKP -    -         -        -         -    -         -        - 
    

    If the database in the current partition of the active MASP is not coherent, refer to Verifying the Database to resolve the database problem.

    If the database in the current partition of the active MASP is coherent, or after the database problem has been resolved, continue the procedure by performing one of these steps.

  2. The database can be backed up to the removable media in the active MASP or in both MASPs (if the removable media is present in both MASPs).

    Perform one of these substeps.

    1. If the database will be backed up to the removable media in both MASPs, check the removable media drives in both MASPs for removable media.
      If removable media is present in both MASPs, continue the procedure by performing one of these steps.
      • If the removable media will be used for the backup, continue the procedure with 3. When the backup is performed, the database in the current partition of each fixed disk is copied to the corresponding removable media on each MASP.
      • If the removable media will not be used for the backup, remove the media that will not be used for the backup and insert the media that will be used for the backup. Refer to Removable USB Drive for information about removing and inserting the removable media. After the media has been inserted into the removable media drives, continue the procedure with 3.

      If the removable media drives in both MASPs are empty, insert the media that will be used for the backup. Refer to Removable USB Drive for information about inserting the removable media. After the media has been inserted into the removable media drives, continue the procedure with 3.

      If the removable media drive in only one MASP contains removable media, continue the procedure by performing one of these steps.
      • If the removable media that is present will be used for the backup, insert the media that will be used for the backup into the empty removable media drive. Refer to Removable USB Drive for information about inserting the removable media. After the media has been inserted into the removable media drive, continue the procedure with 3.
      • If the removable media that is present will not be used for the backup, remove the media from that removable media drive and insert the media that will be used for the backup into both removable media drives. Refer to Removable USB Drive for information about removing and inserting the removable media. After the media has been inserted into the removable media drives, continue the procedure with 3.
    2. If the database will be backed up to the removable media in only one MASP, the removable media must be inserted in the removable media drive on the active MASP. Check the removable media drives in both MASPs for removable media.

      If removable media is inserted into the removable media drive on active MASP and no removable media is inserted into the removable media drive on the standby MASP, and this media will be used for the backup, continue the procedure with 3. When the backup is performed, the database in the current partition of the fixed disk on the active MASP is copied to the removable media on the active MASP.

      If removable media is inserted into the removable media drive on active MASP and no removable media is inserted into the removable media drive on the standby MASP, and this media will not be used for the backup, remove the media from the removable media drive and insert the media that will be used for the backup into the removable media drive on the active MASP. After the media has been inserted, continue the procedure with 3.

      If removable media is inserted into the removable media drive on standby MASP and no removable media is inserted into the removable media drive on the active MASP, remove the media from the removable media drive and insert the media that will be used for the backup into the removable media drive on the active MASP. After the media has been inserted, continue the procedure with 3.

      If removable media drives in both MASPs are empty, insert the media that will be used for the backup into the removable media drive on the active MASP. After the media has been inserted, continue the procedure with 3.

  3. Backup the database by entering this command.

    chg-db:action=backup:dest=remove

    During command execution, these messages should appear.

    
    BACKUP (REMOVABLE) : MASP A - Backup starts on active MASP.
    BACKUP (REMOVABLE) : MASP A - Backup to removable device complete.
    

    Note:

    This command can take up to 30 minutes to execute, depending on the size of the database and other system activity that is in progress when this command is entered. If this command takes more than 60 minutes to execute, contact the Customer Care Center for assistance. Refer to My Oracle Support (MOS) for the contact information.
  4. Verify that the databases on the removable media (RD BKUP on both MASPs or the active MASP if the backup was performed only to the removable media on the active MASP) and the current partition of the active MASP (FD CRNT) are coherent using the rept-stat-db command.

    If the database was backed up to the removable media, this is an example of the possible output.

    
    rlghncxa03w 06-03-13 16:07:48 GMT  EAGLE5 45.5.0
    DATABASE STATUS: >> OK <<
            E5TDM 1114 ( STDBY )                 E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP Y        35 09-02-19 10:19:18 GMT  Y       35 09-02-19 10:19:18 GMT
    FD CRNT Y       106                        Y      106
            E5MCAP 1113                          E5MCAP 1115
            - --------                         - --------
    RD BKUP Y       106 09-03-23 16:09:53 GMT  Y      106 09-03-23 16:09:53 GMT 
    USB BKP -    -         -        -         -    -         -        - 
    

    Note:

    If the database was backed up to only the removable media on the active MASP, then only the RD BKUP entry for the active MASP (in this example, MCAP 1115) is displayed.
  5. If the database was backed up to the removable media, remove the removable media from the removable media drives on the MASPs. For more information on removing the removable media from the removable media drives, refer to Removable USB Drive.
  6. Label the removable media 1 through 4 if the backup is performed weekly or monthly, A through D if the backup is performed quarterly.

    For more information on labeling the removable media, see Chapter 2, “Preventive Maintenance,” in Maintenance Guide.

Figure 2-5 Making a Backup of the Database to the Removable Cartridge or Removable Media



Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4

2.5 Restoring the Database Locally

The restore procedures are used to bring a database from the backup partition of both MASPs and load the database onto the current partitions of both MASPs. It is also used to load a database from a removable media on to the current partitions of both MASPs. To restore a database, the chg-db command uses these parameters.

:action=restore – the operation to perform on the database, restoring a previously backed up database

:src – the source of the database that is being restored.
  • fixed – the backup partition of the fixed disk.
  • remove – the removable media for E5-based control cards installed in the EAGLE.
  • sloc – the source location (either 1113 or 1115) of the MASP that contains the removable media from which the database will be restored. The sloc parameter can be specified only with the src=remove parameter.

The database can also be restored from the FTP server. Perform the procedure Restoring the Database from the FTP Server, to restore the database from the FTP server.

Caution:

If the restore device state option is on, shown by the ON value for the RSTRDEV field in the rtrv-stpopts command output, the state of the cards, SS7 signaling links, TCP/IP data links, and terminals before the chg-db:action=restore and init-sys commands are performed will not be maintained after these commands are performed. The persistent device state table becomes obsolete and is disabled. UIM 1257 is generated.
rlghncxa03w 06-10-01 16:07:48 GMT  EAGLE5 36.0.0
1234.1257    SYSTEM       INFO  DB Restore has cleared and disabled PDS

2.5.1 Restoring the Database from the Backup Partition of the Fixed Disk

This procedure is used to restore the database from the backup partition of the fixed disk using the chg-db command with the action=restore and src=fixed parameters.

The databases in the backup partitions of both MASPs (RD BKUP) must be coherent. For more information on verifying the database,refer to Verifying the Database.

Caution:

Using the action=restore parameter with the chg-db command is an emergency recovery procedure, and requires the init-sys command to download the restored database to all the cards in the EAGLE 5
  1. Verify that the databases in the backup partitions of both MASPs (FD BKUP) are coherent using the rept-stat-db command.

    The following is an example of the possible output:

    
    rlghncxa03w 13-07-01 16:07:48 GMT  EAGLE5 45.0.0
    DATABASE STATUS: >> OK <<
            E5TDM 1114 ( STDBY)                 E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  Y       35 04-06-01 10:19:18 GMT  Y       35 04-06-01 10:19:18 GMT
    FD CRNT  Y      106                        Y      106           
             E5MDAL 1117
             - --------
    RD BKUP  -    -         -        -
    

    The following is an example of the possible output:

    
    rlghncxa03w 13-06-01 16:07:48 GMT  EAGLE5 45.0.0
    DATABASE STATUS: >> OK <<
            E5TDM 1114 ( STDBY )                 E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP Y        35 09-02-19 10:19:18 GMT  Y       35 09-02-19 10:19:18 GMT
    FD CRNT Y       106                        Y      106
            E5MCAP 1113                         E5MCAP 1115
            - --------                        - --------
    RD BKUP -    -         -        -         -    -         -        - 
    USB BKP -    -         -        -         -    -         -        - 
    
  2. Enter the chg-db:action=restore:src=fixed command.

    This command can take up to 30 minutes to execute, depending on other system activity that is in progress when this command is entered.

    Note:

    If this command takes more than 60 minutes to execute, contact the Customer Care Center for assistance. Refer to My Oracle Support (MOS) for the contact information.

    During command execution, these messages appear (the active MASP is displayed first):

    
    RESTORE (FIXED) : MASP A - Restore starts on active MASP.
    RESTORE (FIXED) : MASP A - Restore from fixed disk on active MASP complete.
    RESTORE (FIXED) : MASP A - Restore starts on standby MASP.
    RESTORE (FIXED) : MASP A - MASP(s) will reboot to load data.
    RESTORE (FIXED) : MASP A - Restore from fixed disk on stdby MASP complete.
    

    The action of this command is shown in Figure 2-6.

    Figure 2-6 Restore Action on the Fixed Disk

    img/t_restore_db_from_backup_partition_fixed_disk_db_mgt_procedure_dbadmin_sys_mgt-fig1.jpg
  3. When the commands have successfully completed, re-initialize the EAGLE 5 using the init-sys command.

    Caution:

    The init-sys command causes a complete reload of the EAGLE 5, and should only be used during periods of low traffic. Using this command ensures that all cards are running the same database, but will interrupt service.

    Note:

    The init-sys command must be entered twice within 30 seconds for the EAGLE 5 to be re-initialized. If the init-sys command is not executed twice within 30 seconds, the attempt to re-initialize the EAGLE 5 is aborted.

    When the init-sys command is first entered, this message should appear.

    
    rlghncxa03w 06-10-01  07:05:01 GMT  EAGLE5 36.0.0
    CAUTION: This command causes a complete system reload, and
    will result in traffic loss.
    Re-enter command within 30 seconds to confirm.
    

    When the init-sys command is re-entered within the 30 second time limit, this message should appear.

    
    rlghncxa03w 06-10-01  07:05:17 GMT  EAGLE5 36.0.0
    Init System command issued at terminal #3
    

    From the time that the init-sys command is accepted, you must wait approximately 2 minutes before you can perform step 4 (logging into the EAGLE 5). If the EAGLE 5 terminal is in the VT-100/VT-320 mode, the terminal display will be refreshed with non-zero alarm counts. During this 2 minutes interval, an intermediate screen refresh caused by the MASPs role change from active to standby, and from standby to active. This screen refresh is typically a partial refresh and the alarm indicators are set to zero.

    If you are logged into the EAGLE 5 in the KSR mode, the only response you will receive that you are now able to log into the EAGLE 5 is that you will receive UAM 0009, MASP became active. UAM 0009 could be issued twice due to possible transient MASP role change (switching from active to standby). Following the execution of the init-sys command, the MASP that was active before the init-sys command was entered will be the active MASP when the EAGLE 5 has finished reinitializing.

  4. Log into the EAGLE 5 using the login or act-user command.

    This is an example of the messages that appear when you have successfully logged onto the EAGLE 5.

    
    NOTICE: This is a private computer system. 
    Unauthorized access or use may lead to prosecution. 
    
    0 LOGIN failures since last successful LOGIN
    Last successful LOGIN was on port 4 on 04-06-01 @ 09:34:56
    
  5. Verify that the databases of both MASPs are coherent using the rept-stat-db command.

    This is an example of the possible output.

    
    rlghncxa03w 13-06-01 16:07:48 GMT  EAGLE5 45.0.0
    DATABASE STATUS: >> OK <<
            E5TDM 1114 ( STDBY)                 E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  Y       35 04-06-01 10:19:18 GMT  Y       35 04-06-01 10:19:18 GMT
    FD CRNT  Y       35                        Y       35           
             E5MDAL 1117
             - --------
    RD BKUP  -    -         -        -
    

    The following is an example of the possible output:

    
    rlghncxa03w 13-07-01 16:07:48 GMT  EAGLE5 45.0.0
    DATABASE STATUS: >> OK <<
            E5TDM 1114 ( STDBY )                 E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP Y        35 09-02-19 10:19:18 GMT  Y       35 09-02-19 10:19:18 GMT
    FD CRNT Y        35                        Y       35
            E5MCAP 1113                         E5MCAP 1115
            - --------                        - --------
    RD BKUP -    -         -        -         -    -         -        - 
    USB BKP -    -         -        -         -    -         -        - 
    

Figure 2-7 Restoring the Database from the Backup Partition of the Fixed Disk



2.5.2 Restoring the Database from the Removable Media

This procedure is used to restore the database from the removable media using the chg-db command with the action=restore and src=remove parameters. The src=usb parameter is also used for restoring the database from the USB drive in the flush-mounted USB port.

Removable media that contains the database being restored must be inserted into the removable media drive in one or both of the MASPs. When the database is being restored, the database on the removable media in one of the MASPs is copied to the current partition of both fixed disks. The removable media to copy the database from is specified with the sloc parameter. The value of the sloc parameter is the location of the MASP that contains the removable media, either 1113 or 1115, that the database will be copied from. The sloc parameter is optional. If the sloc parameter is not specified, the database will be copied from the removable media in the active MASP. If removable media is installed in both MASPs, and the database levels of the removable media are not the same, the sloc parameter must be specified with the chg-db command. The database on the removable media (RD BKUP) must be coherent. If the database on the removable media is not coherent, contact the Customer Care Center for assistance. Refer to My Oracle Support (MOS) for the contact information.

Caution:

Using the action=restore parameter with the chg-db command is an emergency recovery procedure, and requires the init-sys command to download the restored database to all the cards in the EAGLE.
  1. Verify the control cards that are installed in the EAGLE.

    Refer to Maintenance and Administration Subsystem for information about the control cards.

  2. Verify that the database on the removable media (RD BKUP) is coherent using the rept-stat-db command.
    1. The following is an example of the possible output.
      
      rlghncxa03w 06-10-13 16:07:48 GMT  EAGLE5 45.0.0
      DATABASE STATUS: >> OK <<
              E5TDM 1114 ( STDBY )                 E5TDM 1116 ( ACTV )
               C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
               - -------- ---------------------  - -------- ---------------------
      FD BKUP Y        35 09-10-01 10:19:18 GMT  Y       35 09-10-01 10:19:18 GMT
      FD CRNT Y        95                        Y       95
              E5MCAP 1113                          E5MCAP 1115
              - --------                         - --------
      RD BKUP Y       106 09-09-30 16:09:53 GMT  Y      106 09-09-30 16:09:53 GMT 
      USB BKP -    -         -        -         -    -         -        - 
      
      If removable media is installed in the MASP that you wish to use to restore the database, and you wish to use this media to restore the database, continue the procedure by performing one of these actions.
      • If the database is coherent, continue the procedure with 3.
      • If the database is not coherent, contact the Customer Care Center for assistance. Refer to My Oracle Support (MOS) for the contact information.
      If removable media is installed in the MASP that you wish to use to restore the database, but you do not wish to use this media to restore the database, continue the procedure by performing these actions.
      • Remove the media from the removable media drive.
      • Insert the removable media that does contain the database that you wish to use to restore the database into the removable media drive that you wish to use.
      • Enter the rept-stat-db command.
      • If the database is coherent, continue the procedure with 3.
      • If the database is not coherent, contact the Customer Care Center for assistance. Refer to My Oracle Support (MOS) for the contact information.
      If removable media is not installed in the MASP that you wish to use to restore the database, continue the procedure by performing these actions.
      • Insert the removable media that does contain the database that you wish to use to restore the database into the removable media drive that you wish to use.
      • Enter the rept-stat-db command.
      • If the database is coherent, continue the procedure with 3.
      • If the database is not coherent, contact the Customer Care Center for assistance. Refer to My Oracle Support (MOS) for the contact information.
  3. Restore the database by performing one of these substeps.
    1. Enter the following command.

      chg-db:action=restore:src=remove

      During command execution, these messages should appear.

      
      RESTORE (REMOVABLE) : MASP A - Restore starts on active MASP.
      RESTORE (REMOVABLE) : MASP A - Restore starts on standby MASP.
      RESTORE (REMOVABLE) : MASP A - MASP(s) will reboot to load data.
      RESTORE (REMOVABLE) : MASP A - Restore from removable drive complete.
      

      Note:

      This command can take up to 30 minutes to execute, depending on the size of the database and other system activity that is in progress when this command is entered. If this command takes more than 60 minutes to execute, contact the Customer Care Center for assistance. Refer to My Oracle Support (MOS) for the contact information.

      After this command has completed, continue the procedure with 4.

    2. When the database is being restored from removable media, the database on the removable media in one of the MASPs is copied to the current partition of both fixed disks.

      The removable media to copy the database from can be specified with the sloc parameter. The value of the sloc parameter is the location of the MASP that contains the removable media, either 1113 or 1115, that the database will be copied from. The sloc parameter is optional. If the sloc parameter is not specified, the database will be copied from the removable media in the active MASP. If removable media is installed in both MASPs, and the database levels of the removable media are not the same, the sloc parameter must be specified with the chg-db command.

      For this example, enter this command.

      chg-db:action=restore:src=remove:sloc=1113

      During command execution, these messages should appear.

      
      RESTORE (REMOVABLE) : MASP A - Restore starts on active MASP.
      RESTORE (REMOVABLE) : MASP A - Restore starts on standby MASP.
      RESTORE (REMOVABLE) : MASP A - MASP(s) will reboot to load data.
      RESTORE (REMOVABLE) : MASP A - Restore from removable drive complete.
      

      Note:

      This command can take up to 30 minutes to execute, depending on the size of the database and other system activity that is in progress when this command is entered. If this command takes more than 60 minutes to execute, contact My Oracle Support for assistance. Refer to My Oracle Support (MOS) for the contact information.

      After this command has completed, continue the procedure with 4.

  4. When the commands have successfully completed, re-initialize the EAGLE using the init-sys command.

    Caution:

    The init-sys command causes a complete reload of the EAGLE, and should only be used during periods of low traffic. Using this command ensures that all cards are running the same database, but will interrupt service.

    Note:

    The init-sys command must be entered twice within 30 seconds for the EAGLE to be re-initialized. If the init-sys command is not executed twice within 30 seconds, the attempt to re-initialize the EAGLE is aborted.

    When the init-sys command is first entered, this message should appear.

    
    rlghncxa03w 06-10-01  07:05:01 GMT  EAGLE5 36.0.0
    CAUTION: This command causes a complete system reload, and
    will result in traffic loss.
    Re-enter command within 30 seconds to confirm.
    

    When the init-sys command is re-entered within the 30 second time limit, this message should appear.

    
    rlghncxa03w 06-10-01  07:05:17 GMT  EAGLE5 36.0.0
    Init System command issued at terminal #3
    

    From the time that the init-sys command is accepted, you must wait approximately 2 minutes before you can perform 5 (logging into the EAGLE). If the EAGLE terminal is in the VT-100/VT-320 mode, the terminal display will be refreshed with non-zero alarm counts. During this 2 minutes interval, an intermediate screen refresh caused by the MASPs role change from active to standby, and from standby to active. This screen refresh is typically a partial refresh and the alarm indicators are set to zero.

    If you are logged into the EAGLE in the KSR mode, the only response you will receive that you are now able to log into the EAGLE is that you will receive UAM 0009, MASP became active. UAM 0009 could be issued twice due to possible transient MASP role change (switching from active to standby). Following the execution of the init-sys command, the MASP that was active before the init-sys command was entered will be the active MASP when the EAGLE has finished reinitializing.

  5. Log into the EAGLE using the login or act-user command.

    This is an example of the messages that appear when you have successfully logged into the EAGLE.

    
    NOTICE: This is a private computer system. 
    Unauthorized access or use may lead to prosecution. 
    
    0 LOGIN failures since last successful LOGIN
    Last successful LOGIN was on port 4 on 04-06-01 @ 09:34:56
    
  6. Verify that the databases on the removable media (RD BKUP), and the current partitions of both MASPs (FD CRNT) are coherent using the rept-stat-db command.

    The following is an example of the possible output:

    
    rlghncxa03w 06-10-13 16:07:48 GMT  EAGLE5 45.0.0
    DATABASE STATUS: >> OK <<
            E5TDM 1114 ( STDBY )               E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP Y        35 09-10-01 10:19:18 GMT  Y       35 09-10-01 10:19:18 GMT
    FD CRNT Y        95                        Y       95
            E5MCAP 1113                        E5MCAP 1115
            - --------                         - --------
    RD BKUP Y       106 09-09-30 16:09:53 GMT  Y      106 09-09-30 16:09:53 GMT 
    USB BKP -    -         -        -         -    -         -        - 
    

    This procedure is finished.

  7. Remove the removable media from the removable media drive on the E5-MDAL card.

2.6 Repairing the Database

Perform the repair procedure whenever the two fixed disks have a different database image, such as after a MASP failure. This procedure copies the fixed disk image of the database associated with the active MASP to the fixed disk of the standby MASP. Figure 2-8 illustrates this action. To repair a database, The chg-db command uses only one parameter, action=repair – the operation to perform on the database, repairing a database

Figure 2-8 Action of the Repair Procedure

img/t_repair_db_db_mgt_procedure_dbadmin_sys_mgt-fig1.jpg

To repair the database, perform this procedure.

The databases in the current (FD CRNT) and the backup (FD BKUP) partitions of the active MASP must be coherent. For more information on verifying the database, refer to Verifying the Database.

Caution:

To prevent any potential database corruption when performing this procedure, the terminals must be placed out of service with the rmv-trm command before executing the chg-db:action=repair command.
  1. Verify that the databases in the current (FDCRNT) and the backup (FDBKUP) partitions of the active MASP are coherent using the rept-stat-dbcommand.

    This is an example of the possible output.

    
    rlghncxa03w 13-07-01 16:07:48 GMT  EAGLE5 45.0.0
    DATABASE STATUS: >> NOT OK <<
             E5TDM 1114 ( STDBY)               E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  N       35 INCOHERENT             Y       55 DIFF LEVEL           
    FD CRNT  N      106 INCOHERENT             Y       55 
             E5MDAL 1117
             - --------
    RD BKUP  -    -         -        -
    

    If E5-based control cards are installed in the EAGLE, this is an example of the possible output.

    
    rlghncxa03w 13-07-01 16:07:48 GMT  EAGLE5 45.0.0
    DATABASE STATUS: >> OK <<
             E5TDM 1114 ( STDBY )              E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  N       35 INCOHERENT             Y       55 DIFF LEVEL           
    FD CRNT  N      106 INCOHERENT             Y       55 
            E5MCAP 1113                         E5MCAP 1115
            - --------                        - --------
    RD BKUP -    -         -        -         -    -         -        - GMT
    USB BKP -    -         -        -         -    -         -        - GMT
    
  2. Display the terminal configuration in the database with the rtrv-trm command.

    The SEAS terminals are shown in the output with the entry SEAS in the TYPE field. This is an example of the possible output. In this example, the SEAS terminals are terminals 18 and 27. If no SEAS terminals are shown in the rtrv-trm command output, go to step 5.

    
    rlghncxa03w 10-07-01 16:02:08 GMT EAGLE5 42.0.0
    TRM  TYPE     COMM        FC    TMOUT MXINV DURAL
    1    VT320    9600-7-E-1  SW    30    5     99:59:59
    2    KSR      9600-7-E-1  HW    30    5     INDEF
    3    PRINTER  4800-7-E-1  HW    30    0     00:00:00
    4    VT320    2400-7-E-1  BOTH  30    5     00:30:00
    5    VT320    9600-7-O-1  NONE  30    5     00:00:30
    6    VT320    9600-7-O-1  NONE  30    5     00:00:30
    7    PRINTER  9600-7-N-2  HW    30    5     00:30:00
    8    KSR     19200-7-E-2  BOTH  30    5     00:30:00
    9    VT320    9600-7-O-1  NONE  30    5     00:00:30
    10   VT320    9600-7-E-1  HW    30    5     00:30:00
    11   VT320    4800-7-E-1  HW    30    5     00:30:00
    12   PRINTER  9600-7-E-1  HW    30    4     00:30:00
    13   VT320    9600-7-O-1  NONE  30    5     00:30:00
    14   VT320    9600-7-E-2  SW    30    8     00:30:00
    15   VT320    9600-7-N-2  HW    30    5     00:30:00
    16   VT320    9600-7-E-2  BOTH  30    3     00:30:00
    
    TRM  TYPE      LOC              TMOUT MXINV DURAL      SECURE
    17   TELNET    1201             60    5     00:30:00   yes
    18   SEAS      1201             60    5     00:30:00   yes
    19   TELNET    1201             60    5     00:30:00   yes
    20   TELNET    1201             60    5     00:30:00   yes
    21   TELNET    1201             60    5     00:30:00   yes
    22   TELNET    1201             60    5     00:30:00   yes
    23   TELNET    1201             60    5     00:30:00   yes
    24   TELNET    1201             60    5     00:30:00   yes
    25   TELNET    1203             60    5     00:30:00   yes
    26   TELNET    1203             60    5     00:30:00   yes
    27   SEAS      1203             60    5     00:30:00   yes
    28   TELNET    1203             60    5     00:30:00   yes
    29   TELNET    1203             60    5     00:30:00   yes
    30   TELNET    1203             60    5     00:30:00   yes
    31   TELNET    1203             60    5     00:30:00   yes
    32   TELNET    1203             60    5     00:30:00   yes
    33   TELNET    1205             60    5     00:30:00   yes
    34   TELNET    1205             60    5     00:30:00   yes
    35   TELNET    1205             60    5     00:30:00   yes
    36   TELNET    1205             60    5     00:30:00   yes
    37   TELNET    1205             60    5     00:30:00   yes
    38   TELNET    1205             60    5     00:30:00   yes
    39   TELNET    1205             60    5     00:30:00   yes
    40   TELNET    1205             60    5     00:30:00   yes
    

    Note:

    The rtrv-trm command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-trm command, see the rtrv-trm command description in Commands User's Guide.
  3. Display the status of the terminals with the rept-stat-trm command with the terminal number of the SEAS terminals.

    For this example, enter these commands.

    rept-stat-trm:trm=18

    This is an example of the possible output.

    
    rlghncxa03w 06-10-01 15:08:45 GMT EAGLE5 36.0.0
    TRM   PST           SST           AST
    18     IS-NR         Active        -----
    Command Completed.
    

    rept-stat-trm:trm=27

    This is an example of the possible output.

    
    rlghncxa03w 06-10-01 15:08:45 GMT EAGLE5 36.0.0
    TRM   PST           SST           AST
    27     IS-NR         Active        -----
    Command Completed.
    
  4. Place the SEAS terminals out of service using the rmv-trm command with the number of the terminal displayed in step 3 whose state is not OOS-MT-DSBLD.

    The force=yes parameter must be used when placing the last SEAS terminal out of service.

    For this example, enter these commands.

    rmv-trm:trm=18

    rmv-trm:trm=27:force=yes

    If the status of the SEAS terminals shown in the PST field in step 3 is OOS-MT-DSBLD (out-of-service maintenance disabled), the terminal is already out of service and the rmv-trm command does not need to be executed for that terminal.

    This message should appear when each of these commands have successfully completed.

    
    rlghncxa03w 06-10-01 15:08:45 GMT EAGLE5 36.0.0
    Inhibit message sent to terminal
    
    rlghncxa03w 06-10-01 15:08:45 GMT EAGLE5 36.0.0
    Command Completed.
    
  5. Enter the chg-db:action=repair command.

    This command can take up to 30 minutes to execute, depending on the size of the database and other system activity that is in progress when this command is entered.

    Note:

    If this command takes more than 60 minutes to execute, contact My Oracle Support (MOS).

    During command execution, these messages appear:

    
    REPAIR: MASP A - Repair starts on standby MASP.
    REPAIR: MASP A - Standby MASP will reboot to load data.
    REPAIR: MASP A - Repair from fixed disk complete.
    
  6. Verify that the databases of both MASPs are coherent using the rept-stat-dbcommand.

    The following is an example of the possible output:

    
    rlghncxa03w 13-07-01 16:07:48 GMT  EAGLE5 45.0.0
    DATABASE STATUS: >> OK <<
             E5TDM 1114 ( STDBY )              E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  N       55 09-03-01 13:11:43 GMT  Y       55 09-03-01 13:11:43 GMT
    FD CRNT  N       55                        Y       55  
            E5MCAP 1113                        E5MCAP 1115
            - --------                        - --------
    RD BKUP -    -         -        -         -    -         -        - GMT
    USB BKP -    -         -        -         -    -         -        - GMT
    

    If SEAS terminals are shown in the rtrv-trm command output in step 2, go to step 7. Otherwise this procedure is completed.

  7. Put the SEAS terminals back into service with the rst-trm command with the number of the terminals specified in step 4.

    For this example, enter these commands.

    rst-trm:trm=18

    rst-trm:trm=27

    This message should appear when each command has successfully completed.

    
    rlghncxa03w 06-10-01 15:08:45 GMT EAGLE5 36.0.0
    Allow message sent to terminal
    
    rlghncxa03w 06-10-01 15:08:45 GMT EAGLE5 36.0.0
    Command Completed.
    

Figure 2-9 Repairing the Database



2.7 Copying the Database from the Active to the Standby Fixed Disk

This procedure copies everything on the active fixed disk to the standby fixed disk using the copy-disk command. Figure 2-10 shows the action of the copy-disk command.

Figure 2-10 Action of the Copy Disk Procedure


img/t_copy_database_from_active_to_standby_fixed_disk_db_mgt_procedure_dbadmin_sys_mgt-fig1.jpg

The copy-disk command uses these parameters.

:sloc – the card location of the active fixed disk

:dloc – the card location of the standby fixed disk

:force – does the standby fixed disk contain system data? This parameter provides some protection against data loss from copying over a fixed disk containing system data. If the standby fixed disk contains system data, you must specify the force=yes parameter. The default value for this parameter is no.

:format – is the standby fixed disk to be formatted before the data from the active fixed disk is copied to the standby fixed disk? The default value for this parameter is yes, the standby fixed disk will be formatted before copying.

Specify the format=no parameter with the copy-disk command to copy to the standby fixed disk without formatting the standby fixed disk. The standby fixed disk must be properly formatted to specify the format=no parameter. If the standby fixed disk is not properly formatted and the format=no parameter is specified, the copy-disk command will be rejected with this message.

E2819 Cmd Rej: Destination disk is unformatted

Note:

The performance time required to copy a fixed disk to another fixed disk varies depending on database size and system activity. This operation should typically take no longer than 2.5 hours. If you are not performing the low-level format (format=no), the operation should take no longer than 1 hour. If the copy-disk operation exceeds 3 hours, contact My Oracle Support for assistance. Refer to My Oracle Support (MOS) for the contact information. If the copy-disk operation without the low-level format exceeds 1.5 hours, contact My Oracle Support.

The databases in the current (FD CRNT) and the backup (FD BKUP) partitions of the active MASP must be coherent. For more information on verifying the database, refer to the Verifying the Database section. Measurements must be inhibited.

The standby fixed disk cannot be formatted if the security log on the standby fixed disk contains any entries that have not been copied to the FTA area of the fixed disk. This can be verified with the rept-stat-seculog command. If the security log on the standby fixed disk contains entries that have not been copied to the file transfer area of the fixed disk, copy these entries to the file transfer area using the copy-seculog command.

The copy-disk command can be executed if the status of the security log on the standby fixed disk cannot be determined. This allows the copy-disk command to format and initialize a previously un-initialized fixed disk. An un-initialized fixed disk does not contain a security log.

Caution:

To prevent any potential database corruption when performing this procedure, the SEAS terminals must be placed out of service with the rmv-trm command before executing the copy-disk command.
  1. Verify that the databases in the current (FDCRNT) and the backup (FDBKUP) partitions of the active MASP are coherent using the rept-stat-dbcommand.

    This is an example of the possible output.

    
    rlghncxa03w 06-10-01 16:07:48 GMT  EAGLE5 36.0.0
    DATABASE STATUS: >> NOT OK <<
            E5TDM 1114 ( STDBY)                 E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  Y       75 04-06-01 13:11:43 GMT  Y       95 04-06-01 13:11:43 GMT
    FD CRNT  N       55 DIFF LEVEL             Y      105     
             E5MDAL 1117
             - --------
    RD BKUP  -    -         -        -
    

    If E5-based control cards are installed in the EAGLE, this is an example of the possible output.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> OK <<
            E5TDM 1114 ( STDBY )                 E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  Y       75 09-02-19 10:19:18 GMT  Y       95 09-02-19 10:19:18 GMT
    FD CRNT  N       55 DIFF LEVEL             Y      105
            E5MCAP 1113                         E5MCAP 1115
            - --------                        - --------
    RD BKUP -    -         -        -         -    -         -        -
    USB BKP -    -         -        -         -    -         -        -
    
  2. Verify whether or nor the Measurements Platform option is enabled (PLATFORMENABLE = on) using the rtrv-measopts command.
    
    rlghncxa03w 06-10-01 16:02:05 GMT  EAGLE5 36.0.0
    PLATFORMENABLE   = on
    COLLECT15MIN     = off
    CLLIBASEDNAME    = off
    ----------------------
    SYSTOTSTP        = off
    SYSTOTTT         = off
    

    Note:

    The rtrv-measopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-measopts command, see the rtrv-measopts command description in Commands User's Guide.
    • If the Measurements Platform is enabled, continue the procedure with 5.
    • If the Measurements Platform is not enabled, continue the procedure with 3.
  3. Verify that measurement collection is on or off using the rtrv-meas-sched command.

    This is an example of the possible output. The COLLECT field shows whether measurement collection is on or off. In this example, measurement collection is on.

    
    rlghncxa03w 06-10-01 12:22:55 GMT EAGLE5 36.0.0 
    COLLECT        =  on
    GTWYLSFLTR     =  both
    ---------------------
    SYSTOT-STP     =  off
    SYSTOT-TT      =  off
    COMP-LNKSET    =  off
    COMP-LINK      =  on
    GTWY-STP       =  on
    GTWY-LNKSET    =  on
    MTCD-STP       =  on
    MTCD-LINK      =  on
    MTCD-LNKSET    =  on
    
    • If measurement collection is off, continue the procedure with 5.
    • If measurement collection is on, continue the procedure with 4.
  4. Inhibit all measurements using the chg-meas:collect=off command.

    Caution:

    Measurement collection must be turned off or the copy-disk command cannot be executed. The chg-meas:collect=on command should not be executed while the copy-disk command is in progress. If possible, do not turn off measurement collection at midnight since doing so can cause the loss of an entire day of measurements. For the period of time that measurement collection is turned off, those measurements will be lost.

    This message should appear.

    
    rlghncxa03w 06-10-01 16:12:50 GMT  EAGLE5 36.0.0
    CHG-MEAS: MASP A - COMPLTD
    
  5. Verify that the security log on the standby MASP contains no entries that must be copied to the FTA area of the fixed disk with the rept-stat-seculog command.

    This is an example of the possible output.

    
    rlghncxa03w 06-10-01 15:59:06 GMT EAGLE5 36.0.0
                 -- SINCE LAST UPLOAD --  OLDEST   NEWEST   LAST
    LOC  ROLE    ENTRIES %FULL OFLO FAIL  RECORD   RECORD   UPLOAD
    1114 Active  8312    84    No   No    03-12-05 04-06-01 04-05-30
                                          11:23:56 15:59:06 14:02:22 
    
    1116 Standby 693     7     No   No    03-12-05 04-06-01 04-05-30
                                          11:24:12 14:00:06 14:02:13
    

    If the number shown in the ENTRIES field for the standby MASP (shown with the entry Standby in the ROLE field) is 0, continue the procedure with 7.

    If the number shown in the ENTRIES field for the standby MASP is greater than 0, these entries must be copied to the FTA area of the fixed disk. To copy these entries, continue the procedure with 6.

  6. Copy the security log entries on the standby MASP to the FTA area on the fixed disk with the copy-seculog command.

    For this example, enter the copy-seculog:slog=stb command. This is an example of the message that should appear.

    
    rlghncxa03w 06-10-01 15:59:06 GMT EAGLE5 36.0.0
    Security log on E5TDM 1116 copied to file 961004s.log on E5TDM 1114
    
  7. Display the terminal configuration in the database with the rtrv-trm command.

    The SEAS terminals are shown in the output with the entry SEAS in the TYPE field. This is an example of the possible output. In this example, the SEAS terminals are terminals 18 and 27. If no SEAS terminals are shown in the rtrv-trm command output, continue the procedure with 10.

    rlghncxa03w 10-07-01 16:02:08 GMT EAGLE5 42.0.0
    TRM  TYPE     COMM        FC    TMOUT MXINV DURAL
    1    VT320    9600-7-E-1  SW    30    5     99:59:59
    2    KSR      9600-7-E-1  HW    30    5     INDEF
    3    PRINTER  4800-7-E-1  HW    30    0     00:00:00
    4    VT320    2400-7-E-1  BOTH  30    5     00:30:00
    5    VT320    9600-7-O-1  NONE  30    5     00:00:30
    6    VT320    9600-7-O-1  NONE  30    5     00:00:30
    7    PRINTER  9600-7-N-2  HW    30    5     00:30:00
    8    KSR     19200-7-E-2  BOTH  30    5     00:30:00
    9    VT320    9600-7-O-1  NONE  30    5     00:00:30
    10   VT320    9600-7-E-1  HW    30    5     00:30:00
    11   VT320    4800-7-E-1  HW    30    5     00:30:00
    12   PRINTER  9600-7-E-1  HW    30    4     00:30:00
    13   VT320    9600-7-O-1  NONE  30    5     00:30:00
    14   VT320    9600-7-E-2  SW    30    8     00:30:00
    15   VT320    9600-7-N-2  HW    30    5     00:30:00
    16   VT320    9600-7-E-2  BOTH  30    3     00:30:00
    
    TRM  TYPE      LOC              TMOUT MXINV DURAL      SECURE
    17   TELNET    1201             60    5     00:30:00   yes
    18   SEAS      1201             60    5     00:30:00   yes
    19   TELNET    1201             60    5     00:30:00   yes
    20   TELNET    1201             60    5     00:30:00   yes
    21   TELNET    1201             60    5     00:30:00   yes
    22   TELNET    1201             60    5     00:30:00   yes
    23   TELNET    1201             60    5     00:30:00   yes
    24   TELNET    1201             60    5     00:30:00   yes
    25   TELNET    1203             60    5     00:30:00   yes
    26   TELNET    1203             60    5     00:30:00   yes
    27   SEAS      1203             60    5     00:30:00   yes
    28   TELNET    1203             60    5     00:30:00   yes
    29   TELNET    1203             60    5     00:30:00   yes
    30   TELNET    1203             60    5     00:30:00   yes
    31   TELNET    1203             60    5     00:30:00   yes
    32   TELNET    1203             60    5     00:30:00   yes
    33   TELNET    1205             60    5     00:30:00   yes
    34   TELNET    1205             60    5     00:30:00   yes
    35   TELNET    1205             60    5     00:30:00   yes
    36   TELNET    1205             60    5     00:30:00   yes
    37   TELNET    1205             60    5     00:30:00   yes
    38   TELNET    1205             60    5     00:30:00   yes
    39   TELNET    1205             60    5     00:30:00   yes
    40   TELNET    1205             60    5     00:30:00   yes
    

    Note:

    The rtrv-trm command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-trm command, see the rtrv-trm command description in Commands User's Guide.

    If SEAS terminals are not shown in the rtrv-trm output, continue the procedure with 10.

    If SEAS terminals are shown in the rtrv-trm output, continue the procedure with 8.

  8. Display the status of the SEAS terminals with the rept-stat-trm command with the terminal number of the SEAS terminals.

    For this example, enter these commands.

    rept-stat-trm:trm=18

    This is an example of the possible output.

    
    rlghncxa03w 06-10-01 15:08:45 GMT EAGLE5 36.0.0
    TRM   PST           SST           AST
    18    IS-NR         Active        -----
    Command Completed.
    

    rept-stat-trm:trm=27

    This is an example of the possible output.

    
    rlghncxa03w 06-10-01 15:08:45 GMT EAGLE5 36.0.0
    TRM   PST           SST           AST
    27    IS-NR         Active        -----
    Command Completed.
    
  9. Place the SEAS terminals out of service using the rmv-trm command with the number of the terminal displayed in 8 whose state is not OOS-MT-DSBLD.

    The force=yes parameter must be used when placing the last SEAS terminal out of service.

    For this example, enter these commands.

    rmv-trm:trm=18

    rmv-trm:trm=27:force=yes

    If the status of the SEAS terminals shown in the PST field in 8 is OOS-MT-DSBLD (out-of-service maintenance disabled), the terminal is already out of service and the rmv-trm command does not need to be executed for that terminal.

    This message should appear when each of these commands have successfully completed.

    
    rlghncxa03w 06-10-01 15:08:45 GMT EAGLE5 36.0.0
    Inhibit message sent to terminal
    
    rlghncxa03w 06-10-01 15:08:45 GMT EAGLE5 36.0.0
    Command Completed.
    
  10. Enter the copy-disk command along with the card location of the standby E5-TDM (shown by the indicator STDBY in the rept-stat-db command output in 1) that the data is being copied to.

    If the standby fixed disk contains system data, the force=yes parameter must be specified with the copy-disk command. If you do not wish to format the standby fixed disk before copying, specify the format=no parameter with the copy-disk command.

    For this example, enter this command.

    copy-disk:dloc=1114:sloc=1116:force=yes:format=yes

    In this example, the standby fixed disk contains EAGLE data and will be formatted before any data is copied to the standby fixed disk.

    Note:

    The performance time required to copy a fixed disk to another fixed disk varies depending on database size and system activity. This operation should typically take no longer than 2.5 hours. If you are not performing the low-level format (format=no), the operation should take no longer than 1 hour. If the copy-disk operation exceeds 3 hours, contact My Oracle Support for assistance. Refer to My Oracle Support (MOS) for the contact information. If the copy-disk operation without the low-level format exceeds 1.5 hours, contact My Oracle Support.

    warning:

    Failure of the copy-disk command may result in corrupted E5-TDMs. If you experience a copy-disk command failure, contact the My Oracle Support for assistance. Refer to My Oracle Support (MOS) for the contact information.

    When the command has been executed and completed, these messages should appear.

    
        rlghncxa03w 06-10-01 10:22:05 GMT EAGLE5 36.0.0
        copy-disk:sloc=1116:dloc=1114:force=yes
        Command entered at terminal #3.
    ;
    
        rlghncxa03w 06-10-01 10:22:06 GMT EAGLE5 36.0.0
        Copy-disk (fixed): from active (1116) to standby (1114) started.
        Extended processing required, please wait.
    ;
    
        rlghncxa03w 06-10-01 10:22:08 GMT EAGLE5 36.0.0
        Copy-disk (fixed): format of standby disk started
    ;
    
        rlghncxa03w 06-10-01 10:27:08 GMT EAGLE5 36.0.0
        Copy-disk (fixed): format in progress
    ;
        rlghncxa03w 06-10-01 10:32:08 GMT EAGLE5 36.0.0
        Copy-disk (fixed): format in progress
    ;
    
        rlghncxa03w 06-10-01 11:07:05 GMT EAGLE5 36.0.0
        Copy-disk (fixed): format of standby disk completed
    ;
    
        rlghncxa03w 06-10-01 11:07:06 GMT EAGLE5 36.0.0
        Copy-disk (fixed): copying to standby disk started
    ;
    
        rlghncxa03w 06-10-01 11:12:06 GMT EAGLE5 36.0.0
        Copy-disk (fixed): copy in progress
    ;
    
        rlghncxa03w 06-10-01 11:27:10 GMT EAGLE5 36.0.0
        Copy-disk (fixed): from active (1116) to standby (1114) completed.
        Measurements collection may be turned on now if desired.
    

    If the format=no parameter was specified in this example, these messages should appear when the copy-disk command has successfully completed.

    copy-disk:dloc=1114:sloc=1116:force=yes:format=no

    
        rlghncxa03w 06-10-01 10:22:06 GMT EAGLE5 36.0.0
        Copy-disk (fixed): from active (1116) to standby (1114) started.
        Extended processing required, please wait.
    ;
    
        rlghncxa03w 06-10-01 11:07:08 GMT EAGLE5 36.0.0
        Copy-disk (fixed): copying to standby disk started
    ;
    
        rlghncxa03w 06-10-01 11:12:06 GMT EAGLE5 36.0.0
        Copy-disk (fixed): copy in progress
    ;
    
        rlghncxa03w 06-10-01 11:17:06 GMT EAGLE5 36.0.0
        Copy-disk (fixed): copy in progress
    ;
    
        rlghncxa03w 06-10-01 11:22:06 GMT EAGLE5 36.0.0
        Copy-disk (fixed): copy in progress
    ;
    
        rlghncxa03w 06-10-01 11:27:08 GMT EAGLE5 36.0.0
        Copy-disk (fixed): from active (1116) to standby (1114) completed.
        Measurements collection may be turned on now if desired.
    

    The standby MASP is rebooted to load the data when the command completes successfully.

    Note:

    While this command is executing, commands that affect the database configuration cannot be executed. Any attempt to execute such a command will be rejected.
    • If measurement collection was turned off in 4, continue the procedure with 11.
    • If measurement collection was not turned off in 4, continue the procedure with 12.
  11. Turn measurement collection on using the chg-meas:collect=on command.

    This message should appear.

    
    rlghncxa03w 06-10-01 16:12:50 GMT  EAGLE5 36.0.0
    CHG-MEAS: MASP A - COMPLTD
    
  12. Verify that the databases of both MASPs are coherent using the rept-stat-db command.

    This is an example of the possible output.

    
    rlghncxa03w 06-10-01 16:07:48 GMT  EAGLE5 36.0.0
    DATABASE STATUS: >> OK <<
            E5TDM 1114 ( STDBY)                 E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP  Y       95 04-06-01 05:53:36 GMT  Y       95 04-06-01 05:53:36 GMT
    FD CRNT  Y      105                        Y      105     
             E5MDAL 1117
             - --------
    RD BKUP  -    -         -        -
    

    If E5-based control cards are installed in the EAGLE, this is an example of the possible output.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> OK <<
            E5TDM 1114 ( STDBY )                 E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP Y        95 09-02-19 10:19:18 GMT  Y       95 09-02-19 10:19:18 GMT
    FD CRNT Y       105                        Y      105
            E5MCAP 1113                         E5MCAP 1115
            - --------                        - --------
    RD BKUP -    -         -        -         -    -         -        -
    USB BKP -    -         -        -         -    -         -        -
    

    If SEAS terminals are shown in the rtrv-trm command output in 7, continue the procedure with 13. Otherwise this procedure is completed.

  13. Put the SEAS terminals back into service using the rst-trm command with the number of the terminals specified in 9.

    For this example, enter these commands.

    rst-trm:trm=18

    rst-trm:trm=27

    This message should appear when each command has successfully completed.

    
    rlghncxa03w 06-10-01 15:08:45 GMT EAGLE5 36.0.0
    Allow message sent to terminal
    
    rlghncxa03w 06-10-01 15:08:45 GMT EAGLE5 36.0.0
    Command Completed.
    

Figure 2-11 Copying the Database from the Active to the Standby Fixed Disk



Sheet 1 of 3



Sheet 2 of 3



Sheet 3 of 3

2.8 Backing Up System Data to the Removable Media

This section details the procedure used to make a backup copy of the system data in addition to the database.

The term “database” refers to all data that can be administered by the user, including shelves, cards, links, routes, global title translation tables, and gateway screening tables. The term “system data” refers to data that cannot be administered by the user, including maintenance software modules and generic program loads (GPLs).

  1. Perform Making a Backup of the Database to the Removable Media to make a backup of the database to the removable cartridge or removable media. Perform this procedure without performing the last two steps (removing the media) and labeling the media. After the backup of the database has been made, continue the procedure with 2.
  2. Make a backup copy of the GPLs on the fixed disk of the active E5-TDM to the removable media using the copy-gpl command. Perform the following substep.
    1. If the removable media was used to make the backup of the database, the GPLs are copied from the active E5-TDM to the removable media on the active MASP. For this example, enter this command.

      copy-gpl:sloc=1116:dloc=1115:ddrv=remove

      During command execution, these messages should appear.

      
          rlghncxa03w 09-03-01 14:50:46 GMT EAGLE5 40.1.0
          COPY-GPL: MASP B - COPY STARTS ON ACTIVE MASP
      ;
      
          rlghncxa03w 09-03-01 14:50:46 GMT EAGLE5 40.1.0
          COPY GPL: MASP B - COPY TO REMOVABLE DRIVE COMPLETE
      
  3. Verify the GPLs on the removable media with the rtrv-gpl command.

    This is an example of the possible output.

    
        tekelecstp 18-01-18 21:23:11 EST  EAGLE 46.5.1.5.0-73.10.0
        rtrv-gpl
        Command entered at terminal #18.
    ;
    
    Command Accepted - Processing
        tekelecstp 18-01-18 21:23:11 EST  EAGLE 46.5.1.5.0-73.10.0
        GPL Auditing  ON
    
        GPL       CARD  RELEASE      APPROVED         TRIAL        REMOVE TRIAL
        OAMHC     1114  143-010-000  143-010-000 ALM  -----------  -----------
        OAMHC     1116  143-010-000  143-010-000 ALM  -----------  -----------
        OAMHC     1115  -----------  -----------      -----------  -----------
        OAMHC69   1114  143-010-000  143-010-000 ALM  -----------  -----------
        OAMHC69   1116  143-010-000  143-010-000 ALM  -----------  -----------
        OAMHC69   1115  -----------  -----------      -----------  -----------
        IPSG32    1114  143-010-000  143-010-000      143-010-000  -----------
        IPSG32    1116  143-010-000  143-010-000      143-010-000  -----------
        IPSG32    1115  -----------  -----------      -----------  -----------
        BLMCAP    1114  143-010-000  143-010-000      143-010-000  -----------
        BLMCAP    1116  143-010-000  143-010-000      143-010-000  -----------
        BLMCAP    1115  -----------  -----------      -----------  -----------
        HIPR2     1114  143-010-000  143-010-000      143-010-000  -----------
        HIPR2     1116  143-010-000  143-010-000      143-010-000  -----------
        HIPR2     1115  -----------  -----------      -----------  -----------
        SFAPP     1114  143-010-000  143-010-000 ALM  143-010-000  -----------
        SFAPP     1116  143-010-000  143-010-000 ALM  143-010-000  -----------
        SFAPP     1115  -----------  -----------      -----------  -----------
        SS7HC     1114  143-010-000  143-010-000      143-010-000  -----------
        SS7HC     1116  143-010-000  143-010-000      143-010-000  -----------
        SS7HC     1115  -----------  -----------      -----------  -----------
        SCCPHC    1114  143-010-000  143-010-000      143-010-000  -----------
        SCCPHC    1116  143-010-000  143-010-000      143-010-000  -----------
        SCCPHC    1115  -----------  -----------      -----------  -----------
        ERTHC     1114  143-010-000  143-010-000      143-010-000  -----------
        ERTHC     1116  143-010-000  143-010-000      143-010-000  -----------
        ERTHC     1115  -----------  -----------      -----------  -----------
        IPSHC     1114  143-010-000  143-010-000      143-010-000  -----------
        IPSHC     1116  143-010-000  143-010-000      143-010-000  -----------
        IPSHC     1115  -----------  -----------      -----------  -----------
        ATMHC     1114  143-010-000  143-010-000      143-010-000  -----------
        ATMHC     1116  143-010-000  143-010-000      143-010-000  -----------
        ATMHC     1115  -----------  -----------      -----------  -----------
        IPSG      1114  143-010-000  143-010-000      143-010-000  -----------
        IPSG      1116  143-010-000  143-010-000      143-010-000  -----------
        IPSG      1115  -----------  -----------      -----------  -----------
        PKTGHC    1114  143-010-000  143-010-000      -----------  -----------
        PKTGHC    1116  143-010-000  143-010-000      -----------  -----------
        PKTGHC    1115  -----------  -----------      -----------  -----------
        BLIXP     1114  143-010-000  143-010-000      143-010-000  -----------
        BLIXP     1116  143-010-000  143-010-000      143-010-000  -----------
        BLIXP     1115  -----------  -----------      -----------  -----------
        MCPHC     1114  143-010-000  143-010-000      143-010-000  -----------
        MCPHC     1116  143-010-000  143-010-000      143-010-000  -----------
        MCPHC     1115  -----------  -----------      -----------  -----------
        SIPHC     1114  143-010-000  143-010-000      143-010-000  -----------
        SIPHC     1116  143-010-000  143-010-000      143-010-000  -----------
        SIPHC     1115  -----------  -----------      -----------  -----------
        DEIRHC    1114  143-010-000  143-010-000      143-010-000  -----------
        DEIRHC    1116  143-010-000  143-010-000      143-010-000  -----------
        DEIRHC    1115  -----------  -----------      -----------  -----------
        ENUMHC    1114  143-010-000  143-010-000      143-010-000  -----------
        ENUMHC    1116  143-010-000  143-010-000      143-010-000  -----------
        ENUMHC    1115  -----------  -----------      -----------  -----------
        PKTG64    1114  143-010-000  143-010-000      -----------  -----------
        PKTG64    1116  143-010-000  143-010-000      -----------  -----------
        PKTG64    1115  -----------  -----------      -----------  -----------
        BLDC64    1114  143-010-000  -----------      143-010-000  -----------
        BLDC64    1116  143-010-000  000-000-000 ALM  143-010-000  -----------
        BLDC64    1115  -----------  -----------      -----------  -----------
        SCCP64    1114  143-010-000  143-010-000      143-010-000  -----------
        SCCP64    1116  143-010-000  143-010-000      143-010-000  -----------
        SCCP64    1115  -----------  -----------      -----------  -----------
        BLSLC32   1114  143-010-000  143-010-000      143-010-000  -----------
        BLSLC32   1116  143-010-000  143-010-000      143-010-000  -----------
        BLSLC32   1115  -----------  -----------      -----------  -----------
        BLSLC64   1114  143-010-000  143-010-000      143-010-000  -----------
        BLSLC64   1116  143-010-000  143-010-000      143-010-000  -----------
        BLSLC64   1115  -----------  -----------      -----------  -----------
        SIP64     1114  143-010-000  143-010-000      143-010-000  -----------
        SIP64     1116  143-010-000  143-010-000      143-010-000  -----------
        SIP64     1115  -----------  -----------      -----------  -----------
        DEIR64    1114  143-010-000  143-010-000      143-010-000  -----------
        DEIR64    1116  143-010-000  143-010-000      143-010-000  -----------
        DEIR64    1115  -----------  -----------      -----------  -----------
        ENUM64    1114  143-010-000  143-010-000      143-010-000  -----------
        ENUM64    1116  143-010-000  143-010-000      143-010-000  -----------
        ENUM64    1115  -----------  -----------      -----------  -----------
        BLDC32    1114  143-010-000  -----------      143-010-000  -----------
        BLDC32    1116  143-010-000  -----------      143-010-000  -----------
        BLDC32    1115  -----------  -----------      -----------  -----------
        MCPHC69   1114  143-010-000  143-010-000      143-010-000  -----------
        MCPHC69   1116  143-010-000  143-010-000      143-010-000  -----------
        MCPHC69   1115  -----------  -----------      -----------  -----------
        IPSHC69   1114  143-010-000  143-010-000      143-010-000  -----------
        IPSHC69   1116  143-010-000  143-010-000      143-010-000  -----------
        IPSHC69   1115  -----------  -----------      -----------  -----------
        BLSL932   1114  143-010-000  143-010-000      143-010-000  -----------
        BLSL932   1116  143-010-000  143-010-000      143-010-000  -----------
        BLSL932   1115  -----------  -----------      -----------  -----------
    
    ;
    Command Executed
    

    This example shows GPLs on an EAGLE that has E5-based control cards installed. The GPLs were copied to the removable media in both MASPs. The USB credit card flash media is not inserted into the USB credit card flash media drive in the E5-MCAP card of the active MASP (card location 1115). If the GPLs were copied only to the removable media on the active MASP, the removable media is not inserted in the standby MASP and the GPL version number for the standby MASP is not displayed.

  4. Perform the following action:

    Remove the removable media from the removable media drives on the MASPs. For more information on removing the removable media from the removable media drives, refer to Removable USB Drive.

  5. Label the removable media, 1 through 4 if the backup is performed weekly or monthly, A through D if the backup is performed quarterly.

    For more information on labeling the removable media, see Chapter 2, “Preventive Maintenance,” in Maintenance Guide.

2.9 Restoring System Data from a Removable Media

This section presents the procedure for restoring system data from a system backup removable media that was made by performing Backing Up System Data to the Removable Media.

Caution:

Using the action=restore parameter with the chg-db command is an emergency recovery procedure, and requires the init-sys command to download the restored database to all the cards in the EAGLE.

Caution:

If the restore device state option is on, shown by the ON value for the RSTRDEV field in the rtrv-stpopts command output, the state of the cards, SS7 signaling links, TCP/IP data links, and terminals before the chg-db:action=restore and init-sys commands are performed will not be maintained after these commands are performed. The persistent device state table becomes obsolete and is disabled. UIM 1257 is generated.

rlghncxa03w 09-10-01 16:07:48 GMT  EAGLE5 41.1.0 
1234.1257    SYSTEM       INFO  DB Restore has cleared and disabled PDS
  1. Perform Restoring the Database from the Removable Media to restore the database from the removable media. If the database is being restored from a removable media, do not remove the removable media. After the database has been restored, continue the procedure with the next step.
  2. Copy the GPLs from the removable media to the standby E5-TDM using the copy-gpl command. Perform the following substep.
    1. If the removable media was used to restore the database, the GPLs are copied from the removable media on the active MASP to the standby E5-TDM. For this example, enter this command.

      copy-gpl:sloc=1115:dloc=1114:sdrv=remove

      During command execution, these messages should appear.

      
          rlghncxa03w 09-10-01 14:50:46 GMT EAGLE5 41.1.0
          COPY-GPL: MASP A - COPY STARTS ON REMOVABLE DRIVE
      ;
      
          rlghncxa03w 09-10-01 14:50:46 GMT EAGLE5 41.1.0
          COPY GPL: MASP A - COPY TO STANDBY MASP COMPLETE
      
  3. Verify the GPLs on the standby E5-TDM and removable media with the rtrv-gpl command.

    This is an example of the possible output:

    
    rlghncxa03w 8-12-13 07:01:08 GMT EAGLE5 45.0.0
    GPL Auditing  ON
    
    GPL       CARD  RELEASE      APPROVED         TRIAL        REMOVE TRIAL
    SIPHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    SIPHC     1116  134-003-000  134-002-000      134-002-000  134-003-000
    SIPHC     1115  -----------  -----------      -----------  -----------
    GLS       1114  134-003-000  134-003-000      134-002-000  134-003-000
    GLS       1116  134-003-000  134-002-000      134-002-000  134-003-000
    GLS       1115  -----------  -----------      -----------  -----------
    CDU       1114  163-001-000  163-001-000      163-000-000  163-001-000
    CDU       1116  163-001-000  163-000-000      163-000-000  163-001-000
    CDU       1115  -----------  -----------      -----------  -----------
    IMT       1114  134-003-000  134-003-000      134-002-000  134-003-000
    IMT       1116  134-003-000  134-002-000      134-002-000  134-003-000
    IMT       1115  -----------  -----------      -----------  -----------
    ATMANSI   1114  134-003-000  134-003-000      134-002-000  134-003-000
    ATMANSI   1116  134-003-000  134-002-000      134-002-000  134-003-000
    ATMANSI   1115  -----------  -----------      -----------  -----------
    BPHCAP    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BPHCAP    1116  134-003-000  134-002-000      134-002-000  134-003-000
    BPHCAP    1115  -----------  -----------      -----------  -----------
    BPDCM     1114  134-003-000  134-003-000      134-002-000  134-003-000
    BPDCM     1116  134-003-000  134-002-000      134-002-000  134-003-000
    BPDCM     1115  -----------  -----------      -----------  -----------
    BLMCAP    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLMCAP    1116  134-003-000  134-002-000      134-002-000  134-003-000
    BLMCAP    1115  -----------  -----------      -----------  -----------
    OAMHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    OAMHC     1116  134-003-000  134-002-000      134-002-000  134-003-000
    OAMHC     1115  -----------  -----------      -----------  -----------
    HIPR2     1114  134-003-000  134-003-000      134-002-000  134-003-000
    HIPR2     1116  134-003-000  134-002-000      134-002-000  134-003-000
    HIPR2     1115  -----------  -----------      -----------  -----------
    IPLIM     1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPLIM     1116  134-003-000  134-002-000      134-002-000  134-003-000
    IPLIM     1115  -----------  -----------      -----------  -----------
    IPLIMI    1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPLIMI    1116  134-003-000  134-002-000      134-002-000  134-003-000
    IPLIMI    1115  -----------  -----------      -----------  -----------
    SS7IPGW   1114  134-003-000  134-003-000      134-002-000  134-003-000
    SS7IPGW   1116  134-003-000  134-002-000      134-002-000  134-003-000
    SS7IPGW   1115  -----------  -----------      -----------  -----------
    VSCCP     1114  134-003-000  134-003-000      134-002-000  134-003-000
    VSCCP     1116  134-003-000  134-002-000      134-002-000  134-003-000
    VSCCP     1115  -----------  -----------      -----------  -----------
    ATMITU    1114  134-003-000  134-003-000      134-002-000  134-003-000
    ATMITU    1116  134-003-000  134-002-000      134-002-000  134-003-000
    ATMITU    1115  -----------  -----------      -----------  -----------
    VCDU      1114  163-001-000  163-001-000      163-000-000  163-001-000
    VCDU      1116  163-001-000  163-000-000      163-000-000  163-001-000
    VCDU      1115  -----------  -----------      -----------  -----------
    BPMPL     1114  134-003-000  134-003-000      134-002-000  134-003-000
    BPMPL     1116  134-003-000  134-002-000      134-002-000  134-003-000
    BPMPL     1115  -----------  -----------      -----------  -----------
    SS7ML     1114  134-003-000  134-003-000      134-002-000  134-003-000
    SS7ML     1116  134-003-000  134-002-000      134-002-000  134-003-000
    SS7ML     1115  -----------  -----------      -----------  -----------
    BPHMUX    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BPHMUX    1116  134-003-000  134-002-000      134-002-000  134-003-000
    BPHMUX    1115  -----------  -----------      -----------  -----------
    IPGWI     1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPGWI     1116  134-003-000  134-002-000      134-002-000  134-003-000
    IPGWI     1115  -----------  -----------      -----------  -----------
    IPS       1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPS       1116  134-003-000  134-002-000      134-002-000  134-003-000
    IPS       1115  -----------  -----------      -----------  -----------
    BPDCM2    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BPDCM2    1116  134-003-000  134-002-000      134-002-000  134-003-000
    BPDCM2    1115  -----------  -----------      -----------  -----------
    EROUTE    1114  134-003-000  134-003-000      134-002-000  134-003-000
    EROUTE    1116  134-003-000  134-002-000      134-002-000  134-003-000
    EROUTE    1115  -----------  ----------      -----------  -----------
    BPMPLT    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BPMPLT    1116  134-003-000  134-002-000      134-002-000  134-003-000
    BPMPLT    1115  -----------  -----------      -----------  -----------
    MCP       1114  134-003-000  134-003-000      134-002-000  134-003-000
    MCP       1116  134-003-000  134-002-000      134-002-000  134-003-000
    MCP       1115  -----------  -----------      -----------  -----------
    BPHCAPT   1114  134-003-000  134-003-000      134-002-000  134-003-000
    BPHCAPT   1116  134-003-000  134-002-000      134-002-000  134-003-000
    BPHCAPT   1115  -----------  -----------      -----------  -----------
    SS7HC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    SS7HC     1116  134-003-000  134-002-000      134-002-000  134-003-000
    SS7HC     1115  -----------  -----------      -----------  -----------
    BLBIOS    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLBIOS    1116  134-003-000  134-002-000      134-002-000  134-003-000
    BLBIOS    1115  -----------  -----------      -----------  -----------
    BLCPLD    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLCPLD    1116  134-003-000  134-002-000      134-002-000  134-003-000
    BLCPLD    1115  -----------  -----------      -----------  -----------
    GLSHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    GLSHC     1116  134-003-000  134-002-000      134-002-000  134-003-000
    GLSHC     1115  -----------  -----------      -----------  -----------
    IMTPCI    1114  134-003-000  134-003-000      134-002-000  134-003-000
    IMTPCI    1116  134-003-000  134-002-000      134-002-000  134-003-000
    IMTPCI    1115  -----------  -----------      -----------  -----------
    PLDPMC1   1114  134-003-000  134-003-000      134-002-000  134-003-000
    PLDPMC1   1116  134-003-000  134-002-000      134-002-000  134-003-000
    PLDPMC1   1115  -----------  -----------      -----------  -----------
    IPLHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPLHC     1116  134-003-000  134-002-000      134-002-000  134-003-000
    IPLHC     1115  -----------  -----------      -----------  -----------
    IPGHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPGHC     1116  134-003-000  134-002-000      134-002-000  134-003-000
    IPGHC     1115  -----------  -----------      -----------  -----------
    SS7EPM    1114  134-003-000  134-003-000      134-002-000  134-003-000
    SS7EPM    1116  134-003-000  134-002-000      134-002-000  134-003-000
    SS7EPM    1115  -----------  -----------      -----------  -----------
    BLBEPM    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLBEPM    1116  134-003-000  134-002-000      134-002-000  134-003-000
    BLBEPM    1115  -----------  -----------      -----------  -----------
    BLVXW6    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLVXW6    1116  134-003-000  134-002-000      134-002-000  134-003-000
    BLVXW6    1115  -----------  -----------      -----------  -----------
    BLDIAG6   1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLDIAG6   1116  134-003-000  134-002-000      134-002-000  134-003-000
    BLDIAG6   1115  -----------  -----------      -----------  -----------
    SCCPHC    1114  134-003-000  134-003-000      134-002-000  134-003-000
    SCCPHC    1116  134-003-000  134-002-000      134-002-000  134-003-000
    SCCPHC    1115  -----------  -----------      -----------  -----------
    BLBSMG    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLBSMG    1116  134-003-000  134-002-000      134-002-000  134-003-000
    BLBSMG    1115  -----------  -----------      -----------  -----------
    ERTHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    ERTHC     1116  134-003-000  134-002-000      134-002-000  134-003-000
    ERTHC     1115  -----------  -----------      -----------  -----------
    IPSHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPSHC     1116  134-003-000  134-002-000      134-002-000  134-003-000
    IPSHC     1115  -----------  -----------      -----------  -----------
    ATMHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    ATMHC     1116  134-003-000  134-002-000      134-002-000  134-003-000
    ATMHC     1115  -----------  -----------      -----------  -----------
    IPSG      1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPSG      1116  134-003-000  134-002-000      134-002-000  134-003-000
    IPSG      1115  -----------  -----------      -----------  -----------
    BLROM1    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLROM1    1116  134-003-000  134-002-000      134-002-000  134-003-000
    BLROM1    1115  -----------  -----------      -----------  -----------
    BLIXP     1114  163-003-000  163-003-000      163-002-000  163-003-000
    BLIXP     1116  163-003-000  163-002-000      163-002-000  163-003-000
    BLIXP     1115  -----------  -----------      -----------  -----------
    

    This example shows GPLs on an EAGLE that has E5-based control cards installed. The GPLs were copied from the removable media in on the active MASP. The USB credit card flash media is not inserted into the USB credit card flash media drive in the E5-MCAP card of the active MASP (card location 1115).

  4. Enter the init-card command specifying the location of the E5-MCAP card making up active MASP.

    This step makes the standby MASP the active MASP. The MASP that was active is now the standby MASP.

    For this example, enter this command.

    init-card:loc=1115

    This message should appear.

    
    rlghncxa03w 09-10-01  11:11:28 GMT  EAGLE5 41.1.0
    Init Card command issued to card 1115
    
  5. Copy the GPLs from the removable media to the standby E5-TDM using the copy-gpl command. Perform the following substep:
    1. If the removable media was used to restore the database, the GPLs are copied from the removable media on on the active MASP to the standby E5-TDM. For this example, enter this command.

      copy-gpl:sloc=1113:dloc=1116:sdrv=remove

      During command execution, these messages should appear.

      
          rlghncxa03w 09-10-01 14:50:46 GMT EAGLE5 41.1.0
          COPY-GPL: MASP A - COPY STARTS ON REMOVABLE DRIVE
      ;
      
          rlghncxa03w 09-10-01 14:50:46 GMT EAGLE5 41.1.0
          COPY GPL: MASP A - COPY TO STANDBY MASP COMPLETE
      
  6. Verify the GPLs on the standby E5-TDM and the removable media with the rtrv-gpl command.

    This is an example of the possible output.

    
    rlghncxa03w 8-12-13 07:01:08 GMT EAGLE5 45.0.0
    GPL Auditing  ON
    
    GPL       CARD  RELEASE      APPROVED         TRIAL        REMOVE TRIAL
    SIPHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    SIPHC     1116  134-003-000  134-003-000      134-002-000  134-003-000
    SIPHC     1115  -----------  -----------      -----------  -----------
    GLS       1114  134-003-000  134-003-000      134-002-000  134-003-000
    GLS       1116  134-003-000  134-003-000      134-002-000  134-003-000
    GLS       1115  -----------  -----------      -----------  -----------
    CDU       1114  163-001-000  163-001-000      163-000-000  163-001-000
    CDU       1116  163-001-000  163-001-000      163-000-000  163-001-000
    CDU       1115  -----------  -----------      -----------  -----------
    IMT       1114  134-003-000  134-003-000      134-002-000  134-003-000
    IMT       1116  134-003-000  134-003-000      134-002-000  134-003-000
    IMT       1115  -----------  -----------      -----------  -----------
    ATMANSI   1114  134-003-000  134-003-000      134-002-000  134-003-000
    ATMANSI   1116  134-003-000  134-003-000      134-002-000  134-003-000
    ATMANSI   1115  -----------  -----------      -----------  -----------
    BPHCAP    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BPHCAP    1116  134-003-000  134-003-000      134-002-000  134-003-000
    BPHCAP    1115  -----------  -----------      -----------  -----------
    BPDCM     1114  134-003-000  134-003-000      134-002-000  134-003-000
    BPDCM     1116  134-003-000  134-003-000      134-002-000  134-003-000
    BPDCM     1115  -----------  -----------      -----------  -----------
    BLMCAP    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLMCAP    1116  134-003-000  134-003-000      134-002-000  134-003-000
    BLMCAP    1115  -----------  -----------      -----------  -----------
    OAMHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    OAMHC     1116  134-003-000  134-003-000      134-002-000  134-003-000
    OAMHC     1115  -----------  -----------      -----------  -----------
    HIPR2     1114  134-003-000  134-003-000      134-002-000  134-003-000
    HIPR2     1116  134-003-000  134-003-000      134-002-000  134-003-000
    HIPR2     1115  -----------  -----------      -----------  -----------
    IPLIM     1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPLIM     1116  134-003-000  134-003-000      134-002-000  134-003-000
    IPLIM     1115  -----------  -----------      -----------  -----------
    IPLIMI    1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPLIMI    1116  134-003-000  134-003-000      134-002-000  134-003-000
    IPLIMI    1115  -----------  -----------      -----------  -----------
    SS7IPGW   1114  134-003-000  134-003-000      134-002-000  134-003-000
    SS7IPGW   1116  134-003-000  134-003-000      134-002-000  134-003-000
    SS7IPGW   1115  -----------  -----------      -----------  -----------
    VSCCP     1114  134-003-000  134-003-000      134-002-000  134-003-000
    VSCCP     1116  134-003-000  134-003-000      134-002-000  134-003-000
    VSCCP     1115  -----------  -----------      -----------  -----------
    ATMITU    1114  134-003-000  134-003-000      134-002-000  134-003-000
    ATMITU    1116  134-003-000  134-003-000      134-002-000  134-003-000
    ATMITU    1115  -----------  -----------      -----------  -----------
    VCDU      1114  163-001-000  163-001-000      163-000-000  163-001-000
    VCDU      1116  163-001-000  163-001-000      163-000-000  163-001-000
    VCDU      1115  -----------  -----------      -----------  -----------
    BPMPL     1114  134-003-000  134-003-000      134-002-000  134-003-000
    BPMPL     1116  134-003-000  134-003-000      134-002-000  134-003-000
    BPMPL     1115  -----------  -----------      -----------  -----------
    SS7ML     1114  134-003-000  134-003-000      134-002-000  134-003-000
    SS7ML     1116  134-003-000  134-003-000      134-002-000  134-003-000
    SS7ML     1115  -----------  -----------      -----------  -----------
    BPHMUX    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BPHMUX    1116  134-003-000  134-003-000      134-002-000  134-003-000
    BPHMUX    1115  -----------  -----------      -----------  -----------
    IPGWI     1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPGWI     1116  134-003-000  134-003-000      134-002-000  134-003-000
    IPGWI     1115  -----------  -----------      -----------  -----------
    IPS       1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPS       1116  134-003-000  134-003-000      134-002-000  134-003-000
    IPS       1115  -----------  -----------      -----------  -----------
    BPDCM2    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BPDCM2    1116  134-003-000  134-003-000      134-002-000  134-003-000
    BPDCM2    1115  -----------  -----------      -----------  -----------
    EROUTE    1114  134-003-000  134-003-000      134-002-000  134-003-000
    EROUTE    1116  134-003-000  134-003-000      134-002-000  134-003-000
    EROUTE    1115  -----------  ----------      -----------  -----------
    BPMPLT    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BPMPLT    1116  134-003-000  134-003-000      134-002-000  134-003-000
    BPMPLT    1115  -----------  -----------      -----------  -----------
    MCP       1114  134-003-000  134-003-000      134-002-000  134-003-000
    MCP       1116  134-003-000  134-003-000      134-002-000  134-003-000
    MCP       1115  -----------  -----------      -----------  -----------
    BPHCAPT   1114  134-003-000  134-003-000      134-002-000  134-003-000
    BPHCAPT   1116  134-003-000  134-003-000      134-002-000  134-003-000
    BPHCAPT   1115  -----------  -----------      -----------  -----------
    SS7HC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    SS7HC     1116  134-003-000  134-003-000      134-002-000  134-003-000
    SS7HC     1115  -----------  -----------      -----------  -----------
    BLBIOS    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLBIOS    1116  134-003-000  134-003-000      134-002-000  134-003-000
    BLBIOS    1115  -----------  -----------      -----------  -----------
    BLCPLD    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLCPLD    1116  134-003-000  134-003-000      134-002-000  134-003-000
    BLCPLD    1115  -----------  -----------      -----------  -----------
    GLSHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    GLSHC     1116  134-003-000  134-003-000      134-002-000  134-003-000
    GLSHC     1115  -----------  -----------      -----------  -----------
    IMTPCI    1114  134-003-000  134-003-000      134-002-000  134-003-000
    IMTPCI    1116  134-003-000  134-003-000      134-002-000  134-003-000
    IMTPCI    1115  -----------  -----------      -----------  -----------
    PLDPMC1   1114  134-003-000  134-003-000      134-002-000  134-003-000
    PLDPMC1   1116  134-003-000  134-003-000      134-002-000  134-003-000
    PLDPMC1   1115  -----------  -----------      -----------  -----------
    IPLHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPLHC     1116  134-003-000  134-003-000      134-002-000  134-003-000
    IPLHC     1115  -----------  -----------      -----------  -----------
    IPGHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPGHC     1116  134-003-000  134-003-000      134-002-000  134-003-000
    IPGHC     1115  -----------  -----------      -----------  -----------
    SS7EPM    1114  134-003-000  134-003-000      134-002-000  134-003-000
    SS7EPM    1116  134-003-000  134-003-000      134-002-000  134-003-000
    SS7EPM    1115  -----------  -----------      -----------  -----------
    BLBEPM    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLBEPM    1116  134-003-000  134-003-000      134-002-000  134-003-000
    BLBEPM    1115  -----------  -----------      -----------  -----------
    BLVXW6    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLVXW6    1116  134-003-000  134-003-000      134-002-000  134-003-000
    BLVXW6    1115  -----------  -----------      -----------  -----------
    BLDIAG6   1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLDIAG6   1116  134-003-000  134-003-000      134-002-000  134-003-000
    BLDIAG6   1115  -----------  -----------      -----------  -----------
    SCCPHC    1114  134-003-000  134-003-000      134-002-000  134-003-000
    SCCPHC    1116  134-003-000  134-003-000      134-002-000  134-003-000
    SCCPHC    1115  -----------  -----------      -----------  -----------
    BLBSMG    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLBSMG    1116  134-003-000  134-003-000      134-002-000  134-003-000
    BLBSMG    1115  -----------  -----------      -----------  -----------
    ERTHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    ERTHC     1116  134-003-000  134-003-000      134-002-000  134-003-000
    ERTHC     1115  -----------  -----------      -----------  -----------
    IPSHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPSHC     1116  134-003-000  134-003-000      134-002-000  134-003-000
    IPSHC     1115  -----------  -----------      -----------  -----------
    ATMHC     1114  134-003-000  134-003-000      134-002-000  134-003-000
    ATMHC     1116  134-003-000  134-003-000      134-002-000  134-003-000
    ATMHC     1115  -----------  -----------      -----------  -----------
    IPSG      1114  134-003-000  134-003-000      134-002-000  134-003-000
    IPSG      1116  134-003-000  134-003-000      134-002-000  134-003-000
    IPSG      1115  -----------  -----------      -----------  -----------
    BLROM1    1114  134-003-000  134-003-000      134-002-000  134-003-000
    BLROM1    1116  134-003-000  134-003-000      134-002-000  134-003-000
    BLROM1    1115  -----------  -----------      -----------  -----------
    BLIXP     1114  163-003-000  163-003-000      163-002-000  163-003-000
    BLIXP     1116  163-003-000  163-003-000      163-002-000  163-003-000
    BLIXP     1115  -----------  -----------      -----------  -----------
    

    This example shows GPLs on an EAGLE that has E5-based control cards installed. The GPLs were copied from the removable media in on the active MASP.

    This procedure is finished.

Figure 2-12 Restoring System Data from a Removable Cartridge or Removable Media



Sheet 1 of 2



Sheet 2 of 2

2.10 Formatting the Fixed Disk of the Standby E5-TDM

Use this procedure to format the fixed disk of the standby E5-TDM using the format-disk command.

The format-disk command uses these parameters.

:type – The type of disk or media being formatted.

  • system – A removable media containing system data (GPLs and the database). To format removable media, perform Formatting Removable Media.
  • fixed – The fixed disk of the standby E5-TDM.

    Note:

    If a format-disk:type=fixed command failure causes the standby E5-TDM to boot continuously, insert a removable disk that has the same release as the active E5-TDM into the E5-MDAL. The standby E5-TDM can then boot off of the removable disk.

:loc – The location of the standby E5-TDM, either 1114 or 1116.

:low – Is a check of the disk or media being performed and any problems found on the disk or media being repaired, yes or no? The low=yes parameter performs a check of the disk or media and any problems that are found are repaired. As an E5-TDM, no data is destroyed during this operation. If the low=no parameter is specified, the check of the disk or media is not performed. The default value for this parameter is no.

:force – Format the disk if the disk contains system data, yes or no. The default value for this parameter is no.

Note:

Reduce extended execution time when specifying the force=yes option by also using the low=no option.

:prtngrp – Indicates which disk partition group is being formatted, the active partition group (prtngrp=active) or the inactive partition group (prtngrp=inactive). The default value for the prtngrp parameter is active. The prtngrp parameter can be specified only with the low=no parameter. Contact My Oracle Support (MOS) before using the prtngrp=inactive parameter.

The database in the current (FD CRNT) partition of the active MASP must be coherent. For more information on verifying the database, refer to Verifying the Database.

Measurement collection must be turned off before the format-disk command can be executed.

The standby fixed disk cannot be formatted if the security log on the standby fixed disk contains any entries that have not been copied to the FTA area of the fixed disk. This can be verified with the rept-stat-seculog command. If the security log on the standby fixed disk contains entries that have not been copied to the file transfer area of the fixed disk, copy these entries to the file transfer area using the copy-seculog command.

  1. Use the rept-stat-db command to verify that the database in the current (FDCRNT) partition of the active MASP is coherent .

    The following is an example of the possible output:

    
    rlghncxa03w 13-06-01 16:07:48 GMT  EAGLE5 45.0.0
    DATABASE STATUS: >> OK <<
            E5TDM 1114 ( STDBY )                 E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP Y        35 09-02-19 10:19:18 GMT  Y       35 09-02-19 10:19:18 GMT
    FD CRNT Y       106                        Y      106
            E5MCAP 1113                         E5MCAP 1115
            - --------                        - --------
    RD BKUP Y      106 09-02-15 16:09:53 GMT  Y      106 09-02-15 16:09:53 GMT 
    USB BKP -    -         -        -         Y       95 09-02-13 16:09:53 GMT 
    

    If the current database on the active MASP is not coherent, refer to Verifying the Database to resolve the database problem.

  2. Verify whether or not the Measurements Platform option is enabled (PLATFORMENABLE = on) using the rtrv-measopts command. If platformenable is ON, no further check is required for the format-disk command (as MCP will take care of measurement once platformenable is on). If PLATFORMENABLE is off, check COLLECT using rtrv-meas-sched command.

    This is an example of the possible output. The COLLECT field shows whether measurement collection is on or off. In this example, measurement collection is on.

    
    rlghncxa03w 06-10-01 12:22:55 GMT EAGLE5 36.0.0 
    COLLECT        =  on
    GTWYLSFLTR     =  both
    ---------------------
    SYSTOT-STP     =  off
    SYSTOT-TT      =  off
    COMP-LNKSET    =  off
    COMP-LINK      =  on
    GTWY-STP       =  on
    GTWY-LNKSET    =  on
    MTCD-STP       =  on
    MTCD-LINK      =  on
    MTCD-LNKSET    =  on
    

    Note:

    If measurement collection is off, skip 3 and go to 4.
  3. Turn measurement collection off using the chg-meas:collect=off command.

    Caution:

    Measurement collection must be turned off or the format-disk command cannot be executed. The chg-meas:collect=on command should not be executed while the format-disk command is in progress. If possible, do not turn off measurement collection at midnight since doing so can cause the loss of an entire day of measurements. For the period of time that measurement collection is turned off, those measurements will be lost.

    This message should appear.

    
    rlghncxa03w 06-10-01 16:12:50 GMT  EAGLE5 36.0.0
    CHG-MEAS: MASP A - COMPLTD
    
  4. Verify whether or not the Measurements Platform option is enabled (PLATFORMENABLE = on) using the rtrv-measopts command. If platformenable is ON, no further check is required for the format-disk command (as MCP will take care of measurement once platformenable is on). If PLATFORMENABLE is off, check to see if COLLECT is on using the rtrv-meas-sched command. If COLLECT is on, turn it off. If COLLECT is off, run the format-disk command, and turn it on.
    
    rlghncxa03w 06-10-01 16:02:05 GMT  EAGLE5 36.0.0
    PLATFORMENABLE   = on
    COLLECT15MIN     = off
    CLLIBASEDNAME    = off
    ----------------------
    SYSTOTSTP        = off
    SYSTOTTT         = off
    

    Note:

    The rtrv-measopts command output contains other fields that are not used by this procedure. To view all fields displayed by the rtrv-measopts command, see the rtrv-measopts command description in Commands User's Guide.

    Note:

    If 4 shows that the Measurements Platform is not enabled, go to 7.
  5. Use the rept-stat-meas command to display the status of MCPMs in the database .

    This is an example of the possible output.

    
    rlghncxa03w 09-02-01 16:43:42 GMT  EAGLE5 40.0.0
    
                          PST            SST       AST
    MEAS SS               IS-NR          Active    -----
            ALARM STATUS =   No Alarms
    
        CARD   VERSION         TYPE    PST           SST        AST
        2107 P 101-009-000     EDSM    IS-NR         Active     -----
           IP Link A                   IS-NR         Active     Available
        2108   101-009-000     EDSM    IS-NR         Active     -----
           IP Link A                   IS-NR         Active     Available
        2111   101-009-000     EDSM    IS-NR         Active     -----
           IP Link A                   IS-NR         Active     Available
      
        CARD 2107 ALARM STATUS = No Alarms
        CARD 2108 ALARM STATUS = No Alarms
        CARD 2111 ALARM STATUS = No Alarms
    
  6. Use the rmv-card command, specifying the card location of the MCPM, to place all MCPMs out of service .

    If the MCPM to be placed out of service is the last MCPM that is in service, the force=yes parameter must also be specified. For this example, enter these commands.

    rmv-card:loc=2107

    rmv-card:loc=2108

    rmv-card:loc=2111:force=yes

    When each of these commands have successfully completed, this message should appear.

    
    rlghncxa03w 06-10-01 09:12:36 GMT  EAGLE5 36.0.0
    Card has been inhibited.
    
  7. Verify that the security log on the standby MASP contains no entries that must be copied to the FTA area of the fixed disk with the rept-stat-seculog command.

    This is an example of the possible output.

    
    rlghncxa03w 06-10-01 15:59:06 GMT EAGLE5 36.0.0
                 -- SINCE LAST UPLOAD --  OLDEST   NEWEST   LAST
    LOC  ROLE    ENTRIES %FULL OFLO FAIL  RECORD   RECORD   UPLOAD
    1114 Active  8312    84    No   No    03-12-05 04-06-01 04-05-30
                                          11:23:56 15:59:06 14:02:22 
    
    1116 Standby 693     7     No   No    03-12-05 04-06-01 04-05-30
                                          11:24:12 14:00:06 14:02:13
    

    If the number shown in the ENTRIES field for the standby MASP (shown with the entry Standby in the ROLE field) is 0, go to step 9.

    If the number shown in the ENTRIES field for the standby MASP is greater than 0, these entries must be copied to the FTA area of the fixed disk. To copy these entries, go to step 8.

    For this example, go to 8.

  8. Copy the security log entries on the standby MASP to the FTA area on the fixed disk with the copy-seculog command.

    For this example, enter the copy-seculog:slog=stb command. This is an example of the message that should appear.

    
    rlghncxa03w 06-10-01 15:59:06 GMT EAGLE5 36.0.0
    Security log on E5TDM 1116 copied to file 961004s.log on E5TDM 1114
    
  9. Enter the format-disk command to format the fixed disk of the standby E5-TDM.

    For this example, the fixed disk of the standby E5-TDM contains system data and a checkof the fixed disk of the standby E5-TDM for problems is not performed.

    format-disk:type=fixed:force=yes:low=no:loc=1114

    Note:

    1. The force=yes parameter must be specified with the format-disk command if the fixed disk of the standby E5-TDM to be formatted contains system data. All data on the fixed disk of the standby E5-TDM will be lost.
    2. The low=no parameter specified in this command example does not allow a check of the fixed disk of the standby E5-TDM for problems to be performed. If you wish to perform a check of the fixed disk of the standby E5-TDM for problems, specify the low=yes parameter with the format-disk command. Because the default value for the low parameter is no, the low parameter can be omitted when entering the format-disk command if you do not wish to perform a check of the fixed disk of the standby E5-TDM for problems.
    3. If a format-disk:type=fixed command failure causes the standby E5-TDM to boot continuously, insert a removable disk that has the same release as the active E5-TDM into the E5-MDAL. The standby E5-TDM can then boot off of the removable disk.
    4. The optional parameter prtngrp parameter can be specified with this command. The prtngrp parameter indicates which disk partition group is being formatted, the active partition group (prtngrp=active) or the inactive partition group (prtngrp=inactive). The default value for the prtngrp parameter is active. The prtngrp parameter can be specified only with the low=no parameter. Contact the Customer Care Center before using the prtngrp=inactive parameter. Refer to My Oracle Support (MOS) for the contact information.

    Formatting the fixed disk of the standby E5-TDM can take from 14 minutes to 1 hour and 25 minutes to execute. It may take longer depending on other system activity that is in progress when this command is entered. When this command has successfully completed, these messages should appear.

    
        rlghncxa03w 06-10-01 09:44:08 GMT  EAGLE5 36.0.0
        format-disk:type=fixed:low=no:force=yes
        Command entered at terminal #3.
    ;
    
        rlghncxa03w 06-10-01 09:44:08 GMT  EAGLE5 36.0.0
        Format-disk of standby fixed disk started.
        Extended processing required, please wait.
    ;
    
        rlghncxa03w 06-10-01 09:44:08 GMT  EAGLE5 36.0.0
        Format-disk (fixed) format in progress.
    ;
    
        rlghncxa03w 06-10-01 09:44:08 GMT  EAGLE5 36.0.0
        Format-disk (fixed) format is complete.
    ;
    
        rlghncxa03w 06-10-01 09:44:08 GMT  EAGLE5 36.0.0
        Format-disk of standby fixed disk completed.
    

    To turn measurement collection on, go to step 10, otherwise, this procedure is finished.

    If measurement collection was not turned off in step 3, skip steps 10 and 11, and go to step 12.

  10. To turn measurement collection on, enter this command.

    chg-meas:collect=on

    This message should appear.

    
    rlghncxa03w 06-10-01 16:12:50 GMT  EAGLE5 36.0.0
    CHG-MEAS: MASP A - COMPLTD
    
  11. Verify that measurement collection is on using the rtrv-meas-sched command, shown by the COLLECT = on field in the output.

    This is an example of the possible output.

    
    rlghncxa03w 06-10-01 12:22:55 GMT EAGLE5 36.0.0 
    COLLECT        =  on
    GTWYLSFLTR     =  both
    ---------------------
    SYSTOT-STP     =  off
    SYSTOT-TT      =  off
    COMP-LNKSET    =  off
    COMP-LINK      =  on
    GTWY-STP       =  on
    GTWY-LNKSET    =  on
    MTCD-STP       =  on
    MTCD-LINK      =  on
    MTCD-LNKSET    =  on
    

    Note:

    MCPMs were not placed out of service in step 6, skip steps 12 and step 13. This procedure is finished.
  12. Place the MCPMs back into service using the rst-card specifying the location of each MCPM.

    For this example, enter these commands.

    rst-card:loc=2107

    rst-card:loc=2108

    rst-card:loc=2111

    When each of these commands have successfully completed, this message should appear.

    
    rlghncxa03w 06-10-01 21:20:37 GMT EAGLE5 36.0.0
    Card has been allowed.
    
  13. Display the status of the MCPMs in the database with the rept-stat-meas command.

    This is an example of the possible output.

    
    rlghncxa03w 09-02-01 16:43:42 GMT  EAGLE5 40.0.0
    
                          PST            SST       AST
    MEAS SS               IS-NR          Active    -----
            ALARM STATUS =   No Alarms
    
        CARD   VERSION         TYPE    PST           SST        AST
        2107 P 101-009-000     EDSM    IS-NR         Active     -----
           IP Link A                   IS-NR         Active     Available
        2108   101-009-000     EDSM    IS-NR         Active     -----
           IP Link A                   IS-NR         Active     Available
        2111   101-009-000     EDSM    IS-NR         Active     -----
           IP Link A                   IS-NR         Active     Available
      
        CARD 2107 ALARM STATUS = No Alarms
        CARD 2108 ALARM STATUS = No Alarms
        CARD 2111 ALARM STATUS = No Alarms
    

Figure 2-13 Formatting the Fixed Disk of the Standby E5-TDM



Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4

2.11 Formatting Removable Media

Use this procedure to prepare removable media for use on the EAGLE for holding system data or measurements data using the format-disk command. The format-disk command uses these parameters.

Note:

This procedure can be performed only if E5-based control cards are installed in the EAGLE. Refer to Maintenance and Administration Subsystem for more information about the control cards.
:type – The type of media that is being formatted.
  • system – Removable media containing system data (GPLs and the database)
  • meas – Removable media containing measurements data
  • fixed – The fixed disk of the standby E5-TDM. To format the fixed disk of the standby E5-TDM, perform Formatting the Fixed Disk of the Standby E5-TDM.

:loc – The location of the E5-MCAP card that contains the media that is being formatted, either 1113 or 1115.

:low – Is a check of the media being performed and any problems found on the media being repaired, yes or no? The low=yes parameter performs a check of the media and any problems that are found are repaired. No data is destroyed during this operation. If the low=no parameter is specified, the check of the media is not performed. The default value for this parameter is no.

:force – Format the media if the media contains system data, yes or no. The default value for this parameter is no.

:prtngrp – Indicates which disk partition group is being formatted, the active partition group (prtngrp=active) or the inactive partition group (prtngrp=inactive). The default value for the prtngrp parameter is active. The removable media does not contain an inactive partition group, so the prtngrp=inactive cannot be specified in this procedure.

Note:

Reduce extended execution time when specifying the force=yes option by also using the low=no option.

The database in the current (FD CRNT) partition of the active MASP must be coherent. If the current partition of the active MASP is not coherent, contact the customer care center. Refer to My Oracle Support (MOS) for the contact information.

Measurement collection must be turned off before the format-disk command can be executed.

  1. Check the removable media drives on each MASP for removable media.

    Perform one of these substeps.

    1. If there is no removable media in both removable media drives, insert the removable media that will be formatted into one of the removable media drives. Continue the procedure with 2. Refer to Removable USB Drive for more information about removing the removable media.
    2. If removable media is in the removable media drives, and the media in these drives will be formatted, continue the procedure with 2.
    3. If removable media is in the removable media drives, and the media in these drives will not be formatted, remove the removable media from the removable media drive that will be used to format the removable media. Insert the removable media that will be formatted into this drive. Continue the procedure with 2. Refer to Removable USB Drive for more information about removing and inserting the removable media.
  2. Verify that the database in the current (FDCRNT) partition of the active MASP is coherent using the rept-stat-db command.

    This is an example of the possible output.

    
    rlghncxa03w 09-03-01 16:07:48 GMT  EAGLE5 40.1.0
    DATABASE STATUS: >> OK <<
            E5TDM 1114 ( STDBY )                 E5TDM 1116 ( ACTV )
             C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
             - -------- ---------------------  - -------- ---------------------
    FD BKUP Y        35 09-02-19 10:19:18 GMT  Y       35 09-02-19 10:19:18 GMT
    FD CRNT Y       106                        Y      106
            E5MCAP 1113                         E5MCAP 1115
            - --------                        - --------
    RD BKUP Y      106 09-02-15 16:09:53 GMT  Y      106 09-02-15 16:09:53 GMT 
    USB BKP -    -         -        -         Y       95 09-02-13 16:09:53 GMT 
    

    If the current partition of the active MASP is not coherent, contact the customer care center. Refer to My Oracle Support (MOS) for the contact information.

    If the current partition of the active MASP is coherent and removable media will be formatted, continue the procedure with 4.

  3. Verify whether or nor the Measurements Platform option is enabled (PLATFORMENABLE = on) using the rtrv-measopts command.
    
    rlghncxa03w 09-03-01 16:02:05 GMT  EAGLE5 40.1.0
    PLATFORMENABLE   = on
    COLLECT15MIN     = off
    CLLIBASEDNAME    = off
    ----------------------
    SYSTOTSTP        = off
    SYSTOTTT         = off
    

    Note:

    The rtrv-measopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-measopts command, see the rtrv-measopts command description in Commands User's Guide.

    If the Measurements Platform is enabled, continue the procedure with 8

    If the Measurements Platform is not enabled, go to 4.

  4. Verify that measurement collection is on or off using the rtrv-meas-sched command.

    This is an example of the possible output. The COLLECT field shows whether measurement collection is on or off. In this example, measurement collection is on.

    
    rlghncxa03w 09-03-01 12:22:55 GMT EAGLE5 40.1.0 
    COLLECT        =  on
    GTWYLSFLTR     =  both
    ---------------------
    SYSTOT-STP     =  off
    SYSTOT-TT      =  off
    COMP-LNKSET    =  off
    COMP-LINK      =  on
    GTWY-STP       =  on
    GTWY-LNKSET    =  on
    MTCD-STP       =  on
    MTCD-LINK      =  on
    MTCD-LNKSET    =  on
    

    If measurement collection is off, continue the procedure with 3.

    If measurement collection is on, continue the procedure with 5.

  5. Turn measurement collection off using the chg-meas:collect=off command.

    Caution:

    Measurement collection must be turned off or the format-disk command cannot be executed. The chg-meas:collect=on command should not be executed while the format-disk command is in progress. If possible, do not turn off measurement collection at midnight since doing so can cause the loss of an entire day of measurements. For the period of time that measurement collection is turned off, those measurements will be lost.

    This message should appear.

    
    rlghncxa03w 09-03-01 16:12:50 GMT  EAGLE5 40.1.0
    CHG-MEAS: MASP A - COMPLTD
    
  6. Display the status of the MCPMs in the database with the rept-stat-meas command.

    This is an example of the possible output.

    
    rlghncxa03w 09-03-01 16:43:42 GMT  EAGLE5 40.1.0
    
                          PST            SST       AST
    MEAS SS               IS-NR          Active    -----
            ALARM STATUS =   No Alarms
    
        CARD   VERSION         TYPE    PST           SST        AST
        2107 P 101-009-000     EDSM    IS-NR         Active     -----
           IP Link A                   IS-NR         Active     Available
        2108   101-009-000     EDSM    IS-NR         Active     -----
           IP Link A                   IS-NR         Active     Available
        2111   101-009-000     EDSM    IS-NR         Active     -----
           IP Link A                   IS-NR         Active     Available
      
        CARD 2107 ALARM STATUS = No Alarms
        CARD 2108 ALARM STATUS = No Alarms
        CARD 2111 ALARM STATUS = No Alarms
    
  7. Place all the MCPMs out of service using the rmv-card command, specifying the card location of the MCPM.

    If the MCPM to be placed out of service is the last MCPM that is in service, the force=yes parameter must also be specified. For this example, enter these commands.

    rmv-card:loc=2107

    rmv-card:loc=2108

    rmv-card:loc=2111:force=yes

    When each of these commands have successfully completed, this message should appear.

    
    rlghncxa03w 09-03-01 09:12:36 GMT  EAGLE5 40.1.0
    Card has been inhibited.
    
  8. Format the removable media by performing one of these substeps.
    1. To format removable media for system data, for this example, enter this command.

      format-disk:type=system:loc=1113

      If a check of the media for problems will be performed, specify the low=yes parameter with the format-disk command. If the low=yes parameter is not specified, a check of the media for problems will not be performed.

      If the media contains system data, the force=yes parameter must be specified with the format-disk command. All data on the removable media will be lost.

      When this command has successfully completed, these messages should appear.

      
          rlghncxa03w 09-03-01 09:44:08 GMT  EAGLE5 40.1.0
          format-disk:type=system
          Command entered at terminal #3.
      ;
      
          rlghncxa03w 09-03-01 09:44:08 GMT  EAGLE5 40.1.0
          Format disk of system removable media started.
      ;
      
          rlghncxa03w 09-03-01 09:44:08 GMT  EAGLE5 40.1.0
          Format disk in progress.
      ;
          rlghncxa03w 09-03-01 09:44:08 GMT  EAGLE5 40.1.0
          Format disk in progress.
      ;
      
          rlghncxa03w 09-03-01 09:44:08 GMT  EAGLE5 40.1.0
          Format disk (removable media) format is complete.
      ;
      
          rlghncxa03w 09-03-01 09:44:08 GMT  EAGLE5 40.1.0
          Format disk of system removable media completed.
          Measurements collection may be turned on now if desired. 
      
    2. To format removable media for measurements data, for this example, enter this command.

      format-disk:type=meas:loc=1113

      If a low level format of the media will be performed, specify the low=yes parameter with the format-disk command. If the low=yes parameter is not specified, a low level format of the media will not be performed.

      If the media contains system data, the force=yes parameter must be specified with the format-disk command. All data on the removable media will be lost.

      When this command has successfully completed, these messages should appear.

      
          rlghncxa03w 09-03-01 09:44:08 GMT  EAGLE5 40.1.0
          format-disk:type=meas
          Command entered at terminal #3.
      ;
      
          rlghncxa03w 09-03-01 09:44:08 GMT  EAGLE5 40.1.0
          Format disk of measurements removable media started.
      ;
      
          rlghncxa03w 09-03-01 09:44:08 GMT  EAGLE5 40.1.0
          Format disk in progress.
      ;
      
          rlghncxa03w 09-03-01 09:44:08 GMT  EAGLE5 40.1.0
          Format disk in progress.
      ;
      
          rlghncxa03w 09-03-01 09:44:08 GMT  EAGLE5 40.1.0
          Format disk (removable media) format is complete.
      ;
      
          rlghncxa03w 09-03-01 09:44:08 GMT  EAGLE5 40.1.0
          Format disk of measurements removable media completed.
          Measurements collection may be turned on now if desired. 
      

    If 5 was not performed, continue the procedure with .

    If 5 was performed, continue the procedure with 9.

  9. Turn measurement collection on using the chg-meas:collect=on command.

    This message should appear.

    
    rlghncxa03w 09-03-01 16:12:50 GMT  EAGLE5 40.1.0
    CHG-MEAS: MASP A - COMPLTD
    
  10. Verify that measurement collection is on using the rtrv-meas-sched command, shown by the COLLECT = on field in the output.

    This is an example of the possible output.

    
    rlghncxa03w 09-03-01 12:22:55 GMT EAGLE5 40.1.0 
    COLLECT        =  on
    GTWYLSFLTR     =  both
    ---------------------
    SYSTOT-STP     =  off
    SYSTOT-TT      =  off
    COMP-LNKSET    =  off
    COMP-LINK      =  on
    GTWY-STP       =  on
    GTWY-LNKSET    =  on
    MTCD-STP       =  on
    MTCD-LINK      =  on
    MTCD-LNKSET    =  on
    
  11. Place the MCPMs back into service using the rst-card specifying the location of each MCPM.

    For this example, enter these commands.

    rst-card:loc=2107

    rst-card:loc=2108

    rst-card:loc=2111

    When each of these commands have successfully completed, this message should appear.

    
    rlghncxa03w 09-03-01 21:20:37 GMT EAGLE5 40.1.0
    Card has been allowed.
    
  12. Display the status of the MCPMs in the database with the rept-stat-meas command.

    This is an example of the possible output.

    
    rlghncxa03w 09-03-01 16:43:42 GMT  EAGLE5 40.1.0
    
                          PST            SST       AST
    MEAS SS               IS-NR          Active    -----
            ALARM STATUS =   No Alarms
    
        CARD   VERSION         TYPE    PST           SST        AST
        2107 P 101-009-000     EDSM    IS-NR         Active     -----
           IP Link A                   IS-NR         Active     Available
        2108   101-009-000     EDSM    IS-NR         Active     -----
           IP Link A                   IS-NR         Active     Available
        2111   101-009-000     EDSM    IS-NR         Active     -----
           IP Link A                   IS-NR         Active     Available
      
        CARD 2107 ALARM STATUS = No Alarms
        CARD 2108 ALARM STATUS = No Alarms
        CARD 2111 ALARM STATUS = No Alarms
    

Figure 2-14 Formatting Removable Media



Sheet 1 of 3



Sheet 2 of 3



Sheet 3 of 3