NETXPORTERR messages are returned to $STDLIST when executing the
NETCONTROL command. The NETCONTROL command initiates, terminates,
and controls the operation of the Network Transport subsystem of the links.
MESSAGE: TRANSPORT NOT ACTIVE.
Level: 0001
CAUSE: Issued NETCONTROL STATUS command on inactive
transport.
ACTION: Issue NETCONTROL START.
MESSAGE: DIAG COMMAND NOT SUPPORTED. NETXPORT RUNNING IN UNSUPPORTED
MODE. RESTART NETXPORT TO CLEAR CONDITION.
Level: 0011
CAUSE: The use of the NETCONTROL DIAG command invalidates
Hewlett-Packard support of Network Transport.
ACTION: Do not use the NETCONTROL DIAG command. This
command is reserved for Hewlett-Packard support personnel. Network
Transport must be shut down and restarted to clear the effects of this
command.
MESSAGE: TRANSPORT STATISTICS UNAVAILABLE.
Level: 0020
CAUSE: A call to cache information used by the diagnostic tool has
failed, although the NETCONTROL START command has completed
successfully.
ACTION: Bring down the transport and retry the command. If the
problem persists, see Appendix A "Submitting a CR"
of this manual.
MESSAGE: CONF= OPTION NOT SUPPORTED. NETXPORT RUNNING IN UNSUPPORTED
MODE. RESTART NETXPORT TO CLEAR CONDITION.
Level: 0021
CAUSE: The use of the CONF= option in a NETCONTROL
command invalidates Hewlett-Packard support of the Network Transport.
ACTION: Shutdown the Network Transport and restart it
without using the CONF option.
MESSAGE: X.25 LEVEL 3 DOWN ON DTC FOR DEVICE linkname.
Level: 25
CAUSE: The DTC has lost or was unable to start level 2 and/or
level 3 for the X.25 card specified in the NMCONFIG path
LINK.linkname.
ACTION: No action required. When level 3 is established,
the host will be informed.
Level: 4000
CAUSE: Certain NETCONTROL functions and entities are
mutually exclusive and cannot be combined on the same command line.
Multiples of the same function are not allowed.
ACTION: Check the NS 3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and retry.
MESSAGE: EXPECTED STATUS KEYWORD ALL.
Level: 4002
CAUSE: Typographical error.
ACTION: Type the word ALL after STATUS =.
Correct and retry.
MESSAGE: EXPECTED SEMICOLON.
Level: 4003
CAUSE: Typographical error. There must be a blank between
NETCONTROL and the first entity or function on the command
line. All following entities or functions must be separated by semicolons.
ACTION: Check the NS 3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and retry.
MESSAGE: INVALID NETCONTROL KEYWORD: EXPECTED START STOP, TRACEON,
TRACEOFF, MONON, MONOFF, STATUS, VERSION, NET, GATE, OR NI.
Level: 4004
CAUSE: Only the keywords listed are allowed.
ACTION: Check the NS 3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and retry.
MESSAGE: EXPECTED EQUAL.
Level: 4006
CAUSE: For TRACEON=Type, the type is a required parameter,
one of H,D,M,B,N,S.
ACTION: Check the NS 3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and retry.
MESSAGE: EXPECTED LINK NAME.
Level: 4007
CAUSE: No link name follows the ADDLINK= or
DELLINK= keyword.
ACTION: Reissue the NETCONTROL ADDLINK or DELLINK
command with the appropriate link name.
MESSAGE: KEYWORD SPECIFIED REDUNDANTLY.
Level: 4008
CAUSE: Certain NETCONTROL functions and entities are
mutually exclusive and cannot be combined on the same command line.
Multiples of the same function are not allowed.
ACTION: Check the NS 3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and retry.
MESSAGE: BOTH START AND STOP ISSUED.
Level: 4009
CAUSE: Both parameters not allowed in a single NETCONTROL
command.
ACTION: Pick appropriate command. Correct and
retry.
MESSAGE: INVALID TRACE TYPE. EXPECTED COMBINATION OF D,H,M,B,N,S.
Level: 4011
CAUSE: Usually a typographical error. Recommended combination
for trace type is HMD.
ACTION: Check the NS 3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and retry.
Level: 4012
CAUSE: Usually a typographical error. DEFAULT: Disk.
ACTION: Check the NS 3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and retry.
MESSAGE: INVALID FILE NAME.
Level: 4013
CAUSE: An invalid file name has been supplied with the
NETCONTROL TRACEON option. Usually a typographical error.
ACTION: Check the NS 3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and retry.
MESSAGE: INVALID RECORD SIZE, MUST BE >5 AND 1024.
Level: 4014
CAUSE: Trace file record size specified in command line
parameter is too large or too small.
ACTION: Correct with valid value; retry.
MESSAGE: INVALID FILE SIZE, MUST BE > THAN 32 AND 32000.
Level: 4015
CAUSE: Trace file size specified in command line parameter
is too large or too small.
ACTION: Correct with valid value; retry.
MESSAGE: CONTROL PROCESS NOT STARTED (NMERR= ! ).
Level: 4016
CAUSE: NMMON was unable to launch the Control Process,
or user issued a command when the transport was not active.
ACTION: Issue NETCONTROL START. Then retry command. If
problem persists, see Appendix A "Submitting a CR"
of this manual.
MESSAGE: DATA DICTIONARY FULL, TRY AGAIN.
Level: 4017
CAUSE: Data dictionary full.
ACTION: Reissue the command after waiting a few minutes. If the
problem persists, then see Appendix A
"Submitting a CR" of this manual.
MESSAGE: TRACE OPEN ERROR.
Level: 4021
CAUSE: Usually, you are trying to open a trace on an
already opened trace file.
ACTION: Ensure that the trace file exists and is open. If it
exists and is not open, then see Appendix A "Submitting
a CR" of this manual.
MESSAGE: BAD DIAG VALUE, EXPECTED SET(0-31) OR RST(0-31).
Level: 4023
CAUSE: Invalid DIAG value.
ACTION: The DIAG keyword command is not for customer use.
Contact your Hewlett-Packard representative.
MESSAGE: NET NOT ALLOWED WITH PROT.
Level: 4025
CAUSE: The two entities (NET and PROT) cannot be
used together.
ACTION: Pick appropriate entity and reissue
command.
MESSAGE: EXPECTED VERSION KEYWORD MOD.
Level: 4026
CAUSE: User typed an illegal command.
ACTION: Type word MOD after
VERSION=.
MESSAGE: FOPEN FAILED ON NETMSG.NET.SYS.
Level: 4028
CAUSE: Usually appears with an MPE XL command.
ACTION: Fix the MPE XL error. Ensure that the NETMSG file
exists; if it does, then see Appendix A "Submitting a
CR" of this manual.
MESSAGE: MESSAGE CATALOG ERROR ON NETMSG.NET.SYS.
Level: 4029
CAUSE: Usually appears with an MPE XL command.
ACTION: Fix the MPE XL error. Ensure that the NETMSG file
exists; if it does, then see Appendix A "Submitting
a CR" of this manual.
MESSAGE: GATE &NET FUNCTIONS ENTERED, ONLY ONE ALLOWED.
Level: 4030
CAUSE: The GATE and NET keywords have been
specified on the same NETCONTROL command line.
ACTION: Reissue the NETCONTROL command using only one of
the keywords.
MESSAGE: TRACEON AND TRACEOFF NOT ALLOWED ON SAME LINE.
Level: 4031
CAUSE: The TRACEON and TRACEOFF keywords have
been specified on the same NETCONTROL command line.
ACTION: Reissue the NETCONTROL command using only one of
the keywords.
MESSAGE: NO FUNCTION KEYWORDS ENTERED.
Level: 4033
CAUSE: User typed an illegal command. Specifying an entity
requires a function to act on it.
ACTION: Check NS 3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and retry.
Level: 4040
CAUSE: Network Transport software module version numbers
do not match.
ACTION: Issue the NETCONTROL VERSION=MOD command to see
which numbers do not match, then see Appendix A
"Submitting a CR" of this manual.
MESSAGE: VERSION ERROR: UPDATE NUMBERS DIFFER.
Level: 4041
CAUSE: Network Transport software module version numbers
do not match.
ACTION: Issue the NETCONTROL VERSION=MOD command to see
which numbers do not match, then see Appendix A
"Submitting a CR" of this manual.
MESSAGE: VERSION ERROR: VERSION NUMBERS DIFFER.
Level: 4042
CAUSE: Network Transport software module version numbers
do not match.
ACTION: Issue the NETCONTROL VERSION=MOD command to see
which numbers do not match, then see Appendix A
"Submitting a CR" of this manual.
MESSAGE: VERSION ERROR: MISSING REQUIRED MODULE (S).
Level: 4043
CAUSE: Either missing software module or possible internal error.
ACTION: Issue the NETCONTROL VERSION=MOD command to find
out which module is missing.
MESSAGE: VERSION ERROR: BAD MODULE (S).
Level: 4044
CAUSE: There may be no version stamp; file label may be overwritten, or
possible bad software installation.
ACTION: See Appendix A "Submitting a CR"
of this manual.
MESSAGE: ALREADY STARTED.
Level: 4045
CAUSE:NETCONTROL START command issued for an already
active entity.
ACTION: None.
MESSAGE: NOT STARTED.
Level: 4046
CAUSE: The NETCONTROL STOP command was issued when the
network transport was never running.
ACTION: Check the command for correctness. If it is correct,
no further action is required.
MESSAGE: TOO MANY MESSAGES TO BE DISPLAYED.
Level: 4047
CAUSE: The NETCONTROL error reporting mechanism has
encountered more than 6 errors.
ACTION: Fix the errors displayed and try the command again. If
this error persists, submit and CR. See Appendix A
"Submitting a CR"
MESSAGE: ! PROTOCOL IS NOT ACTIVE.
Level: 4048
CAUSE: Trace issued on an inactive protocol.
ACTION: Check configuration file. All protocols must be
configured.
MESSAGE: THIS COMBINATION OF FUNCTIONS
AND OBJECTS NOT ALLOWED.
Level: 4049
CAUSE: Certain NETCONTROL functions and entities are
mutually exclusive and cannot be combined on the same command line.
Multiples of the same function are not allowed.
ACTION: Check NS 3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and retry.
MESSAGE: niName NOT CONFIGURED.
Level: 4050
CAUSE: The NI named is not configured.
ACTION: Alter the configuration file appropriately, shut
down the transport, and reconfigure.
MESSAGE: NAME LONGER THAN 8 CHARACTERS.
Level: 4051
CAUSE: Usually a command line syntax error.
ACTION: Rename if necessary; retype and retry.
MESSAGE: COMMAND NOT EXECUTED DUE TO VERSION MISMATCH.
Level: 4052
CAUSE: Missing software modules or module version number mismatch.
ACTION: Issue the NETCONTROL VERSION=MOD command for more
information. See Appendix A "Submitting a CR" of
this manual.
MESSAGE: ! DEVICE NOT CONFIGURED.
Level: 4053
CAUSE: The link name specified with the ADDLINK or
DELLINK keyword in the NETCONTROL command line is not
configured.
ACTION: Check the command for correctness. If it appears correct
and the link is configured correctly, see Appendix A
"Submitting a CR" of this manual.
MESSAGE: THE ENTITY IS NOT ACTIVE.
Level: 4054
CAUSE: Issued a NETCONTROL STATUS command on an inactive
entity.
ACTION: None.
MESSAGE: INTERNAL ERROR ON STATUS, TRY AGAIN.
Level: 4055
CAUSE:NETCONTROL STATUS error.
ACTION: Wait and try again; if problem persists, see
Appendix A "Submitting a CR" of this
manual.
MESSAGE: ! DEVICE ALREADY STARTED.
Level: 4056
CAUSE: The link name specified by the NETCONTROL ADDLINK
command has already been started.
ACTION: Check the command for correctness. If it appears
correct, no further action is required.
MESSAGE: ! DEVICE NOT STARTED.
Level: 4057
CAUSE: The link name specified by the NETCONTROL DELLINK
command is already shut down.
ACTION: Check the command for correctness. If it appears
correct, no further action is necessary.
MESSAGE: X25 NOT INSTALLED.
Level: 4058
CAUSE: An attempt was made to start an X25 network when
X25 is not installed on the system.
ACTION: Install X25. If X25 is properly installed then see
"Appendix A "Submitting a CR" of this
manual.
MESSAGE: BAD UPDATE VALUE, EXPECTED INTERNET OR MAPPING.
Level: 4059
CAUSE: Something other than the supported INTERNET or
MAPPING option follows the UPDATE= option in the
NETCONTROL command line.
ACTION: Consult the NS 3000/iX Operations and Maintenance
Reference Manual for the correct syntax for the NETCONTROL
command. Once the syntax has been corrected, retry the
command.
MESSAGE: THIS UPDATE IS NOT ALLOWABLE FOR THIS ENTITY.
Level: 4060
CAUSE: The entity associated with the NETCONTROL UPDATE
command may not be updated.
ACTION: Consult the NS 3000/iX Operations and Maintenance
Reference Manual for the correct syntax for the NETCONTROL
command. Once the syntax has been corrected, retry the
command.
MESSAGE: CONFIGURATION FILE NOT VALID.
Level: 4061
CAUSE: Validation errors occurred on a NETCONTROL START or
UPDATE commands.
ACTION: Correct the invalid parameters in your configuration
file and try again.
MESSAGE: UNABLE TO LOCK CONFIGURATION FILE. (NMERR= error number).
Level: 4062
CAUSE: Unable to lock the configuration file for execution
of a NETCONTROL START or UPDATE.
ACTION: Wait and try again; if problem persists, see
Appendix A "Submitting a CR" of this
manual.
MESSAGE: PROTOCOL START FAILED.
Level: 4063
CAUSE: During a NETCONTROL START one or more of the NI
specific protocols failed to start.
ACTION: Stop the network. Check the configuration of the effected
protocols to be sure that they are correct. Then restart the network. If
the error persists, then see Appendix A "Submitting
a CR" of this manual.
MESSAGE: GENERAL PROTOCOL STARTUP FAILED.
Level: 4064
CAUSE: During a NETCONTROL START one or more of the
general protocols or common modules failed to start. This prevented startup
of any NI-specific protocols. Any further attempts to start networks will
also fail, unless networking is first stopped.
ACTION: Do a netcontrol stop. Check the configuration of the TCP
and IP modules to be sure that they are correct. Then try restarting the
network. If the error persists, see Appendix A
"Submitting a CR" of this manual.
MESSAGE: VERSION ERROR: INTERNAL ERROR (NMERR= error number).
Level: 4100
CAUSE: An internal error occurred while the network transport
was checking its module versions.
ACTION: Review the referenced NMERR elsewhere in this manual.
Confirm that there have been no validation errors with this configuration
file. If the error still occurs, see Appendix A
"Submitting a CR" of this manual.
MESSAGE: TRANSPORT NOT YET DOWN.
Level: 4101
CAUSE: Detected upon issuing a NETCONTROL START command.
The prior NETCONTROL STOP command failed to completely terminate the
Network Transport.
ACTION: Perform the following steps:
Wait a few minutes, then retry the NETCONTROL START command.
If the problem persists, abort any remaining network users.
Level: 4200
CAUSE: Opening the configuration file failed.
ACTION: Confirm that the configuration file
NMCONFIG.PUB.SYS exists and is valid. Retry the NETCONTROL
command.
Level: 4202
CAUSE: Accessing the configuration file returned the
specified error.
ACTION: Review the description of the NMERR referenced elsewhere
in this manual. Confirm that there are no validation errors with the
configuration file. If the error still occurs, restore a backup copy of the
configuration file NMCONFIG.PUB.SYS.
MESSAGE: INTERNAL ERROR ON START.
Level: 4203
CAUSE: A serious internal error has been detected during
the execution of the NETCONTROL START command.
ACTION: SeeAppendix A "Submitting a CR"
of this manual.
MESSAGE: linkname DEVICE STARTUP FAILED.
Level: 4204
CAUSE:
The configured device does not exist on the system.
The link connection is bad due to faulty hardware.
An internal error has occurred during device startup.
ACTION:
Consult the SHERLOCK diagnostics to determine the cause
of the link error. If no link error is indicated, see
Appendix A "Submitting a CR"
of this manual.
Consult the SHERLOCK diagnostics to determine the cause
of the link error. If no link error is indicated, see
Appendix A "Submitting a CR"
of this manual.
Consult the SHERLOCK diagnostics to determine the cause
of the link error. If no link error is indicated, see
Appendix A "Submitting a CR"
of this manual.
MESSAGE: linkName DEVICE IN BOTH ADDLINK AND DELLINK FUNCTIONS.
Level: 4205
CAUSE: The same linkname is the object of both the
ADDLINK and DELLINK option in the NETCONTROL
command above. This is not permitted.
ACTION: Do the ADDLINK and DELLINK on separate
NETCONTROL command lines when the same linkname is used for both
functions.
MESSAGE: HOST — DTC CONFIGURATION MISMATCH FOR DEVICE linkname.
ENSURE HOST NAME IS CONFIGURED ON DTC.
Level: 4206
CAUSE: The host name and/or host link name is not configured
for the DTC name and card number specified with this device.
ACTION: Ensure that the DTC name and card number configured for
this device are correct. Then use the DTC Manager to add the host name and
host link name to the configuration for the appropriate DTC and card number.
Restart the DTC card.
MESSAGE: HOST — DTC VERSION MISMATCH FOR DEVICE linkname.
Level: 4207
CAUSE: The version number of the Remote Link Manager (RLM) on the
host and the version number of MARS on the DTC are incompatible.
ACTION: Ensure that the DTC name configured for this device is
correct. Contact your Hewlett-Packard support engineer to correct the
problem.
MESSAGE: X.25 CARD DOWN ON DTC FOR DEVICE linkname.
Level: 4208
CAUSE: The X.25 code must be downloaded on an X.25 card
on the DTC before the Network Transport attempts to open the link.
ACTION: Ensure that the DTC name and card number configured
for this device are correct. Using the Openview DTC Manager, download X.25
for the appropriate DTC and card.
MESSAGE: X.25 NOT STARTED ON DTC FOR DEVICE linkname.
Level: 4209
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.
MESSAGE: HOST LOST CONTACT WITH DTC FOR DEVICE linkname.
Level: 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.
Level: 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".
Level: 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".
Level: 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".
Level: 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".
Level: 4215
CAUSE: The path LINK.linkname was created in
NMCONFIG.PUB.SYS, but the DTC name was not added.
ACTION: Using NMMGR, update the path and validate the DTS
subsystem.
MESSAGE: CANNOT FIND DTC CONFIGURED FOR DEVICE linkname.
Level: 4216
CAUSE: This error may be caused by one of the following reasons:
The host has a non-existent DTC configured in the
NMCONFIG.PUB.SYS path LINK.linkname.
The DTC configured in the NMCONFIG.PUB.SYS path
LINK.linkname is down or flooded.
ACTION: Check the configuration data and verify that it is correct.
Restart the DTC if necessary.
MESSAGE: MAXIMUM X.25 LINKS ALREADY STARTED, CANNOT START DEVICE linkname.
Level: 4217
CAUSE: Too many X.25 links have been started on the host.
ACTION: Stop unused X.25 links or Network
Interfaces.
MESSAGE: CANNOT OPEN NETWORK DIRECTORY FILE.
Level: 4218
CAUSE: NETCP was unable to open the file NSDIR.NET.SYS.
ACTION: Check to be sure that the files NSDIR.NET.SYS and
NSDIRK.NET.SYS exist. If they exist and they are not being
accessed by another process, then try recreating the files. Otherwise, see
Appendix A "Submitting a CR" of this
manual.
Complete PDF