The RMS troubleshooting process usually begins after you observe an error condition or unexpected state change in Cluster Admin in one of the following areas:
Clusterwide table
RMS tree
Graph
The clusterwide table contains summary information and is a good place to start looking for error conditions. For additional details, you can look at the RMS tree or the graph. Depending on whether you need to look at the switchlogs or application logs, you can then use the log viewer facility to view the log files.
The log viewer has search facilities based on the following:
Keywords
Severity
Non-zero exit codes
Search for causes of errors using the keywords and the date range fields. For emergency, alert, and critical conditions, you can do a search based on severity. For proactive troubleshooting, you can perform a search based on severity for the error, warning, notice, and info severity codes.
Note
It is recommended that you periodically use the log viewer and check the log files based on the severity levels to avoid serious problems. If you cannot diagnose the cause of a problem, look at the log viewer from two or more nodes in the cluster.
Refer to the "F.9 RMS troubleshooting" for an explanation on corrective action.
Resolve error conditions as follows:
Use the Cluster Admin GUI.
View the log files if needed.
Change log levels to get more details.
If you cannot resolve an error condition with the GUI, you can use the command line interface. Use standard UNIX commands.
If a problem persists, check if it is a non-RMS issue and refer to the appropriate manual.
Check for system-related issues like operating system, hardware, or network errors.
Contact field engineers if you cannot resolve the issue.
