HP Guardian Errors Manual page 65

The line normally exhibits error 248 on the operator console when the line is initially brought
up. The message should be followed by another message announcing that the line is up.
By performing successive SCF STATS commands (at one minute intervals) and observing the
U-FRAME counts, you can determine whether data is being transmitted and received. The FCS
error count indicates that garbled data was received.
If the SCF STATS commands do not indicate both send and receive data, place the local modem
in analog loopback and observe the U-FRAME counts again. If both send and receive counts are
incrementing, the local controller and modem are working properly. If both systems check out, first
check the lines by using the modem self test, then observe the U-FRAME counts with the remote
modem in digital loopback. If all tests indicate data is being transmitted and received, then a trace
at both ends of the line should indicate the cause of the not-ready condition.
If this problem persists, your service provider needs to run traces or perform other corrective action.
Refer to the Expand Network Management Guide for further information.
249 (%371)
Cause The network control process ($NCP) caused the Expand process to terminate its traffic
(already sent to its remote destination) for one of the following reasons:
A connection to a remote system was established or reestablished over the same path or a
different path.
The network control process came up (for example, after a crash or a takeover by the backup).
There was no longer a path to the remote system (operator message 43, LDEV ldev NET:
CONNECTION LOST TO SYS nnn, is generated by the network control process).
Or, the Expand process encountered one of the following situations:
The level-4 protocol detected a protocol error.
An I/O power on occurred but all lines used by the Expand process were attached to the
controller for which the IOPON occurred.
A processor power on occurred.
The Expand process received a request from a system for which it is not the current path.
A Expand process received a request to forward a message, but all its lines were down.
Effect The procedure sets the error code and returns. The request to perform the operation is sent
but it might not have been performed.
Recovery Corrective action is device dependent and application dependent. If this problem persists,
your service provider needs to run traces or perform other corrective action. For additional
information, see the Expand Network Management Guide
250 (%372)
Cause The referenced system in the network is down, or it is not currently connected to the system
on which the requested process is running (path error).
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Corrective action is application dependent. If this problem persists, your service provider
needs to run traces or perform other corrective action.
251 (%373)
Network error; operation aborted.
(device type: 63)
All paths to the system are down.
(device type: 63)
Network protocol error (path error).
(device type: any except 2)
Error Code Descriptions 65