Table Of Contents
X.25 Station Type for ISDN D-channel Interface
Prerequisites for X.25 Station Type for ISDN D-channel Interface
Information About X.25 Station Type for ISDN D-channel Interface
Configuring X.25 on ISDN D-channel Interface
How to Configure X.25 Encapsulation on ISDN BRI D-channel Interface
Configuring X.25 Encapsulation on ISDN BRI D-channel Interface
Configuration Examples for X.25 Encapsulation on ISDN BRI D-channel Interface
X.25 Encapsulation on an ISDN BRI D-channel Interface: Example
X.25 Station Type for ISDN D-channel Interface
The X.25 Station Type for ISDN D-channel Interface feature permits configuration of the X.25 station type for the ISDN D-channel interface with the encapsulation x25 command on this interface. This feature allows the mapping of closed user group (CUG) of the X.25 packets that originates from the point-of-sale devices terminating the ISDN-BRI D-channel interface configured as an X.25 data communications equipment (DCE) station of Cisco routers with an ISDN BRI interface.
The default encapsulation of the BRI D-channel interface is X.25 encapsulation in data terminal equipment (DTE) mode. To change the X.25 station type on the ISDN BRI D-channel interface, use the encapsulation 25 command with the appropriate keyword in the interface configuration mode. If no keyword is specified, the interface will be configured with X.25 encapsulation in DTE mode.
When a router boots up with the new ISDN BRI interface, the encapsulation will not show up explicitly in the ISDN BRI D-channel interface configuration although the encapsulation will be set as an X.25 DTE station, the default for this interface. When the no encapsulation command is issued on the ISDN BRI D-channel interface, the interface will be set as an X.25 DTE station, the default. This will show up in the running configuration of the interface as encapsulation x25.
Feature History for X.25 Station Type for ISDN D-channel Interface
12.3(7)XR
This feature was introduced.
12.3(14)T
This feature was integrated into Cisco IOS Release 12.3(14)T.
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
•
Prerequisites for X.25 Station Type for ISDN D-channel Interface
•
•
•
Prerequisites for X.25 Station Type for ISDN D-channel Interface
•
For more details, see the following URL:
/en/US/docs/ios/12_3/dial/command/reference/dia_i2g.html#1050084
•
Information About X.25 Station Type for ISDN D-channel Interface
To configure the X.25 Station Type for ISDN D-channel Interface feature, you should understand the following concepts:
•
Configuring X.25 on ISDN D-channel Interface
If the D channel of an ISDN BRI interface will carry X.25 traffic, you need to configure the feature that is described in the Configuring X.25 on ISDN feature guide.
A BRI is an ISDN interface. It consists of two B channels (B1 and B2) and one D-channel. The B channels are used to transfer data, voice, and video. The D channel controls the B channels.
ISDN uses the D-channel to carry signal information. ISDN can also use the D-channel in a BRI to carry X.25 packets. The D-channel has a capacity of 16 kbps; the X.25 over D-channel can use up to 9.6 kbps.
When this feature is configured, a separate X.25-over-D-channel logical interface is created. You can set its parameters without disrupting the original ISDN interface configuration. The original BRI interface will continue to represent the D, B1, and B2 channels.
An interface configured for X.25 traffic over the D channel can be used as a primary interface where low-volume, sporadic, interactive traffic is the normal mode of operation. Supported traffic includes IPX, AppleTalk, transparent bridging, XNS, DECnet, and IP.
For more details on how to configure the X.25 over ISDN D-channel Interface feature, see the following URL:
X.25 Closed User Groups
A closed user group (CUG) is a collection of DTE devices for which the network controls access between two members and between a member and a non-member. An X.25 network can support up to 10,000 CUGs (numbered between 0 and 9999), each of which can have any number of member DTE devices. An individual DTE becomes a member of a specific network CUG by subscription. The subscription data includes the local number that the DTE will use to identify the network CUG (which may or may not be the same as the network number, as determined by network administration and the DTE device's requirements), and any restriction that prohibits the DTE from placing a call within the CUG or, conversely, prohibits the network from presenting a call within the CUG to the DTE.
With the X.25 CUGs feature, the router's X.25 DCE interfaces can be configured to perform the standard CUG access controls that are normally associated with a direct attachment to an X.25 network point of presence (POP). The router's DCE interface acts as the boundary between the DTE and the network, and CUG use ensures that only those incoming and outgoing switched virtual circuits (SVCs) consistent with the configured CUG subscriptions are permitted. X.25 CUG configuration commands on the router are specified at every POP, and CUG security decisions are made solely from those commands.
The X.25 CUGs feature is used for additional X.25 access protection and security. In a setup where DTE devices are attached to a public data network (PDN), you can derive a private subnetwork by subscribing your DTE devices to a set of CUGs, which allows closer control of your DTE devices, such as permitting or restricting which DTE can talk to other DTE devices and for what particular purpose. For example, a distinct CUG can be defined to handle each of the different modes of connectivity, such as following:
•
•
•
•
For more details, see the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/x25scugs.htm
How to Configure X.25 Encapsulation on ISDN BRI D-channel Interface
This section contains following procedure:
•
Configuring X.25 Encapsulation on ISDN BRI D-channel Interface
To configure X.25 encapsulation on ISDN BRI D-channel Interface, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
Note
DETAILED STEPS
Examples
The following example configures the X.25 encapsulation in DCE mode on an BRI interface 2/0:0:
interface BRI2/0:0ip address 1.1.1.2 255.255.255.0encapsulation X.25 dceno ip mroute-cacheX.25 subscribe cug-serviceX.25 subscribe local-cug 10 network-cug 100!Configuration Examples for X.25 Encapsulation on ISDN BRI D-channel Interface
This section provides following configuration example:
•
X.25 Encapsulation on an ISDN BRI D-channel Interface: Example
The following example shows X.25 encapsulation configured on interface BRI2/0:
Current configuration: 2275 bytes!version 12.3service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname Router!boot system flash c1700-voice-mzenable password cisco!memory-size iomem 15tdm clock bri-autovoice-card 2!no aaa new-modelip subnet-zero!!!no ftp-server write-enableisdn switch-type basic-net3!no voice hpi capture bufferno voice hpi capture destination!interface FastEthernet0/0ip address 10.0.2.199 255.255.255.0speed 100!interface BRI2/0no ip addressisdn switch-type basic-net3isdn protocol-emulate networkisdn layer1-emulate networkno isdn outgoing display-ieisdn x25 static-tei 1isdn x25 dchannelisdn skipsend-idverify!interface BRI2/0:0no ip addressencapsulation x25 dcex25 subscribe cug-service incoming-access outgoing-accessx25 subscribe local-cug 5000 network-cug 55 preferential!interface BRI2/1no ip addressshutdownisdn switch-type basic-net3!ip classlessno ip http server!voice-port 2/0!voice-port 2/1!line con 0line aux 0line vty 0 4login!endAdditional References
The following sections provide references related to the X.25 Station Type for ISDN D-channel Interface feature.
Related Documents
Cisco IOS Release 12.3 Configuration Guides and Command References
Cisco IOS Release 12.3 Configuration Guides and Command References
Cisco IOS Dial Technologies Command Reference, Release 12.3
"Dial Technologies Commands: isdn all through isdn x25" section in Cisco IOS Dial Technologies Command Reference, Release 12.3
Standards
MIBs
•
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Command Reference
This feature uses no new or modified commands. All commands used with this feature are documented in the Cisco IOS Release 12.3 command reference publications.
•
•
•
•
•
encapsulation x25
To specify a serial interface's operation as an X.25 device, use the encapsulation x25 command in interface configuration mode. To remove the specification, use the no form of this command.
encapsulation x25 [dte | dce] [ddn | bfe | ietf]
no encapsulation x25 [dte | dce] [ddn | bfe | ietf]
Syntax Description
Defaults
The default serial encapsulation is High-Level Data Link Control (HDLC). You must explicitly configure an X.25 encapsulation method.
DTE operation is the default X.25 mode. Cisco's traditional X.25 encapsulation method is the default.
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
10.3
The following keywords were added:
•
•
•
•
•
12.3(14)T
This command was integrated into Cisco IOS Release 12.3(14)T.
Usage Guidelines
One end of an X.25 link must be a logical DCE device and the other end a logical DTE device. (This assignment is independent of the interface's hardware DTE or DCE identity.) Typically, when connecting to a public data network (PDN), the customer equipment acts as the DTE device and the PDN attachment acts as the DCE.
Cisco has long supported the encapsulation of a number of datagram protocols, using a standard means when available and a proprietary means when necessary. The IETF adopted a standard, RFC 1356, for encapsulating most types of datagram traffic over X.25. X.25 interfaces use Cisco's traditional method unless explicitly configured for IETF operation; if the ietf keyword is specified, that standard is used unless Cisco's traditional method is explicitly configured. For details see the x25 map command.
You can configure a router attaching to the DDN or to a BFE device to use their respective algorithms to convert between IP and X.121 addresses by using the ddn or bfe option, respectively. An IP address must be assigned to the interface, from which the algorithm will generate the interface's X.121 address. For proper operation, this X.121 address must not be modified.
A router DDN attachment can operate as either a DTE or a DCE device. A BFE attachment can operate only as a DTE device. The ietf option is not available if either the ddn or bfe option is selected.
Examples
The following example configures the interface for connection to a BFE device:
interface serial 0encapsulation x25 bfeRelated Commands
x25 subscribe cug-service
To enable and control standard closed user group (CUG) service, use the x25 subscribe cug-service command in the appropriate interface, line, or X.25 profile configuration mode. To disable standard CUG service, use the no form of this command.
x25 subscribe cug-service [incoming-access] [outgoing-access] [suppress preferential | suppress all]
no x25 subscribe cug-service [incoming-access | outgoing-access] [suppress preferential | suppress all]
Syntax Description
Defaults
No incoming access and no outgoing access. (This is the most restrictive setting.)
CUG selection facilities are not suppressed.Command Modes
Interface configuration
Line configuration
X.25 profile configurationCommand History
Usage Guidelines
When entering this command, specify the incoming-access or the outgoing-access keyword or both, unless you intend to have neither incoming nor outgoing access on the interface.
This command assumes that an X.25 network connection is being implemented and observes rules defined by X.25 and X.301 for CUG access. This command is enabled on a per-interface or per-line basis. Use this command to modify existing specified options without otherwise affecting the CUGs already defined.
The x25 subscribe cug-service command can be used to configure CUG security on synchronous X.25 data communications equipment (DCE) interfaces or terminal lines. A CUG service can be applied to console lines, auxiliary lines, standard asynchronous lines, and virtual terminal lines. A line configured for CUG service will apply CUG security to packet assembler/disassembler (PAD), X.28 mode, and protocol translation sessions. CUG protection is applied to incoming calls destined for the terminal line and call requests specified from the line.
The CUG selection facility suppression options are not available for terminal lines because incoming PAD calls are terminated by the line.
Use the x25 subscribe cug-service command with the suppress preferential or suppress all keywords to configure CUG selection facility suppression. The CUG selection facility suppression options are available on synchronous X.25 DCE interfaces only; they are not available on terminal lines because incoming PAD calls are terminated by the line.
The following restrictions apply to the x25 subscribe cug-service command:
•
•
•
Examples
CUG Service on a Terminal Line Example
The following example shows the configuration of CUG behavior on asynchronous line 1 and virtual terminal lines 0 to 9. The users of virtual terminal lines 0 to 9 have access only within the corporate CUGs designated for engineering (CUG 1102 or 1103); any call from a network X.25-class service destined for the line will be refused unless the inbound point of presence (POP) has validated it as a member of one of those two CUGs.
line vty 0 9Location Company A. Engineering Accessx25 subscribe cug-servicex25 subscribe local-cug 2 network-cug 1102 preferentialx25 subscribe local-cug 3 network-cug 1103CUG Service with CUG Selection Facility Suppression and Incoming Access Example
In the following example, CUG selection facility suppression and incoming access are configured for all CUGs, including the preferred CUG on the X.25 profile:
x25 profile CUG-SUPRS-ALL dcex25 subscribe cug-service incoming-access suppress allx25 subscribe local-cug 0 network-cug 10 preferentialx25 subscribe local-cug 20 network-cug 202x25 subscribe local-cug 40 network-cug 40CUG Service with Incoming and Outgoing Access Example
The following example shows subscribing to both incoming and outgoing CUG service on the interface:
interface serial0encapsulation x25 dcex25 subscribe cug-service incoming-access outgoing-accessRelated Commands
x25 subscribe local-cug
To configure subscription to a specific closed user group (CUG), use the x25 subscribe local-cug command in interface configuration or line configuration mode. To remove the CUG subscription, use the no form of this command.
x25 subscribe local-cug number network-cug number [no-incoming | no-outgoing | preferential]
no x25 subscribe local-cug number network-cug number [no-incoming | no-outgoing | preferential]
Syntax Description
Defaults
Incoming and outgoing access.
Preferential (if this is the only CUG specified).Command Modes
Interface configuration
Line configurationCommand History
Usage Guidelines
The first x25 subscribe local-cug command in a group of configurations will automatically enable CUG service behavior on the interface or line, if it is not already enabled, with the default setting of no public access.
The x25 subscribe cug-service command can be used to configure CUG subscription on X.25 synchronous data communications equipment (DCE) interfaces, console lines, auxiliary lines, standard asynchronous lines, and virtual terminal lines. A line configured for CUG service will apply CUG security to packet assembler/disassembler (PAD), X.28 mode, and protocol translation sessions. CUG protection is applied to incoming calls destined for the terminal line and call requests specified from the line.
A CUG number has only local significance. Because CUG service is a cooperative process among the network attachments (DCE devices), the local CUG number may have to be translated into a number that is significant to the network as a whole. For instance, two DTE devices may use CUG numbers 1 and 5 to refer to the global CUG number 1043 of the network. In this instance, both DCE devices would be configured to translate between the local CUG number of their DTE and the network CUG number. Duplicate network CUG identifiers are permitted for different local CUG identifiers.
A DTE subscription to a CUG that also includes the no-incoming option prevents incoming calls on that CUG (however, the DTE may still receive calls within other CUGs to which it is subscribed, or from the open network if incoming public access is subscribed).
CUG subscription of a DTE will not permit an outgoing call (call request) from the CUG if the no-outgoing option is configured.
The CUG will be assumed to be set to preferential (preferred) if there is only one CUG subscribed on that interface.
Examples
X.25 CUG Subscription on an Interface Example
The following example subscribes local CUGs 5000, 100, 200, and 300 to networks 55, 11, 22, and 33, respectively, with local CUG 5000 being set as the preferred CUG:
Router(config)# interface serial0Router(config-if)# encapsulation x25 dceRouter(config-if)# x25 subscribe cug-service incoming-access outgoing-accessRouter(config-if)# x25 subscribe local-cug 5000 network-cug 55 preferentialRouter(config-if)# x25 subscribe local-cug 100 network-cug 11Router(config-if)# x25 subscribe local-cug 200 network-cug 22Router(config-if)# x25 subscribe local-cug 300 network-cug 33X.25 CUG Subscription on a Terminal Line Example
The following example shows the configuration of CUG behavior on asynchronous line 1 and virtual terminal lines 0 to 9. The users of virtual terminal lines 0 to 9 have access only within the corporate CUGs designated for engineering (CUG 1102 or 1103); any call from a network X.25-class service destined for the line will be refused unless the inbound POP has validated it as a member of one of those two CUGs.
Router(config)# line vty 0 9Router(config-line)# Location Company A. Engineering AccessRouter(config-line)# x25 subscribe cug-serviceRouter(config-line)# x25 subscribe local-cug 2 network-cug 1102 preferentialRouter(config-line)# x25 subscribe local-cug 3 network-cug 1103Related Commands
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
Defaults
All traffic is displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Caution
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
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 x25Serial0: X.25 I R/Inactive Restart (5) 8 lci 0Cause 7, Diag 0 (Network operational/No additional information)Serial0: X.25 O R3 Restart Confirm (3) 8 lci 0Serial0: X.25 I P1 Call (15) 8 lci 1From(6): 170091 To(6): 170090Facilities: (0)Call User Data (4): 0xCC000000 (ip)Serial0: X.25 O P3 Call Confirm (3) 8 lci 1Serial0: X.25 I D1 Data (103) 8 lci 1 PS 0 PR 0Serial0: X.25 O D1 Data (103) 8 lci 1 PS 0 PR 1Serial0: X.25 I P4 Clear (5) 8 lci 1Cause 9, Diag 122 (Out of order/Maintenance action)Serial0: X.25 O P7 Clear Confirm (3) 8 lci 1debug x25 events for DNS-Based X.25 Routing: Example
The following example of the debug x25 command with the events keyword 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 events00:18:25:Serial1:X.25 I R1 Call (11) 8 lci 102400:18:25: From (0): To (4):44400: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 DNS00:18:26:DNS got X.25 host mapping for "444" via network00: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 100:20:04: From (0): To (4):44400:20:04: Facilities:(6)00:20:04: Packet sizes:128 12800:20:04: Window sizes:2 200: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 100:20:04: From (0): To (0):00:20:04: Facilities:(6)00:20:04: Packet sizes:128 12800:20:04: Window sizes:2 200:20:04:Serial1:X.25 O R1 Call Confirm (5) 8 lci 102400:20:04: From (0): To (0):00:20:04: Facilities:(0)Record Boundary Preservation: Examples
The following examples show output for the x25 debug command with the events keyword 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 11001Serial0/1:X.25 O R1 Call (10) 8 lci 64From (5):13133 To (5):12131Facilities:(0)Serial0/1:X.25 I R1 Call Confirm (3) 8 lci 64The 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 64Cause 0, Diag 122 (DTE originated/Maintenance action)X25 RBP:X.25 circuit clearedSerial0/1:X.25 O R1 Clear Confirm (3) 8 lci 64The 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 transferX25 RBP:End of data transferSerial0/1:X.25 O R1 Clear (5) 8 lci 64Cause 9, Diag 122 (Out of order/Maintenance action)Serial0/1:X.25 I R1 Clear Confirm (3) 8 lci 64The following examples show output of the x25 debug command with the events keyword 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 PVCSerial1/0:X.25 O D1 Reset (5) 8 lci 1Cause 0, Diag 113 (DTE originated/Remote network problem)Serial1/0:X.25 I D2 Reset Confirm (3) 8 lci 1The following display shows establishment of connection:
X25 RBP:Incoming connection for port 9998 from 2.30.0.30 port 11002Serial1/0:X.25 O D1 Reset (5) 8 lci 1Cause 0, Diag 0 (DTE originated/No additional information)Serial1/0:X.25 I D2 Reset Confirm (3) 8 lci 1The following display shows termination of connection when the X.25 PVC was reset:
Serial1/0:X.25 I D1 Reset (5) 8 lci 1Cause 15, Diag 122 (Network operational (PVC)/Maintenance action)X25 RBP:Reset packet receivedSerial1/0:X.25 O D3 Reset Confirm (3) 8 lci 1The 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 transferX25 RBP:End of data transferSerial1/0:X.25 O D1 Reset (5) 8 lci 1Cause 0, Diag 113 (DTE originated/Remote network problem)Serial1/0:X.25 I D2 Reset Confirm (3) 8 lci 1The following examples show output of the x25 debug command with the events keyword 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 1024Cause 0, Diag 122 (DTE originated/Maintenance action)X25 RBP:X.25 circuit clearedSerial0/1:X.25 O R1 Clear Confirm (3) 8 lci 1024The following display shows that the X.25 call was reset:
Serial0/1:X.25 I D1 Reset (5) 8 lci 1024Cause 0, Diag 122 (DTE originated/Maintenance action)X25 RBP:Reset packet receivedSerial0/1:X.25 O R1 Clear (5) 8 lci 1024Cause 9, Diag 122 (Out of order/Maintenance action)Serial0/1:X.25 I R1 Clear Confirm (3) 8 lci 1024The following examples show output of the x25 debug command with the events keyword 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 1Cause 0, Diag 122 (DTE originated/Maintenance action)X25 RBP:Reset packet receivedSerial0/0:X.25 O D2 Reset Confirm (3) 8 lci 1The 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 0Cause 0, Diag 122 (DTE originated/Maintenance action)X25 RBP:X.25 PVC inactiveSerial0/0:X.25 O R2 Restart Confirm (3) 8 lci 0Serial0/0:X.25 O D1 Reset (5) 8 lci 1Cause 1, Diag 113 (Out of order (PVC)/Remote network problem)Serial0/0:X.25 I D3 Reset Confirm (3) 8 lci 1debug x25 dump Example
The following is sample output for the debug x25 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 dumpSerial1: X.25 O R/Inactive Restart (5) 8 lci 0Cause 0, Diag 0 (DTE originated/No additional information)0: 1000FB00 00 ..{..Serial1: X.25 I R2 Restart (5) 8 lci 0Cause 7, Diag 0 (Network operational/No additional information)0: 1000FB ..{3: 0700 ..Serial1: X.25 I R1 Call (13) 8 lci 1From (4): 2501 To (4): 2502Facilities: (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 10: 10010F ...Serial1: X.25 I D1 Data (103) 8 lci 1 PS 0 PR 00: 100100 45000064 00000000 ...E..d....11: FF01A764 0A190001 0A190002 0800CBFB ..'d..........K{27: 0B1E22CA 00000000 00028464 ABCDABCD .."J.......d+M+M43: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M59: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M75: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M91: ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+MSerial1: X.25 O D1 Data (103) 8 lci 1 PS 0 PR 10: 100120 45000064 00000000 .. E..d....11: FF01A764 0A190002 0A190001 0000D3FB ..'d..........S{27: 0B1E22CA 00000000 00028464 ABCDABCD .."J.......d+M+M43: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M59: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M75: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M91: ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+MSerial1: X.25 I R1 Clear (5) 8 lci 1Cause 9, Diag 122 (Out of order/Maintenance action)0: 100113 097A ....zSerial1: X.25 O R1 Clear Confirm (3) 8 lci 10: 100117 .Table 1 describes significant fields shown in the displays.
Related Commands
show x25 cug
To display information about all closed user groups (CUGs) or specific CUGs (defined by the local or network CUG number), use the show x25 cug command in EXEC mode.
show x25 cug {local-cug [number] | network-cug [number]}
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
You must designate either the local CUG or the network CUG by the choice of keyword. Within that designation you can view all CUGs or a specific CUG defined by its local or network CUG identifier.
Examples
CUG Selection Facility Suppress Option Example
The following is sample output for the show x25 cug command when CUG selection facility is suppressed for all CUGs on serial interface 1/2 and for the preferential CUG on the X.25 profile named "cug".
Router# show x25 cug local-cugX.25 Serial1/2, 2 CUGs subscribed with no public accessCUG selection facility suppressed for all CUGslocal-cug 100 <-> network-cug 10local-cug 1 <-> network-cug 11PROFILE cug, 2 CUGs subscribed with incoming public accessCUG selection facility suppressed for preferential CUGlocal-cug 0 <-> network-cug 0 , preferentiallocal-cug 100 <-> network-cug 100local-cug 200 <-> network-cug 200Local CUG Example
The following sample output from the show x25 cug local-cug command displays information about all local CUGs on configured on the router.
Router# show x25 cug local-cugX.25 Serial1/1, 3 CUGs subscribed with no public accesslocal-cug 99 <-> network-cug 9999, no-incoming, preferentiallocal-cug 100 <-> network-cug 1000local-cug 101 <-> network-cug 1001PROFILE cugs, 2 CUGs subscribed with with incoming public accesslocal-cug 1 <-> network-cug 10, no-outgoinglocal-cug 2 <-> network-cug 20, no-incoming, preferentialLine: 129 aux 0 , 1 CUGs subscribed with outgoing public accesslocal-cug 1 <-> network-cug 10Line: 130 vty 0 , 4 CUGs subscribed with incoming and outgoing public accesslocal-cug 1 <-> network-cug 10local-cug 50 <-> network-cug 5, preferentiallocal-cug 60 <-> network-cug 6, no-incominglocal-cug 70 <-> network-cug 7, no-outgoingLine: 131 vty 1 , 1 CUGs subscribed with no public accesslocal-cug 1 <-> network-cug 10Network CUG Example
The following is sample output from the show x25 cug network-cug command specifically for network number 10 showing that local CUG 1 is associated with it.
Router# show x25 cug network-cug 10X.25 Serial1/2, 5 CUGs subscribed with no public accessnetwork-cug 10 <-> local-cug 1PROFILE cugs, 2 CUGs subscribed with no public accessnetwork-cug 10 <-> local-cug 1 , no-outgoingLine: 129 aux 0 , 1 CUGs subscribed with no public accessnetwork-cug 10 <-> local-cug 1Line: 130 vty 0 , 4 CUGs subscribed with incoming and outgoing public accessnetwork-cug 10 <-> local-cug 1Line: 131 vty 1 , 1 CUGs subscribed with no public accessnetwork-cug 10 <-> local-cug 1Table 52 describes the significant fields shown in the displays.
Related Commands
Copyright © 2004, 2005 Cisco Systems, Inc. All rights reserved.
Guest
