Router Cisco Ios XR
Router Cisco Ios XR
Americas 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 527-0883
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.
CCVP, the Cisco Logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems,
Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco
Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing,
FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream,
Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StackWise, The Fastest Way
to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0612R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Preface ix
Contents 1-1
Contents 2-1
Prerequisites 2-1
Software Requirements 2-1
Hardware Prerequisites and Documentation 2-2
Contents 3-1
Prerequisites 3-1
Software Requirements 3-1
Hardware Requirements 3-2
Restrictions 3-2
Contents 4-1
Contents 5-1
Contents 6-1
Contents 7-1
GLOSSARY
INDEX
This guide describes how to create the initial configuration for a router using the
Cisco IOS XR software. This guide also describes how to complete additional administration,
maintenance, and troubleshooting tasks that may be required after initial configuration.
This preface contains the following sections:
• Changes to This Document, page ix
• About This Document, page ix
• Obtaining Documentation, page xi
• Documentation Feedback, page xii
• Cisco Product Security Overview, page xii
• Product Alerts and Field Notices, page xiii
• Obtaining Technical Assistance, page xiv
• Obtaining Additional Publications and Information, page xv
Intended Audience
This document is intended for the following people:
• Experienced service provider administrators
• Cisco telecommunications management engineers
• Third-party field service technicians who have completed the Cisco IOS XR software training
sessions
• Customers who daily use and manage routers running Cisco IOS XR software
Related Documents
For a complete listing of available documentation for the Cisco IOS XR software and the routers on
which it operates, see the following Web pages:
• Cisco IOS XR Software Documentation
http://www.cisco.com/univercd/cc/td/doc/product/ioxsoft/index.htm
• Cisco CRS-1 Carrier Routing System Documentation
http://www.cisco.com/univercd/cc/td/doc/product/core/crs/
• Cisco 12000 Series Router Documentation
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/index.htm
• Cisco Catalyst 6509 Switch Documentation
http://www.cisco.com/en/US/products/hw/switches/ps708/
tsd_products_support_series_home.html
Note Cisco IOS XR software runs only on the Cisco XR 12000 Series Routers listed in the “Supported
Standalone System Configurations” section on page 1 in Chapter 1, “Introduction to Cisco IOS XR
Software.”
Conventions
This document uses the following conventions:
Item Convention
Commands and keywords boldface font
Variable for which you supply values italic font
Displayed session and system information screen font
Commands and keywords you enter in an boldface screen font
interactive environment
Variables you enter in an interactive environment italic screen font
Menu items and button names boldface font
Menu navigation Option > Network Preferences
Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the
publication.
Tip Means the following information will help you solve a problem. The information in tips might not be
troubleshooting or an action, but contains useful information.
Caution Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. This section explains the
product documentation resources that Cisco offers.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
Ordering Documentation
You must be a registered Cisco.com user to access Cisco Marketplace. Registered users may order
Cisco documentation at the Product Documentation Store at this URL:
http://www.cisco.com/go/marketplace/docstore
If you do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Documentation Feedback
You can provide feedback about Cisco technical documentation on the Cisco Technical Support &
Documentation site area by entering your comments in the feedback form available in every online
document.
A current list of security advisories, security notices, and security responses for Cisco products is
available at this URL:
http://www.cisco.com/go/psirt
To see security advisories, security notices, and security responses as they are updated in real time, you
can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS)
feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to
encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been
encrypted with PGP versions 2.x through 9.x.
Never use a revoked encryption key or an expired encryption key. The correct public key to use in your
correspondence with PSIRT is the one linked in the Contact Summary section of the Security
Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT to find other means of encrypting the data before sending
any sensitive material.
To access the Product Alert Tool, you must be a registered Cisco.com user. (To register as a Cisco.com
user, go to this URL: http://tools.cisco.com/RPF/register/register.do) Registered users can access the
tool at this URL: http://tools.cisco.com/Support/PAT/do/ViewMyProfiles.do?local=en
Note Use the Cisco Product Identification Tool to locate your product serial number before submitting a
request for service online or by phone. You can access this tool from the Cisco Technical Support &
Documentation website by clicking the Tools & Resources link, clicking the All Tools (A-Z) tab, and
then choosing Cisco Product Identification Tool from the alphabetical list. This 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.
If you suspect that the browser is not refreshing a web page, force the browser to update the web page
by holding down the Ctrl key while pressing F5.
To find technical information, narrow your search to look in technical documentation, not the entire
Cisco.com website. On the Cisco.com home page, click the Advanced Search link under the Search box
and then click the Technical Support & Documentation.radio button.
To provide feedback about the Cisco.com website or a particular technical document, click Contacts &
Feedback at the top of any Cisco.com web page.
• Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, 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 magazine for Cisco networking professionals. 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 subscribe to Packet magazine at this URL:
http://www.cisco.com/packet
• 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
• Networking products offered by Cisco Systems, as well as customer support services, can be
obtained at this URL:
http://www.cisco.com/en/US/products/index.html
• Networking Professionals Connection is an interactive website where networking professionals
share questions, suggestions, and information about networking products and technologies with
Cisco experts and other networking professionals. Join a discussion at this URL:
http://www.cisco.com/discuss/networking
• “What’s New in Cisco Documentation” is an online publication that provides information about the
latest documentation releases for Cisco products. Updated monthly, this online publication is
organized by product category to direct you quickly to the documentation for your products. You
can view the latest release of “What’s New in Cisco Documentation” at this URL:
http://www.cisco.com/univercd/cc/td/doc/abtunicd/136957.htm
• 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
This chapter introduces the routers that support Cisco IOS XR software and the user interfaces you can
use to manage routers that run Cisco IOS XR software.
Contents
This chapter contains the following sections:
• Supported Standalone System Configurations, page 1-1
• Cisco CRS-1 Multishelf System Overview, page 1-2
• Router Management Interfaces, page 1-6
• Selecting and Identifying the Designated Shelf Controller, page 1-7
• Connecting to the Router Through the Console Port, page 1-9
• Where to Go Next, page 1-14
Note Many cards operate in both Cisco XR 12000 Series routers and in Cisco 12000 Series routers. For the
latest information on which cards are supported by the Cisco IOS XR software in Cisco XR 12000 Series
routers and Cisco 12000 Series routers, see Release Notes for Cisco IOS XR Software Release 3.4.
The Cisco IOS XR software also runs on Cisco CRS-1 Multishelf Systems, which are described in the
following section.
129492
1 2 1 3
1 Cisco CRS-1 16-Slot Line Card Chassis (two 3 Cisco Catalyst 6509 Switch (two suggested)
required)
2 Cisco CRS-1 Fabric Card Chassis (one
required)
158260
1 2 1 3
1 Cisco CRS-1 16-Slot Line Card Chassis (two 3 Cisco Catalyst 6509 Switch (two suggested)
required)
2 Cisco CRS-1 Fabric Card Chassis (two
required)
149632
1 2 1 3
1 Cisco CRS-1 16-Slot Line Card Chassis (two 3 Cisco Catalyst 6509 Switch (two suggested)
required)
2 Cisco CRS-1 Fabric Card Chassis (four
required)
For more information on multishelf systems, see Chapter 3, “Bringing Up the Cisco IOS XR Software
on a Multishelf System.”
Command-Line Interface
The CLI is the primary user interface for configuring, monitoring, and maintaining routers that run the
Cisco IOS XR software. The CLI allows you to directly and simply execute Cisco IOS XR commands.
All procedures in this guide use the CLI. Before you can use other router management interfaces, you
must first use the CLI to install and configure those interfaces. Guidelines for using the CLI are
presented in the following chapters:
• Chapter 4, “Configuring General Router Features”
• Chapter 5, “Configuring Additional Router Features”
• Chapter 6, “CLI Tips, Techniques, and Shortcuts”
For information on CLI procedures for other tasks, such as hardware interface and software protocol
management, see the Cisco IOS XR software documents listed in the “Related Documents” section on
page x.
sends the response to the client in the form of encoded XML API tags. The XML API supports readily
available transport layers, including Telnet, Secure Shell (SSH), and Common Object Request Broker
Architecture (CORBA). The Secure Socket Layer (SSL) transport is also supported by the XML API.
For more information, see the Cisco IOS XR software documents listed in the “Related Documents”
section on page x.
Note Throughout this guide, the term RP is used to refer to the RP cards supported on Cisco CRS-1 routers
and the PRP cards supported on Cisco XR 12000 Series Routers. If a feature or an issue applies to only
one platform, the accompanying text specifies the platform.
Although each router or multishelf system can have multiple RP cards, only one can serve as the DSC
and control the router or multishelf system. The DSC provides system-wide administrative functions,
including:
• User configuration using a terminal connection or network connection
• Distribution of software to each node in the router or system
• Coordination of software versioning and configurations for all nodes in the router or system
• Hardware inventory and environmental monitoring
The first step in setting up a new router is to select or identify the DSC because the initial router
configuration takes place through the DSC. The following sections describe how to select and identify
the DSC on different routers and the multishelf system:
• Selecting and Identifying the DSC on Cisco CRS-1 Routers, page 1-8
• Selecting and Identifying the DSC on Cisco CRS-1 Multishelf Systems, page 1-8
• Selecting and Identifying the DSC on Cisco XR 12000 and 12000 Series Routers, page 1-9
Tip After the router starts for the first time, you can use the redundancy reddrv command to select which
RP becomes the DSC during a restart.
The active RP and DSC lights the Primary LED on the RP front panel. The alphanumeric LED display
on the active RP displays ACTV RP. By default, the other RP becomes the standby RP, displays STBY
RP on the alphanumeric display, and takes over if the DSC fails.
To visually determine which RP is operating as the DSC in a Cisco CRS-1 router, look for the RP on
which the Primary LED is lit. You can also look for the RP that displays the ACTV RP message on the
alphanumeric display.
Tip After the router starts for the first time, you can use the redundancy reddrv command to select which
Rack 0 RP becomes the DSC during a restart.
The active RP and DSC lights the Primary LED on the RP front panel. The alphanumeric LED display
on the active RP displays ACTV RP. By default, the other RP becomes the standby RP, displays STBY
RP on the alphanumeric display, and takes over if the DSC fails.
After the DSC starts up in Rack 0, the DSC remains in Rack 0 while at least one RP in Rack 0 is operating
properly. If both RPs in Rack 0 fail, the active RP in the other rack becomes the DSC. The process of
moving the DSC function from one rack to another is called DSC migration. For more information on
DSC migration, see the Cisco IOS XR System Management Configuration Guide, Release 3.4.
Note Any LCC can host the DSC. The FCC cannot host the DSC function.
Selecting and Identifying the DSC on Cisco XR 12000 and 12000 Series Routers
A Cisco XR 12000 or 12000 Series router supports multiple PRPs. When the router is started for the first
time, the PRP in the lowest-numbered slot becomes the active PRP and is identified by the alphanumeric
display: ACTV RP. The active PRP serves as the DSC. If another PRP is configured as a standby PRP
for the DSC, that PRP can assume the DSC role if the DSC fails.
To have a PRP in a higher-numbered slot become the DSC, you must bring up the router with only that
PRP installed. After the chosen PRP becomes the DSC, it remains the DSC after subsequent restarts and
you can add the other PRPs.
Note Additional PRPs can be installed to host secure domain routers (SDRs), which are introduced in
Chapter 4, “Configuring General Router Features.” To configure general router features, you must
connect to the DSC. To configure SDR features, you must connect to the PRP for the appropriate SDR.
Figure 1-4 Communication Ports on the RP for a Cisco CRS-1 16-Slot LCC
RP
RJ-45 cable
Local terminal or
terminal server for
CLI communication Console
AUX
RJ-45 cable
HDD
PC Card
(disk1:)
Primary
116547
Status
Figure 1-5 Communication Ports on the RP for Cisco CRS-1 4-slot and 8-Slot LCCs
RJ-45 cable
Local terminal or
terminal server for
CLI communication Console Terminal connection
PC
CARD User-removable flash disk1
stores installation PIE files
EXT
CLK 1
EXT
CLK 2
LED status
displays
(alphanumeric)
149693
Figure 1-6 Communication Ports on the PRP-2 for a Cisco XR 12000 Series Router
SL
SL 0
OT
OT
-
-1
Ethernet cable
ETH 0
Network LIN
K
Management Ethernet connection for
out-of-band network communication
DA
TA
ETH 1
or SNMP communication.
DA
TA
SI
G
AC
T
BITS 1
SI
G
AC
T
RJ-45 cable
Modem connection
AUX
Local terminal or
PERFORMANCE ROUTE PROCESSOR 2
LED status
displays
(alphanumeric)
149695
SUMMARY STEPS
DETAILED STEPS
Where to Go Next
If you have logged into the router or multishelf system, you are ready to perform general router
configuration as described in Chapter 4, “Configuring General Router Features.”
If the router is prompting you to enter a root-system username, bring up the router or multishelf system
as described in the appropriate chapter:
• Chapter 2, “Bringing Up the Cisco IOS XR Software on a Standalone Router”
• Chapter 3, “Bringing Up the Cisco IOS XR Software on a Multishelf System”
This chapter provides instructions for bringing up the Cisco IOS XR software on a standalone router for
the first time. This section applies to standalone routers that are delivered with Cisco IOS XR software
installed.
Note If you are upgrading a Cisco XR 12000 Series Router from Cisco IOS software to
Cisco IOS XR software, see the Cisco IOS XR software document titled Upgrading from Cisco IOS to
Cisco IOS XR Software on the Cisco 12000 Series Router.
Contents
This chapter contains the following sections:
• Prerequisites, page 2-1
• Bringing Up and Configuring a Standalone Router, page 2-2
• Verifying the System After Initial Bring-Up, page 2-4
• Where to Go Next, page 2-8
Prerequisites
The following sections describe the software and hardware requirements for bringing up a standalone
system.
Software Requirements
The system requires the following software:
• Cisco IOS XR Software Release 3.4.0
• ROMMON 1.42 or later version on each RP in the system
Caution The ROM Monitor software must be upgraded to version 1.42 or a later version on all RPs before a
Cisco CRS-1 system is upgraded to Cisco IOS XR Software Release 3.4.0 or a later release. If the router
is brought up with an incompatible version of the ROM Monitor software, then the standby RP may fail
to boot. For instructions to overcome a boot block in the standby RP in a single-chassis system, see
Cisco IOS XR ROM Monitor Guide. If a boot block occurs in a multishelf system, contact your
Cisco Systems support representative for assistance. See Obtaining Technical Assistance, page xiv.
Note If you are upgrading a Cisco 12000 Series Router from Cisco IOS software to Cisco IOS XR software,
you must first prepare the router. Refer to Upgrading from Cisco IOS to Cisco IOS XR Software on the
Cisco 12000 Series Router for more information. See the “Related Documents” section on page x for a
complete listing of available documents.
SUMMARY STEPS
DETAILED STEPS
Examples
The following example shows the root-system username and password configuration for a new router,
and it shows the initial log in:
--- Administrative User Dialog ---
Username: cisco
Password:
RP/0/0/CPU0:ios#
The secret line in the configuration command script shows that the password is encrypted. When you
enter the password during configuration and login, the password is hidden.
SUMMARY STEPS
1. show version
2. admin
show platform [node-id]
end
3. show redundancy
4. show environment
DETAILED STEPS
Example:
RP/0/RP0/CPU0:router# show environment
--More--
0/1/*
host 32, 30 26, 27 35
cpu 34
fabricq0 27
fabricq1 32
ingressq 37
egressq 32 27
ingresspse 35
egresspse 29
jacket 25 24 25
spa0 19 25, 32
spa5 25 24
0/6/*
host 32, 26 27, 25 33
cpu 35
fabricq0 27
fabricq1 32
ingressq 37
egressq 30 25
ingresspse 31
egresspse 29
jacket 24 25 26
spa0 19 25, 31
spa4 22 33, 35
spa5 24 24
0/RP0/*
host 23 24 24, 33, 26,
24, 27
0/RP1/*
host 23 24 24, 32, 26,
24, 26
In the following example, LED status of the nodes in a Cisco CRS-1 router is shown:
RP/0/RP0/CPU0:router# show environment leds
See the Cisco IOS XR Interface and Hardware Component Command Reference for more information.
The following EXEC mode sample output displays the nodes assigned to the default SDR, which is
called the owner SDR:
RP/0/RP0/CPU0:router# show platform
The following administration EXEC mode sample output displays all router nodes:
RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router# end
Note Line cards in Cisco CRS-1 routers are called modular services cards (MSCs). The show platform
command output is different for Cisco CRS-1 routers and Cisco XR 12000 Series Routers.
In the following example, information is shown for a single node in a Cisco CRS-1 router:
For more information on node IDs, see the Cisco IOS XR System Management Configuration Guide,
Release 3.4.
For more information on the show platform command, see the Cisco IOS XR Interface and Hardware
Component Command Reference.
Where to Go Next
For information on configuring basic router features, see Chapter 4, “Configuring General Router
Features.”
This chapter describes how to bring up the Cisco IOS XR software on a Cisco CRS-1 Carrier Routing
System Multishelf System for the first time.
Contents
This chapter contains the following sections:
• Prerequisites, page 3-1
• Restrictions, page 3-2
• Information About Bringing Up a Multishelf System, page 3-3
• Configuring the External Cisco Catalyst 6509 Switches, page 3-8
• Integrated Switch System, page 3-20
• Bringing Up and Configuring Rack 0, page 3-28
• Bringing Up and Verifying FCCs, page 3-34
• Bringing Up and Verifying the Non-DSC LCC, page 3-37
• Verifying the Spanning Tree, page 3-39
• Verifying Fabric Cabling Connections, page 3-43
• Where to Go Next, page 3-47
Prerequisites
The following sections describe the software and hardware requirements for bringing up a multishelf
system.
Software Requirements
The multishelf system requires the following software:
• Cisco IOS XR Software Release 3.4
Caution The ROM Monitor software must be upgraded to version 1.42 or a later version on all RPs before a
Cisco CRS-1 system is upgraded to Cisco IOS XR Software Release 3.4.0 or a later release. If the router
is brought up with an incompatible version of the ROM Monitor software, then the standby RP may fail
to boot. For instructions to overcome a boot block in the standby RP in a single-chassis system, see
Cisco IOS XR ROM Monitor Guide. If a boot block occurs in a multishelf system, contact your
Cisco Systems support representative for assistance. See Obtaining Technical Assistance, page xiv.
In addition, Cisco CRS-1 multishelf systems should be upgraded to ROMMON release 1.40 before being
upgraded to Cisco IOS XR Release 3.4.0 to ensure that RPs are assigned the correct rack numbers during
system boot.
Hardware Requirements
Before you can bring up a multishelf system, the system components must be physically installed and
tested. Three multishelf system configurations are supported, and they require the following
components:
• Two 16-slot line card chassis containing eight FC/M (S13) fabric cards
• Two external Gigabit Ethernet Cisco Catalyst 6509 switches
Single-FCC systems require one FCC containing eight SFC (S2) fabric cards. Two-FCC systems require
two FCCs, and four-FCC systems require four FCCs. In two- and four-FCC configurations, the eight
SFC (S2) fabric cards are distributed equally in the FCCs.
For instructions to install, cable, and verify a multishelf system, see the documents listed on the
Cisco CRS-1 documentation web page listed in the “Related Documents” section on page x.
Restrictions
The following restrictions apply to multishelf systems in Cisco IOS XR Software Release 3.4.0.
• The multishelf system supports:
– Two 16-slot line card chassis.
– One, two, or four FCCs.
– Two external Catalyst switches to form a control Ethernet plane used for administrative
management and monitoring of the system.
• The 4-slot and 8-slot LCCs are not supported.
• Although Cisco IOS XR Software Release 3.4.0 supports the addition of a second line card chassis,
the removal of a line card chassis is restricted. Consult your Cisco Systems support representative
for more information (see the “Obtaining Technical Assistance” section on page xiv).
Bringup Overview
The bringup procedure for a multishelf system starts after the hardware installation is complete. The
bringup procedure tasks configure the system components to work together and verify the operation and
configuration of system components. To bring up the multishelf system, complete the following
procedures in the sequence shown:
1. Configuring the External Cisco Catalyst 6509 Switches, page 3-8
2. Bringing Up and Configuring Rack 0, page 3-28
3. Bringing Up and Verifying FCCs, page 3-34
4. Bringing Up and Verifying the Non-DSC LCC, page 3-37
5. Verifying the Spanning Tree, page 3-39
During the bringup procedure, you need the information presented in the following section.
Caution Failure to assign a unique rack number to each chassis in the system can result in serious system error
and potential downtime. Unique rack numbers must be assigned and committed on Rack 0 before the
additional chassis are powered on and brought on line.
Fabric Cards
OIM-LED 1
OIM-LED 1
OIM23
OIM22
OIM21
OIM16
OIM15
OIM14
OIM13
OIM12
OIM23
OIM22
OIM21
OIM16
OIM15
OIM14
OIM13
OIM12
SM0
SM1
SM2
SM3
SM0
SM1
SM2
SM3
SC
INPUT FAN OUTPUT INPUT FAN OUTPUT INPUT FAN OUTPUT INPUT FAN OUTPUT
OK OK FAIL OK OK FAIL OK OK FAIL OK OK FAIL
OIM-LED 1
RP (SC)
RP (SC)
RP (SC)
RP (SC)
OIM23
OIM22
OIM21
OIM16
OIM15
OIM14
OIM13
OIM12
OIM23
OIM22
OIM21
OIM16
OIM15
OIM14
OIM13
OIM12
SM4
SM7
SM4
SM7
DSC
SC
138118
Line Card Chassis Fabric Card Chassis Line Card Chassis
Rack 1 Rack F0 Rack 0
Note Chassis, shelf, and rack are used interchangeably. Each term refers to the physical tower that contains
the installed cards, power, and cooling equipment. In general, chassis describes the system components.
Rack is used in software to assign a rack number to each chassis.
A rack number plan lists each chassis in a system with the correct chassis serial ID and an assigned rack
number. The serial ID is the chassis serial number, which can be accessed by the software and uniquely
identifies the chassis. The rack number for an LCC is a number in the range of 0 to 255, which is easier
to remember and read than serial numbers in display messages.
The rack number plan is used during the startup and configuration of Rack 0. The LCC that hosts the
DSC must be configured as Rack 0. The non-DSC LCC must be configured to use a rack number in the
range of 1 to 255. FCC rack numbers range from F0 to F3, as shown in Table 3-1, Table 3-2, and
Table 3-3.
Table 3-1 shows a sample rack number plan for a single-FCC system.
Table 3-1 Sample Rack Number Plan for a Single-FCC Multishelf System
Table 3-2 shows a sample rack number plan for a two-FCC system.
Table 3-2 Sample Rack Number Plan for a Two-FCC Multishelf System
Table 3-3 shows a sample rack number plan for a four-FCC system.
Table 3-3 Sample Rack Number Plan for a Four-FCC Multishelf System
To complete the rack number plan, change the rack number for the non-DSC LCC if you want, and record
the serial number for each chassis. The chassis serial number is attached to the back of the chassis, as
shown in Figure 3-2 and Figure 3-3.
SN: XXXNNNNXXXX
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
9
5
1
10
6
2
11
7
3
12
8
4
129761, 781-00375-01
9
5
1
10
6
2
11
7
3
12
8
4
PWR
OK
FLT
AC PWR
FAIL OK
CB
TRIP FLT
I AC
LIM PWR
FAIL OK
OT CB
TRIP FLT
I AC
LIM FAIL
OT CB
TRIP
I
LIM
OT
PWR
OK
FLT
AC PWR
FAIL OK
CB
TRIP FLT
I AC
LIM PWR
FAIL OK
OT CB
TRIP FLT
I AC
LIM FAIL
OT CB
TRIP
I
LIM
OT
SN: AAANNNNXXXX
116535
Caution Always assign a rack number to each chassis in the system before the chassis is booted. If a chassis is
not assigned a rack number, or if the rack number conflicts with an existing chassis, it may not be
recognized by the system or cause other operational difficulties.
If you cannot locate or read the chassis serial number on a chassis, you can view the serial number stored
in software as described in the following documents:
• To display the chassis serial numbers in administration EXEC mode, see Cisco IOS XR System
Management Configuration Guide, Release 3.4.
• To display the configured chassis serial numbers in administration EXEC mode, see Cisco IOS XR
System Management Configuration Guide, Release 3.4.
• To display the chassis serial numbers in ROM Monitor, see Cisco IOS XR ROM Monitor Guide.
See the “Bringing Up and Configuring Rack 0” section on page 3-28 for complete instructions to bring
up a new router and configure the rack numbers.
RP
Catalyst RP
Ethernet Line Card
Switch Chassis
SCGE
SCGE
Fabric Card
Chassis
Catalyst
Ethernet
Switch RP
RP
138147
Line Card
Chassis
Prerequisites
The following sections describe the software and hardware requirements for bringing up Catalyst 6509
switches in a multishelf system.
Software Requirements
Each Cisco Catalyst 6509 switch requires the same software:
• Cisco IOS Release 12.2(14r)S9 with SUP720 Supervisor Engine controller module
• System Bootstrap (ROMMON), Version 1.3 or later
• BOOTLDR: s72033_rp Software (s72033_rp-PSV-M), Version 12.2(17d)SXB7
Both switches should use the same software. The filename of the software is
72033-psv-mz.122-17d.SXB8.bin, and is available on CCO at:
http://www.cisco.com/kobayashi/sw-center/lan/cat6000.shtml
Hardware Requirements
• Two external Cisco Catalyst 6509 switches correctly cabled to the Cisco CRS-1 multishelf router.
• The recommended hardware configuration for an AC-powered Cisco Catalyst 6509 system is shown
in the following table:
Restrictions
The following restrictions apply to Cisco Catalyst 6509 switches that are installed in a multishelf system:
• Both Catalyst switches must operate with the same Cisco IOS software release.
• The spanning tree implementation of Cisco CRS-1 control Ethernet assumes that all Catalyst switch
ports connected to the multishelf system are kept in VLAN 1.
• The Gigabit Interface Converter (GBIC) transceiver module used on the Catalyst switches must
match the SFP optic used on each RP and SCGE card in the system. The GBIC can be either LX/LH
or SX, but the same type must be used on both ends.
Note Both Catalyst switches must be dedicated for use with the multishelf system. The Catalyst switches
should not be used for any other purpose.
Note Configure the primary Catalyst switch with priority 0 to make the switch the root of the network.
Configure the second Catalyst switch with a number greater than 0 and less than 32768. If the primary
Catalyst switch (priority 0) fails, the second switch becomes the root of the network.
SUMMARY STEPS
1. configure
2. spanning-tree portfast default
3. spanning-tree mode mst
4. spanning-tree mst configuration
5. name mst_region
6. revision number
7. instance instance_id vlan range
8. end
9. spanning-tree mst hello-time seconds
10. spanning-tree mst forward-time seconds
11. spanning-tree mst max-age seconds
12. spanning-tree mst max-hops hops
13. spanning-tree mst instance_id priority priority
14. udld aggressive
15. udld message time interval
16. interface gigabitethernet slot/port
17. switchport
18. switchport mode access
DETAILED STEPS
Example:
router# configure
Step 2 spanning-tree portfast default Enables PortFast by default on all access ports.
Example:
router(config)# spanning-tree portfast default
Step 3 spanning-tree mode mst Selects the MST mode for the Spanning Tree Protocol.
Example:
router(config)# spanning-tree mode mst
Step 4 spanning-tree mst configuration Places the router in spanning tree MST configuration
mode.
Example:
router(config)# spanning-tree mst configuration
Step 5 name mst_region Defines a name for an MST region.
Example:
router(config-mst)# name STP_1
Step 6 revision number Sets a revision number for the MST configuration.
• This number must be identical on both switches.
Example:
router(config-mst)# revision 1
Step 7 instance instance_id vlan range Maps the MST instance to a range of VLANs.
Example:
router(config-mst)# instance 1 vlan 1
Step 8 end Exits spanning tree MST configuration mode.
Example:
router(config-mst)# end
Step 9 spanning-tree mst hello-time seconds Sets the hello-time delay timer for all instances on the
switch.
Example: • We recommend 1 second.
router(config)# spanning-tree mst hello-time 1
Note When configuring the Catalyst 6509 switches, the difference between configuring single-, two-, and
four-FCC multishelf systems is the number of interfaces that require configuration. When additional
FCCs are present, additional interfaces must be configured for the connections to those FCCs.
CAT6k-1(config-if)# end
CAT6k-2(config-mst)# revision 1
CAT6k-2(config-mst)# instance 1 vlan 1
CAT6k-2(config-mst)# end
CAT6k-2(config)# spanning-tree mst hello-time 1
CAT6k-2(config)# spanning-tree mst forward-time 6
CAT6k-2(config)# spanning-tree mst max-age 8
CAT6k-2(config)# spanning-tree mst max-hops 4
CAT6k-2(config)# spanning-tree mst 0-1 priority 28672
CAT6k-2(config)# udld aggressive
CAT6k-2(config)# udld message time 7
CAT6k-2(config)# interface gigabitethernet 0/1
CAT6k-2(config-if)# switchport
CAT6k-2(config-if)# switchport mode access
CAT6k-2(config-if)# switchport access vlan 1
CAT6k-2(config-if)# end
Note When configuring the Catalyst 6509 switches, the difference between configuring single-, two-, and
four-FCC multishelf systems is the number of interfaces that require configuration. When additional
FCCs are present, additional interfaces must be configured for the connections to those FCCs.
The following configuration display shows an example configuration for one of the Catalyst 6509
Switches in a four-FCC multishelf system:
Router# show running-config
Building configuration...
instance 1 vlan 1
!
spanning-tree mst hello-time 1
spanning-tree mst forward-time 6
spanning-tree mst max-age 8
spanning-tree mst 0-1 priority 28672
diagnostic cns publish cisco.cns.device.diag_results
diagnostic cns subscribe cisco.cns.device.diag_commands
!
redundancy
mode sso
main-cpu
auto-sync running-config
auto-sync standard
!
vlan internal allocation policy ascending
vlan access-log ratelimit 2000
!
!
interface GigabitEthernet1/1
no ip address
switchport
switchport mode access
spanning-tree portfast
!
interface GigabitEthernet1/2
no ip address
switchport
switchport mode access
spanning-tree portfast
!
interface GigabitEthernet1/3
no ip address
switchport
switchport mode access
spanning-tree portfast
!
interface GigabitEthernet1/4
no ip address
switchport
switchport mode access
spanning-tree portfast
!
interface GigabitEthernet1/5
no ip address
switchport
switchport mode access
spanning-tree portfast
!
interface GigabitEthernet1/6
no ip address
switchport
switchport mode access
spanning-tree portfast
!
interface GigabitEthernet1/7
no ip address
switchport
switchport mode access
spanning-tree portfast
!
interface GigabitEthernet1/8
no ip address
switchport
no ip http server
!
!
!
!
!
line con 0
line vty 0 4
login
!
End
The listed interfaces should include the port to which you have connected. If the port is not listed, contact
Cisco Technical Support. For contact information, see the “Obtaining Technical Assistance” section on
page xiv.
CAT6k-1# show spanning-tree
MST00
MST01
Spanning tree enabled protocol mstp
Root ID Priority 1
Address 0013.1a4f.75c0
This bridge is the root
Hello Time 1 sec Max Age 8 sec Forward Delay 6 sec
Bridge ID Priority 1 (priority 0 sys-id-ext 1)
Address 0013.1a4f.75c0
Hello Time 1 sec Max Age 8 sec Forward Delay 6 sec
Interface Role Sts Cost Prio.Nbr Type
Router#
The output of this command should display “connected.” If it does not, then the connector may have a
partial fiber cut or a bad optic. You may need to jiggle the GBIC wire to ensure that it is firmly inserted.
Re-enter the command show interface until the port displays a status of “connected” or “disabled” for
every port that displays a connector type.
Caution If this problem is not resolved and the Cisco CRS-1 router enters the forwarding state, a loop occurs.
Note When the 22-port SCGE cards are installed, there is no requirement for an external switch device
(Catalyst 6509) to provide control Ethernet connectivity.
For information about the cabling schemes for a single-FCC multishelf system, two-FCC multishelf
system, and four-FCC multishelf system, see Cisco CRS-1 Carrier Routing System Multishelf System
Interconnection and Cabling Guide.
This section includes the following topics:
• Prerequisites for an Integrated Switch System, page 3-20
• Restrictions for an Integrated Switch System, page 3-21
• Before You Begin, page 3-21
• Information About the Integrated Switch Implementation, page 3-21
• Implementing the Integrated Switch System, page 3-23
Software Requirements
• Requires ROMMON 1.43 or higher on all RP and 22-port SCGE nodes. The 22-port SCGE card
comes with ROMMON 1.43 or later version.
Note ROMMON 1.43 is the first ROMMON version to support 22-port SCGE cards and other cards.
• Requires Cisco IOS XR Software Release 3.4.1 to support 22-port SCGE cards.
Hardware Requirements
Route processors (RPs) should be revision 8 or higher. SMF cables are required and LX optics is
recommended.
LED Description
Green Link Up
Blinking Green Activity
Amber Port error disabled Unidirectional Link Detection
(UDLD)
Off Link Down
Type Description
Switch connections The BCM5618s create the intra-rack control network. The BCM5690s
create the inter-rack control network. There are two BCM5690 switches
that are connected through a 10 Gbps stacking link. Port 11 on
BCM5690-sw1 is connected to BCM5618-sw0-GE, which is also referred
to as BCM5618-GE0. This is the link that connects the intra-rack control
network to the inter-rack control network. Port 0 on BCM5618-sw0 is
connected to the control Ethernet port for the CPU.
Port configuration Both BCM5690 switches are configured to forward traffic only to port 11
of BCM5690-sw1 (for example, the CPU bound port). Because forwarding
is not enabled between any other ports on those switches, the switches can
never participate in a loop. The BCM5618s are configured in a very similar
manner by enabling forwarding to only port 0 (CPU port) of BCM5618-sw0
to or from any other port.
The switches on the 22-port SCGE, which are connected to each other, form the core of the network. The
RP connections form the edge (regardless of whether the 22-port SCGEs are connected in a full or partial
mesh). In steady state, the integrated switch network has the root in the core. The root is one of the
22-port SCGEs.The following default priorities are achieved with the RSTP software:
• RP is set to 36864.
• 22-port SCGE is set to 32768.
SUMMARY STEPS
1. admin
2. clear controller switch errdisable {port {FE | GE} {0 | 1}} {location node-id}}
3. clear controller switch inter-rack {errdisable {ports {number | all} | statistics {all | ports
number}} {location node-id}
DETAILED STEPS
Example:
RP/0/RP0/CPU0:router# admin
Step 2 clear controller switch errdisable {port {FE | GE} Clears the err-disable state of the switch port for the
{0 | 1}} {location node-id}} RP ports.
Example:
RP/0/RP0/CPU0:router(admin)# clear controller switch
inter-rack statistics all location f0/sc0/cpu0
To verify the port statistics, use show controllers switch inter-rack statistics command with the detail
and location keywords, as shown in the following example:
RP/0/RP0/CPU0:router(admin)# show controllers switch inter-rack statistics 0 detail
location f0/sc0/cpu0
GE_Port_0
Rx fragment : 0 Tx fragment : 0
Rx unicast : 1642337 Tx unicast : 379927
Rx multicast : 51619 Tx multicast : 205950
Rx broadcast : 91436 Tx broadcast : 150357
Rx FCS error : 0 Tx FCS error : 0
Rx Pause : 0 Tx Pause : 0
Rx Undersize : 0 Tx Oversize : 0
Rx FFP drop : 0 Tx CFI drop : 0
Rx Control frame : 0 Tx Cell error : 0
Tx Jabber : 0
Tx excessive collision: 0
Tx tagged vlan : 0
Tx abort : 0
Verifying Bidirectionality
To verify the bidirection for the integrated switch, you can use the Unidirectional Link Detection
(UDLD) protocol to detect unidirectional links on Ethernet ports. UDLD is a Layer 2 protocol. UDLD
is useful at linkup time. If the link is detected to be unidirectional, the port is shut down. In addition,
UDLD detects unidirectional failures after a port has been up and bidirectional for a certain time. If a
transceiver goes wrong, UDLD protects the control network from faulty transceivers that are plugged
into the control network.
To provide the port information that is disabled (UDLD), use the show controllers switch udld ports
command.
To verify STP information for inter-rack switches, use the show controllers switch inter-rack ports
command, as shown in the following example:
RP/0/RP0/CPU0:router(admin)# show controllers switch inter-rack stp location f0/sc0/cpu0
SUMMARY STEPS
DETAILED STEPS
Example:
RP/0/RP0/CPU0:router# admin
Step 5 configure Places the router in administration configuration mode.
Example:
RP/0/RP0/CPU0:router(admin)# configure
Step 6 dsc serial serial ID rack 0 Defines which LCC is Rack 0.
• The LCC containing the DSC should be configured with
Example:
the lowest rack number.
RP/0/RP0/CPU0:router(admin-config)# dsc
serial TBA00000001 rack 0 • Replace serial ID with the serial number of the LCC you
want to configure as Rack 0.
• See the “Preparing a Rack Number Plan” section on
page 3-3 for information on locating the serial number.
Examples
This section contains examples for the following subjects:
• Example: Configuring and Verifying the Rack Numbers in a Single-FCC Multishelf System, page
3-31
• Example: Mapping Each Fabric Plane in a Single-FCC Multishelf System, page 3-32
• Example: Mapping Each Fabric Plane in a Two-FCC Multishelf System, page 3-32
• Example: Mapping Each Fabric Plane in a Four-FCC Multishelf System, page 3-33
Example: Configuring and Verifying the Rack Numbers in a Single-FCC Multishelf System
In the following example, rack numbers are assigned to each LCC and FCC in administration
configuration mode:
RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# configure
RP/0/RP0/CPU0:router(admin-config)# dsc serial TBA00000001 rack 0
RP/0/RP0/CPU0:router(admin-config)# dsc serial TBA00000002 rack 1
RP/0/RP0/CPU0:router(admin-config)# dsc serial TBA00000003 rack F0
RP/0/RP0/CPU0:router(admin-config)# commit
RP/0/RP0/CPU0:router(admin-config)# show running-config | include dsc
Building configuration...
dsc serial TBA00000003 rack F0
dsc serial TBA00000001 rack 0
dsc serial TBA00000002 rack 1
RP/0/RP0/CPU0:router(admin-config)#
In the following example, each fabric plane is assigned to an FCC slot in administration configuration
mode:
RP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 0
RP/0/RP0/CPU0:router(admin-config)# oim count 1
RP/0/RP0/CPU0:router(admin-config)# oim instance 0 location F0/SM9/FM
RP/0/RP0/CPU0:router(admin-config)# commit
RP/0/RP0/CPU0:router(admin-config)# end
RP/0/RP0/CPU0:router(admin)#
Building configuration...
username admin
secret 5 $1$iGx3$0BI/8hOKRUMqtfWC4IUn50
group root-system
group cisco-support
!
dsc serial TBA09250241 rack 1
dsc serial TBA09270100 rack F0
dsc serial TBA09300128 rack F1
controllers fabric plane 0
oim count 1
oim instance 0 location F0/SM0/FM
!
controllers fabric plane 1
oim count 1
oim instance 0 location F0/SM9/FM
!
controllers fabric plane 2
oim count 1
oim instance 0 location F0/SM12/FM
!
controllers fabric plane 3
oim count 1
oim instance 0 location F0/SM21/FM
!
controllers fabric plane 4
oim count 1
oim instance 0 location F1/SM0/FM
!
controllers fabric plane 5
oim count 1
oim instance 0 location F1/SM91/FM
!
controllers fabric plane 6
oim count 1
oim instance 0 location F1/SM12/FM
!
controllers fabric plane 7
oim count 1
oim instance 0 location F1/SM21/FM
!
end
The following configuration display is an example of a configuration for a four-FCC multishelf system:
RP/0/RP0/CPU0:router(admin)# show running-config
Building configuration...
username admin
secret 5 $1$iGx3$0BI/8hOKRUMqtfWC4IUn50
group root-system
group cisco-support
!
dsc serial TBA09250241 rack 1
dsc serial TBA09270100 rack F0
dsc serial TBA09300128 rack F1
dsc serial TBA09460027 rack F3
dsc serial TBA09460028 rack F2
controllers fabric plane 0
oim count 1
oim instance 0 location F0/SM0/FM
!
controllers fabric plane 1
oim count 1
oim instance 0 location F0/SM9/FM
!
controllers fabric plane 2
oim count 1
oim instance 0 location F1/SM0/FM
!
controllers fabric plane 3
oim count 1
oim instance 0 location F1/SM9/FM
!
controllers fabric plane 4
oim count 1
oim instance 0 location F2/SM0/FM
!
controllers fabric plane 5
oim count 1
oim instance 0 location F2/SM9/FM
!
controllers fabric plane 6
oim count 1
oim instance 0 location F3/SM0/FM
!
controllers fabric plane 7
oim count 1
oim instance 0 location F3/SM9/FM
!
end
SUMMARY STEPS
DETAILED STEPS
Examples
This section contains an example for the following task:
• Verify That All Fabric Planes Are Ready to Handle Data, page 3-36
In the following examples, the fabric planes are examined in administration EXEC mode to ensure that
they are ready to handle traffic.
0 NORMAL PRESENT
1 NORMAL PRESENT
F0 NORMAL PRESENT
RP/0/RP0/CPU0:router(admin)#
SUMMARY STEPS
DETAILED STEPS
SUMMARY STEPS
1. admin
2. show platform
3. show spantree mst 1 detail location rack/slot/cpu0
DETAILED STEPS
Examples
This section contains examples for the following subjects:
• Verify That the FCCs and Non-DSC LCC Are Communicating with the DSC, page 3-40
• Verify the Spanning Tree, page 3-41
Verify That the FCCs and Non-DSC LCC Are Communicating with the DSC
In the following EXEC mode example, all modules are displayed and the state for all modules is
“IOS XR RUN.”
RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# end
Instance 1
Vlans mapped: 1
Instance 1
Vlans mapped: 1
Instance 1
Vlans mapped: 1
Instance 1
Vlans mapped: 1
Instance 1
Vlans mapped: 1
Instance 1
Vlans mapped: 1
Figure 3-5 shows the faceplate of the CRS-FCC- LED panel. The CRS-FCC-LED is also called an
optical interface module (OIM) LED panel. This panel goes into slot LM0 or LM1 in a fabric card
chassis.The OIM LED panel provides connectivity information on how the fabric chassis cards are
functioning in the multishelf system. LEDs 0 through 11 correspond to OIM 0 through OIM 11 (FM 0
through FM 11 in software). Table 3-7 describes the possible states of the LEDs shown in Figure 3-5.
8 4 0
9 5 1
10 6 2
11 7 3
J0
8 4 0
10
9
6
5
2
1 8 4 0
11 7 3
J1
9 5 1
8 4 0
9 5 1
10
11 7
6
3
2
10 6 2
J2
8 4 0
11 7 3
9 5 1
10
11 7
6
3
2
J3
J0
8 4 0
9 5 1
10 6 2
11 7 3
J4
8 4 0
9 5 1
10 6 2
11 7 3
J5
8 4 0
9 5 1
10 6 2
11 7 3
J6
8 4 0
9 5 1
10 6 2
11 7 3
J7
8 4 0
9 5 1
10 6 2
11 7 3
J8
129913
Because the OIM LED panel is present only in the fabric card chassis, the LEDs indicate the status of
the bundles in the fabric card chassis only. Therefore, if a connection is wrong, the equipment assumes
that the connection at the line card chassis is fixed, and the connection at the fabric card chassis is the
one that needs to be relocated to the correct position as indicated by the LEDs.
Bundles are mapped to LEDs as follows:
The OIM LED panel has 9 rows of 12 LEDs— the 9 rows correspond to the 9 connectors for each slot,
and 12 LEDs correspond to the 12 slots in the cage. Separate OIM LED panels provide status for the
upper and lower card cages. The LED rows map to the connector number, and the LEDs in each LED
row map to the slot number.
The following description helps explain the states of LEDs on the OIM LED panel. In Figure 3-6, fabric
cables should connect an LCC S13 card to the FCC S2 card as follows: A0 to J0, A1 to J1, and A2 to J2.
Instead, A1 is incorrectly connected to J2. This incorrect connection causes the LED corresponding to
J2 to blink red, indicating that the cable connection is incorrect. The LED corresponding to J1 blinks
green to show where the misplaced cable should be connected.
Figure 3-6 Illustration of How OIM LED Panel LEDs Map to Bundles and Slots (Single-Module Cabling)
2
1 9 5 6
8 4 0 7
9 5 1 OIM11 OIM0
9 5 1
10 6 2 10 6 2
3 12
11
8
7
4
3
11 7 3
3
9 5 1 J0 J0 A0
10 6 2
8 4 0
11 7 3 8
12 8 4
9 5 1
10
9
6
5
2
1
J1 J1 A1
10 6 2 11 7 3
4 12 8 4
11 7 3
4
10
9
6
5 1
J2 J2 A2
8 4 0
138285
9 5 1
10 6 2
11 7 3
Where to Go Next
For information on configuring basic router features, see Chapter 4, “Configuring General Router
Features.”
This chapter describes how to communicate with the router using the command-line interface (CLI), and
it describes basic Cisco IOS XR software configuration management.
Contents
The chapter contains the following sections:
• Secure Domain Routers, page 4-1
• Connecting and Communicating with the Router, page 4-2
• Logging In to a Router or an SDR, page 4-11
• CLI Prompt, page 4-12
• User Access Privileges, page 4-13
• Navigating the Cisco IOS XR Command Modes, page 4-17
• Managing Configuration Sessions, page 4-23
• Configuring the SDR Hostname, page 4-38
• Configuring the Management Ethernet Interface, page 4-39
• Manually Setting the Router Clock, page 4-44
• Where to Go Next, page 4-46
SDRs perform routing functions in the same manner as a physical router, but share some chassis
resources with the rest of the system. For example, the applications, configurations, protocols, and
routing tables assigned to an SDR belong to that SDR only, but other functions, such as chassis control,
switch fabric, and partitioning, are shared with the rest of the system.
To manage the owner SDR, you must connect to the active RP for the owner SDR. In administration
configuration mode, you can define new SDRs and assign resources to them (such as DRPs, MSCs, and
line cards.) In configuration mode, you can configure the operation of the owner SDR. Although you can
reassign cards from one SDR to another, you cannot configure and manage cards assigned to a
named SDR. To manage cards assigned to a named SDR, you must connect to the appropriate
named SDR.
When you manage a named SDR, you must connect to the active RP for that named SDR. You can
connect to the named SDR using any of the connection methods you use for the owner SDR (for example,
you can connect through the console port or the Management Ethernet interface), and you have control
over only the cards assigned to that named SDR. For example, you cannot configure and manage
interfaces on line cards assigned to the owner SDR or other SDRs unless you connect directly to those
SDRs.
Note Cisco IOS XR Software releases 2, 3, and 3.2 support only one SDR on the Cisco CRS-1 router.
Cisco IOS XR Software Release 3.2 supports multiple SDRs on Cisco XR 12000 Series Routers, and
Cisco IOS XR Software Release 3.3 supports multiple SDRs on the Cisco CRS-1 routers and
Cisco XR 12000 Series Routers. For more information, see Cisco IOS XR System Management
Configuration Guide.
Figure 4-1 Communication Ports on the RP for a Cisco CRS-1 16-Slot Line Card Chassis
RP
RJ-45 cable
Local terminal or
terminal server for
CLI communication Console
AUX
RJ-45 cable
HDD
PC Card
(disk1:)
Primary
116547
Status
The first time a router is started, you must use a direct connection to the DSC Console port to connect
to the router and enter the initial configuration. When you use a direct connection to the Console port,
CLI commands are entered at a terminal or at a computer running terminal emulation software. A direct
Console port connection is useful for entering initial configurations and performing some debugging
tasks.
This chapter describes some of the tasks you might want to perform during your initial configuration.
One of those tasks is the configuration of the Management Ethernet interface, which is described in the
“Configuring the Management Ethernet Interface” section on page 4-39. After the Management Ethernet
interface is configured, most router management and configuration sessions take place over an Ethernet
network connected to the Management Ethernet interface. SNMP agents and the CWI also use the
network connection.
The modem connection can be used for remote communications with the router and serves as an alternate
remote communications path if the Management Ethernet interface fails.
Figure 4-2 Communication Ports on the RP for a Cisco CRS-1 4-Slot and 8-Slot LCCs
RJ-45 cable
Local terminal or
terminal server for
CLI communication Console Terminal connection
PC
CARD User-removable flash disk1
stores installation PIE files
EXT
CLK 1
EXT
CLK 2
LED status
displays
(alphanumeric)
149693
B1
AUX 0
Local terminal or
Remote terminal for
terminal server for
CLI communication
AUX 1
CLI communication
CLASS 1 LASER PRODUCT CLEAN
LASERPRODUKT DER KLASSE 1 CONNECTOR
PRODUIT LASER DE CLASSE 1 WITH ALCOHOL
1 WIPES BEFORE
PRODUCTO LASER CLASE 1 CONNECTING
PIDVID
CPU0
Ethernet
CPU1 CPU1 Console
AUX connection CPU1 connection
Ethernet
Network
Management
Ethernet
connections
for out-of-band
network
communication
Remote CLI, CWI,
XML, or SNMP
communication
CLEI
FDA
SN
CRS-DRP-ACC
PR ST
IM AT
AR US
Y
138093
Figure 4-4 Communication Ports on the PRP-2 for a Cisco XR 12000 Series Router
SL
SL 0
OT
OT
-
-1
Ethernet cable ETH 0
or SNMP communication.
DA
TA
SI
G
AC
T
BITS 1
SI
G
AC
T
RJ-45 cable
Modem connection
AUX
Local terminal or
PERFORMANCE ROUTE PROCESSOR 2
LED status
displays
(alphanumeric)
149695
SUMMARY STEPS
DETAILED STEPS
SUMMARY STEPS
DETAILED STEPS
• Telnet clients can connect to a Telnet server in the router. The Telnet server is disabled by default
and can be enabled with the telnet ipv4 server or telnet ipv6 server command in global
configuration mode.
• Secure Shell (SSH) clients can connect to an SSH server in the router. The SSH server is disabled
by default and can be enabled with the ssh server command in global configuration mode. The SSH
server handles both Secure Shell Version 1 (SSHv1) and SSHv2 incoming client connections for
both IPv4 and IPv6 address families.
To start a Telnet network connection, you start the Telnet client software with a command similar to the
following:
telnet ManagementEthernetInterfaceIPaddress
For specific instructions on connecting to the router through a Telnet or SSH client, see the instructions
for that software.
Ask your system administrator for the IP address of the Management Ethernet interface.
When the Telnet session is established, the router prompts you to log in, as described in the “Logging In
to a Router or an SDR” section on page 4-11.
Username: iosxr
Password: password
RP/0/RP0/CPU0:router#
Note Passwords are case sensitive. If you want to log in to an SDR using a root-system username from the
owner SDR, enter the username in the following format: username@admin. To support admin login,
local database authentication must be enabled with the aaa authentication login remote local
command. For more information, see Cisco IOS XR System Security Configuration Guide.
After you log in, the router displays the CLI prompt, which is described in the “CLI Prompt” section on
page 4-12. The command set that you can use is determined by the privileges assigned to your username.
For information on how privileges are assigned to usernames, see the Cisco IOS XR System Security
Configuration Guide.
CLI Prompt
After you log in, you see the CLI prompt for the Cisco IOS XR software. This prompt identifies the
router or SDR to which you are issuing commands. The CLI prompt represents the path, through the
router, to the CPU that executes the commands you enter. The syntax for the CLI prompt is:
type/rack/slot/module: router-name#. The CLI prompt is described in Table 4-1.
For example, the following prompt indicates that the CLI commands are executed on the RP in rack 0,
slot RP0, by the “CPU0” module on a router named “router:”
RP/0/RP0/CPU0:router#
bgp
ospf
hsrp
isis
route-map
route-policy
static
vrrp
cef
lpts
iep
rib
multicast
mpls-te
mpls-ldp
mpls-static
ouni
fabric
bundle
network
transport
ppp
hdlc
--More--
Note Only the root-system users, root-lr users, or users associated with the WRITE:AAA task ID can
configure task groups. (The root-lr user has the highest level of privileges in an SDR. In previous
releases, SDRs were called logical routers (LRs).)
Although the predefined user groups are sufficient for the needs of most organizations, administrators
can configure their own groups. For more information, see Cisco IOS XR System Security Configuration.
Displaying the User Groups and Task IDs for Your User Account
To display the user groups and task IDs associated with your account, enter the show user command in
EXEC mode. Table 4-3 summarizes the options available for this command.
Command Description
show user Displays your user name.
show user group Displays the user groups assigned to your account.
Command Description
show user tasks Displays the task IDs assigned to your account.
show user all Displays all user groups and task ID information for your
account.
show aaa usergroup group-name Displays the task IDs assigned to a user group.
Examples
To display your username, enter the show user command:
RP/0/RP0/CPU0:router# show user
cisco
To display the tasks assigned to your account and your rights to those tasks, enter the show user tasks
command:
RP/0/RP0/CPU0:router# show user tasks
To display the user groups assigned to your user account, enter the show user group command:
RP/0/RP0/CPU0:router# show user group
root-system
To display the rights assigned to a user group, enter the show aaa usergroup group-name command:
RP/0/RP0/CPU0:router# show aaa usergroup root-system
Login
EXEC mode
Configuration submode
examples
Logical router configuration submode
Interface
configuration submode
Router
configuration submode
Line template
configuration submode
Task group
149947
configuration submode
RP/0/RP0/CPU0:router(config)#
When the router enters interface configuration submode, the prompt changes to include “(config-if)”
after the router name:
RP/0/RP0/CPU0:router(config)# interface POS 0/2/0/0
RP/0/RP0/CPU0:router(config-if)#
EXEC mode enables a basic set of commands to display the operational state of an SDR and the
Cisco IOS XR software. Most CLI commands in EXEC mode do not change the SDR operation.
The most common EXEC commands are show commands (to display SDR configuration or
operational data) and clear commands (to clear or reset SDR counters).
In EXEC mode, you can display the configuration of an SDR but not the configuration of the
system. The difference is that SDRs are defined in administration configuration mode, which is a
submode of administration EXEC mode. SDRs are configured in global configuration mode.
Additional commands are available depending on the access privileges (user groups) assigned to
your username. Minimal privileges also include a small set of EXEC commands for connecting to
remote devices, changing terminal line settings on a temporary basis, and performing basic tests.
Administration EXEC Administration EXEC mode is used to manage system resources. In administration EXEC mode,
you can display the configuration of the system but not the configuration of an SDR. The difference
is that SDRs are defined in administration configuration mode, which is a submode of
administration EXEC mode. SDRs are configured in global configuration mode.
Administration EXEC mode is used primarily to display system-wide parameters, configure the
administration plane over the control Ethernet, and configure SDR. These operations are available
only to users with the required root level access.
From EXEC mode, use the admin command to enter administration EXEC mode:
RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)#
administration Administration configuration mode allows you to create SDRs and assign system resources to
configuration mode SDRs. Multishelf systems are also configured in administration configuration mode.
From administration EXEC mode, use the configure command to enter administration
configuration submode:
RP/0/RP0/CPU0:router(admin)# configure
RP/0/RP0/CPU0:router(admin-config)#
Note The system prompt changes to “router(config)” to indicate that the router is now in global
configuration mode.
Configuration From the global configuration mode, you can also enter other, more specific command modes.
submodes These modes are available based on your assigned access privileges and include protocol-specific,
platform-specific, and feature-specific configuration modes.
In the following example, MPLS LDP configuration mode is entered from global configuration
mode. The prompt for MPLS LDP configuration submode appears as config-ldp. The following
command syntax is used for entering configuration MPLS LDP submode:
RP/0/RP0/CPU0:router#
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# mpls ldp
RP/0/RP0/CPU0:router(config-ldp)
Note The availability of any particular mode depends on the router features and the access rights
of the individual user. For example, a configuration mode for configuring access servers is
not available on most routers.
Interface configuration The interface configuration submode is used to select and configure a hardware interface, such as a
Packet-over-SONET/SDH (POS) interface. To enter interface configuration mode from global
configuration mode, use an interface command. An interface configuration command always
follows an interface global configuration command, which defines the interface type. The following
command syntax is used for entering interface configuration submode:
RP/0/RP0/CPU0:router(config)# interface POS 0/2/0/0
RP/0/RP0/CPU0:router(config-if)#
Router configuration The router configuration submode is used to select and configure a routing protocol, such as BGP,
OSPF, or IS-IS. The following command syntax is used for entering router configuration submode:
RP/0/RP0/CPU0:router(config)# router <protocol> <protocol_options>
Replace protocol with the keyword for the protocol you want to configure. Replace
protocol_options with any keywords and arguments required for that protocol. In the following
example, the router enters the router configuration mode for BGP:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router bgp 140
RP/0/RP0/CPU0:router(config-bgp)#
During normal operation, users do not interact with ROMMON. This mode is accessed only by
manually interrupting the boot process and placing the system in ROMMON. Once in ROMMON,
you can perform ROM Monitor tasks, including reinstallation of the Cisco IOS XR software,
password recovery, and other diagnostic tasks.
The ROM Monitor CLI mode is accessible only from a terminal connected directly to the Console
port of the primary RP, a terminal-modem connection to the AUX port, or through a terminal server.
See Cisco IOS XR ROM Monitor Guide for information and instructions on using ROM Monitor
mode.
--More--
Step 1 Start a session by logging in to the router and entering EXEC mode, as shown in the following example:
router con0_RP0_CPU0 is now available
Username: iosxr
Password:<secret>
RP/0/RP0/CPU0:router#
From EXEC mode you can issue EXEC commands or enter global configuration mode. Examples of
EXEC commands are the show commands used to display system status and clear commands to clear
counters or interfaces.
Step 2 Enter a question mark at the end of the prompt, or after a command, to display the available options:
RP/0/RP0/CPU0:router# show ?
Note The commands available to you depend on the router mode and your user group assignments.
Step 3 If you belong to a user group that has configuration privileges, you can place the router in the global
configuration mode by entering the configure command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)#
Step 4 From global configuration mode, you can place the router in a configuration submode, such as interface
configuration mode or a protocol-specific configuration mode.
In the following example, the router enters interface configuration mode and the user selects a POS
interface for configuration. The command syntax is interface type rack/slot/module/port.
RP/0/RP0/CPU0:router(config)# interface POS 0/2/0/4
RP/0/RP0/CPU0:router(config-if)#
The command mode prompt changes from “(config)” to “(config-if)” and you can now enter
configuration commands for the specified interface.
Step 5 To exit interface configuration mode and return to global configuration mode, enter the exit command.
To return to EXEC mode, enter the end command.
Global
EXEC mode configuration
mode
Stage 1: Stage 2:
Enter configuration "Commit" changes
changes or load a to the running
saved configuration. configuration.
Administration
Administration
configuration
mode
mode
Save configuration
changes to a file.
149946
Global configuration mode is used to configure SDR features, such as routing protocols and interfaces.
Administration configuration mode is used to assign hardware components to SDRs and to configure
multishelf systems.
The following sections describe the management options for configuration sessions:
• Displaying the Active Configuration Sessions, page 4-24
• Starting a Configuration Session, page 4-25
• Starting an Exclusive Configuration Session, page 4-26
• Displaying Configuration Details with show Commands, page 4-26
• Saving the Target Configuration to a File, page 4-33
• Loading the Target Configuration from a File, page 4-33
To view the active SDR configuration sessions, connect to the appropriate SDR and enter the show
configuration sessions command in EXEC mode, as shown in the following example:
RP/0/RP0/CPU0:router# show configuration sessions
If an asterisk (*) appears in the Lock column, the user is using an exclusive configuration session and
you cannot start a configuration session until the exclusive configuration session is closed. For more
information, see the “Starting an Exclusive Configuration Session” section on page 4-26.
Note Configuration sessions for the administration configuration and each SDR are managed independently.
For example, if a user locks the administration configuration, you can still configure an SDR if other
users have not locked a configuration session for that SDR.
Note The target configuration is not a copy of the running configuration; the target configuration contains only
the configuration commands entered during the target configuration session.
While in configuration mode, you can enter all Cisco IOS XR software commands that are supported in
that configuration mode. Each command is added to the target configuration. You can view the target
configuration by entering the show configuration command in configuration mode. The target
configuration is not applied until you enter the commit command, as described in the “Committing
Changes to the Running Configuration” section on page 4-34.
Target configurations can be saved to disk as nonactive configuration files. These saved files can be
loaded, further modified, and committed at a later time. For more information, see the “Saving the Target
Configuration to a File” section on page 4-33.
Examples
This example shows a simple owner SDR configuration session in which the target configuration is
created and previewed in global configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface POS 0/2/0/1
RP/0/RP0/CPU0:router(config-if)# description faq
RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.10.10.10 255.0.0.0
RP/0/RP0/CPU0:router(config-if)# show configuration
Building configuration...
interface POS0/0/0/1
description faq
ipv4 address 10.10.10.10 255.0.0.0
end
The following example shows a simple administration configuration session in which the target
configuration is created and previewed in administration configuration mode:
RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# configure
RP/0/RP0/CPU0:router(admin-config)# sdr test
RP/0/RP0/CPU0:router(admin-config-sdr:test)# location 0/1/SP
RP/0/RP0/CPU0:router(admin-config-sdr:test)# show configuration
Building configuration...
sdr test
location 0/1/SP
!
end
RP/0/RP0/CPU0:router(config)#
Note If the configuration is already locked by another user, the configure exclusive command fails. To display
locked and unlocked configuration sessions, see the “Displaying the Active Configuration Sessions”
section on page 4-24.
To start an exclusive configuration session for the administration configuration, connect to the DSC and
enter the configure exclusive command in administration EXEC mode:
RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# configure exclusive
RP/0/RP0/CPU0:router(admin-config)#
The running configuration is unlocked when the user who started the exclusive configuration session
exits the configuration mode, as described in the “Ending a Configuration Session” section on page 4-37.
In EXEC and global configuration mode, you can view the SDR configuration for the SDR to which you
are connected. When you are connected to the DSC and operating in administration EXEC and
administration configuration mode, you can view the administration configuration, which includes
hardware assignments for SDRs and multishelf systems.
To display the SDR portion of the running configuration, connect to the appropriate SDR and enter the
show running-config command in EXEC or global configuration mode, as shown in the following
example:
RP/0/RP1/CPU0:router(config)# show running-config
Building configuration...
!! Last configuration change at 11:05:38 UTC Mon May 02 2005 by cisco
!
hostname router
logging console debugging
telnet ipv4 server max-servers 5
username iosxr
password 7 011F0706
group root-system
group cisco-support
!
ntp
interface Loopback99
broadcast
!
interface Loopback999
broadcast
!
interface Loopback9999
broadcast
!
authenticate
max-associations 2000
!
interface Loopback0
ipv4 address 10.1.2.3 255.255.0.0
load-interval 0
!
interface Loopback1
ipv4 address 10.4.5.6 255.255.0.0
!
interface Loopback7
load-interval 0
!
interface Loopback2000
load-interval 0
!
interface Loopback2001
load-interval 0
!
interface Loopback2003
load-interval 0
!
interface MgmtEth0/RP1/CPU0/0
ipv4 address 10.11.12.13 255.255.0.0
!
interface POS0/0/0/0
shutdown
!
interface POS0/0/0/1
shutdown
!
interface POS0/0/0/2
shutdown
!
interface POS0/0/0/3
shutdown
!
interface POS0/3/0/0
shutdown
!
interface POS0/3/0/1
shutdown
!
interface POS0/3/0/2
shutdown
!
interface POS0/3/0/3
shutdown
!
interface preconfigure MgmtEth0/RP0/CPU0/0
shutdown
!
router static
address-family ipv4 unicast
0.0.0.0/0 MgmtEth0/RP1/CPU0/0
!
!
end
To display the administration portion of the running configuration, connect to the DSC and enter the
show running-config command in administration EXEC or administration configuration mode, as
shown in the following example:
RP/0/RP0/CPU0:router(admin)# show running-config
Building configuration...
sdr test
location 0/1/* primary
!
username cisco
secret 5 $1$SegP$9jcoyk09S5cM.h/tX36yj.
group root-system
!
end
Building configuration...
!! Last configuration change at 11:05:38 UTC Mon May 02 2005 by <removed>
!
hostname <removed>
logging console debugging
telnet ipv4 server max-servers 5
username <removed>
password 7 <removed>
group root-system
group cisco-support
!
ntp
interface Loopback99
broadcast
!
interface Loopback999
broadcast
!
interface Loopback9999
broadcast
!
authenticate
max-associations 2000
!
interface Loopback0
ipv4 address 10.0.0.0 255.0.0.0
load-interval 0
!
interface Loopback1
ipv4 address 10.0.0.0 255.0.0.0
!
interface Loopback7
load-interval 0
!
interface Loopback2000
load-interval 0
!
interface Loopback2001
load-interval 0
!
interface Loopback2003
load-interval 0
!
interface MgmtEth0/RP1/CPU0/0
ipv4 address 10.0.0.0 255.0.0.0
!
interface POS0/0/0/0
shutdown
!
interface POS0/0/0/1
shutdown
!
interface POS0/0/0/2
shutdown
!
interface POS0/0/0/3
shutdown
!
interface POS0/3/0/0
shutdown
!
interface POS0/3/0/1
shutdown
!
interface POS0/3/0/2
shutdown
!
interface POS0/3/0/3
shutdown
!
interface preconfigure MgmtEth0/RP0/CPU0/0
shutdown
!
router static
address-family ipv4 unicast
0.0.0.0/0 MgmtEth0/RP1/CPU0/0
!
!
end
To display the sanitized administration portion of the running configuration, connect to the DSC and
enter the show running-config sanitized command in administration EXEC or administration
configuration mode, as shown in the following example:
RP/0/RP0/CPU0:router(admin)# show running-config sanitized
Building configuration...
sdr <removed>
location 0/1/* primary
!
username <removed>
secret 5 <removed>
group root-system
!
end
Building configuration...
interface POS0/3/0/3
description faq
ipv4 address 10.1.1.1 255.0.0.0
end
To display the target administration configuration changes you have entered, enter the show
configuration command in administration configuration mode or in any submode, as shown in the
following example:
RP/0/RP0/CPU0:router(admin-config-sdr:test)# show configuration
Building configuration...
sdr test
location 0/1/* primary
!
end
Note The merge option does not appear in command help until the target configuration contains at least one
configuration change.
The following example shows how to display the active SDR configuration (show running-config),
configure an interface, and display the “merged” configuration:
RP/0/RP0/CPU0:router# show running-config
Building configuration...
!! Last configuration change at 16:52:49 UTC Sun March 10 2004 by cisco
!
hostname router
shutdown
end
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface POS 0/3/0/3
RP/0/RP0/CPU0:router(config-if)# description faq
RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.1.1.1 255.0.0.0
Note You can view configuration errors only during the current configuration session. If you exit
configuration mode after the commit operation, the configuration error information is lost.
In the following example, an error is introduced in global configuration mode and the error information
is displayed after the commit operation fails:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# taskgroup bgp
RP/0/RP0/CPU0:router(config-tg)# description this is a test of an invalid taskgroup
RP/0/RP0/CPU0:router(config-tg)# commit
% Failed to commit one or more configuration items. Please use 'show configurati
on failed' to view the errors
Note You can view configuration errors only during the current configuration session. If you exit
configuration mode after the commit operation, the configuration error information is lost.
Note You can also save a configuration to a file using the show configuration | file filename command.
Loading.
77 bytes parsed in 1 sec (76)bytes/sec
Building configuration...
interface POS0/3/0/1
description this is my interface
ipv4 address 10.1.1.1 255.0.0.0
shutdown
end
RP/0/RP0/CPU0:router(config)# clear
RP/0/RP0/CPU0:router(config)# show configuration
Building configuration...
end
Note If you try to end a configuration session without saving your changes to the running configuration with
the commit command, you are prompted to save the changes. See the “Ending a Configuration Session”
section on page 4-37 for more information.
To commit target configuration changes to the running configuration, enter the commit command by
itself or with one or more of the options described in Table 4-5.
Command Description
commit (Default) Merges the target configuration with the running configuration
and commits changes only if all changes in the target configuration pass
the semantic verification process. If any semantic errors are found, none
of the configuration changes takes effect.
commit best-effort Merges the target configuration with the running configuration and
commits only valid changes (best effort). Some configuration changes
might fail due to semantic errors.
commit comment line (Optional) Assigns a comment to a commit.
• This text comment is displayed in the commit entry displayed with
the show configuration commit list [detail] command.
• The line argument is the text for the optional comment or label.
• The comment option must appear at the end of the command line. If
multiple options are entered, all text after the comment option is
treated as a comment.
commit confirmed (Optional) Commits the configuration in global configuration mode on a
seconds trial basis for a minimum of 30 seconds and a maximum of 300 seconds
(5 minutes).
• During the trial configuration, enter commit to confirm the
configuration. If you do not enter the commit command, the router
reverts to the previous configuration when the trial time period
expires.
• The confirmed option is not available in administration
configuration mode.
commit label line (Optional) Assigns a meaningful label. This label is displayed in the
output for the show configuration commit list [detail] command instead
of the numeric label.
• The line argument is the text for the optional comment or label.
commit force (Optional) Merges the target configuration with the running
configuration and allows a configuration commit in low-memory
conditions.
A low-memory warning occurs when a user attempts to commit a target
configuration that exceeds the default capacity of the router.
The recommended resolution to such a warning is to remove
configurations using the no commands.
Caution The force option can cause the router to experience severe
problems if low-memory conditions occur. The force option
should be used only to remove configurations.
commit replace (Optional) Replaces the contents of the running configuration with the
target configuration.
Examples
In the following example, the default commit command is entered in global configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface POS 0/0/0/2
RP/0/RP0/CPU0:router(config-if)# description faq
RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.1.1.1 255.0.0.0
RP/0/RP0/CPU0:router(config-if)# commit
Note The preceding message is stored in the log and appears only if logging is configured to display on screen.
In the next example, the commit command is entered with the label and comment options in
administration configuration mode:
RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# configure
RP/0/RP0/CPU0:router(admin-config)# sdr test
RP/0/RP0/CPU0:router(admin-config-sdr:test)# location 0/1/* primary
RP/0/RP0/CPU0:router(admin-config-sdr:test)# commit label test comment This is a test
RP/0/RP0/CPU0:router(admin-config)# show configuration commit list detail
Note Configuration files are stored on the same flash disk as the boot image. Access these configurations only
through the CLI commands for configuration management, history, and rollback. Direct modification or
deletion of these files can result in lost router configurations.
Building configuration...
taskgroup bgp
!
end
In the preceding example, the show configuration command displays the target configuration, which
includes the failed configuration.
Note The failed configuration is discarded if you exit global configuration mode or administration
configuration mode without recovering the configuration. After recovery, correct and commit the
configuration or save it to a file to avoid losing it.
Note If you use the exit command to exit global configuration or administration configuration mode, the
router prompts you to save changes, discard changes, or cancel the action, as described in the next
section.
Note If you enter the exit command in a configuration submode, the command returns you to the parent
configuration level.
If you end a configuration session without committing the configuration changes, the router prompts you
to save changes, discard changes, or cancel the action, as shown in the following example:
RP/0/RP0/CPU0:router(config-if)# end
Note In EXEC mode, the exit command logs the user out of the system.
Note No blanks or spaces are permitted as part of a name. Do not expect case to be preserved. Upper- and
lowercase characters look the same to many Internet software applications. It may seem appropriate to
capitalize a name the same way you might if you were writing, but conventions dictate that computer
names appear all lowercase. For more information, see RFC 1178, Choosing a Name for Your Computer.
Table 4-6 provides examples of Management Ethernet interface names for a single-shelf system.
--------------------------------------------------------------------------------
Tip For information on additional configuration options for the Management Ethernet interface, see
Cisco IOS XR Interface and Hardware Component Configuration Guide.
Prerequisites
To configure the Ethernet Management port for network communications, you must enter the interface
network addresses and subnet mask. Consult your network administrator or system planner for this
information.
SUMMARY STEPS
1. configure
2. interface MgmtEthrack/slot/CPU0/port
3. ipv4 address ipv4-address subnet-mask
4. no shutdown
5. exit
6. router static address-family ipv4 unicast 0.0.0.0/0 default-gateway
7. commit
8. end
9. show interfaces MgmtEthrack/slot/CPU0/port
DETAILED STEPS
Example:
RP/0/RP0/CPU0:router# configure
Step 2 interface MgmtEthrack/slot/CPU0/port Enters interface configuration mode and specifies the
Management Ethernet interface of the primary RP.
Example: • The syntax is
RP/0/RP0/CPU0:router(config)# interface interface typerack/slot/module/port:
MgmtEth0/RP0/CPU0/0
The command parameters are described in Table 4-6.
Step 3 ipv4 address ipv4-address subnet-mask Assigns an IP address and subnet mask to the interface.
Example:
RP/0/RP0/CPU0:router(config-if)# ipv4 address
10.1.1.1 255.0.0.0
Step 4 no shutdown Places the interface in an “up” state.
Example:
RP/0/RP0/CPU0:router(config-if)# no shutdown
Step 5 exit Exits the Management Ethernet interface configuration
mode.
Step 6 router static address family ipv4 unicast Configures a default route to use for communications with
0.0.0.0/0 default-gateway devices on other networks.
• Replace default-gateway with the IP address of the
Example: local gateway that can be used to reach other
RP/0/RP0/CPU0:router (config)# router static networks.
address-family ipv4 unicast 0.0.0.0/0 12.25.0.1
• This default route applies to all interfaces. You might
need to configure additional static routes to support
your network. For more information on configuring
static routes, see Cisco IOS XR Routing
Configuration Guide.
Step 7 commit Commits the target configuration to the running
configuration.
Example:
RP/0/RP0/CPU0:router(config)# commit
Example:
RP/0/RP0/CPU0:router# show interfaces
MgmtEth0/RP0/CPU0/0
Examples
In the following example, the Management Ethernet interface on the RP in slot RP1 is configured with
an IP address:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface MgmtEth0/RP1/CPU0/0
RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.1.1.1 255.255.255.0
RP/0/RP0/CPU0:router(config-if)# no shutdown
RP/0/RP0/CPU0:router(config-if)# commit
RP/0/RP0/CPU0:router(config-if)# end
RP/0/RP0/CPU0:router#
RP/0/RP0/CPU0:router# show interfaces mgmtEth 0/RP0/CPU0/0
Related Documents
SUMMARY STEPS
1. configure
2. clock timezone zone hours-offset
3. commit
4. end
5. clock set hh:mm:ss dd mm yyyy
6. clock update-calendar
7. show clock
DETAILED STEPS
Example:
RP/0/RP0/CPU0:router# configure
Step 2 clock timezone zone hours-offset Sets the time zone for the router clock.
• The clock timezone command should be entered
Example: before the clock is set because it defines the difference
RP/0/RP0/CPU0:router(config)# clock timezone between the system time and UTC.
pst -8
Note The system time is the time that appears when you
enter the show clock command.
Example:
RP/0/RP0/CPU0:router(config-if)# end
Step 5 clock set hh:mm:ss dd mm yyyy Sets the system software clock.
Example:
RP/0/RP0/CPU0:router# clock set 14:12:00 10 feb
2004
Step 6 clock update-calendar Updates the hardware clock (calendar clock) with the new
clock settings.
Example: • The hardware clock is battery operated and runs
RP/0/RP0/CPU0:router# clock update-calendar continuously, even if the router is powered off or
rebooted.
Step 7 show clock Displays the clock setting.
• Use this command to verify the settings.
Example:
RP/0/RP0/CPU0:router# show clock
Examples
In the following example, the manual system clock is configured:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# clock timezone pst -8
RP/0/RP0/CPU0:router(config)# commit
RP/0/RP0/CPU0:router(config)# end
RP/0/RP0/CPU0:router# clock set 14:12:00 10 feb 2004
14:12:00.090 PST Tue Feb 10 2004
RP/0/RP0/CPU0:router# clock update-calendar
RP/0/RP0/CPU0:router# show clock
14:12:00.090 PST Tue Feb 10 2004
Related Documents
Related Topic Document Title
Descriptions of the clock commands available in the Cisco IOS XR System Management Command
Cisco IOS XR software Reference
Commands used to configure the NTP Cisco IOS XR System Management Command
Reference
Configuration of the NTP on the Cisco IOS XR software Cisco IOS XR System Management Configuration
Guide
Where to Go Next
When you have completed the configuration procedures in this chapter, consider the following resources
for additional configuration documentation:
• For information on configuring additional general router features, see Chapter 5, “Configuring
Additional Router Features.”
• For information on using the Cisco IOS XR software more efficiently, see Chapter 6, “CLI Tips,
Techniques, and Shortcuts.”
• For information on configuring interfaces, see the hardware documents listed in the “Related
Documents” section on page x.
This chapter contains instructions and information for entering basic configurations using the
command-line interface (CLI).
Contents
This chapter contains the following sections:
• Configuring the Domain Name and Domain Name Server, page 5-1
• Configuring Telnet, HTTP, and XML Host Services, page 5-2
• Managing Configuration History and Rollback, page 5-3
• Configuring Logging and Logging Correlation, page 5-9
• Creating and Modifying User Accounts and User Groups, page 5-13
• Configuration Limiting, page 5-16
SUMMARY STEPS
1. configure
Examples
In the following example, the domain name and DNS are configured:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# domain name cisco.com
RP/0/RP0/CPU0:router(config)# domain name-server 10.1.1.1
RP/0/RP0/CPU0:router(config)# commit
RP/0/RP0/CPU0:router(config)# end
RP/0/RP0/CPU0:router# show hosts
Related Documents
Prerequisites
The following prerequisites must be met before configuring the Telnet, HTTP, and XML host services:
• For the XML and HTTP host services, the Manageability package must be installed and activated
on the router.
• To enable the Secure Socket Layer (SSL) of the HTTP and XML services, the Security package must
be installed and activated on the router.
See Cisco IOS XR System Management Configuration Guide, Release 3.4 for information on installing
and activating packages.
SUMMARY STEPS
1. configure
2. telnet ipv4 server max-servers 5
3. telnet ipv6 server max-servers 5
4. http server
5. xml agent corba
6. commit
Examples
In the following example, the host services are enabled:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# telnet ipv4 server max-servers 5
RP/0/RP0/CPU0:router(config)# telnet ipv6 server max-servers 5
RP/0/RP0/CPU0:router(config)# http server
RP/0/RP0/CPU0:router(config)# xml agent corba
RP/0/RP0/CPU0:router(config)# commit
Related Documents
The Cisco IOS XR software automatically saves up to 100 of the most recent commitIDs. The following
sections describe how to manage configuration changes and roll back to a previously committed
configuration:
• Displaying the CommitIDs, page 5-4
• Displaying the Configuration Changes Recorded in a CommitID, page 5-4
• Previewing Rollback Configuration Changes, page 5-5
• Rolling Back the Configuration to a Specific Rollback Point, page 5-6
• Rolling Back the Configuration over a Specified Number of Commits, page 5-6
• Loading CommitID Configuration Changes to the Target Configuration, page 5-7
• Loading Rollback Configuration Changes to the Target Configuration, page 5-8
• Deleting CommitIDs, page 5-8
RP/0/RP1/CPU0:router# admin
RP/0/RP1/CPU0:router(admin)# show configuration commit list
2000000021 Commit ID
2000000022 Commit ID
Building configuration...
username cisco
secret 5 $1$MgUH$xzUEW6jLfyAYLKJE.3p440
group root-system
!
end
1000000217 Commit ID
1000000218 Commit ID
1000000219 Commit ID
Building configuration...
no interface Loopback100
interface POS0/1/0/0
no ipv6 nd dad attempts
!
!
no route-policy xx
end
To display the prospective rollback configuration changes from the current configuration to a specified
number of previous sessions, go to EXEC or administration EXEC mode and enter the show
configuration rollback changes last commit-range command:
RP/0/RP0/CPU0:router# show configuration rollback changes last 2
Building configuration...
interface Loopback3
no description
no ipv4 address 10.0.1.1 255.0.0.0
exit
interface Loopback4
no description
no ipv4 address 10.0.0.1 255.0.0.0
end
In the preceding example, the command display shows the proposed rollback configuration changes for
the last two commit IDs.
Tip To preview the commands that undo the configuration during a rollback, use the show configuration
rollback changes command.
Tip To preview the commands that undo the configuration during a rollback, use the show configuration
rollback changes command.
To roll back to the last x commits made, go to EXEC or administration EXEC mode and enter the
rollback configuration last x command; x is a number ranging from 1 to the number of saved commits
in the commit database.
In the following example, a request is made to roll back the configuration changes made during the
previous two commits:
RP/0/RP0/CPU0:router# rollback configuration last 2
Note Unlike the rollback process, loading the commitID configuration changes loads only the changes made
during that commit operation. The load process does not load all changes made between the commitID
and the current committed configuration.
RP/0/RP1/CPU0:router# config
Building configuration...
interface Loopback100
!
interface POS0/1/0/0
ipv6 nd dad attempts 50
!
end
Tip To display the rollback changes, enter the show configuration rollback changes command.
To load rollback configuration changes from the current configuration to a specific session, go to global
configuration or administration configuration mode and enter the load rollback changes to commitId
command:
RP/0/0/CPU0:router(config)# load rollback changes to 1000000068
Building configuration...
Loading.
233 bytes parsed in 1 sec (231)bytes/sec
To load rollback configuration changes from the current configuration to a specified number of previous
sessions, go to global configuration or administration configuration mode and enter the load rollback
changes last commit-range command:
RP/0/0/CPU0:router(config)# load rollback changes last 6
Building configuration...
Loading.
221 bytes parsed in 1 sec (220)bytes/sec
In the preceding example, the command loads the rollback configuration changes for the last six
commitIDs.
To load the rollback configuration for a specific commitID, go to global configuration or administration
configuration mode and enter the load rollback changes commitId command:
RP/0/0/CPU0:router(config)# load rollback changes 1000000060
Building configuration...
Loading.
199 bytes parsed in 1 sec (198)bytes/sec
Deleting CommitIDs
You can delete the oldest configuration commitIDs by entering the clear configuration commit
command in EXEC or administration EXEC mode. The clear configuration commit command must be
followed by either the amount of disk space you want to reclaim or number of commitIDs you want to
delete. To reclaim disk space from the oldest commitIDs, enter the clear configuration commit
command followed by the keyword diskspace and number of kilobytes to reclaim:
RP/0/0/CPU0:router# clear configuration commit diskspace 50
To delete a specific number of the oldest commitIDs, enter the clear configuration commit command
followed by the keyword oldest and number of commitIDs to delete:
You can log messages based on the severity level of the messages, as shown in Table 5-2.
Table 5-2 Logging Severity Levels for System Error Messages
Level Description
Level 0—Emergencies System has become unusable.
Level 1—Alerts Immediate action needed to restore system stability.
Level 2—Critical Critical conditions that may require attention.
Level 3—Errors Error conditions that may help track problems.
Level 4—Warnings Warning conditions that are not severe.
Level 5—Notifications Normal but significant conditions that bear notification.
Level 6—Informational Informational messages that do not require action.
Level 7—Debugging Debugging messages are for system troubleshooting only.
SUMMARY STEPS
1. configure
2. logging {ip-address | hostname}
3. logging trap severity
4. logging console [severity]
5. logging buffered [severity | buffer-size]
6. commit
7. end
8. show logging
DETAILED STEPS
Example:
RP/0/RP0/CPU0:router# configure
Step 2 logging {ip-address | hostname} Specifies a syslog server host to use for system logging.
Example:
RP/0/RP0/CPU0:router(config)# logging 10.1.1.1
Step 3 logging trap severity Limits the logging of messages sent to syslog servers to
only those messages at the specified level.
Example: • See Table 5-2 for a summary of the logging severity
RP/0/RP0/CPU0:router(config)# logging trap debugging levels.
Step 4 logging console [severity] Logs messages on the console.
• When a severity level is specified, only messages at
Example: that severity level are logged on the console.
RP/0/RP0/CPU0:router(config)# logging console • See Table 5-2 for a summary of the logging severity
emergencies levels.
Step 5 logging buffered [severity | buffer-size] Copies logging messages to an internal buffer.
• Newer messages overwrite older messages after the
Example: buffer is filled.
RP/0/RP0/CPU0:router(config)# logging buffered
1000000
• Specifying a severity level causes messages at that
level and numerically lower levels to be logged in an
internal buffer. See Table 5-2 for a summary of the
logging severity levels.
• The buffer size is from 4096 to 4,294,967,295 bytes.
Messages above the set limit are logged to the
console.
Step 6 commit Commits the target configuration to the router running
configuration.
Example:
RP/0/RP0/CPU0:router(config)# commit
Step 7 end Ends the configuration session and returns to EXEC
mode.
Example:
RP/0/RP0/CPU0:router(config)# end
Step 8 show logging Displays the messages that are logged in the buffer.
Example:
RP/0/RP0/CPU0:router# show logging
Examples
Related Documents
For more information on message logging and configuration of alarm correlation, see the following Cisco
documents:
Note The management of user accounts, user groups, and task IDs is part of the “AAA” feature in the
Cisco IOS XR software. AAA stands for “authentication, authorization, and accounting,” a suite of
security features included in the Cisco IOS XR software. For more information on the AAA concepts
and configuration tasks, see Cisco IOS XR System Security Configuration Guide and Cisco IOS XR
System Security Command Reference. For instructions to activate software packages, see Cisco IOS XR
System Management Configuration Guide, Release 3.4.
Displaying Details About User Accounts, User Groups, and Task IDs
Table 5-3 summarizes the EXEC mode commands used to display details about user accounts, user
groups, and task IDs.
Table 5-3 Commands to Display Details About Users and User Groups
Command Description
show aaa userdb username Displays the task IDs and privileges assigned to a specific username. To display
all users on the system, enter the command without a username.
show aaa usergroup usergroup-name Displays the task IDs and privileges that belong to a user group. To display all
groups on the system, enter the command without a group name.
show task supported Displays all task IDs for the system. Only the root-system users, root-lr users, or
users associated with the WRITE:AAA task ID can configure task groups.
EXEC mode
usergroup usergroup-name
User group configuration submode
taskgroup taskgroup-name
116542
Task group configuration submode
SUMMARY STEPS
1. configure
2. username user-name
3. password {0 | 7} password
or
secret {0 | 5} password
4. group group-name
5. Repeat Step 4 for each user group to be associated with the user specified in Step 2.
6. commit
DETAILED STEPS
Example:
RP/0/RP0/CPU0:router# configure
Step 2 username user-name Creates a name for a new user (or identifies a current user)
and enters username configuration submode.
Example: • The user-name argument can be only one word. Spaces
RP/0/RP0/CPU0:router(config)# username user1 and quotation marks are not allowed.
Step 3 password {0 | 7} password Specifies a password for the user named in Step 2.
or
• Use the secret command to create a secure login
secret {0 | 5} password password for the user names specified in Step 2.
• Entering 0 following the password command specifies
Example: that an unencrypted (clear-text) password follows.
RP/0/RP0/CPU0:router(config-un)# password 0 Entering 7 following the password command specifies
pwd1
that an encrypted password follows.
or
• Entering 0 following the secret command specifies that
RP/0/RP0/CPU0:router(config-un)# secret 5 pwd1
a secure unencrypted (clear-text) password follows.
Entering 5 following the secret command specifies that
a secure encrypted password follows.
• Type 0 is the default for the password and secret
commands.
Step 4 group group-name Assigns the user named in Step 2 to a user group.
• The user takes on all attributes of the user group, as
Example: defined by the user group association to various task
RP/0/RP0/CPU0:router(config-un)# group sysadmin groups.
• Each user must be assigned to at least one user group.
A user may belong to multiple user groups.
Step 5 Repeat Step 4 for each user group to be associated with —
the user specified in Step 2.
Step 6 commit Saves configuration changes and activates them as part of
the running configuration.
Example:
RP/0/RP0/CPU0:router(config-un)# commit
Related Documents
For more information on configuration and management of users and user access privileges, see the
following Cisco documents:
Configuration Limiting
The Cisco IOS XR software places preset limits on the configurations you can apply to the running
configuration of a router. These limits ensure that the router has sufficient system resources (such as
RAM) for normal operations. Under most conditions, these preset limits are sufficient.
In some cases, for which a large number of configurations is required for a particular feature, it may be
necessary to override the preset configuration limits. This override can be done only if configurations
for another feature are low or unused. For example, if a router requires a large number of BGP
configurations and Multiprotocol Label Switching (MPLS) is not being used at all, then the BGP limits
can be increased to use the unused memory assigned to MPLS.
Caution Overriding the default configuration limits can result in a low-memory condition.
The following sections describe the limits you can configure, default and maximum values, and
commands for configuring and displaying the configuration limits:
• Static Route Configuration Limits, page 5-16
• IS-IS Configuration Limits, page 5-17
• OSPFv2 and v3 Configuration Limits, page 5-17
• BGP Configuration Limits, page 5-20
• Routing Policy Language Line and Policy Limits, page 5-21
• Multicast Configuration Limits, page 5-23
• MPLS Configuration Limits, page 5-23
Examples
In the following example, the maximum number of static IPv4 routes is changed to 5000 and the new
configuration is displayed.
RP/0/RP1/CPU0:router# configure
RP/0/RP1/CPU0:router(config)# router static
RP/0/RP1/CPU0:router(config-static)# maximum path ipv4 5000
RP/0/RP1/CPU0:router(config-static)# commit
router static
maximum path ipv4 5000
address-family ipv4 unicast
0.0.0.0/0 172.29.52.1
!
!
Examples
In the following example, the maximum number of active parallel paths for each route is increased to
10, and the maximum number of prefixes redistributed into IS-IS is increased to 12,000:
RP/0/RP1/CPU0:router# configure
RP/0/RP1/CPU0:router(config)# router isis 100 address-family ipv4
RP/0/RP1/CPU0:router(config-isis-af)# maximum-paths 10
RP/0/RP1/CPU0:router(config-isis-af)# maximum-redistributed-prefixes 12000
RP/0/RP1/CPU0:router(config-isis-af)# commit
RP/0/RP1/CPU0:Mar 30 14:11:07 : config[65739]: %LIBTARCFG-6-COMMIT : Configurati
on committed by user 'cisco'. Use 'show configuration commit changes 1000000535' to view
the changes.
RP/0/RP1/CPU0:router(config-isis-af)#
Default Absolute
Feature Limit Maximum Maximum Configuration Command Show Current Settings Command
Description Limit Limit (Router Configuration Mode) (EXEC Mode)
Maximum number of 255 1024 maximum interfaces n show ospf
interfaces that can be
configured for an
OSPF instance
Maximum routes 10,000 28,672 maximum redistributed-prefixes show ospf
redistributed into n Note The maximum number of
OSPF redistributed prefixes is
displayed only if
redistribution is configured.
Maximum number of 32 32 maximum paths n show running-config router ospf
parallel routes (OSPFv2)
Note This command shows only
(maximum paths) on
16 changes to the default value.
Cisco CRS-1 routers
(OSPFv3) If the maximum paths
command does not appear,
the router is set to the default
value.
Maximum number of 16 16 maximum paths n show running-config router ospf
parallel routes
Note This command shows only
(maximum paths) on a
changes to the default value.
Cisco XR 12000
If the maximum paths
Series Router
command does not appear,
the router is set to the default
value.
Examples
The following subsections provide the following examples:
• Maximum Interfaces for Each OSPF Instance, page 5-18
• Maximum Routes Redistributed into OSPF, page 5-19
• Number of Parallel Links (max-paths), page 5-19
In the following example, the show ospf command is used to display the maximum number of OSPF
interfaces:
RP/0/RP1/CPU0:router# show ospf
In the following example, the maximum redistributed-prefixes command is used to set the maximum
routes redistributed into OSPF:
RP/0/RP1/CPU0:router# configure
RP/0/RP1/CPU0:router(config)# router ospf 100
RP/0/RP1/CPU0:router(config-router)# maximum redistributed-prefixes 12000
RP/0/RP1/CPU0:router(config-router)# end
Uncommitted changes found, commit them? [yes]: y
In the following example, the maximum paths command is used to set the maximum number of parallel
routes:
RP/0/RP1/CPU0:router# configure
RP/0/RP1/CPU0:router(config)# router ospf 100
RP/0/RP1/CPU0:router(config-router)# maximum paths 10
RP/0/RP1/CPU0:router(config-router)# end
Uncommitted changes found, commit them? [yes]: y
Default Absolute
Maximum Maximum Configuration Command Show Current Settings Command
Feature Limit Description Limit Limit (Router Configuration Mode) (EXEC Mode)
Maximum number of neighbors 1024 1024 None. This limit cannot be None
(peers) changed or exceeded.
IPv4 unicast maximum prefixes 524,288 4,294,967, maximum-prefix n show bgp neighbor IP_address
that can be received from a 295
neighbor
IPv4 multicast maximum prefixes 131,072 4,294,967, maximum-prefix n show bgp neighbor IP_address
that can be received from a 295
neighbor
IPv6 unicast maximum prefixes 131,072 4,294,967, maximum-prefix n show bgp neighbor IP_address
that can be received from a 295
neighbor
Maximum equal-cost parallel 1 8 maximum-paths n show running-config
routes to external peers
Note This command shows
only changes to the
default value. If the
maximum paths
command does not
appear, the router is set
to the default value.
A cease-notification message is sent to the neighbor and the peering with the neighbor is terminated
when the number of prefixes received from the peer for a given address family exceeds the maximum
limit (either set by default or configured by the user) for that address family.
However, if the warning-only keyword (for the maximum-prefix command) is configured, the
Cisco IOS XR software sends only a log message, but continues peering with the sender. If the peer is
terminated, the peer stays down until the clear bgp command is issued.
The same set of actions (sending cease notification followed by the termination of the peering) is taken
for a neighbor with which peering has already been established if you decide to configure a maximum
that is less than the number of prefixes that have already been received from the neighbor.
Examples
The following example shows how to set the BGP configuration limits:
RP/0/RP1/CPU0:router# configure
RP/0/RP1/CPU0:router(config)# router bgp 100
RP/0/RP1/CPU0:router(config-bgp)# neighbor 10.1.1.1
RP/0/RP1/CPU0:router(config-bgp-nbr)# remote-as 1
RP/0/RP1/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast
RP/0/RP1/CPU0:router(config-bgp-nbr-af)# maximum-paths 4
RP/0/RP1/CPU0:router(config-bgp-nbr-af)# maximum-prefix 100000
RP/0/RP1/CPU0:router(config-bgp-nbr-af)# commit
Examples
In the following example, the show rpl maximum command is used in EXEC mode to display the
current setting for RPL limits and number of each limit currently in use. A summary of the memory used
by all of the defined policies is also shown below the limit settings.
RP/0/RP1/CPU0:router# show rpl maximum
In the next example, the rpl maximum command changes the currently configured line and policy
limits. The show rpl maximum command displays the new settings.
RP/0/RP1/CPU0:router# configure
RP/0/RP1/CPU0:router(config)# rpl maximum policies 4000
RP/0/RP1/CPU0:router(config)# rpl maximum lines 80000
RP/0/RP1/CPU0:router(config)# commit
IPv6 ACL 1000 16000 ipv6 access-list maximum show access-lists ipv6
(access list and prefix list) acl threshold n maximum
IPv6 ACE 50,000 350,000 ipv6 access-list maximum show access-lists ipv6
ace threshold n maximum
(access list and prefix list)
This chapter describes techniques for using the command-line interface (CLI) of the
Cisco IOS XR software.
Contents
The chapter contains the following sections:
• CLI Tips and Shortcuts, page 6-1
• Displaying System Information with show Commands, page 6-5
• Wildcards, Templates, and Aliases, page 6-11
• Command History, page 6-16
• Key Combinations, page 6-18
Note Commands can be entered in uppercase, lowercase, or mixed case. Only passwords are case sensitive.
However, the Cisco Systems documentation convention presents commands in lowercase.
Tip The space (or lack of a space) before the question mark (?) is significant. If you include a space before
the question mark, the system displays all available options for a command or CLI mode. If you do not
include a space, the system displays a list of commands that begin with a particular character string.
Command Description
partial-command? Enter a question mark (?) at the end of a partial command to list the commands that begin with those
characters.
RP/0/RP0/CPU0:router# co?
configure copy
Note Do not include a space between the command and question mark.
? Lists all commands available for a particular command mode.
command ? Include a space before the question mark (?) to list the keywords and arguments that belong to a
command.
RP/0/RP0/CPU0:router# configure ?
Note For most commands, the <cr> symbol indicates that you can execute the command with the
syntax already entered. For the preceding example, press Return to enter global configuration
mode.
command keyword ? Enter a question mark (?) after the keyword to list the next available syntax option for the command.
RP/0/RP0/CPU0:router# show aaa ?
The following example shows how to add an entry to access list 99. The added entry denies access to all
hosts on subnet 172.0.0.0 and ignores bits for IPv4 addresses that start within the range of 0 to 255. The
following steps provide an example of on-screen command help:
Step 1 Enter the access-list command, followed by a space and a question mark, to list the available options for
the command:
RP/0/0/CPU0:router(config)# ipv4 access-list ?
Note The number ranges (within the angle brackets) are inclusive ranges.
Step 2 Enter the access list name list1, followed by a space and another question mark, to display the arguments
that apply to the keyword and brief explanations:
RP/0/0/CPU0:router(config)# ipv4 access-list list1 ?
Step 3 Enter the deny option and a question mark to see more command options:
RP/0/0/CPU0:router(config)#ipv4 access-list list1 deny ?
The <cr> symbol by itself indicates that there are no more keywords or arguments.
Step 5 Press Return to execute the command:
RP/0/RP0/CPU0:router(config)# ipv4 access-list list1 deny 172.31.134.0
Note The configuration does not become active until you enter the commit command to add the target
configuration to the running configuration.
RP/0/RP0/CPU0:router# configure
The CLI displays the full command name. You must then press Return to execute the command. This
feature allows you to modify or reject the suggested command.
In the next example, the CLI recognizes two commands that match the text entered:
RP/0/RP1/CPU0:router#co<Tab>
configure copy
RP/0/RP1/CPU0:router#con<Tab>
RP/0/RP1/CPU0:router#configure
Tip If your keyboard does not have a Tab key, press Ctrl-I instead.
Note The percent sign (%) indicates the line in which the error message occurred.
To display the correct command syntax, enter the “?” after the command:
RP/0/0/CPU0:router# configure ?
In the next example, Ctrl-A is used to display the beginning of the command line, and the dollar sign at
the end of the command line shows the command has been scrolled to the right and the end of the
command is hidden.
RP/0/0/CPU0:router(config)# ipv4 access-list 101 permit tcp 172.31.134.5 255.255.255.0 17$
In the next example, the right arrow key has been used to scroll to the right. Notice that dollar sign
symbols appear at both ends of the line, which indicates that command information is hidden from the
beginning and end of the command.
RP/0/0/CPU0:router(config)# $ccess-list 101 permit tcp 172.31.134.5 255.255.255.0 172.31.$
By default, the Cisco IOS XR software uses a terminal screen 80 columns wide. To adjust for a different
screen width, use the terminal width command in EXEC mode.
Use line wrapping with the command history feature to recall and modify previous complex command
entries.
For more information on the use of these commands, see the “Related Documents” section on page x.
Tip If you do not see the --More-- prompt, try entering a value for the screen length with the terminal
length command in EXEC mode. Command output is not paused if the length value is set to zero. The
following example shows how to set the terminal length:
For information on searching or filtering CLI output, see the “Filtering show Command Output” section
on page 6-9.
This feature enables you to save any show command output in a file for further analysis and reference.
When you choose to redirect command output, consider the following guidelines:
• If the full path of the file is not specified, the default directory for your account is used. You should
always save your target configuration files to this location.
• If the saved output is to be used as a configuration file, the filename should end with the cfg suffix
for easy identification. This suffix is not required, but can help locate target configuration files.
Example: myconfig.cfg
In the following example, a target configuration file is saved to the default user directory:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# show configure | file disk0:myconfig.cfg
RP/0/RP0/CPU0:router(config)# abort
RP/0/RP0/CPU0:router#
router static
address-family ipv4 unicast
0.0.0.0/0 10.21.0.1
0.0.0.0/0 pos0/1/0/1 10.21.0.1
!
!
interface pos0/1/0/1
ipv4 address 10.21.54.31 255.255.0.0
!
Note See the “Using Wildcards to Identify Interfaces in show Commands” section on page 6-11 for more
information.
interface POS0/1/0/0
ipv4 address 10.2.3.4 255.255.255.0
pos
crc 32
!
shutdown
keepalive disable
!
interface POS0/1/0/1
ipv4 address 10.2.3.5 255.255.255.0
pos
crc 32
!
shutdown
keepalive disable
!
interface POS0/1/0/2
ipv4 address 10.2.3.6 255.255.255.0
pos
crc 32
!
shutdown
keepalive disable
!
interface POS0/1/0/3
ipv4 address 10.2.3.7 255.255.255.0
pos
crc 32
!
shutdown
keepalive disable
!
--More--
Command Description
show command | begin regular-expression Begins unfiltered output of the show command with the first line that
contains the regular expression.
show command | exclude regular-expression Displays output lines that do not contain the regular expression.
show command | include regular-expression Displays output lines that contain the regular expression.
show command | file device0:path/file Writes the output lines that contain the regular expression to the specified
file on the specified device.
In the following example, the show interface command includes only lines in which the expression
“protocol” appears:
RP/0/RP0/CPU0:router# show interface | include protocol
Note Filtering is available for submodes, complete commands, and anywhere that <cr> appears in the “?”
output.
Building configuration...
line console
Tip On most systems, Ctrl-Z can be entered at any time to interrupt the output and return to EXEC mode.
For more information, see Appendix A, “Understanding Regular Expressions, Special Characters, and
Patterns.”
Note The wildcard (*) must be the last character in the interface name.
Example
In the following example, the configuration for all POS interfaces in rack 0, slot 1 is displayed:
RP/0/RP1/CPU0:router# show running-config interface pos0/1/*
interface POS0/1/0/0
ipv4 address 10.2.3.4 255.255.255.0
pos
crc 32
!
keepalive disable
interface POS0/1/0/1
ipv4 address 10.2.3.5 255.255.255.0
pos
crc 32
!
keepalive disable
interface POS0/1/0/2
ipv4 address 10.2.3.6 255.255.255.0
pos
crc 32
!
keepalive disable
interface POS0/1/0/3
ipv4 address 10.2.3.7 255.255.255.0
pos
crc 32
!
keepalive disable
--More--
The two primary steps in working with templates are creating templates and applying templates. The
following procedure describes how to create a configuration template.
SUMMARY STEPS
1. configure
2. template template-name [($parameter $parameter...)] [config-commands]
3. Enter the template commands.
4. end-template
5. commit
6. show running-config template template-name
DETAILED STEPS
Example:
Router# configure
Step 2 template template-name [($parameter Enters template configuration mode and creates a template.
$parameter...)] [config-commands]
• template-name: Unique name for the template to be
applied to the running configuration.
Example:
RP/0/RP0/CPU0:router(config)# template tmplt_1
• parameter: (Optional) Actual values of the variables
specified in the template definition. Up to five
parameters can be specified within parentheses. Each
parameter must begin with the $ character. Templates
can be created with or without parameters.
• config-commands: (Optional) Global configuration
commands to be added to the template definition. Any
name in a command (such as the server name, group
name, and so on) can be parameterized. This means that
those parameters can be used in the template commands
(starting with $) and replaced with real arguments when
applied.
• To remove the template, use the no form of this
command.
Step 3 Enter the template commands. Defines the template commands.
Example:
RP/0/RP0/CPU0:router(config-TPL)# hostname test
Step 4 end-template Ends the template definition session and exits template
configuration mode.
Example: • When you end the template session, you are returned to
RP/0/RP0/CPU0:router(config-TPL)# end-template global configuration mode.
Example:
RP/0/RP0/CPU0:router# show running-config
template tmplt_1
Examples
In the following example, a simple template is defined. The template contents are then displayed with
the show running-config template template-name command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# template jbtest
RP/0/RP0/CPU0:router(config-TPL)# hostname test
RP/0/RP0/CPU0:router(config-TPL)# end-template
RP/0/RP0/CPU0:router(config)# commit
RP/0/RP0/CPU0:router(config)# show running-config template jbtest
template jbtest
hostname test
end-template
In the next example, a template is defined, and the template requires a parameter. The template contents
are then displayed with the show running-config template template-name command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# template test2 (hostname)
RP/0/RP0/CPU0:router(config-TPL)# hostname $hostname
RP/0/RP0/CPU0:router(config-TPL)# end-template
RP/0/RP0/CPU0:router(config)# commit
RP/0/RP0/CPU0:router(config)# show running-config template test2
• After a template is applied, the show configuration command displays the target configuration
changes. The target configuration must be committed (with the commit command) to become part
of the running configuration.
Examples
In the following example, a simple template is defined. The template contents are then displayed with
the show running-config template template-name command:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# apply-template jbtest
RP/0/RP0/CPU0:router(config) show configuration
Building configuration...
hostname test
end
In the next example, a template with one parameter is applied and the show configuration command
displays the result:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# apply-template test2 (router)
RP/0/RP0/CPU0:router(config)# show configuration
Building configuration...
hostname router
end
Aliases
Cisco IOS XR software lets you define command line aliases for any physical or logical entity in a
router. After you define the alias, it can be used in the CLI to reference the real entity.
To create a command alias, enter the alias command in global configuration or administration
configuration mode:
alias alias-name [(parameter1 parameter2...)] command-syntax [$parameter1] [command-syntax
[$parameter2]}
Table 6-5 defines the alias command syntax.
Table 6-5 alias Command Syntax
Multiple commands can be supported under a single command alias, and multiple variables can be
supported for each command. If multiple commands are specified under a single alias, then each
command is executed in the order in which it is listed in the alias command.
In the following example, an alias named my-cookie is created for the Management Ethernet interface,
and then the new alias is specified to enter interface configuration mode:
RP/0/0/CPU0:router(config)# alias my-cookie mgmtEth 0/0/CPU0/0
After you enter a command with an alias, the router displays the command you entered with the alias
value so that you can verify that alias value.
To delete a specific alias, enter the no form of the alias command with the alias name.
Command History
The Cisco IOS XR software lets you display a history of the most recently entered and deleted
commands. You can also redisplay the command line while a console message is being shown. The
following sections describe the command history functionality:
• Displaying Previously Entered Commands, page 6-16
• Recalling Previously Entered Commands, page 6-17
• Recalling Deleted Entries, page 6-17
• Redisplaying the Command Line, page 6-17
Note To roll back to a previously committed configuration, see the “Managing Configuration History and
Rollback” section on page 5-3.
Note The Esc, Y key sequence does not function unless the Ctrl-Y key combination is pressed first. If the
Esc, Y is pressed more than ten times, the history cycles back to the most recent entry in the buffer.
Key Combinations
The following sections provide information on key combinations:
• Key Combinations to Move the Cursor, page 6-18
• Keystrokes to Control Capitalization, page 6-18
• Keystrokes to Delete CLI Entries, page 6-19
Note Cisco IOS XR commands are generally case insensitive and typically all in lowercase.
Keystrokes Purpose
Esc, C Capitalizes the letter at the cursor.
Keystrokes Purpose
Esc, L Changes the word at the cursor to lowercase.
Esc, U Capitalizes letters from the cursor to the end of the word.
Keystrokes Deletes
Delete or Backspace The character to the left of the cursor.
Ctrl-D The character at the cursor.
Ctrl-K All characters from the cursor to the end of the command
line.
Ctrl-U or Ctrl-X All characters from the cursor to the beginning of the
command line.
Ctrl-W The word to the left of the cursor.
Esc, D From the cursor to the end of the word.
This chapter describes the tools and procedures used to identify the source of hardware and software
problems. This chapter also provides instructions on gathering data for further analysis by Cisco
customer support representatives.
Contents
This chapter contains the following sections:
• Additional Sources for Information, page 7-1
• Basic Troubleshooting Commands, page 7-1
• Configuration Error Messages, page 7-7
• Memory Warnings in Configuration Sessions, page 7-9
• Interfaces Not Coming Up, page 7-13
Note Different show commands are available in different command modes, and the same show command can
show different results in different command modes.
Command Description
show variables boot Displays the boot variables.
(EXEC and administration EXEC
modes)
show configuration Displays the uncommitted configuration changes made during a configuration
session. This command can be entered in any configuration mode.
(Global configuration and
administration configuration modes)
show context (and show exception) Displays context information about all recent reloads.
(EXEC and administration EXEC
modes)
show controller Displays hardware controller information.
(Administration EXEC mode)
show controllers Displays hardware controller information.
(EXEC mode)
show debug Displays debug flags enabled from the current terminal.
(EXEC and administration EXEC
modes)
show environment [options] Displays hardware information for the physical components and systems, including
(EXEC and administration EXEC fans, LEDs, power supply voltage and current information, and temperatures. To view
modes) the command options, enter the show environment ? command.
Command Description
show interfaces Displays interface status and configuration.
(EXEC mode)
show logging Displays the contents of logging buffers.
(EXEC and administration EXEC
modes)
show memory Displays memory statistics.
(EXEC and administration EXEC
modes)
show platform Displays information about node status on the router. To display the nodes assigned
to an SDR, enter this command in EXEC mode. To display all the nodes in a router,
(EXEC and administration EXEC
enter this command in administration EXEC mode.
modes)
show processes blocked Displays blocked processes.
(EXEC and administration EXEC
modes)
show redundancy Display the status of the primary (active) route processor (RP) and the standby
(EXEC and administration EXEC (redundant) RP.
modes)
show running-config [command] Displays the current running configuration.
(EXEC and administration EXEC
modes)
show tech-support Collects a large amount of system information for troubleshooting. The output should
be provided to technical support representatives when a problem is reported. Because
(EXEC and administration EXEC
of the impact the command can have on a running system, it is reserved for users
modes)
assigned to the cisco-support task ID.
show user [group | tasks | all] Displays the username for the current logged-in user. Use this command to also
display the groups and associated task IDs assigned to the account.
(EXEC mode)
show version Displays basic system information.
(EXEC and administration EXEC
modes)
Each exclamation point (!) indicates receipt of a reply. A period (.) indicates the network server timed
out while waiting for a reply. Other characters may appear in the ping output display, depending on the
protocol type.
Examples
In the following example, a successful ping attempt is shown:
RP/0/RP0/CPU0:router# ping 10.233.233.233
The following example shows the output of ping through the fabric:
RP/0/RP1/CPU0:router(admin)# ping fabric location 0/6/5
Examples
In the following example, the route for an IP address is displayed:
RP/0/RP0/CPU0:router# traceroute 10.233.233.233
Caution Debug commands can generate a very large amount of output and can render the system unusable. Use
debug to troubleshoot specific problems or during specific troubleshooting sessions on systems that are
not in production.
In the next example, administration EXEC mode is the entry point to debug mode:
RP/0/RP1/CPU0:router# admin
RP/0/RP1/CPU0:router(admin)# debug
RP/0/RP1/CPU0:router(admin-debug)# ?
You can also enter the complete command from EXEC mode, as shown in the following example:
RP/0/RP0/CPU0:router# debug aaa all
The preceding example is for a Cisco CRS-1 router. On a Cisco XR 12000 Series Router, the slot
number of the tty ID is 0 or 1 instead of RP0 or RP1.
Enter the show debug conditions command to display the conditional debugging status. For example:
RP/0/RP0/CPU0:router# show debug conditions
You can also turn off debugging from the undebug mode, as shown in the following example:
RP/0/RP0/CPU0:router# undebug
RP/0/RP0/CPU0:router(undebug)# aaa all
RP/0/RP0/CPU0:router(undebug)# exit
Disabling Debugging for All Services Started at the Active Terminal Session
Use the undebug all or no debug all command to turn off all debugging started by the active terminal
session. For example, if you enter either of these commands while connected to the router through the
console port on the active RP, all debug sessions started from that console port are disabled. In the
following example, debugging for all services is disabled and then verified:
RP/0/RP0/CPU0:router# undebug all
RP/0/RP0/CPU0:router# show debug
Note The show configuration failed command can be entered in either the EXEC mode or any configuration
mode. In any mode, the configuration failures from the most recent commit operation are displayed.
In the following example, a configuration error occurs when an invalid commit operation is attempted:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# taskgroup bgp
RP/0/RP0/CPU0:router(config-tg)# description this is a test of an invalid taskgroup
RP/0/RP0/CPU0:router(config-tg)# commit
% Failed to commit one or more configuration items. Please use 'show configurati
on failed' to view the errors
To display the configuration items that failed, including a description of the error, enter the
show configuration failed command:
RP/0/RP0/CPU0:router(config-tg)# show configuration failed
You can also display the failed configuration items without the error description by entering the
show configuration failed noerror command:
RP/0/RP0/CPU0:router(config-tg)# show configuration failed noerror
Caution Never ignore a low-memory warning. These warnings indicate a memory state that could affect system
operations if not addressed.
Although users are allowed to enter configuration mode, they should immediately reduce memory usage
using the tools described in the “Removing Configurations to Resolve Low-Memory Warnings” section
on page 7-11.
Failure to take action can result in a worsening situation and eventual impact to router operations.
Caution The commit force command should be used only to apply configurations that reduce memory usage.
Adding configurations that increase memory usage could result in serious loss of router operation.
To display general memory usage for the device as a whole and by process, enter the show memory
command. Table 7-1 describes the meaning of each heading.
RP/0/RP0/CPU0:router# show memory
kernel: jid 1
Address Bytes What
000d2000 12288 Program Stack
00112000 12288 Program Stack
Total Allocated Memory: 0
Total Shared Memory: 0
pkg/bin/wd-mbi: jid 72
Address Bytes What
4817f000 4096 Program Stack (pages not allocated)
48180000 516096 Program Stack (pages not allocated)
481fe000 8192 Program Stack
48200000 8192 Program Text
--More--
Heading Description
Physical Memory Amount of physical memory installed on the device.
Application Memory Memory available for the system to use (total memory minus image size,
reserved, IOMem, and flashfsys).
Image Size of the bootable image.
Reserved Reserved for packet memory.
IOMem IO memory—Currently used as a backup for packet memory.
flashfsys Flash file system memory.
Process and JID Process and job ID.
Address Starting address in memory.
Bytes Size of memory block.
What Block description.
Caution Committing a target configuration that has caused a low-memory warning can make the system unstable.
Clearing a target configuration is a preventive measure to not let the system go into a worse memory state
due to additional configuration. In addition, all other active configuration sessions can be closed to
minimize the churn.
Step 1 Enter the show memory summary command in EXEC mode to display the overall system memory:
RP/0/RP0/CPU0:router# show memory summary
Step 2 Enter the show configuration commit list command in EXEC or administration EXEC mode to list the
configurations you can remove.
Note To display the details of a configuration, enter the show configuration commit changes command
followed by a commitID number. To display additional configuration history information, enter the show
configuration history ? command, and use the command options to display additional information.
Step 3 Enter the show running-config command to display the current configuration.
Step 4 Remove configurations as needed to free memory.
For more information, see the “Managing Configuration History and Rollback” section on page 5-3.
Command Description
show configuration sessions Displays the active configuration sessions.
clear configuration sessions session-id Clears a configuration session.
In the following example, the open configuration sessions are displayed with the show configuration
sessions command. The clear configuration sessions command is then used to clear a configuration
session.
RP/0/RP0/CPU0:router# show configuration sessions
Command Description
show interfaces Displays detailed information about all interfaces installed or
configured on the device, whether or not they are operational.
show interfaces type instance Specifies a particular interface, rather than displaying information for
all interfaces, as in the following example:
show interface POS0/1/0/0
show ipv4 interface Displays basic, IP-related information for all available interfaces.
show ipv6 interface
show ipv4 interface brief Quickly displays the most critical information about the interfaces,
including the interface status (up or down) and the protocol status.
show ipv6 interface brief
Step 1 Enter the show platform command in administration EXEC to verify that all nodes are in the “IOS XR
RUN” state:
RP/0/RP0/CPU0:router(admin)# show platform
Note Line cards in Cisco CRS-1 routers are called modular services cards (MSCs). The show platform
command output is different for Cisco CRS-1 routers and Cisco XR 12000 Series Routers. When this
command is entered in EXEC mode, the display shows only those nodes assigned to the SDR.
Step 2 Enter the show ipv4 interface brief command to verify IP address configuration and protocol status:
RP/0/RP0/CPU0:router# show ipv4 interface brief
Note You must enter the commit command to make the new configuration part of the active running
configuration. If you end the configuration session, you are automatically prompted to commit
the changes, as shown in the second example:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface pos0/2/0/1
RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.1.1.1 255.0.0.0
RP/0/RP0/CPU0:router(config-if)# no shutdown
RP/0/RP0/CPU0:router(config-if)# commit
RP/0/RP0/CPU0:router(config-if)# end
RP/0/RP0/CPU0:router#
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface pos0/2/0/2
RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.1.1.2 255.255.0.0
RP/0/RP0/CPU0:router(config-if)# no shutdown
RP/0/RP0/CPU0:router(config-if)# end
Uncommitted changes found, commit them? [yes]: yes
RP/0/RP0/CPU0:router#
Step 4 Enter the show ipv4 interface brief command to verify that the interfaces are “Up” in the Status column:
RP/0/RP0/CPU0:router# show ipv4 interface brief
Step 5 If the interface is in the “Shutdown/Down” state, as shown in the previous example, perform the
following tasks:
a. Verify that the status of the interface is “Shutdown”:
RP/0/RP0/CPU0:router# show running-config interface POS0/2/0/3
interface pos0/2/0/3
shutdown
keepalive disable
!
Step 6 If the interface state is still displayed as “Down,” verify that the physical cable connections are correctly
installed. The following message indicates that the interface has either a bad connection or no
connection:
LC/0/0/1:Sep 29 15:31:12.921 : plim_4p_oc192[183]: %SONET-4-
ALARM : SONET0_1_1_0: SLOS
Step 7 Verify again that the interface is up by entering the show ipv4 interface brief command:
RP/0/RP0/CPU0:router# show ipv4 interface brief
Step 8 Repeat these steps for every interface, until every interface shows both Status and Protocol as “Up.”
This appendix describes the regular expressions, special or wildcard characters, and patterns that can be
used with filters to search through command output. The filter commands are described in the “Filtering
show Command Output” section on page 6-9. The following sections describe features you can use with
filters:
• Regular Expressions, page A-1
• Special Characters, page A-2
• Character Pattern Ranges, page A-2
• Multiple-Character Patterns, page A-3
• Complex Regular Expressions Using Multipliers, page A-3
• Pattern Alternation, page A-4
• Anchor Characters, page A-4
• Underscore Wildcard, page A-4
• Parentheses Used for Pattern Recall, page A-4
Regular Expressions
A regular expression is a pattern (a phrase, number, or more complex pattern):
• Regular expressions are case sensitive and allow for complex matching requirements. Simple
regular expressions include entries like Serial, misses, or 138.
• Complex regular expressions include entries like 00210... , ( is ), or [Oo]utput.
A regular expression can be a single-character pattern or multiple-character pattern. That is, a regular
expression can be a single character that matches the same single character in the command output or
multiple characters that match the same multiple characters in the command output. The pattern in the
command output is referred to as a string.
The simplest regular expression is a single character that matches the same single character in the
command output. Letter (A–Z and a–z), digits (0–9), and other keyboard characters (such as ! or ~) can
be used as a single-character pattern.
Special Characters
Certain keyboard characters have special meaning when used in regular expressions. Table A-1 lists the
keyboard characters that have special meaning.
To use these special characters as single-character patterns, remove the special meaning by preceding
each character with a backslash (\). In the following examples, single-character patterns matching a
dollar sign, an underscore, and a plus sign, respectively, are shown.
\$ \_ \+
Multiple-Character Patterns
Multiple-character regular expressions can be formed by joining letters, digits, and keyboard characters
that do not have a special meaning. With multiple-character patterns, order is important. The regular
expression a4% matches the character a followed by a 4 followed by a %. If the string does not have
a4%, in that order, pattern matching fails.
The multiple-character regular expression a. uses the special meaning of the period character to match
the letter a followed by any single character. With this example, the strings ab, a!, and a2 are all valid
matches for the regular expression.
Put a backslash before the keyboard characters that have special meaning to indicate that the character
should be interpreted literally. Remove the special meaning of the period character by putting a
backslash in front of it. For example, when the expression a\. is used in the command syntax, only the
string a. is matched.
A multiple-character regular expression containing all letters, all digits, all keyboard characters, or a
combination of letters, digits, and other keyboard characters is a valid regular expression. For example:
telebit 3107 v32bis.
Character Description
* Matches 0 or more single-character or multiple-character patterns.
+ Matches 1 or more single-character or multiple-character patterns.
? Matches 0 or 1 occurrences of a single-character or multiple-character pattern.
The following example matches any number of occurrences of the letter a, including none:
a*
The following pattern requires that at least one occurrence of the letter a in the string be matched:
a+
The following pattern matches the string bb or bab:
ba?b
The following string matches any number of asterisks (*):
\**
To use multipliers with multiple-character patterns, enclose the pattern in parentheses. In the following
example, the pattern matches any number of the multiple-character string ab:
(ab)*
As a more complex example, the following pattern matches one or more instances of alphanumeric pairs:
([A-Za-z][0-9])+
The order for matches using multipliers (*, +, and ?) is to put the longest construct first. Nested
constructs are matched from outside to inside. Concatenated constructs are matched beginning at the left
side of the construct. Thus, the regular expression matches A9b3, but not 9Ab3 because the letters are
specified before the numbers.
Pattern Alternation
Alternation can be used to specify alternative patterns to match against a string. Separate the alternative
patterns with a vertical bar (|). Only one of the alternatives can match the string. For example, the regular
expression codex|telebit matches the string codex or the string telebit, but not both codex and telebit.
Anchor Characters
Anchoring can be used to match a regular expression pattern against the beginning or end of the string.
Regular expressions can be anchored to a portion of the string using the special characters shown in
Table A-3.
Character Description
^ Matches the beginning of the string.
$ Matches the end of the string.
For example, the regular expression ^con matches any string that starts with con, and sole$ matches any
string that ends with sole.
In addition to indicating the beginning of a string, the ^ can be used to indicate the logical function “not”
when used in a bracketed range. For example, the expression [^abcd] indicates a range that matches any
single letter, as long as it is not the letters a, b, c, and d.
Underscore Wildcard
Use the underscore to match the beginning of a string (^), the end of a string ($), parentheses (( )) , space
( ), braces ({}), comma (,), and underscore (_). The underscore can be used to specify that a pattern exists
anywhere in the string. For example, _1300_ matches any string that has 1300 somewhere in the string
and is preceded by or followed by a space, brace, comma, or underscore. Although _1300_ matches the
regular expression {1300_, it does not match the regular expressions 21300 and 13000t.
The underscore can replace long regular expression lists. For example, instead of specifying
^1300( ) ( )1300$ {1300, ,1300, {1300} ,1300, (1300, simply specify _1300_.
To create a regular expression that recalls a previous pattern, use parentheses to indicate memory of a
specific pattern and a backslash (\) followed by a digit to reuse the remembered pattern. The digit
specifies the occurrence of a parenthesis in the regular expression pattern. When there is more than one
remembered pattern in the regular expression, \1 indicates the first remembered pattern, \2 indicates the
second remembered pattern, and so on.
The following regular expression uses parentheses for recall:
a(.)bc(.)\1\2
This regular expression matches an a followed by any character (call it character number 1), followed by
bc followed by any character (character number 2), followed by character number 1 again, followed by
character number 2 again. So, the regular expression can match aZbcTZT. The software remembers that
character number 1 is Z and character number 2 is T, and then uses Z and T again later in the regular
expression.
A
AAA authentication, authorization, and accounting. A network security service that provides the primary
framework to set up access control on a Cisco CRS-1 router or access server. AAA is an architectural
framework and modular means of configuring three independent but closely related security functions
in a consistent manner.
ACL access control list. A list kept by routers to control access to or from the router for a number of services
(for example, to prevent packets with a certain IP address from leaving a particular interface on the
router).
active Denotes a card or process that performs a system task; in a redundant configuration, there is an inactive
standby card or process available to become active. Active cards or processes are also sometimes
denoted as primary.
active software set The set of Cisco IOS XR software packages activated in one or more nodes in a router.
algorithm A well-defined rule or process for arriving at a solution to a problem. In networking, algorithms
commonly are used to determine the best route for traffic from a particular source to a particular
destination.
APS automatic protection switching. A method that allows transmission equipment to recover automatically
from failures, such as a cut cable.
ASIC application-specific integrated circuit. A chip designed for use in a specific hardware device. An ASIC
is a chip designed for a special application, such as a particular kind of transmission protocol.
B
bandwidth The amount of data that can be sent in a fixed amount of time. For digital devices, the bandwidth is
usually expressed in bits per second (Bps) or bytes per second.
BGP Border Gateway Protocol. A routing protocol used between autonomous systems. It is the routing
protocol that makes the internet work. BGP is a distance-vector routing protocol that carries
connectivity information and an additional set of BGP attributes. These attributes allow for a rich set
of policies for deciding the best route to use to reach a given destination.
C
card type The type of the card inserted in a slot.
CDP Cisco Discovery Protocol. CDP runs on all Cisco devices so that these devices can learn about
neighboring devices and exchange information. CDP uses a well-known multicast MAC address.
During system initialization, the application-specific integrated circuit (ASIC) is configured to forward
these packets to the Cisco IOS XR software CPU, which processes the packets.
CLI command-line interface. A text-based user interface to an operating system. A command-line interface
is a user interface to a computer operating system or an application in which the user responds to a
visual prompt by typing a command on a specified line, receives a response from the system, and then
enters another command, and so forth. Typically, most of the UNIX-based systems today offer both a
command-line interface and graphical user interface (GUI). See also GUI.
committed/saved The configuration stored in the system for a particular node. The RP loads the committed configuration
software into memory at startup.
configuration
configuration In Cisco routers, a 16-bit, user-configurable value that determines how the router functions during
register initialization. The configuration register can be stored in hardware or software. In hardware, the bit
position is set using a jumper. In software, the bit position is set by specifying a hexadecimal value
using configuration commands. A hexadecimal or decimal value that represents the 16-bit
configuration register value that you want to use the next time the router is restarted. The value range
is from 0x0 to 0xFFFF (0 to 65535 in decimal).
control plane The control plane oversees the operation of the data plane, allocating resources, providing information,
and handling errors to allow data plane operations to be continuous and efficient.
CORBA Common Object Request Broker Architecture. Specification that provides the standard interface
definition between OMG-compliant objects. CORBA allows applications to communicate with one
another no matter where they are located or who has designed them.
CoS class of service. An indication of how an upper-layer protocol requires a lower-layer protocol to treat
its messages. In SNA subarea routing, CoS definitions are used by subarea nodes to determine the
optimal route to establish a given session. A CoS definition comprises a virtual route number and
transmission priority field. Repetitive, regularly timed signals are used to control synchronous
processes.
CWI Craft Works Interface. Graphical user interface (GUI) used to configure and operate a router. The CWI
client runs in a web browser.
D
DDTS distributed defect tracking system. A method to track software errors and resolutions.
DHCP Dynamic Host Configuration Protocol. Provides a mechanism for allocating IP addresses dynamically
so that addresses can be reused when hosts no longer need them.
DIMM dual in-line memory module. Small circuit boards carrying memory integrated circuits, with signal and
power pins on both sides of the board, in contrast to single-in-line memory modules (SIMMs).
disk0 Name of the flash disk on which the Cisco IOS XR software is stored.
disk1 Name of the optional flash disk on which the Cisco IOS XR software can be stored in preparation for
installation or upgrade.
DNS Domain Name System. Mechanism used in the Internet and on private intranets for translating names
of host computers into addresses. The DNS also allows host computers not directly on the Internet to
have a registered name in the same style.
DPT Dynamic Packet Transport. DPT rings are dual, counter-rotating fiber rings. Both fibers are used
concurrently to transport both data and control traffic.
DSC designated shelf controller. The RP or RP pair that controls a standalone router or a multishelf system.
The DSC is selected from among the route processors (RPs) installed in the router or multishelf system.
E
eBGP external Border Gateway Protocol. BGP sessions are established between routers in different
autonomous systems. eBGPs communicate among different network domains.
ECC error correction code. ECC is used to correct errors within memories on the Cisco CRS-1 router.
Ethernet Baseband LAN specification invented by Xerox Corporation and developed jointly by Xerox, Intel, and
Digital Equipment Corporation. Ethernet networks use CSMA/CD and run over a variety of cable types
at 10 Mbps. Ethernet standards are defined by the IEEE 802.3 specification.
F
fabric Connectivity between all line cards. Also referred to as switch fabric.
fabric cable Fabric cables are optical array cables that interconnect the fabric components in each chassis of a Cisco
CRS-1 Carrier Routing System Multishelf System. Each fabric cable contains 72 fiber-optic strands,
which are packaged as 6 ribbon cables with 12 fibers in each ribbon cable.
FC fan controller. Two fan controller cards are installed in every line card chassis as a redundant pair to
manage the fan assemblies; a BITS timing connector exists on the fan controller card.
FIB Forwarding Information Base. Database that stores information about switching of data packets. A FIB
is based on information in the Routing Information Base (RIB). It is the optimal set of selected routes
that are installed in the line cards for forwarding. See also RIB.
flooding Traffic-passing technique used by switches and bridges in which traffic received on an interface is sent
out all the interfaces of that device except the interface on which the information was originally
received.
forwarding Process of sending a frame toward its ultimate destination by way of an internetworking device.
FRR fast reroute. Automatically reroutes traffic on a label switch path (LSP) if a node or link in an LSP fails.
FRR reduces the loss of packets traveling over an LSP.
FTP File Transfer Protocol. Application protocol, part of the TCP/IP protocol stack, used for transferring
files between network nodes. FTP is defined in RFC 959.
G
GE Gigabit Ethernet. Standard for a high-speed Ethernet, approved by the IEEE 802.3z standards committee
in 1996.
Gigabit Ethernet Standard for a high-speed Ethernet, approved by the IEEE 802.3z standards committee in 1996.
GUI graphical user interface. A user environment that uses pictorial and textual representations of the input
and output of applications and the hierarchical or other data structure in which information is stored.
Such conventions as buttons, icons, and windows are typical, and many actions are performed using a
pointing device (such as a mouse). Microsoft Windows and the Apple Macintosh are prominent
examples of platforms using a GUI. See also CLI.
H
HA High availability is defined as the continuous operation of systems. For a system to be available, all
components, including application and database servers, storage devices, and the end-to-end network,
need to provide continuous service.
HDLC high-level data link control. ISO communications protocol used in X.25 packet-switching networks.
HDLC provides error correction at the data link layer and contains the following subsets: LAPB and
SDLC.
hexadecimal A number system having 16 as its base. This number representation uses the digits 0–9, with their usual
meaning, plus the letters A–F (or a–f) to represent hexadecimal digits with values of (decimal) 10 to
15. The far right digit counts ones, the next counts multiples of 16, then 16^2 = 256, and so on.
Hexadecimal is more succinct than binary for representing bit masks, machines addresses, and other
low-level constants but it is still reasonably easy to split a hex number into different bit positions. For
example, the top 16 bits of a 32-bit word are the first four hex digits.
hop Passage of a data packet between two network nodes (for example, between two routers). See also hop
count.
hop count Routing metric used to measure the distance between a source and a destination.
HTTP Hypertext Transfer Protocol. Used by web browsers and web servers to transfer files, such as text and
graphic files. HTTP is the set of rules for exchanging files (text, graphic images, sound, video, and other
multimedia files) on the World Wide Web. Relative to the TCP/IP suite of protocols (which are the basis
for information exchange on the Internet), HTTP is an application protocol.
I
ICMP Internet Control Message Protocol. Network layer Internet (TCP/IP) protocol that reports errors and
provides other information relevant to IP packet processing.
IEP IP explicit path. List of IP addresses, each representing a node or link in the explicit path.
IETF Internet Engineering Task Force. Task force consisting of over 80 working groups responsible for
developing Internet standards. The IETF operates under the auspices of ISOC.
IGMP Internet Group Management Protocol. Governs the management of multicast groups in a TCP/IP
network. Used by IP hosts to report their multicast group memberships to an adjacent multicast router.
IGP Interior Gateway Protocol. Internet protocol used to exchange routing information within an
autonomous system. Examples of common Internet IGPs include IGRP, OSPF, and RIP. See also OSPF
and RIP.
installed software The set of Cisco IOS XR software packages installed on a router.
set
IOS XR The Cisco operating system used on the Cisco CRS-1 router and Cisco XR 12000 Series Router.
IP Internet Protocol. Network layer protocol in the TCP/IP stack offering a connectionless internetwork
service. IP provides features for addressing, type-of-service specification, fragmentation and
reassembly, and security.
IPv4 IP Version 4. Network layer for the TCP/IP protocol suite. A connectionless, best-effort packet
switching protocol.
IPv6 IP Version 6. Replacement for IPv4. A next-generation IP protocol. IPv6 is backward compatible with
and designed to fix the shortcomings of IPv4, such as data security and maximum number of user
addresses. IPv6 increases the address space from 32 to 128 bits, providing for an unlimited number of
networks and systems. It also supports quality of service (QoS) parameters for real-time audio and
video.
IPX Internetwork Packet Exchange. NetWare network layer (Layer 3) protocol used for transferring data
from servers to workstations. IPX is similar to IP and XNS.
IS-IS Intermediate System-to-Intermediate System. OSI link-state hierarchical routing protocol based on
DECnet Phase V routing, whereby ISs (routers) exchange routing information based on a single metric
to determine network topology.
K
keepalive interval Period of time between each keepalive message sent by a network device.
keepalive message Message sent by one network device to inform another network device that the virtual circuit between
the two is still active.
L
Layer 2 Layer 2 refers to the data link layer of the commonly referenced multilayered communication model,
Open Systems Interconnection (OSI). The data link layer contains the address inspected by a bridge or
switch. Layer 2 processing is faster than layer 3 processing, because less analysis of the packet is
required.
Layer 3 Layer 3 refers to the network layer of the commonly referenced multilayered communication model,
Open Systems Interconnection (OSI). The network layer is concerned with knowing the address of the
neighboring nodes in the network, selecting routes and quality of service, and recognizing and
forwarding to the transport layer incoming messages for local host domains.
A router is a Layer 3 device, although some newer switches also perform Layer 3 functions. The
Internet Protocol (IP) address is a Layer 3 address.
LC line card. Line cards in the Cisco CRS-1 system are referred to as modular services cards (MSCs).
LDP label distribution protocol. A standard protocol between MPLS-enabled routers to negotiate the labels
(addresses) used to forward packets. The Cisco proprietary version of this protocol is the Tag
Distribution Protocol (TDP).
LIB Label Information Base. The table that contains the labels in use on the node.
loopback Send the outgoing signals back to the receiving side for testing.
M
MAC address Standardized data link layer address that is required for every port or device that connects to a LAN.
Other devices in the network use these addresses to locate specific ports in the network and to create
and update routing tables and data structures. MAC addresses are 6 bytes long and are controlled by
the IEEE. Also known as a hardware address, MAC layer address, and physical address.
mask Pattern of bits used to reject or accept bit patterns in another set of data.
MBI minimum boot image. Software image containing a kernel and minimum set of drivers and components
to boot a node.
Mbps megabits per second. A bit rate expressed in millions of binary bits per second. 1 megabit = 220 bits, or
1,048,576 bits.
MIB Management Information Base. Database of network management information that is used and
maintained by a network management protocol like Simple Network Management Protocol (SNMP).
The value of an MIB object can be changed or retrieved using SNMP commands, usually through a GUI
network management system. MIB objects are organized in a tree structure that includes public
(standard) and private (proprietary) branches.
MPLS Multiprotocol Label Switching. Switching method that forwards IP traffic using a label. This label
instructs the routers and switches in the network where to forward the packets based on pre-established
IP routing information
MPLS TE Multiprotocol Label Switching traffic engineering. A switching method that forwards IP traffic using
a label. This label instructs the routers and switches in the network where to forward the packets based
on pre-established IP routing information.
MSC modular services card. Module in which the ingress and egress packet processing and queueing
functions are carried out in the Cisco CRS-1 architecture. Up to 16 MSCs are installed in a line card
chassis; each MSC must have an associated physical line interface module (PLIM) (of which there are
several types to provide a variety of physical interfaces). The MSC and PLIM mate together on the line
card chassis midplane. See also PLIM.
MTU maximum transmission unit. Maximum packet size, in bytes, that a particular interface can handle.
multicast Multicast is a feature that refers to single packets copied by the network and sent to a specific subset
of network addresses. These addresses are specified in the Destination Address Field. See also unicast.
N
netboot Loading software images from a network server, such as TFTP.
NSF nonstop forwarding. Packets keep flowing during events such as failover, process restarts, and the
upgrade or downgrade of software packages. Nonstop forwarding is the ability of a router to continue
to forward traffic toward a router that may be recovering from a transient failure and the ability of a
router recovering from a transient failure in the control plane to continue correctly forwarding traffic
sent to it by a peer.
NTP Network Time Protocol. Protocol built on top of TCP that ensures accurate local time-keeping with
reference to radio and atomic clocks located on the Internet. This protocol is capable of synchronizing
distributed clocks within milliseconds over long time periods.
NVRAM nonvolatile RAM. Static random access memory that is made into nonvolatile storage by having a
battery permanently connected.
O
OC-x Optical carrier, where x=3, 12, 48, or 192, relating to the various speeds within a SONET network.
OIR online insertion and removal. Feature that permits the addition, replacement, or removal of cards
without interrupting the system power, entering console commands, or causing other software or
interfaces to shut down. Sometimes called hot-swapping or power-on servicing.
OSI Open Systems Interconnection. International standardization program created by ISO and ITU-T to
develop standards for data networking that facilitate multivendor equipment interoperability.
OSPF Open Shortest Path First. Link-state, hierarchical Interior Gateway Protocol (IGP) routing algorithm
proposed as a successor to Routing Information Protocol (RIP) in the Internet community. OSPF
features include least-cost routing, multipath routing, and load balancing. OSPF was derived from an
early version of the Intermediate System-to-Intermediate System (IS-IS) protocol. See also IGP and
RIP.
P
package A group of software components installed on the router.
packet Logical grouping of information that includes a header containing control information and (usually)
user data. Packets most often are used to refer to network layer units of data.
Packet over POS. Packet over SONET/SDH enables core routers to send native IP packets directly over SONET or
SONET/SDH SDH frames.
PAP Password Authentication Protocol. Authentication protocol that allows PPP peers to authenticate one
another. The remote router attempting to connect to the local router is required to send an authentication
request. Unlike Challenge Handshake Authentication Protocol (CHAP), PAP passes the password and
the hostname or username in the clear (unencrypted). PAP does not itself prevent unauthorized access
but merely identifies the remote end. The router or access server then determines whether that user is
allowed access. PAP is supported only on PPP lines. See also PPP.
PCMCIA Personal Computer Memory Card International Association. Standard for credit card-size memory or
I/O device.
PIE package installation envelope. An installable software file with the suffix pie. A PIE may be a package
or a Software Maintenance Upgrade (SMU). A PIE is used to deliver Cisco IOS XR software. A PIE
may contain a single component, group of components (called a package), or set of packages. When a
PIE contains more than one component, it is called a “Composite PIE.”
PLIM Physical layer interface module. Provides the physical interface for a line card. Also handles
media-specific functions, such as framing, clock recovery, channelization, and optical signaling for line
interfaces connecting to a Cisco CRS-1 router.
PM performance monitoring. Provides a variety of automatic functions to aid in the maintenance and
operation of the network. PM is continuous, in-service monitoring of transmission quality that uses
software-provisionable performance parameters. Performance parameters are measured for all four
layers of the SONET signal: physical, section, line, and STS path.
POS Packet over SONET/SDH. POS enables core routers to send native IP packets directly over
Synchronous Optical Network (SONET) or Synchronous Digital Hierarchy (SDH) frames.
PPP Point-to-Point Protocol. Successor to SLIP that provides router-to-router and host-to-network
connections over synchronous and asynchronous circuits. Whereas SLIP was designed to work with IP,
PPP was designed to work with several network layer protocols, such as IP, IPX, and ARA. PPP also
has built-in security mechanisms, such as CHAP and PAP. PPP relies on two protocols: LCP and NCP.
primary RP The first route processor configured for DSC or logical router operation. If a second RP is configured
as a redundant RP, it becomes the secondary RP.
Q
QoS quality of service. A set of parameters that describes a flow of data, such as guaranteed bandwidth,
delay, and delivery guarantee.
R
RCP remote copy protocol. A protocol that allows users to copy files to and from a file system residing on
a remote host or server on the network. The RCP protocol uses TCP to ensure the reliable delivery of
data.
RIB Routing Information Base. This is the set of all available routes from which to choose the FIB. The RIB
essentially contains all routes available for selection. Essentially, it is the sum of all routes learned by
dynamic routing protocols, all directly attached networks (that is. networks to which a given router has
interfaces connected), and any additional configured routes, such as static routes.
RIP Routing Information Protocol. A simple routing protocol that is part of the TCP/IP protocol suite and
the most common IGP in the Internet. RIP determines a route based on the smallest hop count between
source and destination. It is a distance vector protocol that broadcasts routing information to
neighboring routers. It is known to use excessive bandwidth. See also hop count and IGP.
ROM Monitor ROM Monitor is a bootstrap program that initializes the hardware and boots the system when a router
is powered on or reset. ROM Monitor mode is also known as “ROMMON,” which reflects the CLI
prompts for the mode.
rommon B1> (Cisco CRS-1 routers)
or
rommon1> (Cisco XR 12000 Series Routers)
router Network layer device that uses one or more routing metrics to determine the optimal path along which
network traffic should be forwarded. Routers forward packets from one network to another based on
network layer information.
routing Process of finding a path to a destination host. Routing is very complex in large networks because of
the many potential intermediate destinations a packet might traverse before reaching its destination
host.
routing metric A routing algorithm determines that one route is better than another. This information is stored in
routing tables. Metrics include bandwidth, communication cost, delay, hop count, load, MTU, path
cost, and reliability. Sometimes referred to simply as a metric. See also algorithm.
routing protocol Protocol that accomplishes routing through the implementation of a specific routing algorithm.
Examples of routing protocols include BGP, OSPF, and IS-IS.
routing table Table stored in a router or some other internetworking device that keeps track of routes to particular
network destinations and, in some cases, metrics associated with those routes.
RP route processor. Cards that contain run-control software on the router. Two RPs are installed as a
redundant pair in dedicated slots in the front of each line card chassis.
RPF Reverse Path Forwarding. Multicasting technique in which a multicast datagram is forwarded from all but
the receiving interface if the receiving interface is the one used to forward unicast datagrams to the source
of the multicast datagram.
RSVP Resource Reservation Protocol. Protocol that supports the reservation of resources across an IP
network. Applications running on IP end systems can use RSVP to indicate to other nodes the nature
(bandwidth, jitter, maximum burst, and so on) of the packet streams they want to receive. RSVP
depends on IPv6. Also known as Resource Reservation Setup Protocol. See also IPv6.
running The router configuration currently in effect. Although the user can save multiple versions of the router
configuration configuration for future reference, only one copy of the running configuration exists in the router at any
given time.
Rx The receiver end of a fabric link. All links are unidirectional. See also Tx.
S
SCFC shelf controller/fan controller. Combines shelf controller function and fan controller function on one
card. Two are installed in each fabric chassis.
SDH Synchronous Digital Hierarchy. European standard that defines a set of rate and format standards that
are sent using optical signals over fiber. SDH is similar to SONET, with a basic SDH rate of
155.52 Mbps, designated at STM-1.
SDR secure domain router. A collection of line cards and route processors that form a complete router. Each
router contains its own instance of dynamic routing, IP stack, system database, interface manager, and
event notification system.
SDRAM synchronous dynamic random access memory. A form of dynamic RAM that adds a separate clock
signal to the control signals.
shelf controller The hardware component that manages the configuration and health of a fabric chassis within the
Cisco CRS-1 router.
shelf manager The shelf manager process runs on a router or switch, doing platform-dependent functions, including
handling OIR events. Shelf manager is formerly called platform manager.
SMU Software Maintenance Upgrade. A “point fix” for a critical problem. SMUs are delivered as PIE files
and are used to update software packages.
SNMP Simple Network Management Protocol. SNMP is the protocol governing network management and the
monitoring of network devices and their functions. It is not necessarily limited to TCP/IP networks.
SNMPv3 Simple Network Management Protocol Version 3. An interoperable standards-based protocol for
network management. SNMPv3 provides secure access to devices by a combination of authenticating
and encrypting packets over the network.
software A list of packages activated for a particular node. A software configuration consists of a boot package
configuration and additional feature packages.
SONET Synchronous Optical Network. A standard format for transporting a wide range of digital
telecommunications services over optical fiber. SONET is characterized by standard line rates, optical
interfaces, and signal formats. See also SDH.
SP service processor. An SP on each card maintains an internal management connection to the shelf
controller for the rack. The SP is referred to in CLI commands to identify the nodeID for fabric, alarm
and fan controller cards.
Example:
RP/0/RPO/CPU:router# admin show controllers fabric connectivity location 0/SM0/SP
SPE Synchronous Payload Envelope. Portion of the SONET frame containing overhead information (POH
and user data).
SPF shortest path first. Routing algorithm that iterates on length of path to determine a shortest-path
spanning tree. Commonly used in link-state routing algorithms. Sometimes called Dijkstra's algorithm.
SSH Secure Shell. A protocol that provides a secure remote connection to a router through a Transmission
Control Protocol (TCP) application.
SSL secure socket layer. A secure socket between two entities with authentication.
standby Denotes an inactive card or process that waits to become active; standby cards or processes are also
sometimes denoted as backup.
startup The router configuration designated to be applied on the next router startup.
configuration
subinterface Virtual interfaces created on a hardware interface. These software-defined interfaces allow for
segregation of traffic into separate logical channels on a single hardware interface and better utilization
of the available bandwidth on the physical interface.
switchover A switch between the active and standby cards. The switchover can be initiated by command, or it can
occur automatically when the active card fails.
system restart Soft reset of a router node. This involves restarting all processes running on that node.
T
TAC Cisco Technical Assistance Center.
TACACS Terminal Access Controller Access Control System. Authentication protocol, developed by the DDN
community, that provides remote access authentication and related services, such as event logging.
User passwords are administered in a central database rather than in individual routers, providing an
easily scalable network security solution.
tar A tar file is a file produced by the UNIX tar program, which packages multiple files in a single file for
distribution as a single unit. Each tar file has a tar filename extension.
target configuration A “two-stage” configuration of the Cisco IOS XR software running configuration. This allows users to
make changes to the running configuration and accept these changes by entering the commit command.
task ID An identifier that determines user access to a given command or series of commands. A user must be
a member of a group with the appropriate task IDs assigned to it to execute the related commands.
Tbps terabits per second. The amount of data that can be sent in a fixed amount of time. 1 terabit = 240 bits,
or 1,099,511,627,776 bits.
TCP Transmission Control Protocol. Connection-oriented transport layer protocol that provides reliable
full-duplex data transmission. TCP is part of the TCP/IP protocol stack.
Telnet Standard terminal emulation protocol in the TCP/IP protocol stack. Telnet is used for remote terminal
connection, enabling users to log in to remote systems and use resources as if they were connected to
a local system. Telnet is defined in RFC 854.
terabyte A unit of computer memory or data storage capacity equal to 1024 gigabytes (240 bytes).
Approximately 1 trillion bytes.
TFTP Trivial File Transfer Protocol. A simplified version of FTP that allows files to be transferred from one
computer to another over a network, usually without the use of client authentication (for example,
username and password).
Note: some TFTP servers (such as Sun Solaris) may not support file sizes larger that 32 MB.
trap Message sent by an SNMP agent to an NMS, a console, or a terminal to indicate the occurrence of a
significant event, such as a specifically defined condition or a threshold that was reached.
tunnel Secure communication path between two peers, such as two routers.
Tx The transmitter end of a fabric link. All links are unidirectional. See also Rx.
U
UDP User Datagram Protocol. Connectionless transport layer protocol in the TCP/IP protocol stack. UDP is
a simple protocol that exchanges datagrams without acknowledgments or guaranteed delivery,
requiring that error processing and retransmission be handled by other protocols. UDP is defined in
RFC 768.
unicast A unicast transmission sends one copy of each packet to each member of the group. This method is
transmission inefficient because the same information must be carried multiple times, requiring extra bandwidth.
V
VCSEL vertical cavity surface emitting laser.
vm A vm file is a Cisco IOS XR software file that can be installed from ROM Monitor mode. A vm file is
typically used to install the Cisco IOS XR software when the software has not yet been installed or has
been corrupted.
VPN Virtual Private Network. Enables IP traffic to travel securely over a public TCP/IP network by
encrypting all traffic from one network to another. A VPN uses “tunneling” to encrypt all information
at the IP level.
W
WRED Weighted Random Early Detection. Queueing method that ensures that high-precedence traffic has
lower loss rates than other traffic during times of congestion.
X
XML Extensible Markup Language. A standard maintained by the World Wide Web Consortium (W3C) that
defines a syntax that lets you create markup languages to specify information structures. Information
structures define the type of information, for example, subscriber name or address, not how the
information looks (bold, italic, and so on). External processes can manipulate these information
structures and publish them in a variety of formats. XML allows you to define your own customized
markup language.
XML agent A process on the router that is sent XML requests by XML clients and is responsible for carrying out
the actions contained in the request and returning an XML response back to the client. The XML Agent
for CORBA is an example of an XML agent provided on the Cisco CRS-1 router.
XML client An external application that sends an XML request to the router and receives XML responses to those
requests.
XML operation A portion of an XML request that specifies an operation that the XML client would like the XML agent
to perform.
XML operation The router code that carries out a particular XML operation including parsing the operation XML,
provider performing the operation, and assembling the operation XML response
XML request An XML document sent to the router containing a number of requested operations to be carried out.
XML schema An XML document specifying the structure and possible contents of XML elements that can be
contained in an XML document.
verification
Symbols
Catalyst switch 3-18
? command 6-2 fabric cabling 3-43
FCC 3-34
non-DSC LCC 3-37
A
spanning tree 3-39
abbreviated commands, entering 6-2 standalone router 2-4
abort command 4-38
aborting command output 6-7
C
admin command 3-39
administration configuration mode 4-19 capitalization, keyboard shortcuts 6-18
administration EXEC mode 4-19 cards
alarm correlation, logging 5-10 CRS-FCC-LED See OIM LED
alarm logging DRP PLIM 4-5
correlation 5-10 OIM LED
locations 5-9 illustration 3-45
severity levels 5-9 LED interpretation 3-44
alias command 6-15 PRP-2, illustration 1-12, 4-5
aliases, introduction 6-15 RP for 16-slot LCC 1-10, 4-3
alphanumeric LED display RP for 4-slot and 8-slot LCCs 1-11, 4-4
DRP PLIM illustration 4-5 card type, displayed in prompt 4-12
PRP-2 illustration 1-12, 4-5 characters
RP for 16-slot LCC illustration 1-10, 4-3 anchor A-4
RP for 4-slot and 8-slot LCCs, illustration 1-11, 4-4 parentheses for pattern recall A-4
alternative configuration, loading at startup 4-33 pattern ranges A-2
anchor characters A-4 special A-2
underscore wildcard A-4
Cisco Catalyst 6509 Switch
B
configuration 3-8
BGP, configuration limits 5-20 hardware requirements 3-9
bring up restrictions 3-10
multishelf system, first time 3-3 software requirements 3-9
standalone router, first time 2-2 Cisco IOS XR software
rollback
O
configuration
oim count command 3-31 loading changes to the target configuration 5-8
oim instance command 3-31 overview 5-3
OIM LED card previewing changes 5-5
illustration 3-45 procedure 5-6
LED interpretation 3-46 rollback failure 5-3
operator user group 4-14 packages
Optical Interface Module. See OIM package incompatibility 5-3
OSPF, configuration limits 5-17 rollback configuration command 5-6
owner SDR 4-1 ROM monitor mode 4-21
root command 4-37
root-lr user group 4-14
P
root-system user group 4-14
partial command, entry 6-4 route processors
password command 5-15 DRP PLIM illustration 4-5
pattern PRP-2 illustration 1-12, 4-5
alternation A-4 RP for 16-slot LCC illustration 1-10, 4-3
multiple-character A-3 RP for 4-slot and 8-slot LCCs, illustration 1-11, 4-4
recall A-4 router
ping command 7-3 clock setting 4-44
Primary LED name configuration 4-38
RP for 16-slot LCC illustration 1-10, 4-3 name displayed in prompt 4-12
RP for 4-slot and 8-slot LCCs, illustration 1-11, 4-4 verification
prompt Catalyst switch 3-18
command mode identification 4-18 fabric cabling 3-43
PRP-1, not supported 1-9 FCC 3-34
PRP-2, connections 1-9 non-DSC LCC 3-37
spanning tree 3-39
standalone router 2-4
R
router configuration mode 4-20
rack number router static address family ipv4 command 4-42
displayed in prompt 4-12 router submode configuration 4-21
four-FCC system plan 3-5 RPL, configuration limits 5-21
preparing a plan 3-3 rpl maximum lines command 5-21
single-FCC system plan 3-4 rpl maximum policies command 5-21
two-FCC system plan 3-5
redirecting command output 6-8
resource management 5-16