A P P E N D I X B - Error Messages from the PMS Application

A P P E N D I X B

Error Messages from the PMS Application

This appendix contains information on PMS error messages.

Overview

PMS is a high-level application. Thus, faults in various places in the software and hardware underlying this application can result in PMS error messages. For example, a fault could occur on the midplane or on a disk. This situation may make it difficult to isolate where a specific fault is occurring. A solution to many PMS error messages is to reset the distributed management card.

PMS error messages are printed to the console you are using to execute the pmsd CLI command; they are not saved to a log on either the distributed management card or on a node board.

Messages

Board RG0 resource state must be OFFLINE to perform operation on this slot

Cause: Resource Group 0 (RG0), or the group of applications on a node board that PMS manages, must be offline before you can run certain commands from the distributed management card.

Action: Change the RG0 state from active to offline. For example, use the command pmsd appoperset -o force_offline.

DM board or switch board slot not managed by PMS Daemon

Cause: Many pmsd CLI commands can generate this message.

Action: PMS does not manage the distributed management card or the switching fabric boards.

Slot not configured to be managed by PMS Daemon

Cause: Many pmsd CLI commands can generate this message.

Action: Use the pmsd slotaddressset command to set the IP address for the slot.

Unable to communicate with CPU board PMS Daemon

Cause: Several pmsd CLI commands can generate this message.

Action: (1) Check network connectivity. (2) Check to see if the ping command works between the distributed management card and the node board. (3) Check the status of the node board with the pmsd slotrndadderssshow command, and modify if appropriate, with the pmsd slotrndaddersssadd command.

Unable to communicate with DM board PMS Daemon

Cause: Many pmsd CLI commands can generate this message. The distributed management card CPU may be temporarily overloaded.

Action: (1) Retry the command after waiting 15 seconds or more. (2) Reset the distributed management card.

Unable to connect to CPU board PMS Daemon

Cause: Several pmsd CLI commands can generate this message.

Unable to connect to DM board COSL

Cause: Many pmsd CLI commands can generate this message. The message usually results from PMS being unable to monitor or control the hardware; PMS cannot get the information it needs from the lower-level common operating system library (COSL) hardware interface.

Action: Reset the distributed management card.

Unable to connect to DM board PMS Daemon

Cause: Many pmsd CLI commands can generate this message. The distributed management card CPU may be temporarily overloaded.

Action: (1) Retry the command after waiting 15 seconds or more. (2) Reset the distributed management card.

Unable to disconnect from DM board COSL

Action: Reset the distributed management card.

Unable to fetch valid data from DM board COSL

Action: Reset the distributed management card.

Unable to get valid data for this slot

Cause: Many pmsd CLI commands can generate this message. The most probable cause is that PMS is having trouble communicating with the hardware or the node boards.

Action: (1) Check network connectivity. (2) Reset the distributed management card. (3) Reboot the node boards.

Unable to perform operation on empty slot/entry

Cause: Many pmsd CLI commands can generate this message.

Action: If you want to use PMS to control the slot, put a board in the slot.

Unable to perform operation on this slot

Cause: Many pmsd CLI commands can generate this message. For example, if you used the pmsd hardware -o reset command on a slot that was empty or not powered on, this message would display.

Action: Compare the command issued and the state of the slot.

Unable to perform operation on this slot/entry

Cause: Several pmsd CLI commands can generate this message.

Action: (1) Make sure the remote distributed management card and the remote node board are operational. (2) Check network connectivity. (3) Check the status of the node board with the pmsd slotrndadderssshow command, and modify if appropriate, with the pmsd slotrndaddersssadd command.

Unable to start CPU board PMS Daemon

Cause: The PMS daemon can't be started on a node board.

Action: (1) Check to see if a PMS daemon is already running on the node board; if there is, stop the daemon and try restarting it. (2) Reboot the node board and try restarting the daemon.

Unable to start DM board PMS Daemon

Cause: May occur after the CLI pmsd start command is used. The PMS daemon can't be started on the distributed management card.

Action: (1) Check to see if a PMS daemon is already running; if there is, stop the daemon and try restarting it. (2) Reset the distributed management card.

Unable to stop CPU board PMS Daemon

Cause: The PMS daemon can't be stopped on the node board.

Action: (1) Check to see if a PMS daemon is already running; if there is, stop the daemon with the command kill process number. (2) Reboot the node board.

Unable to stop DM board PMS Daemon

Cause: May occur after the CLI pmsd stop command is used. The PMS daemon can't be stopped on the distributed management card.

Action: (1) Check to see if a PMS daemon is already running; if there is, stop the daemon with the Chorus command akill process number. (2) Reset the distributed management card.

Unable to write default data to DM board COSL

Action: Reset the distributed management card.