Cisco MGX Route Processor Module
(RPM-XF) Installation and Configuration
Guide
Release 5.2
September 2005
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
Customer Order Number: OL-6594-01
Text Part Number: OL-6594-01, Rev. C0
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.
CCSP, the Cisco Square Bridge logo, Follow Me Browsing, 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 Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco
Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation,
Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo,
iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing,
Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, 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 United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0501R)
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Copyright © 2005 Cisco Systems, Inc. All rights reserved.
C O N T E N T S
About This Guide
Objectives
Audience
xvii
xvii
xvii
Organization
xvii
Conventions xix
Warning Definition xx
Class 1 Laser Product Warning
Laser Beam Warning xxi
xxi
Documentation xxii
Documentation Notes for these Product Releases xxii
Related Documentation xxii
Technical Manual Order of Use xxiii
Technical Manual Titles and Descriptions xxiv
Obtaining Documentation xxxv
Cisco.com xxxv
Documentation DVD xxxv
Ordering Documentation xxxvi
Documentation Feedback
xxxvi
Cisco Product Security Overview xxxvi
Reporting Security Problems in Cisco Products
xxxvii
Obtaining Technical Assistance xxxvii
Cisco Technical Support Website xxxvii
Submitting a Service Request xxxviii
Definitions of Service Request Severity xxxviii
Obtaining Additional Publications and Information
CHAPTER
1
Overview of the MGX RPM-XF
Changes to this Document
RPM-XF Performance
xxxix
1-1
1-1
1-2
RPM-XF Physical Overview
1-3
RPM-XF System Specifications
Cisco MGX 8850 Cellbus
1-7
1-7
Cisco MGX 8850 Serial Bus Interface
1-8
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
iii
Contents
RPM-XF Midplane Connector
Front Panel LEDs
1-8
1-8
Cisco IOS Software Compatibility
CHAPTER
2
1-9
Preparing to Install the MGX RPM-XF
Safety Recommendations
2-1
2-1
Maintaining Safety with Electricity 2-2
Preventing Electrostatic Discharge Damage
General Site Requirements 2-3
Power Supply Considerations
Installation Checklist
Creating a Site Log
2-3
2-3
2-4
2-4
Preparing to Connect to a Network 2-5
Ethernet Connection 2-5
Console and Auxiliary Ports 2-5
Console Port Connection 2-6
Auxiliary Port Connections 2-6
CHAPTER
3
Installing the MGX RPM-XF Front and Back Cards
Inspecting the System
Required Tools and Parts
3-1
3-1
3-2
Installing and Removing the RPM-XF Cards 3-2
Before Installing Front or Back Cards 3-3
Installing the RPM-XF Front Card 3-4
Removing the RPM-XF Card 3-4
Installing and Removing Back Cards in the Cisco MGX 8850 Midplane
Installing the Back Cards 3-7
Removing the Back Cards 3-7
Installing SFP Modules 3-9
Removing SFP Modules 3-9
Connecting a Console Terminal or PC to the Console Port
CHAPTER
4
3-6
3-10
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
4-1
Overview and Features 4-1
MGX-XF-UI Management Back Card 4-2
MGX-XF-UI/B Management Back Card 4-3
Fast Ethernet Overview 4-3
IEEE 802.3u 100BASE-T Fast Ethernet Specifications
iv
4-4
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Contents
Installation Guidelines 4-5
New Installation Guidelines 4-5
Replacement Installation Guidelines
4-5
Software Configuration 4-5
Configuring the Console and Auxiliary Ports 4-6
Console and Auxiliary Port Default Values 4-6
Console and Auxiliary Port Syntax 4-6
Configuring the Console Port 4-7
Configuring the Auxiliary Port 4-7
Console and Auxiliary Port Configuration Commands 4-8
Console and Auxiliary Port Example Configuration 4-10
Configuring the Fast Ethernet Ports 4-10
Fast Ethernet Default Values 4-10
Fast Ethernet Port Syntax 4-11
Configure the Fast Ethernet Port 4-11
Fast Ethernet Port Configuration Commands 4-12
Fast Ethernet Port Example Configuration 4-12
Verifying Ethernet Connectivity 4-12
Checking System Status 4-13
Troubleshooting the Management Back Card
CHAPTER
5
4-16
Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards
MGX-1OC12POS-IR Overview and Features
5-1
5-1
MGX-2OC12POS Overview and Features
5-3
Installation Guidelines 5-6
New Installation Guidelines 5-6
Replacement Installation Guidelines
5-6
Software Configuration 5-6
Back Card Default Values 5-7
MGX-1OC12POS-IR Back Card Syntax 5-8
MGX-2 OC12POS Back Card Syntax 5-8
Configuring the Interface 5-8
Customizing the MGX-1OC12POS-IR or MGX-2OC12POS
Setting the Clock Source 5-9
Configuring Framing 5-10
Specifying SONET Overhead 5-10
Configuring POS SPE Scrambling 5-11
Configuring Loopback Testing 5-11
Example Configuration 5-12
5-9
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
v
Contents
Checking System Status
Troubleshooting the Back Card
CHAPTER
6
5-12
5-13
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
MGX-1GE Features and Specifications
6-2
MGX-2GE Features and Specifications
6-3
SFP Specifications
6-1
6-5
Installation Guidelines 6-5
First Time Installation 6-5
Replacement Installation 6-6
Software Configuration Guidelines 6-6
Back Card Default Values 6-6
Back Card Syntax 6-7
Interface Configuration 6-7
Customization 6-8
Auto Negotiation 6-8
Loopback Testing 6-9
802.1q VLAN Encapsulation 6-9
Example Configuration 6-10
System Status Check
CHAPTER
7
6-10
Installation Troubleshooting
6-16
Configuring the MGX RPM-XF
7-1
Accessing the RPM-XF Command Line Interface
7-1
Booting the RPM-XF 7-2
RPM-XF Boot Flash Memory Precautions 7-2
Verifying the Cisco IOS Files in Boot Flash Memory 7-2
Verifying the Cisco IOS Files in the PXM45 C:FW Directory 7-2
Verifying the Cisco IOS Configuration Files in the PXM45 E:RPM Directory
Initializing the RPM-XF Card 7-4
Assigning an IP Address to the Switch Interface 7-5
Booting RPM-XF Using TFTP from a TFTP Server 7-7
RPM-XF Boot-up Sequence 7-8
7-3
Verifying the Configuration 7-9
Verifying the Interface Status 7-9
Viewing the Hardware Configuration 7-10
Viewing the Boot Variable 7-11
Displaying Back Card Information 7-11
vi
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Contents
Establishing 1:N Redundancy Between Two or More RPM-XF Cards 7-13
Using switchredcd Command to Switch from Active to Standby Card
Deleting Redundancy 7-15
Adding Additional Primary Cards 7-16
Upgrading Redundant RPM-XF Cards 7-17
Upgrading Non-redundant RPM-XF Cards 7-17
Enabling IP Accounting Counters
CHAPTER
8
Configuring PNNI Communications
7-15
7-18
8-1
Configuration Quickstarts 8-1
Switch and RPM-XF Preparation Quickstart 8-1
RPM-XF to RPM-XF Connection Quickstart 8-2
RPM-XF Slave to the AXSM Master Connection Quickstart 8-4
AXSM Slave to RPM-XF Master Connection Quickstart 8-6
Configuring PNNI Connections 8-7
Verifying the PNNI Controller Configuration 8-7
Assigning Link Resources to a PNNI Controller 8-8
VPI and VCI Assignments 8-9
Bandwidth Allocations 8-10
Number of Connections 8-10
Switch Partition Provisioning 8-11
Configuring Switch Interface Signaling 8-12
Creating and Configuring a Switch Subinterface 8-13
Creating a Slave Connection on the RPM-XF 8-15
Creating a Master Connection on the RPM-XF 8-18
Connection Management 8-21
Deleting a Connection 8-21
Modifying Traffic Parameters 8-21
Downing and Upping the Connection 8-22
Rerouting the Connection 8-22
Connection Synchronization 8-22
Manually Resynchronizing Connections 8-23
Automatically Resynchronizing Connections 8-23
Connection State Alarms
CHAPTER
9
Configuring MPLS Features
8-24
9-1
MPLS Overview 9-1
ATM MPLS 9-2
MPLS in the Cisco MGX 8850 Switch
9-2
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
vii
Contents
MPLS Features 9-2
System Block Diagram 9-3
MPLS Class of Service Support 9-4
Configuring MPLS for Cisco MGX 8850 9-4
Adding an MPLS Controller to the PXM45 and Configuring an RPM-XF LSC 9-5
Adding and Partitioning an AXSM NNI Port for MPLS 9-6
Configuring an RPM-XF as an Edge Label Switch Router 9-8
Mapping an AXSM Port and ELSR Port to XTagATM Interfaces on the LSC 9-9
VPN Overview 9-9
Requirements 9-10
MPLS VPN Features 9-10
Supported Platforms 9-11
How VPNs Work 9-11
VPNs for MPLS 9-11
VPN Route-Target Communities and Export and Import Lists
iBGP Distribution of VPN Routing Information 9-12
Label Forwarding 9-12
Examples of VPN Topologies 9-12
9-11
Configuring a VPN 9-13
Prerequisites for VPN Operation 9-13
Configuring VPN Operation 9-14
Configuring VRFs 9-14
Configuring BGP 9-15
Balancing eiBGP Load Sharing 9-16
Configure Import and Export Routes 9-17
Checking the VRFs 9-18
Multicast VPN 9-18
Multicast VPN Operation 9-19
Multicast VPN Example Configuration 9-20
IP Multicast 9-20
Multicast Protocols 9-20
Multicast Protocols Supported in SP Core 9-21
Multicast Modes 9-21
Source Specific Multicast 9-21
SSM Configuration Example 9-22
mVPN Forwarding Operation 9-22
VRF Configuration Example 9-23
MPLS LDP
9-24
Support for Multi-VC on the RPM-XF
viii
9-24
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Contents
Configuring Multi-VC on the RPM-XF eLSR
CHAPTER
10
Configuring Quality of Service
9-25
10-1
General QoS Configuration Procedure 10-2
Creating a QoS Boilerplate 10-3
Creating a Class Map 10-3
Creating a Policy Map 10-3
Assigning a QoS Boilerplate to an Interface
10-4
Class Map Commands 10-4
Creating a Class Map 10-4
Matching Attributes 10-5
Policy Map Commands 10-6
Creating a Policy Map 10-6
Assigning a Class to a Policy Map 10-6
Specifying a Committed Access Rate 10-7
Enabling Weighted Random Early Detection 10-8
Bandwidth Reservation and Low-Latency Priority Queueing
Bandwidth Reservation Queueing 10-10
Low-Latency Priority Queueing 10-11
Generic Traffic Shaping 10-11
Specifying a Queue Limit 10-12
Applying Set Values 10-12
Service-Policy Command
10-10
10-13
Show Commands 10-14
show policy map 10-14
show policy-map interface
show class-map 10-15
show vlans 10-15
10-15
Quality of Service Policy Propagation Example Using Border Gateway Protocol
10-15
Versatile Traffic Management System 10-18
VTMS Buffer Management 10-19
VTMS Queuing 10-20
Queuing CLI Commands 10-20
MultiLink PPP/Link Fragmentation Interleaving
MLP/LFI Configuration 10-21
10-20
Configuring Internet Protocol Header Compression
IPHC Configuration 10-22
Compression Configuration 10-23
IPHC Command Summary 10-23
10-22
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
ix
Contents
IPHC Examples
10-25
Enabling IP Radio Access Network 10-25
IPPRAN Command Summary 10-26
hw-module rpm ipran 10-26
ppp iphc max-time 10-26
show rpm ipran 10-27
show ip rtp header-compression 10-27
Configuring IP-RAN 10-28
Configuring the RPM-XF for IP-RAN 10-28
Configuring the MPSM Card for IP-RAN 10-31
IP-RAN Examples 10-32
Configuration Example 10-32
Display Example 10-33
APPENDIX
A
Maintaining the MGX RPM-XF
Reading Front Panel LEDs
A-1
A-1
Recovering a Lost Password A-3
Password Recovery Procedure
A-4
Virtual Configuration Register Settings A-6
Changing Configuration Register Settings A-7
Virtual Configuration Register Bit Meanings A-8
Enabling Booting from the PXM Hard Disk A-10
Enabling Booting from Bootflash A-10
Copying a Cisco IOS Image to Bootflash
A-10
Recovering Boot and System Images A-12
Using the xmodem Command A-12
Using the tftpdnld Command A-13
APPENDIX
B
Cable and Connector Specifications
B-1
100BASE-T Fast Ethernet Specifications
B-1
Console and Auxiliary Port Signals and Pinouts
Identifying a Rollover Cable B-2
Console Port Signals and Pinouts B-2
Auxiliary Port Signals and Pinouts B-4
Fast Ethernet RJ-45 Connector Pinouts
SFP Specifications
x
B-2
B-6
B-7
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Contents
APPENDIX
C
Cisco IOS and Configuration Basics
C-1
Cisco IOS Software Basics C-1
Cisco IOS Modes of Operation C-1
Getting Context-Sensitive Help C-3
Saving Configuration Changes C-3
Manually Configuring RPM-XF C-4
Verifying Network Connectivity C-5
APPENDIX
D
Command Summary
D-1
User Exec Mode Commands
D-1
Privileged Exec Mode Commands
D-3
Global Configuration Mode Commands
D-6
Interface Configuration Mode Commands
QoS Configuration Mode Commands
D-10
D-13
INDEX
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xi
Contents
xii
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
F I G U R E S
Figure 1-1
RPM-XF Installed in a Cisco MGX 8850 Chassis (Front View)
Figure 1-2
RPM-XF Back Cards Installed in Cisco MGX 8850 (Back View)
Figure 1-3
RPM-XF Connected to the Cisco MGX 8850 Midplane and to the Back Cards
Figure 1-4
RPM-XF Front Panel
Figure 3-1
Backplane Inspection Check Points
Figure 3-2
Damaged Connectors on the Card
Figure 3-3
Front Card Extractor Latch
Figure 3-4
RPM-XF Installed in the Cisco MGX 8850 Chassis—Front View
Figure 3-5
RPM-XF Back Cards Connected to a Cisco MGX 8850—Back View
Figure 3-6
Installing an SFP Module
Figure 3-7
Disconnecting SFP Latch Mechanisms
Figure 3-8
Connecting a Console Terminal to the MGX-XF-UI Console Port
Figure 4-1
MGX-XF-UI and MGX-XF-UI/B Faceplate
Figure 4-2
MGX-XF-UI/B Card—Side View
Figure 5-1
MGX-1OC12POS-IR Back Card
Figure 5-2
MGX-2OC12POS Back Card
Figure 6-1
MGX-1GE Back Card
6-2
Figure 6-2
MGX-2GE Back Card
6-3
Figure 8-1
RPM-XF-to-RPM-XF Connections
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
Cisco MGX 8850s with ELSR and LSC Configured RPM-XF
Figure 9-2
VPN with a Service Provider (P) Backbone Network
Figure 9-3
VPNs Communicate with Customer Sites
Figure 9-4
Multi-VC Configuration
Figure 10-1
QoS Process
Figure 10-2
RPM-XF Routes and QoS Policy Application
Figure 10-3
IP-RAN Solution
Figure A-1
MGX RPM-XF Front Panel LEDs
Figure B-1
Identifying a Rollover Cable
Figure B-2
Connecting the Console Port to a PC
1-4
1-5
1-6
1-9
3-3
3-4
3-5
3-6
3-8
3-9
3-10
3-11
4-2
4-3
5-2
5-4
8-2
9-4
9-13
9-13
9-25
10-2
10-16
10-28
A-2
B-2
B-3
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xiii
Figures
Figure B-3
Connecting the Console Port to a Terminal
Figure B-4
Connecting the Auxiliary Port to a PC
Figure B-5
Connecting the Auxiliary Port to a Terminal
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
xiv
B-3
B-4
B-5
B-6
B-6
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
T A B L E S
Table 1-2
RPM-XF Card Specification
Table 4-1
Management Back Card Installation Troubleshooting
Table 5-1
MGX-1OC12POS-IR Front Panel LED and Port Descriptions
Table 5-2
SFP Modules and Cables
Table 5-3
MGX-1OC12POS-IR Interface Syntax
Table 5-4
MGX-2OC12POS Interface Syntax
Table 5-5
MGX-1OC12POS-IR or MGX-2OC12POS Installation Troubleshooting
Table 6-1
Cisco MGX 1GE Front Panel LED and Port Descriptions
Table 6-2
MGX-1GE or MGX-2GE Interface Syntax
Table 6-3
MGX-1GE and MGX-2GE Installation Troubleshooting
Table 8-1
Switch Partition Parameter Description
Table 8-2
Partitioning VPI/VCI Resources on the RPM-XF
Table 9-1
Multicast VPN Terms
Table 10-1
CAR Actions
Table 10-2
Configuration Commands
Table 10-3
IPHC Statistics
Table 10-4
IP-RAN Configuration Commands
Table 10-5
Virtual-Access Statistics
Table 10-6
addcon Command Parameters for the IP-RAN Solution
Table A-1
Front Panel LEDs
Table A-2
Virtual Configuration Register Bit Meaning
Table A-3
Explanation of Boot Field (Configuration Register Bits 00 to 03)
Table A-4
Default Boot Filenames
Table A-5
Configuration Register Settings for Broadcast Address Destination
Table A-6
System Console Terminal Baud Rate Settings
Table B-2
Console Port Signaling and Cabling Using a DB-25 Adapter
Table B-4
Auxiliary Port Signaling and Cabling Using a DB-25 Adapter
1-7
4-16
5-2
5-5
5-8
5-8
5-14
6-2
6-7
6-17
8-9
8-10
9-19
10-8
10-23
10-24
10-26
10-27
10-31
A-2
A-6
A-7
A-8
A-9
A-9
B-4
B-5
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xv
Tables
xvi
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
About This Guide
This section describes the objectives, audience, organization, and conventions of the Cisco MGX Route
Processor Module (RPM-XF) Installation and Configuration Guide, Release 5.2.
Objectives
This 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 Cisco 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.
Audience
This 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.
Organization
The 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 Includes basic installation information and describes how to
Cards
make connections to LANs, the main PXM1, and console.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xvii
About This Guide
Organization
Chapter
Title
Description
Chapter 4
Installing and Configuring the MGX-XF-UI Describes how to install and configure the MGX-XF-UI
and MGX-XF-UI/B Management Back Cards 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 Cisco MGX 8850 switch.
Chapter 10
Configuring Quality of Service
Describes how to configure QoS7 on the RPM-XF. Also
describes IPRAN configuration.
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
xviii
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
About This Guide
Conventions
Conventions
This 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
•
Nonprinting characters, such as passwords, are in angle brackets (< >).
•
Default responses to system prompts are in square brackets ([ ]).
screen
font.
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
Warning
Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xix
About This Guide
Conventions
Warning Definition
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
Advarsel
Aviso
xx
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.
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.
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
About This Guide
Conventions
Class 1 Laser Product Warning
Warning
Waarschuwing
Varoitus
Class 1 laser product.
Klasse-1 laser produkt.
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!
Varning!
Producto láser Clase I.
Laserprodukt av klass 1.
Laser Beam Warning
Warning
Waarschuwing
Varoitus
Do not stare into the beam or view it directly with optical instruments.
Niet in de straal staren of hem rechtstreeks bekijken met optische instrumenten.
Ä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
Advarsel
Aviso
Non fissare il raggio con gli occhi né usare strumenti ottici per osservarlo direttamente.
Stirr eller se ikke direkte pŒ strŒlen med optiske instrumenter.
Não olhe fixamente para o raio, nem olhe para ele directamente com instrumentos ópticos.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xxi
About This Guide
Documentation
¡Advertencia!
Varning!
No mirar fijamente el haz ni observarlo directamente con instrumentos ópticos.
Rikta inte blicken in mot strålen och titta inte direkt på den genom optiska instrument.
Documentation
A Guide to Cisco Multiservice Switch Documentation document ships with your product. That guide
contains general information about how to locate Cisco MGX, BPX, SES, and CWM documentation
online.
Documentation Notes for these Product Releases
This release includes new hardware or features for the following releases:
•
Cisco MGX Release 5.2 introduces the Cisco MGX 8850/B multiservice switch
•
Cisco MGX Release 5.2, for these multiservice switches:
– Cisco MGX 8850 (PXM1E)
– Cisco MGX 8850 (PXM45)
– Cisco MGX 8950
– Cisco MGX 8830
•
Cisco MGX Release 1.3, for these multiservice switches:
– Cisco MGX 8850 (PXM1)
– Cisco MGX 8230
– Cisco MGX 8250
•
Cisco MGX Release 5.2, for the Route Processor Modules (RPM-XF and RPM-PR)
•
Cisco WAN Manager Release 15.1. CWM Release 15 introduced a helpful new documentation
feature: web-based online help. To invoke online help, press F1 on a PC, press the Help key on a
UNIX workstation, or select Help from the main or popup menu. Cisco WAN Manager online help
has been updated for Release 15.1.
Other components of multiservice WAN products, such as the Service Expansion Shelf (SES) and WAN
switching software have no new features for this release.
Related Documentation
This section describes the technical manuals and release notes that support this release of Cisco
Multiservice Switch products.
xxii
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
About This Guide
Documentation
Technical Manual Order of Use
Use the technical manuals listed here in the following order:
Step 1
Refer to the documents that ship with your product. Observe all safety precautions.
•
Regulatory Compliance and Safety Information for Cisco Multiservice Switch Products (MGX, BPX,
and SES)—This document familiarizes you with safety precautions for your product.
•
Guide to Cisco Multiservice Switch Documentation—This document explains how to find
documentation for MGX, BPX, and SES multiservice switches and media gateways as well as CWM
network management software. These documents are available only online.
•
Installation Warning Card—This document provides precautions about installing your cards. It
explains such subjects as removing the shipping tab and inserting cards properly into the correct
slots.
Step 2
Refer to the release notes for your product.
Step 3
If your network uses the CWM network management system, upgrade CWM. (If you are going to install
CWM for the first time, do so after Step 4.) Upgrade instructions are included in the following
documents:
Step 4
•
Cisco WAN Manager Installation Guide, Release 15.1
•
Cisco WAN Manager User’s Guide, Release 15.1
If your network contains MGX and SES products, refer to this manual for planning information:
•
Step 5
Step 6
Step 7
Step 8
Note
Cisco PNNI Network Planning Guide for MGX and SES Products
Refer to these manuals for information about installing cards and cables in the MGX chassis:
•
Cisco MGX 8800/8900 Hardware Installation Guide, Releases 2 - 5.2 for installing cards and cables
in these chassis.
•
Cisco MGX 8xxx Edge Concentrator Installation and Configuration Guide for installing cards and
cables in the Cisco MGX 8230, Cisco MGX 8250, or Cisco MGX 8850 (PXM1) chassis.
Refer to the manuals that help you configure your MGX switch and processor cards:
•
Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 for these chassis.
•
Cisco MGX 8xxx Edge Concentrator Installation and Configuration Guide for the Cisco MGX 8230,
Cisco MGX 8250, or Cisco MGX 8850 (PXM1) chassis.
Refer to the manual that supports the additional cards you intend to install in your switch. For example:
•
The services books can help you establish ATM, Frame Relay, or circuit emulation services on your
switch.
•
The VISM book can help you set up your switch as a voice gateway, and the RPM book can help
you implement IP on the switch.
Additional books, such as command reference guides and error message books, can help with the daily
operation and maintenance of your switch.
Manual titles may be different for earlier software releases. The titles shown in Table 1 are for the
September 2005 release.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xxiii
About This Guide
Documentation
Technical Manual Titles and Descriptions
Table 1 lists the technical manuals and release notes that support the September 2005 multiservice
switch product releases. Books and release notes in Table 1 are listed in order of use and include
information about which multiservice switch or media gateway the document supports.
The books for Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) switches were not
updated for the September 2005 release, therefore, some information about configuring and using the
new MPSM-8-T1E1 card in these switches is included in the following books:
•
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX
Switches, Release 5.2
•
Cisco Frame Relay Services (FRSM/MPSM) Configuration Guide and Command Reference for
MGX Switches, Release 5.2
•
Cisco Circuit Emulation Services (CESM/MPSM) Configuration Guide and Command Reference for
MGX Switches, Release 5.2
Information about how to install or upgrade to the MPSM-8-T1E1 card in Cisco MGX 8230, Cisco
MGX 8250, and Cisco MGX 8850 (PXM1) switches is in the Release Notes for Cisco MGX 8230, Cisco
MGX 8250, and Cisco MGX 8850 (PXM1) Switches, Release 1.3.11.
Note
Refer to each product’s release notes for the latest information on features, bug fixes, and more.
Terms
Two main types of ATM cards are used in MGX switches: AXSM and AUSM. AXSM stands for ATM
Switching Service Module. AUSM stands for ATM UNI (User Network Interface) Service Module.
CWM stands for Cisco WAN Manager, our multiservice switch network management system.
Legacy service module refers to a previously introduced card. For this release, the term is used
specifically for the CESM-8-T1E1, FRSM-8-T1E1, and AUSM-8-T1E1 cards, which can now be
replaced by the new MPSM-8-T1E1 card.
MPSM stands for Multiprotocol Service Module.
RPM stands for Route Processor Module.
SES stands for Service Expansion Shelf.
VISM stands for Voice Interworking Service Module.
VXSM stands for Voice Switch Service Module.
Table 1
Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (September 2005
Product Releases)
Document Title and Part Number
MGX
BPX
MGX
MGX
8850
with SES 8230 Rel. 8250 Rel. (PXM1)
Rel. 4
1.3
1.3
Rel. 1.3
MGX
8830
Rel. 5.2
MGX
8850
(PXM1E)
Rel. 5.2
MGX
8850
(PXM45)
Rel. 5.2
MGX
8950
Rel. 5.2
MGX
8880
Rel. 5.2.
x
x
x
x
x
Overview and Safety Documents
Guide to Cisco Multiservice Switch x
Documentation
x
x
x
DOC-7814807=
xxiv
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
About This Guide
Documentation
Table 1
Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (September 2005
Product Releases) (continued)
Document Title and Part Number
MGX
BPX
MGX
MGX
8850
with SES 8230 Rel. 8250 Rel. (PXM1)
Rel. 4
1.3
1.3
Rel. 1.3
MGX
8830
Rel. 5.2
MGX
8850
(PXM1E)
Rel. 5.2
MGX
8850
(PXM45)
Rel. 5.2
MGX
8950
Rel. 5.2
MGX
8880
Rel. 5.2.
Installation Warning Card
x
x
x
x
x
x
x
x
x
Regulatory Compliance and Safety x
Information for Cisco Multiservice
Switch Products (MGX, BPX, and
SES)
x
x
x
x
x
x
x
x
—
—
—
—
—
—
—
—
x
Release Notes for Cisco MGX 8850 —
(PXM1E/PXM45), Cisco MGX
8950, and Cisco MGX 8830
Switches, Release 5.2.00
—
—
—
x
x
x
x
x
x
x
—
—
—
—
—
—
—
—
—
—
—
x
—
x
x
x
x
x
x
x
x
x
x
—
x
x
x
x
x
x
—
x
—
—
—
x
—
x
x
x
DOC-7812348=
DOC-7814790=
Release Notes for the Cisco MGX
8880 Media Gateway, Release
5.0.02
OL-6493-01
OL-6478-01
Release Notes for Cisco MGX 8230, —
Cisco MGX 8250, and Cisco MGX
8850 (PXM1) Switches, Release
1.3.11
OL-4539-01
Release Notes for the Cisco Voice
Switch Service Module (VXSM),
Release 5.0.02
OL-4627-01
Release Notes for Cisco WAN
Manager, Release 15.1.00
OL-6495-01
Release Notes for the Cisco Voice
Interworking Service Module
(VISM), Release 3.3
OL-5357-01
—
Release Notes for Cisco MGX
Route Processor Module (RPM-XF)
IOS Release 12.3(11)T3 for
PXM45-based Switches, Release
5.1.00
OL-4536-01
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xxv
About This Guide
Documentation
Table 1
Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (September 2005
Product Releases) (continued)
Document Title and Part Number
MGX
BPX
MGX
MGX
8850
with SES 8230 Rel. 8250 Rel. (PXM1)
Rel. 4
1.3
1.3
Rel. 1.3
—
Release Notes for Cisco MGX
Route Processor Module (RPM-PR)
IOS Release 12.3(11)T3 for MGX
Releases 1.3.11 and 5.1.00
MGX
8830
Rel. 5.2
MGX
8850
(PXM1E)
Rel. 5.2
MGX
8850
(PXM45)
Rel. 5.2
MGX
8950
Rel. 5.2
MGX
8880
Rel. 5.2.
x
x
x
x
x
x
x
x
—
x
—
—
—
—
—
—
—
—
—
x
—
—
—
—
—
—
—
—
—
x
—
—
—
—
—
—
Cisco MGX 8800/8900 Hardware
Installation Guide, Releases 2 - 5.2
—
—
—
x
x
x
x
x
x
—
—
—
—
—
—
—
—
x
—
—
—
x
x
x
x
x
—
—
—
—
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Cisco WAN Manager User’s Guide, x
Release 15.1
x
x
x
x
x
x
x
x
OL-4535-01
Cisco MGX 8230 Edge
Concentrator Overview, Release
1.1.31
DOC-7812899=
Cisco MGX 8250 Edge
Concentrator Overview, Release
1.1.31
DOC-7811576=
Cisco MGX 8850 Multiservice
Switch Overview, Release 1.1.31
OL-1154-01
Hardware Installation Guides
OL-4545-01
Cisco Service Expansion Shelf
Hardware Installation Guide,
Release 11
DOC-786122=
Planning and Configuration Guides
Cisco PNNI Network Planning
Guide for MGX and SES Products
OL-3847-01
Cisco MGX 8800/8900 Series
Configuration Guide, Release 5.2
OL-6482-01
Cisco WAN Manager Installation
Guide, Release 15.1
OL-6259-01
OL-6257-01
xxvi
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
About This Guide
Documentation
Table 1
Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (September 2005
Product Releases) (continued)
Document Title and Part Number
Cisco MGX 8850 Edge
Concentrator Installation and
Configuration, Release 1.1.31
MGX
BPX
MGX
MGX
8850
with SES 8230 Rel. 8250 Rel. (PXM1)
Rel. 4
1.3
1.3
Rel. 1.3
MGX
8830
Rel. 5.2
MGX
8850
(PXM1E)
Rel. 5.2
MGX
8850
(PXM45)
Rel. 5.2
MGX
8950
Rel. 5.2
MGX
8880
Rel. 5.2.
—
—
—
x
—
—
—
—
—
x
—
—
—
—
—
—
—
—
—
x
—
—
—
—
—
—
—
—
—
x
—
—
—
—
—
—
x
x
x
—
—
—
—
—
—
—
—
—
—
x
—
—
2
2
2
x
x
x
—
—
2
2
2
x
x
x
—
—
DOC-7811223=
Cisco SES PNNI Controller
Software Configuration Guide,
Release 31
DOC-7814258=
Cisco MGX 8230 Edge
Concentrator Installation and
Configuration, Release 1.1.31
DOC-7811215=
Cisco MGX 8250 Edge
Concentrator Installation and
Configuration, Release 1.1.31
DOC-7811217=
Service Module Configuration and Reference Guides
—
Cisco MGX Route Processor
Module (RPM-PR) Installation and
Configuration Guide, Release 5.21
78-12510-02
Frame Relay Software
—
Configuration Guide and Command
Reference for the Cisco MGX 8850
FRSM12 Card, Release 31
DOC-7810327=
Cisco ATM Services
—
(AUSM/MPSM) Configuration
Guide and Command Reference for
MGX Switches, Release 5.22
OL-6479-01
Cisco Frame Relay Services
—
(FRSM/MPSM) Configuration
Guide and Command Reference for
MGX Switches, Release 5.22
OL-6480-01
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xxvii
About This Guide
Documentation
Table 1
Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (September 2005
Product Releases) (continued)
Document Title and Part Number
MGX
BPX
MGX
MGX
8850
with SES 8230 Rel. 8250 Rel. (PXM1)
Rel. 4
1.3
1.3
Rel. 1.3
Cisco Circuit Emulation Services
—
(CESM/MPSM) Configuration
Guide and Command Reference for
MGX Switches, Release 5.22
2
2
2
—
—
—
MGX
8830
Rel. 5.2
MGX
8850
(PXM1E)
Rel. 5.2
MGX
8850
(PXM45)
Rel. 5.2
MGX
8950
Rel. 5.2
MGX
8880
Rel. 5.2.
x
x
x
—
—
—
—
—
x
x
x
—
—
—
—
x
x
x
—
—
—
x
—
x
—
—
—
—
—
—
—
—
x
—
x
—
x
x
x
x
x
x
—
x
—
x
—
—
—
—
—
—
—
—
x
—
—
—
—
—
—
—
OL-6481-01
—
Cisco MGX Route Processor
Module (RPM-XF) Installation and
Configuration Guide, Release 5.21
OL-5087-01
—
Cisco ATM Services (AXSM)
Configuration Guide and Command
Reference for MGX Switches,
Release 5.2
OL-6484-01
—
Cisco ATM and Frame Relay
Services (MPSM-T3E3-155 and
MPSM-16-T1E1) Configuration
Guide and Command Reference for
MGX Switches, Release 5.2
OL-6487-01
Cisco Voice Switch Services
(VXSM) Configuration Guide and
Command Reference for MGX
Switches, Release 5
OL-4625-01
Cisco Voice Interworking Services
(VISM) Configuration Guide and
Command Reference, Release 3.3
OL-5358-01
Reference Guides
Cisco MGX 8230 Multiservice
Gateway Error Messages, Release
1.1.31
DOC-78112113=
Cisco MGX 8230 Multiservice
Gateway Command Reference,
Release 1.1.31
DOC-7811211=
xxviii
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
About This Guide
Documentation
Table 1
Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (September 2005
Product Releases) (continued)
Document Title and Part Number
Cisco MGX 8250 Multiservice
Gateway Command Reference,
Release 1.1.31
MGX
BPX
MGX
MGX
8850
with SES 8230 Rel. 8250 Rel. (PXM1)
Rel. 4
1.3
1.3
Rel. 1.3
MGX
8830
Rel. 5.2
MGX
8850
(PXM1E)
Rel. 5.2
MGX
8850
(PXM45)
Rel. 5.2
MGX
8950
Rel. 5.2
MGX
8880
Rel. 5.2.
—
—
x
—
—
—
—
—
—
—
—
x
—
—
—
—
—
—
—
x
x
x
—
—
—
—
—
—
x
x
x
—
—
—
—
—
x
—
—
—
—
—
—
—
—
—
—
—
—
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
—
—
—
x
x
x
x
x
DOC-7811212=
Cisco MGX 8250 Multiservice
Gateway Error Messages, Release
1.1.31
DOC-7811216=
Cisco MGX 8800 Series Switch
Command Reference, Release
1.1.31
DOC-7811210=
Cisco MGX 8800 Series Switch
System Error Messages, Release
1.1.31
DOC-7811240=
Cisco SES PNNI Controller
Command Reference, Release 31
DOC-7814260=
Cisco MGX 8800/8900 Series
Command Reference, Release 5.2
OL-6483-01
Cisco WAN Manager SNMP Service x
Agent, Release 15.1
OL-6260-01
Cisco WAN Manager Database
Interface Guide, Release 15.1
x
OL-6261-01
Cisco MGX and Service Expansion x
Shelf Error Messages, Release 5.2
OL-6485-01
1. This document was not updated for the September 2005 release.
2. Some configuration and command information is included in this book for using the multiprotocol service module (MPSM-8-T1E1/MPSM-16-T1E1) in
a Cisco MGX 8230, MGX 8250, or MGX 8850 (PXM1) switch.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xxix
About This Guide
Documentation
Note
For the September 2005 product release, there are no new features for the Service Expansion Shelf (SES)
of the BPX switch and BPX WAN switching software. Therefore, documentation for these items was not
updated. Table 1 lists the most recent technical manuals and release notes for these products.
Table 1 also lists the latest documentation available for the Cisco MGX 8230, Cisco MGX 8250, and
Cisco MGX 8850 (PXM1) switches. These switches use the PXM1 processor card. Although there are
new features in MGX Release 1.3 for these switches, only the release notes were updated. And the
following books contain some information about configuring the MPSM-8-T1E1 and MPSM-16-T1E1
cards for use in these switches:
•
Cisco Circuit Emulation Services (CESM/MPSM) Configuration Guide and Command Reference for
MGX Switches, Release 5.2
•
Cisco Frame Relay Services (FRSM/MPSM) Configuration Guide and Command Reference for
MGX Switches, Release 5.2
•
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX
Switches, Release 5.2
Table 2 lists the documents that ship with product.
Table 3 contains alphabetized titles and descriptions of all the manuals and release notes listed in
Table 1.
Table 2
Documents that Ship with Multiservice Switch Products
Document Title
Description
Guide to Cisco Multiservice Switch Documentation
Describes how to find the manuals and release notes that
support multiservice switches and network management
products. These documents are available only online. This
guide ships with product.
DOC-7817081=
Installation Warning Card
DOC-7812348=
Regulatory Compliance and Safety Information for Cisco
Multiservice Switch Products (MGX, BPX, and SES)
DOC-7814790=
xxx
Contains precautions that you should take before you
insert a card into a slot. This Warning Card ships with
product.
Provides regulatory compliance information, product
warnings, and safety recommendations for all the Cisco MGX
multiservice switches: MGX 8230, MGX 8250, MGX 8850
(PXM1), MGX 8850 (PXM45), MGX 8850 (PXM1E), MGX
8830 and MGX 8950. Also provides such information for the
MGX 8880 Media Gateway. This book ships with product.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
About This Guide
Documentation
Table 3
Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products
Document Title
Description
Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and Provides software configuration procedures for provisioning
ATM and Frame Relay connections on the new
MPSM-16-T1E1) Configuration Guide and Command
MPSM-T3E3-155 multiprotocol service module. Also
Reference for MGX Switches, Release 5.2
describes all MPSM-T3E3-155 commands.
OL-6487-01
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Provides software configuration procedures for provisioning
connections and managing the AUSM cards supported in this
Command Reference for MGX Switches, Release 5.2
release. Also describes all AUSM commands. Includes
OL-6479-01
software configuration procedures for provisioning
connections and managing the MPSM-8-T1E1 card as an
AUSM card replacement.
Cisco ATM Services (AXSM) Configuration Guide and
Command Reference for MGX Switches, Release 5.2
OL-4548-01
Cisco Circuit Emulation Services (CESM/MPSM)
Configuration Guide and Command Reference for MGX
Switches, Release 5.2
OL-6481-01
Cisco Frame Relay Services (FRSM/MPSM) Configuration
Guide and Command Reference for MGX Switches, Release
5.2
OL-6480-01
Cisco MGX 8230 Edge Concentrator Installation and
Configuration, Release 1.1.3
Explains how to configure the AXSM cards and provides 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.
Provides software configuration procedures for provisioning
connections and managing the Circuit Emulation Service
Module (CESM) cards supported in this release. Also
describes all CESM commands. Includes software
configuration procedures for provisioning connections and
managing the MPSM-8-T1E1 card as a CESM card
replacement.
Provides software configuration procedures for provisioning
connections and managing the Frame Relay Service Module
(FRSM) cards supported in this release. Also describes all
FRSM commands. Includes software configuration
procedures for provisioning connections and managing the
MPSM-8-T1E1 card as an FRSM card replacement.
Provides installation instructions for the Cisco MGX 8230
edge concentrator.
DOC-7811215=
Cisco MGX 8230 Edge Concentrator Overview, Release 1.1.3 Describes the system components and function of the
Cisco MGX 8250 edge concentrator.
DOC-7812899=
Cisco MGX 8230 Multiservice Gateway Command Reference, Provides detailed information on the general command line
Release 1.1.3
interface commands.
DOC-7811211=
Cisco MGX 8230 Multiservice Gateway Error Messages,
Release 1.1.3
Provides error message descriptions and recovery
procedures.
DOC-78112113=
Cisco MGX 8250 Edge Concentrator Installation and
Configuration, Release 1.1.3
Provides installation instructions for the Cisco MGX 8250
edge concentrator.
DOC-7811217=
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xxxi
About This Guide
Documentation
Table 3
Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued)
Document Title
Description
Cisco MGX 8250 Edge Concentrator Overview, Release 1.1.3 Describes the system components and function of the
Cisco MGX 8250 edge concentrator.
DOC-7811576=
Cisco MGX 8250 Multiservice Gateway Command Reference, Provides detailed information on the general command line
Release 1.1.3
interface commands.
DOC-7811212=
Cisco MGX 8250 Multiservice Gateway Error Messages,
Release 1.1.3
Provides error message descriptions and recovery
procedures.
DOC-7811216=
Cisco MGX 8800 Series Switch Command Reference, Release Provides detailed information on the general command line
for the Cisco MGX 8850 (PXM1), Cisco MGX 8250, and
1.1.3
Cisco MGX 8230 edge concentrators.
DOC-7811210=
Cisco MGX 8800 Series Switch System Error Messages,
Release 1.1.3
DOC-7811240=
Cisco MGX 8800/8900 Hardware Installation Guide,
Releases 2 - 5.2
OL-4545-01
Cisco MGX 8800/8900 Series Configuration Guide, Release
5.2
OL-6482-01
Cisco MGX 8800/8900 Series Command Reference, Release
5.2
OL-6483-01
xxxii
Provides error message descriptions and recovery procedures
for Cisco MGX 8850 (PXM1), Cisco MGX 8250, and
Cisco MGX 8230 edge concentrators.
Describes how to install the Cisco MGX 8950, the
Cisco MGX 8850 (PXM1E/PXM45), the Cisco MGX
8850/B (PXM1E/PXM45), and the Cisco MGX 8830
switches. Also describes how to install the MGX 8880 Media
Gateway. This document 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 8830 switch uses a PXM1E controller card
and supports cell bus-based service modules. The Cisco
MGX 8950 supports only serial bus-based service modules.
The Cisco MGX 8880 uses a PXM45/C controller card, and
supports only serial bus-based service modules. This
hardware installation guide replaces all previous hardware
guides for these switches.
Describes how to configure the Cisco MGX 8880 Media
Gateway. Also describes how to configure Cisco MGX 8850
(PXM1E), Cisco MGX 8850 (PXM45), the Cisco MGX
8850/B (PXM1E/PXM45), and Cisco MGX 8830 switches to
operate as ATM edge switches and the Cisco MGX 8950
switch to operate as a core switch. This guide also provides
some operation and maintenance procedures.
Describes the PXM commands that are available in the CLI
of the Cisco MGX 8850 (PXM45), Cisco MGX 8850
(PXM1E), Cisco MGX 8950, and Cisco MGX 8830 switches.
Also describes the PXM commands that are available in the
CLI of the Cisco MGX 8880 Media Gateway.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
About This Guide
Documentation
Table 3
Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued)
Document Title
Description
Cisco MGX 8850 Edge Concentrator Installation and
Configuration, Release 1.1.3
Provides installation instructions for the Cisco MGX 8850
(PXM1) edge concentrator.
DOC-7811223=
Cisco MGX 8850 Multiservice Switch Overview, Release 1.1.3 Describes the system components and function of the
Cisco MGX 8850 (PXM1) edge concentrator.
OL-1154-01
Cisco MGX and Service Expansion Shelf Error Messages,
Release 5.2
Provides error message descriptions and recovery
procedures.
OL-6485-01
Cisco MGX Route Processor Module (RPM-XF) Installation
and Configuration Guide, Release 5.2
OL-6954-01
Cisco MGX Route Processor Module (RPM-PR) Installation
and Configuration Guide, Release 5.2
OL-7349-01
Describes how to install and configure the Cisco MGX Route
Processor Module (RPM-XF) in the Cisco MGX 8850
(PXM45), Cisco MGX 8880 (PXM45), and Cisco MGX 8950
switch. Also provides site preparation procedures,
troubleshooting procedures, maintenance procedures, cable
and connector specifications, and basic Cisco IOS
configuration information.
Describes how to install and configure the Cisco MGX Route
Processor Module (RPM/B or RPM-PR) in the
Cisco MGX 8850 (PXM1), 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.
OL-3847-01
Provides guidelines for planning a PNNI network that uses
Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E),
Cisco MGX 8950, or Cisco BPX 8600 switches or the
MGX 8880 Media Gateway. When connected to a PNNI
network, each Cisco BPX 8600 Series switch requires an SES
for PNNI route processing.
Cisco Service Expansion Shelf Hardware Installation Guide,
Release 1
Provides instructions for installing and maintaining an SES
controller.
Cisco PNNI Network Planning Guide for MGX and SES
Products
DOC-786122=
Cisco SES PNNI Controller Command Reference, Release 3
DOC-7814260=
Cisco SES PNNI Controller Software Configuration Guide,
Release 3
Describes the commands used to configure and operate the
SES PNNI controller.
Describes how to configure, operate, and maintain the SES
PNNI controller.
DOC-7814258=
Cisco Voice Interworking Services (VISM) Configuration
Guide and Command Reference, Release 3.3
OL-5358-01
Describes how to install and configure the Voice
Interworking Service Module (VISM) in the Cisco
MGX 8830, Cisco MGX 8850 (PXM45), and Cisco MGX
8850 (PXM1E) multiservice switches. Provides site
preparation procedures, troubleshooting procedures,
maintenance procedures, cable and connector specifications,
and Cisco CLI configuration information.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xxxiii
About This Guide
Documentation
Table 3
Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued)
Document Title
Description
Cisco Voice Switch Services (VXSM) Configuration and
Command Reference Guide for MGX Switches, Release 5
Describes the features and functions of the new Voice Switch
Service Module (VXSM) in the Cisco MGX 8880 Media
Gateway and in the Cisco MGX8850 (PXM45 and PXM1E)
multiservice switches. Also provides configuration
procedures, troubleshooting procedures, and Cisco CLI
configuration information.
OL-4625-01
Cisco WAN Manager Database Interface Guide, Release 15.1 Provides information about accessing the CWM Informix
database that is used to store information about the network
OL-6261-01
elements.
Cisco WAN Manager Installation Guide, Release 15.1
OL-6259-01
Cisco WAN Manager SNMP Service Agent, Release 15.1
OL-6260-01
Cisco WAN Manager User’s Guide, Release 15.1
OL-6257-01
Provides procedures for installing Release 15.1 of the CWM
network management system.
Provides information about the CWM Simple Network
Management Protocol service agent, an optional adjunct to
CWM that is used for managing Cisco WAN switches
through SNMP.
Describes how to use the CWM Release 15.1 software, which
consists of user applications and tools for network
management, connection management, network
configuration, statistics collection, and security management.
Note
The CWM interface now has built-in documentation
support in the form of online Help. On a PC, press F1
to access Help; on a UNIX workstation, press the
Help key. Alternatively, on either system you can
select Help from the main or popup menu.
Frame Relay Software Configuration Guide and Command
Describes how to use the high-speed Frame Relay
Reference for the Cisco MGX 8850 FRSM12 Card, Release 3 (FRSM-12-T3E3) commands that are available in the CLI of
the Cisco MGX 8850 (PXM45) switch.
DOC-7810327=
Release Notes for Cisco MGX 8230, Cisco MGX 8250, and
Cisco MGX 8850 (PXM1) Switches, Release 1.3.11
OL-4539-01
Provides new feature, upgrade, and compatibility
information, as well as information about known and
resolved anomalies.
Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco Provides new feature, upgrade, and compatibility
information, as well as information about known and
MGX 8950, and Cisco MGX 8830 Switches, Release 5.2.00
resolved anomalies.
OL-6478-01
Release Notes for the Cisco MGX 8880 Media Gateway,
Release 5.0.02
Provides new feature and compatibility information, as well
as information about known and resolved anomalies.
OL-6493-01
Provides upgrade and compatibility information, as well as
Release Notes for Cisco MGX Route Processor Module
(RPM-PR) IOS Release 12.3(11)T3 for MGX Releases 1.3.11 information about known and resolved anomalies.
and 5.1.00
OL-7292-01
xxxiv
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
About This Guide
Obtaining Documentation
Table 3
Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued)
Document Title
Description
Release Notes for Cisco MGX Route Processor Module
(RPM-XF) IOS Release 12.3(11)T3 for PXM45-based
Switches, Release 5.1.00
Provides upgrade and compatibility information, as well as
information about known and resolved anomalies.
OL-7059-01
Release Notes for the Cisco Voice Interworking Service
Module (VISM), Release 3.3
OL-5357-01
Release Notes for the Cisco Voice Switch Service Module
(VXSM), Release 5.0.02
OL-7088-01
Release Notes for Cisco WAN Manager, Release 15.1.00
OL-6495-01
Provides new feature, upgrade, and compatibility
information, as well as information about known and
resolved anomalies.
Provides new feature, upgrade, and compatibility
information, as well as information about known and
resolved anomalies.
Provides new feature, upgrade, and compatibility
information, as well as information about known and
resolved anomalies.
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several
ways to obtain technical assistance and other technical resources. These sections explain how to obtain
technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
http://www.cisco.com
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation DVD
Cisco documentation and additional literature are available in a Documentation DVD package, which
may have shipped with your product. The Documentation DVD is updated regularly and may be more
current than printed documentation. The Documentation DVD package is available as a single unit.
Registered Cisco.com users (Cisco direct customers) can order a Cisco Documentation DVD (product
number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.
Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xxxv
About This Guide
Documentation Feedback
Cisco Marketplace:
http://www.cisco.com/go/marketplace/
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from
the Ordering tool:
http://www.cisco.com/en/US/partner/ordering/
•
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 1 800 553-NETS (6387).
Documentation Feedback
You can send comments about technical documentation 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 Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you can perform these tasks:
•
Report security vulnerabilities in Cisco products.
•
Obtain assistance with security incidents that involve Cisco products.
•
Register to receive security information from Cisco.
A current list of security advisories and notices for Cisco products is available at this URL:
http://www.cisco.com/go/psirt
If you prefer to see advisories and notices as they are updated in real time, you can access a Product
Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
xxxvi
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
About This Guide
Obtaining Technical Assistance
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them,
and we strive to correct all vulnerabilities quickly. If you think that you might have identified a
vulnerability in a Cisco product, contact PSIRT:
Tip
•
Emergencies — [email protected]
•
Nonemergencies — [email protected]
We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive
information that you send to Cisco. PSIRT can work from encrypted information that is compatible with
PGP versions 2.x through 8.x.
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence
with PSIRT is the one that has the most recent creation date in this public key server list:
http://pgp.mit.edu:11371/pks/lookup?search=psirt%40cisco.com&op=index&exact=on
In an emergency, you can also reach PSIRT by telephone:
•
1 877 228-7302
•
1 408 525-6532
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco
Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical
Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical
Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service
contract, contact your reseller.
Cisco Technical Support Website
The Cisco Technical Support Website provides online documents and tools for troubleshooting and
resolving technical issues with Cisco products and technologies. The website is available 24 hours a day,
365 days a year, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password.
If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xxxvii
About This Guide
Obtaining Technical Assistance
Note
Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting
a web or phone request for service. You can access the CPI tool from the Cisco Technical Support
Website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product
Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product
Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID
or model name; by tree view; or for certain products, by copying and pasting show command output.
Search results show an illustration of your product with the serial number label location highlighted.
Locate the serial number label on your product and record the information before placing a service call.
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3
and S4 service requests are those in which your network is minimally impaired or for which you require
product information.) After you describe your situation, the TAC Service Request Tool provides
recommended solutions. If your issue is not resolved using the recommended resources, your service
request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone.
(S1 or S2 service requests are those in which your production network is down or severely degraded.)
Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business
operations running smoothly.
To open a service request 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 list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity
definitions.
Severity 1 (S1)—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.
Severity 2 (S2)—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.
Severity 3 (S3)—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.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or
configuration. There is little or no effect on your business operations.
xxxviii
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
About This Guide
Obtaining Additional Publications and Information
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online
and printed sources.
•
Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit
Cisco Marketplace, the company store, at this URL:
http://www.cisco.com/go/marketplace/
•
Cisco Press publishes a wide range of general networking, training and certification titles. Both new
and experienced users will benefit from these publications. For current Cisco Press titles and other
information, go to Cisco Press at this URL:
http://www.ciscopress.com
•
Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and
networking investments. Each quarter, Packet delivers coverage of the latest industry trends,
technology breakthroughs, and Cisco products and solutions, as well as network deployment and
troubleshooting tips, configuration examples, customer case studies, certification and training
information, and links to scores of in-depth online resources. You can access Packet magazine at
this URL:
http://www.cisco.com/packet
•
iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies
learn how they can use technology to increase revenue, streamline their business, and expand
services. The publication identifies the challenges facing these companies and the technologies to
help solve them, using real-world case studies and business strategies to help readers make sound
technology investment decisions. 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/ipj
•
World-class networking training is available from Cisco. You can view current offerings at
this URL:
http://www.cisco.com/en/US/learning/index.html
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
xxxix
About This Guide
Obtaining Additional Publications and Information
xl
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
C H A P T E R
1
Overview of the MGX RPM-XF
This chapter provides an overview of the MGX Route Processor Module (RPM-XF) and its relationship
to the Cisco MGX 8850 switch. This chapter contains the following sections:
•
Changes to this Document
•
RPM-XF Performance
•
RPM-XF Physical Overview
•
RPM-XF System Specifications
•
Cisco MGX 8850 Cellbus
•
Cisco MGX 8850 Serial Bus Interface
•
RPM-XF Midplane Connector
•
Front Panel LEDs
•
Cisco IOS Software Compatibility
Changes to this Document
Table 1-1 summarizes the changes made to this document since Release 5.1.
Table 1-1
Changes to This Guide Since the Previous Release
Section and Link
Status
Description
Chapter 3, “Installing the MGX RPM-XF
Front and Back Cards”
New
•
Added sections Installing SFP Modules, page 3-9 and
Removing SFP Modules, page 3-9
Chapter 4, “Installing and Configuring the
MGX-XF-UI and MGX-XF-UI/B
Management Back Cards”
New
•
Added section MGX-XF-UI/B Management Back Card,
page 4-3
Chapter 5, “Installing and Configuring the
MGX-1OC12POS and the
MGX-2OC12POS Back Cards”
Changed
•
Updated SFP specifications in MGX-2OC12POS Overview
and Features, page 5-3
•
Updated faceplate image in MGX-2OC12POS Overview
and Features, page 5-3
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
1-1
Chapter 1
Overview of the MGX RPM-XF
RPM-XF Performance
Table 1-1
Changes to This Guide Since the Previous Release (continued)
Section and Link
Status
Chapter 6, “Installing and Configuring the
Cisco MGX-1GE and MGX-2GE Gigabit
Ethernet Back Cards”
Changed
Chapter 10, “Configuring Quality of
Service”
Changed
Description
•
Updated section SFP Specifications, page 6-5
•
Updated faceplate image in MGX-2GE Features and
Specifications, page 6-3
•
Merged most MGX-1GE and MGX-2GE subsections
•
Expanded section Configuring Internet Protocol Header
Compression, page 10-22
•
Added new section Enabling IP Radio Access Network,
page 10-25
Appendix B, “Cable and Connector
Specifications”
Changed
•
Updated section SFP Specifications, page B-7
Appendix D, “Command Summary”
Changed
•
Updated section User Exec Mode Commands, page D-1
•
Updated section Privileged Exec Mode Commands,
page D-3
•
Updated section Global Configuration Mode Commands,
page D-6
•
Updated section Interface Configuration Mode Commands,
page D-10
RPM-XF Performance
The MGX RPM-XF is a next-generation, high performance model of the RPM for the Cisco 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 Cisco 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, one or two high speed uplinks (either OC12 POS or Gigabit Ethernet)
are supported through a backcard placed in the upper backcard slot. The console and aux connections
and two 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 Cisco MGX 8850.
1-2
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 1
Overview of the MGX RPM-XF
RPM-XF Physical Overview
RPM-XF Physical Overview
The MGX RPM-XF-512 module fits in a 32-slot, full-height Cisco MGX 8850 chassis. The RPM-XF
connects to the PXM45 switch module, the MGX-XF-UI or MGX-XF-UI/B, MGX-1OC12POS-IR,
MGX-2OC12POS, MGX-1GE, and MGX-2GE 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 Cisco 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 Cisco 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 ortw o high-speed uplinks through a back card in the upperbackcard slot,and a
console/aux dualfastethernet(FE)back card in the low erbackcard slot.The high speed uplink can be either
an O C12 PO S orG igabitEthernetback card w ith one ortw o ports.
The RPM-XF installs into one slot in the Cisco MGX 8850 chassis and connects to the Cisco MGX 8850
midplane. (See Figure 1-1.) When the RPM-XF is installed (in the front of the Cisco MGX 8850
chassis), its back cards must also be connected to the midplane (from the rear of the Cisco 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 Cisco 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 Cisco MGX 8850 chassis.)
Figure 1-2 shows the rear view of the Cisco 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 or MGX-XF-UI/B management card is always installed in the lower bay
slot directly behind the RPM-XF cards.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
1-3
Chapter 1
Overview of the MGX RPM-XF
RPM-XF Physical Overview
Figure 1-1
RPM-XF Installed in a Cisco MGX 8850 Chassis (Front View)
FAN
1
2
3
ACT
STBY
SM
SM
4
ACT
STBY
5
6
7
8
CONTROL
PORT
ACT
CONTROL
PORT
CB TX
FAIL
FAIL
PORT 1
PORT 1
PORT 2
PORT 2
PORT 2
PORT 3
PORT 3
PORT 3
CR
PORT 4
PORT 4
PORT 4
MJ
MJ
PORT 5
PORT 5
PORT 5
MIN
MIN
PORT 6
PORT 6
PORT 6
DC-A
PORT 7
PORT 7
PORT 7
DC-B
PORT 8
PORT 8
PORT 8
CR
10
CPU OK
CB TX
11
CPU OK
CB TX
12
CPU OK
CB TX
13
ACT
STBY
14
ACT
FAIL
PORT 1
PORT 2
PORT 2
PORT 3
PORT 3
PORT 4
PORT 4
PORT 5
PORT 5
DC-A
PORT 6
PORT 6
DC-B
PORT 7
PORT 7
PORT 8
PORT 8
AXSM-E
AXSM-E
SYSTEM
STATUS
SYSTEM
STATUS
ACO
ACO
HIST
CB RX
CB RX
CB RX
CB RX
LM1 OK
LM1 OK
LM1 OK
LM1 OK
LM2 OK
LM2 OK
LM2 OK
LM2 OK
HIST
AXSM
SYSTEM
STATUS
SYSTEM
STATUS
SYSTEM
STATUS
PORT 9
PORT 9
PORT 9
PORT 9
PORT 9
PORT 10
PORT 10
PORT 10
PORT 10
PORT 10
PORT 11
PORT 11
PORT 11
PORT 11
PORT 11
PORT 12
PORT 12
PORT 12
PORT 12
PORT 12
PORT 13
PORT 13
PORT 13
PORT 13
PORT 13
PORT 14
PORT 14
PORT 14
PORT 14
PORT 14
PORT 15
PORT 15
PORT 15
PORT 15
PORT 15
PORT 16
PORT 16
PORT 16
PORT 16
PORT 16
19
20
21
22
ACT
ACT
STBY
STBY
FAIL
FAIL
1:N RED
1:N RED
BERT
BERT
SRM
4T-E1
SRM
4T-E1
ACO
HIST
AXSM
PXM45
PXM45
SYSTEM
STATUS
SYSTEM
STATUS
RPM-XF
RPM-XF
RPM-XF
RPM-XF
SM
18
16
ENET
AXSM
SM
15
STBY
FAIL
PORT 1
HIST
ACO
17
CPU OK
STBY
FAIL
PORT 1
ENET
SM
9
23
24
25
26
27
28
29
30
ACT
ACT
STBY
STBY
FAIL
FAIL
1:N RED
1:N RED
BERT
BERT
SRM
4T-E1
SRM
4T-E1
31
32
FAN
75538
Power supply
1-4
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 1
Overview of the MGX RPM-XF
RPM-XF Physical Overview
Figure 1-2
RPM-XF Back Cards Installed in Cisco MGX 8850 (Back View)
FAN
16
15
14
13
12
11
MGX-10C 12
POS-IR
MGX-10C 12
POS-IR
LINK
LINK
TX
RX
TX
FAIL
32
31
30
MGX-1GE
RX
TX
TX
8
TX
RX
LINK
TX
FAIL
FAIL
RX
RX
TX
TX
27
26
25
MGX-XF-UI
MGX-XF-UI
MGX-XF-UI
MGX-XF-UI
A
U
X
A
U
X
A
U
X
A
U
X
C
O
N
S
O
L
E
C
O
N
S
O
L
E
C
O
N
S
O
L
E
C
O
N
S
O
L
E
STATUS
L
N
K
L
N
K
L
N
K
A
C
T
A
C
T
A
C
T
ETHERNET 0
ETHERNET 0
C
P
M
P
M
P
L
A
N
L
A
N
1
1
L
A
N
L
A
N
2
2
EXT CLK 1
EXT CLK 1
EXT CLK 2
EXT CLK 2
A
L
A
R
M
A
L
A
R
M
24
L
N
K
A
C
T
3
2
1
22
21
20
19
18
17
PXM-HD
ENABLED
L
N
K
A
C
T
ETHERNET 0
ETHERNET 0
L
N
K
A
C
T
ETHERNET 1
4
STATUS
L
N
K
A
C
T
ETHERNET 1
23
PXM-HD
SIGNAL
L
N
K
5
PXM-UI-S3
C
P
ENABLED
STATUS
6
RX
28
STATUS
7
MGX-1GE
PXM-UI-S3
LINK
FAIL
RX
29
RX
9
10
A
C
T
ETHERNET 1
ETHERNET 1
SIGNAL
RX
RX
P
O
R
T
2
P
O
R
T
2
TX
TX
Power supply
75539
FAN
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 Cisco MGX 8850 Serial Interface
Controllers.
The Cisco 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
1-5
Chapter 1
Overview of the MGX RPM-XF
RPM-XF Physical Overview
RPM-XF Connected to the Cisco MGX 8850 Midplane and to the Back Cards
RPM-XF
high speed back card
RPM-XF Front Card
Routing Engine
- RM7000A
- I/O Assy
PCI
#1
PCI
#2
MGX-XF-UI
management back card
LAN
Aux
ATM
interface
Cellbus to PXM
Cisco MGX 8850
midplane
Console
75868
Figure 1-3
The RPM-XF fits into the Cisco 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 Cisco 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. The following half-height high-speed uplink
back cards, which must be installed in the upper slot, are supported:
•
1-port OC12 POS
•
2-port OC12 POS
•
1-port Gigabit Ethernet
•
2-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:
1-6
•
static route
•
IGRP
•
RIPv1
•
RIPv2
•
OSPF
•
EIGRP
•
IS-IS
•
BGP with multiprotocol extensions
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 1
Overview of the MGX RPM-XF
RPM-XF System Specifications
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 System Specifications
Table 1-2 summarizes the key attributes of the RPM-XF card.
Table 1-2
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-8 for more information
Back cards
MGX-XF-UI or MGX-XF-UI/B management back card with 2 Fast
Ethernet (100BASE-T) ports. The MGX-XF-UI/B back card is slotted to
accommodate the Cisco MGX 8880 RCON module.
(port adapters)
High-speed back cards:
•
MGX-1OC12POS-IR and MGX-20C12POS
•
MGX-1GE and MGX-2GE
Cisco MGX 8850 Cellbus
The Cisco MGX 8850 cellbus in the Cisco 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
1-7
Chapter 1
Overview of the MGX RPM-XF
Cisco MGX 8850 Serial Bus Interface
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.
Cisco MGX 8850 Serial Bus Interface
The ATM connection is a permanent, internal ATM interface that connects directly to the Cisco MGX
8850 midplane. The ATM interface connects to a high speed cross-bar switch through the Cisco 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 Connector
The Cisco 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 LEDs
The 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 the “Reading Front Panel LEDs” section Appendix A, “Maintaining the MGX
RPM-XF.”
1-8
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 1
Overview of the MGX RPM-XF
Cisco IOS Software Compatibility
Figure 1-4
RPM-XF Front Panel
CPU OK
CB TX
CPU OK
CB TX
CB RX
CB RX
LM1 OK
LM2 OK
LM1 OK
LM2 OK
75534
RPM-XF
Cisco IOS Software Compatibility
The RPM-XF is supported in Cisco IOS Release 12.3(11)T4.
For more information about RPM-XF software configuration, refer to the Cisco IOS configuration and
command reference documentation.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
1-9
Chapter 1
Overview of the MGX RPM-XF
Cisco IOS Software Compatibility
1-10
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
C H A P T E R
2
Preparing 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 Cisco 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 Cisco 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
2-1
Chapter 2
Preparing to Install the MGX RPM-XF
Maintaining 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 Cisco MGX 8850 AC and MGX 8850 DC systems within their marked electrical ratings and
product usage instructions.
•
Install the Cisco 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.
•
Cisco 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.
•
Cisco 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 a Cisco MGX
8850 DC-input power entry module.
– Cisco 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.
2-2
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 2
Preparing to Install the MGX RPM-XF
General Site Requirements
Preventing Electrostatic Discharge Damage
Electrostatic 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 Requirements
This 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 Considerations
Check 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 Cisco 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 Cisco MGX 8850 chassis. The RPM-XF, when
installed in the Cisco MGX 8850 chassis, receives –48 volts DC power from the midplane.
The DC power supply of the RPM-XF is part of the Cisco MGX 8850 chassis. The RPM-XF, when
installed in the Cisco MGX 8850 chassis, receives –48 volts DC power from the midplane.
The RPM-XF is installed in the Cisco MGX 8850 chassis. Refer to the Cisco MGX 8850 Routing Switch
Installation Guide. The location of the Cisco 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
2-3
Chapter 2
Preparing to Install the MGX RPM-XF
Installation Checklist
Installation Checklist
The 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 _________________________________________
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-XF-UI or MGX-XF-UI/B 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 or
MGX-XF-UI/B console port
Signal distance limits verified
RPM-XF and MGX-XF-UI or MGX-XF-UI/B properly
installed in corresponding chassis slots.
Startup sequence steps completed
Initial system operation verified
Software image verified
Creating a Site Log
The 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:
•
2-4
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 2
Preparing to Install the MGX RPM-XF
Preparing 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 Network
When setting up your RPM-XF in the Cisco 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 Connection
The Ethernet ports located on the MGX-XF-UI or MGX-XF-UI/B back card support IEEE Ethernet
standard 802.3 and Fast Ethernet standard 802.3u. The back card implementation supports the following
connections:
•
10BASE-T— 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 10BASE-T Ethernet
operates at 10Mbs and can be connected through the RJ-45 connector.
•
100BASE-TX—100BASE-T Ethernet, half and full duplex over Category 5 UTP, Electronics
Industry Association and Telecommunications Industry Association [EIA/TIA]-568-compliant
cable. The 100BASE-T Ethernet operates at 100Mbs and can be connected through the RJ-45
connector.
The cables required to connect the MGX-XF-UI or MGX-XF-UI/B 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 Ports
The MGX-XF-UI and MGX-XF-UI/B include 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
2-5
Chapter 2
Preparing to Install the MGX RPM-XF
Preparing 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 Connection
The MGX-XF-UI and MGX-XF-UI/B include 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
We do not provide console cables in the MGX-RPM-XF-512, MGX-XF-UI, or MGX-XF-UI/B 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 Connections
The 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 or MGX-XF-UI/B is not supported.
Note
We do not provide console cables in the MGX-RPM-XF-512, MGX-XF-UI, or MGX-XF-UI/B 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.”
2-6
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
C H A P T E R
3
Installing the MGX RPM-XF Front and Back Cards
This chapter describes how to install the Cisco MGX Route Processor Module (RPM-XF), the
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 Cisco MGX 8850 Midplane
•
Connecting a Console Terminal or PC to the Console Port
Inspecting the System
Do not unpack the RPM-XF front card and MGX-XF-UI or MGX-XF-UI/B management 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 back card and
are ready to begin the installation, unpack the cards.
The RPM-XF, management backcard, 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 or MGX-XF-UI/B
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,
MGX-XF-UI, or MGX-XF-UI/B 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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
3-1
Chapter 3
Installing the MGX RPM-XF Front and Back Cards
Required Tools and Parts
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).
Required Tools and Parts
Installing the RPM-XF and back cards requires tools and parts that are not provided as standard
equipment. You need the following tools and equipment to install the RPM-XF and back cards in the
Cisco 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 the “Identifying a Rollover Cable” section in Appendix B,
“Cable and Connector Specifications.”
– 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 Console Port” section later in this chapter for
the procedure to connect a console terminal.
Installing and Removing the RPM-XF Cards
The following sections describe how to install and remove the RPM-XF in the Cisco MGX 8850
midplane.
Note
Warning
3-2
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 Cisco MGX 8850
chassis.
Only trained and qualified personnel should install or replace this equipment.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 3
Installing the MGX RPM-XF Front and Back Cards
Installing and Removing the RPM-XF Cards
Warning
Note
Before handling the RPM-XF, attach a wrist strap.
It is not necessary to power OFF the Cisco MGX 8850 chassis. The RPM-XF can be removed and
inserted in the Cisco MGX 8850 chassis while the system is up and running.
Before Installing Front or Back Cards
Before 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.
Backplane Inspection Check Points
Bent pins
•
Bent divider
48456
Figure 3-1
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
3-3
Chapter 3
Installing the MGX RPM-XF Front and Back Cards
Installing and Removing the RPM-XF Cards
Figure 3-2
Damaged Connectors on the Card
48459
Damaged holes
Installing the RPM-XF Front Card
Perform the following steps to install the RPM-XF in the Cisco 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 Card
Double-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
3-4
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 3
Installing the MGX RPM-XF Front and Back Cards
Installing and Removing the RPM-XF Cards
Figure 3-3
Front Card Extractor Latch
Top of card
H8293
Slot
Perform the following steps to remove an RPM-XF front card from the Cisco MGX 8850 chassis.
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 Cisco 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
3-5
Chapter 3
Installing the MGX RPM-XF Front and Back Cards
Installing and Removing Back Cards in the Cisco MGX 8850 Midplane
Figure 3-4
RPM-XF Installed in the Cisco MGX 8850 Chassis—Front View
FAN
1
2
3
ACT
STBY
SM
SM
4
ACT
STBY
5
6
7
8
CONTROL
PORT
ACT
CONTROL
PORT
CB TX
FAIL
FAIL
PORT 1
PORT 1
PORT 2
PORT 2
PORT 2
PORT 3
PORT 3
PORT 3
CR
PORT 4
PORT 4
PORT 4
MJ
MJ
PORT 5
PORT 5
PORT 5
MIN
MIN
PORT 6
PORT 6
PORT 6
DC-A
PORT 7
PORT 7
PORT 7
DC-B
PORT 8
PORT 8
PORT 8
CR
10
CPU OK
CB TX
11
CPU OK
CB TX
12
CPU OK
CB TX
13
ACT
STBY
14
ACT
FAIL
PORT 1
PORT 2
PORT 2
PORT 3
PORT 3
PORT 4
PORT 4
PORT 5
PORT 5
DC-A
PORT 6
PORT 6
DC-B
PORT 7
PORT 7
PORT 8
PORT 8
AXSM-E
AXSM-E
SYSTEM
STATUS
SYSTEM
STATUS
ACO
ACO
HIST
CB RX
CB RX
CB RX
CB RX
LM1 OK
LM1 OK
LM1 OK
LM1 OK
LM2 OK
LM2 OK
LM2 OK
LM2 OK
HIST
AXSM
SYSTEM
STATUS
SYSTEM
STATUS
SYSTEM
STATUS
PORT 9
PORT 9
PORT 9
PORT 9
PORT 9
PORT 10
PORT 10
PORT 10
PORT 10
PORT 10
PORT 11
PORT 11
PORT 11
PORT 11
PORT 11
PORT 12
PORT 12
PORT 12
PORT 12
PORT 12
PORT 13
PORT 13
PORT 13
PORT 13
PORT 13
PORT 14
PORT 14
PORT 14
PORT 14
PORT 14
PORT 15
PORT 15
PORT 15
PORT 15
PORT 15
PORT 16
PORT 16
PORT 16
PORT 16
PORT 16
19
20
21
22
ACT
ACT
STBY
STBY
FAIL
FAIL
1:N RED
1:N RED
BERT
BERT
SRM
4T-E1
SRM
4T-E1
ACO
HIST
AXSM
PXM45
PXM45
SYSTEM
STATUS
SYSTEM
STATUS
RPM-XF
RPM-XF
RPM-XF
RPM-XF
SM
18
16
ENET
AXSM
SM
15
STBY
FAIL
PORT 1
HIST
ACO
17
CPU OK
STBY
FAIL
PORT 1
ENET
SM
9
23
24
25
26
27
28
29
30
ACT
ACT
STBY
STBY
FAIL
FAIL
1:N RED
1:N RED
BERT
BERT
SRM
4T-E1
SRM
4T-E1
31
32
FAN
75538
Power supply
Installing and Removing Back Cards in the Cisco MGX 8850
Midplane
The following sections describe how to install and remove the management and high-speed uplink back
cards from the Cisco MGX 8850 midplane.
3-6
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 3
Installing the MGX RPM-XF Front and Back Cards
Installing and Removing Back Cards in the Cisco MGX 8850 Midplane
Installing the Back Cards
Use the following procedure to install the management and high-speed uplink back cards in the Cisco
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 or MGX-XF-UI/B 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
Step 3
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.
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 Cisco 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 Cards
Use the following procedure to remove the back cards from the Cisco 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
3-7
Chapter 3
Installing the MGX RPM-XF Front and Back Cards
Installing and Removing Back Cards in the Cisco MGX 8850 Midplane
Step 4
Gently pull the card out of the card cage.
Figure 3-5
RPM-XF Back Cards Connected to a Cisco MGX 8850—Back View
FAN
16
15
14
13
12
11
MGX-10C 12
POS-IR
MGX-10C 12
POS-IR
LINK
LINK
TX
RX
TX
FAIL
32
31
30
MGX-1GE
RX
TX
TX
8
TX
RX
LINK
TX
FAIL
FAIL
RX
RX
TX
TX
27
26
25
MGX-XF-UI
MGX-XF-UI
MGX-XF-UI
MGX-XF-UI
A
U
X
A
U
X
A
U
X
A
U
X
C
O
N
S
O
L
E
C
O
N
S
O
L
E
C
O
N
S
O
L
E
C
O
N
S
O
L
E
STATUS
L
N
K
L
N
K
L
N
K
A
C
T
A
C
T
A
C
T
ETHERNET 0
ETHERNET 0
C
P
M
P
M
P
L
A
N
L
A
N
1
1
L
A
N
L
A
N
2
2
EXT CLK 1
EXT CLK 1
EXT CLK 2
EXT CLK 2
A
L
A
R
M
A
L
A
R
M
24
L
N
K
A
C
T
3
2
1
22
21
20
19
18
17
PXM-HD
ENABLED
L
N
K
A
C
T
ETHERNET 0
ETHERNET 0
L
N
K
A
C
T
ETHERNET 1
4
STATUS
L
N
K
A
C
T
ETHERNET 1
23
PXM-HD
SIGNAL
L
N
K
5
PXM-UI-S3
C
P
ENABLED
STATUS
6
RX
28
STATUS
7
MGX-1GE
PXM-UI-S3
LINK
FAIL
RX
29
RX
9
10
A
C
T
ETHERNET 1
ETHERNET 1
SIGNAL
RX
RX
P
O
R
T
2
P
O
R
T
2
TX
TX
Power supply
3-8
75539
FAN
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 3
Installing the MGX RPM-XF Front and Back Cards
Installing and Removing Back Cards in the Cisco MGX 8850 Midplane
Installing SFP Modules
The following high-speed back cards use SFP modules:
•
MGX-1GE
•
MGX-2GE
•
MGX-2OC12POS
Follow these steps to install an SFP module in these cards:
Warning
Step 1
Because invisible laser radiation may be emitted from the aperture of the port when no fiber cable is
connected, avoid exposure to laser radiation and do not stare into open apertures.
Slide the SFP into the slot until it locks into position (see Figure 3-6).
Installing an SFP Module
94126
Figure 3-6
Caution
Step 2
Do not remove the optical port plugs from the SFP until you are ready to connect cabling.
Connect the network cable to the SFP module.
Removing SFP Modules
Follow these steps to remove an SFP module from the high-speed back cards:
Step 1
Disconnect all cables from the SFP.
Warning
Because invisible laser radiation may be emitted from the aperture of the port when no fiber cable is
connected, avoid exposure to laser radiation and do not stare into open apertures.
Caution
The latching mechanism used on many SFPs locks the SFP into place when cables are connected. Do not
pull on the cabling in an attempt to remove the SFP.
Step 2
Disconnect the SFP latch. See Figure 3-7.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
3-9
Chapter 3
Installing the MGX RPM-XF Front and Back Cards
Connecting a Console Terminal or PC to the Console Port
Note
SFP modules use various latch designs to secure the module in the SFP port. Latch designs are not linked
to SFP model or technology type. For information on the SFP technology type and model, see the label
on the side of the SFP.
Figure 3-7
Disconnecting SFP Latch Mechanisms
1
2
3
4
A
117722
B
Tip
Step 3
1
Sliding latch
3
Bale-clasp latch
2
Swing and slide latch
4
Plastic collar latch
Use a pen, screwdriver, or other small straight tool to gently release a bale-clasp handle if you cannot
reach it with your fingers.
Grasp the SFP on both sides and remove it.
Tip
Caution
If the SFP transceiver appears to be stuck, with the SFP latch in the fully unlocked position, push
it back into the socket to release the latch, then pull out to remove it.
DO NOT use a screwdriver to pry the SFP transceiver loose! This will damage the socket on
the MGX-XF Back Card.
Connecting a Console Terminal or PC to the Console Port
The MGX-XF-UI and MGX-XF-UI/B management back cards include 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.
3-10
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 3
Installing the MGX RPM-XF Front and Back Cards
Connecting a Console Terminal or PC to the Console Port
Step 1
Connect the terminal (see Figure 3-8) 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.
For cable pinouts, see Appendix B, “Cable and Connector Specifications.”
Step 2
Note
Configure your terminal or PC terminal emulation software for 9600 baud, 8 data bits, no parity, and
1 stop bit.
The default parameters for the console port are 9600 baud, 8 data bits, no parity and 1 stop bit.
Figure 3-8
Connecting a Console Terminal to the MGX-XF-UI Console Port
FAN
16
15
14
12
13
MGX-10C
POS-IR
LINK
TX
12
PXM-U
E
MGX-1G
E
MGX-1G
MGX-10C
POS-IR
LINK
TX
12
LINK
LINK
TX
7
8
9
10
11
TX
PXM-U
6
5
4
3
2
1
I-S3
I-S3
C
P
RX
C
P
RX
FAIL
M
P
RX
FAIL
M
P
RX
FAIL
FAIL
L
A
N
RX
L
A
N
TX
RX
RX
TX
RX
1
1
L
A
N
TX
L
A
N
TX
2
2
EXT CLK
EXT CLK
EXT CLK
EXT CLK
A
L
A
R
M
32
31
30
27
28
29
23
24
25
2
2
A
L
A
R
M
26
1
1
22
21
20
19
18
17
PXM-HD
PXM-HD
F-UI
MGX-X
F-UI
MGX-X
ENABLE
ENABLE
D
D
F-UI
MGX-X
F-UI
MGX-X
A
U
X
A
U
X
A
U
X
A
U
X
C
O
N
S
O
L
E
C
O
N
S
O
L
E
C
O
N
S
O
L
E
C
O
N
S
O
L
E
STATU
STATU
STATU
STATU
PC
S
S
S
S
L
N
K
L
N
K
L
N
K
L
N
K
A
C
T
ETHE
ETHE
ETHE
ETHE
RNET
A
C
T
A
C
T
A
C
T
RNET
RNET
0
SIGN
0
SIGN
AL
P
O
R
T
2
RX
A
C
T
A
C
T
A
C
T
RNET
RNET
TX
TX
ETHE
ETHE
ETHE
RNET
P
O
R
T
2
L
N
K
L
N
K
L
N
K
A
C
T
AL
RX
0
L
N
K
ETHE
RNET
0
RNET
1
1
1
1
FAN
OK
RJ-45-to-DB-25 adapter
Note
75649
RJ-45 rollover cable
I/O
card
AUX
SER 0
LAN
ETH
ply
r sup
Powe
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
3-11
Chapter 3
Installing the MGX RPM-XF Front and Back Cards
Connecting a Console Terminal or PC to the Console Port
3-12
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
C H A P T E R
4
Installing and Configuring the MGX-XF-UI and
MGX-XF-UI/B Management Back Cards
This chapter describes how to install and configure the MGX-XF-UI and MGX-XF-UI/B management
back cards that are used in conjunction with and to configure the Cisco Route Processor Module
(RPM-XF). This chapter includes the following sections:
•
Overview and Features
•
Fast Ethernet Overview
•
Installation Guidelines
•
Software Configuration
•
Troubleshooting the Management Back Card
Overview and Features
The RPM-XF supports the following management backcards:
•
MGX-XF-UI
•
MGX-XF-UI/B
Both management back cards provide 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
•
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
•
Connecting to the auxiliary port through a modem is not supported.
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 10BASE-T or 100BASE-T network
management LAN.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
4-1
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Overview and Features
MGX-XF-UI Management Back Card
The MGX-XF-UI is a management back card (Figure 4-1) that provides management capabilities for the
RPM-XF through a console connection, an auxiliary connection, and two fast ethernet (FE) ports.
Figure 4-1
MGX-XF-UI and MGX-XF-UI/B Faceplate
MGX-XF-UI/B
A
U
X
1
C
O
N
S
O
L
E
2
3
STATUS
L
N
K
A
C
T
ETHERNET 0
4
L
N
K
A
C
T
122078
ETHERNET 1
1
2
4-2
3
AUX—An RJ-45 receptacle that provides
connection to an auxiliary device that is used
as an external terminal for local
administrative access.
CONSOLE—An RJ-45 receptacle that
provides a serial connection used for an
external terminal for local administrative
access.
4
STATUS LED
•
Green—The back card is active.
•
Off—The back card is not detected or a
major failure has disabled the back card.
ETHERNET 0 AND ETHERNET 1—Two
fast ethernet (FE) RJ-45 receptacles that
comply with Ethernet standards and that are
used to connect the RPM-XF to a
10/100BASE-T network management LAN.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Fast Ethernet Overview
MGX-XF-UI/B Management Back Card
The MGX-XF-UI/B is a management back card that provides management capabilities for the RPM-XF
through a console connection, an auxiliary connection, and two fast ethernet (FE) ports.
The MGX-XF-UI/B faceplate is the same as the MGX-XF-UI (Figure 4-1). The board silhouette
(Figure 4-2) is notched to accommodate the redundancy connector (RCON) of the Cisco MGX 8880
Media Gateway, directly behind the RPM-XF card.
Figure 4-2
MGX-XF-UI/B Card—Side View
1
F-UI/B
MGX-X
A
U
X
C
O
N
S
O
L
E
US
STAT
L
N
K
A
C
T
0
RNET
ETHE
L
N
K
1
RNET
ETHE
122076
A
C
T
1
Notched card, to fit into the Cisco MGX 8880
RCON
Fast Ethernet Overview
Fast 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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
4-3
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Fast Ethernet Overview
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, 100BASE-T specifies a 100-Mbps, baseband LAN with maximum network segments.
IEEE 802.3u 100BASE-T Fast Ethernet Specifications
Each Fast Ethernet port on the MGX-XF-UI back card has an RJ-45 connector to attach to Category 5
UTP for 100BASE-TX. Figure 4-1 shows the Fast Ethernet MGX-RJ45-FE back card. The following
lists the cabling specifications for 100-Mbps Fast Ethernet transmission over UTP cables.
Parameter
RJ-45
Cable specification
Category 5 1 UTP2, 22 to 24 AWG
Maximum cable length
—
Maximum segment length
328 ft (100 m) for 100BASE-TX
Maximum network length
656 ft (200 m) (with 1 repeater)
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.
The following table summarizes IEEE 802.3u 100BASE-T physical characteristics.
Parameter
100BASE-TX
Data rate (Mbps)
100
Signaling method
Baseband
Maximum segment length
100 m between DTE1 and repeaters
Media
RJ-45
Topology
Star/Hub
1. DTE = data terminal equipment.
4-4
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Installation Guidelines
Installation Guidelines
This section contains guidelines for the following procedures:
•
New installation
•
Replacement installation
The 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 Guidelines
For information on installing the back cards, see the “Installing and Removing Back Cards in the Cisco
MGX 8850 Midplane” in Chapter 3, “Installing the MGX RPM-XF Front and Back Cards.”
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 Guidelines
For information on installing the back cards, see the “Installing and Removing Back Cards in the Cisco
MGX 8850 Midplane” in Chapter 3, “Installing the MGX RPM-XF Front and Back Cards.”
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).
Software Configuration
After 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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
4-5
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Software Configuration
Configuring the Console and Auxiliary Ports
This 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
The following table 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.
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
Console and Auxiliary Port Syntax
To specify a serial port in a configuration command, use the syntax in the following table to identify the
serial interfaces on the management back card.
Type of Interface
Port
Console port
0
Auxiliary port
0
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
4-6
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Software Configuration
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
Ctrl-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.
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,
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
4-7
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Software Configuration
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
Ctrl-Z to exit 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 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.
This section covers the following topics:
•
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 0
Router(config-line)# speed 9600
4-8
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Software Configuration
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 0
Router(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 0
Router(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 0
Router(config-line)# parity none
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
4-9
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Software Configuration
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 Ports
This 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
•
Checking System Status
Fast Ethernet Default Values
The following table 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.
Command Name
Default Setting
Command Syntax
Remote Side
Setting
duplex
auto
duplex [auto | half | full]
Same.
speed
auto
speed [10 | 100 | auto]
Same.
keepalive*
10 second keepalive
[no] keepalive period
Same.
mtu *
1500
mtu size
Same.
length*
24
length size
—
width*
80
width size
—
1
1. mtu=maximum transmission unit
4-10
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Software Configuration
Fast Ethernet Port Syntax
To specify an interface number in a configuration command, use the syntax in the following table to
identify fast ethernet interfaces on the management back card.
Type of Interface
Bay (always 2)
Port
Fast Ethernet
2/
[0 | 1 ]
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
Step 5
Add any other configuration subcommands required.
Step 6
Enter the no shutdown command to enable the interface. For example,
Router(config-if)# no shutdown
Step 7
When you have included all of the configuration subcommands to complete the configuration, press
Ctrl-Z to exit 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 the configuration, check it using show interface FastEthernet bay/port.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
4-11
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Software Configuration
Fast Ethernet Port Configuration Commands
The following sections present some of the commands that you can use to customize your fast ethernet
port configuration.
This section covers the following topics:
•
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/0
Router(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/0
Router(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 auto
end
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
4-12
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Software Configuration
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 ms
Router#
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.
Checking 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/0
FastEthernet2/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/0
Interface FastEthernet2/0
Hardware is GT96100A FE
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
4-13
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Software Configuration
IDB Ptr = 0x41F27050, Instance Ptr = 0x42CA4B28
GT96100A register pointer = 0x15000000
FE register pointer = 0x15088800
PHY 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:
Register 0x08:
Register 0x10:
Register 0x18:
1000
0000
0084
0000
782D
0000
4780
0000
0013
0000
0000
00C8
78E2
0000
00F4
0000
01E1
0000
2040
0000
41E1
0000
0000
0000
0007
0000
0000
0000
2001
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
4-14
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Software Configuration
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
Malloc Rx ring 2 ptr = 0x1F3445C0, Malloc Rx ring 3 ptr
Shadow Rx ring 0 ptr = 0x41F2833C, Shadow Rx ring 1 ptr
Shadow Rx ring 2 ptr = 0x42CA5414, Shadow Rx ring 3 ptr
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
=
=
=
=
0x1F344180
0x1F344A00
0x42CA52E8
0x42CA5540
MIB Counters:
Filtered packets = 0, Number of Throttles = 0
Rx
Rx
Rx
Rx
Rx
framing errors = 0, Rx overflow errors = 0
buffer errors = 0, Rx end of packet errors = 0
soft overflow errors ring 0 = 0 Rx soft overflow errors ring 1 = 0
soft overflow errors ring 2 = 0 Rx soft overflow errors ring 3 = 0
miss count = 0
Tx
Tx
Tx
Tx
Tx
single collision errors = 0, Tx multiple collision errors = 0
end of packet errors = 0, Tx deferred errors = 0
underrun errors = 0, Tx late collision errors = 0
carrier loss errors = 0, Tx excessive collision errors = 0
buffer errors = 0, Tx fatal errors = 0
Spurious SMI Interrupts = 0
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
4-15
Chapter 4
Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards
Troubleshooting the Management Back Card
Troubleshooting the Management Back Card
Refer to the following table for descriptions of the LEDs on the management back card. Follow the
instructions in Table 4-1 on the next page to troubleshoot the installation.
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-1
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.
Configuration incorrect.
Check the configuration to make sure the baud
rate and other settings are correct.
Bad cable.
Replace the cable.
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.
Bad back card.
Replace the back card.
Bad front card.
Replace the front card.
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.
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.
Bad back card.
Replace the back card.
Bad front card.
Replace the front card.
The console or
auxiliary port do not
work.
The fast ethernet
port(s) does not work.
4-16
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
C H A P T E R
5
Installing 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 Back Card
MGX-1OC12POS-IR Overview and Features
The 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).
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
5-1
Chapter 5
Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards
MGX-1OC12POS-IR Overview and Features
Figure 5-1
MGX-1OC12POS-IR Back Card
MGX-1OC 12
POS-IR
1
LINK
TX
RX
2
3
FAIL
RX
4
80748
TX
Table 5-1
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
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.
5-2
Fiber Type
Wavelength (nm)
Core Size (microns)
Cable Distance
Single-mode fiber
1300
8 to 10
49,213 ft (15 km)
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 5
Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards
MGX-2OC12POS 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.
MGX-2OC12POS Overview and Features
The 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).
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
5-3
Chapter 5
Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards
MGX-2OC12POS Overview and Features
Figure 5-2
MGX-2OC12POS Back Card
MGX-2
OC12POS
1
ENBL
2
ST
6
1
3
4
SD
ST
7
2
5
122605
SD
1
3
5
ENBL LED
2
Port 0 status LED
•
Off—The back card is functioning.
•
Green—The link is up.
•
Yellow—The back card has failed
•
Yellow—The link is down.
Port 0 signal detect LED
4
Port 1 status LED
•
Green—A signal is present.
•
Green—The link is up.
•
Green (flashing)—Loss of signal
•
Yellow—The link is down.
Port 1 signal detect LED
•
6
Port 0 SFP receptacle
Green—A signal is present.
Green (flashing)—Loss of signal
7
Port 1 SFP receptacle
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 SFP
module (see Table 5-2).
5-4
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 5
Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards
MGX-2OC12POS Overview and Features
Table 5-2
SFP Modules and Cables
SFP Module
9/125 um
Single-mode
1310 nm Cable
SMFIR-622-SFP
15 km
SMFLR-622-SFP
40 km
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 Cisco IOS boot time
•
Initializing and configuring the GE back card
•
Downloading the POS back card 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 back card port and card status LEDs
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
5-5
Chapter 5
Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards
Installation Guidelines
Installation Guidelines
This section contains guidelines for the following procedures:
•
New installation
•
Replacement installation
The 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 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 Guidelines
For 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 Guidelines
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-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 Configuration
After the MGX-1OC12POS-IR or MGX-2OC12POS back card is successfully installed, you can
configure the card for network use.
Note
5-6
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 5
Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards
Software Configuration
This section covers the following topics:
•
Back Card Default Values
•
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
•
Checking System Status
Back Card Default Values
This section 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 following 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.
Command Name
Default
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
4470
mtu size
Same.
pos framing
SONET
pos framing [sonet | sdh]
Same.
[no] pos scramble-atm
Same.
pos flag [c2 | j0 | s1s0] value
Same.
pos scramble-atm No scrambling
2
pos flag (
c2—0xcf
j0—0x01
s1s0—0x00
1. mtu=maximum transmission unit
2. SONET overhead
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
5-7
Chapter 5
Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards
Software Configuration
MGX-1OC12POS-IR Back Card Syntax
To specify an interface number in a configuration command, use the syntax in Table 5-3 to identify
interfaces on the MGX-1OC12POS-IR back card.
Table 5-3
MGX-1OC12POS-IR Interface Syntax
Type of Interface Bay/ (always 1)
Port
POS interface
0
1/
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 Syntax
To specify an interface number in a configuration command, use the syntax in Table 5-4 to identify
interfaces on the MGX-2OC12POS back card.
Table 5-4
MGX-2OC12POS Interface Syntax
Type of Interface Bay/ (always 1)
Port
POS interface
0 or 1
1/
The following example shows the syntax for configuring an MGX-2OC12POS back card.
Router(config)# interface pos 1/0
Router(config)# interface pos 1/1
Configuring the Interface
After 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.
Router(config-if)# ip address 192.168.255.255 255.255.255.0
Step 3
Specify either HDLC or PPP encapsulation. For example,
Router(config-if)# encapsulation hdlc
5-8
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 5
Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards
Software Configuration
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 the “Back Card Default Values” section on page 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.
Router(config-if)# no shutdown
Step 7
When you have included all of the configuration subcommands to complete the configuration, press
Ctrl-Z to exit 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 stored.
After you complete your configuration, check it by entering the show interface pos <bay/port>
command.
Customizing the MGX-1OC12POS-IR or MGX-2OC12POS
The following sections present some of the commands that you can use to customize your
MGX-1OC12POS-IR or MGX-2OC12POS back card configuration.
This section covers the following topics:
•
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]
Parameter
Description
internal
Specifies that the internal clock source is used.
line
Specifies that the network clock source is used.
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/0
Router(config-if)# clock source line
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
5-9
Chapter 5
Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards
Software Configuration
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.
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/0
Router(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]
Parameter
Description
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
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/0
Router(config-if)# pos flag c2 0xCF
5-10
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 5
Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards
Software Configuration
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/0
Router(config-if)# pos scramble-atm
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]
Parameter
Description
line
Loops any inbound traffic received at the MGX-1OC12POS-IR or
MGX-2OC12POS back card’s network interface back into the
network.
Note
internal
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.
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.
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/0
Router(config-if)# loopback line
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
5-11
Chapter 5
Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards
Software Configuration
Example Configuration
The 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/0
ip address 10.1.2.4 255.0.0.0
clock source line
no shutdown
no keepalive
no cdp enable
crc 32
Router 2:
interface pos 3/0
ip address 10.1.2.3 255.0.0.0
clock source internal
no shutdown
no keepalive
no cdp enable
no ip mroute-cache
crc 32
Checking System Status
Each 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/0
POS1/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
5-12
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 5
Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards
Troubleshooting the Back Card
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/0
SECTION
LOF =
LINE
AIS =
PATH
AIS =
LOP =
0
LOS = 0
BIP(B1) = 0
0
RDI = 0
FEBE = 0
BIP(B2) = 0
0
0
RDI = 0
NEWPTR = 0
FEBE = 0
PSE = 0
BIP(B3) = 0
NSE = 0
Active Defects: None
Active Alarms: None
Alarm reporting enabled for: SF SD SLOS SLOF B1-TCA LAIS LRDI B2-TCA PAIS PLOP PRDI PUNEQ
B3-TCA
Framing: SONET
OVERHEAD BYTES
S1/S0 = 0, C2 = CF
CLOCK RECOVERY
RDOOL = 0
State: RDOOL_state = False
PATH 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:
TCA thresholds:
Clock source:
SF = 10e-3
B1 = 10e-6
SD = 10e-6
B2 = 10e-6
B3 = 10e-6
internal
Troubleshooting the Back Card
The following table describes the LEDs on the MGX-1OC12POS-IR or MGX-2OC12POS back card.
Follow the instructions in Table 5-5 to troubleshoot the installation.
LED
Status
Description
LINK
Green
Carrier detected.
Off
Carrier not detected.
Green
Transmitting traffic.
Off
Not transmitting traffic.
Green
Receiving traffic.
Off
Not receiving traffic.
Yellow
Major failure has disabled the back card.
Off
Back card is operating properly
TX (transmit)
RX (receive)
FAIL
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
5-13
Chapter 5
Installing and Configuring the MGX-1OC12POS and the MGX-2OC12POS Back Cards
Troubleshooting the Back Card
Table 5-5
Symptom
MGX-1OC12POS-IR or MGX-2OC12POS Installation Troubleshooting
Possible Cause
The back card fail LED The back card is not
does not light during
properly seated.
the power-on self-test. Bad back card slot or
midplane connector.
Be sure the ejector levers are fully closed and that
the captive screws have been tightened.
Back card initialization Bad back card slot or
fails.
midplane connector.
Remove the back cards (upper and lower slots) and
the front card and install them into another chassis
slot.
Remove the back cards (upper and lower slots) and
the front card and install them into another chassis
slot.
Bad back card.
Replace the back card.
Bad front card.
Replace the front card.
The interface does not Configuration
come up or constantly mismatched.
comes up and then goes
down.
Cables connected
incorrectly.
Bad cables.
5-14
Corrective Action
Check the configuration on both sides. (Refer to
the “Software Configuration” section on page 5-6
for more information.)
Check the cabling on both sides. Ensure the
receive is connected to the transmit on the remote
end and vice versa.
Replace the cables. Ensure your cabling meets the
specifications in the “MGX-1OC12POS-IR
Overview and Features” section on page 5-1 or the
“MGX-2OC12POS Overview and Features”
section on page 5-3.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
C H A P T E R
6
Installing 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
•
MGX-2GE Features and Specifications
•
SFP Specifications
•
Installation Guidelines
•
Software Configuration Guidelines
•
System Status Check
•
Installation Troubleshooting
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
6-1
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
MGX-1GE Features and Specifications
MGX-1GE Features and Specifications
The 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
MGX-1GE
1
LINK
TX
RX
2
3
FAIL
RX
4
80747
TX
Table 6-1
Cisco MGX 1GE 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
RJ-45 Ethernet cable connectors
The MGX-1GE back card provides an IEEE 802.3z compliant Gigabit Ethernet interface that runs at
1 Gbps in full duplex mode.
6-2
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
MGX-2GE Features and Specifications
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, T), which you can change or upgrade
at any time (see the “SFP Specifications” section on page 6-5).
MGX-2GE Features and Specifications
The dual-port MGX-2GE back card provides a gigabit ethernet trunk uplink to devices (see Figure 6-1).
Figure 6-2
MGX-2GE Back Card
MGX-2GE
1
ENBL
2
ST
6
1
3
4
SD
ST
7
2
5
122606
SD
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
6-3
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
MGX-2GE Features and Specifications
1
3
5
ENBL LED
2
Port 0 status LED
•
Off—The back card is functioning.
•
Green—The link is up.
•
Yellow—The back card has failed
•
Yellow—The link is down.
Port 0 signal detect LED
4
Port 1 status LED
•
Green—A signal is present.
•
Green—The link is up.
•
Green (flashing)—Loss of signal
•
Yellow—The link is down.
Port 1 signal detect LED
•
6
Port 0 SFP receptacle
Green—A signal is present.
Green (flashing)—Loss of signal
7
Port 1 SFP receptacle
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:
6-4
•
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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
SFP Specifications
SFP Specifications
The following table lists the SFPs and their respective cable types and lengths for the MGX-1GE and
MGX-2GE back cards. All SFP modules are hot swappable.
SFP
Description
GLC-SX-MM 1000Base SX
62.5/125 um
Multimode
850 nmCable
50/125 um
Multimode
850 nmCable
62.5/125 um
50/125 um
9/125 um
Category 5
Multimode
Multimode
Singlemode
Cable
1310 nmCable 1310 nm Cable 1310 nm Cable
220 M at
500 M at
—
160 MHz-km 400 MHz-km
—
—
—
275 M at
550 M at
200 MHz-km 500 MHz-km
GLC-LH-SM
1000Base LH/LX —
—
550 M at
550 M at
500 MHz-km 400 MHz-km
10 km
—
GLC-ZX-SM
1000Base ZX
—
—
—
—
70 km
—
GLC-T
1000BASE-T
(Copper)
—
—
—
—
—
100M
Installation Guidelines
This section contains guidelines for the following procedures:
•
First Time Installation
•
Replacement Installation
The MGX-1GE and 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.
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.
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 or MGX-2GE back card hardware for the first time, you must configure
it entering the configure command. For information about configuring the MGX-1GE or MGX-2GE
back card, see the “Software Configuration Guidelines” section.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
6-5
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
Software Configuration Guidelines
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 or 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-1GE or MGX-2GE back card configuration (those configured as Up).
Software Configuration Guidelines
After the MGX-1GE or MGX-2GE back card is successfully installed, you can configure the card for
network use.
Note
You do not need to configure the MGX-1GE or 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.
This section covers the following topics:
•
Back Card Default Values
•
Back Card Syntax
•
Interface Configuration
•
Customization
•
Example Configuration
Back Card Default Values
This section lists default values for the MGX-1GE or 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.
The following 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.
Command Name
Default
Setting
Command Syntax
Remote Side Setting
bandwidth*
1000000
bandwidth kilobits
Same.
keepalive*
10 second
keepalive
[no] keepalive period
Same.
mtu1*
1500
mtu size
Same.
negotiation auto
[enabled]
[no] negotiation auto
Same.
1. mtu=(maximum transmission unit)
6-6
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
Software Configuration Guidelines
Back Card Syntax
To specify an interface number in a configuration command, use the syntax in Table 6-2 to identify
interfaces on the MGX-1GE or MGX-2GE back card.
Table 6-2
MGX-1GE or MGX-2GE Interface Syntax
Type of Interface
Bay
Ports
Subinterface (optional)
GE interface
1/
0 (MGX-1GE)
1–1000
0 or 1 (MGX-2GE)
The following example shows the syntax for configuring the Gigabit Ethernet interface on the
MGX-1GE or MGX-2GE back card:
Router(config)# interface gigabitethernet 1/0
Router(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 or MGX-2GE back card:
Router(config)# interface gigabitethernet 1/0.2
Router(config-subif)#
Interface Configuration
After you verify that the MGX-1GE or 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:
Router(config-if)# ip address 192.168.255.255 255.255.255.0
Step 3
If necessary, modify the MGX-1GE or 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 the “Back Card Default Values” section on page 6-6.
Step 4
Add any other configuration subcommands required for the enabling of routing protocols and adjust the
interface characteristics.
Step 5
Enter the no shutdown command to enable the interface.
Router(config-if)# no shutdown
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
6-7
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
Software Configuration Guidelines
Step 6
When you have included all of the configuration subcommands to complete the configuration, press
Ctrl-Z to exit configuration mode.
Step 7
Write the new configuration to memory.
Router# copy running-config startup-config
The system displays an OK message when the configuration is stored.
After you have completed your configuration, you can check it using the show interface
gigabitethernet <bay/port>.
Customization
The following sections present some of the commands that you can use to customize your MGX-1GE or
MGX-2GE back card configuration.
This section covers the following topics:
•
Auto Negotiation
•
Loopback Testing
•
802.1q VLAN Encapsulation
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/0
Router(config-if)# negotiation auto
6-8
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
Software Configuration Guidelines
Loopback Testing
To enable loopback testing of data transmitted from the front card to the MGX-1GE or MGX-2GE back
card and back, use the loopback command in interface configuration mode.
loopback [ mac | driver ]
[no] loopback [ mac | driver ]
Parameter
driver or external
mac or internal1
Description
1
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.
Loops any outbound traffic received at the MGX-1GE or MGX-2GE back
card’s network interface back into the front card at the MAC controller.
1. Depending on software release version.
Use the no form of the command to stop the loopback test.
In the following example, a loopback is set for the MGX-1GE or MGX-2GE back card:
Router(config)# interface gigabitethernet 1/0
Router(config-if)# loopback mac
Note
Loopback tests disrupt user traffic on production networks
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.2
Router(config-subif)#encapsulation dot1q 2
Router(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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
6-9
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
System Status Check
Example Configuration
The following is an example of configuration file commands for a Cisco RPM-XF with an MGX-1GE
or 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/0
ip address 10.1.2.4 255.0.0.0
no shutdown
no keepalive
no cdp enable
Router 2:
interface gigabitethernet 3/0
ip address 10.1.2.3 255.0.0.0
no shutdown
no keepalive
no cdp enable
no ip mroute-cache
System Status Check
Each 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/0
GigabitEthernet1/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
6-10
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
System Status Check
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/0
Interface GigabitEthernet1/0(idb 0x43B978A0)
Hardware is Gigabit Ethernet MAC Controller, Slot Index 1
Network Connection Mode is auto
negotiate 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
Card Interrupt Mask
Card ASIC Reset
Card Discrete Input
Card Discrete Output
Card Local Bus Timeout
Card Local Bus Timeout Address
Card PCI SERR Address
Card PCI PERR Address
Card PCI Bus Idle Stats
Card PCI Bus Transfer Stats
Card Wrap Test
Card Debug Header Control
Barium Registers
ID
Configuration
Reset PCI Bus A
Reset PCI Bus B
Reset PCI Bus C
PCI Bus A Status
PCI Bus B Status
PCI Bus C Status
Global IronBus Cfg1
Global IronBus Cfg2
Global IronBus Sts1
Global IronBus Sts2
DMA Reset
Interrupt Status
Interrupt Mask
Iron Bus 0 Status 1
Iron Bus 0 Status 2
Iron Bus 0 Status 3
Iron Bus 1 Status 1
Iron Bus 1 Status 2
Iron Bus 1 Status 3
TIB0 DMA Desc Base
TIB0 Buffer Size
TIB0 DMA Status
TIB0 DMA Control
00000000
00000000
00000000
01000010
000000B1
0000FFFF
00000000
00000000
00000000
FB52A437
0703854C
00000000
00000000
00136049
00000008
00008280
00000280
00000280
540070A0
054C6086
0000F11C
0000F11C
00000000
00004000
4000801F
00000000
00000000
00000000
0FFFFF0F
0000FFFF
000CFFFF
00000000
00000000
00000000
00000400
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
6-11
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
System Status Check
TIB0
TIB0
FIB0
FIB0
FIB0
FIB0
FIB0
FIB0
TIB1
TIB1
TIB1
TIB1
TIB1
TIB1
FIB1
FIB1
FIB1
FIB1
FIB1
FIB1
TIB2
TIB2
TIB2
TIB2
TIB2
TIB2
FIB2
FIB2
FIB2
FIB2
FIB2
FIB2
6-12
DMA Desc Word0
DMA Desc Word1
DMA Desc Base
Buffer Size
DMA Status
DMA Control
DMA Desc Word0
DMA Desc Word1
DMA Desc Base
Buffer Size
DMA Status
DMA Control
DMA Desc Word0
DMA Desc Word1
DMA Desc Base
Buffer Size
DMA Status
DMA Control
DMA Desc Word0
DMA Desc Word1
DMA Desc Base
Buffer Size
DMA Status
DMA Control
DMA Desc Word0
DMA Desc Word1
DMA Desc Base
Buffer Size
DMA Status
DMA Control
DMA Desc Word0
DMA Desc Word1
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000400
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
TIB FPGA Registers
Config
InterruptStatus
InterruptMask
Type/Version
SdramWritePtr0
SdramWritePtr1
SdramWritePtr2
SdramReadPtr0
SdramReadPtr1
SdramReadPtr2
GigMacCrcErrors
GigMacParityErrors
OutSyncErrors
SdramParityErrors
SdramAddr0
SdramAddr1
SdramAddr2
BufferSize0
BufferSize1
BufferSize2
SdramSopWritePtr0
SdramSopWritePtr1
SdramSopWritePtr2
GigEConfig
Address filtering
CAMControlStatus
CAMWriteTrigger
CAMReadTrigger
CAMReg2
CAMReg1
00
00
00
8D
10
00
00
00
00
00
0
0
0
0
00
00
00
93
03
00
00
00
00
01
enabled
F5
F5
F5
FFFFFFFF
FFFF0000
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
System Status Check
CAMReg0
UnicastFrames
MulticastFrames
Bytes
Aborts
WaterMarkLevel
03340000
0
0
0
0
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 parity
FlowControl
00
Control frame detected by DA & TYPE filed match
TrunkConfig
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 datapath
MatchLogicControl 00
SuppLogicControl
10
Drop <= 63 bytes enabled
TypeUserConfig
00
User Field = 00
Type Field = 00
CTRLFieldConfig
02
Don't learn
RFRHPtimeLo
A2
RFRHPTimeHi
05
ONEQTypeLo
00
ONEQTypeHi
00
ColorLo
00
ColorHi
00
IndexByte0
00
IndexByte1
00
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
6-13
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
System Status Check
IndexByte2
00
ISLAddDa
0000000000
ISLAddSa
000000000000
Match
000000000000
TrafficThresByte0 00
TrafficThresByte1 00
TimeIntervalByte0 00
TimeIntervalByte1 00
GARPAddress
000000000000
Control Frame DA
010000C28001
Control Frame SA
005054AD5A22
CntrlFrameType0
08
CntrlFrameType1
88
CntrlFrameOpcode0 01
CntrlFrameOpcode1 00
CntrlFramePtime0
00
CntrlFramePtime1
08
ColThreshold
00
ColDistance0
00
ColDistance1
00
IPCRcvTime10
00
IPCRcvTime11
00
IPCRcvTime20
00
IPCRcvTime21
00
IPGTxTime0
08
IPGTxTime1
00
TXLnkConfg0
A0
Full duplex capable
Pause capable
TXLnkConfg1
01
Asymmetric on pause capable
No error, link ok
RCVLnkConfgStatus0 BC
Full duplex capable
Pause capable
RCVLnkConfgStatus1 50
Link failure
Ack configuration
RMAC Control
03
Full duplex
Link up - enable reception
TMAC Control
01
Link up
RMACRecvStatus
10
Rx synchronized
LoopBackControl
00
RAMReadEnable
00
TFIFOThreshold
01
threshold set to 16 bytes
CPSoftReset
1F
unset system tx logic
unset system rx logic
unset Mac Tx logic
unset Mac Rx logic
unset link autonegotiation logic
CPInterrupt
20
RMAC receive config change
CPInterruptMask
0F
Host CPU slave machine error mask
Mac CPU slave machine error mask
Global CPU slave machine error mask
Global CPU master machine error mask
CPStatConfig
02
Clear on read enabled
6-14
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
System Status Check
SFP Module Information
Type = 1, SFP_1000BASE_SX
AFT Information
0050.54ad.5a22(
1,
1) ffff.ffff.ffff(
1,
1) 0100.0ccc.cccc(
1,
2)
3 Addresses in CAM
GigMac 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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
6-15
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
Installation Troubleshooting
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#
Installation Troubleshooting
The following table describes the LEDs on the MGX-1GE and MGX-2GE back cards. Follow the
instructions in Table 6-3 to troubleshoot the installation.
LED
Status
Description
LINK
Green
Carrier detected.
Off
Carrier not detected.
Green
Transmitting traffic.
Off
Not transmitting traffic.
Green
Receiving traffic.
Off
Not receiving traffic.
Yellow
Major failure has disabled the back card.
Off
Back card is operating properly
TX (transmit)
RX (receive)
FAIL
6-16
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
Installation Troubleshooting
Table 6-3
MGX-1GE and MGX-2GE Installation Troubleshooting
Symptom
Possible Cause
Corrective Action
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.
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.
Back card initialization Bad back card slot or
fails.
midplane connector.
Remove the back cards (upper and lower slots) and
the front card and install them into another chasis
slot.
Bad back card.
Replace the back card.
Bad front card.
Replace the front card.
The interface does not Configuration
come up or constantly mismatched.
comes up and then goes
down.
Cables connected
incorrectly.
Bad cables.
Check the configuration on both sides. (See the
“Software Configuration Guidelines” section on
page 6-6 for more information.)
Check the cabling on both sides. Ensure the
receive is connected to the transmit on the remote
end and vice versa.
Replace the cables. Ensure your cabling meets the
specifications in the “MGX-1GE Features and
Specifications” section on page 6-2 or the
“MGX-2GE Features and Specifications” section
on page 6-3.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
6-17
Chapter 6
Installing and Configuring the Cisco MGX-1GE and MGX-2GE Gigabit Ethernet Back Cards
Installation Troubleshooting
6-18
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
C H A P T E R
7
Configuring 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 Interface
To 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 or MGX-XF-UI/B 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 management 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 management
back card to 9600 baud. See the “Configuring the Console and Auxiliary Ports” section in
Chapter 4, “Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management
Back Cards.”
cc from another Cisco 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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
7-1
Chapter 7
Configuring the MGX RPM-XF
Booting the RPM-XF
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.
You can also telnet through the Fast Ethernet ports on the management back card. See Chapter 4,
“Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back Cards,” to see
how to assign IP address to the FE interface.
Note
Connecting a modem to the auxiliary port on the management back card is not supported.
Booting the RPM-XF
The RPM-XF boot flash is used to store boot image, configuration and run-time image files. A valid
RPM-XF boot image must be present in the boot flash to successfully boot the card.
RPM-XF Boot Flash Memory Precautions
The 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 boot flash, you will need to use the ROM Monitor to recover the
boot flash. In the ROM Monitor mode, use the tftpdnld utility described in the “Using the tftpdnld
Command” section in Appendix A, “Maintaining the MGX RPM-XF.”
Verifying the Cisco IOS Files in Boot Flash Memory
Enter the show bootflash command to verify the Cisco IOS files in the boot flash memory. The following
example shows the RPM-XF command sequence.
router-slot14#show bootflash:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time-----1
.. image
D7F765BC 306604
20 2647428 Apr 22 2002 11:22:47
2
.D config
65AD67B1 327CE0
18
136795 Apr 26 2002 05:02:06
3
.. config
C3CBD7D7 34937C
18
136732 Apr 30 2002 02:15:24
name
rpmxf-boot-mz.020405
auto_config_slot14
auto_config_slot14
62614660 bytes available (2921340 bytes used)
Verifying the Cisco IOS Files in the PXM45 C:FW Directory
On 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
7-2
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 7
Configuring the MGX RPM-XF
Booting the RPM-XF
The following example shows 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
drwxrwxrwx 1 0
-rwxrwxrwx 1 0
-rwxrwxrwx 1 0
-rwxrwxrwx 1 0
-rwxrwxrwx 1 0
-rwxrwxrwx 1 0
-rwxrwxrwx 1 0
-rwxrwxrwx 1 0
-rwxrwxrwx 1 0
0
0
0
0
0
0
0
0
0
0
13312
13312
7438480
6049940
3121648
6049444
6043924
6043892
2654768
6050100
Apr
Apr
Apr
Apr
Mar
Apr
Mar
Mar
Mar
Mar
29
29
8
4
29
2
22
20
29
29
18:45
14:42
17:18
17:48
18:16
16:09
14:04
18:51
18:14
17:15
./
../
rpmxf-p12-mz.020405
pxm45_003.000.000.026-A_mgx.fw
axsm_003.000.000.234-P1.fw
pxm45_003.000.000.000-D_mgx.fw
pxm45_003.000.000.001-A_mgx.fw
pxm45_003.000.000.239-A_mgx.fw
axsme_003.000.000.234-P1.fw
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 Directory
On 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 example shows 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
drwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
-rwxrwxrwx 1 0
0
2048
2048
627
806
632
5747
77849
59697
14
14
14
14
14
14
14
14
842
May
May
Feb
Feb
Feb
Apr
Feb
Feb
May
May
May
May
May
May
May
May
Apr
13
13
5
6
4
16
13
13
13
13
13
13
13
13
13
13
25
12:41
11:24
13:33
20:01
23:16
14:34
01:07
00:53
11:14
11:14
11:14
11:14
11:14
11:14
11:14
11:14
18:25
./
../
zen10.conf.svenki
rpm12.conf.svenki
zenith10.conf.svenki
slot05
zen14.conf.svenki021202
zen3.conf.svenki021202
auto_config_slot05
auto_config_slot13
auto_config_slot03
auto_config_slot01
auto_config_slot06
auto_config_slot09
auto_config_slot12
auto_config_slot14
zen
In the file system :
total space : 102140 K bytes
free space : 89446 K bytes
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
7-3
Chapter 7
Configuring the MGX RPM-XF
Booting the RPM-XF
Initializing the RPM-XF Card
The 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#dir
Directory of bootflash:/
1
3
-rw-rw-
2647428
136732
Apr 22 2002 11:22:47
Apr 30 2002 02:15:24
rpmxf-boot-mz.020405
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
0
0
0
0
0
0
0
-rw-rw-rw-rw-rw-rw-rw-rw-
7438480
6049940
3121648
6049444
6043924
6043892
2654768
6050100
Apr
Apr
Mar
Apr
Mar
Mar
Mar
Mar
09
05
30
03
22
21
30
30
2002
2002
2002
2002
2002
2002
2002
2002
01:18:34
01:48:02
02:16:02
00:09:12
22:04:12
02:51:20
02:14:22
01:15:30
rpmxf-p12-mz.020405
pxm45_003.000.000.026-A_mgx.fw
axsm_003.000.000.234-P1.fw
pxm45_003.000.000.000-D_mgx.fw
pxm45_003.000.000.001-A_mgx.fw
pxm45_003.000.000.239-A_mgx.fw
axsme_003.000.000.234-P1.fw
pxm45_003.000.000.009-A_mgx.fw
838616064 bytes total (482072752 bytes free)
To boot the runtime image from the boot flash, copy the image to the boot flash, as follows.
Router#copy x:rpmxf-p12-mz.1228T_XT1 bootflash:
Destination filename [rpmxf-p12-mz.1228T_XT1]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
:
:
:
:
:
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
7445832 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 existing boot system commands.
Router(config)#no boot system
7-4
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 7
Configuring the MGX RPM-XF
Booting the RPM-XF
Step 7
The RPM-XF can be booted from either the boot flash or PXM45 hard disk, by entering either,
boot system bootflash:< filename> to load the runtime software from the boot flash
or
boot 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 Interface
You 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
Step 1
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.
Enter show ip int brief to display your router IP interfaces.
Router#show ip int brief
Interface
Switch0
Switch1
FastEthernet2/0
FastEthernet2/1
Note
Step 2
IP-Address
unassigned
unassigned
unassigned
unassigned
OK?
YES
YES
YES
YES
Method
unset
unset
unset
unset
Status
Protocol
up
up
up
up
administratively down down
administratively down down
The switch0 interface cannot be assigned an IP address.
Enter conf terminal to enter global configuration mode.
Router#conf terminal
Enter 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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
7-5
Chapter 7
Configuring the MGX RPM-XF
Booting the RPM-XF
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 brief
Interface
Switch0
Switch1
Note
Step 7
IP-Address
unassigned
1.1.1.1
OK? Method Status
YES unset up
YES manual up
Protocol
up
up
The newly added interface address appears in the display.
Enter show run to verify the configuration of the RPM-XF, as shown in the following sample output.
Router#show run
Building configuration...
Current configuration :687 bytes
!
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Router
!
boot system x:rpmxf-p12-mz.020405
boot config e:auto_config_slot02
no logging console
enable password cisco
!
ip subnet-zero
!
!
!
interface Switch1
ip address 1.1.1.1 255.255.255.0
switch auto_synch off
!
ip classless
no ip http server
ip pim bidir-enable
!
snmp-server engineID local 80000009FF0000A100000000
snmp-server community public RO
snmp-server community private RW
snmp-server ifindex persist
!
!
line con 0
exec-timeout 0 0
stopbits 1
line aux 0
stopbits 1
line vty 0 4
exec-timeout 0 0
no login
!
end
7-6
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 7
Configuring the MGX RPM-XF
Booting the RPM-XF
Step 8
Enter copy run start at the prompt to write the configuration to the router NVRAM memory.
Router#copy run start
Building 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 the “Creating and Configuring a Switch
Subinterface” in Chapter 8, “Configuring PNNI Communications.”
Booting RPM-XF Using TFTP from a TFTP Server
Once 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 run
Building configuration...
Current configuration : 710 bytes
!
version 12.1
no service single-slot-reload-enable
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Router
!
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
7-7
Chapter 7
Configuring the MGX RPM-XF
Booting the RPM-XF
boot system tftp://171.69.1.129/tftpboot/shrinath/rpmxf-p12-mz
boot config e:auto_config_slot11
logging rate-limit console 10 except errors
enable password cisco
!
ip subnet-zero
no 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 start
Building 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 Sequence
Each time you turn on power to the RPM-XF, by inserting the RPM-XF into the Cisco 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.)
•
3.
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.
The RPM-XF will look for the runtime image either in boot flash 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 boot flash.
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 boot flash.
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.
7-8
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 7
Configuring the MGX RPM-XF
Verifying the Configuration
6.
For normal RPM-XF operation, there must be a valid Cisco IOS image in the PXM45 C:FW
directory or in boot flash, and a configuration in NVRAM. in boot flash, 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.”
Verifying the Configuration
Enter the show commands to display the status of the all interfaces.
Verifying 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 0
Switch0 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 Switch1
Switch1 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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
7-9
Chapter 7
Configuring the MGX RPM-XF
Verifying the Configuration
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 enabled
Switch0 is up, line protocol is up
Switch1 is up, line protocol is up
Switch1.40 is up, line protocol is up
Internet address is 2.2.2.2/24
Switch1.41 is up, line protocol is up
Internet address is 3.3.3.3/24
Switch1.42 is up, line protocol is up
FastEthernet2/0 is administratively down, line protocol is down
FastEthernet2/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.
7-10
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 7
Configuring the MGX RPM-XF
Verifying the Configuration
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 version
Cisco 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 Software
BOOTLDR:RPMXF Software (RPMXF-BOOT-M), Experimental Version 12.2(20020321:034801)
[swtools-zenith1.nightly 192]
router2-slot14 uptime is 5 hours, 38 minutes
System returned to ROM by reload
System 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 Cache
Last reset from service module reset
PXF 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 bootvar
BOOT variable = x:rpmxf-p12-mz.1228T_XT1,12;
CONFIG_FILE variable = e:auto_config_slot02
BOOTLDR variable = bootflash:rpmxf-boot-mz.1228T_XT1
Configuration register is 0x2
Displaying 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>enable
Password:
Router#show rpm
RPM is in chassis slot 11
PXM has ip address 172.29.5.248
Active PXM is in slot 7
Network IO Interrupt Throttling:
throttle count=0, timer count=0
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
7-11
Chapter 7
Configuring the MGX RPM-XF
Verifying the Configuration
active=0, configured=1
netint usec=4000, netint mask usec=1000
RPM-XF IO FPGA Registers:
flash_watchdog_enable
flash_size
lev1_watchdog
led_control
lev2_watchdog
int_status_0
int_mask_0
masked_int_status_0
int_mask_1
reset
power_adjust
slot_id
(0x14200000)
(0x14200004)
(0x14200008)
(0x14200014)
(0x14200018)
(0x1420001C)
(0x14200024)
(0x1420006C)
(0x14200028)
(0x1420002C)
(0x14200054)
(0x14200058)
:
:
:
:
:
:
:
:
:
:
:
:
0x00000033
0x00000006
0x0000FA00
0x00000002
0x000FFFFF
0x00001000
0xC3CEFC81
0x00000000
0x00000004
0x00000002
0x00000000
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-03
Management 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-info
PXM Supports Redundancy :Yes
RPM Physical Slot Number :14
RPM Logical Slot Number :14
RPM Selftest :Disabled
RPM Selftest Period :0
RPM Backcard Type [Upper Slot] :MGX-XF-OC12
RPM Backcard Type [Lower Slot] :MGX-XF-UI
RPM Card State :ACTIVE
RPM Internal Card State :ACTIVE
RPM skipped initial configuration in the NVRAM:Yes
Configuration file was received from PXM:Yes
Auto Configuration File Used :None
RPM Redundancy Mode:Linked
RPM Redundancy Link Type:Primary
See the “Verifying Ethernet Connectivity”section in Chapter 4, “Installing and Configuring the
MGX-XF-UI and MGX-XF-UI/B Management Back Cards,” to verify that each interface port is
functioning properly.
7-12
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 7
Configuring the MGX RPM-XF
Establishing 1:N Redundancy Between Two or More RPM-XF Cards
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 Cisco 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:
Step 5
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.
Enter the addred command.
Switch.7.PXM.a > addred <redPrimarySlotNum> <redSecondarySlotNum> <redType>
Parameter
Description
<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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
7-13
Chapter 7
Configuring the MGX RPM-XF
Establishing 1:N Redundancy Between Two or More RPM-XF Cards
Note
Step 6
After you enter the addred command, the switch resets the secondary card; therefore, the
secondary card will be unavailable for a few minutes.
When the reset is complete, enter the dspcds command to show the primary and secondary cards in the
active and standby states, respectively.
The redundant RPM cards are shown in slots 2 and 10 with the standby card in slot 10.
Unknown.8.PXM.a > dspcds
Unknown
System Rev:03.00
Chassis Serial No: SCA0444006R Chassis Rev:E0
Step 7
Card
Slot
---
Front/Back
Card State
----------
Card
Type
--------
Alarm
Status
--------
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
Empty
Active/Active
Empty
Active/Empty
Empty
Empty
Standby/Active
Active/Active
Empty
Standby/Active
Active/Empty
Empty
Empty
Empty
Empty
--RPM_XF
--RPM_PR
----PXM45B
PXM45B
--RPM_XF
RPM_XF
---------
--NONE
--NONE
----NONE
NONE
--NONE
NONE
---------
May. 13, 2002 18:55:56 GMT
GMT Offset:0
Node Alarm:MAJOR
Redundant
Redundancy
Slot
Type
------------10
--NA
----08
07
--00
NA
---------
--PRIMARY SLOT
--NO REDUNDANCY
----PRIMARY SLOT
SECONDARY SLOT
--SECONDARY SLOT
NO REDUNDANCY
---------
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 > dspred
Unknown
System Rev:03.00
May. 13, 2002 18:57:26 GMT
MGX8850
Node Alarm:MAJOR
Logical
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
7-14
The standby card must not have any configurations and must not be configured. Therefore, do not
provision the standby card.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 7
Configuring the MGX RPM-XF
Establishing 1:N Redundancy Between Two or More RPM-XF Cards
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 Cisco 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 10
switchredcd: Do you want to proceed (Yes/No)? y
Parameter
Description
2
Active or primary card.
10
Standby or secondary card.
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 2
switchredcd: Do you want to proceed (Yes/No)? y
Parameter
Description
10
Active or primary card.
2
Standby or secondary card.
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
7-15
Chapter 7
Configuring the MGX RPM-XF
Establishing 1:N Redundancy Between Two or More RPM-XF Cards
Unknown.8.PXM.a > dspred
Unknown
System Rev:03.00
May. 13, 2002 18:58:45 GMT
MGX8850
Node Alarm:MAJOR
Logical
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.
Unknown.8.PXM.a > dspcds
Unknown
System Rev:03.00
Chassis Serial No: SCA0444006R Chassis Rev:E0
Card
Slot
---
Front/Back
Card State
----------
Card
Type
--------
Alarm
Status
--------
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
Empty
Active/Active
Empty
Active/Empty
Empty
Empty
Standby/Active
Active/Active
Empty
Active/Active
Active/Empty
Empty
Empty
Empty
Empty
--RPM_XF
--RPM
----PXM45B
PXM45B
--RPM_XF
RPM_XF
---------
--NONE
--NONE
----NONE
NONE
--NONE
NONE
---------
May. 13, 2002 19:00:33 GMT
GMT Offset:0
Node Alarm:MAJOR
Redundant
Redundancy
Slot
Type
------------NA
--NA
----08
07
--NA
NA
---------
--NO REDUNDANCY
--NO REDUNDANCY
----PRIMARY SLOT
SECONDARY SLOT
--NO REDUNDANCY
NO REDUNDANCY
---------
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 2
switch.7.PXM.a > addred 3 10 2
switch.7.PXM.a > addred 4 10 2
7-16
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 7
Configuring the MGX RPM-XF
Establishing 1:N Redundancy Between Two or More RPM-XF Cards
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 boot
flash 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 boot
flash 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
7-17
Chapter 7
Configuring the MGX RPM-XF
Enabling IP Accounting Counters
Enabling IP Accounting Counters
The 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:
7-18
Command
Description
ip accounting ?
pop20-slot6(config-if)#ip accounting ?
precedence
Count packets by IP precedence on
this interface
dscp
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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
C H A P T E R
8
Configuring 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 Quickstarts
Configuration 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 Quickstart
The 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
8-1
Chapter 8
Configuring PNNI Communications
Configuration Quickstarts
Command
Step 1
Purpose
Prompt: Switch.7.PXM.a
>
dspcontrollers
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.
Step 2
addcontroller <cntrlrId> i
<cntrlrType> <slot>
[cntrlrName]
Adds a controller.
Prompt: RPM-XF
Assign the switch1 interface resources to the PNNI controller.
This procedure must be completed once for each RPM-XF card.
(config) #
interface switch1
switch partition <options>
ingress-percentage-bandwidth
<options>
egress-percentage-bandwidth
<options>
vpi <options>
vci <options>
connection-limit <options>
See the “Assigning Link Resources to a PNNI Controller” section
later in this chapter.
Related commands:
show switch partitions
RPM-XF to RPM-XF Connection Quickstart
The 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
PXM45
PXM45
RPM-XF
RPM-XF
AXSM
PXM45
PXM45
RPM-XF
RPM-XF
1
7 8 9 10
1
7 8 9 10
0/2000
Slave
0/2001
Master
Connection A
8-2
0/200
Master
0/200
Slave
Connection B
0/300
Slave
75810
AXSM
PNNI
0/305
Master
Connection C
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 8
Configuring PNNI Communications
Configuration Quickstarts
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.
Step 1
Command
Purpose
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 connection
show ip int br
Step 3
cc <slot>
dspcon <port> <vpi> <vci>
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.
Change to an active PXM45 card and copy or write down the
ATM address for the slave endpoint.
See the “Creating a Slave Connection on the RPM-XF” section
later in this chapter.
Step 4
interface Switch 1.xx <options>
ip address <options>
pvc vpi/vci
At the RPM that will host the master side of the connection,
create and configure a subinterface to host the master side
connection.
See the “Creating and Configuring a Switch Subinterface”
section later in this chapter.
Step 5
switch connection <options>
Related commands
show switch connection
show ip int br
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
8-3
Chapter 8
Configuring PNNI Communications
Configuration Quickstarts
RPM-XF Slave to the AXSM Master Connection Quickstart
The 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.
Figure 8-2
RPM-XF Slave to AXSM Master Connections
PXM45
PXM45
RPM-XF
AXSM
AXSM
PXM45
PXM45
RPM-XF
1
7 8 9
11
1
7 8 9
UNI port
to CPE
75788
AXSM
PNNI
UNI port
to CPE
0/100
Master
0/100
Slave
0/200
Master
0/200
Slave
Connection B
Connection A
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.
Step 1
Command
Purpose
interface Switch 1.xx <options>
ip address <options>
pvc vpi/vci
At the RPM that hosts 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 connection
show ip int br
8-4
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 8
Configuring PNNI Communications
Configuration Quickstarts
Step 3
Command
Purpose
cc <slot>
dspcon <port> <vpi> <vci>
Change to active PXM45 card and copy or write down the ATM
address for the slave endpoint.
See the “Creating a Slave Connection on the RPM-XF” section
later in this chapter.
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-link
dsppnni-node-list
dsppnni-node
dsppnni-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
Step 6
addport
addpart
The dsppnni-link command provides real-time data.
For the other dsppnni commands, designate a PNNI
topology state element (PTSE) time out.
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>
Add the master side of the connection to the UNI port.
Related commands
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.
dspcons
dspcon <port> <vpi> <vci>
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
8-5
Chapter 8
Configuring PNNI Communications
Configuration Quickstarts
AXSM Slave to RPM-XF Master Connection Quickstart
The 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
75811
PXM45
PXM45
RPM-XF
AXSM
AXSM
AXSM
PXM45
PXM45
RPM-XF
PNNI
UNI port
to CPE
UNI port
to CPE
0/100
Master
0/100
Slave
0/200
Slave
Connection A
0/200
Master
Connection B
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.
Step 1
Command
Purpose
dnln
cnfcdsct
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-link
dsppnni-node-list
dsppnni-node
dsppnni-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.
8-6
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 8
Configuring PNNI Communications
Configuring PNNI Connections
Step 3
Command
Purpose
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
dspcons
dspcon <port> <vpi> <vci>
Step 5
interface Switch 1.xx <options>
ip address <options>
pvc 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.
See the “Creating and Configuring a Switch Subinterface”
section later in this chapter.
Step 6
switch connection <options>
Related commands
show switch connection
show ip int br
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.
Configuring PNNI Connections
The following sections describe the steps listed in the configuration quickstarts.
Verifying the PNNI Controller Configuration
A 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.
Switch.7.PXM.a > dspcontrollers
Switch
System Rev: 02.01
MGX8850
Number 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:
Mar. 22, 2001 11:25:29 PST
Node Alarm: CRITICAL
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
8-7
Chapter 8
Configuring PNNI Communications
Configuring PNNI Connections
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 Controller
Link 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
Parameter
Description
partId
Range is 1 to 10.
ctrlrId
Range is 2 to 20; 2 is reserved for PNNI.
Enter the ingress-percentage-bandwidth command at the swpart prompt to specify the minimum and
maximum ingress percentage bandwidth.
(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>
8-8
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 8
Configuring PNNI Communications
Configuring PNNI Connections
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 100
Router(config-if-swpart)#egress-percentage-bandwidth 1 100
Router(config-if-swpart)#vpi 0 0
Router(config-if-swpart)#vci 2000 3000
Router(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
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-connectionlimit
The minimum number of connections that can be added on this controller.
max-connectionlimit
The maximum number of connections that can be added on this controller.
VPI and VCI Assignments
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
8-9
Chapter 8
Configuring PNNI Communications
Configuring PNNI Connections
Partitions:
•
Partition 1 (Partition ID 5; Interface # 1)—VPI range: 0 to 100; VCI range: 32 to 65535
•
Partition 2 (Partition ID 6; Interface # 1)—VPI range: 101 to 200; VCI range: 32 to 65535
•
Partition 3 (Partition ID 1; Interface # 1)—VPI range: 201 to 240; VCI range: 32 to 65535
Table 8-2
Partitioning VPI/VCI Resources on the RPM-XF
Partition 1 Partition 2 Partition 3
PNNI Controller
LSC1
LSC2
X
X
X
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 Allocations
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.
Router(config-if-swpart)#ingress-percentage-bandwidth 1 100
Router(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.
8-10
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 8
Configuring PNNI Communications
Configuring PNNI Connections
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
Switch 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
Router(config-if-swpart)#
Router(config-if-swpart)#
Router(config-if-swpart)#
Router(config-if-swpart)#
Router(config-if-swpart)#
partition <partId> <ctrlrId>
ingress-percentage-bandwidth <ingMinPctBw> <ingMaxPctBw>
egress-percentage-bandwidth <egrMinPctBw> <egrMaxPctBw>
vpi <min_vpi> <max_vpi>
vci <min_vci> <max_vci>
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 terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#interface switch1
Router(config-if)#switch part 1 2
Router(config-if-swpart)#ingress-percentage-bandwidth 1 100
Router(config-if-swpart)#egress-percentage-bandwidth 1 100
Router(config-if-swpart)#vpi 0 0
Router(config-if-swpart)#vci 2000 3000
Router(config-if-swpart)#connection-limit 100 1000
Router(config-if-swpart)#end
Router#copy run start
Building configuration...
[OK]
Step 3
Enter the show switch partition commands to verify your configuration.
Router#show
Part Ctrlr
Id
Id
1
2
switch partition
Guar
Max
Guar
Ing%Bw Ing%Bw Egr%Bw
1
100
1
Max
Egr%Bw
100
minVpi maxVpi minVci maxVci MaxCons
0
0
2000
3000
1001
Router#show switch partition vcc 1
------------------------------------------------------Shelf
: 1
Pxm Slot
: 7
Slot
: 9
IfType
: 3
IfNum
: 1
Partition ID
: 1
Controller ID
: 2
Guaranteed Ingress Pct BW: 1
Max Ingress Pct BW
: 100
Guaranteed Egress Pct BW : 1
Max Egress Pct BW
: 100
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
8-11
Chapter 8
Configuring PNNI Communications
Configuring PNNI Connections
VPI Low
VPI High
VCI Low
VCI High
Maximum # of Connections
:
:
:
:
:
0
0
2000
3000
1001
Configuring Switch Interface Signaling
The 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 > dsppnports
Summary of total connections
(p2p=point to point,p2mp=point to
Type
#Svcc:
#Svpc:
#SpvcD:
p2p:
0
0
3
p2mp: 0
0
0
multipoint,SpvcD=DAX spvc,SpvcR=Routed spvc)
#SpvpD: #SpvcR: #SpvpR: #Total:
0
0
0
3
0
0
0
0
Total=3
Summary of total configured SPVC endpoints
Type
#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
7.36
up
up
Undefined
0
7.37
up
up
Undefined
0
7.38
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.
8-12
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 8
Configuring PNNI Communications
Configuring PNNI Connections
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
sigType: private
addrPlan: aesa
sigVpi:
0
rccVpi:
n/a
version:
side:
sigVci:
rccVci:
uni3.1
network
5
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
sigType: private
addrPlan: aesa
sigVpi:
0
rccVpi:
n/a
Step 3
version:
side:
sigVci:
rccVci:
none
network
5
n/a
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 using 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 Subinterface
The 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
8-13
Chapter 8
Configuring PNNI Communications
Configuring PNNI Connections
To create a switch subinterface, configure the following features, as described in the procedure below:
Step 1
•
IP address for the subinterface
•
PVC for the subinterface
•
PVC configuration parameters
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
Step 3
The IP addresses for the subinterfaces at the slave and master ends of a connection should share
the same subnet.
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
Step 4
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.
Enter a question mark to list the commands available for configuring 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
8-14
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 8
Configuring PNNI Communications
Configuring PNNI Connections
no
oam
oam-pvc
pppoe
pppoe-client
protocol
random-detect
service-policy
transmit-priority
tx-ring-limit
ubr
vbr-nrt
vbr-rt
vc-hold-queue
vcci
Negate a command or set its defaults
Configure oam parameters
Send oam cells on this pvc
PPPoE options
pppoe client
Map an upper layer protocol to this connection.
Configure WRED
Attach a policy-map to a VC
set the transmit priority for this VC
Configure PA level transmit ring limit
Enter Unspecified Peak Cell Rate (pcr) in Kbps.
Enter Variable Bit Rate (pcr)(scr)(bcs)
Enter Variable Bit Rate (pcr)(average)
Configure hold queue size
VCC Identifier
The following example shows some commands you might want to use to configure the PVC.
Router(config-if-atm-vc)#oam-pvc manage
Router(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-vc
Router(config-subif)#
Creating a Slave Connection on the RPM-XF
When 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>enable
Password:
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#interface switch 1.1
Router(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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
8-15
Chapter 8
Configuring PNNI Communications
Configuring PNNI Connections
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
Step 6
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.
Press Ctrl-Z to exit configuration mode. Then save your configuration change.
Router(config-subif)#^Z
Router#copy run start
Building configuration...
[OK]
8-16
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 8
Configuring PNNI Communications
Configuring PNNI Connections
Step 7
Enter the show switch connection command to view the slave endpoint connection. For example,
Router#show switch connection
Step 8
lVpi lVci
NSAP Address
Synch
rVpi rVci Status
0
default
0
2000
inSynch:
Parameter
Description
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.
Enter the show ip interface brief command to view the IP interfaces on the RPM-XF.
Router#show ip int br
Interface
FastEthernet1/1
Switch1
Switch1.1
Step 9
0
IP-Address
172.29.52.3
unassigned
1.1.1.1
OK?
YES
YES
YES
Method
manual
NVRAM
manual
Status
Protocol
administratively down down
up
up
up
up
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.
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 2000
Port
Vpi Vci
Owner
State
------------------------------------------------------------------------Local 9:-1.1:-1
0.2000
SLAVE
FAIL
Address: 47.00918100000000036b5e2bb2.000001074b01.00
Remote 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: 0
Continuity Check: Disabled
Frame Discard: Disabled
L-Utils: 0
R-Utils: 0
Max Cost: 0
Routing Cost: 0
OAM 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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
8-17
Chapter 8
Configuring PNNI Communications
Configuring PNNI Connections
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-XF
When 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>enable
Password:
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#interface switch 1.2 point-to-point
Router(config-subif)#
Note
Step 2
When configuring the subinterface, you must specify point-to-point or p, mu, tag or mpls.
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
8-18
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 8
Configuring PNNI Communications
Configuring PNNI Connections
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
Step 6
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.)
Press Ctrl-Z to exit configuration mode and then save your configuration change.
Router(config-subif)#^Z
Router#copy run start
Building configuration...
[OK]
Step 7
Enter the show switch connection command to view the master endpoint connection.
Router#show switch connection
lVpi lVci
NSAP Address
Synch
rVpi rVci Status
0
0
default
47.0091.8100.0000.0003.6b5e.2bb2.0000.0107.4b01.00
0
0
2000
2001
0
inSynch
2000 inSynch
Parameter
Description
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
8-19
Chapter 8
Configuring PNNI Communications
Configuring PNNI Connections
Parameter
Description
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.
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.
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 2001
Port
Vpi Vci
Owner
State
------------------------------------------------------------------------Local 9:-1.1:-1
0.2001
MASTER
OK
Address: 47.00918100000000036b5e2bb2.000001074b01.00
Remote 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: 0
Continuity Check: Disabled
Frame Discard: Disabled
L-Utils: 100
R-Utils: 100
Max Cost: -1
Routing Cost: 0
OAM 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>enable
Password:
Router#show ip int br
Interface
FastEthernet1/1
Switch1
Switch1.1
Switch1.2
Step 10
IP-Address
172.29.52.3
unassigned
1.1.1.1
1.1.2.1
OK?
YES
YES
YES
YES
Method
manual
NVRAM
manual
manual
Status
Protocol
administratively down down
up
up
up
up
up
up
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
8-20
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 8
Configuring PNNI Communications
Connection Management
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.
Connection Management
This section describes connection management tasks for the RPM-XF.
Deleting a Connection
To 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 Parameters
The 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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
8-21
Chapter 8
Configuring PNNI Communications
Connection Management
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.
Downing and Upping the Connection
A 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 Connection
A 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 Synchronization
RPM-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.
8-22
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 8
Configuring PNNI Communications
Connection Management
•
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.
•
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 terminal
Router(config)# interface sw1
Router(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 t
Router(config)# int sw1
Router(config-if)#switch auto_synch on <off|manual> “default is off”
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
8-23
Chapter 8
Configuring PNNI Communications
Connection State Alarms
Connection State Alarms
This 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
8-24
•
There is a change in the endpoint status.
•
A failure is detected by the Connection Manager during a routine routing status check.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
C H A P T E R
9
Configuring 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 Cisco MGX 8850 and covers
the following topics:
•
MPLS Overview
•
Configuring MPLS for Cisco 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 Cisco MGX 8850 Release 5.1 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 Overview
This section describes MPLS and the role of the RPM-XF as an ELSR and LSC within the Cisco 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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
9-1
Chapter 9
Configuring MPLS Features
MPLS 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 MPLS
MPLS 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.
Cisco 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 Cisco MGX 8850 Switch
On the Cisco 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
Cisco MGX 8850, see the ““System Block Diagram” section on page 9-3.
MPLS 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 Cisco 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 Cisco MGX 8850 shelf:
– Regular XtagATM interfaces
– VP tunnel based XtagATM interfaces
– MPLS COS on the LSC
9-2
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 9
Configuring MPLS Features
MPLS Overview
Note
Using LSC and ELSR on the same RPM-XF is not supported.
Note
RPM-XF ELSR does not support LSC redundancy.
•
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 Cisco MGX 8850 (Release 5.1) 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 Cisco MGX 8850 (Release 5.1) on the
right.
Note
Interoperability between the RPM-XF LSC/ELSR in a Cisco MGX 8850 (Release 5.1) node and an
RPM-PR ELSR in a PXM1-based Cisco MGX 8850/8250/8230 node is also supported. Refer to the
Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide for details.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
9-3
Chapter 9
Configuring MPLS Features
Configuring MPLS for Cisco MGX 8850
Figure 9-1
Cisco MGX 8850s with ELSR and LSC Configured RPM-XF
MGX 8850 (Release 3)
RPM-XF
LSC
Master
MGX 8850 (Release 3)
RPM-XF
LSC-B
Master
LDP
LDP
ELSR
LDP
Slave
Slave
RPM-XF
ELSR-B
RPM-XF
Slave
Slave
AXSM
PXM
AXSM
AXSM
Unlabeled traffic
Labeled traffic
PXM
AXSM
75540
LVC
Unlabeled traffic
MPLS Class of Service Support
This 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 Cisco 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 Cisco MGX 8850
This section describes procedures needed to configure the RPM-XF, the PXM45, and AXSM cards to
support MPLS on Cisco MGX 8850 switches.
To support MPLS, you need to do the following:
9-4
•
Add an MPLS controller to the PXM45 for an RPM-XF LSC.
•
Configure an RPM-XF as the LSC.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 9
Configuring MPLS Features
Configuring MPLS for Cisco MGX 8850
•
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 LSC
The 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]
Parameter
Description
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.
For example,
MGX8850.7.PXM.a>addcontroller 5 i 3 5 LSC-5
Step 2
Parameter
Description
cntrlrId
5
i
i = internal
cntrlrType
3 = LSC
slot
5 = RPM-XF LSC inserted in slot 5.
cntrlrName
LSC-5
Enter the cc command, cc 5, to change to the RPM-XF card.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
9-5
Chapter 9
Configuring MPLS Features
Configuring MPLS for Cisco MGX 8850
Step 3
Enter the commands shown in the following example to configure the RPM-XF as an LSC.
RPM-XF>enable
Password:
RPM-XF#config terminal
Enter configuration commands, one per line. End with CNTL/Z.
RPM-XF(config)#interface loopback0
RPM-XF(config-if)#ip address 28.28.28.28 255.255.255.255
RPM-XF(config-if)#interface switch1
RPM-XF(config-if)#no ip address
RPM-XF(config-if)#label-control-protocol vsi id 5
RPM-XF(config-if)#switch partition 5 5
RPM-XF(config-if-swpart)#ingress-percentage-bandwidth 10 100
RPM-XF(config-if-swpart)#egress-percentage-bandwidth 10 100
RPM-XF(config-if-swpart)#vpi 0 50
RPM-XF(config-if-swpart)#vci 32 10000
RPM-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 MPLS
Next, 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
Step 3
4 = policing on and 5 = policing off (for ATM Forum service types)
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]
9-6
Parameter
Description
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 9
Configuring MPLS Features
Configuring MPLS for Cisco MGX 8850
Parameter
Description
maxRate
Maximum rate depends on connection, as follows:
OC48—between 50 and 5651320
OC12—between 50 and 1412830
OC3—between 50 and 353207
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.
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>
Parameter
Description
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.)
For example,
MGX8850.1.AXSM.a>addpart 1 2 5 500000 500000 500000 500000 0 1500 32 65535 4000 4000
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
9-7
Chapter 9
Configuring MPLS Features
Configuring MPLS for Cisco MGX 8850
Step 6
Enter the dspparts command to view the newly-added partition and verify its settings.
MGX8850.1.AXSM.a > dspparts
if part Ctlr egr
egr
ingr
ingr
min max
min
max min
max
Num 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 Router
You can also configure an RPM-XF as an Edge Label Switch Router (ELSR) on the Cisco 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 loopback0
RPMELSR(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 switch1
RPMELSR(config-if)#switch partition 5 5
RPMELSR(config-if)#ingress-percentage-bandwidth 10 100
RPMELSR(config-if)#egress-percentage-bandwidth 10 100
RPMELSR(config-if)#vpi 100 100
RPMELSR(config-if)#vci 32 65535
RPMELSR(config-if)#connection-limit 1 10000
Step 3
Enter the following commands to create an MPLS sub-interface.
RPMELSR(config)#interface switch1.11 mpls
RPMELSR(config-if)#ip unnumbered loopback0
RPMELSR(config-if)#mpls ip
RPMELSR(config-if)#mpls atm control-vc 100 32
RPMELSR(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
9-8
Because Cisco Express Forwarding is enabled on RPM-XF by default, it is not necessary to use
the ip cef command.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 9
Configuring MPLS Features
VPN Overview
Mapping an AXSM Port and ELSR Port to XTagATM Interfaces on the LSC
Enter 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>enable
Password:
Step 3
Enter config t to enter global configuration mode.
RPMLSC#config t
Enter 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 XTagATM1111
RPMLSC(config-if)#ip unnumbered Loopback0
RPMLSC(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 XTagATM4122
RPMLSC(config-if)#ip unnumbered loopback0
RPMLSC(config-if)#extended-port Switch1 descriptor “4:1.2:2”
RPMLSC(config-if)#mpls ip
RPMLSC(config-if)#mpls atm control-vc 100 32
RPMLSC(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 Overview
Virtual 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 M PLS V PN s,referto:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/vpn.htm
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
9-9
Chapter 9
Configuring MPLS Features
VPN 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#x
tocid151250
Requirements
The 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 Features
Beyond 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
9-10
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).
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 9
Configuring MPLS Features
How 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 Platforms
All Cisco routers, including the Cisco 3600 Series Routers, the Cisco 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 Work
Each 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 MPLS
A 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 Lists
The 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
9-11
Chapter 9
Configuring MPLS Features
How VPNs Work
iBGP Distribution of VPN Routing Information
A 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 Forwarding
Based 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 Topologies
A 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.
9-12
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 9
Configuring MPLS Features
Configuring a VPN
Figure 9-2
VPN with a Service Provider (P) Backbone Network
VPN 2
VPN 1
Site 1
Service provider
backbone
PE
P
Site 1
P
CE
PE
CE
Site 2
P
PE
P
CE
VPN 1
17265
Site 2
CE
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
VPN2
VPN3
VPN1
Site 1
Site 2
Site 4
Site 5
17266
Site 3
Configuring a VPN
This 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.
Prerequisites for VPN Operation
The network must be running the following Cisco IOS services before you can configure VPN operation:
•
CEF switching in every tag-enabled router.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
9-13
Chapter 9
Configuring MPLS Features
Configuring a VPN
•
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 Operation
This 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 name
RPM(config-router-af)# aggregate-address
RPM(config-router-af)# auto-summary
RPM(config-router-af)# default-information originate
RPM(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)# synchronization
RPM(config-router-af)# table-map...
9-14
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 9
Configuring MPLS Features
Configuring a VPN
Note
Step 5
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.”
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 name
RPM(config-router-af)# auto-summary
RPM(config-router-af)# default-information originate
RPM(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)#
RPM(config-router-af)#
RPM(config-router-af)#
RPM(config-router-af)#
Step 3
neighbor
neighbor
neighbor
neighbor
address | peer-group} remote-as as-number
address | peer-group} update-source interface
peer-group peer-group
address peer-group peer-group
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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
9-15
Chapter 9
Configuring MPLS Features
Configuring a VPN
Step 4
Enter optional BGP global commands that affect all address families.
RPM(config-router)#
RPM(config-router)#
RPM(config-router)#
RPM(config-router)#
RPM(config-router)#
RPM(config-router)#
RPM(config-router)#
RPM(config-router)#
RPM(config-router)#
RPM(config-router)#
RPM(config-router)#
RPM(config-router)#
Step 5
bgp always-compare-med
bgp bestpath ...
bgp client-to-client reflection
bgp cluster-id ...
bgp confederation ...
bgp default local-XFeference ...
bgp deterministic-med ...
bgp fast-external-fallover ...
bgp log-neighbor-changes
bgp redistribute-internal
bgp router-id ...
timers bgp ...
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-number
RPM(config-router)# neighbor address update-source interface
Step 8
Activate the advertisement of VPNv4 NLRIs.
RPM(config-router)# address-family vpnv4
RPM(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.
9-16
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 9
Configuring MPLS Features
Configuring a VPN
Command
Description
maximum-path <nums>
Configure maximum number of EiBGP parallel routes.
For example:
bgpbox-zenith-CE1(config)#router bgp 4
bgpbox-zenith-CE1(config-rout)#maximum-paths 3
bgpbox-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.0
BGP routing table entry for 141.22.0.0/16, version 18
Paths: (2 available, best #1)
Multipath: eBGP
Advertised to non peer-group peers:
7.0.76.9
100 5
7.0.76.2 from 7.0.76.2 (100.0.0.2)
Origin IGP, localpref 100, valid, external, multipath,
best
100 5
7.0.76.9 from 7.0.76.9 (100.0.0.9)
Origin IGP, localpref 100, valid, external, multipath
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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
9-17
Chapter 9
Configuring MPLS Features
Multicast VPN
Checking the VRFs
Perform the following steps to verify the VPN configuration.
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-number
RPM# 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
Multicast VPN
Multicast 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.
9-18
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 9
Configuring MPLS Features
Multicast 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.
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.
Multicast VPN Operation
Multicast 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.
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
9-19
Chapter 9
Configuring MPLS Features
Multicast VPN
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 coke
rd 1:1
route-target export 1:1
route-target import 1:1
mdt default 232.0.0.1
mdt data 232.0.1.0 0.0.0.255 threshold 500
!
ip pim sparse-mode
IP Multicast
IP 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 Protocols
The 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
9-20
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 9
Configuring MPLS Features
Multicast VPN
•
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)
•
PIM Dense-Mode:
Multicast Modes
– 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 Multicast
Source 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
9-21
Chapter 9
Configuring MPLS Features
Multicast VPN
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 Operation
The 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.
9-22
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 9
Configuring MPLS Features
Multicast VPN
VRF Configuration Example
ip 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 tunnel0
Tunnel0 is up, line protocol is up
Hardware 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 interface
Address
Interface
Ver/ Nbr
Query DR
DR
Mode
Count Intvl Prior
156.1.1.10
Switch1.56
v2/SD 1
30
1
0.0.0.0
10.10.10.10
Tunnel0
v2/SD 2
30
1 10.10.10.10
PE 1#sh ip mroute
IP 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,
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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
9-23
Chapter 9
Configuring MPLS Features
MPLS LDP
MPLS LDP
MPLS 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.
Support for Multi-VC on the RPM-XF
This 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.
9-24
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 9
Configuring MPLS Features
Support for Multi-VC on the RPM-XF
Configuring Multi-VC on the RPM-XF eLSR
Figure 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.
PXF queues for mpls
bit to COS
Class of Services
LVCs
In: map IP precedence
Cos0 10% + 10% Cos0
Cos1
bit to mpls exp. bit
Cos2 10% + 10% Cos1
Cos3
int
sw
1.11
Traffic for
or one IP dest. prefix
mpls
(to LSC-5)
int sw 1.15
mpls
(to LSC-9)
Incoming unlabeled IP traffic
Note
Cos0 10% + 10% Cos2 int sw
w1
Cos1
Cos2
Cos3 20% + 20% Cos3
Outgoing labeled mpls traffic
80214
int PCS 1/0
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
match ip precedence
class-map match-all
match ip precedence
class-map match-all
match ip precedence
IP_PREC0
0 4
IP_PREC1
1 5
IP_PREC2
2 6
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
9-25
Chapter 9
Configuring MPLS Features
Support for Multi-VC on the RPM-XF
class-map match-all IP_PREC3
match 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_EXP0
class IP_PREC0
set mpls experimental 0
policy-map set_EXP1
class IP_PREC1
set mpls experimental 1
policy-map set_EXP2
class IP_PREC2
set mpls experimental 2
policy-map set_EXP3
class IP_PREC3
set mpls experimental 3
!
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
!
interface Switch1
no ip address
switch 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 mpls
ip unnumbered Loopback1
service-policy output COS_0123
mpls ip
mpls atm switch-partition 8
mpls atm multi-vc
mpls atm control-vc 140 32
mpls 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 4
class-map match-all IP_PREC1
match ip precedence 1 5
class-map match-all IP_PREC2
9-26
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 9
Configuring MPLS Features
Support for Multi-VC on the RPM-XF
match ip precedence 2 6
class-map match-all IP_PREC3
match ip precedence 3 7
!
policy-map set_EXP0123
class IP_PREC0
set mpls experimental
class IP_PREC1
set mpls experimental
class IP_PREC2
set mpls experimental
class IP_PREC3
set mpls experimental
!
0
1
2
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
class-map match-all COS_1
match mpls experimental
class-map match-all COS_2
match mpls experimental
class-map match-all COS_3
match mpls experimental
!
policy-map COS_0123
class COS_0
bandwidth percent
class COS_1
bandwidth percent
class COS_2
bandwidth percent
class COS_3
bandwidth percent
!
0 4
1 5
2 6
3 7
20
20
20
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
9-27
Chapter 9
Configuring MPLS Features
Support for Multi-VC on the RPM-XF
9-28
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
C H A P T E R
10
Configuring 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
•
MultiLink PPP/Link Fragmentation Interleaving
•
Configuring Internet Protocol Header Compression
•
Enabling IP Radio Access Network
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-1
Chapter 10
Configuring Quality of Service
General QoS Configuration Procedure
•
Set specifies an IP precedence/DSCP or MPLS experimental value that can be used by other routers
to manage QoS.
•
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 Procedure
You 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
RPM-XF
Packet
Service-policy command
applies a class-map and
policy-map to a specific
interface.
Class-map commands
tell the router how to
recognize a packet that
is subject to QoS. For
example, watch for a
packet associated with
a specific access list.
Pack
et
Packet
75647
Packet
Policy-map commands
tell the router what to
do with a packet. For
example, drop the
packet or let it through.
10-2
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
General QoS Configuration Procedure
Creating a QoS Boilerplate
This 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 mink
Router(config-cmap)#
As the example shows, after you enter the class-map name command, you enter class map configuration
mode (config-cmap).
Note
Step 2
Some Cisco IOS documents refer to the QoS configuration modes as the modular CLI.
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)# exit
Router(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 lynx
Router(config-pmap)#
As the example shows, after you enter the policy-map name command, you enter policy map
configuration mode (config-pmap).
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-3
Chapter 10
Configuring Quality of Service
Class Map Commands
Step 2
Associate the policy map with a class map.
Router(config-pmap)# class mink
Router(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)# exit
Router(config-pmap)# exit
Router(config)#
You have completed the creation of a QoS boilerplate, which can be assigned to an interface.
Assigning a QoS Boilerplate to an Interface
Use 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/0
Router(config-if)# service-policy input lynx
Class Map Commands
This 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 Map
You 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
10-4
Parameter
Description
match-any
A single match rule is sufficient for class membership.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
Class Map Commands
Parameter
Description
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.
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 mink
Router(config-cmap)#
Matching Attributes
Use 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-5
Chapter 10
Configuring Quality of Service
Policy 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 mink
Router(config-cmap)# match access-group 1
Router(config-cmap)# match ip precedence 3 7
Policy Map Commands
This 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 Map
You 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 lynx
Router(config-pmap)#
Assigning a Class to a Policy Map
Use 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.
10-6
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
Policy Map Commands
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 lynx
Router(config-pmap)# class mink
Router(config-pmap-c)#
In the following example, the default class map is assigned to the policy map named lynx.
Router(config)# policy-map lynx
Router(config-pmap)# class class-default
Router(config-pmap-c)#
Specifying a Committed Access Rate
To specify a committed access rate, 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.
You can specify the rate commitment as either a bit rate or as a percentage of the bandwidth. When using
the IP-RAN feature, always specify a CIR percentage so you can take advantage of the dynamic
bandwidth feature. For more information, see the “Enabling IP Radio Access Network” section on
page 10-25. The following command summaries show the two command forms.
police bps [burst-normal] [burst-max] [conform-action action exceed-action action]
police cir percent percent [bc conform-burst-in-msec] [be peak-burst-in-msec]
[conform-action action exceed-action action]
no police
Note
The RPM-XF does not support the pir percent or violate-action keywords for the police command.
Parameter
Description
bps
Average rate in bits per second. Valid values are 8000 to 200000000.
normal-burst
(Optional) Normal burst size in bytes. Valid values are 1000 to
51200000. The default normal burst size is 1500 bytes.
max-burst
(Optional) Excess burst size in bytes. Valid values are 1,000 to
51200000.
conform-action action
Indicates the action that should be taken if the rate or percent 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 or percent is
exceeded.
See Table 10-1 for a list of actions.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-7
Chapter 10
Configuring Quality of Service
Policy Map Commands
Parameter
Description
cir
Committed information rate (CIR). Indicates that the CIR will be used
for policing traffic.
percent
Specifies that percent of bandwidth will be used for calculating the CIR.
percent
Specifies the bandwidth percentage. Valid range is a number from 1
to 100.
bc
(Optional) Conform burst (bc) size used by the first token bucket for
policing traffic.
conform-burst-in-msec
(Optional) Specifies the bc value in milliseconds (ms). Valid range is a
number from 1 to 2000.
Table 10-1
CAR Actions
Action
Description
drop
Drop all matched traffic.
set-clp-transmit value
Set the ATM Cell Loss Priority (CLP) bit from 0 to 1 on the ATM cell and
transmits the packet with the ATM CLP bit set to 1.
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.
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.
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 lynx
Router(config-pmap)# class mink
Router(config-pmap-c)# police 720000 90000 90000 conform-action transmit exceed-action
drop
Enabling Weighted Random Early Detection
Use 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.
10-8
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
Policy Map Commands
Note
The bandwidth must be set before you can enable WRED (see Bandwidth Reservation and Low-Latency
Priority Queueing, page 10-10).
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]
Parameter
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.
prec
Tip
•
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.
Specify the precedence values according to the information in the following table.
In most cases, the benefits of WRED can be best realized if you use the random-detect keyword without
arguments.
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.
Use the no form of the command to disable WRED.
The following example shows the implementation of WRED.
Router(config)# policy-map lynx
Router(config-pmap)# class class-default
Router(config-pmap-c)# random-detect
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-9
Chapter 10
Configuring Quality of Service
Policy Map Commands
Bandwidth Reservation and Low-Latency Priority Queueing
This 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
[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# enable
Router# configure terminal
Router(config)# class-map city
Router(config-cmap)# match ip precedence 1 2 3 4
Router(config-cmap)# class-map boston
Router(config-cmap)# match ip precedence 5 6 7
Router(config-cmap)# policy-map precedence-queues
Router(config-pmap)# class city
Router(config-pmap-c)# bandwidth 16
Router(config-pmap-c)# class boston
Router(config-pmap-c)# bandwidth 40
Router(config-pmap-c)# interface switch1:1
Router(config-if)# service-policy output precedence-queues
Router(config-if)# end
10-10
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
Policy Map Commands
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# enable
Router# configure terminal
Router(config)# class-map voice
Router(config-cmap)# match ip rtp 2000 2000
Router(config-cmap)# policy-map voice-queue
Router(config-pmap)# class voice
Router(config-pmap-c)# priority 56
Router(config-pmap-c)# interface switch1:1
Router(config-if)# service-policy output voice-queue
Router(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 Shaping
The 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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-11
Chapter 10
Configuring Quality of Service
Policy Map Commands
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 100
Router(config-pmap-c)#
Specifying a Queue Limit
This 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 lynx
Router(config-pmap)# class class-default
Router(config-pmap-c)# queue-limit 256
Applying Set Values
The 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.
10-12
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
Service-Policy Command
Parameter
Description
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.
Internally visible values are the following.
Parameter
Description
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.
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
Router(config-pmap)# class
Router(config-pmap-c)# set
Router(config-pmap-c)# set
lynx
mink
ip precedence 7
qos-group 8
Service-Policy Command
To associate a policy map with an interface, use the service-policy command.
service-policy [input | output] name
[no] service-policy [input | output] name
Parameter
Description
input
Incoming traffic on an interface.
output
Outgoing traffic on an interface.
name
Name of a policy map.
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-13
Chapter 10
Configuring Quality of Service
Show Commands
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/0
Router(config-if)# service-policy input lynx
In the following example, a policy map is applied to an ATM PVC.
Router(config)# interface switch1.1
Router(config-if)# pvc 0/101
Router(config-if-atm-vc)# service-policy input lynx
Show Commands
This section lists show commands you can use to get information about class maps and policy maps.
show policy map
This 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
10-14
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
Quality of Service Policy Propagation Example Using Border Gateway Protocol
show policy-map interface
This 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-map
This 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)
show vlans
This command can list up to 1000 virtual LAN subinterfaces. For example,
Router# show vlans
Virtual LAN ID: 1 (IEEE 802.1Q Encapsulation)
VLAN Trunk Interface: GigabitEthernet1/0
Protocols Configured: Address:
Received:
IP
200.1.1.1
18
Transmitted:
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-15
Chapter 10
Configuring Quality of Service
Quality of Service Policy Propagation Example Using Border Gateway Protocol
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).
RPM-XF Routes and QoS Policy Application
1. Route announced
2. Route arrives
3. QoS policy applied
RPM-XF
Autonomous
system 60
Router
B
Autonomous
system 30
Autonomous
75648
Figure 10-2
system 10
4. Packet sent with QoS policy
RPM-XF Configuration
Router(config)# router bgp 30
Router(config)# table-map precedence-map
Router(config-router)# neighbor 20.20.20.1 remote-as 10
Router(config-router)# neighbor 20.20.20.1 send-community
Router(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 10
Router(config-route-ma)# match community 1
Router(config-route-ma)# set ip precedence priority
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 20
Router(config-route-ma)# match community 2
Router(config-route-ma)# set ip precedence immediate
Match community 3 and set the IP precedence to Flash.
Router(config)# route-map precedence-map permit 30
Router(config-route-ma)# match community 3
Router(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 40
Router(config-route-ma)# match community 4
Router(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 50
Router(config-route-ma)# match community 5
Router(config-route-ma)# set ip precedence critical
Match community 6 and set the IP precedence to internet.
Router(config)# route-map precedence-map permit 60
Router(config-route-ma)# match community 6
Router(config-route-ma)# set ip precedence internet
10-16
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
Quality of Service Policy Propagation Example Using Border Gateway Protocol
Match community 7 and set the IP precedence to network.
Router(config)# route-map precedence-map permit 70
Router(config-route-ma)# match community 7
Router(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 75
Router(config-route-ma)# match ip address 69
Router(config-route-ma)# match as-path 1
Router(config-route-ma)# set ip precedence critical
Router(config-route-ma)# set ip qos-group 9
For everything else, set the IP precedence to routine.
Router(config)# route-map precedence-map permit 80
Router(config-route-ma)# set ip precedence routine
Define the community lists.
Router(config)#
Router(config)#
Router(config)#
Router(config)#
Router(config)#
Router(config)#
Router(config)#
ip
ip
ip
ip
ip
ip
ip
community-list
community-list
community-list
community-list
community-list
community-list
community-list
1
2
3
4
5
6
7
permit
permit
permit
permit
permit
permit
permit
60:1
60:2
60:3
60:4
60:5
60:6
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 Configuration
RouterB(config)# router bgp 10
RouterB(config-router)# neighbor 30.30.30.1 remote-as 30
RouterB(config-router)# neighbor 30.30.30.1 send-community
RouterB(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 10
RouterB(config-route-ma)# match ip address 10
RouterB(config-route-ma)# set community 60:1
Match prefix 20 and set community to 60:2.
RouterB(config)# route-map send_community permit 20
RouterB(config-route-ma)# match ip address 20
RouterB(config-route-ma)# set community 60:2
Match prefix 30 and set community to 60:3.
RouterB(config)# route-map send_community permit 30
RouterB(config-route-ma)# match ip address 30
RouterB(config-route-ma)# set community 60:3
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-17
Chapter 10
Configuring Quality of Service
Versatile Traffic Management System
Match prefix 40 and set community to 60:4.
RouterB(config)# route-map send_community permit 40
RouterB(config-route-ma)# match ip address 40
RouterB(config-route-ma)# set community 60:4
Match prefix 50 and set community to 60:5.
RouterB(config)# route-map send_community permit 50
RouterB(config-route-ma)# match ip address 50
RouterB(config-route-ma)# set community 60:5
Match prefix 60 and set community to 60:6.
RouterB(config)# route-map send_community permit 60
RouterB(config-route-ma)# match ip address 60
RouterB(config-route-ma)# set community 60:6
Match prefix 70 and set community to 60:7.
RouterB(config)# route-map send_community permit 70
RouterB(config-route-ma)# match ip address 70
RouterB(config-route-ma)# set community 60:7
For all others, set community to 60:8.
RouterB(config)# route-map send_community permit 80
RouterB(config-route-ma)# set community 60:8
Define the access lists.
RouterB(config)#
RouterB(config)#
RouterB(config)#
RouterB(config)#
RouterB(config)#
RouterB(config)#
RouterB(config)#
access-list
access-list
access-list
access-list
access-list
access-list
access-list
10
20
30
40
50
60
70
permit
permit
permit
permit
permit
permit
permit
61.0.0.0
62.0.0.0
63.0.0.0
64.0.0.0
65.0.0.0
66.0.0.0
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.1
ip address 200.28.38.2 255.255.255.0
bgp-policy source ip-prec-map
no ip mroute-cache
no cdp enable
frame-relay interface-dlci 20 IETF
interface switch1.2
ip address 200.28.28.2 255.255.255.0
bgp-policy source qos-group
no ip mroute-cache
no cdp enable
Versatile Traffic Management System
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.
10-18
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
Versatile Traffic Management System
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 Management
In 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
•
pool 1: 4672 bytes–total 500
•
pool 2: 1600 bytes–total 30000
•
pool 3: 640 bytes–total 67671
•
pool 4: 256 bytes–total 98173
•
pool 5: 64 bytes–total 131000
Buffer Management CLI Commands
show pxf cpu buffers
show pxf cpu buffers leaked <pool no>
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-19
Chapter 10
Configuring Quality of Service
MultiLink PPP/Link Fragmentation Interleaving
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
show
show
show
pxf
pxf
pxf
pxf
cpu
cpu
cpu
cpu
queue <interface> - summarized info
queue <qid> - detailed info including CIR, MIR, EIR, stats, etc.
statistics qos <interface>
police <policy map>
MultiLink PPP/Link Fragmentation Interleaving
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.
10-20
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
MultiLink PPP/Link Fragmentation Interleaving
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 Configuration
The following configuration commands can be used to configure MLP/LFI:
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.
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
pvc toortr01 0/58
vbr-nrt 406 406
protocol ppp Virtual-Template15
interface Virtual-Template15
bandwidth 320
ip address 10.16.0.105 255.255.255.252
ip tcp header-compression iphc-format
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-21
Chapter 10
Configuring Quality of Service
Configuring Internet Protocol Header Compression
service-policy output VOIP_PRI
ppp multilink
ppp multilink fragment-delay 14
ppp multilink interleave
ip rtp header-compression iphc-format
Configuring Internet Protocol Header Compression
Internet Protocol Header Compression (IPHC) increases the bandwidth utilization of PPP links when IP
headers are extremely large or when the header and payload sizes are similar. PPP link utilization is
important because it directly affects the number of calls that an aggregation node can handle. IPHC
supports compressed Real Time Protocol (cRTP), compressed User Datagram Protocol (cUDP), and
compressed Transport Control Protocol (cTCP).
The RPM-XF compresses IP datagrams on multi-link PPP or PPPoATM PVCs towards the endpoint
router, and each PVC supports multiple IPHC data flows. Each flow represents a unique combination of
IP/UDP headers. The RPM-XF supports 1000 flows per PVC and 200 PVCs per card. Inactive flows are
released after a configurable timeout.
IPHC Configuration
An IHC-enabled flow sends the first packet with a full header, which is a special form of the normal
IP+UDP and IPHC header. Subsequent packets are compressed using the cUDP or cRTP protocol, which
replaces full headers with deltas for the IP/UDP/RTP header fields that differ from the full header, such
as IPID, RTP Sequence, and RTP timestamp. Each of the deltas can be zero or non-zero, where zero
indicates no header change. Packets with zero deltas contain just the essential fields and are of the
smallest possible size. Packets with non-zero deltas vary in size depending on the number of deltas and
the delta values themselves. The decompressor maintains a copy of the original full header and
reconstructs packet headers. You can configure IPHC as follows:
•
Compressed packet with IPID delta (normal compression with all deltas)
When the decompressor receives a compressed packet with IPID delta, it reconstructs the packet
header by adding the deltas to the respective fields of the saved uncompressed header. In the typical
case, IPHC compresses the header to 2-5 bytes if 8-bit compression is used (add 1 additional byte if
16 bit compression is used and another 2 bytes if UDP checksum is present) for cUDP and 2-8 bytes
if 8-bit compression is used (add 1 additional byte if 16 bit compression is used and another 2 bytes
if UDP checksum is present) for cRTP.
Use the ip rtp header-compression iphc-format command to enable this feature.
•
Compressed packet without IPID delta (cUDP without IPID delta)
When the decompressor receives a compressed packet, it reconstructs the packet using stored header
information in the same way as described above, except that because the compressor does not
encode the IPID delta, the delta is assumed to be 0 and the integrity of the IPID field is not
guaranteed.
Use the ip rtp header-compression iphc-format and hw-module rpm ipran commands to enable
this feature. For more information, see Configuring the RPM-XF for IP-RAN, page 10-28.
Note
10-22
This feature is an IPHC enhancement that is enabled only when IP-RAN is enabled. If IP-RAN
is disabled, IPHC uses normal compression.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
Configuring Internet Protocol Header Compression
Note
RPM-XF supports TCP decompression, but not TCP compression; TCP packets are always 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. Avoid carrying TCP traffic on an IPHC enabled
interface, especially if the customer edge router can NOT stop TCP compression selectively.
Compression Configuration
By default, the cRTP protocol compresses all UDP and RTP packets. For those networks where
compression of UDP packets apart from RTP is undesirable, you can selectively disable UDP
compression. Use the hw-module rpm udp-comp command to enable or disable UDP compression
when cRTP is enabled.
Note
You cannot disable UDP compression when IP-RAN is enabled; IP-RAN only compresses cUDP
packets.
IPHC Command Summary
The following CLI commands support IPHC:
Table 10-2
Configuration Commands
Command
Description
clear ip rtp
header-compression
Reset cRTP/cUDP statistics for the interface to zero.
clear ip tcp
header-compression
Reset TCP decompression statistics for the interface.
hw-module rpm udp-comp
Enable UDP header compression. The no version of this command
disables UDP compression. By default, cUDP is enabled when
cRTP is enabled.
ip rtp
compression-connections
<number>
Specifies the total number of cRTP/cUDP header compression
connections supported on the interface. The default is 16. The
maximum is 1000. The no version of this command restores the
default—16.
ip rtp header-compression
iphc-format
Enable cRTP/cUDP header compression using iphc-format on an
interface. The no version of this command disables header
compression.
ppp iphc max-time
Set the timeout value for IPHC flows. The default time is 5 seconds.
The no version of this command restores the default timeout.
show pxf cpu queue <qid>
Use the dedicated Queue ID (qid) for cTCP queue.
show pxf cpu queue RP
Show the cTCP packets punted to the route processor.
show 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-23
Chapter 10
Configuring Quality of Service
Configuring Internet Protocol Header Compression
Table 10-2
Configuration Commands
Command
Description
show int <interface>
rpmxf-iphc-db
Show interface IPHC database for debugging.
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.
The show ip rtp header-compression and show ip tcp header-compression commands display the
following IPHC statistics:
Table 10-3
IPHC Statistics
Statistic
Description
Rcvd:
total
Total packets processed by the decompressor.
compressed
Compressed cRTP/cUDP packets received.
status msgs
Context status messages received. This is sent by the decompressor when the
compressed packet sequence number contained in its header is different from the one
expected by the de-compressor. Also sent when the flow has timed out on the
de-compressor and the compressor has not sent a full-header in response to the
timeout.
dropped
Indicates the number of compressed packets that were dropped because of errors.
Sent:
total
Total packets processed by the compressor.
compressed
Compressed cRTP/cUDP 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/cUDP connections on the virtual-access interface. This
number represents the final negotiated value for either PPPoATM or Multi-link PPP.
10-24
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
Enabling IP Radio Access Network
IPHC Examples
The following examples display IPHC information.
show pxf cpu statistics crtp [interface]
Interface Virtual-Access3:
Rcvd: compressed : 0 pkts
fullheader : 0 pkts
dropped
: 0 pkts
cs (status) : 0 pkts
Sent: compressed : 0 pkts
fullheader : 0 pkts
uncompressed: 0 pkts
cs (status) : 0 pkts
Collisions
: 0 pkts
Punted to RP
: 0 pkts
Compressed TCP in : 0 pkts
Max CID
: 1000
Cids in use
: 0
Timeout (compr)
: 9
Timeout (decompr) : 8
/ 0 bytes
/ 0 bytes
/ 0 bytes
/ 0 bytes
/ 0 bytes
(IP Options/RTP ext/CSRC)
show int <interface> rpmxf-iphc-db
Interface : Virtual-Access3
IPHC enabled: yes IPHC id: 1 vcci: 15 states: 0 hashMask: 0x3E8
Tx stats in shadow memory:
compressedout
:pkts = 0 , bytes
uncompressedout
:pkts = 0 , bytes
fullheaderout
:pkts = 0 , bytes
cs_packet_rcvd 0 num_cid_collisions
= 0
= 0
= 0
0
Rx stats in shadow memory:
compressedin
:pkts = 0 , bytes = 0
fullheaderin
:pkts = 0 , bytes = 0
compressed_tcp_in :pkts = 0
cs_packet_sent 0 punted(IP options/RTP ext/CSRC list) 0
tossed packets(bad CRC) 0
IPHC enabled on PXF(read from PXF): yes
Enabling IP Radio Access Network
IP Radio Access Network (IP-RAN) is a collection of features that optimize IP communications for the
radio access network. IP-RAN has the following features:
•
Disable sending IP ID field delta in IPHC packet flows
•
Suppress CS packet for cUDP sequence number mismatch
•
Flow expiration timer
•
cUDP compression only
•
Dynamic bandwidth negotiation
These features primarily optimize bandwidth utilization for the radio access network. This is important
for voice traffic over WAN links, such as T1/E1 lines, where cost is a significant factor.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-25
Chapter 10
Configuring Quality of Service
Enabling IP Radio Access Network
IPPRAN Command Summary
The following CLI commands support IP-RAN:
Table 10-4
IP-RAN Configuration Commands
Command
Description
hw-module rpm ipran
Enable IP-RAN features. The no version of this command disables
IP-RAN.
ppp iphc max-time
Set the timeout value for IPHC flows. The no version of this
command restores the default timeout. This is a generic feature that
applies to all IPHC flows, not just IP-RAN.
show rpm ipran
Display IP-RAN operational status, which is either enabled or
disabled.
show ip rtp
header-compression
virtual-access
Display header compression statistics.
hw-module rpm ipran
To enable IP Radio Access Network (IP-RAN) features on a Route Processor Module (RPM-XF), use
the hw-module rpm ipran command in global configuration mode. To disable IP-RAN, use the no form
of this command.
hw-module rpm ipran
no hw-module rpm ipran
This command enables IP-RAN features on an RPM-XF card. These features optimize multi-link PPP
connections through the MPSM to help fully utilize radio access networks.
ppp iphc max-time
To specify the maximum amount of time to wait before expiring an IPHC flow, use the ppp iphc
max-time command in interface configuration mode. To return to the default value, use the no form of
this command.
ppp iphc max-time length-of-time
no ppp iphc max-time
length-of-time
10-26
Specifies the number of seconds to wait before expiring an IPCH flow. The
amount of time can be in the range of 0 to 255 seconds. The default value is 5
seconds.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
Enabling IP Radio Access Network
The ppp iphc max-time command can improve IPHC performance by expiring the flow context ID for
flows that have become idle. If there has been no activity on a flow for length-of-time, the flow context
ID can be reused by a new flow. This command applies to all IPHC flows, not just the IP-RAN solution.
This command implements the same functionality as the ip header-compression max-time command.
show rpm ipran
To display the operational status of the IP Radio Access Network (IP-RAN) feature, use the show rpm
ipran command in privileged EXEC mode.
show rpm ipran
This command displays the operational status of IP-RAN, which is either enabled or disabled.
show ip rtp header-compression
To display Compressed Real-Time Transport Protocol (CRTP) statistics, use the show ip rtp
header-compression command in privileged EXEC mode.
show ip rtp header-compression [detail] [interface-type interface-number]
detail
(Optional) Displays details of each connection.
interface-type
interface-number
(Optional) The interface type and number. For the RPM-XF, enter
virtual-access and the interface number.
Enter this command to retrieve information regarding RTP header compression on a specific interface.
When you specify the detail keyword, the following information is displayed.
Table 10-5
Virtual-Access Statistics
Statistic
Description
Max Header
The maximum size of the full header that can be sent on the link. A full header is the
IP packet sent out uncompressed. It contains additional information, like Context ID
used for the flow. Not supported on the RPM-XF.
Max Time
The maximum time between sending of full headers for a particular flow. After this
time a full-header must be sent out for the flow. Not supported on the RPM-XF.
Max Period
The maximum number of compressed packets after which a full header must be sent
for a particular flow. Not supported on the RPM-XF.
Feedback
Enable sending and receiving of CS packets - CS packets are used as a feedback
mechanism by the decompressor to inform the compressor about packet loss.
Tx Context
The number of flows currently in use for the Tx direction.
Rx Context
The number of flows currently in use for the Rx direction.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-27
Chapter 10
Configuring Quality of Service
Enabling IP Radio Access Network
Configuring IP-RAN
The IP-RAN solution utilizes the RPM-XF and MPSM cards. The MPSM card connects the RPM-XF
router to access routers over MLPPP (Multilink PPP) links (see Figure 10-3IP-RAN Solution).
IP-RAN Solution
IP Access
T1/E1 Links
ATM PVC
MPSM
Line
Side
PPPMux
PPPMux
MLPPP
PPP
Switch
Side
PPP
PPPoATM
IP Core
RPM-XF
PPPoATM
MLPPP
Data Protocols
122946
Figure 10-3
The connection between the MPSM and RPM-XF is an ATM PVC that uses PPPoATM encapsulation.
To create the slave connection at the RPM-XF, you need bandwidth information for the MLPPP bundle.
To create the master connection at the MPSM, you need the NSAP address and VPI/VCI used at the
RPM.
This section explains the RPM-XF configuration procedure in detail, and summarizes the MPSM
configuration procedure.
Configuring the RPM-XF for IP-RAN
IP-RAN configuration includes the following tasks:
•
Define QoS Service Policy
•
Enable and Configure IP-RAN
•
Configure PVC
Define QoS Service Policy
To define the QoS service policy, perform the following steps:
Step 1
Define QoS classes for the data types in your network. The following example shows typical definitions
for voice and data classes.
Router(config)# class-map <data>
Router(config-cmap)# match ip precedence <0>
Router(config-cmap)# class-map <voice>
Router(config-cmap)# match ip precedence <1>
10-28
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
Enabling IP Radio Access Network
Step 2
Configure a policy map. Specify class bandwidths as a percentage to fully utilize the dynamic bandwidth
feature. The following example shows a typical policy.
Router(config)# policy-map <ipran-policy-name>
Router(config-pmap)# class <voice>
Router(config-pmap-c)# priority
Router(config-pmap-c)# police cir percent <1-100>
Router(config-pmap)# class <data>
Router(config-pmap-c)# bandwidth percent <1-100>
Enable and Configure IP-RAN
To enable and configure IP-RAN, perform the following steps:
Step 1
Enable IP-RAN feature set.
Router(config)# hw-module rpm ipran
Step 2
Configure virtual templates for PVC endpoints. These templates enable and configure IPHC.
Router(config)# interface VirtualTemplate <1>
Router(config-if)# ip address <address> <mask>
Router(config-if)# ip tcp header-compression iphc-format
Router(config-if)# ppp iphc max-time <1-255>
Router(config-if)# ip rtp header-compression iphc-format
Router(config-if)# ip rtp compression-connections <1-1000>
Step 3
Configure Switch1 for SAR-based QoS. The dynamic bandwidth feature requires this mode.
Router(config)# interface Switch1
Router(config-if)# atm sar-based-cbwfq
Configure PVC
For the IP-RAN solution, you connect the RPM-XF to the MPSM-16-T1E1 with a PVC. When IP-RAN
is enabled, the following PVC restrictions apply:
•
Cisco PPP over AAL5 encapsulation is compatible with the MPSM-16-T1E1 card only. To use Cisco
PPP over AAL5 encapsulation with FRSM or MPSM(ASAP) cards, disable IP-RAN.
•
The PVCs cannot be configured for MLP-LFI.
•
The dynamic bandwidth feature applies to all PVC slave endpoints on the RPM-XF
•
The service policy that is attached to the PVC must have bandwidths configured as a percent, rather
than an absolute value.
To create a PVC between the RPM-XF and MPSM-16-T1E1 for the IP-RAN solution, perform the
following steps:
Step 1
Create a point-to-point subinterface on Switch1. The RPM-XF routes traffic to the endpoint routers
through this interface.
Router(config)# interface Switch1.1 point-to-point
Step 2
Add and configure a PVC on this subinterface. Configure the service type as either vbr-rt or vbr-nrt,
and specify bandwidth (PCR and SCR) and burst size (MBS) of the corresponding MLPPP bundle.
Apply Cisco PPP over AAL5 encapsulation and the appropriate virtual template. Finally, apply the
policy-map created in the “Define QoS Service Policy” section on page 10-28.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-29
Chapter 10
Configuring Quality of Service
Enabling IP Radio Access Network
Router(config-subif)# pvc
Router(config-if-atm-vc)#
Router(config-if-atm-vc)#
Router(config-if-atm-vc)#
Step 3
<vpi/vci>
vbr-nrt <pcr> <scr> <mbs>
encapsulation aal5ciscoppp Virtual-Template<1>
service-policy output <ipran-policy-name>
Create a slave connection endpoint and display its information.
Router(config-subif)# switch connection vcc <vpi> <vci> master remote
Router# show switch connection vcc <vpi> <vci>
---------------------------------------------------------Alarm state
: No alarm
Local Sub-Interface
: 1
Local VPI
: 0
Local VCI
: 101
Remote NSAP address
: default
Local NSAP address
: 47.009181000000000164444B61.000001011802.00
Remote VPI
: 0
Remote VCI
: 0
Routing Priority
: N/A
Max Cost
: N/A
Preferred Route Id
: N/A
Directed Route
: N/A
Percent Util
: 100
Remote PCR
: 34400
Remote SCR
: 34400
Remote MBS
: 1024
Local PCR
: 34400
Local SCR
: 34400
Remote Percent Util
: 100
Connection Master
: Remote
Slave type
: N/A
Synch Status
: inSynch
Auto Synch
: OFF
Admin Status
: UP
Conn-Id
: 0
Update Count
: 140840001
Step 4
Record the local NSAP address, VPI, VCI, remote PCR and remote SCR values (shown in bold); you
will need these to add an endpoint at the MPSM.
Step 5
Add the MPSM connection for this PVC. For more information, see “Configuring the MPSM Card for
IP-RAN” section on page 10-31.
Step 6
Open a management session to the PXM card and verify the connection.
MGX.PXM> dspcons
Local Port
Vpi.Vci
Remote Port Vpi.Vci
State
Owner Pri Persisteny
----------------------+------------------------+---------+-------+---+---------1:1.2:2
0 101
27.65535
8 1000
OK
SLAVE Persistent
Local Addr: 47.009181000000000164444b61.000001011802.00
Remote Addr: 47.009181000000000164444b61.0000011b1fff.00
Preferred Route ID:Cast Type: P2P
Viewing Status
To view IP-RAN status, use the show rpm ipran command and to view IP-RAN statistics use the show
ip rtp header-compression virtual-access command, specifying the virtual-access interface for the
IP-RAN connection.
10-30
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
Enabling IP Radio Access Network
Configuring the MPSM Card for IP-RAN
This section contains a Quickstart for configuring lines, bundles, and connections on the MPSM-16T1E1
card. For complete configuration information, see the “Adding a Connection to an MP Bundle for the
IP-RAN Solution” section in the Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and
MPSM-16T1E1) Configuration Guide and Command Reference for MGX Switches, Release 5.1 book.
Command
Comments
Step 1
Establish a configuration session with
the MPSM card.
Use a user name with GROUP 1 privileges or higher.
Step 2
addmpbundle
Add a bundle.
Step 3
addppplink
Add PPP links to the bundle.
Step 4
addpppmux
Add PPPMux to the bundle.
Step 5
addcon
Connect bundle to RPM-XF
Table 10-6 describes the parameters of the addcon command
that apply to IP-RAN PVCs.
Step 6
dspcon
Display connection information.
Table 10-6 describes the addcon command arguments for an adding a master connection at the MPSM.
The remaining addcon arguments are unused for MLPPP connections.
Table 10-6
addcon Command Parameters for the IP-RAN Solution
Parameter
Description
ifnum
Identifies the logical interface on the local end of the connection you want
to configure, range 1-16.
dlci
Identifies the Data Link Connection Identifier (DLCI) value. Use a value of
1000 for all IP-RAN connections.
chanType
Use a value of 5 to specify a frame-forwarding channel type.
serviceType
Identifies the ATM service type of the connection. For IP-RAN connections,
only rtVBR and nrtVBR is supported. Select one of the following only:
•
2 = rtVBR
•
3 = nrtVBR
mastership
Mastership role of the connection. When adding IP-RAN connections, the
master side of the connection is provisioned on the MPSM card and the slave
side of the connection is provisioned on the RPM-XF side. Use a value of 1
to select master.
cir
Committed Information Rate (in bits per second). Range: 0–1984001. Set
this to the bundle bandwidth on the MPSM.
-slave
Slave-end connection identifier of the RPM-XF endpoint of the connection
in the format nsap_address.vpi.vci. To find the NSAP address use the
RPM-XF show switch connection vcc <vpi> <vci> command. Remove all
the decimal points from the NSAP address and then append the vpi and vci
of the RPM-XF connection endpoint, separated by decimal points.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-31
Chapter 10
Configuring Quality of Service
Enabling IP Radio Access Network
Table 10-6
addcon Command Parameters for the IP-RAN Solution (continued)
Parameter
Description
-lpcr
Local PCR. Range: 10–104268 cells per second. Set this to the rpcr cell rate
of the RPM-XF slave connection. See Configure PVC, page 10-29.
-lscr
Local SCR. Range: 10–104268 cells per second. Set this to the rscr cell rate
of the RPM-XF slave connection. See Configure PVC, page 10-29.
IP-RAN Examples
The following examples show a typical IP-RAN configuration.
Configuration Example
The following example enables IP-RAN and configures associated QoS and switch parameters.
Router> enable
Router# configure terminal
Router(config)# hw-module rpm ipran
Configure Layer 3 QoS, specifying bandwidths as a percentage only. For more information see the
“Class Map Commands” section on page 10-4 and the “Policy Map Commands” section on page 10-6.
Router(config)# class-map data
Router(config-cmap)# match ip precedence 0
Router(config-cmap)# class-map voice
Router(config-cmap)# match ip precedence 1
Router(config)# policy-map foo
Router(config-pmap)# class voice
Router(config-pmap-c)# priority
Router(config-pmap-c)# police cir percent 50
Router(config-pmap-c-police)# conform-action transmit
Router(config-pmap-c-police)# exceed-action drop
Router(config-pmap-c-police)# class data
Router(config-pmap-c)# bandwidth percent 35
Router(config-pmap-c)# class class-default
Router(config-pmap-c)# bandwidth percent 15
Configure a virtual template that defines IPHC settings.
Router(config)# interface Virtual-Template1
Router(config-if)# ip address 192.168.1.1 255.255.255.0
Router(config-if)# ip tcp header-compression iphc-format
Router(config-if)# ip ospf hello-interval 1
Router(config-if)# ip ospf dead-interval 3
Router(config-if)# keepalive 1
Router(config-if)# ppp timeout retry 1
Router(config-if)# ppp iphc max-time 8
Router(config-if)# ip rtp header-compression iphc-format
Router(config-if)# ip rtp compression-connections 1000
Configure switch for SAR-based QoS.
Router(config-if)# interface Switch1
Router(config-if)# atm sar-based-cbwfq
10-32
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Chapter 10
Configuring Quality of Service
Enabling IP Radio Access Network
Configure sub interface and PVC. The bundle bandwidth in this example is 6,144.000 bps.
Router(config-if)# interface Switch1.1 point-to-point
Router(config-subif)# pvc 0/101
Router(config-if-atm-vc)# encapsulation aal5ciscoppp Virtual-Template1
Router(config-if-atm-vc)# vbr-nrt 6144 6144 1024
Router(config-if-atm-vc)# service-policy output foo
Router(config-if-atm-vc)# switch connection vcc 0 101 master remote
Display Example
Router# show ip rtp header-compression virtual-access 1 detail
RTP/UDP/IP header compression statistics:
Configured:
Max Header 168 Bytes, Max Time 5 Secs, Max Period 256 Packets, Feedback On
Negotiated:
Max Header 168 Bytes, Max Time 5 Secs, Max Period 256 Packets, Feedback On
TX contexts:
RX contexts:
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
10-33
Chapter 10
Configuring Quality of Service
Enabling IP Radio Access Network
10-34
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
A P P E N D I X
A
Maintaining 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 LEDs
The 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
A-1
Appendix A
Maintaining the MGX RPM-XF
Reading Front Panel LEDs
Figure A-1
MGX RPM-XF Front Panel LEDs
CPU OK
CB TX
CPU OK
CB TX
CB RX
CB RX
LM1 OK
LM2 OK
LM1 OK
LM2 OK
75534
RPM-XF
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.
Table A-1
A-2
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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix A
Maintaining the MGX RPM-XF
Recovering a Lost Password
Table A-1
Front Panel LEDs (continued)
LED NAME
COLOR
DEFINITION
CB TX
Off
Cells are not being transmitted to the cellbus
Green
Cells are being transmitted to the cellbus
Off
Cells are not being received from the cellbus
Green
Cells are being received from the cellbus
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
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
CB RX
LM1 OK
LM2 OK
Recovering a Lost Password
This 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
A-3
Appendix A
Maintaining the MGX RPM-XF
Recovering a Lost Password
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 Procedure
Complete 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 or MGX-XF-UI/B 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 Cisco 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>
A-4
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix A
Maintaining the MGX RPM-XF
Recovering a Lost Password
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$s9syZt4uKn3SnpuLDrhuei
enable 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
Step 12
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.
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 newpassword1
Router(config)# enable password newpassword2
Router(config)# line con 0
Router(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/0
Router(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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
A-5
Appendix A
Maintaining the MGX RPM-XF
Virtual Configuration Register Settings
Step 17
Caution
Press Ctrl-Z or enter end to exit configuration mode and return to the EXEC command interpreter.
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 Settings
The 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
A-6
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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix A
Maintaining the MGX RPM-XF
Virtual Configuration Register Settings
Table A-2
Virtual Configuration Register Bit Meaning (continued)
Bit No.1
Hexadecimal
Meaning
08
0x0100
Break is disabled
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.
Changing Configuration Register Settings
Complete 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> enable
password: enablepassword
MGX 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.)
Table A-3
Step 4
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.
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)
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
A-7
Appendix A
Maintaining the MGX RPM-XF
Virtual Configuration Register Settings
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 Meanings
The 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
A-8
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
cisco3-RPM-XF
0
0
1
1
cisco4-RPM-XF
0
1
0
0
cisco5-RPM-XF
0
1
0
1
cisco6-RPM-XF
0
1
1
0
cisco7-RPM-XF
0
1
1
1
cisco10-RPM-XF
1
0
0
0
cisco11-RPM-XF
1
0
0
1
cisco12-RPM-XF
1
0
1
0
cisco13-RPM-XF
1
0
1
1
cisco14-RPM-XF
1
1
0
0
cisco15-RPM-XF
1
1
0
1
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix A
Maintaining the MGX RPM-XF
Virtual Configuration Register Settings
Table A-4
Default Boot Filenames (continued)
Filename
Bit 3
Bit 2
Bit 1
Bit 0
cisco16-RPM-XF
1
1
1
0
cisco17-RPM-XF
1
1
1
1
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> enable
Password: enablepassword
Router#config terminal
Enter configuration commands, one per line. End with CTRL/Z
Router(config)#config-register 0x2102
Router(config)#no boot system
Router(config)#boot system bootflash:rpmxf-p12-mz.122-7b.bin
Router(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.)
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>
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-6
System Console Terminal Baud Rate Settings
Baud
Bit 12
Bit 11
Bit 05
1200
1
0
0
2400
1
1
0
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
A-9
Appendix A
Maintaining the MGX RPM-XF
Copying a Cisco IOS Image to Bootflash
Table A-6
System Console Terminal Baud Rate Settings (continued)
Baud
Bit 12
Bit 11
Bit 05
4800
0
1
0
9600
0
0
0
19200
0
0
1
38400
0
1
1
57600
1
0
1
115200
1
1
1
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 Disk
To disable break and enable booting from the PXM hard disk, use the following commands:
Router> enable
Password:enablepassword
Router# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#config-register 0x2102
Router(config)#no boot system
Router(config)#boot system x:rpmxf-p12-mz.122-7b.bin
Router(config)#end
Enabling Booting from Bootflash
To disable break and enable booting from bootflash, use the following commands:
Router> enable
Password:enablepassword
Router# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#config-register 0x2102
Router(config)#no boot system
Router(config)#boot system bootflash:rpmxf-p12-mz.122-7b.bin
Router(config)#end
Copying a Cisco IOS Image to Bootflash
You 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.
A-10
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix A
Maintaining the MGX RPM-XF
Copying 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> enable
Password: enablepassword
Router# 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> enable
Password: enablepassword
Router# config terminal
Router(config)# no boot system
Router(config)# boot system bootflash:rpmxf-p12-mz.122-7b.bin
Press Ctrl-Z to exit configuration mode
Step 9
Write the new configuration to memory.
Router# copy running-config startup-config
The system displays an OK message when the configuration has been saved.
Step 10
Enter the reload command to reboot the RPM-XF.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
A-11
Appendix A
Maintaining the MGX RPM-XF
Recovering 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 Images
If 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 Command
Enter 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:
Step 1
•
-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.
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]: y
Ready 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> enable
Password: enablepassword
Router# 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.
A-12
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix A
Maintaining the MGX RPM-XF
Recovering Boot and System Images
Using the tftpdnld Command
Enter the tftpdnld command on the fast ethernet ports on the MGX-XF-UI or MGX-XF-UI/B
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:
Step 1
•
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)
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
rommon
rommon
rommon
rommon
rommon
rommon
1>
2>
3>
4>
5>
6>
7>
IP_ADDRESS=10.1.0.1
IP_SUBNET_MASK=255.255.255.0
DEFAULT_GATEWAY=10.0.0.1
TFTP_SERVER=10.2.0.3
TFTP_FILE=rpmxf-p12-mz.122-7b.bin
TFTP_MACADDR=0050.3eff.f301
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> enable
Password: enablepassword
Router# 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
A-13
Appendix A
Maintaining the MGX RPM-XF
Recovering Boot and System Images
A-14
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
A P P E N D I X
B
Cable and Connector Specifications
This appendix provides the following pinout information:
•
100BASE-T 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.
100BASE-T Fast Ethernet Specifications
Each Fast Ethernet port on the MGX-XF-UI or MGX-XF-UI/B back card has an RJ-45 connector to
attach to Category 5 UTP for 100BASE-TX. The following table lists the cabling specifications for
100-Mbps Fast Ethernet transmission over UTP cables.
Parameter
RJ-45
Cable specification
Category 5 1 UTP2, 22 to 24 AWG
Maximum cable length
—
Maximum segment length
328 ft (100 m) for 100BASE-TX
Maximum network length
656 ft (200 m) (with 1 repeater)
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
B-1
Appendix B
Cable and Connector Specifications
Console and Auxiliary Port Signals and Pinouts
Console and Auxiliary Port Signals and Pinouts
The 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 Cable
You 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
Pin 1 and pin 8
should be the
same color
Pin 8
H3824
Pin 1
Console Port Signals and Pinouts
Use 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-1 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).
B-2
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix B
Cable and Connector Specifications
Console and Auxiliary Port Signals and Pinouts
Connecting the Console Port to a PC
PC
RJ-45-to-RJ-45
rollover cable
MGX 8850 RPM
Table B-1
RJ-45-to-DB-25 adapter
(labeled “Terminal”)
18083
Figure B-2
Console Port Signaling and Cabling Using a DB-9 Adapter
MGX-XF-UI or
MGX-XF-UI/B
Console Port (DTE)
RJ-45-to-RJ-45 Rollover Cable
RJ-45-to-DB-9
Terminal Adapter
Console
Device
Signal
RJ-45 Pin
RJ-45 Pin
DB-9 Pin
Signal
8
8
CTS
1
RTS
1
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
1. Pin 1 is connected internally to pin 8.
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-2 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).
Connecting the Console Port to a Terminal
RJ-45-to-RJ-45
rollover cable
MGX 8850 RPM
Terminal
RJ-45-to-DB-25 adapter
(labeled “Terminal”)
18082
Figure B-3
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
B-3
Appendix B
Cable and Connector Specifications
Console and Auxiliary Port Signals and Pinouts
Table B-2
Console Port Signaling and Cabling Using a DB-25 Adapter
MGX-XF-UI or
MGX-XF-UI/B Console
Port (DTE)
RJ-45-to-RJ-45 Rollover Cable
RJ-45-to-DB-25
Terminal Adapter
Console
Device
Signal
RJ-45 Pin
RJ-45 Pin
DB-25 Pin
Signal
8
5
CTS
1
RTS
1
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
1. Pin 1 is connected internally to pin 8.
Note
This cabling configuration can also be used to connect a terminal with the auxiliary port.
Auxiliary Port Signals and Pinouts
Use 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-1 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).
Connecting to the auxiliary port through a modem is not supported.
Figure B-4
Connecting the Auxiliary Port to a PC
RJ-45-to-RJ-45
rollover cable
MGX 8850 RPM
B-4
PC
RJ-45-to-DB-25 adapter
(labeled “Terminal”)
18083
Note
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix B
Cable and Connector Specifications
Console and Auxiliary Port Signals and Pinouts
Table B-3
Auxiliary Port Signaling and Cabling Using a DB-9 Adapter
MGX-XF-UI or
MGX-XF-UI/B
Console Port (DTE)
RJ-45-to-RJ-45 Rollover Cable
RJ-45-to-DB-9
Terminal Adapter
Console
Device
Signal
RJ-45 Pin
RJ-45 Pin
DB-9 Pin
Signal
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
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-2 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).
Connecting the Auxiliary Port to a Terminal
Terminal
RJ-45-to-RJ-45
rollover cable
MGX 8850 RPM
Table B-4
RJ-45-to-DB-25 adapter
(labeled “Terminal”)
18082
Figure B-5
Auxiliary Port Signaling and Cabling Using a DB-25 Adapter
MGX-XF-UI or
MGX-XF-UI/B Console
Port (DTE)
RJ-45-to-RJ-45 Rollover Cable
RJ-45-to-DB-25
Terminal Adapter
Console
Device
Signal
RJ-45 Pin
RJ-45 Pin
DB-25 Pin
Signal
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
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
B-5
Appendix B
Cable and Connector Specifications
Fast Ethernet RJ-45 Connector Pinouts
Fast Ethernet RJ-45 Connector Pinouts
This section provides pinouts for the FE RJ-45 connectors.
Note
Note
Cisco Systems does not provide FE port adapter cables. These cables must be ordered from commercial
cable vendors.
Pin
Description
1
Receive Data + (RxD+)
2
RxD–
3
Transmit Data + (TxD+)
6
TxD–
Use the proper common-mode line terminations 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 100BASE-TX 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
Ethernet port
3 TxD+
3 RxD+
6 TxD–
6 RxD–
1 RxD+
1 TxD+
2 RxD–
2 TxD–
Crossover Cable Pinout for FE-TX RJ-45 Connections Between Hubs and Repeaters
Hub or LAN switch
3 TxD+
3 TxD+
6 TxD–
6 TxD–
1 RxD+
1 RxD+
2 RxD–
2 RxD–
H3138
Hub or LAN switch
H7101
Hub or LAN switch
Figure B-7
B-6
Straight-Through Cable Pinout for FE-TX RJ-45 Connection to a Hub or Repeater
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix B
Cable and Connector Specifications
SFP Specifications
SFP Specifications
This section lists the Small-Form-Factor Pluggable (SFP) module cable specifications that are used with
the MGX-1GE and MGX-2GE Gigabit Ethernet back cards. The table lists the SFPs and their respective
cable types and lengths.
The MGX-1GE and MGX-2GE back cards provide trunks with 1 Gbps throughput per port over
multimode fiber, single-mode fiber, and copper, depending on the SFP type.
SFP
Description
GLC-SX-MM 1000Base SX
62.5/125 um
Multimode
850 nmCable
50/125 um
Multimode
850 nmCable
62.5/125 um
50/125 um
9/125 um
Category 5
Multimode
Multimode
Singlemode
Cable
1310 nmCable 1310 nm Cable 1310 nm Cable
—
500 M at
220 M at
160 MHz-km 400 MHz-km
—
—
—
550 M at
275 M at
200 MHz-km 500 MHz-km
GLC-LH-SM
1000Base LH/LX —
—
550 M at
550 M at
500 MHz-km 400 MHz-km
10 km
—
GLC-ZX-SM
1000Base ZX
—
—
—
—
70 km
—
GLC-T
1000BASE-T
(Copper)
—
—
—
—
—
100M
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
B-7
Appendix B
Cable and Connector Specifications
SFP Specifications
B-8
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
A P P E N D I X
C
Cisco 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 Basics
This section provides you with some basic information about the Cisco IOS software.
Cisco IOS Modes of Operation
Cisco 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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
C-1
Appendix C
Cisco IOS and Configuration Basics
Cisco IOS Software Basics
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 Log in.
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.
MGX8850-RPM>
Privileged
EXEC
Enter the enable EXEC
Privileged EXEC commands set operating
command from user EXEC
parameters. The privileged command set
includes those commands contained in user mode.
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.
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
Enter the reload EXEC
command from privileged
EXEC mode. Click Break
during the first 60 seconds
(sec) while the system is
booting.
ROMMON>
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.
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.
C-2
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix C
Cisco IOS and Configuration Basics
Cisco IOS Software Basics
Getting Context-Sensitive Help
In 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 Changes
Whenever 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> enable
MGX8850-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> enable
MGX8850-RPM# copy startup-config running-config
To erase both configuration files (and start over), enter the write erase and reload commands.
MGX8850-RPM> enable
MGX8850-RPM# write erase
MGX8850-RPM# reload
Warning
This command sequence will erase the entire RPM-XF configuration in RAM and NVRAM and reload
the RPM-XF.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
C-3
Appendix C
Cisco IOS and Configuration Basics
Manually Configuring RPM-XF
Manually Configuring RPM-XF
You 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 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 Cisco 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
C-4
When you finish configuring the RPM-XF, enter the exit command until you return to the privileged
EXEC prompt (MGX8850-RPM-XF#).
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix C
Cisco IOS and Configuration Basics
Manually Configuring 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.
Verifying Network Connectivity
When 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 , “Installing and Configuring the MGX-XF-UI and MGX-XF-UI/B Management Back
Cards”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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
C-5
Appendix C
Cisco IOS and Configuration Basics
Manually Configuring RPM-XF
C-6
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
A P P E N D I X
D
Command Summary
This chapter 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
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.
—
exit
Terminate an existing network
connection.
Exits a terminal session.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
D-1
Appendix D
Command Summary
User Exec Mode Commands
D-2
Command
Description
Command Use and Purpose
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).
—
release
Release a resource.
—
renew
Renew a resource.
—
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.
—
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix D
Command Summary
Privileged Exec Mode Commands
Privileged Exec Mode Commands
Command
Description
Command Use and Purpose
<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.
analyze
Analyze IOS resources.
—
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.
—
elog
Event-logging control.
—
enable
Turn on privileged commands.
—
erase
Erase a file system.
—
event-log
Enable, disable, or initialize
event logging.
—
exatm-test-client
Test client for exatm API.
—
exit
Exit from the EXEC.
—
format
Format a file system.
Formats a Flash disk or Flash card.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
D-3
Appendix D
Command Summary
Privileged Exec Mode Commands
D-4
Command
Description
Command Use and Purpose
help
Description of the interactive
help system.
—
iterate-ip-addrs
Show IDBs visited by IP address —
iterators.
lock
Lock the terminal.
Sets up a temporary password on a line.
login
Log in as a particular user.
—
logout
Exit from the EXEC.
—
loop-counter
IDB loop debug command.
—
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.
release
Release a resource.
—
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.
renew
Renew a resource.
—
resume
Resume an active network
connection.
Navigates to another open Telnet, rlogin,
LAT, or PAD session.
rlogin
Open an rlogin connection.
—
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix D
Command Summary
Privileged Exec Mode Commands
Command
Description
Command Use and Purpose
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.
set
Set system parameter.
—
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.
socktest
Run a socket test.
—
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.
upgrade
Upgrade software.
—
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
D-5
Appendix D
Command Summary
Global Configuration Mode Commands
Global Configuration Mode Commands
D-6
Command
Description
Command Use and Purpose
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.
—
archive
Archive the configuration.
—
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.
audit
Audit the router.
—
banner
Define a login banner.
Displays a banner on terminals with an
interactive EXEC.
boot
Modify system boot parameters. —
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.
—
call
Configure call parameters.
—
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.
control-plane
Configure control plane
services.
—
controller
Configure a specific controller.
Configures a controller-type and enters
config-controller mode.
coverage
Coverage analysis tools.
—
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.
—
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix D
Command Summary
Global Configuration Mode Commands
Command
Description
Command Use and Purpose
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.
downloadcompatible-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.
—
flow-sampler-map
Configure flow sampler.
—
help
Description of the interactive
help system.
—
hostname
Set system network name.
Specifies the host name of the RPM-XF.
hw-module
Configure hardware modules.
The rpm keyword specifies the RPM-XF.
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.
memory
Configure memory management. —
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
D-7
Appendix D
Command Summary
Global Configuration Mode Commands
D-8
Command
Description
Command Use and Purpose
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.
—
password
Configure encryption password
(key).
—
periodic-ping
Configure periodic ping.
—
policy-manager
Configure policy manager.
—
policy-map
Configure QoS policy map.
Enters config-pmap mode. From there you
can enter config-pmap-c mode.
ppp
Configure ppp parameters.
The iphc keyword configures timeouts for
the RPM-XF card.
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
Configure processes.
—
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.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix D
Command Summary
Global Configuration Mode Commands
Command
Description
Command Use and Purpose
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.
—
subscriber
Configure subscribers.
—
table-map
Configure table map.
—
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.
—
track
Configure object tracking.
—
username
Establish user name
authentication.
Assigns a user name that is displayed in the
configuration files.
vc-class
Configure per VC parameters.
—
virtual-profile
Virtual profile configuration.
Enables virtual profiles by AAA
configuration.
virtual-template
Virtual template configuration.
—
vlan
Configure VLAN.
—
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
D-9
Appendix D
Command Summary
Interface Configuration Mode Commands
Interface Configuration Mode Commands
D-10
Command
Description
Command Use and Purpose
arp
Set arp type (arpa, probe, snap)
or timeout.
—
atm
Modify ATM parameters.
—
autodetect
Autodetect encapsulation on a
serial interface.
—
backup
Modify backup parameters.
Not supported.
bandwidth
Set bandwidth informational
parameter.
—
barium
Configure Barium on POS
interface.
—
bgp-policy
Apply policy propagated by bgp Enables QPPB on the interface.
community string.
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.
—
compress
Configure serial interface
compression.
—
crc
Specify CRC word size.
—
custom-queue-list
Assign a custom queue list to an —
interface.
dampening
Enable event dampening.
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.
—
dot1q
Configure dot1q on interface.
—
down-when-looped
Force looped serial interface
down.
—
duplex
Configure duplex operation.
—
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix D
Command Summary
Interface Configuration Mode Commands
Command
Description
Command Use and Purpose
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.
fair-queue
Enable fair queuing on an
interface.
—
flow-sampler
Attach flow sampler to the
interface.
—
full-duplex
Configure full-duplex mode.
—
glbp
Configure Gateway Load
Balancing Protocol
—
half-duplex
Configure half-duplex mode.
—
help
Description of the interactive
help system.
—
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-controlprotocol
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-reservedbandwidth
Maximum reservable bandwidth —
on an interface.
media-type
Interface media type.
—
mpls
Configure MPLS interface
parameters.
—
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
D-11
Appendix D
Command Summary
Interface Configuration Mode Commands
D-12
Command
Description
Command Use and Purpose
mtu
Set the interface maximum
transmission unit (MTU).
—
multilink-group
Put interface into a multilink
bundle.
—
negotiation
Select Autonegotiation mode.
—
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.
routing
Configure per-interface routing.
—
serial
Configure serial 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 switch configuration.
—
tag-control-protocol Tag switch controller control
protocol commands.
—
tag-switching
—
Tag switching interface
configuration commands.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Appendix D
Command Summary
QoS Configuration Mode Commands
Command
Description
Command Use and Purpose
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.
—
tx-ring-limit
Configure PA level transmit ring —
limit.
vrrp
Configure VRRP on interface.
—
QoS Configuration Mode Commands
Quality of Service (QoS) commands are described inChapter 10, “Configuring Quality of Service”.
Command
Description
Command Use and Purpose
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.
—
Command
Description
Command Use and Purpose
class
Policy criteria.
—
description
Class-map description.
—
exit
Exit from QoS policy-map
configuration mode.
—
no
Negate or set default values of a —
command.
rename
Rename this class-map.
—
Command
Description
Command Use and Purpose
bandwidth
Class-based weighted fair queue. —
exit
Exit from QoS class action
configuration mode.
—
description
Class-map description.
—
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
D-13
Appendix D
Command Summary
QoS Configuration Mode Commands
D-14
Command
Description
Command Use and Purpose
no
Negate or set default values of a —
command.
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.
—
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
I N D EX
increasing
Numerics
reservation
802.1q PXF switching
10-2
10-7
10-1
BGP
community string
configuring
A
9-15
bit width flow control
access-group command
accounting
D-6
boilerplate
10-5
access list entries, creating
assigning to interface
D-1
Q0S
D-6
10-4
10-2
boot
AC power
power supply removal
active connections
addred command
see BGP
D-7
buffer, pool settings
10-2
D-12
xvii
D-6
authorization
D-6
bundling the interface
10-4
audience, for this document
A-10
Border Gateway Protocol
7-13, 7-16
assigning interfaces
7-8
bootload-failure response
D-5
ARPA encapsulation
authentication
sequence
3-5
adjusting file parameters
C
D-6
authorization attributes, assigning
auxiliary port
adapter
D-10
D-1
cable
assemblies
B-3, B-5
B-3, B-5
pinouts
console
B-3, B-5
cables
B
Fast Ethernet RJ-45 pinout
back cards
B-6
CAR
example configuration
MGX-XF-UI
6-10
caution
4-2
MGX-XF-UI, side view
MGX-XF-UI/B
4-3
See committed access rate
4-3
halting the router
A-6
changing configuration register settings
A-7
channelized T3 line card
bandwidth
command
4-6, 5-7, 6-6
guarantee
10-8
line clock source
character-bits values
5-9
D-6
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
IN-1
Index
Cisco 10000 Series edge services router (ESR)
restricting access
buffers
C-1
getting help
calendar
modes of operation
saving the configuration
class command
call
C-1
cd
D-4
D-6, D-10
class
QoS configuration
CLNS destination
10-4, D-6
D-3
clear counters
D-5
code-point values
4-6, 4-10, 5-7, 5-9
clns
D-3, D-6, D-10
clock source
connected to MGX 8850 RPM
commands
3-7
compress
4-6, 4-10, 5-7
D-10
config-cmap
D-1, D-3
D-6
access-enable
access-list
D-1, D-3
access-profile
D-1, D-3
access-template
D-3
A-7, A-9, D-6
config terminal
C-4
configure
D-3
D-1, D-3
controller
D-6
control-pane
copy
D-6
10-3
config-register
connect
D-6
D-1
D-6, D-10
clock
10-5
combo card
alias
10-4
clear
10-3
clock source command
1-99
D-6
class-map
10-3
D-10
D-3
chat-script
10-3, 10-5
CLI
modular
D-3
D-6
cdp
10-4
class-map command
D-6
carrier-delay
C-3
A-9
D-6
busy-message
C-3
C-3
Class C Flash file
A-9
Break (interrupt)
erasing the configuration
aaa
D-6
boot system
D-1
Cisco IOS software
basics
boot
D-6
D-3
analyze
D-3
copy running-config startup-config
archive
D-3, D-6
coverage
arp
async-bootp
atm
D-6
D-10
custom-queue-list
debug
D-6
autodetect
D-10
b (boot)
A-8
backup
D-10
bandwidth
banner
D-6
dampening
D-10
audit
4-6, 4-10, 5-7, 6-6, D-10
D-6
bgp-policy
IN-2
crc
D-6, D-10
D-10
C-3, C-5
default
D-10
D-10
D-3
D-6, D-10
default-value
define
D-6
delay
D-10
delete
D-3
description
D-6
D-10
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Index
dialer
D-6, D-10
dialer-group
dialer-list
dir
D-10
disconnect
dnsix-nat
key
D-7
download-compatible-config
down-when-looped
D-7
D-7
lock
login
D-7, D-11
D-2, D-4
logout
4-6, 5-7, D-11
D-3
D-3
fair-queue
D-11
loop-counter
D-4
mac-address
D-11
map-class
D-3
D-7
map-group
D-1, D-3, D-7, D-11
extended-port
D-7
D-2, D-4
loopback
exatm-test-client
D-2
login string
D-7
event-log
D-11
D-4
logging
A-7, C-4, D-1, D-3, D-7
map list
D-11
D-11
D-7
match
D-11
D-11
D-7
lock terminal
D-10
D-10
encapsulation
exit
D-7
D-3
erase
4-6, 4-10, 5-7, 6-6, D-11
load interval
D-10
duplex
D-4
label-control-protocol
D-7
line
enable
D-11
kerberos
D-7
end
D-11
keepalive
D-1, D-3
dnsix-dmdp
elog
isis
iterate-ip-addrs
D-1, D-3
dot1q
D-7
iso-igrp
D-7
D-3
disable
do
ipc
10-3, 10-5, D-13
Flash related
A-8
max-reserved-bandwidth
flow-sampler
D-11
media-type
flow-sampler-map
format
5-7
full-duplex
D-11
D-11
D-2, D-4, D-7, D-11
hold-queue
hostname
hw-module
D-8
D-7
D-7, D-11
D-4
more
D-4
mpls
D-4, D-8, D-11
mtu
10-26
hw-module rpm udp-comp
ip
modemcap
D-4
D-2, D-4
mtrace
D-7
hw-module rpm ipran
interface
D-4, D-8
mstat
D-7
10-23
D-7
microcode
mrinfo
D-11
D-11
D-8
monitor
D-11
half-duplex
help
menu
D-3
framing
glbp
memory
D-7
D-11
D-2, D-4
4-6, 4-10, 5-7, 6-6, D-12
multilink
D-8
multilink-group
name-connection
D-12
D-2, D-4
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
IN-3
Index
negotiation
no
router
D-12
routing
D-4, D-8, D-12
ntp
rtr
D-8, D-12
parser
D-8
password
peer
D-8
periodic-ping
policy-map
5-7
set
D-8
10-3, 10-6, D-8
D-5
D-12
D-9
pos framing
10-13, D-12
D-5
show class-map
show ip rtp
D-12
ppp
scramble
service-policy
10-7
policy-manager
pos
D-9
service
C-5, D-2, D-4
police
scheduler
serial
D-8
D-12
D-9
send
D-12
ping
D-9
10-15
10-27
show policy-map
5-10
D-2, D-4, D-8, D-12
ppp iphc max-time
10-26
10-14
show policy-map interface serial
show rpm ipran
10-27
ppp multilink
D-8
show sys info
D-2
priority-group
D-12
show version
A-7
priority list
privilege
show vlans
D-8
shutdown
D-8
process
slip
D-8
process-max-time
prompt
pvc
D-12
pwd
D-4
D-12
snapshot
snmp
speed
random-detect
rate-limit
D-12
D-9, D-12
socktest
D-8
10-8, D-12
D-12
D-8
D-12
D-9
D-5
source
queue list
10-15
D-2, D-5
SNMP
D-8
pulse-time
rbe
D-8
D-12
D-12
squeeze
D-5
standby
D-9, D-12
state machine
D-9
D-9
regexp
D-8
state-machine
release
D-2, D-4
subscriber
reload
rename
renew
resume
A-8, C-3, D-4
D-2, D-4
rlogin
rmon
D-2, D-4, D-8
D-8, D-12
route-map
IN-4
D-8
D-9
D-9
D-12
D-2, D-5
table-map
D-2, D-4
resume string
switch
systat
D-4
D-9
tacacs-server
D-9
tag-control-protocol
tag-switching
telnet
10-15
D-12
D-9, D-12
C-5, D-2, D-5
template
D-9
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Index
terminal queue
test
saving changes to
D-9
configuration mode
D-5
tftp-server
timeout
class map
D-9
exiting
D-13
time-range
trace
D-7
D-7
connections
traceroute
active
D-2, D-5
D-5
asynchronous
D-9
traffic-shape
D-13
D-5
tunnel open
rlogin
D-4
serial
D-5
terminal
D-2
tx-ring-limit
D-4
listing active
D-13
transmit interface
tunnel
10-3
configure mode
D-9
C-5
track
D-1
terminating
D-13
D-1
D-5
undelete
D-5
console port
upgrade
D-5
adapter
B-3, B-5
pinouts
B-3, B-5
username
vc-class
tunnel
D-2
undebug
verify
D-9
D-2
console port connection
D-9
virtual-profile
counters, clearing
D-9
virtual-template
D-9
crc command
vrrp
D-13
crossover cable
write
Fast Ethernet
D-2, D-5
D-5
D-5
write erase
C-3
committed access rate (CAR)
10-15, D-12
committed information rate (CIR)
community list
10-17
community string
10-3
10-3
config terminal command
configuration
displaying
cTCP
10-22
cUDP
10-22
current settings
4-6, 5-7
B-6
D-4
10-7
data path, determining
C-3
C-4
See distributed CAR
D-2
differentiated service code point
directory, displaying
A-8
settings, changing
D-2
DCAR
destination, tracing
register
boot field
10-22
D-9
D
D-10
config-cmap command
config-pmap mode
cRTP
C-3, C-5
D-1
CPU process handling
D-9
vlan
which-route
3-10
copy running-config startup-config command
D-5
where
C-3
D-4
distributed CAR (DCAR) policy
A-7
10-5
D-12
documentation
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
IN-5
Index
for VIP-related software commands
objectives
forward traffic
4-13
frame header, customizing
xvii
organization
10-8
framing
xvii
referenced and related
xvii
SDH STM-1
software configuration
xvii, 7-10
SONET STS-3c
drop keyword
dscp
5-10
5-10
front card
10-8
drop probability
5-10
removal
10-9
3-5
10-5
G
E
gigabit Ethernet interface, assigning
echo message
global configuration mode
D-2, D-4
10-4
C-2
eiBGP
load sharing
9-16
H
EMI requirements
with 10BASE-T
enable command
B-6
hardware
C-4
encapsulation command
installation procedures
4-6, 5-7
error messages in terminal sessions
header compression
D-3
see IPHC
Ethernet
host failure
interface
10-4
10-22
D-6
hw-module rpm ipran command
Ethernet 10BaseT connection
ewc value
3-1 to 3-11
2-5
10-26
hw-module rpm udp-comp command
10-23
10-9
exiting terminal session
D-7
exponential-weighting-constant value
I
10-9
export routes
iBGP
configuring
9-17
9-12
ICMP echo messages
D-2, D-4
import and export routes
configuring
F
9-17
import routes
Fast Ethernet
configuring
straight-through cable
filenames, netbooting
B-6
installation
A-9
changing configuration register settings
files
internal loopback
undeleting
D-5
buffer overflow message
C-5
D-11
Internet Protocol Header Compression
Flash memory
see IPHC
A-11
ensuring available space before copying to
IN-6
9-17
IOS
A-11
supported class maps
10-5
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Index
IP
L
accounting
7-18
address mapping
LEDs
D-6
differentiated service code point
dscp value
10-5
illustrated
1-9, A-2
line card
10-13
multicast packet rate
clock source
D-4
5-9
precedence value
10-8
logging, clearing
services on ports
D-11
logical name, assigning
ip address configuration subcommand
IPHC
commands
configurable compression
M
10-22
without IPID delta
maintenance procedures
10-22
IP Radio Access Network
mapping rules
configuring
overview
10-32
10-6
match command
10-33
10-9
10-3, 10-5
maximum transmission unit command
10-25
See mtu command
10-28
PVC
max-value threshold
connections
statistics
rules
10-3
mark-denom value
10-28
display example
10-3
policy, creating
10-26
configuration example
features
10-6
class, creating
10-25
commands
memory, testing
10-31
10-9
D-5
MGX-1GE back card
10-27
features
6-2
installation
K
6-16
MGX-1OC12POS-IR back card
keepalive command
4-6, 4-10, 5-7, 6-6
configuration
5-6
customizing
keywords
set-clp-transmit
5-9
default values
10-8
5-7
set-dscp-transmit value
10-8
example configuration
set-prec-transmit value
10-8
features
set-qos-transmit value
transmit
A-1
maps
See IPRAN
IPRAN
10-1
10-23
10-25
with IPID delta
5-11, 6-9
low-latency priority
10-23
D-2
loopback
command
10-22
example
5-8, 6-7
D-1
10-8
10-8
5-1
installation
5-6
interface configuration
syntax
5-12
5-8
5-8
troubleshooting
5-13
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
IN-7
Index
MGX-2GE back card
features
no shutdown command
NVRAM
6-3
installation
configuration
O
5-6
customizing
5-9
default values
OC-12 POS line card
5-7
framing mode
example configuration
5-12
5-10
interoperability
5-3
5-10
loopback testing
installation
5-6
interface configuration
syntax
C-3
6-16
MGX-2OC12POS back card
features
5-9, 6-7
5-11, 6-9
scrambling POS synchronous payload envelope
(SPE) 5-11
5-8
5-8
troubleshooting
5-13
P
1-3
packet
MGX 8850
three-slot model
MGX RPM-XF
performance
1-2
Physical Overview
10-15
class maps
10-3
defining characteristics
1-3
powered by Cisco MGX 8850 backplane
shipping package contents
1-3, 2-3
discarding
recognizing
cable specifications
min-value threshold
adjusting
9-10, 9-11
mtu command
4-6, 4-10, 5-7, 6-6
multicast packet rate
multicast VPN
D-7
backup
10-3
MPLS VPN
10-1
parameters
10-9
10-20
modular CLI
10-5
10-3
source, slowing
4-4
10-5
10-3
IP precedence value
3-1
MII
MLP/LFI
classifying
bandwidth
D-10
dialer map
D-7
MPLS
D-2
D-10
D-8, D-11
privilege
9-18
MultiLink PPP/Link Fragmentation Interleaving
scheduler
SNMP
see MLP/LFI
D-8
D-9
D-9, D-12
TACACS
D-9
terminal lines
N
D-2
password
neighbor information, requesting
netbooting
A-8
netload requests
D-9
network layer connection
D-1
temporary
D-2, D-4
ping command
C-5
pinouts
D-2
network management station (NMS)
IN-8
restricting access
D-2
D-1
RJ-45
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Index
Fast Ethernet
policy propagation
B-6
Fast Ethernet crossover and straight-through
cables B-6
police command
service policy
set
10-7
10-3, 10-6
configuration example
description
See QPPB
enabling
ports
support
D-5
5-7, 5-10
pos framing command
10-2
D-10
10-2
queue
5-7, 5-11
limits
POS synchronous payload envelope (SPE)
ppp iphc max-time command
5-11
size
10-12
10-9
10-26
D-1
precedence value
10-9
prioritize queuing
D-8
R
RADIUS
privileged EXEC mode
C-2
D-6
random-detect command
procedures
random-detect keyword
installation
3-1 to 3-11
maintenance
propagation
reload command
A-1 to A-12
10-2
protocols
D-9
10-15
10-8
10-9
A-8
remote monitoring
D-8
resetting functions
D-1
restricting access
policy propagation border gateway
D-1
resuming session numbers
D-1
RJ-45
publication conventions
xix
1Fast Ethernet
cable specifications
4-4, B-1
cable
Q
Fast Ethernet pinout
QoS
specifications
boilerplate creation
class map
10-3
match command
10-1
10-3
performance, improving
10-3
4-4, B-1
B-6
Fast Ethernet
10-6
cable
B-6
cable pinout
packet management process
policies, entering
B-6
crossover and straight-through cable pinouts
10-3
committed access rate (CAR)
policy map
3-2
quality of service. See QoS.
5-7, 5-10
pos scramble-atm command
PPP session
10-1
10-15
qualified personnel warning
pos flag command
routing
10-2
QPPB
10-15
policy propagation border gateway protocol
source
D-12
weighted random early detection (WRED)
policy-map command
policy map statistics
10-2
10-7
10-3
B-6
crossover and straight-through cable pinouts
pinouts
B-6
B-6
roll-over cable, identifying
ROM monitor mode
B-2
C-2
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
IN-9
Index
router
telnet command
managing QoS
C-5
temporary access list entries
10-2, 10-12
temporary passwords
D-1
D-2
terminal connection, opening
S
terminal lines
D-1
D-2
terminal session
safety
with electricity
closing
2-2
sending ICMP echo msgs
debug output
D-4
service-policy command
D-7
D-3
error messages
10-3, 10-13
exiting
session
D-3
D-1
exiting
D-1
threshold maximum and minimum
number
D-1
time, configuring
set command
trace command
10-12
set-dscp-transmit value keyword
10-8
set-prec-transmit value keyword
10-8
set-qos-transmit value keyword
10-9
D-6
C-5
traceroutes
described
D-4
showing statistics
10-8
D-2
traffic
setup
manual configuration
clearing
C-4
show class-map command
show ip rtp command
controlling priority
10-15
10-27
show policy-map command
10-14
show policy-map interface serial command
show rpm ipran command
show statistics
10-8
prioritizing
10-2
traffic shaping
10-7
10-1
10-8
D-2, D-4
U
A-11
specifications
system
10-15
forwarding
transmit keyword
10-27
software
upgrading
D-1
upgrading the software
user EXEC mode
1-9
statements, matching
static ARP entry, setting
D-1
D-6
synchronous payload envelope (SPE)
system code, updating
C-2
user-profile, creating
10-6
A-11
A-11
5-11
V
verifying network connectivity
C-5
Versatile Traffic Management System
T
see VTMS
TACACS+
Telnet
D-6
version information, requesting
virtual configuration register
D-1
D-2
A-6 to A-10
to device
D-1
VPN
IN-10
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
Index
MPLS
9-10, 9-11
multicast
9-18
overview
9-9
routing
VTMS
9-11, 9-12
10-18
W
warning
class 1 laser product
definition
laser beam
xxi
xx
xxi
qualified personnel
3-2
weighted random early detection
See WRED
working directory, displaying
WRED
D-4
10-1, 10-8, 10-15
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005
IN-11
Index
IN-12
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide
Release 5.2, Part Number OL-6594-01, Rev. C0, September 2005