NS3000/iX Error Messages Reference Manual (36923-90041)

392 Chapter19
Logging Location Codes
DC/LDM Logging Location Codes
ACTION: DC/LDM will continue operating, but if this situation
continues, the network may run out of buffers. In addition, any
subsequent network shutdown may hang. See Appendix A, “Submitting
an SR,” of this manual.
MESSAGE: Error in releasing write buffer in current state
23 CLAS0000 CAUSE: Upon entering into a “sick” state because of some other
problem, DC/LDM attempted to clean up after the last message it
received, in this case a read event message, but in trying to free the
buffer in that message, the system routine bmgr_free_buffer
reported an error.
ACTION: DC/LDM is in a “sick” state and cannot continue operating. In
addition, one buffer may have been lost, so any subsequent network
shutdown may hang. See Appendix A, “Submitting an SR,” of this
manual.
MESSAGE: Internal error—invalid state
24 CLAS0000 CAUSE: After receiving a message instructing it to do something, and
figuring out what that message was, DC/LDM discovered its current
state was not a known state.
ACTION: DC/LDM is now “sick” and cannot continue operating;
probably its context memory has somehow been overwritten. DC/LDM
also attempted to send an asynchronous error message to all modules to
which it was bound, but if the context was indeed corrupt, these may
not have been sent. Immediately take a memory dump and see
Appendix A, “Submitting an SR,” of this manual
MESSAGE: Invalid message was received and discarded
25 CLAS0000 CAUSE: DC/LDM received an input message which it did not
understand at all, and could not process.
ACTION: The input message was ignored, and DC/LDM is still
operating. However, whichever module sent the bad message sent it to
the wrong place, so there is a problem in that other module. See
Appendix A, “Submitting an SR,” of this manual.
MESSAGE: Insufficient frames for inbound packets—packet
discarded
27 CLAS0000 CAUSE: While processing a read event message from a lower level
driver, DC/LDM attempted to get a message frame from the upper level
NI port, but the system routine get_msg_frame reported there were
no message frames available.
ACTION: No message frame was obtained. DC/LDM is still operating,
but the system is probably under a very heavy load. The inbound packet
was dropped by DC/LDM, and the remote will probably retransmit it
later. No action is required.