Verifying Recovery

8 Verifying Recovery

This chapter describes procedures used to verify the status of the LSMS after performing recovery procedures.

Introduction

This chapter describes procedures used to verify the status of the LSMS after performing recovery procedures.

Verifying that the LSMS Is Fully Functional

Perform the tests in the order shown in Table 8-1 to verify that the LSMS is fully functional following file system restoration. If any of these tests fail, contact the unresolvable-reference.html#GUID-646F2C79-C167-4B5A-A8DF-7ED0EAA9AD66.

Table 8-1 Recovery Acceptance Tests

	Condition to Verify	Test to Perform
1	One server is in ACTIVE state and the other server is in STANDY state	Verifying the State of the Servers
2	The appropriate software processes are running on the primary server	Verifying the Processes Running on the Active Server
3	The GUI process can be started on the primary server	Verifying the GUI Operability on the Active Server
4	Switchover can be performed from the active server to the standby server	Manually Switching Over from the Active Server to the Standby Server
5	The appropriate software processes can be run on the newly active server	Verifying the Processes Running on the Active Server
6	The GUI process can be started on the newly active server	Verifying the GUI Operability on the Active Server
7	Switchover can be performed from the active server to the standby server	Manually Switching Over from the Active Server to the Standby Server
8	The appropriate software processes can be run on the newly active server	Verifying the Processes Running on the Active Server
9	The GUI process can be started on the newly active server	Verifying the GUI Operability on the Active Server

Verifying the State of the Servers

Use the TPD High Availability (HA) utility to verify that one server is in ACTIVE state and the other server is in STANDBY state. See Determining the Server Status.

Verifying the Processes Running on the Active Server

Display the status of all processes that are configured to run on the active server by entering each of the following commands and examining their outputs:

# /usr/TKLC/plat/bin/syscheck -v proc run

# /usr/TKLC/plat/bin/syscheck -v lsmshc proc

The following sample output from syscheck -v proc run indicates which processes are configured to be running on the active server and that all expected instances of the processes are running:


Running modules in class proc... 
       run: Checking supman...
       run: Found 1 instance(s) of the supman process.
       run: Checking lsman...
       run: Found 1 instance(s) of the lsman process.
       run: Checking npacagent...
       run: Found 1 instance(s) of the npacagent process.
       run: Checking eagleagent...
       run: Found 2 instance(s) of the eagleagent process.
       run: Checking rmtpmgr...
       run: Found 1 instance(s) of the rmtpmgr process.
       run: Checking rmtpagent...
       run: Found 1 instance(s) of the rmtpagent process.
       run: Checking reportman...
       run: Found 1 instance(s) of the reportman process.
       run: Checking lsmslogd...
       run: Found 1 instance(s) of the lsmslogd process.
       run: Checking sentryd...
       run: Found 1 instance(s) of the sentryd process.
       run: Checking survMon...
       run: Found 1 instance(s) of the survMon process.
       run: Checking smartd...
       run: Found 1 instance(s) of the smartd process.
       run: Checking atd...
       run: Found 1 instance(s) of the atd process.
       run: Checking crond...
       run: Found 1 instance(s) of the crond process.
       run: Checking sshd...
       run: Found 7 instance(s) of the sshd process.
       run: Checking syscheck...
       run: Found 1 instance(s) of the syscheck process.
       run: Checking syslogd...
       run: Found 1 instance(s) of the syslogd process.
Return string: "OK"
                                 OK
The log is available at:
  -->/var/TKLC/log/syscheck/fail_log

If you see FAILURE (similar to the following example) for any process except the GUI process, contact the unresolvable-reference.html#GUID-646F2C79-C167-4B5A-A8DF-7ED0EAA9AD66:


run: Only 0 instance(s) of  lsmslogd running. 1 instance(s) required.

The following sample output from syscheck -v lsmshc proc indicates which processes are configured to be running on the active server and that all expected instances of the processes are running:


Running modules in class lsmshc...
      proc: Node active, checking
      proc: Checking supman...
      proc: Found 1 instance(s) of the supman process.
      proc: Checking lsman...
      proc: Found 1 instance(s) of the lsman process.
      proc: Checking npacagent...
      proc: Found 1 instance(s) of the npacagent process.
      proc: Checking eagleagent...
      proc: Found 1 instance(s) of the eagleagent process.
      proc: Checking rmtpmgr...
      proc: Found 1 instance(s) of the rmtpmgr process.
      proc: Checking rmtpagent...
      proc: Found 1 instance(s) of the rmtpagent process.
      proc: Checking reportman...
      proc: Found 1 instance(s) of the reportman process.
      proc: Checking lsmslogd...
      proc: Found 1 instance(s) of the lsmslogd process.
      proc: Checking sentryd...
      proc: Found 1 instance(s) of the sentryd process.
Return string: "OK"
                                 OK
The log is available at:
  -->/var/TKLC/log/syscheck/fail_log

Verifying the GUI Operability on the Active Server

Perform the following procedure to verify that the LSMS graphical user interface will open:

Perform the procedure described in “Logging In to LSMS Server Command Line” using the hostname of the active server.
Perform the procedure described in Starting an Web-Based LSMS GUI Session, using an NPAC-provided Service Provider ID.
Select Exit/Logout from the User/Session menu on the LSMS Console window.
The console logout window displays. Click OK to complete the logout.