Content:
This message is generated when a node has left the cluster in an orderly manner (i.e., when cfconfig -u is executed).
Content:
The connection between CF and other nodes has been completed.
Content:
The messages that start with cf: elmlog !rebuild starting are as follows.
cf: elmlog !rebuild starting due to node joining configuration
cf: elmlog !rebuild starting due to node failure
cf: elmlog !rebuild starting due to administrator request
cf: elmlog !rebuild starting due to configuration disagreement
These messages are output when a node reconfiguration is started.
Content:
This message is generated when a node detects a join server and joins an existing cluster, rather than forming a new one.
Content:
This message is generated when a node volunteers to be a join server, but detects an eligible join server with a higher id.
Content:
This message is generated when a node joins an existing cluster.
Content:
The node nodename left the membership of the cluster clustername due to the LEFTCLUSTER event.
Content:
Indicates that the specified node has detected another node as 'questionable'. A node is marked questionable when a heartbeat has not been received in 1/2 the cluster timeout value.
Content:
Indicates that the specified node has detected that this node is 'questionable'. A node is marked questionable when a heartbeat has not been received in 1/2 the cluster timeout value.
Content:
This message is generated by CF as it is starting.
Content:
This message is generated by CF as it is stopping.
Content:
The message indicates that the default value is set for CLUSTER_NODEDOWN_HTBTRPLY.
Content:
The message indicates that the value is set for CLUSTER_NODEDOWN_HTBTRPLY.
Content:
The message indicates that the value is set for CLUSTER_TIMEOUT.
Content:
The message indicates that the value is set for CLUSTER_FORCE_PANIC_TIMEOUT.
Content:
The message indicates that the value is set for CLUSTER_IP_CTRL_TOS.
Content:
The message indicates that the value is set for CLUSTER_IP_DATA_TOS.
Content:
The message indicates that the value is set for CLUSTER_IP_TTL.
Content:
The message indicates that the default value is set for CLUSTER_TIMEOUT.
Content:
The message indicates that the default value is set for CLUSTER_FORCE_PANIC_TIMEOUT.
Content:
The message indicates that the default value is set for CLUSTER_IP_TTL.
Content:
The message indicates that the default value is set for CLUSTER_IP_CTRL_TOS.
Content:
The message indicates that the default value is set for CLUSTER_IP_DATA_TOS.
Content:
Indicates SF (Shutdown Facility) successfully closed CF device.
Content:
Indicates that a LEFTCLUSTER event occurred, but SF (Shutdown Facility) does not have the CF device open. The LEFTCLUSTER will be handled by CF.
Content:
Indicates a LEFTCLUSTER event occurred and the event is being delivered to SF (Shutdown Facility).
Content:
Indicates that CF notified SF (Shutdown Facility) of a node LEFTCLUSTER event, so SF can process the event.
Content:
Indicates SF (Shutdown Facility) has interrupted its wait for event processing, most likely in preparation of stopping.
Content:
Indicates the LEFTCLUSTER event is being broadcast to all the nodes in the cluster.
Content:
Indicates a LEFTCLUSTER event was received and there were other pending events queued.
Content:
The LEFTCLUSTER event was received from the node nodename and the entry of this node will be removed from the SF processing list.
Content:
Indicates the LEFTDOWN event is being broadcast to all the nodes in the cluster.
Content:
Indicates the nodedown event is being broadcast to all the nodes in the cluster.
Content:
Information message.
Content:
Indicates that a node-down event was received, but there is still a LEFTCLUSTER event pending that will be processed first.
Content:
Indicates SF (Shutdown Facility) successfully opened CF device.
Content:
Indicates that the ENS event daemon is stopping.
Content:
Indicates that the ENS node daemon is stopping.
Content:
This message is generated when an ICF route is activated again.
Corrective action:
This message may be generated by the temporary high load on CPU. The heartbeat will return to its normal operation when the load is reduced. You can usually ignore this message if the high CPU load lasts for only a short time.
Content:
Information message.
Content:
Information message.
Content:
This message is generated when the join server is stopped.
Content:
This message is generated when the join daemon is started.
Content:
This message is generated when an active join daemon shuts down.
Content:
Indicates the specified route has transitioned from DOWN to UP as a result of the cluster interconnect getting a link UP.
Content:
This message is generated when a CF initialization is complete.
Content:
Indicates the specified node has not responded to heartbeats in 1/2 the cluster timeout value. If the cluster timeout value is set to the default of 10 seconds, this message will occur when no heartbeats are received from the specified node in 5 seconds.
Content:
A heartbeat to check the status of a node <nodename> is stopped.
The message indicates that the node is alive.
Content:
A heartbeat to check the status of a node <nodename> is started.
Content:
A heartbeat to check the status of a node <nodename> is started.
Content:
Indicates the cfreg daemon has stopped normally.
Content:
CF is started with the CIP interface cipN set to IP address Addr.
Content:
During ELM rebuild post node-down processing, a non-existent lock server was found, so the server is being deleted from the server pool.
Content:
This is a notice message that indicates that remote file copying is redundantly performed by using cfcp.
Content:
Indicates ELM (enhanced lock manager) is rebuilding its lock tables.
Content:
Remote file copy with cfcp failed due to invalid usage of cfcp.
