PRIMECLUSTER Messages

7.2.2 Error messages

This section explains messages that are output upon error occurrence at executing the cipconfig command for each option specified to the command.

7.2.2.1 cipconfig -l

cipconfig: could not start CIP - detected a problem with CF.
cipconfig: cannot open mconn: #04xx: generic:reason_text

Content:

Getting the node state information from CF has failed. Or, opening the CF device has failed.

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

cipconfig: cannot setup cip: #04xx: generic: reason_text

Content:

The CIP startup routine has failed. There may be problems with the configuration file. Additional error messages, for this case, may also be generated in the system log file:

OSDU_cip_start: cip kickoff failed (errno)

OSDU_cip_start: dl_attach failed: devpathn

OSDU_cip_start: dl_bind failed: devpathn

OSDU_cip_start: dl_info failed: devpath

OSDU_cip_start: failed to open device: /dev/cip (errno)

OSDU_cip_start: failed to open device: devpath (errno)

OSDU_cip_start: I_PLINK failed: devpath (errno)

OSDU_cip_start: POPing module failed: errno

OSDU_cip_start: ppa n is not valid: devpath

OSDU_cip_start: setup controller/speed failed: devpath (errno)

If the device driver for any of the network interfaces used by CIP responds in an unexpected way to DLPI messages, additional message output may occur:

dl_info: DL_INFO_REQ putmsg failed (errno)

dl_info: getmsg for DL_INFO_ACK failed (errno)

dl_attach: DL_ACCESS error

dl_attach: DL_ATTACH_REQ putmsg failed (errno)

dl_attach: DL_BADPPA error

dl_attach: DL_OUTSTATE error

dl_attach: DL_SYSERR error

dl_attach: getmsg for DL_ATTACH response failed (errno)

dl_attach: unknown error

dl_attach: unknown error hexvalue

dl_bind: DL_ACCESS error

dl_bind: DL_BADADDR error

dl_bind: DL_BIND_REQ putmsg failed (errno)

dl_bind: DL_BOUND error

dl_bind: DL_INITFAILED error

dl_bind: DL_NOADDR error

dl_bind: DL_NOAUTO error

dl_bind: DL_NOTESTAUTO error

dl_bind: DL_NOTINIT error

dl_bind: DL_NOXIDAUTO error

dl_bind: DL_OUTSTATE error

dl_bind: DL_SYSERR error

dl_bind: DL_UNSUPPORTED error

dl_bind: getmsg for DL_BIND response failed (errno)

dl_bind: unknown error

dl_bind: unknown error hexvalue

Corrective action:

If these messages appear and they do not seem to be associated with problems in your CIP configuration file, contact field engineers.

7.2.2.2 cipconfig -u

cipconfig: cannot unload cip: #04xx: generic: reason_text

Content:

The CIP shutdown routine has failed. Usually this mean that another PRIMECLUSTER Layered Service has a CIP interface open (active).

Corrective action:

Stop the currently open interface. Additional error messages, for this case, may also be generated in the system log file:

OSDU_cip_stop: failed to unload cip driver

OSDU_cip_stop: failed to open device: /dev/cip (errno)