Cisco IOS XR Getting Started Guide Cisco IOS XR Software Release 3.3

R3.3 Beta Draft—Cisco Confidential Information

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-01 R3.3 Beta Draft—Cisco Confidential Information

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

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

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

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

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

qgg g y ggy 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)

Preface xi Changes to This Document xi About This Document xi Intended Audience xii Organization of the Document xii Related Documents xii Conventions xiii Obtaining Documentation xiii Cisco.com xiii Product Documentation DVD xiv Ordering Documentation xiv Documentation Feedback xiv Cisco Product Security Overview xiv Reporting Security Problems in Cisco Products xv Obtaining Technical Assistance xv Cisco Technical Support & Documentation Website xvi Submitting a Service Request xvi Definitions of Service Request Severity xvi Obtaining Additional Publications and Information xvii xviii

CHAPTER 1 Introduction to Cisco IOS XR Software 1-1 Contents 1-1 Supported Standalone System Configurations 1-1 Cisco CRS-1 Multishelf System Overview 1-2 Router Management Interfaces 1-5 Command-Line Interface 1-5 Craft Works Interface 1-5 Extensible Markup Language API 1-5 Simple Network Management Protocol 1-6 Selecting and Identifying the Designated Shelf Controller 1-6 Selecting and Identifying the DSC on Cisco CRS-1 Routers 1-7 Selecting and Identifying the DSC on Cisco CRS-1 Multishelf Systems 1-7 Selecting and Identifying the DSC on Cisco XR 12000 and 12000 Series Routers 1-8

Cisco IOS XR Getting Started Guide iii Contents

R3.3 Beta Draft—Cisco Confidential Information

Connecting to the Router Through the Console Port 1-8 Where to Go Next 1-14

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

CHAPTER 3 Bringing Up the Cisco IOS XR Software on a Multishelf System 3-1 Contents 3-1 Prerequisites 3-1 Software Requirements 3-2 Hardware Requirements 3-2 Restrictions 3-2 Information About Bringing Up a Multishelf System 3-2 Bringup Overview 3-3 Preparing a Rack Number Plan 3-3 Configuring the External Cisco Catalyst 6509 Switches 3-8 Prerequisites 3-8 Restrictions 3-9 Before You Begin 3-10 Information About the Catalyst Switch Configuration 3-10 Configuring the Catalyst Switches with Cisco IOS Commands 3-10 Verifying the Catalyst Switch 3-15 Bringing Up and Configuring Rack 0 3-17 Bringing Up and Verifying the FCC 3-24 Bringing Up and Verifying the Non-DSC LCC 3-28 Verifying the Spanning Tree 3-29 Verifying Fabric Cabling Connections 3-37 Troubleshooting Tips 3-40 Where to Go Next 3-40

CHAPTER 4 Configuring General Router Features 4-1 Contents 4-1 Secure Domain Routers 4-1

Cisco IOS XR Getting Started Guide iv Contents

R3.3 Beta Draft—Cisco Confidential Information

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 4-10 Logging In to a Router or an SDR 4-11 CLI Prompt 4-12 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 4-14 Navigating the Cisco IOS XR Command Modes 4-15 Identifying the Command Mode in the CLI Prompt 4-16 Summary of Common Command Modes 4-17 Entering EXEC Commands from a Configuration Mode 4-19 Command Mode Navigation Example 4-20 Managing Configuration Sessions 4-21 Entering Configuration Changes in the Nonactive Target Configuration 4-22 Committing Changes to the Running Configuration 4-22 Displaying Configuration Details with show Commands 4-24 Displaying Configuration Errors 4-29 Reloading a Failed Configuration 4-30 Clearing All Changes to a Target Configuration 4-30 Ending a Configuration Session 4-31 Locking and Unlocking the Running Configuration During Configuration Sessions 4-32 Configuring the Router Hostname 4-33 Configuring the Management Ethernet Interface 4-34 Specifying the Management Ethernet Interface Name in CLI Commands 4-34 Displaying the Available Management Ethernet Interfaces 4-36 Configuring the Management Ethernet Interface 4-36 Manually Setting the Router Clock 4-39 Where to Go Next 4-41

CHAPTER 5 Configuring Additional Router Features 5-1 Contents 5-1 Configuring the Domain Name and Domain Name Server 5-1 Configuring Telnet, HTTP, and XML Host Services 5-2 Prerequisites 5-3 Managing Configuration History and Rollback 5-3

Cisco IOS XR Getting Started Guide v Contents

R3.3 Beta Draft—Cisco Confidential Information

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 the Configuration Changes for a Specific CommitID 5-7 Loading Rollback Configuration Changes to the Target Configuration 5-7 Deleting CommitIDs 5-8 Saving and Loading Target Configuration Files 5-9 Saving the Target Configuration to a File 5-9 Loading the Target Configuration from a File 5-9 Loading an Alternative Configuration at System Startup 5-10 Configuring Logging and Logging Correlation 5-10 Logging Locations and Severity Levels 5-10 Alarm Logging Correlation 5-11 Configuring Basic Message Logging 5-11 Creating and Modifying User Accounts and User Groups 5-13 Displaying Details About User Accounts, User Groups, and Task IDs 5-14 Configuring User Accounts 5-14 Creating Users and Assigning Groups 5-15 Configuration Limiting 5-17 Static Route Configuration Limits 5-18 IS-IS Configuration Limits 5-19 OSPFv2 and v3 Configuration Limits 5-19 BGP Configuration Limits 5-22 Routing Policy Language Line and Policy Limits 5-24 Multicast Configuration Limits 5-25 MPLS Configuration Limits 5-26 Other Configuration Limits 5-26

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

Cisco IOS XR Getting Started Guide vi Contents

R3.3 Beta Draft—Cisco Confidential Information

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 6-6 Halting the Display of Screen Output 6-7 Redirecting Output to a File 6-7 Narrowing Output from Large Configurations 6-8 Filtering show Command Output 6-9 Wildcards, Templates, and Aliases 6-11 Using Wildcards to Identify Interfaces in show Commands 6-11 Creating Configuration Templates 6-12 Applying Configuration Templates 6-14 Aliases 6-16 Keystrokes Used as Command Aliases 6-17 Command History 6-17 Recalling Previously Entered Commands 6-17 Recalling Deleted Entries 6-18 Redisplaying the Command Line 6-18 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

CHAPTER 7 Upgrading and Managing Cisco IOS XR Software 7-1 Contents 7-1 Overview of Cisco IOS XR Software Packages 7-1 Information About Package Management 7-9 Overview of Package Management 7-10 Managing Software Packages in a Multishelf System 7-11 Upgrading Packages 7-12 Downgrading Packages 7-13 Standard PIE Filenames and Version Numbers 7-13 Software Maintenance Update PIE Filenames and Version Numbers 7-15 Impact of Package Version Changes 7-18 Impact of Package Activation and Deactivation 7-18 Activation and Deactivation Prerequisites 7-19 Package Management Procedures 7-19 Displaying Cisco IOS XR Software Information 7-20

Cisco IOS XR Getting Started Guide vii Contents

R3.3 Beta Draft—Cisco Confidential Information

Obtaining and Placing Cisco IOS XR Software 7-26 Controlling install Command Operation 7-29 Upgrading and Adding Packages from a Flash Disk 7-30 Upgrading and Adding Packages from a Network File Server 7-34 Rolling Back to the Last Committed Package Set 7-37 Rolling Back to a Noncommitted Rollback Point 7-38 Committing the Active Package Set 7-39 Deactivating a Package 7-39 Removing Inactive Packages from the Router 7-39 Configuration Examples for Managing Packages 7-40 Activating and Testing a Package on the Router: Example 7-40

CHAPTER 8 Managing the Router Hardware 8-1 Contents 8-1 Displaying Hardware Status 8-1 Displaying Hardware Version Information 8-2 Displaying the Chassis Serial Numbers (Cisco CRS-1 Routers) 8-3 Displaying the Configured Chassis Serial Numbers 8-4 Displaying Software and Hardware Information 8-4 Displaying SDR Node IDs and Status 8-5 Displaying Router Node IDs and Status 8-7 Displaying Router Environment Information 8-8 Displaying RP Redundancy Status 8-10 RP Redundancy and Switchover 8-11 Establishing RP Redundancy on the Cisco CRS-1 Router 8-11 Establishing RP Redundancy on Cisco XR 12000 Series Routers 8-12 Determining the Active RP in a Redundant Pair 8-13 Role of the Standby RP 8-13 Summary of Redundancy Commands 8-13 Automatic Switchover 8-14 RP Redundancy During RP Reload 8-14 Manual Switchover 8-14 Communicating with a Standby RP 8-15 Reloading, Shutting Down, or Power Cycling a Node 8-16 Reloading the Active RP 8-16 Administratively Shutting Down or Powering On or Off a Node 8-18 Using Controller Commands to Manage Hardware Components 8-18 Formatting Hard Drives, Flash Drives, and Other Storage Devices 8-19 Removing and Replacing Cards 8-19

Cisco IOS XR Getting Started Guide viii Contents

R3.3 Beta Draft—Cisco Confidential Information

Removing Line Cards, MSCs, or PLIMs 8-20 Replacing an MSC 8-21 Replacing a Line Card or PLIM with the Same Media Type and Port Count 8-21 Replacing a Line Card or PLIM with the Same Media Type and a Different Port Count 8-21 Replacing a Line Card or PLIM with a Different Media Type 8-22 Removing and Replacing Cisco CRS-16-FC Switch Fabric Cards 8-22 Removing and Replacing Cisco CRS-8-FC/S Switch Fabric Cards 8-31 Removing and Replacing CSC and SFC Cards 8-40 Removing and Replacing CSFC Cards 8-45 Adding a Standby PRP to a Cisco 12000 Series Router 8-46

CHAPTER 9 Troubleshooting the Cisco IOS XR Software 9-1 Contents 9-1 Additional Sources for Information 9-1 Basic Troubleshooting Commands 9-2 Using show Commands to Display System Status and Configuration 9-2 Using the ping Command 9-3 Using the traceroute Command 9-3 Using debug Commands 9-4 Understanding Processes and Threads 9-7 Commands Used to Display Process and Thread Details 9-8 Commands Used to Manage Process and Threads 9-13 Configuration Error Messages 9-14 Configuration Failures During a Commit Operation 9-14 Configuration Errors at Startup 9-15 Memory Warnings in Configuration Sessions 9-15 Understanding Low-Memory Warnings in Configuration Sessions 9-16 Displaying System Memory Information 9-17 Removing Configurations to Resolve Low-Memory Warnings 9-18 Contacting TAC for Additional Assistance 9-21 Interfaces Not Coming Up 9-21 Verifying the System Interfaces 9-22

APPENDIX A Understanding Regular Expressions, Special Characters, and Patterns D-1 Regular Expressions D-1 Special Characters D-2 Character Pattern Ranges D-2 Multiple-Character Patterns D-3

Cisco IOS XR Getting Started Guide ix Contents

R3.3 Beta Draft—Cisco Confidential Information

Complex Regular Expressions Using Multipliers D-3 Pattern Alternation D-4 Anchor Characters D-4 Underscore Wildcard D-4 Parentheses Used for Pattern Recall D-4

G LOSSARY

I NDEX

Cisco IOS XR Getting Started Guide x R3.3 Beta Draft—Cisco Confidential Information

Preface

Beta Draft Cisco Confidential Information

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 xi • Obtaining Documentation, page xiii • Documentation Feedback, page xiv • Cisco Product Security Overview, page xiv • Obtaining Technical Assistance, page xv • Obtaining Additional Publications and Information, page xvii

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 Date Change Summary OL-8524-01 January 2005 Initial release of the document.

About This Document

The following sections provide information about Cisco IOS XR Getting Started Guide and related documents: • Intended Audience, page xii • Organization of the Document, page xii • Related Documents, page xii • Conventions, page xiii

Cisco IOS XR Getting Started Guide xi Preface About This Document R3.3 Beta Draft—Cisco Confidential Information 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”

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

Cisco IOS XR Getting Started Guide xii Preface Obtaining Documentation R3.3 Beta Draft—Cisco Confidential Information Conventions

This document uses the following conventions:

Item Convention Commands and keywords boldface font Variable for which you supply values italic font Displayed session and system information screen font Commands and keywords you enter in an boldface screen font interactive environment Variables you enter in an interactive environment italic screen font Menu items and button names boldface font Menu navigation Option > Network Preferences

Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the publication.

Tip Means the following information will help you solve a problem. The information in tips might not be troubleshooting or an action, but contains useful information.

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

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL: http://www.cisco.com/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

Cisco IOS XR Getting Started Guide xiii Preface Documentation Feedback R3.3 Beta Draft—Cisco Confidential Information Product Documentation DVD

Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation. The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have pdf versions of the documentation available. The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from Cisco Marketplace at this URL: http://www.cisco.com/go/marketplace/

Ordering Documentation

Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL: http://www.cisco.com/go/marketplace/ Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at [email protected] or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com. You can send comments about Cisco documentation to [email protected]. You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address: Cisco Systems Attn: Customer Document Ordering 170 West Tasman Drive San Jose, CA 95134-9883 We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL: http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

Cisco IOS XR Getting Started Guide xiv Preface Obtaining Technical Assistance R3.3 Beta Draft—Cisco Confidential Information

From this site, you can perform these tasks: • Report security vulnerabilities in Cisco products. • Obtain assistance with security incidents that involve Cisco products. • Register to receive security information from Cisco. A current list of security advisories and notices for Cisco products is available at this URL: http://www.cisco.com/go/psirt If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL: http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT: • Emergencies—[email protected] 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. • Nonemergencies—[email protected] In an emergency, you can also reach PSIRT by telephone: • 1 877 228-7302 • 1 408 525-6532

Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

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

The link on this page has the current PGP key ID in use.

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 IOS XR Getting Started Guide xv Preface Obtaining Technical Assistance R3.3 Beta Draft—Cisco Confidential Information 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 (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.

Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco 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.

Cisco IOS XR Getting Started Guide xvi Preface Obtaining Additional Publications and Information R3.3 Beta Draft—Cisco Confidential Information

Severity 1 (S1)—Your network is “down,” or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation. Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation. Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels. Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources. • Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL: http://www.cisco.com/go/marketplace/ • Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL: http://www.ciscopress.com • Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL: http://www.cisco.com/packet • iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL: http://www.cisco.com/go/iqmagazine or view the digital edition at this URL: http://ciscoiq.texterity.com/ciscoiq/sample/ • 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

Cisco IOS XR Getting Started Guide xvii Preface

R3.3 Beta Draft—Cisco Confidential Information

• Networking Professionals Connection is an interactive website for networking professionals to 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 • World-class networking training is available from Cisco. You can view current offerings at this URL: http://www.cisco.com/en/US/learning/index.html

Cisco IOS XR Getting Started Guide xviii R3.3 Beta Draft—Cisco Confidential Information

CHAPTER 1

Introduction to Cisco IOS XR Software

Beta Draft Cisco Confidential Information

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-5 • Selecting and Identifying the Designated Shelf Controller, page 1-6 • Connecting to the Router Through the Console Port, page 1-8 • 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 12010 Router • Cisco XR 12016 Router • Cisco XR 12404 Router • Cisco XR 12406 Router • Cisco XR 12410 Router • Cisco XR 12416 Router

Cisco IOS XR Getting Started Guide 1-1 Chapter 1 Introduction to Cisco IOS XR Software Cisco CRS-1 Multishelf System Overview R3.3 Beta Draft—Cisco Confidential Information

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 router LCCs to act as a single system. This release of the multishelf system supports two 16-slot LCCs and one 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, and Figure 1-2 shows the four-FCC multishelf system.

Cisco IOS XR Getting Started Guide 1-2 Chapter 1 Introduction to Cisco IOS XR Software Cisco CRS-1 Multishelf System Overview R3.3 Beta Draft—Cisco Confidential Information

Figure 1-1 Single-FCC Multishelf System

INPUT FAN OUTPUT INPUT FAN OUTPUT OK OK FAIL OK OK FAIL

1 2 1 3 129492

1 Cisco CRS-1 16-Slot Line Card Chassis (two 3 Cisco Catalyst 6509 Switch (two suggested) required) 2 Cisco CRS-1 Fabric Card Chassis (one required)

Cisco IOS XR Getting Started Guide 1-3 Chapter 1 Introduction to Cisco IOS XR Software Cisco CRS-1 Multishelf System Overview R3.3 Beta Draft—Cisco Confidential Information

Figure 1-2 Four-FCC Multishelf System

INPUT FAN OUTPUT INPUT FAN OUTPUT OK OK FAIL OK OK FAIL

1 2 1 3 149632

1 Cisco CRS-1 16-Slot Line Card Chassis (two 3 Cisco Catalyst 6509 Switch (two suggested) required) 2 Cisco CRS-1 Fabric Card Chassis (four required)

For more information on multishelf systems, see Chapter 3, “Bringing Up the Cisco IOS XR Software on a Multishelf System.”

Cisco IOS XR Getting Started Guide 1-4 Chapter 1 Introduction to Cisco IOS XR Software Router Management Interfaces R3.3 Beta Draft—Cisco Confidential Information 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-5 • Craft Works Interface, page 1-5 • Extensible Markup Language API, page 1-5 • Simple Network Management Protocol, page 1-6

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

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

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

Cisco IOS XR Getting Started Guide 1-5 Chapter 1 Introduction to Cisco IOS XR Software Selecting and Identifying the Designated Shelf Controller R3.3 Beta Draft—Cisco Confidential Information

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

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

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

Cisco IOS XR Getting Started Guide 1-6 Chapter 1 Introduction to Cisco IOS XR Software Selecting and Identifying the Designated Shelf Controller R3.3 Beta Draft—Cisco Confidential Information

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. If you want a particular RP to become the DSC at startup, you must remove all other RPs before starting the router. If the router has multiple RPs installed on initial startup or during a restart, the router or multishelf system selects an RP to be 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-7 • Selecting and Identifying the DSC on Cisco CRS-1 Multishelf Systems, page 1-7 • Selecting and Identifying the DSC on Cisco XR 12000 and 12000 Series Routers, page 1-8

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. To select a specific RP to become the DSC for a new installation, install that RP first, apply power to the system, and wait for that RP to start up. When the Primary LED on the RP front panel lights, the RP is operating as the DSC, and you can install the other RP.

Note This method of selecting the DSC works only when the router is started with a single RP, and this should only happen the first time the router is started.

If two RPs are installed, either RP can become the DSC, and there is no way to predict which RP will become the DSC. The RP that starts up first becomes the active RP and DSC and lights the Primary LED on the RP front panel. The alphanumeric LED display on the RP displays ACTV RP. 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 will be in Rack 0. If you want to select a particular RP within Rack 0 to become the DSC, install that RP first, and wait for the RP to start up. When the Primary LED on the RP front panel lights (or the alphanumeric display shows ACTV RP), the RP is operating as the DSC, and you can install the other RP. 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 the DSC. 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.

Note Any LCC can host the DSC. The FCC cannot host the DSC function.

Cisco IOS XR Getting Started Guide 1-7 Chapter 1 Introduction to Cisco IOS XR Software Connecting to the Router Through the Console Port R3.3 Beta Draft—Cisco Confidential Information

To visually determine which RP is operating as the DSC in a multishelf system, go to Rack 0 and look for the RP on which the Primary LED is lit or the alphanumeric display shows ACTV RP. Rack 0 is the first LCC to receive power and is configured as Rack 0 during the multishelf bring-up procedure, which is described in Chapter 3, “Bringing Up the Cisco IOS XR Software on a Multishelf System.”

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-3 shows the RP connections on the Cisco CRS-1 16-Slot Line Card Chassis, and Figure 1-4 shows the RP connections on the Cisco CRS-1 8-Slot Line Card Chassis. Figure 1-5 shows the PRP-1 connections on the Cisco XR 12000 Series Router. Figure 1-6 shows the PRP-2 connections on the Cisco XR 12000 Series Router.

Cisco IOS XR Getting Started Guide 1-8 Chapter 1 Introduction to Cisco IOS XR Software Connecting to the Router Through the Console Port R3.3 Beta Draft—Cisco Confidential Information

Figure 1-3 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 Optical GigE for control plane:

CNTL ETH 1 not user-configurable Management Ethernet connection Network MGMT ETH for out-of-band network communciation Remote CLI, CWI, XML, or SNMP communication.

Primary Status 116547

Cisco IOS XR Getting Started Guide 1-9 Chapter 1 Introduction to Cisco IOS XR Software Connecting to the Router Through the Console Port R3.3 Beta Draft—Cisco Confidential Information

Figure 1-4 Communication Ports on the RP for a Cisco CRS-1 8-Slot LCC RJ-45 cable

Local terminal or terminal server for CLI communication. Console Terminal connection

AUX Modem connection RJ-45 cable ALARM PID/VID

Remote terminal for CRITICAL CLI communication. MAJOR MINOR Ethernet cable Network MGMT Management Ethernet connection ETH CNTL for out-of-band network communication Remote CLI, CWI, XML, ETH 0 Optical GigE for control plane: or SNMP communication. CNTL not user-configurable Remote file storage. ETH 1

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

LED status displays (alphanumeric) Primary Primary RP (On=Primary) Status

Card status (Green=OK) 122803

Cisco IOS XR Getting Started Guide 1-10 Chapter 1 Introduction to Cisco IOS XR Software Connecting to the Router Through the Console Port R3.3 Beta Draft—Cisco Confidential Information

Figure 1-5 Communication Ports on the PRP-1 for a Cisco XR 12000 Series Router

PC User-removable flash disk1: CARD stores installation PIE files.

A second internal Flash disk0: EJECT stores installed software and active configurations.

SLOT-2 SLOT-1 PRIMARY Ethernet cable Network ETH0

LINK EN Remote CLI, CWI, XML, TX RX or SNMP communication. PRIMARY Remote file storage. ETH1

LINK EN TX RX RJ-45 cable AUX Modem connection Remote terminal for CLI communication. Console Terminal connection

RJ-45 cable RESET

Local terminal or terminal server for PERFORMANCE ROUTE PROCESSOR 1 (PRP-1) CLI communication.

LED status displays (alphanumeric) 129010

Cisco IOS XR Getting Started Guide 1-11 Chapter 1 Introduction to Cisco IOS XR Software Connecting to the Router Through the Console Port R3.3 Beta Draft—Cisco Confidential Information

Figure 1-6 Communication Ports on the PRP-2 for a Cisco XR 12000 Series Router

User-removable flash disk1: stores installation PIE files

A second internal flash disk0: stores installed software and active configurations

SLOT-0SLOT-1 ETH 0 Ethernet cable LINK Network DATA ETH 1 Remote CLI, CWI, XML, LINK or SNMP communication. DATA BITS 0 Remote file storage SIG

ACT BITS 1 SIG

ACT RJ-45 cable AUX Modem connection

Remote terminal for ETH 2 CONSOLE CLI communication Terminal connection RJ-45 cable

Local terminal or PERFORMANCE ROUTE PROCESSOR 2 terminal server for

CLI communication RESET

LED status displays (alphanumeric) 138282

Cisco IOS XR Getting Started Guide 1-12 Chapter 1 Introduction to Cisco IOS XR Software Connecting to the Router Through the Console Port R3.3 Beta Draft—Cisco Confidential Information

To connect to the router, perform the following procedure.

SUMMARY STEPS

1. Power on the standalone router, or power on Rack 0 in a multishelf system. 2. Identify the DSC. 3. Connect a terminal to the Console port of the DSC. 4. Start the terminal emulation program. 5. Press Enter. 6. Log in to the router.

DETAILED STEPS

Command or Action Purpose Step 1 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 xii. Step 2 Identify the DSC. Identifies the RP to which you must connect in the next step. • For more information, see the “Selecting and Identifying the Designated Shelf Controller” section on page 1-6. Step 3 Connect a terminal to the Console port of the DSC. Establishes a communications path to the router. • 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 • For information on the cable requirements for the Console port, see the hardware documentation listed in the “Related Documents” section on page xii.

Cisco IOS XR Getting Started Guide 1-13 Chapter 1 Introduction to Cisco IOS XR Software Where to Go Next R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 4 Start the terminal emulation program. (Optional.) Prepares a computer for router communications. • 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. Step 5 Press Enter. Initiates communication with the router. • 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 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”

Cisco IOS XR Getting Started Guide 1-14 R3.3 Beta Draft—Cisco Confidential Information

CHAPTER 2

Bringing Up the Cisco IOS XR Software on a Standalone Router

Beta Draft Cisco Confidential Information

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

This chapter contains the following sections: • Hardware Prerequisites and Documentation, page 2-1 • Bringing Up and Configuring a Standalone Router, page 2-2 • Verifying the System After Initial Bring-Up, page 2-3 • Where to Go Next, page 2-7

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

Cisco IOS XR Getting Started Guide 2-1 Chapter 2 Bringing Up the Cisco IOS XR Software on a Standalone Router Bringing Up and Configuring a Standalone Router R3.3 Beta Draft—Cisco Confidential Information

For information on how to complete these procedures for your router equipment, see the hardware documents listed in the “Related Documents” section on page xii.

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 xii 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. Establish a connection to the DSC Console port. 2. Type the username for the root-system login and press Return. 3. Type the password for the root-system login and press Return. 4. Log in to the router.

DETAILED STEPS

Command or Action Purpose Step 1 Establish a connection to the DSC Console port. Initiates communication with the router. • For instructions on connecting to the Console port, see the “Connecting to the Router Through the Console Port” section on page 1-8. • 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 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. Step 3 Type the password for the root-system login and press Creates an encrypted password for the root-system Return. username.

Cisco IOS XR Getting Started Guide 2-2 Chapter 2 Bringing Up the Cisco IOS XR Software on a Standalone Router Verifying the System After Initial Bring-Up R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 4 Retype the password for the root-system login and Allows the router to verify that you have entered the same press Return. password both times. • If the passwords do not match, the router prompts you to repeat the process. Step 5 Log in to the router. Establishes your access rights for the router management session. • 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: lab 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.

User Access Verification

Username: lab 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. show version 2. admin show platform [node-id] end 3. show redundancy

Cisco IOS XR Getting Started Guide 2-3 Chapter 2 Bringing Up the Cisco IOS XR Software on a Standalone Router Verifying the System After Initial Bring-Up R3.3 Beta Draft—Cisco Confidential Information

4. show environment

DETAILED STEPS

Command or Action Purpose Step 1 show version Displays information about the router, including image names, uptime, and other system information.

RP/0/RP0/CPU0:router# show version Step 2 admin Places the router in administration EXEC mode, displays show platform [node-id] information about the status of cards and modules installed end in the router, and terminates administration EXEC mode. • Some cards support a CPU module and service RP/0/RP0/CPU0:router# admin processor (SP) module. Other cards support only a RP/0/RP0/CPU0:router(admin)# show platform 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. Note To view the status of all cards and modules, the show platform command must be executed in administration EXEC mode. Step 3 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. Example: RP/0/RP0/CPU0:router# show redundancy • If both RPs are working correctly, the This node row 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-5 • show environment Command, page 2-5 • show platform Command, page 2-6 • show redundancy Command, page 2-7

Cisco IOS XR Getting Started Guide 2-4 Chapter 2 Bringing Up the Cisco IOS XR Software on a Standalone Router Verifying the System After Initial Bring-Up R3.3 Beta Draft—Cisco Confidential Information

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/RP0/CPU0:router# show version

ROM: System Bootstrap, Version 1.15(20040120:002852) ,

router uptime is 2 days, 1 hour, 59 minutes System image file is "tftp://223.0.0.0/usr/comp-hfr-full.vm-1.0.0

cisco CRS-16/S (7450) processor with 2097152K bytes of memory. 7450 processor at 650Mhz, Implementation , Revision

4 Packet over SONET network interface(s) 4 SONET/SDH Port controller(s) 1 Ethernet/IEEE 802.3 interface(s) 2043k bytes of non-volatile configuration memory. 1000592k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).

Configuration register is 0x2

Package active on node 0/2/SP: hfr-admin, V 1.0.0, Cisco Systems, at mem:hfr-admin-1.0.0 Built on Fri Mar 5 19:12:26 PST 2004 --More--

show environment Command To display environmental monitor parameters for the system, use the show environment command in EXEC mode. The following command syntax is used: show environment [options] Table 2-1 defines the show environment command options. Table 2-1 show environment Command Options

Option Displays all Information for all environmental monitor parameters. last Information measured in the prior measurement interval (Cisco XR 12000 Series Routers only). table Environmental parameter ranges. temperatures System temperature information. voltages System voltage information.

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 Exhaust Hotspot Temperature Temperature Temperature (deg C) (deg C) (deg C)

0/2/* host 31, 27 43, 45 48 cpu 31

Cisco IOS XR Getting Started Guide 2-5 Chapter 2 Bringing Up the Cisco IOS XR Software on a Standalone Router Verifying the System After Initial Bring-Up R3.3 Beta Draft—Cisco Confidential Information

fabricq0 46 fabricq1 44 ingressq 34 egressq 41 43 ingresspse 35 egresspse 42 plimasic 30, 31 42 0/RP1/* host 38 44 cpu 36 ingressq 42 fabricq0 43 0/SM0/* host 29, 29 41, 33

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/2/*: Module (host) LED status says: OK 0/2/*: Module (plimasic) LED status says: OK 0/SM0/*: Module (host) LED status says: OK

See the Cisco IOS XR Interface and Hardware Component Command Reference for more information.

show platform Command The following is sample output from the show platform command for all nodes in a router: RP/0/RP0/CPU0:router# admin

RP/0/RP0/CPU0:router(admin)# show platform

Node Type PLIM State Config State ------0/0/SP MSC(SP) N/A IOS-XR RUN PWR,NSHUT,MON 0/0/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/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 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.

In the following example, information is shown for a single node in a Cisco CRS-1 router:

RP/0/RP0/CPU0:router(admin)# show platform 0/2/cpu0

Node Type PLIM State Config State ------0/2/CPU0 MSC 16OC48-POS/DPT IOS-XR RUN PWR,NSHUT,MON

For more information on nodeID, see the “Displaying SDR Node IDs and Status” section on page 8-5. For more information on the show platform command, see the Cisco IOS XR Interface and Hardware Component Command Reference.

Cisco IOS XR Getting Started Guide 2-6 Chapter 2 Bringing Up the Cisco IOS XR Software on a Standalone Router Where to Go Next R3.3 Beta Draft—Cisco Confidential Information

show redundancy Command To display information about the active and standby (inactive) RPs, enter the show redundancy command as follows: 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

Where to Go Next

For information on configuring basic router features, see Chapter 4, “Configuring General Router Features.”

Cisco IOS XR Getting Started Guide 2-7 Chapter 2 Bringing Up the Cisco IOS XR Software on a Standalone Router Where to Go Next R3.3 Beta Draft—Cisco Confidential Information

Cisco IOS XR Getting Started Guide 2-8 R3.3 Beta Draft—Cisco Confidential Information

CHAPTER 3

Bringing Up the Cisco IOS XR Software on a Multishelf System

Beta Draft Cisco Confidential Information

This chapter describes how to bring up the Cisco IOS XR Software on a multishelf system for the first time.

Contents

This chapter contains the following sections: • Prerequisites, page 3-1 • Restrictions, page 3-2 • Information About Bringing Up a Multishelf System, page 3-2 • Configuring the External Cisco Catalyst 6509 Switches, page 3-8 • Bringing Up and Configuring Rack 0, page 3-17 • Bringing Up and Verifying the FCC, page 3-24 • Bringing Up and Verifying the Non-DSC LCC, page 3-28 • Verifying the Spanning Tree, page 3-29 • Verifying Fabric Cabling Connections, page 3-37 • Troubleshooting Tips, page 3-40 • Where to Go Next, page 3-40

Prerequisites

The following sections describe the software and hardware requirements for bringing up a multishelf system.

Cisco IOS XR Getting Started Guide 3-1 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Restrictions R3.3 Beta Draft—Cisco Confidential Information Software Requirements

The multishelf system requires the following software: • Cisco IOS XR Software Release 3.3 • ROMMON 1.32 or higher on each RP in the system

Hardware Requirements

Before you can bring up a multishelf system, the system components must be physically installed and tested. Two multishelf systems 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 fabric chassis containing eight SFC (S2) fabric cards. Four-FCC systems require four FCCs with eight SFC (S2) fabric cards distributed 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 xii.

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 or four fabric card chassis. – 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 xv).

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

Cisco IOS XR Getting Started Guide 3-2 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Information About Bringing Up a Multishelf System R3.3 Beta Draft—Cisco Confidential Information Bringup Overview

The bringup procedure for a multishelf system starts after the hardware installation is complete. The bringup procedure tasks configure the system components to work together and verify the operation and configuration of system components. To bring up the multishelf system, complete the following procedures in the sequence shown: 1. Configuring the External Cisco Catalyst 6509 Switches, page 3-8 2. Bringing Up and Configuring Rack 0, page 3-17 3. Bringing Up and Verifying the FCC, page 3-24 4. Bringing Up and Verifying the Non-DSC LCC, page 3-28 5. Verifying the Spanning Tree, page 3-29 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 1. This rack number is used to identify a chassis in the system, and maintain the software and configurations for the chassis.

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 1DSC in a CRS-1/M-F1 Multishelf System

Gigabit Ethernet Control Bus

INPUT FAN OUTPUT INPUT FAN OUTPUT INPUT FAN OUTPUT INPUT FAN OUTPUT OK OK FAIL OK OK FAIL OK OK FAIL OK OK FAIL SC SM0 SM1 SM2 SM3 SM0 SM1 SM2 SM3 OIM23 OIM22 OIM21 OIM16 OIM15 OIM14 OIM13 OIM12 OIM23 OIM22 OIM21 OIM16 OIM15 OIM14 OIM13 OIM12 OIM-LED 1 OIM-LED 1

Fabric Cards Fabric Catalyst 6509 Switches

DSC SC SM4 SM7 SM4 SM7 OIM23 OIM22 OIM21 OIM16 OIM15 OIM14 OIM13 OIM12 OIM23 OIM22 OIM21 OIM16 OIM15 OIM14 OIM13 OIM12 RP (SC) RP (SC) RP (SC) RP (SC) OIM-LED 1 OIM-LED 1 Fabric Cards Fabric

Line Card Chassis Fabric Card Chassis Line Card Chassis

Rack 1 Rack F0 Rack 0 138118

Cisco IOS XR Getting Started Guide 3-3 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Information About Bringing Up a Multishelf System R3.3 Beta Draft—Cisco Confidential Information

Note Chassis, shelf, and rack are used interchangeably. Each term refers to the physical tower that contains the installed cards, power, and cooling equipment. In general, chassis describes the system components. Rack is used in software to assign a rack number to each chassis.

A rack number plan lists each chassis in a system with the correct chassis serial ID and an assigned rack number. The serial ID is the chassis serial number, which can be accessed by the software and uniquely identifies the chassis. The rack number for an LCC is a number in the range of 0 to 255, which is easier to remember and read than serial numbers in display messages. The rack number plan is used during the startup and configuration of Rack 0. The LCC that hosts the DSC must be configured as Rack 0. The non-DSC LCC must be configured to use a rack number in the range of 1 to 255. In a single-FCC system, the FCC must be configured as Rack F0. In a four-FCC system, the FCC rack numbers are F0, F1, F2, and F3. 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 Serial ID Rack Number LCC containing the active DSC 0 Non-DSC LCC 1 Fabric chassis F0

Table 2 shows a sample rack number plan for a four-FCC system.

Table 2 Sample Rack Number Plan for a Four-FCC Multishelf System

Chassis Serial ID Rack Number LCC containing the active DSC 0 Non-DSC LCC 1 Fabric chassis 0 F0 Fabric chassis 1 F1 Fabric chassis 2 F2 Fabric chassis 3 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.

Cisco IOS XR Getting Started Guide 3-4 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Information About Bringing Up a Multishelf System R3.3 Beta Draft—Cisco Confidential Information

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 129761, 781-00375-01

Cisco IOS XR Getting Started Guide 3-5 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Information About Bringing Up a Multishelf System R3.3 Beta Draft—Cisco Confidential Information

Figure 3 Location of the Serial Number on a Line Card Chassis

PWR OK

FLT

AC PWR FAI L OK

CB TRIP FLT

I A LIM C PWR FAIL OK

OT CB TRIP FLT

I LIM AC FAIL

OT CB TRIP

I LIM

PWR OK

FLT

AC PWR FAIL OK

CB TRIP FLT

I LIM AC PWR FAIL OK

OT CB TRIP FLT

I L AC IM FAIL

OT CB TRIP

I LIM

SN: AAANNNNXXXX 116535

Caution Always assign a rack number to each chassis in the system before the chassis is booted. If a chassis is not assigned a rack number, or if the rack number conflicts with an existing chassis, it may not be recognized by the system or cause other operational difficulties.

Cisco IOS XR Getting Started Guide 3-6 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Information About Bringing Up a Multishelf System R3.3 Beta Draft—Cisco Confidential Information

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 sections: • To display the chassis serial numbers in administration EXEC mode, see the “Displaying the Chassis Serial Numbers (Cisco CRS-1 Routers)” section on page 8-3. • To display the configured chassis serial numbers in administration EXEC mode, see the “Displaying the Configured Chassis Serial Numbers” section on page 8-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-17 for complete instructions to bring up a new router and configure the rack numbers.

Cisco IOS XR Getting Started Guide 3-7 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Configuring the External Cisco Catalyst 6509 Switches R3.3 Beta Draft—Cisco Confidential Information 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 either 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-8 • Restrictions, page 3-9 • Before You Begin, page 3-10 • Information About the Catalyst Switch Configuration, page 3-10 • Configuring the Catalyst Switches with Cisco IOS Commands, page 3-10 • Verifying the Catalyst Switch, page 3-15

Figure 4 Control Ethernet Network Connections in a Single-FCC System

Catalyst RP Ethernet Line Card Switch Chassis

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.

Cisco IOS XR Getting Started Guide 3-8 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Configuring the External Cisco Catalyst 6509 Switches R3.3 Beta Draft—Cisco Confidential Information

Software Requirements

Each Cisco Catalyst 6509 Switch requires the same software: • Cisco IOS Release 12.2(14r)S9 with SUP720 Supervisor Engine controller module • System Bootstrap (ROMMON), Version 1.3 or later • BOOTLDR: s72033_rp Software (s72033_rp-PSV-M), Version 12.2(17d)SXB7 Both switches should use the same software. The filename of the software is 72033-psv-mz.122-17d.SXB8.bin, and is available on CCO at: http://www.cisco.com/kobayashi/sw-center/lan/cat6000.shtml

Hardware Requirements

• Two external Cisco Catalyst 6509 Switches correctly cabled to the Cisco CRS-1 multishelf router. • The recommended hardware configuration for an AC-powered Cisco Catalyst 6509 system is shown in the following table:

Quantity Description Part 1 Catalyst 6509 Chassis, 9slot, 15RU, No Pow Supply, No Fan WS-C6509 Tray 1 Cisco CAT6000-SUP720 IOS IP S733Z-12217SXB (see Software Requirements for complete details). 1 Catalyst 6500/Cisco 7600 Supervisor 720 Fabric MSFC3 WS-SUP720-3B PFC3B 1 Catalyst 6500 Sup720 Compact Flash Mem 256MB MEM-C6K-CPTFL256M 1 Catalyst 6000 16-port Gig-Ethernet Mod. (Req. GBICs) WS-X6416-GBIC 8 1000BASE-LX/LH long haul GBIC (singlemode or WS-G5486 multimode) 1 Catalyst 6509 High Speed Fan Tray WS-C6K-9SLOT-FAN2 2 Catalyst 6000 2500W AC Power Supply WS-CAC-2500W 2 Power Cord, 250Vac 16A, straight blade NEMA 6-20 plug, CAB-AC-2500W-US1 US

Restrictions

The following restrictions apply to 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 router 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.

Cisco IOS XR Getting Started Guide 3-9 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Configuring the External Cisco Catalyst 6509 Switches R3.3 Beta Draft—Cisco Confidential Information 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 xii 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 switches—they 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 with Cisco IOS Commands

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.

The following sections describe how to configure a single-FCC multishelf system: • Configure the First Catalyst Switch, page 3-10 • Configure the Second Catalyst Switch, page 3-11 • Example to Configure a Single-FCC Multishelf System, page 3-12 The following section provides an example of how to configure a four-FCC multishelf system: • Example to Configure a Four-FCC Multishelf System, page 3-13

Configure the First Catalyst Switch

To configure the first Catalyst 6509 Switch, use the following procedure: 1. In the Cisco IOS software, enter the following commands for each port, including ports that are not currently being used (for example, interface Gi 0/1):

Cisco IOS XR Getting Started Guide 3-10 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Configuring the External Cisco Catalyst 6509 Switches R3.3 Beta Draft—Cisco Confidential Information

a. interface type slot/port b. switchport mode access c. switchport access vlan 1 d. spanning-tree portfast default e. end f. Repeat these steps for each interface in the switch. 2. Configure the spanning tree by entering the following commands: a. spanning-tree mode mst b. no spanning-tree optimize bpdu transmission c. spanning-tree mst configuration d. name STP_1 e. revision 1 f. instance 1 vlan 1 g. end 3. Enter the following commands in global configuration mode to complete the spanning tree configuration: a. spanning-tree mst hello-time 1 b. spanning-tree mst forward-time 6 c. spanning-tree mst max-age 8 d. spanning-tree mst 0-1 priority 0

Note The primary Catalyst switch should be configured with priority 0. This makes the switch the root of the network.

Configure the Second Catalyst Switch

To configure the second Catalyst 6509 Switch, use the following procedure: 1. In the Cisco IOS software, enter the following commands for each port, including ports that are not currently being used (for example, interface Gi 0/1): a. interface type slot/port b. switchport mode access c. switchport access vlan 1 d. spanning-tree portfast default e. end f. Repeat these steps for each interface in the switch. 2. Configure the spanning tree by entering the following commands: a. spanning-tree mode mst b. no spanning-tree optimize bpdu transmission c. spanning-tree mst configuration

Cisco IOS XR Getting Started Guide 3-11 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Configuring the External Cisco Catalyst 6509 Switches R3.3 Beta Draft—Cisco Confidential Information

d. name STP_1 e. revision 1 f. instance 1 vlan 1 g. end 3. Enter the following commands in global configuration mode to complete the spanning tree configuration: a. spanning-tree mst hello-time 1 b. spanning-tree mst forward-time 6 c. spanning-tree mst max-age 8 d. spanning-tree mst 0-1 priority 28672

Note The second Catalyst switch should be configured with a number greater than 0 and less than 32768. In this example, the priority is set as 28672. If the primary Catalyst switch (priority 0) fails, the second switch becomes the root of the network.

Example to Configure a Single-FCC Multishelf System

Example to Configure the First Catalyst Switch: CAT6k-1# interface Gi 0/1 CAT6k-1(config-if)# switchport mode access CAT6k-1(config-if)# switchport access vlan 1 CAT6k-1(config-if)# spanning-tree portfast default CAT6k-1(config-if)# end CAT6k-1(config)# spanning-tree mode mst CAT6k-1(config-mst)# no spanning-tree optimize bpdu transmission CAT6k-1(config-mst)# 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 0-1 priority 0

Example to Configure the Second Catalyst Switch: CAT6k-1# interface Gi 0/1 CAT6k-1(config-if)# switchport mode access CAT6k-1(config-if)# switchport access vlan 1 CAT6k-1(config-if)# spanning-tree portfast default CAT6k-1(config-if)# end CAT6k-1(config)# spanning-tree mode mst CAT6k-1(config-mst)# no spanning-tree optimize bpdu transmission CAT6k-1(config-mst)# 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 0-1 priority 28672

Cisco IOS XR Getting Started Guide 3-12 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Configuring the External Cisco Catalyst 6509 Switches R3.3 Beta Draft—Cisco Confidential Information

Example to Configure a Four-FCC Multishelf System

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

Cisco IOS XR Getting Started Guide 3-13 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Configuring the External Cisco Catalyst 6509 Switches R3.3 Beta Draft—Cisco Confidential Information

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

Cisco IOS XR Getting Started Guide 3-14 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Configuring the External Cisco Catalyst 6509 Switches R3.3 Beta Draft—Cisco Confidential Information

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

Cisco IOS XR Getting Started Guide 3-15 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Configuring the External Cisco Catalyst 6509 Switches R3.3 Beta Draft—Cisco Confidential Information

• 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. 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 xv. 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 Desg FWD 20000 128.1 P2p Gi1/2 Desg FWD 20000 128.2 P2p Gi1/3 Desg FWD 20000 128.3 P2p

Cisco IOS XR Getting Started Guide 3-16 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Configuring Rack 0 R3.3 Beta Draft—Cisco Confidential Information

Gi1/4 Desg FWD 20000 128.4 P2p Gi1/5 Desg FWD 20000 128.5 P2p Gi1/6 Desg FWD 20000 128.6 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 FWD 20000 128.1 P2p Gi1/2 Desg FWD 20000 128.2 P2p Gi1/3 Desg FWD 20000 128.3 P2p Gi1/4 Desg FWD 20000 128.4 P2p Gi1/5 Desg FWD 20000 128.5 P2p Gi1/6 Desg FWD 20000 128.6 P2p CAT6k-1#

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

Cisco IOS XR Getting Started Guide 3-17 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Configuring Rack 0 R3.3 Beta Draft—Cisco Confidential Information

Note In the Cisco IOS XR Software Release 3.3, Beta 2, replace any CLI references to FCC rack numbers in the dsc serial command as follows: F0 = 240, F1 = 241, F2 = 242, and F3 = 243. For example, to define the serial number for rack F1, enter 241 in place of F1.

Summary Steps

1. Power down all LCCs and FCCs. 2. Apply power to the LCC that contains the DSC. 3. Connect to the DSC console port and log in. 4. admin 5. configure 6. dsc serial serial ID rack 0 7. dsc serial serial ID rack rackNumber 8. dsc serial serial ID rack Fn 9. 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

Detailed Steps

Command or Action Purpose Step 1 Power down all LCCs and FCCs. Prepares the LCCs and FCCs for startup in the proper sequence. • Each LCC and FCC should be powered up in the order specified in this chapter. Step 2 Apply power to the LCC that contains the DSC. Boots the LCC containing the DSC. • 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 xii for site planning information including DSC placement.

Cisco IOS XR Getting Started Guide 3-18 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Configuring Rack 0 R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose 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-8. 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. • The LCC containing the DSC should be Example: configured with the lowest rack number. RP/0/RP0/CPU0:router(admin-config)# dsc serial TBA00000001 rack 0 • Replace serial ID with the serial number of the LCC you want to configure as Rack 0. • See the “Preparing a Rack Number Plan” section on page 3-3 for information on locating the serial number. Step 7 dsc serial serial ID rack rackNumber Defines the rack number for the second LCC. • See the “Preparing a Rack Number Plan” Example: section on page 3-3 for information on RP/0/RP0/CPU0:router(admin-config)# dsc serial TBA00000002 locating the serial numbers and selecting rack 1 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.

Cisco IOS XR Getting Started Guide 3-19 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Configuring Rack 0 R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 8 dsc serial serial ID rack Fn Defines the rack number for an FCC. • See the “Preparing a Rack Number Plan” Example: section on page 3-3 for information on RP/0/RP0/CPU0:router(admin-config)# dsc serial TBA00000003 locating the serial numbers and selecting rack F0 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 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 Displays the committed rack number configuration. Verify that the serial numbers entered for each chassis are correct. Example: RP/0/RP0/CPU0:router(admin-config)# show running-config | include dsc Step 11 controllers fabric plane planeNumber Configures a plane to operate in an FCC slot. oim count 1 oim instance 0 location Frack/slot/FM • Enter this command sequence for each of the eight fabric planes.

Example: • Replace planeNumber with the number of RP/0/RP0/CPU0:router(admin-config)# controllers fabric the plane (0 to 7) you want to configure. plane 0 • Replace rack with the FCC rack number RP/0/RP0/CPU0:router(admin-config)# oim count 1 RP/0/RP0/CPU0:router(admin-config)# oim instance 0 assigned to the FCC that hosts the plane. location F0/SM9/FM • 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.

Cisco IOS XR Getting Started Guide 3-20 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Configuring Rack 0 R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 12 commit Commits the target configuration to the router running configuration. Example: RP/0/RP0/CPU0:router(admin-config)# commit 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)#

Cisco IOS XR Getting Started Guide 3-21 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Configuring Rack 0 R3.3 Beta Draft—Cisco Confidential Information

Examples

This section contains examples for the following subjects: • Example: Configuring and Verifying the Rack Numbers in a Single-FCC Multishelf System, page 3-22 • Example: Mapping Each Fabric Plane in a Single-FCC Multishelf System, page 3-22 • Example: Mapping Each Fabric Plane in a Four-FCC Multishelf System, page 3-23

Example: Configuring and Verifying the Rack Numbers in a Single-FCC Multishelf System

In the following example, rack numbers are assigned to each LCC and FCC in administration configuration mode: RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# configure RP/0/RP0/CPU0:router(admin-config)# dsc serial TBA00000001 rack 0 RP/0/RP0/CPU0:router(admin-config)# dsc serial TBA00000002 rack 1 RP/0/RP0/CPU0:router(admin-config)# dsc serial TBA00000003 rack F0 RP/0/RP0/CPU0:router(admin-config)# commit RP/0/RP0/CPU0:router(admin-config)# show running-config | include dsc

Building configuration... dsc serial TBA00000003 rack F0 dsc serial TBA00000001 rack 0 dsc serial TBA00000002 rack 1 RP/0/RP0/CPU0:router(admin-config)#

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 1 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 2 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 3 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 4 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 5 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 6 location F0/SM18/FM

Cisco IOS XR Getting Started Guide 3-22 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Configuring Rack 0 R3.3 Beta Draft—Cisco Confidential Information

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 7 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 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/SM11/FM ! controllers fabric plane 2 oim count 1 oim instance 0 location F1/SM0/FM ! controllers fabric plane 3 oim count 1 oim instance 0 location F1/SM11/FM ! controllers fabric plane 4 oim count 1 oim instance 0 location F2/SM0/FM ! controllers fabric plane 5 oim count 1 oim instance 0 location F2/SM11/FM ! controllers fabric plane 6 oim count 1 oim instance 0 location F3/SM0/FM ! controllers fabric plane 7 oim count 1 oim instance 0 location F3/SM11/FM !

Cisco IOS XR Getting Started Guide 3-23 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Verifying the FCC R3.3 Beta Draft—Cisco Confidential Information

end

Bringing Up and Verifying the FCC

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. Apply power to all FCCs. 2. show controllers fabric rack all detail 3. show controllers fabric plane all detail 4. show controllers fabric connectivity all detail 5. On the external Catalyst switches, verify that the links are not unidirectional.

Cisco IOS XR Getting Started Guide 3-24 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Verifying the FCC R3.3 Beta Draft—Cisco Confidential Information

Detailed Steps

Command or Action Purpose Step 1 Apply power to all FCCs. Starts the 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 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 the FCCs display “IOS XR RUN.” This indicates that each SCGE has successfully loaded the Cisco IOS XR software. • If an SCGE card fails to boot properly, see Cisco CRS-1 Multishelf Troubleshooting Guide. Step 2 show controllers fabric rack all detail Displays the status of all racks in the system. • In a properly operating system, the rack Example: status for all racks should be Normal, and RP/0/RP0/CPU0:router(admin)# show controllers fabric rack the server status should be Present. all detail • See the Cisco CRS-1 Multishelf Troubleshooting Guide for more information. Step 3 show controllers fabric plane all detail Displays the status of all racks and additional information for racks in installation mode. Example: • Wait for the status in the Admin State and RP/0/RP0/CPU0:router(admin)# show controllers fabric plane Oper State columns to change to UP for all detail all planes. • See the Cisco CRS-1 Multishelf Troubleshooting Guide for more information.

Cisco IOS XR Getting Started Guide 3-25 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Verifying the FCC R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 4 show controllers fabric connectivity all detail Displays the LCC cards that can communicate with all eight fabric planes. Example: • The expected output should contain a RP/0/RP0/CPU0:router(admin)# show controllers fabric series of ‘1’s for each of the fabric planes connectivity all detail 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 “.” • If the fabric planes are down, or unable to communicate with the line cards, see the Cisco CRS-1 Multishelf Troubleshooting Guide. Step 5 On the external Catalyst switches, verify that the links are not Verifies that the links from the chassis to the unidirectional. 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-15. The verification commands must be entered from a terminal directly connected to the external Catalyst switches, using Cisco IOS CLI commands.

Cisco IOS XR Getting Started Guide 3-26 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Verifying the FCC R3.3 Beta Draft—Cisco Confidential Information

Examples

This section contains an example for the following task: • Verify That All Fabric Planes Are Ready to Handle Data, page 3-27

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 they are ready to handle traffic.

show controllers fabric rack all detail 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 Rack Server Num Status Status ------

0 NORMAL PRESENT 1 NORMAL PRESENT F0 NORMAL PRESENT RP/0/RP0/CPU0:router(admin)#

show controllers fabric plane all detail In the following example, all eight planes are displayed, and the administrative and operational state of each plane is up. RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all detail

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

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 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:router(admin)# show controllers fabric connectivity all detail

Card In Tx Planes Rx Planes Monitored Total Percent R/S/M Use 01234567 01234567 For (s) Uptime (s) Uptime ------0/0/CPU0 1 11111111 11111111 335147 335147 100.0000 0/2/CPU0 1 11111111 11111111 335147 335147 100.0000 0/RP0/CPU0 1 11111111 11111111 335147 335147 100.0000 0/RP1/CPU0 1 11111111 11111111 335147 335147 100.0000

Cisco IOS XR Getting Started Guide 3-27 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Bringing Up and Verifying the Non-DSC LCC R3.3 Beta Draft—Cisco Confidential Information Bringing Up and Verifying the Non-DSC LCC

When the FCC is 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. Apply power to the second LCC. 2. show controllers fabric rack all detail 3. show controllers fabric plane all detail 4. show controllers fabric connectivity all detail 5. On the external Catalyst switches, verify that the links are not unidirectional. 6. exit

Detailed Steps

Command or Action Purpose Step 1 Apply power to the second LCC. Starts up the LCC. • Allow the chassis to fully boot. • Verify that “IOS XR RUN” appears on the RP faceplates. • In Rack F0, verify that the indicator LED on the OIM LED panel is green for each 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. • If the RPs fail to boot properly, see the Cisco CRS-1 Multishelf Troubleshooting Guide. Step 2 show controllers fabric rack all detail Displays the status of all racks in the system. • In a properly operating system, the rack Example: status for all racks should be Normal, and RP/0/RP0/CPU0:router(admin)# show controllers fabric rack the server status should be Present. all detail • See the Cisco CRS-1 Multishelf Troubleshooting Guide for more information.

Cisco IOS XR Getting Started Guide 3-28 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Verifying the Spanning Tree R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 3 show controllers fabric plane all detail Displays the status of all racks and additional information for racks in install mode. Example: • Wait for the status in the Admin State and RP/0/RP0/CPU0:router(admin)# show controllers fabric plane Oper State columns to change to UP for all detail all planes. • See the Cisco CRS-1 Multishelf Troubleshooting Guide for more information. Step 4 show controllers fabric connectivity all detail Displays the LCC cards that can communicate with all eight fabric planes. Example: • The expected output should contain a RP/0/RP0/CPU0:router(admin)# show controllers fabric series of ‘1’s for each of the fabric planes connectivity all detail 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 “.” • If the fabric planes are down, or unable to communicate with the line cards, see the Cisco CRS-1 Multishelf Troubleshooting Guide. Step 5 On the external Catalyst switches, verify that the links are not Verifies that the links from the chassis to the unidirectional. 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-15. 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 the FCC are up and running, it is time to verify the spanning tree on the control network as described in the following procedure.

Cisco IOS XR Getting Started Guide 3-29 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Verifying the Spanning Tree R3.3 Beta Draft—Cisco Confidential Information

Summary Steps

1. show platform 2. show spantree mst 1 detail location rack/slot/cpu0

Cisco IOS XR Getting Started Guide 3-30 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Verifying the Spanning Tree R3.3 Beta Draft—Cisco Confidential Information

Detailed Steps

Cisco IOS XR Getting Started Guide 3-31 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Verifying the Spanning Tree R3.3 Beta Draft—Cisco Confidential Information

Cisco IOS XR Getting Started Guide 3-32 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Verifying the Spanning Tree R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 1 admin Places the router in administration EXEC mode. Example: • All commands listed in this procedure RP/0/RP0/CPU0:router# admin should be entered on the pre-existing single-chassis system. Step 2 show platform Displays the status of all LCC modules. • The state for all modules should be Example: IOS XR RUN. RP/0/RP0/CPU0:router(admin)# show platform • It can take a few minutes for all LCC modules to start up. • If the DSC is unable to communicate with the equipment, see the Cisco CRS-1 Multishelf Troubleshooting Guide. Note To view the status of all cards and modules, the show platform command must be executed in administration EXEC mode. Step 3 end Changes mode from administration EXEC mode to EXEC mode. Example: RP/0/RP0/CPU0:router(admin)# end Step 4 show spantree mst 1 detail location rack/slot/cpu0 Verifies the spanning tree. • Enter this command for each RP and Example: SCGE card in the system. RP/0/RP0/CPU0:router# show spantree mst 1 detail location 0/rp0/cpu0 • The output for each RP and SCGE card RP/0/RP0/CPU0:router# show spantree mst 1 detail location should display the following: 0/rp1/cpu0 – In the switched Interface column, one RP/0/RP0/CPU0:router# show spantree mst 1 detail location 1/rp0/cpu0 GE port should be in the forwarding RP/0/RP0/CPU0:router# show spantree mst 1 detail location (FWD) state. 1/rp1/cpu0 RP/0/RP0/CPU0:router# show spantree mst 1 detail location – Each RP and SCGE card should F0/SC0/cpu0 display the same designated root RP/0/RP0/CPU0:router# show spantree mst 1 detail location MAC address. F0/SC1/cpu0 – 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-15. • For more information to troubleshoot the control Ethernet network, see the Cisco CRS-1 Multishelf Troubleshooting Guide.

Cisco IOS XR Getting Started Guide 3-33 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Verifying the Spanning Tree R3.3 Beta Draft—Cisco Confidential Information

Examples

This section contains examples for the following subjects: • Verify That the FCC and Non-DSC LCC Are Communicating with the DSC, page 3-34 • Verify the Spanning Tree, page 3-35

Verify That the FCC 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

Cisco IOS XR Getting Started Guide 3-34 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Verifying the Spanning Tree R3.3 Beta Draft—Cisco Confidential Information

RP/0/RP0/CPU0:router(admin)# end

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# show spantree mst 1 detail location 0/rp0/cpu0

Instance 1 Vlans mapped: 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 00-05-9a-3e-89-4f Bridge ID Priority 32769 (32768 + 1) Bridge Max Age 8 sec 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

RP/0/RP0/CPU0:router# show spantree mst 1 detail location 0/rp1/cpu0

Instance 1 Vlans mapped: 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 00-05-9a-39-91-14 Bridge ID Priority 32769 (32768 + 1) Bridge Max Age 8 sec 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

RP/0/RP0/CPU0:router# show spantree mst 1 detail location 1/rp0/cpu0

Instance 1 Vlans mapped: 1

Cisco IOS XR Getting Started Guide 3-35 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Verifying the Spanning Tree R3.3 Beta Draft—Cisco Confidential Information

Designated Root 00-0e-39-fe-70-00 Designated Root Priority 1 (0 + 1) Designated Root Port GE_Port_0

Bridge ID MAC ADDR 00-05-9a-3e-89-2a Bridge ID Priority 32769 (32768 + 1) Bridge Max Age 8 sec 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

RP/0/RP0/CPU0:router# show spantree mst 1 detail location 1/rp1/cpu0

Instance 1 Vlans mapped: 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 00-05-9a-3e-89-fe Bridge ID Priority 32769 (32768 + 1) Bridge Max Age 8 sec 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# show spantree mst 1 detail location F0/SC0/cpu0

Instance 1 Vlans mapped: 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 00-05-9a-39-91-be Bridge ID Priority 32769 (32768 + 1) Bridge Max Age 8 sec 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

RP/0/RP0/CPU0:router# show spantree mst 1 detail location F0/SC1/cpu0

Instance 1 Vlans mapped: 1

Designated Root 00-0e-39-fe-70-00

Cisco IOS XR Getting Started Guide 3-36 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Verifying Fabric Cabling Connections R3.3 Beta Draft—Cisco Confidential Information

Designated Root Priority 1 (0 + 1) Designated Root Port GE_Port_1

Bridge ID MAC ADDR 00-05-9a-39-91-68 Bridge ID Priority 32769 (32768 + 1) Bridge Max Age 8 sec 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, a fiber module LED panel, or an FM LED panel. This panel goes into slot LM0 or LM1 in a fabric card chassis.The OIM LED panel provides connectivity

Cisco IOS XR Getting Started Guide 3-37 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Verifying Fabric Cabling Connections R3.3 Beta Draft—Cisco Confidential Information

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-3 describes the possible states of the LEDs shown in Figure 3-5.

Figure 3-5 Optical Interface Module LED Panel (Part CRS-FCC-LED)

8 4 0

9 5 1

10 6 2

11 7 3 J0

8 4 0 9 5 1 8 4 0 10 6 2

11 7 3 J1 9 5 1

8 4 0

9 5 1 10 6 2 10 6 2 11 7 3 J2 11 7 3 8 4 0

9 5 1

10 6 2 11 7 3 J0 J3

8 4 0

9 5 1

10 6 2

11 7 3 J4

8 4 0

9 5 1

10 6 2

11 7 3 J5

8 4 0

9 5 1

10 6 2

11 7 3 J6

8 4 0

9 5 1

10 6 2

11 7 3 J7

8 4 0

9 5 1

10 6 2

11 7 3 J8 129913

Cisco IOS XR Getting Started Guide 3-38 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Verifying Fabric Cabling Connections R3.3 Beta Draft—Cisco Confidential Information

Table 3-3 LED Status Interpretation

LED State and Color Meaning If the LED is off, it can mean: • The board to which the cable is connected is powered off at one end or the other Off • The board is not present • The cable not connected at one end or the other. Green The cable is properly connected at both ends, and data transmission is okay. Yellow The cable is properly connected at both ends, but there are some data errors. The cable is not connected to the correct place (when more than one cable is Red incorrect). The cable is not connected to the correct place (when the cable is the only or “first” Blinking red such cable) The blinking LED indicates the place where the first and only incorrect cable should Blinking green be connected (corresponds to the blinking red above).

Because the OIM LED panel is present only in the fabric card chassis, the LEDs indicate the status of the bundles in the fabric card chassis only. Therefore, if a connection is wrong, the equipment assumes that the connection at the line card chassis is fixed, and the connection at the fabric card chassis is the one that needs to be relocated to the correct position as indicated by the LEDs. Bundles are mapped to LEDs as follows: The OIM LED panel has 9 rows of 12 LEDs— the 9 rows correspond to the 9 connectors for each slot, and 12 LEDs correspond to the 12 slots in the cage. Separate OIM LED panels provide status for the upper and lower card cages. The LED rows map to the connector number, and the LEDs in each LED row map to the slot number. The following description helps explain the states of LEDs on the OIM LED panel. In this example, assume txA and txB are transmitting ports on the S13 fabric card in the line card chassis. Port rxA is the link port on the S2 fabric card of the fabric card chassis that should receive data and idle cells from txA, and rxB is the link port on the S2 fabric card of the fabric card chassis that should receive data and idle cells from txB. Now assume that txA has been connected to rxA. This connection causes the LED corresponding to bundle rxA to alight green. If txB is incorrectly connected to rxX, the LED corresponding to the bundle of rxX alights red, and the LED corresponding to the bundle of rxB alights as blinking green. See Figure 3-6 to illustrate this relationship between the OIM LED panel LEDs and the bundles and slots involved in this connection. Figure 3-6 depicts one row of LEDs on the OIM LED panel.

Cisco IOS XR Getting Started Guide 3-39 Chapter 3 Bringing Up the Cisco IOS XR Software on a Multishelf System Troubleshooting Tips R3.3 Beta Draft—Cisco Confidential Information

Figure 3-6 Illustration of How OIM LED Panel LEDs Map to Bundles and Slots (Single-Module Cabling)

OIM11 OIM10OIM9 OIM1 OIM0

1 rxA 2 rxX rxB rxA txA 3 rxB 8 4 0

9 5 1 rxC 10 6 2

11 7 3 txB

txC 138285 S13 card in S2 cards in Fabric Card Chassis Line Card Chassis

1 Wrong connection—solid red light 3 Port rxA—solid green light 2 Port rxB—blinking green light

Troubleshooting Tips

For detailed instructions to troubleshoot a multishelf system, see Cisco CRS-1 Multishelf Troubleshooting Guide.

Where to Go Next

For information on configuring basic router features, see Chapter 4, “Configuring General Router Features.”

Cisco IOS XR Getting Started Guide 3-40 R3.3 Beta Draft—Cisco Confidential Information

CHAPTER 4

Configuring General Router Features

Beta Draft Cisco Confidential Information

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-15 • Managing Configuration Sessions, page 4-21 • Configuring the Router Hostname, page 4-33 • Configuring the Management Ethernet Interface, page 4-34 • Manually Setting the Router Clock, page 4-39 • Where to Go Next, page 4-41

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 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 default SDR and other named SDRs.

Cisco IOS XR Getting Started Guide 4-1 Chapter 4 Configuring General Router Features Connecting and Communicating with the Router R3.3 Beta Draft—Cisco Confidential Information

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 default SDR, you must connect to the active RP for the default 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 default 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 default 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 default 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 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. Connections are made either through a direct physical connection to the Console port of the primary route processor (RP) or from a remote location using a modem or an Ethernet connection. • 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 performance route processor 1 (PRP-1) connections for a Cisco XR 12000 Series Router. • Figure 4-4 shows the performance route processor 2 (PRP-2) connections for a Cisco XR 12000 Series Router.

Cisco IOS XR Getting Started Guide 4-2 Chapter 4 Configuring General Router Features Connecting and Communicating with the Router R3.3 Beta Draft—Cisco Confidential Information

Figure 4-1 Communication Ports on the RP for a Cisco CRS-1 16-Slot Line Card Chassis

RP RJ-45 cable

Local terminal or terminal server for CLI communication. Console AUX

RJ-45 cable

HDD

Remote terminal for CLI communication.

PC Card (disk1:)

CNTL ETH 0 Optical GigE for control plane:

CNTL ETH 1 not user-configurable Management Ethernet connection Network MGMT ETH for out-of-band network communciation Remote CLI, CWI, XML, or SNMP communication.

Primary Status 116547 The first time a router is started, you must use a direct connection to the 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-34. 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.

Cisco IOS XR Getting Started Guide 4-3 Chapter 4 Configuring General Router Features Connecting and Communicating with the Router R3.3 Beta Draft—Cisco Confidential Information

Figure 4-2 Communication Ports on the RP for a Cisco CRS-1 8-Slot Line Card Chassis RJ-45 cable

Local terminal or terminal server for CLI communication. Console Terminal connection

AUX Modem connection RJ-45 cable ALARM PID/VID

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

LED status displays (alphanumeric) Primary Primary RP (On=Primary) Status

Card status (Green=OK) 122803

Cisco IOS XR Getting Started Guide 4-4 Chapter 4 Configuring General Router Features Connecting and Communicating with the Router R3.3 Beta Draft—Cisco Confidential Information

Figure 4-3 Communication Ports on the PRP-1 for a Cisco XR 12000 Series Router

PC User-removable flash disk1: CARD stores installation PIE files.

A second internal Flash disk0: EJECT stores installed software and active configurations.

SLOT-2 SLOT-1 PRIMARY Ethernet cable Network ETH0

LINK EN Remote CLI, CWI, XML, TX RX or SNMP communication. PRIMARY Remote file storage. ETH1

LINK EN TX RX RJ-45 cable AUX Modem connection Remote terminal for CLI communication. Console Terminal connection

RJ-45 cable RESET

Local terminal or terminal server for PERFORMANCE ROUTE PROCESSOR 1 (PRP-1) CLI communication.

LED status displays (alphanumeric) 129010

Cisco IOS XR Getting Started Guide 4-5 Chapter 4 Configuring General Router Features Connecting and Communicating with the Router R3.3 Beta Draft—Cisco Confidential Information

Figure 4-4 Communication Ports on the PRP-2 for a Cisco XR 12000 Series Router

User-removable flash disk1: stores installation PIE files

A second internal flash disk0: stores installed software and active configurations

SLOT-0SLOT-1 ETH 0 Ethernet cable LINK Network DATA ETH 1 Remote CLI, CWI, XML, LINK or SNMP communication. DATA BITS 0 Remote file storage SIG

ACT BITS 1 SIG

ACT RJ-45 cable AUX Modem connection

Remote terminal for ETH 2 CONSOLE CLI communication Terminal connection RJ-45 cable

Local terminal or PERFORMANCE ROUTE PROCESSOR 2 terminal server for

CLI communication RESET

LED status displays (alphanumeric) 138282

The following sections describe three ways to connect to the router: • 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

Cisco IOS XR Getting Started Guide 4-6 Chapter 4 Configuring General Router Features Connecting and Communicating with the Router R3.3 Beta Draft—Cisco Confidential Information Establishing a Connection Through the Console Port

To connect to the router through the console port, perform the following procedure.

SUMMARY STEPS

1. Identify the primary RP. 2. Connect a terminal to the Console port of the primary RP. 3. Start the terminal emulation program. 4. Press Enter. 5. Log in to the router.

DETAILED STEPS

Command or Action Purpose Step 1 Identify the primary RP. Identifies the RP to which you must connect in the next step. • This step is not required when the router hosts only one RP. • On a Cisco CRS-1 router, the primary RP is identified by a lighted Primary LED on the RP front panel. • On a Cisco XR 12000 Series Router, the primary RP is identified by the alphanumeric display: PRI RP. Step 2 Connect a terminal to the Console port of the primary Establishes a communications path to the router. RP. • During the initial 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 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 • For information on the cable requirements for the Console port, see the hardware documentation listed in the “Related Documents” section on page xii.

Cisco IOS XR Getting Started Guide 4-7 Chapter 4 Configuring General Router Features Connecting and Communicating with the Router R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 3 Start the terminal emulation program. (Optional) Prepares a computer for router communications. • 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. Step 4 Press Enter. Initiates communication with the router. • 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 5 Log in to the router. Establishes your access rights for the router management session. • 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.

Cisco IOS XR Getting Started Guide 4-8 Chapter 4 Configuring General Router Features Connecting and Communicating with the Router R3.3 Beta Draft—Cisco Confidential Information

To establish a connection through a terminal server, perform the following procedure:

SUMMARY STEPS

1. Install and configure the terminal server. 2. Connect the terminal server to the Console port of the target RP. 3. Power on the router. 4. Identify the target RP. 5. telnet access-server-address port 6. Press Enter. 7. Log in to the router.

DETAILED STEPS

Command or Action Purpose Step 1 Install and configure the terminal server. Prepares the terminal server for communications with the router and with Telnet clients. • 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. 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: – Bits per second: 9600/9600 – Data bits: 8 – Parity: None – Stop bit: 2 – Flow control: None • For information on the cable requirements for the Console port, see the hardware documentation listed in the “Related Documents” section on page xii. • To enable terminal server connections to the Console ports on two RPs, install a cable between each Console port and the terminal server.

Cisco IOS XR Getting Started Guide 4-9 Chapter 4 Configuring General Router Features Connecting and Communicating with the Router R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 3 Power on the router. Starts 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 xii. Step 4 Identify the target RP. Identifies the RP to which you connect in the next step. • This step is not required when the router hosts only one RP. • On a Cisco CRS-1 router, the primary RP is identified by a lighted Primary LED on the RP front panel. • On a Cisco XR 12000 Series Router, the primary 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. Step 5 telnet access-server-address port Establishes a Telnet session with the terminal server. • 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. Step 6 Press Enter. (Optional) Initiates communications with the router. • 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 7 Log in to the router. Establishes your access rights for the router management session. • 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-36.

Cisco IOS XR Getting Started Guide 4-10 Chapter 4 Configuring General Router Features Logging In to a Router or an SDR R3.3 Beta Draft—Cisco Confidential Information

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. • 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. The SSH server handles both Secure Shell Version 1 (SSHv1) and SSHv2 incoming client connections for both IPv4 and IPv6 address families.

Note IPv6 is not supported on Cisco XR 12000 Series routers.

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 default SDR on a system with multiple SDRs, you can manage general features that apply to the entire system and the interfaces assigned to the default SDR. If you log in to an 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 default SDR • Passwords configured for specific lines on the router (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.

Cisco IOS XR Getting Started Guide 4-11 Chapter 4 Configuring General Router Features CLI Prompt R3.3 Beta Draft—Cisco Confidential Information

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 into an SDR using a root-system username from the default 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 Task ID Reference 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 Description type Type of interface or card with which you are communicating. For most user communication tasks, the type is “RP.” rack Chassis number of the rack. In a single-shelf system, the rack is always “0.” slot Slot in which the RP is installed. In a Cisco CRS-1 router, the 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. module 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. router-name Hostname of the router or SDR. The hostname is usually defined during initial configuration of the router, as described in the “Configuring the Router Hostname” section on page 4-33.

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#

Cisco IOS XR Getting Started Guide 4-12 Chapter 4 Configuring General Router Features User Access Privileges R3.3 Beta Draft—Cisco Confidential Information 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

Cisco IOS XR Getting Started Guide 4-13 Chapter 4 Configuring General Router Features User Access Privileges R3.3 Beta Draft—Cisco Confidential Information

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 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 Privileges root-system Display and execute all commands for all SDRs in the system. root-lr Display and execute all commands within a single SDR. sysadmin 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. netadmin Configure network protocols, such as Border Gateway Protocol (BGP) and Open Shortest Path First (OSPF) (usually network administrators). operator Perform day-to-day monitoring activities, and have limited configuration rights. cisco-support Debug and troubleshoot features (usually Cisco support personnel).

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 Description show user Displays your user name. show user group Displays the user groups assigned to your account. show user tasks Displays the task IDs assigned to your account.

Cisco IOS XR Getting Started Guide 4-14 Chapter 4 Configuring General Router Features Navigating the Cisco IOS XR Command Modes R3.3 Beta Draft—Cisco Confidential Information

Table 4-3 Options to Display Information About Your Account (continued)

Command Description show user all Displays all user groups and task ID information for your account. show aaa usergroup group-name Displays the task IDs assigned to a user group.

Examples

To display your username, enter the show user command: RP/0/RP0/CPU0:router# show user

Username: crs

To display the tasks assigned to your account and your rights to those tasks, enter the show user tasks command: RP/0/RP0/CPU0:router# show user tasks

Task: basic-services : READ WRITE EXECUTE NOTIFY Task: cdp : READ Task: diag : READ Task: ext-access : READ EXECUTE Task: logging : READ

To display the user groups assigned to your user account, enter the show user group command: RP/0/RP0/CPU0:router# show user group

User group operator

To display the rights assigned to a user group, enter the show aaa usergroup group-name command: RP/0/RP0/CPU0:router# show aaa usergroup operator

User group 'operator' Inherits from task group 'operator'

User group 'operator' has the following combined set of task IDs (including all inherited groups): Task: basic-services : READ WRITE EXECUTE NOTIFY Task: cdp : READ Task: diag : READ Task: ext-access : READ EXECUTE Task: logging : READ

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-16 • Summary of Common Command Modes, page 4-17

Cisco IOS XR Getting Started Guide 4-15 Chapter 4 Configuring General Router Features Navigating the Cisco IOS XR Command Modes R3.3 Beta Draft—Cisco Confidential Information

• Entering EXEC Commands from a Configuration Mode, page 4-19 • Command Mode Navigation Example, page 4-20 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

EXEC mode

Admin EXEC mode

Admin configuration mode Global configuration mode

Configuration submode examples Logical router configuration submode Interface configuration submode

Router configuration submode

Line template configuration submode

Task group configuration submode 116544

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:routername# configure RP/0/RP0/CPU0:routername(config)#

When the router enters interface configuration submode, the prompt changes to include “(config-if)” after the router name: RP/0/RP0/CPU0:routername(config)# interface POS 0/2/0/0 RP/0/RP0/CPU0:routername(config-if)#

Cisco IOS XR Getting Started Guide 4-16 Chapter 4 Configuring General Router Features Navigating the Cisco IOS XR Command Modes R3.3 Beta Draft—Cisco Confidential Information 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 Description EXEC Logging in to a router running the Cisco IOS XR software automatically places the router in EXEC mode. Example: RP/0/RP0/CPU0:router#

EXEC mode enables a basic set of commands to display the operational state of the router and examine the state of an operating system. Most CLI commands in EXEC mode do not change the system operation. The most common EXEC commands are show commands (to display router configuration or operational data) and clear commands (to clear or reset system counters). 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. Global configuration Global configuration mode is the starting point for system configuration. Commands entered in this mode affect the system 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: RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)#

Note The system prompt changes to “router(config)” to indicate that the router is now in global configuration mode. Configuration From the global configuration mode, you can also enter other, more specific command modes. submodes These modes are available based on your assigned access privileges and include protocol-specific, platform-specific, and feature-specific configuration modes. In the following example, MPLS LDP configuration mode is entered from global configuration mode. The prompt for MPLS LDP configuration submode appears as config-ldp. The following command syntax is used for entering configuration MPLS LDP submode: RP/0/RP0/CPU0:router# RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# mpls ldp RP/0/RP0/CPU0:router(config-ldp)

Note The availability of any particular mode depends on the router features and the access rights of the individual user. For example, a configuration mode for configuring access servers is not available on most routers.

Cisco IOS XR Getting Started Guide 4-17 Chapter 4 Configuring General Router Features Navigating the Cisco IOS XR Command Modes R3.3 Beta Draft—Cisco Confidential Information

Table 4-4 Common Command Modes and CLI prompts (continued)

Command Mode Description Interface configuration The interface configuration submode is used to select and configure a hardware interface, such as a Packet-over-SONET/SDH (POS) interface. To enter interface configuration mode from global configuration mode, use an interface command. An interface configuration command always follows an interface global configuration command, which defines the interface type. The following command syntax is used for entering interface configuration submode: RP/0/RP0/CPU0:router(config)# interface POS 0/2/0/0 RP/0/RP0/CPU0:router(config-if)# Router configuration The router configuration submode is used to select and configure a routing protocol, such as BGP, OSPF, or IS-IS. The following command syntax is used for entering router configuration submode: RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router RP/0/RP0/CPU0:router(config-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)# Router submode Router configuration submodes are accessed from router configuration mode. The following configuration 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

Cisco IOS XR Getting Started Guide 4-18 Chapter 4 Configuring General Router Features Navigating the Cisco IOS XR Command Modes R3.3 Beta Draft—Cisco Confidential Information

Table 4-4 Common Command Modes and CLI prompts (continued)

Command Mode Description Administration EXEC The Cisco IOS XR software provides a separate administration EXEC mode for users with the and administration appropriate access permissions. This mode is used primarily to display system-wide parameters, configuration modes configure the administration plane over the control Ethernet, and configure SDRs on multiple-shelf systems. 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. The following command syntax is used for entering administration EXEC and administration configuration submode: RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# RP/0/RP0/CPU0:router(admin)# configure RP/0/RP0/CPU0:router(admin-config)#

ROM Monitor The ROM Monitor is a bootstrap program that initializes the hardware and boots the system when (ROMMON) mode 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

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

Cisco IOS XR Getting Started Guide 4-19 Chapter 4 Configuring General Router Features Navigating the Cisco IOS XR Command Modes R3.3 Beta Draft—Cisco Confidential Information 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: 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 Show AAA configuration and operational data adjacency Adjacency information aliases Display alias commands aps SONET APS information arm IP ARM information arp ARP table as-path-access-list List AS path access lists asic-errors ASIC error information auto-rp Auto-RP Commands bgp BGP show commands buffer-manager Show all buffer manager memory related information calendar Display the system calendar cdp CDP information cef Cisco Express Forwarding cetftp CRS-1 control plane ethernet TFTP server checkpoint Show checkpoint services cinetd Cisco inetd services clns Display CLNS related information clock Display the system clock commit Show commit information community-list List community-list configuration Contents of Non-Volatile memory --More--

Note The commands available to you depend on the router mode and your user group assignments.

Step 3 If you belong to a user group that has configuration privileges, you can place the router in the global configuration mode by entering the configure command: RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)#

Step 4 From global configuration mode, you can place the router in a configuration submode, such as interface configuration mode or a protocol-specific configuration mode.

Cisco IOS XR Getting Started Guide 4-20 Chapter 4 Configuring General Router Features Managing Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information

In the following example, the router enters interface configuration mode and the user selects a POS interface for configuration. The command syntax is interface type rack/slot/module/port. RP/0/RP0/CPU0:router(config)# interface POS 0/2/0/4 RP/0/RP0/CPU0:router(config-if)#

The command mode prompt changes from “(config)” to “(config-if)” and you can now enter configuration commands for the specified interface. Step 5 To exit interface configuration mode and return to global configuration mode, enter the exit command. To return to EXEC mode, enter the end command.

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. The following sections describe the management options for configuration sessions: • Entering Configuration Changes in the Nonactive Target Configuration, page 4-22 • Committing Changes to the Running Configuration, page 4-22 • Displaying Configuration Details with show Commands, page 4-24 • Displaying Configuration Errors, page 4-29 • Reloading a Failed Configuration, page 4-30 • Clearing All Changes to a Target Configuration, page 4-30 • Ending a Configuration Session, page 4-31 • Locking and Unlocking the Running Configuration During Configuration Sessions, page 4-32 Figure 4-6 illustrates the two-stage configuration process.

Figure 4-6 Two-Stage Configuration Process

Stage 1: Stage 2: Create the Enter configuration "Commit" changes target configuration EXEC mode changes to the to the by entering global nonactive target running configuration. configuration mode. configuration.

Automatic Save 116541

Save the target configuration Startup configuration to file, or load a file.

Cisco IOS XR Getting Started Guide 4-21 Chapter 4 Configuring General Router Features Managing Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information Entering Configuration Changes in the Nonactive Target Configuration

When you place the router in global 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.

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 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-22. 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 and Loading Target Configuration Files” section on page 5-9. This example shows a simple configuration session in which the target configuration is created and previewed:

Step 1 To create a new target configuration session, enter global configuration mode using the configure command: RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)#

Step 2 Make changes to the target configuration. These changes do not affect the running configuration. The CLI automatically verifies the syntax of your commands and allows only valid entries: 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

Step 3 To display the inactive changes, use the show configuration command: 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

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.

Cisco IOS XR Getting Started Guide 4-22 Chapter 4 Configuring General Router Features Managing Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information

To commit target configuration changes to the running configuration, enter the commit command by itself or with one of the options described in Table 4-5.

Table 4-5 Commit Command Options

Command Description commit (Default) Merges the target configuration with the running configuration and commits changes only if all changes in the target configuration pass the semantic verification process. If any semantic errors are found, none of the configuration changes takes effect. commit best-effort Merges the target configuration with the running configuration and commits only valid changes (best effort). Some configuration changes might fail due to semantic errors. commit comment line (Optional) Assigns a comment to a commit. • This text comment is displayed in the commit entry displayed with the show configuration commit list [detail] command. • The line argument is the text for the optional comment or label. • The comment option must appear at the end of the command line. If multiple options are entered, all text after the comment option is treated as a comment. commit confirmed (Optional) Commits the configuration on a trial basis for a minimum of seconds 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 an SDR owner to commit the configuration 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.

Cisco IOS XR Getting Started Guide 4-23 Chapter 4 Configuring General Router Features Managing Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information

In the following example, the default commit option is entered: RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# interface POS 0/0/0/2 RP/0/RP0/CPU0:router(config-if)# description faq RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.1.1.1 255.0.0.0 RP/0/RP0/CPU0:router(config-if)# commit

Note 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-31 for more information.

When a target configuration is committed to the running configuration, a configuration change message is logged, as shown in the following example: RP/0/0/0:Aug 6 09:26:17.781 : %LIBTARCFG-6-COMMIT Configuration committed by user ‘user_a'. 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.

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.

Displaying Configuration Details with show Commands

Table 4-6 summarizes the commands used in global configuration mode to display the contents of the target configuration, the running configuration, or a combination of both.

Table 4-6 Configuration show Commands in Global Configuration Mode

Command Description show running-config Displays the contents of the active running configuration. This is the committed configuration that defines the router operations. show running-config sanitized Displays the contents of the active 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. show configuration Displays the changes made to the target configuration. These are the changes that have been entered but not yet committed. show configuration merge Displays the combined contents of the target and running configuration without committing the changes.

Cisco IOS XR Getting Started Guide 4-24 Chapter 4 Configuring General Router Features Managing Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information

Note You can use the show running-config command in the EXEC mode to display the contents of the running configuration.

The following sections provide examples of displaying configuration details: • Displaying the Current Running Configuration, page 4-25 • Displaying the Sanitized Running Configuration, page 4-26 • Displaying the Target (Nonactive) Configuration Changes, page 4-28 • Displaying the Merged Configuration Before Committing the Changes, page 4-28

Displaying the Current Running Configuration

To display the details of the currently running configuration, enter the show running-config command. The running configuration is the active configuration used to operate the router. RP/0/RP1/CPU0:router(config)# show running-config

Building configuration... !! Last configuration change at 11:05:38 UTC Mon May 02 2005 by lab ! 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

Cisco IOS XR Getting Started Guide 4-25 Chapter 4 Configuring General Router Features Managing Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information

load-interval 0 ! interface MgmtEth0/RP1/CPU0/0 ipv4 address 10.11.12.13 255.255.0.0 ! interface POS0/0/0/0 shutdown ! interface POS0/0/0/1 shutdown ! interface POS0/0/0/2 shutdown ! interface POS0/0/0/3 shutdown ! interface POS0/3/0/0 shutdown ! interface POS0/3/0/1 shutdown ! interface POS0/3/0/2 shutdown ! interface POS0/3/0/3 shutdown ! interface preconfigure MgmtEth0/RP0/CPU0/0 shutdown ! router static address-family ipv4 unicast 0.0.0.0/0 MgmtEth0/RP1/CPU0/0 ! ! end

Displaying the Sanitized Running Configuration

To display the sanitized version of the currently running configuration, enter the show running-config sanitized command. 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 ! hostname logging console debugging telnet ipv4 server max-servers 5 username password 7 group root-system group cisco-support ! ntp interface Loopback99 broadcast !

Cisco IOS XR Getting Started Guide 4-26 Chapter 4 Configuring General Router Features Managing Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information

interface Loopback999 broadcast ! interface Loopback9999 broadcast ! authenticate max-associations 2000 ! interface Loopback0 ipv4 address 10.0.0.0 255.0.0.0 load-interval 0 ! interface Loopback1 ipv4 address 10.0.0.0 255.0.0.0 ! interface Loopback7 load-interval 0 ! interface Loopback2000 load-interval 0 ! interface Loopback2001 load-interval 0 ! interface Loopback2003 load-interval 0 ! interface MgmtEth0/RP1/CPU0/0 ipv4 address 10.0.0.0 255.0.0.0 ! interface POS0/0/0/0 shutdown ! interface POS0/0/0/1 shutdown ! interface POS0/0/0/2 shutdown ! interface POS0/0/0/3 shutdown ! interface POS0/3/0/0 shutdown ! interface POS0/3/0/1 shutdown ! interface POS0/3/0/2 shutdown ! interface POS0/3/0/3 shutdown ! interface preconfigure MgmtEth0/RP0/CPU0/0 shutdown ! router static address-family ipv4 unicast 0.0.0.0/0 MgmtEth0/RP1/CPU0/0 ! ! end

Cisco IOS XR Getting Started Guide 4-27 Chapter 4 Configuring General Router Features Managing Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information

Displaying the Target (Nonactive) Configuration Changes

To display the changes you have entered into the nonactive target configuration, enter the show configuration command. The target configuration includes changes that have not yet been committed, and are therefore not part of the active running configuration. 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

Displaying the Merged Configuration Before Committing the Changes

To display the currently running configuration combined with the nonactive changes from the target configuration, enter the show configuration merge command in any configuration mode. In the following example, the user first displays the active configuration, then makes the necessary configuration changes, and displays the “merged” configuration. The merged configuration provides a preview of what the new active configuration will be after the commit command is executed.

Note The “merged” 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.

Step 1 Display the currently running configuration: RP/0/RP0/CPU0:router# show running-config

Building configuration... !! Last configuration change at 16:52:49 UTC Sun March 10 2004 by lab ! hostname router shutdown end

Step 2 Open a target configuration session and enter configuration changes: 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

Step 3 Display the “merged” configuration before committing the new settings: RP/0/RP0/CPU0:router(config-if)# show configuration merge Building configuration... hostname router interface POS0/3/0/3 description faq ipv4 address 10.1.1.1 255.0.0.0 shutdown end

Cisco IOS XR Getting Started Guide 4-28 Chapter 4 Configuring General Router Features Managing Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information

Displaying Configuration Errors

Configuration changes are automatically verified during the commit operation, and a configuration message is displayed if one or more configuration entries fail. To display the cause of each failure, enter the show configuration failed commands, as summarized in Table 4-7.

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.

Table 4-7 Commands to Display Configuration Failure Details

Command Description show configuration failed Displays commit error messages and descriptions generated during the last configuration commit. show configuration failed load Displays any syntax errors found in a configuration loaded with the load command. show configuration failed noerror Displays only commit error messages (without error descriptions).

In the following example, the configuration commit encounters an error: RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# taskgroup bgp RP/0/RP0/CPU0:router(config-tg)# description this is a test of an invalid taskgroup RP/0/RP0/CPU0:router(config-tg)# commit

% Failed to commit one or more configuration items. Please use 'show configurati on failed' to view the errors

To display the configuration items that failed, enter the show configuration failed command. The output from this command includes a description of the error: 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 !

To display the configuration items that failed without error descriptions, enter 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 !

Cisco IOS XR Getting Started Guide 4-29 Chapter 4 Configuring General Router Features Managing Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information 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. You can load the configuration changes into the target configuration, correct the errors, and commit the changes. To load a failed configuration, enter the load configuration failed command, as shown in the following example: RP/0/0/CPU0:router(config-tg)# load configuration failed

RP/0/0/CPU0:router(config)# show configuration

Building configuration... taskgroup bgp ! end

In the preceding example, the show configuration command displays the target configuration, which includes the failed configuration.

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. This command deletes any configuration changes that have not been committed. 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

Cisco IOS XR Getting Started Guide 4-30 Chapter 4 Configuring General Router Features Managing Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information Ending a Configuration Session

The commands used to end a configuration session are summarized in Table 4-8.

Table 4-8 Commands to End a Configuration Sessions

Command Description end Returns to the next highest mode, one step at a time. If you use this command to exit configuration mode when uncommitted changes are present, the router prompts you to select 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 is used to log out of the system. exit Returns directly to EXEC mode from any configuration mode. You are not prompted to save any uncommitted changes to the target configuration. abort Discards any changes to the target configuration and returns directly to EXEC mode. No warning is given before the configuration changes are deleted.

The following sections provide examples of ending a configuration session: • Exit Command Example, page 4-31 • End Command Example, page 4-31 • Abort Command Example, page 4-32

Exit Command Example

To return to the previous configuration mode without saving changes to the target configuration, use the exit command. When you use this command to return to the EXEC mode, you are prompted to commit any uncommitted changes. 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)# exit Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]:yes RP/0/RP0/CPU0:router#

Note In EXEC mode, the exit command is used to log out of the system.

End Command Example

To return to EXEC mode without saving changes to the target configuration, use the end command. You are prompted to commit any uncommitted changes. RP/0/RP0/CPU0:router# configure

Cisco IOS XR Getting Started Guide 4-31 Chapter 4 Configuring General Router Features Managing Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information

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)# end Uncommitted changes found, commit them? [yes]: no RP/0/RP0/CPU0:router#

Tip You can also end a configuration session by pressing Ctrl-Z.

Abort Command Example

To discard any changes to the target configuration and return to EXEC mode, use the abort command. You are not prompted to commit any uncommitted changes: 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#

Locking and Unlocking the Running Configuration During Configuration Sessions

When you place the router in global configuration mode with the configure command, a new target configuration is automatically created. More than one user can open a target configuration session at a time, allowing multiple users to work on separate target configurations. By default, 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. You can lock the running configuration for the duration of your own configuration session and use commands to display the other active configuration sections, as described in Table 4-9. Table 4-9 Configuration Session Commands

Command Description show configuration sessions Displays the other configuration sessions on the router. configure Enters global configuration mode and allows other users to commit target configurations.

Cisco IOS XR Getting Started Guide 4-32 Chapter 4 Configuring General Router Features Configuring the Router Hostname R3.3 Beta Draft—Cisco Confidential Information

Table 4-9 Configuration Session Commands (continued)

Command Description configure exclusive Enters global configuration mode and denies other users the ability to commit changes while your configuration session is active. Other users can still enter global configuration mode and populate a target configuration, but they cannot commit those changes to the running configuration until you exit your exclusive configuration session. Note If the configuration is already locked by another user, the configure exclusive command fails. exit or end Unlocks the other configuration sessions by ending your configuration session and returning to EXEC mode.

To display the current configuration sessions, enter the show configuration sessions command in EXEC mode. Exclusive configuration sessions are noted by an asterisk (*), as shown in the following example: RP/0/RP0/CPU0:router# show configuration sessions

Session Line User Date Lock 00000000-000650a4-00000000 dummy_line root Thu Oct 3 12:20:12 2003 00000000-0006a0a3-00000000 dummy_line root Thu Oct 3 12:24:23 2003 *

To lock the running configuration so that other users cannot commit changes while your configuration session is active, enter the configure exclusive command: RP/0/RP0/CPU0:router# configure exclusive RP/0/RP0/CPU0:router(config)#

The running configuration is unlocked when the user who entered the configuration mode using the configure exclusive command exits the configuration mode: RP/0/RP0/CPU0:router(config)# exit

Configuring the Router Hostname

The hostname identifies a router 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 router on the network. To configure the hostname, perform the following procedure:

SUMMARY STEPS

1. configure 2. hostname router-name 3. commit

Cisco IOS XR Getting Started Guide 4-33 Chapter 4 Configuring General Router Features Configuring the Management Ethernet Interface R3.3 Beta Draft—Cisco Confidential Information

Example

The following example shows how to configure the hostname for the router: RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# hostname new_name 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)#

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.

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-10 describes the Management Ethernet interface name syntax.

Table 4-10 Management Ethernet Interface Name Syntax Description

Syntax Components Description type Interface type for a Management Ethernet port is “MgmtEth.” rack Chassis number of the rack. In a single-shelf system, the rack is always “0.” slot Physical slot of the RP on which the interface is located. For a Cisco CRS-1 router, the slot is “RP0” or “RP1.” For a Cisco XR 12000 Series Router, the PRPs may be installed in slots 0 through 15, depending on the router model.

Cisco IOS XR Getting Started Guide 4-34 Chapter 4 Configuring General Router Features Configuring the Management Ethernet Interface R3.3 Beta Draft—Cisco Confidential Information

Table 4-10 Management Ethernet Interface Name Syntax Description (continued)

Syntax Components Description module On an RP, the module is “CPU0.” port On Cisco XR 12000 Series Routers, there are two Ethernet ports on PRP-1 cards and 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. Specify 0 for the MGMT ETH interface on an RP.

Table 4-10 provides examples of Management Ethernet interface names for a single-shelf system.

Table 4-11 Management Ethernet Interface Names for Single-Shelf Systems

Management Interface Interface Name Example Cisco CRS-1 RP in slot RP0 MgmtEth0/RP0/CPU0/0 router(config)# interface MgmtEth0/RP0/CPU0/0 Cisco CRS-1 RP in slot RP1 MgmtEth0/RP1/CPU0/0 router(config)# interface MgmtEth0/RP1/CPU0/0 Cisco XR 12000 Series Router PRP MgmtEth0/0/CPU0/0 router(config)# interface MgmtEth0/0/CPU0/0 in slot 0, port ETH0 Cisco XR 12000 Series Router PRP MgmtEth0/0/CPU0/1 router(config)# interface MgmtEth0/0/CPU0/1 in slot 0, port ETH1 Cisco XR 12000 Series Router PRP MgmtEth0/1/CPU0/0 router(config)# interface MgmtEth0/1/CPU0/0 in slot 1, port ETH0 Cisco XR 12000 Series Router PRP MgmtEth0/1/CPU0/1 router(config)# interface MgmtEth0/1/CPU0/1 in slot 1, port ETH1

Cisco IOS XR Getting Started Guide 4-35 Chapter 4 Configuring General Router Features Configuring the Management Ethernet Interface R3.3 Beta Draft—Cisco Confidential Information Displaying the Available Management Ethernet Interfaces

To display the router interfaces, enter the show interface brief command in EXEC mode as follows: RP/0/0/CPU0:router# show interface brief

Intf Intf LineP Encap MTU BW Name State State Type (byte) (Kbps)

------

Nu0 up up Null 1500 Unknown

Mg0/0/CPU0/0 up up ARPA 1514 100000

Mg0/0/CPU0/1 admin-down admin-down ARPA 1514 10000

PO0/3/0/0 admin-down admin-down HDLC 4474 155520

PO0/3/0/1 admin-down admin-down HDLC 4474 155520

PO0/3/0/2 admin-down admin-down HDLC 4474 155520

PO0/3/0/3 admin-down admin-down HDLC 4474 155520

PO0/3/0/4 admin-down admin-down HDLC 4474 155520

PO0/3/0/5 admin-down admin-down HDLC 4474 155520

PO0/3/0/6 admin-down admin-down HDLC 4474 155520

PO0/3/0/7 admin-down admin-down HDLC 4474 155520 . . .

The Management Ethernet interfaces are listed with the prefix Mg in the Intf Name column.

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.

Cisco IOS XR Getting Started Guide 4-36 Chapter 4 Configuring General Router Features Configuring the Management Ethernet Interface R3.3 Beta Draft—Cisco Confidential Information

SUMMARY STEPS

1. configure 2. interface MgmtEth0/slot/CPU0/port 3. ipv4 address ipv4-address subnet-mask 4. no shutdown 5. exit 6. router static address-family ipv4 unicast 0.0.0.0/0 default-gateway 7. commit 8. end 9. show interfaces MgmtEth0/slot/CPU0/port

DETAILED STEPS

Command or Action Purpose Step 1 configure Enters global configuration mode.

Example: RP/0/RP0/CPU0:router# configure

Step 2 interface MgmtEth0/slot/CPU0/port Enters interface configuration mode and specifies the Management Ethernet interface of the primary RP. Example: RP/0/RP0/CPU0:router(config)# interface • The syntax is MgmtEth0/RP0/CPU0/0 interface typerack/slot/module/port: The command parameters are described in Table 4-10. Step 3 ipv4 address ipv4-address subnet-mask Assigns an IP address and subnet mask to the interface.

Example: RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.1.1.1 255.0.0.0 Step 4 no shutdown Places the interface in an “up” state.

Example: RP/0/RP0/CPU0:router(config-if)# no shutdown Step 5 exit Exits the Management Ethernet interface configuration mode.

Cisco IOS XR Getting Started Guide 4-37 Chapter 4 Configuring General Router Features Configuring the Management Ethernet Interface R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 6 router static address family ipv4 unicast 0.0.0.0/0 Configures a default route to use for default-gateway communications with devices on other networks.

Example: • Replace default-gateway with the IP RP/0/RP0/CPU0:router (config)# router static address of the local gateway that can be address-family ipv4 unicast 0.0.0.0/0 12.25.0.1 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 MgmtEth0/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# RP/0/RP0/CPU0:router# show interfaces MgmtEth 0/RP1/CPU0/0 MgmtEth0/RP1/CPU0/0 is up, line protocol is up Hardware is Management Ethernet, address is 0005.9a39.910c (bia 0005.9a39.910c ) Internet address is 10.1.1.1 MTU 1514 bytes, BW 100000 Kbit reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, Full-duplex, 100Mb/s loopback not set ARP type ARPA, ARP timeout 01:00:00 Last clearing of "show interface" counters never 30 second input rate 0 bits/sec, 0 packets/sec

Cisco IOS XR Getting Started Guide 4-38 Chapter 4 Configuring General Router Features Manually Setting the Router Clock R3.3 Beta Draft—Cisco Confidential Information

30 second output rate 0 bits/sec, 0 packets/sec 15205 packets input, 7467959 bytes, 0 total input drops 0 drops for unrecognized upper-level protocol Received 2352 broadcast packets, 0 multicast packets 0 runts, 0 giants, 0 throttles, 0 parity 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 13528 packets output, 656060 bytes, 0 total output drops Output 56 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

--More--

Related Documents

Related Topic Document Title Additional information on configuring management Cisco IOS XR Interface and Hardware Component Configuration interfaces 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. configure 2. clock timezone zone hours-offset 3. commit 4. end 5. clock set hh:mm:ss dd mm yyyy 6. clock update-calendar 7. show clock

Cisco IOS XR Getting Started Guide 4-39 Chapter 4 Configuring General Router Features Manually Setting the Router Clock R3.3 Beta Draft—Cisco Confidential Information

DETAILED STEPS

Command or Action Purpose Step 1 configure Enters global configuration mode.

Example: RP/0/RP0/CPU0:router# configure Step 2 clock timezone zone hours-offset Sets the time zone for the router clock. • The clock timezone command should be Example: entered before the clock is set because it defines RP/0/RP0/CPU0:router(config)# clock timezone pst -8 the difference between the system time and UTC. Note 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 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 Ends the configuration session and returns to EXEC mode.

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

Cisco IOS XR Getting Started Guide 4-40 Chapter 4 Configuring General Router Features Where to Go Next R3.3 Beta Draft—Cisco Confidential Information

Step 6 clock update-calendar Updates the hardware clock (calendar clock) with the new clock settings.

Example: • The hardware clock is battery operated and runs RP/0/RP0/CPU0:router# clock update-calendar continuously, even if the router is powered off or rebooted. Step 7 show clock Displays the clock setting. • Use this command to verify the settings. Example: RP/0/RP0/CPU0:router# show clock

Examples

In the following example, the manual system clock is configured: RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# clock timezone pst -8 RP/0/RP0/CPU0:router(config)# commit RP/0/RP0/CPU0:router(config)# end RP/0/RP0/CPU0:router# clock set 14:12:00 10 feb 2004 14:12:00.090 PST Tue Feb 10 2004 RP/0/RP0/CPU0:router# clock update-calendar RP/0/RP0/CPU0:router# show clock 14:12:00.090 PST Tue Feb 10 2004

Related Documents

Related Topic Document Title Descriptions of the clock commands available in the Cisco IOS XR System Management Command Cisco IOS XR software Reference Commands used to configure the NTP Cisco IOS XR System Management Command Reference Configuration of the NTP on the Cisco IOS XR software Cisco IOS XR System Management Configuration Guide

Where to Go Next

When you have completed the configuration procedures in this chapter, consider the following resources for additional configuration documentation: • For information on configuring additional general router features, see Chapter 5, “Configuring Additional Router Features.” • For information on using the Cisco IOS XR software more efficiently, see Chapter 6, “CLI Tips, Techniques, and Shortcuts.” • For information on configuring interfaces, see the hardware documents listed in the “Related Documents” section on page xii.

Cisco IOS XR Getting Started Guide 4-41 Chapter 4 Configuring General Router Features Where to Go Next R3.3 Beta Draft—Cisco Confidential Information

Cisco IOS XR Getting Started Guide 4-42 R3.3 Beta Draft—Cisco Confidential Information

CHAPTER 5

Configuring Additional Router Features

Beta Draft Cisco Confidential Information

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

Contents

This chapter contains the following sections: • Configuring the Domain Name and Domain Name Server, page 5-1 • Configuring Telnet, HTTP, and XML Host Services, page 5-2 • Managing Configuration History and Rollback, page 5-3 • Saving and Loading Target Configuration Files, page 5-9 • Configuring Logging and Logging Correlation, page 5-10 • Creating and Modifying User Accounts and User Groups, page 5-13 • Configuration Limiting, page 5-17

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.

Cisco IOS XR Getting Started Guide 5-1 Chapter 5 Configuring Additional Router Features Configuring Telnet, HTTP, and XML Host Services R3.3 Beta Draft—Cisco Confidential Information

To configure the DNS and DNS server, complete the following steps:

SUMMARY STEPS

1. configure 2. domain name domain-name-of-organization 3. domain name-server ipv4-address 4. commit 5. end 6. 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 Document Title Complete descriptions of the domain services Implementing Host Services and Applications on Cisco IOS XR commands 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.

Note IPv6 is not supported on the Cisco XR 12000 Series Router.

Cisco IOS XR Getting Started Guide 5-2 Chapter 5 Configuring Additional Router Features Managing Configuration History and Rollback R3.3 Beta Draft—Cisco Confidential Information 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. configure 2. telnet ipv4 server max-servers 5 3. telnet ipv6 server max-servers 5 4. http server 5. xml agent corba 6. commit

Examples

In the following example, the host services are enabled: RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# telnet ipv4 server max-servers 5 RP/0/RP0/CPU0:router(config)# telnet ipv6 server max-servers 5 RP/0/RP0/CPU0:router(config)# http server RP/0/RP0/CPU0:router(config)# xml agent corba RP/0/RP0/CPU0:router(config)# commit

Related Documents

Related Topic Document Title Installation and activation of the Manageability and Chapter 7, “Upgrading and Managing Cisco IOS XR Software” Security Packages Descriptions of the HTTP and XML server commands Cisco IOS XR System Management Command Reference Descriptions of the Telnet commands 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.

Cisco IOS XR Getting Started Guide 5-3 Chapter 5 Configuring Additional Router Features Managing Configuration History and Rollback R3.3 Beta Draft—Cisco Confidential Information

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 the Configuration Changes for a Specific CommitID, page 5-7 • Loading Rollback Configuration Changes to the Target Configuration, page 5-7 • Deleting CommitIDs, page 5-8

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 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: RP/0/RP0/CPU0:router# show configuration commit list

SNo. Label/ID User Line Client Time Stamp ~~~~ ~~~~~~~~ ~~~~ ~~~~ ~~~~~~ ~~~~~~~~~~ 1 1000000391 user_a con0_33_1 CLI 19:29:18 UTC Wed Jan 10 2004 2 1000000390 user_a con0_33_1 CLI 19:29:16 UTC Wed Jan 10 2004 3 1000000389 user_a con0_33_1 CLI 19:29:15 UTC Wed Jan 10 2004 4 1000000388 user_a con0_33_1 CLI 19:29:12 UTC Wed Jan 10 2004 5 1000000387 user_a con0_33_1 CLI 19:26:16 UTC Wed Jan 10 2004 6 1000000386 user_a con0_32_1 CLI 19:18:38 UTC Wed Jan 10 2004 7 1000000385 user_a con0_33_1 CLI 19:14:09 UTC Wed Jan 10 2004 8 1000000384 user_a con0_33_1 CLI 19:13:58 UTC Wed Jan 10 2004 9 1000000383 user_a con0_33_1 CLI 19:13:33 UTC Wed Jan 10 2004 10 1000000382 user_a con0_33_1 CLI 19:12:50 UTC Wed Jan 10 2004 11 1000000381 user_a con0_33_1 CLI 19:12:48 UTC Wed Jan 10 2004 12 1000000380 user_a con0_33_1 CLI 19:12:46 UTC Wed Jan 10 2004 13 1000000379 user_a con0_33_1 CLI 19:12:43 UTC Wed Jan 10 2004

Cisco IOS XR Getting Started Guide 5-4 Chapter 5 Configuring Additional Router Features Managing Configuration History and Rollback R3.3 Beta Draft—Cisco Confidential Information

14 1000000378 user_a con0_33_1 CLI 19:12:14 UTC Wed Jan 10 2004 15 1000000377 user_a con0_33_1 CLI 19:10:47 UTC Wed Jan 10 2004

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 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. Label/ID User Line Client Time Stamp ~~~~ ~~~~~~~~ ~~~~ ~~~~ ~~~~~~ ~~~~~~~~~~ 1 1000000144 user_a vty0 CLI 00:16:51 UTC Thu May 11 2004 2 1000000143 user_a vty0 CLI 00:04:32 UTC Thu May 11 2004 3 1000000142 user_a 0.0.0.0 XMLAgent 21:58:36 UTC Wed May 11 2004 4 1000000141 user_a 0.0.0.0 XMLAgent 21:46:07 UTC Wed May 11 2004 5 1000000140 user_b con0_RP1_C CLI 21:43:30 UTC Wed May 11 2004 6 1000000139 user_a 0.0.0.0 XMLAgent 21:40:13 UTC Wed May 11 2004 7 1000000138 user_a 0.0.0.0 XMLAgent 21:34:48 UTC Wed May 11 2004 8 1000000137 user_b con0_RP1_C CLI 21:32:10 UTC Wed May 11 2004 9 1000000136 user_a 0.0.0.0 XMLAgent 21:30:13 UTC Wed May 11 2004 10 1000000135 user_b con0_RP1_C CLI 19:45:04 UTC Wed May 11 2004 11 1000000134 user_b con0_RP1_C CLI 19:37:26 UTC Wed May 11 2004 12 1000000133 user_b con0_RP1_C CLI 19:36:27 UTC Wed May 11 2004 13 1000000132 user_b con0_33_1 Rollback 18:34:45 UTC Wed May 11 2004 14 1000000131 user_b con0_33_1 Rollback 18:32:37 UTC Wed May 11 2004 15 1000000130 user_b con0_33_1 Rollback 18:31:09 UTC Wed May 11 2004 16 1000000129 user_b con0_33_1 CLI 18:28:12 UTC Wed May 11 2004 17 1000000128 user_b con0_33_1 CLI 18:27:22 UTC Wed May 11 2004 18 1000000127 user_b con0_33_1 CLI 18:27:19 UTC Wed May 11 2004 19 1000000126 user_b con0_33_1 Rollback 18:25:55 UTC Wed May 11 2004 20 1000000125 user_b con0_33_1 Rollback 18:24:25 UTC Wed May 11 2004

Displaying the Configuration Changes Recorded in a CommitID

To display the configuration changes made during a specific commit session (commitID), enter the show configuration commit changes command followed by a commitID number, as shown in the following example: RP/0/0/CPU0:router# show configuration commit changes 1000000071 Building configuration... hostname router2 end

Cisco IOS XR Getting Started Guide 5-5 Chapter 5 Configuring Additional Router Features Managing Configuration History and Rollback R3.3 Beta Draft—Cisco Confidential Information 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 session, enter the show configuration rollback changes to commitId command: RP/0/RP0/CPU0:router# show configuration rollback changes to 1000000373

Building configuration... interface Loopback2 no description no ipv4 address 10.0.0.1 255.0.0.0

To display the prospective rollback configuration changes from the current configuration to a specified number of previous sessions, 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.

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, enter the rollback configuration to commitId command: RP/0/RP0/CPU0:router# rollback configuration to 1000000325

Configuration successfully rolled back to ’1000000325’.

Cisco IOS XR Getting Started Guide 5-6 Chapter 5 Configuring Additional Router Features Managing Configuration History and Rollback R3.3 Beta Draft—Cisco Confidential Information 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 and commits the rolled-back 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, 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 1 sec Committing. 1 items committed in 1 sec (0)items/sec Updating. Updated Commit database in 1 sec Configuration successfully rolled back 2 commits.

Loading the Configuration Changes for a Specific CommitID

You can load the configuration changes recorded by any commitID by entering the load commit changes command in global configuration mode. The load commit changes command must be followed by a commitID number, as shown in the following example: RP/0/0/CPU0:router(config)# load commit changes 1000000066 Building configuration... Loading. 21 bytes parsed in 1 sec (20)bytes/sec

The configuration changes are added to the target configuration and are not applied until you enter the commit command.

Tip To display the target configuration, enter the show configuration command.

Loading Rollback Configuration Changes to the Target Configuration

You can load rollback configuration changes to the target configuration by entering the load rollback changes command in global configuration mode. This command is similar to the rollback configuration command. The difference between the commands is that the load rollback changes command copies the rollback changes to the target configuration and does not commit the changes.

Cisco IOS XR Getting Started Guide 5-7 Chapter 5 Configuring Additional Router Features Managing Configuration History and Rollback R3.3 Beta Draft—Cisco Confidential Information

Tip To display the rollback changes, enter the show configuration rollback changes command.

To load rollback configuration changes from the current configuration to a specific session, 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, 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, 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 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]

Cisco IOS XR Getting Started Guide 5-8 Chapter 5 Configuring Additional Router Features Saving and Loading Target Configuration Files R3.3 Beta Draft—Cisco Confidential Information Saving and Loading Target Configuration Files

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. The following sections describe how to save and load target configurations: • Saving the Target Configuration to a File, page 5-9 • Loading the Target Configuration from a File, page 5-9

Saving the Target Configuration to a File

To save the configuration changes in the target configuration to a file, enter the show configuration | file filename command. • 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. • The filename should end with the cfg file extension for easy identification. This suffix is not required, but can help locate target configuration files. Example: myconfig.cfg

Tip If you have not changed directories since login, you can display your default directory by entering the pwd command.

In the following example, a target configuration file is saved to the root of disk0: RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# show configuration | file disk0:myconfig.cfg RP/0/RP0/CPU0:router(config)# abort RP/0/RP0/CPU0:router#

Loading the Target Configuration from a File

Enter the load filename command to populate the target configuration with the contents of a previously saved configuration file. 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 default location is used. You should always save your target configuration files to this location. 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/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# load disk0:myconfig.cfg RP/0/RP0/CPU0:router(config)# show configuration Building configuration... interface POS 0/3/0/0 description My Pos Interface ipv4 address 10.10.11.20 255.0.0.0 !end

Cisco IOS XR Getting Started Guide 5-9 Chapter 5 Configuring Additional Router Features Configuring Logging and Logging Correlation R3.3 Beta Draft—Cisco Confidential Information 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.

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. 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-11 • 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 Command (Global Configuration Mode) console logging console vty terminal logging monitor external syslog server logging trap internal buffer 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 Description Level 0—Emergencies System has become unusable. Level 1—Alerts Immediate action needed to restore system stability. Level 2—Critical Critical conditions that may require attention. Level 3—Errors Error conditions that may help track problems. Level 4—Warnings Warning conditions that are not severe. Level 5—Notifications Normal but significant conditions that bear notification.

Cisco IOS XR Getting Started Guide 5-10 Chapter 5 Configuring Additional Router Features Configuring Logging and Logging Correlation R3.3 Beta Draft—Cisco Confidential Information

Table 5-2 Logging Severity Levels for System Error Messages (continued)

Level Description Level 6—Informational Informational messages that do not require action. Level 7—Debugging 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.

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. configure 2. logging {ip-address | hostname} 3. logging trap severity 4. logging console [severity] 5. logging buffered [severity | buffer-size] 6. commit 7. end 8. show logging

Cisco IOS XR Getting Started Guide 5-11 Chapter 5 Configuring Additional Router Features Configuring Logging and Logging Correlation R3.3 Beta Draft—Cisco Confidential Information

DETAILED STEPS

Command or Action Purpose Step 1 configure Enters global configuration mode.

Example: RP/0/RP0/CPU0:router# configure Step 2 logging {ip-address | hostname} Specifies a syslog server host to use for system logging.

Example: RP/0/RP0/CPU0:router(config)# logging 10.1.1.1 Step 3 logging trap severity Limits the logging of messages sent to syslog servers to only those messages at the specified level. Example: RP/0/RP0/CPU0:router(config)# logging trap debugging • See Table 5-2 for a summary of the logging severity levels. Step 4 logging console [severity] Logs messages on the console. • When a severity level is specified, only Example: messages at that severity level are logged on RP/0/RP0/CPU0:router(config)# logging console the console. emergencies • See Table 5-2 for a summary of the logging severity levels. Step 5 logging buffered [severity | buffer-size] Copies logging messages to an internal buffer. • Newer messages overwrite older messages Example: after the buffer is filled. RP/0/RP0/CPU0:router(config)# logging buffered 1000000 • Specifying a severity level causes messages at that level and numerically lower levels to be logged in an internal buffer. See Table 5-2 for a summary of the logging severity levels. • The buffer size is from 4096 to 4,294,967,295 bytes. Messages above the set limit are logged to the console. Step 6 commit Commits the target configuration to the router running configuration.

Example: RP/0/RP0/CPU0:router(config)# commit Step 7 end Ends the configuration session and returns to EXEC mode.

Example: RP/0/RP0/CPU0:router(config)# end Step 8 show logging Displays the messages that are logged in the buffer.

Example: RP/0/RP0/CPU0:router# show logging

Cisco IOS XR Getting Started Guide 5-12 Chapter 5 Configuring Additional Router Features Creating and Modifying User Accounts and User Groups R3.3 Beta Draft—Cisco Confidential Information

Examples

In the following example, basic message logging is configured: RP/0/RP0/CPU0:router# config 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 (10 messages dropped, 0 flushes, 0 overruns) Console logging: level debugging, 103 messages logged Monitor logging: level debugging, 0 messages logged Trap logging: level informational, 0 messages logged Buffer logging: level debugging, 107 messages logged

Log Buffer (16384 bytes):

RP/0/RP0/CPU0:Apr 6 21:30:59.515 : alphadisplay[103][317]: alpha_display_drain_ queue: Draining 1 message from the queue of size = 1 RP/0/RP0/CPU0:Apr 6 21:31:03.099 : ingressq[227]: %INGRESSQ_DLL-3-HALF_DEPTH_PA RT_DISCOVERED : ingressq dll: half depth memory detected, memory: DQ External QE Memory --More--

Related Documents

For more information on message logging and configuration of alarm correlation, see the following Cisco documents:

Related Topic Document Title Configuration of system logging Cisco IOS XR System Management Configuration Guide Commands used to configure logging Cisco IOS XR System Management Command Reference Configuration of alarm correlation and generating Cisco IOS XR System Management Configuration Guide complex queries Commands used to configure alarm correlation Cisco IOS XR System Management Command Reference Retrieve logging events through an XML interface Cisco IOS XR XML API Guide

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

Cisco IOS XR Getting Started Guide 5-13 Chapter 5 Configuring Additional Router Features Creating and Modifying User Accounts and User Groups R3.3 Beta Draft—Cisco Confidential Information

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

Displaying Details About User Accounts, User Groups, and Task IDs

Table 5-3 summarizes the EXEC mode commands used to display details about user accounts, user groups, and task IDs.

Table 5-3 Commands to Display Details About Users and User Groups

Command Description show aaa userdb username Displays the task IDs and privileges assigned to a specific username. To display all users on the system, enter the command without a username. show aaa usergroup usergroup-name Displays the task IDs and privileges that belong to a user group. To display all groups on the system, enter the command without a group name. show task supported Displays all task IDs for the system. Only the root-system users, root-lr users, or users associated with the WRITE:AAA task ID can configure task groups.

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.

Cisco IOS XR Getting Started Guide 5-14 Chapter 5 Configuring Additional Router Features Creating and Modifying User Accounts and User Groups R3.3 Beta Draft—Cisco Confidential Information

Figure 5-1 AAA Configuration Submodes User login

EXEC mode

Global configuration mode

(commands) AAA configuration submodes username username Username configuration submode

usergroup usergroup-name User group configuration submode

taskgroup taskgroup-name Task group configuration submode 116542

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. configure 2. username user-name 3. password {0 | 7} password or secret {0 | 5} password 4. group group-name 5. Repeat Step 4 for each user group to be associated with the user specified in Step 2. 6. end or commit

Cisco IOS XR Getting Started Guide 5-15 Chapter 5 Configuring Additional Router Features Creating and Modifying User Accounts and User Groups R3.3 Beta Draft—Cisco Confidential Information

DETAILED STEPS

Command or Action Purpose Step 1 configure Enters global configuration mode.

Example: RP/0/RP0/CPU0:router# configure Step 2 username user-name Creates a name for a new user (or identifies a current user) and enters username configuration submode.

Example: • The user-name argument can be only one word. Spaces RP/0/RP0/CPU0:router(config)# username user1 and quotation marks are not allowed. Step 3 password {0 | 7} password Specifies a password for the user named in Step 2. or • Use the secret command to create a secure login secret {0 | 5} password password for the user names specified in Step 2. • Entering 0 following the password command specifies that an unencrypted (clear-text) password follows. Example: Entering 7 following the password command specifies RP/0/RP0/CPU0:router(config-un)# password 0 pwd1 that an encrypted password follows. or • Entering 0 following the secret command specifies that RP/0/RP0/CPU0:router(config-un)# secret 5 pwd1 a secure unencrypted (clear-text) password follows. Entering 5 following the secret command specifies that a secure encrypted password follows. • Type 0 is the default for the password and secret commands. Step 4 group group-name Assigns the user named in Step 2 to a user group. • The user takes on all attributes of the user group, as Example: defined by the user group association to various task RP/0/RP0/CPU0:router(config-un)# group sysadmin groups. • Each user must be assigned to at least one user group. A user may belong to multiple user groups.

Cisco IOS XR Getting Started Guide 5-16 Chapter 5 Configuring Additional Router Features Configuration Limiting R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 5 Repeat Step 4 for each user group to be associated with — the user specified in Step 2. Step 6 end Saves configuration changes. or • When you issue the end command, the system prompts commit you to commit changes: Uncommitted changes found. Commit them? – Entering yes saves configuration changes to the Example: running configuration file, exits the configuration RP/0/RP0/CPU0:router(config-un)# end session, and returns the router to EXEC mode. or RP/0/RP0/CPU0:router(config-un)# commit – Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes. • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

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.

Cisco IOS XR Getting Started Guide 5-17 Chapter 5 Configuring Additional Router Features Configuration Limiting R3.3 Beta Draft—Cisco Confidential Information

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-18 • IS-IS Configuration Limits, page 5-19 • OSPFv2 and v3 Configuration Limits, page 5-19 • BGP Configuration Limits, page 5-22 • Routing Policy Language Line and Policy Limits, page 5-24 • Multicast Configuration Limits, page 5-25 • MPLS Configuration Limits, page 5-26

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 Configuration Command Show Current Settings Command Feature Limit Description Limit Limit (Global Configuration Mode) (EXEC Mode) Maximum static IPv4 4000 128,000 route maximum ipv4 n show running-config route maximum routes Maximum static IPv61 4000 128,000 route maximum ipv6 n show running-config route maximum routes

1. IPv6 is not supported on the Cisco XR 12000 Series Router.

Examples

In the following example, the maximum number of static IPv4 routes is changed to 5000. The new setting is then displayed with the show running-config route maximum command. RP/0/RP1/CPU0:router# configure RP/0/RP1/CPU0:router(config)# route maximum ipv4 5000 RP/0/RP1/CPU0:router(config)# commit RP/0/RP1/CPU0:Mar 30 15:50:38 : ipv4_static[214]: %IP_STATIC-6-CONFIG_MAXIMUM_CH ANGE : The maximum number of configurations for static routes has been changed f rom 4000 to 5000 RP/0/RP1/CPU0:Mar 30 15:50:39 : config[65740]: %LIBTARCFG-6-COMMIT : Configurati on committed by user 'lab'. Use 'show configuration commit changes 1000000538' to view the c hanges. RP/0/RP1/CPU0:router(config)# end RP/0/RP1/CPU0:Mar 30 15:50:46 : config[65740]: %SYS-5-CONFIG_I : Configured from console by lab

RP/0/RP1/CPU0:router# show running-config route maximum route maximum ipv4 5000

RP/0/RP1/CPU0:router#

Cisco IOS XR Getting Started Guide 5-18 Chapter 5 Configuring Additional Router Features Configuration Limiting R3.3 Beta Draft—Cisco Confidential Information 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 Absolute Configuration Command Show Current Settings Maximum Maximum (Address Family Configuration Command Feature Limit Description Limit Limit Mode) (EXEC Mode) Maximum number of 10,000 28,000 maximum-redistributed-prefixes n show isis adjacency prefixes redistributed into IS-IS Number of active parallel 832maximum-paths n show isis route paths for each route on a Cisco CRS-1 router Number of active parallel 816maximum-paths n show isis route paths for each route on a Cisco XR 12000 Series Router

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 'lab'. 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.

Cisco IOS XR Getting Started Guide 5-19 Chapter 5 Configuring Additional Router Features Configuration Limiting R3.3 Beta Draft—Cisco Confidential Information

Table 5-6 OSPFv2 and OSPFv3 Configuration Limits and Commands

Default Absolute Feature Limit Maximum Maximum Configuration Command Show Current Settings Command Description Limit Limit (Router Configuration Mode) (EXEC Mode) Maximum number of 255 1024 maximum interfaces n show ospf interfaces that can be configured for an OSPF instance Maximum routes 10,000 28,672 maximum redistributed-prefix n show ospf redistributed into Note The maximum number of OSPF redistributed prefixes is displayed only if redistribution is configured. Maximum number of 32 32 maximum paths n show running-config router ospf parallel routes (OSPFv2) Note This command shows only (maximum paths) on 16 changes to the default value. Cisco CRS-1 routers (OSPFv3) If the maximum paths command does not appear, the router is set to the default value. Maximum number of 16 16 maximum paths n show running-config router ospf parallel routes Note This command shows only (maximum paths) on a changes to the default value. Cisco XR 12000 If the maximum paths Series Router command does not appear, the router is set to the default value.

Examples

The following subsections provide the following examples: • Maximum Interfaces for Each OSPF Instance, page 5-20 • Maximum Routes Redistributed into OSPF, page 5-22 • Number of Parallel Links (max-paths), page 5-22

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

Cisco IOS XR Getting Started Guide 5-20 Chapter 5 Configuring Additional Router Features Configuration Limiting R3.3 Beta Draft—Cisco Confidential Information

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 'lab'. 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 lab

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

Cisco IOS XR Getting Started Guide 5-21 Chapter 5 Configuring Additional Router Features Configuration Limiting R3.3 Beta Draft—Cisco Confidential Information

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 'lab'. 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 lab RP/0/RP1/CPU0:router#

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 'lab'. 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 lab 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

Default Absolute Maximum Maximum Configuration Command Show Current Settings Command Feature Limit Description Limit Limit (Router Configuration Mode) (EXEC Mode) Maximum number of neighbors 1024 1024 None. This limit cannot be None (peers) changed or exceeded. IPv4 unicast maximum prefixes 524,288 4,294,967, maximum-prefix n show bgp neighbor IP_address that can be received from a 295 neighbor

Cisco IOS XR Getting Started Guide 5-22 Chapter 5 Configuring Additional Router Features Configuration Limiting R3.3 Beta Draft—Cisco Confidential Information

Table 5-7 BGP Configuration Limits and Commands (continued)

Default Absolute Maximum Maximum Configuration Command Show Current Settings Command Feature Limit Description Limit Limit (Router Configuration Mode) (EXEC Mode) IPv4 multicast maximum prefixes 131,072 4,294,967, maximum-prefix n show bgp neighbor IP_address that can be received from a 295 neighbor IPv61 unicast maximum prefixes 131,072 4,294,967, maximum-prefix n show bgp neighbor IP_address that can be received from a 295 neighbor Maximum equal-cost parallel 18maximum-paths n show running-config routes to external peers Note This command shows only changes to the default value. If the maximum paths command does not appear, the router is set to the default value.

1. IPv6 is not supported on the Cisco XR 12000 Series Router.

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 maximum number of IPv4 unicast prefixes allowed from the neighbor at 10.1.1.1 to 100,000: 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-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 'lab'. 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 lab RP/0/RP1/CPU0:router(config-bgp-nbr-af)#

Cisco IOS XR Getting Started Guide 5-23 Chapter 5 Configuring Additional Router Features Configuration Limiting R3.3 Beta Draft—Cisco Confidential Information Routing Policy Language Line and Policy Limits

Two limits for Routing Policy Language (RPL) configurations exist: 1. 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. 2. 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

Default Absolute Show Current Settings Maximum Maximum Configuration Command Command Limit Description Limit Limit (Global Configuration Mode) (EXEC Mode) Maximum number of RPL lines 65,536 131,072 rpl maximum lines n show rpl maximum lines Maximum number of RPL policies 3500 5000 rpl maximum policies n show rpl max policies

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

Cisco IOS XR Getting Started Guide 5-24 Chapter 5 Configuring Additional Router Features Configuration Limiting R3.3 Beta Draft—Cisco Confidential Information

Compiled policies size (kB) 0 RP/0/RP1/CPU0:router#

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 Absolute Show Current Settings Maximum Maximum Configuration Command Command Feature Limit Description Limit Limit (Global Configuration Mode) (EXEC Mode) Internet Group Management Protocol (IGMP) Limits Maximum number of 50,000 75,000 maximum groups n show igmp summary groups used by IGMP and accepted by a router Maximum number of 20,000 40,000 maximum groups per-interface n show igmp summary groups for each interface accepted by a router Multicast Source Discovery Protocol (MSDP) Limits Maximum MSDP Source 20,000 75,000 maximum external-sa n show msdp summary Active (SA) entries Maximum MSDP SA 20,000 75,000 maximum peer-external-sa n show msdp summary entries that can be learned from MSDP peers Protocol Independent Multicast (PIM) Limits Maximum PIM routes 100,000 200,000 maximum routes n show pim summary supported Maximum PIM egress 300,000 600,000 maximum route-interfaces n show pim summary states Maximum PIM registers 20,000 75,000 maximum register-states n show pim summary Maximum number of 500 5000 maximum group-mappings autorp n show pim summary PIM group map ranges learned from Auto-RP

Cisco IOS XR Getting Started Guide 5-25 Chapter 5 Configuring Additional Router Features Configuration Limiting R3.3 Beta Draft—Cisco Confidential Information 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

Default Absolute Show Current Settings Maximum Maximum Configuration Command Command Limit Description Limit Limit (Global Configuration Mode) (EXEC Mode) Maximum traffic engineer (TE) 2500 4096 mpls traffic-eng maximum show mpls traffic-eng tunnels head 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

Default Absolute Show Current Settings Maximum Maximum Configuration Command Command Limit Description Limit Limit (Global Configuration Mode) (EXEC Mode) IPv4 ACL 5000 9000 ipv4 access-list oor acl show ipv4 access-lists threshold n (access list and prefix list) IPv4 ACE 200,000 350,000 ipv4 access-list oor ace show ipv4 access-lists threshold n (access list and prefix list) IPv61 ACL 1000 2000 ipv6 access-list oor acl show ipv4 access-lists threshold n (access list and prefix list) IPv61 ACE 50,000 100,000 ipv6 access-list oor ace show ipv4 access-lists threshold n (access list and prefix list)

1. IPv6 is not supported on the Cisco XR 12000 Series Router.

Cisco IOS XR Getting Started Guide 5-26 R3.3 Beta Draft—Cisco Confidential Information

CHAPTER 6

CLI Tips, Techniques, and Shortcuts

Beta Draft Cisco Confidential Information

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-4 • Using the no Form of a Command, page 6-5 • Editing Command Lines that Wrap, page 6-5

Cisco IOS XR Getting Started Guide 6-1 Chapter 6 CLI Tips, Techniques, and Shortcuts CLI Tips and Shortcuts R3.3 Beta Draft—Cisco Confidential Information 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 Description partial-command? Enter a question mark (?) at the end of a partial command to list the commands that begin with those characters. RP/0/RP0/CPU0:router# co?

configure copy

Note Do not include a space between the command and question mark. ? Lists all commands available for a particular command mode. command ? Include a space before the question mark (?) to list the keywords and arguments that belong to a command. RP/0/RP0/CPU0:router# configure ?

exclusive Configure exclusively from this terminal terminal Configure from the terminal

Note For most commands, the 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 Show all the local taskgroups configured in the system userdb Show all local users with the usergroups each belong to usergroup Show all the local usergroups configured in the system

Note Include a space between the keyword and question mark.

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:

Cisco IOS XR Getting Started Guide 6-2 Chapter 6 CLI Tips, Techniques, and Shortcuts CLI Tips and Shortcuts R3.3 Beta Draft—Cisco Confidential Information

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 Control access lists log updates maximum Out of resources configration WORD Access list name - maximum 32 characters

Note The number ranges (within the angle brackets) are inclusive ranges.

Step 2 Enter the access list name list1, followed by a space and another question mark, to display the arguments that apply to the keyword and brief explanations: RP/0/0/CPU0:router(config)# ipv4 access-list list1 ?

<1-2147483646> Sequence number for this entry deny Specifies packets to reject permit Specifies packets to forward remark Comment for access list 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). 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 Wildcard bits log Log matches against this entry log-input Log matches against this entry, including input interface

RP/0/RP0/CPU0:router(config)# ipv4 access-list list1 deny 172.31.134.0

Cisco IOS XR Getting Started Guide 6-3 Chapter 6 CLI Tips, Techniques, and Shortcuts CLI Tips and Shortcuts R3.3 Beta Draft—Cisco Confidential Information

The 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

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 configure copy RP/0/RP1/CPU0:router#con RP/0/RP1/CPU0:router#configure

Tip If your keyboard does not have a Tab key, press Ctrl-I instead.

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 ?

Cisco IOS XR Getting Started Guide 6-4 Chapter 6 CLI Tips, Techniques, and Shortcuts CLI Tips and Shortcuts R3.3 Beta Draft—Cisco Confidential Information

exclusive Configure exclusively from this terminal terminal Configure from the terminal

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 router static command creates a static route, and the no router static command deletes a route when entered with the same parameters as an existing route. 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 xii 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$

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.

Cisco IOS XR Getting Started Guide 6-5 Chapter 6 CLI Tips, Techniques, and Shortcuts Displaying System Information with show Commands R3.3 Beta Draft—Cisco Confidential Information 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-6 • Halting the Display of Screen Output, page 6-7 • Redirecting Output to a File, page 6-7 • Narrowing Output from Large Configurations, page 6-8 • Filtering show Command Output, page 6-9

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 Description Command Mode show version Displays system information. EXEC mode show configuration Displays the uncommitted configuration changes made during a EXEC or any configuration session. configuration mode show running-config [command] Displays the current running configuration. EXEC or any configuration mode show tech-support Collects a large amount of system information for EXEC mode troubleshooting. You can provide this output to technical support representatives when reporting a problem. show platform (EXEC mode) Displays information about cards and modules assigned to the EXEC mode SDR. show platform (administration Displays information about all cards and modules in the router. administration EXEC mode) EXEC mode show environment [all | fans | leds | Displays hardware information for the system, including fans, EXEC mode power-supply | table | temperatures LEDs, power supply voltage and current, and temperatures. | voltages | l]

For more information on the use of these commands, see the “Related Documents” section on page xii.

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:

Cisco IOS XR Getting Started Guide 6-6 Chapter 6 CLI Tips, Techniques, and Shortcuts Displaying System Information with show Commands R3.3 Beta Draft—Cisco Confidential Information

• 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 Show AAA configuration and operational data adjacency Adjacency information aliases Display alias commands alphadisplay Shows the message being displayed on the alpha display aps SONET APS information arm IP ARM information arp ARP table as-path-access-list List AS path access lists asic-errors ASIC error information atc Attractor Cache related auto-rp Auto-RP Commands bgp BGP show commands buffer-manager Show all buffer manager memory related information bundle Show hardware related information for Bundles. calendar Display the system calendar cdp CDP information cef Cisco Express Forwarding cetftp HFR control plane ethernet TFTP server checkpoint Show checkpoint services cinetd cinetd daemon clns Display CLNS related information clock Display the system clock commit Show commit information --More--

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

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

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:

Cisco IOS XR Getting Started Guide 6-7 Chapter 6 CLI Tips, Techniques, and Shortcuts Displaying System Information with show Commands R3.3 Beta Draft—Cisco Confidential Information

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, enter an additional argument at the end of the show running-config command. You can also use a wildcard to display all instances for a feature.

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.

Cisco IOS XR Getting Started Guide 6-8 Chapter 6 CLI Tips, Techniques, and Shortcuts Displaying System Information with show Commands R3.3 Beta Draft—Cisco Confidential 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 ! 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, or exclude) and a regular expression. Table 6-3 shows the filtering options for the show command.

Ta b l e 6 - 3 s h o w C o m m a n d Filter Options

Command Description show command | begin regular-expression Begins unfiltered output of the show command with the first line that contains the regular expression. show command | exclude regular-expression Displays output lines that do not contain the regular expression. show command | include regular-expression Displays output lines that contain the regular expression. show command | file disk0:myconfigfile Writes the output lines that contain the regular expression to the specified file on the specified device.

Cisco IOS XR Getting Started Guide 6-9 Chapter 6 CLI Tips, Techniques, and Shortcuts Displaying System Information with show Commands R3.3 Beta Draft—Cisco Confidential Information

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 is administratively down 0 drops for unrecognized upper-level protocol POS0/2/0/1 is administratively down, line protocol is administratively down 0 drops for unrecognized upper-level protocol POS0/2/0/2 is administratively down, line protocol is administratively down 0 drops for unrecognized upper-level protocol POS0/2/0/3 is administratively down, line protocol is administratively down 0 drops for unrecognized upper-level protocol MgmtEthernet0/RP0/CPU0/0 is administratively down, line protocol is administratively down MgmtEthernet0/RP0/CPU0/0 is administratively down, line protocol is administratively down 0 drops for unrecognized upper-level protocol

Note Filtering is available for submodes, complete commands, and anywhere that appears in the “?” output.

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

Cisco IOS XR Getting Started Guide 6-10 Chapter 6 CLI Tips, Techniques, and Shortcuts Wildcards, Templates, and Aliases R3.3 Beta Draft—Cisco Confidential Information

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-12 • 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.

Table 6-4 Examples of Wildcard Usage

Wildcard Syntax Description * Specifies all interfaces pos* Specifies all POS interfaces in the system pos0/1/* Specifies all POS interfaces in rack 0, slot 1 pos0/3/4.* 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 255.255.255.0 pos crc 32 ! keepalive disable interface POS0/1/0/1 ipv4 address 10.2.3.5 255.255.255.0 pos crc 32 !

Cisco IOS XR Getting Started Guide 6-11 Chapter 6 CLI Tips, Techniques, and Shortcuts Wildcards, Templates, and Aliases R3.3 Beta Draft—Cisco Confidential Information

keepalive disable interface POS0/1/0/2 ipv4 address 10.2.3.6 255.255.255.0 pos crc 32 ! keepalive disable interface POS0/1/0/3 ipv4 address 10.2.3.7 255.255.255.0 pos crc 32 ! keepalive disable

--More--

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. configure 2. template template-name [parameter] [config-commands] 3. Enter the template definitions. 4. end-template 5. show running-config template template-name

Cisco IOS XR Getting Started Guide 6-12 Chapter 6 CLI Tips, Techniques, and Shortcuts Wildcards, Templates, and Aliases R3.3 Beta Draft—Cisco Confidential Information

6. Apply the template. a. configure b. apply-template template-name [parameter] c. show running-config

DETAILED STEPS

Command or Action Purpose Step 1 configure Enters global configuration mode.

Example: Router# configure Step 2 template template-name [parameter] Enters template configuration mode and creates a template. [config-commands] • template-name: Unique name for the template to be applied to the running configuration. Example: • parameter: (Optional) Actual values of the variables RP/0/RP0/CPU0:router(config)# template tmplt_1 specified in the template definition. Up to five parameters can be specified within parentheses. 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. Type the template command in global configuration mode. Step 3 Enter the template definitions. —

Example: RP/0/RP0/CPU0:router(config-TPL)# interface pos0/2/0/4 RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.0.0.1 RP/0/RP0/CPU0:router(config-if)# exit Step 4 end-template Ends the template definition session and exits template configuration mode.

Example: • When you end the template session, you are returned to RP/0/RP0/CPU0:router(config-TPL)# end-template global configuration mode.

Cisco IOS XR Getting Started Guide 6-13 Chapter 6 CLI Tips, Techniques, and Shortcuts Wildcards, Templates, and Aliases R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 5 show running-config template template-name Displays the details of the template.

Example: RP/0/RP0/CPU0:router# show running-config template tmplt_1 Step 6 Apply the template: Applies a defined template and its parameters to the running configuration of the system. a. configure • Type this command in global configuration mode. b. apply-template template-name [parameter] • Only one template can by applied at a time. c. show running-config • If the same template is applied multiple times, the most recent application overwrites the previous ones. Example: RP/0/RP0/CPU0:router# configure • Provide the exact number of parameters for the RP/0/RP0/CPU0:router(config)# apply-template template. tmplt_1 RP/0/RP0/CPU0:router(config)# commit • Templates are applied as a “best effort” operation; only RP/0/RP0/CPU0:router(config)# show valid changes are committed. If any command in the running-config template fails, that command is discarded. ... template tmplt_1 • To remove the template, use the no form of this interface POS0/2/0/4 command. ipv4 address 10.0.0.1 255.255.255.0 ! end-template .. interface POS0/2/0/4 ipv4 address 10.0.0.1 255.255.255.0 !

RP/0/RP0/CPU0:router(config)# exit

Applying Configuration Templates

To apply a template, enter the apply-template template-name [parameter] command in global configuration mode. The following command applies the template tmplt_1: RP/0/RP0/CPU0:router(config)# apply-template tmplt_1

The following apply command applies the template bar with two arguments: RP/0/RP0/CPU0:router(config)# apply-template bar (mibtwister %wd_default_mem.tcl)

Cisco IOS XR Getting Started Guide 6-14 Chapter 6 CLI Tips, Techniques, and Shortcuts Wildcards, Templates, and Aliases R3.3 Beta Draft—Cisco Confidential Information

To display the results of the previously applied templates, enter the show running-config command: RP/0/RP0/CPU0:router# show running-config

hostname mibtwister #new hostname set by apply bar template bar (abc cde ) hostname $abc fault manager policy %wd_default_cpu.tcl system fault manager policy $cde system logging trap logging trap informational logging console debugging logging history size 1 logging history warnings logging monitor debugging logging buffered 16384 end-template template tmplt_1 interface preconfigure pos0/1/0/2 ipv4 address 10.2.3.4 255.255.255.0 ! end-template . . . fault manager policy %wd_default_cpu.tcl system fault manager policy %wd_default_mem.tcl system # substituted logging trap logging trap informational logging console debugging logging history size 1 logging history warnings logging monitor debugging logging buffered 16384 . . . interface preconfigure pos0/1/0/2 # set by apply tmplt_1 ipv4 address 10.2.3.4 255.255.255.0 ! . . .

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(config)# template tmplt_1 RP/0/RP0/CPU0:router(config-TPL)# interface pos0/2/0/4 RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.2.3.4 255.255.255.0 RP/0/RP0/CPU0:router(config-if)# exit RP/0/RP0/CPU0:router(config-TPL)# end-template RP/0/RP0/CPU0:router(config)# exit RP/0/RP0/CPU0:router# show running-config template tmplt_1 interface pos0/2/0/4 ipv4 address 10.2.3.4 255.255.255.0 ! end-template

interface pos0/2/0/4 ipv4 address 10.2.3.4 255.255.0.0 !

Cisco IOS XR Getting Started Guide 6-15 Chapter 6 CLI Tips, Techniques, and Shortcuts Wildcards, Templates, and Aliases R3.3 Beta Draft—Cisco Confidential Information

In the following example, a template named bar with two parameters is defined: RP/0/RP0/CPU0:router(config)# template bar (abc cde) RP/0/RP0/CPU0:router(config-TPL)# hostname $abc RP/0/RP0/CPU0:router(config-TPL)# fault manager policy %wd_default_cpu.tcl system RP/0/RP0/CPU0:router(config-TPL)# fault manager policy $cde system RP/0/RP0/CPU0:router(config-TPL)# logging trap RP/0/RP0/CPU0:router(config-TPL)# logging trap informational RP/0/RP0/CPU0:router(config-TPL)# logging console debugging RP/0/RP0/CPU0:router(config-TPL)# logging history size 1 RP/0/RP0/CPU0:router(config-TPL)# logging history warnings RP/0/RP0/CPU0:router(config-TPL)# logging monitor debugging RP/0/RP0/CPU0:router(config-TPL)# logging buffered 16384 RP/0/RP0/CPU0:router(config-TPL)# end-template RP/0/RP0/CPU0:router(config)# exit RP/0/RP0/CPU0:router#show running-config template bar

template bar (abc cde) hostname $abc fault manager policy %wd_default_cpu.tcl system fault manager policy $cde system logging trap logging trap informational logging console debugging logging history size 1 logging history warnings logging monitor debugging logging buffered 16384 end-template

Note Configuration commands in the template body can have variables beginning with the dollar sign ($). When the template is applied, variables beginning with “$” can be substituted by real arguments.

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 following command in global configuration mode: alias alias-name command-syntax Table 6-5 defines the alias command syntax. Table 6-5 alias Command Syntax

Syntax Specifies that the Alias Is Created for alias-name Name of the command alias. An alias name can be a single word or multiple words joined by a dash (–). command-syntax Original command syntax. Valid abbreviations of the original command syntax can be entered for the command-syntax argument.

To delete all aliases in a command mode or a specific alias, enter the no form of the alias command.

Cisco IOS XR Getting Started Guide 6-16 Chapter 6 CLI Tips, Techniques, and Shortcuts Command History R3.3 Beta Draft—Cisco Confidential Information

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.

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.

Cisco IOS XR Getting Started Guide 6-17 Chapter 6 CLI Tips, Techniques, and Shortcuts Key Combinations R3.3 Beta Draft—Cisco Confidential Information

Table 6-6 Command History

Command or Key Combination Purpose Ctrl-P or the up arrow key Recalls commands in the history buffer, beginning with the most recent command. Repeat the key sequence to recall successively older commands. Ctrl-N or the down arrow key 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.

Note Use the terminal history command to set the number of command line entries the system holds for recall during a terminal session.

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 Recalls the Ctrl-Y Most recent entry in the buffer (press the keys simultaneously). Esc, Y 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

Cisco IOS XR Getting Started Guide 6-18 Chapter 6 CLI Tips, Techniques, and Shortcuts Key Combinations R3.3 Beta Draft—Cisco Confidential Information 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: • 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.

Table 6-8 Key Combinations Used to Move the Cursor

Keystrokes Function Moves the Cursor Left arrow or Ctrl-B Back character 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. Right arrow or Ctrl-F Forward character One character to the right. Esc, B Back word Back one word. Esc, F Forward word Forward one word. Ctrl-A Beginning of line To the beginning of the line. Ctrl-E End of line To the end of the command 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 Purpose Esc, C Capitalizes the letter at the cursor. Esc, L Changes the word at the cursor to lowercase. Esc, U Capitalizes letters from the cursor to the end of the word.

Cisco IOS XR Getting Started Guide 6-19 Chapter 6 CLI Tips, Techniques, and Shortcuts Key Combinations R3.3 Beta Draft—Cisco Confidential Information 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 Deletes Delete or Backspace The character to the left of the cursor. Ctrl-D The character at the cursor. Ctrl-K All characters from the cursor to the end of the command line. Ctrl-U or Ctrl-X All characters from the cursor to the beginning of the command line. Ctrl-W The word to the left of the cursor. Esc, D From the cursor to the end of the word.

Transposing Mistyped Characters

To transpose mistyped characters, use the Ctrl-T key combination.

Cisco IOS XR Getting Started Guide 6-20 R3.3 Beta Draft—Cisco Confidential Information

CHAPTER 7

Upgrading and Managing Cisco IOS XR Software

Beta Draft Cisco Confidential Information

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

This chapter contains the following sections: • Overview of Cisco IOS XR Software Packages, page 7-1 • Information About Package Management, page 7-9 • Package Management Procedures, page 7-19 • Configuration Examples for Managing Packages, page 7-40

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 line card support. Bundles are groups of packages that can be downloaded as a set. The Cisco IOS XR Unicast Routing Core Bundle provides six packages for use on every router. The following subsections describe the following packages and bundles: • Cisco IOS XR Software Bundles, page 7-2 • OS Package, page 7-2 • Base Package, page 7-3 • Admin Package, page 7-4 • Forwarding Package, page 7-4 • Routing Package, page 7-5 • Line Card Package, page 7-6 • Manageability Package, page 7-6 • Security Package, page 7-7

Cisco IOS XR Getting Started Guide 7-1 Chapter 7 Upgrading and Managing Cisco IOS XR Software Overview of Cisco IOS XR Software Packages R3.3 Beta Draft—Cisco Confidential Information

• MPLS Package, page 7-7 • Multicast Package, page 7-8 • Diagnostics Package, page 7-9 • Session Border Controller Package, page 7-9

Cisco IOS XR Software Bundles

The Cisco IOS XR Software packages are provided in the feature bundles listed in Table 7-1. These packages are described in the sections that follow. Table 7-1 Cisco IOS XR Software Bundles

Package

Bundle OS Base Admin Forwarding Routing Line Card Management Multicast MPLS Security Diagnostics Session Border Controller Cisco IOS XR Unicast Routing Core XXXXXX Bundle Cisco IOS XR IP/MPLS Core Software XXXXXXXXX XX (Releases 3.2.0 and later) Cisco IOS XR IP/MPLS Core Software XXXXXXXXXXXX with Encryption (Releases 3.2.0 and later)

OS Package

The OS package provides the basic operating system and the following features: • 1 GB flash • DOSFAT 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

Cisco IOS XR Getting Started Guide 7-2 Chapter 7 Upgrading and Managing Cisco IOS XR Software Overview of Cisco IOS XR Software Packages R3.3 Beta Draft—Cisco Confidential Information

Base Package

The Base package provides the basic infrastructure required to boot the router to the CLI prompt and add 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 • 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 • Netio—DLL Restart • Packet manager • Password management • PFI • QSM • RADIUS support • Rate limiting router addressed and originated packets—hardcoded • Role-based authorization • Scoped restarts • 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) • SysDB—Hitless downgrade or upgrade • Syslog over IPv4 transport • Syslog over IPv6 transport • Syslog support • TACACS+ support • Version manager (including data translator)

Cisco IOS XR Getting Started Guide 7-3 Chapter 7 Upgrading and Managing Cisco IOS XR Software Overview of Cisco IOS XR Software Packages R3.3 Beta Draft—Cisco Confidential Information

Admin Package

The Admin package provides the basic software required to manage the router. The Admin package provides the following features: • Admin plane—secure 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 • 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

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)

Cisco IOS XR Getting Started Guide 7-4 Chapter 7 Upgrading and Managing Cisco IOS XR Software Overview of Cisco IOS XR Software Packages R3.3 Beta Draft—Cisco Confidential Information

• 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 • TFTP support • Trace route support • Weighted Random Early Detection (WRED)—based on bytes or packets or time

Routing Package

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 support—intra-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

Cisco IOS XR Getting Started Guide 7-5 Chapter 7 Upgrading and Managing Cisco IOS XR Software Overview of Cisco IOS XR Software Packages R3.3 Beta Draft—Cisco Confidential Information

• RIB support redistribution • Route dampening • Route redistribution • Show advertised routes

Line Card Package

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

The Manageability package supports the following features:

Cisco IOS XR Getting Started Guide 7-6 Chapter 7 Upgrading and Managing Cisco IOS XR Software Overview of Cisco IOS XR Software Packages R3.3 Beta Draft—Cisco Confidential Information

• Alarms management—configuration, operation, and correlation support • Configuration editor and manager • Accounting and statistics management • Performance management • Fault manager • Network Time Protocol (NTP) configuration and operation • Control point and network management—generic requirements • Terminal services enhancements • Enhanced command-line interface (CLI) • Extensible markup language (XML) interface and schemas • Craft Works Interface (CWI) • Common Object Request Broker Architecture (CORBA) support • Simple Network Management Protocol (SNMP) v1, v2c, and v3 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

Security Package

The Security package supports the following features: • Client and server support • Secure socket layer (SSL—SSL V2, SSL V3, 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

The Multiprotocol Label Switching (MPLS) package supports the following features: • MPLS forwarding and load balancing

Cisco IOS XR Getting Started Guide 7-7 Chapter 7 Upgrading and Managing Cisco IOS XR Software Overview of Cisco IOS XR Software Packages R3.3 Beta Draft—Cisco Confidential Information

• 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 HA—nonstop forwarding (NSF) and hitless software upgrade – RSVP refresh reduction • UNI – UNI-C AAA CLI – UNI-C core – UNI-C HA—NSF 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 • LMP—static configuration • Fast reroute (FRR) with link, node, and bandwidth protection • XML schema support, configuration, and operation

Multicast Package

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

Cisco IOS XR Getting Started Guide 7-8 Chapter 7 Upgrading and Managing Cisco IOS XR Software Information About Package Management R3.3 Beta Draft—Cisco Confidential Information

• 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. 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 control and manage 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.

Information About Package Management

This section describes the following concepts for managing Cisco IOS XR software packages: • Overview of Package Management, page 7-10 • Managing Software Packages in a Multishelf System, page 7-11 • Upgrading Packages, page 7-12 • Downgrading Packages, page 7-13 • Standard PIE Filenames and Version Numbers, page 7-13 • Software Maintenance Update PIE Filenames and Version Numbers, page 7-15

Cisco IOS XR Getting Started Guide 7-9 Chapter 7 Upgrading and Managing Cisco IOS XR Software Information About Package Management R3.3 Beta Draft—Cisco Confidential Information

• Impact of Package Version Changes, page 7-18 • Impact of Package Activation and Deactivation, page 7-18 • Controlling install Command Operation, page 7-29 • Activation and Deactivation Prerequisites, page 7-19

Overview of Package Management

Package management processes include the following: • Viewing which packages are available on the router • Adding or removing optional packages • Upgrading or downgrading an package or package set that has been added to the router • Removing packages that are no longer in use • Rolling back the selected package set to a previous package set The general procedure for adding optional packages, upgrading a package or package set, or downgrading packages on the router is as follows: 1. Copy the package file or files to the router or a file server to which the router has access. 2. Add the package or packages on the router. 3. Activate the package or packages on the router. 4. Commit the current set of packages. 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

Active Committed Flash disk1: Inactive Software Software Software Configuration Configuration Install Activate Flash disk0: Install Add Install Commit Install Deactivate

TFTP, FTP, or

RCP file server 116634

Packages are stored in package installation envelope (PIE) files, which 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). 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). 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.

Cisco IOS XR Getting Started Guide 7-10 Chapter 7 Upgrading and Managing Cisco IOS XR Software Information About Package Management R3.3 Beta Draft—Cisco Confidential Information

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

Cisco IOS XR Getting Started Guide 7-11 Chapter 7 Upgrading and Managing Cisco IOS XR Software Information About Package Management R3.3 Beta Draft—Cisco Confidential Information

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 individual chassis.

Figure 7-2 DSC in a CRS-1/M-F1 Multishelf System

Gigabit Ethernet Control Bus

Fabric Cards Fabric Catalyst 6509 Switches

DSC SC SM4 SM7 SM4 SM7 OIM23 OIM22 OIM21 OIM16 OIM15 OIM14 OIM13 OIM12 OIM23 OIM22 OIM21 OIM16 OIM15 OIM14 OIM13 OIM12 RP (SC) RP (SC) RP (SC) RP (SC) OIM-LED 1 OIM-LED 1 Fabric Cards Fabric

Line Card Chassis Fabric Card Chassis Line Card Chassis

Rack 1 Rack F0 Rack 0 138118

Upgrading Packages

To upgrade a package that is currently active on the router, add and activate a newer version of the same package for one or more cards for which an older version is already active (see Figure 7-3). The older version of the same 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 delete an inactive package from disk0, enter the install remove command. See the “Removing Inactive Packages from the Router” section on page 7-39 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.

Cisco IOS XR Getting Started Guide 7-12 Chapter 7 Upgrading and Managing Cisco IOS XR Software Information About Package Management R3.3 Beta Draft—Cisco Confidential Information

Figure 7-3 Example of a Maintenance Release Package Upgrade

MPLS 2.0.0 MPLS 2.0.0

Routing 2.0.0 Routing 2.0.1

Forwarding 2.0.0 Forwarding 2.0.0

Base 2.0.0 Base 2.0.0 116630

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 delete an inactive package from the disk, enter the install remove command. See the “Removing Inactive Packages from the Router” section on page 7-39 for more information.

Standard PIE Filenames and Version Numbers

Standard 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 composite-package filename are part of the filename, as shown in the following list.

Cisco IOS XR Getting Started Guide 7-13 Chapter 7 Upgrading and Managing Cisco IOS XR Software Information About Package Management R3.3 Beta Draft—Cisco Confidential Information

The format for a composite-package filename on Cisco CRS-1 routers is: comp-platform-composite_name.pie-major.minor.maintenance The format for a composite-package filename on Cisco XR 12000 Series Routers is: platform-composite_name.pie-major.minor.maintenance The “comp” prefix indicates that the file is a composite of multiple packages. The format for single-package PIEs on Cisco CRS-1 routers is: platform-package_type.-p.pie-major.minor.maintenance The format for single-package PIEs on Cisco XR 12000 Series Routers is: platform-package_type.pie-major.minor.maintenance The filename components for all packages are described in Table 7-2.

Table 7-2 Composite- and Single-Package Filename Components

Component Description platform 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.” composite_name Identifies a specific composite package. • 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 “Cisco IOS XR Software Bundles” section on page 7-2). package_type 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

Cisco IOS XR Getting Started Guide 7-14 Chapter 7 Upgrading and Managing Cisco IOS XR Software Information About Package Management R3.3 Beta Draft—Cisco Confidential Information

Table 7-2 Composite- and Single-Package Filename Components (continued)

Component Description major Identifies the major release of this 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. minor Identifies the minor release of this package. • A minor release contains one or more of the following: – New features – Bug fixes • 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. maintenance Identifies the maintenance release of this package. • 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.

Software Maintenance Update PIE Filenames and Version Numbers

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.

Cisco IOS XR Getting Started Guide 7-15 Chapter 7 Upgrading and Managing Cisco IOS XR Software Information About Package Management R3.3 Beta Draft—Cisco Confidential Information

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 xv. The format for a single-package SMU filename is: platform-package_type-major.minor.maintenance.ddts.pie The format for a composite-package SMU filename is: comp-platform-composite_name.ddts.pie The “comp” prefix indicates that the file is a composite file containing multiple updates. The other filename components are described in Table 7-3.

Table 7-3 SMU Single- and Composite-Package Filename Components

Component Description platform Identifies the platform for which the software package is designed. • For packages designed for CRS-1 routers, the platform designation is either “hfr” or “CRS-1.” • For packages designed for Cisco XR 12000 Series Routers, the platform designation is “c12k.” composite_name Identifies a specific composite package. • The composite name is a name or number that is unique to the SMU. ddts Identifies a Distributed Defect Tracking System (DDTS) number that describes the problem this SMU addresses. Note DDTS is the method used to track known bugs and the resolutions or workarounds for those issues. package_type 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

Cisco IOS XR Getting Started Guide 7-16 Chapter 7 Upgrading and Managing Cisco IOS XR Software Information About Package Management R3.3 Beta Draft—Cisco Confidential Information

Table 7-3 SMU Single- and Composite-Package Filename Components (continued)

In the following example, the SMU for the base package version 2.0.0 fixes DDTS CSCec98765:

SMU SMU Filename base-2.0.0.CSCec98765-1.0.0 hfr-base-2.0.0.CSCec98765.pie

In the following example, the SMU comp-001.CSCec98766 provides changes to multiple packages, as specified in DDTS CSCec98766:

SMU SMU Filename comp-001.CSCec98766 comp-hfr-001.CSCec98766.pie

Cisco IOS XR Getting Started Guide 7-17 Chapter 7 Upgrading and Managing Cisco IOS XR Software Information About Package Management R3.3 Beta Draft—Cisco Confidential Information

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

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 “Standard PIE Filenames and Version Numbers” section on page 7-13 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-26 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 system. The router need not be restarted or reloaded. • When a package is deactivated, the commands associated with the features being deactivated are removed from the system and are no longer available to the user. • During a software package deactivation, upgrade, or downgrade, any incompatible configurations are removed from the running configuration 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. • The cards may reload. • No impact: no processes in the card are affected.

Cisco IOS XR Getting Started Guide 7-18 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

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.

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. • Initial activation of any package must always be performed for the default set of supported card types. • 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. • The package must be compatible with the card for which it is being activated. • Some packages require the activation or deactivation of other packages. • The package being activated must be compatible with the current active software set. While a software package is being activated, other requests are not allowed to execute on the system. Each install CLI request is assigned a requestID, which can be used later to review the events. Package activation is complete 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.

Package Management Procedures

Review the concepts in the “Information About Package Management” section on page 7-9 before performing the following tasks. The following sections describe package management tasks: • Displaying Cisco IOS XR Software Information, page 7-20 • Obtaining and Placing Cisco IOS XR Software, page 7-26 • Controlling install Command Operation, page 7-29 • Upgrading and Adding Packages from a Flash Disk, page 7-30 • Upgrading and Adding Packages from a Network File Server, page 7-34 • Rolling Back to the Last Committed Package Set, page 7-37 • Rolling Back to a Noncommitted Rollback Point, page 7-38 • Committing the Active Package Set, page 7-39

Cisco IOS XR Getting Started Guide 7-19 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

• Deactivating a Package, page 7-39 • Removing Inactive Packages from the Router, page 7-39

Displaying Cisco IOS XR Software Information

The Cisco IOS XR software can exist in several states on the router. Software that has not been added to a local storage device with the install add command is stored in PIE files. Some software packages may have been added but not activated, and others can be activated but not committed. To view the status of the Cisco IOS XR software packages on your router, use the following procedures: • Displaying the Available PIE Files, page 7-20 • Displaying the Packages that are Ready for Activation, page 7-20 • Displaying the Active Packages for All Cards, page 7-21 • Displaying the Active Packages for a Single Card, page 7-22 • Displaying the Committed Package Versions, page 7-23 • Displaying Rollback Points, page 7-24 • Displaying install Command Progress, page 7-25 • Displaying the Installation Log, page 7-25

Displaying the Available PIE Files

PIE files are often stored in the root directory of flash disk1. To display the files that are available to be unpaked and added to the boot device (using the install add command), use the dir command and specify the root of flash disk1. For example: RP/0/RP0/CPU0:Router# dir disk1:

Displaying the Packages that are Ready for Activation

Inactive packages are packages that have been added, but have either not been activated or have been deactivated. An inactive package can be activated or removed. To display the list of inactive packages, enter the show install inactive summary command as follows: RP/0/RP0/CPU0:router# show install inactive summary

Default Profile: Inactive Packages: disk0:hfr-mini-3.3.0

Note This command displays only packages that are inactive on all nodes in the system or SDR.

Cisco IOS XR Getting Started Guide 7-20 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

Displaying the Active Packages for All Cards

In the following example, the active packages for all cards in a Cisco XR 12000 Series Router are shown: RP/0/RP0/CPU0:router(admin)#show install active

Node 0/1/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Active Packages: disk0:hfr-diags-3.3.84 disk0:comp-hfr-full-3.3.84

Node 0/1/CPU0 [LC] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/lc/mbihfr-lc.vm Active Packages: disk0:hfr-diags-3.3.84 disk0:comp-hfr-full-3.3.84

Node 0/RP0/CPU0 [RP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/mbihfr-rp.vm Active Packages: disk0:hfr-diags-3.3.84 disk0:hfr-mgbl-3.3.84 disk0:hfr-k9sec-3.3.84 disk0:comp-hfr-full-3.3.84

Node 0/RP1/CPU0 [RP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/mbihfr-rp.vm Active Packages: disk0:hfr-diags-3.3.84 disk0:hfr-mgbl-3.3.84 disk0:hfr-k9sec-3.3.84 disk0:comp-hfr-full-3.3.84

Node 0/SM0/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Active Packages: disk0:hfr-diags-3.3.84 disk0:comp-hfr-full-3.3.84

Node 0/SM1/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Active Packages: disk0:hfr-diags-3.3.84 disk0:comp-hfr-full-3.3.84

Node 0/SM2/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Active Packages: disk0:hfr-diags-3.3.84 disk0:comp-hfr-full-3.3.84

Node 0/SM3/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Active Packages: disk0:hfr-diags-3.3.84 disk0:comp-hfr-full-3.3.84

RP/0/RP0/CPU0:router#

Cisco IOS XR Getting Started Guide 7-21 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

In the preceding example, the composite package comp-hfr-full-3.3.84 is active. In the next example, the show install active detail command also displays the active packages within each composite package: RP/0/RP0/CPU0:router#show install active detail Node 0/1/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Active Packages: disk0:hfr-diags-3.3.84 disk0:comp-hfr-full-3.3.84 disk0:hfr-admin-3.3.84 disk0:hfr-base-3.3.84 disk0:hfr-os-mbi-3.3.84

Node 0/1/CPU0 [LC] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/lc/mbihfr-lc.vm Active Packages: disk0:hfr-diags-3.3.84 disk0:comp-hfr-full-3.3.84 disk0:hfr-mcast-3.3.84 disk0:hfr-mpls-3.3.84 disk0:hfr-lc-3.3.84 disk0:hfr-fwdg-3.3.84 disk0:hfr-admin-3.3.84 disk0:hfr-base-3.3.84 disk0:hfr-os-mbi-3.3.84

Node 0/RP0/CPU0 [RP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/mbihfr-rp.vm Active Packages: disk0:hfr-diags-3.3.84 disk0:hfr-mgbl-3.3.84 disk0:hfr-k9sec-3.3.84 disk0:comp-hfr-full-3.3.84 disk0:hfr-mcast-3.3.84 disk0:hfr-mpls-3.3.84 disk0:hfr-rout-3.3.84 disk0:hfr-lc-3.3.84 disk0:hfr-fwdg-3.3.84 disk0:hfr-admin-3.3.84 disk0:hfr-base-3.3.84 disk0:hfr-os-mbi-3.3.84

Node 0/RP1/CPU0 [RP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/mbihfr-rp.vm Active Packages: disk0:hfr-diags-3.3.84 disk0:hfr-mgbl-3.3.84 disk0:hfr-k9sec-3.3.84 disk0:comp-hfr-full-3.3.84 disk0:hfr-mcast-3.3.84 --More--

Displaying the Active Packages for a Single Card

To display the active packages for a single card, enter the show install active command with the location option. The following example shows the active packages on an RP in a Cisco CRS-1 router: RP/0/RP0/CPU0:router#show install active location 0/rp0/cpu0

Node 0/RP0/CPU0 [RP] [SDR: Owner]

Cisco IOS XR Getting Started Guide 7-22 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

Boot Image: /disk0/hfr-os-mbi-3.3.84/mbihfr-rp.vm Active Packages: disk0:hfr-diags-3.3.84 disk0:hfr-mgbl-3.3.84 disk0:hfr-k9sec-3.3.84 disk0:comp-hfr-full-3.3.84

Displaying the Committed Package Versions

Committed packages are the packages that are persistent across router reloads. If you add and activate a package, it remains active until the next SDR 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. To view which packages are committed, enter the show install committed command using the following syntax: show install committed [SDR] [detail] [summary] [location nodeID]

Note For more information on the command options, see Cisco IOS XR System Management Command Reference, Release 3.3.

In the following example, the committed packages are shown: RP/0/RP0/CPU0:router# show install committed

Node 0/1/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Committed Packages: disk0:comp-hfr-full-3.3.84

Node 0/1/CPU0 [LC] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/lc/mbihfr-lc.vm Committed Packages: disk0:comp-hfr-full-3.3.84

Node 0/RP0/CPU0 [RP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/mbihfr-rp.vm Committed Packages: disk0:comp-hfr-full-3.3.84

Node 0/RP1/CPU0 [RP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/mbihfr-rp.vm Committed Packages: disk0:comp-hfr-full-3.3.84

Node 0/SM0/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Committed Packages: disk0:comp-hfr-full-3.3.84

Node 0/SM1/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Committed Packages: disk0:comp-hfr-full-3.3.84

Node 0/SM2/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Committed Packages:

Cisco IOS XR Getting Started Guide 7-23 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

disk0:comp-hfr-full-3.3.84

Node 0/SM3/SP [SP] [SDR: Owner] Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vm Committed Packages: disk0:comp-hfr-full-3.3.84

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.

Displaying Rollback Points

A rollback point is created every time a software package set is committed. Beginning with Release 3.0, 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 admin 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. 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, Release 3.3.

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

Node 0/RP0/CPU0 [RP] [SDR: Owner]

Cisco IOS XR Getting Started Guide 7-24 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

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

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

Displaying install Command Progress

Only one install command can be active at a time. After the install command starts, the router may display the command prompt, which allows you to enter other commands. If additional command displays or messages obscure the install command progress, you can display the install command progress by entering the show install request command, as shown in the following example: RP/0/RP0/CPU0:router(admin)#show install request

Install operation 16 'install activate disk0:hfr-mpls-3.3.80' started by user 'cisco' at 04:48:13 UTC Mon Nov 14 2005.

Displaying the Installation Log

The installation log records all package management events started with the install command. To display the installation log events, enter the show install log command using the following syntax: show install log [eventNumber] [detail] [verbose]

Cisco IOS XR Getting Started Guide 7-25 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

Note For more information on the command options, see Cisco IOS XR System Management Command Reference, Release 3.3.

The following example shows how to display information on all saved log events: RP/0/RP0/CPU0:router(admin)# show install log

Install operation 1 started by user 'cisco' at 21:10:19 UTC Thu Nov 03 2005. install commit Install operation 1 completed successfully at 21:10:21 UTC Thu Nov 03 2005.

Install operation 2 started by user 'cisco' at 21:18:22 UTC Thu Nov 03 2005. install deactivate disk0:hfr-mpls-3.3.0 globally Install operation 2 completed successfully at 21:19:20 UTC Thu Nov 03 2005.

Install operation 3 started by user 'cisco' at 21:19:38 UTC Thu Nov 03 2005. install commit Install operation 3 completed successfully at 21:19:39 UTC Thu Nov 03 2005.

Install operation 4 started by user 'cisco' at 21:22:06 UTC Thu Nov 03 2005. install activate disk0:hfr-mpls-3.3.0 globally Install operation 4 completed successfully at 21:22:47 UTC Thu Nov 03 2005.

Install operation 5 started by user 'cisco' at 21:23:03 UTC Thu Nov 03 2005. install commit Install operation 5 completed successfully at 21:23:06 UTC Thu Nov 03 2005.

5 entries shown (max log size 50 entries)

The next example shows how to display information on a specified log event: RP/0/RP0/CPU0:router(admin)# show install log 1

Install operation 1 started by user 'cisco' at 21:10:19 UTC Thu Nov 03 2005. install commit Install operation 1 completed successfully at 21:10:21 UTC Thu Nov 03 2005.

Obtaining and Placing Cisco IOS XR Software

Your router may already contain the software you need on flash disk0 or flash disk1. To view the Cisco IOS XR software available on your router, see the “Displaying Cisco IOS XR Software Information” section on page 7-20. One way to obtain software and place it on the router is to request the software from Cisco on a flash disk that you can insert into the removable flash disk slot, 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 flash disk0.

Note Flash disk0 is required and used by the system, and flash disk0 should never be manipulated by the user. In addition, the hard disk is used to store system files, such as logs and user files. It should also not be used to store installation PIE files.

Cisco IOS XR Getting Started Guide 7-26 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

If the software you want to add is not on the router, the fastest way to get the software is to download it as follows: 1. Locate the software on Cisco.com and download the software. 2. Unpack the software bundle, if it is packaged in a tar file. 3. Transfer the package files to the router or a network file server to which the router has network access. The following sections describe how to complete these tasks.

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 software before you transfer it to the router. Each tar file is used to package multiple files in a single file to make downloading simpler. Third-party software programs can unpack tar files and place the unpackaged files in a folder you select. For more information on unpacking tar files, see the documentation for the third-party program that unpacks these files.

Transferring Installation Files to a Network File Server or the Router

When the files are downloaded and unpacked, you may have one or two types of installation files. PIE files (with the pie extension) can be added while the router is running. The vm files must be added from the ROM Monitor program as described in Cisco IOS XR ROM Monitor Guide. You can use the guidelines in this section to transfer both types of installation files. The Cisco IOS XR software can be added from either a network file server or flash disk1. If flash disk1 is not installed, copy the files to a network file server to which your router has network access. Consult your system administrator for the location and availability of your network server. If flash disk1 is installed, you can copy installation files to that flash disk and then add the software from flash disk1. You can copy files to the router using TFTP, FTP, SFTP, or rcp protocols (see Table 7-4).

Cisco IOS XR Getting Started Guide 7-27 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

Table 7-4 Download Protocols Supported by Cisco IOS XR Software

Name Description Trivial File Transfer TFTP is a simplified version of FTP that allows files to be transferred from one computer to another Protocol 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 FTP is part of the TCP/IP protocol stack and requires a username and password. Remote Copy Protocol The rcp protocol uses TCP to ensure the reliable delivery of data, and rcp downloads require a usernames. SSH File Transfer SFTP is part of the SSHv2 feature in the Security package and provides for secure file transfers. Protocol For more information, see the Cisco IOS XR System Security Configuration Guide.

The router commands listed in Table 7-5 show how to copy package files to the router using three types of file transfer protocols.

Table 7-5 Commands for Copying Package Files to the Router

Server Type Command and Example TFTP 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-full.pie disk1:

FTP 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:[email protected]/images/comp-hfr-full.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://[email protected]/images/comp-hfr-full.pie disk1:

Table 7-6 describes the command variables for copying packages from a network server.

Table 7-6 Command Variables for Copying and Adding Packages from a Network Server

Variable Description hostname_or_ipaddress Host name or IP address of the server that stores the source file. pie-name 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.

Cisco IOS XR Getting Started Guide 7-28 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

Variable Description username Required for FTP and rcp only and must be a valid username on the FTP or rcp server. password Required for FTP only. If a password is not provided, the networking device accepts anonymous FTP. directory-path The specified directory should be a directory under the home directory of the user. In the rcp and FTP examples in Table 7-5, 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.

Controlling install Command Operation

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. 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 determine if an install command is currently running, enter the show install request command. 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

Note The install add and install activate commands must be executed in admin EXEC mode and are described later in this chapter.

Cisco IOS XR Getting Started Guide 7-29 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information Upgrading and Adding Packages from a Flash Disk

The processes for upgrading, downgrading, and adding optional packages are introduced in the “Information About Package Management” section on page 7-9. The procedure in this section describes how to upgrade or add Cisco IOS XR software supplied in PIE files that are stored on flash disk1. This software 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.

Prerequisites

Before upgrading or adding packages from flash disk1, verify that the following prerequisites have been met: • For Cisco CRS-1 routers, ROM Monitor 1.32 or higher is installed. For instructions on upgrading ROM Monitor, see Cisco IOS XR ROM Monitor Guide. • For Cisco XR 12000 Series Routers, ROM Monitor 1.14 is installed. For instructions on upgrading ROM Monitor, see Cisco IOS XR ROM Monitor Guide. • All packages to be upgraded or added are present on flash disk1. For more information, see the “Obtaining and Placing Cisco IOS XR Software” section on page 7-26. • Prerequisites for the activation of packages are met as described in the “Activation and Deactivation Prerequisites” section on page 7-19.

Summary Steps

1. Connect to the DSC console port and log in. 2. dir disk1: 3. admin 4. install add disk1:pie-file [activate] 5. install activate disk0:package [location nodeID] [test] 6. Repeat Steps 4 through 6 until all packages are activated. 7. show install active 8. install commit

Cisco IOS XR Getting Started Guide 7-30 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

Detailed Steps

Command or Action Purpose Step 1 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-8. Step 2 dir disk1: (Optional) Displays the files that are available for package upgrades and additions. Example: • Only PIE files can be added and activated RP/0/0/CPU0:router# dir disk1: using this procedure. • For more information on PIE file names, see the “Standard PIE Filenames and Version Numbers” section on page 7-13. Step 3 admin Places the router in admin EXEC mode.

Example: RP/0/0/CPU0:router# admin Step 4 install add disk1:pie-file [activate] Adds a PIE file and prepares it for activation on the router. Example: • Replace pie-file with the name of the PIE RP/0/0/CPU0:router(admin)# install add file you want to add. disk1:c12k-mgbl.pie-3.3.0.1i • The activate option automatically activates the software package after it is successfully added. Note 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.

Cisco IOS XR Getting Started Guide 7-31 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 5 install activate disk0: package [location nodeID] [test] Activates a package that was previously added to the router. Example: • Skip this step if the package was activated RP/0/0/CPU0:router(admin)# install activate earlier with the install add command. disk0:c12k-mgbl-3.3.0 • Replace package with the name of an inactive package, which can be displayed as described in the previous step. • 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, enter the show platform command. • 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. Tip 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. To view an example of an activation with the test option and the information you can display, see “Activating and Testing a Package on the Router: Example” section on page 7-40. Step 6 Repeat Steps 4 through 6 until all packages are activated. Activates additional packages as required for your router. Step 7 show install active (Optional) Displays all active packages. • Use this display to determine if the correct Example: packages are active. RP/0/0/CPU0:router# show install active Step 8 install commit (Optional) Commits the current set of packages so that these packages are used if the router is restarted. For more information, see Example: RP/0/0/CPU0:router(admin)# install commit the “Committing the Active Package Set” section on page 7-39.

Cisco IOS XR Getting Started Guide 7-32 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

Examples

This section contains examples for the following subjects: • Adding a Package, page 7-33 • Activating a Package, page 7-33 • Activating a Package for a Single Card, page 7-33

Adding a Package

The following example shows how to add the contents of a PIE file on disk1 to disk0: RP/0/RP0/CPU0:router(admin)#install add disk1:hfr-mpls.pie synchronous

Install operation 4 'install add /disk1:hfr-mpls.pie synchronous' started by user 'cisco' at 03:17:05 UTC Mon Nov 14 2005. 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 03:18:30 UTC Mon Nov 14 2005. RP/0/RP0/CPU0:router(admin)#

Activating a Package

The following example shows the activation of the MPLS package on a Cisco CRS-1 router: RP/0/RP0/CPU0:router(admin)#install activate disk0:hfr-mpls-3.3.80 synchronous

Install operation 5 'install activate disk0:hfr-mpls-3.3.80 synchronous' started by user 'cisco' at 03:20:44 UTC Mon Nov 14 2005. Info: The changes made to software configurations will not be persistent across system reloads. Use the command Info: 'admin install 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 Install operation 5 completed successfully at 03:22:04 UTC Mon Nov 14 2005.

Activating a Package for a Single Card

The following example shows the activation of a routing package on a single card on a Cisco XR 12000 Series Router: RP/0/0/CPU0:router(admin)# install activate disk0:hfr-rout-1.0.0 location 0/2/CPU0

Cisco IOS XR Getting Started Guide 7-33 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information Upgrading and Adding Packages from a Network File Server

The processes for upgrading, downgrading, and adding optional packages are introduced in the “Information About Package Management” section on page 7-9. The procedure in this section describes how to upgrade or add Cisco IOS XR software supplied in PIE files that are stored on a network file server. This software can include any of the following: • The Cisco IOS XR Unicast Routing Core Bundle (six packages in one PIE file) • Any of the five optional packages (one package for each 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.

Prerequisites

Before upgrading or adding packages from a network file server, verify that the following prerequisites have been met: • For Cisco CRS-1 routers, ROM Monitor 1.32 or higher is installed. For instructions on upgrading ROM Monitor, see Cisco IOS XR ROM Monitor Guide. • For Cisco XR 12000 Series Routers, ROM Monitor 1.14 is installed. For instructions on upgrading ROM Monitor, see Cisco IOS XR ROM Monitor Guide. • All packages to be upgraded or added are present on a network file server. For more information, see the “Obtaining and Placing Cisco IOS XR Software” section on page 7-26. • Prerequisites for the activation of packages are met as described in the “Activation and Deactivation Prerequisites” section on page 7-19.

Summary Steps

1. Connect to the DSC console port and log in. 2. dir disk1: 3. admin 4. 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] 5. install activate disk0:package [location nodeID] [test] 6. Repeat Steps 4 through 6 until all packages are activated. 7. show install active 8. install commit

Cisco IOS XR Getting Started Guide 7-34 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

Detailed Steps

Command or Action Purpose Step 1 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-8. Step 2 dir disk1: (Optional) Displays the installation files that are available for package upgrades and additions. Example: RP/0/0/CPU0:router# dir disk1: • Only PIE files can be added using this procedure. • For more information on PIE file names, see the “Standard PIE Filenames and Version Numbers” section on page 7-13. Step 3 admin Places the router in admin EXEC mode.

Example: RP/0/0/CPU0:router# admin Step 4 install add Adds a PIE file and prepares it for activation tftp://hostname_or_ipaddress/directory-path/pie-file on the router. [activate] or • Replace hostname_or_ipaddress with the install add ftp://username:password@hostname_or_ipaddress/ host name or IP address of the network directory-path/pie-file [activate] file server. or • Replace directory-path with the network install add file server path that leads to the PIE file to rcp://username@hostname_or_ipaddress/directory-path/ be added. pie-file [activate] • Replace pie-file with the name of the PIE file you want to add. Example: RP/0/0/CPU0:router(admin)# install add • Replace username with a username that tftp://10.1.1.1/images/hfr-k9sec-p.pie has access privileges to the directory in or which the PIE file is stored. RP/0/0/CPU0:router(admin)# install add • Replace password with the password ftp://john:[email protected]/images/hfr-k9sec-p.pie associated with the username that has or access privileges to the directory in which RP/0/0/CPU0:router(admin)# install add the PIE file is stored. rcp://[email protected]/images/gsr-k9sec-p.pie • The activate option automatically activates the software package after it is successfully added. Note 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.

Cisco IOS XR Getting Started Guide 7-35 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 5 install activate disk0:package [location nodeID] [test] Activates a package that was added to the router. Example: • Replace package with the name of an RP/0/0/CPU0:router(admin)# install activate inactive package, which can be displayed disk0:c12k-mgbl-3.3.0 as described in the previous step. • 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, enter the show platform command. • 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. Tip 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. To view an example of an activation with the test option and the information you can display, see “Activating and Testing a Package on the Router: Example” section on page 7-40. Step 6 Repeat Steps 4 through 6 until all packages are activated. Activates additional packages as required for your router. Step 7 show install active (Optional) Displays all active packages. • Use this display to determine if the correct Example: packages are active. RP/0/0/CPU0:router# show install active Step 8 install commit (Optional) Commits the current set of packages so that these packages are used if the router is restarted. For more information, see Example: RP/0/0/CPU0:router(admin)# install commit the “Committing the Active Package Set” section on page 7-39.

Cisco IOS XR Getting Started Guide 7-36 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

Examples

This section contains examples for the following subjects: • Adding a Package from a TFTP File Server, page 7-37 • Adding and Activating a Package from an FTP File Server with One Command, page 7-37

Adding a Package from a TFTP File Server

The following example shows how to add the Manageability package from a TFTP server to a Cisco CRS-1 router: RP/0/RP0/CPU0:router(admin)#install add tftp://10.0.0.0/hfr-mpls.pie synchronous

Install operation 4 'install add /tftp://10.0.0.0 /hfr-mpls.pie synchronous' started by user 'cisco' at 03:17:05 UTC Mon Nov 14 2005. 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 03:18:30 UTC Mon Nov 14 2005. RP/0/RP0/CPU0:router(admin)#

Adding and Activating a Package from an FTP File Server with One Command

The following example shows the addition and activation of the Security package on a Cisco CRS-1 router: RP/0/RP0/CPU0:router(admin)# install add ftp://john:[email protected]/images/hfr-k9sec-p.pie activate

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

Cisco IOS XR Getting Started Guide 7-37 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information

Info: indirectly cause every node in the router to reload. Proceed with this install operation? [confirm] / 10% complete. The install operation can still be aborted (ctrl-c). 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 Noncommitted Rollback Point

Beginning in Release 3.0, you can roll back the system to noncommitted rollback points, which are described in the “Displaying Rollback Points” section on page 7-24. To roll back to a noncommitted rollback point, enter the install rollback command in admin EXEC mode with the rollback point number.

Note 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. However, if you choose a rollback point that is older than the most recent point, you must enter the install rollback command with the reload option, which reloads the router and interrupts traffic.

Tip To display the noncommitted 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' 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 Install operation 10 completed successfully at 07:51:24 UTC Mon Nov 14 2005.

Cisco IOS XR Getting Started Guide 7-38 Chapter 7 Upgrading and Managing Cisco IOS XR Software Package Management Procedures R3.3 Beta Draft—Cisco Confidential Information Committing the Active Package Set

To make the current active package set persistent across router reloads, enter the install commit command in admin EXEC mode. The following example shows the commitment of the active software on a Cisco CRS-1 router: RP/0/RP0/CPU0:router(admin)# install commit

Install operation 6 'install commit' started by user 'cisco' at 03:22:28 UTC Mon Nov 14 2005. Install operation 6 completed successfully at 03:22:31 UTC Mon Nov 14 2005. RP/0/RP0/CPU0:router(admin)#

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.

Deactivating a Package

When you deactivate a package, the package features are unavailable to the router. The package files are still on the router, and can be activated later. Prerequisites for the deactivation of packages should be met as described in the “Activation and Deactivation Prerequisites” section on page 7-19. To deactivate a package, enter the install deactivate command in admin EXEC mode, as shown in the following example: RP/0/RP0/CPU0:router(admin)# install deactivate disk0:hfr-mpls-3.3.80 synchronous

Install operation 7 'install deactivate disk0:hfr-mpls-3.3.80 synchronous' started by user 'cisco' at 03:22:55 UTC Mon Nov 14 2005. Info: The changes made to software configurations will not be persistent across system reloads. Use the command Info: 'admin install 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 Install operation 7 completed successfully at 03:24:17 UTC Mon Nov 14 2005. RP/0/RP0/CPU0:router(admin)# install commit

Removing Inactive Packages from the Router

To remove a package or an SMU from the router, you must first deactivate the package. The steps to remove inactive software are as follows: 1. install deactivate package 2. install remove package Packages can be removed only if they are deactivated from all cards. 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.

Cisco IOS XR Getting Started Guide 7-39 Chapter 7 Upgrading and Managing Cisco IOS XR Software Configuration Examples for Managing Packages R3.3 Beta Draft—Cisco Confidential Information

Tip To preview the impact of a deactivation, enter the test option with the install deactivate command to display the results of the action without impacting the router.

The following example shows the deactivation and removal of the MPLS package: RP/0/RP0/CPU0:router(admin)# install deactivate disk0:hfr-mpls-3.3.80 synchronous

RP/0/RP0/CPU0:router(admin)# install remove inactive

Install operation 4 'install remove inactive' started by user 'cisco' at 12:59:45 UTC Mon Dec 05 2005. Info: This operation will remove the following package: Info: disk0:hfr-os-ldr-3.3.80 Proceed with removing these packages? [confirm] y

The install operation will continue asynchronously. Install operation 4 completed successfully Install operation 4 completed successfully at 13:01:44 UTC Mon Dec 05 2005.

Configuration Examples for Managing Packages

This section provides the following package management examples: • Activating and Testing a Package on the Router: Example, page 7-40

Activating and Testing a Package on the Router: Example

To preview the impact of a package activation, enter the install activate command in admin EXEC mode with the test option. The test option simulates the activation and displays the results, but it does not actually activate the package. Review the test activation results to determine if the activation can be successful and what level of restart is required. To display the details of a test activation, enter the show install log ID detail command or the show install log ID verbose command. Replace ID with the operation ID that appears after the install activate command is entered. In the following example, a Manageability package activation is tested. The router assigns operation ID 33 to this text activation, and this ID is used with the show install log command to display the details of the text activation. RP/0/RP1/CPU0:router(admin)# install activate disk0:hfr-mgbl-3.3.80 test

Cisco IOS XR Getting Started Guide 7-40 Chapter 7 Upgrading and Managing Cisco IOS XR Software Configuration Examples for Managing Packages R3.3 Beta Draft—Cisco Confidential Information

RP/0/RP1/CPU0:Nov 19 17:10:48.217 : instdir[200]: Install operation 33 'install activate disk0:hfr-mgbl-3.3.80 test' started by user 'cisco' at 17:10:48 UTC Sat Nov 19 2005. / 0% complete. The install operation can still be aborted (ctrl-c). \ 1% complete. The install operation can still be aborted (ctrl-c). | 1% complete. The install operation can still be aborted (ctrl-c). / 10% complete. The install operation can still be aborted (ctrl-c). - 10% complete. The install operation can still be aborted (ctrl-c). RP/0/RP1/CPU0:router(admin)#Warning: SDR Owner: No incompatible configuration will be removed due to the Warning: 'test' option Warning: SDR Owner: The previous installation operation will be aborted. Info: SDR Owner: No configuration operations need to be rolled back. 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 33 completed successfully at 17:10:58 UTC Sat Nov 19 2005.

RP/0/RP1/CPU0:router(admin)# show install log detail

Install operation 33 started by user 'cisco' at 17:10:48 UTC Sat Nov 19 2005. install activate disk0:hfr-mgbl-3.3.80 test Install operation 33 completed successfully at 17:10:58 UTC Sat Nov 19 2005.

Summary: Node 0/0/SP: No processes affected

Node 0/0/CPU0: No processes affected

Node 0/3/SP: No processes affected

Node 0/3/CPU0: No processes affected

Node 0/RP1/CPU0: Activated: hfr-mgbl-3.3.80 6 hfr-mgbl processes affected (0 updated, 6 added, 0 removed, 0 impacted)

Node 0/SM0/SP: No processes affected

Install logs: Install operation 33 'install activate disk0:hfr-mgbl-3.3.80 test' started by user 'cisco' at 17:10:48 UTC Sat Nov 19 2005. Warning: No changes will occur due to 'test' option being specified. The Warning: following is the predicted output for this install command. Warning: SDR Owner: No incompatible configuration will be removed due to Warning: the 'test' option Warning: SDR Owner: The previous installation operation will be aborted. Info: SDR Owner: No configuration operations need to be rolled back. 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

Cisco IOS XR Getting Started Guide 7-41 Chapter 7 Upgrading and Managing Cisco IOS XR Software Configuration Examples for Managing Packages R3.3 Beta Draft—Cisco Confidential Information

Info: install verify Install operation 33 completed successfully at 17:10:58 UTC Sat Nov 19 2005.

RP/0/RP1/CPU0:router(admin)# show install log 33 verbose

Install operation 33 started by user 'cisco' at 17:10:48 UTC Sat Nov 19 2005. install activate disk0:hfr-mgbl-3.3.80 test Install operation 33 completed successfully at 17:10:58 UTC Sat Nov 19 2005.

Summary: Node 0/0/SP: No processes affected

Node 0/0/CPU0: No processes affected

Node 0/3/SP: No processes affected

Node 0/3/CPU0: No processes affected

Node 0/RP1/CPU0: Activated: hfr-mgbl-3.3.80 6 hfr-mgbl processes affected (0 updated, 6 added, 0 removed, 0 impacted)

Node 0/SM0/SP: No processes affected

Installation changes:

Installation changes on node 0/RP1/CPU0: Adding executable: ipsla_ma Adding executable: ipsla_path_setup_test Adding executable: ipsla_responder Adding executable: ipsla_sa Adding executable: ipsla_ts_svr Adding executable: man_craft_show Adding executable: monitor_controller Adding executable: monitor_interface Adding executable: perfmgmt_show Adding and starting process: pm_collector

Cisco IOS XR Getting Started Guide 7-42 Chapter 7 Upgrading and Managing Cisco IOS XR Software Configuration Examples for Managing Packages R3.3 Beta Draft—Cisco Confidential Information

Adding and starting process: pm_server Adding executable: show_ipsla_common Adding executable: show_ipsla_ma_ltrace Adding executable: show_ipsla_resp_ltrace Adding executable: show_ipsla_resp_stats Adding executable: show_ipsla_sa_ltrace Adding executable: show_ipsla_stats Adding executable: show_ipsla_ts_ltrace Adding and starting process: snmppingd Adding executable: xml_demo_agent Adding executable: xml_mda_show_ltrace Adding executable: xml_tty_client Adding and starting process: xmlagent Adding file: sh_ciscosensormib_ns_cfg__api.configinfo Adding file: sh_emweb_ns_cfg__api.configinfo Adding file: sh_frucontrolmib_ns_cfg__api.configinfo Adding file: sh_ipsla_ns_cfg__api.configinfo Adding file: sh_perfmgmt_ns_cfg__api.configinfo Adding file: sh_xmlagent_ns_cfg__api.configinfo Adding file: comm.jar Adding file: comm.jar.nonwindows Adding file: comm.jar.unix Adding file: craft.html Adding file: cwi.xml Adding file: cwi_definitions.jar Adding file: cwi_desktop.jar Adding file: cwi_help.zip Adding file: cwi_if.jar Adding file: cwi_ne.jar Adding file: cwi_tools.jar Adding file: installer.jar Adding file: javax.comm.properties Adding file: jcl.jar Adding file: libSerial.so.linux Adding file: librxtxSerial.jnilib.mac Adding file: orb.jar Adding file: win32com.dll.win Adding DLL: lib_ipsla_app_cmn_bag_descr.dll Adding DLL: libipsla_icmp_echo.dll Adding DLL: libipsla_icmp_path_echo.dll Adding DLL: libipsla_icmp_pathjitter.dll Adding DLL: libipsla_infra.dll Adding DLL: libipsla_infra_comp.dll Adding DLL: libipsla_udp_echo.dll Adding DLL: libipsla_udp_jitter.dll Adding DLL: libipsla_utils.dll Adding DLL: libperfmgmtbagdesc.dll Adding DLL: libplatform_ipsla_ts.dll Adding DLL: libtaoorbutils.dll Adding DLL: libxmlalarmops.dll Adding DLL: libxmlcfgmgrdebug.dll Adding DLL: libxmlcfgmgrops.dll Adding DLL: libxmlcliops.dll Adding DLL: libxmlmdadebug.dll Adding DLL: libxmlmdaops.dll Adding DLL: libxmlmdatrans.dll Adding DLL: libxmlservice.dll Adding DLL: libxmltarcfg.dll Adding DLL: libxmlttycmn.dll Adding DLL: libhttperr.dll Adding DLL: libipsla_error.dll Adding DLL: libpm_error.dll Adding DLL: libtaoorb_error.dll Adding DLL: libxmlalarmerror.dll

Cisco IOS XR Getting Started Guide 7-43 Chapter 7 Upgrading and Managing Cisco IOS XR Software Configuration Examples for Managing Packages R3.3 Beta Draft—Cisco Confidential Information

Adding DLL: libxmlcfgmgrerror.dll Adding DLL: libxmlclierror.dll Adding DLL: libxmlmdaerror.dll Adding DLL: libxmlserviceerror.dll Adding DLL: libxmlttyerror.dll Adding DLL: libbulkfilemib.dll Adding DLL: libciscoassetmib.dll Adding DLL: libciscosensormib.dll Adding DLL: libenhimagemib.dll Adding DLL: libeventmib.dll Adding DLL: libexpressionmib.dll Adding DLL: libfrucontrolmib.dll Adding DLL: libftpclientmib.dll Adding DLL: libpingmib.dll Adding DLL: librttmonmib.dll Adding file: Manageabilty-Debug.info Adding file: Manageabilty.info Adding file: Performance-Management.info Adding file: Event.mib Adding file: bulkfile.mib Adding file: ciscoasset.mib Adding file: ciscosensor.mib Adding file: enhimage.mib Adding file: expression.mib Adding file: frucontrol.mib Adding file: ftpclient.mib Adding file: ping.mib Adding file: rttmon.mib Adding file: bulkfilemib_cmds.parser Adding file: cfg_emorb_cmds.parser Adding file: cfg_emorb_xmlagent.parser Adding file: cfg_ipsla.parser Adding file: cfg_perfmgmt.parser Adding file: ciscoassetmib_cmds.parser Adding file: ciscosensormib_cmds.parser Adding file: debug_ipsla.parser Adding file: enhimagemib_cmds.parser Adding file: eventmib_cmds.parser Adding file: expressionmib_cmds.parser Adding file: frucontrolmib_cmds.parser Adding file: ftpclientmib_cmds.parser Adding file: http_cfg_cmds.parser Adding file: http_debug_cmds.parser Adding file: man_craft_show.parser Adding file: oper_perfmgmt.parser Adding file: pingmib_cmds.parser Adding file: rttmonmib_cmds.parser Adding file: show_ipsla.parser Adding file: show_ipsla_ts.parser Adding file: xml_cfgmgr_debug.parser Adding file: xml_cli_debug.parser Adding file: xml_infra_cfg.parser Adding file: xml_infra_debug.parser Adding file: xml_infra_show.parser Adding file: xml_mda_debug.parser Adding file: xml_mda_show.parser Adding file: xml_tty_agent_cfg.parser Adding file: xml_tty_client_exec.parser Adding file: xml_tty_cmn_debug.parser Adding file: sh_mgbl_ns_cfg__api.partitioninfo Adding and starting process: emweb Adding and starting process: xml_tty_agent Adding file: ipsla_app_common_cfg.schema Adding file: ipsla_app_common_oper.schema

Cisco IOS XR Getting Started Guide 7-44 Chapter 7 Upgrading and Managing Cisco IOS XR Software Configuration Examples for Managing Packages R3.3 Beta Draft—Cisco Confidential Information

Adding file: ipsla_op_def_cfg.schema Adding file: ipsla_op_hist_oper.schema Adding file: ipsla_op_hist_path_oper.schema Adding file: ipsla_op_oper.schema Adding file: ipsla_op_react_cfg.schema Adding file: ipsla_op_sched_cfg.schema Adding file: ipsla_op_stats_enhc_oper.schema Adding file: ipsla_op_stats_hrly_d_oper.schema Adding file: ipsla_op_stats_hrly_nd_oper.schema Adding file: ipsla_op_stats_hrly_oper.schema Adding file: ipsla_op_stats_ltst_oper.schema Adding file: ipsla_op_stats_oper.schema Adding file: ipsla_react_trig_cfg.schema Adding file: ipsla_resp_cfg.schema Adding file: ipsla_resp_oper.schema Adding file: manageability_perf_cfg_common.schema Adding file: manageability_perf_enable_monitor_cfg.schema Adding file: manageability_perf_enable_stats_cfg.schema Adding file: manageability_perf_enable_thresh_cfg.schema Adding file: manageability_perf_oper.schema Adding file: manageability_perf_stats_cfg.schema Adding file: manageability_perf_thresh_cfg.schema Adding file: httpd.startup Adding file: ipsla_ma.startup Adding file: ipsla_responder.startup Adding file: ipsla_sa.startup Adding file: ipsla_ts_svr.startup Adding file: pingmib.startup Adding file: pm_collector.startup Adding file: pm_server.startup Adding file: xml_tty_agent.startup Adding file: xmlagent.startup Replacing file: md5_manifest

Installation impact details: Output format: (:) [package:component] Level : the distance from the process along the DLL dependency chain Impact : a one character indication of how this server or DLL is impacted: C modified; A added; R removed; I impacted by its dependencies Note : blank, or one of these annotations: d duplicate (this DLL has already been listed previously for this process) s self-managing (this server self-manages changes in its dependencies Name : the name of this server or DLL Type : "server" or "DLL" Package : the Package containing this server or DLL Component: the source code component containing this server or DLL

Node class: RP 1 node(s): 0/RP1/CPU0 6 New Servers to be started 0 (A: ) pm_collector server [hfr-mgbl:manageability-perf] 0 (A: ) pm_server server [hfr-mgbl:manageability-perf] 0 (A: ) snmppingd server [hfr-mgbl:snmp-pingmib] 0 (A: ) xmlagent server [hfr-mgbl:generic-xmlagent] 0 (A: ) emweb server [hfr-mgbl:emweb] 0 (A: ) xml_tty_agent server [hfr-mgbl:man-xml-ttyagent]

Cisco IOS XR Getting Started Guide 7-45 Chapter 7 Upgrading and Managing Cisco IOS XR Software Configuration Examples for Managing Packages R3.3 Beta Draft—Cisco Confidential Information

Cisco IOS XR Getting Started Guide 7-46 R3.3 Beta Draft—Cisco Confidential Information

CHAPTER 8

Managing the Router Hardware

Beta Draft Cisco Confidential Information

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

This chapter contains the following sections: • Displaying Hardware Status, page 8-1 • RP Redundancy and Switchover, page 8-11 • Reloading, Shutting Down, or Power Cycling a Node, page 8-16 • Using Controller Commands to Manage Hardware Components, page 8-18 • Formatting Hard Drives, Flash Drives, and Other Storage Devices, page 8-19 • Removing and Replacing Cards, page 8-19

Displaying Hardware Status

The following sections describe how to display different types of hardware status information: • Displaying Hardware Version Information, page 8-2 • Displaying the Chassis Serial Numbers (Cisco CRS-1 Routers), page 8-3 • Displaying the Configured Chassis Serial Numbers, page 8-4 • Displaying Software and Hardware Information, page 8-4 • Displaying SDR Node IDs and Status, page 8-5 • Displaying Router Environment Information, page 8-8 • Displaying RP Redundancy Status, page 8-10

Cisco IOS XR Getting Started Guide 8-1 Chapter 8 Managing the Router Hardware Displaying Hardware Status R3.3 Beta Draft—Cisco Confidential Information Displaying Hardware Version Information

The show diag command displays detailed information on the hardware components for each node. This information includes the card serial number and the ROMMON software version. The syntax for the show diag command is: show diag [nodeID | details | summary]

Tip For information on the software version, use the show version command.

In the following example, the show diag command displays information for all nodes: RP/0/RP0/CPU0:Router# show diag

NODE 0/0/SP : MSC(SP) MAIN: type 500060, 0800-019840-1033 rev 01 dev 010cd8 HW version 0.0 S/N SAD07290129 PCA: 0073-007648-04 rev 08 Board State : IOS XR RUN PLD: Motherboard: 0xf425, Processor: 0x0000, Power: N/A MONLIB: QNXFFS Monlib Version 2.2 ROMMON: Version 1.15(20040603:013227) [CRS-1 ROMMON]

NODE 0/0/CPU0 : MSC(16OC48-POS/DPT) MAIN: type 500060, 0800-019840-1033 rev 01 dev 010cd8 HW version 0.0 S/N SAD07290129 PCA: 0073-007648-04 rev 08 Board State : IOS XR RUN PLD: Motherboard: 0x0025, Processor: 0xda13, Power: N/A MONLIB: QNXFFS Monlib Version 2.2 ROMMON: Version 1.15(20040603:013406) [CRS-1 ROMMON]

NODE 0/2/SP : 4OC192-POS/DPT PLIM PRESENT

NODE 0/3/SP : MSC(SP) MAIN: type 500060, 0800-025021-259 rev 01 dev 000000 HW version 0.0 S/N SAD074907X6 PCA: 0073-007648-06 rev 11 Board State : IOS XR RUN PLD: Motherboard: 0xfa25, Processor: 0x0000, Power: N/A MONLIB: QNXFFS Monlib Version 2.2 ROMMON: Version 1.15(20040603:013227) [CRS-1 ROMMON]

NODE 0/3/CPU0 : MSC(16OC48-POS/DPT) MAIN: type 500060, 0800-025021-259 rev 01 dev 000000 HW version 0.0 S/N SAD074907X6 PCA: 0073-007648-06 rev 11 Board State : IOS XR RUN PLD: Motherboard: 0x0025, Processor: 0xda13, Power: N/A MONLIB: QNXFFS Monlib Version 2.2 ROMMON: Version 1.15(20040603:013406) [CRS-1 ROMMON]

NODE 0/RP0/CPU0 : RP MAIN: type 100000, 0000-000000-00 rev 01 dev 000000 HW version 0.0 S/N SAD07150223 PCA: 0073-007641-04 rev 05

Cisco IOS XR Getting Started Guide 8-2 Chapter 8 Managing the Router Hardware Displaying Hardware Status R3.3 Beta Draft—Cisco Confidential Information

Board State : IOS XR RUN PLD: Motherboard: 0x0018, Processor: 0xda13, Power: 0x001f MONLIB: QNXFFS Monlib Version 2.1 ROMMON: Version 1.15(20040603:013406) [CRS-1 ROMMON]

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 node: RP/0/RP0/CPU0:router# show diag 0/2/cpu0

RACK 0 SLOT 2 : MSC(16OC48-POS/DPT) MAIN: type 500060, 0000-000000-00 rev 00 dev 000000 HW version 0.0 S/N SAD0719013M PCA: 0073-007648-04 rev 07 Board State : IOS XR RUN PLD: Motherboard: 0x0024, Processor: 0xda12, Power: 0xf100 MONLIB: QNXFFS Monlib Version 2.1 ROMMON: Version 1.15(20040120:002937) [CRS-1 ROMMON]

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

Cisco IOS XR Getting Started Guide 8-3 Chapter 8 Managing the Router Hardware Displaying Hardware Status R3.3 Beta Draft—Cisco Confidential Information

--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. 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)#

Note This command can also be entered in administration configuration mode.

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/RP0/CPU0:router# show version

ROM: System Bootstrap, Version 1.15(20040120:002852) ,

router uptime is 2 days, 1 hour, 59 minutes System image file is "tftp://223.0.0.0/usr/comp-hfr-full.vm-1.0.0

cisco CRS-16/S (7450) processor with 2097152K bytes of memory. 7450 processor at 650Mhz, Implementation , Revision

Configuration register is 0x0

Cisco IOS XR Getting Started Guide 8-4 Chapter 8 Managing the Router Hardware Displaying Hardware Status R3.3 Beta Draft—Cisco Confidential Information

Package active on node 0/2/SP: hfr-admin, V 1.0.0, Cisco Systems, at mem:hfr-admin-1.0.0 Built on Fri Mar 5 19:12:26 PST 2004 --More--

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 a Cisco CRS-1 router: 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.” • 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

Cisco IOS XR Getting Started Guide 8-5 Chapter 8 Managing the Router Hardware Displaying Hardware Status R3.3 Beta Draft—Cisco Confidential Information

Table 8-1 Node ID Components on Cisco CRS-1 Routers (continued)

Card Type Rack Slot Module (the card type to which you are (always “0” in a (the physical slot in which the (the entity on the card that is issuing commands) single-shelf system) card is installed) the target of the command) Cisco CRS-1 SPA Interface 0–255 0–7 (8-slot chassis) CPU0 Processor (SIP)-800 0–15 (16-slot chassis) 1-Port OC-192c/STM-64c 0–255 0–7 (8-slot chassis) 0–5 (SPA module number on Packet-over-SONET/SDH (POS) 0–15 (16-slot chassis) the Cisco CRS-1 SIP-800) XFP SPA 4-Port OC-3c/STM-1 POS SPA 8-Port Gigabit Ethernet SPA Switch fabric module 0–255 SM0–SM3 (8-slot chassis) SP SM0–SM7 (16-slot chassis) Alarm cards 0–255 AM0–AM1 (16-slot chassis) SP Fan controller cards 0–255 FC0–FC1 (16-slot chassis) SP

Table 8-2 Node ID Components on Cisco XR 12000 Series Routers

Slot Card Type Rack (the logical slot number Module (the card type to which you are (always “0” in a single-shelf reported in command (the entity on the card that issuing commands) system) displays) executes the commands) Route processor 0 0–151, 2 CPU0 Cisco XR 12000 and 12000 Series 0 0–151 CPU0 line cards Cisco XR 12000 and 12000 Series 0 0–151 CPU0 SPA Interface Processor (SIP)-600 1-Port 10-Gigabit Ethernet SPA 0 0–151 0-1 (SPA module number on the Cisco XR 12000 and 5-Port Gigabit Ethernet SPA 12000 Series SIP-600) 10-Port Gigabit Ethernet SPA 1-Port OC-192c/STM-64c POS/RPR SPA Clock and scheduler cards (CSCs) 0 CSC 0 and 13 CPU0 Switch fabric cards (SFCs) 0 SFC 0, 1, 2, 3, and 43, 4 CPU0 Consolidated switch fabric (CSF) 0 Dedicated slot 175 CPU0 card

1. Depends on router model. 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.

Cisco IOS XR Getting Started Guide 8-6 Chapter 8 Managing the Router Hardware Displaying Hardware Status R3.3 Beta Draft—Cisco Confidential Information Displaying Router Node IDs and Status

In administration EXEC mode, the show platform command displays information for all router nodes, which includes nodes in all chassis and SDRs. In administration EXEC mode, the command display also includes additional nodeids 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

Cisco IOS XR Getting Started Guide 8-7 Chapter 8 Managing the Router Hardware Displaying Hardware Status R3.3 Beta Draft—Cisco Confidential Information

F0/AM1/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON F0/LM0/SP FCC-LED(SP) N/A IOS XR RUN PWR,NSHUT,MON F0/LM1/SP UNKNOWN(SP) N/A IN-RESET 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.

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 [all | fans | leds | power-supply | table | temperatures | voltages] You can use the show environment command options to limit the detail in the command display. The following example shows the full environment status report: RP/0/0/CPU0:router# show environment

Temperature Information ------

R/S/I Modules Sensor Temp. (deg C)

0/0/* host Inlet 23.0 host Hot 23.0 0/3/* host Inlet 24.0 host Hot 33.0 0/4/* host Inlet 24.5 host Hot 31.5 0/5/* host Inlet 23.5 host Hot 30.5 0/6/* host Hot 31.5 host Inlet 22.5 0/7/* host Inlet 20.0 host Hot 29.5 0/8/* host Inlet 20.5 host Hot 32.0

Threshold Information ------

R/S/I Modules Sensor Minor Major Critical (Lo/Hi) (Lo/Hi) (Lo/Hi)

0/0/* host InletTemp --/ 55 --/ 60 --/ --

Cisco IOS XR Getting Started Guide 8-8 Chapter 8 Managing the Router Hardware Displaying Hardware Status R3.3 Beta Draft—Cisco Confidential Information

host HotTemp --/ 66 --/ 69 --/ -- host PLIM_V4_1.6V --/ -- --/ -- --/ -- host PLIM_V5_1.8V --/ -- --/ -- --/ -- host PLIM_V3_2.5V --/ -- --/ -- --/ -- host 3.3V 2950/3500 2900/3600 --/ -- host 5V 4800/5150 4700/5200 --/ -- host Mbus5V 4700/5300 4500/5500 --/ -- 0/3/* host InletTemp --/ 55 --/ 60 --/ 70 host HotTemp --/ 66 --/ 69 --/ 75 host PLIM_V3_1.5V --/ -- --/ -- --/ -- host PLIM_V8_1.8V --/ -- --/ -- --/ -- host PLIM_V7_2.5V --/ -- --/ -- --/ -- host 3.3V --/ -- --/ -- --/ -- host 5V 4800/5200 4700/5300 4600/5400 host Mbus5V 4700/5300 4600/5400 4500/5500 0/4/* host InletTemp --/ 55 --/ 60 --/ 70 host HotTemp --/ 66 --/ 69 --/ 75 host PLIM_V3_1.5V --/ -- --/ -- --/ -- host PLIM_V8_1.8V --/ -- --/ -- --/ -- host PLIM_V7_2.5V --/ -- --/ -- --/ -- host PLIM_V6_1.5V --/ -- --/ -- --/ -- host 5V --/ -- --/ -- --/ -- host 3.3V --/ -- --/ -- --/ -- host Mbus5V 4700/5300 4600/5400 4500/5500 0/5/* host InletTemp --/ 55 --/ 60 --/ 70 host HotTemp --/ 66 --/ 69 --/ 75 host PLIM_V3_1.5V --/ -- --/ -- --/ -- host PLIM_V8_1.8V --/ -- --/ -- --/ -- host PLIM_V7_2.5V --/ -- --/ -- --/ -- host PLIM_V6_1.5V --/ -- --/ -- --/ -- host 5V --/ -- --/ -- --/ -- host 3.3V --/ -- --/ -- --/ -- host Mbus5V 4700/5300 4600/5400 4500/5500 0/6/* host HotTemp --/ 66 --/ 69 --/ 75 host InletTemp --/ 55 --/ 60 --/ 70 host PLIM_V3_1.5V --/ -- --/ -- --/ -- host PLIM_V8_1.8V --/ -- --/ -- --/ -- host PLIM_V7_2.5V --/ -- --/ -- --/ -- host 3.3V --/ -- --/ -- --/ -- host Mbus5V 4700/5300 4600/5400 4500/5500 0/7/* host InletTemp --/ 55 --/ 60 --/ 70 host HotTemp --/ 66 --/ 69 --/ 75 host PLIM_V3_1.5V --/ -- --/ -- --/ -- host PLIM_V8_1.8V --/ -- --/ -- --/ -- host PLIM_V7_2.5V --/ -- --/ -- --/ -- host PLIM_V6_1.5V --/ -- --/ -- --/ -- host 5V --/ -- --/ -- --/ -- host 3.3V --/ -- --/ -- --/ -- host Mbus5V 4700/5300 4600/5400 4500/5500 0/8/* host InletTemp --/ 55 --/ 60 --/ 70 host HotTemp --/ 66 --/ 69 --/ 75 host PLIM_V3_1.5V --/ -- --/ -- --/ -- host PLIM_V8_1.8V --/ -- --/ -- --/ -- host PLIM_V7_2.5V --/ -- --/ -- --/ -- host 3.3V --/ -- --/ -- --/ -- host 5V 4800/5200 4700/5300 4600/5400 host Mbus5V 4700/5300 4600/5400 4500/5500

Voltage Information ------

R/S/I Modules Sensor Voltage (mV) Margin

0/0/* host PLIM_V4_1.6V 1612 nominal

Cisco IOS XR Getting Started Guide 8-9 Chapter 8 Managing the Router Hardware Displaying Hardware Status R3.3 Beta Draft—Cisco Confidential Information

host PLIM_V5_1.8V 1804 nominal host PLIM_V3_2.5V 2504 nominal host 3.3V 3296 nominal host 5V 5048 nominal host Mbus5V 5048 n/a 0/3/* host PLIM_V3_1.5V 1496 nominal host PLIM_V8_1.8V 1788 nominal host PLIM_V7_2.5V 2492 nominal host 3.3V 3284 nominal host 5V 5000 nominal host Mbus5V 5024 n/a 0/4/* host PLIM_V3_1.5V 1500 nominal host PLIM_V8_1.8V 1796 nominal host PLIM_V7_2.5V 2488 nominal host PLIM_V6_1.5V 1508 nominal host 5V 4976 nominal host 3.3V 3288 nominal host Mbus5V 5048 n/a 0/5/* host PLIM_V3_1.5V 1504 nominal host PLIM_V8_1.8V 1792 nominal host PLIM_V7_2.5V 2488 nominal host PLIM_V6_1.5V 1504 nominal host 5V 4976 nominal host 3.3V 3284 nominal host Mbus5V 4984 n/a 0/6/* host PLIM_V3_1.5V 1496 nominal host PLIM_V8_1.8V 1792 nominal host PLIM_V7_2.5V 2476 nominal host 3.3V 3300 nominal host Mbus5V 5016 n/a 0/7/* host PLIM_V3_1.5V 1504 nominal host PLIM_V8_1.8V 1796 nominal host PLIM_V7_2.5V 2484 nominal host PLIM_V6_1.5V 1504 nominal host 5V 4976 nominal host 3.3V 3276 nominal host Mbus5V 4984 n/a 0/8/* host PLIM_V3_1.5V 1496 nominal host PLIM_V8_1.8V 1792 nominal host PLIM_V7_2.5V 2492 nominal host 3.3V 3280 nominal host 5V 5000 nominal host Mbus5V 5024 n/a

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 syntax for the show redundancy command is: show redundancy 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

Cisco IOS XR Getting Started Guide 8-10 Chapter 8 Managing the Router Hardware RP Redundancy and Switchover R3.3 Beta Draft—Cisco Confidential Information

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 router and Cisco XR 12000 Series Router platforms. After redundancy is established, redundancy management is the same on both platforms. The following sections describe RP redundancy and switchover: • Establishing RP Redundancy on the Cisco CRS-1 Router, page 8-11 • Establishing RP Redundancy on Cisco XR 12000 Series Routers, page 8-12 • Determining the Active RP in a Redundant Pair, page 8-13 • Role of the Standby RP, page 8-13 • Summary of Redundancy Commands, page 8-13 • Automatic Switchover, page 8-14 • RP Redundancy During RP Reload, page 8-14 • Manual Switchover, page 8-14 • Communicating with a Standby RP, page 8-15 • Reloading the Active RP, page 8-16

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.

Cisco IOS XR Getting Started Guide 8-11 Chapter 8 Managing the Router Hardware RP Redundancy and Switchover R3.3 Beta Draft—Cisco Confidential Information

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 PLIM PLIM PLIM PLIM FC0 FC1 PLIM PLIM PLIM PLIM

PL0 PL1 PL2 PL3 PL4 PL5 PL6 PL7 Line card PLIM PLIM PLIM PLIM RP0 RP1 PLIM PLIM PLIM PLIM

PL PL PL PL PL PL PL8 PL9 10 11 12 13 14 15 116536 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.

Cisco IOS XR Getting Started Guide 8-12 Chapter 8 Managing the Router Hardware RP Redundancy and Switchover R3.3 Beta Draft—Cisco Confidential Information

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 first RP in a redundant pair to boot with a valid Cisco IOS XR software boot package 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: RP/0/RP1/CPU0:router#

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.

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.

Cisco IOS XR Getting Started Guide 8-13 Chapter 8 Managing the Router Hardware RP Redundancy and Switchover R3.3 Beta Draft—Cisco Confidential Information

Table 8-3 RP Redundancy Commands

Command Description show redundancy Displays the redundancy status of the RPs. This command also displays the boot and switch-over history for the RPs. redundancy switchover Forces a manual switchover to the standby RP. This command works only if the standby RP is installed and in the “ready” state. show platform 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-16 for more information.

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

Cisco IOS XR Getting Started Guide 8-14 Chapter 8 Managing the Router Hardware RP Redundancy and Switchover R3.3 Beta Draft—Cisco Confidential Information

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

Initializing DDR SDRAM...found 2048 MB Initializing ECC on bank 0 . . . Turning off data cache, using DDR for first time

Initializing NVRAM... Testing a portion of DDR SDRAM ...done Reading ID EEPROMs ... Initializing SQUID ... Initializing PCI ...

PCI0 device[1]: Vendor ID 0x10ee

Configuring MPPs ... Configuring PCMCIA slots ... --More--

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/0/CPU0:router(admin)# show redundancy Redundancy information for node 0/0/CPU0: ======Node 0/0/CPU0 is in ACTIVE role Partner node (0/1/CPU0) is in UNKNOWN role

Reload and boot info ------RP reloaded Thu Apr 21 16:48:48 2005: 4 hours, 49 minutes ago Active node booted Thu Apr 21 16:48:48 2005: 4 hours, 49 minutes ago There have been 0 switch-overs since reload

RP/0/0/CPU0:router# redundancy switchover

Switchover disallowed: Standby node is not ready.

Communicating with a Standby RP

The active RP automatically synchronizes all system software, settings, and configurations with the standby RP. Under normal operating conditions, users communicate only with the active RP, as indicated in the CLI prompt. Users do not communicate directly with the standby RP. You can connect a terminal directly to the Console port of the standby RP to 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.

Cisco IOS XR Getting Started Guide 8-15 Chapter 8 Managing the Router Hardware Reloading, Shutting Down, or Power Cycling a Node R3.3 Beta Draft—Cisco Confidential Information 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 Description hw-module location nodeID power This command must be entered in administration configuration mode and disable 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. hw-module location nodeID This command must be entered in administration configuration mode and shutdown 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 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. reload 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). See the “Reloading the Active RP” section on page 8-16 for more information. show variables boot Displays the configuration register setting for the router. • Use this command in administration EXEC mode. • 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.

Cisco IOS XR Getting Started Guide 8-16 Chapter 8 Managing the Router Hardware Reloading, Shutting Down, or Power Cycling a Node R3.3 Beta Draft—Cisco Confidential Information

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. show redundancy 2. admin 3. show variables boot 4. (Optional) config-register 0x2102 5. exit 6. reload

DETAILED STEPS

Command or Action Purpose Step 1 show redundancy Displays the RP redundancy status. • If a standby RP is in “ready” redundancy state, the reload Example: command also causes the router to gracefully fail over to RP/0/RP0/CPU0:router# show redundancy the standby RP. Step 2 admin Enters administration EXEC mode.

Example: RP/0/RP0/CPU0:router# admin Step 3 show variables boot Displays the configuration register setting. • Enter this command in administration EXEC mode. Example: • For normal operations, the configuration register setting RP/0/RP0/CPU0:router(admin)# show variables boot 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. Note For instructions on how to enter ROM Monitor bootstrap mode, see Cisco IOS XR ROM Monitor Guide.

Cisco IOS XR Getting Started Guide 8-17 Chapter 8 Managing the Router Hardware Using Controller Commands to Manage Hardware Components R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 4 config-register 0x2102 (Optional) Sets the configuration register to 0x2102. • This step is necessary only if the register is not set to Example: 0x2102 in the running configuration. RP/0/RP0/CPU0:router(admin)# config-register 0x2102 Step 5 exit Exits administration EXEC mode.

Example: RP/0/RP0/CPU0:router(admin)# exit Step 6 reload Reloads the active RP according to the configuration register setting. Example: • If the setting is 0x2102, then the RP reloads the RP/0/RP0/CPU0:router# reload Cisco IOS XR software. • If the standby RP is in “ready” redundancy state, the router fails 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.

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 node using the hw-module location nodeID power disable command in administration configuration mode.

Note These commands apply only to Cisco XR 12000 Series Routers and cannot be used to disable power for the RP from which the command is entered.

For more information on the use of these commands, see the Cisco IOS XR Interface and Hardware Component Command Reference.

Using Controller Commands to Manage Hardware Components

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

Cisco IOS XR Getting Started Guide 8-18 Chapter 8 Managing the Router Hardware Formatting Hard Drives, Flash Drives, and Other Storage Devices R3.3 Beta Draft—Cisco Confidential Information 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: [monlib-filename] [recover] Table 8-5 describes the format command syntax.

Table 8-5 format command Syntax Description

Variable Description filesystem Specifies the memory device to format, followed by a colon. The supported file systems are bootflash:, harddisk:, disk0:, and disk1:. monlib-filename (Optional) Names the ROM Monitor library file (monlib file) to use for formatting the bootflash. The default monlib file is the one bundled with the system software. Note The monlib file is used by ROMMON for accessing the file system on the medium. recover (Optional) Recovers any sector read errors on a flash disk (disk0 or disk1).

In the following example, the format command is used to format the hard disk: RP/0/RP0/CPU0:router# format harddisk:

For information on the use of these commands, see the Cisco IOS XR System Management Command Reference.

Removing and Replacing Cards

This section describes card replacement issues and procedures for the following tasks: • Removing Line Cards, MSCs, or PLIMs, page 8-20 • Replacing an MSC, page 8-21 • Replacing a Line Card or PLIM with the Same Media Type and Port Count, page 8-21 • Replacing a Line Card or PLIM with the Same Media Type and a Different Port Count, page 8-21 • Replacing a Line Card or PLIM with a Different Media Type, page 8-22 • Removing and Replacing Cisco CRS-16-FC Switch Fabric Cards, page 8-22 • Removing and Replacing Cisco CRS-8-FC/S Switch Fabric Cards, page 8-31 • Removing and Replacing CSC and SFC Cards, page 8-40 • Removing and Replacing CSFC Cards, page 8-45 • Adding a Standby PRP to a Cisco 12000 Series Router, page 8-46

Cisco IOS XR Getting Started Guide 8-19 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information 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 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 outer 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.

Cisco IOS XR Getting Started Guide 8-20 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information Replacing an MSC

When you replace an MSC, the guidelines in the “Removing Line Cards, MSCs, or PLIMs” section on page 8-20 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-20 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-20 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 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.

Cisco IOS XR Getting Started Guide 8-21 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information 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-20 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.

Tip For more information about switch fabric cards, see the hardware documentation listed in the “Related Documents” section on page xii.

Before you remove a switch fabric card, be sure to monitor the “down flags,” as noted in the Purpose column. Down flags reflect the internal status of the fabric plane. The down flag states are as follows: • P—The plane has been administratively shut down by a user. • p—The plane has been shut down by internal fabric software. • m—Multicast traffic has been shut down.

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/RP0/CPU0:router# show user group

Username: cisco

Cisco IOS XR Getting Started Guide 8-22 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

User group root-system User group cisco-support

To confirm your login status including root, use the show user all | include root command: RP/0/RP0/CPU0:router# show user all | include root

User group root-system Task: root-system : READ WRITE EXECUTE NOTIFY Task: root-lr : READ WRITE EXECUTE NOTIFY

SUMMARY STEPS

1. admin 2. show platform 3. show controllers fabric plane all 4. configure 5. controllers fabric plane plane_number shutdown 6. commit 7. end 8. show controllers fabric plane all 9. end 10. configure 11. hw-module power disable location nodeID 12. commit 13. end 14. admin 15. show platform 16. When the fabric card state changes to UNPOWERED, replace the fabric card. 17. end 18. configure 19. no hw-module power disable location nodeID 20. commit 21. end 22. admin 23. show platform 24. configure 25. no controllers fabric plane plane_number shutdown 26. commit 27. end 28. show controllers fabric plane all

Cisco IOS XR Getting Started Guide 8-23 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

DETAILED STEPS

Command or Action Purpose Step 1 admin Enters administration EXEC mode.

Example: RP/0/RP0/CPU0:router# admin Step 2 show platform Displays all cards on the router. • Allows you to identify a fabric card (identified with an Example: SM prefix). RP/0/RP0/CPU0:router(admin)# show platform • 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: RP/0/RP0/CPU0:router(admin)# configure Step 5 controllers fabric plane plane_number Shuts down the fabric plane. shutdown

Example: RP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 0 shutdown Step 6 commit Commits the target configuration to the router running configuration. Example: RP/0/RP0/CPU0:router(admin-config)# commit Step 7 end Exits administration configuration mode and returns to administration EXEC mode. Example: RP/0/RP0/CPU0:router(admin-config)# end

Cisco IOS XR Getting Started Guide 8-24 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 8 show controllers fabric plane all Displays the status of each fabric plane. • The Admin State and Oper State columns should read Example: DOWN. RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all Step 9 end Exits administration EXEC mode and returns to EXEC mode.

Example: RP/0/RP0/CPU0:router(admin)# end Step 10 configure Enters configuration mode.

Example: RP/0/RP0/CPU0:router# configure 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(config)# hw-module power disable location 0/SM0/SP Step 12 commit Commits the target configuration to the router running configuration. Example: RP/0/RP0/CPU0:router(config)# commit Step 13 end Exits configuration mode and returns to EXEC mode.

Example: RP/0/RP0/CPU0:router(config)# end Step 14 admin Enters administration EXEC mode.

Example: RP/0/RP0/CPU0:router# admin Step 15 show platform Displays the status of all cards on the router. • Check the State column for the status of the fabric card. Example: • Do not continue to the next step until the status in the RP/0/RP0/CPU0:router(admin)# show platform 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. Step 16 When the fabric card state changes to Replaces the physical card. UNPOWERED, replace the fabric card. Step 17 end Exits administration EXEC mode and returns to EXEC mode.

Example: RP/0/RP0/CPU0:router(config)# end

Cisco IOS XR Getting Started Guide 8-25 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 18 configure Enters configuration mode.

Example: RP/0/RP0/CPU0:router# configure Step 19 no hw-module power disable location nodeID Sets the target configuration to restore power to the fabric card. Example: RP/0/RP0/CPU0:router(config)# no hw-module power disable location 0/SM0/SP

Step 20 commit Commits the target configuration to the router running configuration. Example: RP/0/RP0/CPU0:router(config)# commit Step 21 end Ends the configuration session and returns to EXEC mode.

Example: RP/0/RP0/CPU0:router(config)# end Step 22 admin Enters administration EXEC mode.

Example: RP/0/RP0/CPU0:router# admin Step 23 show platform Displays the status of all cards on the router. • Check the State column for the status of the fabric card. Example: • Do not continue to the next step until the status in the RP/0/RP0/CPU0:router(admin)# show platform 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. Step 24 configure Enters administration configuration mode.

Example: RP/0/RP0/CPU0:router(admin)# configure Step 25 no controllers fabric plane plane_number Sets the target configuration to bring up the fabric plane. shutdown

Example: RP/0/RP0/CPU0:router(admin-config)# no controllers fabric plane 0 shutdown Step 26 commit Commits the target configuration to the router running configuration. Example: RP/0/RP0/CPU0:router(admin-config)# commit

Cisco IOS XR Getting Started Guide 8-26 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 27 end Exits administration configuration mode and returns to administration EXEC mode. Example: RP/0/RP0/CPU0:router(admin-config)# end Step 28 show controllers fabric plane all Displays the fabric plane status. • The Admin State and Oper State columns should read UP. Example: RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all

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, p - plane oper down

C - card admin down, c - card oper down L - link port admin down, l - linkport oper down A - asic admin down, a - asic oper down B - bundle port admin Down, b - bundle port oper down I - bundle admin down, i - bundle oper down N - node admin down, n - node down o - other end of link down d - data down f - failed component downstream m - plane multicast 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

Cisco IOS XR Getting Started Guide 8-27 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

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 5 02:15:09.265 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO WN : Plane 0 state changed to DOWN: RP/0/RP1/CPU0:Oct 5 02:15:09.319 : 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 - link port admin down, l - linkport oper down A - asic admin down, a - asic oper down B - bundle port admin Down, b - bundle port oper down I - bundle admin down, i - bundle oper down N - node admin down, n - node down 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 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)# end

RP/0/RP1/CPU0:router# configure

RP/0/RP1/CPU0:router(config)# hw-module power disable location 0/SM0/SP

RP/0/RP1/CPU0:router(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(config)# end

RP/0/RP1/CPU0:router# admin

RP/0/RP1/CPU0:router(admin)# show platform Node Type PLIM State Config State

Cisco IOS XR Getting Started Guide 8-28 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

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

When the State for the fabric card changes to UNPOWERED, replace the fabric card. RP/0/RP1/CPU0:router(admin)# end

RP/0/RP1/CPU0:router# configure

RP/0/RP1/CPU0:router(config)# no hw-module power disable location 0/SM0/SP

RP/0/RP1/CPU0:router(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.80/ sp/mbihfr-sp.vm validated

RP/0/RP1/CPU0:router(config)# end

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

Cisco IOS XR Getting Started Guide 8-29 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

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 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 - link port admin down, l - linkport oper down A - asic admin down, a - asic oper down B - bundle port admin Down, b - bundle port oper down I - bundle admin down, i - bundle oper down N - node admin down, n - node down o - other end of link down d - data down f - failed component downstream m - plane multicast down

Plane Admin Oper Id State State ------0 UP UP 1 UP UP 2 UP UP 3 UP UP

Cisco IOS XR Getting Started Guide 8-30 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

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

Tip For more information about switch fabric cards, see the hardware documentation listed in the “Related Documents” section on page xii.

Note This procedure does not apply when starting the router for the first time or after a power cycle or reload.

Prerequisites

Username: cisco User group root-system User group cisco-support

Cisco IOS XR Getting Started Guide 8-31 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

To confirm your login status including root, use the show user all | include root command: RP/0/RP0/CPU0:router# show user all | include root

User group root-system Task: root-system : READ WRITE EXECUTE NOTIFY Task: root-lr : READ WRITE EXECUTE NOTIFY

SUMMARY STEPS

1. admin 2. show platform 3. show controllers fabric plane all 4. configure 5. controllers fabric plane plane_number shutdown 6. controllers fabric plane plane_number shutdown 7. commit 8. end 9. show controllers fabric plane all 10. end 11. configure 12. hw-module power disable location nodeID 13. commit 14. end 15. admin 16. show platform 17. When the fabric card state changes to UNPOWERED, replace the fabric card. 18. end 19. configure 20. no hw-module power disable location nodeID 21. commit 22. end 23. admin 24. show platform 25. configure 26. no controllers fabric plane plane_number shutdown 27. no controllers fabric plane plane_number shutdown 28. commit 29. end 30. show controllers fabric plane all

Cisco IOS XR Getting Started Guide 8-32 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

DETAILED STEPS

Command or Action Purpose Step 1 admin Enters administration EXEC mode.

Example: RP/0/RP0/CPU0:router# admin Step 2 show platform Displays all cards on the router. • Allows you to identify a fabric card (identified with an Example: SM prefix). RP/0/RP0/CPU0:router(admin)# show platform • 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 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: RP/0/RP0/CPU0:router(admin)# configure Step 5 controllers fabric plane plane_number Shuts down one of the two fabric planes on a CRS-8-FC/S shutdown card. • Before removing a CRS-8-FC/S card, shut down both Example: planes for the fabric card. The fabric planes are assigned RP/0/RP0/CPU0:router(admin-config)# to fabric cards as follows: controllers fabric plane 0 shutdown – 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 controllers fabric plane plane_number Shuts down one of the two fabric planes on a CRS-8-FC/S shutdown card. • Shut down the companion plane to the plane shut down Example: in the previous step. RP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 1 shutdown

Cisco IOS XR Getting Started Guide 8-33 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 7 commit Commits the target configuration to the router running configuration. Example: RP/0/RP0/CPU0:router(admin-config)# commit Step 8 end Exits administration configuration mode and returns to administration EXEC mode. Example: RP/0/RP0/CPU0:router(admin-config)# end Step 9 show controllers fabric plane all Displays the status of each fabric plane. • The Admin State and Oper State columns should read Example: DOWN for both of the shutdown planes. RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all Step 10 end Exits administration EXEC mode and returns to EXEC mode.

Example: RP/0/RP0/CPU0:router(admin)# end Step 11 configure Enters configuration mode.

Example: RP/0/RP0/CPU0:router# configure Step 12 hw-module power disable location nodeID Sets the target configuration to remove power from the fabric card.

Example: RP/0/RP0/CPU0:router(config)# hw-module power disable location 0/SM0/SP Step 13 commit Commits the target configuration to the router running configuration. Example: RP/0/RP0/CPU0:router(config)# commit Step 14 end Exits configuration mode and returns to EXEC mode.

Example: RP/0/RP0/CPU0:router(config)# end Step 15 admin Enters administration EXEC mode.

Example: RP/0/RP0/CPU0:router# admin Step 16 show platform Displays the status of all cards on the router. • Check the State column for the status of the fabric card. Example: • Do not continue to the next step until the status in the RP/0/RP0/CPU0:router# show platform 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.

Cisco IOS XR Getting Started Guide 8-34 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 17 When the fabric card state changes to Replaces the physical card. UNPOWERED, replace the fabric card. Step 18 end Exits administration EXEC mode and returns to EXEC mode.

Example: RP/0/RP0/CPU0:router(admin)# end Step 19 configure Enters configuration mode.

Example: RP/0/RP0/CPU0:router# configure Step 20 no hw-module power disable location nodeID Sets the target configuration to restore power to the fabric card. Example: RP/0/RP0/CPU0:router(config)# no hw-module power disable location 0/SM0/SP

Step 21 commit Commits the target configuration to the router running configuration. Example: RP/0/RP0/CPU0:router(config)# commit Step 22 end Ends the configuration session and returns to EXEC mode.

Example: RP/0/RP0/CPU0:router(config)# end Step 23 admin Enters administration EXEC mode.

Example: RP/0/RP0/CPU0:router# admin Step 24 show platform Displays the status of all cards on the router. • Check the State column for the status of the fabric card. Example: • Do not continue to the next step until the status in the RP/0/RP0/CPU0:router(admin)# show platform 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. Step 25 configure Enters administration configuration mode.

Example: RP/0/RP0/CPU0:router(admin)# configure Step 26 no controllers fabric plane plane_number Sets the target configuration to bring up one of the two fabric shutdown planes on the card.

Example: RP/0/RP0/CPU0:router(admin-config)# no controllers fabric plane 0 shut

Cisco IOS XR Getting Started Guide 8-35 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 27 no controllers fabric plane plane_number Sets the target configuration to bring up one of the two fabric shutdown planes on the card.

Example: RP/0/RP0/CPU0:router(admin-config)# no controllers fabric plane 1 shut Step 28 commit Commits the target configuration to the router running configuration. Example: RP/0/RP0/CPU0:router(admin-config)# commit Step 29 end Exits administration configuration mode and returns to administration EXEC mode. Example: RP/0/RP0/CPU0:router(admin-config)# end Step 30 show controllers fabric plane all Displays the fabric plane status. • The Admin State and Oper State columns should read UP Example: for both fabric planes on the fabric card. RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all

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

RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all

Flags: P - plane admin down, p - plane oper down

Plane Admin Oper

Cisco IOS XR Getting Started Guide 8-36 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

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 5 02:15:09.265 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO WN : Plane 0 state changed to DOWN: RP/0/RP1/CPU0:Oct 5 02:15:09.265 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO WN : Plane 1 state changed to DOWN: RP/0/RP1/CPU0:Oct 5 02:15:09.319 : 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

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

RP/0/RP1/CPU0:router# configure

RP/0/RP1/CPU0:router(config)# hw-module power disable location 0/SM0/SP

RP/0/RP1/CPU0:router(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.

Cisco IOS XR Getting Started Guide 8-37 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

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

RP/0/RP1/CPU0:router# admin

RP/0/RP1/CPU0:router(admin)# show platform Node Type PLIM State Config State

When the State for the fabric card changes to UNPOWERED, replace the fabric card.

RP/0/RP1/CPU0:router(config)# no hw-module power disable location 0/SM0/SP

RP/0/RP1/CPU0:router(config)# commit

RP/0/RP1/CPU0:router(config)# end

RP/0/RP1/CPU0:router# admin

RP/0/RP1/CPU0:router(admin)# show platform

Node Type PLIM State Config State

RP/0/RP1/CPU0:router(admin)# show platform

Node Type PLIM State Config State

Cisco IOS XR Getting Started Guide 8-38 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

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

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

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

Plane Admin Oper Id State State ------0 UP UP 1 UP UP 2 UP UP 3 UP UP 4 UP UP

Cisco IOS XR Getting Started Guide 8-39 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

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

Username: cisco User group root-system User group cisco-support

To confirm your login status including root, use the show user all | include root command: RP/0/RP0/CPU0:router# show user all | include root

User group root-system Task: root-system : READ WRITE EXECUTE NOTIFY Task: root-lr : READ WRITE EXECUTE NOTIFY

SUMMARY STEPS

1. admin 2. show platform 3. configure 4. hw-module location slot shutdown 5. hw-module location slot power disable 6. commit 7. end 8. show platform 9. Remove and replace the CSC or SFC. 10. configure 11. no hw-module location slot power disable 12. commit

Cisco IOS XR Getting Started Guide 8-40 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

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 Purpose Step 1 admin Enters administration EXEC mode.

Example: RP/0/0/CPU0:router# admin Step 2 show platform Displays the state of all cards on the router. • Allows you to identify the CSC or SFC you want to Example: replace. RP/0/0/CPU0:router(admin)# show platform • 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. Step 3 configure 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 Caution Shut down only one CSC or SFC from the location 0/16/CPU0 shutdown 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

Cisco IOS XR Getting Started Guide 8-41 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 6 commit Commits the target configuration to the router running configuration. Example: Note You do not need to enter the end or exit command or RP/0/0/CPU0:router(admin-config)# commit press Ctrl-Z to exit administration configuration mode until the end of this procedure. If you exit administration configuration mode, you must reenter this mode to complete the procedure. Step 7 end Exits administration configuration mode and returns to administration EXEC mode. Example: RP/0/RP0/CPU0:router(admin-config)# end Step 8 show platform (Optional) Displays the state of all cards on the router. • Allows you to verify that the CSC or SFC you want to Example: replace is shut down and the power is off. RP/0/0/CPU0:router(admin)# show platform Step 9 Remove and replace the CSC or SFC. Replaces the physical card. Step 10 configure Enters administration configuration mode.

Example: RP/0/0/CPU0:router(admin)# configure 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 Step 12 commit Commits the target configuration to the router running configuration. Example: RP/0/0/CPU0:router(admin-config)# commit Step 13 end Exits administration configuration mode and returns to administration EXEC mode. Example: RP/0/RP0/CPU0:router(admin-config)# end Step 14 show platform (Optional) Displays the state of all cards on the router. • Allows you to verify that the replacement CSC or SFC Example: has power on. RP/0/0/CPU0:router(admin)# show platform

Cisco IOS XR Getting Started Guide 8-42 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

Command or Action Purpose Step 15 configure Enters administration configuration mode.

Example: RP/0/0/CPU0:router(admin)# configure 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 Commits the target configuration to the router running configuration. Example: RP/0/0/CPU0:router(admin-config)# commit Step 18 end Exits administration configuration mode and returns to administration EXEC mode. Example: RP/0/RP0/CPU0:router(admin-config)# end Step 19 show platform (Optional) Displays the state of all cards on the router. • Allows you to verify that the replacement CSC or SFC Example: has power and has been brought up. RP/0/0/CPU0:router(admin)# show platform

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

Cisco IOS XR Getting Started Guide 8-43 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

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

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

Cisco IOS XR Getting Started Guide 8-44 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

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

RP/0/0/CPU0:router(admin-config)# commit

RP/0/0/CPU0:router(admin-config)# end

RP/0/0/CPU0:router(admin)# show platform

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

Cisco IOS XR Getting Started Guide 8-45 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information 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 xii 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 • 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-1 ships with 512 MB, and 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 512MB Sandisk flash disk in PCMCIA slot 0 and slot 1. The minimum requirement is one 512MB 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 theCisco 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. On the standby PRP: a. Attach a terminal to the console port, and place the PRP in ROM Monitor mode. b. unset TURBOBOOT c. unset BOOT d. sync e. boot tftp://server/directory/filename 2. Wait for boot process to complete.

Cisco IOS XR Getting Started Guide 8-46 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

3. On the active PRP: a. show platform b. show redundancy

DETAILED STEPS

Command or Action Purpose Step 1 On the standby PRP, attach a terminal to the Refer to Cisco IOS XR ROM Monitor Guide for more console port, and place the PRP in ROM Monitor information. mode. Step 2 unset TURBOBOOT Clears the TURBOBOOT variable. The TURBOBOOT variable is only used on the DSC. 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 Step 5 boot tftp://server/directory/filename 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. Step 7 On the active PRP: Displays the standby PRP card in the screen output. show platform

Example: RP/0/0/CPU0:router# show platform Step 8 On the active PRP: Displays the redundancy status of the standby PRP card. show redundancy

Example: RP/0/0/CPU0:router# show redundancy

Cisco IOS XR Getting Started Guide 8-47 Chapter 8 Managing the Router Hardware Removing and Replacing Cards R3.3 Beta Draft—Cisco Confidential Information

Cisco IOS XR Getting Started Guide 8-48 R3.3 Beta Draft—Cisco Confidential Information

CHAPTER 9

Troubleshooting the Cisco IOS XR Software

Beta Draft Cisco Confidential Information

This chapter describes the tools and procedures used to identify the source of hardware and software problems. This information can be used to resolve an issue or see more specific troubleshooting guides for help on a specific topic. This chapter also provides instructions on gathering data for further analysis by Cisco customer support representatives.

Contents

This chapter contains the following sections: • Additional Sources for Information, page 9-1 • Basic Troubleshooting Commands, page 9-2 • Understanding Processes and Threads, page 9-7 • Configuration Error Messages, page 9-14 • Memory Warnings in Configuration Sessions, page 9-15 • 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 xii.

Cisco IOS XR Getting Started Guide 9-1 Chapter 9 Troubleshooting the Cisco IOS XR Software Basic Troubleshooting Commands R3.3 Beta Draft—Cisco Confidential Information 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-3 • Using the traceroute Command, page 9-3 • Using debug Commands, page 9-4

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. All show commands (except show configuration) are entered in EXEC mode. 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. Table 9-1 Common show Commands in Cisco IOS XR Software

Command Description show variables boot Displays the boot variables. Note This command must be entered in administration EXEC mode. show configuration Displays the uncommitted configuration changes made during a configuration session. This command can be entered in any configuration mode. show context (and show exception) Displays context information about all recent reloads. show controller Displays hardware controller information. show debug Displays debug flags enabled from the current terminal. show environment [all | fans | leds | Displays hardware information for the physical components and systems, including power-supply | table | temperatures fans, LEDs, power supply voltage and current information, and temperatures. | voltages | l] show exception Displays all exception dump configurations. show install Displays installed and active software packages. show interfaces Displays interface status and configuration. show logging Displays the contents of logging buffers. show memory Displays memory statistics. show platform Displays information about node status on the router. To display the nodes assigned to an SDR, enter this command in EXEC mode. To display all the nodes in a router, enter this command in administration EXEC mode. show process blocked Displays blocked processes. show redundancy Display the status of the primary (active) route processor (RP) and the standby (redundant) RP. show running-config [command] Displays the current running configuration. This command can be entered in either configuration or EXEC mode.

Cisco IOS XR Getting Started Guide 9-2 Chapter 9 Troubleshooting the Cisco IOS XR Software Basic Troubleshooting Commands R3.3 Beta Draft—Cisco Confidential Information

Table 9-1 Common show Commands in Cisco IOS XR Software (continued)

Command Description show tech-support Collects a large amount of system information for troubleshooting. The output should be provided to technical support representatives when a problem is reported. Because of the impact the command can have on a running system, it is reserved for users assigned to the cisco-support task ID. show tracebacks Allows you to get a dump of all unsolicited debug messages that contained traceback information (that is, a list of program counters back from the line of code generating the message) along with the dynamic link library (DLL) information necessary to decode the traceback. show user [group | tasks | all] Displays the username for the current logged-in user. Use this command to also display the groups and associated task IDs assigned to the account. show version Displays basic system information.

Using the ping Command

Use the ping command to diagnose network connectivity. Enter a hostname or an IP address as an argument to this command. The ping command sends an echo request packet to an address, then awaits a reply. Ping output can help you evaluate path-to-host reliability, delays over the path, and whether the host 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 following 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)

Using the traceroute Command

Use the traceroute command 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.

Cisco IOS XR Getting Started Guide 9-3 Chapter 9 Troubleshooting the Cisco IOS XR Software Basic Troubleshooting Commands R3.3 Beta Draft—Cisco Confidential Information

This command works by taking advantage of the error messages generated by routers when a datagram exceeds its time-to-live (TTL) value. 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 172.25.0.2 11 msec 2 msec 1 msec 2 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-5 • Enabling Debugging for a Feature, page 9-5 • Disabling Debugging for a Service, page 9-6 • Displaying Debugging Status, page 9-5

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.

Cisco IOS XR Getting Started Guide 9-4 Chapter 9 Troubleshooting the Cisco IOS XR Software Basic Troubleshooting Commands R3.3 Beta Draft—Cisco Confidential Information

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. For example: RP/0/RP0/CPU0:router# debug RP/0/RP0/CPU0:router(debug)# ?

aaa AAA Authentication, Authorization and Accounting adjacency Adjacency debug adjacency platform AIB information aib AIB information alarm-logger Turn on alarm debugging arm IP Address Repository Manager arp IP ARP transactions asic-errors Debug ASIC erors asic-scan Debug Asic Scan --More--

Enabling Debugging for a Feature

To enable debugging for a feature, enter the debug command 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

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.

Cisco IOS XR Getting Started Guide 9-5 Chapter 9 Troubleshooting the Cisco IOS XR Software Basic Troubleshooting Commands R3.3 Beta Draft—Cisco Confidential Information

Enter the show debug condition 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

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

Cisco IOS XR Getting Started Guide 9-6 Chapter 9 Troubleshooting the Cisco IOS XR Software Understanding Processes and Threads R3.3 Beta Draft—Cisco Confidential Information 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 CLI Syntax Description Process • Process name 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. 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 Multiple instances of a process can run simultaneously on a node. • job-ID 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 A “thread” is a unit of execution within a process. • thread-ID 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.

Cisco IOS XR Getting Started Guide 9-7 Chapter 9 Troubleshooting the Cisco IOS XR Software Understanding Processes and Threads R3.3 Beta Draft—Cisco Confidential Information

Figure 9-1 Modular Process Architecture in Cisco IOS XR Software

"Message passing bus” Processes OS

etc... Microkernel

Processes Process manager 116545

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 Description monitor processes 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). monitor threads Displays interactive, auto-updating process and thread statistics in a full-screen mode. show processes Displays information about active processes. show processes abort Displays process aborts. show processes blocked Displays details for reply, send, and mutually exclusive (mutex) blocked processes. show processes boot Displays process boot information. show processes cpu Displays CPU use for each process. show processes dynamic Displays process data for dynamically created processes. show processes failover Displays process automatic switchover information. show processes log Displays the process log.

Cisco IOS XR Getting Started Guide 9-8 Chapter 9 Troubleshooting the Cisco IOS XR Software Understanding Processes and Threads R3.3 Beta Draft—Cisco Confidential Information

Table 9-3 Commands to Display Process and Thread Information (continued)

Command Description show processes memory Shows memory use for each process. show processes startup 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-9 • show processes process-name Command, page 9-10 • show processes memory Command, page 9-11 • monitor processes Command, page 9-12 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 mode. Table 9-4 describes the column heading output.

Table 9-4 Column Heading Descriptions for show processes Output

Output Heading Description JID 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). 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. LastCPU CPU number on which the process was last running. The value is 0 or 1. For a single processor node, the value is 0. Stack Size of the memory stack of the process. pri Process priority. state Process state. HR:MM:SS:MSEC Time the process has run since starting. NAME Process name.

Cisco IOS XR Getting Started Guide 9-9 Chapter 9 Troubleshooting the Cisco IOS XR Software Understanding Processes and Threads R3.3 Beta Draft—Cisco Confidential Information

The following is sample output from the show processes command: RP/0/RP0/CPU0:router# show processes

JID TID LastCPU Stack pri state HR:MM:SS:MSEC NAME 1 1 0 0K 0 Ready 1:57:41:0542 procnto-600-smp-cisco-instr 1 2 1 0K 0 Running 1:57:37:0022 procnto-600-smp-cisco-instr 1 3 1 0K 10 Receive 0:00:05:0723 procnto-600-smp-cisco-instr 1 4 1 0K 10 Receive 0:00:00:0001 procnto-600-smp-cisco-instr 1 5 0 0K 63 Receive 0:00:00:0000 procnto-600-smp-cisco-instr 1 6 1 0K 63 Receive 0:00:00:0000 procnto-600-smp-cisco-instr 1 7 0 0K 63 Receive 0:00:00:0000 procnto-600-smp-cisco-instr 1 8 0 0K 10 Receive 0:00:01:0885 procnto-600-smp-cisco-instr 1 9 1 0K 10 Receive 0:00:03:0416 procnto-600-smp-cisco-instr 1 10 1 0K 10 Receive 0:00:00:0001 procnto-600-smp-cisco-instr 1 11 1 0K 10 Receive 0:00:04:0861 procnto-600-smp-cisco-instr 1 15 0 0K 10 Receive 0:00:02:0020 procnto-600-smp-cisco-instr 1 18 1 0K 10 Receive 0:00:03:0278 procnto-600-smp-cisco-instr 1 20 1 0K 10 Receive 0:00:00:0732 procnto-600-smp-cisco-instr 1 21 1 0K 10 Receive 0:00:02:0692 procnto-600-smp-cisco-instr 1 22 0 0K 10 Running 0:00:03:0788 procnto-600-smp-cisco-instr 1 23 1 0K 10 Receive 0:00:11:0785 procnto-600-smp-cisco-instr 1 25 0 0K 10 Receive 0:00:04:0037 procnto-600-smp-cisco-instr --More-- 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 Description JID Job ID—This 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 Process ID—This changes when process is restarted. Executable path Path for the process executable. Instance 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). Version ID API version. Respawn ON or OFF—Determines if this process restarts automatically in case of failure. Respawn count Number of times this process has been (re)started (that is, the first start makes this count 1). Max. spawns per minute Number of respawns not to be exceeded in 1 minute. If this number is exceeded, stop restarting. Last started Date and time the process was last started. Process state Current state of the process. Started on config Configuration command that started (or would start) this process.

Cisco IOS XR Getting Started Guide 9-10 Chapter 9 Troubleshooting the Cisco IOS XR Software Understanding Processes and Threads R3.3 Beta Draft—Cisco Confidential Information

Table 9-5 Heading Descriptions for show processes process-name Output (continued)

Output Heading Description core Memory segments to include in a core file. Max. core Number of times to dump a core file—0 = infinity.

The following is sample output from the show processes command: RP/0/RP0/CPU0:router# show processes ospf

Job Id: 261 PID: 139453 Executable path: /hfr-rout-0.44.0/bin/ospf Instance #: 1 Version ID: 00.00.0000 Respawn: ON Respawn count: 1 Max. spawns per minute: 12 Last started: Wed Mar 17 07:46:26 2004 Process state: Run Package state: Normal Started on config: cfg/gl/ipv4-ospf/proc/100/ord_a/routerid core: TEXT SHAREDMEM MAINMEM Max. core: 0 Mandatory: ON Placement: ON startup_path: /pkg/startup/ospf.startup Process cpu time: 0.410 user, 0.183 kernel, 0.593 total JID TID LastCPU Stack pri state HR:MM:SS:MSEC NAME 261 1 0 40K 10 Receive 0:00:00:0397 ospf 261 2 1 40K 10 Receive 0:00:00:0003 ospf 261 3 0 40K 10 Receive 0:00:00:0007 ospf 261 4 1 40K 10 Condvar 0:00:00:0000 ospf --More-- 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 Description JID 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). Text Size of text region (process executable). Data Size of data region (initialized and uninitialized variables). Stack Size of process stack. Dynamic Size of dynamically allocated memory. Process Process name.

Cisco IOS XR Getting Started Guide 9-11 Chapter 9 Troubleshooting the Cisco IOS XR Software Understanding Processes and Threads R3.3 Beta Draft—Cisco Confidential Information

The following is sample output from the show processes memory command: RP/0/RP0/CPU0:router# show processes memory

JID Text Data Stack Dynamic Process 55 28672 4096 69632 17072128 eth_server 164 143360 4096 20480 13238272 hfr_fgid_server 317 167936 4096 45056 10526720 syslogd 122 512000 4096 77824 9797632 bgp 265 57344 4096 57344 5877760 parser_server 254 40960 4096 143360 3084288 netio 63 8192 4096 24576 2314240 nvram 314 4096 4096 36864 1699840 sysdb_svr_local 341 495616 4096 40960 1576960 wdsysmon 259 53248 4096 28672 1490944 nvgen_server 189 32768 4096 32768 1425408 hd_drv 69 77824 4096 110592 1421312 qnet 348 323584 4096 40960 1392640 ospf 347 323584 4096 40960 1392640 ospf 346 323584 4096 40960 1392640 ospf 345 323584 4096 40960 1392640 ospf 344 323584 4096 40960 1392640 ospf 261 323584 4096 40960 1392640 ospf --More-- 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 Description JID 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). TIDS 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. Chans Channels (client connections) to the server. FDs Number of files open. Tmrs Number of timers for the process. MEM Total memory of the process. HH:MM:SS Run time of process since last restart. CPU Percentage of CPU used by process thread. NAME Process name.

Cisco IOS XR Getting Started Guide 9-12 Chapter 9 Troubleshooting the Cisco IOS XR Software Understanding Processes and Threads R3.3 Beta Draft—Cisco Confidential Information

The following is sample output from the monitor processes command: RP/0/RP0/CPU0:router# monitor processes

195 processes; 628 threads; 3300 channels, 4579 fds CPU states: 47.6% idle, 1.2% user, 51.1% kernel Memory: 2048M total, 1576M avail, page size 4K

JID TIDS Chans FDs Tmrs MEM HH:MM:SS CPU NAME 1 27 198 8 1 0 5:53:31 51.11% kernel 52 5 215 44 5 228K 0:00:02 0.52% devc-conaux 342 4 195 14 6 1M 0:00:08 0.34% wdsysmon 495806 1 1 10 0 648K 0:00:00 0.16% ptop 293 7 31 39 11 352K 0:00:09 0.07% shelfmgr 55 11 24 14 5 16M 0:00:29 0.06% eth_server 121 3 10 8 2 564K 0:00:05 0.02% bcm_process 311 4 7 18 4 216K 0:00:02 0.01% sysdb_medusa_s 138 4 14 40 5 240K 0:00:01 0.01% devc-vty 265 5 31 19 4 204K 0:00:09 0.01% packet

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 ? Displays or prints the interactive commands. q Quits the monitor processes display and returns to the system prompt. n Changes the number of processes to be displayed. d Changes the delay interval between updates. k Kills a process. l Refreshes the screen. t Sorts the display by time (default). m Sorts the display by memory used. c Sorts the display by number of open channels. f 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. 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.

Cisco IOS XR Getting Started Guide 9-13 Chapter 9 Troubleshooting the Cisco IOS XR Software Configuration Error Messages R3.3 Beta Draft—Cisco Confidential Information

Table 9-9 Commands to Manage Processes

Command Description process {kill | restart | start} Manually stops, starts, or restarts a process or process instance. process mandatory {on | off} Changes the mandatory setting for a process. process mandatory reboot {enable | disable} 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-14 • Configuration Errors at Startup, page 9-15

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

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 !

Cisco IOS XR Getting Started Guide 9-14 Chapter 9 Troubleshooting the Cisco IOS XR Software Memory Warnings in Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information

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-16 • Displaying System Memory Information, page 9-17 • Removing Configurations to Resolve Low-Memory Warnings, page 9-18 • Contacting TAC for Additional Assistance, page 9-21

Cisco IOS XR Getting Started Guide 9-15 Chapter 9 Troubleshooting the Cisco IOS XR Software Memory Warnings in Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information 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-18. 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.

Cisco IOS XR Getting Started Guide 9-16 Chapter 9 Troubleshooting the Cisco IOS XR Software Memory Warnings in Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information 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 What 000d2000 12288 Program Stack 00112000 12288 Program Stack Total Allocated Memory: 0 Total Shared Memory: 0

pkg/bin/wd-mbi: jid 72 Address Bytes What 4817f000 4096 Program Stack (pages not allocated) 48180000 516096 Program Stack (pages not allocated) 481fe000 8192 Program Stack 48200000 8192 Program Text --More--

Table 9-10 Heading Descriptions for show memory Command Output

Heading Description Physical Memory Amount of physical memory installed on the device. Application Memory Memory available for the system to use (total memory minus image size, reserved, IOMem, and flashfsys). Image Size of the bootable image. Reserved Reserved for packet memory. IOMem IO memory—Currently used as a backup for packet memory. flashfsys Flash file system memory. Process and JID Process and job ID. Address Starting address in memory. Bytes Size of memory block. What Block description.

Cisco IOS XR Getting Started Guide 9-17 Chapter 9 Troubleshooting the Cisco IOS XR Software Memory Warnings in Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information 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-18 • Removing Committed Configurations to Free System Memory, page 9-18 • 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 mode to see if a large configuration forced the router over the limit.

Cisco IOS XR Getting Started Guide 9-18 Chapter 9 Troubleshooting the Cisco IOS XR Software Memory Warnings in Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information

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. Label/ID User Line Client Time Stamp ~~~~ ~~~~~~~~ ~~~~ ~~~~ ~~~~~~ ~~~~~~~~~~ 1 1000000144 user vty0 CLI 00:16:51 UTC Thu Dec 11 2003 2 1000000143 user vty0 CLI 00:04:32 UTC Thu Dec 11 2003 3 1000000142 user 0.0.0.0 XMLAgent 21:58:36 UTC Wed Dec 10 2003 4 1000000141 user 0.0.0.0 XMLAgent 21:46:07 UTC Wed Dec 10 2003 5 1000000140 cisco con0_RP1_C CLI 21:43:30 UTC Wed Dec 10 2003 6 1000000139 user 0.0.0.0 XMLAgent 21:40:13 UTC Wed Dec 10 2003 7 1000000138 user 0.0.0.0 XMLAgent 21:34:48 UTC Wed Dec 10 2003 8 1000000137 cisco con0_RP1_C CLI 21:32:10 UTC Wed Dec 10 2003 9 1000000136 user 0.0.0.0 XMLAgent 21:30:13 UTC Wed Dec 10 2003 10 1000000135 cisco con0_RP1_C CLI 19:45:04 UTC Wed Dec 10 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.

Cisco IOS XR Getting Started Guide 9-19 Chapter 9 Troubleshooting the Cisco IOS XR Software Memory Warnings in Configuration Sessions R3.3 Beta Draft—Cisco Confidential Information

Rolling Back to a Previously Committed Configuration

You can roll back the system to a previous committed configuration, as shown in the following procedure:

Step 1 Enter the show configuration commit list command to display the commitIDs available for rollback: RP/0/RP0/CPU0:router# show configuration commit list

SNo. Label/ID User Line Client Time Stamp ~~~~ ~~~~~~~~ ~~~~ ~~~~ ~~~~~~ ~~~~~~~~~~ 1 1000000391 user_a con0_33_1 CLI 19:29:18 UTC Wed Dec 10 2003 2 1000000390 user_a con0_33_1 CLI 19:29:16 UTC Wed Dec 10 2003 3 1000000389 user_a con0_33_1 CLI 19:29:15 UTC Wed Dec 10 2003 4 1000000388 user_a con0_33_1 CLI 19:29:12 UTC Wed Dec 10 2003 5 1000000387 user_a con0_33_1 CLI 19:26:16 UTC Wed Dec 10 2003 6 1000000386 user_a con0_32_1 CLI 19:18:38 UTC Wed Dec 10 2003 7 1000000385 user_a con0_33_1 CLI 19:14:09 UTC Wed Dec 10 2003 8 1000000384 user_a con0_33_1 CLI 19:13:58 UTC Wed Dec 10 2003 9 1000000383 user_a con0_33_1 CLI 19:13:33 UTC Wed Dec 10 2003 10 1000000382 user_a con0_33_1 CLI 19:12:50 UTC Wed Dec 10 2003

Step 2 Enter the show configuration rollback changes to commit-id command to display the details of a specific commit ID: RP/0/RP0/CPU0:router# show configuration rollback changes to 1000000373

Building configuration... interface Loopback2 no description no ipv4 address 10.0.5.1 255.0.0.0

Step 3 Roll back the configuration with the rollback configuration to commitId command: RP/0/RP0/CPU0:router# rollback configuration to 1000000325

Configuration successfully rolled back to ’1000000325’. RP/0/RP0/CPU0:router#

For more information, see 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).

Table 9-11 Session Commands

Command Description show configuration sessions Displays the active configuration sessions. clear configuration sessions session-id Clears a configuration session.

Cisco IOS XR Getting Started Guide 9-20 Chapter 9 Troubleshooting the Cisco IOS XR Software Interfaces Not Coming Up R3.3 Beta Draft—Cisco Confidential Information

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 Line User Date Lock 00000211-002c409b-00000000 con0_RP1_CPU0 UNKNOWN Mon Feb 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 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 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 Description show interface Displays detailed information about all interfaces installed or configured on the device, whether or not they are operational. show interface type instance Specifies a particular interface, rather than displaying information for all interfaces, as in the following example: show interface POS0/1/0/0 show ipv4 interface Displays basic, IP-related information for all available interfaces. show ipv4 interface brief Quickly displays the most critical information about the interfaces, including the interface status (up or down) and the IPv4 protocol status.

Cisco IOS XR Getting Started Guide 9-21 Chapter 9 Troubleshooting the Cisco IOS XR Software Interfaces Not Coming Up R3.3 Beta Draft—Cisco Confidential Information 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.

Step 2 Enter the show ipv4 interface brief command to verify IP address configuration and protocol status: RP/0/RP0/CPU0:router# show ipv4 interface brief

Interface IP-Address Status Protocol POS0/1/0/0 unassigned Shutdown Down POS0/1/0/1 unassigned Shutdown Down POS0/1/0/2 unassigned Shutdown Down POS0/1/0/3 unassigned Shutdown Down POS0/1/0/4 unassigned Shutdown Down POS0/1/0/5 unassigned Shutdown Down POS0/1/0/6 unassigned Shutdown Down POS0/1/0/7 unassigned Shutdown Down POS0/1/0/8 unassigned Shutdown Down POS0/1/0/9 unassigned Shutdown Down POS0/1/0/10 unassigned Shutdown Down POS0/1/0/11 unassigned Shutdown Down POS0/1/0/12 unassigned Shutdown Down POS0/1/0/13 unassigned Shutdown Down POS0/1/0/14 unassigned Shutdown Down POS0/1/0/15 unassigned Shutdown Down POS0/2/0/0 10.10.1.101 Down Down POS0/2/0/1 unassigned Shutdown Down POS0/2/0/2 unassigned Shutdown Down POS0/2/0/3 unassigned Shutdown Down TenGigE0/3/0/0 unassigned Shutdown Down TenGigE0/3/0/2 unassigned Shutdown Down MgmtEth0/RP0/CPU0/0 unassigned Shutdown Down

Cisco IOS XR Getting Started Guide 9-22 Chapter 9 Troubleshooting the Cisco IOS XR Software Interfaces Not Coming Up R3.3 Beta Draft—Cisco Confidential Information

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 IP-Address Status Protocol POS0/1/0/0 unassigned Shutdown Down POS0/1/0/1 unassigned Shutdown Down POS0/1/0/2 unassigned Shutdown Down POS0/1/0/3 unassigned Shutdown Down POS0/1/0/4 unassigned Shutdown Down POS0/1/0/5 unassigned Shutdown Down POS0/1/0/6 unassigned Shutdown Down POS0/1/0/7 unassigned Shutdown Down POS0/1/0/8 unassigned Shutdown Down POS0/1/0/9 unassigned Shutdown Down POS0/1/0/10 unassigned Shutdown Down POS0/1/0/11 unassigned Shutdown Down POS0/1/0/12 unassigned Shutdown Down POS0/1/0/13 unassigned Shutdown Down POS0/1/0/14 unassigned Shutdown Down POS0/1/0/15 unassigned Shutdown Down POS0/2/0/0 10.10.1.101 Up Up POS0/2/0/1 10.1.1.1 Up Up POS0/2/0/3 10.1.1.2 Shutdown Down POS0/2/0/3 unassigned Shutdown Down TenGigE0/3/0/0 unassigned Shutdown Down TenGigE0/3/0/2 unassigned Shutdown Down MgmtEth0/RP0/CPU0/0 unassigned Shutdown Down

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 interface POS0/2/0/3

interface pos0/2/0/3 shutdown keepalive disable !

Cisco IOS XR Getting Started Guide 9-23 Chapter 9 Troubleshooting the Cisco IOS XR Software Interfaces Not Coming Up R3.3 Beta Draft—Cisco Confidential Information

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-4- ALARM : SONET0_1_1_0: SLOS

Step 7 Verify again that the interface is up by entering the show ipv4 interface brief command: RP/0/RP0/CPU0:router# show ipv4 interface brief

Interface IP-Address Status Protocol POS0/1/0/0 unassigned Shutdown Down POS0/1/0/1 unassigned Shutdown Down POS0/1/0/2 unassigned Shutdown Down POS0/1/0/3 unassigned Shutdown Down POS0/1/0/4 unassigned Shutdown Down POS0/1/0/5 unassigned Shutdown Down POS0/1/0/6 unassigned Shutdown Down POS0/1/0/7 unassigned Shutdown Down POS0/1/0/8 unassigned Shutdown Down POS0/1/0/9 unassigned Shutdown Down POS0/1/0/10 unassigned Shutdown Down POS0/1/0/11 unassigned Shutdown Down POS0/1/0/12 unassigned Shutdown Down POS0/1/0/13 unassigned Shutdown Down POS0/1/0/14 unassigned Shutdown Down POS0/1/0/15 unassigned Shutdown Down POS0/2/0/0 10.10.1.101 Up Up POS0/2/0/1 10.1.1.1 Up Up POS0/2/0/2 10.1.1.2 Up Up POS0/2/0/3 unassigned Shutdown Down TenGigE0/3/0/0 unassigned Shutdown Down TenGigE0/3/0/2 unassigned Shutdown Down MgmtEth0/RP0/CPU0/0 unassigned Shutdown Down

Step 8 Repeat these steps for every interface, until every interface shows both Status and Protocol as “Up.”

Cisco IOS XR Getting Started Guide 9-24 R3.3 Beta Draft—Cisco Confidential Information

APPENDIX A

Understanding Regular Expressions, Special Characters, and Patterns

Beta Draft Cisco Confidential Information

This appendix describes the regular expressions, special or wildcard characters, and patterns that can be used with filters to search through command output. The filter commands are described in the “Filtering show Command Output” section on page 6-9. The following sections describe features you can use with filters: • Regular Expressions, page A-1 • Special Characters, page A-2 • Character Pattern Ranges, page A-2 • Multiple-Character Patterns, page A-3 • Complex Regular Expressions Using Multipliers, page A-3 • Pattern Alternation, page A-4 • Anchor Characters, page A-4 • Underscore Wildcard, page A-4 • Parentheses Used for Pattern Recall, page A-4

Regular Expressions

A regular expression is a pattern (a phrase, number, or more complex pattern): • Regular expressions are case sensitive and allow for complex matching requirements. Simple regular expressions include entries like Serial, misses, or 138. • Complex regular expressions include entries like 00210... , ( is ), or [Oo]utput. A regular expression can be a single-character pattern or multiple-character pattern. That is, a regular expression can be a single character that matches the same single character in the command output or multiple characters that match the same multiple characters in the command output. The pattern in the command output is referred to as a string. The simplest regular expression is a single character that matches the same single character in the command output. Letter (A–Z and a–z), digits (0–9), and other keyboard characters (such as ! or ~) can be used as a single-character pattern.

Cisco IOS XR Getting Started Guide A-1 Appendix A Understanding Regular Expressions, Special Characters, and Patterns Special Characters R3.3 Beta Draft—Cisco Confidential Information 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 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. _ (underscore) 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: [a–dA–D] To add a dash as a single-character pattern in the search range, include another dash and precede it with a backslash: [a–dA–D\–] A bracket (]) can also be included as a single-character pattern in the range: [a–dA–D\–\]] 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: [^a–dqsv] The following example matches anything except a right square bracket (]) or the letter d: [^\]d]

Cisco IOS XR Getting Started Guide A-2 Appendix A Understanding Regular Expressions, Special Characters, and Patterns Multiple-Character Patterns R3.3 Beta Draft—Cisco Confidential Information 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])+

Cisco IOS XR Getting Started Guide A-3 Appendix A Understanding Regular Expressions, Special Characters, and Patterns Pattern Alternation R3.3 Beta Draft—Cisco Confidential Information

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.

Cisco IOS XR Getting Started Guide A-4 Appendix A Understanding Regular Expressions, Special Characters, and Patterns Parentheses Used for Pattern Recall R3.3 Beta Draft—Cisco Confidential Information

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.

Cisco IOS XR Getting Started Guide A-5 Appendix A Understanding Regular Expressions, Special Characters, and Patterns Parentheses Used for Pattern Recall R3.3 Beta Draft—Cisco Confidential Information

Cisco IOS XR Getting Started Guide A-6 R3.3 Beta Draft—Cisco Confidential Information

GLOSSARY

AAA authentication, authorization, and accounting. A network security service that provides the primary framework to set up access control on a Cisco CRS-1 router or access server. AAA is an architectural framework and modular means of configuring three independent but closely related security functions in a consistent manner.

ACL access control list. A list kept by routers to control access to or from the router for a number of services (for example, to prevent packets with a certain IP address from leaving a particular interface on the router). active Denotes a card or process that performs a system task; in a redundant configuration, there is an inactive standby card or process available to become active. Active cards or processes are also sometimes denoted as primary. active RP The RP that is active in a redundant pair of RPs. active software The software configuration marked as active for a node. configuration active software set The set of Cisco IOS XR software packages activated in one or more nodes in a router. algorithm A well-defined rule or process for arriving at a solution to a problem. In networking, algorithms commonly are used to determine the best route for traffic from a particular source to a particular destination.

APS automatic protection switching. A method that allows transmission equipment to recover automatically from failures, such as a cut cable.

ASIC application-specific integrated circuit. A chip designed for use in a specific hardware device. An ASIC is a chip designed for a special application, such as a particular kind of transmission protocol.

B bandwidth The amount of data that can be sent in a fixed amount of time. For digital devices, the bandwidth is usually expressed in bits per second (Bps) or bytes per second.

BGP Border Gateway Protocol. A routing protocol used between autonomous systems. It is the routing protocol that makes the internet work. BGP is a distance-vector routing protocol that carries connectivity information and an additional set of BGP attributes. These attributes allow for a rich set of policies for deciding the best route to use to reach a given destination.

Cisco IOS XR Getting Started Guide GL-1 Glossary

R3.3 Beta Draft—Cisco Confidential Information

C card type The type of the card inserted in a slot.

CDP Cisco Discovery Protocol. CDP runs on all Cisco devices so that these devices can learn about neighboring devices and exchange information. CDP uses a well-known multicast MAC address. During system initialization, the application-specific integrated circuit (ASIC) is configured to forward these packets to the Cisco IOS XR software CPU, which processes the packets.

Cisco.com The Cisco website

CLI command-line interface. A text-based user interface to an operating system. A command-line interface is a user interface to a computer operating system or an application in which the user responds to a visual prompt by typing a command on a specified line, receives a response from the system, and then enters another command, and so forth. Typically, most of the UNIX-based systems today offer both a command-line interface and graphical user interface (GUI). See also GUI. committed/saved The configuration stored in the system for a particular node. The RP loads the committed configuration software into memory at startup. configuration configuration In Cisco routers, a 16-bit, user-configurable value that determines how the router functions during register initialization. The configuration register can be stored in hardware or software. In hardware, the bit position is set using a jumper. In software, the bit position is set by specifying a hexadecimal value using configuration commands. A hexadecimal or decimal value that represents the 16-bit configuration register value that you want to use the next time the router is restarted. The value range is from 0x0 to 0xFFFF (0 to 65535 in decimal). control plane The control plane oversees the operation of the data plane, allocating resources, providing information, and handling errors to allow data plane operations to be continuous and efficient.

CORBA Common Object Request Broker Architecture. Specification that provides the standard interface definition between OMG-compliant objects. CORBA allows applications to communicate with one another no matter where they are located or who has designed them.

CoS class of service. An indication of how an upper-layer protocol requires a lower-layer protocol to treat its messages. In SNA subarea routing, CoS definitions are used by subarea nodes to determine the optimal route to establish a given session. A CoS definition comprises a virtual route number and transmission priority field. Repetitive, regularly timed signals are used to control synchronous processes.

CWI Craft Works Interface. Graphical user interface (GUI) used to configure and operate a router. The CWI client runs in a web browser.

DDTS distributed defect tracking system. A method to track software errors and resolutions.

DHCP Dynamic Host Configuration Protocol. Provides a mechanism for allocating IP addresses dynamically so that addresses can be reused when hosts no longer need them.

Cisco IOS XR Getting Started Guide GL-2 Glossary

R3.3 Beta Draft—Cisco Confidential Information

DIMM dual in-line memory module. Small circuit boards carrying memory integrated circuits, with signal and power pins on both sides of the board, in contrast to single-in-line memory modules (SIMMs). disk0 Name of the flash disk on which the Cisco IOS XR software is stored. disk1 Name of the optional flash disk on which the Cisco IOS XR software can be stored in preparation for installation or upgrade.

DNS Domain Name System. Mechanism used in the Internet and on private intranets for translating names of host computers into addresses. The DNS also allows host computers not directly on the Internet to have a registered name in the same style.

DPT Dynamic Packet Transport. DPT rings are dual, counter-rotating fiber rings. Both fibers are used concurrently to transport both data and control traffic.

DSC designated shelf controller. The RP or RP pair that controls a standalone router or a multishelf system. The DSC is selected from among the route processors (RPs) installed in the router or multishelf system.

E eBGP external Border Gateway Protocol. BGP sessions are established between routers in different autonomous systems. eBGPs communicate among different network domains.

ECC error correction code. ECC is used to correct errors within memories on the Cisco CRS-1 router. egress Outgoing channel.

Ethernet Baseband LAN specification invented by Xerox Corporation and developed jointly by Xerox, Intel, and Digital Equipment Corporation. Ethernet networks use CSMA/CD and run over a variety of cable types at 10 Mbps. Ethernet standards are defined by the IEEE 802.3 specification.

F fabric Connectivity between all line cards. Also referred to as switch fabric.

FC fan controller. Two fan controller cards are installed in every line card chassis as a redundant pair to manage the fan assemblies; a BITS timing connector exists on the fan controller card.

FIB Forwarding Information Base. Database that stores information about switching of data packets. A FIB is based on information in the Routing Information Base (RIB). It is the optimal set of selected routes that are installed in the line cards for forwarding. See also RIB. flooding Traffic-passing technique used by switches and bridges in which traffic received on an interface is sent out all the interfaces of that device except the interface on which the information was originally received. forwarding Process of sending a frame toward its ultimate destination by way of an internetworking device.

Cisco IOS XR Getting Started Guide GL-3 Glossary

R3.3 Beta Draft—Cisco Confidential Information

FRR fast reroute. Automatically reroutes traffic on a label switch path (LSP) if a node or link in an LSP fails. FRR reduces the loss of packets traveling over an LSP.

FTP File Transfer Protocol. Application protocol, part of the TCP/IP protocol stack, used for transferring files between network nodes. FTP is defined in RFC 959.

GE Gigabit Ethernet. Standard for a high-speed Ethernet, approved by the IEEE 802.3z standards committee in 1996.

Gigabit Ethernet The Ethernet speed for the Cisco CRS-1 router control bus running between all chassis.

GUI graphical user interface. A user environment that uses pictorial and textual representations of the input and output of applications and the hierarchical or other data structure in which information is stored. Such conventions as buttons, icons, and windows are typical, and many actions are performed using a pointing device (such as a mouse). Microsoft Windows and the Apple Macintosh are prominent examples of platforms using a GUI. See also CLI.

HA High availability is defined as the continuous operation of systems. For a system to be available, all components, including application and database servers, storage devices, and the end-to-end network, need to provide continuous service.

HDLC high-level data link control. ISO communications protocol used in X.25 packet-switching networks. HDLC provides error correction at the data link layer and contains the following subsets: LAPB and SDLC. hexadecimal A number system having 16 as its base. This number representation uses the digits 0–9, with their usual meaning, plus the letters A–F (or a–f) to represent hexadecimal digits with values of (decimal) 10 to 15. The far right digit counts ones, the next counts multiples of 16, then 16^2 = 256, and so on.

Hexadecimal is more succinct than binary for representing bit masks, machines addresses, and other low-level constants but it is still reasonably easy to split a hex number into different bit positions. For example, the top 16 bits of a 32-bit word are the first four hex digits. hop Passage of a data packet between two network nodes (for example, between two routers). See also hop count. hop count Routing metric used to measure the distance between a source and a destination.

HTTP Hypertext Transfer Protocol. Used by web browsers and web servers to transfer files, such as text and graphic files. HTTP is the set of rules for exchanging files (text, graphic images, sound, video, and other multimedia files) on the World Wide Web. Relative to the TCP/IP suite of protocols (which are the basis for information exchange on the Internet), HTTP is an application protocol.

Cisco IOS XR Getting Started Guide GL-4 Glossary

R3.3 Beta Draft—Cisco Confidential Information

ICMP Internet Control Message Protocol. Network layer Internet (TCP/IP) protocol that reports errors and provides other information relevant to IP packet processing.

IEP IP explicit path. List of IP addresses, each representing a node or link in the explicit path.

IETF Internet Engineering Task Force. Task force consisting of over 80 working groups responsible for developing Internet standards. The IETF operates under the auspices of ISOC.

IGMP Internet Group Management Protocol. Governs the management of multicast groups in a TCP/IP network. Used by IP hosts to report their multicast group memberships to an adjacent multicast router.

IGP Interior Gateway Protocol. Internet protocol used to exchange routing information within an autonomous system. Examples of common Internet IGPs include IGRP, OSPF, and RIP. See also OSPF and RIP. ingress Incoming channel. installed software The set of Cisco IOS XR software packages installed on a router. set

IOS XR The Cisco operating system used on the Cisco CRS-1 router and Cisco XR 12000 Series Router.

IP Internet Protocol. Network layer protocol in the TCP/IP stack offering a connectionless internetwork service. IP provides features for addressing, type-of-service specification, fragmentation and reassembly, and security.

IPv4 IP Version 4. Network layer for the TCP/IP protocol suite. A connectionless, best-effort packet switching protocol.

IPv6 IP Version 6. Replacement for IPv4. A next-generation IP protocol. IPv6 is backward compatible with and designed to fix the shortcomings of IPv4, such as data security and maximum number of user addresses. IPv6 increases the address space from 32 to 128 bits, providing for an unlimited number of networks and systems. It also supports quality of service (QoS) parameters for real-time audio and video.

IPX Internetwork Packet Exchange. NetWare network layer (Layer 3) protocol used for transferring data from servers to workstations. IPX is similar to IP and XNS.

IS-IS Intermediate System-to-Intermediate System. OSI link-state hierarchical routing protocol based on DECnet Phase V routing, whereby ISs (routers) exchange routing information based on a single metric to determine network topology.

Cisco IOS XR Getting Started Guide GL-5 Glossary

R3.3 Beta Draft—Cisco Confidential Information

K keepalive interval Period of time between each keepalive message sent by a network device. keepalive message Message sent by one network device to inform another network device that the virtual circuit between the two is still active.

Layer 2 Layer 2 refers to the data link layer of the commonly referenced multilayered communication model, Open Systems Interconnection (OSI). The data link layer contains the address inspected by a bridge or switch. Layer 2 processing is faster than layer 3 processing, because less analysis of the packet is required.

Layer 3 Layer 3 refers to the network layer of the commonly referenced multilayered communication model, Open Systems Interconnection (OSI). The network layer is concerned with knowing the address of the neighboring nodes in the network, selecting routes and quality of service, and recognizing and forwarding to the transport layer incoming messages for local host domains.

A router is a Layer 3 device, although some newer switches also perform Layer 3 functions. The Internet Protocol (IP) address is a Layer 3 address.

LC line card. Line cards in the Cisco CRS-1 system are referred to as modular services cards (MSCs).

LDP label distribution protocol. A standard protocol between MPLS-enabled routers to negotiate the labels (addresses) used to forward packets. The Cisco proprietary version of this protocol is the Tag Distribution Protocol (TDP).

LIB Label Information Base. The table that contains the labels in use on the node. loopback Send the outgoing signals back to the receiving side for testing.

MAC address Standardized data link layer address that is required for every port or device that connects to a LAN. Other devices in the network use these addresses to locate specific ports in the network and to create and update routing tables and data structures. MAC addresses are 6 bytes long and are controlled by the IEEE. Also known as a hardware address, MAC layer address, and physical address. mask Pattern of bits used to reject or accept bit patterns in another set of data.

MBI minimum boot image. Software image containing a kernel and minimum set of drivers and components to boot a node.

Mbps megabits per second. A bit rate expressed in millions of binary bits per second. 1 megabit = 220 bits, or 1,048,576 bits.

Cisco IOS XR Getting Started Guide GL-6 Glossary

R3.3 Beta Draft—Cisco Confidential Information

MIB Management Information Base. Database of network management information that is used and maintained by a network management protocol like Simple Network Management Protocol (SNMP). The value of an MIB object can be changed or retrieved using SNMP commands, usually through a GUI network management system. MIB objects are organized in a tree structure that includes public (standard) and private (proprietary) branches.

MPLS Multiprotocol Label Switching. Switching method that forwards IP traffic using a label. This label instructs the routers and switches in the network where to forward the packets based on pre-established IP routing information

MPLS TE Multiprotocol Label Switching traffic engineering. A switching method that forwards IP traffic using a label. This label instructs the routers and switches in the network where to forward the packets based on pre-established IP routing information.

MSC modular services card. Module in which the ingress and egress packet processing and queueing functions are carried out in the Cisco CRS-1 router 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.

MTU maximum transmission unit. Maximum packet size, in bytes, that a particular interface can handle. multicast Multicast is a feature that refers to single packets copied by the network and sent to a specific subset of network addresses. These addresses are specified in the Destination Address Field. See also unicast.

N netboot Loading software images from a network server, such as TFTP. node A card installed and running on the router.

NSF nonstop forwarding. Packets keep flowing during events such as failover, process restarts, and the upgrade or downgrade of software packages. Nonstop forwarding is the ability of a router to continue to forward traffic toward a router that may be recovering from a transient failure and the ability of a router recovering from a transient failure in the control plane to continue correctly forwarding traffic sent to it by a peer.

NTP Network Time Protocol. Protocol built on top of TCP that ensures accurate local time-keeping with reference to radio and atomic clocks located on the Internet. This protocol is capable of synchronizing distributed clocks within milliseconds over long time periods.

NVRAM nonvolatile RAM. Static random access memory that is made into nonvolatile storage by having a battery permanently connected.

OC-x Optical carrier, where x=3, 12, 48, or 192, relating to the various speeds within a SONET network.

Cisco IOS XR Getting Started Guide GL-7 Glossary

R3.3 Beta Draft—Cisco Confidential Information

OIR online insertion and removal. Feature that permits the addition, replacement, or removal of cards without interrupting the system power, entering console commands, or causing other software or interfaces to shut down. Sometimes called hot-swapping or power-on servicing.

OSI Open Systems Interconnection. International standardization program created by ISO and ITU-T to develop standards for data networking that facilitate multivendor equipment interoperability.

OSPF Open Shortest Path First. Link-state, hierarchical Interior Gateway Protocol (IGP) routing algorithm proposed as a successor to Routing Information Protocol (RIP) in the Internet community. OSPF features include least-cost routing, multipath routing, and load balancing. OSPF was derived from an early version of the Intermediate System-to-Intermediate System (IS-IS) protocol. See also IGP and RIP.

P package A group of software components installed on the router. packet Logical grouping of information that includes a header containing control information and (usually) user data. Packets most often are used to refer to network layer units of data.

Packet over POS. Packet over SONET/SDH enables core routers to send native IP packets directly over SONET or SONET/SDH SDH frames.

PAP Password Authentication Protocol. Authentication protocol that allows PPP peers to authenticate one another. The remote router attempting to connect to the local router is required to send an authentication request. Unlike Challenge Handshake Authentication Protocol (CHAP), PAP passes the password and the hostname or username in the clear (unencrypted). PAP does not itself prevent unauthorized access but merely identifies the remote end. The router or access server then determines whether that user is allowed access. PAP is supported only on PPP lines. See also PPP.

PCMCIA Personal Computer Memory Card International Association. Standard for credit card-size memory or I/O device.

PIE package installation envelope. An installable software file with the suffix pie. A PIE may be a package or a Software Maintenance Upgrade (SMU). A PIE is used to deliver Cisco IOS XR software. A PIE may contain a single component, group of components (called a package), or set of packages. When a PIE contains more than one component, it is called a “Composite PIE.”

PLIM Physical layer interface module. Provides the physical interface for a line card. Also handles media-specific functions, such as framing, clock recovery, channelization, and optical signaling for line interfaces connecting to a Cisco CRS-1 router.

PM performance monitoring. Provides a variety of automatic functions to aid in the maintenance and operation of the network. PM is continuous, in-service monitoring of transmission quality that uses software-provisionable performance parameters. Performance parameters are measured for all four layers of the SONET signal: physical, section, line, and STS path.

POS Packet over SONET/SDH. POS enables core routers to send native IP packets directly over Synchronous Optical Network (SONET) or Synchronous Digital Hierarchy (SDH) frames.

Cisco IOS XR Getting Started Guide GL-8 Glossary

R3.3 Beta Draft—Cisco Confidential Information

PPP Point-to-Point Protocol. Successor to SLIP that provides router-to-router and host-to-network connections over synchronous and asynchronous circuits. Whereas SLIP was designed to work with IP, PPP was designed to work with several network layer protocols, such as IP, IPX, and ARA. PPP also has built-in security mechanisms, such as CHAP and PAP. PPP relies on two protocols: LCP and NCP. primary RP The first route processor configured for DSC or logical router operation. If a second RP is configured as a redundant RP, it becomes the secondary RP.

QoS quality of service. A set of parameters that describes a flow of data, such as guaranteed bandwidth, delay, and delivery guarantee.

RCP remote copy protocol. A protocol that allows users to copy files to and from a file system residing on a remote host or server on the network. The RCP protocol uses TCP to ensure the reliable delivery of data.

RIB Routing Information Base. This is the set of all available routes from which to choose the FIB. The RIB essentially contains all routes available for selection. Essentially, it is the sum of all routes learned by dynamic routing protocols, all directly attached networks (that is. networks to which a given router has interfaces connected), and any additional configured routes, such as static routes.

RIP Routing Information Protocol. A simple routing protocol that is part of the TCP/IP protocol suite and the most common IGP in the Internet. RIP determines a route based on the smallest hop count between source and destination. It is a distance vector protocol that broadcasts routing information to neighboring routers. It is known to use excessive bandwidth. See also hop count and IGP.

ROM Monitor 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 prompts for the mode. rommon B1> (Cisco CRS-1 routers)

or rommon1> (Cisco XR 12000 Series Routers)

ROMMON See ROM Monitor. router Network layer device that uses one or more routing metrics to determine the optimal path along which network traffic should be forwarded. Routers forward packets from one network to another based on network layer information. routing Process of finding a path to a destination host. Routing is very complex in large networks because of the many potential intermediate destinations a packet might traverse before reaching its destination host.

Cisco IOS XR Getting Started Guide GL-9 Glossary

R3.3 Beta Draft—Cisco Confidential Information routing metric A routing algorithm determines that one route is better than another. This information is stored in routing tables. Metrics include bandwidth, communication cost, delay, hop count, load, MTU, path cost, and reliability. Sometimes referred to simply as a metric. See also algorithm. routing protocol Protocol that accomplishes routing through the implementation of a specific routing algorithm. Examples of routing protocols include BGP, OSPF, and IS-IS. routing table Table stored in a router or some other internetworking device that keeps track of routes to particular network destinations and, in some cases, metrics associated with those routes.

RP route processor. Cards that contain run-control software on the router. Two RPs are installed as a redundant pair in dedicated slots in the front of each line card chassis.

RPF Reverse Path Forwarding. Multicasting technique in which a multicast datagram is forwarded from all but the receiving interface if the receiving interface is the one used to forward unicast datagrams to the source of the multicast datagram.

RSVP Resource Reservation Protocol. Protocol that supports the reservation of resources across an IP network. Applications running on IP end systems can use RSVP to indicate to other nodes the nature (bandwidth, jitter, maximum burst, and so on) of the packet streams they want to receive. RSVP depends on IPv6. Also known as Resource Reservation Setup Protocol. See also IPv6. running The router configuration currently in effect. Although the user can save multiple versions of the router configuration configuration for future reference, only one copy of the running configuration exists in the router at any given time.

Rx The receiver end of a fabric link. All links are unidirectional. See also Tx.

SCFC shelf controller/fan controller. Combines shelf controller function and fan controller function on one card. Two are installed in each fabric chassis.

SDH Synchronous Digital Hierarchy. European standard that defines a set of rate and format standards that are sent using optical signals over fiber. SDH is similar to SONET, with a basic SDH rate of 155.52 Mbps, designated at STM-1.

SDR secure domain router. A collection of line cards and route processors that form a complete router. Each router contains its own instance of dynamic routing, IP stack, system database, interface manager, and event notification system.

SDRAM synchronous dynamic random access memory. A form of dynamic RAM that adds a separate clock signal to the control signals. shelf controller The hardware component that manages the configuration and health of a fabric chassis within the Cisco CRS-1 router. shelf manager The shelf manager process runs on a router or switch, doing platform-dependent functions, including handling OIR events. Shelf manager is formerly called platform manager.

SMU Software Maintenance Upgrade. A “point fix” for a critical problem. SMUs are delivered as PIE files and are used to update software packages.

Cisco IOS XR Getting Started Guide GL-10 Glossary

R3.3 Beta Draft—Cisco Confidential Information

SNMP Simple Network Management Protocol. SNMP is the protocol governing network management and the monitoring of network devices and their functions. It is not necessarily limited to TCP/IP networks.

SNMPv3 Simple Network Management Protocol Version 3. An interoperable standards-based protocol for network management. SNMPv3 provides secure access to devices by a combination of authenticating and encrypting packets over the network. software A list of packages activated for a particular node. A software configuration consists of a boot package configuration and additional feature packages.

SONET Synchronous Optical Network. A standard format for transporting a wide range of digital telecommunications services over optical fiber. SONET is characterized by standard line rates, optical interfaces, and signal formats. See also SDH.

SP service processor. An SP on each card maintains an internal management connection to the shelf controller for the rack. The SP is referred to in CLI commands to identify the nodeID for fabric, alarm and fan controller cards.

Example: RP/0/RPO/CPU:router# admin show controllers fabric connectivity location 0/SM0/SP

SPE Synchronous Payload Envelope. Portion of the SONET frame containing overhead information (POH and user data).

SPF shortest path first. Routing algorithm that iterates on length of path to determine a shortest-path spanning tree. Commonly used in link-state routing algorithms. Sometimes called Dijkstra's algorithm.

SSH Secure Shell. A protocol that provides a secure remote connection to a router through a Transmission Control Protocol (TCP) application.

SSL secure socket layer. A secure socket between two entities with authentication. standby Denotes an inactive card or process that waits to become active; standby cards or processes are also sometimes denoted as backup. startup The router configuration designated to be applied on the next router startup. configuration subinterface Virtual interfaces created on a hardware interface. These software-defined interfaces allow for segregation of traffic into separate logical channels on a single hardware interface and better utilization of the available bandwidth on the physical interface. switchover A switch between the active and standby cards. The switchover can be initiated by command, or it can occur automatically when the active card fails. system reload Reload of a router node. system restart Soft reset of a router node. This involves restarting all processes running on that node.

Cisco IOS XR Getting Started Guide GL-11 Glossary

R3.3 Beta Draft—Cisco Confidential Information

TAC Cisco Technical Assistance Center.

TACACS Terminal Access Controller Access Control System. Authentication protocol, developed by the DDN community, that provides remote access authentication and related services, such as event logging. User passwords are administered in a central database rather than in individual routers, providing an easily scalable network security solution. tar A tar file is a file produced by the UNIX tar program, which packages multiple files in a single file for distribution as a single unit. Each tar file has a tar filename extension. target configuration A “two-stage” configuration of the Cisco IOS XR software running configuration. This allows users to make changes to the running configuration and accept these changes by entering the commit command. task ID An identifier that determines user access to a given command or series of commands. A user must be a member of a group with the appropriate task IDs assigned to it to execute the related commands.

Tbps terabits per second. The amount of data that can be sent in a fixed amount of time. 1 terabit = 240 bits, or 1,099,511,627,776 bits.

TCP Transmission Control Protocol. Connection-oriented transport layer protocol that provides reliable full-duplex data transmission. TCP is part of the TCP/IP protocol stack.

Telnet Standard terminal emulation protocol in the TCP/IP protocol stack. Telnet is used for remote terminal connection, enabling users to log in to remote systems and use resources as if they were connected to a local system. Telnet is defined in RFC 854. terabyte A unit of computer memory or data storage capacity equal to 1024 gigabytes (240 bytes). Approximately 1 trillion bytes.

TFTP Trivial File Transfer Protocol. A simplified version of FTP that allows files to be transferred from one computer to another over a network, usually without the use of client authentication (for example, username and password).

Note: some TFTP servers (such as Sun Solaris) may not support file sizes larger that 32 MB. trap Message sent by an SNMP agent to an NMS, a console, or a terminal to indicate the occurrence of a significant event, such as a specifically defined condition or a threshold that was reached. tunnel Secure communication path between two peers, such as two routers.

Tx The transmitter end of a fabric link. All links are unidirectional. See also Rx.

Cisco IOS XR Getting Started Guide GL-12 Glossary

R3.3 Beta Draft—Cisco Confidential Information

UDP User Datagram Protocol. Connectionless transport layer protocol in the TCP/IP protocol stack. UDP is a simple protocol that exchanges datagrams without acknowledgments or guaranteed delivery, requiring that error processing and retransmission be handled by other protocols. UDP is defined in RFC 768. unicast Message sent to a single network destination. unicast A unicast transmission sends one copy of each packet to each member of the group. This method is transmission inefficient because the same information must be carried multiple times, requiring extra bandwidth.

VCSEL vertical cavity surface emitting laser. vm A vm file is a Cisco IOS XR software file that can be installed from ROM Monitor mode. A vm file is typically used to install the Cisco IOS XR software when the software has not yet been installed or has been corrupted.

VPN Virtual Private Network. Enables IP traffic to travel securely over a public TCP/IP network by encrypting all traffic from one network to another. A VPN uses “tunneling” to encrypt all information at the IP level.

WRED Weighted Random Early Detection. Queueing method that ensures that high-precedence traffic has lower loss rates than other traffic during times of congestion.

XML Extensible Markup Language. A standard maintained by the World Wide Web Consortium (W3C) that defines a syntax that lets you create markup languages to specify information structures. Information structures define the type of information, for example, subscriber name or address, not how the information looks (bold, italic, and so on). External processes can manipulate these information structures and publish them in a variety of formats. XML allows you to define your own customized markup language.

XML agent A process on the router that is sent XML requests by XML clients and is responsible for carrying out the actions contained in the request and returning an XML response back to the client. The XML Agent for CORBA is an example of an XML agent provided on the Cisco CRS-1 router.

XML client An external application that sends an XML request to the router and receives XML responses to those requests.

XML operation A portion of an XML request that specifies an operation that the XML client would like the XML agent to perform.

Cisco IOS XR Getting Started Guide GL-13 Glossary

R3.3 Beta Draft—Cisco Confidential Information

XML operation The router code that carries out a particular XML operation including parsing the operation XML, provider performing the operation, and assembling the operation XML response

XML request An XML document sent to the router containing a number of requested operations to be carried out.

XML response The response to an XML request.

XML schema An XML document specifying the structure and possible contents of XML elements that can be contained in an XML document.

Cisco IOS XR Getting Started Guide GL-14 R3.3 Beta Draft—Cisco Confidential Information

INDEX

Symbols C

? command 6-2 capitalization, keyboard shortcuts 6-19 cards CRS-FCC-LED 3-37 A FM LED 3-37 abbreviated commands, entering 6-2 OIM LED 3-37, 3-39 abort command 4-32 card type, displayed in prompt 4-12 aborting command output 6-7 characters admin command 3-33 anchor D-4 administration configuration mode 4-19 parentheses for pattern recall D-4 administration EXEC mode 4-19 pattern ranges D-2 alarm correlation, logging 5-11 special D-2 alarm logging underscore wildcard D-4 correlation 5-11 chassis locations 5-10 number, displayed in prompt 4-12 severity levels 5-10 Cisco IOS XR software aliases 6-16 supported hardware 1-1 alphanumeric LED display, illustration (16-slot Cisco IOS XR Software Selector tool 7-26 chassis) 1-9, 4-3 cisco-support user group 4-14 alphanumeric LED display, illustration (8-slot clear command 9-18 chassis) 1-10, 4-4 clear configuration commit command 5-8 alphanumeric LED display, illustration (PRP-1) 1-11, 1-12, 4-5, 4-6 clear configuration sessions command 9-21 anchor characters D-4 CLI asynchronous operation, install command 7-29 identifying command mode 4-16 introduction 1-5 logging in 4-11 B prompt 4-12

BGP, configuration limits 5-22 clock, router 4-39 bring up clock and scheduler card See CSC hardware, first time 1-8, 2-2 clock set command 4-40 verifying status 2-3 clock timezone command 4-40 clock update-calendar command 4-41

Cisco IOS XR Getting Started Guide IN-1 Index

R3.3 Beta Draft—Cisco Confidential Information command-line interface See CLI loading changes 5-7 command mode committing a configuration 4-22 administration configuration 4-19 committing packages 7-39 administration EXEC 4-19 complex expressions D-3 CLI prompt 4-16 config-register command 8-18 configuration submodes 4-17 configuration EXEC 4-17 clearing changes 4-30 global configuration 4-17 committing 4-22 interface configuration 4-18 displaying 4-24 navigation 4-15 displaying errors 4-29 navigation example 4-20 ending a session 4-31 ROM monitor mode 4-19 limiting 5-17 router configuration 4-18 limits router submode configuration 4-18 BGP 5-22 commands IS-IS 5-19 abbreviated 6-2 MPLS 5-26 aliases 6-16 multicast 5-25 applying templates 6-14 OSPF 5-19 completing a partial command 6-4 other 5-26 creating templates 6-12 RPL 5-24 identifying syntax errors 6-4 static routes 5-18 more prompt, responding to 6-6 merged configuration, displaying 4-24, 4-28 no form 6-5 overview 4-21 on-screen help 6-2 reloading a failed configuration 4-30 output running configuration filtering 6-8 displaying 4-25, 4-26 halting 6-7 locking 4-32 narrowing 6-8 unlocking 4-32 redirecting to a file 6-7 target configuration recall deleted entries 6-18 displaying 4-28 redisplaying 6-18 introduction 4-22 wildcards 6-11 loading from a file 5-9 wrapped lines, editing 6-5 saving to a file 5-9 commit command 4-22 configuration files, storage 4-24 commit force command 9-19 configuration mode, entering EXEC commands 4-19 commitIDs configurations, multishelf systems 1-2 clearing 5-8 configurations, single-shelf systems 1-1 displaying 5-4 configuration submodes 4-17 displaying changes 5-5 configuration templates

Cisco IOS XR Getting Started Guide IN-2 Index

R3.3 Beta Draft—Cisco Confidential Information

applying 6-14 domain name, configuration 5-1 creating 6-12 domain name command 5-2 configure exclusive command 4-33 domain name server, configuration 5-1 connection domain name-server command 5-2 CLI prompt 4-12 drives, formatting 8-19 Console port connection 4-3 E illustration (16-slot chassis) 1-9, 4-3 illustration (8-slot chassis) 1-10, 1-11, 1-12, 4-4, 4-5, 4-6 end command 3-33, 4-31 console port, connecting to 1-8, 2-2 errors consolidated switch fabric cards See CSFC displaying configuration errors 4-29 controller fabric plane command 8-24, 8-33 syntax 6-4 controllers command 8-18 Ethernet interface copy ftp command 7-28 configuring 4-34 copy rcp command 7-28 connection, illustration (16-slot chassis) 1-9, 4-3 copy tftp command 7-28 connection, illustration (8-slot chassis) 1-10, 1-11, 1-12, correlation, alarm logging 5-11 4-4, 4-5, 4-6 CPU0 module 4-12 displaying 4-36 Craft Works Interface See CWI EXEC commands, entering in configuration mode 4-19 CSC EXEC mode 4-17 removing and replacing 8-40 exit command 4-31 CSFC expressions removing and replacing 8-45 complex D-3 cursor movement 6-19 regular D-1 CWI extensible markup language See XML introduction 1-5 F

D Figures debug command 9-5 multishelf system 1-3, 1-4 debugging file disabling for all services, all sessions 9-6 redirecting output to 6-7 disabling for all services, one session 9-6 file storage disabling for a service 9-6 flash disk0 7-11 displaying features 9-5 File Transfer Protocol See FTP displaying status 9-5 filters, command output 6-8 enabling 9-5 flash disk default SDR 4-1 disk0 7-11 disk0 7-11 flash disk0

Cisco IOS XR Getting Started Guide IN-3 Index

R3.3 Beta Draft—Cisco Confidential Information

configuration file storage 4-24 ipv4 access-list oor ace threshold command 5-26 FM LED card 3-37 ipv4 access-list oor acl threshold command 5-26 format command 8-19 ipv4 address command 4-37 formatting drives 8-19 ipv6 access-list oor ace threshold command 5-26 FTP 7-28 ipv6 access-list oor acl threshold command 5-26 IS-IS, configuration limits 5-19

G K global configuration mode 4-17 group command 5-16 keyboard shortcuts capitalization 6-19 command history 6-18 H cursor movement 6-19 halting command output 6-7 deleting text 6-20 hardware recalling deleted entries 6-18 displaying status 8-1 transposing letters 6-20 documentation xii history, commands 6-17 L hostname configuration 4-33 LED panel on OIM LED card 3-37, 3-39 displayed in prompt 4-12 line card hostname command 4-33 removal 8-20 HTTP server configuration 5-2 replacement 8-21, 8-22 hw-module location command 8-16, 8-18, 8-41, 8-42, 8-43 line wrap, editing long lines 6-5 load command 5-9 load commit changes command 5-7 I load rollback changes command 5-7, 5-8 install activate command 7-32, 7-36 logging install activate command, test option 7-40 alarm correlation 5-11 install command, synchronous and asynchronous configuration 5-11 operation 7-29 output locations 5-10 install commit command 7-39 severity levels 5-10 install deactivate command 7-39 logging buffered command 5-10, 5-12 install remove command 7-39 logging command 5-12 install rollback committed command 7-37, 7-38 logging console command 5-10, 5-12 interface configuration mode 4-18 logging monitor command 5-10 interface MgmtEth command 4-37 logging trap command 5-10, 5-12 interface preconfigure command 8-20, 8-21 log in, router 4-11 interfaces, verifying operation 9-21

Cisco IOS XR Getting Started Guide IN-4 Index

R3.3 Beta Draft—Cisco Confidential Information long lines, editing 6-5 configuration submodes 4-17 low memory warning, removing configurations 9-18 EXEC 4-17 global configuration 4-17 interface configuration 4-18 M ROM monitor 4-19 Management Ethernet interface router configuration 4-18 configuration 4-36 router submode configuration 4-18 configuring 4-34 modem connection connection illustration (16-slot chassis) 4-3 illustration (16-slot chassis) 1-9, 4-3 connection illustration (8-slot chassis) 4-4 illustration (8-slot chassis) 1-10, 1-11, 1-12, 4-4, 4-5, 4-6 displaying 4-36 module 8-5, 8-8 establishing a connection through 4-10 module, number displayed in prompt 4-12 name syntax 4-34 monitor processes command 9-8, 9-12 maximum external-sa command 5-25 monitor threads command 9-8 maximum group-mappings autorp command 5-25 More prompt 6-6 maximum groups command 5-25 MPLS maximum groups per-interface command 5-25 configuration limits 5-26 maximum interfaces command 5-20 package features 7-7 maximum-paths command (BGP) 5-23 mpls traffic-eng maximum tunnels command 5-26 maximum-paths command (IS-IS) 5-19 MSC maximum paths command (OSPF) 5-20 removal 8-20 maximum peer-external-sa command 5-25 multicast, configuration limits 5-25 maximum-prefix command 5-22 multimodule configuration 3-39 maximum redistributed-prefix command (OSPF) 5-20 multishelf system maximum-redistributed-prefixes command (IS-IS) 5-19 components (figure) 1-3, 1-4 maximum register-states command 5-25 multishelf systems 1-2 maximum route-interfaces command 5-25 maximum routes command 5-25 N MBI 8-13 memory name displaying system memory 9-17 router, configuring 4-33 low memory warnings 9-16 router name displayed in prompt 4-12 management 5-17 named SDR 4-1 removing configurations 9-18 netadmin user group 4-14 merged configuration, displaying 4-24, 4-28 network connection, overview 4-3 minimum boot image 8-13 no, command form 6-5 mode node administration configuration 4-19 administrative shutdown 8-18 administration EXEC 4-19 power cycle 8-16

Cisco IOS XR Getting Started Guide IN-5 Index

R3.3 Beta Draft—Cisco Confidential Information

reload 8-16 names 7-13 shutdown 8-16 version numbers 7-13 no debug command 9-6 ping command 9-3 no hw-module node command 8-25, 8-34 PLIM nonactive target configuration 4-22 removal 8-20 replacement 8-21, 8-22 power cycle 8-16 O power on, first time 1-8, 2-2 OIM LED card 3-37 Primary LED illustration (16-slot chassis) 1-9, 4-3 OIM LEDs used for troubleshooting fabric card Primary LED illustration (8-slot chassis) 1-10, 4-4 connections 3-40 process 9-7 OIR 8-20 process command 9-14 for switch fabric cards 8-22, 8-31 process mandatory command 9-14 online insertion and removal 8-20 process mandatory reboot command 9-14 operator user group 4-14 Optical Interface Module. See OIM 3-37 OSPF, configuration limits 5-19 R

rack, displayed in prompt 4-12 P rack number 8-5, 8-8 rcp 7-28 package redirecting command output 6-7, 6-8 activation redundancy impact on running configuration 7-18 automatic failover 8-14 introduction 7-11 commands 8-13 addition, introduction 7-11 manual switchover 8-14 committing a package set 7-11 primary RP 8-13 deactivation 7-39 standby RP 8-13 impact on running configuration 7-18 redundancy switchover command 8-14 removal 7-39 reload rollback 7-11 software 8-16 packages reload command 8-14, 8-16 committing 7-39 Remote Copy Protocol See rcp partial command, entry 6-4 resource management 5-17 password command 5-16 rollback pattern committed software 7-37 alternation D-4 configuration, overview 5-3 multiple-character D-3 configuration rollback failure 5-4 recall D-4 history log, displaying 5-5 PIE files loading changes to the target configuration 5-7

Cisco IOS XR Getting Started Guide IN-6 Index

R3.3 Beta Draft—Cisco Confidential Information

package incompatibility 5-4 secure domain routers 4-1 points, displaying 7-24 service processor See SP points, rolling back 7-38 session previewing changes 5-6 configuration overview 4-21 procedure 5-6 ending 4-31 rollback configuration command 5-6 SFC rollback configuration to command 9-20 removing and replacing 8-40 rollback for packages SFTP 7-28 introduction 7-11 shortcuts ROM monitor mode 4-19 capitalization 6-19 root-lr user group 4-14 command history 6-18 root-system user group 4-14 cursor movement 6-19 route maximum ipv4 command 5-18 deleting text 6-20 route maximum ipv6 command 5-18 recalling deleted entries 6-18 route processors transposing letters 6-20 faceplate illustration (16-slot chassis) 1-9, 4-3 show aaa userdb command 5-14 faceplate illustration (8-slot chassis) 1-10, 4-4 show aaa usergroup command 4-15, 5-14 faceplate illustration (PRP-1) 1-11, 1-12, 4-5, 4-6 show bgp neighbor command 5-22 router show clock command 4-41 clock setting 4-39 show configuration command 5-9, 6-6, 9-2 name configuration 4-33 show configuration commit changes command 5-5, 9-19 name displayed in prompt 4-12 show configuration commit history 9-18 verifying status 2-3 show configuration commit history command 5-5, 9-18 router configuration mode 4-18 show configuration commit list 9-20 router submode configuration 4-18 show configuration commit list command 5-4, 9-20 RPL, configuration limits 5-24 show configuration failed command 9-14 rpl maximum lines command 5-24 show configuration failed noerror command 9-15 rpl maximum policies command 5-24 show configuration failed startup command 9-15 RP reload 8-14 show configuration rollback changes 9-20 running configuration show configuration rollback changes command 5-6 displaying 4-25, 4-26 show configuration rollback changes to command 9-20 locking 4-32 show configuration sessions command 4-32, 9-21 unlocking 4-32 show context command 9-2 show controller command 9-2 show controller fabric plane all command 8-24, 8-33 S show controllers command 8-18 SDR 4-1 show debug command 9-2, 9-5 secret command 5-16 show debug condition command 9-6 secure domain router, logging in 4-11 show diag chassis command 8-3

Cisco IOS XR Getting Started Guide IN-7 Index

R3.3 Beta Draft—Cisco Confidential Information show diag command 8-2 show processes startup command 9-9 show environment command 2-5, 6-6, 8-8, 9-2 show redundancy command 2-7, 8-10, 8-13, 8-14, 8-17, 9-2 show exception command 9-2 show rpl maximum lines command 5-24 show hosts command 5-2 show rpl max policies command 5-24 show igmp summary command 5-25 show running-config command 6-6, 8-20, 9-2 show install active command 7-22 show running-config route maximum command 5-18 show install active detail command 7-22 show running-config router ospf command 5-20 show install command 9-2 show task supported command 4-13, 5-14 show install committed command 7-23 show tech-support command 6-6, 9-3 show install rollback ? command 7-24 show tracebacks command 9-3 show install rollback command 7-24 show user all command 8-23, 8-32, 8-40 show interface command 9-21 show user command 4-15, 9-3 show interfaces command 8-20, 9-2 show user group command 4-15, 8-22, 8-31, 8-40 show interfaces MgmtEth command 4-38 show user tasks command 4-15 show ipv4 access-lists command 5-26 show variables boot command 8-16, 8-17, 9-2 show ipv4 interface brief command 9-21 show version command 2-5, 6-6, 8-4, 9-3 show ipv4 interface command 9-21 shutdown 8-16 show isis adjacency command 5-19 Simple Network Management Protocol 1-6 show isis route command 5-19 single-shelf systems 1-1 show logging command 5-12, 9-2 slot, number displayed in prompt 4-12 show memory command 9-2, 9-17 slot number 8-5, 8-8 show memory summary command 9-17, 9-18 SMU 7-10 show mpls traffic-eng maximum tunnels command 5-26 filenames 7-15 show msdp summary command 5-25 version numbers 7-15 show ospf command 5-20 SNMP (Simple Network Management Protocol) 1-6 show pim summary command 5-25 software, documentation xii show platform command (administration EXEC Software Maintenance Update See SMU mode) 8-7 software packages show platform command (EXEC mode) 8-5 activating show process blocked command 9-2 on a single card 7-33 show processes abort command 9-8 activation show processes blocked command 9-8 impact on running configuration 7-18 show processes boot command 9-8 impact on system 7-18 show processes command 9-8, 9-9, 9-10 prerequisites 7-19 show processes cpu command 9-8 active packages show processes dynamic command 9-8 displaying all 7-21 show processes failover command 9-8 displaying for a card 7-22 show processes log command 9-8 Cisco IOS XR Software Selector tool 7-26 show processes memory command 9-9, 9-11 committing 7-39

Cisco IOS XR Getting Started Guide IN-8 Index

R3.3 Beta Draft—Cisco Confidential Information

configuration rollback failure 5-4 complex regular expressions D-3 deactivation error identification 6-4 impact on running configuration 7-18 pattern alternation D-4 impact on system 7-18 pattern recall D-4 prerequisites 7-19 regular expressions D-1 displaying committed versions 7-23 special characters D-2 downgrading 7-13 wildcard underscore D-4 impact of version changes 7-18 sysadmin user group 4-14 management overview 7-10 removing inactive software 7-39 T rollback 7-37, 7-38 SMUs 7-15 tab key 6-4 upgrading 7-12 target configuration 4-22 version numbers 7-13 clearing changes 4-30 SP 8-6 displaying 4-28 special characters D-2 loading from a file 5-9 SSH File Transfer Protocol 7-28 saving to a file 5-9 start up task group, introduction 4-13 hardware, first time 1-8, 2-2 task ID, introduction 4-13 verifying status 2-3 task IDs static route, configuration limits 5-18 displaying 4-14 Status LED illustration (16-slot chassis) 1-9, 4-3 Telnet server configuration 5-2 Status LED illustration (8-slot chassis) 1-10, 4-4 templates status LEDs applying 6-14 CRS-FCC-LED 3-38, 3-40 creating 6-12 OIM LED 3-38, 3-40 terminal connection, illustration (16-slot chassis) 1-9, 4-3 stopping command output 6-7 terminal connection, illustration (8-slot chassis) 1-10, submodes, configuration 4-17 1-11, 1-12, 4-4, 4-5, 4-6 switch fabric cards terminal history command 6-18 Cisco XR 12000 Series routers terminal server, establishing a connection through 4-8 removing and replacing 8-40 terminal settings, default values 1-13, 4-7, 4-9 CRS-1routers TFTP removing and replacing 8-22, 8-31 introduction 7-28 switch fabric card See SFC 8-40 thread 9-7, 9-9, 9-12 synchronous operation time, setting the router clock 4-39 install command 7-29 time zone, setting the router clock 4-39 syntax TLSv1 7-7 anchor characters D-4 traceroute command 9-3 character pattern ranges D-2 Transport Layer Security Version 1 7-7

Cisco IOS XR Getting Started Guide IN-9 Index

R3.3 Beta Draft—Cisco Confidential Information

Trivial File Transfer Protocol See TFTP X troubleshooting basic commands 9-2 XML displaying system memory information 9-17 API 1-5 errors at startup 9-15 host service configuration 5-2 failed commit operation 9-14 low memory warnings 9-16 processes and threads 9-7 type, card type displayed in prompt 4-12

U undebug all command 9-6 underscore wildcard character D-4 user access task IDs, displaying 4-14 user accounts configuration overview 5-14 creating 5-15 user groups assigning to a user 5-15 displaying 4-14 introduction 4-13 predefined 4-14 user interfaces CLI 1-5 CWI 1-5 SNMP 1-6 XML API 1-5 username command 5-16

W warning, low memory 9-16 wildcards 6-11

Cisco IOS XR Getting Started Guide IN-10