|
|
This appendix covers the X.25 cause and diagnostic codes, as referred to in the debug x25 all command of the "Debug Commands" chapter. For more information on these codes, see the 1984 ITU-T X.25 Recommendation.
Table A-1 describes the differences between our implementation of certain X.25 network-generated, "international problem" diagnostic fields and the definitions provided in Annex E of ITU-T Recommendation X.25. The Annex E Table E-1/X.25 includes the complete diagnostic field listing.
| Decimal Value | Annex E, Rec. X.25 Diagnostic Description | Cisco Proprietary Definition of Diagnostic Codes |
|---|---|---|
| 112 | International problem | Not used. |
| 113 | Remote network problem | Not used. |
| 114 | International protocol problem | Not used. |
| 115 | International link out of order | Indicates one of the following failures: failed when initializing a switched PVC; in TCP tunneling, failed when initiating or resetting a PVC; or, failed when PAD PVC circuit was initiated or reset. |
| 116 | International link busy | Not used. |
| 117 | Transit network facility problem | Not used. |
| 118 | Remote network facility problem | Not used. |
| 119 | International routing problem | Indicates the following failure: in TCP tunneling of X.25 when session is closed by network. In addition to its standard meaning, Cisco routers use this code to signal an abnormal X.25-over-TCP (XOT) condition. This code is used when an X.25 Virtual Circuit connection is intiated using XOT, but but the remote XOT peer closed the TCP connection. This commonly occurs when the remote XOT peer could not route the received call. |
| 120 | Temporary routing problem | Indicates the following failure: when tunneling X.25 through TCP/IP and the remote network is identified as unreachable.
In addition to its standard meaning, Cisco routers use this code to signal an abnormal X.25-over-TCP (XOT) condition. This code is used when an X.25 Virtual Circuit connection cannot be intiated using XOT because the TCP connection fails due to an unreachable remote XOT peer. |
| 121 | Unknown called DNIC | Not used. |
| 122 | Maintenance action (may apply to maintenance action within a national network | For CMNS, indicates the following: router fails to route the call due to setup or unreachability of destination; when VC is cleared using the clear x25-vc EXEC command; when router CLEARs a VC when its idle timer expires. |
A cause code indicates an event that triggered an X.25 packet. The cause code can only appear in entries for CLEAR REQUEST, REGISTRATION CONFIRMATION, RESET REQUEST, and RESTART packets. Possible values for the cause code can vary, depending on the type of packet. Because the REGISTRATION exchange is not supported, those cause codes are not documented in this section.
Table A-2 describes the meanings of cause codes for CLEAR REQUEST packets.
| Code (Hex) | Code (Dec) | Description |
|---|---|---|
| 00 | 0 (or 128 to 255) | DTE originated |
| 01 | 1 | Number busy |
| 03 | 3 | Invalid facility request |
| 05 | 5 | Network congestion |
| 09 | 9 | Out of order |
| 0B | 11 | Access barred |
| 0D | 13 | Not obtainable |
| 11 | 17 | Remote procedure error |
| 13 | 19 | Local procedure error |
| 15 | 21 | RPOA out of order |
| 19 | 25 | Reverse charging not accepted |
| 21 | 33 | Incompatible destination |
| 29 | 41 | Fast select not accepted |
| 39 | 57 | Ship absent |
Table A-3 describes the meanings of cause codes for RESET REQUEST packets.
| Code (Hex) | Code (Dec) | Description |
|---|---|---|
| 00 | 0 (or 128 to 255) | DTE originated |
| 01 | 1 | Out of order |
| 03 | 3 | Remote procedure error |
| 05 | 5 | Local procedure error |
| 07 | 7 | Network congestion |
| 09 | 9 | Remote DTE operational |
| 0F | 15 | Network operational |
| 11 | 17 | Incompatible destination |
| 1D | 29 | Network out of order |
Table A-4 describes the meanings of cause codes for RESTART packets.
| Code (Hex) | Code (Dec) | Description |
|---|---|---|
| 00 | 0 (or 128 to 255) | DTE restarting |
| 01 | 1 | Local procedure error |
| 03 | 3 | Network congestion |
| 07 | 7 | Network operational |
| 7F | 127 | Registration/cancellation confirmed |
The X.25 diag (diagnostic) code provides an additional hint as to what, if anything, went wrong. This code can only appear in entries for CLEAR REQUEST, DIAGNOSTIC, RESET REQUEST, and RESTART packets. Unlike the cause codes, the diag codes do not vary depending upon the type of packet.
Table A-5 describes the meanings of possible diag codes.
Diagnostic codes with values of 80 or greater in hexadecimal, or with values of 128 or greater in decimal, are specific to a particular network. To learn the meanings of these codes, contact the administrator for that network.
|
|