Sun Microsystems Netra CT 820 Administration Manual page 86

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.
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 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.
72 Netra CT 820 Server System Administration Guide • March 2004