HP 3000 Manuals HP 3000 Manuals
Chapter 12 NETXPORTERR Error Messages
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.
0001 MESSAGE TRANSPORT NOT ACTIVE.
CAUSE Issued NETCONTROL STATUS command on inactive
transport.
ACTION Issue NETCONTROL START.
0011 MESSAGE DIAG COMMAND NOT SUPPORTED. NETXPORT RUNNING IN
UNSUPPORTED MODE. RESTART NETXPORT TO CLEAR
CONDITION.
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.
0020 MESSAGE TRANSPORT STATISTICS UNAVAILABLE.
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 "Submitting an SR"
in appendix A of this manual.
0021 MESSAGE CONF= OPTION NOT SUPPORTED. NETXPORT RUNNING IN
UNSUPPORTED MODE. RESTART NETXPORT TO CLEAR
CONDITION.
CAUSE The use of the CONF= option in a NETCONTROL
command invalidates Hewlett- Packard support of
the Network Transport.
ACTION Shut down the Network Transport and restart it
without using the CONF option.
25 MESSAGE X.25 LEVEL 3 DOWN ON DTC FOR DEVICE linkname.
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.
2000 MESSAGE TRACE FILE IS !.
CAUSE Informative message.
ACTION None.
4000 MESSAGE TOO MANY PARMS IN COMMAND LINE.
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 NS3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and
retry.
4002 MESSAGE EXPECTED STATUS KEYWORD ALL.
CAUSE Typographical error.
ACTION Type the word ALL after STATUS =. Correct and
retry.
4003 MESSAGE EXPECTED SEMICOLON.
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 NS3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and
retry.
4004 MESSAGE INVALID NETCONTROL KEYWORD: EXPECTED START STOP,
TRACEON, TRACEOFF, MONON, MONOFF, STATUS,
VERSION, NET, GATE, OR NI.
CAUSE Only the keywords listed are allowed.
ACTION Check the NS3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and
retry.
4006 MESSAGE EXPECTED EQUAL.
CAUSE For TRACEON=Type, the type is a required
parameter, one of H,D,M,B,N,S.
ACTION Check the NS3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and
retry.
4007 MESSAGE EXPECTED LINK NAME.
CAUSE No link name follows the ADDLINK= or DELLINK=
keyword.
ACTION Reissue the NETCONTROL ADDLINK or DELLINK
command with the appropriate link name.
4008 MESSAGE KEYWORD SPECIFIED REDUNDANTLY.
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 NS3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and
retry.
4009 MESSAGE BOTH START AND STOP ISSUED.
CAUSE Both parameters not allowed in a single
NETCONTROL command.
ACTION Pick appropriate command. Correct and retry.
4011 MESSAGE INVALID TRACE TYPE. EXPECTED COMBINATION OF
D,H,M,B,N,S.
CAUSE Usually a typographical error. Recommended
combination for trace type is HMD.
ACTION Check the NS3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and
retry.
4012 MESSAGE INVALID TRACE DESTINATION. EXPECTED DISC.
CAUSE Usually a typographical error. DEFAULT: Disc.
ACTION Check the NS3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and
retry.
4013 MESSAGE INVALID FILE NAME.
CAUSE An invalid file name has been supplied with the
NETCONTROL TRACEON option. Usually a
typographical error.
ACTION Check the NS3000/iX Operations and Maintenance
Reference Manual for proper syntax. Ensure file
exists. Correct and retry.
4014 MESSAGE INVALID RECORD SIZE, MUST BE >5 AND <1024.
CAUSE Trace file record size specified in command line
parameter is too large or too small.
ACTION Correct with valid value; retry.
4015 MESSAGE INVALID FILE SIZE, MUST BE > THAN 32 AND <
32000.
CAUSE Trace file size specified in command line
parameter is too large or too small.
ACTION Correct with valid value; retry.
4016 MESSAGE CONTROL PROCESS NOT STARTED (NMERR= ! ).
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 "Submitting an SR" in
appendix A of this manual.
4017 MESSAGE DATA DICTIONARY FULL, TRY AGAIN.
CAUSE Data dictionary full.
ACTION Reissue the command after waiting a few minutes.
If the problem persists, then see "Submitting an
SR" in appendix A of this manual.
4021 MESSAGE TRACE OPEN ERROR.
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
"Submitting an SR" in appendix A of this manual.
4023 MESSAGE BAD DIAG VALUE, EXPECTED SET(0-31) OR RST(0-31).
CAUSE Invalid DIAG value.
ACTION The DIAG keyword command is not for customer
use. Contact your Hewlett-Packard
representative.
4025 MESSAGE NET NOT ALLOWED WITH PROT.
CAUSE The two entities (NET and PROT) cannot be used
together.
ACTION Pick appropriate entity and reissue command.
4026 MESSAGE EXPECTED VERSION KEYWORD MOD.
CAUSE User typed an illegal command.
ACTION Type word MOD after VERSION=.
4028 MESSAGE FOPEN FAILED ON NETMSG.NET.SYS.
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 "Submitting an
SR" in appendix A of this manual.
4029 MESSAGE MESSAGE CATALOG ERROR ON NETMSG.NET.SYS.
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 "Submitting an
SR" in appendix A of this manual.
4030 MESSAGE GATE & NET FUNCTIONS ENTERED, ONLY ONE ALLOWED.
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.
4031 MESSAGE TRACEON AND TRACEOFF NOT ALLOWED ON SAME LINE.
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.
4033 MESSAGE NO FUNCTION KEYWORDS ENTERED.
CAUSE User typed an illegal command. Specifying an
entity requires a function to act on it.
ACTION Check NS3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and
retry.
4034 MESSAGE TRACE PREVIOUSLY ENABLED.
CAUSE Informative message.
ACTION None.
4035 MESSAGE ENTITY WAS NOT TRACING.
CAUSE Informative message.
ACTION None.
4040 MESSAGE VERSION ERROR: FIX NUMBERS DIFFER.
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 "Submitting
an SR" in appendix A of this manual.
4041 MESSAGE VERSION ERROR: UPDATE NUMBERS DIFFER.
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 "Submitting
an SR" in appendix A of this manual.
4042 MESSAGE VERSION ERROR: VERSION NUMBERS DIFFER.
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 "Submitting
an SR" in appendix A of this manual.
4043 MESSAGE VERSION ERROR: MISSING REQUIRED MODULE (S).
CAUSE Either missing software module or possible
internal error.
ACTION Issue the NETCONTROL VERSION=MOD command to find
out which module is missing.
4044 MESSAGE VERSION ERROR: BAD MODULE (S).
CAUSE There may be no version stamp; file label may be
overwritten, or possible bad software
installation.
ACTION See "Submitting an SR" in appendix A of this
manual.
4045 MESSAGE ALREADY STARTED.
CAUSE NETCONTROL START command issued for an already
active entity.
ACTION None.
4046 MESSAGE NOT STARTED.
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.
4047 MESSAGE TOO MANY MESSAGES TO BE DISPLAYED.
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 SR.
See "Submitting an SR" in appendix A of this
manual.
4048 MESSAGE ! PROTOCOL IS NOT ACTIVE.
CAUSE Trace issued on an inactive protocol.
ACTION Check configuration file. All protocols must be
configured.
4049 MESSAGE THIS COMBINATION OF FUNCTIONS AND OBJECTS NOT
ALLOWED.
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 NS3000/iX Operations and Maintenance
Reference Manual for proper syntax. Correct and
retry.
4050 MESSAGE niName NOT CONFIGURED.
CAUSE The NI named is not configured.
ACTION Alter the configuration file appropriately, shut
down the transport, and reconfigure.
4051 MESSAGE NAME LONGER THAN 8 CHARACTERS.
CAUSE Usually a command line syntax error.
ACTION Rename if necessary; retype and retry.
4052 MESSAGE COMMAND NOT EXECUTED DUE TO VERSION MISMATCH.
CAUSE Missing software modules or module version
number mismatch.
ACTION Issue the NETCONTROL VERSION=MOD command for
more information. See "Submitting an SR" in
appendix A of this manual.
4053 MESSAGE ! DEVICE NOT CONFIGURED.
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 "Submitting an SR" in appendix A
of this manual.
4054 MESSAGE THE ENTITY IS NOT ACTIVE.
CAUSE Issued a NETCONTROL STATUS command on an
inactive entity.
ACTION None.
4055 MESSAGE INTERNAL ERROR ON STATUS, TRY AGAIN.
CAUSE NETCONTROL STATUS error.
ACTION Wait and try again; if problem persists, see
"Submitting an SR" in appendix A of this manual.
4056 MESSAGE ! DEVICE ALREADY STARTED.
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.
4057 MESSAGE ! DEVICE NOT STARTED.
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.
4058 MESSAGE X25 NOT INSTALLED.
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 "Submitting an SR" in appendix A of this
manual.
4059 MESSAGE BAD UPDATE VALUE, EXPECTED INTERNET OR MAPPING.
CAUSE Something other than the supported INTERNET or
MAPPING option follows the UPDATE= option in the
NETCONTROL command line.
ACTION Consult the NS3000/iX Operations and Maintenance
Reference Manual for the correct syntax for the
NETCONTROL command. Once the syntax has been
corrected, retry the command.
4060 MESSAGE THIS UPDATE IS NOT ALLOWABLE FOR THIS ENTITY.
CAUSE The entity associated with the NETCONTROL UPDATE
command may not be updated.
ACTION Consult the NS3000/iX Operations and Maintenance
Reference Manual for the correct syntax for the
NETCONTROL command. Once the syntax has been
corrected, retry the command.
4061 MESSAGE CONFIGURATION FILE NOT VALID.
CAUSE Validation errors occurred on a NETCONTROL START
or UPDATEcommands.
ACTION Correct the invalid parameters in your
configuration file and try again.
4062 MESSAGE UNABLE TO LOCK CONFIGURATION FILE. (NMERR= error
number).
CAUSE Unable to lock the configuration file for
execution of a NETCONTROL START or UPDATE.
ACTION Wait and try again; if problem persists, see
"Submitting an SR" in appendix A of this manual.
4063 MESSAGE PROTOCOL START FAILED.
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 "Submitting an SR" in
appendix A of this manual.
4064 MESSAGE GENERAL PROTOCOL STARTUP FAILED.
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 "Submitting an SR" in
appendix A of this manual.
4100 MESSAGE VERSION ERROR: INTERNAL ERROR (NMERR= error
number).
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 "Submitting an
SR" in appendix A of this manual.
4101 MESSAGE TRANSPORT NOT YET DOWN.
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:
1. Wait a few minutes, then retry the
NETCONTROL START command. If the problem
persists, abort any remaining network
users.
2. Submit an SR any time this problem
occurs. See "Submitting an SR" in
appendix A of this manual.
4200 MESSAGE CONFIGURATION FILE NOT OPENED.
CAUSE Opening the configuration file failed.
ACTION Confirm that the configuration file
NMCONFIG.PUB.SYS exists and is valid. Retry the
NETCONTROL command.
4201 MESSAGE INTERNAL BUFFER ERROR.
CAUSE Creating a network transport buffer area failed.
ACTION See "Submitting an SR" in appendix A of this
manual.
4202 MESSAGE INTERNAL CONFIGURATION FILE ERROR (NMERR= error
number).
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.
4203 MESSAGE INTERNAL ERROR ON START.
CAUSE A serious internal error has been detected
during the execution of the NETCONTROL START
command.
ACTION See "Submitting an SR" in appendix A of this
manual.
4204 MESSAGE linkname DEVICE STARTUP FAILED.
CAUSE
1. The configured device does not exist on
the system.
2. The link connection is bad due to faulty
hardware.
3. An internal error has occurred during
device startup.
ACTION
1. Consult the SHERLOCK diagnostics to
determine the cause of the link error.
If no link error is indicated, see
"Submitting an SR" in appendix A of this
manual.
2. Consult the SHERLOCK diagnostics to
determine the cause of the link error.
If no link error is indicated, see
"Submitting an SR" in appendix A of this
manual.
3. Consult the SHERLOCK diagnostics to
determine the cause of the link error.
If no link error is indicated, see
"Submitting an SR" in appendix A of this
manual.
4205 MESSAGE linkName DEVICE IN BOTH ADDLINK AND DELLINK
FUNCTIONS.
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.
4206 MESSAGE HOST - DTC CONFIGURATION MISMATCH FOR DEVICE
linkname. ENSURE HOST NAME IS CONFIGURED ON
DTC.
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.
4207 MESSAGE HOST - DTC VERSION MISMATCH FOR DEVICE linkname.
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.
4208 MESSAGE X.25 CARD DOWN ON DTC FOR DEVICE linkname.
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.
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 IEEE802.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.
4215 MESSAGE DTC NAME NOT CONFIGURED IN NMCONFIG PATH
"LINK.linkname".
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.
4216 MESSAGE CANNOT FIND DTC CONFIGURED FOR DEVICE linkname.
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.
4217 MESSAGE MAXIMUM X.25 LINKS ALREADY STARTED, CANNOT START
DEVICE linkname.
CAUSE Too many X.25 links have been started on the
host.
ACTION Stop unused X.25 links or Network Interfaces.
4218 MESSAGE CANNOT OPEN NETWORK DIRECTORY FILE.
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
"Submitting an SR" in appendix A of this manual.