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

498 Chapter21
Logging Location Codes
Control Process Logging Location Codes
asynchronous DCLDM event message indicating its LAPB PSI link
reported another failure (PARM = upper 16 bits of status from the call
to xp_connect_the_driver: usually the connect event code from
LAPB).
ACTION: NETCP disconnected the device and notified protocols that the
link went down. This is most likely a link level problem. Consult the
link diagnostics and check the modems. Confirm that the link
connection is working for the affected link. If the link is connection is
working, then see Appendix A , “Submitting a CR,” of this manual.
313 CLAS0003 MESSAGE: INTERNAL ERROR; Dial
CAUSE: While restarting a LAPB PSI link because an unexpected error
occurred while connected (see error 257), NETCP encountered an error
when it instructed the local side to reestablish a level 1 connection so
that a level 2 connection can be established later (PARM = 32-bit status
returned by the call to xp_connect_the_driver).
ACTION: NETCP brought the device and its driver down, and notified
protocols that the link went down. This is most likely a link level
problem. Another possibility is that the DCLDM or LAPB driver are
hung. Consult the link diagnostics and check the modems. Confirm that
the link connection is working for the affected link. If the link is
connection is working, then see Appendix A , “Submitting a CR,” of this
manual.
315 CLAS0003 MESSAGE: INTERNAL ERROR; Dial
CAUSE: While processing a legal dial request message, NETCP found
that the link appeared to already be connected, so dialing was not
possible (PARM = adjusted LAPB status).
ACTION: None. This is an informative error message only. Another
class-3 logging message may have preceded this, indicating that the
link just connected.
316 CLAS0003 MESSAGE: INTERNAL ERROR; Dial
CAUSE: NETCP received a legal dial request message but encountered
an error while downloading the phone number to the link (PARM =
32-bit status returned by the call to xp_driver_config_dial).
ACTION: This event may follow a previous asynchronous link error,
which may indicate the original problem. Another possibility is that the
DCLDM or LAPB driver are hung. Also check the validity of the phone
number in the configuration. If the situation continues, additional
information may be gained by enabling logging classes 10 and 12 for
link subsystem 28 (LAPB), and class 0 for subsystem 4 (DCLDM). If
this still does not reveal the problem, see Appendix A , “Submitting a
CR,” of this manual.
CAUSE: NETCP received a legal dial request message but encountered
an error while trying to establish a level 2 connection at the LAPB