Sun Microsystems Netra CT 820 Administration Manual page 87

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
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 fetch valid data from 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 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.
Appendix B Error Messages from the PMS Application 73