Table of ContentsX.25 Cause and Diagnostic Codes X.25 Cause and Diagnostic CodesThis 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. Table A-1 : Annex E International Problem Diagnostic Code Differences
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. Table A-2 : Cause Code Descriptions for CLEAR REQUEST Packets
Table A-3 describes the meanings of cause codes for RESET REQUEST packets. Table A-3 : Cause Code Descriptions for RESET REQUEST Packets
Table A-4 describes the meanings of cause codes for RESTART packets. Table A-4 : Cause Code Descriptions for RESTART Packets
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. Table A-5 : X.25 Diagnostic Field Code Descriptions
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.
|