NS3000/iX Error Messages Reference Manual (36923-90041)

362 Chapter19
Logging Location Codes
Control Process Logging Location Codes
them within a 15-second timeout period (PARM = 32-bit port number of
the general protocol module which failed to reply). One of these errors
will appear for each module that fails to reply.
ACTION: This error in itself was not fatal, and NETCP processing
continued. This can mean either that a temporary Path Verify storm is
occurring because a heavily used link has failed, or it can mean there is
a problem with the general protocol module. In addition, if the reply
ever does arrive, NETCP will probably discard it, but may instead get
confused if it arrives while awaiting some other reply. If the problem
persists, first look for previous errors 678 or 679. The PARM for these
would contain the interface code from the reply, and should tell HP
what module was sending to CP. If this does not help, you can still
determine which module by restarting the network and taking note of
all port numbers printed on the console when Transport starts up, and
the modules which printed those ports. Then when the next error 629
occurs, match those port numbers with the PARM value printed for the
error. Afterward see Appendix A, “Submitting an SR,” of this manual, to
report a problem against the general protocol module which is failing to
reply.
MESSAGE: Bad status
630 CLAS0002 CAUSE: While processing a Path Verify operation because NETCP
detected a possible problem or change in state of a certain network, or
because of a Path Verify message received from IPU in response to a
redirect packet IPU received from a GATEWAY, NETCP encountered
an error trying to send a Path Verify message to one of the general
protocols (PARM = 32-bit status returned by the call to send_msg).
ACTION: This error was not fatal; messages were sent to all the other
general protocols, and NETCP will not expect a reply for the send that
failed. However, the affected protocol module will not be aware there
may be a problem with the path, and may continue to try to use it. If
NETCP tracing was active, the tracefile will show the message which
could not be sent, and the interface code in that message will indicate
which module was not accessible. If the problem happens frequently,
see Appendix A, “Submitting an SR,” of this manual.
MESSAGE: Bad status
631 CLAS0002 CAUSE: While processing a Path Verify operation because NETCP
detected a possible problem or change in state of a certain network, or
because of a Path Verify message received from IPU in response to a
redirect packet IPU received from a GATEWAY, NETCP encountered
an error trying to send a path verify message to the ICMP Server
module of Transport (PARM = 32-bit status returned by the call to
send_msg).
ACTION: This error was not fatal; messages were sent to all the general
protocols, and NETCP will not expect a reply to the send that failed.
However, the ICMP Server module will not be aware there may be a