PRIMECLUSTER Messages

5.1.3 Warning Messages

CF: A node reconfiguration event has occured on cluster node: %s.

Content:

A node reconfiguration event has occurred on the specified node. This message is displayed when an extra node is added or other reconfiguration event has occurred.

Corrective action:

No action is required.

CF: carp_event: bad nodeid (#0000 nodenum)

Content:

This message is generated by CIP when a bad nodenumber is received.

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

CF: carp_event: Warning: CARP: Node %d trying to be our CIP address %d.%d.%d.%d. (#0000 n1 n2 n3 n4)

Content:

On the displayed node, the CIP address of CARP (CIP APR daemon) is the same as the CIP address of this node.

Corrective action:

Correct the redundant CIP address and restart CF.

CF: cf_cleanup_module: defer work element still in use

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

CF: cf_cleanup_module: input work element still in use

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

CF: cflog: Check the keywords in the format specified. (#xxxx n1)

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

CF: cfng Error: cfng_unpack_def: nsi_getarrcnt failed. (#xxxx)

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

CF: cfng Error: cfng_unpack_def: nsi_setarrcnt failed. (#xxxx)

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

CF: cfng Error: cfng_unpack_def: nsi_unpack failed. (#xxxx)

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

CF: cfng Error: cfng_unpack_grpname: failed. (#xxxx)

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

CF: cfng Error: ng_create: cfng_unpack_def failed. (#xxxx)

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

CF: cfng Error: ng_create: group already exists. (#xxxx)

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

CF: cfng Error: ng_delete: cfng_unpack_def failed. (#xxxx)

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

CF: cfng Error: ng_delete: group does not exist. (#xxxx)

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

CF: cfng Error: ng_eventd: nsi_setarrcnt failed. (#xxxx)

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

CF: cfng Error: ng_op_done: cfng_unpack_def failed. (#xxxx)

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

CF: cfng Error: ng_replace: cfng_unpack_def failed. (#xxxx)

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

CF: cfng Error: ng_replace: failed. (#xxxx)

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

CF: cfng: ng_delete_all Error: %s. (#xxxx)

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

CF: cfng: ng_eventd: nsi_pack failed. (#xxxx)

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

CF: cfng: ng_eventd: nsi_size failed. (#xxxx)

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

CF: cfng: ng_node_change: failed to get name from node id. (#xxxx)

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

CF: cfset Error: linux_ioctl: not enough memory to return values.

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

CF: cfset Error: linux_ioctl: OSD_copy_from_user fails.

Content:

A buffer copy from userspace to kernelspace has failed.

Corrective action:

Check for an associated OS error and correct problem if possible. If OS problem is corrected, restart CF. If OS problem not identified, 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."

CF: cfset Error: linux_ioctl: OSD_copy_to_user fails.

Content:

A buffer copy from kernelspace to userspace has failed.

Corrective action:

Check for an associated OS error and correct problem if possible. If OS problem is corrected, restart CF. If OS problem not identified, 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."

CF: Cfset: Invalid value for CLUSTER_NODEDOWN_HTBTRPLY, setting to ON: %s. (#0000 n1)

Content:

The value set for CLUSTER_NODEDOWN_HTBTRPLY in /etc/default/cluster.config is invalid.

Corrective action:

Set the valid value for CLUSTER_NODEDOWN_HTBTRPLY in /etc/default/cluster.config. Apply this value to the CF module by cfset command.

CF: Cfset: Invalid value for CLUSTER_TIMEOUT, setting to 1: %s. (#0000 n1)

Content:

The value set for CLUSTER_TIMEOUT in /etc/default/cluster.config is invalid.

Corrective action:

Set the valid value for CLUSTER_TIMEOUT in /etc/default/cluster.config. Apply this value to the CF module by cfset command.

CF: cftool -k may be required for node: %s.

Content:

A node is trying to join the cluster, but has not yet been declared DOWN.

Corrective action:

If SF (Shutdown Facility) is not running, a 'cftool -k' may be required to transit the specified node to a DOWN state. If SF 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."

CF: CF-force-panic timeout: requires CFSF is not running.

Content:

Indicates CF is running in Debug mode and a forced panic was attempted, but SF (Shutdown Facility) cannot be activated in this mode.

Corrective action:

CF should not be in the Debug mode unless instructed by field engineers.

CF: cip: Failed to register ens EVENT_CIP

Content:

This message is generated when failed in registration of the function executed upon ENS event EVENT_CIP generation during CIP initialization.

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

CF: cip: Failed to register ens EVENT_NODE_LEFTCLUSTER

Content:

This message is generated when failed in registration of the function executed upon ENS event EVENT_NODE_LEFTCLUSTER generation during CIP initialization.

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

CF: cip: Failed to register icf channel ICF_SVC_CIP_CTL

Content:

This message is generated when failed in registration of the function to ICF service ICF_CIP_CTL during CIP initialization.

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

CF: cip: message SYNC_CIP_VERSION is too short

Content:

This message is generated when CIP receives a garbled message.

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

CF: Damaged raw icf packet detected in JoinGetMessage: dropped.

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

CF: device %s ineligible for CF use. Now "enslaved" to a bonding driver.

Content:

During CF initialization the specified CF cluster device was found to be inadequate. The device is already used' by another driver.

Corrective action:

Check the configuration for the specified device. It is not valid to use a device for a cluster interconnect if that device is used by another driver.

CF: device %s: link is %s

Content:

During CF initialization, the current link state of the cluster interconnect is reported.

Corrective action:

No action is required.

CF: ELM init: : %s.

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

cf: eventlog   CF: Problem detected on cluster interconnect device-name to node nodename: missing heartbeat replies.

Content:

The heartbeat between CF's has discontinued. It is possible that communications cannot be done because of hardware failure of the network connected to the cluster.

Corrective action:

Replace the LAN card or the cable to remove the hardware breakdown cause.

CF: Icf: Xmit timeout: flush svcq.

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

CF: Initialization failed. Error: No network interface devices found.

Content:

During CF initialization phase, no network devices were found. CF cannot complete initialization.

Corrective action:

Determine if there are any network devices on the node. If network devices are present, 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."

CF: Initialization failed. Error: Unsupported network interface devices found.

Content:

The name of the network device created and used by PRIMECLUSTER has already been existed.

Corrective action:

Check if the name of the network device "cipX (X is a number from 0 to 7)" exists on the node.
If it exists, change the name to other than "cipX."

CF: Join Aborted: nodename1 or nodename2 must be removed from cluster.

Content:

Two nodes in the cluster have the same node ID.

Corrective action:

Recheck the cluster configuration and then configure the nodes in the cluster again to avoid duplicate node IDs. After that, restart the CF.

CF: Join Aborted: Duplicate nodename nodename exists in cluster clustername.

Content:

The join processing cannot complete due to another node in the cluster having the same nodename.

Corrective action:

Determine why multiple nodes in the cluster have the same nodename, fix the problem, and restart CF.

CF: Join client nodename timed out. (#0000 nodenum)

Content:

This message is output on a node, which is a join server, when no response is received from a client node for a certain period of time. In this case, the client node has not joined a cluster.

Corrective action:

Restart the client node to check if the error is solved.

If the error is not solved, 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."

CF: Join Error: Attempt to send message on unconfigured device. (#0000 n1)

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

CF: Join Error: Invalid configuration: another node has a device with a duplicate address.

Content:

Another node in the cluster is using the same internal unique node ID.

Corrective action:

This is most likely due to multiple cluster nodes having the same MAC address for a cluster device. Generally occurs if a virtual device is incorrectly configured. Correct the problem and restart CF.

CF: Join Error: Same node ID for nodename1 and nodename2 in same cluster. (#0000 n1)

Content:

Two nodes in the cluster have the same node ID..

Corrective action:

Recheck the cluster configuration and then configure the nodes in the cluster again to avoid duplicate node IDs. After that, restart the CF.

CF: Join Read Config Error: internal configuration error.

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

CF: Join Server Reply Error: Attempt to send message on unconfigured device. (#0000 n1)

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

CF: MTU mismatch found on cluster interconnect devname to node nodename.

Content:

The specified cluster interconnect has a different MTU (maximum transmission unit) on this cluster node compared to the peer cluster node.

Corrective action:

Correct the problem with the device(s) which have mismatched MTUs and restart CF.

CF: No join servers found.

Content:

This message is generated when a node cannot detect any nodes willing to act as a join server.

Corrective action:

If no other active nodes exist, no corrective action is required. In other cases, check the network configuration.

If the network configuration is correct, 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."

CF: nodename: busy serving another client: retrying.

Content:

The server nodename cannot accept the join request from this client node because it is currently executing the join processing of another client node. The client node will retry joining the cluster later.

Corrective action:

As it is an information message, no action is required. If retries repeated several times in vain, however, check the network configuration. If possible, reboot each cluster node to see whether the problem is cleared. If the problem cannot be solved, 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."

CF: nodename Error: local node has no route to node: join aborted.

Content:

This message is generated when a node is attempting to join a cluster, but fails to detect a route to one or more nodes that are already members of the cluster.

Corrective action:

Check the network configuration.

CF: nodename Error: no echo response from node: join aborted.

Content:

This message is generated when a node is attempting to join a cluster, but is having difficulty communicating with all the nodes in the cluster.

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

CF: OSD_allocate_memory: Warning, vmalloc failure...retrying (%d %d)

Content:

The CF memory allocator is having unexpected failures when requesting kernel memory using the vmalloc interface. The memory request will be retried.

Corrective action:

Check for associated OS messages indicating depletion of OS memory. It may be necessary to reboot the node to correct the problem with kernel memory depletion.

If no OS error was found or the problem cannot be identified, 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."

CF: OSD_defer_work_element_alloc: no free work_elements

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

CF: OSD_defer_work_element_alloc: no more work_elements, never should be here

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

CF: OSD_iwork_element_alloc: no free work_elements

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

CF: OSD_iwork_element_alloc: no more work_elements, never should be here

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

CF: Problem detected on cluster interconnect devicename to node nodename : ICF route marked down.

Content:

The ICF route is closed, as delay of communications using ICF failed five consecutive times.

Corrective action:

Replace the LAN card or the cable to remove the hardware breakdown cause.

CF: Received out of sequence packets from join client: nodename

Content:

This message is generated when a node, acting as a join server, is having difficulty communicating with the client node. Both nodes will attempt to restart the join process.

Corrective action:

No action is required.

CF: route ignored on local device: %s. (#0000 n1 n2 n3)

Content:

The specified cluster interconnect has a different MTU (maximum transmission unit) on this cluster node compared to the peer cluster node.

Corrective action:

Correct the problem with the device(s) which have mismatched MTUs and restart CF.

CF: Route recovery on devname to node nodename. (#xxxx n1 n2 n3 n4)

Content:

This message indicates that a new network was discovered to a displayed cluster node because an extra network was added or the network error is resolved, and the new network is now being used.

Corrective action:

No action is required.

CF: servername: ...

Content:

There are the following messages that begin by "CF: servername:"

CF: servername: busy: cluster join in progress: retrying

CF: servername: busy: local node not DOWN: retrying

CF: servername: busy mastering: retrying

CF: servername: busy serving another client: retrying

CF: servername: local node's status is UP: retrying

CF: servername: new node number not available: join aborted

These messages are generated when a node is attempting to join a cluster, but the join server is busy with another client node. (Only one join may be active in/on the cluster at a time.) Another reason for this message to be generated is that the client node is currently in LEFTCLUSTER state. A node cannot re-join a cluster, unless its state is DOWN. (For details on the " cftool -k" command, see the manual pages of "cftool".)

Corrective action:

If the client node is in the LEFTCLUSTER state, change to the DOWN state. For details on the " cftool -k" command, see the manual pages of "cftool". In other cases, no action is required.

CF: socket refcnt less than initialized value: ignored. (#0000 n1)

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

CF: symsrv loadsyms Error: failure to upload symsrv semaphore function table. (#0000 n1)

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

CF: this node attempting to declare itself failed: ignored.

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

CF: this node attempting to declare itself questionable: ignored.

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

CF: unexpected icfip_sock_data_ready call: ignored.

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

CF: unexpected icfip_sock_destruct call: ignored. (#0000 n1)

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

CF: unexpected icfip_sock_error_report call: ignored.

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

CF: unexpected icfip_sock_state_change call: ignored.

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

CF: unexpected icfip_sock_write_space call: ignored.

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

CF: Unknown log event: strings: %s, %s

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

CF: User level event memory overflow: Event dropped (#0000 eventid)

Content:

This message is generated when an ENS user event is received, but there is no memory for the event to be queued.

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

CF: WARNING: a new symsrv driver will be used upon system reboot.

Content:

The symsrv driver that is loaded in the kernel is an old version that does not match the current CF driver. A new symsrv driver will be used after the system is rebooted.

Corrective action:

Reboot the node so that the new symsrv driver will be loaded.

CF: WARNING: an old version of the symsrv driver is being used.

Content:

The symsrv driver that is loaded in the kernel is an old version that does not match the current CF driver. This is most likely due to installing a CF patch while the symsrv driver was still loaded in the kernel.

Corrective action:

Reboot the node so that the new symsrv driver will be loaded.

CF: WARNING: cfconfig command execution will not be synchronized.

Content:

The symsrv driver that is loaded in the kernel is an old version that does not match the current CF driver. Execution of the cfconfig command will not be synchronized.

Corrective action:

Reboot the node so that the new symsrv driver will be loaded.

CF: %s: busy: a node is leaving cluster: retrying.

Content:

This node is joining the cluster and the join master has responded that it is currently busy processing a node leaving the cluster operation. The join will be retried.

Corrective action:

No action is required.

CF: %s: busy: node down processing in progress: retrying.

Content:

A destination node is in stop processing. The connection will be retried.

Corrective action:

No action is required.

CF: %s: device not found.

Content:

During CF initialization the specified device was not found.

Corrective action:

Check the CF configuration that the specified cluster devices are valid and restart CF.

CF: %s: missed echo responses: retrying.

Content:

A connection between nodes failed. The connection will be retried.

Corrective action:

A network communication error is caused by a high load state or the network itself has problems. No corrective action is required if the connection is completed after retry.

When the connection fails again after retry, 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."

CF: %s: Node down in progress. Joins retry until node down complete.

Content:

When a node within the cluster is under stop processing, this node cannot join the cluster. The node has to wait to join the cluster until it is completely stopped.

Corrective action:

No action is required.

CF: %s: Node leaving cluster. Joins retry until node leaves cluster.

Content:

When a node within the cluster is under stop processing, this node cannot join the cluster. The node has to wait to join the cluster until it is completely stopped.

Corrective action:

No action is required.

CF: %s: Node trying to join cluster but not declared DOWN.

Content:

A node is trying to join the cluster, but has not yet been declared DOWN.

Corrective action:

If SF (Shutdown Facility) is not running, a 'cftool -k' is required to transit the specified node to a DOWN state. If SF 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."

cf_register_ioctls: %d errors

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

cf_unregister_ioctls: %d errors

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

cip: Add device %s does not support multicast (0x%x)

Content:

The specified device does not support multicast.

Corrective action:

Check the specified device to determine if it is faulty or misconfigured.

cip: Device %s does not support multicast (0x%x)

Content:

The specified device does not support multicast.

Corrective action:

Check the specified device to determine if it is faulty or misconfigured.

cip: failed to allocate memory for device.

Content:

During CIP module initialization allocation of memory failed.

Corrective action:

A memory allocation error or other OS error may be the cause of this error. To solve the problem, search the OS error that indicates why memory requirements by OS failed. If no OS error was found or the problem cannot be identified, 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."

cip: Msg size %d exceeds mtu %d

Content:

This message indicates that the upper-layer protocol (IP) attempted to send a packet that is larger than the CIP device MTU.

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

cip: NULL in_dev for unit %d

Content:

Information message.

Corrective action:

No action is required.

cip: Only ETH_P_IP type packet is supported.

Content:

Non-IP packet was sent to CIP.

Corrective action:

No action is required.

cip: receiving multicast address requests of invalid size (%d, %d)

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

cip: Strange socket buffer. Insufficient room.

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

cluster interconnect is not yet configured.

Content:

During CIP initialization, no valid cluster interconnects were detected. Available.

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

create_dev_entry for %s: %s got 0x%08x

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

Failed to Register the CF driver (rc=0x%08x)

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

linux_setconf: no configured netinfo devices found

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

OSD_lock_user_memory: NOT IMPLEMENTED

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

OSD_NET_one_device_detach: invalid device index

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

OSD_SYS_create_device failed to create cip.

Content:

During CIP module initialization the device creation failed.

Corrective action:

A memory allocation error or other OS error may be the cause of this error. To solve the problem, search the OS error that indicates why memory requirements by OS failed. If no OS error was found or the problem cannot be identified, 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."

OSD_unlock_user_memory: NOT IMPLEMENTED

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

size of base data structures do not match!!! cannot load!!! exiting...

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

Warning!!! ifreq size is different

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

Warning!!! in_device size is different

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

Warning!!! in_ifaddr size is different

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

Warning!!! net_device size is different

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

Warning!!! packet_type size is different

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

Warning!!! rwlock_t size is different

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

Warning!!! semaphore size is different

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

Warning!!! sk_buff size is different

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

Warning!!! spinlock_t size is different

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

Warning!!! timer_list size is different

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

Warning!!! wait_queue_head_t size is different

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