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

138 Chapter14
VALERR and VALWARN Messages
ACTION: Use NMMGR to change the configuration file so that at least
one NETXPORT.NI.NIname.LINK.linkname record exists for this
network. Validate the Network Transport again.
MESSAGE: NO PHONE NUMBER REQUIRED FOR DC LINK.
108 CAUSE: Phone data has been erroneously configured for a direct
connect link.
ACTION: Delete the phone data, or correct the link type.
MESSAGE: LOOPBACK ONLY CONFIGURATION NOT ALLOWED.
109 CAUSE: Loopback is the only NI configured.
ACTION: Use NMMGR to add NIs for LAN or router networks and
validate the Network Transport again.
MESSAGE: LINK TYPE MUST BE X.25 IN LINK CONFIGURATION.
110 CAUSE: The link specified in the
NETXPORT.NI.NIname.LINK.linkname is not configured as an X.25
link.
ACTION: Use NMMGR to change the link type in LINK.linkname to
an X.25, or create a new link of type X.25 and associate it with this
NIname. Validate the network transport configuration again.
MESSAGE: MUST CONFIGURE A NODE NAME.
111 CAUSE: There is no node name configured under the NODENAME path.
ACTION: Use NMMGR to configure a local node name under the
NODENAME path.
MESSAGE: NOT A VALID LOGGING CLASS FOR SUBSYSTEM 40.
112 CAUSE: A class other than CLAS0000, CLAS0001, CLAS0002,
CLAS0003, CLAS0004, or CLAS0005 has been configured as a logging
class for subsystem 40 (remote link manager).
ACTION: Use NMMGR to change the configuration file so that only
valid classes are configured. Validate the network transport
configuration again.
MESSAGE: SUBSYSTEM 40 LOGGING NOT CONFIGURED.
113 CAUSE: The LOGGING.SUB0040 record does not exist in the
configuration file.
ACTION: Use NMMGR and go to the LOGGING screens to add the
LOGGING.SUB0040 record to the configuration. Logging classes 0000
through 0005 should also be added to the configuration so that logging
is completely configured for Remote Link Management.