4 Recovery Support

The information in this section describes the recommended backing up of the RTDB and presents additional recovery support procedures that may be referred to by alarms recovery actions.

Recovering from Problems

This section describes the following recovery procedures:

• Restoring the RTDB from Backup Files
• Recovering From Alarms

Restoring the RTDB from Backup Files

This section describes the procedure for restoring the RTDB from backup files.

Note:

It is recommended that the RTDB be backed up daily (see section, Daily Maintenance Procedures). For ELAP 8.0 or later, daily backups are created automatically.

Use the following procedure to restore the RTDB from a previously prepared backup file.

Caution:

Contact unresolvable-reference.html#GUID-A2C37E16-F0BA-4FB6-9D93-1D4A95A40DC7 before performing this procedure.

1. Contact unresolvable-reference.html#GUID-A2C37E16-F0BA-4FB6-9D93-1D4A95A40DC7.
2. Log in to the ELAP command line interface with user name elapdev and the password associated with that user name.
3. Use the Secure File Transfer Protocol (sftp) to transfer the RTDB backup file, created by the procedure Backing Up the RTDB, to the following location:

   
   /var/TKLC/elap/free/backup
   

4. Log in to the ELAP GUI (see Accessing the ELAP GUI Interface).
5. Select Process Control>Stop Software to ensure that no other updates are occurring.

   The screen shown in Figure 4-1 is displayed.

   Figure 4-1 Stop ELAP Software

   
   
   
   After the software on the selected ELAP has stopped, the screen shown in Figure 4-2 is displayed.

   Figure 4-2 Stop ELAP Software - Success

   
   
   
6. Select RTDB>Maintenance>Restore RTDB.

   The screen shown in Figure 4-3 is displayed.

   Figure 4-3 Restoring the RTDB

   
   
   
7. On the screen shown in Figure 4-3 , select the file that was transferred in 3. Click Restore the RTDB from the Selected File.
8. To confirm restoring a file, click Confirm RTDB Restore shown in Figure 4-4.

   Figure 4-4 Restore the RTDB Confirm

   
   
   
   After the file is successfully restored, the success screen is displayed.

Recovering From Alarms

Alarms are resolved in order of severity level from highest to lowest. When combination alarms are decoded into their individual component alarms, the customer can decide in which order to resolve the alarms because all alarms are of equal severity. For assistance in deciding which alarm to resolve first or how to perform a recovery procedure, contact unresolvable-reference.html#GUID-A2C37E16-F0BA-4FB6-9D93-1D4A95A40DC7.

Evaluate the following problems to find the appropriate recovery procedure as follows:

• If the problem being investigated is no longer displayed on the ELAP GUI, perform the following:
  1. Procedure Decode Alarm Strings
  2. Procedure Determine Alarm Cause
  3. Recovery procedure to which you are directed by procedure Determine Alarm Cause
• If the problem being investigated is being reported currently on the ELAP GUI, perform the following:
  1. Procedure Decode Alarm Strings

Decode Alarm Strings

Use the following procedure to decode alarm strings that consist of multiple alarms.

1. Log in to the User Interface screen of the ELAP GUI (see Accessing the ELAP GUI Interface).
2. After logging in to the ELAP, select Maintenance>Decode MPSAlarm from the menu.
3. Enter the 16-digit alarm string into the window on the Decode MPSAlarm screen, as shown in Figure 4-5.

   Figure 4-5 Decode MPS Alarm Screen

   
   
   
   
   
4. Click the Decode button.
   The system returns information on the Alarm Category (Critical Application, Major Platform) and error text, as shown in Figure 4-6.

   Figure 4-6 Decoded MPS Alarm Information

   
   
   
   
   
5. Find the alarm text string shown on the GUI in Table 5-1. Note the corresponding alarm number change. Perform procedure Determine Alarm Cause.

   Note:

   For combination errors, multiple procedures may be required to resolve the problem.

Determine Alarm Cause

Use this procedure to find information about recovering from an alarm.

1. Record the alarm data string shown in the banner or the Alarm View on the ELAPGUI , or as decoded from Decode Alarm Strings.
2. Run syscheck in Verbose mode (see Running syscheck Through the ELAP GUI).
3. Examine the syscheck output for specific details about the alarm.
4. Find the recovery procedure for the alarm in the procedures shown in Platform and Application Alarms. The alarms are ordered by ascending alarm number.
   Other procedures may be required to complete an alarm recovery procedure:

   • Refer to procedures for replacing Field Replaceable Units (FRUs) in Field Replaceable Units if instructed by an alarm recovery procedure to replace a FRU.
   • Refer to general procedures used in a number of alarm recovery procedures in Platform and Application Alarms
5. If the alarm persists after performing the appropriate procedure, call unresolvable-reference.html#GUID-A2C37E16-F0BA-4FB6-9D93-1D4A95A40DC7.