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

Chapter 12 125
NETXPORTERR Error Messages
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.
MESSAGE: HOST LOST CONTACT WITH DTC FOR DEVICE linkname.
4210 CAUSE: The control connection between the host and the DTC was lost.
ACTION: Verify that the DTC configured for this device is still
functioning.
MESSAGE: INVALID CARD NUMBER FOR DTC FOR DEVICE
linkname.
4211 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.
MESSAGE: COULD NOT GET DATA FROM NMCONFIG PATH
“DTS.DTCPC”.
4212 CAUSE: The path DTS.DTC was created, but no data was added.
ACTION: Using NMMGR, update the path and validate the DTS
subsystem.
MESSAGE: LAN LINK NAME NOT CONFIGURED IN NMCONFIG PATH
“DTS.DTCPC”.
4213 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.
MESSAGE: COULD NOT GET DATA FROM NMCONFIG PATH
“LINK.linkname”.
4214 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.
MESSAGE: DTC NAME NOT CONFIGURED IN NMCONFIG PATH
“LINK.linkname”.
4215 CAUSE: The path LINK.linkname was created in NMCONFIG.PUB.SYS,
but the DTC name was not added.