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

490 Chapter21
Logging Location Codes
Control Process Logging Location Codes
254 CLAS0002 MESSAGE: INTERNAL ERROR; Configuration file error
CAUSE: NETCP tried to search the NMCONFIG file to determine if an
NI having a specific name was configured or not, but was unable to open
the file (PARM = 32-bit status returned by the call to nmconfopen).
ACTION: Check that the NMCONFIG file exists and is not already
opened by some other user, such as a STORE process or someone
running NMMGR. If this is not the problem, there may be a bug in the
NMS subsystem or in NETCP; see Appendix A , “Submitting a CR,” of
this manual.
256 CLAS0002 MESSAGE: INBOUND; Device disconnected
CAUSE: NETCP received an asynchronous event message from the
DCLDM indicating that its LAPB PSI link was disconnected (PARM =
32-bit NETCP device state bitmask for the device). NETCP will not
attempt to reconnect the device because it appears neither level 1 nor
level 2 connections were established when this event occurred. May be
followed by informative error 101 if outbound data was queued when
the error occurred.
ACTION: This error may follow a previous asynchronous link error,
which may indicate an earlier problem. Additional information may be
gained by enabling logging classes 3 for Transport subsystem 3, 10 and
12 for link subsystem 28 (LAPB) and class 0 for subsystem 4 (DCLDM),
then reproducing the problem. It may be possible to manually restart
the device using a :NETCONTROL ADDLINK=linkname; NET=niname
command. If the problem persists, see Appendix A , “Submitting a CR,”
of this manual.
257 CLAS0003 MESSAGE: INBOUND; Device disconnected
CAUSE: NETCP received an asynchronous event message from the
DCLDM indicating that its LAPB PSI link was closed (PARM = 16-bit
internal ldev number of the device). NETCP will attempt to reconnect
the device because it appears either level 1 or level 2 connections, or
both, were established when the event occurred. 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. The link will
reconnect automatically unless error 256 appears. This event may
follow a previous asynchronous link error, which may indicate an
earlier problem. If the situation continues, there may be a problem with
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).
258 CLAS0003 MESSAGE: INBOUND; Device connected
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).