Cisco MGX Route Processor Module (RPM-XF) Installation and ... · Cisco MGX Route Processor Module...

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

800 553-NETS (6387)Fax: 408 526-4100

Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration GuideRelease 4October 2003

Customer Order Number: Text Part Number: OL-5087-01

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.

CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.

All other trademarks mentioned in this document or Web site 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. (0304R)

Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration GuideCopyright © 2002, 2003, Cisco Systems, Inc.All rights reserved.

iCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide

Release 4, Part Number OL-5087-01 Rev. B0, April 25, 2005

C O N T E N T S

Objectives xv

Audience xv

Revision History xviRelease 4 xvi

Organization xvii

Conventions xviiiWarning Definition xixClass 1 Laser Product Warning xixLaser Beam Warning xx

Related Documentation xxiCisco WAN Manager Release 12 xxiCisco MGX 8850 (PXM45) Multiservice Switch Release 4 xxiiCisco MGX 8850 (PXM1E) Multiservice Switch Release 4 xxiiiCisco MGX 8950 Multiservice Service Release 4 xxivSES PNNI Release 4 xxvCisco MGX 8830 Multiservice Switch Release 4 xxviCisco WAN Switching Software Release 9.4 xxviiMGX 8850 (PXM1) Edge Concentrator Release 1.2.20 xxviiiMGX 8250 Edge Concentrator Release 1.2.20 xxviiiMGX 8230 Edge Concentrator Release 1.2.20 xxix

Obtaining Documentation xxxiCisco.com xxxiDocumentation CD-ROM xxxiOrdering Documentation xxxiDocumentation Feedback xxxi

Obtaining Technical Assistance xxxiiCisco TAC Website xxxiiOpening a TAC Case xxxiiTAC Case Priority Definitions xxxiii

Obtaining Additional Publications and Information xxxiii

C H A P T E R 1 Overview of the MGX RPM-XF 1-1

Performance 1-1

Physical Overview 1-2

Contents

iiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


System Specifications 1-6

MGX 8850 Cellbus 1-6

MGX 8850 Serial Bus Interface 1-7

RPM-XF Midplane Connector 1-7

Front Panel LEDs 1-7

Cisco IOS Software Compatibility 1-8

C H A P T E R 2 Preparing to Install the MGX RPM-XF 2-1

Safety Recommendations 2-1

Maintaining Safety with Electricity 2-2Preventing Electrostatic Discharge Damage 2-3

General Site Requirements 2-3Power Supply Considerations 2-3

Installation Checklist 2-4

Creating a Site Log 2-4

Preparing to Connect to a Network 2-5Ethernet Connection 2-5Console and Auxiliary Ports 2-5Console Port Connection 2-6Auxiliary Port Connections 2-6

C H A P T E R 3 Installing the MGX RPM-XF Front and Back Cards 3-1

Inspecting the System 3-1

Required Tools and Parts 3-2

Installing and Removing the RPM-XF Cards 3-2Before Installing Front or Back Cards 3-3Installing the RPM-XF Front Card 3-4Removing the RPM-XF Card 3-4

Installing and Removing Back Cards in the MGX 8850 Midplane 3-6Installing the Back Cards 3-7Removing the Back Cards 3-7

Connecting a Console Terminal or PC to the MGX-XF-UI Console Port 3-9

C H A P T E R 4 Installing and Configuring the MGX-XF-UI Management Back Card 4-1

Overview and Features 4-1

Fast Ethernet Overview 4-3IEEE 802.3u 100BaseT Fast Ethernet Specifications 4-3

Contents

iiiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


Installation Guidelines 4-4New Installation Guidelines 4-4Replacement Installation Guidelines 4-4

Software Configuration 4-5Configuring the Console and Auxiliary Ports 4-5

Console and Auxiliary Port Default Values 4-5Console and Auxiliary Port Syntax 4-5Configuring the Console Port 4-6Configuring the Auxiliary Port 4-7Console and Auxiliary Port Configuration Commands 4-7Console and Auxiliary Port Example Configuration 4-9

Configuring the Fast Ethernet Ports 4-9Fast Ethernet Default Values 4-9Fast Ethernet Port Syntax 4-10Configure the Fast Ethernet Port 4-10Fast Ethernet Port Configuration Commands 4-11Fast Ethernet Port Example Configuration 4-12Verifying Ethernet Connectivity 4-12Using show Commands to Check System Status 4-12

Troubleshooting the Installation 4-15

C H A P T E R 5 Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards 5-1

MGX-1OC12POS-IR Overview and Features 5-1

MGX-2OC12POS Overview and Features 5-4

Installation Guidelines 5-6New Installation Guidelines 5-6Replacement Installation Guidelines 5-6

Software Configuration 5-6MGX-1OC12POS-IR and MGX-2OC12POS Back Card Default Values 5-7MGX-1OC12POS-IR Back Card Syntax 5-7MGX-2 OC12POS Back Card Syntax 5-8Configuring the Interface 5-8Customizing the MGX-1OC12POS-IR or MGX-2OC12POS 5-9

Setting the Clock Source 5-9Configuring Framing 5-9Specifying SONET Overhead 5-10Configuring POS SPE Scrambling 5-10Configuring Loopback Testing 5-11

Example Configuration 5-11

Contents

ivCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


Using show Commands to Check System Status 5-12

Troubleshooting the Installation 5-13

C H A P T E R 6 Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards 6-1

MGX-1GE Features and Specifications 6-2MXG-1GE SFP Specifications 6-3MGX-1GE Installation Guidelines 6-3

MGX-1GE First Time Installation 6-4MGX-1GE Replacement Installation 6-4

MGX-1GE Software Configuration Guidelines 6-4MGX-1GE Back Card Default Values 6-4MGX-1GE Back Card Syntax 6-5MGX-1GE Interface Configuration 6-5MGX-1GE Customization 6-6MGX-1GE Example Configuration 6-7

MGX-1GE System Status Check 6-8

MGX-2GE Features and Specifications 6-15MXG-2GE SFP Specifications 6-16MGX-2GE Installation Guidelines 6-17

MGX-2GE First Time Installation 6-17MGX-2GE Replacement Installation 6-17

MGX-2GE Software Configuration Guidelines 6-18MGX-2GE Back Card Default Values 6-18MGX-2GE Back Card Syntax 6-18MGX-2GE Interface Configuration 6-19MGX-2GE Customization 6-20MGX-2GE Example Configuration 6-21

MGX-2GE System Status Check 6-21

MGX-1GE and MGX-2GE Installation Troubleshooting 6-28

C H A P T E R 7 Configuring the MGX RPM-XF 7-1

Accessing the RPM-XF Command Line Interface 7-1

Booting the RPM-XF 7-2RPM-XF Bootflash Precautions 7-2Verifying the Cisco IOS Files on Bootflash 7-2Verifying the Cisco IOS Files in the PXM45 C:FW Directory 7-2Verifying the Cisco IOS Configuration Files in the PXM45 E:RPM Directory 7-3Initializing the RPM-XF Card 7-3Assigning an IP Address to the Switch Interface 7-5

Contents

vCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


Booting RPM-XF Using TFTP from a TFTP Server 7-7RPM-XF Boot-up Sequence 7-8

Verifying the Configuration 7-9Using the show Commands to Verify the Interface Status 7-9Viewing the Hardware Configuration 7-10Viewing the Boot Variable 7-11Using show Commands to Display Back Card Information 7-11

Establishing 1:N Redundancy Between Two or More RPM-XF Cards 7-12Using switchredcd Command to Switch from Active to Standby Card 7-14Deleting Redundancy 7-15Adding Additional Primary Cards 7-16Upgrading Redundant RPM-XF Cards 7-16Upgrading Non-redundant RPM-XF Cards 7-17

Enabling IP Accounting Counters 7-18

C H A P T E R 8 Configuring PNNI Communications 8-1

Configuration Quickstarts 8-1Switch and RPM-XF Preparation Quickstart 8-1RPM-XF to RPM-XF Connection Quickstart 8-2RPM-XF Slave to the AXSM Master Connection Quickstart 8-3AXSM Slave to RPM-XF Master Connection Quickstart 8-6

Configuring PNNI Connections 8-7Verifying the PNNI Controller Configuration 8-7Assigning Link Resources to a PNNI Controller 8-8

VPIs and VCIs 8-10Bandwidth 8-10Number of Connections 8-11Resource Partition Provisioning 8-11

Configuring Switch Interface Signaling 8-12Creating and Configuring a Switch Subinterface 8-14Creating a Slave Connection on the RPM-XF 8-16Creating a Master Connection on the RPM-XF 8-19

Connection Management 8-23Deleting a Connection 8-23Modifying Traffic Parameters 8-23Downing and Upping the Connection 8-24Rerouting the Connection 8-24Connection Synchronization 8-24

Manually Resynchronizing Connections 8-25

Contents

viCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


Automatically Resynchronizing Connections 8-25

Connection State Alarms 8-25

C H A P T E R 9 Configuring MPLS Features 9-1

MPLS Overview 9-1ATM MPLS 9-2

MPLS in the MGX 8850 Switch 9-2Features 9-2System Block Diagram 9-3

MPLS Class of Service Support 9-4

Configuring MPLS for MGX 8850 9-4Adding an MPLS Controller to the PXM45 and Configuring an RPM-XF LSC 9-5Adding and Partitioning an AXSM NNI Port for MPLS 9-6Configuring an RPM-XF as an Edge Label Switch Router 9-8Mapping an AXSM Port and ELSR Port to XTagATM Interfaces on the LSC 9-9

VPN Overview 9-9Requirements 9-10MPLS VPN Features 9-10Supported Platforms 9-11

How VPNs Work 9-11VPNs for MPLS 9-11VPN Route-Target Communities and Export and Import Lists 9-11iBGP Distribution of VPN Routing Information 9-12Label Forwarding 9-12Examples of VPN Topologies 9-12

Configuring a VPN 9-13Prerequisites for VPN Operation 9-14Configuring VPN Operation 9-14

Configuring VRFs 9-14Configuring BGP 9-15Balancing eiBGP Load Sharing 9-16Configure Import and Export Routes 9-17Checking the VRFs 9-17

Multicast VPN 9-19Multicast VPN Operation 9-19

Multicast VPN Example Configuration 9-20IP Multicast 9-20Multicast Protocols 9-21

Multicast Protocols Supported in SP Core 9-21

Contents

viiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


Multicast Modes 9-21Source Specific Multicast 9-22

SSM Configuration Example 9-22mVPN Forwarding Operation 9-22VRF Configuration Example 9-23

MPLS LDP 9-24

Support for Multi-VC on the RPM-XF 9-25Configuring Multi-VC on the RPM-XF eLSR 9-25

C H A P T E R 10 Configuring Quality of Service 10-1

General QoS Configuration Procedure 10-2Creating a QoS Boilerplate 10-3

Creating a Class Map 10-3Creating a Policy Map 10-3

Assigning a QoS Boilerplate to an Interface 10-4

Class Map Commands 10-4Creating a Class Map 10-4Matching Attributes 10-5

Policy Map Commands 10-6Creating a Policy Map 10-6Assigning a Class to a Policy Map 10-6Specifying a Committed Access Rate 10-7Enabling Weighted Random Early Detection 10-8Bandwidth Reservation and Low-Latency Priority Queueing 10-9

Bandwidth Reservation Queueing 10-9Low-Latency Priority Queueing 10-10

Generic Traffic Shaping 10-11Specifying a Queue Limit 10-11Applying Set Values 10-12

Service-Policy Command 10-13

Show Commands 10-14show policy map 10-14show policy-map interface 10-14show class-map 10-14show vlans 10-15

Quality of Service Policy Propagation Example Using Border Gateway Protocol 10-15

Versatile Traffic Management System (VTMS) 10-19VTMS Buffer Management 10-19

VTMS Queuing 10-20

Contents

viiiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


Queuing CLI Commands 10-20

MultiLink PPP/Link Fragmentation Interleaving (MLP/LFI) 10-21MLP/LFI Configuration 10-21

Internet Protocol Header Compression (IPHC) 10-22cRTP Configuration 10-23

Examples 10-24

A P P E N D I X A Maintaining the MGX RPM-XF A-1

Reading Front Panel LEDs A-1

Recovering a Lost Password A-3Password Recovery Procedure A-4

Virtual Configuration Register Settings A-6Changing Configuration Register Settings A-7Virtual Configuration Register Bit Meanings A-8Enabling Booting from the PXM Hard Disk A-10Enabling Booting from Bootflash A-10

Copying a Cisco IOS Image to Bootflash A-10

Recovering Boot and System Images A-12Using the xmodem Command A-12Using the tftpdnld Command A-13

A P P E N D I X B Cable and Connector Specifications B-1

100BaseT Fast Ethernet Specifications B-1

Console and Auxiliary Port Signals and Pinouts B-2Identifying a Rollover Cable B-2Console Port Signals and Pinouts B-2Auxiliary Port Signals and Pinouts B-4

Fast Ethernet RJ-45 Connector Pinouts B-6

SFP Specifications B-7

A P P E N D I X C Cisco IOS and Configuration Basics C-1

Cisco IOS Software Basics C-1Cisco IOS Modes of Operation C-1Getting Context-Sensitive Help C-3Saving Configuration Changes C-3

Manually Configuring RPM-XF C-4Verifying Network Connectivity C-5

Contents

ixCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


A P P E N D I X D Command Summary D1

User Exec Mode Commands D1

Privileged Exec Mode Commands D3

Global Configuration Mode Commands D5

Interface Configuration Mode Commands D9

QoS Configuration Mode Commands D12

Contents

xCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


T A B L E S

xiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


Table 1-1 RPM-XF Card Specification 1-6

Table 4-1 Specifications and Connection Limits for Fast Ethernet 100-Mbps Transmission 4-3

Table 4-2 EEE 802.3u Physical Characteristics 4-4

Table 4-3 Console/Auxiliary Port Defaults 4-5

Table 4-4 Console/Auxiliary Port Syntax 4-6

Table 4-5 Fast Ethernet Port Defaults 4-10

Table 4-6 Fast Ethernet Port Syntax 4-10

Table 4-7 MGX-XF-UI Back Card LED Status and Definitions 4-15

Table 4-8 Management Back Card Installation Troubleshooting 4-15

Table 5-1 MGX MGX-1OC12POS-IR Front Panel LED and Port Descriptions 5-2

Table 5-2 MGX-1OC12POS-IR Cable Specifications 5-3

Table 5-3 MGX MGX-2OC12POS Front Panel LED and Port Descriptions 5-4

Table 5-4 MGX-2OC12POS Cable Specifications 5-5

Table 5-5 MGX-1OC12POS-IR and MGX-2OC12POS Back Card Defaults 5-7

Table 5-6 MGX-1OC12POS-IR Interface Syntax 5-8

Table 5-7 MGX-2OC12POS Interface Syntax 5-8

Table 5-8 MGX-1OC12POS-IR or MGX-2OC12POS Back Card LED Status and Definitions 5-13

Table 5-9 MGX-1OC12POS-IR or MGX-2OC12POS Installation Troubleshooting 5-13

Table 6-1 MGX 1GE Front Panel LED and Port Descriptions 6-2

Table 6-3 MGX-1GE Back Card Defaults 6-5

Table 6-4 MGX-1GE Interface Syntax 6-5

Table 6-5 MGX 2GE Front Panel LED and Port Descriptions 6-15

Table 6-7 MGX-2GE Back Card Defaults 6-18

Table 6-8 MGX-2GE Interface Syntax 6-18

Table 6-9 MGX-1GE and MGX-2GE Back Card LED Status and Definitions 6-28

Table 6-10 MGX-1GE and MGX-2GE Installation Troubleshooting 6-28

Table 8-1 Switch Partition Parameter Description 8-9

Table 8-2 Partitioning VPI/VCI Resources on the RPM-XF 8-10

Table 9-1 Multicast VPN Terms 9-19

Table 10-1 CAR Actions 10-7

Table 10-2 Precedence Values 10-9

Tables

xiiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


Table 10-3 cRTP Configuration Commands 10-23

Table 10-4 cRTP Statistics 10-24

Table A-1 Front Panel LEDs A-2

Table A-2 Virtual Configuration Register Bit Meaning A-6

Table A-3 Explanation of Boot Field (Configuration Register Bits 00 to 03) A-7

Table A-4 Default Boot Filenames A-8

Table A-5 Configuration Register Settings for Broadcast Address Destination A-9

Table A-6 System Console Terminal Baud Rate Settings A-9

Table B-1 Specifications and Connection Limits for Fast Ethernet 100-Mbps Transmission B-1

Table B-3 Console Port Signaling and Cabling Using a DB-25 Adapter B-4

Table B-5 Auxiliary Port Signaling and Cabling Using a DB-25 Adapter B-5

Table B-6 FE RJ-45 Connector Pinout B-6

Table D-1 Commands in User EXEC Mode—Router> D1

Table D-2 Commands in Privileged EXEC Mode—Router# D3

Table D-3 Commands in Global Configuration Mode—Router(config)# D5

Table D-4 Commands in Interface Configuration Mode—Router(config-if)# D9

Table D-5 QoS Class-Map Configuration Commands—Router(config-cmap)# D12

Table D-6 QoS Policy-Map Configuration Commands—Router(config-pmap)# D12

Table D-7 QoS Policy-Map Class Configuration Commands—Router(config-pmap-c)# D12

F I G U R E S

xiiiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


Figure 1-1 RPM-XF Installed in an MGX 8850 Chassis (Front View) 1-3

Figure 1-2 RPM-XF Back Cards Installed in MGX 8850 (Back View) 1-4

Figure 1-3 RPM-XF Connected to the MGX 8850 Midplane and to the Back Cards 1-5

Figure 1-4 RPM-XF Front Panel 1-8

Figure 3-1 Backplane Inspection Check Points 3-3

Figure 3-2 Damaged Connectors on the Card 3-3

Figure 3-3 Front Card Extractor Latch 3-4

Figure 3-4 RPM-XF Installed in the MGX 8850 Chassis (Front View) 3-6

Figure 3-5 RPM-XF Back Cards Connected to an MGX 8850 (Back View) 3-8

Figure 3-6 Connecting a Console Terminal to the MGX-XF-UI Console Port 3-10

Figure 4-1 MGX-XF-UI Management Back Card 4-2

Figure 5-1 MGX-1OC12POS-IR Back Card 5-2

Figure 5-2 MGX-2OC12POS Back Card 5-4

Figure 6-1 MGX-1GE Back Card 6-2

Figure 6-2 MGX-2GE Back Card 6-15

Figure 8-1 RPM-XF-to-RPM-XF Connections 8-2

Figure 8-2 RPM-XF Slave to AXSM Master Connections 8-4

Figure 8-3 RPM-XF Master to AXSM Slave Connections 8-6

Figure 9-1 MGX 8850s with ELSR and LSC Configured RPM-XF 9-4

Figure 9-2 VPN with a Service Provider (P) Backbone Network 9-13

Figure 9-3 VPNs Communicate with Customer Sites 9-13

Figure 9-4 Multi-VC Configuration 9-25

Figure 10-1 QoS Process 10-2

Figure 10-2 RPM-XF Routes and QoS Policy Application 10-15

Figure A-1 MGX RPM-XF Front Panel LEDs A-2

Figure B-1 Identifying a Rollover Cable B-2

Figure B-2 Connecting the Console Port to a PC B-3

Figure B-3 Connecting the Console Port to a Terminal B-3

Figure B-4 Connecting the Auxiliary Port to a PC B-4

Figure B-5 Connecting the Auxiliary Port to a Terminal B-5

Figure B-6 Straight-Through Cable Pinout for FE-TX RJ-45 Connection to a Hub or Repeater B-6

Figures

xivCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


Figure B-7 Crossover Cable Pinout for FE-TX RJ-45 Connections Between Hubs and Repeaters B-6

xvCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


About This Guide

This section discusses the objectives, audience, organization, and conventions of the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 3.

ObjectivesThis publication provides instructions for the initial site preparation and installation of the Cisco MGX Route Processor Module (RPM-XF). Troubleshooting, maintenance procedures, and cable specifications are also provided.

Only basic software configuration information is included in this publication. For detailed software configuration information, refer to the MGX 8850 and Cisco IOS configuration and command reference publications. These publications are available on the Documentation CD-ROM that comes with your RPM-XF, or you can order printed copies.

AudienceThis document was written for engineers, users, network administrators, and technicians that are familiar with Cisco MGX Series switches and Cisco routers. Readers should be familiar with electronic circuitry and wiring practices.

xviCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


About This GuideRevision History

Revision HistoryThe updates, additions, and changes to this document are listed in this section by release and chapter.

Note The Revision History was begun with Release 4.

Release 4• Chapter 5, “Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back

Cards”

– Added new section: MGX-2OC12POS Overview and Features, page 5-4

– Revised Installation Guidelines, page 5-6.

– Revised section: Software Configuration, page 5-6

• Chapter 6, “Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards”

– Revised chapter to describe both the MGX-1GE and the MGX-2GE cards.

– Revised section: MGX-1GE Features and Specifications, page 6-2

– Added new section: MGX-2GE Features and Specifications, page 6-15

– Added revised section: MGX-1GE and MGX-2GE Installation Troubleshooting, page 6-28

• Chapter 7, “Configuring the MGX RPM-XF”

– Added new section: Enabling IP Accounting Counters, page 7-18

• Chapter 9, “Configuring MPLS Features”

– Add new section: Balancing eiBGP Load Sharing, page 9-16

– Added new section: Multicast VPN, page 9-19

• Chapter 10, “Configuring Quality of Service”

– Added new section Versatile Traffic Management System (VTMS), page 10-19

– Added new section MultiLink PPP/Link Fragmentation Interleaving (MLP/LFI), page 10-21

– Added new section Internet Protocol Header Compression (IPHC), page 10-22

xviiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


About This GuideOrganization

OrganizationThe major sections of this publication are as follows:

Chapter Title Description

Chapter 1 Overview of the MGX RPM-XF Discusses the features and specifications of the Route Processor Module (RPM-XF).

Chapter 2 Preparing to Install the MGX RPM-XF Discusses environmental requirements, safety recommendations, and describes the various ports and how to prepare for connections between networks and ports.

Chapter 3 Installing the MGX RPM-XF Front and Back Cards

Includes basic installation information and describes how to make connections to LANs, the main PXM1, and console terminal.

Chapter 4 Installing and Configuring the MGX-XF-UI Management Back Card

Describes how to install and configure the MGX-XF-UI management back card.

Chapter 5 Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards

Describes how to install and configure the single-port OC-12 POS2 back card.

Chapter 6 Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards

Describes how to install and configure the single-port GE3 back card.

Chapter 7 Configuring the MGX RPM-XF Describes the initial configuration of the RPM-XF using Configuration Mode or AutoInstall. This chapter also explains how to configure and use 1:N redundancy on the RPM-XF.

Chapter 8 Configuring PNNI Communications Describes how to configure the RPM-XF to operate as an edge router in a PNNI network.This chapter also explains how to configure all port adapter interfaces, followed by procedures for configuring PVCs4 and connections with other RPM-XFs.

Chapter 9 Configuring MPLS Features Describes MPLS5 and VPN6 features used with the RPM-XF in the MGX 8850 switch.

Chapter 10 Configuring Quality of Service Describes how to configure QoS7 on the RPM-XF.

Appendix A Maintaining the MGX RPM-XF Provides selected maintenance procedures, including password recovery, virtual configuration register settings, and system code upgrades.

Appendix B Cable and Connector Specifications Provides pinouts for the various ports on the RPM-XF and associated cables.

Appendix C Cisco IOS and Configuration Basics Provides information on the Cisco IOS operating system and configuring the RPM-XF card.

Appendix D Command Summary Provides provides a high level view of many of the commands that run on the RPM-XF.

1. PXM=prpocessor switch control module

2. POS=Packet Over SONET

3. GE=Gigabit Ethernet

4. PVC=Permanent Virtual Circuit

5. MPLS=Multiprotocol Label Switching

6. VPN=Virtual Private Network

7. QoS=Quality of Service

xviiiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


About This GuideConventions

ConventionsThis publication uses the following conventions to convey instructions and information.

Command descriptions use these conventions:

• Commands and keywords are in boldface.

• Arguments for which you supply values are in italics.

• Elements in square brackets ([ ]) are optional.

• Alternative but required keywords are grouped in braces ({ }) and are separated by vertical bars ( | ).

Examples use these conventions:

• Terminal sessions and information the system displays are in screen font.

• Information you enter is in boldface screen font.

• Nonprinting characters, such as passwords, are in angle brackets (< >).

• Default responses to system prompts are in square brackets ([ ]).

Notes, tips cautions, and warnings use the following conventions and symbols:

Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in this manual.

Tip Means the following information will help you solve a problem. The tip information might not be troubleshooting or even an action, but could be useful information.

Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Warning Means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. To see translated versions of the warning, refer to the Regulator Compliance and Safety document that accompanied the device.

xixCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide



Warning Definition

Class 1 Laser Product Warning

Warning Means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents.

Waarschuwing Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk letsel kan veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich bewust te zijn van de bij elektrische schakelingen betrokken risico's en dient u op de hoogte te zijn van standaard maatregelen om ongelukken te voorkomen.

Varoitus Tämä varoitusmerkki merkitsee vaaraa. Olet tilanteessa, joka voi johtaa ruumiinvammaan. Ennen kuin työskentelet minkään laitteiston parissa, ota selvää sähkökytkentöihin liittyvistä vaaroista ja tavanomaisista onnettomuuksien ehkäisykeinoista.

Attention Ce symbole d'avertissement indique un danger. Vous vous trouvez dans une situation pouvant causer des blessures ou des dommages corporels. Avant de travailler sur un équipement, soyez conscient des dangers posés par les circuits électriques et familiarisez-vous avec les procédures couramment utilisées pour éviter les accidents.

Warnung Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu einer Körperverletzung führen könnte. Bevor Sie mit der Arbeit an irgendeinem Gerät beginnen, seien Sie sich der mit elektrischen Stromkreisen verbundenen Gefahren und der Standardpraktiken zur Vermeidung von Unfällen bewußt.

Avvertenza Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di lavorare su qualsiasi apparecchiatura, occorre conoscere i pericoli relativi ai circuiti elettrici ed essere al corrente delle pratiche standard per la prevenzione di incidenti.

Advarsel Dette varselsymbolet betyr fare. Du befinner deg i en situasjon som kan føre til personskade. Før du utfører arbeid på utstyr, må du vare oppmerksom på de faremomentene som elektriske kretser innebærer, samt gjøre deg kjent med vanlig praksis når det gjelder å unngå ulykker.

Aviso Este símbolo de aviso indica perigo. Encontra-se numa situação que lhe poderá causar danos físicos. Antes de começar a trabalhar com qualquer equipamento, familiarize-se com os perigos relacionados com circuitos eléctricos, e com quaisquer práticas comuns que possam prevenir possíveis acidentes.

¡Atención! Este símbolo de aviso significa peligro. Existe riesgo para su integridad física. Antes de manipular cualquier equipo, considerar los riesgos que entraña la corriente eléctrica y familiarizarse con los procedimientos estándar de prevención de accidentes.

Varning! Denna varningssymbol signalerar fara. Du befinner dig i en situation som kan leda till personskada. Innan du utför arbete på någon utrustning måste du vara medveten om farorna med elkretsar och känna till vanligt förfarande för att förebygga skador.

xxCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide



Laser Beam Warning

Warning Class 1 laser product.

Waarschuwing Klasse-1 laser produkt.

Varoitus Luokan 1 lasertuote.

Attention Produit laser de classe 1.

Warnung Laserprodukt der Klasse 1.

Avvertenza Prodotto laser di Classe 1.

Advarsel Laserprodukt av klasse 1.

Aviso Produto laser de classe 1.

¡Advertencia! Producto láser Clase I.

Varning! Laserprodukt av klass 1.

Warning Do not stare into the beam or view it directly with optical instruments.

Waarschuwing Niet in de straal staren of hem rechtstreeks bekijken met optische instrumenten.

Varoitus Älä katso säteeseen äläkä tarkastele sitä suoraan optisen laitteen avulla.

Attention Ne pas fixer le faisceau des yeux, ni l'observer directement à l'aide d'instruments optiques.

Warnung Nicht direkt in den Strahl blicken und ihn nicht direkt mit optischen Geräten prüfen.

Avvertenza Non fissare il raggio con gli occhi né usare strumenti ottici per osservarlo direttamente.

Advarsel Stirr eller se ikke direkte pŒ strŒlen med optiske instrumenter.

Aviso Não olhe fixamente para o raio, nem olhe para ele directamente com instrumentos ópticos.

¡Advertencia! No mirar fijamente el haz ni observarlo directamente con instrumentos ópticos.

Varning! Rikta inte blicken in mot strålen och titta inte direkt på den genom optiska instrument.

xxiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


About This GuideRelated Documentation

Related DocumentationThe following Cisco publications contain additional information related to the operation of this product and associated equipment in a Cisco WAN switching network.

Cisco WAN Manager Release 12Table 1 lists the product documentation for the Cisco WAN Manager (CWM) network management system for Release 12.

Table 1 Cisco WAN Manager Release 12 Documentation

Title Description

Cisco WAN Manager Installation Guide for Solaris 8, Release 12

OL-3837-01

Provides procedures for installing Release 12 of the CWM network management system and Release 5.4 of CiscoView on a Solaris 8 platform.

Cisco WAN Manager User’s Guide, Release 12

OL-3838-01

Describes how to use the CWM Release 12 software, which consists of user applications and tools for network management, connection management, network configuration, statistics collection, and security management.

Cisco WAN Manager SNMP Service Agent Guide, Release 12

OL-3840-01

Provides information about the CWM Simple Network Management Protocol Service Agent, an optional adjunct to CWM that is used for managing Cisco WAN switches using SNMP.

Cisco WAN Manager Database Interface Guide, Release 12

OL-3839-01

Provides information about accessing the CWM Informix OnLine database that is used to store information about the network elements.

xxiiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide



Cisco MGX 8850 (PXM45) Multiservice Switch Release 4 Table 2 lists the product documentation for the installation and operation of the Cisco MGX 8850 (PXM45) Multiservice Switch Release 4.

Table 2 Cisco MGX 8850 (PXM45) Release 4 Documentation

Title Description

Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Hardware Installation Guide

OL-3842-01

Describes how to install the Cisco MGX 8950, the Cisco MGX 8850 (PXM1E/PXM45), and the Cisco MGX 8830 switches. This documentation explains what each switch does and covers site preparation, grounding, safety, card installation, and cabling. The Cisco MGX 8850 switch uses either a PXM45 or a PXM1E controller card and provides support for both serial bus based and cell bus based service modules. The Cisco MGX 8950 supports only serial bus based service modules. This hardware installation guide replaces all previous hardware guides for these switches.

Frame Relay Software Configuration Guide and Command Reference for the Cisco MGX 8850 FRSM12 Card, Release 3*

DOC-7810327=

Describes how to use the high-speed Frame Relay (FRSM-12-T3E3) commands that are available in the CLI of the Cisco MGX 8850 (PXM45) switch.

Cisco ATM Services (AXSM) Software Configuration Guide and Command Reference for MGX Switches, Release 4

OL-3852-01

Explains how to configure the AXSM cards and a command reference that describes the AXSM commands in detail. The AXSM cards covered in this manual are the AXSM-XG, AXSM/A, AXSM/B, AXSM-E, and AXSM-32-T1E1-E.

Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Software Configuration Guide, Release 4

OL-3845-01

Describes how to configure the Cisco MGX 8950, the Cisco MGX 8850 (PXM1E/PXM45), and the Cisco MGX 8830 switches with PXM45 or PXM1E controller cards to operate as ATM core switches or edge switches. This guide also provides some operation and maintenance procedures.

Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference, Release 4

OL-3846-01

Describes the PXM commands that are available on the CLI of the Cisco MGX 8830, Cisco MGX 8850, and Cisco MGX 8950 switches.

Cisco Circuit Emulation Software Configuration Guide and Command Reference, Release 4

OL-3853-01

Provides software configuration procedures for provisioning connections and managing the CESM cards supported in this release. Also provides descriptions for all CESM commands.

PNNI Network Planning Guide for MGX and SES Products

OL-3847-01

Provides guidelines for planning a PNNI network that uses Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), Cisco MGX 8950, and Cisco BPX 8600 switches. When connected to a PNNI network, each Cisco BPX 8600 series switch requires an SES for PNNI route processing.

Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4

OL-3186-01

Describes how to install and configure the Cisco MGX Route Processor Module (RPM-XF) in the Cisco MGX 8850 (PXM45) and MGX 8950 Release 4 switch. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and basic Cisco IOS configuration information.

xxiiiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide



Cisco MGX 8850 (PXM1E) Multiservice Switch Release 4Table 3 lists the product documentation for the installation and operation of the Cisco MGX 8850 (PXM1E) Multiservice Switch Release 4.

Cisco VISM Installation and Configuration Guide, Release 3*

OL-2521-01

Describes how to install and configure the Voice Interworking Service Module (VISM) in the Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 switches. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and Cisco CLI configuration information.

Regulatory Compliance and Safety Information for the Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and MGX 8950 Switches*

DOC-7814790=

Provides regulatory compliance, product warnings, and safety recommendations for the Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 switches.

* This book was last updated for Release 3.

Table 2 Cisco MGX 8850 (PXM45) Release 4 Documentation (continued)

Title Description

Table 3 Cisco MGX 8850 (PXM1E) Release 4 Documentation

Title Description


OL-3842-01



OL-3845-01



OL-3846-01



OL-3853-01


Cisco Frame Relay Software Configuration Guide and Command Reference, Release 4

OL-3851-01

Provides software configuration procedures for provisioning connections and managing the FRSM cards supported in this release. Also provides descriptions for all FRSM commands.

xxivCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide



Cisco MGX 8950 Multiservice Service Release 4Table 4 lists the product documentation for the installation and operation of the Cisco MGX 8950 Multiservice Switch Release 4.

Cisco AUSM Software Configuration Guide and Command Reference for Cisco MGX 8850 (PXM1E) and Cisco MGX 8830, Release 3*

DOC-7814254=

Provides software configuration procedures for provisioning connections and managing the AUSM cards supported in this release. Also provides descriptions for all AUSM commands.


OL-3847-01

Provides guidelines for planning a PNNI network that uses Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), Cisco MGX 8950, and Cisco BPX 8600 switches. When connected to a PNNI network, each Cisco BPX 8600 series switch requires an SES for PNNI route processing.


OL-2521-01

Describes how to install and configure VISM in the Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830 Release 4 switches. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and Cisco CLI configuration information.

Regulatory Compliance and Safety Information for the Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and MGX 8950 Switches. *

DOC-7814790=



Table 3 Cisco MGX 8850 (PXM1E) Release 4 Documentation (continued)

Title Description

Table 4 Cisco MGX 8950 Release 4 Documentation

Title Description


OL-3842-01

Describes how to install the Cisco MGX 8950, the Cisco MGX 8850 (PXM1E/PXM45), and the Cisco MGX 8830 switches. This documentation explains what each switch does and covers site preparation, grounding, safety, card installation, and cabling. The Cisco MGX 8850 switch uses either a PXM45 or a PXM1E controller card and provides support for both serial bus based and cell bus based service modules. The Cisco MGX 8950 supports only serial us based service modules. This hardware installation guide replaces all previous hardware guides for these switches.


OL-3845-01


xxvCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide



SES PNNI Release 4 Table 5 lists the product documentation for the understanding, the installation, and the operation of the Service Expansion Shelf (SES) Private Network-to-Network Interface (PNNI) Controller.


OL-3846-01


Cisco ATM Services (AXSM) Software Configuration Guide and Command Reference for MGX Switches, Release 4

OL-3852-01

This guide explains how to configure the AXSM cards and a command reference that describes the AXSM commands in detail. The AXSM cards covered in this manual are the AXSM-XG, AXSM/A, AXSM/B, AXSM-E, and AXSM-32-T1E1-E.


OL-3847-01


Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4

OL-3186-01

Describes how to install and configure the Cisco MGX Route Processor Module (RPM-XF) in the Cisco MGX 8850 Release 4 switch. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and basic Cisco IOS configuration information.

Regulatory Compliance and Safety Information for the Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and MGX 8950 Switches. *

DOC-7814790=



Table 4 Cisco MGX 8950 Release 4 Documentation (continued)

Title Description

Table 5 SES PNNI Controller Release 4 Documentation

Title Description

Cisco SES PNNI Controller Software Configuration Guide, Release 3*

DOC-7814258=

Describes how to configure, operate, and maintain the SES PNNI Controller.

Cisco SES PNNI Controller Command Reference, Release 3*

DOC-7814260=

Provides a description of the commands used to configure and operate the SES PNNI Controller.

xxviCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide



Cisco MGX 8830 Multiservice Switch Release 4Table 6 lists the product documentation for the installation and operation of the Cisco MGX 8830 Multiservice Switch Release 4.


OL-3847-01



Table 5 SES PNNI Controller Release 4 Documentation (continued)

Title Description

Table 6 Cisco MGX 8830 Release 4 Documentation

Title Description


OL-3842-01



OL-3845-01



OL-3846-01



OL-3853-01


Cisco Frame Relay Software Configuration Guide and Command Reference, Release 4

OL-3851-01

Provides software configuration procedures for provisioning connections and managing the FRSM cards supported in this release. Also provides descriptions for all FRSM commands.

Cisco AUSM Software Configuration Guide and Command Reference for MGX 8850 (PXM1E) and MGX 8830, Release 3*

DOC-7814254=

Provides software configuration procedures for provisioning connections and managing the AUSM cards supported in this release. Also provides descriptions for all AUSM commands.

xxviiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide



Cisco WAN Switching Software Release 9.4Table 7 lists the product documentation for the installation and operation of the Cisco WAN Switching Software Release 9.4.


OL-3847-01



OL-2521-01

Describes how to install and configure VISM in the Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830 Release 4 switches. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and Cisco CLI configuration information.

Regulatory Compliance and Safety Information for the Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and MGX 8950 Switches.*

DOC-7814790=



Table 6 Cisco MGX 8830 Release 4 Documentation (continued)

Title Description

Table 7 Cisco WAN Switching Release 9.4 Documentation

Title Description

9.4.00 Version Software Release Notes Cisco WAN Switching System Software

OL-3189-01

Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.

Cisco BPX 8600 Series Installation and Configuration, Release 9.3.30

DOC-7812907=

Provides a general description and technical details of the Cisco BPX broadband switch.

Cisco WAN Switching Command Reference, Release 9.3.30

DOC-7812906=

Provides detailed information on the general command line interface commands.

Cisco IGX 8400 Series Installation Guide

OL-1165-05

Provides hardware installation and basic configuration information for Cisco IGX 8400 Series switches that are running Switch Software Release 9.3.30 or later.

Cisco IGX 8400 Series Provisioning Guide

OL-1166-03

Provides information for configuration and provisioning of selected services for the Cisco IGX 8400 Series switches that are running Switch Software Release 9.3.30 or later.

Cisco IGX 8400 Series Regulatory Compliance and Safety Information

DOC-7813227=

Provides regulatory compliance, product warnings, and safety recommendations for the Cisco IGX 8400 Series switch.

xxviiiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide



MGX 8850 (PXM1) Edge Concentrator Release 1.2.20

Note The Release 1.x books have not been updated recently. Please check the Release Notes for the latest information.

Table 8 lists the product documentation for the installation and operation of the Cisco MGX 8850 Edge Concentrator.

MGX 8250 Edge Concentrator Release 1.2.20Table 9 lists the product documentation for the installation and operation of the Cisco MGX 8250 Edge Concentrator.

Table 8 MGX 8850 Edge Concentrator Release 1.2.20 Documentation

Title Description

Release Notes for Cisco WAN MGX 8850 (PXM1), MGX 8250, and MGX 8230 Software Version 1.2.20

OL-3244-01


Cisco MGX 8850 Edge Concentrator Installation and Configuration, Release 1.1.3

DOC-7811223=

Provides installation instructions for the Cisco MGX 8850 edge concentrator.

Cisco MGX 8800 Series Switch Command Reference, Release 1.1.3

DOC-7811210=

Provides detailed information on the general command line for the Cisco MGX 8850 edge concentrator.

Cisco MGX 8800 Series Switch System Error Messages, Release 1.1.3

DOC-7811240=

Provides error message descriptions and recovery procedures.

Cisco MGX 8850 Multiservice Switch Overview, Release 1.1.3

OL-1154-01

Provides a technical description of the system components and functionality of the Cisco MGX 8850 edge concentrator from a technical perspective.

Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1

DOC-7812278=

Describes how to install and configure the Cisco MGX Route Processor Module (RPM/B and RPM-PR) in the Cisco MGX 8850, the Cisco MGX 8250, and the Cisco MGX 8230 edge concentrators. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and basic Cisco IOS configuration information.

Cisco VISM Installation and Configuration Guide, Release 3

OL-2521-01

Describes how to install and configure VISM in the Cisco MGX 8850, Cisco MGX 8250, and Cisco MGX 8230 switches. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and Cisco CLI configuration information.

xxixCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide



MGX 8230 Edge Concentrator Release 1.2.20Table 10 lists the product documentation for the installation and operation of the Cisco MGX 8230 Edge Concentrator.

Table 9 MGX 8250 Multiservice Gateway Documentation

Title Description


OL-3244-01



DOC-7811217=

Provides installation instructions for the Cisco MGX 8250 Edge Concentrator.

Cisco MGX 8250 Multiservice Gateway Command Reference, Release 1.1.3

DOC-7811212=


Cisco MGX 8250 Multiservice Gateway Error Messages, Release 1.1.3

DOC-7811216=


Cisco MGX 8250 Edge Concentrator Overview, Release 1.1.3

DOC-7811576=

Describes the system components and functionality of the Cisco MGX 8250 Edge Concentrator from a technical perspective.


DOC-7812278=



OL-2521-01


Table 10 MGX 8230 Edge Concentrator Documentation

Title Description


OL-3244-01



DOC-7811215=

Provides installation instructions for the Cisco MGX 8230 Edge Concentrator.

xxxCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide



Cisco MGX 8230 Multiservice Gateway Command Reference, Release 1.1.3

DOC-7811211=


Cisco MGX 8230 Multiservice Gateway Error Messages, Release 1.1.3

DOC-78112113=


Cisco MGX 8230 Edge Concentrator Overview, Release 1.1.3

DOC-7812899=

Provides a technical description of the system components and functionality of the Cisco MGX 8250 Edge Concentrator from a technical perspective.


DOC-7812278=



OL-2521-01


Table 10 MGX 8230 Edge Concentrator Documentation (continued)

Title Description

xxxiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


About This GuideObtaining Documentation

Obtaining DocumentationCisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.comYou can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/en/US/support/tsd_documentation.html

You can access the Cisco website at this URL:


International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROMCisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.

Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

All users can order annual or quarterly subscriptions through the online Subscription Store:

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

Ordering DocumentationYou can find instructions for ordering documentation at this URL:

http://www.cisco.com/en/US/ordering/index.shtml

You can order Cisco documentation in these ways:

• Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:


• Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation FeedbackYou can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.

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


http://www.cisco.com/public/countries_languages.shtml


http://www.cisco.com/en/US/ordering/index.shtml


http://www.cisco.com/en/US/support/tsd_documentation.html

xxxiiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


About This GuideObtaining Technical Assistance

You can send your comments in e-mail to [email protected].

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco SystemsAttn: Customer Document Ordering170 West Tasman DriveSan Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical AssistanceFor all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance.

Cisco TAC WebsiteThe Cisco TAC website (http://www.cisco.com/tac) provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year.

Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

http://tools.cisco.com/RPF/register/register.do

Opening a TAC CaseThe online TAC Case Open Tool (http://www.cisco.com/tac/caseopen) is the fastest way to open P3 and P4 cases. (Your network is minimally impaired or you require product information). After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using these recommendations, your case will be assigned to a Cisco TAC engineer.

For P1 or P2 cases (your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227) EMEA: +32 2 704 55 55 USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

http://www.cisco.com/tac

http://tools.cisco.com/RPF/register/register.do

http://www.cisco.com/tac/caseopen


xxxiiiCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


About This GuideObtaining Additional Publications and Information

TAC Case Priority DefinitionsTo ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—Your network is “down” or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and InformationInformation about Cisco products, technologies, and network solutions is available from various online and printed sources.

• The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

• Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

• Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

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

• iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

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

• Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

• Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/index.html


http://www.cisco.com/en/US/products/products_catalog_links_launch.html

http://www.ciscopress.com

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

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

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

http://www.cisco.com/en/US/learning/index.html

xxxivCisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


About This GuideObtaining Additional Publications and Information

C H A P T E R

1-1Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


1Overview of the MGX RPM-XF

This chapter provides an overview of the MGX Route Processor Module (RPM-XF) and its relationship to the MGX 8850 switch. This chapter contains the following sections:

• Performance

• Physical Overview

• System Specifications

• MGX 8850 Cellbus

• MGX 8850 Serial Bus Interface

• RPM-XF Midplane Connector

• Front Panel LEDs

• Cisco IOS Software Compatibility

PerformanceThe MGX RPM-XF is a next-generation, high performance model of the RPM for the MGX 8850 platform, using PXM45 processor modules. It is a router module based on an RM7000A MIPS processing engine that will fit into almost any full-height service module slot on a 32-slot MGX 8850 (see Figure 1-1).

Note The MGX RPM-XF can occupy slots 1-6 and 9-14.

The RPM-XF hardware provides forwarding technology for packet switching capabilities in excess of 2-million pps. The forwarding engine is packet based and is interfaced to the midplane of the system through a combination of switch interface technologies.

In addition to the routing function, a single high speed uplink (either OC12 POS or Gigabit Ethernet) is supported through a backcard placed in the upper backcard slot. The console and aux connections and 2 Fast Ethernet ports are available on a separate management back card, which must be located in the lower backcard slot.

The RPM-XF provides integrated IP in an ATM platform, enabling services such as integrated Point-to-Point Protocol (PPP) and IP virtual private networks (VPNs) using MPLS technology. It provides Cisco IOS-based multiprotocol routing over ATM and ATM Interface Layer 3 Termination, Local Server Interconnect over High-Speed LANs, access concentration, and switching between Ethernet LANs and the WAN facilities of the MGX 8850.



Chapter 1 Overview of the MGX RPM-XFPhysical Overview

Physical OverviewThe MGX RPM-XF-512 module fits in a 32-slot, full-height MGX 8850 chassis. The RPM-XF connects to the PXM45 switch module, the MGX-XF-UI, MGX-1OC12POS-IR, and MGX-1GE back cards, and other service modules via the midplane.

The RPM-XF receives power from the midplane and communicates over the midplane with the PXM45 using IPC over ATM. The RPM-XF runs Cisco IOS software.

The MGX 8850 is affected by the traffic load coming from the RPM-XF. All RPM-XF trunk traffic travels over the integrated ATM interface to the MGX 8850 serial bus, which switches traffic to the appropriate service module or RPM-XF. Both the RPM-XF and the PXM45 are configured manually to create connections before any user data can flow through the PXM45.

The RPM-XF has an integrated ATM interface—a permanently attached ATM port connection. The RPM-XF supports one high-speed uplink through a back card in the upper backcard slot and a console/aux dual fast ethernet (FE) back card in the lower backcard slot. The high speed uplink can be either a one-port OC12 POS or a one-port gigabit ethernet back card.

The RPM-XF installs into one slot in the MGX 8850 chassis and connects to the MGX 8850 midplane. (See Figure 1-1.) When the RPM-XF is installed (in the front of the MGX 8850 chassis), its back cards must also be connected to the midplane (from the rear of the MGX 8850 chassis) and their ports cabled to network devices. (See Figure 1-2.) See Appendix B, “Cable and Connector Specifications” for cable and connection details.

Note In the MGX 8850, slots 7 and 8 are reserved for the PXM45 cards occupying the full height of the chassis. Slots 15, 16, 31, and 32 are also reserved. (See Figure 1-1, which shows the PXM45 and RPM-XF cards installed in the front of the MGX 8850 chassis.)

Figure 1-2 shows the rear view of the MGX 8850 chassis, in which PXM45-UI-S3 cards are visible in the top slots and PXM hard disk, directly behind the PXM45s. In the same illustration, either an MGX-1OC12POS-IR or MGX-1GE back card is always installed in the upper bay back slots of the RPM-XF and the MGX-XF-UI management card is always installed in the lower bay slot directly behind the RPM-XF cards.




Figure 1-1 RPM-XF Installed in an MGX 8850 Chassis (Front View)

7553

8

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

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

FAN

FAN

ACT

STBY

FAIL

1:N RED

BERT

SRM4T-E1

ACT

STBY

FAIL

1:N RED

BERT

SRM4T-E1

ACT

STBY

FAIL

1:N RED

BERT

SRM4T-E1

ACT

STBY

FAIL

1:N RED

BERT

SRM4T-E1

SM SM

SM SM

SM

DC-B

PXM45

SYSTEMSTATUS

DC-A

MIN

MJ

HIST

ENET

ACO

ACO

CR

CONTROLPORT

HIST

DC-B

PXM45

SYSTEMSTATUS

DC-A

MIN

MJ

HIST

ENET

ACO

ACO

CR

CONTROLPORT

HIST

Power supply

AXSM

SYSTEMSTATUS

PORT 1

FAIL

STBY

ACT

PORT 5

PORT 4

PORT 3

PORT 7

PORT 6

PORT 8

PORT 2

PORT 9

PORT 13

PORT 12

PORT 11

PORT 15

PORT 14

PORT 16

PORT 10

AXSM

SYSTEMSTATUS

PORT 1

FAIL

STBY

ACT

PORT 5

PORT 4

PORT 3

PORT 7

PORT 6

PORT 8

PORT 2

PORT 9

PORT 13

PORT 12

PORT 11

PORT 15

PORT 14

PORT 16

PORT 10

AXSM

SYSTEMSTATUS

PORT 1

FAIL

STBY

ACT

PORT 5

PORT 4

PORT 3

PORT 7

PORT 6

PORT 8

PORT 2

PORT 9

PORT 13

PORT 12

PORT 11

PORT 15

PORT 14

PORT 16

PORT 10

AXSM-E

SYSTEMSTATUS

PORT 1

FAIL

STBY

ACT

PORT 5

PORT 4

PORT 3

PORT 7

PORT 6

PORT 8

PORT 2

PORT 9

PORT 13

PORT 12

PORT 11

PORT 15

PORT 14

PORT 16

PORT 10

AXSM-E

SYSTEMSTATUS

PORT 1

FAIL

STBY

ACT

PORT 5

PORT 4

PORT 3

PORT 7

PORT 6

PORT 8

PORT 2

PORT 9

PORT 13

PORT 12

PORT 11

PORT 15

PORT 14

PORT 16

PORT 10

LM2 OK

RPM-XF

LM1 OK

CB RX

CB TX

CPU OK

LM2 OK

RPM-XF

LM1 OK

CB RX

CB TX

CPU OK

LM2 OK

RPM-XF

LM1 OK

CB RX

CB TX

CPU OK

LM2 OK

RPM-XF

LM1 OK

CB RX

CB TX

CPU OK




Figure 1-2 RPM-XF Back Cards Installed in MGX 8850 (Back View)

The RPM-XF uses an RM7000A MIPS processor, a parallel packet processing engine, an integrated ATM interface, and the Serial Interface ASIC to interface with the MGX 8850 Serial Interface Controllers.

The MGX 8850 chassis can be completely populated with 12 RPM-XF blades. This allows you to use multiple RPM-XFs to achieve load sharing. Load sharing is achieved by manually distributing connections across multiple RPM-XF router blades.

7553

9

116 15 14 13 12 11 10 9 8 7 6 5 4 3 2

1732 31 30 29 28 27 26 25 24 23 22 21 20 19 18

FAN

FAN

Power supply

PXM-UI-S3

EXT CLK 2

ALARM

LAN

2

LAN

1

MP

CP

EXT CLK 1

PXM-UI-S3

EXT CLK 2

ALARM

LAN

2

LAN

1

MP

CP

EXT CLK 1

PXM-HD

ENABLED

P

RX

RT2

O

TX

SIGNAL

PXM-HD

ENABLED

P

RX

RT2

O

TX

SIGNAL

STATUS

ETHERNET 0

LNK

ACT

MGX-XF-UI

AUX

CONSOLE

ETHERNET 1

LNK

ACT

STATUS

ETHERNET 0

LNK

ACT

MGX-XF-UI

AUX

CONSOLE

ETHERNET 1

LNK

ACT

STATUS

ETHERNET 0

LNK

ACT

MGX-XF-UI

AUX

CONSOLE

ETHERNET 1

LNK

ACT

STATUS

ETHERNET 0

LNK

ACT

MGX-XF-UI

AUX

CONSOLE

ETHERNET 1

LNK

ACT

FAIL

LINK TX

TX

RX

RX

MGX-1GE

FAIL

LINK TX

TX

RX

RX

MGX-1GE

FAIL

LINK TX

TX

RX

RX

MGX-10C 12POS-IR

FAIL

LINK TX

TX

RX

RX

MGX-10C 12POS-IR




Figure 1-3 RPM-XF Connected to the MGX 8850 Midplane and to the Back Cards

The RPM-XF fits into the MGX 8850 midplane architecture so that the front card provides Cisco IOS router services, and the back cards provide physical network connectivity. The RPM-XF front card also provides ATM connectivity to the MGX 8850 Serial Interface at full-duplex OC-24.

The RPM-XF back cards are connected to the front card by a dual PCI bus (see Figure 1-3). Each RPM-XF card is equipped with two half-height back cards. Initially, two half-height high-speed uplink back cards, which must be installed in the upper slot, are supported. They are

• 1-port OC12 POS

• 1-port Gigabit Ethernet

The management card is always installed in the lower slot.

Although in most service provider network cores, the recommended routing protocols are OSPF or IS-IS, with additional use of BGP, where appropriate, the RPM-XF supports all of the following IP routing protocols:

• static route

• IGRP

• RIPv1

• RIPv2

• OSPF

• EIGRP

• IS-IS

• BGP with multiprotocol extensions

Note The MAC addresses remain with the chassis slot, not with a particular card or interface. Any new RPM-XF placed in a slot will receive the MAC addresses previously assigned to that slot. Moving an RPM-XF card to a different slot or chassis results in its receiving a new MAC address.

RPM-XF Front CardRPM-XF

high speed back card

Routing Engine- RM7000A- I/O Assy

Cellbus to PXM

PCI#1

PCI#2

ATMinterface

MGX-XF-UImanagement back card

Cisco MGX 8850midplane 75

868

LAN

Aux

Console



Chapter 1 Overview of the MGX RPM-XFSystem Specifications

System SpecificationsTable 1-1 summarizes the key attributes of the RPM-XF card.

MGX 8850 CellbusThe MGX 8850 cellbus in the MGX 8850 midplane communicates between the RPM-XF, service modules (cellbus slaves) and the PXM45 (cellbus master) (see Figure 1-3). Each cellbus is connected to a set of PXM45 cards. Only one cellbus can be active at a time.

Communication from master to slaves consists of a broadcast to all slaves. The first byte of the cell header contains addressing information. Each slave will monitor data traffic and “pick up” cells that are destined to its slot. Also, a multicast bit allows all slaves to receive a cell simultaneously.

Communication from the slaves to the master is more complicated. Because many slaves might attempt to transmit simultaneously, arbitration among slaves is required. At the start of a given cell period, the master will poll all slaves to see if they have anything to send. By the end of the current cell, the master will grant, or allow, one of the slaves to transmit. Polling and data transmission occur simultaneously.

Table 1-1 RPM-XF Card Specification

Front card RPM-XF

Card dimensions 15.65" x 15.83" (double-height)

Weight (front and back card)

6.75 lb

Processor 400 MHz RM7000A RISC

Power consumption 110W

Cellbus interface speed OC-3

Serial interface speed OC-24

Memory Up to 512 Mbytes DRAM, up to 64 Mbytes Flash.

Console port Configuration Port. Asynch interface speed based on config-register up to 115,200 baud.

Auxiliary port Maintenance Port. Asynch interface speed configurable up to 115,200 baud. See “Setting the Port Speed for the Console and Auxiliary Ports” section on page 4-7 for more information

Back cards

(port adapters)

MGX-XF-UI Management Back Card with 2 Fast Ethernet (100BaseT). ports.

Two high-speed back cards:

• MGX-1OC12POS-IR

• MGX-1GE



Chapter 1 Overview of the MGX RPM-XFMGX 8850 Serial Bus Interface

MGX 8850 Serial Bus InterfaceThe ATM connection is a permanent, internal ATM interface that connects directly to the MGX 8850 midplane. The ATM interface connects to a high speed cross-bar switch through the MGX 8850 Serial Bus Interface. The Serial Bus Interface is comprised of 4 High-Speed Serial Links in two redundant sets (A and B). These High-Speed Serial Links carry serial data at a bit-rate of 1.25 Gigabits per second. Each link has separate transmit and receive lines, with differential signal transmission using Gigabit Ethernet SERDES transceivers.

The RPM-XF connects to the Serial Bus Interface through a dedicated, ATM cell-based ASIC. Packet-to-cell translation is provided through two dedicated segmentation and reassembly (SAR) devices that support cell rates of OC-24 through the Serial Bus ASIC.

RPM-XF Midplane ConnectorThe MGX 8850 cellbus and the RPM-XF back cards connect through two sets of connectors placed at the rear of the RPM-XF motherboard (see Figure 1-3). The two connectors each have 360 pins, for a total of 720 pins.

Front Panel LEDsThe LEDs indicate the current operating condition of the RPM-XF (see Figure 1-4). You can observe the LEDs and note the fault condition the RPM-XF is encountering. If you need assistance, contact your system administrator or TAC, if necessary. For a table showing how to interpret RPM-XF front panel LED activity, see Appendix A, “Maintaining the MGX RPM-XF,” the “Reading Front Panel LEDs” section.



Chapter 1 Overview of the MGX RPM-XFCisco IOS Software Compatibility

Figure 1-4 RPM-XF Front Panel

Cisco IOS Software CompatibilityThe RPM-XF is supported in Cisco IOS Release 12.2(8)YP.

For more information about RPM-XF software configuration, refer to the Cisco IOS configuration and command reference documentation.

7553

4

LM2 OK

RPM-XF

LM1 OK

CB RX

CB TX

CPU OK

LM2 OK

LM1 OK

CB RX

CB TX

CPU OK

C H A P T E R



2Preparing to Install the MGX RPM-XF

This chapter describes the tasks you must perform before you begin to install the MGX Route Processor Module (RPM-XF). This chapter includes the following sections:

• Safety Recommendations

• Maintaining Safety with Electricity

• General Site Requirements

• Installation Checklist

• Creating a Site Log

• Preparing to Connect to a Network

Safety Recommendations

Note The RPM-XF is a service module that fits in the MGX 8850 chassis. Refer to the Cisco MGX 8850 Routing Switch Installation Guide for further recommendations about safety.

The guidelines that follow help ensure your safety and protect the MGX 8850 equipment. The list of guidelines may not address all potentially hazardous situations in your working environment, so be alert, and exercise good judgement at all times.

The safety guidelines are as follows:

• Keep the chassis area clear and dust-free before, during, and after installation.

• Keep tools away from walk areas where people could fall over them.

• Do not wear loose clothing or jewelry, such as rings, bracelets, or chains, which may become caught in the chassis.

• Wear safety glasses if you are working under any conditions that may be hazardous to your eyes.

• Do not perform any actions that create a potential hazard to people or make the equipment unsafe.

• Never attempt to lift an object that is too heavy for one person to handle.



Chapter 2 Preparing to Install the MGX RPM-XFMaintaining Safety with Electricity

Maintaining Safety with Electricity

Warning Before working on a chassis or working near power supplies, unplug the power cords on an AC-powered system. On a DC-powered system, disconnect the power at the circuit breakers.

Follow these guidelines when working on equipment powered by electricity:

• Locate the emergency power-off switch for the room in which you are working. If an electrical accident occurs, you can quickly turn off the power.

• Do not work alone if potentially hazardous conditions exist anywhere in your workspace.

• Never assume that power is disconnected from a circuit—Always check the circuit.

• Carefully look for possible hazards in your work area, such as moist floors, ungrounded power extension cords, or missing safety grounds.

• If an electrical accident occurs:

– Use caution—Do not let yourself become a victim.

– Disconnect power from the system.

– If possible, send another person to get medical aid. Otherwise, assess the condition of the victim then call for help.

• Use the MGX 8850 AC and MGX 8850 DC systems within their marked electrical ratings and product usage instructions.

• Install the MGX 8850 AC or MGX 8850 DC systems with the following local, national, or international electrical codes:

– United States—National Fire Protection Association (NFPA70), United States National Electrical Code.

– Canada—Canadian Electrical Code, Part 1, CSA C22.1.

– Other countries—International Electromechanical Commission (IEC) 364, Part 1 through Part 7.

• MGX 8850 AC models are shipped with a 3-wire electrical cord with a grounding-type plug that fits only a grounding type power outlet. This is a safety feature that you should not circumvent. Equipment grounding should comply with local and national electrical codes.

• MGX 8850 DC models are equipped with DC power entry modules and require you to terminate the DC input wiring on a DC source capable of supplying at least 60A. A 60A circuit breaker is required at the 48 VDC facility power source. An easily accessible disconnect device should be incorporated into the facility wiring. Be sure to connect the grounding wire conduit to a solid earth ground. A closed loop ring is recommended to terminate the ground conductor at the ground stud.

• Other DC power guidelines are as follows:

– Only a DC power source that complies with the safety extra low voltage (SELV) requirements of UL 1950, CSA C22.2 No. 950-95, EN 60950 and IEC 950 can be connected to an MGX 8850 DC-input power entry module.

– MGX 8850 DC which is equipped with DC power entry modules is intended only for installation in a restricted access location. In the United States, a restricted access area is in accordance with Articles 110–16, 110–17, and 110–18 of the National Electrical Code ANSI/NFPA 70.



Chapter 2 Preparing to Install the MGX RPM-XFGeneral Site Requirements

Preventing Electrostatic Discharge DamageElectrostatic discharge (ESD) can damage equipment and impair electrical circuitry. It occurs when electronic components are improperly handled and can result in complete or intermittent failures.

Always follow ESD prevention procedures when removing and replacing components. Ensure that the chassis is electrically connected to earth ground. Wear an ESD preventive wrist strap, ensuring that it makes good skin contact. Connect the clip to an unpainted surface of the chassis frame to safely channel unwanted ESD voltages to ground. To properly guard against ESD damage and shocks, the wrist strap and cord must operate effectively. If no wrist strap is available, ground yourself by touching the metal part of the chassis.

Caution For safety, periodically check the resistance value of the antistatic strap, which should be between 1 and 10 megohms (Mohms).

General Site RequirementsThis section describes the requirements your site must meet for safe installation and operation of your system. Ensure that your site is properly prepared before beginning installation.

Power Supply ConsiderationsCheck the power at your site to ensure that you are receiving “clean” power (free of spikes and noise). Install a power conditioner if necessary.

Warning The MGX 8850 and RPM-XF are designed to work with TN power systems.

The AC power supply of the RPM-XF is part of the MGX 8850 chassis. The RPM-XF, when installed in the MGX 8850 chassis, receives –48 volts DC power from the midplane.

The DC power supply of the RPM-XF is part of the MGX 8850 chassis. The RPM-XF, when installed in the MGX 8850 chassis, receives –48 volts DC power from the midplane.

The RPM-XF is installed in the MGX 8850 chassis. Refer to the Cisco MGX 8850 Routing Switch Installation Guide. The location of the MGX 8850 chassis and the layout of your equipment rack or wiring room are extremely important for proper system operation. Equipment placed too close together, inadequate ventilation, and inaccessible panels can cause system malfunctions and shutdowns, and can make RPM-XF maintenance difficult.



Chapter 2 Preparing to Install the MGX RPM-XFInstallation Checklist

Installation ChecklistThe Installation Checklist lists the procedures for initial hardware installation of a new RPM-XF. Make a copy of this checklist and mark the entries as you complete each procedure. Include a copy of the checklist for each system in your Site Log (see the next section, “Creating a Site Log”).

RPM-XF installation checklist for site _________________________________________

Creating a Site LogThe Site Log provides a record of all actions relevant to the RPM-XF. Keep it near the chassis where anyone who installs or maintains the RPM-XF has access to it. Use the Installation Checklist (see the previous section, “Installation Checklist”) to verify the steps in the installation and maintenance of your RPM-XF. Site Log might include the following entries:

• Installation progress—Make a copy of the “Installation Checklist” and insert it into the Site Log. Fill in the checklist as you complete each procedure.

Installation Checklist Verified by Date

Installation checklist copied

Background information placed in the Site Log

Site power voltages verified

Required tools available

Additional equipment available

MGX RPM-XF received

MGX RPM-XF-UI received

Cisco Documentation CD received

Cisco Information Packet received

Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide received

Optional printed documentation received

Chassis components verified

Initial electrical connections established

ASCII terminal or PC attached to MGX-XF-UI console port

Signal distance limits verified

RPM-XF and MGX-XF-UI properly installed in corresponding chassis slots.

Startup sequence steps completed

Initial system operation verified

Software image verified



Chapter 2 Preparing to Install the MGX RPM-XFPreparing to Connect to a Network

• Upgrade and maintenance procedures—Use the Site Log as a record of ongoing system maintenance and expansion. Each time a procedure is performed on the RPM-XF, update the Site Log to reflect the following conditions:

– Configuration changes

– Changes and updates to Cisco IOS software

– Maintenance schedules and requirements

– Corrective maintenance procedures performed

– Intermittent problems

– Related comments and notes

Preparing to Connect to a NetworkWhen setting up your RPM-XF in the MGX 8850, consider distance limitations and potential electromagnetic interference (EMI) as defined by the EIA.

Note The Fast Ethernet, console, and auxiliary ports contain safety extra-low voltage (SELV) circuits. Connect them only to SELV-circuit equipment.

Ethernet ConnectionThe Ethernet ports located on the MGX-XF-UI back card support IEEE Ethernet standard 802.3 and Fast Ethernet standard 802.3u. The MGX-XF-UI back card implementation supports the following connections:

• 10BaseT— Ethernet on unshielded twisted-pair (UTP) cable. The maximum segment distance is 328 feet (100 meters). UTP cables look like wiring used for ordinary telephones; however, UTP cables meet certain electrical standards that telephone cables do not. The 10BaseT Ethernet operates at 10Mbs and can be connected through the RJ-45 connector.

• 100BaseTX—100BaseT Ethernet, half and full duplex over Category 5 UTP, Electronics Industry Association and Telecommunications Industry Association [EIA/TIA]-568-compliant cable. The 100BaseT Ethernet operates at 100Mbs and can be connected through the RJ-45 connector.

The cables required to connect the MGX-XF-UI Fast Ethernet ports to an Ethernet network are not included. For cable ordering information, contact customer service.

For cable and port pinouts, see Appendix B, “Cable and Connector Specifications.”

Console and Auxiliary PortsThe MGX-XF-UI includes asynchronous serial console and auxiliary ports. The console and auxiliary ports provide local administrative access to the RPM-XF. This section discusses important cabling information to consider before connecting a console terminal to the console port or the auxiliary port.



Chapter 2 Preparing to Install the MGX RPM-XFPreparing to Connect to a Network

The main difference between the console and auxiliary ports is that the auxiliary port supports hardware flow control and the console port does not. Flow control paces the transmission of data, ensuring that the receiving device can absorb the data sent to it before the sending device sends more. When the buffers on the receiving device are full, a message is sent to the sending device to suspend transmission until the data in the buffers has been processed.

Console Port ConnectionThe MGX-XF-UI includes an EIA/TIA-232 asynchronous serial console port (RJ-45). This port will appear as a DTE device at the end of the cable.

Note Cisco Systems does not provide console cables in the MGX-RPM-XF-512 or MGX-XF-UI kit. Console cables can be ordered as spares from Cisco Systems.

To connect an ASCII terminal to the console port, use the RJ-45 rollover cable with the female RJ-45-to-DB-25 adapter (labeled “Terminal”). To connect a PC running terminal emulation software to the console port, use the RJ-45 rollover cable with the female RJ-45-to-DB-9 adapter (labeled “Terminal”). The default parameters for the console port are 9600 baud, 8 data bits, no parity, and 1 stop bit.

The console port does not support hardware flow control. For detailed information about installing a console terminal, see Chapter 3, “Installing the MGX RPM-XF Front and Back Cards.” For cable and port pinouts, see Appendix B, “Cable and Connector Specifications.”

Auxiliary Port ConnectionsThe RPM-XF includes an EIA/TIA-232 asynchronous serial auxiliary port (RJ-45) that supports flow control. This port will appear as a DTE device at the end of the cable.

Note Connecting a modem to the auxiliary port on the MGX-XF-UI is not supported.

Note Cisco Systems does not provide console cables in the MGX-RPM-XF-512 or MGX-XF-UI kit. Console cables can be ordered as spares from Cisco Systems.

For detailed information about connecting devices to the auxiliary port, see Chapter 3, “Installing the MGX RPM-XF Front and Back Cards.” For cable and port pinouts, see Appendix B, “Cable and Connector Specifications.”

C H A P T E R



3Installing the MGX RPM-XF Front and Back Cards

This chapter describes how to install the MGX Route Processor Module (RPM-XF), the MGX-XF-UI management back card, and the high-speed uplink back cards. This chapter includes the following sections:

• Inspecting the System

• Required Tools and Parts

• Installing and Removing the RPM-XF Cards

• Installing and Removing Back Cards in the MGX 8850 Midplane

• Connecting a Console Terminal or PC to the MGX-XF-UI Console Port

Inspecting the SystemDo not unpack the RPM-XF front card and MGX-XF-UI back card until you are ready to install them. If the site is not ready, keep the cards in the shipping container to protect them. When you determine where you want to install the RPM-XF and the corresponding MGX-XF-UI back card and are ready to begin the installation, unpack the cards.

The RPM-XF, MGX-XF-UI, and any optional equipment you ordered might be shipped in more than one container. When you unpack each shipping container, check the packing list to ensure that you received all of the following items:

• MGX RPM-XF and MGX-XF-UI

Note Cisco Systems does not provide cables required to connect the back cards to external devices. These cables must be ordered from commercial cable vendors. For pinouts to these cables, see Appendix B, “Cable and Connector Specifications.”

Cisco Systems also does not provide console and auxiliary cables in the RPM-XF or MGX-XF-UI kit. Console and auxiliary cables can be ordered as spares from Cisco Systems.

• Cisco Information Packet publication

• Cisco Documentation CD-ROM

• Optional printed publications, as specified on your order

Inspect all items for shipping damage. If anything appears to be damaged, or if you encounter problems when installing or configuring your system, contact the Cisco Technical Assistance Center (TAC).



Chapter 3 Installing the MGX RPM-XF Front and Back CardsRequired Tools and Parts

Required Tools and Parts Installing the RPM-XF and MGX-XF-UI requires tools and parts that are not provided as standard equipment. You will need the following tools and equipment to install the RPM-XF and MGX-XF-UI in the MGX 8850 chassis:

• Number 2 Phillips-head screwdriver

• ESD preventive wrist strap

• Cables for Ethernet back card interfaces

• Console and auxiliary cables

– Standard RJ-45-to-RJ-45 rollover cable

Note For more information, see Appendix B, “Cable and Connector Specifications,” in the “Identifying a Rollover Cable” section.

– Cable adapters

RJ-45-to-DB-9 female DTE adapter (labeled “Terminal”)

RJ-45-to-DB-25 female DTE adapter (labeled “Terminal”)

Note For cable information, see Chapter 2, “Preparing to Install the MGX RPM-XF.” For cable pinouts, see Appendix B, “Cable and Connector Specifications.”

• Console terminal (an ASCII terminal or a PC running terminal emulation software) configured for 9600 baud, 8 data bits, no parity, and 1 stop bit.

See the “Connecting a Console Terminal or PC to the MGX-XF-UI Console Port” section later in this chapter for the procedure to connect a console terminal.

Installing and Removing the RPM-XF CardsThe following sections describe how to install and remove the RPM-XF in the MGX 8850 midplane.

Note Installing and removing RPM-XF service modules is similar to installing and removing other service modules, such as an AXSM, which also goes into the midplane from the front of the MGX 8850 chassis.

Warning Only trained and qualified personnel should install or replace this equipment.

Warning Before handling the RPM-XF, attach a wrist strap.

Note It is not necessary to power OFF the MGX 8850 chassis. The RPM-XF can be removed and inserted in the MGX 8850 chassis while the system is up and running.



Chapter 3 Installing the MGX RPM-XF Front and Back CardsInstalling and Removing the RPM-XF Cards

Before Installing Front or Back CardsBefore you install a front or back card, perform the following inspections.

• Inspect the backplane for bent pins or bent dividers between pin rows (see Figure 3-1).

If the backplane has bent pins, do not install a card in that slot. Installing a card into a damaged backplane slot will damage the connector on the card.

Figure 3-1 Backplane Inspection Check Points

• Inspect the card for damaged holes on the connector (see Figure 3-2).

If the connector has damaged holes, do not install the card. Installing a card that has a damaged connector will damage the backplane. Return damaged cards to Cisco Systems.

Figure 3-2 Damaged Connectors on the Card

Bent pins Bent divider 4845

6

4845

9

Damaged holes




Installing the RPM-XF Front CardPerform the following steps to install the RPM-XF in the MGX 8850 chassis.

Step 1 Position the rear edge of the card over the appropriate slot card guide at the top and bottom of the cage.

Note Verify that the intended slot for the card is the correct slot before you insert the card.

Step 2 Carefully slide the RPM-XF card all the way into the slot.

Step 3 Press both extractor levers until they snap into the vertical position.

Note The RPM-XF should slide in and out with only slight friction on the adjacent board EMI gaskets. Do not use force. Investigate any binding.

Removing the RPM-XF CardDouble-height front cards have a latch on the ejector at both the top and the bottom of the front panel. (See Figure 3-3.)

Warning To prevent damage to the cards from static electricity, put on a wrist strap and connect it to any convenient metal contact on the system or card cage before you touch any cards.

Figure 3-3 Front Card Extractor Latch

Perform the following steps to remove an RPM-XF front card from the MGX 8850 chassis.

Top of card

Slot

H82

93




Step 1 Press the tip of a small, flat-head screwdriver into the slot of the extractor lever (see Figure 3-3); press until the latch springs open, to approximately 10°.

Step 2 To separate the card from the backplane connector, pull the extractor lever(s) out.

Step 3 Gently pull the RPM-XF out along the guides. If it sticks, jiggle it gently.

Step 4 Carefully pull the card out of the card cage. Store it in an anti-static bag.

Note The RPM-XF slides along plastic guides into the front of the MGX 8850 system (see Figure 3-4) and connects to the chassis midplane. When removing the RPM-XF, you may feel some resistance as the midplane connector unseats.



Chapter 3 Installing the MGX RPM-XF Front and Back CardsInstalling and Removing Back Cards in the MGX 8850 Midplane

Figure 3-4 RPM-XF Installed in the MGX 8850 Chassis (Front View)

Installing and Removing Back Cards in the MGX 8850 MidplaneThe following sections describe how to install and remove the MGX-XF-UI management and high-speed uplink back cards (MGX-1GE and MGX-1OC12POS-IR) from the MGX 8850 midplane.

7553

8

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

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

FAN

FAN

ACT

STBY

FAIL

1:N RED

BERT

SRM4T-E1

ACT

STBY

FAIL

1:N RED

BERT

SRM4T-E1

ACT

STBY

FAIL

1:N RED

BERT

SRM4T-E1

ACT

STBY

FAIL

1:N RED

BERT

SRM4T-E1

SM SM

SM SM

SM

DC-B

PXM45

SYSTEMSTATUS

DC-A

MIN

MJ

HIST

ENET

ACO

ACO

CR

CONTROLPORT

HIST

DC-B

PXM45

SYSTEMSTATUS

DC-A

MIN

MJ

HIST

ENET

ACO

ACO

CR

CONTROLPORT

HIST

Power supply

AXSM

SYSTEMSTATUS

PORT 1

FAIL

STBY

ACT

PORT 5

PORT 4

PORT 3

PORT 7

PORT 6

PORT 8

PORT 2

PORT 9

PORT 13

PORT 12

PORT 11

PORT 15

PORT 14

PORT 16

PORT 10

AXSM

SYSTEMSTATUS

PORT 1

FAIL

STBY

ACT

PORT 5

PORT 4

PORT 3

PORT 7

PORT 6

PORT 8

PORT 2

PORT 9

PORT 13

PORT 12

PORT 11

PORT 15

PORT 14

PORT 16

PORT 10

AXSM

SYSTEMSTATUS

PORT 1

FAIL

STBY

ACT

PORT 5

PORT 4

PORT 3

PORT 7

PORT 6

PORT 8

PORT 2

PORT 9

PORT 13

PORT 12

PORT 11

PORT 15

PORT 14

PORT 16

PORT 10

AXSM-E

SYSTEMSTATUS

PORT 1

FAIL

STBY

ACT

PORT 5

PORT 4

PORT 3

PORT 7

PORT 6

PORT 8

PORT 2

PORT 9

PORT 13

PORT 12

PORT 11

PORT 15

PORT 14

PORT 16

PORT 10

AXSM-E

SYSTEMSTATUS

PORT 1

FAIL

STBY

ACT

PORT 5

PORT 4

PORT 3

PORT 7

PORT 6

PORT 8

PORT 2

PORT 9

PORT 13

PORT 12

PORT 11

PORT 15

PORT 14

PORT 16

PORT 10

LM2 OK

RPM-XF

LM1 OK

CB RX

CB TX

CPU OK

LM2 OK

RPM-XF

LM1 OK

CB RX

CB TX

CPU OK

LM2 OK

RPM-XF

LM1 OK

CB RX

CB TX

CPU OK

LM2 OK

RPM-XF

LM1 OK

CB RX

CB TX

CPU OK




Installing the Back CardsUse the following procedure to install the MGX-XF-UI management and high-speed uplink back cards in the MGX 8850 midplane:

Note Ensure that the two extractor levers are in the “in” position. When the card is being inserted into the slot, the levers should be vertical along the line of the back card.

Step 1 Position the rear card guides over the appropriate slot (directly behind the RPM-XF in the chassis) at the top and bottom of the card cage.

Note The MGX-XF-UI is always installed in the lower slot and the high-speed uplink back cards are always installed in the upper slot.

There are two connectors each with 360 pins, for a total of 720 pins. The top and bottom connectors are mechanically identical.

Step 2 Push the back card firmly but gently into the slot and then all the way into the connectors on the midplane.

Note Correct alignment between connector pins and receptacles is extremely important. First, make sure all pins on the card are straight. Make sure the connector on the card is aligned with the midplane connector. Insert the card gently. It may be necessary to push the card slightly to one side to achieve alignment.

Step 3 Tighten the two captive screws on the back card faceplate.

Tighten the upper and lower screws to prevent misalignment of the card. Do not overtighten the screws. Tighten only enough to secure the card.

Back cards installed in an MGX 8850 chassis and connected to the midplane are illustrated in Figure 3-5.

Note Figure 3-5 shows RPM-XF back cards in slots 9, 10, 11, and 12. You can see MGX-XF-UI cards in the bottom slots, MGX-1GE cards in slot 9 and 10, and MGX-1OC12POS-IR cards in slots 11 and 12.

Removing the Back CardsUse the following procedure to remove the back cards from the MGX 8850 midplane.

Step 1 Label and remove any cables connected to the back card.

Step 2 Use a flat screwdriver to remove the two retaining screws in the back card faceplate.

Step 3 Pull both extractor levers out to the horizontal position.

This action will start the removal of the card.




Step 4 Gently pull the card out of the card cage.

Figure 3-5 RPM-XF Back Cards Connected to an MGX 8850 (Back View)

7553

9

116 15 14 13 12 11 10 9 8 7 6 5 4 3 2

1732 31 30 29 28 27 26 25 24 23 22 21 20 19 18

FAN

FAN

Power supply

PXM-UI-S3

EXT CLK 2

ALARM

LAN

2

LAN

1

MP

CP

EXT CLK 1

PXM-UI-S3

EXT CLK 2

ALARM

LAN

2

LAN

1

MP

CP

EXT CLK 1

PXM-HD

ENABLED

P

RX

RT2

O

TX

SIGNAL

PXM-HD

ENABLED

P

RX

RT2

O

TX

SIGNAL

STATUS

ETHERNET 0

LNK

ACT

MGX-XF-UI

AUX

CONSOLE

ETHERNET 1

LNK

ACT

STATUS

ETHERNET 0

LNK

ACT

MGX-XF-UI

AUX

CONSOLE

ETHERNET 1

LNK

ACT

STATUS

ETHERNET 0

LNK

ACT

MGX-XF-UI

AUX

CONSOLE

ETHERNET 1

LNK

ACT

STATUS

ETHERNET 0

LNK

ACT

MGX-XF-UI

AUX

CONSOLE

ETHERNET 1

LNK

ACT

FAIL

LINK TX

TX

RX

RX

MGX-1GE

FAIL

LINK TX

TX

RX

RX

MGX-1GE

FAIL

LINK TX

TX

RX

RX

MGX-10C 12POS-IR

FAIL

LINK TX

TX

RX

RX

MGX-10C 12POS-IR



Chapter 3 Installing the MGX RPM-XF Front and Back CardsConnecting a Console Terminal or PC to the MGX-XF-UI Console Port

Connecting a Console Terminal or PC to the MGX-XF-UI Console Port

The MGX-XF-UI management back card includes asynchronous serial console and auxiliary ports. These ports provide administrative access to the RPM-XF locally using a console terminal.

Use the following procedure to connect a terminal (an ASCII terminal or a PC running terminal emulation software) to the console port on the MGX-XF-UI.

Step 1 Connect the terminal (see Figure 3-6) using the thin, flat, RJ-45-to-RJ-45 rollover cable (which looks like a telephone cable) and an RJ-45-to-DB-9 or RJ-45-to-DB-25 adapter (labeled “Terminal”) to the console port on the MGX-XF-UI.

For cable pinouts, see Appendix B, “Cable and Connector Specifications.”

Step 2 Configure your terminal or PC terminal emulation software for 9600 baud, 8 data bits, no parity, and 1 stop bit.

Note The default parameters for the console port on the MGX-XF-UI are 9600 baud, 8 data bits, no parity and 1 stop bit.



Chapter 3 Installing the MGX RPM-XF Front and Back CardsConnecting a Console Terminal or PC to the MGX-XF-UI Console Port

Figure 3-6 Connecting a Console Terminal to the MGX-XF-UI Console Port

Note Changing the console speed on the terminal server is not recommended as it may put the RPM-XF in ROMMON mode. To avoid this, set the config-register to 0x2102.

1

16 15 14 13 12 11 10 9 8 7 6 5 4 3 2

17

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18

FAN

FAN

Power supply

PXM-UI-S3

EXT CLK 2

ALARM

LAN

2

LAN

1

MP

CP

EXT CLK 1

PXM-UI-S3

EXT CLK 2

ALARM

LAN

2

LAN

1

MP

CP

EXT CLK 1

PXM-HD

ENABLED

P

RX

RT2

O

TX

SIGNAL

PXM-HD

ENABLED

P

RX

RT2

O

TX

SIGNAL

STATUS

ETHERNET 0

LNK

ACT

MGX-XF-UI

AUX

CONSOLE

ETHERNET 1

LNK

ACT

STATUS

ETHERNET 0

LNK

ACT

MGX-XF-UI

AUX

CONSOLE

ETHERNET 1

LNK

ACT

STATUS

ETHERNET 0

LNK

ACT

MGX-XF-UI

AUX

CONSOLE

ETHERNET 1

LNK

ACT

STATUS

ETHERNET 0

LNK

ACT

MGX-XF-UI

AUX

CONSOLE

ETHERNET 1

LNK

ACT

FAIL

LINK TX

TX

RX

RX

MGX-1GE

FAIL

LINK TX

TX

RX

RX

MGX-1GE

FAIL

LINK TX

TX

RX

RX

MGX-10C 12

POS-IR

FAIL

LINK TX

TX

RX

RX

MGX-10C 12

POS-IR

7564

9

RJ-45 rollover cable

PC

AU

XS

ER

0E

TH

OK

LA

N

I/Ocard

RJ-45-to-DB-25 adapter

C H A P T E R



4Installing and Configuring the MGX-XF-UI Management Back Card

This chapter describes how to install and configure the MGX-XF-UI management back card that is used in conjunction with and to configure the Cisco Route Processor Module (RPM-XF). This chapter includes the following sections:

• Overview and Features

• Installation Guidelines

• Software Configuration

• Troubleshooting the Installation

Overview and FeaturesThe MGX-XF-UI management back card (Figure 4-1) provides remote management capabilities for the RPM-XF.



Chapter 4 Installing and Configuring the MGX-XF-UI Management Back CardOverview and Features

Figure 4-1 MGX-XF-UI Management Back Card

The management back card provides the following features:

• Multi-speed auxiliary port—The auxiliary port (AUX) is an asynchronous EIA/TIA-232 serial port used to connect an external terminal for local administrative access. The auxiliary port is capable of operating at a user specified baud rate (1200–115200 baud).

Note Connecting to the auxiliary port through a modem is not supported.

• Multi-speed console port—The console port (Console) is an asynchronous EIA/TIA-232 serial port used to connect an external terminal for local administrative access. The console port is capable of operating at a user specified baud rate (1200–115200 baud).

Note It is recommended that the console port speed always be set to 9600 baud.

• Two fast ethernet ports—The MGX-XF-UI contains two IEEE 802.3u-compliant fast ethernet ports (Ethernet 0 and Ethernet 1) used to connect the RPM-XF to a 10BaseT or 100BaseT network management LAN.

7553

5

STATUS

ETHERNET 0

LNK

ACT

MGX-XF-UI

AUX

CONSOLE

ETHERNET 1

LNK

ACT



Chapter 4 Installing and Configuring the MGX-XF-UI Management Back CardFast Ethernet Overview

Fast Ethernet OverviewFast Ethernet is commonly used for all carrier sense multiple access/collision detection (CSMA/CD), local-area networks (LANs) that generally conform to Ethernet specifications, including Fast Ethernet under IEEE 802.3u.

IEEE 802.3u is well suited to applications where a local communication medium must carry sporadic, occasionally heavy traffic at high peak data rates. Stations on a CSMA/CD LAN can access the network at any time. Before sending data, the station listens to the network to see if it is in use. If it is, the station waits until the network is not in use, then transmits; this is a half-duplex operation. A collision occurs when two stations listen for network traffic, hear none, and transmit very close to simultaneously. When this happens, both transmissions are damaged, and the stations must retransmit. The stations detect the collision and use backoff algorithms to determine when they should retransmit.

Both Ethernet and IEEE 802.3u are broadcast networks, which means that all stations see all transmissions. Each station must examine received frames to determine whether it is the intended destination and, if it is, pass the frame to a higher protocol layer for processing.

Each physical layer protocol has a name that summarizes its characteristics in the format speed/signaling method/segment length,

where

• speed is the LAN speed in megabits per second (Mbps),

• signaling method is either baseband or broadband, and

• segment length is typically the maximum length between stations in hundreds of meters.

Therefore, 100BaseT specifies a 100-Mbps, baseband LAN with maximum network segments.

IEEE 802.3u 100BaseT Fast Ethernet SpecificationsEach Fast Ethernet port on the MGX-XF-UI back card has an RJ-45 connector to attach to Category 5 UTP for 100BaseTX. Figure 4-1 shows the Fast Ethernet MGX-RJ45-FE back card. Table 4-1 lists the cabling specifications for 100-Mbps Fast Ethernet transmission over UTP cables. Table 4-2 summarizes IEEE 802.3u 100BaseT physical characteristics.

Table 4-1 Specifications and Connection Limits for Fast Ethernet 100-Mbps Transmission

Parameter RJ-45

Cable specification Category 51 UTP2, 22 to 24 AWG

1. EIA/TIA-568 or EIA-TIA-568 TSB-36 compliant.

2. Cisco Systems does not supply Category 5 UTP RJ-45 cables. They are available commercially.

Maximum cable length —

Maximum segment length 328 ft (100 m) for 100BaseTX

Maximum network length 656 ft (200 m) (with 1 repeater)



Chapter 4 Installing and Configuring the MGX-XF-UI Management Back CardInstallation Guidelines

Installation GuidelinesThis section contains guidelines for the following procedures:

• New installation

• Replacement installation

The Cisco MGX-XF-UI back cards are cold swappable, which means you can remove and replace the back cards when all interfaces on the back cards are in the shutdown state.

Caution Handling of back cards requires proper observance of ESD practices and procedures. During installation or removal of back cards, the operator must be appropriately grounded and place all sensitive electronics in approved ESD containers or packaging.

New Installation GuidelinesFor information on installing the back cards, see the “Installing and Removing Back Cards in the MGX 8850 Midplane” section on page 3-6.

After installing the MGX-XF-UI for the first time, you must configure it by entering the configure command. For information about configuring the management back card, see the “Software Configuration” section below.

Replacement Installation GuidelinesFor information on removing and installing the back card hardware, refer to the “Installing and Removing Back Cards in the MGX 8850 Midplane” section on page 3-6.

If a management back card is replaced, the system automatically downloads the necessary information from the RPM-XF front card. There is no need to configure the new back card unless the front card has been reloaded or switched over subsequent to the removal of the back card. After the information is downloaded, the system recognizes only those interfaces that match the previous management back card configuration (those configured as Up).

Table 4-2 EEE 802.3u Physical Characteristics

Parameter 100BaseTX

Data rate (Mbps) 100

Signaling method Baseband

Maximum segment length 100 m between DTE1 and repeaters

1. DTE = data terminal equipment.

Media RJ-45

Topology Star/Hub



Chapter 4 Installing and Configuring the MGX-XF-UI Management Back CardSoftware Configuration

Software ConfigurationAfter the management back card is successfully installed you can configure the interfaces on the card.

Note You do not need to configure the management back card if this is a replacement installation. The system automatically downloads the necessary configuration information from the RPM-XF front card.

This section covers the following topics:

• Configuring the Console and Auxiliary Ports

• Configuring the Fast Ethernet Ports

Configuring the Console and Auxiliary PortsThis section covers the following topics:

• Console and Auxiliary Port Default Values

• Console and Auxiliary Port Syntax

• Configuring the Console Port

• Configuring the Auxiliary Port

• Console and Auxiliary Port Configuration Commands

• Console and Auxiliary Port Example Configuration

Console and Auxiliary Port Default Values

Table 4-3 lists default values for the console and auxiliary port on the management back card. The commands marked with an asterisk (*) are described in the Cisco IOS command reference documentation. The other commands are among those described in this chapter.

Console and Auxiliary Port Syntax

To specify a serial port in a configuration command, use the syntax in Table 4-4 to identify the serial interfaces on the management back card.

Table 4-3 Console/Auxiliary Port Defaults

Command Name Default Setting Command Syntax

stopbits 1 stopbits [1 | 1.5 | 2 ]

parity none parity [even | mark | none | odd | space ]

databits 8 databits [5 | 6 | 7 | 8]

speed 9600 speed [1200 | 2400 | 4800 | 9600 | 19200 | 38400 | 57600 | 115200 ]

length* 24 length size

width* 80 width size




The following example shows the syntax for configuring the console port on the management back card.

Router(config)# line console 0

The following example shows the syntax for configuring the auxiliary port on the management back card.

Router(config)# line aux 0

Configuring the Console Port

After you verify that the management back card is installed correctly, use the following procedure to configure the console port.

Step 1 At the global configuration prompt, specify the console port by entering line console 0. For example,

Router(config)# line console 0

Step 2 Configure the console port speed. For example,

Router(config-line)# speed 9600

Step 3 Configure the number of data bits for the console port. For example,

Router(config-line)# databits 8

Step 4 Configure the number of stop bits for the console port. For example,

Router(config-line)# stopbits 1

Step 5 Configure the parity for the console port. For example,

Router(config-line)# parity none

Step 6 Add any other configuration subcommands required.

Step 7 When you have included all of the configuration subcommands to complete the configuration, press Cntl-Z to exit the configuration mode.

Step 8 Write the new configuration to memory.

Router# copy running-config startup-config

The system displays an OK message when the configuration is saved.

After you complete your configuration, check it using show line console 0.

Table 4-4 Console/Auxiliary Port Syntax

Type of Interface Port

Console port 0

Auxiliary port 0




Configuring the Auxiliary Port

After you verify that the management back card is installed correctly, use the following procedure to configure the auxiliary port.

Step 1 At the global configuration prompt, specify the auxiliary port by entering line aux 0. For example,

Router(config)# line aux 0

Step 2 Configure the auxiliary port speed. For example,

Router(config-line)# speed 9600

Step 3 Configure the number of data bits for the auxiliary port. For example,

Router(config-line)# databits 8

Step 4 Configure the number of stop bits for the auxiliary port. For example,

Router(config-line)# stopbits 1

Step 5 Configure the parity for the auxiliary port. For example,

Router(config-line)# parity none


Step 7 When you have included all of the configuration subcommands to complete the configuration, press Cntl-Z to exit configuration mode.




After you complete your configuration, check it using show line aux 0.

Console and Auxiliary Port Configuration Commands

The following sections present some of the commands that you can use to customize your console and auxiliary port configuration.


• Setting the Port Speed for the Console and Auxiliary Ports

• Setting the Number of Data Bits for the Console and Auxiliary Ports

• Setting the Number of Stop Bits for the Console and Auxiliary Ports

• Setting the Parity for the Console and Auxiliary Ports

Setting the Port Speed for the Console and Auxiliary Ports

You can use the speed command to set the speed for the port.

speed baud rate

The default is 9600 baud.




Note Setting the console port speed also adjusts the ROM Monitor configuration register for the console port speed.

Because the ROM Monitor only supports a limited number of console port speeds, it is recommended that the console port speed be set to one of the following baud rates: 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200.

Because the ROM Monitor only supports the auxiliary port at 9600 baud, it is recommended that the auxiliary port speed be set to 9600 baud.

In this example, the console port is setup to use 9600 baud.

Router(config)# line console 0Router(config-line)# speed 9600

Setting the Number of Data Bits for the Console and Auxiliary Ports

You can use the databits command to set the number of data bits for the port.

databits [5 | 6 | 7 | 8]

The default is 8 data bits.

Note Because the ROM monitor only supports 8 data bits, it is recommended that the number of data bits be set to 8.

In this example, the console port is setup to use 8 data bits.

Router(config)# line console 0Router(config-line)# databits 8

Setting the Number of Stop Bits for the Console and Auxiliary Ports

You can use the stopbits command to set the number of stop bits for the port.

stopbits [1 | 1.5 | 2]

The default is 1 stop bit.

Note Because the ROM monitor only supports 1 stop bit, it is recommended that the number of stop bits be set to 1.

In this example, the console port is setup to use 1 stop bit.

Router(config)# line console 0Router(config-line)# stopbits 1

Setting the Parity for the Console and Auxiliary Ports

You can use the parity command to set the parity for the port.

parity [even | mark | none | odd | space]

The default is no parity.




Note Because the ROM monitor does not support parity, it is recommended that parity be set to none.

In this example, the console port is setup to use no parity.

Router(config)# line console 0Router(config-line)# parity none

Console and Auxiliary Port Example Configuration

The following is an example of configuration file commands for the console and auxiliary ports on the management back card.

line console 0 databits 8 stopbits 1 parity none speed 115200 length 25 width 80

line aux 0 databits 8 stopbits 1 parity none speed 9600 length 24 width 80

Configuring the Fast Ethernet PortsThis section covers the following topics:

• Fast Ethernet Default Values

• Fast Ethernet Port Syntax

• Configure the Fast Ethernet Port

• Fast Ethernet Port Configuration Commands

• Fast Ethernet Port Example Configuration

• Using show Commands to Check System Status

Fast Ethernet Default Values

Table 4-5 lists the default values for the fast ethernet ports on the management back card. The commands marked with an asterisk (*) are described in the Cisco IOS command reference documentation. The other commands are among those described in this chapter.

The table includes the command used for modifying the default value and indicates whether a value needs to be the same on the remote end of the connection.




Fast Ethernet Port Syntax

To specify an interface number in a configuration command, use the syntax in Table 4-6 to identify fast ethernet interfaces on the management back card.

The following example shows the syntax for configuring the first fast ethernet port on the management back card.

Router(config)# interface FastEthernet 2/0

Configure the Fast Ethernet Port

After you verify that the management back card is installed correctly, use the following procedure to configure the fast ethernet ports. Be prepared with the information you will need, such as the interface IP address.

The following is for creating a basic configuration—Enabling an interface.

Step 1 At the global configuration prompt, specify the fast ethernet port by entering interface FastEthernet bay/port. For example,

Router(config)# interface FastEthernet 2/0

Step 2 Assign an IP address and a subnet mask to the interface with the ip address configuration subcommand. For example,

Router(config-if)# ip address 192.168.255.255 255.255.255.0

Step 3 Configure the fast ethernet port speed. For example,

Router(config-if)# speed auto

Step 4 Configure the fast ethernet port duplex. For example,

Router(config-if)# duplex auto

Table 4-5 Fast Ethernet Port Defaults

Command Name Default Setting Command SyntaxRemote Side Setting

duplex auto duplex [auto | half | full] Same.

speed auto speed [10 | 100 | auto] Same.

keepalive* 10 second keepalive [no] keepalive period Same.

mtu1*

1. mtu=maximum transmission unit

1500 mtu size Same.

length* 24 length size —

width* 80 width size —

Table 4-6 Fast Ethernet Port Syntax

Type of Interface Bay (always 2) Port

Fast Ethernet 2/ [0 | 1 ]





Step 6 Enter the no shutdown command to enable the interface. For example,

Router(config-if)# no shutdown





After you complete the configuration, check it using show interface FastEthernet bay/port.

Fast Ethernet Port Configuration Commands

The following sections present some of the commands that you can use to customize your fast ethernet port configuration.


• Setting the Fast Ethernet Port Speed

• Setting the Fast Ethernet Port Duplex

Setting the Fast Ethernet Port Speed

You can use the speed command to set the speed for the port.

speed [auto | 10 | 100]

The default is auto negotiation.

In this example, fast ethernet port 0 is setup to use auto negotiation.

Router(config)# interface FastEthernet 2/0Router(config-line)# speed auto

Setting the Fast Ethernet Port Duplex

You can use the speed command to set the duplex mode for the port.

duplex [auto | half| full]

The default is auto negotiation.

In this example, fast ethernet port 0 is setup to use auto negotiation.

Router(config)# interface FastEthernet 2/0Router(config-line)# duplex auto




Fast Ethernet Port Example Configuration

The following is an example of configuration file commands for the console and auxiliary ports on the management back card.

interface FastEthernet2/0 ip address 10.0.0.1 255.255.255.0 no shutdown duplex auto speed autoend

Verifying Ethernet Connectivity

The ping command lets you verify that an interface port is functioning and check the path between a specific port and connected network devices. This section provides brief descriptions of the ping command. After you verify that the system has booted successfully and is operational, you can use this command to verify the status of interface ports. The remote device can be a server, a router, or a PC.

The ping command sends an echo request out to a remote device at an IP address that you specify. After sending a series of signals, the command waits a specified time for the remote device to echo the signals. Each returned signal is displayed as an exclamation point (!) on the console terminal; each signal that is not returned before the specified time-out is displayed as a period (.). A series of exclamation points (!!!!!) indicates a good connection; a series of periods (.....) or the messages [timed out] or [failed] indicate that the connection failed.

The following is an example of a successful ping command to a remote server with the address 1.1.1.10.

Router#ping 1.1.1.10

Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 1.1.1.10, timeout is 2 seconds:.!!!!Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/1 msRouter#

If the connection fails, verify that you entered the correct IP address for the remote device and that the remote device is active (powered on). Then repeat the ping command.

Using show Commands to Check System Status

Each interface maintains information about its configuration, traffic, errors and so on. You can access this information by entering the show commands. Following are descriptions and examples of show commands that display interface information and status.

Enter the show interface FastEthernet bay/port command to show general information about the interface.

Router# show interface FastEthernet 2/0FastEthernet2/0 is up, line protocol is up Hardware is GT96k FE, address is 0004.282b.2484 (bia 0004.282b.2484) Internet address is 10.0.0.1/24 MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 100Mb/s, 100BaseTX/FX ARP type: ARPA, ARP Timeout 04:00:00 Last input 2d07h, output 00:00:06, output hang never Last clearing of "show interface" counters 00:00:37




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 Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog 0 input packets with dribble condition detected 0 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out

Enter the show controller FastEthernet bay/port command to show controller specific information about the interface. For the fast ethernet port on the management back card this includes information such as error statistics and register settings.

Router# show controller FastEthernet 2/0Interface FastEthernet2/0Hardware is GT96100A FE

IDB Ptr = 0x41F27050, Instance Ptr = 0x42CA4B28GT96100A register pointer = 0x15000000FE register pointer = 0x15088800PHY register pointer = 0x15080800

GT96100A Registers: GPIO 2 Config register = 0xFF7FFF7F (b/s 0x7FFF7FFF) GPIO IO register = 0x3D003D00 (b/s 0x003D003D) CIU Aributer register = 0xFF030080 (b/s 0x800003FF) PHY Address register = 0x01000000 (b/s 0x00000001) PHY Data register = 0x8047200E (b/s 0x0E204780) Serial Interrupt 0 Mask register = 0xF00F0000 (b/s 0x00000FF0) Serial Interrupt 1 Mask register = 0xF00F0000 (b/s 0x00000003) Serial Cause register = 0x00000000 (b/s 0x00000000)

FE Registers: Port Configuration Register = 0x80000000 (b/s 0x00000080) EN HS(8K) HM(0) Port Configuration Extend register = 0x00DC0100 (b/s 0x0001DC00) PRIOTX=1:1 PRIORX=(00) ~FCTLen ~FLP ~FCTL MFL=64KB MIBclrMode Speed=Auto Port Command register = 0x00000000 (b/s 0x00000000) Port Status Register = 0x0F000000 (b/s 0x0000000F) Speed=100MB Duplex=FD Fctl=DIS Link=UP ~Paused ~TXinProg Serial Parameter register = 0x23882100 (b/s 0x00218823) Hash table pointer register = 0x003D301F (b/s 0x1F303D00) Source Address Low register = 0xF2410000 (b/s 0x000041F2) Source Address High register = 0x00010000 (b/s 0x00000100) SDMA Configuration register = 0x00220000 (b/s 0x00002200) RC=0 BLMR=BE BLMT=BE RIFB BSZ=4 SDMA Command register = 0x80000300 (b/s 0x00030080) STDL STDH ERD Interrupt Mask register = 0xCD3D0080 (b/s 0x80003DCD) Interrupt Cause register = 0x00000000 (b/s 0x00000000) IP Diff Services to Priority 0 Low register = 0x00000000 (b/s 0x00000000) IP Diff Services to Priority 0 High register = 0x00000000 (b/s 0x00000000) IP Diff Services to Priority 1 Low register = 0x00000000 (b/s 0x00000000) IP Diff Services to Priority 1 High register = 0x00000000 (b/s 0x00000000) IP VLAN Tag Priority = 0xCCF00000 (b/s 0x0000F0CC) First Rx Descriptor Pointer Ring 0 register = 0xA03D341F (b/s 0x1F343DA0)




Current Rx Descriptor Pointer Ring 0 register = 0xA03D341F (b/s 0x1F343DA0) First Rx Descriptor Pointer Ring 1 register = 0x8041341F (b/s 0x1F344180) Current Rx Descriptor Pointer Ring 1 register = 0x8041341F (b/s 0x1F344180) First Rx Descriptor Pointer Ring 2 register = 0xC045341F (b/s 0x1F3445C0) Current Rx Descriptor Pointer Ring 2 register = 0xC045341F (b/s 0x1F3445C0) First Rx Descriptor Pointer Ring 3 register = 0x004A341F (b/s 0x1F344A00) Current Rx Descriptor Pointer Ring 3 register = 0x004A341F (b/s 0x1F344A00) First Tx Descriptor Pointer Ring 0 register = 0x204F341F (b/s 0x1F344F20) First Tx Descriptor Pointer Ring 1 register = 0x8056341F (b/s 0x1F345680)

PHY Registers: Register 0x00: 1000 782D 0013 78E2 01E1 41E1 0007 2001 Register 0x08: 0000 0000 0000 0000 0000 0000 0000 0000 Register 0x10: 0084 4780 0000 00F4 2040 0000 0000 0000 Register 0x18: 0000 0000 00C8 0000 0000 0000 0000

Hardware MAC address filter (hash: addr) 0x112D: 0004.282b.2484 0x1899: 0100.0ccc.cccc 0x7FFF: ffff.ffff.ffff

Software MAC address filter (hash: length/addr/mask/hits): 0x00: 0 ffff.ffff.ffff 0000.0000.0000 0 0xAC: 0 0004.282b.2484 0000.0000.0000 0 0xC0: 0 0100.0ccc.cccc 0000.0000.0000 0

Transmit Descriptor Information: Tx ring size = 128 Tx ring 0 ptr = 0x1F344E40, Tx ring 1 ptr = 0x1F345680 Malloc Tx ring 0 ptr = 0x1F344E40, Malloc Tx ring 1 ptr = 0x1F345680 Shadow Tx ring 0 ptr = 0x41F28468, Shadow Tx ring 1 ptr = 0x42CB71C0 Head Tx ring 0 = 0xE, Head Tx ring 1 = 0x0 Tail Tx ring 0 = 0xE, Tail Tx ring 1 = 0x0 Tail Count Tx ring 0 = 0x0, Tail Count Tx ring 1 = 0x0

Receive Descriptor Information: Rx ring size = 64 Rx ring 0 ptr = 0x1F343D40, Rx ring 1 ptr = 0x1F344180 Rx ring 2 ptr = 0x1F3445C0, Rx ring 3 ptr = 0x1F344A00 Malloc Rx ring 0 ptr = 0x1F343D40, Malloc Rx ring 1 ptr = 0x1F344180 Malloc Rx ring 2 ptr = 0x1F3445C0, Malloc Rx ring 3 ptr = 0x1F344A00 Shadow Rx ring 0 ptr = 0x41F2833C, Shadow Rx ring 1 ptr = 0x42CA52E8 Shadow Rx ring 2 ptr = 0x42CA5414, Shadow Rx ring 3 ptr = 0x42CA5540 Head Rx ring 0 = 0x6, Head Rx ring 1 = 0x0 Head Rx ring 2 = 0x0, Head Rx ring 3 = 0x0 Tail Rx ring 0 = 0x0, Tail Rx ring 1 = 0x0 Tail Rx ring 2 = 0x0, Tail Rx ring 3 = 0x0

MIB Counters: Filtered packets = 0, Number of Throttles = 0

Rx framing errors = 0, Rx overflow errors = 0 Rx buffer errors = 0, Rx end of packet errors = 0 Rx soft overflow errors ring 0 = 0 Rx soft overflow errors ring 1 = 0 Rx soft overflow errors ring 2 = 0 Rx soft overflow errors ring 3 = 0 Rx miss count = 0

Tx single collision errors = 0, Tx multiple collision errors = 0 Tx end of packet errors = 0, Tx deferred errors = 0 Tx underrun errors = 0, Tx late collision errors = 0 Tx carrier loss errors = 0, Tx excessive collision errors = 0 Tx buffer errors = 0, Tx fatal errors = 0

Spurious SMI Interrupts = 0



Chapter 4 Installing and Configuring the MGX-XF-UI Management Back CardTroubleshooting the Installation

Troubleshooting the InstallationRefer to Table 4-7 for descriptions of the LEDs on the management back card. Follow the instructions in Table 4-8 on the next page to troubleshoot the installation.

Table 4-7 MGX-XF-UI Back Card LED Status and Definitions

LED Status Description

STATUS Green Back card is operating properly.

Off Back card is not detected or a major failure has disabled the card.

Table 4-8 Management Back Card Installation Troubleshooting

Symptom Possible Cause Corrective Action

The Status LED does not light during the power-on self-test

The back card is not properly seated.

Be sure the ejector levers are fully closed and that the captive screws have been tightened.

Bad back card slot or midplane connector.

Remove the back cards (upper and lower slots) and the front card and install them into another chassis slot.

The console or auxiliary port do not work.

Configuration incorrect. Check the configuration to make sure the baud rate and other settings are correct.

Bad cable. Replace the cable.



Bad back card. Replace the back card.

Bad front card. Replace the front card.

The fast ethernet port(s) does not work.

Configuration incorrect. Check the configuration to make sure the speed and duplex settings match the remote end. Also try forcing the speed and duplex settings (turn off auto negotiation).

Bad cable. Replace the cable.







Chapter 4 Installing and Configuring the MGX-XF-UI Management Back CardTroubleshooting the Installation

C H A P T E R



5Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards

This chapter describes how to install and configure the single-port MGX-1OC12POS (Packet Over SONET) back card and the dual-port MGX-2OC12POS back card on a Cisco RPM-XF.

This chapter includes the following sections:

• MGX-1OC12POS-IR Overview and Features

• MGX-2OC12POS Overview and Features

• Installation Guidelines

• Software Configuration

• Troubleshooting the Installation

MGX-1OC12POS-IR Overview and FeaturesThe MGX-1OC12POS-IR back card (Figure 5-1) is fully compatible with standards-based POS implementations on platforms such as the Cisco 7200, the Cisco 7500, the Cisco 10000 edge services router (ESR), and the Cisco 12000 series gigabit switch router (GSR).



Chapter 5 Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back CardsMGX-1OC12POS-IR Overview and Features

Figure 5-1 MGX-1OC12POS-IR Back Card

The MGX-1OC12POS-IR back card (see Figure 5-1) provides a trunk uplink that supports OC-12c/STM-4c bandwidth of 622 Mbps throughput over a standard SONET/SDH interface using a single-mode fiber, intermediate-reach SC connector (see Table 5-2).

Table 5-1 MGX MGX-1OC12POS-IR Front Panel LED and Port Descriptions

LED Description

1 LINK LED Green—A link has been established. Off—A link has not been established.

2 TX and RX LEDs Green—The back card is receiving or transmitting traffic. Off—The back card is not receiving or transmitting traffic.

3 FAIL LED Yellow—The back card has failed. Off—The back card is operating properly.

4 TX and RX Ports SC connectors

8074

8

FAIL

LINK TX

TX

RX

RX

MGX-1OC 12POS-IR

4

23

1



Chapter 5 Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back CardsMGX-1OC12POS-IR Overview and Features

The MGX-1OC12POS-IR back card provides the following key features:

• Efficient, high-performance bandwidth utilization—OC-12 performance of 622 Mbps provides the bandwidth required to meet the most demanding user requirements, such as faster access to web pages, real-time video, large file transfers, and other data-intensive applications.

The Cisco POS implementation offers a 25 to 30 percent gain in efficiency over multiservice IP traffic now running over ATM networks. It achieves this efficiency gain by eliminating the overhead required in ATM implementations, such as ATM cell header, IP over ATM encapsulation, and segmentation and reassembly (SAR).

• Optimized for IP-based differentiated services—The Cisco POS solution supports Internet-based multiservice networks based on IP. The Cisco POS implementation places the IP layer directly above the SONET layer and eliminates the overhead required to run IP over ATM over SONET.

• Configurable clock sources—The MGX-1OC12POS-IR back card is capable of providing the clock source for the POS link and also retrieving the clock source from network.

• Configurable loopbacks for troubleshooting—The MGX-1OC12POS-IR back card is capable of configuring both an internal loopback (loops outbound traffic back towards the front card) and a network loopback (loops inbound traffic back towards the network).

• Alarm processing—The MGX-1OC12POS-IR back card implements SONET alarms that are fully Bellcore GR-253 compliant.

Table 5-2 MGX-1OC12POS-IR Cable Specifications

Fiber Type Wavelength (nm) Core Size (microns) Cable Distance

Single-mode fiber 1300 8 to 10 49,213 ft (15 km)



Chapter 5 Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back CardsMGX-2OC12POS Overview and Features

MGX-2OC12POS Overview and FeaturesThe MGX-2OC12POS back card (Figure 5-2) is fully compatible with standards-based POS implementations on platforms such as the Cisco 7200, the Cisco 7500, the Cisco 10000 edge services router (ESR), and the Cisco 12000 series gigabit switch router (GSR).

Figure 5-2 MGX-2OC12POS Back Card

Table 5-3 MGX MGX-2OC12POS Front Panel LED and Port Descriptions

LED Description




4 TX and RX Ports SC connectors.

5 TX and RX Ports SC connectors.

1010

92

FAIL

LINK TX

TX

RX

RX

4

TX

RX

5

23

1

MGX- 2OC12POS



Chapter 5 Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back CardsMGX-2OC12POS Overview and Features

The MGX-2OC12POS back card (see Figure 5-2) provides two trunk uplinks. Each trunk supports an OC-12c/STM-4c bandwidth of 622 Mbps throughput. Each port provides a standard SONET/SDH interface using a single-mode fiber, intermediate-reach SC connector (see Table 5-3).

The MGX-2OC12POS back card provides the following key features:

• Efficient, high-performance bandwidth utilization—OC-12 performance of 622 Mbps provides the bandwidth required to meet the most demanding user requirements, such as faster access to web pages, real-time video, large file transfers, and other data-intensive applications.

The Cisco POS implementation offers a 25 to 30 percent gain in efficiency over multiservice IP traffic now running over ATM networks. It achieves this efficiency gain by eliminating the overhead required in ATM implementations, such as ATM cell header, IP over ATM encapsulation, and segmentation and reassembly (SAR).

• Optimized for IP-based differentiated services—The Cisco POS solution supports Internet-based multiservice networks based on IP. The Cisco POS implementation places the IP layer directly above the SONET layer and eliminates the overhead required to run IP over ATM over SONET.

• Configurable clock sources—The MGX-2OC12POS back card is capable of providing the clock source for the POS link and also retrieving the clock source from network.

• Configurable loopbacks for troubleshooting—The MGX-2OC12POS back card is capable of configuring both an internal loopback (loops outbound traffic back towards the front card) and a network loopback (loops inbound traffic back towards the network).

• Alarm processing—The MGX-2OC12POS back card implements SONET alarms that are fully Bellcore GR-253 compliant.

• SFP (Small Form Factor Pluggable) Hot Swapping and Security—The MGX-2OC12POS back card is hot swappable and can be removed and replaced even when the interfaces are NOT shutdown.

• Card OIR (Online Insertion & Removal) support—There is online support for the insertion and removal of the MGX-2OC12POS back card.

The MGX-2OC12POS back card uses the MGX-2GE driver, which performs the following tasks:

• Initializing the POS driver subsystem at IOS boot time

• Initializing and configuring the the GE backcard

• Downloading the POS backcard firmware images

• Collecting statistics for the CLI and SNMP

• Managing alarm and trap events after insertion, removal, and hot swap

• Managing interface status and configuration changes

• Processing events and alarms

• Monitoring data path hardware failures

• Controlling front card and backcard port and card status LEDs

Table 5-4 MGX-2OC12POS Cable Specifications

Fiber Type Wavelength (nm) Core Size (microns) Cable Distance

Single-mode fiber 1300 8 to 10 49,213 ft (15 km)



Chapter 5 Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back CardsInstallation Guidelines

Installation GuidelinesThis section contains guidelines for the following procedures:



The Cisco MGX-1OC12POS-IR back cards are cold swappable, which means that you can remove and replace the back cards only when all the interfaces on are shutdown.

The Cisco MGX-2OC12POS back cards are hot swappable, which means that you can remove and replace the back cards even when the interfaces are not shutdown.

Caution To prevent electrostatic discharge (ESD) damage, handle back cards by the faceplate or the card carrier edges only. Avoid touching the back card printed circuit board, components, or any connector pins.

New Installation GuidelinesFor information on installing the back card hardware, see Chapter 3, “Installing the MGX RPM-XF Front and Back Cards.”

After installing the MGX-1OC12POS-IR or the MGX-2OC12POS for the first time, you must configure it by entering the configure command. For information about configuring the MGX-1OC12POS-IR and MGX-2OC12POS back cards, see the “Software Configuration” section below.

Replacement Installation GuidelinesFor information on removing and installing the back card hardware, see Chapter 3, “Installing the MGX RPM-XF Front and Back Cards.”

If an MGX-1OC12POS-IR or an MGX-2OC12POS back card is replaced, the system automatically downloads the necessary information from the RPM-XF front card. There is no need to configure the new back card, unless the front card has been reloaded or switched over subsequent to the removal of the back card of the same type. After the information is downloaded, the system recognizes only those interfaces that match the previous MGX-1OC12POS-IR or MGX-2OC12POS back card configuration (those configured as Up).

Software ConfigurationAfter the MGX-1OC12POS-IR or MGX-2OC12POS back card is successfully installed, you can configure the card for network use.

Note You do not need to configure the MGX-1OC12POS-IR or MGX-2OC12POS back card if this is a replacement installation. The system automatically downloads the necessary configuration information from the RPM-XF front card.


• MGX-1OC12POS-IR and MGX-2OC12POS Back Card Default Values



Chapter 5 Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back CardsSoftware Configuration

• MGX-1OC12POS-IR Back Card Syntax

• MGX-2 OC12POS Back Card Syntax

• Configuring the Interface

• Customizing the MGX-1OC12POS-IR or MGX-2OC12POS

• Example Configuration

• Using show Commands to Check System Status

MGX-1OC12POS-IR and MGX-2OC12POS Back Card Default ValuesTable 5-5 lists default values for the MGX-1OC12POS-IR and MGX-2OC12POS back cards. The commands marked with an asterisk (*) are described in the Cisco IOS command reference documentation. The other commands are among those described in this chapter.

The table includes the command used for modifying a default value and indicates whether a value needs to be the same (or opposite) on the remote end of the connection.

MGX-1OC12POS-IR Back Card SyntaxTo specify an interface number in a configuration command, use the syntax in Table 5-6 to identify interfaces on the MGX-1OC12POS-IR back card.

Table 5-5 MGX-1OC12POS-IR and MGX-2OC12POS Back Card Defaults

Command NameDefault Setting Command Syntax Remote Side Setting

bandwidth* 622000 bandwidth kilobits Same.

clock source line clock source [line | internal] At least one side must be set to internal.

crc* 32 crc [16 | 32] Same.

encapsulation* HDLC encapsulation [hdlc | ppp] Same.

keepalive* 10 second keepalive

[no] keepalive period Same.

mtu*1

1. mtu=maximum transmission unit

4470 mtu size Same.

pos framing SONET pos framing [sonet | sdh] Same.

pos scramble-atm No scrambling [no] pos scramble-atm Same.

pos flag2(

2. SONET overhead

c2—0xcfj0—0x01s1s0—0x00

pos flag [c2 | j0 | s1s0] value Same.




The following example shows the syntax for configuring an MGX-1OC12POS-IR back card.

Router(config)# interface pos 1/0

MGX-2 OC12POS Back Card SyntaxTo specify an interface number in a configuration command, use the syntax in Table 5-7 to identify interfaces on the MGX-2OC12POS back card.

The following example shows the syntax for configuring an MGX-2OC12POS back card.

Router(config)# interface pos 1/0Router(config)# interface pos 1/1

Configuring the InterfaceAfter you verify that the MGX-1OC12POS-IR or MGX-2OC12POS back card is installed correctly, use the following procedure to configure the new interface. Be prepared with the information you will need, such as the interface IP address.

The following procedure is for creating a basic configuration—Enabling an interface.

Step 1 At the global configuration prompt, specify the new interface to configure by entering the interface pos <bay/port> command and interface address. For example,

Router(config)# interface pos 1/0

Step 2 Assign an IP address and a subnet mask to the interface with the ip address configuration subcommand, as in the following example.


Step 3 Specify either HDLC or PPP encapsulation. For example,

Router(config-if)# encapsulation hdlc

Step 4 If necessary, modify the MGX-1OC12POS-IR or MGX-2OC12POS back card configuration or that of the remote device to ensure that, where appropriate, they use the same settings. For more information, see the “Remote Side Setting” column in Table 5-5 or Table 5-7.

Step 5 Add any other configuration subcommands required for the enabling of routing protocols and adjust the interface characteristics.

Step 6 Enter the no shutdown command to enable the interface.

Table 5-6 MGX-1OC12POS-IR Interface Syntax

Type of Interface Bay/ (always 1) Port

POS interface 1/ 0

Table 5-7 MGX-2OC12POS Interface Syntax

Type of Interface Bay/ (always 1) Port

POS interface 1/ 0 or 1








The system displays an OK message when the configuration is stored.

After you complete your configuration, check it by entering the show interface pos <bay/port> command.

Customizing the MGX-1OC12POS-IR or MGX-2OC12POSThe following sections present some of the commands that you can use to customize your MGX-1OC12POS-IR or MGX-2OC12POS back card configuration.


• Setting the Clock Source

• Configuring Framing

• Specifying SONET Overhead

• Configuring POS SPE Scrambling

• Configuring Loopback Testing

Setting the Clock Source

At the prompt, set the internal or line clock source by entering the clock source command.

clock source [internal | line]

The default is clock source line.

In this example, the back card is instructed to use a line clock source.

Router(config)# interface pos 1/0Router(config-if)# clock source line

Configuring Framing

You can use the pos framing command to set framing to SONET STS-3c or SDH STM-1 framing.

pos framing [sdh | sonet][no] pos framing

The default is SONET.

Parameter Description

internal Specifies that the internal clock source is used.

line Specifies that the network clock source is used.




Make sure your system supports SDH before using this option.

Use the no form of the command to restore the default framing mode.

In the following example, the framing type is set to SONET.

Router(config)# interface pos 1/0Router(config-if)# no pos framing

Specifying SONET Overhead

You can use the pos flag command to assign values for specific elements of the frame header. This command is typically used to meet a standards requirement or to ensure interoperability with another vendor's equipment.

pos flag [ c2 | j0 | s1s0 value][no] pos flag [ c2 | j0 | s1s0 value]

The default values are c2–0xCF, j0–0x01, and s1s0–0.

Use the no form of the command to restore the default values.

In the following example, the c2 bit is set to 0xCF.

Router(config)# interface pos 1/0Router(config-if)# pos flag c2 0xCF

Configuring POS SPE Scrambling

The pos scramble-atm command allows you to scramble the POS synchronous payload envelope (SPE). SONET payload scrambling applies a self-synchronous scrambler to the SPE of the interface to ensure sufficient bit transition density.

pos scramble-atm[no] pos scramble-atm

The default is no POS SPE scrambling.

Use the no form of the command to disable scrambling.

In the following example, scrambling is enabled:

Router(config)# interface pos 1/0Router(config-if)# pos scramble-atm


c2 Specifies a path signal identifier, and value is one of the following:

• 0xCF for PPP or HDLC without scrambling

• 0x16 for PPP or HDLC with scrambling

j0 Specifies the section trace byte, and value is 0x1 for interoperability with some SDH devices in Japan.

s1s0 Designates part of the payload pointer byte, and value is one of the following:

• 0 for OC-3c

• 2 for AU-4




Configuring Loopback Testing

To enable loopback testing of data transmitted from the front card to the MGX-1OC12POS-IR or MGX-2OC12POS back card and back, use the loopback command in interface configuration mode.

loopback [line | internal][no] loopback [line | internal]

Use the no form of the command to stop the loopback test.

In the following example, a loopback is set for the MGX-1OC12POS-IR or MGX-2OC12POS back card:

Router(config)# interface pos 1/0Router(config-if)# loopback line

Example ConfigurationThe following is an example of configuration file commands for a Cisco RPM-XF with an MGX-1OC12POS-IR or MGX-2OC12POS back card (Router 1) connected back-to-back with a Cisco 12000 series router with an OC-12c/STM-4c Layer 3 POS back card in slot 3 (Router 2).

Router 1:

interface pos 1/0ip address 10.1.2.4 255.0.0.0clock source lineno shutdownno keepaliveno cdp enablecrc 32Router 2:

interface pos 3/0ip address 10.1.2.3 255.0.0.0clock source internalno shutdownno keepaliveno cdp enable


line Loops any inbound traffic received at the MGX-1OC12POS-IR or MGX-2OC12POS back card’s network interface back into the network.

Note Even though the inbound traffic is looped back towards the network, the inbound traffic continues to flow into the front card. Outbound traffic (from the front card) is silently dropped by the back card’s network interface.

internal Loops any outbound traffic received at the MGX-1OC12POS-IR or MGX-2OC12POS back card’s network interface back into the front card.

Note Even though the outbound traffic is looped back towards the front card, the outbound traffic continues to flow towards the network. Inbound traffic (from the network) is silently dropped by the back card’s network interface.




no ip mroute-cachecrc 32

Using show Commands to Check System StatusEach back card maintains information about its configuration, traffic, errors and so on. You can access this information by entering the show commands. Following are descriptions and examples of show commands that display back card information and status.

Enter the show interface pos <bay/port> command to show general information about the interface, as shown in the following example.

Router# show interface pos 1/0POS1/0 is up, line protocol is up Hardware is Skystone 4302 Sonet Framer Internet address is 1.1.100.2/24 MTU 4470 bytes, BW 622000 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, crc 32, loopback not set Keepalive set (10 sec) Scramble disabled Last input 00:00:02, output 00:00:07, output hang never Last clearing of "show interface" counters 00:00:16 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 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 0 carrier transitions

Use the show controller pos <bay/port > command to show controller-specific information about the interface, as shown in the following example. For the MGX-1OC12POS-IR or MGX-2OC12POS back card, this includes information such as, which SONET alarms are currently active, the SONET information received from the remote end, and the SONET configuration parameters.

Router# show controller pos 1/0

POS1/0SECTION LOF = 0 LOS = 0 BIP(B1) = 0LINE AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0PATH AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0

Active Defects: NoneActive Alarms: NoneAlarm reporting enabled for: SF SD SLOS SLOF B1-TCA LAIS LRDI B2-TCA PAIS PLOP PRDI PUNEQ B3-TCA

Framing: SONETOVERHEAD BYTES S1/S0 = 0, C2 = CFCLOCK RECOVERY



Chapter 5 Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back CardsTroubleshooting the Installation

RDOOL = 0 State: RDOOL_state = FalsePATH TRACE BUFFER: STABLE Remote hostname : Router Remote interface: POS1/0 Remote IP addr : 0.0.0.0 Remote Rx(K1/K2): B1/32 Tx(K1/K2): 08/00

BER thresholds: SF = 10e-3 SD = 10e-6TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6

Clock source: internal

Troubleshooting the InstallationRefer to Table 5-8 for descriptions of the LEDs on the MGX-1OC12POS-IR or MGX-2OC12POS back card. Follow the instructions in Table 5-9 to troubleshoot the installation.

Table 5-8 MGX-1OC12POS-IR or MGX-2OC12POS Back Card LED Status and Definitions


LINK Green Carrier detected.

Off Carrier not detected.

TX (transmit) Green Transmitting traffic.

Off Not transmitting traffic.

RX (receive) Green Receiving traffic.

Off Not receiving traffic.

FAIL Yellow Major failure has disabled the back card.

Off Back card is operating properly

Table 5-9 MGX-1OC12POS-IR or MGX-2OC12POS Installation Troubleshooting


The back card fail LED does not light during the power-on self-test.





Back card initialization fails.







Chapter 5 Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back CardsTroubleshooting the Installation

The interface does not come up or constantly comes up and then goes down.

Configuration mismatched.

Check the configuration on both sides. (Refer to the “Software Configuration” section on page 5-6 for more information.)

Cables connected incorrectly.

Check the cabling on both sides. Ensure the receive is connected to the transmit on the remote end and vice versa.

Bad cables. Replace the cables. Ensure your cabling meets the specifications in Table 5-2 on page 5-3.

Table 5-9 MGX-1OC12POS-IR or MGX-2OC12POS Installation Troubleshooting (continued)


C H A P T E R



6Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards

This chapter describes how to install and configure the single-port Gigabit Ethernet (MGX-1GE) back card and the dual-port Gigabit Ethernet (MGX-2GE) back card.

This chapter includes the following sections:

• MGX-1GE Features and Specifications

– MXG-1GE SFP Specifications

– MGX-1GE Installation Guidelines

– MGX-1GE Software Configuration Guidelines

– MGX-1GE System Status Check

• MGX-2GE Features and Specifications

– MXG-2GE SFP Specifications

– MGX-2GE Installation Guidelines

– MGX-2GE Software Configuration Guidelines

– MGX-2GE System Status Check

• MGX-1GE and MGX-2GE Installation Troubleshooting



Chapter 6 Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back CardsMGX-1GE Features and Specifications

MGX-1GE Features and SpecificationsThe single-port MGX-1GE back card provides a gigabit ethernet trunk uplink to devices (see Figure 6-1).

Figure 6-1 MGX-1GE Back Card

The MGX-1GE back card provides an IEEE 802.3z compliant Gigabit Ethernet interface that runs at 1 Gbps in full duplex mode.

Table 6-1 MGX 1GE Front Panel LED and Port Descriptions

LED Description




4 TX and RX Ports RJ-45 Ethernet cable connectors

8074

7

FAIL

LINK TX

TX

RX

RX

MGX-1GE

4

23

1




The MGX-1GE back card provides the following key features:

• Efficient, high-performance Gigabit Ethernet bandwidth.

• Optimized Gigabit Ethernet IP-based multiservice network services.

• Auto negotiation.

• Flow control.

• 802.1q encapsulation support for VLANs.

• Configurable loopbacks for troubleshooting.

The MGX-1GE uses a Small Form-factor Pluggable (SFP) module that supports Gigabit Ethernet rates on a variety of Gigabit Ethernet interface types (SX, LH/LX, ZX), which you can change or upgrade at any time (see Table 6-2).

MXG-1GE SFP SpecificationsTable 6-2 lists the GE back card SFPs and their respective cable types and lengths.

The MGX-1GE back card shown in Figure 6-1 provides a trunk uplink that supports 1 Gbps throughput using multi-mode or single-mode fiber, depending the connector type.

MGX-1GE Installation GuidelinesThis section contains guidelines for the following procedures:



The MGX-1GE back cards are cold swappable, which means you can remove and replace the back cards only when the interface on the back cards is in the shutdown state.


Table 6-2 MGX-1GE Cable Specifications

SFP

62.5/125 um Multimode850 nmCable

50/125 um Multimode850 nmCable


50/125 um Multimode1310 nm Cable

9/125 um Singlemode1310 nm Cable

1000Base SX 220 M@ 160 MHz-km

275 M@ 200 MHz-km

500 M@ 400 MHz-km

550 M@ 500 MHz-km

— — —

1000Base LH/LX

— — 550 M @ 500 MHz-km

550 M@ 400 MHz-km

10 km

1000Base ZX — — — — 70 km




MGX-1GE First Time Installation

For information on installing the back card hardware, see Chapter 3, “Installing the MGX RPM-XF Front and Back Cards.”

After installing the MGX-1GE back card hardware for the first time, you must configure it entering the configure command. For information about configuring the MGX-1GE back card, see the “MGX-1GE Software Configuration Guidelines” section below.

MGX-1GE Replacement Installation

For information on removing and installing the back card hardware, see Chapter 3, “Installing the MGX RPM-XF Front and Back Cards.”

If an MGX-1GE back card is replaced, the system automatically downloads the necessary configuration information from the RPM-XF front card; there is no need to configure the new back card unless the front card has been reloaded or switched over subsequent to removal of a back card of the same type. After the information is downloaded, the system recognizes only those interfaces that match the previous MGX-1GE back card configuration (those configured as Up).

MGX-1GE Software Configuration GuidelinesAfter the MGX-1GE back card is successfully installed, you can configure the card for network use.

Note You do not need to configure the MGX-1GE back card if this is a replacement installation in the same chassis slot. The system automatically downloads the necessary configuration information from the RPM-XF front card.


• MGX-1GE Back Card Default Values

• MGX-1GE Back Card Syntax

• MGX-1GE Interface Configuration

• MGX-1GE Customization

• MGX-1GE Example Configuration

• MGX-1GE System Status Check


MGX-1GE Back Card Default Values

Table 6-3 lists default values for the MGX-1GE back card. The commands marked with an asterisk (*) are described in the Cisco IOS command reference documentation. The other commands are among those described in this chapter.





MGX-1GE Back Card Syntax

To specify an interface number in a configuration command, use the syntax in Table 6-4 to identify interfaces on the MGX-1GE back card.

The following example shows the syntax for configuring the Gigabit Ethernet interface on the MGX-1GE back card:

Router(config)# interface gigabitethernet 1/0Router(config-if)#

Note The subinterface configuration is to be used only for configuring 802.1q encapsulation for VLAN support.

The following example shows the syntax for configuring the Gigabit Ethernet subinterface on the MGX-1GE back card:

Router(config)# interface gigabitethernet 1/0.2Router(config-subif)#

MGX-1GE Interface Configuration

After you verify that the MGX-1GE back card is installed correctly, use the following procedure to configure the new interface. Be prepared with the information you will need, such as the interface IP address.

The following procedure is for creating a basic configuration—enabling an interface.

Step 1 At the global configuration prompt, specify the new interface to configure by entering the interface gigabitethernet <bay/port> command and interface address. For example,

Router(config)# interface gigabitethernet 1/0

Step 2 Assign an IP address and a subnet mask to the interface with the ip address configuration subcommand, as in the following example:

Table 6-3 MGX-1GE Back Card Defaults





mtu1*

1. mtu=(maximum transmission unit)

1500 mtu size Same.

negotiation auto [enabled] [no] negotiation auto Same.

Table 6-4 MGX-1GE Interface Syntax

Type of Interface Bay/ (always 1) Port (always 0) .Subinterface (optional)

GE interface 1/ 0 1–1000





Step 3 If necessary, modify the MGX-1GE back card configuration or that of the remote device to ensure that, where appropriate, they use the same settings. For more information, see the “Remote Side Setting” column in Table 6-3.








After you have completed your configuration, you can check it using the show interface gigabitethernet <bay/port>.

MGX-1GE Customization

The following sections present some of the commands that you can use to customize your MGX-1GE back card configuration.


• MGX-1GE Auto Negotiation

• MGX-1GE Loopback Testing

• MGX-1GE 802.1q VLAN Encapsulation

MGX-1GE Auto Negotiation

The negotiation auto command allows you to enable or disable auto negotiation on the Gigabit Ethernet interface. Flow control is the only parameter that is negotiated as the interface is always full duplex with a 1 Gbps speed.

negotiation auto[no] negotiation auto

The default is negotiation auto.

Use the no form of the command to disable auto negotiation.

In the following example, auto negotiation is enabled:

Router(config)# interface gigabitethernet 1/0Router(config-if)# negotiation auto

MGX-1GE Loopback Testing

To enable loopback testing of data transmitted from the front card to the MGX-1GE back card and back, use the loopback command in interface configuration mode.




loopback [ mac | driver ][no] loopback [ mac | driver ]


In the following example, a loopback is set for the MGX-1GE back card:

Router(config)# interface gigabitethernet 1/0Router(config-if)# loopback mac

Note Loopback tests disrupt user traffic on production networks

MGX-1GE 802.1q VLAN Encapsulation

To define the VLAN encapsulation format as IEEE 802.1Q, use the following commands in interface configuration mode to specify the subinterface the VLAN will use and to define the encapsulation format as IEEE 802.1Q (dot1q), and specify the VLAN identifier:

Router(config)#interface gigabitethernet <bay/port.subinterface>Router(config-subif)#encapsulation dot1q <vlan-identifier>

Example:

Router(config)#interface gigabitethernet 1/0.2Router(config-subif)#encapsulation dot1q 2Router(config-subif)#ip address 10.1.1.1 255.255.255.0

For more information, refer to the Cisco IOS documentation at

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/8021q.htm

MGX-1GE Example Configuration

The following is an example of configuration file commands for a Cisco RPM-XF with an MGX-1GE back card (Router 1) connected back-to-back with a Cisco 7200 series router with a gigabit ethernet line card in slot 3 (Router 2).

Router 1:

interface gigabitethernet 1/0ip address 10.1.2.4 255.0.0.0no shutdownno keepaliveno cdp enable

Router 2:

interface gigabitethernet 3/0ip address 10.1.2.3 255.0.0.0


driver or external1 Loops any outbound traffic from the front card back to the front card at the SERDES. This test must be performed with an external loopback cable on the interface to clear the alarm.

mac or internal1 Loops any outbound traffic received at the MGX-1GE back card’s network interface back into the front card at the MAC controller.

1. Depending on software release version.




no shutdownno keepaliveno cdp enableno ip mroute-cache

MGX-1GE System Status CheckEach back card maintains information about its configuration, traffic, errors and so on. You can access this information by using the show commands. Following are descriptions and examples of show commands that display back card information and status.

Enter the show interface gigabitethernet <bay/port> command to show general information about the interface, as shown in the following example.

GE-Slot-2#show interface gigabitethernet 1/0GigabitEthernet1/0 is up, line protocol is up Hardware is Gigabit Ethernet MAC Controller, address is 0050.54ad.5a22 (bia 0050.54ad.5a22) Internet address is 3.3.3.3/24 MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex mode, link type is autonegotiation, media type is SX output flow-control is off, input flow-control is off ARP type:ARPA, ARP Timeout 04:00:00 Last input never, output 00:00:05, output hang never Last clearing of "show interface" counters 2d00h Input queue:0/75/3/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, 3 runts, 0 giants, 0 throttles 3 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 0 multicast, 0 pause input 0 input packets with dribble condition detected 21691 packets output, 2597423 bytes, 0 underruns 0 output errors, 0 collisions, 3 interface resets 0 babbles, 0 late collision, 0 deferred 3 lost carrier, 0 no carrier, 0 pause output 0 output buffer failures, 0 output buffers swapped out

Enter the show controller gigabitethernet <bay/port > command to show controller-specific information about the interface, as shown in the following example.

GE-Slot-2#show controller gigabitethernet 1/0Interface GigabitEthernet1/0(idb 0x43B978A0)Hardware is Gigabit Ethernet MAC Controller, Slot Index 1

Network Connection Mode is autonegotiate state:RPMXF_GE_COMPLETE_NEGOTIATE

the other end auto-negotiate mode is auto port monitoring status = 0x0

network link is up, loopback type is none SFP type is 1000BASE-SX ip_routecache=0x11(dfs=0/mdfs=0), max_mtu=1524 rpmxf_ge_ds=0x442E2C80




resets=3, reset_init=1, reset_restart=3 link_state_reason=5

GE Backcard Registers Card Interrupt Status 00000000 Card Interrupt Mask 00000000 Card ASIC Reset 00000000 Card Discrete Input 01000010 Card Discrete Output 000000B1 Card Local Bus Timeout 0000FFFF Card Local Bus Timeout Address 00000000 Card PCI SERR Address 00000000 Card PCI PERR Address 00000000 Card PCI Bus Idle Stats FB52A437 Card PCI Bus Transfer Stats 0703854C Card Wrap Test 00000000 Card Debug Header Control 00000000

Barium Registers ID 00136049 Configuration 00000008 Reset PCI Bus A Reset PCI Bus B Reset PCI Bus C PCI Bus A Status 00008280 PCI Bus B Status 00000280 PCI Bus C Status 00000280 Global IronBus Cfg1 540070A0 Global IronBus Cfg2 054C6086 Global IronBus Sts1 0000F11C Global IronBus Sts2 0000F11C DMA Reset 00000000 Interrupt Status 00004000 Interrupt Mask 4000801F Iron Bus 0 Status 1 00000000 Iron Bus 0 Status 2 00000000 Iron Bus 0 Status 3 00000000 Iron Bus 1 Status 1 0FFFFF0F Iron Bus 1 Status 2 0000FFFF Iron Bus 1 Status 3 000CFFFF TIB0 DMA Desc Base 00000000 TIB0 Buffer Size 00000000 TIB0 DMA Status 00000000 TIB0 DMA Control 00000400 TIB0 DMA Desc Word0 00000000 TIB0 DMA Desc Word1 00000000 FIB0 DMA Desc Base 00000000 FIB0 Buffer Size 00000000 FIB0 DMA Status 00000000 FIB0 DMA Control 00000000 FIB0 DMA Desc Word0 00000000 FIB0 DMA Desc Word1 00000000 TIB1 DMA Desc Base 00000000 TIB1 Buffer Size 00000000 TIB1 DMA Status 00000000 TIB1 DMA Control 00000000 TIB1 DMA Desc Word0 00000000 TIB1 DMA Desc Word1 00000000 FIB1 DMA Desc Base 00000000 FIB1 Buffer Size 00000000 FIB1 DMA Status 00000000 FIB1 DMA Control 00000400 FIB1 DMA Desc Word0 00000000 FIB1 DMA Desc Word1 00000000




TIB2 DMA Desc Base 00000000 TIB2 Buffer Size 00000000 TIB2 DMA Status 00000000 TIB2 DMA Control 00000000 TIB2 DMA Desc Word0 00000000 TIB2 DMA Desc Word1 00000000 FIB2 DMA Desc Base 00000000 FIB2 Buffer Size 00000000 FIB2 DMA Status 00000000 FIB2 DMA Control 00000000 FIB2 DMA Desc Word0 00000000 FIB2 DMA Desc Word1 00000000

TIB FPGA Registers Config 00 InterruptStatus 00 InterruptMask 00 Type/Version 8D SdramWritePtr0 10 SdramWritePtr1 00 SdramWritePtr2 00 SdramReadPtr0 00 SdramReadPtr1 00 SdramReadPtr2 00 GigMacCrcErrors 0 GigMacParityErrors 0 OutSyncErrors 0 SdramParityErrors 0 SdramAddr0 00 SdramAddr1 00 SdramAddr2 00 BufferSize0 93 BufferSize1 03 BufferSize2 00 SdramSopWritePtr0 00 SdramSopWritePtr1 00 SdramSopWritePtr2 00 GigEConfig 01 Address filtering enabled CAMControlStatus F5 CAMWriteTrigger F5 CAMReadTrigger F5 CAMReg2 FFFFFFFF CAMReg1 FFFF0000 CAMReg0 03340000 UnicastFrames 0 MulticastFrames 0 Bytes 0 Aborts 0 WaterMarkLevel 00DB

FIB FPGA Registers Config 00 InterruptStatus 00 InterruptMask 00 Type/Version 07 SdramWritePtr0 80 SdramWritePtr1 53 SdramWritePtr2 07 SdramReadPtr0 70 SdramReadPtr1 53 SdramReadPtr2 07 BariumCrcErrors 0 BariumParityErrors 0




OutSyncErrors 0 SdramParityErrors 0 SdramAddr0 00 SdramAddr1 00 SdramAddr2 00 BufferSize0 F4 BufferSize1 01 BufferSize2 00 SdramSopWritePtr0 70 SdramSopWritePtr1 53 SdramSopWritePtr2 07 GigMacH0 00000000 SynergyH1 000000000000 SynergyH2 000101000000 GigEConfig 01 Add synergy header

GigMac Registers:Control 00 Even parityFlowControl 00 Control frame detected by DA & TYPE filed matchTrunkConfig 02 Encapuslation mode - 802.1q Disable Trunking modeTrunkConfig2 06 Enable parity checking in internal xmit trunking datapath Enable parity checking in internal receive trunking datapathMatchLogicControl 00SuppLogicControl 10 Drop <= 63 bytes enabledTypeUserConfig 00 User Field = 00 Type Field = 00CTRLFieldConfig 02 Don't learnRFRHPtimeLo A2RFRHPTimeHi 05ONEQTypeLo 00ONEQTypeHi 00ColorLo 00ColorHi 00IndexByte0 00IndexByte1 00IndexByte2 00ISLAddDa 0000000000ISLAddSa 000000000000Match 000000000000TrafficThresByte0 00TrafficThresByte1 00TimeIntervalByte0 00TimeIntervalByte1 00GARPAddress 000000000000Control Frame DA 010000C28001Control Frame SA 005054AD5A22CntrlFrameType0 08CntrlFrameType1 88CntrlFrameOpcode0 01CntrlFrameOpcode1 00CntrlFramePtime0 00CntrlFramePtime1 08ColThreshold 00ColDistance0 00ColDistance1 00




IPCRcvTime10 00IPCRcvTime11 00IPCRcvTime20 00IPCRcvTime21 00IPGTxTime0 08IPGTxTime1 00TXLnkConfg0 A0 Full duplex capable Pause capableTXLnkConfg1 01 Asymmetric on pause capable No error, link okRCVLnkConfgStatus0 BC Full duplex capable Pause capableRCVLnkConfgStatus1 50 Link failure Ack configurationRMAC Control 03 Full duplex Link up - enable receptionTMAC Control 01 Link upRMACRecvStatus 10 Rx synchronizedLoopBackControl 00RAMReadEnable 00TFIFOThreshold 01 threshold set to 16 bytesCPSoftReset 1F unset system tx logic unset system rx logic unset Mac Tx logic unset Mac Rx logic unset link autonegotiation logicCPInterrupt 20 RMAC receive config changeCPInterruptMask 0F Host CPU slave machine error mask Mac CPU slave machine error mask Global CPU slave machine error mask Global CPU master machine error maskCPStatConfig 02 Clear on read enabled

SFP Module Information Type = 1, SFP_1000BASE_SX

AFT Information0050.54ad.5a22( 1, 1) ffff.ffff.ffff( 1, 1) 0100.0ccc.cccc( 1, 2)

3 Addresses in CAMGigMac RAM Statistics: defab = 0 defer = 0 abt_lcol = 0 colte = 0 colex = 0 col1 = 0 colm = 0 colt = 0 abt_len = 0 undrn = 0




tcrc = 0 ttot = 21694 toct = 2684083 t64 = 17542 t127 = 0 t255 = 0 t511 = 4152 t1023 = 0 t1518 = 0 t1548 = 0 tgiant = 0 mcast = 4152 bcast = 0 tpause = 0 tisl = 0 tiq = 0

rtot = 3 roct = 34 rcrc = 0 jbbr = 0 runt = 3 short_len = 0 r64 = 0 r127 = 0 r255 = 0 r511 = 0 r1023 = 0 r1518 = 0 r1548 = 0 rgiant = 0 rcode = 3 totrm = 0 totrb = 0 totrg = 0 rpause = 0 rcntl = 0 risl = 0 riq = 0 rdrop = 3 rsupp = 0 rinvalid_encap = 0 rfifo_full = 0

GigMac Register Statistics: seq_err_cntr = 0 datapar_err_cntr = 0 lenpar_err_cntr = 0 pkt_drp_cntr = 0 len_mis_err_cntr = 0 tx_dp_par_err_cntr = 0 rx_dp_par_err_cntr = 0 rx_incr_err_cntr = 0 cbl_drop_cntr = 0

From Iron Bus Statistics: fib_barium_crc_error = 0 fib_barium_parity_error = 0 fib_out_sync_error = 0 fib_sdram_parity_error = 0

To Iron Bus Statistics: tib_gigmac_crc_error = 0 tib_gigmac_parity_error = 0




tib_out_sync_error = 0 tib_sdram_parity_error = 0 tib_unicast_frame_counter = 0 tib_multicast_frame_counter = 0 tib_byte_counter = 0 tib_abort_counter = 0

GE-Slot-2#




MGX-2GE Features and SpecificationsThe dual-port MGX-2GE back card provides a gigabit ethernet trunk uplink to devices (see Figure 6-2).

Figure 6-2 MGX-2GE Back Card

Table 6-5 MGX 2GE Front Panel LED and Port Descriptions

LED Description






1010

80

FAIL

LINK TX

TX

RX

RX

MGX-2GE

4

TX

RX

5

23

1




The MGX-2GE back card uses an MGX-2GE driver and provides two IEEE 802.3z compliant Gigabit Ethernet interfaces that run at 1 Gbps in full duplex mode.

The MGX-2GE back card provides the following key features:

• Efficient, high-performance Gigabit Ethernet bandwidth.

• Optimized Gigabit Ethernet IP-based multiservice network services.

• Auto negotiation.

• Flow control.

• 802.1q encapsulation support for VLANs.

• Configurable loopbacks for troubleshooting.

• SFP (Small Form Factor Pluggable) Security

• Link Management (Auto Negotiation)

• Flow Control Between Gigabit Links

• Interface MAC Address Assignment

• MAC Address Filtering

• Card OIR (Online Insertion & Removal) support

• SFP Hot Swapping

The MGX-2GE driver performs the following tasks:

• Initializing the GE driver subsystem at IOS boot time

• Initializing and configuring the GE backcard

• Downloading the GE backcard firmware images

• Collecting statistics for the CLI and SNMP

• Managing alarm and trap events after insertion, removal, and hot swap

• Managing interface status and configuration changes

• Processing events and alarms

• Monitoring data path hardware failures

• Controlling front card and backcard port and card status LEDs

MXG-2GE SFP SpecificationsTable 6-6 lists the GE back card SFPs and their respective cable types and lengths.

The MGX-2GE back card shown in Figure 6-2 provides a trunk uplink that supports 1 Gbps throughput using multi-mode or single-mode fiber, depending the connector type.




MGX-2GE Installation GuidelinesThis section contains guidelines for the following procedures:

• MGX-2GE First Time Installation

• MGX-2GE Replacement Installation

The MGX-2GE back cards are hot swappable, which means you can remove and replace the back cards without shutting the cards down or turning the power off.


MGX-2GE First Time Installation

For information on installing the back card hardware, see Chapter 3, “Installing the MGX RPM-XF Front and Back Cards.”

After installing the MGX-2GE back card hardware for the first time, you must configure it entering the configure command. For information about configuring the MGX-2GE back card, see the “MGX-2GE Software Configuration Guidelines” section.

MGX-2GE Replacement Installation

For information on removing and installing the back card hardware, see Chapter 3, “Installing the MGX RPM-XF Front and Back Cards.”

If an MGX-2GE back card is replaced, the system automatically downloads the necessary configuration information from the RPM-XF front card; there is no need to configure the new back card unless the front card has been reloaded or switched over subsequent to removal of a back card of the same type. After the information is downloaded, the system recognizes only those interfaces that match the previous MGX-2GE back card configuration (those configured as Up).

Table 6-6 MGX-2GE Cable Specifications

SFP







275 M@ 200 MHz-km

500 M@ 400 MHz-km

550 M@ 500 MHz-km

— — —

1000Base LH/LX

— — 550 M @ 500 MHz-km

550 M@ 400 MHz-km

10 km

1000Base ZX — — — — 70 km




MGX-2GE Software Configuration GuidelinesAfter the MGX-2GE back card is successfully installed, you can configure the card for network use.

Note You do not need to configure the MGX-2GE back card if this is a replacement installation in the same chassis slot. The system automatically downloads the necessary configuration information from the RPM-XF front card.


• MGX-2GE Back Card Default Values

• MGX-2GE Back Card Syntax

• MGX-2GE Interface Configuration

• MGX-2GE Customization


MGX-2GE Back Card Default Values

Table 6-7 lists default values for the MGX-2GE back card. The commands marked with an asterisk (*) are described in the Cisco IOS command reference documentation. The other commands are among those described in this chapter.


MGX-2GE Back Card Syntax

To specify an interface number in a configuration command, use the syntax in Table 6-8 to identify interfaces on the MGX-2GE back card.

Table 6-7 MGX-2GE Back Card Defaults





mtu1*

1. mtu=(maximum transmission unit)

1500 mtu size Same.

negotiation auto [enabled] [no] negotiation auto Same.

Table 6-8 MGX-2GE Interface Syntax

Type of Interface Bay Ports Subinterface (optional)

GE interface 1/ 0 or 1 1–1000




The following example shows the syntax for configuring the Gigabit Ethernet interface on the MGX-2GE back card:

Router(config)# interface gigabitethernet 1/0Router(config-if)#

Note The subinterface configuration is to be used only for configuring 802.1q encapsulation for VLAN support.

The following example shows the syntax for configuring the Gigabit Ethernet subinterface on the MGX-2GE back card:

Router(config)# interface gigabitethernet 1/0.2Router(config-subif)#

MGX-2GE Interface Configuration

After you verify that the MGX-2GE back card is installed correctly, use the following procedure to configure the new interface. Be prepared with the information you will need, such as the interface IP address.

The following procedure is for creating a basic configuration—enabling an interface.

Step 1 At the global configuration prompt, specify the new interface to configure by entering the interface gigabitethernet <bay/port> command and interface address. For example,

Router(config)# interface gigabitethernet 1/0

Step 2 Assign an IP address and a subnet mask to the interface with the ip address configuration subcommand, as in the following example:


Step 3 If necessary, modify the MGX-2GE back card configuration or that of the remote device to ensure that, where appropriate, they use the same settings. For more information, see the “Remote Side Setting” column in Table 6-7.








After you have completed your configuration, you can check it using the show interface gigabitethernet <bay/port>.




MGX-2GE Customization

The following sections present some of the commands that you can use to customize your MGX-2GE back card configuration.


• MGX-2GE Auto Negotiation

• MGX-2GE Loopback Testing

• MGX-2GE 802.1q VLAN Encapsulation

MGX-2GE Auto Negotiation

The negotiation auto command allows you to enable or disable auto negotiation on the Gigabit Ethernet interface. Flow control is the only parameter that is negotiated as the interface is always full duplex with a 1 Gbps speed.

negotiation auto[no] negotiation auto

The default is negotiation auto.

Use the no form of the command to disable auto negotiation.

In the following example, auto negotiation is enabled:

Router(config)# interface gigabitethernet 1/0Router(config-if)# negotiation auto

MGX-2GE Loopback Testing

To enable loopback testing of data transmitted from the front card to the MGX-2GE back card and back, use the loopback command in interface configuration mode.

loopback [ mac | driver ][no] loopback [ mac | driver ]


In the following example, a loopback is set for the MGX-2GE back card:

Router(config)# interface gigabitethernet 1/0Router(config-if)# loopback mac

Note Loopback tests disrupt user traffic on production networks


driver or external1 Loops any outbound traffic from the front card back to the front card at the SERDES. This test must be performed with an external loopback cable on the interface to clear the alarm.

mac or internal1 Loops any outbound traffic received at the MGX-2GE back card’s network interface back into the front card at the MAC controller.

1. Depending on software release version.




MGX-2GE 802.1q VLAN Encapsulation

To define the VLAN encapsulation format as IEEE 802.1Q, use the following commands in interface configuration mode to specify the subinterface the VLAN will use and to define the encapsulation format as IEEE 802.1Q (dot1q), and specify the VLAN identifier:

Router(config)#interface gigabitethernet <bay/port.subinterface>Router(config-subif)#encapsulation dot1q <vlan-identifier>

Example:

Router(config)#interface gigabitethernet 1/0.2Router(config-subif)#encapsulation dot1q 2Router(config-subif)#ip address 10.1.1.1 255.255.255.0

For more information, refer to the Cisco IOS documentation at

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/8021q.htm

MGX-2GE Example Configuration

The following is an example of configuration file commands for a Cisco RPM-XF with an MGX-2GE back card (Router 1) connected back-to-back with a Cisco 7200 series router with a gigabit ethernet line card in slot 3 (Router 2).

Router 1:

interface gigabitethernet 1/0ip address 10.1.2.4 255.0.0.0no shutdownno keepaliveno cdp enable

Router 2:

interface gigabitethernet 3/0ip address 10.1.2.3 255.0.0.0no shutdownno keepaliveno cdp enableno ip mroute-cache

MGX-2GE System Status CheckEach back card maintains information about its configuration, traffic, errors and so on. You can access this information by using the show commands. Following are descriptions and examples of show commands that display back card information and status.

Enter the show interface gigabitethernet <bay/port> command to show general information about the interface, as shown in the following example.

GE-Slot-2#show interface gigabitethernet 1/0GigabitEthernet1/0 is up, line protocol is up Hardware is Gigabit Ethernet MAC Controller, address is 0050.54ad.5a22 (bia 0050.54ad.5a22) Internet address is 3.3.3.3/24 MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec)




Full-duplex mode, link type is autonegotiation, media type is SX output flow-control is off, input flow-control is off ARP type:ARPA, ARP Timeout 04:00:00 Last input never, output 00:00:05, output hang never Last clearing of "show interface" counters 2d00h Input queue:0/75/3/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, 3 runts, 0 giants, 0 throttles 3 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 0 multicast, 0 pause input 0 input packets with dribble condition detected 21691 packets output, 2597423 bytes, 0 underruns 0 output errors, 0 collisions, 3 interface resets 0 babbles, 0 late collision, 0 deferred 3 lost carrier, 0 no carrier, 0 pause output 0 output buffer failures, 0 output buffers swapped out

Enter the show controller gigabitethernet <bay/port > command to show controller-specific information about the interface, as shown in the following example.

GE-Slot-2#show controller gigabitethernet 1/0Interface GigabitEthernet1/0(idb 0x43B978A0)Hardware is Gigabit Ethernet MAC Controller, Slot Index 1

Network Connection Mode is autonegotiate state:RPMXF_GE_COMPLETE_NEGOTIATE

the other end auto-negotiate mode is auto port monitoring status = 0x0

network link is up, loopback type is none SFP type is 1000BASE-SX ip_routecache=0x11(dfs=0/mdfs=0), max_mtu=1524 rpmxf_ge_ds=0x442E2C80 resets=3, reset_init=1, reset_restart=3 link_state_reason=5

GE Backcard Registers Card Interrupt Status 00000000 Card Interrupt Mask 00000000 Card ASIC Reset 00000000 Card Discrete Input 01000010 Card Discrete Output 000000B1 Card Local Bus Timeout 0000FFFF Card Local Bus Timeout Address 00000000 Card PCI SERR Address 00000000 Card PCI PERR Address 00000000 Card PCI Bus Idle Stats FB52A437 Card PCI Bus Transfer Stats 0703854C Card Wrap Test 00000000 Card Debug Header Control 00000000

Barium Registers ID 00136049 Configuration 00000008 Reset PCI Bus A Reset PCI Bus B Reset PCI Bus C PCI Bus A Status 00008280




PCI Bus B Status 00000280 PCI Bus C Status 00000280 Global IronBus Cfg1 540070A0 Global IronBus Cfg2 054C6086 Global IronBus Sts1 0000F11C Global IronBus Sts2 0000F11C DMA Reset 00000000 Interrupt Status 00004000 Interrupt Mask 4000801F Iron Bus 0 Status 1 00000000 Iron Bus 0 Status 2 00000000 Iron Bus 0 Status 3 00000000 Iron Bus 1 Status 1 0FFFFF0F Iron Bus 1 Status 2 0000FFFF Iron Bus 1 Status 3 000CFFFF TIB0 DMA Desc Base 00000000 TIB0 Buffer Size 00000000 TIB0 DMA Status 00000000 TIB0 DMA Control 00000400 TIB0 DMA Desc Word0 00000000 TIB0 DMA Desc Word1 00000000 FIB0 DMA Desc Base 00000000 FIB0 Buffer Size 00000000 FIB0 DMA Status 00000000 FIB0 DMA Control 00000000 FIB0 DMA Desc Word0 00000000 FIB0 DMA Desc Word1 00000000 TIB1 DMA Desc Base 00000000 TIB1 Buffer Size 00000000 TIB1 DMA Status 00000000 TIB1 DMA Control 00000000 TIB1 DMA Desc Word0 00000000 TIB1 DMA Desc Word1 00000000 FIB1 DMA Desc Base 00000000 FIB1 Buffer Size 00000000 FIB1 DMA Status 00000000 FIB1 DMA Control 00000400 FIB1 DMA Desc Word0 00000000 FIB1 DMA Desc Word1 00000000 TIB2 DMA Desc Base 00000000 TIB2 Buffer Size 00000000 TIB2 DMA Status 00000000 TIB2 DMA Control 00000000 TIB2 DMA Desc Word0 00000000 TIB2 DMA Desc Word1 00000000 FIB2 DMA Desc Base 00000000 FIB2 Buffer Size 00000000 FIB2 DMA Status 00000000 FIB2 DMA Control 00000000 FIB2 DMA Desc Word0 00000000 FIB2 DMA Desc Word1 00000000

TIB FPGA Registers Config 00 InterruptStatus 00 InterruptMask 00 Type/Version 8D SdramWritePtr0 10 SdramWritePtr1 00 SdramWritePtr2 00 SdramReadPtr0 00 SdramReadPtr1 00 SdramReadPtr2 00 GigMacCrcErrors 0




GigMacParityErrors 0 OutSyncErrors 0 SdramParityErrors 0 SdramAddr0 00 SdramAddr1 00 SdramAddr2 00 BufferSize0 93 BufferSize1 03 BufferSize2 00 SdramSopWritePtr0 00 SdramSopWritePtr1 00 SdramSopWritePtr2 00 GigEConfig 01 Address filtering enabled CAMControlStatus F5 CAMWriteTrigger F5 CAMReadTrigger F5 CAMReg2 FFFFFFFF CAMReg1 FFFF0000 CAMReg0 03340000 UnicastFrames 0 MulticastFrames 0 Bytes 0 Aborts 0 WaterMarkLevel 00DB

FIB FPGA Registers Config 00 InterruptStatus 00 InterruptMask 00 Type/Version 07 SdramWritePtr0 80 SdramWritePtr1 53 SdramWritePtr2 07 SdramReadPtr0 70 SdramReadPtr1 53 SdramReadPtr2 07 BariumCrcErrors 0 BariumParityErrors 0 OutSyncErrors 0 SdramParityErrors 0 SdramAddr0 00 SdramAddr1 00 SdramAddr2 00 BufferSize0 F4 BufferSize1 01 BufferSize2 00 SdramSopWritePtr0 70 SdramSopWritePtr1 53 SdramSopWritePtr2 07 GigMacH0 00000000 SynergyH1 000000000000 SynergyH2 000101000000 GigEConfig 01 Add synergy header

GigMac Registers:Control 00 Even parityFlowControl 00 Control frame detected by DA & TYPE filed matchTrunkConfig 02 Encapuslation mode - 802.1q Disable Trunking mode




TrunkConfig2 06 Enable parity checking in internal xmit trunking datapath Enable parity checking in internal receive trunking datapathMatchLogicControl 00SuppLogicControl 10 Drop <= 63 bytes enabledTypeUserConfig 00 User Field = 00 Type Field = 00CTRLFieldConfig 02 Don't learnRFRHPtimeLo A2RFRHPTimeHi 05ONEQTypeLo 00ONEQTypeHi 00ColorLo 00ColorHi 00IndexByte0 00IndexByte1 00IndexByte2 00ISLAddDa 0000000000ISLAddSa 000000000000Match 000000000000TrafficThresByte0 00TrafficThresByte1 00TimeIntervalByte0 00TimeIntervalByte1 00GARPAddress 000000000000Control Frame DA 010000C28001Control Frame SA 005054AD5A22CntrlFrameType0 08CntrlFrameType1 88CntrlFrameOpcode0 01CntrlFrameOpcode1 00CntrlFramePtime0 00CntrlFramePtime1 08ColThreshold 00ColDistance0 00ColDistance1 00IPCRcvTime10 00IPCRcvTime11 00IPCRcvTime20 00IPCRcvTime21 00IPGTxTime0 08IPGTxTime1 00TXLnkConfg0 A0 Full duplex capable Pause capableTXLnkConfg1 01 Asymmetric on pause capable No error, link okRCVLnkConfgStatus0 BC Full duplex capable Pause capableRCVLnkConfgStatus1 50 Link failure Ack configurationRMAC Control 03 Full duplex Link up - enable receptionTMAC Control 01 Link upRMACRecvStatus 10 Rx synchronized




LoopBackControl 00RAMReadEnable 00TFIFOThreshold 01 threshold set to 16 bytesCPSoftReset 1F unset system tx logic unset system rx logic unset Mac Tx logic unset Mac Rx logic unset link autonegotiation logicCPInterrupt 20 RMAC receive config changeCPInterruptMask 0F Host CPU slave machine error mask Mac CPU slave machine error mask Global CPU slave machine error mask Global CPU master machine error maskCPStatConfig 02 Clear on read enabled

SFP Module Information Type = 1, SFP_1000BASE_SX

AFT Information0050.54ad.5a22( 1, 1) ffff.ffff.ffff( 1, 1) 0100.0ccc.cccc( 1, 2)

3 Addresses in CAMGigMac RAM Statistics: defab = 0 defer = 0 abt_lcol = 0 colte = 0 colex = 0 col1 = 0 colm = 0 colt = 0 abt_len = 0 undrn = 0 tcrc = 0 ttot = 21694 toct = 2684083 t64 = 17542 t127 = 0 t255 = 0 t511 = 4152 t1023 = 0 t1518 = 0 t1548 = 0 tgiant = 0 mcast = 4152 bcast = 0 tpause = 0 tisl = 0 tiq = 0

rtot = 3 roct = 34 rcrc = 0 jbbr = 0 runt = 3 short_len = 0 r64 = 0 r127 = 0




r255 = 0 r511 = 0 r1023 = 0 r1518 = 0 r1548 = 0 rgiant = 0 rcode = 3 totrm = 0 totrb = 0 totrg = 0 rpause = 0 rcntl = 0 risl = 0 riq = 0 rdrop = 3 rsupp = 0 rinvalid_encap = 0 rfifo_full = 0

GigMac Register Statistics: seq_err_cntr = 0 datapar_err_cntr = 0 lenpar_err_cntr = 0 pkt_drp_cntr = 0 len_mis_err_cntr = 0 tx_dp_par_err_cntr = 0 rx_dp_par_err_cntr = 0 rx_incr_err_cntr = 0 cbl_drop_cntr = 0

From Iron Bus Statistics: fib_barium_crc_error = 0 fib_barium_parity_error = 0 fib_out_sync_error = 0 fib_sdram_parity_error = 0

To Iron Bus Statistics: tib_gigmac_crc_error = 0 tib_gigmac_parity_error = 0 tib_out_sync_error = 0 tib_sdram_parity_error = 0 tib_unicast_frame_counter = 0 tib_multicast_frame_counter = 0 tib_byte_counter = 0 tib_abort_counter = 0

GE-Slot-2#



Chapter 6 Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back CardsMGX-1GE and MGX-2GE Installation Troubleshooting

MGX-1GE and MGX-2GE Installation TroubleshootingSee Table 6-9 for descriptions of the LEDs on the MGX-1GE and MGX-2GE back cards. Follow the instructions in Table 6-10 to troubleshoot the installation.

Table 6-9 MGX-1GE and MGX-2GE Back Card LED Status and Definitions


LINK Green Carrier detected.

Off Carrier not detected.

TX (transmit) Green Transmitting traffic.

Off Not transmitting traffic.

RX (receive) Green Receiving traffic.

Off Not receiving traffic.

FAIL Yellow Major failure has disabled the back card.

Off Back card is operating properly

Table 6-10 MGX-1GE and MGX-2GE Installation Troubleshooting


The back card fail LED does not light during the power-on self-test when the back card is plugged into the back card slot.





Back card initialization fails.


Remove the back cards (upper and lower slots) and the front card and install them into another chasis slot.



The interface does not come up or constantly comes up and then goes down.

Configuration mismatched.

Check the configuration on both sides. (See the “MGX-1GE Software Configuration Guidelines” section on page 6-4 for more information.)

Cables connected incorrectly.

Check the cabling on both sides. Ensure the receive is connected to the transmit on the remote end and vice versa.

Bad cables. Replace the cables. Ensure your cabling meets the specifications in Table 6-6 on page 6-17.

C H A P T E R



7Configuring the MGX RPM-XF

This chapter describes how to complete a basic configuration of the MGX Route Processor Module (RPM-XF). The chapter contains the following sections:

• Accessing the RPM-XF Command Line Interface

• Booting the RPM-XF

• Verifying the Configuration

• Establishing 1:N Redundancy Between Two or More RPM-XF Cards

• Enabling IP Accounting Counters

This chapter provides information necessary to get the RPM-XF up and running. Detailed command information is available in the Cisco IOS command reference publications.

Accessing the RPM-XF Command Line InterfaceTo configure the RPM-XF, you must access the command line interface (CLI) of the RPM-XF.

The RPM-XF CLI can be accessed using any of the following methods:

• Console port on the MGX-XF-UI management back card of the RPM-XF

If you configure the RPM-XF on site, connect a console terminal (an ASCII terminal or a PC running terminal emulation software) directly to the console port on your MGX-XF-UI back card using an RS-232 to RJ-45 rollover cable for CLI access (see Chapter 3, “Installing the MGX RPM-XF Front and Back Cards”).

Note It is recommended that you always set the line speed on the console port of the MGX-XF-UI back card to 9600 baud. See “Configuring the Console and Auxiliary Ports” in Chapter 4.

• cc from another MGX 8850 card

After initial configuration, you can also configure the RPM-XF through the PXM45. You can access the RPM-XF CLI by entering the cc (change card) command from any of the other cards in the switch.

• Telnet from a workstation, PC, or another router

After initial configuration, you can also configure the RPM-XF remotely via Telnet. After the RPM-XF is installed and has PVCs to other RPM-XFs or routers in the network, you can Telnet to access the RPM-XF CLI remotely from these other devices.



Chapter 7 Configuring the MGX RPM-XFBooting the RPM-XF

You can also telnet through the Fast Ethernet ports on the MGX-XF-UI management back card. See Chapter 4, “Installing and Configuring the MGX-XF-UI Management Back Card,” to see how to assign IP address to the FE interface.

Note Connecting a modem to the auxiliary port on the MGX-XF-UI is not supported.

Booting the RPM-XFThe RPM-XF bootflash is used to store boot image, configuration and run-time image files. A valid RPM-XF boot image must be present in the bootflash to successfully boot the card.

RPM-XF Bootflash PrecautionsThe RPM-XF boot image that comes loaded on the Flash will work for all RPM-XF IOS images. Therefore, there is no reason to delete or move the factory installed boot image.

If you accidently delete or corrupt the bootflash, you will need to use the ROM Monitor to recover the bootflash. In the ROM Monitor mode, use the tftpdnld utility described in the “Using the tftpdnld Command” section in Appendix A.

Verifying the Cisco IOS Files on BootflashEnter the show bootflash command to verify the Cisco IOS files on the bootflash. The following screen displays the RPM-XF command sequence.

router-slot14#show bootflash:-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name1 .. image D7F765BC 306604 20 2647428 Apr 22 2002 11:22:47 rpmxf-boot-mz.0204052 .D config 65AD67B1 327CE0 18 136795 Apr 26 2002 05:02:06 auto_config_slot143 .. config C3CBD7D7 34937C 18 136732 Apr 30 2002 02:15:24 auto_config_slot14

62614660 bytes available (2921340 bytes used)

Verifying the Cisco IOS Files in the PXM45 C:FW DirectoryOn the PXM45 hard drive, the RPM-XF image files are stored in the C:FW directory. To see these files, change the directory to C:FW and enter the ll command. You can also enter x: to view the C:FW directory on the PXM hard disk. You should see a file with a name beginning with rpmxf-p12-mz, which is the Cisco IOS image.

Tip FTP the RPM-XF Cisco IOS image into the C:FW directory of the PXM45 hard disk with the filename specified in the RPM-XF boot system command.

The following screen displays the PXM, AXSM, and RPM-XF images displayed after entering the ll command.

Unknown.7.PXM.a > cd C:FW

Unknown.7.PXM.a > ll




Listing Directory .:drwxrwxrwx 1 0 0 13312 Apr 29 18:45 ./drwxrwxrwx 1 0 0 13312 Apr 29 14:42 ../-rwxrwxrwx 1 0 0 7438480 Apr 8 17:18 rpmxf-p12-mz.020405 -rwxrwxrwx 1 0 0 6049940 Apr 4 17:48 pxm45_003.000.000.026-A_mgx.fw -rwxrwxrwx 1 0 0 3121648 Mar 29 18:16 axsm_003.000.000.234-P1.fw -rwxrwxrwx 1 0 0 6049444 Apr 2 16:09 pxm45_003.000.000.000-D_mgx.fw -rwxrwxrwx 1 0 0 6043924 Mar 22 14:04 pxm45_003.000.000.001-A_mgx.fw -rwxrwxrwx 1 0 0 6043892 Mar 20 18:51 pxm45_003.000.000.239-A_mgx.fw -rwxrwxrwx 1 0 0 2654768 Mar 29 18:14 axsme_003.000.000.234-P1.fw -rwxrwxrwx 1 0 0 6050100 Mar 29 17:15 pxm45_003.000.000.009-A_mgx.fw

In the file system : total space : 818961 K bytes free space : 470713 K bytes

Verifying the Cisco IOS Configuration Files in the PXM45 E:RPM DirectoryOn the PXM45 hard disk, RPM-XF configuration files are stored in the E:RPM directory. To see these files, enter the dir E:RPM command on the PXM.

The following screen displays the RPM-XF configuration files stored in the E:RPM directory on the PXM hard disk.

Unknown.8.PXM.a > dir E:RPM

Listing Directory E:RPM:drwxrwxrwx 1 0 0 2048 May 13 12:41 ./drwxrwxrwx 1 0 0 2048 May 13 11:24 ../-rwxrwxrwx 1 0 0 627 Feb 5 13:33 zen10.conf.svenki -rwxrwxrwx 1 0 0 806 Feb 6 20:01 rpm12.conf.svenki -rwxrwxrwx 1 0 0 632 Feb 4 23:16 zenith10.conf.svenki -rwxrwxrwx 1 0 0 5747 Apr 16 14:34 slot05 -rwxrwxrwx 1 0 0 77849 Feb 13 01:07 zen14.conf.svenki021202 -rwxrwxrwx 1 0 0 59697 Feb 13 00:53 zen3.conf.svenki021202 -rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot05 -rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot13 -rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot03 -rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot01 -rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot06 -rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot09 -rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot12 -rwxrwxrwx 1 0 0 14 May 13 11:14 auto_config_slot14 -rwxrwxrwx 1 0 0 842 Apr 25 18:25 zen

In the file system : total space : 102140 K bytes free space : 89446 K bytes

Initializing the RPM-XF CardThe first time you boot the RPM-XF card, it comes up in boot mode (Boot-Hold). Refer to the Cisco MGX 8850 Switch Software Configuration Guide for instructions on copying files.

Step 1 From the switch CLI, enter cc <RPM-XF card slot #> to access the router card.

The router prompt (>) appears.




Step 2 Enter enable and your password when prompted, so that you can enter privileged commands.

Step 3 Enter dir to display the flash memory directory as shown here. Note the boot image software version.

router2-slot14#dirDirectory of bootflash:/

1 -rw- 2647428 Apr 22 2002 11:22:47 rpmxf-boot-mz.020405 3 -rw- 136732 Apr 30 2002 02:15:24 auto_config_slot14

65536000 bytes total (62614660 bytes free)

Step 4 Enter dir x: to display the contents of the C:FW directory on the PXM45 hard drive. Note the runtime image filename for Step 7.

router2-slot14#dir x:Directory of x:/

0 -rw- 7438480 Apr 09 2002 01:18:34 rpmxf-p12-mz.020405 0 -rw- 6049940 Apr 05 2002 01:48:02 pxm45_003.000.000.026-A_mgx.fw 0 -rw- 3121648 Mar 30 2002 02:16:02 axsm_003.000.000.234-P1.fw 0 -rw- 6049444 Apr 03 2002 00:09:12 pxm45_003.000.000.000-D_mgx.fw 0 -rw- 6043924 Mar 22 2002 22:04:12 pxm45_003.000.000.001-A_mgx.fw 0 -rw- 6043892 Mar 21 2002 02:51:20 pxm45_003.000.000.239-A_mgx.fw 0 -rw- 2654768 Mar 30 2002 02:14:22 axsme_003.000.000.234-P1.fw 0 -rw- 6050100 Mar 30 2002 01:15:30 pxm45_003.000.000.009-A_mgx.fw

838616064 bytes total (482072752 bytes free)

To boot the runtime image from the bootflash, copy the image to the bootflash, as follows.

Router#copy x:rpmxf-p12-mz.1228T_XT1 bootflash:Destination filename [rpmxf-p12-mz.1228T_XT1]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC:::::CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC7445832 bytes copied in 84.180 secs (88640 bytes/sec)

Step 5 Enter configure terminal at the prompt to enable the RPM-XF interface.

Router#configure terminal

Step 6 Enter no boot system to clear any existing boot system commands.

Router(config)#no boot system

Step 7 The RPM-XF can be booted from either the bootflash or PXM45 hard disk, by entering either,

boot system bootflash:< filename> to load the runtime software from the bootflashorboot system x:< filename> to load the runtime software from the PXM45 hard disk

Step 8 Enter end or press Ctrl Z to exit the configuration interface mode.

Router(config-if)#end




Step 9 Enter copy run start to save the configuration.

Router#copy run start

Step 10 Enter reload on the RPM-XF.

Router#reload

To verify the version, enter the show version or show bootvar commands. See the “Verifying the Configuration” section later in this chapter.

Assigning an IP Address to the Switch InterfaceYou need to assign an IP address for the RPM-XF on the ATM switch. This procedure tells you how to configure the ATM switch interface with the IP address.

Timesaver Obtain the correct IP and ATM network addresses for your RPM-XF on the ATM switch from your system administrator or consult your network plan to determine correct addresses before you continue to configure the RPM-XF.

Step 1 Enter show ip int brief to display your router IP interfaces.

Router#show ip int briefInterface IP-Address OK? Method Status ProtocolSwitch0 unassigned YES unset up up Switch1 unassigned YES unset up up FastEthernet2/0 unassigned YES unset administratively down down FastEthernet2/1 unassigned YES unset administratively down down

Note The switch0 interface can not be assigned an IP address.

Step 2 Enter conf terminal to enter global configuration mode.

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

Step 3 To enter interface configuration mode for the ATM interface, enter interface switch1 at the prompt.

Router(config)#interface switch1

Step 4 Enter ip address followed by the IP address to be assigned to the ATM switch.

Router(config-if)#ip address 1.1.1.1 255.255.255.0

Step 5 Enter end or press Ctrl-Z to exit the configuration interface mode.

Router(config-if)#end

Step 6 Enter show ip int brief to display the IP address assigned to the ATM switch. For example,

Router#show ip int briefInterface IP-Address OK? Method Status ProtocolSwitch0 unassigned YES unset up up Switch1 1.1.1.1 YES manual up up




Note The newly added interface address appears in the display.

Step 7 Enter show run to verify the configuration of the RPM-XF, as shown in the following example screen.

Router#show runBuilding configuration...

Current configuration :687 bytes!version 12.2no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname Router!boot system x:rpmxf-p12-mz.020405boot config e:auto_config_slot02no logging consoleenable password cisco!ip subnet-zero!!!interface Switch1 ip address 1.1.1.1 255.255.255.0 switch auto_synch off! ip classlessno ip http serverip pim bidir-enable!snmp-server engineID local 80000009FF0000A100000000snmp-server community public ROsnmp-server community private RWsnmp-server ifindex persist!!line con 0 exec-timeout 0 0 stopbits 1line aux 0 stopbits 1line vty 0 4 exec-timeout 0 0 no login!end

Step 8 Enter copy run start at the prompt to write the configuration to the router NVRAM memory.

Router#copy run startBuilding configuration...[OK]

The IP address is now active and ready to use.




Note The ATM interface can be further configured with logical subinterfaces as needed. To see how to configure subinterfaces on the ATM switch interface, see Chapter 8, “Configuring PNNI Communications,” the “Creating and Configuring a Switch Subinterface” section.

Booting RPM-XF Using TFTP from a TFTP ServerOnce you add the IP address on the FastEthernet port, you can configure the RPM-XF card to load runtime software from the TFTP server.

Note This procedure is optional. The preferred procedure for loading the runtime software from the PXM45 hard drive is described earlier in “Initializing the RPM-XF Card.”

Use the following procedure to configure the RPM-XF card to load runtime software from a TFTP server:

Step 1 Enter cc <RPM-XF card slot #> to access the router card.

The router prompt (>) appears.

Step 2 Enter enable and your password, when prompted, so that you can enter privileged commands.

Step 3 Enter config terminal to enter global configuration mode.

Step 4 Enter boot system tftp followed by the image name and address of the server from which you want to download the boot file as shown in this example.

Router(config)#boot system tftp://171.69.1.129/tftpboot/shrinath/rpmxf-p12-mz

Step 5 Enter end or press Ctrl-Z to exit configuration mode.

Router(config)#end

Step 6 Enter show run to view your configuration. The configuration is similar to the following example..

Router#show runBuilding configuration...

Current configuration : 710 bytes!version 12.1no service single-slot-reload-enableservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname Router!boot system tftp://171.69.1.129/tftpboot/shrinath/rpmxf-p12-mzboot config e:auto_config_slot11logging rate-limit console 10 except errorsenable password cisco!ip subnet-zerono ip finger!no ip dhcp-client network-discovery




Step 7 Enter copy run start at the prompt to write the configuration to the router NVRAM memory.

Router#copy run startBuilding configuration...[OK]

Step 8 To load the runtime image from the TFTP server, enter the reload command on the RPM-XF.

Router#reload

You can also reboot the RPM-XF by entering the resetcd <slot #> command on the PXM.

Note Omitting the card number resets the entire system or causes PXM switchover.

RPM-XF Boot-up SequenceEach time you turn on power to the RPM-XF, by inserting the RPM-XF into the MGX 8850, it goes through the following boot sequence:

1. The RPM-XF runs diagnostics on the CPU, memory, and interfaces.

2. The system boot software, which is the boot image, executes and searches for a valid Cisco IOS image, which is the RPM-XF runtime software.

The source of the Cisco IOS image is determined by the configuration register setting. To verify this setting, you can enter either the show version or show bootvar command. (See the “Viewing the Hardware Configuration” section later in this chapter.)

• If the configuration register is set to the factory-default of 0x2102, the RPM-XF will come up and stay in boot mode until a run-time image is specified in the configuration. Entering the dspcds command on the PXM will show the card in Boot-Hold state.

3. The RPM-XF will look for the runtime image either in bootflash or in the C:FW directory on the PXM hard disk. The search for runtime image is determined by the boot system command entered.

• Entering the boot system x:<runtime_image_name> command will result in a search for a runtime image in the PXM C:FW directory on the PXM hard disk.

• Entering the boot system bootflash:<runtime_image_name> command will result in a search for a run time image in the bootflash.

4. If the runtime software is not found after three attempts, the RPM-XF reverts to the Boot-Hold state.

5. If a valid Cisco IOS image is found, then the RPM-XF searches for a valid configuration, which can reside in NVRAM or as a configuration file either in the PXM E:RPM directory or in bootflash.

If you want to load from a specific configuration file, you should enter either the boot config bootflash:<config_file> command or the boot config e:<config_file> command.

6. For normal RPM-XF operation, there must be a valid Cisco IOS image in the PXM45 C:FW directory or in bootflash, and a configuration in NVRAM. in bootflash, or in the PXM45 E:RPM directory on the PXM disk.

The first time you boot the RPM-XF, configure the RPM-XF interfaces and save the configuration to a file in NVRAM. Then follow the procedure described in “Initializing the RPM-XF Card.” For information on the Cisco IOS instructions, see Appendix C, “Cisco IOS and Configuration Basics.”



Chapter 7 Configuring the MGX RPM-XFVerifying the Configuration

Verifying the ConfigurationEnter the show commands to display the status of the all interfaces.

Using the show Commands to Verify the Interface Status

In the following procedure, enter the show commands to verify that interfaces are configured and operating correctly.

Step 1 Enter the show interface switch <number> command to specify one of the interfaces. Verify that the interface is up. When the interface and line protocol are up, this indicates that you have working interfaces as shown in the following examples.

Cell bus interface:

Router#show interfaces Switch 0Switch0 is up, line protocol is up Hardware is Mxt4400 Based ATM PA MTU 4470 bytes, sub MTU 4470, BW 149760 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ATM, loopback not set Encapsulation(s):AAL5, PVC mode 249 maximum active VCs, 16 current VCCs VC idle disconnect time:300 seconds Last input never, output never, output hang never Last clearing of "show interface" counters 1d22h 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, 1 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 267611 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 183681 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out

Serial bus interface:

Router#show interfaces Switch1Switch1 is up, line protocol is up Hardware is Mxt4700 Based ATM PA MTU 4470 bytes, sub MTU 4470, BW 1197656 Kbit, DLY 100 usec, reliability 255/255, txload 204/255, rxload 209/255 Encapsulation ATM, loopback not set Encapsulation(s):AAL5, PVC mode 15743 maximum active VCs, 2009 current VCCs VC idle disconnect time:300 seconds Last input never, output never, output hang never Last clearing of "show interface" counters 1d22h Input queue:0/75/2/0 (size/max/drops/flushes); Total output drops:0 Queueing strategy:fifo Output queue :0/40 (size/max) 5 minute input rate 982254000 bits/sec, 558113 packets/sec 5 minute output rate 958783000 bits/sec, 544781 packets/sec 354773033 packets input, 712453604 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 2 input errors, 1 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 1464016596 packets output, 4226118672 bytes, 0 underruns




0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out

Step 2 Enter the show protocols command to display the protocols configured for the entire system and for the specific interfaces.

If necessary, return to configuration mode to add or remove protocol routing on the system or specific interfaces.

Verify that the line protocol is up. When the interface and line protocol are up, this indicates that you have a working interface, as shown below.

router2-slot14#show protocols Global values: Internet Protocol routing is enabledSwitch0 is up, line protocol is upSwitch1 is up, line protocol is upSwitch1.40 is up, line protocol is up Internet address is 2.2.2.2/24Switch1.41 is up, line protocol is up Internet address is 3.3.3.3/24Switch1.42 is up, line protocol is upFastEthernet2/0 is administratively down, line protocol is downFastEthernet2/1 is administratively down, line protocol is down

Step 3 Enter the show running-config command to display the running configuration file.

Step 4 Enter the show startup-config command to display the configuration stored in NVRAM.

Verify that the configuration is accurate for the system and that each interface is the same. If they are different from running-config, you may have forgotten to enter a copy run start command.

If the interface is down and you have configured it to be up, or if the displays indicate that the hardware is not functioning properly, be sure that the network interface is properly connected and terminated. If you still have problems bringing the interface up, contact a system administrator or TAC for assistance.

For detailed software configuration information, refer to the Cisco IOS configuration and command reference publications. These publications are available on the Documentation CD-ROM that came with your RPM-XF, or you can order printed copies.

Viewing the Hardware Configuration

The show version (or show hardware) command displays the configuration of the system hardware, for example, the number of each back card type installed, the software version, the names and sources of configuration files, and the boot images.

Note You may not be able to view hardware configuration information entering show version from a remote location.

The following is an example of the show version command output.

router2-slot14#show versionCisco Internetwork Operating System Software IOS (tm) RPMXF Software (RPMXF-P12-M), Experimental Version 12.2(20020418:192730) [swtools-zenith_fcs1_throttle.nightly 112]Copyright (c) 1986-2002 by cisco Systems, Inc.Compiled Mon 29-Apr-02 04:20 by Image text-base:0x4000A940, data-base:0x41000000




ROM:System Bootstrap, Version 12.2(20020127:182207) [swtools-ROMMON 113], DevTest SoftwareBOOTLDR:RPMXF Software (RPMXF-BOOT-M), Experimental Version 12.2(20020321:034801) [swtools-zenith1.nightly 192]

router2-slot14 uptime is 5 hours, 38 minutesSystem returned to ROM by reloadSystem image file is "x:rpmxf-p12-mz_fcs1.020429"

cisco RPM-XF (RPM-XF1) processor with 487424K/32768K bytes of memory.R7000 CPU at 400Mhz, Implementation 39, Rev 3.3, 256KB L2, 4096KB L3 CacheLast reset from service module resetPXF processor tmc0 is running.PXF processor tmc1 is running.2 FastEthernet/IEEE 802.3 interface(s)2 ATM network interface(s)509K bytes of non-volatile configuration memory.

65536K bytes of Flash internal SIMM (Sector size 512KB).Configuration register is 0x2

WARNING:Image contains R7k watch exception code.

Viewing the Boot Variable

The show bootvar command displays the boot variable, as shown in the following example.

Router#show bootvarBOOT variable = x:rpmxf-p12-mz.1228T_XT1,12;CONFIG_FILE variable = e:auto_config_slot02BOOTLDR variable = bootflash:rpmxf-boot-mz.1228T_XT1Configuration register is 0x2

Using show Commands to Display Back Card Information

To determine which type of back card is installed in your system, enter the show rpm command. In the following example, back card information is displayed for the RPM-XF card in slot 11.

Router>enablePassword:Router#show rpmRPM is in chassis slot 11PXM has ip address 172.29.5.248Active PXM is in slot 7

Network IO Interrupt Throttling: throttle count=0, timer count=0 active=0, configured=1 netint usec=4000, netint mask usec=1000

RPM-XF IO FPGA Registers: flash_watchdog_enable (0x14200000) : 0x00000033 flash_size (0x14200004) : 0x00000006 lev1_watchdog (0x14200008) : 0x0000FA00 led_control (0x14200014) : 0x00000002 lev2_watchdog (0x14200018) : 0x000FFFFF int_status_0 (0x1420001C) : 0x00001000 int_mask_0 (0x14200024) : 0xC3CEFC81 masked_int_status_0 (0x1420006C) : 0x00000000 int_mask_1 (0x14200028) : 0x00000004 reset (0x1420002C) : 0x00000002 power_adjust (0x14200054) : 0x00000000



Chapter 7 Configuring the MGX RPM-XFEstablishing 1:N Redundancy Between Two or More RPM-XF Cards

slot_id (0x14200058) : 0x0000000B

RPM EEPROM contents: Hardware Revision :0.4 Part Number :73-5426-03 Board Revision :04 Deviation Number :0-0 Fab Version :02 PCB Serial Number :SAG06112DYF RMA Test History :00 RMA Number :0-0-0-0 RMA History :00 Top Assy. Part Number :800-09307-03Management Back Card EEPROM contents: Hardware Revision :0.1 Part Number :73-5822-01 Board Revision :A0 Deviation Number :0-0 Fab Version :01 PCB Serial Number :SAK0519002H RMA Test History :00 RMA Number :0-0-0-0 RMA History :00 Top Assy. Part Number :800-09492-01

zen2-slot14#sh rpm card-infoPXM Supports Redundancy :YesRPM Physical Slot Number :14RPM Logical Slot Number :14RPM Selftest :DisabledRPM Selftest Period :0RPM Backcard Type [Upper Slot] :MGX-XF-OC12RPM Backcard Type [Lower Slot] :MGX-XF-UIRPM Card State :ACTIVERPM Internal Card State :ACTIVERPM skipped initial configuration in the NVRAM:YesConfiguration file was received from PXM:YesAuto Configuration File Used :NoneRPM Redundancy Mode:LinkedRPM Redundancy Link Type:Primary

See “Verifying Ethernet Connectivity” in Chapter 4 to verify that each interface port is functioning properly.

Establishing 1:N Redundancy Between Two or More RPM-XF Cards

RPM-XF cards support 1:N redundancy, whereby one RPM-XF card can be configured as a redundant or secondary (backup) card for one or multiple primary RPM-XF cards, forming a redundant group. There can be multiple redundant groups in one shelf. RPM-XF 1:N redundancy is a warm redundancy, in which the configuration of a failed primary card is copied to the standby secondary card. All traffic to and from the primary RPM-XF card is switched to the secondary card after it becomes active. Because this is a warm redundancy solution, service interruption is expected. As with other service modules, the layer 2 state is restored when the secondary card becomes active. However, RPM-XF also performs layer 3 functionality, such as maintaining routing tables. The routing tables are created manually or by routing protocols, such as IGRP, BGP, or OSPF. Because routing protocols are used, the layer 3 state is restored within three to five minutes, depending on the protocol used and the size of the configuration.




RPM-XF 1:N redundancy supports the following features:

• Increases availability by decreasing the DPM of the network by reducing boot-up, switchover, and upgrade times.

• Supports L2 redundancy and restores L3 state via reconvergence.

• Support for up to 11 active (primary) RPM-XF cards per single redundant (standby or secondary) RPM-XF.

• Support for a maximum of 6 redundant groups per MGX 8850.

The redundant card must be present and active and must not have any resource partitions configured. Any connection configuration will cause the addred command to be rejected.

To establish a backup card for an RPM-XF card, use the following procedure.

Step 1 Log on to the switch.

Step 2 If you have not done so already, initialize both cards as described earlier in this chapter in the “Initializing the RPM-XF Card” section.

Step 3 Enter the dspcds command to verify that the primary and secondary RPM-XF card are in the “Active” state.

Step 4 Verify that there is an auto_config_slot# file on the E:RPM directory of PXM disk for the slot corresponding to the primary RPM-XF card. If not, do the following:

a. log onto the primary RPM-XF card and

b. add boot config e:auto_config_slot# to the configuration and

c. enter a write mem. With RPM-XF redundancy, configuration is always stored in the auto_config file on the PXM disk.

Step 5 Enter the addred command.

Switch.7.PXM.a > addred <redPrimarySlotNum> <redSecondarySlotNum> <redType>

Note After you enter the addred command, the switch resets the secondary card; therefore, the secondary card will be unavailable for a few minutes.

Step 6 When the reset is complete, enter the dspcds command to show the primary and secondary cards in the active and standby states, respectively.


<redPrimarySlotNum> Slot number of the primary RPM-XF card.

<redSecondarySlotNum> Slot number of the secondary RPM-XF card.

<redType> 2 for 1:n redundancy.

Note 1 is for 1:1 redundancy, which is not supported.




The redundant RPM cards are shown in slots 2 and 10 with the standby card in slot 10.

Unknown.8.PXM.a > dspcdsUnknown System Rev:03.00 May. 13, 2002 18:55:56 GMTChassis Serial No: SCA0444006R Chassis Rev:E0 GMT Offset:0 Node Alarm:MAJORCard Front/Back Card Alarm Redundant Redundancy Slot Card State Type Status Slot Type --- ---------- -------- -------- ------- -----

01 Empty --- --- --- --- 02 Active/Active RPM_XF NONE 10 PRIMARY SLOT03 Empty --- --- --- --- 04 Active/Empty RPM_PR NONE NA NO REDUNDANCY05 Empty --- --- --- --- 06 Empty --- --- --- --- 07 Standby/Active PXM45B NONE 08 PRIMARY SLOT08 Active/Active PXM45B NONE 07 SECONDARY SLOT09 Empty --- --- --- --- 10 Standby/Active RPM_XF NONE 00 SECONDARY SLOT11 Active/Empty RPM_XF NONE NA NO REDUNDANCY12 Empty --- --- --- --- 13 Empty --- --- --- --- 14 Empty --- --- --- --- 15 Empty --- --- --- ---

Step 7 To display the redundancy relationship between all cards in the switch, enter the dspred command.

Redundant cards are displayed as shown below, indicating primary and secondary slot numbers, card types, card states, and redundancy type. Observe that the standby card’s front panel CPU OK LED is Yellow.

Unknown.8.PXM.a > dspredUnknown System Rev:03.00 May. 13, 2002 18:57:26 GMTMGX8850 Node Alarm:MAJORLogical Primary Secondary Card Redundancy Slot Slot Card Slot Red Type Type State State ----- ----- ----------- ---- ------------ ------------ ---------- 2 2 Active 10 Standby RPM-XF 1:n 7 7 Standby 8 Active PXM45 1:1 15 15 Empty 16 Empty SRM 1:1 31 31 Empty 32 Empty SRM 1:1

Note The standby card must not have any configurations and must not be configured. Therefore, do not provision the standby card.

Using switchredcd Command to Switch from Active to Standby Card

Enter the switchredcd command to manually change the active card to the standby card. You may want to do this if you need to remove the original active card from the MGX 8850 shelf. Before you begin this procedure, make sure that the destination card is in Standby mode. To change the active cards, follow the steps below. The primary or active card in slot 2 is switched to standby or secondary, and the standby card in slot 10 is switched to primary or active.

Step 1 Enter the switchredcd command.




Unknown.7.PXM.a > switchredcd 2 10switchredcd: Do you want to proceed (Yes/No)? y

The card in slot 10 is now the active RPM-XF card, and the RPM-XF card in slot 2 is reset. It comes up in standby mode after a couple of minutes.

The new active card will not revert to standby mode automatically. Enter switchredcd to manually switch over the active card back to standby mode. This procedure is the only way the active card will switch over to standby, unless the active card fails.

Step 2 Enter the same command to switch the active card back to the original RPM-XF.

Unknown.7.PXM.a > switchredcd 10 2switchredcd: Do you want to proceed (Yes/No)? y

Deleting Redundancy

To delete card redundancy, the primary card must be active, otherwise this command will be rejected.

Step 1 Enter the delred command followed by the primary card’s slot number. For example,

Unknown.8.PXM.a > delred 2

Step 2 After deleting a card redundancy, enter the dspred command to display the redundancy relationship between the remaining redundant cards in the switch, as shown in the following example.

The remaining redundant cards are displayed as shown below, indicating primary and secondary slot numbers, card types, card states, and redundancy type.

Unknown.8.PXM.a > dspredUnknown System Rev:03.00 May. 13, 2002 18:58:45 GMTMGX8850 Node Alarm:MAJORLogical Primary Secondary Card Redundancy Slot Slot Card Slot Red Type Type State State ----- ----- ----------- ---- ------------ ------------ ---------- 7 7 Standby 8 Active PXM45 1:1 15 15 Empty 16 Empty SRM 1:1 31 31 Empty 32 Empty SRM 1:1

Step 3 The secondary card is reset and comes back up as an active normal RPM-XF card (if it is the last primary card) that can be used for any other purpose. Note in the example below that the card in slot 10 is now active.


2 Active or primary card.

10 Standby or secondary card.


10 Active or primary card.

2 Standby or secondary card.




Unknown.8.PXM.a > dspcdsUnknown System Rev:03.00 May. 13, 2002 19:00:33 GMTChassis Serial No: SCA0444006R Chassis Rev:E0 GMT Offset:0 Node Alarm:MAJORCard Front/Back Card Alarm Redundant Redundancy Slot Card State Type Status Slot Type --- ---------- -------- -------- ------- -----

01 Empty --- --- --- --- 02 Active/Active RPM_XF NONE NA NO REDUNDANCY03 Empty --- --- --- --- 04 Active/Empty RPM NONE NA NO REDUNDANCY05 Empty --- --- --- --- 06 Empty --- --- --- --- 07 Standby/Active PXM45B NONE 08 PRIMARY SLOT08 Active/Active PXM45B NONE 07 SECONDARY SLOT09 Empty --- --- --- --- 10 Active/Active RPM_XF NONE NA NO REDUNDANCY11 Active/Empty RPM_XF NONE NA NO REDUNDANCY12 Empty --- --- --- --- 13 Empty --- --- --- --- 14 Empty --- --- --- --- 15 Empty --- --- --- ---

Adding Additional Primary Cards

You can add one or more additional RPM-XF cards as primary cards backed up by the secondary card by entering the addred command as follows.

Switch.7.PXM.a > addred <redPrimarySlotNum> <redSecondarySlotNum> <redType>

Repeat this command for each additional card you want to add to the secondary card backup protection. In the following example, the primary cards in slots 2, 3, and 4 are being backed up by the secondary RPM-XF in slot 10.

Note The secondary card does not get reset when adding additional primary cards to a redundancy group.

switch.7.PXM.a > addred 2 10 2switch.7.PXM.a > addred 3 10 2switch.7.PXM.a > addred 4 10 2

Upgrading Redundant RPM-XF Cards

The following procedure describes how to upgrade redundant RPM-XF cards.

Note Redundancy must be established as described above, before you use this procedure.

Step 1 Copy the new RPM-XF image to the location from which you want to boot the card. (PXM disk or bootflash or tftp server).

Step 2 On the primary/active RPM-XF card, modify the running configuration to boot from the new upgrade software.




Step 3 Enter the write memory or wr mem command to save the configuration.

Step 4 Enter the switchredcd command, as follows, to switch to the secondary card.

switch.7.PXM.a > switchredcd <fromSlot> <toSlot>

This step makes the secondary card active and resets the primary RPM-XF card. When the primary card resets, it loads the upgraded software defined in Step 1.

Step 5 Modify the configuration of the secondary card to boot from the new upgrade software and enter wr mem to save the configuration.

Step 6 Enter the switchredcd command, as follows, to switch to the primary card from the secondary card. This command is entered only after the primary card has booted and is in the standby state.

switch.7.PXM.a > switchredcd <fromSlot> <toSlot>

This step makes the upgraded primary card active and resets the secondary card. When the reset is complete, the secondary card runs the upgrade software and is now in the standby state.

Step 7 Continue this procedure from Step 2 for all remaining cards.

Upgrading Non-redundant RPM-XF Cards

The following procedure describes how to upgrade non-redundant RPM-XF cards.

Step 1 Copy the new RPM-XF image to the location from which you want to boot the card. (PXM disk or bootflash or tftp server).

Step 2 Configure the RPM-XF card to store its configuration on the PXM hard disk by entering the boot config e:auto_config_slot# command, or save it in NVRAM by entering the wr mem (write memory) command.

Step 3 Modify the running configuration to boot from the new upgrade software by entering the boot system command.

Step 4 Enter wr mem to save the configuration.

Step 5 Reset the RPM-XF card by entering the resetcd command from the PXM or the reload command from the RPM-XF.



Chapter 7 Configuring the MGX RPM-XFEnabling IP Accounting Counters

Enabling IP Accounting CountersThe RPM-XF stores packet/byte counters based on precedence/dscp values on a per interface level and are for input values ONLY. The following CLI commands enables this feature:

Command Description

ip accounting ? pop20-slot6(config-if)#ip accounting ?precedence Count packets by IP precedence on

this interfacedscp Count packets by dscp on this

interface

ip accounting precedence ? pop20-slot6(config-if)#ip accounting precedence ?input received packets and bytes

ip accounting dscp ? pop20-slot6(config-if)#ip accounting dscp ?input received packets and bytes

show int [interface] precedence pop20-slot5# show int [interface] precedence

show int [interface] dscp pop20-slot5# show int [interface] dscp

clear counters pop20-slot5#clear counters

C H A P T E R



8Configuring PNNI Communications

This chapter explains how to configure the RPM-XF to operate as an edge router in a PNNI network. When it is operating as a PNNI edge router, you can configure soft permanent virtual circuits (SPVCs) between the RPM-XF and other switch cards. For example, you can configure an SPVC between two RPM-XFs, or between an RPM-XF and an AXSM card. The SPVC can be configured between cards in the same switch, or between cards on two different switches. When the connection endpoints terminate on different switches, PNNI routes and, if necessary, reroutes connections between the endpoints.

This chapter begins with configuration quickstarts that provide overviews of the tasks required to configure RPM-XF SPVC connections. This chapter contains the following sections:

• Configuration Quickstarts

• Configuring PNNI Connections

• Connection Management

• Connection State Alarms

Configuration QuickstartsConfiguration quickstarts are designed as an overview and quick reference for those who have already configured RPM-XF cards. Use these quickstarts as a guide to configuring your RPM-XF card. If you need additional information on any step, look in the “Purpose” column for a reference to detailed documentation.

Switch and RPM-XF Preparation QuickstartThe following quickstart procedure describes tasks that prepare the switch and the RPM-XF to support multiple PNNI connections through RPM-XF. Follow this procedure whenever you configure a new RPM-XF in a switch.



Chapter 8 Configuring PNNI CommunicationsConfiguration Quickstarts

RPM-XF to RPM-XF Connection QuickstartThe following quickstart procedure describes how to configure a PNNI SPVC between two RPM-XF subinterfaces. Figure 8-1 illustrates three types of RPM-XF to RPM-XF connections.

Figure 8-1 RPM-XF-to-RPM-XF Connections

Command Purpose

Step 1 Prompt: Switch.7.PXM.a >

dspcontrollers

addcontroller <cntrlrId> i <cntrlrType> <slot> [cntrlrName]

Verify that a PNNI controller is defined on the PXM45 card and configured correctly. A PNNI controller is defined once for each switch.

See the “Verifying the PNNI Controller Configuration” section later in this chapter.

Adds a controller.

Step 2 Prompt: RPM-XF (config) #

interface switch1switch partition <options>ingress-percentage-bandwidth <options>egress-percentage-bandwidth <options>vpi <options>vci <options>connection-limit <options>

Related commands:

show switch partitions

Assign the switch1 interface resources to the PNNI controller. This procedure must be completed once for each RPM-XF card.

See the “Assigning Link Resources to a PNNI Controller” section later in this chapter.

AX

SM

1

PX

M45

7

PX

M45

8

RP

M-X

F

9

RP

M-X

F

10

AX

SM

PNNI

0/2000Slave

Connection A

0/2001Master

0/200Master

0/200Slave

0/300Slave

0/305Master

1

PX

M45

7

PX

M45

8

RP

M-X

F

9

RP

M-X

F

10

Connection B Connection C

7581

0




Connection endpoints are established on subinterfaces, which are identified by the PVC number in the format VPI/VCI. The subinterfaces can be located on the same RPM-XF card, on different RPM-XF cards within the same switch, or on RPM-XF cards in different switches. You must define the slave end of the connection first, and then the master end.

Connection B is defined between subinterfaces on two different RPM-XF cards in two different switches. Before the connection can operate, the PNNI link between the two switches must be established. Refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide.

Connection A is defined between two subinterfaces on the same RPM-XF; connection C is configured between two subinterfaces that are on different RPM-XF cards in the same switch. When both ends of a connection terminate on the same switch, there is no need for the PNNI trunk shown in Figure 8-1.

RPM-XF Slave to the AXSM Master Connection QuickstartThe following quickstart procedure describes how to configure a PNNI SPVC between an RPM-XF subinterface and an AXSM port. Figure 8-2 illustrates two types of RPM-XF to AXSM connections.

Command Purpose

Step 1 interface Switch 1.xx <options>ip address <options>pvc vpi/vci

At the RPM that will host the slave side of the connection, create and configure a subinterface to host the slave side connection.

See the “Creating and Configuring a Switch Subinterface” section later in this chapter.

Step 2 switch connection <options>

Related commands

show switch connectionshow ip int br

Add the slave end of the new connection to the subinterface PVC.

See the “Creating a Slave Connection on the RPM-XF” section later in this chapter.

Step 3 cc <slot>dspcon <port> <vpi> <vci>

Change to an active PXM45 card and copy or write down the ATM address for the slave endpoint.



At the RPM that will host the master side of the connection, create and configure a subinterface to host the master side connection.



Related commands


Add the master end of the new connection to the subinterface PVC.

See the “Creating a Master Connection on the RPM-XF” section later in this chapter.




Figure 8-2 RPM-XF Slave to AXSM Master Connections

Connection endpoints are established on subinterfaces, which are identified by the PVC number in the format VPI/VCI. The RPM-XF and AXSM cards can be located on the same switch or on different switches. You must define the RPM-XF as the slave end of the connection first, and then you can define the master end of the connection.

Connection B is defined between the RPM-XF and AXSM cards in two different switches. Before the connection can operate, the PNNI link between the two switches must be established. Refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide.

Connection A is defined between the RPM-XF and AXSM cards in the same switch. When both ends of a connection terminate on the same switch, there is no need for the PNNI trunk shown in Figure 8-2.

AX

SM

1P

XM

457

PX

M45

8

RP

M-X

F

9

AX

SM

11

AX

SM

PNNI

0/100Master

Connection A

0/100Slave

0/200Master

0/200Slave

1

PX

M45

7

PX

M45

8

RP

M-X

F

9

Connection B

7578

8

UNI portto CPE

UNI portto CPE

Command Purpose


At the RPM that hosts the slave side of the connection, create and configure a subinterface to host the slave side connection.



Related commands


Add the slave end of the new connection to the subinterface PVC.


Step 3 cc <slot>dspcon <port> <vpi> <vci>

Change to active PXM45 card and copy or write down the ATM address for the slave endpoint.





Step 4 cnfcdsct upln

At the AXSM card that will host the master side of the connection, configure the card and the line, if these components are not configured already.

Refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Chapter 3, “Preparing AXSM Cards and Lines for Communication.”

Step 5 dsppnni-linkdsppnni-node-listdsppnni-nodedsppnni-reachable-addr network

If the RPM-XF card that hosts the slave side of the connection is on a different switch, verify communications between the local and remote switches.

Refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Chapter 5, “Provisioning AXSM Communication Links,” the “Verifying PNNI Communications” section.

Note The dsppnni-link command provides real-time data.For the other dsppnni commands, designate a PNNI topology state element (PTSE) time out.

Step 6 addport addpart

Add an AXSM UNI port to host the master connection and create a PNNI partition for that port.

Refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Chapter 5, “Provisioning AXSM Communication Links,” the “MPLS and PNNI UNI Port Configuration Quickstart” section.

Step 7 addcon <options>

Related commands

dspconsdspcon <port> <vpi> <vci>

Add the master side of the connection to the UNI port.

Refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Chapter 5, “Provisioning AXSM Communication Links,” the “Configuring the Master Side of SPVCs and SPVPs” section.

Command Purpose




AXSM Slave to RPM-XF Master Connection QuickstartThe following quickstart procedure describes how to configure a PNNI SPVC between an RPM-XF subinterface and an AXSM port. Figure 8-3 illustrates two types of RPM-XF to AXSM connections.

Figure 8-3 RPM-XF Master to AXSM Slave Connections

Connection endpoints are established on subinterfaces, which are identified by the PVC number in the format VPI/VCI. The RPM-XF and AXSM cards can be located on the same switch or on different switches. You must define the slave end of the connection first, and then define the master end.

Connection B is defined between RPM-XF and AXSM cards in two different switches. Before the connection can operate, the PNNI link between the two switches must be established. Refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide.

Connection A is defined between RPM-XF and AXSM cards in the same switch. When both ends of a connection terminate on the same switch, there is no need for the PNNI trunk shown in Figure 8-3.

AX

SM

PX

M45

PX

M45

RP

M-X

F

AX

SM

AX

SM

0/100Slave

Connection A

0/100Master

0/200Slave

0/200Master

PX

M45

PX

M45

RP

M-X

F

Connection B

7581

1

UNI portto CPE

UNI portto CPE

PNNI

Command Purpose

Step 1 dnlncnfcdsct upln

At the AXSM card that will host the slave side of the connection, configure the card and the line, if these components have not been configured already.

Refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Chapter 3, “Preparing AXSM Cards and Lines for Communication.”

Step 2 dsppnni-linkdsppnni-node-listdsppnni-nodedsppnni-reachable-addr network

If the RPM-XF card that hosts the master side of the connection is on a different switch, verify communications between the local and remote switches.

Refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Chapter 5, “Provisioning AXSM Communication Links,” the “Verifying PNNI Communications” section.



Chapter 8 Configuring PNNI CommunicationsConfiguring PNNI Connections

Configuring PNNI ConnectionsThe following sections describe the steps listed in the configuration quickstarts.

Verifying the PNNI Controller ConfigurationA PNNI controller must be added to the switch before PNNI can route communications for RPM-XF connections. The PNNI controller is added just once, usually during general switch configuration. To verify that the PNNI controller is added and configured correctly, enter the dspcontrollers command on the PXM45 as shown in the following example.

Step 3 addport addpart

Add an AXSM UNI port to host the slave connection and create a PNNI partition for that port.

Refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Chapter 5, “Provisioning AXSM Communication Links,” the “MPLS and PNNI UNI Port Configuration Quickstart” section.

Step 4 addcon <options>

Related commands

dspconsdspcon <port> <vpi> <vci>

Add the slave side of the connection to the UNI port. Be sure to copy or write down the ATM address for the slave endpoint.

Refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Chapter 5, “Provisioning AXSM Communication Links,” the “Configuring the Slave Side of SPVCs and SPVPs” section.


At the RPM that will host the master side of the connection, create and configure a subinterface to host the master side connection.



Related commands


Add the master end of the new connection to the subinterface PVC.

See the “Creating a Master Connection on the RPM-XF” section later in this chapter.

Command Purpose




Switch.7.PXM.a > dspcontrollersSwitch System Rev: 02.01 Mar. 22, 2001 11:25:29 PSTMGX8850 Node Alarm: CRITICALNumber of Controllers: 1 Controller Name: PNNI Controller Controller Id: 2 Controller Location: Internal Controller Type: PNNI Controller Logical Slot: 7 Controller Bay Number: 0 Controller Line Number: 0 Controller VPI: 0 Controller VCI: 0 Controller In Alarm: NO Controller Error:

The Controller ID, Controller Location, and Controller Type must match the values shown in the example above. The controller name is defined by the person that creates the controller and can be different from what is shown above.

If the dspcontrollers command does not display a PNNI controller, enter the addcontroller command. (Refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide.)

Assigning Link Resources to a PNNI ControllerLink resources must be defined on the RPM-XF before you can create a connection or configure a PNNI. Link resources include the following features.

• Ingress bandwidth

• Egress bandwidth

• Virtual path identifier (VPI) range

• Virtual channel identifier (VCI) range

• Number of connections

The switch partition command is used to add or modify the resource partitioning on the RPM-XF. Enter the switch partition command before you add any connections to the RPM-XF.

Note PAR is not supported.

To assign link resources to a controller, use the following switch partition routine.

Step 1 Enter the switch partition command.

(config-if)# switch partition <partId> <ctrlrId>

Step 2 Enter the ingress-percentage-bandwidth command at the swpart prompt to specify the minimum and maximum ingress percentage bandwidth.


partId Range is 1 to 10.

ctrlrId Range is 2 to 20; 2 is reserved for PNNI.




(config-if-swpart)# ingress-percentage-bandwidth <ingMinPctBw> <ingMaxPctBw>

Step 3 Enter the egress-percentage-bandwidth command to specify the minimum and maximum egress percentage bandwidth.

(config-if-swpart)# egress-percentage-bandwidth <egrMinPctBw> <egrMaxPctBw>

Step 4 Enter the vpi command to specify the minimum and maximum vpi.

(config-if-swpart)# vpi <min_vpi> <max_vpi>

Step 5 Enter the vci command to specify the minimum and maximum vci.

(config-if-swpart)# vci <min_vci> <max_vci>

Step 6 Enter the connection-limit command to specify the minimum and maximum number of connections.

(config-if-swpart)# connection-limit <min_con> <max_con>

The following is an example of the switch partition commands.

Router(config-if)#switch part 1 2 Router(config-if-swpart)#ingress-percentage-bandwidth 1 100Router(config-if-swpart)#egress-percentage-bandwidth 1 100Router(config-if-swpart)#vpi 0 0Router(config-if-swpart)#vci 2000 3000Router(config-if-swpart)#connection-limit 1000 4000

partId = 1 for PNNI.

ctrlrId = 2 for PNNI.

Table 8-1 describes switch partition command parameters.

Table 8-1 Switch Partition Parameter Description


ingress-percent The percentage of the ingress bandwidth on the ATM switch interface that can be allocated by the controller type. The aggregate of the ingress bandwidth across all three controllers can exceed 100 percent.

egress-percent The percentage of the egress bandwidth on the ATM switch interface that can be allocated by the controller type. The aggregate of the egress bandwidth across all three controllers can exceed 100 percent.

min-vpi The minimum VPI value that can be assigned on SPVCs on this controller.

max-vpi The maximum VPI value that can be assigned on SPVCs on this controller.

min-vci The minimum VCI value that can be assigned on SPVCs on this controller.

max-vci The maximum VCI value that can be assigned on SPVCs on this controller.

min-connection-limit

The minimum number of connections that can be added on this controller.

max-connection-limit

The maximum number of connections that can be added on this controller.




VPIs and VCIs

The following list shows how VPI/VCI resources on the RPM-XF can be partitioned among the PNNI controller and two LSCs. The controllers and partitions are the following.

Controllers:

• PNNI Controller—Controller ID 2

• LSC1—Controller ID 3

• LSC2—Controller ID 4

Note LSC controller IDs must match those defined in the addcontroller command. See Chapter 9, “Configuring MPLS Features,” the “Adding an MPLS Controller to the PXM45 and Configuring an RPM-XF LSC” section on page 9-5.

Partitions:

• Partition 1 (Partition ID 5; Interface # 1)—VPI range: 0 to 100; VCI range: 32 to 65535



VPI/VCI ranges cannot overlap between partitions, and a partition can only be used by one controller. The VPI/VCI range can be expanded or reduced as long as the VPI/VCIs are not in use. Existing connections will remain unaffected.

The VPI and VCI partitioning parameters can be configured from CWM or via the CLI command switch partition. Refer to the Cisco MGX 8850 Routing Switch Command Reference for the command syntax and usage.

Bandwidth

Bandwidth is also configured by using the switch partition command. The bandwidth allocated to each controller is managed by the following parameters:

• Minimum bandwidth is the guaranteed minimum bandwidth that will be reserved for use by the controller.

• Maximum bandwidth is the maximum bandwidth that can be used by the controller.

Bandwidth partitioning for the ingress direction and the egress direction are managed separately. As with VPI/VCI resources, the bandwidth partition can be expanded or reduced as long as the resource is not in use.

The bandwidth partitioning parameters can be configured through the switch partition CLI command as shown in this example.

Table 8-2 Partitioning VPI/VCI Resources on the RPM-XF

Partition 1 Partition 2 Partition 3

PNNI Controller X

LSC1 X

LSC2 X




Router(config-if-swpart)#ingress-percentage-bandwidth 1 100Router(config-if-swpart)#egress-percentage-bandwidth 1 100

Number of Connections

The number of connections or connection-limit is also configured by entering the switch partition command. The number of connections or lvcs that each controller can add is managed by the following parameters:

• min-connection-limit is the minimum number of connections reserved for a controller.

• max-connection-limit is the maximum number of connections reserved for a controller.

Bandwidth partitioning for the ingress direction and the egress direction are managed separately. As with VPI/VCI resources, the bandwidth partition can be expanded or reduced as long as the resource is not in use.

The number of connections can be configured through the switch partition CLI command as shown in this example.

Router(config-if-swpart)#connection-limit 100 1000

Resource Partition Provisioning

Use the switch partition routine to set the percentage of ingress and egress bandwidth, as shown in the following procedure. (See the “Assigning Link Resources to a PNNI Controller” section earlier in this chapter.)

Step 1 Enter the following switch partition commands to configure the resource partition and set the percentage of ingress and egress bandwidth on the RPM.

Router(config-if)# switch partition <partId> <ctrlrId>Router(config-if-swpart)# ingress-percentage-bandwidth <ingMinPctBw> <ingMaxPctBw>Router(config-if-swpart)# egress-percentage-bandwidth <egrMinPctBw> <egrMaxPctBw> Router(config-if-swpart)# vpi <min_vpi> <max_vpi>Router(config-if-swpart)# vci <min_vci> <max_vci>Router(config-if-swpart)# connection-limit <min_con> <max_con>

partId = 1 for PNNI

ctrlrId = 2 for PNNI

Step 2 Enter the copy run start command to save the configuration to the RPM’s memory.




Router#config terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#interface switch1Router(config-if)#switch part 1 2 Router(config-if-swpart)#ingress-percentage-bandwidth 1 100Router(config-if-swpart)#egress-percentage-bandwidth 1 100Router(config-if-swpart)#vpi 0 0Router(config-if-swpart)#vci 2000 3000Router(config-if-swpart)#connection-limit 100 1000Router(config-if-swpart)#endRouter#copy run startBuilding configuration...[OK]

Step 3 Enter the show switch partition commands to verify your configuration.

Router#show switch partitionPart Ctrlr Guar Max Guar Max Id Id Ing%Bw Ing%Bw Egr%Bw Egr%Bw minVpi maxVpi minVci maxVci MaxCons1 2 1 100 1 100 0 0 2000 3000 1001

Router#show switch partition vcc 1-------------------------------------------------------Shelf : 1Pxm Slot : 7Slot : 9IfType : 3IfNum : 1Partition ID : 1Controller ID : 2Guaranteed Ingress Pct BW: 1Max Ingress Pct BW : 100Guaranteed Egress Pct BW : 1Max Egress Pct BW : 100VPI Low : 0VPI High : 0VCI Low : 2000VCI High : 3000Maximum # of Connections : 1001

Configuring Switch Interface SignalingThe procedure in this section describes how to configure the signaling for the switch interface so it can support PNNI connections. This configuration is performed on the PXM45 card.

On the PXM45 card, the switch interface appears as a PNNI port, as shown in the following procedure.

Step 1 Enter the dsppnports command to determine which PNNI ports represent RPM-XF switch interfaces.




Switch.7.PXM.a > dsppnportsSummary of total connections(p2p=point to point,p2mp=point to multipoint,SpvcD=DAX spvc,SpvcR=Routed spvc)Type #Svcc: #Svpc: #SpvcD: #SpvpD: #SpvcR: #SpvpR: #Total:p2p: 0 0 3 0 0 0 3 p2mp: 0 0 0 0 0 0 0 Total=3 Summary of total configured SPVC endpointsType #SpvcCfg: #SpvpCfg:p2p: 7 0 p2mp: 0 0

Per-port status summary

PortId IF status Admin status ILMI state #Conns

7.35 up up Undefined 0




Type <CR> to continue, Q<CR> to stop:

9.1.2.2 up up Undefined 4

1:1.1:1 provisioning up Undefined 0

1:1.2:2 down up Undefined 0

2:1.1:1 up up Disable 1

2:2.1:1 provisioning down Undefined 0

2:2.2:2 provisioning down Undefined 0

3:2.1:5 up up UpAndNormal 1

3:2.2:4 building vc up Disable 0

In the example above, port 9.1.2.2 represents an RPM-XF switch interface.

Step 2 To display the port signaling type, enter the dsppnportsig command.

Switch.7.PXM.a > dsppnportsig 9.1.2.2

provisioned IF-type: uni version: uni3.1 sigType: private side: network addrPlan: aesa sigVpi: 0 sigVci: 5rccVpi: n/a rccVci: n/a

The provisioned IF-type field in the example above indicates this port is a UNI port, and the version field indicates the signaling is configured to the default value, uni3.1. The correct value for a PNNI RPM-XF port is none. If the signaling is configured correctly, the dsppnportsig command displays the following information.




Switch.7.PXM.a > dsppnportsig 9.1.2.2

provisioned IF-type: uni version: none sigType: private side: network addrPlan: aesa sigVpi: 0 sigVci: 5rccVpi: n/a rccVci: n/a

Step 3 If you need to change the port signaling configuration, enter the dnpnport command to bring down the port on which you want to configure signaling. For example,

Switch.7.PXM.a > dnpnport 9.1.2.2

Step 4 Configure the RPM-XF port UNI signaling to self by entering the cnfpnportsig command.

Switch.7.PXM.a > cnfpnportsig <portid> -univer none

Replace portid with the port number as shown in the following example:

Switch.7.PXM.a > cnfpnportsig 9.1.2.2 -univer none

Step 5 Bring up the port you just configured with the uppnport command. For example,

Switch.7.PXM.a > uppnport 9.1.2.2

Step 6 To verify the configuration change, reenter the dsppnportsig command.

Creating and Configuring a Switch SubinterfaceThe switch interface on the RPM-XF does not directly support connection endpoints. Before you can create a connection endpoint, you must define a switch subinterface and define a PVC on that interface. The connection endpoint is configured using the VPI and VCI of the PVC.

Some subinterfaces support multiple PVCs (multipoint) that do the equivalent of broadcasting. Others support only one PVC (point-to-point). If a point-to-multipoint PVC exists, then that PVC can be used as the sole broadcast PVC for all multicast requests.

Each subinterface is identified using the notation interface switch 1.<subinterface>. The interface switch 1is the switch interface number, which is always 1, and the <subinterface> is a number that identifies the subinterface. You can choose the subinterface number when you create the subinterface. The subinterface number has to be unique on the RPM-XF card, but it does not have to match any other number.

To create a switch subinterface, configure the following features, as described in the procedure below:

• IP address for the subinterface

• PVC for the subinterface

• PVC configuration parameters

Step 1 To create the subinterface, enter the interface command.

Router(config)# interface switch 1.<subinterface> <multipoint | point-to-point | mpls | tag-switching>

The following example adds subinterface 1 to the switch 1 interface and defines the subinterface as a point-to-point connection.




Router(config)#interface switch 1.1 point-to-point

Step 2 Enter the ip command to add an IP address to the subinterface.

Router(config-subif)# ip address <ip_addr> <subnet_mask>

The following example adds IP address 1.1.1.1 to subinterface 1 and defines the network mask as 255.255.255.0

Router(config-subif)#ip address 1.1.1.1 255.255.255.0

Note The IP addresses for the subinterfaces at the slave and master ends of a connection should share the same subnet.

Step 3 Enter the pvc command to add a PVC to the subinterface.

Router(config-subif)# pvc <vpi>/<vci>

The following example creates a PVC on the subinterface and assigns it VPI 0 and VCI 2000.

Router(config-subif)#pvc 0/2000

After you enter this command, the switch enters virtual circuit configuration mode for this PVC.

Note The VPI and VCI values you enter for the PVC must be within the ranges set for the PNNI controller when the PNNI partition was defined for the switch interface. For more information, see the “Assigning Link Resources to a PNNI Controller” section earlier in this chapter.

Step 4 Enter a question mark to list the commands that you can use to configure the PVC.




Router(config-if-atm-vc)#?ATM virtual circuit configuration commands: atm atm pvc commands broadcast Pseudo-broadcast class-vc Configure default vc-class name default Set a command to its defaults dialer set dialer pool this pvc belongs to encapsulation Select ATM Encapsulation for VC exit-vc Exit from ATM VC configuration mode ilmi Configure ILMI management inarp Change the inverse arp timer on the PVC ip addr inarp Assign an ip address to the atm interface through ATMInarp max-reserved-bandwidth Maximum Reservable Bandwidth on a vc no Negate a command or set its defaults oam Configure oam parameters oam-pvc Send oam cells on this pvc pppoe PPPoE options pppoe-client pppoe client protocol Map an upper layer protocol to this connection. random-detect Configure WRED service-policy Attach a policy-map to a VC transmit-priority set the transmit priority for this VC tx-ring-limit Configure PA level transmit ring limit ubr Enter Unspecified Peak Cell Rate (pcr) in Kbps. vbr-nrt Enter Variable Bit Rate (pcr)(scr)(bcs) vbr-rt Enter Variable Bit Rate (pcr)(average) vc-hold-queue Configure hold queue size vcci VCC Identifier

The following example shows some commands you might want to use to configure the PVC.

Router(config-if-atm-vc)#oam-pvc manageRouter(config-if-atm-vc)#encapsulation aal5snap

Step 5 When you have finished configuring the PVC, enter the exit-vc command to return to subinterface configuration mode.

Router(config-if-atm-vc)#exit-vcRouter(config-subif)#

Creating a Slave Connection on the RPM-XFWhen you create a slave connection on an RPM-XF card, that connection endpoint does not route or reroute connections. Connection routing is the responsibility of the master connection endpoint.

To perform routing and rerouting, the master connection endpoint requires the ATM address of the slave endpoint, so the slave endpoint must be defined first. The following procedure describes how to create a slave connection endpoint.

Note You must configure both the slave and master connection endpoints before the connection can operate.

If you have not already done so, create a subinterface and PVC to host the slave connection endpoint. See the “Creating and Configuring a Switch Subinterface” section earlier in this chapter.

Step 1 If the switch is not in subinterface configuration mode, change to that mode.




Router>enablePassword: Router#configure terminal Enter configuration commands, one per line. End with CNTL/Z.Router(config)#interface switch 1.1Router(config-subif)#

Step 2 To create a VCC, define the slave connection endpoint with the switch connection command as follows:

Router(config-subif)# switch connection vcc <localVPI> <localVCI> master remote

The VPI and VCI that you enter must match the VPI and VCI you used when you configured the PVC that hosts this connection. The following example creates a slave connection for the PVC labeled VPI 0, VCI 2000.

Router(config-subif)#switch connection vcc 0 2000 master remote

Step 3 To create a VPC, define the slave connection endpoint with the switch connection command as follows:

Router(config-subif)# switch connection vpc <localVPI> master remote

The VPI that you enter must match the VPI you used when you configured the PVC that hosts this connection.

You must also add the atm pvp tunnel using the same VPI, before adding the PVC, as follows:

Router(config-subif)# atm pvp <vpi> <PCR>

After you create the slave connection endpoint, the RPM-XF enters switch connection configuration mode. The following prompt displays:

Router(config-if-swconn)#

Step 4 To display a list of configuration commands, enter a question mark at the switch connection prompt. For example,

Router(config-if-swconn)#?Switch connection configuration commands: auto_synch enable auto synch cost Maximum connection cost default Set a command to its defaults exit-swconn Exit from switch connection configuration mode no Negate a command or set its defaults priority Routing Priority reroute reroute the connection rmbs remote MBS value rpcr remote PCR value rscr remote SCR value rutil Connection remote percent utilization shutdown down the connection util Connection local percent utilization

Step 5 Configure the switch connection using the switch connection configuration commands.

Note Local traffic parameters of an RPM endpoint are in kilobits per second (kbps) while remote traffic parameters are in cells per second (cps). 2824661 cells per second equal 1197656 kilobits per second.

Step 6 Press Ctrl-Z to exit configuration mode. Then save your configuration change.




Router(config-subif)#^ZRouter#copy run startBuilding configuration...[OK]

Step 7 Enter the show switch connection command to view the slave endpoint connection. For example,

Router#show switch connection SynchlVpi lVci NSAP Address rVpi rVci Status

0 2000 default 0 0 inSynch:

Step 8 Enter the show ip interface brief command to view the IP interfaces on the RPM-XF.

Router#show ip int brInterface IP-Address OK? Method Status ProtocolFastEthernet1/1 172.29.52.3 YES manual administratively down down Switch1 unassigned YES NVRAM up up Switch1.1 1.1.1.1 YES manual up up

Step 9 To enable IP communications over the slave connection endpoint, configure the router for IP routing.

The ATM connection acts as an intermediate IP network between the IP routers connected at the master and slave endpoints.

Before you can configure a master endpoint, you must locate and note the ATM address for this interface.


lVpi Represents the local VPI you specified when creating the connection.

lVci Represents the local VCI you specified when creating the connection.

NSAP Address Displays default as the address, identifying the connection endpoint as a slave endpoint. Master connection endpoints display an ATM address.

rVpi Represents the remote VPI. A zero (0) value designates that it is a slave endpoint.

rVci Represents the remote VCI. A zero (0) value designates that it is a slave endpoint.




Step 10 To display the ATM address assigned to the slave connection, switch to the active PXM45 card and enter the dspcon command to display connection information. For example,

Router#cc 7

(session redirected)

Switch.7.PXM.a > dspcon 9.1.2.2 0 2000Port Vpi Vci Owner State -------------------------------------------------------------------------Local 9:-1.1:-1 0.2000 SLAVE FAIL Address: 47.00918100000000036b5e2bb2.000001074b01.00Remote Routed 0.0 MASTER -- Address: 00.000000000000000000000000.000000000000.00

-------------------- Provisioning Parameters -------------------- Connection Type: VCC Cast Type: Point-to-Point Service Category: UBR Conformance: UBR.1 Bearer Class: BCOB-X Last Fail Cause: N/A Attempts: 0Continuity Check: Disabled Frame Discard: Disabled L-Utils: 0 R-Utils: 0 Max Cost: 0 Routing Cost: 0OAM Segment Ep: Enabled

---------- Traffic Parameters ----------Tx PCR: 353208 Rx PCR: 353208 Tx CDV: N/A Rx CDV: N/A Tx CTD: N/A Rx CTD: N/A

The slave endpoint ATM address appears below the Local port identification. This is the address you need to enter when you create a master connection endpoint at either an RPM-XF card or an AXSM card. The connection state is FAIL because the master endpoint has not been created.

Step 11 Copy or write down the slave endpoint ATM address for later use. (See the “Creating a Master Connection on the RPM-XF” section below.)

You are now ready to create the master endpoint on either an RPM-XF card or an AXSM card.

Creating a Master Connection on the RPM-XFWhen creating a master connection on an RPM-XF card, that connection endpoint is responsible for routing and rerouting connections. Before you can create the master endpoint, you must create a slave endpoint on either an RPM-XF or AXSM card. The following procedure describes how to create a master endpoint.

If you have not done so already, create a subinterface and PVC to host the master connection endpoint. See the “Creating and Configuring a Switch Subinterface” section earlier in this chapter.

Note The master and slave endpoints can be on the same RPM-XF card as shown in the following example. This example configuration can be used for testing and configuration practice. However, it has no practical application because you can still configure the RPM-XF to route between two Ethernet interfaces. If you do configure master and slave endpoints on the same RPM-XF card, each endpoint must use a different subinterface.




Step 1 Enter subinterface configuration mode. The following example shows how to do this from the user exec mode:

Router>enablePassword: Router#configure terminal Enter configuration commands, one per line. End with CNTL/Z.Router(config)#interface switch 1.2 point-to-pointRouter(config-subif)#

Note When configuring the subinterface, you must specify point-to-point or p, mu, tag or mpls.

Step 2 To create a VCC, enter the switch connection command to define the master connection endpoint.

Router(config-subif)# switch connection vcc <localVPI> <localVCI> master local raddr <ATMaddr> <remoteVPI> <remoteVCI>

The local VPI and VCI that you enter must match the VPI and VCI you used when you configured the PVC that hosts this connection. The ATM address is the address you copied or wrote down when you created the slave endpoint, and the remote VPI and VCI must match the values set for the slave endpoint. (See the “Creating a Slave Connection on the RPM-XF” section above.)

The following example creates a master connection for the PVC labeled VPI 0, VCI 2000:

Router(config-subif)#switch connection vcc 0 2001 master local raddr 47.00918100000000036b5e2bb2.000001074b01.00 0 2000

Step 3 To create a VPC, enter the switch connection command to define the master connection endpoint.

Router(config-subif)# switch connection vpc <localVPI> master local raddr <ATMaddr> <remoteVPI>

The VPI that you enter must match the VPI used to configure the PVC and the atm PVP that hosts this connection.

After you create the master connection endpoint, the RPM-XF enters the switch connection configuration mode and displays the following prompt:




Router(config-if-swconn)#

Step 4 To display a list of configuration commands, enter a question mark at the switch connection prompt.

Router(config-if-swconn)#?Switch connection configuration commands: auto_synch enable auto synch cost Maximum connection cost default Set a command to its defaults exit-swconn Exit from switch connection configuration mode no Negate a command or set its defaults priority Routing Priority reroute reroute the connection rmbs remote MBS value rpcr remote PCR value rscr remote SCR value rutil Connection remote percent utilization shutdown down the connection util Connection local percent utilization

Step 5 Configure the switch connection using the switch connection configuration commands.

Note Local traffic parameters of an RPM endpoint are in kilobits per second (kbps) while remote traffic parameters are in cells per second (cps). (353208 cps equal 149760 kbps.)

Step 6 Press Ctrl-Z to exit configuration mode and then save your configuration change.

Router(config-subif)#^ZRouter#copy run startBuilding configuration...[OK]

Step 7 Enter the show switch connection command to view the master endpoint connection.

Router#show switch connection SynchlVpi lVci NSAP Address rVpi rVci Status

0 2000 default 0 0 inSynch 0 2001 47.0091.8100.0000.0003.6b5e.2bb2.0000.0107.4b01.00 0 2000 inSynch

In the example above, both master and slave endpoints are on the same RPM-XF card, so both appear in the connection display. If the master and slave endpoints were on different switches, the display would show only an entry for the local endpoint. If the local endpoint is the master endpoint, the slave ATM address is shown.


lVpi Represents the local VPI you specified when creating the connection.

lVci Represents the local VCI you specified when creating the connection.

NSAP Address Displays default as the address, identifying the connection endpoint as a slave endpoint. Master connection endpoints display an ATM address.

rVpi Represents the remote VPI. A zero (0) value designates that it is a slave endpoint.

rVci Represents the remote VCI. A zero (0) value designates that it is a slave endpoint.




Step 8 To verify that the new connection is operating properly, switch to the active PXM45 card and enter the dspcon command to display connection information.

Switch.7.PXM.a > dspcon 9.1.2.2 0 2001Port Vpi Vci Owner State -------------------------------------------------------------------------Local 9:-1.1:-1 0.2001 MASTER OK Address: 47.00918100000000036b5e2bb2.000001074b01.00Remote 9:-1.1:-1 0.2000 SLAVE OK Address: 47.00918100000000036b5e2bb2.000001074b01.00

-------------------- Provisioning Parameters -------------------- Connection Type: VCC Cast Type: Point-to-Point Service Category: UBR Conformance: UBR.1 Bearer Class: BCOB-X Last Fail Cause: No Fail Attempts: 0Continuity Check: Disabled Frame Discard: Disabled L-Utils: 100 R-Utils: 100 Max Cost: -1 Routing Cost: 0OAM Segment Ep: Enabled

---------- Traffic Parameters ----------Tx PCR: 353208 Rx PCR: 353208 Tx CDV: N/A Rx CDV: N/A Tx CTD: N/A Rx CTD: N/A

Note that the ATM addresses for both ends of the connection are displayed. The connection state is OK. The connection configuration is complete.

Step 9 To view the IP interfaces on the RPM-XF, switch back to the RPM-XF card and enter the show ip interface brief command.

Switch.7.PXM.a > cc 9

(session redirected)

Router>enablePassword: Router#show ip int brInterface IP-Address OK? Method Status ProtocolFastEthernet1/1 172.29.52.3 YES manual administratively down down Switch1 unassigned YES NVRAM up up Switch1.1 1.1.1.1 YES manual up up Switch1.2 1.1.2.1 YES manual up up

Step 10 To validate that a local connection is operating correctly, ping the local IP address.

Router#ping 1.1.2.1

Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 1.1.2.1, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

To enable IP communications over the master connection endpoint, configure the router for IP routing. The ATM connection will act as an intermediate IP network between the IP routers connected at the master and slave endpoints.

To validate communications to remote devices at the connection endpoints, ping devices on those networks. For example, ping a device connected to an RPM-XF interface, or ping an IP address on the ATM end station connected to an AXSM port.



Chapter 8 Configuring PNNI CommunicationsConnection Management

Connection ManagementThis section describes connection management tasks for the RPM-XF.

Deleting a ConnectionTo delete a connection, you must delete both ends of the connection. The connection stops working when you delete either end, but you must delete both ends to remove the entire connection configuration.

To delete a connection endpoint on an RPM-XF card, enter the no form of the switch connection command.

(config-if)# no switch connection vcc <localVPI> <localVCI> master <local | remote> [raddr <remoteNsapAddress> <remoteVPI> <remoteVCI>]

For example:

Router(config-subif)# no switch connection vcc 0 2000 master remote

To delete a connection endpoint on an AXSM card, refer to the Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide, Chapter 5, “Provisioning AXSM Communication Links,” the “Deleting SPVCs and SPVPs” section.

Modifying Traffic ParametersThe following traffic connection parameters can be modified:

• Service Type

• PCR/SCR/MBS

• Connection Cost

• Channel Utilization

• Encapsulation Type

• Virtual Template ID

• Inarp Timer

• OAM Loopback Frequency

• Enable/Disable OAM Management

• OAM Retry Up Count/Down Count Interval

• Routing Priority

There is a limitation on the changing of the service type. Although the service type can be modified using the Cisco IOS CLI on the RPM-XF, the new service type is not effective in PNNI. PNNI does not support the changing of the service type. The service type cannot be modified via Cisco WAN Manager (CWM).

Changes to the PCR/MCR/SCR, Connection Cost, and Channel Utilization parameters result in connection reroutes, while changes to the remaining parameters result in database updates.

Enter the switch connection command to modify an existing connection that terminates on an RPM-XF.



Chapter 8 Configuring PNNI CommunicationsConnection Management

Downing and Upping the ConnectionA connection that terminates on an RPM-XF can be manually downed and upped. When a connection is down, its respective PNNI will be derouted and will remain derouted until the connection is upped again by the user. The master endpoint will attempt to reestablish the PNNI when the connection is upped.

Enter the shutdown command at the swconn configuration level to down a connection.

Router(config-subif-swconn)#shutdown

Enter the no shutdown command at the swconn configuration level to up a connection.

Router(config-subif-swconn)#no shutdown

Rerouting the ConnectionA connection that terminates on an RPM-XF can be manually released and rerouted. Enter the reroute command and the respective SPVC will be released and automatically rerouted to the best available path.

Enter the reroute command at the swconn configuration level.

Router(config-subif-swconn)#reroute

Connection SynchronizationRPM-XF connection management data base synchronization refers to the synchronization between the RPM-XF and the PNNI database and is built from the IOS config file. The persistence of connection database on the RPM-XF card across card resets depends upon the user’s execution of the write mem command on the RPM-XF card. Due to this, there is a possibility that the RPM-XF connection data base is out of synch with the PNNI connection database.

A connection can be in the following synch states:

• inSynch—The SPVC parameter values at the RPM-XF card match with the values at the PNNI controller. The connection is programmed in the RPM-XF hardware.

• mismatch—There is a mismatch in the SPVC parameter values between the RPM-XF and the PNNI controller’s database. However the connection is programmed in the RPM-XF hardware.

Delete and re-add or simply modify the connection with the correct parameters.

• onlyOnRpm —Connection exists only in RPM-XF database but does not exist in the PNNI controller’s database on the PXM. The connection is not programmed in the RPM-XF hardware.

Delete and re-add the connection.

• notOnRpm—Connection does not exist in the RPM-XF database but it exists in the PNNI controller’s database on the PXM. However the connection is programmed on the RPM-XF hardware.

Delete and re-add the connection.

• onlyOnRpm (NoRsrc)—Connection exists on both the RPM-XF database and on the PNNI controller’s database, but cannot be programmed on the RPM-XF hardware because of insufficient resources in the resource partition (for example, number of connections or bandwidth).

Modify the resource partition for the PNNI controller to adjust the connection-limit or ingress/egress bandwidth.



Chapter 8 Configuring PNNI CommunicationsConnection State Alarms

• notOnRpm (NoRsrc)—Connection does not exist on the RPM-XF database, but exists on the PNNI controller’s database. Connection can not be programmed on the RPM-XF hardware because of insufficient resources in the RPM-XF partition (for example, VPI/VCI).

Modify the resource partition for the PNNI controller to adjust the VPI or VCI ranges and then readd the connection.

Manually Resynchronizing Connections

You can manually resynchronize connections. However, out of synchronization conditions may be triggered by

• Periodic kickoffs

• Individual connection provisioning

• RPM reset

You can force resynchronization by entering the start_resynch command at the configure interface level.

Router# config terminalRouter(config)# interface sw1Router(config-if)#switch start_resynch

Automatically Resynchronizing Connections

The auto_synch command corrects mismatches between the PXM and RPM databases. If your network is highly unstable, do not turn on auto_synch.

The commands that are used to enable and disable the auto_synch feature are moved under the new switch command. Here is an example of how you use this command on the config level.

Router# conf tRouter(config)# int sw1Router(config-if)#switch auto_synch on <off|manual> “default is off”

Connection State AlarmsThis section describes the alarm state of each PNNI, how alarms occur, and what they mean.

Endpoint status indicators reported by RPM-XF and their meanings include:

• egrAisRdi—The endpoint is receiving AIS or RDI cells in the egress direction (from the network).

• oamLpbkFail—An OAM loopback failure has occurred.

• mismatch—There is a mismatch between the RPM-XF and PNNI controller’s connection database.

• conditioned—There is a routing failure.

• onlyOnRpm—The connection exists only on the RPM-XF card.

These alarms are triggered when

• There is a change in the endpoint status.

• A failure is detected by the Connection Manager during a routine routing status check.



Chapter 8 Configuring PNNI CommunicationsConnection State Alarms

C H A P T E R



9Configuring MPLS Features

This chapter describes Multiprotocol Label Switching (MPLS) and features such as Virtual Private Network (VPN) used with the Route Processor Module (RPM-XF) in the MGX 8850 and covers the following topics:

• MPLS Overview

• Configuring MPLS for MGX 8850

• VPN Overview

• How VPNs Work

• Configuring a VPN

• Multicast VPN

• MPLS LDP

• Support for Multi-VC on the RPM-XF

This chapter focuses on configuring the RPM-XF MPLS features for the Edge Label Switch Router (ELSR) and Label Switch Controller (LSC) on the MGX 8850 Release 3 shelf.

For information on MPLS, refer to the Cisco MPLS Controller Software Configuration Guide. For MPLS and VPN commands, refer to the Cisco MPLS VPN Feature Guide.

MPLS OverviewThis section describes MPLS and the role of the RPM-XF as an ELSR and LSC within the MGX 8850 switch.

The labels used to forward packets are negotiated using Label Distribution Protocol (LDP) or Tag Distribution Protocol (TDP). In this context, the RPM-XF functions as an Edge LSR to receive and label IP packets. In ATM cell-based mode, RPM-XF can also function as the LSC, which controls label distribution in the MPLS network. However, an RPM-XF card cannot function as both an ELSR and LSC simultaneously.

There are two different modes of MPLS operation.

• Packet-based

• ATM cell-based.



Chapter 9 Configuring MPLS FeaturesMPLS Overview

The RPM-XF GigE or POS packet-based MPLS operations and configurations are similar to any IOS router packet-based MPLS operations and configurations. The PVC packet-based MPLS configurations are similar to RPM-PR configurations. This chapter mainly focuses on ATM cell-based MPLS operations, with some focus on the packet-based MPLS with the RPM-XF.

ATM MPLSMPLS combines the performance and virtual circuit capabilities of Layer 2 (data link layer) switching with the scalability of Layer 3 (network layer) routing capabilities. This combination enables service providers to deliver solutions for managing growth and provide a variety of services, while leveraging existing networking infrastructures.

MGX 8850 supports the Label Switch Controller (LSC) function that enables you to set up LVCs directly on ATM interfaces within an ATM switch. The LVCs are established under the direct control of MPLS signaling, and each LVC corresponds to a distinct MPLS label value.

The RPM-XF supports MPLS VPNs. In MPLS VPN operation, the RPM-XF will act as a Provider Edge (PE) router. PE router function is a combination of the MPLS Edge LSR function and the use of the Border Gateway Protocol (BGP) v4 with Multiprotocol Extensions to carry routing information for the VPNs.

MPLS in the MGX 8850 Switch

On the MGX 8850 platform, MPLS provides an IP solution without the cost of Layer 2 management. In contrast to IP over ATM, MPLS reduces the customer’s network management and operational costs. N provides the same level of privacy as does Frame Relay or ATM.

For a description of how the RPM-XF acts as an Edge LSR to support MPLS feeder functionality in the MGX 8850, see the ““System Block Diagram” section on page 9-3.

Features

The RPM-XF supports the following features:

• MPLS Applications

– MPLS VPN

– MPLS COS with Multi-VC

• Edge LSR functionality in the RPM-XF on the MGX 8850 shelf.

– ATM cell-based MPLS on regular and PVP (VP tunnel) LC-ATM interfaces

– PVC packet-based MPLS

Note RPM-XF switch interface can support 2000 PVCs, 4000 LVCs, and 240 PVPs.

• LSC functionality in the RPM-XF on the MGX 8850 shelf.

– Regular XtagATM interfaces

– VP tunnel based XtagATM interfaces

– MPLS COS on the LSC

Note Using LSC and ELSR on the same RPM-XF is not supported.

Note RPM-XF ELSR does not support LSC redundancy.



Chapter 9 Configuring MPLS FeaturesMPLS Overview

• MPLS on the RPM-XF Gigabit Ethernet (MGX-1GE).

• MPLS on the OC-12 Packet Over SONET (MGX-1OC12POS-IR).

• Protocol supported:

– OSPF

– IS-IS

– MPLS LDP

– BGP (VPN addition provided by BGP, RIPv2, OSPF, and static routes for PE–CE links.)

Note RPM-XF can support up to 2000 Interface Descriptor Blocks (IDBs).

• 1:N redundancy based on RPM-XF changeovers.

System Block Diagram

In the system block diagram (see Figure 9-1), one common configuration is shown for cell-based MPLS deploying RPM-XF as an ELSR and LSC. The figure depicts two MGX 8850 (Release 3) nodes, each having an RPM-XF LSC and an RPM-XF ELSR. The following section shows a sample configuration for the RPM-XF LSC and RPM-XF ELSR in the MGX 8850 (Release 3) on the right.

Note Interoperability between the RPM-XF LSC/ELSR in an MGX 8850 (Release 3) node and an RPM-PR ELSR in an MGX 8850 (Release 1) is also supported. Refer to the Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide for details.



Chapter 9 Configuring MPLS FeaturesConfiguring MPLS for MGX 8850

Figure 9-1 MGX 8850s with ELSR and LSC Configured RPM-XF

MPLS Class of Service SupportThis section discusses the mapping of the MPLS Class of Service (CoS) to the service class templates (SCT). SCTs are used on AXSM cards to provide configurability of default VC and Quality of Service (QoS) parameters. SCTs are not supported on RPM-XF. RPM-XF uses a fixed set of default VC and QoS parameters.

Service class templates 4 or 5 need to be configured on AXSM cards and service class template 5 needs to be configured on AXSM-E cards before you can configure the MGX 8850 for MPLS support.

Note RPM-XF follows a set of unchangeable default VC parameters and QoS settings for MPLS and PNNI service types and therefore does not require an SCT.

Configuring MPLS for MGX 8850This section describes procedures needed to configure the RPM-XF, the PXM45, and AXSM cards to support MPLS on MGX 8850 switches.

To support MPLS, you need to

• Add an MPLS controller to the PXM45 for an RPM-XF LSC.

• Configure an RPM-XF as the LSC.

ELSR

RPM-XF

PXM

Unlabeled traffic

AXSM

Slave

Slave

AXSM

Slave

PXM

LSC-BRPM-XF

SlaveLVC

LDP

LDP LDP

AXSM

MasterLSC

RPM-XF

Master

AXSM

Unlabeled trafficLabeled traffic

MGX 8850 (Release 3) MGX 8850 (Release 3)

7554

0

ELSR-B

RPM-XF




• Add and partition an AXSM port for MPLS.

• Configure an RPM-XF as the ELSR.

• Map the AXSM port and the RPM-XF ELSR port to XTagAtm interfaces on the LSC.

• Configure an RPM-XF to perform basic LSC operations. For more information, refer to: http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftlsc.htm#xtocid20

• Configure an RPM-XF LSC network configuration to connect to Cisco BPX Switches. For more information, refer to: http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftlsc.htm#95055

• Configure simple PVC-Based Packet MPLS network configurations. For more information, refer to: http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftlsc.htm#xtocid26

Adding an MPLS Controller to the PXM45 and Configuring an RPM-XF LSCThe first task in establishing MPLS services with an RPM-XF LSC (LSC-B in Figure 9-1) is to add an MPLS controller on the PXM45. This is similar to adding the PNNI controller to the PXM45. (See Chapter 6.) To add the MPLS controller, follow these steps.

Step 1 Access the switch CLI and enter the addcontroller command.

MGX8850.7.PXM.a>addcontroller <cntrlrId> i <cntrlrType> <slot> [cntrlrName]

For example,

MGX8850.7.PXM.a>addcontroller 5 i 3 5 LSC-5

Step 2 Enter the cc command, cc 5, to change to the RPM-XF card.


cntrlrId Range is from 1 through 20. 1 is reserved for PAR, 2 is reserved for PNNI, and 3 is reserved for LSC.

i Internal

cntrlrType 1 is reserved for PAR, 2 is reserved for PNNI, and 3 is reserved for LSC.

slot RPM-XF LSC slot, 1– 6 and 9 – 14.

cntrlrName An optional field that specifies the name of the controller.


cntrlrId 5

i i = internal

cntrlrType 3 = LSC

slot 5 = RPM-XF LSC inserted in slot 5.

cntrlrName LSC-5




Step 3 Enter the commands shown in the following example to configure the RPM-XF as an LSC.

RPM-XF>enablePassword: RPM-XF#config terminalEnter configuration commands, one per line. End with CNTL/Z.RPM-XF(config)#interface loopback0RPM-XF(config-if)#ip address 28.28.28.28 255.255.255.255RPM-XF(config-if)#interface switch1RPM-XF(config-if)#no ip addressRPM-XF(config-if)#label-control-protocol vsi id 5RPM-XF(config-if)#switch partition 5 5RPM-XF(config-if-swpart)#ingress-percentage-bandwidth 10 100RPM-XF(config-if-swpart)#egress-percentage-bandwidth 10 100RPM-XF(config-if-swpart)#vpi 0 50 RPM-XF(config-if-swpart)#vci 32 10000RPM-XF(config-if-swpart)#connection-limit 1 10000

Note The VSI Controller ID must match the addcontroller command ID entered in the previous step.

Adding and Partitioning an AXSM NNI Port for MPLSNext, follow these steps to add and then partition a NNI port on an AXSM card for MPLS.

Step 1 Enter the cc command to change to an AXSM card.

MGX8850.7.a>cc 1

Step 2 Enter the cnfcdsct command as shown in the following example, to configure the AXSM card service class template (SCT) for PNNI and MPLS.

MGX8850.1.AXSM.a>cnfcdsct 4

Note 4 = policing on and 5 = policing off (for ATM Forum service types)

Step 3 Enter the upln command to bring up the desired line.

MGX8850.1.AXSM.a>upln 1.1

Step 4 Enter the addport command to add the port.

addport <ifNum> <bay.line> <guaranteedRate> <maxRate> <sctID> <ifType> [vpiNum]


ifNum A number between 1 and 60.

bay.line Port location designating back card bay; 1 for top and 2 for bottom. line is back card specific.

guaranteedRate Virtual rates in cells per second.




For example,

MGX8850.1.AXSM.a>addport 1 1.1 353207 353207 4 0

Step 5 Enter the addpart command to partition the port you have just added.

addpart <ifNum> <partId> < cntlrId> <egrminbw> <egrmaxbw> <ingminbw> <ingmaxbw> <minVpi> <maxVpi> <minVci> <maxVci> <minConns> <maxConns>

For example,

MGX8850.1.AXSM.a>addpart 1 2 5 500000 500000 500000 500000 0 1500 32 65535 4000 4000

maxRate Maximum rate depends on connection, as follows:

OC48—between 50 and 5651320



T3—between 50 and 96000(PLCP), 104268(ADM)

E3—between 50 and 80000

sctID Port SCT ID, between 0 and 255. For default file use 0. For MPLS, use 4 or 5.

ifType 1 for uni; 2 for nni; 3 for vnni

vpiNum Used for configuring interface as virtual trunk, between 1 and 4095.



ifNum A number between 1 and 60.

partId Partition identifier; a number from 1 through 5.

cntlrId Controller identifier; a number from 1 through 20. 1 is reserved for PAR, 2 is reserved for PNNI, and 3 is reserved for LSC.

egrminbw Egress guaranteed% bandwidth in units of 0.0001% of interface bandwidth.

egrmaxbw Egress maximum % bandwidth in units of 0.0001% of interface bandwidth.

ingminbw Ingress guaranteed % bandwidth in units of 0.0001% of interface bandwidth.

ingmaxbw Ingress maximum % bandwidth in units of 0.0001% of interface bandwidth.

minVpi Minimum VPI value, which is a number between 0 and 4095.(0 to 255 for UNI interface)

maxVpi Maximum VPI value, which is number between 0 and 4095.(0 to 255 for UNI interface)

minVci Minimum VCI value, which is a number between 32 and 65535.

maxVci Maximum VCI value, which is a number between 32 and 65535.

minConns Guaranteed number of connections, which is a number between 0 and the maximum number of connections in portgroup (see dspcd for portgroup information.)

maxConns Maximum number of connections, which is a number between 0 and the maximum number of connections in portgroup (see dspcd for portgroup information.)




Step 6 Enter the dspparts command to view the newly-added partition and verify its settings.

MGX8850.1.AXSM.a > dsppartsif part Ctlr egr egr ingr ingr min max min max min maxNum ID ID GuarBw MaxBw GuarBw MaxBw vpi vpi vci vci conn conn (.0001%)(.0001%)(.0001%)(.0001%)----------------------------------------------------------------------------- 1 2 5 500000 500000 500000 500000 0 1500 32 65535 4000 4000

Configuring an RPM-XF as an Edge Label Switch RouterYou can also configure an RPM-XF as an Edge Label Switch Router (ELSR) on the MGX 8850 Release 3 shelf where you have installed the Label Switch Controller (LSC). This is shown in Figure 9-1 as ELSR B. Follow these steps to configure this function.

Step 1 With the RPM-XF in the global configuration operating mode, enter the following commands.

RPMELSR(config)#interface loopback0RPMELSR(config-if)#ip address 192.168.3.11 255.255.255.255

Step 2 Enter the following commands to configure the MPLS partition.

RPMELSR(config)#int switch1RPMELSR(config-if)#switch partition 5 5RPMELSR(config-if)#ingress-percentage-bandwidth 10 100RPMELSR(config-if)#egress-percentage-bandwidth 10 100RPMELSR(config-if)#vpi 100 100RPMELSR(config-if)#vci 32 65535RPMELSR(config-if)#connection-limit 1 10000

Step 3 Enter the following commands to create an MPLS sub-interface.

RPMELSR(config)#interface switch1.11 mplsRPMELSR(config-if)#ip unnumbered loopback0RPMELSR(config-if)#mpls ip RPMELSR(config-if)#mpls atm control-vc 100 32RPMELSR(config-if)#mpls atm vpi 100 vci-range 33-65535

Note If the RPM-XF ELSR partition to the LSC has a non-zero vpi range, it is necessary to configure the mpls atm control-vc and the mpls atm vpi statements under the mpls subInterface. You must also configure the same under the Xtagatm interface on the LSC.

If you use the vp tunnel, you do not need to configure the control vc. Refer to the “Mapping an AXSM Port and ELSR Port to XTagATM Interfaces on the LSC” section.

Note Because Cisco Express Forwarding is enabled on RPM-XF by default, it is not necessary to use the ip cef command.



Chapter 9 Configuring MPLS FeaturesVPN Overview

Mapping an AXSM Port and ELSR Port to XTagATM Interfaces on the LSCEnter the following commands into the RPM-XF LSC (LSC-B in Figure 9-1) to map the AXSM port and the ELSR port configured in previous procedures to this LSC.

Step 1 Enter the cc command, cc 5, to switch to the RPM-XF LSC card.

Step 2 Enter enable and your password.

RPMLSC>enablePassword:

Step 3 Enter config t to enter global configuration mode.

RPMLSC#config tEnter configuration commands, one per line. End with CNTL/Z.

Step 4 Enter the interface XTagATM, ip, extended-port, and mpls commands to setup communication to the AXSM port, as shown in the following example for AXSM port 1.1.

RPMLSC(config)#interface XTagATM1111RPMLSC(config-if)#ip unnumbered Loopback0RPMLSC(config-if)# extended-port Switch1 descriptor ”1:1.1:1"RPMLSC(config-if)# mpls ip

Step 5 Enter the interface XTagATM, ip, extended-port, and mpls commands for the ELSR (ELSR-B in Figure 9-1), as shown in the following example.

RPMLSC(config)#interface XTagATM4122RPMLSC(config-if)#ip unnumbered loopback0RPMLSC(config-if)#extended-port Switch1 descriptor “4:1.2:2”RPMLSC(config-if)#mpls ipRPMLSC(config-if)#mpls atm control-vc 100 32RPMLSC(config-if)#mpls atm vpi 100 vci-range 33-65535

Note The extended port switch1 descriptor <slot:bay.line:port> identifies the location of the extended switch port that the XTagATM interface represents. For RPM-XF, the descriptor follows the format <slot>:1.2:2 where <slot> is the logical slot of the RPM-XF card.

VPN OverviewVirtual Private Networks (VPNs) provide the appearance, functions, and usefulness of a dedicated private network. The VPN feature for MPLS allows a Cisco IOS network to deploy scalable IPv4 Layer 3 VPN backbone service with private addressing, controlled access, and service-level guarantees between sites.

VPNs are supported by service provider networks over which labeled packets are forwarded from RPM-PR or RPM-XF Edge LSRs to other RPM-PR or RPM-XF Edge LSRs. A VPN service creates multiple private network environments within the public infrastructure. Service providers can use VPNs to target a given clientele and deliver individualized private network services to that clientele in a secure IP environment by using the public infrastructure.

For more information on MPLS VPNs, refer to: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/vpn.htm



Chapter 9 Configuring MPLS FeaturesVPN Overview

For more information on MPLS VPN enhancements, refer to: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/vpn_en.htm#xtocid151250

RequirementsThe requirements for an effective VPN are

• Privacy—All IP VPN services offer privacy over a shared (public) network infrastructure, the most well known solution of which is an encrypted tunnel. An IP VPN service must offer private addressing, where addresses within a customer private network do not need to be globally unique.

• Scalability—IP VPN services must scale to serve hundreds of thousands of sites and users. An IP VPN service should also serve as a management tool for service providers to control access to services, such as closed user groups for data and voice services. Controlled access places performance limits upon authorized programs, processes, or other systems in a network.

• Flexibility—IP VPN services must accommodate any-to-any traffic patterns and be able to accept new sites quickly, connect users over different media, and meet transport and bandwidth requirements of new intranet applications.

• Predictable Performance—Intranet applications supported by an IP VPN service require different classes of service. The service level performance between customer sites must be guaranteed. Examples include widespread connectivity required by remote access for mobile users and sustained performance required by interactive intranet applications in branch offices.

MPLS VPN FeaturesBeyond the functions of an IP VPN, the VPN features for MPLS allow a Cisco IOS network to deploy the following scalable IPv4 Layer 3 VPN backbone services:

• Connectionless Service—MPLS VPNs are connectionless. They are less complex because they do not require tunnels or encryption to ensure network privacy.

• Centralized Service—VPNs in Layer 3 privately connect users to intranet services and allow flexible delivery of customized services to the user group represented by a VPN. VPNs deliver IP services such as multicast, QoS, and telephony support within a VPN, and centralized services like content and web hosting. Combinations of services can be customized for individual customers.

• Scalability—MPLS based VPNs use Layer 3 connectionless architecture and are highly scalable.

• Security—MPLS VPNs provide the same security level as connection-based VPNs. Packets from one VPN cannot accidentally go to another VPN. At the edge of a provider network, incoming packets go to the correct VPN. On the backbone, VPN traffic remains separate.

Note Spoofing of a PER is nearly impossible because incoming packets are IP packets and must be received on an interface or subinterface uniquely identified with a VPN tag.

• Easy to Create—MPLS VPNs are connectionless. It is easy to add sites to intranets and extranets and to form closed user groups. A given site can have multiple memberships.

• Flexible Addressing—MPLS VPNs provide a public and private view of addresses, enabling customers to use their own unregistered or private addresses. Customers can freely communicate across a public IP network without network address translation (NAT).



Chapter 9 Configuring MPLS FeaturesHow VPNs Work

• Straightforward Migration—MPLS VPNs can be built over multiple network architectures, including IP, ATM, Frame Relay, and hybrid networks. There is no requirement to support MPLS on the customer edge (CE) router.

Supported PlatformsAll Cisco routers, including the Cisco 3600 Series Routers, the MGX 8850 Multiservice Switch equipped with RPM-PRs or RPM-XFs, and the Cisco 6400 Series Routers, as well as several other devices, support VPNs. Any LSR-capable platform can serve in the backbone. In addition to devices already mentioned, the LightStream 1010 ATM Switch, Catalyst 8540 MSR, and the BPX 8650 multiservice switch also support VPNs. Non-MPLS capable ATM switches can also be used, as they can carry MPLS over PVCs or PVPs.

How VPNs WorkEach VPN is associated with one or more VPN routing/forwarding instances (VRFs), which defines a VPN at a customer site attached to a PE router. A VRF table consists of the following components.

• IP routing table

• Derived Cisco Express Forwarding table

• Set of interfaces that use the forwarding table

• Set of rules and routing protocol variables that determine what goes into the forwarding table

VPNs for MPLSA customer site can be a member of multiple VPNs. However, a site can be associated with only one VRF. A customer site’s VRF contains all routes available to the site from the associated VPNs.

The IP routing table and CEF table for each VRF store packet forwarding information. (Together, these tables are analogous to the forwarding information base [FIB] used in MPLS.) A logically separate set of routing and CEF tables is constructed for each VRF. These tables prevent packets from being forwarded outside a VPN and prevent packets outside a VPN from being forwarded to a router within the VPN.

VPN Route-Target Communities and Export and Import ListsThe distribution of VPN routing information is controlled through the use of VPN route-target communities, implemented by Border Gateway Protocol (BGP) extended communities. Distribution works as follows:

• When a VPN route is injected into BGP, it is associated with a list of VPN route-target communities. This list is set through an export list associated with the VRF from which the route was learned.

• Associated with each VRF is an import list of route-target communities, which defines values to be verified by the VRF table before a route is deemed eligible for import into the VPN routing instance. For example, if a given VRF’s import list includes community-distinguishers A, B, and C, then any VPN route carrying A, B, or C is imported into the VRF.



Chapter 9 Configuring MPLS FeaturesHow VPNs Work

iBGP Distribution of VPN Routing InformationA PER learns an IP prefix from a CE router through static configuration, a BGP session, RIP, or OSPF. The PER then generates a VPN-IPv4 (vpnv4) prefix by linking an 8-byte route distinguisher to the IP prefix. The VPN-IPv4 address uniquely identifies hosts within each VPN site, even if the site uses globally non-unique (unregistered private) IP addresses. The route distinguisher used to create the VPN-IPv4 prefix is specified by a configuration command on the PER.

BGP uses VPN-IPv4 addresses to distribute network reachability information for each VPN within a service provider network. In building and maintaining routing tables, BGP sends routing messages within (interior BGP or iBGP) or between IP domains (exterior BGP or eBGP).

BGP propagates vpnv4 information using BGP multiprotocol extensions for handling extended addresses. Refer to RFC 2283, Multiprotocol Extensions for BGP-4. BGP propagates reachability information (expressed as VPN-IPv4 addresses) among PE routers; reachability information for a given VPN is propagated only to members of that VPN. BGP multiprotocol extensions identify valid recipients of VPN routing information.

Label ForwardingBased on the routing information stored in each VRF’s IP routing and CEF tables, MPLS uses extended VPN-IPv4 addresses to forward packets to their destinations.

To achieve this, an MPLS label is associated with each customer route. The PE router assigns the route originator’s label and directs data packets to the correct CE router. Tag forwarding across the provider backbone is based on dynamic IP paths or Traffic Engineered paths.

A customer data packet has two levels of labels attached when it is forwarded across the backbone.

• The top label directs the packet to the correct PE router.

• The second label indicates how that PE router should forward the packet.

The PE router associates each CE router with a forwarding table that contains only the set of routes that are available to that CE router.

Examples of VPN TopologiesA VPN contains customer devices attached to CE routers. These customer devices use the VPN to exchange data. Only the PE routers are aware of the VPN.

An example of a VPN with a service provider (P) backbone network, service provider edge routers (PE), and CE routers is shown in Figure 9-2.



Chapter 9 Configuring MPLS FeaturesConfiguring a VPN

Figure 9-2 VPN with a Service Provider (P) Backbone Network

Three VPNs communicating with five customer sites are shown in Figure 9-3. Notice that sites 1, 3, and 4 are members of two VPNs.

Figure 9-3 VPNs Communicate with Customer Sites

Configuring a VPNThis section explains how to configure the RPM-XF for VPN operation. It begins by listing the prerequisites for VPN configuration, then gives the configuration steps.

CE

PE

PE

CE

PE CE

CE

P

Service providerbackbone

VPN 1

VPN 1

VPN 2

Site 1 Site 1

Site 2

Site 2

P

P

P

1726

5

Site 2

VPN1VPN2

VPN3

Site 4

Site 5

1726

6

Site 3

Site 1




Prerequisites for VPN OperationThe network must be running the following Cisco IOS services before you can configure VPN operation:

• CEF switching in every tag-enabled router

• MPLS connectivity among all provider edge (PE) routers with VPN service or MPLS in all provider backbone (P) routers

• MPLS with VPN code in all provider routers with a VPN edge service (PE) routers

• BGP in all routers providing a VPN service

Complete the following tasks before you configure VPN operation:

• Turn on Cisco Express Forwarding (CEF). (CEF is enabled by default on RPM-XF.)

• Configure MPLS.

• Turn on BGP between provider routers for distribution of VPN routing information.

Configuring VPN OperationThis section describes how to configure routing protocols and create VRFs for a VPN. See the “MPLS Class of Service Support” section for the commands used in the tasks. Perform the following four tasks to configure and verify VPNs in your network:

1. Configure VRFs and associate interfaces with VRFs.

2. Configure BGP between provider routers for distribution of VPN routing information.

3. Configure import and export routes to control the distribution of routing information.

4. Verify VPN operation.

Configuring VRFs

To create a VRF, perform the following steps on the provider edge router.

Step 1 Enter VRF configuration mode and specify the VRF to which subsequent commands apply.

RPM(config)# ip vrf vrf-name

Step 2 Define the instance by assigning a name and an 8-byte route distinguisher.

RPM(config-vrf)# rd route-distinguisher

Step 3 Associate interfaces with the VRF.

RPM(config-if)# ip vrf forwarding vrf-name

Step 4 If BGP is used between the PE and a VRF CE, configure BGP parameters for the VRF CE session.

RPM(config-router)# address-family ipv4 vrf nameRPM(config-router-af)# aggregate-addressRPM(config-router-af)# auto-summaryRPM(config-router-af)# default-information originateRPM(config-router-af)# default-metric ...RPM(config-router-af)# distance ...RPM(config-router-af)# distribute-list ...RPM(config-router-af)# network ...RPM(config-router-af)# neighbor ...




RPM(config-router-af)# redistribute ...RPM(config-router-af)# synchronizationRPM(config-router-af)# table-map...

Note To ensure that addresses learned from CE routers via BGP are properly treated as VPN IPv4 addresses on a PE router, enter the command no bgp default ipv4-activate before configuring any CE neighbors. See Step 2 and Step 3 in the next section, “Configuring BGP.”

Step 5 If RIP is used between the PE and VRF CEs, configure RIP parameters (in a VRF address-family submode).

Note The default for auto-summary and synchronization in VRF address-family submode is off.

RPM(config-router)# address-family ipv4 vrf nameRPM(config-router-af)# auto-summaryRPM(config-router-af)# default-information originateRPM(config-router-af)# default-metric ...RPM(config-router-af)# distance ...RPM(config-router-af)# network ...RPM(config-router-af)# offset-list ...RPM(config-router-af)# redistribute ...

Step 6 Exit from the address family config mode.

RPM(config-router-af)# exit-address-family

Step 7 Configure static routes for the VRF.

RPM(config)# ip route [vrf vrf-name] destination <interface> ip_address

Configuring BGP

To configure Border Gateway Protocol (BGP) router address families, define sessions, and set global variables for routing protocols, perform the following steps with the PE router in configuration mode.

Step 1 Configure BGP address families.

RPM(config-router)# address-family {ipv4 | vpnv4}[unicast | multicast]

Step 2 Define BGP sessions.

RPM(config-router-af)# neighbor address | peer-group} remote-as as-numberRPM(config-router-af)# neighbor address | peer-group} update-source interfaceRPM(config-router-af)# neighbor peer-group peer-groupRPM(config-router-af)# neighbor address peer-group peer-group

Step 3 Activate a BGP session by entering the no bgp default ipv4-activate command to prevent automatic advertisement of address family IPv4 for every neighbor.

This command is required on a PE that establishes BGP sessions with CE routers. To enable advertisement of IPv4 prefixes for a particular neighbor, enter address-family mode for IPv4 then enter the neighbor...activate command for the neighbor.

RPM(config-router)# no bgp default ipv4-activate




For a particular address family, enter neighbor... activate.

RPM(config-router-af)# [no] neighbor address |peer-group} activate

Step 4 Enter optional BGP global commands that affect all address families.

RPM(config-router)# bgp always-compare-medRPM(config-router)# bgp bestpath ...RPM(config-router)# bgp client-to-client reflectionRPM(config-router)# bgp cluster-id ...RPM(config-router)# bgp confederation ...RPM(config-router)# bgp default local-XFeference ...RPM(config-router)# bgp deterministic-med ...RPM(config-router)# bgp fast-external-fallover ...RPM(config-router)# bgp log-neighbor-changesRPM(config-router)# bgp redistribute-internalRPM(config-router)# bgp router-id ...RPM(config-router)# timers bgp ...

Step 5 Enter BGP configuration commands for address family IPv4.

All BGP configuration commands supported in previous versions of IOS are valid for address family IPv4 unicast. These commands affect either all IPv4 instances or the default IPv4 routing table. For backward compatibility, these commands can be entered in either router config mode or in address family mode for ipv4 unicast. See Step 3 for information on the command no bgp default ipv4-activate.

RPM(config-router)# bgp ...

Step 6 Enter BGP configuration commands for address family VPNv4.

RPM(config-router)# bgp dampening ...RPM(config-router)# neighbor ...RPM(config-router)# neighbor address | peer-group}activate

Step 7 To configure iBGP to exchange VPNv4 Network Layer Reachability Information (NLRI) (between PE router and route reflector or between PE routers), first define an iBGP BGP session.

Note To ensure that VPN packets are properly tag forwarded between the PE routers, specify loopback addresses for the neighbor address and the update-source interface.

RPM(config-router)# neighbor address remote-as as-numberRPM(config-router)# neighbor address update-source interface

Step 8 Activate the advertisement of VPNv4 NLRIs.

RPM(config-router)# address-family vpnv4RPM(config-router-af)# neighbor address activate

Balancing eiBGP Load Sharing

External and Internal Border Gateway Protocol (eiBGP) load sharing is an enhancement to Border Gateway Protocol (BGP) that enables load sharing over parallel links between customer edge routers and service provider edge routers. This feature enables service providers to share customer traffic loads over parallel paths within an MPLS core network.

To balance load sharing over BGP, you configure traffic to be directed by gateway routers over multiple paths between autonomous systems (AS). The following CLI commands are used to implement this feature.




Configure Import and Export Routes

To configure VRF route target extended communities and import route maps, perform the following steps with the PE router in configuration mode.

Step 1 Enter VRF configuration mode and specify a VRF.

RPM(config)# ip vrf vrf-name

Step 2 Import routing information from the specified extended community.

RPM(config-vrf)# route-target import community-distinguisher

Step 3 Export routing information to the specified extended community.

RPM(config-vrf)# route-target export community-distinguisher

Step 4 Associate the specified route map with the VRF being configured.

RPM(config-vrf)# import map route-map

Checking the VRFs

Perform the following steps to verify the VPN configuration.

Command Description

maximum-path <nums> Configure maximum number of EiBGP parallel routes.

For example:

bgpbox-zenith-CE1(config)#router bgp 4bgpbox-zenith-CE1(config-rout)#maximum-paths 3bgpbox-zenith-CE1(config-rout)#end

show ip bgp This command has been enhanced to show the multipaths.

Each multipath is marked as 'multipath'.

The bestpath is marked as 'multipath' and 'bestpath'.

The output also has what flavour of multipath is enabled.

For example:

bgpbox-zenith-CE1#sh ip bgp 141.22.0.0BGP routing table entry for 141.22.0.0/16, version 18Paths: (2 available, best #1)Multipath: eBGPAdvertised to non peer-group peers:7.0.76.9100 57.0.76.2 from 7.0.76.2 (100.0.0.2)Origin IGP, localpref 100, valid, external, multipath, best100 57.0.76.9 from 7.0.76.9 (100.0.0.9)Origin IGP, localpref 100, valid, external, multipath




Step 1 Display the set of defined VRFs and the interfaces associated with each one.

RPM# show ip vrf

Step 2 Display detailed information about configured VRFs, including the import and export community lists.

RPM# show ip vrf detail

Step 3 Display the IP routing table for VRF.

RPM# show ip route vrf vrf-name

Step 4 Display the routing protocol information associated with a VRF.

RPM# show ip protocols vrf vrf-name

Step 5 Display the CEF forwarding table associated with a VRF.

RPM# show ip cef vrf vrf-name

Step 6 Display the VRF table associated with an interface. Use either of the following commands:

RPM# show ip interface interface-numberRPM# show cef interface interface-number

Step 7 Display VPNv4 NLRI information.

The keyword all displays the entire database. The keyword rd displays NLRIs that match the specified route distinguisher. The keyword vrf displays NLRIs with the specified VRF. Add the keyword tags after any of the other keywords and arguments to list the tags distributed with the VPNv4 NLRIs.

RPM # show ip bgp vpnv4 all [tags]RPM # show ip bgp vpnv4 rd route-distinguisher [tags]RPM # show ip bgp vpnv4 vrf vrf-name [tags]

Step 8 Display tag forwarding entries that correspond to VRF routes advertised by this router.

RPM # show mpls forwarding vrf vrf-name [prefix mask/length] [detail]

Step 9 You can also use ping or traceroute.

RPM # ping vrf vpn 1.1.1.1

where 1.1.1.1 is the destination address

Step 10 Enter the following telnet command to check the VRFs.

telnet 1.1.1.1 /vrf vpn



Chapter 9 Configuring MPLS FeaturesMulticast VPN

Multicast VPNMulticast VPN (Virtual Private Network) provides the ability to transport multicast traffic inside an MPLS-VPN using multicast tunneling. A single MPLS-VPN endpoint can send a multicast packet to all other destination endpoints in the MPLS-VPN.

Multicast VPN supports the following things:

• MPLS frame-based encapsulation

• PIM-SM and PIM-SSM core modes

• Maximum of 384 mVRFs

• ATM, POS and GIGE interfaces

• Point-to-point ATM sub-interfaces

Multicast VPN does NOT support the following commands:

• ip multicast rate-limit

• ip multicast multipath

Table 9-1 defines some of the terms used for multicast VPN.

Multicast VPN OperationMulticast VPN is the ability to support multicast traffic inside a MPLS-VPN using multicast tunneling. It does NOT use the MPLS as a transport for multicast traffic across the Providers network.

A CE router (customer edge router) sends a multicast packet (C-packet (customer packet)) to a PE router (provider edge router). The PE router creates a P-packet (provider packet) by adding either a GRE-IP header or an IP-IP header to this packet. The PE router then sends the P-packet to one or more P routers (provider routers) using multicast processing.

A multicast domain is a set of multicast enabled VRFs (mVRFs) that can send multicast traffic to each other. Multicast VPN mapping is achieved by encapsulating C-packets into P-packets using GRE.

Table 9-1 Multicast VPN Terms

Term Definition Description

VPN Virtual Private Network

mVPN Multicast Virtual Private Network

An MPLS-VPN that supports native multicast.

VRF VPN Routing and Forwarding Table

Holds Unicast routing table for a VPN at a PE.

mVRF Multicast VPN Routing and Forwarding Table

Multicast routing table for a VPN at a PE

MDT Multicast Distribution Tree A multicast tree built in the P-network for each Multicast Domain.

Default-MDT Default Multicast Distribution Tree

All mVRFs belong to one. Used for PIM control traffic, low bandwidth sources, flooding of Dense-mode.

Data-MDT Data Multicast Distribution Tree Created on demand, for high bandwidth sources, avoids replication to uninterested PEs.




A customer multicast packet (C-packet) originating from one segment of a MPLS-VPN is sent to the other segments of the MPLS-VPN as follows:

1. The CE router sends a C-packet to a PE router.

2. The PE router builds a Provider multicast packet (P-packet) by adding a GRE-IP header and sends the P-packet to one or more P routers using multicast processing. The destination IP address in the P-packet contains a multicast address which was configured for the MPLS-VPN (VRF).

3. The P router(s) forward the P-packet within the Provider network using multicast processing. Forwarding is based on the multicast address in the P-packet.

4. The other PE routes associated withe MPLS-VPN segment receive the P-packet, remove the tunnel header and forward the C-packet to the CE route(s) associated with the MPLS-VPN segment using multicast processing. Forwarding is base on the multicast address in the C-packet.

Multicast VPN Example Configuration

ip vrf cokerd 1:1route-target export 1:1route-target import 1:1mdt default 232.0.0.1mdt data 232.0.1.0 0.0.0.255 threshold 500

!ip pim sparse-mode

IP MulticastIP Multicast is transmits information from a single source to multiple destinations. A single copy of a datagram is sent from the source and replicated through the receivers.

IP Multicast is a normal IP packet, but uses a multicast destination address. Destination addresses are in the range 224.0.0.0–239.255.255.255 (D-Class). Sources transmit to a group address and destinations listen for that group

Multicast traffic is forwarded using a Multicast Distribution Tree of which there are two types:

• Source Trees

• Shared Trees

Packets are directed from source trees to shared trees using IP Multicast States. These states provide the forwarding entries for packet distribution down a tree and consist of the Source Address (root) and the Destination Group of the multicast stream.

Source trees are expressed as (S, G) for (Source, Group) and refer to a specific source for a specific group. Shared trees are expressed as (*, G) for (*, Group) and refer to all sources for a specific group.

Multicast traffic travels from source (root) to receivers (leaves) via the shortest path. A rendezvous point router handles many multicast groups. Receivers connected to the rendezvous point to learn about the sources. The Sources transmit to the rendezvous point and the rendezvous point forwards to the receivers




Multicast ProtocolsThe RPM-XF supports the following multicast modes:

• Dense Mode Protocols – Flood and Prune

– Distance Vector Multicast Routing Protocol (DVMRP)

– Protocol Independent Multicast (PIM-DM) - Legacy

• Sparse Mode Protocols – Join and Prune

– Core Based Trees (CBT)

– Protocol Independent Multicast (PIM-SM)

PIM-SM is the most widely used multicast protocol and uses the existing unicast table for RPF check.

• Link State Protocols

– Multicast Open Shortest Path First (MOSPF)

Multicast Protocols Supported in SP Core

Only PIM based protocols are supported by IOS in the core. The following PIM modes are supported by Cisco IOS:

• PIM Bidirectional (PIM-BIDIR)

• PIM Source Specific Multicast (PIM-SSM)

• PIM Sparse-Mode (PIM-SM)

• PIM modes supported by Zenith

• PIM Source Specific Multicast (PIM-SSM)

• PIM Sparse-Mode (PIM-SM)

Multicast Modes

• PIM Dense-Mode

– Flood and Prune behavior—push model that uses source trees only, is for legacy applications, and is rarely deployed.

• PIM Sparse-Mode

– Join and Prune—pull model that uses shared trees, but may switch to source trees.

• Bi-directional PIM

– Like PIM-SM, but uses a BIDIR shared tree for all traffic.

• Source-Specific Multicast (SSM)

– Always uses a (S, G) source tree—no RP is needed S/W needed in receivers, IGMPv3 or intelligence in last hop router.




Source Specific MulticastSource Specific Multicast (SSM) permits the provider edge (PE) router to connect directly to a source tree for an MDT. No rendezvous points are needed in the network. Rendezvous points are a potential failure point and an additional overhead in Source Specific Multicast.

Source Specific Multicast uses shared trees and bidirectional trees. However, a source and groups (S, G) state is required for each mVPN in a PE router. For example, if there are 5 PE routers each holding an mVRF RED, there will be 5 (S, G) entries.

SSM Configuration Example

ip pim ssm range Data-MDT-Range!ip access-list standard Data-MDT-Range permit 239.192.10.0 0.0.0.255

mVPN Forwarding OperationThe section describes the operation of mVPN forwarding.

Forwarding C-packets (from CE) takes place as follows:

1. A C-Packet arrives on a VRF configured PE interface

2. The mVRF (fib index) is implicitly identified.

3. A normal RPF check is performed on the C-source.

A search is performed to find the (*,G) or (S,G) entry. The source IP address, multicast group address, and the FIB index are used to perform the search. PXF will use at least one context (new work) for the search.

4. The packet is punted to RP if no match is found. This lets the IOS create the (*,G)/(S,G) entry for the group.

5. The C-packet is replicated out the customer-network interfaces in the o-list of the matched (*,G)/(S,G) entry.

PXF uses one feedback for each replication. If the o-list contains an MTI, the C-packet is encapsulated into a P-packet. The source is a PE BGP peer address and the destination is the MDT Group address. The encapsulated packet will be replicated on all the o/g interfaces in the o-list of the global (*,G)/(S,G) entry for the MDT group, such as other PE and P routers. PXF uses two feedbacks for each of such replications.

6. PXF takes one last feedback for cleanup.

Forwarding P-packets (from P-network)

7. The P-packet is forwarded through the P-network as a normal multicast.

8. The global interface transmits the P-packet and searches for the (S, G) or (*, G) entry for the MDT-group.

9. A normal RPF check is performed on the P-source (PE peer). PXF uses at least one context (new work) for the check.




10. The P-packet is replicated out interfaces in the o-list. At this point this would be P/PE interfaces in the global mroute table.

11. PXF takes one feedback for each replication. If the outgoing interface list includes an mVRF i/f, the P-packet is de-encapsulated. The target mVRF is derived from the MDT-group and is already programmed in PXF by the PXF client.

12. A search is performed in the target mVRF using the source and group address from the inner packet. This takes at least one feedback. If no match is found, the packet is dropped. This implies no receivers.

13. The C-packet is then replicated out the o-list of the matched entry in the mVRF. The PXF takes one feedback for each replication.

14. In the end, one feedback is required for the clean-up.

VRF Configuration Exampleip multicast-routing vrf CustomerB

ip vrf CustomerB rd 101:1 route-target export 101:1 route-target import 101:1 mdt default 238.1.1.1 mdt data 238.1.2.0 0.0.0.255 threshold 1

interface Switch1.56 point-to-point ip vrf forwarding CustomerB ip address 156.1.1.10 255.255.255.0 ip pim sparse-mode

02:05:15: %LINEPROTO-5-UPDOWN:Line protocol on Interface Tunnel0, changed state to up

pop20-slot10#sh int tunnel0Tunnel0 is up, line protocol is upHardware is Tunnel Interface is unnumbered. Using address of Loopback0 (10.10.10.10) MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec, reliability 255/255, txload 112/255, rxload 1/255 Encapsulation TUNNEL, loopback not set Keepalive not set Tunnel source 10.10.10.10 (Loopback0), destination 238.1.1.1 Tunnel protocol/transport GRE/IP Multicast, key disabled, sequencing disabled Tunnel TTL 255 Checksumming of packets disabled, fast tunneling enabled

PE 1# show ip pim vrf CustomerB interfaceAddress Interface Ver/ Nbr Query DR DR

Mode Count Intvl Prior 156.1.1.10 Switch1.56 v2/SD 1 30 1 0.0.0.010.10.10.10 Tunnel0 v2/SD 2 30 1 10.10.10.10

PE 1#sh ip mrouteIP Multicast Routing TableFlags:

D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, P - Pruned, R - RP-bit set, F - Register flag,



Chapter 9 Configuring MPLS FeaturesMPLS LDP

T - SPT-bit set, J - Join SPT, M - MSDP created entry, X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel Y - Joined MDT-data group, y - Sending to MDT-data groupOutgoing interface flags: H - Hardware switched Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode

(10.10.10.10, 238.1.2.0), 00:28:43/00:03:28, flags: FTZ Incoming interface: Loopback0, RPF nbr 0.0.0.0 Outgoing interface list: Switch1.2, Forward/Sparse-Dense, 00:27:43/00:03:18 Switch1.7, Forward/Sparse-Dense, 00:28:43/00:03:18

(10.10.10.10, 238.1.1.1), 21:29:48/00:01:24, flags: FTZ Incoming interface: Loopback0, RPF nbr 0.0.0.0 Outgoing interface list: Switch1.7, Forward/Sparse-Dense, 18:14:59/00:03:25 Switch1.2, Forward/Sparse-Dense, 21:29:48/00:02:56

MPLS LDPMPLS label distribution protocol (LDP) allows the construction of highly scalable and flexible IP Virtual Private Networks (VPNs) that support multiple levels of services. LDP provides a standard methodology for hop-by-hop, or dynamic label, distribution in an MPLS network by assigning labels to routes that have been chosen by the underlying Interior Gateway Protocol (IGP) routing protocols. The resulting labeled paths, called label switch paths (LSPs), forward label traffic across an MPLS backbone to particular destinations. These capabilities enable service providers to implement Cisco MPLS-based IP VPNs and IP+ATM services across multivendor MPLS networks.

LDP is a superset of the prestandard Tag Distribution Protocol (TDP) from Cisco, which also supports MPLS forwarding along normally routed paths. For those features that LDP and TDP share in common, the pattern of protocol exchanges between network routing platforms is identical. The differences between LDP and TDP for those features supported by both protocols are largely embedded in their respective implementation details, such as the encoding of protocol messages.

This release of the Cisco IOS, which supports both the LDP and TDP protocols, provides the means for transitioning an existing network from a TDP operating environment to an LDP operating environment. Thus, you can run LDP and TDP simultaneously on any given router platform. The routing protocol that you select can be configured on a per-interface basis for directly- connected neighbors and on a per-session basis for nondirectly connected (targeted) neighbors. In addition, LSP across an MPLS network can be supported by LDP on some hops and by TDP on other hops.

For more information, including configuration tasks, transitioning a network from TDP to LDP, and command reference documentation, refer to the Cisco IOS Release 12.2T “MPLS Label Distribution Protocol” documentation at the following URL http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ldp_221t.htm#xtocid212130.

Note There is no CWM support planned for LDP or TDP.



Chapter 9 Configuring MPLS FeaturesSupport for Multi-VC on the RPM-XF

Support for Multi-VC on the RPM-XFThis feature enables support for initiation of multiple label switched paths (LSPs) per destination on the RPM-XF to provide different class of service (COS). Four LVCs will be created corresponding to the four MPLS COS. The MPLS COS functionality enables network administrators to satisfy a wide range of requirements in transmitting IP packets through an MPLS-enabled network.

Multi-VC feature is to be enabled on RPM-XF eLSR. Internally, the RPM-XF eLSR creates 4 queues within the RM7000A MIPS processing engine to provide the Qos for the 4 MPLS COS. Bandwidth allocation for each MPLS COS is configurable via IOS Modular Qos CLI and is calculated based on the MPLS partition configured on the RPM-XF eLSR."

Incoming unlabeled IP packets into the RPM-XF eLSR are classified into different MPLS COS based on the IP precedence bit settings. Based on the MPLS COS classification for the packet, the correct LVC is then used for the label imposition and packet forwarding. After this, the packet is queued up onto the corresponding RM7000A MIPS processing engine queue COS queue.

The following example demonstrates a typical configuration of multi-vc mode with modular QoS.

Configuring Multi-VC on the RPM-XF eLSRFigure 9-4 depicts a sample traffic flow of a RPM-XF eLSR with Multi-VC feature enabled. Incoming unlabeled IP packets flows in through the incoming POS interface. The input service-policy configured on the POS interface maps each packet IP precedence bit to the MPLS experimental bit. Each MPLS experimental bit is mapped to an MPLS COS. According to the packet MPLS COS, one of the 4 LVCs (cos-map can be used to control the number of LVCs to be created for each destination IP prefix) will be used for label imposition and packet forwarding. After the packet is imposed with the correct label, the packet will be queued up to the end of the corresponding COS queue to be sent out from the RPM-XF ATM interface, switch1.

Figure 9-4 is created based on the System Block Diagram shown in Figure 9-1. The depicted as RPM-XF eLSR in the following figure is the ELSR-B in Figure 9-1. The following configuration sections are also build on this reference.

Figure 9-4 Multi-VC Configuration

RPM-XF eLSR Out: map exp.bit to COS

PXF queues for mplsClass of Services

int sw 1.11mpls

(to LSC-5)

Cos0 10% + 10% Cos0

10% + 10% Cos1

10% + 10% Cos2

20% + 20% Cos3

In: map IP precedencebit to mpls exp. bit

int sw 1.15mpls

(to LSC-9)

Cos1Cos2Cos3

Cos3

Cos0Cos1Cos2

int PCS 1/0int PCS 1/0 int sw 1w 1int PCS 1/0 int sw 1

LVCs

Incoming unlabeled IP traffic Outgoing labeled mpls traffic

Traffic for one IP dest.or one IP dest. prefixTraffic for one IP dest. prefix

8021

4




Note Multi-VC should be configured only on an RPM-XF edge LSR.

The following configuration sample shows five basic steps to be performed on the RPM-XF eLSR:

• Configuring Policy Map to map IP Precedence to MPLS Experimental Bit.

• Attaching Input Service Policy to input interface.

• Configuring Output Service Policy to allocate bandwidth to each MPLS COS Queue.

• Attaching Output Service Policy to output MPLS interface and

• Binding a MPLS partition to the output MPLS interface (New addition specific for RPM-XF).

The following is an example of how to configure multi-VC on the RPM-XF.

! Zenith-ELSR

class-map match-all IP_PREC0match ip precedence 0 4class-map match-all IP_PREC1match ip precedence 1 5class-map match-all IP_PREC2match ip precedence 2 6class-map match-all IP_PREC3match ip precedence 3 7!class-map match-all COS_0 match mpls experimental 0 4 class-map match-all COS_1 match mpls experimental 1 5 class-map match-all COS_2 match mpls experimental 2 6 class-map match-all COS_3 match mpls experimental 3 7 !policy-map set_EXP0class IP_PREC0set mpls experimental 0policy-map set_EXP1class IP_PREC1set mpls experimental 1policy-map set_EXP2class IP_PREC2set mpls experimental 2policy-map set_EXP3class IP_PREC3set mpls experimental 3!policy-map COS_0123class COS_0 bandwidth percent 20class COS_1 bandwidth percent 20class COS_2 bandwidth percent 20class COS_3 bandwidth percent 40!interface Switch1 no ip addressswitch partition 8 8 ingress-percentage-bandwidth 50 100




egress-percentage-bandwidth 50 100 vpi 140 145 vci 32 65535 connection-limit 8000 8000 ! switch auto_synch off!interface Switch1.14 mplsip unnumbered Loopback1service-policy output COS_0123mpls ip mpls atm switch-partition 8mpls atm multi-vcmpls atm control-vc 140 32mpls atm vpi 140-145 vci-range 33-65535!

The following is an example of how to configuring policy map to map IP precedence to MPLS experimental bit.

class-map match-all IP_PREC0 match ip precedence 0 4class-map match-all IP_PREC1 match ip precedence 1 5class-map match-all IP_PREC2 match ip precedence 2 6class-map match-all IP_PREC3 match ip precedence 3 7!

policy-map set_EXP0123 class IP_PREC0 set mpls experimental 0 class IP_PREC1 set mpls experimental 1 class IP_PREC2 set mpls experimental 2 class IP_PREC3 set mpls experimental 3!

The following is an example of how to attach input service policy to input interface.

int POS1/0 service-policy input set_EXP0123!

The following is an example of how to configure output service policy to allocate bandwidth to each MPLS COS queue.

class-map match-all COS_0 match mpls experimental 0 4class-map match-all COS_1 match mpls experimental 1 5class-map match-all COS_2 match mpls experimental 2 6class-map match-all COS_3 match mpls experimental 3 7!

policy-map COS_0123 class COS_0 bandwidth percent 20




class COS_1 bandwidth percent 20 class COS_2 bandwidth percent 20 class COS_3 bandwidth percent 40!

The following is an example of how to attach output service policy to output MPLS interface and bind an MPLS partition to the output MPLS interface.

interface switch1.11 mpls service-policy output COS_0123 mpls atm switch-partition 5!

Note The configuration example for the ELSR-B in Figure 9-1 already has switch-partition 5 and interface switch1.11 configured to enable cell-based MPLS without multi-VC feature. These examples show the additional commands required to enable the multi-VC feature.

C H A P T E R



10Configuring Quality of Service

This chapter explains how to configure Quality of Service (QoS) on the RPM-XF and contains the following sections:

• General QoS Configuration Procedure

• Class Map Commands

• Policy Map Commands

• Service-Policy Command

• Show Commands

• Quality of Service Policy Propagation Example Using Border Gateway Protocol

• Versatile Traffic Management System (VTMS)

• MultiLink PPP/Link Fragmentation Interleaving (MLP/LFI)

• Internet Protocol Header Compression (IPHC)

Quality of Service (QoS) on the RPM-XF supports the following features:

• Committed access rate (CAR) measures traffic rates and, based on the rates, takes actions (such as dropping packets). RPM-XF QoS supports CAR ("police") on input packets and shaping ("shape") on output packets.

• Random Early Detection (RED) is a congestion avoidance mechanism that takes advantage of TCP's congestion control mechanism. By randomly dropping packets prior to periods of high congestion, RED tells the packet source to decrease its transmission rate. Assuming the packet source is using TCP, it will decrease its transmission rate until all the packets reach their destination, indicating that the congestion is cleared.

• Weighted random early detection (WRED) uses an algorithm to randomly discard packets during congestion. This approach reduces congestion by causing the packet source to slow down.

Weighted RED (WRED) generally drops packets selectively based on IP precedence. Packets with a higher IP precedence are less likely to be dropped than packets with a lower precedence. Thus, higher priority traffic is delivered with a higher probability than lower priority traffic.

• Bandwidth reservation, also referred as fair queueing, assigns bandwidth to certain streams of packets.

• Low-latency priority queueing can be assigned for real-time traffic such as voice and video.

• Traffic shaping is used to control traffic by maintaining data flow at a set rate.

• Set specifies an IP precedence/DSCP or MPLS experimental value that can be used by other routers to manage QoS.



Chapter 10 Configuring Quality of ServiceGeneral QoS Configuration Procedure

• 802.1q support allows PXF switching for ARPA encapsulation.

• Versatile Traffic Management System (VTMS)

• MultiLink PPP/Link Fragmentation Interleaving (MLP/LFI)

• Internet Protocol Header Compression (IPHC)

In addition, the RPM-XF supports QoS policy propagation through the Border Gateway Protocol (QPPB). For a QPPB configuration example, see “Quality of Service Policy Propagation Example Using Border Gateway Protocol” section on page 10-15

General QoS Configuration ProcedureYou can configure WRED, CAR, and other qualities of service by performing the following tasks:

1. Create a QoS boilerplate that defines the criteria for prioritizing traffic.

2. Apply the boilerplate to an interface.

Figure 10-1 shows an overview of the QoS process.

Figure 10-1 QoS Process

Policy-map commandstell the router what todo with a packet. For example, drop the packet or let it through.

Service-policy commandapplies a class-map andpolicy-map to a specificinterface.

Packet

Packet

RPM-XF

Packet

7564

7

Class-map commandstell the router how torecognize a packet thatis subject to QoS. For example, watch for a packet associated witha specific access list.

Packet



Chapter 10 Configuring Quality of ServiceGeneral QoS Configuration Procedure

Creating a QoS BoilerplateThis section provides the information you need to create a QoS boilerplate. To create a QoS boilerplate, perform two procedures:

1. Create a class map—The class map tells the RPM-XF how to recognize the packets that are subject to QoS.

2. Create a policy map—The policy map lists QoS services to be applied to packets described by one or more class maps.

Creating a Class Map

The following procedure describes how to create a class map.

Step 1 Assign a name to your class map by entering the class-map name command. In the following example, a class map named mink is created.

Router(config)# class-map minkRouter(config-cmap)#

As the example shows, after you enter the class-map name command, you enter class map configuration mode (config-cmap).

Note Some Cisco IOS documents refer to the QoS configuration modes as the modular CLI.

Step 2 Describe the characteristics of the packets that are subject to QoS by entering the match command. In the following example, the packet is described as being associated to access group 10 and having the IP precedence bit set to 1.

Router(config-cmap)# match access-group 10 Router(config-cmap)# match ip precedence 1

Step 3 Exit class map configuration mode.

Router(config-cmap)# exitRouter(config)

As a result of the creation of a class map, the router can recognize packets that are subject to QoS. You must now tell the router the action to take on those packets.

Creating a Policy Map

The following procedure describes how to create a policy map.

Step 1 Assign a name to your policy map by entering the policy-map name command. In the following example, a policy map named lynx is created.

Router(config)# policy-map lynxRouter(config-pmap)#

As the example shows, after you enter the policy-map name command, you enter policy map configuration mode (config-pmap).



Chapter 10 Configuring Quality of ServiceClass Map Commands

Step 2 Associate the policy map with a class map.

Router(config-pmap)# class minkRouter(config-pmap-c)#

As the example shows, after entering the class name command, enter the policy map class configuration mode (config-pmap-c).

Step 3 Describe the QoS actions you want the router to perform when the router encounters a packet that has the characteristics described by the class map.

In this example, the router executes default behavior for the police command. (See the “Specifying a Committed Access Rate” section on page 10-7 for details.)

Router(config-pmap-c)# police 80000

Step 4 Exit policy map configuration mode.

Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)#

You have completed the creation of a QoS boilerplate, which can be assigned to an interface.

Assigning a QoS Boilerplate to an InterfaceUse the service-policy command to assign a QoS boilerplate to an interface. In the following example, the policy map lynx is assigned to traffic that enters the gigabit Ethernet interface of an RPM-XF.

Router(config)# interface gigabitethernet 1/0Router(config-if)# service-policy input lynx

Class Map CommandsThis section describes commands for creating and modifying class maps.

You can have up to 2048 policy maps. You can have up to 32 class maps per policy map. However, you can only have up to a total of 256 class maps, including the class-default. The same class map can be applied to different policy maps.

Creating a Class MapYou can create a class map and enter class-map configuration mode by entering the class-map command.

class-map [match-any | match-all] class-map-name[no] class-map class-map-name


match-any A single match rule is sufficient for class membership.



Chapter 10 Configuring Quality of ServiceClass Map Commands

The default value is match-all.

Use the no class-map command to delete a class map.

Cisco IOS software supports a maximum of 255 unique class maps.

In the following example, a class-map named mink is created. In the example, the default value of match-all is used.

Router(config)# class-map minkRouter(config-cmap)#

Matching AttributesUse the match command to define the characteristics of the packets that belong to the class map.

match match_statement[no] match match_statement

The match command match_statement is one of the following values:

• match [not] access-group number—Specifies that the packet must (or must not) be permitted by the access group whose number is from 1 to 2699.

• match [not] access-group name access-list-name—Specifies that the packet must (or must not) be permitted by the access list whose name is access-list-name.

• match [not] any—Specifies that all (or no) packets belong to this class.

• match [not] ip dscp code-point-value1 […[code-point_value8]]—Specifies that the packet IP differentiated service code point (dscp) value must (or must not) match one or more of the code-point values in the range 0 to 63. You can specify up to eight code point values, separating consecutive values with a space.

• match [not] ip precedence prec_value1 […[prec_value8]]—Specifies that the packet IP precedence value must (or must not) match one or more precedence values in the range 0 to 7. You can specify up to eight precedence values, separating consecutive values with a space.

• match [not] qos-group number—Specifies that the packet QoS group number value must (or must not) be in the group number range 0 to 99.

• match [not] ip rtp lowest-udp-port:2000-65535 range:0-16383—Used to match a packet that has an even numbered UDP port within (or outside of) the specified range. Only even ports are matched because they carry the real time data streams. Odd ports are not matched because they only carry control information.

• match [not] mpls experimental experimental-value—Specifies that the packet experimental bits must (or must not) match the specified experimental value(s) (in the range from 0 to 7). You can specify up to eight experimental values, separating consecutive values with a space. Note that this match can only match MPLS (tagged) frames.

Use the no form of this command to disable the match attributes.

match-all Only those packets that have all the specified attributes are part of the class.

class-map-name Any word or number.

Note The class named class-default is reserved and cannot be modified with match statements.




Chapter 10 Configuring Quality of ServicePolicy Map Commands

To construct your mapping rules, enter one or more match commands. Each packet is compared to the criteria specified by the match commands to determine if the packet contains the attribute you specify.

The RPM-XF supports a maximum of 16 match statements in a class map.

In the following example, a class map is created that tells the router to look for packets that belong to access group 1 and have an IP precedence value of 3 or 7.

Router(config)# class-map minkRouter(config-cmap)# match access-group 1Router(config-cmap)# match ip precedence 3 7

Policy Map CommandsThis section describes commands for creating and modifying policy maps.

You can have up to 2048 policy maps. You can have up to 32 class maps per policy map. However, you can only have up to a total of 256 class maps, including the class-default. The same class map can be applied to different policy maps.

Creating a Policy MapYou can create a policy map and enter policy-map configuration mode by entering the policy-map command from global configuration mode.

policy-map policy-map-name[no] policy-map policy-map-name

The policy-map-name can be any word or number.

Use the no form of the command to remove a policy map.

In the following example, a policy map named lynx is created.

Router(config)# policy-map lynxRouter(config-pmap)#

Assigning a Class to a Policy MapUse the class class-map-name command from policy-map configuration mode to assign a class map to a policy map.

class class-map-name[no] class class-map-name

The class-map-name is the name assigned to the class map.

Use the no form of the command to remove a class.

You can use a special class map name called class-default on a given interface to assign QoS policies to all packets that are not already described in the policy map by a class of a different name.

After you enter the class class-map-name command, you enter policy-map class configuration mode, in which you can enter QoS policies.




Tip A packet is processed by a policy map as soon as a match is found. When you assign class names to a policy map, assign the first name to the class that is most likely to be used. This can improve QoS performance.

In the following example, the class map named mink is assigned to the policy map named lynx.

Router(config)# policy-map lynxRouter(config-pmap)# class minkRouter(config-pmap-c)#

In the following example, the default class map is assigned to the policy map named lynx.

Router(config)# policy-map lynxRouter(config-pmap)# class class-defaultRouter(config-pmap-c)#

Specifying a Committed Access RateTo specify a committed access rate (CAR), enter the police command while you are in policy-map class configuration mode. You can use this command to control low-priority traffic, so that an interface has more bandwidth for high-priority traffic or to enforce a specific rate on an interface.

police bps [normal-burst | max-burst | conform-action action | exceed-action action][no] police [normal-burst | max-burst | conform-action action | exceed-action action]


bps A value from 8000 to 2,000,000,000 bits per second.

normal-burst A value from 2000 to 1,024,000,000 bytes.

max-burst A value from 2000 to 1,024,000,000 bytes.

conform-action action Indicates the action that should be taken if the rate is not exceeded. See Table 10-1 for a list of actions.

exceed-action action Indicates the action that should be taken if the rate is exceeded. See Table 10-1 for a list of actions.

Table 10-1 CAR Actions

Action Description

drop Drop all matched traffic.

set-dscp-transmit value Set dscp and send it (mark unmatched traffic with a new dscp value). Value is in the range 0 to 63.

set-mpls-exp-transmit value

Set the MPLS experimental bits and send it. Value is in the range 0 to 7.

set-prec-transmit value Rewrite packet procedure and send it (mark matched traffic with a new IP precedence value). Value is in the range 0 to 7.




If you enter only police bps at the command line, the following default behavior occurs: traffic that conforms to the bps value is transmitted and traffic that exceeds the bps value is dropped.

Use the no form of the command to disable policing.

In the following example, CAR is assigned to the class named mink.

Router(config)# policy-map lynxRouter(config-pmap)# class minkRouter(config-pmap-c)# police 720000 90000 90000 conform-action transmit exceed-action drop

Enabling Weighted Random Early DetectionUse the random-detect command to enable weighted random early detection (WRED), which randomly discards packets during congestion based on IP precedence settings. The random-detect command enables a WRED drop policy for a traffic class that includes a bandwidth guarantee.

Note The bandwidth must be set before you can enable WRED (see Bandwidth Reservation and Low-Latency Priority Queueing, page 10-9).

Note On the ATM interface, you can only use WRED on a variable bit rate (VBR) PVCs. You cannot use WRED on PVCs configured for an unspecified bit rate (UBR).

random-detect [ewc value | prec prec-value min-value max-value mark-denom][no] random-detect [ewc value | prec prec-value min-value max-value mark-denom]

set-qos-transmit value Set QoS group and send it (mark matched traffic with a new QoS value). Value is in the range 0 to 99.

transmit Forward traffic.

Table 10-1 CAR Actions (continued)

Action Description


ewc value Exponential-weighting-constant (ewc) value allows you to modify the default method that random-detect uses to calculate average queue size. Random-detect determines the average queue size based on the current queue length and the last average queue length. You can specify a value from 1 to 16.

• The higher the value, the more dependent the average is on the historical average, making WRED slow to react to changing traffic conditions that may be only temporary.

• The lower the value, the less dependent the average is on the historical average, making WRED more sensitive to rapidly changing traffic conditions.

prec Specify the precedence values according to the information in Table 10-2.




Tip In most cases, the benefits of WRED can be best realized if you use the random-detect keyword without arguments.

Use the no form of the command to disable WRED.

The following example shows the implementation of WRED.

Router(config)# policy-map lynxRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# random-detect

Bandwidth Reservation and Low-Latency Priority QueueingThis section explains how to configure bandwidth reservation and low-latency priority. These queueing methods let you offer differentiated service to customers.

The RPM-XF typically uses a single queue for packets from all traffic streams waiting for the link to transmit them in the order of their arrival. This method is simple, efficient, and offers optimal average delay per packet because it always uses the entire link bandwidth. But the single queue method does not distinguish among different traffic streams—the more traffic in a stream, the larger its share of the link bandwidth.

Bandwidth reservation divides the link bandwidth among the different traffic streams into multiple queues, with each queue receiving its fair share of the link bandwidth divided among all non-empty queues. You do not waste bandwidth associated with an empty queue, and by dividing the unused bandwidth to the queues with packets to send, multiple queueing has the same average delay per packet as the single queue scheme, with the advantage of fairness.

Low-latency priority queueing lets you assign a guaranteed minimum bandwidth to one queue to minimize the packet-delay variance for delay-sensitive traffic, such as live voice and video.

Note Bandwidth and low-latency priority cannot be combined in the same class.

Bandwidth Reservation Queueing

Use the bandwidth command to create multiple class queues.

bandwidth rate-in-kbps

Table 10-2 Precedence Values

Value Description

precedence A value from 0 to 7. 0 typically represents low-priority traffic that can be aggressively managed (dropped) ; 7 represents high-priority traffic.

min-value Specifies a minimum threshold. Enter a value in the range of 32 to 16,384.

max-value Specifies a maximum threshold. Enter a value in the range of 32 to 16,384.

mark-denom Specifies drop probability. Enter a value in the range of 1 to 65,535. For example, if you set this value to 256, 1 out of 256 packets is dropped when the average queue is at the maximum threshold.




[no] bandwidth

The rate-in-kbps parameter is a value in the range from 8 to 2,000,000 representing between 1% to 99% of the link bandwidth.

Use the no form of the command to disable bandwidth queueing.

The following sample configuration creates two class queues.

• A 18 kbps queue for packets with IP precedence bit settings of 1, 2, 3, or 4.

• A 54 kbps queue for packets with IP precedence bit settings of 5, 6, or 7.

Assuming that the interface has 128 kbps bandwidth, the two class queues receive 25% and 62% of the interface bandwidth. All other traffic, including IP precedence 0, receives the rest of the bandwidth—8 kbps or 13%.

Router# enableRouter# configure terminalRouter(config)# class-map cityRouter(config-cmap)# match ip precedence 1 2 3 4Router(config-cmap)# class-map bostonRouter(config-cmap)# match ip precedence 5 6 7Router(config-cmap)# policy-map precedence-queuesRouter(config-pmap)# class cityRouter(config-pmap-c)# bandwidth 16Router(config-pmap-c)# class bostonRouter(config-pmap-c)# bandwidth 40Router(config-pmap-c)# interface switch1:1Router(config-if)# service-policy output precedence-queuesRouter(config-if)# end

The actual throughput of a queue may be higher when one or more of the other queues on the link are idle.

Low-Latency Priority Queueing

Low-latency priority queueing lets you assign a specified share of the link bandwidth to one queue that receives priority over all others. Low-latency priority queueing minimizes the packet-delay variance for delay-sensitive traffic, such as live voice and video.

Use the priority command to create a low-latency priority queue.

priority rate-in-kbps[no] priority

The rate-in-kbps parameter is a value in the range from 8 to 2,000,000, representing the guaranteed minimum bandwidth.

Use the no form of the command to disable priority queueing.

The following sample configuration creates a priority queue for voice traffic, and applies it to interface switch1.1.

Router# enableRouter# configure terminalRouter(config)# class-map voiceRouter(config-cmap)# match ip rtp 2000 2000Router(config-cmap)# policy-map voice-queueRouter(config-pmap)# class voiceRouter(config-pmap-c)# priority 56Router(config-pmap-c)# interface switch1:1Router(config-if)# service-policy output voice-queueRouter(config-if)# end




The actual throughput of a priority queue may be higher than the minimum because it allocates the entire link bandwidth to a priority queue if all the other queues on the link are empty.

Generic Traffic ShapingThe RPM-XF uses traffic shaping as a mechanism to control or modify the flow of traffic on an interface to meet the requirements of a remote site, or to conform to a service rate that is provided on that interface. Generic Traffic Shaping (GTS) supports traffic shaping on all interfaces regardless of the encapsulation of the interface.

There are two implementations of traffic shaping in the current Cisco IOS software: GTS and Frame Relay Traffic Shaping (FRTS). This section describes GTS.

Note The RPM-XF does not support Frame Relay.

Note Use the traffic shape command in policy map class configuration mode. It is not supported in interface configuration mode.

The traffic shape command limits the throughput equal to rate-in-kbps.

shape rate-in-kbps[no] shape

The rate-in-kbps parameter is a value in the range from 56 to 2,000,000, representing the maximum throughput allowed.

Use the no form of the command to disable traffic shaping.

In the following sample configuration, the traffic shape is set to a throughput of 100.

Router(config-pmap-c)# shape 100Router(config-pmap-c)#

Specifying a Queue LimitThis section describes how to specify the number of packets held by the queue. Increase the queue limit to reduce the number of packets dropped due to temporary congestion on the assigned interface. Queue limit operates on the default packet drop method of congestion management.You cannot use the queue limit command on ATM PVCs configured for unspecified bit rate (UBR).

Note On the ATM interface, you can only apply queue limits on variable bit rate (VBR) PVCs.

queue-limit packets[no] queue-limit

The packets parameter is a number of packets from 32 to 16,384 in powers of 2 (for example, 64, 128, 256).




Note If the number of packets specified is not a power of 2, the number entered is automatically rounded up to a power of 2. For example, if the number of packets is entered as 60, it will be rounded up to 64.

Use the no form of the command to return the queue limit to its default value.

Use the show interface command to determine the current queue limit. If you set the queue limit to a high value, this may reduce the number of packet buffers available to other interfaces.

In the following example, the queue limit is set to 256 packets:

Router(config)# policy-map lynxRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# queue-limit 256

Applying Set ValuesThe set command allows you to mark bit values that can be used by other routers to manage QoS.

set {ip {dscp value | precedence value} | qos-group value | atm-clp | mpls experimental value}[no] set {ip {dscp value | precedence value} | qos-group value | mpls experimental value}

Externally visible values are the following.

Internally visible values are the following.

Use the no form of the command to return the set values to their defaults.

In the following sample configuration, bit values are set for IP precedence and a QoS group.

Router(config)# policy-map lynxRouter(config-pmap)# class mink


dscp A value between 0 and 63.

precedence A precedence bit setting between 0 and 7. 0 typically represents low-priority traffic; 7 represents high-priority traffic.


qos-group Sets a group ID in the routing table that can be used to classify packets into QoS groups. Values range between 0 and 99.

atm-clp Sets the ATM cell-loss priority. Use this argument to increase the likelihood that ATM cells on the specified PVC are dropped under heavy congestion.

mpls experimental A value between 0 and 7, where 0 typically represents low priority traffic and 7 represents high priority traffic.

Note set mpls experimental will cause the experimental bits to be set only on imposition frames (i.e. frames with tags being added to the MPLS tag stack).

Note set mpls experimental is only valid on an input policy map.



Chapter 10 Configuring Quality of ServiceService-Policy Command

Router(config-pmap-c)# set ip precedence 7Router(config-pmap-c)# set qos-group 8

Service-Policy CommandTo associate a policy map with an interface, use the service-policy command.

service-policy [input | output] name[no] service-policy [input | output] name

Note The bandwidth, low-latency priority, random-delete, queue limit, and shape parameters are used with output only, and are ignored when using the input argument.

Use the no form of the command to remove a service policy from an interface.

No more than two service policies can be associated with an interface, one for input and one for output.

On the ATM interface, you can only apply a policy map on a PVC.

In the following example, the policy map lynx is applied to the incoming traffic on an interface of the Gigabit Ethernet line card.

Note CEF switching must be on to use the service-policy command.

Router(config)# interface gigabitethernet 1/0Router(config-if)# service-policy input lynx

In the following example, a policy map is applied to an ATM PVC.

Router(config)# interface switch1.1Router(config-if)# pvc 0/101Router(config-if-atm-vc)# service-policy input lynx


input Incoming traffic on an interface.

output Outgoing traffic on an interface.

name Name of a policy map.



Chapter 10 Configuring Quality of ServiceShow Commands

Show CommandsThis section lists show commands you can use to get information about class maps and policy maps.

show policy mapThis command displays the configuration of one or all policy maps and lists information about the configurations. For example,

Router# show policy-map lynx Policy Map lynx class mink set qos-group 8 Policy Map jaguar class class-default random-detect random-detect exponential-weighting-constant 9 random-detect precedence 0 16 32 10 random-detect precedence 1 18 32 10 random-detect precedence 2 20 32 10 random-detect precedence 3 22 32 10 random-detect precedence 4 24 32 10 random-detect precedence 5 26 32 10 random-detect precedence 6 28 32 10 random-detect precedence 7 30 32 10

show policy-map interfaceThis command displays statistics of a policy map on one or all interfaces. This example shows statistics for a particular serial interface.

Router# show policy-map interface [pos1/0] Pos1/0 service-policy input: lynx class-map: mink (match-all) 0 packets, 0 bytes 5 minute rate 0 bps match: access-group 3 set: qos-group 8

show class-mapThis command lists the class maps and displays their match statements. For example,

Router# show class-map mink Class Map match-all mink (id 3) Match access-group 3

Class Map match-all pink (id 4) Match access-group 23 Match qos-group 32

Class Map match-any class-default (id 0) Match any Class Map match-all customer_pri (id 2)



Chapter 10 Configuring Quality of ServiceQuality of Service Policy Propagation Example Using Border Gateway Protocol

show vlansThis command can list up to 1000 virtual LAN subinterfaces. For example,

Router# show vlansVirtual LAN ID: 1 (IEEE 802.1Q Encapsulation)VLAN Trunk Interface: GigabitEthernet1/0Protocols Configured: Address: Received: Transmitted: IP 200.1.1.1 18 273894058

Quality of Service Policy Propagation Example Using Border Gateway Protocol

Quality of Service (QoS) Policy Propagation using Border Gateway Protocol (QPPB) allows you to classify packets by IP precedence based on BGP community lists, BGP autonomous system paths, and access lists. After a packet has been classified, you can use other QoS features such as committed access rate (CAR) and weighted random early detection (WRED) to specify and enforce policies to fit your business model.

The example below shows how to do the following.

1. Create route maps to match BGP community lists, access lists, and BGP AS paths.

2. Apply IP precedence to routes learned from neighbors.

In this example, the RPM-XF learns routes from autonomous system (AS) 10 and AS 60. QoS policy is applied to all packets that match the defined route maps. Any packets from the RPM-XF to AS 10 or AS 60 are sent to the appropriate QoS policy (see Figure 10-2).

Figure 10-2 RPM-XF Routes and QoS Policy Application

RPM-XF ConfigurationRouter(config)# router bgp 30Router(config)# table-map precedence-mapRouter(config-router)# neighbor 20.20.20.1 remote-as 10Router(config-router)# neighbor 20.20.20.1 send-communityRouter(config-router)# neigh 20.20.20.1 route-map precedence-map out!Router(config)# ip bgp-community new-format

Match community 1, set the IP precedence to priority, and set the QoS group to 1.

Router(config)# route-map precedence-map permit 10Router(config-route-ma)# match community 1Router(config-route-ma)# set ip precedence priority

RPM-XF

2. Route arrives3. QoS policy applied

1. Route announced

4. Packet sent with QoS policy

RouterB

Autonomoussystem 30

7564

8

Autonomoussystem 60

Autonomous

system 10




Router(config-route-ma)# set ip qos-group 1

Match community 2 and set the IP precedence to immediate.

Router(config)# route-map precedence-map permit 20Router(config-route-ma)# match community 2Router(config-route-ma)# set ip precedence immediate

Match community 3 and set the IP precedence to Flash.

Router(config)# route-map precedence-map permit 30Router(config-route-ma)# match community 3Router(config-route-ma)# set ip precedence flash

Match community 4 and set the IP precedence to Flash-override.

Router(config)# route-map precedence-map permit 40Router(config-route-ma)# match community 4Router(config-route-ma)# set ip precedence flash-override

Match community 5 and set the IP precedence to critical.

Router(config)# route-map precedence-map permit 50Router(config-route-ma)# match community 5Router(config-route-ma)# set ip precedence critical

Match community 6 and set the IP precedence to internet.

Router(config)# route-map precedence-map permit 60Router(config-route-ma)# match community 6Router(config-route-ma)# set ip precedence internet

Match community 7 and set the IP precedence to network.

Router(config)# route-map precedence-map permit 70Router(config-route-ma)# match community 7Router(config-route-ma)# set ip precedence network

Match ip address access list 69 or match AS path 1, set the IP precedence to critical, and set the QoS group to 9.

Router(config)# route-map precedence-map permit 75Router(config-route-ma)# match ip address 69Router(config-route-ma)# match as-path 1Router(config-route-ma)# set ip precedence criticalRouter(config-route-ma)# set ip qos-group 9

For everything else, set the IP precedence to routine.

Router(config)# route-map precedence-map permit 80Router(config-route-ma)# set ip precedence routine

Define the community lists.

Router(config)# ip community-list 1 permit 60:1Router(config)# ip community-list 2 permit 60:2Router(config)# ip community-list 3 permit 60:3Router(config)# ip community-list 4 permit 60:4Router(config)# ip community-list 5 permit 60:5Router(config)# ip community-list 6 permit 60:6Router(config)# ip community-list 7 permit 60:7

Define the AS path.

Router(config)# ip as-path access-list 1 permit ^10_60




Define the access list.

Router(config)# access-list 69 permit 69.0.0.0

Router B Running ConfigurationRouterB(config)# router bgp 10RouterB(config-router)# neighbor 30.30.30.1 remote-as 30RouterB(config-router)# neighbor 30.30.30.1 send-communityRouterB(config-router)# neigh 30.30.30.1 route-map send_community out!RouterB(config)# ip bgp-community new-format

Match prefix 10 and set community to 60:1.

RouterB(config)# route-map send_community permit 10RouterB(config-route-ma)# match ip address 10RouterB(config-route-ma)# set community 60:1













For all others, set community to 60:8.

RouterB(config)# route-map send_community permit 80RouterB(config-route-ma)# set community 60:8

Define the access lists.

RouterB(config)# access-list 10 permit 61.0.0.0RouterB(config)# access-list 20 permit 62.0.0.0RouterB(config)# access-list 30 permit 63.0.0.0RouterB(config)# access-list 40 permit 64.0.0.0RouterB(config)# access-list 50 permit 65.0.0.0




RouterB(config)# access-list 60 permit 66.0.0.0RouterB(config)# access-list 70 permit 67.0.0.0

The following example shows how to configure several interfaces to classify packets based on the IP precedence and QoS group ID.

interface switch1.1ip address 200.28.38.2 255.255.255.0bgp-policy source ip-prec-mapno ip mroute-cacheno cdp enableframe-relay interface-dlci 20 IETF

interface switch1.2ip address 200.28.28.2 255.255.255.0bgp-policy source qos-groupno ip mroute-cacheno cdp enable



Chapter 10 Configuring Quality of ServiceVersatile Traffic Management System (VTMS)

Versatile Traffic Management System (VTMS)Versatile Traffic Management System (VTMS) on the RPM-XF allows bandwidth sharing between VCs (virtual channels). When a VC is idle, its bandwidth can be used by other VCs. It allows all VCs to share the same VTMS link and supports ATM and either POS (Packet Over SONET) or GigE links.

VTMS on the RPM-XF uses a bandwidth divisor of 65535, and uses dummy full queues to handle traffic congestion. It allows packet dropping, including UBR (undefined bit rate) packet dropping.

VTMS uses the flow bits in the packet header to suppress packet dequeuing.

There are two kinds of flow bit controls:

• software flow bits

• hardware queue statuses

A packet is enqueued if both the software flow bits and the hardware queue statuses indicate ready and is dequeued if both the software flow bits and the hardware queue statuses indicate congestion.

When a packet is enqueued it adds a flow bit to a flow bit table. The flow bit table is used to determine whether a line card is congested. When a line card is congested, VTMS creates a dummy full queue, which forces the packet to be dropped or dequeued.

Note VTMS uses dummy full queues for UBR also; however, since RPM-XF drops headers in UBR packets, UBR packets are dropped if there is traffic congestion on the interface.

Note VTMS on the RPM-XF is enabled by default.

VTMS Buffer ManagementIn VTMS, it is important to recognize the difference between buffers and queues:

• Buffers are memory areas that only store the packets. RPM-XF has 128 MB of buffer memory.

• Queues are data structures that point to packets in the buffers in a specific order.

Packets are grouped by class and are queued in a first-in-first-out order (fifo). Packets are then directed to one of three possible path:

• fast path

• punt path

• drop path

The memory buffers can be configured by the administrator and allocated during initialization. The administrator can configure up to eight memory buffer pools, designated as pool 0 through pool 7. An example memory buffer pool allocation is as follows:

• pool 0: 9216 bytes–total 100







Chapter 10 Configuring Quality of ServiceVersatile Traffic Management System (VTMS)


Buffer Management CLI Commandsshow pxf cpu buffersshow pxf cpu buffers leaked <pool no>

VTMS Queuing

Queues are data structures that point to packets in the buffer in a specific order based on the VTMS configuration. VTMS assign packets to one of the following two classes of queues:

Work queues

Packet queues

Queuing techniques depends on QoS features required, throughput, latency, and packet sizes. Queuing on the RMP-XF is optimized for low and high speed interfaces that experience small packets, low latency, and advanced QoS.

The VTMS scheduler determines how packets are directed. After packets are assigned to a class, VTMS scheduler directs them to one the following different types of queues based on the VTMS configuration.

• First-In-First-Out (FIFO)

• Fair Queuing

• Weighted Fair Queuing (WFQ)

• Class Based WFQ (CBWFQ)

• Low Latency Priority Queuing (LLQ)

• Custom Queuing

First-In-First-Out (FIFO) queuing is the highest priority type of queuing and is used for control traffic such as routing updates.

Fair Queuing services packets based on flow and packet sizes, so that smaller packets do not get stuck behind larger packets.

Weighted Fair Queuing (WFQ) services packets based on weight. The weight is assigned to each work queue based on the IP precedence value of the packets in that queue.

Class Based WFQ (CBWFQ) services classified traffic. Classified traffic is configured by the user. The weights are configured by VTMS based on bandwidth for that queue.

Low Latency Priority Queuing (LLQ) is an additional queue created on demand after it has been configured to do so. LLQ services classified packets that are sent to it and is used for small packets and voice.

Custom Queuing services packets in a round robin manner, based on specific user configuration information. Custom Queuing can service up to 16 queues.

Queuing CLI Commands

show pxf cpu queue <interface> - summarized infoshow pxf cpu queue <qid> - detailed info including CIR, MIR, EIR, stats, etc.show pxf cpu statistics qos <interface>show pxf cpu police <policy map>



Chapter 10 Configuring Quality of ServiceMultiLink PPP/Link Fragmentation Interleaving (MLP/LFI)

MultiLink PPP/Link Fragmentation Interleaving (MLP/LFI)MultiLink PPP/Link Fragmentation Interleaving (MLP/LFI) allows a large packet to be divided into smaller fragments so that excessive head of line blocking can be avoided for smaller packets such as VoIP packets.

On slow speed interfaces (slower than T1), a packet with maximum MTU (maximum transmission unit) can cause excessive head of line blocking in LLQs (low latency priority queues) especially in VoIP (Voice over IP) applications. The solution is to implement MLP/LFI on these interfaces.

The RPM-XF supports MLP/LFI on MLPPP interfaces and supports up to 200 MLP/LFI-enabled interfaces. MLP/LFI and PPP interfaces use the MLPPP (Multilink Point-to-Point Protocol) long sequence number fragment format headers.

MLP/LFI over multiple links in an MLPPP bundle is not supported. Receiving and reassembling out of sequence fragments is also not supported.

If a packet is dequeued, MLP/LFI will reschedule and retransmit each fragment separately. MLP/LFI will then reassemble the packet at the far end only after all the fragments have been received.

MLP/LFI ConfigurationThe following configuration commands can be used to configure MLP/LFI:

Using the match ip rtp command is just one way of classifying traffic for interleaving. You can also use an access list. The policy-map command associates a class of traffic to a priority queue, and the priority command sets the priority of that class within the policy-map. The service policy then attaches that classification and action to an interface. For example:

class-map match-all VOIP match ip rtp 16384 16383

class-map LESS_CRITICAL match access-group 101 policy-map VOIP_PRI class VOIP priority 50 class LESS_CRITICAL set ip precedence 5 interface sw1.100 point-to-point

Table 10-1 MLP/LFI Configuration Commands

Command Description

ppp multilink Enable multilink on the interface.

ppp multilink fragmentation Enable multilink fragmentation.

ppp multilink fragment-delay<milliseconds>

Set the maximum delay (in milliseconds) between fragments. For example, you can configure a voice stream with a maximum delay of 20 milliseconds. The MLPPP will choose a fragment size based on this value.

ppp multilink interleave Enable real-time packet interleaving on bundled transmissions.

match ip rtp<starting-port-number><range-of-ports>

Configure which traffic will be prioritized for interleaving based on the starting-port-number or range-of-ports. These assignments can be used to map packets to a specific class.



Chapter 10 Configuring Quality of ServiceInternet Protocol Header Compression (IPHC)

pvc toortr01 0/58 vbr-nrt 406 406protocol ppp Virtual-Template15interface Virtual-Template15bandwidth 320ip address 10.16.0.105 255.255.255.252ip tcp header-compression iphc-formatservice-policy output VOIP_PRIppp multilinkppp multilink fragment-delay 14ppp multilink interleaveip rtp header-compression iphc-format

Internet Protocol Header Compression (IPHC)Internet Protocol Header Compression (IPHC) allows low speed links to run more efficiently when IP headers are extremely large or of comparable size to the payload. IPHC supports compressed Routing Table Protocol (cRTP), compressed User Datagram Protocol (cUDP), and compressed Transport Control Protocol (cTCP). IPHC is supported on PPPoA and MLP links, can have up to 200 total interfaces and a maximum of 512 configurable connections per interface.

An IPHC-enabled interface sends only changes to the header instead of sending the entire header with every packet. At the beginning of a transmission, the transmitting end (the compressor) sends a full header packet to the receiving end (the decompressor). After the initial packet is sent, the compressor sends all other packets with headers that contain only the differences between them and the original full header. The decompressor maintains a copy of the original full header and reconstructs all the other packet headers by adding the changes to them.

The header data that is different with each packet is referred to as the session state and is identified by a session ID or connection ID.

When the decompressor receives a compressed packet, it reconstructs the packet header by adding the difference to the saved uncompressed header. In the typical case, IPHC enables the header to be compressed to two bytes (four bytes if UDP checksums are used).

The following fields in a packet header usually remain the same through out a transmission:

• IP source and destination addresses

• User Datagram Protocol (UDP) source and destination ports

• Routing Table Protocol (RTP) SSRC fields

The following fields in a packet header usually change during a transmission:

• IP packet ID

• UDP checksum

• RTP sequence number

• RTP time stamp

• The RTP marker bit




Note RPM-XF does NOT support TCP compression. TCP packets are transmitted un-compressed. The decompression of compressed TCP packets is done by punting them to the route processor. A separate queue between the PXF and the route processor is used for compressed TCP traffic. TCP packets are dropped at speeds above 2.4 Mbps. It is not recommended to carry TCP traffic on an IPHC enabled interface , especially if the customer edge router can NOT stop TCP compression selectively.

cRTP ConfigurationIPHC provides the following CLI commands to enable cRTP on an interface:

The following cRTP statistics are supported on the RPM-XF:

Table 10-3 cRTP Configuration Commands

Command Description

ip rtp header-compression Enable RTP header compression on an interface. The recommended value for RPM-XF is 512.

no ip rtp header-compression Disable RTP header compression on an interface.

ip rtp compression-connections <number>

Specifies the total number of RTP header compression connections supported on the interface. The default is 16. The maximum is 512. To reduce collision probability, configure the number of connections to 512 and never have more than 128 active flows at any time.

no ip rtp compression-connections

Set the RTP connections back to the default–16.

clear ip rtp header-compression

Reset all statistics for the interface to zero.

show ip rtp header-compression [interface]

Show all statistics for the interface.

show ip tcp header-compression [interface]

Show TCP decompression statistics for the interface.

clear ip tcp header-compression

Reset TCP decompression statistics for the interface.

sh pxf cpu queue RP Show the cTCP packets punted to the route processor.

sh pxf cpu queue <qid> Use the dedicated Queue ID (qid) for cTCP queue.

show hard pxf cpu statistics crtp [interface]

Show all PXF IPHC statistics for an interface. The statistics of any processing done by the route processor will not be reflected in this information.

show int <interface> rpmxf-iphc-db

Show interface IPHC database for debugging.




Examples

show hard pxf cpu statistics crtp [interface]

Interface Virtual-Access#: Rcvd: 51564 compressed 1 fullheaderin 0 dropped Sent: 0 compressed, 0 fullheaderout Connect: 512 max_cid, 0 collisions Context: 4198 sent, 0 rcvd 0 compressed TCP packets dropped 0 punted to RP due to IP options/RTP ext/CSRC 0 sent uncompresssed

show int <interface> rpmxf-iphc-db

Interface : Switch1.3701IPHC enabled: yes IPHC id: 2 vcci: 8 states: 512 hashMask: 0x1FFIPHC disabled and then not enabled via negotiation: yesIPHC enabled on PXF(read from PXF): yesTx stats in shadow memory:compressedout 0 uncompressedout 0 fullheaderout 0cs_packet_rcvd 0 num_cid_collisions 0Rx stats in shadow memory:compressedin 0 tossed packets(bad CRC) 0 compressed_tcp_in 0cs_packet_sent 0 punted(IP options/RTP ext/CSRC list) 0show rpm iphc allocated-ids - Show IPHC ids allocated

Table 10-4 cRTP Statistics

Statistic Description

Rcvd:

total Total packets processed by the decompressor.

compressed Compressed RTP/UDP packets received.

status msgs Context status messages received. This is sent by the decompressor when it finds issue with the sequence number of the compressed packet received.

dropped Indicates the number of compressed packets received after sending a context status message. These packets are dropped.

Sent:

total Total packets processed by the compressor.

compressed Compressed RTP/UDP packets sent

status msgs Context status messages sent. This is sent by the decompressor when it finds issue with the sequence number of the compressed packet received.

Connect:

collisions Number of uncompressed packets sent when a free connection ID could not be found after retries.

rx slots, tx slots Indicates the number of cRTP connections configured for the interface (if the interface specified is Virtual-template) or the negotiated connections (if the interface specified is virtual-access).




show rpm iphc connection - Show IPHC conn: buffer for a given iphc id and cidshow rpm iphc entry - Show IPHC entry for a given IPHC idshow rpm iphc num-active-ids - Show number of IPHC ids allocated

A-1Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


A P P E N D I X AMaintaining the MGX RPM-XF

This appendix describes maintenance procedures you might need to perform as your internetworking needs change. Appendix A contains the following sections:

• Reading Front Panel LEDs

• Recovering a Lost Password

• Virtual Configuration Register Settings

• Copying a Cisco IOS Image to Bootflash

• Recovering Boot and System Images

Reading Front Panel LEDsThe LEDs on the front panel of the RPM-XF indicate the current operating condition of the RPM-XF. You can observe the LEDs, note the fault condition the RPM-XF is encountering, and contact your system administrator or TAC, if necessary.

Figure A-1 shows the front panel and LEDs of the RPM-XF. Table A-1 describes how to interpret front-panel LED activity.



Appendix A Maintaining the MGX RPM-XFReading Front Panel LEDs

Figure A-1 MGX RPM-XF Front Panel LEDs

The LEDs are labeled and indicate overall status and activity on ports by flickering. When there is heavy activity on a port, the LED might be on constantly. If an LED is not on when the port is active and the cable is connected correctly, there might be a problem with the port.

7553

4

LM2 OK

RPM-XF

LM1 OK

CB RX

CB TX

CPU OK

LM2 OK

LM1 OK

CB RX

CB TX

CPU OK

Table A-1 Front Panel LEDs

LED NAME COLOR DEFINITION

CPU OK Off CPU is not operational

Green Card is Active

Yellow Card is Standby

Red Card has Failed



Appendix A Maintaining the MGX RPM-XFRecovering a Lost Password

Recovering a Lost PasswordThis section describes how to recover a lost enable or console login password, and how to replace a lost enable secret password on your RPM.

Note It is possible to recover the enable or console login password. The enable secret password is encrypted, however, and must be replaced with a new enable secret password.

Following is an overview of the steps in the password recovery procedure:

• If you can log in to the RPM-XF, enter the show version command to determine the existing configuration register value.

• Press the Break key to get to the bootstrap program prompt (ROM monitor). You might need to reload the system image by power cycling the RPM-XF.

• Change the configuration register so the following functions are enabled: Break; ignore startup configuration; boot from bootflash memory.

Note The key to recovering a lost password is to set the configuration register bit 6 (0x0040) so that the startup configuration (usually in NVRAM) is ignored. This will allow you to log in without using a password and to display the startup configuration passwords.

• Power cycle the RPM-XF by turning power off and then back on.

• Log in to the RPM-XF and enter the privileged EXEC mode.

• Enter the show startup-config command to display the passwords.

– Recover or replace the displayed passwords.

– Change the configuration register back to its original setting.

CB TX Off Cells are not being transmitted to the cellbus

Green Cells are being transmitted to the cellbus

CB RX Off Cells are not being received from the cellbus

Green Cells are being received from the cellbus

LM1 OK Off Back card in bay 1 is not present

Green Back card in bay 1 is present and cable connected

Red Back card in bay 1 is present but cable is not connected

LM2 OK Off Back card in bay 2 is not present

Green Back card in bay 2 is present and cable connected

Red Back card in bay 2 is present but cable is not connected

Table A-1 Front Panel LEDs (continued)

LED NAME COLOR DEFINITION




Note To recover a lost password if Break is disabled on the RPM-XF, you must have physical access to the RPM-XF.

Password Recovery ProcedureComplete the following steps to recover or replace a lost enable, enable secret, or console login password.

Step 1 Attach an ASCII terminal to the console port on your MGX-XF-UI back card.

Step 2 Configure the terminal to operate at 9600 baud, 8 data bits, no parity, and 1stop bit. If you have changed the configuration parameters of the console port, then configure the terminal to use those parameters instead.

Step 3 If you can log in to the RPM-XF as a non privileged user, enter the show version command to display the existing configuration register value. Note the value for use later. If you cannot log in to the RPM-XF, go to the next step.

Step 4 Press the Break key or send a Break from the console terminal.

If Break is enabled, the RPM-XF enters the ROM monitor, indicated by the ROM monitor prompt (rommon 1>). Proceed to Step 6. If Break is disabled, power cycle the RPM-XF. (Remove the RPM-XF from the MGX 8850 chassis and then reinsert it.) Then proceed to Step 5.

Step 5 Within 60 seconds of restoring the power to the RPM-XF, press the Break key or send a Break.

This action causes the RPM-XF to enter the ROM monitor and display the ROM monitor prompt (rommon 1>).

Step 6 To set the configuration register on an RPM-XF, use the configuration register utility by entering the confreg command at the ROM monitor prompt as follows:

rommon 1> confreg

Answer yes to the enable question “ignore system config info?” Note the current configuration register settings.

Step 7 Initialize the RPM-XF by entering the reset command as follows:

rommon 2> reset

The RPM-XF will initialize, the configuration register will be set to 2142, and the RPM-XF will boot the system image from Flash memory and enter the system configuration dialog (setup) as follows:

--- System Configuration Dialog --

Step 8 Enter no in response to the system configuration dialog prompts until the following message is displayed:

Press RETURN to get started!

Step 9 Press Return. The user EXEC prompt is displayed as follows:

Router>




Step 10 Enter the enable command to enter the privileged EXEC mode.

Then enter the show startup-config command to display the passwords in the configuration file as follows:

Router# show startup-config

Step 11 Scan the configuration file display looking for the passwords (the enable passwords are usually near the beginning of the file, and the console login or user EXEC password is near the end). The passwords displayed will look something like this:

enable secret 5 $1$ORPP$s9syZt4uKn3SnpuLDrhueienable password 23skiddoo..line con 0 password onramp

The enable secret password is encrypted and cannot be recovered; it must be replaced. The enable and console passwords may be encrypted or clear text. Proceed to the next step to replace an enable secret, console login, or enable password. If there is no enable secret password, note the enable and console login passwords if they are not encrypted and proceed to Step 16.

Caution Do not start the next step unless you determine you must change or replace the enable, enable secret, or console login passwords. Failure to follow the steps as shown may cause you to erase your RPM-XF configuration.

Step 12 Enter the configure memory command to load the startup configuration file into running memory. This action allows you to modify or replace passwords in the configuration.

Router# configure memory

Step 13 Enter the privileged EXEC command configure terminal to enter configuration mode.

Router# configure terminal

Step 14 To change all three passwords, enter the following commands:

Router(config)# enable secret newpassword1Router(config)# enable password newpassword2Router(config)# line con 0Router(config-line)# password newpassword3

Change only the passwords necessary for your configuration. You can remove individual passwords by using the no form of the above commands. For example, entering the no enable secret command will remove the enable secret password.

Step 15 You must configure all interfaces to not administratively shutdown as follows:

Router(config)# interface fastethernet 2/0Router(config-int)# no shutdown

Enter the equivalent commands for all interfaces that were originally configured. If you omit this step, all interfaces will be administratively shutdown and unavailable when the RPM-XF is restarted.

Step 16 Use the config-register command to set the configuration register to the original value noted in Step 3 or Step 7, or to the factory default value 0x2102 as follows:

Router(config)# config-register 0x2102

Step 17 Press Ctrl-Z or enter end to exit configuration mode and return to the EXEC command interpreter.



Appendix A Maintaining the MGX RPM-XFVirtual Configuration Register Settings

Caution Do not start the next step unless you have changed or replaced a password. If you skipped Step 12 through Step 15, skip to Step 19. Failure to observe this caution will cause you to erase your RPM-XF configuration file.

Step 18 Enter the copy running-config startup-config command to save the new configuration to nonvolatile memory.

Step 19 Enter the reload command to reboot the RPM-XF.

Step 20 Log in to the RPM-XF with the new or recovered passwords.

This routine completes the steps for recovering or replacing a lost enable, enable secret, or console login password.

Virtual Configuration Register SettingsThe RPM-XF has a 16-bit virtual configuration register, which is written into NVRAM. You might want to change the virtual configuration register settings for the following reasons:

• Set and display the configuration register value.

• Force the system into the ROM monitor or boot ROM.

• Select a boot source and default boot filename.

• Enable or disable the Break function.

• Control broadcast addresses.

• Set the console terminal baud rate.

• Recover a lost password (ignore the configuration file in NVRAM).

• Enable Trivial File Transfer Protocol (TFTP) server boot.

Table A-2 lists the meaning of each of the virtual configuration memory bits and defines the boot field names.

Caution To avoid confusion and possibly halting the RPM-XF, remember that valid configuration register settings might be combinations of settings and not just the individual settings listed in Table A-2. For example, the factory default value of 0x2102 is a combination of settings.

Table A-2 Virtual Configuration Register Bit Meaning

Bit No.1 Hexadecimal Meaning

00–03 0x0000–0x000F Boot field

05 0x0020 Console line speed

06 0x0040 Causes system software to ignore the contents of NVRAM (startup-config)

07 0x0080 OEM bit is enabled

08 0x0100 Break is disabled




Changing Configuration Register SettingsComplete the following steps to change the configuration register while running Cisco IOS software.

Step 1 Enter the enable command and your password to enter privileged mode.

Router> enablepassword: enablepasswordMGX 8850-RPM#

Step 2 Enter the configure terminal command at the privileged-level system prompt (#).

Router# configure terminal

Step 3 To set the contents of the configuration register, enter the configuration command config-register 0x<value>, where value is a hexadecimal number (see Table A-2 and Table A-3).

Router(config)# config-register 0xvalue

(The virtual configuration register is stored in NVRAM.)

Step 4 Press Ctrl-Z to exit configuration mode.

The new settings will be saved to memory; however, the new settings are not effective until the system software is reloaded by rebooting the RPM-XF.

Step 5 To display the configuration register value currently in effect and the value that will be used at the next reload, enter the show version EXEC command. The value displays on the last line of the screen display.

Configuration register is 0x142 (will be 0x102 at next reload)

10 0x0400 IP broadcast with all zeros

11–12 0x0800–0x1000 Console line speed

13 0x2000 Load the boot ROM software if a Flash boot fails five times

14 0x4000 IP broadcasts do not have network numbers

15 0x8000 Enable diagnostic messages and ignore the contents of NVRAM

1. The factory default value for the configuration register is 0x2102. This value is a combination of the following: bit 13 = 0x2000, bit 8 = 0x0100, and bits 00 through 03 = 0x0002.

Table A-2 Virtual Configuration Register Bit Meaning (continued)

Bit No.1 Hexadecimal Meaning

Table A-3 Explanation of Boot Field (Configuration Register Bits 00 to 03)

Boot Field Boot Process

0x0 Stops the boot process in the ROM monitor.

0x1 Stops the boot process in the boot ROM monitor.

0x2 Full boot process, which loads the Cisco IOS image in Flash memory.

0x3–0xF Specifies a default filename for booting over the network from a TFTP server. Enables boot system commands that override the default filename for booting over the network from a TFTP server.




Step 6 Reboot the RPM-XF.

The new value takes effect. Configuration register changes take effect only when the RPM-XF restarts, which occurs when you turn the system on or when you enter the reload command.

Virtual Configuration Register Bit MeaningsThe lowest four bits of the virtual configuration register (bits 3, 2, 1, and 0) form the boot field (see Table A-3). The boot field specifies a number in binary form. If you set the boot field value to 0, you must boot the operating system manually by entering the b command at the bootstrap prompt. For example

> b [ tftp ] bootflash filename

The b command options are as follows:

• b—Boots the default system software from ROM

• b bootflash—Boots the first file in bootflash memory

• b filename [host]—Boots from the network using a TFTP server

• b bootflash [filename]—Boots the file filename from bootflash memory

For more information about the command b [tftp] bootflash filename, refer to the Cisco IOS configuration publications.

If you set the boot field value to a value of 0x2 through 0xF, and a valid system boot command is stored in the configuration file, the RPM-XF boots the system software as directed by that value. If you set the boot field to any other bit pattern, the RPM-XF uses the resulting number to form a default boot filename for booting from the network using a TFTP server. (See Table A-4.)

Table A-4 Default Boot Filenames

Filename Bit 3 Bit 2 Bit 1 Bit 0

bootstrap mode 0 0 0 0

ROM software 0 0 0 1

cisco2-RPM-XF 0 0 1 0















In the following example, the virtual configuration register is set to boot the RPM-XF from bootflash memory and to ignore Break at the next reboot of the RPM-XF.

Router> enablePassword: enablepasswordRouter#config terminalEnter configuration commands, one per line. End with CTRL/Z Router(config)#config-register 0x2102Router(config)#no boot system Router(config)#boot system bootflash:rpmxf-p12-mz.122-7b.binRouter(config)#end

The RPM-XF creates a default boot filename as part of the automatic configuration processes. The boot filename consists of cisco plus the octal equivalent of the boot field number, a hyphen, and the processor type.

Note A boot system configuration command in the RPM-XF configuration in NVRAM overrides the default boot filename.

Bit 8 controls the console Break key. Setting bit 8 (the factory default) causes the processor to ignore the console Break key. Clearing bit 8 causes the processor to interpret the Break key as a command to force the system into the bootstrap monitor, thereby halting normal operation. A break can be sent in the first 60 seconds while the system reboots, regardless of the configuration settings.

Bit 10 controls the host portion of the IP broadcast address. Setting bit 10 causes the processor to use all zeros; clearing bit 10 (the factory default) causes the processor to use all ones. Bit 10 interacts with bit 14, which controls the network and subnet portions of the broadcast address. (See Table A-5.)

Bits 5, 11, and 12 in the configuration register determine the baud rate of the console terminal. Table A-6 shows the bit settings for the available baud rates. (The factory-set default baud rate is 9600 baud.)



Table A-4 Default Boot Filenames (continued)

Filename Bit 3 Bit 2 Bit 1 Bit 0

Table A-5 Configuration Register Settings for Broadcast Address Destination

Bit 14 Bit 10 Address (<net > <host>)

Off Off <ones> <ones>

Off On <zeros> <zeros>

On On <net> <zeros>

On Off <net> <ones>

Table A-6 System Console Terminal Baud Rate Settings

Baud Bit 12 Bit 11 Bit 05

1200 1 0 0

2400 1 1 0



Appendix A Maintaining the MGX RPM-XFCopying a Cisco IOS Image to Bootflash

Bit 13 determines the server response to a bootload failure. Setting bit 13 causes the server to load operating software from ROM after five unsuccessful attempts to load a boot file from the network. Clearing bit 13 causes the server to continue attempting to load a boot file from the network indefinitely. By factory default, bit 13 is set to 1.

Enabling Booting from the PXM Hard DiskTo disable break and enable booting from the PXM hard disk, use the following commands:

Router> enablePassword:enablepasswordRouter# config terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#config-register 0x2102Router(config)#no boot systemRouter(config)#boot system x:rpmxf-p12-mz.122-7b.binRouter(config)#end

Enabling Booting from BootflashTo disable break and enable booting from bootflash, use the following commands:

Router> enablePassword:enablepasswordRouter# config terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#config-register 0x2102Router(config)#no boot systemRouter(config)#boot system bootflash:rpmxf-p12-mz.122-7b.binRouter(config)#end

Copying a Cisco IOS Image to BootflashYou may need to copy a new Cisco IOS image to bootflash whenever a new image or maintenance release becomes available. Enter the copy tftp bootflash command for the copy procedure.

4800 0 1 0

9600 0 0 0

19200 0 0 1

38400 0 1 1

57600 1 0 1

115200 1 1 1

Table A-6 System Console Terminal Baud Rate Settings (continued)

Baud Bit 12 Bit 11 Bit 05



Appendix A Maintaining the MGX RPM-XFCopying a Cisco IOS Image to Bootflash

Perform the following steps to copy a new image to Bootflash memory from a TFTP server.

Step 1 Enter the show bootflash command to ensure that there is enough space available before copying a file to bootflash memory. Compare the size of the file you want to copy to the amount of available bootflash memory displayed.

Step 2 Make a backup copy of the current image.

Enter enable mode and then enter the copy bootflash tftp command. Ensure that the filename of the current image is different from the new image so that you do not overwrite it.

Step 3 Enter the copy tftp bootflash command to copy the new image into bootflash.

Router> enablePassword: enablepasswordRouter# copy tftp bootflash

Step 4 The RPM-XF prompts you for the IP address or name of the remote TFTP server.

Address or name of remote host [ ]?

Step 5 Enter the IP address or name of the remote host.

The RPM-XF then prompts you for the name of the source file.

Source filename []?

Step 6 Enter the name of the source file. The following prompt displays.

Destination filename [filename]?

Step 7 Press Return to accept the default filename or enter a different filename. A message similar to the following example displays.

Accessing tftp://hostname/rpmxf-p12-mz.122-7b.bin...Loading rpmxf-p12-mz.122-7b.bin from 172.16.72.1 (via FastEthernet2/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 2647996/5295104 bytes]

Step 8 Update your configuration to use the new software image. For example,

Router> enablePassword: enablepasswordRouter# config terminalRouter(config)# no boot systemRouter(config)# boot system bootflash:rpmxf-p12-mz.122-7b.bin

Press Ctrl-Z to exit configuration mode



The system displays an OK message when the configuration has been saved.

Step 10 Enter the reload command to reboot the RPM-XF.



Appendix A Maintaining the MGX RPM-XFRecovering Boot and System Images

Note For more information on the copy tftp bootflash command and other related commands, refer to the Cisco IOS command reference publications.

Recovering Boot and System ImagesIf your RPM-XF experiences difficulties and no longer contains a valid Cisco IOS software image in bootflash memory, the ROM Monitor contains tools to help you recover from this situation. You can recover the Cisco IOS image using one of the following ROM monitor commands:

• xmodem—Use this to download a new image directly over the console port on the management back card via the xmodem protocol.

• tftpdnld—Use this to download a new image directly from a TFTP server via one of the fast ethernet ports on the management back card.

Using the xmodem CommandEnter the xmodem command to establish a connection between a console and the router console port for disaster recovery, if both the boot and system images are erased from bootflash memory. The xmodem command syntax is the following.

xmodem [-r | -x | -c | -y] [filename]

Where:

• -r—Immediately launch the image after the download.

• -x—Use 1024 byte packets during the download.

• -c—Use CRC-16 instead of checksum during the download.

• -y—Use Y-modem (instead of X-modem) for the download.

Step 1 At the ROM Monitor prompt, issue the xmodem -r command to download a new Cisco IOS image into the RPM-XF and launch it. For example:

rommon 1> xmodem -r filename

Do not start the sending program yet...

Invoke this application only for disaster recovery.Do you wish to continue? y/n [n]: yReady to receive file ...

Step 2 Using your terminal program, start the X-modem upload.

Step 3 After the image download is complete, the ROM monitor will launch the image.

Step 4 After the Cisco IOS image loads, squeeze the bootflash as follows:

Router> enablePassword: enablepasswordRouter# squeeze bootflash:




Step 5 Copy a Cisco IOS image into bootflash.

See “Copying a Cisco IOS Image to Bootflash” section on page A-10 for additional information.

Using the tftpdnld CommandEnter the tftpdnld command on the fast ethernet ports on the MGX-XF-UI management back card to download a new Cisco IOS image for disaster recovery, if both the boot and system images are erased from bootflash memory. The tftpdnld command syntax is the following:

tftpdnld [-r]

Where

• -r—Immediately launch the image after the download.

The following variables are REQUIRED and must be set for the tftpdnld command:

• IP_ADDRESS—The IP address to use for the TFTP download.

• IP_SUBNET_MASK—The subnet mask to use for the TFTP download.

• DEFAULT_GATEWAY—The default gateway to use for the TFTP download.

• TFTP_SERVER—The IP address of the TFTP server from which to download.

• TFTP_FILE—The name of the file to download.

• TFTP_MACADDR—The MAC address to assign to the fast ethernet port for the TFTP download.

The following variables are OPTIONAL and do not have to be set for the tftpdnld command:

• TFTP_VERBOSE—Verbosity setting; 0 = quiet, 1 = progress(default), 2 = verbose

• TFTP_RETRY_COUNT—Retry count for ARP and TFTP (default = 7)

• TFTP_TIMEOUT—Overall time-out of TFTP operation in seconds (default = 7200)

• TFTP_CHECKSUM—Perform checksum test on downloaded image 0 = no, 1 = yes (default = 1)

• FE_PORT—0 = Ethernet 0 (default), 1 = Ethernet 1

• FE_SPEED_MOD —0 = 10Mbps half-duplex, 1 = 10Mbps full-duplex, 2 = 100Mbps half-duplex, 3 = 100Mbps full-duplex, 4 = Auto Speed, Auto Duplex (default)

Step 1 At the ROM Monitor prompt enter the tftpdnld -r command to download a new Cisco IOS image into the RPM-XF and launch it. For example,

rommon 1> IP_ADDRESS=10.1.0.1rommon 2> IP_SUBNET_MASK=255.255.255.0rommon 3> DEFAULT_GATEWAY=10.0.0.1rommon 4> TFTP_SERVER=10.2.0.3rommon 5> TFTP_FILE=rpmxf-p12-mz.122-7b.binrommon 6> TFTP_MACADDR=0050.3eff.f301rommon 7> tftpdnld -r

Step 2 After the image download is complete, the ROM monitor will launch the image.

Step 3 After the Cisco IOS image loads, squeeze the bootflash, as follows:

Router> enablePassword: enablepasswordRouter# squeeze bootflash:




Step 4 Copy a Cisco IOS image into bootflash. See “Copying a Cisco IOS Image to Bootflash” section on page A-10 for additional information.

B-1Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


A P P E N D I X BCable and Connector Specifications

This appendix provides the following pinout information:

• 100BaseT Fast Ethernet Specifications

• Console and Auxiliary Port Signals and Pinouts

• Fast Ethernet RJ-45 Connector Pinouts

• SFP Specifications

Note All pins not listed in the tables in this appendix are not connected.

Note Cisco Systems does not provide fast ethernet (FE) port adapter cables. These cables must be ordered from outside commercial cable vendors.

Note Cisco Systems does not provide console and auxiliary cables in the kit. Console and auxiliary cables can be ordered as spares from Cisco Systems.

100BaseT Fast Ethernet SpecificationsEach Fast Ethernet port on the MGX-XF-UI back card has an RJ-45 connector to attach to Category 5 UTP for 100BaseTX. Table B-1 lists the cabling specifications for 100-Mbps Fast Ethernet transmission over UTP cables.

Table B-1 Specifications and Connection Limits for Fast Ethernet 100-Mbps Transmission

Parameter RJ-45

Cable specification Category 51 UTP2, 22 to 24 AWG

1. EIA/TIA-568 or EIA-TIA-568 TSB-36 compliant.

2. Cisco Systems does not supply Category 5 UTP RJ-45 cables. They are available commercially.

Maximum cable length —

Maximum segment length 328 ft (100 m) for 100BaseTX

Maximum network length 656 ft (200 m) (with 1 repeater)



Appendix B Cable and Connector SpecificationsConsole and Auxiliary Port Signals and Pinouts

Console and Auxiliary Port Signals and PinoutsThe RPM-XF requires console and auxiliary cables so you can connect a console (an ASCII terminal or PC running terminal emulation software) or modem to your RPM-XF. Cisco Systems does not provide these items. You will need the following items:

• Standard RJ-45-to-RJ-45 rollover cable (see the next section, “Identifying a Rollover Cable” for more information)

• Cable adapters

– RJ-45-to-DB-9 female DTE adapter (labeled Terminal)

– RJ-45-to-DB-25 female DTE adapter (labeled Terminal)

Identifying a Rollover CableYou can identify a rollover cable by comparing the two modular ends of the cable. Holding the cables side-by-side, with the tab at the back, the wire connected to the pin on the outside of the left plug should be the same color as the wire connected to the pin on the outside of the right plug (see Figure B-1). If your cable was purchased from Cisco Systems, pin 1 will be white on one connector, and pin 8 will be white on the other (a rollover cable reverses pins 1 and 8, 2 and 7, 3 and 6, and 4 and 5).

Figure B-1 Identifying a Rollover Cable

Console Port Signals and PinoutsUse the thin, flat RJ-45-to-RJ-45 rollover cable and RJ-45-to-DB-9 female DTE adapter (labeled Terminal) to connect the console port to a PC running terminal emulation software. Figure B-2 shows how to connect the console port to a PC. Table B-2 lists the pinouts for the asynchronous serial console port, the RJ-45-to-RJ-45 rollover cable, and the RJ-45-to-DB-9 female DTE adapter (labeled Terminal).

Pin 1 Pin 8

H38

24

Pin 1 and pin 8should be the

same color




Figure B-2 Connecting the Console Port to a PC

Table B-2 Console Port Signaling and Cabling Using a DB-9 Adapter

Note This cabling configuration can also be used to connect a PC with the auxiliary port.

Use the thin, flat RJ-45-to-RJ-45 rollover cable and RJ-45-to-DB-25 female DTE adapter (labeled Terminal) to connect the console port to a terminal. Figure B-3 shows how to connect the console port to a terminal. Table B-3 lists the pinouts for the asynchronous serial console port, the RJ-45-to-RJ-45 rollover cable, and the RJ-45-to-DB-25 female DTE adapter (labeled Terminal).

Figure B-3 Connecting the Console Port to a Terminal

MGX-XF-UI Console Port (DTE) RJ-45-to-RJ-45 Rollover Cable

RJ-45-to-DB-9Terminal Adapter

ConsoleDevice

Signal RJ-45 Pin RJ-45 Pin DB-9 Pin Signal

RTS 11

1. Pin 1 is connected internally to pin 8.

8 8 CTS

DTR 2 7 6 DSR

TxD 3 6 2 RxD

GND 4 5 5 GND

GND 5 4 5 GND

RxD 6 3 3 TxD

DSR 7 2 4 DTR

CTS 8 1 7 RTS

RJ-45-to-RJ-45rollover cable

RJ-45-to-DB-25 adapter(labeled “Terminal”)

PC

1808

3MGX 8850 RPM



Terminal

1808

2MGX 8850 RPM




Note This cabling configuration can also be used to connect a terminal with the auxiliary port.

Auxiliary Port Signals and PinoutsUse the thin, flat RJ-45-to-RJ-45 rollover cable and RJ-45-to-DB-9 female DTE adapter (labeled Terminal) to connect the auxiliary port to a PC running terminal emulation software. Figure B-2 shows how to connect the auxiliary port to a PC. Table B-2 lists the pinouts for the asynchronous serial auxiliary port, the RJ-45-to-RJ-45 rollover cable, and the RJ-45-to-DB-9 female DTE adapter (labeled Terminal).

Note Connecting to the auxiliary port through a modem is not supported.

Figure B-4 Connecting the Auxiliary Port to a PC

Table B-3 Console Port Signaling and Cabling Using a DB-25 Adapter



ConsoleDevice


RTS 11

1. Pin 1 is connected internally to pin 8.

8 5 CTS

DTR 2 7 6 DSR

TxD 3 6 3 RxD

GND 4 5 7 GND

GND 5 4 7 GND

RxD 6 3 2 TxD

DSR 7 2 20 DTR

CTS 8 1 4 RTS



PC

1808

3MGX 8850 RPM




Table B-4 Auxiliary Port Signaling and Cabling Using a DB-9 Adapter

Use the thin, flat RJ-45-to-RJ-45 rollover cable and RJ-45-to-DB-25 female DTE adapter (labeled Terminal) to connect the auxiliary port to a terminal. Figure B-3 shows how to connect the auxiliary port to a terminal. Table B-3 lists the pinouts for the asynchronous serial auxiliary port, the RJ-45-to-RJ-45 rollover cable, and the RJ-45-to-DB-25 female DTE adapter (labeled Terminal).

Figure B-5 Connecting the Auxiliary Port to a Terminal



ConsoleDevice


RTS 1 8 8 CTS

DTR 2 7 6 DSR

TxD 3 6 2 RxD

GND 4 5 5 GND

GND 5 4 5 GND

RxD 6 3 3 TxD

DSR 7 2 4 DTR

CTS 8 1 7 RTS

Table B-5 Auxiliary Port Signaling and Cabling Using a DB-25 Adapter



ConsoleDevice


RTS 1 8 5 CTS

DTR 2 7 6 DSR

TxD 3 6 3 RxD

GND 4 5 7 GND

GND 5 4 7 GND

RxD 6 3 2 TxD

DSR 7 2 20 DTR

CTS 8 1 4 RTS



Terminal

1808

2MGX 8850 RPM



Appendix B Cable and Connector SpecificationsFast Ethernet RJ-45 Connector Pinouts

Fast Ethernet RJ-45 Connector PinoutsTable B-6 provides pinouts for the FE RJ-45 connectors.

Note Cisco Systems does not provide FE port adapter cables. These cables must be ordered from commercial cable vendors.

Note Referring to the RJ-45 pinout in Table B-6, proper common-mode line terminations should be used for the unused Category 5, UTP cable pairs 4/5 and 7/8. Common-mode termination reduces the contributions to electromagnetic interference (EMI) and susceptibility to common-mode sources. Wire pairs 4/5 and 7/8 are actively terminated in the RJ-45 port circuitry in the 100BaseTX port circuitry in the FE-TX port adapter.

Depending on your RJ-45 interface cabling requirements, use the pinouts in Figure B-6 and Figure B-7.

Figure B-6 Straight-Through Cable Pinout for FE-TX RJ-45 Connection to a Hub or Repeater

Figure B-7 Crossover Cable Pinout for FE-TX RJ-45 Connections Between Hubs and Repeaters

Table B-6 FE RJ-45 Connector Pinout

Pin Description

1 Receive Data + (RxD+)

2 RxD–

3 Transmit Data + (TxD+)

6 TxD–

Hub or LAN switch Ethernet port

3 TxD+

6 TxD–

1 RxD+

2 RxD–

3 RxD+

6 RxD–

1 TxD+

2 TxD– H71

01

Hub or LAN switch

3 TxD+

6 TxD–

1 RxD+

2 RxD–

3 TxD+

6 TxD–

1 RxD+

2 RxD– H31

38

Hub or LAN switch



Appendix B Cable and Connector SpecificationsSFP Specifications

SFP SpecificationsTable B-7 lists the Small-Form-Factor Pluggable (SFP) module cable specifications that are used with the MGX-1GE Gigabit Ethernet back card. The table lists the SFPs and their respective cable types and lengths.

The MGX-1GE back card provides a trunk uplink that supports 1 Gbps throughput using multimode or single-mode fiber, depending on the connector type. (See Table B-7.)

Table B-7 MGX-1GE Cable Specifications

SFP







275 M@ 200 MHz-km

500 M@ 400 MHz-km

550 M@ 500 MHz-km

— — —

1000Base LH/LX

— — 550 M @ 500 MHz-km

550 M@ 400 MHz-km

10 km

1000Base ZX — — — — 70 km



Appendix B Cable and Connector SpecificationsSFP Specifications

C-1Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


A P P E N D I X CCisco IOS and Configuration Basics

This appendix contains basic information about the Cisco IOS software and about configuring the RPM-XF, and includes the following sections:

• Cisco IOS Software Basics

– Cisco IOS Modes of Operation

– Getting Context-Sensitive Help

– Saving Configuration Changes

• Manually Configuring RPM-XF

– Verifying Network Connectivity

Cisco IOS Software BasicsThis section provides you with some basic information about the Cisco IOS software.

Cisco IOS Modes of OperationCisco IOS software provides access to several different command modes. Each command mode provides a different group of related commands.

For security purposes, Cisco IOS software provides two levels of access to commands: user and privileged. The unprivileged-user mode is called “user EXEC” mode. The privileged mode is called “privileged EXEC” mode and requires a password. The commands available in user EXEC mode are a subset of the commands available in privileged EXEC mode. Table C-1 describes some of the most commonly used modes, how to enter the modes, and the resulting prompts. The prompt helps you identify which mode you are in and, therefore, which commands are available.



Appendix C Cisco IOS and Configuration BasicsCisco IOS Software Basics

Almost every configuration command also has a no form. In general, use the no form to disable a feature or function. Use the command without the keyword no to re-enable a disabled feature or to enable a feature that is disabled by default. For example, IP routing is enabled by default. To disable IP routing, enter the no ip routing command and enter ip routing to reenable it. The Cisco IOS software command reference publication provides the complete syntax for the configuration commands and describes what the no form of a command does.

Table C-1 Cisco IOS Operating Modes

Mode of Operation Usage How to Enter the Mode Prompt

User EXEC User EXEC commands allow you to connect to remote devices, change terminal settings on a temporary basis, perform basic tests, and list system information. The EXEC commands available at the user level are a subset of those available at the privileged level.

Log in. MGX8850-RPM>

Privileged EXEC

Privileged EXEC commands set operating parameters. The privileged command set includes those commands contained in user EXEC mode, and also the configure command through which you can access the remaining command modes. Privileged EXEC mode also includes high-level testing commands, such as debug.

Enter the enable EXEC command from user EXEC mode.

MGX8850-RPM#

Global configuration

Global configuration commands apply to features that affect the system as a whole.

Enter the configure privileged EXEC command from global configuration mode.

MGX8850-RPM(config)#

Interface configuration

Interface configuration commands modify the operation of an interface such as a Fast Ethernet or Gigabit Ethernet. Many features are enabled by per-interface. Interface configuration commands always follow an interface global configuration command, which defines the interface type.

Enter the interface type number command from global configuration mode. For example, enter the interface fastethernet 2/1 command to configure the ATM interface.

MGX8850-RPM(config-if)#

ROM monitor ROM monitor commands are used to perform low-level diagnostics. You can also use the ROM monitor commands to recover from a system failure and stop the boot process in a specific operating environment.1

1. You can modify the configuration register value using the config-reg configuration command. See Appendix A, “Maintaining the MGX RPM-XF” the “Virtual Configuration Register Settings” section for more information.

Enter the reload EXEC command from privileged EXEC mode. Click Break during the first 60 seconds (sec) while the system is booting.

ROMMON>



Appendix C Cisco IOS and Configuration BasicsCisco IOS Software Basics

Getting Context-Sensitive HelpIn any command mode, to view a list of available commands, enter a question mark (?).

MGX8850-RPM> ?

To obtain a list of commands that begin with a particular character sequence, type in those characters followed immediately by the question mark (?). Do not include a space. This form of help is called word help because it completes a word for you.

MGX8850-RPM# co?configure connect copy

To list keywords or arguments, enter a question mark in place of a keyword or argument. Include a space before the question mark. This form of help is called command syntax help. It reminds you which keywords or arguments are applicable based on the command, keywords, and arguments you have already entered.

MGX8850-RPM# configure ? memory Configure from NV memory network Configure from a TFTP network host terminal Configure from the terminal <cr>

You can also abbreviate commands and keywords by entering just enough characters to make the command unique from other commands. For example, you can abbreviate the show command to sh.

Saving Configuration ChangesWhenever you make changes to the RPM-XF configuration, you must save the changes to memory so they will not be lost if the system is rebooted. There are two types of configuration files: the running (current operating) configuration and the startup (last saved) configuration. The running configuration is stored in RAM; the startup configuration is stored in NVRAM.

To display the current running configuration, enter the show running-config command. Enter the copy running-config startup-config command to save the current running configuration to the startup configuration file in NVRAM.

MGX8850-RPM> enableMGX8850-RPM# copy running-config startup-config

To display the startup configuration, enter the show startup-config command. Enter the copy startup-config running-config command to write the startup configuration to the running configuration.

MGX8850-RPM> enableMGX8850-RPM# copy startup-config running-config

To erase both configuration files (and start over), enter the write erase and reload commands.

MGX8850-RPM> enableMGX8850-RPM# write eraseMGX8850-RPM# reload

Warning This command sequence will erase the entire RPM-XF configuration in RAM and NVRAM and reload the RPM-XF.



Appendix C Cisco IOS and Configuration BasicsManually Configuring RPM-XF

Manually Configuring RPM-XFYou can configure the RPM-XF manually if you prefer not to use AutoInstall or the prompt-driven System Configuration Dialog.

Perform the following steps to configure the RPM-XF manually:

Step 1 Connect a console terminal to the RPM-XF.

Follow the instructions described in Chapter 3, “Installing the MGX RPM-XF Front and Back Cards,” in the “Connecting a Console Terminal or PC to the MGX-XF-UI Console Port” section and then power on the RPM-XF.

Step 2 When you are prompted to enter the initial dialog, enter no to go into the normal operating mode of the RPM-XF.

Would you like to enter the initial dialog? [yes]: no

After a few seconds you will see the user EXEC prompt (Router>).

By default, the host name is Router, but the prompt will match the current host name. In the following examples, the host name is MGX8850-RPM-XF.

Step 3 Enter the enable command to enter enable mode. You can make configuration changes only in enable mode.

Router> enable

Step 4 Assign a hostname for the RPM-XF using the hostname command.

Router> hostname MGX8850-RPM-XF

The prompt will change to the privileged EXEC (enable) prompt, MGX8850-RPM-XF#.

Step 5 Enter the configure terminal command at the enable prompt to enter the configuration mode.

MGX8850-RPM-XF# config terminal

You can now enter any changes you want to the configuration. You may want to perform the following tasks:

1. Enter an enable secret using the enable secret command.

2. Enter an enable password using the enable password command.

3. Assign addresses to the interfaces using the protocol address command.

4. Specify which protocols to support on the interfaces.

Refer to the Cisco IOS configuration and command reference publications for more information about the commands you can use to configure the RPM-XF. You can also refer to the MGX 8850 Wide Area Switch Command Reference and MGX 8850 Wide Area Switch Installation and Configuration documents for information about the commands you can use to configure the RPM-XF.

Step 6 When you finish configuring the RPM-XF, enter the exit command until you return to the privileged EXEC prompt (MGX8850-RPM-XF#).

Step 7 To save the configuration changes to NVRAM, enter the copy run start command at the privileged EXEC prompt.

MGX8850-RPM-XF# copy run start********




The RPM-XF is now configured and will boot with the configuration you entered.

This concludes the initial RPM-XF configuration.

Verifying Network ConnectivityWhen you have installed and configured the RPM-XF, you can use the following commands in user EXEC mode to verify network connectivity:

• ping—Sends a special datagram to the destination device, then waits for a reply datagram from that device.See Chapter 4, “Installing and Configuring the MGX-XF-UI Management Back Card”the “Verifying Ethernet Connectivity” section for a detailed ping procedure.

• telnet—Logs in to a remote node.

• traceroute—Discovers the routes that packets take when traveling from one RPM-XF to any other router.

If there is a problem with network connectivity, see Appendix A, “Maintaining the MGX RPM-XF” the “Reading Front Panel LEDs” section and check the cable connections. If there is still a problem, check the RPM-XF configuration. Contact customer service for further assistance.

D-1Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


A P P E N D I X DCommand Summary

This chapter (Table D-1 through Table D-7) provides a high level view of many of the commands that run on the RPM-XF. It does not describe command keywords or arguments. This appendix contains the following sections:

• User Exec Mode Commands

• Privileged Exec Mode Commands

• Global Configuration Mode Commands

• Interface Configuration Mode Commands

• QoS Configuration Mode Commands

To find more information about a command, refer to the Cisco IOS command reference guides.

User Exec Mode Commands

Table D-1 Commands in User EXEC Mode—Router>

Command Description Command Use and Purpose

<1-99> Session number to resume. Navigates between Telnet and other sessions at a network management station (NMS).

access-enable Create a temporary access-list entry.

Restricts access to the RPM-XF.

access-profile Apply user-profile to interface. Applies per-user authorization attributes to an interface during a PPP session.

clear Reset functions. Clears counters in the show interface command; clears traffic on a line; clears logging.

connect Open a terminal connection. Uses Telnet to connect to a device.

disable Turn off privileged commands. —

disconnect Terminate an existing network connection.

—

enable Turn on privileged commands. —



Appendix D Command SummaryUser Exec Mode Commands

exit Terminate an existing network connection.

Exits a terminal session.

help Description of the interactive help system.

Obtains a brief description of the help system in any command mode.

lock Lock the terminal. Sets up a temporary password on a line.

login Log in as a particular user. —

logout Exit from the user Exec mode. —

mrinfo Request neighbor and version information from a multicast router.

—

mstat Show statistics after multiple multicast traceroutes.

Displays IP multicast packet rate and loss information.

mtrace Trace reverse multicast path. Traces the path from a source to a destination branch for a multicast distribution tree.

name-connection Name an existing network connection.

Assigns a logical name to an interface.

ping Send ICMP echo messages. Verifies interface connectivity.

ppp Start IETF Point-to-Point Protocol (PPP).

—

resume Resume an active network connection.

—

rlogin Open an rlogin connection. —

show Show information about the system.

Keywords include hardware, version, and facility-alarm.

slip Start Serial-Line IP (SLIP). —

systat Display information about terminal lines.

Displays information about the active lines on the router.

telnet Initiate a Telnet session. —

terminal Set terminal line parameters. —

traceroute Trace route to destination. Determines the path data follows from source port to a specified destination.

tunnel Open a tunnel connection. Sets up a network layer connection to a router.

where List active connections. —

Table D-1 Commands in User EXEC Mode—Router> (continued)




Appendix D Command SummaryPrivileged Exec Mode Commands

Privileged Exec Mode Commands

Table D-2 Commands in Privileged EXEC Mode—Router#


<1-99> Session number to resume. —

access-enable Create a temporary access list entry.

Restricts access to the RPM-XF.

access-profile Apply user-profile to interface. Applies per-user authorization attributes to PPP sessions.

access-template Create a temporary access-list entry.

Customizes a temporary access-list entry.

archive .Manage archive files. —

calendar Manage the hardware calendar. —

cd Change current directory. Navigates to another directory.

clear Reset functions. Clears counters in the show interface command; clears traffic on a line; clears logging.

clock Manage the system clock. Sets the date and time on a RPM-XF.

configure Enter configuration mode. Enters terminal and memory configuration mode.

connect Open a terminal connection. To log in to a host that supports Telnet, rlogin, or LAT, use the connect EXEC command.

copy Copy from one file to another. —

debug Debugging functions (see also '"undebug").

Displays debug command output and error messages in the current terminal session.

delete Delete a file. Deletes a file on a Flash memory device.

dir List files on a file system. Displays a list of files on a file system.

disable Turn off privileged commands. Use disable to exit privileged EXEC mode and return to user EXEC mode.

disconnect Disconnect an existing network connection.

—

enable Turn on privileged commands. —

erase Erase a file system. —

exit Exit from the EXEC. —

format Format a file system. Formats a Flash disk or Flash card.


—

lock Lock the terminal. Sets up a temporary password on a line.

login Log in as a particular user. —

logout Exit from the EXEC. —



Appendix D Command SummaryPrivileged Exec Mode Commands

microcode Microcode commands. Enables PXM, SAR, and all hardware types that support downloadable microcode.

monitor Monitoring different system events.

—

more Display the contents of a file. —

mpls Configure router traffic engineering.

Enables multiprotocol label switching through use of traffic engineering tag switching commands.

mrinfo Request neighbor and version information from a multicast router.

Identifies neighboring multicast routers that are peers of the local router.

mstat Show statistics after multiple multicast traceroutes are run.

Displays IP multicast packet rate and loss information.

mtrace Trace reverse multicast path from destination to source.

Traces the path from a source to a destination branch for a multicast distribution tree.

name-connection Name an existing network connection.

Assigns a logical name to a connection.

no Negate a command or reset its defaults.

—

ping Send ICMP echo messages. —

ppp Start IETF Point-to-Point Protocol (PPP).

Starts an asynchronous connection using PPP.

pwd Display current working directory.

Shows the current setting of the cd command.

reload Halt system and perform a cold restart.

Reloads the operating system.

rename Rename a file. Renames a file in a Class C Flash file system.

resume Resume an active network connection.

Navigates to another open Telnet, rlogin, LAT, or PAD session.

rlogin Open an rlogin connection. —

rsh Execute a command on a remote RSH host.

—

send Send a message to other TTY lines.

Sends messages to one or all terminal lines.

show Displays information about the running system.

Keywords include class-map, policy-map, controllers, environment, facility-alarm, hardware, ppp multilink, startup-config, running-config, and version.

slip Start Serial-Line IP (SLIP). Starts a serial connection to a remote host using SLIP.

Table D-2 Commands in Privileged EXEC Mode—Router# (continued)




Appendix D Command SummaryGlobal Configuration Mode Commands

Global Configuration Mode Commands

squeeze Squeeze a file system. Permanently deletes files from a Flash card.

start-chat Start a chat-script on a line. —

systat Display information about terminal lines.

Displays information about the active lines on the router.

telnet Initiate a Telnet session. —

terminal Set terminal line parameters. —

test Test subsystems, memory, and interfaces.

—

traceroute Trace route to destination. Determines the path data follows from source port to a specified destination.

tunnel Open a tunnel connection. Sets up a network layer connection to a router.

undebug Disable debugging functions (see also debug).

—

undelete Undelete a file. Recovers files marked deleted from a Flash card.

verify Verify a file. Verifies the checksum of a Flash memory file.

where List active connections. —

which-route Perform OSI route table lookup and display results.

Displays the routing table in which a specified CLNS destination is found.

write Perform OSI route table lookup and display results.

Writes running configuration to memory, network, or terminal.

Table D-3 Commands in Global Configuration Mode—Router(config)#


aaa Authentication, authorization, and accounting.

Accounting for billing or security purposes when you use RADIUS or TACACS+.

access-list Add an access list entry. —

alias Create command alias. —

arp Set a static ARP entry. Maps Mac address to IP address.

async-bootp Modify system bootp parameters.

Supports extended BOOTP requests. Specifies information sent in response to BOOTP requests.

banner Define a login banner. Displays a banner on terminals with an interactive EXEC.

boot Modify system boot parameters. —

Table D-2 Commands in Privileged EXEC Mode—Router# (continued)





buffers Adjust system buffer pool parameters.

Adjusts buffer pool settings and the limits at which temporary buffers are created and destroyed.

busy-message Display message when connection to host fails.

—

cdp Global Cisco Discovery Protocol configuration subcommands.

—

chat-script Define a modem chat script. —

class-map QoS class-map command. Enters config-cmap configuration mode.

clns Global CLNS configuration subcommands.

—

clock Configure time-of-day clock. —

config-register Define the configuration register. Defines system startup behavior.

controller Configure a specific controller. Configures a controller-type and enters config-controller mode.

default Set a command to its default value.

—

default-value Default character-bits values. Changes the flow control default value from a 7-bit width to an 8-bit width.

define Interface range macro definition. —

dialer Dialer commands. —

dialer-list Create a dialer list entry. —

dnsix-dmdp Provide DMDP service for DNSIX.

—

dnsix-nat Provide DNSIX service for audit trails.

—

do To run exec commands in config mode.

—

download-compatible-config

Generate a configuration compatible with older software.

—

enable Modify enable password parameters.

—

end Exit from configure mode. —

exception Perform exception handling. —

exit Exit from configure mode. Closes terminal sessions and exits configuration modes.

file Adjust file system parameters. —


—

hostname Set system network name. Specifies the host name of the RPM-XF.

Table D-3 Commands in Global Configuration Mode—Router(config)# (continued)





interface Select an interface to configure and enter config-if mode.

Configures an interface type and enters config-if mode.

ip Global IP configuration subcommands.

—

ipc Configure IPC system. —

isis Global ISIS configuration subcommands.

—

kerberos Configure Kerberos. —

key Key management. —

line Configure a terminal line. —

logging Modify message logging facilities.

Stores or deletes the log.

login-string Define a host-specific login string.

—

map-class Configure static map class. Defines parameters shared with the dialer map command.

map-list Configure static map list. Specifies a map group and links it to a local E.164 or X.121 source address and a remote E.164 or X.121 destination address.

menu Define a user-interface menu. Specifies underlying commands for user interface menus.

microcode Configure microcode. —

modemcap Modem Capabilities database. —

mpls Configure MPLS parameters. —

multilink PPP multilink global configuration.

—

no Negate a command or set its defaults.

—

ntp Configure NTP. Configures Network Time Protocol.

parser Configure parser. —

policy-map Configure QoS policy map. Enters config-pmap mode. From there you can enter config-pmap-c mode.

priority-list Build a priority list. Establishes queuing priorities based upon the protocol type. This is one of the steps to establishing queuing priorities based on logical unit (LU) addresses.

privilege Command privilege parameters. Adjusts privilege level needed to access configuration commands.

process-max-time Maximum time for process to run before voluntarily relinquishing processor.

—






prompt Set system prompt. Customizes the system prompt.

queue-list Build a custom queue list. Assigns priority queueing on an interface.

rbe Commands for Routing RFC 1483 Ethernet encapsulated packets.

—

regexp regexp commands. —

resume-string Define a host-specific resume string.

—

rlogin Rlogin configuration commands. —

rmon Remote monitoring. Remote monitoring for Ethernet interfaces.

route-map Create route-map or enter route-map command mode.

Defines the conditions for redistributing routes from one routing protocol into another or enables policy routing. Enters config-route-map mode.

router Enable a routing process. Enables various routing protocols.

rtr RTR base configuration. Configures a response time reporter probe.

scheduler Scheduler parameters. Schedules timing for CPU process handling.

service Modify use of network-based services.

—

snmp Modify non-engine SNMP parameters.

—

snmp-server Modify SNMP parameters. —

standby Global HSRP configuration commands.

—

state-machine Define a TCP dispatch state machine.

—

tacacs-server Modify TACACS query parameters.

—

tag-switching Dynamic tag switching command

—

template Select template to configure. —

terminal-queue Terminal queue commands. Changes the retry interval for a terminal port queue.

tftp-server Provide TFTP service for netload requests.

—

time-range Define time range entries. —

username Establish user name authentication.

Assigns a user name that is displayed in the configuration files.

vc-class Configure per VC parameters. —





Appendix D Command SummaryInterface Configuration Mode Commands

Interface Configuration Mode Commands

virtual-profile Virtual profile configuration. Enables virtual profiles by AAA configuration.

virtual-template Virtual template configuration. —

vpdn Virtual Private Dialup Network —

vpdn-group VPDN group configuration. —

vpdn-template VPDN template configuration. —

Table D-4 Commands in Interface Configuration Mode—Router(config-if)#


arp Set arp type (arpa, probe, snap) or timeout.

—

atm Modify ATM parameters. —

backup Modify backup parameters. Not supported.

bandwidth Set bandwidth informational parameter.

—

barium Configure Barium on POS interface.

—

bgp-policy Apply policy propagated by bgp community string.

Enables QPPB on the interface.

carrier-delay Specify delay for interface transitions.

—

cdp CDP interface subcommands. —

class-int Configure default vc-class name. —

clns CLNS interface subcommands. —

clock Configure interface clock source.

—

crc Specify CRC word size. —

custom-queue-list Assign a custom queue list to an interface.

—

default Set a command to its default value(s).

—

delay Specify interface throughput delay.

—

description Interface specific description. Adds comments to an interface configuration.

dialer Dial-on-demand routing (DDR) commands.

—






dialer-group Assign interface to dialer list. —

duplex Configure duplex operation. —

duplex full Configure full-duplex operational mode.

—

duplex half Configure half-duplex and related commands.

—

encapsulation Set encapsulation type for an interface.

—

extended-port Map XTagATM interface to switch port.

—

exit Exit from interface configuration mode.

—


—

hold-queue Set hold queue depth. —

ip Interface Internet protocol config commands.

Configures IP services on ports and interfaces.

isis IS-IS commands. —

iso-igrp ISO-IGRP interface subcommands.

Filters the establishment of ISO IGRP adjacencies.

keepalive Enables keepalive. —

label-control-protocol

Label switch controller control protocol commands.

—

load-interval Specify interval for load calculation for an interface.

Changes the time span during which data is accumulated for use in computing load statistics.

logging Configure logging for interface. Logs messages to a syslog server.

loopback Configure internal loopback on an interface.

—

mac-address Manually set MAC address. —

map-group Configure static map group. —

max-reserved-bandwidth

Maximum reservable bandwidth on an interface.

—

media-type Interface media type. —

mpls Configure MPLS interface parameters.

—

mtu Set the interface maximum transmission unit (MTU).

—

multilink-group Put interface into a multilink bundle.

—

negotiation Select Autonegotiation mode. —

Table D-4 Commands in Interface Configuration Mode—Router(config-if)# (continued)





no Negate a command or reset its defaults.

—

ntp Configure NTP. Configures Network Time Protocol.

peer Peer parameters for ATM MPLS interfaces.

—

pos Modify POS parameters. —

ppp Point-to-point protocol. —

priority-group Assign a priority group to an interface.

—

pulse-time Force DTR low during resets. —

pvc Configure ATM PVC parameters.

—

rate-limit Rate limit. Configures committed access rate (CAR) and distributed CAR (DCAR) policies.

random-detect Enable Weighted Random Early Detection (WRED) on an interface.

—

rmon Configure remote monitoring on an interface.

—

service-policy Configure QoS service policy. —

shutdown Shut down the selected interface. —

snapshot Configure snapshot support on the interface.

—

snmp Modify SNMP interface parameters.

—

source Get config from another source. —

speed Configure speed operation. —

standby HSRP interface configuration parameters.

—

switch RPM configuration. —

tag-control-protocol Tag switch controller control protocol commands.

—

tag-switching Tag switching interface configuration commands.

—

timeout Define timeout values for this interface.

—

traffic-shape Enable traffic shaping on an interface or sub-interface.

—

transmit-interface Assign a transmit interface to a receive-only interface.

—





Appendix D Command SummaryQoS Configuration Mode Commands

QoS Configuration Mode CommandsQuality of Service (QoS) commands are described in Chapter 8.

tx-ring-limit Configure PA level transmit ring limit.

—

vpdn Virtual Private Dialup Network. —



Table D-5 QoS Class-Map Configuration Commands—Router(config-cmap)#


description Class-map description. —

exit Exit from QoS class-map configuration mode.

—

match Classification criteria. —

no Negate or set default values of a command.

—

rename Rename this class-map. —

Table D-6 QoS Policy-Map Configuration Commands—Router(config-pmap)#


class Policy criteria. —


exit Exit from QoS policy-map configuration mode.

—


—

rename Rename this class-map. —

Table D-7 QoS Policy-Map Class Configuration Commands—Router(config-pmap-c)#


bandwidth Class-based weighted fair queue. —

exit Exit from QoS class action configuration mode.

—



—




police Police (committed access rate–CAR).

—

priority Priority queue. —

queue-limit Tail drop. —

random-detect Weighted random early detect. —

set Set QoS values. —

shape Shaped transmission. —

Table D-7 QoS Policy-Map Class Configuration Commands—Router(config-pmap-c)# (continued)


IN-1Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide


I N D E X

Numerics

100BASE-T

maximum cable lengths 4-4

specifications 4-3, B-1

transmission recommendations 4-3, B-1

1-99 command D1, D3

4E

straight-through cable B-6

802.1q PXF switching 10-2

A

aaa command D5

access-enable command D1, D3

access-group command 10-5

access-list command D5

access list entries, creating D1

access-profile command D1, D3

access-template command D3

accounting D5

AC power

power supply removal 3-4

active connections D5

addred command 7-13, 7-16

adjusting file parameters D6

alias command D5

ARPA encapsulation 10-2

arp command D5, D9

assigning interfaces 10-4

async-bootp command D5

audience, for this document xv

authentication D5

authorization D5

authorization attributes, assigning D1

auxiliary port

adapter B-3, B-5

B

backup command D9

bandwidth

guarantee 10-8

increasing 10-7

bandwidth command 4-5, 5-7, 6-5, 6-18, D9

bandwidth reservation 10-1

banner command D5

BGP

configuring 9-15

bgp community string D9

bgp-policy command D9

bit width flow control D6

boilerplate

assigning to interface 10-4

Q0S 10-2

boot

command D5

sequence 7-8

bootload-failure response A-10

Border Gateway Protocol

see BGP

buffer

pool settings D6

buffers command D6

bundling the interface D10

busy-message command D6

Index



C

cable

assemblies B-3, B-5

pinouts

console B-3, B-5

cables

100BASE-T

maximum lengths 4-4

4E RJ-45 pinout B-6

calendar command D3

CAR

See committed access rate

carrier-delay command D9

caution

halting the router A-6

cd command D3, D4

cdp command D6, D9

changing configuration register settings A-7

channelized T3 line card

line clock source 5-9

character-bits values D6

Cisco 10000 Series edge services router (ESR)

restricting access D1

Cisco IOS software

basics C-1

erasing the configuration C-3

getting help C-3

modes of operation C-1

saving the configuration C-3

Class C Flash file D4

class command 10-4

class-map command 10-3, 10-5, D6

clear command D1, D3

CLI

modular 10-3

QoS configuration 10-3

clns command D6, D9

CLNS destination D5

clock command D3, D6

clock source command 4-5, 4-10, 5-7, 5-9

code-point values 10-5

Combo card

connected to MGX 8850 RPM 3-7

serial connection

configuring C-5

commands

1-99 D1, D3

aaa D5

access-enable D1, D3

access-list D5

access-profile D1, D3

access-template D3

alias D5

arp D5, D9

async-bootp D5

b (boot) A-8

backup D9

bandwidth 4-5, 4-10, 5-7, 6-5, 6-18, D9

banner D5

bgp-policy D9

boot D5

boot system A-9

Break (interrupt) A-9

buffers D6

busy-message D6

calendar D3

carrier-delay D9

cd D3

cdp D6, D9

class 10-4

class-map 10-4

clear D3

clear counters D1

clns D6, D9

clock D3, D6

clock source 4-5, 4-10, 5-7

config-cmap 10-3

Index



config-register A-7, A-9, D6

config terminal C-4

configure D3

connect D1, D3

controller D6

copy D3

copy running-config startup-config C-3, C-4

debug D3

default D6, D9

default-value D6

delay D9

delete D3

description D9

dir D3

disable D1, D3

disconnect D1, D3

enable A-7, C-4, D1, D3

encapsulation 4-5, 5-7

end D6

erase D3

EXEC mode D1

exit D2, D3, D6, D10

Flash related A-8

format D3

framing 5-7

help D2, D3, D6, D10

hold-queue D10

hostname D6

interface D7

in user EXEC mode D1

ip D7, D10

ipc D7

isis D10

iso-igrp D10

keepalive 4-5, 4-10, 5-7, 6-5, 6-18

kerberos D7

key D7

line D7

load interval D10

lock D3

lock terminal D2

logging D7, D10

login D2, D3

login string D7

logout D2, D3

loopback D10

mac-address D10

map-class D7

map list D7

match 10-3, 10-5, D12

menu D7

more D4

mpls D4, D7, D10

mrinfo D4

mstat D2, D4

mtrace D2, D4

mtu 4-5, 4-10, 5-7, 6-5, 6-18, D10

multilink D7

multilink-group D10

name-connection D2, D4

no D4, D7, D11

ntp D7, D11

ping C-5, D2, D4

police 10-7

policy map D7

policy-map 10-3, 10-6

pos framing 5-9

ppp D2, D4

ppp multilink D7

priority list D7

privilege D7

prompt D8

pwd D4

queue list D8

random-detect 10-8

rate-limit D11

reload A-8, C-3, D4

rename D4

Index



resume D2, D4

resume string D8

rlogin D2, D4, D8

rmon D8

route-map D8

router D8

rtr D8

scheduler D8

scramble 5-7

send D4

service D8

service-policy 10-13, D11

show class-map 10-14

show policy-map 10-14

show policy-map interface serial 10-14

show sys info D2

show version A-7

show vlans 10-15

shutdown D11

slip D2, D4

SNMP D8

snmp D11

squeeze D5

state machine D8

systat D2, D5

tacacs-server D8

tag-switching D8, D11

Telnet D2, D5

telnet C-5

terminal queue D8

test D5

tftp-server D8

timeout D11

trace C-5

traceroute D2, D5

transmit interface D11

tunnel D5

tunnel open D2

undebug D5

undelete D5

username D8

verify D5

virtual-profile D9

where D2, D5

which-route D5

write erase C-3

committed access rate (CAR) 10-7, 10-15, D11

common-mode line terminations, RJ-45

4E B-6

community list 10-16

community string D9

compression

see IPHC 10-22

config-cmap command 10-3

config-pmap mode 10-3

config-register command D6

config terminal command C-4

configuration

displaying C-3

register

boot field A-8

settings, changing A-7

saving changes to C-3

configuration mode

class map 10-3

exiting D6

configure command D3

configure mode D6

connect command D1, D3

connections

active D5

asynchronous D4

listing active D2

rlogin D4

serial D4

terminal D1

terminating D1

tunnel D2

Index



console port

adapter B-3, B-5

pinouts B-3, B-5

Console Port Connection 3-9

controller command D6

copy command D3

copy running-config startup-config command C-3, C-4

counters, clearing D1

CPU process handling D8

crc command 4-5, 5-7

crossover cable

4E B-6

cRTP 10-22

cTCP 10-22

cUDP 10-22

current settings D4

D

data path, determining D2

DCAR

See distributed CAR

debug command D3

default command D6, D9

default-value command D6

delay command D9

delete command D3

description command D9

destination, tracing D2

differentiated service code point 10-5

dir command D3

directory, displaying D4

disable command D1, D3

disconnect command D1, D3

distributed CAR (DCAR) policy D11

documentation

for VIP-related software commands 4-12

objectives xv

organization xvii

referenced and related xv

software configuration xv, 7-10

drop keyword 10-7

drop probability 10-9

dscp 10-5

E

echo message D2, D4

eiBGP

load sharing 9-16

EMI requirements

with 10BASE-T B-6

enable

command D1, D3

enable command C-4

encapsulation command 4-5, 5-7

end command D6

erase command D3

error messages in terminal sessions D3

Ethernet

interface 10-4

Ethernet 10BaseT connection 2-5

ewc value 10-8

exception command D6

exit command D2, D3, D6, D10

exiting terminal session D6

exponential-weighting-constant value 10-8

export routes

configuring 9-17

F

Fast Ethernet

specifications 4-3, B-1

file command D6

filenames, netbooting A-9

files

Index



undeleting D5

Flash memory

buffer overflow message A-11

ensuring available space before copying to A-11

format command D3

forward traffic 10-8

frame header, customizing 5-10

framing

SDH STM-1 5-9

SONET STS-3c 5-9

front card

removal 3-4

G

gigabit Ethernet interface, assigning 10-4

global configuration mode C-2

H

hardware

installation procedures 3-1 to ??

help command D2, D3, D6, D10

hold-queue command D10

host failure D6

hostname command D6

I

iBGP 9-12

ICMP echo messages D2, D4

IEEE 802.3u specifications 4-4

import and export routes

configuring 9-17

import routes

configuring 9-17

installation

changing configuration register settings C-4

interface command D7

internal loopback D10

Internet Protocol Header Compression

see IPHC

IOS

supported class maps 10-5

IP

address mapping D5

command D7, D10

config commands D10

differentiated service code point 10-5

multicast packet rate D4

precedence value 10-7

services on ports D10

IP accounting 7-18

ip address configuration subcommand 5-8, 6-5, 6-19

ipc command D7

ip dscp value 10-12

IPHC 10-22

isis command D10

iso-igrp command D10

K

keepalive command 4-5, 4-10, 5-7, 6-5, 6-18

kerberos command D7

key command D7

keywords

drop 10-7

set-dscp-transmit value 10-7

set-prec-transmit value 10-7

set-qos-transmit value 10-7, 10-8

transmit 10-8

L

LEDs

illustrated 1-8, A-2

Index



line card

clock source 5-9

line command D7

load-interval command D10

lock command D2, D3

logging, clearing D1

logging command D7, D10

logical name, assigning D2

login command D2, D3

login-string command D7

logout command D2, D3

loopback

command 5-11, 6-6, 6-20, D10

low-latency priority 10-1

M

mac-address command D10

maintenance procedures A-1

map-class command D7

map-list command D7

mapping rules 10-6

maps

class, creating 10-3

policy, creating 10-3

rules 10-6

mark-denom value 10-9

match command 10-3, 10-5, D12

maximum transmission unit command

See mtu command

max-value threshold 10-9

memory, testing D5

menu command D7

MGX-1GE back card

configuration 6-4

customizing 6-6

default values 6-4

example configuration 6-7

features 6-2

installation 6-3, 6-28

interface configuration 6-5

specifications 6-3

syntax 6-5

MGX-1OC12POS-IR back card

configuration 5-6

customizing 5-9

default values 5-7


features 5-1

installation 5-6


syntax 5-7

troubleshotting 5-13

MGX-2GE back card

configuration 6-18

customization 6-20

default values 6-18


features 6-15

installation 6-17, 6-28


specifications 6-16

syntax 6-18

MGX-2OC12POS back card

configuration 5-6

customizing 5-9

default values 5-7


features 5-4

installation 5-6


syntax 5-8

troubleshotting 5-13

MGX 8850

three-slot model 1-2

MGX 8850 RPM

powered by Cisco MGX 8850 backplane 1-2, 2-3

shipping package contents 3-1

Index



MGX RPM-XF

performance 1-1

Physical Overview 1-2

MII

cable specifications 4-4

min-value threshold 10-9

MLP/LFI 10-21

modular CLI 10-3

more command D4

mpls command D4, D7, D10

MPLS VPN 9-10, 9-11

mrinfo command D2, D4

mstat command D2, D4

mtrace command D2, D4

mtu command 4-5, 4-10, 5-7, 6-5, 6-18, D10

multicast packet rate D2

Multicast VPN 9-19

multilink command D7

multilink-group command D10

MultiLink PPP/Link Fragmentation Interleaving

see MLP/LFI

N

name-connection command D2, D4

neighbor information, requesting D2

netbooting A-8

netload requests D8

network layer connection D2

network management station (NMS) D1

no command D4, D7, D11

no shutdown command 5-8, 6-6, 6-19

ntp command D7, D11

NVRAM C-3

O

OC-12 POS line card

command syntax 6-5

framing mode 5-10

interoperability 5-10

loopback testing 5-11, 6-6, 6-20

scrambling POS synchronous payload envelope (SPE) 5-10

P

packet

classifying 10-15

class maps 10-3

defining characteristics 10-5

discarding 10-3

IP precedence value 10-5

recognizing 10-3

source, slowing 10-1

parameters

adjusting D6

backup D9

bandwidth D9

dialer map D7

MPLS D7, D10

privilege D7

scheduler D8

SNMP D8, D11

TACACS D8

terminal lines D2

password


temporary D2, D3

ping command C-5, D2, D4

pinouts

RJ-45

4E B-6

4E crossover and straight-through cables B-6

police command 10-7

policy-map command 10-3, 10-6, D7

policy map statistics 10-14

Index



policy propagation border gateway protocol

See QPPB

ports

source D5

pos flag command 5-7, 5-10

pos framing command 5-7, 5-9

pos scramble-atm command 5-7, 5-10

POS synchronous payload envelope (SPE) 5-10

ppp command D2, D4

PPP session D1

precedence value 10-8

prioritize queuing D8

priority-list command D7

privilege command D1, D3, D7

privileged EXEC mode C-2

procedures

installation 3-1 to ??

maintenance A-1 to A-12

prompt command D8

propagation 10-2

protocols

policy propagation border gateway 10-15

routing D8

publication conventions xviii

pwd command D4

Q

QoS

boilerplate creation 10-3

class map 10-3

committed access rate (CAR) 10-1

match command 10-3

packet management process 10-3

performance, improving 10-7

policies, entering 10-6

policy map 10-3

policy propagation 10-2

service policy D11

set 10-1

weighted random early detection (WRED) 10-1

QPPB

configuration example 10-15

description 10-2

enabling D9

support 10-2

qualified personnel warning 3-2

quality of service. See QoS.

queue

limits 10-12

size 10-8

queue-list command D8

R

RADIUS D5

random-detect command 10-8

random-detect keyword 10-9

rate-limit command D11

reload command A-8, D4

remote monitoring D8

rename command D4

resetting functions D1


resume command D2, D4

resume-string command D8

resuming session numbers D1

RJ-45

1FE

cable specifications 4-3, B-1

4E

cable B-6

cable pinout B-6

crossover and straight-through cable pinouts B-6

cable

4E pinout B-6

specifications 4-3, 4-4, B-1

common-mode line terminations

Index



4E B-6

crossover and straight-through cable pinouts B-6

pinouts B-6

rlogin command D2, D4, D8

rmon command D8

roll-over cable, identifying B-2

ROM monitor mode C-2

route-map command D8

router

managing QoS 10-1, 10-12

router command D8

rsh command D4

rtr command D8

S

safety

with electricity 2-2

scheduler command D8

security command D5

send command D4

sending ICMP echo msgs D4

serial-line IP

See slip command

service command D8

service-policy command 10-3, 10-13

session

exiting D2

number D1

set command 10-12

set-dscp-transmit value keyword 10-7

set-prec-transmit value keyword 10-7

set-qos-transmit value keyword 10-7, 10-8

setup

manual configuration C-4

show class-map command 10-14

show command D2, D4

show interface command D1

show policy-map command 10-14

show policy-map interface serial command 10-14

show statistics D2, D4

shutdown command D11

slip command D2, D4

snmp command D11

snmp-server command D8

software

upgrading A-11

specifications

Fast Ethernet (100BASE-T) 4-3, B-1

IEEE 802.3u 4-4

system 1-8

squeeze command D5

state-machine command D8

statements, matching 10-6

static ARP entry, setting D5

synchronous payload envelope (SPE) 5-10

systat command D2, D5

system code, updating A-11

T

TACACS+ D5

tacacs-server command D8

tag-switching command D8, D11

Telnet D1

command D2, D5

to device D1

telnet command C-5

temporary access list entries D1

temporary passwords D2

terminal command D2, D5

terminal connection, opening D1

terminal lines D2

terminal-queue command D8

terminal session

closing D6

debug output D3

error messages D3

Index



exiting D2

test command D5

tftp-server command D8

threshold maximum and minimum 10-9

time, configuring D6

timeout command D11

trace command C-5

traceroute command D5

traceroutes

described D4

showing statistics D2

tracerte command D2

traffic

clearing D1

controlling priority 10-7

dropping matched 10-7

forwarding 10-8

prioritizing 10-2

traffic shaping 10-1

transmission recommendations

100BASE-T 4-3, B-1

transmit-interface command D11

transmit keyword 10-8

tunnel command D2, D5

U

undebug command D3, D5

undelete command D5

upgrading the software A-11

user EXEC mode C-2

username command D8

user-profile, creating D1

V

verify command D5

verifying network connectivity C-5

Versatile Traffic Management System

see VTMS

version information, requesting D2

virtual configuration register A-6 to ??

virtual-profile command D9

VPN

MPLS 9-10, 9-11

multicast 9-19

overview 9-9

routing 9-11, 9-12

VTMS 10-19

W

warning

class 1 laser product xix

definition xix

laser beam xx

qualified personnel 3-2

weighted random early detection

See WRED

where command D2, D5

which-route command D5

working directory, displaying D4

WRED 10-1, 10-8, 10-15

write command D5

Index



Cisco MGX Route Processor Module (RPM-XF) Installation and ... · Cisco MGX Route Processor Module...

Documents

Transcript of Cisco MGX Route Processor Module (RPM-XF) Installation and ... · Cisco MGX Route Processor Module...