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

Chapter 12 125
NETXPORTERR Error Messages
4209 MESSAGE: X.25 NOT STARTED ON DTC FOR DEVICE linkname.
CAUSE: The X.25 card on the DTC was reset, but X.25 was not
restarted.
ACTION: Ensure that the DTC name and card number configured for
this device are correct. Using the Openview DTC Manager, start X.25
for the appropriate DTC and card.
4210 MESSAGE: HOST LOST CONTACT WITH DTC FOR DEVICE linkname.
CAUSE: The control connection between the host and the DTC was lost.
ACTION: Verify that the DTC configured for this device is still
functioning.
4211 MESSAGE: INVALID CARD NUMBER FOR DTC FOR DEVICE
linkname.
CAUSE: This error could occur for one of the following reasons:
• The card number specified does not exist on the DTC.
• The card number specified is not an X.25 card.
• The card number specified has not been configured using the
Openview DTC Manager.
ACTION: Ensure that the DTC name and card number configured for
this device are correct. Using the Openview DTC Manager, configure
and start X.25 for the appropriate DTC and card.
4212 MESSAGE: COULD NOT GET DATA FROM NMCONFIG PATH
“DTS.DTCPC”.
CAUSE: The path DTS.DTC was created, but no data was added.
ACTION: Using NMMGR, update the path and validate the DTS
subsystem.
4213 MESSAGE: LAN LINK NAME NOT CONFIGURED IN NMCONFIG PATH
“DTS.DTCPC”.
CAUSE: The path DTS.DTC was created in NMCONFIG.PUB.SYS, but the
IEEE 802.3 link name was not added.
ACTION: Using NMMGR, update the path and validate the DTS
subsystem.
4214 MESSAGE: COULD NOT GET DATA FROM NMCONFIG PATH
“LINK.linkname”.
CAUSE: The path LINK.linkname was created in NMCONFIG.PUB.SYS,
but no data was added.
ACTION: Using NMMGR, update the path and validate the DTS
subsystem.