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

340 Chapter19
Logging Location Codes
Control Process Logging Location Codes
the phone system; additional information may be gained by enabling
logging classes 10 and 12 for link subsystem 28 (LAPB) and class 0 for
subsystem 4 (DCLDM).
MESSAGE: INBOUND; Device connected
258 CLAS0003 CAUSE: NETCP received an asynchronous event message from the
DCLDM indicating that its LAPB PSI link has established a level 2
connection (PARM = 16-bit internal ldev number of the device).
ACTION: None. This is an informative message only. The LAPB link is
now successfully engaged in protocol handshaking, and will stay up
unless an error, disconnect, or idle timeout occurs, or the network is
stopped.
MESSAGE: INBOUND; Device disconnected
259 CLAS0003 CAUSE: NETCP received an asynchronous event message from the
DCLDM indicating that its LAPB PSI link was disconnected by its
remote side (PARM = 0). May be followed by informative error 101 if
outbound data was queued when the error occurred.
ACTION: None. This is an informative error message only. NETCP will
now tell the driver on the local side to disconnect, so informative error
257 should follow.
MESSAGE: PACKET DISCARD; Illegal phone number
260 CLAS0002 CAUSE: NETCP received an asynchronous event message from the
DCLDM indicating that its LAPB driver had some problem handling a
phone number change request (PARM = 32-bit NETCP device state
bitmask for the device).
ACTION: This error may be related to the syntax or length of the phone
number, but could also be caused by some internal problem. Use
NMMGR to check the syntax of the telephone number in the
NMCONFIG file for the affected link. Then attempt a :NETCONTROL
ADDLINK=linkname; NET=niname command. If the error persists, see
Appendix A, “Submitting an SR,” of this manual.
MESSAGE: INBOUND; Device disconnected
261 CLAS0002 CAUSE: NETCP received an asynchronous event message from the
DCLDM indicating that closing its LAPB PSI link failed (PARM =
16-bit internal ldev number of the device). NETCP will attempt to bring
down the device and its driver. May be followed by informative error
101 if outbound data was queued when the error occurred.
ACTION: See Appendix A, “Submitting an SR,” of this manual.