Cisco IOS XR Getting Started Guide

Cisco IOS XR Getting Started Guide
Cisco IOS XR Software Release 3.3
Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 526-4100
Text Part Number: OL-8524-04
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs 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.
q g g g y g g y y iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, 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. (0601R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Cisco IOS XR Getting Started Guide Copyright 2006 Cisco Systems, Inc. All rights reserved.
Preface
xi xi
Changes to This Document
About This Document xiii Intended Audience xiii Organization of the Document Related Documents xiv Conventions xiv
xiii
Obtaining Documentation xv Cisco.com xv Product Documentation DVD xv Ordering Documentation xv Documentation Feedback
xvi
Cisco Product Security Overview xvi Reporting Security Problems in Cisco Products Product Alerts and Field Notices
xvii
xvi
Obtaining Technical Assistance xvii Cisco Technical Support & Documentation Website Submitting a Service Request xviii Definitions of Service Request Severity xviii Obtaining Additional Publications and Information
1
xix
xvii
CHAPTER
Introduction to Cisco IOS XR Software Contents

1-1
1-1
Supported Standalone System Configurations Cisco CRS-1 Multishelf System Overview Router Management Interfaces 1-6 Command-Line Interface 1-6 Craft Works Interface 1-6 Extensible Markup Language API 1-6 Simple Network Management Protocol
1-2
1-1
1-7
Selecting and Identifying the Designated Shelf Controller 1-7 Selecting and Identifying the DSC on Cisco CRS-1 Routers 1-8 Selecting and Identifying the DSC on Cisco CRS-1 Multishelf Systems 1-8 Selecting and Identifying the DSC on Cisco XR 12000 and 12000 Series Routers
1-9
iii
Contents
Connecting to the Router Through the Console Port Where to Go Next

2
1-14
1-9
CHAPTER
Bringing Up the Cisco IOS XR Software on a Standalone Router Contents

2-1
2-1
Prerequisites 2-1 Software Requirements 2-2 Hardware Prerequisites and Documentation Bringing Up and Configuring a Standalone Router Verifying the System After Initial Bring-Up Where to Go Next
3
2-9 2-4
2-2 2-2
CHAPTER
Bringing Up the Cisco IOS XR Software on a Multishelf System Contents

3-1
3-1
Prerequisites 3-1 Software Requirements 3-2 Hardware Requirements 3-2 Restrictions

3-3 3-3
Information About Bringing Up a Multishelf System Bringup Overview 3-3 Preparing a Rack Number Plan 3-3
Configuring the External Cisco Catalyst 6509 Switches 3-8 Prerequisites 3-9 Restrictions 3-10 Before You Begin 3-11 Information About the Catalyst Switch Configuration 3-11 Configuring the Catalyst Switches 3-11 Verifying the Catalyst Switch 3-19 Bringing Up and Configuring Rack 0 Bringing Up and Verifying FCCs Verifying the Spanning Tree Where to Go Next
4
3-41 3-27 3-31 3-21
Bringing Up and Verifying the Non-DSC LCC

3-32 3-38
Verifying Fabric Cabling Connections
CHAPTER
Configuring General Router Features Contents

4-1
4-1
iv
Contents
Secure Domain Routers
4-1
Connecting and Communicating with the Router 4-2 Establishing a Connection Through the Console Port 4-7 Establishing a Connection Through a Terminal Server 4-8 Establishing a Connection Through the Management Ethernet Interface Logging In to a Router or an SDR CLI Prompt
4-12 4-11
4-10
User Access Privileges 4-13 User Groups, Task Groups, and Task IDs 4-13 Predefined User Groups 4-14 Displaying the User Groups and Task IDs for Your User Account Navigating the Cisco IOS XR Command Modes 4-17 Identifying the Command Mode in the CLI Prompt 4-18 Summary of Common Command Modes 4-19 Entering EXEC Commands from a Configuration Mode 4-21 Command Mode Navigation Example 4-22 Managing Configuration Sessions 4-23 Displaying the Active Configuration Sessions 4-24 Starting a Configuration Session 4-24 Starting an Exclusive Configuration Session 4-25 Displaying Configuration Details with show Commands 4-26 Saving the Target Configuration to a File 4-32 Loading the Target Configuration from a File 4-33 Loading an Alternative Configuration at System Startup 4-33 Clearing All Changes to a Target Configuration 4-33 Committing Changes to the Running Configuration 4-34 Reloading a Failed Configuration 4-36 Exiting a Configuration Submode 4-37 Ending a Configuration Session 4-37 Aborting a Configuration Session 4-38 Configuring the SDR Hostname
4-38
4-14
Configuring the Management Ethernet Interface 4-39 Specifying the Management Ethernet Interface Name in CLI Commands Displaying the Available Management Ethernet Interfaces 4-40 Configuring the Management Ethernet Interface 4-41 Manually Setting the Router Clock Where to Go Next
4-45 4-43
4-39
Contents
CHAPTER
Configuring Additional Router Features Contents

5-1
5-1
Configuring the Domain Name and Domain Name Server Configuring Telnet, HTTP, and XML Host Services Prerequisites 5-3
5-2
5-1
Managing Configuration History and Rollback 5-3 Displaying the CommitIDs 5-4 Displaying the Configuration History Log 5-5 Displaying the Configuration Changes Recorded in a CommitID 5-5 Previewing Rollback Configuration Changes 5-6 Rolling Back the Configuration to a Specific Rollback Point 5-6 Rolling Back the Configuration over a Specified Number of Commits 5-7 Loading CommitID Configuration Changes to the Target Configuration 5-7 Loading Rollback Configuration Changes to the Target Configuration 5-8 Deleting CommitIDs 5-9 Configuring Logging and Logging Correlation 5-9 Logging Locations and Severity Levels 5-10 Alarm Logging Correlation 5-10 Configuring Basic Message Logging 5-11 Disabling Console Logging 5-13 Creating and Modifying User Accounts and User Groups 5-13 Displaying Details About User Accounts, User Groups, and Task IDs Configuring User Accounts 5-14 Creating Users and Assigning Groups 5-15 Configuration Limiting 5-16 Static Route Configuration Limits 5-17 IS-IS Configuration Limits 5-18 OSPFv2 and v3 Configuration Limits 5-18 BGP Configuration Limits 5-21 Routing Policy Language Line and Policy Limits Multicast Configuration Limits 5-24 MPLS Configuration Limits 5-25 Other Configuration Limits 5-25
6
5-14
5-22
CHAPTER
CLI Tips, Techniques, and Shortcuts Contents

6-1
6-1
CLI Tips and Shortcuts 6-1 Entering Abbreviated Commands
6-2
vi
Contents
Using the Question Mark (?) to Display On-Screen Command Help Completing a Partial Command with the Tab Key 6-4 Identifying Command Syntax Errors 6-5 Using the no Form of a Command 6-5 Editing Command Lines that Wrap 6-5 Displaying System Information with show Commands 6-6 Common show Commands 6-6 Browsing Display Output when the --More-- Prompt Appears Halting the Display of Screen Output 6-8 Redirecting Output to a File 6-8 Narrowing Output from Large Configurations 6-8 Filtering show Command Output 6-10 Wildcards, Templates, and Aliases 6-11 Using Wildcards to Identify Interfaces in show Commands Creating Configuration Templates 6-13 Applying Configuration Templates 6-15 Aliases 6-16 Keystrokes Used as Command Aliases 6-17 Command History 6-17 Recalling Previously Entered Commands Recalling Deleted Entries 6-18 Redisplaying the Command Line 6-18
6-17
6-2
6-7
6-11
Key Combinations 6-18 Key Combinations to Move the Cursor 6-19 Keystrokes to Control Capitalization 6-19 Keystrokes to Delete CLI Entries 6-20 Transposing Mistyped Characters 6-20
7
CHAPTER
Upgrading and Managing Cisco IOS XR Software Contents

7-1
7-1
Overview of Cisco IOS XR Software Packages 7-1 Package Installation Envelopes (PIE Files) 7-2 Summary of Cisco IOS XR Software Packages 7-2 PIE Filenames and Version Numbers 7-4 Information About Package Management 7-7 Overview of Package Management 7-7 Managing Software Packages in a Multishelf System 7-8 Managing Software Packages in Secure Domain Routers (SDRs) Default Software Profile for SDRs 7-10
7-9
vii
Contents
Upgrading Packages 7-10 Downgrading Packages 7-11 Impact of Package Version Changes 7-11 Impact of Package Activation and Deactivation Controlling install Command Operations 7-12 Displaying Installation Log Information 7-12
7-11
Package Management Procedures 7-15 Activation and Deactivation Prerequisites 7-15 Obtaining and Placing Cisco IOS XR Software 7-16 Prepare for Software install Operations 7-19 Adding and Activating Packages 7-27 Committing the Active Package Set 7-37 Deactivating and Removing Cisco IOS XR Software Packages Rolling Back a Previous install Operation 7-42 Cisco IOS XR Software Package Feature List
8
7-46
7-38
CHAPTER
Managing the Router Hardware Contents

8-1
8-1
Displaying Hardware Status 8-1 Displaying Secure Domain Router Hardware Version Information 8-2 Displaying System Hardware Version Information 8-4 Displaying the Chassis Serial Numbers (Cisco CRS-1 Routers) 8-10 Displaying the Configured Chassis Serial Numbers 8-10 Displaying Software and Hardware Information 8-11 Displaying SDR Node IDs and Status 8-12 Displaying Router Node IDs and Status 8-14 Displaying Router Environment Information 8-15 Displaying RP Redundancy Status 8-17 RP Redundancy and Switchover 8-18 Establishing RP Redundancy on the Cisco CRS-1 Router 8-18 Establishing RP Redundancy on Cisco XR 12000 Series Routers Determining the Active RP in a Redundant Pair 8-20 Role of the Standby RP 8-20 Summary of Redundancy Commands 8-21 Automatic Switchover 8-21 RP Redundancy During RP Reload 8-21 Manual Switchover 8-22 Communicating with a Standby RP 8-23 DSC Migration on Cisco CRS-1 Multishelf Systems
8-19
8-23
viii
Contents
Reloading, Shutting Down, or Power Cycling a Node 8-24 Reloading the Active RP 8-25 Administratively Shutting Down or Powering On or Off a Node Using Controller Commands to Manage Hardware Components Formatting Hard Drives, Flash Drives, and Other Storage Devices
8-27
8-27 8-27
Removing and Replacing Cards 8-28 Removing Line Cards, MSCs, or PLIMs 8-28 Replacing an MSC 8-29 Replacing a Line Card or PLIM with the Same Media Type and Port Count 8-29 Replacing a Line Card or PLIM with the Same Media Type and a Different Port Count Replacing a Line Card or PLIM with a Different Media Type 8-30 Removing and Replacing Cisco CRS-16-FC Switch Fabric Cards 8-30 Removing and Replacing Cisco CRS-8-FC/S Switch Fabric Cards 8-38 Removing and Replacing CSC and SFC Cards 8-47 Removing and Replacing CSFC Cards 8-53 Adding a Standby PRP to a Cisco 12000 Series Router 8-53
9
8-29
CHAPTER
Troubleshooting the Cisco IOS XR Software Contents

9-1 9-1
9-1
Additional Sources for Information
Basic Troubleshooting Commands 9-2 Using show Commands to Display System Status and Configuration Using the ping Command 9-4 Using the traceroute Command 9-4 Using debug Commands 9-5 Understanding Processes and Threads 9-8 Commands Used to Display Process and Thread Details 9-9 Commands Used to Manage Process and Threads 9-14 Configuration Error Messages 9-15 Configuration Failures During a Commit Operation Configuration Errors at Startup 9-16
9-15
9-2
Memory Warnings in Configuration Sessions 9-16 Understanding Low-Memory Warnings in Configuration Sessions 9-17 Displaying System Memory Information 9-18 Removing Configurations to Resolve Low-Memory Warnings 9-19 Contacting TAC for Additional Assistance 9-21 Interfaces Not Coming Up 9-21 Verifying the System Interfaces
9-22
ix
Contents
APPENDIX
Understanding Regular Expressions, Special Characters, and Patterns Regular Expressions Special Characters
A-1 A-2 A-2 A-3 A-3
A-1
Character Pattern Ranges Multiple-Character Patterns Pattern Alternation Anchor Characters Underscore Wildcard
A-4 A-4 A-4
Complex Regular Expressions Using Multipliers
Parentheses Used for Pattern Recall

GLOSSARY
A-4
INDEX
Preface
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 xi About This Document, page xiii Obtaining Documentation, page xv Documentation Feedback, page xvi Cisco Product Security Overview, page xvi Product Alerts and Field Notices, page xvii Obtaining Technical Assistance, page xvii Obtaining Additional Publications and Information, page xix
Changes to This Document

Table 1 lists the technical changes made to this document since it was first printed.
Table 1 Changes to This Document
Revision OL-8524-04
Date October 2006
Change Summary Chapter 8, Managing the Router Hardware,was modified as follows:
Added DSC Migration on Cisco CRS-1 Multishelf Systems section on page 8-23.
xi
Preface Changes to This Document
Table 1
Changes to This Document (continued)
Revision OL-8524-03
Date July 2006
Change Summary Chapter 1, Introduction to Cisco IOS XR Software,was modified as follows:
Updated the Cisco CRS-1 Multishelf System Overview section on page 2 to include two-FCC multishelf systems.
Chapter 3, Bringing Up the Cisco IOS XR Software on a Multishelf System,was modified as follows:
Updated the Prerequisites section on page 1 to show that multishelf systems require Cisco IOS XR Software Release 3.3.1 and ROMMON 1.40 or higher on each RP in the system. Updated the chapter to include two-FCC multishelf systems. Updated the Configuring the External Cisco Catalyst 6509 Switches section on page 8 to include Unidirectional Link Detection (UDLD) protocol configuration and refine the configuration procedure.
OL-8524-02
May 2006
Chapter 1, Introduction to Cisco IOS XR Software,was modified as follows:
Updated the Selecting and Identifying the Designated Shelf Controller section on page 7 to identify the default active RP and DSC. Added a note about the command that defines the default active RP.
Chapter 7, Upgrading and Managing Cisco IOS XR Software, was modified as follows:

Added Default Software Profile for SDRs section on page 10. Added examples for the detail and verbose options to the Displaying Installation Log Information section on page 12. Added optional verification steps after package activation and deactivation.
Chapter 8, Managing the Router Hardware,was modified as follows:
Updated the Determining the Active RP in a Redundant Pair section on page 20 to reflect that the active RP is determined by configuration settings.
OL-8524-01
April 2006
Initial release of the document.
xii
Preface About This Document
About This Document

The following sections provide information about Cisco IOS XR Getting Started Guide and related documents:

Intended Audience, page xiii Organization of the Document, page xiii Related Documents, page xiv Conventions, page xiv
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
Organization of the Document

This document contains the following chapters:

Chapter 1, Introduction to Cisco IOS XR Software 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 Chapter 4, Configuring General Router Features Chapter 5, Configuring Additional Router Features Chapter 6, CLI Tips, Techniques, and Shortcuts Chapter 7, Upgrading and Managing Cisco IOS XR Software Chapter 8, Managing the Router Hardware Chapter 9, Troubleshooting the Cisco IOS XR Software Appendix A, Understanding Regular Expressions, Special Characters, and Patterns
xiii
Preface About This Document
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 Commands and keywords Variable for which you supply values Displayed session and system information Commands and keywords you enter in an interactive environment Menu items and button names Menu navigation
Convention boldface font italic font

screen
font font
boldface screen
Variables you enter in an interactive environment italic screen font boldface font 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.
xiv
Preface Obtaining Documentation
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 You can access the Cisco website at this URL: http://www.cisco.com You can access international Cisco websites at this URL: http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD

The Product Documentation DVD is a library of technical product documentation on a portable medium. The DVD enables you to access installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the HTML documentation and some of the PDF files found on the Cisco website at this URL: http://www.cisco.com/univercd/home/home.htm The Product Documentation DVD is created and released regularly. DVDs are available singly or by subscription. Registered Cisco.com users can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at the Product Documentation Store at this URL: http://www.cisco.com/go/marketplace/docstore
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
xv
Preface Documentation Feedback
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.
Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL: http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html From this site, you will find information about how to do the following:

Report security vulnerabilities in Cisco products Obtain assistance with security incidents that involve Cisco products Register to receive security information from Cisco
A current list of security advisories, 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
Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
For emergencies only security-alert@cisco.com An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
For nonemergencies psirt@cisco.com 1 877 228-7302 1 408 525-6532
In an emergency, you can also reach PSIRT by telephone:

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
xvi
Preface Product Alerts and Field Notices
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.
Product Alerts and Field Notices

Modifications to or updates about Cisco products are announced in Cisco Product Alerts and Cisco Field Notices. You can receive Cisco Product Alerts and Cisco Field Notices by using the Product Alert Tool on Cisco.com. This tool enables you to create a profile and choose those products for which you want to receive information. 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
Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day at this URL: http://www.cisco.com/techsupport Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL: http://tools.cisco.com/RPF/register/register.do
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
xvii
Preface Obtaining Technical Assistance
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.
Tip
Displaying and Searching on Cisco.com 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.
Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL: http://www.cisco.com/techsupport/servicerequest For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly. To open a service request by telephone, use one of the following numbers: Asia-Pacific: +61 2 8446 7411 Australia: 1 800 805 227 EMEA: +32 2 704 55 55 USA: 1 800 553 2447 For a complete list of Cisco TAC contacts, go to this URL: http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions. Severity 1 (S1)An existing network is down or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation. Severity 2 (S2)Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
xviii
Preface Obtaining Additional Publications and Information
Severity 3 (S3)Operational performance of the network is impaired while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels. Severity 4 (S4)You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
The Cisco Online Subscription Center is the website where you can sign up for a variety of Cisco e-mail newsletters and other communications. Create a profile and then select the subscriptions that you would like to receive. To visit the Cisco Online Subscription Center, go to this URL: http://www.cisco.com/offer/subscribe The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco channel product offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL: http://www.cisco.com/go/guide 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 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 Whats 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 Whats New in Cisco Documentation at this URL: http://www.cisco.com/univercd/cc/td/doc/abtunicd/136957.htm
xix
Preface Obtaining Additional Publications and Information
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
Whats 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 Whats 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
xx
C H A P T E R
Introduction to Cisco IOS XR Software

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
Supported Standalone System Configurations

The Cisco IOS XR software runs on the following standalone systems:

Cisco CRS-1 8-Slot Line Card Chassis (LCC) Cisco CRS-1 16-Slot LCC Cisco XR 12006 Router Cisco XR 12008 Router Cisco XR 12010 Router Cisco XR 12012 Router Cisco XR 12016 Router Cisco XR 12404 Router Cisco XR 12406 Router Cisco XR 12410 Router Cisco XR 12416 Router
1-1
Chapter 1 Cisco CRS-1 Multishelf System Overview
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.3. The Cisco IOS XR software also runs on Cisco CRS-1 Multishelf Systems, which are described in the following section.
Cisco CRS-1 Multishelf System Overview

The multishelf system enables multiple Cisco CRS-1 LCCs to act as a single system. This release of the multishelf system supports two 16-slot LCCs and one, two, or four fabric card chassis (FCCs) to provide a total switching capacity of up to 1.28 terabits per second (Tbps). Two external Cisco Catalyst switches provide control-plane connectivity between the chassis. Figure 1-1 shows the single-FCC multishelf system, Figure 1-2 shows the two-FCC multishelf system, and Figure 1-3 shows the four-FCC multishelf system.
1-2
Chapter 1
Introduction to Cisco IOS XR Software Cisco CRS-1 Multishelf System Overview
Figure 1-1
Single-FCC Multishelf System
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
1
1 2
Cisco CRS-1 16-Slot Line Card Chassis (two 3 required) Cisco CRS-1 Fabric Card Chassis (one required)
Cisco Catalyst 6509 Switch (two suggested)
1-3
129492
Chapter 1 Cisco CRS-1 Multishelf System Overview
Figure 1-2
Two-FCC Multishelf System
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
1 2
Cisco CRS-1 16-Slot Line Card Chassis (two 3 required) Cisco CRS-1 Fabric Card Chassis (two required)
1-4
158260
Chapter 1
Introduction to Cisco IOS XR Software Cisco CRS-1 Multishelf System Overview
Figure 1-3
Four-FCC Multishelf System
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
1 2
Cisco CRS-1 16-Slot Line Card Chassis (two 3 required) 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.
1-5
149632
Chapter 1 Router Management Interfaces
Router Management Interfaces

Because new routers are not yet configured for your environment, you must start configuration using the command-line interface (CLI). This guide provides instructions on using the CLI to configure basic router features. The Cisco IOS XR software supports the following router management interfaces, which are described in the following sections:

Command-Line Interface, page 1-6 Craft Works Interface, page 1-6 Extensible Markup Language API, page 1-6 Simple Network Management Protocol, page 1-7
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 xiv.
Craft Works Interface

The Craft Works Interface (CWI) is a client-side application used to configure and manage routers that run the Cisco IOS XR software. CWI includes advanced CLI features and a graphical user interface, and it is included with the Cisco IOS XR Manageability package. The CWI is a desktop used to launch management and configuration applications. The management and configuration features include fault management, configuration management, performance management, security management, and inventory management, with an emphasis on speed and efficiency. For more information, see the Cisco IOS XR software documents listed in the Related Documents section on page xiv.
Extensible Markup Language API

The Extensible Markup Language (XML) application programming interface (API) is an XML interface used for rapid development of client applications and perl scripts to manage and monitor the router. Client applications can be used to configure the router or request status information from the router by encoding a request in XML API tags and sending it to the router. The router processes the request and
1-6
Chapter 1
Introduction to Cisco IOS XR Software Selecting and Identifying the Designated Shelf Controller
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 xiv.
Simple Network Management Protocol

Simple Network Management Protocol (SNMP) is an application-layer protocol designed to facilitate the exchange of management information between network devices. By using SNMP-transported data (such as packets per second and network error rates), network administrators can more easily manage network performance, find and solve network problems, and plan for network growth. The Cisco IOS XR software supports SNMP v1, v2c, and v3. SNMP is part of a larger architecture called the Internet Network Management Framework (NMF), which is defined in Internet documents called RFCs. The SNMPv1 NMF is defined by RFCs 1155, 1157, and 1212, and the SNMPv2 NMF is defined by RFCs 1441 through 1452. SNMP is a popular protocol for managing diverse commercial internetworks and those used in universities and research organizations. SNMP-related standardization activity continues even as vendors develop and release state-of-the-art, SNMP-based management applications. SNMP is a relatively simple protocol, yet its feature set is sufficiently powerful to handle the difficult problems presented in trying to manage the heterogeneous networks of today. For more information, see the Cisco IOS XR software documents listed in the Related Documents section on page xiv.
Selecting and Identifying the Designated Shelf Controller

The designated shelf controller (DSC) controls a standalone router or a multishelf System. A DSC is a role that is assigned to one route processor (RP) card or performance route processor (PRP) card in each router or multishelf system. RP cards operate in Cisco CRS-1 routers, and PRP cards operate in Cisco XR 12000 and 12000 Series routers.
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
1-7
Chapter 1 Selecting and Identifying the Designated Shelf Controller
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
Selecting and Identifying the DSC on Cisco CRS-1 Routers

A Cisco CRS-1 router supports up to two RPs. If only one RP is installed, that RP automatically becomes the DSC. If two RPs are installed, the default configuration selects RP0 as the DSC. To select RP1 to become the DSC for a new installation, install RP1 first, apply power to the system, and wait for RP1 to start up. When the Primary LED on the RP1 front panel lights, RP1 is operating as the DSC, and you can install RP0.
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.
Selecting and Identifying the DSC on Cisco CRS-1 Multishelf Systems

A Cisco CRS-1 Multishelf System supports up to two RPs in each LCC. Each LCC must have at least one RP, so a multishelf system supports between two and four RPs. The RPs in a multishelf system operate much like the RPs in a standalone router. The difference is that only one LCC can host the DSC. During the initial startup of a multishelf system, the DSC is RP0 in the LCC with the lowest configured rack number, which is usually Rack 0. If you want to select RP1 within Rack 0 to become the DSC, install RP1 first, and wait for RP1 to start up. When the Primary LED on the RP1 front panel lights (or the alphanumeric display shows ACTV RP), RP1 is operating as the DSC, and you can install RP0. If you are setting up a new multishelf system, the instructions in Chapter 3, Bringing Up the Cisco IOS XR Software on a Multishelf System, specify the appropriate time to bring up and configure the DSC.
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.
1-8
Chapter 1
Introduction to Cisco IOS XR Software Connecting to the Router Through the Console Port
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 or primary PRP and is identified by the alphanumeric display: PRI 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.
Connecting to the Router Through the Console Port

The first time you connect to a new router with Cisco IOS XR software, you must connect through the Console port on the DSC. Although typical router configuration and management take place using an Ethernet port on the DSC, this port must be configured for your local area network before it can be used. Figure 1-4 shows the RP connections on the Cisco CRS-1 16-Slot Line Card Chassis, and Figure 1-5 shows the RP connections on the Cisco CRS-1 8-Slot Line Card Chassis. Figure 1-6 shows the PRP-2 connections on the Cisco XR 12000 Series Router.
1-9
Chapter 1 Connecting to the Router Through the Console Port
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
Remote terminal for CLI communication
PC Card (disk1:)
CNTL ETH 0
Network Remote CLI, CWI, XML, or SNMP communication
Management Ethernet connection for out-of-band network communciation
CNTL ETH 1 MGMT ETH
Optical Gigabit Ethernet for control plane: (not user configurable)
Status
1-10
116547
Primary
Chapter 1
Figure 1-5
Communication Ports on the RP for a Cisco CRS-1 8-Slot LCC RJ-45 cable
Console AUX
Terminal connection Modem connection
RJ-45 cable
ALARM PID/VID
Remote terminal for CLI communication Ethernet cable
CRITICAL MAJOR MINOR
Network Remote CLI, CWI, XML, or SNMP communication. Remote file storage
MGMT ETH CNTL ETH 0 CNTL ETH 1
Management Ethernet connection for out-of-band network communication Optical Gigabit Ethernet for control plane: (not user configurable)
PC CARD
User-removable flash disk1 stores installation PIE files A second internal flash disk0 stores installed software and active configurations
EXT CLK 1 EXT CLK 2
Primary Status
LED status displays (alphanumeric) Primary RP (on=primary) Card status (green=OK)
149693
1-11
Chapter 1 Connecting to the Router Through the Console Port
Figure 1-6
Communication Ports on the PRP-2 for a Cisco XR 12000 Series Router
-1 OT SL 0 OT SL
Ethernet cable
ETH 0 ETH 1 BITS 0 BITS 1 AUX
Management Ethernet connection for out-of-band network communication
K LIN TA DA K LIN TA DA G SI T AC G SI T AC
RJ-45 cable Remote terminal for CLI communication RJ-45 cable

ETH 2 CONSOLE
Modem connection Terminal connection
1-12
149695
PERFORMANCE ROUTE PROCESSOR 2
RE SE T
LED status displays (alphanumeric)
Chapter 1
To connect to the router, perform the following procedure.
SUMMARY STEPS
1. 2. 3. 4. 5. 6.
Power on the standalone router, or power on Rack 0 in a multishelf system. Identify the DSC. Connect a terminal to the Console port of the DSC. Start the terminal emulation program. Press Enter. Log in to the router.
DETAILED STEPS
Command or Action
Step 1
Purpose
Power on the standalone router, or power on Rack 0 in Starts the router or Rack 0. a multishelf system. This step is required only if the power is not on.
For information on power installation and controls, see the hardware documentation listed in the Related Documents section on page xiv. For more information, see the Selecting and Identifying the Designated Shelf Controller section on page 1-7. During the initial setup, you can communicate with the router only through the Console port of the DSC. The router Console port is designed for a serial cable connection to a terminal or a computer that is running a terminal emulation program. The terminal settings are:
Bits per second: 9600/9600 Data bits: 8 Parity: None Stop bit: 2 Flow control: None
Step 2
Identify the DSC.
Identifies the RP to which you must connect in the next step.
Step 3
Connect a terminal to the Console port of the DSC.
Establishes a communications path to the router.

For information on the cable requirements for the Console port, see the hardware documentation listed in the Related Documents section on page xiv.
1-13
Chapter 1 Where to Go Next
Command or Action
Step 4
Purpose (Optional.) Prepares a computer for router communications.

Start the terminal emulation program.
The step is not required if you are connecting through a terminal. Terminals send keystrokes to and receive characters from another device. If you connect a computer to the Console port, you must use a terminal emulation program to communicate with the router. For instructions on using the terminal emulation program, see the documentation for that program. If no text or router prompt appears when you connect to the console port, press Enter to initiate communications. If no text appears when you press Enter, give the router more time to complete the initial boot procedure, then press Enter. If the prompt gets lost among display messages, press Enter again. If the router has no configuration, the router displays the prompt: Enter root-system username: If the router has been configured, the router displays the prompt: Username:
Step 5
Press Enter.
Initiates communication with the router.
Step 6
Log in to the router.
Establishes your access rights for the router management session.
Enter the root-system username and password or the username and password provided by your system administrator. After you log in, the router displays the CLI prompt, which is described in the CLI Prompt section on page 4-12. If the router prompts you to enter a root-system username, the router is not configured, and you should follow one of the bring up procedures mentioned in the next section.
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
1-14
C H A P T E R
Bringing Up the Cisco IOS XR Software on a Standalone Router

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

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-9
Prerequisites
The following sections describe the software and hardware requirements for bringing up a standalone system.
2-1
Chapter 2 Bringing Up and Configuring a Standalone Router
Software Requirements
The multishelf system requires the following software:

Cisco IOS XR Software Release 3.3.1 ROMMON 1.40 or higher on each RP in the system
Caution
The ROM Monitor software must be upgraded to version 1.40 or higher on all RPs before a Cisco CRS-1 system is upgraded to Cisco IOS XR Software Release 3.3.1 or higher 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 -xvii.
Hardware Prerequisites and Documentation

The Cisco IOS XR software runs on the routers listed in the Supported Standalone System Configurations section on page 1-1. Before a router can be started, the following hardware management procedures must be completed:

Site preparation Equipment unpacking Router installation
For information on how to complete these procedures for your router equipment, see the hardware documents listed in the Related Documents section on 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 xiv for a complete listing of available documents.
Bringing Up and Configuring a Standalone Router

To bring up a standalone router, you need to connect to the router and configure root-system username and password as described in the following procedure:
SUMMARY STEPS
1. 2. 3. 4.
Establish a connection to the DSC Console port. Type the username for the root-system login and press Return. Type the password for the root-system login and press Return. Log in to the router.
2-2
Chapter 2
Bringing Up the Cisco IOS XR Software on a Standalone Router Bringing Up and Configuring a Standalone Router
DETAILED STEPS
Command or Action
Step 1
Purpose Initiates communication with the router.
Establish a connection to the DSC Console port.
For instructions on connecting to the Console port, see the Connecting to the Router Through the Console Port section on page 1-9. If the router has been configured, the router displays the prompt: Username: If the Username prompt appears, skip this procedure and continue general router configuration as described in Chapter 4, Configuring General Router Features.
Step 2 Step 3 Step 4
Type the username for the root-system login and press Sets the root-system username, which is used to log in to the Return. router. Type the password for the root-system login and press Creates an encrypted password for the root-system Return. username. Retype the password for the root-system login and press Return. Allows the router to verify that you have entered the same password both times.
If the passwords do not match, the router prompts you to repeat the process.
Step 5

Enter the root-system username and password that were created earlier in this procedure. After you log in, the router displays the CLI prompt, which is described in the CLI Prompt section on page 4-12.
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 ---
Enter root-system username: cisco Enter secret: Enter secret again: RP/0/0/CPU0:Jan 10 12:50:53.105 : exec[65652]: %MGBL-CONFIG-6-DB_COMMIT : 'Administration configuration committed by system'. Use 'show configuration commit changes 2000000009' to view the changes. Use the 'admin' mode 'configure' command to modify this configuration.
2-3
Chapter 2 Verifying the System After Initial Bring-Up
User Access Verification 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.
Verifying the System After Initial Bring-Up

To verify the status of the router, perform the following procedure:
SUMMARY STEPS
1. 2.
show version admin show platform [node-id] end show redundancy show environment
3. 4.
2-4
Chapter 2
Bringing Up the Cisco IOS XR Software on a Standalone Router Verifying the System After Initial Bring-Up
DETAILED STEPS
Command or Action
Step 1
show version
Purpose Displays information about the router, including image names, uptime, and other system information. Places the router in administration EXEC mode, displays information about the status of cards and modules installed in the router, and terminates administration EXEC mode.
RP/0/RP0/CPU0:router# show version
Step 2
admin show platform [node-id] exit RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# show platform RP/0/RP0/CPU0:router(admin)# exit
Some cards support a CPU module and service processor (SP) module. Other cards support only a single module. A card module is also called a node. When a node is working properly, the status of the node in the State column is IOS XR RUN. Type the show platform node-id command to display information for a specific node. Replace node-id with a node name from the show platform command Node column. To view the status of all cards and modules, the show platform command must be executed in administration EXEC mode.
Note
Step 3
show redundancy
Example:
RP/0/RP0/CPU0:router# show redundancy
Displays the state of the primary (active) and standby (inactive) RPs, including the ability of the standby to take control of the system.
If both RPs are working correctly, one node displays active role, the Partner node row displays standby role, and the Standby node row displays Ready.
Step 4
show environment
Displays information about the hardware attributes and status.
Example:
RP/0/RP0/CPU0:router# show environment
Examples of show Commands

The following sections provide examples of show commands:

show version Command, page 2-6 show environment Command, page 2-6 show platform Command, page 2-8 show redundancy Command, page 2-9
2-5
show version Command
To display basic information about the router configuration, type the show version command in EXEC mode, as shown in the following example:
RP/0/RP1/CPU0:CRS-8_P1# show version Cisco IOS XR Software, Version 3.3.0[2I] Copyright (c) 2006 by cisco Systems, Inc. ROM: System Bootstrap, Version 1.38(20050525:193559) [CRS-1 ROMMON], CRS-8_P1 uptime is 1 week, 1 day, 17 hours, 1 minute System image file is "disk0:hfr-os-mbi-3.3.0/mbihfr-rp.vm" cisco CRS-8/S (7457) processor with 4194304K bytes of memory. 7457 processor at 1197Mhz, Revision 1.2 16 Packet over SONET/SDH network interface(s) 16 SONET/SDH Port controller(s) 2 Ethernet/IEEE 802.3 interface(s) 16 GigabitEthernet/IEEE 802.3 interface(s) 2043k bytes of non-volatile configuration memory. 38079M bytes of hard disk. 1000592k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes). 1000640k bytes of ATA PCMCIA card at disk 1 (Sector size 512 bytes). Package active on node 0/1/SP: hfr-diags, V 3.3.0[2I], Cisco Systems, at disk0:hfr-diags-3.3.0 Built on Mon Mar 13 12:58:02 UTC 2006 By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8 hfr-admin, V 3.3.0[2I], Cisco Systems, at disk0:hfr-admin-3.3.0 Built on Mon Mar 13 11:46:36 UTC 2006 By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8 hfr-base, V 3.3.0[2I], Cisco Systems, at disk0:hfr-base-3.3.0 Built on Mon Mar 13 11:43:22 UTC 2006 By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8 hfr-os-mbi, V 3.3.0[2I], Cisco Systems, at disk0:hfr-os-mbi-3.3.0 Built on Mon Mar 13 11:27:02 UTC 2006 By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8 --More--
show environment Command
To display environmental monitor parameters for the system, use the show environment command in EXEC or administration EXEC mode. The following command syntax is used: show environment [options]
2-6
Chapter 2
Bringing Up the Cisco IOS XR Software on a Standalone Router Verifying the System After Initial Bring-Up
Enter the show environment ? command to display the command options. In the following example, temperature information for a Cisco CRS-1 router is shown:
RP/0/RP0/CPU0:router# show environment temperatures R/S/I Modules Inlet Temperature (deg C) Exhaust Temperature (deg C) Hotspot Temperature (deg C)
0/1/* host cpu fabricq0 fabricq1 ingressq egressq ingresspse egresspse jacket spa0 spa5 0/6/* host cpu fabricq0 fabricq1 ingressq egressq ingresspse egresspse jacket spa0 spa4 spa5 0/RP0/* host 0/RP1/* host 23 24 24, 32, 26, 24, 26 23 24 24, 33, 26, 24, 27 32, 26 27, 25 33 35 27 32 37 25 31 29 26 25, 31 33, 35 24 32, 30 26, 27 35 34 27 32 37 27 35 29 25 25, 32 24
32
25 19 25
24
30
24 19 22 24
25
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 0/1/*: Module (host) LED status says: OK 0/1/*: Module (jacket) LED status says: OK 0/1/*: Module (spa0) LED status says: OK 0/1/*: Module (spa5) LED status says: OK 0/6/*: Module (host) LED status says: OK 0/6/*: Module (jacket) LED status says: OK 0/6/*: Module (spa0) LED status says: OK 0/6/*: Module (spa4) LED status says: OK 0/6/*: Module (spa5) LED status says: OK 0/RP0/*: Module (host) LED status says: OK 0/RP0/*: Alarm LED status says: NONE 0/RP1/*: Module (host) LED status says: OK 0/RP1/*: Alarm LED status says: NONE
See the Cisco IOS XR Interface and Hardware Component Command Reference for more information.
2-7
show platform Command
The show platform command displays information on router resources. In EXEC mode, the show platform command displays the resources assigned to the secure domain router (SDR) you are managing. In administration EXEC mode, the show platform command displays all router resources.
Note
SDRs are introduced in Chapter 4, Configuring General Router Features. 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 Node Type PLIM State Config State ----------------------------------------------------------------------------0/1/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON 0/1/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON 0/1/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON 0/6/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON 0/6/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON 0/6/4 MSC(SPA) 8XOC3/OC12-POS OK PWR,NSHUT,MON 0/6/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON 0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON
The following administration EXEC mode sample output displays all router nodes:
RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# show platform Node Type PLIM State Config State ----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/1/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON 0/1/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON 0/1/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON 0/6/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/6/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON 0/6/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON 0/6/4 MSC(SPA) 8XOC3/OC12-POS OK PWR,NSHUT,MON 0/6/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON 0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 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.
2-8
Chapter 2
Bringing Up the Cisco IOS XR Software on a Standalone Router Where to Go Next
In the following example, information is shown for a single node in a Cisco CRS-1 router:
RP/0/RP0/CPU0:CRS-8_P1# show platform 0/1/CPU0 Node Type PLIM State Config State ----------------------------------------------------------------------------0/1/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON
For more information on node IDs, see the Displaying SDR Node IDs and Status section on page 8-12. For more information on the show platform command, see the Cisco IOS XR Interface and Hardware Component Command Reference.
show redundancy Command
To display information about the active and standby (inactive) RPs, enter the show redundancy command as follows:
RP/0/RP0/CPU0:CRS-8_P1# show redundancy Redundancy information for node 0/RP0/CPU0: ========================================== Node 0/RP0/CPU0 is in ACTIVE role Partner node (0/RP1/CPU0) is in STANDBY role Standby node in 0/RP1/CPU0 is ready Reload and boot info ---------------------RP reloaded Wed Feb 15 13:58:32 2006: 1 week, 6 days, 22 hours, 49 minutes ago Active node booted Wed Feb 15 13:58:32 2006: 1 week, 6 days, 22 hours, 49 minuto Standby node boot Wed Feb 15 13:59:00 2006: 1 week, 6 days, 22 hours, 49 minuteo Standby node last went not ready Wed Mar 1 07:40:00 2006: 5 hours, 8 minutes ao Standby node last went ready Wed Mar 1 07:40:00 2006: 5 hours, 8 minutes ago There have been 0 switch-overs since reload
Where to Go Next
For information on configuring basic router features, see Chapter 4, Configuring General Router Features.
2-9
2-10
C H A P T E R
Bringing Up the Cisco IOS XR Software on a Multishelf System

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

Prerequisites, page 3-1 Restrictions, page 3-3 Information About Bringing Up a Multishelf System, page 3-3 Configuring the External Cisco Catalyst 6509 Switches, page 3-8 Bringing Up and Configuring Rack 0, page 3-21 Bringing Up and Verifying FCCs, page 3-27 Bringing Up and Verifying the Non-DSC LCC, page 3-31 Verifying the Spanning Tree, page 3-32 Verifying Fabric Cabling Connections, page 3-38 Where to Go Next, page 3-41
Prerequisites
The following sections describe the software and hardware requirements for bringing up a multishelf system.
3-1
Chapter 3 Prerequisites
The multishelf system requires the following software:

Cisco IOS XR Software Release 3.3.1 ROMMON 1.40 or higher on each RP in the system
Caution
The ROM Monitor software must be upgraded to version 1.40 or higher on all RPs before a Cisco CRS-1 system is upgraded to Cisco IOS XR Software Release 3.3.1 or higher 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 -xvii. In addition, Cisco CRS-1 Multishelf systems should be upgraded to ROMMON release 1.40 before being upgraded to IOS XR Release 3.3.1 to ensure RPs are assigned the correct rack numbers during system boot. For more information, see Cisco IOS XR ROM Monitor Guide.
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. Both systems 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 xiv.
3-2
Chapter 3
Bringing Up the Cisco IOS XR Software on a Multishelf System Restrictions
Restrictions
The following restrictions apply to multishelf systems in Cisco IOS XR Software Release 3.3.
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 8-slot LCCs are not supported. Although Cisco IOS XR Software Release 3.3 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 xvii).
Information About Bringing Up a Multishelf System

The following sections provide information that is good to know before you bring up a multishelf system:

Bringup Overview, page 3-3 Preparing a Rack Number Plan, page 3-3
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. 2. 3. 4. 5.
Configuring the External Cisco Catalyst 6509 Switches, page 3-8 Bringing Up and Configuring Rack 0, page 3-21 Bringing Up and Verifying FCCs, page 3-27 Bringing Up and Verifying the Non-DSC LCC, page 3-31 Verifying the Spanning Tree, page 3-32
During the bringup procedure, you need the information presented in the following section.
Preparing a Rack Number Plan

In a multishelf system, each chassis must be assigned a unique rack number, as shown in Figure 3-1. This rack number is used to identify a chassis in the system, and maintain the software and configurations for the chassis.
3-3
Chapter 3 Information About Bringing Up a Multishelf System
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.
Figure 3-1 DSC in a CRS-1/M-F1 Multishelf System
Gigabit Ethernet Control Bus
Fabric Cards
OIM-LED 1 OIM23 OIM22 OIM21 SM0 SM1 SM2 SM3 OIM16 OIM15 OIM14 OIM13 OIM12
SC
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
Catalyst 6509 Switches
Fabric Cards
OIM-LED 1 OIM23 OIM22 OIM21 SM4 RP (SC) RP (SC) SM7 OIM16 OIM15 OIM14 OIM13 OIM12
SC
DSC
Line Card Chassis Rack 1

Note
Fabric Card Chassis Rack F0
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 1, Table 2 and Table 3. Table 1 shows a sample rack number plan for a single-FCC system.
Table 1 Sample Rack Number Plan for a Single-FCC Multishelf System
Chassis LCC containing the active DSC Non-DSC LCC Fabric chassis
Serial ID
Rack Number 0 1 F0
3-4
138118
Chapter 3
Bringing Up the Cisco IOS XR Software on a Multishelf System Information About Bringing Up a Multishelf System
Table 2 shows a sample rack number plan for a two-FCC system.

Table 2 Sample Rack Number Plan for a Two-FCC Multishelf System
Chassis LCC containing the active DSC Non-DSC LCC Fabric chassis 0 Fabric chassis 1
Serial ID
Rack Number 0 1 F0 F1
Table 3 shows a sample rack number plan for a four-FCC system.

Table 3 Sample Rack Number Plan for a Four-FCC Multishelf System
Chassis LCC containing the active DSC Non-DSC LCC Fabric chassis 0 Fabric chassis 1 Fabric chassis 2 Fabric chassis 3
Serial ID
Rack Number 0 1 F0 F1 F2 F3
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 2 and Figure 3.
3-5
Chapter 3 Information About Bringing Up a Multishelf System
Figure 2
Location of the Serial Number on a Fabric Card Chassis
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
9 5 1 10 6 2 11 7 3 12 8 4
3-6
129761, 781-00375-01
Chapter 3
Bringing Up the Cisco IOS XR Software on a Multishelf System Information About Bringing Up a Multishelf System
Figure 3
Location of the Serial Number on a Line Card Chassis
PWR OK FLT AC FAIL CB TRIP I LIM OT PWR OK FLT AC FAIL CB TRIP I LIM OT PWR OK FLT AC FAIL CB TRIP I LIM OT
PWR OK FLT AC FAIL CB TRIP I LIM OT PWR OK FLT AC FAIL CB TRIP I LIM OT PWR OK FLT AC FAIL CB TRIP I LIM OT
SN: AAANNNNXXXX
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.
116535
3-7
Chapter 3 Configuring the External Cisco Catalyst 6509 Switches
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-21 for complete instructions to bring up a new router and configure the rack numbers.
Configuring the External Cisco Catalyst 6509 Switches

The control Ethernet network is formed by interconnecting each RP and shelf controller Gigabit Ethernet (SCGE) card in the system through two external Catalyst switches. (The SCGE card is the control card in an FCC.) The Catalyst switches are also directly connected using one or more Gigabit Ethernet links (see Figure 4). These Catalyst switches must also be configured for operation with the Cisco CRS-1 multishelf router. This section includes instructions to configure and verify the Catalyst switches using the Cisco IOS Software. For instructions to install and cable the Catalyst switches, see CRS-1 Multishelf System Interconnection and Cabling Guide. This section includes the following topics:

Prerequisites, page 3-9 Restrictions, page 3-10 Before You Begin, page 3-11 Information About the Catalyst Switch Configuration, page 3-11 Configuring the Catalyst Switches, page 3-11 Verifying the Catalyst Switch, page 3-19
3-8
Chapter 3
Bringing Up the Cisco IOS XR Software on a Multishelf System Configuring the External Cisco Catalyst 6509 Switches
Figure 4
Control Ethernet Network Connections in a Single-FCC System
RP
Catalyst Ethernet Switch
RP Line Card Chassis SCGE
SCGE Fabric Card Chassis Catalyst Ethernet Switch
RP
RP Line Card Chassis

138147
Prerequisites
The following sections describe the software and hardware requirements for bringing up Catalyst 6509 Switches in a multishelf system.
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
3-9
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: Description Part
Quantity 1 1 1 1 1 8 1 2 2
Catalyst 6509 Chassis, 9slot, 15RU, No Pow Supply, No Fan WS-C6509 Tray Cisco CAT6000-SUP720 IOS IP (see Software Requirements for complete details). Catalyst 6500/Cisco 7600 Supervisor 720 Fabric MSFC3 PFC3B Catalyst 6500 Sup720 Compact Flash Mem 256MB Catalyst 6000 16-port Gig-Ethernet Mod. (Req. GBICs) 1000BASE-LX/LH long haul GBIC (singlemode or multimode) Catalyst 6509 High Speed Fan Tray Catalyst 6000 2500W AC Power Supply Power Cord, 250Vac 16A, straight blade NEMA 6-20 plug, US S733Z-12217SXB WS-SUP720-3B MEM-C6K-CPTFL256M WS-X6416-GBIC WS-G5486 WS-C6K-9SLOT-FAN2 WS-CAC-2500W CAB-AC-2500W-US1
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.
3-10
Chapter 3
Before You Begin

Before you begin to bring up the Catalyst 6509 switches, consider the following:

The Catalyst switches must be installed, including all cables properly connected between the switches and the Cisco CRS-1 router. See the Related Documents section on page xiv for a hyperlink to documents on installing and connecting the Catalyst switches. For additional information regarding Cisco IOS commands and usage, see the Cisco IOS Software Configuration page at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/index.htm
Information About the Catalyst Switch Configuration

The configuration described in the following sections places all Catalyst ports in VLAN 1. The configuration on the Catalyst switches is the same as the configuration on the Cisco CRS-1 router internal Broadcom switchesthey all participate in a Multiple Spanning Tree (MST) region with one MST instance. The Catalyst switches are made the root of the network by assigning them the highest priority. Because there are two Catalyst switches, one is selected as the root-bridge device. 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.
Configuring the Catalyst Switches

The Cisco IOS software configuration must be applied to both external Catalyst switches.
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.
3-11
To configure the Catalyst 6509 Switches, use the following procedure:
Summary Steps
1. 2. 3. 4. 5. 6. 7. 8. 9.
configure spanning-tree portfast default spanning-tree mode mst spanning-tree mst configuration name mst_region revision number instance instance_id vlan range end 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 19. switchport access vlan 1 20. end 21. Repeat Step 16 to Step 20 for all interfaces. 22. Repeat all steps for the second switch.
Detailed Steps
Command or Action
Step 1
configure
Purpose Places the switch in global configuration mode.
Example:
router# configure
Step 2
spanning-tree mode mst
Selects the MST mode for the spanning tree protocol.
Example:
router(config)# spanning-tree mode mst
3-12
Chapter 3
Command or Action
Step 3
spanning-tree portfast default
Purpose Enables PortFast by default on all access ports.
Example:
router(config)# spanning-tree portfast default
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.
Example:
router(config-mst)# revision 1
This number must be identical on both switches.
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:
router(config)# spanning-tree mst hello-time 1
We recommend 1 second.
Step 10
spanning-tree mst forward-time seconds
Sets the forward-delay timer for all MST instances on the switch.
Example:
router(config)# spanning-tree mst forward-time 6
We recommend 6 seconds.
Step 11
spanning-tree mst max-age seconds
Sets the max-age timer for all MST instances on the switch.
Example:
router(config)# spanning-tree mst max-age 8
We recommend 8 second.
Step 12
spanning-tree mst max-hops hops
Specifies the number of possible hops in the region before a BPDU is discarded.
Example:
router(config)# spanning-tree mst max-hops 4
We recommend 4 hops.
3-13
Command or Action
Step 13
spanning-tree mst instance_id priority priority
Purpose Sets the spanning tree priority for the switch.
Example:
router(config)# spanning-tree mst 0-1 priority 28672
The primary Catalyst switch should be configured with priority 0. This makes the switch the root of the network. The second Catalyst switch should be configured 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.
Step 14
udld aggressive
Enables the Unidirectional Link Detection (UDLD) protocol aggressive mode.
Example:
router(config)# udld aggressive
Step 15
udld message time interval
Example:
router(config)# udld message time 7
Configures the time between UDLD probe messages on ports that are in advertisement mode and are currently determined to be bidirectional

Valid values are from 7 to 90 seconds. We recommend 7 seconds.
Step 16
interface gigabitethernet slot/port
Enters interface configuration mode for the specified interface.
Example:
router(config)# interface GigabitEthernet3/1
Step 17
switchport
Example:
router(config-if)# switchport
Configures a LAN interface as a Layer 2 interface in preparation for additional switchport commands. Specifies a nontrunking, nontagged single-VLAN Layer-2 interface.
Step 18
switchport mode access
Example:
router(config-if)# switchport mode access
Step 19
switchport access vlan 1
(Optional) Assigns ports to VLAN 1, which is the default selection.
Example:
router(config-if)# switchport access vlan 1
Step 20
end
Exits interface configuration mode and returns to global configuration mode.
Example:
router(config-if)# end
3-14
Chapter 3
Command or Action
Step 21
Purpose Configures remaining interfaces.
Repeat Step 16 to Step 20 for all interfaces.
Repeat this configuration for each port, including ports that are not currently being used (for example, interface gigabitethernet 0/1).
Step 22
Repeat all steps for the second switch.
Configures a second switch for redundancy.
Example to Configure a Single-FCC Multishelf System

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 configuring. When additional FCCs are present, additional interfaces must be configured for the connections to those FCCs.
Example to Configure the First Catalyst Switch:
CAT6k-1# configure CAT6k-1(config)# spanning-tree portfast default CAT6k-1(config)# spanning-tree mode mst CAT6k-1(config)# no spanning-tree optimize bpdu transmission CAT6k-1(config)# spanning-tree mst configuration CAT6k-1(config-mst)# name STP_1 CAT6k-1(config-mst)# revision 1 CAT6k-1(config-mst)# instance 1 vlan 1 CAT6k-1(config-mst)# end CAT6k-1(config)# spanning-tree mst hello-time 1 CAT6k-1(config)# spanning-tree mst forward-time 6 CAT6k-1(config)# spanning-tree mst max-age 8 CAT6k-1(config)# spanning-tree mst max-hops 4 CAT6k-1(config)# spanning-tree mst 0-1 priority 0 CAT6k-1(config)# udld aggressive CAT6k-1(config)# udld message time 7 CAT6k-1(config)# interface gigabitethernet 0/1 CAT6k-1(config-if)# switchport CAT6k-1(config-if)# switchport mode access CAT6k-1(config-if)# switchport access vlan 1 CAT6k-1(config-if)# end
Example to Configure the Second Catalyst Switch:

CAT6k-2# configure CAT6k-2(config)# spanning-tree portfast default CAT6k-2(config)# spanning-tree mode mst CAT6k-2(config)# no spanning-tree optimize bpdu transmission CAT6k-2(config)# spanning-tree mst configuration CAT6k-2(config-mst)# name STP_1 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
3-15
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
Example Configuration for a Four-FCC Multishelf System

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 configuring. 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... Current configuration : 2873 bytes ! version 12.2 service timestamps debug uptime service timestamps log uptime no service password-encryption service counters max age 10 ! hostname Router ! logging snmp-authfail ! ip subnet-zero ! ! ! mpls ldp logging neighbor-changes no mls flow ip no mls flow ipv6 mls cef error action freeze ! power redundancy-mode combined ! spanning-tree mode mst spanning-tree portfast default no spanning-tree optimize bpdu transmission spanning-tree extend system-id ! spanning-tree mst configuration name STP_1 revision 1 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 !
3-16
Chapter 3
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 switchport mode access spanning-tree portfast ! interface GigabitEthernet1/9 no ip address switchport switchport mode access spanning-tree portfast !
3-17
interface GigabitEthernet1/10 no ip address switchport switchport mode access spanning-tree portfast ! interface GigabitEthernet1/11 no ip address switchport switchport mode access spanning-tree portfast ! interface GigabitEthernet1/12 no ip address switchport switchport mode access spanning-tree portfast ! interface GigabitEthernet1/13 no ip address switchport switchport mode access spanning-tree portfast ! interface GigabitEthernet1/14 no ip address switchport switchport mode access spanning-tree portfast ! interface GigabitEthernet1/15 no ip address switchport switchport mode access spanning-tree portfast ! interface GigabitEthernet1/16 no ip address switchport switchport mode access spanning-tree portfast ! interface GigabitEthernet5/1 no ip address shutdown ! interface GigabitEthernet5/2 no ip address shutdown ! interface Vlan1 no ip address shutdown ! ip classless no ip http server ! ! ! ! !
3-18
Chapter 3
line con 0 line vty 0 4 login ! End
Verifying the Catalyst Switch

As each rack in the multishelf system is brought up, verify that the Catalyst switch links are operating correctly by completing the tasks in the following sections:

Verify the Interface Status Verify Communication Between the Catalyst Switch and an LCC or FCC Verify that the Links are Not Unidirectional
Verify the Interface Status

To verify that the interfaces are connected, enter the command show interfaces status. Enter the command on a terminal connected to each Catalyst switch.
CAT6k-1# show interfaces status Port Name Status Vlan Duplex Speed Type Gi1/1 connected 1 full 1000 1000BaseLH Gi1/2 connected 1 full 1000 1000BaseLH Gi1/3 connected 1 full 1000 1000BaseLH Gi1/4 connected 1 full 1000 1000BaseLH Gi1/5 connected 1 full 1000 1000BaseLH Gi1/6 connected 1 full 1000 1000BaseLH Gi1/7 disabled 1 full 1000 1000BaseSX Gi1/8 disabled 1 full 1000 1000BaseSX Gi1/9 disabled 1 full 1000 1000BaseSX Gi1/10 disabled 1 full 1000 1000BaseSX Gi1/11 disabled 1 full 1000 1000BaseSX Gi1/12 disabled 1 full 1000 1000BaseSX Gi1/13 disabled 1 full 1000 1000BaseSX Gi1/14 disabled 1 full 1000 1000BaseSX Gi1/15 disabled 1 full 1000 1000BaseSX Gi1/16 disabled 1 full 1000 1000BaseSX Gi5/1 disabled 1 full 1000 1000BaseSX Gi5/2 connected routed a-full a-100 10/100/1000BaseT CAT6k-1#
Verify Communication Between the Catalyst Switch and an LCC or FCC

To verify that the Catalyst switch is communicating with an LCC or FCC in forwarding mode, enter the command show spanning tree. This command displays the states of the spanning tree ports. Verify that the ports used to connect the DSC, remote LCC RP, and FCC SCGE are in the FWDG state.
3-19
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 xvii.
CAT6k-1# show spanning-tree MST00 Spanning tree enabled protocol mstp Root ID Priority 0 Address 0013.1a4f.75c0 This bridge is the root Hello Time 1 sec Max Age 8 sec Forward Delay 6 sec Bridge ID Priority 0 (priority 0 sys-id-ext 0) Address 0013.1a4f.75c0 Hello Time 1 sec Max Age 8 sec Forward Delay 6 sec Interface Role Sts Cost Prio.Nbr Type ---------------- ---- --- --------- -------- -------------------------------Gi1/1 Gi1/2 Gi1/3 Gi1/4 Gi1/5 Gi1/6 Desg Desg Desg Desg Desg Desg FWD FWD FWD FWD FWD FWD 20000 20000 20000 20000 20000 20000 128.1 128.2 128.3 128.4 128.5 128.6 P2p P2p P2p P2p P2p P2p
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 ---------------- ---- --- --------- -------- -------------------------------Gi1/1 Desg Gi1/2 Desg Gi1/3 Desg Gi1/4 Desg Gi1/5 Desg Gi1/6 Desg CAT6k-1# FWD FWD FWD FWD FWD FWD 20000 20000 20000 20000 20000 20000 128.1 128.2 128.3 128.4 128.5 128.6 P2p P2p P2p P2p P2p P2p
Verify that the Links are Not Unidirectional

After an LCC or FCC is brought up, verify that the Catalyst links are operating correctly. If a link has a partial fiber cut or a bad optic, the control Ethernet network can become unidirectional and cause a loop. To verify the links in a Catalyst switch using the Cisco IOS software, enter the command show interface in EXEC mode.
3-20
Chapter 3
Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Configuring Rack 0
In the following example, the command is entered for a specific port. The keywords | inc Gig narrows the output to Gigabit Ethernet ports.
Router# show interface gi 6/1 | inc Gig GigabitEthernet6/1 is up, line protocol is up (connected) 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.
Bringing Up and Configuring Rack 0

When the control network has been established by installing, cabling, and configuring the Catalyst switches, it is time to bring up and configure Rack 0 in the multishelf system, as described in the following procedure.
Summary Steps
1. 2. 3. 4. 5. 6. 7. 8. 9.
Power down all LCCs and FCCs. Apply power to the LCC that contains the DSC. Connect to the DSC console port and log in. admin configure dsc serial serial ID rack 0 dsc serial serial ID rack rackNumber dsc serial serial ID rack Fn commit
10. show running-config | include dsc 11. controllers fabric plane planeNumber
oim count 1 oim instance 0 location Frack/slot/FM

12. commit 13. end
3-21
Chapter 3 Bringing Up and Configuring Rack 0
Detailed Steps
Command or Action
Step 1
Purpose Prepares the LCCs and FCCs for startup in the proper sequence.
Power down all LCCs and FCCs.
Each LCC and FCC should be powered up in the order specified in this chapter. Allow the rack to fully boot. Verify that IOS XR RUN appears on the RP faceplates. See the Cisco CRS-1 documentation web page listed in the Related Documents section on page xiv for site planning information including DSC placement.
Step 2
Apply power to the LCC that contains the DSC.
Boots the LCC containing the DSC.

Step 3
Connect to the DSC console port and log in.
Establishes a CLI management session with the router. For more information, see the Connecting to the Router Through the Console Port section on page 1-9.
Step 4
admin
Places the router in administration EXEC mode.
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.
Example:
RP/0/RP0/CPU0:router(admin-config)# dsc serial TBA00000001 rack 0
The LCC containing the DSC should be configured with the lowest rack number. 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.
3-22
Chapter 3
Command or Action
Step 7
dsc serial serial ID rack rackNumber
Purpose Defines the rack number for the second LCC.
Example:
RP/0/RP0/CPU0:router(admin-config)# dsc serial TBA00000002 rack 1
See the Preparing a Rack Number Plan section on page 3-3 for information on locating the serial numbers and selecting rack numbers. Replace serial ID with the serial number of the second LCC. Replace rackNumber with a number in the range of 1 to 255. When each subsequent LCC comes on line, the DSC examines the chassis serial number and automatically assigns the correct rack number to that chassis. See the Preparing a Rack Number Plan section on page 3-3 for information on locating the serial numbers and selecting rack numbers. Enter this command for every FCC in the multishelf system. Replace serial ID with the serial number of the FCC. Replace n with the FCC rack number. These numbers begin with F0 and increment to F1, F2, and F3. When each subsequent rack comes on line, the DSC examines the chassis serial number and automatically assigns the correct rack number to that chassis.
Step 8
dsc serial serial ID rack Fn
Defines the rack number for an FCC.
Example:
RP/0/RP0/CPU0:router(admin-config)# dsc serial TBA00000003 rack F0
Step 9
commit
Commits the target configuration to the router running configuration.
Example:
RP/0/RP0/CPU0:router(admin-config)# commit
Step 10
show running-config | include dsc
Example:
RP/0/RP0/CPU0:router(admin-config)# show running-config | include dsc
Displays the committed rack number configuration. Verify that the serial numbers entered for each chassis are correct.
3-23
Command or Action
Step 11
controllers fabric plane planeNumber oim count 1 oim instance 0 location Frack/SMslot/FM
Purpose Configures a plane to operate in an FCC slot.

Enter this command sequence for each of the eight fabric planes. Replace planeNumber with the number of the plane (0 to 7) you want to configure. Replace rack with the FCC rack number assigned to the FCC that hosts the plane. Replace slot with the FCC slot number that supports the fabric plane you are configuring. Valid slot numbers are SM0 to SM23. The plane numbers and slot numbers are determined by the hardware installation and cabling. The software configuration must match the hardware configuration. For more information, see Cisco CRS-1 Carrier Routing System Multishelf System Interconnection and Cabling Guide.
Example:
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
Step 12
commit
Example:
Step 13
end
Exits administration configuration mode and enters administration EXEC mode.
Example:
RP/0/RP0/CPU0:router(admin-config)# end RP/0/RP0/CPU0:router(admin)#
Examples
This section contains examples for the following subjects:

Example: Configuring and Verifying the Rack Numbers in a Single-FCC Multishelf System, page 3-24 Example: Mapping Each Fabric Plane in a Single-FCC Multishelf System, page 3-25 Example: Mapping Each Fabric Plane in a Two-FCC Multishelf System, page 3-25 Example: Mapping Each Fabric Plane in a Four-FCC Multishelf System, page 3-26
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
3-24
Chapter 3
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)#
Example: Mapping Each Fabric Plane in a Single-FCC Multishelf System

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)# controllers fabric plane 1 RP/0/RP0/CPU0:router(admin-config)# oim count 1 RP/0/RP0/CPU0:router(admin-config)# oim instance 0 location F0/SM6/FM RP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 2 RP/0/RP0/CPU0:router(admin-config)# oim count 1 RP/0/RP0/CPU0:router(admin-config)# oim instance 0 location F0/SM3/FM RP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 3 RP/0/RP0/CPU0:router(admin-config)# oim count 1 RP/0/RP0/CPU0:router(admin-config)# oim instance 0 location F0/SM0/FM RP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 4 RP/0/RP0/CPU0:router(admin-config)# oim count 1 RP/0/RP0/CPU0:router(admin-config)# oim instance 0 location F0/SM12/FM RP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 5 RP/0/RP0/CPU0:router(admin-config)# oim count 1 RP/0/RP0/CPU0:router(admin-config)# oim instance 0 location F0/SM15/FM RP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 6 RP/0/RP0/CPU0:router(admin-config)# oim count 1 RP/0/RP0/CPU0:router(admin-config)# oim instance 0 location F0/SM18/FM RP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 7 RP/0/RP0/CPU0:router(admin-config)# oim count 1 RP/0/RP0/CPU0:router(admin-config)# oim instance 0 location F0/SM21/FM RP/0/RP0/CPU0:router(admin-config)# commit RP/0/RP0/CPU0:router(admin-config)# end RP/0/RP0/CPU0:router(admin)#
Example: Mapping Each Fabric Plane in a Two-FCC Multishelf System

The following configuration display is an example of a configuration for a four-FCC multishelf system:
P/0/RP0/CPU0:R2D2-L0(admin)# show running-config Building configuration... username admin secret 5 $1$iGx3$0BI/8hOKRUMqtfWC4IUn50 group root-system group cisco-support !
3-25
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
Example: Mapping Each Fabric Plane in a Four-FCC Multishelf System

The following configuration display is an example of a configuration for a four-FCC multishelf system:
P/0/RP0/CPU0:R2D2-L0(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 !
3-26
Chapter 3
Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Verifying FCCs
controllers fabric plane oim count 1 oim instance 0 location ! controllers fabric plane oim count 1 oim instance 0 location ! controllers fabric plane oim count 1 oim instance 0 location ! controllers fabric plane oim count 1 oim instance 0 location ! controllers fabric plane oim count 1 oim instance 0 location ! controllers fabric plane oim count 1 oim instance 0 location ! end
2 F1/SM0/FM 3 F1/SM9/FM 4 F2/SM0/FM 5 F2/SM9/FM 6 F3/SM0/FM 7 F3/SM9/FM
Bringing Up and Verifying FCCs

When Rack 0 is up and configured to support the rack number and FCC fabric plane plans, it is time to bring up and configure the FCC in the multishelf system as described in the following procedure.
Summary Steps
1. 2. 3. 4. 5.
Apply power to all FCCs. show controllers fabric rack all detail show controllers fabric plane all detail show controllers fabric connectivity all detail On the external Catalyst switches, verify that the links are not unidirectional.
3-27
Chapter 3 Bringing Up and Verifying FCCs
Detailed Steps
Command or Action
Step 1
Purpose Starts the FCCs.

Apply power to all FCCs.
Allow each FCC to fully boot. Verify that IOS XR RUN appears on the SC faceplates. Verify that the indicator LED on the OIM LED panel is green for each fabric cable connected to Rack 0. Each FCC loads any required software and configurations from the DSC, including the rack number and appropriate Cisco IOS XR software packages. Do not proceed until both SCGEs in each FCCs display IOS XR RUN. This indicates that each SCGE has successfully loaded the Cisco IOS XR software. In a properly operating system, the rack status for all racks should be Normal, and the server status should be Present.
Step 2
show controllers fabric rack all detail
Displays the status of all racks in the system.
Example:
RP/0/RP0/CPU0:router(admin)# show controllers fabric rack all detail
Step 3
show controllers fabric plane all detail
Displays the status of all racks and additional information for racks in installation mode.
Example:
RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all detail
Wait for the status in the Admin State and Oper State columns to change to UP for all planes.
3-28
Chapter 3
Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Verifying FCCs
Command or Action
Step 4
show controllers fabric connectivity all detail
Purpose Displays the LCC cards that can communicate with all eight fabric planes.
Example:
RP/0/RP0/CPU0:router(admin)# show controllers fabric connectivity all detail
The expected output should contain a series of 1s for each of the fabric planes active in the system. If a fabric plane is administratively shutdown the output of the command above remains the same. If the fabric card is physically removed or powered down, the 1 changes to .
Step 5
On the external Catalyst switches, verify that the links are not unidirectional.
Verifies that the links from the chassis to the external Catalyst switches are operating correctly.

If a unidirectional link is present, a loop may occur. For instructions to verify the Catalyst links, see the Verifying the Catalyst Switch section on page 3-19. The verification commands must be entered from a terminal directly connected to the external Catalyst switches, using Cisco IOS CLI commands.
Examples
This section contains an example for the following task:
Verify That All Fabric Planes Are Ready to Handle Data, page 3-29
Verify That All Fabric Planes Are Ready to Handle Data

In the following examples, the fabric planes are examined in administration EXEC mode to ensure that they are ready to handle traffic.
In the following example, the rack status is normal and the server status is present.
RP/0/RP0/CPU0:router(admin)# show controllers fabric rack all detail Rack Num ---Rack Status -----Server Status ------
0 NORMAL PRESENT 1 NORMAL PRESENT F0 NORMAL PRESENT RP/0/RP0/CPU0:router(admin)#
3-29
Chapter 3 Bringing Up and Verifying FCCs
In the following example, all eight planes are displayed, and the administrative and operational state of each plane is up.
RP/0/RP0/CPU0:CRS-8_P1(admin)# show controllers fabric plane all detail Flags: P C L A B I N o f m plane admin down, p card admin down, c link port admin down, l asic admin down, a bundle port admin Down, b bundle admin down, i node admin down, n other end of link down d failed component downstream plane multicast down plane oper down card oper down linkport oper down asic oper down bundle port oper down bundle oper down node down data down
Plane Admin Oper Down Total Down Id State State Flags Bundles Bundles -----------------------------------------------------0 UP UP 0 0 1 UP UP 0 0 2 UP UP 0 0 3 UP UP 0 0 4 UP UP 0 0 5 UP UP 0 0 6 UP UP 0 0 7 UP UP 0 0
The expected output should contain a series of 1s for each of the fabric planes active in the system. If a fabric plane is administratively shut down, the output of the command remains the same. If the fabric card is physically removed or powered down, the 1 changes to a dot (.).
RP/0/RP0/CPU0:CRS-8_P1(admin)# show controllers fabric connectivity all detail Flags: P C L A B I N o f m plane admin down, p - plane oper down - card admin down, c - card oper down - link port admin down, l - linkport oper down - asic admin down, a - asic oper down - bundle port admin Down, b - bundle port oper down - bundle admin down, i - bundle oper down - node admin down, n - node down - other end of link down d - data down - failed component downstream - plane multicast down
Card In Tx Planes Rx Planes Monitored Total Percent R/S/M Use 01234567 01234567 For (s) Uptime (s) Uptime ------------------------------------------------------------------------------0/1/CPU0 1 11111111 11111111 1245608 1245608 100.0000 0/6/CPU0 1 11111111 11111111 1245608 1245608 100.0000 0/RP0/CPU0 1 11111111 11111111 1245608 1245608 100.0000 0/RP1/CPU0 1 11111111 11111111 1245608 1245608 100.0000
3-30
Chapter 3
Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Verifying the Non-DSC LCC
Bringing Up and Verifying the Non-DSC LCC

When all FCCs are up and properly supporting Rack 0, it is time to bring up and configure the next LCC in the multishelf system as described in the following procedure:
Summary Steps
1. 2. 3. 4. 5. 6.
Apply power to the second LCC. show controllers fabric rack all detail show controllers fabric plane all detail show controllers fabric connectivity all detail On the external Catalyst switches, verify that the links are not unidirectional. exit
Detailed Steps
Command or Action
Step 1
Purpose Starts up the LCC.

Apply power to the second LCC.
Allow the chassis to fully boot. Verify that IOS XR RUN appears on the RP faceplates. In each FCC, verify that the indicator LED on the OIM LED panel is green for each fabric cable connected to the non-DSC LCC. The LCC loads any necessary software and configurations from the DSC, including the rack number and appropriate Cisco IOS XR software packages. Do not proceed until both RPs in the LCC display IOS XR RUN. This indicates that the RP has successfully loaded the Cisco IOS XR software. In a properly operating system, the rack status for all racks should be Normal, and the server status should be Present.
Step 2
Displays the status of all racks in the system.
Example:
RP/0/RP0/CPU0:router(admin)# show controllers fabric rack all detail
Step 3
Displays the status of all racks and additional information for racks in install mode.
Example:
RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all detail
Wait for the status in the Admin State and Oper State columns to change to UP for all planes.
3-31
Chapter 3 Verifying the Spanning Tree
Command or Action
Step 4
Purpose Displays the LCC cards that can communicate with all eight fabric planes.
Example:
RP/0/RP0/CPU0:router(admin)# show controllers fabric connectivity all detail
The expected output should contain a series of 1s for each of the fabric planes active in the system. If a fabric plane is administratively shutdown the output of the command above remains the same. If the fabric card is physically removed or powered down, the 1 changes to .
Step 5
On the external Catalyst switches, verify that the links are not unidirectional.
Verifies that the links from the chassis to the external Catalyst switches are operating correctly.

If a unidirectional link is present, a loop may occur. For instructions to verify the Catalyst links, see the Verifying the Catalyst Switch section on page 3-19. The verification commands must be entered from a terminal directly connected to the external Catalyst switches, using Cisco IOS CLI commands.
Step 6
exit
Exits administration EXEC mode and returns to EXEC mode.
Example:
RP/0/RP0/CPU0:router(admin)# exit RP/0/RP0/CPU0:router#
Verifying the Spanning Tree

When the both LCCs and all FCCs are up and running, it is time to verify the spanning tree on the control network as described in the following procedure.
Summary Steps
1. 2. 3.
admin show platform show spantree mst 1 detail location rack/slot/cpu0
3-32
Chapter 3
Bringing Up the Cisco IOS XR Software on a Multishelf System Verifying the Spanning Tree
Detailed Steps
Command or Action
Step 1
admin
Purpose Places the router in administration EXEC mode.
Example:
All commands listed in this procedure should be entered on the pre-existing single-chassis system.
Step 2
show platform
Displays the status of all hardware components.

Note
Example:
RP/0/RP0/CPU0:router(admin)# show platform
The state for all modules should be IOS XR RUN or OK. It can take a few minutes for all LCC modules to start up. To view the status of all cards and modules, the show platform command must be executed in administration EXEC mode.
3-33
Command or Action
Step 3
show spantree mst 1 detail location rack/slot/cpu0
Purpose Verifies the spanning tree.
Example:
RP/0/RP0/CPU0:router(admin)# location 0/rp0/cpu0 RP/0/RP0/CPU0:router(admin)# location 0/rp1/cpu0 RP/0/RP0/CPU0:router(admin)# location 1/rp0/cpu0 RP/0/RP0/CPU0:router(admin)# location 1/rp1/cpu0 RP/0/RP0/CPU0:router(admin)# location F0/SC0/cpu0 RP/0/RP0/CPU0:router(admin)# location F0/SC1/cpu0 show spantree mst 1 detail show spantree mst 1 detail show spantree mst 1 detail show spantree mst 1 detail show spantree mst 1 detail show spantree mst 1 detail
Enter this command for each RP and SCGE card in the system. The output for each RP and SCGE card should display the following:
In the Switched Interface column, one
GE port should be in the forwarding (FWD) state.

Each RP and SCGE card should
display the same designated root MAC address.
Verify that the designated root address matches the expected Catalyst switch, as defined by the Catalyst switch configuration. The root address should be the switch with the lowest priority number (0). For more information to configure and verify the external Catalyst switches, see the Verifying the Catalyst Switch section on page 3-19.
Examples

Verify That the FCCs and Non-DSC LCC Are Communicating with the DSC, page 3-35 Verify the Spanning Tree, page 3-36
3-34
Chapter 3
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)# show platform
Node Type PLIM State Config State ----------------------------------------------------------------------------0/3/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/3/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON 0/FC0/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/FC1/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/AM0/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/AM1/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM1/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM4/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM5/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM6/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM7/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/3/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/3/CPU0 MSC 8-10GbE IOS XR RUN PWR,NSHUT,MON 1/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 1/FC0/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/FC1/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/AM0/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/AM1/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM0/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM1/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM2/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM3/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM4/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM5/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM6/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM7/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON F0/SM0/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MON F0/SM3/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MON F0/SM6/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MON F0/SM9/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MON F0/SM12/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MON F0/SM15/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MON F0/SM18/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MON F0/SM21/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MON F0/SC0/CPU0 FCC-SC(Active) N/A IOS XR RUN PWR,NSHUT,MON F0/SC1/CPU0 FCC-SC(Standby) N/A PRESENT PWR,NSHUT,MON F0/AM1/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON RP/0/RP0/CPU0:router(admin)# end
3-35
Verify the Spanning Tree

For each RP and SCGE card in the system, verify that:

One GE port in the Switched Interface column is in the forwarding (FWD) state. Each RP and SCGE card displays the same designated root MAC address. The designated root address matches the expected Catalyst switch, as defined by the Catalyst switch configuration. The root address should be the switch with the lowest priority number (0).
The following EXEC commands display RP and SCGE card information that you can use to verify the spanning tree:
RP/0/RP0/CPU0:router(admin)# show spantree mst 1 detail location 0/rp0/cpu0 Instance Vlans mapped: 1 1
Designated Root 00-0e-39-fe-70-00 Designated Root Priority 1 (0 + 1) Designated Root Port GE_Port_0 Bridge ID MAC ADDR Bridge ID Priority Bridge Max Age 8 sec 00-05-9a-3e-89-4f 32769 (32768 + 1) Hello Time 1 sec
Forward Delay
6 sec
Max Hops 4
Switched Interface State Role Cost Prio Type -------------------- ----- ---- --------- ---- -------------------------------FE_Port_1 BLK altn 200000 128 P2P GE_Port_0 FWD root 20000 128 P2P GE_Port_1 BLK altn 20000 128 P2P
Designated Root 00-0e-39-fe-70-00 Designated Root Priority 1 (0 + 1) Designated Root Port GE_Port_0 Bridge ID MAC ADDR Bridge ID Priority Bridge Max Age 8 sec 00-05-9a-39-91-14 32769 (32768 + 1) Hello Time 1 sec
Forward Delay
6 sec
Max Hops 4
Switched Interface State Role Cost Prio Type -------------------- ----- ---- --------- ---- -------------------------------FE_Port_0 FWD desg 200000 128 P2P GE_Port_0 FWD root 20000 128 P2P GE_Port_1 BLK altn 20000 128 P2P
3-36
Chapter 3
Designated Root 00-0e-39-fe-70-00 Designated Root Priority 1 (0 + 1) Designated Root Port GE_Port_0 Bridge ID MAC ADDR Bridge ID Priority Bridge Max Age 8 sec 00-05-9a-3e-89-2a 32769 (32768 + 1) Hello Time 1 sec
Forward Delay
6 sec
Max Hops 4
Switched Interface State Role Cost Prio Type -------------------- ----- ---- --------- ---- -------------------------------FE_Port_1 FWD desg 200000 128 P2P GE_Port_0 FWD root 20000 128 P2P GE_Port_1 BLK altn 20000 128 P2P
Designated Root 00-0e-39-fe-70-00 Designated Root Priority 1 (0 + 1) Designated Root Port GE_Port_0 Bridge ID MAC ADDR Bridge ID Priority Bridge Max Age 8 sec 00-05-9a-3e-89-fe 32769 (32768 + 1) Hello Time 1 sec
Forward Delay
6 sec
Max Hops 4
Switched Interface State Role Cost Prio Type -------------------- ----- ---- --------- ---- -------------------------------FE_Port_0 BLK altn 200000 128 P2P GE_Port_0 FWD root 20000 128 P2P GE_Port_1 BLK altn 20000 128 P2P
RP/0/RP0/CPU0:router(admin)# show spantree mst 1 detail location F0/SC0/cpu0 Instance Vlans mapped: 1 1
Designated Root 00-0e-39-fe-70-00 Designated Root Priority 1 (0 + 1) Designated Root Port GE_Port_1 Bridge ID MAC ADDR Bridge ID Priority Bridge Max Age 8 sec 00-05-9a-39-91-be 32769 (32768 + 1) Hello Time 1 sec
Forward Delay
6 sec
Max Hops 4
Switched Interface State Role Cost Prio Type -------------------- ----- ---- --------- ---- -------------------------------FE_Port_1 BLK altn 200000 128 P2P GE_Port_0 BLK altn 20000 128 P2P GE_Port_1 FWD root 20000 128 P2P
3-37
Chapter 3 Verifying Fabric Cabling Connections
RP/0/RP0/CPU0:router(admin)# show spantree mst 1 detail location F0/SC1/cpu0 Instance Vlans mapped: 1 1
Designated Root 00-0e-39-fe-70-00 Designated Root Priority 1 (0 + 1) Designated Root Port GE_Port_1 Bridge ID MAC ADDR Bridge ID Priority Bridge Max Age 8 sec 00-05-9a-39-91-68 32769 (32768 + 1) Hello Time 1 sec
Forward Delay
6 sec
Max Hops 4
Switched Interface State Role Cost Prio Type -------------------- ----- ---- --------- ---- -------------------------------FE_Port_0 FWD desg 200000 128 P2P GE_Port_0 BLK altn 20000 128 P2P GE_Port_1 FWD root 20000 128 P2P
Verifying Fabric Cabling Connections

When the fabric cabling is complete and the power is on for all LCCs and FCCs, you can verify the fabric cabling connections, as described in this section. 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-4 describes the possible states of the LEDs shown in Figure 3-5.
Table 3-4 LED Status Interpretation
LED State and Color
Off
Meaning If the LED is off, it can mean: The board to which the fabric cable is connected is powered off at one end or the other
The board is not present
Green Yellow Red Blinking red Blinking green
The fabric cable is not connected at one end or the other. The fabric cable is properly connected at both ends, and data transmission is okay. The fabric cable is properly connected at both ends, but there are some data errors. The fabric cable is not connected to the correct place (when more than one fabric cable is incorrect). The fabric cable is not connected to the correct place (when the fabric cable is the only or first such fabric cable) The blinking LED indicates the place where the first and only incorrect fabric cable should be connected (corresponds to the blinking red above).
3-38
Chapter 3
Bringing Up the Cisco IOS XR Software on a Multishelf System Verifying Fabric Cabling Connections
Figure 3-5
Optical Interface Module LED Panel (Part CRS-FCC-LED)
8 9 10 11 7 6 5
4 1 2 3
J0
8 9 10 11 7 6 5
4 1 2 3
8 9 10 6 7 5
4 1 2 3
J1
8 9 10 11 7 6 5
4 1 2 3
J2
8 9 10 11 7 6 5
4 1 2 3
11
J3
J0
8 9 10 11 7 6 5
4 1 2 3
J4
8 9 10 11 7 6 5
4 1 2 3
J5
8 9 10 11 7 6 5
4 1 2 3
J6
8 9 10 11 7 6 5
4 1 2 3
J7
8 9 10 11 7 6 5
4 1 2 3
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.
129913
J8
3-39
Chapter 3 Verifying Fabric Cabling Connections
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
8 9 10 11 7 6 3 5 2 4 1
9 10 6 7 8 4 3 5 2 1
5 7
OIM11
11 12
OIM0
3 3
9 10 6 7 8
5 2 3 4
J0
J0
8
A0
8 9 10 11 7 6 5
4 1
11 12
9 10 11 7 8 6
5 2 3 4
J1
J1
A1
4
3
12
4
9 10 6 5 1
J2
J2
A2
138285
8 9 10 11 7 6 5
4 1 2 3
1 2
OIM LED card Solid green LEDIndicates that the fabric cable connected to the corresponding port (J0) is connected correctly.
6 7
S13 cardThis card is installed in an LCC. Correct fabric cable connection between FCC and LCC.
Flashing green LEDIndicates that a single fabric cable 8 is incorrectly connected and should be connected to the corresponding connector (J1). Flashing red LEDIndicates that a single fabric cable is 9 incorrectly connected to the corresponding connector (J2). OIM card
Incorrect fabric cable connection between FCC and LCC.
Fabric card chassis
3-40
Chapter 3
Bringing Up the Cisco IOS XR Software on a Multishelf System Where to Go Next
Where to Go Next
For information on configuring basic router features, see Chapter 4, Configuring General Router Features.
3-41
3-42
C H A P T E R
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-43 Where to Go Next, page 4-45
Secure Domain Routers

Cisco CRS-1 routers and Cisco XR 12000 Series Routers can be partitioned into multiple, independent routers known as secure domain routers (SDRs). Every router ships with a default SDR, which is called the owner SDR because it by default owns all RPs and line cards installed in the routing system. To build additional SDRs, you must create each SDR using configuration commands, name the SDR, assign RP, DRP, and line cards to the SDR, and then configure the interfaces on the line cards on the new SDR. An SDR is a group of cards within a router that is configured to operate as an independent router. SDRs that are created with configuration commands are called named SDRs and are configured with custom names to distinguish them from the owner SDR and other named SDRs.
4-1
Chapter 4 Connecting and Communicating with the Router
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 router s and Cisco XR 12000 Series Routers. For more information, see Cisco IOS XR System Management Configuration Guide.
Connecting and Communicating with the Router

To manage or configure a router running the Cisco IOS XR software, you must first connect to the router using a terminal or a PC. Before you connect to the router, you must determine which router entity you want to manage. You can manage the following router entities:

Owner SDR. Connect to the designated shelf controller (DSC). Router or multishelf system hardware. Connect to the DSC. Named SDR. For Cisco CRS-1 routers, connect to the RP or DRP that serves as the designated SDR system controller (DSDRSC) for that named SDR. For Cisco XR 12000 Series Routers, connect to the RP that serves as the DSDRSC for that named SDR.
Connections are made either through a direct physical connection to the Console port of the DSC or DSDRSC or from a remote location using a modem or an Ethernet connection that leads to the DSC or DSDRSC.

Figure 4-1 shows the RP connections on the Cisco CRS-1 16-Slot Line Card Chassis, and Figure 4-2 shows the RP connections on the Cisco CRS-1 8-Slot Line Card Chassis. Figure 4-3 shows the DRP PLIM connections. Figure 4-4 shows the performance route processor 2 (PRP-2) connections for a Cisco XR 12000 Series Router.
4-2
Chapter 4
Configuring General Router Features Connecting and Communicating with the Router
Figure 4-1
Communication Ports on the RP for a Cisco CRS-1 16-Slot Line Card Chassis
RP
RJ-45 cable
Console AUX
RJ-45 cable
HDD
Remote terminal for CLI communication
PC Card (disk1:)
CNTL ETH 0
Network Remote CLI, CWI, XML, or SNMP communication
Management Ethernet connection for out-of-band network communciation
CNTL ETH 1 MGMT ETH
Optical Gigabit Ethernet for control plane: (not user configurable)
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.
116547
Primary
4-3
Figure 4-2
Communication Ports on the RP for a Cisco CRS-1 8-Slot Line Card Chassis RJ-45 cable
Console AUX
Terminal connection Modem connection
RJ-45 cable
ALARM PID/VID
Remote terminal for CLI communication Ethernet cable
CRITICAL MAJOR MINOR
MGMT ETH CNTL ETH 0 CNTL ETH 1
Management Ethernet connection for out-of-band network communication Optical Gigabit Ethernet for control plane: (not user configurable)
PC CARD
EXT CLK 1 EXT CLK 2
Primary Status
LED status displays (alphanumeric) Primary RP (on=primary) Card status (green=OK)
4-4
149693
Chapter 4
Figure 4-3 Communication Ports on the DRP PLIM CPU0 AUX connection
CPU0 Console connection
RJ-45 cable Local terminal or terminal server for CLI communication

CLEAN
CONNECTOR WITH ALCOHOL WIPES BEFORE CONNECTING
B1
AUX 0 AUX 1
CLASS 1 LASER PRODUCT LASERPRODUKT DER KLASSE 1 PRODUIT LASER DE CLASSE 1 1 PRODUCTO LASER CLASE 1
RJ-45 cable
PIDVID
MGMT ETH 0 MGMT ETH 1
CPU1 AUX connection Network Management Ethernet connections for out-of-band network communication
CPU0 Ethernet CPU1 Ethernet CPU1 Console connection
Remote CLI, CWI, XML, or SNMP communication
CLEI
138093
FDA
SN
CRS-DRP-ACC
Y AR US IM AT PR ST
4-5
Figure 4-4
Communication Ports on the PRP-2 for a Cisco XR 12000 Series Router
-1 OT SL 0 OT SL
Ethernet cable
ETH 0 ETH 1 BITS 0 BITS 1 AUX
Management Ethernet connection for out-of-band network communication
K LIN TA DA K LIN TA DA G SI T AC G SI T AC

ETH 2 CONSOLE
Modem connection Terminal connection
The following sections describe three ways to connect to a DSC or DSDRSC:

Establishing a Connection Through the Console Port, page 4-7 Establishing a Connection Through a Terminal Server, page 4-8 Establishing a Connection Through the Management Ethernet Interface, page 4-10
4-6
149695
PERFORMANCE ROUTE PROCESSOR 2
RE SE T
LED status displays (alphanumeric)
Chapter 4
Establishing a Connection Through the Console Port

To connect to the router through the console port, perform the following procedure.
SUMMARY STEPS
1. 2. 3. 4. 5.
Identify the active RP or DRP. Connect a terminal to the Console port of the active RP or DRP. Start the terminal emulation program. Press Enter. Log in to the router.
DETAILED STEPS
Command or Action
Step 1
Purpose Identifies the RP or DRP to which you must connect in the next step.

Identify the active RP or DRP.
This step is not required when the router hosts only one RP. On a Cisco CRS-1 router, the active RP or DRP is identified by a lighted Primary LED on the RP front panel. On a Cisco XR 12000 Series Router, the active RP is identified by the alphanumeric display: PRI RP.
Step 2
Connect a terminal to the Console port of the active RP Establishes a communications path to the router. or DRP. During the initial setup, you can communicate with the router only through the Console port of the active RP.
The router Console port is designed for a serial cable connection to a terminal or a computer that is running a terminal emulation program. The terminal settings are:
For information on the cable requirements for the Console port, see the hardware documentation listed in the Related Documents section on page xiv.
4-7
Command or Action
Step 3
Purpose (Optional) Prepares a computer for router communications.

Start the terminal emulation program.
The step is not required if you are connecting through a terminal. Terminals send keystrokes to and receive characters from another device. If you connect a computer to the Console port, you must use a terminal emulation program to communicate with the router. For instructions on using the terminal emulation program, see the documentation for that program. If no text or router prompt appears when you connect to the Console port, press Enter to initiate communications. If no text appears when you press Enter and the router has been started recently, give the router more time to complete the initial boot procedure, then press Enter. If the router has no configuration, the router displays the prompt: Enter root-system username:. If a standalone router is starting up for the first time, see Chapter 2, Bringing Up the Cisco IOS XR Software on a Standalone Router. If a multishelf system is starting up for the first time, see Chapter 3, Bringing Up the Cisco IOS XR Software on a Multishelf System. If the router has been configured, the router displays the prompt: Username:
Step 4
Press Enter.
Initiates communication with the router.
Step 5
Enter your username and password, as described in the Logging In to a Router or an SDR section on page 4-11. After you log in, the router displays the CLI prompt, which is described in the CLI Prompt section on page 4-12.
Establishing a Connection Through a Terminal Server

A terminal server connection provides a way to access the Console port from a remote location. It is less expensive to connect to the router through the Management Ethernet interface (because you do not have the additional cost of a terminal server). However, if you need to perform tasks that require Console port access from a remote location, a terminal server is the best connection method. The procedure for connecting to the router through a terminal server is similar to the procedure for directly connecting through the Console port. For both connection types, the physical connection takes place through the Console port. The difference is that the terminal server connects directly to the Console port, and you must use a Telnet session to establish communications through the terminal server to the router.
4-8
Chapter 4
To establish a connection through a terminal server, perform the following procedure:
SUMMARY STEPS
1. 2. 3. 4. 5. 6. 7.
Install and configure the terminal server. Connect the terminal server to the Console port of the target RP or DRP. Power on the router. Identify the target RP or DRP. telnet access-server-address port Press Enter. Log in to the router.
DETAILED STEPS
Command or Action
Step 1
Purpose Prepares the terminal server for communications with the router and with Telnet clients.

Install and configure the terminal server.
This step is usually preformed once. For router access, users need the Telnet server IP address and port number for each RP they access. For additional information on configuring terminal services, including terminal servers and templates, see the Cisco IOS XR System Management Configuration Guide.
Step 2
Connect the terminal server to the Console port of the Establishes a communications path between the terminal target RP or DRP. server and the router.
During the initial router setup, you can communicate with the router only through the Console port of the primary RP. The router Console port is designed for a serial cable connection to a terminal or terminal server. The terminal settings are:
For information on the cable requirements for the Console port, see the hardware documentation listed in the Related Documents section on page xiv. To enable terminal server connections to the Console ports on multiple RPs and DRPs, install a cable between each Console port and the terminal server.
4-9
Command or Action
Step 3
Purpose Starts the router.

Power on the router.
This step is required only if the router power is not on. For information on power installation and controls, see the hardware documentation listed in the Related Documents section on page xiv.
Step 4
Identify the target RP or DRP.
Identifies the RP or DRP to which you connect in the next step.

This step is not required when the router hosts only one RP or DRP. On a Cisco CRS-1 router, the active RP or DRP is identified by a lighted Primary LED on the RP front panel. On a Cisco XR 12000 Series Router, the active RP is identified by the alphanumeric display: PRI RP. If you cannot look at the RPs, use a Management Ethernet interface connection to determine which RP is active, or establish terminal server connections to both RPs and then try both. Replace access-server-address with the IP address of the terminal server, and replace port with the terminal server port number that connects to the target RP Console port. If no text or router prompt appears when you start the Telnet session, press Enter to initiate communications. If the router has no configuration, the router displays the prompt: Enter root-system username: Enter the root-system username and password when prompted. If the router has been configured, the router displays the prompt: Username:
Step 5
telnet access-server-address port
Establishes a Telnet session with the terminal server.
Step 6
Press Enter.
(Optional) Initiates communications with the RP or DRP.

Step 7
Enter a username and password when prompted.
Establishing a Connection Through the Management Ethernet Interface

The Management Ethernet interface allows you to manage the router using a network connection. Before you can use the Management Ethernet interface, the interface must be configured, as described in the Configuring the Management Ethernet Interface section on page 4-41.
4-10
Chapter 4
Configuring General Router Features Logging In to a Router or an SDR
Once configured, the network connection takes place between client software on a workstation computer and a server process within the router. The type of client software you use depends on the server process you want to use. The Cisco IOS XR software supports the following client and server services:
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.
Logging In to a Router or an SDR

The login process can require users to enter a password or a username and password before accessing the router CLI. The user groups to which your username is assigned determine which commands you can use. If you log in to a router with a single SDR configured (this is the default configuration), you can manage the entire router. If you log in to the owner SDR on a system with multiple SDRs, you can manage general features that apply to the entire system and the interfaces assigned to the owner SDR. If you log in to a named SDR, you can manage only that SDR. For more information on SDRs, see the Secure Domain Routers section on page 4-1. When you log in, the username and password may be validated by any of the following services:

Usernames configured on the router (username command in global configuration mode) Root-system usernames configured on the owner SDR Passwords configured for the router console and auxiliary ports (password or secret command in line configuration mode) A RADIUS server A TACACS+ server
The username and password validation method that your router uses is determined by the router configuration. For information on configuring username and password validation methods, see the Cisco IOS XR System Security Configuration Guide. For information on which username and password to use, see your system administrator.
4-11
Chapter 4 CLI Prompt
To log in to the router, enter your username and password when prompted. For example:
User Access Verification 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. 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.
Table 4-1 CLI Prompt Description
Prompt Syntax Components type rack
Description Type of interface or card with which you are communicating. For most user communication tasks, the type is RP. Rack number. In a standalone router, the rack number is always 0. In a multishelf system, the range for LCC rack numbers is 0 to 255, and the range for FCC rack numbers is F0 to F7. Slot in which the RP or DRP is installed. In a Cisco CRS-1 router, the RP physical slot number is RP0 or RP1. In a Cisco XR 12000 Series Router, the physical slot number can be 0 to 15, and there can be multiple SDRs, each of which is represented by an RP. Entity on a card that executes user commands or communicates with a port (interface). For executing commands from the EXEC prompt, the module is the CPU0 of the RP. CPU0 also controls the forwarding and operating system (OS) functions for the system. DRPs have two processors: CPU0 and CPU1. Hostname of the router or SDR. The hostname is usually defined during initial configuration of the router, as described in the Configuring the SDR Hostname section on page 4-38.
slot
module
router-name
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#
4-12
Chapter 4
Configuring General Router Features User Access Privileges
User Access Privileges

When you log in to the router, your username and password are used to determine if you are authorized to access the router. After you successfully log in, your username is used to determine which commands you are allowed to use. The following sections provide information on how the router determines which commands you can use:

User Groups, Task Groups, and Task IDs, page 4-13 Predefined User Groups, page 4-14 Displaying the User Groups and Task IDs for Your User Account, page 4-14
User Groups, Task Groups, and Task IDs

The commands that each user can use are defined by the user groups to which he or she belongs. Within the Cisco IOS XR software, the commands for a particular feature, such as access control lists, are assigned to tasks, which are uniquely identified by task IDs. If a user wants to use a particular command, his or her username must be associated with the appropriate task ID. The association between a username and a task ID takes place through two intermediate entities, the user group and task group. The user group is basically a logical container that can be used to assign the same task IDs to multiple users. Instead of assigning task IDs to each user, you can assign them to the user group, and then assign users to the user group. When a task is assigned to a user group, you can define the access rights for the commands associated with that task. These rights include read, write, execute, and notify. The task group is also a logical container, but it is used to group tasks. Instead of assigning task IDs to each user group, you assign them to a task group, which allows you to quickly enable access to a specific set of tasks by assigning a task group to a user group. To summarize the associations, usernames are assigned to user groups, which are then assigned to task groups. Users can be assigned to multiple user groups, and each user group can be assigned to one or more task groups. The commands that a user can execute are all those commands assigned to the tasks within the task groups that are associated with the user groups to which the user belongs. Users are not assigned to groups by default and must be explicitly assigned by an administrator. You can display all task IDs available on the system with the show task supported command. For example:
RP/0/RP0/CPU0:router# show task supported bgp ospf hsrp isis route-map route-policy static vrrp cef lpts iep rib multicast mpls-te mpls-ldp mpls-static ouni
4-13
Chapter 4 User Access Privileges
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).)
Predefined User Groups

The Cisco IOS XR software includes a set of predefined user groups that meets the needs of most organizations. The predefined user groups are described in Table 4-2.
Table 4-2 Predefined User Group Descriptions
User Group root-system root-lr sysadmin
Privileges Display and execute all commands for all SDRs in the system. Display and execute all commands within a single SDR. Perform system administration tasks for the router, such as maintaining where the core dumps are stored or setting up the Network Time Protocol (NTP) clock. Configure network protocols, such as Border Gateway Protocol (BGP) and Open Shortest Path First (OSPF) (usually used by network administrators). Perform day-to-day monitoring activities, and have limited configuration rights. Debug and troubleshoot features (usually used by Cisco support personnel).
netadmin
operator cisco-support
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.
Table 4-3 Options to Display Information About Your Account
Command show user show user group
Description Displays your user name. Displays the user groups assigned to your account.
4-14
Chapter 4
Configuring General Router Features User Access Privileges
Table 4-3
Options to Display Information About Your Account (continued)
Command show user tasks show user all show aaa usergroup group-name
Description Displays the task IDs assigned to your account. Displays all user groups and task ID information for your account. Displays the task IDs assigned to a user group.
Examples
To display your username, enter the show user command:
RP/0/RP0/CPU0:CRS-8_P1# 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:CRS-8_P1# show user tasks Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: aaa acl admin atm basic-services bcdl bfd bgp boot bundle cdp cef config-mgmt config-services crypto diag drivers eigrp ext-access fabric fault-mgr filesystem firewall fr hdlc host-services hsrp interface inventory ip-services ipv4 ipv6 isis logging lpts monitor mpls-ldp mpls-static mpls-te : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG
4-15
Chapter 4 User Access Privileges
Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task:
multicast netflow network ospf ouni pkg-mgmt pos-dpt ppp qos rib rip root-lr root-system route-map route-policy sbc snmp sonet-sdh static sysmgr system transport tty-access tunnel universal vlan vrrp
: : : : : : : : : : : : : : : : : : : : : : : : : : :
READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ
WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE
EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE
DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG (reserved) DEBUG (reserved) DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG (reserved) DEBUG DEBUG
To display the user groups assigned to your user account, enter the show user group command:
RP/0/RP0/CPU0:CRS-8_P1# 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:CRS-8_P1# show aaa usergroup root-system User group 'root-system' Inherits from task group 'root-system' User group 'root-system' has the following combined set of task IDs (including all inherited groups): Task: aaa : READ WRITE EXECUTE Task: acl : READ WRITE EXECUTE Task: admin : READ WRITE EXECUTE Task: atm : READ WRITE EXECUTE Task: basic-services : READ WRITE EXECUTE Task: bcdl : READ WRITE EXECUTE Task: bfd : READ WRITE EXECUTE Task: bgp : READ WRITE EXECUTE Task: boot : READ WRITE EXECUTE Task: bundle : READ WRITE EXECUTE Task: cdp : READ WRITE EXECUTE Task: cef : READ WRITE EXECUTE Task: config-mgmt : READ WRITE EXECUTE Task: config-services : READ WRITE EXECUTE Task: crypto : READ WRITE EXECUTE Task: diag : READ WRITE EXECUTE Task: drivers : READ WRITE EXECUTE Task: eigrp : READ WRITE EXECUTE Task: ext-access : READ WRITE EXECUTE Task: fabric : READ WRITE EXECUTE Task: fault-mgr : READ WRITE EXECUTE
DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG
4-16
Chapter 4
Configuring General Router Features Navigating the Cisco IOS XR Command Modes
Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task: Task:
filesystem firewall fr hdlc host-services hsrp interface inventory ip-services ipv4 ipv6 isis logging lpts monitor mpls-ldp mpls-static mpls-te multicast netflow network ospf ouni pkg-mgmt pos-dpt ppp qos rib rip root-lr root-system route-map route-policy sbc snmp sonet-sdh static sysmgr system transport tty-access tunnel universal vlan vrrp
: : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : :
READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ READ
WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE
EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE EXECUTE
DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG (reserved) DEBUG (reserved) DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG (reserved) DEBUG DEBUG
Navigating the Cisco IOS XR Command Modes

The CLI for the Cisco IOS XR software is divided into different command modes. Each mode provides access to a subset of commands used to configure, monitor, and manage the router. Access to a mode is determined by your user group assignments. The following sections describe the navigation of the command modes:

Identifying the Command Mode in the CLI Prompt, page 4-18 Summary of Common Command Modes, page 4-19 Entering EXEC Commands from a Configuration Mode, page 4-21 Command Mode Navigation Example, page 4-22
4-17
Chapter 4 Navigating the Cisco IOS XR Command Modes
Figure 4-5 illustrates the basic command mode navigation for the CLI. Only a small sample of the possible configuration submodes is shown.
Figure 4-5 Example of Command Mode Navigation in Cisco IOS XR software
Login
EXEC mode
Administration EXEC mode
Administration configuration mode
Global configuration mode Configuration submode examples Interface configuration submode Router configuration submode Line template configuration submode
149947
Logical router configuration submode
Task group configuration submode
Identifying the Command Mode in the CLI Prompt

The command mode is identified in the CLI prompt after the router name. For example, when the router enters global configuration mode from the EXEC mode, the CLI prompt changes to include (config) after the router name:
RP/0/RP0/CPU0:router# configure 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)#
4-18
Chapter 4
Summary of Common Command Modes

Table 4-4 summarizes the most common command modes of the Cisco IOS XR software and the associated CLI prompts.
Table 4-4 Common Command Modes and CLI prompts
Command Mode EXEC
Description Logging in to an SDR running the Cisco IOS XR software automatically places the router in EXEC mode. Example:
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 configuration mode
Administration configuration mode allows you to create SDRs and assign system resources to 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)#
4-19
Table 4-4
Common Command Modes and CLI prompts (continued)
Command Mode Global configuration
Description Global configuration mode is the starting point for SDR configuration. Commands entered in this mode affect the SDR as a whole, rather than just one protocol or interface. Global configuration mode is also used for entering configuration submodes to configure specific elements, such as interfaces or protocols. To enter global configuration mode, enter the configure command at the EXEC command prompt:
Note
The system prompt changes to router(config) to indicate that the router is now in global configuration mode.
Configuration submodes
From the global configuration mode, you can also enter other, more specific command modes. 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:
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)#
4-20
Chapter 4
Table 4-4
Common Command Modes and CLI prompts (continued)
Command Mode Router submode configuration
Description Router configuration submodes are accessed from router configuration mode. The following command syntax is used for entering router address family configuration submode:
RP/0/RP0/CPU0:router(config)# router bgp 140 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 multicast RP/0/RP0/CPU0:router(config-bgp-af)#
For more information, see the following Cisco Systems documents:

Cisco IOS XR Routing Configuration Guide Cisco IOS XR Routing Command Reference
ROM Monitor (ROMMON) mode
The 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 prompt for the mode.
rommon B1>
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.
Entering EXEC Commands from a Configuration Mode

EXEC commands can be executed from any configuration mode by preceding the command with the do keyword. Executing EXEC commands from a configuration mode allows you to display the state of the system without exiting the configuration mode. For example:
RP/0/RP0/CPU0:router(config)# do show version Cisco IOS-XR Software, Version 1.0.0 Copyright (c) 2004 by cisco Systems, Inc. ROM: System Bootstrap, Version 1.15(20040120:002852) [ROMMON], router uptime is 1 hour, 40 minutes 1000592k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes). Configuration register is 0x2 --More--
4-21
Command Mode Navigation Example

The following steps provide an example of command mode navigation:
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
Press RETURN to get started.
User Access Verification 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 ? aaa adjacency aliases aps arm arp as-path-access-list asic-errors auto-rp bgp buffer-manager calendar cdp cef cetftp checkpoint cinetd clns clock commit community-list configuration --More-Show AAA configuration and operational data Adjacency information Display alias commands SONET APS information IP ARM information ARP table List AS path access lists ASIC error information Auto-RP Commands BGP show commands Show all buffer manager memory related information Display the system calendar CDP information Cisco Express Forwarding CRS-1 control plane ethernet TFTP server Show checkpoint services Cisco inetd services Display CLNS related information Display the system clock Show commit information List community-list Contents of Non-Volatile memory
Note Step 3
The commands available to you depend on the router mode and your user group assignments.
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:
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.
4-22
Chapter 4
Configuring General Router Features Managing Configuration Sessions
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.
The command mode prompt changes from (config) to configuration commands for the specified interface.
Step 5
(config-if)
and you can now enter
To exit interface configuration mode and return to global configuration mode, enter the exit command. To return to EXEC mode, enter the end command.
Managing Configuration Sessions

In the Cisco IOS XR software, the running (active) configuration can never be altered directly. All configuration changes are entered into an inactive target configuration. When the target configuration is ready for use, you can apply that configuration to the router with the commit command. This two-stage process allows configuration changes to be made, edited, and verified before the actual running state of the router is impacted. Figure 4-6 illustrates the two-stage configuration process.
Figure 4-6 Two-Stage Configuration Process
EXEC mode
Global configuration mode Stage 1: Enter configuration changes or load a saved configuration. Stage 2: "Commit" changes to the running configuration.
Administration mode
Administration configuration 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-24 Starting an Exclusive Configuration Session, page 4-25 Displaying Configuration Details with show Commands, page 4-26 Saving the Target Configuration to a File, page 4-32 Loading the Target Configuration from a File, page 4-33
4-23
Chapter 4 Managing Configuration Sessions
Loading an Alternative Configuration at System Startup, page 4-33 Clearing All Changes to a Target Configuration, page 4-33 Committing Changes to the Running Configuration, page 4-34 Reloading a Failed Configuration, page 4-36 Exiting a Configuration Submode, page 4-37 Ending a Configuration Session, page 4-37 Aborting a Configuration Session, page 4-38
Displaying the Active Configuration Sessions

Before you start a configuration session, you might want to check to see if there are other configuration sessions in progress. More than one user can open a target configuration session at a time, allowing multiple users to work on separate target configurations. The procedure for viewing the active configuration sessions depends on the type of configuration session. For administration configuration sessions, which assign hardware components in SDRs and multishelf systems, you must be in administration EXEC mode to view the active administration configuration sessions. For SDR configuration sessions, you must be in EXEC mode to view the active SDR configuration sessions. To view the active administration configuration sessions, connect to the DSC and enter the show configuration sessions command in administration EXEC mode, as shown in the following example:
RP/0/RP0/CPU0:CRS-8_P1# admin RP/0/RP0/CPU0:CRS-8_P1(admin)# show configuration sessions Session 00000201-002180dd-00000000 Line vty0 User cisco Date Thu Mar 16 14:47:08 2006 Lock
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 Session 00000201-002180dd-00000000 00000201-001b307a-00000000 Line vty0 vty2 User test cisco Date Thu Mar 16 13:16:17 2006 Thu Mar 16 13:16:17 2006 Lock *
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-25.
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.
Starting a Configuration Session

When you place the router in global configuration mode or administration configuration mode using the configure command, a new target configuration session is created. The target configuration allows you to enter, review, and verify configuration changes without impacting the running configuration.
4-24
Chapter 4
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-32.
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:CRS-8_P1# admin RP/0/RP0/CPU0:CRS-8_P1(admin)# configure RP/0/RP0/CPU0:CRS-8_P1(admin-config)# sdr test RP/0/RP0/CPU0:CRS-8_P1(admin-config-sdr:test)# location 0/1/SP RP/0/RP0/CPU0:CRS-8_P1(admin-config-sdr:test)# show configuration Building configuration... sdr test location 0/1/SP ! end
Starting an Exclusive Configuration Session

An exclusive configuration session allows you to configure the administration configuration or an SDR and lock out all users from committing configuration changes until you are done. Other users can still create and modify a target configuration, but they cannot commit those changes to the running configuration until you exit your exclusive configuration session.
4-25
During regular configuration sessions, the running configuration is locked whenever a commit operation is being performed. This automatic locking ensures that each commit operation is completed before the next one begins. Other users receive an error message if they attempt to commit a target configuration while another commit operation is under way. To start an exclusive configuration session for an SDR, connect to that SDR and enter the configure exclusive command:
RP/0/RP0/CPU0:router# configure exclusive 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.
Displaying Configuration Details with show Commands

The following sections describe the following tasks:

Displaying the Running Configuration, page 4-26 Displaying a Sanitized Version of the Running Configuration, page 4-28 Displaying the Target Configuration, page 4-30 Displaying a Combined Target and Running Configuration, page 4-31 Displaying Configuration Error Messages and Descriptions, page 4-31 Displaying Configuration Error Messages Without Descriptions, page 4-32 Displaying Configuration Error Messages Produced While Loading a Configuration, page 4-32
Displaying the Running Configuration

The running configuration is the committed configuration that defines the router operations, and it is divided into the administration configuration and an SDR configuration for each SDR. The portion of the running configuration that you can view depends on the current CLI mode and SDR connection. 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.
4-26
Chapter 4
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 !
4-27
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:CRS-8_P1(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
Displaying a Sanitized Version of the Running Configuration

A sanitized running configuration report displays the contents of the running configuration without installation specific parameters. Some configuration details, such as IP addresses, are replaced with different addresses. The sanitized configuration can be used to share a configuration without exposing the configuration details. In EXEC and global configuration mode, you can view the sanitized 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 sanitized administration configuration, which includes hardware assignments for SDRs and multishelf systems. To display the sanitized SDR portion of the running configuration, enter the show running-config sanitized command in EXEC or global configuration mode, as shown in the following example:
RP/0/RP1/CPU0:router(config)# show running-config sanitized 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>
4-28
Chapter 4
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
4-29
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:CRS-8_P1(admin)# show running-config sanitized Building configuration... sdr <removed> location 0/1/* primary ! username <removed> secret 5 <removed> group root-system ! end
Displaying the Target Configuration

The target configuration includes the configuration changes that have been entered but not yet committed. These changes are not yet part of the running configuration. You can view the target configuration in global configuration and administration configuration modes. You cannot view the target configuration in EXEC modes because the target configuration must be committed or abandoned before returning to EXEC or administration EXEC mode. To display the target configuration changes you have entered for an SDR, enter the show configuration command in global configuration mode or in any submode, as shown in the following example:
RP/0/RP0/CPU0:router(config-if)# show configuration 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:CRS-8_P1(admin-config-sdr:test)# show configuration Building configuration... sdr test location 0/1/* primary ! end
4-30
Chapter 4
Displaying a Combined Target and Running Configuration

Although the target and running configurations remain separate until the target configuration is committed, you can preview the combined target and running configuration without committing the changes. The combined configuration shows what the new running configuration will look like after the changes from the target configuration are committed. It does not represent the actual running configuration. You can preview the combined configuration in global configuration and administration configuration modes. You cannot preview the combined configuration in EXEC modes because the target configuration must be committed or abandoned before returning to EXEC or administration EXEC mode. To display the combined target and running configuration, enter the show configuration merge command in any configuration mode.
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 RP/0/RP0/CPU0:router(config-if)# show configuration merge Building configuration... !! Last configuration change at 16:52:49 UTC Sun March 10 2004 by cisco ! hostname router interface POS0/3/0/3 description faq ipv4 address 10.1.1.1 255.0.0.0 shutdown end
Displaying Configuration Error Messages and Descriptions

Configuration changes are automatically verified during the commit operation, and a message is displayed if one or more configuration entries fail. To display an error message and description for a failed configuration, enter the show configuration failed command.
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.
4-31
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 RP/0/RP0/CPU0:router(config-tg)# show configuration failed !! CONFIGURATION FAILED DUE TO SEMANTIC ERRORS taskgroup bgp !!% Usergroup/Taskgroup names cannot be taskid names !
Displaying Configuration Error Messages Without Descriptions

Configuration changes are automatically verified during the commit operation, and a message is displayed if one or more configuration entries fail. To display only the error message (without a description) for a failed configuration, enter the show configuration failed noerror command, as shown in the following example:
RP/0/RP0/CPU0:router(config-tg)# show configuration failed noerror !! CONFIGURATION FAILED DUE TO SEMANTIC ERRORS taskgroup bgp !
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.
Displaying Configuration Error Messages Produced While Loading a Configuration

To display any syntax errors found in a configuration loaded with the load command, enter the show configuration failed load command.
Saving the Target Configuration to a File

Target configurations can be saved to a separate file without committing them to the running configuration. Target configuration files can then be loaded at a later time and further modified or committed. To save the configuration changes in the target configuration to a file, enter the save configuration device: command. Replace the device argument with the name of the device on which you want to store the file (for example, disk0). After you enter this command, the router prompts you to enter a filename. If you enter only a filename, the file is stored in the root directory of the device. To store the file in a
4-32
Chapter 4
directory, enter the directory path and filename when prompted. We recommend that you specify the cfg file extension for easy identification. This suffix is not required, but it can help locate target configuration files. Example: myconfig.cfg In the following example, a target configuration file is saved to the usr/cisco directory of disk0:
RP/0/RP1/CPU0:CRS-8_P1(admin-config)# save configuration disk0: Destination file name (control-c to abort): [/running-config]?/usr/cisco/test.cfg Building configuration. 1 lines built in 1 second [OK]
Note
You can also save a configuration to a file using the show configuration | file filename command.
Loading the Target Configuration from a File

To populate the target configuration with the contents of a previously saved configuration file, go to global configuration or administration configuration mode and Enter the load filename command. Consider the following when entering the filename argument:

The filename argument specifies the configuration file to be loaded into the target configuration. If the full path of the file is not specified, the router attempts to load the file from the root directory on the device.
In the following example, a target configuration file is loaded into the current configuration session. The current configuration session is therefore populated with the contents of the file:
RP/0/RP1/CPU0:CRS-8_P1(config)# load disk0:/usr/cisco/test.cfg Loading. 77 bytes parsed in 1 sec (76)bytes/sec
Loading an Alternative Configuration at System Startup

When a router is reset or powered on, the last running configuration is loaded and used to operate the router. You can load an alternative configuration during system boot. See Cisco IOS XR ROM Monitor Guide for information and instructions on this process.
Clearing All Changes to a Target Configuration

To clear changes made to the target configuration without terminating the configuration session, enter the clear command in global configuration mode or administration configuration mode. This command deletes any configuration changes that have not been committed.
4-33
In the following example, the user configures an interface but does not commit it. After reviewing the changes to the target configuration with the show configuration command, the user decides to remove the changes and start over by entering the clear command:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# interface POS 0/3/0/1 RP/0/RP0/CPU0:router(config-if)# description this is my interface RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.1.1.1 255.0.0.0 RP/0/RP0/CPU0:router(config-if)# shutdown RP/0/RP0/CPU0:router(config-if)# exit RP/0/RP0/CPU0:router(config)# show configuration 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
Committing Changes to the Running Configuration

The changes in the target configuration do not become part of the running configuration until you enter the commit command. When you commit a target configuration, you can use the commit command to do either of the following:

Merge the target configuration with the running configuration to create a new running configuration. Replace the running configuration with the target configuration.
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.
Table 4-5 Commit Command Options
Command commit
Description (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. 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 best-effort
4-34
Chapter 4
Table 4-5
Commit Command Options (continued)
Command commit comment line
Description (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 seconds
(Optional) Commits the configuration in global configuration mode on a 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.
4-35
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 RP/0/0/0:Aug 6 09:26:17.781 : %LIBTARCFG-6-COMMIT Configuration committed by user cisco'. Use 'show configuration commit changes 1000000124' to view the changes.
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:CRS-8_P1# admin RP/0/RP0/CPU0:CRS-8_P1(admin)# configure RP/0/RP0/CPU0:CRS-8_P1(admin-config)# sdr test RP/0/RP0/CPU0:CRS-8_P1(admin-config-sdr:test)# location 0/1/* primary RP/0/RP0/CPU0:CRS-8_P1(admin-config-sdr:test)# commit label test comment This is a test RP/0/RP0/CPU0:CRS-8_P1(admin-config)# show configuration commit list detail 1) CommitId: 2000000018 UserId: jbowman Client: CLI Comment: This is a test . . . Label: test Line: vty1 Time: 23:45:40 UTC Tue Mar 07 2006
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.
Reloading a Failed Configuration

If the router displays a configuration failure message when you attempt to commit a configuration change, the configuration changes are not lost. While you remain in global configuration mode or administration configuration mode, you can load the configuration changes into the target configuration, correct the errors, and commit the changes. To load a failed configuration, go to global configuration or administration configuration mode and enter the load configuration failed commit command, as shown in the following example:
RP/0/0/CPU0:router(config)# load configuration failed commit RP/0/0/CPU0:router(config)# show configuration Building configuration... taskgroup bgp ! end
4-36
Chapter 4
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.
Exiting a Configuration Submode

When you have finished configuration changes in a configuration submode, such as the interface or SDR configuration submodes, you can return to return to the previous configuration mode and continue making configuration changes. To exit a configuration submode, enter the exit command, as shown in the following example:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# interface POS 0/3/0/1 RP/0/RP0/CPU0:router(config-if)# description this is my interface RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.1.1.1 255.0.0.0 RP/0/RP0/CPU0:router(config-if)# exit RP/0/RP0/CPU0:router(config)#
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.
Ending a Configuration Session

You can use any of the following methods to end a configuration session:

Enter the exit command in global configuration or administration configuration mode. Enter the end command in any configuration mode or submode Press Ctrl-Z.
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:CRS-8_P1(config-if)# end Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]:
4-37
Chapter 4 Configuring the SDR Hostname
Respond to the prompt by entering one of the following options:

yes, commit the configuration changes and exit configuration mode no, exit configuration mode without committing the configuration changes cancel, remain in configuration mode without committing the configuration changes
Note
In EXEC mode, the exit command logs the user out of the system.
Aborting a Configuration Session

When you abort a configuration session, any changes are discarded and the configuration session ends. No warning is given before the configuration changes are deleted. In global configuration mode, the abort command discards configuration changes and returns to EXEC mode. In administration configuration mode, the abort command discards configuration changes and returns to administration EXEC mode. To abort a configuration session, enter the abort command, as shown in the following example:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# hostname host1 RP/0/RP0/CPU0:router(config)# interface POS 0/2/0/2 RP/0/RP0/CPU0:router(config-if)# description this is my interface RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.1.1.1 255.0.0.0 RP/0/RP0/CPU0:router(config-if)# shutdown RP/0/RP0/CPU0:router(config-if)# abort RP/0/RP0/CPU0:router#
Configuring the SDR Hostname

The hostname identifies an SDR on the network. Although devices can be uniquely identified by their Layer 2 and Layer 3 addresses (such as an IP address), it is often simpler to remember network devices by an alphanumeric hostname. This name is used in the CLI prompt and default configuration filenames and to identify the SDR on the network. To configure the hostname, enter the hostname command with the SDR name as shown in the following example:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# hostname SDR_SJ RP/0/RP0/CPU0:router(config)# commit RP/0/RP0/CPU0:Apr 7 00:07:33.246 : config[65669]: %LIBTARCFG-6-COMMIT : Configu ration committed by user 'user_a'. Use 'show configuration commit changes 1000000067' to view the changes. RP/0/RP0/CPU0:new_name(config)#
The preceding example sets the SDR name to SDR_SJ.
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.
4-38
Chapter 4
Configuring General Router Features Configuring the Management Ethernet Interface
Configuring the Management Ethernet Interface

The Management Ethernet interface on the RPs is used to connect the router to a network for remote management using a Telnet client, the Craft Works Interface (CWI), the Simple Network Management Protocol (SNMP), or other management agents. The following sections provide information on the Management Ethernet interface:

Specifying the Management Ethernet Interface Name in CLI Commands Displaying the Available Management Ethernet Interfaces Configuring the Management Ethernet Interface
Specifying the Management Ethernet Interface Name in CLI Commands

Before you can configure the Management Ethernet interface, you must know the Management Ethernet interface name, which is defined using the following syntax: typerack/slot/module/port. Table 4-6 describes the Management Ethernet interface name syntax.
Table 4-6 Management Ethernet Interface Name Syntax Description
Syntax Components type rack
Description Interface type for a Management Ethernet port is MgmtEth. Chassis number of the rack. In a single-shelf system, the rack is always 0. In a multishelf system, the LCC rack number range is 0 to 255. Physical slot of the RP or DRP on which the interface is located. For a Cisco CRS-1 router, the RP slot is RP0 or RP1 and the DRP slot is a number in the range of 0 to 7 (8-slot chassis) or 0 to 15 (16-slot chassis). For a Cisco XR 12000 Series Router, the PRPs may be installed in slots 0 through 15, depending on the router model. On an RP, the module is CPU0. DRPs have two processors, so the module is either CPU0 and CPU1. On Cisco XR 12000 Series Routers, there are three Ethernet ports on PRP-2 cards. The Ethernet ports are labeled ETH 0, ETH 1, and ETH 2. For the ETH 0 port, specify 0, for the ETH 1 port, specify 1, and for the ETH 2 port, specify 2. On a Cisco CRS-1 router, one Ethernet port labeled MGMT ETH exists on each RP, and one port exists for each DRP processor. Specify 0 for the MGMT ETH interface on an RP or DRP.
slot
module port
Table 4-6 provides examples of Management Ethernet interface names for a single-shelf system.
Table 4-7 Management Ethernet Interface Names for Single-Shelf Systems
Management Interface Cisco CRS-1 RP in slot RP0 Cisco CRS-1 RP in slot RP1 Cisco CRS-1 DRP CPU0 in slot 5
Interface Name MgmtEth0/RP0/CPU0/0 MgmtEth0/RP1/CPU0/0 MgmtEth0/5/CPU0/0
Example router(config)# interface MgmtEth0/RP0/CPU0/0 router(config)# interface MgmtEth0/RP1/CPU0/0 router(config)# interface MgmtEth0/5/CPU0/0
4-39
Chapter 4 Configuring the Management Ethernet Interface
Table 4-7
Management Ethernet Interface Names for Single-Shelf Systems (continued)
Cisco CRS-1 DRP CPU1 in slot 5
MgmtEth0/5/CPU1/0
router(config)# interface MgmtEth0/5/CPU1/0 router(config)# interface MgmtEth0/0/CPU0/0 router(config)# interface MgmtEth0/0/CPU0/1 router(config)# interface MgmtEth0/1/CPU0/0 router(config)# interface MgmtEth0/1/CPU0/1
Cisco XR 12000 Series Router PRP MgmtEth0/0/CPU0/0 in slot 0, port ETH0 Cisco XR 12000 Series Router PRP MgmtEth0/0/CPU0/1 in slot 0, port ETH1 Cisco XR 12000 Series Router PRP MgmtEth0/1/CPU0/0 in slot 1, port ETH0 Cisco XR 12000 Series Router PRP MgmtEth0/1/CPU0/1 in slot 1, port ETH1
Displaying the Available Management Ethernet Interfaces

To display the router interfaces, enter the show interfaces brief command in EXEC mode as follows:
RP/0/0/CPU0:router# show interfaces brief Intf Name Intf State LineP State Encap MTU Type (byte) BW (Kbps)
-------------------------------------------------------------------------------Nu0 Mg0/0/CPU0/0 Mg0/0/CPU0/1 PO0/3/0/0 PO0/3/0/1 PO0/3/0/2 PO0/3/0/3 PO0/3/0/4 PO0/3/0/5 PO0/3/0/6 PO0/3/0/7 . . . up up admin-down admin-down admin-down admin-down admin-down admin-down admin-down admin-down admin-down up up admin-down admin-down admin-down admin-down admin-down admin-down admin-down admin-down admin-down Null ARPA ARPA HDLC HDLC HDLC HDLC HDLC HDLC HDLC HDLC 1500 1514 1514 4474 4474 4474 4474 4474 4474 4474 4474 Unknown 100000 10000 155520 155520 155520 155520 155520 155520 155520 155520
The Management Ethernet interfaces are listed with the prefix Mg in the Intf Name column.
4-40
Chapter 4
Configuring General Router Features Configuring the Management Ethernet Interface
Configuring the Management Ethernet Interface

To use the Management Ethernet interface for system management and remote communication, you must configure an IP address and a subnet mask for the interface. If you want the interface to communicate with devices on other networks (such as remote management stations or TFTP servers), you need to configure a default route for the router.
Tip
For information on additional configuration options for the Management Ethernet interface, see the 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. 2. 3. 4. 5. 6. 7. 8. 9.
configure interface MgmtEthrack/slot/CPU0/port ipv4 address ipv4-address subnet-mask no shutdown exit router static address-family ipv4 unicast 0.0.0.0/0 default-gateway commit end show interfaces MgmtEthrack/slot/CPU0/port
DETAILED STEPS
Command or Action
Step 1
configure
Purpose Enters global configuration mode.
Example:
RP/0/RP0/CPU0:router# configure
Step 2
interface MgmtEthrack/slot/CPU0/port
Example:
RP/0/RP0/CPU0:router(config)# interface MgmtEth0/RP0/CPU0/0
Enters interface configuration mode and specifies the Management Ethernet interface of the primary RP.
The syntax is interface typerack/slot/module/port: The command parameters are described in Table 4-6.
4-41
Chapter 4 Configuring the Management Ethernet Interface
Command or Action
Step 3
ipv4 address ipv4-address subnet-mask
Purpose 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 Step 6
exit
Exits the Management Ethernet interface configuration mode. Configures a default route to use for communications with devices on other networks.
router static address family ipv4 unicast 0.0.0.0/0 default-gateway
Example:
RP/0/RP0/CPU0:router (config)# router static address-family ipv4 unicast 0.0.0.0/0 12.25.0.1
Replace default-gateway with the IP address of the local gateway that can be used to reach other networks. 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 the 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
Step 8
end
Ends the configuration session and returns to EXEC mode.
Example:
RP/0/RP0/CPU0:router(config)# end
Step 9
show interfaces MgmtEthrack/slot/CPU0/port
Displays the interface details to verify the settings.
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#
4-42
Chapter 4
Configuring General Router Features Manually Setting the Router Clock
RP/0/RP0/CPU0:router# show interfaces mgmtEth 0/RP0/CPU0/0 MgmtEth0/RP0/CPU0/0 is up, line protocol is up Hardware is Management Ethernet, address is 0011.93ef.e8ea (bia 0011.93ef.e8e) Description: Connected to Lab LAN Internet address is 10.1.1.1/24 MTU 1514 bytes, BW 100000 Kbit reliability 255/255, txload Unknown, rxload Unknown Encapsulation ARPA, loopback not set, ARP type ARPA, ARP timeout 04:00:00 Last clearing of "show interface" counters never 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 375087 packets input, 22715308 bytes, 87 total input drops 0 drops for unrecognized upper-level protocol Received 297320 broadcast packets, 0 multicast packets 0 runts, 0 giants, 0 throttles, 0 parity 48 input errors, 43 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 89311 packets output, 6176363 bytes, 0 total output drops Output 53 broadcast packets, 0 multicast packets 0 output errors, 0 underruns, 0 applique, 0 resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions
Related Documents
Related Topic Additional information on configuring management interfaces Document Title Cisco IOS XR Interface and Hardware Component Configuration Guide
Manually Setting the Router Clock

Generally, if the system is synchronized by a valid outside timing mechanism, such as a Network Time Protocol (NTP) or VINES clock source, you need not set the software clock. Use the clock set command for initial configuration or if a network time source is not available. The clock timezone command should be entered before the clock is set because it defines the difference between the system time and Coordinated Universal Time (UTC). When you set the time, you set the system time, and the router uses the clock timezone command setting to translate that time to UTC. The system internally keeps time in UTC. When you enter the show clock command, the router displays the system time. To manually set the router clock, complete the following steps:
SUMMARY STEPS
1. 2. 3. 4. 5. 6. 7.
configure clock timezone zone hours-offset commit end clock set hh:mm:ss dd mm yyyy clock update-calendar show clock
4-43
Chapter 4 Manually Setting the Router Clock
DETAILED STEPS
Command or Action
Step 1
configure
Example:
Step 2
clock timezone zone hours-offset
Sets the time zone for the router clock.
Example:
RP/0/RP0/CPU0:router(config)# clock timezone pst -8
The clock timezone command should be entered before the clock is set because it defines the difference between the system time and UTC. The system time is the time that appears when you enter the show clock command. zone: Name of the time zone to be displayed when standard time is in effect. hours-offset: Difference in hours from UTC. For detailed information about setting the system clock, including the configuration of a network time server, see the following Cisco documents:
Cisco IOS XR System Management
Note
Configuration Guide
Cisco IOS XR System Security Command
Reference
Step 3
commit
Commits the target configuration to the running configuration.
Example:
RP/0/RP0/CPU0:router(config-if)# commit
Step 4
end
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
4-44
Chapter 4
Configuring General Router Features Where to Go Next
Step 6
clock update-calendar
Updates the hardware clock (calendar clock) with the new clock settings.
Example:
RP/0/RP0/CPU0:router# clock update-calendar
The hardware clock is battery operated and runs continuously, even if the router is powered off or rebooted. Use this command to verify the settings.
Step 7
show clock
Displays the clock setting.
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 Descriptions of the clock commands available in the Cisco IOS XR software Commands used to configure the NTP Configuration of the NTP on the Cisco IOS XR software Document Title Cisco IOS XR System Management Command Reference Cisco IOS XR System Management Command Reference 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 xiv.
4-45
4-46
C H A P T E R
Configuring Additional Router Features

This chapter contains instructions and information for entering basic configurations using the command-line interface (CLI).
Contents

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
Configuring the Domain Name and Domain Name Server

Configure a domain name and domain name server (DNS) for your router to make contacting other devices on your network more efficient. Use the following guidelines:
To define a default domain name that the Cisco IOS XR software uses to complete unqualified hostnames (names without a dotted-decimal domain name), use the domain-name command in global configuration mode. To specify the address of one or more name servers to use for name and address resolution, use the domain name-server command in global configuration mode. If no name server address is specified, the default name server is 255.255.255.255 so the DNS lookup can be broadcast to the local network segment. If a DNS server is in the local network, it replies. If not, there might be a server that knows how to forward the DNS request to the correct DNS server. Use the show hosts command in EXEC mode to display the default domain name, the style of name lookup service, a list of name server hosts, and the cached list of hostnames and addresses.
5-1
Chapter 5 Configuring Telnet, HTTP, and XML Host Services
To configure the DNS and DNS server, complete the following steps:
SUMMARY STEPS
1. 2. 3. 4. 5. 6.
configure domain name domain-name-of-organization domain name-server ipv4-address commit end show hosts
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 Default domain is cisco.com Name/address lookup uses domain service Name servers: 10.1.1.1
Related Documents
Related Topic Complete descriptions of the domain services commands Document Title Implementing Host Services and Applications on Cisco IOS XR Software in the Cisco IOS XR IP Addresses and Services Configuration Guide
Configuring Telnet, HTTP, and XML Host Services

For security, some host services are disabled by default. Host services, such as Telnet, Extensible Markup Language (XML), and HTTP, can be optionally enabled using the commands described in this section. Host services provide the following features:

Enabling the Telnet server allows users to log in to the router using IPv4 or IPv6 Telnet clients. Enabling the HTTP server allows users to log in to the router using the CWI. Enabling the XML agent enables XML Common Object Request Broker Architecture (CORBA) agent services so that you can manage and configure the router using an XML interface.
5-2
Chapter 5
Configuring Additional Router Features Managing Configuration History and Rollback
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 Chapter 7, Upgrading and Managing Cisco IOS XR Software, for information on installing and activating packages.
SUMMARY STEPS
1. 2. 3. 4. 5. 6.
configure telnet ipv4 server max-servers 5 telnet ipv6 server max-servers 5 http server xml agent corba 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
Related Topic Installation and activation of the Manageability and Security Packages Descriptions of the Telnet commands Document Title Chapter 7, Upgrading and Managing Cisco IOS XR Software
Descriptions of the HTTP and XML server commands Cisco IOS XR System Management Command Reference Cisco IOS XR IP Addresses and Services Command Reference
Managing Configuration History and Rollback

After each commit operation, a record of the committed configuration changes is saved. This record contains only the changes made during the configuration session; it does not contain the complete configuration. Each record is assigned a unique ID, known as a commitID.
5-3
Chapter 5 Managing Configuration History and Rollback
When multiple commitIDs are present, you can use a commitID to identify a previous configuration to which you want to return, or you can use the commitID to load the configuration changes made during that configuration session. You can also load configuration changes from multiple commitIDs, and you can clear commitIDs. If you are thinking about rolling back the configuration to a specific commitID, consider the following guidelines:
You cannot roll back to a configuration that was removed because of package incompatibility. Configuration rollbacks can succeed only when the configuration passes all compatibility checks with the currently active Cisco IOS XR software. If an incompatible configuration is found during the rollback operation, the operation fails and an error is displayed.
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 History Log, page 5-5 Displaying the Configuration Changes Recorded in a CommitID, page 5-5 Previewing Rollback Configuration Changes, page 5-6 Rolling Back the Configuration to a Specific Rollback Point, page 5-6 Rolling Back the Configuration over a Specified Number of Commits, page 5-7 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-9
Displaying the CommitIDs

To display a history of up to 100 of the most recent commitIDs, enter the show configuration commit list command in EXEC or administration EXEC mode. Up to 100 of the most recent commitIDs are saved by the system. Each commitID entry shows the user who committed configuration changes, the connection used to execute the commit, and commitID time stamp. The commitIDs are shown in the Label/ID column. The following example shows the show configuration commit list command display in EXEC and administration EXEC modes:
RP/0/RP1/CPU0:router# show configuration SNo. ~~~~ 1 2 3 Label/ID ~~~~~~~~ 1000000219 1000000218 1000000217 User ~~~~ cisco cisco cisco Line ~~~~ vty0 vty1 con0_RP0_C commit list Time Stamp ~~~~~~~~~~ 12:27:50 UTC Wed Mar 22 2006 11:43:31 UTC Mon Mar 20 2006 17:44:29 UTC Wed Mar 15 2006
Client ~~~~~~ CLI CLI CLI
RP/0/RP1/CPU0:router# admin RP/0/RP1/CPU0:router(admin)# show configuration commit list SNo. ~~~~ 1 2 3 Label/ID ~~~~~~~~ 2000000022 2000000021 2000000020 User ~~~~ cisco cisco SYSTEM Line ~~~~ vty1 con0_RP0_C con0_RP0_C Client ~~~~~~ CLI CLI Setup Dial Time Stamp ~~~~~~~~~~ 15:03:59 UTC Fri Mar 17 2006 17:42:55 UTC Wed Mar 15 2006 17:07:39 UTC Wed Mar 15 2006
5-4
Chapter 5
Displaying the Configuration History Log

To display the header records for up to 1000 commit events, enter the show configuration commit history command in EXEC or administration EXEC mode, as shown in the following example. The output from this command does not show the details of the entries, but allows you to display a larger list of the commit events that occurred. To display the commitIDs to which you can roll back, use the show configuration commit list command.
RP/0/RP0/CPU0:router# show configuration commit history SNo. ~~~~ 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Label/ID ~~~~~~~~ 1000000144 1000000143 1000000142 1000000141 1000000140 1000000139 1000000138 1000000137 1000000136 1000000135 1000000134 1000000133 1000000132 1000000131 1000000130 1000000129 1000000128 1000000127 1000000126 1000000125 User ~~~~ user_a user_a user_a user_a user_b user_a user_a user_b user_a user_b user_b user_b user_b user_b user_b user_b user_b user_b user_b user_b Line Client ~~~~ ~~~~~~ vty0 CLI vty0 CLI 0.0.0.0 XMLAgent 0.0.0.0 XMLAgent con0_RP1_C CLI 0.0.0.0 XMLAgent 0.0.0.0 XMLAgent con0_RP1_C CLI 0.0.0.0 XMLAgent con0_RP1_C CLI con0_RP1_C CLI con0_RP1_C CLI con0_33_1 Rollback con0_33_1 Rollback con0_33_1 Rollback con0_33_1 CLI con0_33_1 CLI con0_33_1 CLI con0_33_1 Rollback con0_33_1 Rollback Time Stamp ~~~~~~~~~~ 00:16:51 UTC 00:04:32 UTC 21:58:36 UTC 21:46:07 UTC 21:43:30 UTC 21:40:13 UTC 21:34:48 UTC 21:32:10 UTC 21:30:13 UTC 19:45:04 UTC 19:37:26 UTC 19:36:27 UTC 18:34:45 UTC 18:32:37 UTC 18:31:09 UTC 18:28:12 UTC 18:27:22 UTC 18:27:19 UTC 18:25:55 UTC 18:24:25 UTC
Thu Thu Wed Wed Wed Wed Wed Wed Wed Wed Wed Wed Wed Wed Wed Wed Wed Wed Wed Wed
May May May May May May May May May May May May May May May May May May May May
11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004
Displaying the Configuration Changes Recorded in a CommitID

To display the configuration changes made during a specific commit session (commitID), go to EXEC or administration EXEC mode and enter the show configuration commit changes command followed by a commitID number. The easiest way to determine the commitID is to enter the show configuration commit changes ? command first. In the following example, the command help is used to display the available commitIDs, and then the changes for a specific commitID are displayed:
RP/0/RP1/CPU0:router(admin)# show configuration commit changes ? last since 2000000020 2000000021 2000000022 Changes made in the most recent <n> commits Changes made since (and including) a specific commit Commit ID Commit ID Commit ID
RP/0/RP1/CPU0:router(admin)# show configuration commit changes 2000000020 Building configuration... username cisco secret 5 $1$MgUH$xzUEW6jLfyAYLKJE.3p440 group root-system ! end
5-5
Previewing Rollback Configuration Changes

The show configuration rollback changes command allows you to preview the configuration changes that take place if you roll back the configuration to a specific commitID. For example, if you want to roll back the configuration to a specific point, all configuration changes made after that point must be undone. This rollback process is often accomplished by executing the no version of commands that must be undone. To display the prospective rollback configuration changes from the current configuration to a specific commitID, go to EXEC or administration EXEC mode and enter the show configuration rollback changes to commitId command. In the following example, the command help displays the available commitIDs, and then the rollback changes are displayed.
RP/0/RP1/CPU0:router# show configuration rollback changes to ? 1000000217 1000000218 1000000219 Commit ID Commit ID Commit ID
RP/0/RP1/CPU0:router# show configuration rollback changes to 1000000218 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.
Rolling Back the Configuration to a Specific Rollback Point

When you roll back the configuration to a specific rollback point, you undo all configuration changes made during the session identified by the commit ID for that rollback point, and you undo all configuration changes made after that point. The rollback process rolls back the configuration and commits the rolled-back configuration. The rollback process also creates a new rollback point so that you can roll back the configuration to the previous configuration.
5-6
Chapter 5
Tip
To preview the commands that undo the configuration during a rollback, use the show configuration rollback changes command. To roll back the router configuration to a previously committed configuration, go to EXEC or administration EXEC mode and enter the rollback configuration to commitId command:
RP/0/RP1/CPU0:router# rollback configuration to 1000000220 Loading Rollback Changes. Loaded Rollback Changes in 1 sec Committing. 2 items committed in 1 sec (1)items/sec Updating. Updated Commit database in 1 sec Configuration successfully rolled back to '1000000220'.
Rolling Back the Configuration over a Specified Number of Commits

When you roll back the configuration over a specific number of commits, you do not have to enter a specific commit ID. Instead, you specify a number x, and the software undoes all configuration changes made in the last x committed configuration sessions. The rollback process rolls back the configuration, commits the rolled-back configuration, and creates a new commitID for the previous configuration.
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 Loading Rollback Changes. Loaded Rollback Changes in Committing. 1 items committed in 1 sec Updating. Updated Commit database in Configuration successfully
1 sec (0)items/sec 1 sec rolled back 2 commits.
Loading CommitID Configuration Changes to the Target Configuration

If the changes saved for a specific commitID are close to what you want, but a rollback is not appropriate, you can load the configuration changes for a commitID into the target configuration, modify the target configuration, and then commit the new configuration. Unlike the rollback process, the loaded changes are not applied until you commit them.
5-7
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. To load commitID changes in the target configuration, go to global configuration or administration configuration mode and enter the load commit changes command with the commitID number. In the following example, show commands are used to display the changes for a commitID, the commitID configuration is loaded into the target configuration, and the target configuration is displayed:
RP/0/RP1/CPU0:router# show configuration commit changes ? last since 1000000217 1000000218 1000000219 1000000220 1000000221 Changes made in the most recent <n> commits Changes made since (and including) a specific commit Commit ID Commit ID Commit ID Commit ID Commit ID
RP/0/RP1/CPU0:router# show configuration commit changes 1000000219 Building configuration... interface Loopback100 ! interface POS0/1/0/0 ipv6 nd dad attempts 50 ! end RP/0/RP1/CPU0:router# config RP/0/RP1/CPU0:router(config)# load commit changes 1000000219 Building configuration... Loading. 77 bytes parsed in 1 sec (76)bytes/sec RP/0/RP1/CPU0:router(config)# show configuration Building configuration... interface Loopback100 ! interface POS0/1/0/0 ipv6 nd dad attempts 50 ! end
Loading Rollback Configuration Changes to the Target Configuration

If the changes for a specific rollback point are close to what you want, but a rollback is not appropriate, you can load the rollback configuration changes into the target configuration, modify the target configuration, and then commit the new configuration. Unlike the rollback process, the loaded changes are not applied until you commit them.
Tip
To display the rollback changes, enter the show configuration rollback changes command.
5-8
Chapter 5
Configuring Additional Router Features Configuring Logging and Logging Correlation
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 Deleting 4 rollback points '1000000001' to '1000000004' 64 KB of disk space will be freed. Continue with deletion?[confirm]
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:
RP/0/0/CPU0:router# clear configuration commit oldest 5 Deleting 5 rollback points '1000000005' to '1000000009' 80 KB of disk space will be freed. Continue with deletion?[confirm]
Configuring Logging and Logging Correlation

System messages generated by the Cisco IOS XR software can be logged to a variety of locations based on the severity level of the messages. For example, you could direct information messages to the system console and also log debugging messages to a network server. In addition, you can define correlation rules that group and summarize related events, generate complex queries for the list of logged events, and retrieve logging events through an XML interface.
5-9
Chapter 5 Configuring Logging and Logging Correlation
The following sections describe logging and the basic commands used to log messages in Cisco IOS XR software:

Logging Locations and Severity Levels, page 5-10 Alarm Logging Correlation, page 5-10 Configuring Basic Message Logging, page 5-11
Logging Locations and Severity Levels

Error messages can be logged to a variety of locations, as shown in Table 5-1.
Table 5-1 Logging Locations for System Error Messages
Logging Destination console vty terminal external syslog server internal buffer
Command (Global Configuration Mode) logging console logging monitor logging trap logging buffered
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 Level 0Emergencies Level 1Alerts Level 2Critical Level 3Errors Level 4Warnings Level 5Notifications Level 6Informational Level 7Debugging
Description System has become unusable. Immediate action needed to restore system stability. Critical conditions that may require attention. Error conditions that may help track problems. Warning conditions that are not severe. Normal but significant conditions that bear notification. Informational messages that do not require action. Debugging messages are for system troubleshooting only.
Alarm Logging Correlation

Alarm logging correlation is used to group and filter similar messages to reduce the amount of redundant logs and isolate the root causes of the messages. For example, the original message describing a card online insertion and removal (OIR) and system state being up or down can be reported, and all subsequent messages reiterating the same event can be correlated. When you create correlation rules, a common root event that is generating larger volumes of follow-on error messages can be isolated and sent to the correlation buffer. An operator can extract all correlated messages for display later, should the need arise. See the Cisco IOS XR System Management Configuration Guide for more information.
5-10
Chapter 5
Configuring Additional Router Features Configuring Logging and Logging Correlation
Configuring Basic Message Logging

Numerous options for logging system messages in Cisco IOS XR software are available. This section provides a basic example. To configure basic message logging, complete the following steps:
SUMMARY STEPS
1. 2. 3. 4. 5. 6. 7. 8.
configure logging {ip-address | hostname} logging trap severity logging console [severity] logging buffered [severity | buffer-size] commit end show logging
DETAILED STEPS
Command or Action
Step 1
configure
Example:
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
Example:
RP/0/RP0/CPU0:router(config)# logging trap debugging
Limits the logging of messages sent to syslog servers to only those messages at the specified level.
See Table 5-2 for a summary of the logging severity levels. When a severity level is specified, only messages at that severity level are logged on the console. See Table 5-2 for a summary of the logging severity levels.
Step 4
logging console [severity]
Logs messages on the console.
Example:
RP/0/RP0/CPU0:router(config)# logging console emergencies
5-11
Chapter 5 Configuring Logging and Logging Correlation
Command or Action
Step 5
logging buffered [severity
Purpose | buffer-size] Copies logging messages to an internal buffer.
Example:
RP/0/RP0/CPU0:router(config)# logging buffered 1000000
Newer messages overwrite older messages after the buffer is filled. 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
Example:
RP/0/RP0/CPU0:router(config)# commit
Step 7
end
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
In the following example, basic message logging is configured:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# logging 10.1.1.1 RP/0/RP0/CPU0:router(config)# logging trap debugging RP/0/RP0/CPU0:router(config)# logging console emergencies RP/0/RP0/CPU0:router(config)# logging buffered 1000000 RP/0/RP0/CPU0:router(config)# commit RP/0/RP0/CPU0:router(config)# end RP/0/RP0/CPU0:router# show logging Syslog logging: enabled (162 messages dropped, 0 flushes, 0 overruns) Console logging: level emergencies, 593 messages logged Monitor logging: level debugging, 0 messages logged Trap logging: level debugging, 2 messages logged Logging to 10.1.1.1, 2 message lines logged Buffer logging: level debugging, 722 messages logged Log Buffer (1000000 bytes): RP/0/RP0/CPU0:Apr RP/0/RP0/CPU0:Apr RP/0/RP0/CPU0:Apr LC/0/1/CPU0:Apr 8 LC/0/6/CPU0:Apr 8 RP/0/RP0/CPU0:Apr RP/0/RP1/CPU0:Apr LC/0/1/CPU0:Apr 8 8 19:18:58.679 8 19:19:01.287 8 19:22:15.658 19:22:30.122 : 19:22:30.160 : 8 19:22:30.745 8 19:22:32.596 19:22:35.181 : : instdir[203]: %INSTALL-INSTMGR-6-INSTALL_OP : instdir[203]: %INSTALL-INSTMGR-6-INSTALL_OP : instdir[203]: %INSTALL-INSTMGR-6-INSTALL_OP sysmgr[74]: %OS-SYSMGR-7-INSTALL_NOTIFICATION sysmgr[74]: %OS-SYSMGR-7-INSTALL_NOTIFICATION : sysmgr[79]: %OS-SYSMGR-7-INSTALL_NOTIFICATI : sysmgr[79]: %OS-SYSMGR-7-INSTALL_NOTIFICATI sysmgr[74]: %OS-SYSMGR-7-INSTALL_FINISHED : s
5-12
Chapter 5
Configuring Additional Router Features Creating and Modifying User Accounts and User Groups
LC/0/6/CPU0:Apr 8 RP/0/RP0/CPU0:Apr RP/0/RP1/CPU0:Apr RP/0/RP0/CPU0:Apr RP/0/RP0/CPU0:Apr RP/0/RP0/CPU0:Apr --More--
19:22:35.223 : 8 19:22:36.122 8 19:22:37.790 8 19:22:41.015 8 19:22:59.844 8 19:22:59.851
sysmgr[74]: %OS-SYSMGR-7-INSTALL_FINISHED : s : sysmgr[79]: %OS-SYSMGR-7-INSTALL_FINISHED : : sysmgr[79]: %OS-SYSMGR-7-INSTALL_FINISHED : : schema_server[332]: %MGBL-SCHEMA-6-VERSIONC : instdir[203]: %INSTALL-INSTMGR-4-ACTIVE_SOF : instdir[203]: %INSTALL-INSTMGR-6-INSTALL_OP
Related Documents
For more information on message logging and configuration of alarm correlation, see the following Cisco documents: Related Topic Configuration of system logging Commands used to configure logging Configuration of alarm correlation and generating complex queries Commands used to configure alarm correlation Retrieve logging events through an XML interface Document Title Cisco IOS XR System Management Configuration Guide Cisco IOS XR System Management Command Reference Cisco IOS XR System Management Configuration Guide Cisco IOS XR System Management Command Reference Cisco IOS XR XML API Guide
Disabling Console Logging

To disable console logging, enter the logging console disable command in global configuration mode.
Creating and Modifying User Accounts and User Groups

In the Cisco IOS XR software, users are assigned individual usernames and passwords. Each username is assigned to one or more user groups, each of which defines display and configuration commands the user is authorized to execute. This authorization is enabled by default in the Cisco IOS XR software, and each user must log in to the system using a unique username and password. The following sections describe the basic commands used to configure users and user groups. For a summary of user accounts, user groups, and task IDs, see the User Access Privileges section on page 4-13.

Displaying Details About User Accounts, User Groups, and Task IDs, page 5-14 Configuring User Accounts, page 5-14
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 Chapter 7, Upgrading and Managing Cisco IOS XR Software.
5-13
Chapter 5 Creating and Modifying User Accounts and User Groups
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 show aaa userdb username show aaa usergroup usergroup-name show task supported
Description Displays the task IDs and privileges assigned to a specific username. To display all users on the system, enter the command without a username. 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. 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.
Configuring User Accounts

User accounts, user groups, and task groups are created by entering the appropriate commands in one of the AAA configuration submodes, as shown in Figure 5-1. This section describes the process to configure usernames. For instructions to configure user groups, task groups, and other AAA security features, see the Cisco IOS XR System Security Configuration Guide.
Figure 5-1 AAA Configuration Submodes
User login
EXEC mode
Global configuration mode (commands) username username AAA configuration submodes Username configuration submode
usergroup usergroup-name
User group configuration submode
Task group configuration submode
5-14
116542
taskgroup taskgroup-name
Chapter 5
Configuring Additional Router Features Creating and Modifying User Accounts and User Groups
Creating Users and Assigning Groups

To create a user, assign a password, and assign the user to a group, perform the following procedure:
SUMMARY STEPS
1. 2. 3.
configure username user-name password {0 | 7} password or secret {0 | 5} password group group-name Repeat Step 4 for each user group to be associated with the user specified in Step 2. commit
4. 5. 6.
DETAILED STEPS
Command or Action
Step 1
configure
Example:
Step 2
username user-name
Creates a name for a new user (or identifies a current user) and enters username configuration submode.
Example:
RP/0/RP0/CPU0:router(config)# username user1
The user-name argument can be only one word. Spaces and quotation marks are not allowed. Use the secret command to create a secure login password for the user names specified in Step 2. Entering 0 following the password command specifies that an unencrypted (clear-text) password follows. Entering 7 following the password command specifies that an encrypted password follows. Entering 0 following the secret command specifies that 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 3
password {0 | 7} password
Specifies a password for the user named in Step 2.

or
secret {0 | 5} password
Example:
RP/0/RP0/CPU0:router(config-un)# password 0 pwd1
or
RP/0/RP0/CPU0:router(config-un)# secret 5 pwd1
5-15
Chapter 5 Configuration Limiting
Command or Action
Step 4
group group-name
Purpose Assigns the user named in Step 2 to a user group.
Example:
RP/0/RP0/CPU0:router(config-un)# group sysadmin
The user takes on all attributes of the user group, as defined by the user group association to various task groups. Each user must be assigned to at least one user group. A user may belong to multiple user groups.
Step 5 Step 6
Repeat Step 4 for each user group to be associated with the user specified in Step 2.
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: Related Topic Document Title
Create users, assign users to user groups, create and Cisco IOS XR System Security Configuration Guide modify user groups, and configure remote AAA access
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.
5-16
Chapter 5
Configuring Additional Router Features Configuration Limiting
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-17 IS-IS Configuration Limits, page 5-18 OSPFv2 and v3 Configuration Limits, page 5-18 BGP Configuration Limits, page 5-21 Routing Policy Language Line and Policy Limits, page 5-22 Multicast Configuration Limits, page 5-24 MPLS Configuration Limits, page 5-25
Static Route Configuration Limits

Table 5-4 summarizes the maximum limits for static routes, including the commands used to display and change the limits.
Table 5-4 Static Route Configuration Limits and Commands
Default Absolute Maximum Maximum Feature Limit Description Limit Limit Maximum static IPv4 routes Maximum static IPv6 routes 4000 4000 40,000 40,000
Configuration Command (Static Router Configuration Mode) maximum path ipv4 n maximum path ipv6 n
Show Current Settings Command (EXEC or Global Configuration Mode) show running-config router static show running-config router static
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 RP/0/RP1/CPU0:router(config-static)# RP/0/RP1/CPU0:router(config-static)# RP/0/RP1/CPU0:router(config-static)# router static maximum path ipv4 5000 address-family ipv4 unicast 0.0.0.0/0 172.29.52.1 ! ! static maximum path ipv4 5000 commit show running-config router static
5-17
IS-IS Configuration Limits

Table 5-5 summarizes the maximum limits for IS-IS, including the commands used to display and change the limits.
Table 5-5 IS-IS Configuration Limits and Commands
Default Maximum Feature Limit Description Limit Maximum number of prefixes redistributed into IS-IS 10,000
Absolute Maximum Limit 28,000
Configuration Command (Address Family Configuration Mode)
Show Current Settings Command (EXEC Mode)
maximum-redistributed-prefixes n show isis adjacency
Number of active parallel 8 paths for each route on a Cisco CRS-1 router Number of active parallel 8 paths for each route on a Cisco XR 12000 Series Router
32
maximum-paths n
show isis route
16
maximum-paths n
show isis route
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)#
OSPFv2 and v3 Configuration Limits

Table 5-6 summarizes the maximum limits for OSPF, including the commands used to display and change the limits.
5-18
Chapter 5
Table 5-6
OSPFv2 and OSPFv3 Configuration Limits and Commands
Feature Limit Description Maximum number of interfaces that can be configured for an OSPF instance Maximum routes redistributed into OSPF
Default Maximum Limit 255
Absolute Maximum Limit 1024
Configuration Command (Router Configuration Mode) maximum interfaces n
Show Current Settings Command (EXEC Mode) show ospf
10,000
28,672
maximum redistributed-prefixes show ospf n Note The maximum number of redistributed prefixes is displayed only if redistribution is configured. maximum paths n show running-config router ospf
Note
Maximum number of parallel routes (maximum paths) on Cisco CRS-1 routers
32 (OSPFv2) 16 (OSPFv3)
32
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. 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.
Maximum number of 16 parallel routes (maximum paths) on a Cisco XR 12000 Series Router
16
maximum paths n
show running-config router ospf

Note
Examples
The following subsections provide the following examples:

Maximum Interfaces for Each OSPF Instance, page 5-19 Maximum Routes Redistributed into OSPF, page 5-20 Number of Parallel Links (max-paths), page 5-21
Maximum Interfaces for Each OSPF Instance

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 Routing Process "ospf 100" with ID 0.0.0.0 Supports only single TOS(TOS0) routes Supports opaque LSA It is an area border router Initial SPF schedule delay 5000 msecs Minimum hold time between two consecutive SPFs 10000 msecs Maximum wait time between two consecutive SPFs 10000 msecs Initial LSA throttle delay 500 msecs Minimum hold time for LSA throttle 5000 msecs
5-19
Maximum wait time for LSA throttle 5000 msecs Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs Maximum number of configured interfaces 255 --More--
The following example configures the maximum interface limit on a router:

RP/0/RP1/CPU0:router# configure RP/0/RP1/CPU0:router(config)# router ospf 100 RP/0/RP1/CPU0:router(config-router)# maximum interfaces 600 RP/0/RP1/CPU0:router(config-router)# end Uncommitted changes found, commit them? [yes]: y RP/0/RP1/CPU0:Mar 30 16:12:39 : config[65740]: %LIBTARCFG-6-COMMIT : Configurati on committed by user 'cisco'. Use 'show configuration commit changes 1000000540' to view the c hanges. RP/0/RP1/CPU0:Mar 30 16:12:39 : config[65740]: %SYS-5-CONFIG_I : Configured from console by cisco RP/0/RP1/CPU0:router# show ospf Routing Process "ospf 100" with ID 0.0.0.0 Supports only single TOS(TOS0) routes Supports opaque LSA It is an area border router Initial SPF schedule delay 5000 msecs Minimum hold time between two consecutive SPFs 10000 msecs Maximum wait time between two consecutive SPFs 10000 msecs Initial LSA throttle delay 500 msecs Minimum hold time for LSA throttle 5000 msecs Maximum wait time for LSA throttle 5000 msecs Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs Maximum number of configured interfaces 600 --More--
Maximum Routes Redistributed into 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 RP/0/RP1/CPU0:Mar 30 16:26:52 : config[65740]: %LIBTARCFG-6-COMMIT : Configurati on committed by user 'cisco'. Use 'show configuration commit changes 1000000541' to view the changes. RP/0/RP1/CPU0:Mar 30 16:26:52 : config[65740]: %SYS-5-CONFIG_I : Configured from console by cisco RP/0/RP1/CPU0:router#
5-20
Chapter 5
Number of Parallel Links (max-paths)

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 RP/0/RP1/CPU0:Mar 30 18:05:13 : config[65740]: %LIBTARCFG-6-COMMIT : Configurati on committed by user 'cisco'. Use 'show configuration commit changes 1000000542' to view the changes. RP/0/RP1/CPU0:Mar 30 18:05:13 : config[65740]: %SYS-5-CONFIG_I : Configured from console by cisco RP/0/RP1/CPU0:router#
BGP Configuration Limits

The maximum number of BGP neighbors (peers) that can be configured is 1024. This number cannot be changed through configuration. Any attempt to configure additional neighbors beyond the limit fails. To prevent neighbors (peers) from flooding BGP with advertisements, a limit is placed on the number of prefixes that can be accepted from a peer for each supported address family. You can override the default limits for an address family with the maximum-prefix command. Table 5-7 summarizes the maximum configuration limits for BGP.
Table 5-7 BGP Configuration Limits and Commands
Feature Limit Description Maximum number of neighbors (peers) IPv4 unicast maximum prefixes that can be received from a neighbor IPv4 multicast maximum prefixes that can be received from a neighbor IPv6 unicast maximum prefixes that can be received from a neighbor Maximum equal-cost parallel routes to external peers
Default Maximum Limit 1024 524,288
Configuration Command (Router Configuration Mode) None. This limit cannot be changed or exceeded.
Show Current Settings Command (EXEC Mode) None show bgp neighbor IP_address
4,294,967, maximum-prefix n 295 4,294,967, maximum-prefix n 295 4,294,967, maximum-prefix n 295 8 maximum-paths n
131,072
show bgp neighbor IP_address
131,072
show bgp neighbor IP_address
show running-config
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.
5-21
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 RP/0/RP1/CPU0:Mar 30 19:13:16 : config[65740]: %LIBTARCFG-6-COMMIT : Configurati on committed by user 'cisco'. Use 'show configuration commit changes 1000000544' to view the c hanges. RP/0/RP1/CPU0:Mar 30 19:13:17 : config[65740]: %SYS-5-CONFIG_I : Configured from console by cisco RP/0/RP1/CPU0:router(config-bgp-nbr-af)#
Routing Policy Language Line and Policy Limits

Two limits for Routing Policy Language (RPL) configurations exist:
1. 2.
Lines of configuration: The number of lines entered by the user, including the beginning and ending statements (that is route-policy). The lines of configuration for sets are also included. Number of RPL policies: The number of policies that can be configured on the router. Policies are counted only once: Multiple use of the same policy counts as a single policy toward the limit 1.
The limits for RPL lines and policies are summarized in Table 5-8. You can change the default values up to the absolute maximum, but you cannot change the value to a number less than the number of items that are currently configured.
Table 5-8 Maximum Lines of RPL: Configuration Limits and Commands
Limit Description Maximum number of RPL lines Maximum number of RPL policies
Default Maximum Limit 65,536 3500
Absolute Maximum Limit 131,072 5000
Show Current Settings Configuration Command Command (Global Configuration Mode) (EXEC Mode) rpl maximum lines n rpl maximum policies n show rpl maximum lines show rpl maximum policies
5-22
Chapter 5
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 Current Current Max Total Limit Limit -----------------------------------------------------------Lines of configuration 0 65536 131072 Policies 0 3500 5000 Compiled policies size (kB) 0 RP/0/RP1/CPU0:router#
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 RP/0/RP1/CPU0:Apr 1 00:23:44.062 : config[65709]: %LIBTARCFG-6-COMMIT : Configu ration committed by user 'UNKNOWN'. Use 'show configuration commit changes 1000000010' to vi ew the changes. RP/0/RP1/CPU0:router(config)# exit RP/0/RP1/CPU0:Apr 1 00:23:47.781 : config[65709]: %SYS-5-CONFIG_I : Configured from console by console RP/0/RP1/CPU0:router# show rpl maximum Current Current Max Total Limit Limit -----------------------------------------------------------Lines of configuration 0 80000 131072 Policies 0 4000 5000 Compiled policies size (kB) 0 RP/0/RP1/CPU0:router#
5-23
Multicast Configuration Limits

Table 5-9 summarizes the maximum limits for multicast configuration, including the commands used to display and change the limits.
Table 5-9 Multicast Configuration Limits and Commands
Default Maximum Feature Limit Description Limit Maximum number of groups used by IGMP and accepted by a router 50,000
Absolute Maximum Limit 75,000
Configuration Command maximum groups n (router IGMP configuration mode)
Show Current Settings Command (EXEC Mode) show igmp summary
Internet Group Management Protocol (IGMP) Limits
Maximum number of 20,000 groups for each interface accepted by a router
40,000
maximum groups n (router IGMP interface configuration mode)
show igmp summary
Multicast Source Discovery Protocol (MSDP) Limits
Maximum MSDP Source 20,000 Active (SA) entries Maximum MSDP SA entries that can be learned from MSDP peers Maximum PIM routes supported Maximum PIM egress states Maximum PIM registers Maximum number of PIM group map ranges learned from Auto-RP 20,000
75,000 75,000
maximum external-sa n (router MSDP configuration mode) maximum peer-external-sa n (router MSDP configuration mode)
show msdp summary show msdp summary
Protocol Independent Multicast (PIM) Limits
100,000 300,000 20,000 500
200,000 600,000 75,000 5000
maximum routes n (router PIM configuration mode) maximum route-interfaces n (router PIM configuration mode) maximum register-states n (router PIM configuration mode) maximum group-mappings autorp n (router PIM configuration mode)
show pim summary show pim summary show pim summary show pim summary
5-24
Chapter 5
MPLS Configuration Limits

Table 5-10 summarizes the maximum limits for MPLS configuration, including the commands used to display and change the limits.
Table 5-10 MPLS Configuration Limits and Commands
Limit Description Maximum traffic engineer (TE) tunnels head
Default Maximum Limit 2500
Show Current Settings Configuration Command Command (Global Configuration Mode) (EXEC Mode) mpls traffic-eng maximum show mpls traffic-eng tunnels n maximum tunnels
Other Configuration Limits

Table 5-11 summarizes the maximum limits for additional configuration limits, including the commands used to display and change the limits.
Table 5-11 Additional Configuration Limits and Commands
Limit Description IPv4 ACL (access list and prefix list) IPv4 ACE (access list and prefix list) IPv6 ACL (access list and prefix list) IPv6 ACE (access list and prefix list)
Default Maximum Limit 5000 200,000 1000 50,000
Absolute Maximum Limit 16000 350,000 16000 350,000
Show Current Settings Configuration Command Command (Global Configuration Mode) (EXEC Mode) ipv4 access-list maximum acl threshold n ipv4 access-list maximum ace threshold n ipv6 access-list maximum acl threshold n ipv6 access-list maximum ace threshold n show access-lists ipv4 maximum show access-lists ipv4 maximum show access-lists ipv6 maximum show access-lists ipv6 maximum
5-25
5-26
C H A P T E R
CLI Tips, Techniques, and Shortcuts

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-6 Wildcards, Templates, and Aliases, page 6-11 Command History, page 6-17 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.
CLI Tips and Shortcuts

The following sections describe tips and shortcuts useful when using the CLI:

Entering Abbreviated Commands, page 6-2 Using the Question Mark (?) to Display On-Screen Command Help, page 6-2 Completing a Partial Command with the Tab Key, page 6-4 Identifying Command Syntax Errors, page 6-5 Using the no Form of a Command, page 6-5 Editing Command Lines that Wrap, page 6-5
6-1
Chapter 6 CLI Tips and Shortcuts
Entering Abbreviated Commands

You can abbreviate commands and keywords to the number of characters that allow a unique abbreviation. For example, the configure command can be abbreviated as config because the abbreviated form of the command is unique. The router accepts and executes the abbreviated command.
Using the Question Mark (?) to Display On-Screen Command Help

Use the question mark (?) to learn what commands are available and the correct syntax for a command. Table 6-1 summarizes the options for on-screen help.
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.
Table 6-1
On-Screen Help Commands
Command partial-command?
Description 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.
? command ?
Lists all commands available for a particular command mode. Include a space before the question mark (?) to list the keywords and arguments that belong to a command.
RP/0/RP0/CPU0:router# configure ? exclusive terminal <cr> Configure exclusively from this terminal Configure from the terminal
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 ? taskgroup userdb usergroup Show all the local taskgroups configured in the system Show all local users with the usergroups each belong to Show all the local usergroups configured in the system
Note
Include a space between the keyword and question mark.
6-2
Chapter 6
CLI Tips, Techniques, and Shortcuts CLI Tips and Shortcuts
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 ? log-update maximum WORD Control access lists log updates Out of resources configration Access list name - maximum 32 characters
Note Step 2
The number ranges (within the angle brackets) are inclusive ranges. 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 ? <1-2147483646> Sequence number for this entry deny Specifies packets to reject permit Specifies packets to forward remark Comment for access list <cr> 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 ? <0-255> An IPv4 Protocol Number A.B.C.D Source IP address or prefix ahp Authentication Header Protocol any Any source host eigrp Cisco's EIGRP Routing Protocol esp Encapsulation Security Payload gre Cisco's GRE Tunneling host A single source host icmp Internet Control Message Protocol igmp Internet Gateway Message Protocol igrp Cisco's IGRP Routing Protocol ipinip IP in IP tunneling ipv4 Any IPv4 Protocol nos KA9Q NOS Compatible IP over IP Tunneling ospf OSPF Routing Protocol pcp Payload Compression Protocol pim Protocol Independent Multicast sctp Stream Control Transmission Protocol tcp Transport Control Protocol udp User Datagram Protocol RP/0/0/CPU0:router(config)#ipv4 access-list list1 deny
Generally, uppercase letters represent variables (arguments).
6-3
Chapter 6 CLI Tips and Shortcuts
Step 4
Enter an IP address, followed by a space and a question mark (?), to list additional options:
RP/0/RP0/CPU0:router(config)# ipv4 access-list list1 deny 172.31.134.0 ? A.B.C.D log log-input <cr> Wildcard bits Log matches against this entry Log matches against this entry, including input interface
RP/0/RP0/CPU0:router(config)# ipv4 access-list list1 deny 172.31.134.0
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.
Completing a Partial Command with the Tab Key

If you cannot remember a complete command name or want to reduce the amount of typing you have to perform, enter the first few letters of the command, then press the Tab key. If only one command begins with that character string, the system completes the command for you. If the characters you entered indicate more than one command, the system beeps to indicate that the text string is not unique and the system provides a list of commands that match the text entered. In the following example, the CLI recognizes conf as a unique string in EXEC mode and completes the command when Tab is pressed:
RP/0/RP0/CPU0:router# conf<Tab> 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.
6-4
Chapter 6
CLI Tips, Techniques, and Shortcuts CLI Tips and Shortcuts
Identifying Command Syntax Errors

If an incorrect command is entered, an error message is returned with the caret (^) at the point of the error. In the following example, the caret appears where the character was typed incorrectly in the command:
RP/0/0/CPU0:router# configure termiMal ^ % Invalid input detected at '^' marker.
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 ? exclusive Configure exclusively from this terminal terminal Configure from the terminal <cr>
Using the no Form of a Command

Almost every configuration command has a no form. Depending on the command, the no form may enable or disable a feature. For example, when configuring an interface, the no shutdown command brings up the interface, and the shutdown command shuts down the interface. The username command creates a new user, and the no username command deletes a user when entered with a valid username. The Cisco IOS XR software command reference publications provide the complete syntax for the configuration commands and describe what the no form of a command does. See the Related Documents section on page xiv for more information.
Editing Command Lines that Wrap

The CLI provides a wraparound feature for commands that extend beyond a single line on the screen. When the cursor reaches the right margin, the command line shifts ten spaces to the left. The first ten characters of the line are not shown, but it is possible to scroll back and check the syntax at the beginning of the command. To scroll back, press Ctrl-B or the left arrow key repeatedly, or press Ctrl-A to return directly to the beginning of the line. In the following example, the ipv4 access-list command entry is too long to display on one line. When the cursor reaches the end of the line, the line is shifted to the left and redisplayed. The dollar sign ($) after the command prompt indicates that the line has been scrolled to the left and the beginning of the command is hidden.
RP/0/0/CPU0:router(config)# $s-list 101 permit tcp 172.31.134.5 255.255.255.0 172.31.135.0
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$
6-5
Chapter 6 Displaying System Information with show Commands
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.
Displaying System Information with show Commands

The show commands display information about the system and its configuration. The following sections describe some common show commands and provide techniques to manage the output from those commands:

Common show Commands, page 6-6 Browsing Display Output when the --More-- Prompt Appears, page 6-7 Halting the Display of Screen Output, page 6-8 Redirecting Output to a File, page 6-8 Narrowing Output from Large Configurations, page 6-8 Filtering show Command Output, page 6-10
Common show Commands

Some of the most common show commands are described in Table 6-2.
Table 6-2 Common show Commands in Cisco IOS XR Software
Command show version
Description Displays system information.
Command Mode EXEC or administration EXEC mode Global or administration configuration mode
show configuration
Displays the uncommitted configuration changes made during a configuration session.
show running-config (EXEC or global configuration mode)
Displays the current running configuration for the SDR to which EXEC or global you are connected. configuration mode administration EXEC or administration configuration mode
Displays the current running configuration that applies to the show running-config (administration EXEC or entire router or multishelf system. administration configuration mode)
6-6
Chapter 6
CLI Tips, Techniques, and Shortcuts Displaying System Information with show Commands
Table 6-2
Common show Commands in Cisco IOS XR Software (continued)
Command show tech-support
Description
Command Mode
Collects a large amount of system information for EXEC or troubleshooting. You can provide this output to technical support administration representatives when reporting a problem. EXEC mode Displays information about cards and modules assigned to the SDR to which you are connected. Displays information about all cards and modules in the router. EXEC mode administration EXEC mode
show platform (EXEC mode) show platform (administration EXEC mode) show environment
Displays hardware information for the system, including fans, EXEC mode or LEDs, power supply voltage and current, and temperatures. Enter administration show environment ? to see additional command options. EXEC mode For more information on the use of these commands, see the Related Documents section on page xiv.
Browsing Display Output when the --More-- Prompt Appears

When command output requires more than one screen, such as for the ?, show, or more command, the output is presented one screen at a time, and a --More-- prompt is displayed at the bottom of the screen. To display additional command output, do one of the following:

Press Return to display the next line. Press the space bar to display the next screen of output.
The following example shows one screen of data and the --More-- prompt:
RP/0/RP0/CPU0:router# show ? aaa adjacency aliases alphadisplay aps arm arp as-path-access-list asic-errors atc auto-rp bgp buffer-manager bundle calendar cdp cef cetftp checkpoint cinetd clns clock commit --More-Show AAA configuration and operational data Adjacency information Display alias commands Shows the message being displayed on the alpha display SONET APS information IP ARM information ARP table List AS path access lists ASIC error information Attractor Cache related Auto-RP Commands BGP show commands Show all buffer manager memory related information Show hardware related information for Bundles. Display the system calendar CDP information Cisco Express Forwarding HFR control plane ethernet TFTP server Show checkpoint services cinetd daemon Display CLNS related information Display the system clock Show commit information
6-7
Tips
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:
RP/0/RP1/CPU0:router# terminal length 20
For information on searching or filtering CLI output, see the Filtering show Command Output section on page 6-10.
Halting the Display of Screen Output

To interrupt screen output and terminate a display, press Ctrl-C, as shown in the following example:
RP/0/RP0/CPU0:router# show running-config <Ctrl-C>
Redirecting Output to a File

By default, CLI command output is displayed on screen. CLI command output can be redirected to a user-specified file by entering a filename and location after the show command syntax. The following command syntax is used to redirect output to a file:
show
command
| file
filename
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#
Narrowing Output from Large Configurations

Displaying a large running configuration can produce thousands of lines of output. To limit the output of a show command to only the items you want to view, use the procedures in the following sections:

Limiting show Command Output to a Specific Feature or Interface, page 6-9 Using Wildcards to Display All Instances of an Interface, page 6-9
6-8
Chapter 6
CLI Tips, Techniques, and Shortcuts Displaying System Information with show Commands
Limiting show Command Output to a Specific Feature or Interface

Entering keywords and arguments in the show command limits the show output to a specific feature or interface. In the following example, only information about the static IP route configuration is displayed:
RP/0/RP1/CPU0:router# show running-config router static 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 ! !
In the following example, the configuration for a specific interface is displayed:

RP/0/RP0/CPU0:router# show running-config interface POS 0/1/0/1 interface pos0/1/0/1 ipv4 address 10.21.54.31 255.255.0.0 !
Using Wildcards to Display All Instances of an Interface

To display the configuration for all instances, enter the asterisk (*) wildcard character.
Note
See the Using Wildcards to Identify Interfaces in show Commands section on page 6-11 for more information. In the following example, a configuration for all Packet-over-SONET/SDH (POS) interfaces is displayed:
RP/0/RP1/CPU0:router# show running-config interface pos * 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 !
6-9
interface POS0/1/0/3 ipv4 address 10.2.3.7 255.255.255.0 pos crc 32 ! shutdown keepalive disable ! --More--
Filtering show Command Output

Output from the show commands can generate a large amount of data. To display only a subset of information, enter the pipe character (|) followed by a keyword (begin, include, exclude, or file) and a regular expression. Table 6-3 shows the filtering options for the show command.
Table 6-3 show Command Filter Options
Command
show command | begin regular-expression
Description Begins unfiltered output of the show command with the first line that contains the regular expression. Displays output lines that do not contain the regular expression. Displays output lines that contain the regular expression. Writes the output lines that contain the regular expression to the specified file on the specified device.
show command | exclude regular-expression show command | include regular-expression show command | file device0:path/file
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 Null0 is up, line protocol is up 0 drops for unrecognized upper-level protocol POS0/2/0/0 is administratively down, line protocol 0 drops for unrecognized upper-level protocol POS0/2/0/1 is administratively down, line protocol 0 drops for unrecognized upper-level protocol POS0/2/0/2 is administratively down, line protocol 0 drops for unrecognized upper-level protocol POS0/2/0/3 is administratively down, line protocol 0 drops for unrecognized upper-level protocol MgmtEthernet0/RP0/CPU0/0 is administratively down, down MgmtEthernet0/RP0/CPU0/0 is administratively down, down 0 drops for unrecognized upper-level protocol
is administratively down is administratively down is administratively down is administratively down line protocol is administratively line protocol is administratively
Note
Filtering is available for submodes, complete commands, and anywhere that output.
<cr>
appears in the ?
6-10
Chapter 6
CLI Tips, Techniques, and Shortcuts Wildcards, Templates, and Aliases
Adding a Filter at the --More-- Prompt

You can specify a filter at the --More-- prompt of a show command output by entering a forward slash (/) followed by a regular expression. The filter remains active until the command output finishes or is interrupted (using Ctrl-Z or Ctrl-C). The following rules apply to this technique:

If a filter is specified at the original command or previous --More-- prompt, a second filter cannot be applied. The use of the keyword begin does not constitute a filter. The minus sign () preceding a regular expression displays output lines that do not contain the regular expression. The plus sign (+) preceding a regular expression displays output lines that contain the regular expression.
In the following example, the user adds a filter at the --More-- prompt to show only the lines in the remaining output that contain the regular expression ip.
RP/0/RP0/CPU0:router# show configuration running | begin line Building configuration... line console exec-timeout 120 120 ! logging trap --More-/ip filtering... ip route 0.0.0.0 255.255.0.0 pos0/2/0/0 interface pos0/2/0/0 ip address 172.19.73.215 255.255.0.0 end
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.
Wildcards, Templates, and Aliases

This section contains the following topics:

Using Wildcards to Identify Interfaces in show Commands, page 6-11 Creating Configuration Templates, page 6-13 Aliases, page 6-16 Keystrokes Used as Command Aliases, page 6-17
Using Wildcards to Identify Interfaces in show Commands

Wildcards (*) identify a group of interfaces in show commands. Table 6-4 provides examples of wildcard usage to identify a group of interfaces.
6-11
Chapter 6 Wildcards, Templates, and Aliases
Table 6-4
Examples of Wildcard Usage
Wildcard Syntax * pos* pos0/1/* pos0/3/4.*
Description Specifies all interfaces Specifies all POS interfaces in the system Specifies all POS interfaces in rack 0, slot 1 Specifies all subinterfaces for POS0/3/4
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 pos crc 32 ! keepalive disable interface POS0/1/0/1 ipv4 address 10.2.3.5 pos crc 32 ! keepalive disable interface POS0/1/0/2 ipv4 address 10.2.3.6 pos crc 32 ! keepalive disable interface POS0/1/0/3 ipv4 address 10.2.3.7 pos crc 32 ! keepalive disable --More--
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
6-12
Chapter 6
In the following example, the state of all POS interfaces is displayed:

RP/0/RP1/CPU0:router# show interfaces pos* brief Intf Intf LineP Encap MTU BW Name State State Type (byte) (Kbps) -------------------------------------------------------------------------------PO0/1/0/0 up up HDLC 4474 2488320 PO0/1/0/1 up up HDLC 4474 2488320 PO0/1/0/2 up up HDLC 4474 2488320 PO0/1/0/3 up up HDLC 4474 2488320 PO0/1/0/4 up up HDLC 4474 2488320 PO0/1/0/5 up up HDLC 4474 2488320 PO0/1/0/6 up up HDLC 4474 2488320 PO0/1/0/7 up up HDLC 4474 2488320 PO0/1/0/8 up up HDLC 4474 2488320 PO0/1/0/9 up up HDLC 4474 2488320 PO0/1/0/10 up up HDLC 4474 2488320 PO0/1/0/11 up up HDLC 4474 2488320 PO0/1/0/12 up up HDLC 4474 2488320 PO0/1/0/13 up up HDLC 4474 2488320 PO0/1/0/14 up up HDLC 4474 2488320 PO0/1/0/15 up up HDLC 4474 2488320
Creating Configuration Templates

Configuration templates allow you to create a name that represents a group of configuration commands. After a template is defined, it can be applied to interfaces by you or other users. As networks scale to large numbers of nodes and ports, the ability to configure multiple ports quickly using templates can greatly reduce the time it takes to configure interfaces. 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. 2. 3. 4. 5. 6.
configure template template-name [($parameter $parameter...)] [config-commands] Enter the template commands. end-template commit show running-config template template-name
6-13
DETAILED STEPS
Command or Action
Step 1
configure
Example:
Router# configure
Step 2
template template-name [($parameter $parameter...)] [config-commands]
Enters template configuration mode and creates a template.

template-name: Unique name for the template to be applied to the running configuration. 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.
Example:
RP/0/RP0/CPU0:router(config)# template tmplt_1
Step 3
Enter the template commands.

Example:
RP/0/RP0/CPU0:router(config-TPL)# hostname test
Defines the template commands.
Step 4
end-template
Ends the template definition session and exits template configuration mode.
Example:
RP/0/RP0/CPU0:router(config-TPL)# end-template
When you end the template session, you are returned to global configuration mode.
Step 5
commit
Applies the target configuration commands to the running configuration.
Example:
RP/0/RP0/CPU0:router(config-TPL)# commit
Step 6
show running-config template template-name
Displays the details of the template.
Example:
RP/0/RP0/CPU0:router# show running-config template tmplt_1
6-14
Chapter 6
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 template test2 (hostname ) hostname $hostname end-template
Applying Configuration Templates

To apply a template, enter the apply-template template-name [(parameter)] command in global configuration mode and consider the following guidelines:

Only one template can by applied at a time. If the same template is applied multiple times, the most recent application overwrites the previous ones. Provide the exact number of parameters for the template. Templates are applied as a best effort operation; only valid changes are committed. If any command in the template fails, that command is discarded. 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.
6-15
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
Syntax alias-name command-syntax (parameterx)
Specifies that the Alias Is Created for Name of the command alias. An alias name can be a single word or multiple words joined by a dash (). Original command syntax. Valid abbreviations of the original command syntax can be entered for the command-syntax argument. Argument or keyword that belongs to the command you specified for the command-syntax argument. When the parameter is entered in parenthesis after the alias name, the alias requires a parameter name. To associate the parameter with a command within the alias, enter the $ character preceding the parameter name.
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.
6-16
Chapter 6
CLI Tips, Techniques, and Shortcuts Command History
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
RP/0/0/CPU0:router(config)# interface my-cookie RP/0/0/CPU0:router(config)# interface mgmtEth 0/0/CPU0/0 RP/0/0/CPU0:router(config-if)#
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.
Keystrokes Used as Command Aliases

The system can be configured to recognize particular keystrokes (key combination or sequence) as command aliases. In other words, a keystroke can be set as a shortcut for executing a command. To enable the system to interpret a keystroke as a command, use the Ctrl-V or Esc, Q key combinations before entering the command sequence.
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:

Recalling Previously Entered Commands, page 6-17 Recalling Deleted Entries, page 6-18 Redisplaying the Command Line, page 6-18
Note
To roll back to a previously committed configuration, see the Managing Configuration History and Rollback section on page 5-3.
Recalling Previously Entered Commands

The Cisco IOS XR software records the ten most recent commands issued from the command line in its history buffer. This feature is particularly useful for recalling long or complex commands or entries, including access lists. To recall commands from the history buffer, use one of the commands or key combinations listed in Table 6-6.
6-17
Chapter 6 Key Combinations
Table 6-6
Command History
Command or Key Combination Ctrl-P or the up arrow key Ctrl-N or the down arrow key
Purpose Recalls commands in the history buffer, beginning with the most recent command. Repeat the key sequence to recall successively older commands. Returns to more recent commands in the history buffer after recalling commands with Ctrl-P or the up arrow key. Repeat the key sequence to recall successively more recent commands.
Recalling Deleted Entries

The Cisco IOS XR CLI also stores deleted commands or keywords in a history buffer. The buffer stores the last ten items that have been deleted using Ctrl-K, Ctrl-U, or Ctrl-X. Individual characters deleted using Backspace or Ctrl-D are not stored. Table 6-7 identifies the keystroke combinations used to recall deleted entries to the command line.
Table 6-7 Keystroke Combinations to Recall Deleted Entries
Command or Key Combination Ctrl-Y Esc, Y
Recalls the Most recent entry in the buffer (press the keys simultaneously). Previous entry in the history buffer (press the keys sequentially).
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.
Redisplaying the Command Line

If the system sends a message to the screen while a command is being entered, the current command line entry can be redisplayed using the Ctrl-L or Ctrl-R key combination.
Key Combinations
The following sections provide information on key combinations:

Key Combinations to Move the Cursor, page 6-19 Keystrokes to Control Capitalization, page 6-19 Keystrokes to Delete CLI Entries, page 6-20
6-18
Chapter 6
CLI Tips, Techniques, and Shortcuts Key Combinations
Key Combinations to Move the Cursor

Table 6-8 shows the key combinations or sequences you can use to move the cursor around on the command line to make corrections or changes. When you use cursor control keys, consider the following guidelines:
Table 6-8
Ctrl indicates the Control key, which must be pressed simultaneously with its associated letter key. Esc indicates the Escape key, which must be pressed first, followed by its associated letter key. Keys are not case sensitive.
Key Combinations Used to Move the Cursor
Keystrokes Left arrow or Ctrl-B
Function Back character
Moves the Cursor One character to the left.When you enter a command that extends beyond a single line, you can press the left arrow or Ctrl-B keys repeatedly to scroll back toward the system prompt and verify the beginning of the command entry, or you can press the Ctrl-A key combination. One character to the right. Back one word. Forward one word. To the beginning of the line. To the end of the command line.
Right arrow or Ctrl-F Esc, B Esc, F Ctrl-A Ctrl-E
Forward character Back word Forward word Beginning of line End of line
Keystrokes to Control Capitalization

Letters can be capitalized or uncapitalized using simple key sequences. Table 6-9 describes the keystroke combinations used to control capitalization.
Note
Cisco IOS XR commands are generally case insensitive and typically all in lowercase.
Table 6-9
Keystrokes Used to Control Capitalization
Keystrokes Esc, C Esc, L Esc, U
Purpose Capitalizes the letter at the cursor. Changes the word at the cursor to lowercase. Capitalizes letters from the cursor to the end of the word.
6-19
Chapter 6 Key Combinations
Keystrokes to Delete CLI Entries

Table 6-10 describes the keystrokes used to delete command line entries.
Table 6-10 Keystrokes for Deleting Entries
Keystrokes Delete or Backspace Ctrl-D Ctrl-K Ctrl-U or Ctrl-X Ctrl-W Esc, D
Deletes The character to the left of the cursor. The character at the cursor. All characters from the cursor to the end of the command line. All characters from the cursor to the beginning of the command line. The word to the left of the cursor. From the cursor to the end of the word.
Transposing Mistyped Characters

To transpose mistyped characters, use the Ctrl-T key combination.
6-20
C H A P T E R
Upgrading and Managing Cisco IOS XR Software

The Cisco IOS XR software is divided into software packages so that you can select which features run on your router. This chapter describes the concepts and tasks necessary to add feature packages, upgrade the active set of packages, roll back to a previously active set of packages, and perform other related package management tasks.
Contents

Overview of Cisco IOS XR Software Packages, page 7-1 Information About Package Management, page 7-7 Package Management Procedures, page 7-15 Cisco IOS XR Software Package Feature List, page 7-46
Overview of Cisco IOS XR Software Packages

The Cisco IOS XR software is divided into software packages so that you can select which features run on your router. Each package contains the components to perform a specific set of router functions, such as routing, security, or Modular Services card support. Bundles are groups of packages that can be downloaded as a set. For example, the Unicast Routing Core Bundle provides six packages for use on every router. Adding a package to the router does not affect the operation of the router: it only copies the package files to a local storage device on the router, known as the boot device. (such as the internal flash disk0: on a Cisco CRS-1, or the compact flash drive on a Cisco XR 12000 Series Router). To make the package functional on the router, you must activate it for one or more cards. To upgrade a package, you activate a newer version of the package. Once the automatic compatibility checks have passed, the new version will be activated, and the old version will be deactivated. To downgrade a package, you activate an older version of the package. Once the automatic compatibility checks have passed, the older version will be activated, and the newer version will be deactivated. This section contains the following information:

Package Installation Envelopes (PIE Files), page 7-2 Summary of Cisco IOS XR Software Packages, page 7-2 PIE Filenames and Version Numbers, page 7-4
7-1
Chapter 7 Overview of Cisco IOS XR Software Packages
Package Installation Envelopes (PIE Files)

Package Installation Envelopes (PIE), are nonbootable files that can be used to upgrade or add software packages to the router. A PIE file may contain a single package or a set of packages (called a composite package or bundle). Because the files are nonbootable, they must be added and activated on a running router. PIE files have a pie extension. When a PIE file contains software for a specific bug fix, it is called a Software Maintenance Update (SMU).
Note
Files with the vm extension are bootable installation files used only to replace all current Cisco IOS XR software. These files are installed from ROM Monitor mode, which causes significant router downtime. Cisco Systems recommends installing or upgrading software packages only using PIE files as described in this document. For more information on vm files, see Cisco IOS XR ROM Monitor Guide. If the manageability PIE is installed, the entire SONET MIB history is available. If needed, you must configure SNMP and enable the SONET trap.
Summary of Cisco IOS XR Software Packages

Every router includes a basic set of required packages contained in the Cisco IOS XR Unicast Routing Core Bundle. Additional optional packages can be added and activated on the router to provide specific features. This section includes the following information:

Packages in the Cisco IOS XR Unicast Routing Core Bundle, page 7-2 Optional Cisco IOS XR Software Packages, page 7-3 Summary of Cisco IOS XR Software Bundles, page 7-4
Packages in the Cisco IOS XR Unicast Routing Core Bundle

describes the packages contained in the Cisco IOS XR Unicast Routing Core Bundle.
Table 7-1 Packages Included in the Cisco IOS XR Unicast Routing Core Bundle
Name
Description
Operating System (OS) and Kernel, file system, memory management, and other slow changing core Minimum Boot Image components (MBI) Base Administration Routing Forwarding Modular Services card or line card drivers Interface manager, system database, checkpoint services, configuration management, other slow-changing components Resource management: rack, fabric, SDR RIB, BGP, ISIS, OSPF, EIGRP, RIP, RPL FIB, ARP, QoS, ACL, and other components MSC or line card drivers
7-2
Chapter 7
Upgrading and Managing Cisco IOS XR Software Overview of Cisco IOS XR Software Packages
The filename for this bundle is:

Filename for Cisco CRS-1 Routers: comp-hfr-mini.pie-version Filename for Cisco XR 12000 Series Routers: c12k-mini.pie-version.
See Cisco IOS XR Software Package Feature List, page 7-46 for additional information on the specific features provided by each package.
Optional Cisco IOS XR Software Packages

Table 7-2 describes the optional packages that can be activated individually.
Table 7-2 Optional Cisco IOS XR Software Packages
Name Manageability MPLS Multicast Security Session Border Controller Diagnostics
Description Support for HTTP, XML, SNMP and other management tools. Support for Multiprotocol Label Switching (MPLS). Support for multicast protocols. Support for Secure Sockets Layer (SSL), certificates and other security tools. Support for border management services for control and management of real-time multimedia traffic (Cisco XR 12000 Series Routers only). Support for testing and verifying hardware functionality while connected to a live network, helping ensure high availability.
Software Maintenance Updates

An SMU is a PIE file that contains fixes for a specific defect. A composite SMU is a PIE file that contains SMUs for more than one package. SMUs are added and activated using the same procedures as other PIE files. SMUs are created to respond to immediate issues and do not include new features. Typically, SMUs do not have a large impact on router operations. SMU versions are synchronized to the package major, minor, and maintenance versions they upgrade. SMUs are not an alternative to maintenance releases. They provide quick resolution of immediate issues. All bugs fixed by SMUs are integrated into the maintenance releases. For information on available SMUs, contact the TAC, as described in the Obtaining Technical Assistance section on page xvii.
7-3
Summary of Cisco IOS XR Software Bundles

The Cisco IOS XR Software packages are provided in the feature bundles listed in Table 7-3. These packages are described in the sections that follow.
Table 7-3 Cisco IOS XR Software Bundles
Package Session Border Controller X X
Management
Bundle Cisco IOS XR Unicast Routing Core Bundle Cisco IOS XR IP/MPLS Core Software (Releases 3.2.0 and later) Cisco IOS XR IP/MPLS Core Software with Encryption (Releases 3.2.0 and later)
X X X
X X X
X X X
X X X
X X X
X X X X X X X X X X X X
PIE Filenames and Version Numbers

PIE filenames have two formats: one for composite-package PIEs and one for single-package PIEs. A composite-package file is a PIE file that contains multiple packages.
Note
Hyphens in the filename are part of the filename. Table 7-4 and Table 7-4 show the filenames in Cisco CRS-1 and Cisco XR 12000 Series Routers.
Table 7-4
PIE Filenames for Cisco CRS-1 Routers
Software delivery type Composite (Bundle) PIE Single package PIE Composite SMU
Cisco CRS-1 Router filename comp-platform-composite_name.pie-major.minor.maintenance platform-package_type.-p.pie-major.minor.maintenance comp-platform-composite_name.ddts.pie
Example
comp-hfr-mini.pie-3.3.30
hfr-mgbl-p.pie-3.3.30 comp-hfr-001.CSCec98xxx.pie
7-4
Diagnostics
Forwarding
Multicast
Line Card
Security
Routing
Admin
MPLS
Base
OS
Chapter 7
Upgrading and Managing Cisco IOS XR Software Overview of Cisco IOS XR Software Packages
Table 7-4
PIE Filenames for Cisco CRS-1 Routers (continued)
Software delivery type Single package SMU

Note
Cisco CRS-1 Router filename platform-package_type-major.minor.maintenance.ddts.pie
Example
hfr-base-3.3.30.CSCei4xxx.pi e
*A SMU composite name usually is 001, which means the SMU is the first SMU for that DDTS. In rare cases in which the same DDTS requires multiple composite SMUs, a second composite version number is released as 002. In the previous example, a second composite SMU comp-002.CSCec98766 would be created for DDTS CSCec98766.
Table 7-5
PIE Filenames for Cisco XR 12000 Series Routers
Software delivery type Composite (Bundle) PIE Single package PIE Composite SMU* Single package SMU
Note
Cisco XR 12000 Series Router filename platform-composite_name.pie-major.minor.maintenance platform-package_type.pie-major.minor.maintenance comp-platform-composite_name.ddts.pie platform-package_type-major.minor.maintenance.ddts.pie
Example
c12k-mini.pie-3.3.30 c12k-mpls.pie-3.3.30 comp-c12k-001.CSCec98xxx.pie c12k-base-3.3.30.CSCei45xxx.pi e
*A SMU composite name usually is 001, which means the SMU is the first SMU for that DDTS. In rare cases in which the same DDTS requires multiple composite SMUs, a second composite version number is released as 002. In the previous example, a second composite SMU comp-002.CSCec98766 would be created for DDTS CSCec98766.
Filename Component Description

The filename components for all packages are described in Table 7-6.
Table 7-6 Composite- and Single-Package Filename Components
Component comp platform
Description The comp prefix indicates that the file is a composite of multiple packages. Identifies the platform for which the software package is designed.

For packages designed for CRS-1 routers, the platform designation is hfr. For packages designed for Cisco XR 12000 Series Router, the platform designation is c12k. The only composite PIE file at this time is named mini and includes all packages described in the Cisco IOS XR Unicast Routing Core Bundle (see the Summary of Cisco IOS XR Software Bundles section on page 7-4).
composite_name
Identifies a specific composite package.
7-5
Table 7-6
Composite- and Single-Package Filename Components (continued)
Component package_type
Description Identifies the type of package the file supports (package_type applies only to single-package PIEs). Package types include:

fwdg for the Forwarding package lc for the Line Card package mcast for the Multicast package mgbl for the Manageability package mpls for the MPLS package k9sec for the Security package rout for the Routing package diags for the Diagnostics package sbc for the Session Border Controller package A major release occurs when there is a major architectural change to the product (for example, a major new capability is introduced). All packages operating on the router must be at the same major release level. A major release is the least frequent release and may require a router reboot. A minor release contains one or more of the following:
New features Bug fixes
major
Identifies the major release of this package.

minor
Identifies the minor release of this package.
The minor release version does not have to be identical for all software packages operating on the router, but the operating packages must be certified by Cisco as compatible with each other. A minor release may require a router reboot. A maintenance release contains a collection of bug fixes for a package. The maintenance release version does not have to be identical for all software packages operating on the router, but the major and minor versions of the maintenance release must match those of the package being updated. A maintenance release does not usually require a router reboot.
maintenance
Identifies the maintenance release of this package.

ddts
SMUs only. Identifies a Distributed Defect Tracking System (DDTS) number that describes the problem this SMU addresses. DDTS is the method used to track known bugs and the resolutions or workarounds for those issues.
7-6
Chapter 7
Upgrading and Managing Cisco IOS XR Software Information About Package Management
Information About Package Management

This section describes the following concepts for managing Cisco IOS XR software packages:

Overview of Package Management, page 7-7 Managing Software Packages in a Multishelf System, page 7-8 Managing Software Packages in Secure Domain Routers (SDRs), page 7-9 Upgrading Packages, page 7-10 Downgrading Packages, page 7-11 Impact of Package Version Changes, page 7-11 Impact of Package Activation and Deactivation, page 7-11 Controlling install Command Operations, page 7-12 Displaying Installation Log Information, page 7-12
Overview of Package Management

The general procedure for adding optional packages, upgrading a package or package set, or downgrading packages on the router is as follows:
1. 2. 3. 4.
Copy the package file or files to the router or a file server to which the router has access. Add the package or packages to the router using the command install add. Activate the package or packages on the router using the command install activate. Commit the current set of packages using the command install commit.
Figure 7-1 illustrates key steps in the package management process.

Figure 7-1 Process to Add, Activate, and Commit Cisco IOS XR Software Packages
Archive of PIE files Flash disk1: Inactive Software Flash disk0: Install Activate Install Commit Install Deactivate Active Software Configuration Committed Software Configuration
Install Add
TFTP, FTP, or RCP file server
When you are adding an optional package, upgrading a package, or downgrading a package and the package version you want to use is not available on the router, you must copy the appropriate PIE file to the router or a network file server to which the router has access.
116634
7-7
Chapter 7 Information About Package Management
You can place the files on the router by inserting a flash disk with the appropriate files in the slot for flash disk1, or you can copy files to the router using one of several file transfer protocols. Although you can transfer PIE files to flash disk1 or flash disk0, the recommended approach is to store PIE files on flash disk1. By default, flash disk1 serves as the archive for PIE files that are no longer in use or have yet to be added. Flash disk0 serves as the storage location for all files that are ready for activation.
Tip
Before copying PIE files to the router, check to see if the required PIE files are on flash disk1. When the required PIE file is on the router or on an accessible network file server, the next step is to use the install add command to unpack the PIE file and move the package software to flash disk0. On routers with primary and standby RPs, the package is also added to the standby RP so that the standby RP is prepared to take over if the primary RP fails. The add process produces package software that is ready for activation.
Note
The disk that holds the unpacked software files is also known as the boot device. By default, Cisco CRS-1 routers and Cisco XR 12000 Series Routers use flash disk0 as the boot device. To use an alternate storage device, such as flash disk1, refer to the Router Recovery with ROM Monitor chapter of the Cisco IOS XR ROM Monitor Guide. Remember that all RPs in a system must use the same boot device. If the boot device on the primary RP is flash disk0, then the standby RP must also have a flash disk0. When you activate a software package with the install activate command, the router starts using the package version you have activated. If you are activating an optional package that has not been previously activated, the package is activated on all cards. If you are activating a newer (upgrade) or an older (downgrade) version of a previously activated package, you can choose to activate the package on all cards or on specific cards. When a package is activated during an upgrade or a downgrade, the previously active package version is deactivated. The final step in adding, upgrading, or downgrading a package is to commit the current set of packages to the router configuration. When a router is reloaded, it loads the last committed set of packages. If different packages have been activated and not committed, those packages are not loaded. To ensure that recently activated packages become part of the committed package set, enter the install commit command. Although the term commit sounds final, the Cisco IOS XR software provides the flexibility to roll back the selected package set to previously saved package sets. Each time a package is activated or deactivated, a rollback point is created that defines the package set that is active after the package activation or deactivation. The software also creates a rollback point for the last committed package set. If you find that you prefer a previous package set over the currently active package set, you can use the install rollback command to make a previously active package set active again.
Managing Software Packages in a Multishelf System

Adding and activating Cisco IOS XR software packages in a multishelf system is the same as in a single-shelf system. Software packages and related configurations are synchronized throughout a multishelf system by the DSC using the Ethernet control network, as shown in Figure 7-2. The DSC maintains an inventory of the packages, versions, and configurations for each node in the system. Whenever a chassis comes on line, the DSC verifies that the software configuration for that chassis is correct and downloads any required packages and configurations. The active RP in each chassis then distributes and manages the software and configurations for the cards and equipment in that chassis.
7-8
Chapter 7
Figure 7-2
DSC in a CRS-1/M-F1 Multishelf System
Gigabit Ethernet Control Bus
Fabric Cards
SC
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
INPUT OK
FAN OK
OUTPUT FAIL
Catalyst 6509 Switches
Fabric Cards
SC
DSC
Fabric Card Chassis Rack F0
Managing Software Packages in Secure Domain Routers (SDRs)

Software packages are added to the boot device (usually disk0) of the DSC. Once added, a package can be activated for all SDRs in the system, or for a specific SDR.
Note
In Release 3.3, SDR-specific activation is supported for specific packages and upgrades, such as optional packages and SMUs. Packages that do not support SDR-specific activation can only be activated for all SDRs in the system. See the release notes for the software package release for more information. See also the Software Package Management Commands on Cisco IOS XR Software module of Cisco IOS XR System Management Command Reference and the Configuring Secure Domain Routers on Cisco IOS XR Software module of Cisco IOS XR System Management Configuration Guide.

To access install commands, you must be a member of the root-system user group with access to the Administration EXEC mode. Most show install commands can be used in the EXEC mode of an SDR to view the details of the active packages for that SDR.
138118
7-9
Default Software Profile for SDRs

When a new non-owner SDR is created, the nodes assigned to that SDR are activated with the default software profile. In Release 3.3, the default profile is defined by the last install operation that did not specify an SDR. To view the default software profile, use the show install active summary command in Administration EXEC mode. Any new nodes that are configured to become a part of an SDR will boot with the default software profile listed in the output of this command.
RP/0/0/CPU0:router(admin)# show install active summary Default Profile: SDRs: Owner sdr1 Active Packages: disk0:c12k-sbc-3.3.0 disk0:c12k-diags-3.3.0 disk0:c12k-mgbl-3.3.0 disk0:c12k-mcast-3.3.0 disk0:c12k-mpls-3.3.0 disk0:c12k-k9sec-3.3.0 disk0:c12k-mini-3.3.0
Upgrading Packages
To upgrade a package that is currently active on the router, add and activate a newer version of the same package (see Figure 7-3). The older version of the software package is deactivated automatically. These actions are permitted only after the package compatibility checks and API version compatibility checks have passed. Deactivated packages are not removed from the router. To remove inactive package files, use the install remove command. See the Deactivating and Removing Cisco IOS XR Software Packages section on page 7-38 for more information.
Caution
Upgrading or downgrading a software package can cause a process to restart or a new process to start. Use the test option to preview the impact of the package activation.
Figure 7-3 Example of a Maintenance Release Package Upgrade
MPLS 2.0.0 Routing 2.0.0 Forwarding 2.0.0 Base 2.0.0
MPLS 2.0.0 Routing 2.0.1 Forwarding 2.0.0 Base 2.0.0

116630
7-10
Chapter 7
Downgrading Packages
To downgrade a software package, activate an older version on one or more cards for which that package is already active. The newer version of the same software package is deactivated automatically. These actions are performed only after the package compatibility checks and API version compatibility checks have passed. Deactivated packages are not removed from the router. To remove inactive package files, use the install remove command. See the Deactivating and Removing Cisco IOS XR Software Packages section on page 7-38 for more information.
Impact of Package Version Changes

Each package upgrade has a different impact on the operation of the router, depending on the type of package and whether the upgrade is for a major, minor, or maintenance release. The following resources can provide more information on the impact of a package version change:

See the PIE Filenames and Version Numbers section on page 7-4 for more information on the typical impact for major, minor, and maintenance releases. For specific information regarding the impact of an upgrade, consult the release notes for the package release, and test the impact of the package activation by adding the test option to the install activate command. The IOS XR Software Selector tool also contains information on package version compatibility. See the Obtaining and Placing Cisco IOS XR Software section on page 7-16 for information regarding online compatibility resources.
Impact of Package Activation and Deactivation

Activation or deactivation of a package can have an immediate impact on the system. The system can be affected in the following ways:

When a new package is activated, any new CLI commands for the package are added to the SDRs impacted by the new software. The router need not be restarted or reloaded. When a package is deactivated, the commands associated with the features being deactivated are removed from any SDR impacted by the operation. The commands are no longer available to the user. During a software package deactivation, upgrade, or downgrade, any incompatible configurations are removed from the running configuration of any SDR impacted by the operation, and saved to a file. Incompatible configurations are those configurations that are not supported by the new version of the software package.
Note
You must address any issues that result from the revised configuration and reapply the configuration, if necessary.

New processes may be started. Running processes may be stopped or restarted. All processes in the cards may be restarted. Restarting processes in the cards is equivalent to a soft reset.
7-11
The cards may reload. No impact: no processes in the card are affected.
Tip
When activating and deactivating packages, use the test option to test the effects of a command without impacting the running system. After the activation or deactivation process completes, enter the show install log command to display the process results.
Controlling install Command Operations

The install command is used in different forms to perform many package management tasks, such as adding and activating packages. Only one install command can run at a time.
Delaying the return of the CLI prompt
By default, the CLI prompt is returned to the screen before the installation operation is complete, which allows you to enter other noninstall commands. If additional installation requests are attempted before the first operation is complete, they are not executed. To delay the return of the CLI prompt until an installation operation is complete, enter the install command with the synchronous option. For example: install add disk1:pie-file synchronous install activate disk0:package synchronous To determine if an install command is currently running, enter the show install request command.
Displaying Installation Log Information

The install log provides information on the history of the install operations. Each time an install operation is run, a number is assigned to that operation. Table 0-1 summarizes the commands used to view the install log.

Use the show install log command to display information about both successful and failed install operations. The show install log command with no arguments displays a summary of all installation operations. Specify the request-id argument to display details for a specific operation. Use the detail or verbose keywords to display detailed information, including file changes, nodes that could be reloaded, impact to processes, and impact to dynamic link libraries (DLL).
Tip
By default, the install log stores up to fifty (50) entries. Use the install log-history size command to reset the number of entries to any value from 0-255.
Examples
Display install log Entries, page 7-13
7-12
Chapter 7
Display install log Entries

The following example displays information for the install requests. Use the verbose keyword to display detailed information, including files changes, impact to processes, and impact to dynamic link libraries (DLL).
RP/0/RP0/CPU0:router(admin)# show install log verbose Install operation 1 started by user 'labuser' at 17:48:51 UTC Sat Jun 03 2006. install add /disk1:hfr-diags-p.pie-PD34-06.06.07 /disk1:hfr-k9sec-p.pie-PD34-06.06.07 /disk1:hfr-mcast-p.pie-PD34-06.06.07 /disk1:hfr-mgbl-p.pie-PD34-06.06.07 /disk1:hfr-mpls-p.pie-PD34-06.06.07 Install operation 1 completed successfully at 17:51:32 UTC Sat Jun 03 2006. Install logs: Install operation 1 'install add /disk1:hfr-diags-p.pie-PD34-06.06.07 /disk1:hfr-k9sec-p.pie-PD34-06.06.07 /disk1:hfr-mcast-p.pie-PD34-06.06.07 /disk1:hfr-mgbl-p.pie-PD34-06.06.07 /disk1:hfr-mpls-p.pie-PD34-06.06.07' started by user 'labuser' at 17:48:51 UTC Sat Jun 03 2006. Info: The following packages are now available to be activated: Info: Info: disk0:hfr-diags-3.4.0.1I Info: disk0:hfr-k9sec-3.4.0.1I Info: disk0:hfr-mcast-3.4.0.1I Info: disk0:hfr-mgbl-3.4.0.1I Info: disk0:hfr-mpls-3.4.0.1I Info: Install operation 1 completed successfully at 17:51:32 UTC Sat Jun 03 2006. Install operation 2 started by user 'labuser' at 18:06:32 UTC Sat Jun 03 2006. install activate disk0:hfr-diags-3.4.0.1I disk0:hfr-k9sec-3.4.0.1I disk0:hfr-mcast-3.4.0.1I disk0:hfr-mgbl-3.4.0.1I disk0:hfr-mpls-3.4.0.1I Install operation 2 completed successfully at 18:07:48 UTC Sat Jun 03 2006. Summary: Install method: parallel Summary of changes on nodes 0/1/SP, 0/6/SP, 0/SM0/SP, 0/SM1/SP, 0/SM2/SP, 0/SM3/SP: Activated: hfr-diags-3.4.0.1I No processes affected Summary of changes on nodes 0/1/CPU0, 0/6/CPU0: Activated: hfr-diags-3.4.0.1I hfr-mcast-3.4.0.1I hfr-mpls-3.4.0.1I 1 hfr-mpls processes affected (0 updated, 1 added, 0 removed, 0 impacted) 2 hfr-mcast processes affected (0 updated, 2 added, 0 removed, 0 impacted) Summary of changes on nodes 0/RP0/CPU0, 0/RP1/CPU0: Activated: hfr-diags-3.4.0.1I hfr-k9sec-3.4.0.1I hfr-mcast-3.4.0.1I hfr-mgbl-3.4.0.1I hfr-mpls-3.4.0.1I 6 hfr-mgbl processes affected (0 updated, 6 added, 0 removed, 0 impacted) 8 hfr-mpls processes affected (0 updated, 8 added, 0 removed, 0 impacted) 7 hfr-k9sec processes affected (0 updated, 7 added, 0 removed, 0 impacted)
7-13
14 hfr-mcast processes affected (0 updated, 14 added, 0 removed, 0 impacted) Install logs: Install operation 2 'install activate disk0:hfr-diags-3.4.0.1I disk0:hfr-k9sec-3.4.0.1I disk0:hfr-mcast-3.4.0.1I disk0:hfr-mgbl-3.4.0.1I disk0:hfr-mpls-3.4.0.1I' started by user 'labuser' at 18:06:32 UTC Sat Jun 03 2006. Info: The changes made to software configurations will not be Info: persistent across system reloads. Use the command 'admin install Info: commit' to make changes persistent. Info: Please verify that the system is consistent following the Info: software change using the following commands: Info: show system verify --More--
The following example displays information for a specific install request. Use the detail keyword to display additional information, including impact to processes and nodes impacted.
RP/0/RP0/CPU0:router(admin)# show install log 2 detail Install operation 2 started by user 'labuser' at 18:06:32 UTC Sat Jun 03 2006. install activate disk0:hfr-diags-3.4.0.1I disk0:hfr-k9sec-3.4.0.1I disk0:hfr-mcast-3.4.0.1I disk0:hfr-mgbl-3.4.0.1I disk0:hfr-mpls-3.4.0.1I Install operation 2 completed successfully at 18:07:48 UTC Sat Jun 03 2006. Summary: Install method: parallel Summary of changes on nodes 0/1/SP, 0/6/SP, 0/SM0/SP, 0/SM1/SP, 0/SM2/SP, 0/SM3/SP: Activated: hfr-diags-3.4.0.1I No processes affected Summary of changes on nodes 0/1/CPU0, 0/6/CPU0: Activated: hfr-diags-3.4.0.1I hfr-mcast-3.4.0.1I hfr-mpls-3.4.0.1I 1 hfr-mpls processes affected (0 updated, 1 added, 0 removed, 0 impacted) 2 hfr-mcast processes affected (0 updated, 2 added, 0 removed, 0 impacted) Summary of changes on nodes 0/RP0/CPU0, 0/RP1/CPU0: Activated: hfr-diags-3.4.0.1I hfr-k9sec-3.4.0.1I hfr-mcast-3.4.0.1I hfr-mgbl-3.4.0.1I hfr-mpls-3.4.0.1I 6 hfr-mgbl processes affected (0 updated, 6 added, 0 removed, 0 impacted) 8 hfr-mpls processes affected (0 updated, 8 added, 0 removed, 0 impacted) 7 hfr-k9sec processes affected (0 updated, 7 added, 0 removed, 0 impacted) 14 hfr-mcast processes affected (0 updated, 14 added, 0 removed, 0 impacted) Install logs: Install operation 2 'install activate disk0:hfr-diags-3.4.0.1I disk0:hfr-k9sec-3.4.0.1I disk0:hfr-mcast-3.4.0.1I disk0:hfr-mgbl-3.4.0.1I disk0:hfr-mpls-3.4.0.1I' started by user 'labuser' at 18:06:32 UTC Sat Jun 03 2006. Info: The changes made to software configurations will not be Info: persistent across system reloads. Use the command 'admin install
7-14
Chapter 7
Upgrading and Managing Cisco IOS XR Software Package Management Procedures
Info: commit' to make changes persistent. Info: Please verify that the system is consistent following the Info: software change using the following commands: Info: show system verify Info: install verify Install operation 2 completed successfully at 18:07:48 UTC Sat Jun 03 2006.
Package Management Procedures

Review the concepts in the Information About Package Management section on page 7-7 before performing the following tasks. The following sections describe package management tasks:

Activation and Deactivation Prerequisites, page 7-15 Obtaining and Placing Cisco IOS XR Software, page 7-16 Prepare for Software install Operations, page 7-19 Adding and Activating Packages, page 7-27 Committing the Active Package Set, page 7-37 Deactivating and Removing Cisco IOS XR Software Packages, page 7-38 Rolling Back a Previous install Operation, page 7-42
Activation and Deactivation Prerequisites

The following prerequisites must be met for a package to be activated or deactivated.
All cards should be installed and operating properly. For example, you should not activate or deactivate packages while cards are booting, while cards are being upgraded or replaced, or when you anticipate an automatic switchover activity. If a ROM Monitor upgrade is required for the software package, the upgrade must be completed before the package is activated. For ROM Monitor upgrade information and procedures, see Cisco IOS XR ROM Monitor Guide. Although more than one version of a software package can be added to a storage device, only one version of a package can be active for any card. Some packages require the activation or deactivation of other packages. The package being activated must be compatible with the current active software set. In Release 3.3, SDR-specific activation is supported for specific packages and upgrades, such as optional packages and SMUs. Packages that do not support SDR-specific activation can only be activated for all SDRs in the system. For detailed instructions, see the Managing Cisco IOS XR Software Packages module of the Cisco IOS XR Getting Started Guide.
While a software package is being activated, other requests are not allowed to execute on the system. Each CLI install request is assigned a requestID, which can be used later to review the events. Package activation is completed when a message similar to the following appears:
Install operation 2 completed successfully at 20:30:29 UTC Mon Nov 14 2005.
Activation is performed only after the package compatibility checks and API version compatibility checks have passed. If a conflict is found, an on-screen error message is displayed.
7-15
Chapter 7 Package Management Procedures
Obtaining and Placing Cisco IOS XR Software

This section contains information to locate the available software packages, and transfer them to either a local storage device or network server. Once this is done, the package or packages can be added and activated on the router. There are two primary ways to obtain Cisco IOS XR software packages.
Request the software from Cisco on a flash disk that you can insert into the removable flash disk slot (usually flash disk1). Flash disk1 is optional on Cisco CRS-1 routers and on Cisco XR 12000 Series Routers. When it is installed, flash disk1 can be used to store PIE files, which can then be used to add new software to the boot device (usually flash disk0). Download the Cisco IOS XR software packages to a local storage device of the DSC, such as flash disk1, or to a remote server, such as a tftp or rcp server.
The boot device is the local disk on the DSC where Cisco IOS XR software is added and activated. PIE files should not be stored on this boot device.

The default boot device on a Cisco CRS-1 router is disk0. All PIE files should be stored on flash disk1. On the Cisco XR 12000 Series Router, the supported boot devices are disk1 and compact flash.
This section includes the following information:

Locating and Downloading Cisco IOS XR Software, page 7-16 Unpacking Software Bundles (tar Files), page 7-16 Transferring Installation Files from a Network File Server to a Local Storage Device, page 7-17
Locating and Downloading Cisco IOS XR Software

To obtain Cisco IOS XR software, use the Cisco IOS XR Software Selector tool at the following website: http://www.cisco.com/cgi-bin/Software/IOXPlanner/planner-tool/ioxplanner.cgi? The Cisco IOS XR Software Selector tool allows you to browse for your software upgrade from a single interface. You can display and select software by package or bundle name, release, and platform. The tool also includes XML schemas. Choosing a platform, release, or software feature automatically limits the choices based on your selection, until you arrive at your preferred software. After you select the package or bundle you want, platform, and release number, follow the instructions on the web page to download the software you have selected.
Unpacking Software Bundles (tar Files)

If the software you downloaded is in a tar file (which is denoted by a tar filename extension), you must unpack the file before the PIE files can be added to the router. Third-party software programs can unpack tar files and place the Cisco IOS XR software files in a folder you select. For more information on unpacking tar files, see the documentation for the third-party program.
7-16
Chapter 7
Transferring Installation Files from a Network File Server to a Local Storage Device
If the Cisco IOS XR software pie files are located on a remote TFTP, FTP, SFTP, or rcp server, you can copy the files to a local storage device such as disk1. Once the pie files are located on a local storage device, the software packages can be added and activated on the router from that storage device. Table 7-7 describes the supported server protocols, and the CLI syntax used copy files from each server type to the local storage device.
Tip
Cisco IOS XR software pie files can also be added to the router boot device directly from the remote server. See Adding and Activating Packages, page 7-27 for more information.
Note
Consult your system administrator for the location and availability of your network server.
Table 7-7
Download Protocols Supported by Cisco IOS XR Software
Name Trivial File Transfer Protocol
Description TFTP is 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 Cisco IOS XR images may be larger than 32 MB, and the TFTP services provided by some vendors may not support a file this large. If you do not have access to a TFTP server that supports files larger than 32 MB, download the software image using FTP or rcp.
File Transfer Protocol Remote Copy Protocol SSH File Transfer Protocol
FTP is part of the TCP/IP protocol stack and requires a username and password. The rcp protocol uses TCP to ensure the reliable delivery of data, and rcp downloads require a usernames. SFTP is part of the SSHv2 feature in the Security package and provides for secure file transfers. For more information, see the Cisco IOS XR System Security Configuration Guide.
The router commands listed in Table 7-8 show how to copy package files to the router using three types of file transfer protocols.
Table 7-8 Commands for Copying Package Files to the Router
Server Type TFTP
Command and Example The following command syntax is used: copy tftp://hostname_or_ipaddress/directory-path/pie-name disk1: Example:
RP/0/RP0/CPU0:router# copy tftp://10.1.1.1/images/comp-hfr-mini.pie disk1:
7-17
Server Type FTP
Command and Example The following command syntax is used: copy ftp://username:password@hostname_or_ipaddress/directory-path/pie-name disk1: Example:
RP/0/RP0/CPU0:router# copy ftp://john:secret@10.1.1.1/images/comp-hfr-mini.pie disk1:
rcp
The following command syntax is used: copy rcp://username@hostname_or_ipaddress/directory-path/pie-name disk1: Example:

RP/0/RP0/CPU0:router# copy rcp://john@10.1.1.1/images/comp-hfr-mini.pie disk1:
Table 7-9 describes the command variables for copying packages from a network server.
Table 7-9 Command Variables for Copying and Adding Packages from a Network Server
Variable hostname_or_ipaddress pie-name username password directory-path
Description Host name or IP address of the server that stores the source file. Name of the PIE file (package). See the Overview of Cisco IOS XR Software Packages section on page 7-1 for descriptions of the available packages. Required for FTP and rcp only and must be a valid username on the FTP or rcp server. Required for FTP only. If a password is not provided, the networking device accepts anonymous FTP. The specified directory should be a directory under the home directory of the user. In the rcp and FTP examples in Table 7-8, the file being downloaded is in a subdirectory called images in the home directory of the user john.
Note
For FTP and rcp services, directory-path is the directory relative to the username home directory. If you want to specify an absolute path for the directory, you must add a / following the server address.
When the installation files have been transferred to a network file server or the router, you are ready to activate or upgrade the software.
Note
Files with the vm extension are bootable installation files used only to replace all current Cisco IOS XR software. These files are installed from ROMMON and cause significant router downtime. We recommend installing or upgrading software packages using only PIE files, as described in this chapter. See Cisco IOS XR ROM Monitor Guide for information on installing from vm files.
7-18
Chapter 7
Prepare for Software install Operations

Before adding or activating Cisco IOS XR software:

Update the ROM Monitor software, if necessary. Determine if a software change is required. Verify that the new package is supported on your system. Some software packages require that other packages or package versions be activated on a router or SDR, and some packages only support specific cards. Always review the release notes for important information related to that release and to help determine the package compatibility with your router configuration. Verify that the system is stable and prepared for the software changes.
Caution
The ROM Monitor software must be upgraded to version 1.40 or higher on all RPs before a Cisco CRS-1 system is upgraded to Cisco IOS XR Software Release 3.3.1 or higher 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 -xvii. In addition, Cisco CRS-1 Multishelf systems should be upgraded to ROMMON release 1.40 before being upgraded to IOS XR Release 3.3.1 to ensure RPs are assigned the correct rack numbers during system boot. For more information, see Cisco IOS XR ROM Monitor Guide. This section includes instructions to prepare for software install operations.
Note
Activation is performed only after the automatic package compatibility and API version compatibility checks have passed. If a conflict is found, an on-screen error message is displayed.
SUMMARY STEPS
1.
Verify that the ROM Monitor version is correct:

a. admin b. show diag c. Update the ROM Monitor software, if necessary.
2.
Display the currently active software packages and determine if a change is necessary: show install active [sdr sdr-name]
3.
Display package information such as expiration date, package components and compatible cards: show install pie-info device:package [brief | detail | verbose] Verify that there are no corrupted software files: install verify [sdr sdr-name] exit
4.
5.
7-19
6.
Verify the system is stable:

a. show system verify start b. show system verify [start | report | detail]
7.
show clock
DETAILED STEPS
Command or Action
Step 1
Purpose

Verify that the ROM Monitor version is correct:

admin show diag
Enters Administration EXEC mode. In Administration EXEC mode, the show diag command displays the ROM Monitor (ROMMON) software version for all cards in the system. Verify that the correct ROM Monitor software version is installed before upgrading Cisco IOS XR software packages. See Activation and Deactivation Prerequisites, page 7-15 for the required ROM Monitor (ROMMON) software version. Update the ROM Monitor software if necessary. For instructions, see Cisco IOS XR ROM Monitor Guide. Displays the active software for an SDR or for all SDRs. Use this command to determine what software should be added, upgraded or downgraded on the router, and to compare to the active software report after install operations are complete.
To display the active software for all SDRs on the
Example:
RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# show diag
Note
Step 2
show install active [sdr sdr-name]
Example:
RP/0/RP0/CPU0:router(admin)# show install active
router, enter this command in Administration EXEC mode.

To display the active packages for a specific SDR
from Administration EXEC mode, use the sdr sdr-name keyword and argument.
Enter this command in EXEC mode when logged
in to a specific SDR to display information for that SDR only.

Note
You can also display the active packages for a specific node, and view results in detailed or summary mode. See Software Package Management Commands on Cisco IOS XR Software module of the Cisco IOS XR System Management Command Reference for more information.
7-20
Chapter 7
Command or Action
Step 3
show install pie-info device:package [brief|detail|verbose]
Purpose Displays information imbedded in the package. The following keywords provide three levels of information:
Example:
RP/0/RP0/CPU0:router(admin)# show install pie-info disk1:/hfr-mcast-p.pie-3.3.30
brief (default): displays the expiration date of the file, the size, and the installed package name. The expiration date is used for certifying the package. detail: displays the package components, the compatible cards, the expiration date, file size, and the installed package name. verbose: displays information from the detail display and sub-component information. Always review the release notes for the software package for important information related to that release and to help determine the package compatibility with your router configuration.
Note
Step 4
Verify that there are no corrupted software files.

install verify [sdr sdr-name]
Example:
RP/0/RP0/CPU0:router(admin)# install verify
Verifies the consistency of a previously installed software set with the package file from which it originated. This command can be used as a debugging tool to verify the validity of the files that constitute the packages to determine if there are any corrupted files. This command is particularly useful when issued after the activation of a package or upgrading the Cisco IOS XR software to a major release. To perform the command for a specific secure domain router (SDR), use the install verify command with the sdr keyword and sdr-name argument.
Note
The install verify command can take up to two minutes per package to process.
Step 5
exit
Exits Administration EXEC mode and returns to EXEC mode.
Example:
RP/0/RP0/CPU0:router(admin)# exit
7-21
Command or Action
Step 6
Purpose Displays a variety of information including the memory and CPU usage, process status, protocol status, and other status information.

show system verify start show system verify [detail|report]
Example:
RP/0/RP0/CPU0:router# show system verify start RP/0/RP0/CPU0:router# show system verify
To initiate the system status check, enter the show system verify start command. Enter the show system verify or show system verify detail command display system status information.
The detail keyword displays additional
information at the card and processor level, including actual numbers.

The report keyword displays the same information
as the default show system verify command

Note
While most of the output should display the status OK, some processes may show other output, such as Warning. This does not specifically indicate a problem. Contact your Cisco technical support representative for more information on the output of this command.
Step 7
show clock
Verifies that the system clock is correct. Software operations use certificates based on router clock times.
Example:
RP/0/RP0/CPU0:router# show clock
Examples

Verify that the ROM Monitor version is correct, page 7-22 Display the active software for all SDRs or for a specific SDR, page 7-23 Display information about the contents of a PIE file, page 7-24 Verify that there are no corrupted software files., page 7-24 Verify the current system status, page 7-25 Verify that the system clock is correct, page 7-27
Verify that the ROM Monitor version is correct

In the following example, the ROM Monitor software version is displayed in the ROMMON: field for each card.
Note
For instructions to upgrade the ROM Monitor software, see Cisco IOS XR ROM Monitor Guide.
RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# show diag
7-22
Chapter 7
NODE 0/1/SP : MSC(SP) MAIN: board type 500060 800-25021-05 rev B0 dev 079239 S/N SAD09280BS9 PCA: 73-7648-08 rev B0 PID: CRS-MSC VID: V02 CLEI: IPUCAC1BAA ECI: 132502 Board State : IOS XR RUN PLD: Motherboard: 0x0025, Processor: 0xda13, Power: N/A MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193402) [CRS-1 ROMMON] PLIM 0/1/CPU0 : JACKET CARD MAIN: board type 580070 800-23819-03 rev C0 dev N/A S/N SAD094401CR PCA: 73-8982-06 rev C0 PID: CRS1-SIP-800 VID: V01 CLEI: COUIAAMCAA ECI: 134912 Board State : IOS XR RUN PLD: Motherboard: 0x0025, Processor: 0xda13, Power: N/A MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193559) [CRS-1 ROMMON] Interface port config: 0 Ports Optical reach type: Unknown Connector type: MT-P
--More--
Display the active software for all SDRs or for a specific SDR
The following example displays the active packages for all SDRs in the system. Use this information to determine if a software change is required:
RP/0/RP1/CPU0:router(admin)#show install active summary Default Profile: SDRs: Owner CE1b Active Packages: disk0:hfr-diags-3.3.30 disk0:hfr-mgbl-3.3.30 disk0:hfr-k9sec-3.3.30 disk0:comp-hfr-mini-3.3.30
The following example displays a summary of active packages for a specific SDR:
RP/0/RP1/CPU0:router(admin)# show install active summary sdr owner Active Packages: disk0:hfr-diags-3.3.30 disk0:hfr-mgbl-3.3.30 disk0:hfr-k9sec-3.3.30 disk0:comp-hfr-mini-3.3.30
7-23
Display information about the contents of a PIE file

In the following example, information is displayed about the Multicast PIE. This command displays the expiry date of the package, the cards supported by the package, and other details. Use this information to verify the compatibility of the package with your system and other software packages.
Note
A software activation is performed only after the automatic package compatibility and API version compatibility checks have passed. If a conflict is found, an on-screen error message is displayed.
RP/0/RP1/CPU0:router(admin)#show install pie-info disk1:/hfr-mcast-p.pie-3.3.30 detail Contents of pie file '/disk1:/hfr-mcast-p.pie-3.3.30': Expiry date : Jan 19, 2007 02:55:56 UTC Uncompressed size : 9539249 hfr-mcast-3.3.30 hfr-mcast V3.3.30[1I] Multicast Package Vendor : Cisco Systems Desc : Multicast Package Build : Built on Fri Feb 24 08:18:54 UTC 2006 Source : By edde-bld1 in /vws/aga/production/3.3.30/hfr/workspace for c2.95.3-p8 Card(s): RP, DRP, DRPSC, OC3-POS-4, OC12-POS, GE-3, OC12-POS-4, OC48-POS, E3-OC48-POS, E3-OC12-POS-4, E3-OC3-POS-16, E3-OC3C Components in package hfr-mcast-3.3.30, package hfr-mcast: platform-ipv4-mrib V[fwd-33/9] HFR platform dependent DLL for MRIB doc-hfr-mcast V[ci-33/5] Contains the man page documentation for HFR --MORE--

Verifies the consistency of the currently active software against the file from which it originated.
RP/0/RP0/CPU0:router(admin)#install verify Install operation 5 'install verify' started by user 'lab' at 14:06:40 UTC Wed May 10 2006. The install operation will continue asynchronously. RP/0/RP0/CPU0:router(admin)#Info: This operation can take up to 2 minutes. Info: Please be patient. Info: Verify operation successful, no anomalies found. Info: Node 0/1/SP Info: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful. Info: Node 0/1/CPU0 Info: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-mcast-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-mpls-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-lc-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-fwdg-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful. Info: Node 0/6/SP Info: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful. Info: Node 0/6/CPU0 Info: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful.
7-24
Chapter 7
Info: [SUCCESS] /bootflash/hfr-mcast-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-mpls-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-lc-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-fwdg-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful. Info: Node 0/RP0/CPU0 Info: [SUCCESS] /disk0/hfr-mgbl-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-k9sec-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-diags-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-rout-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-mcast-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-mpls-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-lc-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-fwdg-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-admin-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-base-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-os-mbi-3.3.30: Verification Successful. Info: Node 0/RP1/CPU0 Info: [SUCCESS] /disk0/hfr-mgbl-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-k9sec-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-diags-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-rout-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-mcast-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-mpls-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-lc-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-fwdg-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-admin-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-base-3.3.30: Verification Successful. Info: [SUCCESS] /disk0/hfr-os-mbi-3.3.30: Verification Successful. Info: Node 0/SM0/SP Info: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful. Info: Node 0/SM1/SP Info: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful. Info: Node 0/SM2/SP Info: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful. Info: Node 0/SM3/SP Info: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful. Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful. Install operation 5 completed successfully at 14:12:21 UTC Wed May 10 2006.
Verify the current system status

The following example shows how to prepare for system verification:
RP/0/RP1/CPU0:router# show system verify start Storing initial router status ... done.
7-25
The following example shows output from running the show system verify command:
Note
RP/0/RP1/CPU0:router# show system verify Getting current router status ... System Verification Report ========================== - Verifying Memory Usage - Verified Memory Usage - Verifying CPU Usage - Verified CPU Usage Verifying Blocked Processes Verified Blocked Processes Verifying Aborted Processes Verified Aborted Processes Verifying Crashed Processes Verified Crashed Processes
: [OK] : [OK]
: [OK] : [OK] : [OK]
- Verifying LC Status - Verified LC Status - Verifying QNET Status Unable to get current LC status info - Verified QNET Status
: [OK]
: [FAIL]
- Verifying GSP Fabric Status - Verified GSP Fabric Status : [OK] - Verifying GSP Ethernet Status gsp WARNING messages for router Current set of gsp ping nodes does not match initial set of nodes - Verified GSP Ethernet Status : [WARNING] Verifying POS interface Status Verified POS interface Status Verifying TenGigE interface Status Verified TenGigE interface Status
: [OK] : [OK]
- Verifying TCP statistics - Verified TCP statistics : [OK] - Verifying UDP statistics tcp_udp_raw WARNING messages for router UDP Packets sent has not increased during this period. - Verified UDP statistics : [WARNING] - Verifying RAW statistics - Verified RAW statistics : [OK] Verifying RIB Status Verified RIB Status Verifying CEF Status Verified CEF Status Verifying CEF Consistency Status Verified CEF Consistency Status Verifying BGP Status Verified BGP Status Verifying ISIS Status Verified ISIS Status Verifying OSPF Status
: [OK] : [OK] : [OK] : [OK] : [OK]
7-26
Chapter 7
- Verified OSPF Status - Verifying Syslog Messages - Verified Syslog Messages
: [OK]
: [OK]
System may not be stable. Please look into WARNING messages.
Verify that the system clock is correct

The following example displays the current system clock setting:
RP/0/RP1/CPU0:router#show clock 17:30:47.718 UTC Sat Apr 15 2006
Adding and Activating Packages

The procedure in this section describes how to upgrade or add Cisco IOS XR software PIE files that are stored on a local storage device, such as flash disk1, or on a remote TFTP, FTP, SFTP, or rcp server. The PIE software file can include any of the following:

The Cisco IOS XR Unicast Routing Core Bundle (six packages in one composite PIE file) Any of the five optional packages (one package per PIE file) Software Maintenance Updates (SMUs)
When you need to add and activate two or more of the preceding package types, you should add and activate them in the order listed above. For an description of the software management process, see Information About Package Management, page 7-7. These instructions are also used to downgrade software packages. See Downgrading Packages, page 7-11 for more information.
Note
By default, install operations are performed asynchronously: the CLI prompt is returned before the operation is complete, allowing the operator to continue work while the installation is completed in the background. Use the synchronous keyword at the end of install commands to delay the return of the CLI prompt until an installation operation is complete. See Controlling install Command Operations, page 7-12 for more information.
Prerequisites
Before upgrading or adding packages from flash disk1, verify that the following prerequisites have been met:

Verify that the ROM Monitor version is correct. For instructions on upgrading ROM Monitor, see Cisco IOS XR ROM Monitor Guide. All packages to be upgraded or added are present on a local storage device (flash disk1) or a network file server. For more information, see the Obtaining and Placing Cisco IOS XR Software section on page 7-16. Prerequisites for the activation of packages are met as described in the Activation and Deactivation Prerequisites section on page 7-15. Complete the procedures described in Prepare for Software install Operations, page 7-19.
7-27
Summary Steps
1. 2. 3. 4.
Connect to the DSC console port and log in. dir device: admin Add the pie file to the router boot device: install add device:pie-file [activate] or install add tftp://hostname_or_ipaddress/directory-path/pie-file [activate] or install add ftp://username:password@hostname_or_ipaddress/directory-path/pie-file [activate] or install add rcp://username@hostname_or_ipaddress/directory-path/pie-file [activate] show install inactive install activate device:package [sdr sdr-name] [location nodeID] [test] Repeat Steps 4 through 6 until all packages are added and activated. (Optional) show install active (Optional) install verify [sdr sdr-name]
5. 6. 7. 8. 9.
10. (Optional) exit 11. (Optional) Verify the system is stable: a. show system verify start b. show system verify [start | report | detail] 12. (Optional) Commits the current set of packages: a. admin b. install commit 13. Upgrade the field-programmable device (FPD) software, if necessary.
7-28
Chapter 7
Detailed Steps
Command or Action
Step 1
Purpose Establishes a CLI management session with the router. For more information, see the Connecting to the Router Through the Console Port section on page 1-9.
Connect to the DSC console port and log in.
Step 2
dir device:
(Optional) Displays the package files that are available for package upgrades and additions.

Example:
RP/0/RP0/CPU0:router# dir disk1:
Only PIE files can be added and activated using this procedure. For more information on PIE file names, see the PIE Filenames and Version Numbers section on page 7-4.
Step 3
admin
Example:
Places the router in Administration EXEC mode. The install commands are entered in Administration EXEC mode.
Note
Some show install commands can be entered in EXEC mode on an SDR.
7-29
Command or Action
Step 4
install add device:pie-file [activate]
Purpose Unpacks a pie file from local storage device or network server and add the package files to the boot device of the router. The boot device is located on the DSC.

or
install add tftp://hostname_or_ipaddress/directory-path/pie-file [activate]
or
install add ftp://username:password@hostname_or_ipaddress/ directory-path/pie-file [activate]
Replace pie-file with the name of the PIE file you want to add. The activate option automatically activates the software package after it is successfully added. Multiple versions of a software package can be added to the storage device without impacting the running configuration, but only one version of a package can be activated for a card.
or
install add rcp://username@hostname_or_ipaddress/directory-path/ pie-file [activate]
Note
Example:
RP/0/RP0/CPU0:router(admin)# install add disk1:c12k-mgbl.pie-3.3.30.1i
or
RP/0/RP0/CPU0:router(admin)# install add tftp://10.1.1.1/images/hfr-k9sec-p.pie
The following arguments are used when adding a package from a pie file located on a network server.
or
RP/0/RP0/CPU0:router(admin)# install add ftp://john:secret@10.1.1.1/images/hfr-k9sec-p.pie
Replace hostname_or_ipaddress with the host name or IP address of the network file server. Replace directory-path with the network file server path that leads to the PIE file to be added. Replace pie-file with the name of the PIE file you want to add. Replace username with a username that has access privileges to the directory in which the PIE file is stored. Replace password with the password associated with the username that has access privileges to the directory in which the PIE file is stored. The activate option automatically activates the software package after it is successfully added. Multiple versions of a software package can be added to the storage device without impacting the running configuration, but only one version of a package can be activated for a card.
or
RP/0/RP0/CPU0:router(admin)# install add rcp://john@10.1.1.1/images/gsr-k9sec-p.pie
Note
7-30
Chapter 7
Command or Action
Step 5
show install inactive summary [location nodeID]
Purpose (Optional) Displays the inactive packages on the router. Verify that the package added in the previous step appears in the display. To display the inactive packages for a specific card (node), use the location option and specify the node ID. Activates a package that was added to the router boot device.
Example:
RP/0/RP0/CPU0:router# show install inactive summary
Step 6
install activate device:package [sdr sdr-name] [location nodeID] [test]
Example:
RP/0/RP0/CPU0:router(admin)# install activate disk0:c12k-mgbl-3.3.30
Skip this step if the package was activated earlier with the install add command. Replace device:package with the name of the boot device and inactive package, which can be displayed as described in the previous step. Press ? after a partial package name to display all possible matches available for activation. If there is only one match, press [TAB] to fill in the rest of the package name. By default, packages are activated for all cards supported by that package. To activate a package for a specific card (node), use the location option and specify the node ID. To display a list of node IDs for the entire system, enter the show platform command in Administration EXEC mode. A package cannot be activated on a single node unless some version of the package being activated is already active on all nodes. The package being activated must be compatible with the currently active software to operate. When an activation is attempted, the system runs an automatic compatibility check to ensure the package is compatible with the other active software on the router. The activation is permitted only after all compatibility checks have passed. When activating packages, use the test option to test the effects of a command without impacting the running system. After the activation process completes, enter the show install log command to display the process results.
Tip
7-31
Command or Action
Step 7 Step 8
Purpose Activates additional packages as required for your router. (Optional) Displays all active packages.
Repeat Steps 4 through 6 until all packages are activated.

show install active
Example:
RP/0/RP0/CPU0:router# show install active
Use this display to determine if the correct packages are active.
Step 9

Example:
(Optional) Verifies the consistency of a installed software set with the package file from which it originated. This command can be used as a debugging tool to verify the validity of the files that constitute the packages to determine if there are any corrupted files. This command is particularly useful when issued after the activation of a package or upgrading the Cisco IOS XR software to a major release. To perform the command for a specific secure domain router (SDR), use the install verify command with the sdr keyword and sdr-name argument.
Note
Step 10
exit
(Optional) Exits Administration EXEC mode and returns to EXEC mode. Use this command only if you run the show system verify commands, which are entered in EXEC mode.
Example:
7-32
Chapter 7
Command or Action
Step 11
Purpose (Optional) Displays a variety of information including the memory and CPU usage, process status, protocol status, and other status information. Use this information to verify that the system is stable.


Example:
The detail keyword displays
additional information at the card and processor level, including actual numbers.
The report keyword displays the
same information as the default show system verify command

Note
7-33
Command or Action
Step 12
admin install commit
Purpose (Optional) Commits the current set of packages so that these packages are used if the router is restarted.
Note
Example:
RP/0/RP0/CPU0:router(admin)# install commit
This command is entered in Administration EXEC mode.
For more information, see the Committing the Active Package Set section on page 7-37.
Step 13
Upgrade the field-programmable device (FPD) software, if necessary.
Whenever a Cisco IOS XR software image is released that supports SPAs and SIPs, a companion SPA or SIP FPD image is bundled with the Cisco IOS XR software release. However, the FPD image is not automatically upgraded. You must manually upgrade the FPD image running on the SPA or SIP when you upgrade the Cisco IOS XR software image. FPD versions must be compatible with the Cisco IOS XR software that is running on the router. For information on FRDs, including instructions to upgrade FRD images, refer to the Upgrading FPD Cisco IOS XR Software chapter of Cisco IOS XR Interface and Hardware Component Configuration Guide.
Examples

Adding a Package, page 7-34 Activating a Package, page 7-35 Adding and Activating a Package from an FTP File Server with One Command, page 7-35
Adding a Package
The following example shows how to add the contents of a PIE file on disk1 to the boot device on the DSC. Because the software package is added to the boot device by default, it is not necessary to specify the device in the CLI.
RP/0/RP0/CPU0:router(admin)# install add disk1:hfr-mpls-p.pie-3.3.30 synchronous Install operation 4 'install add /disk1:hfr-mpls.pie synchronous' started by user 'cisco' at 18:10:18 UTC Sat Apr 08 2006. Info: The following package is now available to be activated: Info: Info: disk0:hfr-mpls-3.3.80 Info: Install operation 4 completed successfully at 18:14:11 UTC Sat Apr 08 2006.
7-34
Chapter 7
The following example shows how to add the contents of a PIE file on a TFTP server to the boot device on the DSC:
RP/0/RP0/CPU0:router(admin)#install add tftp://209.165.201.1/hfr-mpls.pie synchronous Install operation 4 'install add /tftp://209.165.201.1/hfr-mpls.pie synchronous' started by user 'cisco' at 18:16:18 UTC Sat Apr 08 2006. Info: The following package is now available to be activated: Info: Info: disk0:hfr-mpls-3.3.80 Info: Install operation 4 completed successfully at 18:19:10 UTC Sat Apr 08 2006.
Activating a Package
The following example shows the activation of the MPLS package on a Cisco CRS-1 router. The package is activated on the boot device disk0.
RP/0/RP0/CPU0:router(admin)#install activate disk0:hfr-mpls-3.3.30 synchronous Install operation 15 'install activate disk0:hfr-mpls-3.3.30 synchronous' started by user 'lab' at 19:15:33 UTC Sat Apr 08 2006. Info: The changes made to software configurations will not be persistent Info: across system reloads. Use the command 'admin install commit' to make Info: changes persistent. Info: Please verify that the system is consistent following the software Info: change using the following commands: Info: show system verify Info: install verify Install operation 5 completed successfully at 19:16:18 UTC Sat Apr 08 2006.
Adding and Activating a Package from an FTP File Server with One Command
To add and activate a package with a single command, enter the install add command with the activate keyword. In the following example, the Manageability PIE located on disk1 is verified, unpacked, and added to the boot device disk0. The package is also activated for all SDRs in the system.
RP/0/RP0/CPU0:router(admin)# install add disk1:hfr-mgbl-p.pie-3.3.30 activate Install operation 4 'install add /disk1:hfr-mgbl-p.pie-3.3.30 activate' started by user 'cisco' at 07:58:56 UTC Wed Mar 01 2006. The install operation will continue asynchronously. :router(admin)#Part 1 of 2 (add software): Started Info: The following package is now available to be activated: Info: Info: disk0:hfr-mgbl-3.3.30 Info: Part 1 of 2 (add software): Completed successfully Part 2 of 2 (activate software): Started Info: The changes made to software configurations will not be persistent across system reloads. Use the command 'admin install Info: commit' to make changes persistent. Info: Please verify that the system is consistent following the software change using the following commands: Info: show system verify Info: install verify Part 2 of 2 (activate software): Completed successfully Part 1 of 2 (add software): Completed successfully Part 2 of 2 (activate software): Completed successfully Install operation 4 completed successfully at 08:00:24 UTC Wed Mar 01 2006.
7-35
Displaying the Active Packages

The following example displays a summary of the active packages on a router. By default, the active packages for all SDRs are displayed.
RP/0/RP0/CPU0:router(admin)#show install active summary Default Profile: SDRs: Owner CE1b Active Packages: disk0:hfr-diags-3.3.30 disk0:hfr-mgbl-3.3.30 disk0:hfr-k9sec-3.3.30 disk0:comp-hfr-mini-3.3.30
You can also display the active packages for a specific SDR, or for a specific node. To display the packages contained in the Cisco IOS XR Unicast Routing Core Bundle, enter the show install active command without the summary keyword:
RP/0/RP0/CPU0:router(admin)# show install active SDR Owner RP/0/RP0/CPU0:router(admin)#s how install active sdr owner Node 0/1/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm Active Packages: disk0:hfr-diags-3.3.30 disk0:comp-hfr-mini-3.3.30 Node 0/1/CPU0 [LC] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm Active Packages: disk0:hfr-diags-3.3.30 disk0:comp-hfr-mini-3.3.30 Node 0/6/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm Active Packages: disk0:hfr-diags-3.3.30 disk0:comp-hfr-mini-3.3.30 Node 0/6/CPU0 [LC] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm Active Packages: disk0:hfr-diags-3.3.30 disk0:comp-hfr-mini-3.3.30 Node 0/RP0/CPU0 [RP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm Active Packages: disk0:hfr-diags-3.3.30 disk0:hfr-mgbl-3.3.30 disk0:hfr-k9sec-3.3.30 disk0:comp-hfr-mini-3.3.30 --More--
7-36
Chapter 7
Committing the Active Package Set

Committed packages are the active packages that are persistent across router reloads. If you add and activate a package, it remains active until the next system reload. If you commit a package set, all packages in that set remain active across router reloads until the package set is replaced with another committed package set. Before committing a package set, verify that the system is operating correctly and that the router is forwarding packets as expected. To make the current active package set persistent across router reloads, enter the install commit command in Administration EXEC mode. In the following example, the active software packages are committed on a Cisco CRS-1 router:
RP/0/RP0/CPU0:router(admin)# install commit Install operation 16 'install commit' started by user 'lab' at 19:18:58 UTC Sat Apr 08 2006. Install operation 16 completed successfully at 19:19:01 UTC Sat Apr 08 2006.
Note
If the system is reloaded before the current active software is committed with the install commit command, the previously committed software set is used.
Displaying the Committed Package Versions

To view which packages are committed, enter the show install committed command using the following syntax: show install committed [sdr sdr-name] [location node-id] [[detail [sdr sdr-name | location node-id]] [[summary [sdr sdr-name]]
Note
Enter the show install committed command in Administration EXEC mode to display information for the entire system. Use the sdr sdr-name keyword and argument to display information for a specific SDR. Enter the show install committed command in EXEC mode of an SDR to display information for that SDR. For more information on the command options, see Cisco IOS XR System Management Command Reference. In the following example, the committed packages are shown:
RP/0/RP0/CPU0:router# show install committed Secure Domain Router: Owner Node 0/1/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm Committed Packages: disk0:hfr-diags-3.3.30 disk0:comp-hfr-mini-3.3.30 Node 0/1/CPU0 [LC] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm Committed Packages: disk0:hfr-diags-3.3.30 disk0:comp-hfr-mini-3.3.30
7-37
Node 0/6/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm Committed Packages: disk0:hfr-diags-3.3.30 disk0:comp-hfr-mini-3.3.30 Node 0/6/CPU0 [LC] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm Committed Packages: --More--
As with the show install active command, the show install committed command may display a composite package that represents all packages in the Cisco IOS XR Unicast Routing Core Bundle.
Deactivating and Removing Cisco IOS XR Software Packages

When a package is deactivated, it is no longer active on the router, but the package files remain on the router. The package files can be reactivated later, or they can be removed from the router. A package is deactivated using the following methods:

When a newer version of a package is activated, the earlier version of the package is automatically deactivated. See Adding and Activating Packages, page 7-27 for instructions. To downgrade a package, activate the older version. The newer package version will be deactivated automatically. See Adding and Activating Packages, page 7-27 for instructions. Use the install deactivate command to deactivate a package. This command to turn off the package features for a card or card type.
Restrictions

Packages can be removed only if they are deactivated from all cards in all SDRs. A package cannot be deactivated if that package is required by another active package. When a deactivation is attempted, the system runs an automatic check to ensure that the package is not required by other active packages. The deactivation is permitted only after all compatibility checks have passed. Router reloads: If the deactivation requires a router reload, a confirmation prompt appears. Use the install deactivate command with the noprompt keyword to automatically ignore any reload confirmation prompts and proceed with the package deactivation. The router reloads if required. Node reloads: If a software operation requires a node reload, the configuration register for that node should be set to autoboot. If the config-register for the node is not set to autoboot, then the system automatically changes the setting and the node reloads. A message describing the change is displayed. FPD versions must be compatible with the Cisco IOS XR software that is running on the router; if an incompatibility exists between an FPD version and the Cisco IOS XR software, the device with the FPGA may not operate properly until the incompatibility is resolved. For information on FRDs, including instructions to upgrade FRD images, refer to the Upgrading FPD Cisco IOS XR Software chapter of Cisco IOS XR Interface and Hardware Component Configuration Guide.
7-38
Chapter 7
Summary Steps
1. 2. 3. 4. 5. 6.
admin install deactivate device:package [sdr sdr-name] [location node-id] [test] (Optional) show install inactive summary (Optional) install verify [sdr sdr-name] (Optional) exit (Optional) Verify the system is stable:
a. show system verify start b. show system verify [start | report | detail]
7.
(Optional) Commits the current set of packages:

a. admin b. install commit
8.
(Optional) install remove {[device:package] [inactive [device]]} [test]
Detailed Steps
Command or Action
Step 1
admin
Purpose Enters Administration EXEC mode.
Example:
Step 2
install deactivate device:package [sdr sdr-name] [location node-id] [test]
Deactivates a package for all SDRs, or for a specific SDR. Press ? after a partial package name to display all possible matches available for deactivation. If there is only one match, press [TAB] to fill in the rest of the package name. To deactivate a package only for a specific SDR, use the SDR keyword and sdr-name argument. When a package is deactivate for an SDR, a notification message appears on the console for that SDR with information on the impact of the deactivation. Use the location node-id keyword and argument to deactivate the package for a specific node, if supported.
Example:
RP/0/RP1/CPU0:router(admin)# install deactivate disk0:hfr-diags-3.3.30
Step 3
show install inactive summary
(Optional) Displays a summary of the inactive packages.
Example:
RP/0/RP1/CPU0:router(admin)# show install inactive summary
7-39
Command or Action
Step 4
Purpose (Optional) Verifies the consistency of a installed software set with the package file from which it originated. This command can be used as a debugging tool to verify the validity of the files that constitute the packages to determine if there are any corrupted files. This command is particularly useful when issued after the activation of a package or upgrading the Cisco IOS XR software to a major release. To perform the command for a specific secure domain router (SDR), use the install verify command with the sdr keyword and sdr-name argument.
Note

Example:
Step 5
exit
(Optional) Exits Administration EXEC mode and returns to EXEC mode. Use this command only if you run the show system verify commands, which are entered in EXEC mode. (Optional) Displays a variety of information including the memory and CPU usage, process status, protocol status, and other status information. Use this information to verify that the system is stable.

Example:
Step 6

Example:
The detail keyword displays additional
information at the card and processor level, including actual numbers.

The report keyword displays the same information
as the default show system verify command

Note
7-40
Chapter 7
Command or Action
Step 7
admin install commit
Purpose (Optional) Commits the current set of packages so that these packages are used if the router is restarted. Packages can only be removed if the deactivation operation is committed.
Note
Example:
RP/0/RP1/CPU0:router(admin)# install commit
This command is entered in Administration EXEC mode.
For more information, see the Committing the Active Package Set section on page 7-37.
Step 8
install remove {[device:package] [inactive [device]]} [test]
(Optional) Removes the inactive package.
Only inactive packages can be removed from the router. Packages can be removed only if they are deactivated from all cards in all SDRs. The package deactivation must be committed. Enter the command install remove inactive to remove all inactive packages. Specify a specific package with the device:package keyword and argument.
Example:
RP/0/RP1/CPU0:router(admin)# install remove disk0:hfr-diags-3.3.30
Examples
In the following example, the a package is deactivated from the router, the changes are committed, and the inactive package is removed from the router:

Deactivate the Package, page 7-41 Commit the Active Software Set, page 7-42 Display the Inactive Packages, page 7-42 Remove the Inactive Package from the Router, page 7-42
Deactivate the Package

RP/0/RP1/CPU0:router(admin)# install deactivate disk0:hfr-diags-3.3.30 Install operation 27 'install deactivate disk0:hfr-diags-3.3.30' started by user 'lab' at 23:29:37 UTC Sat Apr 15 2006. The install operation will continue asynchronously. RP/0/RP1/CPU0:router(admin)#Info: The changes made to software configuration Info: across system reloads. Use the command 'admin install commit' to make Info: changes persistent. Info: Please verify that the system is consistent following the software Info: change using the following commands: Info: show system verify Info: install verify Install operation 27 completed successfully at 23:30:22 UTC Sat Apr 15 2006.
7-41
Commit the Active Software Set

RP/0/RP1/CPU0:router(admin)# install commit Install operation 29 'install commit' started by user 'lab' at 23:39:21 UTC Sat Apr 15 2006. Install operation 29 completed successfully at 23:39:24 UTC Sat Apr 15 2006.
Display the Inactive Packages

RP/0/RP1/CPU0:router(admin)# show install inactive summary Default Profile: SDRs: Owner Inactive Packages: disk0:hfr-diags-3.3.30
Remove the Inactive Package from the Router

The following example shows how to remove an inactive package. In this example, the operation is run in test mode. The operation is confirmed and the package is removed.
RP/0/RP1/CPU0:router(admin)# install remove disk0:hfr-diags-3.3.30 test Install operation 30 'install remove disk0:hfr-diags-3.3.30 test' started by user 'lab' at 23:40:22 UTC Sat Apr 15 2006. Warning: No changes will occur due to 'test' option being specified. The Warning: following is the predicted output for this install command. Info: This operation will remove the following package: Info: disk0:hfr-diags-3.3.30 Info: After this install remove the following install rollback points will Info: no longer be reachable, as the required packages will not be present: Info: 4, 9, 10, 14, 15, 17, 18 Proceed with removing these packages? [confirm] y
The install operation will continue asynchronously. Install operation 30 completed successfully at 23.
Rolling Back a Previous install Operation

The roll back process returns the active software to a previous version. This section includes the following information:

Displaying Rollback Points, page 7-43 Display the Package Versions Associated With a Rollback Point, page 7-43 Rolling Back to the Last Committed Package Set, page 7-44 Rolling Back to a Specific Rollback Point, page 7-45
7-42
Chapter 7
Displaying Rollback Points

A rollback point is created every time a software package set is committed. Beginning with Release 3.3, you can roll back the router to previously committed rollback points. For example, if you committed a package set and later committed a different package set, you can roll back the software to use the previously committed package set.
Note
Rollback operations are performed for the entire router, not a specific SDR. This command can only be run from Administration EXEC mode. To display the eligible rollback points, enter the show install rollback ? command as follows:
RP/0/RP1/CPU0:router(admin)# show install rollback ? RP/0/RP0/CPU0:router(admin)#show install rollback ? 0 ID of the rollback point to show package information for 2 ID of the rollback point to show package information for
In this example, the rollback points are 0 and 2.
Display the Package Versions Associated With a Rollback Point

To display the package versions associated with one of these rollback points, enter the show install rollback command using the following syntax: show install rollback rollbackPoint [detail] [location nodeID]
Note
For more information on the command options, see Cisco IOS XR System Management Command Reference. The following example shows how to display the packages that would become active if the software was rolled back to rollback point 2:
RP/0/RP0/CPU0:router(admin)# show install rollback 2 Secure Domain Router: Owner Node 0/1/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Rollback Packages: disk0:hfr-diags-3.3.84 disk0:comp-hfr-mini-3.3.84 Node 0/1/CPU0 [LC] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/lc/mbihfr-lc.vm Rollback Packages: disk0:hfr-diags-3.3.84 disk0:comp-hfr-mini-3.3.84 Node 0/RP0/CPU0 [RP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/mbihfr-rp.vm Rollback Packages: disk0:hfr-diags-3.3.84 disk0:hfr-mgbl-3.3.84 disk0:hfr-k9sec-3.3.84 disk0:comp-hfr-mini-3.3.84
7-43
Node 0/RP1/CPU0 [RP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/mbihfr-rp.vm Rollback Packages: disk0:hfr-diags-3.3.84 disk0:hfr-mgbl-3.3.84 disk0:hfr-k9sec-3.3.84 disk0:comp-hfr-mini-3.3.84 Node 0/SM0/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Rollback Packages: disk0:hfr-diags-3.3.84 disk0:comp-hfr-mini-3.3.84 Node 0/SM1/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Rollback Packages: disk0:hfr-diags-3.3.84 disk0:comp-hfr-mini-3.3.84 Node 0/SM2/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Rollback Packages: disk0:hfr-diags-3.3.84 disk0:comp-hfr-mini-3.3.84 Node 0/SM3/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Rollback Packages: disk0:hfr-diags-3.3.84 disk0:comp-hfr-mini-3.3.84
Rolling Back to the Last Committed Package Set

To roll back to the last committed package set, enter the install rollback to committed command in Administration EXEC mode.
Tip
To display the committed package versions, enter the show install committed command. In the following example, the system is rolled back to the last committed package set:
RP/0/RP1/CPU0:router(admin)# install rollback to committed Install operation 27 'install rollback to committed' started by user 'cisco' at 16:41:38 UTC Sat Nov 19 2005. Info: The rollback to committed software will require a reload of impacted Info: nodes because it is over multiple activation & deactivation Info: operations. Info: This operation will reload the following node: Info: 0/RP1/CPU0 (RP) (SDR: Owner) Info: This operation will reload all RPs in the Owner SDR, and thereby
7-44
Chapter 7
Info: indirectly cause every node in the router to reload. Proceed with this install operation? [confirm] RP/0/RP1/CPU0:router(admin)#Updating Commit Database. Please wait...[OK] Info: The changes made to software configurations will not be persistent Info: across system reloads. Use the command 'admin install commit' to make Info: changes persistent. Info: Please verify that the system is consistent following the software Info: change using the following commands: Info: show system verify Info: install verify Install operation 27 completed successfully at 16:42:23 UTC Sat Nov 19 2005.
Rolling Back to a Specific Rollback Point

The following rules apply when rolling back to an uncommitted rollback point:

If you roll back to the most recent noncommitted rollback point (with the highest number), you do not need to reload the router. You can repeat the rollback process one rollback point at a time without reloading if you always choose the most recent rollback point. If you choose a rollback point that is older than the most recent point, the impacted nodes reload, interrupting data traffic on those nodes. Before the reload occurs, you are prompted to confirm the install rollback operation.
Tip
To display the rollback points, enter the show install rollback ? command. In the following example, the system is rolled back to noncommitted rollback point 8:
RP/0/RP0/CPU0:router(admin)# install rollback to 8 Install operation 10 'install rollback to 8' started by user 'cisco' at 07:49:26 UTC Mon Nov 14 2005. The install operation will continue asynchronously. RP/0/RP0/CPU0:router(admin)#Info: The changes made to software configurations will not be persistent Info: across system reloads. Use the command 'admin install commit' to make Info: changes persistent. Info: Please verify that the system is consistent following the software Info: change using the following commands: Info: show system verify Info: install verify The currently active software is the same as the committed software. Install operation 10 completed successfully at 07:51:24 UTC Mon Nov 14 2005.
7-45
Chapter 7 Cisco IOS XR Software Package Feature List
Cisco IOS XR Software Package Feature List

OS Package Features, page 7-46 Base Package Features, page 7-46 Admin Package Features, page 7-47 Forwarding Package Features, page 7-48 Routing Package Features, page 7-49 Line Card Package Features, page 7-49 Manageability Package Features, page 7-50 Security Package Features, page 7-51 MPLS Package Features, page 7-51 Diagnostics Package, page 7-52 Session Border Controller Package, page 7-53
OS Package Features
The OS package provides the basic operating system and the following features:

1-GB flash DOS FAT file system support Flash disk support Initial system bring up from disk0 QNET QNX flash file system Spinning media support System bring up from disk1 System bring up from ROM Monitor (ROMMON) using TFTP on Cisco CRS-1 routers System bring up from ROM Monitor (ROMMON) using Boothelper and TFTP on Cisco XR 12000 Series Routers
Base Package Features

The Base package provides the basic infrastructure required to boot the router to the CLI prompt and activate software packages. The Base package also provides the following features:

AAA Services BCDL Dependency checker DLL upgrade GSP Hitless software upgrade or downgrade using PIE files Interface manager
7-46
Chapter 7
Upgrading and Managing Cisco IOS XR Software Cisco IOS XR Software Package Feature List
Maintenance and display of counters for each entry in the internal Forwarding Information Base (FIB) Maintenance and display of internal FIB upon user request MD5 or one-way encryption support Netio NetioDLL Restart Network Time Protocol (NTP) configuration and operation Packet manager Password management PFI QSM RADIUS support Rate limiting router addressed and originated packetshardcoded Role-based authorization Scoped restarts Simple Network Management Protocol (SNMP) v1, v2c, and v3 support Support for routing inbound packets using Layer 3 information Support for routing inbound packets using Layer 4 information Support of forwarding to target route processor (RP) and distributed route processor (DRP) SysDBHitless downgrade or upgrade Syslog over IPv4 transport Syslog over IPv6 transport Syslog support TACACS+ support Version manager (including data translator)
Admin Package Features

The Admin package provides the basic software required to manage the router. The Admin package provides the following features:

Admin planesecure domain router (SDR) plane isolation Admin plane support Control Fast Ethernet (FE) support Control Gigabit Ethernet (GE) support DSDRSC election Designated shelf controller (DSC) election Fabric card online insertion and removal (OIR) Fabric manager Fabric plane management
7-47
Fabric statistics Fabric topology management Cisco CRS-1 platform support Cisco XR 12000 Series Router support for Cisco XR 12006, Cisco XR 12010, Cisco XR 12016, Cisco XR 12404, Cisco XR 12406, Cisco XR 12410, and Cisco XR 12416 routers SDR infrastructure SDR plane support Management GE support Owner SDR support
Forwarding Package Features

The Forwarding package provides the following features:

(X) access control lists (ACLs) Quality of service (QoS) and class of service (CoS) using MQC Queueing (ingress and egress) Policing (ingress and egress) Diagnostic and network management support ARP Class-based marking (ingress and egress) for discard class, multicast traffic, EXP, QoS group, v4 DSCP, and v4 precedence CLNS services dCEF support DHCP relay DNS client support FTP client and FTP client support High-level data link control (HDLC) (Cisco) IPv4 IPv6 (excluding IPSec and mobility) Layer 3 loopback, policing (dual-rate, three-color policer and single-rate, three-color policer), load balancing through CEF, and load balancing through CEF (IPv6 forwarding services) MDRR support NTP support with external source PPP support Random Early Detection (RED)based on precedence DSCP EXP Sockets Label Information Base (LIB) support Telnet support
7-48
Chapter 7
TFTP support Trace route support Weighted Random Early Detection (WRED)based on bytes or packets or time
Routing Package Features

The Routing package supports routing protocols (BGP, OSPF, and IS-IS), RIB, and the routing policy engine. The Routing package supports the following features:

MP-BGP v4 OSPFv2 and OSPFv3 IS-IS Static routes Route policy language (RPL) BTSH Conditional route injection (conditional advertisement) Exponential backoff shortest path first (SPF) algorithm support Extended community Filter prefixes on a per-peer basis for inbound and outbound prefix advertisement Graceful restart with NSF (Cisco implementation and IS-IS) MD5 authentication MPLS TE supportintra-area Multipath support for eBGP Multiple RIB table support for AFI and SAFI Name-based community set Next-hop propagation Prioritized RIB update RIB standby capable RIB support redistribution Route dampening Route redistribution Show advertised routes
Line Card Package Features

The Line Card package supports the following features:

Alarms and (performance monitoring) PM Automatic Protection Switching (APS) during line card (LC) failure APS during LC OIR APS and MSP GR-253
7-49
G-783 Annex A/G-841 (no Annex B) Cisco IOS-like APS and MSP Bellcore GR-253 (as applicable) Dynamic mapping of queues to interfaces Hierarchical QoS (on cards that support this) ITU-T G.957 (as applicable) Layer 1 loopback Loopback support (for each subinterface and for each port) OC-192 OC-48 Optical power monitoring Pointer activity monitoring SONET and Synchronous Digital Hierarchy (SDH) alarm recognition and processing SONET and SDH header byte visibility and manipulation SONET and SDH concatenated Standards-compliant SONET and SDH interface Stratum 3 and G.813 clocking Maximum number of egress (CoS) queues as supported by hardware Maximum number of ingress queues as supported by the hardware Maximum number of interfaces as supported by hardware Maximum prefix table size as supported by hardware Synchronization: local (internal) or loop timed (recovered from network); Stratum 3 (4.6 pmm) clock accuracy
Manageability Package Features

The Manageability package supports the following features:

Alarms managementconfiguration, operation, and correlation support Configuration editor and manager Accounting and statistics management Performance management Fault Management Control point and network managementgeneric requirements Terminal services enhancements Enhanced command-line interface (CLI) Extensible markup language (XML) interface and schemas Common Object Request Broker Architecture (CORBA) support MIB support. For a complete list of supported MIBs, go to the following link: http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
7-50
Chapter 7
Security Package Features

The Security package supports the following features:

Client and server support Secure socket layer (SSLSSL V2, SSL V3 and SSL V23) Control packet policing IPSec Client and server support (Secure Shell [SSH] and SFTP) Enhanced password security IPv6 SSH and SFTP MD5 PKI Random number generator Selective packet discard SHTTP support Software authentication SSHv1 and SSHv2 support Transport Layer Security Version 1 (TLSv1) support
MPLS Package Features

The Multiprotocol Label Switching (MPLS) package supports the following features:

MPLS forwarding and load balancing MPLS traffic engineering (MPLS TE) Label distribution protocol (LDP)
LDP core (RFC 3036) (including link and targeted neighbors) LDP graceful restart (draft-ieft-mpls-ldp-graceful-restart02.txt) LDP high availability (HA) (restart automatic switchover) LDP MIBs (draft-ieft-mpls-ldp0mib-08.txt) LDP support for Layer 3 load balancing LDP support on Packet-over-SONET/SDH (POS) interfaces
Resource Reservation Protocol (RSVP)

RSVP authentication, authorization, and accounting (AAA) CLI RSVP core RSVP extensions for OUNI RSVP graceful restart and hellos RSVP HAnonstop forwarding (NSF) and hitless software upgrade RSVP refresh reduction
7-51
UNI
UNI-C AAA CLI UNI-C core UNI-C HANSF and hitless software upgrade UNI-C hierarchical SONET alarms suppression UNI-C line protocol state control UNI-C local path restoration UNI-C node recovery support
LMPstatic configuration Fast reroute (FRR) with link, node, and bandwidth protection XML schema support, configuration, and operation
Multicast Package Features

The Multicast package supports the following features:

Auto-RP and Bootstrap Router (BSR) Bidirectional Protocol Independent Multicast (PIM) Dynamic registration using Internet Group Management Protocol (IGMP) Explicit tracking of hosts, groups, and channels for IGMPv3 MBGP MSDP Multicast NSF Multicast Reverse Path Forwarding (RPF)loose mode Out-of-resource handling PIM-SM PIM-SSM Source Specific Multicast with IGMP v3
Diagnostics Package
Cisco IOS XR online diagnostics allow you to test and verify hardware functionality while connected to a live network. Scheduled diagnostics help ensure system high availability (HA). If a problem is detected, online diagnostics help isolate the location of the problem, allowing you to identify and replace the hardware. Online diagnostics are also used for system acceptance when receiving new hardware. The online diagnostics contain tests that check different hardware components and verify the data path and control signals. Nondisruptive online diagnostic tests provide background health monitoring and can be scheduled or run on demand. On-demand diagnostics run from the command-line interface (CLI); scheduled diagnostics run at user-designated intervals or specified times when the system is connected to a live network.
7-52
Chapter 7
Integrated Field Diagnostics (IFDs) are provided to allow the loading and unloading of offline diagnostic images. Loading a diagnostic image places the specified location out of service. When an offline diagnostic image is loaded, the diagnostic start and diagnostic stop commands are used to control test execution, and the show diagnostic content and show diagnostic results commands are used to show the test list and results. The integrated field diagnostics detect problems in hardware components, including memory (failures that occur over time). For more general information on diagnostics, see Cisco IOS XR Diagnostics. See Cisco IOS XR Interface and Hardware Component Command Reference for diagnostic command information.
Session Border Controller Package

The Session Border Controller (SBC) package provides border management services for Cisco XR 12000 Series Routers. Session Border Controllers controls and manages real-time multimedia traffic flows between IP network borders, handling signaling and media. SBCs perform native IP interconnection functions required for real-time communications, such as access control, NAT/firewall traversal, bandwidth policing, accounting, signaling interworking, legal intercept, and QoS management.
7-53
7-54
C H A P T E R
Managing the Router Hardware

This chapter describes the command-line interface (CLI) techniques and commands used to manage and configure the hardware components of a router running the Cisco IOS XR software.
Contents

Displaying Hardware Status, page 8-1 RP Redundancy and Switchover, page 8-18 DSC Migration on Cisco CRS-1 Multishelf Systems, page 8-23 Reloading, Shutting Down, or Power Cycling a Node, page 8-24 Using Controller Commands to Manage Hardware Components, page 8-27 Formatting Hard Drives, Flash Drives, and Other Storage Devices, page 8-27 Removing and Replacing Cards, page 8-28
Displaying Hardware Status

The following sections describe how to display different types of hardware status information:

Displaying Secure Domain Router Hardware Version Information, page 8-2 Displaying System Hardware Version Information, page 8-4 Displaying the Chassis Serial Numbers (Cisco CRS-1 Routers), page 8-10 Displaying the Configured Chassis Serial Numbers, page 8-10 Displaying Software and Hardware Information, page 8-11 Displaying SDR Node IDs and Status, page 8-12 Displaying Router Environment Information, page 8-15 Displaying RP Redundancy Status, page 8-17
8-1
Chapter 8 Displaying Hardware Status
Displaying Secure Domain Router Hardware Version Information

To display hardware version information for the components assigned to a Secure Domain Router (SDR), connect to the appropriate DSDRSC and enter the show diag command in EXEC mode. The displayed information includes the card serial number and the ROMMON software version. The syntax for the show diag command in EXEC mode is: show diag [nodeID | details | summary]
Note
The show diag command output is different for Cisco CRS-1 routers and Cisco XR 12000 Series Routers. In the following example, the show diag command displays information for all nodes in the SDR:
RP/0/RP0/CPU0:Router# show diag PLIM 0/1/CPU0 : JACKET CARD MAIN: board type 580070 800-23819-03 rev C0 dev N/A S/N SAD094401CR PCA: 73-8982-06 rev C0 PID: CRS1-SIP-800 VID: V01 CLEI: COUIAAMCAA ECI: 134912 Board State : IOS XR RUN PLD: Motherboard: 0x0025, Processor: 0xda13, Power: N/A MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193559) [CRS-1 ROMMON] Interface port config: 0 Ports Optical reach type: Unknown Connector type: MT-P NODE 0/1/0 : 4xOC3 POS SPA MAIN: board type 0440 68-2169-01 rev C0 dev N/A S/N JAB093309PA PCA: 73-9313-04 rev B0 PID: SPA-4XOC3-POS VID: V01 CLEI: IPUIAFNRAA NODE 0/1/5 : 8xGE SPA MAIN: board type 044f 68-2239-01 rev A0 dev N/A S/N SAD0937022J PCA: 73-8557-03 rev A0 PID: SPA-8X1GE VID: V01 CLEI: CNUIAH6AAA
8-2
Chapter 8
Managing the Router Hardware Displaying Hardware Status
PLIM 0/6/CPU0 : JACKET CARD MAIN: board type 580070 800-23819-03 rev C0 dev N/A S/N SAD094203W2 PCA: 73-8982-06 rev C0 PID: CRS1-SIP-800 VID: V01 CLEI: COUIAAMCAA ECI: 134912 Board State : IOS XR RUN PLD: Motherboard: 0x0025, Processor: 0xda13, Power: N/A MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193559) [CRS-1 ROMMON] Interface port config: 0 Ports Optical reach type: Unknown Connector type: MT-P NODE 0/6/0 : 4xOC3 POS SPA MAIN: board type 0440 68-2169-01 rev C0 dev N/A S/N JAB093309MG PCA: 73-9313-04 rev B0 PID: SPA-4XOC3-POS VID: V01 CLEI: IPUIAFNRAA NODE 0/6/4 : 8xOC3/OC12 POS SPA MAIN: board type 0404 68-2164-01 rev 34 dev N/A S/N JAB094706L9 PCA: 73-9941-02 rev 04 PID: SPA-8XOC12-POS VID: V01 CLEI: SOUIAA8BAA NODE 0/6/5 : 8xGE SPA MAIN: board type 044f 68-2239-01 rev A0 dev N/A S/N SAD093909GM PCA: 73-8557-03 rev A0 PID: SPA-8X1GE VID: V01 CLEI: CNUIAH6AAA NODE 0/RP0/CPU0 : RP MAIN: board type 100002 800-22921-10 rev B0 dev 080366, 080181 S/N SAD093507J8 PCA: 73-8564-10 rev B0 PID: CRS-8-RP VID: V01 CLEI: IPUCABWBAA ECI: 129507 Board State : IOS XR RUN PLD: Motherboard: 0x0038, Processor: 0x0038, Power: 0x0000 MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193559) [CRS-1 ROMMON]
8-3
NODE 0/RP1/CPU0 : RP MAIN: board type 100002 800-22921-10 rev B0 dev 080366, 080181 S/N SAD093507JP PCA: 73-8564-10 rev B0 PID: CRS-8-RP VID: V01 CLEI: IPUCABWBAA ECI: 129507 Board State : IOS XR RUN PLD: Motherboard: 0x0038, Processor: 0x0038, Power: 0x0000 MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193559) [CRS-1 ROMMON]
In the following example, the show diag command displays information for a single node:
RP/0/RP0/CPU0:router# show diag 0/RP0/CPU0 NODE 0/RP0/CPU0 : RP MAIN: board type 100002 800-22921-10 rev B0 dev 080366, 080181 S/N SAD093507J8 PCA: 73-8564-10 rev B0 PID: CRS-8-RP VID: V01 CLEI: IPUCABWBAA ECI: 129507 Board State : IOS XR RUN PLD: Motherboard: 0x0038, Processor: 0x0038, Power: 0x0000 MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193559) [CRS-1 ROMMON]
Displaying System Hardware Version Information

To display hardware version information for all or some of the components assigned in a system, connect to the DSC and enter the show diag command in administration EXEC mode. When this command is entered in administration EXEC mode, you can display information on RPs, MSCs or line cards, fabric cards, and system components such as the chassis, fan trays, and power supplies.
Note
If you enter the show diag command in EXEC mode, the software displays only the hardware assigned to the SDR to which you are connected. The syntax for the show diag command in administration EXEC mode is: show diag [nodeID | chassis | details | fans | power-supply | summary]
Tip
For information on the software version, use the show version command.
8-4
Chapter 8
In the following example, the show diag command displays information for all nodes in the system:
RP/0/RP1/CPU0:router(admin)# show diag NODE 0/1/SP : MSC(SP) MAIN: board type 500060 800-25021-05 rev B0 dev 079239 S/N SAD09280BS9 PCA: 73-7648-08 rev B0 PID: CRS-MSC VID: V02 CLEI: IPUCAC1BAA ECI: 132502 Board State : IOS XR RUN PLD: Motherboard: 0x0025, Processor: 0xda13, Power: N/A MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193402) [CRS-1 ROMMON] PLIM 0/1/CPU0 : JACKET CARD MAIN: board type 580070 800-23819-03 rev C0 dev N/A S/N SAD094401CR PCA: 73-8982-06 rev C0 PID: CRS1-SIP-800 VID: V01 CLEI: COUIAAMCAA ECI: 134912 Board State : IOS XR RUN PLD: Motherboard: 0x0025, Processor: 0xda13, Power: N/A MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193559) [CRS-1 ROMMON] Interface port config: 0 Ports Optical reach type: Unknown Connector type: MT-P NODE 0/1/0 : 4xOC3 POS SPA MAIN: board type 0440 68-2169-01 rev C0 dev N/A S/N JAB093309PA PCA: 73-9313-04 rev B0 PID: SPA-4XOC3-POS VID: V01 CLEI: IPUIAFNRAA NODE 0/1/5 : 8xGE SPA MAIN: board type 044f 68-2239-01 rev A0 dev N/A S/N SAD0937022J PCA: 73-8557-03 rev A0 PID: SPA-8X1GE VID: V01 CLEI: CNUIAH6AAA
8-5
NODE 0/6/SP : MSC(SP) MAIN: board type 500060 800-25021-06 rev A0 dev 080229 S/N SAD093702ES PCA: 73-7648-08 rev C0 PID: CRS-MSC VID: V03 CLEI: IPUCAD0BAA ECI: 135786 Board State : IOS XR RUN PLD: Motherboard: 0x0025, Processor: 0xda13, Power: N/A MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193402) [CRS-1 ROMMON] PLIM 0/6/CPU0 : JACKET CARD MAIN: board type 580070 800-23819-03 rev C0 dev N/A S/N SAD094203W2 PCA: 73-8982-06 rev C0 PID: CRS1-SIP-800 VID: V01 CLEI: COUIAAMCAA ECI: 134912 Board State : IOS XR RUN PLD: Motherboard: 0x0025, Processor: 0xda13, Power: N/A MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193559) [CRS-1 ROMMON] Interface port config: 0 Ports Optical reach type: Unknown Connector type: MT-P NODE 0/6/0 : 4xOC3 POS SPA MAIN: board type 0440 68-2169-01 rev C0 dev N/A S/N JAB093309MG PCA: 73-9313-04 rev B0 PID: SPA-4XOC3-POS VID: V01 CLEI: IPUIAFNRAA NODE 0/6/4 : 8xOC3/OC12 POS SPA MAIN: board type 0404 68-2164-01 rev 34 dev N/A S/N JAB094706L9 PCA: 73-9941-02 rev 04 PID: SPA-8XOC12-POS VID: V01 CLEI: SOUIAA8BAA NODE 0/6/5 : 8xGE SPA MAIN: board type 044f 68-2239-01 rev A0 dev N/A S/N SAD093909GM PCA: 73-8557-03 rev A0 PID: SPA-8X1GE VID: V01 CLEI: CNUIAH6AAA
8-6
Chapter 8
NODE 0/RP0/CPU0 : RP MAIN: board type 100002 800-22921-10 rev B0 dev 080366, 080181 S/N SAD093507J8 PCA: 73-8564-10 rev B0 PID: CRS-8-RP VID: V01 CLEI: IPUCABWBAA ECI: 129507 Board State : IOS XR RUN PLD: Motherboard: 0x0038, Processor: 0x0038, Power: 0x0000 MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193559) [CRS-1 ROMMON] NODE 0/RP1/CPU0 : RP MAIN: board type 100002 800-22921-10 rev B0 dev 080366, 080181 S/N SAD093507JP PCA: 73-8564-10 rev B0 PID: CRS-8-RP VID: V01 CLEI: IPUCABWBAA ECI: 129507 Board State : IOS XR RUN PLD: Motherboard: 0x0038, Processor: 0x0038, Power: 0x0000 MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193559) [CRS-1 ROMMON] NODE 0/SM0/SP : FC/S MAIN: board type 400035 800-23168-05 rev B0 dev N/A S/N SAD0933081S PCA: 73-8682-05 rev B0 PID: CRS-8-FC/S VID: V01 CLEI: IPUCABXBAA ECI: 129510 Board State : IOS XR RUN PLD: Motherboard: 0x001e, Processor: 0x0000, Power: N/A MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193402) [CRS-1 ROMMON] NODE 0/SM1/SP : FC/S MAIN: board type 400035 800-23168-05 rev B0 dev N/A S/N SAD09300492 PCA: 73-8682-05 rev B0 PID: CRS-8-FC/S VID: V01 CLEI: IPUCABXBAA ECI: 129510 Board State : IOS XR RUN PLD: Motherboard: 0x001e, Processor: 0x0000, Power: N/A MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193402) [CRS-1 ROMMON]
8-7
NODE 0/SM2/SP : FC/S MAIN: board type 400035 800-23168-05 rev B0 dev N/A S/N SAD09330830 PCA: 73-8682-05 rev B0 PID: CRS-8-FC/S VID: V01 CLEI: IPUCABXBAA ECI: 129510 Board State : IOS XR RUN PLD: Motherboard: 0x001e, Processor: 0x0000, Power: N/A MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193402) [CRS-1 ROMMON] NODE 0/SM3/SP : FC/S MAIN: board type 400035 800-23168-05 rev B0 dev N/A S/N SAD0933081W PCA: 73-8682-05 rev B0 PID: CRS-8-FC/S VID: V01 CLEI: IPUCABXBAA ECI: 129510 Board State : IOS XR RUN PLD: Motherboard: 0x001e, Processor: 0x0000, Power: N/A MONLIB: QNXFFS Monlib Version 3.0 ROMMON: Version 1.38(20050525:193402) [CRS-1 ROMMON] Rack 0: Fan Tray 0 : Fan Tray Upper MAIN: board type 900160 800-23275-05 rev A0 dev N/A S/N TBA09370056 PCA: 0-0-00 rev 00 PID: CRS-8-LCC-FAN-TR VID: V01 CLEI: IPPQAGWJAB ECI: 133434 Fan Tray 1 : Fan Tray Lower MAIN: board type 900160 800-23275-05 rev A0 dev N/A S/N TBA09370055 PCA: 0-0-00 rev 00 PID: CRS-8-LCC-FAN-TR VID: V01 CLEI: IPPQAGWJAB ECI: 133434 Rack 0:
8-8
Chapter 8
Power Supply A : MAIN: board type b00181 341-112-01 rev C0 dev N/A S/N TD109320008 PCA: 0-0-00 rev 00 PID: CRS-8-AC-RECT VID: V01 CLEI: IPP1D0WAAA ECI: 129500 Power Supply B : MAIN: board type b00181 341-112-01 rev C0 dev N/A S/N TD10931000X PCA: 0-0-00 rev 00 PID: CRS-8-AC-RECT VID: V01 CLEI: IPP1D0WAAA ECI: 129500 RACK 0 : MAIN: board type 0001e4 800-23271-04 rev F0 dev 076763 S/N TBA09370035 PCA: 73-8696-03 rev A0 PID: CRS-8-LCC VID: V01 CLEI: IPMEZ10BRA ECI: 446387 RACK NUM: 0
Note
Line cards in Cisco CRS-1 routers are called modular services cards (MSCs). The show diag command output is different for Cisco CRS-1 routers and Cisco XR 12000 Series Routers. In the following example, the show diag command displays information for a single system component:
RP/0/RP1/CPU0:router(admin)# show diag chassis RACK 0 : MAIN: board type 0001e4 800-23271-04 rev F0 dev 076763 S/N TBA09370035 PCA: 73-8696-03 rev A0 PID: CRS-8-LCC VID: V01 CLEI: IPMEZ10BRA ECI: 446387 RACK NUM: 0
8-9
Displaying the Chassis Serial Numbers (Cisco CRS-1 Routers)

Each chassis serial number must be defined during the configuration of multishelf routers. To view the actual serial number for each chassis in the system, enter the command show diag chassis in administration EXEC mode.

The chassis serial numbers are displayed in the Main category for each chassis. The Rack Num field displays the rack number assigned to that serial number.
For example:
RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# show diag chassis RACK 0 : MAIN: board type 0001e0 800-24872 dev 075078 S/N TBA00000001 PCA: 73-7640-05 rev 20 PID: CRS-16-LCC VID: V01 CLEI: IPM6700DRA ECI: 445022 RACK NUM: 0 RACK 1 : MAIN: board type 0001e0 800-24872-01 rev 20 dev 075078 S/N TBA00000002 PCA: 73-7640-05 rev 20 PID: CRS-16-LCC VID: V01 CLEI: IPM6700DRA ECI: 445022 RACK NUM: 1
--MORE--
Displaying the Configured Chassis Serial Numbers

Enter the command show running-config | include dsc in administration EXEC mode to display the serial number configured for each rack number. This command is used to verify that the configuration is correct. The serial numbers displayed are those entered by an operator. If this number if wrong due to an entry error, the number is still displayed, but the DSC does not recognize the chassis.
Note
This command can also be entered in administration configuration mode.
8-10
Chapter 8
For example:
RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# 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)#
Displaying Software and Hardware Information

The show version command displays a variety of system information, including the hardware and software versions, router uptime, boot settings (including the configuration register), and active software. The syntax for the show version command is: show version The following is sample output from the show version command:
RP/0/RP1/CPU0:router# show version Cisco IOS XR Software, Version 3.3.0[2I] Copyright (c) 2006 by cisco Systems, Inc. ROM: System Bootstrap, Version 1.38(20050525:193559) [CRS-1 ROMMON], router uptime is 1 week, 1 day, 17 hours, 1 minute System image file is "disk0:hfr-os-mbi-3.3.0/mbihfr-rp.vm" cisco CRS-8/S (7457) processor with 4194304K bytes of memory. 7457 processor at 1197Mhz, Revision 1.2 16 Packet over SONET/SDH network interface(s) 16 SONET/SDH Port controller(s) 2 Ethernet/IEEE 802.3 interface(s) 16 GigabitEthernet/IEEE 802.3 interface(s) 2043k bytes of non-volatile configuration memory. 38079M bytes of hard disk. 1000592k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes). 1000640k bytes of ATA PCMCIA card at disk 1 (Sector size 512 bytes). Package active on node 0/1/SP: hfr-diags, V 3.3.0[2I], Cisco Systems, at disk0:hfr-diags-3.3.0 Built on Mon Mar 13 12:58:02 UTC 2006 By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8 hfr-admin, V 3.3.0[2I], Cisco Systems, at disk0:hfr-admin-3.3.0 Built on Mon Mar 13 11:46:36 UTC 2006 By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8 hfr-base, V 3.3.0[2I], Cisco Systems, at disk0:hfr-base-3.3.0 Built on Mon Mar 13 11:43:22 UTC 2006 By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8 hfr-os-mbi, V 3.3.0[2I], Cisco Systems, at disk0:hfr-os-mbi-3.3.0 Built on Mon Mar 13 11:27:02 UTC 2006 By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8 --More--
8-11
Displaying SDR Node IDs and Status

In EXEC mode, the show platform command displays information for all nodes assigned to a secure domain router (SDR). For each node, this information includes the host card type, the operational state, and the configuration state. To display information on a single node, enter the command with a node ID. The syntax for the show platform command on Cisco CRS-1 routers is: show platform [nodeID] The syntax for the show platform command on Cisco XR 12000 Series Routers is: show platform The following example displays the status for all nodes in the SDR to which you are connected:
RP/0/RP0/CPU0:router# show platform Node Type PLIM State Config State ----------------------------------------------------------------------------0/0/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/2/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/RP0/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON
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. The nodeID appears in the rack/slot/module notation, and the nodeID components are as follows:

The rack number in a single-shelf system is always 0. In a multishelf system, the line card chassis (LCC) rack number range is 0 to 255 and the FCC rack number range is F0 to F7. The slot is the number of the physical slot in which the card is installed. The module identifies a system hardware component.
Table 8-1 summarizes the nodeID for each type of card in a Cisco CRS-1 system, and Table 8-2 summarizes the nodeID for each type of card in a Cisco XR 12000 Series Router.
Table 8-1 Node ID Components on Cisco CRS-1 Routers
Card Type (the card type to which you are issuing commands) Route processor DRP MSC PLIM Cisco CRS-1 SPA Interface Processor (SIP)-800
Rack (always 0 in a single-shelf system) 0255 0-255 0255 0255 0255
Slot (the physical slot in which the card is installed) RP0 and RP1 07 (8-slot chassis) 015 (16-slot chassis) 07 (8-slot chassis) 015 (16-slot chassis) 07 (8-slot chassis) 015 (16-slot chassis) 07 (8-slot chassis) 015 (16-slot chassis)
Module (the entity on the card that is the target of the command) CPU0 CPU0 or CPU1 Service processor (SP) CPU0 CPU0
8-12
Chapter 8
Table 8-1
Node ID Components on Cisco CRS-1 Routers (continued)
Card Type (the card type to which you are issuing commands) 1-Port OC-192c/STM-64c Packet-over-SONET/SDH (POS) XFP SPA 4-Port OC-3c/STM-1 POS SPA 8-Port Gigabit Ethernet SPA Switch fabric module Alarm cards Fan controller cards
Rack (always 0 in a single-shelf system) 0255
Slot (the physical slot in which the card is installed) 07 (8-slot chassis) 015 (16-slot chassis)
Module (the entity on the card that is the target of the command) 05 (SPA module number on the Cisco CRS-1 SIP-800)
0255 0255 0255
SM0SM3 (8-slot chassis) SM0SM7 (16-slot chassis) AM0AM1 (16-slot chassis) FC0FC1 (16-slot chassis)
SP SP SP
Table 8-2
Node ID Components on Cisco XR 12000 Series Routers
Card Type (the card type to which you are issuing commands) Route processor
Rack (always 0 in a single-shelf system) 0
Slot (the logical slot number reported in command displays) 0151, 2 0151 0151
Module (the entity on the card that executes the commands) CPU0 CPU0 CPU0
Cisco XR 12000 and 12000 Series 0 line cards Cisco XR 12000 and 12000 Series 0 SPA Interface Processor (SIP)-600 0 1-Port 10-Gigabit Ethernet SPA 5-Port Gigabit Ethernet SPA 10-Port Gigabit Ethernet SPA 1-Port OC-192c/STM-64c POS/RPR SPA Clock and scheduler cards (CSCs) 0 0 Switch fabric cards (SFCs) Consolidated switch fabric (CSF) 0 card
1. Depends on router model.
0151
0-1 (SPA module number on the Cisco XR 12000 and 12000 Series SIP-600)
CSC 0 and 13 SFC 0, 1, 2, 3, and 4 Dedicated slot 17

5 3, 4
CPU0 CPU0 CPU0
2. RP pairs can be in any adjacent slot pairs as long as the even-numbered slot is the smaller slot number. For example, an RP pair can be installed in slots 0 and 1, 2 and 3, or 14 and 15. 3. Not used on Cisco XR 12404 routers. 4. Total number of SFC slots depends on router model. 5. Used only on Cisco XR 12404 routers.
8-13
Displaying Router Node IDs and Status

In administration EXEC mode, the show platform command displays information for all router nodes, which include nodes in all chassis and SDRs. In administration EXEC mode, the command display also includes additional node IDs such as those for fabric cards, alarm modules, and fan controllers. For each node, this information includes the host card type, the operational state, and the configuration state. To display information on a single node, enter the command with a node ID. The syntax for the show platform command on Cisco CRS-1 routers is: show platform [nodeID] The syntax for the show platform command on Cisco XR 12000 Series Routers is: show platform The following example displays the status for all nodes in a Cisco CRS-1 Multishelf System:
RP/0/RP0/CPU0:router(admin)# show platform Node Type PLIM State Config State ----------------------------------------------------------------------------0/5/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/5/CPU0 MSC 4OC192-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/7/SP DRP(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/7/CPU0 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON 0/7/CPU1 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON 0/14/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/14/CPU0 MSC 8-10GbE IOS XR RUN PWR,NSHUT,MON 0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON 0/FC0/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/FC1/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/AM0/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/AM1/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM1/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM4/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM5/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM6/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM7/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/4/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/4/CPU0 MSC 4OC192-POS/DPT IOS XR RUN PWR,NSHUT,MON 1/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 1/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON 1/FC0/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/FC1/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/AM0/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM0/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM1/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM3/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM4/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM5/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM6/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON 1/SM7/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON F0/SM4/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MON F0/SM5/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MON F0/SM6/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MON F0/SM7/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MON F0/SC0/CPU0 FCC-SC(Active) N/A IOS XR RUN PWR,NSHUT,MON F0/SC1/CPU0 FCC-SC(Standby) N/A IOS XR RUN PWR,NSHUT,MON F0/AM0/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON
8-14
Chapter 8
F0/AM1/SP F0/LM0/SP F0/LM1/SP
ALARM(SP) FCC-LED(SP) UNKNOWN(SP)
N/A N/A N/A
IOS XR RUN IOS XR RUN IN-RESET
PWR,NSHUT,MON PWR,NSHUT,MON PWR,NSHUT,MON
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. The nodeID appears in the rack/slot/module notation, and the nodeID components are as follows:

The rack number in a single-shelf system is always 0. In a multishelf system, the LCC rack number range is 0 to 255 and the FCC rack number range is F0 to F7. The slot is the number of the physical slot in which the card is installed. The module identifies a system hardware component.
Table 8-1 summarizes the nodeID for each type of card in a Cisco CRS-1 router, and Table 8-2 summarizes the nodeID for each type of card in a Cisco XR 12000 Series Router.
Displaying Router Environment Information

The show environment command displays hardware information for the system, including fan speeds, LED indications (Cisco CRS-1 routers only), power supply voltage and current information, and temperatures. The syntax for the show environment command is: show environment [options] You can use the show environment command options to limit the detail in the command display. To view the command options, enter the show environment ? command. The following example shows the full environment status report:
RP/0/0/CPU0:router# show environment Temperature Information --------------------------------------------R/S/I 0/0/* 0/3/* 0/4/* 0/5/* 0/6/* 0/7/* 0/8/* Modules Sensor host host host host host host host host host host host host host host Inlet Hot Inlet Hot Inlet Hot Inlet Hot Hot Inlet Inlet Hot Inlet Hot Temp. (deg C) 23.0 23.0 24.0 33.0 24.5 31.5 23.5 30.5 31.5 22.5 20.0 29.5 20.5 32.0
8-15
Threshold Information --------------------------------------------R/S/I Modules Sensor Minor (Lo/Hi) --/ 55 --/ 66 --/ ---/ ---/ -2950/3500 4800/5150 4700/5300 --/ 55 --/ 66 --/ ---/ ---/ ---/ -4800/5200 4700/5300 --/ 55 --/ 66 --/ ---/ ---/ ---/ ---/ ---/ -4700/5300 --/ 55 --/ 66 --/ ---/ ---/ ---/ ---/ ---/ -4700/5300 --/ 66 --/ 55 --/ ---/ ---/ ---/ -4700/5300 --/ 55 --/ 66 --/ ---/ ---/ ---/ ---/ ---/ -4700/5300 --/ 55 --/ 66 --/ ---/ ---/ ---/ -4800/5200 4700/5300 Major (Lo/Hi) --/ 60 --/ 69 --/ ---/ ---/ -2900/3600 4700/5200 4500/5500 --/ 60 --/ 69 --/ ---/ ---/ ---/ -4700/5300 4600/5400 --/ 60 --/ 69 --/ ---/ ---/ ---/ ---/ ---/ -4600/5400 --/ 60 --/ 69 --/ ---/ ---/ ---/ ---/ ---/ -4600/5400 --/ 69 --/ 60 --/ ---/ ---/ ---/ -4600/5400 --/ 60 --/ 69 --/ ---/ ---/ ---/ ---/ ---/ -4600/5400 --/ 60 --/ 69 --/ ---/ ---/ ---/ -4700/5300 4600/5400 Critical (Lo/Hi) --/ ---/ ---/ ---/ ---/ ---/ ---/ ---/ ---/ 70 --/ 75 --/ ---/ ---/ ---/ -4600/5400 4500/5500 --/ 70 --/ 75 --/ ---/ ---/ ---/ ---/ ---/ -4500/5500 --/ 70 --/ 75 --/ ---/ ---/ ---/ ---/ ---/ -4500/5500 --/ 75 --/ 70 --/ ---/ ---/ ---/ -4500/5500 --/ 70 --/ 75 --/ ---/ ---/ ---/ ---/ ---/ -4500/5500 --/ 70 --/ 75 --/ ---/ ---/ ---/ -4600/5400 4500/5500
0/0/*
0/3/*
0/4/*
0/5/*
0/6/*
0/7/*
0/8/*
host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host
InletTemp HotTemp PLIM_V4_1.6V PLIM_V5_1.8V PLIM_V3_2.5V 3.3V 5V Mbus5V InletTemp HotTemp PLIM_V3_1.5V PLIM_V8_1.8V PLIM_V7_2.5V 3.3V 5V Mbus5V InletTemp HotTemp PLIM_V3_1.5V PLIM_V8_1.8V PLIM_V7_2.5V PLIM_V6_1.5V 5V 3.3V Mbus5V InletTemp HotTemp PLIM_V3_1.5V PLIM_V8_1.8V PLIM_V7_2.5V PLIM_V6_1.5V 5V 3.3V Mbus5V HotTemp InletTemp PLIM_V3_1.5V PLIM_V8_1.8V PLIM_V7_2.5V 3.3V Mbus5V InletTemp HotTemp PLIM_V3_1.5V PLIM_V8_1.8V PLIM_V7_2.5V PLIM_V6_1.5V 5V 3.3V Mbus5V InletTemp HotTemp PLIM_V3_1.5V PLIM_V8_1.8V PLIM_V7_2.5V 3.3V 5V Mbus5V
8-16
Chapter 8
Voltage Information --------------------------------------------R/S/I 0/0/* Modules Sensor host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host host PLIM_V4_1.6V PLIM_V5_1.8V PLIM_V3_2.5V 3.3V 5V Mbus5V PLIM_V3_1.5V PLIM_V8_1.8V PLIM_V7_2.5V 3.3V 5V Mbus5V PLIM_V3_1.5V PLIM_V8_1.8V PLIM_V7_2.5V PLIM_V6_1.5V 5V 3.3V Mbus5V PLIM_V3_1.5V PLIM_V8_1.8V PLIM_V7_2.5V PLIM_V6_1.5V 5V 3.3V Mbus5V PLIM_V3_1.5V PLIM_V8_1.8V PLIM_V7_2.5V 3.3V Mbus5V PLIM_V3_1.5V PLIM_V8_1.8V PLIM_V7_2.5V PLIM_V6_1.5V 5V 3.3V Mbus5V PLIM_V3_1.5V PLIM_V8_1.8V PLIM_V7_2.5V 3.3V 5V Mbus5V Voltage (mV) 1612 1804 2504 3296 5048 5048 1496 1788 2492 3284 5000 5024 1500 1796 2488 1508 4976 3288 5048 1504 1792 2488 1504 4976 3284 4984 1496 1792 2476 3300 5016 1504 1796 2484 1504 4976 3276 4984 1496 1792 2492 3280 5000 5024 Margin nominal nominal nominal nominal nominal n/a nominal nominal nominal nominal nominal n/a nominal nominal nominal nominal nominal nominal n/a nominal nominal nominal nominal nominal nominal n/a nominal nominal nominal nominal n/a nominal nominal nominal nominal nominal nominal n/a nominal nominal nominal nominal nominal n/a
0/3/*
0/4/*
0/5/*
0/6/*
0/7/*
0/8/*
Displaying RP Redundancy Status

The show redundancy command displays the redundancy status of the route processors (RPs). This command also displays the boot and switch-over history for the RPs. The show redundancy operates in EXEC or administration EXEC mode.
8-17
Chapter 8 RP Redundancy and Switchover
In the following example, the show redundancy command displays the redundancy status for a redundant RP pair:
RP/0/RP0/CPU0:router# show redundancy This node (0/RP0/CPU0) is in ACTIVE role Partner node (0/RP1/CPU0) is in STANDBY role Standby node in 0/RP1/CPU0 is ready Reload and boot info ---------------------RP reloaded Fri Apr 9 03:44:28 2004: 16 hours, 51 minutes ago This node booted Fri Apr 9 06:19:05 2004: 14 hours, 16 minutes ago Last switch-over Fri Apr 9 06:53:18 2004: 13 hours, 42 minutes ago Standby node boot Fri Apr 9 06:54:25 2004: 13 hours, 41 minutes ago Standby node last not ready Fri Apr 9 20:35:23 2004: 0 minutes ago Standby node last ready Fri Apr 9 20:35:23 2004: 0 minutes ago There have been 2 switch-overs since reload
RP Redundancy and Switchover

RP redundancy is established differently between the Cisco CRS-1 routers and Cisco XR 12000 Series Routers. After redundancy is established, redundancy management is the same for all routers. The following sections describe RP redundancy and switchover:

Establishing RP Redundancy on the Cisco CRS-1 Router, page 8-18 Establishing RP Redundancy on Cisco XR 12000 Series Routers, page 8-19 Determining the Active RP in a Redundant Pair, page 8-20 Role of the Standby RP, page 8-20 Summary of Redundancy Commands, page 8-21 Automatic Switchover, page 8-21 RP Redundancy During RP Reload, page 8-21 Manual Switchover, page 8-22 Communicating with a Standby RP, page 8-23 Reloading the Active RP, page 8-25
Establishing RP Redundancy on the Cisco CRS-1 Router

Cisco CRS-1 routers have two slots for RPs: RP0 and RP1 (see Figure 8-1). These slots are configured for redundancy by default, and the redundancy cannot be eliminated. To establish RP redundancy, install RPs into both slots.
8-18
Chapter 8
Managing the Router Hardware RP Redundancy and Switchover
Figure 8-1
Redundant Set of RPs Installed in Slots RP0 and RP1 in a 16-Slot Chassis
A0
A1
A2
AM0
B0
B1
B2
AM1 Line card Line card

116536
PLIM
PLIM
PLIM
PLIM FC0 FC1 PLIM
PLIM PLIM
PLIM PLIM
PL0 PL1 PL2 PL3
PL4 PL5 PL6 PL7
PLIM
PLIM
PLIM
PLIM RP0 RP1 PLIM
PL PL PL8 PL9 10 11
PL PL PL PL 12 13 14 15
Note: Illustration not to scale
Establishing RP Redundancy on Cisco XR 12000 Series Routers

In a Cisco XR 12000 Series Router, redundant RPs are formed when you insert two RP cards into paired redundancy slots. Redundancy slots are paired as follows:

Slot 0 and Slot 1 Slot 2 and Slot 3 Slot 4 and Slot 5 Slot 6 and Slot 7 Slot 8 and Slot 9 Slot 10 and Slot 11 Slot 12 and Slot 13 Slot 14 and Slot 15
RPs that are seated in paired redundancy slots cannot be assigned to different SDRs. For example, an RP that is installed in Slot 3 can be assigned to one SDR, while an RP that is installed in Slot 4 can be assigned to a different SDR because Slot 3 and Slot 4 are not a redundant pair. However, you cannot have the RP in Slot 3 assigned to a different SDR than the RP in Slot 2 because Slot 2 and Slot 3 are a redundant pair.
PLIM
PLIM
8-19
RP redundancy is established when the Cisco IOS XR software is brought up on both cards in paired redundancy slots. For example, if you install the Cisco IOS XR software on the DSC, an RP in the paired redundancy slot comes up as the standby DSC after the minimum boot image (MBI) is loaded and the redundant RP synchronizes with the DSC.
Determining the Active RP in a Redundant Pair

During system startup, the software configuration (redundancy reddrv command) determines which RP in each redundant pair becomes the active RP. You can tell which RP is the active RP in the following ways:
On Cisco CRS-1 routers, the active RP can be identified by the green Primary LED on the faceplate of the card. The active RP is indicated when the Primary LED is on. The alphanumeric LED display on the RP displays ACTV RP. On Cisco XR 12000 Series Routers, the alphanumeric LED display on the active PRP displays: PRI RP. The slot of the active RP is indicated in the CLI prompt. For example:
In this example, the prompt indicates that you are communicating with the active RP in slot RP1. See the CLI Prompt section on page 4-12 for a complete description of the CLI prompt.
Enter the show redundancy command in EXEC mode to display a summary of the active and standby RP status. For example:
RP/0/0/CPU0:router# show redundancy Redundancy information for node 0/0/CPU0: ========================================== Node 0/0/CPU0 is in ACTIVE role Partner node (0/1/CPU0) is in STANDBY role Standby node in 0/1/CPU0 is ready Reload and boot info ---------------------PRP reloaded Thu Jan 12 05:51:33 2006: 11 hours, 19 minutes ago Active node booted Thu Jan 12 05:51:33 2006: 11 hours, 19 minutes ago Standby node boot Thu Jan 12 06:28:15 2006: 10 hours, 43 minutes ago Standby node last went not ready Thu Jan 12 06:31:16 2006: 10 hours, 40 minutes ago Standby node last went ready Thu Jan 12 06:31:16 2006: 10 hours, 40 minutes ago There have been 0 switch-overs since reload
Role of the Standby RP

The second RP to boot in a redundant pair automatically becomes the standby RP. While the active RP manages the system and communicates with the user interface, the standby RP maintains a complete backup of the software and configurations for all cards in the system. If the active RP fails or goes off line for any reason, the standby RP immediately takes control of the system.
8-20
Chapter 8
Managing the Router Hardware RP Redundancy and Switchover
Summary of Redundancy Commands

RP redundancy is enabled by default in the Cisco IOS XR software, but you can use the commands described in Table 8-3 to display the redundancy status of the cards or force a manual switchover.
Table 8-3 RP Redundancy Commands
Command show redundancy redundancy switchover show platform
Description Displays the redundancy status of the RPs. This command also displays the boot and switch-over history for the RPs. Forces a manual switchover to the standby RP. This command works only if the standby RP is installed and in the ready state. Displays the status for node, including the redundancy status of the RP cards. In EXEC mode, this command displays status for the nodes assigned to the SDR. In administration EXEC mode, this command displays status for all nodes in the system.
Automatic Switchover
Automatic switchover from the active RP to the standby RP occurs only if the active RP encounters a serious system error, such as the loss of a mandatory process or a hardware failure. When an automatic switchover occurs, the RPs respond as follows:

If a standby RP is installed and ready for switchover, the standby RP becomes the active RP. The original active RP attempts to reboot. If the standby RP is not in ready state, then both RPs reboot. The first RP to boot successfully assumes the role of active RP.
RP Redundancy During RP Reload

The reload command causes the active RP to reload the Cisco IOS XR software. When an RP reload occurs, the RPs respond as follows:

If a standby RP is installed and ready for switchover, the standby RP becomes the active RP. The original active RP reboots and becomes the standby RP. If the standby RP is not in the ready state, then both RPs reboot. The first RP to boot successfully assumes the role of active RP.
Caution
You should not use the reload command to force an RP switchover because the result could be a significant loss of router operations. Instead, use the redundancy switchover command to fail over to the standby RP, then use the hw-module location nodeID reload command to reload the new standby RP. See the Reloading, Shutting Down, or Power Cycling a Node section on page 8-24 for more information.
8-21
Manual Switchover
You can force a manual switchover from the active RP to the standby RP using the redundancy switchover command. If a standby RP is installed and ready for switchover, the standby RP becomes the active RP. The original active RP becomes the standby RP. In the following example, partial output for a successful redundancy switchover operation is shown:
RP/0/RP0/CPU0:router# show redundancy This node (0/RP0/CPU0) is in ACTIVE role Partner node (0/RP1/CPU0) is in STANDBY role Standby node in 0/RP1/CPU0 is ready RP/0/RP0/CPU0:router# redundancy switchover Updating Commit Database. Please wait...[OK] Proceed with switchover 0/RP0/CPU0 -> 0/RP1/CPU0? [confirm] Initiating switch-over. RP/0/RP0/CPU0:router# <Your 'TELNET' connection has terminated>
In the preceding example, the Telnet connection is lost when the previously active RP resets. To continue management of the router, you must connect to the newly activated RP as shown in the following example:
User Access Verification Username: cisco Password: Last switch-over Sat Apr 15 12:26:47 2006: 1 minute ago RP/0/RP1/CPU0:router#
If the standby RP is not in ready state, the switchover operation is not allowed. In the following example, partial output for a failed redundancy switchover attempt is shown:
RP/0/RP1/CPU0:router# show redundancy Redundancy information for node 0/RP0/CPU0: ========================================== Node 0/RP1/CPU0 is in ACTIVE role Partner node (0/RP0/CPU0) is in UNKNOWN role Reload and boot info ---------------------RP reloaded Wed Mar 29 17:22:08 2006: 2 weeks, 2 days, 19 hours, 14 minutes ago Active node booted Sat Apr 15 12:27:58 2006: 8 minutes ago Last switch-over Sat Apr 15 12:35:42 2006: 1 minute ago There have been 4 switch-overs since reload RP/0/RP1/CPU0:router# redundancy switchover Switchover disallowed: Standby node is not ready.
8-22
Chapter 8
Managing the Router Hardware DSC Migration on Cisco CRS-1 Multishelf Systems
Communicating with a Standby RP

The active RP automatically synchronizes all system software, settings, and configurations with the standby RP. If you connect to the standby RP through the console port, you can view the status messages for the standby RP. The standby RP does not display a CLI prompt, so you cannot manage the standby card while it is in standby mode. If you connect to the standby RP through the management Ethernet port, the prompt that appears is for the active RP, and you can manage the router the same as if you had connected through the management Ethernet port on the active RP.
DSC Migration on Cisco CRS-1 Multishelf Systems

Designated Shelf Controller (DSC) migration is the act of moving the DSC role to a different part of the router. The DSC role automatically migrates when the DSC cannot perform its function on the shelf in which it currently resides. The cause of a DSC migration can be a failure of both of the RPs in the DSC shelf or any event that removes power from the DSC line card chassis (LCC). DSC migration can be triggered by the following methods:
1. 2. 3. 4.
Shutdown power to DSC LCC. (Recommended) Hardware-module reset or shutdown of a standby RP then an active RP in a DSC LCC. (Not recommended) Online, insertion, removal (OIR) for an active RP and standby RP in a DSC LCC simultaneously. (Not recommended) Removal of control Ethernet connectivity to both RPs in a DSC LCC. (Not recommended)
Note
If planned downtime of a DSC LCC occurs, the recommended method of triggering DSC migration is to shutdown the power to the DSC LCC. The methods, which are not recommended, shutdown only one transport medium in the system. For example, control Ethernet but fabric medium can still be up for another 30 seconds. This causes an inconsistent system view in the named SDR using DRP paired across the rack in which the DRP loses control Ethernet connectivity, but the LR plane is still working and can bring the named SDR into an inconsistent view if the named SDR is across the rack. To support DSC migration in Cisco IOS XR Software Release 3.3.2 and higher, we recommend that you:
Keep the default placement of all four RPs in the owner SDR. When the owner SDR spans both LCCs, the impact on the SDR resources is minimal in the remaining rack. Existing connections are not interrupted for the resources in the remaining rack, but a delay in routing new connections can occur while the routing tables are updated. Run all routing protocols in a named SDR. In addition, by running all routing protocols in a named SDR, which requires a distributed route processor (DRP) paired across the rack, the operation of Cisco Nonstop Forwarding (NSF) and Cisco Nonstop Routing (NSR) continues.
An election process selects the node that is to receive the DSC role upon DSC migration. The basis of the election is the shelf number. The shelf with the lowest number is designated to receive the DSC role. DSC migration can cause a very short interruption to traffic flowing through the owner SDR. Although the time can vary with the addition of new features to DSC management and other factors, in the current release the time is likely to be around 20 to 30 seconds.
8-23
Chapter 8 Reloading, Shutting Down, or Power Cycling a Node
The reason for the traffic loss is because virtual Interfaces (VI), such as loopback, null, tunnels, and bundles are hosted on the DSDRSC of an SDR. For the owner SDR, the DSDRSC is the same node as the DSC itself. For DSC migration to occur, both active and standby DSC must be lost. Therefore, for the owner SDR, both active and standby DSDRSC are lost. VI's must be recreated on the new DSC, which is also the new DSDRSC. This operation takes some time, during which routing protocols such as BGP that use loopback or null interfaces are affected. Similarly, tunnels and bundles must also be recreated, affecting protocols such as MPLS. As a result, there is a drop in traffic in the default or owner SDR.
Note
In Cisco IOS XR Software Release 3.3.0 and higher, DSC migration is disabled if the RPs in both LCCs are assigned to different SDRs. To minimize the impact of DSC migration, create named SDRs that operate on DRP in each LCC. If the DSC rack fails, any named SDRs on the failed rack also fail. However, named SDRs on the unaffected rack can continue through DSC migration without any interruption in service. If the failure in the DSC rack affects only the RP cards, the named SDR in the affected rack cannot function after the RPs on that rack go down.
Reloading, Shutting Down, or Power Cycling a Node

Use the commands described in this section to reload the Cisco IOS XR software on the active RP or on any specified node in the system. This section also describes the commands used to administratively shut down a node and power a node on or off. Table 8-4 summarizes the commands described in this section.
Table 8-4 Commands to Reload, Shut Down, or Power Cycle a Node
Command hw-module location nodeID power disable
Description This command must be entered in administration configuration mode and administratively turns the power off for a Cisco XR 12000 Series Router node. The changes do not take effect until you enter the commit command. To power on a node, use the no form of this command.
Note
This command applies only to Cisco XR 12000 Series Routers and cannot be used to disable power on the RP from which the command is entered.
hw-module location nodeID reload
This command works in EXEC mode and reloads the Cisco IOS XR software on a specific node or all nodes. To specify all nodes, enter all for the nodeID. The node reloads with the current running configuration and active software set for that node. This command must be entered in administration configuration mode and administratively shuts down a specified node on a Cisco XR 12000 Series Router. Nodes that are shut down still have power, but cannot load or operate Cisco IOS XR software. To return a node to the up state, use the no form of this command.
Note
hw-module location nodeID shutdown
This command applies only to Cisco XR 12000 Series Routers and cannot be used to shut down the RP from which the command is entered.
8-24
Chapter 8
Managing the Router Hardware Reloading, Shutting Down, or Power Cycling a Node
Table 8-4
Commands to Reload, Shut Down, or Power Cycle a Node (continued)
Command reload
Description Causes the active RP to reload the Cisco IOS XR software according to the configuration register setting (for example, 0x0 to enter ROMMON bootstrap mode and 0x2102 to reload the RP to EXEC mode). The reload command can be entered in EXEC or administration EXEC modes, and you can see additional options by entering the reload ? command. See the Reloading the Active RP section on page 8-25 for more information. Displays the configuration register setting for the router.

show variables boot
Use this command in administration EXEC mode to see the variables for both RPs. The configuration register setting determines how the router boots during a system reset. The most common configuration register settings are:
0x2102: The active RP loads the Cisco IOS XR software and default
configuration on the next system boot. After logging in, the user can access EXEC mode.
0x0: The active RP enters the bootstrap ROM Monitor (rommon B1> ) on the
next system boot.
Reloading the Active RP

The reload command causes the active RP to reload the Cisco IOS XR software according to the configuration register setting. This setting determines how the active RP acts when reloaded. This section contains instructions to reload the Cisco IOS XR software and return to EXEC mode. For instructions to use the reload command for entering ROM Monitor bootstrap mode, see Cisco IOS XR ROM Monitor Guide.
Caution
Because the reload command causes the active RP to go off line and either reload Cisco IOS XR software or enter ROM Monitor mode, the router experiences a loss of service unless a redundant standby RP is installed and in ready state. To display the status of the standby RP, type the show redundancy command in EXEC mode.
SUMMARY STEPS
1. 2. 3. 4. 5. 6.
show redundancy admin show variables boot (Optional) config-register 0x2102 exit reload
8-25
Chapter 8 Reloading, Shutting Down, or Power Cycling a Node
DETAILED STEPS
Command or Action
Step 1
show redundancy
Purpose Displays the RP redundancy status.
Example:
RP/0/RP0/CPU0:router# show redundancy
If a standby RP is in ready redundancy state, the reload command also causes the router to gracefully fail over to the standby RP.
Step 2
admin
Enters administration EXEC mode.
Example:
Step 3
show variables boot
Displays the configuration register setting.
Enter this command in administration EXEC mode. For normal operations, the configuration register setting is 0x2102, which causes the active RP to reload the Cisco IOS XR software. Verify that the configuration register setting is 0x2102. If it is not, complete Step 3 to reset the configuration register to 0x2102. For instructions on how to enter ROM Monitor bootstrap mode, see Cisco IOS XR ROM Monitor Guide. This step is necessary only if the register is not set to 0x2102 in the running configuration.
Example:
RP/0/RP0/CPU0:router(admin)# show variables boot
Note
Step 4
config-register 0x2102
(Optional) Sets the configuration register to 0x2102.
Example:
RP/0/RP0/CPU0:router(admin)# config-register 0x2102
Step 5
exit
Exits administration EXEC mode.
Example:
Step 6
reload
Reloads the active RP according to the configuration register setting.

Example:
RP/0/RP0/CPU0:router# reload
If the setting is 0x2102, then the RP reloads the Cisco IOS XR software. If the standby RP is in ready redundancy state, the router switches over to the standby RP. If a standby RP is not installed or not in a ready state, the router experiences a loss of service while the active RP is reloading the Cisco IOS XR software.
8-26
Chapter 8
Managing the Router Hardware Using Controller Commands to Manage Hardware Components
Administratively Shutting Down or Powering On or Off a Node

A Cisco XR 12000 Series Router node can be administratively shut down by entering the hw-module location nodeID shutdown command in administration configuration mode. A node that is shut down still has power, but cannot load or run the Cisco IOS XR software. You can also administratively turn power off for a Cisco XR 12000 Series Router node using the hw-module location nodeID power disable command in administration configuration mode. For more information on the use of these commands, see Cisco IOS XR Interface and Hardware Component Command Reference.
Using Controller Commands to Manage Hardware Components

The controller, controllers, and show controllers commands are used to manage and display settings for various hardware components, including the switch fabric management, Ethernet control plane, and interface manager. These commands are primarily diagnostic and related to driver-level details. The information available with these commands varies widely and is hardware specific. For information on the use of these commands, see the Cisco IOS XR Interface and Hardware Component Command Reference.
Formatting Hard Drives, Flash Drives, and Other Storage Devices

To format a storage device on the router, use the format command in EXEC mode.
Caution
Formatting a storage device deletes all data on that device. The following command syntax is used: format filesystem: [options] Table 8-5 describes the format command syntax.
Table 8-5 format command Syntax Description
Variable filesystem
Description Specifies the memory device to format, followed by a colon. The supported file systems are bootflash:, compactflash:, flash:, harddisk:, harddiska:, disk0:, and disk1:. Enter format ? to see the devices supported on your router. Enter format filesystem: ? to see the available options. For more information, see Cisco IOS XR System Management Command Reference.
options
In the following example, the format command is used to format the hard disk:
RP/0/RP0/CPU0:router# format harddisk:
8-27
Chapter 8 Removing and Replacing Cards
Removing and Replacing Cards

This section describes card replacement issues and procedures for the following tasks:

Removing Line Cards, MSCs, or PLIMs, page 8-28 Replacing an MSC, page 8-29 Replacing a Line Card or PLIM with the Same Media Type and Port Count, page 8-29 Replacing a Line Card or PLIM with the Same Media Type and a Different Port Count, page 8-29 Replacing a Line Card or PLIM with a Different Media Type, page 8-30 Removing and Replacing Cisco CRS-16-FC Switch Fabric Cards, page 8-30 Removing and Replacing Cisco CRS-8-FC/S Switch Fabric Cards, page 8-38 Removing and Replacing CSC and SFC Cards, page 8-47 Removing and Replacing CSFC Cards, page 8-53 Adding a Standby PRP to a Cisco 12000 Series Router, page 8-53
Removing Line Cards, MSCs, or PLIMs

Line cards, modular services cards (MSCs), and physical layer interface modules (PLIMs) are designed for online insertion and removal (OIR). On Cisco XR 12000 Series Routers, a line card is a single card that contains all service processing functions and physical line interfaces. On Cisco CRS-1 routers, the service processing functions are provided on the MSC, and the physical line interface is provided on a separate card that connects the physical lines to the MSC. The OIR feature allows you to remove and replace cards without removing power to the card or chassis. Removing a card interrupts all traffic passing through the card, but it does not remove the card configuration. When you remove a card, the configuration remains for all interfaces, but the interfaces do not appear in the output of the show interfaces command. You can view interface configurations by entering the show running-config command. The following example shows how the configuration appears when a card is removed:
RP/0/0/CPU0:router# show running-config Building configuration... hostname router router ospf 3269 area 0 interface POS0/3/0/0 cost 20 ! interface preconfigure POS0/3/0/0 ipv4 address 10.10.50.1 255.255.255.0 ! interface preconfigure POS0/3/0/1 description POS0/3/0/1 shutdown ! interface preconfigure POS0/3/0/2 description POS0/3/0/2 shutdown ! interface preconfigure POS0/3/0/3
8-28
Chapter 8
Managing the Router Hardware Removing and Replacing Cards
description POS0/3/0/3 shutdown !
In this example, the MSC in slot 3 is removed, and the interface configuration for all four interfaces changes to interface preconfigure. However, the router ospf reference to a slot 3 interface does not change. If you replace a PLIM with another PLIM that uses the same media type and port count, the configuration becomes active on the replacement card. To remove the configuration for a slot after a card is removed, use the no interface preconfigure command to remove all interface configuration statements for that card in the running configuration. In addition, search the configuration for any references to the removed interfaces, such as the router ospf reference to slot 3 in the preceding example. To remove the configuration for a slot when a card is installed, use the no interface command to remove all interface configuration statements for that card in the running configuration. In addition, search the configuration for any references to the removed interfaces. Each PLIM supports a specific media type (POS or Ethernet, for example) and port count. If you replace a PLIM with one that supports a different media type or port count, you should review the configuration and revise it to support the replacement PLIM.
Replacing an MSC
When you replace an MSC, the guidelines in the Removing Line Cards, MSCs, or PLIMs section on page 8-28 apply. Because only one type of MSC exists, no special procedures are required for card removal and replacement.
Replacing a Line Card or PLIM with the Same Media Type and Port Count
When you replace a line card or PLIM with a card that is of the same media type and has the same port count as the replaced card, the guidelines in the Removing Line Cards, MSCs, or PLIMs section on page 8-28 apply. Because the replacement card is of the same media type and port count, no special procedures are required for card removal and replacement.
Replacing a Line Card or PLIM with the Same Media Type and a Different Port Count
When you replace a line card or PLIM with a card that is of the same media type with a different port count, the guidelines in the Removing Line Cards, MSCs, or PLIMs section on page 8-28 apply. If the new card has a greater port count than the replaced card, the configuration applies to the corresponding lower port numbers, and the ports that did not exist on the replaced card have no configuration and come up in the shutdown state. If the new card supports fewer ports, the existing configuration for the corresponding number of ports on the new card set is applied. The previous configuration for the removed ports remains in interface preconfigure state, as shown in the following example:
RP/0/0/CPU0:router# show running-config Building configuration... hostname rtp-gsr1 interface POS0/3/0/0
8-29
ipv4 address 10.10.50.1 255.255.255.0 ! interface preconfigure POS0/3/0/1 description POS0/3/0/1 shutdown ! interface preconfigure POS0/3/0/2 description POS0/3/0/2 shutdown ! interface preconfigure POS0/3/0/3 description POS0/3/0/3 shutdown !
In the preceding example, a four-port card has been replaced with a single-port card. The configuration from port 1 on the four-port card is applied to the single port on the replacement card, and the remaining port configurations change to interface preconfigure. To remove the configuration for the missing interfaces, use the no interface preconfigure command. In addition, search for and remove any configuration references to the removed interfaces. Whenever you replace a line card or PLIM with the same media type and a different port count, review the running configuration in the router and revise the configuration as necessary.
Replacing a Line Card or PLIM with a Different Media Type

When you replace a line card or PLIM with a card that is of a different media type (for example, if you replace a POS PLIM with an Ethernet PLIM), the guidelines in the Removing Line Cards, MSCs, or PLIMs section on page 8-28 apply. Review the running configuration in the router and revise the configuration as necessary for the new media type.
Removing and Replacing Cisco CRS-16-FC Switch Fabric Cards

The 16-slot LCCs support two switch fabric cards: the CRS-16-FC/S and the CRS-16-FC/M. The CRS-16-FC/S switch fabric card provides the Stage 1, 2, and 3 switch fabric for one fabric plane in a standalone Cisco CRS-1 Carrier Routing System 16-Slot Line Card Chassis. The CRS-16-FC/M switch fabric card provides the Stage 1 and 3 switch fabric for one fabric plane in a Cisco CRS-1 LCC within a multishelf system. The Cisco CRS-1 16-Slot LCC can support the maximum throughput with seven of the eight fabric planes. To prevent traffic loss, we recommend that you shut the power down on a fabric plane for a switch fabric card before you remove it. If a switch fabric card is removed with the power on, the card is not harmed, but some traffic may be lost. When the replacement card is inserted, you can restore the power to the fabric plane and bring up the replacement card. This section describes how to properly remove and replace Cisco CRS-16-FC/S and Cisco CRS-16-FC/M cards for upgrades or repairs.
Note
The process of removing and replacing cards while the router power is on is called online insertion and removal (OIR). This procedure removes power to a specific slot before the switch fabric card is replaced. The power remains on for all other slots.
8-30
Chapter 8
Tip
For more information about switch fabric cards, see the hardware documentation listed in the Related Documents section on page xiv.
Note
This procedure does not apply when starting the router for the first time or after a power cycle or reload.
Prerequisites
You should have a working knowledge of Cisco IOS XR software and have sufficient permissions to configure the software. You must log in as root-system before starting the procedure. To confirm your login status, use the show user group command:
RP/0/RP1/CPU0:router# show user group root-system, cisco-support
To confirm your login status including root, use the show user all | include root command:
RP/0/RP1/CPU0:router# show user all | include root Groups: root-system, cisco-support Task: root-lr : READ Task: root-system : READ
WRITE WRITE
EXECUTE EXECUTE
DEBUG (reserved) DEBUG (reserved)
SUMMARY STEPS
1. 2. 3. 4. 5. 6. 7. 8. 9.
admin show platform show controllers fabric plane all configure controllers fabric plane plane_number shutdown commit end show controllers fabric plane all configure
10. hw-module power disable location nodeID 11. commit 12. end 13. show platform 14. When the fabric card state changes to UNPOWERED, replace the fabric card. 15. configure 16. no hw-module power disable location nodeID 17. commit 18. end
8-31
19. show platform 20. configure 21. no controllers fabric plane plane_number shutdown 22. commit 23. end 24. show controllers fabric plane all
DETAILED STEPS
Command or Action
Step 1
admin
Purpose Enters administration EXEC mode.
Example:
Step 2
show platform
Displays all cards on the router.
Example:
Allows you to identify a fabric card (identified with an SM prefix). The number following the SM prefix identifies the corresponding fabric plane, as follows:
Slot SM0: fabric plane 0 Slot SM1: fabric plane 1 Slot SM2: fabric plane 2 Slot SM3: fabric plane 3 Slot SM4: fabric plane 4 Slot SM5: fabric plane 5 Slot SM6: fabric plane 6 Slot SM7: fabric plane 7
Step 3
show controllers fabric plane all
Displays the status of each fabric plane.
Example:
RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all
Step 4
configure
Enters administration configuration mode.
Example:
Step 5
controllers fabric plane plane_number shutdown
Shuts down the fabric plane.
Example:
RP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 0 shutdown
8-32
Chapter 8
Command or Action
Step 6
commit
Purpose Commits the target configuration to the router running configuration.
Example:
Step 7
end
Exits administration configuration mode and returns to administration EXEC mode.
Example:
RP/0/RP0/CPU0:router(admin-config)# end
Step 8
Example:
The Admin State and Oper State columns should read DOWN.
Step 9
configure
Example:
Step 10
hw-module power disable location nodeID
Sets the target configuration to remove power from the fabric card.
Example:
RP/0/RP0/CPU0:router(admin-config)# hw-module power disable location 0/SM0/SP
Step 11
commit
Example:
Step 12
end
Example:
Step 13
show platform
Displays the status of all cards on the router.
Check the State column for the status of the fabric card. Do not continue to the next step until the status in the State column changes to UNPOWERED. It takes some time for the card to shut down. Repeat the show platform command to check the card state.
Example:
Step 14 Step 15
When the fabric card state changes to UNPOWERED, replace the fabric card.
configure
Replaces the physical card. Enters administration configuration mode.
Example:
8-33
Command or Action
Step 16
no hw-module power disable location nodeID
Purpose Sets the target configuration to restore power to the fabric card.
Example:
RP/0/RP0/CPU0:router(admin-config)# no hw-module power disable location 0/SM0/SP
Step 17
commit
Example:
Step 18
end
Ends the configuration session and returns to administration EXEC mode.
Example:
Step 19
show platform
Check the State column for the status of the fabric card. Do not continue to the next step until the status in the State column changes to IOS XR RUN. It takes some time for the card to start up. Repeat the show platform command to check the card state.
Example:
Step 20
configure
Example:
Step 21
no controllers fabric plane plane_number shutdown
Sets the target configuration to bring up the fabric plane.
Example:
RP/0/RP0/CPU0:router(admin-config)# no controllers fabric plane 0 shutdown
Step 22
commit
Example:
Step 23
end
Example:
Step 24
Displays the fabric plane status.
The Admin State and Oper State columns should read UP.
Example:
8-34
Chapter 8
Examples
The following example shows the commands and command responses for replacing a CRS-16-FC/S card:
RP/0/RP1/CPU0:router# admin RP/0/RP1/CPU0:router(admin)# show platform Node Type PLIM State Config State ----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/1/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM7/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all Flags: P - plane admin down, C L A B I N o f m Plane p - plane oper down card oper down linkport oper down asic oper down bundle port oper down bundle oper down node down data down
card admin down, c link port admin down, l asic admin down, a bundle port admin Down, b bundle admin down, i node admin down, n other end of link down d failed component downstream plane multicast down Oper
Admin
Id State State -------------------0 UP UP 1 UP UP 2 UP UP 3 UP UP 4 UP UP 5 UP UP 6 UP UP 7 UP UP RP/0/RP1/CPU0:router(admin)# configure RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 0 shutdown RP/0/RP1/CPU0:router(admin-config)# commit RP/0/RP1/CPU0:Oct WN : Plane 0 state RP/0/RP1/CPU0:Oct T : Administration 5 02:15:09.265 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO changed to DOWN: 5 02:15:09.319 : config[65734]: %MGBL-LIBTARCFG-6-ADMIN_COMMI configuration committed by user 'jim'.
8-35
RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all Flags: P C L A B I N o f m plane admin down, p card admin down, c link port admin down, l asic admin down, a bundle port admin Down, b bundle admin down, i node admin down, n other end of link down d failed component downstream plane multicast down plane oper down card oper down linkport oper down asic oper down bundle port oper down bundle oper down node down data down
Plane Admin Oper Id State State -------------------0 DOWN DOWN 1 UP UP 2 UP UP 3 UP UP 4 UP UP 5 UP UP 6 UP UP 7 UP UP RP/0/RP1/CPU0:router(admin)# configure RP/0/RP1/CPU0:router(admin-config)# hw-module power disable location 0/SM0/SP RP/0/RP1/CPU0:router(admin-config)# commit RP/0/RP1/CPU0:Oct 5 02:18:24.774 : config[65734]: %MGBL-LIBTARCFG-6-COMMIT : Co nfiguration committed by user 'jim'. Use 'show configuration commit changes 10 00000142' to view the changes. RP/0/RP1/CPU0:router(config)#LC/0/1/CPU0:Oct 5 02:18:26.873 : fabricq_mgr[ 127]: %FABRIC-FABRICQ-3-FI_UNCORR_ERROR : fabricq: Major error in Fabric Interfa ce : RS Uncorrectable errors on Fabricq ASIC 0 link 3 RP/0/RP1/CPU0:Oct 5 02:18:28.959 : shelfmgr[284]: %PLATFORM-SHELFMGR-3-POWERDOW N_RESET : Node 0/SM0/SP is powered off due to admin power off request RP/0/RP1/CPU0:router(admin-config)# end RP/0/RP1/CPU0:router(admin)# show platform Node Type PLIM
State
Config State
----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/1/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/S(SP) N/A UNPOWERED NPWR,NSHUT,MON 0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM7/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON
8-36
Chapter 8
When the state of the fabric card changes to UNPOWERED, replace the fabric card.
RP/0/RP1/CPU0:router# configure RP/0/RP1/CPU0:router(admin-config)# no hw-module power disable location 0/SM0/SP RP/0/RP1/CPU0:router(admin-config)# commit RP/0/RP1/CPU0:Oct 5 02:19:30.472 : config[65734]: %MGBL-LIBTARCFG-6-COMMIT : Co nfiguration committed by user 'jim'. Use 'show configuration commit changes 10 00000143' to view the changes. RP/0/RP1/CPU0:router(config)#RP/0/RP1/CPU0:Oct 5 02:19:42.747 : shelfmgr[2 84]: %PLATFORM-MBIMGR-7-IMAGE_VALIDATED : 0/SM0/SP: MBI tftp:/hfr-os-mbi-3.3.0/ sp/mbihfr-sp.vm validated RP/0/RP1/CPU0:router(admin-config)# end RP/0/RP1/CPU0:router(admin)# show platform Node Type PLIM State Config State
----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/1/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/S(SP) N/A MBI-BOOTING PWR,NSHUT,MON 0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM7/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON RP/0/RP1/CPU0:router(admin)# show platform Node Type PLIM State Config State
----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/1/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/S(SP) N/A MBI-RUNNING PWR,NSHUT,MON 0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM7/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON RP/0/RP1/CPU0:router(admin)# show platform Node Type PLIM State Config State ----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/1/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON
8-37
0/SM7/SP
FC/S(SP)
N/A
IOS XR RUN
PWR,NSHUT,MON
RP/0/RP1/CPU0:router(admin)# configure RP/0/RP1/CPU0:router(admin-config)#SP/0/SM0/SP:Oct 5 02:20:19.102 : init[6
5541]: %OS-INIT-7-MBI_STARTED : total time 7.678 seconds SP/0/SM0/SP:Oct 5 02:20:21.361 : insthelper[60]: %INSTALL-INSTHELPER-7-PKG_DOWN LOAD : MBI running; starting software download SP/0/SM0/SP:Oct 5 02:22:23.458 : init[65541]: %OS-INIT-7-INSTALL_READY : total time 132.060 seconds SP/0/SM0/SP:Oct 5 02:22:39.329 : sfe_drvr[108][120]: Board revision : 0x06. SP/0/SM0/SP:Oct 5 02:22:47.306 : sfe_drvr[108]: %FABRIC-FABRIC_DRVR-6-ASIC_IN ITIALIZED : Fabric ASICs initialized SP/0/SM0/SP:Oct 5 02:23:06.316 : alphadisplay[100]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : Alpha display on node 0/SM0/SP changed to IOS-XR in state default RP/0/RP1/CPU0:router(admin-config)# no controllers fabric plane 0 shutdown RP/0/RP1/CPU0:router(admin-config)# commit RP/0/RP1/CPU0:Oct 5 02:25:15.736 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO WN : Plane 0 state changed to UP: RP/0/RP1/CPU0:Oct 5 02:25:15.759 : config[65734]: %MGBL-LIBTARCFG-6-ADMIN_COMMI T : Administration configuration committed by user 'jim'. RP/0/RP1/CPU0:router(admin-config)# end RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all Flags: P - plane admin down, p - plane oper down C - card admin down, c - card oper down L A B I N o f m link port admin down, l asic admin down, a bundle port admin Down, b bundle admin down, i node admin down, n other end of link down d failed component downstream plane multicast down linkport oper down asic oper down bundle port oper down bundle oper down node down data down
Plane Admin Oper Id State State -------------------0 UP UP 1 UP UP 2 UP UP 3 UP UP 4 UP UP 5 UP UP 6 UP UP 7 UP UP
Removing and Replacing Cisco CRS-8-FC/S Switch Fabric Cards

Each CRS-8-FC/S switch fabric card provides the Stage 1, 2, and 3 switch fabric for two fabric planes in a standalone Cisco CRS-1 Carrier Routing System 8-Slot Line Card Chassis.
8-38
Chapter 8
The Cisco CRS-1 8-Slot LCC can support the maximum throughput with seven of the eight fabric planes. However, because each CRS-8-FC/S switch fabric card hosts two fabric planes, replacing a fabric card does reduce the maximum throughput and impacts router traffic if the router is operating at maximum capacity. To minimize traffic loss, we recommend that you shut the power down for the switch fabric card before you remove it. If a switch fabric card is removed with power on, the card is not harmed, but the traffic impact may be greater than if the card power were removed. When the replacement card is inserted, you can restore the power and bring up the replacement card. This section describes how to properly remove and replace a Cisco CRS-8-FC/S switch fabric card for upgrades or repairs.
Note
The process of removing and replacing cards while the router power is on is called online insertion and removal (OIR). This procedure removes power to a specific slot before the switch fabric card is replaced. The power remains on for all other slots.
Tip
For more information about switch fabric cards, see the hardware documentation listed in the Related Documents section on page xiv.
Note
This procedure does not apply when starting the router for the first time or after a power cycle or reload.
Prerequisites
WRITE WRITE
EXECUTE EXECUTE
SUMMARY STEPS
1. 2. 3. 4. 5. 6. 7.
admin show platform show controllers fabric plane all configure controllers fabric plane plane_number shutdown controllers fabric plane plane_number shutdown commit
8-39
8. 9.
end show controllers fabric plane all
10. configure 11. hw-module power disable location nodeID 12. commit 13. end 14. show platform 15. When the fabric card state changes to UNPOWERED, replace the fabric card. 16. configure 17. no hw-module power disable location nodeID 18. commit 19. end 20. show platform 21. configure 22. no controllers fabric plane plane_number shutdown 23. no controllers fabric plane plane_number shutdown 24. commit 25. end 26. show controllers fabric plane all
DETAILED STEPS
Command or Action
Step 1
admin
Example:
8-40
Chapter 8
Command or Action
Step 2
show platform
Purpose Displays all cards on the router.
Example:
Allows you to identify a fabric card (identified with an SM prefix). The number following the SM prefix identifies the corresponding fabric planes, as follows:
Slot SM0: fabric planes 0 and 1 Slot SM1: fabric planes 2 and 3 Slot SM2: fabric planes 4 and 5 Slot SM3: fabric planes 6 and 7
Step 3
Example:
Step 4
configure
Example:
Step 5
Shuts down one of the two fabric planes on a CRS-8-FC/S card.
Example:
Before removing a CRS-8-FC/S card, shut down both planes for the fabric card. The fabric planes are assigned to fabric cards as follows:
Slot SM0: fabric planes 0 and 1 Slot SM1: fabric planes 2 and 3 Slot SM2: fabric planes 4 and 5 Slot SM3: fabric planes 6 and 7
Step 6
Shuts down one of the two fabric planes on a CRS-8-FC/S card.
Example:
Shut down the companion plane to the plane shut down in the previous step.
Step 7
commit
Example:
Step 8
end
Example:
8-41
Command or Action
Step 9
Purpose Displays the status of each fabric plane.
Example:
The Admin State and Oper State columns should read DOWN for both of the shutdown planes.
Step 10
configure
Example:
Step 11
hw-module power disable location nodeID
Sets the target configuration to remove power from the fabric card.
Example:
RP/0/RP0/CPU0:router(admin-config)# hw-module power disable location 0/SM0/SP
Step 12
commit
Example:
Step 13
end
Example:
RP/0/RP0/CPU0:router(admin-config))# end
Step 14
show platform
Check the State column for the status of the fabric card. Do not continue to the next step until the status in the State column changes to UNPOWERED. It takes some time for the card to shut down. Repeat the show platform command to check the card state.
Example:
Step 15 Step 16
When the fabric card state changes to UNPOWERED, replace the fabric card.
configure
Example:
Step 17
no hw-module power disable location nodeID
Sets the target configuration to restore power to the fabric card.
Example:
RP/0/RP0/CPU0:router(admin-config)# no hw-module power disable location 0/SM0/SP
Step 18
commit
Example:
8-42
Chapter 8
Command or Action
Step 19
end
Purpose Ends the configuration session and returns to administration EXEC mode.
Example:
RP/0/RP0/CPU0:router(admin)# end
Step 20
show platform
Check the State column for the status of the fabric card. Do not continue to the next step until the status in the State column changes to IOS XR RUN. It takes some time for the card to start up. Repeat the show platform command to check the card state.
Example:
Step 21
configure
Example:
Step 22
Sets the target configuration to bring up one of the two fabric planes on the card.
Example:
RP/0/RP0/CPU0:router(admin-config)# no controllers fabric plane 0 shut
Step 23
Sets the target configuration to bring up one of the two fabric planes on the card.
Example:
RP/0/RP0/CPU0:router(admin-config)# no controllers fabric plane 1 shut
Step 24
commit
Example:
Step 25
end
Example:
Step 26
Displays the fabric plane status.
Example:
The Admin State and Oper State columns should read UP for both fabric planes on the fabric card.
Examples
The following example shows the commands and command responses for replacing a CRS-8-FC/S card:
RP/0/RP1/CPU0:router# admin RP/0/RP1/CPU0:router(admin)# show platform
8-43
Node Type PLIM State Config State ----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/1/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all Flags: P - plane admin down, C L A B I N o f m Plane p - plane oper down card oper down linkport oper down asic oper down bundle port oper down bundle oper down node down data down
card admin down, c link port admin down, l asic admin down, a bundle port admin Down, b bundle admin down, i node admin down, n other end of link down d failed component downstream plane multicast down Oper
Admin
Id State State -------------------0 UP UP 1 UP UP 2 UP UP 3 UP UP 4 UP UP 5 UP UP 6 UP UP 7 UP UP RP/0/RP1/CPU0:router(admin)# configure RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 0 shutdown RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 1 shutdown RP/0/RP1/CPU0:router(admin-config)# commit RP/0/RP1/CPU0:Oct WN : Plane 0 state RP/0/RP1/CPU0:Oct WN : Plane 1 state RP/0/RP1/CPU0:Oct T : Administration 5 02:15:09.265 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO changed to DOWN: 5 02:15:09.265 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO changed to DOWN: 5 02:15:09.319 : config[65734]: %MGBL-LIBTARCFG-6-ADMIN_COMMI configuration committed by user 'jim'.
RP/0/RP1/CPU0:router(admin-config)# end RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all Flags: P C L A B I N plane admin down, card admin down, link port admin down, asic admin down, bundle port admin Down, bundle admin down, node admin down, p c l a b i n plane oper down card oper down linkport oper down asic oper down bundle port oper down bundle oper down node down
8-44
Chapter 8
o - other end of link down d - data down f - failed component downstream m - plane multicast down Plane Admin Oper Id State State -------------------0 DOWN DOWN 1 DOWN DOWN 2 UP UP 3 UP UP 4 UP UP 5 UP UP 6 UP UP 7 UP UP RP/0/RP1/CPU0:router(admin)# configure RP/0/RP1/CPU0:router(admin-config)# hw-module power disable location 0/SM0/SP RP/0/RP1/CPU0:router(admin-config)# commit RP/0/RP1/CPU0:Oct 5 02:18:24.774 : config[65734]: %MGBL-LIBTARCFG-6-COMMIT : Co nfiguration committed by user 'jim'. Use 'show configuration commit changes 10 00000142' to view the changes. RP/0/RP1/CPU0:router(config)#LC/0/1/CPU0:Oct 5 02:18:26.873 : fabricq_mgr[ 127]: %FABRIC-FABRICQ-3-FI_UNCORR_ERROR : fabricq: Major error in Fabric Interfa ce : RS Uncorrectable errors on Fabricq ASIC 0 link 3 RP/0/RP1/CPU0:Oct 5 02:18:28.959 : shelfmgr[284]: %PLATFORM-SHELFMGR-3-POWERDOW N_RESET : Node 0/SM0/SP is powered off due to admin power off request RP/0/RP1/CPU0:router(admin-config)# end RP/0/RP1/CPU0:router(admin)# show platform Node Type PLIM
State
Config State
----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/1/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/S(SP) N/A UNPOWERED NPWR,NSHUT,MON 0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON
When the State for the fabric card changes to UNPOWERED, replace the fabric card.
RP/0/RP1/CPU0:router(admin)# configure RP/0/RP1/CPU0:router(admin-config)# no hw-module power disable location 0/SM0/SP RP/0/RP1/CPU0:router(admin-config)# commit RP/0/RP1/CPU0:Oct 5 02:19:30.472 : config[65734]: %MGBL-LIBTARCFG-6-COMMIT : Co nfiguration committed by user 'jim'. Use 'show configuration commit changes 10 00000143' to view the changes. RP/0/RP1/CPU0:router(config)#RP/0/RP1/CPU0:Oct 5 02:19:42.747 : shelfmgr[2 84]: %PLATFORM-MBIMGR-7-IMAGE_VALIDATED : 0/SM0/SP: MBI tftp:/hfr-os-mbi-3.3.0/ sp/mbihfr-sp.vm validated RP/0/RP1/CPU0:router(admin-config)# end
8-45
RP/0/RP1/CPU0:router(admin)# show platform Node Type PLIM State Config State
----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/1/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/S(SP) N/A MBI-BOOTING PWR,NSHUT,MON 0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON RP/0/RP1/CPU0:router(admin)# show platform Node Type PLIM State Config State
----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/1/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/S(SP) N/A MBI-RUNNING PWR,NSHUT,MON 0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON RP/0/RP1/CPU0:router(admin)# show platform Node Type PLIM State Config State ----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/1/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON RP/0/RP1/CPU0:router(admin)# configure RP/0/RP1/CPU0:router(admin-config)#SP/0/SM0/SP:Oct 5 02:20:19.102 : init[6
5541]: %OS-INIT-7-MBI_STARTED : total time 7.678 seconds SP/0/SM0/SP:Oct 5 02:20:21.361 : insthelper[60]: %INSTALL-INSTHELPER-7-PKG_DOWN LOAD : MBI running; starting software download SP/0/SM0/SP:Oct 5 02:22:23.458 : init[65541]: %OS-INIT-7-INSTALL_READY : total time 132.060 seconds SP/0/SM0/SP:Oct 5 02:22:39.329 : sfe_drvr[108][120]: Board revision : 0x06. SP/0/SM0/SP:Oct 5 02:22:47.306 : sfe_drvr[108]: %FABRIC-FABRIC_DRVR-6-ASIC_IN ITIALIZED : Fabric ASICs initialized SP/0/SM0/SP:Oct 5 02:23:06.316 : alphadisplay[100]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : Alpha display on node 0/SM0/SP changed to IOS-XR in state default RP/0/RP1/CPU0:router(admin-config)# no controllers fabric plane 0 shutdown RP/0/RP1/CPU0:router(admin-config)# no controllers fabric plane 1 shutdown RP/0/RP1/CPU0:router(admin-config)# commit RP/0/RP1/CPU0:Oct 5 02:25:15.736 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO WN : Plane 0 state changed to UP: RP/0/RP1/CPU0:Oct 5 02:25:15.736 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO WN : Plane 1 state changed to UP: RP/0/RP1/CPU0:Oct 5 02:25:15.759 : config[65734]: %MGBL-LIBTARCFG-6-ADMIN_COMMI T : Administration configuration committed by user 'jim'.
8-46
Chapter 8
RP/0/RP1/CPU0:router(admin-config)# end RP/0/RP1/CPU0:Oct 5 02:25:41.891 : config[65734]: %MGBL-SYS-5-CONFIG_I : Config ured from console by jim RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all Flags: P - plane admin down, p - plane oper down C - card admin down, c - card oper down L A B I N o f m link port admin down, l asic admin down, a bundle port admin Down, b bundle admin down, i node admin down, n other end of link down d failed component downstream plane multicast down linkport oper down asic oper down bundle port oper down bundle oper down node down data down
Plane Admin Oper Id State State -------------------0 UP UP 1 UP UP 2 UP UP 3 UP UP 4 UP UP 5 UP UP 6 UP UP 7 UP UP
Removing and Replacing CSC and SFC Cards

On Cisco XR 12000 Series Routers that use clock and scheduler cards (CSCs) and switch fabric cards (SFCs), the CSCs and SFCs work together to provide the switch fabric for the router. Although some router cards can be removed without software preparation, it is best to shut down and remove the power from a CSC or an SFC slot before removing a card. When the new card is inserted, you can restore the power to the slot and bring up the replacement card. This section describes how to properly remove and replace CSCs and SFCs for repairs.
Prerequisites
WRITE WRITE
EXECUTE EXECUTE
8-47
SUMMARY STEPS
1. 2. 3. 4. 5. 6. 7. 8. 9.
admin show platform configure hw-module location slot shutdown hw-module location slot power disable commit end show platform Remove and replace the CSC or SFC.
10. configure 11. no hw-module location slot power disable 12. commit 13. end 14. show platform 15. configure 16. no hw-module location slot shutdown 17. commit 18. end 19. show platform
DETAILED STEPS
Command or Action
Step 1
admin
Example:
RP/0/0/CPU0:router# admin
Step 2
show platform
Displays the state of all cards on the router.
Example:
RP/0/0/CPU0:router(admin)# show platform
Allows you to identify the CSC or SFC you want to replace. Note the node ID (in the first column) for the card you want to replace. You need to enter this ID later in this procedure.
8-48
Chapter 8
Command or Action
Step 3
configure
Purpose Enters administration configuration mode.
Example:
RP/0/0/CPU0:router(admin)# configure
Step 4
hw-module location slot shutdown
Configures a slot to shut down when the configuration is committed.
Example:
RP/0/0/CPU0:router(admin-config)# hw-module location 0/16/CPU0 shutdown
Caution
Shut down only one CSC or SFC from the combined set of CSCs and SFCs at a time. For example, shut down one CSC or one SFC, but do not shut down two CSCs, two or more SFCs, or cards of both types at the same time. When shutting down a CSC, shutdown the standby CSC.
Step 5
hw-module location slot power disable
Configures a slot to power down when the configuration is committed.
Example:
RP/0/0/CPU0:router(admin-config)# hw-module location 0/16/CPU0 power disable
Step 6
commit

Note
Example:
RP/0/0/CPU0:router(admin-config)# commit
You do not need to enter the end or exit command or press Ctrl-Z to exit administration configuration mode until the end of this procedure. If you exit administration configuration mode, you must re-enter this mode to complete the procedure.
Step 7
end
Example:
Step 8
show platform
(Optional) Displays the state of all cards on the router.
Example:
Allows you to verify that the CSC or SFC you want to replace is shut down and the power is off.
Step 9 Step 10
Remove and replace the CSC or SFC.

configure
Example:
Step 11
no hw-module location slot power disable
Configures a slot to power up when the configuration is committed.
Example:
RP/0/0/CPU0:router(admin-config)# no hw-module location 0/16/CPU0 power disable
8-49
Command or Action
Step 12
commit
Purpose Commits the target configuration to the router running configuration.
Example:
Step 13
end
Example:
Step 14
show platform
Example:
Allows you to verify that the replacement CSC or SFC has power.
Step 15
configure
Example:
Step 16
no hw-module location slot shutdown
Configures a slot to start when the configuration is committed.
Example:
RP/0/0/CPU0:router(admin-config)# no hw-module location 0/16/CPU0 shutdown
Step 17
commit
Example:
Step 18
end
Example:
Step 19
show platform
Example:
Allows you to verify that the replacement CSC or SFC has power and has been brought up.
8-50
Chapter 8
Examples
Replacing a CSC: Example
The following example shows commands to change a CSC:

RP/0/0/CPU0:router# admin RP/0/0/CPU0:router(admin)# show platform Node Type PLIM State Config State ----------------------------------------------------------------------------0/0/CPU0 PRP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/3/CPU0 L3LC Eng 3 OC3-POS-8 IOS XR RUN PWR,NSHUT,MON 0/4/CPU0 L3LC Eng 3 GE-4 IOS XR RUN PWR,NSHUT,MON 0/5/CPU0 L3LC Eng 3 GE-4 IOS XR RUN PWR,NSHUT,MON 0/6/CPU0 L3LC Eng 3 OC48-POS IOS XR RUN PWR,NSHUT,MON 0/7/CPU0 L3LC Eng 3 GE-4 IOS XR RUN PWR,NSHUT,MON 0/8/CPU0 L3LC Eng 3 OC12-POS-4 IOS XR RUN PWR,NSHUT,MON 0/16/CPU0 CSC10 N/A PWD PWR,NSHUT,MON 0/17/CPU0 CSC10(P) N/A PWD PWR,NSHUT,MON 0/18/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/19/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/20/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/21/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/22/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/24/CPU0 ALARM10 N/A PWD PWR,NSHUT,MON 0/25/CPU0 ALARM10 N/A PWD PWR,NSHUT,MON 0/29/CPU0 GSR16-BLOWER N/A PWD PWR,NSHUT,MON RP/0/0/CPU0:router(admin)# configure RP/0/0/CPU0:router(admin-config)# hw-module location 0/16/CPU0 shutdown RP/0/0/CPU0:router(admin-config)# hw-module location 0/16/CPU0 power disable RP/0/0/CPU0:router(admin-config)# commit
Primary Clock is CSC_1 Fabric Clock is Non Redundant Bandwidth Mode : Full Bandwidth RP/0/0/CPU0:router(admin-config)# end
8-51
RP/0/0/CPU0:router(admin)# show platform Node Type PLIM State Config State ----------------------------------------------------------------------------0/0/CPU0 PRP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/3/CPU0 L3LC Eng 3 OC3-POS-8 IOS XR RUN PWR,NSHUT,MON 0/4/CPU0 L3LC Eng 3 GE-4 IOS XR RUN PWR,NSHUT,MON 0/5/CPU0 L3LC Eng 3 GE-4 IOS XR RUN PWR,NSHUT,MON 0/6/CPU0 L3LC Eng 3 OC48-POS IOS XR RUN PWR,NSHUT,MON 0/7/CPU0 L3LC Eng 3 GE-4 IOS XR RUN PWR,NSHUT,MON 0/8/CPU0 L3LC Eng 3 OC12-POS-4 IOS XR RUN PWR,NSHUT,MON 0/16/CPU0 CSC10 N/A Admin Down NPWR,SHUT,MON 0/17/CPU0 CSC10(P) N/A PWD PWR,NSHUT,MON 0/18/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/19/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/20/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/21/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/22/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/24/CPU0 ALARM10 N/A PWD PWR,NSHUT,MON 0/25/CPU0 ALARM10 N/A PWD PWR,NSHUT,MON 0/29/CPU0 GSR16-BLOWER N/A PWD PWR,NSHUT,MON
Replace the CSC or SFC at this point.

RP/0/0/CPU0:router(admin)# configure RP/0/0/CPU0:router(admin-config)# no hw-module location 0/16/CPU0 power disable RP/0/0/CPU0:router(admin-config)# commit
Primary Clock is CSC_1 Fabric Clock is Redundant Bandwidth Mode : Full Bandwidth RP/0/0/CPU0:router(admin-config)# end RP/0/0/CPU0:router(admin)# show platform Node Type PLIM State Config State ----------------------------------------------------------------------------0/0/CPU0 PRP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/3/CPU0 L3LC Eng 3 OC3-POS-8 IOS XR RUN PWR,NSHUT,MON 0/4/CPU0 L3LC Eng 3 GE-4 IOS XR RUN PWR,NSHUT,MON 0/5/CPU0 L3LC Eng 3 GE-4 IOS XR RUN PWR,NSHUT,MON 0/6/CPU0 L3LC Eng 3 OC48-POS IOS XR RUN PWR,NSHUT,MON 0/7/CPU0 L3LC Eng 3 GE-4 IOS XR RUN PWR,NSHUT,MON 0/8/CPU0 L3LC Eng 3 OC12-POS-4 IOS XR RUN PWR,NSHUT,MON 0/16/CPU0 CSC10 N/A Admin Down PWR,SHUT,MON 0/17/CPU0 CSC10(P) N/A PWD PWR,NSHUT,MON 0/18/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/19/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/20/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/21/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/22/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/24/CPU0 ALARM10 N/A PWD PWR,NSHUT,MON 0/25/CPU0 ALARM10 N/A PWD PWR,NSHUT,MON 0/29/CPU0 GSR16-BLOWER N/A PWD PWR,NSHUT,MON RP/0/0/CPU0:router(admin)# configure RP/0/0/CPU0:router(admin-config)# no hw-module location 0/16/CPU0 shutdown
8-52
Chapter 8
RP/0/0/CPU0:router(admin-config)# commit RP/0/0/CPU0:router(admin-config)# end RP/0/0/CPU0:router(admin)# show platform Node Type PLIM State Config State ----------------------------------------------------------------------------0/0/CPU0 PRP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/3/CPU0 L3LC Eng 3 OC3-POS-8 IOS XR RUN PWR,NSHUT,MON 0/4/CPU0 L3LC Eng 3 GE-4 IOS XR RUN PWR,NSHUT,MON 0/5/CPU0 L3LC Eng 3 GE-4 IOS XR RUN PWR,NSHUT,MON 0/6/CPU0 L3LC Eng 3 OC48-POS IOS XR RUN PWR,NSHUT,MON 0/7/CPU0 L3LC Eng 3 GE-4 IOS XR RUN PWR,NSHUT,MON 0/8/CPU0 L3LC Eng 3 OC12-POS-4 IOS XR RUN PWR,NSHUT,MON 0/16/CPU0 CSC10 N/A PWD PWR,NSHUT,MON 0/17/CPU0 CSC10(P) N/A PWD PWR,NSHUT,MON 0/18/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/19/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/20/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/21/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/22/CPU0 SFC10 N/A PWD PWR,NSHUT,MON 0/24/CPU0 ALARM10 N/A PWD PWR,NSHUT,MON 0/25/CPU0 ALARM10 N/A PWD PWR,NSHUT,MON 0/29/CPU0 GSR16-BLOWER N/A PWD PWR,NSHUT,MON
Removing and Replacing CSFC Cards

On Cisco XR 12404 routers, which use consolidated switch fabric cards (CSFCs), you must power off the router before changing a CSFC card. For more information about removing and replacing CSFCs, see the hardware documentation listed in the Related Documents section on page xiv.
Adding a Standby PRP to a Cisco 12000 Series Router

A second PRP card can be added to a Cisco 12000 Series Router for redundancy. To add a standby PRP, boot the card from ROMMON mode with the minimum boot image (MBI) software package. This will bring up the PRP so it can be recognized by the DSC. The new standby PRP will download the appropriate software and configurations from the DSC, and reboot. This section provides instructions to boot the standby RP after it is installed in the chassis. See the Related Documents section on page xiv for more information on installing PRP cards.
Prerequisites
The standby PRP must be installed in a slot next to the active PRP. For example, the PRPs can be installed in slot 0 and slot 1, slot 2 and slot 3, slot 4 and slot 5, slot 6 and slot 7, slot 8 and slot 9, and so on. MBI software package mbiprp-rp.vm. This package is used to boot any PRP other than the DSC, including the standby PRP and PRPs in named SDRs. ROMMON version bfprp_romupgrade-1.14.0.91 or higher Boothelper version c12kprp-boot-mz.120-30.S or higher
8-53
The boothelper must be stored as the first file in the bootflash, or the ROMMON variable must be set to point to the boothelper. To set the ROMMON variable, enter the following command in ROM Monitor mode: BOOTLDR=bootflash:/c12kprp-boot-mz.120-30.S Each PRP must have at least 1024 MB of memory installed. The PRP-2 ships with 1024 MB of memory. Upgrade the memory in your PRP, if necessary. Flash disks:
The recommended flash disk setup for all PRPs is two 512-MB Sandisk flash disk in PCMCIA
slot 0 and slot 1. The minimum requirement is one 512-MB Sandisk flash disk installed in slot 0 on every physical PRP card in the system. PRP cards use the flash disk to store the Cisco IOS XR software and running configurations.
The same flash disk size must be used in all PRPs in the Cisco XR 12000 Series Router. Each flash disk must be formatted by the Cisco IOS XR software before use. To format a disk,
insert the disk into a running PRP and enter the command format disknumber:. Example: format disk0:.
Summary Steps
1. 2. 3. 4. 5. 6. 7. 8.
Attach a terminal to the standby PRP console port, and place the PRP in ROM Monitor mode. unset TURBOBOOT unset BOOT sync boot tftp://server/directory/filename Wait for boot process to complete. show platform show redundancy
DETAILED STEPS
Command or Action
Step 1 Step 2
Purpose Refer to Cisco IOS XR ROM Monitor Guide for more information. Clears the TURBOBOOT variable. The TURBOBOOT variable is only used on the DSC.
Attach a terminal to the standby PRP console port, and place the PRP in ROM Monitor mode.
unset TURBOBOOT
Example:
rommon># unset turboboot
Step 3
unset BOOT
Clears the boot variable.
Example:
rommon># unset BOOT
Step 4
sync
Saves the changes.
Example:
rommon># sync
8-54
Chapter 8
Command or Action
Step 5
boot tftp://server/directory/filename
Purpose Retrieves the file from the TFTP server and installs it on disk0.
Example:
rommon># boot tftp://192.168.1.1/dir/mbiprp-rp.vm
Step 6
Wait for boot process to complete.
The standby PRP will boot and all ROMMON variables (such as confreg and BOOT) will be set. Once the standby PRP is recognized by the DSC, the appropriate software will download and the standby PRP card will reload the Cisco IOS XR software from disk. Displays the status of all cards.
Step 7
show platform
Enter this command on the active PRP. The active and standby PRPs are operating properly when the state for each card is IOS XR RUN. Enter this command on the active PRP. When redundancy is fully established, the partner node is in Standby role and the standby node is ready.
Example:
RP/0/0/CPU0:router# show platform
Step 8
show redundancy
Displays the redundancy status of the PRP cards.
Example:
RP/0/0/CPU0:router# show redundancy
8-55
8-56
C H A P T E R
Troubleshooting the Cisco IOS XR Software

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

Additional Sources for Information, page 9-1 Basic Troubleshooting Commands, page 9-2 Understanding Processes and Threads, page 9-8 Configuration Error Messages, page 9-15 Memory Warnings in Configuration Sessions, page 9-16 Interfaces Not Coming Up, page 9-21
Additional Sources for Information

For additional information on troubleshooting, see the following sources:

If the Cisco IOS XR software does not start and display the EXEC mode prompt, see Cisco IOS XR ROM Monitor Guide. The Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content. http://www.cisco.com/public/support/tac/home.shtml The Related Documents section on page xiv.
9-1
Chapter 9 Basic Troubleshooting Commands
Basic Troubleshooting Commands

The following sections describe some basic techniques used to determine connectivity to another device and display information on the configuration and operation of a router.

Using show Commands to Display System Status and Configuration, page 9-2 Using the ping Command, page 9-4 Using the traceroute Command, page 9-4 Using debug Commands, page 9-5
Using show Commands to Display System Status and Configuration

Use show commands to check the status of various Cisco IOS XR software subsystems and services. Table 9-1 lists some of the common show commands. To display a complete list of the available show commands, enter the show ? command to access the on-screen help system.
Note
Different show commands are available in different command modes, and the same show command can show different results in different command modes.
Table 9-1
Common show Commands in Cisco IOS XR Software
Command show variables boot (EXEC and administration EXEC modes) show configuration (Global configuration and administration configuration modes) show context (and show exception) (EXEC and administration EXEC modes) show controller (Administration EXEC mode) show controllers (EXEC mode) show debug (EXEC and administration EXEC modes) show environment [options] (EXEC and administration EXEC modes)
Description Displays the boot variables.
Displays the uncommitted configuration changes made during a configuration session. This command can be entered in any configuration mode. Displays context information about all recent reloads.
Displays hardware controller information. Displays hardware controller information. Displays debug flags enabled from the current terminal.
Displays hardware information for the physical components and systems, including fans, LEDs, power supply voltage and current information, and temperatures. To view the command options, enter the show environment ? command.
9-2
Chapter 9
Troubleshooting the Cisco IOS XR Software Basic Troubleshooting Commands
Table 9-1
Common show Commands in Cisco IOS XR Software (continued)
Command show exception (EXEC and administration EXEC modes) show install (EXEC and administration EXEC modes) show interfaces (EXEC mode) show logging (EXEC and administration EXEC modes) show memory (EXEC and administration EXEC modes) show platform (EXEC and administration EXEC modes) show processes blocked (EXEC and administration EXEC modes) show redundancy (EXEC and administration EXEC modes) show running-config [command] (EXEC and administration EXEC modes) show tech-support (EXEC and administration EXEC modes) show user [group | tasks | all] (EXEC mode) show version (EXEC and administration EXEC modes)
Description Displays all exception dump configurations.
Displays installed and active software packages.
Displays interface status and configuration. Displays the contents of logging buffers.
Displays memory statistics.
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, enter this command in administration EXEC mode. Displays blocked processes.
Display the status of the primary (active) route processor (RP) and the standby (redundant) RP. Displays the current running configuration.
Collects a large amount of system information for troubleshooting. The output should be provided to technical support representatives when a problem is reported. Because of the impact the command can have on a running system, it is reserved for users assigned to the cisco-support task ID. 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. Displays basic system information.
9-3
Using the ping Command

Use the ping command to diagnose network connectivity. In EXEC mode, enter a hostname or an IP address as an argument to this command. In administration EXEC mode, you can use the fabric or the control Ethernet network (in a multishelf system) to ping other nodes. The ping command sends an echo request packet to a destination, then awaits a reply. Ping output can help you evaluate path-to-destination reliability, delays over the path, and whether the destination can be reached or is functioning. 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 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.233.233.233, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/7 ms
In the next example, an unsuccessful ping attempt is shown:

RP/0/RP0/CPU0:router# ping 10.1.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
The following example shows the output of ping through the fabric:
RP/0/RP1/CPU0:CRS-8_P1(admin)# ping fabric location 0/6/5 Src node: Dest node: Local node: Packet cnt: Hold-off (ms): 529 109 529 1 300 : 0/RP1/CPU0 : 0/6/5 : 0/RP1/CPU0 Packet size: Time-out(s):
128 2
Payload ptn type: default (0) Max retries: 5
Running Fabric node ping. Please wait... Src: 529:, Dest: 109, Sent: 1, Rec'd: 1, Mismatched: 0 Min/Avg/Max RTT: 20000/20000/20000 Fabric node ping succeeded for node: 109
Using the traceroute Command

Use the traceroute command in EXEC mode to discover the routes that packets take when traveling to their destination. Enter a hostname or an IP address as an argument to this command. This command works by taking advantage of the error messages generated by routers when a datagram exceeds its time-to-live (TTL) value.
9-4
Chapter 9
The traceroute command starts by sending probe datagrams with a TTL value of 1, causing the first router to discard the probe datagram and send back an error message. The traceroute command sends several probes at each TTL level and displays the round-trip time for each. The traceroute command sends one probe at a time. Each outgoing packet may result in one or two error messages. A time exceeded error message indicates that an intermediate router has seen and discarded the probe. A destination unreachable error message indicates that the destination node has received the probe and discarded it because it could not deliver the packet. If the timer times out before a response comes in, the traceroute command prints an asterisk (*). The traceroute command terminates when the destination responds, the maximum TTL is exceeded, or the user interrupts the trace with the escape sequence.
Examples
In the following example, the route for an IP address is displayed:
RP/0/RP0/CPU0:router# traceroute 10.233.233.233 Type escape sequence to abort. Tracing the route to 10.233.233.233 1 2 172.25.0.2 11 msec 2 msec 1 msec 192.255.254.254 1 msec * 2 msec
Using debug Commands

Debug commands are used to diagnose and resolve network problems. Use debug commands to troubleshoot specific problems or during troubleshooting sessions. Use debug commands to turn on or off debugging for a specific service or subsystem. When debugging is turned on for a service, a debug message is generated each time the debugging code section is entered. The following sections provide information on debugging:

Displaying a List of Debug Features, page 9-6 Enabling Debugging for a Feature, page 9-6 Disabling Debugging for a Service, page 9-7 Displaying Debugging Status, page 9-7
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.
9-5
Displaying a List of Debug Features

To display a list of the available debug features, enter the debug mode and enter a ? for on-screen help. The set of debug mode features is different in EXEC and administration EXEC modes. In the following example, EXEC mode is the entry point to debug mode:
RP/0/RP0/CPU0:router# debug RP/0/RP0/CPU0:router(debug)# ? aaa adjacency adjacency aib alarm-logger arm arp asic-errors asic-scan --More-AAA Authentication, Authorization and Accounting Adjacency debug platform AIB information AIB information Turn on alarm debugging IP Address Repository Manager IP ARP transactions Debug ASIC erors Debug Asic Scan
In the next example, administration EXEC mode is the entry point to debug mode:
RP/0/RP1/CPU0:CRS-8_P1# admin RP/0/RP1/CPU0:CRS-8_P1(admin)# debug RP/0/RP1/CPU0:CRS-8_P1(admin-debug)# ? cctl Chassis control driver process debug cetftp Control ethernet TFTP (CE-TFTP) server process debug cpuctrl Debug Cpuctrl Driver describe Describe a command without taking real actions diagnostic Diagnostic debugging dsc dsc debug: all, fsm, table, cfg, and api dumper Admin Debug Dumper exit Exit from this submode fabric Fabric debugging fabricq Debug Fabric Queue Manager fia Debug the Fabric Interface ASIC (FIA) driver gsp Admin Debug gsp ingressq Debug Ingress Queue Manager install Install debug information inv Inventory manager process debug invd Inventory debug: all, trap, dll mem invmgr Inventory Manager client API interface debug ntp NTP information oird oird all, event, message pair DRP Pairing debug: Display debugging messages of drp_pairing shelfmgr Shelfmgr debug: all, heartbeat, boot, fsm, init and eah sysdb Configure SysDB debug settings upgrade-fpd Debug upgrade fpd --More--
Enabling Debugging for a Feature

To enable debugging for a feature, enter the debug command in EXEC or administration EXEC mode and then enable the feature for debugging. For example:
RP/0/RP0/CPU0:router# debug RP/0/RP0/CPU0:router(debug)# aaa all RP/0/RP0/CPU0:router(debug)# exit
You can also enter the complete command from EXEC mode, as shown in the following example:
RP/0/RP0/CPU0:router# debug aaa all
9-6
Chapter 9
Displaying Debugging Status

Enter the show debug command to display the debugging features enabled for your terminal session. The terminal session is labeled tty and represents your connection to the router through a specific port, which might be the console port, auxiliary port, or Management Ethernet interface. In the following example, the command display indicates that debugging is enabled for two features (AAA and ipv4 io icmp) from a terminal session on the console port of RP1:
RP/0/RP0/CPU0:router# show debug #### debug flags set from tty 'con0_RP1_CPU0' aaa all flag is ON ipv4 io icmp flag is ON RP/0/RP0/CPU0:router# no debug aaa all RP/0/RP0/CPU0:router# show debug #### debug flags set from tty 'con0_RP1_CPU0' ipv4 io icmp flag is ON #### ####
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 #### debug conditions set from tty 'con0_RP1_CPU0' #### interface condition is ON for interface 'POS0/2/0/1'
Disabling Debugging for a Service

Use the no form of the debug command or the undebug command to turn off debugging for a service or subsystem. In the following example, the no debug command disables debugging for the AAA feature:
RP/0/RP0/CPU0:router# no debug aaa all RP/0/RP0/CPU0:router# show debug #### debug flags set from tty 'con0_RP1_CPU0' ipv4 io icmp flag is ON ####
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 No matching debug flags set
9-7
Chapter 9 Understanding Processes and Threads
Disabling Debugging for All Services Started at All Terminal Sessions

Use the undebug all all-tty command to turn off debugging for all services that have been started from all terminal sessions. For example if you enter this command while connected to the router through the console port on the active RP, all debug sessions started from all ports are disabled. In the following example, debugging for all services and ports is disabled and then verified:
RP/0/0/CPU0:router# undebug all all-tty RP/0/0/CPU0:router# show debug No matching debug flags set
Understanding Processes and Threads

To achieve high availability and performance, the Cisco IOS XR software is built on a modular system of processes. Each process provides specific functionality for the system and runs in a protected memory space to ensure problems with one process cannot impact the entire system. Multiple instances of a process can run on a single node, and multiple threads of execution can run on each process instance. Table 9-2 provides a summary of terms for processes and threads in the Cisco IOS XR software.
Table 9-2 Process and Thread Syntax and Descriptions
Term Process
CLI Syntax
Description
A process is a group of threads that share a protected memory space. Processes run independently of other processes and can be individually started, restarted, or executable-name stopped. Process name In the command-line interface (CLI) syntax, the process name (or executable-name) identifies all instances of a process on a node. Usage example: To change the core-dumping options for all instances of a process, specify the executable-name of the process.
Process instance
JID job-ID
Multiple instances of a process can run simultaneously on a node. In the CLI, the process instance is shown as the job ID. Usage example: To change the core-dumping options for only a single instance of a process, specify the job-ID of the process instance.
Thread
TID thread-ID
A thread is a unit of execution within a process. Multiple threads can run inside each instance of a process (known as multithreading). Each thread is assigned a thread ID number.
Under normal operating conditions, processes are managed automatically by the Cisco IOS XR software. Processes are started, stopped, or restarted as required by the running configuration of the router. In addition, processes are checkpointed to optimize performance during process restart and automatic switchover. Figure 9-1 illustrates how the Cisco IOS XR software manages the operations of processes and acts as a message, passing bus to coordinate interactions between processes. In this way, processes can run independently, but still communicate and cooperate with other processes. If a process needs to be stopped or restarted, it affects only that process and related processes and threads.
9-8
Chapter 9
Troubleshooting the Cisco IOS XR Software Understanding Processes and Threads
Figure 9-1
Modular Process Architecture in Cisco IOS XR Software
"Message passing bus Processes OS
etc... Microkernel
116545
Process manager
Processes
Commands Used to Display Process and Thread Details

Table 9-3 describes some of the commands used to display information on the processes and threads running on a router. For complete details on the commands and options related to process and thread management, see the Cisco IOS XR System Management Command Reference.
Table 9-3 Commands to Display Process and Thread Information
Command monitor processes (EXEC and administration EXEC modes)
Description Displays the ten most active processes and the current CPU usage. The output from this command continually refreshes until quit (enter the q-key to quit). Displays interactive, auto-updating process and thread statistics in a full-screen mode. Displays information about active processes. Displays process aborts. Displays details for reply, send, and mutually exclusive (mutex) blocked processes. Displays process boot information. Displays CPU use for each process.
monitor threads (EXEC and administration EXEC modes) show processes (EXEC and administration EXEC modes) show processes aborts (EXEC and administration EXEC modes) show processes blocked (EXEC and administration EXEC modes) show processes boot (EXEC and administration EXEC modes) show processes cpu (EXEC mode)
9-9
Table 9-3
Commands to Display Process and Thread Information (continued)
Command show processes dynamic (EXEC and administration EXEC modes) show processes failover (EXEC and administration EXEC modes) show processes log (EXEC and administration EXEC modes) show processes memory (EXEC and administration EXEC modes) show processes startup (EXEC and administration EXEC modes)
Description Displays process data for dynamically created processes. Displays process automatic switchover information. Displays the process log. Shows memory use for each process. Shows process data for processes created at startup.
Examples
The following examples show the output and heading descriptions for commands commonly used to display information on processes and process memory usage:

show processes Command, page 9-10 show processes process-name Command, page 9-11 show processes memory Command, page 9-12 monitor processes Command, page 9-13
show processes Command

To display the running processes and information, such as the name, ID number, and state of the processes, enter the show processes command in EXEC or administration EXEC mode. Table 9-4 describes the column heading output.
Table 9-4 Column Heading Descriptions for show processes Output
Output Heading JID TID
Description Job IDIn the CLI, the process instance is shown as the job ID (multiple instances of a process can run simultaneously on a node). Thread IDA thread is a unit of execution within a process. Multiple threads can run inside each instance of a process (known as multithreading). Each thread is assigned a thread ID number.
Stack pri state HR:MM:SS:MSEC NAME
Size of the memory stack of the process. Process priority. Process state. Time the process has run since starting. Process name.
9-10
Chapter 9
The following is sample output from the show processes command:

RP/0/RP1/CPU0:CRS-8_P1# show processes JID TID 1 1 1 2 1 3 1 4 1 5 1 6 1 7 1 8 1 9 1 10 1 11 1 12 1 13 1 16 1 18 1 21 1 26 1 27 1 28 1 29 1 30 1 31 --More-Stack pri state 0K 0 Ready 0K 63 Receive 0K 10 Nanosleep 0K 63 Receive 0K 10 Receive 0K 63 Receive 0K 63 Receive 0K 63 Receive 0K 63 Receive 0K 63 Receive 0K 63 Receive 0K 63 Receive 0K 63 Receive 0K 10 Receive 0K 10 Receive 0K 10 Receive 0K 10 Receive 0K 10 Receive 0K 10 Receive 0K 10 Receive 0K 10 Receive 0K 10 Running HR:MM:SS:MSEC 10:06:42:0191 0:00:00:0000 0:00:00:0002 0:00:00:0000 0:00:01:0030 0:00:00:0000 0:00:00:0000 0:00:00:0000 0:00:00:0000 0:00:00:0000 0:00:00:0000 0:00:00:0000 0:00:00:0000 0:00:00:0000 0:00:00:0000 0:00:01:0693 0:00:00:0000 0:00:00:0001 0:00:00:0000 0:00:00:0000 0:00:00:0000 0:00:21:0855 NAME procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr procnto-600-smp-cisco-instr
show processes process-name Command

The show processes process-name command displays detailed information about a process. Table 9-5 describes the heading output.
Table 9-5 Heading Descriptions for show processes process-name Output
Output Heading JID
Description Job IDThis remains constant over process restarts. In the CLI, the process instance is shown as the job ID (multiple instances of a process can run simultaneously on a node).
PID Executable path Instance Version ID Respawn Respawn count Max. spawns per minute Last started
Process IDThis changes when process is restarted. Path for the process executable. Instance of the process. More than one instance of a process may run at a given time (each instance may have more than one thread). API version. ON or OFFDetermines if this process restarts automatically in case of failure. Number of times this process has been (re)started (that is, the first start makes this count 1). Number of respawns not to be exceeded in 1 minute. If this number is exceeded, stop restarting. Date and time the process was last started.
9-11
Table 9-5
Heading Descriptions for show processes process-name Output (continued)
Output Heading Process state Started on config core Max. core
Description Current state of the process. Configuration command that started (or would start) this process. Memory segments to include in a core file. Number of times to dump a core file0 = infinity.
The following is sample output from the show processes command:

RP/0/RP1/CPU0:CRS-8_P1# show processes ospf Job Id: 292 PID: 241787 Executable path: /disk0/hfr-rout-3.3.90/bin/ospf Instance #: 1 Version ID: 00.00.0000 Respawn: ON Respawn count: 1 Max. spawns per minute: 12 Last started: Sat Apr 15 13:05:34 2006 Process state: Run Package state: Normal Started on config: cfg/gl/ipv4-ospf/proc/10/ord_f/default/ord_a/routeridf core: TEXT SHAREDMEM MAINMEM Max. core: 0 Placement: ON startup_path: /pkg/startup/ospf.startup Ready: 2.024s Available: 6.030s Process cpu time: 1.558 user, 0.139 kernel, 1.697 total JID TID Stack pri state HR:MM:SS:MSEC NAME 292 1 60K 10 Receive 0:00:00:0287 ospf 292 2 60K 10 Receive 0:00:00:0002 ospf 292 3 60K 10 Receive 0:00:00:0025 ospf 292 4 60K 10 Receive 0:00:01:0239 ospf 292 5 60K 10 Receive 0:00:00:0004 ospf 292 6 60K 10 Condvar 0:00:00:0001 ospf 292 7 60K 10 Receive 0:00:00:0000 ospf -------------------------------------------------------------------------------
show processes memory Command

The show processes memory command displays details of memory usage for a given process or all processes, as shown in the following example. Table 9-6 describes the column heading output.
Table 9-6 Column Heading Descriptions for show process memory Output
Output Heading JID
Description Job ID. In the CLI, the process instance is shown as the job ID (multiple instances of a process can run simultaneously on a node). Size of text region (process executable). Size of data region (initialized and uninitialized variables). Size of process stack.
Text Data Stack
9-12
Chapter 9
Table 9-6
Column Heading Descriptions for show process memory Output (continued)
Output Heading Dynamic Process
Description Size of dynamically allocated memory. Process name.
The following is sample output from the show processes memory command:
RP/0/RP0/CPU0:router# show processes memory JID Text 55 28672 164 143360 317 167936 122 512000 265 57344 254 40960 63 8192 314 4096 341 495616 259 53248 189 32768 69 77824 348 323584 347 323584 346 323584 345 323584 344 323584 261 323584 --More-Data 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 Stack 69632 20480 45056 77824 57344 143360 24576 36864 40960 28672 32768 110592 40960 40960 40960 40960 40960 40960 Dynamic 17072128 13238272 10526720 9797632 5877760 3084288 2314240 1699840 1576960 1490944 1425408 1421312 1392640 1392640 1392640 1392640 1392640 1392640 Process eth_server hfr_fgid_server syslogd bgp parser_server netio nvram sysdb_svr_local wdsysmon nvgen_server hd_drv qnet ospf ospf ospf ospf ospf ospf
monitor processes Command

This command shows the top ten processes of CPU usage. The display refreshes every 10 seconds. Table 9-7 describes the heading output. To change the monitor processes command to display parameters or terminate the display and return to the system prompt, see the interactive display characters described in Table 9-8.
Table 9-7 Heading Descriptions for monitor process Output
Output Heading JID
Description Job ID. In the CLI, the process instance is shown as the job ID (multiple instances of a process can run simultaneously on a node). Thread IDA thread is a unit of execution within a process. Multiple threads can run inside each instance of a process (known as multithreading). Each thread is assigned a thread ID number.
TIDS
Chans FDs Tmrs
Channels (client connections) to the server. Number of files open. Number of timers for the process.
9-13
Table 9-7
Heading Descriptions for monitor process Output (continued)
Output Heading MEM HH:MM:SS CPU NAME
Description Total memory of the process. Run time of process since last restart. Percentage of CPU used by process thread. Process name.
The following is sample output from the monitor processes command:

RP/0/RP1/CPU0:CRS-8_P1# monitor processes Computing times... 225 processes; 776 threads; 4314 channels, 5757 fds CPU states: 97.8% idle, 1.0% user, 1.0% kernel Memory: 4096M total, 3534M avail, page size 4K JID TIDS Chans 1 33 228 59 11 23 333 8 39 74 12 190 65759 1 1 282 11 80 155 4 35 182 16 107 362 5 6 318 19 21 FDs Tmrs 176 1 13 6 35 12 9 3 14 0 80 12 33 6 39 10 38 2 64 5 MEM 0 36M 1M 1M 720K 1M 636K 3M 1M 680K HH:MM:SS 10:19:42 0:02:07 0:00:41 0:00:57 0:00:00 0:00:05 0:00:29 0:00:37 0:00:02 0:00:01 CPU 1.06% 0.43% 0.19% 0.13% 0.09% 0.05% 0.05% 0.01% 0.01% 0.01% NAME procnto-600-smp-cisco-i eth_server shelfmgr qnet ptop netio dsc gsp top_procs raw_ip
To list the interactive commands, type ? during the display. The options are described in Table 9-8.
Table 9-8 Interactive Display Commands for the monitor processes Command
Command Description ? q n d k l t m c f Displays or prints the interactive commands. Quits the monitor processes display and returns to the system prompt. Changes the number of processes to be displayed. Changes the delay interval between updates. Kills a process. Refreshes the screen. Sorts the display by time (default). Sorts the display by memory used. Sorts the display by number of open channels. Sorts the display by number of open files.
Commands Used to Manage Process and Threads

Table 9-9 describes the commands used to reset the options for a thread or to manually stop, start, and restart a process.
9-14
Chapter 9
Troubleshooting the Cisco IOS XR Software Configuration Error Messages
For complete details on the commands and options related to process and thread management, see the Cisco IOS XR System Management Command Reference.
Caution
Manually stopping, starting, or restarting a process can seriously impact the operation of a router. Use these commands only under the direction of a technical support representative.
Table 9-9
Commands to Manage Processes
Command process {shutdown | restart | start} process process mandatory {on | off} process process mandatory reboot {enable | disable} location {nodeID | all}
Description Manually stops, starts, or restarts a process or process instance. Changes the mandatory setting for a process. Changes how the system reacts to mandatory processes that go down.
Configuration Error Messages

The following sections contain information on configuration error messages:

Configuration Failures During a Commit Operation, page 9-15 Configuration Errors at Startup, page 9-16
Configuration Failures During a Commit Operation

A target configuration is added to the running configuration of a router when the commit command is entered. During this operation, the changes are automatically verified by the other components in the system. If successful, the configuration becomes part of the running configuration. If some configuration items fail, an error message is returned. To display the configuration items that failed and see the cause of each failure, enter the show configuration failed command.
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
9-15
Chapter 9 Memory Warnings in Configuration Sessions
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 !! CONFIGURATION FAILED DUE TO SEMANTIC ERRORS taskgroup bgp !!% Usergroup/Taskgroup names cannot be taskid names !
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 !! CONFIGURATION FAILED DUE TO SEMANTIC ERRORS taskgroup bgp
Configuration Errors at Startup

Configuration errors that occurred during system startup can be displayed with the show configuration failed startup command. For example:
RP/0/RP0/CPU0:router# show configuration failed startup !! CONFIGURATION FAILED DUE TO SYNTAX ERRORS ntp xml agent corba http server
Memory Warnings in Configuration Sessions

The Cisco IOS XR software automatically monitors and manages the system resources in a router. Under normal operating conditions, memory problems should not occur. When a low-memory issue does occur, it is often in the form of a low-memory warning during a configuration session. Low-memory conditions can be caused by multiple, large configurations being added to the router at a single time. Users can remove the source of a problem by removing configurations. The following sections describe the commands used to display memory usage in a router and what to do if a low-memory warning appears:

Understanding Low-Memory Warnings in Configuration Sessions, page 9-17 Displaying System Memory Information, page 9-18 Removing Configurations to Resolve Low-Memory Warnings, page 9-19 Contacting TAC for Additional Assistance, page 9-21
9-16
Chapter 9
Troubleshooting the Cisco IOS XR Software Memory Warnings in Configuration Sessions
Understanding Low-Memory Warnings in Configuration Sessions

The Cisco IOS XR software monitors memory usage in the Cisco CRS-1 router. If system memory becomes low, an error message is displayed when you attempt to enter configuration mode. An out-of-memory error message is displayed during one of the following situations:

When a user attempts to enter configuration mode. During a configuration session when the memory shortage occurs. When a user attempts to load a target configuration from a large file that results in a memory shortage. During a commit operation that results in the low-memory warning message. The commit operation is denied and only lr-root users can perform commit operations to remove configurations.
Caution
Never ignore a low-memory warning. These warnings indicate a memory state that could affect system operations if not addressed.
WARNING! MEMORY IS IN MINOR STATE

If the system memory begins to run low, the following minor memory warning is displayed when you enter a new configuration mode.
WARNING! MEMORY IS IN MINOR STATE
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 9-19. Failure to take action can result in a worsening situation and eventual impact to router operations.
ERROR! MEMORY IS IN SEVERE (or CRITICAL) STATE

When the memory is in a severe or critical state, router operation and performance is likely to be affected. Regular users are not allowed to enter configuration mode. Only lr-root owners can enter configuration mode to free memory by removing configurations. In some situations, the commit command is not allowed. Users with lr-root access can still use the commit force command to apply configurations that reduce memory usage. Reducing memory usage normally means removing configurations, but a user can also add configurations that reduce memory usage. For example, configuring the shutdown command on an interface could cause numerous routes to be purged from Border Gateway Protocol (BGP), the Routing Information Base (RIB), and Forwarding Information Base (FIB) configurations.
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.
9-17
Displaying System Memory Information

To display a high level summary of system memory, enter the show memory summary command. Table 9-9 describes the meaning of each heading.
RP/0/RP0/CPU0:router# show memory summary Physical Memory: 2048M total Application Memory : 1787M (1509M available) Image: 132M (bootram: 132M) Reserved: 128M, IOMem: 0, flashfsys: 0 Total shared window: 0 RP/0/RP1/CPU0:router#
To display general memory usage for the device as a whole and by process, enter the show memory command. Table 9-9 describes the meaning of each heading.
RP/0/RP0/CPU0:router# show memory Physical Memory: 2048M total Application Memory : 1787M (1510M available) Image: 132M (bootram: 132M) Reserved: 128M, IOMem: 0, flashfsys: 0 Total shared window: 0 kernel: jid 1 Address Bytes 000d2000 12288 00112000 12288 Total Allocated Memory: 0 Total Shared Memory: 0 pkg/bin/wd-mbi: Address 4817f000 48180000 481fe000 48200000 --More-jid 72 Bytes 4096 516096 8192 8192
What Program Stack Program Stack
What Program Program Program Program
Stack (pages not allocated) Stack (pages not allocated) Stack Text
Table 9-10
Heading Descriptions for show memory Command Output
Heading Physical Memory Application Memory Image Reserved IOMem flashfsys Process and JID Address Bytes What
Description Amount of physical memory installed on the device. Memory available for the system to use (total memory minus image size, reserved, IOMem, and flashfsys). Size of the bootable image. Reserved for packet memory. IO memoryCurrently used as a backup for packet memory. Flash file system memory. Process and job ID. Starting address in memory. Size of memory block. Block description.
9-18
Chapter 9
Troubleshooting the Cisco IOS XR Software Memory Warnings in Configuration Sessions
Removing Configurations to Resolve Low-Memory Warnings

To resolve most low-memory problems, you should remove the configurations from the router that are consuming the most memory. Often, memory problems occur when a large new configuration is added to the system. The following sections provide information to resolve low-memory issues:

Clearing a Target Configuration, page 9-19 Removing Committed Configurations to Free System Memory, page 9-19 Rolling Back to a Previously Committed Configuration, page 9-20 Clearing Configuration Sessions, page 9-20
Clearing a Target Configuration

A low-memory warning can occur when a large configuration file is loaded into a target configuration session. To remove the target configuration, enter the clear command to discard the changes. For example:
RP/0/RP0/CPU0:router(config)# clear
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.
Removing Committed Configurations to Free System Memory

You can reduce memory usage by removing configurations from the router, as shown in the following procedure:
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 Physical Memory: 2048M total Application Memory : 1787M (1511M available) Image: 132M (bootram: 132M) Reserved: 128M, IOMem: 0, flashfsys: 0 Total shared window: 0
Step 2
Enter the show configuration commit history command in EXEC or administration EXEC mode to see if a large configuration forced the router over the limit.
9-19
The output from this command does not show the details of the entries, but allows you to display a larger list of the commit events that occurred. To display the commitIDs to which you can roll back, use the show configuration commit history command.
RP/0/RP0/CPU0:router# show configuration commit history SNo. ~~~~ 1 2 3 4 5 6 7 8 9 10 Label/ID ~~~~~~~~ 1000000144 1000000143 1000000142 1000000141 1000000140 1000000139 1000000138 1000000137 1000000136 1000000135 User ~~~~ user user user user cisco user user cisco user cisco Line ~~~~ vty0 vty0 0.0.0.0 0.0.0.0 con0_RP1_C 0.0.0.0 0.0.0.0 con0_RP1_C 0.0.0.0 con0_RP1_C Client ~~~~~~ CLI CLI XMLAgent XMLAgent CLI XMLAgent XMLAgent CLI XMLAgent CLI Time Stamp ~~~~~~~~~~ 00:16:51 UTC 00:04:32 UTC 21:58:36 UTC 21:46:07 UTC 21:43:30 UTC 21:40:13 UTC 21:34:48 UTC 21:32:10 UTC 21:30:13 UTC 19:45:04 UTC
Thu Thu Wed Wed Wed Wed Wed Wed Wed Wed
Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec
11 11 10 10 10 10 10 10 10 10
2003 2003 2003 2003 2003 2003 2003 2003 2003 2003
Step 3
Enter the show configuration commit changes command followed by a commitID number to display the configuration changes for a commit session (commitID). For example:
RP/0/RP0/CPU0:router# show configuration commit changes 1000000053 Building configuration... interface preconfigure MgmtEth0/RP1/CPU0/0 ipv4 address 10.8.50.10 255.255.0.0 proxy-arp ! router static address-family ipv4 unicast 172.255.254.254/32 12.8.0.1 ! ! end
Step 4
Remove the configuration using the appropriate configuration commands. In some situations, the commit command is not allowed. Users with lr-root access can still use the commit force command, but this command should be used only to remove configurations. The addition of new configurations seriously impacts router operation.
For more information, see the Managing Configuration History and Rollback section on page 5-3.
Rolling Back to a Previously Committed Configuration

You can roll back the system to a previous committed configuration, as described in the Managing Configuration History and Rollback section on page 5-3.
Clearing Configuration Sessions

Active configuration sessions and their associated target configurations can consume system memory. Users with the appropriate access privileges can display the open configuration sessions of other users and terminate those sessions, if necessary (see Table 9-11).
9-20
Chapter 9
Troubleshooting the Cisco IOS XR Software Interfaces Not Coming Up
Table 9-11
Session Commands
Command show configuration sessions clear configuration sessions session-id
Description Displays the active configuration sessions. 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 Session 00000211-002c409b-00000000 Line User Date con0_RP1_CPU0 UNKNOWN Mon Feb Lock 2 01:02:09 2004
RP/0/RP0/CPU0:router# clear configuration sessions 00000211-002c409b-00000000 session ID '00000211-002cb09b-00000000' terminated
Contacting TAC for Additional Assistance

If you remove configurations and the low-memory condition remains, you may need to contact TAC for additional assistance. See the Additional Sources for Information section on page 9-1.
Interfaces Not Coming Up

The router interfaces are directly used in processing network traffic, so their status information is crucial to understanding how the device is functioning. This section contains information on the EXEC mode commands used to verify that the router interfaces are operational. The basic commands used in this process are summarized in Table 9-12.
Table 9-12 show interface Commands
Command show interfaces
Description 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 show ipv6 interface show ipv4 interface brief show ipv6 interface brief
Displays basic, IP-related information for all available interfaces. Quickly displays the most critical information about the interfaces, including the interface status (up or down) and the protocol status.
9-21
Chapter 9 Interfaces Not Coming Up
Verifying the System Interfaces

Perform the following steps to verify the system interfaces.
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 Node Type PLIM State Config State ----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/1/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/2/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/2/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/3/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/3/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON 0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON
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. Enter the show ipv4 interface brief command to verify IP address configuration and protocol status:
RP/0/RP0/CPU0:router# show ipv4 interface brief Interface POS0/1/0/0 POS0/1/0/1 POS0/1/0/2 POS0/1/0/3 POS0/1/0/4 POS0/1/0/5 POS0/1/0/6 POS0/1/0/7 POS0/1/0/8 POS0/1/0/9 POS0/1/0/10 POS0/1/0/11 POS0/1/0/12 POS0/1/0/13 POS0/1/0/14 POS0/1/0/15 POS0/2/0/0 POS0/2/0/1 POS0/2/0/2 POS0/2/0/3 TenGigE0/3/0/0 TenGigE0/3/0/2 MgmtEth0/RP0/CPU0/0 IP-Address unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned 10.10.1.101 unassigned unassigned unassigned unassigned unassigned unassigned Status Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Down Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Protocol Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down
Step 2
9-22
Chapter 9
Troubleshooting the Cisco IOS XR Software Interfaces Not Coming Up
Step 3
Configure the interfaces, as shown in the following examples.
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 Interface POS0/1/0/0 POS0/1/0/1 POS0/1/0/2 POS0/1/0/3 POS0/1/0/4 POS0/1/0/5 POS0/1/0/6 POS0/1/0/7 POS0/1/0/8 POS0/1/0/9 POS0/1/0/10 POS0/1/0/11 POS0/1/0/12 POS0/1/0/13 POS0/1/0/14 POS0/1/0/15 POS0/2/0/0 POS0/2/0/1 POS0/2/0/3 POS0/2/0/3 TenGigE0/3/0/0 TenGigE0/3/0/2 MgmtEth0/RP0/CPU0/0 IP-Address unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned 10.10.1.101 10.1.1.1 10.1.1.2 unassigned unassigned unassigned unassigned Status Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Up Up Shutdown Shutdown Shutdown Shutdown Shutdown Protocol Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Up Up Down Down Down Down Down
9-23
Chapter 9 Interfaces Not Coming Up
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 !
b.
Bring the interface up with the following commands:

RP/0/RP0/CPU0:router(config)# controller pos 0/2/0/3 RP/0/RP0/CPU0:router(config-sonet)# no shutdown RP/0/RP0/CPU0:router(config-sonet)# commit RP/0/RP0/CPU0:router(config-sonet)# exit RP/0/RP0/CPU0:router(config)# interface pos 0/2/0/3 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#
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-4ALARM : 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 Interface POS0/1/0/0 POS0/1/0/1 POS0/1/0/2 POS0/1/0/3 POS0/1/0/4 POS0/1/0/5 POS0/1/0/6 POS0/1/0/7 POS0/1/0/8 POS0/1/0/9 POS0/1/0/10 POS0/1/0/11 POS0/1/0/12 POS0/1/0/13 POS0/1/0/14 POS0/1/0/15 POS0/2/0/0 POS0/2/0/1 POS0/2/0/2 POS0/2/0/3 TenGigE0/3/0/0 TenGigE0/3/0/2 MgmtEth0/RP0/CPU0/0 IP-Address unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned 10.10.1.101 10.1.1.1 10.1.1.2 unassigned unassigned unassigned unassigned Status Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Shutdown Up Up Up Shutdown Shutdown Shutdown Shutdown Protocol Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Up Up Up Down Down Down Down
Step 8
Repeat these steps for every interface, until every interface shows both Status and Protocol as Up.
9-24
A P P E N D I X
Understanding Regular Expressions, Special Characters, and Patterns

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-10. 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 (AZ and az), digits (09), and other keyboard characters (such as ! or ~) can be used as a single-character pattern.
A-1
Appendix A Special Characters
Special Characters
Certain keyboard characters have special meaning when used in regular expressions. Table A-1 lists the keyboard characters that have special meaning.
Table A-1 Characters with Special Meaning
Character . * + ? ^ $ _ (underscore)
Special Meaning Matches any single character, including white space. Matches 0 or more sequences of the pattern. Matches 1 or more sequences of the pattern. Matches 0 or 1 occurrences of the pattern. Matches the beginning of the string. Matches the end of the string. Matches a comma (,), left brace ({), right brace (}), left parenthesis ( ( ), right parenthesis ( ) ), the beginning of the string, the end of the string, or a space.
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. \$ \_ \+
Character Pattern Ranges

A range of single-character patterns can be used to match command output. To specify a range of single-character patterns, enclose the single-character patterns in square brackets ([ ]). Only one of these characters must exist in the string for pattern-matching to succeed. For example, [aeiou] matches any one of the five vowels of the lowercase alphabet, while [abcdABCD] matches any one of the first four letters of the lowercase or uppercase alphabet. You can simplify a range of characters by entering only the endpoints of the range separated by a dash (), as in the following example: [adAD] To add a dash as a single-character pattern in the search range, include another dash and precede it with a backslash: [adAD\] A bracket (]) can also be included as a single-character pattern in the range: [adAD\\]] Invert the matching of the range by including a caret (^) at the start of the range. The following example matches any letter except the ones listed: [^adqsv] The following example matches anything except a right square bracket (]) or the letter d: [^\]d]
A-2
Appendix A
Understanding Regular Expressions, Special Characters, and Patterns Multiple-Character Patterns
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.
Complex Regular Expressions Using Multipliers

Multipliers can be used to create more complex regular expressions that instruct Cisco IOS XR software to match multiple occurrences of a specified regular expression. Table A-2 lists the special characters that specify multiples of a regular expression.
Table A-2 Special Characters Used as Multipliers
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])+
A-3
Appendix A Pattern Alternation
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.
Table A-3 Special Characters Used for Anchoring
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_.
Parentheses Used for Pattern Recall

Use parentheses with multiple-character regular expressions to multiply the occurrence of a pattern. The Cisco IOS XR software can remember a pattern for use elsewhere in the regular expression.
A-4
Appendix A
Understanding Regular Expressions, Special Characters, and Patterns Parentheses Used for Pattern Recall
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-5
Appendix A Parentheses Used for Pattern Recall
A-6
G L O S S A RY
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. 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). 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. The RP that is active in a redundant pair of RPs. The software configuration marked as active for a node. The set of Cisco IOS XR software packages activated in one or more nodes in a router. 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. automatic protection switching. A method that allows transmission equipment to recover automatically from failures, such as a cut cable. 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.
ACL
active
active RP active software configuration active software set algorithm
APS
ASIC
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. 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.
BGP
GL-1
Glossary
C
card type CDP
The type of the card inserted in a slot. 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. The Cisco website 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. The configuration stored in the system for a particular node. The RP loads the committed configuration into memory at startup. In Cisco routers, a 16-bit, user-configurable value that determines how the router functions during 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). 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. 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. 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. Craft Works Interface. Graphical user interface (GUI) used to configure and operate a router. The CWI client runs in a web browser.
Cisco.com CLI
committed/saved software configuration configuration register
control plane
CORBA
CoS
CWI
D
DDTS DHCP
distributed defect tracking system. A method to track software errors and resolutions. Dynamic Host Configuration Protocol. Provides a mechanism for allocating IP addresses dynamically so that addresses can be reused when hosts no longer need them.
GL-2
Glossary
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). Name of the flash disk on which the Cisco IOS XR software is stored. Name of the optional flash disk on which the Cisco IOS XR software can be stored in preparation for installation or upgrade. 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. Dynamic Packet Transport. DPT rings are dual, counter-rotating fiber rings. Both fibers are used concurrently to transport both data and control traffic. 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.
disk0 disk1
DNS
DPT
DSC
E
eBGP
external Border Gateway Protocol. BGP sessions are established between routers in different autonomous systems. eBGPs communicate among different network domains. error correction code. ECC is used to correct errors within memories on the Cisco CRS-1 router. Outgoing channel. 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.
ECC egress Ethernet
F
fabric fabric cable
Connectivity between all line cards. Also referred to as switch fabric. 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. 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. 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. 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.
FC
FIB
flooding
GL-3
Glossary
forwarding FRR
Process of sending a frame toward its ultimate destination by way of an internetworking device. 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. 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.
FTP
G
GE
Gigabit Ethernet. Standard for a high-speed Ethernet, approved by the IEEE 802.3z standards committee in 1996. Standard for a high-speed Ethernet, approved by the IEEE 802.3z standards committee in 1996. 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.
Gigabit Ethernet GUI
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. 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. A number system having 16 as its base. This number representation uses the digits 09, with their usual meaning, plus the letters AF (or af) 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.
HDLC
hexadecimal
hop
Passage of a data packet between two network nodes (for example, between two routers). See also hop count. Routing metric used to measure the distance between a source and a destination. 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.
hop count HTTP
GL-4
Glossary
I
ICMP
Internet Control Message Protocol. Network layer Internet (TCP/IP) protocol that reports errors and provides other information relevant to IP packet processing. IP explicit path. List of IP addresses, each representing a node or link in the explicit path. 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. 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. 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. Incoming channel. The set of Cisco IOS XR software packages installed on a router. The Cisco operating system used on the Cisco CRS-1 router and Cisco XR 12000 Series Router. 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. IP Version 4. Network layer for the TCP/IP protocol suite. A connectionless, best-effort packet switching protocol. 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. Internetwork Packet Exchange. NetWare network layer (Layer 3) protocol used for transferring data from servers to workstations. IPX is similar to IP and XNS. 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.
IEP IETF
IGMP
IGP
ingress installed software set IOS XR IP
IPv4
IPv6
IPX
IS-IS
GL-5
Glossary
K
keepalive interval keepalive message
Period of time between each keepalive message sent by a network device. 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 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.
Layer 3
LC LDP
line card. Line cards in the Cisco CRS-1 system are referred to as modular services cards (MSCs). 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). Label Information Base. The table that contains the labels in use on the node. Send the outgoing signals back to the receiving side for testing.
LIB loopback
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. Pattern of bits used to reject or accept bit patterns in another set of data. minimum boot image. Software image containing a kernel and minimum set of drivers and components to boot a node. megabits per second. A bit rate expressed in millions of binary bits per second. 1 megabit = 220 bits, or 1,048,576 bits.
mask MBI
Mbps
GL-6
Glossary
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. 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 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. 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. MSCs are also referred to as line cards.
MPLS
MPLS TE
MSC
MTU multicast
maximum transmission unit. Maximum packet size, in bytes, that a particular interface can handle. 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 node NSF
Loading software images from a network server, such as TFTP. A card installed and running on the router. 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. 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. nonvolatile RAM. Static random access memory that is made into nonvolatile storage by having a battery permanently connected.
NTP
NVRAM
GL-7
Glossary
O
OC-x OIR
Optical carrier, where x=3, 12, 48, or 192, relating to the various speeds within a SONET network. 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. Open Systems Interconnection. International standardization program created by ISO and ITU-T to develop standards for data networking that facilitate multivendor equipment interoperability. 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.
OSI
OSPF
P
package packet
A group of software components installed on the router. 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. POS. Packet over SONET/SDH enables core routers to send native IP packets directly over SONET or SDH frames. 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. Personal Computer Memory Card International Association. Standard for credit card-size memory or I/O device. 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. 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. 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.
Packet over SONET/SDH PAP
PCMCIA
PIE
PLIM
PM
GL-8
Glossary
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. 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. 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.
PPP
primary 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. 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. 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 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)
RIB
RIP
ROM Monitor
or
rommon1> (Cisco XR 12000 Series Routers)
ROMMON router
See ROM Monitor. 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.
GL-9
Glossary
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. 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. Protocol that accomplishes routing through the implementation of a specific routing algorithm. Examples of routing protocols include BGP, OSPF, and IS-IS. 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. 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. 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. 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. The router configuration currently in effect. Although the user can save multiple versions of the router configuration for future reference, only one copy of the running configuration exists in the router at any given time. The receiver end of a fabric link. All links are unidirectional. See also Tx.
routing metric
routing protocol
routing table
RP
RPF
RSVP
running configuration
Rx
S
SCFC
shelf controller/fan controller. Combines shelf controller function and fan controller function on one card. Two are installed in each fabric chassis. 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. 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. synchronous dynamic random access memory. A form of dynamic RAM that adds a separate clock signal to the control signals. The hardware component that manages the configuration and health of a fabric chassis within the Cisco CRS-1 router.
SDH
SDR
SDRAM
shelf controller
GL-10
Glossary
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. Software Maintenance Upgrade. A point fix for a critical problem. SMUs are delivered as PIE files and are used to update software packages. 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. 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. A list of packages activated for a particular node. A software configuration consists of a boot package and additional feature packages. 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. 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
SMU
SNMP
SNMPv3
software configuration SONET
SP
SPE
Synchronous Payload Envelope. Portion of the SONET frame containing overhead information (POH and user data). 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. Secure Shell. A protocol that provides a secure remote connection to a router through a Transmission Control Protocol (TCP) application. secure socket layer. A secure socket between two entities with authentication. Denotes an inactive card or process that waits to become active; standby cards or processes are also sometimes denoted as backup. The router configuration designated to be applied on the next router startup.
SPF
SSH
SSL standby
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. 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. Reload of a router node. Soft reset of a router node. This involves restarting all processes running on that node.
switchover
system reload system restart
GL-11
Glossary
T
TAC TACACS
Cisco Technical Assistance Center. 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. 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. make changes to the running configuration and accept these changes by entering the commit command.
tar
target configuration A two-stage configuration of the Cisco IOS XR software running configuration. This allows users to
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. 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. Transmission Control Protocol. Connection-oriented transport layer protocol that provides reliable full-duplex data transmission. TCP is part of the TCP/IP protocol stack. 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. A unit of computer memory or data storage capacity equal to 1024 gigabytes (240 bytes). Approximately 1 trillion bytes. 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.
Tbps
TCP
Telnet
terabyte
TFTP
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. Secure communication path between two peers, such as two routers. The transmitter end of a fabric link. All links are unidirectional. See also Rx.
tunnel Tx
GL-12
Glossary
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. Message sent to a single network destination. A unicast transmission sends one copy of each packet to each member of the group. This method is inefficient because the same information must be carried multiple times, requiring extra bandwidth.
unicast unicast transmission
V
VCSEL vm
vertical cavity surface emitting laser. 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. 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.
VPN
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. 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. An external application that sends an XML request to the router and receives XML responses to those requests. A portion of an XML request that specifies an operation that the XML client would like the XML agent to perform.
XML agent
XML client
XML operation
GL-13
Glossary
XML operation provider XML request XML response XML schema
The router code that carries out a particular XML operation including parsing the operation XML, performing the operation, and assembling the operation XML response An XML document sent to the router containing a number of requested operations to be carried out. The response to an XML request. An XML document specifying the structure and possible contents of XML elements that can be contained in an XML document.
GL-14
I N D EX
Symbols
? command
6-2
standalone router, first time verification Catalyst switch fabric cabling FCC
6-2 3-27 3-31 3-32 2-4 3-19 3-38
2-2
A
abbreviated commands, entering abort command admin command
4-38 6-8
non-DSC LCC spanning tree
standalone router
aborting command output

3-33
administration configuration mode administration EXEC mode alarm correlation, logging alarm logging correlation locations
5-10 5-10 5-10 6-16 6-16 4-19 5-10
4-19
C
capitalization, keyboard shortcuts cards CRS-FCC-LED See OIM LED CSC, removing and replacing CSFC, removing and replacing DRP PLIM OIM LED illustration
3-39 3-38 4-5 8-28 8-47 8-53 6-19
severity levels alias command
MSC removal
aliases, introduction
alphanumeric LED display DRP PLIM illustration PRP-2 illustration

4-5 1-12, 4-6 1-10, 4-3 1-11, 4-4 4-33
LED interpretation PLIM removal PRP

8-28
RP for 16-slot LCC illustration RP for 8-slot LCC illustration anchor characters
A-4
hardware requirements PRP-2 illustration standby, adding RP for 16-slot LCC RP for 8-slot LCC software requirements
7-12 8-53
8-53
alternative configuration, loading at startup asynchronous operation, install command
1-12, 4-6 8-53
1-10, 4-3 1-11, 4-4 8-47 4-12
B
BGP, configuration limits bring up multishelf system, first time
3-3 5-21
SFC, removing and replacing card type, displayed in prompt characters anchor
A-4
IN-1
Index
parentheses for pattern recall pattern ranges special

A-2 A-4 A-2
A-4
router submode configuration commands abbreviated aliases

6-16 6-15 6-2
4-21
underscore wildcard configuration restrictions

3-8
Cisco Catalyst 6509 Switch hardware requirements

3-10 3-9 3-10
applying templates creating templates
completing a partial command

6-13 6-5
6-4
identifying syntax errors no form

1-1 7-16 6-5 6-2
software requirements Cisco IOS XR software
more prompt, responding to on-screen help output filtering halting

5-9 9-21 6-8 6-8 6-8 6-8 6-18
6-7
supported standalone systems cisco-support user group clear command

4-33, 9-19 4-14
Cisco IOS XR Software Selector tool
clear configuration commit command clear configuration sessions command CLI identifying command mode introduction logging in prompt
4-12 4-43 1-6 4-11 4-18
narrowing
redirecting to a file recall deleted entries redisplaying wildcards

6-18 6-11
wrapped lines, editing commit command

4-34
6-5 4-34
commit best-effort command commit comment command commit confirmed command

4-44 4-45
clock, setting the router time clock set command

4-44
clock and scheduler card See CSC clock timezone command
4-35 4-35
commit force command commitIDs clearing displaying

4-19 5-9 5-4
4-35, 9-20
clock update-calendar command command-line interface See CLI command mode administration configuration administration EXEC CLI prompt EXEC
4-19 4-20 4-20 4-18 4-20 4-19
displaying changes loading changes

5-7
5-5
commit label command commit replace command
4-35 4-35 4-34
configuration submodes global configuration interface configuration navigation

4-17 4-22
committing a configuration committing packages complex expressions configuration Cisco Catalyst 6509 Switch
4-20 7-37 A-3
config-register command
8-26
navigation example ROM monitor

4-21
3-8
router configuration
clearing changes
4-33
IN-2
Index
committing displaying files, storage limiting limits BGP IS-IS MPLS OSPF other RPL
5-21 5-18
4-34 4-26 4-37
controller fabric plane command controllers command copy ftp command copy rcp command copy tftp command CPU0 module
4-12 8-27
8-32, 8-41
ending a session
5-16
controllers fabric plane command

7-18 7-18 7-17 5-10
3-24
4-36
correlation, alarm logging
5-25 5-24
Craft Works Interface See CWI CRS-FCC-LED card See OIM LED CSC card, removing and replacing CSFC card, removing and replacing Ctrl-Z command
5-17 4-33 4-21 4-37 6-19 1-6 8-47 8-53
multicast
5-25 5-22
5-18
static routes
cursor movement CWI, introduction
loading an alternate overview submodes

4-23
mode, entering EXEC commands reloading a failed configuration

4-20
4-36
D
debug command debugging
9-6
target configuration loading from a file saving to a file templates applying creating configurations multishelf systems standalone router configure command Console port connection
1-9, 4-3 4-5 1-2 1-1 4-24 4-26 6-15 6-13 4-32 4-33
disabling for all services, all sessions disabling for all services, one session disabling for a service displaying features displaying status enabling default SDR See DSC disk0
7-8 5-1 9-6 4-1 9-6 9-7 9-7
9-8 9-7
designated shelf controller
configure exclusive command
domain name, configuration domain name command

1-12, 4-6 1-10, 4-3 1-11, 4-4 5-2
DRP PLIM illustration PRP-2 illustration
domain name server, configuration domain name-server command drives, formatting DSC illustrated in rack 0 migration
3-9 8-23 1-7 3-4 8-27 5-2
5-1
RP for 16-slot LCC illustration RP for 8-slot LCC illustration control Ethernet network single-FCC system illustration
consolidated switch fabric cards See CSFC
selection and identification
IN-3
Index
dsc serial command
3-22, 3-23
FPD images FTP

7-17
7-34
E
end command errors syntax
6-5 4-37
G
GBIC transceiver module
3-10
Ethernet interface configuring displaying

4-39 4-40 4-5
Gigabit Interface Converter (GBIC) transceiver module 3-10 global configuration mode group command
5-16 4-20
DRP PLIM illustration PRP-2 illustration
1-12, 4-6 1-10, 4-3 1-11, 4-4 4-21
H
halting command output hardware displaying status documentation history, commands hostname configuration
4-38 4-12 4-38 5-2 8-24, 8-27, 8-49, 8-50 8-1 xiv 6-17 6-8
RP for 16-slot LCC illustration RP for 8-slot LCC illustration EXEC mode exit command expressions complex regular
A-3 A-1 4-19 4-37
EXEC commands, entering in configuration modes
extensible markup language See XML
displayed in prompt hostname command
HTTP server configuration
F
FCC serial number displaying with CLI physical location
3-6 7-34 8-10
hw-module location command
I
install activate command
7-31
field programmable device (FPD) images file, redirecting output to file storage flash disk0
7-8 7-17 6-8
install command, synchronous and asynchronous operation 7-12 install commit command
7-37 7-44
File Transfer Protocol (FTP) filters, command output flash disk configuration file storage disk0
7-8 8-27 8-27 6-8
install rollback committed command interface configuration mode interface MgmtEth command
4-36 4-20 4-41
interface preconfigure command interfaces, verifying operation
8-29, 8-30 9-21 5-25 5-25
format command formatting drives
ipv4 access-list maximum ace threshold command ipv4 access-list maximum acl threshold command ipv4 address command
4-42
IN-4
Index
ipv6 access-list maximum ace threshold command ipv6 access-list maximum acl threshold command IS-IS, configuration limits
5-18
5-25 5-25
log in, router
4-11 6-5 9-19
long lines, editing
low memory warning, removing configurations
K
keyboard shortcuts capitalization
6-19 6-18 6-19
M
Management Ethernet interface configuring displaying
4-39 4-40 4-5 4-10
command history cursor movement deleting text

6-20
DRP PLIM illustration

6-18
establishing a connection through name syntax

4-39 4-6 6-20
recalling deleted entries transposing letters
PRP-2 illustration
RP for 16-slot LCC illustration
4-3 4-4 5-24 5-24
L
LCC serial number displaying with CLI physical location line card removal
8-28 8-29, 8-30 6-5 3-7 8-10
RP for 8-slot LCC illustration maximum external-sa command maximum groups command IGMP configuration mode IGMP interface mode
5-24
maximum group-mappings autorp command

5-24
maximum interfaces command maximum path ipv4 command maximum path ipv6 command maximum paths command
5-8 4-36
5-19 5-17 5-17
replacement load command
line wrap, editing long lines

4-33
load commit changes command load rollback changes command logging alarm correlation configuration severity levels logging command
5-11 5-10 5-10 5-10
OSPF BGP IS-IS
5-19
load configuration failed commit command

5-9
maximum-paths command
5-21 5-18 5-19 5-24
maximum paths command, OSPF maximum-prefix command

5-21
maximum peer-external-sa command
output locations
maximum-redistributed-prefixes command (IS-IS)

5-10, 5-12
5-18 5-19
logging buffered command

5-11
maximum redistributed-prefixes command (OSPF) maximum register-states command

5-24 5-24
logging console command logging monitor command logging trap command
5-10, 5-11 5-13
maximum route-interfaces command maximum routes command MBI

8-20 5-24
logging console disable command

5-10 5-10, 5-11
memory displaying system memory

9-18
IN-5
Index
low memory warnings management

5-16
9-17
N
name, router configuring named SDR
4-38 4-12
removing configurations minimum boot image mode

8-20
9-19
displayed in prompt
4-19 4-1
administration configuration administration EXEC configuration submodes EXEC

4-19 4-20 4-20 4-19 4-20
netadmin user group no, command form node
4-14 4-3
network connection, overview

6-5
global configuration interface configuration ROM monitor

4-21
administrative shutdown power cycle

8-24
8-27
router configuration modem connection
4-20 4-21
reload
8-24 8-24 9-7 8-33, 8-42
router submode configuration DRP PLIM illustration PRP-2 illustration

4-5
shutdown
no debug command
no hw-module node command
1-12, 4-6 1-10, 4-3 1-11, 4-4
RP for 16-slot LCC illustration RP for 8-slot LCC illustration module node ID component
8-12, 8-15
O
oim count command
3-24 3-24
oim instance command

4-12
number displayed in prompt monitor processes command monitor threads command More prompt MPLS configuration limits package features MSC card removal multishelf system four-FCC system illustration hardware requirements overview restrictions
1-2 3-3 3-2 5-25 7-51 6-7 9-9
OIM LED card illustration OIR line cards, MSCs and PLIMs switch fabric cards, 8-slot FCC
5-25 8-28 8-30 8-39 3-39 3-40
9-9, 9-13
LED interpretation
switch fabric cards, 16-slot FCC online insertion and removal See OIR
5-24
mpls traffic-eng maximum tunnels command

8-28
multicast, configuration limits
operator user group
4-14
Optical Interface Module. See OIM

1-5
OSPF, configuration limits owner SDR

4-1
5-18
single-FCC system illustration software requirements

2-2, 3-2
1-3
P
package activation
two-FCC system illustration
1-4
IN-6
Index
impact on running configuration introduction

7-8 7-8 7-8
7-11
R
rack number displayed in prompt four-FCC system plan node ID component preparing a plan
3-3 3-4 3-5 4-12 3-5 8-12, 8-15
addition, introduction deactivation rollback set committing

7-37 7-8 7-38
committing a package set
impact on running configuration
7-11
single-FCC system plan two-FCC system plan

6-4
partial command, entry password command pattern alternation recall PIE files names
7-4 7-4 A-4 A-4
rcp
7-17 6-8
5-15
redirecting command output redundancy automatic failover

8-21
multiple-character
A-3
commands primary RP standby RP
8-21 8-22
manual switchover
8-20 8-53
PRP slot pairs
version numbers ping command PLIM removal

8-28 9-4
8-20 8-21, 8-22
redundancy switchover command reload command reloading software

8-21, 8-25 8-24 7-17
replacement different media type

8-30 8-29
Remote Copy Protocol (rcp) resource management rollback configuration history log, displaying overview procedure packages
9-15 5-3 5-6 5-16
same media type, different port count same media type and port count power cycle Primary LED RP for 16-slot LCC illustration RP for 8-slot LCC illustration process, definition process command
9-8 9-15 9-15 1-10, 4-3 1-11, 4-4 8-24 8-29
5-5 5-8
loading changes to the target configuration previewing changes

5-6 5-4
rollback failure
process mandatory command prompt
process mandatory reboot command command mode identification PRP hardware requirements redundancy slot pairs software requirements
8-53 8-53 8-53 4-18
displaying rollback points introduction

7-8 7-44
7-43
last committed set
package incompatibility rolling back to points ROM Monitor mode

7-2
5-4
7-45 5-7
rollback configuration command
IN-7
Index
ROM monitor mode root-lr user group route processors
4-21
See SDR serial number displaying with CLI FCC location

4-5 3-6 3-7 8-10
4-14 4-14
root-system user group DRP PLIM illustration PRP-2 illustration
LCC location
1-10, 4-3 1-11, 4-4
1-12, 4-6
service processor See SP session configuration overview ending

4-37 8-47 4-23
RP for 16-slot LCC illustration RP for 8-slot LCC illustration router clock setting
4-43 4-38 4-12
SFC card, removing and replacing SFTP

7-17
name configuration verification Catalyst switch fabric cabling FCC

3-27
name displayed in prompt

3-19 3-38
shortcuts capitalization
6-19 6-18 6-19
command history cursor movement deleting text

6-20
non-DSC LCC spanning tree standalone router
3-31 3-32 2-4 4-20 4-42
recalling deleted entries transposing letters

6-20
6-18
show aaa userdb command
5-14 4-16, 5-14 5-21
router configuration mode
show aaa usergroup command show bgp neighbor command show clock command
4-45
router static address family ipv4 command router submode configuration RPL, configuration limits
5-22 5-22 5-22 4-21
show configuration command
4-30, 4-33, 6-6, 9-2 5-5 5-5, 9-20 5-5, 9-19
rpl maximum lines command RP reload

8-21
show configuration commit changes ? command show configuration commit changes command show configuration commit history command show configuration commit list command
5-4
rpl maximum policies command
S
save configuration command SDR default package profile introduction logging in named owner
4-1 4-1 5-15 4-1 4-11 7-9 7-10 4-32
show configuration failed command
4-31, 9-15 4-32 4-32, 9-16 9-16
show configuration failed load command show configuration failed startup command show configuration merge command show configuration sessions command show context command show controller command show controllers command
9-2 9-2 8-27, 9-2 4-31
show configuration failed noerror command
show configuration rollback changes command

4-24, 9-21
5-6
managing packages
secret command
show controllers fabric connectivity command show controllers fabric plane all command
3-29, 3-32
secure domain router

8-32, 8-41
IN-8
Index
show controllers fabric plane command show controllers fabric rack command show debug command
9-2, 9-7 9-7
3-28, 3-31 3-28, 3-31
show processes cpu command
9-9 9-10 9-10
show processes dynamic command show processes failover command show processes log command
9-10
show debug conditions command show diag chassis command show diag command
8-2, 8-4 8-10
show processes memory command show processes startup command show redundancy command
9-10, 9-12 9-10
show environment command show exception command show hosts command show install command
5-2
2-6, 6-7, 8-15, 9-2
2-9, 8-18, 8-20, 8-21, 8-26, 9-3 5-22 5-22
9-2, 9-3
show rpl maximum lines command show running-config command
show rpl maximum policies command

5-24
show igmp summary command

9-3
4-27, 4-28, 6-6, 8-28, 9-3 5-19 5-17
show running-config router ospf command

7-37 7-43 7-43 4-40
show install committed command show install rollback ? command show install rollback command show interfaces brief command show interfaces command
show running-config router static command show running-config sanitized command show task supported command show tech-support command show user all command show user command
4-13, 5-14 6-7, 9-3
4-28, 4-30
8-28, 9-3, 9-21 4-42
8-31, 8-39, 8-47
show interfaces MgmtEth command show ipv4 access-lists command show ipv4 interface command show ipv6 access-lists command show ipv6 interface command show isis adjacency command show isis route command show logging command show memory command
5-18 5-12, 9-3 9-3, 9-18
4-15, 9-3 4-16, 8-31, 8-39, 8-47 4-15 8-25, 8-26, 9-2
5-25 9-21
show user group command show user tasks command show version command shutting down a node slot number displayed in prompt node ID component SMU
7-2 7-3 7-3 4-12
show ipv4 interface brief command

9-21
show variables boot command

9-21 8-24
5-25
2-6, 6-6, 8-11, 9-3
show ipv6 interface brief command

9-21 5-18
Simple Network Management Protocol
1-7
8-12, 8-15
show memory summary command show msdp summary command show ospf command
5-19 5-24
9-18, 9-19 5-25
filenames
show mpls traffic-eng maximum tunnels command

5-24
version numbers
SNMP (Simple Network Management Protocol) software, documentation

xiv
1-7
show pim summary command show platform command EXEC mode

8-12 2-8
Software Maintenance Update See SMU software packages activation impact on running configuration
7-11
administration EXEC mode show processes abort command show processes boot command show processes command
8-14
9-9 9-3, 9-9
impact on system prerequisites committing

7-15
7-11
show processes blocked command

9-9
Cisco IOS XR Software Selector tool

7-37
7-16
9-9, 9-10, 9-11
IN-9
Index
configuration rollback failure deactivation
5-4
CRS-FCC-LED OIM LED

7-11
3-38, 3-40
3-38, 3-40 6-8 4-20
impact on running configuration impact on system prerequisites downgrading

7-15 7-37 7-11
stopping command output submodes, configuration switch fabric cards
displaying committed versions

7-11 7-11
Cisco XR 12000 Series routers removing and replacing CRS-1 routers removing and replacing switch fabric card See SFC syntax
8-30, 8-38 8-47 7-12 8-47
impact of version changes management overview rollback SMUs upgrading SP

8-13 7-44, 7-45 7-3 7-10 7-4 7-7
synchronous operation, install command anchor characters

3-32 A-4 A-2 A-3
version numbers
character pattern ranges

A-2 7-17
spanning tree, verification special characters SSH File Transfer Protocol ssh server command standalone router bring up
2-2 1-1 1-1 4-11
complex regular expressions error identification pattern alternation pattern recall

A-4 A-1 A-2 A-4 4-14 6-5 A-4
regular expressions special characters sysadmin user group

2-4
supported hardware supported systems standby PRP, adding start up
wildcard underscore
verification after bring up

8-53
T
3-3 2-2
multishelf system, first time standalone router, first time verification Catalyst switch fabric cabling FCC
3-27 3-31 3-32 2-4 3-19 3-38
tab key
6-4
target configuration clearing changes loading from a file saving to a file task ID displaying introduction
4-14 4-13 4-11 4-11 5-2 4-32 4-13 4-33 4-33
task group, introduction
non-DSC LCC spanning tree standalone router Status LED
static route, configuration limits RP for 16-slot LCC illustration RP for 8-slot LCC illustration status LEDs
5-17
telnet ipv4 server command telnet ipv6 server command Telnet server configuration templates applying
6-15
1-10, 4-3 1-11, 4-4
IN-10
Index
creating
6-13
predefined user interfaces

4-5
4-14
terminal connection DRP PLIM illustration PRP-2 illustration

1-12, 4-6 1-10, 4-3 1-11, 4-4 4-8
CLI CWI
1-6 1-6 1-7 1-6 5-15
RP for 16-slot LCC illustration RP for 8-slot LCC illustration terminal settings, default values TFTP thread
7-17 9-8, 9-10, 9-13 4-43
SNMP
XML API
terminal server, establishing a connection through

1-13, 4-7, 4-9
username command
V
vm files
4-43 7-2
time, setting the router clock TLSv1

7-51 9-4
time zone, setting the router clock traceroute command
W
7-51 7-17
Transport Layer Security Version 1 Trivial File Transfer Protocol (TFTP) troubleshooting basic commands errors at startup
9-2
warning, low memory wildcards

6-11
9-17
displaying system memory information

9-16 9-15 9-17 9-8 4-12
9-18
X
XML API
1-6 5-2
failed commit operation low memory warnings processes and threads
host service configuration
type, card type displayed in prompt
U
undebug all command
9-7 A-4 7-2
underscore wildcard character Unicast Routing Core Bundle user access task IDs, displaying user accounts configuration overview creating user groups assigning to a user displaying introduction
4-14 4-13 5-15 5-15 5-14 4-14
IN-11
Index
IN-12

Cisco IOS XR Getting Started Guide

Uploaded by

Copyright:

Available Formats

You might also like

Cisco IOS XR Getting Started Guide

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cisco IOS XR Getting Started Guide

Uploaded by

Copyright:

Available Formats

Cisco IOS XR Getting Started Guide

Cisco IOS XR Software Release 3.3

Text Part Number: OL-8524-04

Changes to This Document

Introduction to Cisco IOS XR Software Contents