The warning messages displayed by Cluster Admin are described in message number sequence.
Content:
Interface is being used by CF. Using the same interface for the Shutdown Facility may cause problems if cluster partition occurs.
Corrective action:
Check the interface used in the Shutdown Facility.
Content:
Some nodes are unreachable. Running the SF Wizard when some nodes are unreachable can result in incorrect node elimination later on. We strongly recommend you to exit the SF Wizard and do the configuration at a later time when all the nodes are UP and reachable.
Corrective action:
Exist the SF Wizard and check that all the nodes are UP and reachable. Then, perform the configuration.
Content:
Specified Timeout for the RCCU Shutdown Agent is different from the default timeout.
Corrective action:
Set the default timeout value for the RCCU Shutdown Agent.
Content:
Unable to get status of shutdown agent. Check the hardware/software configuration for the shutdown agent. Running the SF Wizard now can result in incorrect configuration. We strongly recommend you to exit the SF Wizard and do the configuration after correcting the shutdown agent setup.
Corrective action:
Exist the SF Wizard and correct the shutdown agent. Then, perform the configuration.
Content:
By choosing "Use Defaults," you will reset the previously configured username and passwords. Are you sure you want to use the default settings?
Corrective action:
If there is no problem for resetting the previously configured username and passwords, select "Use Defaults."
Content:
An internal error occurred in the program.
Corrective action:
Record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
An internal error occurred in the program.
Corrective action:
Record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Information message.
Corrective action:
No action is required.
Content:
Information message.
Corrective action:
No action is required.
Content:
Information message.
Corrective action:
No action is required.
Content:
Information message.
Corrective action:
No action is required.
Content:
This message asks user to allow/disallow forced shutdown without stopping the applications.
Corrective action:
User should answer yes or no for the forced shutdown.
Content:
This message asks user to allow/disallow forced shutdown without stopping the applications.
Corrective action:
User should answer yes or no for the forced shutdown.
Content:
This message asks user to allow/disallow forced shutdown without stopping RMS on all the nodes.
Corrective action:
User should answer yes or no for the forced shutdown.
Content:
RMS cannot be started. Please start CF first.
Corrective action:
Please start CF.
Content:
Maximum number of post cards can be opened is up to five. Please close some of the post cards.
Corrective action:
Please close some of the post cards.
Content:
To check the status or RMS from Cluster Admin, the processing is managed at each node.
This processing is managed separately from connected/selected nodes during Web-Based Admin View or Cluster Admin startup. There is no method to check which node the processing is managed.
This message is output when disconnecting the appropriate node from Web-Based Admin View due to a system shutdown, and so on.
Depending on the management status in Cluster Admin, this message may output even after stopping the system; however there is no problem because this operation is normal.
Corrective action:
Press the Retry button.
Re-connecting Web-Based Admin View to the host allows Cluster Admin to get the status of RMS.
Content:
This message asks user to bring the scalable application Offline.
Corrective action:
User should answer yes or no for the switchover.
Content:
This message asks user to forcibly bring the scalable application Online.
Corrective action:
User should answer yes or no for the forced switchover.
Content:
GUI message asking to forcibly stop RMS on all the nodes without performing Offline processing.
Corrective action:
User should answer yes or no for the forced shutdown.
Content:
This message asks user to change applications to maintenance mode.
Corrective action:
User should answer yes or no for the change.
Content:
This message asks user to change the scalable application to maintenance mode.
Corrective action:
User should answer yes or no for the change.
Content:
This message asks user to change all the applications on the cluster to maintenance mode.
Corrective action:
User should answer yes or no for the change.
