HP X.25/9000 User's Guide HP-UX 11i v3 (5900-1523, August 2011)

Table 56 DTE-Specific signals (continued)
ExplanationISO DescriptionDiagnostic
X.121 address. Internal problem which may be generated by
components of X.25/9000 architecture.
Level 2 is coming up or a SABM frame is received. System sends
RESTART REQUEST indicating host is up.
DTE operational.161 (RESTART)
Either level 3 or level 2 detected as down. Request delivered when
network interface was not operational. Condition usually results in an
DTE not operational.162 (CLEAR, RESET)
error returned to the application instead of CLEAR. Diagnostic is used
when RESTART INDICATION has been received by interface. Interface
is going down. RESTART REQUEST was sent on network.
Lack of memory to establish, reset, or clear a call, to process data,
expedite data or acknowledgments, or to perform internal operation.
DTE resource constraint.163 (CLEAR, RESET)
This may indicate lack of network memory, or resource constraints on
card. When resource constraint appears on connected circuit, CLEAR
will be sent only if no recovery is possible.
CALL INDICATION requiring fast select facility has been received and
fast select is not configured. Results in error when detected on CALL
REQUEST.
Fast select not
subscribed.
164 (CLEAR)
X.25 subsystem is down when X.25/9000 to IP subsystem is servicing
CALL CONFIRMATION or incoming DATA.
Disconnection (transient
condition).
225 (CLEAR)
Table 57 OSI Network service problem
ExplanationISO DescriptionDiagnostic
Due to internal constraints at high levels other than lack of network
memory, CALL INDICATION cannot be serviced.
Connection rejection.
Cause unspecified
(transient condition).
227 (CLEAR)
OSI network service not operational.OSI Network Service
problem.
224 (CLEAR, RESET)
X.25 to IP subsystem clears incoming CALL INDICATION which has
calling address not present in IP to X.121 mapping table. If call were
Connection rejection.
Reason unspecified.
228 (CLEAR)
accepted, circuit would be half-duplex enabling remote node to send(Permanent condition)
(Transient condition). and receive while local host would only be able to receive. When
X.25/IP output routine has data addressed to remote node it must be
able to map the IP address to the X.121 address. If it cannot do so,
the IP packet is discarded. Clearing the INCOMING CALL when the
remote's X.121 address is not in the map table prevents a half-duplex
circuit from being established.
No listen socket capable of servicing CALL INDICATION. X.25
subsystem is down when X.25-to-IP subsystem is servicing CALL
INDICATION.
Connection rejection.
NSAP unreachable
(transient condition).
231 (CLEAR)
CALL INDICATION with first byte of call user data other than CC (hex)
received on system which does not have X.25/9000 programmatic
access configured in kernel.
Connection rejection.
NSAP unreachable
(permanent condition).
232 (CLEAR)
Message (sequence of packets with the M bit set followed by packet
with M bit not set) received, and size exceeds maximum size allowed
Reset. Cause
unspecified.
233 (RESET)
by application for inbound data message. Corresponds to specific
out-of-band event delivered to user. Data was received on VC without
a user, that is, an IP or programmatic access application. X.25
subsystem was down when X.25 to IP subsystem serviced incoming
DATA on permanent VC.
Error returned to the application due to network congestion condition.Reset. Congestion.234 (RESET)
156 Diagnostic messages