HP 3000 Manuals HP 3000 Manuals
DC/LDM Logging Location Codes
DC/LDM (Data Comm Logical Device Manager) is a module between
NS Transport and the LAP-B Driver, which helps provide NS over
point-to-point Router networks.
2 CLAS0000 Message: Send_msg error
Cause: While DC/LDM was attempting to send a message
to another module, for some normal purpose (other than
an error reply), the system routine send_msg reported
an error.
Action: No message was sent. DC/LDM is now "sick"
and cannot continue operating. An asynchronous error
message was sent to all modules to which DC/LDM was
bound. See "Submitting an SR" in appendix A of this
manual.
4 CLAS0000 Message: A connect event has been received from the
lower manager
Cause: This is not an error. DC/LDM received a
connect-completion event message from one of the lower
level drivers bound to it. This logs the fact the
link is now connected.
Action: No action required. An asynchronous event
message was sent to all modules to which DC/LDM was
bound.
12 CLAS0000 Message: Unable to obtain a message frame from target
pool
Cause: While DC/LDM was attempting to get a message
frame from another port, for use as an event or reply
message, the system routine get_ msg_ frame reported
an error.
Action: DC/LDM is now "sick" and cannot continue
operating. No message frame was obtained. See
"Submitting an SR" in appendix A of this manual.
15 CLAS0000 Message: Write request is invalid in current state
Cause: A write event was invalid, or DC/LDM is sick,
and a Compatibility mode write request was being
worked on. Since that write cannot be completed,
DC/LDM notifies the CM sender, and logs the original
error.
Action: See "Submitting an SR" in appendix A of this
manual.
16 CLAS0000 Message: Send_msg error while issuing CM reply
Cause: During error processing of an invalid write
event, DC/LDM encountered another error while trying
to send the Compatibility mode error reply message
back to the requester, when the system routine
send_msg reported an error.
Action: No message was sent, so the CM module may not
be aware any problem has occurred. This may affect
other operations on the network. See "Submitting an
SR" in appendix A of this manual.
17 CLAS0000 Message: Invalid CM request received in current state
Cause: During error processing of an invalid write
event, DC/LDM discovered the message it was working on
was not a write event message.
Action: The message should have been a write event,
so this indicates an internal bug in DC/LDM. See
"Submitting an SR" in appendix A of this manual.
18 CLAS0000 Message: Send_msg error while issuing NM reply
Cause: While attempting to send an error reply
message back to the sender of an earlier Native mode
trace request or HLIO request, the system routine
send_msg reported an error.
Action: No message was sent, so the sender may not be
aware any problem has occurred. This may affect other
operations on the network. DC/LDM is still operating.
See "Submitting an SR" in appendix A of this manual.
19 CLAS0000 Message: Invalid NM request received in current state
Cause: In attempting to send an error reply message
for an earlier HLIO request, DC/LDM hit a bug because
that request was not understood by the code which
sends the replies.
Action: The request should have been understood, so
this indicates an internal bug in DC/LDM. No message
was sent, so the sender may not be aware any problem
has occurred. This may affect other operations on the
network. DC/LDM is still operating. See "Submitting
an SR" in appendix A of this manual.
20 CLAS0000 Message: Invalid event received in current state
Cause: An invalid event message was received by
DC/LDM. Events cannot be replied to, but this logs the
bad state DC/LDM was in at the time the event was
received.
Action: If this was a read event, its buffer was
freed; otherwise the event message was ignored.
DC/LDM is still operating. See "Submitting an SR" in
appendix A of this manual.
22 CLAS0000 Message: Error in releasing CM request write buffer
Cause: During error processing of an invalid write
event, DC/LDM encountered another error while trying
to free the BMGR buffer referenced by the bad write
request message, but the system routine
bmgr_free_buffer reported an error.
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 "Submitting an SR" in appendix A of
this manual.
23 CLAS0000 Message: Error in releasing write buffer in current
state
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 "Submitting an SR" in appendix A of this
manual.
24 CLAS0000 Message: Internal error - invalid state
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 "Submitting an SR" in appendix A
of this manual.
25 CLAS0000 Message: Invalid message was received and discarded
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 "Submitting an SR"
in appendix A of this manual.
27 CLAS0000 Message: Insufficient frames for inbound packets -
packet discarded
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.
33 CLAS0000 Message: Asynchronous error event received from lower
manager
Cause: DC/LDM received a fatal error notification
event message from a lower level LAN or LAP-B driver.
This logs the error status reported by that driver.
Action: DC/LDM is still operating, but the driver is
probably not. It has flushed (replied to) any pending
requests for the link which reported the error. An
asynchronous error message was sent to all modules to
which DC/LDM was bound. See "Submitting an SR" in
appendix A of this manual.
34 CLAS0000 Message: Asynchronous warning event received from
lower manager
Cause: DC/LDM received a nonfatal asynchronous
warning event message from a lower level LAN or LAP-B
driver. This logs the status reported by that driver.
Action: An asynchronous event message was sent to all
modules to which DC/LDM was bound. DC/LDM is still
operating, but the driver may be having problems. No
action required.
37 CLAS0000 Message: Port error while obtaining message for
inbound packet
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 an error other than a
lack of message frames.
Action: No message frame was obtained. The inbound
packet was dropped. DC/LDM is now "sick" and cannot
continue operating. See "Submitting an SR" in
appendix A of this manual.
38 CLAS0000 Message: Write sap is invalid
Cause: While processing a write request message from
NI, DC/LDM discovered the SAP to write to had not yet
been opened, but there was no reply port in the
message to notify about this situation.
Action: DC/LDM is still operating. The buffer in the
write message was freed, but since the reply port
number was unknown, no reply message was sent. This
may or may not affect operations on the network or the
application. If this problem persists, see
"Submitting an SR" in appendix A of this manual.
39 CLAS0000 Message: Error encountered during removal of DC/LDM
Cause 1: While stopping the DC/LDM, an error occurred
when deleting a CM Port Dictionary entry or HLIO
device, when releasing a device, or because of a bad
DC/LDM state.
Action 1: DC/LDM continued stopping, but this could
indicate a more serious problem in the High Level I/O
system or the DC/LDM. If the problem occurs every
time, see "Submitting an SR" in appendix A of this
manual.
Cause 2: While flushing its port subqueues, DC/LDM
found an I/O request message on its port having a
nonzero buffer ID, but when trying to free the BMGR
buffer referenced by that message, the system routine
bmgr_free_buffer reported an error.
Action 2: DC/LDM will continue stopping, but if this
situation continues, the network may run out of
buffers. In addition, any subsequent network shutdown
may hang. See "Submitting an SR" in appendix A of
this manual.
40 CLAS0000 Message: Error encountered in configurator module
Cause 1: While starting the DC/LDM, an error occurred
when adding a CM Port Dictionary entry, reading the
LSS link table, loading a manager plabel, allocating
an HLIO device, creating an LDM port, adding a device,
sending a message, or changing a port subqueue.
Action 1: DC/LDM did not start. See "Submitting an
SR" in appendix A of this manual.
Cause 2: While stopping the DC/LDM, an error occurred
when deleting a CM Port Dictionary entry or HLIO
device, when releasing a device, or because of a bad
DC/LDM state.
Action 2: DC/LDM continued stopping, but this could
indicate a more serious problem in the High Level I/O
system or the DC/LDM. If the problem occurs every
time, see "Submitting an SR" in appendix A of this
manual.
Cause 3: While flushing its port subqueues, DC/LDM
found a read event message on its port having a
nonzero buffer ID, but when trying to free the BMGR
buffer referenced by that message, the system routine
bmgr_free_buffer reported an error.
Action 3: 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 "Submitting an SR" in appendix A of
this manual.