Cisco Network Solutions for the Telco DCN: Telephone Switch Environments
Available Languages
Table Of Contents
Cisco Network Solutions for the Telco DCN: Telephone Switch Environments
BX.25 as a DCN Transport Mechanism
Differences Between BX.25 and X.25
Cisco Telephone Switch Migration Solutions Overview
CDR Bill Collection Networks: Cisco XOT and RBP Solutions
Cisco XOT Features for Transporting CDR Data
Configuring XOT on the Billing Collector Side of the Network
Configuring XOT on the Telephone Switch Side of the Network
Sterling 5000 Collector Configuration: Examples
Configuring a Cisco Router for a Host That Supports XOT
Mercury Mediation Bill Collector That Supports XOT: Example
Verifying the SVC Connection on the Mercury Mediation Device
Cisco RBP and RBP Q-Bit Features for Transporting CDR Data
RBP and RBP Q-Bit File Type Compatibility
Configuring a Cisco Router for a CDR Host That Supports the RBP Feature
Cisco X.25 RBP with the Inter-mediatE to a Lucent 5ESS Switch: Example
Cisco X.25 RBP with the Inter-mediatE to a Nortel DMS 100 Switch: Example
Configuring the Cisco X.25 RBP Q-Bit Feature for the MTP File Type
Cisco X.25 RBP Q-Bit Feature with the Inter-mediatE to a Class 5 Switch with MTP File Type: Example
Configuring the Cisco X.25 RBP Q-Bit Feature for the MNP File Type
Cisco X.25 RBP Q-Bit Feature with the Inter-mediatE to a Class 5 Switch with MNP File Type: Example
Debugging an X.25 Serial Connection
Debugging the RBP Configuration
Configuring an Intec Telecom Systems Inter-mediatE System
Switch Monitoring Networks: Cisco STUN OSS Connectivity Solution
Migrating to TCP/IP Using Cisco STUN
Configuring STUN on the Workstation Side of the Network
Configuring STUN on the Telephone Switch Side of the Network
Cisco STUN OSS Connectivity Solution: Examples
Verifying Links in the Cisco STUN OSS Connectivity Solution
Switch Monitoring Networks: Cisco X.25 BAI OSS Connectivity Solution
Cisco X.25 BAI OSS Connectivity Overview
Adding Cisco X.25 BAI to the Telco DCN
Configuring Cisco X.25 BAI on the NMA Side of the Network
NMA Gateway Configuration: Example
NMA-Side Configuration: Example
Verifying Address Substitutions
Configuring Cisco X.25 BAI on the Telephone Switch Side of the Network
X.25 BAI Telephone Switch Side Configuration: Example
Verifying PVC-to-SVC Conversions
Configuring SCC0 and SCC1 on the Lucent 5ESS Telephone Switch Form
Lucent DRM-Side Configuration: Example
Application Host Configuration: Example
Switch Monitoring Networks: IP and Cisco X.25 BAI and EOR Solutions
Configuring a Cisco Router with X.25 BAI and EOR on the Telephone Switch Side of the Network
Cisco Router with X.25 BAI and EOR on the Telephone Switch Side of the Network: Example
Verifying Cisco X.25 BAI and EOR Configurations
TTI Telecom Monitoring Application Cisco X.25 BAI Solution
Provisioning Networks: Cisco X.25 RBP Solution
Cisco X.25 RBP Solution Overview
Adding Cisco X.25 RBP to the Telco DCN Provisioning Connection
Configuring the CONNECTVU-ATP Application
Configuring the Lucent 5ESS Echo Back Port
Configuring the Echo Back Port on the Cisco Router
Echo Back Port Configuration: Example
Configuring the Lucent 5ESS Recent Change Port
Configuring the Recent Change Port on the Cisco Router
Recent Change Port Configuration: Example
Debugging the Echo Back and Recent Change Ports
Configuring ADC Service Activation Provisioning
ADC Service Activation Provisioning: Example
Traffic Data Collection Networks: Cisco X.25 RBP and XOT Solutions
Adding Cisco X.25 RBP to the Telco DCN Traffic Data Collection Connection
Configuring Cisco X.25 RBP for Traffic Data Collection Applications
Cisco X.25 RBP in the Traffic Data Collection Application: Example
Debugging the Traffic Data Collection Connection
Configuring the Lucent 5ESS EDAS Port
Lucent cpblx Form Parameter Descriptions
Cisco Network Solutions for the Telco DCN: Telephone Switch Environments
Information in this document is directed to competitive local exchange carriers (CLECs), incumbent local exchange carriers (ILECs), and Post, Telephone, and Telegraph (PTT) agencies, collectively referred to as telcos (short for telephone companies). This document provides descriptions of Cisco network solutions for transporting data between a telephone switch and the Operations Support Systems (OSSs) in a telco data communications network (DCN).
The DCN transports network management traffic between network elements and their respective OSSs, making them a vital link between the service network and the network operations center (NOC). The solutions presented in following sections will help telcos migrate their legacy networks to a router-based TCP/IP network, which will simplify the DCN and reduce equipment costs.
Version History
Contents
Several methods for implementing the migration to TCP/IP are described in this document, including detailed configuration examples for migrating the host applications that preserve the legacy transport connection on the telephone switch. These migration methods are provided in the following sections:
•
Cisco Telephone Switch Migration Solutions Overview
•
•
•
•
•
•
•
Prerequisites
The features described in this document are supported on the Cisco Telco and Enterprise feature sets.
Cisco IOS software is packaged in feature sets that are supported on specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator at http://www.cisco.com/go/fn.
To access Cisco Feature Navigator, you must have an account on Cisco.com. Qualified users can establish an account on Cisco.com by following the directions at http://www.cisco.com/register. If you have an account but have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you.
The Telco DCN Network
The telco DCN is an out-of-band operations support network used to connect telco central office (CO) equipment to a NOC. As part of the International Telecommunication Union (ITU) Telecommunications Management Network (TMN) specification defined by ITU-T M.3010, the DCN provides the link between the service network and the NOC. The specification defines the management requirements of DCN administrators to plan, provision, install, maintain, operate, and administer telecommunications networks and services. The primary function of the DCN is to enable surveillance and monitor the status of the support network, yet it also supports Operations, Administration, Maintenance, and Provisioning (OAM&P) functions including monitoring alarms and the trunk, collecting billing information, and network provisioning tasks.
Figure 1 shows the elements of a typical DCN network.
Figure 1 Typical DCN Network Elements
Multiple networks are included in the DCN network cloud. The networks serve to connect a mainframe or minicomputer and workstation configured as an OSS at a NOC, to a large array of devices and systems referred to as network elements.
Network elements in a DCN include alarm units, Class 4 and 5 telephone switches such as the Lucent 5ESS, add/drop multiplexers (ADMs) and optical repeaters, voice switches, digital cross-connect systems, Frame Relay or ATM switches, routers, digital subscriber line access multiplexers (DSLAMs), remote access switches, digital loop transmission systems, and so on, that make up the provisioned services infrastructure used to deliver services to customers. The OSS controls and stores the network management data collected about and from the various network elements.
BX.25 Overview
The following sections provide an overview of the BX.25 protocol:
•
BX.25 as a DCN Transport Mechanism
The regional Bell operating companies (RBOCs) and other incumbent local exchange carriers (ILECs) use the BX.25 protocol and the X.25 protocol to transport monitoring data, traffic data, and provisioning data between a Class 4 or Class 5 telephone switch and an OSS in their DCNs.
BX.25 is a variation of the ITU X.25 standard introduced in the early 1980s by AT&T Bell Laboratories. BX.25 contains many of the features standardized in the 1984 ITU X.25 standards, but adds some special features above Layer 3 of the Open System Interconnection (OSI) protocol stack. (Information presented here focuses only on the first three layers of the OSI protocol stack—the physical, data link, and network layers—and does not address the upper layer requirements of BX.25 such as the Transaction-Oriented Protocol).
Differences Between BX.25 and X.25
Many voice switch manufacturers use the BX.25 interface on the maintenance port. BX.25 or X.25 interfaces are also found on products such as the Lucent 5ESS/4ESS, Lucent 1A, Nortel DMS100, and Siemens Elektronisches Wahlsystem Digital (EWSD) telephone switches. These voice switches are used by many RBOCs, competitive local exchange carriers (CLECs), Post, Telephone, and Telegraph (PTT) organizations, and international exchange carriers.
The main difference between X.25 and BX.25 can be found in BX.25 Issue 3, which is also the basis for the migration strategies presented in the following sections.
BX.25 Issue 3 can be configured for use over point-to-point networks, over dialup connections, or over packet-switched networks. The solutions presented in the following sections show techniques available from Cisco IOS software to replicate the point-to-point environment and the packet-switched network environment over a TCP/IP backbone. The BX.25 protocol as of Issue 3 is compatible with Issue 1980 of the Consultative Committee for International Telegraph and Telephone (CCITT) recommendation for X.25. At the physical layer, BX.25 supports the CCITT V.35 EIA/TIA-232C and EIA/TIA-449 interfaces. (Note that the Cisco IOS software allows you to select either the 1980 or 1984 version of X.25 using the x25 version command. See the X.25 Version Configuration document at http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a0080455518.html.)
Cisco Telephone Switch Migration Solutions Overview
Solutions for that part of the DCN that uses BX.25 as a transport mechanism to a Class 4 or Class 5 telephone switch are described in following sections. You will see examples mainly of connectivity to a Lucent 5ESS telephone switch, although examples for Siemens and Nortel telephone switches are also included, and the procedures provided can be applied to DCNs with other types of switches and equipment.
Figure 2 shows a Lucent 5ESS telephone switch with the connections that are required for its use and maintenance.
Figure 2 Connections and Networks Required for a Lucent 5ESS Telephone Switch
The connections can be divided into the following categories:
•
•
•
•
Figure 2 shows multiple networks and the legacy transport methods that are used to connect multiple OSSs to the Lucent 5ESS telephone switch. This multiplicity of networks is not an uncommon occurrence in a large PTT or ILEC. Separate networks were built by the various operations organizations using a particular OSS. The billing organization, for example, would often build a separate network for just collecting CDR.
The long-term goal is to consolidate these various networks into an IP backbone. To this end, Cisco Systems offers several solutions that address the varying needs of service providers that have selected OSSs from various vendors with different features. The solutions you choose to migrate an application in your DCN to an IP-based network will depend on the OSS vendor. Today, Cisco can offer the following solutions:
•
•
•
The short-term goal is to migrate all of the various OSSs to a TCP/IP stack utilizing the Cisco X.25 RBP solution, so that the DCN for a telco service provider will look like Figure 3.
Figure 3 A Telco DCN Fully Migrated to TCP/IP
In Figure 3, the call detail record (CDR) collection host still has a BX.25 stack and a serial interface. XOT is used to transport the BX.25 data. The monitoring portion of the OSS has redundant serial BX.25 gateways defined and, in this configuration, the Cisco STUN feature is the best solution. The provisioning and the traffic engineering hosts have both implemented a TCP/IP stack and the Cisco X.25 RBP solution.
The following sections describe migration solutions for each of the connection categories:
•
•
•
•
The solutions are presented with procedures and examples that have been tested with vendor-specific OSSs that transport the BX.25 data across the DCN when Cisco routers have been introduced into the network for the purpose of migrating the network to TCP/IP.
CDR Bill Collection Networks: Cisco XOT and RBP Solutions
This section describes Cisco telco solutions for CDR billing collection networks like the one highlighted in Figure 4.
Figure 4 Legacy CDR Bill Collection Network
CDR billing collection information was originally collected on magnetic tapes and transported on trucks, then dialup connections were used for transferring this data electronically in early network implementations. As the amount of billing data grew, data collection migrated to X.25 networks.
The next generation of networks will transport the CDR data over a high-speed IP backbone. A first step toward this next-generation DCN is to use XOT or RBP to transport the CDR data. This section provides configuration tasks and examples for transporting CDR billing collection information over a router-based network using XOT and RBP. The tasks and examples in this section include a network with a Sterling 5000 Collector and a Kansys, Inc. Mercury Mediation device. The RBP solution was tested on Intec Telecom Systems and implemented RBP on its Inter-mediatE application.
This section contains the following information and tasks:
•
•
•
•
•
•
•
•
•
Cisco XOT Features for Transporting CDR Data
XOT was specified in RFC 1613 by engineers at Cisco Systems to allow for the transport of X.25 packets over a TCP/IP network; that is, XOT tunnels X.25 traffic through an IP cloud. XOT allows X.25 (and BX.25) packets to be sent over a TCP/IP network instead of a Link Access Procedure, Balanced (LAPB) link. The packets can originate from an X.25 DTE device or can be packet assembler/disassembler (PAD)-originated traffic. XOT allows the router to transport X.25 virtual connections (VCs) transparently over a TCP connection on a one-to-one basis; one VC creates one TCP connection. XOT preserves the legacy transport connection on the telephone switch in a DCN while allowing at least partial migration of the network to TCP/IP.
Configurations for the Sterling 5000 Collector map a permanent virtual circuit (PVC) from the Sterling 5000 Collector across an IP backbone to the telephone switch. XOT encapsulates the BX.25 packets in TCP/IP and transports the packets across the core of the network. The BX.25 packets are removed from TCP/IP and forwarded out the serial interface.
Kansys, Inc. has implemented the switched virtual circuit (SVC) portion of XOT in its Mercury Mediation device, which allows the OSS support of XOT directly on the host. In addition to these devices, Cisco has implemented and tested other CDR applications such as Lucent Billdats.
The BX.25 Security I-Frame
In early telco DCNs, BX.25 was implemented in a dialup environment that was used by bill collection applications such as the Lucent Billdats or the 4Tel Sterling 5000 Collector applications. Billing data represents a large part of the service provider revenue. The BX.25 implementation added an Information Frame (I-Frame) for security in the dialup network environment. The I-Frame passed a plain text password from the OSS to the telephone switch, a practice that was intended to prevent service providers from exposing their billing hosts and switches to public networks.
Note
Before migrating to a Cisco TCP/IP network and using XOT to transport the billing data, you must turn off the BX.25 I-Frame.
The parameters for setting the I-Frame in the Lucent 5ESS telephone switch are contained in a switch configuration form named cpblx3. Figure 5 shows field 19, the security field, and the options for setting the I-Frame. To turn off security and the I-Frame, set this field to N. (See the "Lucent cpblx Form Parameter Descriptions" section for more information about filling in the cpblx3 form.)
Figure 5 Security Field from Lucent 5ESS cpblx3 Form
Once this task is performed, you will need to configure X.25 and LAPB parameters for XOT. The following "X.25 and LAPB Parameters" section summarizes the more important X.25 and LAPB parameters and their Cisco default settings. Additional X.25 configuration and troubleshooting information can be found in the "Cisco IOS X.25 Toolkit."
X.25 and LAPB Parameters
X.25 is an International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) protocol standard capable of providing connectivity across public data networks (PDNs). The X.25 network layer protocol is called the Packet Level Protocol (PLP), and it manages packet exchanges between data terminal equipment (DTE) devices across virtual circuits. The PLP operates in five distinct modes: call setup, data transfer, idle, call clearing, and restarting.
LAPB operates at the data link layer of the OSI reference model. LAPB specifies methods for exchanging data (in units called frames), detecting out-of-sequence or missing frames, retransmitting frames, and acknowledging frames. Several protocol parameters can be modified to change LAPB protocol performance on a particular link. Because X.25 operates PLP on top of LAPB, setting the X.25 and LAPB parameters is essential for correct X.25 behavior. It is important that the X.25 and LAPB parameters match on the OSS host, the telephone switch, and the routers performing X.25 over TCP (XOT) encapsulation.
The Cisco X.25 and LAPB parameters and their Cisco defaults are listed in Table 1, Table 2, and Table 3. Sections following the table describe how to set these parameters for specific Cisco solutions.
Configuring XOT on the Billing Collector Side of the Network
Figure 4 shows a basic CDR network with a bill collector application that polls a Lucent 5ESS telephone switch for billing information over a BX.25 network.
Figure 6 shows what the CDR collection connection in Figure 4 would look like when Cisco routers replace the X.25 PAD and use TCP/IP via XOT to transport the billing information. The Cisco 3631 and Cisco 3662 edge routers encapsulate the BX.25 packets.
Figure 6 Sterling 5000 Collector Polling a Telephone Switch Across a Cisco Network
To configure XOT on a Cisco 3631 edge router connected to a Sterling 5000 Collector, see Figure 6 and perform the following steps. See the "Sterling 5000 Collector Configuration: Examples" section for configuration examples.
Step 1
Router-3631# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 2
Router-3631(config)# interface serial 3/0Step 3
Router-3631(config-if)# shutdownStep 4
Router-3631(config-if)# description AMA Billing FE56Step 5
Router-3631(config-if)# encapsulation x25 dceStep 6
Router-3631(config-if)# x25 ltc 5Step 7
Router-3631(config-if)# x25 win 7Step 8
Router-3631(config-if)# x25 wout 7Step 9
Router-3631(config-if)# x25 ips 512Step 10
Router-3631(config-if)# x25 ops 512Step 11
Router-3631(config-if)# no x25 linkrestartStep 12
Router-3631(config-if)# x25 pvc 1 tunnel 172.30.109.48 interface serial 1/0 pvc 1 windowsize 3 3Step 13
Router-3631(config-if)# clockrate 56000Step 14
Router-3631(config-if)# no shutdownStep 15
Router-3631(config-if)# endRouter-3631(config)# endStep 16
Router-3631# copy run startDestination filename [startup-config]?Building configuration...[OK]
Configuring XOT on the Telephone Switch Side of the Network
To configure XOT on a Cisco 3662 edge router connected to a telephone switch, see Figure 6 and perform the following steps. See the "Sterling 5000 Collector Configuration: Examples" section for configuration examples.
Step 1
Router-3662# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 2
Router-3662(config)# interface serial 1/0Step 3
Router-3662(config-if)# shutdownStep 4
Router-3662(config-if)# description AMA Billing 5ESS LucentStep 5
Router-3662(config-if)# encapsulation x25 dceStep 6
Router-3662(config-if)# x25 ltc 5Step 7
Router-3662(config-if)# x25 win 7Step 8
Router-3662(config-if)# x25 wout 7Step 9
Router-3662(config-if)# x25 ips 512Step 10
Router-3662(config-if)# x25 ops 512Step 11
Router-3662(config-if)# no x25 linkrestartStep 12
Router-3662(config-if)# x25 pvc 1 xot 172.31.229.247 interface serial 3/0 pvc 1 xot-promiscuous window size 3 3Step 13
Router-3662(config-if)# clockrate 56000Step 14
Router-3662(config-if)# no shutdownStep 15
Router-3662(config-if)# endRouter-3662(config)# endStep 16
Router-3662# copy run startDestination filename [startup-config]?Building configuration...[OK]
Sterling 5000 Collector Configuration: Examples
This section provides examples of the following Sterling 5000 Collector configurations:
•
•
•
•
•
•
The Sterling 5000 Collector configuration examples are similar and show how to configure XOT in a DCN that uses a Sterling 5000 Collector to poll a Class 5 telephone switch. Each configuration maps a PVC from the Sterling 5000 Collector across an IP backbone to the telephone switch. XOT encapsulates the BX.25 packets in TCP/IP and transports the packets across the core of the network. The BX.25 packets are removed from TCP/IP and forwarded out the serial interface. The main differences in the configuration examples provided in this section are the switch types; however, in your DCN there could also be variations with how X.25 or the Layer 3 parameters are configured.
Sterling 5000 Collector Polling a Lucent 5ESS Telephone Switch: Example
The following example shows how to configure XOT in a DCN that uses a Sterling 5000 Collector to poll a Lucent 5ESS telephone switch. The edge routers (the Cisco 3631 and Cisco 3662 routers in Figure 7) encapsulate the BX.25 packets.
Figure 7 Sterling 5000 Collector Polling a Lucent 5ESS Telephone Switch
Cisco 3631 Edge Router Connected to the Sterling 5000 Collector (Polling Lucent 5ESS Switch): Example
The following partial example shows the configuration for a Cisco 3631 edge router connected to a Sterling 5000 Collector that polls a Lucent 5ESS telephone switch for billing data. In this example the PVCs are mapped to a far-end router. The PVC connections are always established, and the destination is predetermined and is the X.25 equivalent of a leased line.
x25 routing!interface Ethernet2/1descriptionip address 172.31.229.247 255.255.255.0! Serial 3/0 specifies network module 3 and port 0.interface Serial3/0! Serial interface description.description AMA Billing FE56no ip address! X.25 DCE encapsulation.encapsulation x25 dceno ip mroute-cacheno logging event subif-link-status! The low two-way channel VC number is 5, making the PVC range 1 through 4.x25 ltc 5! The input and output window size is changed from the default of 2 to 7.x25 win 7x25 wout 7! The maximum input and output packet size is changed from the default of 128 to 512.x25 ips 512x25 ops 512! The system default is to force X.25 packet-level restarts when the link level resets.! The no x25 linkrestart command disables this function.no x25 linkrestart! The x25 pvc commands configure different PVC LCNs on the host side that are each! mapped to a different Class 5 telephone switch. The PVC LCN on the host side is always! mapped to the PVC with LCN 1 on the Lucent 5ESS telephone switches.! X.25 input and output window sizes of 3 were specified for this interface.x25 pvc 1 tunnel 172.30.109.48 interface Serial 1/0 pvc 1 windowsize 3 3x25 pvc 2 tunnel 172.30.115.120 interface Serial 1/0 pvc 1 windowsize 3 3x25 pvc 3 tunnel 172.30.128.248 interface Serial 1/0 pvc 1 windowsize 3 3x25 pvc 4 tunnel 172.30.136.248 interface Serial 1/0 pvc 1 windowsize 3 3! The clock rate is set to 56000 baud, to supply clock signaling to the DTE device.clockrate 56000Cisco 3662 Edge Router Connected to the Lucent 5ESS Telephone Switch: Example
The following partial example shows the configuration for a Cisco 3662 edge router located in the central office. The router connects to the Lucent 5ESS telephone switch using BX.25.
x25 routing!interface Ethernet0/0description AMA Billingip address 172.30.109.48 255.255.255.192no ip directed-broadcast!interface Serial1/0description AMA Billing 5ESS Lucentno ip addressno ip directed-broadcast! X.25 DTE encapsulation.encapsulation x25no ip mroute-cache! The low two-way channel VC number is 5, making the PVC range 1 through 4.x25 ltc 5! The input and output window size is changed from the default of 2 to 7.x25 win 7x25 wout 7! The maximum input and output packet size is changed from the default of 128 to 512.x25 ips 512x25 ops 512! The system default is to force X.25 packet-level restarts when the link level resets.! The no x25 linkrestart command disables this function.no x25 linkrestart! PVC 1 from the Lucent 5ESS telephone switch is mapped to PVC 1 at serial interface 3/0.! X.25 input and output window sizes of 3 were specified for this interface.x25 pvc 1 xot 172.31.229.247 interface Serial 3/0 pvc 1 xot-promiscuous window size 3 3! The clock rate is set to 19200 baud, to supply clock signaling to the DTE device.clockrate 56000Sterling 5000 Collector Polling a Siemens EWSD Telephone Switch: Example
The following example shows how to configure XOT in a DCN that uses a Sterling 5000 Collector to poll a Siemens EWSD telephone switch, as shown in Figure 8.
Figure 8 Sterling 5000 Collector Polling a Siemens EWDS Telephone Switch
Cisco 3631 Edge Router Connected to the Sterling 5000 Collector (Polling Siemens EWSD Switch): Example
The following partial example shows the configuration for a Cisco 3631 edge router connected to a Sterling 5000 Collector that polls a Siemens EWSD telephone switch for billing data. See the examples for the Lucent 5ESS switch for configuration notes.
x25 routing!interface Ethernet0/1descriptionip address 172.31.229.248 255.255.255.0no logging event subif-link-status!interface Ethernet0/2no ip addressno logging event subif-link-statusshutdown!interface Ethernet0/3no ip addressno logging event subif-link-statusshutdown!interface Serial1/0description AMA Billing FE56no ip addressencapsulation x25 dceno ip mroute-cacheno logging event subif-link-statusx25 ltc 5x25 win 7x25 wout 7x25 ips 512x25 ops 512x25 pvc 1 tunnel 172.30.108.48 interface Serial 0 pvc 1 windowsize 3 3x25 pvc 2 tunnel 172.30.113.184 interface Serial 0 pvc 1 windowsize 3 3x25 pvc 3 tunnel 172.30.130.248 interface Serial 1/0 pvc 1 windowsize 3 3x25 pvc 4 tunnel 172.30.114.248 interface Serial 0 pvc 1 windowsize 3 3clockrate 56000Cisco 3662 Edge Router Connected to the Siemens EWSD Telephone Switch: Example
The following partial example shows the configuration for a Cisco 3662 edge router located in the central office (also referred to as the CO). The router connects to the Siemens EWSD telephone switch using BX.25. See the examples for the Lucent 5ESS switch for configuration notes.
x25 routing!interface Ethernet0descriptionip address 172.30.113.184 255.255.255.192no mop enabled!interface Serial0description AMA Billing Siemens EWSDno ip addressencapsulation x25no ip mroute-cachex25 ltc 5x25 win 7x25 wout 7x25 ips 512x25 ops 512no x25 linkrestartx25 pvc 1 tunnel 172.31.229.248 interface Serial 1/0 pvc 2 windowsize 3 3clockrate 19200!Sterling 5000 Collector Polling a Nortel DMS/DPP Telephone Switch: Example
This example shows how to configure XOT in a DCN that uses a Sterling 5000 Collector to poll a Nortel DMS/DPP telephone switch. The edge routers (the Cisco 3631 and Cisco 3662 routers in Figure 9) encapsulate the BX.25 packets.
Figure 9 Sterling 5000 Collector Polling a Nortel DMS/DPP Telephone Switch
Cisco 3631 Edge Router Connected to the Sterling 5000 Collector (Polling Nortel DMS/DPP Switch)
The following partial example shows the configuration for a Cisco 3631 edge router connected to a Sterling 5000 Collector that polls a Nortel DMS/DPP telephone switch for billing data. See the examples for the Lucent 5ESS switch for configuration notes.
x25 routing!interface Ethernet0/0description to Nortel DMS/DPP Portip address 172.31.228.248 255.255.255.0no logging event subif-link-status!interface Serial1/0description AMA Billing FE56no ip addressencapsulation x25 dceno ip mroute-cacheno logging event subif-link-statusx25 ltc 5x25 win 7x25 wout 7x25 ips 512x25 ops 512x25 pvc 1 tunnel 172.30.108.48 interface Serial 0 pvc 1 windowsize 3 3x25 pvc 3 tunnel 172.30.130.248 interface Serial 1/0 pvc 1 windowsize 3 3x25 pvc 4 tunnel 172.30.114.248 interface Serial 0 pvc 1 windowsize 3 3clockrate 56000!Cisco 3662 Edge Router Connected to the Nortel DMS/DPP Telephone Switch: Example
The following partial example shows the configuration for a Cisco 3662 edge router located in the central office. The router connects to the Nortel DMS/DPP telephone switch using BX.25. See the examples for the Lucent 5ESS switch for configuration notes.
x25 routing!interface Ethernet0description - to DCN Bay RR 261.6 Hubip address 172.30.108.48 255.255.255.192no ip redirectsno mop enabled!interface Serial0description AMA Billing DPP Nortelno ip addressencapsulation x25no ip mroute-cachex25 ltc 2x25 win 7x25 wout 7x25 ips 512x25 ops 512x25 pvc 1 tunnel 172.31.228.248 interface Serial 1/0 pvc 1 windowsize 3 3clockrate 56000Configuring a Cisco Router for a Host That Supports XOT
Examples in earlier sections about the Sterling 5000 Collector described methods to create Cisco XOT tunnels with routers at both ends of the network. Another method is to have the OSS support XOT directly on the host. Kansys, Inc. has implemented the SVC portion of XOT in its Mercury Mediation device (see Figure 10).
Figure 10 Kansys CDR Bill Collection Application with XOT on the Host
The host makes an X.25 SVC call to the router connected to the Lucent 5ESS telephone switch. The X.25 call is encapsulated in an XOT packet. The TCP/IP session is terminated on the router and the X.25 packet is removed. The X.25 SVC is terminated by the router and converted to a PVC.
To configure a Cisco router to support a bill collector host that supports XOT, see Figure 10 and perform the following steps. See the "Mercury Mediation Bill Collector That Supports XOT: Example" section for a configuration example. See the "Verifying the SVC Connection on the Mercury Mediation Device" section for a verification example.
Step 1
Router-B# show versionStep 2
Router-B# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 3
Router-B(config)# x25 routingStep 4
Router-B(config)# interface serial 1/2Step 5
Router-B(config-if)# shutdownStep 6
Router-B(config-if)# description AMA connection to Lucent 5ESS switchStep 7
Router-B(config-if)# x25 address 5555550137Step 8
Router-B(config-if)# encapsulation x25 dceStep 9
Router-B(config-if)# x25 win 3Step 10
Router-B(config-if)# x25 wout 3Step 11
Router-B(config-if)# x25 ips 512Step 12
Router-B(config-if)# x25 ops 512Step 13
Router-B(config-if)# clockrate 56000Step 14
Router-B(config-if)# lapb N1 4152Step 15
Router-B(config-if)# x25 pvc 1 svc 5555550140 packetsize 512 512 windowsize 3 3Step 16
Router-B(config-if)# no ignore-hw local-loopbackStep 17
Router-B(config-if)# no ip mroute-cacheStep 18
Router-B(config-if)# no ip addressStep 19
Router-B(config-if)# no shutdownStep 20
Router-B(config-if)# endStep 21
Router-B(config)# x25 route 5555550137 interface serial 1/2Step 22
Router-B(config)# x25 route 5555550140 xot 192.168.3.20Step 23
Router-B(config)# endStep 24
Router-B# copy run startDestination filename [startup-config]?Building configuration...[OK]
Mercury Mediation Bill Collector That Supports XOT: Example
The following example shows how to configure a network with a Mercury Mediation bill collector that supports XOT. The Mercury Mediation device is polling a Lucent 5ESS telephone switch. The example configures the router connected to the Lucent 5ESS, which is identified as Router B in Figure 10.
interface Serial1/2description AMA connection to Lucent 5ESS switchno ip addressencapsulation x25 dceno ip mroute-cachex25 address 5555550137x25 win 3x25 wout 3x25 ips 512x25 ops 512x25 pvc 1 svc 5555550140 packetsize 512 512 windowsize 3 3no ignore-hw local-loopbackclockrate 56000lapb N1 4152!x25 route 5555550137 interface Serial1/2x25 route 5555550140 xot 192.168.3.20Verifying the SVC Connection on the Mercury Mediation Device
It is important that it be the Mercury Mediation device that places the X.25 SVC call to the router interface. The router terminates the SVC call and converts the SVC to a PVC. The X.25 address assigned to serial interface 1/2 (5555550137) must match the destination address of the X.25 call placed by the Mercury Mediation device. The source address of the call (5555550140) must match the X.121 address assigned to the command, to convert between PVC and SVC. Use the show x25 vc EXEC command to verify the correct configuration.
The following example output shows that the application with X.121 address 5555550140 is connected to router serial interface 1/2 with X.121 address 5555550137:
Router-B # show x25 vcPVC 1, State: D1, Interface: Serial1/2Started 01:13:53, last input 00:00:06, output 00:00:06Connects 5555550140 <--> 5555550137 fromXOT between 10.129.48.4, 1998 and 192.168.3.20, 1833Window size input: 3, output: 3Packet size input: 512, output: 512PS: 0 PR: 1 ACK: 1 Remote PR: 0 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 293/153757 packets 32/313 Resets 4/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [192.168.3.20,1833/10.129.48.4,1998]Started 00:00:44, last input 00:00:06, output 00:00:06Connects 5555550140 <--> 5555550137 from Serial1/2 PVC 1Window size input: 3, output: 3Packet size input: 512, output: 512PS: 1 PR: 0 ACK: 0 Remote PR: 1 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 153651/179 packets 305/24 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0Cisco RBP and RBP Q-Bit Features for Transporting CDR Data
The previous sections described how to collect CDRs using XOT. This section describes how to configure a Cisco router for a CDR host that supports RBP and RBP Q-bit.
The Cisco RBP Feature
Cisco implemented the RBP feature to help the migration of the OSSs to TCP/IP. The RBP feature is a six-byte header inserted at the beginning of the TCP data field that allows the router to pass the end-of-record information between BX.25 and TCP sessions. More information on RBP can be found in the "Adding Cisco X.25 RBP to the Telco DCN Provisioning Connection" section and in the X.25 Record Boundary Preservation for Data Communications Networks feature module located at this URL: http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a008045552b.html
The Cisco RBP feature marks the end of record in a TCP session. In the ITU-T Recommendation X.25 standards, the end of record is marked with a more data bit (M-bit). The RBP solution is a six-byte header inserted at the front of the TCP data field that allows the router to pass the end of record information between the BX.25 and the TCP sessions. More information on RBP can be found in the "Adding Cisco X.25 RBP to the Telco DCN Provisioning Connection" section and in the X.25 Record Boundary Preservation for Data Communications Networks feature module.
The Cisco RBP Q-Bit Feature
The RBP Q-Bit feature offered in Cisco IOS Release 12.4(15)T and later releases downloads Call Detail Records (CDRs) from Class 5 switches. In releases prior to Cisco IOS Release 12.4(15)T, the end of record was lost when mediating between an X.25 transport and a TCP/IP transport. In the ITU-T Recommendation X.25 standards, the end of record is marked with a more data bit (M-bit). RBP was developed to maintain the end of record in a TCP connection for migrating traditional applications connecting to a Class 5 telephone switch from an X.25 transport to a TCP/IP transport. RBP enables hosts using TCP/IP-based protocols to exchange data with devices that use the X.25 protocol, retaining the logical record boundaries indicated by use of the X.25 M-bit.
RBP and RBP Q-Bit File Type Compatibility
The original RBP feature works with the file types of XFER, Bellcore 385 (BC385) and GEC-Plessey Telecommunications (GPT); however, the file types MNP and MTP are not supported because these protocols require the X.25 M-bit and Q-bit. The Q-bit in an X.25 frame differentiates control frames from data frames. MNP and MTP use control frames in the Call Detail Record transfer. The enhanced RBP Q-bit solution identifies control frames and data frames in the RBP six-byte header.
Cisco has worked with Intec Telecom Systems to implement the RBP Q-bit solution on their Inter-mediatE application. The Inter-mediatE application supports the collections of CDRs using the following file types:
•
•
•
•
A key point is that the Bellcore 385 AMATPS file type and the Nortel XFER file type require only end of record or M-bit support. See the "Configuring an Intec Telecom Systems Inter-mediatE System" section for more information about configuring the Inter-mediatE application.
Configuring a Cisco Router for a CDR Host That Supports the RBP Feature
The RBP solution implements TCP/IP from the Inter-mediatE host to an access router in the central office. Figure 11 shows a network with RBP configured on a Lucent 5ESS. RBP is transporting Bellcore 385 AMATPS-formatted data.
Figure 11 Call Detail Record Collection Using RBP Session over TCP/IP
A serial connection from the access router to the Lucent 5ESS switch must be configured for LAPB at Layer 2 and BX.25 at Layer 3. The BX.25 standard specifies an additional I-Frame at the LAPB layer. The additional I-Frame supports a clear text password, which must be turned off. The I-Frame is described in the "The BX.25 Security I-Frame" section."
To configure the serial ports on the Cisco router to make the connections between the access router and the Lucent 5ESS switch, refer to Figure 11 and perform the following steps. See the "Cisco X.25 RBP with the Inter-mediatE to a Lucent 5ESS Switch: Example" section and "Cisco X.25 RBP with the Inter-mediatE to a Nortel DMS 100 Switch: Example" section for configuration examples.
Step 1
Router-A# show versionStep 2
Router-A# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 3
Router-A(config)# interface Loopback0Router-A(config-if)# ip address 10.60.128.8 255.255.255.255Router-A(config-if)# endStep 4
Router-A(config)# x25 routingStep 5
Router-A(config)# interface serial 1/0Step 6
Router-A(config-if)# shutdownStep 7
Router-A(config-if)# description Collection of Call Detail Records portStep 8
Router-A(config-if)# encapsulation x25 dceStep 9
Router-A(config-if)# x25 loc 4Step 10
Router-A(config-if)# x25 threshold 1Step 11
Router-A(config-if)# x25 ips 512Step 12
Router-A(config-if)# x25 ops 512Step 13
Router-A(config-if)# x25 pvc 1 rbp local port 10000Step 14
Router-A(config-if)# clockrate 56000Step 15
Router-A(config-if)# no shutdownStep 16
Router-A(config-if)# endRouter-A(config)# endStep 17
Router-A# copy running-config startup-configDestination filename [startup-config]?Building configuration...[OK]
Cisco X.25 RBP with the Inter-mediatE to a Lucent 5ESS Switch: Example
The following example shows how to configure RBP on the serial interface that will connect to the Lucent 5ESS switch:
interface Serial1/0no ip addressencapsulation x25 dceno ip mroute-cachex25 ltc 4x25 ips 512x25 ops 512x25 pvc 1 rbp local port 10000clockrate 56000Cisco X.25 RBP with the Inter-mediatE to a Nortel DMS 100 Switch: Example
The Inter-mediatE host can be configured to use Nortel's XFER protocol for collecting the call detail records from a DMS 100 switch. You can also use RBP with the XFER protocol. The following example shows how to configure RBP on the serial interface that will connect to the Nortel DMS 100 switch:
interface Serial1/0no ip addressencapsulation x25 dceno ip mroute-cachex25 ltc 4x25 ips 512x25 ops 512x25 pvc 1 rbp local port 10000x25 map rbp 00006300 cud 0xB0 local port 20000clockrate 56000Configuring the Cisco X.25 RBP Q-Bit Feature for the MTP File Type
The Inter-mediatE host can be configured to use MTP file types for collecting the call detail records from a Class 5 switch. MTP is typically used with the collection of call records from the following switch types:
•
•
•
The configuration shown in Figure 12 is a test setup for MTP file type retrieval. The Cisco 2651XMBR5 router is connected to the network with the Fast Ethernet interface 0/0. The Inter-mediatE application is connected to the network with a TCP/IP connection over Ethernet. The Inter-mediatE application will connect via a TCP/IP session to the Cisco 2651XMB router.
Figure 12 TCP/IP-to-X.25 Mediation: MTP File Type Retrieval
To configure the serial ports on the Cisco router to make the connections between the access router and the Class 5 switch, refer to Figure 12 and perform the following steps. See the "Cisco X.25 RBP Q-Bit Feature with the Inter-mediatE to a Class 5 Switch with MTP File Type: Example" section for a configuration example. See the "Debugging Cisco X.25 RBP" section for debugging examples.
Step 1
Router-A# show versionStep 2
Router-A# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 3
Router-A(config)# interface Loopback0Router-A(config-if)# ip address 10.60.128.8 255.255.255.255Router-A(config-if)# endStep 4
Router-A(config)# x25 routingStep 5
Router-A(config)# interface serial 1/0Step 6
Router-A(config-if)# shutdownStep 7
Router-A(config-if)# description Collection of Call Detail Records portStep 8
Router-A(config-if)# encapsulation x25 dceStep 9
Router-A(config-if)# x25 loc 4Step 10
Router-A(config-if)# x25 map rbp 3178650503 local port 30010 q-bitStep 11
Router-A(config-if)# clockrate 56000Step 12
Router-A(config-if)# no shutdownStep 13
Router-A(config-if)# endRouter-A(config)# endStep 14
Router-A# copy running-config startup-configDestination filename [startup-config]?Building configuration...[OK]
Cisco X.25 RBP Q-Bit Feature with the Inter-mediatE to a Class 5 Switch with MTP File Type: Example
The following example shows how to configure RBP and the new Q-bit keyword on the serial interface that will connect to the Class 5 switch. Figure 12 shows the physical configuration.
interface Serial0/1description X.25 RBP+Q Inter-mediatEno ip addressencapsulation x25 dcex25 ltc 4x25 map rbp 3178650503 local port 30010 q-bitclock rate 56000Configuring the Cisco X.25 RBP Q-Bit Feature for the MNP File Type
The Inter-mediatE host can be configured to use the MNP file for collecting the call detail records from a Class 5 switch. MNP is typically used with the collection of call records from the Nortel MTX, Nortel DMS300, and Nortel DMS 500 switch types. The configuration shown in Figure 13 is a test setup for MNP file type retrieval.
Figure 13 TCP/IP-to-X.25 Mediation: MNP File Type Retrieval
To configure the serial ports on the Cisco router to make the connections between the access router and the Class 5 switch, refer to Figure 13 and perform the following steps. See the "Cisco X.25 RBP Q-Bit Feature with the Inter-mediatE to a Class 5 Switch with MNP File Type: Example" section for a configuration example. See the "Debugging Cisco X.25 RBP" section for debugging examples.
Step 1
Router-A# show versionStep 2
Router-A# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 3
Router-A(config)# interface Loopback0Router-A(config-if)# ip address 10.60.128.8 255.255.255.255Router-A(config-if)# endStep 4
Router-A(config)# x25 routingStep 5
Router-A(config)# interface serial 1/0Step 6
Router-A(config-if)# shutdownStep 7
Router-A(config-if)# description Collection of Call Detail Records portStep 8
Router-A(config-if)# encapsulation x25 dceStep 9
Router-A(config-if)# x25 loc 4Step 10
Router-A(config-if)# x25 map rbp 3178650503 local port 30010 q-bitStep 11
Router-A(config-if)# clockrate 56000Step 12
Router-A(config-if)# no shutdownStep 13
Router-A(config-if)# endRouter-A(config)# endStep 14
Router-A# copy running-config startup-configDestination filename [startup-config]?Building configuration...[OK]
Cisco X.25 RBP Q-Bit Feature with the Inter-mediatE to a Class 5 Switch with MNP File Type: Example
The following example shows a router configuration for RBP with the new Q-bit option on the serial interface that will connect to the Class 5 switch. Figure 13 shows the physical configuration.
interface Serial0/1description X.25 RBP+Q Inter-mediatEno ip addressencapsulation x25 dcex25 ltc 4x25 map rbp 3178650503 local port 30010 q-bitclock rate 56000!Debugging Cisco X.25 RBP
This section contains the following procedures that are useful for debugging RBP:
•
•
•
The debugging examples in this section are based on the previous configuration example. The test network is shown in Figure 13.
Caution
Debugging a TCP/IP Connection
As shown in the "Cisco X.25 RBP Q-Bit Feature with the Inter-mediatE to a Class 5 Switch with MNP File Type: Example" section and Figure 13, the Inter-mediatE host is configured to use the MTP file format for collecting the call detail records from a Class 5 switch. The Cisco 2651XMB router is configured with RBP and with the new Q-bit option on the serial interface that will connect to the Class 5 switch.
The following steps were performed in a lab environment and show different portions of the startup and teardown of a data transfer of the MTP file type between the Inter-mediatE application and the Class 5 switch. Not all of the data transfer output is shown, and the debugging output is pulled from various tests.
Step 1
2651XMB# terminal monitorStep 2
2651XMB# debug x25 allX.25 packet debugging is onStep 3
2651XMB# debug x25 dumpX.25 packet debugging is onX.25 packet dump debugging is onStep 4
2651XMB# debug ip packetIP packet debugging is on
Tip
2651XMB# debug ip packet dump detailIP packet debugging is on (detailed) (dump)The following examples show a series of debug outputs.
Output 1: The following example lists the TCP connection to port 30010 from IP address 172.16.4.59 and port 51608.
Feb 7 07:27:07.628: X25 RBP: Incoming connection for port 30010 from 172.16.4.59 port 51608Output 2: Example Output 1 showed the Inter-mediatE application making a TCP/IP connection to the Cisco 2651XMB router, which is mediated to X.25. In the following example, the Cisco 2651XMB router is making an outbound X.25 call on serial interface 1/0 LCI 4 to destination X.121 address 317650503 from source X.121 address 0. The source address is 0 because no X.121 address was assigned to serial interface 0/1. You can verify that this was outbound data by the "X.25 O" string in the debug; the bold O indicates outbound.
Feb 7 07:27:07.628: X25 RBP: Incoming connection for port 30010 from 158.155.4.59 port 51608Feb 7 07:27:07.632: Serial0/1: X.25 O R1 Call (11) 8 lci 4Feb 7 07:27:07.632: From (0): To (10): 3178650503Feb 7 07:27:07.632: Facilities: (0)Feb 7 07:27:07.632: Call User Data (1): 0xC0 (unknown)0: 10040B0A 31786505 ....1xe.8: 0300C0 ..@Output 3: The router is receiving an inbound X.25 call confirm on serial interface 1/0 LCI 4. You can verify that this is inbound data by the "X.25 I" string in the debug; the bold I indicates inbound.
Feb 7 07:27:07.640: Serial0/1: X.25 I R1 Call Confirm (3) 8 lci 40: 10040F ...Step 5
Debugging an X.25 Serial Connection
Cisco IOS offers the debug x25 command with various options. Typically, you enable all the options, with the exception of data display, to debug an X.25 application.
Step 1
2651XMB# terminal monitorStep 2
2651XMB# debug x25 allX.25 packet debugging is onStep 3
2651XMB# debug x25 dumpX.25 packet debugging is onX.25 packet dump debugging is onThe following examples show a series of debug output with only X.25 debugging enabled on serial interface 0/1 on the Cisco 2651XMB router.
Output 1: The report shows an inbound call (I, highlighted in bold text) from the Class 5 switch to the router on LCI 11.
*May 24 05:16:06.884: Serial0/1: X.25 I R1 Call (14) 8 lci 11*May 24 05:16:06.884: From (10): 3178650503 To (0):*May 24 05:16:06.884: Facilities: (0)*May 24 05:16:06.884: Call User Data (4): 0xC0000000 (unknown)0: 100B0B A0317865 050300C0 ... 1xe...@11: 000000 ...Output 2: The router sends a call confirm outbound (O, highlighted in bold text) on LCI 11.
*May 24 05:16:06.888: Serial0/1: X.25 O R1 Call Confirm (5) 8 lci 11*May 24 05:16:06.888: From (0): To (0):*May 24 05:16:06.888: Facilities: (0)0: 100B0F00 00 .....Output 3: The Class 5 switch is sending a packet inbound with the Q-bit set.
*May 24 05:16:07.658: Serial0/1: X.25 I D1 Data (38) Q 8 lci 11 PS 0 PR 00: 900B00 03650054 5446494C ....e.TTFIL11: 452D3030 30310000 00000000 00000000 E-0001..........27: 00000000 00000000 000000 ...........*May 24 05:16:07.658: X25 RBP: Q-bit received in X25 data packetOutput 4: The Inter-mediatE application has sent a TCP/IP packet to the router. TCP/IP debugging is disabled, so you do not see the packet.
*May 24 05:16:11.079: X25 RBP: Q-bit received in RBP recordOutput 5: The router mediated the TCP/IP packet to X.25 and sent it to the Class 5 switch.
*May 24 05:16:11.079: Serial0/1: X.25 O D1 Data (5) Q 8 lci 11 PS 0 PR 10: 900B20 0081 .. ..Out put 6: A data packet is received from the class 5 switch.
*May 24 05:16:11.600: Serial0/1: X.25 I D1 RR (3) 8 lci 11 PR 10: 100B21 ..!Output 7: An X.25 packet is received from the Class 5 switch with the Q-bit set.
*May 24 05:16:12.109: Serial0/1: X.25 I D1 Data (5) Q 8 lci 11 PS 1 PR 10: 900B22 00A2 .."."*May 24 05:16:12.109: X25 RBP: Q-bit received in X25 data packetOutput 8: The Inter-mediatE application has sent a TCP/IP packet to the router. TCP/IP debugging is disabled, so you do not see the packet.
*May 24 05:16:15.935: X25 RBP: Q-bit received in RBP recordOutput 9: The router mediated the TCP/IP packet to X.25 and sends it out the interface to the Class 5 switch.
*May 24 05:16:15.939: Serial0/1: X.25 O D1 Data (6) Q 8 lci 11 PS 1 PR 20: 900B42 00A306 ..B.#.Output 10: An X.25 packet is sent from the Class 5 switch.
*May 24 05:16:16.740: Serial0/1: X.25 I D1 RR (3) 8 lci 11 PR 20: 100B41 ..AOutput 11: Another X.25 packet is sent from the Class 5 switch.
*May 24 05:16:17.269: Serial0/1: X.25 I D1 Data (131) 8 lci 11 M PS 2 PR 20: 100B54 00000000 00000000 ..T........11: 00000000 00000000 00000000 00000000 ................27: 00000000 00000000 00000000 00000000 ................43: 00000000 00000000 00000000 00000000 ................59: 00000000 00000000 00000000 00000000 ................75: 00000000 00000000 00000000 00000000 ................91: 00000000 00000000 00000000 00000000 ................107: 00000000 00000000 00000000 00000000 ................123: 00000000 00000000 ........Output 12: Another X.25 packet sent from the Class 5 switch.
*May 24 05:16:17.289: Serial0/1: X.25 I D1 Data (131) 8 lci 11 M PS 3 PR 20: 100B56 00000000 00000000 ..V........11: 00000000 00000000 00000000 00000000 ................27: 00000000 00000000 00000000 00000000 ................43: 00000000 00000000 00000000 00000000 ................59: 00000000 00000000 00000000 00000000 ................75: 00000000 00000000 00000000 00000000 ................91: 00000000 00000000 00000000 00000000 ................107: 00000000 00000000 00000000 00000000 ................123: 00000000 00000000 ........Output 13: Another X.25 packet sent to the Class 5 switch.
*May 24 05:16:17.293: Serial0/1: X.25 O D1 RR (3) 8 lci 11 PR 40: 100B81 ...Output 14: Another X.25 packet sent from the Class 5 switch.
*May 24 05:16:17.317: Serial0/1: X.25 I D1 Data (131) 8 lci 11 M PS 4 PR 20: 100B58 00000000 00000000 ..X........11: 00000000 00000000 00000000 00000000 ................27: 00000000 00000000 00000000 00000000 ................43: 00000000 00000000 00000000 00000000 ................59: 00000000 00000000 00000000 00000000 ................75: 00000000 00000000 00000000 00000000 ................91: 00000000 00000000 00000000 00000000 ................107: 00000000 00000000 00000000 00000000 ................123: 00000000 00000000
Note
Output 15: The file transfer is complete and TCP session is terminated.
*May 24 05:16:31.649: [158.155.4.59,12500/158.155.4.100,43760]: TCP receive error, End of data transferOutput 16: The router terminates the RBP session.
*May 24 05:16:31.649: X25 RBP: End of data transfer*May 24 05:16:31.653: Serial0/1: X.25 O R1 Clear (5) 8 lci 11*May 24 05:16:31.653: Cause 9, Diag 122 (Out of order/Maintenance action)0: 100B1309 7A ....zOutput 17: The Class 5 switch confirms the Clear of the SVC.
*May 24 05:16:31.889: Serial0/1: X.25 I P7 RR (3) 8 lci 11 PR 50: 100BA1 ..!*May 24 05:16:31.889: Serial0/1: X.25 I R1 Clear Confirm (3) 8 lci 110: 100B17 ...Step 4
Debugging the RBP Configuration
The following examples show the router configuration followed by the debug x25 all command output.
Router Configuration
interface FastEthernet0/0description SERVIDOR X25ip address 192.168.1.254 255.255.255.0no ip mroute-cacheduplex autospeed auto!!interface Serial0/1/0bandwidth 9no ip addressencapsulation x25no ip mroute-cachex25 address 074610619x25 map rbp 098110661 remote host 192.168.1.100 port 10000no cdp enable!line vty 0 4privilege level 15password ciscono logintransport input telnet sshline vty 5 15privilege level 15login localtransport input telnet ssh!debug x25 all Command
With the debug x25 all command enabled, you see the following reports when the X.25 call comes in:
Output 1: The call comes into the router. The I in the packet debug output identifies the packet is inbound to the router interface. The calling address is 09811066, which is the X.121 address on the Class 5 switch. The address called is 074610619, which is the address assigned to serial interface 0/1/0.
*Oct 2 10:35:32.935: Serial0/1/0: X.25 I R1 Call (18) 8 lci 1*Oct 2 10:35:32.939: From (9): 098110661 To (9): 074610619*Oct 2 10:35:32.939: Facilities: (0)*Oct 2 10:35:32.939: Call User Data (4): 0x01000000 (pad)Output 2: The outgoing packet is identified by the O. The call is cleared by the router because of an invalid destination address. RBP is mediating between TCP/IP and X.25. The x25 map command is used to map an incoming TCP/IP session to X.25. There is not a RBP statement to map an incoming X.25 call to a TCP/IP session, so the router has no place to forward the packet and clears the call.
*Oct 2 10:35:32.939: Serial0/1/0: X.25 O R1 Clear (5) 8 lci 1*Oct 2 10:35:32.939: Cause 0, Diag 67 (DTE originated/Invalid destination address)Output 3: The packet is inbound as identified by the I. The Clear Confirmed packet confirms the call has been cleared.
*Oct 2 10:35:32.975: Serial0/1/0: X.25 I R1 Clear Confirm (3) 8 lci 1Configuring an Intec Telecom Systems Inter-mediatE System
Intec's Data Collection and Mediation Platform is called Inter-mediatE. All data enters the system through input data portals. The Portal Definition window examples in the following procedure are from Inter-mediatE's Customer Equipment Data Portal Definition Interface. In the following steps, you will configure the system that will collect call detail records using a data collection protocol (Bellcore 385 or AMATPS, or Nortel's XFER) built on top of RBP.
Configuration of a portal consists of defining the parameters provided by several tabs on the Portal Definition window.
To supply the values required for the Portal Definition, perform the following steps:
Step 1
In the following example, the System Name is KFSTST and the Portal Name is RBP. The critical fields on this window are Plug-in and Business Logic Name (see Figure 14).
Figure 14 Portal Window
Step 2
Step 3
Step 4
Figure 15 File Naming Window
Choices displayed on the File Naming window depend upon the collection protocol chosen on the Portal window. In Figure 14, Bellcore 385 and RBP were chosen. Because Bellcore 385 supports several different file formats, there are two choices for these formats. If XFER had been chosen in the Portal window, the File Naming window would offer a choice of Nortel dirfile filename formats.
Step 5
Figure 16 Routing Window
Choices displayed on the Routing window depend upon the collection protocol chosen on the Portal window. In Figure 14, Bellcore 385 (AMATPS) and RBP were chosen, so parameters for configuring Bellcore 385 are entered here.
Step 6
Step 7
The name in the Class Name field is only significant in that it must be available on the host. Refer to Inter-mediatE product documentation for more information. Typically, an Inter-mediatE host initiates the call.
Step 8
Figure 17 Protocol Window
Choices displayed on the Protocol window depend upon the collection protocol chosen on the Portal window. In Figure 14, Bellcore 385 (AMATPS) and RBP were chosen, so parameters for configuring Bellcore 385 are entered here.
Note
Tip
Switch Monitoring Networks: Cisco STUN OSS Connectivity Solution
This section describes Cisco telco solutions for legacy telephone switch monitoring networks like the one highlighted in Figure 18.
Figure 18 Legacy Switch Monitoring Connections
The solutions are described in the following sections:
•
•
•
Switch Monitoring Overview
One of the major functions of the DCN is to enable monitoring of the telephone switch. Monitoring of the Class 5 telephone switches was done originally with modems and dual, private line circuits.
The RBOCs built the private networks in the 1980s and 1990s with Lucent Datakit hardware and used the Datakit networks for monitoring their switches. Also, Lucent and Bellcore often used Datakit nodes as the communications front-end platform for an OSS application. In Figure 21, the Lucent Network Fault Management (NFM) application is shown with a Datakit node acting as the communications front end.
The dual connections for monitoring a Lucent 5ESS are designated specialized common carrier 0 (SCC0) and SCC1. There are two circuits as shown in Figure 19 for redundancy. One of the connections is active and the second connection remains in standby mode and functions as backup for the active connection. The original design assumed the two links to look like dedicated circuits to the Lucent 5ESS telephone switch and that design has not changed over the years. The Lucent 5ESS switch expects to see the control leads on the standby connection because this is what a modem would supply. In addition, placing a scope on the standby link shows that the Lucent 5ESS is sending Set Asynchronous Balance Mode (SABM) requests on the standby link. The OSS monitoring applications ignore the SABMs on the standby link. If a network replaces the dedicated circuits, it must provide control leads and ignore the SABMs on the standby link. Some OSS applications will send out SABMs on the standby link that will be ignored by the Lucent 5ESS switch. For example, the Lucent NFM application with a Datakit communications front end will send out SABMs on the standby link.
On the active link, BX.25 is being passed using LAPB. The Lucent 5ESS telephone switch and the monitoring application are typically configured for seven PVCs on both the specialized common carrier 0SCC0) and SCC1 connections. The links can be configured for up to nine virtual channels.
The following list provides the PVCs that the switch can use on the monitoring channels. A definition of the type of data carried on each of the PVCs is also provided.
•
•
•
•
•
•
•
•
•
The central office technician can switch the links from the console on the Lucent 5ESS telephone switch. The fail-over between the links is done at the LAPB layer. Remember that the original design assumed that the connections were over private line circuits, so LAPB was used to control the links. The Lucent telephone switch issues a LAPB disconnect frame to remove a link.
The following example shows information provided in a LAPB disconnect frame:
03 61 a0 57 .a.W(EQ) 10 19:15:34.6988116 LAPB: Addr=001 Type=DISC/RD P/F=1(F) FCS=GoodRecord #10 (EQ) Captured on 04.19.01 at 19:15:34.698811606 Length = 4LAPB:Address = 001Frame Type = 0x53 (DISC/RD)Control Information = 0x53...1 .... P/F Bit = 1 (Final)FCS = 0x81-76 (Good)Record #10 (EQ) Captured on 04.19.01 at 19:15:34.698811606 Length = 4The LAPB disconnect frame tears down the X.25 layer and causes the Lucent 5ESS telephone switch and a network monitoring application, such as the Lucent NFM application bundle, to respond to SABMs on the standby link (see Figure 19).
Figure 19 Redundant Serial Links for Telephone Switch Monitoring Applications
The standby link becomes the active link and the active link becomes the backup. The original configuration assumed by LAPB would be passed between an OSS such as the Lucent NFM, or the Network Management Application (NMA) application by Telcordia, and the Lucent 5ESS telephone switch. Essentially, LAPB is used to verify that the network is up end to end.
The Lucent Datakit Network
A typical Datakit network is shown in Figure 20.
Figure 20 Typical Datakit Network
The Datakit node is providing the communications front end to the network management application (NFM or NMA). BX.25 packets are transmitted from Synchronous Line Module (SLM) cards on the Datakit node. The Datakit acts as a transport. The NFM application has two connections, SCC0 and SCC1, for redundancy. The NFM host is supplying leads on both interfaces but ignoring SABMs on the standby interface. The NFM is sending out the SABMs that the Lucent 5ESS switch is ignoring. If communication is lost on the active interface, the NFM host will respond to the SABMs on the standby interface and it will become the active interface. The Lucent 5ESS console indicates which interface is active and which is in standby mode.
Migrating to TCP/IP Using Cisco STUN
The Cisco STUN feature provides another way that customers can migrate the switch monitoring portion of a DCN to a TCP/IP network.
In this solution, the network administrator configures STUN on both the SCC0 and SCC1 connection, thereby enabling both links to act as circuits. The STUN feature looks like a pair of circuits to the OSS and the Lucent 5ESS. The LAPB layer is passed end to end. LAPB will control the link as designed.
The routers are acting as a circuit or a cable extension. The fail-over or recovery mechanism is initiated only by the end devices—the network monitoring application at one end of the network and the Class 5 telephone switch at the other end of the network. A LAPB disconnect frame can be used as the fail-over mechanism when configured for a pair of circuits. The only disadvantage to this solution is that STUN is time sensitive; that is, if another application applies a heavy load to the links, the connection may time out.
Figure 21 shows how some telcos have updated a DCN that uses the Lucent NFM application by removing the Lucent Datakit network with its proprietary trunk and replacing it with Cisco routers and TCP/IP. A Datakit node acts as a front end for the NFM application as described in the previous section. A STUN tunnel is configured for each of the SCC channels, from the Lucent NFM and Datakit node OSS at the NOC across the TCP/IP network, to the Lucent 5ESS telephone switch in the central office.
Figure 21 Lucent NFM Connection to a Lucent 5ESS Switch Using STUN
Each STUN tunnel is connected to separate physical interfaces. In Figure 21, the SCC0 interface is connected to STUN tunnel 1. The SCC1 interface is connected to STUN tunnel 2. The routers forward the packets across the network in a way similar to a leased-line circuit with modems. The only places that X.25 parameters can be set are on the Datakit node and the Lucent 5ESS telephone switch.
Lucent has developed a new communications server, the Element Mediation Module (EMM), which is an alternative to using a Datakit node for a communications server (see Figure 22). As with the configuration seen in Figure 21, the end devices control the X.25 exchange; the routers only forward packets across the network. The only places that X.25 parameters can be set are on the EMM and the Lucent 5ESS switch. One difference from the Datakit front end is that the EMM will shut down the standby interface, so the control leads are dropped and no SABMs are sent out from the EMM on the standby interface.
In Figure 22, the NFM/EMM combination and Class 5 telephone switch will set up the X.25 connection on either SCC0 or SCC1. Seven PVCs will be set up across the X.25 connection, sequentially numbered 1 through 7. The STUN-configured routers just forward the LAPB packets. The routers do not participate at the LAPB or X.25 layers. The end devices control the PVCs, and either device can reset the PVCs.
Figure 22 NFM/EMM with Cisco STUN Solution
In early testing with the NFM/EMM solution, customers have found that the end devices would not wait long enough for a link to come up before resetting the link and initializing a backup link, so the seven PVCs were never established. There are controls in the EMM for starting and resetting the links. The default delay timer should be increased on the EMM in this situation. This increase is accomplished in the startup script on the EMM. EMM version 6.2 or later is required.
Configuring STUN on the Workstation Side of the Network
To configure the STUN tunnel on the workstation side of the telco DCN, see Figure 22 and perform the following steps. See the "Cisco STUN OSS Connectivity Solution: Examples" section for a configuration example. See the "Verifying Links in the Cisco STUN OSS Connectivity Solution" section for verification examples. See the "Debugging STUN Connections" section for debugging examples.
Step 1
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#Step 2
Router(config)# hostname Router-2611Step 3
Router-2611(config)# stun peer-name 10.10.10.2Router-2611(config)# stun protocol-group 101 basicRouter-2611(config)# stun protocol-group 102 basicConfigure the Ethernet Interface
Step 4
Router-2611(config)# interface ethernet 0/0Step 5
Router-2611(config-if)# ip address 10.10.10.2 255.255.255.0Step 6
Router-2611(config)# no keepalive
Tip
Step 7
Router-2611(config)# half-duplexStep 8
Router-2611(config-if)# endConfigure Serial Interface 1/2
Step 9
Router-2611(config)# interface serial 1/2Step 10
Router-2611(config-if)# no ip addressStep 11
Router-2611(config-if)# encapsulation stunStep 12
Router-2611(config-if)# clockrate 9600Step 13
Router-2611(config-if)# stun group 101Step 14
Router-2611(config-if)# stun route all tcp 10.10.10.1Step 15
Router-2611(config-if)# endConfigure Serial Interface 1/3
Step 16
Router-2611(config)# interface serial 1/3Step 17
Router-2611(config-if)# no ip addressStep 18
Router-2611(config-if)# encapsulation stunStep 19
Router-2611(config-if)# clockrate 9600Step 20
Router-2611(config-if)# stun group 102Step 21
Router-2611(config-if)# stun route all tcp 10.10.10.1Step 22
Router-2611(config-if)# endRouter-2611(config)# endStep 23
Router-2611# copy run startDestination filename [startup-config]?Building configuration...[OK]
Configuring STUN on the Telephone Switch Side of the Network
To configure the STUN tunnel on the telephone switch side of the telco DCN, see Figure 22 and perform the following steps. See the "Cisco STUN OSS Connectivity Solution: Examples" section for configuration examples. See the "Verifying Links in the Cisco STUN OSS Connectivity Solution" section for verification examples. See the "Debugging STUN Connections" section for debugging examples.
Step 1
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#Step 2
Router(config)# hostname Router-3640R1Step 3
Router-3640R1(config)# stun peer-name 10.10.10.1Router-3640R1(config)# stun protocol-group 101 basicRouter-3640R1(config)# stun protocol-group 102 basicConfigure the Ethernet Interface
Step 4
Router-3640R1(config)# interface ethernet 0/0Step 5
Router-3640R1(config-if)# ip address 10.10.10.2 255.255.255.0Step 6
Router-3640R1(config-if)# half-duplexStep 7
Router-3640R1(config-if)# endConfigure Serial Interface 1/2
Step 8
Router-3640R1(config)# interface serial 1/2Step 9
Router-3640R1(config-if)# no ip addressStep 10
Router-3640R1(config-if)# encapsulation stunStep 11
Router-3640R1(config-if)# clockrate 9600Step 12
Router-3640R1(config-if)# stun group 101Step 13
Router-3640R1(config-if)# stun route all tcp 10.10.10.2Step 14
Router-3640R1(config-if)# endConfigure Serial Interface 1/3
Step 15
Router-3640R1(config)# interface serial 1/3Step 16
Router-3640R1(config-if)# no ip addressStep 17
Router-3640R1(config-if)# encapsulation stunStep 18
Router-3640R1(config-if)# clockrate 9600Step 19
Router-3640R1(config-if)# stun group 102Step 20
Router-3640R1(config-if)# stun route all tcp 10.10.10.2Step 21
Router-3640R1(config-if)# endRouter-3640R1(config)# endStep 22
Router-3640R1# copy run startDestination filename [startup-config]?Building configuration...[OK]
Cisco STUN OSS Connectivity Solution: Examples
This section provides examples of the following configurations and status reports:
•
•
In the following examples, the communications front end for the NFM application is an EMM server. The SCC links from the EMM server are connected to a Cisco 2611 router named Router-2611, as shown in Figure 23.
Figure 23 NFM/EMM with Cisco STUN Solution
The cables connecting the EMM to the Cisco 2611 router are Cisco V.35 DCE, which is a CAB-V.35MC (cable part number 72-08002-01). The cables connecting the Lucent 5ESS to the Cisco 3640R1 router are Cisco EIA/TIA-232 DCE (cable part number 72-0794-01). The Cisco 2611 router is connected using an Ethernet cross-over cable to a Cisco 3640R1 router, which is connected using SCC0 and SCC1 to the 3B21 device on the Lucent 5ESS.
Note
The configuration examples show two tunnel groups configured as type basic. Tunnel group 101 is assigned to serial interface 1/2 on the Cisco 2611 router, and serial interface 1/2 on the Cisco 3640R1 router. Tunnel group 102 is assigned to serial interface 1/3 on the Cisco 2611 router, and serial interface 1/3 on the Cisco 3640R1 router.
Cisco 2611 Edge Router STUN Connection to the Workstation: Example
The following example shows the configuration for a Cisco 2611 router named Router-2611. Notice that the peer name is the IP address of the Ethernet interface on the router. Another and better possibility would be to use a loopback IP address that cannot go down instead of the peer name. A STUN group of 101 is assigned to serial interface 1/2. All of the traffic arriving on serial interface 1/2 will be encapsulated in TCP/IP packets and forwarded across the IP cloud to the Cisco 3640R1 router at IP address 10.10.10.1. All of the traffic arriving on serial interface 1/3 is assigned to STUN group 102 and is forwarded across the network to IP address 10.10.10.1.
hostname Router-2611!stun peer-name 10.10.10.2stun protocol-group 101 basicstun protocol-group 102 basic!interface Ethernet0/0ip address 10.10.10.2 255.255.255.0no keepalivehalf-duplex!interface Serial1/2no ip addressencapsulation stunclockrate 9600stun group 101stun route all tcp 10.10.10.1!interface Serial1/3no ip addressencapsulation stunclockrate 9600stun group 102stun route all tcp 10.0.10.1Cisco 3640R1 Edge Router STUN Connection to the Telephone Switch: Example
The following example shows the configuration for a Cisco 3640R1 edge router on the telephone switch side of the network. The peer name is the IP address of the Ethernet interface on the router; however, you could use a loopback IP address that cannot go down, instead of the peer name. A STUN group of 101 is assigned to serial interface 1/2. All of the traffic arriving on serial interface 1/2 will be encapsulated in TCP/IP packets and forwarded across the IP cloud to the Cisco 2611 router at IP address 10.10.10.2. All of the traffic arriving on serial interface 1/3 is assigned to STUN group 102 and is forwarded across the network to IP address 10.10.10.2.
hostname Router-3640R1stun peer-name 10.10.10.1stun protocol-group 101 basicstun protocol-group 102 basic!interface Ethernet0/0ip address 10.10.10.1 255.255.255.0half-duplextarp enable!interface Serial1/2no ip addressencapsulation stunclockrate 9600stun group 101stun route all tcp 10.10.10.2!interface Serial1/3no ip addressencapsulation stunclockrate 9600stun group 102stun route all tcp 10.10.10.2Verifying Links in the Cisco STUN OSS Connectivity Solution
The following examples show how to verify the two STUN links. Use the show interface EXEC command on the two serial interfaces, and check that the line protocol is up and encapsulation set for the link is STUN.
Router-3640R1# show interface serial 1/2Serial1/2 is up, line protocol is upHardware is CD2430 in sync modeMTU 2104 bytes, BW 128 Kbit, DLY 20000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation STUN, loopback not setLast input 00:00:02, output 00:00:40, output hang neverLast clearing of "show interface" counters 00:20:56Queueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec155 packets input, 316 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort9 packets output, 43 bytes, 0 underruns0 output errors, 0 collisions, 2 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsDCD=up DSR=up DTR=up RTS=up CTS=upRouter-3640R1# show interface serial 1/3Serial1/3 is up, line protocol is upHardware is CD2430 in sync modeMTU 2104 bytes, BW 128 Kbit, DLY 20000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation STUN, loopback not setLast input 00:00:00, output 00:00:00, output hang neverLast clearing of "show interface" counters 00:21:00Queueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 1 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec527 packets input, 3295 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort77 packets output, 275 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out4 carrier transitionsDCD=up DSR=up DTR=up RTS=up CTS=upUse the show stun EXEC command on the Cisco 3640R1 router to display a report on the two tunnels. As shown in the following example, the peer address for the tunnel is the IP address assigned to Ethernet interface 0/0 on the Cisco 3640R1 router, so the router is peered to itself at IP address 10.10.10.1. The tunnel on serial interface 1/2 is tunnel group 101 and is a basic tunnel. All traffic is routed to IP address 10.10.10.2, which is the IP address of Ethernet interface 0/0 on the Cisco 2611 router.
Group 101 is the SCC0 link. The state of the tunnel is open or up. If the tunnel was down, the state would be marked closed. The number of packets received is 1042, and the number of packets transmitted is 1025.
Group 102 is the SCC1 link. The tunnel is connected to IP address 10.10.10.2, which is the Cisco 2611 router and serial interface 1/3. The state of the tunnel is open or up. The number of packets transmitted is 318, and the number of packets received is 1013. The SCC1 link was not configured correctly, so the interface shows 83 dropped packets.
Looking at the counters is one method of determining if the tunnel is functioning.
Router-3640R1# show stunThis peer: 10.10.10.1*Serial1/2 -- scc0 (group 101 [basic])state rx_pkts tx_pkts dropsall TCP 10.10.10.2 open 1042 1025 0Serial1/3 -- scc1 on 5ESS (group 102 [basic])state rx_pkts tx_pkts dropsall TCP 10.10.10.2 open 318 1013 83Debugging STUN Connections
The possible STUN debugs are shown in the following example, and can be used to perform basic debugging of the STUN tunnels:
Router-3640R1# debug stun ?events STUN connections and statuspacket All STUN activitytg Display stun transmission groupsTo make sure data is passing across the tunnels, enter the debug stun packet command. A sample debug report and a detailed description of the first two packets follow:
Router-3640R1# debug stun packetSTUN packet debugging is onRouter-3640R1#00:40:01: STUN basic: 00:06:16 Serial1/2 NDI: Data: 034300:40:01: STUN basic: 00:00:00 Serial1/2 SDI: Data: 030f00:40:05: STUN basic: 00:00:04 Serial1/2 SDI: Data: 013f00:40:06: STUN basic: 00:00:00 Serial1/2 NDI: Data: 017300:40:06: STUN basic: 00:00:00 Serial1/2 SDI: Data: 011100:40:06: STUN basic: 00:00:00 Serial1/2 NDI: Data: 03001000fb000000:40:06: STUN basic: 00:00:00 Serial1/2 NDI: Data: 011100:40:06: STUN basic: 00:00:00 Serial1/2 SDI: Data: 032100:40:06: STUN basic: 00:00:00 Serial1/2 SDI: Data: 012010020500:40:06: STUN basic: 00:00:00 Serial1/2 SDI: Data: 012210034100:40:06: STUN basic: 00:00:00 Serial1/2 SDI: Data: 012410040100:40:06: STUN basic: 00:00:00 Serial1/2 NDI: Data: 0141Following are detailed descriptions of the first two packets from the debug report:
00:40:01: STUN basic: 00:06:16 Serial1/2 NDI: Data: 0343STUN basic: the encapsulation scheme is basic00:06:16: time elapsed from the previous packet .Serial1/2: Interface reporting the eventNDI: The data is received from the NetworkData: 0343: The data received from the Network00:40:01: STUN basic: 00:00:00 Serial1/2 SDI: Data: 030fSTUN basic: the encapsulation scheme is basic00:00:00: time elapsed from the previous packet .Serial1/2: Interface reporting the eventSDI: The data is received from the Serial LinkData: 030f: The data received from the Serial LinkSwitch Monitoring Networks: Cisco X.25 BAI OSS Connectivity Solution
The Cisco X.25 BAI OSS connectivity solution is described in the following sections:
•
•
•
•
•
•
Cisco X.25 BAI OSS Connectivity Overview
One of the downfalls to the STUN solution is scaling. The service provider must dedicate two ports on the OSS for every Lucent 5ESS telephone switch, which makes for many circuits tunneled across an IP network.
Service providers want to take advantage of the scaling inherent in the X.25 protocol. Cisco has developed a solution to allow a customer to configure an OSS with an X.25 SVC to connect the active SCC link on a Lucent 5ESS telephone switch. The key pieces of the solution are the Cisco X.25 Backup Active Interface (BAI) feature, X.25 SVC-to-PVC conversion, and X.25 address substitution. The Cisco X.25 BAI feature preserves the original redundancy and monitoring capability available from SCC0 and SCC1 links in DCN, but uses SVCs to route X.25, thereby greatly reducing the number of interfaces required in the DCN.
In Figure 24, the Datakit node provides the communications front end to a network management application and provides two links, SCC0 and SCC1, for link redundancy. One link is active and passes data across the network; the other remains in standby mode.
Figure 24 Network Management Application Monitors Lucent 5ESS Switch over Datakit Network
The Datakit node acts as a transport, so that to the network management application and the Lucent 5ESS switch, the node looks like it has two individual circuits. The network management application host is supplying leads on both interfaces but ignoring SABM messages on the standby interface. If communication is lost on the active interface, the network management application host responds to the SABM messages on the standby interface and it becomes the active interface.
As Figure 25 shows, Cisco offers solutions that allow telco service providers to reduce operating costs, translate and migrate existing X.25-based DCNs to IP-based DCNs, and bridge traditional telephony operations to newer ones.
Figure 25 Network Management Application Monitors Lucent 5ESS Switch over IP Network
The Cisco X.25 BAI feature is a part of the Cisco IOS Telco Feature Set, a bundle of applications specific to the DCN environment. Specifically, the Cisco X.25 BAI feature provides dual serial interfaces to preserve the redundancy and monitoring capability available from the SCC0 and SCC1 links on the Lucent 5ESS switch in the DCN network.
Adding Cisco X.25 BAI to the Telco DCN
The following sections describe how to incorporate the Cisco X.25 BAI feature in a telco DCN using the Telcordia NMA switch monitoring application.
In Figure 25, a Cisco 3631 router is connected over a serial connection to the NMA application. The Cisco 3631 router is connected over a TCP/IP backbone to a Cisco 3662 router in the central office. The Cisco 3662 router has two serial connections to the Lucent 5ESS telephone switch and the connections are terminated on SCC0 and SCC1, on the switch.
In the configurations included in this section, the NMA host will be configured with seven X.25 SVCs. The SVCs will be put into an XOT tunnel on the Cisco 3631 router and forwarded across the network. The Cisco 3662 router will then terminate the XOT session and convert the seven SVCs to seven PVCS.
The backup active interface interface configuration command is configured on the Cisco 3662 router. The backup active interface command causes the interface with the standby link on it to go into testing mode. The testing mode brings the leads high but ignores the SABMs from the Lucent 5ESS telephone switch. The backup active interface command allows the router to switch between serial ports when a LAPB disconnect frame is received on the active interface.
Configuring Cisco X.25 BAI on the NMA Side of the Network
To configure a backup active interface on the NMA side of the telco DCN, see Figure 25 and perform the following steps. See the "NMA Gateway Configuration: Example" section and "NMA-Side Configuration: Example" section for configuration examples. See the "Verifying Address Substitutions" section for verification examples.
Step 1
Router-3631# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 2
Router-3631(config)# x25 routingStep 3
Router-3631(config)# interface serial 1/1Step 4
Router-3631(config-if)# no ip addressStep 5
Router-3631(config-if)# encapsulation x25 dceStep 6
Router-3631(config-if)# no ip mroute-cacheStep 7
Router-3631(config-if)# x25 version 1980Step 8
Router-3631(config-if)# x25 htc 64Step 9
Router-3631(config-if)# x25 wout 4Step 10
Router-3631(config-if)# clockrate 56000Step 11
Router-3631(config-if)# x25 route 5550427111101 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222201 xot 10.60.128.8Step 12
Router-3631(config-if)# x25 route 5550427111102 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222202 xot 10.60.128.8Step 13
Router-3631(config-if)# x25 route 5550427111103 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222203 xot 10.60.128.8Step 14
Router-3631(config-if)# x25 route 5550427111104 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222204 xot 10.60.128.8Step 15
Router-3631(config-if)# x25 route 5550427111105 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222205 xot 10.60.128.8Step 16
Router-3631(config-if)# x25 route 5550427111106 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222206 xot 10.60.128.8Step 17
Router-3631(config-if)# x25 route 5550427111107 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222207 xot 10.60.128.8Step 18
Router-3631(config-if)# endRouter-3631(config)# endStep 19
Router-3631# copy run startDestination filename [startup-config]?Building configuration...[OK]
NMA Gateway Configuration: Example
In the following NMA gateway configuration, the X.121 address assigned to the NMA gateway is 5550427222200. The gateway is configured for no PVCs and SVCs with a range of 1 to 64. The packet size is 128 and the window size is 4. The NMA is set up as a DTE.
02-05-17 13:49:51 edt x25 config (ocs_x25_cnfg) jump:Gateway name: j1g08061 gateway type: standarddevice name: %nmasp1#j1g08061asgnd module: %nmasp1#m1gateway stat: enablelocal address: 5550427222200station type: dtenetwork type: standard min lcn: 1baud: 9600 max lcn: 64def thru class: 75 def window size: 4max packet size: 128 ack window size: 4def packet size: 128 num pvc: 0flow control neg: no pvc origin: 1thruput neg: no defer_dsl: yeslap t1: 3 fast select: nolap t2: 0 facility marker: no chanloopback: nolap n2: 20 sys err: yestrace: nolap K: 7 ignore D bit: no chantrace: noThe following example lists a target configuration for one of the channels. The example shows that the channel will be mapped to PVC 4 on the Lucent 5ESS 5 telephone switch. PVC 4 is a TTY input used as the ADMIN channel. The X.25 called address for the Cisco 3662 router is 5550427111104. The subaddress 04 is used to map the address to PVC 4.
02-05-17 14:08:26 edt target config (ocs_target_cnfg) jump:target id: wngrflxads0 target type: switchchannel id: admin platform: vos alt class:target model: 5ess_admin surveil mode: directchan status: connect monitor timer: 0alwayschannel type: raw msg log: yestarget group:ne user id: ne password: *init script: no deactivation script: noprotocol: native x25_svc parity: no line type: non_dialcls user grp:gateway name: j1g08061call address: 5550427111104NMA-Side Configuration: Example
In the following example, the NMA is connected to serial interface 1/1 on a Cisco 3631 router. The interface is configured for X.25 SVCs only, and the SVC range is 1 to 64. The incoming and outgoing X.25 packet size is the Cisco IOS default 128; the X.25 window size is 4.
x25 routing!interface Serial1/1no ip addressencapsulation x25 dceno ip mroute-cachex25 version 1980x25 htc 64x25 win 4x25 wout 4clockrate 56000Verifying Address Substitutions
The NMA will place seven X.25 calls to the Cisco 3662 router, but the router interface can have only one X.121 address and does not support subaddressing. The configuration must work around this restriction, and does so using X.121 address substitution.
NMA is set up to distinguish between virtual circuits by the unique called X.121 address. The X.121 address of the Cisco 3662 router interface is 5550427111100, and NMA adds a subaddress to make each X.121 call unique, so the example target configuration for the ADMIN channel contains an X.121 call to 5550427111104.
Remember that the Cisco 3662 router interface supports only one X.121 address and does not support subaddressing, so the Cisco 3631 router configuration substitutes the X.121 called address with the X.121 address on serial interface 4/0 of the Cisco 3662 router. The same X.121 address is assigned to serial interface 4/1 because serial interface 4/1 is the backup active interface for serial interface 4/0.
In addition, the Cisco 3662 router needs a unique source X.121 address for each SVC to map to the appropriate PVC; the configuration adds a unique subaddress to each calling address. Table 4 lists the address substitutions.
The configuration moves the subaddress from the called address to the calling address. The configuration is accommodating the limitations of the host and the Cisco IOS software.
The following partial example lists the global commands that perform the address substitution:
x25 route 5550427111101 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222201 xot 10.60.128.8!x25 route 5550427111102 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222202 xot 10.60.128.8!x25 route 5550427111103 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222203 xot 10.60.128.8!x25 route 5550427111104 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222204 xot 10.60.128.8!x25 route 5550427111105 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222205 xot 10.60.128.8!x25 route 5550427111106 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222206 xot 10.60.128.8!x25 route 5550427111107 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222207 xot 10.60.128.8To verify the X.121 address substitutions, perform the following steps:
Step 1
Router# show x25 route# Match Substitute Route to1 dest 5550427111101 source 5550427222200Sub-dest 5550427111100Sub-source 5550427222201xot 10.60.128.82 dest 5550427111102 source 5550427222200Sub-dest 5550427111100Sub-source 5550427222202xot 10.60.128.83 dest 5550427111103 source 5550427222200Sub-dest 5550427111100Sub-source 5550427222203xot 10.60.128.84 dest 5550427111104 source 5550427222200Sub-dest 5550427111100Sub-source 5550427222204xot 10.60.128.85 dest 5550427111105 source 5550427222200Sub-dest 5550427111100Sub-source 5550427222205xot 10.60.128.86 dest 5550427111106 source 5550427222200Sub-dest 5550427111100Sub-source 5550427222206xot 10.60.128.87 dest 5550427111107 source 5550427222200Sub-dest 5550427111100Sub-source 5550427222207xot 10.60.128.8Step 2
Router# show x25 vcSVC 58, State: D1, Interface: Serial1/1Started 00:15:54, last input 00:15:37, output 00:00:03Connects 5550427222205 <--> 5550427111100 toXOT between 10.59.251.66, 11102 and 10.60.128.8, 1998Window size input: 4, output: 4Packet size input: 128, output: 128PS: 5 PR: 0 ACK: 0 Remote PR: 5 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 111340/2 packets 1021/2 Resets 1/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 59, State: D1, Interface: Serial1/1Started 00:15:57, last input 00:15:40, output 00:00:58Connects 5550427222203 <--> 5550427111100 toXOT between 10.59.251.66, 11101 and 10.60.128.8, 1998Window size input: 4, output: 4Packet size input: 128, output: 128PS: 5 PR: 3 ACK: 3 Remote PR: 5 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 1130/4 packets 13/3 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 60, State: D1, Interface: Serial1/1Started 00:15:57, last input 00:15:39, output 00:00:58Connects 5550427222202 <--> 5550427111100 toXOT between 10.59.251.66, 11100 and 10.60.128.8, 1998Window size input: 4, output: 4Packet size input: 128, output: 128PS: 2 PR: 2 ACK: 0 Remote PR: 2 RCNT: 2 RNR: TxP/D state timeouts: 0 timer (secs): 0data bytes 680/2 packets 10/2 Resets 0/0 RNRs 7/0 REJs 0/0 INTs 0/0SVC 61, State: D1, Interface: Serial1/1Started 00:15:59, last input 00:15:14, output 00:00:00Connects 5550427222201 <--> 5550427111100 toXOT between 10.59.251.66, 11099 and 10.60.128.8, 1998Window size input: 4, output: 4Packet size input: 128, output: 128PS: 2 PR: 0 ACK: 0 Remote PR: 2 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 9000/10 packets 450/6 Resets 2/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 62, State: D1, Interface: Serial1/1Started 00:15:59, last input 00:15:36, output 00:15:38Connects 5550427222207 <--> 5550427111100 toXOT between 10.59.251.66, 11098 and 10.60.128.8, 1998Window size input: 4, output: 4Packet size input: 128, output: 128PS: 1 PR: 2 ACK: 2 Remote PR: 1 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 103/2 packets 1/2 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 63, State: D1, Interface: Serial1/1Started 00:16:01, last input 00:12:18, output 00:12:16Connects 5550427222204 <--> 5550427111100 toXOT between 10.59.251.66, 11097 and 10.60.128.8, 1998Window size input: 4, output: 4Packet size input: 128, output: 128PS: 6 PR: 7 ACK: 7 Remote PR: 6 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 224/13 packets 14/7 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 64, State: D1, Interface: Serial1/1Started 00:16:01, last input 00:15:37, output 00:15:37Connects 5550427222206 <--> 5550427111100 toXOT between 10.59.251.66, 11096 and 10.60.128.8, 1998Window size input: 4, output: 4Packet size input: 128, output: 128PS: 6 PR: 3 ACK: 3 Remote PR: 6 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 70/9 packets 6/3 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [10.60.128.8,1998/10.59.251.66,11096]Started 00:16:01, last input 00:15:37, output 00:15:37Connects 5550427222206 <--> 5550427111100 from Serial1/1 SVC 64Window size input: 4, output: 4Packet size input: 128, output: 128PS: 3 PR: 6 ACK: 6 Remote PR: 3 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 9/70 packets 3/6 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [10.60.128.8,1998/10.59.251.66,11097]Started 00:16:01, last input 00:12:18, output 00:12:18Connects 5550427222204 <--> 5550427111100 from Serial1/1 SVC 63Window size input: 4, output: 4Packet size input: 128, output: 128PS: 7 PR: 6 ACK: 6 Remote PR: 7 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 13/224 packets 7/14 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [10.60.128.8,1998/10.59.251.66,11098]Started 00:15:59, last input 00:15:39, output 00:15:36Connects 5550427222207 <--> 5550427111100 from Serial1/1 SVC 62Window size input: 4, output: 4Packet size input: 128, output: 128PS: 2 PR: 1 ACK: 1 Remote PR: 2 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 2/103 packets 2/1 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [10.60.128.8,1998/10.59.251.66,11099]Started 00:15:59, last input 00:00:01, output 00:15:15Connects 5550427222201 <--> 5550427111100 from Serial1/1 SVC 61Window size input: 4, output: 4Packet size input: 128, output: 128PS: 0 PR: 2 ACK: 2 Remote PR: 0 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 10/9000 packets 6/450 Resets 0/2 RNRs 0/0 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [10.60.128.8,1998/10.59.251.66,11100]Started 00:15:59, last input 00:00:59, output 00:15:40Connects 5550427222202 <--> 5550427111100 from Serial1/1 SVC 60Window size input: 4, output: 4Packet size input: 128, output: 128PS: 2 PR: 2 ACK: 2 Remote PR: 0 RCNT: 0 RNR: RxP/D state timeouts: 0 timer (secs): 0data bytes 2/680 packets 2/10 Resets 0/0 RNRs 0/7 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [10.60.128.8,1998/10.59.251.66,11101]Started 00:15:59, last input 00:00:59, output 00:15:41Connects 5550427222203 <--> 5550427111100 from Serial1/1 SVC 59Window size input: 4, output: 4Packet size input: 128, output: 128PS: 3 PR: 5 ACK: 5 Remote PR: 3 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 4/1130 packets 3/13 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [10.60.128.8,1998/10.59.251.66,11102]Started 00:15:56, last input 00:00:00, output 00:15:38Connects 5550427222205 <--> 5550427111100 from Serial1/1 SVC 58Window size input: 4, output: 4Packet size input: 128, output: 128PS: 0 PR: 7 ACK: 7 Remote PR: 0 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 2/111560 packets 2/1023 Resets 0/1 RNRs 0/0 REJs 0/0 INTs 0/0Step 3
SVC 63, State: D1, Interface: Serial1/1Started 00:16:01, last input 00:12:18, output 00:12:16Connects 5550427222204 <--> 5550427111100 toXOT between 10.59.251.66, 11097 and 10.60.128.8, 1998Window size input: 4, output: 4Packet size input: 128, output: 128PS: 6 PR: 7 ACK: 7 Remote PR: 6 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 224/13 packets 14/7 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0In the following example, SVC 63 is mapped to SVC 1 on the XOT connection:
SVC 1, State: D1, Interface:[10.60.128.8,1998/10.59.251.66,11097]Started 00:16:01, last input 00:12:18, output 00:12:18Connects 5550427222204 <--> 5550427111100 from Serial1/1 SVC 63Window size input: 4, output: 4Packet size input: 128, output: 128PS: 7 PR: 6 ACK: 6 Remote PR: 7 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 13/224 packets 7/14 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0
Configuring Cisco X.25 BAI on the Telephone Switch Side of the Network
To configure a backup active interface on the telephone switch side of the telco DCN, see Figure 25 and perform the following steps. See the "X.25 BAI Telephone Switch Side Configuration: Example" section for a configuration example. See the "Verifying PVC-to-SVC Conversions" section for a verification example.
Step 1
Router-3662# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 2
Router-3662(config)# x25 routingConfigure the Active Serial Interface
Step 3
Router-3662(config)# interface serial 4/0Step 4
Router-3662(config-if)# SCC0 Link to 5ESS (UnManaged)Step 5
Router-3662(config-if)# no ip addressStep 6
Router-3662(config-if)# encapsulation x25 dceStep 7
Router-3662(config-if)# backup active interface serial 4/1Step 8
Router-3662(config-if)# x25 version 1980Step 9
Router-3662(config-if)# x25 address 5550427111100Step 10
Router-3662(config-if)# x25 ltc 8Step 11
Router-3662(config-if)# x25 t10 30Step 12
Router-3662(config-if)# x25 t12 30Step 13
Router-3662(config-if)# x25 win 4Step 14
Router-3662(config-if)# x25 wout 4Step 15
Router-3662(config-if)# x25 threshold 1Step 16
Router-3662(config-if)# x25 pvc 1 svc 5550427222201 packetsize 128 128 windowsize 4 4Router-3662(config-if)# x25 pvc 2 svc 5550427222202 packetsize 128 128 windowsize 4 4Router-3662(config-if)# x25 pvc 3 svc 5550427222203 packetsize 128 128 windowsize 4 4...Router-3662(config-if)# x25 pvc 7 svc 5550427222207 packetsize 128 128 windowsize 4 4Step 17
Router-3662(config-if)# clockrate 9600Step 18
Router-3662(config-if)# lapb t1 5000Step 19
Router-3662(config-if)# lapb t2 200Step 20
Router-3662(config-if)# lapb t4 10Step 21
Router-3662(config-if)# lapb n2 7Step 22
Router-3662(config-if)# lapb k 4Step 23
Router-3662(config-if)# endConfigure the Backup Serial Interface
Step 24
Router-3662(config)# interface serial 4/1Step 25
Router-3662(config-if)# SCC1 Link (UnManaged)Step 26
Router-3662(config-if)# no ip addressStep 27
Router-3662(config-if)# encapsulation x25 dceStep 28
Router-3662(config-if)# x25 version 1980Step 29
Router-3662(config-if)# x25 address 5550427111100Step 30
Router-3662(config-if)# x25 ltc 8Step 31
Router-3662(config-if)# x25 t10 30Step 32
Router-3662(config-if)# x25 t12 30Step 33
Router-3662(config-if)# x25 win 4Step 34
Router-3662(config-if)# x25 wout 4Step 35
Router-3662(config-if)# x25 threshold 1Step 36
Router-3662(config-if)# x25 pvc 1 svc 5550427222201 packetsize 128 128 windowsize 4 4Router-3662(config-if)# x25 pvc 2 svc 5550427222202 packetsize 128 128 windowsize 4 4Router-3662(config-if)# x25 pvc 3 svc 5550427222203 packetsize 128 128 windowsize 4 4...Router-3662(config-if)# x25 pvc 7 svc 5550427222207 packetsize 128 128 windowsize 4 4Step 37
Router-3662(config-if)# clockrate 9600Step 38
Router-3662(config-if)# lapb t1 5000Step 39
Router-3662(config-if)# lapb t2 200Step 40
Router-3662(config-if)# lapb t4 10Step 41
Router-3662(config-if)# lapb n2 7Step 42
Router-3662(config-if)# lapb k 4Step 43
Router-3662(config-if)# endEnable X.25 Routing
Step 44
Router-3662(config)# x25 route 55504271111 interface serial 4/0Step 45
Router-3662(config)# x25 route 55504271111 interface serial 4/1Step 46
Router-3662(config)# endStep 47
Router-3662# copy run startDestination filename [startup-config]?Building configuration...[OK]
X.25 BAI Telephone Switch Side Configuration: Example
The Cisco 3662 router in Figure 25 terminates the X.25 SVCs and converts them to the appropriate PVC. A unique calling address is used to map the SVC to the correct PVC mapping. Because the NMA does not actually generate a unique calling address, the unique calling address was created on the Cisco 3631 router using address substitution. The SVC-to-PVC conversion command is shown in the following example report for each interface.
In the following example, the ADMIN channel is mapped to PVC 4 by the calling address 5550427222204. The backup active interface command configures serial interface 4/1 as the backup to serial interface 4/0. The X.25 SVC call will be routed to the interface that is up (active). The X.25 routing table is built with the x25 route commands listed in the following example.
Serial interfaces 4/0 and 4/1 are set to a packet size of 128 and a window size of 4. Because BX.25 Issue 3 supports the 1980 version of X.25 code, you need to use the x25 version command (a hidden command) to set the interface to 1980. In addition, the router is configured to acknowledge every packet received with an X.25 threshold setting of one.
The following partial example lists the relevant router configuration commands for the Cisco 3662 router:
x25 routing!interface Serial4/0description SCC0 Link to 5ESS (UnManaged)no ip addressencapsulation x25 dcebackup active interface Serial4/1x25 version 1980x25 address 5550427111100x25 ltc 8x25 t10 30x25 t12 30x25 win 4x25 wout 4x25 threshold 1x25 pvc 1 svc 5550427222201 packetsize 128 128 windowsize 4 4x25 pvc 2 svc 5550427222202 packetsize 128 128 windowsize 4 4x25 pvc 3 svc 5550427222203 packetsize 128 128 windowsize 4 4x25 pvc 4 svc 5550427222204 packetsize 128 128 windowsize 4 4x25 pvc 5 svc 5550427222205 packetsize 128 128 windowsize 4 4x25 pvc 6 svc 5550427222206 packetsize 128 128 windowsize 4 4x25 pvc 7 svc 5550427222207 packetsize 128 128 windowsize 4 4clockrate 9600lapb T1 5000lapb T2 200lapb T4 10lapb N2 7lapb k 4!interface Serial4/1description SCC1 link (UnManaged)no ip addressencapsulation x25 dcex25 version 1980x25 address 5550427111100x25 ltc 8x25 t10 30x25 t12 30x25 win 4x25 wout 4x25 threshold 1x25 pvc 1 svc 5550427222201 packetsize 128 128 windowsize 4 4x25 pvc 2 svc 5550427222202 packetsize 128 128 windowsize 4 4x25 pvc 3 svc 5550427222203 packetsize 128 128 windowsize 4 4x25 pvc 4 svc 5550427222204 packetsize 128 128 windowsize 4 4x25 pvc 5 svc 5550427222205 packetsize 128 128 windowsize 4 4x25 pvc 6 svc 5550427222206 packetsize 128 128 windowsize 4 4x25 pvc 7 svc 5550427222207 packetsize 128 128 windowsize 4 4clockrate 9600lapb T1 5000lapb T2 200lapb T4 10lapb N2 7lapb k 4!x25 route 55504271111 interface Serial4/0x25 route 55504271111 interface Serial4/1Verifying PVC-to-SVC Conversions
The X.25 PVCs are mapped to the X.25 SVCs. For example, PVC 4 is connected to SVC 5550427222204 mapped to 5550427111100. The calling address is 5550427222204, which is the NMA address with the subaddress 04 on the end. The called address is the X.121 address assigned to serial interface 4/0 and 4/1, which is the X.121 address 5550427111100. In the following example, serial interface 4/0 is up and serial interface 4/1 is in testing mode:
Router# show x25 vcPVC 1, State: D1, Interface: Serial4/0Started 02:58:25, last input 00:00:00, output 00:01:39Connects 5550427222201 <--> 5550427111100 fromXOT between 10.60.128.8, 1998 and 10.59.251.66, 11161Window size input: 4, output: 4Packet size input: 128, output: 128PS: 2 PR: 0 ACK: 7 Remote PR: 2 RCNT: 1 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 20/24720 packets 16/1236 Resets 687/0 RNRs 0/0 REJs 0/0 INTs 0/0PVC 2, State: D1, Interface: Serial4/0Started 02:58:25, last input 00:01:45, output neverConnects 5550427222202 <--> 5550427111100 fromXOT between 10.60.128.8, 1998 and 10.59.251.66, 11163Window size input: 4, output: 4Packet size input: 128, output: 128PS: 0 PR: 4 ACK: 4 Remote PR: 0 RCNT: 0 RNR: RxP/D state timeouts: 0 timer (secs): 0data bytes 0/2924 packets 0/43 Resets 24/0 RNRs 0/46 REJs 0/0 INTs 0/0PVC 3, State: D1, Interface: Serial4/0Started 02:58:25, last input 00:01:45, output 00:01:38Connects 5550427222203 <--> 5550427111100 fromXOT between 10.60.128.8, 1998 and 10.59.251.66, 11166Window size input: 4, output: 4Packet size input: 128, output: 128PS: 2 PR: 4 ACK: 4 Remote PR: 2 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 24/4831 packets 16/63 Resets 10/0 RNRs 0/0 REJs 0/0 INTs 0/0PVC 4, State: D1, Interface: Serial4/0Started 02:58:30, last input 00:01:34, output 00:01:35Connects 5550427222204 <--> 5550427111100 fromXOT between 10.60.128.8, 1998 and 10.59.251.66, 11164Window size input: 4, output: 4Packet size input: 128, output: 128PS: 3 PR: 6 ACK: 6 Remote PR: 3 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 67/400 packets 19/38 Resets 5/0 RNRs 0/1 REJs 0/0 INTs 0/0PVC 5, State: D1, Interface: Serial4/0Started 02:57:35, last input 00:00:00, output 00:01:39Connects 5550427222205 <--> 5550427111100 fromXOT between 10.60.128.8, 1998 and 10.59.251.66, 11165Window size input: 4, output: 4Packet size input: 128, output: 128PS: 2 PR: 0 ACK: 5 Remote PR: 2 RCNT: 3 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 8/202550 packets 8/1806 Resets 872/0 RNRs 0/2 REJs 0/0 INTs 0/0PVC 6, State: D1, Interface: Serial4/0Started 02:58:32, last input 00:01:34, output 00:01:37Connects 5550427222206 <--> 5550427111100 fromXOT between 10.60.128.8, 1998 and 10.59.251.66, 11162Window size input: 4, output: 4Packet size input: 128, output: 128PS: 3 PR: 6 ACK: 6 Remote PR: 3 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 23/300 packets 11/22 Resets 6/0 RNRs 0/0 REJs 0/0 INTs 0/0PVC 7, State: D1, Interface: Serial4/0Started 02:58:32, last input 00:01:35, output 00:01:38Connects 5550427222207 <--> 5550427111100 fromXOT between 10.60.128.8, 1998 and 10.59.251.66, 11160Window size input: 4, output: 4Packet size input: 128, output: 128PS: 2 PR: 1 ACK: 1 Remote PR: 2 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 8/206 packets 8/2 Resets 6/0 RNRs 0/17 REJs 0/0 INTs 0/0PVC 1, State: P/Inactive, Interface: Serial4/1Started 02:58:32, last input 00:01:59, output 00:08:30PVC <--> SVC to 5550427222201, not connectedWindow size input: 4, output: 4Packet size input: 128, output: 128P/D state timeouts: 1 timer (secs): 0data bytes 16/67500 packets 12/3375 Resets 102/1 RNRs 0/0 REJs 0/0 INTs 0/0PVC 2, State: P/Inactive, Interface: Serial4/1Started 02:58:34, last input 00:03:20, output neverPVC <--> SVC to 5550427222202, not connectedWindow size input: 4, output: 4Packet size input: 128, output: 128P/D state timeouts: 0 timer (secs): 0data bytes 0/4624 packets 0/68 Resets 4/0 RNRs 0/66 REJs 0/0 INTs 0/0PVC 3, State: P/Inactive, Interface: Serial4/1Started 02:58:34, last input 00:16:27, output 00:07:03PVC <--> SVC to 5550427222203, not connectedWindow size input: 4, output: 4Packet size input: 128, output: 128P/D state timeouts: 0 timer (secs): 0data bytes 49/7378 packets 27/131 Resets 4/0 RNRs 0/0 REJs 0/0 INTs 0/0PVC 4, State: P/Inactive, Interface: Serial4/1Started 02:58:34, last input 00:06:55, output 00:06:56PVC <--> SVC to 5550427222204, not connectedWindow size input: 4, output: 4Packet size input: 128, output: 128P/D state timeouts: 0 timer (secs): 0data bytes 53/632 packets 23/46 Resets 4/0 RNRs 0/0 REJs 0/0 INTs 0/0PVC 5, State: P/Inactive, Interface: Serial4/1Started 02:58:36, last input 00:02:02, output 00:07:02PVC <--> SVC to 5550427222205, not connectedWindow size input: 4, output: 4Packet size input: 128, output: 128P/D state timeouts: 0 timer (secs): 0data bytes 9/719695 packets 9/6672 Resets 118/0 RNRs 0/1 REJs 0/0 INTs 0/0PVC 6, State: P/Inactive, Interface: Serial4/1Started 02:58:36, last input 00:07:01, output 00:07:01PVC <--> SVC to 5550427222206, not connectedWindow size input: 4, output: 4Packet size input: 128, output: 128P/D state timeouts: 0 timer (secs): 0data bytes 280/532 packets 28/56 Resets 5/0 RNRs 0/0 REJs 0/0 INTs 0/0PVC 7, State: P/Inactive, Interface: Serial4/1Started 02:58:36, last input 00:07:03, output 00:07:00PVC <--> SVC to 5550427222207, not connectedWindow size input: 4, output: 4Packet size input: 128, output: 128P/D state timeouts: 0 timer (secs): 0data bytes 11/17298 packets 11/142 Resets 5/0 RNRs 0/57 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [10.59.251.66,11160/10.60.128.8,1998]Started 00:02:01, last input 00:01:43, output 00:01:40Connects 5550427222207 <--> 5550427111100 from Serial4/0 PVC 7Window size input: 4, output: 4Packet size input: 128, output: 128PS: 1 PR: 2 ACK: 2 Remote PR: 1 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 103/2 packets 1/2 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [10.59.251.66,11161/10.60.128.8,1998]Started 00:02:01, last input 00:01:51, output 00:00:00Connects 5550427222201 <--> 5550427111100 from Serial4/0 PVC 1Window size input: 4, output: 4Packet size input: 128, output: 128PS: 6 PR: 2 ACK: 2 Remote PR: 4 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 1240/2 packets 62/2 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [10.59.251.66,11162/10.60.128.8,1998]Started 00:02:01, last input 00:01:42, output 00:01:39Connects 5550427222206 <--> 5550427111100 from Serial4/0 PVC 6Window size input: 4, output: 4Packet size input: 128, output: 128PS: 6 PR: 3 ACK: 3 Remote PR: 6 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 70/9 packets 6/3 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [10.59.251.66,11163/10.60.128.8,1998]Started 00:02:02, last input never, output 00:01:58Connects 5550427222202 <--> 5550427111100 from Serial4/0 PVC 2Window size input: 4, output: 4Packet size input: 128, output: 128PS: 4 PR: 0 ACK: 0 Remote PR: 4 RCNT: 0 RNR: TxP/D state timeouts: 0 timer (secs): 0data bytes 272/0 packets 4/0 Resets 0/0 RNRs 2/0 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [10.59.251.66,11164/10.60.128.8,1998]Started 00:02:03, last input 00:01:44, output 00:01:42Connects 5550427222204 <--> 5550427111100 from Serial4/0 PVC 4Window size input: 4, output: 4Packet size input: 128, output: 128PS: 6 PR: 3 ACK: 3 Remote PR: 6 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 70/9 packets 6/3 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [10.59.251.66,11165/10.60.128.8,1998]Started 00:02:03, last input 00:01:48, output 00:00:00Connects 5550427222205 <--> 5550427111100 from Serial4/0 PVC 5Window size input: 4, output: 4Packet size input: 128, output: 128PS: 7 PR: 2 ACK: 2 Remote PR: 3 RCNT: 0 RNR: noWindow is closedP/D state timeouts: 0 timer (secs): 0data bytes 20826/2 packets 191/2 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 1, State: D1, Interface: [10.59.251.66,11166/10.60.128.8,1998]Started 00:02:05, last input 00:01:54, output 00:02:01Connects 5550427222203 <--> 5550427111100 from Serial4/0 PVC 3Window size input: 4, output: 4Packet size input: 128, output: 128PS: 4 PR: 2 ACK: 2 Remote PR: 4 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 48/2 packets 4/2 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0The X.25 routing table for the 3662 router follows. A call placed to 5550427111100 will try serial interface 4/0 first. If serial interface 4/0 is in testing mode or is down, the Cisco IOS software examines serial interface 4/1 next. If serial interface 4/1 is up the call will be routed on serial interface 4/1.
Router# show x25 route# Match Substitute Route to1 dest 55504271111 Serial4/02 dest 55504271111 Serial4/1Configuring SCC0 and SCC1 on the Lucent 5ESS Telephone Switch Form
The Lucent 5ESS cpblx form follows with an example configuration of the SCC0 and SCC1 ports in bold text. (See the "Lucent cpblx Form Parameter Descriptions" section for descriptions of important fields in this form.) The configuration in the form was used with the testing described for the Cisco X.25 BAI feature. The switch technician configures the port setup from the switch console. Notice that field 65 has an X.25 packet size of 128. Fields 59 and 61 are the output and input buffer sizes, respectively. These fields must be three bytes larger than the packet size. In the example, the packet size is 128 and the buffer size is 131.
cpblx3Communications Protocol Option Block (Recent Change and Verify)1.option_name:cpblx3002.speed:9600 3.duplex:full 4.ds_type:201CPL5.carrier:s 6.line_access:direct 7.mode_op:b8.pdtime1:30 9.pdtime2:50 10.window:411.rexmit:7 12.dcedte:0 13.pcsd_stat:active14.config:duplex15.ldtel sid tlim telno1)______ ____ ______________2)______ ____ ______________3)______ ____ ______________4)______ ____ ______________19.security:n 20.link_id:021.feid_len:0 22.neid_len:0 23.password_len:024.feid.fend1)____ 4)____ 7)____ 10)____ 13)____2)____ 5)____ 8)____ 11)____ 14)____3)____ 6)____ 9)____ 12)____ 15)____35.neid.nend1)____ 4)____ 7)____ 10)____ 13)____2)____ 5)____ 8)____ 11)____ 14)____3)____ 6)____ 9)____ 12)____ 15)____46.pswrd.pwrd1)____ 4)____ 7)____ 10)____ 13)____2)____ 5)____ 8)____ 11)____ 14)____3)____ 6)____ 9)____ 12)____ 15)____57.perm_state:allow 58.outscrsiz:3300 59.outpktsiz:13160.inscrsiz:3300 61.inpktsiz:13162.hup:n 63.spckt:0 64.x3wsize:4 65.x3psize:12866.x3pvcn.ldinno1)_____ 6)5 11)_____ 16)_____ 21)_____ 26)_____ 31)_____2)_____ 7)6 12)_____ 17)_____ 22)_____ 27)_____ 32)_____3)2 8)7 13)_____ 18)_____ 23)_____ 28)_____4)3 9)_____ 14)_____ 19)_____ 24)_____ 29)_____5)4 10)_____ 15)_____ 20)_____ 25)_____ 30)_____81.time_ti:180 82.time_tj:60 83.time_tf:60 84.time_tl:6085.time_td:180 86.time_ts:180 87.time_ack:5Monitoring the Lucent DRM
The Lucent Distinctive Remote Module (DRM) is a small remote switch that is a slave to the Lucent 5ESS telephone switch. The DRM is used to service small office parks. The DRM is based on a Sun Microsystems workstation platform. The monitoring of the DRM is done over one physical connection, so there is no standby connection to be configured like there is for the Lucent 5ESS telephone switch. The connection from the Lucent DRM is EIA/TIA-449 (RS-449). The typical Lucent installation is done with an (EIA/TIA) RS-449-to-RS-232 convertor from Blackbox Corporation. Figure 27 shows an initial sample test network that was set up to test a Cisco STUN implementation and an XOT implementation.
Figure 26 Lucent DRM Preliminary Test Configurations
The actual network also was tested with an EIA/TIA-449 connection between the DRM and the router. The test setup is shown in Figure 27.
Figure 27 Lucent DRM Network Test Configurations
Configuring the Lucent DRM
Examples of the STUN configurations for the routers labeled 2600-A and 2600-B are listed in the following sections:
•
•
Troubleshooting a single connection is the same process as described in the "Verifying Links in the Cisco STUN OSS Connectivity Solution" section, which describes enabling two STUN links for the SCC0 and SCC1 connections to a Lucent 5ESS telephone switch.
Note
Lucent DRM-Side Configuration: Example
In the following configuration example, the STUN peer name is the IP address of the Ethernet port. The loopback address would also be another and possibly better choice.
stun peer-name 172.21.192.47stun protocol-group 103 basic!interface Ethernet0/1ip address 172.21.192.47 255.255.255.0!interface Serial1/0no ip addressencapsulation stunclockrate 9600stun group 103stun route all tcp 172.20.46.140Application Host Configuration: Example
In the following configuration example, the STUN peer name is the IP address of the Ethernet port:
stun peer-name 172.20.46.140stun protocol-group 103 basic!interface Ethernet0/0ip address 172.20.46.140 255.255.255.0!interface Serial1/6description CO1 to CO2no ip addressencapsulation stunno ignore-hw local-loopbackclockrate 9600stun group 103stun route all tcp 172.21.192.47Switch Monitoring Networks: IP and Cisco X.25 BAI and EOR Solutions
The obvious next step in migrating to the next generation operations network is to move applications to TCP/IP. The solutions described in earlier sections for monitoring the Lucent 5ESS switch used dual serial BX.25 ports or a serial X.25 port on the OSS. Service providers and vendors are working with Cisco to make the transition to TCP/IP on the OSS. The two OSS solutions that have migrated to TCP/IP for monitoring Class 5 switches are described in the following section:
•
•
The examples for the solutions described in this section focus on the Lucent 5ESS switch because of the unique properties of its SCC0 and SCC1 ports. This section also highlights solutions for the Telcordia NMA application and the TTI Telecom monitoring application.
Configuring a Cisco Router with X.25 BAI and EOR on the Telephone Switch Side of the Network
Previous sections described a solution using the backup active interface command (see the "Adding Cisco X.25 BAI to the Telco DCN" section). This section builds on that configuration. The NMA application is configured for an IP gateway. The router is configured with Cisco protocol translation and the X.25 BAI feature. The PVCs are configured as dynamic. Additionally, the configuration described in this section requires use of the End of Record (EOR) feature. A hexadecimal value of 19 is configured as the end of record. The NMA profile is configured to parse for the EOR character and to forward the data from an optical convergence switch (OCS) module to the application upon receipt of the EOR.
Figure 28 Cisco IP to X.25 BAI with EOR Solution for OSS Connectivity
To configure the X.25 BAI and EOR solution on a Cisco 3662 router in front of the Lucent 5ESS switch, see Figure 28 and perform the following steps. See the "Cisco Router with X.25 BAI and EOR on the Telephone Switch Side of the Network: Example" section for a configuration example. See the "Verifying Cisco X.25 BAI and EOR Configurations" section for a verification example.
Step 1
Router-3662# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 2
Router-3662(config)# x25 routingConfigure the Active Serial Interface
Step 3
Router-3662(config)# interface serial 4/0Step 4
Router-3662(config-if)# SCC0 Link to 5ESS (UnManaged)Step 5
Router-3662(config-if)# no ip addressStep 6
Router-3662(config-if)# encapsulation x25 dceStep 7
Router-3662(config-if)# backup active interface serial 4/1Step 8
Router-3662(config-if)# x25 version 1980Step 9
Router-3662(config-if)# x25 address 12345678Step 10
Router-3662(config-if)# x25 ltc 8Step 11
Router-3662(config-if)# x25 t10 30Step 12
Router-3662(config-if)# x25 t12 30Step 13
Router-3662(config-if)# x25 win 4Step 14
Router-3662(config-if)# x25 wout 4Step 15
Router-3662(config-if)# x25 threshold 1Step 16
Router-3662(config-if)# clockrate 9600Step 17
Router-3662(config-if)# lapb t1 5000Step 18
Router-3662(config-if)# lapb t2 200Step 19
Router-3662(config-if)# lapb t4 10Step 20
Router-3662(config-if)# lapb n2 7Step 21
Router-3662(config-if)# lapb k 4Step 22
Router-3662(config-if)# endConfigure the Backup Serial Interface
Step 23
Router-3662(config)# interface serial 4/1Step 24
Router-3662(config-if)# SCC1 Link (UnManaged)Step 25
Router-3662(config-if)# no ip addressStep 26
Router-3662(config-if)# encapsulation x25 dceStep 27
Router-3662(config-if)# x25 version 1980Step 28
Router-3662(config-if)# x25 address 12345678Step 29
Router-3662(config-if)# x25 ltc 8Step 30
Router-3662(config-if)# x25 t10 30Step 31
Router-3662(config-if)# x25 t12 30Step 32
Router-3662(config-if)# x25 win 4Step 33
Router-3662(config-if)# x25 wout 4Step 34
Router-3662(config-if)# x25 threshold 1Step 35
Router-3662(config-if)# clockrate 9600Step 36
Router-3662(config-if)# lapb t1 5000Step 37
Router-3662(config-if)# lapb t2 200Step 38
Router-3662(config-if)# lapb t4 10Step 39
Router-3662(config-if)# lapb n2 7Step 40
Router-3662(config-if)# lapb k 4Step 41
Router-3662(config-if)# endEnable Protocol Translation
Step 42
Router-3662(config-if)# translate tcp 10.60.150.128 port 1031 x25 12345678 pvc 1 dynamic max-users 1 EOR 0x19 insertRouter-3662(config-if)# translate tcp 10.60.150.128 port 1032 x25 12345678 pvc 2 dynamic max-users 1 EOR 0x19 insertRouter-3662(config-if)# translate tcp 10.60.150.128 port 1033 x25 12345678 pvc 3 dynamic max-users 1 EOR 0x19 insertRouter-3662(config-if)# translate tcp 10.60.150.128 port 1034 x25 12345678 pvc 4 dynamic max-users 1 EOR 0x19 insertRouter-3662(config-if)# translate tcp 10.60.150.128 port 1035 x25 12345678 pvc 5 dynamic max-users 1 EOR 0x19 insertRouter-3662(config-if)# translate tcp 10.60.150.128 port 1036 x25 12345678 pvc 6 dynamic max-users 1 EOR 0x19 insertRouter-3662(config-if)# translate tcp 10.60.150.128 port 1037 x25 12345678 pvc 7 dynamic max-users 1 EOR 0x19 insertEnable X.25 Routing
Step 43
Router-3662(config)# x25 route 12345678 interface Serial4/0Step 44
Router-3662(config)# x25 route 12345678 interface Serial4/1Step 45
Router-3662(config)# endStep 46
Router-3662# copy run startDestination filename [startup-config]?Building configuration...[OK]
Cisco Router with X.25 BAI and EOR on the Telephone Switch Side of the Network: Example
The following shows an example of the configuration once the steps listed in the "Configuring a Cisco Router with X.25 BAI and EOR on the Telephone Switch Side of the Network" section are completed. Remember that the configuration on the router must match the configuration on the Lucent 5ESS; therefore, the X.25 and LAPB parameters must match.
x25 routinginterface Serial4/0description SCC0 Link to 5ESS (UnManaged)no ip addressencapsulation x25 dcebackup active interface Serial4/1x25 version 1980x25 address 12345678x25 ltc 8x25 t10 30x25 t12 30x25 win 4x25 wout 4x25 threshold 1clockrate 9600lapb T1 5000lapb T2 200lapb T4 10lapb N2 7lapb k 4!interface Serial4/1description SCC1 link (UnManaged)no ip addressencapsulation x25 dcex25 version 1980x25 address 12345678x25 ltc 8x25 t10 30x25 t12 30x25 win 4x25 wout 4x25 threshold 1clockrate 9600lapb T1 5000lapb T2 200lapb T4 10lapb N2 7lapb k 4x25 route 12345678 interface Serial4/0x25 route 12345678 interface Serial4/1!translate tcp 10.60.150.128 port 1031 x25 12345678 pvc 1 dynamic max-users 1 EOR 0x19 inserttranslate tcp 10.60.150.128 port 1032 x25 12345678 pvc 2 dynamic max-users 1 EOR 0x19 inserttranslate tcp 10.60.150.128 port 1033 x25 12345678 pvc 3 dynamic max-users 1 EOR 0x19 inserttranslate tcp 10.60.150.128 port 1034 x25 12345678 pvc 4 dynamic max-users 1 EOR 0x19 inserttranslate tcp 10.60.150.128 port 1035 x25 12345678 pvc 5 dynamic max-users 1 EOR 0x19 inserttranslate tcp 10.60.150.128 port 1036 x25 12345678 pvc 6 dynamic max-users 1 EOR 0x19 inserttranslate tcp 10.60.150.128 port 1037 x25 12345678 pvc 7 dynamic max-users 1 EOR 0x19 insertVerifying Cisco X.25 BAI and EOR Configurations
The following sections contain useful information for verifying the Cisco X.25 BAI and EOR configurations:
•
•
•
Following is a list of additional EXEC commands that can be used to troubleshoot the configurations:
•
•
•
•
•
•
•
•
•
Verifying the Active Interface with the show interface Command
The show interface command can be used to determine which router interface is active to the Lucent 5ESS switch and which interface is in the Standby mode. The active interface will be listed as up and line protocol as up. The following is sample output from the show interface serial 4/0 command:
Router-3662# show interface serial 4/0Serial4/0 is up, line protocol is upHardware is CD2430 in sync modeDescription: SCC0 Link to 5ESS (UnManaged)Backup interface Serial4/1, failure delay 0 sec, secondary disable delay 0 sec,kickin load not set, kickout load not setMTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation X25, loopback not setX.25 DCE, address 12345678, state R1, modulo 8, timer 0Defaults: idle VC timeout 0cisco encapsulationinput/output window sizes 4/4, packet sizes 128/128Timers: T10 30, T11 180, T12 30, T13 60Channels: Incoming-only none, Two-way 8-1024, Outgoing-only noneRESTARTs 25/0 CALLs 0+0/0+0/0+0 DIAGs 2/0LAPB DCE, state CONNECT, modulo 8, k 4, N1 12056, N2 7T1 5000, T2 200, interface outage (partial T3) 0, T4 10VS 0, VR 3, tx NR 3, Remote VR 0, Retransmissions 0Queues: U/S frames 0, I frames 0, unack. 0, reTx 0IFRAMEs 4042/4218 RNRs 0/0 REJs 0/0 SABM/Es 11/23 FRMRs 0/0 DISCs 0/2Last input 00:00:00, output 00:00:00, output hang neverLast clearing of "show interface" counters 01:21:32Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue :3/40 (size/max)5 minute input rate 1000 bits/sec, 4 packets/sec5 minute output rate 0 bits/sec, 2 packets/sec8553 packets input, 383358 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort4497 packets output, 21498 bytes, 0 underruns0 output errors, 0 collisions, 3 interface resets0 output buffer failures, 0 output buffers swapped out4 carrier transitionsDCD=up DSR=up DTR=up RTS=up CTS=upThe interface supporting the SCC channel in Standby mode will be listed as "testing." In the following example, serial interface 4/1 is connected to SCC1, which is in Standby mode. The report from the show interface serial 4/1 command shows the interface is in testing mode (highlighted for purpose of example in bold text), instead of up or down. The line protocol is down.
Router-3662# show interface serial 4/1Serial4/1 is testing, line protocol is downHardware is CD2430 in sync modeDescription: SCC1 link (UnManaged)Backup interface Serial4/0, failure delay 0 sec, secondary disable delay 0 sec,kickin load not set, kickout load not setMTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation X25, loopback not setX.25 DCE, address 12345678, state R/Inactive, modulo 8, timer 0Defaults: idle VC timeout 0cisco encapsulationinput/output window sizes 4/4, packet sizes 128/128Timers: T10 30, T11 180, T12 30, T13 60Channels: Incoming-only none, Two-way 8-1024, Outgoing-only noneRESTARTs 23/0 CALLs 0+0/0+0/0+0 DIAGs 0/0LAPB DCE, state DISCONNECT, modulo 8, k 4, N1 12056, N2 7T1 5000, T2 200, interface outage (partial T3) 0, T4 10VS 0, VR 0, tx NR 0, Remote VR 0, Retransmissions 0Queues: U/S frames 0, I frames 0, unack. 0, reTx 0IFRAMEs 20/0 RNRs 0/0 REJs 0/0 SABM/Es 0/23 FRMRs 0/0 DISCs 0/0Last input 00:00:00, output 00:00:23, output hang neverLast clearing of "show interface" counters 01:21:41Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue :0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec57 packets input, 114 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort60 packets output, 220 bytes, 0 underruns0 output errors, 0 collisions, 3 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsDCD=up DSR=up DTR=up RTS=up CTS=upVerifying the Interface Type and Clock Rate with the show controllers Command
Another useful command to verify the interface type and the interface clock rate is the show controllers command. Sample output from the show controllers serial 4/0 command follows. The third line of the output (in bold text) shows that the cable type on the interface is RS-232 DCE and the clock rate is 9600 baud.
Router-3662# show controllers serial 4/0CD2430 Slot 4, Port 0, Controller 0, Channel 0, Revision 18Channel mode is synchronous serialidb 0x61B1445C, buffer size 1524, RS-232 DCE cable, clockrate 9600Global registersrpilr 0x2, rir 0x0, risr 0x0, rfoc 0x0, rdr 0x0tpilr 0x1, tir 0x0, tisr 0x68, tftc 0x0, tdr 0x90mpilr 0x3, mir 0x0, misr 0x60bercnt 0xFF, stk 0x0Per-channel registers for channel 0Option registers0x02 0x00 0x42 0x67 0x60 0x00 0x00Command and status registerscmr 0xC0, ccr 0x00, csr 0xCC, msvr-rts 0xF1, msvr-dtr 0xF1Clock option registersrcor 0x86, rbpr 0x01, tcor 0xC0, tbpr 0x77Interrupt registersier 0x89, livr 0x00, licr 0x00DMA buffer status 0x22DMA receive registersarbaddr 0xFA370E4, arbcnt 1548, arbsts 0x1brbaddr 0xFA36A64, brbcnt 1548, brbsts 0x1rcbaddr 0xFA363E6DMA transmit registersatbaddr 0xF8014D6, atbcnt 5, atbsts 0x62btbaddr 0xFCADDF6, btbcnt 5, btbsts 0x62tcbaddr 0xFCADDFBSpecial character registersschr1 0x00, schr2 0x00, schr3 0x00, schr4 0x00scrl 0x0, scrh 0x0, lnxt 0xF1Driver context informationContext structure 0x61B16C78, Register table 0x3E800400Serial Interface Control 5:1 Register (0x3E800802) is 0x80Adaptor Flags 0x0Serial Modem Control Register (0x3E800804) is 0x1DReceive static buffer 0x61A520B0Receive particle buffers 0x61B17240, 0x61B17200Transmit DMA buffers 0x0, 0x0, 0x0, 0x0Transmit packet with particles 0x0, first word is 0x0Interrupt rates (per second) transmit 1, receive 3, modem 0True fast-switched packets 0Semi fast-switched packets 0Transmitter hang count 0Residual indication count 0Bus error count 0Aborted short frames count 0CRC short frames count 0Error countersCTS deassertion failures 0Nested interrupt errors transmit 0, receive 0, modem 0Verifying the Active TCP Connection with the show tcp brief Command
To verify the TCP connections from the NMA, use the show tcp brief command. The following is sample output from this command. The output shows TCP connections to IP address 10.6.15.128, which is the virtual IP address for protocol translation. There are seven TCP sessions, which translate into the seven PVCs. The seven TCP port numbers are 1031, 1032, 1033, 1034, 1035, 1036, and 1037.
Router# show tcp briefTCB Local Address Foreign Address (state)6220F464 10.6.15.128.1037 nma.nn.4510 ESTAB62217D44 10.6.15.128.1033 nma.nn.4508 ESTAB6220AE70 10.6.15.128.1035 nma.nn.4505 ESTAB622101BC 10.6.15.128.1034 nma.nn.4504 ESTAB6221731C 10.6.15.128.1032 nma.nn.4507 ESTAB621FE0AC 10.6.15.128.1036 nma.nn.4503 ESTAB621F1EF8 10.6.15.128.1031 nma.nn.4512 ESTAB
Note
interface FastEthernet0/0ip address 10.6.15.1 255.255.255.0speed 100full-duplexTTI Telecom Monitoring Application Cisco X.25 BAI Solution
The TTI Telecom monitoring application has an IP interface that can be used with a Cisco router to monitor the BX.25 ports SCC0 and SCC1 on a Lucent 5ESS switch. The application is shown in Figure 29. The router configuration for converting between TCP/IP and BX.25 utilizes Cisco protocol translation. The configuration is very similar to the configuration used in the last section for the Telcordia NMA application. The configuration requires two serial interfaces that are paired with the backup active interface command. The PVCs in the protocol translation statements must be set up as dynamic. The TTI application does not use the End of Record (EOR) feature. There must be an X.25 route statement that points to each serial interface. Use the commands in the "Verifying Cisco X.25 BAI and EOR Configurations" section to verify and troubleshoot this configuration.
Figure 29 Cisco IP to BX.25 BAI Solution for OSS Connectivity
The following is a sample configuration for the TTI Telecom monitoring application. Remember that the configuration on the router must match the configuration on the Lucent 5ESS; therefore, the X.25 and LAPB parameters must match.
x25 routinginterface Serial4/0description SCC0 Link to 5ESS (UnManaged)no ip addressencapsulation x25 dcebackup active interface Serial4/1x25 version 1980x25 address 12345678x25 ltc 8x25 t10 30x25 t12 30x25 win 4x25 wout 4x25 threshold 1clockrate 9600lapb T1 5000lapb T2 200lapb T4 10lapb N2 7lapb k 4!interface Serial4/1description SCC1 link (UnManaged)no ip addressencapsulation x25 dcex25 version 1980x25 address 12345678x25 ltc 8x25 t10 30x25 t12 30x25 win 4x25 wout 4x25 threshold 1clockrate 9600lapb T1 5000lapb T2 200lapb T4 10lapb N2 7lapb k 4x25 route 12345678 interface Serial4/0x25 route 12345678 interface Serial4/1!translate tcp 10.60.150.128 port 1031 stream x25 12345678 pvc 1 dynamic max-users 1translate tcp 10.60.150.128 port 1032 stream x25 12345678 pvc 2 dynamic max-users 1translate tcp 10.60.150.128 port 1033 stream x25 12345678 pvc 3 dynamic max-users 1translate tcp 10.60.150.128 port 1034 x25 12345678 pvc 4 dynamic max-users 1translate tcp 10.60.150.128 port 1035 x25 12345678 pvc 5 dynamic max-users 1translate tcp 10.60.150.128 port 1036 x25 12345678 pvc 6 dynamic max-users 1translate tcp 10.60.150.128 port 1037 x25 12345678 pvc 7 dynamic max-users 1Provisioning Networks: Cisco X.25 RBP Solution
This section describes Cisco telco solutions for telephone switch provisioning networks like the one highlighted in Figure 30.
Figure 30 Legacy Switch Provisioning Network
The Cisco X.25 RBP solution is described in the following sections:
•
•
•
•
•
•
•
•
Cisco X.25 RBP Solution Overview
Telco provisioning applications automate the assignment of Class 5 telephone switch resources for new voice services and connections.
Both Figure 30 and Figure 31 show a Recent Change (RC) port and Echo Back (EB) port on the Lucent 5ESS telephone switch connected over a Datakit network. The goal is to replace the Lucent Datakit network with a TCP/IP network, and one method available is XOT. However, a better method would be for the host to migrate to TCP/IP and to implement the Cisco X.25 RBP feature. Later in this section, CONNECTVU-ATP and the ADC Service Activation examples will focus on the Cisco X.25 RBP solution for migrating to TCP/IP. Figure 31 also shows the Cisco X.25 RBP implementation that was designed to replace the network seen in Figure 30.
The Cisco X.25 RBP feature enables hosts on a DCN using TCP/IP-based protocols to exchange data with devices that use the X.25 protocol, and to retain the logical record boundaries indicated, by use of the X.25 "more data" bit (M-bit).
The Cisco DCN solution provides a flexible design for TCP/IP-to-X.25 protocol mediation or TCP/IP-to-asynchronous conversion. The challenge is to preserve the M-bit of the X.25 session across the TCP/IP session, and the Cisco X.25 RBP feature does exactly that. The Cisco X.25 RBP allows a long list of changes to be submitted at one time to the Lucent 5ESS switch. As Figure 31 shows, a TCP/IP session is initiated in the CONNECTVU-APX application to the access router in the central office. The central office router terminates the TCP session and initiates an X.25 session. The CONNECTVU-APX application data is transferred between the TCP/IP session and the X.25 session by the access router in the central office. Refer to the X.25 Record Boundary Preservation for Data Communications Networks feature document for more information about the Cisco X.25 RBP feature. The solution is open to any vendor.
Before the introduction of the Cisco X.25 RBP feature, Cisco IOS software provided two methods for enabling the exchange of data between X.25 hosts and hosts using TCP/IP-based protocols: protocol translation and XOT. Protocol translation supports a variety of configurations, including translation of a data stream between an X.25 circuit that is using X.29 and a TCP session. The X.29 protocol is an integral part of protocol translation. One aspect of X.29 is that it is asymmetric and allows the packaging of data into X.25 packets to be controlled in one direction only. The TCP protocol is stream-oriented, rather than packet-oriented. TCP does not attach significance to TCP datagram boundaries, and those boundaries can change when a datagram is retransmitted. This inability to preserve boundaries makes protocol translation appropriate only for configurations in which the X.25 packet boundary is not significant.
XOT allows X.25 packets to be forwarded over a TCP session. This functionality allows full control over the X.25 circuit, but the host terminating the TCP session must implement the XOT protocol and the X.25 packet layer protocol.
The Cisco X.25 RBP feature offers a solution positioned between these two options: It allows logical message boundaries to be indicated without requiring the TCP host to be aware of X.25 protocol details.
The TCP protocol does not attach significance to datagram boundaries, so a protocol must be layered over a TCP session to convey record boundary information. The Cisco X.25 RBP feature uses a 6-byte record header that specifies the amount of data following and indicates whether that data should be considered the final part of a logical record.
Adding Cisco X.25 RBP to the Telco DCN Provisioning Connection
This section uses the Lucent CONNECTVU-ATP application to show how to add the Cisco X.25 RBP feature to the telco DCN.
The Lucent CONNECTVU-ATP solution shown in Figure 31 is designed to manage and provision telephony switch resources.
Figure 31 CONNECTVU-ATP Connected Using Cisco X.25 RBP
The Cisco telco DCN solutions are designed to provide all communications needs between the CONNECTVU-APX application and the Lucent 5ESS. All Cisco telco DCN solutions hardware is fully Network Equipment Building Systems (NEBS) 3-compliant. The Cisco telco DCN solution supports the CONNECTVU-APX application by providing protocol conversion and mediation for both the EB and RC connections to the Lucent 5ESS telephone switch.
Configuring the CONNECTVU-ATP Application
The CONNETVU-ATP application must be configured for the TCP/IP and the Record Boundary Preservation (RBP) header. Sample screen configurations follow, with user input in bold text. The RBP header is configured by setting the RC LINK INTF field and the EB LINK INTF to IP-X25-DY. The IP address of the router connected to the Echo Back and Recent Change ports is 10.181.254.1 and is listed in the address fields.
CONNECTVU-ATP Switch Administration
SWITCH CLLI: LAB00 SWITCH NAME: LAB00GENERIC: 5E14 RC SERV: LAB00RC EB SERV: LABD00EBDMS LOGIN: DMS PASSWORD: ASM LOGIN:ASM MACHINE NAME (D&L):INHIBIT RETRU INTVL: 10 OFFICE ID: CVUNOVERIFY MAX RC VCS: 4RC LINK INTF: IP-X25-DY EB LINK INTF: IP-X25-DYRC DIALSTRING/IP ADDRESS: 10.181.254.1EB DIALSTRING/IP ADDRESS: 10.181.254.1Attributes for Recent Change Links TCP/IP Connectivity
LINK ID 1 LINK ID 2 LINK ID 3 LINK ID 4LOGIN:PASSWORD:SECURITYCLASS:TCP/IPPORT: 20002 ? ? ?Attributes for Echo Back Links TCP/IP Connectivity
LINK ID 1 LINK ID 2 LINK ID 3 LINK ID 4LOGIN:PASSWORD:SECURITYCLASS:TCP/IPPORT: 20001 ? ? ?Configuring the Lucent 5ESS Echo Back Port
This section describes configuration of the EB port on the Lucent 5ESS telephone switch. The parameters required for the CONNECTVU-APX application are listed in the following configuration examples, with user input in bold text. See the "Configuring the Echo Back Port on the Cisco Router" section for the procedure to configure a Cisco router for the EB port.
The EB port X.25 administration table is as follows:
Interface Type: RS232 / RS449X121 local address: 5553501136_____________Baud Rate: 4800______Window Size: 128______Packet Size: 2______High two-way virtual circuit number: 3_____T10: 60____(Default) T11: 180___(Default)T12: 60____(Default) T13: 60____(Default)T20: 180___(Default) T21: 200___(Default)T22: 180___(Default) T23: 180___(Default)The EB port LAPB administration table is as follows:
N1 Frame Size: 4136_______Window Size: 7 (Default)Interface Mode: DCE / DTETimers:N2: 20___ (Default)T1: 3000_ (Default)T2: 400__T4: 25___Configuring the Echo Back Port on the Cisco Router
To configure the EB port on a Cisco router, see Figure 31 and perform the following steps. See the "Echo Back Port Configuration: Example" section for a configuration example.
Step 1
Router-C# show versionStep 2
Router-C# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 3
Router-C(config)# interface serial 1/0Step 4
Router-C(config-if)# shutdownStep 5
Router-C(config-if)# description EchoBackStep 6
Router-C(config-if)# encapsulation x25Step 7
Router-C(config-if)# x25 version 1980Step 8
Router-C(config-if)# x25 htc 3Step 9
Router-C(config-if)# x25 threshold 1Step 10
Router-C(config-if)# x25 map rbp 5553501136 cud 0xC1 local port 20001Step 11
Router-C(config-if)# clockrate 9600Step 12
Router-C(config-if)# lapb t2 400Step 13
Router-C(config-if)# lapb t4 25Step 14
Router-C(config-if)# lapb n1 4136Step 15
Router-C(config-if)# no shutdownStep 16
Router-C(config-if)# endRouter-C(config)# endStep 17
Router-C# copy run start (saves the configuration to non-volatile memory)Destination filename [startup-config]?Building configuration...[OK]
Echo Back Port Configuration: Example
The following example shows the configuration of the EB port:
interface Serial1/0description EchoBackno ip addressencapsulation x25no ip route-cacheno ip mroute-cachex25 version 1980x25 htc 3x25 threshold 1x25 map rbp 5553501136 cud 0xC1 local port 20001clockrate 9600lapb T2 400lapb T4 25lapb N1 4136Configuring the Lucent 5ESS Recent Change Port
This section describes configuration of the RC port on the Lucent 5ESS telephone switch. The parameters required for the CONNECTVU-APX application are listed in the following configuration examples, with user input in bold text. See the "Configuring the Recent Change Port on the Cisco Router" section for the procedure to configure a Cisco router for the RC port.
The RC port X.25 administration table is as follows:
X.25 Connection Parameters for the Router: Recent Change (Port Number: ____)Interface Type: RS232 / RS449X121 local address: 5553501135_____________Baud Rate: 4800______Window Size: 128______Packet Size: 2______High two-way virtual circuit number: 4_____T10: 60 ___(Default) T11: 180___(Default)T12: 60____(Default) T13: 60____(Default)T20: 180___(Default) T21: 200___(Default)T22: 180___(Default) T23: 180___(Default)The RC port LAPB administration table is as follows:
N1 Frame Size: 4136_______Window Size: 7_(Default)Interface Mode: DCE / DTETimers:N2: 20___ (Default)T1: 3000_ (Default)T2: 400__T4: 25___Configuring the Recent Change Port on the Cisco Router
To configure the RC port on a Cisco router, see Figure 31 and perform the following steps. See the "Recent Change Port Configuration: Example" section for a configuration example. See the "Debugging the Echo Back and Recent Change Ports" section for a debugging examples.
Step 1
Router-C# show versionStep 2
Router-C# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 3
Router-C(config-if)# interface serial 1/1Step 4
Router-C(config-if)# shutdownStep 5
Router-C(config-if)# description RecentChangeStep 6
Router-C(config-if)# encapsulation x25 dteStep 7
Router-C(config-if)# x25 version 1980Step 8
Router-C(config-if)# x25 htc 4Step 9
Router-C(config-if)# x25 threshold 1Step 10
Router-C(config-if)# x25 map rbp 5553501135 cud 0xC1 local port 20002Step 11
Router-C(config-if)# clockrate 9600Step 12
Router-C(config-if)# lapb t2 400Step 13
Router-C(config-if)# lapb t4 25Step 14
Router-C(config-if)# lapb n1 4136Step 15
Router-C(config-if)# no shutdownStep 16
Router-C(config-if)# endRouter-C(config)# endStep 17
Router-C# copy run startDestination filename [startup-config]?Building configuration...[OK]
Recent Change Port Configuration: Example
The following example shows the configuration of the RC port:
interface Serial1/1description RecentChangeno ip addressencapsulation x25no ip route-cacheno ip mroute-cachex25 version 1980x25 htc 4x25 threshold 1x25 map rbp 5553501135 cud 0xC1 local port 20002clockrate 9600lapb T2 400lapb T4 25lapb N1 4136Debugging the Echo Back and Recent Change Ports
The following procedure provides helpful hints on debugging problems with EB and RC port connectivity:
Step 1
Router-C# show controllers serial 1/2CD2430 Slot 1, Port 2, Controller 0, Channel 2, Revision 16Channel mode is synchronous serialidb 0x819D6014, buffer size 1524, RS-232 DCE cable, clockrate 9600Global registersrpilr 0x2, rir 0x0, risr 0x0, rfoc 0x0, rdr 0x0tpilr 0x1, tir 0x0, tisr 0x0, tftc 0x0, tdr 0x0mpilr 0x3, mir 0x0, misr 0x0bercnt 0xFF, stk 0x0Per-channel registers for channel 2Option registers0x02 0x00 0x42 0x67 0x60 0x00 0x00Command and status registerscmr 0xC0, ccr 0x00, csr 0x04, msvr-rts 0x10, msvr-dtr 0x10Clock option registersrcor 0x86, rbpr 0x01, tcor 0xC0, tbpr 0x77Interrupt registersier 0x00, livr 0x08, licr 0x08DMA buffer status 0x00DMA receive registersarbaddr 0x35A8D04, arbcnt 1548, arbsts 0x1brbaddr 0x35A8684, brbcnt 1548, brbsts 0x1rcbaddr 0x0DMA transmit registersatbaddr 0x0, atbcnt 0, atbsts 0x0btbaddr 0x0, btbcnt 0, btbsts 0x0tcbaddr 0x0Special character registersschr1 0x00, schr2 0x00, schr3 0x00, schr4 0x00scrl 0x0, scrh 0x0, lnxt 0x0Driver context informationContext structure 0x819D8888, Register table 0x40800400Serial Interface Control 5:1 Register (0x4080080A) is 0x80Adaptor Flags 0x0Serial Modem Control Register (0x4080080C) is 0x14Receive static buffer 0x81919A04Receive particle buffers 0x819D9100, 0x819D90C0Transmit DMA buffers 0x0, 0x0, 0x0, 0x0Transmit packet with particles 0x0, first word is 0x0Interrupt rates (per second) transmit 0, receive 0, modem 0True fast-switched packets 0Semi fast-switched packets 0Transmitter hang count 0Residual indication count 0Bus error count 0Aborted short frames count 0CRC short frames count 0Error countersCTS deassertion failures 0Nested interrupt errors transmit 0, receive 0, modem 0Step 2
Router-C# show interface serial 1/1Serial1/1 is up, line protocol is downHardware is CD2430 in sync modeDescription: RecentChangeMTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation X25, loopback not setX.25 DCE, address 5555275555, state R/Inactive, modulo 8, timer 0Defaults: idle VC timeout 0cisco encapsulationinput/output window sizes 2/2, packet sizes 128/128Timers: T10 60, T11 180, T12 60, T13 60Channels: Incoming-only none, Two-way 1-1024, Outgoing-only noneRESTARTs 0/0 CALLs 0+0/0+0/0+0 DIAGs 0/0LAPB DCE, state SABMSENT, modulo 8, k 7, N1 12056, N2 20T1 3000, T2 0, interface outage (partial T3) 0, T4 0VS 0, VR 0, tx NR 0, Remote VR 0, Retransmissions 10Queues: U/S frames 0, I frames 0, unack. 0, reTx 0IFRAMEs 0/0 RNRs 0/0 REJs 0/0 SABM/Es 11/0 FRMRs 0/0 DISCs 0/0Last input 00:00:02, output 00:00:00, output hang neverLast clearing of "show interface" counters 00:17:12Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue :0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec14 packets input, 31 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort13 packets output, 26 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out3 carrier transitionsDCD=up DSR=up DTR=up RTS=up CTS=upStep 3
Router-C# terminal monitorRouter-C# debug lapbLAPB link debugging is onRouter-C#00:07:53: Serial1/1: LAPB T1 SABMSENT 473 1700:07:53: Serial1/1: LAPB O SABMSENT (2) SABM P00:07:56: Serial1/1: LAPB T1 SABMSENT 476 1800:07:56: Serial1/1: LAPB O SABMSENT (2) SABM P00:07:59: Serial1/1: LAPB T1 SABMSENT 479 1900:07:59: Serial1/1: LAPB O SABMSENT (2) SABM P00:08:02: Serial1/1: LAPB T1 SABMSENT 482 000:08:02: Serial1/1: LAPB O SABMSENT (2) SABM P00:08:05: Serial1/1: LAPB T1 SABMSENT 485 100:08:05: Serial1/1: LAPB O SABMSENT (2) SABM P00:08:08: Serial1/1: LAPB T1 SABMSENT 488 200:08:08: Serial1/1: LAPB O SABMSENT (2) SABM P00:08:11: Serial1/1: LAPB T1 SABMSENT 491 300:08:11: Serial1/1: LAPB O SABMSENT (2) SABM P00:08:14: Serial1/1: LAPB T1 SABMSENT 494 400:08:14: Serial1/1: LAPB O SABMSENT (2) SABM P00:08:17: Serial1/1: LAPB T1 SABMSENT 497 500:08:17: Serial1/1: LAPB O SABMSENT (2) SABM P00:08:20: Serial1/1: LAPB T1 SABMSENT 500 6Step 4
Router-C(config)# interface serial 1/1Router-C(config-if)# shutdown00:10:40: %LINK-5-CHANGED: Interface Serial1/1, changed state to administrativeRouter-C(config-if)# clockrate 9600Router-C(config-if)# no shutdownRouter-C(config-if)# end00:11:25: %LINK-3-UPDOWN: Interface Serial1/1, changed state to up00:11:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/1, changed stp00:11:27: %SYS-5-CONFIG_I: Configured from console by consoleStep 5
00:12:38: Serial1/1: LAPB I CONNECT (2) RR P 100:12:38: Serial1/1: LAPB O CONNECT (2) RR F 100:13:03: Serial1/1: LAPB I CONNECT (2) RR P 100:13:03: Serial1/1: LAPB O CONNECT (2) RR F 100:13:28: Serial1/1: LAPB I CONNECT (2) RR P 100:13:28: Serial1/1: LAPB O CONNECT (2) RR F 100:13:53: Serial1/1: LAPB I CONNECT (2) RR P 100:13:53: Serial1/1: LAPB O CONNECT (2) RR F 100:14:18: Serial1/1: LAPB I CONNECT (2) RR P 100:14:18: Serial1/1: LAPB O CONNECT (2) RR F 100:14:43: Serial1/1: LAPB I CONNECT (2) RR P 100:14:43: Serial1/1: LAPB O CONNECT (2) RR F 1Step 6
Router-C# show interface serial 1/1Serial1/1 is up, line protocol is upHardware is CD2430 in sync modeDescription: RecentChangeMTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation X25, loopback not setX.25 DTE, address <none>, state R1, modulo 8, timer 0Defaults: idle VC timeout 0cisco encapsulationinput/output window sizes 2/2, packet sizes 128/128Timers: T20 180, T21 200, T22 180, T23 180Channels: Incoming-only none, Two-way 1-4, Outgoing-only noneRESTARTs 4/0 CALLs 0+10/0+0/0+0 DIAGs 0/0LAPB DTE, state CONNECT, modulo 8, k 7, N1 12056, N2 20T1 3000, T2 0, interface outage (partial T3) 0, T4 0VS 1, VR 1, tx NR 1, Remote VR 1, Retransmissions 0Queues: U/S frames 0, I frames 0, unack. 0, reTx 0IFRAMEs 38/4 RNRs 0/0 REJs 0/0 SABM/Es 74/3 FRMRs 0/0 DISCs 0/1Last input 00:00:21, output 00:00:21, output hang 02:36:08Last clearing of "show interface" counters 02:33:07Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue :0/40 (size/max)Step 7
Caution
Router-C# debug x25 ?all Show all X.25 traffic (default)annexg X.25 over Frame-Relay (Annex-G) Eventsaodi Always On/Direct ISDN (PPP over X.25) eventscmns Show only CMNS trafficevents Show X.25 traffic without normal Data and RR packetsinterface Show X.25 or CMNS traffic on one interfaceonly Show only X.25 trafficvc X.25 traffic across a specific virtual circuitxot Show only XOT (X.25-Over-TCP) traffic<cr>Router-C# debug x25 interface serial 1/2X.25 packet debugging is onX.25 debug output restricted to interface Serial1/2Router-C#Router-C# debug x25 eventsX.25 special event debugging is onIn the following output, the LAPB layer is up. An X.25 RBP call comes onto serial interface 1/1. The call is destined for port 20001. In the example, an RPB statement had not been set up for TCP port 20001 (see bold text).
Router-C# debug x25 allX.25 packet debugging is on00:19:18: Serial1/1: LAPB O CONNECT (2) RR F 100:19:43: Serial1/1: LAPB I CONNECT (2) RR P 100:19:43: Serial1/1: LAPB O CONNECT (2) RR F 100:19:55: X25 RBP: Incoming connection for port 20001 from 172.22.45.49 port 63900:19:55: X25 RBP: no usable map found for port 20001Step 8
00:20:33: Serial1/1: LAPB O CONNECT (2) RR F 100:20:58: Serial1/1: LAPB I CONNECT (2) RR P 100:20:58: Serial1/1: LAPB O CONNECT (2) RR F 100:21:15: X25 RBP: Incoming connection for port 20002 from 172.22.45.49 port 63600:21:15: x25rbp_place_call: calling (10) 5557777777 from (0)00:21:15: Serial1/1: X.25 O R1 Call (10) 8 lci 102400:21:15: From (0): To (10): 5557777777Step 9
Router-C(config-if)# x25 htc 4Monitor the outgoing call to the switch again. You can see the call go out on logical channel 4. The call is cleared by the switch. You can also can see the Clear Request sent to the switch. The router confirms the clear. Notice the I on the debug output. The I stands for incoming packet to the interface. The O stands for the packet being sent out the interface to the Lucent 5ESS telephone switch.
02:39:27: Serial1/1: LAPB I CONNECT (2) RR P 102:39:27: Serial1/1: LAPB O CONNECT (2) RR F 102:39:32: X25 RBP: Incoming connection for port 20002 from 172.22.45.49 port 60202:39:32: x25rbp_place_call: calling (10) 5553501135 from (0)02:39:32: Serial1/1: X.25 O R1 Call (13) 8 lci 402:39:32: From (0): To (10): 555350113502:39:32: Facilities: (0)02:39:32: Call User Data (3): 0x313933 (unknown)02:39:32: Serial1/1: LAPB O CONNECT (15) IFRAME 1 102:39:33: Serial1/1: LAPB I CONNECT (2) RR (R) 202:39:33: Serial1/1: LAPB I CONNECT (7) IFRAME 1 202:39:33: Serial1/1: X.25 I R1 Clear (5) 8 lci 402:39:33: Cause 0, Diag 0 (DTE originated/No additional information)02:39:33: x25rbp_clear: context 8196B5AC, state 2, packet 81A9B264, reason 8127)02:39:33: X25 RBP: X.25 circuit cleared02:39:33: Serial1/1: X.25 O R1 Clear Confirm (3) 8 lci 402:39:33: Serial1/1: LAPB O CONNECT (5) IFRAME 2 2Step 10
Router-C(config)# interface serial 1/1Router-C(config-if)# no x25 map rbp 5553501135 local port 20002Router-C(config-if)# x25 map rbp 5553501135 cud 193 local port 20002Router-C(config-if)# no shutdown02:37:47: %LINK-3-UPDOWN: Interface Serial1/1, changed state to up02:37:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/1, changed stpinterface Serial1/1description RecentChangeno ip addressencapsulation x25no ip route-cacheno ip mroute-cachex25 htc 4x25 map rbp 5553501135 cud 193 local port 20002clockrate 9600The call was rejected because of an unknown CUD:
02:39:32: X25 RBP: Incoming connection for port 20002 from 172.22.45.49 port 60202:39:32: x25rbp_place_call: calling (10) 5553501135 from (0)02:39:32: Serial1/1: X.25 O R1 Call (13) 8 lci 402:39:32: From (0): To (10): 555350113502:39:32: Facilities: (0)02:39:32: Call User Data (3): 0x313933 (unknown)02:39:32: Serial1/1: LAPB O CONNECT (15) IFRAME 1 102:39:33: Serial1/1: LAPB I CONNECT (2) RR (R) 202:39:33: Serial1/1: LAPB I CONNECT (7) IFRAME 1 202:39:33: Serial1/1: X.25 I R1 Clear (5) 8 lci 402:39:33: Cause 0, Diag 0 (DTE originated/No additional information)02:39:33: x25rbp_clear: context 8196B5AC, state 2, packet 81A9B264, reason 8127)02:39:33: X25 RBP: X.25 circuit cleared02:39:33: Serial1/1: X.25 O R1 Clear Confirm (3) 8 lci 4Step 11
Router-C(config)# interface serial 1/1Router-C(config-if)# shutdownRouter-C(config-if)# no shutdown02:44:38: %LINK-5-CHANGED: Interface Serial1/1, changed state to administrativen02:44:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/1, changed st2%Map not foundRouter-C(config-if)# no x25 map rbp 5553501135 cud c1 local port 20002Router-C(config-if)# x25 map rbp 5553501135 cud 0xc1 local port 20002Router-C(config-if)# no shutdownRouter-C(config-if)# endThe following report indicates this fix worked. The call was not rejected due to the CUD. You see the router give an error message that the Cisco IOS software does not recognize a CUD of 0XC1.
02:46:58: Serial1/1: LAPB I CONNECT (2) RR P 102:46:58: Serial1/1: LAPB O CONNECT (2) RR F 102:47:18: X25 RBP: Incoming connection for port 20002 from 172.22.45.49 port 60602:47:18: x25rbp_place_call: calling (10) 5553501135 from (0)02:47:18: Serial1/1: X.25 O R1 Call (11) 8 lci 402:47:18: From (0): To (10): 555350113502:47:18: Facilities: (0)02:47:18: Call User Data (1): 0xC1 (unknown)02:47:18: Serial1/1: LAPB O CONNECT (13) IFRAME 1 102:47:18: Serial1/1: LAPB I CONNECT (2) RR (R) 202:47:18: Serial1/1: LAPB I CONNECT (7) IFRAME 1 202:47:18: Serial1/1: X.25 I R1 Clear (5) 8 lci 402:47:18: Cause 0, Diag 0 (DTE originated/No additional information)02:47:18: x25rbp_clear: context 8196B5AC, state 2, packet 81A9B264, reason 8127)02:47:18: X25 RBP: X.25 circuit cleared02:47:18: Serial1/1: X.25 O R1 Clear Confirm (3) 8 lci 4The following debug report shows all four channels connected on the RC port. LCI 4 will be brought up first. The router places the call on the highest available channel first.
02:57:15: X25 RBP: Incoming connection for port 20002 from 172.22.45.49 port 61402:57:15: x25rbp_place_call: calling (10) 5553501135 from (0)02:57:15: Serial1/1: X.25 O R1 Call (11) 8 lci 402:57:15: From (0): To (10): 555350113502:57:15: Facilities: (0)02:57:15: Call User Data (1): 0xC1 (unknown)02:57:15: Serial1/1: LAPB O CONNECT (13) IFRAME 7 202:57:16: Serial1/1: LAPB I CONNECT (2) RR (R) 002:57:16: Serial1/1: LAPB I CONNECT (7) IFRAME 2 002:57:16: Serial1/1: X.25 I R1 Call Confirm (5) 8 lci 402:57:16: From (0): To (0):02:57:16: Facilities: (0)02:57:16: x25rbp_enter_p4: context 81BB2304, state 2, packet 81A9B264, reason 8)02:57:16: x25rbp_enter_d1: context 81BB2304, state 0, packet 81A9B264, reason 8)02:57:16: Serial1/1: LAPB O CONNECT (2) RR (R) 302:57:22: Serial1/1: X.25 O D1 Data (40) 8 lci 4 PS 0 PR 002:57:22: Serial1/1: LAPB O CONNECT (42) IFRAME 0 302:57:23: Serial1/1: LAPB I CONNECT (2) RR (R) 102:57:23: Serial1/1: LAPB I CONNECT (5) IFRAME 3 102:57:23: Serial1/1: X.25 I D1 RR (3) 8 lci 4 PR 102:57:23: Serial1/1: LAPB O CONNECT (2) RR (R) 402:57:24: Serial1/1: LAPB I CONNECT (15) IFRAME 4 102:57:24: Serial1/1: X.25 I D1 Data (13) 8 lci 4 PS 0 PR 102:57:24: Serial1/1: LAPB O CONNECT (2) RR (R) 502:57:25: X25 RBP: Incoming connection for port 20002 from 172.22.45.49 port 61702:57:25: x25rbp_place_call: calling (10) 5553501135 from (0)02:57:25: Serial1/1: X.25 O R1 Call (11) 8 lci 302:57:25: From (0): To (10): 555350113502:57:25: Facilities: (0)02:57:25: Call User Data (1): 0xC1 (unknown)02:57:25: Serial1/1: LAPB O CONNECT (13) IFRAME 1 502:57:25: Serial1/1: LAPB I CONNECT (2) RR (R) 202:57:26: Serial1/1: LAPB I CONNECT (7) IFRAME 5 202:57:26: Serial1/1: X.25 I R1 Call Confirm (5) 8 lci 302:57:26: From (0): To (0):02:57:26: Facilities: (0)02:57:26: x25rbp_enter_p4: context 81C0FC8C, state 2, packet 81A9B264, reason 8)02:57:26: x25rbp_enter_d1: context 81C0FC8C, state 0, packet 81A9B264, reason 8)02:57:26: Serial1/1: LAPB O CONNECT (2) RR (R) 602:57:31: Serial1/1: X.25 O D1 Data (40) 8 lci 3 PS 0 PR 002:57:31: Serial1/1: LAPB O CONNECT (42) IFRAME 2 602:57:32: Serial1/1: LAPB I CONNECT (2) RR (R) 302:57:32: Serial1/1: LAPB I CONNECT (5) IFRAME 6 302:57:32: Serial1/1: X.25 I D1 RR (3) 8 lci 3 PR 102:57:32: Serial1/1: LAPB O CONNECT (2) RR (R) 702:57:33: Serial1/1: LAPB I CONNECT (16) IFRAME 7 302:57:33: Serial1/1: X.25 I D1 Data (14) 8 lci 3 PS 0 PR 102:57:33: Serial1/1: LAPB O CONNECT (2) RR (R) 002:57:33: X25 RBP: Incoming connection for port 20002 from 172.22.45.49 port 61302:57:33: x25rbp_place_call: calling (10) 5553501135 from (0)02:57:33: Serial1/1: X.25 O R1 Call (11) 8 lci 202:57:33: From (0): To (10): 555350113502:57:33: Facilities: (0)02:57:33: Call User Data (1): 0xC1 (unknown)02:57:33: Serial1/1: LAPB O CONNECT (13) IFRAME 3 002:57:34: Serial1/1: LAPB I CONNECT (2) RR (R) 402:57:34: Serial1/1: LAPB I CONNECT (7) IFRAME 0 402:57:34: Serial1/1: X.25 I R1 Call Confirm (5) 8 lci 202:57:34: From (0): To (0):02:57:34: Facilities: (0)02:57:34: x25rbp_enter_p4: context 81C101C0, state 2, packet 81A9B264, reason 8)02:57:34: x25rbp_enter_d1: context 81C101C0, state 0, packet 81A9B264, reason 8)02:57:34: Serial1/1: LAPB O CONNECT (2) RR (R) 102:57:40: Serial1/1: X.25 O D1 Data (40) 8 lci 2 PS 0 PR 002:57:40: Serial1/1: LAPB O CONNECT (42) IFRAME 4 102:57:41: Serial1/1: LAPB I CONNECT (2) RR (R) 502:57:41: Serial1/1: LAPB I CONNECT (5) IFRAME 1 502:57:41: Serial1/1: X.25 I D1 RR (3) 8 lci 2 PR 102:57:41: Serial1/1: LAPB O CONNECT (2) RR (R) 202:57:42: Serial1/1: LAPB I CONNECT (17) IFRAME 2 502:57:42: Serial1/1: X.25 I D1 Data (15) 8 lci 2 PS 0 PR 102:57:42: Serial1/1: LAPB O CONNECT (2) RR (R) 302:57:42: X25 RBP: Incoming connection for port 20002 from 172.22.45.49 port 61702:57:42: x25rbp_place_call: calling (10) 5553501135 from (0)02:57:42: Serial1/1: X.25 O R1 Call (11) 8 lci 102:57:42: From (0): To (10): 555350113502:57:42: Facilities: (0)02:57:42: Call User Data (1): 0xC1 (unknown)02:57:42: Serial1/1: LAPB O CONNECT (13) IFRAME 5 302:57:43: Serial1/1: LAPB I CONNECT (2) RR (R) 602:57:43: Serial1/1: LAPB I CONNECT (7) IFRAME 3 602:57:43: Serial1/1: X.25 I R1 Call Confirm (5) 8 lci 102:57:43: From (0): To (0):02:57:43: Facilities: (0)02:57:43: x25rbp_enter_p4: context 818A4724, state 2, packet 81A9B264, reason 8)02:57:43: x25rbp_enter_d1: context 818A4724, state 0, packet 81A9B264, reason 8)02:57:43: Serial1/1: LAPB O CONNECT (2) RR (R) 402:57:49: Serial1/1: X.25 O D1 Data (40) 8 lci 1 PS 0 PR 002:57:49: Serial1/1: LAPB O CONNECT (42) IFRAME 6 402:57:50: Serial1/1: LAPB I CONNECT (2) RR (R) 702:57:50: Serial1/1: LAPB I CONNECT (5) IFRAME 4 702:57:50: Serial1/1: X.25 I D1 RR (3) 8 lci 1 PR 102:57:50: Serial1/1: LAPB O CONNECT (2) RR (R) 502:57:51: Serial1/1: LAPB I CONNECT (17) IFRAME 5 702:57:51: Serial1/1: X.25 I D1 Data (15) 8 lci 1 PS 0 PR 102:57:51: Serial1/1: LAPB O CONNECT (2) RR (R) 602:57:51: Serial1/1: X.25 O D1 Data (45) 8 lci 4 PS 1 PR 102:57:51: Serial1/1: LAPB O CONNECT (47) IFRAME 7 602:57:51: Serial1/1: LAPB I CONNECT (2) RR (R) 002:57:52: Serial1/1: LAPB I CONNECT (5) IFRAME 6 002:57:52: Serial1/1: X.25 I D1 RR (3) 8 lci 4Step 12
Router-C# show debugLAPB:LAPB link debugging is onTCP:TCP special event debugging is onX.25:X.25 packet debugging is onRouter-C# no debug lapbLAPB link debugging is offRouter-C# show debugTCP:TCP special event debugging is onX.25:X.25 packet debugging is onRouter-C# no debug allAll possible debugging has been turned offStep 13
Router-C# debug ip tcp ?driver TCP driver eventsdriver-pak TCP driver verboseheader-compression Header compression statisticsintercept TCP interceptpacket TCP packetsrcmd Rcmd transactionssack Selective-ACKtransactions Significant TCP eventsRouter-C# debug ip tcp transactionsTCP special event debugging is onStep 14
Router-C# show running-configBuilding configuration...Using 1994 out of 29688 bytes!version 12.1service configservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname Router-C!enable secret 5 $1$a/sP$r9xXAWz0d7XZnpzApk1831enable password cisco!!memory-size iomem 10ip subnet-zerono ip routingno ip finger!!interface FastEthernet0/0ip address 172.22.45.102 255.255.255.0no ip route-cacheno ip mroute-cachespeed autohalf-duplexno cdp enable!interface FastEthernet0/1no ip addressno ip route-cacheno ip mroute-cacheshutdownduplex autospeed autono cdp enable!interface Serial1/0description EchoBackno ip addressencapsulation x25no ip route-cacheno ip mroute-cachex25 version 1980x25 htc 3x25 threshold 1x25 map rbp 5553501136 cud 0xC1 local port 20001clockrate 9600lapb T2 400lapb T4 25lapb N1 4136!interface Serial1/1description RecentChangeno ip addressencapsulation x25no ip route-cacheno ip mroute-cachex25 version 1980x25 htc 4x25 threshold 1x25 map rbp 5553501135 cud 0xC1 local port 20002clockrate 9600lapb T2 400lapb T4 25lapb N1 4136!interface Serial1/2no ip addressno ip route-cacheno ip mroute-cacheshutdownno cdp enable!interface Serial1/3no ip addressno ip route-cacheno ip mroute-cacheshutdownno cdp enable!interface Serial1/4no ip addressno ip route-cacheno ip mroute-cacheshutdownno cdp enable!interface Serial1/5no ip addressno ip route-cacheno ip mroute-cacheshutdownno cdp enable!interface Serial1/6no ip addressno ip route-cacheno ip mroute-cacheshutdownno cdp enable!interface Serial1/7no ip addressno ip route-cacheno ip mroute-cacheshutdownno cdp enable!ip classlessno ip http server!!snmp-server engineID local 00000009020000036B490D00snmp-server community public RO!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password ciscologinline vty 5 50login!no scheduler allocateend!Step 15
Router-C# quit
Configuring ADC Service Activation Provisioning
This section describes the ADC Service Activation application for provisioning Class 5 telephone switches. This section will demonstrate provisioning of a Lucent 5ESS telephone switch as an example of how to add the Cisco X.25 RBP feature to the telco DCN.
In the sample scenario shown in Figure 32, the ADC Service Activation application has implemented the Cisco X.25 RBP feature and is connecting using TCP/IP to the router in the CO. The router in the central office is starting an X.25 session out to the Lucent 5ESS telephone switch. The end of the data record is marked by the M-bit on the X.25 side of the network. The X.25 RBP header marks the end of record on the TCP/IP side of the network. This scenario was tested with the default X.25 CCITT version of 1984.
Figure 32 ADC and Cisco X.25 RBP
To configure the Cisco X.25 RBP feature in ADC Service Activation provisioning, see Figure 32 and perform the following steps. See the "ADC Service Activation Provisioning: Example" section for a configuration example.
Step 1
Router-D# show versionStep 2
Router-D# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 3
Router-D(config)# interface serial 1/0Step 4
Router-D(config-if)# shutdownStep 5
Router-D(config-if)# description Voice ActivationStep 6
Router-D(config-if)# encapsulation x25 dceStep 7
Router-D(config-if)# x25 address 5553501130Step 8
Router-D(config-if)# x25 htc 7Step 9
Router-D(config-if)# x25 win 3Step 10
Router-D(config-if)# x25 wout 3Step 11
Router-D(config-if)# x25 ips 256Step 12
Router-D(config-if)# x25 ops 256Step 13
Router-D(config-if)# x25 subscribe flow-control alwaysStep 14
Router-D(config-if)# x25 threshold 1Step 15
Router-D(config-if)# x25 map rbp 5553501136 cud 0xC1 local port 10006Step 16
Router-D(config-if)# clockrate 56000Step 17
Router-D(config-if)# no shutdownStep 18
Router-D(config-if)# endRouter-D(config)# endStep 19
Router-D# copy run startDestination filename [startup-config]?Building configuration...[OK]
ADC Service Activation Provisioning: Example
The following example shows the configuration for serial interface 1/6:
interface Serial1/6no ip addressencapsulation x25 dcex25 address 5553501130X25 htc 7x25 win 3x25 wout 3x25 ips 256x25 ops 256x25 threshold 1x25 subscribe flow-control alwaysx25 map rbp 5553501136 cud 0xC1 local port 10006no ignore-hw local-loopbackclockrate 56000Traffic Data Collection Networks: Cisco X.25 RBP and XOT Solutions
This section describes Cisco telco solutions for traffic data collection networks like the one highlighted in Figure 33.
Figure 33 Legacy Traffic Data Collection Network
Use of the Cisco X.25 RBP feature with the Traffic Data Management System (TDMS) software application is described in the following sections:
•
•
•
Adding Cisco X.25 RBP to the Telco DCN Traffic Data Collection Connection
TDMS software is an OSS solution for network traffic monitoring, data collection, forecasting, and performance management. Originally developed by Lucent Technologies, TDMS collects, processes, analyzes, and generates reports of traffic performance. Traffic data collection applications are used for monitoring and troubleshooting the voice portion of the network. The traffic data is collected from the EDAS port on the telephone switch.
The TDMS application uses a Lucent Datakit node as the communications front end with BX.25 as the transport method (see Figure 34). The TDMS application pulls its data off the EDAS port on the Lucent 5ESS telephone switch. The EDAS port on the switch is a serial connection. The XOT solution can be used with versions of TDMS that use the Lucent Datakit node.
Figure 34 Traffic Data Collection Connection with XOT
The TDMS application supports the Cisco X.25 RBP feature, as of Release 4.3. This support eliminates the need for a Datakit node to serve as a front end for the application. A TCP/IP stack resides on the TDMS application. The Cisco X.25 RBP feature marks the end of a record on the TCP/IP sides of the network (see Figure 35).
Figure 35 Traffic Data Collection Connection with Cisco X.25 RBP
Configuring Cisco X.25 RBP for Traffic Data Collection Applications
The procedure in this section sets the low two-way channel to 4 for the router configuration. This configuration allocates space for PVC 1, PVC 2, and PVC 3. The router is set up to be a DCE at Layer 3. The packet size is changed from a default of 128 to 256. The router is acknowledging every packet with the x25 threshold command. The X.25 version is 1984, which is the default. The TCP ports are mapped as follows:
TCP Port Number PVC Number10001 110002 210003 3The router supplies the interface clocking. The router clock rate is 9600 baud. The physical cable is an EIA/TIA-232 DCE.
To configure Cisco X.25 RBP on a Cisco 3662 edge router in the traffic data collections portion of the telco DCN, see Figure 35 and perform the following steps. See the "Cisco X.25 RBP in the Traffic Data Collection Application: Example" section for a configuration example. See the "Debugging the Traffic Data Collection Connection" section for a debugging example.
Step 1
3662-router# show versionStep 2
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 3
3662-router(config)# x25 routingStep 4
3662-router(config)# interface serial 4/2Step 5
3662-router(config-if)# shutdownStep 6
3662-router(config-if)# description EDAS portStep 7
3662-router(config-if)# encapsulation x25 dceStep 8
3662-router(config-if)# x25 loc 4Step 9
3662-router(config-if)# x25 threshold 1Step 10
3662-router(config-if)# x25 ips 256Step 11
3662-router(config-if)# x25 ops 256Step 12
3662-router(config-if)# x25 pvc 1 rbp local port 100013662-router(config-if)# x25 pvc 2 rbp local port 100023662-router(config-if)# x25 pvc 3 rbp local port 10003Step 13
3662-router(config-if)# clockrate 9600Step 14
3662-router(config-if)# no shutdownStep 15
3662-router(config-if)# end3662-router(config)# endStep 16
3662-router# copy running-config startup-configDestination filename [startup-config]?Building configuration...[OK]
Cisco X.25 RBP in the Traffic Data Collection Application: Example
The following example shows the configuration for serial interface 4/2:
x25 routinginterface Serial4/2description EADASno ip addressencapsulation x25 dceno ip mroute-cachex25 ltc 4x25 ips 256x25 ops 256x25 threshold 1x25 pvc 1 rbp local port 10001x25 pvc 2 rbp local port 10002x25 pvc 3 rbp local port 10003no ignore-hw local-loopbackclockrate 9600Debugging the Traffic Data Collection Connection
To debug the traffic data collection connection, perform the following steps:
Step 1
3662-router# show interface serial 4/2Serial4/2 is up, line protocol is upHardware is CD2430 in sync modeDescription: EADASMTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation X25, loopback not setX.25 DCE, address <none>, state R1, modulo 8, timer 0Defaults: idle VC timeout 0cisco encapsulationinput/output window sizes 2/2, packet sizes 256/256Timers: T10 60, T11 180, T12 60, T13 60Channels: Incoming-only none, Two-way 4-1024, Outgoing-only noneRESTARTs 2/0 CALLs 0+0/0+0/0+0 DIAGs 0/0LAPB DCE, state CONNECT, modulo 8, k 7, N1 12056, N2 20T1 3000, T2 0, interface outage (partial T3) 0, T4 0VS 2, VR 3, tx NR 3, Remote VR 2, Retransmissions 0Queues: U/S frames 0, I frames 0, unack. 0, reTx 0IFRAMEs 663/1627 RNRs 0/0 REJs 0/0 SABM/Es 0/2 FRMRs 0/0 DISCs 0/0Last input 00:00:07, output 00:00:07, output hang neverLast clearing of "show interface" counters 2d04hInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue :0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec4027 packets input, 128719 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort3481 packets output, 9246 bytes, 0 underruns0 output errors, 0 collisions, 20 interface resets0 output buffer failures, 0 output buffers swapped out3 carrier transitionsDCD=up DSR=up DTR=up RTS=up CTS=upStep 2
3662-router# show controller serial 4/2CD2430 Slot 4, Port 2, Controller 0, Channel 2, Revision 18Channel mode is synchronous serialidb 0x62F0AD64, buffer size 1524, RS-232 DCE cable, clockrate 9600Global registersrpilr 0x2, rir 0x2, risr 0x0, rfoc 0x0, rdr 0x2tpilr 0x1, tir 0x2, tisr 0x68, tftc 0x0, tdr 0xFFmpilr 0x3, mir 0x2, misr 0x60bercnt 0xFF, stk 0x0Per-channel registers for channel 2Option registers0x02 0x00 0x42 0x67 0x60 0x00 0x00Command and status registerscmr 0xC0, ccr 0x00, csr 0xCC, msvr-rts 0xF1, msvr-dtr 0xF1Clock option registersrcor 0x86, rbpr 0x01, tcor 0xC0, tbpr 0x77Interrupt registersier 0x89, livr 0x08, licr 0x08DMA buffer status 0x20DMA receive registersarbaddr 0x3C90064, arbcnt 1548, arbsts 0x1brbaddr 0x3C8F9E4, brbcnt 1548, brbsts 0x1rcbaddr 0x3C8F369DMA transmit registersatbaddr 0x3CD4EF6, atbcnt 2, atbsts 0x62btbaddr 0x3A01B18, btbcnt 2, btbsts 0x62tcbaddr 0x3A01B1ASpecial character registersschr1 0x00, schr2 0x00, schr3 0x00, schr4 0x00scrl 0x0, scrh 0x0, lnxt 0xF1Driver context informationContext structure 0x62F0DB68, Register table 0x3E800400Serial Interface Control 5:1 Register (0x3E80080A) is 0x80Adaptor Flags 0x0Serial Modem Control Register (0x3E80080C) is 0x1DReceive static buffer 0x62DB54C8Receive particle buffers 0x62F0E1C0, 0x62F0E180Transmit DMA buffers 0x0, 0x0, 0x0, 0x0Transmit packet with particles 0x0, first word is 0x0Interrupt rates (per second) transmit 0, receive 0, modem 0True fast-switched packets 0Semi fast-switched packets 0Transmitter hang count 0Residual indication count 0Bus error count 0Aborted short frames count 0CRC short frames count 0Error countersCTS deassertion failures 0Nested interrupt errors transmit 0, receive 0, modem 0Step 3
3662-router# debug X25 allThe following reports show the X.25 connection to the EDAS port. The debug report indicates the TCP connections from the TDMS as recognized by the Cisco X.25 RBP feature. A TCP session to port 10003 is coming in from the TDMS host, which has the IP address 172.20.7.6.
*Mar 3 20:28:30.779: X25 RBP: Incoming connection for port 10003 from 172.20.7.6The router reset PVC 3, as expected:
*Mar 3 20:28:30.779: Serial4/2: X.25 O D1 Reset (5) 8 lci 3*Mar 3 20:28:30.779: Cause 9, Diag 0 (Remote DTE operational (PVC)/No additi)The switch confirms the reset:
*Mar 3 20:28:30.819: Serial4/2: X.25 I D3 Reset Confirm (3) 8 lci 3The router sends out data to the switch:
*Mar 3 20:28:30.819: Serial4/2: X.25 O D1 Data (5) 8 lci 3 PS 0 PR 0Data is being sent from the switch on LCI 3, which is PVC 3:
*Mar 3 20:28:32.411: Serial4/2: X.25 I D1 Data (127) 8 lci 3 PS 0 PR 1Step 4
3662-router# debug X25 allThe report should indicate that PVC 3 is up. You see Receiver Ready messages being sent by the router on PVC 3, only because the router has a complete path only for PVC 3. Receiver Ready messages are being sent in on PVC 1, PVC 2, and PVC 3 from the Lucent 5ESS telephone switch:
*Mar 3 20:28:32.411: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 1*Mar 3 20:28:44.367: Serial4/2: X.25 I D1 RR (3) 8 lci 2 PR 0*Mar 3 20:29:27.035: Serial4/2: X.25 I D1 RR (3) 8 lci 1 PR 0*Mar 3 20:29:34.571: Serial4/2: X.25 I D1 RR (3) 8 lci 3 PR 1*Mar 3 20:29:44.607: Serial4/2: X.25 I D1 RR (3) 8 lci 2 PR 0Step 5
3662-router# debug X25 allThe report should indicate that data is being sent from the router on LCI 3, which is PVC 3:
*Mar 3 20:30:18.843: Serial4/2: X.25 O D1 Data (5) 8 lci 3 PS 1 PR 1The report should indicate that data is being sent from the switch on LCI 3, which is PVC 3:
*Mar 3 20:30:20.111: Serial4/2: X.25 I D1 Data (127) 8 lci 3 PS 1 PR 2*Mar 3 20:30:20.111: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 2*Mar 3 20:30:27.295: Serial4/2: X.25 I D1 RR (3) 8 lci 1 PR 0*Mar 3 20:30:44.867: Serial4/2: X.25 I D1 RR (3) 8 lci 2 PR 0*Mar 3 20:31:20.006: Serial4/2: X.25 I D1 RR (3) 8 lci 3 PR 2*Mar 3 20:31:20.950: Serial4/2: X.25 O D1 Data (5) 8 lci 3 PS 2 PR 2*Mar 3 20:31:23.246: Serial4/2: X.25 I D1 Data (135) 8 lci 3 PS 2 PR 3*Mar 3 20:31:23.246: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 3Step 6
3662-router# debug X25 allThe report should indicate that a TCP session to port 10001 is coming in from the TDMS host, which has IP address 172.20.7.6:
*Mar 3 20:39:23.202: X25 RBP: Incoming connection for port 10001 from 172.20.7.6The report should indicate that the router reset PVC 1, as expected:
*Mar 3 20:39:23.202: Serial4/2: X.25 O D1 Reset (5) 8 lci 1*Mar 3 20:39:23.202: Cause 9, Diag 0 (Remote DTE operational (PVC)/No additi)The report should indicate that the switch confirms the reset:
*Mar 3 20:39:23.246: Serial4/2: X.25 I D3 Reset Confirm (3) 8 lci 1The report should indicate that data is being sent from the switch on LCI 1, which is PVC 1:
*Mar 3 20:39:23.246: Serial4/2: X.25 O D1 Data (6) 8 lci 1 PS 0 PR 0*Mar 3 20:39:23.822: Serial4/2: X.25 I D1 Data (31) 8 lci 1 PS 0 PR 1Step 7
3662-router# debug X25 all*Mar 3 20:47:21.058: X25 RBP: Incoming connection for port 10003 from 172.20.7.6*Mar 3 20:47:21.058: Serial4/2: X.25 O D1 Reset (5) 8 lci 3*Mar 3 20:47:21.058: Cause 9, Diag 0 (Remote DTE operational (PVC)/No additi)*Mar 3 20:47:21.102: Serial4/2: X.25 I D3 Reset Confirm (3) 8 lci 3*Mar 3 20:47:21.102: Serial4/2: X.25 O D1 Data (5) 8 lci 3 PS 0 PR 0*Mar 3 20:47:22.366: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 0 PR 1*Mar 3 20:47:22.366: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 1*Mar 3 20:47:22.590: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 1 PR 1*Mar 3 20:47:22.590: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 2*Mar 3 20:47:22.826: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 2 PR 1*Mar 3 20:47:22.826: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 3*Mar 3 20:47:23.066: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 3 PR 1*Mar 3 20:47:23.066: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 4*Mar 3 20:47:23.306: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 4 PR 1*Mar 3 20:47:23.306: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 5*Mar 3 20:47:23.542: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 5 PR 1*Mar 3 20:47:23.542: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 6*Mar 3 20:47:23.778: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 6 PR 1*Mar 3 20:47:23.778: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 7*Mar 3 20:47:24.014: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 7 PR 1*Mar 3 20:47:24.014: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 0*Mar 3 20:47:24.250: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 0 PR 1*Mar 3 20:47:24.250: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 1*Mar 3 20:47:24.486: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 1 PR 1*Mar 3 20:47:24.486: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 2*Mar 3 20:47:24.722: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 2 PR 1*Mar 3 20:47:24.722: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 3*Mar 3 20:47:24.958: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 3 PR 1*Mar 3 20:47:24.958: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 4*Mar 3 20:47:25.194: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 4 PR 1*Mar 3 20:47:25.194: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 5*Mar 3 20:47:25.430: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 5 PR 1*Mar 3 20:47:25.430: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 6*Mar 3 20:47:25.666: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 6 PR 1*Mar 3 20:47:25.666: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 7*Mar 3 20:47:25.902: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 7 PR 1*Mar 3 20:47:25.902: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 0*Mar 3 20:47:26.138: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 0 PR 1*Mar 3 20:47:26.138: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 1*Mar 3 20:47:26.374: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 1 PR 1*Mar 3 20:47:26.374: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 2*Mar 3 20:47:26.610: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 2 PR 1*Mar 3 20:47:26.610: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 3*Mar 3 20:47:26.846: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 3 PR 1*Mar 3 20:47:26.846: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 4*Mar 3 20:47:27.082: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 4 PR 1*Mar 3 20:47:27.082: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 5*Mar 3 20:47:27.318: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 5 PR 1*Mar 3 20:47:27.318: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 6*Mar 3 20:47:27.554: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 6 PR 1*Mar 3 20:47:27.554: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 7*Mar 3 20:47:27.790: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 7 PR 1*Mar 3 20:47:27.790: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 0*Mar 3 20:47:28.034: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 0 PR 1*Mar 3 20:47:28.034: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 1*Mar 3 20:47:28.286: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 1 PR 1*Mar 3 20:47:28.286: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 2*Mar 3 20:47:28.538: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 2 PR 1*Mar 3 20:47:28.538: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 3*Mar 3 20:47:28.790: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 3 PR 1*Mar 3 20:47:28.790: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 4*Mar 3 20:47:29.042: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 4 PR 1*Mar 3 20:47:29.042: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 5*Mar 3 20:47:29.294: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 5 PR 1*Mar 3 20:47:29.294: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 6*Mar 3 20:47:29.542: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 6 PR 1*Mar 3 20:47:29.546: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 7*Mar 3 20:47:29.794: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 7 PR 1*Mar 3 20:47:29.794: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 0*Mar 3 20:47:30.046: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 0 PR 1*Mar 3 20:47:30.046: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 1*Mar 3 20:47:30.290: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 1 PR 1*Mar 3 20:47:30.290: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 2*Mar 3 20:47:30.534: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 2 PR 1*Mar 3 20:47:30.534: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 3*Mar 3 20:47:30.770: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 3 PR 1*Mar 3 20:47:30.774: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 4*Mar 3 20:47:31.006: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 4 PR 1*Mar 3 20:47:31.010: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 5*Mar 3 20:47:31.246: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 5 PR 1*Mar 3 20:47:31.246: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 6*Mar 3 20:47:31.482: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 6 PR 1*Mar 3 20:47:31.482: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 7*Mar 3 20:47:31.718: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 7 PR 1*Mar 3 20:47:31.718: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 0*Mar 3 20:47:31.954: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 0 PR 1*Mar 3 20:47:31.954: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 1*Mar 3 20:47:32.194: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 1 PR 1*Mar 3 20:47:32.194: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 2*Mar 3 20:47:32.430: Serial4/2: X.25 I D1 Data (259) 8 lci 3 M PS 2 PR 1*Mar 3 20:47:32.430: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 3*Mar 3 20:47:32.558: Serial4/2: X.25 I D1 Data (127) 8 lci 3 PS 3 PR 1*Mar 3 20:47:32.558: Serial4/2: X.25 O D1 RR (3) 8 lci 3 PR 4*Mar 3 20:47:48.482: Serial4/2: X.25 I D1 RR (3) 8 lci 2 PR 0*Mar 3 20:48:16.042: Serial4/2: X.25 I D1 RR (3) 8 lci 1 PR 1*Mar 3 20:48:33.574: Serial4/2: X.25 I D1 RR (3) 8 lci 3 PR 1*Mar 3 20:48:48.622: Serial4/2: X.25 I D1 RR (3) 8 lci 2 PR 0
Configuring the Lucent 5ESS EDAS Port
Note
Following is a sample of the Lucent 5ESS EDAS port configuration form with the required field values shown in bold text. (See the "Lucent cpblx Form Parameter Descriptions" section for descriptions of important fields in this form.) Notice that field 65 has an X.25 packet size of 256. Fields 59 and 61 are the input and output buffer sizes. These fields must be three bytes larger than the packet size. In the example, the packet size is 256 and the buffer size is 259.
Communications Protocol Option Block (Recent Change and Verify)1.option_name:cpblx332.speed:9600 3.duplex:full 4.ds_type:2024A5.carrier:c 6.line_access:private 7.mode_op:b8.pdtime1:60 9.pdtime2:100 10.window:411.rexmit:3 12.dcedte:0 13.pcsd_stat:active14.config:simplex(3/4)35.neid.nend1)____ 4)____ 7)____ 10)____ 13)____2)____ 5)____ 8)____ 11)____ 14)____3)____ 6)____ 9)____ 12)____ 15)____46.pswrd.pwrd1)____ 4)____ 7)____ 10)____ 13)____2)____ 5)____ 8)____ 11)____ 14)____3)____ 6)____ 9)____ 12)____ 15)____57.perm_state:allow 58.outscrsiz:4062 59.outpktsiz:25960.inscrsiz:4062 61.inpktsiz:259cpblx3 (4/4)62.hup:n 63.spckt:0 64.x3wsize:2 65.x3psize:25666.x3pvcn.ldinno1)_____ 6)_____ 11)_____ 16)_____ 21)_____ 26)_____31)_____2)1 7)_____ 12)_____ 17)_____ 22)_____ 27)_____32)_____3)3 8)_____ 13)_____ 18)_____ 23)_____ 28)_____4)2 9)_____ 14)_____ 19)_____ 24)_____ 29)_____5)_____ 10)_____ 15)_____ 20)_____ 25)_____ 30)_____81.time_ti:180 82.time_tj:60 83.time_tf:60 84.time_tl:6085.time_td:180 86.time_ts:180 87.time_ack:5Lucent cpblx Form Parameter Descriptions
This section describes important fields in the Lucent cpblx form and lists values that can be entered in the fields.
1.
Option block name. This is a key field. Legal values: alphanumeric characters.
2.
Data rate of associated communications equipment.
Legal values: 110, 300, 1200, 1800, 2400, 4800, 9600, 56000, 64000, null.
3.
Full or half-duplex.
Legal values: full, half, null.
4.
PC modem type.
Legal values: 201CDDD, 209A, NOPORT, 201CPL, 212A, PL201C, 202/108, 2024A, RS449, 208A, 2048A, ITAPAC, 703COU, 703CCUL, 703CCUH, 703CDO, RS232, RS422, RS423, 208ADDD, CCITT 208B, NODS, NULL.
Note
Multiple values may be considered equivalent in the database. Any legal value may be entered, but the value may not be shown in the Recent Change and Verify displays.
Table 5 lists which values are displayed for the set of equivalent values.
Table 5 Equivalent Values
703COU
703COU, 212A
703CCUL
703CCUL, 208A
703CCUH
703CCUH, 208B
703CDO
703CDO, 209A
RS232
RS232, RS449
RS422
RS422, RS423, NODS, NULL
5.
Continuous or switched carrier.
Legal values: c, s, null.
6.
Type of line access.
Legal values: direct, private, noACU, ACU, null.
7.
Mode operation. Block or send/receive mode of operation.
Legal values: b, s, null.
8.
Maximum time to wait for level 2 protocol acknowledgment. Values entered represent tenths of a second.
Legal values: 0 to 255, HEX.
9.
Maximum time to allow the data link to be idle. Values entered represent tenths of a second.
Legal values: 0 to 255, HEX.
10.
Maximum number of I-Frames a station may have outstanding.
Legal values: 0 to 7.
11.
Maximum number of retransmissions of an individual frame.
Legal values: 0 to 7.
12.
Data terminal equipment or data circuit-terminating equipment (DCE).
Legal values: 0 (data terminal equipment); 1 (data circuit-terminating equipment).
13.
Normal status for this pcsd.
Legal values: active (active device of duplex pair); standby (standby device of duplex pair); null.
14.
Simplex, duplex, or multiple configuration.
Legal values: duplex (one of a duplex pair); null: multiple; simplex (simplex Peripheral Controller Subdevice or PCSD).
15.
System identification (id), time limit, telephone number.
16.
System identifier.
Legal values: 0 to 65535, HEX, null.
Note
17.
Time limit (seconds).
Legal values: 0 to 255, HEX, null.
18.
Telephone number.
Legal values: alphanumeric or null.
19.
Check security information.
Legal values: y, n, null.
20.
Link identification number.
Legal values: 0 to 7; default value: 0.
21.
Length of far-end system identifier.
Legal values: 0 to 15; default value: 0.
22.
Length of near-end system identifier.
Legal values: 0 to 15; default value: 0.
23.
Length of password.
Legal values: 0 to 15; default value: 0.
24.
Far-end system identifier.
Legal values: 0 to 255, HEX, null; default value: 0.
25.
Near-end system identifier.
Legal values: 0 to 255, HEX, null; default value: 0.
26.
Password.
Legal values: 0 to 255, HEX, null; default value: 0.
27.
Dialup permission state.
Legal values: allow (allow dialup connection); condalw (if duplex and primary not active; allow dialup connection); inhibit (inhibit dialup connection).
28.
Output buffer area size (words).
Legal values: 0 to 65535, HEX.
Note
29.
Data portion of output buffer (bytes).
Legal values: 0 to 640, 0x0 to 0x280, null.
30.
Input buffer area size (words).
Legal values: 0 to 65535, HEX.
Note
31.
Data portion of input buffer (bytes).
Legal values: 0 to 640, 0x0 to 0x280, null.
32.
Hang up on last close.
Legal values: y, n, null.
33.
Link data packet size.
Legal values: 0 to 255.
34.
Level 3 protocol window size.
Legal values: 0 to 7, 0x0 to 0x7, null.
35.
Level 3 protocol packet size.
Legal values: 0 to 637, 0x0 to 0x27D, null.
36.
Logical channel number corresponding to the partition number.
Legal values: 0 to 4095, 0x0 to 0xFFF, null.
37.
Interrupt packet timer.
Legal values: 180 to 600 seconds; default value: 180.
38.
Reject packet timer.
Legal values: 60 to 600 seconds; default value: 60.
39.
Flow control packet timer.
Legal values: 10 to 600 seconds; default value: 60.
40.
Unacknowledged data packet timer.
Legal values: 60 to 600 seconds; default value: 60.
41.
Reset request timer.
Legal values: 180 to 600 seconds; default value: 180.
42.
Restart request timer.
Legal values: 180 to 600 seconds; default value: 180.
43.
Acknowledgment timer.
Legal values: 5 to 300 seconds; default value: 5.
Additional References
This section provides the following additional reference information:
Related Documents
AMATPS generic requirements
TR-TSY-000385, AUTOMATIC MESSAGE ACCOUNTING TELEPROCESSING SYSTEM (AMATPS) GENERIC REQUIREMENTS, September 1986
AMATPS PPSN generic requirements
TA-TSY-000787, AMATPS GENERIC REQUIREMENTS FOR USE WITH PUBLIC PACKET SWITCHED NETWORKS (PPSN)
BX.25 protocol specification
Pub 54001, Operations Systems Network Communications Protocol Specification, BX.25, Issue 3 Addendum A, August 1983
TCP/IP-to-X.25 protocol mediation
X.25 Record Boundary Preservation for Data Communications Networks Cisco IOS Release 12.2(8)T feature module
X.25
•
•
•
•
X.25 troubleshooting
Appendix A, "Cisco IOS X.25 Toolkit" in the Cisco Network Solutions for the Telco DCN document.
Related Websites
4Tel
EVOLVING Systems (TDMS support)
Kansys, Inc
Lucent OS
Lucent Billdats
Intec
Telesciences
TTI Telecom
Technical Assistance
Glossary
ADM—add/drop multiplexer
BAI—Backup Active Interface
BX.25—AT&T Bell Laboratories' variation of the ITU X.25 standard
CCITT—Consultative Committee for International Telegraph and Telephone
CDR—call detail record
CLEC—competitive local exchange carrier
CUD—Call User Data
DCE—data communications equipment (EIA expansion); data circuit-terminating equipment (ITU-T expansion)
DCN—data communications network
DRM—Lucent Distinctive Remote Module
DSLAM—digital subscriber line access multiplexer
DTE—data terminal equipment
EB—Echo Back
EDAS—Engineering Data Acquisition System
EIA/TIA—Electronic Industries Alliance/Telecommunications Industry Alliance
EMM—Element Mediation Module
EOR—End of Record
GPT—GEC-Plessey Telecommunications, manufacturers of System-X
I-Frame—Information Frame
ILEC—incumbent local exchange carrier
ITU—International Telecommunication Union
LAPB—Link Access Procedure, Balanced
LCI—logical channel identifier
M-bit—more data bit
MNP—Multi Network Protocol
MTP—Message Transfer Protocol
MUX—multiplexer
NEBS—Network Equipment Building Systems
NFM—Network Fault Management
NMA—Network Management Application from Telcordia
NOC—network operations center
OCS—optical convergence switch
OSS—Operations Support Systems
PAD—packet assembler/disassembler
PTT—Post, Telephone, and Telegraph
PVC—permanent virtual circuit
RBOC—regional Bell operating company
RBP—Record Boundary Preservation
RC—Recent Change
SABM—Set Asynchronous Balance Mode
SCC—specialized common carrier
SDH—Synchronous Digital Hierarchy
SLM—Synchronous Line Module
SONET—Synchronous Optical Network
STUN—serial tunnel
SVC—switched virtual circuit
TDMS—Traffic Data Management System
telco—telephone company
VC—virtual circuit; virtual connections (XOT)
X.25—ITU-T standard
XFER—DMS-100 Data Transferral Application Protocol
XOT—X.25 over TCP
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2002-2007 Cisco Systems, Inc. All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)