Chapter 12 NETXPORTERR Error Messages

CAUSE: Issued NETCONTROL STATUS command on inactive transport.

ACTION: Issue NETCONTROL START.

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.

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 an SR ” of this manual.

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.

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.

CAUSE: Informative message.

ACTION: None.

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.

CAUSE: Typographical error.

ACTION: Type the word ALL after STATUS =. Correct and retry.

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.

CAUSE: Only the keywords listed are allowed.

ACTION: Check the NS 3000/iX Operations and Maintenance Reference Manual for proper syntax. Correct and retry.

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.

CAUSE: No link name follows the ADDLINK= or DELLINK= keyword.

ACTION: Reissue the NETCONTROL ADDLINK or DELLINK command with the appropriate link name.

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.

CAUSE: Both parameters not allowed in a single NETCONTROL command.

ACTION: Pick appropriate command. Correct and retry.

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.

CAUSE: Usually a typographical error. DEFAULT: Disk.

ACTION: Check the NS 3000/iX Operations and Maintenance Reference Manual for proper syntax. Correct and retry.

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.

CAUSE: Trace file record size specified in command line parameter is too large or too small.

ACTION: Correct with valid value; retry.

CAUSE: Trace file size specified in command line parameter is too large or too small.

ACTION: Correct with valid value; retry.

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 an SR ” of this manual.

CAUSE: Data dictionary full.

ACTION: Reissue the command after waiting a few minutes. If the problem persists, then see Appendix A “Submitting an SR ” of this manual.

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 an SR ” of this manual.

CAUSE: Invalid DIAG value.

ACTION: The DIAG keyword command is not for customer use. Contact your Hewlett-Packard representative.

CAUSE: The two entities (NET and PROT) cannot be used together.

ACTION: Pick appropriate entity and reissue command.

CAUSE: User typed an illegal command.

ACTION: Type word MOD after VERSION=.

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 an SR ” of this manual.

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 an SR ” of this manual.

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.

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.

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.

CAUSE: Informative message.

ACTION: None.

CAUSE: Informative message.

ACTION: None.

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 an SR ” of this manual.

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 an SR ” of this manual.

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 an SR ” of this manual.

CAUSE: Either missing software module or possible internal error.

ACTION: Issue the NETCONTROL VERSION=MOD command to find out which module is missing.

CAUSE: There may be no version stamp; file label may be overwritten, or possible bad software installation.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: NETCONTROL START command issued for an already active entity.

ACTION: None.

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.

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 Appendix A “Submitting an SR ” of this manual.

CAUSE: Trace issued on an inactive protocol.

ACTION: Check configuration file. All protocols must be configured.

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.

CAUSE: The NI named is not configured.

ACTION: Alter the configuration file appropriately, shut down the transport, and reconfigure.

CAUSE: Usually a command line syntax error.

ACTION: Rename if necessary; retype and retry.

CAUSE: Missing software modules or module version number mismatch.

ACTION: Issue the NETCONTROL VERSION=MOD command for more information. See Appendix A “Submitting an SR ” of this manual.

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 an SR ” of this manual.

CAUSE: Issued a NETCONTROL STATUS command on an inactive entity.

ACTION: None.

CAUSE: NETCONTROL STATUS error.

ACTION: Wait and try again; if problem persists, see Appendix A “Submitting an SR ” of this manual.

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.

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.

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 an SR ” of this manual.

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.

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.

CAUSE: Validation errors occurred on a NETCONTROL START or UPDATE commands.

ACTION: Correct the invalid parameters in your configuration file and try again.

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 an SR ” of this manual.

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 an SR ” of this manual.

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 an SR ” of this manual.

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 an SR ” of this manual.

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:

CAUSE: Opening the configuration file failed.

ACTION: Confirm that the configuration file NMCONFIG.PUB.SYS exists and is valid. Retry the NETCONTROL command.

CAUSE: Creating a network transport buffer area failed.

ACTION: See Appendix A “Submitting an SR ” of this manual.

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.

CAUSE: A serious internal error has been detected during the execution of the NETCONTROL START command.

ACTION: SeeAppendix A “Submitting an SR ” of this manual.

CAUSE:

ACTION:

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.

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.

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.

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.

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.

CAUSE: The control connection between the host and the DTC was lost.

ACTION: Verify that the DTC configured for this device is still functioning.

CAUSE: This error could occur for one of the following reasons:

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.

CAUSE: The path DTS.DTC was created, but no data was added.

ACTION: Using NMMGR, update the path and validate the DTS subsystem.

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.

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.

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.

CAUSE: This error may be caused by one of the following reasons:

ACTION: Check the configuration data and verify that it is correct. Restart the DTC if necessary.

CAUSE: Too many X.25 links have been started on the host.

ACTION: Stop unused X.25 links or Network Interfaces.

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 an SR ” of this manual.