3.7.7 Procedure 18 POST CONFIGURATION HEALTH CHECK

Table 3-23 Procedure 18 – Post Configuration Health Check

S T E P # This procedure determines the health of the Server after an installation. This procedure will perform a syscheck on each LSMS server.Estimated time:5 minutes

☐1.

MPS A and B: Log in to the server as the

user “root”.

 
Login: root
Password: <root_password>

☐2.

MPS A and B: Validate date, time and time zone to ensure accuracy. 

# date
Thu May 12 05:55:27 EDT 2016

MPS A and B: Run the “hastatus” command to verify the HA state of this server.

Run the following command on both LSMS A and B to verify the HA state of mated LSMS pair.

# hastatus

Verify that the hastatus of one of the servers is Active and the other is Standby.

WARNING: If the output from the above command is anything else other than “ACTIVE” and “STANDBY”, do not proceed with this procedure and contact My Oracle Support following the instructions on the Appendix E.

☐3.

LSMS Standby server:

Verify that the STANDBY server’s MySQL replication is functioning properly.

Run the following command to verify that MySQL replication is working correctly on the STANDBY LSMS server:

# tail /var/TKLC/lsms/logs/dbreplMon.log

If MySQL replication is functioning correctly then the following output will be observed, make sure that at least the last line of your output matches the lines below.

Thu May 12 05:58:12 2016 All tests passed on STANDBY
FIPS integrity verification test failed.
FIPS integrity verification test failed.
Thu May 12 05:59:19 2016 All tests passed on STANDBY
FIPS integrity verification test failed.
FIPS integrity verification test failed.
Thu May 12 06:00:25 2016 All tests passed on STANDBY
FIPS integrity verification test failed.
FIPS integrity verification test failed.
Thu May 12 06:01:32 2016 All tests passed on STANDBY

WARNING: If at least the last line of your output does not match the lines above then do not proceed with this upgrade and contact My Oracle Support following the instructions on the Appendix E.

☐4.

MPS A and B:

Execute syscheck

 
# syscheck
Running modules in class disk...
OK
Running modules in class hardware...
OK
Running modules in class lsmshc...
OK
Running modules in class net...
OK
Running modules in class proc...
OK
Running modules in class services...
OK
Running modules in class system...
OK
Running modules in class upgrade...
OK
LOG LOCATION: /var/TKLC/log/syscheck/fail_log

☐5.

LSMS Active server:

Capture the output of ‘sentry status’ command

Run the following command on the ACTIVE LSMS server to display the current LSMS sentry status:

# sentry status

Note: Verify that the output displays a Status of “running” for all processes; the regional processes (npacagents) may or may not be associated in the Comment field. If the output from this command displays any other Status than “running” contact My Oracle Support following the instructions on the Appendix E.

Capture the output from this command and make it available to Oracle Technical Services if required.

This procedure is complete!