PRIMECLUSTER Messages

4.3 Information Messages

This section explains the FJSVcluster format information messages in the order of message numbers. Almost all information messages require no corrective action. Only when action is required, the corrective action is described.

2100 The resource data base has already been set. (detail:code1-code2)

2200 Cluster configuration management facility initialization started.

2201 Cluster configuration management facility initialization completed.

2202 Cluster configuration management facility exit processing started.

2203 Cluster configuration management facility exit processing completed.

2204 Cluster event control facility started.

2205 Cluster event control facility stopped.

2206  The process (count: appli) was restarted.

Content:

The process monitoring function detected that a process being monitored had stopped and restarted the process. count indicates the restart count of the process to be monitored. appli indicates the absolute path name of the restarted process.

Corrective action:

Message 2207 is output before this message.

See the explanation of message 2207.

2620 On the SysNode " SysNode ", the userApplication " userApplication " transitioned to the state state . Therefore, message " number " has been canceled.

Content:

Since the userApplication state has changed, the message has been cancelled. You do not need to respond to the operator intervention message.
SysNode indicates the name of SysNode in which the userApplication state has been changed. userApplication indicates the name of userApplication whose status has been changed. state indicates the userApplication state. number indicates the message number.

2621 The response to the operator intervention message " number " was action.

Content:

The response to the operator intervention message has been made.
number indicates the number of the operator intervention message to which you responded. action indicates with or without response

by yes or no.

2622 There are no outstanding operator intervention messages.

2700 The resource fail has recovered.SysNode:SysNode
    userApplication:userApplication Resorce:resource

Content:

The resource recovered from the failure.
SysNode indicates the name of SysNode whose resource has been recovered. userApplication indicates the name of the userApplication to which the recovered resource belongs. resource indicates the name of the resource that has recovered from the error state.

2701 A failed resource has recovered. SysNode:SysNode

Content:

SysNode that was in the Faulted state due to a node panic entered the Online state.
SysNode indicates a recovered SysNode.

2914 A new disk device(disk ) was found.

Content:

A new disk device(disk ) was found. disk indicates a newly detected shared disk device.

Corrective action:

Register a new detected shared disk device (disk) in the resource database by executing the "clautoconfig(1M)" or using the CRM main window. For details on the "clautoconfig(1M)" command, see the manual pages of "clautoconfig(1M)."

Supplement

This message is also displayed when a node is started on a machine where a DVD or CD-ROM is in a DVD-ROM device.
If the device name indicating the DVD-ROM is in "(disk)", it is not necessary to register it in the resource database. Start up the node after checking a DVD or CD-ROM is not in the DVD-ROM.

2927 A node (node) detected an additional disk. (disk)

Content:

A node (node) detected an additional disk. (disk)
node indicates the node identifier of the node on which a new disk unit was detected while disk indicates the newly detected disk unit.

Corrective action:

Register a newly detected disk unit (disk) in the resource database. A disk unit can be registered in the resource database by using the clautoconfig(1M) command or the CRM main window. For details on the clautoconfig(1M) command, see the manual page describing clautoconfig(1M).
If there are many newly detected disk units, "..." will be suffixed to disk. In this case, you can reference all of newly detected disk units by searching for the message having number 2914 in the /var/adm/messages file on the node where the message has been output.

Supplement

This message is also displayed when a node is started on a machine where a DVD or CD-ROM is in a DVD-ROM device.
If the device name indicating the DVD-ROM in "(disk)", it is not necessary to register it in the resource database. Start up the node after checking a DVD or CD-ROM is not in the DVD-ROM.

3040 The console monitoring agent has been started. (node:nodename)

3041 The console monitoring agent has been stopped. (node:nodename)

3042 The RCI monitoring agent has been started.

3043 The RCI monitoring agent has been stopped.

3044 The console monitoring agent took over monitoring Node targetnode.

3045 The console monitoring agent cancelled to monitor Node targetnode.

3046 The specified option is not registered because it is not required for device. (option:option)

3050 Patrol monitoring started.

3051 Patrol monitoring stopped.

3052 A failed LAN device is found to be properly running as a result of hardware diagnostics. (device:altname rid:rid)

Content:

This indicates that the faulty LAN device is operating normally, as a result of hardware diagnosis.

altname indicates the interface name of the specified LAN device while rid indicates its resource ID.

3053 A failed shared disk unit is found to be properly running as a result of hardware diagnostics. (device:altname rid:rid)

Content:

This indicates that the faulty shared device is operating normally, as a result of hardware diagnosis.

altname indicates the device name of the shared device that is operating normally while rid indicates its resource ID.

3070  "Wait-For-PROM" is enable on the node. (node:nodename)

Content:

"Wait-For-PROM" of the RCI monitoring agent is enabled on the node nodename.

Corrective action:

"Wait-for-PROM," which is not supported, has been enabled. Change the setting of the Shutdown Facility to disable "Wait-for-PROM." For the details, see "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)."

3071  "Wait-For-PROM" of the console monitoring agent is enable on the node. (node:nodename)

Corrective action:

"Wait-for-PROM," which is not supported, has been enabled. Change the setting of the Shutdown Facility to disable "Wait-for-PROM." For the details, see "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)."

3080 The MMB monitoring agent has been started.

3081 The MMB monitoring agent has been stopped.

3082 MMB has been recovered from the failure. (node:nodename mmb_ipaddress1:mmb_ipaddress1 mmb_ipaddress2:mmb_ipaddress2 node_ipaddress1:node_ipaddress1 node_ipaddress2:node_ipaddress2)

3083 Monitoring another node has been started.

3084 Monitoring another node has been stopped.

3085 The MMB IP address or the Node IP address has been changed. (mmb_ipaddress1:mmb_ipaddress1 mmb_ipaddress2:mmb_ipaddress2 node_ipaddress1:node_ipaddress1 node_ipaddress2:node_ipaddress2)

Content:

This indicates that the MMB IP address or the IP address in the management LAN of the shutdown configuration has been changed.

3120 The iRMC asynchronous monitoring agent has been started.

3121 The iRMC asynchronous monitoring agent has been stopped.

3122 MMB has been recovered.
(node:nodename mmb_ipaddress1:mmb_ipaddress1 mmb_ipaddress2:mmb_ipaddress2 node_ipaddress:node_ipaddress)

3123 iRMC has been recovered.
(node:nodename irmc_ipaddress:irmc_ipaddress node_ipaddress:node_ipaddress)

3124 The node status is received.
(node:nodename from:irmc/mmb_ipaddress)

3110 The SNMP monitoring agent has been started.

3111 The SNMP monitoring agent has been stopped.

3200 Cluster resource management facility initialization started.

3201 Cluster resource management facility initialization completed.

3202 Cluster resource management facility exit processing completed.

3203 Resource activation processing started.

3204 Resource activation processing completed.

3205 Resource deactivation processing started.

3206 Resource deactivation processing completed.