Guest

Cisco IOS Software Releases 12.3 T

X.25 Data Display Trace

Hierarchical Navigation

Downloads

Table Of Contents

X.25 Data Display Trace

Contents

Displaying the Contents of X.25 Packets

Additional References

Related Documents

Standards

Technical Assistance

Command Reference

debug x25

debug x25 interface

debug x25 vc

debug x25 xot


X.25 Data Display Trace

The X.25 Data Display Trace feature enhances the Cisco IOS debugging capability for X.25. This feature enables an authorized user to display the entire X.25-encoded traffic stream, including user data, for those packets specified by an X.25 debug command.

Feature History for the X.25 Data Display Trace Feature

Feature History
 
Release
Modification

12.3(2)T

This feature was introduced.


Finding Support Information for Platforms and Cisco IOS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

Contents

•Displaying the Contents of X.25 Packets

•Additional References

•Command Reference

Displaying the Contents of X.25 Packets

To augment the reporting of X.25 traffic information to include the contents of the X.25 packets, use the commands listed in the following task. Note that an entry of the debug x25, debug x25 interface, debug x25 vc, or debug x25 xot commands will override any prior entry of any of these commands.

Caution The reported X.25 packet information may contain sensitive data; for example, clear-text account identities and passwords. The network access policies and router configuration should be controlled appropriately to address this risk.
Caution The X.25 debug commands can generate large amounts of debugging output. If logging of debug output to the router console is enabled (the default condition), this output may fill the console buffer, preventing the router from processing packets until the contents of the console buffer have been printed.

SUMMARY STEPS

1. enable

2. debug x25 [only | cmns | xot] [events | all] [dump]

3. debug x25 interface {serial-interface | cmns-interface [mac mac-address]} [vc number] [events | all] [dump]

4. debug x25 vc number [events | all] [dump]

5. debug x25 xot [remote ip-address [port number]] [local ip-address [port number]] [events | all] [dump]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2 

debug x25 [only | cmns | xot] [events | all] [dump]

Example:

Router# debug x25 events

Displays information about all X.25 traffic or a specific X.25 service class.

•Use the dump keyword to display the contents, including user data, of X.25 packets.

Step 3 

debug x25 interface {serial-interface | cmns-interface [mac mac-address]} [vc number] [events | all] [dump]

Example:

Router# debug x25 interface serial 0 dump

Displays information about X.25, Annex G or CMNS contexts or virtual circuits that occur on the identified interface.

•CMNS reports may be restricted to packets occurring on the interface with the specified remote host.

•Use the dump keyword to display the contents, including user data, of X.25 packets.

Step 4 

debug x25 vc number [events | all] [dump]

Example:

Router# debug x25 vc 1 events

Displays information about traffic for all virtual circuits that use a given number.

•Use the dump keyword to display the contents, including user data, of X.25 packets.

Step 5 

debug x25 xot [remote ip-address [port number]] [local ip-address [port number]] [events | all] [dump]

Example:

Router# debug x25 xot remote 10.0.155.71 port 1998

Displays information about traffic to or from a specific X.25 over TCP (XOT) host.

•Use the dump keyword to display the contents, including user data, of X.25 packets.

Additional References

The following sections provide references related to X.25.

Related Documents

Related Topic
Document Title

X.25 configuration tasks

Cisco IOS Wide-Area Networking Configuration Guide, Release 12.3

X.25 commands

Cisco IOS Wide-Area Networking Command Reference, Release 12.3


Standards

Standards
Title

ITU-T 1993 Recommendation X.25

Interface between DTE and DCE for terminals operating in the packet mode and connected to public data networks by dedicated circuit


Technical Assistance

Description
Link

Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/public/support/tac/home.shtml


Command Reference

This section documents modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.3 command reference publications.

•debug x25

•debug x25 interface

•debug x25 vc

•debug x25 xot

debug x25

To display information about all X.25 traffic or a specific X.25 service class, use the debug x25 command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug x25 [only | cmns | xot] [events | all] [dump]

no debug x25 [only | cmns] [events | all] [dump]

Syntax Description

only

(Optional) Displays information about X.25 services only.

cmns

(Optional) Displays information about CMNS services only.

xot

(Optional) Displays information about XOT services only.

events

(Optional) Displays all traffic except Data and Receiver Ready (RR) packets.

all

(Optional) Displays all traffic. This is the default.

dump

(Optional) Displays the encoded packet contents in hexadecimal and ASCII formats.


Defaults

All traffic is displayed.

Command Modes

Privileged EXEC

Command History

Release
Modification

10.0

This command was introduced.

12.0(5)T

For Domain Name System (DNS)-based X.25 routing, additional functionality was added to the debug x25 events command to describe the events that occur while the X.25 address is being resolved to an IP address using a DNS server. The debug domain command can be used along with debug x25 events to observe the whole DNS-based X.25 routing data flow.

12.0(7)T

For the X.25 Closed User Groups (CUGs) feature, functionality was added to the debug x25 events command to describe events that occur during CUG activity.

12.2(8)T

The debug x25 events command was enhanced to display events specific to Record Boundary Preservation protocol.

12.3(2)T

The dump keyword was added.


Usage Guidelines

Caution The X.25 debug commands can generate large amounts of debugging output. If logging of debug output to the router console is enabled (the default condition), this output may fill the console buffer, preventing the router from processing packets until the contents of the console buffer have been printed.

The debug x25, debug x25 interface, debug x25 vc, and debug x25 xot commands all generate the same basic output. The debug x25 interface, debug x25 vc, and debug x25 xot commands narrow the scope of the debug x25 output to specific virtual circuits or types of traffic.

This command is particularly useful for diagnosing problems encountered when placing calls. The debug x25 all output includes data, control messages, and flow control packets for all virtual circuits of the router.

All debug x25 commands can take either the events or the all keyword. The keyword all is the default and causes all packets meeting the other debug criteria to be reported. The keyword events omits reports of any Data or RR flow control packets; the normal flow of data and RR packets is commonly large and less interesting to the user, so event reporting can significantly decrease the processor load induced by debug reporting.

Use the dump keyword to display the entire contents, including user data, of X.25 packets. The encoded X.25 packet contents are displayed after the standard packet description. The output includes the offset into the packet and the display of the data in both hexadecimal and ASCII formats.

Caution The X.25 packet information that is reported by using the dump keyword may contain sensitive data; for example, clear-text account identities and passwords. The network access policies and router configuration should be controlled appropriately to address this risk.

Examples

The following is sample output from the debug x25 command, displaying output concerning the functions X.25 restart, call setup, data exchange, and clear: 

Router# debug x25


Serial0: X.25 I R/Inactive Restart (5) 8 lci 0

  Cause 7, Diag 0 (Network operational/No additional information)

Serial0: X.25 O R3 Restart Confirm (3) 8 lci 0

Serial0: X.25 I P1 Call (15) 8 lci 1

From(6): 170091 To(6): 170090

   Facilities: (0)

   Call User Data (4): 0xCC000000 (ip)

Serial0: X.25 O P3 Call Confirm (3) 8 lci 1

Serial0: X.25 I D1 Data (103) 8 lci 1 PS 0 PR 0

Serial0: X.25 O D1 Data (103) 8 lci 1 PS 0 PR 1

Serial0: X.25 I P4 Clear (5) 8 lci 1

  Cause 9, Diag 122 (Out of order/Maintenance action)

Serial0: X.25 O P7 Clear Confirm (3) 8 lci 1

debug x25 events for DNS-Based X.25 Routing: Example

The following example of the debug x25 events command shows output related to the DNS-Based X.25 Routing feature. It shows messages concerning access to the DNS server. In the example, nine alternate addresses for one XOT path are entered into the DNS server database. All nine addresses are returned to the host cache of the router by the DNS server. However, only six addresses will be used during the XOT switch attempt because this is the limit that XOT allows. 

Router# debug x25 events


00:18:25:Serial1:X.25 I R1 Call (11) 8 lci 1024

00:18:25: From (0): To (4):444 

00:18:25: Facilities:(0)

00:18:25: Call User Data (4):0x01000000 (pad)

00:18:25:X.25 host name sent for DNS lookup is "444"

00:18:26:%3-TRUNCATE_ALT_XOT_DNS_DEST:Truncating excess XOT addresses (3)

returned by DNS

00:18:26:DNS got X.25 host mapping for "444" via network

00:18:32:[10.1.1.8 (pending)]:XOT open failed (Connection timed out; remote host not 
responding)

00:18:38:[10.1.1.7 (pending)]:XOT open failed (Connection timed out; remote host not 
responding)

00:18:44:[10.1.1.6 (pending)]:XOT open failed (Connection timed out; remote host not 
responding)

00:18:50:[10.1.1.5 (pending)]:XOT open failed (Connection timed out; remote host not 
responding)

00:18:56:[10.1.1.4 (pending)]:XOT open failed (Connection timed out; remote host not 
responding)

00:20:04:[10.1.1.3,1998/10.1.1.3,11007]:XOT O P2 Call (17) 8 lci 1

00:20:04: From (0): To (4):444

00:20:04: Facilities:(6)

00:20:04:  Packet sizes:128 128

00:20:04:  Window sizes:2 2

00:20:04: Call User Data (4):0x01000000 (pad) 

00:20:04:[10.1.1.3,1998/10.1.1.3,11007]:XOT I P2 Call Confirm (11) 8 lci 1

00:20:04: From (0): To (0):

00:20:04: Facilities:(6)

00:20:04:  Packet sizes:128 128

00:20:04:  Window sizes:2 2

00:20:04:Serial1:X.25 O R1 Call Confirm (5) 8 lci 1024

00:20:04: From (0): To (0):

00:20:04: Facilities:(0)

Record Boundary Preservation: Examples

The following examples show output for the x25 debug events command when record boundary preservation (RBP) has been configured using the x25 map rbp local command.

The following display shows establishment of connection: 

X25 RBP:Incoming connection for port 9999 from 10.0.155.30 port 11001

Serial0/1:X.25 O R1 Call (10) 8 lci 64

  From (5):13133 To (5):12131

  Facilities:(0)

Serial0/1:X.25 I R1 Call Confirm (3) 8 lci 64

The following display shows that the X.25 call was cleared by the X.25 host: 

Serial0/1:X.25 I R1 Clear (5) 8 lci 64

  Cause 0, Diag 122 (DTE originated/Maintenance action)

X25 RBP:X.25 circuit cleared

Serial0/1:X.25 O R1 Clear Confirm (3) 8 lci 64

The following display shows that the TCP session has terminated: 

[10.0.155.30,11000/10.0.155.33,9999]:TCP receive error, End of data transfer

X25 RBP:End of data transfer

Serial0/1:X.25 O R1 Clear (5) 8 lci 64

Cause 9, Diag 122 (Out of order/Maintenance action)

Serial0/1:X.25 I R1 Clear Confirm (3) 8 lci 64

The following examples show output of the x25 debug events command when RBP has been configured using the x25 pvc rbp local command.

The following display shows data on the permanent virtual circuit (PVC) before the TCP session has been established: 

X25 RBP:Data on unconnected PVC

Serial1/0:X.25 O D1 Reset (5) 8 lci 1

  Cause 0, Diag 113 (DTE originated/Remote network problem)

Serial1/0:X.25 I D2 Reset Confirm (3) 8 lci 1

The following display shows establishment of connection: 

X25 RBP:Incoming connection for port 9998 from 2.30.0.30 port 11002

Serial1/0:X.25 O D1 Reset (5) 8 lci 1

  Cause 0, Diag 0 (DTE originated/No additional information)

Serial1/0:X.25 I D2 Reset Confirm (3) 8 lci 1

The following display shows termination of connection when the X.25 PVC was reset: 

Serial1/0:X.25 I D1 Reset (5) 8 lci 1

  Cause 15, Diag 122 (Network operational (PVC)/Maintenance action)

X25 RBP:Reset packet received

Serial1/0:X.25 O D3 Reset Confirm (3) 8 lci 1

The following display shows that the TCP session has terminated: 

[2.30.0.30,11003/2.30.0.33,9998]:TCP receive error, End of data transfer

X25 RBP:End of data transfer

Serial1/0:X.25 O D1 Reset (5) 8 lci 1

  Cause 0, Diag 113 (DTE originated/Remote network problem)

Serial1/0:X.25 I D2 Reset Confirm (3) 8 lci 1

The following examples show output of the x25 debug events command when RBP has been configured using the x25 map rbp remote command.

The following display shows that the X.25 call was cleared: 

Serial0/1:X.25 I R1 Clear (5) 8 lci 1024

  Cause 0, Diag 122 (DTE originated/Maintenance action)

X25 RBP:X.25 circuit cleared

Serial0/1:X.25 O R1 Clear Confirm (3) 8 lci 1024

The following display shows that the X.25 call was reset: 

Serial0/1:X.25 I D1 Reset (5) 8 lci 1024

  Cause 0, Diag 122 (DTE originated/Maintenance action)

X25 RBP:Reset packet received

Serial0/1:X.25 O R1 Clear (5) 8 lci 1024

  Cause 9, Diag 122 (Out of order/Maintenance action)

Serial0/1:X.25 I R1 Clear Confirm (3) 8 lci 1024

The following examples show output of the x25 debug events command when RBP has been configured using the x25 pvc rbp remote command.

The following display shows that the X.25 PVC has been reset: 

Serial0/0:X.25 I D1 Reset (5) 8 lci 1

  Cause 0, Diag 122 (DTE originated/Maintenance action)

X25 RBP:Reset packet received

Serial0/0:X.25 O D2 Reset Confirm (3) 8 lci 1

The following display shows that the connection was terminated when the X.25 interface was restarted: 

Serial0/0:X.25 I R1 Restart (5) 8 lci 0

  Cause 0, Diag 122 (DTE originated/Maintenance action)

X25 RBP:X.25 PVC inactive

Serial0/0:X.25 O R2 Restart Confirm (3) 8 lci 0

Serial0/0:X.25 O D1 Reset (5) 8 lci 1

  Cause 1, Diag 113 (Out of order (PVC)/Remote network problem)

Serial0/0:X.25 I D3 Reset Confirm (3) 8 lci 1

x25 debug dump Output:: Example

The following is sample output for the x25 debug dump command. The encoded X.25 packet contents are displayed after the standard packet description. The output includes the offset into the packet and the display of the data in both hexadecimal and ASCII formats. 

Router# debug x25 dump


Serial1: X.25 O R/Inactive Restart (5) 8 lci 0

   Cause 0, Diag 0 (DTE originated/No additional information)

       0: 1000FB00 00                          ..{..           

Serial1: X.25 I R2 Restart (5) 8 lci 0

   Cause 7, Diag 0 (Network operational/No additional information)

       0:                              1000FB               ..{

       3: 0700                                 ..              

Serial1: X.25 I R1 Call (13) 8 lci 1

   From (4): 2501 To (4): 2502

   Facilities: (0)

   Call User Data (4): 0xCC000000 (ip)

       0:            10010B 44250225 0100CC00       ...D%.%..L.

      11: 0000                                 ..              

Serial1: X.25 O R1 Call Confirm (3) 8 lci 1

       0: 10010F                               ...             

Serial1: X.25 I D1 Data (103) 8 lci 1 PS 0 PR 0

       0:            100100 45000064 00000000       ...E..d....

      11: FF01A764 0A190001 0A190002 0800CBFB  ..'d..........K{

      27: 0B1E22CA 00000000 00028464 ABCDABCD  .."J.......d+M+M

      43: ABCDABCD ABCDABCD ABCDABCD ABCDABCD  +M+M+M+M+M+M+M+M

      59: ABCDABCD ABCDABCD ABCDABCD ABCDABCD  +M+M+M+M+M+M+M+M

      75: ABCDABCD ABCDABCD ABCDABCD ABCDABCD  +M+M+M+M+M+M+M+M

      91: ABCDABCD ABCDABCD ABCDABCD           +M+M+M+M+M+M    

Serial1: X.25 O D1 Data (103) 8 lci 1 PS 0 PR 1

       0:            100120 45000064 00000000       .. E..d....

      11: FF01A764 0A190002 0A190001 0000D3FB  ..'d..........S{

      27: 0B1E22CA 00000000 00028464 ABCDABCD  .."J.......d+M+M

      43: ABCDABCD ABCDABCD ABCDABCD ABCDABCD  +M+M+M+M+M+M+M+M

      59: ABCDABCD ABCDABCD ABCDABCD ABCDABCD  +M+M+M+M+M+M+M+M

      75: ABCDABCD ABCDABCD ABCDABCD ABCDABCD  +M+M+M+M+M+M+M+M

      91: ABCDABCD ABCDABCD ABCDABCD           +M+M+M+M+M+M    

 Serial1: X.25 I R1 Clear (5) 8 lci 1

   Cause 9, Diag 122 (Out of order/Maintenance action)

       0:            100113 097A                    ....z      

 Serial1: X.25 O R1 Clear Confirm (3) 8 lci 1

       0:                   100117                     .


Table 1 describes significant fields shown in the displays.

Table 1 debug x25 Field Descriptions 

Field
Description

Serial0

Interface on which the X.25 event occurred.

X.25

Type of event this message describes.

I

Letter indicating whether the X.25 packet was input (I) or output (O) through the interface.

R3

State of the service or virtual circuit (VC). Possible values follow:

R/Inactive—Packet layer awaiting link layer service

R1—Packet layer ready

R2—Data terminal equipment (DTE) restart request

R3—DCE restart indication

P/Inactive—VC awaiting packet layer service

P1—Idle

P2—DTE waiting for DCE to connect CALL

P3—DCE waiting for DTE to accept CALL

P4—Data transfer

P5—CALL collision

P6—DTE clear request

P7—DCE clear indication

D/Inactive—VC awaiting setup

D1—Flow control ready

D2—DTE reset request

D3—DCE reset indication

Refer to Annex B of the ITU-T Recommendation X.25 for more information on these states.

Restart

The type of X.25 packet. Possible values follow:

R Events

•Restart

•Restart Confirm

•Diagnostic

P Events

•Call

•Call Confirm

•Clear

•Clear Confirm

D Events

•Reset

•Reset Confirm

D1 Events

•Data

•Receiver Not Ready (RNR)

•RR (Receiver Ready)

•Interrupt

•Interrupt Confirm

XOT Overhead

•PVC Setup

Refer to RFC 1613 Cisco Systems X.25 over TCP (XOT) for information about the XOT PVC Setup packet type.

(5)

Number of bytes in the packet.

8

Modulo of the virtual circuit. Possible values are 8 and 128.

lci 0

VC number. Refer to Annex A of the ITU-T Recommendation X.25 for information on VC assignment.

Cause 7

Code indicating the event that triggered the packet. The Cause field can appear only in entries for Clear, Reset, and Restart packets. Possible values for the Cause field can vary, depending on the type of packet. Refer to the appendix "X.25 Cause and Diagnostic Codes" in the Cisco IOS Debug Command Reference for an explanation of these codes.

Diag 0

Code providing an additional hint of what, if anything, went wrong. The Diag field can appear only in entries for Clear, Diagnostic (as "error 0"), Reset, and Restart packets.Refer to the appendix "X.25 Cause and Diagnostic Codes" in the Cisco IOS Debug Command Reference for an explanation of these codes.

(Network operational/
No additional information)

The standard explanations of the Cause and Diagnostic codes (cause/diag).

From (6):170091

Source address. (6) indicates the number of digits in the address that follows. The source address is part of the address block that may be encoded in Call Setup packets.

To (6): 170090

Destination address. (6) indicates the number of digits in the address that follows. The destination address is part of the address block that may be encoded in Call Setup packets.

Facilities:(0)

Indicates that a facilities block is encoded and that it consists of 0 bytes. A breakdown of the encoded facilities (if any) follows.

Call User Data (4):

Indicates that the Call User Data (CUD) field is present and consists of 4 bytes.

0xCC000000 (ip)

Protocol identifier (PID). This subfield of the CUD field is presented in the output as a hexadecimal string followed by the name of the protocol (in this case, IP) that the string represents.

Any bytes following the PID are designated "user data" and may be used by an application separately from the PID.


Related Commands

Command
Description

debug x25 interface

Displays information about a specific X.25 or CMNS context or virtual circuit.

debug x25 vc

Displays information about traffic for all virtual circuits that use a given number.

debug x25 xot

Displays information about traffic to or from a specific XOT host.


debug x25 interface

To display information about the specific X.25, Annex G or CMNS contexts or virtual circuits that occur on the identified interface, use the debug x25 interface command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug x25 interface {serial-interface | cmns-interface [mac mac-address]} [vc number] [events | all] [dump]

no debug x25 interface {serial-interface | cmns-interface mac mac-address} [vc number] [events | all] [dump]

Syntax Description

serial-interface

Serial interface number that is configured for X.25 or Annex G service.

cmns-interface mac mac-address

Interface supporting CMNS traffic and, if specified, the MAC address of a remote host. The interface type can be Ethernet, Token Ring, or FDDI.

 

(Optional) MAC address of the CMNS interface and remote host.

vc number

(Optional) Virtual circuit number. Range is from 1 to 4095.

events

(Optional) Displays all traffic except Data and Receiver Ready (RR) packets.

all

(Optional) Displays all traffic. This is the default.

dump

(Optional) Displays the encoded packet contents in hexadecimal and ASCII formats.


Defaults

All traffic is displayed.

Command Modes

Privileged EXEC

Command History

Release
Modification

10.0

This command was introduced.

12.3(2)T

The dump keyword was added.


Usage Guidelines

Caution The X.25 debug commands can generate large amounts of debugging output. If logging of debug output to the router console is enabled (the default condition), this output may fill the console buffer, preventing the router from processing packets until the contents of the console buffer have been printed.

The debug x25, debug x25 interface, debug x25 vc, and debug x25 xot commands all generate the same basic output. The debug x25 interface, debug x25 vc, and debug x25 xot commands narrow the scope of the debug x25 output to specific virtual circuits or types of traffic.

The debug x25 interface command is useful for diagnosing problems encountered with a single X.25 or CMNS host or virtual circuit.

The keyword all is the default and causes all packets meeting the other debug criteria to be reported. The keyword events omits reports of any Data or RR flow control packets; the normal flow of data and RR packets is commonly large and less interesting to the user, so event reporting can significantly decrease the processor load induced by debug reporting.

Use the dump keyword to display the entire contents, including user data, of X.25 packets. The encoded X.25 packet contents are displayed after the standard packet description. The output includes the offset into the packet and the display of the data in both hexadecimal and ASCII formats.

Caution The X.25 packet information that is reported by using the dump keyword may contain sensitive data; for example, clear-text account identities and passwords. The network access policies and router configuration should be controlled appropriately to address this risk.

Examples

The following is sample output from the debug x25 interface command: 

Router# debug x25 interface serial 0


X.25 packet debugging is on

X.25 packet debugging is restricted to interface serial0


Serial0: X.25 I R/Inactive Restart (5) 8 lci 0

  Cause 7, Diag 0 (Network operational/No additional information)

Serial0: X.25 O R3 Restart Confirm (3) 8 lci 0

Serial0: X.25 I P1 Call (15) 8 lci 1

From(6): 170091 To(6): 170090

   Facilities: (0)

   Call User Data (4): 0xCC000000 (ip)

Serial0: X.25 O P3 Call Confirm (3) 8 lci 1

Serial0: X.25 I D1 Data (103) 8 lci 1 PS 0 PR 0

Serial0: X.25 O D1 Data (103) 8 lci 1 PS 0 PR 1

Serial0: X.25 I P4 Clear (5) 8 lci 1

  Cause 9, Diag 122 (Out of order/Maintenance action)

Serial0: X.25 O P7 Clear Confirm (3) 8 lci 1


Table 2 describes significant fields shown in the display.

Table 2 debug x25 interface Field Descriptions 

Field
Description

Serial0

Interface on which the X.25 event occurred.

X.25

Type of event this message describes.

I

Letter indicating whether the X.25 packet was input (I) or output (O) through the interface.

R3

State of the service or virtual circuit (VC). Possible values follow:

R/Inactive—Packet layer awaiting link layer service

R1—Packet layer ready

R2—Data terminal equipment (DTE) restart request

R3—DCE restart indication

P/Inactive—VC awaiting packet layer service

P1—Idle

P2—DTE waiting for DCE to connect CALL

P3—DCE waiting for DTE to accept CALL

P4—Data transfer

P5—CALL collision

P6—DTE clear request

P7—DCE clear indication

D/Inactive—VC awaiting setup

D1—Flow control ready

D2—DTE reset request

D3—DCE reset indication

Refer to Annex B of the ITU-T Recommendation X.25 for more information on these states.

Restart

The type of X.25 packet. Possible values follow:

R Events

•Restart

•Restart Confirm

•Diagnostic

P Events

•Call

•Call Confirm

•Clear

•Clear Confirm

D Events

•Reset

•Reset Confirm

D1 Events

•Data

•Receiver Not Ready (RNR)

•RR (Receiver Ready)

•Interrupt

•Interrupt Confirm

XOT Overhead

•PVC Setup

(5)

Number of bytes in the packet.

8

Modulo of the virtual circuit. Possible values are 8 and 128.

lci 0

VC number. Refer to Annex A of the ITU-T Recommendation X.25 for information on VC assignment.

Cause 7

Code indicating the event that triggered the packet. The Cause field can appear only in entries for Clear, Reset, and Restart packets. Possible values for the Cause field can vary, depending on the type of packet. Refer to the appendix "X.25 Cause and Diagnostic Codes" in the Cisco IOS Debug Command Reference for an explanation of these codes.

Diag 0

Code providing an additional hint of what, if anything, went wrong. The Diag field can appear only in entries for Clear, Diagnostic (as "error 0"), Reset, and Restart packets. Refer to the appendix "X.25 Cause and Diagnostic Codes" in the Cisco IOS Debug Command Reference for an explanation of these codes.

(Network operational/
No additional information)

The standard explanations of the Cause and Diagnostic codes (cause/diag).

From (6):170091

Source address. (6) indicates the number of digits in the address that follows. The source address is part of the address block that may be encoded in Call Setup packets.

To (6): 170090

Destination address. (6) indicates the number of digits in the address that follows. The destination address is part of the address block that may be encoded in Call Setup packets.

Facilities:(0)

Indicates that a facilities block is encoded and that it consists of 0 bytes. A breakdown of the encoded facilities (if any) follows.

Call User Data (4):

Indicates that the Call User Data (CUD) field is present and consists of 4 bytes.

0xCC000000 (ip)

Protocol identifier (PID). This subfield of the CUD field is presented in the output as a hexadecimal string followed by the name of the protocol (in this case, IP) that the string represents.

Any bytes following the PID are designated "user data" and may be used by an application separately from the PID.


Related Commands

Command
Description

debug x25

Displays information about all X.25 traffic or a specific X.25 service class.

debug x25 vc

Displays information about traffic for all virtual circuits that use a given number.

debug x25 xot

Displays information about traffic to or from a specific XOT host.


debug x25 vc

To display information about traffic for all virtual circuits that have a given number, use the debug x25 vc command. To disable debugging output, use the no debug x25 command.

debug x25 vc number [events | all] [dump]

no debug x25 vc number [events | all] [dump]

Syntax Description

number

Virtual circuit number. Range is from 1 to 4095.

events

(Optional) Displays all traffic except Data and Receiver Ready (RR) packets.

all

(Optional) Displays all traffic. This is the default.

dump

(Optional) Displays the encoded packet contents in hexadecimal and ASCII formats.


Defaults

All traffic is displayed.

Command Modes

Privileged EXEC

Command History

Release
Modification

10.0

This command was introduced.

12.3(2)T

The dump keyword was introduced.


Usage Guidelines

Caution The X.25 debug commands can generate large amounts of debugging output. If logging of debug output to the router console is enabled (the default condition), this output may fill the console buffer, preventing the router from processing packets until the contents of the console buffer have been printed.

The debug x25, debug x25 interface, debug x25 vc, and debug x25 xot commands all generate the same basic output. The debug x25 interface, debug x25 vc, and debug x25 xot commands narrow the scope of the debug x25 output to specific virtual circuits or types of traffic.

Because no interface is specified by the debug x25 vc command, traffic on any virtual circuit that has the specified number is reported.

Virtual circuit (VC) zero (vc 0) cannot be specified. It is used for X.25 service messages, such as RESTART packets, not virtual circuit traffic. Service messages can be monitored only when no virtual circuit filter is used.

Use the dump keyword to display the entire contents, including user data, of X.25 packets. The encoded X.25 packet contents are displayed after the standard packet description. The output includes the offset into the packet and the display of the data in both hexadecimal and ASCII formats.

Caution The X.25 packet information that is reported by using the dump keyword may contain sensitive data; for example, clear-text account identities and passwords. The network access policies and router configuration should be controlled appropriately to address this risk.

Examples

The following example show sample output for the debug x25 vc command: 

Router# debug x25 vc 1 events


X.25 special event debugging is on

X.25 debug output restricted to VC number 1


Router# show debug


X.25 (filtered for VC 1):

  X.25 special event debugging is on

*Jun 18 20:22:29.735 UTC:Serial0:X.25 O R1 Call (13) 8 lci 1

*Jun 18 20:22:29.735 UTC:  From (4):2501 To (4):2502

*Jun 18 20:22:29.735 UTC:  Facilities:(0)

*Jun 18 20:22:29.735 UTC:  Call User Data (4):0xCC000000 (ip)

*Jun 18 20:22:29.739 UTC:Serial0:X.25 I R1 Call Confirm (3) 8 lci 1

*Jun 18 20:22:36.651 UTC:Serial0:X.25 O R1 Clear (5) 8 lci 1

*Jun 18 20:22:36.651 UTC:  Cause 9, Diag 122 (Out of order/Maintenance action)

*Jun 18 20:22:36.655 UTC:Serial0:X.25 I R1 Clear Confirm (3) 8 lci 1

Table 3 describes significant fields shown in the display.

Table 3 debug x25 vc Field Descriptions 

Field
Description

Serial0

Interface on which the X.25 event occurred.

X.25

Type of event this message describes.

O

Letter indicating whether the X.25 packet was input (I) or output (O) through the interface.

R1

State of the service or virtual circuit (VC). Possible values follow:

R/Inactive—Packet layer awaiting link layer service

R1—Packet layer ready

R2—Data terminal equipment (DTE) restart request

R3—DCE restart indication

P/Inactive—VC awaiting packet layer service

P1—Idle

P2—DTE waiting for DCE to connect CALL

P3—DCE waiting for DTE to accept CALL

P4—Data transfer

P5—CALL collision

P6—DTE clear request

P7—DCE clear indication

D/Inactive—VC awaiting setup

D1—Flow control ready

D2—DTE reset request

D3—DCE reset indication

Refer to Annex B of the ITU-T Recommendation X.25 for more information on these states.

Call

The type of X.25 packet. Possible values follow:

R Events

•Restart

•Restart Confirm

•Diagnostic

P Events

•Call

•Call Confirm

•Clear

•Clear Confirm

D Events

•Reset

•Reset Confirm

D1 Events

•Data

•Receiver Not Ready (RNR)

•RR (Receiver Ready)

•Interrupt

•Interrupt Confirm

XOT Overhead

•PVC Setup

(5)

Number of bytes in the packet.

8

Modulo of the virtual circuit. Possible values are 8 and 128.

lci 0

VC number. Refer to Annex A of the ITU-T Recommendation X.25 for information on VC assignment.

From (4):2501

Source address. (4) indicates the number of digits in the address that follows. The source address is part of the address block that may be encoded in Call Setup packets.

To (4): 2502

Destination address. (4) indicates the number of digits in the address that follows. The destination address is part of the address block that may be encoded in Call Setup packets.

Facilities:(0)

Indicates that 0 bytes are being used to encode facilities.

Call User Data (4):

Indicates that the Call User Data (CUD) field is present and consists of 4 bytes.

0xCC000000 (ip)

Protocol identifier (PID). This subfield of the CUD field is presented in the output as a hexadecimal string followed by the name of the protocol (in this case, IP) that the string represents.

Any bytes following the PID are designated "user data" and may be used by an application separately from the PID.

Cause 7

Code indicating the event that triggered the packet. The Cause field can appear only in entries for Clear, Reset, and Restart packets. Possible values for the Cause field can vary, depending on the type of packet. Refer to the appendix "X.25 Cause and Diagnostic Codes" in the Cisco IOS Debug Command Reference for an explanation of these codes.

Diag 0

Code providing an additional hint of what, if anything, went wrong. The Diag field can appear only in entries for Clear, Diagnostic (as "error 0"), Reset, and Restart packets. Refer to the appendix "X.25 Cause and Diagnostic Codes" in the Cisco IOS Debug Command Reference for an explanation of these codes.

(Network operational/
No additional information)

The standard explanations of the Cause and Diagnostic codes (cause/diag).


Related Commands

Command
Description

debug x25

Displays information about all X.25 traffic or a specific X.25 service class.

debug x25 interface

Displays information about a specific X.25 or CMNS context or virtual circuit.

debug x25 xot

Displays information about traffic to or from a specific XOT host.


debug x25 xot

To display information about traffic to or from a specific X.25 over TCP (XOT) host, use the debug x25 xot command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug x25 xot [remote ip-address [port number]] [local ip-address [port number]] [events | all] [dump]

no debug x25 xot [remote ip-address [port number]] [local ip-address [port number]] [events | all] [dump]

Syntax Description

remote ip-address [port number]

(Optional) Remote IP address and, optionally, a port number. Range is from 1 to 65535.

local ip-address [port number]

(Optional) Local host IP address and, optionally, a port number. Range is from 1 to 65535.

events

(Optional) Displays all traffic except Data and Receiver Ready (RR) packets.

all

(Optional) Displays all traffic. This is the default.

dump

(Optional) Displays the encoded packet contents in hexadecimal and ASCII formats.


Defaults

All traffic is displayed.

Command Modes

Privileged EXEC

Command History

Release
Modification

10.0

This command was introduced.

12.3(2)T

The dump keyword was added.


Usage Guidelines

Caution The X.25 debug commands can generate large amounts of debugging output. If logging of debug output to the router console is enabled (the default condition), this output may fill the console buffer, preventing the router from processing packets until the contents of the console buffer have been printed.

The debug x25, debug x25 interface, debug x25 vc, and debug x25 xot commands all generate the same basic output. The debug x25 interface, debug x25 vc, and debug x25 xot commands narrow the scope of the debug x25 output to specific virtual circuits or types of traffic.

The debug x25 xot output allows you to restrict the debug output reporting to XOT traffic for one or both hosts or host/port combinations. Because each XOT virtual circuit uses a unique TCP connection, an XOT debug request that specifies both host addresses and ports will report traffic only for that virtual circuit. Also, you can restrict reporting to sessions initiated by the local or remote router by specifying 1998 for the remote or local port. (XOT connections are received on port 1998.)

Use the dump keyword to display the entire contents, including user data, of X.25 packets. The encoded X.25 packet contents are displayed after the standard packet description. The output includes the offset into the packet and the display of the data in both hexadecimal and ASCII formats.

Caution The X.25 packet information that is reported by using the dump keyword may contain sensitive data; for example, clear-text account identities and passwords. The network access policies and router configuration should be controlled appropriately to address this risk.

Examples

The following example shows sample output for the debug x25 xot command: 

Router# debug x25 xot


X.25 packet debugging is on

X.25 debug output restricted to protocol XOT


Router# show debug


X.25 (filtered for XOT):

  X.25 packet debugging is on

*Jun 18 20:32:34.699 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT I P/Inactive Call (19) 8 
lci 1

*Jun 18 20:32:34.699 UTC:  From (4):2501 To (4):2502

*Jun 18 20:32:34.699 UTC:  Facilities:(6)

*Jun 18 20:32:34.699 UTC:    Packet sizes:128 128

*Jun 18 20:32:34.699 UTC:    Window sizes:2 2

*Jun 18 20:32:34.699 UTC:  Call User Data (4):0xCC000000 (ip)

*Jun 18 20:32:34.707 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT O P3 Call Confirm (11) 8 
lci 1

*Jun 18 20:32:34.707 UTC:  From (0): To (0):

*Jun 18 20:32:34.707 UTC:  Facilities:(6)

*Jun 18 20:32:34.707 UTC:    Packet sizes:128 128

*Jun 18 20:32:34.707 UTC:    Window sizes:2 2

*Jun 18 20:32:34.715 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT I D1 Data (103) 8 lci 1 
PS 0 PR 0

*Jun 18 20:32:34.723 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT O D1 Data (103) 8 lci 1 
PS 0 PR 1

*Jun 18 20:32:34.731 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT I D1 Data (103) 8 lci 1 
PS 1 PR 1

*Jun 18 20:32:34.739 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT O D1 Data (103) 8 lci 1 
PS 1 PR 2

*Jun 18 20:32:34.747 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT I D1 Data (103) 8 lci 1 
PS 2 PR 2

*Jun 18 20:32:34.755 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT O D1 Data (103) 8 lci 1 
PS 2 PR 3

*Jun 18 20:32:34.763 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT I D1 Data (103) 8 lci 1 
PS 3 PR 3

*Jun 18 20:32:34.771 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT O D1 Data (103) 8 lci 1 
PS 3 PR 4

*Jun 18 20:32:34.779 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT I D1 Data (103) 8 lci 1 
PS 4 PR 4

*Jun 18 20:32:34.787 UTC:[10.0.155.71,11001/10.0.155.70,1998]:XOT O D1 Data (103) 8 lci 1 
PS 4 PR 5

Table 4 describes the significant fields shown in the display.

Table 4 debug x25 debug xot Field Descriptions 

Field
Description

[10.0.155.71,11001/10.0.155.70,1998]

TCP connection identified by the remote IP address, remote TCP port/local IP address, local TCP port.

An XOT connection is always placed to port ID 1998, so a remote port ID of 1998 implies that the router initiated the TCP connection, whereas a local port ID of 1998 implies that the router received the TCP connection.

XOT

Type of event this message describes.

I

Letter indicating whether the X.25 packet was input (I) or output (O) through the interface.

P/Inactive

State of the service or virtual circuit (VC). Possible values follow:

R/Inactive—Packet layer awaiting link layer service

R1—Packet layer ready

R2—Data terminal equipment (DTE) restart request

R3—DCE restart indication

P/Inactive—VC awaiting packet layer service

P1—Idle

P2—DTE waiting for DCE to connect CALL

P3—DCE waiting for DTE to accept CALL

P4—Data transfer

P5—CALL collision

P6—DTE clear request

P7—DCE clear indication

D/Inactive—VC awaiting setup

D1—Flow control ready

D2—DTE reset request

D3—DCE reset indication

Refer to Annex B of the ITU-T Recommendation X.25 for more information on these states.

Call

The type of X.25 packet. Possible values follow:

R Events

•Restart

•Restart Confirm

•Diagnostic

P Events

•Call

•Call Confirm

•Clear

•Clear Confirm

D Events

•Reset

•Reset Confirm

D1 Events

•Data

•Receiver Not Ready (RNR)

•RR (Receiver Ready)

•Interrupt

•Interrupt Confirm

XOT Overhead

•PVC Setup

(19)

Number of bytes in the packet.

8

Modulo of the virtual circuit. Possible values are 8 and 128.

lci 1

VC number. Refer to Annex A of the ITU-T Recommendation X.25 for information on VC assignment.

From (4):2501

Source address. (4) indicates the number of digits in the address that follows. The source address is part of the address block that may be encoded in Call Setup packets.

To (4): 2502

Destination address. (4) indicates the number of digits in the address that follows. The destination address is part of the address block that may be encoded in Call Setup packets.

Facilities:(6)

Indicates that a facilities block is encoded and that it consists of 6 bytes. A breakdown of the encoded facilities follows.

Packet sizes

Encoded packet size facility settings.

Window sizes

Encoded window size facility settings.

Call User Data (4):

Indicates that the Call User Data (CUD) field is present and consists of 4 bytes.

0xCC000000 (ip)

Protocol identifier (PID). This subfield of the CUD field is presented in the output as a hexadecimal string followed by the name of the protocol (in this case, IP) that the string represents.

Any bytes following the PID are designated "user data" and may be used by an application separately from the PID.

Cause 7

Code indicating the event that triggered the packet. The Cause field can appear only in entries for Clear, Reset, and Restart packets. Possible values for the Cause field can vary, depending on the type of packet. Refer to the appendix "X.25 Cause and Diagnostic Codes" in the Cisco IOS Debug Command Reference for an explanation of these codes.

Diag 0

Code providing an additional hint of what, if anything, went wrong. The Diag field can appear only in entries for Clear, Diagnostic (as "error 0"), Reset, and Restart packets. Refer to the appendix "X.25 Cause and Diagnostic Codes" in the Cisco IOS Debug Command Reference for an explanation of these codes.

(Network operational/
No additional information)

The standard explanations of the Cause and Diagnostic codes (cause/diag).


Related Commands

Command
Description

debug x25

Displays information about all X.25 traffic or a specific X.25 service class.

debug x25 interface

Displays information about a specific X.25 or CMNS context or virtual circuit.

debug x25 vc

Displays information about traffic for all virtual circuits that use a given number.


Copyright © 2003 Cisco Systems, Inc. All rights reserved.