NS3000/iX Operations and Maintenance Reference Manual (36922-90039)

Chapter 5 63

Common Network Problems

Command Errors

If you are using the interactive capabilities of NS 3000/iX and

associated links and receive an error, refer to “NS 3000/iX Network

Services Error Messages” in the NS 3000/iX Error Messages Reference

Manual.

The command errors ﬁt into four categories:

• Syntax errors or invalid options. These errors result from user

errors when issuing the command. They are readily corrected by

checking for the correct syntax and reissuing the command.

• Warnings. If a command is executable but may give unexpected

results, a warning is issued. This would occur in a situation where

conﬂicting options were speciﬁed. The warning informs you which

option was actually used (or not used).

• Resource Errors. These errors occur when a system resource

needed for the execution of the command is not available. If they

occur, you can wait and reissue the command later, when the

resource may be available. If resource errors happen frequently the

conﬁguration or resource allocation of the system may be

inadequate. The network manager may need to investigate further.

• Internal Errors. These errors indicate that the software is

malfunctioning. If they ever occur, notify your HP representative.

The network manager should follow the steps outlined in Appendix

B, “Submitting an SR.”"

For syntax errors and warnings, consult the reference pages in this

manual for that command’s correct syntax and options, or refer to

Using NS 3000/iX Network Services.

Line Opening Errors

There are several reasons why a DSLINE command for opening a

communications line might be rejected. Some line opening errors

actually occur when a REMOTE HELLO (or DSCOPY, or programmatic

RPMCREATE or FOPEN) is executed, not when the DSLINE is done. The

following list summarizes the likely causes of line opening failures:

• The user made a syntax error in the DSLINE command.

• The user speciﬁed an erroneous nodename or envid in the DSLINE

command. The node name must match the one conﬁgured for the

system the user is trying to reach. Make sure that all users know the

correct node names. You may want to post a map with the conﬁgured

node names for all the nodes on the network. The correct node

names can be checked in the network directory (if one is being used).