Cisco Network Solutions for the Telco DCN · iii Cisco Network Solutions for the Telco DCN CONTENTS...

Cisco Network Solutionsfor the Telco DCNOctober 25, 2007

This document was created as a joint effort between Don Schriner in the Cisco CTO Consulting Engineering Group and Alliene Turner in Cisco IOS Documentation.

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

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.

Cisco Network Solutions for the Telco DCN

Copyright © 2005-2007 Cisco Systems, Inc. All rights reserved.

CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0710R)

C O N T E N T S

C H A P T E R 1 Introduction to Cisco Network Solutions for the Telco DCN 1-1

Introduction 1-1

Prerequisites 1-1

The Telco DCN Network: Overview 1-2

Organization of This Document 1-3

C H A P T E R 2 Telephone Switch Environments 2-1

Introduction 2-1

BX.25 Overview 2-2

BX.25 as a DCN Transport Mechanism 2-2

Differences Between BX.25 and X.25 2-2

Cisco Telephone Switch Migration Solutions Overview 2-3

CDR Bill Collection Networks: Cisco XOT and RBP Solutions 2-5

Cisco XOT Features for Transporting CDR Data 2-6

The BX.25 Security I-Frame 2-6

X.25 and LAPB Parameters 2-7

Configuring XOT on the Billing Collector Side of the Network 2-9

Configuring XOT on the Telephone Switch Side of the Network 2-11

Sterling 5000 Collector Configuration: Examples 2-12

Configuring a Cisco Router for a Host That Supports XOT 2-17

Mercury Mediation Bill Collector That Supports XOT: Example 2-19

Verifying the SVC Connection on the Mercury Mediation Device 2-19

Cisco RBP and RBP Q-Bit Features for Transporting CDR Data 2-20

The Cisco RBP Feature 2-20

The Cisco RBP Q-Bit Feature 2-20

RBP and RBP Q-Bit File Type Compatibility 2-21

Configuring a Cisco Router for a CDR Host That Supports the RBP Feature 2-21

Cisco X.25 RBP with the Inter-mediatE to a Lucent 5ESS Switch: Example 2-23

Cisco X.25 RBP with the Inter-mediatE to a Nortel DMS 100 Switch: Example 2-23

Configuring the Cisco X.25 RBP Q-Bit Feature for the MTP File Type 2-24

Cisco X.25 RBP Q-Bit Feature with the Inter-mediatE to a Class 5 Switch with MTP File Type: Example 2-25

Configuring the Cisco X.25 RBP Q-Bit Feature for the MNP File Type 2-26

iiiCisco Network Solutions for the Telco DCN

Contents

Cisco X.25 RBP Q-Bit Feature with the Inter-mediatE to a Class 5 Switch with MNP File Type: Example 2-27

Debugging Cisco X.25 RBP 2-28

Debugging a TCP/IP Connection 2-28

Debugging an X.25 Serial Connection 2-29

Debugging the RBP Configuration 2-32

Configuring an Intec Telecom Systems Inter-mediatE System 2-33

Switch Monitoring Networks: Cisco STUN OSS Connectivity Solution 2-38

Switch Monitoring Overview 2-38

The Lucent Datakit Network 2-40

Migrating to TCP/IP Using Cisco STUN 2-40

Configuring STUN on the Workstation Side of the Network 2-42

Configuring STUN on the Telephone Switch Side of the Network 2-44

Cisco STUN OSS Connectivity Solution: Examples 2-46

Verifying Links in the Cisco STUN OSS Connectivity Solution 2-48

Debugging STUN Connections 2-49

Switch Monitoring Networks: Cisco X.25 BAI OSS Connectivity Solution 2-50

Cisco X.25 BAI OSS Connectivity Overview 2-50

Adding Cisco X.25 BAI to the Telco DCN 2-51

Configuring Cisco X.25 BAI on the NMA Side of the Network 2-52

NMA Gateway Configuration: Example 2-53

NMA-Side Configuration: Example 2-54

Verifying Address Substitutions 2-54

Configuring Cisco X.25 BAI on the Telephone Switch Side of the Network 2-58

X.25 BAI Telephone Switch Side Configuration: Example 2-62

Verifying PVC-to-SVC Conversions 2-63

Configuring SCC0 and SCC1 on the Lucent 5ESS Telephone Switch Form 2-66

Monitoring the Lucent DRM 2-67

Configuring the Lucent DRM 2-68

Lucent DRM-Side Configuration: Example 2-68

Application Host Configuration: Example 2-69

Switch Monitoring Networks: IP and Cisco X.25 BAI and EOR Solutions 2-69

Configuring a Cisco Router with X.25 BAI and EOR on the Telephone Switch Side of the Network 2-69

Cisco Router with X.25 BAI and EOR on the Telephone Switch Side of the Network: Example 2-73

Verifying Cisco X.25 BAI and EOR Configurations 2-74

TTI Telecom Monitoring Application Cisco X.25 BAI Solution 2-77

Provisioning Networks: Cisco X.25 RBP Solution 2-79

Cisco X.25 RBP Solution Overview 2-80

ivCisco Network Solutions for the Telco DCN

Contents

Adding Cisco X.25 RBP to the Telco DCN Provisioning Connection 2-80

Configuring the CONNECTVU-ATP Application 2-81

Configuring the Lucent 5ESS Echo Back Port 2-82

Configuring the Echo Back Port on the Cisco Router 2-82

Echo Back Port Configuration: Example 2-84

Configuring the Lucent 5ESS Recent Change Port 2-84

Configuring the Recent Change Port on the Cisco Router 2-85

Recent Change Port Configuration: Example 2-86

Debugging the Echo Back and Recent Change Ports 2-87

Configuring ADC Service Activation Provisioning 2-97

ADC Service Activation Provisioning: Example 2-99

Traffic Data Collection Networks: Cisco X.25 RBP and XOT Solutions 2-99

Adding Cisco X.25 RBP to the Telco DCN Traffic Data Collection Connection 2-100

Configuring Cisco X.25 RBP for Traffic Data Collection Applications 2-101

Cisco X.25 RBP in the Traffic Data Collection Application: Example 2-103

Debugging the Traffic Data Collection Connection 2-103

Configuring the Lucent 5ESS EDAS Port 2-108

Lucent cpblx Form Parameter Descriptions 2-109

C H A P T E R 3 Transmission Equipment in X.25 Environments 3-1

Introduction 3-1

Cisco Network Solutions for the Telco DCN Transmission Equipment in X.25 Environments 3-2

Migration Requirements for a DCN 3-2

X.25 and LAPB Parameters for XOT and Protocol Translation 3-4

Adding Cisco XOT to the DCN 3-4

TL1 in the Cisco Network 3-8

Protocol Translation as an X.25-to-TCP/IP Mediation Function 3-9

Migration Prerequisites 3-12

Asynchronous Console Configuration 3-12

Protocol Translation Ruleset Feature 3-12

Cisco X.25 Version Feature 3-12

TCP-to-X.25 Protocol Translation Between IP-Based Hosts and X.25 Interfaces 3-13

Fujitsu SONET GNE Protocol Translation Configuration 3-13

Cable Requirements for the Fujitsu SONET GNE 3-14

Provisioning the Fujitsu SONET GNE 3-14

Configuring a Cisco Protocol Translation Router for the Fujitsu SONET GNE 3-16

Testing Protocol Translation on the Fujitsu SONET GNE 3-19

ADC Soneplex Protocol Translation Configuration 3-20

ADC Soneplex Cable Requirement 3-20

vCisco Network Solutions for the Telco DCN

Contents

Provisioning the ADC Soneplex 3-21

Configuring a Cisco Protocol Translation Router for the ADC Soneplex 3-23

Testing Protocol Translation on the ADC Soneplex 3-26

Alcatel Litespan Protocol Translation Configuration 3-27

Provisioning the Alcatel Litespan 3-28

Configuring a Cisco Protocol Translation Router for the Alcatel Litespan 3-30

Testing Protocol Translation on the Alcatel Litespan 3-33

Alcatel 1603 SM Protocol Translation Configuration 3-33

Cable Requirements for the Alcatel 1603 SM 3-34

Provisioning the Alcatel 1603 SM 3-35

Configuring a Cisco Protocol Translation Router for the Alcatel 1603 SM 3-35

Testing Protocol Translation on the Alcatel 1603 SM 3-38

Alcatel 1633 SX DCS Protocol Translation Configuration 3-39

Cable Requirements for the Alcatel 1633 SX DCS 3-39

Provisioning the Alcatel 1633 SX DCS 3-39

Configuring a Cisco Protocol Translation Router for the Alcatel 1633 SX DCS 3-42

Testing Protocol Translation on the Alcatel 1633 SX DCS 3-44

Alcatel DCS-DEXCS Protocol Translation Configuration 3-45

Cable Requirement for the Alcatel DCS-DEXCS 3-46

Provisioning the Alcatel DCS-DEXCS 3-46

Configuring a Cisco Protocol Translation Router for the Alcatel DCS-DEXCS 3-47

Testing Protocol Translation on the Alcatel DCS-DEXCS 3-49

Tellabs Titan 5500 DCS via DCN Protocol Translation Configuration 3-50

Cable Requirements for the Tellabs Titan 5500 DCS 3-51

Provisioning the Tellabs Titan 5500 DCS 3-51

Configuring a Cisco Protocol Translation Router for the Tellabs Titan 5500 DCS 3-53

Testing Protocol Translation on the Tellabs Titan 5500 DCS 3-56

Applied Digital T3AS DCS via DCN Protocol Translation Configuration 3-57

Cable Requirements for the Applied Digital T3AS DCS 3-58

Provisioning the Applied Digital T3AS DCS 3-60

Configuring a Cisco Protocol Translation Router for the Applied Digital T3AS DCS 3-60

Testing Protocol Translation on the Applied Digital T3AS Digital Cross-Connect 3-63

Wiltron Test System Protocol Translation Configuration 3-63

Configuring a Cisco Router for Protocol Translation to Wiltron 3-64

Testing Protocol Translation on the Wiltron 3-66

Troubleshooting Telco Equipment in X.25 Environments 3-67

Using Network Management Application Alarms to Identify System Problems 3-67

viCisco Network Solutions for the Telco DCN

Contents

C H A P T E R 4 SONET/SDH OSI Environments 4-1

Introduction 4-1

Scaling SONET/SDH in the Telco DCN: Overview 4-1

OSI as a DCN Transport Mechanism 4-3

IP Standards Development for the DCC and the DCN 4-4

DCN Design Considerations for OSI 4-4

DCN Design with a Classic OSI Implementation 4-6

IS-IS Multiarea DCN Architecture with SONET/SDH Deployment in All Central Offices 4-8

The Cisco Three-Tiered DCN Network Architecture 4-12

Three-Tiered DCN Network Overview 4-12

OSI Addressing Issues and Suggestions 4-13

OSI Addressing Implementation 4-16

Access Layer Configuration 4-18

SONET/SDH Scaling Issues for Multiple OSI Areas 4-18

Defining IS-IS Multiareas with ISL Trunking 4-21

Configuring an IS-IS Multiarea Network on a VLAN Using ISL Encapsulation 4-24

Designated IS Election Process on a LAN 4-25

Verifying an IS-IS Multiarea Network Using VLAN Trunking and ISL Encapsulation 4-26

Configuring a Cisco Catalyst 2924XL VLAN Using ISL Encapsulation 4-29

Verifying the Cisco Catalyst 2924XL VLAN Configuration Using ISL Encapsulation 4-30

Defining IS-IS Multiareas with IEEE 802.1Q Trunking 4-31

Configuring an IEEE 802.1Q Trunk Router 4-32

Configuring a Cisco Catalyst 2924XL VLAN with IEEE 802.1Q Encapsulation 4-33

Verifying a Cisco Catalyst 2924XL VLAN with IEEE 802.1Q Encapsulation 4-33

Defining Multiple Areas with Manual Area Addressing 4-34

Configuring Manual Area Addressing 4-35

Verifying Adjacencies in a Network with Manual Area Addresses 4-37

Troubleshooting Adjacencies in a Network with Manual Area Addresses 4-38

Using Generic Routing Encapsulation Tunnels to Prevent Area Partitions 4-38

CLNS over GRE Tunnels 4-39

Configuring a GRE Tunnel 4-40

IS-IS Attach-Bit Control Feature 4-45

Verifying IS-IS Attach-Bit Control 4-46

Using IP over CLNS Tunnels to Access Remote Devices 4-50

Configuring a Tunnel Using IP over CLNS 4-51

Verifying the IP over CLNS Tunnel Configuration 4-52

Configuring a Contact Closure Device 4-53

Verifying the Contact Closure Device Configuration 4-53

Mapping NSAPs to Device Names Using TARP 4-54

viiCisco Network Solutions for the Telco DCN

Contents

Enabling TARP 4-59

Using TARP with Remote Login Applications 4-61

Controlling TARP Propagation Using Split Horizon 4-64

Additional Methods of Controlling the Propagation of TARP Packets 4-66

TARP PDU Packet Propagation Control Configuration Commands 4-68

Maintaining and Troubleshooting the IS-IS Network 4-68

Mapping NSAPs to CLNS Host Names 4-69

Using TLV 137 to Correlate Router and Host Names 4-69

Displaying IS-IS Network Topology 4-70

Verifying IS-IS Adjacency Formation 4-72

Verifying IS-IS Network Connectivity Using the ping and traceroute Commands 4-79

Troubleshooting Network Connections Using the ping clns Command 4-80

Troubleshooting Network Connections Using TARP PDUs 4-84

Distribution Layer Configuration 4-87

Configuring the Distribution Network 4-87

Distribution Network Configuration Example 4-89

Core Layer Configuration 4-92

OSI Domains and the Core 4-92

Configuring the Core Network 4-93

Core Network Configuration Examples 4-93

Configuring the First Core Router 4-94

Verifying the First Core Router Configuration 4-95

Configuring a Second Core Router 4-96

Configuring the ISO IGRP Routing Protocol 4-96

Configuring a Third Core Router 4-97

Verifying the Routing Table 4-98

Verifying Network Connectivity 4-99

Adding Redundancy to the Core 4-99

Tunneling Across the Core 4-100

Completing the Core Router Configurations 4-100

C H A P T E R 5 MPLS in the DCN 5-1

Introduction 5-1

MPLS in the DCN: Overview 5-2

Scenarios for Service Providers Deploying MPLS VPNS in the DCN 5-3

Shared Core Network 5-5

Multiple DCNs 5-6

Untrusted Management Traffic 5-9

Enterprise User Traffic VPN 5-10

viiiCisco Network Solutions for the Telco DCN

Contents

Service Provider Network for Customer Data with a Management VPN for a DCN 5-11

Benefits of MPLS VPNs on a DCN 5-12

Supported Platforms 5-13

Design Details 5-14

Traffic Separation 5-14

Routing Information in a VRF 5-15

Deploying MPLS VPNs on a DCN 5-16

Core Architecture 5-16

Route Reflectors in an MPLS Network 5-17

IPsec-Aware MPLS VPN 5-18

Configuration Examples for MPLS VPNs on a DCN 5-18

Data Center PE (PE-5)-Blue Routes Imported: Example 5-19

Data Center PE (PE-4)-Red Routes Imported: Example 5-19

Central Center PE (PE-1)-Blue and Red Routes Exported: Example 5-19

Central Center PE (PE-2)-Blue and Red Routes Exported: Example 5-20

A P P E N D I X A Cisco IOS X.25 Toolkit A-1

Introduction A-1

Multi-PAD Support for X.25 Connections A-1

Relay X.25 VC Number A-4

Configuring a Network Without the X.25 Relay Feature A-5

Router 2821 Configuration: Example A-6

Router 2851 Configuration: Example A-6

Router 3725A Configuration: Example A-7

Router 2651XMA Configuration: Example A-8

Debug Command Traces Without the X.25 Relay Feature Enabled A-8

Configuring a Network with the X.25 Relay Feature A-16

Configuring X.25 Relay on Router 2851 A-16

Router 2851 with X.25 Relay Configured: Example A-17

Configuring X.25 Relay on Router 3725A A-17

Debug Command Traces with the X.25 Relay Feature Enabled A-18

X.25 Throughput Negotiation A-24

Network Element Dial-Out Prevention A-26

Modem Always On for Network Elements A-27

Debugging X.25 A-28

Debugging LAPB A-29

Router 2821 Configuration for LAPB Debugging: Example A-30

Router 2851 Configuration for LAPB Debugging: Example A-31

ixCisco Network Solutions for the Telco DCN

Contents

Debugging LABP Without Interface Filtering A-32

Debugging LABP with Interface Filtering A-38

A P P E N D I X B References B-1

Introduction B-1

References for Telephone Switch Environments B-2

References for Transmission Equipment in X.25 Environments B-3

References for SONET/SDH OSI Environments B-4

References for MPLS in the DCN B-5

References for X.25 Toolkit B-5

G L O S S A R Y

I N D E X

xCisco Network Solutions for the Telco DCN

C H A P T E R 1
Introduction to Cisco Network Solutions for the Telco DCN
First Published: October 25, 2007Last Updated: October 25, 2007

Finding Support Information for Platforms and Cisco IOS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

IntroductionThis 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. This document describes 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 this document will help telcos migrate their legacy networks to a router-based TCP/IP network, which will simplify the DCN and reduce equipment costs.

This chapter provides the following sections:

• Prerequisites, page 1-1

• The Telco DCN Network: Overview, page 1-2

• Organization of This Document, page 1-3

PrerequisitesCisco IOS software is packaged in feature sets that are supported on specific platforms. The features described in this document are supported on the Cisco Telco and Enterprise feature sets. To get updated information regarding platform support for this feature, see the “Finding Support Information for Platforms and Cisco IOS Software Images” section.

1-1Cisco Network Solutions for the Telco DCN

http://www.cisco.com/go/cfn

Chapter 1 Introduction to Cisco Network Solutions for the Telco DCNThe Telco DCN Network: Overview

The Telco DCN Network: OverviewThe 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 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 performing network provisioning tasks.

Figure 1-1 shows the elements of a typical DCN network.

Figure 1-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.

TDM

8886

0

Network OperationsCenter

OperationsSupportSystems

Workstation

Mainframeor minicomputer

Alarms, control, and test messages

Configuration and backup files

Network Elements

SONET/SDHring

Transmissionsystem

DSL

ATM

Alarmunits

Class 4/5telephone

switch

ADM

Dial

GNE

Dialup,leased

line

X.25(XOT)

IP/OSI

Frame Relay, ATM, T1/E1

Billing data collection

Software downloads

MUX


Chapter 1 Introduction to Cisco Network Solutions for the Telco DCNOrganization of This Document

Organization of This DocumentThis document describes Cisco’s telco DCN migration solutions in the following chapters and appendixes:

• Chapter 2, “Telephone Switch Environments” describes specific solutions for that part of the DCN that uses BX.25 as a transport mechanism to a Class 4 or Class 5 telephone switch. The chapter uses examples mainly of connectivity to a Lucent 5ESS telephone switch, although examples for Siemens and Nortel telephone switches are also included, and procedures provided in this chapter can be applied to DCNs with other types of switches and equipment.

• Chapter 3, “Transmission Equipment in X.25 Environments” describes solutions that will help telcos migrate transmission equipment that use the X.25 protocol to a router-based TCP/IP network. Specifically, the solutions will help service providers migrate their OSSs with an X.25 interface onto a TCP/IP backbone.

• Chapter 4, “SONET/SDH OSI Environments” describes solutions that will help telcos connect their SONET/SDH network elements to a router-based network using the Open System Interconnection (OSI) protocol, which simplifies the DCN and reduces equipment costs.

• Chapter 5, “MPLS in the DCN” describes an architecture based on MPLS (Multiprotocol Label Switching) technology for converged networks that provides a framework DCN for a growing range of new technologies being deployed on a single foundation.

• Appendix A, “Cisco IOS X.25 Toolkit” describes Cisco IOS features that can be useful in DCN X.25 networks.

• Appendix B, “References” contains references related to information in the chapters of this document.


Chapter 1 Introduction to Cisco Network Solutions for the Telco DCNOrganization of This Document


C H A P T E R 2
Telephone Switch Environments

Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images


IntroductionThe data communications network (DCN) transports network management traffic between network elements and their respective Operations Support Systems (OSSs), making them a vital link between the service network and the network operations center (NOC). The solutions presented in this chapter will help telcos migrate their legacy networks to a router-based TCP/IP network, which will simplify the DCN and reduce equipment costs.

Several methods for implementing the migration to TCP/IP are described, including detailed configuration examples for migrating the host applications that preserve the legacy transport connection on the telephone switch.

This chapter describes specific solutions for that part of the DCN that uses BX.25 as a transport mechanism to a Class 4 or Class 5 telephone switch. This chapter uses examples mainly of connectivity to a Lucent 5ESS telephone switch, although examples for Siemens and Nortel telephone switches are also included, and procedures provided in this chapter can be applied to DCNs with other types of switches and equipment. These solutions are described in the following sections:

• BX.25 Overview, page 2-2

• Cisco Telephone Switch Migration Solutions Overview, page 2-3

• CDR Bill Collection Networks: Cisco XOT and RBP Solutions, page 2-5

• X.25 and LAPB Parameters, page 2-7

• Switch Monitoring Networks: Cisco STUN OSS Connectivity Solution, page 2-38

• Switch Monitoring Networks: Cisco X.25 BAI OSS Connectivity Solution, page 2-50

• Switch Monitoring Networks: IP and Cisco X.25 BAI and EOR Solutions, page 2-69

• Provisioning Networks: Cisco X.25 RBP Solution, page 2-79

• Traffic Data Collection Networks: Cisco X.25 RBP and XOT Solutions, page 2-99



Chapter 2 Telephone Switch EnvironmentsBX.25 Overview

• Lucent cpblx Form Parameter Descriptions, page 2-109

BX.25 OverviewThe following sections provide an overview of the BX.25 protocol:

• BX.25 as a DCN Transport Mechanism, page 2-2

• Differences Between BX.25 and X.25, page 2-2

BX.25 as a DCN Transport MechanismThe 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.25Many 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.)


http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a0080455518.html



Chapter 2 Telephone Switch EnvironmentsCisco Telephone Switch Migration Solutions Overview

Cisco Telephone Switch Migration Solutions OverviewSolutions 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-1 shows a Lucent 5ESS telephone switch with the connections that are required for its use and maintenance.

Figure 2-1 Connections and Networks Required for a Lucent 5ESS Telephone Switch

The connections can be divided into the following categories:

• Collection of call detail records (CDRs) or billing information

• Monitoring for alarms

• Provisioning of new services

• Collection of trunk (traffic) engineering data

Figure 2-1 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:

• Cisco serial tunneling (STUN)

• XOT

8256

0

Lucent 5ESS

Call detail recordcollection

Monitoring

Provisioning

Datakit node

EDAS

EchoBack

SCC0

SCC1

Traffic engineering

X.25

Datakitbackbone

COSAM

Datakit node

X.25 PAD X.25 PAD Recent Change

ModemsModems


Chapter 2 Telephone Switch EnvironmentsCisco Telephone Switch Migration Solutions Overview

• Cisco X.25 Record Boundary Preservation (RBP)

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 2-2.

Figure 2-2 A Telco DCN Fully Migrated to TCP/IP

In Figure 2-2, 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:

• Data collected from the telephone switch for customer billing—See the “CDR Bill Collection Networks: Cisco XOT and RBP Solutions” section on page 2-5. This section includes information about the enhanced RBP Q-bit solution, which identifies control frames and data frames in the RBP six-byte header and allows Nortel’s Multi Network Protocol (MNP) and Ericsson’s Message Transfer Protocol (MTP) file types to be supported these file types use control frames in the CDR transfer.

• Data collected from the telephone switch for alarm monitoring—See the “Switch Monitoring Networks: Cisco STUN OSS Connectivity Solution” section on page 2-38, the “Switch Monitoring Networks: Cisco X.25 BAI OSS Connectivity Solution” section on page 2-50, and the “Switch Monitoring Networks: IP and Cisco X.25 BAI and EOR Solutions” section on page 2-69.

• Data exchanged between the telephone switch and the provisioning application—See the “Provisioning Networks: Cisco X.25 RBP Solution” section on page 2-79.

• Data exchanged between the traffic engineering application and the Engineering Data Acquisition System (EDAS) port on the telephone switch—See the “Traffic Data Collection Networks: Cisco X.25 RBP and XOT Solutions” section on page 2-99.

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.

8255

9

Lucent 5ESS


Monitoring

Provisioning

RBP

RBP

STUN

STUN

XOT

Traffic engineering

IPbackbone

BX.25


Chapter 2 Telephone Switch EnvironmentsCDR Bill Collection Networks: Cisco XOT and RBP Solutions

CDR Bill Collection Networks: Cisco XOT and RBP SolutionsThis section describes Cisco telco solutions for CDR billing collection networks like the one highlighted in Figure 2-3.

Figure 2-3 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, page 2-6

• The BX.25 Security I-Frame, page 2-6

• Configuring XOT on the Billing Collector Side of the Network, page 2-9

• Configuring XOT on the Telephone Switch Side of the Network, page 2-11

• Configuring a Cisco Router for a Host That Supports XOT, page 2-17

• Cisco RBP and RBP Q-Bit Features for Transporting CDR Data, page 2-20

• Configuring a Cisco Router for a CDR Host That Supports the RBP Feature, page 2-21

• Configuring the Cisco X.25 RBP Q-Bit Feature for the MTP File Type, page 2-24

• Configuring the Cisco X.25 RBP Q-Bit Feature for the MNP File Type, page 2-26

• Debugging Cisco X.25 RBP, page 2-28

• Configuring an Intec Telecom Systems Inter-mediatE System, page 2-33

8256

1

Lucent 5ESS


Monitoring

Provisioning

Datakit node

EDAS

Recent Change

EchoBack

SCC0

SCC1ModemsModems

Traffic engineering

X.25

Datakitbackbone

COSAM

Datakit node

X.25 PAD X.25 PAD


Chapter 2 Telephone Switch EnvironmentsCDR Bill Collection Networks: Cisco XOT and RBP Solutions

Cisco XOT Features for Transporting CDR DataXOT 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-FrameIn 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 The Operations Systems Network Communications Protocol Specification (Publication 54001) calls for the I-Frame to be implemented only in a dialup or public environment. Although the billing hosts and the Class 5 telephone switches support the security I-Frame, the Cisco X.25 implementation does not. The Cisco network is typically a private enterprise, so Cisco customers must disable the I-Frame on the OSS and the Lucent 5ESS telephone switch. Cisco has validated that BX.25 can be transported directly over its networks using X.25, or over an IP infrastructure using X.25 over TCP (XOT) as defined in RFC 1613, once the I-Frames are disabled. These configurations have been successfully tested with both the Sterling 5000 Collector and the Lucent Billdats applications employing Cisco networks.

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 2-4 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 on page 2-109 for more information about filling in the cpblx3 form.)

Figure 2-4 Security Field from Lucent 5ESS cpblx3 Form

19. security: 19 security definition: check security information legal values: Y, N, Null default value: N


Chapter 2 Telephone Switch EnvironmentsX.25 and LAPB Parameters

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 ParametersX.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 2-1, Table 2-2, and Table 2-3. Sections following the table describe how to set these parameters for specific Cisco solutions.

Table 2-1 Cisco X.25 Packet-Setting Parameters

FunctionCisco IOS Commands

Default Value Usage Notes

Input window size

Output window size

x25 win

x25 wout

2 packets Window size is the default number of packets a VC can send before waiting for an X.25 acknowledgment.

Input packet size

Output packet size

x25 ips

x25 ops

128 packets

Input and output packet sizes must be set to the same value.

Window modulus x25 modulo modulo 8 Window modulus defines flow control with a sliding window sequence count. The window counter restarts at zero upon reaching the upper limit.

Lowest and highest incoming-only VC number

x25 lic

x25 hic

0 X.25 switch is configured for an incoming-only VC range, from the perspective of the DTE device. 0 = disabled.

Lowest and highest outgoing-only VC number

x25 loc

x25 hoc

0 X.25 switch is configured for an outgoing-only VC range, from the perspective of the DTE device. 0 = disabled.



Lowest two-way VC number

x25 ltc 1 X.25 switch is configured for a two-way VC range. Value must be larger than incoming-only range, and must come before any outgoing-only range.

Highest two-way VC number

x25 htc 1024

Table 2-2 Cisco X.25 Timer Definitions

FunctionCisco IOS Commands Default Usage Notes

T10 x25 t10 60 seconds DCE Restart Request timer

T11 x25 t11 180 seconds DCE Incoming Call timer

T12 x25 t12 60 seconds DCE Reset Indication timer

T13 x25 t13 60 seconds DCE Clear Indication timer

T20 x25 t20 180 seconds DTE Restart Request retransmission timer

T21 x25 t21 200 seconds DTE Call Request retransmission timer

T22 x25 t22 180 seconds DTE Reset Request retransmission timer

T23 x25 t23 180 seconds DTE Clear Request retransmission timer

Table 2-3 Cisco LAPB Timer Definitions


T1 labp t1 3000 milliseconds Retransmission timer; period ranges from 1 to 64,000 milliseconds (ms).

T2 labp t2 0 milliseconds (disabled) Explicit acknowledge deferral timer (length of time the DTE or DCE device has before acknowledging a frame).

T3 lapb interface-outage

0 milliseconds (disabled) Interface outage timer (length of time the interface can be down before the packet layer is notified of an outage); partial T3 timer functionality.

T4 lapb t4 0 milliseconds (disabled by default)

Idle link timer, after which the Cisco IOS software sends out a poll packet to determine whether the link has suffered an unsignaled failure. Any T4 value (except 0) must be greater than what is set for the LAPB T1 timer.

Table 2-1 Cisco X.25 Packet-Setting Parameters (continued)

FunctionCisco IOS Commands

Default Value Usage Notes



Configuring XOT on the Billing Collector Side of the NetworkFigure 2-3 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 2-5 shows what the CDR collection connection in Figure 2-3 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 2-5 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 2-5 and perform the following steps. See the “Sterling 5000 Collector Configuration: Examples” section on page 2-12 for configuration examples.

Step 1 Enter configuration mode:

Router-3631# configure terminal

N1 lapb n1 Maximum value for the interface

The maximum number of bits in a LAPB frame, which determines the maximum size of an X.25 packet. When LAPB is used over leased lines, the N1 parameter should be eight times the hardware maximum transmission unit (MTU) size plus any protocol overhead. The LAPB N1 range is dynamically calculated by the Cisco IOS software whenever an MTU change, a Layer 2 or Layer 3 modulo change, or a compression change occurs on a LAPB interface.

N2 lapb n2 20 transmissions Transmission count, or the maximum number of times a data frame can be transmitted.

K lapb k 7 frames The maximum permissible number of outstanding frames, called the window size.

Table 2-3 Cisco LAPB Timer Definitions


8235

5

IPcloud

BX.25 BX.25XOT

Cisco 3631

Serial 3/0, PVC1

Sterling 5000Collector

Cisco 3662

XOT

Class 4/5telephone switch

Serial 1/0, PVC1

X.25 over aTCP tunnel



Enter configuration commands, one per line. End with CNTL/Z.

Step 2 Start interface configuration mode for the serial interface connected to the Sterling 5000 Collector port. In the following steps, serial interface 3/0 is used, which specifies network module 3 and port 0 on the Cisco 3631 router connected to the Sterling 5000 Collector.

Router-3631(config)# interface serial 3/0

Step 3 Shut down the interface:

Router-3631(config-if)# shutdown

Step 4 Enter a description for the serial interface:

Router-3631(config-if)# description AMA Billing FE56

Step 5 Configure X.25 DCE encapsulation on the serial interface:

Router-3631(config-if)# encapsulation x25 dce

Step 6 Set the low two-way channel VC number to 5, which sets the PVC range from 1 to 4:

Router-3631(config-if)# x25 ltc 5

Step 7 Change the input window size (maximum unacknowledged X.25 packets) from the default of 2 to 7:

Router-3631(config-if)# x25 win 7

Step 8 Change the output window size (maximum unacknowledged X.25 packets) from the default of 2 to 7:

Router-3631(config-if)# x25 wout 7

Step 9 Change the maximum input packet size from the default of 128 to 512:

Router-3631(config-if)# x25 ips 512

Step 10 Change the maximum output packet size from the default of 128 to 512:

Router-3631(config-if)# x25 ops 512

Step 11 The system default is to force X.25 packet-level restarts when the link level resets. Disable this function with the no x25 linkrestart command:

Router-3631(config-if)# no x25 linkrestart

Step 12 Map the PVC across the TCP/IP network to the serial interface on the Cisco router connected to the Lucent 5ESS telephone switch. In the example for this step, PVC 1 from the Sterling 5000 Collector OSS is mapped to PVC 1 at serial interface 1/0 on the Cisco router, at IP address 172.30.109.48. Specify an X.25 input and output window size of 3 for this interface:

Router-3631(config-if)# x25 pvc 1 tunnel 172.30.109.48 interface serial 1/0 pvc 1 windowsize 3 3

Step 13 The router is functioning as a DCE device and must supply clock signaling to the DTE device. Set the clock rate to 56000 baud:

Router-3631(config-if)# clockrate 56000

Step 14 Restart the interface:

Router-3631(config-if)# no shutdown

Step 15 Exit the interface and global configuration modes:

Router-3631(config-if)# endRouter-3631(config)# end



Step 16 Copy the running configuration to the startup configuration. This step saves the configuration in nonvolatile memory so that it will be available the next time the router boots up:

Router-3631# copy run startDestination filename [startup-config]? Building configuration...[OK]

Configuring XOT on the Telephone Switch Side of the NetworkTo configure XOT on a Cisco 3662 edge router connected to a telephone switch, see Figure 2-5 and perform the following steps. See the “Sterling 5000 Collector Configuration: Examples” section on page 2-12 for configuration examples.


Router-3662# configure terminalEnter configuration commands, one per line. End with CNTL/Z.

Step 2 Start interface configuration mode for the serial interface connected to the Class 5 switch port. In this example, the port is a Lucent 5ESS telephone switch. In the following steps, serial interface 1/0 is used, which specifies network module 1 and port 0 on the Cisco 3662 router connected to the Lucent 5ESS:



Router-3662(config-if)# shutdown


Router-3662(config-if)# description AMA Billing 5ESS Lucent



Step 6 Set the low two-way channel VC number to 5, which sets the PVC range from 1 to 4:







Router-3662(config-if)# x25 ips 512


Router-3662(config-if)# x25 ops 512



Step 11 The system default is to force X.25 packet-level restarts when the link level resets. Disable this function with the no x25 linkrestart command:

Router-3662(config-if)# no x25 linkrestart

Step 12 Map the PVC across the TCP/IP network to the serial interface on the Cisco router connected to the Lucent 5ESS telephone switch:

Router-3662(config-if)# x25 pvc 1 xot 172.31.229.247 interface serial 3/0 pvc 1 xot-promiscuous window size 3 3




Router-3662(config-if)# no shutdown





Sterling 5000 Collector Configuration: Examples

This section provides examples of the following Sterling 5000 Collector configurations:

• Sterling 5000 Collector Polling a Lucent 5ESS Telephone Switch: Example, page 2-13

• Cisco 3631 Edge Router Connected to the Sterling 5000 Collector (Polling Lucent 5ESS Switch): Example, page 2-13

• Cisco 3662 Edge Router Connected to the Lucent 5ESS Telephone Switch: Example, page 2-14

• Sterling 5000 Collector Polling a Siemens EWSD Telephone Switch: Example, page 2-14

• Cisco 3631 Edge Router Connected to the Sterling 5000 Collector (Polling Siemens EWSD Switch): Example, page 2-14

• Cisco 3662 Edge Router Connected to the Siemens EWSD Telephone Switch: Example, page 2-15

• Sterling 5000 Collector Polling a Nortel DMS/DPP Telephone Switch: Example, page 2-16

• Cisco 3662 Edge Router Connected to the Nortel DMS/DPP Telephone Switch: Example, page 2-16

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 2-6) encapsulate the BX.25 packets.

Figure 2-6 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/1 description ip 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 FE56 no ip address! X.25 DCE encapsulation. encapsulation x25 dce no ip mroute-cache no 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 7 x25 wout 7! The maximum input and output packet size is changed from the default of 128 to 512. x25 ips 512 x25 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 3 x25 pvc 2 tunnel 172.30.115.120 interface Serial 1/0 pvc 1 windowsize 3 3 x25 pvc 3 tunnel 172.30.128.248 interface Serial 1/0 pvc 1 windowsize 3 3 x25 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 56000

8255

1

IPcloud

BX.25 BX.25XOT

Cisco 3631

Serial 3/0, PVC1

Sterling 5000Collector

Cisco 3662

XOT


Lucent 5ESS

Serial 1/0, PVC1

172.31.229.247Ethernet 2/1

172.30.109.48Ethernet 0/0



Cisco 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/0

description AMA Billing ip address 172.30.109.48 255.255.255.192 no ip directed-broadcast!interface Serial1/0 description AMA Billing 5ESS Lucent no ip address no ip directed-broadcast! X.25 DTE encapsulation.encapsulation x25 no 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 7 x25 wout 7! The maximum input and output packet size is changed from the default of 128 to 512. x25 ips 512 x25 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 56000

Sterling 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 2-7.

Figure 2-7 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.

8255

2

IPcloud

BX.25 BX.25XOT

Cisco 3631Sterling 5000Collector

Cisco 3662

XOT

Siemens EWSD

Serial 1/0, PVC2


Serial 0, PVC1

172.31.229.248Ethernet 0/1

172.30.113.184Ethernet 0



x25 routing!interface Ethernet0/1 description ip address 172.31.229.248 255.255.255.0 no logging event subif-link-status!interface Ethernet0/2 no ip address no logging event subif-link-status shutdown!interface Ethernet0/3 no ip address no logging event subif-link-status shutdown!interface Serial1/0 description AMA Billing FE56 no ip address encapsulation x25 dce no ip mroute-cache no logging event subif-link-status x25 ltc 5 x25 win 7 x25 wout 7 x25 ips 512 x25 ops 512 x25 pvc 1 tunnel 172.30.108.48 interface Serial 0 pvc 1 windowsize 3 3 x25 pvc 2 tunnel 172.30.113.184 interface Serial 0 pvc 1 windowsize 3 3 x25 pvc 3 tunnel 172.30.130.248 interface Serial 1/0 pvc 1 windowsize 3 3 x25 pvc 4 tunnel 172.30.114.248 interface Serial 0 pvc 1 windowsize 3 3 clockrate 56000

Cisco 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 Ethernet0 description ip address 172.30.113.184 255.255.255.192 no mop enabled!interface Serial0 description AMA Billing Siemens EWSD no ip address encapsulation x25 no ip mroute-cache x25 ltc 5 x25 win 7 x25 wout 7 x25 ips 512 x25 ops 512 no x25 linkrestart x25 pvc 1 tunnel 172.31.229.248 interface Serial 1/0 pvc 2 windowsize 3 3 clockrate 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 2-8) encapsulate the BX.25 packets.

Figure 2-8 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/0 description to Nortel DMS/DPP Port ip address 172.31.228.248 255.255.255.0 no logging event subif-link-status!interface Serial1/0 description AMA Billing FE56 no ip address encapsulation x25 dce no ip mroute-cache no logging event subif-link-status x25 ltc 5 x25 win 7 x25 wout 7 x25 ips 512 x25 ops 512 x25 pvc 1 tunnel 172.30.108.48 interface Serial 0 pvc 1 windowsize 3 3 x25 pvc 3 tunnel 172.30.130.248 interface Serial 1/0 pvc 1 windowsize 3 3 x25 pvc 4 tunnel 172.30.114.248 interface Serial 0 pvc 1 windowsize 3 3 clockrate 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 Ethernet0 description - to DCN Bay RR 261.6 Hub ip address 172.30.108.48 255.255.255.192 no ip redirects

8255

3

IPcloud

BX.25 BX.25XOT

Cisco 3631Sterling 5000Collector

Cisco 3662

XOT

Nortel DMS/DPP

Serial 1/0, PVC1


Serial 0, PVC1

172.31.228.248Ethernet 0/0

172.30.108.48Ethernet 0



no mop enabled!interface Serial0 description AMA Billing DPP Nortel no ip address encapsulation x25 no ip mroute-cache x25 ltc 2 x25 win 7 x25 wout 7 x25 ips 512 x25 ops 512 x25 pvc 1 tunnel 172.31.228.248 interface Serial 1/0 pvc 1 windowsize 3 3 clockrate 56000

Configuring a Cisco Router for a Host That Supports XOTExamples 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 2-9).

Figure 2-9 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 2-9 and perform the following steps. See the “Mercury Mediation Bill Collector That Supports XOT: Example” section on page 2-19 for a configuration example. See the “Verifying the SVC Connection on the Mercury Mediation Device” section on page 2-19 for a verification example.

Step 1 Verify that you are running Cisco IOS Release 12.1(16) or a later software release that supports telco DCN functions:

Router-B# show version


Router-B# configure terminalEnter configuration commands, one per line. End with CNTL/Z.

8235

6

IPcloud

MercuryMediation

Router BLucent 5ESS

X.25

X.25 over a TCP tunnel

XOT

Serial 1/2, PVC1

SVC-to-PVCconversion



Step 3 Enable X.25 routing:

Router-B(config)# x25 routing

Step 4 Start interface configuration mode for serial interface 1/2, which specifies network module 1, port 2:

Router-B(config)# interface serial 1/2


Router-B(config-if)# shutdown


Router-B(config-if)# description AMA connection to Lucent 5ESS switch

Step 7 Configure the address for the X.25 serial interface:

Router-B(config-if)# x25 address 5555550137


Router-B(config-if)# encapsulation x25 dce


Router-B(config-if)# x25 win 3


Router-B(config-if)# x25 wout 3

Step 11 Change the maximum input X.25 packet size from the default of 128 to 512:

Router-B(config-if)# x25 ips 512

Step 12 Change the maximum output X.25 packet size from the default of 128 to 512:

Router-B(config-if)# x25 ops 512


Router-B(config-if)# clockrate 56000

Step 14 The LAPB N1 parameter sets the maximum bits per frame. Set this timer to 4152:

Router-B(config-if)# lapb N1 4152

Step 15 The X.25 SVC call to destination 5555550137 is converted to PVC 1. The call must be from address 5555550140. Specify the PVC-to-SVC conversion, an X.25 packet size of 512, and input and output window sizes of 3:

Router-B(config-if)# x25 pvc 1 svc 5555550140 packetsize 512 512 windowsize 3 3

Step 16 Enable monitoring of the LL pin for DCE mode:

Router-B(config-if)# no ignore-hw local-loopback

Step 17 Disable fast switching of IP multicast:

Router-B(config-if)# no ip mroute-cache

Step 18 Disable IP addressing:

Router-B(config-if)# no ip address




Router-B(config-if)# no shutdown

Step 20 Exit interface configuration mode:

Router-B(config-if)# end

Step 21 Create an entry in the X.25 routing table to map incoming X.25 calls with the destination address 5555550137 to serial interface 1/2:

Router-B(config)# x25 route 5555550137 interface serial 1/2

Step 22 Create an entry in the X.25 routing table to map an outgoing call from the Lucent 5ESS telephone switch to the host application. The X.121 destination address of the host is 5555550140:

Router-B(config)# x25 route 5555550140 xot 192.168.3.20

Step 23 Exit global configuration mode:

Router-B(config)# end


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 2-9.

interface Serial1/2 description AMA connection to Lucent 5ESS switch no ip address encapsulation x25 dce no ip mroute-cache x25 address 5555550137 x25 win 3 x25 wout 3 x25 ips 512 x25 ops 512 x25 pvc 1 svc 5555550140 packetsize 512 512 windowsize 3 3 no ignore-hw local-loopback clockrate 56000 lapb N1 4152!x25 route 5555550137 interface Serial1/2x25 route 5555550140 xot 192.168.3.20

Verifying 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 vc

PVC 1, State: D1, Interface: Serial1/2 Started 01:13:53, last input 00:00:06, output 00:00:06 Connects 5555550140 <--> 5555550137 from XOT between 10.129.48.4, 1998 and 192.168.3.20, 1833 Window size input: 3, output: 3 Packet size input: 512, output: 512 PS: 0 PR: 1 ACK: 1 Remote PR: 0 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data 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:06 Connects 5555550140 <--> 5555550137 from Serial1/2 PVC 1 Window size input: 3, output: 3 Packet size input: 512, output: 512 PS: 1 PR: 0 ACK: 0 Remote PR: 1 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 153651/179 packets 305/24 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0

Cisco RBP and RBP Q-Bit Features for Transporting CDR DataThe 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 on page 2-80 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 on page 2-80 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


http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a008045552b.html

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftdcnrbp.pdf


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:

• Bellcore 385 AMATPS

• Nortel XFER

• MNP

• MTP

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 on page 2-33 for more information about configuring the Inter-mediatE application.

Configuring a Cisco Router for a CDR Host That Supports the RBP FeatureThe RBP solution implements TCP/IP from the Inter-mediatE host to an access router in the central office. Figure 2-10 shows a network with RBP configured on a Lucent 5ESS. RBP is transporting Bellcore 385 AMATPS-formatted data.

Figure 2-10 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 on page 2-6.”

Lucent 5ESSRouter A10

3759

TCP/IP to BX25mediation

IP

BX25 PVCsRBP session over TCP/IP

Inter-mediatE



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 2-10 and perform the following steps. See the “Cisco X.25 RBP with the Inter-mediatE to a Lucent 5ESS Switch: Example” section on page 2-23 and “Cisco X.25 RBP with the Inter-mediatE to a Nortel DMS 100 Switch: Example” section on page 2-23 for configuration examples.

Step 1 Verify that you are running Cisco IOS Release 12.2(8)T or later software that supports telco DCN functions and the Cisco X.25 RBP feature:

Router-A# show version

Step 2 Enter global configuration mode:

Router-A# configure terminal


Step 3 Configure the loopback interface:

Router-A(config)# interface Loopback0Router-A(config-if)# ip address 10.60.128.8 255.255.255.255Router-A(config-if)# end


Router-A(config)# x25 routing

Step 5 Select the serial interface that is connected to the Billing port on the Lucent 5ESS. In the example, serial interface 1/0 is used, which specifies network module 1, port 0:

Router-A(config)# interface serial 1/0


Router-A(config-if)# shutdown

Step 7 Supply a description for the serial interface:

Router-A(config-if)# description Collection of Call Detail Records port


Router-A(config-if)# encapsulation x25 dce

Step 9 Set the lowest outgoing channel to 4:

Router-A(config-if)# x25 loc 4

Step 10 Set the X.25 threshold to 1. This command instructs the router to send acknowledgment packets when the router is not busy sending other packets, even if the number of input packets has not reached the input window size count:

Router-A(config-if)# x25 threshold 1


Router-A(config-if)# x25 ips 512


Router-A(config-if)# x25 ops 512



Step 13 Enable the RBP feature on the router. The Inter-mediatE application requires one PVC. The PVC range is from 1 through 3. Because the low two-way channel was set to 4 with the x25 loc 4 command in an earlier step, PVC 1 is mapped to TCP port 10000. The TCP port was chosen arbitrarily:

Router-A(config-if)# x25 pvc 1 rbp local port 10000

Step 14 The router is functioning as a DCE device. The DCE must supply clock signaling to the DTE device, which is the billing port on the switch. Set the clock rate to 56000 baud:

Router-A(config-if)# clockrate 56000


Router-A(config-if)# no shutdown


Router-A(config-if)# endRouter-A(config)# end


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/0 no ip address encapsulation x25 dce no ip mroute-cache x25 ltc 4 x25 ips 512 x25 ops 512 x25 pvc 1 rbp local port 10000 clockrate 56000

Cisco 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/0 no ip address encapsulation x25 dce no ip mroute-cache x25 ltc 4 x25 ips 512 x25 ops 512 x25 pvc 1 rbp local port 10000 x25 map rbp 00006300 cud 0xB0 local port 20000 clockrate 56000



Configuring the Cisco X.25 RBP Q-Bit Feature for the MTP File TypeThe 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:

• Ericsson AXE-10

• Ericsson AXE-10 International

• Global System for Mobile Telecommunications mobile switching center (MSC GSM)

The configuration shown in Figure 2-11 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 2-11 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 2-11 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 on page 2-25 for a configuration example. See the “Debugging Cisco X.25 RBP” section on page 2-28 for debugging examples.




Router-A# configure terminalEnter configuration commands, one per line. End with CNTL/Z.





TCP/IP-to-X.25 mediation

Class 5telephone switch

Cisco 2651XMB

IP

RBP session over TCP/IP X.25 SVC

2312

30

Inter-mediatE



Step 5 Select the serial interface that is connected to the billing port on the Lucent 5ESS. In the example, serial interface 1/0 is used, which specifies network module 1, port 0:










Step 10 Enable the RBP feature on the router. The Inter-mediatE application requires one SVC. The PVC range is from 1 to 3 because the low two-way channel was set to 4 with the x25 loc 4 command in an earlier step. The SVC range is from 4 to 1024. The router will be calling a destination X.121 address of 3178650503. A calling address is not assigned on this serial interface, so the source address is 0. TCP port 30010 was chosen arbitrarily. The q-bit keyword was added to the command, to identify that the header will support the Q-bit:

Router-A(config-if)# x25 map rbp 3178650503 local port 30010 q-bit









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 2-11 on page 2-24 shows the physical configuration.

interface Serial0/1 description X.25 RBP+Q Inter-mediatE no ip address encapsulation x25 dce



x25 ltc 4 x25 map rbp 3178650503 local port 30010 q-bit clock rate 56000

Configuring the Cisco X.25 RBP Q-Bit Feature for the MNP File TypeThe 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 2-12 is a test setup for MNP file type retrieval.

Figure 2-12 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 2-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 MNP File Type: Example” section on page 2-27 for a configuration example. See the “Debugging Cisco X.25 RBP” section on page 2-28 for debugging examples.




Router-A# configure terminal






Step 5 Select the serial interface that is connected to the billing port on the Lucent 5ESS. In the example, serial interface 1/0 is used, which specifies network module 1, port 0:


TCP/IP-to-BX.25 mediation

Class 5telephone switch

Cisco 2651XMB

IP

RBP session over TCP/IP BX.25 SVC

2312

31

Inter-mediatE











Step 10 Enable the RBP feature on the router. The Inter-mediatE application requires one SVC. The PVC range is from 1 to 3 because the low two-way channel was set to 4 with the x25 loc 4 command in an earlier step. The SVC range is from 4 to 1024. The router will be calling a destination X.121 address of 3178650503. A calling address is not assigned on this serial interface, so the source address is 0. TCP port 30010 was chosen arbitrarily. The q-bit keyword was added to identify that the header will support the Q-bit:

Router-A(config-if)# x25 map rbp 3178650503 local port 30010 q-bit









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 2-12 on page 2-26 shows the physical configuration.

interface Serial0/1 description X.25 RBP+Q Inter-mediatE no ip address encapsulation x25 dce x25 ltc 4 x25 map rbp 3178650503 local port 30010 q-bit clock rate 56000!



Debugging Cisco X.25 RBPThis section contains the following procedures that are useful for debugging RBP:

• Debugging a TCP/IP Connection, page 2-28

• Debugging an X.25 Serial Connection, page 2-29

• Debugging the RBP Configuration, page 2-32

The debugging examples in this section are based on the previous configuration example. The test network is shown in Figure 2-12 on page 2-26.

Caution Enabling debugging can severely degrade performance of the router. Cisco strongly recommends that debugging be done in a lab and not in a production network.

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 on page 2-27 and Figure 2-12 on page 2-26, 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 If you are logged in remotely, enable monitoring of the debug output using the terminal monitor command:

2651XMB# terminal monitor

Step 2 Enter the debug x25 all command to enable all traffic debugging for X.25:

2651XMB# debug x25 allX.25 packet debugging is on

Step 3 (Optional) To enable X.25 data display of the data in the X.25 packets, enter the debug x25 dump command:

2651XMB# debug x25 dumpX.25 packet debugging is onX.25 packet dump debugging is on

Step 4 Enable the debug ip packet command to debug the TCP/IP connection between the Inter-mediatE application and the Cisco 2651XMB router:

2651XMB# debug ip packet

IP packet debugging is on



Tip An alternative to this step is to enable the debug ip packet dump detail command.

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 51608

Output 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 4 0: 10040F ...

Step 5 Disable all debug commands when you are done.

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 If you are logged in remotely, enable monitoring of the debug output using the terminal monitor command:

2651XMB# terminal monitor

Step 2 Enter the debug x25 all command to enable all traffic debugging for X.25:

2651XMB# debug x25 allX.25 packet debugging is on



Step 3 (Optional) To enable X.25 data display of the data in the X.25 packets, enter the debug x25 dump command:

2651XMB# debug x25 dumpX.25 packet debugging is onX.25 packet dump debugging is on

The 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 0 0: 900B00 03650054 5446494C ....e.TTFIL 11: 452D3030 30310000 00000000 00000000 E-0001.......... 27: 00000000 00000000 000000 ........... *May 24 05:16:07.658: X25 RBP: Q-bit received in X25 data packet

Output 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 record

Output 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 1 0: 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 1 0: 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 1 0: 900B22 00A2 .."." *May 24 05:16:12.109: X25 RBP: Q-bit received in X25 data packet

Output 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 record

Output 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 2 0: 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 2 0: 100B41 ..A

Output 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 2 0: 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 2 0: 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 4 0: 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 2 0: 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 Not all of the file transfer data is displayed.

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 transfer

Output 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 ....z



Output 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 5 0: 100BA1 ..! *May 24 05:16:31.889: Serial0/1: X.25 I R1 Clear Confirm (3) 8 lci 11 0: 100B17 ...

Step 4 Disable all commands when you are done.

Debugging the RBP Configuration

The following examples show the router configuration followed by the debug x25 all command output.

Router Configurationinterface 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 10000 no 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 1

Configuring an Intec Telecom Systems Inter-mediatE SystemIntec’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 The Portal tab is the first one on the left. If the Portal parameters are not displayed, click the Portal tab.

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 2-13).



Figure 2-13 Portal Window

Step 2 Define the Plug-in to be a protocol-to-file type mapping that supports data collection using RBP. Choose a value from the drop-down menu.

Step 3 The Business Logic Name maps mediation processing rules to the data. Choose a value from the Business Logic Name drop-down menu for the system to collect.

Step 4 From the Portal window, click the File Naming tab. Use the File Naming window to choose file types (see Figure 2-14).



Figure 2-14 File Naming Window

Choices displayed on the File Naming window depend upon the collection protocol chosen on the Portal window. In Figure 2-13, 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 From the File Naming window, click the Routing tab. Use the Routing window (see Figure 2-15) to enter the host name or IP address of the router and the TCP socket number that RBP is configured on.



Figure 2-15 Routing Window

Choices displayed on the Routing window depend upon the collection protocol chosen on the Portal window. In Figure 2-13, Bellcore 385 (AMATPS) and RBP were chosen, so parameters for configuring Bellcore 385 are entered here.

Step 6 In the Route1 tab, enter the host name or IP address of the router in the Host Name/Address field.

Step 7 In the Port Number field, enter the TCP socket port number that RBP is configured on.

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 From the Routing window, click the Protocol tab. Use the Protocol window (see Figure 2-16) to define the protocols that ride on top of RBP.



Figure 2-16 Protocol Window

Choices displayed on the Protocol window depend upon the collection protocol chosen on the Portal window. In Figure 2-13, Bellcore 385 (AMATPS) and RBP were chosen, so parameters for configuring Bellcore 385 are entered here.

Note CUD is not required in the Call User Data field. The system uses 0xC0 by default.

Tip Click the Help tool in the upper right hand corner of the window to understand what is required in each field. The Help tool provides descriptions of the supported protocols, and hardware tips and suggestions for many of the available settings.


Chapter 2 Telephone Switch EnvironmentsSwitch Monitoring Networks: Cisco STUN OSS Connectivity Solution

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 2-17.

Figure 2-17 Legacy Switch Monitoring Connections

The solutions are described in the following sections:

• Switch Monitoring Overview, page 2-38

• The Lucent Datakit Network, page 2-40

• Migrating to TCP/IP Using Cisco STUN, page 2-40

• Configuring STUN on the Workstation Side of the Network, page 2-42

• Configuring STUN on the Telephone Switch Side of the Network, page 2-44

Switch Monitoring OverviewOne 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 2-20 on page 2-41, 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 2-18 on page 2-40 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

8256

2

Lucent 5ESS


Monitoring

Provisioning

Datakit node

EDAS

EchoBack

SCC0

SCC1

Traffic engineering

X.25

Datakitbackbone

COSAM

Datakit node


ModemsModems



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.

• PVC 1: Emergency Action Interface (EAI) information

• PVC 2: Summary status data (headers) for alarms (HDR)

• PVC 3: Controls the display of the page (Alarm)

• PVC 4: TTY input (Admin)

• PVC 5: TTY output (logging or maintenance channel, MTC)

• PVC 6: TTY input (Admin 2)

• PVC 7: TTY output (MTC 2)

• PVC 8: TTY input

• PVC 9: TTY output

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=Good Record #10 (EQ) Captured on 04.19.01 at 19:15:34.698811606 Length = 4LAPB: Address = 001 Frame 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 = 4

The 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 2-18).



Figure 2-18 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 NetworkA typical Datakit network is shown in Figure 2-19.

Figure 2-19 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 STUNThe 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.

8235

7

Fiber link

Datakitnode

SCC1

SCC0

SCC1

SCC0

Dedicatedcircuits

BX.25/X.25 Lucent 5ESS

EIA/TIA-232cables

Network management

application

8235

8

Sam 64Sam 16

Fiber link

Datakitnode

SCC1SCC1

Proprietarytrunk SCC0

SLM cards

BX.25SCC0

Lucent 5ESS

EIA/TIA-232cables

Network management

application



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 2-20 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 2-20 Lucent NFM Connection to a Lucent 5ESS Switch Using STUN

Each STUN tunnel is connected to separate physical interfaces. In Figure 2-20, 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 2-21). As with the configuration seen in Figure 2-20, 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 2-21, 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 2-21 NFM/EMM with Cisco STUN Solution

8235

9Fiber link

Datakitnode

SCC1SCC1

EIA/TIA-232

STUN tunnel 2

SCC0

SLM cards

SCC0

Lucent 5ESS

STUN tunnel 1

IP cloud

NFM

8236

0

SCC1 Cisco 2611 Cisco 3640R1

SCC0

3B215ESS

STUN tunnel group 101


EMMworkstation

SCC1

SCC0

NFM

10.10.10.2Ethernet 0/0

10.10.10.1Ethernet 0/0

Serial 1/2

Serial 1/3Serial 1/3

Serial 1/2



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 NetworkTo configure the STUN tunnel on the workstation side of the telco DCN, see Figure 2-21 and perform the following steps. See the “Cisco STUN OSS Connectivity Solution: Examples” section on page 2-46 for a configuration example. See the “Verifying Links in the Cisco STUN OSS Connectivity Solution” section on page 2-48 for verification examples. See the “Debugging STUN Connections” section on page 2-49 for debugging examples.


Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#

Step 2 Define the host name:

Router(config)# hostname Router-2611

Step 3 Configure the STUN global settings. The peer name is mapped to the IP address of the Ethernet interface on Router-2611 with the stun peer-name command, which also enables further STUN configuration. After using this command, define the protocol group in which you want to place this interface with the stun protocol-group command. In later steps, you will enable STUN encapsulation on the interface using the encapsulation stun command, and then place the interface in a STUN group with the stun group command:

Router-2611(config)# stun peer-name 10.10.10.2Router-2611(config)# stun protocol-group 101 basicRouter-2611(config)# stun protocol-group 102 basic

Configure the Ethernet Interface

Step 4 Start interface configuration mode for Ethernet interface 0/0:

Router-2611(config)# interface ethernet 0/0

Step 5 Configure the IP addresses for the interface:

Router-2611(config-if)# ip address 10.10.10.2 255.255.255.0

Step 6 Disable keepalives. This action prevents the tunnel from being dropped if the protocol goes down on the Ethernet interface:

Router-2611(config)# no keepalive

Tip An alternative to this step is to use the loopback interface.

Step 7 For this configuration, set the interface to half-duplex mode:

Router-2611(config)# half-duplex




Router-2611(config-if)# end

Configure Serial Interface 1/2



Step 10 Disable IP addresses on the interface:

Router-2611(config-if)# no ip address

Step 11 Configure STUN encapsulation:

Router-2611(config-if)# encapsulation stun



Step 13 Assign the interface to STUN group 101:

Router-2611(config-if)# stun group 101

Step 14 Route all traffic arriving on serial interface 1/2 to Router-3640R1 at IP address 10.10.10.1 (see Figure 2-21 on page 2-41):

Router-2611(config-if)# stun route all tcp 10.10.10.1









Router-2611(config-if)# encapsulation stun




Router-2611(config-if)# stun group 102

Step 21 Route all traffic arriving on serial interface 1/3 to Router-3640R1 at IP address 10.10.10.1 (see Figure 2-21 on page 2-41):

Router-2611(config-if)# stun route all tcp 10.10.10.1







Configuring STUN on the Telephone Switch Side of the NetworkTo configure the STUN tunnel on the telephone switch side of the telco DCN, see Figure 2-21 on page 2-41 and perform the following steps. See the “Cisco STUN OSS Connectivity Solution: Examples” section on page 2-46 for configuration examples. See the “Verifying Links in the Cisco STUN OSS Connectivity Solution” section on page 2-48 for verification examples. See the “Debugging STUN Connections” section on page 2-49 for debugging examples.


Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#

Step 2 Define the host name:

Router(config)# hostname Router-3640R1

Step 3 Configure the STUN global settings. The peer name is mapped to the IP address of the Ethernet interface on Router-3640R1 with the stun peer-name command, which also enables further STUN configuration. After using this command, define the protocol group in which you want to place this interface with the stun protocol-group command. In later steps, you will enable STUN encapsulation on the interface using the encapsulation stun command, and then place the interface in a STUN group with the stun group command:

Router-3640R1(config)# stun peer-name 10.10.10.1Router-3640R1(config)# stun protocol-group 101 basicRouter-3640R1(config)# stun protocol-group 102 basic

Configure the Ethernet Interface

Step 4 Start interface configuration mode for Ethernet interface 0/0:

Router-3640R1(config)# interface ethernet 0/0

Step 5 Configure the IP addresses for the interface:

Router-3640R1(config-if)# ip address 10.10.10.2 255.255.255.0

Step 6 For this configuration, set the interface to half-duplex mode:

Router-3640R1(config-if)# half-duplex


Router-3640R1(config-if)# end





Router-3640R1(config)# interface serial 1/2


Router-3640R1(config-if)# no ip address


Router-3640R1(config-if)# encapsulation stun

Step 11 Set the clock rate to 9600 baud:

Router-3640R1(config-if)# clockrate 9600


Router-3640R1(config-if)# stun group 101

Step 13 Route all traffic arriving on serial interface 1/2 to Router-2611 at IP address 10.10.10.2 (see Figure 2-21 on page 2-41):

Router-3640R1(config-if)# stun route all tcp 10.10.10.2


Router-3640R1(config-if)# end



Router-3640R1(config)# interface serial 1/3


Router-3640R1(config-if)# no ip address


Router-3640R1(config-if)# encapsulation stun


Router-3640R1(config-if)# clockrate 9600


Router-3640R1(config-if)# stun group 102

Step 20 Route all traffic arriving on serial interface 1/3 to Router-2611 at IP address 10.10.10.2 (see Figure 2-21 on page 2-41):

Router-3640R1(config-if)# stun route all tcp 10.10.10.2


Router-3640R1(config-if)# endRouter-3640R1(config)# end


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:

• Cisco 2611 Edge Router STUN Connection to the Workstation: Example, page 2-46

• Cisco 3640R1 Edge Router STUN Connection to the Telephone Switch: Example, page 2-47

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 2-22.

Figure 2-22 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 EMM Version 6.2 was tested. Earlier versions are not recommended.

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!

8236

0

SCC1 Cisco 2611 Cisco 3640R1

SCC0

3B215ESS



EMMworkstation

SCC1

SCC0

NFM

10.10.10.2Ethernet 0/0

10.10.10.1Ethernet 0/0

Serial 1/2


Serial 1/2



stun peer-name 10.10.10.2stun protocol-group 101 basicstun protocol-group 102 basic!interface Ethernet0/0 ip address 10.10.10.2 255.255.255.0 no keepalive half-duplex!interface Serial1/2 no ip address encapsulation stun clockrate 9600 stun group 101 stun route all tcp 10.10.10.1!interface Serial1/3 no ip address encapsulation stun clockrate 9600 stun group 102 stun route all tcp 10.0.10.1

Cisco 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/0 ip address 10.10.10.1 255.255.255.0 half-duplex tarp enable!interface Serial1/2 no ip address encapsulation stun clockrate 9600 stun group 101 stun route all tcp 10.10.10.2!interface Serial1/3 no ip address encapsulation stun clockrate 9600 stun group 102 stun route all tcp 10.10.10.2



Verifying 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/2

Serial1/2 is up, line protocol is up Hardware is CD2430 in sync mode MTU 2104 bytes, BW 128 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation STUN, loopback not set Last input 00:00:02, output 00:00:40, output hang never Last clearing of "show interface" counters 00:20:56 Queueing strategy: fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 155 packets input, 316 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 9 packets output, 43 bytes, 0 underruns 0 output errors, 0 collisions, 2 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up

Router-3640R1# show interface serial 1/3

Serial1/3 is up, line protocol is up Hardware is CD2430 in sync mode MTU 2104 bytes, BW 128 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation STUN, loopback not set Last input 00:00:00, output 00:00:00, output hang never Last clearing of "show interface" counters 00:21:00 Queueing strategy: fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops 5 minute input rate 0 bits/sec, 1 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 527 packets input, 3295 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 77 packets output, 275 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out 4 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up

Use 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 stun

This peer: 10.10.10.1 *Serial1/2 -- scc0 (group 101 [basic]) state rx_pkts tx_pkts drops all TCP 10.10.10.2 open 1042 1025 0 Serial1/3 -- scc1 on 5ESS (group 102 [basic]) state rx_pkts tx_pkts drops all TCP 10.10.10.2 open 318 1013 83

Debugging 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 status packet All STUN activity tg Display stun transmission groups

To 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 packet

STUN 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: 0141

Following are detailed descriptions of the first two packets from the debug report:

00:40:01: STUN basic: 00:06:16 Serial1/2 NDI: Data: 0343

STUN 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 Network

00:40:01: STUN basic: 00:00:00 Serial1/2 SDI: Data: 030f


Chapter 2 Telephone Switch EnvironmentsSwitch Monitoring Networks: Cisco X.25 BAI OSS Connectivity Solution

STUN 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 Link

Switch 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, page 2-50

• Adding Cisco X.25 BAI to the Telco DCN, page 2-51

• Configuring Cisco X.25 BAI on the NMA Side of the Network, page 2-52

• Configuring Cisco X.25 BAI on the Telephone Switch Side of the Network, page 2-58

• Configuring SCC0 and SCC1 on the Lucent 5ESS Telephone Switch Form, page 2-66

• Switch Monitoring Networks: IP and Cisco X.25 BAI and EOR Solutions, page 2-69

Cisco X.25 BAI OSS Connectivity OverviewOne 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 2-23, 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 2-23 Network Management Application Monitors Lucent 5ESS Switch over Datakit

Network

Fiberlink

Datakitnode

SCC1

BX.25SCC0

BX.25SCC0

Proprietary trunk

Sam 16Sam 64

SCC1

6256

5

EIA/TIA-232cables

Lucent 5ESSNetwork management

application



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 2-24 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 2-24 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 DCNThe 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 2-24, 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.

8255

4X.25 SVC XOT X.25 PVCRedundant serial port

X.25 SVC-to-PVCconversion

X.25SCC 0

SCC 1IP cloud

NMA Cisco 3631

Serial 1/1

Cisco 3662

10.60.128.8

Lucent 5ESS




Configuring Cisco X.25 BAI on the NMA Side of the NetworkTo configure a backup active interface on the NMA side of the telco DCN, see Figure 2-24 and perform the following steps. See the “NMA Gateway Configuration: Example” section on page 2-53 and “NMA-Side Configuration: Example” section on page 2-54 for configuration examples. See the “Verifying Address Substitutions” section on page 2-54 for verification examples.




Router-3631(config)# x25 routing







Step 6 Disable fast switching of IP multicast:

Router-3631(config-if)# no ip mroute-cache

Step 7 Set the X.25 version to 1980 using the x25 version 1980 hidden command:

Router-3631(config-if)# x25 version 1980

Step 8 Set the high two-way channel to 64 so that the SVC range will be from 1 to 64, and will match the OSS:

Router-3631(config-if)# x25 htc 64





Step 11 Configure the XOT route and address substitution for SVC 1:

Router-3631(config-if)# x25 route 5550427111101 source 5550427222200 substitute-dest 5550427111100 substitute-source 5550427222201 xot 10.60.128.8



















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: standard device name: %nmasp1#j1g08061 asgnd module: %nmasp1#m1 gateway stat: enable local address: 5550427222200 station type: dte network type: standard min lcn: 1 baud: 9600 max lcn: 64 def thru class: 75 def window size: 4 max packet size: 128 ack window size: 4 def packet size: 128 num pvc: 0 flow control neg: no pvc origin: 1 thruput neg: no defer_dsl: yes lap t1: 3 fast select: no lap t2: 0 facility marker: no chanloopback: no lap n2: 20 sys err: yestrace: no lap K: 7 ignore D bit: no chantrace: no



The 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: switch channel id: admin platform: vos alt class: target model: 5ess_admin surveil mode: direct chan status: connect monitor timer: 0always channel type: raw msg log: yes target group: ne user id: ne password: * init script: no deactivation script: no

protocol: native x25_svc parity: no line type: non_dial cls user grp: gateway name: j1g08061 call address: 5550427111104

NMA-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/1 no ip address encapsulation x25 dce no ip mroute-cache x25 version 1980 x25 htc 64 x25 win 4 x25 wout 4 clockrate 56000

Verifying 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 2-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.8

To verify the X.121 address substitutions, perform the following steps:

Step 1 Enter the show x25 route EXEC command to list the X.25 route table and the address substitution shown in Table 2-4. The following example shows a sample X.25 route table:

Router# show x25 route

# Match Substitute Route to 1 dest 5550427111101 source 5550427222200 Sub-dest 5550427111100 Sub-source 5550427222201 xot 10.60.128.8 2 dest 5550427111102 source 5550427222200 Sub-dest 5550427111100 Sub-source 5550427222202 xot 10.60.128.8 3 dest 5550427111103 source 5550427222200 Sub-dest 5550427111100

Table 2-4 X.121 Address Substitution

NMA Calling Address

NMA Called Address

Substituted Calling Address

Substituted Called Address

PVC Channel Description

5550427222200 5550427111101 5550427222201 5550427111100 1 EIA

5550427222200 5550427111102 5550427222202 5550427111100 2 Alarm

5550427222200 5550427111103 5550427222203 5550427111100 3 Header

5550427222200 5550427111104 5550427222204 5550427111100 4 MTC

5550427222200 5550427111105 5550427222205 5550427111100 5 Admin

5550427222200 5550427111106 5550427222206 5550427111100 6 MTC2

5550427222200 5550427111107 5550427222207 5550427111100 7 Admin2



Sub-source 5550427222203 xot 10.60.128.8 4 dest 5550427111104 source 5550427222200 Sub-dest 5550427111100 Sub-source 5550427222204 xot 10.60.128.8 5 dest 5550427111105 source 5550427222200 Sub-dest 5550427111100 Sub-source 5550427222205 xot 10.60.128.8 6 dest 5550427111106 source 5550427222200 Sub-dest 5550427111100 Sub-source 5550427222206 xot 10.60.128.8 7 dest 5550427111107 source 5550427222200 Sub-dest 5550427111100 Sub-source 5550427222207 xot 10.60.128.8

Step 2 Enter the show x25 vc EXEC command to display the state of the X.25 SVCs and what the SVCs are connected to. The following example shows a typical report:

Router# show x25 vc

SVC 58, State: D1, Interface: Serial1/1 Started 00:15:54, last input 00:15:37, output 00:00:03 Connects 5550427222205 <--> 5550427111100 to XOT between 10.59.251.66, 11102 and 10.60.128.8, 1998 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 5 PR: 0 ACK: 0 Remote PR: 5 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 111340/2 packets 1021/2 Resets 1/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 59, State: D1, Interface: Serial1/1 Started 00:15:57, last input 00:15:40, output 00:00:58 Connects 5550427222203 <--> 5550427111100 to XOT between 10.59.251.66, 11101 and 10.60.128.8, 1998 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 5 PR: 3 ACK: 3 Remote PR: 5 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 1130/4 packets 13/3 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 60, State: D1, Interface: Serial1/1 Started 00:15:57, last input 00:15:39, output 00:00:58 Connects 5550427222202 <--> 5550427111100 to XOT between 10.59.251.66, 11100 and 10.60.128.8, 1998 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 2 PR: 2 ACK: 0 Remote PR: 2 RCNT: 2 RNR: Tx P/D state timeouts: 0 timer (secs): 0 data bytes 680/2 packets 10/2 Resets 0/0 RNRs 7/0 REJs 0/0 INTs 0/0SVC 61, State: D1, Interface: Serial1/1 Started 00:15:59, last input 00:15:14, output 00:00:00 Connects 5550427222201 <--> 5550427111100 to XOT between 10.59.251.66, 11099 and 10.60.128.8, 1998 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 2 PR: 0 ACK: 0 Remote PR: 2 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 9000/10 packets 450/6 Resets 2/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 62, State: D1, Interface: Serial1/1 Started 00:15:59, last input 00:15:36, output 00:15:38 Connects 5550427222207 <--> 5550427111100 to XOT between 10.59.251.66, 11098 and 10.60.128.8, 1998



Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 1 PR: 2 ACK: 2 Remote PR: 1 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 103/2 packets 1/2 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 63, State: D1, Interface: Serial1/1 Started 00:16:01, last input 00:12:18, output 00:12:16 Connects 5550427222204 <--> 5550427111100 to XOT between 10.59.251.66, 11097 and 10.60.128.8, 1998 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 6 PR: 7 ACK: 7 Remote PR: 6 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 224/13 packets 14/7 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0SVC 64, State: D1, Interface: Serial1/1 Started 00:16:01, last input 00:15:37, output 00:15:37 Connects 5550427222206 <--> 5550427111100 to XOT between 10.59.251.66, 11096 and 10.60.128.8, 1998 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 6 PR: 3 ACK: 3 Remote PR: 6 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data 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:37 Connects 5550427222206 <--> 5550427111100 from Serial1/1 SVC 64 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 3 PR: 6 ACK: 6 Remote PR: 3 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data 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:18 Connects 5550427222204 <--> 5550427111100 from Serial1/1 SVC 63 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 7 PR: 6 ACK: 6 Remote PR: 7 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data 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:36 Connects 5550427222207 <--> 5550427111100 from Serial1/1 SVC 62 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 2 PR: 1 ACK: 1 Remote PR: 2 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data 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:15 Connects 5550427222201 <--> 5550427111100 from Serial1/1 SVC 61 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 0 PR: 2 ACK: 2 Remote PR: 0 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data 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:40 Connects 5550427222202 <--> 5550427111100 from Serial1/1 SVC 60 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 2 PR: 2 ACK: 2 Remote PR: 0 RCNT: 0 RNR: Rx P/D state timeouts: 0 timer (secs): 0 data 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:41 Connects 5550427222203 <--> 5550427111100 from Serial1/1 SVC 59 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 3 PR: 5 ACK: 5 Remote PR: 3 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data 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:38 Connects 5550427222205 <--> 5550427111100 from Serial1/1 SVC 58 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 0 PR: 7 ACK: 7 Remote PR: 0 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 2/111560 packets 2/1023 Resets 0/1 RNRs 0/0 REJs 0/0 INTs 0/0

Step 3 Examine the report. A closer look at the connection that will map to PVC 4 or the ADMIN channel reveals that SVC 63 is the connection. The following example shows a calling address of 5550427222204 and a called address of 5550427111100:

SVC 63, State: D1, Interface: Serial1/1 Started 00:16:01, last input 00:12:18, output 00:12:16 Connects 5550427222204 <--> 5550427111100 to XOT between 10.59.251.66, 11097 and 10.60.128.8, 1998 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 6 PR: 7 ACK: 7 Remote PR: 6 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 224/13 packets 14/7 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0

In 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:18 Connects 5550427222204 <--> 5550427111100 from Serial1/1 SVC 63 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 7 PR: 6 ACK: 6 Remote PR: 7 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data 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 NetworkTo configure a backup active interface on the telephone switch side of the telco DCN, see Figure 2-24 on page 2-51 and perform the following steps. See the “X.25 BAI Telephone Switch Side Configuration: Example” section on page 2-62 for a configuration example. See the “Verifying PVC-to-SVC Conversions” section on page 2-63 for a verification example.







Configure the Active Serial Interface




Router-3662(config-if)# SCC0 Link to 5ESS (UnManaged)





Step 7 Configure serial interface 4/1 as the backup to serial interface 4/0:

Router-3662(config-if)# backup active interface serial 4/1




Router-3662(config-if)# x25 address 5550427111100

Step 10 Set the low two-way VC channel to 8:


Step 11 Set the X.25 T10 timer to 30:

Router-3662(config-if)# x25 t10 30







Step 15 Set the X.25 threshold to 1. This command instructs the router to send acknowledgment packets when it is not busy sending other packets, even if the number of input packets has not reached the input window size count:

Router-3662(config-if)# x25 threshold 1

Step 16 Configure seven SVC-to-PVC conversions. Notice how the PVC number and the last digit of the X.121 address match in this example. The X.121 address is used to map to the appropriate PVC. Specify an X.25 packet size of 128, and input and output window sizes of 4 for these interfaces:

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 4





Step 18 Set the LAPB T1 timer to 5000:

Router-3662(config-if)# lapb t1 5000





Step 21 Set the LAPB N2 timer to 7:

Router-3662(config-if)# lapb n2 7

Step 22 Set the LAPB K timer to 4:

Router-3662(config-if)# lapb k 4



Configure the Backup Serial Interface




Router-3662(config-if)# SCC1 Link (UnManaged)























Step 36 Configure seven SVC-to-PVC conversions. Specify an X.25 packet size of128, and input and output window sizes of 4 for these interfaces:

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 4















Enable X.25 Routing

Step 44 Create an entry in the X.25 routing table for X.25 address 55504271111 on serial interface 4/0:

Router-3662(config)# x25 route 55504271111 interface serial 4/0


Router-3662(config)# x25 route 55504271111 interface serial 4/1


Router-3662(config)# end





X.25 BAI Telephone Switch Side Configuration: Example

The Cisco 3662 router in Figure 2-24 on page 2-51 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/0 description SCC0 Link to 5ESS (UnManaged) no ip address encapsulation x25 dce backup active interface Serial4/1 x25 version 1980 x25 address 5550427111100 x25 ltc 8 x25 t10 30 x25 t12 30 x25 win 4 x25 wout 4 x25 threshold 1 x25 pvc 1 svc 5550427222201 packetsize 128 128 windowsize 4 4 x25 pvc 2 svc 5550427222202 packetsize 128 128 windowsize 4 4 x25 pvc 3 svc 5550427222203 packetsize 128 128 windowsize 4 4 x25 pvc 4 svc 5550427222204 packetsize 128 128 windowsize 4 4 x25 pvc 5 svc 5550427222205 packetsize 128 128 windowsize 4 4 x25 pvc 6 svc 5550427222206 packetsize 128 128 windowsize 4 4 x25 pvc 7 svc 5550427222207 packetsize 128 128 windowsize 4 4 clockrate 9600 lapb T1 5000 lapb T2 200 lapb T4 10 lapb N2 7 lapb k 4!interface Serial4/1 description SCC1 link (UnManaged) no ip address encapsulation x25 dce x25 version 1980



x25 address 5550427111100 x25 ltc 8 x25 t10 30 x25 t12 30 x25 win 4 x25 wout 4 x25 threshold 1 x25 pvc 1 svc 5550427222201 packetsize 128 128 windowsize 4 4 x25 pvc 2 svc 5550427222202 packetsize 128 128 windowsize 4 4 x25 pvc 3 svc 5550427222203 packetsize 128 128 windowsize 4 4 x25 pvc 4 svc 5550427222204 packetsize 128 128 windowsize 4 4 x25 pvc 5 svc 5550427222205 packetsize 128 128 windowsize 4 4 x25 pvc 6 svc 5550427222206 packetsize 128 128 windowsize 4 4 x25 pvc 7 svc 5550427222207 packetsize 128 128 windowsize 4 4 clockrate 9600 lapb T1 5000 lapb T2 200 lapb T4 10 lapb N2 7 lapb k 4!x25 route 55504271111 interface Serial4/0x25 route 55504271111 interface Serial4/1

Verifying 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 vc

PVC 1, State: D1, Interface: Serial4/0 Started 02:58:25, last input 00:00:00, output 00:01:39 Connects 5550427222201 <--> 5550427111100 from XOT between 10.60.128.8, 1998 and 10.59.251.66, 11161 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 2 PR: 0 ACK: 7 Remote PR: 2 RCNT: 1 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 20/24720 packets 16/1236 Resets 687/0 RNRs 0/0 REJs 0/0 INTs 0/0PVC 2, State: D1, Interface: Serial4/0 Started 02:58:25, last input 00:01:45, output never Connects 5550427222202 <--> 5550427111100 from XOT between 10.60.128.8, 1998 and 10.59.251.66, 11163 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 0 PR: 4 ACK: 4 Remote PR: 0 RCNT: 0 RNR: Rx P/D state timeouts: 0 timer (secs): 0 data bytes 0/2924 packets 0/43 Resets 24/0 RNRs 0/46 REJs 0/0 INTs 0/0PVC 3, State: D1, Interface: Serial4/0 Started 02:58:25, last input 00:01:45, output 00:01:38 Connects 5550427222203 <--> 5550427111100 from XOT between 10.60.128.8, 1998 and 10.59.251.66, 11166 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 2 PR: 4 ACK: 4 Remote PR: 2 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 24/4831 packets 16/63 Resets 10/0 RNRs 0/0 REJs 0/0 INTs 0/0PVC 4, State: D1, Interface: Serial4/0



Started 02:58:30, last input 00:01:34, output 00:01:35 Connects 5550427222204 <--> 5550427111100 from XOT between 10.60.128.8, 1998 and 10.59.251.66, 11164 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 3 PR: 6 ACK: 6 Remote PR: 3 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 67/400 packets 19/38 Resets 5/0 RNRs 0/1 REJs 0/0 INTs 0/0PVC 5, State: D1, Interface: Serial4/0 Started 02:57:35, last input 00:00:00, output 00:01:39 Connects 5550427222205 <--> 5550427111100 from XOT between 10.60.128.8, 1998 and 10.59.251.66, 11165 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 2 PR: 0 ACK: 5 Remote PR: 2 RCNT: 3 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 8/202550 packets 8/1806 Resets 872/0 RNRs 0/2 REJs 0/0 INTs 0/0PVC 6, State: D1, Interface: Serial4/0 Started 02:58:32, last input 00:01:34, output 00:01:37 Connects 5550427222206 <--> 5550427111100 from XOT between 10.60.128.8, 1998 and 10.59.251.66, 11162 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 3 PR: 6 ACK: 6 Remote PR: 3 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 23/300 packets 11/22 Resets 6/0 RNRs 0/0 REJs 0/0 INTs 0/0PVC 7, State: D1, Interface: Serial4/0 Started 02:58:32, last input 00:01:35, output 00:01:38 Connects 5550427222207 <--> 5550427111100 from XOT between 10.60.128.8, 1998 and 10.59.251.66, 11160 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 2 PR: 1 ACK: 1 Remote PR: 2 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 8/206 packets 8/2 Resets 6/0 RNRs 0/17 REJs 0/0 INTs 0/0PVC 1, State: P/Inactive, Interface: Serial4/1 Started 02:58:32, last input 00:01:59, output 00:08:30 PVC <--> SVC to 5550427222201, not connected Window size input: 4, output: 4 Packet size input: 128, output: 128 P/D state timeouts: 1 timer (secs): 0 data bytes 16/67500 packets 12/3375 Resets 102/1 RNRs 0/0 REJs 0/0 INTs 0/0PVC 2, State: P/Inactive, Interface: Serial4/1 Started 02:58:34, last input 00:03:20, output never PVC <--> SVC to 5550427222202, not connected Window size input: 4, output: 4 Packet size input: 128, output: 128 P/D state timeouts: 0 timer (secs): 0 data bytes 0/4624 packets 0/68 Resets 4/0 RNRs 0/66 REJs 0/0 INTs 0/0PVC 3, State: P/Inactive, Interface: Serial4/1 Started 02:58:34, last input 00:16:27, output 00:07:03 PVC <--> SVC to 5550427222203, not connected Window size input: 4, output: 4 Packet size input: 128, output: 128 P/D state timeouts: 0 timer (secs): 0 data bytes 49/7378 packets 27/131 Resets 4/0 RNRs 0/0 REJs 0/0 INTs 0/0PVC 4, State: P/Inactive, Interface: Serial4/1 Started 02:58:34, last input 00:06:55, output 00:06:56 PVC <--> SVC to 5550427222204, not connected Window size input: 4, output: 4 Packet size input: 128, output: 128 P/D state timeouts: 0 timer (secs): 0 data bytes 53/632 packets 23/46 Resets 4/0 RNRs 0/0 REJs 0/0 INTs 0/0PVC 5, State: P/Inactive, Interface: Serial4/1



Started 02:58:36, last input 00:02:02, output 00:07:02 PVC <--> SVC to 5550427222205, not connected Window size input: 4, output: 4 Packet size input: 128, output: 128 P/D state timeouts: 0 timer (secs): 0 data bytes 9/719695 packets 9/6672 Resets 118/0 RNRs 0/1 REJs 0/0 INTs 0/0PVC 6, State: P/Inactive, Interface: Serial4/1 Started 02:58:36, last input 00:07:01, output 00:07:01 PVC <--> SVC to 5550427222206, not connected Window size input: 4, output: 4 Packet size input: 128, output: 128 P/D state timeouts: 0 timer (secs): 0 data bytes 280/532 packets 28/56 Resets 5/0 RNRs 0/0 REJs 0/0 INTs 0/0PVC 7, State: P/Inactive, Interface: Serial4/1 Started 02:58:36, last input 00:07:03, output 00:07:00 PVC <--> SVC to 5550427222207, not connected Window size input: 4, output: 4 Packet size input: 128, output: 128 P/D state timeouts: 0 timer (secs): 0 data 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:40 Connects 5550427222207 <--> 5550427111100 from Serial4/0 PVC 7 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 1 PR: 2 ACK: 2 Remote PR: 1 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data 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:00 Connects 5550427222201 <--> 5550427111100 from Serial4/0 PVC 1 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 6 PR: 2 ACK: 2 Remote PR: 4 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data 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:39 Connects 5550427222206 <--> 5550427111100 from Serial4/0 PVC 6 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 6 PR: 3 ACK: 3 Remote PR: 6 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data 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:58 Connects 5550427222202 <--> 5550427111100 from Serial4/0 PVC 2 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 4 PR: 0 ACK: 0 Remote PR: 4 RCNT: 0 RNR: Tx P/D state timeouts: 0 timer (secs): 0 data 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:42 Connects 5550427222204 <--> 5550427111100 from Serial4/0 PVC 4 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 6 PR: 3 ACK: 3 Remote PR: 6 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data 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:00 Connects 5550427222205 <--> 5550427111100 from Serial4/0 PVC 5 Window size input: 4, output: 4



Packet size input: 128, output: 128 PS: 7 PR: 2 ACK: 2 Remote PR: 3 RCNT: 0 RNR: no Window is closed P/D state timeouts: 0 timer (secs): 0 data 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:01 Connects 5550427222203 <--> 5550427111100 from Serial4/0 PVC 3 Window size input: 4, output: 4 Packet size input: 128, output: 128 PS: 4 PR: 2 ACK: 2 Remote PR: 4 RCNT: 0 RNR: no P/D state timeouts: 0 timer (secs): 0 data bytes 48/2 packets 4/2 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0

The 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 to 1 dest 55504271111 Serial4/0 2 dest 55504271111 Serial4/1

Configuring SCC0 and SCC1 on the Lucent 5ESS Telephone Switch FormThe 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 on page 2-109 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.

cpblx3 Communications Protocol Option Block (Recent Change and Verify)

1.option_name:cpblx300

2.speed:9600 3.duplex:full 4.ds_type:201CPL

5.carrier:s 6.line_access:direct 7.mode_op:b

8.pdtime1:30 9.pdtime2:50 10.window:4

11.rexmit:7 12.dcedte:0 13.pcsd_stat:active

14.config:duplex

15.ldtel sid tlim telno 1)______ ____ ______________ 2)______ ____ ______________ 3)______ ____ ______________ 4)______ ____ ______________

19.security:n 20.link_id:0

21.feid_len:0 22.neid_len:0 23.password_len:0

24.feid.fend



1)____ 4)____ 7)____ 10)____ 13)____ 2)____ 5)____ 8)____ 11)____ 14)____ 3)____ 6)____ 9)____ 12)____ 15)____

35.neid.nend 1)____ 4)____ 7)____ 10)____ 13)____ 2)____ 5)____ 8)____ 11)____ 14)____ 3)____ 6)____ 9)____ 12)____ 15)____

46.pswrd.pwrd 1)____ 4)____ 7)____ 10)____ 13)____ 2)____ 5)____ 8)____ 11)____ 14)____ 3)____ 6)____ 9)____ 12)____ 15)____

57.perm_state:allow 58.outscrsiz:3300 59.outpktsiz:131

60.inscrsiz:3300 61.inpktsiz:131

62.hup:n 63.spckt:0 64.x3wsize:4 65.x3psize:128

66.x3pvcn.ldinno

1)_____ 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:60

85.time_td:180 86.time_ts:180 87.time_ack:5

Monitoring the Lucent DRMThe 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 2-26 shows an initial sample test network that was set up to test a Cisco STUN implementation and an XOT implementation.

Figure 2-25 Lucent DRM Preliminary Test Configurations82

555

IP cloud

DRM

Sun RS-449

BlackboxIC456A-R2

BlackboxEIA/TIA-232

cable

Cisco 2600-A

172.21.192.47Ethernet 0/1

172.20.46.140Ethernet 0/0

Cisco 2600-B

Cisco V.36 DCECAB-V35MC72-08002/01

Cisco EIA/TIA-232 DCE72-0794-01

EMMworkstation

NFM host



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 2-26.

Figure 2-26 Lucent DRM Network Test Configurations

Configuring the Lucent DRMExamples of the STUN configurations for the routers labeled 2600-A and 2600-B are listed in the following sections:

• Lucent DRM-Side Configuration: Example, page 2-68

• Application Host Configuration: Example, page 2-69

Troubleshooting a single connection is the same process as described in the “Verifying Links in the Cisco STUN OSS Connectivity Solution” section on page 2-48, which describes enabling two STUN links for the SCC0 and SCC1 connections to a Lucent 5ESS telephone switch.

Note Another method to extend the single monitoring connection over an IP backbone would be to use XOT. XOT was described in the “CDR Bill Collection Networks: Cisco XOT and RBP Solutions” section on page 2-5.

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/1 ip address 172.21.192.47 255.255.255.0!interface Serial1/0 no ip address encapsulation stun clockrate 9600 stun group 103 stun route all tcp 172.20.46.140

8255

6

IP cloud

DRM

Sun RS-449

Male-to-malegender sender Cisco 2600-A Cisco 2600-B

Cisco V.36 DCECAB-V35MC72-08002/01

Cisco EIA/TIA-449 DCE72-0796-01

EMMworkstation

NFM host

172.21.192.47Ethernet 0/1

172.20.46.140Ethernet 0/0


Chapter 2 Telephone Switch EnvironmentsSwitch Monitoring Networks: IP and Cisco X.25 BAI and EOR Solutions

Application 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/0 ip address 172.20.46.140 255.255.255.0!interface Serial1/6 description CO1 to CO2 no ip address encapsulation stun no ignore-hw local-loopback clockrate 9600 stun group 103 stun route all tcp 172.21.192.47

Switch 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:

• Configuring a Cisco Router with X.25 BAI and EOR on the Telephone Switch Side of the Network, page 2-69

• TTI Telecom Monitoring Application Cisco X.25 BAI Solution, page 2-77

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 on page 2-51). 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 2-27 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 2-27 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 on page 2-73 for a configuration example. See the “Verifying Cisco X.25 BAI and EOR Configurations” section on page 2-74 for a verification example.





Configure the Active Serial Interface




Router-3662(config-if)# SCC0 Link to 5ESS (UnManaged)





Step 7 Configure serial interface 4/1 as the backup to serial interface 4/0:

Router-3662(config-if)# backup active interface serial 4/1









Networkmanagementapplication

1170

80

Lucent 5ESS

IP

X.25 protocoltranslation

Serial 4/1 SCC1

Serial 4/0X.25 SCC0

3662

7 X.25 PVCsRedundant serial ports

7 TCP sessions

























Configure the Backup Serial Interface




Router-3662(config-if)# SCC1 Link (UnManaged)





































Enable Protocol Translation

Step 42 Configure protocol translations statements to convert the incoming TCP session to an X.25 PVC. The dynamic keyword works with the backup active interface command to allow the switching between SCC0 and SCC1. The EOR keyword inserts a hexadecimal value of 19 at the end of a record being sent to the NMA application. The NMA application must be set up to parse for the EOR.

Router-3662(config-if)# translate tcp 10.60.150.128 port 1031 x25 12345678 pvc 1 dynamic max-users 1 EOR 0x19 insert



Router-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 insert

Enable X.25 Routing


Router-3662(config)# x25 route 12345678 interface Serial4/0


Router-3662(config)# x25 route 12345678 interface Serial4/1


Router-3662(config)# end



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 routing

interface Serial4/0 description SCC0 Link to 5ESS (UnManaged) no ip address encapsulation x25 dce backup active interface Serial4/1 x25 version 1980 x25 address 12345678 x25 ltc 8 x25 t10 30 x25 t12 30 x25 win 4 x25 wout 4 x25 threshold 1 clockrate 9600 lapb T1 5000 lapb T2 200 lapb T4 10 lapb N2 7



lapb k 4!interface Serial4/1 description SCC1 link (UnManaged) no ip address encapsulation x25 dce x25 version 1980 x25 address 12345678 x25 ltc 8 x25 t10 30 x25 t12 30 x25 win 4 x25 wout 4 x25 threshold 1 clockrate 9600 lapb T1 5000 lapb T2 200 lapb T4 10 lapb N2 7 lapb k 4

x25 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 insert

Verifying Cisco X.25 BAI and EOR Configurations

The following sections contain useful information for verifying the Cisco X.25 BAI and EOR configurations:

• Verifying the Active Interface with the show interface Command, page 2-75

• Verifying the Interface Type and Clock Rate with the show controllers Command, page 2-76

• Verifying the Active TCP Connection with the show tcp brief Command, page 2-77

Following is a list of additional EXEC commands that can be used to troubleshoot the configurations:

• debug pad

• debug translate

• debug x25 event

• show controllers

• show debug

• show interface

• show running configuration



• show tcp brief

• show version

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/0

Serial4/0 is up, line protocol is up Hardware is CD2430 in sync mode Description: 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 set MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation X25, loopback not set X.25 DCE, address 12345678, state R1, modulo 8, timer 0 Defaults: idle VC timeout 0 cisco encapsulation input/output window sizes 4/4, packet sizes 128/128 Timers: T10 30, T11 180, T12 30, T13 60 Channels: Incoming-only none, Two-way 8-1024, Outgoing-only none RESTARTs 25/0 CALLs 0+0/0+0/0+0 DIAGs 2/0 LAPB DCE, state CONNECT, modulo 8, k 4, N1 12056, N2 7 T1 5000, T2 200, interface outage (partial T3) 0, T4 10 VS 0, VR 3, tx NR 3, Remote VR 0, Retransmissions 0 Queues: U/S frames 0, I frames 0, unack. 0, reTx 0 IFRAMEs 4042/4218 RNRs 0/0 REJs 0/0 SABM/Es 11/23 FRMRs 0/0 DISCs 0/2 Last input 00:00:00, output 00:00:00, output hang never Last clearing of "show interface" counters 01:21:32 Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue :3/40 (size/max) 5 minute input rate 1000 bits/sec, 4 packets/sec 5 minute output rate 0 bits/sec, 2 packets/sec 8553 packets input, 383358 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 4497 packets output, 21498 bytes, 0 underruns 0 output errors, 0 collisions, 3 interface resets 0 output buffer failures, 0 output buffers swapped out 4 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up

The 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/1

Serial4/1 is testing, line protocol is down Hardware is CD2430 in sync mode Description: SCC1 link (UnManaged) Backup interface Serial4/0, failure delay 0 sec, secondary disable delay 0 sec, kickin load not set, kickout load not set MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation X25, loopback not set



X.25 DCE, address 12345678, state R/Inactive, modulo 8, timer 0 Defaults: idle VC timeout 0 cisco encapsulation input/output window sizes 4/4, packet sizes 128/128 Timers: T10 30, T11 180, T12 30, T13 60 Channels: Incoming-only none, Two-way 8-1024, Outgoing-only none RESTARTs 23/0 CALLs 0+0/0+0/0+0 DIAGs 0/0 LAPB DCE, state DISCONNECT, modulo 8, k 4, N1 12056, N2 7 T1 5000, T2 200, interface outage (partial T3) 0, T4 10 VS 0, VR 0, tx NR 0, Remote VR 0, Retransmissions 0 Queues: U/S frames 0, I frames 0, unack. 0, reTx 0 IFRAMEs 20/0 RNRs 0/0 REJs 0/0 SABM/Es 0/23 FRMRs 0/0 DISCs 0/0 Last input 00:00:00, output 00:00:23, output hang never Last clearing of "show interface" counters 01:21:41 Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue :0/40 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 57 packets input, 114 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 60 packets output, 220 bytes, 0 underruns 0 output errors, 0 collisions, 3 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up

Verifying 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/0

CD2430 Slot 4, Port 0, Controller 0, Channel 0, Revision 18Channel mode is synchronous serial idb 0x61B1445C, buffer size 1524, RS-232 DCE cable, clockrate 9600

Global registers rpilr 0x2, rir 0x0, risr 0x0, rfoc 0x0, rdr 0x0 tpilr 0x1, tir 0x0, tisr 0x68, tftc 0x0, tdr 0x90 mpilr 0x3, mir 0x0, misr 0x60 bercnt 0xFF, stk 0x0Per-channel registers for channel 0 Option registers 0x02 0x00 0x42 0x67 0x60 0x00 0x00 Command and status registers cmr 0xC0, ccr 0x00, csr 0xCC, msvr-rts 0xF1, msvr-dtr 0xF1 Clock option registers rcor 0x86, rbpr 0x01, tcor 0xC0, tbpr 0x77 Interrupt registers ier 0x89, livr 0x00, licr 0x00 DMA buffer status 0x22 DMA receive registers arbaddr 0xFA370E4, arbcnt 1548, arbsts 0x1 brbaddr 0xFA36A64, brbcnt 1548, brbsts 0x1 rcbaddr 0xFA363E6 DMA transmit registers atbaddr 0xF8014D6, atbcnt 5, atbsts 0x62 btbaddr 0xFCADDF6, btbcnt 5, btbsts 0x62



tcbaddr 0xFCADDFB Special character registers schr1 0x00, schr2 0x00, schr3 0x00, schr4 0x00 scrl 0x0, scrh 0x0, lnxt 0xF1Driver context information Context structure 0x61B16C78, Register table 0x3E800400 Serial Interface Control 5:1 Register (0x3E800802) is 0x80 Adaptor Flags 0x0 Serial Modem Control Register (0x3E800804) is 0x1D Receive static buffer 0x61A520B0 Receive particle buffers 0x61B17240, 0x61B17200 Transmit DMA buffers 0x0, 0x0, 0x0, 0x0 Transmit packet with particles 0x0, first word is 0x0 Interrupt rates (per second) transmit 1, receive 3, modem 0 True fast-switched packets 0 Semi fast-switched packets 0 Transmitter hang count 0 Residual indication count 0 Bus error count 0 Aborted short frames count 0 CRC short frames count 0Error counters CTS deassertion failures 0 Nested interrupt errors transmit 0, receive 0, modem 0

Verifying 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 brief

TCB 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 The IP address used in protocol translation must come from a locally attached subnet to the router. The IP address cannot be assigned to an interface on the router. In this example, the IP address is a free address from Fast Ethernet interface 0/0. The configuration for Fast Ethernet interface 0/0 is listed next.

interface FastEthernet0/0 ip address 10.6.15.1 255.255.255.0 speed 100 full-duplex

TTI Telecom Monitoring Application Cisco X.25 BAI SolutionThe 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 2-28. 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 on page 2-74 to verify and troubleshoot this configuration.

Figure 2-28 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 routing

interface Serial4/0 description SCC0 Link to 5ESS (UnManaged) no ip address encapsulation x25 dce backup active interface Serial4/1 x25 version 1980 x25 address 12345678 x25 ltc 8 x25 t10 30 x25 t12 30 x25 win 4 x25 wout 4 x25 threshold 1 clockrate 9600 lapb T1 5000 lapb T2 200 lapb T4 10 lapb N2 7 lapb k 4!interface Serial4/1 description SCC1 link (UnManaged) no ip address encapsulation x25 dce x25 version 1980 x25 address 12345678 x25 ltc 8 x25 t10 30 x25 t12 30 x25 win 4 x25 wout 4 x25 threshold 1 clockrate 9600 lapb T1 5000 lapb T2 200 lapb T4 10

NetraFault

1170

81

Lucent 5ESS

IP


Serial 4/1 SCC1

Serial 4/0X.25 SCC0

3662

7 X.25 PVCsRedundant serial ports

7 TCP sessions


Chapter 2 Telephone Switch EnvironmentsProvisioning Networks: Cisco X.25 RBP Solution

lapb N2 7 lapb k 4

x25 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 1 translate tcp 10.60.150.128 port 1032 stream x25 12345678 pvc 2 dynamic max-users 1 translate 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 1 translate tcp 10.60.150.128 port 1035 x25 12345678 pvc 5 dynamic max-users 1 translate tcp 10.60.150.128 port 1036 x25 12345678 pvc 6 dynamic max-users 1 translate tcp 10.60.150.128 port 1037 x25 12345678 pvc 7 dynamic max-users 1

Provisioning Networks: Cisco X.25 RBP SolutionThis section describes Cisco telco solutions for telephone switch provisioning networks like the one highlighted in Figure 2-29.

Figure 2-29 Legacy Switch Provisioning Network

The Cisco X.25 RBP solution is described in the following sections:

• Cisco X.25 RBP Solution Overview, page 2-80

• Adding Cisco X.25 RBP to the Telco DCN Provisioning Connection, page 2-80

• Configuring the CONNECTVU-ATP Application, page 2-81

• Configuring the Lucent 5ESS Echo Back Port, page 2-82

• Configuring the Echo Back Port on the Cisco Router, page 2-82

• Configuring the Lucent 5ESS Recent Change Port, page 2-84

• Configuring the Recent Change Port on the Cisco Router, page 2-85

• Configuring ADC Service Activation Provisioning, page 2-97

8256

3

Lucent 5ESS

Monitoring

Provisioning

Datakit node

EDAS

SCC0

SCC1ModemsModems

X.25

COSAM

Datakit node

X.25 PAD X.25 PADCall detail recordcollection

EchoBack

Traffic engineering

Datakitbackbone

Recent Change (RC)



Cisco X.25 RBP Solution OverviewTelco provisioning applications automate the assignment of Class 5 telephone switch resources for new voice services and connections.

Both Figure 2-29 and Figure 2-30 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 2-30 also shows the Cisco X.25 RBP implementation that was designed to replace the network seen in Figure 2-29.

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 2-30 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 ConnectionThis section uses the Lucent CONNECTVU-ATP application to show how to add the Cisco X.25 RBP feature to the telco DCN.


http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftdcnrbp.htm#xtocid0


The Lucent CONNECTVU-ATP solution shown in Figure 2-30 is designed to manage and provision telephony switch resources.

Figure 2-30 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 ApplicationThe 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: LAB00

GENERIC: 5E14 RC SERV: LAB00RC EB SERV: LABD00EB

DMS LOGIN:DMS PASSWORD: ASM LOGIN:

ASM MACHINE NAME (D&L):

INHIBIT RETRU INTVL: 10OFFICE ID: CVUNOVERIFY MAX RC VCS: 4

RC LINK INTF:IP-X25-DY EB LINK INTF: IP-X25-DY

RC DIALSTRING/IP ADDRESS: 10.181.254.1

EB DIALSTRING/IP ADDRESS: 10.181.254.1

Attributes for Recent Change Links TCP/IP Connectivity

LINK ID 1 LINK ID 2 LINK ID 3 LINK ID 4

LOGIN:

PASSWORD:

8255

7TCP/IPRouter C

RC link

EB link

Lucent 5ESS

TCP (RBP) session X.25 SVC

IP cloud

CONNECTVU-ATP

10.181.254.1



SECURITYCLASS:

TCP/IPPORT: 20002 ? ? ?

Attributes for Echo Back Links TCP/IP Connectivity

LINK ID 1 LINK ID 2 LINK ID 3 LINK ID 4

LOGIN:

PASSWORD:

SECURITYCLASS:

TCP/IPPORT: 20001 ? ? ?

Configuring the Lucent 5ESS Echo Back PortThis 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 on page 2-82 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 RouterTo configure the EB port on a Cisco router, see Figure 2-30 on page 2-81 and perform the following steps. See the “Echo Back Port Configuration: Example” section on page 2-84 for a configuration example.



Step 1 Verify that you are running Cisco IOS Release 12.2(8)T or a later software release that supports telco DCN functions:

Router-C# show version


Router-C# configure terminalEnter configuration commands, one per line. End with CNTL/Z.

Step 3 Select the serial interface for the EB port. In the example, serial interface 1/0 is used, which specifies network module 1, port 0:

Router-C(config)# interface serial 1/0


Router-C(config-if)# shutdown


Router-C(config-if)# description EchoBack

Step 6 Enable X.25 DTE encapsulation on the interface. DTE is the default value for the interface:

Router-C(config-if)# encapsulation x25


Router-C(config-if)# x25 version 1980

Step 8 Set the high two-way channel to 3 so that the SVC range will be from 1 to 3:

Router-C(config-if)# x25 htc 3


Router-C(config-if)# x25 threshold 1

Step 10 Enable the RBP feature on the router. The Call User Data (CUD) field must be set to 0xC1. The customer sets the called X.121 address. In this example, the called X.121 address is 5553501136. You can specify the TCP port. In this example, the TCP port is set to 20001:

Router-C(config-if)# x25 map rbp 5553501136 cud 0xC1 local port 20001


Router-C(config-if)# clockrate 9600

Step 12 Set the T2 parameter to 400 milliseconds, which specifies the length of time the DTE or DCE has before acknowledging a frame:

Router-C(config-if)# lapb t2 400

Step 13 Set the LAPB T4 timer to 25 seconds, which specifies the length of time the link can sit idle. The Cisco default for the LAPB T4 timer is 0, which disables the feature.


Step 14 The LAPB N1 parameter sets the maximum bits per frame. Set this timer to 4136:

Router-C(config-if)# lapb n1 4136




Router-C(config-if)# no shutdown


Router-C(config-if)# endRouter-C(config)# end


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/0 description EchoBack no ip address encapsulation x25 no ip route-cache no ip mroute-cache x25 version 1980 x25 htc 3 x25 threshold 1 x25 map rbp 5553501136 cud 0xC1 local port 20001 clockrate 9600 lapb T2 400 lapb T4 25 lapb N1 4136

Configuring the Lucent 5ESS Recent Change PortThis 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 on page 2-85 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 RouterTo configure the RC port on a Cisco router, see Figure 2-30 on page 2-81 and perform the following steps. See the “Recent Change Port Configuration: Example” section on page 2-86 for a configuration example. See the “Debugging the Echo Back and Recent Change Ports” section on page 2-87 for a debugging examples.


Router-C# show version


Router-C# configure terminalEnter configuration commands, one per line. End with CNTL/Z.

Step 3 Select the serial interface for the RC port. In the example, serial interface 1/1 is used, which specifies network module 1, port 1:

Router-C(config-if)# interface serial 1/1


Router-C(config-if)# shutdown


Router-C(config-if)# description RecentChange

Step 6 Enable X.25 DTE encapsulation on the interface. DTE is the default X.25 encapsulation.

Router-C(config-if)# encapsulation x25 dte


Router-C(config-if)# x25 version 1980




Router-C(config-if)# x25 threshold 1



Step 10 Enable the RBP feature on the router. The CUD field must be set to 0xC1. The customer sets the called X.121 address. In this example, the called X.121 address is 5553501135. You can specify the TCP port. In this example, the TCP port is set to 20002:

Router-C(config-if)# x25 map rbp 5553501135 cud 0xC1 local port 20002


Router-C(config-if)# clockrate 9600

Step 12 Set the T2 parameter to 400 milliseconds, which specifies the length of time the DTE or DCE has before acknowledging a frame:


Step 13 Set the LAPB T4 timer to 25 seconds, which is the length of time the link can sit idle. The Cisco default for the LAPB T4 timer is 0, which disables the feature.


Step 14 Set the LAPB N1 parameter to 4136, which determines the maximum bits per frame:

Router-C(config-if)# lapb n1 4136


Router-C(config-if)# no shutdown


Router-C(config-if)# endRouter-C(config)# end


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/1 description RecentChange no ip address encapsulation x25 no ip route-cache no ip mroute-cache x25 version 1980 x25 htc 4 x25 threshold 1 x25 map rbp 5553501135 cud 0xC1 local port 20002 clockrate 9600 lapb T2 400 lapb T4 25 lapb N1 4136



Debugging the Echo Back and Recent Change Ports

The following procedure provides helpful hints on debugging problems with EB and RC port connectivity:

Step 1 Verify that the serial cable is correct. The show controllers EXEC command will display the type of cable connected to the router. In the example, the cable is connected to slot 1, port 2 on the router. The correct cable type is EIA/TIA-232 DCE for the EB and RC ports. A clock rate of 9600 baud can also be verified.

Router-C# show controllers serial 1/2

CD2430 Slot 1, Port 2, Controller 0, Channel 2, Revision 16Channel mode is synchronous serial idb 0x819D6014, buffer size 1524, RS-232 DCE cable, clockrate 9600

Global registers rpilr 0x2, rir 0x0, risr 0x0, rfoc 0x0, rdr 0x0 tpilr 0x1, tir 0x0, tisr 0x0, tftc 0x0, tdr 0x0 mpilr 0x3, mir 0x0, misr 0x0 bercnt 0xFF, stk 0x0Per-channel registers for channel 2 Option registers 0x02 0x00 0x42 0x67 0x60 0x00 0x00 Command and status registers cmr 0xC0, ccr 0x00, csr 0x04, msvr-rts 0x10, msvr-dtr 0x10 Clock option registers rcor 0x86, rbpr 0x01, tcor 0xC0, tbpr 0x77 Interrupt registers ier 0x00, livr 0x08, licr 0x08 DMA buffer status 0x00 DMA receive registers arbaddr 0x35A8D04, arbcnt 1548, arbsts 0x1 brbaddr 0x35A8684, brbcnt 1548, brbsts 0x1 rcbaddr 0x0 DMA transmit registers atbaddr 0x0, atbcnt 0, atbsts 0x0 btbaddr 0x0, btbcnt 0, btbsts 0x0 tcbaddr 0x0 Special character registers schr1 0x00, schr2 0x00, schr3 0x00, schr4 0x00 scrl 0x0, scrh 0x0, lnxt 0x0Driver context information Context structure 0x819D8888, Register table 0x40800400 Serial Interface Control 5:1 Register (0x4080080A) is 0x80 Adaptor Flags 0x0 Serial Modem Control Register (0x4080080C) is 0x14 Receive static buffer 0x81919A04 Receive particle buffers 0x819D9100, 0x819D90C0 Transmit DMA buffers 0x0, 0x0, 0x0, 0x0 Transmit packet with particles 0x0, first word is 0x0 Interrupt rates (per second) transmit 0, receive 0, modem 0 True fast-switched packets 0 Semi fast-switched packets 0 Transmitter hang count 0 Residual indication count 0 Bus error count 0 Aborted short frames count 0 CRC short frames count 0Error counters CTS deassertion failures 0 Nested interrupt errors transmit 0, receive 0, modem 0



Step 2 Verify that the interface is up. In the sample output, the physical interface is up but the line protocol is down. Notice at the bottom of the output shown, the physical leads are up. The physical cable connection is good, but Layer 2 is not up. You know that Layer 2 is down because line protocol is down.

Router-C# show interface serial 1/1

Serial1/1 is up, line protocol is down Hardware is CD2430 in sync mode Description: RecentChange MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation X25, loopback not set X.25 DCE, address 5555275555, state R/Inactive, modulo 8, timer 0 Defaults: idle VC timeout 0 cisco encapsulation input/output window sizes 2/2, packet sizes 128/128 Timers: T10 60, T11 180, T12 60, T13 60 Channels: Incoming-only none, Two-way 1-1024, Outgoing-only none RESTARTs 0/0 CALLs 0+0/0+0/0+0 DIAGs 0/0 LAPB DCE, state SABMSENT, modulo 8, k 7, N1 12056, N2 20 T1 3000, T2 0, interface outage (partial T3) 0, T4 0 VS 0, VR 0, tx NR 0, Remote VR 0, Retransmissions 10 Queues: U/S frames 0, I frames 0, unack. 0, reTx 0 IFRAMEs 0/0 RNRs 0/0 REJs 0/0 SABM/Es 11/0 FRMRs 0/0 DISCs 0/0 Last input 00:00:02, output 00:00:00, output hang never Last clearing of "show interface" counters 00:17:12 Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue :0/40 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 14 packets input, 31 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 13 packets output, 26 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out 3 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up

Step 3 Enable LAPB debugging to help determine the problem. If you are logged in to the router remotely, you will need to use the terminal monitor EXEC command to display the output on your terminal. The following output shows SABMs being sent out of the router. The bold LABP O report indicates that a packet is being sent out of the interface.

Router-C# terminal monitor

Router-C# debug lapb

LAPB 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 2



00: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 6

Step 4 The problem in the sample output is lack of clocking on the serial interface, so enable the clock rate and you should see the interface come up:

Router-C(config)# interface serial 1/1Router-C(config-if)# shutdown

00:10:40: %LINK-5-CHANGED: Interface Serial1/1, changed state to administrative

Router-C(config-if)# clockrate 9600Router-C(config-if)# no shutdownRouter-C(config-if)# end

00: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 console

Step 5 Check the LAPB output again. The report shows receiver ready packets going in (I) and out (O) of the serial interface, indicating that the protocol is up at Layer 2:

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 1

00: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 1

Step 6 Enter the show interface EXEC command to verify that the line protocol is up:

Router-C# show interface serial 1/1

Serial1/1 is up, line protocol is up Hardware is CD2430 in sync mode Description: RecentChange MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation X25, loopback not set X.25 DTE, address <none>, state R1, modulo 8, timer 0 Defaults: idle VC timeout 0 cisco encapsulation input/output window sizes 2/2, packet sizes 128/128 Timers: T20 180, T21 200, T22 180, T23 180 Channels: Incoming-only none, Two-way 1-4, Outgoing-only none RESTARTs 4/0 CALLs 0+10/0+0/0+0 DIAGs 0/0 LAPB DTE, state CONNECT, modulo 8, k 7, N1 12056, N2 20 T1 3000, T2 0, interface outage (partial T3) 0, T4 0 VS 1, VR 1, tx NR 1, Remote VR 1, Retransmissions 0 Queues: U/S frames 0, I frames 0, unack. 0, reTx 0 IFRAMEs 38/4 RNRs 0/0 REJs 0/0 SABM/Es 74/3 FRMRs 0/0 DISCs 0/1



Last input 00:00:21, output 00:00:21, output hang 02:36:08 Last clearing of "show interface" counters 02:33:07 Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue :0/40 (size/max)

Step 7 Debug the X.25 layer. There are a number of options for X.25 debugging.

Caution If the routers are loaded with a production release of the software, be careful of which debugging features are used. You can enable debugging for a specific serial interface or events; the commands are shown.

Router-C# debug x25 ?

all Show all X.25 traffic (default) annexg X.25 over Frame-Relay (Annex-G) Events aodi Always On/Direct ISDN (PPP over X.25) events cmns Show only CMNS traffic events Show X.25 traffic without normal Data and RR packets interface Show X.25 or CMNS traffic on one interface only Show only X.25 traffic vc X.25 traffic across a specific virtual circuit xot Show only XOT (X.25-Over-TCP) traffic <cr>

Router-C# debug x25 interface serial 1/2

X.25 packet debugging is onX.25 debug output restricted to interface Serial1/2Router-C#

Router-C# debug x25 events

X.25 special event debugging is on

In 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 all

X.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 20001

Step 8 Place a call to TCP port 20002 and then watch the debug report. The report indicates that the LAPB layer is up. Next, place an X.25 RPB call to TCP port 20002, which is a valid TCP port for an X.25 RBP statement. The TCP session is accepted and an X.25 call is placed to the switch. Notice that the router is calling the X.121 address 5557777777 on logical channel identifier (LCI) 1024, but LCI 1024 is not correct. To make it correct, lower the highest two-way channel to 3 for the EB link, or 4 for the RC link, depending on the port:

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 636



00: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): 5557777777

Step 9 Set the high two-way channel to 4 for the RC link on serial interface 1/1:


Monitor 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 2

Step 10 Place a call with the wrong CUD field. Notice that the call is now placed on LCI 4. The CUD field was set to 193 decimal.

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 shutdown

02:37:47: %LINK-3-UPDOWN: Interface Serial1/1, changed state to up02:37:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/1, changed stp

interface Serial1/1 description RecentChange no ip address encapsulation x25 no ip route-cache no ip mroute-cache x25 htc 4 x25 map rbp 5553501135 cud 193 local port 20002 clockrate 9600

The 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 4



02: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 4

Step 11 Attempt to fix the rejected call by changing the CUD to hexadecimal number C1:

Router-C(config)# interface serial 1/1Router-C(config-if)# shutdownRouter-C(config-if)# no shutdown

02: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 found

Router-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)# end

The 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 4

The 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 1



02: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 4

Step 12 Enter the show debug EXEC command to display which debug statements have been started on the router. Use the no form of a debug command to disable the command.

Router-C# show debug

LAPB: LAPB link debugging is onTCP: TCP special event debugging is onX.25: X.25 packet debugging is on

Router-C# no debug lapb

LAPB link debugging is off

Router-C# show debug

TCP: TCP special event debugging is onX.25: X.25 packet debugging is on

Router-C# no debug all

All possible debugging has been turned off

Step 13 Debug the TCP session on the router. The list of TCP sessions that can be debugged is shown in the following example. Enter the debug ip tcp transactions command to start the test:

Router-C# debug ip tcp ?

driver TCP driver events driver-pak TCP driver verbose header-compression Header compression statistics intercept TCP intercept packet TCP packets rcmd Rcmd transactions sack Selective-ACK transactions Significant TCP events

Router-C# debug ip tcp transactions

TCP special event debugging is on



Step 14 Check the router configuration by entering the show running-config EXEC command:

Router-C# show running-config

Building 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/0 ip address 172.22.45.102 255.255.255.0 no ip route-cache no ip mroute-cache speed auto half-duplex no cdp enable!interface FastEthernet0/1 no ip address no ip route-cache no ip mroute-cache shutdown duplex auto speed auto no cdp enable!interface Serial1/0 description EchoBack no ip address encapsulation x25 no ip route-cache no ip mroute-cache x25 version 1980 x25 htc 3 x25 threshold 1 x25 map rbp 5553501136 cud 0xC1 local port 20001 clockrate 9600 lapb T2 400 lapb T4 25 lapb N1 4136!interface Serial1/1 description RecentChange no ip address encapsulation x25 no ip route-cache no ip mroute-cache x25 version 1980



x25 htc 4 x25 threshold 1 x25 map rbp 5553501135 cud 0xC1 local port 20002 clockrate 9600 lapb T2 400 lapb T4 25 lapb N1 4136!interface Serial1/2 no ip address no ip route-cache no ip mroute-cache shutdown no cdp enable!interface Serial1/3 no ip address no ip route-cache no ip mroute-cache shutdown no cdp enable!interface Serial1/4 no ip address no ip route-cache no ip mroute-cache shutdown no cdp enable!interface Serial1/5 no ip address no ip route-cache no ip mroute-cache shutdown no cdp enable!interface Serial1/6 no ip address no ip route-cache no ip mroute-cache shutdown no cdp enable!interface Serial1/7 no ip address no ip route-cache no ip mroute-cache shutdown no cdp enable!ip classlessno ip http server!!snmp-server engineID local 00000009020000036B490D00snmp-server community public RO!line con 0 exec-timeout 0 0 transport input noneline aux 0line vty 0 4 password cisco login



line vty 5 50 login!no scheduler allocateend!

Step 15 End the display and debugging session:

Router-C# quit

Configuring ADC Service Activation ProvisioningThis 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 2-31, 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 2-31 ADC and Cisco X.25 RBP

To configure the Cisco X.25 RBP feature in ADC Service Activation provisioning, see Figure 2-31 and perform the following steps. See the “ADC Service Activation Provisioning: Example” section on page 2-99 for a configuration example.


Router-D# show version


Router-D# configure terminalEnter configuration commands, one per line. End with CNTL/Z.

Step 3 Select the serial interface for the EB port. In the example, serial interface 1/0 is used, which specifies network module 1, port 0:

Router-D(config)# interface serial 1/0

8255

8TCP/IPRouter D

RC link

Lucent 5ESS

TCP (RBP) session X.25 SVC

IP cloud

Service Activation

10.60.128.8Loopback




Router-D(config-if)# shutdown

Step 5 Enter a description on the serial interface:

Router-D(config-if)# description Voice Activation


Router-D(config-if)# encapsulation x25 dce

Step 7 Set the X.25 address on the interface. This address is the calling address for the inbound SVC to the switch:

Router-D(config-if)# x25 address 5553501130


Router-D(config-if)# x25 htc 7


Router-D(config-if)# x25 win 3


Router-D(config-if)# x25 wout 3


Router-D(config-if)# x25 ips 256


Router-D(config-if)# x25 ops 256

Step 13 Set the X.25 optional user facility. The command will permit or deny flow control parameter negotiation of the packet or window size:

Router-D(config-if)# x25 subscribe flow-control always


Router-D(config-if)# x25 threshold 1

Step 15 Enable the RBP feature on the router. The CUD field must be set to 0xC1. The customer sets the called X.121 address. In this example, the called X.121 address is 5553501136. You can specify the TCP port. In this example, the TCP port is set to 10006:

Router-D(config-if)# x25 map rbp 5553501136 cud 0xC1 local port 10006


Router-D(config-if)# clockrate 56000


Router-D(config-if)# no shutdown


Router-D(config-if)# endRouter-D(config)# end


Chapter 2 Telephone Switch EnvironmentsTraffic Data Collection Networks: Cisco X.25 RBP and XOT Solutions


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/6 no ip address encapsulation x25 dce x25 address 5553501130 X25 htc 7 x25 win 3 x25 wout 3 x25 ips 256 x25 ops 256 x25 threshold 1 x25 subscribe flow-control always x25 map rbp 5553501136 cud 0xC1 local port 10006 no ignore-hw local-loopback clockrate 56000

Traffic 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 2-32.



Figure 2-32 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, page 2-100

• Configuring Cisco X.25 RBP for Traffic Data Collection Applications, page 2-101

• Debugging the Traffic Data Collection Connection, page 2-103

Adding Cisco X.25 RBP to the Telco DCN Traffic Data Collection ConnectionTDMS 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 2-33). 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 2-33 Traffic Data Collection Connection with XOT

8256

4

Lucent 5ESS


Monitoring

Provisioning

Datakit node

EDAS

EchoBack

SCC0

SCC1

Traffic engineering

X.25

Datakitbackbone

COSAM

Datakit node


ModemsModems

8254

8

Datakitnode

X.253 PVCs

X.253 PVCs

TCP session

EDAS

Lucent 5ESS

XOT tunnel

IP cloud

TDMS



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 2-34).

Figure 2-34 Traffic Data Collection Connection with Cisco X.25 RBP

Configuring Cisco X.25 RBP for Traffic Data Collection ApplicationsThe 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 NumberPVC Number100011100022100033

The 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 2-34 and perform the following steps. See the “Cisco X.25 RBP in the Traffic Data Collection Application: Example” section on page 2-103 for a configuration example. See the “Debugging the Traffic Data Collection Connection” section on page 2-103 for a debugging example.

Step 1 Verify that you are running Cisco IOS Release 12.2(8)T or a later software release that supports telco DCN functions and the Cisco X.25 RBP feature:

3662-router# show version


Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.


3662-router(config)# x25 routing

8254

9

TCP/IP

3662

Serial 4/2

EIA/TIA-232 DTE

3 TCP sessions

EDAS

Lucent 5ESS

3 X.25 PVCs

Record boundarypreservation supported

IP cloud

TDMS

10.60.128.8



Step 4 Select the serial interface that is connected to the EDAS port on the Lucent 5ESS. In the example, serial interface 4/2 is used, which specifies network module 4, port 2:

3662-router(config)# interface serial 4/2


3662-router(config-if)# shutdown


3662-router(config-if)# description EDAS port


3662-router(config-if)# encapsulation x25 dce


3662-router(config-if)# x25 loc 4

Step 9 Set the X.25 threshold to 1. This command instructs the router to send packets when the router is not busy sending other packets, even if the number of input packets has not reached the input window size count.

3662-router(config-if)# x25 threshold 1


3662-router(config-if)# x25 ips 256


3662-router(config-if)# x25 ops 256

Step 12 Enable the RBP feature on the router. The TDMS application requires three PVCs. The PVC range is from 1 through 3. PVC 1 is mapped to TCP port 10001. PVC 2 is mapped to TCP port 10002. PVC 3 is mapped to TCP port 10003. The TCP ports were chosen arbitrarily.

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 10003

Step 13 The router is functioning as a DCE device. The DCE must supply clock signaling to the DTE device, which is the EDAS port on the switch. Set the clock rate to 9600 baud:

3662-router(config-if)# clockrate 9600


3662-router(config-if)# no shutdown


3662-router(config-if)# end3662-router(config)# end


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 routing

interface Serial4/2 description EADAS no ip address encapsulation x25 dce no ip mroute-cache x25 ltc 4 x25 ips 256 x25 ops 256 x25 threshold 1 x25 pvc 1 rbp local port 10001 x25 pvc 2 rbp local port 10002 x25 pvc 3 rbp local port 10003 no ignore-hw local-loopback clockrate 9600

Debugging the Traffic Data Collection Connection

To debug the traffic data collection connection, perform the following steps:

Step 1 Enter the show interface serial EXEC command on the interface connected to the EDAS port on the switch. The report indicates that the physical interface is up and all of the control leads are up. The line protocol is up, which means that LAPB is up.

3662-router# show interface serial 4/2

Serial4/2 is up, line protocol is up Hardware is CD2430 in sync mode Description: EADAS MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation X25, loopback not set X.25 DCE, address <none>, state R1, modulo 8, timer 0 Defaults: idle VC timeout 0 cisco encapsulation input/output window sizes 2/2, packet sizes 256/256 Timers: T10 60, T11 180, T12 60, T13 60 Channels: Incoming-only none, Two-way 4-1024, Outgoing-only none RESTARTs 2/0 CALLs 0+0/0+0/0+0 DIAGs 0/0 LAPB DCE, state CONNECT, modulo 8, k 7, N1 12056, N2 20 T1 3000, T2 0, interface outage (partial T3) 0, T4 0 VS 2, VR 3, tx NR 3, Remote VR 2, Retransmissions 0 Queues: U/S frames 0, I frames 0, unack. 0, reTx 0 IFRAMEs 663/1627 RNRs 0/0 REJs 0/0 SABM/Es 0/2 FRMRs 0/0 DISCs 0/0 Last input 00:00:07, output 00:00:07, output hang never Last clearing of "show interface" counters 2d04h Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue :0/40 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 4027 packets input, 128719 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 3481 packets output, 9246 bytes, 0 underruns 0 output errors, 0 collisions, 20 interface resets



0 output buffer failures, 0 output buffers swapped out 3 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up

Step 2 Enter the show controller serial EXEC command to verify the cable type being used. The following report shows an EIA/TIA-232 DCE cable type with the clock rate set to 9600 baud:

3662-router# show controller serial 4/2

CD2430 Slot 4, Port 2, Controller 0, Channel 2, Revision 18Channel mode is synchronous serial idb 0x62F0AD64, buffer size 1524, RS-232 DCE cable, clockrate 9600

Global registers rpilr 0x2, rir 0x2, risr 0x0, rfoc 0x0, rdr 0x2 tpilr 0x1, tir 0x2, tisr 0x68, tftc 0x0, tdr 0xFF mpilr 0x3, mir 0x2, misr 0x60 bercnt 0xFF, stk 0x0Per-channel registers for channel 2 Option registers 0x02 0x00 0x42 0x67 0x60 0x00 0x00 Command and status registers cmr 0xC0, ccr 0x00, csr 0xCC, msvr-rts 0xF1, msvr-dtr 0xF1 Clock option registers rcor 0x86, rbpr 0x01, tcor 0xC0, tbpr 0x77 Interrupt registers ier 0x89, livr 0x08, licr 0x08 DMA buffer status 0x20 DMA receive registers arbaddr 0x3C90064, arbcnt 1548, arbsts 0x1 brbaddr 0x3C8F9E4, brbcnt 1548, brbsts 0x1 rcbaddr 0x3C8F369 DMA transmit registers atbaddr 0x3CD4EF6, atbcnt 2, atbsts 0x62 btbaddr 0x3A01B18, btbcnt 2, btbsts 0x62 tcbaddr 0x3A01B1A Special character registers schr1 0x00, schr2 0x00, schr3 0x00, schr4 0x00 scrl 0x0, scrh 0x0, lnxt 0xF1Driver context information Context structure 0x62F0DB68, Register table 0x3E800400 Serial Interface Control 5:1 Register (0x3E80080A) is 0x80 Adaptor Flags 0x0 Serial Modem Control Register (0x3E80080C) is 0x1D Receive static buffer 0x62DB54C8 Receive particle buffers 0x62F0E1C0, 0x62F0E180 Transmit DMA buffers 0x0, 0x0, 0x0, 0x0 Transmit packet with particles 0x0, first word is 0x0 Interrupt rates (per second) transmit 0, receive 0, modem 0 True fast-switched packets 0 Semi fast-switched packets 0 Transmitter hang count 0 Residual indication count 0 Bus error count 0 Aborted short frames count 0 CRC short frames count 0Error counters CTS deassertion failures 0 Nested interrupt errors transmit 0, receive 0, modem 0

Step 3 Enable debugging using the debug x25 all EXEC command and watch for a TCP session connect. In this configuration example, the host will connect to TCP port 10003:

3662-router# debug X25 all



The 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.6

The 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 3

The 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 0

Data 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 1

Step 4 Enable X.25 debugging using the debug X25 all command to check the PVCs when no data is being set.


The 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 0

Step 5 Enable X.25 debugging using the debug X25 all command to check the data going back and forth on PVC 3 between the host application and the switch:


The 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 1

The 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 3

Step 6 Enable X.25 debugging using the debug X25 all command to check that a connection is being started on TCP port 10001 and PVC 1:




The 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.6

The 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 1

The 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 1

Step 7 The last check is a debugging session with a long data transfer on PVC 3. A TCP session to port 10003 is coming in from the TDMS host, which has IP address 172.20.7.6. Enable X.25 debugging again. You should see a long report similar to the following example:


*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 The service provider must be using release 4.3 of the port configuration application and must select the Cisco option.

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 on page 2-109 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:cpblx33

2.speed:9600 3.duplex:full 4.ds_type:2024A

5.carrier:c 6.line_access:private 7.mode_op:b

8.pdtime1:60 9.pdtime2:100 10.window:4

11.rexmit:3 12.dcedte:013.pcsd_stat:active

14.config:simplex

(3/4)

35.neid.nend 1)____ 4)____ 7)____ 10)____ 13)____ 2)____ 5)____ 8)____ 11)____ 14)____ 3)____ 6)____ 9)____ 12)____ 15)____

46.pswrd.pwrd 1)____ 4)____ 7)____ 10)____ 13)____ 2)____ 5)____ 8)____ 11)____ 14)____ 3)____ 6)____ 9)____ 12)____ 15)____

57.perm_state:allow 58.outscrsiz:4062 59.outpktsiz:259

60.inscrsiz:406261.inpktsiz:259

cpblx3 (4/4)

62.hup:n 63.spckt:0 64.x3wsize:2 65.x3psize:256

66.x3pvcn.ldinno

1)_____ 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:60

85.time_td:180 86.time_ts:180 87.time_ack:5



Lucent cpblx Form Parameter DescriptionsThis section describes important fields in the Lucent cpblx form and lists values that can be entered in the fields.

1. option_name: (OPTIONNAME) Required

Option block name. This is a key field. Legal values: alphanumeric characters.

2. speed: (SPEED)

Data rate of associated communications equipment.

Legal values: 110, 300, 1200, 1800, 2400, 4800, 9600, 56000, 64000, null.

3. duplex: (DUPLEX)

Full or half-duplex.

Legal values: full, half, null.

4. ds_type: (DSTYPE)

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 Enter RS449 when the PC modem is a 500B data set.

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 2-5 lists which values are displayed for the set of equivalent values.

5. carrier: (CARRIER)

Continuous or switched carrier.

Legal values: c, s, null.

6. line_access: (LINEACCESS)

Type of line access.

Legal values: direct, private, noACU, ACU, null.

Table 2-5 Equivalent Values

Displayed Value Equivalent Values

703COU 703COU, 212A

703CCUL 703CCUL, 208A

703CCUH 703CCUH, 208B

703CDO 703CDO, 209A

RS232 RS232, RS449

RS422 RS422, RS423, NODS, NULL



7. mode_op: (MODEOP)

Mode operation. Block or send/receive mode of operation.

Legal values: b, s, null.

8. pdtime1: (PDTIME1) Required

Maximum time to wait for level 2 protocol acknowledgment. Values entered represent tenths of a second.

Legal values: 0 to 255, HEX.

9. pdtime2: (PDTIME2) Required

Maximum time to allow the data link to be idle. Values entered represent tenths of a second.


10. window: (WINDOW) Required

Maximum number of I-Frames a station may have outstanding.

Legal values: 0 to 7.

11. rexmit: (REXMIT) Required

Maximum number of retransmissions of an individual frame.


12. dcedte: (DCEDTE) Required

Data terminal equipment or data circuit-terminating equipment (DCE).

Legal values: 0 (data terminal equipment); 1 (data circuit-terminating equipment).

13. pcsd_stat: (PCSDSTAT)

Normal status for this pcsd.

Legal values: active (active device of duplex pair); standby (standby device of duplex pair); null.

14. config: (CONFIG)

Simplex, duplex, or multiple configuration.

Legal values: duplex (one of a duplex pair); null: multiple; simplex (simplex Peripheral Controller Subdevice or PCSD).

15. ldtel (LDTEL)

System identification (id), time limit, telephone number.

16. ldtel.sid (*LDTEL.SID[ROW])

System identifier.

Legal values: 0 to 65535, HEX, null.

Note A value of 65535 in row 1 will deactivate the Communications Protocol Handler (CPH) packet retransmission facility. This action will result in no packets being retransmitted. Any other value will result in the default action of retransmitting a packet up to two times by CPH.

17. ldtel.tlim (*LDTEL.TLIM[ROW])

Time limit (seconds).

Legal values: 0 to 255, HEX, null.



18. ldtel.telno (*LDTEL.TELNO[ROW])

Telephone number.

Legal values: alphanumeric or null.

19. security: (SECURITY)

Check security information.

Legal values: y, n, null.

20. link_id: (LINKID)

Link identification number.

Legal values: 0 to 7; default value: 0.

21. feid_len: (FEIDLEN)

Length of far-end system identifier.


22. neid_len: (NEIDLEN)

Length of near-end system identifier.


23. password_len: (PASSWORDLEN)

Length of password.


24. feid.fend (*FEID.FEND[ROW])

Far-end system identifier.

Legal values: 0 to 255, HEX, null; default value: 0.

25. neid.nend (*NEID.NEND[ROW])

Near-end system identifier.


26. pswrd.pwrd (*PSWRD.PWRD[ROW])

Password.


27. perm_state: (PERMSTATE) Required

Dialup permission state.

Legal values: allow (allow dialup connection); condalw (if duplex and primary not active; allow dialup connection); inhibit (inhibit dialup connection).

28. outscrsiz: (OUTSCRSIZ) Required

Output buffer area size (words).


Note When the size of the outscrsiz buffer is increased, the growth and degrowth procedures for the SDL must be followed. Failure to follow the procedures will cause the IOPs to initialize.



29. outpktsiz: (OUTPKTSIZ) Required

Data portion of output buffer (bytes).

Legal values: 0 to 640, 0x0 to 0x280, null.

30. inscrsiz: (INSCRSIZ) Required

Input buffer area size (words).


Note When the size of the inscrsiz buffer is increased, the growth and degrowth procedures for the SDL must be followed. Failure to follow the procedures will cause the IOPs to initialize.

31. inpktsiz: (INPKTSIZ) Required

Data portion of input buffer (bytes).


32. hup: (HUP)

Hang up on last close.

Legal values: y, n, null.

33. spckt: (SPCKT) Required

Link data packet size.


34. x3wsize: (X3WSIZE) Required

Level 3 protocol window size.


35. x3psize: (X3PSIZE) Required

Level 3 protocol packet size.

Legal values: 0 to 637, 0x0 to 0x27D, null.

36. x3pvcn.ldinno (*X3PVCN.LDINNO[ROW])

Logical channel number corresponding to the partition number.

Legal values: 0 to 4095, 0x0 to 0xFFF, null.

37. time_ti (TIMETI)

Interrupt packet timer.

Legal values: 180 to 600 seconds; default value: 180.

38. time_tj: (TIMETJ)

Reject packet timer.


39. time_tf: (TIMETF)

Flow control packet timer.




40. time_tl: (TIMETL)

Unacknowledged data packet timer.


41. time_td: (TIMETD)

Reset request timer.


42. time_ts: (TIMETS)

Restart request timer.


43. time_ack: (TIMEACK)

Acknowledgment timer.





C H A P T E R 3
Transmission Equipment in X.25 Environments



IntroductionThe data communications network (DCN) transports network management traffic between network elements and their respective Operations Support System (OSS), making them a vital link between the service network and the network operations center (NOC). The solutions presented in this chapter will help telcos migrate transmission equipment that use the X.25 protocol to a router-based TCP/IP network. The solutions in this chapter will help service providers migrate their OSSs with an X.25 interface onto a TCP/IP backbone.

This chapter presents the recommended Cisco architecture for building the router-based DCN. Several methods for implementing and scaling an IP network are included with detailed configuration examples. This chapter describes routing X.25 over an IP backbone using RFC 1613, or mediating between TCP/IP and X.25. In addition, the chapter describes ways to migrate the OSS from an X.25 to a TCP/IP interface. These architectures and software features are described in the following main sections:

• Cisco Network Solutions for the Telco DCN Transmission Equipment in X.25 Environments, page 3-2

• Migration Prerequisites, page 3-12

• TCP-to-X.25 Protocol Translation Between IP-Based Hosts and X.25 Interfaces, page 3-13

• Troubleshooting Telco Equipment in X.25 Environments, page 3-67

• Using Network Management Application Alarms to Identify System Problems, page 3-67

The solutions presented here use Cisco routers. Cisco routers can carry multiple protocols on a single DCN and reduce equipment costs, operations costs, and maintenance costs.



Chapter 3 Transmission Equipment in X.25 EnvironmentsCisco Network Solutions for the Telco DCN Transmission Equipment in X.25 Environments

Cisco Network Solutions for the Telco DCN Transmission Equipment in X.25 Environments

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, SONET/Synchronous Digital Hierarchy (SDH) add/drop multiplexers (ADMs), optical repeaters, digital loop carrier systems, digital cross-connect systems, high-data-rate digital subscriber line (HDSL) shelves, test heads, Frame Relay or ATM switches, routers, digital subscriber line access multiplexers (DSLAMs), and remote access switches 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.

The long-term goal of the services providers is to migrate their DCN to TCP/IP. Classic DCNs are typically X.25 networks. Figure 3-1 shows a traditional X.25 network.

Figure 3-1 Traditional X.25 DCN

Migration Requirements for a DCNThe first step in migrating to Cisco DCN solutions is to deploy a TCP/IP core network and run X.25 at the edges of the network, as shown in Figure 3-2. This step allows service providers to remove the X.25 network but leave OSSs and network elements unchanged.

1274

81

Lucent 5ESS


Monitoring

Provisioning X.25 switch

X.25 PAD

X.25 PAD

X.25 switchTrafficengineering

data

X.25backbone

X.25 PAD

SONET/SDH

Test head

Digitalloop carrier

HDSL shelf

X.25 PAD



Figure 3-2 Cisco XOT DCN Solution

The second step is to migrate the OSS to TCP/IP. Migrating the OSS to TCP/IP is easier than migrating the network elements to TCP/IP, because there are fewer OSSs than network elements. The Cisco IOS software provides X.25-to-TCP/IP mediation functions with its protocol translation and Record Boundary Preservation features. Protocol translation is typically used for mediation with transmission network elements, as shown in Figure 3-3, and works well with Transaction Language 1 (TL1), which is explained in more detail in the “TL1 in the Cisco Network” section on page 3-8.

Figure 3-3 Cisco Protocol Translation Solution

1274

82

Lucent 5ESS


Monitoring

Provisioning

X.25 TCP/IP or X.25 over IP X.25

Data centerrouter C

Data centerrouter D

Data centerrouter F

Trafficengineering

data

IPbackbone

CO router A

SONET/SDH

Test head

Digitalloop carrier

HDSL shelf

CO router B

1274

83

Lucent 5ESS


Monitoring

Provisioning

TCP/IP X.25

Data centerrouter C

Data centerrouter D

Data centerrouter F

Trafficengineering

data

IPbackbone

CO router A

SONET/SDH

Test head

Digitalloop carrier

HDSL shelf

CO router B



The third step is for the network elements themselves to migrate to Ethernet interfaces with TCP/IP stacks. This step in the migration process is shown in Figure 3-4.

Figure 3-4 Cisco IP End-to-End Solution

This chapter describes specific solutions for preserving the X.25 connection to transmission equipment as shown in Figure 3-2 and Figure 3-3. This chapter also describes how to scale XOT. Specific examples of implementing XOT are described in Chapter 2, “Telephone Switch Environments.” This chapter provides examples of connectivity with protocol translation, describes Class 5 switch connectivity, and provides examples of connectivity with XOT.

X.25 and LAPB Parameters for XOT and Protocol Translation

The “X.25 and LAPB Parameters” section in the “Telephone Switch Environments” chapter contains information about setting X.25 and Link Access Procedure, Balanced (LAPB) parameters and implementing XOT in the Cisco network. Tables in the appendix describe the LAPB and X.25 functions used when configuring a link, and list the Cisco IOS command counterparts next to the functions, along with default values and usage notes, in one place for easy reference.

Adding Cisco XOT to the DCN

The following guidelines offer a conservative approach to implementing XOT. The guidelines provide the ability to fall back to an original configuration if problems occur.

• The first step in implementing an XOT solution is to build an IP core.

1274

84

Lucent 5ESS


Monitoring

Provisioning

TCP/IP

Data centerrouter C

Data centerrouter D

Data centerrouter F

Trafficengineering

data

IPbackbone

CO router A

SONET/SDH

Test head

Digitalloop carrier

HDSL shelf

CO router B



• The next steps are to add access routers in the central office (also referred to as the CO), and locate access routers in front of the OSS, as shown in Figure 3-2. Add access ports for initial deployment, then add ports as the XOT network grows. If an X.25 packet assembler/disassembler (PAD) is in the central office, the service provider may choose to connect the X.25 PAD to the router. Eventually, the X.25 PAD is eliminated and the network element is connected directly to the router.

• Pretest configurations in a lab to determine that the class of Cisco router chosen has the CPU performance desired for each X.25 access point. You can select from Cisco 805, 1720, 2600 series, 2600 XM, 2800 series, 3640, 3660, 3725, 3745, 3825, and 3845 routers. XOT is a process-switched feature, which means the CPU must process every packet. Consider the following requirements and configuration options for each X.25 connection:

– What is the proposed speed of each X.25 connection?

– What size X.25 windows are you using (both in and out sizes)?

– What X.25 packet size are you using?

– What X.25 options do you want to negotiate?

– What filters do you want to use?

– What are the traffic volumes of each transaction, per router?

Before starting this task, you must have a clear idea of what X.25 network services are used on the X.25 public data network (PDN) connections. If the hosts are Cisco platform routers, or if Cisco equipment is providing X.25 switching, it is strongly recommended that the debug x25 EXEC command output be captured for representative sessions. If possible, similar system debugs should be obtained to gather specific configuration or operational information about the X.25 equipment. You should also review the contract with your X.25 PDN service provider, to determine if any nonstandard services are being used.

Note Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. The best situation is to collect the debug information in a lab.

In assessing the suitability of XOT for an implementation, an intermediate step of inserting a Cisco router between X.25 hosts or end devices and the existing X.25 PDN connection, and configuring the Cisco router to switch X.25 traffic, can be performed because, if the connectivity works when switching between two X.25 interfaces, it is likely to work for switched traffic between X.25 and XOT. This intermediate step assumes that the X.25 PDN is not providing a network service that Cisco has not implemented.

Cisco recommends that you introduce XOT in your network in stages while maintaining existing X.25 PDN connections. Depending upon services being used, it would then be possible to configure X.25 routing to use either the X.25 PDN or an XOT session based on a source or destination address or other possible criteria. Then migrate to XOT one class of user or access point at a time while monitoring connections and router performance for any problems. This approach should also provide an early warning if X.25 usage and traffic patterns present a scalability problem for the configured network.

Once it has been determined that XOT can handle the X.25 connectivity needs, the X.25 routing configuration commands that use the X.25 PDN can be removed from the configuration, and the router disconnected from that network.

A few other guidelines to consider are as follows:

• Make certain all X.25 functionality is placed in the access routers. Do not implement X.25 functionality in the core and distribution routers. The network should perform all XOT at the access layer using process switching. The core and distribution routers should perform routing of IP



packets only. This architecture facilitates simpler configurations and makes the XOT network easier to manage. Plus, this architecture pushes process switching to the edge of the network, which leaves a clean IP core.

• It is possible to simplify X.25 route statements in the access routers when X.25 addressing is laid out for summarization. What follows is an example of how X.121 addressing could be implemented. The example is based on the U.S. telephone numbering system.

An X.121 address is made up of an area code and a local office exchange. For example, a three-digit Area code, three-digit local code of Exchange, and two-digit port number on the Router combines for a total of eight digits in the pattern AAAEEERR.

From the data terminal equipment (DTE) address, you can determine the location of the equipment in the network, and two digits for subaddressing are still available. In addition, the addressing scheme allows for summarization of a collection of addresses on a router. This scheme minimizes the number of XOT routes in the router located in front of the OSS. Specifically for a route in a central office, the following addressing uses Area code 317 and the Exchange 855 where the central office resides. The first router in the building is numbered 01 and the ports are numbered XX.

AAAEEERRXX = 31785501XX

All of the routes to the first router can be summarized into one route using the x25 route command, as follows:

router C# configure terminalEnter configuration commands, one per line. End with CNTL/Z.router C(config)# x25 route 31785501 xot 192.168.100.1

An example network configuration is shown in Figure 3-5. The OSS is on the left side of the figure connected by X.25 to access routers in the data center. The middle portion of the diagram shows the IP backbone, which comprises a core set of routers and a set of distribution routers. The right side of the figure has two routers connected to various network elements in the central office. The X.121 address for the top router is 31785501. Basically, the router sits in the 317 area code in a central office with a local exchange number of 855 and the assigned router number. The first network element connected to the router is a SONET/SDH gateway network element (GNE) with the X.121 address of 3178550101. The last 01 represents the first connection on router 01.



Figure 3-5 Summarizing Routes to a Router

A single X.25 route can be entered into the data center routers to connect to all of the network elements to central office router 01. Following is the X.25 route statement that is configured for data center router 01 in Figure 3-5:

x25 route 31785501 xot 192.168.100.1

This statement directs all calls destined to router 01 in central office 317855. The route can be verified using the show x25 route EXEC command, as follows:

router C# show x25 route

# Match Substitute Route to match/use1 dest ^6242232001 Serial1/0 12/122 dest 317816 xot 192.168.100.1 0/03 dest 31785501 xot 192.168.100.1 0/0

Alternatively, you could use a parallel addressing scheme that incorporates both the new addressing scheme previously described and your current X.121 addressing scheme, to fall back on in the interim if needed.

• As implementations of XOT have grown, the number of static X.25 routes that must be maintained in access routers has also grown. The technique previously shown of summarizing routes is a helpful tool in reducing the number of route statements to maintain in a router, but you still must maintain access routes in multiple routers across the network. A feature to centralize the X.25 routing database has been developed for the DCN called DNS-Based X.25 Routing. More information can be found in the Cisco feature module titled “DNS-Based X.25 Routing” at the following URL: http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1830/products_feature_guide09186a00800879c8.html

What follows is an example of how to configure the feature. In the example, the customer can place the X.121 address in the A record of the DNS entry. The router is configured with a global x25 route command statement that points the router to the DNS, as follows:

x25 route ^.* xot dns \0

1274

85

Lucent 5ESS


Monitoring

Provisioning

Data centerrouter C

X.121: 40854701

Data centerrouter D

X.121: 40854702

Trafficengineering

data

IPbackbone

CO router 01X.121: 31785501

SONET/SDH3178550101

Test head3178550104

Digital loop carrier3178550102

HDSL shelf3178550103

CO router 023178550102

X.25 TCP/IP or X.25 over IP X.25

Data centerrouter F

X121: 40854701

Data centerrouter F

X.121: 40854703


http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1830/products_feature_guide09186a00800879c8.html



The x25 route command uses pattern matching and substitution. The caret (^) matches the beginning of the input string. The period (.) matches any single character including a space. The asterisk (*) matches zero or more occurrences of the preceding characters. The pattern in this example (^.*) matches the entire X.121 destination address beginning with the first character of the address. The pattern “\0” substitutes the destination X.121 address for the DNS string to look up. A detailed explanation of expression substitution can be found in a Cisco IOS chapter titled “Regular Expressions” at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/ftersv_c/ftsappx/tcfaapre.htm

The DNS address is configured using the ip name-server command. The ip name-server command identifies the IP address of the DNS that the router should send queries to. You can configure multiple DNS queries, as shown in the following example:

ip name-server 192.168.1.104ip name-server 192.168.20.104

• Remember to configure TCP keepalives in and out for the permanent virtual circuits (PVCs) and switched virtual circuits (SVCs) of the access (X.25) devices so that when a route (TCP connection) fails, a CLR message is sent on an SVC and a Reset message sent on a PVC. The following two commands tear down the TCP connection if the X.25 connection idles out or does not perform its clear call sequence appropriately.

service tcp-keepalives-in service tcp-keepalives-out

• Make sure that the OSS port, which is an aggregation of X.25 virtual circuits from X.25 terminals in the network, has a high-speed interface to ensure good throughput.

If you have more questions and can provide your network X.25 PDN details, Cisco support personnel can provide specific guidelines to help you. Also, see the “X.25 over TCP/IP” configuration example available at this link from the Cisco TAC website: http://www.cisco.com/warp/public/133/x25_over_tcpip.html

TL1 in the Cisco NetworkIn North America, service providers use TL1, a standard machine language, to communicate with network elements. More specifically, TL1 is used by the OSS to communicate to network elements. Bellcore developed the TL1 language and standard back in the early 1980s for the RBOCs, and defined the language in the Bellcore document GR-831-CORE. TL1 is an ASCII-based instruction set and is widely used in the North America for the management of transmission network elements. TL1 is not used for the management of Class 5 switches. A simple explanation of TL1 can be found at the following website: http://www.tl1.com/

For TL1, a semicolon terminates instructions and messages. From a Layer 3 perspective on a Cisco router, the semicolon terminator character can be used for mediating between TCP/IP and X.25. As stated previously, service providers migrate their DCN from an X.25 network to IP DCN in stages. The first stage is to install an IP backbone and run XOT across the DCN as shown in Figure 3-2. The second stage is to migrate the OSS to IP and mediate between IP and X.25 in the access router as shown in Figure 3-3.

One implementation issue that service providers encounter is the forwarding of complete TL1 messages. Some network elements will not accept a TL1 message split across multiple packets. The packet assembler/disassembler (PAD) feature in the Cisco IOS software is used in protocol translation sessions. PAD Parameter 3 is the Data Forwarding parameter. Cisco has implemented a value of 128 for this


http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/ftersv_c/ftsappx/tcfaapre.htm



http://www.cisco.com/warp/public/133/x25_over_tcpip.html

http://www.cisco.com/warp/public/133/x25_over_tcpip.html


parameter, which causes the router to forward data on receipt of a semicolon. In other words, as shown in Figure 3-6, the router will buffer incoming TL1 data in the TCP/IP packets and forward out on the X.25 side a complete TL1 message in an X.25 packet when a semicolon is received. (Cisco also implemented a value of 130 for PAD Parameter 3, which forwards data when either a semicolon or an ASCII carriage return is received.)

Figure 3-6 TL1 Translation in a Cisco Network

The following example shows the PAD profile for a router connected to a Fujitsu FLM:

x29 profile fujitsu 1:0 2:1 3:128 4:0

In this profile:

• Parameter 1 is PAD Recall Using a Character and determines whether the start-stop mode of the DTE is allowed to escape from data transfer mode to send PAD command signals. Parameter 1 is not supported for Telnet, so this parameter is set to the minimum of 0 (the default is 1).

• Parameter 2 is the Echo parameter, which determines if characters are locally echoed. Parameter 2 is set to 1, which sets local echo on.

• Parameter 3 was described earlier and in this profile is set to 128 (router forwards data on receipt of a semicolon).

• Parameter 4 is the Selection of Idle Timer Delay and selects the amount of time the PAD waits in 20ths of a second for additional data before forwarding data. When Parameter 4 is enabled and a data forwarding character is received, the data packet is forwarded immediately. The PAD profile for the router connected to the Fujitsu FLM has Parameter 4 is set to 0, which means that there is no timer; data will wait for the data forwarding character.

Documentation about the Cisco supported PAD parameters can be found in the Cisco IOS chapter “X.3 PAD Parameters” at this URL: http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca7e7.html#1026177

Protocol Translation as an X.25-to-TCP/IP Mediation FunctionMediation between TCP/IP and X.25 on a Cisco router is done by either protocol translation or record boundary preservation.

Note The Record Boundary Preservation feature was developed specifically for use with Lucent 5ESS and other Class 5 switches. The Class 5 switches do not use TL1 as their machine language, but instead have their own proprietary languages. The Record Boundary Preservation feature is described in Chapter 2, “Telephone Switch Environments.”

1275

01

IPbackbone

TCP session

TCP/IPOSS Fujitsu FLM

X.25 PVC

X.25

TCP out


TCP in


http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca7e7.html#1026177




We have already acknowledged that the long-term goal of service providers is to migrate their DCNs to TCP/IP, and that the first step is to migrate to a TCP/IP core network and run X.25. This first step allows removal of the X.25 network but leaves the OSSs and network elements unchanged.

The second step is to migrate the OSS to TCP/IP, which is easier than migrating the network elements to TCP/IP because, typically, the service provider has a smaller number of OSSs. Of the X.25-to-TCP/IP mediation functions offered by Cisco, protocol translation is used for mediation with transmission network elements, the main reason being that protocol translation works well with network elements using TL1. TL1 is described in the “TL1 in the Cisco Network” section on page 3-8. This section focuses on protocol translation as an X.25-to-TCP/IP mediation function.

To begin our understanding of protocol translation as an X.25-to-TCP/IP mediation function, we need to remember that every X.25 virtual circuit (VC) is translated to a separate TCP session, and each of those TCP sessions is terminated on the router. Look at the simple example shown in Figure 3-7.

Figure 3-7 Protocol Translation as an X.25-to-TCP/IP Mediation Function

In Figure 3-7, there are two OSSs and one craft access terminal communicating with four network elements that are connected to central office router A. The craft access terminal is a UNIX host that can connect to the X.25 SVCs configured for administrator access. The administrator access is a direct user interface to enter commands. In North America, those commands are entered using the TL1 language. In this example, there are three potential sessions to each network element for a total of 12 sessions. There could be 12 TCP sessions terminated on central office router A and translated to 12 X.25 VCs. Protocol translation uses a virtual terminal (vty) session to terminate each TCP session, and each translate statement requires a separate vty session.

Note A common mistake made when migrating to environments using protocol translation is to forget to increase the number of vty sessions. The Cisco IOS command parser does not check the number of available vty sessions and compare it to the number required to fulfill the protocol translation statement. There is no way for the Cisco IOS command parser to know how many protocol translation statements are concurrently invoked. When the router runs out of vty sessions, new Telnet sessions are rejected. It can be difficult to determine the source of the problem when a NOC complains that an application cannot connect. Typically, you assume that vty sessions are available, but you will need to add vtys.

1274

86

Monitoring

Provisioning

Craft access

Data centerrouter C

Data centerrouter D

IPbackbone

CO router A

SONET/SDH

Test head

Digital loop carrier

HDSL shelf

TCP/IP X.25



Going back to Figure 3-7, you need to add vty sessions into the configuration to accommodate the protocol translation sessions. The following example shows the command to add 12 vty sessions:

line vty 5 12

Another potential problem for service providers using protocol translation as an X.25-to-TCP/IP mediation function is for the packet sizes to be different between TCP/IP and X.25. The Cisco IOS software extracts the data from the TCP/IP packet based on the configured output packet size on the X.25 interface and adds a 3-byte header. Cisco IOS software sends the X.25 packet. If the data from the TCP/IP packet cannot be contained in one X.25 packet, the software sets the More bit in the X.25 packet. For example, if the software receives a 471-byte TCP payload and the X.25 interface is configured with an output packet size of 128, the software sends out four X.25 packets (three 128-byte and one 87-byte packet; the first three packets will have the More bit set).

Note The input and output packet sizes can be set within the Cisco IOS software. The commands for changing the X.25 packet sizes are described in the The “X.25 and LAPB Parameters” section in the “Telephone Switch Environments” chapter.

Protocol translation is process switched, so you will need to monitor the router CPU usage as the translation statements are added to the router. Each new connection or translate statement will add packets for the CPU to process.

The TCP sessions in protocol translation are terminated on the router. The IP address used with protocol translation cannot be an IP address assigned to an interface on the router. The Cisco IOS software will not allow this configuration. The IP address must be an unused address from a locally attached subnetwork. Service providers often choose an unused IP address from a locally attached Ethernet. The downside is that the connection will be lost if the Ethernet goes down. A better choice is to set up a subnetwork on a loopback interface and use a free IP address. A sample configuration for doing this follows:

interface Loopback0ip address 192.168.10.1 255.255.255.252

This example creates a small subnetwork. You would use the free IP address 192.168.10.1 for the translation statement. The interface will always be up unless you shut down the interface. You can check the interface status with the show interfaces EXEC command, as shown in the following example:

Router# show interfaces loopback 0

Loopback0 is up, line protocol is up Hardware is Loopback Internet address is 192.168.10.1/30 MTU 1514 bytes, BW 8000000 Kbit, DLY 5000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation LOOPBACK, loopback not set Last input never, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/0 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out


Chapter 3 Transmission Equipment in X.25 EnvironmentsMigration Prerequisites

Migration PrerequisitesBefore starting the tasks in the configuration sections, read the following paragraphs to understand Cisco software features that will help you configure your network:

• Asynchronous Console Configuration, page 3-12

• Protocol Translation Ruleset Feature, page 3-12

• Cisco X.25 Version Feature, page 3-12

Asynchronous Console ConfigurationBy default, Cisco routers do not accept incoming network connections to asynchronous ports (TTY lines). You must specify an incoming transport protocol, or specify the transport input all command before the line will accept incoming connections. For example, if you are using a Cisco router as a terminal server to make console-to-port connections to routers or other devices, you will not be able to use Telnet to connect to these devices. You will receive the message “Connection Refused.” See the Cisco IOS chapter “Configuring Terminal Operating Characteristics for Dial-in Sessions” at http://www.cisco.com/en/US/docs/ios/12_2/termserv/configuration/guide/tcftrmop.html for more information.

Protocol Translation Ruleset FeatureThe Protocol Translation Ruleset feature provides an effective method for creating Cisco IOS protocol translation configurations by defining a set of statements called a ruleset. The ruleset applies pattern matching and substitution technology to use incoming protocol elements, such as a destination address and port, to determine the outgoing protocol elements and translation options specified for originated connections. The ruleset also contains options to control the protocol translation sessions. The Protocol Translation Ruleset feature is especially useful for users that need to configure a large number of translate commands, because it makes it easy to create many individual translate configuration commands using a single ruleset-based command. You can learn more about this feature in the Cisco IOS Protocol Translation Ruleset feature module at this URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_8/gt_ptagg.pdf

Technical discussions about protocol translation and X.25 are popular threads on the Index of /news/cisco/cs/pt (protocol translation) and x25 (X.25) aliases. See the following links to get started:

http://topic.cisco.com/news/cisco/cs/pt/msg02598.html

http://topic.cisco.com/news/cisco/cs/x25/msg20160.html

Cisco X.25 Version FeatureBy default, Cisco IOS X.25 software conforms to the Consultative Committee for International Telegraph and Telephone (CCITT) 1984 X.25 recommendation. The Cisco IOS X.25 implementation was designed to conform to the CCITT 1984 X.25 recommendation, because the 1984 implementation represents the largest set of X.25 devices deployed at that time and because protocol conformance testing to the 1984 standard is readily available.


http://www.cisco.com/en/US/docs/ios/12_2/termserv/configuration/guide/tcftrmop.html




http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_8/gt_ptagg.htm

http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_8/gt_ptagg.htm

http://topic.cisco.com/news/cisco/cs/pt/msg02598.html

http://topic.cisco.com/news/cisco/cs/x25/msg20160.html

Chapter 3 Transmission Equipment in X.25 EnvironmentsTCP-to-X.25 Protocol Translation Between IP-Based Hosts and X.25 Interfaces

If your network employs devices that comply with the 1980, 1988, or 1993 X.25 recommendation, you will need to use the x25 version command to change the version for both X.25 class services such as X.25 and Connection-Mode Network Service (CMNS), and X.25 configuration profiles.

A common use of the x25 version command is to specify the 1980 X.25 behavior set to suppress the signaling of facilities that are not defined by that recommendation. This functionality benefits customers with an attached X.25 device that is not capable of correctly handling one or more of the facilities defined in the subsequent standards.

Note The Cisco IOS implementations of the 1980, 1988, and 1993 X.25 behavior sets have not been tested for compliance with the CCITT recommendations. For example, configuring an interface with the x25 version 1988 command will not necessarily create an interface that offers an X.25 connection that is in full compliance with the 1988 recommendation; it only enables select features from the 1988 standard that are supported by the Cisco IOS X.25 implementation. More information about this feature can be found in the Cisco IOS X.25 Version Configuration feature module at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_8/gtx25ver.pdf

TCP-to-X.25 Protocol Translation Between IP-Based Hosts and X.25 Interfaces

This section describes the tasks to configure a Cisco router to perform TCP-to-X.25 protocol translation between IP-based hosts and the following X.25 TL1 messaging maintenance interfaces:

• Fujitsu SONET GNE Protocol Translation Configuration, page 3-13

• ADC Soneplex Protocol Translation Configuration, page 3-20

• Alcatel Litespan Protocol Translation Configuration, page 3-27

• Alcatel 1603 SM Protocol Translation Configuration, page 3-33

• Alcatel 1633 SX DCS Protocol Translation Configuration, page 3-39

• Alcatel DCS-DEXCS Protocol Translation Configuration, page 3-45

• Tellabs Titan 5500 DCS via DCN Protocol Translation Configuration, page 3-50

• Applied Digital T3AS DCS via DCN Protocol Translation Configuration, page 3-57

• Wiltron Test System Protocol Translation Configuration, page 3-63

The Cisco IOS translation feature enables the OSS on the IP network to access an X.25 management interface, despite differences in the native protocol stacks. See the “Troubleshooting Telco Equipment in X.25 Environments” section on page 3-67 for information about verifying or troubleshooting your configurations.

Fujitsu SONET GNE Protocol Translation ConfigurationAs shown in Figure 3-8, the Cisco IOS protocol translation feature enables users on a TCP/IP network to access X.25 network elements, despite differences in the native protocol stacks.


http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123t/123t_8/gtx25ver.pdf



Figure 3-8 Protocol Translation Between IP Hosts and Fujitsu X.25 Interfaces

The monitoring OSS applications in this example are Telcordia’s Network Management Application (NMA) used for performance monitoring, and FlexR+, an element manager from Fujitsu used for provisioning.

Cable Requirements for the Fujitsu SONET GNE

The OSSI cable connects to (CN9) - FLM150ADM, (CN1) - FLM600ADM, or (CN9) - FLM2400ADM. This cable has a 37-pin (EIA/TIA) RS-449 male (DTE) connector on the Fujitsu end. See Table 3-1 and the “CONNECT OSS1 CABLES” section in the Fujitsu DLP installation manual for more information.

Set the DIP switch to OS in the SV module that is connected to the Cisco router. This DIP switch will also be set to OS in all other SV modules, unless a back-to-back cable is used to extend the SDCC between routes, although this configuration is not recommended under normal circumstances.

Provisioning the Fujitsu SONET GNE

The following steps show how to provision a Fujitsu SONET GNE to use X.25.

Note Before entering any command configuration information, contact the NMA database personnel to verify all pertinent information such as the Packet DTN or the IP address, the SCID, and the TIDs at both GNEs, if appropriate.

1274

87

Monitoring: NMA

Provisioning: FlexR

Craft access

Data centerrouter C

Data centerrouter D

IPbackbone

SONET/SDH

TCP/IP sessions are translatedto X.25 sessions in Router A

TCP/IP X.25

CO router A

RS449

Table 3-1 OSSI Cable Specification

Device Connector Part number Item number

TL1 CN9 / 37-pin, D-sub female, RS422/449

22-532-XXX 24AWG, 25 pr 999



Step 1 Log in to the element where the operations support system interface (OSSI) gateway will be established (either the primary or alternate GNE) using the following command:

COMMAND: ACT-USER

Tip Although this example uses TL1 commands, either TL1 or FlexR commands can be used for each of the following steps.

Step 2 Enter the following responses to the commands to set up OSSI for the OSSI port:

Changes do not take effect until the INIT-OSSI command is issued, as follows:

COMMAND: INIT-OSSI

When prompted, leave DL and NL blank, which defaults to both.

Step 3 This step sets up the virtual channel for OSSI ports. Ports 1 to 8 are PVCs; ports 9 to 16 could be set up as SVCs. At the primary gateway access, PVC numbers 1 to 4 will be built. At the alternate gateway, PVC numbers 5 to 8 will be built.

Step 4 All other fields need to be set to null when assigning PVCs. Changes do not take effect until the INIT-OSSI command is issued. This command must be issued after each PVC is added. Repeat this step for each of the PVCs. To delete an LCN, enter 0000000 in the PEER field.

Step 5 Enter the following responses to the commands to set up X.25 for the OSSI port:

COMMAND: ED-OSSI

TYPE: X.25 Layer 3

K: 7

T1: 3

N1: 1080

N2: 10

IS/OOS: IS

COMMAND: ED-VC

AID: 1 to 4 or 5 to 8 (the number of PVCs being added)

LCGN: 0

LCN: Logical channel number (LCN) of the VC being added, that is, the same as AID or 1 to 8

PEER: Peer address is a seven-digit number equal to the LCN being provisioned, for example: LCN1 = 1111111, LCN2 = 2222222, and so on

Type: PVC

COMMAND: ED-X.25

Addr: The DTN or IP address with socket number for the NMA address

Size: 128



Step 6 Any changes made do not take effect until the INIT-OSSI command is issued, as follows:

COMMAND: INIT-OSSI

When prompted, leave DL and NL blank, which defaults to both.

Step 7 After setting up the gateway OSSI (either primary or alternate), enter the following commands, and then make and keep a paper copy of the settings for future reference:

Step 8 Log out using the following commands (system reply prompts are also shown):

COMMAND: canc-user:(TID):UID:(ctag);

IP BC

<

FUJITSU 99-04-19 07:22:16

M BC COMPLD

This completes the steps for provisioning the Fujitsu SONET equipment for alarm reporting.

Configuring a Cisco Protocol Translation Router for the Fujitsu SONET GNE

This section describes the steps required to configure router A in the central office in Figure 3-8. The router is being configured to translate four TCP sessions into four PVCs.

Step 1 Use the show version EXEC command to verify that you are running Cisco IOS Release 12.1(16) or later release software that supports the Telco DCN functions. Protocol translation is supported in the Telco and Enterprise feature sets. The following partial example indicates the router is running Cisco IOS Release 12.3(12) of a Telco DCN feature set (see bold text):

router A# show version

Wdnw: 2

Dbit: N

T20: 180

T21: 200

T22: 180

T23: 180

CUG: Leave blank for PVCs. This field is used only when building SVCs.

LCRL: 1

LCRU: 8 (Note that Step 3 must be completed before this parameter can be changed from 255.)

COMMAND: RTRV-X25

COMMAND: RTRV-OSSI (State should be IS and Type should be X.25)

COMMAND: RTRV-VC



Cisco Internetwork Operating System Software IOS (tm) C2600 Software (C2600-TELCO-M), Version 12.3(12), RELEASE SOFTWARE (fc3)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2004 by cisco Systems, Inc.Compiled Mon 29-Nov-04 15:40 by kellythwImage text-base: 0x80008098, data-base: 0x81237034...


router A# configure terminal


router A(config)# x25 routing

Step 4 Set up a PAD profile statement. The PAD profile defines the control of information from the terminal to the PAD, which in this case is from the TCP session to the X.25 session, as follows:

router A(config)# x29 profile fujitsu 1:0 2:1 3:128 4:0


• Parameter 2 is the Echo parameter, which determines whether the characters are to be echoed locally. PAD Parameter 2 is set to 1, which sets the local echo on.

• Parameter 3 is the Data Forwarding parameter. Cisco has implemented a value of 128, which causes the router to forward data on receipt of a semicolon.

• Parameter 4 is the Selection of Idle Timer Delay and selects the amount of time the PAD waits in 20ths of a second for additional data before forwarding data. When Parameter 4 is enabled and a data forwarding character is received, the data packet is forwarded immediately. A value of 0 means that there is no timer; data will wait for the data forwarding character.

Step 5 Start interface configuration mode for loopback interface 0 and configure an IP address using the following commands:

router A(config)# interface loopback 0router A(config-if)# ip address 192.168.10.1 255.255.255.252


router A(config)# interface serial 3/3


router A(config-if)# shutdown

Step 8 Enter a description for the interface:

router A(config-if)# description SONET GNE1

Step 9 Remove the IP address from the interface, if it has one:

router A(config-if)# no ip address

Step 10 Remove IP-directed broadcasts from the interface:

router A(config-if)# no ip directed-broadcast




router A(config-if)# encapsulation x25 dce

Step 12 Configure the X.121 address on the serial interface. This address is the source X.121 address when a call is placed to the network element. Note that the network element can restrict which X.121 addresses that the network element will accept calls from, so be certain that the address you enter matches the expected source address.

router A(config-if)# x25 address 6242232001

Step 13 Configure the low two-way channel on the serial interface:

router A(config-if)# x25 ltc 9

Step 14 The router is functioning as the DCE device and must supply clock signaling to the DTE device. Set the clock rate to 9600 baud:

router A(config-if)# clockrate 9600


router A(config-if)# no shutdown

Step 16 Set up protocol translation statements to create PVCs 1 to 4 in global configuration mode:

router A(config)# translate tcp 192.168.10.2 port 2001 x25 6242232001 pvc 1 packetsize 128 128 windowsize 2 2 profile fujitsupvc max-users 1router A(config)# translate tcp 192.168.10.2 port 2002 x25 6242232001 pvc 2 packetsize 128 128 windowsize 2 2 profile fujitsupvc max-users 1router A(config)# translate tcp 192.168.10.2 port 2003 x25 6242232001 pvc 3 packetsize 128 128 windowsize 2 2 profile fujitsupvc max-users 1router A(config)# translate tcp 192.168.10.2 port 2004 x25 6242232001 pvc 4 packetsize 128 128 windowsize 2 2 profile fujitsupvc max-users 1

• The protocol translation statement maps the PVCs with IP address 192.168.10.2 and TCP ports 2001 to 2004. The TCP session is terminated on the router.

• The IP address is a free address on the subnetwork associated with the loopback interface. The IP address is used now by the router for protocol translation.

• The X.121 address of 6242232001 is used to map the PAD to serial interface 3/3. Note that the X.121 address is needed even though the translate statement configures a PVC, because this is the Cisco IOS mechanism used to direct the PAD to the correct interface.

• The X.25 packet size is set to 128 in and 128 out. The window size is set to 2 packets in and 2 packets out. The PAD profile name is fujitsupvc.

• The max-users option sets the number of simultaneous users that can use the command, and is set to 1.

Step 17 Create a route statement to map X.121 address 6142232001 to serial interface 3/3:

router A(config)# x25 route ^6142232001 interface serial 3/3

Step 18 Create additional vty sessions for the translate statements to use. The Cisco defaults are vty 0 to 4. Additional TCP sessions are denied after that number of sessions is exceeded.

Note Each vty consumes about 800 bytes of memory. Each translate statement requires a vty when open. The preferred transport protocol is Telnet.

router A(config)# line vty 5 15router A(config-line)# transport preferred telnet



Step 19 Exit the configuration modes and return to the EXEC prompt:

router A(config-line)# end

Step 20 Copy the running configuration to the startup configuration. This step saves the configuration in nonvolatile memory so that it is available the next time the router boots up:

router A# copy running-config startup-configDestination filename [startup-config]? Building configuration...[OK]

Testing Protocol Translation on the Fujitsu SONET GNE

This section describes how to establish a direct Telnet session to test the translate TCP port on router A. To establish a direct Telnet session for protocol translation, determine the IP address and TCP port number configured with the translate statement. In this example (see Figure 3-8), the configuration for PVC 1 uses IP address 192.168.10.2 and TCP port 4001.

Step 1 Initiate a Telnet session to IP address 192.168.10.2 and TCP port number 2001:

router A# telnet 192.168.10.2 2001Trying ... Open

Step 2 Type a TL1 command for this network element. This example uses the retrieve header command, which allows you to verify the connection.

Note The FLM ADM will not respond if the TID is not correct in the TL1 command.

rtrv-hrd:(TID)::(CTAG);

The output from the FLM is not displayed.

Step 3 Escape out of the Telnet session using the key sequence Ctrl-shift-^-x (simultaneously press and release the Ctrl, Shift, and 6 keys and then press the x key).

Step 4 The Telnet session is still active. Display active sessions on the router using the show sessions EXEC command:

router A# show sessions

Conn Host Address Byte Idle Conn Name* 1 192.168.10.2 192.168.10.2 0 0 192.168.10.2

Step 5 Use the disconnect command to disconnect the Telnet session from the translate IP address and port, and issue the show sessions command again to verify the connection is disconnected:

router A# disconnect


Conn Host Address Byte Idle Conn Name

The testing for PVC 1 is complete. Repeat steps 1 through 4 for the other three PVCs.



ADC Soneplex Protocol Translation ConfigurationThis section describes the steps required to configure a Cisco router to perform TCP-to-X.25 protocol translation between an IP-based OSS and the X.25-TL1 messaging maintenance interface on an ADC Soneplex. Figure 3-9 shows Soneplex connectivity in a Cisco network.

Figure 3-9 ADC Soneplex Connectivity

ADC Soneplex Cable Requirement

Figure 3-10 and Figure 3-11 show the front and back view of a Soneplex shelf. Port 3 on the back of the Soneplex is the Craft port that supports TL1 over X.25. Port 3 is used in the following configuration example, and is a standard (EIA/TIA) RS-232 interface. Table 3-2 lists the cable pinout for port 3.

Figure 3-10 ADC Soneplex Front View

1274

88

Monitoring: NMA

Craft access

Data centerrouter C

IPbackbone

Soneplex


TCP/IP X.25

1 PVC, 2 SVCs

CO router A

RS232



Figure 3-11 ADC Soneplex Rear View

For this configuration, monitoring of the network element is done by an NMA from Telcordia. The Soneplex in this example is assumed to be running version 5.x . A PVC is set up for monitoring the host NMA. Two SVCs are set up for Craft access.

Provisioning the ADC Soneplex

The following steps show how to provision the X.25 interface on an ADC Soneplex. Use communication port 3 on the Soneplex shelf for X.25 connectivity (reference ADC practice ADCP-61-311, DLP523).

Step 1 Start the task for provisioning the Soneplex X.25 interface by entering the main menu and logging in using the following username and password (all capital letters are required for these words):

User Name: SONEPLEXPassword : SONEPLEX1

Table 3-2 ADC Soneplex Port-3 Pinout

Connection Numbers at Port-3 Equipment End

PinNumber

LeadDesignation

1 FG

2 TD

3 RD

4 RTS

5 CTS

6 DSR

7 SG

8 DCD

15 TC

17 RC

20 DTR



Note the firmware version displayed on the Logon screen.

The system responds with the Soneplex main menu, as follows:

SONEPLEX MAIN MENU

1. Alarms

2. Display Status

3. Unit Configuration

4. System Administration

5. System Configuration

6. System Maintenance

7. Performance Monitoring

Step 2 From the main menu, choose 5, System Configuration. This action displays the following system configuration choices:

SYSTEM CONFIGURATION

1. System TID/Date/Time

2. Serial Port Configuration

3. X.25 Port Configuration

4. Shelf Housekeeping Labels

Step 3 Choose 3, X.25 Port Configuration. In this example, the data link or LAPB and X.25 layers are set up as follows:

Table 3-3 lists the network layer parameters that must be set for the Soneplex shelves running firmware versions 3.x. Version 3 of the firmware supports only one Craft port.

X.25 CONFIGURATION

Address Field Assignment DTE

Window Size 7

Frame Size 1080 bits

N2 7

T1 3 seconds

Table 3-3 Network Layer Parameters for Firmware Version 3.x

ParameterVirtual Circuit andLogical Channel 1

Virtual Circuit andLogical Channel 2

Application TL1 Craft

Packet Size 128 128

Window Size 2 2

D-bit Support No No

Keyboard Timeout Not applied 30 minutes



Table 3-4 lists the network parameters for the Soneplex shelves running firmware 5.x. Version 5 firmware supports one PVC and two SVCs. The two SVCs are Craft ports.

Configuring a Cisco Protocol Translation Router for the ADC Soneplex

This section describes the steps required to configure the central office router A in Figure 3-9. The router is being configured to convert one TCP session to PVC 1, and multiple TCP sessions to multiple SVCs.

Step 1 Use the show version EXEC command to verify that you are running Cisco IOS Release 12.1(16) or later release software that supports the Telco DCN functions. Protocol translation is supported in the Telco and Enterprise feature sets. The following partial example indicates the router is running Cisco IOS Release 12.3(12) of a Telco DCN feature set (see bold text) :



Step 2 Enter global configuration mode.


Step 3 Enable X.25 routing.


Step 4 Set up a PAD profile statement for the PVC that is used by the NMA. The PAD profile defines the control of information from the terminal to the PAD, which in this case is from the TCP session to the X.25 session.

Table 3-4 Network Layer Parameters for Firmware Version 5.x or Later Versions

Virtual Circuit 1 2 3

Circuit Type PVC SVC SVC

Logical Channel 1 — —

Application TL1 Not set Not set

Packet Size 128 128 128

Window Size 2 2 2

D-bit Support No No No

Keyboard Timeout Not set 30 minutes 30 minutes

SVC CRAFT ADDRESS

6142234000 Craft Dtn.

— —

SVC TL1 ADDRESS Leave blank — —



router A(config)# x29 profile soneplexpvc 1:0 2:1 3:128 4:0

• Parameter 1 is PAD Recall Using a Character and determines whether the start-stop mode of the DTE is allowed to escape from data transfer mode to send PAD command signals. PAD Parameter 1 is not supported for Telnet, so this parameter is set to the minimum of 0 (the default is 1).

• Parameter 2 is the Echo parameter, which determines whether the characters are to be echoed locally. Parameter 2 is set to 1, which sets the local echo on.

• Parameter 3 is the Data Forwarding parameter. Cisco has implemented value 128, which causes the router to forward data on receipt of a semicolon.

• Parameter 4 is the Selection of Idle Timer Delay and selects the amount of time the PAD waits in 20ths of a second for additional data before forwarding data. When Parameter 4 is enabled and a data forwarding character is received, the data packet is forwarded immediately. The value of 0 means that there is no timer; data will wait for the data forwarding character.

Step 5 Set up a PAD profile statement for the PVC that is used by NMA. The PAD profile defines the control of information from the terminal to the PAD, which in this case is from the TCP session to the X.25 session.

router A(config)# x29 profile soneplexsvc 1:0 2:1 3:2 4:2



• Parameter 3 is the Data Forwarding parameter and is set to 2, which will cause the router to forward data on receipt of an ASCII carriage return.

• Parameter 4 is the Selection of Idle Timer Delay and selects the amount of time the PAD waits in 20ths of a second for additional data before forwarding data. When Parameter 4 is enabled and a data forwarding character is received, the data packet is forwarded immediately. The value 2 means that the Cisco IOS software waits 2/20ths of a second before forwarding the data.

Step 6 Start interface configuration mode for loopback interface 0 and configure an IP address:







router A(config-if)# description Soneplex (RR and shelf)







Step 12 Configure X.25 DCE encapsulation on the serial interface. The Soneplex is the DTE. (Note that the encapsulation is at the X.25 layer, not the physical layer.)




Step 14 Configure the X.121 address on the serial interface. This is the calling address used when SVCs are created.




Step 16 Configure the X.25 idle timer, which is the period of inactivity after which the router can clear an SVC. The idle timer value is in minutes.

router A(config-if)# x25 idle 5



Step 18 Set up a protocol translation statement to create PVC 1 in global configuration mode:

router A(config)# translate tcp 192.168.10.2 port 4001 x25 6242235000 pvc 1 packetsize 128 128 windowsize 2 2 profile soneplexpvc max-users 1

• The protocol translation statement maps PVC 1 with IP address 192.168.10.2 and TCP port 4001. The TCP session is terminated on the router.



• The X.25 packet size is set to 128 in and 128 out. The window size is set to 2 packets in and 2 packets out. The PAD profile name is soneplexpvc.

• The max-users option sets the number of simultaneous users that can use the command, which is set to 1.

Step 19 Set up a protocol translation statement to create an SVC:

router A(config)# translate tcp 192.168.10.2 port 4002 x25 6142234000 profile soneplexsvc

• The protocol translation statement maps an SVC with IP address 192.168.10.2 and TCP port 4002. The TCP session is terminated on the router.


• The X.121 address of 6242234000 is used to map the PAD to serial interface 1/1. The X.121 address is the Cisco IOS mechanism used to direct the PAD to the correct serial interface.

• The PAD profile name is soneplexsvc.







Step 22 Create additional vty sessions for the translate statements to use. The Cisco defaults are vty 0 to 4. Additional TCP sessions are denied after that number of sessions is exceeded.





Step 24 Copy the running configuration to the startup configuration. This step saves the configuration in nonvolatile memory so that it is available the next time the router boots up.


Testing Protocol Translation on the ADC Soneplex

This section describes how to establish a direct Telnet session to test the translate TCP port on router A. To establish a direct Telnet session for protocol translation, determine the IP address and TCP port number configured with the translate statement. In this example (see Figure 3-9), the configuration for PVC 1 uses IP address 192.168.10.2 and TCP port 4001.


Router# telnet 192.168.10.2 4001Trying 192.168.10.2 ... Open

Step 2 Type a TL1 command for this network element. Begin by typing a semicolon (;):

;

The response should be as follows:

TID DATE TIMEM 0 DENYIPNV

Step 3 Log in by entering the following commands (use all capital letters when indicated):

act-user::SONEPLEX:CTAG::SONEPLEX1;

The response should be as follows:

TID DATE TIMEctag COMPLD“SONEPLEX”



Step 4 Log out of the Soneplex by entering the following commands (use all capital letters when indicated):

canc-user::SONEPLEX:ctag::SONEPLEX1;

Step 5 Escape out of the Telnet session using the key sequence Ctrl-shift-^-x (simultaneously press and release the Ctrl, Shift, and 6 keys and then press the x key):








The test is complete when the output of the show sessions command indicates that there are no connections.

Alcatel Litespan Protocol Translation ConfigurationThis section describes the steps to configure a Cisco router to perform TCP-to-X.25 protocol translation when you connect equipment to the X.25 maintenance port on an Alcatel Litespan digital loop carrier. Figure 3-12 shows a sample configuration.

Figure 3-12 Alcatel Litespan Protocol Translation

1274

89Monitoring: NMA

Craft access

Data centerrouter C

IPbackbone

Alcatel Lightspan


TCP/IP X.25

1 PVC, 4 SVCs

AMS

Litecraft

CO router A

RS232



The OSS is connected to the network via TCP/IP. The following section describes how to configure an Alcatel Litespan X.25-TL1 messaging maintenance interface. The Cisco IOS translation feature enables OSS users on one network to access network elements on another network, despite differences in the native protocol stacks.

The OSSs connecting to the Litespan are NMA, AMS, and Litecraft. The NMA system collects and analyzes information and alarms from the Litespan. The AMS and Litecraft applications use GUIs with the Litespan platform. Both interfaces provide a full complement of management functions for Operations, Administration, Maintenance, and Provisioning (OAM&P) using either a TCP/IP or an X.25 interface. The following procedure is based on the legacy X.25 management interface.

Provisioning the Alcatel Litespan

The following steps show how to provision the X.25 management port on the Alcatel Litespan device for one PVC and four SVCs.

Step 1 Log in to the Litespan 2000 by entering the following command:

ACT-USER::OPTILINK:::OPTILINK;

Step 2 Provision lower-level X.25 by entering the following commands:

ED-LLX25::COT-1-AUX2::::EXTERNAL,RS232,96,7,20,200,40,20,auto,active,10,10,disable,enable,,dte,on,standard;

CLOCK=EXTERNAL,

PHYSICALINTERFACE=RS232,

LINESPEED=96,

WINDOWSIZE=2,

TIMERT1=20,

TIMERT3=200,

TIMERT4=40,

COUNTERN2=20,

STARTMODE=AUTO,

CONNECTMODE=ACTIVE,

DCDPOLLTIMER=10,

DCDPOLLRETRY=10,

AUTOCALLMODE=DISABLE,

AUTOANSWERMODE=ENABLE,

DIALSTRING=,

TERMINALMODE=DTE,

AUTOCONFIG=ON,

NETWORKTYPE=STANDARD

Step 3 Provision upper level X.25 by entering the following commands. The Xs represent the X.25 DTN of the Litespan system.

ED-ULX25::COT-1-AUX2::::DTE,1,0,4,0,1,2,0,0,128,512,1984,3,0,XXXXXXXXXX ,2,1800,2000,1800,1800,0,0,0,1800;



LINETYPE=DTE,

NUMPVC=1,

NUMSVC2W=0,

NUMSVCIN=4,

NUMSVCOUT=0,

PVCLCNLOW=1,

SVCLCNLOWIN=2,

SVCLCNLOW2W=0,

SVCLCNLOWOUT=0,

DFLTPKLEN=128,

MAXPKLEN=512,

CCITTCONFORM=1984,

THROUGHCLSNEGO=3,

SETCUG=0,

DTEADDRESS=XXXXXXXXXX

L3WINDOWSIZE=2,

TIMERT20=1800,

TIMERT21=2000,

TIMERT22=1800,

TIMERT23=1800,

TIMERT24=0,

TIMERT25=0,

Step 4 Make the VCs active by entering the following command:

CONN-LLX25::COT-1-AUX2;

Step 5 Verify the VCs are active by entering the following command:

RTRV-COND-X25;

Step 6 Change the mode of the lower layer X.25 after the VCs have been made active by entering the following command:

ED-LLX25::COT-1-AUX2::::,,,,,,startmode=auto;

Step 7 Retrieve all parameters by entering the following commands, then make and keep a paper copy of the settings for future reference:

RTRV-LLX25::COT-1-AUX2;

RTRV-ULX25::COT-1-AUX2;

RTRV-COND-X25;

Step 8 Log out of the Litespan 2000 by entering the following command:

CANC-USER;



Configuring a Cisco Protocol Translation Router for the Alcatel Litespan

This section describes the steps required to configure router A in the central office in Figure 3-12. Router A is being configured to convert one TCP session to one PVC, and four TCP sessions to four SVCs.








Step 4 Set up a PAD profile statement for the PVC that is used by NMA. The PAD profile defines the control of information from the terminal to the PAD, which in this case is from the TCP session to the X.25 session.

router A(config)# x29 profile Litespanpvc 1:0 2:1 3:128 4:0

• Parameter 1 is PAD Recall Using a Character and determines whether the start-stop mode of the DTE is allowed to escape from data transfer mode to send PAD command signals. PAD Parameter 1 is not supported for Telnet, so this parameter is set to the minimum of 0 (the default is 1).



• Parameter 4 is the Selection of Idle Timer Delay and selects the amount of time the PAD waits in 20ths of a second for additional data before forwarding data. When Parameter 4 is enabled and a data forwarding character is received, the data packet is forwarded immediately. The value 0 means that there is no timer; the data will wait for the data forwarding character.

Step 5 Set up a PAD profile statement for the SVC that is used by NMA. The PAD profile defines the control of information from the terminal to the PAD, which in this case is from the TCP session to the X.25 session.

router A(config)# x29 profile Litespansvc 1:0 2:1 3:130 4:0





• Parameter 3 is the Data Forwarding parameter. Cisco has implemented value 130, which causes the router to forward data on receipt of a semicolon or an ASCII carriage return.

• Parameter 4 is the Selection of Idle Timer Delay and selects the amount of time the PAD waits in 20ths of a second for additional data before forwarding data. When Parameter 4 is enabled and a data forwarding character is received, the data packet is forwarded immediately. The value 0 means that there is no timer; the data will wait for the data forwarding character.








router A(config-if)# description Litespan





Step 12 Configure X.25 DCE encapsulation on the serial interface. The Litespan is the DTE. (Note that the encapsulation is at the X.25 layer, not the physical layer.)











router A(config)# translate tcp 192.168.10.2 port 4001 x25 6242233001 pvc 1 packetsize 128 128 windowsize 2 2 profile Litespanpvc max-users 1






• The X.25 packet size is set to 128 in and 128 out. The window size is set to 2 packets in and 2 packets out.

• The PAD profile name is Litespanpvc.


Step 18 Set up a protocol translation statement to create an SVC.

router A(config)# translate tcp 192.168.10.2 port 3001 x25 6142234000 profile Litespansvc




• The PAD profile name is Litespansvc.

Step 19 Create a route statement to map X.121 address 6142234000 to serial interface 1/1.




Step 21 Create additional vty sessions for the translate statements to use. The Cisco defaults are vty 0 to 4. Additional TCP sessions are denied after the number of sessions is exceeded.



Step 22 Exit the configuration modes and return to the EXEC prompt.






Testing Protocol Translation on the Alcatel Litespan

This section describes how to establish a direct Telnet session to test protocol translation and X.25 connectivity to the network element. To establish a direct Telnet session for protocol translation, determine the IP address and TCP port number configured with the translate statement. In this example (see Figure 3-12), the configuration uses IP address 192.168.10.2 and TCP port 4001.


router A# telnet 192.168.10.2 4001Trying 192.168.10.2 ... Open

Step 2 Type a TL1 command for this network element. The following example uses a semicolon (;), and system reply prompts are also shown:

;<<< RTRV-HRD:TID:::CTAG;










Alcatel 1603 SM Protocol Translation ConfigurationThis section describes the steps required for a Cisco router to perform TCP-to-X.25 protocol translation between an IP-based OSS and an Alcatel 1603 SM X.25-TL1 messaging maintenance interface, as shown in Figure 3-13.



Figure 3-13 Alcatel 1603 SM Protocol Translation

Figure 3-14 is a photo of the Alcatel 1603 SM OC-3/12 SONET multiplexer that can be configured to support OC-3 and OC-12 line rates from a single, compact, 10.5-inch shelf.

Figure 3-14 Alcatel 1603 SM OC-3/12 SONET Transport System

The management port is TL1 over X.25. The OSS in this example uses NMA for monitoring performance. NMA is a Telcordia product.

Cable Requirements for the Alcatel 1603 SM

The electrical interface to the Alcatel 1603 SM is an (EIA/TIA) RS-232 cable. Cisco cable part number CAB-232FC is required for the router end if the network module is an NM-4A/S or NM-8A/S. Because the Alcatel 1603 SM end is wire-wrapped, one end of the M25B will need a pig-tail cable, part number CAB2812F/BARE-1.5-SP. Wrap the wire according to the drawing in Alcatel practice 363-203-452, DLP124, page 4.

1279

67

Monitoring: NMA

Craft access

Data centerrouter C

IPbackbone


TCP/IP X.25

8 PVCsCO router A

RS232 1603 SM Sonet

1603 SM Sonet

1603 SM Sonet

1603 SM Sonet



Provisioning the Alcatel 1603 SM

The following steps show how to provision an Alcatel 1603 SM to use X.25.

Step 1 Set up the OSS port as follows:

PORT::x25PORT:CTAG:::BAUD=9600,BITS=8,PAR=NONE,SBITS=1,LWID=80, TYPE=VT100,ECHO=N:IS;

Step 2 Enter X.25 incoming service information:

ED-X25::X25:CTAG::::IS;

Step 3 Enter login information for NMA and TST at the local and remote nodes.

ENTER-SECU-USER:: followed by:NMAHOSP:CTAG::NMAHOS#1,,PCMAINT=7,PCPROV=,PCSECU=0,PCT EST=0:PAGE=0,UAGE=0,TDMIS=Y;then repeat with the following:ANTST:CTAG::ANTST%1,,PCMAINT=7,PCPROV=7,PCSECU=7,PCTEST=7:PAGE=0,UAGE=0, TDMIS=N;

Step 4 Edit the timeout information for the X.25 connection.

ED-SECU-CID::MAINT-OS:CTAG::,,,:TMOUT=0;

Step 5 Retrieve all parameters by entering the following statements:

RTRV-ATTR-PORT::ALL:CTAG;RTRV-ATTR-SDCC::ALL:CTAG;RTRV-COND-PORT::ALL:CTAG;RTRV-SECU-USER::ALL:CTAG;RTRV-SECU-CID::ALL:CTAG;RTRV-X25::X25:CTAG;

Configuring a Cisco Protocol Translation Router for the Alcatel 1603 SM

This section describes the steps required to configure router A in the central office in Figure 3-13. The router is configured to translate eight TCP sessions into eight PVCs.










Step 4 Set up a PAD profile statement for the PVCs that are used by the NMA and other applications. The PAD profile defines the control of information from the terminal to the PAD, which in this case is from the TCP session to the X.25 session.

router A(config)# x29 profile Alcatelpvc 1:0 2:1 3:128 4:0




• Parameter 4 is the Selection of Idle Timer Delay and selects the amount of time the PAD waits in 20ths of a second for additional data before forwarding data. If a data forwarding character is received, the data packet is forwarded immediately. The value 0 means that there is no timer, so the data will wait for the data forwarding character.








router A(config-if)# description Alcatel 1603





Step 11 Configure X.25 DCE encapsulation on the serial interface. The Alcatel 1603 SM is the DTE. (Note that the encapsulation is at the X.25 layer, not the physical layer.)








Step 14 Configure the low two-way channel on the serial interface. The following command defines a PVC range from 1 to 8 and the start of the SVC range at 9:




Step 16 Set up protocol translation statements to create eight PVCs in global configuration mode:

router A(config)# translate tcp 192.168.10.2 port 2001 x25 6242232001 pvc 1 packetsize 128 128 windowsize 2 2 profile Alcatelpvc max-users 1








• The protocol translation statements map PVCs 1 to 8 with IP address 192.168.10.2, and to TCP ports 2001 to 2008. The TCP session is terminated on the router.



• The X.25 packet size is set to 128 in and 128 out. The window size is set to 2 packets in and 2 packets out. The PAD profile name is Alcatelpvc.













Testing Protocol Translation on the Alcatel 1603 SM




Step 2 Type a TL1 command for this network element. This example uses the retrieve header command, which allows you to verify the connection:


The output from the Alcatel 1603 SM is not displayed.












Alcatel 1633 SX DCS Protocol Translation ConfigurationThis section describes the steps required to configure a Cisco router to perform TCP-to-X.25 protocol translation between an IP-based OSS and an Alcatel 1633 SX Digital Cross-Connect System (DCS) X.25-TL1 messaging maintenance interface, as shown in Figure 3-15.

Figure 3-15 Alcatel 1633 SX Protocol Translation

The Alcatel 1633 SX is a broadband DCS.

Cable Requirements for the Alcatel 1633 SX DCS

The Alcatel 1633 SX DCS is a DTE device with a 25-pin (EIA/TIA) RS-232 female connector. The tasks in this section assume an NM-4/AS or NM-8/AS network module is used. The network module requires Cisco cable part number CAB-232FC, or an equivalent synchronous null modem pinout cable when connected to the Cisco router. Only communication ports 2 and 3 can be configured for X.25. The Alcatel 1633 SX requires a 50-foot, 8-pair shielded cable (Alcatel part number 694-8483-00X).

Provisioning the Alcatel 1633 SX DCS

The following steps show how to provision an Alcatel 1633 SX DCS to use X.25. The steps set up eight SVCs. The command interface for the Alcatel 1633 SX DCS is case-sensitive and, unless otherwise indicated, requires commands be entered in capital letters.

Step 1 Set up the link:

COMMAND ED-CIDCPORT: 3OS: YBAUD: 9600AUTOIN: %

Step 2 Set up the communication port:

COMMAND: ED-CID-OSPORT

1279

68

Monitoring: NMA

OPS INE

Craft access

Data centerrouter C

IPbackbone


TCP/IP X.25

8 SVCs

1633SX

CO router A

RS232



CPORT: 3MODEM: NOSIZE: 128L3-WINDOW: 2K-WINDOW: 7HI-PVC: 0LO-IC-SVC: 1HI-IC-SVC: 8LO-2W-SVC: 8HI-2W-SVC: 8LO-OG-SVC: 8HI-OG-SVC: 8CTAG: (your initials)

Step 3 Set up the OS channel for SVCs 1 to 3:

COMMAND: ENT-CID-OSCHAN or ED-CID-OSCHANPORT: 3CHANNEL: 1 PROTOCOL: SVCLCN: (blank for SVC)AUTOLOGIN: %CTAG: (your initials)

COMMAND: ENT-CID-OSCHAN or ED-CID-OSCHANPORT: 3CHANNEL: 2 PROTOCOL: SVCLCN:v(blank for SVC)AUTOLOGIN: %CTAG: (your initials)

COMMAND: ENT-CID-OSCHAN or ED-CID-OSCHANPORT: 3CHANNEL: 3 PROTOCOL: SVCLCN: (blank for SVC)AUTOLOGIN: %CTAG: (your initials)

Step 4 Place the link in service:

COMMAND:RST-CIDCPORT: 3

Step 5 Configure NMA Logon Security:

COMMAND: ENT-USERUID: nmahos (lower case only)PWD: nmahost (lower case only)UCFCI: FUFCFO:vFAuth Level: 30OMODE: COSL: CMEPSUNAM: NMARUSURE: NODSKBFIND: ALWAYSTYPE: TTYDM: NOECHOOSTYPE: NMALNKTMR: 0LOTO: NKAMINTVL: 0MIPINTVL: 0



Step 6 Configure Operations System/Intelligent Network Elements (OPS/INE) Logon Security:

COMMAND: ENT-USERUID: opsine (lower case only)PWD: opsine#1 (lower case only) UCFCI: ZUFCFO: ZAuth Level: 28OMODE: COSL: BUNAM: OPSINERUSURE: NODSKBFIND: ALWAYSTYPE: TTYDM: NOECHOOSTYPE: OPSINELNKTMR: 0LOTO: NKAMINTVL: 0MIPINTVL: 0

Step 7 Set up the OS address for the NMA:

Command: ENT-OSADDR-SITEADDR: (Use main DTN address or CONET IP address and socket)

Autoin: nmahos (Automatically logs on to NMA when the link comes up and a call request is received, and a call clear is returned.)

Step 8 Set up the OS address for OPS/INE:

Command: ENT-OSADDR-SITEADDR: 1111111 Autoin: ospine (Automatically logs in OPS-INE when link comes up and a call request is received and a call clear is returned.)

Step 9 Set up the OS address setup for Craft:

Command: ENT-OSADDR-SITEADDR: 0Autoin: % (Requires manual logon when link comes up and a call request is received and a call clear is returned.)

Step 10 Enter the following commands to obtain the current parameter settings:

RTRV-CID:::ctag; (Retrieves link setups)RTRV-OSADDR-SITE::ctag; (Retrieves the site addresses entered)RTRV-PRVG-USER:::ctag; (Retrieves all user IDs and privileges for logon)

Step 11 Log off the system by entering the following command:

canc-user;



Configuring a Cisco Protocol Translation Router for the Alcatel 1633 SX DCS

This section describes the steps required to configure router A in the central office in Figure 3-15. The router is being configured to translate eight TCP sessions into eight SVCs.








Step 4 Set up a PAD profile statement for the PVCs that are used by NMA and other applications. The PAD profile defines the control of information from the terminal to the PAD, which in this case is from the TCP session to the X.25 session. The name of the PAD profile is 1633SXSVC.

router A(config)# x29 profile 1633SXSVC 1:0 2:1 3:130 4:0



• Parameter 3 is the Data Forwarding parameter. Cisco has implemented value 130, which causes the router to forward data on receipt of a semicolon or ASCII carriage return.

• Parameter 4 is the Selection of Idle Timer Delay and selects the amount of time the PAD waits in 20ths of a second for additional data before forwarding data. If a data forwarding character is received, the data packet is forwarded immediately. The value 0 means that there is no timer, so the data will wait for the data forwarding character.










router A(config-if)# description Alcatel 1633SX





Step 11 Configure X.25 DCE encapsulation on the serial interface. The Alcatel 1633 SX DCS is the DTE. (Note that the encapsulation is at the X.25 layer, not the physical layer.)




Step 13 Configure the X.121 address on the serial interface. This allows the calling address to be used when SVCs are created.


Step 14 Configure the X.25 idle timer, which is the period of inactivity after which the router can clear an SVC. The idle timer value is in minutes.




Step 16 Set up a protocol translation statement to create the SVC in global configuration mode:

router A(config)# translate tcp 192.168.10.2 port 3000 x25 6142233001 profile 1633SXSVC

• The translate statement maps an SVC with IP address 192.168.10.2 and TCP port 3000. The TCP session is terminated on the router.

• The IP address is a free address on the subnet associated with the loopback interface. The IP address is used now by the router for protocol translation.

• The X.121 address of 6242233001 is used to map the PAD to serial interface 1/1.

• The PAD profile name is 1633SXSVC.

Step 17 Create a route statement to map X.121 address 6142233001 to serial interface 1/1 in global configuration mode:











Testing Protocol Translation on the Alcatel 1633 SX DCS






The output from the Alcatel 1633 SX DCS is not displayed.










The final test is to have the NMA or OPS/INE establish a call, make a connection, and complete a command to the Alcatel 1633 SX DCS.



Alcatel DCS-DEXCS Protocol Translation ConfigurationThis section describes the steps required for a Cisco router to perform TCP-to-X.25 protocol translation between an IP-based OSS and an Alcatel DCS-DEXCS X.25-TL1 messaging maintenance interface, as shown in Figure 3-16.

Figure 3-16 Alcatel DCS-DEXCS Protocol Translation

The DSC-DEXCS is a family of products that provide cross-connect capability at the DS0 level for DS1, DS3, and STS1 signals; see Figure 3-17.

Figure 3-17 Alcatel DCS-DEXCS

1279

69

Monitoring: NMA

OPS INE

Craft access

SARTS

Data centerrouter C

IPbackbone


TCP/IP X.25

SVCs

Dexcs

CO router A

RS232



The monitoring host in this example is running Telcordia’s NMA application. The provisioning host is running Telcordia’s Operations System/Intelligent Network Elements (OPS/INE) application. Switched Access Remote Test System (SARTS) provides the test access and control links that interface to Digital Cross-Connect Systems or Digital Test Access Units.

Cable Requirement for the Alcatel DCS-DEXCS

Connect LINK J42 (a DTE male connector) from the Alcatel DCS-DEXCS using a Cisco CAB-232 FC cable or equivalent null modem cable to the router X.25 (EIA/TIA) RS-232 port. Table 3-5 lists the specifications and part numbers.

Provisioning the Alcatel DCS-DEXCS

The following steps show how to provision an Alcatel DCS-DEXCS to use X.25. The steps set up SVCs. The Alcatel DCS-DEXCS system software is case-sensitive and requires that commands be entered in capital letters.

Step 1 Enable the X.25 feature:

Command: UTL SET FEATURE SIO1 X25

Step 2 Provision (grow) the links:

Command: GRTH LINK 6 9600 0 0 0 SVC<CR>Command: UTL SET LINK 17 9600 0 0 0<CR>Command: UTL SET LINK 18 9600 0 0 0<CR>Command: UTL SET LINK 19 9600 0 0 0<CR>Command: UTL SET LINK 20 9600 0 0 0<CR>

Step 3 Reboot the Alcatel DCS-DEXCS so the X.25 configuration takes effect:

Command: RMV MS Command: RST MS CLR

Note If the Alcatel DCS-DEXCS is carrying traffic, this procedure must be performed only during the maintenance window.

Step 4 Set the Alcatel DCS-DEXCS internal and external addresses::

Command: UTL SET DTEADR INT SIO1 adr;ADR: USE DTN or IP address and socket# ASSIGNED TO NMA for DEXCS Command: UTL SET DTEADR EXT NMA adr;ADR: ENTER ADDRESS USED IN AI ALIAS FOR CALLER'S NUMBER IN LINE 7, MENU 9 (MAIN DTN# OF Router)

Command: UTL SET DTEADR EXT OPSINEADR;1111111<CR>

Command: UTL SET DTEADR EXT CRAFT ADR;123<CR>

Table 3-5 Alcatel DCS-DEXCS Cable Specification

Device Connector Cable

TL1 J42 (DTE) or J43 (DCE) / RS-232C DB25-pin P/N 452-0000-097



Step 5 Set the SARTS protocol features in the Alcatel DCS-DEXCS:

Command: UTL SET FEATURE LINKS EOMT<CR>UTL SET FEATURE SIOCMD DKPT<CR>RMV SIO 1RST SIO 1

Step 6 Configure NMA Logon Security:

Command: ASN USER 102 LOGON nma nma134<CR>Command: ASN USER 102 POOL 1-255<CR>Command: UTL SET USER 102 CLASS 7,8,9,11,12,13,14,15,16< cr >

Step 7 Configure OPS/INE Logon Security:

Command: ASN USER 101 LOGON opsine opsineCommand: ASN USER 101 POOL 1-255Command: UTL SET USER 101 CLASS 2,3,4,5,6,7,8,9,10,11,12,13,14,15,16<CR>

Step 8 Configure SARTS Logon Security:

Command: ASN USER 103 LOGON sarts sarts<CR>Command: ASN USER 103 POOL 1-255Command: UTL SET USER 103 CLASS 9,10,11,12,13,16<CR>

Step 9 Enter the following commands to retrieve settings. Make and keep a paper copy of the settings for future reference.

DISPLAY LINK 1-6<CR>DISPLAY LINK 17 20UTL QRY ASN USER 101-103<CR>UTL SET FEATURE STATUS ALL<CR>UTL QRY ASN USER 101-103<CR>UTL QRY DTEADR ALL

Configuring a Cisco Protocol Translation Router for the Alcatel DCS-DEXCS

This section describes the steps required to configure router A in the central office in Figure 3-16. The router is being configured to translate TCP sessions into SVCs.










Step 4 Set up a PAD profile statement for the SVCs that are used by NMA, SARTS, and OPS/INE applications. The PAD profile defines the control of information from the terminal to the PAD, which in this case is from the TCP session to the X.25 session.

router A(config)# x29 profile DEXCS 1:0 2:1 3:64 4:0



• Parameter 3 is the Data Forwarding parameter, and is set to a value of 64, which will cause the router to forward data upon receipt of an ASCII special character other than ESCAPE, BEL, ENQ, ACK, DEL, CAN, DC2, ETX, EOT HT, LT, VT, or FF.

• Parameter 4 is the Selection of Idle Timer Delay and selects the amount of time the PAD waits in 20ths of a second for additional data before forwarding data. If a data forwarding character is received, the data packet is forwarded immediately. The value 0 means that there is no timer, so data will wait for the data forwarding character.

Step 5 Start interface configuration mode for loopback interface 0 and configure an IP address using the following commands:







router A(config-if)# description Alcatel DEXCS





Step 11 Configure X.25 DCE encapsulation on the serial interface. The Alcatel DCS-DEXCS is the DTE. (Note that the encapsulation is at the X.25 layer, not the physical layer.)








Step 14 Configure the X.25 idle timer, which is the period of inactivity after which the router can clear an SVC. The idle timer value is set in minutes.




Step 16 Set up a protocol translation statement to create SVCs in global configuration mode:

router A(config)# translate tcp 192.168.10.2 port 3000 x25 6142233000 profile DEXCS




• The PAD profile name is DEXCS.








Step 20 Copy the running configuration to the startup configuration. This step saves the configuration in nonvolatile memory so that it is available the next time the router boots up:


Testing Protocol Translation on the Alcatel DCS-DEXCS

This section describes how to establish a direct Telnet session to test protocol translation and X.25 connectivity to the network element. To establish a direct Telnet session for protocol translation, determine the IP address and TCP port number configured with the translate statement. In this example (see Figure 3-16), the configuration uses IP address 192.168.10.2 and port number 3000.





Step 2 Type TL1 commands for the network element.

DISPLAY LINK 1-6<CR>DISPLAY LINK 17 20UTL QRY ASN USER 101-103<CR>UTL SET FEATURE STATUS ALL<CR>UTL QRY ASN USER 101-103<CR>UTL QRY DTEADR ALL





Step 5 Use the disconnect command to disconnect the Telnet session from the translate IP address and port, and issue the show sessions command again to verify the connection is disconnected, as follows:





The final test is to have NMA and OPS/INE establish a call, make a connection, and complete a command to the DEXCS.

Tellabs Titan 5500 DCS via DCN Protocol Translation ConfigurationThis section describes the steps required for a Cisco router to perform TCP-to-X.25 protocol translation. For this task, the OSS is connected via TCP/IP to the DCN. The Tellabs Titan 5500 DCS is connected to the DCN via the X.25-TL1 messaging maintenance interface, as shown in Figure 3-18.



Figure 3-18 Tellabs Titan 5500 Protocol Translation

The TITAN 5500 is a DCS that can terminate any mix of DS1, DS3, STS-1, OC-3, and OC-12 signals.

The monitoring host in this example is running Telcordia’s NMA application. The provisioning host is running Telcordia’s OPS/INE application. SARTS provides the test access and control links that interface Digital Cross-Connect Systems or Digital Test Access Units.

Cable Requirements for the Tellabs Titan 5500 DCS

The cabling assumes that the service provider is connecting to a NM-4/AS or NM-8/AS. If you use a different Cisco network module, a different Cisco cable will be required. The Tellabs cable, part number 50-0493, is required if the Admin backplane is revision D or lower. This cable swaps pins 14 and 16 to 15 and 17 for timing. Connect the 50-0493 cable to the router cable (CAB-232FC) between Link 4A (J13) on the Tellabs Titan 5500 DCS and available X.25/RS-232 ports on the router. Use the other 50-0493 cable and CAB-232FC cable for Link 8B (J13) on the Tellabs Titan 5500 DCS.

Note P1 on the 50-0493 must be connected to the Tellabs Titan 5500 DCS end, with P2 connected to the router cable.

Verify that jumpers J6 and J7 on the APM Module (81.5501A) have pins 2 and 3 jumpered together. Check both Admin complexes APMs A and B.

Provisioning the Tellabs Titan 5500 DCS

The following steps show how to provision the X.25 management link on a Tellabs Titan 5500 DCS and set up SVCs.

Step 1 Set up the link:

Command: ED-LINKLINK# LINK-4 (and repeat for LINK-8)SYBAUD: 9600

1279

70

Monitoring: NMA

OPS INE

Craft access

SARTS

Data centerrouter C

IPbackbone


TCP/IP X.25

SVCs

Titan 5500

CO router A

RS232



PVCS: 0SVCS: 8SYCLK: TEREFMWIN: 7T1: 30T4: 20N2: 7FMMODE: DTEPKWIND: 2PKWINM: 2PKSIZD: 128PKSIZM: 128DBIT: OFFPKMODE: DTEPST: IS

Step 2 Set up the X.25 channel:

COMMAND: ED-SECU-CHANCHAN# CHAN-4-1&&-8 (Repeat for CHAN-8-1&&-8)CAPC: A9CTYPE: OSS-SECURE

Step 3 Set up the X.25 links in service:

COMMAND: ED-LINK::LINK-4:CTAG:::IS; (Repeat for Link 8)

Step 4 Enter logons for NMA, SARTS, and OPS/INE:

COMMAND: ENT-SECU-USERUID: NMAHOSPWD: NMAHOS%1UPC: A6

ENT-SECU-USER::NMAHOS:CTAG::NMAHOS%1,,UPC=A6;

COMMAND: ENT-SECU-USERUID: OPSINEPWD: OPSINE#1UPC: A6

ENT-SECU-USER::OPSINE:CTAG::OPSINE#1,,UPC=A6

COMMAND: ENT-SECU-USERUID: ANTSTPWD: ANTST%1UPC: A9

ENT-SECU-USER::ANTST:CTAG::ANTST%1,,UPC=A9

COMMAND: ENT-SECU-USERUID: TCENTERPWD: CENTER%1UPC: A2

ENT-SECU-USER::TCENTER:CTAG::CENTER%1,,A2;

COMMAND: ENT-SECU-USERUID: SARTSPWD: SARTS%1UPC: A4

ENT-SECU-USER::SARTS:CTAG::SARTS%1,,UPC=A4;



Step 5 Retrieve all setups by entering the following commands. Make and keep a paper copy of the settings for future reference:

RTRV-LINK::LINK-4:CTAG;RTRV-LINK::LINK-8:CTAG;RTRV-SECU-USER:::CTAG;RTRV-SECU-CHAN::CHAN-4-1&&-8:CTAG;RTRV-SECU-CHAN::CHAN-8-1&&-8:CTAG;

Configuring a Cisco Protocol Translation Router for the Tellabs Titan 5500 DCS

This section describes the steps required to configure router A in the central office in Figure 3-18. The router is being configured to translate TCP sessions into SVCs. The Tellabs Titan 5500 DCS has two ports for Operation, Administration, and Maintenance (OAM). The ports back up each other.








Step 4 Set up a PAD profile statement for the SVCs that are used by NMA, SARTS, and OPS/INE applications. The PAD profile defines the control of information from the terminal to the PAD, which in this case is from the TCP session to the X.25 session. The name of the PAD profile is Titan.

router A(config)# x29 profile Titan 1:0 2:1 3:64 4:0



• Parameter 3 is the Data Forwarding parameter, and is set to a value of 64, which will forward data upon receipt of an ASCII special character other than ESCAPE, BEL, ENQ, ACK, DEL, CAN, DC2, ETX, EOT HT, LT, VT, or FF.











router A(config-if)# description Tellab Titan 5500





Step 11 Configure X.25 DCE encapsulation on the serial interface. The Tellabs Titan 5500 DCS is the DTE. (Note that the encapsulation is at the X.25 layer, not the physical layer.)






Step 14 Configure the X.25 idle timer, which is the period of inactivity after which the router can clear an SVC. The idle timer value is configured in minutes.




Step 16 Start interface configuration mode for serial interface 1/2, which specifies network module 1, port 2. This port backs up serial interface port 1/1.





router A(config-if)# description Tellab Titan 5500 backup port







Step 21 Configure X.25 DCE encapsulation on the serial interface. The Tellabs Titan 5500 is the DTE. (Note that the encapsulation is at the X.25 layer, not the physical layer.).






Step 24 Configure the X.25 idle timer, which is the period of inactivity after which the router can clear an SVC. The idle timer value is set in minutes.




Step 26 Set up a protocol translation statement to create SVCs in global configuration mode:

router A(config)# translate tcp 192.168.10.2 port 3000 x25 6142233001 profile Titan


• The IP address is a free address on the subnet associated with the loopback interface. The IP address is now used by the router for protocol translation.


• The PAD profile name is Titan.

Step 27 Set up a second protocol translation statement to create SVCs:

router A(config)# translate tcp 192.168.10.2 port 3000 x25 6142234001 profile Titan

• This second translate statement allows serial interface 1/2 to back up serial interface 1/1. The first translate statement ensures that Cisco IOS hosts will be executed. If serial interface 1/1 is down, this second translate statement is executed (once serial interface 1/2 is up).

• The translate statement also maps an SVC with IP address 192.168.10.2 and TCP port 3000. The TCP session is terminated on the router.



• The PAD profile name is Titan.














Testing Protocol Translation on the Tellabs Titan 5500 DCS

This section describes how to establish a direct Telnet session to test protocol translation and X.25 connectivity to the network element. To establish a direct Telnet session for protocol translation, determine the IP address and TCP port number configured with the translate statement. In this example (see Figure 3-18), the configuration uses IP address 192.168.10.2 and port number 3000.



Step 2 Type a TL1 command for the network element:

RTRV-LINK::LINK-4:CTAG;












The final test is to have NMA and OPS/INE establish a call, make a connection, and complete a command to the Tellabs Titan 5500 DCS.

Applied Digital T3AS DCS via DCN Protocol Translation ConfigurationThis section describes the steps required for a Cisco router to perform TCP-to-X.25 protocol translation. For this task, the OSS is connected via TCP/IP to the DCN. The Applied Digital T3AS DCS is connected to the DCN via the X.25-TL1 messaging maintenance interface, as shown in Figure 3-19.

Figure 3-19 Applied Digital T3AS Protocol Translation

The Applied Digital T3AS Digital Cross-Connect System (DCS) Test and Performance Monitoring System is designed to enable both Local Exchange Carriers (LECs) and Inter-exchange Carriers (IECs) to focus attention on enhancement of network quality, revenue generation from new services, and reduction of overall network management expense. The system provides detailed performance monitoring of DS3, DS2, and DS1 signals, and supports DS1, DS0, and subrate signal intrusive and nonintrusive testing.

The NMA system collects and analyzes information on network alarms and performance data. SARTS provides the test access and control links that interface to Digital Cross-Connect Systems or Digital Test Access Units; see Figure 3-20.

1279

71

Monitoring: NMA

OPS INE

Craft access

SARTS

Data centerrouter C

IPbackbone


TCP/IP X.25

SVCs

T3AS

CO router A

RS232



Figure 3-20 SARTS Switched Access Remote Test System

The setup shown in Figure 3-20 is for a synchronous TL1 interface between the Applied Digital T3AS DCS and a Cisco router. Figure 3-21 shows the central office configuration using a Cisco 3662 router.

Figure 3-21 Applied Digital T3AS DCS Central Office Configuration

Cable Requirements for the Applied Digital T3AS DCS

Use a Cisco CAB-232-FC cable connected to port 9 on the Applied Digital T3AS DCS as shown in Table 3-6.

Table 3-7 lists the TL1-to-X.25 pin arrangement.

1279

72

SARTS system

Test center

Test system

ControllerSARTS

Model T38Adigital accesstest system

RouterX.25

Database

IPTL1

1

144

IO DSLcircuits

X25TL1

NMS system

Communication lines Digital offices

1279

73

To Network Management NMAand SARTS

Applied DigitalAccess Test System

T3AS

T1s

X.25RS232

Serial interface 3/3

3662-DC-CO

Table 3-6 Applied Digital T3AS DCS Cable Specification

Cable Type Specification

DB25 (Male) RS-232/ASYNC or SYNCH25 conductor cable



An asynchronous port is used for configuration of X.25.

Table 3-8 indicates the TL1 asynchronous 25-pin arrangement.

Table 3-7 TL1-to-X.25 Pin Arrangement

J920 (Connector Number at Equipment End)Pin Number Lead Designation

P9-12(Connector Number at CA Assembly End to X.25 Network)Pin Number

1 SHLD 1

15 TXC 15

16 — —

4 RTS 4

17 RXC 17

5 CTS 5

18 — —

6 DSR 6

7 TXCOM 7

20 DTR 20

9 — —

22 — —

10 — —

11 — —

24 — —

12 — —

25 — —

8 RLSD 8

3 +RXD 3

2 +TXD 2

Table 3-8 TL1 Asynchronous 25-pin Arrangement

PinNumber

LeadDesignation Connection Number

PinNumber

1 SHLD P1-4 1

2 +TXD P1-4 2

3 +RXD P1-4 3

4 RTS P5-8 4

5 CTS P5-8 5

6 DSR P5-8 6



Provisioning the Applied Digital T3AS DCS

The following steps show how to provision the X.25 management link on an Applied Digital T3AS DCS and set up SVCs.

Step 1 Log in to the Applied Digital T3AS DCS:

< logon; systemPassword: GOLD3+

Step 2 Edit the local network address for the NMA:

< ed-local-netaddr::50::::,50;< ed-local-netaddr::50::::,,xxxxxxxxxx; (DTN# or IP address and socket#)

Step 3 Edit the local network address for the SARTS:

< ed-local-netaddr::56::::,56;< ed-local-netaddr::56::::,,xxxxxxxxxx; (DTN# or IP address and socket #)

Step 4 Edit the local network address for Craft access:

< ed-local-netaddr::42::::,42;< ed-local-netaddr::42::::,,xxxxxxxxxx; (Craft alias T3ASRRxxxxxxx(where xxxxxx is RR, floor, and bay information)

Step 5 Retrieve the Applied Digital T3AS DCS parameters. Make and keep a paper copy for future reference.

rtrv-packet::9;rtrv-eqpt::2-3;;rtrv-port::9;rtrv-local-netaddr::42&&56;rtrv-peer::50; (NMA)rtrv-peer::52; (SARTS)rtrv-peer::55; (VDT)

Configuring a Cisco Protocol Translation Router for the Applied Digital T3AS DCS

This section describes the steps required to configure the central office router A in Figure 3-19. The router is being configured to translate TCP sessions into SVCs.

7 SGND P5-8 7

20 DTR P5-8 20

1 SHLD P5-8 1

2 +TXD P5-8 2

3 +RXD P5-8 3

Table 3-8 TL1 Asynchronous 25-pin Arrangement

PinNumber

LeadDesignation Connection Number

PinNumber







router A# configure terminalrouter A(config)#








router A(config-if)# description T3SA





Step 9 Configure X.25 DCE encapsulation on the serial interface. The Applied Digital T3AS DCS is the DTE. (Note that the encapsulation is at the X.25 layer, not the physical layer.)




Step 11 Configure the X.25 idle timer, which is the period of inactivity after which the router can clear an SVC. The idle timer value is configured in minutes.







router A(config if)# exit

Step 14 Set up a PAD profile statement for the SVCs in global configuration mode. The PAD profile defines the control of information from the terminal to the PAD, which in this case is from the TCP session to the X.25 session. The name of the PAD profile is Titan.

router A(config)# x29 profile T3SAsvc 1:0 2:1 3:128 4:0





Step 15 Set up a protocol translation statement to create SVCs:

router A(config)# translate tcp 192.168.10.2 port 3000 x25 6142233001 profile T3SAsvc


• The IP address is a free address on the subnet associated with the loopback interface. The IP address is now used by the router for protocol translation.


• The PAD profile name is T3SAsvc.



Step 17 Exit the configuration modes and return to the EXEC prompt::






Testing Protocol Translation on the Applied Digital T3AS Digital Cross-Connect

This section describes how to establish a direct Telnet session to test the translate TCP port on router A. To establish a direct Telnet session for protocol translation, determine the IP address and TCP port number configured with the translate statement. In this example (see Figure 3-19), the configuration uses IP address 192.168.10.2 and port number 3000.




RTRV-HRD::::CTAG;










Wiltron Test System Protocol Translation ConfigurationThis section describes the steps required to configure a Cisco router to perform TCP-to-X.25 protocol translation between an IP-based OSS and X.25-TL1 messaging maintenance interface on a Wiltron test system. The Cisco IOS protocol translation feature enables the OSS on the IP network to access an X.25 management interface, despite differences in the native protocol stacks.

Wilton’s Centralized Maintenance Test System (CMTS) provides the equipment needed to remotely and locally access, test, and monitor special service circuits and subscriber loops; see Figure 3-22.



Figure 3-22 Wilton Test System Protocol Translation Configuration

Configuring a Cisco Router for Protocol Translation to Wiltron

This section describes the steps required to configure the central office router designated router A in Figure 3-22. The router is being configured to convert one TCP session to one SVC.

Step 1 Use the show version EXEC command to verify that you are running Cisco IOS Release 12.1(16) or later release software that supports the Telco DCN functions. Protocol translation is supported in the Telco and Enterprise feature sets. The following partial example indicates that the router is running Cisco IOS Release 12.3(12) of a Telco DCN feature set (see bold text):







Step 4 Set up a PAD profile statement for the PVC that is used by SARTs. The PAD profile defines the control of information from the terminal to the PAD, which in this case is from the TCP session to the X.25 session.

router A(config)# x29 profile wiltronsvc 1:0 2:1 3:128 4:0

1355

63

Wiltron

Monitoring: NMA

SARTS

Craft access

TCP/IP X.25

Data centerrouter C

IPbackbone

CO router A


RS-232

SVCs




• Parameter 2 is the Echo parameter, which determines whether characters are to be echoed locally. Parameter 2 is set to 1, which sets the local echo on.

• Parameter 3 is the Data Forwarding parameter and is set to 128, which causes the router to forward data on receipt of a semicolon.

• Parameter 4 is the Selection of Idle Timer Delay and selects the amount of time the PAD waits in 20ths of a second for additional data before forwarding data. If a data forwarding character is received, the data packet is forwarded immediately. Setting the value to 0 means that the Cisco IOS must wait indefinitely for the semicolon character.








router A(config-if)# description Wiltron





Step 11 Configure X.25 DCE encapsulation on the serial interface. The Wiltron is the DTE device. (Note that this is at Layer 1, or the physical layer.)






Step 14 Configure the X.25 idle timer, which is the period of inactivity after which the router can clear a switched virtual circuit. The idle timer value is set in minutes.

Router(config-if)# x25 idle 5






Router(config)# translate tcp 192.168.10.2 port 3000 x25 6142233000 profile wltronsvc



• The X.121 address of 6142233000 is used to map the PAD to serial interface 3/3:









router A# copy running-config startup-configDestination filename [startup-config]?Building configuration...[OK]

Testing Protocol Translation on the Wiltron

This section describes how to establish a direct Telnet session and test protocol translation and X.25 connectivity to the Wiltron network element. To establish a direct Telnet session for protocol translation, determine the IP address and TCP port number configured with the translate statement. In this example (see Figure 3-22), the configuration uses IP address 192.168.10.2 and port number 3000.



Step 2 Enter the TL1 command that retrieves the header for the Wiltron Test Head:

RTRV-HRD:TID:::CTAG;

Step 3 Escape out of the Telnet session using the escape key sequence Ctrl-shift-^-x (simultaneously press and release the Ctrl, Shift, and 6 keys and then press the x key).


Chapter 3 Transmission Equipment in X.25 EnvironmentsTroubleshooting Telco Equipment in X.25 Environments


router A# show sessionsConn Host Address Byte Idle Conn Name* 1 192.168.10.2 192.168.10.2 0 0 192.168.10.2






Troubleshooting Telco Equipment in X.25 EnvironmentsFollowing are Cisco IOS EXEC commands that may be useful in maintaining a network with X.25 and protocol translation enabled. The Cisco IOS command references contain explanations of the displays provided by these commands.

• debug x25 xot—Displays information about traffic to or from a specific XOT host.

• debug x25—Displays information about all X.25 traffic or a specific X.25 service class, including XOT.

• show interfaces—Displays statistics and useful information about the interfaces configured on the router.

• show sessions—Displays information about open Telnet connections.

• show tcp brief—Displays a concise description of TCP connection endpoints.

• show translate—Displays translation sessions that have been configured.

• show x25 route—Displays the X.25 routing table.

Search for these commands in the “Cisco IOS Master Commands List” at http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124mindx/124index.htm.

Caution Take care in issuing the Cisco IOS debug commands, because they can consume CPU cycles and interfere with the normal operation of the network.

Using Network Management Application Alarms to Identify System Problems

The NMA system collects and analyzes information from network alarms and network performance data. The NMA system receives network element messages and analyzes them within the context of the entire communications network, so that trouble indications can be generated for the causes, not the symptoms,


http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124mindx/124index.htm

http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124mindx/124index.htm

Chapter 3 Transmission Equipment in X.25 EnvironmentsUsing Network Management Application Alarms to Identify System Problems

of network failures. The analyzed network problems are routed to a maintenance center and identify the network entity requiring service maintenance or restoration. The incoming alarms are associated to an office equipment entity created in the NMA database. A single office equipment entity is created to represent the central office plant. The receipt of any alarm will result in a trouble ticket being created by the NMA against the office equipment entity. Multiple alarm conditions for the same central office plant will result in additional alarm conditions on the NMA trouble ticket.


C H A P T E R 4
SONET/SDH OSI Environments



IntroductionThe data communications network (DCN) transports network management traffic between network elements and their respective Operations Support System (OSS), making them a vital link between the service network and the network operations center (NOC). The solutions presented in this chapter will help telcos connect their Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) network elements to a router-based network using the Open System Interconnection (OSI) protocol, which simplifies the DCN and reduces equipment costs.

This chapter presents the recommended Cisco architecture for building the OSI network. Several methods for implementing and scaling an OSI network are included with detailed configuration examples. Specific Cisco IOS software features such as Intermediate System-to-Intermediate System (IS-IS) multiareas, VLAN support for International Standards Organization Connectionless Network Service (ISO CLNS), Target Identifier Address Resolution Protocol (TARP), and IS-IS attach bit control are described. These architectures and software features are described in the following main sections:

• Scaling SONET/SDH in the Telco DCN: Overview, page 4-1

• The Cisco Three-Tiered DCN Network Architecture, page 4-12

• Access Layer Configuration, page 4-18

• Distribution Layer Configuration, page 4-87

• Core Layer Configuration, page 4-92

Scaling SONET/SDH in the Telco DCN: OverviewSONET/SDH has become the transport technology of choice for regional Bell operating companies (RBOCs), inter-exchange carriers (IXCs), Post, Telephone, and Telegraph (PTT) organizations, and other carriers to meet the demand for bandwidth and new services. The growth of SONET/SDH and the



Chapter 4 SONET/SDH OSI EnvironmentsScaling SONET/SDH in the Telco DCN: Overview

increasing demands for both existing time-division multiplexing (TDM) and new packet-based data services necessitate better and more scalable DCNs for network operations and management connectivity between network elements and their respective OSSs. As SONET/SDH rings grow in both size and number, the service provider needs to deploy higher bandwidth and more scalable DCN networks to manage SONET/SDH network elements.

RBOCs, Inter-exchange carriers (IXCs), PTTs, and their vendors have worked with standards bodies to define more powerful management networks for SONET/SDH. These standards documents recommend that OSI-based protocols be used by the SONET/SDH network elements’ ring network management.

While IP and OSI protocols are being widely adopted and deployed by RBOCs and PTTs within their DCNs, it is not realistic to replace their vast installed infrastructure of overlay networks that support legacy DCN protocols. To streamline operations and stay competitive, telcos must reduce the number of overlay DCNs they currently have deployed to support various legacy protocols. The new DCNs must support both legacy protocols, which will continue to be in use for the foreseeable future, and the new standards-based protocols. The challenge is to provide this support over a common infrastructure and create a seamless network of networks that can manage the network through a single DCN utility. Figure 4-1 shows a typical DCN network.

Figure 4-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, telephone switches such as the Lucent 5ESS, SONET/SDH 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.

TDM

8886

0

Network OperationsCenter

OperationsSupportSystems

Workstation

Mainframeor minicomputer

Alarms, control, and test messages

Configuration and backup files

Network Elements

SONET/SDHring

Transmissionsystem

DSL

ATM

Alarmunits

Class 4/5telephone

switch

ADM

Dial

GNE

Dialup,leased

line

X.25(XOT)

IP/OSI

Frame Relay, ATM, T1/E1

Billing data collection

Software downloads

MUX



The OSS controls and stores the network management data collected about and from the various network elements.

DCNs are the networks deployed by a telco or service provider that contain all the cabling, network management (NM) stations, switches, network elements and other necessary equipment for delivering and managing services to the service providers’ customers (see Figure 4-1). The DCN is an out-of-band network; that is, it does not transit the same bandwidth segment used by services such as voice and its associated in-band signaling. It does, however, share the same transport equipment and interfaces with switching equipment considered to be the infrastructure of the public switched telephone network (PSTN). This document focuses on a design architecture and Cisco IOS software features for scaling the OSI DCNs.

In addition to the need for scalability, there are other factors driving change in the traditional DCN that is providing operations support for today’s TDM-based services.

These factors are:

• The use of IP and OSI-based intranets within the central office to facilitate communication between network elements and management stations (collectively, the OSS) is increasing.

• “Intelligent” (feature-rich) network elements are requiring more frequent software version updates than their less feature-rich predecessors.

• Software downloads to intelligent network elements across the management network—some many megabytes in size—are increasing bandwidth requirements.

• More and more network elements and OSSs are upgrading to support Ethernet interfaces.

• As competition offers more alternatives, upgraded DCNs are offering the ability to remotely turn up services faster as demanded by their customers.

OSI as a DCN Transport MechanismWith the advent of SONET/SDH networks, service providers and their equipment vendors foresaw the need for new, more powerful service delivery support networks to manage today’s optical networks. In 1988, the International Telecommunication Union (ITU) adopted the M.30 recommendation, which was revised in 1992 and again in 1996, and today is known as recommendation M.3010, Principles for a Telecommunications Management Network.

Recommendation M.3010 defines the architectural requirements for a Telecommunications Management Network (TMN) to support management network operators in planning, provisioning, installing, maintaining, operating, and administering telecommunications networks and services. Within that document, the ITU describes the DCN, which provides the communications backbone between network elements and OSSs in the PSTN.

Using the DCN concepts outlined in M.3010, in December 1995 Bellcore developed an industry standard for SONET—GR-253-CORE—that includes generic DCN requirements. GR253-CORE has become the standard for DCNs within the United States. These standards recommend that OSI-based protocols be used by the OSSs for SONET/SDH ring network management.

As a result of the GR253 and M.3010 standards, SONET/SDH vendors worldwide use the seven-layer OSI protocol stack for the management of their equipment. One application protocol that rides on Layer 7 of the OSI protocol stack, for example, is Transaction Language 1 (TL1). TL1 provides for the definition of messages and protocols between network elements and management stations, and facilitates the gathering of data from SONET equipment.



As SONET/SDH rings grow in both size and number, telcos must deploy higher bandwidth and more scalable DCN networks to manage SONET/SDH network elements. This growth necessitates a migration of DCNs from X.25 networks running from 9.6 kbps to 56 kbps to intranets running at 1.544 Mbps or higher. Both synchronous and asynchronous interfaces are migrating to Ethernet interfaces running at 10 Mbps on network elements and OSSs.

OSI protocol stacks used in SONET/SDH network elements for management require that the DCN be able to use OSI to route to and from the network element and its associated OSS, in addition to the higher bandwidth requirements. A typical RBOC, for example, may have already deployed several thousand SONET rings and is rapidly adding new rings by the hundreds or thousands annually. This large number of SONET network elements demands a DCN that can scale.

IP Standards Development for the DCC and the DCN

The ITU-T has developed a new standard outlining architecture requirements for IP-only domains, OSI-only domains, and IP and OSI domains titled Architecture and Specification of the Data Communication Network, document number G.7712/Y.1703. Basically, the standard adds IP to the DCN and the data communications channel (DCC) architectures. The premise of the standard is that SONET/SDH network elements will still act as routers to forward management traffic across the DCC. In OSI environments, IS-IS is the routing protocol of choice. In mixed environments, Integrated IS-IS is the routing protocol of choice. In IP-only environments, the routing protocol can be either Open Shortest Path First (OSPF) or Integrated IS-IS. The ITU-T document also describes manual tunneling mechanisms for bridging IP-only or for CLNS-only involvements; however, this document focuses on only OSI solutions for SONET/SDH.

DCN Design Considerations for OSI

The current Bellcore and ITU standards recommend the use of the OSI protocol stack for the management of SONET/SDH network elements. Figure 4-2 shows the packet flow from the OSS to a SONET network element. The packet leaves the OSS and is routed across the DCN by routers to the gateway network element (GNE). The GNE routes the packet from the Ethernet network onto the SONET DCC. The packet is routed around the ring. The SONET network element is acting as an IS-IS router. The SONET DCC is the physical path. The SONET network element and GNE are IS-IS Level 1 routers. The standalone routers in the DCN perform the IS-IS Level 2 function. Notice that the DCC has become part of the DCN. The performance of the DCN is determined by all of the components.



Figure 4-2 Packet Flow in a DCN Network

Fundamental issues to address in designing a DCN today are the routing performance of the IS-IS routers and the bandwidth on the DCC. When designing the DCN network, the service provider must take into account the performance characteristic of all the routers, including the routing engine in the network element. Today, the routing engine in the network elements (NEs) can typically support a routing table of only 50 to 100 entries, so this limitation binds the Level 1 area size to 50 to 100 routers. The section DCC is used for management. The bandwidth of the section DCC is 192 KB. The D1 through D3 bytes of the section overhead DCC are used. A packet should not have to make more than seven hops on the DCC to enter the DCN because of bandwidth limitations and the performance of the router in the network element. As the size of the ring approaches 16 nodes, a second GNE must be added to the ring.

The first step for designing a DCN network is to gather information about a particular network environment. The natural geographic groupings of rings should be identified and a breakdown of the average central office size should be computed. This information is required for planning the OSI-based DCN.

Following are the questions that need to be answered before the design process is begun:

• What is the number of SONET nodes in the network today?

• What is the growth rate (number of nodes added per year) of the SONET/SDH network?

• What is the size of the Level 1 OSI area that the routing engine can support? In other words, how many Level 1 routers can be in an area?

• What is the size of the OSI domain that the Level 2 routing engine can support?

• How many network elements does the service provider want to place in an area to start with? Does the service provider want to leave room for growth within an area?

• How many central offices does the service provider have in the DCN?

• Does the service provider want to support a single GNE or dual GNEs?

• What is the average ring size?

• How many rings can be aggregated into a single area?

IntranetIP/OSI

L1/L2

Level 1 and Level 2 router

Ethernet hub

SONET/SDH NE

SONET Data Communications Channel

OSS L1/L2

L1/L2

L1/L2

CLNS packet flow

Area A

Area C

Area B

L1

L1

L1

L1

L1L1 L1

L1

L1

8878

6

L1/L2L1/L2



• How many SONET rings are in a large-sized central office?

• How many SONET rings are in a medium-sized central office?

• How many SONET rings are in a small-sized central office?

DCN Design with a Classic OSI Implementation

This document reviews a classic OSI design, and then reviews an improved design using multiareas. For purpose of example, answers to questions from a hypothetical large-sized service provider network are provided. This information is needed to design a network based on the three-tiered architecture.


There are 25,000 SONET/SDH nodes deployed today.


There are 4000 SONET/SDH nodes added per year.


The Level 1 area size is 50 routers.


The domain size is 500 Level 2 routers.


The service provider wants to place 30 network elements in an area and leave address space for 20 additional network elements in an area.


There are 1700 central offices in the network.


Most of the rings have a single GNE. The design will assume a single GNE per ring.


Average ring size is ten.


A maximum of three SONET/SDH rings will be placed in an area.


The large-sized central office will have 36 SONET rings.


The medium-sized central office will have ten SONET rings.


The small-sized central office will have one SONET ring.

To begin the network design, place the central offices in geographic areas. In this network design, there are five geographic areas. Within each geographic area, the service provider can determine the actual number of large-, medium-, and small-sized central offices. This network design example will use the following rules:



• A small-sized central office has 1 ring, a medium-sized central office has up to 10 rings, and a large-sized central office has up to 12 rings.

• The service provider has estimated the percentage of large-sized central offices to be 10 percent, medium-sized central offices to be 40 percent, and small-sized central offices to be 50 percent.

• Medium- and large-sized central offices will have redundant routers and redundant WAN links. Small central offices will have a single router and redundant WAN links.

An alternative to estimating the percentage of small-, medium- and large-sized central offices is for the service provider to count the number of central offices. Table 4-1 lists the central office breakdown by geographic area using the estimated percentages.

Next, determine the number of Level 2 routers required in each geographic area. Today in small-sized central offices, the service provider in the classic implementation of this network design would typically not have any SONET rings. The network design allows for one ring per office eventually, for growth. Because of the performance limitations of the SONET/SDH network elements, the design calls for many small areas. Remember that the network element routing engine can support only 50 entries in its routing table. Each area requires a Level 2 router, so the logical place for the Level 2 function to be performed is on a standalone router in each central office.

Placing the Level 2 function on the GNE will constrain the size of the routing domain because of performance limitations of the IS-IS routing engine in the GNE. The network design calls for every central office to have at least one OSI area. In this network, large-sized central offices have 36 rings, which equates to 12 Level 2 routers. Also remember that the design criteria questions indicated the average ring size to be ten network elements, and that three rings should be placed in an area. This design will leave address space in an area to add network elements when the rings grow. The computation for the network design is as follows:

36 rings ÷ 3 rings per area = 12 Level 1 areas

The 36 SONET rings in a large-sized central office are split among 12 Level 1 areas. For every Level 1 area, a connection to the backbone is made through a standalone Level 1/Level 2 router, so 12 standalone routers are needed.

The medium-sized office has ten SONET/SDH rings per office. The new network design calls for three rings per OSI area. The computation for the network design is as follows:

10 rings ÷ 3 rings per area = 4 Level 1 areas (rounded up)

The small-sized central office has at most one SONET ring and requires one router per central office. Given these design parameters, the number of standalone routers that will be required are listed in Table 4-2.

Table 4-1 Central Office Breakdown by Geographic Area

Geographic Location

Small-Sized Central Offices

Medium-Sized Central Offices

Large-Sized Central Offices

Total Number of Central Offices

Group 1 150 75 25 250

Group 2 300 150 50 500

Group 3 120 60 20 200

Group 4 360 180 60 600

Group 5 90 45 15 150

Totals 1020 510 170 1700



To show how the numbers in Table 4-2 were derived from Table 4-1, look at Group 1: There are 150 small-sized central offices and one Level 1/Level 2 router per central office. In all, there are 150 Level 2 routers to support small-sized central offices for Group 1, as the following computation indicates:

Group 1 small-sized central offices:

150 small-sized central offices x 1 router per central office = 150 Level 2 routers

There are 75 medium-sized central offices in Group 1. Each medium-sized central office requires four Level 1/Level 2 routers as previously computed, so the total number of Level 1/ Level 2 routers for medium-sized central offices is as defined in the following equation:

Group 1 medium-sized central offices:

75 medium-sized central offices x 4 routers per central office = 300 Level 2 routers

There are 25 large-sized central offices in Group 1. A large-sized central office requires 12 Level 1/Level 2 routers, as computed in the first equation following Table 4-1. The following computation indicates the total number of Level 1/Level 2 routers required:

Group 1 large-sized central offices:

25 large-sized central offices x 12 routers per central office = 300 Level 2 routers

In Table 4-2, the number of standalone Level 2 routers is 5,100. The total number of domains for each group was computed as follows: The number of Level 2 routers in a group was divided by the domain size. The domain size was determined by the routing engine performance of the standalone router. In this design, the domain size is 500, and there would be a total of 13 domains for the network.

A number of obvious issues come up with this example: It is necessary to purchase a large number of standalone routers to provide the Level 2 functions. All of the routers must be monitored and maintained by a NOC. A method of routing between OSI domains is required, and either an interdomain routing protocol or static routes must be used.

IS-IS Multiarea DCN Architecture with SONET/SDH Deployment in All Central Offices

Now let us design the network using the Cisco IOS software IS-IS multiarea feature. Service providers deploying SDH rings today typically are managing all of their rings with OSI, and their network design option assumes that at least one OSI area should be supported in every central office, and that a Level 2 router is placed in every central office.

Table 4-2 Standalone Router Requirements

Geographic Location

Total Number of Offices

Level 2 Small-Sized

Level 2 Medium-Sized

Level 2 Large-Sized Level 2 Total

Total Number of Domains

Group 1 250 150 300 300 750 2

Group 2 500 300 600 600 1500 4

Group 3 200 120 240 240 600 2

Group 4 600 360 720 720 1800 4

Group 5 150 90 180 180 450 1

— — — — — 5100 13



The following are the key assumptions for this network design:


There are 25,000 SONET/SDH nodes deployed today.


There are 4000 SONET/SDH nodes added per year.


The Level 1 area size is 50 routers.


The domain size is 500 Level 2 routers.


The customer wants to place 30 network elements in an area and leave address space for 20 additional network elements in an area.


There are 1700 central offices in the network.


Most of the rings have a single GNE.


Average ring size is ten.


Three SONET/SDH rings per area 3 are required.


The large-sized central office will have 36 SONET rings.


The medium-sized central office will have ten SONET rings.


The small-sized central office will have one SONET ring.

There are five geographic areas, and within each geographic area the actual number of large-, medium-, and small-sized central offices must be determined. The central office size can be allocated as follows: 10 percent large-sized, 30 percent medium-sized, and 60 percent small-sized. Table 4-1 will be used again to represent the numbers of central offices per geographic area. The number of rings terminating in a differently sized central office can be as follows: A small-sized central office can have 1, a medium-sized central office can have 10, and a large-sized central office can have 36 rings. Small-sized central offices would have one SONET/SDH ring. Each central office will have at least one OSI area.

The next step is to compute the number of Level 2 routers required to implement the design. The design will use Cisco 3621 routers in small-sized central offices, which can support up to twelve Level 1 OSI areas. The assumption is that there will be only one OSI area per small-sized central office, and one Cisco 3621 router will be sufficient per small-sized central office. The Cisco 3631 router has two network modules that can be used for contact closure and serial connectivity.



Next, compute the number of small-sized routers for each group. In Group 1, there are 150 small-sized central offices and there is one Level 1/Level 2 router per central office. There are 150 Level 2 routers to support small-sized central offices for Group 1. The computations follow the totals that are listed in Table 4-3.

As Table 4-3 indicates, the number of Level 2 routers has still been substantially reduced over the classic DCN design. Use the following computations to understand how the reductions were made:

Group 1 small-sized central office:










Next, compute the number of routers required for the medium-sized central offices. The network design uses Cisco 3631-DC-central office or Cisco 3662-DC-central office routers. Both of these routers support 12 Level 1 OSI areas with the IS-IS multiarea software. This design calls for ten OSI rings per central office. The original network design called for four Level 1 areas:

10 rings ÷ 3 rings per area = 4 Level 1 areas (rounded up)

One Cisco 3631 or Cisco 3662 router running the IS-IS multiarea software will support a medium-sized central office. The design calls for redundant IS-IS Level 1/Level 2 routers for medium- and large-sized offices. There are 75 medium-sized central offices in Group 1. Each medium-sized central office requires one Level 1/Level 2 router as previously computed, and a second router for backup. The total number of Level 1/ Level 2 routers for medium-sized central offices is as follows (see Table 4-3):



Table 4-3 Level 2 Router Requirements

Geographic Location

Total Number of Offices

Level 2 Small-Sized

Level 2 Medium-Sized

Level 2 Large-Sized Level 2 Total

Total Number of Domains

Group 1 250 150 150 50 350 1

Group 2 500 300 300 100 700 2

Group 3 200 120 120 40 280 1

Group 4 600 360 360 120 840 2

Group 5 150 90 90 30 210 1

— 1700 — — — 2380 7











The computation of the large-sized central office numbers for Table 4-3 is the same process as previously outlined for the medium-sized central offices. (See Table 4-1 for the number of central offices.) The design uses Cisco 3631-DC-central office or Cisco 3662-DC-central office routers. Both of these routers support 12 Level 1 OSI areas with the IS-IS multiarea software. The design calls for 36 OSI rings per central office, as defined in the original network design computation:

36 rings ÷ 3 rings per area = 12 Level 1 areas

One Cisco 3631 or Cisco 3662 router running the IS-IS multiarea software will support a large-sized central office. The design calls for redundant IS-IS Level 1/Level 2 routers for medium- and large-sized offices. A second router will be placed in every large-sized office. There are 25 large-sized central offices in Group 1. The total number of Level 1/ Level 2 routers for large-sized central offices is as follows:


25 large-sized central offices x 2 routers per central office = 50 Level 2 routers.

The following examples show the remainder of the group’s computations:


50 large-sized central offices x 2 routers per central office = 100 Level 2 routers.







The total number of Level 2 routers is listed in Table 4-3.

The network is divided into five geographic areas, and each geographic area is a logical grouping of central offices. The logical central office grouping will make up an OSI domain. (In IS-IS, a domain is a logical set of networks, unlike Internet domains that are general groupings of networks based on organization type or geography.) In this design, the performance characteristics of Level 2 routers allow the OSI domain to grow to 500 standalone routers. The domain size assumes that the routers have at least the performance capability of a Cisco 3662 or 3631 router. In Table 4-3, the number of Level 2 routers in Groups 2 and 4 exceeds 500, so these groups are split into two domains. A domain is made up of standalone access routers and standalone distribution routers; see Figure 4-3 and the next section.


Chapter 4 SONET/SDH OSI EnvironmentsThe Cisco Three-Tiered DCN Network Architecture

The Cisco Three-Tiered DCN Network ArchitectureService providers need a basic architecture for the DCN network. The recommended architecture is a three-tiered design. This design is described in the following sections:

• Three-Tiered DCN Network Overview, page 4-12

• OSI Addressing Issues and Suggestions, page 4-13

• OSI Addressing Implementation, page 4-16

Three-Tiered DCN Network OverviewA three-tiered DCN architecture design will ensure manageable and scalable networks with the ability to easily add network equipment with new features and new services as needed. At the core of the DCN are multiprotocol routers capable of transporting IP, OSI, and X.25.

A three-tiered architecture solution as shown in Figure 4-3 consists of core, distribution, and access elements. A backbone contains routers or WAN switches that form a core or transport utility. Switching centers equipped with distribution routers are located around the backbone to provide symmetric connectivity to central offices. At each central office, access routers provide connectivity into their respective switching and distribution center. Reliability is built into the DCN by designing in redundancy at each tier of the architecture. The access layer defines the DCN interface to the network elements located within the central office. The access routers are configured as Level 1/Level 2. The core and distribution routers are configured as Level 1/Level 2 or Level 2.

Figure 4-3 DCN Three-Tiered Architecture

The IS-IS routing protocol is run within the OSI domains. Static routes or an interdomain routing protocol can be run between the OSI domains. Cisco recommends running an interdomain routing protocol in the core. Cisco customers have traditionally used ISO-IGRP (the Interior Gateway Routing Protocol developed by Cisco Systems for ISO CLNS) as their interdomain routing protocol. Cisco has developed support for CLNS extensions within multiprotocol Border Gateway Protocol (BGP). The BGP work is based on Internet Engineering Task Force (IETF) RFC 2283. BGP is the mostly widely implemented interdomain routing protocol today.

Accesscentral offices

Distribution Core 8878

9



When implementing the three-tier architecture, it is important to look at the bandwidth of the links and location of the NOC. Typically, the NOC or the data centers with the OSS are built as an additional access site in the architecture. The size of the links to the distribution center may be larger because of the amount of traffic. In the DCN environment, the flow of data is between the OSSs and the network elements, which are downstream from the central office. Typically, very little data is sent between network elements and central offices today, but there are applications that will create more traffic between central offices. These applications include remote login and signaling for bandwidth. Remote login allows a technician logged in to a network element to access another network element over the DCN. The remote login feature saves the technician from needing to be physically at a site to perform maintenance and troubleshooting tasks.

Bandwidth signaling applications are being defined as part of the following standards:

• ITU-T G.807—Requirements for the Automatic Switched Transport Network (ASTN)

• ITU-T G.8080—Architecture for the Automatic Switched Optical Network (ASON)

• Optical Internetworking Forum (OIF) User Network Interface (UNI) 1.0—This standard provides signaling between network elements, and between network elements and clients. It also provides signaling for both in-band and out-of-band or DCN networks, and for bandwidth.

OSI Addressing Issues and SuggestionsIn ITU-T Recommendation X.213, Data Networks and Open Systems Communications Open Systems Interconnections Service Definitions, the network layer addressing is described in ANNEX A. The document is also referred to as ISO/IEC 8348:1996(E). Refer to ITU-T Recommendation X.213 for complete details about OSI addressing. This section focuses on basic address information used in the SONET/SDH environments.

The OSI network address is referred to as a network service access point (NSAP). The NSAP is assigned to the end system (ES) or intermediate system (IS) device. Unlike in IP, which has an address for every network interface, the OSI network device receives only one address, the NSAP address. The NSAP address has two parts, the Initial Domain Part (IDP) and Domain Specific Part (DSP), as shown in Figure 4-4.

Figure 4-4 NSAP Addresses

8878

8

IDPInitial Domain Part

DSPDomain Specific Part

AFIAuthority Format

Identifier

IDIInitial Domain Identifier

NSAP Address

Initial Domain Part



The IDP of the NSAP is assigned by address authorities. The address authorities allocate the bytes in the DSP. Six address authorities are currently defined, each briefly described as follows:

• ITU-T E.164—Specifies the initial domain identifier (IDI) as an ISDN number up to 15 digits long. This recommendation also specifies a PSTN up to 12 digits long.

• ITU-T F.69—Specifies the IDI as an international telex number up to eight digits long.

• ITU-T X.121—Specifies the IDI as an X.121 address for public X.25 networks, and is up to 14 digits long.

• International Organization for Standardization/International Electrotechnical Commission (ISO/IEC) Data Country Code (ISO DCC)—Specifies the IDI as a three-digit numeric code as defined by ISO 3166. An ISO member body within a country is assigned a three-digit code. The DSP is allocated by the ISO member body for a country.

• ISO 6523-ICD—Specifies the IDI as a four-digit International Code Designator (ICD) as defined by ISO 6523.

• Local—This address is the IDI and, if null, is used for local routing.

The SONET/SDH environments utilize the address authority defined by the ISO DCC. The AFI can have a value of 38 or 39. The value for the IDI is the country code. For the United States, the IDI is 840. The American National Standards Institute (ANSI) is the ISO body in the United States that assigns the 39.840 address space. The DSP addressing is defined in the American National Standard X3.216-1992, Structure and Semantics of the Domain Specific Part of the Network Service Access Point Address.

An ANSI-defined DSP is shown in Figure 4-5. The DSP is 17 binary octets long. The breakdown of the DSP is listed after the figure; the number of octets is shown under each category.

Figure 4-5 ANSI DSP Structure

• AFI—Authority format identifier value of 39 defines the NSAP type as ISO/IEC. The length is one binary octet.

• IDI—Initial domain identifier value of 840 defines the country as United States. The length is two binary octets.

• DFI—Domain Specific Part format identifier specifies the version of the ANSI X3.216. The decimal value is 128. Hexadecimal value is 80. The length is one binary octet.

• org—The organization is identified by the value that is assigned by ANSI. The length is three binary octets.

• res—A reserved field set to a value of 0. The length is two binary octets.

• rd—A routing domain prefix to be used for address summarization. This prefix allows the summarization of the multiple areas with one routing entry. The length is two binary octets.

IDP

AFI IDI DFI

39 840 128 org res rd area system sel

1 2 1 3 2 2 2 6 1

DSP

Number of Octets

8878

7



• area—This portion of the NSAP identifies the unique Level 1 area. The length is two binary octets.

• system—This is the unique system identifier of an ES. There can only be one ES within an area with this unique identifier. There is no definition on how to assign the identifier. Implementors often use the MAC address off the first Ethernet port or a portion of the IP address. The length is six binary octets.

• sel—The NSAP selector is used to specify the network service user. The NSAP selector is used to differentiate multiple applications connections to the same ES. An analogous solution would be TCP/IP port numbers. The network layer is set to a value of 0, so a Cisco router is typically configured to a value of 0. The length is one binary octet.

In the Telcordia Specification GR-253-core, in Section 8 of the document, the NSAP address is described with reference to the DCN and SONET network elements. ISO DCC is the selected address format, and the AFI has a decimal value of 39 that is encoded in binary coded decimal. The AFI is configured into Cisco IOS software in decimal format. The AFI is broken down in Figure 4-6.

Figure 4-6 AFI Structure

The ISO DCC in this example is for the United States, so the IDI decimal value is 840. The IDP portion of the NSAP is encoded in packed binary coded decimal format. The AFI and a portion of the IDI is shown in Figure 4-7.

Figure 4-7 AFI and IDI Structure

The IDI shown in Figure 4-7 takes up 1.5 octets. The IDI has two octets set aside. The Telcordia GR-253 specification calls for filling the last four bits of the octet with ones. This process is referred to as the IDI PAD. Because there is no decimal value for the binary number 1111 in Binary Coded Decimal (BCD), the number is represented in hexadecimal as an F. The DSP portion of the NSAP is typically configured in hexadecimal. The DFI portion of the DSP has a decimal value of 128, a binary value of 1000 0000, and a hexadecimal value of 80; see Figure 4-8.

AFI

Octets 1

Decimal 3 9

Binary 0011 1001

Cisco IOS entry 3 9

AFI IDI IDI PAD

Octets 1 1.5 0.5

Decimal 3 9 8 4 0 None

Binary 0011 1001 1000 0100 0000 1111

Cisco IOS entry 3 9 8 4 0 F



Figure 4-8 AFI, IDI , and DFI Structure

The next portion of the DSP, which is the organizational identifier, is assigned by ANSI. The organization identifier is made up of three octets that are entered into the Cisco IOS software as six hexadecimal characters.

The following example uses an organization identifier of 119999. The NSAP has the following format:

39.840f.80yy.yyyy.rrrr.dddd.aaaa.iiii.iiii.iiiii.ss

and can be interpreted as follows:

• y—The organizational identifier as assigned by ANSI or other address authority for your region of the world.

• r—This portion of the NSAP is reserved and given a value of zero.

• d—The routing domain portion of the NSAP address. The routing domain is a collection of Level 1 areas. The routing domain allows the collection of Level 1 areas to be summarized among the Level 2 routers. The field can be provided in hexadecimal characters.

• a—The Level 1 area address as defined by ISO 10589. The field can be provided in hexadecimal characters.

• i—The individual system identifier. The structure of the format of the value is chosen by the customer. Customers typically input the MAC address of the first Ethernet port or a portion of the IP address.

• s—The NSAP selector. The value for a network entity title (NET) is zero.

Following is an example of the Cisco IOS software commands used to configure the NSAP on a Cisco router:

router isis DCNnet 39.840f.8011.9999.0000.0001.000b.00e0.f725.3338.00

OSI Addressing ImplementationThis section describes how to implement an addressing plan based on the “OSI Addressing Issues and Suggestions” section on page 4-13. ANSI or the ISO DCC address authority in your geographic area of the world assigns the address space. ANSI can be contacted at http://ansi.org/.

Instructions for applying for a unique organizational identifier are included under the registration services portion of the ANSI website. In this example, the unique organizational identifier is 119999. The next portion of the DSP is marked reserved. The reserved portion of the NSAP is two octets. The NSAP up to this point looks like 39.840f.8011.9999.0000, and the format of the DSP is defined, but the service provider determines the assignment of the address space.

Because the remainder of the DSP is left up to the service provider, let us look at an example. In the example, the routing domain, the area, the individual system identifier, and NSAP selector will be filled out. The example has the following five OSI routing domains—domain 1111, domain 2222, domain

AFI IDI IDI PAD DFI

Octets 1 1.5 0.5 1

Decimal 3 9 8 4 0 None 128

Binary 0011 1001 1000 0100 0000 1111 1000 0000

Cisco IOS entry 3 9 8 4 0 F 8 0


http://ansi.org/


3333, domain 4444, and domain 5555. The first alternative has five OSI domains or routing domains. Each domain is two octets long. The key to laying out the address space is to allow summarization of domains, as follows:

OSI domain 1: 39.840f. 8011.9999.0000.1111

OSI domain 2: 39.840f. 8011.9999.0000.2222

OSI domain 3: 39.840f. 8011.9999.0000.3333

OSI domain 4: 39.840f. 8011.9999.0000.4444

OSI domain 5: 39.840f. 8011.9999.0000.5555

The area addressing can be created by adding the area addresses one at a time within a domain. Therefore, the first area within domain 1111 could be area address 0001, and the NSAP would be as follows:

39.840f.8011.9999.0000.1111.0001

The system identifier uniquely identifies the device within the area. To create this identifier, service providers often use the MAC address of the first Ethernet port on the router, which is displayed by entering the show interface EXEC command on the router (for purpose of example, the MAC address is shown in bold text):

Router# show interface ethernet 0/0

Ethernet0/0 is up, line protocol is down Hardware is AmdP2, address is 00d0.5872.9720 (bia 00d0.5872.9720) Internet address is 172.168.0.22/24 MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, reliability 231/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) ARP type: ARPA, ARP Timeout 04:00:00 Last input never, output 00:00:08, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 input packets with dribble condition detected 12 packets output, 1009 bytes, 0 underruns 12 output errors, 0 collisions, 2 interface resets 0 babbles, 0 late collision, 0 deferred 13 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out

The following example shows how to use the MAC address 00d0.5872.9720 to create the area identifier:

39.840f.8011.9999.0000.1111.0001.00d0.5872.9720

It is also acceptable to use the IP address in the station identifier. In the following example, the IP address on the Ethernet interface is 172.168.0.22. Some service providers choose to use the IP address on the loopback interface, but for this example the Ethernet interface is used. The 172 portion of the IP address was left out and the remainder of the IP address was imbedded.

39.840f.8011.9999.0000.1111.0001.0168.0000.0022

The following example is another way to use the IP address to create the area address:

39.840f.8011.9999.0000.0001.1721.6800.0022


Chapter 4 SONET/SDH OSI EnvironmentsAccess Layer Configuration

A final example would be to take the IP address and encode it in hexadecimal format. This action allows the entire IP address to be placed into the end system identifier, but recognizing the IP address is not as straightforward by doing so. The following list shows the loopback address 172.168.0.22 encoded as hexadecimal numbers:

• 172 = ac

• 168 = a8

• 0 = 00

• 22 = 16

Plugging the hexadecimal numbers into the end system identifier would result in the number 39.840f.8011.9999.0000.1111.0001.0000.aca8.0016. Notice that the first two octets of the system identifier are padded with 0s.

Note The NSAP selector is set to 00 for an IS-IS device. The following example shows what the NSAP of an IS-IS router would look like: 39.840f.8011.9999.0000.1111.0001.00d0.5872.9720.00.

Access Layer ConfigurationThis section focuses on the access layer of Cisco’s three-tiered network architecture and contains these sections:

• SONET/SDH Scaling Issues for Multiple OSI Areas, page 4-18

• Defining IS-IS Multiareas with ISL Trunking, page 4-21

• Defining IS-IS Multiareas with IEEE 802.1Q Trunking, page 4-31

• Defining Multiple Areas with Manual Area Addressing, page 4-34

• Using Generic Routing Encapsulation Tunnels to Prevent Area Partitions, page 4-38

• IS-IS Attach-Bit Control Feature, page 4-45

• Using IP over CLNS Tunnels to Access Remote Devices, page 4-50

• Mapping NSAPs to Device Names Using TARP, page 4-54

• Maintaining and Troubleshooting the IS-IS Network, page 4-68

SONET/SDH Scaling Issues for Multiple OSI AreasAll SONET/SDH nodes on a ring are typically Level 1 routers, because of the performance issue described in the “DCN Design Considerations for OSI” section on page 4-4. SONET/SDH nodes on a ring should be in the same OSI area if the nodes are all Level 1. SONET/SDH devices must be organized into many small-sized OSI areas, as described in earlier sections about IS-IS multiarea DCN architecture. The IS-IS multiarea was added to the Cisco IOS feature set to improve the scaling of an IS-IS network in the SONET/SDH environments. The feature allows the configuration of up to 29 Level 1 IS-IS processes on Cisco routers.



Note The maximum number IS-IS process that can be configured is 29. However, the configuration of multiprotocol BGP (mBGP) CLNS and ISO-IGRP changes that number. If you configure mBGP CLNS, two IS-IS processes are used and you can configure only one instance of mBGP. On a router with mBGP CLNS configured, the user can only configure 27 IS-IS processes.

The configuration for ISO-IGRP takes two IS-IS processes. You can configure multiple ISO-IGRP processes and each ISO-IGRP process configured uses two IS-IS processes. If you configure two ISO-IGRP processes, then four IS-IS processes would be used. You have the ability to configure 25 IS-IS processes, which is 29 IS-IS processes minus the four IS-IS processes used by the two ISO-IGRP instances.

If you configure the mBGP CLNS process and one ISO-IGRP processes, you can configure 25 IS-IS processes. You start with 29 IS-IS processes and subtract the two IS-IS processes used by the one ISO-IGRP process and subtract the two IS-IS processes used by the mBGP CLNS process.

The number of IS-IS processes supported are specific to a platform, the architecture of the network, and the other tasks being performed on a platform. Specific base guidelines have been released for the Cisco 1800, 2600, and 3600 series platforms, as listed in Table 4-4.

These numbers assume that the customer is implementing the three-tiered network architecture described in the “The Cisco Three-Tiered DCN Network Architecture” section on page 4-12. A flat network with many IS-IS adjacencies will not perform as well as the tiered network. For example, a poor design builds a Frame Relay cloud that peers all the sites together. As the number of sites in the Frame Relay network increase, the number of IS-IS adjacencies to maintain and the number of CPU cycles would also increase.

Table 4-4 IS-IS Processes Supported on Cisco Router Platforms

Router Platform IS-IS Processes

Cisco 1841 3

Cisco 2610, Cisco 2611, Cisco 2620, Cisco 2621, and Cisco 2651

3

Cisco 2691 8

Cisco 2811 8

Cisco 2821 8

Cisco 2851 8

Cisco 3640 8

Cisco 3725 8

Cisco 3631 12

Cisco 3662 12

Cisco 3745 15

Cisco 3825 15

Cisco 3845 20



The CPU cycles on the router can be affected by other features enabled in the Cisco IOS software. Service providers often perform protocol translation on access routers. The router is translating between a TCP/IP session from the OSS and X.25 to the network element. Each packet is process-switched by the CPU, which affects the amount of CPU cycles available for maintaining IS-IS adjacencies.

Cisco routers are used to interconnect each Level 1 area or ring to the Level 2 backbone. A typical routing engine in a SONET network element can support only a routing table of 50 to 100 entries. This limitation bounds the area size to 50 Level 1 SONET routers. The service provider will need to check with their specific SONET/SDH vendors. Basic network designs were reviewed earlier in this document. Also, some SONET/SDH vendors have limitations on the number of ES adjacencies and Level 1 adjacencies that a GNE can support. The number of adjacencies has been as low as 15 on some SONET/SDH nodes. In early deployments, service providers were running into adjacency problems when implementing Ethernet hubs because they were putting multiple GNEs from different OSI areas on the same Ethernet hub, as shown in Figure 4-9. The GNEs in the different areas were forming ES adjacencies, which caused performance problems for the GNEs.

Note Gateway network elements are the network elements that are connected to the Ethernet and the optical ring or chain. The gateway network element is a gateway between the DCN and the in-band management channel, which is called the data communication channel (DCC).

Figure 4-9 GNEs Forming ES Adjacencies

Cisco’s solution is shown in Figure 4-10. Cisco recommends installing an Ethernet switch and separating the GNEs, thereby placing all the GNEs in different OSI areas on a separate VLAN. Figure 4-10 shows 12 OSI areas that correspond to 12 VLANs.

9570

7

NE

Area0001

NE

Area0002

Area0011

Area0012

VLAN 1

VLAN 2

VLAN 11

VLAN 12

GNE

GNE

NEGNE

NEGNE

CLNS packet flow



Figure 4-10 GNEs Separated by an Ethernet Switch

SONET network elements communicate over a DCC in-band channel in the SONET ring at 192 KB. The in-band channel is used to access SONET nodes on the ring. Typically, there is only one GNE onto smaller rings deployed in a metropolitan setting. The DCC is often used to access the SONET node placed on a customer site or to access an optical amplifier in the fiber. Extending the DCN to these sites would not make sense from an economic or security standpoint. The limited 192 KB bandwidth of the DCC limits the size of the SONET/SDH ring. One method around the DCC bandwidth limitation is to add GNEs to the ring. The GNEs should be separated by four to seven hops. The service provider should consult the GNE vendor.

Defining IS-IS Multiareas with ISL TrunkingThis section describes the configuration for an IS-IS multiarea with VLANs using Inter-Switch Link (ISL) trunking (a Cisco-proprietary protocol that maintains VLAN information as traffic flows between switches and routers). Typically, the multiarea feature is used at the access portion of the network. The OSS is located in the data center, and the CLNS packets are routed across the network to the central office router. Figure 4-11 shows a typical configuration.

Figure 4-11 IS-IS Multiarea Network Using ISL

9570

6

NE

Area0001

NE

Area0002

Area0011

Area0012

GNE

GNE

NEGNE

NEGNE

CLNS packet flow

VLAN 1

VLAN 2

VLAN 11

VLAN 12

9511

8

OSS

Central officerouter

VLAN using ISL

NE14A

NE15A

NE25A

NE26A

NE14BArea0001

Area0002

Area0003

NE25A

NE26B

CLNS packet flow

IP/OSI



Figure 4-11 shows three IS-IS Level 1 areas. For purpose of example, the areas are small, with only two or three SONET or SDH network elements per area. A more typical area would have 30 to 50 network elements.

This configuration example uses a Cisco 3640 router and a Cisco Catalyst 2924XL switch. The IS-IS multiarea feature supports only one Level 1 or Level 2 IS-IS process per router. The router can be configured for up to 28 independent Level 1 processes and one Level 1/Level 2 process.

The number of IS-IS Level 1 processes supported depends upon the router platform. Each Level 1 IS-IS process must have a unique NSAP within an OSI area. The unique portion of the NSAP is the system identifier. The same unique system identifier must be used when creating multiple NSAPS on the Cisco 3640 router. In this example, the system identifier used is MAC address 0010.7bc7.ae40 from Ethernet port 0/0. See the “OSI Addressing Implementation” section on page 4-16 for more information about selecting system identifiers.

The MAC address is listed in the output of the show interface command, as the following example shows (text bolded for purpose of example):

3640A# show interface ethernet0/0

Ethernet0/0 is up, line protocol is up Hardware is AmdP2, address is 0010.7bc7.ae40 (bia 0010.7bc7.ae40) Internet address is 192.168.0.49/24 MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:07, output 00:00:00, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 4 packets input, 533 bytes, 0 no buffer Received 3 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 input packets with dribble condition detected 11 packets output, 786 bytes, 0 underruns 0 output errors, 0 collisions, 4 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out

Using address examples from the “OSI Addressing Implementation” section on page 4-16, the routing domain number is 1111. The following example configures the access router to handle the following three OSI areas:

39.840f.8011.9999.0000.1111.0001

39.840f.8011.9999.0000.1111.0002

39.840f.8011.9999.0000.1111.0003

The corresponding NSAPs for the Cisco 3640 router are built with a unique system identifier and a network selector value of 00. The network selector for the network layer is 00. The chosen system identifier for this example is the MAC address from Ethernet interface 0/0, so the NSAPs for the Cisco 3640 routers are as follows:

net 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00

net 39.840f.8011.9999.0000.1111.0002.0010.7bc7.ae40.00



net 39.840f.8011.9999.0000.1111.0003.0010.7bc7.ae40.00

An interface can be associated with only one IS-IS processes. In the first solution that Cisco provided to service providers, a separate Ethernet interface was configured for every IS-IS process and LAN. Each LAN was on a separate hub, as shown in Figure 4-12.

Figure 4-12 IS-IS Multiarea Network Using Separate Ethernet Interfaces

The next solution that Cisco provides makes it possible to consolidate the individual hubs into a Cisco Catalyst switch with VLANs. Each VLAN on the Cisco Catalyst switch had a separate Ethernet connection from the router, as shown in Figure 4-13.

Figure 4-13 IS-IS Multiarea Network Consolidating Hubs on a Switch (VLAN Trunking)

The number of physical Ethernet interfaces can be reduced by using VLAN trunking. A separate IS-IS process can be assigned to a subinterface. The example in this section focuses on implementing an IS-IS multiarea on an ISL trunk, as shown in Figure 4-14.

9511

5

CLNS packet flow


E 0/0

E 0/2

E 0/1

NE14A

NE15A

NE25A

NE26A

NE14BArea0001

Area0002

Area0003

NE25B

NE26B

9511

7

CLNS packet flow


NE14A

NE15A

NE25A

NE26A

NE14BArea0001

Area0002

Area0003

NE25B

NE26B

E 0/0

E 0/2

E 0/1



Figure 4-14 IS-IS Multiarea Network Using VLAN Trunking and ISL Encapsulation

Configuring an IS-IS Multiarea Network on a VLAN Using ISL Encapsulation

This section uses the network shown in Figure 4-14 as the basis for the configurations. The examples use a Cisco 3640 router with the Telco Feature Set running Cisco IOS Release 12.2(15)T.

Begin by enabling a CLNS routing and enabling TARP (assuming that TARP will be used). TARP is the target identifier (TID) Address Resolution Protocol, which is the name given to a piece of equipment by service providers in the United States. (TARP is an application that automates the mapping of CLNS addresses to TIDs, and will be described in more detail in the “Enabling TARP” section on page 4-59.)

The following example shows how to enable TARP and assign the router a TID using the router’s host name; in this example, the assigned TID is 3640A for a Cisco 3640 router:

clns routingtarp runtarp tid 3640A

Next, create the IS-IS routing processes for the three areas shown in Figure 4-14. The first IS-IS routing process created can be a Level 1/Level 2, which is a circuit-type Level 1/Level 2. (Note that the circuit-type Level 1/Level 2 configuration will not show up in the system configuration output because “is-type level-1-2” is the default.) The remaining IS-IS processes will be Level 1, which is specified and identified in the Cisco IOS software as “is-type level-1.” After the first Level 1/Level 2 IS-IS process is configured, the remaining processes will automatically be configured by the software as “is-type level-1.”

Each IS-IS process has an identifier. In the examples, the IS-IS process identifiers are named after the OSI area. For example, the IS-IS process identifier area0001 is used for area 0001. (Note that the IS-IS process identifier name is arbitrary, but that area names are useful for troubleshooting. The service provider could have named the IS-IS processes after colors, for example.) The system identifier used in the example is the MAC address (0010.7bc7.ae40) from Ethernet port 0/0.

The following example shows how to configure the IS-IS routing processes for the three areas:

router isis area0001 net 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00!router isis area0002 net 39.840f.8011.9999.0000.1111.0002.0010.7bc7.ae40.00 is-type level-1!router isis area0003 net 39.840f.8011.9999.0000.1111.0003.0010.7bc7.ae40.00 is-type level-1

9511

6

CLNS packet flow

3640ACentral office

router

2924XL

NE14A

NE15A

NE25A

NE26A

NE14BArea0001

Area0002

Area0003

NE25B

NE26B

VLAN using ISL



The IS-IS process area0001 is specified in the Cisco IOS software with the is-type level-1-2 command, which is the Cisco IOS software default, but no is-type commands will be displayed in the configuration output. The area0001 process will provide connectivity back to the IS-IS backbone. There can be only one Level 2 IS-IS process, and each additional IS-IS process will be at Level 1. Each IS-IS process must be assigned to a separate interface. Fast Ethernet port 3/0 is configured for ISL trunking with three subinterfaces. The encapsulation on the interface is ISL (specified with the encapsulation isl command).

Designated IS Election Process on a LAN

Generally, service providers configure the Cisco access router to be the designated IS on the Ethernet interface. In IS-IS routing, a broadcast medium such as a LAN is not treated as a fully connected topology. Instead, a logical representation of the LAN is created called a pseudonode, which is generated by a Designated Intermediate System (DIS).

The DIS is responsible for creating and updating the pseudonode line-state packet (LSP) and flooding the LSPs over the LAN. On a broadcast medium such as Ethernet, one DIS is selected for Level 1 routers and a separate DIS is selected for Level 2 routers. There is no backup DIS. The election of a DIS can be preempted by a DIS with a higher priority. The routers on the LAN, including the DIS, form an adjacency with the pseudonode. A router elects itself the DIS based on interface priority. The priority range is from 0 (lowest) to 127 (highest). A priority of 64 is the default, and a priority of 127 sets the router to be elected as the DIS. If two routers have the same priority, the router with the highest subnetwork point of attachment (SNPA) wins the election.

The SNPA, which is the MAC address on the LAN or the data-link connection identifier (DLCI) on a Frame Relay network, is also used to configure a CLNS route for an interface. For the configuration example in this section, the SONET network elements are configured as Level 1 IS-IS routers. In real network implementations, service providers have found that forcing the Cisco router to be the DIS works best. Service providers are basically offloading the DIS functions onto the CPU of the standalone Cisco routers, as opposed to a SONET/SDH network element. This configuration is done by setting the IS-IS priority to 127 on the interface. A Level 1 IS-IS pseudonode is selected on each VLAN.

The Cisco router labeled “3640A” in Figure 4-14 is the DIS for each VLAN, and Fast Ethernet interface 3/0.1 is configured first. In the following example, the interface is configured with ISL encapsulation and VLAN 1 is assigned to the interface. IS-IS process area0001 is assigned to the interface using the clns router isis area0001 command. The assignment of the IS-IS processes to the interfaces is shown in the following example. The IS-IS priority for selecting the DIS is modified to 127, from the default 64, to force the Cisco 3640 router to be the DIS. TARP is enabled on the interface. An IP subnet is assigned to VLAN 1 so that the network administrator can assign an IP address to the Cisco Catalyst 2924XL switch for management of the switch. The following example shows how to configure the Cisco router labeled “3640A” as the DIS for each VLAN. The IS-IS priority is set to 127 on the interface.

interface FastEthernet3/0 no ip address duplex auto speed auto no cdp enable!interface FastEthernet3/0.1 description IS-IS area 0001 encapsulation isl 1 ip address 192.168.2.61 255.255.255.192 no ip redirects no cdp enable clns router isis area0001 isis priority 127 tarp enable



Fast Ethernet interface 3/0.2 is configured next. In the following example, the interface is configured with ISL encapsulation, and VLAN 2 is assigned to the interface. IS-IS process area0002 is assigned to the interface by the clns router isis area0002 command. The assignment of the IS-IS processes to the interfaces is shown in the following example. The IS-IS priority for selecting the DIS is modified to 127 from the default 64, to force the Cisco 3640 router to be the DIS. TARP is enabled on the interface.

interface FastEthernet3/0.2 description IS-IS area 0002 encapsulation isl 2 no cdp enable clns router isis area0002 isis priority 127 tarp enable

Fast Ethernet interface 3/0.3 is the third subinterface to be configured. As with the first two subinterfaces, this interface is configured with ISL encapsulation, and VLAN 3 is assigned to the interface. IS-IS process area0003 is assigned to the interface by the clns router isis area0003 command. The assignment of the IS-IS processes to the interfaces is shown in the following example. The IS-IS priority for selecting the DIS is modified to 127 from the default 64, to force the Cisco 3640 router to be the DIS. TARP is enabled on the interface.

interface FastEthernet3/0.3 description IS-IS area 0003 encapsulation isl 3 no cdp enable clns router isis area0003 isis priority 127 tarp enable!

Verifying an IS-IS Multiarea Network Using VLAN Trunking and ISL Encapsulation

The next step is to verify that CLNS is operating on the router. Use the show clns EXEC command to verify that CLNS is running. The following example shows typical output of the show clns command:

3640A# show clns

Global CLNS Information: 3 Interfaces Enabled for CLNS NET: 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00 NET: 39.840f.8011.9999.0000.1111.0002.0010.7bc7.ae40.00 NET: 39.840f.8011.9999.0000.1111.0003.0010.7bc7.ae40.00 Configuration Timer: 60, Default Holding Timer: 300, Packet Lifetime 64 ERPDU's requested on locally generated packets Intermediate system operation enabled (CLNS forwarding allowed) IS-IS level-1-2 Router: area0001 Routing for Area: 39.840f.8011.9999.0000.1111.0001 IS-IS level-1 Router: area0002 Routing for Area: 39.840f.8011.9999.0000.1111.0002 IS-IS level-1 Router: area0003 Routing for Area: 39.840f.8011.9999.0000.1111.0003

The sample output shows that the router has CLNS enabled on three interfaces. The three OSI NSAPs are listed. Notice that the system identifier—0010.7bc7.ae40—is the same for all three NSAPs. The three IS-IS processes are listed with their respective process identifiers—area0001, area0002, and area0003. The routing area assigned to each process is also listed.

The three interfaces running CLNS can be further examined using the show clns interface EXEC command. Sample command output for all three interfaces follows, starting with Fast Ethernet interface 3/0.1:



3640A# show clns interface fastethernet 3/0.1

FastEthernet3/0.1 is up, line protocol is up Checksums enabled, MTU 1497, Encapsulation SAP ERPDUs enabled, min. interval 10 msec. RDPDUs enabled, min. interval 100 msec., Addr Mask enabled, last sent 00:47:38 Congestion Experienced bit set at 4 packets CLNS fast switching enabled CLNS SSE switching disabled DEC compatibility mode OFF for this interface Next ESH/ISH in 23 seconds Routing Protocol: IS-IS (area0001) Circuit Type: level-1-2 Interface number 0x0, local circuit ID 0x1 Level-1 Metric: 10, Priority: 127, Circuit ID: 3640A.01 Level-1 IPv6 Metric: 10 Number of active level-1 adjacencies: 2 Level-2 Metric: 10, Priority: 127, Circuit ID: 3640A.01 Level-2 IPv6 Metric: 10 Number of active level-2 adjacencies: 0 Next IS-IS LAN Level-1 Hello in 1 seconds Next IS-IS LAN Level-2 Hello in 2 seconds

In this sample output for Fast Ethernet interface 3/0.1, the interface is up and the line protocol is up. Notice that CLNS fast switching is enabled by default. The routing protocol is IS-IS and the associated IS-IS process identifier is area0001. The Circuit Type report indicates whether this circuit is Level 1, Level 2, or Level-1-2. In this case, the circuit type is Level-1-2. The IS-IS priority is 127 on the interface for the Cisco router labeled “3640A.” The Cisco 3640 router is the DIS and identified as the DIS in the Circuit ID field. In other words, the circuit identifier lists the designated router’s host name or system identifier if the routers do not know the host name. In this case, the designated router’s host name is 3640A. Remember that the Cisco 3640 router interface is set to IS-IS priority of 127, which is the highest value. There are two active Level 1 adjacencies. The adjacency numbers correspond to those shown in Figure 4-14. The Cisco router labeled “3640A” should have a Level 1 adjacency with the SONET/SDH nodes labeled “NE14A” and “NE15A.” The Level 2 routing metric is 10 and the IS-IS Level 2 priority is 127. The Circuit ID field lists 3640A as the designated router. There are no Level 2 IS-IS adjacencies on Fast Ethernet interface 3/.01. (Normally, the Level 2 adjacency would come from the WAN connection back to the distribution router, or to a Level 2 adjacency with a second Level-1-2 router in the central office configured for a different OSI area on the Level-1-2 IS-IS process.)

The following example shows sample output for Fast Ethernet interface 3/0.2:


FastEthernet3/0.2 is up, line protocol is up Checksums enabled, MTU 1497, Encapsulation SAP ERPDUs enabled, min. interval 10 msec. RDPDUs enabled, min. interval 100 msec., Addr Mask enabled Congestion Experienced bit set at 4 packets CLNS fast switching enabled CLNS SSE switching disabled DEC compatibility mode OFF for this interface Next ESH/ISH in 40 seconds Routing Protocol: IS-IS (area0002) Circuit Type: level-1-2 Interface number 0x0, local circuit ID 0x1 Level-1 Metric: 10, Priority: 127, Circuit ID: 3640A.01 Level-1 IPv6 Metric: 10 Number of active level-1 adjacencies: 1 Next IS-IS LAN Level-1 Hello in 2 seconds



This sample output indicates the second VLAN is configured on Fast Ethernet interface 3/0.2. The interface is up and the line protocol is up. CLNS fast switching is enabled by default. The routing protocol is IS-IS and the associated IS-IS process identifier is area0002. The circuit type is Level-1-2 . Fast Ethernet interface 3/0.2 is a Level 1/Level 2 link. The IS-IS priority is 127 on the interface for the Cisco router labeled “3640A,” so 3640A is the DIS and is identified as the DIS in the Circuit ID report. There is one active Level 1 adjacency with SONET/SDH node NE25A.

The following example shows sample output for Fast Ethernet interface 3/0.3:


FastEthernet3/0.3 is up, line protocol is up Checksums enabled, MTU 1497, Encapsulation SAP ERPDUs enabled, min. interval 10 msec. RDPDUs enabled, min. interval 100 msec., Addr Mask enabled Congestion Experienced bit set at 4 packets CLNS fast switching enabled CLNS SSE switching disabled DEC compatibility mode OFF for this interface Next ESH/ISH in 17 seconds Routing Protocol: IS-IS (area0003) Circuit Type: level-1-2 Interface number 0x0, local circuit ID 0x1 Level-1 Metric: 10, Priority: 127, Circuit ID: 3640A.01 Level-1 IPv6 Metric: 10 Number of active level-1 adjacencies: 1 Next IS-IS LAN Level-1 Hello in 1 seconds

The third VLAN is configured on Fast Ethernet interface 3/0.3. The interface is up and the line protocol is up. CLNS fast switching is enabled by default. The routing protocol is IS-IS, and the associated IS-IS process is area0003. The circuit type is Level-1-2. The IS-IS priority is 127 on the interface for the Cisco router labeled “3640A,” so 3640A is the DIS and is identified as the DIS as part of the Circuit ID report. There is one active Level 1 adjacency with SONET/SDH node NE26A.

The next step is to examine the IS-IS adjacencies. Use the show clns is-neighbor detail EXEC command to see the adjacency to the SONET/SDH node NE14A:

3640A# show clns is-neighbor detail

Area area0001:System Id Interface State Type Priority Circuit Id FormatNE15A Fa3/0.1 Up L1 55 3640A.01 Phase V Area Address(es): 39.840f.8011.9999.0000.1111.0001 Uptime: 00:04:16NE14A Fa3/0.1 Up L1 64 3640A.01 Phase V Area Address(es): 39.840f.8011.9999.0000.1111.0001 Uptime: 00:04:16

Area area0002:System Id Interface State Type Priority Circuit Id FormatNE25A Fa3/0.2 Up L1 64 3640A.01 Phase V Area Address(es): 39.840f.8011.9999.0000.1111.0002 Uptime: 00:04:17

Area area0003:System Id Interface State Type Priority Circuit Id FormatNE26B Fa3/0.3 Up L1 64 3640A.01 Phase V Area Address(es): 39.840f.8011.9999.0000.1111.0003 Uptime: 00:04:16

In this sample output, the three IS-IS processes running on the Cisco router are listed by process identifier. The IS-IS process identifiers are area0001, area0002, and area0003.



Examining the IS-IS process identifier area0001 in more detail indicates the following:

• IS-IS process identifier area0001 lists two system identifiers—NE14A and NE15A—on Fast Ethernet interface 3/0.1. The IS-IS adjacency state is up for both SONET network elements. The adjacency type is a Level 1.

• The priority advertised by device NE14A is 64 and the priority advertised by device NE15A is 55. The Circuit ID field uniquely identifies the interface on the IS-IS router with a one-octet number. On an Ethernet or multiaccess network, the circuit and system identifier of the DIS are concatenated to create the pseudonode (.3640A.01). The system identifier has been replaced with the host name by Cisco IOS software, so the pseudonode of IS-IS process area0001 is 3640A.01. The Circuit ID field in the output actually shows the pseudonode identifier.

• The neighbor considers the Cisco router labeled “3640A” to be the DIS. Router 3640A was selected as the DIS because its priority was set to 127, which is higher than the value of 64 advertised by device NE14A, or the value of 55 advertised by device NE15A.

• The adjacency type is Phase V OSI, as opposed to a Phase IV DECNet adjacency. SONET/SDH will always be Phase V.

• The area address is 39.840f.8011.9999.0000.1111.0001.

• The uptime is how long the adjacency has been up, which is a little over 4 minutes. Adjacency uptime is useful debugging information.

Configuring a Cisco Catalyst 2924XL VLAN Using ISL Encapsulation

This section reviews configuration for the Cisco Catalyst switch seen in Figure 4-14 on page 4-24. The example configures three VLANs, one VLAN for each OSI area. VLAN 1 is the default. For management of the switch interface, VLAN 1 is defined and assigned an IP address, as shown in the following example:

interface VLAN1 ip address 192.168.12.50 255.255.255.0 no ip route-cache

In the following example, Fast Ethernet ports 0/1 through 0/4 and 0/13 through 0/22 are assigned to VLAN 1:

interface FastEthernet0/1!interface FastEthernet0/2!interface FastEthernet0/3!interface FastEthernet0/4!interface FastEthernet0/13!interface FastEthernet0/14!interface FastEthernet0/15!interface FastEthernet0/16!interface FastEthernet0/17!interface FastEthernet0/18!interface FastEthernet0/19!



interface FastEthernet0/20!interface FastEthernet0/21!interface FastEthernet0/22!

The switch ports are configured as both access and for VLAN 1. VLAN 1 is the default and does not display in the Cisco IOS software configuration file. The OSI area 39.840f.8011.9999.0000.1111.0001 is assigned to IS-IS routers or network elements connected to VLAN 1. Device NE14A in Figure 4-14 on page 4-24 is connected to switch port 0/2. Device NE15A is connected to switch port 0/3.

In the following example, Fast Ethernet ports 0/5 through 0/8 are assigned to VLAN 2:

interface FastEthernet0/5 switchport access vlan 2!interface FastEthernet0/6 switchport access vlan 2!interface FastEthernet0/7 switchport access vlan 2!interface FastEthernet0/8 switchport access vlan 2

The switch ports are configured as both access and for VLAN 2. The OSI area 39.840f.8011.9999.0000.1111.0002 is assigned to IS-IS routers or network elements connected to VLAN 2. Device NE25A in Figure 4-14 on page 4-24 is connected to switch port 0/5.

In the following example, Fast Ethernet ports 0/9 through 0/12 are assigned to VLAN 3:

!interface FastEthernet0/9 switchport access vlan 3!interface FastEthernet0/10 switchport access vlan 3!interface FastEthernet0/11 switchport access vlan 3!interface FastEthernet0/12 switchport access vlan 3!

The switch ports are configured as both access and for VLAN 3. The OSI area 39.840f.8011.9999.0000.1111.0003 is assigned to IS-IS routers or network elements connected to VLAN 3. Device NE26A in Figure 4-14 is connected to switch port 0/10.

In the following example, switch ports 0/23 and 0/24 are configured as trunks with ISL encapsulation. The Cisco IOS software default trunk encapsulation type is ISL.

interface FastEthernet0/23 switchport mode trunk!interface FastEthernet0/24 switchport mode trunk

Verifying the Cisco Catalyst 2924XL VLAN Configuration Using ISL Encapsulation

To verify port assignment to the VLANs, use the show vlan brief EXEC command:



Router-2924XL# show vlan brief

VLAN Name Status Ports---- -------------------------------- --------- -------------------------------1 default active Fa0/1, Fa0/2, Fa0/3, Fa0/4, Fa0/13, Fa0/14, Fa0/15, Fa0/16, Fa0/17, Fa0/18, Fa0/19, Fa0/20, Fa0/21, Fa0/222 VLAN0002 active Fa0/5, Fa0/6, Fa0/7, Fa0/83 VLAN0003 active Fa0/9, Fa0/10, Fa0/11, Fa0/121002 fddi-default active 1003 token-ring-default active 1004 fddinet-default active 1005 trnet-default active

Status of a specific port such as the device NE14A connection can be verified using the show interface EXEC command:

Router-2924XL# show interface fastethernet 0/3

FastEthernet0/3 is up, line protocol is up Hardware is Fast Ethernet, address is 00d0.796c.acc3 (bia 00d0.796c.acc3) MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255 Encapsulation ARPA, loopback not set, keepalive not set Full-duplex, 100Mb/s, 100BaseTX/FX ARP type: ARPA, ARP Timeout 04:00:00 Last input never, output 00:00:00, output hang never Last clearing of "show interface" counters never Queueing strategy: fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops 5 minute input rate 2000 bits/sec, 0 packets/sec 5 minute output rate 7000 bits/sec, 2 packets/sec 2186 packets input, 1256415 bytes, 0 no buffer Received 1535 broadcasts, 0 runts, 0 giants, 0 throttles 105 input errors, 105 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 watchdog, 1528 multicast 0 input packets with dribble condition detected 12421 packets output, 5859914 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out

Defining IS-IS Multiareas with IEEE 802.1Q TrunkingThis section describes the requirements for implementing an IS-IS multiarea using IEEE 802.1Q encapsulation, instead of the ISL encapsulation used in the “Defining IS-IS Multiareas with ISL Trunking” section. In this configuration, which is shown in Figure 4-15, the network is basically the same as that used in the ISL example—the OSS is located in the data center and the CLNS packets are routed across the network to the central office router. The difference is that IEEE 802.1Q encapsulation will be used for the VLAN trunks.



Figure 4-15 IS-IS Multiarea Network with an IEEE 802.1Q Trunk

Figure 4-16 shows three IS-IS Level 1 areas. For the purpose of example, the areas are small, with only two or three SONET/SDH network elements per area. A typical area would have 30 to 50 network elements. This configuration is done using a Cisco 3640 router and Cisco Catalyst 2924XL switch.

Figure 4-16 IS-IS Multiarea Network Using VLAN Trunking and IEEE 802.1Q Encapsulation

Configuring an IEEE 802.1Q Trunk Router

The following configuration shows the IEEE 802.1Q encapsulation changes on the Cisco router interfaces. The configuration is the same as that seen in the “Configuring an IS-IS Multiarea Network on a VLAN Using ISL Encapsulation” section except for the encapsulation scheme. The encapsulation dot1q command is used on the three subinterfaces, which enables IEEE 802.1Q encapsulation.

interface FastEthernet3/0.1 description IS-IS area 0001 encapsulation dot1Q 1 native ip address 192.168.12.24 255.255.255.0 no ip redirects no cdp enable clns router isis area0001 isis priority 127 tarp enable!interface FastEthernet3/0.2

9562

9

OSS

IP/OSI

CLNS packet flow


VLAN using802.1Q

NE14BArea0001

Area0002

Area0003

NE14A

NE15A

NE25BNE25A

NE26BNE26A

9511

9

CLNS packet flow

Central office router 2924XL

NE14A

NE15A

NE25A

NE26A

NE14BArea0001

Area0002

Area0003

NE25B

NE26B

VLAN using 802.1Q



description IS-IS area 0002 encapsulation dot1Q 2 no ip redirects no cdp enable clns router isis area0002 isis priority 127 tarp enable!interface FastEthernet3/0.3 description IS-IS area 0003 encapsulation dot1Q 3 no ip redirects no cdp enable clns router isis area0003 isis priority 127 tarp enable

Configuring a Cisco Catalyst 2924XL VLAN with IEEE 802.1Q Encapsulation

This section describes the changes required for the Cisco Catalyst switch configuration using the ISL implementation shown in Figure 4-14 on page 4-24, to using the IEEE 802.1Q implementation shown in Figure 4-15 on page 4-32. The configuration is the same as that in the “Configuring a Cisco Catalyst 2924XL VLAN Using ISL Encapsulation” section except for the VLAN encapsulation scheme. The VLAN trunking encapsulation changes from ISL to IEEE 802.1Q encapsulation. Fast Ethernet port 0/23 is set up as the switch trunk port in both examples. In the following example, the switchport trunk encapsulation dot1q command is used on the switch port trunk, which enables IEEE 802.1Q encapsulation:

interface FastEthernet0/23 switchport trunk encapsulation dot1q switchport mode trunk!interface FastEthernet0/24 switchport trunk encapsulation dot1q switchport mode trunk

Verifying a Cisco Catalyst 2924XL VLAN with IEEE 802.1Q Encapsulation

To verify port assignments of the VLANs, use the show vlan brief EXEC command:

Router# show vlan brief

VLAN Name Status Ports---- -------------------------------- --------- -------------------------------1 default active Fa0/1, Fa0/2, Fa0/3, Fa0/4, Fa0/13, Fa0/14, Fa0/15, Fa0/16, Fa0/17, Fa0/18, Fa0/19, Fa0/20, Fa0/21, Fa0/222 VLAN0002 active Fa0/5, Fa0/6, Fa0/7, Fa0/83 VLAN0003 active Fa0/9, Fa0/10, Fa0/11, Fa0/121002 fddi-default active 1003 token-ring-default active 1004 fddinet-default active 1005 trnet-default active



Status of a specific port, such as the device NE14A connection, can be verified using the show interface EXEC command:

Router# show interface fastethernet 0/10

FastEthernet0/10 is up, line protocol is up Hardware is Fast Ethernet, address is 00d0.796c.accb (bia 00d0.796c.accb) MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255 Encapsulation ARPA, loopback not set, keepalive not set Half-duplex, 10Mb/s, 100BaseTX/FX ARP type: ARPA, ARP Timeout 04:00:00 Last input never, output 00:00:00, output hang never Last clearing of "show interface" counters never Queueing strategy: fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 1 packets/sec 1 packets input, 64 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 watchdog, 0 multicast 0 input packets with dribble condition detected 72 packets output, 4039 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out

Defining Multiple Areas with Manual Area AddressingThe designers of the ISO IS-IS protocol realized that there would be situations when the network would need to be readdressed. A provision was made in ISO 10589 to allow multiple area addresses to be associated with one area. ISO 10589 defines a management parameter for manual area addresses. A manual area address parameter is set in each IS-IS router that contains a list of all of the area addresses. The list of area addresses is distributed in the Level 1 LSP. The area comprises the union of all of the area addresses advertised, and the Level 2 router creates a composite list. All of the IS-IS routers, according to ISO 10589, must support at least three area addresses within an area. Two IS-IS routers must have at least one area address in common for an adjacency to be formed.

Originally, the Cisco IOS software supported only three area addresses within an area. Cisco changed this limit to support a minimum of three and a maximum of 254 addresses. The change was made to accommodate the SONET/SDH environment.

Caution The number of manual area addresses that are configured should match between two IS-IS routers. Cisco routers will not form an adjacency if the number of areas do not match. Therefore, changing the number of manual area addresses in a live network can cause a loss of connectivity.

Service providers have used manual area addressing as a tool to expand their networks without readdressing the network. Manual area addressing was used before the IS-IS multiarea feature was available. Incumbent local exchange carriers (ILECs) and PTTs typically deploy large numbers of small-sized SONET/SDH rings or chains. The rings and chains grow over time. Service providers did not want to readdress the network as it grew in size, so they would split the rings into groups and assign an area address. As SONET/SDH nodes were added to the rings or chains in the group, the overall area grew in size. The number of Level 1 IS-IS routers also grew. Eventually, the area size needed to be split.



When a new standalone router was added to the area, one of the groups was migrated to the new router, and the NET was removed from the old group. This technique is used less frequently since the introduction of the IS-IS multiarea feature.

The configuration to add the manual area addressing is based on the network shown in Figure 4-17. NETs will be added to IS-IS process area 0001.

Figure 4-17 Sample Network for Configuring Manual Area Addresses

The following example shows the configuration before manual area addresses are added:

router isis area0001 net 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00

Configuring Manual Area Addressing

This section shows how to configure manual area addresses using the max-area-addresses router configuration command. The default value for this command is three addresses (which will not appear in router configurations).

The following example shows how to change the maximum number of manual area addresses to four, and configure four corresponding NETs:

3640A(config)# router isis area00013640A(config-router)# max-area-addresses 43640A(config-router)# net 39.840f.8011.9999.0000.1111.0004.0010.7bc7.ae40.003640A(config-router)# net 39.840f.8011.9999.0000.1111.0005.0010.7bc7.ae40.003640A(config-router)# net 39.840f.8011.9999.0000.1111.0006.0010.7bc7.ae40.003640A(config-router)# net 39.840f.8011.9999.0000.1111.0007.0010.7bc7.ae40.00%The maximum allowed addresses already configured

The IS-IS router configured for manual area addressing with multiple areas will have multiple NETs associated with one IS-IS process. There will still be one IS-IS process and one IS-IS area.

Note Do not confuse this configuration with the IS-IS multiarea configuration, which has multiple IS-IS processes and areas.

9563

0

NE14BArea0001

Area0002

Area0003

NE14A

NE15A

NE25BNE25A

NE26BNE26A

CLNS packet flow

Fast Ethernet3/0.1

Fast Ethernet3/0.3

Fast Ethernet3/0.2

Central officeRouter 3640A

VLAN using802.1Q



The following example displays the new IS-IS portion of the configuration. Under IS-IS process area0001, there are now four NET statements; one area will advertise the multiple NETs.

router isis area0001 max-area-addresses 4 net 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00 net 39.840f.8011.9999.0000.1111.0004.0010.7bc7.ae40.00 net 39.840f.8011.9999.0000.1111.0005.0010.7bc7.ae40.00 net 39.840f.8011.9999.0000.1111.0006.0010.7bc7.ae40.00!router isis area0002 net 39.840f.8011.9999.0000.1111.0002.0010.7bc7.ae40.00 is-type level-1!router isis area0003 net 39.840f.8011.9999.0000.1111.0003.0010.7bc7.ae40.00 is-type level-1

Use the show clns EXEC command to display all the NETs that are configured:

3640A# show clns

Global CLNS Information: 3 Interfaces Enabled for CLNS NET: 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00 NET: 39.840f.8011.9999.0000.1111.0004.0010.7bc7.ae40.00 NET: 39.840f.8011.9999.0000.1111.0005.0010.7bc7.ae40.00 NET: 39.840f.8011.9999.0000.1111.0006.0010.7bc7.ae40.00 NET: 39.840f.8011.9999.0000.1111.0002.0010.7bc7.ae40.00 NET: 39.840f.8011.9999.0000.1111.0003.0010.7bc7.ae40.00 Configuration Timer: 60, Default Holding Timer: 300, Packet Lifetime 64 ERPDU's requested on locally generated packets Intermediate system operation enabled (CLNS forwarding allowed) IS-IS level-1-2 Router: area0001 Routing for Area: 39.840f.8011.9999.0000.1111.0001 IS-IS level-1 Router: area0002 Routing for Area: 39.840f.8011.9999.0000.1111.0002 IS-IS level-1 Router: area0003 Routing for Area: 39.840f.8011.9999.0000.1111.0003

The show clns protocol EXEC command provides useful information about the manual area addresses configured. The following example displays the system identifier and the IS type as Level-1-2. There are four manual area addresses and four areas are listed. This example displays one area, but all area addresses would be advertised. An adjacent host still needs to be configured for the same number of manual area addresses and matching NETs to form balanced adjacencies.

3640A# show clns protocol

IS-IS Router: area0001 System Id: 0010.7BC7.AE40.00 IS-Type: level-1-2 Maximum nr of area adresses in this area is 4 Manual area address(es): 39.840f.8011.9999.0000.1111.0001 39.840f.8011.9999.0000.1111.0004 39.840f.8011.9999.0000.1111.0005 39.840f.8011.9999.0000.1111.0006 Routing for area address(es): 39.840f.8011.9999.0000.1111.0001 39.840f.8011.9999.0000.1111.0004 39.840f.8011.9999.0000.1111.0005 39.840f.8011.9999.0000.1111.0006 Interfaces supported by IS-IS: FastEthernet3/0.1 - OSI



Redistribute: static (on by default) Distance for L2 CLNS routes: 110 RRR level: none Generate narrow metrics: level-1-2 Accept narrow metrics: level-1-2 Generate wide metrics: none Accept wide metrics: none IS-IS Router: area0002 System Id: 0010.7BC7.AE40.00 IS-Type: level-1 Manual area address(es): 39.840f.8011.9999.0000.1111.0002 Routing for area address(es): 39.840f.8011.9999.0000.1111.0002 Interfaces supported by IS-IS: FastEthernet3/0.2 - OSI Redistribute: static (on by default) Distance for L2 CLNS routes: 110 RRR level: none Generate narrow metrics: level-1-2 Accept narrow metrics: level-1-2 Generate wide metrics: none Accept wide metrics: none IS-IS Router: area0003 System Id: 0010.7BC7.AE40.00 IS-Type: level-1 Manual area address(es): 39.840f.8011.9999.0000.1111.0003 Routing for area address(es): 39.840f.8011.9999.0000.1111.0003 Interfaces supported by IS-IS: FastEthernet3/0.3 - OSI Redistribute: static (on by default) Distance for L2 CLNS routes: 110 RRR level: none Generate narrow metrics: level-1-2 Accept narrow metrics: level-1-2 Generate wide metrics: none Accept wide metrics: none

Verifying Adjacencies in a Network with Manual Area Addresses

Use the show clns neighbors EXEC command to verify that adjacencies are being formed. The following example indicates that an adjacency is up for IS-IS process area0001. The adjacency type is IS but the protocol is End System-Intermediate System (ES-IS) (see bold text), so an IS-IS adjacency is not being formed for IS-IS process area0001:

3640A# show clns neighbors

Area area0001:System Id Interface SNPA State Holdtime Type ProtocolNE15A Fa3/0.1 0010.7bd8.c7d0 Up 263 IS ES-ISNE14A Fa3/0.1 00e0.b064.4325 Up 293 IS ES-IS

Area area0002:System Id Interface SNPA State Holdtime Type ProtocolNE25A Fa3/0.2 00e0.b064.434e Up 22 L1 IS-IS



Area area0003:System Id Interface SNPA State Holdtime Type ProtocolNE26A Fa3/0.3 00d0.5872.9720 Up 28 L1 IS-IS

Troubleshooting Adjacencies in a Network with Manual Area Addresses

Use the debug isis adj-packets command to debug IS-IS adjacency packets. In the following example, an IS-IS Hello (IIH) message comes in on Fast Ethernet interface 3/0.1 and causes a maximum area address mismatch error report to be displayed. (In the following output, text is in bold for purpose of example.) The network element with MAC address 00e0.b064.4325, which is device NE14A, is sending an IIH. The IIH has a different number of maximum area addresses than router 3640A. The number of maximum area addresses needs to be changed to match router 3640A. The change also needs to be made to device NE15A.

3640A# debug isis adj-packets

IS-IS Adjacency related packets debugging is on3640A#00:45:07: ISIS-Adj (area0001): Rec L1 IIH from 00e0.b064.4325 (FastEthernet3/0.1), cir type L1, cir id 00E0.B064.4324.02, length 14700:45:07: ISIS-Adj (area0001): Max-area-addresses mismatch, in L1 IIH from FastEthernet3/0.1

In the network configuration, the maximum number of manual area addresses has been changed to four on devices NE14A, NE14B, and NE15A. The show clns neighbors command now indicates that the adjacency is up and the protocol being used is IS-IS:


Area area0001:System Id Interface SNPA State Holdtime Type ProtocolNE15A Fa3/0.1 0010.7bd8.c7d0 Up 27 L1 IS-ISNE14A Fa3/0.1 00e0.b064.4325 Up 24 L1 IS-IS



Using Generic Routing Encapsulation Tunnels to Prevent Area PartitionsA GNE provides a gateway between the DCN LAN and the SONET DCC. The DCC is the embedded operations channel. There are two DCCs in the SONET/SDH frame: the section DCC and the line DCC. The section DCC is embedded in the section overhead and is made up of three bytes that create a 192-kbps data path. The section DCC has been standardized in TMN for management of the downstream SONET network elements. The line DCC is made up of nine bytes that create a 576-kbps data channel. The standards have carved out the bandwidth in the line DCC, but the TMN standards do not define use of the line DCC. Therefore, vendors have implemented proprietary uses for the line DCC.

Figure 4-18 shows the flow of CLNS packets across the network. For a CLNS packet to move from the OSS to device NE3, the packet must be routed across the DCN to the LAN in central office Router A or Router B. For purpose of example, assume that the packet arrives at the LAN in central office Router A.



Device GNE 1 routes the packet from the LAN to the DCC and forward the packet across the section DCC to device NE2. Device NE2 forwards the packet across the section DCC to device NE3. The action of routing packets between the DCN and the section DCC is the definition of a GNE.

Figure 4-18 Typical GNE Configuration

The service provider will typically implement one GNE per SONET/SDH ring on small-sized rings. The definition of small is typically six network elements or fewer. ILECs and PTTs typically have many small-sized rings or chains to extend services out from the central office to businesses. The service provider will build large collector rings to aggregate bandwidth from the small-sized rings. The larger rings typically have multiple GNEs to add redundancy to ring access, as shown in Figure 4-18. This section describes generic routing encapsulation (GRE) tunnels and the IS-IS default Originate features, both of which can be used to improve redundancy.

CLNS over GRE Tunnels

Traditionally the SONET/SDH technology is deployed in ring topologies for redundancy. In the event of a fiber cut (see Figure 4-19), the ring will wrap and the traffic will be either path switched or line switched onto the protected portion of the fiber. The DCC will be preserved as well.

There are times when it may be necessary to deploy fiber-optic cable in a long chain without the geographic diversity shown in Figure 4-19.

9565

5

CLNS packet flow

OSS

Central office Router A

Central office Router B

GNE 1

GNE 6

NE 2

NE 3

NE 4

NE 7

NE 5

IP/OSI



Figure 4-19 GRE Tunnel over CLNS with Cut Fiber Link

If the fiber gets cut, the OSI area will become partitioned and the OSS will not be able to communicate with some of the network elements.

One solution to the partitioned Level 1 area is to build a GRE tunnel between the Cisco routers for CLNS. The GRE tunnel will pass the IS-IS traffic between the partitioned parts of the network, as shown in Figure 4-19.

Configuring a GRE Tunnel

This section describes a sample GRE configuration. The sample network is shown in Figure 4-20 and depicts the following scenario: Router 3640A is in central office A and router 2600D is in central office D. The two central offices have a SONET/SDH chain running between them. The SONET/SDH network elements are all Level 1 routers. Network elements NE14A and NE25A are both GNEs to the SONET/SDH chain, which is in area 00001. The routers 3640A and 2600D are both Level 1/Level 2 access routers. A fiber cut between the network elements would partition area 0001.

Figure 4-20 Typical Network Before GRE Tunnel Configuration

The configuration builds a GRE tunnel between router 3640A and router 2600D. The GRE tunnel and the IP addresses that are used in the tunnel are shown in Figure 4-21.

1171

74

CLNS packet flow

OSS

IP OSI

Central office Router B

Central office Router A

GNE 6 NE5

NE4

NE3

NE2GNE 1Fiber cut X

X

GRE tunnelGRE tunnel OSI area 0001

1033

54

NE14A

NE25A

NE14B

NE25B

Area0001

Network element (NE) = SONET or SDH node

NE15A

2924XL3640ACentral office A

2600DCentral office D

2924XL

Level 2 adjacency

Level 2 adjacency



Figure 4-21 GRE Tunnel Configuration

The following configuration example for the GRE tunnel shows that the router labeled 2600D in Figure 4-21 is configured for IS-IS routing in area 0001:

router isis area0001 net 39.840f.8011.9999.0000.1111.0001.00e0.1ee3.c720.00

Router 2600D is connected to the SONET/SDH device NE25A over Ethernet interface 0/0:

interface Ethernet0/0 ip address 192.168.5.189 255.255.255.192 half-duplex clns router isis area0001

A loopback interface has been created for the GRE tunnel to terminate on router 2600D:

interface Loopback0 ip address 192.168.5.252 255.255.255.192

The source of the GRE tunnel on router 2600D is the loopback address 192.168.5.252. The tunnel destination is the loopback IP address 192.168.14.252 on the router labeled 3640A in Figure 4-21. The routing metric assigned to the GRE tunnel is 30. Some service providers prefer to use the tunnel only in the event of an outage. IS-IS routing for CLNS has been turned up on the tunnel. The IS-IS metric can range from 1 to 63, with 63 being the worst route. The GRE keepalive feature is implemented in the example. The keepalive feature will take down the GRE tunnel interface if the far end of the tunnel becomes unavailable. See the following example:

interface Tunnel1 no ip address keepalive 3 3 clns router isis area0001 isis metric 30 tunnel source 192.168.5.252 tunnel destination 192.168.14.252 tarp enable

The following example shows how to configure router 3640A for IS-IS routing in area 0001:


192.168.14.252

192.168.5.252

1033

55

NE14A

NE25A

NE14B

NE25B

Area0001

NE15A

2924XL

3640ACentral office A


2924XL

GRE tunnel

Level 2 adjacency

Level 2 adjacency



In the following example, router 3640A is connected to SONET/SDH device NE14A over Fast Ethernet interface 3/0.1:

interface FastEthernet3/0.1 description ISIS area 0001 encapsulation dot1Q 1 native ip address 192.168.12.24 255.255.255.0 no ip redirects no cdp enable clns router isis area0001 isis priority 127 tarp enable

The following example creates a loopback interface for the GRE tunnel to terminate on router 3640A:


The source of the GRE tunnel on router 3640A is the loopback 0 IP address 192.168.14.252. The tunnel destination is loopback IP address 192.168.5.252 on router 2600D. The routing metric assigned to the GRE tunnel is 30. The GRE keepalive feature is implemented. See the following example:

interface Tunnel1 no ip address keepalive 3 3 clns router isis area0001 isis metric 30 tunnel source 192.168.5.252 tunnel destination 192.168.14.252 tarp enable

Note The source and destination IP addresses must match on each end of the tunnel. If the IP addresses do not match, the tunnel line protocol will not come up. If you choose to use a source or destination interface when configuring the tunnel, the IP address of the interface of the tunnel will be used.

The status of the tunnel can be examined with the show interface command. In the following example, tunnel 1 is up and line protocol is up. The keepalive option is set to send keepalives every 3 seconds, and set to retry three times before marking the interface line protocol down.

3640A# show interface tunnel 1

Tunnel1 is up, line protocol is up Hardware is Tunnel MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec, reliability 255/255, txload 28/255, rxload 28/255 Encapsulation TUNNEL, loopback not set Keepalive set (3 sec), retries 3 Tunnel source 192.168.14.252, destination 192.168.5.252 Tunnel protocol/transport GRE/IP, key disabled, sequencing disabled Tunnel TTL 255 Checksumming of packets disabled, fast tunneling enabled Last input 00:00:07, output 00:00:00, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 29 Queueing strategy: fifo Output queue: 0/0 (size/max) 5 minute input rate 1000 bits/sec, 0 packets/sec 5 minute output rate 1000 bits/sec, 0 packets/sec 1767 packets input, 705632 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 1945 packets output, 712879 bytes, 0 underruns



0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out

Use the debug tunnel command to debug the tunnel. The following example shows the debug tunnel command output:

3640A# debug tunnel

Tunnel Interface debugging is on3640A#

01:11:24: Tunnel1: GRE/IP to decaps 192.168.5.252->192.168.14.252 (len=1537 ttl=253)01:11:24: Tunnel1: GRE decapsulated CLNS packet01:11:24: Tunnel1: GRE/IP encapsulated 192.168.14.252->192.168.5.252 (linktype=7, len=48)01:11:24: Tunnel1: GRE/IP to decaps 192.168.5.252->192.168.14.252 (len=24 ttl=252)01:11:25: Tunnel1: GRE/IP encapsulated 192.168.14.252->192.168.5.252 (linktype=25, len=1537)01:11:27: Tunnel1: GRE/IP encapsulated 192.168.14.252->192.168.5.252 (linktype=7, len=48)01:11:27: Tunnel1: GRE/IP to decaps 192.168.5.252->192.168.14.252 (len=24 ttl=252)01:11:30: Tunnel1: GRE/IP encapsulated 192.168.14.252->192.168.5.252 (linktype=7, len=48)01:11:30: Tunnel1: GRE/IP to decaps 192.168.5.252->192.168.14.252 (len=24 ttl=252)01:11:31: Tunnel1: GRE/IP to decaps 192.168.5.252->192.168.14.252 (len=1537 ttl=253)01:11:31: Tunnel1: GRE decapsulated CLNS packet

Use the debug tunnel keepalive command to debug the tunnel keepalive. In the following example, notice that the keepalive packets are being sent every 3 seconds:

3640A# debug tunnel keepalive

Tunnel keepalive debugging is on3640A#

01:12:27: Tunnel1: sending keepalive, 192.168.5.252->192.168.14.252 (len=24 ttl=255), counter=101:12:27: Tunnel1: keepalive received, 192.168.5.252->192.168.14.252 (len=24 ttl=252), resetting counter01:12:30: Tunnel1: sending keepalive, 192.168.5.252->192.168.14.252 (len=24 ttl=255), counter=101:12:30: Tunnel1: keepalive received, 192.168.5.252->192.168.14.252 (len=24 ttl=252), resetting counter01:12:33: Tunnel1: sending keepalive, 192.168.5.252->192.168.14.252 (len=24 ttl=255), counter=101:12:33: Tunnel1: keepalive received, 192.168.5.252->192.168.14.252 (len=24 ttl=252), resetting counter01:12:36: Tunnel1: sending keepalive, 192.168.5.252->192.168.14.252 (len=24 ttl=255), counter=101:12:36: Tunnel1: keepalive received, 192.168.5.252->192.168.14.252 (len=24 ttl=252), resetting counter01:12:39: Tunnel1: sending keepalive, 192.168.5.252->192.168.14.252 (len=24 ttl=255), counter=101:12:39: Tunnel1: keepalive received, 192.168.5.252->192.168.14.252 (len=24 ttl=252), resetting counter01:12:42: Tunnel1: sending keepalive, 192.168.5.252->192.168.14.252 (len=24 ttl=255), counter=101:12:42: Tunnel1: keepalive received, 192.168.5.252->192.168.14.252 (len=24 ttl=252), resetting counter01:12:45: Tunnel1: sending keepalive, 192.168.5.252->192.168.14.252 (len=24 ttl=255), counter=101:12:45: Tunnel1: keepalive received, 192.168.5.252->192.168.14.252 (len=24 ttl=252), resetting counter



The next step is to look at the IS-IS topology after breaking the link between SONET/SDH nodes. The following example shows the IS-IS topology with the GRE tunnel up and the SONET/SDH chain in place:

3640A# show isis topology

Area area0001:IS-IS IP paths to level-1 routersSystem Id Metric Next-Hop Interface SNPA3640A --NE15A 30 NE14A Fa3/0.1 00e0.b064.4325 NE25B 40 NE14A Fa3/0.1 00e0.b064.4325 NE14B 20 NE14A Fa3/0.1 00e0.b064.4325 2600D 30 2600D Tu1 *Tunnel* NE14A 10 NE14A Fa3/0.1 00e0.b064.4325 NE25A 40 2600D Tu1 *Tunnel*

IS-IS IP paths to level-2 routersSystem Id Metric Next-Hop Interface SNPA3640A --2600D 30 2600D Tu1 *Tunnel*

All of the network elements can be reached within the area from router 3640A, even though the IS-IS metric was raised to 30 on the tunnel. The tunnel is still the preferred path to router 2600D and network element device NE25A. The traffic could be forced out of the tunnel and onto the SONET/SDH DCC by raising the IS-IS metric.

The next part of this example breaks the connection between devices NE14B and NE15A, as shown in Figure 4-22. The example after the figure displays the new IS-IS topology after the connection break. All of the network elements and routers are still listed, and the connection to devices NE15A and NE25B has moved to the tunnel.

Figure 4-22 GRE Tunnel with Broken Connection


Area area0001:IS-IS IP paths to level-1 routersSystem Id Metric Next-Hop Interface SNPA3640A --NE15A 60 2600D Tu1 *Tunnel* NE25B 50 2600D Tu1 *Tunnel* NE14B 20 NE14A Fa3/0.1 00e0.b064.4325 2600D 30 2600D Tu1 *Tunnel*

192.168.14.252

192.168.5.252

1033

56

NE14A

NE25A

NE14B

NE25B

Area0001

NE15A

2924XL

3640ACentral office A


2924XL

GRE tunnel

Level 2 adjacency

Level 2 adjacency



NE14A 10 NE14A Fa3/0.1 00e0.b064.4325 NE25A 40 2600D Tu1 *Tunnel*

Without the tunnel connection, routers 3640A and 2600D would not be able to see the entire IS-IS area 0001. Devices may not be able to communicate, depending upon where the devices sit in the network. The loss of connectivity can be demonstrated by shutting down the tunnel interface.

The following example displays the new IS-IS topology and indicates that packets reaching router 3640A from the network cloud could be forwarded only to devices NE14A and NE14B.


Area area0001:IS-IS IP paths to level-1 routersSystem Id Metric Next-Hop Interface SNPA3640A --NE15A **NE25B **NE14B 20 NE14A Fa3/0.1 00e0.b064.4325 2600D **NE14A 10 NE14A Fa3/0.1 00e0.b064.4325 NE25A **

IS-IS Attach-Bit Control FeatureRouting traffic between Level 1 areas is done by Level 2 routers. Level 1 routers forward the packets to their nearest Level 1/Level 2 router. Typically located at the access layer of the network, the Level 1/Level 2 routers are standalone Cisco routers, and Level 1 routers are SONET/SDH network elements.

The Level 1/Level 2 Cisco router identifies itself by setting the attach-bit in the link-state packets (LSPs). Often service providers have more than one Level 1/Level 2 router per area for redundancy. On large rings, there may be multiple GNEs with access to separate Level 1/Level 2 routers. A Level 1/Level 2 router can lose connectivity to the area with the OSS or the network backbone. If a Level 1/Level 2 Cisco router is configured for IS-IS multiarea, the Level 1/Level 2 router will set the attach bit. If there are multiple Level 1/ Level 2 routers in the same central office networked to share the WAN link, these two routers would form a Level 2 adjacency. The Level 2 attach bit would be set. In either case, the central office Level 1/Level 2 routers will not have access to the OSS systems in the NOC if the WAN link is down. Packets forwarded to the Level 1/Level 2 router destined for the NOC will be discarded. The service provider wants the packets to be sent out the alternate GNE to an alternate central office.

There is a solution to this problem. For purpose of example, we will use a router named “3640A” (see Figure 4-23) to show the configurations and verifications. Router 3640A will continue to set the attach-bit when it has another Level 2 adjacency or the Cisco IOS IS-IS Multiarea feature is configured. In other words, router 3640A will set the attach-bit if it can reach multiple areas. The Level 1 routers nearest router 3640A will continue to forward traffic to router 3640A. Traffic sent to router 3640A is most likely destined for the area containing the OSS. The traffic, which is usually alarms destined for the NOC and alarm packets, will be dropped.

Cisco developed the IS-IS Attach-Bit Control feature to provide the network administrator with more control in setting the attach-bit. The feature is modeled after the IP default-information originate route-map router subcommand. The new command, set-attach-bit, is an IS-IS CLNS router subcommand and its syntax is as follows:

router isisset-attach-bit {always | never | route-map mapname}



The route-map keyword can be used to specify multiple CLNS routes or prefixes. If one of the routes or prefixes is matched in the Level 2 CLNS routing table, the Level 1/Level 2 router sets the attach bit in the LSP.

The following example contains five SONET/SDH network elements in a chain between central office A and central office D. NE14A and router 3640A are located in central office A. NE14A is a GNE between the SONET/SDH DCC and the Ethernet. Device NE14A forwards traffic destined for another area to the nearest Level 2 router, which is router 3640A.

Located in central office D is the Level 1/Level 2 router labeled 2600D and GNE NE25A. The other three SONET/SDH network elements are located is separate central offices. All of these devices are configured for area 0001. Router 3640A is configured for IS-IS multiarea and is located in area 0003. Figure 4-23 shows the network and the connections to the backbone, which is area 9999.

Figure 4-23 Network with IS-IS Attach-Bit Control Configured

Verifying IS-IS Attach-Bit Control

To verify that the IS-IS Attach-Bit Control feature is configured, first display a baseline configuration without the IS-IS Attach-Bit Control feature configured. The network administrator can look at the attach-bit settings using the show isis database EXEC command. The following example shows output for router 3640A. In the IS-IS process called area000, router 3640A’s attach-bit is set to 1 in the Level-1 link state database. The attach-bit field is labeled “ATT.” The router is configured to run two IS-IS processes, area0001 and area0003.

3640A# show isis database

Area area0001:IS-IS Level-1 Link State Database:LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL3640A.00-00 * 0x00000009 0x7AB5 758 1/0/03640A.03-00 * 0x00000007 0x6705 649 0/0/0NE15A.00-00 0x00000009 0x88E2 520 0/0/0NE25B.00-00 0x0000000A 0x1DB6 660 0/0/0NE25B.02-00 0x00000007 0x2941 871 0/0/0NE14B.00-00 0x00000008 0xF840 744 0/0/0NE14B.02-00 0x00000007 0x622C 794 0/0/02600D.00-00 0x0000000A 0xC715 758 1/0/0NE14A.00-00 0x00000008 0x7C68 578 0/0/0NE14A.01-00 0x00000007 0x8232 735 0/0/0NE25A.00-00 0x00000007 0x8E92 563 0/0/0NE25A.01-00 0x00000007 0x95E2 745 0/0/0

1035

18

NE14AVLAN1

VLAN3

NE25A

NE14B

NE26A NE26B

NE25B

Area0001

Area0003

NE15A

2924XL3640ACentral office A


2924XL

Level 2 adjacency

Level 2 adjacency

Backbonearea 9999



NE25A.02-00 0x00000007 0x69E3 578 0/0/0IS-IS Level-2 Link State Database:LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OLBackBoneR1.00-00 0x0000000D 0x6BEF 599 0/0/03640A.00-00 * 0x0000000A 0x8457 758 0/0/03640A.02-00 * 0x00000007 0xC0AC 886 0/0/02600D.00-00 0x00000009 0xDE1C 765 0/0/02600D.02-00 0x00000007 0xFA61 847 0/0/0

Area area0003:IS-IS Level-1 Link State Database:LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL3631A.00-00 0x00000008 0x33D5 827 0/0/0NE26B.00-00 0x00000009 0xAFE0 652 0/0/0NE26B.02-00 0x00000007 0x87A3 554 0/0/03640A.00-00 * 0x00000008 0x52DE 564 1/0/03640A.01-00 * 0x00000007 0x5325 532 0/0/0NE26A.00-00 0x00000009 0xA756 668 0/0/0NE26A.02-00 0x00000008 0x8904 1128 0/0/0

Next, use the ping clns and show clns route EXEC commands to verify connectivity. Following is the output of ping to an IS-IS router in the area backbone:

3640A# ping clns 39.840f.8011.9999.0000.1111.9999.000d.bc2e.6d80.00

Type escape sequence to abort.Sending 5, 100-byte CLNS Echos with timeout 2 seconds!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

The following example shows the CLNS routing table with a route to backbone area 9999 (text in bold is for purpose of example only and indicates the backbone route):

3640A# show clns route

Codes: C - connected, S - static, d - DecnetIV I - ISO-IGRP, i - IS-IS, e - ES-IS B - BGP, b - eBGP-neighbor

C 39.840f.8011.9999.0000.1111.0003 [2/0], Local IS-IS AreaC 39.840f.8011.9999.0000.1111.0001 [2/0], Local IS-IS AreaC 39.840f.8011.9999.0000.1111.0003.0010.7bc7.ae40.00 [1/0], Local IS-IS NETC 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00 [1/0], Local IS-IS NET

i 39.840f.8011.9999.0000.1111.9999 [110/10] via BackBoneR1, Ethernet0/1

Disconnect the connection to the backbone from router 3640A as shown in Figure 4-24, and display the IS-IS database again using the show isis database EXEC command.



Figure 4-24 Broken Network Link with IS-IS Attach-Bit Control Configured

Router 3640A still has the attach-bit set because the router is configured for the IS-IS Multiarea feature, so router 3640A can reach multiple areas. (You can determine the attach-bit setting by looking at the ATT field in the show isis database command output. The attach-bit is set when the value is 1.)


Area area0001:IS-IS Level-1 Link State Database:LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL3640A.00-00 * 0x00000004 0x84B0 1181 1/0/03640A.03-00 * 0x00000002 0x71FF 1180 0/0/0NE15A.00-00 0x00000004 0x92DD 612 0/0/0NE25B.00-00 0x00000004 0x29B0 491 0/0/0NE25B.02-00 0x00000003 0x313D 1165 0/0/0NE14B.00-00 0x00000003 0x033B 417 0/0/0NE14B.02-00 0x00000002 0x6C27 537 0/0/0NE14A.00-00 0x00000005 0x8265 1179 0/0/0NE14A.01-00 0x00000003 0x8A2E 1170 0/0/0NE25A.00-00 0x00000003 0x46FD 1056 0/0/0NE25A.02-00 0x00000002 0x73DE 409 0/0/0IS-IS Level-2 Link State Database:LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL3640A.00-00 * 0x00000001 0x4A75 1173 0/0/0

Area area0003:IS-IS Level-1 Link State Database:LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL3631A.00-00 0x00000003 0x3DD0 503 0/0/0NE26B.00-00 0x00000004 0xB9DB 576 0/0/0NE26B.02-00 0x00000003 0x8F9F 538 0/0/03640A.00-00 * 0x00000005 0x58DB 1177 1/0/03640A.01-00 * 0x00000004 0x5922 1177 0/0/0NE26A.00-00 0x00000005 0xAF52 1178 0/0/0NE26A.02-00 0x00000003 0x93FE 1166 0/0/0

1035

19

NE14A

NE25A

NE14B

NE26A NE26B

NE25B

Area0001

Area0003

NE15A

2924XL

3640ACentralOffice A

2600DCentralOffice D

2924XL

Level 2 adjacency

Level 2 adjacency

Backbonearea 9999

VLAN1

VLAN3



The CLNS routing table displayed by the show clns route EXEC command shows that no connection to the backbone is available. There are only routes for areas 39.840f.8011.9999.0000.1111.0003 and 39.840f.8011.9999.1111.0001. The backbone route 39.840f.8011.9999.0000.1111.9999 has dropped out of the routing table. Packets destined to the backbone are dropped by router 3640A.

3640A# show clns route


C 39.840f.8011.9999.0000.1111.0003 [2/0], Local IS-IS AreaC 39.840f.8011.9999.0000.1111.0001 [2/0], Local IS-IS AreaC 39.840f.8011.9999.0000.1111.0003.0010.7bc7.ae40.00 [1/0], Local IS-IS NETC 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00 [1/0], Local IS-IS NET

The following example configures the set-attach-bit command. The route-map command sets conditions for setting the attach-bit. The route-map name or map tag assigned for the example is BackBone_Connection. The match clns command names the clns filter command that contains the NSAP address to match in the route table. In this example, the focus is on connectivity to the backbone.

clns filter-set BackBone_Area permit 39.840f.8011.9999.0000.1111.9999!router isis area0001 net 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00 set-attached-bit route-map BackBone_Connection!route-map BackBone_Connection permit 10 match clns address BackBone_Area

The following example reexamines the IS-IS database and the CLNS routing table after the set-attach-bit command is configured. The Level 1 database for the IS-IS area process area0001 shows that router 3640A is no longer setting the attach bit. The ATT field is set to zero for the LSP from router 3640A. Router 2600D is setting the attach-bit and providing access to the backbone. The ATT field is set to 1 for the LSP from router 2600D.


Area area0001:IS-IS Level-1 Link State Database:LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL3640A.00-00 * 0x00000011 0x62CD 1143 0/0/03640A.03-00 * 0x0000000E 0x590C 557 0/0/0NE15A.00-00 0x00000011 0x78EA 910 0/0/0NE25B.00-00 0x0000000F 0x13BB 766 0/0/0NE25B.02-00 0x0000000E 0x1B48 671 0/0/0NE14B.00-00 0x0000000F 0xEA47 700 0/0/0NE14B.02-00 0x0000000E 0x5433 512 0/0/02600D.00-00 0x00000011 0xB91C 1013 1/0/0NE14A.00-00 0x0000000F 0x6E6F 647 0/0/0NE14A.01-00 0x0000000F 0x723A 1106 0/0/0NE25A.00-00 0x0000000E 0x8099 879 0/0/0NE25A.01-00 0x0000000F 0x85EA 917 0/0/0NE25A.02-00 0x0000000F 0x59EB 1140 0/0/0IS-IS Level-2 Link State Database:LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OLBackBoneR1.00-00 0x00000010 0x65F2 426 0/0/03640A.00-00 * 0x00000010 0x2C84 1131 0/0/03640A.02-00 * 0x0000000E 0xB2B3 541 0/0/02600D.00-00 0x0000000F 0xD222 454 0/0/02600D.02-00 0x0000000F 0xEA69 818 0/0/0



Area area0003:IS-IS Level-1 Link State Database:LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL3631A.00-00 0x0000000F 0x25DC 491 0/0/0NE26B.00-00 0x00000010 0xA1E7 523 0/0/0NE26B.02-00 0x0000000F 0x77AB 975 0/0/03640A.00-00 * 0x0000000F 0x44E5 562 1/0/03640A.01-00 * 0x0000000E 0x452C 510 0/0/0NE26A.00-00 0x00000011 0x975E 1151 0/0/0NE26A.02-00 0x0000000F 0x7B0B 1144 0/0/03640A#

Additional information on the IS-IS Attach-Bit Control feature can be found on CCO. Refer also to the Cisco IOS Product Marketing Application Note, Using the IS-IS Attach-Bit Control Feature.

Using IP over CLNS Tunnels to Access Remote DevicesThe SONET/SDH DCC is an extension of the telco DCN. Service providers do not want to build the DCN out to every SONET/SDH location. Figure 4-25 shows a typical telco network where each of the network elements are located at different physical locations. The DCC is used to communicate to remote SONET/SDH add/drop multiplexers (ADMs) on the ring.

Figure 4-25 Typical Telco Network with Network Elements at Different Locations

Service providers need to reach asynchronous and IP devices in the same location as the SONET/SDH nodes. Typically, the service providers are trying to access a contact closure device, as shown in Figure 4-26. Service providers can use the DCC by tunneling IP over CLNS. The router located in the central office in front of the GNE is usually the one used to create the tunnel. The router in the remote location usually terminates the CLNS tunnel and the TCP/IP session. The data is sent out the asynchronous connection to the contact closure device.

1033

51

CLNS packet flow

OSS

IP OSI

Central office router

NE14A

Area0001

NE15A

NE25A

NE26A

NE26BNE26B

NE14B

NE25ANE25A


http://www.cisco.com/cpropart/salestools/cc/pd/iosw/prodlit/isis_an.htm



Figure 4-26 Telco Network Data Flow to a Contact Closure Device

Cisco has developed a contact closure device, which is a network module called the NM-AIC-64 that can be installed in the Cisco 2600, 3600, and 3700 series routers. The tunneling examples in this section use a Contact Closure device (the NM-AIC-64) embedded in router 3631A shown in Figure 4-27.

Figure 4-27 Telco Network with Cisco Contact Closure Device

Configuring a Tunnel Using IP over CLNS

In Figure 4-27, the IP over CLNS tunnel is created from the Cisco 3640A router to the Cisco 3631A router. The following example shows the CLNS tunnel configuration for the two routers:

Cisco 3640A Router Configurationinterface CTunnel1 description connection remote site with 3631A ip address 192.168.10.1 255.255.255.252 ctunnel destination 39.840f.8011.9999.0000.1111.0003.0001.6444.3410.cc!router isis area0003 net 39.840f.8011.9999.0000.1111.0003.0010.7bc7.ae40.00 is-type level-1

Cisco 3631A Router Configurationclns routing!interface CTunnel1

1033

52

TCP/IP over CLNS

TCP/IP

IP

DCCDCCAsynchronous

ContactClosureOSS

NE

GNE GNE

NE

1033

53

CLNS packet flow

IP over CLNS tunnel

NE14A NE14B

NE15A

Area0001

Area0002

Area0003

NE25A NE25B

NE26A

VLAN using ISL

3640ACentral office

router

2924XL

NE26B3631A



ip address 192.168.10.2 255.255.255.252 ctunnel destination 39.840f.8011.9999.0000.1111.0003.0010.7bc7.ae40.cc!router isis area0003 net 39.840f.8011.9999.0000.1111.0003.0001.6444.3410.00 is-type level-1

Verifying the IP over CLNS Tunnel Configuration

The tunnel is actually configured as an interface and the status of the tunnel can be checked with the show interfaces ctunnel1 command, as follows:

3640A# show interfaces ctunnel1

CTunnel1 is up, line protocol is up Hardware is CTunnel Description: connection remote site with 3631A Internet address is 192.168.10.1/30 MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec, reliability 255/255, txload 56/255, rxload 28/255 Encapsulation TUNNEL, loopback not set Keepalive set (10 sec) Tunnel destination 39.840f.8011.9999.0000.1111.0003.0001.6444.3410.cc Last input 00:00:00, output 00:00:00, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/0 (size/max) 5 minute input rate 1000 bits/sec, 3 packets/sec 5 minute output rate 2000 bits/sec, 2 packets/sec 217 packets input, 13104 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 177 packets output, 33658 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out

The report shows that the CLNS tunnel is physically up. The “line protocol is up” report indicates that the router has a route to the CLNS tunnel destination. The hardware report indicates the interface type is CTunnel. The tunnel destination is 39.840f.8011.9999.0000.1111.0003.0001.6444.3410.cc, which is the NET for the Cisco 3631A router. Additional information about the show interfaces ctunnel command can be found in the Cisco IOS Software Release 12.1T IP over a CLNS Tunnel feature module at the following URL: http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1834/products_feature_guide09186a0080080382.html

Note Cisco released the IP over CLNS Tunnel feature before an industry standard existed. An RFC has been created to tunnel IPv4 and IPv6 over CLNS. Cisco supports the feature beginning in Cisco IOS Release 12.3(7)T. The default tunnel mode is the original Cisco solution. An option on the tunnel interface allows the tunnel to be set to GRE. The Cisco IOS Release 12.3(7)T document describing the CLNS Support for GRE Tunneling of IPv4 and IPv6 Packets in CLNS Networks feature module at the following URL: http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps5207/products_feature_guide09186a00801ffb3d.html


http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1834/products_feature_guide09186a0080080382.html




http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps5207/products_feature_guide09186a00801ffb3d.html





Configuring a Contact Closure Device

The tunnel in the previous configuration example was created to access the Contact Closure device (the NM-AIC-64) in the Cisco 3631 router. The NM-AIC-64 is installed in the second network module slot and communicates across the PCI bus in the router. The NM-AIC-64 requires an IP address to access it, and must be assigned an IP address and a static route that points to the IP address of the NM-AIC-64. The static route should be redistributed into the IP routing protocol.

The following example shows the basic configuration for the NM-AIC-64:

alarm-interface 2 ip address 192.168.10.5!ip route 192.168.10.5 255.255.255.255 Serial2/0!router ospf 795 log-adjacency-changes redistribute static subnets network 192.168.0.0 0.0.255.255 area 0

Verifying the Contact Closure Device Configuration

The following example shows the report from issuing the show ip route command on the Cisco 3631A router. The static route to reach NM-AIC-64 is highlighted in bold text for purpose of example. Notice that the NM-AIC-64 looks like a serial device connected to the router.

3631A# show ip route

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route

Gateway of last resort is not set

O 192.168.12.0/24 [110/11112] via 192.168.10.1, 00:10:51, CTunnel1 192.168.10.0/24 is variably subnetted, 2 subnets, 2 masksC 192.168.10.0/30 is directly connected, CTunnel1S 192.168.10.5/32 is directly connected, Serial2/0O 192.168.0.0/24 [110/11121] via 192.168.10.1, 00:10:51, CTunnel1 192.168.2.0/26 is subnetted, 2 subnetsO 192.168.2.64 [110/11112] via 192.168.10.1, 00:10:51, CTunnel1O 192.168.2.128 [110/11112] via 192.168.10.1, 00:10:51, CTunnel1 192.168.3.0/26 is subnetted, 1 subnetsO 192.168.3.128 [110/11122] via 192.168.10.1, 00:10:52, CTunnel1

The following example shows the report from issuing the show ip route command on the Cisco 3640A router. The static route to reach the NM-AIC-64 is highlighted in bold text for purpose of example, and looks like an external route learned over OSPF.

3640A# show ip route

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR



P - periodic downloaded static route

Gateway of last resort is 192.168.0.1 to network 0.0.0.0

C 192.168.12.0/24 is directly connected, FastEthernet3/0.1 192.168.10.0/24 is variably subnetted, 2 subnets, 2 masksC 192.168.10.0/30 is directly connected, CTunnel1O E2 192.168.10.5/32 [110/20] via 192.168.10.2, 00:09:48, CTunnel1C 192.168.0.0/24 is directly connected, Ethernet0/0 12.0.0.0/32 is subnetted, 1 subnetsR 12.222.16.0 [120/1] via 192.168.0.1, 00:00:16, Ethernet0/0 192.168.2.0/26 is subnetted, 2 subnetsC 192.168.2.64 is directly connected, FastEthernet3/0.2C 192.168.2.128 is directly connected, FastEthernet3/0.3 192.168.3.0/26 is subnetted, 1 subnetsO 192.168.3.128 [110/11] via 192.168.2.190, 00:09:48, FastEthernet3/0.3R* 0.0.0.0/0 [120/1] via 192.168.0.1, 00:00:16, Ethernet0/0

For more information about configuring the NM-AIC-64, refer to the document NM-AIC-64, Contact Closure Network Module.

Mapping NSAPs to Device Names Using TARPThis section describes a method of mapping NSAPs to device names. In North America, ILECs and long distance carriers use a TID—a network-wide unique target identifier—to name a piece of equipment. The TID is a string of up to 20 case-sensitive characters. Service providers needed a dynamic method to map TIDs to NSAPs or network entity titles (NETs)—the terms NSAP and NET are often used interchangeably within the telco industry—and TARP serves that purpose. TARP runs over the Connectionless Network Protocol (CLNP), as defined in ISO 8473, and all Cisco routers that support CLNS routing support TARP. TARP is documented in GR-253-Core section 8. Additional documentation about TARP can be found on the ATIS website at www.atis.org. TARP was developed as part of the SONET Interoperability Forum (SIF).

TARP was developed to map the name for a network element (NE) to an NSAP. The OSS administrator typically knows the network element TID when building a profile for the device, but often does not know the NSAP. TARP was designed to dynamically map the TID to the NSAP. TARP was implemented on the router to facilitate the mapping across a network. Typically, the service provider has an OSS in the data center that needs to communicate with a network element in the central office, as shown in Figure 4-28.

Figure 4-28 Typical TARP Configuration and Packet Flow95

114

OSS

Central office router

IP/OSI

VLAN using ISL

NE14A

NE15A

NE25A

NE26A

NE14BArea0001

Area0002

Area0003

NE25A

NE26B

TARP packet flow


http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ft_aicnm.htm


A router can be configured to participate in TARP. The router is actually assigned a TID. The NET of a router is associated with the TID.

Note The network layer for a device cannot have an address in OSI; instead, the device must have an NET. The NET at the network layer is actually an NSAP with a selector value of 00. IS-IS routers are assigned NETs. The TARP cache maps the NET of the IS-IS router to the TID.

The following example shows how to configure the IS-IS router to assign the NET (notice that the NET is the NSAP with a network selector value of 00):


In OSI, File Transfer, Access, and Management (FTAM) and other applications have a specific network selector (also called N-selector) value that identifies the application. The network selector value for the TARP application are the hexadecimal digits AF. The network selector is analogous to a TCP port number.

TARP uses five types of protocol data units (PDUs):

• Type 1 PDU is a request for the NSAP with a specific TID value within a Level 1 routing area. The type 1 PDU is propagated to all of the IS-IS Level 1 adjacencies and ES-IS adjacencies. A separate type 1 PDU is sent to every adjacency. A type 1 packet can be issued from a Cisco router using the tarp resolve tid or tarp resolve tid 1 EXEC command.

• Type 2 PDU is a request for the NSAP with a specific TID value within a Level 2 routing area. A type 2 request PDU is propagated by an individual type 2 PDU being sent to all of the IS-IS and ES-IS adjacencies in the IS-IS router. A type 2 packet can be issued from a Cisco router using the tarp resolve tid 2 EXEC command. The tarp resolve tid EXEC command issues a type 2 packet after the type 1 fails.

• Type 3 PDU is a response to a TARP request. The TARP request could be a type 1, type 2, or type 5 PDU. The type 3 packet is a unicast PDU, and a single PDU is sent directly back to the originator.

• Type 4 PDU is a notification of an NSAP address change or a TID change. The type 4 PDU is propagated through the entire network. The type 4 PDU is sent to all of the adjacencies of the network element.

• Type 5 PDU is a request for a TID that matches a specific NSAP. The type 5 PDU is sent directly to a specific NSAP. A type 5 PDU can be issued from a Cisco router using the tarp query EXEC command.

In a traditional IS-IS implementation, a single IS-IS process is configured. The TARP application uses the NET in the single process for creating the NSAP. If the router is configured with an IS-IS multiarea, TARP will behave as follows:

• The router uses the NET of the Level 2 area if a Level 2 process is configured, so that the NSAP for the TID will be the NET of the Level 2 process with a selector value of AF.

• If no Level 2 process is configured and multiple Level 1 processes are configured, the first active Level 1 process NET will be used.

Note Multiple Level 1 processes are sorted by the process name alphanumerically, and capital letters are sorted ahead of lowercase letters.



If a Level 1 process is added or removed, the NSAP associated with the TID can change at the next reload of the router.

• Type 1 PDUs received are processed as normal. The TARP data cache is checked for an entry. If no entry is present, the type 1 PDU is propagated to all Level 1 IS-IS and ES-IS adjacencies in the same Level 1 area.

• Type 2 PDUs received are processed as normal. The TARP data cache is checked for an entry. If no entry is present, the type 2 PDU is propagated to all IS-IS and ES-IS adjacencies. If the PDU originated in a different Level 1 IS-IS area, the TID and NET of the source will be cached in the TARP data cache.

• Type 4 PDUs are forwarded to all ES-IS and IS-IS adjacencies.

• Type 3 and type 5 PDUs are sent to a specific NSAP and are therefore routed. The type 3 PDU is a response to a type 1 or type 2 PDU originated at a specific address.

The Cisco router labeled “3640A” in Figure 4-29 is configured with multiple IS-IS processes.

Figure 4-29 IS-IS Multiarea Network Using VLAN Trunking and ISL Encapsulation

Use the show tarp tid-cache EXEC command to examine the TARP TID cache. The following is sample output from this command:

3640A# show tarp tid-cache

TID ('*' : static; & : local) NSAP

& 3640A 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.003640A#

The following example lists the configuration for the Cisco 3640 router. The first IS-IS process listed is area0001. The NET associated with the process area0001 is 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00, which matches the NET listed in the TARP TID cache for the Cisco router labeled “3640A.” (Remember the rule that the NET of the Level 2 IS-IS process would be associated with the TID.)

3640A# show configuration

Using 2849 out of 129016 bytes!version 12.2service timestamps debug uptimeservice timestamps log uptime

9511

6

CLNS packet flow

3640ACentral office

router

2924XL

NE14A

NE15A

NE25A

NE26A

NE14BArea0001

Area0002

Area0003

NE25B

NE26B

VLAN using ISL



no service password-encryption!hostname 3640A!boot system slot1:boot system flash boot system romboot system slot0:logging queue-limit 100!ip subnet-zeroclns routingmpls ldp logging neighbor-changesno ftp-server write-enable!!!!interface Ethernet0/0 ip address 192.168.0.49 255.255.255.0 half-duplex no cdp enable!interface Ethernet0/1 no ip address shutdown half-duplex no cdp enable!interface Ethernet0/2 no ip address shutdown half-duplex no cdp enable!interface Ethernet0/3 ip address 10.19.250.33 255.255.255.248 shutdown half-duplex no cdp enable!interface Serial1/0 no ip address clockrate 9600 no cdp enable!interface Serial1/1 no ip address shutdown no cdp enable!interface Serial1/2 no ip address clockrate 9600 no cdp enable!interface Serial1/3 no ip address clockrate 9600 no cdp enable!interface FastEthernet3/0 no ip address duplex auto



speed auto no cdp enable!interface FastEthernet3/0.1 description ISIS area 0001 encapsulation dot1Q 1 native ip address 192.168.12.24 255.255.255.0 no ip redirects no cdp enable clns router isis area0001 isis priority 127 tarp enable!interface FastEthernet3/0.2 description ISIS area 0002 encapsulation dot1Q 2 ip address 192.168.2.125 255.255.255.192 no ip redirects no cdp enable clns router isis area0002 isis priority 127 tarp enable!interface FastEthernet3/0.3 description ISIS area 0003 encapsulation dot1Q 3 ip address 192.168.2.189 255.255.255.192 no ip redirects no cdp enable clns router isis area0003 isis priority 127 tarp enable!router ospf 795 no log-adjacency-changes network 192.168.0.0 0.0.255.255 area 0!router isis area0001 net 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00!router isis area0002 net 39.840f.8011.9999.0000.1111.0002.0010.7bc7.ae40.00 is-type level-1!router isis area0003 net 39.840f.8011.9999.0000.1111.0003.0010.7bc7.ae40.00 is-type level-1!router rip network 192.168.0.0!no ip http serverno ip classlessip route 0.0.0.0 0.0.0.0 172.31.232.17!!no cdp runclns host NE14A 39.840f.8011.9999.0000.1111.0001.00e0.b064.4324.00clns host NE14B 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00clns host NE25A 39.840f.8011.9999.0000.1111.0002.00e0.b064.434e.00clns host NE25B 39.840f.8011.9999.0000.1111.0002.0030.94e2.6ce0.00clns host NE26A 39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00clns host NE26B 39.840f.8011.9999.0000.1111.0003.0010.7b17.f880.00clns host NE15A 39.840f.8011.9999.0000.1111.0001.0010.7bd8.c7d0.00



clns host 3640A 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00!tftp-server slot1:tarp runtarp tid 3640A!line con 0 password ciscoline aux 0line vty 0 4 exec-timeout 0 0 password cisco loginline vty 5 99 login!end

Enabling TARP

The following example shows the tarp run and tarp tid global configuration commands used to enable TARP on a central office router:

tarp runtarp tid 3640A

TARP must be enabled on an interface in order for TARP packets to be forwarded. TARP is enabled on the Cisco router labeled “3640A,” shown in Figure 4-30 on page 4-61. The configuration for Fast Ethernet interface 3/0.1 is listed in the following example; the tarp enable interface configuration command is the last command listed.

interface FastEthernet3/0.1 description ISIS area 0001 encapsulation dot1Q 1 native ip address 192.168.12.24 255.255.255.0 no ip redirects no cdp enable clns router isis area0001 isis priority 127 tarp enable

Use the show tarp EXEC command to display the global TARP configuration information on a router:

3640A# show tarp

Global TARP information: TID of this station is "3640A" Timer T1 (timer for response to TARP Type 1 PDU) is 15 seconds Timer T2 (timer for response to TARP Type 2 PDU) is 25 seconds Timer T3 (timer for response to ARP request) is 40 seconds Timer T4 (timer that starts when T2 expires) is 15 seconds Loop Detection Buffer entry timeout : 300 seconds Loop Detection Buffer zero sequence timer is 300 seconds TID cache entry timeout : 3600 seconds This station will propagate TARP PDUs This station will originate TARP PDUs TID<->NET cache is enabled Sequence number that next packet originated by this station will have : 1 Update remote cache (URC) bit is 0 Packet lifetime : 100 hops Protocol type used in outgoing packets : "FE" N-Selector used in TARP PDU's : "AF"



Use the following information to interpret the report:

• TID of this station is 3640A. (Remember that the TID is case-sensitive.)

• Timers T1, T2, T3, and T4 are set at the default values defined in GR-253-Core Section 8:

– Timer T1 is the time that the router waits for a response to a TARP type 1 PDU. Timer T1 can be altered with the tarp t1-response-timer seconds global configuration command. The range of seconds is from 0 to 3600 with a default of 15.

– Timer T2 is the time that the router waits for a response to a TARP type 2 PDU. Timer T2 can be altered with the tarp t2-response-timer seconds global configuration command. The range of seconds is from 0 to 3600 with a default of 25.

– Timer T3 is the time that the router waits for a response to an address resolution request, which is a TARP type 5 PDU. Timer T3 can be altered with the tarp arp-request-timer seconds global configuration command. The range of seconds is from 0 to 3600 with a default of 40.

– Timer T4 starts when timer T2 expires. The timer is used for error recovery, and can be altered with the tarp post-t2-response-timer seconds global configuration command. The range of seconds is from 0 to 3600 with a default of 15.

• The Loop Detection Buffer helps prevent TARP type 1, type 2, and type 4 packets from looping throughout the network. The entry timeout value determines the amount of time that mapping data will be stored in the loop detection database.

• The Loop Detection Buffer zero sequence timer starts when a TARP packet with a value of 0 (zero) is received. Additional TARP packets with a sequence value of 0 that are received before the timer expires are discarded. The timer value displayed in the example is set to 5 minutes (300 seconds).

• TID cache entry timeout indicates the amount of time the TID-to-NSAP maps will be cached in the router, which in this example is 3600 seconds (1 hour). The TID cache timer is configurable with the tarp cache-timer seconds global configuration command. The caching of the TID can be turned on or off with the tarp allow-caching global configuration command. TID caching is on by default.

• “This station will propagate TARP PDUs” indicates that the router can forward TARP PDUs.

• “This station will originate TARP PDUs” indicates that the router can originate TARP PDUs.

• “TID<->NET cache is enabled” indicates that the TID-to-NSAP maps will be cached by the router. The cache timer is set to 3600 seconds (1 hour). The cache value can range from 30 to 86400 seconds (24 hours).

• “Sequence number that the next TARP packet originated by this router will have” indicates a value of 1; the value can range from 0 to 65535. The sequence number prevents broadcast storms and is the next outgoing TARP packet. The sequence number can be changed with the tarp sequence-number number global configuration command.

• An update remote cache (URC) bit value of 0 (zero) indicates that remote routers should store the TARP type 3 packet in their cache. A value of 1 would tell the remote hosts not to store the packet in the remote router’s cache. The URC value can be changed using the tarp urc {0 | 1} global configuration command.

• Packet lifetime is the number of hops that the packet can live. Each IS-IS router the packet traverses is counted as one hop. The default hop number is 100, and the range is from 0 to 65535.

• Protocol type “FE” is used to identify the CLNP, as specified in GR-253-CORE section 8. This parameter can be configured using Cisco IOS software. The protocol type can be specified in outgoing TARP PDUs with the tarp protocol hex-digit global configuration command.



• N-selector is the network selector value used in TARP PDUs. In this example, the network selector value are the hexadecimal digits AF, which designates the TARP application as specified in GR-253-CORE section 8. This parameter can be configured using Cisco IOS software. The N-selector value generated with the TARP PDU can be changed with the tarp selector hex-digit global configuration command.

Using TARP with Remote Login Applications

One reason TARP was developed was to assist remote login applications. Central office technicians may not know the NSAP of the device that they want to log in to remotely, but they can determine the name of the equipment or the TID.

Network monitoring applications such as Telcordia’s Network Management Application (NMA) or Provision applications such as Fujitsu’s Flexr can also take advantage of TARP as a dynamic method to map TIDs to NSAPs or NETs. The system administrator would have to type in only the TID for the device that was to be monitored or provisioned, which is much easier than typing the NSAP. The OSS application would then issue a TARP type 1 or type 2 packet to learn the NET.

To issue a TARP type 1 or type 2 request on a Cisco router, use the tarp resolve tid EXEC command. Use Figure 4-30 as an example network for interpreting the reports displayed.

Figure 4-30 Sample Network for Interpreting TARP Reports

Issue a TARP type 1 request for the NET for device NE15A using the tarp resolve tid EXEC command:

3640A# tarp resolve tid NE15A

Type escape sequence to abort.Sending TARP type 1 PDU, timeout 15 seconds ...

NET corresponding to TID NE15A is 39.840f.8011.9999.0000.1111.0001.0010.7bd8.c7d0.00

The request returns a message indicating that a TARP type 1 PDU was sent out. The software will wait for 15 seconds for a reply (the default time value for the T1 timer). If no response is received after 15 seconds, a type 2 PDU would be sent out to all of the IS-IS and ES-IS nodes that support TARP.

In this example, the network element with the TID value of NE15A did respond with a TARP type 3 PDU, and the software picked up and displayed the NET on the screen. The NET is 39.840f.8011.9999.0000.1111.0001.0010.7bd8.c7d0.00. The TID-to-NET map will be stored in the router’s TARP data cache.

9562

3

NE14BArea0001

Area0002

Area0003

NE14A

NE15A

NE25BNE25A

NE26BNE26A

CLNS packet flow


VLAN using802.1Q



To display the contents of the TARP data cache, use the show tarp tid-cache EXEC command. The TID for router 3640A and device NE15A is listed in the TARP data cache.



& 3640A 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00 NE15A 39.840f.8011.9999.0000.1111.0001.0010.7bd8.c7d0.00

To clear the TARP cache, use the clear tarp tid-cache command:

3640A# clear tarp tid-table

Check the TARP TID cache after clearing it to verify that only the Cisco router labeled “3640A” is listed:



& 3640A 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00

It is possible to watch the propagation of the TARP PDUs, for example, to watch router 3640A generate a TARP type 1 PDU for every adjacency. Use the show clns neighbors EXEC command to show all of the adjacencies:





Four adjacencies are listed and all are of type Level 1. Figure 4-30 has been redrawn in Figure 4-31 with an arrow depicting each of the TARP type 1 PDUs being sent out. One important point to note is that TARP is not a broadcast protocol. A type 1 packet is generated and sent out to each of the IS-IS adjacencies. Sending separate PDUs to each adjacency will generate more network traffic than a single broadcast packet.

Figure 4-31 Transmission of TARP Type 1 PDUs

9562

4

NE14BArea0001

Area0002

Area0003

NE14A

NE15A

NE25BNE25A

NE26BNE26A


TARP type 1PDUs



TARP debug commands can also help track the packets that are being sent. Before the debug command is issued, a list of the system identifiers will help analyze the command output:

3640A system id 0010.7bc7.ae40NE14A system is 00e0.b064.4324NE14B system id 0050.7363.7b40NE25A system id 00e0.b064.434eNE25B system is 0030.94e2.6ce0NE26A system id 00d0.5872.9720NE26B system id 0010.7b17.f880NE15A system id 0010.7bd8.c7d0

To verify the TARP type 1 PDUs that are being sent out, issue the debug tarp packet command. In addition, issue the debug tarp events command to track additional TARP PDU activity.

3640A# debug tarp packetsTARP packet info debugging is on3640A# debug tarp eventsTARP events debugging is on

Next issue the tarp resolve tid EXEC command for device NE15A. In the following example, the router will wait 15 seconds for a response before issuing a TARP type 2 PDU. Device NE15A responds within 15 seconds with its NET, which is the NSAP address and selector value of 00.

3640A# tarp resolve tid NE15A


NET corresponding to TID NE15A is 39.840f.8011.9999.0000.1111.0001.0010.7bd8.c7d0.00

The debug tarp packets command output shows a TARP type 1 PDU being sent to each of the four IS-IS adjacencies over the Fast Ethernet interface connection; four type 1 PDU packet will be sent out. The first type 1 packet is sent to device NE15A (0010.7bd8.c7d0) from the Cisco router labeled “3640A” (0010.7bc7.ae40):

3640A#00:16:50: TARP-PA: Propagated TARP packet, type 1, out on FastEthernet3/0.100:16:50: Lft = 100, Seq = 7, Prot type = 0xFE, URC = TRUE00:16:50: Dtid len = 5, Stid len = 5, Prot addr len = 2000:16:50: Destination NSAP : 39.840f.8011.9999.0000.1111.0001.0010.7bd8.c7d0.0000:16:50: Originator's NSAP : 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.0000:16:50: Target TID : NE15A00:16:50: Originator's TID : 3640A

The debug tarp packets output continues by showing the second type 1 packet being sent to device NE14A (00e0.b064.4324) from the Cisco router labeled “3640A” (0010.7bc7.ae40):

00:16:50: TARP-PA: Propagated TARP packet, type 1, out on FastEthernet3/0.100:16:50: Lft = 100, Seq = 7, Prot type = 0xFE, URC = TRUE00:16:50: Dtid len = 5, Stid len = 5, Prot addr len = 2000:16:50: Destination NSAP : 39.840f.8011.9999.0000.1111.0001.00e0.b064.4324.0000:16:50: Originator's NSAP : 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.0000:16:50: Target TID : NE15A00:16:50: Originator's TID : 3640A

The debug tarp packets output continues by showing the third type 1 packet being sent to device NE25A (00e0.b064.434e) from the Cisco router labeled “3640A” (0010.7bc7.ae40):

00:16:50: TARP-PA: Propagated TARP packet, type 1, out on FastEthernet3/0.200:16:50: Lft = 100, Seq = 7, Prot type = 0xFE, URC = TRUE



00:16:50: Dtid len = 5, Stid len = 5, Prot addr len = 2000:16:50: Destination NSAP : 39.840f.8011.9999.0000.1111.0002.00e0.b064.434e.0000:16:50: Originator's NSAP : 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.0000:16:50: Target TID : NE15A00:16:50: Originator's TID : 3640A

The debug tarp packets output shows a fourth type 1 packet being sent to device NE26A (00d0.5872.9720) from the Cisco router labeled “3640A” (0010.7bc7.ae40):

00:16:50: TARP-PA: Propagated TARP packet, type 1, out on FastEthernet3/0.300:16:50: Lft = 100, Seq = 7, Prot type = 0xFE, URC = TRUE00:16:50: Dtid len = 5, Stid len = 5, Prot addr len = 2000:16:50: Destination NSAP : 39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.0000:16:50: Originator's NSAP : 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.0000:16:50: Target TID : NE15A00:16:50: Originator's TID : 3640A

Next, the debug tarp packets output shows a type 3 packet being received on Fast Ethernet interface 3/0.1 by router 3640A (0010.7bc7.ae40) from device NE15A (0010.7bd8.c7d0):

00:16:50: TARP-PA: Received TARP type 3 PDU on interface FastEthernet3/0.100:16:50: Lft = 100, Seq = 3, Prot type = 0xFE, URC = TRUE00:16:50: Ttid len = 0, Stid len = 5, Prot addr len = 2000:16:50: Packet sent/propagated by 39.840f.8011.9999.0000.1111.0001.0010.7bd8.c7d0.af00:16:50: Originator's NSAP : 39.840f.8011.9999.0000.1111.0001.0010.7bd8.c7d0.0000:16:50: Originator's TID : NE15A

Finally, the debug tarp events output shows a TARP cache entry being created. A value is set for the loop detection buffer (LDB). The loop detection buffer is a method of deterring packets from propagating TARP packets that the IS-IS router has already seen.

00:16:50: TARP-PA: Created new DYNAMIC cache entry for NE15A00:16:50: TARP-EV: Packet from 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00 discarded - sequence 00:16:50: number (7) <= that in LDB cache entry (7)00:16:50: TARP-EV: Packet from 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00 discarded - sequence 00:16:50: number (7) <= that in LDB cache entry (7)

Notice that the TARP application generated a separate unicast packet for every adjacency instead of a single broadcast packet.

Controlling TARP Propagation Using Split Horizon

The original implementations of TARP had type 1, type 2, and type 4 packets forwarded to IS-IS and ES-IS adjacencies. Service providers were experiencing problems with TARP PDUs looping through the network and causing congestion. One of the first things that Cisco did to control the propagation of TARP packets was to implement split horizon, so that a TARP packet would not be forwarded on the same interface that the packet was received on. The problem was worse on Ethernet interfaces: A router or other device on an Ethernet interface would receive a type 2 PDU. A separate type 2 PDU would be sent to all of the router adjacencies, and these devices should have already received the packet.

This section steps through an example of the network elements without split horizon. Figure 4-32 shows a TARP type 1 PDU being generated from router 3640A. Router 3640A will generate a type 1 PDU to all of its Level 1 adjacencies. The arrows in Figure 4-32 depict the Type 1 PDUs that are being sent out to all of router 3640A’s Level 1 adjacencies.



Figure 4-32 TARP Propagation Control Using Split Horizon

Figure 4-33 shows how the early implementations of TARP would respond to the type 1 PDUs sent out in Figure 4-32. Type 1 PDUs would be forwarded out the interface that the type 1 PDU had arrived on. Device NE 14A has an adjacency with devices NE14B, NE15A, and router 3640A, so device NE14A would send out three type 1 PDUs, which are represented by the three arrows coming out of device NE14A. Device NE15A is the object of the type 1 PDU, and device NE15A responds with a TARP type 3 PDU directly to router 3640A. Device NE25A has two Level 1 IS-IS adjacencies, which are router 3640A and device NE25B, and two type 1 packets are forwarded out, as shown in Figure 4-33 by the two parallel arrows. Similarly, device NE26A has two Level-1 IS-IS adjacencies, which are router 3640A router and device NE26B, and Figure 4-33 shows two TARP type 1 packets being forwarded out.

Figure 4-33 Split Horizon Not Implemented on a Network Element

The point is that TARP packets can multiply quickly on the network. Split horizon is only one method that Cisco implemented to control the number of TARP packets.

At this point, router 3640A has received a type 3 response to the type 1 query; however, numerous packets have been launched. Without split horizon implemented, router 3640A would respond to each of the incoming type 1 PDUs and send back a type 1 packet to each of the adjacencies on the Ethernet interface. Eventually, the packets would expire due to the time-to-live field, but in the meantime much bandwidth has been expended.

9562

4

NE14BArea0001

Area0002

Area0003

NE14A

NE15A

NE25BNE25A

NE26BNE26A


TARP type 1PDUs

9562

7

NE14BArea0001

Area0002

Area0003

NE14A

NE15A

NE25BNE25A

NE26BNE26A


TARP type 1PDUs

TARP type 3PDUs



Figure 4-34 shows what happens when split horizon is implemented on the network elements and the router. Device NE15A responds with a type 3 PDU. Device NE14A sends a type 1 PDU out on the DCC, but not on the Ethernet interface. Remember that split horizon does not allow the device to send a type 1 packet on the same interface that the packet arrived on. With split horizon configured, devices NE15A and NE26A send a type 1 PDU out on the DCC, but not on the Ethernet interface.

Figure 4-34 Split Horizon Implemented on Network Elements and Router 3640A

The problem of looping TARP PDUs has also been addressed by the SONET Interoperability Forum, which is discussed in the next section.

Additional Methods of Controlling the Propagation of TARP Packets

In the original TARP implementation, traffic multiplied exponentially. Cisco developed split horizon to help customers reduce this traffic, which can be implemented by placing all the network elements in the same OSI area. In Figure 4-35, the area is designated 0001.

9562

5

NE14BArea0001

Area0002

Area0003

NE14A

NE15A

NE25BNE25A

NE26BNE26A


TARP type 1PDUs

TARP type 3PDUs



Figure 4-35 Split Horizon and All Network Elements in the Same Area

The SONET Interoperability forum later developed a loop detection procedure using the loop detection buffer on the IS-IS router. Upon receiving a type 1, type 2, or type 4 PDU, the IS-IS router checks the loop detection buffer for a match. If there is no match, an entry is created with the system identifier that originated the packet and its sequence number.

Use the show tarp ldp EXEC command to display the TARP loop detection database on a Cisco router. The output lists the TARP sequence number and the time until the entry is aged out.

In the following example, any new TARP PDUs arriving from system identifier 0010.7BC7.AE40 with a sequence number of 9 or less will be discarded for the next 287 seconds. Any new TARP PDUs arriving from system identifier 0010.7BD8.C7D0 with a sequence number of 5 or less will be discarded for the next 287 seconds.

3640A# show tarp ldb

System ID Sequence Number Expiration (sec) Zero-sequence timer 0010.7BC7.AE40 9 287 0 0010.7BD8.C7D0 5 287 0

In the following example, the output from the debug tarp events command indicates that the TARP entries in the LDB are being aged:

3640A# debug tarp events

01:56:18: TARP-EV: Aging LDB entry for 0010.7BC7.AE40 01:56:18: TARP-EV: Aging LDB entry for 0010.7BD8.C7D0

A TARP type 4 packet is used to notify the network of changes. The type 4 packet is used to notify IS-IS and ES devices of TID changes or address changes. The TARP type 4 packet is used to reset the TARP sequence number to 0 (zero).

9562

6

NE14BArea0001NE14A

NE15A

NE25A

NE26A


TARP type 1PDUs

TARP type 3PDUs

NE14C

NE15BArea0001

NE15C

NE25BArea0001

NE25C

NE26BArea0001

NE26C



TARP PDU Packet Propagation Control Configuration Commands

Cisco has developed software commands that help control the propagation of type 1, type 2, and type 4 TARP PDU packets throughout the network. The tarp route-static global configuration command provides the ability to statically map the propagation of TARP packets across the network, and is issued as follows:

tarp route-static nsap [all | message-type type-number [type-number] [type-number]]

This command creates a manual adjacency to forward the TARP packet. The command can also be used to forward the TARP packets across IS-IS routers that do not support the TARP application. Use this command to forward TARP packets across the core of the network, yet control the propagation of the packets. The tarp route-static command can be implemented by a TARP packet type and is valid for the packet types 1, 2, and 4. TARP type 3 and 5 packets are unicast and sent to only one address; there is no need to apply the tarp route-static command to type 3 and 5 packets.

To control the propagation of TARP packets, use the no tarp propagate interface configuration command:

no tarp propagate [all | message-type type-number [type-number] [type-number]]

This command turns off the propagation by TARP packet type. The no tarp propagate command can be implemented by individual TARP packet type, and types 1, 2, and 4 are valid for the command.

Note If both the tarp route-static and the no tarp propagate commands are issued for type 4 PDUs on the router, the tarp route-static global configuration command takes precedence and the type 4 packets will be unicast to the specified NSAP.

Maintaining and Troubleshooting the IS-IS NetworkThe Cisco IOS software provides commands to help determine the topology and connectivity of the network, and that are useful for verifying and troubleshooting the IS-IS network. The following EXEC commands are described in this section:

• clns host

• debug clns esis packets

• debug isis adjacency

• debug isis adj-packets

• debug tarp events

• debug tarp packets

• ping

• ping clns

• show clns interface

• show clns isis neighbor

• show clns neighbor

• show isis route

• show isis topology



• tarp query

• tarp resolve

• traceroute

• which-route

Caution Take care in issuing the Cisco IOS debug commands, because they can consume CPU cycles and interfere with the normal operation of the network.

Mapping NSAPs to CLNS Host Names

Managing and troubleshooting the networks using NSAP addresses can be cumbersome, because the system identifier in the NSAP is typically in hexadecimal format. This format makes monitoring the IS-IS adjacencies, the ES-IS adjacencies, the IS-IS database, and other information a difficult task. Issuing debugging commands such as the ping clns EXEC command and TARP commands can also be cumbersome. One solution is to statically map NSAPs to host names. In the Cisco IOS software, this mapping can be done using the clns host command. The following example shows how to map CLNS hosts to IS-IS devices:

clns host 3640A 39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00clns host NE14A 39.840f.8011.9999.0000.1111.0001.00e0.b064.4325.00clns host NE14B 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00clns host NE25A 39.840f.8011.9999.0000.1111.0002.00e0.b064.434e.00clns host NE25B 39.840f.8011.9999.0000.1111.0002.0030.94e2.6ce0.00clns host NE26A 39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00clns host NE26B 39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00clns host NE15A 39.840f.8011.9999.0000.1111.0001.0010.7bd8.c7d0.00

Using TLV 137 to Correlate Router and Host Names

The maintenance of the CLNS host statements in every IS-IS router and CLNS host in the network can be cumbersome in a large-sized network. A dynamic solution has been developed as part of the IS-IS protocol. A new type, length, value (TLV) has been defined in Informational RFC 2763, Dynamic Hostname Exchange Mechanism for IS-IS. IS-IS, originally designed for OSI routing, uses TLV parameters to carry information in link-state packets. The new TLV type 137, dynamic host name, and its value field contain the name of the router originating the link-state packet. The feature was introduced in Cisco IOS Release 12.0(4)T, and the show clns neighbors EXEC command uses TLV 137 or the clns host command to correlate router and host name.

Following is sample output from the show clns neighbors command showing the system identifier with the host name:




Area area0003:System Id Interface SNPA State Holdtime Type ProtocolNE26B Fa3/0.3 00d0.5872.9720 Up 26 L1 IS-IS



Note The IS-IS router must support TLV type 137 for the names to be propagated. This technique will become more valuable as more SONET and SDH vendors support TLV type 137.

Displaying IS-IS Network Topology

This section describes how to use Cisco IOS software commands to determine network topology. Use Figure 4-36 as a reference for the command examples.

Figure 4-36 Sample Network for Determining IS-IS Network Topology

Use the show isis topology EXEC command to list the topology of the IS-IS network. The following example lists the topology as shown in Figure 4-36:


Area area0001:IS-IS IP paths to level-1 routersSystem Id Metric Next-Hop Interface SNPA3640A --NE15A 10 NE15A Fa3/0.1 0010.7bd8.c7d0 NE14B 20 NE14A Fa3/0.1 00e0.b064.4325 NE14A 10 NE14A Fa3/0.1 00e0.b064.4325

IS-IS IP paths to level-2 routersSystem Id Metric Next-Hop Interface SNPA3640A --

Area area0002:IS-IS IP paths to level-1 routersSystem Id Metric Next-Hop Interface SNPA3640A --NE25B 20 NE25A Fa3/0.2 00e0.b064.434e NE25A 10 NE25A Fa3/0.2 00e0.b064.434e

Area area0003:IS-IS IP paths to level-1 routersSystem Id Metric Next-Hop Interface SNPANE26B 20 NE26A Fa3/0.3 00d0.5872.9720 3640A --NE26A 10 NE26A Fa3/0.3 00d0.5872.9720

9562

8

NE14BArea0001

Area0002

Area0003

NE14A

NE15A

NE25BNE25A

NE26BNE26A


VLAN using802.1Q

CLNS packet flow



In Figure 4-36, the IS-IS Level 1 area0001 contains the IS-IS Level 1/Level 2 Cisco 3640 router and the IS-IS Level 1 devices NE15A, NE14B, and NE14A. Device NE15A is directly connected using Fast Ethernet interface 3/0.1 to router 3640A, and has a routing metric of 10. The SNPA for device NE15A is 0010.7bd8.c7d0. On an Ethernet interface, the SNPA is the MAC address. Device NE14B is one hop away from router 3640A; therefore, the routing metric is 20 and the next hop IS-IS router is device NE14A. Device NE14A is connected using Fast Ethernet interface 3/0.1. The SNPA is the MAC address (00e0.b064.4325) of device NE14A, the next hop device. Device NE14A is directly connected to Fast Ethernet 3/0.1 and has a routing metric of 10. The SNPA or MAC address of device NE14A is 00e0.b064.4325.

In IS-IS area 0002, there are three system identifiers—router 3640A and devices NE25B and NE25A—as seen in Figure 4-36. Device NE25B can be reached one hop away through device NE25A on Fast Ethernet interface 3/0.2. The routing metric is 20 because device NE25B is one hop away. The SNPA for the next hop device, NE25A, is 00e0.b064.434e. Device NE25A is directly connected with a routing metric of 10.

In IS-IS area 0003, there are three system identifiers—router 3640A and devices NE26B and NE26A, as seen in Figure 4-36. Device NE26B can be reached one hop away through device NE26A on Fast Ethernet interface 3/0.3. The routing metric is 20. The SNPA for the next hop device, NE26A, is 00d0.5872.9720. Device NE26A is directly connected with a routing metric of 10.

Similar network topology information can be gathered from the show isis route EXEC command. The information is similar to that displayed by the show isis topology command, except for an additional field that indicates the state of the adjacency to the next hop IS-IS router. The following example output shows the information displayed by the show isis route command:

3640A# show isis route

Area area0001:IS-IS Level-1 Routing Table - version 5System Id Next-Hop Interface SNPA Metric State3640A --NE15A NE15A Fa3/0.1 0010.7bd8.c7d0 10 Up NE14B NE14A Fa3/0.1 00e0.b064.4325 20 Up NE14A NE14A Fa3/0.1 00e0.b064.4325 10 Up

Area area0002:IS-IS Level-1 Routing Table - version 5System Id Next-Hop Interface SNPA Metric State3640A --NE25B NE25A Fa3/0.2 00e0.b064.434e 20 Up NE25A NE25A Fa3/0.2 00e0.b064.434e 10 Up

Area area0003:IS-IS Level-1 Routing Table - version 4System Id Next-Hop Interface SNPA Metric State3640A --NE26B NE26A Fa3/0.3 00d0.5872.9720 20 Up NE26A NE26A Fa3/0.3 00d0.5872.9720 10 Up

The show isis route EXEC command can be used to specify the next hop to a specific IS-IS router. The following example shows the route to device NE14B:

3640A# show isis route NE14B

Area area0001:System Id Next-Hop Interface SNPA Metric StateNE14B NE14A Fa3/0.1 00e0.b064.4325 20 Up

Area area0002:No IS-IS Level-1 route to NE14B found



Area area0003:No IS-IS Level-1 route to NE14B found

The which-route EXEC command displays the next hop in the route for the packet and specific information about the hop, and is better suited to display the route to device NE14B. The command displays the routing table where the CLNS address is found in the router. The command can also be useful if you are running multiple routing processes on the router.

3640A# which-route NE14B

Route look-up for destination 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00, NE14B Found route in IS-IS level-1 routing table

Adjacency entry used:System Id Interface SNPA State Holdtime Type ProtocolNE14A Fa3/0.1 00e0.b064.4325 Up 23 L1 IS-IS Area Address(es): 39.840f.8011.9999.0000.1111.0001 Uptime: 01:11:57

In this display:

• The NET for device NE14B is 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00, and is found in the Level 1 routing table for the Cisco router labeled “3640A” in Figure 4-36 on page 4-70.

• The system identifier of the adjacent IS-IS router is device NE14A. (The clns host command was used to translate the system identifier to the host identifier.)

• Device NE14A is accessed using Fast Ethernet interface 3/0.1.

• The MAC address or SNPA for device NE14A is 00e0.b064.4325.

• The state of the Level 1 IS-IS adjacency is up and, therefore, device NE14A is reachable.

• The hold time represents the time until the Level 1 adjacency times out, and in this example is 23 seconds. If an IS-IS hello message is not received within 23 seconds, the IS-IS adjacency will be torn down.

• The IS-IS adjacency type is Level 1.

• Protocol: The adjacency was learned from the IS-IS protocol.

• The IS-IS area address is 39.840f.8011.9999.0000.1111.0001 and the area has been available for 1 hour, 11 minutes, and 57 seconds. The uptime report is useful while troubleshooting the length of time that the area has been available.

Verifying IS-IS Adjacency Formation

This section describes how to determine whether two IS-IS router devices are forming IS-IS adjacencies. If the devices are not forming adjacencies, it will be necessary to determine why not. Cisco has found from working with service providers that typically the SONET/SDH nodes do not have a robust debugging capability. Figure 4-37 shows a typical operational IS-IS network.



Figure 4-37 Operational IS-IS Network

The portion of the network that this section focuses on debugging is shown in Figure 4-38, and examines the access router in the central office that supports the Level-1-2 adjacency to the network elements.

Figure 4-38 Access Router in the Central Office that Supports the Level 1-2 Adjacency to the

Network Elements

The Cisco IOS software provides commands that determine the status of the IS-IS adjacency between the Cisco router labeled “3640A” in Figure 4-38 and the network elements. All of the network elements in the example are set up as Level 1 IS-IS routers. Devices NE14A and NE15A are in OSI area 0001, and there should be two Level 1 adjacencies established on Fast Ethernet interface 3/.01.

The show clns interface EXEC command displays the number adjacencies on the interface (report displayed in bold text for purpose of example).

3640A# show clns interface FastEthernet3/0.1

FastEthernet3/0.1 is up, line protocol is up Checksums enabled, MTU 1497, Encapsulation SAP ERPDUs enabled, min. interval 10 msec. RDPDUs enabled, min. interval 100 msec., Addr Mask enabled, last sent 00:00:40 Congestion Experienced bit set at 4 packets CLNS fast switching enabled CLNS SSE switching disabled

9562

9

OSS

IP/OSI

CLNS packet flow


VLAN using802.1Q

NE14BArea0001

Area0002

Area0003

NE14A

NE15A

NE25BNE25A

NE26BNE26A

9563

0

NE14BArea0001

Area0002

Area0003

NE14A

NE15A

NE25BNE25A

NE26BNE26A

CLNS packet flow

Fast Ethernet3/0.1

Fast Ethernet3/0.3

Fast Ethernet3/0.2


VLAN using802.1Q



DEC compatibility mode OFF for this interface Next ESH/ISH in 38 seconds Routing Protocol: IS-IS (area0001) Circuit Type: level-1-2 Interface number 0x0, local circuit ID 0x1 Level-1 Metric: 10, Priority: 127, Circuit ID: 3640A.01 Level-1 IPv6 Metric: 10 Number of active level-1 adjacencies: 2 Level-2 Metric: 10, Priority: 127, Circuit ID: 3640A.01 Level-2 IPv6 Metric: 10 Number of active level-2 adjacencies: 0 Next IS-IS LAN Level-1 Hello in 254 milliseconds Next IS-IS LAN Level-2 Hello in 2 seconds

The output of the command shows that there are two Level 1 adjacencies. There are no Level 2 adjacencies, which corresponds to the configuration seen in Figure 4-38 on page 4-73.

The ES-IS protocol works with the IS-IS protocol. When a router is configured for IS-IS, ES-IS is automatically enabled. End systems and routers send End System Hello (ESH) and Intermediate System Hello (ISH) messages to determine the network addresses of adjacent neighbors. On a LAN, the ESHs are sent to a broadcast address of 09-00-2b-00-00-05 to reach the routers. The ISHs are sent to a broadcast address of 09-00-2b-00-00-04 to reach the end systems. The IS-IS adjacencies are formed IS-IS Hello (IIH) messages and there are three types, as follows:

• IIH message for point-to-point links

• Level 1 LAN IIH message

• Level 2 LAN IIH message

Examine the adjacencies coming up on a working network using Figure 4-38 on page 4-73 as an example. This task requires the MAC address or SNPA for debugging the IIH messages. One method of quickly determining the system identifier is to use the show clns neighbors EXEC command.

In the following example, when the show clns neighbors EXEC command is issued, the host name is displayed instead of the actual system identifier. The host name will be displayed when static host name assignments have been made in the Cisco router, or when the SONET/SDH nodes support dynamic host assignment. Static and dynamic host assignment are explained in the “Mapping NSAPs to CLNS Host Names” section on page 4-69.




Area area0003:System Id Interface SNPA State Holdtime Type ProtocolNE26B Fa3/0.3 00d0.5872.9720 Up 29 L1 IS-IS

Examining IS-IS Adjacency Formation

The next step is to look at how IS-IS adjacencies are formed. Use the debug isis adj-packets EXEC command to watch the IIHs being sent. In the following example, the Fast Ethernet interface has been turned down and then brought up after debugging was turned on to capture the entire process. (Key reports are in bold text for purpose of example.)



3640A# debug isis adj-packets

The Fast Ethernet interface comes up:

00:05:44: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet3/0, changed state to up

Router 3640A in Figure 4-38 on page 4-73 sends Level 1 and Level 2 IIHs:

00:05:44: ISIS-Adj (area0001): Sending L1 LAN IIH on FastEthernet3/0.1, length 149700:05:44: ISIS-Adj (area0001): Sending L2 LAN IIH on FastEthernet3/0.1, length 149700:05:44: ISIS-Adj (area0002): Sending L1 LAN IIH on FastEthernet3/0.2, length 149700:05:44: ISIS-Adj (area0003): Sending L1 LAN IIH on FastEthernet3/0.3, length 149700:05:52: ISIS-Adj (area0003): Sending L1 LAN IIH on FastEthernet3/0.3, length 149700:05:53: ISIS-Adj (area0001): Sending L1 LAN IIH on FastEthernet3/0.1, length 149700:05:53: ISIS-Adj (area0002): Sending L1 LAN IIH on FastEthernet3/0.2, length 149700:05:53: ISIS-Adj (area0001): Sending L2 LAN IIH on FastEthernet3/0.1, length 149700:06:00: ISIS-Adj (area0003): Sending L1 LAN IIH on FastEthernet3/0.3, length 149700:06:02: ISIS-Adj (area0001): Sending L1 LAN IIH on FastEthernet3/0.1, length 149700:06:02: ISIS-Adj (area0002): Sending L1 LAN IIH on FastEthernet3/0.2, length 149700:06:03: ISIS-Adj (area0001): Sending L2 LAN IIH on FastEthernet3/0.1, length 149700:06:08: ISIS-Adj (area0003): Sending L1 LAN IIH on FastEthernet3/0.3, length 149700:06:10: ISIS-Adj (area0001): Sending L1 LAN IIH on FastEthernet3/0.1, length 1497

Router 3640A receives a Level 1 IIH from MAC address 0010.7bd8.c7d0, which is device NE15A. The Level 1 adjacency comes up between router 3640A and device NE15A.

00:06:10: ISIS-Adj (area0001): Rec L1 IIH from 0010.7bd8.c7d0 (FastEthernet3/0.1), cir type L1, cir id 0010.7BD8.C7D0.01, length 14700:06:10: ISIS-Adj (area0001): New adjacency, level 1 for 0010.7bd8.c7d0

Router 3640A receives a Level 1 IIH from MAC address 00e0.b064.4325, which is device NE14A. The Level 1 adjacency comes up between router 3640A and device NE14A.

00:06:10: ISIS-Adj (area0001): Rec L1 IIH from 00e0.b064.4325 (FastEthernet3/0.1), cir type L1, cir id 00E0.B064.4324.02, length 14700:06:10: ISIS-Adj (area0001): New adjacency, level 1 for 00e0.b064.4325...00:06:11: ISIS-Adj (area0001): Sending L1 LAN IIH on FastEthernet3/0.1, length 1497

Router 3640A receives a second IIH from device NE15A. The Cisco 3640A router’s Level 1 adjacency count goes to 1 and the adjacency state is up.

00:06:11: ISIS-Adj (area0001): Rec L1 IIH from 0010.7bd8.c7d0 (FastEthernet3/0.1), cir type L1, cir id 0010.7BC7.AE40.01, length 14700:06:11: ISIS-Adj (area0001): L1 adj count 100:06:11: ISIS-Adj (area0001): Adjacency state goes to Up

Router 3640A and device NE15A are going through the designated router selection. The system identifier of the designated router is 0001.0010.7bc7.AE40, which is router 3640A.

00:06:11: ISIS-Adj (area0001): Run level-1 DR election for FastEthernet3/0.100:06:11: ISIS-Adj (area0001): New level-1 DR 0010.7BC7.AE40 on FastEthernet3/0.100:06:11: ISIS-Adj (area0001): Didn't purge DR LSP--not fully elected

Router 3640A receives a second Level 1 IIH from device NE14A. The Level 1 adjacency count goes to 2. The adjacency state between router 3640A and device NE14A goes to up.

00:06:11: ISIS-Adj (area0001): Rec L1 IIH from 00e0.b064.4325 (FastEthernet3/0.1), cir type L1, cir id 0010.7BC7.AE40.01, length 14700:06:11: ISIS-Adj (area0001): L1 adj count 200:06:11: ISIS-Adj (area0001): Adjacency state goes to Up



The designated router election process runs again. Router 3640A remains the designated router.

00:06:11: ISIS-Adj (area0001): Run level-1 DR election for FastEthernet3/0.100:06:11: ISIS-Adj (area0001): No change (it's us)

The normal sending and receiving of IIHs in area 0001 is shown in the following example:

00:06:12: ISIS-Adj (area0001): Sending L1 LAN IIH on FastEthernet3/0.1, length 149700:06:12: ISIS-Adj (area0001): Rec L1 IIH from 0010.7bd8.c7d0 (FastEthernet3/0.1), cir type L1, cir id 0010.7BC7.AE40.01, length 14700:06:12: ISIS-Adj (area0002): Sending L1 LAN IIH on FastEthernet3/0.2, length 149700:06:12: ISIS-Adj (area0001): Sending L2 LAN IIH on FastEthernet3/0.1, length 149700:06:14: ISIS-Adj (area0001): Sending L1 LAN IIH on FastEthernet3/0.1, length 1497

The same procedure for establishing adjacency in area 0002 and area 0003 takes place. The start of the process of sending and receiving IIHs for both areas is shown in the following example:

00:06:16: ISIS-Adj (area0003): Rec L1 IIH from 00d0.5872.9720 (FastEthernet3/0.3), cir type L1, cir id 00D0.5872.9720.01, length 14700:06:16: ISIS-Adj (area0003): New adjacency, level 1 for 00d0.5872.972000:06:16: ISIS-Adj (area0003): Sending L1 LAN IIH on FastEthernet3/0.3, length 149700:06:16: ISIS-Adj (area0002): Rec L1 IIH from 00e0.b064.434e (FastEthernet3/0.2), cir type L1, cir id 00E0.B064.434E.01, length 14700:06:16: ISIS-Adj (area0002): New adjacency, level 1 for 00e0.b064.434e

Sample Adjacency Debugging Scenario

In Figure 4-39, Nodes 1 through 4 are TN-16s and are SDH network elements that are connected over a fiber-optic link. The GNEs and Cisco routers are located in the Router 1 and Router 2 central offices. The problem is that NE 1 cannot establish a Level 1 adjacency with the Cisco router. The result is that the service provider will have connectivity problems reaching NE 1 from Element Manager System EM-1 Primary. The network elements are configured as Level 1 IS-IS routers. The Cisco routers are configured as Level-1-2 IS-IS routers.

Figure 4-39 Sample Network for Troubleshooting IS-IS Adjacency Problems

The first problem encountered is that the IS-IS adjacency will not come up between Router 1 and NE 1. One way to solve this problem is to determine if the Cisco router interface is up. Use the show clns interface EXEC command to do so (key reports shown in bold text for purpose of example):

Router1# show clns interface Ethernet0

Ethernet0 is up, line protocol is up Checksums enabled, MTU 1497, Encapsulation SAP ERPDUs enabled, min. interval 10 msec. RDPDUs enabled, min. interval 100 msec., Addr Mask enabled

9563

1

NE 1 NE 2 NE 3 NE 4

Ethernet(Area 1, L1)



+GRE Tunnel forArea 1 Ethernet

(Area 11, L1)

Router 1 Router 2

EM-1 Primary EM-2 Secondary

E1 link (L1/L2)



Congestion Experienced bit set at 4 packets CLNS fast switching enabled CLNS SSE switching disabled DEC compatibility mode OFF for this interface Next ESH/ISH in 47 seconds Routing Protocol: IS-IS Circuit Type: level-1-2 Interface number 0x0, local circuit ID 0x1 Level-1 Metric: 10, Priority: 64, Circuit ID: 0000.0000.60B1.01 Number of active level-1 adjacencies: 0 Level-2 Metric: 10, Priority: 64, Circuit ID: 0000.0000.60B1.01 Number of active level-2 adjacencies: 0 Next IS-IS LAN Level-1 Hello in 2 seconds Next IS-IS LAN Level-2 Hello in 1 seconds

The report indicates that the interface is up and the line protocol is up and that the next ESH/ISH will be sent in 47 seconds. The IS-IS routing protocol is turned on and the circuit type is Level-1-2. The number of Level 1 adjacencies is 0 (zero) and the number of Level 2 adjacencies is 0 in the following output. On the Ethernet interface, according to Figure 4-39 on page 4-76, there should be an adjacency with Node 1. The adjacency type should be Level 1 because Node 1 can be configured as only Level 1. The interface is advertising Level 1 and Level 2 IS-IS hello messages.

The next step would be to examine the IS-IS adjacency formation using the debug isis adjacency command. In the following example, Router 1 is sending Level 1 and Level 2 IIHs. The debug command output indicates that the Cisco router is sending out the Level 1 IIH packets and the Level 2 IIH packets on Ethernet interface 0. Router 1 is not receiving the IIHs from NE 1 on Ethernet interface 0.

Router1# debug isis adjacency

IS-IS Adjacency related packets debugging is onRouter1#ISIS-Adj: Sending L2 IIH on Ethernet0ISIS-Adj: Sending L1 IIH on Ethernet0ISIS-Adj: Sending L2 IIH on Ethernet0ISIS-Adj: Sending L1 IIH on Ethernet0

It is also recommended that the Ethernet interface be verified as operational. In this example, the problem was with the software on the SDH network element. The SDH node had to be rebooted for the IS-IS to come up and send the IIH.

Take another look at the problems described previously for Figure 4-39 on page 4-76; that is, the IS-IS adjacency will not come up between Router 1 and NE 1. A report from the show clns interface EXEC command indicates that the interface is up, but no Level 1 adjacency is formed because the value is 0 (report shown in bold text for purpose of example):

Router1# show clns interface Ethernet 0

Ethernet0 is up, line protocol is up Checksums enabled, MTU 1497, Encapsulation SAP ERPDUs enabled, min. interval 10 msec. RDPDUs enabled, min. interval 100 msec., Addr Mask enabled Congestion Experienced bit set at 4 packets CLNS fast switching enabled CLNS SSE switching disabled DEC compatibility mode OFF for this interface Next ESH/ISH in 32 seconds Routing Protocol: IS-IS Circuit Type: level-1-2 Interface number 0x0, local circuit ID 0x1 Level-1 Metric: 10, Priority: 64, Circuit ID: 0000.0000.60B1.01 Number of active level-1 adjacencies: 0 Level-2 Metric: 10, Priority: 64, Circuit ID: 0000.0000.60B1.01



Number of active level-2 adjacencies: 0 Next IS-IS LAN Level-1 Hello in 2 seconds Next IS-IS LAN Level-2 Hello in 1 seconds

Next, enter the debug isis adjacency command on Router 1. In the following example, Router 1 is sending Level 1 and Level 2 IIHs, and receives an IIH from system identifier 0010.7bc7.ae41, which is the NE 1. The circuit type is Level 1. The circuit identifier is 0000.0000.0130.01, which is the view NE 1 has of the DIS (key reports shown in bold text text for purpose of example).

ISIS-Adj: Sending L1 IIH on Ethernet0ISIS-Adj: Sending L2 IIH on Ethernet0ISIS-Adj: Rec L1 IIH from 0010.7bc7.ae41 (Ethernet0), cir type 1, cir id 0000.0000.0130.01ISIS-Adj: Area mismatch, level 1 IIH on Ethernet0ISIS-Adj: Sending L1 IIH on Ethernet0ISIS-Adj: Sending L2 IIH on Ethernet0

The report by the debug isis adjacency command lists an area mismatch for Level 1 IIH. The IS-IS router NE 1 and Router 1 do not have the same area identifier. The NSAP for both devices needs to be checked.

In the following example, the Cisco router is running an IS-IS multiarea, so the IS-IS process associated with Ethernet interface 0 must be checked. The report indicates that IS-IS process area_02 was assigned to Ethernet interface 0.

router isis area_02 net 39.840f.8011.9999.0000.1111.0200.0000.0000.0130.00

To prevent the mismatch, IS-IS process area_01 should have been assigned to Ethernet interface 0:

router isis area_01 net 39.840f.8011.9999.0000.1111.0100.0000.0000.0130.00

The following example shows how to verify that the IS-IS adjacency shown in Figure 4-39 on page 4-76 is coming up correctly after the change. NE 1 is configured as Level 1 IS-IS. Router 1 is configured as a Level 1 and Level 2 router. The debugging is being done on Router 1. Router 1 is sending Level 1 and Level 2 IIHs. Router 1 is receiving Level 1 IIHs from NE 1. The IS-IS adjacencies are coming up correctly.

Router1# debug isis adjacency

IS-IS Adjacency related packets debugging is onRouter1#ISIS-Adj: Sending L2 IIH on Ethernet0ISIS-Adj: Sending L1 IIH on Ethernet0ISIS-Adj: Sending L2 IIH on Ethernet0ISIS-Adj: Sending L1 IIH on Ethernet0ISIS-Adj: Sending L2 IIH on Ethernet0ISIS-Adj: Sending L1 IIH on Ethernet0ISIS-Adj: Sending L2 IIH on Ethernet0ISIS-Adj: Rec L1 IIH from 00e0.b064.4325 (Ethernet0), cir type 1, cir id 0000.0000.60B1.01ISIS-Adj: Sending L1 IIH on Ethernet0ISIS-Adj: Sending L2 IIH on Ethernet0

In the following example output from the show clns isis neighbors command, Router 1 and TN-16 Node 1 have formed a Level 1 adjacency. The designated Level 1 IS on the LAN is circuit identifier 0000.0000.60B1 according to the system identifier 0000.0000.0F0F.

Router1# show clns isis neighbors

System Id Interface State Type Priority Circuit Id Format0000.0000.0F0F Et0 Up L1 64 0000.0000.60B1.01 Phase V



Verifying IS-IS Network Connectivity Using the ping and traceroute Commands

The route to a specific network element can be traced with the traceroute command. The traceroute command uses the Time to Live (TTL) field in an IP datagram to cause routers in the path to send back error messages. The IP version of the traceroute command is the default, and there is a CLNS version of the command. The following example shows a route traced to device NE14B for the sample network shown in Figure 4-40.

Figure 4-40 Sample Network for Determining IS-IS Network Topology

3640A# traceroute clns NE14B

Type escape sequence to abort.Tracing the route to NE14B (39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00)

1 NE14A(39.840f.8011.9999.0000.1111.0001.00e0.b064.4324.00) 0 msec ! 0 msec ! 4 msec ! 2 NE14B(39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00) 0 msec ! 0 msec ! 0 msec !

The ping clns EXEC command is another method to determine connectivity to an IS-IS router or ES. The following example shows sample output of the ping clns EXEC command to device NE14B:

3640A# ping clns NE14B


The following example shows debug command output from the CLNS packets sent from the ping clns command. The ping originates from the Cisco 3640 router with NET 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00, to device NE14B with NET 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00.

3640A#

00:03:45: CLNS: Originating packet, size 10000:03:45: from 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00 to 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00 via 00E0.B064.4324 (FastEthernet3/0.1 00e0.b064.4325)00:03:45: CLNS: Echo Reply PDU received on FastEthernet3/0.1!00:03:45: CLNS: Originating packet, size 10000:03:45: from 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00 to 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00

9562

8

NE14BArea0001

Area0002

Area0003

NE14A

NE15A

NE25BNE25A

NE26BNE26A


VLAN using802.1Q

CLNS packet flow



via 00E0.B064.4324 (FastEthernet3/0.1 00e0.b064.4325)00:03:45: CLNS: Echo Reply PDU received on FastEthernet3/0.1!00:03:45: CLNS: Originating packet, size 10000:03:45: from 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00 to 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00 via 00E0.B064.4324 (FastEthernet3/0.1 00e0.b064.4325)00:03:45: CLNS: Echo Reply PDU received on FastEthernet3/0.1!00:03:45: CLNS: Originating packet, size 10000:03:45: from 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00 to 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00 via 00E0.B064.4324 (FastEthernet3/0.1 00e0.b064.4325)00:03:45: CLNS: Echo Reply PDU received on FastEthernet3/0.1!00:03:45: CLNS: Originating packet, size 10000:03:45: from 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00 to 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00 via 00E0.B064.4324 (FastEthernet3/0.1 00e0.b064.4325)00:03:45: CLNS: Echo Reply PDU received on FastEthernet3/0.1!

The Cisco IOS ping EXEC command does not require the clns keyword in the command string. It is possible to enter the ping command with the CLNS host identifier or the NET and get the same results. The following examples show sample reports from both command strings:

3640A# ping 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00

Translating "39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00"...domain server (255.255.255.255)


3640A# ping NE14B

Translating "NE14B"...domain server (255.255.255.255)


Troubleshooting Network Connections Using the ping clns Command

A typical service provider network is shown in Figure 4-41. In this troubleshooting example, the OSS cannot access device NE26B. The technician at the network operations center (NOC) has connectivity to the central office router.



Figure 4-41 Typical Service Provider Network

Figure 4-42 shows router 3640A and connections to the network elements in the central office. The NOC technician has telnetted to router 3640A and is troubleshooting the OSI connectivity to network element device NE26B.

Figure 4-42 Troubleshooting OSI Connectivity

The first part of the example uses the ping clns EXEC command to try a connection to device NE26B.

Note Not all network elements in the network support the ping clns EXEC command; check with your network element vendor.

In the following example, the ping clns command was not successful at making the connection:


Type escape sequence to abort.Sending 5, 100-byte CLNS Echos with timeout 2 seconds

CLNS: cannot send ECHO.CLNS: cannot send ECHO.CLNS: cannot send ECHO.CLNS: cannot send ECHO.

9562

9

OSS

IP/OSI

CLNS packet flow


VLAN using802.1Q

NE14BArea0001

Area0002

Area0003

NE14A

NE15A

NE25BNE25A

NE26BNE26A

9562

8

NE14BArea0001

Area0002

Area0003

NE14A

NE15A

NE25BNE25A

NE26BNE26A


VLAN using802.1Q

CLNS packet flow



CLNS: cannot send ECHO.Success rate is 0 percent (0/5)

Next, issue the ping clns EXEC command to try a connection to the GNE. In the following example, the network element supports the ping clns command and a successful connection is made:

3640A# ping clns NE26A


The router is configured with clns host command statements for the network elements, so the technician did not have to type out the whole NSAP address; see the section “Mapping NSAPs to CLNS Host Names” section on page 4-69.

The next step is to determine whether the IS-IS adjacency is coming up between router 3640A and device NE26A. Use the show clns interface EXEC command to see that the number of Level 1 IS-IS adjacencies is 0 (text in bold for purpose of example):


FastEthernet3/0.3 is up, line protocol is up Checksums enabled, MTU 1497, Encapsulation SAP ERPDUs enabled, min. interval 10 msec. RDPDUs enabled, min. interval 100 msec., Addr Mask enabled Congestion Experienced bit set at 4 packets CLNS fast switching enabled CLNS SSE switching disabled DEC compatibility mode OFF for this interface Next ESH/ISH in 21 seconds Routing Protocol: IS-IS (area0003) Circuit Type: level-1-2 Interface number 0x0, local circuit ID 0x1 Level-1 Metric: 10, Priority: 127, Circuit ID: 3640A.01 Level-1 IPv6 Metric: 10 Number of active level-1 adjacencies: 0 Next IS-IS LAN Level-1 Hello in 51 milliseconds

The next step is to check processes in area 0003. Use the show clns neighbors EXEC command to display the areas. In the following example, the system identifier for device NE26A is listed and is on Fast Ethernet interface 3/0.3. The protocol that is coming up is ES-IS; therefore, one of the systems is configured as an ES on this interface.




Area area0003:System Id Interface SNPA State Holdtime Type ProtocolNE26A Fa3/0.3 00d0.5872.9720 Up 278 IS ES-IS



Use the debug isis adjacency command to watch IS-IS adjacencies come up. IIHs are being received by router 3640A on Fast Ethernet interfaces 3/0.2 and 3/0.1. IIHs are being sent by router 3640A on Fast Ethernet interfaces 3/0.1, 3/0.2, and 3/0.3. The problem is with device NE26A; it is not sending Level 1 IIHs on Fast Ethernet interface 3/0.3.

3640A# debug isis adjacency

IS-IS Adjacency related packets debugging is on

3640A#01:23:04: ISIS-Adj (area0002): Rec L1 IIH from 00e0.b064.434e (FastEthernet3/0.2), cir type L1, cir id 0010.7BC7.AE40.01, length 14701:23:05: ISIS-Adj (area0001): Rec L1 IIH from 00e0.b064.4325 (FastEthernet3/0.1), cir type L1, cir id 0010.7BC7.AE40.01, length 14701:23:06: ISIS-Adj (area0001): Sending L2 LAN IIH on FastEthernet3/0.1, length 149701:23:06: ISIS-Adj (area0003): Sending L1 LAN IIH on FastEthernet3/0.3, length 149701:23:07: ISIS-Adj (area0001): Sending L1 LAN IIH on FastEthernet3/0.1, length 149701:23:07: ISIS-Adj (area0002): Sending L1 LAN IIH on FastEthernet3/0.2, length 149701:23:09: ISIS-Adj (area0001): Rec L1 IIH from 0010.7bd8.c7d0 (FastEthernet3/0.1), cir type L1, cir id 0010.7BC7.AE40.01, length 14701:23:09: ISIS-Adj (area0001): Sending L1 LAN IIH on FastEthernet3/0.1, length 149701:23:09: ISIS-Adj (area0003): Sending L1 LAN IIH on FastEthernet3/0.3, length 149701:23:10: ISIS-Adj (area0002): Sending L1 LAN IIH on FastEthernet3/0.2, length 149701:23:12: ISIS-Adj (area0001): Sending L1 LAN IIH on FastEthernet3/0.1, length 149701:23:12: ISIS-Adj (area0003): Sending L1 LAN IIH on FastEthernet3/0.3, length 149701:23:12: ISIS-Adj (area0002): Sending L1 LAN IIH on FastEthernet3/0.2, length 149701:23:13: ISIS-Adj (area0001): Rec L1 IIH from 00e0.b064.4325 (FastEthernet3/0.1), cir type L1, cir id 0010.7BC7.AE40.01, length 14701:23:14: ISIS-Adj (area0002): Rec L1 IIH from 00e0.b064.434e (FastEthernet3/0.2), cir type L1, cir id 0010.7BC7.AE40.01, length 14701:23:14: ISIS-Adj (area0001): Sending L2 LAN IIH on FastEthernet3/0.1, length 149701:23:15: ISIS-Adj (area0001): Sending L1 LAN IIH on FastEthernet3/0.1, length 149701:23:15: ISIS-Adj (area0002): Sending L1 LAN IIH on FastEthernet3/0.2, length 149701:23:15: ISIS-Adj (area0003): Sending L1 LAN IIH on FastEthernet3/0.3, length 149701:23:18: ISIS-Adj (area0001): Sending L1 LAN IIH on FastEthernet3/0.1, length 149701:23:18: ISIS-Adj (area0001): Rec L1 IIH from 0010.7bd8.c7d0 (FastEthernet3/0.1), cir type L1, cir id 0010.7BC7.AE40.01, length 14701:23:18: ISIS-Adj (area0002): Sending L1 LAN IIH on FastEthernet3/0.2, length 149701:23:18: ISIS-Adj (area0003): Sending L1 LAN IIH on FastEthernet3/0.3, length 149701:23:21: ISIS-Adj (area0001): Sending L1 LAN IIH on FastEthernet3/0.1, length 149701:23:21: ISIS-Adj (area0003): Sending L1 LAN IIH on FastEthernet3/0.3, length 149701:23:21: ISIS-Adj (area0002): Sending L1 LAN IIH on FastEthernet3/0.2, length 149701:23:22: ISIS-Adj (area0001): Rec L1 IIH from 00e0.b064.4325 (FastEthernet3/0.1), cir type L1, cir id 0010.7BC7.AE40.01, length 14701:23:23: ISIS-Adj (area0002): Rec L1 IIH from 00e0.b064.434e (FastEthernet3/0.2), cir type L1, cir id 0010.7BC7.AE40.01, length 147

The next step is to debug the ES-IS protocol using the debug clns esis packets command. The following example shows a configuration error by the technician:

3640A# debug clns esis packets

ES-IS packets debugging is on

3640A#01:32:22: ES-IS: ISH from 00e0.b064.4325 (FastEthernet3/0.1), HT 30001:32:26: ES-IS: ISH from 00e0.b064.434e (FastEthernet3/0.2), HT 30001:32:30: ES-IS: ISH sent to All ESs (FastEthernet3/0.1): NET 39.840f.8011.9999.0000.1111.0001.0010.7bc7.ae40.00, HT 300, HLEN 3001:32:35: ES-IS: ISH from 00d0.5872.9720 (FastEthernet3/0.3), HT 300



Router 3640A first receives an IS Hello (ISH) from device NE14A (SNPA 00e0.b064.4325) on Fast Ethernet interface 3/0.1. The holdtime is 300 seconds before discarding. Router 3640A receives an ISH from device NE25A (SNPA 00e0.b064.434e) on Fast Ethernet interface 3/0.2. An ISH was sent to all end systems on Fast Ethernet interface 3/0.1 with a hold time of 300 seconds. The packet header length is 30 bytes. The last packet is an ISH from device NE26A (SNPA 00d.0.5872.9720) with a hold time of 300 seconds. Device NE26A has only the ES-IS protocol turned up. Router 3640A is sending out ESHs on all the Fast Ethernet interfaces. Device NE26A is sending an ISH. Device NE26A is configured only to support ES-IS, which was determined because ISHs were being sent, but not IIH.

Once device NE26A is correctly configured for IS-IS routing, verify the correct adjacency using the show clns neighbors EXEC command. The following example shows the report displayed:





The following example shows the results of ping clns commands:

3640A# ping clns NE26A




Successful connection indicates that the network is up and working.

Troubleshooting Network Connections Using TARP PDUs

A TARP type 5 PDU can be used to troubleshoot the network. (See the “Mapping NSAPs to Device Names Using TARP” section on page 4-54 for more information about TARP.) The type 5 PDU is sent to a specific NSAP address requesting the TID. The analogy would be sending an IP ping command in an IP network. The Cisco IOS software provides a ping clns EXEC command, but not all network vendors of SONET/SDH equipment have implemented support for the CLNS ping command. In Figure 4-43, a TARP type 5 PDU is being sent from router 3640A to device NE26B. Figure 4-43 also shows that the response is a type 3 PDU.



Figure 4-43 TARP Type 5 PDU Transmissions

The following example shows how to issue the debug tarp packets and debug tarp events commands and interpret the output:

3640A# debug tarp packetsTARP packet info debugging is on3640A# debug tarp eventsTARP events debugging is on

The tarp query is issued for 39.840f.8011.9999.0000.1111.0003.0010.7b17.f880.00

3640A# tarp query 39.840f.8011.9999.0000.1111.0003.0010.7b17.f880.00


TID corresponding to NET 39.840f.8011.9999.0000.1111.0003.0010.7b17.f880.00 is NE26B

The debug tarp packets command output shows the type 5 PDU being sent to its destination:

3640A#00:15:22: TARP-PA: Originated TARP packet, type 5, to destination 39.840f.8011.9999.0000.1111.0003.0010.7b17.f880.0000:15:22: TARP-EV: Packet from 39.840f.8011.9999.0000.1111.0003.0010.7b17.f880.00 has a 00:15:22: sequence number (4) > that in LDB cache entry (3) 00:15:22: - updating cache entry

A type 3 PDU is received on Fast Ethernet interface 3/0.3. The PDU is the response from device NE26B for the type 5 PDU.

00:15:22: TARP-PA: Received TARP type 3 PDU on interface FastEthernet3/0.300:15:22: Lft = 100, Seq = 4, Prot type = 0xFE, URC = TRUE00:15:22: Ttid len = 0, Stid len = 5, Prot addr len = 2000:15:22: Packet sent/propagated by 39.840f.8011.9999.0000.1111.0003.0010.7b17.f880.af00:15:22: Originator's NSAP : 39.840f.8011.9999.0000.1111.0003.0010.7b17.f880.0000:15:22: Originator's TID : NE26B

The debug tarp event command output indicates that device NE26B is entered into the TARP data cache:

00:15:22: TARP-PA: Created new DYNAMIC cache entry for NE26B

The tarp query command issues a TARP type 5 PDU, which is sent to a specific network and requests the TID or name of the network element.

9563

2

NE14BArea0001

Area0002

Area0003

NE14A

NE15A

NE25BNE25A

NE26BNE26A


TARP type 5PDUs

TARP type 5 PDUs

TARP type 3PDUs



The following example shows a TARP query being sent to device NE14B with NET 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00. The TID is device NE14B. Note that the CLNS host name and the TID were both set to device NE14B, which was chosen by the system administrator.

3640A# tarp query 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00


TID corresponding to NET 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00 is NE14B

Cisco IOS debug commands allow packets issued from a tarp query command to be examined. The following examples show output from the debug tarp events and debug tarp packets EXEC commands. The debug command output is based on the tarp query command. (Bold text highlights key parts of the report for purpose of example.)

3640A# debug tarp eventsTARP events debugging is on3640A# debug tarp packetsTARP packet info debugging is on

3640A#00:33:23: TARP-PA: Originated TARP packet, type 5, to destination 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.0000:33:23: TARP-PA: Received TARP type 3 PDU on interface FastEthernet3/0.100:33:23: Lft = 100, Seq = 2, Prot type = 0xFE, URC = TRUE00:33:23: Ttid len = 0, Stid len = 5, Prot addr len = 2000:33:23: Packet sent/propagated by 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.af00:33:23: Originator's NSAP : 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.0000:33:23: Originator's TID : NE14B00:33:23: TARP-PA: Created new DYNAMIC cache entry for NE14B

The output indicates a TARP type 5 PDU is sent to NET 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00. The packet that was receive is a type 3 PDU and was sent by NSAP 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.af. The network selector on the NSAP is “af,” which designates the TARP application. The output also reports the originator’s NSAP as 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00. More accurately, this label should be the originator’s NET. The originator’s TID is listed as NE14B.

If the NSAP or NET of the IS-IS router is not known but the TID is known, use the tarp resolve EXEC command to test connectivity between devices. The following example shows sample output:

3640A# tarp resolve NE14B


NET corresponding to TID NE14B is 39.840f.8011.9999.0000.1111.0001.0050.7363.7b40.00

In the output, the router will wait 15 seconds for a response before issuing a TARP type 2 PDU. Device NE14B responds within 15 seconds with its NET, which is the NSAP address and selector value of 00.


Chapter 4 SONET/SDH OSI EnvironmentsDistribution Layer Configuration

Distribution Layer ConfigurationThis section focuses on the distribution layer of Cisco’s three-tiered network architecture and contains these sections:

• Configuring the Distribution Network, page 4-87

• Distribution Network Configuration Example, page 4-89

Configuring the Distribution NetworkThe hypothetical network that will be used in this section assumes the network is laid out in three geographic areas. Each geographic area will be a separate Open System Interconnection (OSI) domain. The core routers will be placed in a separate domain in the center. Figure 4-44 shows the concept; domain designations have also been provided.

Figure 4-44 OSI Domains for the Distribution Network

As previously mentioned in this document, Cisco recommends that customers implement a three-tiered architecture in the data communications network (DCN) (see “The Cisco Three-Tiered DCN Network Architecture” section on page 4-12). The network shown in Figure 4-45 has the access layer and distribution routers in the same OSI domain.

Figure 4-45 Three-Tiered Architecture with Routing Protocols and Domains

CoreDomain

bbbb

Domain1111

Domain2222

Domain3333

1039

77

Accessrouters

Distributionrouters

CoreroutersIDRP

IS-IS

IS-IS IS-IS

1039

73

Cloud



The IS-IS routing protocol is running within the OSI domain. The core routers have been placed in a separate OSI domain. An Interdomain Routing Protocol (IDRP) is running between the distribution and core routers. The Level 2 routers within a domain must be connected contiguously to provide access throughout the domain. In Figure 4-45, the distribution routers are connected with Ethernet, and IS-IS is run over the Ethernet. The IDRP runs over a separate Ethernet network, as shown in Figure 4-45. The two Ethernet networks could also be configured using VLANs. A redundant alternative would be to install two switches and configure a separate VLAN for IS-IS and the IDRP on each switch. The service provider should not configure IS-IS and the IDRP on the same VLAN if the IDRP is ISO-IGRP.

The distribution routers should be configured in one IS-IS area that is shared by only the distribution routers in this site. The distribution routers can be configured as Level 1/Level 2 routers. The distribution routers will form a Level 2 adjacency to the access routers over the WAN links, because the access routers in the central office will be in a separate OSI area. The distribution routers will form a Level 1/Level 2 adjacency over the LAN connecting the routers at the distribution site. The service provider should make sure the routers have redundant LANs tiering the area together. The Level 1 area must stay contiguous. In Figure 4-46, there is a separate VLAN configured for IS-IS on each switch. Figure 4-46 also shows the adjacencies.

Figure 4-46 Three-Tiered Architecture with Level 1/Level 2 Adjacencies

An alternative method is to configure the distribution routers as Level 2 routers only. Use the is-type level-2-only command to do so. The service provider would still place all the distribution routers at site A in the same OSI area. The advantage of configuring the routers as Level 2 is that the router needs to maintain only one set of adjacencies and one database. In other words, the Level 1 database and the Level 1 adjacencies are eliminated, which lowers the overhead on the router. The adjacencies are shown in Figure 4-47.

Accessrouters

Level 1/Level 2

DistributionroutersLevel 2

1039

74

Backbone

Level 1adjacency

Level 2adjacency

DistributionSite A

DistributionSite B

Area5001

Area5001Area

4012

Area4005

Level 2adjacency

Level 1/Level2adjacency

Level 2adjacency

Level 1/Level 2adjacency

Area4005Area4005

Area4005Area4005

Corerouters

IS-IS VLANIDRP VLAN



Figure 4-47 Three-Tiered Architecture with Level 2 Adjacencies

Distribution Network Configuration ExampleIn the following sample configuration, the distribution router is in domain 3333 and area0003. The Connectionless Network Service (CLNS) configuration for a distribution router in Distribution site A is listed. The host name of the router is 7507A. Ethernet interfaces 0/0 and 0/1 are connected to two separate LANs, which make up the redundant LANs in the distribution center. Serial interfaces 1/0 through 6/7 are connected using a DS1 link to a separate access site or central office. A second distribution site is recommended for redundancy, as shown in Figure 4-47. The second distribution routers would be connected to the same access sites with a DS1. The configuration would be very similar.

hostname Access7507A!clns routing!!interface Ethernet0/0clns router isis area0003 tarp enable!interface Ethernet0/1clns router isis area0003 tarp enable

!interface Serial1/0 description DS1 City1 clns router isis area0003 tarp enable!interface Serial1/1 description DS1 City2 clns router isis area0003 tarp enable!interface Serial1/2 description DS1 City3

IS-IS VLANIDRP VLAN

Accessrouters

Level1/Level2

DistributionroutersLevel 2

1039

75

Backbone

Level 1adjacency

Level 2adjacency

DistributionSite A

DistributionSite B

Area5001

Area5001Area

4012

Area4005

Level 2adjacency

Level 2adjacency

Level 2adjacency

Level 2adjacency

Area4005Area4005

Area4005Area4005

Corerouters



clns router isis area0003 tarp enable!interface Serial1/3 description DS1 City4 clns router isis area0003 tarp enable!interface Serial1/4 description DS1 City5 clns router isis area0003 tarp enable!interface Serial1/5 description DS1 City6 clns router isis area0003 tarp enable!interface Serial1/6 description DS1 City7 clns router isis area0003 tarp enable!interface Serial1/7 description DS1 City8 clns router isis area0003 tarp enable!interface Serial4/0 description DS1 City9 clns router isis area0003 tarp enable!interface Serial4/1 description DS1 City10 clns router isis area0003 tarp enable!interface Serial4/2 description DS1 City11 clns router isis area0003 tarp enable!interface Serial4/3 description DS1 City12 clns router isis area0003 tarp enable!interface Serial4/4 description DS1 City13 clns router isis area0003 tarp enable!interface Serial4/5 description DS1 City14 clns router isis area0003 tarp enable!interface Serial4/6 description DS1 North1 clns router isis area0003 tarp enable!interface Serial4/7



description T1 City15 clns router isis area0003 tarp enable!interface Serial5/0 description DS1 City16 clns router isis area0003 tarp enable!interface Serial5/1 description DS1 City17 clns router isis area0003 tarp enable!interface Serial5/2 description City18 clns router isis area0003 tarp enable!interface Serial5/3 description DS1 City19 clns router isis area0003 tarp enable!interface Serial5/4 description DS1 Main1 clns router isis area0003 tarp enable!interface Serial5/5 description DS1 City20 clns router isis area0003 tarp enable!interface Serial5/6 description DS1 City21 clns router isis area0003 tarp enable!interface Serial5/7 description DS1 City22 clns router isis area0003 tarp enable!interface Serial6/0 description DS1 City23 clns router isis area0003 tarp enable!interface Serial6/1 description DS1 City24 clns router isis area0003 tarp enable!interface Serial6/2 description DS1 City25 clns router isis area0003 tarp enable!interface Serial6/3 description DS1 City26 clns router isis area0003 tarp enable!


Chapter 4 SONET/SDH OSI EnvironmentsCore Layer Configuration

interface Serial6/4 description DS1 City27 clns router isis area0003 tarp enable!interface Serial6/5 description DS1 City28 clns router isis area0003 tarp enable!interface Serial6/6 description DS1 City29 clns router isis area0003 tarp enable!interface Serial6/7 description DS1 City30 clns router isis area0003 tarp enable!router isis area0003 net 39.840f.8011.9999.0000.3333.0003.1234.0c15.86a3.00!tarp runtarp tid Access7507A

Core Layer ConfigurationThe following sections describe how to configure the core portion of the OSI network:

• OSI Domains and the Core, page 4-92

• Configuring the Core Network, page 4-93

• Core Network Configuration Examples, page 4-93

OSI Domains and the CoreA large OSI network is made up of multiple OSI domains. The recommended architectural design for a large OSI network is to place the core in an OSI domain. The individual OSI domains are connected to the core at two points. Figure 4-48 illustrates this concept. The core configuration can be configured with static routes, ISO-IGRP, or multiprotocol BGP. Multiprotocol BGP configuration is described in the feature module titled Multiprotocol BGP (MP-BGP) Support for CLNS.

ISO-IGRP can be used in the core to link the three OSI domains. The IS-IS routing protocol will be run in each of the three IS-IS domains, as shown in Figure 4-48. The IS-IS routing protocol will be run on the access routers and the distribution routers. The core routers will be the boundary between the IS-IS domains and the ISO-IGRP domain, and the core routers will run the IS-IS and ISO-IGRP routing protocols. The ISO-IGRP routes will be redistributed directly into IS-IS. IS-IS should not be redistributed directly into ISO-IGRP. The routes injected into ISO-IGRP should be summarized. The domain can be summarized with a single static route that can be injected into the core.


http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/fm_bgpmc.htm


Configuring the Core NetworkThe example network used in this section is based on a lab network. The lab network sample configurations will have only one core, instead of the recommended two cores. This section will describe some configuration tricks to implement a second core. The lab network has three routers in the core, which will connect together using Ethernet. In a real network, WAN links, rather than Ethernet, would be used to make the connections. The core routers are connected using Ethernet to distribution routers as shown in Figure 4-48. The four domains are addressed as follows:

39.840f.8011.9999.0000.111139.840f.8011.9999.0000.222239.840f.8011.9999.0000.333339.840f.8011.9999.0000.bbbb

Figure 4-48 Sample Core Network

In the lab network, each backbone router is connected using an Ethernet connection to a distribution router. The distribution router is connected using Ethernet to an access router. To simplify the example, the access site is not redundant and is sufficient for examining the core.

Core Network Configuration ExamplesThis section contains the following configuration examples:

• Configuring the First Core Router, page 4-94

• Verifying the First Core Router Configuration, page 4-95

• Configuring a Second Core Router, page 4-96

• Configuring the ISO IGRP Routing Protocol, page 4-96

• Configuring a Third Core Router, page 4-97

• Verifying the Routing Table, page 4-98

• Verifying Network Connectivity, page 4-99

• Adding Redundancy to the Core, page 4-99

• Tunneling Across the Core, page 4-100

• Completing the Core Router Configurations, page 4-100

BackBone1

Distribution3

Distribution1

Access3

Access1

Fast Ethernet 0/0

Fast Ethernet 0/1

Fast Ethernet 0/1BackBone2

Fast Ethernet 0/0

Fast Ethernet 0/0

Ethernet 1/0

Access2 Distribution2

Ethernet 1/0

Ethernet 5/0

IS-IS routing protocol

Domain 39.840f.8011.9999.0000.1111

Domain 39.840f.8011.9999.0000.2222

Domain 39.840f.8011.9999.0000.3333BackBone3

Domain 39.840f.8011.9999.0000.bbbb

ISO-IGRProuting protocol

1039

76

Fast Ethernet 0/1Fast Ethernet 0/1



Configuring the First Core Router

Start configuration of the core routers with the router named BackBone1. The router will be configured to participate in both IS-IS domain 1111 and area 9999. The IS-IS process identifier is area9999. Remember that the process identifier is similar in concept to a UNIX process identifier.

!router isis area9999 net 39.840f.8011.9999.0000.1111.9999.000d.bc2e.6d80.00 redistribute iso-igrp backbone

The backbone has been assigned its own domain bbbb and all three core routers have been placed in area 1001. The ISO-IGRP process identifier is called backbone.

The following example shows the ISO-IGRP configuration:

router iso-igrp backbone net 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d80.00 redistribute static

The challenge is to summarize the domain into the core using a static route. The route is summarized with the following clns route command. The following clns route command configures a path to domain 1111 or 39.840f.8011.9999.0000.1111. The route can be accessed using Ethernet interface 1/0 on router BackBone1.

clns route 39.840f.8011.9999.0000.1111 Ethernet1/0 000d.bc2e.6d90

Ethernet interface 1/0 is the BackBone1 interface connected to the distribution router, which is labeled Distribution1. The MAC address of Ethernet interface 1/0 on the BackBone1 router is 000d.bc2e.6d90. Use the show interfaces command, as the following sample output shows, to confirm the MAC address.

BackBone1# show interfaces ethernet 1/0

Ethernet1/0 is up, line protocol is down Hardware is AmdP2, address is 000d.bc2e.6d90 (bia 000d.bc2e.6d90) Internet address is 192.168.10.1/26 MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, reliability 128/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) ARP type: ARPA, ARP Timeout 04:00:00 Last input never, output 00:00:08, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 input packets with dribble condition detected 254 packets output, 18476 bytes, 0 underruns 254 output errors, 0 collisions, 4 interface resets 0 babbles, 0 late collision, 0 deferred 255 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out



Figure 4-48 on page 4-93 shows that router BackBone1 on Fast Ethernet interface 0/0 is connected to router BackBone2 on Fast Ethernet interface 0/0. Router BackBone1 on FastEthernet interface 0/1 is connected to router BackBone3 on Fast Ethernet interface 0/1. ISO-IGRP is turned up on these interfaces. For purpose of example, the following configuration shows the routing processes for ISO-IGRP in bold text. The ISO-IGRP process is called backbone. TARP is enabled on the backbone.

interface FastEthernet0/0 ip address 192.168.20.1 255.255.255.252 speed auto half-duplex clns router iso-igrp backbone tarp enable

interface FastEthernet0/1 ip address 192.168.20.5 255.255.255.252 speed auto half-duplex clns router iso-igrp backbone tarp enable

Figure 4-48 on page 4-93 shows that BackBone1 router Ethernet interface 1/0 is connected to the distribution router Distribution1. The IS-IS routing protocol is run over the Ethernet interface 1/0 connection between router BackBone1 and router Distribution1. The core router BackBone1 participates in domain 1111 and the backbone domain bbbb. The following example shows the configuration for Ethernet interface 1/0:

interface Ethernet1/0 ip address 192.168.10.1 255.255.255.192 half-duplex clns router isis area9999

Verifying the First Core Router Configuration

Use the show clns EXEC command to check interface configuration for the core router. The following example shows three interfaces configured for CLNS. Two NETs are shown, one NET for ISO-IGRP and a second for IS-IS.

BackBone1# show clns

Global CLNS Information: 3 Interfaces Enabled for CLNS NET: 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d80.00 NET: 39.840f.8011.9999.0000.1111.9999.000d.bc2e.6d80.00 Configuration Timer: 60, Default Holding Timer: 300, Packet Lifetime 64 ERPDU's requested on locally generated packets Intermediate system operation enabled (CLNS forwarding allowed) ISO-IGRP level-1 Router: backbone Routing for Domain: 39.840F.8011.9999.0000.BBBB, Area: 1001 ISO-IGRP level-2 Router: DOMAIN_backbone Routing for Domain: 39.840F.8011.9999.0000.BBBB IS-IS level-1-2 Router: area9999 Routing for Area: 39.840f.8011.9999.0000.1111.9999

Use the show clns neighbors EXEC command to verify that there are three neighbors. BackBoneR1 has a Level 1 ISO-IGRP adjacency on Fast Ethernet interface 0/1 with BackBoneR3. The router Distribution1 has a Level 1/Level 2 adjaceny on Ethernet interface 1/0. BackBoneR2 has a Level 1 ISO-IGRP adjacency on Fast Ethernet interface 0/0 with BackBoneR3. The following show clns neighbors command output matches the configuration listed earlier and in Figure 4-48 on page 4-93.

BackBoneR1# show clns neighbors



System Id Interface SNPA State Holdtime Type ProtocolBackBoneR3 Fa0/1 0010.7bd8.c7d1 Up 39 L1 ISO-IGRPDistribution1 Et1/0 0010.7b17.f880 Up 9 L1L2 IS-ISBackBoneR2 Fa0/0 000d.bc2e.6d40 Up 50 L1 ISO-IGRP

Use the show clns neighbors detail EXEC command to show additional detail about the neighbors.

BackBoneR1# show clns neighbors detail

System Id Interface SNPA State Holdtime Type ProtocolBackBoneR3 Fa0/1 0010.7bd8.c7d1 Up 36 L1 ISO-IGRP Area Address(es): 39.840f.8011.9999.0000.bbbb.1001 Uptime: 01:32:07Distribution1 Et1/0 0010.7b17.f880 Up 7 L1L2 IS-IS Area Address(es): 39.840f.8011.9999.0000.1111.9999 Uptime: 01:32:08 NSF capableBackBoneR2 Fa0/0 000d.bc2e.6d40 Up 47 L1 ISO-IGRP Area Address(es): 39.840f.8011.9999.0000.bbbb.1001 Uptime: 01:32:08

Configuring a Second Core Router

The configuration for a second core router named BackBone2 in the example network is next. The router will be configured to participate in both IS-IS domain 2222 and area 0002. The IS-IS process identifier is area0002. Remember the process identifier is similar in concept to a UNIX process identifier. In the following example, notice the command to redistribute the routes in ISO-IGRP back into IS-IS. The number of routes will be small, because each domain is summarized with a static route into ISO-IGRP.

!router isis area0002 net 39.840f.8011.9999.0000.2222.0002.000d.bc2e.6d40.00 redistribute iso-igrp backbone

Configuring the ISO IGRP Routing Protocol

This section describes how to configure the ISO-IGRP routing protocol. The backbone has been assigned its own domain as bbbb, and all three core routers have been placed in area 1001. In the following ISO-IGRP configuration example, notice the redistribute static command that redistributes the static route that summarizes domain 2222 into ISO-IGRP:

router iso-igrp backbone net 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d40.00 redistribute static

The challenge is to summarize the domain into the core on a static route. The route is summarized with the clns route command, as shown in the following example. The clns route command configures a path to domain 2222 or 39.840f.8011.9999.0000. 2222. The route can be accessed using Ethernet interface 1/0, on router BackBone1.


Ethernet interface 0/1 is connected to the distribution router labeled Distribution1. The MAC address of Ethernet interface 1/0 on the BackBone1 router is 000d.bc2e.6d50. Use the show interfaces command, as the following sample output shows, to confirm the MAC address.

BackBoneR2# show interfaces ethernet 1/0

Ethernet1/0 is up, line protocol is up Hardware is AmdP2, address is 000d.bc2e.6d50 (bia 000d.bc2e.6d50) Internet address is 192.168.50.1/26



MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:00, output 00:00:04, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 8000 bits/sec, 1 packets/sec 5 minute output rate 4000 bits/sec, 0 packets/sec 2273 packets input, 2301496 bytes, 0 no buffer Received 2266 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 input packets with dribble condition detected 1048 packets output, 816754 bytes, 0 underruns 0 output errors, 0 collisions, 4 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out

Figure 4-48 on page 4-93 shows that BackBone2 Fast Ethernet interface 0/0 is connected to the BackBone1 router, and BackBone2 Fast Ethernet interface 0/1 is connected to the BackBone3 router. ISO-IGRP is turned up on these interfaces. For purpose of example, the following sample configuration shows the routing process for ISO-IGRP in bold text. The ISO-IGRP process is called backbone. TARP is enabled on the backbone.

interface FastEthernet0/0 ip address 192.168.20.2 255.255.255.252 speed auto half-duplex clns router iso-igrp backbone tarp enable!interface FastEthernet0/1 ip address 192.168.20.10 255.255.255.252 speed auto half-duplex clns router iso-igrp backbone tarp enable

Figure 4-48 on page 4-93 shows Ethernet interface 1/0 is connected to the distribution router labeled Distribution1. The IS-IS routing protocol is run over the Ethernet interface 1/0 connection between router BackBone2 and router Distribution2. The core router BackBone2 participates in domain 2222 and the backbone domain bbbb. The following example shows the configuration for Ethernet interface 1/0:

interface Ethernet1/0 ip address 192.168.50.1 255.255.255.192 half-duplex clns router isis area0002 tarp enable

Configuring a Third Core Router

Following is the configuration for the BackBone3 router, without step-by-step explanation. See the “Configuring the First Core Router” and “Verifying the First Core Router Configuration” sections for more details on core router configuration and verification.

router iso-igrp backbone redistribute static



net 39.840f.8011.9999.0000.bbbb.1001.0010.7bd8.c7d0.00!router isis area0033 redistribute iso-igrp backbone net 39.840f.8011.9999.0000.3333.0033.0010.7bd8.c7d0.00!clns route 39.840f.8011.9999.0000.3333 Ethernet5/0 0010.7bd8.c821!interface FastEthernet0/0 ip address 192.168.20.9 255.255.255.252 duplex auto speed auto clns router iso-igrp backbone tarp enable!interface FastEthernet0/1 ip address 192.168.20.6 255.255.255.252 duplex auto speed auto clns router iso-igrp backbone tarp enable!interface Ethernet5/0 ip address 192.168.100.1 255.255.255.252 half-duplex clns router isis area0033

Verifying the Routing Table

To verify the routing table created on the BackBoneR1 router, use the show clns route EXEC command. You will see the static route to domain 39.840f.8011.9999.0000.1111. The routes to domains 39.840f.8011.9999.0000.2222 and 39.840f.8011.9999.0000.3333 are learned from the ISO-IGRP routing protocol. You will also see the IS-IS routes to areas within domain 39.840f.8011.9999.0000.1111.

BackBoneR1# show clns route

ISO-IGRP Routing Table for Domain 39.840F.8011.9999.0000.BBBB, Area 1001System Id Next-Hop SNPA Interface Metric StateBackBoneR3 BackBoneR3 0010.7bd8.c7d1 Fa0/1 110 UpBackBoneR2 BackBoneR2 000d.bc2e.6d40 Fa0/0 110 UpBackBoneR1 0000.0000.0000 -- -- 0 Up

ISO-IGRP Routing Table for Domain 39.840F.8011.9999.0000.BBBBArea Id Next-Hop SNPA Interface Metric State1001 0000.0000.0000 -- -- 0 Up


C 39.840f.8011.9999.0000.1111.9999 [2/0], Local IS-IS AreaC 39.840f.8011.9999.0000.bbbb [2/0], Local ISO-IGRP DomainC 39.840f.8011.9999.0000.1111.9999.000d.bc2e.6d80.00 [1/0], Local IS-IS NETC 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d80.00 [1/0], Local ISO-IGRP NET

i 39.840f.8011.9999.0000.1111.0003 [110/20] via Distribution1, Ethernet1/0S 39.840f.8011.9999.0000.1111 [10/0] via Ethernet1/0I 39.840f.8011.9999.0000.2222 [100/110] via BackBoneR2, FastEthernet0/0



I 39.840f.8011.9999.0000.3333 [100/110] via BackBoneR3, FastEthernet0/1

Verifying Network Connectivity

To verify network connectivity, use the clns ping and trace EXEC commands.

In the following example, the ping is from access router Access1 in domain 1111 to access router Access2 in domain 2222:

Access2# ping clns Access1


The following example traces the route from Access2 to Access1; the route matches what is shown in Figure 4-48 on page 4-93.

Access2# trace clns Access1

Type escape sequence to abort.Tracing the route to Access1 (39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00)

1 Distribution2(39.840f.8011.9999.0000.2222.0002.0030.94e2.6ce0.00) 0 msec ! 0 msec ! 0 msec ! 2 BackBoneR2(39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d40.00) 4 msec ! 4 msec ! 4 msec ! 3 BackBoneR1(39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d80.00) 4 msec ! 4 msec ! 4 msec ! 4 Distribution1(39.840f.8011.9999.0000.1111.9999.0010.7b17.f880.00) 4 msec ! 4 msec ! 4 msec ! 5 Access1(39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00) 4 msec ! 4 msec ! 4 msec !Access2#

Adding Redundancy to the Core

When considering redundancy in the core portion of the network, most service providers will implement more redundancy than has been shown in the examples in this document. The first place the service providers will increase redundancy is between the core router and the distribution router, and the service provider will do so by building redundant LANs. Therefore, a second static route would need to be added for the second LAN. An earlier example in this document configured a single static route for a router designated BackBone1; this configuration is listed again in the following example. A second route would be almost identical, except that the route statement (clns route command) would reflect the appropriate Ethernet interface and its equivalent MAC address.


To continue adding redundancy, add a second core and a second set of distribution sites. In an ISO-IGRP configuration, one core must be a primary route and the second core a secondary or backup. The primary and secondary routes are designated by the length of the route specified in the static routes. The Cisco IOS software prefers the path with the longest route. Examine the route statements for the primary core using the following example:

! BackBone1 Routerclns route 39.840f.8011.9999.0000.1111 Ethernet1/0 000d.bc2e.6d90

! BackBone2 Routerclns route 39.840f.8011.9999.0000.2222 Ethernet1/0 000d.bc2e.6d50



! BackBone3 Routerclns route 39.840f.8011.9999.0000.3333 Ethernet5/0 0010.7bd8.c821

The second core will be made up of routers BackBone1A, BackBone2A and BackBone3A. The following examples show the static route for each of the secondary core routers, by router.

! BackBone1A Routerclns route 39.840f.8011.9999.0000.11 Ethernet1/1 000d.bc2e.7d90

! BackBone2A Routerclns route 39.840f.8011.9999.0000.22 Ethernet1/1 000d.bc2e.7d50

! BackBone3A Routerclns route 39.840f.8011.9999.0000.33 Ethernet4/1 0010.7bd8.d421

Notice that the route is shorter in length for the secondary routers. For example, router BackBone1 has a static route configured for 39.840f.8011.9999.0000.1111 and router BackBone1A has a static route configured for 39.840f.8011.9999.0000.11. The distribution routers have both routes in their routing tables. The distribution routers will choose the longer route or more significant route to forward packets to.

Tunneling Across the Core

Some service providers will have routers in the core that do not route CLNS. So tunnels must be built across the core. Cisco recommends that you route up to the distribution router and build a small number of tunnels across the core between the distribution routers.

Completing the Core Router Configurations

The following sections provide the configurations for the remaining routers in the sample lab network shown in Figure 4-48 on page 4-93:

• Configuring Router Access1, page 4-100



• Configuring Router Distribution1, page 4-105



Configuring Router Access1

The following example shows the relevant CLNS configuration commands for the router designated Access1 in Figure 4-48 on page 4-93:

Access1# show configuration

hostname Access1!clns routing!interface Ethernet0/0 ip address 192.168.10.66 255.255.255.192 half-duplex clns router isis area0003 tarp enable



!interface BRI0/0 no ip address shutdown!router isis area0003 net 39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00!clns host BackBoneR1 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d80.00clns host BackBoneR2 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d40.00clns host BackBoneR3 39.840f.8011.9999.0000.bbbb.1001.0010.7bd8.c7d0.00clns host Distribution2 39.840f.8011.9999.0000.2222.0002.0030.94e2.6ce0.00clns host Distribution1 39.840f.8011.9999.0000.1111.9999.0010.7b17.f880.00clns host Access1 39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00!tarp runtarp tid Access1!

Verifying the Configuration

The following examples display output from the show clns and show clns neighbors EXEC commands for router Access1. The commands display global information about CLNS and the router. The routing area is identified as 39.840f.8011.9999.0000.1111.0003.

Access1# show clns

Global CLNS Information: 2 Interfaces Enabled for CLNS NET: 39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00 Configuration Timer: 60, Default Holding Timer: 300, Packet Lifetime 64 ERPDU's requested on locally generated packets Intermediate system operation enabled (CLNS forwarding allowed) IS-IS level-1-2 Router: area0003 Routing for Area: 39.840f.8011.9999.0000.1111.0003

Access1# show clns neighbors

System Id Interface SNPA State Holdtime Type Protocol3640A Et0/0 0010.7bc7.ae41 Up 26 L2 IS-ISDistribution1 Et0/1 0010.7b17.f881 Up 28 L2 IS-IS

The following example displays information from the show clns route EXEC command:

Access1# show clns routeCodes: C - connected, S - static, d - DecnetIV I - ISO-IGRP, i - IS-IS, e - ES-IS B - BGP, b - eBGP-neighbor

C 39.840f.8011.9999.0000.1111.0003 [2/0], Local IS-IS AreaC 39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00 [1/0], Local IS-IS NET

i 39.840f.8011.9999.0000.1111.0001 [110/10] via 3640A, Ethernet0/0i 39.840f.8011.9999.0000.1111 [110/30] via Distribution1, Ethernet0/1i 39.840f.8011.9999.0000.2222 [110/20] via Distribution1, Ethernet0/1i 39.840f.8011.9999.0000.3333 [110/20] via Distribution1, Ethernet0/1i 39.840f.8011.9999.0000.1111.9999 [110/10] via Distribution1, Ethernet0/1i 39.840f.8011.9999.0000.bbbb [110/20] via Distribution1, Ethernet0/1



The following example shows how to test connectivity by issuing the ping clns command to a backbone router:

Access1# ping clns BackBoneR3


The following example shows how to trace a route to another router:

Access1# trace clns Distribution2

Type escape sequence to abort.Tracing the route to Distribution2 (39.840f.8011.9999.0000.2222.0002.0030.94e2.)

1 Distribution1(39.840f.8011.9999.0000.1111.9999.0010.7b17.f880.00) 0 msec ! ! 2 BackBoneR1(39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d80.00) 0 msec ! 0 m! 3 BackBoneR2(39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d40.00) 0 msec ! 0 m! 4 Distribution2(39.840f.8011.9999.0000.2222.0002.0030.94e2.6ce0.00) 4 msec ! !



Access2# show configuration

clns routing!interface Ethernet0 ip address 192.168.5.190 255.255.255.192 no ip route-cache no ip mroute-cache clns router isis area0012 tarp enable!interface Ethernet1 ip address 192.168.50.66 255.255.255.252 no ip route-cache no ip mroute-cache clns router isis area0012 tarp enable!router isis area0012 net 39.840f.8011.9999.0000.2222.0012.00e0.b064.434e.00!clns host BackBoneR1 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d80.00clns host BackBoneR2 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d40.00clns host BackBoneR3 39.840f.8011.9999.0000.bbbb.1001.0010.7bd8.c7d0.00clns host Distribution2 39.840f.8011.9999.0000.2222.0002.0030.94e2.6ce0.00clns host Distribution1 39.840f.8011.9999.0000.1111.9999.0010.7b17.f880.00clns host Access1 39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00clns host Access2 39.840f.8011.9999.0000.2222.0012.00e0.b064.434e.00!tarp runtarp tid Access2end




The following examples display output from the show clns and show clns neighbors EXEC commands for router Access2. The commands display global information about CLNS and the router. The routing area is identified as 39.840f.8011.9999.0000.2222.0012.

Access2# show clns

Global CLNS Information: 2 Interfaces Enabled for CLNS NET: 39.840f.8011.9999.0000.2222.0012.00e0.b064.434e.00 Configuration Timer: 60, Default Holding Timer: 300, Packet Lifetime 64 ERPDU's requested on locally generated packets Intermediate system operation enabled (CLNS forwarding allowed) IS-IS level-1-2 Router: area0012 Routing for Area: 39.840f.8011.9999.0000.2222.0012


System Id Interface SNPA State Holdtime Type ProtocolDistribution2 Et1 0030.94e2.6ce0 Up 23 L2 IS-ISAccess2#show clns neighbors detail

System Id Interface SNPA State Holdtime Type ProtocolDistribution2 Et1 0030.94e2.6ce0 Up 23 L2 IS-IS Area Address(es): 39.840f.8011.9999.0000.2222.0002 Uptime: 01:49:34

The following example shows the routing table for router Access2. The routes are listed to the backbone domain and the other two domains.

Access2# show clns route

Codes: C - connected, S - static, d - DecnetIV I - ISO-IGRP, i - IS-IS, e - ES-IS

C 39.840f.8011.9999.0000.2222.0012 [2/0], Local IS-IS AreaC 39.840f.8011.9999.0000.2222.0012.00e0.b064.434e.00 [1/0], Local IS-IS NET

i 39.840f.8011.9999.0000.2222.0002 [110/10] via Distribution2, Ethernet1i 39.840f.8011.9999.0000.1111 [110/20] via Distribution2, Ethernet1i 39.840f.8011.9999.0000.2222 [110/30] via Distribution2, Ethernet1i 39.840f.8011.9999.0000.3333 [110/20] via Distribution2, Ethernet1i 39.840f.8011.9999.0000.bbbb [110/20] via Distribution2, Ethernet1



Access3# show configuration!hostname Access3!enable password cisco!clns routing!interface Ethernet0/0



ip address 192.168.3.62 255.255.255.192 half-duplex tarp enable!interface Ethernet0/1 ip address 192.168.101.66 255.255.255.192 half-duplex clns router isis area0035 tarp enable!router isis area0035 net 39.840f.8011.9999.0000.3333.0035.0050.7363.7b40.00!clns host Distribution3 39.840f.8011.9999.0000.3333.0035.00e0.1ee3.c720.00clns host BackBoneR2 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d40.00clns host BackBoneR3 39.840f.8011.9999.0000.bbbb.1001.0010.7bd8.c7d0.00clns host BackBoneR1 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d80.00clns host Distribution2 39.840f.8011.9999.0000.2222.0002.0030.94e2.6ce0.00clns host Distribution1 39.840f.8011.9999.0000.1111.9999.0010.7b17.f880.00clns host Access1 39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00clns host Access2 39.840f.8011.9999.0000.2222.0012.00e0.b064.434e.00clns host Access3 39.840f.8011.9999.0000.3333.0035.0050.7363.7b40.00!tarp runtarp tid Access3!


The following examples display output from the show clns, show clns neighbors, and show clns neighbors detail EXEC commands for router Access3. The commands display global information about CLNS and the router. The routing area is identified as 39.840f.8011.9999.0000.3333.0035.

Access3# show clns

Global CLNS Information: 1 Interfaces Enabled for CLNS NET: 39.840f.8011.9999.0000.3333.0035.0050.7363.7b40.00 Configuration Timer: 60, Default Holding Timer: 300, Packet Lifetime 64 ERPDU's requested on locally generated packets Intermediate system operation enabled (CLNS forwarding allowed) IS-IS level-1-2 Router: area0035 Routing for Area: 39.840f.8011.9999.0000.3333.0035


System Id Interface SNPA State Holdtime Type ProtocolDistribution3 Et0/1 00e0.1ee3.c721 Up 9 L1L2 IS-IS

Access3# show clns neighbors detail

System Id Interface SNPA State Holdtime Type ProtocolDistribution3 Et0/1 00e0.1ee3.c721 Up 9 L1L2 IS-IS Area Address(es): 39.840f.8011.9999.0000.3333.0035Uptime: 00:05:32


Access3# show clns route




C 39.840f.8011.9999.0000.3333.0035 [2/0], Local IS-IS AreaC 39.840f.8011.9999.0000.3333.0035.0050.7363.7b40.00 [1/0], Local IS-IS NET

i 39.840f.8011.9999.0000.3333.0033 [110/20] via Distribution3, Ethernet0/1i 39.840f.8011.9999.0000.1111 [110/20] via Distribution3, Ethernet0/1i 39.840f.8011.9999.0000.2222 [110/20] via Distribution3, Ethernet0/1i 39.840f.8011.9999.0000.3333 [110/30] via Distribution3, Ethernet0/1i 39.840f.8011.9999.0000.bbbb [110/20] via Distribution3, Ethernet0/1

The following example shows how to test connectivity by issuing the ping clns command to router Access1:

Access3# ping clns Access1


The following example shows how to trace a route to another router:

Access3# trace clns Access1

Type escape sequence to abort.Tracing the route to Access1 (39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00)

1 Distribution3(39.840f.8011.9999.0000.3333.0035.00e0.1ee3.c720.00) 4 msec ! 0 msec ! 0 msec ! 2 BackBoneR3(39.840f.8011.9999.0000.bbbb.1001.0010.7bd8.c7d0.00) 0 msec ! 0 msec ! 0 msec ! 3 BackBoneR1(39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d80.00) 0 msec ! 0 msec ! 0 msec ! 4 Distribution1(39.840f.8011.9999.0000.1111.9999.0010.7b17.f880.00) 4 msec ! 4 msec ! 4 msec ! 5 Access1(39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00) 4 msec ! 4 msec ! 4 msec !

Configuring Router Distribution1

The following example shows the relevant CLNS configuration commands for the router designated Distribution1 in Figure 4-48 on page 4-93:

Distribution1# show configuration

hostname Distribution1!enable password cisco!clns routing!interface Ethernet0/0 ip address 192.168.10.2 255.255.255.252 no ip mroute-cache half-duplex clns router isis area9999 tarp enable!interface Ethernet0/1 ip address 192.168.10.65 255.255.255.192 no ip mroute-cache



half-duplex clns router isis area9999 tarp enable!router isis area9999 net 39.840f.8011.9999.0000.1111.9999.0010.7b17.f880.00!clns host BackBoneR1 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d80.00clns host BackBoneR2 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d40.00clns host BackBoneR3 39.840f.8011.9999.0000.bbbb.1001.0010.7bd8.c7d0.00clns host Distribution1 39.840f.8011.9999.0000.1111.9999.0010.7b17.f880.00clns host Distribution2 39.840f.8011.9999.0000.2222.0002.0030.94e2.6ce0.00clns host Access1 39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00!tarp runtarp tid Distribution1


The following examples display output from the show clns, show clns neighbors, and show clns neighbors detail EXEC commands for router Distribution1. The commands display global information about CLNS and the router. The routing area is identified as 39.840f.8011.9999.0000.1111.9999.

Distribution1# show clns

Global CLNS Information: 2 Interfaces Enabled for CLNS NET: 39.840f.8011.9999.0000.1111.9999.0010.7b17.f880.00 Configuration Timer: 60, Default Holding Timer: 300, Packet Lifetime 64 ERPDU's requested on locally generated packets Intermediate system operation enabled (CLNS forwarding allowed) IS-IS level-1-2 Router: area9999 Routing for Area: 39.840f.8011.9999.0000.1111.9999

Distribution1# show clns neighbors

System Id Interface SNPA State Holdtime Type ProtocolAccess1 Et0/1 00d0.5872.9721 Up 9 L2 IS-ISBackBoneR1 Et0/0 000d.bc2e.6d90 Up 25 L1L2 IS-IS

Distribution1# show clns neighbors detail

System Id Interface SNPA State Holdtime Type ProtocolAccess1 Et0/1 00d0.5872.9721 Up 8 L2 IS-IS Area Address(es): 39.840f.8011.9999.0000.1111.0003 Uptime: 00:03:20BackBoneR1 Et0/0 000d.bc2e.6d90 Up 29 L1L2 IS-IS Area Address(es): 39.840f.8011.9999.0000.1111.9999 Uptime: 02:16:45NSF capable


Distribution1# show clns route


C 39.840f.8011.9999.0000.1111.9999.0010.7b17.f880.00 [1/0], Local IS-IS NETC 39.840f.8011.9999.0000.1111.9999 [2/0], Local IS-IS Area

i 39.840f.8011.9999.0000.1111.0001 [110/20] via Access1, Ethernet0/1



i 39.840f.8011.9999.0000.1111.0003 [110/10] via Access1, Ethernet0/1i 39.840f.8011.9999.0000.1111 [110/20] via BackBoneR1, Ethernet0/0i 39.840f.8011.9999.0000.2222 [110/10] via BackBoneR1, Ethernet0/0i 39.840f.8011.9999.0000.bbbb [110/10] via BackBoneR1, Ethernet0/0




hostname Distribution2!interface Ethernet0/0 ip address 192.168.50.65 255.255.255.252 no ip mroute-cache half-duplex clns router isis area0002 tarp enable!interface Ethernet0/1 ip address 192.168.50.2 255.255.255.192 no ip mroute-cache half-duplex clns router isis area0002!router isis area0002 net 39.840f.8011.9999.0000.2222.0002.0030.94e2.6ce0.00!clns host BackBoneR1 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d80.00clns host BackBoneR2 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d40.00clns host BackBoneR3 39.840f.8011.9999.0000.bbbb.1001.0010.7bd8.c7d0.00clns host Distribution2 39.840f.8011.9999.0000.2222.0002.0030.94e2.6ce0.00clns host Distribution1 39.840f.8011.9999.0000.1111.9999.0010.7b17.f880.00clns host Access1 39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00clns host Access2 39.840f.8011.9999.0000.2222.0012.00e0.b064.434e.00!tarp runtarp tid Distribution2!




Global CLNS Information: 2 Interfaces Enabled for CLNS NET: 39.840f.8011.9999.0000.2222.0002.0030.94e2.6ce0.00 Configuration Timer: 60, Default Holding Timer: 300, Packet Lifetime 64 ERPDU's requested on locally generated packets Intermediate system operation enabled (CLNS forwarding allowed) IS-IS level-1-2 Router: area0002 Routing for Area: 39.840f.8011.9999.0000.2222.0002




System Id Interface SNPA State Holdtime Type ProtocolAccess2 Et0/0 00e0.b064.434f Up 8 L2 IS-ISBackBoneR2 Et0/1 000d.bc2e.6d50 Up 27 L1L2 IS-IS


System Id Interface SNPA State Holdtime Type ProtocolAccess2 Et0/0 00e0.b064.434f Up 7 L2 IS-IS Area Address(es): 39.840f.8011.9999.0000.2222.0012 Uptime: 01:48:26BackBoneR2 Et0/1 000d.bc2e.6d50 Up 23 L1L2 IS-IS Area Address(es): 39.840f.8011.9999.0000.2222.0002 Uptime: 01:48:26 NSF capable

The following example displays CLNS route information:



C 39.840f.8011.9999.0000.2222.0002 [2/0], Local IS-IS AreaC 39.840f.8011.9999.0000.2222.0002.0030.94e2.6ce0.00 [1/0], Local IS-IS NET

i 39.840f.8011.9999.0000.2222.0012 [110/10] via Access2, Ethernet0/0i 39.840f.8011.9999.0000.1111 [110/10] via BackBoneR2, Ethernet0/1i 39.840f.8011.9999.0000.2222 [110/20] via BackBoneR2, Ethernet0/1i 39.840f.8011.9999.0000.3333 [110/10] via BackBoneR2, Ethernet0/1i 39.840f.8011.9999.0000.bbbb [110/10] via BackBoneR2, Ethernet0/1




Using 3873 out of 29688 bytes!version 12.3service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname Distribution3!boot-start-markerboot system flash boot system romboot-end-marker!!enable password cisco!



clock timezone EST -5no aaa new-modelip subnet-zeroip domain name compgen.comip host 1d12RAA-2600 172.20.220.61ip host 1d12RAB-2600 172.20.220.60ip host 1d38RAE-7200 172.20.221.65ip host 1d38RAF-7200 172.20.221.66ip host 1d12RAC-2600 172.20.220.62ip name-server 172.30.4.11clns routingno ftp-server write-enablex25 routing!!stun peer-name 172.25.192.47stun protocol-group 103 basic!!interface Loopback0 ip address 192.168.5.252 255.255.255.192!interface Ethernet0/0 ip address 192.168.100.2 255.255.255.192 half-duplex clns router isis area0035 tarp enable!interface Ethernet0/1 ip address 192.168.5.61 255.255.255.192 half-duplex clns router isis area0035 tarp enable!interface Serial1/0 mtu 1562 no ip address encapsulation x25 dce no ip mroute-cache x25 ltc 5 x25 ips 512 x25 ops 512 x25 threshold 1 x25 pvc 1 rbp local port 10000 clockrate 9600!router ospf 795 log-adjacency-changes network 192.168.0.0 0.0.255.255 area 0!router isis area0035 net 39.840f.8011.9999.0000.3333.0035.00e0.1ee3.c720.00!clns host Distribution3 39.840f.8011.9999.0000.3333.0035.00e0.1ee3.c720.00clns host BackBoneR2 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d40.00clns host BackBoneR3 39.840f.8011.9999.0000.bbbb.1001.0010.7bd8.c7d0.00clns host BackBoneR1 39.840f.8011.9999.0000.bbbb.1001.000d.bc2e.6d80.00clns host Distribution2 39.840f.8011.9999.0000.2222.0002.0030.94e2.6ce0.00clns host Distribution1 39.840f.8011.9999.0000.1111.9999.0010.7b17.f880.00clns host Access1 39.840f.8011.9999.0000.1111.0003.00d0.5872.9720.00clns host Access2 39.840f.8011.9999.0000.2222.0012.00e0.b064.434e.00!



tarp runtarp tid Distribution3!




Global CLNS Information: 2 Interfaces Enabled for CLNS NET: 39.840f.8011.9999.0000.3333.0035.00e0.1ee3.c720.00 Configuration Timer: 60, Default Holding Timer: 300, Packet Lifetime 64 ERPDU's requested on locally generated packets Intermediate system operation enabled (CLNS forwarding allowed) IS-IS level-1-2 Router: area0035 Routing for Area: 39.840f.8011.9999.0000.3333.0035


System Id Interface SNPA State Holdtime Type ProtocolBackBoneR3 Et0/0 0010.7bd8.c821 Up 29 L2 IS-ISNE14B Et0/1 0050.7363.7b41 Up 26 L1L2 IS-IS


System Id Interface SNPA State Holdtime Type ProtocolBackBoneR3 Et0/0 0010.7bd8.c821 Up 23 L2 IS-IS Area Address(es): 39.840f.8011.9999.0000.3333.0033 Uptime: 00:52:12NE14B Et0/1 0050.7363.7b41 Up 26 L1L2 IS-IS Area Address(es): 39.840f.8011.9999.0000.3333.0035 Uptime: 00:17:36




C 39.840f.8011.9999.0000.3333.0035 [2/0], Local IS-IS AreaC 39.840f.8011.9999.0000.3333.0035.00e0.1ee3.c720.00 [1/0], Local IS-IS NET

i 39.840f.8011.9999.0000.3333.0033 [110/10] via BackBoneR3, Ethernet0/0i 39.840f.8011.9999.0000.1111 [110/10] via BackBoneR3, Ethernet0/0i 39.840f.8011.9999.0000.2222 [110/10] via BackBoneR3, Ethernet0/0i 39.840f.8011.9999.0000.3333 [110/20] via BackBoneR3, Ethernet0/0i 39.840f.8011.9999.0000.bbbb [110/10] via BackBoneR3, Ethernet0/0


C H A P T E R 5
MPLS in the DCN



IntroductionThis section describes an architecture for converged networks that provides a framework data communications network (DCN) for a growing range of new technologies being deployed, such as Metro Ethernet, L2VPN, and L3VPN on a single foundation. A DCN is the out-of-band operations support network (OSN) that service providers use for connectivity between their Operations Support System (OSS) applications and network elements (transport, switching, routing, and so on). The OSS applications perform network surveillance, provisioning, service restoral, collection of billing data, and other applications.

This DCN architecture uses the Multiprotocol Label Switching (MPLS) technology to provide many distinct advantages to the service provider in deploying a more robust, foolproof, and secure DCN over the traditional IP packet forwarding as shown in Figure 5-1.



Chapter 5 MPLS in the DCNMPLS in the DCN: Overview

Figure 5-1 MPLS/IP in the DCN

The DCN architecture described in this section uses MPLS technology. MPLS provides many advantages to the service provider over the traditional IP packet forwarding technologies, such as deploying a DCN that is more robust and secure. The DCN architecture and related software features are described in the following sections:

• MPLS in the DCN: Overview, page 5-2

• Deploying MPLS VPNs on a DCN, page 5-16

• Configuration Examples for MPLS VPNs on a DCN, page 5-18

MPLS in the DCN: OverviewMPLS is a high-performance, enhanced packet forwarding technology that improves the performance and traffic management capabilities of Layer 2 (data link layer) and Layer 3 (network layer) of the Open System Interconnection (OSI) model. MPLS provides improved switching with more flexibility and controlled routing. Many service providers use MPLS in the main network to provide assured bandwidth and advanced Service Level Agreements (SLAs) services. Deploying MPLS cuts network costs and provides more ways for the service provider to improve network efficiency.

An MPLS virtual private network (VPN) can provide network services that enable connectivity among multiple sites on a shared infrastructure with the same access or security mechanisms that a separate private network would offer. The network is made virtually private for traffic separation using MPLS VPNs.

Service providers can use MPLS to provide VPN services from the central office (CO) to the remote OSS in the data center. This functionality has been traditionally done using IPsec tunnels often requiring a large number of VPN concentrators or firewall products.

Mobile users andTelecommuters

CentralOffice

Data center MPLS/IP

Data communicationsnetwork

CentralOffice

CentralOffice

1432

91



Figure 5-2 shows an example of MPLS VPN architecture over a DCN infrastructure.

Figure 5-2 MPLS VPN Architecture over a DCN Infrastructure

This section provides the following information about MPLS in the DCN:

• Scenarios for Service Providers Deploying MPLS VPNS in the DCN, page 5-3

• Benefits of MPLS VPNs on a DCN, page 5-12

• Supported Platforms, page 5-13

• Design Details, page 5-14

Scenarios for Service Providers Deploying MPLS VPNS in the DCNA small number of service providers have started using the MPLS VPN technology within the DCN during the last few years. Traditionally, service providers have kept their internal enterprise networks and their DCNs separate. In the early days of the DCN, service providers placed the OSS directly on the DCN, as shown Figure 5-3. The OSSs were connected to the DCN and also often connected to the enterprise network. In addition, network operations center (NOC) computers and NOC technicians were directly connected to the DCN.


CentralOffice D

Data center

MPLS/IP

1432

92

NE

CentralOffice A

NE

CentralOffice B

NE

CentralOffice C

NE

CE-1

CE-2

CE-4

CE-3

CE-5

PE-1 PE-2

PE-5 PE-4

PE-3



Figure 5-3 Classic DCN and Enterprise Deployments

Over time, some service providers have chosen to move their OSSs and the NOC technicians to the enterprise portion of the network. The service providers moved the OSSs to the enterprise network because the OSSs (see Figure 5-4) were dual homed. So the OSSs were connected to the enterprise and the DCN, but the service providers considered this to be a security risk. Moving the OSSs to the enterprise networks eliminated the dual homing. The idea was to authenticate user traffic entering the DCN with a firewall. Also, user groups and NOC technicians were required to authenticate when entering the DCN.

The two-network strategy of both an enterprise and a DCN allows the service provider to control access to the DCN. The firewall is the gatekeeper.

2317

00

X.25 X.25

Async

X.25

Metromanagement

VLAN

User groups

DCNbackbone

Internet

Metroprovisioning

SONET SDM GNE

Customer premise

Class 5 Digital loopcenter

HDSL shelf

Central officeData center

Trafficengineering

data

NOCtechnicians

Enterprisenetwork

Provisioning

MetroMetroprovisioning

Provisioning

Metroprovisioning



Figure 5-4 Migrating OSSs to an Enterprise Network

This section describes the business problems that service providers are solving with the MPLS technology, in the following sections:

• Shared Core Network, page 5-5

• Multiple DCNs, page 5-6

• Untrusted Management Traffic, page 5-9

• Enterprise User Traffic VPN, page 5-10

• Service Provider Network for Customer Data with a Management VPN for a DCN, page 5-11

Shared Core Network

Service providers implement MPLS in the DCN in ways different than is typical for an MPLS-based network. For example, in one of the first implementations for MPLS VPNs, service providers combined the enterprise network and DCN. One approach was to build a common core for the DCN and enterprise networks, but keep the distribution and access layers separate for both networks. In this shared core scenario, the core links and core routers are shared between the networks. The enterprise and DCN traffic is placed in separate VPN routing and forwarding (VRF) tables. As shown in Figure 5-5, the enterprise traffic is in its own VRF represented by blue (solid) lines. The DCN traffic is in a separate VRF represented by red (broken) lines. The service provider in this example uses dedicated provider edge (PE) aggregation routers and access routers for the DCN, and uses dedicated PE aggregation routers and access routers for enterprise traffic.

2317

01

X.25

Async

X.25 X.25

NOC technicians

User groups

Internet

Metroprovisioning

SONET/SDH GNE

SONET/SDH NE

SONET/SDH NE

Class 5 Digital loopcenter

HDSL shelf

Trafficengineering

data

Intrusion detectiondevice IDS

Data center Central office

EnterprisenetworkProvisioning

MetroprovisioningProvisioning

Metroprovisioning

DCNbackbone

Sonet/SDH NESONET/SDH NE



Figure 5-5 Shared Core Utilizing MPLS VPN

Multiple DCNs

Some service providers have multiple DCNs in their network. Sometimes, service providers have deployed separate DCNs for different functions. For example, some service providers use one DCN to monitor and provision transmission network elements. A second DCN is used for collection of billing data from Class 5 switches. A third DCN is used for the management and provisioning of Class 5 switches.

EnterpriseMPLS VPN

Central OfficeMPLS VPN

2317

02

Central Office

Central OfficeEnterprise Office

Enterprise Office

Enterprise Office

Central Office

C-PE-2

E-PE-2

E-PE-4

C-PE-4

E-PE-1

C-PE-3

C-PE-1

EnterpriseData CenterEnterprise

Data CenterEnterprise

Data CenterCentral OfficeData Center

Central OfficeData Center


E-PE-3



Figure 5-6 shows an example of multiple DCNs by application.

Figure 5-6 Multiple DCNs by Application

Some manufactures of network elements have required that their traffic be kept separate from other vendors, as shown in Figure 5-7.

2317

03

Traffic Engineering Data

Data Center

Central Office

Async

Provisioning

Class 5 DCN

X.25Class 5Monitoring

Billing DataCollection

Provisioning

Transmission DCNMonitoring

Billing DCN

HDSL Shelf

Digital Loop Carrier

SONET/SDH GNESONET/SDH GNE



Figure 5-7 Multiple DCNs by Vendor

Today, service providers want to consolidate the multiple DCNs into one DCN. In some cases, older DCN equipment no longer being supported by the manufacturer is the compelling reason to consolidate the networks. For example, vendors are getting out of the X.25 equipment market. Also, service providers no longer want to operate and maintain multiple DCNs. Maintaining multiple DCNs requires multiple support staffs, multiple redundant circuits, and multiple support contracts. The MPLS VPN solution is one method for building a common IP core and consolidating multiple DCNs into one DCN. The service provider can create discrete VRFs to isolate vendor traffic or keep applications separate.

In Figure 5-8, vendor A traffic is placed in the red VPN, and vendor B traffic is placed in the blue VPN, so there can be overlapping address space and vendor traffic will be kept separate.

2317

04

Traffic Engineering Data

Data Center

Central Office

Async

Provisioning

Vendor C DCN

Class 5

Monitoring

Provisioning

Vendor B DCNMonitoringSDH Vendor BSDH Vendor B

Provisioning

Vendor A DCNMonitoringSDH Vendor ASDH Vendor A



Figure 5-8 MPLS VPN Implementation for Vendor Traffic Separation

Untrusted Management Traffic

In next generation services such as Metro Ethernet, service providers are deploying on customer premises equipment (CPE) that is managed by the service provider. In other words, the service provider deploys an Ethernet switch on a CPE and manages the switch over a management VLAN connection from the CO, as shown in Figure 5-9. The service provider is concerned about an outsider using the CPE located at the customer premises to break into the network. So the service provider treats management data in the management VLAN as suspect and places the management data in a VPN. Also, the VPN prevents someone from plugging into the customer premises switch and breaking into the classic DCN. If a Metro Ethernet user does manage to break into the management VLAN, the user can only access the management VPN for the Metro Ethernet equipment. The intruder cannot access the classic DCN used for monitoring and provisioning traditional CO equipment such as Class 5 telephone switches, digital loop carrier systems, and other transmission gear.

Vendor A VPN Vendor B VPN

2317

05

Central Office

Central Office

Central Office

Central Office

C-PE-2

E-PE-2

E-PE-4

C-PE-4

Data CenterData CenterData Center

Central OfficeCentral OfficeCentral OfficeCentral OfficeCentral Office

Vendor AVendor AVendor A Vendor BVendor BVendor B Vendor AVendor AVendor A Vendor BVendor BVendor B

C-PE-3C-PE-3E-PE-3E-PE-3

E-PE-1E-PE-1C-PE-1C-PE-1



Figure 5-9 MPLS VPN in the DCN

Enterprise User Traffic VPN

Some service providers have built enterprise networks out to their CO to provide connectivity to the technicians and other user groups located in the CO. These service providers have two networks deployed to the CO building. The first network is for the personnel in the building, and the second network is for CO equipment. An alternative is to use the MPLS VPN solution shown in Figure 5-10.

2317

06

X.25 X.25 X.25

NOC technician

Internet

Metro Ethernetprovisioning

SONET/SDH GNE

SONET/SDH NE

SONET/SDH NE

Class 5

Async

Async

MPLS VPNfor Metro Ethernet

ManagementTraffic

MEaggregation

switch

Customerpremises

Customerpremises

Digital loopcenter

HDSL shelf

ManagementVLANs

Metro Ethernetmanagement

VLAN

Metro Ethernetmanagement

VLAN

Trafficengineering

data


EnterprisenetworkProvisioning


Data centerCentral office

Metro Ethernetprovisioning

DCNbackbone

Sonet/SDH NESONET/SDH NE



Figure 5-10 MPLS VPN for Enterprise Traffic

Service Provider Network for Customer Data with a Management VPN for a DCN

Almost all service providers have built separate DCNs. Cisco is beginning to see service providers create a management VPN on the network that provides customer services. The customers that have implemented this option have implemented an alternate access method in the event the user network becomes unstable. The alternate access may be using an existing DCN and connecting the asynchronous console access to the network elements. A second method may be to use ISDN backup access as a secondary WAN access to the DCN access router. So if the service provider lost the management VPN, the DCN access router could use the ISDN dialup to dial back into the NOC. The service provider will need to determine the number of ISDN dialup connections that the service provider would be required to support in case of a large network outage.

The concept of a service provider network connecting customer sites over a VPN and a separate management VPN is shown in Figure 5-11. Both the Customer A and Customer B sites are connected with a VPN. The customers are aggregated together on a PE dedicated to the customers. The CO access DCN routers are connected to PE aggregation routers dedicated to the DCN. Notice in Figure 5-11 that the DCN access routers have an ISDN backup connection to the data center with the OSSs.

2317

07

X.25 X.25

Async

Central officetechnicians

Enterpriseusers

X.25

MPLS VPN forenterprise traffic

NOCtechnician

DCNbackbone

Internet

Sonet SDM GNE

Class 5


Digital loopcenter

HDSL shelf

Central officeData center

Trafficengineering

data

Enterprisenetwork

Provisioning


Enterprisedata center

MPLS VPN forenterprise trafficMPLS VPN for

enterprise traffic



Figure 5-11 Service Provider Network for Customer Data with a Management VPN for a DCN

Benefits of MPLS VPNs on a DCNDeploying MPLS in the DCN offers the following advantages to service providers:

• Outstanding scalability for the DCN. MPLS VPNs easily scale while providing the same level of security and access as Layer 2 technologies. Adding, moving, or integrating COs is simplified. MPLS technology allows the service provider to quickly consolidate multiple DCNs into one DCN and maintain traffic separation.

• Easier network management. The service provider backbone DCN does not need to be reconfigured to implement a new CO; only the PE router where the CO connects to the main network needs to be added to the VRF table. Cisco IP Solution Center (ISC) Version 4.0 can be used to comprehensively manage the DCN on which the MPLS VPN is implemented.

• Quality of service (QoS) can be applied to the MPLS VPN for guaranteed bandwidth. MPLS QoS features enable the efficient use of existing network elements in the DCN to meet growing bandwidth demands. Multiple class of service (CoS) classes can be assigned to traffic on the VPNs.

Central OfficeMPLS VPN

Customer AMPLS VPN

Customer BMPLS VPN

2317

08

Central OfficeCustomer B

CO-PE: Central Office PECU-PE: Customer PE

Central Office

CO-PE-2

CU-PE-2CO-PE-4

Central OfficeCustomer B

Customer ACustomer ACentral OfficeData Center


ISDNISDN

CO-PE-3CO-PE-3CU-PE-3CU-PE-3

CU-PE-1CU-PE-1CO-PE-1CO-PE-1

CU-PE-4CU-PE-4

Customer A

ISDNISDN

ISDNISDN

ISDNISDN



With MPLS VPNs, advanced IP CoS mechanisms such as Weighted Fair Queuing (WFQ) and Weighted Random Early Detection (WRED) can be applied to VRFs. As described in the “Service Provider Network for Customer Data with a Management VPN for a DCN” section, service providers can have implemented a separate DCN for each vendor so that the vendor traffic is isolated from other vendors. The MPLS VPN solution allows the customer to create one network but meet the vendor’s DCN requirement for SLAs and traffic isolation.

• VRF monitoring using a VRF-aware IP SLAs. IP SLAs uses the Service Assurance Agent (SAA) to measure the hop-by-hop response time for the path through the MPLS network, and can be used to monitor a VRF because the IP SLAs is VRF-aware.

• Path selection using MPLS Traffic Engineering/Fast Reroute (TE/FRR) in the DCN. The MPLS TE feature allows network operations to specify routing paths through the network. This feature can also dynamically look for a route to carry a specified bandwidth traffic capacity through the network. FRR functions when a route fails. Convergence times of less than 50 msec can be achieved using FRR. Such a fast recovery prevents applications from timing out and also prevents loss of data.

• MPLS TE paths are called TE tunnels, and accomplish the following:

– Automatically ensure that the required bandwidth is reserved for the label switched path (LSP) through the network. The bandwidth requirement is provisioned and then checked by the tunnel using Resource Reservation Protocol (RSVP) to verify adequate capacity along the LSP.

– Keep their own topology map and detect a link or router fault.

– Provide operating efficiencies and flexibility.

There is flexibility in terms of routing protocols used at the CO without added overhead. MPLS VPNs greatly simplify service deployment compared to traditional IP VPNs when the number of COs or the number of routes inside the COs increase. MPLS VPNs can provide a simplified managed network without the need to provision a new IPsec tunnel every time a traffic flow is provisioned in the network, and also provide simpler deployment at the CO. MPLS VPNs also do not require translation for the private IP addresses used in the COs.

• Financial benefits: MPLS VPNs provide a robust and scalable platform for IP convergence, enabling service providers to take advantage of lower total cost of ownership, improved operation effectiveness, and improved business performance. Service providers are able to consolidate multiple DCNs into one DCN, which lowers the cost of maintaining and managing the network.

MPLS VPNs simplify the management of the network, thus reducing cost. The network at the COs also becomes more robust and requires fewer upgrades. Advanced MPLS VPN failure recovery mechanisms also reduce network downtime.

• Load distribution: MPLS can be used to distribute traffic load more effectively throughout the DCNs.

• Fault detection and correction: MPLS provides rapid mechanisms to detect and correct faults. MPLS technology has evolved to provide subsecond convergence and improved network traffic reroutes in times of network outage because of human and network errors.

Supported PlatformsA good reference source for platforms that support MPLS can be found in the MPLS VPN and Multi-Virtual Route Forwarding Support for Cisco ISR application note at the following URL: http://www.cisco.com/en/US/products/ps6557/products_white_paper0900aecd8051fbdc.shtml


http://www.cisco.com/en/US/products/ps6557/products_white_paper0900aecd8051fbdc.shtml


MPLS VPN and Multi-Virtual Route Forwarding Support for Cisco ISR

MPLS VPN and Multi-Virtual Route Forwarding Support for Cisco ISR


Design DetailsFind design suggestions for an MPLS DCN in the following sections:

• Traffic Separation, page 5-14

• Routing Information in a VRF, page 5-15

Traffic Separation

MPLS VPNs in the DCN allow service providers to differentiate traffic from separate network elements performing different functions in a converged network. In Figure 5-12, traffic is separated using VRFs shown in blue and red in the DCN.

Figure 5-12 Traffic Separation Using Blue and Red VRFs on the DCN

MPLS technology forwards packets while Border Gateway Protocol (BGP) takes care of route distribution over the network. MPLS VPN enforces traffic separation by assigning a unique VRF table to each traffic type.

The routes in the VRF are called the VPN-IPv4 routes and are kept in a table separate from the global routes. In the global routing table, PE routers store Interior Gateway Protocol (IGP) routes and associated labels distributed via Label Distribution Protocol (LDP)/Tag Distribution Protocol (TDP). In the VRFs, PE routers store VPN routes and associated labels distribution through multiprotocol internal BGP (MP-iBGP), which can run over any interior gateway protocol such as Open Shortest Path First (OSPF), Intermediate System-to-Intermediate System (IS-IS), Routing Information Protocol (RIP), and so on.

An MP-iBGP update is sent to all PE neighbors. PEs receive MP-iBGP routes and translate the VPN-IPv4 addresses to determine the VRF. The elements in a specific VPN thus do not see traffic outside the VPN to which they belong.


CentralOffice D

Data center

MPLS/IP

IGP/LDP

1432

93

NE

CentralOffice A

NE

CentralOffice B

NE

CentralOffice C

NE

CE-1

CE-2

CE-4

CE-3

CE-5

PE-1 PE-2

PE-5 PE-4

Blue traffic Red traffic

Blue MPLS VPN

Red MPLS VPN

PE-3



In Figure 5-13, the incoming interface on the PE determines the forwarding table to use to label-switch the packet.

Figure 5-13 PE Forwards Traffic into Blue and Red VRFs

Traffic forwarding within the network is based on labels. LSPs start and end at the PE routers. Because each interface on a PE router is associated with a particular VPN, a packet can enter a VPN only through that interface. Standard IP forwarding can be used between the PE and customer edge (CE) routers. The CEs can use their own routing mechanism.

MPLS VPNs use two labels to forward the data traffic. The top label forwards the traffic to the correct PE router and the label underneath indicates how the other PE should handle that incoming packet. Thus, the VPN-based traffic separation and distribution occurs without IPsec tunneling or any kind of encryption.

Routing Information in a VRF

VPN routing information is propagated through the use of VPN route target communities implemented using the BGP extended communities. VPNv4 routes are exported to and imported from VRFs in the following ways:

• Exported IPv4 routes are brought from the VRF, translated into VPN-IPv4 routes, and inserted into the MP-BGP table. When a VPN route learned from a CE router is injected into BGP, the list of route target community values is thus set from an export list of route targets associated with the VRF from which the route was learned.

• Imported VPN-IPv4 routes are brought from the MP-BGP table, translated into IPv4 routes, and inserted into the VRF. An import list of route target extended communities is thus associated with each VRF.

PEs need to know which route is intended for which VRF. Figure 5-14 shows a proposed VPN architecture in which the data center PEs import all VRF routes from the COs. Routes are differentiated using red and blue route-target commands.

1432

94

PE

Local routes

RIPOSPF

STATIC

IS-IS

ProvisionedVRFs

PE/CE IPv4 Protocol

CO DCN

MP-iBGP


Chapter 5 MPLS in the DCNDeploying MPLS VPNs on a DCN

Figure 5-14 Proposed VPN Architecture-Data Center PEs Import All VRF Routes from COs

Deploying MPLS VPNs on a DCNKey MPLS infrastructure elements to keep in mind when deploying MPLS on the service provider network are described in the following sections:

• Core Architecture, page 5-16

• Route Reflectors in an MPLS Network, page 5-17

• IPsec-Aware MPLS VPN, page 5-18

Core ArchitectureThe first step in building an MPLS VPN architecture is the design and development of the core MPLS network. The routers in the core are called Provider (P) routers and the routers on the edge are called the Provider Edge (PE) routers. The following are key elements to consider when designing the core:

• The initial reachability information exchanged between PE and P routers is achieved with loopback addresses. Cisco recommends that these addresses be assigned to identify the device in terms of its location in the network cloud. Loopback interfaces are virtual interfaces that are never shut down unless the device is completely isolated or powered off. Loopback interfaces can be set up to allow label switching to use these addresses as the endpoints of a tunnel.


CentralOffice D

Data center

MPLS/IP

IGP/LDP

NE

CentralOffice A

NE

CentralOffice B

NE

CentralOffice C

NE

CE-1

CE-2

CE-4

CE-3

CE-5

PE-1 PE-2

PE-5 PE-4

Blue traffic Red traffic

Blue MPLS VPN

Red MPLS VPN

Int eth 3/2ip vrf forwarding VPN-Redip vrf VPN-Redrd 600:61route-target export 1:63route-target import 1:60

Int eth 3/1ip vrf forwarding VPN-Blueip vrf VPN-Bluerd 500:51route-target export 1:52route-target import 1:50

Int eth 3/2ip vrf forwarding VPN-Redip vrf VPN-Redrd 600:61route-target export 1:61route-target import 1:60

Int eth 3/1ip vrf forwarding VPN-Blueip vrf VPN-Bluerd 500:51route-target export 1:51route-target import 1:50

Int Gig4/1ip vrf forwarding VPN-Blueip vrf VPN-Bluerd 500:50route-target export 1:50route-target import 1:51route-target import 1:52

Int Gig3/1ip vrf forwarding VPN-Redip vrf VPN-Redrd 600:60route-target export 1:60route-target import 1:61route-target import 1:63

PE-3

1432

95


Chapter 5 MPLS in the DCNDeploying MPLS VPNs on a DCN

Cisco recommends that loopback interfaces be defined on PE routers for a specific VPN. VPN reachability can be checked after the PE router is installed at the CO. The advantage with this approach is that the VPN reachability on the PE of the CO in question can be verified before the CO is activated on that MPLS VPN.

• IGP routing such as OSPF, RIP, and IS-IS needs to be set up among all the P and PE routers in the core network.

• Labels should be distributed using LDP. The global routing table created by IGP is used to distribute label information by P and PE routers in the MPLS cloud.

• BGP should be enabled for VRF information. BGP is used to locate the hop closest to a destination. BGP establishes the peer relation to its neighbor using TCP port 179. With iBGP, the neighbor need not be directly connected to the BGP speaker; IGP is used to achieve this.

Route Reflectors in an MPLS NetworkBGP route reflectors (RRs) are not essential for a DCN MPLS network to function. BGP routing requires all the iBGP speakers to be fully meshed. This requirement is not scalable when there are a large number of iBGP hops in the core. The RR feature is a good solution to this iBGP mesh issue. Figure 5-15 shows how RRs reduce network complexity.

Figure 5-15 Route Reflectors Reduce Network Complexity

The choice of RRs in a DCN should include the following factors:

• RR should be used when the core is handling a large amount of edge devices establishing peering relationships.

• More than one RR should be deployed for redundancy when deploying in a DCN.

1432

96

Without RR With RR

RR

RR


Chapter 5 MPLS in the DCNConfiguration Examples for MPLS VPNs on a DCN

IPsec-Aware MPLS VPNFigure 5-16 shows how IPsec tunnels can exist between the CO and the DCN PE router. The two peers can secure different kinds of data streams where each IPsec tunnel uses a separate set of traffic associations. For example, some data streams might be console traffic generated from an optical network, while other data streams might be billing data mapped to an IPsec tunnel.

Figure 5-16 IPsec-Aware MPLS VPN

IPsec sessions can be terminated on the provider edge of the MPLS/IP backbone, and each of these tunnels can be mapped into their respective MPLS VPNs. The mapping between the IPsec and the MPLS VPN can be done based on the deployment model and the policies that need to be applied.

Configuration Examples for MPLS VPNs on a DCNThis section provides the following configuration examples for the blue and red VRFs, as described in the “Traffic Separation” section on page 5-14:

• Data Center PE (PE-5)-Blue Routes Imported: Example, page 5-19

• Data Center PE (PE-4)-Red Routes Imported: Example, page 5-19

• Central Center PE (PE-1)-Blue and Red Routes Exported: Example, page 5-19

• Central Center PE (PE-2)-Blue and Red Routes Exported: Example, page 5-20

See Figure 5-12 for an example of the routes.

Central Office Data center

MPLS/IP


1432

97

Access

Leased line/Frame Relay/

ATM/DSL Dedicated Access

Internet

PE PE

Cisco Router terminatesIPSec Tunnels and Maps

Sessions into MPLS VPNs

Bi-DirectionalIPSec Session

MPLS Core

IP IPsec Session MPLS VPNs IP



Data Center PE (PE-5)-Blue Routes Imported: ExampleThe following configuration defines the VRF:

ip vrf VPN-Bluerd 500:50route-target export 1:50route-target import 1:51route-target import 1:52

The following configuration applies the VRF to the interface facing the DCN:

interface GigabitEthernet4/1description link TO PE-5 ip vrf forwarding VPN-Blueip address 10.1.2.2 255.255.255.0no ip directed-broadcastip pim sparse-modeload-interval 30negotiation autotag-switching ip

Data Center PE (PE-4)-Red Routes Imported: ExampleThe following configuration defines the VRF and the import and export communities:

ip vrf VPN-Redrd 600:60route-target export 1:60route-target import 1:61route-target import 1:62


interface GigabitEthernet3/1description link TO PE-4 ip vrf forwarding VPN-Redip address 10.1.2.1 255.255.255.0no ip directed-broadcastip pim sparse-modeload-interval 30negotiation autotag-switching ip

Central Center PE (PE-1)-Blue and Red Routes Exported: ExampleThe following configuration defines the VRF:

ip vrf VPN-Redrd 600:61route-target export 1:61route-target import 1:60

ip vrf VPN-Bluerd 500:51route-target export 1:51route-target import 1:50




interface ethernet 3/1description link TO CE-2 ip vrf forwarding VPN-Blueip address 10.1.100.2 255.255.255.0no ip directed-broadcastip pim sparse-modeload-interval 30negotiation autotag-switching ip

interface ethernet 3/2description link TO CE-1 ip vrf forwarding VPN-Redip address 10.1.100.5 255.255.255.0no ip directed-broadcastip pim sparse-modeload-interval 30negotiation autotag-switching ip

Central Center PE (PE-2)-Blue and Red Routes Exported: ExampleThe following configuration defines the VRF:

ip vrf VPN-Redrd 600:61route-target export 1:63route-target import 1:60

ip vrf VPN-Bluerd 500:51route-target export 1:52route-target import 1:50


interface ethernet 3/1description link TO CE-5 ip vrf forwarding VPN-Blueip address 10.1.100.2 255.255.255.0no ip directed-broadcastip pim sparse-modeload-interval 30negotiation autotag-switching ip

interface ethernet 3/2description TO link CE-4 ip vrf forwarding VPN-Redip address 10.1.100.5 255.255.255.0no ip directed-broadcastip pim sparse-modeload-interval 30negotiation autotag-switching ip


A
P P E N D I X A Cisco IOS X.25 Toolkit



IntroductionThis appendix describes the following Cisco IOS features that can be useful in data communications network (DCN) X.25 networks:

• Multi-PAD Support for X.25 Connections, page A-1

• Relay X.25 VC Number, page A-4

• X.25 Throughput Negotiation, page A-24

• Network Element Dial-Out Prevention, page A-26

• Modem Always On for Network Elements, page A-27

• Debugging X.25, page A-28

• Debugging LAPB, page A-29

Multi-PAD Support for X.25 ConnectionsMany network elements communicate to hosts via asynchronous X.28 interfaces for incoming and outgoing calls. In Cisco IOS X.28 implementations before the Cisco Multi-PAD Support for X.25 Connections (X.25 Multi-PAD Support) feature was introduced, Cisco routers assigned a main X.121 address to the router and differentiated between asynchronous lines using two digital subaddresses. This solution was not suitable in some service provider networks, because asynchronous X.28 lines on the same router might have different addresses. The Multi-PAD Support feature enables service providers to assign any network element on any asynchronous X.28 line its own X.121 address. The X.25 Multi-PAD Support feature elevated the Cisco router from being more than an end-user based solution to a telco solution.

A-1Cisco Network Solutions for the Telco DCN


Appendix A Cisco IOS X.25 ToolkitMulti-PAD Support for X.25 Connections

The X.25 Multi-PAD Support feature was designed for service providers that have large numbers of asynchronous network elements that are configured for packet assembler/disassembler (PAD) access. Specifically, the network elements need to be connected to the Cisco asynchronous terminal lines, and each network element is assigned its own full X.121 address.

In Figure A-1, the service provider needs to assign an X.121 address to TTY 68 and a separate individual X.121 address to TTY 69. Specifically, the network elements need to receive and initiate PAD calls with full X.121 addresses.

Figure A-1 Multi-PAD Support for X.25 Connections

With the X.25 Multi-PAD Support feature, network elements with different X.121 addresses that have the same last two digits can be connected to the same router with unique, individual addresses. Incoming PAD calls to addresses with different prefixes, but with the same last two-digit subaddress, need to be routed to different lines on the same router.

Although the Cisco IOS PAD feature has a large number of combinations, the service providers ran into the following problems with the Cisco IOS PAD capabilities prior to the X.25 Multi-PAD Support feature:

• While X.25 alias addresses assigned to an interface permit the router to simulate the behavior of multiple PAD addresses, only virtual terminal lines (vtys) are supported, not the physical asynchronous lines (TTYs, CON, or AUX) that the customer requires. In addition, X.25 alias addresses do not support subaddressing.

• The legacy PAD subaddressing feature supports reverse connections. Unfortunately, it forwards incoming calls to the same lines based on the subaddress, whether the call was destined to the interface address or the router’s host address.

• The Cisco protocol translation feature supports full X.121 addresses, but incoming calls are not possible if the line is configured using the autocommand command.

• The X.28 user emulator mode allows reverse connections to be accepted if the line is not engaged with an outgoing call. However, this mode cannot route calls with the same two-digit subaddress to two unique lines on the router. For example, addresses 1234501 and 4567801 are routed to the same line because the numbers have the same last two digits.

The X.25 Multi-PAD Support feature enables the following functionality:

• X.25 addresses can be configured on a TTY line allowing an X.25 call to be destined to and originated from the TTY line.

• X.25 addresses can be associated with a TTY rotary group, so that the rotary group address is routed to the available member TTY line, and the calls originating from the member TTY line can opt to use the rotary address as the source address.

2316

13

XOT/IPcloud

TTY 68

TTY 69X.25 over TCP/IP

X.25 connection Async connection

X25

OSS

Async

Networkelements

PAD-X.28

Router 2Router 1


Appendix A Cisco IOS X.25 ToolkitMulti-PAD Support for X.25 Connections

The X.25 Multi-PAD Support feature will behave as follows when an incoming PAD call is received by the router:

• If an incoming call’s destination address matches the X.121 address of a particular line, the call will be routed to that line. If the line is in use, the call will be cleared with Cause 9, Diag 0 (Out of order/No additional information).

• If an incoming call’s destination address matches the X.121 address of a rotary hunt group, the call will be routed to a line according to the algorithm configured for that group. If a match is found, but there are no available free lines, the call will be cleared with Cause 9, Diag 0 (Out of order/No additional information).

• If no PAD address is found, the call will be passed to other X.25 clients (for example, X.25 switch, datagram encapsulation, and so on) for further processing.

• The X.25 Multi-PAD Support feature is turned off by default.

The X.25 Multi-PAD Support feature will behave as follows when an outgoing call is placed by the network element to the router:

• If the call originates from a line that is a member of a rotary hunt group configured to be used as the source address, that rotary hunt group’s X.121 address will be applied.

• If an X.121 address is specified on the line, calls originating from the line will have that address as the source address.

• If an X.121 address is not specified for the line, but the line is a member of a rotary hunt group that has an X.121 address, calls originating from the line will have the rotary hunt group address as the source address.

• If the outgoing call algorithm finds that the X.25 Multi-PAD Support feature has not been enabled on the line, calls originating from the line will use the router (interface or host) address as the source address. The default is the current behavior.

Following is an example of the commands to assign an X.25 address to a line:

Router(config)# line 98Router(config-line)# x25 address 12345

The command syntax for the x25 rotary line configuration command that assigns an X.25 address to a rotary group is as follows:

x25 rotary group-num x121-address [calling-address [rotary | line]]

no x25 rotary group-num x121-address [calling-address [rotary | line]]

Following is an example of the commands used to assign an X.25 address to a rotary group:

Router(config)# x25 rotary 1 1111 calling-address rotaryRouter(config)# line 33Router(config-line)# x25 address 12345Router(config-line)# rotary 1 round-robin

You can view the X.121 address associated with a line using the show line x121-address EXEC command.

Router# show line x121-address

X121-Addresses Line Rotary 45678 - 1 34567 39 - 23456 34 - 12345 33 -


Appendix A Cisco IOS X.25 ToolkitRelay X.25 VC Number

You can view the X.121 address associated with a rotary hunt group using the show x28 hunt-group EXEC command:

Router# show x28 hunt-group

ID Type HG-Address TTy Address Uses status 1 RRA 45678 39 34567 0 NXTUSE 1 RRA 45678 34 23456 0 NXTUSE

33 12345 0 IDLE

The Multi-PAD Support for X.25 Connections feature module is located at the following URL: http://cisco.com/en/US/products/ps6441/products_feature_guide09186a0080530694.html#wp1075175

Relay X.25 VC NumberThe ITU-T X.25 standard states that the logical channel group number (LCGN) and the logical channel number (LCN) are only significant to the local link. When an X.25 call is switched across a link, the switched virtual circuit (SVC) number can and does change.

An example of a traditional X.25 network is shown in Figure A-2. The OSS makes a call on logical channel identifier (LCI) 1023. The LCI number is 80 between X.25 switches A and B, changes to 200 between X.25 switches B and C, and changes again to 400 between switch C and the network element.

Figure A-2 Classic X.25 LCI Switching Behavior

Cisco’s implementation of XOT follows the ITU-T X.25 standard, so the SVC number changes when switched across an IP backbone. In the case of XOT, the LCI by default changes to 1. The XOT address switching behavior is shown in Figure A-3.

Figure A-3 XOT LCI Switching Behavior

There are some DCN applications that require the same LCI number be used across the network. To provide this capability, Cisco software offers the x25 relay-vc-number interface configuration command. Figure A-4 shows how this command works to keep the LCI the same across the network.

2320

05

X.25 switch A X.25 switch B X.25 switch COSSNetworkelement

OSS makes anX.25 call on

LCI 1023Local call is

made on LCI 80Local call is


made on LCI 400

2320

06OSSNetworkelement


LCI 1023Local call is


made on LCI 400

IP cloud


http://cisco.com/en/US/products/ps6441/products_feature_guide09186a0080530694.html#wp1075175




Figure A-4 XOT Behavior with X.25 Relay Feature

The OSS makes a call on LCI 1023 and the LCI remains 1023 as it is relayed across the XOT link and the local link to the network element. The x25 relay-vc-number command relays the SVC for switched calls between XOT and the interface on which the command is configured, and preserves the SVC number as it is relayed across the network.

This section describes the Relay X.25 feature in the following sections:

• Configuring a Network Without the X.25 Relay Feature, page A-5

• Configuring a Network with the X.25 Relay Feature, page A-16

Configuring a Network Without the X.25 Relay FeatureThis section shows the configuration of a network without the x25 relay-vc-number command inserted in the configuration. Debug commands are used to verify that the LCI is different on each link. Figure A-5 shows the network configuration.

Figure A-5 Sample X.25 Network with XOT Configured

2320

07OSSNetworkelement


LCI 1023XOT relaysLCI 1023

Local callrelays LCI 1023

IP cloud

2320

08

x25 route 3178451060 interface Serial1/0x25 route 3178451061 interface Serial1/0x25 route 317816 interface Serial1/1

translate tcp 192.168.1.229 port 1060 x25 3178451060 translate tcp 192.168.1.229 port 1061 x25 3178451061 translate tcp 192.168.1.229 port 1070 x25 3178161070!x25 route 3178161060 interface Serial0/0/0x25 route 3178161061 interface Serial0/0/1x25 route 317845 interface Serial0/0/0x25 route 317816 interface Serial0/0/1

translate x25 3178451060 tcp 192.168.10.66translate x25 3178451061 tcp 192.168.10.66translate x25 3178161070 tcp 192.168.10.66

x25 route 317845 xot 192.168.11.2x25 route 317816 xot 192.168.11.2

S 0/0/0

S 0/0/1192.168.11.1 192.168.11.2 192.168.10.67 192.168.10.660/0/0

S 0/3/0 FA 0/0 FA 0/0 FA 0/02611B26513725A2851

X.25 XOT X.25 IP

2821

S 0/3/1

S 1/0

S 1/1

S 0/0

S 0/1

192.168.1.239192.168.1.229192.168.1.239192.168.1.229



The configuration for each network device is listed in the following sections:

• Router 2821 Configuration: Example, page A-6

• Router 2851 Configuration: Example, page A-6

• Router 3725A Configuration: Example, page A-7

• Router 2651XMA Configuration: Example, page A-8

Following these configuration examples, the following section shows debug x25 command output from the configured network, to track the LCI numbers that are used to transmit data packets across the network:

• Debug Command Traces Without the X.25 Relay Feature Enabled, page A-8

Router 2821 Configuration: Example

Following is the configuration for the router labeled 2821 in Figure A-5.

x25 routing!interface Loopback0 ip address 192.168.34.1 255.255.255.192!interface GigabitEthernet0/1 ip address 192.168.1.239 255.255.255.0 duplex auto speed auto!interface Serial0/0/0 description RS232 to 2851 0/3/0 no ip address encapsulation x25 x25 address 4085272368!interface Serial0/0/1 description rs232 to 2851 0/3/1 no ip address encapsulation x25 x25 address 4085272361 !translate tcp 192.168.34.60 port 1060 x25 3178161060translate tcp 192.168.34.61 port 1061 x25 3178161061translate tcp 192.168.34.60 port 1070 x25 3178451070translate tcp 192.168.1.229 port 1060 x25 3178451060translate tcp 192.168.1.229 port 1061 x25 3178451061translate tcp 192.168.1.229 port 1070 x25 3178161070!x25 route 3178161060 interface Serial0/0/0x25 route 3178161061 interface Serial0/0/1x25 route 317845 interface Serial0/0/0x25 route 317816 interface Serial0/0/1

Router 2851 Configuration: Example

The following examples show the software version being used and the configuration for the router labeled 2851 in Figure A-5. A connection is made between serial interface 0/3/0 and serial interface 0/3/1. The X.25 packets are routed to router 3725A via XOT at IP address 192.168.11.2.



Software Version2851A# show version

Cisco IOS Software, 2800 Software (C2800NM-IPBASEK9-M), Version 12.4(15)T1, REL)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2007 by Cisco Systems, Inc.Compiled Wed 18-Jul-07 06:21 by prod_rel_team

ROM: System Bootstrap, Version 12.3(8r)T7, RELEASE SOFTWARE (fc1)

2851A uptime is 1 day, 7 hours, 16 minutesSystem returned to ROM by power-onSystem image file is "flash:c2800nm"

Configuration Commandsx25 routing!interface Serial0/3/0 description rs232 to 2821 0/0/0 no ip address encapsulation x25 dce x25 address 200910 clock rate 19200!interface Serial0/3/1 description rs232 to 2821 0/0/1 no ip address encapsulation x25 dce clock rate 19200!route 317845 xot 192.168.11.2x25 route 317816 xot 192.168.11.2

Router 3725A Configuration: Example

Following is the configuration for the router labeled 3725A in Figure A-5.

x25 routing!interface FastEthernet0/0 ip address 192.168.11.2 255.255.255.192 no ip mroute-cache speed auto half-duplex!interface Serial1/0 description rs232 to 26451xma serial 0/0 no ip address encapsulation x25 dce no ip mroute-cache x25 address 4085272000 clock rate 19200!interface Serial1/1 description 449 interface no ip address encapsulation x25 dce no ip mroute-cache x25 address 4085273000 no ignore local-loopback



clock rate 56000!!translate tcp 192.168.11.3 port 1060 x25 3178451060translate tcp 192.168.11.3 port 1061 x25 3178451061


Router 2651XMA Configuration: Example

Following is the configuration for the router labeled 2651XMA in Figure A-5.

x25 routing!!!interface FastEthernet0/0 ip address 192.168.10.67 255.255.255.192 speed auto half-duplex clns router iso-igrp backbone tarp enable!interface Serial0/0 description rs232 to 3725A serial 1/0 no ip address encapsulation x25!interface Serial0/1 description rs449 to 3725A serial 1/1 no ip address encapsulation x25!translate x25 3178451060 tcp 192.168.10.66translate x25 3178451061 tcp 192.168.10.66translate x25 3178161070 tcp 192.168.10.66!

Debug Command Traces Without the X.25 Relay Feature Enabled

This section describes the output of the debug x25 command for a network without the x25 relay-vc-number command in the configuration. Only output for the routers labeled 2851 and 3725A are shown, because these two routers show the LCI changes.

Trace Output for Router 2851 Without X.25 Relay: Example

• The following messages are seen when the debug x25 command is first enabled:

X.25 packet debugging is onX.25 packet dump debugging is onX.25 packet dump is enabled for hex and ascii formats

• Use the show debug command to display the trace output.

• Here is what to look for in the following output example for router 2851:



– Debug trace reports begin with the date and time the debugging is occurring. On the first line of the trace output, the date and time are followed by the interface type, which for this trace is serial interface 0/3/1. The I following X.25 (shown in bold text for purpose of example) indicates incoming packets. If the I was instead an O, the packet would be outgoing on the interface. The Call report indicates the calls is coming in on LCI 1024.

– On the second line, the call is from X.121 address 4085272361, which is the address that was assigned to serial interface 0/0/1 on router 2821. The call is going to X.121 address 3178161070. The source X.121 address is assigned to the router interface with the x25 address command.

2851# show debug

*Aug 17 19:34:30.854: Serial0/3/1: X.25 I R1 Call (19) 8 lci 1024*Aug 17 19:34:30.854: From (10): 4085272361 To (10): 3178161070*Aug 17 19:34:30.854: Facilities: (0)*Aug 17 19:34:30.854: Call User Data (4): 0x01000000 (pad) 0: 14000B AA317816 10704085 ...*1x..p@. 11: 27236100 01000000 '#a.....

The following output shows the trace for router 2851 placing an XOT call to IP address 192.168.11.2, port 1998, from IP address 192.168.11.1, port 16396. On the first line, the date and time are followed by a trace of the XOT call to IP address 192.168.11.2, port 1998 from IP address 192.168.11.1, port 16396. The O (shown in bold text for purpose of example) indicates the call is outbound from the router. The call is placed on LCI 1.

*Aug 17 19:34:30.858: [192.168.11.2,1998/192.168.11.1,16396]: XOT O P2 Call (25) 8 lci 1*Aug 17 19:34:30.858: From (10): 4085272361 To (10): 3178161070*Aug 17 19:34:30.858: Facilities: (6)*Aug 17 19:34:30.858: Packet sizes: 128 128*Aug 17 19:34:30.858: Window sizes: 2 2*Aug 17 19:34:30.858: Call User Data (4): 0x01000000 (pad) 0: 10010BAA 31781610 ...*1x.. 8: 70408527 23610642 07074302 02010000 p@.'#a.B..C..... 24: 00

The following output traces the call confirmation received from router 3725A for the XOT connection on LCI 1. The I (shown in bold text for purpose of example) indicates the packet is incoming.

. . .*Aug 17 19:34:30.874: [192.168.11.2,1998/192.168.11.1,16396]: XOT I P2 Call Confirm (11) 8 lci 1*Aug 17 19:34:30.874: From (0): To (0): *Aug 17 19:34:30.874: Facilities: (6)*Aug 17 19:34:30.874: Packet sizes: 128 128*Aug 17 19:34:30.874: Window sizes: 2 2 0: 10010F 00064207 07430202 .....B..C.. 11:

The following output shows the Call Confirm request packet for the X.25 connection being sent by router 2851 to router 2821 on LCI 1024. The O (shown in bold text for purpose of example) indicates the packet is outbound from the router.

*Aug 17 19:34:30.874: Serial0/3/1: X.25 O R1 Call Confirm (5) 8 lci 1024*Aug 17 19:34:30.874: From (0): To (0): *Aug 17 19:34:30.874: Facilities: (0) 0: 14000F 0000



The following output shows data being transferred across the link (display truncated for easier readability).

. . .*Aug 17 19:34:30.874: [192.168.11.2,1998/192.168.11.1,16396]: XOT I D1 Data (4) Q 8 lci 1 PS 0 PR 0 0: 900100 04 .... *Aug 17 19:34:30.874: Serial0/3/1: X.25 O D1 Data (4) Q 8 lci 1024 PS 0 PR 0 0: 940000 04 .... ! Indicates XOT is trying to make a connection*Aug 17 19:34:30.878: [192.168.11.2,1998/192.168.11.1,16396]: XOT I D1 Data (28) 8 lci 1 PS 1 PR 0 0: 100102 54727969 6E672031 ...Trying 1 11: 39322E31 36382E31 302E3636 202E2E2E 92.168.10.66 ... 27: 20 *Aug 17 19:34:30.878: Serial0/3/1: X.25 O D1 Data (28) 8 lci 1024 PS 1 PR 0 0: 140002 54727969 6E672031 ...Trying 1 11: 39322E31 36382E31 302E3636 202E2E2E 92.168.10.66 ... 27: 20 *Aug 17 19:34:30.906: Serial0/3/1: X.25 I D1 Data (48) Q 8 lci 1024 PS 0 PR 0 0: 940000 00010102 01030204 ........... 11: 01050006 00070408 0009000A 000B0E0C ................ 27: 000D000E 000F0010 7F111512 12130014 ................ 43: 00150016 00 ..... *Aug 17 19:34:30.906: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 Data (48) Q 8 lci 1 PS 0 PR 0 0: 900100 00010102 01030204 ........... 11: 01050006 00070408 0009000A 000B0E0C ................ 27: 000D000E 000F0010 7F111512 12130014 ................ 43: 00150016 00 ..... *Aug 17 19:34:30.910: Serial0/3/1: X.25 I D1 RR (3) 8 lci 1024 PR 1 0: 140021 ..! *Aug 17 19:34:30.910: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 RR (3) 8 lci 1 PR 1 0: 100121 ..! *Aug 17 19:34:30.914: Serial0/3/1: X.25 I D1 RR (3) 8 lci 1024 PR 2 0: 140041 ..A *Aug 17 19:34:30.914: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 RR (3) 8 lci 1 PR 2 0: 100141 ..A *Aug 17 19:34:30.922: [192.168.11.2,1998/192.168.11.1,16396]: XOT I D1 Data (9) 8 lci 1 PS 2 PR 0! Connection is successful 0: 100104 4F70656E 0D0A ...Open.. *Aug 17 19:34:30.922: Serial0/3/1: X.25 O D1 Data (9) 8 lci 1024 PS 2 PR 0 0: 140004 4F70656E 0D0A ...Open.. *Aug 17 19:34:30.934: Serial0/3/1: X.25 I D1 RR (3) 8 lci 1024 PR 3 0: 140061 ..a *Aug 17 19:34:30.934: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 RR (3) 8 lci 1 PR 3 0: 100161 ..a *Aug 17 19:34:30.986: [192.168.11.2,1998/192.168.11.1,16396]: XOT I D1 Data (6) Q 8 lci 1 PS 3 PR 0 0: 900106 060200 ...... *Aug 17 19:34:30.986: Serial0/3/1: X.25 O D1 Data (6) Q 8 lci 1024 PS 3 PR 0 0: 940006 060200 ...... *Aug 17 19:34:30.990: [192.168.11.2,1998/192.168.11.1,16396]: XOT I D1 Data (12) Q 8 lci 1 PS 4 PR 0 0: 900108 06020004 010F0007 ........... 11: 15 . *Aug 17 19:34:30.990: Serial0/3/1: X.25 O D1 Data (12) Q 8 lci 1024 PS 4 PR 0 0: 940008 06020004 010F0007 ........... 11: 15 . *Aug 17 19:34:30.990: [192.168.11.2,1998/192.168.11.1,16396]: XOT I D1 RR (3) 8 lci 1 PR 1 0: 100121 ..! *Aug 17 19:34:30.990: Serial0/3/1: X.25 O D1 RR (3) 8 lci 1024 PR 1 0: 140021 ..!



*Aug 17 19:34:30.998: Serial0/3/1: X.25 I D1 Data (6) Q 8 lci 1024 PS 1 PR 3 0: 940062 000200 ..b... *Aug 17 19:34:31.002: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 Data (6) Q 8 lci 1 PS 1 PR 3 0: 900162 000200 ..b... *Aug 17 19:34:31.002: Serial0/3/1: X.25 I D1 RR (3) 8 lci 1024 PR 4 0: 140081 ... *Aug 17 19:34:31.002: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 RR (3) 8 lci 1 PR 4 0: 100181 ... *Aug 17 19:34:31.006: [192.168.11.2,1998/192.168.11.1,16396]: XOT I D1 RR (3) 8 lci 1 PR 2 0: 100141 ..A *Aug 17 19:34:31.006: Serial0/3/1: X.25 O D1 RR (3) 8 lci 1024 PR 2 0: 140041 ..A *Aug 17 19:34:31.018: [192.168.11.2,1998/192.168.11.1,16396]: XOT I D1 Data (45) 8 lci 1 PS 5 PR 2! Login name and password are entered 0: 10014A 0D0A0D0A 55736572 ..J....User 11: 20416363 65737320 56657269 66696361 Access Verifica 27: 74696F6E 0D0A0D0A 50617373 776F7264 tion....Password 43: 3A20 : *Aug 17 19:34:31.018: Serial0/3/1: X.25 O D1 Data (45) 8 lci 1024 PS 5 PR 2 0: 14004A 0D0A0D0A 55736572 ..J....User 11: 20416363 65737320 56657269 66696361 Access Verifica 27: 74696F6E 0D0A0D0A 50617373 776F7264 tion....Password 43: 3A20 : *Aug 17 19:34:31.106: Serial0/3/1: X.25 I D1 Data (12) Q 8 lci 1024 PS 2 PR 4 0: 940084 00020004 010F0007 ........... 11: 15 . *Aug 17 19:34:31.106: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 Data (12) Q 8 lci 1 PS 2 PR 4 0: 900184 00020004 010F0007 ........... 11: 15 . *Aug 17 19:34:31.110: Serial0/3/1: X.25 I D1 RR (3) 8 lci 1024 PR 5 0: 1400A1 ..! *Aug 17 19:34:31.110: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 RR (3) 8 lci 1 PR 5 0: 1001A1 ..! *Aug 17 19:34:31.114: Serial0/3/1: X.25 I D1 RR (3) 8 lci 1024 PR 6 0: 1400C1 ..A *Aug 17 19:34:31.114: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 RR (3) 8 lci 1 PR 6 0: 1001C1 ..A *Aug 17 19:34:31.114: [192.168.11.2,1998/192.168.11.1,16396]: XOT I D1 RR (3) 8 lci 1 PR 3 0: 100161 ..a *Aug 17 19:34:31.114: Serial0/3/1: X.25 O D1 RR (3) 8 lci 1024 PR 3 0: 140061 ..a *Aug 17 19:34:32.590: Serial0/3/1: X.25 I D1 Data (4) 8 lci 1024 PS 3 PR 6 0: 1400C6 63 ..Fc *Aug 17 19:34:32.590: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 Data (4) 8 lci 1 PS 3 PR 6 0: 1001C6 63 ..Fc *Aug 17 19:34:32.594: [192.168.11.2,1998/192.168.11.1,16396]: XOT I D1 RR (3) 8 lci 1 PR 4 0: 100181 ... *Aug 17 19:34:32.598: Serial0/3/1: X.25 O D1 RR (3) 8 lci 1024 PR 4 0: 140081 ... *Aug 17 19:34:32.790: Serial0/3/1: X.25 I D1 Data (4) 8 lci 1024 PS 4 PR 6! Packets are sent across the XOT connection, noted by I for incoming and O for outgoing. 0: 1400C8 69 ..Hi *Aug 17 19:34:32.790: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 Data (4) 8 lci 1 PS 4 PR 6 0: 1001C8 69 ..Hi *Aug 17 19:34:32.794: [192.168.11.2,1998/192.168.11.1,16396]: XOT I D1 RR (3) 8 lci 1 PR 5 0: 1001A1 ..! *Aug 17 19:34:32.794: Serial0/3/1: X.25 O D1 RR (3) 8 lci 1024 PR 5 0: 1400A1 ..!



*Aug 17 19:34:32.990: Serial0/3/1: X.25 I D1 Data (4) 8 lci 1024 PS 5 PR 6 0: 1400CA 73 ..Js *Aug 17 19:34:32.990: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 Data (4) 8 lci 1 PS 5 PR 6 0: 1001CA 73 ..Js *Aug 17 19:34:32.994: [192.168.11.2,1998/192.168.11.1,16396]: XOT I D1 RR (3) 8 lci 1 PR 6 0: 1001C1 ..A *Aug 17 19:34:32.994: Serial0/3/1: X.25 O D1 RR (3) 8 lci 1024 PR 6 0: 1400C1 ..A *Aug 17 19:34:33.190: Serial0/3/1: X.25 I D1 Data (5) 8 lci 1024 PS 6 PR 6 0: 1400CC 636F ..Lco *Aug 17 19:34:33.190: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 Data (5) 8 lci 1 PS 6 PR 6 0: 1001CC 636F ..Lco *Aug 17 19:34:33.194: [192.168.11.2,1998/192.168.11.1,16396]: XOT I D1 RR (3) 8 lci 1 PR 7 0: 1001E1 ..a *Aug 17 19:34:33.194: Serial0/3/1: X.25 O D1 RR (3) 8 lci 1024 PR 7 0: 1400E1 ..a *Aug 17 19:34:33.462: Serial0/3/1: X.25 I D1 Data (4) 8 lci 1024 PS 7 PR 6 0: 1400CE 0D ..N. *Aug 17 19:34:33.462: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 Data (4) 8 lci 1 PS 7 PR 6 0: 1001CE 0D ..N. . . .*Aug 17 19:34:52.618: Serial0/3/1: X.25 O D1 Data (5) 8 lci 1024 PS 3 PR 5 0: 1400A6 0D0A ..&.. *Aug 17 19:34:52.626: Serial0/3/1: X.25 I D1 RR (3) 8 lci 1024 PR 4 0: 140081 ... *Aug 17 19:34:52.626: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 RR (3) 8 lci 1 PR 4 0: 100181 ... *Aug 17 19:34:52.734: [192.168.11.2,1998/192.168.11.1,16396]: XOT I D1 Data (4) Q 8 lci 1 PS 4 PR 5 0: 9001A8 01 ..(. *Aug 17 19:34:52.734: Serial0/3/1: X.25 O D1 Data (4) Q 8 lci 1024 PS 4 PR 5 0: 9400A8 01 ..(. *Aug 17 19:34:52.746: Serial0/3/1: X.25 I D1 RR (3) 8 lci 1024 PR 5 0: 1400A1 ..! *Aug 17 19:34:52.746: [192.168.11.2,1998/192.168.11.1,16396]: XOT O D1 RR (3) 8 lci 1 PR 5 0: 1001A1 ..!

Router 2851 Receives Call Clear Request Without X.25 Relay: Example

The following output shows router 2851 receiving a Call Clear request packet on LCI 1024. In the first line following the date and time, the interface is identified as serial interface 0/3/1, the packet type is I for inbound from the router, and the Call Clear request is for LCI 1024.

*Aug 17 19:34:52.750: Serial0/3/1: X.25 I R1 Clear (5) 8 lci 1024*Aug 17 19:34:52.750: Cause 0, Diag 0 (DTE originated/No additional information) 0: 140013 0000 .....

The following output shows the Call Clear request was sent across the XOT connection between IP address 192.168.11.2, port 1998 and IP address 192.168.11.1, port 16396:

*Aug 17 19:34:52.750: [192.168.11.2,1998/192.168.11.1,16396]: XOT O P4 Clear (5) 8 lci 1*Aug 17 19:34:52.750: Cause 0, Diag 0 (DTE originated/No additional information) 0: 100113 0000 .....

The following output shows the Call Clear request packet confirmed on LCI 1:

*Aug 17 19:34:52.758: [192.168.11.2,1998/192.168.11.1,16396]: XOT I P6 Clear Confirm (3) 8 lci 1 0: 100117 ...



The following output shows the Clear Confirmed response being sent out serial interface 0/3/1 on LCI 1024 to router 2821:

*Aug 17 19:34:52.758: Serial0/3/1: X.25 O R1 Clear Confirm (3) 8 lci 1024 0: 140017 ...

Trace Output for Router 3725A Without X.25 Relay: Example

This section describes the trace output for router 2851 router as it places an XOT call to router 3725A (see Figure A-5).




• Here is what to look for in the following output example for router 3725A:

– Debug trace reports begin with the date and time the debugging is occurring. On the first line of the trace output, the date and time are followed by the interface, which is an XOT call to IP address 192.168.11.2, port 1998 from IP address 192.168.11, port 16396. The I following the XOT indicates this call is inbound from the router. The call is placed on LCI 1.

3725A# show debug

*Mar 1 07:35:32.766: [192.168.11.1,16396/192.168.11.2,1998]: XOT I P/Inactive Call (25) 8 lci 1*Mar 1 07:35:32.766: From (10): 4085272361 To (10): 3178161070*Mar 1 07:35:32.766: Facilities: (6)*Mar 1 07:35:32.766: Packet sizes: 128 128*Mar 1 07:35:32.766: Window sizes: 2 2*Mar 1 07:35:32.766: Call User Data (4): 0x01000000 (pad) 0: 10010B AA317816 10704085 ...*1x..p@. 11: 27236106 42070743 02020100 0000 '#a.B..C......

Placing a Call from Router 3725A to Router 2651XMA Without X.25 Relay: Example

This section describes the output when router 3725A places a call to router 2651XMA.

• In the following example:

– Data following the date and time lists the interface as serial 1/1. The O following X.25 (shown in bold text for purpose of example) indicates the packets are outgoing. The call is placed on LCI 1.

– Data on the second line indicates the call is from X.121 address 4085272361, which is the address that was assigned to serial interface 0/0/1 on router 2821. The call is going to X.121 address 3178161070. X.121 addresses are assigned with the x25 address command.

*Mar 1 07:35:32.766: Serial1/1: X.25 O R1 Call (19) 8 lci 1*Mar 1 07:35:32.766: From (10): 4085272361 To (10): 3178161070*Mar 1 07:35:32.770: Facilities: (0)*Mar 1 07:35:32.770: Call User Data (4): 0x01000000 (pad) 0: 10010BAA 31781610 ...*1x.. 8: 70408527 23610001 000000 p@.'#a.....

In the following output, the Call Confirm request packet is received on serial 1/1 on LCI 1. The packet is sent via router 2651XMA:

*Mar 1 07:35:32.778: Serial1/1: X.25 I R1 Call Confirm (3) 8 lci 1 0: 10010F



The following output indicates the Call Confirm packet is sent across the XOT connection on LCI 1 by router 3725A:

. . .*Mar 1 07:35:32.778: [192.168.11.1,16396/192.168.11.2,1998]: XOT O P3 Call Confirm (11) 8 lci 1*Mar 1 07:35:32.778: From (0): To (0): *Mar 1 07:35:32.778: Facilities: (6)*Mar 1 07:35:32.778: Packet sizes: 128 128*Mar 1 07:35:32.778: Window sizes: 2 2 0: 10010F 00064207 07430202 .....B..C.. 11:

The following output shows data being sent across the XOT link on LCI 1. The I in the output indicates incoming packets; O indicates outgoing packets. The display has been truncated for easier readability.

*Mar 1 07:35:32.778: Serial1/1: X.25 I D1 Data (4) Q 8 lci 1 PS 0 PR 0 0: 900100 04 .... *Mar 1 07:35:32.778: [192.168.11.1,16396/192.168.11.2,1998]: XOT O D1 Data (4) Q 8 lci 1 PS 0 PR 0 0: 900100 04 .... *Mar 1 07:35:32.782: Serial1/1: X.25 I D1 Data (28) 8 lci 1 PS 1 PR 0 0: 100102 54727969 6E672031 ...Trying 1 11: 39322E31 36382E31 302E3636 202E2E2E 92.168.10.66 ... 27: 20 *Mar 1 07:35:32.786: [192.168.11.1,16396/192.168.11.2,1998]: XOT O D1 Data (28) 8 lci 1 PS 1 PR 0 0: 100102 54727969 6E672031 ...Trying 1 11: 39322E31 36382E31 302E3636 202E2E2E 92.168.10.66 ... 27: 20 *Mar 1 07:35:32.814: [192.168.11.1,16396/192.168.11.2,1998]: XOT I D1 Data (48) Q 8 lci 1 PS 0 PR 0 0: 900100 00010102 01030204 ........... 11: 01050006 00070408 0009000A 000B0E0C ................ 27: 000D000E 000F0010 7F111512 12130014 ................ 43: 00150016 00 ..... *Mar 1 07:35:32.814: Serial1/1: X.25 O D1 Data (48) Q 8 lci 1 PS 0 PR 0 0: 900100 00010102 01030204 ........... 11: 01050006 00070408 0009000A 000B0E0C ................ 27: 000D000E 000F0010 7F111512 12130014 ................ 43: 00150016 00 ..... *Mar 1 07:35:32.818: [192.168.11.1,16396/192.168.11.2,1998]: XOT I D1 RR (3) 8 lci 1 PR 1 0: 100121 ..! *Mar 1 07:35:32.818: Serial1/1: X.25 O D1 RR (3) 8 lci 1 PR 1 0: 100121 ..! *Mar 1 07:35:32.822: [192.168.11.1,16396/192.168.11.2,1998]: XOT I D1 RR (3) 8 lci 1 PR 2 0: 100141 ..A *Mar 1 07:35:32.822: Serial1/1: X.25 O D1 RR (3) 8 lci 1 PR 2 0: 100141 ..A *Mar 1 07:35:32.830: Serial1/1: X.25 I D1 Data (9) 8 lci 1 PS 2 PR 0 0: 100104 4F70656E 0D0A ...Open.. *Mar 1 07:35:32.830: [192.168.11.1,16396/192.168.11.2,1998]: XOT O D1 Data (9) 8 lci 1 PS 2 PR 0 0: 100104 4F70656E 0D0A ...Open.. *Mar 1 07:35:32.842: [192.168.11.1,16396/192.168.11.2,1998]: XOT I D1 RR (3) 8 lci 1 PR 3 0: 100161 ..a *Mar 1 07:35:32.842: Serial1/1: X.25 O D1 RR (3) 8 lci 1 PR 3 0: 100161 ..a *Mar 1 07:35:32.894: Serial1/1: X.25 I D1 Data (6) Q 8 lci 1 PS 3 PR 0 0: 900106 060200 ...... *Mar 1 07:35:32.894: [192.168.11.1,16396/192.168.11.2,1998]: XOT O D1 Data (6) Q 8 lci 1 PS 3 PR 0 0: 900106 060200 ...... *Mar 1 07:35:32.898: Serial1/1: X.25 I D1 Data (12) Q 8 lci 1 PS 4 PR 0



0: 900108 06020004 010F0007 ........... 11: 15 . *Mar 1 07:35:32.898: [192.168.11.1,16396/192.168.11.2,1998]: XOT O D1 Data (12) Q 8 lci 1 PS 4 PR 0 0: 900108 06020004 010F0007 ........... 11: 15 . . . .*Mar 1 07:35:54.382: [192.168.11.1,16396/192.168.11.2,1998]: XOT O D1 RR (3) 8 lci 1 PR 4 0: 100181 ... *Mar 1 07:35:54.386: Serial1/1: X.25 I D1 Data (4) 8 lci 1 PS 2 PR 4 0: 100184 74 ...t *Mar 1 07:35:54.386: [192.168.11.1,16396/192.168.11.2,1998]: XOT O D1 Data (4) 8 lci 1 PS 2 PR 4 0: 100184 74 ...t *Mar 1 07:35:54.398: [192.168.11.1,16396/192.168.11.2,1998]: XOT I D1 RR (3) 8 lci 1 PR 3 0: 100161 ..a *Mar 1 07:35:54.398: Serial1/1: X.25 O D1 RR (3) 8 lci 1 PR 3 0: 100161 ..a *Mar 1 07:35:54.510: [192.168.11.1,16396/192.168.11.2,1998]: XOT I D1 Data (4) 8 lci 1 PS 4 PR 3 0: 100168 0D ..h. *Mar 1 07:35:54.510: Serial1/1: X.25 O D1 Data (4) 8 lci 1 PS 4 PR 3 0: 100168 0D ..h. *Mar 1 07:35:54.514: Serial1/1: X.25 I D1 RR (3) 8 lci 1 PR 5 0: 1001A1 ..! *Mar 1 07:35:54.514: [192.168.11.1,16396/192.168.11.2,1998]: XOT O D1 RR (3) 8 lci 1 PR 5 0: 1001A1 ..! *Mar 1 07:35:54.522: Serial1/1: X.25 I D1 Data (5) 8 lci 1 PS 3 PR 5 0: 1001A6 0D0A ..&.. *Mar 1 07:35:54.522: [192.168.11.1,16396/192.168.11.2,1998]: XOT O D1 Data (5) 8 lci 1 PS 3 PR 5 0: 1001A6 0D0A ..&.. *Mar 1 07:35:54.534: [192.168.11.1,16396/192.168.11.2,1998]: XOT I D1 RR (3) 8 lci 1 PR 4 0: 100181 ... *Mar 1 07:35:54.534: Serial1/1: X.25 O D1 RR (3) 8 lci 1 PR 4 0: 100181 ... *Mar 1 07:35:54.638: Serial1/1: X.25 I D1 Data (4) Q 8 lci 1 PS 4 PR 5 0: 9001A8 01 ..(. *Mar 1 07:35:54.638: [192.168.11.1,16396/192.168.11.2,1998]: XOT O D1 Data (4) Q 8 lci 1 PS 4 PR 5 0: 9001A8 01 ..(. *Mar 1 07:35:54.650: [192.168.11.1,16396/192.168.11.2,1998]: XOT I D1 RR (3) 8 lci 1 PR 5 0: 1001A1 ..! *Mar 1 07:35:54.650: Serial1/1: X.25 O D1 RR (3) 8 lci 1 PR 5 0: 1001A1 ..!

Router 2851 Receives Call Clear Confirmation Packet Without X.25 Relay: Example

In the following examples, the LCI on which the Call Clear request packets are transmitted has changed to LCI 1 from LCI 1024. The Call Clear request packet is received from router 2851 across the XOT link.

*Mar 1 07:35:54.654: [192.168.11.1,16396/192.168.11.2,1998]: XOT I P4 Clear (5) 8 lci 1*Mar 1 07:35:54.654: Cause 0, Diag 0 (DTE originated/No additional information) 0: 100113 0000 .....

The Call Clear request packet is sent across LCI 1 to router 2651XMA:

*Mar 1 07:35:54.654: Serial1/1: X.25 O R1 Clear (5) 8 lci 1*Mar 1 07:35:54.654: Cause 0, Diag 0 (DTE originated/No additional information) 0: 100113 0000



The Call Clear confirmation packet is received by router 2651A:

. . .*Mar 1 07:35:54.662: Serial1/1: X.25 I R1 Clear Confirm (3) 8 lci 1 0: 100117 ...

The Call Clear confirmation packet is sent to router 2851:

. . .*Mar 1 07:35:54.662: <detached>: XOT O P7 Clear Confirm (3) 8 lci 1 0: 100117 ... 3725A#

Configuring a Network with the X.25 Relay FeatureThe following sections describe how to insert the x25 relay vc-number interface command into the configuration so a network can relay the LCI across the XOT connection intact.

• Configuring X.25 Relay on Router 2851, page A-16

• Router 2851 with X.25 Relay Configured: Example, page A-17

• Configuring X.25 Relay on Router 3725A, page A-17

Following the configurations, the following section shows debug x25 command output from the configured network is shown, to track the LCI numbers that are used to transmit data packets:

• Debug Command Traces with the X.25 Relay Feature Enabled, page A-18

Configuring X.25 Relay on Router 2851

The steps for this configuration are performed on router 2851 in Figure A-5. The x25 relay vc-number command is interface-specific and is implemented on serial interface 0/3/1.


2851# config terminalEnter configuration commands, one per line. End with CNTL/Z.

Step 2 Begin interface configuration mode on serial interface 0/3/1:

2851(config)# interface serial 0/3/1

Step 3 Enter the command to relay the LCI:

2851(config-if)# x25 relay-vc-number

Step 4 Shut down the interface to make the change takes effect:

2851(config-if)# shutdown

Step 5 Re-enable the interface:

2851(config-if)# no shutdown2851(config-if)# exit



Router 2851 with X.25 Relay Configured: Example

Following are the configuration commands for router 2851 with the x25 relay-vc-number command included (shown in bold text for purpose of example):

x25 routing

interface GigabitEthernet0/0 description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$ ip address 192.168.11.1 255.255.255.192 duplex auto speed auto!interface GigabitEthernet0/1 ip address 192.168.1.238 255.255.255.0 duplex auto speed auto!interface Serial0/3/0 description rs232 to 2821 0/0/0 no ip address encapsulation x25 dce x25 address 200910 x25 relay-vc-number clock rate 19200!interface Serial0/3/1 description rs232 to 2821 0/0/1 no ip address encapsulation x25 dce shutdown x25 relay-vc-number clock rate 19200!!translate x25 3178161061 tcp 192.168.11.1translate x25 3178161060 tcp 192.168.11.2

Configuring X.25 Relay on Router 3725A

The steps for the following configuration are performed on router 3725A in Figure A-5. The x25 relay vc-number command is interface-specific and is implemented on serial interface 1/0.


3725A# config terminalEnter configuration commands, one per line. End with CNTL/Z.

Step 2 Begin interface configuration mode on serial interface 1/0:

3725A#(config)# interface serial 1/0

Step 3 Shut down the interface, to make sure the change takes effect:

3725A#(config-if)# shutdown

Wait for the “changed state to down” message that indicates the shut down is complete.

Step 4 Enter the command to relay the LCI:

3725A#(config-if)# x25 relay-vc-number



Step 5 Re-enable the interface:

3725A#(config-if)# no shutdown3725A#(config-if)# exit

Debug Command Traces with the X.25 Relay Feature Enabled

This section describes the output of the debug x25 command for a network with the x25 relay-vc-number command inserted in the configuration. Only output for the routers labeled 2851 and 3725A are shown, because these two routers show the LCI changes.

Trace Output for Router 2851 with X.25 Relay: Example




• Here is what to look for in the debug x25 output example shown below for router 2851:

– Debug trace reports begin with the date and time the debugging is occurring. On the first line of the trace output, the date and time are followed by the interface type, which for this run is serial interface 0/3/0. The I following X.25 (shown in bold text for purpose of example) indicates incoming packets. If the I was instead an O, the packet would be outgoing on the interface. The Call report indicates the calls is coming in on LCI 800.

– On the second line, the call is from X.121 address 4085272368, which is the address that was assigned to serial interface 0/0/1 on router 2821. The call is going to X.121 address 3178161070. X.121 addresses are assigned with the x25 address command.

2851# show debug

*Aug 17 19:50:01.602: Serial0/3/0: X.25 I R1 Call (19) 8 lci 800*Aug 17 19:50:01.602: From (10): 4085272368 To (10): 3178161070*Aug 17 19:50:01.602: Facilities: (0)*Aug 17 19:50:01.602: Call User Data (4): 0x01000000 (pad) 0: 13200B AA317816 10704085 . .*1x..p@. 11: 27236800 01000000 '#h.....

The following output shows router 2851 placing a call over the XOT link to IP address 192.168.11.2, port 1998 from IP address 192.168.11.1, port 16511. On the first line, the date and time are followed by a trace of the XOT call to IP address 192.168.11.2, port 1998 from IP address 192.168.11, port 16511. The O (shown in bold text for purpose of example) indicates the call is outbound from the router. The call is placed on LCI 800.

*Aug 17 19:50:01.606: [192.168.11.2,1998/192.168.11.1,16511]: XOT O P2 Call (25) 8 lci 800*Aug 17 19:50:01.606: From (10): 4085272368 To (10): 3178161070*Aug 17 19:50:01.606: Facilities: (6)*Aug 17 19:50:01.606: Packet sizes: 128 128*Aug 17 19:50:01.606: Window sizes: 2 2*Aug 17 19:50:01.606: Call User Data (4): 0x01000000 (pad) 0: 13200BAA 31781610 . .*1x.. 8: 70408527 23680642 07074302 02010000 p@.'#h.B..C..... 24: 00



Remember that in the call made in the “Trace Output for Router 2851 Without X.25 Relay: Example” section, the call was placed on LCI 1, which is the default for XOT. The information in this trace is a first clue that the x25 relay-vc-number command has prevented the default LCI from being used to place a call.

In the following output, the Call Confirmation request packet is received from router 3725A for the XOT connection, still using LCI 800. The I after XOT (shown in bold text for purpose of example) indicates the packet is incoming to the interface.

*Aug 17 19:50:01.622: [192.168.11.2,1998/192.168.11.1,16511]: XOT I P2 Call Confirm (11) 8 lci 800*Aug 17 19:50:01.622: From (0): To (0): *Aug 17 19:50:01.622: Facilities: (6)*Aug 17 19:50:01.622: Packet sizes: 128 128*Aug 17 19:50:01.622: Window sizes: 2 2 0: 13200F 00064207 07430202 . ...B..C.. 11:

The following output shows the call confirmation for the X25 connection being sent by router 2851 to the router 2821 on LCI 800. The O after X.25 (shown in bold text for purpose of example) indicates the call is outbound from the router.

*Aug 17 19:50:01.622: Serial0/3/0: X.25 O R1 Call Confirm (5) 8 lci 800*Aug 17 19:50:01.622: From (0): To (0): *Aug 17 19:50:01.622: Facilities: (0) 0: 13200F 0000 . ...

The following output shows data transferred across the link, all using LCI 800; no changes to the connection number occurs. (The display has been truncated for easier readability.)

*Aug 17 19:50:01.622: [192.168.11.2,1998/192.168.11.1,16511]: XOT I D1 Data (4) Q 8 lci 800 PS 0 PR 0 0: 932000 04 . .. *Aug 17 19:50:01.622: Serial0/3/0: X.25 O D1 Data (4) Q 8 lci 800 PS 0 PR 0 0: 932000 04 . .. *Aug 17 19:50:01.626: [192.168.11.2,1998/192.168.11.1,16511]: XOT I D1 Data (28) 8 lci 800 PS 1 PR 0 0: 132002 54727969 6E672031 . .Trying 1 11: 39322E31 36382E31 302E3636 202E2E2E 92.168.10.66 ... 27: 20 *Aug 17 19:50:01.626: Serial0/3/0: X.25 O D1 Data (28) 8 lci 800 PS 1 PR 0 0: 132002 54727969 6E672031 . .Trying 1 11: 39322E31 36382E31 302E3636 202E2E2E 92.168.10.66 ... 27: 20 *Aug 17 19:50:01.654: Serial0/3/0: X.25 I D1 Data (48) Q 8 lci 800 PS 0 PR 0 0: 932000 00010102 01030204 . ......... 11: 01050006 00070408 0009000A 000B0E0C ................ 27: 000D000E 000F0010 7F111512 12130014 ................ 43: 00150016 00 ..... *Aug 17 19:50:01.654: [192.168.11.2,1998/192.168.11.1,16511]: XOT O D1 Data (48) Q 8 lci 800 PS 0 PR 0 0: 932000 00010102 01030204 . ......... 11: 01050006 00070408 0009000A 000B0E0C ................ 27: 000D000E 000F0010 7F111512 12130014 ................ 43: 00150016 00 ..... *Aug 17 19:50:01.658: Serial0/3/0: X.25 I D1 RR (3) 8 lci 800 PR 1 0: 132021 . ! *Aug 17 19:50:01.658: [192.168.11.2,1998/192.168.11.1,16511]: XOT O D1 RR (3) 8 lci 800 PR 1 0: 132021 . ! *Aug 17 19:50:01.662: Serial0/3/0: X.25 I D1 RR (3) 8 lci 800 PR 2 0: 132041 . A



*Aug 17 19:50:01.662: [192.168.11.2,1998/192.168.11.1,16511]: XOT O D1 RR (3) 8 lci 800 PR 2 0: 132041 . A *Aug 17 19:50:01.670: [192.168.11.2,1998/192.168.11.1,16511]: XOT I D1 Data (9) 8 lci 800 PS 2 PR 0 0: 132004 4F70656E 0D0A . .Open.. *Aug 17 19:50:01.670: Serial0/3/0: X.25 O D1 Data (9) 8 lci 800 PS 2 PR 0 0: 132004 4F70656E 0D0A . .Open.. *Aug 17 19:50:01.682: Serial0/3/0: X.25 I D1 RR (3) 8 lci 800 PR 3 0: 132061 . a *Aug 17 19:50:01.682: [192.168.11.2,1998/192.168.11.1,16511]: XOT O D1 RR (3) 8 lci 800 PR 3 0: 132061 . a *Aug 17 19:50:01.734: [192.168.11.2,1998/192.168.11.1,16511]: XOT I D1 Data (6) Q 8 lci 800 PS 3 PR 0 0: 932006 060200 . .... *Aug 17 19:50:01.734: Serial0/3/0: X.25 O D1 Data (6) Q 8 lci 800 PS 3 PR 0 0: 932006 060200 . .... *Aug 17 19:50:01.738: [192.168.11.2,1998/192.168.11.1,16511]: XOT I D1 Data (12) Q 8 lci 800 PS 4 PR 0 0: 932008 06020004 010F0007 . ......... 11: 15 . *Aug 17 19:50:01.738: Serial0/3/0: X.25 O D1 Data (12) Q 8 lci 800 PS 4 PR 0 0: 932008 06020004 010F0007 . ......... 11: 15 . *Aug 17 19:50:01.738: [192.168.11.2,1998/192.168.11.1,16511]: XOT I D1 RR (3) 8 lci 800 PR 1 0: 132021 . ! *Aug 17 19:50:01.738: Serial0/3/0: X.25 O D1 RR (3) 8 lci 800 PR 1 0: 132021 . ! *Aug 17 19:50:01.746: Serial0/3/0: X.25 I D1 Data (6) Q 8 lci 800 PS 1 PR 3 0: 932062 000200 . b... . . .*Aug 17 19:50:28.850: Serial0/3/0: X.25 O D1 Data (4) Q 8 lci 800 PS 4 PR 5 0: 9320A8 01 . (. *Aug 17 19:50:28.862: Serial0/3/0: X.25 I D1 RR (3) 8 lci 800 PR 5 0: 1320A1 . ! *Aug 17 19:50:28.862: [192.168.11.2,1998/192.168.11.1,16511]: XOT O D1 RR (3) 8 lci 800 PR 5 0: 1320A1 . !

Router 2851 Receives Call Clear Request with X.25 Relay: Example

The following output shows router 2851 receiving a Call Clear request packet on LCI 800. In the first line following the date and time, the interface is identified as serial interface 0/3/0, the packet type is I for inbound from the router, and the Call Clear request is for LCI 800.

*Aug 17 19:50:28.866: Serial0/3/0: X.25 I R1 Clear (5) 8 lci 800*Aug 17 19:50:28.866: Cause 0, Diag 0 (DTE originated/No additional information) 0: 132013 0000 . ...

The following output shows the Call Clear request is sent across an XOT connection between IP address 192.168.11.2, port 1998 and IP address 192.168.11.1, port 16511:

*Aug 17 19:50:28.866: [192.168.11.2,1998/192.168.11.1,16511]: XOT O P4 Clear (5) 8 lci 800*Aug 17 19:50:28.866: Cause 0, Diag 0 (DTE originated/No additional information) 0: 132013 0000 . ...



Router 2851 Receives Call Clear Confirmation Packet with X.25 Relay: Example

The following output shows the Call Clear confirmation packet on LCI 800 across the XOT connection:

*Aug 17 19:50:28.886: [192.168.11.2,1998/192.168.11.1,16511]: XOT I P6 Clear Confirm (3) 8 lci 800 0: 132017

The following output shows the Call Clear confirmation packet being sent out serial 0/3/0 on LCI 800 to router 2821:

. . .*Aug 17 19:50:28.886: Serial0/3/0: X.25 O R1 Clear Confirm (3) 8 lci 800 0: 132017 . . 2851A#

Placing a Call to Router 3725A from Router 2851A with X.25 Relay: Example

The following output shows router 2851A placing a call over the XOT link to router 3725A:

*Mar 1 07:51:03.466: [192.168.11.1,16511/192.168.11.2,1998]: XOT I P/Inactive Call (25) 8 lci 800*Mar 1 07:51:03.466: From (10): 4085272368 To (10): 3178161070*Mar 1 07:51:03.466: Facilities: (6)*Mar 1 07:51:03.466: Packet sizes: 128 128*Mar 1 07:51:03.466: Window sizes: 2 2*Mar 1 07:51:03.466: Call User Data (4): 0x01000000 (pad) 0: 13200B AA317816 10704085 . .*1x..p@. 11: 27236806 42070743 02020100 0000 '#h.B..C......

The call is from IP address 192.168.11.1, port 16396 to IP address 192.168.11.2, port 1998. The I after XOT indicates the call is inbound from the router. The call is placed on LCI 800, which confirms that the router sent the call across the network and retained the LCI 800, and proves that the x25 relay-vc-number command did work.

Placing a Call to Router 2651XMA from Router 3725A with X.25 Relay: Example

In the following output, router 3725A places a call to router 2651XMA.

• On the first line of the trace output, the date and time are followed by the interface type, which for this run is serial interface 1/1. The O (shown in bold text for purpose of example) indicates the packets is outgoing. The call is sent out on LCI 800.

• On the second line, the call is from X.121 address 4085272368, which is the address that was assigned to serial interface 1/1 on router 2821. The call is going to X.121 address 3178161070. X.121 addresses are assigned with the x25 address command.

*Mar 1 07:51:03.466: Serial1/1: X.25 O R1 Call (19) 8 lci 800*Mar 1 07:51:03.466: From (10): 4085272368 To (10): 3178161070*Mar 1 07:51:03.466: Facilities: (0)*Mar 1 07:51:03.466: Call User Data (4): 0x01000000 (pad) 0: 13200BAA 31781610 . .*1x.. 8: 70408527 23680001 000000 p@.'#h.....

The following output shows data transferred across the link, all using LCI 800; no changes to the connection number occurs. (The display has been truncated for easier readability.). . .*Mar 1 07:51:03.478: Serial1/1: X.25 I R1 Call Confirm (3) 8 lci 800 0: 13200F . . *Mar 1 07:51:03.478: [192.168.11.1,16511/192.168.11.2,1998]: XOT O P3 Call Confirm (11) 8 lci 800*Mar 1 07:51:03.478: From (0): To (0): *Mar 1 07:51:03.478: Facilities: (6)*Mar 1 07:51:03.478: Packet sizes: 128 128



*Mar 1 07:51:03.478: Window sizes: 2 2 0: 13200F 00064207 07430202 . ...B..C.. 11: *Mar 1 07:51:03.478: Serial1/1: X.25 I D1 Data (4) Q 8 lci 800 PS 0 PR 0 0: 932000 04 . .. *Mar 1 07:51:03.478: [192.168.11.1,16511/192.168.11.2,1998]: XOT O D1 Data (4) Q 8 lci 800 PS 0 PR 0 0: 932000 04 . .. *Mar 1 07:51:03.482: Serial1/1: X.25 I D1 Data (28) 8 lci 800 PS 1 PR 0 0: 132002 54727969 6E672031 . .Trying 1 11: 39322E31 36382E31 302E3636 202E2E2E 92.168.10.66 ... 27: 20 *Mar 1 07:51:03.482: [192.168.11.1,16511/192.168.11.2,1998]: XOT O D1 Data (28) 8 lci 800 PS 1 PR 0 0: 132002 54727969 6E672031 . .Trying 1 11: 39322E31 36382E31 302E3636 202E2E2E 92.168.10.66 ... 27: 20 *Mar 1 07:51:03.514: [192.168.11.1,16511/192.168.11.2,1998]: XOT I D1 Data (48) Q 8 lci 800 PS 0 PR 0 0: 932000 00010102 01030204 . ......... 11: 01050006 00070408 0009000A 000B0E0C ................ 27: 000D000E 000F0010 7F111512 12130014 ................ 43: 00150016 00 ..... *Mar 1 07:51:03.514: Serial1/1: X.25 O D1 Data (48) Q 8 lci 800 PS 0 PR 0 0: 932000 00010102 01030204 . ......... 11: 01050006 00070408 0009000A 000B0E0C ................ 27: 000D000E 000F0010 7F111512 12130014 ................ 43: 00150016 00 ..... *Mar 1 07:51:03.518: [192.168.11.1,16511/192.168.11.2,1998]: XOT I D1 RR (3) 8 lci 800 PR 1 0: 132021 . ! *Mar 1 07:51:03.518: Serial1/1: X.25 O D1 RR (3) 8 lci 800 PR 1 0: 132021 . ! *Mar 1 07:51:03.518: [192.168.11.1,16511/192.168.11.2,1998]: XOT I D1 RR (3) 8 lci 800 PR 2 0: 132041 . A *Mar 1 07:51:03.518: Serial1/1: X.25 O D1 RR (3) 8 lci 800 PR 2 0: 132041 . A *Mar 1 07:51:03.526: Serial1/1: X.25 I D1 Data (9) 8 lci 800 PS 2 PR 0 0: 132004 4F70656E 0D0A . .Open.. *Mar 1 07:51:03.526: [192.168.11.1,16511/192.168.11.2,1998]: XOT O D1 Data (9) 8 lci 800 PS 2 PR 0 0: 132004 4F70656E 0D0A . .Open.. *Mar 1 07:51:03.542: [192.168.11.1,16511/192.168.11.2,1998]: XOT I D1 RR (3) 8 lci 800 PR 3 0: 132061 . a *Mar 1 07:51:03.542: Serial1/1: X.25 O D1 RR (3) 8 lci 800 PR 3 0: 132061 . a *Mar 1 07:51:03.590: Serial1/1: X.25 I D1 Data (6) Q 8 lci 800 PS 3 PR 0 0: 932006 060200 . .... *Mar 1 07:51:03.590: [192.168.11.1,16511/192.168.11.2,1998]: XOT O D1 Data (6) Q 8 lci 800 PS 3 PR 0 0: 932006 060200 . .... *Mar 1 07:51:03.594: Serial1/1: X.25 I D1 Data (12) Q 8 lci 800 PS 4 PR 0 0: 932008 06020004 010F0007 . ......... 11: 15 . *Mar 1 07:51:03.594: [192.168.11.1,16511/192.168.11.2,1998]: XOT O D1 Data (12) Q 8 lci 800 PS 4 PR 0 0: 932008 06020004 010F0007 . ......... 11: 15 . *Mar 1 07:51:03.594: Serial1/1: X.25 I D1 RR (3) 8 lci 800 PR 1 0: 132021 . ! *Mar 1 07:51:03.594: [192.168.11.1,16511/192.168.11.2,1998]: XOT O D1 RR (3) 8 lci 800 PR 1



0: 132021 . ! *Mar 1 07:51:03.606: [192.168.11.1,16511/192.168.11.2,1998]: XOT I D1 Data (6) Q 8 lci 800 PS 1 PR 3 0: 932062 000200 . b... *Mar 1 07:51:03.606: Serial1/1: X.25 O D1 Data (6) Q 8 lci 800 PS 1 PR 3 0: 932062 000200 . b... *Mar 1 07:51:03.606: [192.168.11.1,16511/192.168.11.2,1998]: XOT I D1 RR (3) 8 lci 800 PR 4 0: 132081 . . *Mar 1 07:51:03.610: Serial1/1: X.25 O D1 RR (3) 8 lci 800 PR 4 0: 132081 . . *Mar 1 07:51:03.610: Serial1/1: X.25 I D1 RR (3) 8 lci 800 PR 2 0: 132041 . A *Mar 1 07:51:03.610: [192.168.11.1,16511/192.168.11.2,1998]: XOT O D1 RR (3) 8 lci 800 PR 2 0: 132041 . A *Mar 1 07:51:03.618: Serial1/1: X.25 I D1 Data (45) 8 lci 800 PS 5 PR 2 0: 13204A 0D0A0D0A 55736572 . J....User 11: 20416363 65737320 56657269 66696361 Access Verifica 27: 74696F6E 0D0A0D0A 50617373 776F7264 tion....Password 43: 3A20 : *Mar 1 07:51:03.618: [192.168.11.1,16511/192.168.11.2,1998]: XOT O D1 Data (45) 8 lci 800 PS 5 PR 2 0: 13204A 0D0A0D0A 55736572 . J....User 11: 20416363 65737320 56657269 66696361 Access Verifica 27: 74696F6E 0D0A0D0A 50617373 776F7264 tion....Password 43: 3A20 : *Mar 1 07:51:03.714: [192.168.11.1,16511/192.168.11.2,1998]: XOT I D1 Data (12) Q 8 lci 800 PS 2 PR 4 0: 932084 00020004 010F0007 . ......... 11: 15 . *Mar 1 07:51:03.714: Serial1/1: X.25 O D1 Data (12) Q 8 lci 800 PS 2 PR 4 0: 932084 00020004 010F0007 . ......... 11: 15 . *Mar 1 07:51:03.714: [192.168.11.1,16511/192.168.11.2,1998]: XOT I D1 RR (3) 8 lci 800 PR 5 0: 1320A1 . ! *Mar 1 07:51:03.714: Serial1/1: X.25 O D1 RR (3) 8 lci 800 PR 5 0: 1320A1 . ! *Mar 1 07:51:03.718: [192.168.11.1,16511/192.168.11.2,1998]: XOT I D1 RR (3) 8 lci 800 PR 6 0: 1320C1 . A *Mar 1 07:51:03.718: Serial1/1: X.25 O D1 RR (3) 8 lci 800 PR 6 0: 1320C1 . A *Mar 1 07:51:03.718: Serial1/1: X.25 I D1 RR (3) 8 lci 800 PR 3 0: 132061 . a *Mar 1 07:51:03.718: [192.168.11.1,16511/192.168.11.2,1998]: XOT O D1 RR (3) 8 lci 800 PR 3 0: 132061 . a *Mar 1 07:51:09.102: [192.168.11.1,16511/192.168.11.2,1998]: XOT I D1 Data (4) 8 lci 800 PS 3 PR 6 0: 1320C6 63 . Fc *Mar 1 07:51:09.102: Serial1/1: X.25 O D1 Data (4) 8 lci 800 PS 3 PR 6 0: 1320C6 63 . Fc *Mar 1 07:51:09.106: Serial1/1: X.25 I D1 RR (3) 8 lci 800 PR 4 0: 132081 . . *Mar 1 07:51:09.106: [192.168.11.1,16511/192.168.11.2,1998]: XOT O D1 RR (3) 8 lci 800 PR 4 0: 132081 . . *Mar 1 07:51:09.298: [192.168.11.1,16511/192.168.11.2,1998]: XOT I D1 Data (4) 8 lci 800 PS 4 PR 6 0: 1320C8 69 . Hi *Mar 1 07:51:09.298: Serial1/1: X.25 O D1 Data (4) 8 lci 800 PS 4 PR 6 0: 1320C8 69 . Hi


Appendix A Cisco IOS X.25 ToolkitX.25 Throughput Negotiation

*Mar 1 07:51:09.306: Serial1/1: X.25 I D1 RR (3) 8 lci 800 PR 5 0: 1320A1 . ! *Mar 1 07:51:09.306: [192.168.11.1,16511/192.168.11.2,1998]: XOT O D1 RR (3) 8 lci 800 PR 5 0: 1320A1 . ! *. . .*Mar 1 07:51:30.706: Serial1/1: X.25 I D1 Data (4) Q 8 lci 800 PS 4 PR 5 0: 9320A8 01 . (. *Mar 1 07:51:30.706: [192.168.11.1,16511/192.168.11.2,1998]: XOT O D1 Data (4) Q 8 lci 800 PS 4 PR 5 0: 9320A8 01 . (. *Mar 1 07:51:30.734: [192.168.11.1,16511/192.168.11.2,1998]: XOT I D1 RR (3) 8 lci 800 PR 5 0: 1320A1 . ! *Mar 1 07:51:30.734: Serial1/1: X.25 O D1 RR (3) 8 lci 800 PR 5 0: 1320A1 . ! *Mar 1 07:51:30.738: [192.168.11.1,16511/192.168.11.2,1998]: XOT I P4 Clear (5) 8 lci 800*Mar 1 07:51:30.738: Cause 0, Diag 0 (DTE originated/No additional information) 0: 132013 0000 . ... *Mar 1 07:51:30.738: Serial1/1: X.25 O R1 Clear (5) 8 lci 800*Mar 1 07:51:30.738: Cause 0, Diag 0 (DTE originated/No additional information) 0: 132013 0000 . ... *Mar 1 07:51:30.742: Serial1/1: X.25 I R1 Clear Confirm (3) 8 lci 800 0: 132017 . . *Mar 1 07:51:30.742: <detached>: XOT O P7 Clear Confirm (3) 8 lci 800 0: 132017 . .

X.25 Throughput NegotiationWhen service providers migrate from the older X.25 DCN to a router-based DCN, some of the older networking devices will clear a call if any throughput negotiation was performed on incoming calls. The older X.25 devices have limited or no support from their vendors to help service providers understand device behavior. With the Cisco X.25 Throughput Negotiation feature, service providers are able to migrate the application transparently to a Cisco-based DCN. The X.25 throughput user facility defines the amount of information that can be passed across the network between two devices. The feature is applied using the x25 throughput negotiation never command on the interface. Throughput is negotiated at call setup. Figure A-6 indicates where the x25 throughput negotiation never command is executed in the router-based DCN.

Figure A-6 X.25 Throughput Negotiation

The Cisco X.25 Throughput Negotiation feature enables a router to negotiate X.25 throughput parameters on behalf of end devices, thereby making X.25 calls possible to devices that cannot themselves negotiate throughput.

2320

09

XOT IPcloud

x25 over TCP/IP

x25 throughput command

x25 connection

x25

OSSNetworkelement

Router 2

Serial 2/1

x25 switchRouter 1

X.25


Appendix A Cisco IOS X.25 ToolkitX.25 Throughput Negotiation

The Cisco X.25 Throughput Negotiation feature enables the router to negotiate throughput values for two types of end devices:

• Devices that never expect throughput values in the incoming call and never send out throughput parameters in the outgoing call.

• Devices that always expect throughput values in the incoming call and always send out throughput parameters in the outgoing call.

The Cisco X.25 throughput negotiation feature works as follows: The router strips out or inserts values, as appropriate, for the end device in the throughput facility field of the X.25 Call and Call-Confirm packets. To insert values appropriately, the router interface connected to the end device must earlier have been configured with the input and output throughput values that are intended to be used by the eventual X.25 call.

X.25 throughput negotiation is enabled using the x25 subscribe interface configuration command:

x25 subscribe throughput {basic | never}

X.25 throughput values are configured on the interface using the x25 facility throughput interface configuration command:

x25 facility throughput in-throughput out-throughput

In Figure A-6, the OSS sets up an X.25 call with the network element and attempts to negotiate throughput, but the legacy X.25 switch connected to Router 2 is unable to negotiate throughput. On the Cisco router interface, the throughput has been turned off with the following command:

x25 subscribe throughput never

No X.25 throughput facility will be sent to the X.25 switch.

The throughput facility for serial interface 2/1 has been defined by the network administrator as follows:

x25 subscribe throughput 48000 48000

The input and output bit rate is values are 48000 bits per second.

Following is a sample configuration for serial interface 2/1 in Figure A-6:

interface serial2/1 description no ip address encapsulation x25 dce x25 version 1993 no x25 security crcdn no x25 security clamn x25 lic 0 x25 hic 0 x25 ltc 1 x25 htc 50 x25 loc 0 x25 hoc 0 x25 win 3 x25 wout 3 x25 ips 128 x25 ops 128 x25 facility throughput 48000 48000 x25 subscribe throughput never x25 subscribe flow-control never clockrate 64000 no cdp enable


Appendix A Cisco IOS X.25 ToolkitNetwork Element Dial-Out Prevention

lapb T1 4000 lapb k 7 no shutdown

More details about the Cisco X.25 Throughput Negotiation feature can be found in the X.25 Throughput Negotiation feature module at the following URL: http://www.cisco.com/en/US/partner/products/ps6441/products_feature_guide09186a0080551e0d.html

Network Element Dial-Out PreventionIn response to a request from service providers to implement network element dial-out prevention, Cisco developed the x28 no-outgoing command. As shown in Figure A-7, the command is used for a network element that is connected asynchronously to a Cisco router to prevent the network element from dialing out towards the host. When the x28 no-outgoing command is configured, the host must set up an X.25 connection to the network element before data transfer can occur. If the X.25 connection is not set up, and the network element sends characters towards the router, the characters are dropped. Also, any local PAD commands sent by a network element are ignored by the router.

Figure A-7 Network Element Dial-Out Prevention

The command syntax for the x28 no-outgoing command is as follows:

x28 no-outgoing

no x28 no-outgoing

To configure X.28 user emulation mode to prevent a network element from dialing out, use the x28 no-outgoing command in user EXEC, privileged EXEC, or line configuration mode.

To configure X.28 user emulation mode on all lines connected to the router, use the x28 no-outgoing command in the user EXEC mode or the privileged EXEC mode.

The x28 no-outgoing command is used with the autocommand command in line configuration mode to configure the X.28 user emulation mode on a per-line basis.

Use of the x28 no-outgoing command on the console will lock the console. Unlock the console by logging in from a different tty or vty. If no line is available, reboot the router.

The following example configures X.28 user emulation mode only on line 33, and is used with the autocommand command to prevent network elements from dialing out through that line:

Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# line 33Router(config-line)# autocommand x28 no-outgoingRouter(config-line)# exit

2316

16

XOT/IPcloud

X.25 over TCP/IP


X.25

OSS

Async

Networkelement

x28 no-outgoing command

Router 2Router 1


http://www.cisco.com/en/US/partner/products/ps6441/products_feature_guide09186a0080551e0d.html



Appendix A Cisco IOS X.25 ToolkitModem Always On for Network Elements

Modem Always On for Network ElementsService providers employ large numbers of asynchronous network elements in the X.25-based data communications networks (DCNs), which are managed via asynchronous connections. The asynchronous terminal (TTY) lines are traditionally connected to the X.25 DCN via a packet assembler/disassembler (PAD). In Figure A-8, a Digital Cross Connect device is asynchronously attached to a PAD for access to the X.25-based DCN.

Figure A-8 Classic X.25-Based DCN

Service providers are migrating to IP-based DCNs and eliminating unsupported devices such as X.25 PADs and X.25 switches. Often, manufacturers are dropping support for these devices, so the network elements must be connected to Cisco asynchronous terminal lines and use the Cisco IOS PAD software. The service providers need Cisco routers to assume that the network element will not provide call control signals to start data transfer towards the host or vice versa. This need is answered by the modem always-on EXEC command, which sets a TTY line to be always ready to interpret characters from network elements.

Figure A-9 shows the point in the network where the modem always-on EXEC command is executed when the network element does not provide any call control signals.

Figure A-9 Modem Always On

The EXEC process associated with the TTY line on the router will be spawned and ready to receive the characters on the modem from the network element as soon as the modem always-on EXEC command is configured, no matter whether the modem associated with the TTY line receives RING, CTS, or DSR signals, or user characters. In Figure A-9, this process occurs on the line labeled TTY 33. You see that there is an X.25 connection from the OSS host to Router 2. There may be times when an X.25 connection

2316

14

X.25backbone

OSS

OSS

X.25 switch

X.25 switch

X.25connections

X.25connections

Sonet/SDH

Digitalloop

carrier

HDSLshelf

Digitalcross

connect

X.25 PAD

X.25 PAD

Asynchronousconnection

Asynchronousconnection

2316

15

XOT/IPcloud

X.25 over TCP/IP


X.25

OSS

Async

Networkelement

modem always-on command

Router 2Router 1


Appendix A Cisco IOS X.25 ToolkitDebugging X.25

has not been brought up and connected to the PAD via a TTY session. In this case, and until the X.25 connection is set up, the data characters and remote PAD parameters received from the network element are ignored.

The modem always-on command is supported only for X.28 PAD connections. Following is the command syntax for the modem always-on EXEC command:

modem always-on

no modem always-on

The following example shows how the modem always-on command is typically configured:

Router(config)# line 33Router(config-line)# rotary 1Router(config-line)# modem always-onRouter(config-line)# no autocommand x28Router(config-line)# end

Use the show line command to verify that the modem always-on command has been activated.

Router# show line 33

Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int* 33 TTY 2400/2400 - always-on - - - 0 0 0/0 -

Debugging X.25The debug x25 command has several keywords associated with it that displays various types of information about X.25 traffic. You can choose to view all information or restrict the reports to a specific interface.

Caution The debug x25 command can generate large amounts of debugging output. If logging of debug output to the router console is enabled (the default condition), this output may fill the console buffer, preventing the router from processing packets until the contents of the console buffer have been printed. To prevent this, do one or more of the following:—Disable logging of debug output to the console. Refer to the logging console command for more information.—Configure the router to discard console output when the buffer overflows. Refer to the logging console guaranteed command for more information.—Use this command only when all reportable X.25 traffic is flowing at a data rate of less than five packets per second.

Perform the following steps to debug X.25 interfaces:

Step 1 Enter the debug x25 command with a question mark to see the keywords that can be used for X.25 debugging:

Router-C# debug x25 ?

all Show all X.25 traffic (default) annexg X.25 over Frame-Relay (Annex-G) Events aodi Always On/Direct ISDN (PPP over X.25) events cmns Show only CMNS traffic events Show X.25 traffic without normal Data and RR packets interface Show X.25 or CMNS traffic on one interface


Appendix A Cisco IOS X.25 ToolkitDebugging LAPB

only Show only X.25 traffic vc X.25 traffic across a specific virtual circuit xot Show only XOT (X.25-Over-TCP) traffic <cr>

Note If the routers are loaded with a production release of the software, be careful which debugging features you enable. You can enable debugging for a specific serial interface or events; use the following examples as a guide.

Step 2 Use the debug x25 interface command to enable debugging on a specific X.25 interface:

Router3# debug x25 interface serial 1/2

X.25 packet debugging is onX.25 debug output restricted to interface Serial1/2

Step 3 Use the debug x25 events command to display information about all X.25 traffic (except data and resource record packets).

The following example shows the traffic coming from remote Router1 (R1):

Router2# debug x25 eventsX.25 special event debugging is on

*Mar 1 04:58:42.350: Serial1: X.25 I R1 Call (12) 8 lci 1*Mar 1 04:58:42.354: From (3): 800 To (3): 900*Mar 1 04:58:42.358: Facilities: (0)*Mar 1 04:58:42.358: Call User Data (4): 0xCC000000 (ip)*Mar 1 04:58:42.366: Serial1: X.25 O R1 Call Confirm (3) 8 lci 1*Mar 1 04:58:42.410: Serial1: X.25 I R1 Call (12) 8 lci 2*Mar 1 04:58:42.410: From (3): 800 To (3): 900*Mar 1 04:58:42.414: Facilities: (0)*Mar 1 04:58:42.414: Call User Data (4): 0xCC000000 (ip)*Mar 1 04:58:42.422: Serial1: X.25 O R1 Call Confirm (3) 8 lci 2

Debugging LAPBThe debug lapb command is a useful tool for debugging X.25 serial interfaces, but enables debugging for all router interfaces, which can generate a large amount of data and make debugging tedious. In Cisco IOS Release 12.4(7.7)T and later releases, Cisco provides a feature to filter the information with the debug interface command. To see debugging information for a specific interface, first enable LAPB debugging using the debug lapb command, then enable debugging on the interface using the debug interface command. If the debug interface command is not set for at least one interface, debugging information for all interfaces running X.25 or LAPB is displayed.

The following examples use the network shown in Figure A-10. In this network, two routers labeled 2821 and 2851 are connected back to back with two serial interfaces that are used for the configuration and debugging examples that follow. Traffic was generated by having a user use Telnet to connect from a PC to router 2611B and issue commands. The connection goes across the network in a combination of X.25 and TCP/IP XOT network links, as shown in Figure A-10. The PC uses Telnet to the translate IP address 192.168.1.229, which is a virtual address associated with router 2821 for protocol translation. The connections are mediated into X.25 and forwarded across the appropriate serial link.



Figure A-10 Sample X.25 Network

The following sections list the configurations for this sample network in the following sections:

• Router 2821 Configuration for LAPB Debugging: Example, page A-30

• Router 2851 Configuration for LAPB Debugging: Example, page A-31

• Debugging LABP Without Interface Filtering, page A-32

• Debugging LABP with Interface Filtering, page A-38

Router 2821 Configuration for LAPB Debugging: ExampleFollowing is the configuration for router 2821 seen in Figure A-10:

x25 routing


interface GigabitEthernet0/1 ip address 192.168.1.239 255.255.255.0 duplex auto speed auto

interface Serial0/0/0 description RS232 to 2851 0/3/0 no ip address encapsulation x25 x25 address 4085272368!interface Serial0/0/1 description rs232 to 2851 0/3/1 no ip address encapsulation x25 x25 address 4085272361

2320

08


translate tcp 192.168.1.229 port 1060 x25 3178451060 translate tcp 192.168.1.229 port 1061 x25 3178451061 translate tcp 192.168.1.229 port 1070 x25 3178161070!x25 route 3178161060 interface Serial0/0/0x25 route 3178161061 interface Serial0/0/1x25 route 317845 interface Serial0/0/0x25 route 317816 interface Serial0/0/1

translate x25 3178451060 tcp 192.168.10.66translate x25 3178451061 tcp 192.168.10.66translate x25 3178161070 tcp 192.168.10.66


S 0/0/0

S 0/0/1192.168.11.1 192.168.11.2 192.168.10.67 192.168.10.660/0/0

S 0/3/0 FA 0/0 FA 0/0 FA 0/02611B26513725A2851

X.25 XOT X.25 IP

2821

S 0/3/1

S 1/0

S 1/1

S 0/0

S 0/1

192.168.1.239192.168.1.229192.168.1.239192.168.1.229



translate tcp 192.168.34.60 port 1060 x25 3178161060translate tcp 192.168.34.61 port 1061 x25 3178161061translate tcp 192.168.34.60 port 1070 x25 3178451070translate tcp 192.168.1.229 port 1060 x25 3178451060translate tcp 192.168.1.229 port 1061 x25 3178451061translate tcp 192.168.1.229 port 1070 x25 3178161070!x25 route 3178161060 interface Serial0/0/0x25 route 3178161061 interface Serial0/0/1x25 route 317845 interface Serial0/0/0x25 route 317816 interface Serial0/0/1

Router 2851 Configuration for LAPB Debugging: ExampleThe following examples show the software version and relevant configuration information for router 2851 in Figure A-10. In this example, a connection is made to both serial interface 0/3/0 and serial interface 0/3/1. The X.25 packets are then routed to router 3725A via XOT at IP address 192.168.11.2.

Software Version 2851# show version

Cisco IOS Software, 2800 Software (C2800NM-IPBASEK9-M), Version 12.4(15)T1, REL)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2007 by Cisco Systems, Inc.Compiled Wed 18-Jul-07 06:21 by prod_rel_team

ROM: System Bootstrap, Version 12.3(8r)T7, RELEASE SOFTWARE (fc1)

2851A uptime is 1 day, 7 hours, 16 minutesSystem returned to ROM by power-onSystem image file is "flash:c2800nm"

This product contains cryptographic features and is subject to UnitedStates and local country laws governing import, export, transfer anduse. Delivery of Cisco cryptographic products does not implythird-party authority to import, export, distribute or use encryption.Importers, exporters, distributors and users are responsible forcompliance with U.S. and local country laws. By using this product youagree to comply with applicable laws and regulations. If you are unableto comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email [email protected].

Cisco 2851 (revision 53.51) with 509952K/14336K bytes of memory.Processor board ID FTX0915A0U216 FastEthernet interfaces3 Gigabit Ethernet interfaces4 Low-speed serial(sync/async) interfaces16 terminal linesDRAM configuration is 64 bits wide with parity enabled.239K bytes of non-volatile configuration memory.250368K bytes of ATA CompactFlash (Read/Write)

Configuration register is 0x2102



Configuration Commandsx25 routing

interface Serial0/3/0 description rs232 to 2821 0/0/0 no ip address encapsulation x25 dce x25 address 200910 clock rate 19200!interface Serial0/3/1 description rs232 to 2821 0/0/1 no ip address encapsulation x25 dce clock rate 19200


Debugging LABP Without Interface FilteringThe following steps show how to enable LAPB debugging and X.25 packet debugging on router 2821. The debug interface command is not included in the configuration.

Step 1 Enable LAPB debugging:

2821# debug lapbLAPB link debugging is on

Step 2 Enable X.25 packet debugging so that you can see the call setup and data pass of this debugging:

2821# debug x25 all dumpX.25: X.25 packet debugging is on X.25 packet dump debugging is on X.25 packet dump is enabled for hex and ascii formats

Step 3 Enable the debug translate command to see the translation process start.

2821R1# debug translateProtocol Translation debugging is on

Step 4 Enable the terminal monitor command to display debug command output during the current terminal session:

2821# terminal monitor

Step 5 To show how the the debug commands work, Telnet to 192.168.1.229, port 1061 on the 2821 router from a PC using the translate tcp command. This command mediates the TCP/IP session to the X.25 SVC that is calling X.121 address 3178451061. The call is routed to serial interface 0/0/0 using the x25 route command, as follows:

2821# config terminal2821(config)# translate tcp 192.168.1.229 port 1061 x25 31784510612821(config)# x25 route 317845 interface Serial0/0/0



Step 6 Display the output of the debug commands:

2821# show debugLAPB: LAPB link debugging is on

X.25: X.25 packet debugging is on X.25 packet dump debugging is on X.25 packet dump is enabled for hex and ascii formatsProtocol translation: Protocol Translation debugging is on

Output for Telnet to 192.168.1.229, Port 1061 on the 2821 Router From a PC

Following is the output for the first connection. The tcppad515 report indicates that protocol translation is starting.

2821#*Aug 16 23:11:25.859: tcppad515: fork started

Router 2821 places a call on serial interface 0/0/0 with source address 4085272368 to destination address 3178451061. The source address 4085272368 was assigned to serial interface 0/0/0 in the configuration listed in the “Router 2821 Configuration for LAPB Debugging: Example”section. The destination address was assigned in Step 5 with the translate tcp command.

*Aug 16 23:11:25.863: Serial0/0/0: X.25 O R1 Call (19) 8 lci 1024*Aug 16 23:11:25.863: From (10): 4085272368 To (10): 3178451061*Aug 16 23:11:25.863: Facilities: (0)*Aug 16 23:11:25.863: Call User Data (4): 0x01000000 (pad) 0: 14000BAA 31784510 ...*1xE. 8: 61408527 23680001 000000 a@.'#h..... *Aug 16 23:11:25.863: Serial0/0/0: LAPB O CONNECT (21) IFRAME 1 1*Aug 16 23:11:25.879: Serial0/0/0: LAPB I CONNECT (2) RR (R) 2*Aug 16 23:11:25.907: Serial0/0/0: LAPB I CONNECT (7) IFRAME 1 2*Aug 16 23:11:25.907: Serial0/0/0: X.25 I R1 Call Confirm (5) 8 lci 1024*Aug 16 23:11:25.907: From (0): To (0): *Aug 16 23:11:25.907: Facilities: (0) 0: 14000F 0000 ..... *Aug 16 23:11:25.911: Serial0/0/0: LAPB O CONNECT (2) RR (R) 2*Aug 16 23:11:25.911: Serial0/0/0: LAPB I CONNECT (6) IFRAME 2 2*Aug 16 23:11:25.911: Serial0/0/0: X.25 I D1 Data (4) Q 8 lci 1024 PS 0 PR 0 0: 940000 04 .... *Aug 16 23:11:25.911: Serial0/0/0: X.25 O D1 Data (48) Q 8 lci 1024 PS 0 PR 0 0: 940000 00010102 01030204 ........... 11: 01050006 00070408 0009000A 000B0E0C ................ 27: 000D000E 000F0010 7F111512 12130014 ................ 43: 00150016 00 ..... *Aug 16 23:11:25.915: Serial0/0/0: LAPB O CONNECT (50) IFRAME 2 3*Aug 16 23:11:25.915: Serial0/0/0: X.25 O D1 RR (3) 8 lci 1024 PR 1 0: 140021 ..! *Aug 16 23:11:25.915: Serial0/0/0: LAPB O CONNECT (5) IFRAME 3 3*Aug 16 23:11:25.935: Serial0/0/0: LAPB I CONNECT (30) IFRAME 3 2*Aug 16 23:11:25.935: Serial0/0/0: X.25 I D1 Data (28) 8 lci 1024 PS 1 PR 0 0: 140002 54727969 6E672031 ...Trying 1 11: 39322E31 36382E31 302E3636 202E2E2E 92.168.10.66 ... 27: 20 *Aug 16 23:11:25.935: Serial0/0/0: X.25 O D1 RR (3) 8 lci 1024 PR 2 0: 140041 ..A *Aug 16 23:11:25.935: Serial0/0/0: LAPB O CONNECT (5) IFRAME 4 4*Aug 16 23:11:25.939: Serial0/0/0: LAPB I CONNECT (2) RR (R) 3*Aug 16 23:11:25.943: Serial0/0/0: LAPB I CONNECT (2) RR (R) 4*Aug 16 23:11:25.947: Serial0/0/0: LAPB I CONNECT (2) RR (R) 5



*Aug 16 23:11:25.979: Serial0/0/0: LAPB I CONNECT (11) IFRAME 4 5*Aug 16 23:11:25.983: Serial0/0/0: X.25 I D1 Data (9) 8 lci 1024 PS 2 PR 0 0: 140004 4F70656E 0D0A ...Open.. *Aug 16 23:11:25.983: Serial0/0/0: X.25 O D1 RR (3) 8 lci 1024 PR 3 0: 140061 ..a *Aug 16 23:11:25.983: Serial0/0/0: LAPB O CONNECT (5) IFRAME 5 5*Aug 16 23:11:25.991: Serial0/0/0: LAPB I CONNECT (2) RR (R) 6*Aug 16 23:11:26.027: Serial0/0/0: LAPB I CONNECT (8) IFRAME 5 6*Aug 16 23:11:26.027: Serial0/0/0: X.25 I D1 Data (6) Q 8 lci 1024 PS 3 PR 0 0: 940006 060200 ...... *Aug 16 23:11:26.027: tcppad515: Sending WILL ECHO*Aug 16 23:11:26.027: Serial0/0/0: X.25 O D1 Data (6) Q 8 lci 1024 PS 1 PR 3 0: 940062 000200 ..b... *Aug 16 23:11:26.027: Serial0/0/0: LAPB O CONNECT (8) IFRAME 6 6*Aug 16 23:11:26.027: Serial0/0/0: X.25 O D1 RR (3) 8 lci 1024 PR 4 0: 140081 ... *Aug 16 23:11:26.027: Serial0/0/0: LAPB O CONNECT (5) IFRAME 7 6*Aug 16 23:11:26.035: Serial0/0/0: LAPB I CONNECT (14) IFRAME 6 6*Aug 16 23:11:26.035: Serial0/0/0: X.25 I D1 Data (12) Q 8 lci 1024 PS 4 PR 0 0: 940008 06020004 010F0007 ........... 11: 15 . *Aug 16 23:11:26.039: Serial0/0/0: LAPB O CONNECT (2) RR (R) 7*Aug 16 23:11:26.039: Serial0/0/0: LAPB I CONNECT (5) IFRAME 7 6*Aug 16 23:11:26.039: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 1 0: 140021 ..! *Aug 16 23:11:26.043: Serial0/0/0: LAPB O CONNECT (2) RR (R) 0*Aug 16 23:11:26.043: Serial0/0/0: LAPB I CONNECT (2) RR (R) 7*Aug 16 23:11:26.043: Serial0/0/0: LAPB I CONNECT (2) RR (R) 0*Aug 16 23:11:26.051: Serial0/0/0: LAPB I CONNECT (5) IFRAME 0 0*Aug 16 23:11:26.051: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 2 0: 140041 ..A *Aug 16 23:11:26.055: Serial0/0/0: LAPB O CONNECT (2) RR (R) 1*Aug 16 23:11:26.091: Serial0/0/0: LAPB I CONNECT (47) IFRAME 1 0*Aug 16 23:11:26.091: Serial0/0/0: X.25 I D1 Data (45) 8 lci 1024 PS 5 PR 2 0: 14004A 0D0A0D0A 55736572 ..J....User 11: 20416363 65737320 56657269 66696361 Access Verifica 27: 74696F6E 0D0A0D0A 50617373 776F7264 tion....Password 43: 3A20 : *Aug 16 23:11:26.095: Serial0/0/0: LAPB O CONNECT (2) RR (R) 2*Aug 16 23:11:26.139: Serial0/0/0: X.25 O D1 Data (12) Q 8 lci 1024 PS 2 PR 4 0: 940084 00020004 010F0007 ........... 11: 15 . *Aug 16 23:11:26.139: Serial0/0/0: LAPB O CONNECT (14) IFRAME 0 2*Aug 16 23:11:26.139: Serial0/0/0: X.25 O D1 RR (3) 8 lci 1024 PR 5 0: 1400A1 ..! *Aug 16 23:11:26.139: Serial0/0/0: LAPB O CONNECT (5) IFRAME 1 2*Aug 16 23:11:26.139: Serial0/0/0: X.25 O D1 RR (3) 8 lci 1024 PR 6 0: 1400C1 ..A *Aug 16 23:11:26.139: Serial0/0/0: LAPB O CONNECT (5) IFRAME 2 2*Aug 16 23:11:26.151: Serial0/0/0: LAPB I CONNECT (2) RR (R) 2*Aug 16 23:11:26.155: Serial0/0/0: LAPB I CONNECT (2) RR (R) 3*Aug 16 23:11:26.167: Serial0/0/0: LAPB I CONNECT (5) IFRAME 2 3*Aug 16 23:11:26.167: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 3 0: 140061 ..a *Aug 16 23:11:26.171: Serial0/0/0: LAPB O CONNECT (2) RR (R) 3*Aug 16 23:11:28.295: Serial0/0/0: X.25 O D1 Data (4) 8 lci 1024 PS 3 PR 6 0: 1400C6 63 ..Fc *Aug 16 23:11:28.295: Serial0/0/0: LAPB O CONNECT (6) IFRAME 3 3*Aug 16 23:11:28.303: Serial0/0/0: LAPB I CONNECT (2) RR (R) 4*Aug 16 23:11:28.315: Serial0/0/0: LAPB I CONNECT (5) IFRAME 3 4*Aug 16 23:11:28.315: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 4 0: 140081 ... *Aug 16 23:11:28.319: Serial0/0/0: LAPB O CONNECT (2) RR (R) 4*Aug 16 23:11:28.495: Serial0/0/0: X.25 O D1 Data (4) 8 lci 1024 PS 4 PR 6



0: 1400C8 69 ..Hi *Aug 16 23:11:28.495: Serial0/0/0: LAPB O CONNECT (6) IFRAME 4 4*Aug 16 23:11:28.503: Serial0/0/0: LAPB I CONNECT (2) RR (R) 5*Aug 16 23:11:28.519: Serial0/0/0: LAPB I CONNECT (5) IFRAME 4 5*Aug 16 23:11:28.519: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 5 0: 1400A1 ..! *Aug 16 23:11:28.523: Serial0/0/0: LAPB O CONNECT (2) RR (R) 5*Aug 16 23:11:28.695: Serial0/0/0: X.25 O D1 Data (4) 8 lci 1024 PS 5 PR 6 0: 1400CA 73 ..Js *Aug 16 23:11:28.695: Serial0/0/0: LAPB O CONNECT (6) IFRAME 5 5*Aug 16 23:11:28.703: Serial0/0/0: LAPB I CONNECT (2) RR (R) 6*Aug 16 23:11:28.715: Serial0/0/0: LAPB I CONNECT (5) IFRAME 5 6*Aug 16 23:11:28.719: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 6 0: 1400C1 ..A *Aug 16 23:11:28.723: Serial0/0/0: LAPB O CONNECT (2) RR (R) 6*Aug 16 23:11:28.895: Serial0/0/0: X.25 O D1 Data (5) 8 lci 1024 PS 6 PR 6 0: 1400CC 636F ..Lco *Aug 16 23:11:28.895: Serial0/0/0: LAPB O CONNECT (7) IFRAME 6 6*Aug 16 23:11:28.903: Serial0/0/0: LAPB I CONNECT (2) RR (R) 7*Aug 16 23:11:28.919: Serial0/0/0: LAPB I CONNECT (5) IFRAME 6 7*Aug 16 23:11:28.919: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 7 0: 1400E1 ..a *Aug 16 23:11:28.923: Serial0/0/0: LAPB O CONNECT (2) RR (R) 7*Aug 16 23:11:29.187: Serial0/0/0: X.25 O D1 Data (4) 8 lci 1024 PS 7 PR 6 0: 1400CE 0D ..N. *Aug 16 23:11:29.187: Serial0/0/0: LAPB O CONNECT (6) IFRAME 7 7*Aug 16 23:11:29.199: Serial0/0/0: LAPB I CONNECT (2) RR (R) 0*Aug 16 23:11:29.211: Serial0/0/0: LAPB I CONNECT (5) IFRAME 7 0*Aug 16 23:11:29.211: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 0 0: 140001 ... *Aug 16 23:11:29.215: Serial0/0/0: LAPB O CONNECT (2) RR (R) 0*Aug 16 23:11:29.223: Serial0/0/0: LAPB I CONNECT (13) IFRAME 0 0*Aug 16 23:11:29.223: Serial0/0/0: X.25 I D1 Data (11) 8 lci 1024 PS 6 PR 0 0: 14000C 0D0A3236 3131423E .....2611B> 11: *Aug 16 23:11:29.223: Serial0/0/0: X.25 O D1 RR (3) 8 lci 1024 PR 7 0: 1400E1 ..a *Aug 16 23:11:29.223: Serial0/0/0: LAPB O CONNECT (5) IFRAME 0 1*Aug 16 23:11:29.231: Serial0/0/0: LAPB I CONNECT (2) RR (R) 1


Step 7 For this portion of the example, Telnet to IP address 192.168.1.229, port 1070 on the 2821 router from a PC using the translate tcp command. This command mediates the TCP/IP session to X.25 with SVC calling X.121 address 3178451061. The call is routed to serial interface 0/0/1 using the x25 route command, as follows:


Following is output from the debug commands on router 2821:

. . .*Aug 16 23:11:39.291: tcppad516: fork started

The following output indicates router 2821 is placing a call on serial interface 0/0/1 with source address 4085272361 to destination address 3178451070. The source address 4085272361 was assigned to serial interface 0/0/1 in the configuration listed in the “Router 2821 Configuration for LAPB Debugging: Example” section. The destination address 3178451070 was assigned in the previous translate tcp command.

*Aug 16 23:11:39.295: Serial0/0/1: X.25 O R1 Call (19) 8 lci 1024



*Aug 16 23:11:39.295: From (10): 4085272361 To (10): 3178161070*Aug 16 23:11:39.295: Facilities: (0)*Aug 16 23:11:39.295: Call User Data (4): 0x01000000 (pad) 0: 14000BAA 31781610 ...*1x.. 8: 70408527 23610001 000000 p@.'#a..... *Aug 16 23:11:39.295: Serial0/0/1: LAPB O CONNECT (21) IFRAME 4 4*Aug 16 23:11:39.311: Serial0/0/1: LAPB I CONNECT (2) RR (R) 5*Aug 16 23:11:39.327: Serial0/0/1: LAPB I CONNECT (7) IFRAME 4 5*Aug 16 23:11:39.327: Serial0/0/1: X.25 I R1 Call Confirm (5) 8 lci 1024*Aug 16 23:11:39.327: From (0): To (0): *Aug 16 23:11:39.327: Facilities: (0) 0: 14000F 0000 ..... *Aug 16 23:11:39.331: Serial0/0/1: LAPB O CONNECT (2) RR (R) 5*Aug 16 23:11:39.331: Serial0/0/1: LAPB I CONNECT (6) IFRAME 5 5*Aug 16 23:11:39.331: Serial0/0/1: X.25 I D1 Data (4) Q 8 lci 1024 PS 0 PR 0 0: 940000 04 .... *Aug 16 23:11:39.331: Serial0/0/1: X.25 O D1 Data (48) Q 8 lci 1024 PS 0 PR 0 0: 940000 00010102 01030204 ........... 11: 01050006 00070408 0009000A 000B0E0C ................ 27: 000D000E 000F0010 7F111512 12130014 ................ 43: 00150016 00 ..... *Aug 16 23:11:39.331: Serial0/0/1: LAPB O CONNECT (50) IFRAME 5 6*Aug 16 23:11:39.331: Serial0/0/1: X.25 O D1 RR (3) 8 lci 1024 PR 1 0: 140021 ..! *Aug 16 23:11:39.331: Serial0/0/1: LAPB O CONNECT (5) IFRAME 6 6*Aug 16 23:11:39.343: Serial0/0/1: LAPB I CONNECT (30) IFRAME 6 5*Aug 16 23:11:39.343: Serial0/0/1: X.25 I D1 Data (28) 8 lci 1024 PS 1 PR 0 0: 140002 54727969 6E672031 ...Trying 1 11: 39322E31 36382E31 302E3636 202E2E2E 92.168.10.66 ... 27: 20 *Aug 16 23:11:39.343: Serial0/0/1: X.25 O D1 RR (3) 8 lci 1024 PR 2 0: 140041 ..A *Aug 16 23:11:39.343: Serial0/0/1: LAPB O CONNECT (5) IFRAME 7 7*Aug 16 23:11:39.359: Serial0/0/1: LAPB I CONNECT (2) RR (R) 6*Aug 16 23:11:39.367: Serial0/0/1: LAPB I CONNECT (2) RR (R) 0*Aug 16 23:11:39.375: Serial0/0/1: LAPB I CONNECT (11) IFRAME 7 0*Aug 16 23:11:39.375: Serial0/0/1: X.25 I D1 Data (9) 8 lci 1024 PS 2 PR 0 0: 140004 4F70656E 0D0A ...Open.. *Aug 16 23:11:39.375: Serial0/0/1: X.25 O D1 RR (3) 8 lci 1024 PR 3 0: 140061 ..a *Aug 16 23:11:39.375: Serial0/0/1: LAPB O CONNECT (5) IFRAME 0 0*Aug 16 23:11:39.387: Serial0/0/1: LAPB I CONNECT (2) RR (R) 1*Aug 16 23:11:39.443: Serial0/0/1: LAPB I CONNECT (8) IFRAME 0 1*Aug 16 23:11:39.443: Serial0/0/1: X.25 I D1 Data (6) Q 8 lci 1024 PS 3 PR 0 0: 940006 060200 ...... *Aug 16 23:11:39.443: tcppad516: Sending WILL ECHO*Aug 16 23:11:39.443: Serial0/0/1: X.25 O D1 Data (6) Q 8 lci 1024 PS 1 PR 3 0: 940062 000200 ..b... *Aug 16 23:11:39.443: Serial0/0/1: LAPB O CONNECT (8) IFRAME 1 1*Aug 16 23:11:39.443: Serial0/0/1: X.25 O D1 RR (3) 8 lci 1024 PR 4 0: 140081 ... *Aug 16 23:11:39.443: Serial0/0/1: LAPB O CONNECT (5) IFRAME 2 1*Aug 16 23:11:39.447: Serial0/0/1: LAPB I CONNECT (14) IFRAME 1 1*Aug 16 23:11:39.447: Serial0/0/1: X.25 I D1 Data (12) Q 8 lci 1024 PS 4 PR 0 0: 940008 06020004 010F0007 ........... 11: 15 . *Aug 16 23:11:39.451: Serial0/0/1: LAPB O CONNECT (2) RR (R) 2*Aug 16 23:11:39.451: Serial0/0/1: LAPB I CONNECT (5) IFRAME 2 1*Aug 16 23:11:39.451: Serial0/0/1: X.25 I D1 RR (3) 8 lci 1024 PR 1 0: 140021 ..! *Aug 16 23:11:39.455: Serial0/0/1: LAPB O CONNECT (2) RR (R) 3*Aug 16 23:11:39.455: Serial0/0/1: LAPB I CONNECT (2) RR (R) 2*Aug 16 23:11:39.459: Serial0/0/1: LAPB I CONNECT (5) IFRAME 3 3*Aug 16 23:11:39.459: Serial0/0/1: X.25 I D1 RR (3) 8 lci 1024 PR 2



0: 140041 ..A *Aug 16 23:11:39.463: Serial0/0/1: LAPB O CONNECT (2) RR (R) 4*Aug 16 23:11:39.483: Serial0/0/1: LAPB I CONNECT (47) IFRAME 4 3*Aug 16 23:11:39.483: Serial0/0/1: X.25 I D1 Data (45) 8 lci 1024 PS 5 PR 2 0: 14004A 0D0A0D0A 55736572 ..J....User 11: 20416363 65737320 56657269 66696361 Access Verifica 27: 74696F6E 0D0A0D0A 50617373 776F7264 tion....Password 43: 3A20 : *Aug 16 23:11:39.487: Serial0/0/1: LAPB O CONNECT (2) RR (R) 5*Aug 16 23:11:39.547: Serial0/0/1: X.25 O D1 Data (12) Q 8 lci 1024 PS 2 PR 4 0: 940084 00020004 010F0007 ........... 11: 15 . *Aug 16 23:11:39.547: Serial0/0/1: LAPB O CONNECT (14) IFRAME 3 5*Aug 16 23:11:39.547: Serial0/0/1: X.25 O D1 RR (3) 8 lci 1024 PR 5 0: 1400A1 ..! *Aug 16 23:11:39.547: Serial0/0/1: LAPB O CONNECT (5) IFRAME 4 5*Aug 16 23:11:39.547: Serial0/0/1: X.25 O D1 RR (3) 8 lci 1024 PR 6 0: 1400C1 ..A *Aug 16 23:11:39.547: Serial0/0/1: LAPB O CONNECT (5) IFRAME 5 5*Aug 16 23:11:39.555: Serial0/0/1: LAPB I CONNECT (2) RR (R) 4*Aug 16 23:11:39.559: Serial0/0/1: LAPB I CONNECT (2) RR (R) 5*Aug 16 23:11:39.567: Serial0/0/1: LAPB I CONNECT (5) IFRAME 5 6*Aug 16 23:11:39.567: Serial0/0/1: X.25 I D1 RR (3) 8 lci 1024 PR 3 0: 140061 ..a *Aug 16 23:11:39.571: Serial0/0/1: LAPB O CONNECT (2) RR (R) 6*Aug 16 23:11:41.407: Serial0/0/1: X.25 O D1 Data (4) 8 lci 1024 PS 3 PR 6 0: 1400C6 63 ..Fc *Aug 16 23:11:41.407: Serial0/0/1: LAPB O CONNECT (6) IFRAME 6 6*Aug 16 23:11:41.419: Serial0/0/1: LAPB I CONNECT (2) RR (R) 7*Aug 16 23:11:41.423: Serial0/0/1: LAPB I CONNECT (5) IFRAME 6 7*Aug 16 23:11:41.423: Serial0/0/1: X.25 I D1 RR (3) 8 lci 1024 PR 4 0: 140081 ... *Aug 16 23:11:41.427: Serial0/0/1: LAPB O CONNECT (2) RR (R) 7*Aug 16 23:11:41.607: Serial0/0/1: X.25 O D1 Data (4) 8 lci 1024 PS 4 PR 6 0: 1400C8 69 ..Hi *Aug 16 23:11:41.607: Serial0/0/1: LAPB O CONNECT (6) IFRAME 7 7*Aug 16 23:11:41.615: Serial0/0/1: LAPB I CONNECT (2) RR (R) 0*Aug 16 23:11:41.623: Serial0/0/1: LAPB I CONNECT (5) IFRAME 7 0*Aug 16 23:11:41.623: Serial0/0/1: X.25 I D1 RR (3) 8 lci 1024 PR 5 0: 1400A1 ..! *Aug 16 23:11:41.627: Serial0/0/1: LAPB O CONNECT (2) RR (R) 0*Aug 16 23:11:41.807: Serial0/0/1: X.25 O D1 Data (4) 8 lci 1024 PS 5 PR 6 0: 1400CA 73 ..Js *Aug 16 23:11:41.807: Serial0/0/1: LAPB O CONNECT (6) IFRAME 0 0*Aug 16 23:11:41.815: Serial0/0/1: LAPB I CONNECT (2) RR (R) 1*Aug 16 23:11:41.823: Serial0/0/1: LAPB I CONNECT (5) IFRAME 0 1*Aug 16 23:11:41.823: Serial0/0/1: X.25 I D1 RR (3) 8 lci 1024 PR 6 0: 1400C1 ..A *Aug 16 23:11:41.827: Serial0/0/1: LAPB O CONNECT (2) RR (R) 1*Aug 16 23:11:42.007: Serial0/0/1: X.25 O D1 Data (5) 8 lci 1024 PS 6 PR 6 0: 1400CC 636F ..Lco *Aug 16 23:11:42.007: Serial0/0/1: LAPB O CONNECT (7) IFRAME 1 1*Aug 16 23:11:42.015: Serial0/0/1: LAPB I CONNECT (2) RR (R) 2*Aug 16 23:11:42.023: Serial0/0/1: LAPB I CONNECT (5) IFRAME 1 2*Aug 16 23:11:42.023: Serial0/0/1: X.25 I D1 RR (3) 8 lci 1024 PR 7 0: 1400E1 ..a *Aug 16 23:11:42.027: Serial0/0/1: LAPB O CONNECT (2) RR (R) 2*Aug 16 23:11:42.243: Serial0/0/1: X.25 O D1 Data (4) 8 lci 1024 PS 7 PR 6 0: 1400CE 0D ..N. *Aug 16 23:11:42.243: Serial0/0/1: LAPB O CONNECT (6) IFRAME 2 2*Aug 16 23:11:42.255: Serial0/0/1: LAPB I CONNECT (2) RR (R) 3*Aug 16 23:11:42.259: Serial0/0/1: LAPB I CONNECT (5) IFRAME 2 3*Aug 16 23:11:42.259: Serial0/0/1: X.25 I D1 RR (3) 8 lci 1024 PR 0 0: 140001 ...



*Aug 16 23:11:42.263: Serial0/0/1: LAPB O CONNECT (2) RR (R) 3*Aug 16 23:11:42.271: Serial0/0/1: LAPB I CONNECT (13) IFRAME 3 3*Aug 16 23:11:42.271: Serial0/0/1: X.25 I D1 Data (11) 8 lci 1024 PS 6 PR 0 0: 14000C 0D0A3236 3131423E .....2611B> 11: *Aug 16 23:11:42.271: Serial0/0/1: X.25 O D1 RR (3) 8 lci 1024 PR 7 0: 1400E1 ..a *Aug 16 23:11:42.271: Serial0/0/1: LAPB O CONNECT (5) IFRAME 3 4*Aug 16 23:11:42.283: Serial0/0/1: LAPB I CONNECT (2) RR (R) 4

Debugging LABP with Interface FilteringThis section repeats the previous commands and steps, but includes the debug interface command with the output.

Step 1 Begin by disabling debugging of the current connections:

2821# no debug allAll possible debugging has been turned off

Step 2 Enable interface filtering on debugging output for serial interface 0/0/0. Wait for the “condition 1 is set” message.

2821# debug interface serial 0/0/0Condition 1 set

Step 3 Enable the debug lapb, debug translate, and debug x25 all dump commands. The dump portion of the debug x25 all dump command displays the data.

2821# debug lapbLAPB link debugging is on

2821# debug translateProtocol Translation debugging is on

2821# debug x25 all dumpX.25 packet debugging is onX.25 packet dump debugging is onX.25 packet dump is enabled for hex and ascii formats2821#

Output for Telnet to 192.168.1.229, Port 1060

Step 4 Repeat the Telnet connections to router 2821 via IP address 192.168.1.229, port 1060.

The output for the first connection follows. Once again, the tcppad515 report indicates that protocol translation is starting on router 2821.

. . .*Aug 16 23:34:05.943: tcppad515: fork started

Router 2821 places a call on serial interface 0/0/0 with source address 4085272368 to destination address 3178451061. Following is sample output:

*Aug 16 23:34:05.947: Serial0/0/0: X.25 O R1 Call (19) 8 lci 1024*Aug 16 23:34:05.947: From (10): 4085272368 To (10): 3178451061*Aug 16 23:34:05.947: Facilities: (0)*Aug 16 23:34:05.947: Call User Data (4): 0x01000000 (pad) 0: 14000BAA 31784510 ...*1xE.



8: 61408527 23680001 000000 a@.'#h..... *Aug 16 23:34:05.947: Serial0/0/0: LAPB O CONNECT (21) IFRAME 3 3*Aug 16 23:34:05.963: Serial0/0/0: LAPB I CONNECT (2) RR (R) 4*Aug 16 23:34:05.991: Serial0/0/0: LAPB I CONNECT (7) IFRAME 3 4*Aug 16 23:34:05.991: Serial0/0/0: X.25 I R1 Call Confirm (5) 8 lci 1024*Aug 16 23:34:05.991: From (0): To (0): *Aug 16 23:34:05.991: Facilities: (0) 0: 14000F 0000 ..... *Aug 16 23:34:05.995: Serial0/0/0: LAPB O CONNECT (2) RR (R) 4*Aug 16 23:34:05.995: Serial0/0/0: LAPB I CONNECT (6) IFRAME 4 4*Aug 16 23:34:05.995: Serial0/0/0: X.25 I D1 Data (4) Q 8 lci 1024 PS 0 PR 0 0: 940000 04 .... *Aug 16 23:34:05.995: Serial0/0/0: X.25 O D1 Data (48) Q 8 lci 1024 PS 0 PR 0 0: 940000 00010102 01030204 ........... 11: 01050006 00070408 0009000A 000B0E0C ................ 27: 000D000E 000F0010 7F111512 12130014 ................ 43: 00150016 00 ..... *Aug 16 23:34:05.995: Serial0/0/0: LAPB O CONNECT (50) IFRAME 4 5*Aug 16 23:34:05.995: Serial0/0/0: X.25 O D1 RR (3) 8 lci 1024 PR 1 0: 140021 ..! *Aug 16 23:34:05.995: Serial0/0/0: LAPB O CONNECT (5) IFRAME 5 5*Aug 16 23:34:06.019: Serial0/0/0: LAPB I CONNECT (30) IFRAME 5 4*Aug 16 23:34:06.019: Serial0/0/0: X.25 I D1 Data (28) 8 lci 1024 PS 1 PR 0 0: 140002 54727969 6E672031 ...Trying 1 11: 39322E31 36382E31 302E3636 202E2E2E 92.168.10.66 ... 27: 20 *Aug 16 23:34:06.019: Serial0/0/0: X.25 O D1 RR (3) 8 lci 1024 PR 2 0: 140041 ..A *Aug 16 23:34:06.019: Serial0/0/0: LAPB O CONNECT (5) IFRAME 6 6*Aug 16 23:34:06.023: Serial0/0/0: LAPB I CONNECT (2) RR (R) 5*Aug 16 23:34:06.027: Serial0/0/0: LAPB I CONNECT (2) RR (R) 6*Aug 16 23:34:06.031: Serial0/0/0: LAPB I CONNECT (2) RR (R) 7*Aug 16 23:34:06.063: Serial0/0/0: LAPB I CONNECT (11) IFRAME 6 7*Aug 16 23:34:06.063: Serial0/0/0: X.25 I D1 Data (9) 8 lci 1024 PS 2 PR 0 0: 140004 4F70656E 0D0A ...Open.. *Aug 16 23:34:06.063: Serial0/0/0: X.25 O D1 RR (3) 8 lci 1024 PR 3 0: 140061 ..a *Aug 16 23:34:06.063: Serial0/0/0: LAPB O CONNECT (5) IFRAME 7 7*Aug 16 23:34:06.075: Serial0/0/0: LAPB I CONNECT (2) RR (R) 0*Aug 16 23:34:06.107: Serial0/0/0: LAPB I CONNECT (8) IFRAME 7 0*Aug 16 23:34:06.107: Serial0/0/0: X.25 I D1 Data (6) Q 8 lci 1024 PS 3 PR 0 0: 940006 060200 ...... *Aug 16 23:34:06.107: tcppad515: Sending WILL ECHO*Aug 16 23:34:06.107: Serial0/0/0: X.25 O D1 Data (6) Q 8 lci 1024 PS 1 PR 3 0: 940062 000200 ..b... *Aug 16 23:34:06.107: Serial0/0/0: LAPB O CONNECT (8) IFRAME 0 0*Aug 16 23:34:06.107: Serial0/0/0: X.25 O D1 RR (3) 8 lci 1024 PR 4 0: 140081 ... *Aug 16 23:34:06.107: Serial0/0/0: LAPB O CONNECT (5) IFRAME 1 0*Aug 16 23:34:06.115: Serial0/0/0: LAPB I CONNECT (14) IFRAME 0 0*Aug 16 23:34:06.115: Serial0/0/0: X.25 I D1 Data (12) Q 8 lci 1024 PS 4 PR 0 0: 940008 06020004 010F0007 ........... 11: 15 . *Aug 16 23:34:06.119: Serial0/0/0: LAPB O CONNECT (2) RR (R) 1*Aug 16 23:34:06.119: Serial0/0/0: LAPB I CONNECT (5) IFRAME 1 0*Aug 16 23:34:06.119: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 1 0: 140021 ..! *Aug 16 23:34:06.119: Serial0/0/0: LAPB I CONNECT (2) RR (R) 1*Aug 16 23:34:06.123: Serial0/0/0: LAPB O CONNECT (2) RR (R) 2*Aug 16 23:34:06.123: Serial0/0/0: LAPB I CONNECT (2) RR (R) 2*Aug 16 23:34:06.131: Serial0/0/0: LAPB I CONNECT (5) IFRAME 2 2*Aug 16 23:34:06.131: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 2 0: 140041 ..A *Aug 16 23:34:06.135: Serial0/0/0: LAPB O CONNECT (2) RR (R) 3



*Aug 16 23:34:06.167: Serial0/0/0: LAPB I CONNECT (47) IFRAME 3 2*Aug 16 23:34:06.167: Serial0/0/0: X.25 I D1 Data (45) 8 lci 1024 PS 5 PR 2 0: 14004A 0D0A0D0A 55736572 ..J....User 11: 20416363 65737320 56657269 66696361 Access Verifica 27: 74696F6E 0D0A0D0A 50617373 776F7264 tion....Password 43: 3A20 : *Aug 16 23:34:06.171: Serial0/0/0: LAPB O CONNECT (2) RR (R) 4*Aug 16 23:34:06.215: Serial0/0/0: X.25 O D1 Data (12) Q 8 lci 1024 PS 2 PR 4 0: 940084 00020004 010F0007 ........... 11: 15 . *Aug 16 23:34:06.215: Serial0/0/0: LAPB O CONNECT (14) IFRAME 2 4*Aug 16 23:34:06.215: Serial0/0/0: X.25 O D1 RR (3) 8 lci 1024 PR 5 0: 1400A1 ..! *Aug 16 23:34:06.215: Serial0/0/0: LAPB O CONNECT (5) IFRAME 3 4*Aug 16 23:34:06.215: Serial0/0/0: X.25 O D1 RR (3) 8 lci 1024 PR 6 0: 1400C1 ..A *Aug 16 23:34:06.215: Serial0/0/0: LAPB O CONNECT (5) IFRAME 4 4*Aug 16 23:34:06.227: Serial0/0/0: LAPB I CONNECT (2) RR (R) 3*Aug 16 23:34:06.231: Serial0/0/0: LAPB I CONNECT (2) RR (R) 4*Aug 16 23:34:06.235: Serial0/0/0: LAPB I CONNECT (2) RR (R) 5*Aug 16 23:34:06.243: Serial0/0/0: LAPB I CONNECT (5) IFRAME 4 5*Aug 16 23:34:06.243: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 3 0: 140061 ..a *Aug 16 23:34:06.247: Serial0/0/0: LAPB O CONNECT (2) RR (R) 5*Aug 16 23:34:07.919: Serial0/0/0: X.25 O D1 Data (4) 8 lci 1024 PS 3 PR 6 0: 1400C6 63 ..Fc *Aug 16 23:34:07.919: Serial0/0/0: LAPB O CONNECT (6) IFRAME 5 5*Aug 16 23:34:07.931: Serial0/0/0: LAPB I CONNECT (2) RR (R) 6*Aug 16 23:34:07.943: Serial0/0/0: LAPB I CONNECT (5) IFRAME 5 6*Aug 16 23:34:07.943: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 4 0: 140081 ... *Aug 16 23:34:07.947: Serial0/0/0: LAPB O CONNECT (2) RR (R) 6*Aug 16 23:34:08.119: Serial0/0/0: X.25 O D1 Data (4) 8 lci 1024 PS 4 PR 6 0: 1400C8 69 ..Hi *Aug 16 23:34:08.119: Serial0/0/0: LAPB O CONNECT (6) IFRAME 6 6*Aug 16 23:34:08.131: Serial0/0/0: LAPB I CONNECT (2) RR (R) 7*Aug 16 23:34:08.143: Serial0/0/0: LAPB I CONNECT (5) IFRAME 6 7*Aug 16 23:34:08.143: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 5 0: 1400A1 ..! *Aug 16 23:34:08.147: Serial0/0/0: LAPB O CONNECT (2) RR (R) 7*Aug 16 23:34:08.319: Serial0/0/0: X.25 O D1 Data (4) 8 lci 1024 PS 5 PR 6 0: 1400CA 73 ..Js *Aug 16 23:34:08.319: Serial0/0/0: LAPB O CONNECT (6) IFRAME 7 7*Aug 16 23:34:08.331: Serial0/0/0: LAPB I CONNECT (2) RR (R) 0*Aug 16 23:34:08.339: Serial0/0/0: LAPB I CONNECT (5) IFRAME 7 0*Aug 16 23:34:08.339: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 6 0: 1400C1 ..A *Aug 16 23:34:08.343: Serial0/0/0: LAPB O CONNECT (2) RR (R) 0*Aug 16 23:34:08.519: Serial0/0/0: X.25 O D1 Data (5) 8 lci 1024 PS 6 PR 6 0: 1400CC 636F ..Lco *Aug 16 23:34:08.519: Serial0/0/0: LAPB O CONNECT (7) IFRAME 0 0*Aug 16 23:34:08.531: Serial0/0/0: LAPB I CONNECT (2) RR (R) 1*Aug 16 23:34:08.543: Serial0/0/0: LAPB I CONNECT (5) IFRAME 0 1*Aug 16 23:34:08.543: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 7 0: 1400E1 ..a *Aug 16 23:34:08.547: Serial0/0/0: LAPB O CONNECT (2) RR (R) 1*Aug 16 23:34:08.851: Serial0/0/0: X.25 O D1 Data (4) 8 lci 1024 PS 7 PR 6 0: 1400CE 0D ..N. *Aug 16 23:34:08.851: Serial0/0/0: LAPB O CONNECT (6) IFRAME 1 1*Aug 16 23:34:08.863: Serial0/0/0: LAPB I CONNECT (2) RR (R) 2*Aug 16 23:34:08.875: Serial0/0/0: LAPB I CONNECT (5) IFRAME 1 2*Aug 16 23:34:08.875: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1024 PR 0 0: 140001 ... *Aug 16 23:34:08.879: Serial0/0/0: LAPB O CONNECT (2) RR (R) 2



*Aug 16 23:34:08.887: Serial0/0/0: LAPB I CONNECT (13) IFRAME 2 2*Aug 16 23:34:08.887: Serial0/0/0: X.25 I D1 Data (11) 8 lci 1024 PS 6 PR 0 0: 14000C 0D0A3236 3131423E .....2611B> 11: *Aug 16 23:34:08.887: Serial0/0/0: X.25 O D1 RR (3) 8 lci 1024 PR 7 0: 1400E1 ..a *Aug 16 23:34:08.887: Serial0/0/0: LAPB O CONNECT (5) IFRAME 2 3*Aug 16 23:34:08.899: Serial0/0/0: LAPB I CONNECT (2) RR (R) 3


Step 5 Once again, use Telnet to connect to 192.168.1.229, port 1070 on the 2821 router from a PC. The translate tcp command mediates the TCP/IP session to X.25 with SVC calling X.121 address 3178451070. The call is routed to serial 0/0/1 via the x25 route command.


Following is the start of output from the debug commands. The tcppad515 report indicates that protocol translation is starting.

*Aug 16 23:34:14.367: tcppad516: fork started

Router 2821 places a call on serial interface 0/0/1 with source address 4085272361 to destination address 3178451070. The source address 4085272361 was assigned to the interface serial 0/0/0 in the configuration listed in the “Router 2821 Configuration for LAPB Debugging: Example” section. The destination address 3178451070 was assigned in the previous translate tcp command.

Notice in the following output that the X.25 connection is made and data is passed across serial interface 0/0/1, but no information about LAPB packets is displayed:

*Aug 16 23:34:14.367: Serial0/0/1: X.25 O R1 Call (19) 8 lci 1024*Aug 16 23:34:14.367: From (10): 4085272361 To (10): 3178161070*Aug 16 23:34:14.367: Facilities: (0)*Aug 16 23:34:14.367: Call User Data (4): 0x01000000 (pad) 0: 14000BAA 31781610 ...*1x.. 8: 70408527 23610001 000000 p@.'#a..... *Aug 16 23:34:14.403: Serial0/0/1: X.25 I R1 Call Confirm (5) 8 lci 1024*Aug 16 23:34:14.403: From (0): To (0): *Aug 16 23:34:14.403: Facilities: (0) 0: 14000F 0000 ..... *Aug 16 23:34:14.407: Serial0/0/1: X.25 I D1 Data (4) Q 8 lci 1024 PS 0 PR 0 0: 940000 04 .... *Aug 16 23:34:14.407: Serial0/0/1: X.25 O D1 Data (48) Q 8 lci 1024 PS 0 PR 0 0: 940000 00010102 01030204 ........... 11: 01050006 00070408 0009000A 000B0E0C ................ 27: 000D000E 000F0010 7F111512 12130014 ................ 43: 00150016 00 ..... *Aug 16 23:34:14.407: Serial0/0/1: X.25 O D1 RR (3) 8 lci 1024 PR 1 0: 140021 ..! *Aug 16 23:34:14.419: Serial0/0/1: X.25 I D1 Data (28) 8 lci 1024 PS 1 PR 0 0: 140002 54727969 6E672031 ...Trying 1 11: 39322E31 36382E31 302E3636 202E2E2E 92.168.10.66 ... 27: 20 *Aug 16 23:34:14.419: Serial0/0/1: X.25 O D1 RR (3) 8 lci 1024 PR 2 0: 140041 ..A *Aug 16 23:34:14.451: Serial0/0/1: X.25 I D1 Data (9) 8 lci 1024 PS 2 PR 0 0: 140004 4F70656E 0D0A ...Open.. *Aug 16 23:34:14.451: Serial0/0/1: X.25 O D1 RR (3) 8 lci 1024 PR 3 0: 140061 ..a *Aug 16 23:34:14.519: Serial0/0/1: X.25 I D1 Data (6) Q 8 lci 1024 PS 3 PR 0 0: 940006 060200 ...... *Aug 16 23:34:14.519: tcppad516: Sending WILL ECHO



*Aug 16 23:34:14.519: Serial0/0/1: X.25 O D1 Data (6) Q 8 lci 1024 PS 1 PR 3 0: 940062 000200 ..b... *Aug 16 23:34:14.519: Serial0/0/1: X.25 O D1 RR (3) 8 lci 1024 PR 4 0: 140081 ... *Aug 16 23:34:14.527: Serial0/0/1: X.25 I D1 Data (12) Q 8 lci 1024 PS 4 PR 0 0: 940008 06020004 010F0007 ........... 11: 15 . *Aug 16 23:34:14.531: Serial0/0/1: X.25 I D1 RR (3) 8 lci 1024 PR 1 0: 140021 ..! *Aug 16 23:34:14.539: Serial0/0/1: X.25 I D1 RR (3) 8 lci 1024 PR 2 0: 140041 ..A *Aug 16 23:34:14.563: Serial0/0/1: X.25 I D1 Data (45) 8 lci 1024 PS 5 PR 2 0: 14004A 0D0A0D0A 55736572 ..J....User 11: 20416363 65737320 56657269 66696361 Access Verifica 27: 74696F6E 0D0A0D0A 50617373 776F7264 tion....Password 43: 3A20 : *Aug 16 23:34:14.627: Serial0/0/1: X.25 O D1 Data (12) Q 8 lci 1024 PS 2 PR 4 0: 940084 00020004 010F0007 ........... 11: 15 . *Aug 16 23:34:14.627: Serial0/0/1: X.25 O D1 RR (3) 8 lci 1024 PR 5 0: 1400A1 ..! *Aug 16 23:34:14.627: Serial0/0/1: X.25 O D1 RR (3) 8 lci 1024 PR 6 0: 1400C1 ..A *Aug 16 23:34:14.647: Serial0/0/1: X.25 I D1 RR (3) 8 lci 1024 PR 3 0: 140061 ..a *Aug 16 23:34:15.935: Serial0/0/1: X.25 O D1 Data (4) 8 lci 1024 PS 3 PR 6 0: 1400C6 63 ..Fc *Aug 16 23:34:15.955: Serial0/0/1: X.25 I D1 RR (3) 8 lci 1024 PR 4 0: 140081 ... *Aug 16 23:34:16.135: Serial0/0/1: X.25 O D1 Data (4) 8 lci 1024 PS 4 PR 6 0: 1400C8 69 ..Hi *Aug 16 23:34:16.151: Serial0/0/1: X.25 I D1 RR (3) 8 lci 1024 PR 5 0: 1400A1 ..! *Aug 16 23:34:16.335: Serial0/0/1: X.25 O D1 Data (4) 8 lci 1024 PS 5 PR 6 0: 1400CA 73 ..Js *Aug 16 23:34:16.351: Serial0/0/1: X.25 I D1 RR (3) 8 lci 1024 PR 6 0: 1400C1 ..A

. . .


A
P P E N D I X B References



IntroductionThis appendix contains references related to information in the chapters of this document, as follows:

• References for Telephone Switch Environments, page B-2

• References for Transmission Equipment in X.25 Environments, page B-3

• References for SONET/SDH OSI Environments, page B-4

• References for MPLS in the DCN, page B-5

• References for X.25 Toolkit, page B-5

B-1Cisco Network Solutions for the Telco DCN


Appendix B ReferencesReferences for Telephone Switch Environments

References for Telephone Switch EnvironmentsRelated Standards and Topics for Telephone Switch Environments Document Title

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 • CCITT 1980 Recommendation X.25

• CCITT 1984 Recommendation X.25

• CCITT 1988 Recommendation X.25

• ITU-T 1993 Recommendation X.25

Related Websites for Telephone Switch Environments Link

4Tel http://www.edb4tel.com/

EVOLVING Systems (TDMS support) http://www.evolving.com/site/home/

Kansys, Inc http://www.kansys.com

Lucent OS http://www.lucent.com/

Lucent Billdats http://www.lucent.com/solutions/

Intec http://www.intec-telecom-systems.com/

Telesciences http://www.telesciences.com/

TTI Telecom http://www.tti-telecom.com


http://www.edb4tel.com/

http://www.cms-c.com/

http://www.evolving.com/site/home/

http://www.kansys.com

http://www.lucent.com/

http://www.lucent.com/solutions/

http://www.intec-telecom-systems.com/

http://www.telesciences.com/

http://www.tti-telecom.com/



Appendix B ReferencesReferences for Transmission Equipment in X.25 Environments

References for Transmission Equipment in X.25 EnvironmentsRelated Standards and Topics for Transmission Equipment in X.25 Environments Document Title

DNS-based X.25 routing DNS-Based X.25 Routing, Cisco IOS Release 12.0(1)T feature module

Transaction Language 1 (TL1) GR-831-CORE, Operations Application Messages - Language For Operations Application Messages

X.25 configuration Cisco IOS Wide-Area Networking Configuration Guide, Release 12.4T

X.25 PAD configuration Cisco IOS Terminal Services Configuration Guide, Release 12.4

X.25 regular expressions “Regular Expressions” chapter in the Cisco IOS Dial Technologies Configuration Guide, Release 12.2

X.25 version selection X.25 Version Configuration, Cisco IOS Release 12.3(8)T feature module

X.3 PAD parameters “X.3 PAD Parameters” appendix in the Cisco IOS Terminal Services Configuration Guide, Release 12.2

Related Websites for Transmission Equipment in X.25 Environments Link

Alcatel 1633 SX multiplexer Information http://www.findarticles.com/p/articles/mi_m0TPY/is_6_234/ai_59667749

Alcatel 1603 SM OC-3 (155 Mbps) SONET Transport System

http://www.alcatel.com/products/productsummary.jhtml?relativePath=/com/en/appxml/opgproduct/alcatel1603smoc3155mbpssonettransportsystemustcm228114621635.jhtml

Litespan products http://www.usa.alcatel.com/products/productsbyreference.jhtml?productRange=LITESPAN&pageNumber=1

RFCs for Transmission Equipment in X.25 Environments Title

RFC 1381 SNMP MIB Extension for X.25 LAPB

RFC 1382 SNMP MIB Extension for the X.25 Packet Layer

RFC 1613 Cisco Systems X.25 over TCP (XOT)


http://www.findarticles.com/p/articles/mi_m0TPY/is_6_234/ai_59667749

http://www.alcatel.com/products/productsummary.jhtml?relativePath=/com/en/appxml/opgproduct/alcatel1603smoc3155mbpssonettransportsystemustcm228114621635.jhtm

http://www.usa.alcatel.com/products/productsbyreference.jhtml?productRange=LITESPAN&pageNumber=1

http://www.cisco.com/en/US/products/ps6441/products_configuration_guide_book09186a0080755197.html

http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_book09186a00804402fe.html





Appendix B ReferencesReferences for SONET/SDH OSI Environments

References for SONET/SDH OSI EnvironmentsRelated Standards and Topics for SONET/SDH OSI Environments Document Title

Bandwidth signaling applications • ITU-T G.807, Requirements for the Automatic Switched Transport Network (ASTN)

• ITU-T G.8080, Architecture for the Automatic Switched Optical Network (ASON)

• Optical Internetworking Forum (OIF) User Network Interface (UNI) 1.0

Cisco IS-IS technical support Integrated Intermediate System-to-Intermediate System (IS-IS) Cisco IOS support page

CLNS tunnel configuration • IP over a CLNS Tunnel, Cisco IOS Release 12.1(5)T feature module

• CLNS Support for GRE Tunneling of IPv4 and IPv6 Packets in CLNS Networks, Cisco IOS Release 12.3(7)T feature module

IP requirements for a DCN ITU-T G.7712/Y.1703, Architecture and Specification of the Data Communication Network

IS-IS attach-bit Using the IS-IS Attach-Bit Control Feature, Cisco IOS Product Marketing Application Note

NM-AIC-64 configuration NM-AIC-64, Contact Closure Network Module, Cisco IOS Release 12.2(8)T feature module

NSAP address structure American National Standard X3.216-1992, Structure and Semantics of the Domain Specific Part of the Network Service Access Point Address

NSAP IDP structure • ITU-T E.164

• ITU-T F.69

• ITU-T X.121

• ISO DCC

• ISO 6523-ICD

Optical internetworking Optical Internetworking Forum (OIF) User Network Interface (UNI) 1.0

OSI addressing issues ITU-T X.213, Data Networks and Open Systems Communications Open Systems Interconnections Service Definitions

SONET requirements for a DCN • Telcordia Specification, Issue 3 of GR-253-CORE, Synchronous Optical Network (SONET) Transport Systems: Common Criteria

• M.3010, Principles for a Telecommunications Management Network

Telcordia SONET transport systems Telcordia Specification, Issue 3 of GR-253-CORE, Synchronous Optical Network (SONET) Transport Systems: Common Criteria, Section 8


http://www.cisco.com/en/US/tech/tk365/tk381/tsd_technology_support_sub-protocol_home.html





http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ft_aicnm.htm

Appendix B ReferencesReferences for MPLS in the DCN

References for MPLS in the DCN

References for X.25 Toolkit

RFCs for SONET/SDH OSI Environments Title

RFC 2763 Dynamic Hostname Exchange Mechanism for IS-IS (Informational)

ITU-T G.7712/Y.1703 Architecture and Specification of the Data Communication Network

ITU-T G.807 Requirements for the Automatic Switched Transport Network (ASTN)

ITU-T G.8080 Architecture for the Automatic Switched Optical Network (ASON)

ITU-T M.3010 Principles for a Telecommunications Management Network

ITU-T X.213 Data Networks and Open Systems Communications Open Systems Interconnections Service Definitions

American National Standard X3.216-199 Structure and Semantics of the Domain Specific Part of the Network Service Access Point Address

Related Standards and Topics for MPLS in the DCN Document Title

MPLS overview Multiprotocol Label Switching (MPLS) Cisco IOS Product Marketing literature page

MPLS platform support MPLS VPN and Multi-Virtual Route Forwarding Support for Cisco ISR Cisco IOS Product Marketing Application Note

Related Standards and Topics for X.25 Toolkit Document Title

Receive and initiate PAD calls on the same terminal line using full X.121 addresses.

Multi-PAD Support for X.25 Connections, Cisco IOS Release 12.4(4)T feature module

Enable a router to negotiate X.25 throughput parameters on behalf of end devices.

X.25 Throughput Negotiation, Cisco IOS Release 12.4(4)T feature module

Cisco X.25 and LAPB configuration and debugging commands

Cisco IOS Wide-Area Networking Configuration Guide, Release 12.2, in the chapter “Configuring X.25 and LAPB,” and in the Cisco IOS Wide-Area Networking Command Reference, Release 12.2, in the chapter “X.25 and LAPB Commands.”




http://www.cisco.com/en/US/products/ps6557/products_ios_technology_home.html

http://www.cisco.com/en/US/partner/products/ps6441/products_feature_guide09186a0080530694.html


http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fwan_c/index.htm

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fwan_r/index.htm

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fwan_r/index.htm

Appendix B ReferencesReferences for X.25 Toolkit


G L O S S A R Y


A

ADM Add/drop multiplexer.

AFI Authority and format identifier.

ANSI American National Standards Institute.

ASCII American Standard Code for Information Interchange.

ATM Asynchronous Transfer Mode. The international standard for cell relay in which multiple service types (such as voice, video, or data) are conveyed in fixed-length (53-byte) cells. Fixed-length cells allow cell processing to occur in hardware, thereby reducing transit delays. ATM is designed to take advantage of high-speed transmission media, such as E3, SONET, and T3.

B

BAI Backup Active Interface.

BCD Binary Coded Decimal.

BX.25 AT&T Bell Laboratories’ variation of the ITU X.25 standard.

C

CCITT Consultative Committee for International Telegraph and Telephone.

CDR Call detail record, which is used to create a telephone bill.

CE Customer edge router.

CLEC Competitive local exchange carrier.

CLNP Connectionless Network Protocol. The OSI network layer protocol that does not require a circuit to be established before data is transmitted.

CMTS Centralized maintenance test system.

CO Central office.

GL-1Cisco Network Solutions for the Telco DCN

Glossary

CPU Central processing unit.

CTS Clear To Send signal is used in EIA/TIA-232 communication to indicate to the modem that it can send data to the peer modem. This is the input signal. Usually, RTS output signal of the peer modem is connected to CTS and is used for flow control.

CUD Call User Data.

D

DCC Data communications channel.

DCE Data communications equipment (EIA expansion); data circuit-terminating equipment (ITU-T expansion).

DCN Data communications network.

DCS Digital cross-connect system.

DFI Domain specific part format identifier.

DIS Designated Intermediate System.

DLCI Data-link connection identifier.

DNS Domain Name System.

DRM Lucent Distinctive Remote Module.

DSLAMs Digital subscriber line access multiplexers. A device that connects many digital subscriber lines to a network by multiplexing the DSL traffic onto one or more network trunk lines.

DSP Domain Specific Part.

DSR (RING) Data Set Ready signal is used in EIA/TIA-232 communication to indicate to the modem that the peer modem wants to dial in. This is the input signal and is typically connected to DTR output of the peer modem.

DTE Data terminal equipment.

DTR Data Terminal Ready signal is used to indicate to the peer modem that this modem wants to dial in to the peer modem. This is the output signal.

E

EB Echo Back.

EDAS Engineering Data Acquisition System.

EIA/TIA Electronic Industries Alliance/Telecommunications Industry Alliance.


Glossary

EMM Element Mediation Module.

EOR End of record.

ES End system.

ESH End System Hello.

F

FTAM File Transfer, Access, and Management.

G

GNE Gateway network element. A gateway refers to a special-purpose device that performs an application-layer conversion of information from one protocol stack to another.

GRE Generic routing encapsulation. Tunneling protocol developed by Cisco that can encapsulate a wide variety of protocol packet types inside IP tunnels, creating a virtual point-to-point link to Cisco routers at remote points over an IP internetwork. By connecting multiprotocol subnetworks in a single-protocol backbone environment, IP tunneling using GRE allows network expansion across a single-protocol backbone environment.

GUI Graphical user interface.

I

IDI Initial domain identifier.

IDP Initial Domain Part.

IECs Inter-exchange carriers.

IEEE Institute of Electrical and Electronics Engineers.

IETF Internet Engineering Task Force.

I-Frame Information Frame.

IIH IS-IS Hello message.

ILEC Incumbent local exchange carrier.

IS Intermediate System.

ISH Intermediate System Hello.

IS-IS Intermediate System-to-Intermediate System. OSI protocol that specifies how routers communicate with routers in different domains.


Glossary

ISL Inter-Switch Link. Cisco-proprietary protocol that maintains VLAN information as traffic flows between switches and routers.

ISO CLNS International Standards Organization Connectionless Network Service.

ISO DCC Data Country Code.

ISO/IEC International Organization for Standardization/International Electrotechnical Commission.

ISO-IGRP Interior Gateway Routing Protocol developed by Cisco for ISO CLNS.

ITU International Telecommunication Union.

IXC Inter-exchange carriers.

L

LAPB Link Access Procedure, Balanced. Data link layer protocol in the X.25 protocol stack. LAPB is a bit-oriented protocol derived from HDLC.

LCI Logical channel identifier.

LCN Logical channel number.

LDB Loop detection buffer.

LDP Label Distribution Protocol.

LECs Local exchange carriers.

LSP Line-state packet; link-state packet; label-switched path.

LSR Label/tag switch router, which is a P router.

M

MAC Media Access Control.

M-bit More data bit.

MIB Management Information Base.

modem modulator-demodulator. Device that converts digital and analog signals. At the source, a modem converts digital signals to a form suitable for transmission over analog communication facilities. At the destination, the analog signals are returned to their digital form. Modems allow data to be transmitted over voice-grade telephone lines.

MPLS Multiprotocol Label Switching. MPLS supports multiple transport protocols such as IP and IPX, and can be transported over multiple Layer 2 protocols such as Frame Relay, ATM, Ethernet, or FDDI.


Glossary

MSC GSM Global System for Mobile Telecommunications mobile switching center.

MUX Multiplexer. Equipment that enables several data streams to be sent over a single physical line. It is also a function by which one connection from an (ISO) layer is used to support more than one connection to the next higher layer. A device for combining several channels to be carried by one line or fiber.

N

NEBS Network Equipment Building Systems.

NET Network entity title.

NFM Network Fault Management.

NMA Network Management Application from Telcordia.

NOC Network operations center.

NSAP Network service access point.

O

OAM Operation, Administration, and Maintenance.

OAM&P Operations, Administration, Maintenance, and Provisioning.

OCS Optical convergence switch.

OSI Open System Interconnection.

OSS Operations Support Systems.

OSSI Operations support system interface (DOCSIS specification).

P

P Provider router located in the interior of a VPN network and performs label and tag switching.

PAD Packet assembler/disassembler. A service specified for X.25 networks and standardized by ITU-Recommendations X.3, X.28,. and X.29, which define a way for asynchronous character-mode terminals (DTE-Cs) to use a packet switching network.

PDN Public data network.

PDUs Protocol data units.

PE Provider edge router that sits on the MPLS/VPN edge and performs tag binding and removal on packets from and to the CE router.


Glossary

PSTN Public switched telephone network.

PTT Post, Telephone, and Telegraph.

PVC Permanent virtual circuit.

Q

Q-bit Used in an X.25 frame to differentiate control frames from data frames. Cisco’s RBP Q-bit solution identifies control frames and data frames in the RBP six-byte header.

R

RBOC Regional Bell operating company.

RBP Record Boundary Preservation.

RC Recent Change.

rotary group A group of one or more lines used for incoming PAD calls. The rotary group is chosen from the subaddress portion of the destination address. Subaddresses in a range from 1 to 99 are tied to rotaries. A subaddress of zero (or trailing zeros) is accepted by the router on the first available vty line.

RR Route reflectors, which are used in BGP to reduce iBGP peer sessions.

RTS Ready To Send signal used in EIA/TIA-232 communication to indicate to the peer modem that it can send data. This is output signal.

S

SABM Set Asynchronous Balance Mode.

SARTS Switched Access Remote Test System.

SCC Specialized common carrier.

SCID System-called identifier.

SDH Synchronous Digital Hierarchy.

SLA Service-level agreement.

SLM Synchronous Line Module.

SNMP Simple Network Management Protocol. Network management protocol used almost exclusively in TCP/IP networks. SNMP provides a means to monitor and control network devices, and to manage configurations, statistics collection, performance, and security.

SNPA Subnetwork point of attachment.


Glossary

SONET Synchronous Optical Network. A standard format for transporting a wide range of digital telecommunications services over optical fiber. SONET is characterized by standard line rates, optical interfaces, and signal formats.

STUN Serial tunnel. Router feature allowing two SDLC- or HDLC-compliant devices to connect to one another through an arbitrary multiprotocol topology using Cisco routers rather than through a direct serial link.

subaddress X.121 addresses are composed of two subfields in a Call Request packet sent when initiating a session. The second subfield currently consists of a two-character numeric value referred to as a subaddress. Permissible subaddress values range from 0 to 99 and are padded with leading zeros when necessary. Following are examples of legal subaddresses: 00, 09, 10, and 99. Either a physical port number or a numeric value for a line is used as a subaddress for PAD connections.

SVC Switched virtual circuit. Virtual circuit that is dynamically established on demand and is torn down when transmission is complete. SVCs are used in situations where data transmission is sporadic.

T

TARP Target Identifier Address Resolution Protocol. In OSS, a protocol that resolves a TL-1 TID to a CLNP address (NSAP).

TCP/IP Transmission Control Protocol/Internet Protocol.

TDM Time-division multiplexing.

TDMS Traffic Data Management System.

telco Telephone company.

TID Target identifier.

TL1 Transaction Language 1.

TMN Telecommunications Management Network.

TTL Time-to-Live field.

U

UID User or unique identifier.

URC Update remote cache.


Glossary

V

VC Virtual circuit; virtual connections (XOT). Logical circuit created to ensure reliable communication between two network devices. A virtual circuit is defined by a VPI/VCI pair, and can be either permanent (PVC) or switched (SVC).

VLAN Virtual LAN. Group of devices on one or more LANs that are configured using management software so that they can communicate as if they were attached to the same wire, when in fact they are located on a number of different LAN segments. Because VLANs are based on logical instead of physical connections, they are extremely flexible.

VRF A VPN routing/forwarding instance. A VRF consists of an IP routing table, a derived forwarding table, a set of interfaces that use the forwarding table, and a set of rules and routing protocols that determine what goes into the forwarding table. In general, a VRF includes the routing information that defines a customer VPN site that is attached to a PE router.

vty Virtual terminal.

X

X.121 ITU-T standard that describes an addressing scheme used in X.25 networks.

X.25 ITU-T standard that defines how connections between DTE and DCE are maintained for remote terminal access and computer communications in PDNs. X.25 specifies LAPB, a data link layer protocol, and Packet Level Protocol (PLP), a network layer protocol.

X.28 ITU-T standard that defines the user interface for an X.25 PAD. All user-entered commands and responses by the PAD are defined by this standard.

XOT X.25 over TCP.


I N D E X

A

ADC Soneplex

port-3 pinout (table) 3-21

protocol translation, testing 3-26

protocol translation router, configuring 3-23

provisioning for X.25 3-21

Alcatel 1603 SM

cable requirements 3-34




Alcatel 1633 SX DCS





Alcatel DCS-DEXCS





Alcatel Litespan




ANSI DSP, structure (figure) 4-14

applications

4Tel 2-6

ADC Service Activation, provisioning 2-97

CDR 2-6

Cisco ISC Version 4.0 5-12

CONNECTVU-ATP, configuring 2-81

EMM, connection using STUN (figure) 2-41, 2-46

Inter-mediatE 2-21

Portal Definition window 2-33

Lucent Billdats 2-6

Lucent CONNECTVU-ATP 2-80

Lucent DRM, monitoring 2-67

Lucent NFM, connection using STUN (figure) 2-41

network management alarms 3-67

OSS monitoring 2-39

Sterling 5000 Collector 2-6

switch monitoring 2-40

TDMS 2-100

telco provisioning 2-80

Telcordia NMA switch monitoring 2-51

traffic data collection 2-101

TTI Telecom Monitoring 2-77

Applied Digital T3AS DCS





TL1 asynchronous 25-pin arrangement (table) 3-59

TL1-to-X.25 pin arrangement (table) 3-59

ATM (Asynchronous Transfer Mode), defined GL-1

B

BX.25

as transport mechanism 2-2

security I-Frame 2-6

X.25, compared 2-2, 2-6

IN-1Cisco Network Solutions for the Telco DCN

Index

C

cable requirements

Alcatel 1603 SM 3-34

Alcatel 1633 SX DCS 3-39

Applied Digital T3AS DCS 3-58

Fujitsu SONET GNE 3-14

CDR (call detail record)

bill collection network (figure) 2-5

Mercury Mediation device 2-5

XOT support for 2-17

Sterling 5000 Collector 2-5

(examples) 2-12

XOT as transport mechanism 2-6

CDR bill collection networks

Cisco XOT and RBP solutions 2-5

data collection and storage 2-5

Cisco EOR (End of Record)

Cisco router on telephone switch side 2-69

(example) 2-73

overview 2-69

CLNP (Connectionless Network Protocol), defined GL-1

console, asynchronous configuration of 3-12

Contact Closure Device

configuring 4-53

Telco DCN data flow to (figure) 4-51

core network

configuration (examples) 4-93

configuring 4-93

redundancy in 4-99

sample (figure) 4-93

tunneling across 4-100

core router

first 4-94

in IS-IS network 4-94

remaining 4-100

second 4-96

third 4-97


CTS (Clear To Send), defined GL-2

D

Datakit node


Synchronous Line Module (SLM) cards 2-40

DCN (data communications network)

application-specific (figure) 5-7

Cisco IP end-to-end solution 3-4

migrating to Cisco solutions 3-2

MPLS in 5-1, 5-2

multiple 5-6

network elements in (figure) 1-2

OSI network, building 4-1

OSI protocol stack and CLNS packet flow (figure) 4-5

out-of-band operations support network (figure) 1-2

overview (figure) 1-2

router-based, building 3-1

SONET/SDH, scaling for 4-1

SONET/SDH DCC as an extension of 4-50

three-tiered architecture 4-12

(figure) 4-87

Level1/Level2 adjacencies (figure) 4-88

Level2 adjacencies (figure) 4-89

vendor-specific (figure) 5-8

DIS (Designated Intermediate System), election process 4-25

distribution network

configuration (example) 4-89

configuring 4-87

OSI domains (figure) 4-87

Index

document organization 1-3

DRM (Lucent Distinctive Remote Module), monitoring 2-67

DSLAMs (digital subscriber line access multiplexers), defined GL-2

DSR (Data Set Ready), defined GL-2

DTR (Data Terminal Ready), defined GL-2

E

echo back port, router configuration 2-82

enterprise network

OSS, migrating to (figure) 5-5

F

file types

Bellcore 385 AMATPS 2-21, 2-35

GPT 2-21

MNP 2-4, 2-21, 2-26

MTP 2-4, 2-24

Nortel XFER 2-21

Fujitsu SONET GNE


OSSI cable requirements (table) 3-14




G

GNE (gateway network element), defined GL-3

GRE (generic routing encapsulation)

defined GL-3

partition prevention using 4-38

tunnels

broken connection (figure) 4-44

CLNS over 4-39

configuring 4-40

I

IEEE 802.1Q encapsulation

VLAN, verifying 4-33

VLAN configuration (example) 4-33

IEEE 802.1Q trunking

IS-IS multiareas, defining 4-31

IEEE 802.1Q trunk router, configuring 4-32

IGRP routing protocol, configuring 4-96

IP backbone

CDR data over high-speed 2-5

(figure) 2-4

RBP 2-3

STUN 2-3

XOT 2-3

IP over CLNS tunnels

configuring 4-51

remote device access 4-50

IS-IS (Intermediate System-to-Intermediate System), defined GL-3

IS-IS adjacency, verifying 4-72

IS-IS Attach-Bit Control feature

broken link (figure) 4-48

configured (figure) 4-46

routing traffic between areas 4-45

verifying 4-46

IS-IS multiarea network

consolidated with VLAN trunking (figure) 4-23

separate Ethernet interfaces (figure) 4-23

verifying 4-26

VLAN trunking and ISL encapsulation 4-24

(figure) 4-56

IS-IS multiareas

DCN architecture design worksheet 4-8

IEEE 802.1Q 4-31

ISL trunking 4-21

manual area addressing 4-34

IS-IS network

adjacency problems, troubleshooting (figure) 4-76


Index

connectivity

troubleshooting 4-68, 4-80

verifying 4-79, 4-99

core router

configuring 4-94

verifying 4-95

displaying 4-70

operational (figure) 4-73

routing table, verifying 4-98

sample topology (figure) 4-70

TARP PDUs, troubleshooting with 4-84

ISL (Inter-Switch Link) encapsulation

defined GL-4

IS-IS multiarea network on VLAN using 4-24

VLAN configuration

(examples) 4-29

verification 4-30

ISL trunking


ISO-IGRP (Interior Gateway Routing Protocol), defined GL-4

L

LAPB (Link Access Procedure, Balanced)

debugging A-29

defined GL-4

overview 2-7

switch monitoring network link control 2-39

timer parameters 2-8

Lucent CONNECTVU-ATP, RBP connection 2-80

Lucent cpblx form

I-Frame 2-6

parameter descriptions 2-109

SCC0 and SCC1 2-66

Lucent Datakit network

(figure) 2-40

TCP/IP, replacing 2-80


M

manual area addressing

configuring 4-35


network adjacency verification 4-37

M-bit

X.25, described 2-21

modem (modulator-demodulator), defined GL-4

modem always on, feature A-27

MPLS (Multiprotocol Label Switching) in DCN

benefits 5-12

core architecture 5-16

defined GL-4

deploying 5-16

(examples) 5-18

(figure) 5-1

IPsec-aware VPN 5-18

management VPN 5-11

overview 5-2

route reflectors in 5-17

secure management data 5-9

shared core network 5-5

technology overview 5-14

user traffic 5-10

vendor-separated traffic

design details 5-14

(figure) 5-9

Multi-PAD Support feature, asynchronous network elements A-1

N

network elements

asynchronous PAD connections for A-1

configured as Level 1 IS-IS routers 4-25, 4-76

dial-out prevention for A-26

Ethernet interface, migrating to 3-4

gateway

Index

between LAN and SONET DCC 4-38

described 4-20

ES adjacencies 4-20

(figure) 4-39

in IS-IS Level 1 areas 4-32

in telco DCN network 1-2, 3-2

(figure) 4-2, 4-50

Level 1-2 adjacency (figure) 4-73

modem always on for A-27

MPLS VPNS and differentiated traffic in converged network 5-14

OSI connectivity to, troubleshooting 4-81

partitions and fiber cut between 4-40

(figure) 4-40

ping command support 4-81

separated by an Ethernet switch (figure) 4-21

single DCN to monitor transmission 5-6

SONET/SDH connectivity to OSS 4-1

SONET-based over DCC in-band channel 4-21

split horizon for control of 4-66

throughput negotiation A-24

TL1 and OSS 3-8

X.25 Multi-PAD Support feature for A-1

NMA (Network Management Application), defined 3-14, GL-5

NSAP (network service access point)

(figure) 4-13

static map to host names 4-69

O

OAM&P (Operations, Administration, Maintenance, and Provisioning), functions in DCN network 1-2

OSI (Open System Interconnection)

addressing

implementation 4-16

issues 4-13

classic network architecture design worksheet 4-6

connectivity, troubleshooting 4-81

network, multiple OSI domains in 4-92

SONET/SDH multiple area scaling issues 4-4, 4-18

OSS (Operations Support Systems)

TCP/IP, migrating to 3-2

P

PLP (Packet Level Protocol), X.25 network layer protocol 2-7

protocol translation

ADC Soneplex 3-20

Alcatel 1603 SM 3-33

Alcatel 1633 SX DCS 3-39

Alcatel DCS-DEXCS 3-45

Alcatel Litespan 3-27

Applied Digital T3AS DCS 3-57

DCN solution (figure) 3-3

Fujitsu SONET GNE 3-13

IP hosts and Fujitsu X.25 interfaces (figure) 3-14

ruleset feature 3-12

TCP-to-X.25 3-13

Tellabs Titan 5500 DCS 3-50

Wiltron Test System 3-63

X.25-to-TCP/IP mediation 3-9

provisioning networks, Cisco X.25 RBP solution 2-79, 2-80

Q

Q-bit

RBP, described 2-21, GL-6

R

RBP (Record Boundary Preservation)

CDR host support 2-21

in provisioning network, configuring 2-80

IP backbone 2-3

overview 2-20


Index

Q-bit 2-21

traffic data collection 2-100

configuring 2-101

RBP Q-Bit feature

MNP file type 2-26

MTP file type 2-24

overview 2-20

recent change port, router configuration 2-85

Relay X.25 VC Number feature, over XOT A-4

rotary group, defined GL-6

router-based DCN, building 3-1

route reflectors, defined GL-6

routes, summarizing X.25 (figure) 3-7

RTS (Ready To Send), defined GL-6

S

SARTS (Switched Access Remote Test System)

test access and control links to DCCS (figure) 3-58

SNMP (Simple Network Management Protocol), defined GL-6

Soneplex Firmware Version 3, network layer parameters 3-22

Soneplex Firmware Version 5, network layer parameters 3-23

SONET (Synchronous Optical Network)

defined GL-7

in DCN network 4-1

SONET rings, managing increases in number of 4-4

standards, tables of B-1

Sterling 5000 Collector

polling Class 5 telephone switch (figure) 2-9

polling Lucent 5ESS telephone switch (example) 2-13

polling Nortel DMS/DPP telephone switch (example) 2-16

polling Siemens EWSD telephone switch (example) 2-14

STUN (serial tunnel)

defined GL-7


IP backbone 2-3

Lucent DRM-side configuration 2-68

on switch monitoring network 2-40

on telephone switch side of network

configuration 2-44

(example) 2-47

on workstation side of network 2-42

subaddress, defined GL-7

SVC (switched virtual circuit), defined GL-7

switch monitoring networks

Cisco X.25 BAI as connectivity solution 2-50, 2-51, 3-20

functions of 2-38

IP and Cisco X.25 BAI and EOR solutions 2-69

(figure) 2-70

PVCs used in 2-39

redundant serial links (figure) 2-40

T

TARP (Target Identifier Address Resolution Protocol)

defined GL-7

enabling 4-59

NSAP to device name, mapping 4-54

packet flow (figure) 4-54

propagation control 4-64, 4-66, 4-68

remote login applications 4-61

TARP reports, interpreting (figure) 4-61

TARP Type 1 PDUs, transmission of (figure) 4-62

TARP Type 5 PDUs, transmission of (figure) 4-85

TCP/IP


backbone 2-51

DCN fully migrated to (figure) 2-4

Lucent Datakit network, replacing 2-80

RBP 2-80, 2-81

connection, debugging 2-28

OSS migration to 2-20

STUN encapsulation 2-46

Index

switch monitoring portion of DCN, migrating to 2-40

telephone switch network, migrating to 2-4

XOT

BX.25 packet transport 2-12

CDR data transport 2-6

telephone switches

BX.25 security password for 2-6

Cisco edge router connected to Nortel DMS⁄ DPP (example) 2-16

Ericsson AXE-10 2-24

Ericsson AXE-10 International 2-24

Lucent 5ESS

BX.25 I-Frame, disabling 2-6

BX.25 router connection (example) 2-14

cpblx3 form 2-6, 2-66, 2-109

echo back port, configuring 2-82

EDAS port configuration form 2-108

network connections (figure) 2-3

RBP and Inter-mediatE 2-21

recent change port, configuring 2-84

MSG GSM 2-24

Siemens EWSD, Cisco edge router connected to (example) 2-15

XOT on router connected to 2-11

Tellabs Titan 5500 DCS





three-tiered network architecture

OSI access layer configuration 4-18

OSI core layer configuration 4-92

OSI distribution layer configuration 4-87

overview 4-12

TLV 137, correlate router and host names using 4-69

transport mechanisms

BX.25 2-2, 2-100

Datakit node 2-40, 2-51

OSI 4-3

TCP/IP 2-20

X.25 2-20

XOT 2-6, 2-9

V

VC (virtual circuit), defined GL-8

VLAN (Virtual LAN), defined GL-8

VRF-VPN (VPN routing/forwarding instance), defined GL-8

W

Wiltron



X

X.121, defined GL-8

X.25

addresses configured on TTY line A-2

BX.25, compared 2-2, 2-6

debugging A-28

defined GL-8

migrating DCN transmission equipment in 3-2

prerequisites 3-12

troubleshooting 3-67

packet-setting parameters 2-7

PLP network layer protocol 2-7

relay VC number over XOT A-4

routes, summarizing 3-7

throughput negotiation A-24

timer definitions 2-8

transmission equipment in DCN (figure) 3-2

version selection feature 3-12

X.25 BAI (Backup Active Interface)

BX.25 ports SCC0 and SCC1 on Lucent 5ESS switch 2-77


Index

on NMA side of network 2-52

on switch monitoring network 2-50

on telephone switch side of network

configuration 2-58

(example) 2-62

X.25 Multi-PAD Support feature A-1

X.25 Throughput Negotiation feature A-24

X.28, defined GL-8

XOT (X.25 over TCP/IP)


(figure) 2-9

DCN solution (figure) 3-3

guidelines for adding to DCN 3-4

host support 2-17

IP backbone 2-3

on billing collector side of network 2-9

on CDR 2-9

overview 2-6


Date post:	23-May-2020
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times

Cisco Network Solutions for the Telco DCN · iii Cisco Network Solutions for the Telco DCN CONTENTS...

Documents