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

Chapter 19 351
Logging Location Codes
Control Process Logging Location Codes
ACTION: This error in itself was not fatal, and NETCP continued
operating. Some kind of timing condition may have occurred. Another
possibility is NETCP or a DCLDM may be confused. If the problem
occurs repeatedly, see Appendix A, “Submitting an SR,” of this manual.
MESSAGE: INTERNAL ERROR; Async request from link
416 CLAS0002 CAUSE: NETCP received an asynchronous SDI event message, but the
specific type of event was something other than an exception event, the
only message type NETCP was expecting (PARM = 32-bit SDI status
field from the message).
ACTION: This error in itself was not fatal, and NETCP continued
operating. However, some other modules on the system may still be
waiting for the event message that mistakenly went to NETCP, and
this could cause problems in those other modules. If disc logging was
enabled, NETCP logged the entire received message to the current NM
logfile, which may aid in diagnosis. If necessary, see Appendix A,
“Submitting an SR,” of this manual.
MESSAGE: Level 3 Up on DTC
417 CLAS0003 CAUSE: NETCP received an SDI asynchronous event message from
X25 informing it that a level 3 connection has been established on a
DTC for an X25 link already started by the Transport (PARM = 32-bit
SDI status field from the message).
ACTION: None. This is an informational message only. NETCP has
connected the device, and Transport will now begin using this link.
MESSAGE: INTERNAL ERROR; Async request from link
418 CLAS0003 CAUSE: NETCP received an SDI asynchronous event message
informing it that an X25 device reported an error (PARM = 32-bit SDI
status field from the message).
ACTION: NETCP will bring down the X25 device and its driver, then
start a 2-minute automatic restart timer. If the problem occurs
repeatedly, stop the network or use the :NETCONTROL
DELLINK=linkname; NET=niname command to remove the DTC link
from Transport use. Verify that the DTC LAN link on the host is
functioning correctly (via LANDAD) then verify that the link on the
DTC is functioning correctly (via the Openview DTC Manager). Once
the errors are corrected, restart the network or use a :NETCONTROL
ADDLINK=linkname; NET=niname command to allow the Transport
to use the DTC link again.
MESSAGE: INTERNAL ERROR; Device open
419 CLAS0002 CAUSE: While starting an 802.3 LAN device prior to opening its driver,
NETCP encountered an error attempting to add multicast addresses to
the driver’s KSO (PARM = 32-bit status returned by the call to
ieee_multicast_add).