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

Chapter 21 531
Logging Location Codes
Control Process Logging Location Codes
691 CLAS0002 MESSAGE: INTERNAL ERROR; No DEVS
CAUSE: While starting an X.25 network due to a :NETCONTROL START
command, or while updating it due to a :NETCONTROL UPDATE
command, NETCP found that none of the X.25 address keys in the
Network Directory file matched any keys in the NMCONFIG file’s SVC
or PVC configurations for that X.25 network (PARM = 0).
ACTION: This error in itself was not fatal, and startup continued.
However, outbound connections cannot be initiated using this X.25
network. Stop the network and use NMMGR to ensure the address keys
in the “Additional Address” field of X.25 Network Directory entries
match “X.25 Address Key” fields in the
NETXPORT.NI.name.PROTOCOL.X25.SVCPATH (or PVCPATH) screens of
the NMCONFIG file. If this does not solve the problem, see Appendix
A , “Submitting a CR,” of this manual.
751 CLAS0003 MESSAGE: INBOUND; Device connected.
CAUSE: NETCP received a connect event and subsequently the LAPB
device for which the connect event was received has been connected.
ACTION: None. This is an informative message only.
758 CLAS0002 MESSAGE: Bad status
CAUSE: NETCP encountered an error while sending a disconnect
message to LAPBMUX driver.
ACTION: NETCP will fail to properly stop the network and/or the driver.
But this may not affect other networks on the system. Try to restart the
network and if it fails, see Appendix A , “Submitting a CR.”
759 CLAS0002 MESSAGE: Receive mag failed
CAUSE: NETCP had sent a disconnect request message but didn’t get a
reply message for more than 30 seconds from the LAPBMUX driver.
ACTION: NETCP may fail to properly stop the network and/or the
driver. But this may not affect other networks on the system. Try to
restart the network and if it fails, see Appendix A , “Submitting a CR.”
760 CLAS0002 MESSAGE: INTERNAL ERROR; Bad/unknown port message
CAUSE: NETCP had sent a disconnect request and was expecting a
disconnect reply message from the LAPBMUX link driver but received
a message which was not a disconnect reply.
ACTION: NETCP may fail to properly stop the network and/or the
driver. But this may not affect other networks on the system. Try to
restart the network and if it fails, see Appendix A , “Submitting a CR.”
761 CLAS0002 MESSAGE: INTERNAL ERROR; Device disconnect failed
CAUSE: NETCP had received a disconnect reply message for its
previous disconnect request but LAPPMUX link driver has sent a bad