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

Chapter 2 33
Operating Your Network
Verifying Network Connections and Services
Miscellaneous Test Errors
Certain errors may appear in all software line tests which do not fit in
the categories described above. They are listed here.
MESSAGE: PCERRMSG FAILED (SOCKERR #)
SOCKERR # CAUSE: Error message could not be acquired from the message
catalogue SOCKCAT.NET.SYS.
ACTION: Ensure that the message catalog exists. Examine errors
returned to the console before and after this error.
MESSAGE: IPCSHUTDOWN FAILED
SOCKERR # CAUSE: Socket could not be closed.
ACTION: Examine errors returned to the console before this error. Take
action for appropriate SOCKERR.
General Test Suggestions
If the following SOCKERRs appear together, then the network may be
“too busy”—that is, coordinating too many processes—to permit proper
operation of the XPVAL tests:
Error Message
REMOTE ABORTED THE CONNECTION
SOCKET TIMEOUT
and
CONNECTION REQUEST FAILED
RESPONSE TO CONNECTION FAILED
LOCAL IPCRECVCN FAILED
Wait until network activity lessens to execute the tests.
Examine the Protocol Module errors regarding the TCP entity. Protocol
Module errors are listed in the “Network Transport Protocol Errors”
table in the NS 3000/iX Error Messages Reference Manual.
To Validate Network Services in Batch Mode
Perform the following steps to use QVALNS to check the Network
Services. The services tested are VT, RFA, NFT, RPM, and RDBA. (Note
that it is not possible to use passwords with QVALNS. If passwords are
required, run NSTEST instead.)
1. Make sure the network transport and Network Services are running
on all nodes that are to be a part of this test.
2. Run the NETTOOL utility by entering the program name:
NETTOOL.NET.SYS
The root menu will appear.