3.1.2 Information Messages; Corrective Action Required

The information messages that corrective actions are required are displayed by Cluster Admin. They are described in message number sequence.

2012 : No matching entries found.

Content:

No results found for the specified entries for log messages.

Corrective action:

Change the entries.

2019 : Exit Cluster Admin?

Content:

Do you want to exit Cluster Admin GUI?

Corrective action:

Click either of the following buttons:

Yes: Exits Cluster Admin GUI.
No: Continues the operation.

2584 :node failed to stop. Do you wish to retry?

Corrective action:

Click either of the following buttons:

Yes: Retries to stop the node.
No: Does not stop the node.

2589 :node failed to start. Do you wish to retry?

Corrective action:

Click either of the following buttons:

Yes: Retries to start the node.
No: Does not start the node.

2597 :Do you wish to invoke the Shutdown Facility Wizard to configure this cluster?

Corrective action:

Invoke the Shutdown Facility Wizard to continue this cluster configuration.

2751 :This configuration uses unconnected interfaces. It is notpossible to verify the integrity of the configuration.
Do you wish to continue?

Corrective action:

Click either of the following buttons:

Yes: Continues the operation.
No: Stops the operation.

2753 :Are you sure you want to mark node0 as down on node1?

Corrective action:

Click either of the following buttons:

Yes: Marks DOWN.
No: Does not mark DOWN.

2754 :Are you sure you wish to remove node from CIM?

Corrective action:

Click either of the following buttons:

Yes: Removes the node.
No: Does not remove the node.

2755 : Are you sure you wish to stop CF and all services on all nodes?

Corrective action:

Click either of the following buttons:

Yes: Stops all the nodes.
No: Does not stop all the nodes.

2756 :Are you sure you wish to override CIM on node?

Corrective action:

Click either of the following buttons:

Yes: Overrides CIM.
No: Does not override CIM.

2904 : Exit Shutdown Facility configuration wizard?

Content:

Do you want to exit the Shutdown Facility configuration wizard?

Corrective action:

Click either of the following buttons:

Yes: Exits the Shutdown Facility configuration wizard.
No: Continues the Shutdown Facility configuration wizard.

2999 : ICMP shutdown agent cannot be selected because the cluster is not on the guest domain in Oracle VM Server for SPARC.
Refer to the "PRIMECLUSTER Installation and Administration Guide" and select an appropriate shutdown agent.

Corrective action:

See "Configuring the Shutdown Facility" in "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)," and then select an appropriate shutdown agent.

3011 : Information: RMS is not running on any of the hosts. It must be started.

Content:

RMS is not running on any node.

Corrective action:

Check if RMS is running or not. Start RMS if it is not running. If RMS is running, 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."

3035 :Shutdown failed.
Click "msg" tab for details of the error returned from hvshut.
Do you want to force a shutdown ?

Corrective action:

Click either of the following buttons:

Yes: Forces a shutdown.
No: Does not force a shutdown.

3045 :Are you sure you want to activate application application across the entire cluster ?
Note that a separate Online request will be needed to actually start the application.

Corrective action:

Click either of the following buttons:

Yes: Activates the cluster application.
No: Does not activate the cluster application.

3046 :Are you sure you want to deactivate application application across the entire cluster ?
Node that an Activation request will be needed to bring the application out of its deactivated state.

Corrective action:

Click either of the following buttons:

Yes: Deactivates the cluster application.
No: Does not deactivate the cluster application.

3047 :Are you sure you wish to attempt to clear all faults for application application on <node type> <node name>?

Content:

Are you sure you wish to attempt to clear all faults for Cluster application userApplication on <node name>?

Corrective action:

Click either of the following buttons:

Yes: Clears Fault.
No: Does not clear Fault.

3049 :Are you sure you want to attempt to clear wait state for <node name> <node type> on all cluster hosts ?
Note that this command assumes the cluster host has been manually "Killed",
i.e, it has been shut down such that no cluster resources are online.
If this command is executed without first having manually "killed" the luster host,
data corruption may occur!

Content:

Are you sure you want to attempt to clear Wait state for <node name> on all cluster hosts?

* It is recommended to click No to protect against potential data corruption.

Corrective action:

Click either of the following buttons:

Yes: Clears Wait state.
No: Does not clear Wait state.

3050 :Are you sure you want to attempt to clear wait state for <node name> <node type> on all cluster hosts ?
Note that it would be done by returning the specified <node type> to online state.

Corrective action:

Click either of the following buttons:

Yes: Clears Wait state.
No: Does not clear Wait state.

3051 :Are you sure you wish to force application application online on <node type> <node name> ?
Warning: The forced switch option ignores potential error conditions. Used improperly, it can result in data corruption.

Corrective action:

Click either of the following buttons:

Yes: Forces the cluster application Online.
No: Does not force the cluster application Online.

3052 :Are you sure you wish to take application application offline on host node and bring it online on <node type> <node name> ?

Corrective action:

Click either of the following buttons:

Yes: Switches the cluster application.
No: Does not switch the cluster application.

3053 :Are you sure you wish to bring application application online on <node type> <node name> ?

Corrective action:

Click either of the following buttons:

Yes: Brings the cluster application Online.
No: Does not bring the cluster application Online.

3054 :Are you sure you wish to bring application application online on the highest priority host?
Note: If the application is already online on the highest priority host,
this operation will not have any effect.

Corrective action:

Click either of the following buttons:

Yes: Brings the cluster application Online.
No: Does not bring the cluster application Online.

3055 :Are you sure you wish to start the RMS Configuration Monitor on <node type> <node name> ?

Corrective action:

Click either of the following buttons:

Yes: Starts RMS.
No: Does not start RMS.

3056 :Are you sure you wish to bring application application to a standby state ?

Corrective action:

Click either of the following buttons:

Yes: Brings the cluster application to Standby.
No: Does not bring the cluster application to Standby.

3060 :Fatal Error internal: RMS.clone called with null pointer.

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."

3061 :Error: Remote connection failed, Exception: message.

Content:

Failed to connect to the Remote host.

Corrective action:

3062 :Error: Unable to connect to host domain port.
message
Verify node name, port number and if web server is running.

Content:

Failed to connect to the Remote host.

Corrective action:

3063 :Error: Unable to open reader for file file
Exception: exception.

Content:

An internal error occurred in the program.

Corrective action:

3064 :No open sessions.

Content:

An internal error occurred in the program.

Corrective action:

3065 :Error: Session <rms session> not found.

Content:

An internal error occurred in the program.

Corrective action:

3066 :Missing rc: internal Error.

Content:

An internal error occurred in the program.

Corrective action:

3067 :rmsCluster.RT is not null.

Content:

An internal error occurred in the program.

Corrective action:

3068 :Warning: Configuration has no graph, only <number of nodes> disjoint nodes.

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."

3069 :Warning: Unable to draw graph.

Content:

An internal error occurred in the program.

Corrective action:

3083 :CRM is not installed on node.

Content:

CRM software has not been installed on the specified node.

Corrective action:

3138 : All SysNodes are online or coming up.

Content:

All sysnodes are up or are coming up.

Corrective action:

Wait for the nodes to be online.

3141 : Unable to get valid RMS or CF Node list.

Content:

An internal error occurred in the program.

Corrective action:

3146 :Are you sure you want to activate scalable application application across the entire cluster ?
Note that a separate Online request will be needed to actually start the application.

Content:

GUI message asking to initiate hvutil -a.

Corrective action:

Click either of the following buttons:

Yes: Starts the scalable application.
No: Does not start the scalable application.

3147 :Are you sure you want to deactivate scalable application application across the entire cluster ?
Note that an Activation request will be needed to bring the application out of its deactivated state.

Content:

GUI message asking to initiate hvutil -d.

Corrective action:

Click either of the following buttons:

Yes: Stops the scalable application.
No: Continues the scalable application.

3148 :Are you sure you wish to attempt to clear all faults for scalable application application on <node type> <node name> ?

Content:

GUI message asking to initiate hvutil -c.

Corrective action:

Click either of the following buttons:

Yes: Clears all Fault states for the scalable application.
No: Does not clear all Fault states for the scalable application.

3151 :Are you sure you wish to take scalable application application offline on host node and bring it online on <node type> <node name> ?

Content:

GUI message asking to initiate hvswitch.

Corrective action:

Click either of the following buttons:

Yes: Switches the scalable application.
No: Does not switch the scalable application.

3152 :Are you sure you wish to bring scalable application application online on <node type> <node name> ?

Content:

GUI message asking to initiate hvswitch.

Corrective action:

Click either of the following buttons:

Yes: Brings the scalable application Online.
No: Does not bring the scalable application to Online.

3153 :Are you sure you wish to bring scalable application application online on the highest priority host?
Note: If the application is already online on the highest priority host,
this operation will not have any effect.

Content:

GUI message asking to initiate hvswitch.

Corrective action:

Click either of the following buttons:

Yes: Brings the scalable application Online.
No: Does not bring the scalable application Online.

3154 :Are you sure you wish to bring scalable application application to a standby state ?

Content:

GUI message asking to initiate hvutil -s.

Corrective action:

Click either of the following buttons:

Yes: Brings the scalable application Standby.
No: Does not bring the scalable application.

3161 :Are you sure you wish to take application application out of maintenance mode?

Content:

GUI message asking to initiate hvutil -m.

Corrective action:

Click either of the following buttons:

Yes: Takes the cluster application out of maintenance mode.
No: Does not take the cluster application out of maintenance mode.

3163 :Are you sure you wish to take scalable application application out of maintenance mode?

Content:

GUI message asking to initiate hvutil -m.

Corrective action:

Click either of the following buttons:

Yes: Takes the cluster application out of maintenance mode.
No: Does not take the cluster application out of maintenance mode.

3164 :Are you sure you wish to take ALL the applications on the cluster out of maintenance mode?

Content:

GUI message asking to initiate hvutil -M.

Corrective action:

Click either of the following buttons:

Yes: Takes all cluster applications out of maintenance mode.
No: Does not take all cluster applications out of maintenance mode.

4100 : ICMP shutdown agent cannot be selected because I/O fencing function of GDS is not configured.
Refer to the "PRIMECLUSTER Installation and Administration Guide" and configure I/O fencing function of GDS first.

Content

The ICMP shutdown agent cannot be selected because the I/O fencing function of GDS is not configured or the setting is incorrect.

Corrective action:

See "Setting I/O Fencing Function of GDS" in "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)," and then set the ICMP shutdown agent after setting the I/O fencing function of GDS.
Add the case-sensitive description to the setting file when setting "SDX_VM_IO_FENCE=on".

4101 : For CF node node, the IP Address m and IP Address n are duplicate.
Select a different IP Address or decrease the number of IP Address.

Content:

IP address m and IP address n which are used to confirm alive node in CF node are duplicated.

Corrective action:

Select a different IP address or decrease the number of IP address.

4102 : The following IP address(es) in the configuration are displayed as blank because they are not assigned on the node.
Select IP address(es) from the list of valid IP address(es) assigned on the node.
       IP Address1(node1)
       IP Address2(node2)
                            :
       IP Address n(node n)

Content:

The configured IP addresses are displayed as blank, because they are not assigned on the node of CF node.

Corrective action:

Select IP address (es) from the list of valid IP address (es) that are assigned on the corresponding node.

4103 : IP address column "IP address n" for CF node node is not selected.
You must specify IP address to check whether the CF node is alive.

Content:

The used IP address in the CF node <CF nodename> cannot be selected.

Corrective action:

Select the IP address used to confirm alive node.

Check whether there are other unselected IP address columns.