Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

Cisco ASR 1000 Series Aggregation Services Routers Software Configuration GuideNovember 24, 2010

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

800 553-NETS (6387)Fax: 408 527-0883

Text Part Number: OL-16506-08

http://www.cisco.com

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

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

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

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

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

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned 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. (1005R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide Copyright © 2010 Cisco Systems, Inc. All rights reserved.

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

CiscOL-16506-08

C O N T E N T S

Preface xi

Objectives xi

Document Revision History xii

Organization xiii

Related Documentation xiv

Cisco ASR 1000 Series Routers Documentation xiv

Document Conventions xv

Obtaining Documentation and Submitting a Service Request xvi

C H A P T E R 1 Software Packaging and Architecture 1-1

Software Packaging on the Cisco ASR 1000 Series Routers 1-1

ASR 1000 Series Routers Software Overview 1-1

Consolidated Packages 1-2

Important Information about Consolidated Packages 1-2

Individual Software Sub-Packages Within a Consolidated Package 1-3

Important Notes about Individual Sub-Packages 1-3

Optional Software Sub-Packages Outside of Consolidated Packages 1-3

Important Notes About Optional Sub-Packages 1-4

Provisioning Files 1-4

Important Information about Provisioning Files 1-4

ROMmon Image 1-5

File to Upgrade Field Programmable Hardware Devices 1-5

Processes 1-5

Processes Overview 1-6

IOS as a Process 1-7

Dual IOS Processes 1-7

File Systems on the Cisco ASR 1000 Series Router 1-8

Autogenerated File Directories and Files on the Cisco ASR 1000 Series Router 1-8

Important Notes Regarding Autogenerated Directories 1-9

C H A P T E R 2 Using Cisco IOS XE Software 2-1

Accessing the CLI Using a Router Console 2-1

Accessing the CLI Using a Directly-Connected Console 2-1

Connecting to the Console Port 2-2

iiio ASR 1000 Series Aggregation Services Routers Software Configuration Guide

Contents

Using the Console Interface 2-2

Accessing the CLI from a Remote Console Using Telnet 2-3

Preparing to Connect to the Router Console Using Telnet 2-3

Using Telnet to Access a Console Interface 2-3

Accessing the CLI from a Remote Console Using a Modem 2-4

Using the Auxiliary Port 2-4

Using Keyboard Shortcuts 2-4

Using the History Buffer to Recall Commands 2-5

Understanding Command Modes 2-6

Understanding Diagnostic Mode 2-8

Getting Help 2-9

Finding Command Options Example 2-9

Using the no and default Forms of Commands 2-12

Saving Configuration Changes 2-13

Managing Configuration Files 2-13

Filtering Output from the show and more Commands 2-14

Powering Off the Router 2-15

Finding Support Information for Platforms and Cisco Software Images 2-15

Using Cisco Feature Navigator 2-15

Using Software Advisor 2-16

Using Software Release Notes 2-16

C H A P T E R 3 Consolidated Packages and Sub-Package Management 3-1

Running the Cisco ASR 1000 Series Routers Overview 3-1

Running Cisco ASR 1000 Series Routers Using Individual and Optional Sub-Packages Overview 3-1

Running Cisco ASR 1000 Series Routers Using a Consolidated Package Overview 3-2

Running Cisco ASR 1000 Series Routers Summary 3-3

Software File Management Command Set Overview 3-4

The request platform Command Set 3-4

The copy Command 3-5

The issu Command Set 3-5

Managing and Configuring the Router to Run Using Consolidated Packages and Individual Sub-Packages 3-6

Quick Start Software Upgrade 3-6

Managing and Configuring a Router to Run Using a Consolidated Package 3-7

Managing and Configuring a Consolidated Package Using the copy Command 3-7

Managing and Configuring a Consolidated Package Using the request platform software package install Command 3-8

ivCisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08

Contents

Managing and Configuring a Router to Run Using Individual Sub-Packages From a Consolidated Package 3-10

Extracting a Consolidated Package and Booting Using the Provisioning File 3-10

Copying a Set of Individual Sub-Package Files and Booting Using a Provisioning File 3-14

Managing and Configuring a Router to Run Using Optional Sub-Packages 3-14

Installing an Optional Sub-Package 3-14

Uninstalling an Optional Sub-Package 3-16

Troubleshooting Software Mismatch with ESP Board ASR1000-ESP10-N 3-17

Upgrading Individual Sub-Packages 3-18

Upgrading a SPA Sub-Package 3-18

C H A P T E R 4 In Service Software Upgrades (ISSU) 4-1

Cisco IOS XE Software Package Compatibility for ISSU 4-1

Prerequisites for ISSU 4-2

Restrictions for ISSU 4-2

Overview of ISSU on the Cisco ASR 1000 Series Routers 4-3

ISSU Rollback Timer Overview on the Cisco ASR 1000 Series Router 4-4

Important Notes about ISSU Compatibility 4-5

ISSU with Dual IOS Processes on a Single RP Overview 4-6

ISSU Upgrade Procedures 4-6

Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration 4-6

Examples 4-9

Using ISSU to Upgrade Sub-Packages in a Dual Route Processor Configuration 4-12

Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1006 Router (issu command set) 4-13

Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1006 Router (request platform command set) 4-45

Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router 4-72

Configuring RPR or SSO on a Cisco ASR 1002 or Cisco ASR 1004 Router 4-72

Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router (issu command set) 4-75

Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router (request platform command set) 4-101

ISSU Upgrade Procedures (Pre Cisco IOS XE Release 2.1.2) 4-123

Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration (Pre Cisco IOS XE 2.1.2) 4-123

Using ISSU to Perform a Consolidated Package Upgrade on a Single Route Processor Configuration (Pre Cisco IOS XE 2.1.2) 4-123

Using ISSU to Upgrade Sub-Packages (Pre Cisco IOS XE Release 2.1.2) 4-123

4-124

vCisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08

Contents

C H A P T E R 5 High Availability Overview 5-1

Hardware Redundancy Overview on the Cisco ASR 1000 Series Routers 5-1

Software Redundancy on the Cisco ASR 1000 Series Routers 5-3

Software Redundancy Overview 5-3

Second IOS Process on a Cisco ASR 1002 or 1004 Router 5-3

Route Processor Redundancy 5-4

Stateful Switchover 5-4

SSO-Aware Protocol and Applications 5-5

Bidirectional Forwarding Detection 5-5

C H A P T E R 6 Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers 6-1

Finding Feature Information 6-1

Contents 6-1

Information About Call Home 6-2

Benefits of Using Call Home 6-2

How to Obtain Smart Call Home Service 6-2

Prerequisites for Call Home 6-3

How to Configure Call Home 6-4

Configuring the Management Interface VRF 6-4

What To Do Next 6-5

Configuring a Destination Profile 6-5

Configuring a Destination Profile to Send Email Messages 6-6

Configuring a Destination Profile to Send HTTP Messages 6-10

Working With Destination Profiles 6-13

Subscribing to Alert Groups 6-16

Periodic Notification 6-16

Message Severity Threshold 6-16

Syslog Pattern Matching 6-17

Configuring Contact Information 6-19

Example 6-21

Configuring the Number of Call Home Messages Sent Per Minute 6-21

Enabling and Disabling Call Home 6-21

Sending Call Home Communications Manually 6-22

Sending a Call Home Test Message Manually 6-22

Sending Call Home Alert Group Messages Manually 6-23

Submitting Call Home Analysis and Report Requests 6-24

Sending the Output of a Command to Cisco or an E-Mail Address 6-25

How To Configure Call Home to Support the Smart Call Home Service 6-26

viCisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08

Contents

Prerequisites 6-26

Configure and Enable Call Home 6-26

Declare and Authenticate a CA Trustpoint 6-28

Examples 6-30

Start Smart Call Home Registration 6-30

What To Do Next 6-31

Displaying Call Home Configuration Information 6-31

Examples 6-32

Default Settings 6-36

Alert Group Trigger Events and Commands 6-37

Message Contents 6-39

Sample Syslog Alert Notification in Long-Text Format 6-43

Sample Syslog Alert Notification in XML Format 6-47

Additional References 6-53

Related Documents 6-53

Standards 6-53

MIBs 6-54

RFCs 6-54

Technical Assistance 6-54

Feature Information for Call Home 6-54

C H A P T E R 7 Console Port, Telnet, and SSH Handling 7-1

Console Port Overview for the Cisco ASR 1000 Series Routers 7-1

Console Port Handling Overview 7-1

Telnet and SSH Overview for the Cisco ASR 1000 Series Routers 7-2

Persistent Telnet and Persistent SSH Overview 7-2

Configuring a Console Port Transport Map 7-2

Examples 7-5

Configuring Persistent Telnet 7-5

Prerequisites 7-5

Examples 7-8

Configuring Persistent SSH 7-9

Examples 7-11

Viewing Console Port, SSH, and Telnet Handling Configurations 7-12

Important Notes and Restrictions 7-17

C H A P T E R 8 Using the Management Ethernet Interface 8-1

Gigabit Ethernet Management Interface Overview 8-1

viiCisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08

Contents

Gigabit Ethernet Port Numbering 8-2

IP Address Handling in ROMmon and the Management Ethernet Port 8-2

Gigabit Ethernet Management Interface VRF 8-2

Common Ethernet Management Tasks 8-3

Viewing the VRF Configuration 8-3

Viewing Detailed VRF Information for the Management Ethernet VRF 8-4

Setting a Default Route in the Management Ethernet Interface VRF 8-4

Setting the Management Ethernet IP Address 8-4

Telnetting over the Management Ethernet Interface 8-5

Pinging over the Management Ethernet Interface 8-5

Copy Using TFTP or FTP 8-5

NTP Server 8-5

SYSLOG Server 8-6

SNMP-related services 8-6

Domain Name Assignment 8-6

DNS service 8-6

RADIUS or TACACS+ Server 8-6

VTY lines with ACL 8-7

C H A P T E R 9 Synchronous Ethernet Support On The Cisco ASR 1000 Series Routers 9-1

Synchronization Status Message and Ethernet Synchronization Messaging Channel 9-2

Synchronization Status Message 9-2

Ethernet Synchronization Messaging Channel 9-3

Restrictions and Usage Guidelines 9-4

Configuring Synchronous Ethernet on the Cisco ASR 1000 Series Routers 9-4

Configuring Clock Recovery from SyncE 9-4

Configuring Clock Recovery from a BITS Port 9-6

Configuring a SyncE Using the System-to-External Method 9-8

Configuring a SyncE Using the Line-to-External Method 9-9

Managing Synchronization on the Cisco ASR 1000 Series Router 9-11

Verification 9-13

Troubleshooting the SyncE Configuration 9-16

C H A P T E R 10 Configuring Bridge Domain Interfaces 10-1

Restrictions for the Bridge Domain Interface 10-1

Information about a Bridge Domain Interface 10-1

Ethernet Virtual Circuit Overview 10-2

Assigning a MAC Address 10-2

Support for IP Protocols 10-2

viiiCisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08

Contents

Support for IP Forwarding 10-3

Packet Forwarding 10-3

Layer 2 to Layer 3 10-3

Layer 3 to Layer 2 10-3

Link States of a Bridge Domain and a Bridge Domain Interface 10-4

Bridge Domain Interface Statistics 10-4

Creating or Deleting a Bridge Domain Interface 10-4

Bridge Domain Interface Scalability 10-5

Configuring a Bridge Domain Interface 10-5

C H A P T E R 11 Tracing and Trace Management 11-1

Tracing Overview 11-1

How Tracing Works 11-1

Tracing Levels 11-2

Viewing a Tracing Level 11-3

Setting a Tracing Level 11-4

Viewing the Content of the Trace Buffer 11-5

C H A P T E R 12 Configuring and Accessing the Web User Interface 12-1

Web User Interface Overview 12-1

Web User Interface General Overview 12-1

Legacy Web User Interface Overview 12-2

Graphics-Based Web User Interface Overview 12-3

Persistent Web User Interface Transport Maps Overview 12-4

Configuring the Router for Web User Interface Access 12-5

Authentication and the Web User Interface 12-7

Domain Name System and the Web User Interface 12-7

Clocks and the Web User Interface 12-7

Accessing the Web User Interface 12-8

Using Auto-Refresh 12-9

Web User Interface Tips and Tricks 12-10

A P P E N D I X A Unsupported Commands A-1

A P P E N D I X B Configuration Examples B-1

Configuring Router to Boot Consolidated Package on TFTP Server B-1

Copying Consolidated Package from TFTP Server to Router B-5

Configuring Router to Boot Using Consolidated Package Stored on Router B-6

ixCisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08

Contents

Extracting Sub-Packages from a Consolidated Package into the Same File System B-7

Extracting Sub-Packages from a Consolidated Package into a Different File System B-8

Configuring Router to Boot Using Sub-Packages B-9

Backing up Configuration Files B-13

Copying Startup Configuration File to Bootflash B-13

Copying Startup Configuration File to USB Flash Disk B-14

Copying Startup Configuration File to a TFTP Server B-14

Enabling Second IOS Process on Single RP Using SSO B-14

ISSU—Consolidated Package Upgrade B-19

xCisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08

Preface

Revised: November 24, 2010, OL-16506-08

This preface describes the objectives and organization of this document and explains how to find additional information on related products and services. This preface contains the following sections:

• Objectives, page xi

• Document Revision History, page xii

• Organization, page xiii

• Related Documentation, page xiv

• Document Conventions, page xv

• Obtaining Documentation and Submitting a Service Request, page xvi

ObjectivesThis document provides an overview of software functionality that is specific to the Cisco ASR 1000 Series Aggregation Services Routers. It is not intended as a comprehensive guide to all of the software features that can be run using the Cisco ASR 1000 Series Routers, but only the software aspects that are specific to these routers.

For information on general software features that are also available on the Cisco ASR 1000 Series Routers, see the Cisco IOS XE technology guide for that specific software feature.

xiCisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08

Preface

Document Revision HistoryThe Document Revision History records technical changes to this document. The table shows the Cisco IOS XE software release number and document revision number for the change, the date of the change, and a brief summary of the change.

Release No. Date Change Summary

IOS XE 3.2.0S November 24, 2010 • Added new content to document bridge domain interface configurations in the “Configuring Bridge Domain Interfaces” chapter.

• Added new content to document the Synchronous Ethernet in the “Synchronous Ethernet Support On The Cisco ASR 1000 Series Routers” chapter.

IOS XE 3.1.0S July 30, 2010 • Added upgrade and file package information and link for Upgrading Field Programmable Hardware Devices for Cisco ASR 1000 Series Routers document in “Software Packaging and Architecture” chapter.

• Added restriction regarding ISSU support in Cisco IOS XE Release 3.1S in “In Service Software Upgrades (ISSU)” chapter.

IOS XE 2.6 February 26, 2010 • Added support for the Call Home feature in the “Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers” chapter.

• Moved the ISSU compatibility tables into the Release Notes for Cisco ASR 1000 Series Aggregation Services Routers for Cisco IOS XE Release 2.

• Relocated other ISSU compatibility information into the “In Service Software Upgrades (ISSU)” chapter.

IOS XE 2.5 December 15, 2009 Updated the “Cisco IOS XE Software Package Compatibility for ISSU” chapter with new compatibility information.

IOS XE 2.4 June 30, 2009 • Updated the “Cisco IOS XE Software Package Compatibility for ISSU” chapter with new compatibility information.

• Updated book with installation information for the new optional sub-package for the Cisco WebEx Node for ASR 1000 Series.

IOS XE 2.3 February 27, 2009 Updated the “Cisco IOS XE Software Package Compatibility for ISSU” chapter with new compatibility information.

IOS XE 2.2 November 20, 2008 Updated the “Cisco IOS XE Software Package Compatibility for ISSU” chapter with new compatibility information.

IOS XE 2.2 November 3, 2008 Added new content to document compatibility of different versions of Cisco IOS XE software in the “Cisco IOS XE Software Package Compatibility for ISSU” chapter.

xiiCisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08

http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/chassis/hw_fp_upgrade.html

http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/chassis/hw_fp_upgrade.html

http://www.cisco.com/en/US/docs/ios/ios_xe/2/release/notes/rnasr21.html



Preface

OrganizationThis document contains the following chapters:

IOS XE 2.2 October 3, 2008 Updated book to document ISSU procedures for Cisco IOS XE Release 2.2. Removed ISSU procedures from the “Consolidated Packages and Sub-Package Management” chapter of the book and created the “In Service Software Upgrades (ISSU)” chapter.

IOS XE 2.2 September 23, 2008 Added troubleshooting information for Cisco ASR 1000 Embedded Services Processor 10G Non Crypto Capable New Feature

IOS XE 2.1 July 2nd, 2008 Added the “Configuring and Accessing the Web User Interface” section to the book.

Added Appendix B to the book.

IOS XE 2.1 May 2nd, 2008 First release.

Chapter Title Description

Chapter 1 Software Packaging and Architecture

Provides an introduction to Cisco ASR 1000 Series Routers software packaging, processes, and file systems.

Chapter 2 Using Cisco IOS XE Software Provides an introduction to accessing the command-line interface (CLI) and using the Cisco software and related tools.

Chapter 3 Consolidated Packages and Sub-Package Management

Provides information on downloading, installing, and running the software on the Cisco ASR 1000 Series Routers.

Chapter 4 In Service Software Upgrades (ISSU)

Provides information on ISSU compatibility and performing limited-downtime software upgrades on the Cisco ASR 1000 Series Routers.

Chapter 5 High Availability Overview Provides an overview of the High Availability architecture, behavior, and features on the Cisco ASR 1000 Series Routers.

Chapter 6 Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers

Provides information about the Call Home feature, which supports e-mail-based and web-based notification of critical system events. A versatile range of message formats are available for optimal compatibility with pager services, standard e-mail, or XML-based automated parsing applications.

Chapter 7 Console Port, Telnet, and SSH Handling

Provides an overview and configuration options for the handling of incoming console port, telnet, and SSH traffic on the Cisco ASR 1000 Series Routers.

Chapter 8 Using the Management Ethernet Interface

Provides an overview and configuration options for the Management Ethernet interface on the Cisco ASR 1000 Series Routers.

xiiiCisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08

Preface

Related DocumentationThis section refers you to other documentation that also might be useful as you configure your Cisco ASR 1000 Series Router. The documentation listed below is available online.

Cisco ASR 1000 Series Routers DocumentationThe Cisco ASR 1000 Series has a documentation roadmap that provides listings to a broad range of documentation available for the Cisco ASR 1000 Series Routers. See the Cisco ASR 1000 Series Router Documentation Roadmap at:

http://cisco.com/en/US/products/ps9343/products_documentation_roadmaps_list.html

The documentation homepage for the Cisco ASR 1000 Series Routers contains a wide variety of hardware and software information for the Cisco ASR 1000 Series Routers and can be viewed at:

http://cisco.com/en/US/products/ps9343/tsd_products_support_series_home.html

The documentation homepage for Cisco IOS XE contains Cisco IOS XE technology guides and feature documentation and can be viewed at:


For information on commands, see one of the following resources:

• Cisco IOS XE Software Command References

• Command Lookup Tool (cisco.com login required)

Chapter 9 Synchronous Ethernet Support On The Cisco ASR 1000 Series Routers

Provides an overview and configuration options for the Synchronous Ethernet on the Cisco ASR 1000 Series Routers.

Chapter 10 Configuring Bridge Domain Interfaces

Provides an overview of configuration options for the Bridge Domain Interface on the Cisco ASR 1000 Series Routers.

Chapter 11 Tracing and Trace Management Provides an overview of tracing on the Cisco ASR 1000 Series Router, and how to manage the tracing process and files.

Chapter 12 Configuring and Accessing the Web User Interface

Provides an overview of the Cisco ASR 1000 Series Router web user interface, and information on configuring and accessing the web user interface.

Chapter Title Description

xivCisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08






http://cisco.com/en/US/products/ps9587/prod_command_reference_list.html

http://tools.cisco.com/Support/CLILookup/cltSearchAction.do

Preface

Document ConventionsThis documentation uses the following conventions:

Command syntax descriptions use the following conventions:

Nested sets of square brackets or braces indicate optional or required choices within optional or required elements. For example:

Examples use the following conventions:

Convention Description

^ or Ctrl The ^ and Ctrl symbols represent the Control key. For example, the key combi-nation ^D or Ctrl-D means hold down the Control key while you press the D key. Keys are indicated in capital letters but are not case sensitive.

string A string is a nonquoted set of characters shown in italics. For example, when setting an SNMP community string to public, do not use quotation marks around the string or the string will include the quotation marks.


bold Bold text indicates commands and keywords that you enter exactly as shown.

italics Italic text indicates arguments for which you supply values.

[x] Square brackets enclose an optional element (keyword or argument).

| A vertical line indicates a choice within an optional or required set of keywords or arguments.

[x | y] Square brackets enclosing keywords or arguments separated by a vertical line indicate an optional choice.

{x | y} Braces enclosing keywords or arguments separated by a vertical line indicate a required choice.


[x {y | z}] Braces and a vertical line within square brackets indicate a required choice within an optional element.

Convention Descriptionscreen Examples of information displayed on the screen are set in Courier font.

bold screen Examples of text that you must enter are set in Courier bold font.

< > Angle brackets enclose text that is not printed to the screen, such as passwords.

! An exclamation point at the beginning of a line indicates a comment line. (Ex-clamation points are also displayed by the Cisco IOS software for certain pro-cesses.)

[ ] Square brackets enclose default responses to system prompts.

xvCisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08

Preface

The following conventions are used to attract the attention of the reader:

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

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

Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

xviCisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Cisco ASR 1000 Series AggregatOL-16506-08

C H A P T E R 1
Software Packaging and Architecture
The Cisco ASR 1000 Series Aggregation Services Routers introduce a new software packaging model and architecture.

This chapter discusses this new packaging and architecture and contains the following sections:

• Software Packaging on the Cisco ASR 1000 Series Routers, page 1-1

• Processes, page 1-5

• File Systems on the Cisco ASR 1000 Series Router, page 1-8

• Autogenerated File Directories and Files on the Cisco ASR 1000 Series Router, page 1-8

Software Packaging on the Cisco ASR 1000 Series RoutersThis section covers the following topics:

• ASR 1000 Series Routers Software Overview, page 1-1

• Consolidated Packages, page 1-2

• Individual Software Sub-Packages Within a Consolidated Package, page 1-3

• Optional Software Sub-Packages Outside of Consolidated Packages, page 1-3

• Provisioning Files, page 1-4

• ROMmon Image, page 1-5

• File to Upgrade Field Programmable Hardware Devices, page 1-5

ASR 1000 Series Routers Software OverviewThe Cisco ASR 1000 Series Routers run using Cisco IOS XE software. Cisco IOS XE is released using consolidated packages and optional sub-packages.

Each consolidated package contains a collection of software sub-packages. Each software sub-package is an individual software file that controls a different element or elements of the Cisco ASR 1000 Series Router. Each individual software sub-package can be upgraded individually, or all software sub-packages for a specific consolidated package can be upgraded as part of a complete consolidated package upgrade. Importantly, IOS (the RPIOS sub-package) is considered one of the seven individual sub-packages that makes up a complete consolidated package. For additional information on individual software sub-packages, see the “Consolidated Packages” section on page 1-2.

1-1ion Services Routers Software Configuration Guide

Chapter 1 Software Packaging and Architecture Software Packaging on the Cisco ASR 1000 Series Routers

A collection of software sub-packages packaged together creates a single consolidated package. A consolidated package allows users to upgrade all individual sub-packages on the router with a single software image download. Consolidated packages can be downloaded from Cisco.com; users who want to run the router using individual sub-packages that are part of the consolidated package must first download the image from Cisco.com and extract the individual sub-packages from the image, which can be done by entering request platform command-line interface commands.

Beginning in Cisco IOS XE Release 2.4, support for a supplemental, optional sub-package of type called “sipspawma” is introduced to support the Cisco WebEx Node for ASR 1000 Series shared port adapter (SPA). Optional sub-packages are installed similarly to individual sub-packages; however, optional sub-packages are not bundled as part of a consolidated package like prior support for the individual sub-packages, and optional sub-packages must be downloaded independently.

See the “Consolidated Packages and Sub-Package Management” chapter of this book for additional information on extracting individual sub-packages from a consolidated package, supplemental optional sub-packages, and other information on managing software.

Consolidated PackagesA consolidated package is a single image composed of individual software sub-package files. A single consolidated package file is a bootable file, and the Cisco ASR 1000 Series Router can be run using the consolidated package.

Note Consolidated packages only contain the required individual sub-package files. These packages do not contain supplemental, optional sub-packages, such as the “sipspawma” package for the Cisco WebEx Node for ASR 1000 Series.

Each consolidated package also contains a provisioning file. A provisioning file is used for booting in cases where the individual sub-packages are extracted from the consolidated package, or optional sub-packages are used to run the router. For additional information on the advantages and disadvantages of running a complete consolidated package, see the “Running the Cisco ASR 1000 Series Routers Overview” section on page 3-1. For additional information on provisioning files, see the “Provisioning Files” section on page 1-4.

For information about the consolidated packages available in a specific version of Cisco IOS XE, see the release notes for that version of Cisco IOS XE. The Cisco IOS XE Software Release Notes page contains the release notes for each version of Cisco IOS XE.

Important Information about Consolidated Packages

• For each version of a consolidated package, the RPBase, RPControl, ESPBase, SIPSPA, and SIPBase sub-packages are identical among consolidated packages.

• For each version of consolidated package, the RPIOS sub-package is always different among consolidated packages.

• A consolidated package file is a bootable file. If the router is configured to run using a the complete consolidated package, boot the router using the consolidated package file. If the router is configured to run using individual sub-packages, boot the router using the provisioning file. For additional information on the advantages and disadvantages of running a complete consolidated package, see the “Running the Cisco ASR 1000 Series Routers Overview” section on page 3-1. For additional information on provisioning files, see the “Provisioning Files” section on page 1-4.

1-2Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08

http://www.cisco.com/en/US/products/ps9587/prod_release_notes_list.html


• If you need to install optional sub-packages, then you must boot the router using the individual sub-package provisioning file method.

Individual Software Sub-Packages Within a Consolidated PackageTable 1-1 provides an overview of the Cisco ASR 1000 Series Routers sub-packages and the purpose of each individual sub-package. Every consolidated package will have all of these individual sub-packages. To see additional information about each individual sub-packages in a particular Cisco IOS XE release, see the Cisco IOS XE Release Notes for that release.

Table 1-1 Individual Sub-Packages

Important Notes about Individual Sub-Packages

• Individual sub-packages cannot be downloaded from Cisco.com individually. To get these individual sub-packages, users must download a consolidated package and then extract the individual sub-packages from the consolidated package using the command-line interface.

• If the router is being run using individual sub-packages instead of being run using a complete consolidated package, the router must be booted using a provisioning file. A provisioning file is included in all consolidated packages and is extracted from the image along with the individual sub-packages whenever individual sub-packages are extracted. For additional information on provisioning files, see the “Provisioning Files” section on page 1-4.

Optional Software Sub-Packages Outside of Consolidated PackagesBeginning in Cisco IOS XE Release 2.4, the ASR 1000 Series Routers support a new type of sub-package—this is an optional software sub-package that is available as a separate, external package that is downloaded and installed along with the other required sub-packages (See Table 1-2).

Sub-Package Purpose

RPBase Provides the operating system software for the Route Processor.

RPControl Controls the control plane processes that interface between the IOS process and the rest of the platform.

RPAccess Exports processing of restricted components, such as Secure Socket Layer (SSL), Secure Shell (SSH), and other security features.

RPIOS Provides the Cisco IOS kernel, which is where IOS features are stored and run.

Each consolidated package has a different RPIOS.

ESPBase Provides the ESP operating system and control processes, and the ESP software.

SIPBase Controls the SIP operating system and control processes.

SIPSPA Provides the SPA driver and Field Programmable Device (FPD) images.


OL-16506-08



Table 1-2 Optional Sub-Packages

Important Notes About Optional Sub-Packages

• Optional sub-packages are downloaded separately from consolidated package files. Optional sub-packages are not contained within a consolidated package for a release.

• Optional package installation works similarly to the installation of individual sub-packages using a provisioning file.

• Optional sub-packages can be uninstalled to remove provisioning when the package no longer applies to an RP.

• Optional sub-packages are easily supported by the standard ISSU upgrade process as long as the package is located in the directory of the provisioning file for each RP.

Provisioning Files

Note You must use the provisioning file to manage the boot process if you need to install optional sub-packages.

Provisioning files manage the boot process when the Cisco ASR 1000 Series Router is configured to run using individual sub-packages or optional sub-packages (such as the package for the Cisco WebEx Node for ASR 1000 Series). When individual sub-packages are being used to run the Cisco ASR 1000 Series Router, the router has to be configured to boot the provisioning file. The provisioning file manages the bootup of each individual sub-package and the Cisco ASR 1000 Series Router assumes normal operation.

Provisioning files are extracted automatically when individual sub-package files are extracted from a consolidated package.

Provisioning files are not necessary for running the router using the complete consolidated package; if you want to run the router using the complete consolidated package, simply boot the router using the consolidated package file.

See the “Running the Cisco ASR 1000 Series Routers Overview” section on page 3-1 for additional information on the advantages and disadvantages of running individual sub-packages versus running a complete consolidated package.

Important Information about Provisioning Files

• Each consolidated package contains two provisioning files. One of the provisioning files is always named “packages.conf”, while the other provisioning file will have a name based on the consolidated package naming structure. In any consolidated package, both provisioning files perform the exact same function.

Sub-Package Purpose

sipspawmak9 Standalone package that provides the system software for the Cisco WebEx Node for ASR 1000 Series.


OL-16506-08

Chapter 1 Software Packaging and Architecture Processes

• In most cases, the “packages.conf” provisioning file should be used to boot the router. Configuring the router to boot using this file is generally easier because the router can be configured to boot using “packages.conf”, so no changes have to be made to the boot statement when Cisco IOS XE is upgraded (the boot system file-system:packages.conf configuration command can remain unmodified before and after an upgrade).

• The provisioning file and individual sub-package files must be kept in the same directory. The provisioning file does not work properly if the individual sub-package files are in other directories.

• The provisioning filename can be renamed; the individual sub-package filenames cannot be renamed.

• After placing the provisioning file and the individual sub-package files in a directory and booting the router, it is highly advisable not to rename, delete, or alter any of these files. Renaming, deleting, or altering the files can lead to unpredictable router problems and behaviors.

ROMmon ImageAn independent ROMmon image is released periodically separate from consolidated packages or any other software releases.

See the documentation that accompanies the ROMmon image for information on each ROMmon image. The ROMmon documents are kept on the Cisco ASR 1000 Series Routers Maintain and Operate Guides documentation section on cisco.com

File to Upgrade Field Programmable Hardware DevicesStarting in Cisco IOS XE Release 3.1.0S, a hardware programmable package file used to upgrade field programmable hardware devices is released as needed. A package file is provided for the field programmable device to customers in cases where a field upgrade is required. If the Cisco ASR 1000 Series Router contains an incompatible version of the hardware programmable firmware on the Cisco ASR1000-RP, Cisco ASR1000-SIP, or Cisco ASR1000-ESP, then that firmware may need to be upgraded.

Generally an upgrade is only necessary in cases where a system message indicates one of the field programmable devices on the Cisco ASR 1000 Series Router needs an upgrade or a Cisco technical support representative suggests an upgrade.

In Cisco IOS XE Release 3.1.0S, a package file that contains a new version of the Complex Programmable Logic Device (CPLD) code is available for users who need to upgrade old versions of firmware on a Cisco ASR1000-RP2 or Cisco ASR1000-SIP10 in a Cisco ASR 1013 Router.

For more information on upgrading field programmable hardware devices, see the Upgrading Field Programmable Hardware Devices for Cisco ASR 1000 Series Routers document.

ProcessesThis section covers the following topics:

• Processes Overview, page 1-6

• IOS as a Process, page 1-7

• Dual IOS Processes, page 1-7


OL-16506-08

http://www.cisco.com/en/US/products/ps9343/prod_maintenance_guides_list.html

http://www.cisco.com/en/US/docs/routers/asr1000/cpld/hw_fp_upgrade.html


Processes OverviewCisco IOS XE has numerous components that run entirely as separate processes on the Cisco ASR 1000 Series Routers. This modular architecture increases network resiliency by distributing operating responsibility among separate processes rather than relying on Cisco IOS software for all operations.

Table 1-3 provides a list of the important individual processes for the Cisco ASR 1000 Series Routers. These processes run in the background, and the CLI on Cisco ASR 1000 Series Routers using Cisco IOS-XE is identical in look, feel, and usage to the Cisco IOS CLI on most platforms. This information is provided because it may be useful for checking router state and troubleshooting, but understanding this information is not essential to understanding most router operations.

Table 1-3 Individual Processes

Process Purpose Affected FRUsSub-Package Mapping

Chassis Manager Responsible for all chassis management functions, including management of the HA state, environmental monitoring, and FRU state control.

RP (one instance per RP) SIP (one instance per SIP) ESP (one instance per ESP)

RPControl SIPBase ESPBase

Host Manager Provides an interface between the IOS process and many of the information-gathering functions of the underlying platform kernel and operating system.



Logger Provides IOS facing logging services to processes running on each FRU.



Interface Manager Provides an interface between the IOS process and the per-SPA interface processes on the SIP.

RP (one instance per RP) SIP (one instance per SIP)

RPControl SIPBase

IOS The IOS process implements all forwarding and routing features for the router.

RP (one per software redundancy instance per RP). Maximum of two instances per RP.

RPIOS

Forwarding Manager Manages the downloading of configuration to each of the ESPs and the communication of forwarding plane information, such as statistics, to the IOS process.

RP (one per software redundancy instance per RP). Maximum of two instances per RP. ESP (one per ESP)

RPControl

ESPBase


OL-16506-08


IOS as a Process

In almost all previous Cisco router platforms, an overwhelming majority of the internal software processes are run using Cisco IOS memory.

The Cisco ASR 1000 Series Routers introduce a distributed software architecture that moves many operating system responsibilities out of the IOS process. In this architecture, IOS, which previously was responsible for almost all of the internal software processes, now runs as one of many Linux processes while allowing other Linux processes to share responsibility for running the router.

This architecture allows for better allocation of memory so the router can run more efficiently. Furthermore, the Cisco ASR 1000 Series Routers has a command-line interface in diagnostic mode that can be accessed in certain scenarios even if the IOS process fails. See the “Understanding Diagnostic Mode” section on page 2-8 for information on diagnostic mode.

Dual IOS Processes

The Cisco ASR 1000 Series Router introduces a dual IOS process model that allows for increased high availability at all times.

Using SSO or RPR, a second IOS process can be enabled on a Cisco ASR 1002 or 1004 Router. On Cisco ASR 1000 Series Routers configured with dual Route Processors, the second IOS process runs on the standby Route Processor.

The state of these dual IOS processes can be checked by entering the show platform command.

Pluggable Services The integration point between platform policy application, such as authentication and the IOS process.

RP (one per software redundancy instance per RP). Maximum of two instances per RP.

RPControl

Shell Manager Provides all user interface features and handling related to features in the non-IOS image of the consolidated package, which are also the features available in diagnostic mode when the IOS process fails.

RP (one instance per RP)

RPControl

SPA driver process Provides an isolated process driver for a specific SPA.

SPA (one instance per SPA per SIP)

SIPSPA

CPP driver process Manages the CPP hardware forwarding engine on the ESP.

ESP (one instance per ESP)

ESPBase

CPP HA process Manages HA state for the CPP hardware forwarding engine.


ESPBase

CPP SP process Performs high-latency tasks for the CPP-facing functionality in the ESP instance of the Forwarding Manager process.


ESPBase

Process Purpose Affected FRUsSub-Package Mapping


OL-16506-08


The advantages of a second IOS process includes:

• Increased fault tolerance—In the event of an active IOS failure, the second IOS process immediately becomes the active IOS process with little to no service disruption.

• No downtime software upgrades—IOS and other software on the router can be upgraded using the In Service Software Upgrade (ISSU) feature in the standby IOS process, thereby allowing the network to remain active during the software upgrade. See the “Router#” section on page 3-20 for additional information on when ISSU can and cannot be used to perform no downtime software upgrades.

File Systems on the Cisco ASR 1000 Series RouterTable 1-4 provides a list of file systems that can be seen on the Cisco ASR 1000 Series Routers.

If you run into a file system not listed in Table 1-4, enter the ? help option or see the copy command reference for additional information on that file system.

Autogenerated File Directories and Files on the Cisco ASR 1000 Series RouterThis section discusses the autogenerated files and directories that might appear on your Cisco ASR 1000 Series Routers, and how the files in these directories can be managed.

Table 1-5 provides a list and descriptions of autogenerated files on the Cisco ASR 1000 Series Routers.

Table 1-4 File Systems

File System Description

bootflash: The boot flash memory file system on the active RP.

cns: The Cisco Networking Services file directory.

harddisk: The hard disk file system on the active RP.

The harddisk: file system is not available on the Cisco ASR 1002 Routers.

nvram: Router NVRAM. You can copy the startup configuration to NVRAM or from NVRAM.

obfl: The file system for Onboard Failure Logging files.

stby-bootflash: The boot flash memory file system on the standby RP.

stby-harddisk: The hard disk file system on the standby RP.

The harddisk: file system is not available on the Cisco ASR 1002 Routers.

stby-usb[0-1]: The Universal Serial Bus (USB) flash drive file systems on the standby RP.

The stby-usb: file system is not available on the Cisco ASR 1002 Routers.

system: The system memory file system, which includes the running configuration.

tar: The archive file system.

tmpsys: The temporary system files file system.

usb[0-1]: The Universal Serial Bus (USB) flash drive file systems on the active RP.

Only usb0: is available on the Cisco ASR 1002 Router.


OL-16506-08


Important Notes Regarding Autogenerated Directories

• Any autogenerated file on the bootflash: directory should not be deleted, renamed, moved, or altered in any way unless directed by customer support. Altering autogenerating files on the bootflash: can have unpredictable consequences for system performance.

• Crashinfo, core, and trace files can be deleted, but the core and tracelog directories that are automatically part of the harddisk: file system should not be deleted.

Table 1-5 Autogenerated Files

File or Directory Description

crashinfo files A crashinfo file may appear in the bootflash: or harddisk: file system.

These files provide descriptive information of a crash and may be useful for tuning or troubleshooting purposes, but the files are not part of router operations and can be erased without impacting the functioning of the router.

core directory The storage area for .core files.

If this directory is erased, it will automatically regenerate itself at bootup. The .core files in this directory can be erased without impacting any router functionality, but the directory itself should not be erased.

lost+found directory This directory is created on bootup if a system check is performed. Its appearance is completely normal and does not indicate any issues with the router.

tracelogs directory The storage area for trace files.

Trace files are useful for troubleshooting; if the IOS process fails, for instance, users or troubleshooting personnel can access trace files using diagnostic mode to gather information related to the IOS failure.

Trace files, however, are not part of router operations and can be erased without impacting the router’s performance.


OL-16506-08



OL-16506-08


C H A P T E R 2
Using Cisco IOS XE Software
This chapter provides information to prepare you to configure the Cisco ASR 1000 Series Routers:

• Accessing the CLI Using a Router Console, page 2-1

• Using the Auxiliary Port, page 2-4

• Using Keyboard Shortcuts, page 2-4

• Using the History Buffer to Recall Commands, page 2-5

• Understanding Command Modes, page 2-6

• Understanding Diagnostic Mode, page 2-8

• Getting Help, page 2-9

• Using the no and default Forms of Commands, page 2-12

• Saving Configuration Changes, page 2-13

• Managing Configuration Files, page 2-13

• Filtering Output from the show and more Commands, page 2-14

• Powering Off the Router, page 2-15

• Finding Support Information for Platforms and Cisco Software Images, page 2-15

Accessing the CLI Using a Router ConsoleThe following sections describe how to access the command-line interface (CLI) using a directly-connected console or by using Telnet or a modem to obtain a remote console:

• Accessing the CLI Using a Directly-Connected Console, page 2-1

• Accessing the CLI from a Remote Console Using Telnet, page 2-3

• Accessing the CLI from a Remote Console Using a Modem, page 2-4

Accessing the CLI Using a Directly-Connected ConsoleThis section describes how to connect to the console port on the router and use the console interface to access the CLI.


Chapter 2 Using Cisco IOS XE Software Accessing the CLI Using a Router Console

The console port on a Cisco ASR 1000 Series Router is an EIA/TIA-232 asynchronous, serial connection with no flow control and an RJ-45 connector. The console port is located on the front panel of each Route Processor (RP).

Connecting to the Console Port

Before you can use the console interface on the router using a terminal or PC, you must perform the following steps:

Step 1 Configure your terminal emulation software with the following settings:

• 9600 bits per second (bps)

• 8 data bits

• No parity

• 1 stop bit

• No flow control

Step 2 Connect to the port using the RJ-45-to-RJ-45 cable and RJ-45-to-DB-25 DTE adapter or using the RJ-45-to-DB-9 DTE adapter (labeled “Terminal”).

Using the Console Interface

Every RP on a Cisco ASR 1000 Series Router has a console interface. Notably, a standby RP can be accessed using the console port in addition to the active RP in a dual RP configuration.

To access the CLI using the console interface, complete the following steps:

Step 1 After you attach the terminal hardware to the console port on the router and you configure your terminal emulation software with the proper settings, the following prompt appears:

Press RETURN to get started.

Step 2 Press Return to enter user EXEC mode. The following prompt appears:

Router>

Step 3 From user EXEC mode, enter the enable command as shown in the following example:

Router> enable

Step 4 At the password prompt, enter your system password. If an enable password has not been set on your system, this step may be skipped. The following example shows entry of the password called “enablepass”:

Password: enablepass

Step 5 When your enable password is accepted, the privileged EXEC mode prompt appears:

Router#

Step 6 You now have access to the CLI in privileged EXEC mode and you can enter the necessary commands to complete your desired tasks.

Step 7 To exit the console session, enter the quit command as shown in the following example:


OL-16506-08

Chapter 2 Using Cisco IOS XE Software Accessing the CLI Using a Router Console

Router# quit

Accessing the CLI from a Remote Console Using TelnetThis section describes how to connect to the console interface on a router using Telnet to access the CLI.

Preparing to Connect to the Router Console Using Telnet

Before you can access the router remotely using Telnet from a TCP/IP network, you need to configure the router to support virtual terminal lines (vtys) using the line vty global configuration command. You also should configure the vtys to require login and specify a password.

Note To prevent disabling login on the line, be careful that you specify a password with the password command when you configure the login line configuration command. If you are using authentication, authorization, and accounting (AAA), you should configure the login authentication line configuration command. To prevent disabling login on the line for AAA authentication when you configure a list with the login authentication command, you must also configure that list using the aaa authentication login global configuration command. For more information about AAA services, refer to the Cisco IOS XE Security Configuration Guide, Release 2 and Cisco IOS Security Command Reference publications.

In addition, before you can make a Telnet connection to the router, you must have a valid host name for the router or have an IP address configured on the router. For more information about requirements for connecting to the router using Telnet, information about customizing your Telnet services, and using Telnet key sequences, refer to the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2SR.

Using Telnet to Access a Console Interface

To access a console interface using Telnet, complete the following steps:

Step 1 From your terminal or PC, enter one of the following commands:

• connect host [port] [keyword]

• telnet host [port] [keyword]

In this syntax, host is the router hostname or an IP address, port is a decimal port number (23 is the default), and keyword is a supported keyword. For more information, refer to the Cisco IOS Configuration Fundamentals Command Reference.

Note If you are using an access server, then you will need to specify a valid port number such as telnet 172.20.52.40 2004, in addition to the hostname or IP address.

The following example shows the telnet command to connect to the router named “router”:

unix_host% telnet routerTrying 172.20.52.40...Connected to 172.20.52.40.Escape character is '^]'.


OL-16506-08

Chapter 2 Using Cisco IOS XE Software Using the Auxiliary Port

unix_host% connect

Step 2 At the password prompt, enter your login password. The following example shows entry of the password called “mypass”:

User Access Verification

Password: mypass

Note If no password has been configured, press Return.

Step 3 From user EXEC mode, enter the enable command as shown in the following example:

Router> enable

Step 4 At the password prompt, enter your system password. The following example shows entry of the password called “enablepass”:

Password: enablepass

Step 5 When the enable password is accepted, the privileged EXEC mode prompt appears:

Router#

Step 6 You now have access to the CLI in privileged EXEC mode and you can enter the necessary commands to complete your desired tasks.

Step 7 To exit the Telnet session, use the exit or logout command as shown in the following example:

Router# logout

Accessing the CLI from a Remote Console Using a ModemTo access the router remotely using a modem through an asynchronous connection, connect the modem to the console port.

The console port on a Cisco 7600 series router is an EIA/TIA-232 asynchronous, serial connection with no flow control and an RJ-45 connector. The console port is located on the front panel of the RP.

To connect a modem to the console port, place the console port mode switch in the in position. Connect to the port using the RJ-45-to-RJ-45 cable and the RJ-45-to-DB-25 DCE adapter (labeled “Modem”).

Using the Auxiliary PortThe auxiliary port on the Route Processor does not serve any useful purpose for customers.

This port should only be accessed under the advisement of a customer support representative.

Using Keyboard ShortcutsCommands are not case sensitive. You can abbreviate commands and parameters if the abbreviations contain enough letters to be different from any other currently available commands or parameters.


OL-16506-08

Chapter 2 Using Cisco IOS XE Software Using the History Buffer to Recall Commands

Table 2-1 lists the keyboard shortcuts for entering and editing commands.

Using the History Buffer to Recall CommandsThe history buffer stores the last 20 commands you entered. History substitution allows you to access these commands without retyping them, by using special abbreviated commands.

Table 2-2 lists the history substitution commands.

Table 2-1 Keyboard Shortcuts

Keystrokes Purpose

Ctrl-B or the Left Arrow key1

Move the cursor back one character

Ctrl-F or the Right Arrow key1

Move the cursor forward one character

Ctrl-A Move the cursor to the beginning of the command line

Ctrl-E Move the cursor to the end of the command line

Esc B Move the cursor back one word

Esc F Move the cursor forward one word

1. The arrow keys function only on ANSI-compatible terminals such as VT100s.

Table 2-2 History Substitution Commands

Command Purpose

Ctrl-P or the Up Arrow key1 Recall 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 key1 Return to more recent commands in the history buffer after recalling commands with Ctrl-P or the Up Arrow key.

Router# show history While in EXEC mode, list the last several commands you have just entered.

1. The arrow keys function only on ANSI-compatible terminals such as VT100s.


OL-16506-08

Chapter 2 Using Cisco IOS XE Software Understanding Command Modes

Understanding Command ModesThe command modes available in the traditional Cisco IOS CLI are exactly the same as the command modes available in Cisco IOS XE.

You use the CLI to access Cisco IOS XE software. Because the CLI is divided into many different modes, the commands available to you at any given time depend on the mode that you are currently in. Entering a question mark (?) at the CLI prompt allows you to obtain a list of commands available for each command mode.

When you log in to the CLI, you are in user EXEC mode. User EXEC mode contains only a limited subset of commands. To have access to all commands, you must enter privileged EXEC mode, normally by using a password. From privileged EXEC mode, you can issue any EXEC command—user or privileged mode—or you can enter global configuration mode. Most EXEC commands are one-time commands. For example, show commands show important status information, and clear commands clear counters or interfaces. The EXEC commands are not saved when the software reboots.

Configuration modes allow you to make changes to the running configuration. If you later save the running configuration to the startup configuration, these changed commands are stored when the software is rebooted. To enter specific configuration modes, you must start at global configuration mode. From global configuration mode, you can enter interface configuration mode and a variety of other modes, such as protocol-specific modes.

ROM monitor mode is a separate mode used when the Cisco IOS XE software cannot load properly. If a valid software image is not found when the software boots or if the configuration file is corrupted at startup, the software might enter ROM monitor mode.

Table 2-3 describes how to access and exit various common command modes of the Cisco IOS XE software. It also shows examples of the prompts displayed for each mode.

Table 2-3 Accessing and Exiting Command Modes

Command Mode Access Method Prompt Exit Method

User EXEC Log in. Router> Use the logout command.

Privileged EXEC

From user EXEC mode, use the enable EXEC command.

Router# To return to user EXEC mode, use the disable command.

Global config-uration

From privileged EXEC mode, use the configure terminal privileged EXEC command.

Router(config)# To return to privileged EXEC mode from global configuration mode, use the exit or end command.

Interface con-figuration

From global configura-tion mode, specify an interface using an interface command.

Router(config-if)# To return to global configuration mode, use the exit command.

To return to privileged EXEC mode, use the end command.


OL-16506-08

Chapter 2 Using Cisco IOS XE Software Understanding Command Modes

Diagnostic The router boots up or accesses diagnostic mode in the following scenarios:

• In some cases, diagnostic mode will be reached when the IOS process or processes fail. In most scenarios, however, the router will reload.

• A user-configured access policy was configured using the transport-map command that directed the user into diagnostic mode. See the “Console Port, Telnet, and SSH Handling” chapter of this book for information on configuring access policies.

• The router was accessed using a Route Processor auxiliary port.

• A break signal (Ctrl-C, Ctrl-Shift-6, or the send break command) was entered and the router was configured to go into diagnostic mode when the break signal was received.

Router(diag)# If the IOS process failing is the reason for entering diagnostic mode, the IOS problem must be resolved and the router rebooted to get out of diagnostic mode.

If the router is in diagnostic mode because of a trans-port-map configuration, access the router through another port or using a method that is configured to connect to the Cisco IOS CLI.

If the router is accessed through the Route Processor auxiliary port, access the router through another port. Accessing the router through the auxiliary port is not useful for customer purposes anyway.

Table 2-3 Accessing and Exiting Command Modes (continued)



OL-16506-08

Chapter 2 Using Cisco IOS XE Software Understanding Diagnostic Mode

Understanding Diagnostic ModeDiagnostic mode is new on the Cisco ASR 1000 Series Routers.

The router boots up or accesses diagnostic mode in the following scenarios:

• The IOS process or processes fail, in some scenarios. In other scenarios, the RP will simply reset when the IOS process or processes fail.

• A user-configured access policy was configured using the transport-map command that directs the user into diagnostic mode.

• The router was accessed using a Route Processor auxiliary port.

• A send break signal (Ctrl-C or Ctrl-Shift-6) was entered while accessing the router, and the router was configured to enter diagnostic mode when a break signal was sent.

In diagnostic mode, a subset of the commands that are also available in User EXEC mode are made available to users. Among other things, these commands can be used to:

• Inspect various states on the router, including the IOS state.

• Replace or roll back the configuration.

• Provide methods of restarting the IOS or other processes.

• Reboot hardware, such as the entire router, an RP, an ESP, a SIP, a SPA, or possibly other hardware components.

• Transfer files into or off of the router using remote access methods such as FTP, TFTP, SCP, and so on.

The diagnostic mode provides a more comprehensive user interface for troubleshooting than previous routers, which relied on limited access methods during failures, such as ROMmon, to diagnose and troubleshoot IOS problems.

The diagnostic mode commands are stored in the non-IOS packages on the Cisco ASR 1000 Series Routers, which is why the commands are available even if the IOS process is not working properly. Importantly, all the commands available in diagnostic mode are also available in privileged EXEC mode on the router even during normal router operation. The commands are entered like any other commands in the privileged EXEC command prompts when used in privileged EXEC mode.

ROM monitor From privileged EXEC mode, use the reload EXEC command. Press the Break key during the first 60 seconds while the system is booting.

> To exit ROM monitor mode, use the continue command.

Table 2-3 Accessing and Exiting Command Modes (continued)



OL-16506-08

Chapter 2 Using Cisco IOS XE Software Getting Help

Getting HelpEntering a question mark (?) at the CLI prompt displays a list of commands available for each command mode. You can also get a list of keywords and arguments associated with any command by using the context-sensitive help feature.

To get help specific to a command mode, a command, a keyword, or an argument, use one of the following commands:

Finding Command Options ExampleThis section provides an example of how to display syntax for a command. The syntax can consist of optional or required keywords and arguments. To display keywords and arguments for a command, enter a question mark (?) at the configuration prompt or after entering part of a command followed by a space. The Cisco IOS XE software displays a list and brief description of available keywords and arguments. For example, if you were in global configuration mode and wanted to see all the keywords or arguments for the arap command, you would type arap ?.

The <cr> symbol in command help output stands for “carriage return.” On older keyboards, the carriage return key is the Return key. On most modern keyboards, the carriage return key is the Enter key. The <cr> symbol at the end of command help output indicates that you have the option to press Enter to complete the command and that the arguments and keywords in the list preceding the <cr> symbol are optional. The <cr> symbol by itself indicates that no more arguments or keywords are available and that you must press Enter to complete the command.

Table 2-5 shows examples of how you can use the question mark (?) to assist you in entering commands.

Table 2-4 Help Commands and Purpose

Command Purpose

help Provides a brief description of the help system in any command mode.

abbreviated-command-entry? Provides a list of commands that begin with a particular character string. (No space between command and question mark.)

abbreviated-command-entry<Tab> Completes a partial command name.

? Lists all commands available for a particular command mode.

command ? Lists the keywords or arguments that you must enter next on the command line. (Space between command and question mark.)


OL-16506-08


Table 2-5 Finding Command Options

Command Comment

Router> enablePassword: <password>Router#

Enter the enable command and password to access privileged EXEC commands. You are in privileged EXEC mode when the prompt changes to a “#” from the “>”; for example, Router> to Router#.

Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#

Enter the configure terminal privileged EXEC command to enter global config-uration mode. You are in global config-uration mode when the prompt changes to Router(config)#.

Router(config)# interface serial ? <0-6> Serial interface numberRouter(config)# interface serial 4 ? /Router(config)# interface serial 4/ ? <0-3> Serial interface numberRouter(config)# interface serial 4/0 ?<cr>Router(config)# interface serial 4/0Router(config-if)#

Enter interface configuration mode by specifying the serial interface that you want to configure using the interface serial global configuration command.

Enter ? to display what you must enter next on the command line. In this example, you must enter the serial interface slot number and port number, separated by a forward slash.

When the <cr> symbol is displayed, you can press Enter to complete the command.

You are in interface configuration mode when the prompt changes to Rout-er(config-if)#.


OL-16506-08


Router(config-if)# ?Interface configuration commands: . . . ip Interface Internet Protocol config commands keepalive Enable keepalive lan-name LAN Name command llc2 LLC2 Interface Subcommands load-interval Specify interval for load calculation for an interface locaddr-priority Assign a priority group logging Configure logging for interface loopback Configure internal loopback on an interface mac-address Manually set interface MAC address mls mls router sub/interface commands mpoa MPOA interface configuration commands mtu Set the interface Maximum Transmission Unit (MTU) netbios Use a defined NETBIOS access list or enable name-caching no Negate a command or set its defaults nrzi-encoding Enable use of NRZI encoding ntp Configure NTP . . .Router(config-if)#

Enter ? to display a list of all the interface configuration commands available for the serial interface. This example shows only some of the available interface configuration commands.

Router(config-if)# ip ?Interface IP configuration subcommands: access-group Specify access control for packets accounting Enable IP accounting on this interface address Set the IP address of an interface authentication authentication subcommands bandwidth-percent Set EIGRP bandwidth limit broadcast-address Set the broadcast address of an interface cgmp Enable/disable CGMP directed-broadcast Enable forwarding of directed broadcasts dvmrp DVMRP interface commands hello-interval Configures IP-EIGRP hello interval helper-address Specify a destination address for UDP broadcasts hold-time Configures IP-EIGRP hold time . . .Router(config-if)# ip

Enter the command that you want to configure for the interface. This example uses the ip command.

Enter ? to display what you must enter next on the command line. This example shows only some of the available interface IP configuration commands.

Table 2-5 Finding Command Options (continued)

Command Comment


OL-16506-08

Chapter 2 Using Cisco IOS XE Software Using the no and default Forms of Commands

Using the no and default Forms of CommandsAlmost every configuration command has a no form. In general, use the no form to disable a function. Use the command without the no keyword to re-enable a disabled function or to enable a function that is disabled by default. For example, IP routing is enabled by default. To disable IP routing, use the no ip routing command; to re-enable IP routing, use the ip routing command. The Cisco IOS software command reference publications provide the complete syntax for the configuration commands and describe what the no form of a command does.

Router(config-if)# ip address ? A.B.C.D IP address negotiated IP Address negotiated over PPPRouter(config-if)# ip address

Enter the command that you want to configure for the interface. This example uses the ip address command.

Enter ? to display what you must enter next on the command line. In this example, you must enter an IP address or the negotiated keyword.

A carriage return (<cr>) is not dis-played; therefore, you must enter addi-tional keywords or arguments to complete the command.

Router(config-if)# ip address 172.16.0.1 ? A.B.C.D IP subnet maskRouter(config-if)# ip address 172.16.0.1

Enter the keyword or argument that you want to use. This example uses the 172.16.0.1 IP address.

Enter ? to display what you must enter next on the command line. In this example, you must enter an IP subnet mask.

A <cr> is not displayed; therefore, you must enter additional keywords or arguments to complete the command.

Router(config-if)# ip address 172.16.0.1 255.255.255.0 ? secondary Make this IP address a secondary address <cr>Router(config-if)# ip address 172.16.0.1 255.255.255.0

Enter the IP subnet mask. This example uses the 255.255.255.0 IP subnet mask.

Enter ? to display what you must enter next on the command line. In this example, you can enter the secondary keyword, or you can press Enter.

A <cr> is displayed; you can press Enter to complete the command, or you can enter another keyword.

Router(config-if)# ip address 172.16.0.1 255.255.255.0Router(config-if)#

In this example, Enter is pressed to complete the command.

Table 2-5 Finding Command Options (continued)

Command Comment


OL-16506-08

Chapter 2 Using Cisco IOS XE Software Saving Configuration Changes

Many CLI commands also have a default form. By issuing the command default command-name, you can configure the command to its default setting. The Cisco IOS software command reference publications describe the function of the default form of the command when the default form performs a different function than the plain and no forms of the command. To see what default commands are available on your system, enter default ? in the appropriate command mode.

Saving Configuration ChangesUse the copy running-config startup-config command to save your configuration changes to the startup configuration so that the changes will not be lost if the software reloads or a power outage occurs. For example:

Router# copy running-config startup-configBuilding configuration...

It might take a minute or two to save the configuration. After the configuration has been saved, the following output appears:

[OK]Router#

This task saves the configuration to NVRAM.

Managing Configuration FilesOn the Cisco ASR 1000 Series Routers, the startup configuration file is stored in the nvram: file system and the running-configuration files are stored in the system: file system. This configuration file storage setup is not unique to the Cisco ASR 1000 Series Routers and is used on several Cisco router platforms.

As a matter of routine maintenance on any Cisco router, users should backup the startup configuration file by copying the startup configuration file from NVRAM onto one of the router’s other file systems and, additionally, onto a network server. Backing up the startup configuration file provides an easy method of recovering the startup configuration file in the event the startup configuration file in NVRAM becomes unusable for any reason.

The copy command can be used to backup startup configuration files. Below are some examples showing the startup configuration file in NVRAM being backed up:

Example 1: Copying Startup Configuration File to BootflashRouter# dir bootflash:Directory of bootflash:/

11 drwx 16384 Dec 4 2007 04:32:46 -08:00 lost+found86401 drwx 4096 Dec 4 2007 06:06:24 -08:00 .ssh14401 drwx 4096 Dec 4 2007 06:06:36 -08:00 .rollback_timer28801 drwx 4096 May 29 2008 16:31:41 -07:00 .prst_sync43201 drwx 4096 Dec 4 2007 04:34:45 -08:00 .installer 12 -rw- 208904396 May 28 2008 16:17:34 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin

Router# copy nvram:startup-config bootflash:Destination filename [startup-config]?

3517 bytes copied in 0.647 secs (5436 bytes/sec)


OL-16506-08

Chapter 2 Using Cisco IOS XE Software Filtering Output from the show and more Commands

Router# dir bootflash:Directory of bootflash:/

11 drwx 16384 Dec 4 2007 04:32:46 -08:00 lost+found86401 drwx 4096 Dec 4 2007 06:06:24 -08:00 .ssh14401 drwx 4096 Dec 4 2007 06:06:36 -08:00 .rollback_timer28801 drwx 4096 May 29 2008 16:31:41 -07:00 .prst_sync43201 drwx 4096 Dec 4 2007 04:34:45 -08:00 .installer 12 -rw- 208904396 May 28 2008 16:17:34 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin13 -rw- 7516 Jul 2 2008 15:01:39 -07:00 startup-config

Example 2: Copying Startup Configuration File to USB Flash DiskRouter# dir usb0:Directory of usb0:/

43261 -rwx 208904396 May 27 2008 14:10:20 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin

255497216 bytes total (40190464 bytes free)

Router# copy nvram:startup-config usb0:Destination filename [startup-config]?


Router# dir usb0:Directory of usb0:/

43261 -rwx 208904396 May 27 2008 14:10:20 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin43262 -rwx 3172 Jul 2 2008 15:40:45 -07:00 startup-config


Example 3: Copying Startup Configuration File to a TFTP ServerRouter# copy bootflash:startup-config tftp:Address or name of remote host []? 172.17.16.81Destination filename [pe24_asr-1002-confg]? /auto/tftp-users/user/startup-config!!3517 bytes copied in 0.122 secs (28828 bytes/sec)

For more detailed information on managing configuration files, see the “Managing Configuration Files” section in the Cisco IOS XE Configuration Fundamentals Configuration Guide, Release 2.

Filtering Output from the show and more CommandsYou can search and filter the output of show and more commands. This functionality is useful if you need to sort through large amounts of output or if you want to exclude output that you need not see.

To use this functionality, enter a show or more command followed by the “pipe” character ( | ); one of the keywords begin, include, or exclude; and a regular expression on which you want to search or filter (the expression is case sensitive):

show command | {append | begin | exclude | include | redirect | section | tee} regular-expression


OL-16506-08

http://www.cisco.com/en/US/docs/ios/ios_xe/fundamentals/configuration/guide/cf_config-files_xe.html

http://www.cisco.com/en/US/docs/ios/fundamentals/configuration/guide/cf_config-files_ps6922_TSD_Products_Configuration_Guide_Chapter.html

http://www.cisco.com/en/US/docs/ios/fundamentals/configuration/guide/12_2sr/cf_12_2sr_book.html

http://www.cisco.com/en/US/docs/ios/ios_xe/fundamentals/configuration/guide/2_xe/cf_xe_book.html

Chapter 2 Using Cisco IOS XE Software Powering Off the Router

The output matches certain lines of information in the configuration file. The following example illustrates how to use output modifiers with the show interface command when you want the output to include only lines in which the expression “protocol” appears:

Router# show interface | include protocol

FastEthernet0/0 is up, line protocol is upSerial4/0 is up, line protocol is upSerial4/1 is up, line protocol is upSerial4/2 is administratively down, line protocol is downSerial4/3 is administratively down, line protocol is down

Powering Off the RouterBefore you turn off a power supply, make certain the chassis is grounded and you perform a soft shutdown on the power supply. Not performing a soft shutdown will often not harm the router, but may cause problems in certain scenarios.

To perform a soft shutdown before powering off the router, enter the reload command to halt the system and then wait for ROM Monitor to execute before proceeding to the next step.

The following screenshot shows an example of this process:

Router# reloadProceed with reload? [confirm]

*Jun 18 19:38:21.870: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload command.

Place the power supply switch in the Off position after seeing this message.

Finding Support Information for Platforms and Cisco Software Images

Cisco software is packaged in feature sets consisting of software images that support specific platforms. The feature sets available for a specific platform depend on which Cisco software images are included in a release. To identify the set of software images available in a specific release or to find out if a feature is available in a given Cisco IOS XE software image, you can use Cisco Feature Navigator or the software release notes.

Using Cisco Feature NavigatorUse Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.


OL-16506-08

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

Chapter 2 Using Cisco IOS XE Software Finding Support Information for Platforms and Cisco Software Images

Using Software AdvisorTo see if a feature is supported by a Cisco IOS XE release, to locate the software document for that feature, or to check the minimum software requirements of Cisco IOS XE software with the hardware installed on your router, Cisco maintains the Software Advisor tool on Cisco.com at http://www.cisco.com/cgi-bin/Support/CompNav/Index.pl.

You must be a registered user on Cisco.com to access this tool.

Using Software Release NotesCisco IOS XE software releases include release notes that provide the following information:

• Platform support information

• Memory recommendations

• New feature information

• Open and resolved severity 1 and 2 caveats for all platforms

Release notes are intended to be release-specific for the most current release, and the information provided in these documents may not be cumulative in providing information about features that first appeared in previous releases. Refer to Cisco Feature Navigator for cumulative feature information.


OL-16506-08

http://www.cisco.com/cgi-bin/Support/CompNav/Index.pl


C H A P T E R 3
Consolidated Packages and Sub-Package Management
This section discusses how consolidated packages and software sub-packages (individual and optional) are managed and are used to run the Cisco ASR 1000 Series Aggregation Services Routers. It contains the following sections:

• Running the Cisco ASR 1000 Series Routers Overview, page 3-1

• Software File Management Command Set Overview, page 3-4

• Managing and Configuring the Router to Run Using Consolidated Packages and Individual Sub-Packages, page 3-6

• Upgrading Individual Sub-Packages, page 3-18

Note This section of the document does not discuss limited downtime upgrades. For information on limited downtime upgrades, see the “In Service Software Upgrades (ISSU)” section on page 4-1.

Running the Cisco ASR 1000 Series Routers OverviewThe Cisco ASR 1000 Series Routers can be run using a complete consolidated package or using individual sub-packages.

This section covers the following topics:

• Running Cisco ASR 1000 Series Routers Using Individual and Optional Sub-Packages Overview, page 3-1

• Running Cisco ASR 1000 Series Routers Using a Consolidated Package Overview, page 3-2

• Running Cisco ASR 1000 Series Routers Summary, page 3-3

Running Cisco ASR 1000 Series Routers Using Individual and Optional Sub-Packages Overview

The Cisco ASR 1000 Series Routers can be configured to run using individual sub-packages and optional sub-packages.


Chapter 3 Consolidated Packages and Sub-Package Management Running the Cisco ASR 1000 Series Routers Overview

When the router is configured to run using individual and optional sub-packages:

• Each individual sub-package within a consolidated package is extracted onto the router as its own file.

• Additionally, any optional sub-packages must be separately downloaded and stored in the same directory with the provisioning file and the other individual sub-packages that have been extracted.

• The router then runs by accessing each file as needed for operational purposes. All individual and optional sub-package files must be stored in the same directory on the router for the router to run properly using individual sub-packages.

When a Cisco ASR 1000 Series Router is configured to run using individual and optional sub-packages, software image content from the RP is copied into memory on an as-needed basis only. Memory is conserved for other router processes, such as passing traffic. The router, therefore, allows for the highest peak traffic load when configured to run using individual sub-packages.

When running the Cisco ASR 1000 Series Routers using individual and optional sub-packages, the router must be configured to boot using the provisioning file that was included in the consolidated package with the individual sub-package files. This provisioning file must also be in the same directory as the individual and optional sub-package files. The router boots faster when configured to run using individual and optional sub-packages than it does when configured to run using a consolidated package.

A Cisco ASR 1000 Series Router cannot be configured to run individual and optional sub-packages stored on a TFTP or any other network server. The individual and optional sub-packages along with the provisioning file must be copied onto the bootflash: file system to run the router using this method.

Running Cisco ASR 1000 Series Routers Using a Consolidated Package Overview

The Cisco ASR 1000 Series Routers can also be configured to run using a consolidated package.

Note Booting the router from a consolidated package is not supported for installation of optional sub-packages. For more information, see the “Running Cisco ASR 1000 Series Routers Using Individual and Optional Sub-Packages Overview” section on page 3-1.

When the router is configured to run using a consolidated package, the entire consolidated package file is copied onto the router or accessed by the router via TFTP or another network transport method. The router runs using the consolidated package file.

When a Cisco ASR 1000 Series Router is configured to run using the consolidated package file, more memory is required to process router requests because the router has to search one larger file for every request. The peak amount of memory available for passing network traffic is therefore lower when the router is configured to run using a consolidated package.

A Cisco ASR 1000 Series Router configured to run using a consolidated package is booted by booting the consolidated package file. Because this file is large, the boot process for routers running using the consolidated package is slower than the boot process for routers running individual sub-packages.

A Cisco ASR 1000 Series Router configured to run using a consolidated package does have some advantages over a Cisco ASR 1000 Series Router configured to run individual sub-packages. First, a consolidated package can be booted and utilized using TFTP or another network transport method. Secondly, configuring the router to use the one consolidated package file is easier than managing several individual sub-package files. Running the router using a consolidated package may be the right method of running the router in certain networking environments.


OL-16506-08

Chapter 3 Consolidated Packages and Sub-Package Management Running the Cisco ASR 1000 Series Routers Overview

The consolidated package should be stored on bootflash:, usb[0-1]:, or a remote file system when this method is used to run the router.

Running Cisco ASR 1000 Series Routers SummaryThis section summarizes the advantages and disadvantages of each method of running your Cisco ASR 1000 Series Routers.

The advantages of running your router using individual sub-packages include:

• Optimizes router memory usage—When the router is booting using the individual and optional sub-package method, software image content from the Router Processor (RP) is copied into memory on an as-needed basis only, which conserves memory for other router processes. The router boots fastest and allows for the highest peak traffic load when booted using the individual sub-package boot approach.

The advantages of running your router using a consolidated package include:

• Simplified installation—Only one software file needs to be managed instead of several separate images.

• Storage—A consolidated package, unlike individual sub-packages, can be used to run the router while being stored in bootflash:, on a USB Flash disk, or on a network server. A consolidated package can be booted and utilized using TFTP or another network transport method, while the individual sub-package method requires the individual sub-package files to be copied into the bootflash: file directory on the router.

Table 3-1 summarizes the advantages and disadvantages of the approaches.


OL-16506-08

Chapter 3 Consolidated Packages and Sub-Package Management Software File Management Command Set Overview

Table 3-1 Advantages and Disadvantages of Running Individual Sub-Packages and Consolidated

Packages

Software File Management Command Set OverviewSoftware files can be managed on the Cisco ASR 1000 Series Routers using three distinct command sets. This section provides overviews of the following command sets:

• The request platform Command Set, page 3-4

• The copy Command, page 3-5

• The issu Command Set, page 3-5

The request platform Command SetThe request platform software package command is part of the larger request platform command set being introduced on the Cisco ASR 1000 Series Routers. For additional information on each request platform command and the options available with each command, see the Cisco IOS Configuration Fundamentals Command Reference.

The request platform software package command, which can be used to upgrade individual sub-packages and a complete consolidated package, is used to upgrade software on the Cisco ASR 1000 Series Routers. Notably, the request platform software package command is the recommended way of performing an individual sub-package upgrad,e and also provides the only method of no-downtime upgrades of individual sub-packages on the router when the router is running individual sub-packages.

Approach Advantages Disadvantages

Individual and optional sub-packages

Note This method is required if you need to install any optional sub-packages for your system.

• Optimizes memory usage, allowing for faster boot times and increased traffic loads.

• Multiple software sub-packages more difficult to manage.

• Cannot be booted from TFTP or any other network server. If you are going to use the individual sub-package boot method, each individual sub-package file must be placed in the bootflash: directory.

• Individual and optional sub-package files and the provisioning file must be stored in bootflash:.

Consolidated Package • Easier management. Only have to manage one file instead of many files.

• A consolidated package file can be stored in bootflash:, on a USB Flash disk, or on any TFTP or other network server.

• Slower boot times and lessened maximum system scalability because the larger image must be processed at all times.


OL-16506-08

Chapter 3 Consolidated Packages and Sub-Package Management Software File Management Command Set Overview

The request platform software package command requires that the destination device or process be specified in the command line, so the commands can be used to upgrade software on both an active or a standby processor. The request platform software package command allows for no downtime software upgrades in many scenarios.

The basic syntax of the command is request platform software package install rp rp-slot-number file file-URL, where rp-slot-number is the number of the RP slot and file-URL is the path to the file being used to upgrade the Cisco ASR 1000 Series Router. The command has other options; see the request platform software package command references for information on all of the options available with this command set.

In Cisco IOS XE Release 2.4, the request platform software package uninstall command is introduced on the Cisco ASR 1000 Series Routers to remove provisioning of an optional sub-package from an RP. The syntax for the command follows the install form of the command: request platform software package uninstall rp rp-slot-number type pkg, where rp-slot-number is the number of the RP slot and pkg is the type of optional sub-package file to be removed.

Note For additional information on limited downtime upgrades using the request platform software package command set, see the “In Service Software Upgrades (ISSU)” section on page 4-1.

The copy CommandThe copy command can be used to move consolidated packages and individual sub-packages onto the router, though using this command to move individual sub-package files from one storage area to another is often inefficient (in these scenarios, it is almost always preferable to move the consolidated package, then extract the sub-packages, or to extract the sub-packages without moving the consolidated package).

To upgrade a consolidated package on the Cisco ASR 1000 Series Routers, copy the consolidated package onto a file system, usually bootflash: or usb[0-1]: on the router, using the copy command as you would on most other Cisco routers. After making this copy, configure the router to boot using the consolidated package file.

To upgrade the router and reboot using individual sub-packages, copy the consolidated package onto the router using the copy command, enter the request platform software package expand command to extract the individual sub-packages, and configure the router to boot using sub-packages. Other methods, such as copying each individual sub-package in the same consolidated package from a directory or using the request platform software package command to extract the sub-packages onto a router directory are also usable, though copying individual sub-packages is often inefficient.

See the copy command reference for a list of the options that are available with the copy command.

The issu Command SetThe issu command set that is available on other Cisco routers is also available on the Cisco ASR 1000 Series Routers. The issu command set can be used to perform both consolidated package and individual sub-package upgrades.

The issu command set includes the issu command with the loadversion, runversion, commitversion, and abortversion options. See the issu command references for information on all of the options available with each of these commands.


OL-16506-08

Chapter 3 Consolidated Packages and Sub-Package Management Managing and Configuring the Router to Run Using Consolidated Packages and Individual Sub-Packages

The issu runversion command is optional for completing a consolidated package upgrade on the Cisco ASR 1000 Series Routers. A user can enter issu commitversion from the active RP to complete the software upgrade, then use the redundancy force-switchover command to switch to the upgraded RP on this platform, if desired.

Note For additional information on limited downtime upgrades using the issu command set, see the “In Service Software Upgrades (ISSU)” section on page 4-1.

Managing and Configuring the Router to Run Using Consolidated Packages and Individual Sub-Packages

This section discusses the following topics:

• Quick Start Software Upgrade, page 3-6

• Managing and Configuring a Router to Run Using a Consolidated Package, page 3-7

• Managing and Configuring a Router to Run Using Individual Sub-Packages From a Consolidated Package, page 3-10

• Managing and Configuring a Router to Run Using Optional Sub-Packages, page 3-14

• Troubleshooting Software Mismatch with ESP Board ASR1000-ESP10-N, page 3-17

Quick Start Software UpgradeThe following instructions provide a quick start version of upgrading the software running the Cisco ASR 1000 Series Routers. These instructions assume the user has access to the consolidated package and that the files will be stored in a bootflash: file system that is not storing any previously installed sub-packages or consolidated packages and that has enough room for the file or files.

For more detailed installation examples, see the other sections of this chapter.

Step 1 Copy the consolidated package into bootflash: using the copy URL-to-image bootflash: command.

Step 2 If you want to run the router using individual sub-packages, enter the request platform software package expand file bootflash:image-name command. If you want to run the router using a consolidated package, skip this step.

Step 3 Enter the dir bootflash: command to verify your consolidated package or your extracted sub-packages are in the directory.

Step 4 If you are trying to run individual sub-packages, use the delete bootdisk:image-name to delete the consolidated package. If you want to run the router using the consolidated package, skip this step.

Step 5 Set up the boot parameters for your boot. Set the configuration register to 0x2 by entering the config-register 0x2102 global configuration command, and enter the boot system flash bootflash:image-name (if running using the consolidated package) or boot system flash bootflash:provisionging-file-name (if running using individual sub-packages) global configuration command.

Step 6 Enter copy running-config startup-config to save your configuration.


OL-16506-08


Step 7 Enter the reload command to reload the router and finish the boot. The upgraded software should be running when the reload completes.

Managing and Configuring a Router to Run Using a Consolidated Package

Note Do not use this procedure if you also need to install any optional sub-packages.

This section documents the following procedures:

• Managing and Configuring a Consolidated Package Using the copy Command, page 3-7

• Managing and Configuring a Consolidated Package Using the request platform software package install Command, page 3-8

Managing and Configuring a Consolidated Package Using the copy Command

To upgrade a consolidated package on the Cisco ASR 1000 Series Routers using the copy command, copy the consolidated package into the bootflash: directory on the router using the copy command as you would on most other Cisco routers. After making this copy, configure the router to boot using the consolidated package file.

In the following example, the consolidated package file is copied onto the bootflash: file system from TFTP. The config-register is then set to boot using boot system commands, and the boot system commands instruct the router to boot using the consolidated package stored in the bootflash: file system. The new configuration is then saved using the copy running-config startup-config command, and the system is then reloaded to complete the process.


11 drwx 16384 Dec 4 2007 04:32:46 -08:00 lost+found86401 drwx 4096 Dec 4 2007 06:06:24 -08:00 .ssh14401 drwx 4096 Dec 4 2007 06:06:36 -08:00 .rollback_timer28801 drwx 4096 Mar 18 2008 17:31:17 -07:00 .prst_sync43201 drwx 4096 Dec 4 2007 04:34:45 -08:00 .installer 13 -rw- 45977 Apr 9 2008 16:48:46 -07:00 target_support_output.tgz.tgz

928862208 bytes total (712273920 bytes free)Router# copy tftp bootflash:Address or name of remote host []? 172.17.16.81Source filename []? /auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.binDestination filename [asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin]? Accessing tftp://172.17.16.81//auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin...Loading /auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin from 172.17.16.81 (via GigabitEthernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


OL-16506-08


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 208904396 bytes]

208904396 bytes copied in 330.453 secs (632176 bytes/sec)Router# dir bootflash:Directory of bootflash:/

11 drwx 16384 Dec 4 2007 04:32:46 -08:00 lost+found86401 drwx 4096 Dec 4 2007 06:06:24 -08:00 .ssh14401 drwx 4096 Dec 4 2007 06:06:36 -08:00 .rollback_timer28801 drwx 4096 Mar 18 2008 17:31:17 -07:00 .prst_sync43201 drwx 4096 Dec 4 2007 04:34:45 -08:00 .installer 12 -rw- 208904396 May 28 2008 16:17:34 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin 13 -rw- 45977 Apr 9 2008 16:48:46 -07:00 target_support_output.tgz.tgz

928862208 bytes total (503156736 bytes free)Router# config tEnter configuration commands, one per line. End with CNTL/Z.Router(config)#boot system flash bootflash:asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.binRouter(config)#config-reg 0x2102Router(config)#exitRouter#show run | include bootboot-start-markerboot system flash bootflash:asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.binboot-end-markerRouter# copy run startDestination filename [startup-config]? Building configuration...[OK]Router# reload

Managing and Configuring a Consolidated Package Using the request platform software package install Command

In the following example, the request platform software package install command is used to upgrade a consolidated package running on RP 0. The force option, which forces the upgrade past any prompt (such as already having the same consolidated package installed), is used in this example.

Router# request platform software package install rp 0 file bootflash:asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin force --- Starting installation state synchronization ---Finished installation state synchronization

--- Starting file path checking ---Finished file path checking

--- Starting image file verification ---Checking image file namesVerifying image file locationsLocating image files and validating name syntaxInspecting image file types

Processing image file constraints

Extracting super package contentVerifying parametersValidating package type


OL-16506-08


Copying package files

Checking and verifying packages contained in super packageCreating candidate provisioning file WARNING: WARNING: Candidate software will be installed upon reboot WARNING: Finished image file verification

--- Starting candidate package set construction ---Verifying existing software setProcessing candidate provisioning file

Constructing working set for candidate package setConstructing working set for running package setChecking command outputConstructing merge of running and candidate packagesFinished candidate package set construction

--- Starting compatibility testing ---Determining whether candidate package set is compatible

WARNING:WARNING: Candidate software combination not found in compatibility databaseWARNING:

Determining whether installation is validDetermining whether installation is valid ... skippedChecking IPC compatibility with running softwareChecking IPC compatibility with running software ... skippedChecking candidate package set infrastructure compatibilityChecking infrastructure compatibility with running softwareChecking infrastructure compatibility with running software ... skippedFinished compatibility testing

--- Starting commit of software changes ---Updating provisioning rollback filesCreating pending provisioning fileCommitting provisioning fileFinished commit of software changes

SUCCESS: Software provisioned. New software will load on reboot.

Router# reload

Note A reload must be performed to finish this procedure. The “Managing and Configuring a Consolidated Package Using the copy Command” section on page 3-7 includes an example of how to configure the router to boot using the consolidated package, and then an example of what happens after the reload is performed to finish the installation.


OL-16506-08


Managing and Configuring a Router to Run Using Individual Sub-Packages From a Consolidated Package

To run the router using individual sub-packages from a consolidated package, follow one of the following procedures:

• Extracting a Consolidated Package and Booting Using the Provisioning File, page 3-10

• Copying a Set of Individual Sub-Package Files and Booting Using a Provisioning File, page 3-14

Extracting a Consolidated Package and Booting Using the Provisioning File

Step 1 Perform one of the following tasks:

a. Copy the consolidated package file (or, in cases where you have every individual sub-package and a provisioning file for the sub-packages available, each individual sub-package and the provisioning file) onto the bootflash: file system using the copy command. Make sure to copy the consolidated package into the bootflash: file system and directory where you want to store the provisioning file and the individual image sub-packages. Enter the request platform software package expand file bootflash:url-to-Cisco-IOS-XE-imagename command with no other option to extract the provisioning file and the individual sub-packages out of the consolidated package file and into the current directory in bootflash:.

b. Copy the consolidated package file onto any file system on your router, then enter the request platform software package expand file file-system:url-to-Cisco-IOS-XE-imagename to bootflash: command to extract the provisioning file and the individual image sub-packages onto the bootflash: file system.

Note After performing this step, do not move any of the files. The bootup process cannot function properly unless all of the sub-packages and the provisioning file are located in the same directory. Also, do not rename the sub-package files. Only the provisioning file can be renamed, and the renaming of the provisioning file, if desired, should be done at this step before the router is rebooted.

Step 2 Configure the router to boot using the provisioning file. The sequence below provides an example that would boot the router using the provisioning file named packages.conf that was stored with the other sub-packages in the bootflash: file system.

Router(config)# no boot systemRouter(config)# config-register 0x2102Router(config)# boot system flash bootflash:packages.confRouter(config)# exit*May 11 01:31:04.815: %SYS-5-CONFIG_I: Configured from console by con Router# copy running-config startup-configBuilding configuration...[OK]Router# reload

Extracting Sub-Packages and Provisioning File Example 1

The following example shows how to extract the individual sub-packages and the provisioning file from a consolidated package that has already been placed in the directory where the user wants to store the individual sub-packages and the provisioning file.


OL-16506-08


Output of the directory before and after the extraction is given to confirm the files were extracted.




Router# request platform software package expand file bootflash:asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.binVerifying parametersValidating package typeCopying package files

SUCCESS: Finished expanding all-in-one software package.


11 drwx 16384 Dec 4 2007 04:32:46 -08:00 lost+found86401 drwx 4096 Dec 4 2007 06:06:24 -08:00 .ssh14401 drwx 4096 Dec 4 2007 06:06:36 -08:00 .rollback_timer28801 drwx 4096 Mar 18 2008 17:31:17 -07:00 .prst_sync43201 drwx 4096 Dec 4 2007 04:34:45 -08:00 .installer 12 -rw- 208904396 May 9 2008 14:36:31 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin57611 -rw- 47071436 May 22 2008 11:26:23 -07:00 asr1000rp1-espbase.02.01.00.122-33.XNA.pkg57602 -rw- 5740 May 22 2008 11:26:22 -07:00 asr1000rp1-packages-adventerprisek9.02.01.00.122-33.XNA.conf57612 -rw- 20334796 May 22 2008 11:26:24 -07:00 asr1000rp1-rpaccess.02.01.00.122-33.XNA.pkg57613 -rw- 22294732 May 22 2008 11:26:24 -07:00 asr1000rp1-rpbase.02.01.00.122-33.XNA.pkg57614 -rw- 21946572 May 22 2008 11:26:25 -07:00 asr1000rp1-rpcontrol.02.01.00.122-33.XNA.pkg57615 -rw- 48099532 May 22 2008 11:26:26 -07:00 asr1000rp1-rpios-adventerprisek9.02.01.00.122-33.XNA.pkg57616 -rw- 34324684 May 22 2008 11:26:27 -07:00 asr1000rp1-sipbase.02.01.00.122-33.XNA.pkg57617 -rw- 22124748 May 22 2008 11:26:28 -07:00 asr1000rp1-sipspa.02.01.00.122-33.XNA.pkg57603 -rw- 6256 May 22 2008 11:26:28 -07:00 packages.conf 13 -rw- 45977 Apr 9 2008 16:48:46 -07:00 target_support_output.tgz.tgz


Extracting Sub-Packages and Provisioning File Example 2

The following example shows how to extract the individual sub-packages and the provisioning file from a consolidated package that has already been placed on the router in a directory that will not store the individual sub-packages and the provisioning file. In this particular example, the contents of a consolidated package stored in usb0: are extracted into bootflash:.


OL-16506-08


Output of the bootflash: directory before and after the extraction is given to confirm the files were extracted.





11 drwx 16384 Dec 13 2004 03:45:47 -08:00 lost+found87937 drwx 4096 Dec 13 2004 03:46:45 -08:00 .rollback_timer14657 drwx 4096 Dec 13 2004 03:47:17 -08:00 .installer29313 drwx 4096 Dec 13 2004 03:53:00 -08:00 .ssh 12 -rw- 33554432 Dec 13 2004 03:53:49 -08:00 nvram_0010058625 drwx 4096 May 7 2008 17:27:51 -07:00 .prst_sync


Router# request platform software package expand file usb0:asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin to bootflash:Verifying parametersValidating package typeCopying package filesSUCCESS: Finished expanding all-in-one software package.


11 drwx 16384 Dec 13 2004 03:45:47 -08:00 lost+found87937 drwx 4096 Dec 13 2004 03:46:45 -08:00 .rollback_timer14657 drwx 4096 Dec 13 2004 03:47:17 -08:00 .installer29313 drwx 4096 Dec 13 2004 03:53:00 -08:00 .ssh 12 -rw- 33554432 Dec 13 2004 03:53:49 -08:00 nvram_0010043979 -rw- 47071436 May 27 2008 14:25:01 -07:00 asr1000rp1-espbase.02.01.00.122-33.XNA.pkg58625 drwx 4096 May 7 2008 17:27:51 -07:00 .prst_sync43970 -rw- 5740 May 27 2008 14:25:00 -07:00 asr1000rp1-packages-adventerprisek9.02.01.00.122-33.XNA.conf43980 -rw- 20334796 May 27 2008 14:25:01 -07:00 asr1000rp1-rpaccess.02.01.00.122-33.XNA.pkg43981 -rw- 22294732 May 27 2008 14:25:02 -07:00 asr1000rp1-rpbase.02.01.00.122-33.XNA.pkg43982 -rw- 21946572 May 27 2008 14:25:03 -07:00 asr1000rp1-rpcontrol.02.01.00.122-33.XNA.pkg43983 -rw- 48099532 May 27 2008 14:25:04 -07:00 asr1000rp1-rpios-adventerprisek9.02.01.00.122-33.XNA.pkg43984 -rw- 34324684 May 27 2008 14:25:05 -07:00 asr1000rp1-sipbase.02.01.00.122-33.XNA.pkg43985 -rw- 22124748 May 27 2008 14:25:05 -07:00 asr1000rp1-sipspa.02.01.00.122-33.XNA.pkg43971 -rw- 6256 May 27 2008 14:25:05 -07:00 packages.conf



OL-16506-08


Extracting Sub-Packages, Configuring the Router to Boot Using the Provisioning File, and Reloading the Router Example

In the following example, the provisioning file and the individual sub-packages are extracted from a consolidated package. The router is then configured to boot using the provisioning file. This example also shows the config-register being set and the running configuration being saved because these tasks must be performed for the router to reload properly. The router is then reloaded to complete the process.









Router(config)# no boot systemRouter(config)# config-register 0x2102Router(config)# boot system flash bootflash:packages.conf


OL-16506-08


Router(config)# exitRouter# copy run startRouter# reload

Copying a Set of Individual Sub-Package Files and Booting Using a Provisioning File

Note Although this upgrade method works, it is less efficient than other methods of upgrading the router’s software.

Step 1 Copy each individual sub-package and the provisioning file into the bootflash: directory using the copy command. Note that this method of running the router will only work if all the individual sub-packages for a release and a provisioning file are downloaded onto the router and stored in the bootflash: directory. No other file directories should be used for booting the router using individual sub-packages. The files can also be moved on the router physically using a USB Flash drive.

Step 2 Configure the router to boot using the provisioning file.

The sequence below provides an example that would boot the router using the provisioning file named “packages.conf” that was stored with the other sub-packages in the bootflash: file system. The router runs using individual sub-packages once the reload is complete.

Router(config)# no boot systemRouter(config)# config-register 0x2102Router(config)# boot system flash bootflash:packages.confRouter(config)# exit*May 11 01:31:04.815: %SYS-5-CONFIG_I: Configured from console by con Router# write memory Building configuration...[OK]Router# reload

Managing and Configuring a Router to Run Using Optional Sub-PackagesTo manage and configure a Cisco ASR 1000 Series Router to run using optional sub-packages, perform the following tasks:

• Installing an Optional Sub-Package, page 3-14 (Required)

• Uninstalling an Optional Sub-Package, page 3-16 (Optional)

Installing an Optional Sub-Package

Note If you install the Cisco WebEx Node for ASR 1000 Series SPA before the software sub-package is installed, you will receive the error message %ASR1000_RP_SPA-3-MISSING_SPA_PKG_ERR. This message will resolve once you download and install the appropriate sipspawma sub-package and then reload the router in individual sub-package mode.


OL-16506-08


To run the router using an optional sub-package, perform the following steps for each RP in the system:

Step 1 Verify that the RP is running in individual sub-package mode and was booted from a provisioning file. For more information, see the “Managing and Configuring a Router to Run Using Individual Sub-Packages From a Consolidated Package” section on page 3-10.

Step 2 Verify that the version of the optional sub-package that you want to install is the same version as the software running on the active RP.

Step 3 Download the optional sub-package that you want to install. Optional sub-packages must be downloaded independently from consolidated packages for the Cisco ASR 1000 Series Routers.

Step 4 On each RP, copy the optional sub-package to the directory where any other individual sub-packages and the provisioning file is located.

Step 5 Run the request platform software package install rp file command, as shown in the following example:

Note Do not use the optional slot or bay keywords for the initial installation.

Router# request platform software package install rp 0 file bootflash:asr1000rp1-sipspawmak9.BLD_V122_33_XND_ASR_RLS4_THROTTLE_LATEST_20090511_042308.pkg--- Starting local lock acquisition on R0 --- Finished local lock acquisition on R0


--- Starting image file verification --- Checking image file names Verifying image file locations Locating image files and validating name syntax Found asr1000rp1-sipspawmak9.BLD_V122_33_XND_ASR_RLS4_THROTTLE_LATEST_20090511_042308.pkgInspecting image file typesProcessing image file constraintsCreating candidate provisioning file

WARNING: No package of type sipspawmak9 is installed.WARNING: Package will be installed for all SIP slots and bays.

Finished image file verification

--- Starting candidate package set construction --- Verifying existing software set Processing candidate provisioning file Constructing working set for candidate package set Constructing working set for running package set Checking command output Constructing merge of running and candidate packages Checking if resulting candidate package set would be complete Finished candidate package set construction



Determining whether installation is valid



OL-16506-08


Software sets are identified as compatible Checking IPC compatibility with running software Checking candidate package set infrastructure compatibility Checking infrastructure compatibility with running software Checking package specific compatibility Finished compatibility testing

--- Starting impact testing ---Checking operational impact of changeFinished impact testing

--- Starting list of software package changes --- No old package files removed New files list: Added asr1000rp1-sipspawmak9.BLD_V122_33_XND_ASR_RLS4_THROTTLE_LATEST_20090511_042308.pkgFinished list of software package changes

--- Starting commit of software changes --- Updating provisioning rollback files Creating pending provisioning file Committing provisioning file Finished commit of software changes

--- Starting analysis of software changes --- Finished analysis of software changes

--- Starting update running software --- Blocking peer synchronization of operating information Creating the command set placeholder directory Finding latest command set Finding latest command shortlist lookup file Finding latest command shortlist file Assembling CLI output libraries Assembling CLI input libraries Applying interim IPC and database definitions Replacing running software Replacing CLI software Restarting software Restarting software: target frus filtered out ... skipped Applying final IPC and database definitions Generating software version information Notifying running software of updates Unblocking peer synchronization of operating information Unmounting old packages Cleaning temporary installation files Finished update running software

SUCCESS: Finished installing software.

Uninstalling an Optional Sub-Package

In Cisco IOS XE Release 2.4, the Cisco ASR 1000 Series Routers support removal of an installed optional sub-package.

To uninstall an optional sub-package, perform the following steps:

Step 1 On each RP in the system, use the request platform software package uninstall command as shown in the following example:

Router# request platform software package uninstall rp 0 type sipspawma--- Starting local lock acquisition on R0 --- Finished local lock acquisition on R0

--- Starting uninstall preparation ---Validating uninstall optionsCreating candidate provisioning fileFinished uninstall preparation


OL-16506-08


--- Starting candidate package set construction --- Verifying existing software set Processing candidate provisioning file Constructing working set for candidate package set Constructing working set for running package set Checking command output Constructing merge of running and candidate packages Checking if resulting candidate package set would be complete Finished candidate package set construction

--- Starting compatibility testing ---Determining whether candidate package set is compatible Determining whether installation is valid Software sets are identified as compatible Checking IPC compatibility with running software Checking candidate package set infrastructure compatibility Checking infrastructure compatibility with running software Checking package specific compatibility Finished compatibility testing

--- Starting list of software package changes --- Old files list: Removed asr1000rp1-sipspawmak9.BLD_V122_33_XND_ASR_RLS4_THROTTLE_LATEST_20090511_042308.pkgNo new package files addedFinished list of software package changes

--- Starting commit of software changes --- Updating provisioning rollback files Creating pending provisioning file Committing provisioning file Finished commit of software changes

--- Starting analysis of software changes --- Finished analysis of software changes

--- Starting update running software --- Blocking peer synchronization of operating information Creating the command set placeholder directory Finding latest command set Finding latest command shortlist lookup file Finding latest command shortlist file Assembling CLI output libraries Assembling CLI input libraries Applying interim IPC and database definitions Replacing running software Replacing CLI software Restarting software Restarting software: target frus filtered out ... skipped Applying final IPC and database definitions Generating software version information Notifying running software of updates Unblocking peer synchronization of operating information Unmounting old packages Cleaning temporary installation files Finished update running software


Step 2 Use the show version provisioned command to verify that the optional sub-package is no longer installed.

Step 3 (Optional) Use the request platform software clean command to remove the unused packages.

Troubleshooting Software Mismatch with ESP Board ASR1000-ESP10-NThe Cisco ASR 1000 ESP board ASR1000-ESP10-N enables users to install a Cisco 7600 series router without encryption features. This unrestricted product format, in which all encryption chips have been removed, can be provided in the Cisco ASR 1002, 1004, and 1006 Series Routers. This ESP must be used with the appropriate Cisco IOS XE 2.2 image that does not contain encryption software.


OL-16506-08

Chapter 3 Consolidated Packages and Sub-Package Management Upgrading Individual Sub-Packages

You cannot load Cisco IOS XE software images or subpackages which contain encryption software, onto a Cisco ASR 1000 Series Router that contains the non crypto enabled ESP board (ASR1000-ESP10-N). As soon as the combination of an encryption-enabled Cisco IOS XE image and encryption-disabled ESP is detected—on bootup, online removal or insertion, or during an install—a message is emitted:

ESP[0|1] does not support strong cryptography. Chassis will reload.

The Route Processor (RP) then reloads the chassis and reboots continuously.

To troubleshoot this problem, follow these steps:

Step 1 Enable ROM Monitor (ROMmon) mode by entering the reload command.

Step 2 Press the Break key during the first 60 seconds while the system is booting.

Step 3 Force the system to remain in ROMmon mode, waiting for manual bootup, by entering the command: confreg 0x0.

Step 4 Load the latest Cisco IOS XE package or subpackages that are compatible with the ASR1000-ESP10-N ESP board.

Compatible subpackages include

– Cisco ASR1000 Series RP1 IP BASE W/O CRYPTO

– Cisco ASR1000 Series RP1 ADVANCED IP SERVICES W/O CRYPTO

– Cisco ASR1000 Series RP1 ADVANCED ENTERPRISE SERVICES W/O CRYPTO

Step 5 Remove the forced manual boot mode by entering the command: confreg config register setting, where config register setting is the default for the user system, often 0x2102.

Step 6 Reboot the system.

Upgrading Individual Sub-PackagesOne consolidated package contains seven individual sub-packages. Each individual sub-package can be upgraded independently.

When using this method to upgrade sub-packages, however, remember that all sub-packages that are part of the same consolidated package should be used together on the Cisco ASR 1000 Series Routers. Individual sub-package upgrades are atypical on the Cisco ASR 1000 Series Routers, because it is very rare to experience a case where a single sub-package is upgraded without upgrading all the sub-packages from the consolidated package. Individual sub-package upgrades are most useful when only a single sub-package of an otherwise functioning set of sub-packages requires an upgrade.

This section uses the SPA sub-package installation to illustrate an individual sub-package upgrade. Although it does not comprehensively cover every possible individual sub-package upgrade scenario, the CLI for each type of upgrade is similar.

Upgrading a SPA Sub-PackageIn the following example, the request platform software package install command is used to upgrade a SIPSPA sub-package for the SPA in bay 0 of the SIP in router slot 1. In this example, the force option, which forces the upgrade past any prompt (such as already having the same sub-package installed), is used.


OL-16506-08


Caution Do not run your router using sub-packages from different consolidated packages. The Cisco ASR 1000 Series Router is not designed to use multiple sub-packages from different consolidated packages. Running sub-packages from different consolidated packages is not recommended and can cause unpredictable router behavior. Individual sub-packages should only be upgraded individually if you or a Cisco customer support representative has determined that upgrading to the same sub-package that is running could have some benefit for your Cisco ASR 1000 Series Router.

Router# request platform software package install rp 0 file bootflash:asr1000rp1-sipspa.02.01.00.122-33.XNA.pkg slot 1 bay 0 force--- Starting installation state synchronization ---Finished installation state synchronization


--- Starting image file verification ---Checking image file namesVerifying image file locationsLocating image files and validating name syntaxInspecting image file typesProcessing image file constraintsCreating candidate provisioning fileFinished image file verification





Determining whether installation is validSoftware sets are identified as compatibleChecking IPC compatibility with running software

Checking candidate package set infrastructure compatibilityChecking infrastructure compatibility with running softwareFinished compatibility testing


--- Starting commit of software changes ---Updating provisioning rollback filesCreating pending provisioning file

Committing provisioning fileFinished commit of software changes


OL-16506-08


--- Starting analysis of software changes ---Finished analysis of software changes

--- Starting update running software ---Blocking peer synchronization of operating informationCreating the command set placeholder directory Finding latest command set Assembling CLI output libraries Assembling CLI input libraries Applying interim IPC and database definitions interim IPC and database definitions applied Replacing running software Replacing CLI software Restarting softwareRestarting SPA CC1/0 Applying interim IPC and database definitions Notifying running software of updates Unblocking peer synchronization of operating information Unmounting old packages Cleaning temporary installation files Finished update running software SUCCESS: Finished installing software.

Router#


OL-16506-08


C H A P T E R 4
In Service Software Upgrades (ISSU)
This section covers the following topics:

• Cisco IOS XE Software Package Compatibility for ISSU, page 4-1

• Prerequisites for ISSU, page 4-2

• Restrictions for ISSU, page 4-2

• Overview of ISSU on the Cisco ASR 1000 Series Routers, page 4-3

• ISSU Upgrade Procedures, page 4-6

• ISSU Upgrade Procedures (Pre Cisco IOS XE Release 2.1.2), page 4-123

Cisco IOS XE Software Package Compatibility for ISSUWhen upgrading the Cisco IOS XE operating system software using the In Service Software Upgrade (ISSU) process, it is important to determine the compatibility of the upgraded software to your current software and hardware. The ISSU process allows software to be updated or otherwise modified while packet forwarding continues with minimal interruption.

Cisco IOS XE release compatibility using the ISSU process utilizes the SSO functionality to preserve state while software versions on the router differ, as during an upgrade. Most SSO-capable features in each Cisco IOS XE release are ISSU capable. ISSU is only supported if SSO is enabled in the configuration and the system is in a steady state (SSO ready state has been achieved). ISSU compatibility depends on the set of specific feature clients that are in use and whether they support ISSU. All ISSU upgrades include at least one IOS switchover operation. It is important to understand which features are in use and whether these features are ISSU compatible.

The Cisco ASR1006 Series Router is a hardware-redundant chassis. The hardware-redundant chassis has two ESP linecards and two RPs which exchange state using hardware links. The Cisco ASR1002 and ASR1004 Series Routers are not hardware redundant, but are software-redundancy capable. The non-redundant chassis has a single RP and a single ESP, but allows the operation of up to two IOS processes on the single RP to exchange states locally.

• Non-hardware-redundant chassis models (such as the Cisco ASR 1002 Router and Cisco ASR 1004 Router)—Supports ISSU only if the router is running in subpackage mode.

• Hardware-redundant chassis models (such as the Cisco ASR 1006 Router)—Supports ISSU when the router is running in sub-package mode or in consolidated package mode.


Chapter 4 In Service Software Upgrades (ISSU) Prerequisites for ISSU

Prerequisites for ISSU Be sure to complete the following prerequisites for running the ISSU process based on your chassis model:

• Refer to the ISSU compatibility tables in the Release Notes for Cisco ASR 1000 Series Aggregation Services Routers at:


• For non-hardware-redundant chassis models (such as the Cisco ASR 1002 Router and Cisco ASR 1004 Router)—Supports ISSU only if the router is running in subpackage mode.

This is because ISSU on these chassis types requires sub-package installation and certain steps in a full ISSU upgrade will have impact equivalent to an ESP or SPA Interface Processor (SIP) online insertion and removal (OIR). SIP impact can be mitigated by installing SIPs one slot at a time if shared port adapters (SPAs) are redundant across SIPs (such as when using Gigabit Etherchannel, load balancing, and so on). Traffic loss cannot be avoided with the installation of the ESP package as a part of ISSU. For a non-hardware-redundant chassis, the chassis must be running with software redundancy active (not simply configured).

• For hardware-redundant chassis models (such as the Cisco ASR 1006 Router)—Supports ISSU when the router is running in sub-package mode or in consolidated package mode.

As with non-hardware-redundant chassis types, SIP impact can be mitigated by installing SIPs one slot at a time if SPAs are redundant across SIPs (such as when using Gigabit Etherchannel). ESP redundancy provides similar capability for the ESP allowing hitless upgrade of a chassis from one software release to another. Consolidated package mode does not provide such a per-slot staging option and always incurs a traffic loss equivalent to simultaneous OIR of all SIPs.

Restrictions for ISSU • Cisco IOS XE software compatibility is between “like” images, for example, advipservicesk9 to

advipservicesk9, adventerprisek9 to adventerprisek9, and so on. Cross-image-type upgrades or installations are not supported in the ISSU process. For example, you cannot upgrade ipbase to advipservicesk9 or advipservices to advipservicesk9.

• Different image types must not be run simultaneously.

• For ATM SPAs on the Cisco ASR1000 Series Routers, ISSU from releases prior to Cisco IOS XE Release 2.5.0 to Cisco IOS XE Release 2.5.0, or from Cisco IOS XE Release 2.5.0 to a release prior to Cisco IOS XE Release 2.5.0, is not supported. If you want to perform ISSU in this environment, you must first remove the configuration from the ATM SPAs on the router, and then shut down the SPAs using the shutdown command prior to running the ISSU process.

• Cisco IOS XE releases not listed as compatible in the ISSU compatibility tables (documented in the Release Notes for Cisco ASR 1000 Series Aggregation Services Routers as stated in the “Prerequisites for ISSU” section on page 4-2) must not be run simultaneously (in a Cisco ASR1006 Series Router) or co-installed on any of the Cisco ASR1000 Series Routers since unexpected failures of one or both RPs or state loss can be experienced. Cisco IOS XE releases listed as partially compatible may incur a loss of state. Cisco IOS XE releases listed as requiring an intermediate release are not directly compatible; however, a migration path is available to preserve some or all state by upgrading to a separate intermediate version, as shown in the tables. The tables do not cover non-redundant (software or hardware) environments as no incremental update is possible under those circumstances.


OL-16506-08


Chapter 4 In Service Software Upgrades (ISSU) Overview of ISSU on the Cisco ASR 1000 Series Routers

• In Cisco IOS XE Release 3.1S, ISSU upgrade and subpackage software upgrade from Cisco IOS XE Release 2.x.x to Cisco IOS XE Release 3.x.xS, including release 3.1S, are not supported. The ISSU downgrade from Cisco IOS XE Release 3.x.xS, including release 3.1S to 2.x.x, is also not supported. ISSU upgrade and subpackage software upgrade is restarted from Cisco IOS XE Release 3.1S. Therefore, rebuilds and releases after Cisco IOS XE Release 3.1S will support ISSU and software upgrade and downgrade, based on the ISSU compatibility matrix tables.

Overview of ISSU on the Cisco ASR 1000 Series Routers The In Service Software Upgrade (ISSU) process allows software to be updated or otherwise modified while packet forwarding continues with minimal interruption.

For the Cisco ASR 1000 Series Routers, it is important to realize that ISSU-compatibility depends on the software sub-package being upgraded and the hardware configuration. Consolidated packages are ISSU-compatible in dual RP configurations only and have other limitations described later in this document. Some RP and ESP software sub-packages can be upgraded using ISSU even in single RP or ESP hardware configurations via dual IOS processes running on the RP; others require dual RP or ESP configurations for an ISSU upgrade. The SPA and SIP software sub-packages must be upgraded on a per-SPA or per-SIP basis. See Table 4-1 to view an ISSU table that addresses the contexts where limited interruption upgrades can be performed.

If you are updating multiple sub-packages, you should also realize that the sequence of the upgrade is important to minimize router downtime for the software upgrade (see the “Using ISSU to Upgrade Sub-Packages (Pre Cisco IOS XE Release 2.1.2)” section on page 4-123).

The specific procedures in this document represent supported and tested installation sequences. The Cisco IOS XE system software allows other installation sequences for special purposes under the guidance of Cisco customer support representatives, but the steps in this document should be followed otherwise. These steps should be followed completely, as the Cisco ASR 1000 Series Routers are designed to run one version of Cisco IOS XE for all consolidated packages and sub-packages on an RP, and running sub-packages from different versions of Cisco IOS XE can cause unexpected router behavior.

When performing ISSU upgrades on the Cisco ASR 1000 Series Routers, it is important to remember that minimal interruption upgrades can be performed using either the issu command set or the request platform command set, and that either command set can be used to perform limited interruption individual consolidated package or sub-package upgrades.

Table 4-1 provides a list of the Cisco ASR 1000 Series Routers sub-packages and whether or not they can be upgraded without losing any network traffic in single and dual RP and ESP configurations using ISSU.

Table 4-1Limited Interruption Upgrade Compatibility Table

Sub-PackageNon-redundant RP and ESP Redundant RP and ESP

Consolidated package (any)

No (Reload required) Yes (RP switchover)

RPBase No (RP Reload required)

Yes (RP switchover)

RPControl Yes (in-service) Yes (in-service)

RPAccess Yes (in-service) Yes (in-service)


OL-16506-08


ISSU Rollback Timer Overview on the Cisco ASR 1000 Series Router

The Cisco ASR 1000 Series Router ISSU procedure has a rollback timer. Rollback timers are used for for ISSU procedures on all Cisco routers that support ISSU, but this section will provide a brief overview of ISSU rollback timers on the Cisco ASR 1000 Series Routers.

During ISSU, the rollback timer begins after the consolidated package or sub-package is loaded. If the upgrade does not move forward in the amount of time specified in the rollback timer, the configuration will automatically “roll back” to the previous configuration and the ISSU upgrade will be cancelled.

Upgrades using the issu command set and the request platform command set both have the rollback timer option. The issu command set always uses a rollback timer; the request platform command set does not use a rollback timer unless the auto-rollback option is used in the request platform software package install command line.

For the issu command set, the issu acceptversion command can be entered to stop the rollback timer without committing the upgrade during the ISSU upgrade. The issu commitversion command can be entered to stop the rollback timer and commit the ISSU upgrade.

For the request platform command set, the request platform software package install rp slot commit command must be entered to stop the rollback timer only in cases where the auto-rollback option is used.

RPIOS Yes1 (IOS software switchover)

Yes (RP switchover)

ESPBase No2 (ESP reload required)

Yes3 (via ESP switchover)

SIPBase4 No (SPAs in SIP do not forward traffic during upgrade)

No (SPAs in SIP do not forward traffic during upgrade)

SIPSPA5 No (SPAs in SIP do not forward traffic during upgrade)

No (SPAs in SIP do not forward traffic during upgrade)

1. Only supported if software redundancy is configured on the RP.

2. ESP has to reload to complete ESPBase sub-package upgrade. All router traffic will be lost during ESP upgrade.

3. An ESP switchover occurs as part of the upgrade, so traffic is forwarded with minimal interruption.

4. Any SIPBase upgrade will require the SPA interfaces to go down during the upgrade for all the SPAs in the SIP.

5. Any SIPSPA upgrade will require the SPA interfaces for that particular SPA to go down during the upgrade.

Note ROMmon images are downloaded separately from Cisco IOS XE images and have their own installation procedures, and are therefore not mentioned as part in this document as part of the ISSU upgrade procedure.

Sub-PackageNon-redundant RP and ESP Redundant RP and ESP


OL-16506-08


The rollback timer for the issu command set can be configured by entering the issu set rollback-timer command. The rollback timer when used with the request platform command set is specified when you use the auto-rollback option when entering the issu request platform software package install command.

For ISSU upgrades on Cisco ASR 1000 Series Routers, it may be advisable to set long rollback times when the upgrade is being performed on routers with large configurations.

The amount of time left on the rollback timer during an ISSU upgrade can be checked by entering the show issu rollback-timer command.

Important Notes about ISSU Compatibility

• It is important to note that every upgrade, including limited interruption supported upgrades, may introduce minor delays (often less than a second) where incoming or buffered traffic may be lost. Careful planning that takes into consideration your hardware configuration before the upgrade, in particular your SIP and SPA hardware installations, can help minimize the impact of lost traffic during the upgrade.

• An RP reload is required to finalize an RPBase sub-package upgrade, as well as any consolidated package upgrade, so all network traffic is lost during the RP reload in single RP configurations during these upgrades. In dual RP configurations, the standby RP can be reset without impacting the active RP, so the standby RP can reset to finish the upgrade without impacting the forwarding of network traffic. The RPBase sub-package upgrade is also performed last so the reload can be delayed in many sub-package upgrade scenarios for this reason.

• Some sub-packages require an RP reload before allowing other sub-packages to be upgraded. To avoid having to reload the RP multiple times to upload multiple packages that require RP reloads, be sure to specify certain sub-package combinations when defining the sub-package names in the issu or request platform software package command in such a way that the command captures the name of all of the sub-packages you would like to upgrade. The RP reload will then upgrade all of the sub-packages that require an upgrade collectively rather than individually. See the “Using ISSU to Upgrade Sub-Packages (Pre Cisco IOS XE Release 2.1.2)” section on page 4-123 for an example of a router upgrade that maximizes uptime by using wildcard characters.

• The RPControl and RPAccess sub-packages can be upgraded without reloading any hardware, so these sub-packages can be upgraded without losing any network traffic. The supported installation procedure instructions specify that these sub-packages be upgraded simultaneously with the RPIOS sub-package.

• The ESP must be reset to finalize an upgrade of the ESPBase sub-package. In a single ESP configuration, traffic will be lost as a result of this reset. In a dual ESP configuration, the standby ESP can be reset without impacting the active ESP, so the standby ESP can reset to finish the upgrade without impacting the forwarding of network traffic.

• If a SIPSPA sub-package is used to upgrade a SPA, the SPA that is being upgraded must be reloaded to finalize the upgrade. All network traffic travelling through that SPA during the SPA reload will be lost. All other SIPs and SPAs on the router continue to be fully operational during the SPA reload.

• Optional sub-packages, such as the “sipspawma” package for the Cisco WebEx Node for the ASR 1000 Series SPA, are also supported by the ISSU process. The optional sub-packages should be downloaded and located in the directory of the provisioning file along with the individual sub-packages on each RP. The optional sub-package version must match the software version of the ISSU target.


OL-16506-08

Chapter 4 In Service Software Upgrades (ISSU) ISSU Upgrade Procedures

• If a SIPBase sub-package is used to upgrade a SIP, that SIP must be reloaded to finalize the upgrade. All network traffic travelling through the SPAs within that SIP during the SIP reload will be lost. All other SIPs and SPAs on the router continue to be fully operational during the SIP reload.

• Wildcard characters in the sub-package name string of the issu or request platform software package command sets can be used to minimize downtime of SIP and SPA sub-package upgrades when the wildcard is defined to capture the SIP and SPA sub-packages simultaneously. Using this wildcard allows the SIP and all the SPAs in the SIP to be updated collectively, thereby allowing for one single traffic disruption for both the SIP and SPA upgrades rather than individual traffic disruptions for the individual upgrades. See the “Using ISSU to Upgrade Sub-Packages (Pre Cisco IOS XE Release 2.1.2)” section on page 4-123 for an examples on using wildcards to avoid multiple SIP and SPA reloads.

• The ISSU upgrade procedures on the Cisco ASR 1000 Series Routers is specific to the router platform. Many of the commands and keywords used to perform ISSU upgrades on the Cisco ASR 1000 Series Routers cannot be used to complete ISSU upgrades on other Cisco routers.

ISSU with Dual IOS Processes on a Single RP Overview

To complete an ISSU upgrade of an individual sub-package using dual IOS processes on a single RP, RPR or SSO must first be enabled.

ISSU with dual IOS processes is useful for upgrading the individual RP sub-packages that can be upgraded without a router reload. See Table 4-1 for a list of these sub-packages. Importantly, note that most sub-package upgrades in a single RP configuration require a hardware reload to complete (whether an RP reload for an RP sub-package, an ESP reload for the ESPBase sub-package, a SIP reload for a SIPBase sub-package, or a SPA reload for the SIPSPA sub-package), so limited interruption upgrades for single RP configurations are not available in most upgrade scenarios.

For information on configuring a second IOS process on a single RP, see the “Configuring RPR or SSO on a Cisco ASR 1002 or Cisco ASR 1004 Router” section on page 4-72.

ISSU Upgrade ProceduresThis section contains the following topics:

• Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration, page 4-6

• Using ISSU to Upgrade Sub-Packages in a Dual Route Processor Configuration, page 4-12

• Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router, page 4-72

Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration

Consolidated packages can only be upgraded using ISSU in dual Route Processor configurations. ISSU is not supported for consolidated package upgrades in single Route Processor configurations.

If you want the RPs on your Cisco ASR 1000 Series router to be running using a consolidated package after the ISSU upgrade is complete, use the following instructions:


OL-16506-08


Note This procedure will only work if the current RPs are already running consolidated packages.

SUMMARY STEPS

1. copy tftp: URL-to-target-location

2. copy source-file-system:filename standby-destination-filesystem

3. dir URL-to-target-location

dir URL-to-target-stby-location

4. issu loadversion rp upgrade-rp-number standby-file-system:filename

5. issu runversion

6. telnet ip-address port

7. issu acceptversion

8. issu commitversion

9. show version, show version active-RP running, show version active-RP provisioned

show platform

show running-configuration

10. hw-module slot RP slot number reload

DETAILED STEPS

Command or Action Purpose

Step 1 copy tftp: URL-to-target-location

copy source-file-system:filename standby-destination-filesystem

ExampleRouter# copy tftp bootflash:

Copy the consolidated package onto the active RP.

Step 2 copy source-file-system:filename standby-destination-filesystem

ExampleRouter# copy bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin stby-bootflash:

Copy the consolidated package onto the standby RP.

Step 3 dir URL-to-target-location

dir URL-to-target-stby-location

ExampleRouter# dir bootflash:Router# dir stby-bootflash:

(Optional) Display the contents of the target directories to confirm the successful copy of the file package.


OL-16506-08


Step 4 issu loadversion rp upgrade-rp-number standby-file-system:filename

ExampleRouter# issu loadversion rp 1 file stby-bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin

Load the target consolidated package onto the standby RP.

After you receive the message indicating that the terminal state has been reached, go on to Step 5.

Step 5 issu runversion

ExampleRouter# issu runversion

Run the consolidated package that was loaded in Step 4.

Note If this command is entered before the terminal state is reached, a “peer is not online” or “Standby RP is not in terminal state” error message will be seen and the issu runversion command will not work. If the issu runversion command does not run for these reasons, wait for the “terminal state is reached” message to appear and retry the issu runversion command. You can also monitor the terminal state using the show platform command.

After ISSU runversion is completed, a switchover will automatically occur and the standby RP will become the active RP.

Step 6 telnet ip-address port

Example[unix-server-1 ~]$ telnet 172.17.52.157 2003User Access Verification

Username: userPassword: ********

Router>

Log on to the RP being upgraded, preferably using the RP’s console port, to complete the upgrade. (This is the new active RP, that was the standby RP prior to the ISSU process.)

Note Ensure the hostname does not end in “-stby” after logging into the RP, as this indicates that the RP being accessed is still the standby RP.

There are many ways to log on to a console port. The example shows access to the console port from a Unix host using telnet.

Step 7 issu acceptversion

ExampleRouter# issu acceptversion

(Optional) Stops the ISSU rollback timer.

This step is optional as long as Step 8 is completed before the rollback timer expires.

Step 8 issu commitversion

ExampleRouter# issu commitversion

Completes the ISSU upgrade.



OL-16506-08


Examples

Router# copy tftp bootflash:Address or name of remote host []? 172.17.16.81 Source filename []? /auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin Destination filename [asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin]? Accessing tftp://172.17.16.81//auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin...Loading /auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin from 172.17.16.81 (via GigabitEthernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 209227980 bytes]


Step 9 show version

show version active-RP running

show version active-RP provisioned

show platform

show running-configuration

(Optional) Enter the show version, show platform, or show runnning-configuration commands to confirm that the upgrade completed successfully, as follows:

• show version—Confirm that the correct software version is running on your router and that the RP was booted from the correct file.

• show running-configuration—Confirm that the booting configuration, in particular the boot system statements, are correct.

Tip Use the show running-config | include boot command to display only the boot statements from the show running-configuration output.

• show platform— Confirm that both RP0 and RP1 are correctly running as active and standby.

Step 10 hw-module slot RP-slot reload

ExampleRouter# hw-module slot R0 reload

Reload the new software on the RP.



OL-16506-08


Router# copy bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin stby-bootflash: Destination filename [asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin]? Copy in progress...CCCCCCCC <output removed for brevity>209227980 bytes copied in 434.790 secs (481216 bytes/sec)


11 drwx 16384 Dec 4 2007 04:32:46 -08:00 lost+found86401 drwx 4096 Dec 4 2007 06:06:24 -08:00 .ssh14401 drwx 4096 Dec 4 2007 06:06:36 -08:00 .rollback_timer28801 drwx 4096 Jul 21 2008 15:29:25 -07:00 .prst_sync43201 drwx 4096 Dec 4 2007 04:34:45 -08:00 .installer 12 -rw- 208904396 May 28 2008 16:17:34 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin57604 -rw- 47071436 May 29 2008 15:45:24 -07:00 asr1000rp1-espbase.02.01.00.122-33.XNA.pkg57602 -rw- 5740 May 29 2008 15:45:23 -07:00 asr1000rp1-packages-adventerprisek9.02.01.00.122-33.XNA.conf57605 -rw- 20334796 May 29 2008 15:45:25 -07:00 asr1000rp1-rpaccess.02.01.00.122-33.XNA.pkg57606 -rw- 22294732 May 29 2008 15:45:25 -07:00 asr1000rp1-rpbase.02.01.00.122-33.XNA.pkg57607 -rw- 21946572 May 29 2008 15:45:26 -07:00 asr1000rp1-rpcontrol.02.01.00.122-33.XNA.pkg57608 -rw- 48099532 May 29 2008 15:45:27 -07:00 asr1000rp1-rpios-adventerprisek9.02.01.00.122-33.XNA.pkg57609 -rw- 34324684 May 29 2008 15:45:28 -07:00 asr1000rp1-sipbase.02.01.00.122-33.XNA.pkg57610 -rw- 22124748 May 29 2008 15:45:29 -07:00 asr1000rp1-sipspa.02.01.00.122-33.XNA.pkg 14 -rw- 275093 May 29 2008 16:27:53 -07:00 crashinfo_RP_00_00_20080529-162753-DST 15 -rw- 7516 Jul 2 2008 15:01:39 -07:00 startup-config 13 -rw- 45977 Apr 9 2008 16:48:46 -07:00 target_support_output.tgz.tgz 16 -rw- 209227980 Jul 17 2008 16:06:58 -07:00 asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin


Router# dir stby-bootflash:Directory of stby-bootflash:/

11 drwx 16384 Dec 13 2004 03:45:47 -08:00 lost+found87937 drwx 4096 Jul 17 2008 16:43:34 -07:00 .rollback_timer14657 drwx 4096 Jul 17 2008 16:43:34 -07:00 .installer29313 drwx 4096 Dec 13 2004 03:53:00 -08:00 .ssh 12 -rw- 33554432 Dec 13 2004 03:53:49 -08:00 nvram_00100 13 -rw- 208904396 Jun 5 2008 20:12:53 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin58625 drwx 4096 Jul 21 2008 15:32:59 -07:00 .prst_sync43972 -rw- 47071436 Jun 5 2008 20:16:55 -07:00 asr1000rp1-espbase.02.01.00.122-33.XNA.pkg43970 -rw- 5740 Jun 5 2008 20:16:54 -07:00 asr1000rp1-packages-adventerprisek9.02.01.00.122-33.XNA.conf43973 -rw- 20334796 Jun 5 2008 20:16:56 -07:00 asr1000rp1-rpaccess.02.01.00.122-33.XNA.pkg43974 -rw- 22294732 Jun 5 2008 20:16:56 -07:00 asr1000rp1-rpbase.02.01.00.122-33.XNA.pkg43975 -rw- 21946572 Jun 5 2008 20:16:57 -07:00 asr1000rp1-rpcontrol.02.01.00.122-33.XNA.pkg43976 -rw- 48099532 Jun 5 2008 20:16:58 -07:00 asr1000rp1-rpios-adventerprisek9.02.01.00.122-33.XNA.pkg


OL-16506-08


43977 -rw- 34324684 Jun 5 2008 20:16:59 -07:00 asr1000rp1-sipbase.02.01.00.122-33.XNA.pkg43978 -rw- 22124748 Jun 5 2008 20:17:00 -07:00 asr1000rp1-sipspa.02.01.00.122-33.XNA.pkg43971 -rw- 6256 Jun 5 2008 20:17:00 -07:00 packages.conf 14 -rw- 209227980 Jul 17 2008 16:16:07 -07:00 asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin


Router# issu loadversion rp 1 file stby-bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin --- Starting installation state synchronization ---Finished installation state synchronization


--- Starting system installation readiness checking ---Finished system installation readiness checking

--- Starting installation changes ---Setting up image to boot on next resetStarting automatic rollback timerFinished installation changes

SUCCESS: Software will now load.

PE23_ASR-1006#*Jul 21 23:34:27.206: %ASR1000_OIR-6-OFFLINECARD: Card (rp) offline in slot R1*Jul 21 23:34:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_NOT_PRESENT)*Jul 21 23:34:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)*Jul 21 23:34:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_REDUNDANCY_STATE_CHANGE)*Jul 21 23:37:05.528: %ASR1000_OIR-6-ONLINECARD: Card (rp) online in slot R1*Jul 21 23:37:25.480: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_FOUND(4))

*Jul 21 23:37:25.480: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))Finished installation state synchronization*Jul 21 23:37:26.349: %REDUNDANCY-3-IPC: IOS versions do not match.*Jul 21 23:38:47.172: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded*Jul 21 23:38:47.173: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)

Router# issu runversion--- Starting installation state synchronization ---Finished installation state synchronization

Initiating active RP failoverSUCCESS: Standby RP will now become active

PE23_ASR-1006#

System Bootstrap, Version 12.2(33r)XN2, RELEASE SOFTWARE (fc1)Technical Support: http://www.cisco.com/techsupportCopyright (c) 2008 by cisco Systems, Inc.

<additional output removed for brevity>

*Jul 21 23:43:31.970: %SYS-5-RESTART: System restarted --Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version 12.2(33)XNA, RELEASE SOFTWARE (fc1)


OL-16506-08


Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2008 by Cisco Systems, Inc.Compiled Thu 01-May-08 00:29 by mcpre*Jul 21 23:43:31.978: %SSH-5-ENABLED: SSH 1.99 has been enabled*Jul 21 23:43:35.196: Relay: standby progression done*Jul 21 23:43:35.197: %PLATFORM-6-RF_PROG_SUCCESS: RF state STANDBY HOT

At this point of the procedure, use your Unix client to log on to the other RP:

[unix-server-1 ~]$ telnet 172.17.52.157 2003User Access Verification

Username: userPassword: ********

Router>

Router# issu acceptversionCancelling rollback timerSUCCESS: Rollback timer cancelled

Router# issu commitversion--- Starting installation changes ---Cancelling rollback timerSaving image changesFinished installation changes

Building configuration...[OK]SUCCESS: version committed: bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin

After you confirm the software versions and configuration, reload the RP as shown in the following example:

Router# hw-module slot R0 reload Proceed with reload of module? [confirm]

*Jul 21 23:54:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_NOT_PRESENT) *Jul 21 23:54:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN) *Jul 21 23:54:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_REDUNDANCY_STATE_CHANGE)

*Jul 21 23:57:05.528: %ASR1000_OIR-6-ONLINECARD: Card (rp) online in slot R0 *Jul 21 23:57:25.480: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_FOUND(4))

*Jul 21 23:57:25.480: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))

*Jul 21 23:58:47.172: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded *Jul 21 23:58:47.173: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)

Using ISSU to Upgrade Sub-Packages in a Dual Route Processor ConfigurationThis section provides instructions on performing an ISSU upgrade on a Cisco ASR 1000 Series Router with dual RPs that is currently running individual sub-packages.

This section covers the following topics

• Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1006 Router (issu command set), page 4-13


OL-16506-08


• Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1006 Router (request platform command set), page 4-45

Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1006 Router (issu command set)

This section provides the instruction for performing an ISSU upgrade using sub-packages on a Cisco ASR 1006 router with a dual RP setup using the issu command set.

This procedure can only be performed if the current ASR 1006 has two active RPs and both RPs are running sub-packages.

SUMMARY STEPS

1. show version

show version active-rp installed

dir filesystem:<directory>

show platform

show redundancy-states

2. copy running-config startup-config

3. mkdir URL-to-directory-name


5. request platform software package expand file URL-to-consolidated-package

6. dir URL-to-consolidated-package

7. copy file-system:asr1000rp1-espbase.version.pkg URL-to-directory-of-sub-packages-active-RP

copy file-system:asr1000rp1-rpaccess.version.pkg URL-to-directory-of-sub-packages-active-RP

copy file-system:asr1000rp1-rpbase.version.pkg URL-to-directory-of-sub-packages-active-RP

copy file-system:asr1000rp1-rpcontrol.version.pkg URL-to-directory-of-sub-packages-active-RP

copy file-system:asr1000rp1-rpios.version.pkg URL-to-directory-of-sub-packages-active-RP

copy file-system:asr1000rp1-sipbase.version.pkg URL-to-directory-of-sub-packages-active-RP

copy file-system:asr1000rp1-sipspa.version.pkg URL-to-directory-of-sub-packages-active-RP

Note In step 6, each individual sub-package that was extracted in step 4 is copied to the directory where the sub-packages that are currently running the standby RP are stored.

8. copy file-system:asr1000rp1-espbase.version.pkg URL-to-directory-of-sub-packages-standby-RP

copy file-system:asr1000rp1-rpaccess.version.pkg URL-to-directory-of-sub-packages-standby-RP

copy file-system:asr1000rp1-rpbase.version.pkg URL-to-directory-of-sub-packages-standby-RP

copy file-system:asr1000rp1-rpcontrol.version.pkg URL-to-directory-of-sub-packages-standby-RP

copy file-system:asr1000rp1-rpios.version.pkg URL-to-directory-of-sub-packages-standby-RP

copy file-system:asr1000rp1-sipbase.version.pkg URL-to-directory-of-sub-packages-standby-RP

copy file-system:asr1000rp1-sipspa.version.pkg URL-to-directory-of-sub-packages-standby-RP


OL-16506-08


9. issu loadversion rp standby-RP file URL-to-standby-file-system:asr1000rp*version*.pkg force

10. hw-module slot standby-RP reload

11. issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp1-{sipbase,sipspa}*version*.pkg slot SIP-slot-number force

issu commitversion

Repeat this step for each SIP installed in the router before moving onto the next step.

12. issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp1-esp*version*.pkg slot standby-ESP-slot

issu commitversion

issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp1-esp*version*.pkg slot active-ESP-slot

issu commitversion

13. issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp1*version*.pkg force

14. show version active-RP provisioned

show version active-RP installed

15. redundancy force-switchover

16. request platform software package clean


OL-16506-08


DETAILED STEPS


Step 1 show version



show platform

show redundancy states

ExampleRouter# show version

Router# show version r0 installed

Router# dir bootflash:

Router# show platform

Router# show redundancy states

(Optional) Use the following commands to confirm the current router configuration, as follows:

• show version and show version active-rp installed—Verify the running version of the Cisco IOS XE software on the router, and which file was used to boot the router, and where that file is stored.

• dir—Confirm that the files that were used to boot the router are located in the directory.

• show platform—Confirm the current status of the active and standby RPs.

• show redundancy states—Confirm the operational and configured redundancy states.

Step 2 copy running-config startup-config

ExampleRouter# copy running-config startup-config

After you have confirmed that the system states are acceptable, save the current configuration to the startup configuration.

Step 3 mkdir URL-to-directory-name

ExampleRouter# mkdir usb0:221subs

Create a directory to store the consolidated package and sub-packages.

This directory must be created in most cases because the consolidated packages and sub-packages have to be separated from the sub-packages that booted the router at this step of the procedure.


ExampleRouter# copy tftp: usb0:221subs

Copy the consolidated package file into the directory created in Step 3.

The consolidated package in this step should not be copied into the same directory where the sub-packages that are currently running your router are stored (the directory containing the packages.conf provisioning file from which the router was booted).

Tip It is recommended that you copy the package onto a usb: or harddisk: file system for space considerations when performing this step of the procedure.

Step 5 request platform software package expand file URL-to-consolidated-package

ExampleRouter# request platform software package expand file usb0:221subs/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin

Extract the sub-packages out of the consolidated package file into the temporary directory.

Note Take extra care to extract the sub-packages to a temporary sub-directory and do not delete any of the files currently running the router at this point of the procedure. To erase the files that were running on the router before the ISSU upgrade, enter the request platform software package clean command after the ISSU upgrade has been completed.


OL-16506-08


Step 6 dir target-URL

ExampleRouter# dir usb0:221subs

(Optional) Display the directory to confirm that the files were extracted.

Step 7 copy file-system:asr1000rp1-espbase.version.pkg URL-to-directory-of-sub-packages-active-RP







ExampleRouter# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg bootflash:

Router# copy usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg bootflash:

Router# copy usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg bootflash:

Router# copy usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg bootflash:

Router# copy usb0:221subs/asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg bootflash:

Router# copy usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg bootflash:

Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg bootflash:

Copy the sub-packages out of the temporary directory into the directory on the router where the sub-packages running the active RP are currently stored.



OL-16506-08


Step 8 copy file-system:asr1000rp1-espbase.version.pkg URL-to-directory-of-sub-packages-standby-RP







ExampleRouter# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg stby-bootflash:

Router# copy usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg stby-bootflash:

Router# copy usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg stby-bootflash:

Router# copy usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg stby-bootflash:

Router# copy usb0:221subs/asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg stby-bootflash:

Router# copy usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg stby-bootflash:

Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg stby-bootflash:

Copy the sub-packages out of the temporary directory into the directory on the router where the sub-packages running the standby RP are currently stored.

Step 9 issu loadversion rp standby-RP file target-standbyRP-URL-for-sub-packages:asr1000rp*version*.pkg force

ExampleRouter# issu loadversion rp 1 file stby-bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg force

Upgrade the RP sub-packages on the standby RP, where the “rp*” wildcard is specified to capture all of the RP sub-packages for the desired upgrade release.



OL-16506-08


Step 10 hw-module slot standby-RP reload


Reload the standby RP.

Step 11 issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp1-{sipbase,sipspa}*version*.pkg slot SIP-slot-number force

issu commitversion


ExampleRouter# issu loadversion rp 0 file bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.122-33.XNB1*.pkg slot 0 force

Router# issu commitversion

Router# issu loadversion rp 0 file bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.122-33.XNB1*.pkg slot 1 force


Router# issu loadversion rp 0 file bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.122-33.XNB1*.pkg slot 2 force


Upgrade the SIP and SPA sub-packages for each SIP on the router.

Note This step must be completed one SIP at a time, and repeated for each SIP installed on the router before performing the next step.

Tip You can use the show ip interface brief command to identify which slots contain SIPs and SPAs. The interfaces with three numbers (in the form SIP-number/SPA-number/interface-number) identify the SIP and SPA locations in the router.

Note The pattern options used in this CLI (sipbase and sipspa) were introduced in Cisco IOS XE Release 2.1.2 and are not available in previous Cisco IOS XE Releases. See the “ISSU Upgrade Procedures (Pre Cisco IOS XE Release 2.1.2)” section on page 4-123 for pre-Cisco IOS XE Release 2.1.2 ISSU upgrade procedures.

Step 12 issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp1-esp*version*.pkg slot standby-RP-slot

issu commitversion

issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp1-esp*version*.pkg slot active-RP-slot

issu commitversion

ExampleRouter# issu loadversion rp 0 file bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.pkg slot 1


Router# issu loadversion rp 0 file bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.pkg slot 0


Upgrade the ESP Base sub-package on the standby and the active ESPs.

After entering the issu loadversion rp command on the active RP, the ESP switchover will occur automatically. Minimal traffic interruption will occur as a result of this switchover.



OL-16506-08


Examples

Router# show versionCisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version 12.2(33)XNA, RELEASE SOFTWARE (fc1)

<output removed for brevity>

System image file is "bootflash:packages.conf"


Router# show platform Chassis type: ASR1006

Slot Type State Insert time (ago) --------- ------------------- --------------------- ----------------- 0 ASR1000-SIP10 ok 00:03:03 0/0 SPA-4XT-SERIAL ok 00:01:35 0/1 SPA-5X1GE-V2 ok 00:01:35 0/2 SPA-2XOC3-POS ok 00:01:36 0/3 SPA-4XT-SERIAL ok 00:01:35 1 ASR1000-SIP10 ok 00:03:03 1/0 SPA-4X1FE-TX-V2 ok 00:01:36 1/1 SPA-2X1GE-V2 ok 00:01:35 1/3 SPA-1XOC12-POS ok 00:01:36 R0 ASR1000-RP1 ok, active 00:03:03 R1 ASR1000-RP1 ok, standby 00:03:03 F0 ASR1000-ESP10 ok, active 00:03:03 F1 ASR1000-ESP10 ok, standby 00:03:03

Step 13 issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp*version*.pkg force

ExampleRouter# issu loadversion rp 0 file bootflash:asr1000rp1-rp*02.02.01.122-33.XNB1*.pkg force

Upgrade all of the sub-packages on the active RP.

Note This step is required to ensure that all sub-packages on the router were upgraded as part of this procedure, and might upgrade some sub-packages that would otherwise be missed in the process.

Step 14 show version active-RP provisioned


ExampleRouter# show version r0 provisioned


(Optional) Confirm that the sub-packages are provisioned and installed.

Step 15 redundancy force-switchover

ExampleRouter# redundancy force-switchover

Force an RP switchover to complete the upgrade.

Step 16 request platform software package clean

ExampleRouter# request platform software package clean

(Optional) Removes all unused sub-packages files from the router.



OL-16506-08


P0 ASR1006-PWR-AC ok 00:02:07 P1 ASR1006-FAN ok 00:02:07

Slot CPLD Version Firmware Version --------- ------------------- --------------------------------------- 0 07091401 12.2(33r)XNB 1 07091401 12.2(33r)XNB R0 07062111 12.2(33r)XNB R1 07062111 12.2(33r)XNB F0 07091401 12.2(33r)XNB F1 07091401 12.2(33r)XNB

Router# show version r0 installed Package: Provisioning File, version: n/a, status: active File: bootflash:packages.conf, on: RP0 Built: n/a, by: n/a File SHA1 checksum: 174bef13f7ce20af077bae7aaefb5279c790dd57

Package: rpbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: RP0 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 661bcb2efda479533c87f23504bf7021d42b3165

Package: rpaccess, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: RP0 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: b0dc8e07cd4f997b045280fa79051e41068c6f3e

Package: rpcontrol, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: RP0/0 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 258c79c9b9e67eb4c21dcb4c9b2fe8b8c1f96cfd

Package: rpios-adventerprisek9, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: RP0/0 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 88ea800ae1c094c46ca5e2f26d116f4e0012c219

Package: rpcontrol, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: RP0/1 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 258c79c9b9e67eb4c21dcb4c9b2fe8b8c1f96cfd

Package: rpios-adventerprisek9, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: RP0/1


OL-16506-08


Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 88ea800ae1c094c46ca5e2f26d116f4e0012c219 Package: rpbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: RP1 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 661bcb2efda479533c87f23504bf7021d42b3165





Package: rpios-adventerprisek9, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: RP1/1 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 88ea800ae1c094c46ca5e2f26d116f4e0012c219

Package: espbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: ESP0 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: da8e5c93d0fa3f7cf27381841fa9efcde409964d

Package: espbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: ESP1


OL-16506-08


Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: da8e5c93d0fa3f7cf27381841fa9efcde409964d

Package: sipbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP0 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 31b36be34aa63e0aafbb8abb2cc40a0cbcd5f68e

Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP0/0 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7 Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP0/1 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7

Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP0/2 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7




Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP1/1


OL-16506-08


Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7

Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP1/2 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7


Package: sipbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP2 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 31b36be34aa63e0aafbb8abb2cc40a0cbcd5f68e

Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP2/0 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7 Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP2/1 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7



Router# mkdir usb0:221subsCreate directory filename [221subs]? Created dir bootflash:221subs


OL-16506-08


Router# copy tftp: usb0:221subs Address or name of remote host []? 172.17.16.81Source filename []? /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.binDestination filename [asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin]? Accessing tftp://172.17.16.81//auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin...Loading /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin from 172.17.16.81 (via GigabitEthernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 209227980 bytes]


Router# request platform software package expand file usb0:221subs/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.binVerifying parametersValidating package typeCopying package filesSUCCESS: Finished expanding all-in-one software package.

Router# dir usb0:221subsDirectory of usb0:/221subs/

72013 -rw- 51904716 Oct 7 2008 15:46:02 -07:00 asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg72004 -rw- 5773 Oct 7 2008 15:46:02 -07:00 asr1000rp1-packages-adventerprisek9.02.02.01.122-33.XNB1.conf72014 -rw- 20533452 Oct 7 2008 15:46:03 -07:00 asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg72015 -rw- 22388940 Oct 7 2008 15:46:03 -07:00 asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg72016 -rw- 27961548 Oct 7 2008 15:46:03 -07:00 asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg72017 -rw- 50942156 Oct 7 2008 15:46:03 -07:00 asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg72018 -rw- 36442316 Oct 7 2008 15:46:03 -07:00 asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg72019 -rw- 26366156 Oct 7 2008 15:46:03 -07:00 asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg72005 -rw- 6290 Oct 7 2008 15:46:03 -07:00 packages.conf72003 -rw- 224768204 Oct 7 2008 15:38:57 -07:00 asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin


Router# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg bootflash:Destination filename [asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC


OL-16506-08


CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC51904716 bytes copied in 5.478 secs (9475122 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg bootflash:Destination filename [asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC20533452 bytes copied in 2.346 secs (8752537 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg bootflash: Destination filename [asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC22388940 bytes copied in 2.496 secs (8969928 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg bootflash:Destination filename [asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC27961548 bytes copied in 2.992 secs (9345437 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg bootflash:Destination filename [asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC50942156 bytes copied in 5.719 secs (8907529 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg bootflash: Destination filename [asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC36442316 bytes copied in 3.906 secs (9329830 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg bootflash:Destination filename [asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg]?


OL-16506-08


Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC26366156 bytes copied in 2.857 secs (9228616 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg stby-bootflash:Destination filename [asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC51904716 bytes copied in 5.478 secs (9475122 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg stby-bootflash:Destination filename [asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC20533452 bytes copied in 2.346 secs (8752537 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg stby-bootflash: Destination filename [asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC22388940 bytes copied in 2.496 secs (8969928 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg stby-bootflash:Destination filename [asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC27961548 bytes copied in 2.992 secs (9345437 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg stby-bootflash:Destination filename [asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC


OL-16506-08



Router# copy usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg stby-bootflash: Destination filename [asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC36442316 bytes copied in 3.906 secs (9329830 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg stby-bootflash:Destination filename [asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC26366156 bytes copied in 2.857 secs (9228616 bytes/sec)

Router#issu loadversion rp 1 file stby-bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg force--- Starting installation state synchronization ---Finished installation state synchronization


--- Starting image file verification ---Checking image file namesVerifying image file locationsLocating image files and validating name syntaxInspecting image file types WARNING: In-service installation of IOSD package WARNING: requires software redundancy on target RP WARNING: or on-reboot parameter WARNING: Automatically setting the on-reboot flag WARNING: In-service installation of RP Base package WARNING: requires software reboot of target RPProcessing image file constraintsCreating candidate provisioning fileFinished image file verification

--- Starting candidate package set construction ---Verifying existing software setProcessing candidate provisioning fileConstructing working set for candidate package setConstructing working set for running package setChecking command outputConstructing merge of running and candidate packagesFinished candidate package set construction

--- Starting compatibility testing ---Determining whether candidate package set is compatibleDetermining whether installation is validDetermining whether installation is valid ... skippedChecking IPC compatibility for candidate softwareChecking candidate package set infrastructure compatibilityChecking infrastructure compatibility with running softwareChecking infrastructure compatibility with running software ... skippedChecking package specific compatibility


OL-16506-08


Finished compatibility testing



Router# hw-module slot r1 reload

Router#*Sep 25 19:16:29.709: %ASR1000_OIR-6-OFFLINECARD: Card (rp) offline in slot R1*Sep 25 19:16:29.787: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_NOT_PRESENT)*Sep 25 19:16:29.788: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)*Sep 25 19:16:29.788: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_REDUNDANCY_STATE_CHANGE)*Sep 25 19:19:05.496: %ASR1000_OIR-6-ONLINECARD: Card (rp) online in slot R1*Sep 25 19:19:30.549: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_FOUND(4))

*Sep 25 19:19:30.550: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))

*Sep 25 19:19:31.512: %REDUNDANCY-3-IPC: IOS versions do not match. *Sep 25 19:21:02.256: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded*Sep 25 19:21:02.257: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)Router#

Router# issu loadversion rp 0 file bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.122-33.XNB1*.pkg slot 0 force--- Starting installation state synchronization ---Finished installation state synchronization







OL-16506-08





Software sets are identified as compatibleChecking IPC compatibility with running softwareChecking candidate package set infrastructure compatibilityChecking infrastructure compatibility with running softwareChecking package specific compatibilityFinished compatibility testing




--- Starting update running software ---Blocking peer synchronization of operating informationCreating the command set placeholder directory Finding latest command set Finding latest command shortlist lookup file Finding latest command shortlist file Assembling CLI output libraries Assembling CLI input libraries Applying interim IPC and database definitions Replacing running software Replacing CLI software Restarting software Restarting SIP0 Applying final IPC and database definitions

*Sep 29 15:12:18.972: %ASR1000_OIR-6-OFFLINECARD: Card (cc) offline in slot 0*Sep 29 15:12:18.973: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/0, interfaces disabled*Sep 29 15:12:18.973: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/1, interfaces disabled*Sep 29 15:12:18.973: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/2, interfaces disabled*Sep 29 15:12:18.973: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/3, interfaces disabled*Sep 29 15:12:18.977: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4XT-SERIAL) offline in subslot 0/0*Sep 29 15:12:18.981: %SPA_OIR-6-OFFLINECARD: SPA (SPA-5X1GE-V2) offline in subslot 0/1*Sep 29 15:12:18.985: %SPA_OIR-6-OFFLINECARD: SPA (SPA-2XOC3-POS) offline in subslot 0/2*Sep 29 15:12:18.994: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4XT-SERIAL) offline in subslot 0/3*Sep 29 15:13:04.553: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 0*Sep 29 15:13:06.051: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/0*Sep 29 15:13:06.935: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/1*Sep 29 15:13:07.765: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/2


OL-16506-08


*Sep 29 15:13:08.250: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/3 Generating software version information Notifying running software of updates Unblocking peer synchronization of operating informationUnmounting old packages

*Sep 29 15:13:14.936: %LINK-3-UPDOWN: SIP0/0: Interface EOBC0/1, changed state to up*Sep 29 15:13:21.431: %FPD_MGMT-3-MISSING_DEV_INFO: Could not find Unknown FPD (FPD ID=1) in the list of FPD IDs populated for SPA-4XT-SERIAL card in subslot 0/0.*Sep 29 15:13:21.634: %SPA_OIR-6-ONLINECARD: SPA (SPA-4XT-SERIAL) online in subslot 0/0Cleaning temporary installation files Finished update running software SUCCESS: Finished installing software.

*Sep 29 15:13:21.967: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/0, changed state to down*Sep 29 15:13:21.968: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/2, changed state to down*Sep 29 15:13:21.969: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/3, changed state to down*Sep 29 15:13:21.969: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/4, changed state to down*Sep 29 15:13:20.772: %LINK-3-UPDOWN: SIP0/1: Interface EOBC0/1, changed state to upFPD ID=1) in the list of FPD IDs populated for SPA-4XT-SERIAL card in subslot 0/3.*Sep 29 15:13:26.364: %SPA_OIR-6-ONLINECARD: SPA (SPA-4XT-SERIAL) online in subslot 0/3*Sep 29 15:13:25.347: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/0, changed state to down*Sep 29 15:13:25.567: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/2, changed state to down*Sep 29 15:13:26.141: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/3, changed state to down*Sep 29 15:13:26.603: %LINK-3-UPDOWN: SIP0/3: Interface EOBC0/1, changed state to up*Sep 29 15:13:28.355: %LINK-3-UPDOWN: Interface Serial0/3/1, changed state to down*Sep 29 15:13:27.112: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/4, changed state to downRouter#Router#Router#Router#Router# issu commitversion --- Starting installation changes ---Cancelling rollback timerFinished installation changes

SUCCESS: Installation changes committed

Router# issu loadversion rp 0 file bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.122-33.XNB1*.pkg slot 1 force--- Starting installation state synchronization ---Finished installation state synchronization




OL-16506-08





Determining whether installation is validSoftware sets are identified as compatibleChecking IPC compatibility with running softwareChecking candidate package set infrastructure compatibilityChecking infrastructure compatibility with running softwareChecking package specific compatibilityFinished compatibility testing





*Sep 29 15:17:29.883: %ASR1000_OIR-6-OFFLINECARD: Card (cc) offline in slot 1*Sep 29 15:17:29.887: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/0, interfaces disabled*Sep 29 15:17:29.887: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/1, interfaces disabled*Sep 29 15:17:29.887: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/3, interfaces disabled*Sep 29 15:17:29.890: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4X1FE-TX-V2) offline in subslot 1/0*Sep 29 15:17:29.895: %SPA_OIR-6-OFFLINECARD: SPA (SPA-2X1GE-V2) offline in subslot 1/1*Sep 29 15:17:29.898: %SPA_OIR-6-OFFLINECARD: SPA (SPA-1XOC12-POS) offline in subslot 1/3*Sep 29 15:18:15.555: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 1*Sep 29 15:18:16.939: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/0


OL-16506-08


*Sep 29 15:18:17.721: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/1*Sep 29 15:18:18.065: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/3*Sep 29 15:18:24.912: %LINK-3-UPDOWN: SIP1/0: Interface EOBC1/1, changed state to up*Sep 29 15:18:27.856: %SPA_OIR-6-ONLINECARD: SPA (SPA-4X1FE-TX-V2) online in subslot 1/0 Generating software version information Notifying running software of updates Unblocking peer synchronization of operating information

*Sep 29 15:18:30.388: %LINK-3-UPDOWN: SIP1/1: Interface EOBC1/1, changed state to upUnmounting old packages

*Sep 29 15:18:32.259: %SPA_OIR-6-ONLINECARD: SPA (SPA-2X1GE-V2) online in subslot 1/1*Sep 29 15:18:33.572: %SPA_OIR-6-ONLINECARD: SPA (SPA-1XOC12-POS) online in subslot 1/3Cleaning temporary installation files Finished update running software SUCCESS: Finished installing software.

*Sep 29 15:18:34.066: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/0, changed state to down*Sep 29 15:18:34.281: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/1, changed state to down*Sep 29 15:18:35.068: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0, changed state to downRouter#*Sep 29 15:18:33.905: %LINK-3-UPDOWN: SIP1/3: Interface EOBC1/1, changed state to up*Sep 29 15:18:34.625: %LINK-3-UPDOWN: SIP1/1: Interface GigabitEthernet1/1/0, changed state to down*Sep 29 15:18:35.293: %LINK-3-UPDOWN: SIP1/1: Interface GigabitEthernet1/1/1, changed state to down*Sep 29 15:18:38.950: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/0, changed state to up*Sep 29 15:18:38.686: %LINK-3-UPDOWN: SIP1/1: Interface GigabitEthernet1/1/0, changed state to up*Sep 29 15:18:39.972: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0, changed state to up

Router# issu commitversion --- Starting installation changes ---Cancelling rollback timerFinished installation changes


Router#Router#Router#Router# issu loadversion rp 0 file bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.122-33.XNB1*.pkg slot 2 force--- Starting installation state synchronization ---Finished installation state synchronization



--- Starting candidate package set construction ---


OL-16506-08


Verifying existing software setProcessing candidate provisioning fileConstructing working set for candidate package setConstructing working set for running package setChecking command outputConstructing merge of running and candidate packagesFinished candidate package set construction







--- Starting update running software ---Blocking peer synchronization of operating informationCreating the command set placeholder directory Finding latest command set Finding latest command shortlist lookup file Finding latest command shortlist file Assembling CLI output libraries Assembling CLI input libraries Applying interim IPC and database definitions Replacing running software Replacing CLI software Restarting software Applying final IPC and database definitions Generating software version information Notifying running software of updates Unblocking peer synchronization of operating informationUnmounting old packagesCleaning temporary installation files Finished update running software SUCCESS: Finished installing software.



OL-16506-08


SUCCESS: Installation changes committedRouter#Router#Router#

Router# issu loadversion rp 0 file bootflash:asr1000rp1-espbase*02.02.01.122-33.XNB1*.pkg slot 1--- Starting installation state synchronization ---Finished installation state synchronization











--- Starting commit of software changes ---Updating provisioning rollback filesCreating pending provisioning fileCommitting provisioning file


OL-16506-08


Finished commit of software changes


--- Starting update running software ---Blocking peer synchronization of operating informationCreating the command set placeholder directory Finding latest command set Finding latest command shortlist lookup file Finding latest command shortlist file Assembling CLI output libraries Assembling CLI input libraries Applying interim IPC and database definitions Replacing running software Replacing CLI software Restarting software Restarting ESP1 Applying final IPC and database definitions

003967: Oct 5 12:15:26.337 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F1:0 is pre-release hardware003972: Oct 5 12:16:07.792 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F1:0 is pre-release hardware003984: Oct 5 12:16:29.016 EDT: %IOSXE-3-PLATFORM: F0: cpp_cp: QFP:00 Thread:043 TS:00000014574807111078 %FWALL-3-HA_INVALID_MSG_RCVD: invalid version 65539 opcode b -Traceback= 801e9f58 800fd87c 800d9489 801c28e9 801c46a6 801c4c2a 80020055 Generating software version information Notifying running software of updates Unblocking peer synchronization of operating informationUnmounting old packagesCleaning temporary installation files Finished update running software SUCCESS: Finished installing software.



Router# issu loadversion rp 0 file bootflash:asr1000rp1-espbase.*02.02.01.122-33.XNB1*.pkg slot 0--- Starting installation state synchronization ---Finished installation state synchronization



--- Starting candidate package set construction ---Verifying existing software setProcessing candidate provisioning fileConstructing working set for candidate package set


OL-16506-08


Constructing working set for running package setChecking command outputConstructing merge of running and candidate packagesFinished candidate package set construction








004324: Oct 5 12:31:20.470 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is pre-release hardware004327: Oct 5 12:32:02.485 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is pre-release hardware Generating software version information Notifying running software of updates Unblocking peer synchronization of operating informationUnmounting old packagesCleaning temporary installation files Finished update running software SUCCESS: Finished installing software.



OL-16506-08



Router# issu loadversion rp 0 file bootflash:asr1000rp1-rp*02.02.01.122-33.XNB1*.pkg force--- Starting installation state synchronization ---Finished installation state synchronization




--- Starting compatibility testing ---Determining whether candidate package set is compatibleDetermining whether installation is validDetermining whether installation is valid ... skippedChecking IPC compatibility for candidate softwareChecking candidate package set infrastructure compatibilityChecking infrastructure compatibility with running softwareChecking infrastructure compatibility with running software ... skippedChecking package specific compatibilityFinished compatibility testing



Router# show version r0 provisioned Package: Provisioning File, version: n/a, status: active File: bootflash:packages.conf, on: RP0 Built: n/a, by: n/a File SHA1 checksum: aca136bd8bcb99f87e6aa7a0ce2a92a3b5a5a200

Package: rpbase, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP0


OL-16506-08


Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: 32b3fceaf59e3acd7cf9937ef33a822d6b359887

Package: rpaccess, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP0 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: 7c8dfdf9b2e3602b0c6c531a88dd93c8d2d180c6

Package: rpcontrol, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP0/0 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5

Package: rpios-adventerprisek9, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP0/0 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202

Package: rpcontrol, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP0/1 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5

Package: rpios-adventerprisek9, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP0/1 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202 Package: rpbase, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP1 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: 32b3fceaf59e3acd7cf9937ef33a822d6b359887


Package: rpcontrol, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP1/0


OL-16506-08


Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5



Package: rpios-adventerprisek9, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP1/1 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202

Package: rpios-adventerprisek9, version: unknown, status: active File: unknown, on: ESP0 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: unknown Package: rpios-adventerprisek9, version: unknown, status: active File: unknown, on: ESP1 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: unknown

Package: rpios-adventerprisek9, version: unknown, status: active File: unknown, on: SIP0 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: unknown

Package: rpios-adventerprisek9, version: unknown, status: active File: unknown, on: SIP0/0 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: unknown




Package: rpios-adventerprisek9, version: unknown, status: active File: unknown, on: SIP1


OL-16506-08


Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: unknown



Package: rpios-adventerprisek9, version: unknown, status: inactive File: unknown, on: SIP1/2 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: unknown


Package: rpios-adventerprisek9, version: unknown, status: inactive File: unknown, on: SIP2 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: unknown






Package: rpbase, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP0 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: 32b3fceaf59e3acd7cf9937ef33a822d6b359887


OL-16506-08










OL-16506-08













OL-16506-08











Router# redundancy force-switchover Proceed with switchover to standby RP? [confirm] Manual Swact = enabled

*Sep 25 19:38:33.562: %SYS-5-SWITCHOVER: Switchover requested by Exec. Reason: redundancy force-switchover

Router# request platform software package clean Cleaning up unnecessary package filesNo path specified, will use booted path bootflash:packages.confCleaning bootflash: Scanning boot directory for packages ... done. Preparing packages list to delete ... asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-espbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg


OL-16506-08


File is in use, will not delete. asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-sipbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-sipspa.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. packages.conf File is in use, will not delete. done. Files that will be deleted: asr1000-rommon.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000-rommon.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg asr1000rp1-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.bin asr1000rp1-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.bin asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.conf asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.conf asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg packages.conf.00- packages.conf.01- packages.conf.02- packages.conf.03- packages.conf.04-

Do you want to proceed? [confirm]y Deleting file bootflash:asr1000-rommon.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000-rommon.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.bin ... done. Deleting file bootflash:asr1000rp1-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.bin ... done. Deleting file bootflash:asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.conf ... done. Deleting file bootflash:asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.conf ... done.


OL-16506-08


Deleting file bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:packages.conf.00- ... done. Deleting file bootflash:packages.conf.01- ... done. Deleting file bootflash:packages.conf.02- ... done. Deleting file bootflash:packages.conf.03- ... done. Deleting file bootflash:packages.conf.04- ... done.SUCCESS: Files deleted.

Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1006 Router (request platform command set)

This section provides the instruction for performing an ISSU upgrade using sub-packages on a Cisco ASR 1006 router with a dual RP setup using the request platform command set.

Prerequisites

This procedure can only be performed if the current ASR 1006 has two active RPs and both RPs are running sub-packages.

SUMMARY STEPS

1. show version


show version standby-rp installed


show platform











OL-16506-08




7. copy file-system:asr1000rp1-espbase.version.pkg URL-to-directory-of-sub-packages-standby-RP







8. request platform software package install rp standby-RP file URL-to-standby-file-system:asr1000rp*version*.pkg force

9. hw-module slot standby-RP reload

10. request platform software package install rp active-RP file URL-to-active-file-system:image slot SIP-slot-number force


11. request platform software package install rp active-RP file URL-to-active-file-system:asr1000rp1-esp*version*.pkg slot standby-ESP-slot

request platform software package install rp active-RP file URL-to-active-file-system:asr1000rp1-esp*version*.pkg slot active-ESP-slot

12. request platform software package install rp active-RP file URL-to-active-file-system:asr1000rp*version*.pkg force

13. show version active-RP provisioned





OL-16506-08


DETAILED STEPS


Step 1 show version


show version standby-rp installed


show platform



























OL-16506-08



















OL-16506-08


Step 7 copy file-system:asr1000rp1-espbase.version.pkg URL-to-directory-of-sub-packages-standby-RP







ExampleRouter# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg stby-bootflash:

Router# copy usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg stby-bootflash:

Router# copy usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg stby-bootflash:

Router# copy usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg stby-bootflash:

Router# copy usb0:221subs/asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg stby-bootflash:

Router# copy usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg stby-bootflash:

Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg stby-bootflash:

Copy the sub-packages out of the temporary directory into the directory on the router where the sub-packages running the standby RP are currently stored.

Step 8 request platform software package install rp standby-RP file target-standbyRP-URL-for-sub-packages:asr1000rp*version*.pkg force

ExampleRouter# request platform software package install rp 1 file stby-bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg force

Upgrade the RP sub-packages on the standby RP, where the “rp*” wildcard is specified to capture all of the RP sub-packages for the desired upgrade release.



OL-16506-08


Step 9 hw-module slot standby-RP reload


Reload the standby RP.

Step 10 request platform software package install rp active-RP file URL-to-active-file-system:asr1000rp1-{sipbase,sipspa}*version*.pkg slot SIP-slot-number force


ExampleRouter# request platform software package install rp 0 file bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.122-33.XNB1*.pkg slot 0 force

Router# request platform software package install rp 0 file bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.122-33.XNB1*.pkg slot 1 force

Router# request platform software package install rp 0 file bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.122-33.XNB1*.pkg slot 2 force





Step 11 request platform software package install rp active-RP file URL-to-active-file-system:asr1000rp1-esp*version*.pkg slot standby-ESP-slot

request platform software package install rp active-RP file URL-to-active-file-system:asr1000rp1-esp*version*.pkg slot active-ESP-slot

ExampleRouter# request platform software package install rp 0 file bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.pkg slot 1

Router# request platform software package install rp 0 file bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.pkg slot 0

Upgrade the ESP Base sub-package on the standby and the active ESPs.

After entering the issu loadversion rp command on the active RP, the ESP switchover will occur automatically. Minimal traffic interruption will occur as a result of this switchover.



OL-16506-08


Examples






Slot Type State Insert time (ago) --------- ------------------- --------------------- ----------------- 0 ASR1000-SIP10 ok 00:03:03 0/0 SPA-4XT-SERIAL ok 00:01:35 0/1 SPA-5X1GE-V2 ok 00:01:35 0/2 SPA-2XOC3-POS ok 00:01:36 0/3 SPA-4XT-SERIAL ok 00:01:35 1 ASR1000-SIP10 ok 00:03:03 1/0 SPA-4X1FE-TX-V2 ok 00:01:36 1/1 SPA-2X1GE-V2 ok 00:01:35 1/3 SPA-1XOC12-POS ok 00:01:36 R0 ASR1000-RP1 ok, active 00:03:03 R1 ASR1000-RP1 ok, standby 00:03:03 F0 ASR1000-ESP10 ok, active 00:03:03 F1 ASR1000-ESP10 ok, standby 00:03:03 P0 ASR1006-PWR-AC ok 00:02:07

Step 12 request platform software package install rp active-RP file URL-to-active-file-system:asr1000rp*version*.pkg force

ExampleRouter# request platform software package install rp 0 file bootflash:asr1000rp1-rp*02.02.01.122-33.XNB1*.pkg force

Upgrade all of the sub-packages on the active RP.


Step 13 show version active-RP provisioned


ExampleRouter# show version r0 provisioned


(Optional) Confirm the sub-packages are provisioned and installed.



Force an RP switchover to complete the upgrade.

Step 15 request platform software package clean (Optional) Remove all unused sub-package files from the router.



OL-16506-08


P1 ASR1006-FAN ok 00:02:07

Slot CPLD Version Firmware Version --------- ------------------- --------------------------------------- 0 07091401 12.2(33r)XNB 1 07091401 12.2(33r)XNB R0 07062111 12.2(33r)XNB R1 07062111 12.2(33r)XNB F0 07091401 12.2(33r)XNB F1 07091401 12.2(33r)XNB

Router# show version r0 installed Package: Provisioning File, version: n/a, status: active File: bootflash:packages.conf, on: RP0 Built: n/a, by: n/a File SHA1 checksum: 174bef13f7ce20af077bae7aaefb5279c790dd57

Package: rpbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: RP0 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 661bcb2efda479533c87f23504bf7021d42b3165





Package: rpios-adventerprisek9, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: RP0/1 Built: 2008-09-24_03.46, by: mcpre


OL-16506-08


File SHA1 checksum: 88ea800ae1c094c46ca5e2f26d116f4e0012c219 Package: rpbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: RP1 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 661bcb2efda479533c87f23504bf7021d42b3165





Package: rpios-adventerprisek9, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: RP1/1 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 88ea800ae1c094c46ca5e2f26d116f4e0012c219

Package: espbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: ESP0 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: da8e5c93d0fa3f7cf27381841fa9efcde409964d

Package: espbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: ESP1 Built: 2008-09-24_03.46, by: mcpre


OL-16506-08


File SHA1 checksum: da8e5c93d0fa3f7cf27381841fa9efcde409964d


Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP0/0 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7 Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP0/1 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7





Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP1/1 Built: 2008-09-24_03.46, by: mcpre


OL-16506-08


File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7



Package: sipbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP2 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 31b36be34aa63e0aafbb8abb2cc40a0cbcd5f68e

Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP2/0 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7 Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg, on: SIP2/1 Built: 2008-09-24_03.46, by: mcpre File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7




Router# copy tftp: usb0:221subs


OL-16506-08


Address or name of remote host []? 172.17.16.81Source filename []? /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.binDestination filename [asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin]? Accessing tftp://172.17.16.81//auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin...Loading /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin from 172.17.16.81 (via GigabitEthernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 209227980 bytes]






Router# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg bootflash:Destination filename [asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC


OL-16506-08


CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC51904716 bytes copied in 5.478 secs (9475122 bytes/sec)






Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg bootflash:Destination filename [asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg]?


OL-16506-08


Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC26366156 bytes copied in 2.857 secs (9228616 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg stby-bootflash:Destination filename [asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC51904716 bytes copied in 5.478 secs (9475122 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg stby-bootflash:Destination filename [asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC20533452 bytes copied in 2.346 secs (8752537 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg stby-bootflash: Destination filename [asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC22388940 bytes copied in 2.496 secs (8969928 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg stby-bootflash:Destination filename [asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC27961548 bytes copied in 2.992 secs (9345437 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg stby-bootflash:Destination filename [asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC


OL-16506-08



Router# copy usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg stby-bootflash: Destination filename [asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC36442316 bytes copied in 3.906 secs (9329830 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg stby-bootflash:Destination filename [asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC26366156 bytes copied in 2.857 secs (9228616 bytes/sec)

Router# request platform software package install rp 1 file stby-bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg force--- Starting installation state synchronization ---Finished installation state synchronization




--- Starting compatibility testing ---Determining whether candidate package set is compatibleDetermining whether installation is validDetermining whether installation is valid ... skippedChecking IPC compatibility for candidate softwareChecking candidate package set infrastructure compatibilityChecking infrastructure compatibility with running softwareChecking infrastructure compatibility with running software ... skipped


OL-16506-08


Checking package specific compatibilityFinished compatibility testing



Router# hw-module slot r1 reload

Router#*Sep 25 18:20:15.371: %ASR1000_OIR-6-OFFLINECARD: Card (rp) offline in slot R1*Sep 25 18:20:15.426: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_NOT_PRESENT)*Sep 25 18:20:15.427: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)*Sep 25 18:20:15.427: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_REDUNDANCY_STATE_CHANGE)*Sep 25 18:22:58.808: %ASR1000_OIR-6-ONLINECARD: Card (rp) online in slot R1*Sep 25 18:23:23.038: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_FOUND(4))


*Sep 25 18:23:23.894: %REDUNDANCY-3-IPC: IOS versions do not match. *Sep 25 18:24:54.264: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded*Sep 25 18:24:54.265: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)Router#shoRouter#Router#

Router#request platform software package install rp 0 file bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 0 force--- Starting installation state synchronization ---Finished installation state synchronization





WARNING:


OL-16506-08


WARNING: Candidate software combination not found in compatibility databaseWARNING:








--- Starting update running software ---Blocking peer synchronization of operating informationCreating the command set placeholder directory Finding latest command set Finding latest command shortlist lookup file Finding latest command shortlist file Assembling CLI output libraries Assembling CLI input libraries Applying interim IPC and database definitions Replacing running software Replacing CLI software Restarting software Restarting SIP0

*Sep 29 13:48:03.269: %ASR1000_OIR-6-OFFLINECARD: Card (cc) offline in slot 0*Sep 29 13:48:03.270: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/0, interfaces disabled*Sep 29 13:48:03.270: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/1, interfaces disabled*Sep 29 13:48:03.271: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/2, interfaces disabled*Sep 29 13:48:03.271: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/3, interfaces disabled*Sep 29 13:48:03.274: %SPA_OIR-6-OFFLINECARD: Applying final IPC and database definitionsSPA (SPA-4XT-SERIAL) offline in subslot 0/0*Sep 29 13:48:03.278: %SPA_OIR-6-OFFLINECARD: SPA (SPA-5X1GE-V2) offline in subslot 0/1*Sep 29 13:48:03.282: %SPA_OIR-6-OFFLINECARD: SPA (SPA-2XOC3-POS) offline in subslot 0/2*Sep 29 13:48:03.286: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4XT-SERIAL) offline in subslot 0/3*Sep 29 13:48:49.448: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 0


OL-16506-08


*Sep 29 13:48:50.872: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/0*Sep 29 13:48:51.703: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/1*Sep 29 13:48:52.680: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/2*Sep 29 13:48:53.217: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/3 Generating software version information

*Sep 29 13:49:01.223: %FPD_MGMT-3-MISSING_DEV_INFO: Could not find Unknown FPD (FPD ID=1) in the list of FPD IDs populated for SPA-4XT-SERIAL card in subslot 0/0. Notifying running software of updates Unblocking peer synchronization of operating information

*Sep 29 13:49:01.336: %SPA_OIR-6-ONLINECARD: SPA (SPA-4XT-SERIAL) online in subslot 0/0*Sep 29 13:49:03.344: %LINK-3-UPDOWN: Interface Serial0/0/2, changed state to downUnmounting old packages

*Sep 29 13:48:59.734: %LINK-3-UPDOWN: SIP0/0: Interface EOBC0/1, changed state to upCleaning temporary installation files Finished update running software SUCCESS: Finished installing software.

Router#*Sep 29 13:49:05.151: %LINK-3-UPDOWN: SIP0/1: Interface EOBC0/1, changed state to up*Sep 29 13:49:08.006: %SPA_OIR-6-ONLINECARD: SPA (SPA-5X1GE-V2) online in subslot 0/1*Sep 29 13:49:09.086: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/2, changed state to down*Sep 29 13:49:09.087: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/3, changed state to down*Sep 29 13:49:09.087: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/4, changed state to down*Sep 29 13:49:09.294: %SPA_OIR-6-ONLINECARD: SPA (SPA-2XOC3-POS) online in subslot 0/2*Sep 29 13:49:09.580: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/0, changed state to down*Sep 29 13:49:07.951: %LINK-3-UPDOWN: SIP0/2: Interface EOBC0/1, changed state to up*Sep 29 13:49:10.067: %ASR1000_SPA-3-UNSUPPORTED_DATA: Data conversion error (media type, 0x1D)-Traceback= 1#e9e10f82e25cfb5f8d242ef69a2dec39 :10000000+61C550 :10000000+61A6B4 :10000000+61AA38 :10000000+25A3950 :10000000+259AB1C ethernet:DF73000+2AA6C if_combined:FD4F000+70070 if_combined:FD4F000+70288 :10000000+2434540 :10000000+2433D9C*Sep 29 13:49:10.070: %ASR1000_SPA-3-UNSUPPORTED_DATA: Data conversion error (media type, 0x1D)-Traceback= 1#e9e10f82e25cfb5f8d242ef69a2dec39 :10000000+61C550 :10000000+61A6B4 :10000000+61AA38 :10000000+25A3950 :10000000+259AB1C ethernet:DF73000+2AA6C if_combined:FD4F000+70070 if_combined:FD4F000+70288 :10000000+2434540 :10000000+2433D9C*Sep 29 13:49:11.161: %FPD_MGMT-3-MISSING_DEV_INFO: Could not find Unknown FPD (FPD ID=1) in the list of FPD IDs populated for SPA-4XT-SERIAL card in subslot 0/3.*Sep 29 13:49:11.289: %SPA_OIR-6-ONLINECARD: SPA (SPA-4XT-SERIAL) online in subslot 0/3*Sep 29 13:49:11.605: %ASR1000_SPA-3-UNSUPPORTED_DATA: Data conversion error (media type, 0x1D)-Traceback= 1#e9e10f82e25cfb5f8d242ef69a2dec39 :10000000+61C550 :10000000+61A6B4 :10000000+61AA38 :10000000+25A3950 :10000000+259AB1C ethernet:DF73000+2AA6C if_combined:FD4F000+70070 if_combined:FD4F000+70288 :10000000+2434540 :10000000+2433D9C*Sep 29 13:49:10.788: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/0, changed state to down*Sep 29 13:49:11.114: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/2, changed state to down*Sep 29 13:49:11.217: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/3, changed state to down*Sep 29 13:49:11.530: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/4, changed state to down*Sep 29 13:49:10.567: %LINK-3-UPDOWN: SIP0/3: Interface EOBC0/1, changed state to up*Sep 29 13:49:13.289: %LINK-3-UPDOWN: Interface Serial0/3/1, changed state to downRouter#Router#


OL-16506-08


Router#request platform software package install rp 0 file bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 1 force--- Starting installation state synchronization ---Finished installation state synchronization










--- Starting update running software ---Blocking peer synchronization of operating informationCreating the command set placeholder directory Finding latest command set Finding latest command shortlist lookup file Finding latest command shortlist file Assembling CLI output libraries Assembling CLI input libraries Applying interim IPC and database definitions Replacing running software


OL-16506-08


Replacing CLI software Restarting software Restarting SIP1 Applying final IPC and database definitions

*Sep 29 13:53:01.370: %ASR1000_OIR-6-OFFLINECARD: Card (cc) offline in slot 1*Sep 29 13:53:01.370: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/0, interfaces disabled*Sep 29 13:53:01.370: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/1, interfaces disabled*Sep 29 13:53:01.370: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/3, interfaces disabled*Sep 29 13:53:01.373: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4X1FE-TX-V2) offline in subslot 1/0*Sep 29 13:53:01.378: %SPA_OIR-6-OFFLINECARD: SPA (SPA-2X1GE-V2) offline in subslot 1/1*Sep 29 13:53:01.381: %SPA_OIR-6-OFFLINECARD: SPA (SPA-1XOC12-POS) offline in subslot 1/3*Sep 29 13:53:45.225: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 1*Sep 29 13:53:47.082: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/0*Sep 29 13:53:47.833: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/1*Sep 29 13:53:48.727: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/3 Generating software version information Notifying running software of updates Unblocking peer synchronization of operating information

*Sep 29 13:53:55.700: %LINK-3-UPDOWN: SIP1/0: Interface EOBC1/1, changed state to upUnmounting old packages

*Sep 29 13:54:03.132: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/0, changed state to down*Sep 29 13:54:03.135: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/1, changed state to down*Sep 29 13:54:00.621: %LINK-3-UPDOWN: SIP1/1: Interface EOBC1/1, changed state to up*Sep 29 13:54:03.449: %SPA_OIR-6-ONLINECARD: SPA (SPA-2X1GE-V2) online in subslot 1/1*Sep 29 13:54:04.139: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0, changed state to downCleaning temporary installation files Finished update running software SUCCESS: Finished installing software.

*Sep 29 13:54:04.320: %SPA_OIR-6-ONLINECARD: SPA (SPA-4X1FE-TX-V2) online in subslot 1/0Router#*Sep 29 13:54:05.911: %LINK-3-UPDOWN: SIP1/1: Interface GigabitEthernet1/1/0, changed state to down*Sep 29 13:54:06.243: %LINK-3-UPDOWN: SIP1/1: Interface GigabitEthernet1/1/1, changed state to down*Sep 29 13:54:03.492: %LINK-3-UPDOWN: SIP1/3: Interface EOBC1/1, changed state to up*Sep 29 13:54:09.434: %SPA_OIR-6-ONLINECARD: SPA (SPA-1XOC12-POS) online in subslot 1/3*Sep 29 13:54:10.427: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/0, changed state to up*Sep 29 13:54:09.709: %LINK-3-UPDOWN: SIP1/1: Interface GigabitEthernet1/1/0, changed state to up*Sep 29 13:54:11.445: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0, changed state to upRouter#Router#Router#Router#Router# request platform software package install rp 0 file bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 2 force--- Starting installation state synchronization ---Finished installation state synchronization


--- Starting image file verification ---


OL-16506-08


Checking image file namesVerifying image file locationsLocating image files and validating name syntaxInspecting image file typesProcessing image file constraintsCreating candidate provisioning fileFinished image file verification








--- Starting update running software ---Blocking peer synchronization of operating informationCreating the command set placeholder directory Finding latest command set Finding latest command shortlist lookup file Finding latest command shortlist file Assembling CLI output libraries Assembling CLI input libraries Applying interim IPC and database definitions Replacing running software Replacing CLI software Restarting software Applying final IPC and database definitions Generating software version information Notifying running software of updates Unblocking peer synchronization of operating informationUnmounting old packagesCleaning temporary installation files Finished update running software


OL-16506-08


SUCCESS: Finished installing software.Router#

Router# request platform software package install rp 0 file bootflash:asr1000rp1-espbase*02.02.01.122-33.XNB1*.pkg slot 1--- Starting installation state synchronization ---Finished installation state synchronization













OL-16506-08




003967: Oct 5 12:15:26.337 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F1:0 is pre-release hardware003972: Oct 5 12:16:07.792 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F1:0 is pre-release hardware003984: Oct 5 12:16:29.016 EDT: %IOSXE-3-PLATFORM: F0: cpp_cp: QFP:00 Thread:043 TS:00000014574807111078 %FWALL-3-HA_INVALID_MSG_RCVD: invalid version 65539 opcode b -Traceback= 801e9f58 800fd87c 800d9489 801c28e9 801c46a6 801c4c2a 80020055 Generating software version information Notifying running software of updates Unblocking peer synchronization of operating informationUnmounting old packagesCleaning temporary installation files Finished update running software SUCCESS: Finished installing software.

Router# request platform software package install rp 0 file bootflash:asr1000rp1-espbase.*02.02.01.122-33.XNB1*.pkg slot 0--- Starting installation state synchronization ---Finished installation state synchronization






OL-16506-08








004324: Oct 5 12:31:20.470 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is pre-release hardware004327: Oct 5 12:32:02.485 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is pre-release hardware Generating software version information Notifying running software of updates Unblocking peer synchronization of operating informationUnmounting old packagesCleaning temporary installation files Finished update running software SUCCESS: Finished installing software.

Router# request platform software package install rp 0 file bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg --- Starting installation state synchronization ---Finished installation state synchronization


--- Starting image file verification ---Checking image file namesVerifying image file locations


OL-16506-08


Locating image files and validating name syntaxInspecting image file types WARNING: In-service installation of IOSD package WARNING: requires software redundancy on target RP WARNING: or on-reboot parameter WARNING: Automatically setting the on-reboot flag WARNING: In-service installation of RP Base package WARNING: requires software reboot of target RPProcessing image file constraintsCreating candidate provisioning fileFinished image file verification








Package: rpcontrol, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active


OL-16506-08


File: bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP0/0 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5







Package: rpcontrol, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive


OL-16506-08


File: bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP1/1 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5












OL-16506-08









Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router

This section explains how to upgrade sub-packages using ISSU on a Cisco ASR 1002 or 1004 Router.

It contains the following sections:

• Configuring RPR or SSO on a Cisco ASR 1002 or Cisco ASR 1004 Router, page 4-72

• Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router (issu command set), page 4-75

• Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router (request platform command set), page 4-101

Configuring RPR or SSO on a Cisco ASR 1002 or Cisco ASR 1004 Router

The following instructions show how to configure RPR or SSO on a Cisco ASR 1002 and Cisco ASR 1004 Routers. The standby IOS process is created automatically as part of these configuration steps.

Step 1 (Optional) Enter the show version command to confirm the amount of DRAM on your router.

Router# show version<some output removed for brevity>


OL-16506-08


32768K bytes of non-volatile configuration memory.4194304K bytes of physical memory.921599K bytes of eUSB flash at bootflash:.39004543K bytes of SATA hard disk at bootflash:.

Configuration register is 0x2102

In the example show version output, the router has 4 GB of DRAM memory.

If you are using a Cisco ASR 1002 Router or Cisco ASR 1004 Router with 2 GB of DRAM memory on the RP, RPR or SSO cannot be configured on your RP.

Step 2 (Optional) Enter show redundancy states to see the current HA configuration.

Router# show redundancy states my state = 13 -ACTIVE peer state = 1 -DISABLED Mode = Simplex Unit ID = 6

Redundancy Mode (Operational) = Non-redundantRedundancy Mode (Configured) = Non-redundantRedundancy State = Non Redundant

In this example, HA for the dual RPs is not configured, as indicated by the non-redundant operational mode.

Step 3 Enter configure terminal to enter global configuration mode.

Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#

Step 4 Enter the redundancy command to enter redundancy configuration mode.

Router(config)# redundancyRouter(config-red)#

Step 5 Enter mode rpr to enable RPR, mode sso to enable SSO, or mode none to disable dual software redundancy.

Router(config-red)# mode rpr

Router(config-red)# mode sso

Router(config-red)# mode none

Step 6 Return to privileged EXEC mode using any method, such as entering Ctrl-Z or the exit command multiple times until you get to the # router prompt.

Router(config-red)#^ZRouter#

Router(config-red)#exitRouter(config)#exitRouter#

Step 7 Enter the show redundancy states command to confirm the configured redundancy mode changed to your new configuration.

In the following example, the configured redundancy mode has been changed to SSO. Note that the operation redundancy mode remains unchanged.

Router# show redundancy states my state = 13 -ACTIVE


OL-16506-08


peer state = 1 -DISABLED Mode = Simplex Unit ID = 6

Redundancy Mode (Operational) = Non-redundantRedundancy Mode (Configured) = ssoRedundancy State = Non Redundant

Step 8 Enter the copy running-config startup-config command to save the new configuration, and press enter to confirm the filename (or change the name, if desired).

Router# copy running-config startup-configDestination filename [startup-config]? Building configuration...[OK]PE25_ASR-1004#

Step 9 The router must be reloaded for the new HA configuration. Enter the reload command to reload the router.

Router# reloadProceed with reload? [confirm]<bootup messages removed for brevity>

If you are not using the console port to complete this procedure, your session may be terminated at this point. If you session is terminated, give the router a few minutes to complete the reload and then log into the router.

Step 10 After the reload is complete, enter the show redundancy states command to confirm the operational redundancy mode has changed to the mode that you configured in Step 5.

In this example, the operational redundancy mode has changed to SSO.

Router# show redundancy states my state = 13 -ACTIVE peer state = 8 -STANDBY HOT Mode = Duplex Unit ID = 6

Redundancy Mode (Operational) = ssoRedundancy Mode (Configured) = ssoRedundancy State = sso

Step 11 (Optional) To confirm an active and a standby IOS process exist, and how the processes are numbered, enter the show platform command.

In this example, the show platform command output reveals that R0/0 is the active IOS process and R0/1 is the standby IOS process.

Router# show platformChassis type: ASR1004

Slot Type State Insert time (ago) --------- ------------------- --------------------- ----------------- 0 ASR1000-SIP10 ok 00:52:34 0/0 SPA-2X1GE-V2 ok 00:51:30 0/1 SPA-2XT3/E3 ok 00:51:24 R0 ASR1000-RP1 ok 00:52:34 R0/0 ok, active 00:52:34 R0/1 ok, standby 00:51:00 F0 ASR1000-ESP10 ok, active 00:52:34 P0 ASR1004-PWR-AC ok 00:51:57 P1 ASR1004-PWR-AC ok 00:51:57


OL-16506-08


Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router (issu command set)

This section provides instructions on using ISSU to upgrade a Cisco ASR 1002 or 1004 Router running sub-packages.

These instructions assume two IOS processes are active on the RP and that the router is already running using sub-packages. For information on checking and configuring two IOS processes on the same RP, see the “Configuring RPR or SSO on a Cisco ASR 1002 or Cisco ASR 1004 Router” section on page 4-72.

SUMMARY STEPS

1. show version

show version installed


show platform


2. redundancy

mode sso












8. issu loadversion rp 0 file file-system:asr1000rp1-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force



11. show platform

12. issu loadversion rp 0 file file-system:asr1000rp1-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force


14. issu loadversion rp 0 file file-system:asr1000rp1-{sipbase,sipspa}*version*.pkg slot SIP-slot-number force

issu commitversion


OL-16506-08


Repeat this step for each SIP installed in your router before proceeding to the next step.

15. issu loadversion rp 0 file file-system:asr1000rp1-esp*version*.pkg force


17. issu loadversion rp 0 file file-system:asr1000rp*version*.pkg

18. show version installed

Step 19 and later does not have to be performed immediately, and should be done at a convenient time.

19. reload



OL-16506-08


DETAILED STEPS


Step 1 show version



show platform






Router# show redundancy-states






Step 2 redundancy

mode sso

ExampleRouter(config)# redundancyRouter(config-red)# mode sso

Configure SSO if it is not already configured.

Note Save the configuration after making this configuration step.

Although SSO is the better redundancy option, RPR can also be used to establish a second IOS process on the RP to complete this process.











OL-16506-08



(Optional) dir target-URL


Router# dir usb0:221subs








OL-16506-08

















Step 8 issu loadversion rp 0 file file-system:asr1000rp1-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force

ExampleRouter# issu loadversion rp 0 file bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}*02.02.01.122-33.XNB1*.pkg bay 1 force

Upgrade the RPAccess, RPIOS, and RPControl sub-packages in the standby bay.



OL-16506-08




Once the SSO or RPR state is reached, commit the software version.



Force a switchover from the active IOS process to the standby IOS process.

Note Your connection to the router often drops and is expected behavior at this point of the procedure in many scenarios. If this step drops your connection to the router, wait a few minutes before reconnecting to the router and then continue to Step 11.

Step 11 show platform

ExampleRouter# show platform

(Optional) Monitor system state to ensure both IOS processes are active.

Step 12 issu loadversion rp 0 file file-system:asr1000rp1-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force

ExampleRouter# issu loadversion rp 0 file bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}*02.02.01.122-33.XNB1*.pkg bay 0 force

Upgrade the RPAccess, RPIOS, and RPControl sub-packages in the standby bay (a different bay than in Step 8).



Commit the software version.



OL-16506-08


Step 14 issu loadversion rp 0 file file-system:asr1000rp1-{sipbase,sipspa}*version*.pkg slot SIP-slot-number force

issu commitversion


ExampleRouter# issu loadversion rp 0 file bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 0 force


Router# issu loadversion rp 0 file bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 1 force


Router# issu loadversion rp 0 file bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 2 force






Step 15 issu loadversion rp 0 file file-system:asr1000rp1-esp*version*.pkg force

ExampleRouter# issu loadversion rp 0 file bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.pkg force

Upgrade the ESP Base sub-package.



Commit the ESP Base software.

Step 17 issu loadversion rp 0 file file-system:asr1000rp*version*.pkg

ExampleRouter# issu loadversion rp 0 file bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg

Upgrades all sub-packages, including the RPBase sub-package, which is the last sub-package that needs to be upgraded.


Step 18 show version installed

ExampleRouter# show version installed

(Optional) Verify that the sub-packages are properly installed.



OL-16506-08


Examples





cisco ASR1004 (RP1) processor with 752142K/6147K bytes of memory.5 Gigabit Ethernet interfaces2 Serial interfaces32768K bytes of non-volatile configuration memory.4194304K bytes of physical memory.937983K bytes of eUSB flash at bootflash:.39004543K bytes of SATA hard disk at bootflash:.253424K bytes of USB flash at usb0:.


Router# show version installedPackage: Provisioning File, version: n/a, status: active File: bootflash:packages.conf, on: RP0 Built: n/a, by: n/a File SHA1 checksum: 9172d30751d79fc1afb7b405eca244bbf9f8f2f2

Package: rpbase, version: 02.01.00.122-33.XNA, status: active File: bootflash:asr1000rp1-rpbase.02.01.00.122-33.XNA.pkg, on: RP0 Built: 2008-05-01_01.48, by: mcpre File SHA1 checksum: c09fe08ff908c8ce0b789d8acc774fe43dacf5e3

Package: rpaccess, version: 02.01.01.122-33.XNA, status: active File: bootflash:asr1000rp1-rpaccess.02.01.01.122-33.XNA.pkg, on: RP0 Built: 2008-07-08_16.01, by: mcpre File SHA1 checksum: c1afc591c9cd198409820226c4f23d2647d0d138<output removed for brevity>

Router# show redundancy states my state = 13 -ACTIVE peer state = 4 -STANDBY COLD Mode = Duplex Unit ID = 48

Redundancy Mode (Operational) = ssoRedundancy Mode (Configured) = ssoRedundancy State = sso Maintenance Mode = Disabled Manual Swact = disabled (peer unit not yet in terminal standby state)

Step 19 reload

ExampleRouter# reload

Reload the RP.

Tip The router will continue normal operation even without a reload, so you can reload the router during scheduled maintenance or a slower traffic period.

Step 20 request platform software package clean (Optional) Removes the unused sub-packages from the router.



OL-16506-08


Communications = Up

client count = 67 client_notification_TMR = 30000 milliseconds RF debug mask = 0x0


Slot Type State Insert time (ago) --------- ------------------- --------------------- ----------------- 0 ASR1000-SIP10 ok 00:04:43 0/0 SPA-1XOC12-POS ok 00:03:25 0/1 SPA-2XOC3-POS ok 00:03:24 0/3 SPA-5X1GE-V2 ok 00:03:20 R0 ASR1000-RP1 ok 00:04:43 R0/0 ok, active 00:04:43 R0/1 ok, standby 00:02:55 F0 ASR1000-ESP10 ok, active 00:04:43 P0 ASR1004-PWR-AC ok 00:03:53 P1 ASR1004-FAN ok 00:03:53

Slot CPLD Version Firmware Version --------- ------------------- --------------------------------------- 0 07091401 12.2(33r)XN1 R0 07062111 12.2(33r)XN2 F0 07091401 12.2(33r)XN1


Router# copy tftp: usb0:221subs Address or name of remote host []? 172.17.16.81Source filename []? /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.binDestination filename [asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin]? Accessing tftp://172.17.16.81//auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin...Loading /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin from 172.17.16.81 (via GigabitEthernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 209227980 bytes]





OL-16506-08




Router# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg bootflash:Destination filename [asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC51904716 bytes copied in 5.478 secs (9475122 bytes/sec)





OL-16506-08




Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg bootflash:Destination filename [asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC26366156 bytes copied in 2.857 secs (9228616 bytes/sec)

Router# issu loadversion rp 0 file bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}*02.02.01.122-33.XNB1*.pkg bay 1 force--- Starting file path checking ---Finished file path checking





OL-16506-08







--- Starting impact testing ---Checking operational impact of change WARNING: Connection may be lost during installation of IOS packageFinished impact testing



--- Starting update running software ---Blocking peer synchronization of operating informationCreating the command set placeholder directory Finding latest command set Finding latest command shortlist lookup file Finding latest command shortlist file Assembling CLI output libraries Assembling CLI input libraries Applying interim IPC and database definitions Replacing running software Replacing CLI software Restarting software

*Sep 25 18:04:24.517: %ASR1000_INFRA-6-BIPC_READ_ERR: R0/0: ppc_linux_iosd-image: connection read error from iman bipc, rc 32, bring down IPC Restarting IOS PID: 19257, in slot/bay 0/1

*Sep 25 18:04:39.325: %PMAN-3-PROCHOLDDOWN: R0/0: pman.sh: The process ppc_linux_iosd-image has been helddown (rc 137)*Sep 25 18:04:39.422: %PMAN-0-PROCFAILCRIT: R0/0: pvp.sh: A critical process ppc_linux_iosd_image has failed (rc 137)*Sep 25 18:04:39.462: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_NOT_PRESENT)*Sep 25 18:04:39.462: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)*Sep 25 18:04:39.463: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_REDUNDANCY_STATE_CHANGE)FIXME: kill/restart security package: 0 1 rp_security1 1 rp_security Applying final IPC and database definitions


OL-16506-08


Generating software version information Notifying running software of updates Unblocking peer synchronization of operating informationUnmounting old packagesCleaning temporary installation files Finished update running software SUCCESS: Finished installing software.

Router#*Sep 25 18:05:32.476: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_FOUND(4))


Router#*Sep 25 18:05:33.409: %REDUNDANCY-3-IPC: IOS versions do not match.*Sep 25 18:07:39.886: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeededRouter#*Sep 25 18:07:39.888: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)Router#Router# issu commitversion --- Starting installation changes ---Cancelling rollback timerFinished installation changes


Router# redundancy force-switchover Proceed with switchover to standby RP? [confirm]

%ASR1000_INFRA-6-CONSOLE_ACTIVE: R0/1 console active. Press RETURN to get started!

*Sep 25 18:08:27.898: %CMANRP-6-CMHASTATUS: RP switchover, received fastpath becoming active event*Sep 25 18:08:28.224: %CMANRP-6-CMHASTATUS: RP switchover, received chassis event to become active*Sep 25 18:08:28.229: %NETCLK-5-NETCLK_MODE_CHANGE: Network clock source not available. The network clock has changed to freerun

*Sep 25 18:08:28.243: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_NOT_PRESENT)*Sep 25 18:08:28.243: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_DOWN)*Sep 25 18:08:28.243 Manual Swact = enabled

*Sep 25 18:08:27.956: %SYS-5-SWITCHOVER: Switchover requested by Exec. Reason: redundancy force-switchover.: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_REDUNDANCY_STATE_CHANGE)*Sep 25 18:08:28.248: %PLATFORM-6-HASTATUS: RP switchover, sent message became active. IOS is ready to switch to primary after chassis confirmation*Sep 25 18:08:28.249: %CMANRP-6-CMHASTATUS: RP switchover, received chassis event became active*Sep 25 18:08:28.497: %PLATFORM-6-HASTATUS_DETAIL: RP switchover, received chassis event became active. Switch to primary (count 1)*Sep 25 18:08:29.746: %ACE-3-TRANSERR: ASR1000-ESP(14): IKEA trans 0x3; opcode 0x25; param 0xA; error 0x4; retry cnt 0*Sep 25 18:08:29.746: %ACE-3-TRANSERR: ASR1000-ESP(14): IKEA trans 0x4; opcode 0x25; param 0xB; error 0x4; retry cnt 0*Sep 25 18:08:29.746: %ACE-3-TRANSERR: ASR1000-ESP(14): IKEA trans 0x5; opcode 0x25; param 0xC; error 0x4; retry cnt 0*Sep 25 18:08:30.630: %LINK-3-UPDOWN: Interface Null0, changed state to up*Sep 25 18:08:30.631: %LINK-3-UPDOWN: Interface Loopback0, changed state to up*Sep 25 18:08:30.635: %LINK-5-CHANGED: Interface POS0/0/0, changed state to administratively down


OL-16506-08


*Sep 25 18:08:30.636: %LINK-5-CHANGED: Interface POS0/1/0, changed state to administratively down*Sep 25 18:08:30.636: %LINK-5-CHANGED: Interface POS0/1/1, changed state to administratively down*Sep 25 18:08:30.636: %LINK-5-CHANGED: Interface GigabitEthernet0/3/0, changed state to administratively down*Sep 25 18:08:30.636: %LINK-5-CHANGED: Interface GigabitEthernet0/3/1, changed state to administratively down*Sep 25 18:08:30.636: %LINK-5-CHANGED: Interface GigabitEthernet0/3/2, changed state to administratively down*Sep 25 18:08:30.636: %LINK-5-CHANGED: Interface GigabitEthernet0/3/3, changed state to administratively down*Sep 25 18:08:30.636: %LINK-5-CHANGED: Interface GigabitEthernet0/3/4, changed state to administratively down*Sep 25 18:08:31.630: %LINEPROTO-5-UPDOWN: Line protocol on Interface Null0, changed state to up*Sep 25 18:08:31.630: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up*Sep 25 18:09:16.667: %REDUNDANCY-3-IPC: IOS versions do not match. *Sep 25 18:09:16.717: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_FOUND(4))


*Sep 25 18:11:00.500: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded*Sep 25 18:11:00.502: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)Router# show platform Chassis type: ASR1004

Slot Type State Insert time (ago) --------- ------------------- --------------------- ----------------- 0 ASR1000-SIP10 ok 00:14:44 0/0 SPA-1XOC12-POS ok 00:04:02 0/1 SPA-2XOC3-POS ok 00:04:02 0/3 SPA-5X1GE-V2 ok 00:04:02 R0 ASR1000-RP1 ok 00:14:44 R0/0 ok, standby 00:02:01 R0/1 ok, active 00:05:57 F0 ASR1000-ESP10 ok, active 00:14:44 P0 ASR1004-PWR-AC ok 00:13:54 P1 ASR1004-FAN ok 00:13:54


Router#Router# issu loadversion rp 0 file bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}*02.02.01.122-33.XNB1*.pkg bay 0 force--- Starting file path checking ---Finished file path checking



OL-16506-08









--- Starting update running software ---Blocking peer synchronization of operating informationCreating the command set placeholder directory Finding latest command set Finding latest command shortlist lookup file Finding latest command shortlist file Assembling CLI output libraries Assembling CLI input libraries Applying interim IPC and database definitions Replacing running software Replacing CLI software Restarting software

*Sep 25 18:13:27.604: %IOSXE-4-PLATFORM: R0/0: kernel: scooby: Scooby: FD close Restarting IOS PID: 20492, in slot/bay 0/0

*Sep 25 18:13:53.696: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_NOT_PRESENT)*Sep 25 18:13:53.696: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)*Sep 25 18:13:53.697: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_REDUNDANCY_STATE_CHANGE)FIXME: kill/restart security package: 0 0 rp_security1 0 rp_security Applying final IPC and database definitions


OL-16506-08


*Sep 25 18:13:56.593: %DYNCMD-7-CMDSET_UNLOADED: The Dynamic Command set from the Shell Manager has been unloaded*Sep 25 18:13:56.963: %DYNCMD-7-CMDSET_LOADED: The Dynamic Command set has been loaded from the Shell Manager*Sep 25 18:13:59.457: %RF-5-RF_RELOAD: Peer reload. Reason: EHSA standby down Generating software version information Notifying running software of updates Unblocking peer synchronization of operating informationUnmounting old packagesCleaning temporary installation files Finished update running software SUCCESS: Finished installing software.

Router#Router#Router# issu commitversion --- Starting installation changes ---Cancelling rollback timerFinished installation changes


*Sep 25 18:14:47.232: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0:0 is pre-release hardware*Sep 25 18:14:47.299: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_FOUND(4))


Router# issu loadversion rp 0 file bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 0 force--- Starting file path checking ---Finished file path checking







OL-16506-08









*Sep 29 11:05:40.249: %ASR1000_OIR-6-OFFLINECARD: Card (cc) offline in slot 0*Sep 29 11:05:40.250: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/0, interfaces disabled*Sep 29 11:05:40.250: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/1, interfaces disabled*Sep 29 11:05:40.250: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/3, interfaces disabled*Sep 29 11:05:48.163: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0:0 is pre-release hardware Generating software version information Notifying running software of updates Unblocking peer synchronization of operating informationUnmounting old packagesCleaning temporary installation files Finished update running software SUCCESS: Finished installing software.

Router#*Sep 29 11:06:23.227: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 0Router#


OL-16506-08


*Sep 29 11:06:23.225: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0:0 is pre-release hardwareRouter#*Sep 29 11:06:24.624: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/0*Sep 29 11:06:25.379: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/1Router#*Sep 29 11:06:26.306: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/3Router#*Sep 29 11:06:33.776: %SPA_OIR-6-ONLINECARD: SPA (SPA-1XOC12-POS) online in subslot 0/0Router#*Sep 29 11:06:33.934: %LINK-3-UPDOWN: SIP0/0: Interface EOBC0/1, changed state to upRouter#Router#*Sep 29 11:06:37.496: %LINK-3-UPDOWN: SIP0/1: Interface EOBC0/1, changed state to upRouter#Router#Router#*Sep 29 11:06:43.820: %SPA_OIR-6-ONLINECARD: SPA (SPA-2XOC3-POS) online in subslot 0/1Router#*Sep 29 11:06:42.046: %LINK-3-UPDOWN: SIP0/3: Interface EOBC0/1, changed state to upRouter#*Sep 29 11:06:48.410: %SPA_OIR-6-ONLINECARD: SPA (SPA-5X1GE-V2) online in subslot 0/3Router#Router#Router# issu commitversion --- Starting installation changes ---Cancelling rollback timerFinished installation changes


Router#Router# issu loadversion rp 0 file bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 1 force--- Starting file path checking ---Finished file path checking





Determining whether installation is validSoftware sets are identified as compatible


OL-16506-08


Checking IPC compatibility with running softwareChecking candidate package set infrastructure compatibilityChecking infrastructure compatibility with running softwareChecking package specific compatibilityFinished compatibility testing







Router#issu loadversion rp 0 file bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.pkg force --- Starting file path checking ---Finished file path checking




OL-16506-08













*Sep 25 18:22:56.525: %ASR1000_OIR-6-OFFLINECARD: Card (fp) offline in slot F0*Sep 25 18:22:58.588: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is pre-release hardware Generating software version information Notifying running software of updates Unblocking peer synchronization of operating information


OL-16506-08


Unmounting old packagesCleaning temporary installation files Finished update running software SUCCESS: Finished installing software.

*Sep 25 18:23:35.356: %DYNCMD-7-CMDSET_UNLOADED: The Dynamic Command set from the Shell Manager has been unloaded*Sep 25 18:23:35.846: %DYNCMD-7-CMDSET_LOADED: The Dynamic Command set has been loaded from the Shell ManagerRouter#*Sep 25 18:23:45.207: %ASR1000_OIR-6-ONLINECARD: Card (fp) online in slot F0Router#*Sep 25 18:23:45.206: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is pre-release hardwareRouter#*Sep 25 18:23:55.309: %CPPHA-7-SYSREADY: F0: cpp_ha: CPP client process FMAN-FP (5 of 5) ready.*Sep 25 18:23:55.698: %CPPHA-7-START: F0: cpp_ha: CPP 0 preparing image /usr/cpp/bin/cpp-mcplo-ucode*Sep 25 18:23:55.931: %CPPHA-7-START: F0: cpp_ha: CPP 0 startup init image /usr/cpp/bin/cpp-mcplo-ucodeRouter#*Sep 25 18:24:00.837: %CPPHA-7-START: F0: cpp_ha: CPP 0 running init image /usr/cpp/bin/cpp-mcplo-ucode*Sep 25 18:24:01.077: %CPPHA-7-READY: F0: cpp_ha: CPP 0 loading and initialization completeRouter#*Sep 25 18:24:01.077: %CPPHA-6-SYSINIT: F0: cpp_ha: CPP HA system configuration start.Router#*Sep 25 18:24:02.403: %IOSXE-6-PLATFORM: F0: cpp_cp: Process CPP_PFILTER_EA_EVENT__API_CALL__REGISTER*Sep 25 18:24:02.597: %CPPHA-6-SYSINIT: F0: cpp_ha: CPP HA system enabled.*Sep 25 18:24:02.598: %CPPHA-6-SYSINIT: F0: cpp_ha: CPP HA system initialization complete.



Router# issu loadversion rp 0 file bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg--- Starting file path checking ---Finished file path checking

--- Starting image file verification ---Checking image file namesVerifying image file locationsLocating image files and validating name syntaxInspecting image file types WARNING: In-service installation of RP Base package WARNING: requires software reboot of target RP WARNING: Automatically setting the on-reboot flagProcessing image file constraintsCreating candidate provisioning fileFinished image file verification



OL-16506-08






Router# show version provisioned Package: Provisioning File, version: n/a, status: active File: bootflash:packages.conf, on: RP0 Built: n/a, by: n/a File SHA1 checksum: aca136bd8bcb99f87e6aa7a0ce2a92a3b5a5a200



Package: rpcontrol, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP0/0 --More-- Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5



OL-16506-08



Package: rpios-adventerprisek9, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active File: bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP0/1 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202 --More-- Package: rpbase, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP1 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: 32b3fceaf59e3acd7cf9937ef33a822d6b359887

Package: rpaccess, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive File: bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP1 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: 7c8dfdf9b2e3602b0c6c531a88dd93c8d2d180c6


Package: rpios-adventerprisek9, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive --More-- File: bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg, on: RP1/0 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202




OL-16506-08


Package: rpios-adventerprisek9, version: unknown, status: active File: unknown, on: ESP0 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: unknown --More-- Package: rpios-adventerprisek9, version: unknown, status: inactive File: unknown, on: ESP1 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: unknown




Package: rpios-adventerprisek9, version: unknown, status: inactive File: unknown, on: SIP0/2 --More-- Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: unknown





--More-- Package: rpios-adventerprisek9, version: unknown, status: inactive File: unknown, on: SIP1/2 Built: 2008-09-24_03.52, by: mcpre File SHA1 checksum: unknown




OL-16506-08



Package: rpios-adventerprisek9, version: unknown, status: inactive File: unknown, on: SIP2/1 Built: 2008-09-24_03.52, by: mcpre --More-- File SHA1 checksum: unknown



Router# reload<some output removed for brevity>

Router# request platform software package clean Cleaning up unnecessary package filesNo path specified, will use booted path bootflash:packages.confCleaning bootflash: Scanning boot directory for packages ... done. Preparing packages list to delete ... asr1000rp1-espbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-sipbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-sipspa.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. packages.conf File is in use, will not delete. done. Files that will be deleted: asr1000-rommon.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000-rommon.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg asr1000rp1-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.bin asr1000rp1-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.bin asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.conf


OL-16506-08


asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.conf asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg packages.conf.00- packages.conf.01- packages.conf.02- packages.conf.03- packages.conf.04- packages.conf.05-

Do you want to proceed? [confirm]y Deleting file bootflash:asr1000-rommon.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000-rommon.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.bin ... done. Deleting file bootflash:asr1000rp1-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.bin ... done. Deleting file bootflash:asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.conf ... done. Deleting file bootflash:asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.conf ... done. Deleting file bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:packages.conf.00- ... done. Deleting file bootflash:packages.conf.01- ... done. Deleting file bootflash:packages.conf.02- ... done. Deleting file bootflash:packages.conf.03- ... done.


OL-16506-08


Deleting file bootflash:packages.conf.04- ... done. Deleting file bootflash:packages.conf.05- ... done.SUCCESS: Files deleted.

Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router (request platform command set)

This section provides instructions on using ISSU to upgrade a Cisco ASR 1002 or 1004 Router running sub-packages using the request platform command set.

These instructions assume two IOS processes are active on the RP and that the router is already running using sub-packages. For information on checking and configuring two IOS processes on the same RP, see the “Configuring RPR or SSO on a Cisco ASR 1002 or Cisco ASR 1004 Router” section on page 4-72.

SUMMARY STEPS

1. show version



show platform


2. redundancy

mode sso












8. request platform software package install rp 0 file file-system:asr1000rp1-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force


10. show platform

11. request platform software package install rp 0 file file-system:asr1000rp1-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force

12. request platform software package install rp 0 file file-system:asr1000rp1-{sipbase,sipspa}*version*.pkg slot SIP-slot-number



OL-16506-08


13. request platform software package install rp 0 file file-system:asr1000rp1-esp*version*.pkg force

14. request platform software package install rp 0 file file-system:asr1000rp*version*.pkg

15. show version provisioned

Step 16 and later does not have to be performed immediately, and should be done at a convenient time.

16. reload



OL-16506-08


DETAILED STEPS


Step 1 show version



show platform






Router# show redundancy-states






Step 2 redundancy

mode sso

ExampleRouter(config)# redundancyRouter(config-red)# mode sso

Configure SSO if it is not already configured.

Note Save the configuration after making this configuration step.

Although SSO is the better redundancy option, RPR can also be used to establish a second IOS process on the RP to complete this process.











OL-16506-08











OL-16506-08

















Step 8 request platform software package install rp 0 file file-system:asr1000rp1-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force

ExampleRouter# request platform software package install rp 0 file bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}*02.02.01.122-33.XNB1*.pkg bay 1 force

Upgrade the RPAccess, RPIOS, and RPControl sub-packages in the standby bay.



OL-16506-08




Force a switchover from the active IOS process to the standby IOS process.

Note Your connection to the router often drops and is expected behavior at this point of the procedure in many scenarios. If this step drops your connection to the router, wait a few minutes before reconnecting to the router and then continue to Step 10.

Step 10 (Optional) show platform

ExampleRouter# show platform

(Optional) Monitor system state to ensure both IOS processes are active.

Step 11 request platform software package install rp 0 file file-system:asr1000rp1-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force

ExampleRouter# request platform software package install rp 0 file bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}*02.02.01.122-33.XNB1*.pkg bay 0 force

Upgrade the RPAccess, RPIOS, and RPControl sub-packages in the standby bay, which in this context is the opposite bay used in Step 8.

Note The pattern options used in this CLI (rpaccess, rpios, and rpcontrol) were introduced in Cisco IOS XE Release 2.1.2 and are not available in previous Cisco IOS XE Releases. See the “ISSU Upgrade Procedures (Pre Cisco IOS XE Release 2.1.2)” section on page 4-123 for pre-Cisco IOS XE Release 2.1.2 ISSU upgrade procedures.

Step 12 request platform software package install rp 0 file file-system:asr1000rp1-{sipbase,sipspa}*version*.pkg slot SIP-slot-number force


ExampleRouter# request platform software package install rp 0 file bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 0 force

Router# request platform software package install rp 0 file bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 1 force

Router# request platform software package install rp 0 file bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 2 force







OL-16506-08


Examples





cisco ASR1004 (RP1) processor with 752142K/6147K bytes of memory.5 Gigabit Ethernet interfaces2 Serial interfaces32768K bytes of non-volatile configuration memory.4194304K bytes of physical memory.937983K bytes of eUSB flash at bootflash:.39004543K bytes of SATA hard disk at bootflash:.253424K bytes of USB flash at usb0:.


Router# show version installedPackage: Provisioning File, version: n/a, status: active File: bootflash:packages.conf, on: RP0 Built: n/a, by: n/a

Step 13 request platform software package install rp 0 file file-system:asr1000rp1-esp*version*.pkg force

ExampleRouter# request platform software package install rp 0 file bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.pkg force

Upgrade the ESP Base sub-package.

Step 14 request platform software package install rp 0 file file-system:asr1000rp*version*.pkg

ExampleRouter# request platform software package install rp 0 file bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg

Upgrade all sub-packages, including the RPBase sub-package, which is the last sub-package that needs to be upgraded.


Step 15 show version installed

ExampleRouter# show version installed

(Optional) Verify that the sub-packages are properly installed.

Step 16 reload

ExampleRouter# reload

Reload the RP.

Tip The router will continue normal operation even without a reload, so you can reload the router during scheduled maintenance or a slower traffic period.

Step 17 request platform software package clean (Optional) Removes the unused sub-packages from the router.



OL-16506-08


File SHA1 checksum: 9172d30751d79fc1afb7b405eca244bbf9f8f2f2

Package: rpbase, version: 02.01.00.122-33.XNA, status: active File: bootflash:asr1000rp1-rpbase.02.01.00.122-33.XNA.pkg, on: RP0 Built: 2008-05-01_01.48, by: mcpre File SHA1 checksum: c09fe08ff908c8ce0b789d8acc774fe43dacf5e3

Package: rpaccess, version: 02.01.01.122-33.XNA, status: active File: bootflash:asr1000rp1-rpaccess.02.01.01.122-33.XNA.pkg, on: RP0 Built: 2008-07-08_16.01, by: mcpre File SHA1 checksum: c1afc591c9cd198409820226c4f23d2647d0d138<output removed for brevity>

Router# show redundancy states my state = 13 -ACTIVE peer state = 4 -STANDBY COLD Mode = Duplex Unit ID = 48

Redundancy Mode (Operational) = ssoRedundancy Mode (Configured) = ssoRedundancy State = sso Maintenance Mode = Disabled Manual Swact = disabled (peer unit not yet in terminal standby state) Communications = Up



Slot Type State Insert time (ago) --------- ------------------- --------------------- ----------------- 0 ASR1000-SIP10 ok 00:04:43 0/0 SPA-1XOC12-POS ok 00:03:25 0/1 SPA-2XOC3-POS ok 00:03:24 0/3 SPA-5X1GE-V2 ok 00:03:20 R0 ASR1000-RP1 ok 00:04:43 R0/0 ok, active 00:04:43 R0/1 ok, standby 00:02:55 F0 ASR1000-ESP10 ok, active 00:04:43 P0 ASR1004-PWR-AC ok 00:03:53 P1 ASR1004-FAN ok 00:03:53



Router# copy tftp: usb0:221subs Address or name of remote host []? 172.17.16.81Source filename []? /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.binDestination filename [asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin]? Accessing tftp://172.17.16.81//auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin...


OL-16506-08


Loading /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin from 172.17.16.81 (via GigabitEthernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 209227980 bytes]






Router# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg bootflash:Destination filename [asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC51904716 bytes copied in 5.478 secs (9475122 bytes/sec)

Router# copy usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg bootflash:Destination filename [asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg]?


OL-16506-08


Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC20533452 bytes copied in 2.346 secs (8752537 bytes/sec)





Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg bootflash:Destination filename [asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC26366156 bytes copied in 2.857 secs (9228616 bytes/sec)


OL-16506-08


Router# request platform software package install rp 0 file bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}*02.02.01.122-33.XNB1*.pkg bay 1 force--- Starting file path checking ---Finished file path checking












--- Starting update running software ---Blocking peer synchronization of operating information


OL-16506-08


Creating the command set placeholder directory Finding latest command set Finding latest command shortlist lookup file Finding latest command shortlist file Assembling CLI output libraries Assembling CLI input libraries Applying interim IPC and database definitions Replacing running software Replacing CLI software Restarting software

*Sep 25 11:23:27.008: %ASR1000_INFRA-6-BIPC_READ_ERR: R0/0: ppc_linux_iosd-image: connection read error from iman bipc, rc 32, bring down IPC Restarting IOS PID: 19252, in slot/bay 0/1

*Sep 25 11:23:41.837: %PMAN-3-PROCHOLDDOWN: R0/0: pman.sh: The process ppc_linux_iosd-image has been helddown (rc 137)*Sep 25 11:23:41.920: %PMAN-0-PROCFAILCRIT: R0/0: pvp.sh: A critical process ppc_linux_iosd_image has failed (rc 137)*Sep 25 11:23:41.962: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_NOT_PRESENT)*Sep 25 11:23:41.962: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)*Sep 25 11:23:41.962: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_REDUNDANCY_STATE_CHANGE)FIXME: kill/restart security package: 0 1 rp_security1 1 rp_security Applying final IPC and database definitions Generating software version information Notifying running software of updates Unblocking peer synchronization of operating informationUnmounting old packagesCleaning temporary installation files Finished update running software SUCCESS: Finished installing software.

Router#*Sep 25 11:24:35.148: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_FOUND(4))


Router#*Sep 25 11:24:36.067: %REDUNDANCY-3-IPC: IOS versions do not match. Router#*Sep 25 11:26:48.281: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeededRouter#*Sep 25 11:26:48.283: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)

Router# redundancy force-switchover Proceed with switchover to standby RP? [confirm]

%ASR1000_INFRA-6-CONSOLE_ACTIVE: R0/1 console active. Press RETURN to get started!

*Sep 25 11:31:33.401: %NETCLK-5-NETCLK_MODE_CHANGE: Network clock source not available. The network clock has changed to freerun

*Sep 25 11:31:33.438: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_NOT_PRESENT)*Sep 25 11:31:33.438: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_DOWN)*Sep 25 11:31:33.438: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_REDUNDANCY_STATE_CHANGE)*Sep 25 11:31:33.442: %PLATFORM-6-HASTATUS: RP switchover, sent message became active. IOS is ready to switch to primary after


OL-16506-08


Manual Swact = enabled

*Sep 25 11:31:33.061: %SYS-5-SWITCHOVER: Switchover requested by Exec. Reason: redundancy force-switchover. chassis confirmation*Sep 25 11:31:33.446: %CMANRP-6-CMHASTATUS: RP switchover, received chassis event became active*Sep 25 11:31:33.692: %PLATFORM-6-HASTATUS_DETAIL: RP switchover, received chassis event became active. Switch to primary (count 1)*Sep 25 11:31:35.683: %ACE-3-TRANSERR: ASR1000-ESP(14): IKEA trans 0x3; opcode 0x25; param 0xA; error 0x4; retry cnt 0*Sep 25 11:31:35.683: %ACE-3-TRANSERR: ASR1000-ESP(14): IKEA trans 0x4; opcode 0x25; param 0xB; error 0x4; retry cnt 0*Sep 25 11:31:35.684: %ACE-3-TRANSERR: ASR1000-ESP(14): IKEA trans 0x5; opcode 0x25; param 0xC; error 0x4; retry cnt 0*Sep 25 11:31:35.802: %LINK-3-UPDOWN: Interface Null0, changed state to up*Sep 25 11:31:35.803: %LINK-3-UPDOWN: Interface Loopback0, changed state to up*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface POS0/0/0, changed state to administratively down*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface POS0/1/0, changed state to administratively down*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface POS0/1/1, changed state to administratively down*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface GigabitEthernet0/3/0, changed state to administratively down*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface GigabitEthernet0/3/1, changed state to administratively down*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface GigabitEthernet0/3/2, changed state to administratively down*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface GigabitEthernet0/3/3, changed state to administratively down*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface GigabitEthernet0/3/4, changed state to administratively down*Sep 25 11:31:36.802: %LINEPROTO-5-UPDOWN: Line protocol on Interface Null0, changed state to up*Sep 25 11:31:36.802: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up*Sep 25 11:32:21.530: %REDUNDANCY-3-IPC: IOS versions do not match. *Sep 25 11:32:21.615: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_FOUND(4))


*Sep 25 11:34:05.450: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded*Sep 25 11:34:05.453: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)


Slot Type State Insert time (ago) --------- ------------------- --------------------- ----------------- 0 ASR1000-SIP10 ok 00:31:12 0/0 SPA-1XOC12-POS ok 00:11:35 0/1 SPA-2XOC3-POS ok 00:11:35 0/3 SPA-5X1GE-V2 ok 00:11:35 R0 ASR1000-RP1 ok 00:31:12 R0/0 ok, standby 00:05:38 R0/1 ok, active 00:13:36 F0 ASR1000-ESP10 ok, active 00:31:12 P0 ASR1004-PWR-AC ok 00:30:22 P1 ASR1004-FAN ok 00:30:22

Slot CPLD Version Firmware Version


OL-16506-08


--------- ------------------- --------------------------------------- 0 07091401 12.2(33r)XN1 R0 07062111 12.2(33r)XN2 F0 07091401 12.2(33r)XN1

Router# request platform software package install rp 0 file bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}*02.02.01.122-33.XNB1*.pkg bay 0 force--- Starting file path checking ---Finished file path checking







--- Starting commit of software changes ---Updating provisioning rollback filesCreating pending provisioning fileCommitting provisioning file

*Sep 25 11:39:35.632: %ACE-3-INITFAIL: ASR1000-ESP(14): initialization failed (timed out)Finished commit of software changes


--- Starting update running software ---Blocking peer synchronization of operating informationCreating the command set placeholder directory Finding latest command set Finding latest command shortlist lookup file


OL-16506-08


Finding latest command shortlist file Assembling CLI output libraries Assembling CLI input libraries Applying interim IPC and database definitions Replacing running software Replacing CLI software Restarting software

*Sep 25 11:40:31.859: %IOSXE-4-PLATFORM: R0/0: kernel: scooby: Scooby: FD close Restarting IOS PID: 21974, in slot/bay 0/0FIXME: kill/restart security package: 0 0 rp_security1 0 rp_security Applying final IPC and database definitions

*Sep 25 11:40:59.590: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_NOT_PRESENT)*Sep 25 11:40:59.591: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)*Sep 25 11:40:59.591: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_REDUNDANCY_STATE_CHANGE)*Sep 25 11:41:02.177: %DYNCMD-7-CMDSET_UNLOADED: The Dynamic Command set from the Shell Manager has been unloaded*Sep 25 11:41:02.719: %DYNCMD-7-CMDSET_LOADED: The Dynamic Command set has been loaded from the Shell Manager*Sep 25 11:41:05.397: %RF-5-RF_RELOAD: Peer reload. Reason: EHSA standby down Generating software version information Notifying running software of updates Unblocking peer synchronization of operating informationUnmounting old packagesCleaning temporary installation files Finished update running software SUCCESS: Finished installing software.

Router#*Sep 25 11:41:50.918: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0:0 is pre-release hardware*Sep 25 11:41:50.937: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_FOUND(4))


Router#

Router# request platform software package install rp 0 file bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 0 force--- Starting file path checking ---Finished file path checking


--- Starting candidate package set construction ---Verifying existing software setProcessing candidate provisioning fileConstructing working set for candidate package setConstructing working set for running package setChecking command output


OL-16506-08


Constructing merge of running and candidate packagesFinished candidate package set construction











*Sep 29 10:11:16.631: %ASR1000_OIR-6-OFFLINECARD: Card (cc) offline in slot 0*Sep 29 10:11:16.632: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/0, interfaces disabled*Sep 29 10:11:16.632: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/1, interfaces disabled*Sep 29 10:11:16.632: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/3, interfaces disabled


OL-16506-08


*Sep 29 10:11:24.575: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0:0 is pre-release hardware Generating software version information Notifying running software of updates Unblocking peer synchronization of operating informationUnmounting old packagesCleaning temporary installation files Finished update running software SUCCESS: Finished installing software.

Router#*Sep 29 10:12:00.274: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 0Router#*Sep 29 10:12:00.271: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0:0 is pre-release hardwareRouter#*Sep 29 10:12:01.833: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/0*Sep 29 10:12:02.579: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/1Router#*Sep 29 10:12:03.460: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/3Router#*Sep 29 10:12:10.405: %LINK-3-UPDOWN: SIP0/0: Interface EOBC0/1, changed state to upRouter#*Sep 29 10:12:16.944: %SPA_OIR-6-ONLINECARD: SPA (SPA-1XOC12-POS) online in subslot 0/0Router#*Sep 29 10:12:15.024: %LINK-3-UPDOWN: SIP0/1: Interface EOBC0/1, changed state to upRouter#*Sep 29 10:12:20.938: %SPA_OIR-6-ONLINECARD: SPA (SPA-2XOC3-POS) online in subslot 0/1Router#*Sep 29 10:12:17.086: %LINK-3-UPDOWN: SIP0/3: Interface EOBC0/1, changed state to upRouter#*Sep 29 10:12:23.640: %SPA_OIR-6-ONLINECARD: SPA (SPA-5X1GE-V2) online in subslot 0/3Router#Router#Router# request platform software package install rp 0 file bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 1 force--- Starting file path checking ---Finished file path checking






OL-16506-08







Router# request platform software package install rp 0 file bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.pkg force--- Starting file path checking ---Finished file path checking


--- Starting candidate package set construction ---Verifying existing software setProcessing candidate provisioning fileConstructing working set for candidate package setConstructing working set for running package setChecking command outputConstructing merge of running and candidate packages


OL-16506-08


Finished candidate package set construction











*Sep 25 12:43:27.892: %ASR1000_OIR-6-OFFLINECARD: Card (fp) offline in slot F0*Sep 25 12:43:29.992: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is pre-release hardware Generating software version information Notifying running software of updates Unblocking peer synchronization of operating informationUnmounting old packagesCleaning temporary installation files Finished update running software


OL-16506-08



Router#*Sep 25 12:44:11.960: %ASR1000_OIR-6-ONLINECARD: Card (fp) online in slot F0Router#*Sep 25 12:44:11.957: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is pre-release hardwareRouter#*Sep 25 12:44:21.256: %CPPHA-7-SYSREADY: F0: cpp_ha: CPP client process FMAN-FP (5 of 5) ready.*Sep 25 12:44:21.798: %CPPHA-7-START: F0: cpp_ha: CPP 0 preparing image /usr/cpp/bin/cpp-mcplo-ucode*Sep 25 12:44:21.909: %CPPHA-7-START: F0: cpp_ha: CPP 0 startup init image /usr/cpp/bin/cpp-mcplo-ucodeRouter#*Sep 25 12:44:26.763: %CPPHA-7-START: F0: cpp_ha: CPP 0 running init image /usr/cpp/bin/cpp-mcplo-ucode*Sep 25 12:44:27.004: %CPPHA-7-READY: F0: cpp_ha: CPP 0 loading and initialization completeRouter#*Sep 25 12:44:27.004: %CPPHA-6-SYSINIT: F0: cpp_ha: CPP HA system configuration start.Router#*Sep 25 12:44:28.321: %IOSXE-6-PLATFORM: F0: cpp_cp: Process CPP_PFILTER_EA_EVENT__API_CALL__REGISTER*Sep 25 12:44:28.516: %CPPHA-6-SYSINIT: F0: cpp_ha: CPP HA system enabled.*Sep 25 12:44:28.517: %CPPHA-6-SYSINIT: F0: cpp_ha: CPP HA system initialization complete.Router#

Router# request platform software package install rp 0 file bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg--- Starting file path checking ---Finished file path checking

--- Starting image file verification ---Checking image file namesVerifying image file locationsLocating image files and validating name syntaxInspecting image file types WARNING: In-service installation of RP Base package WARNING: requires software reboot of target RP WARNING: Automatically setting the on-reboot flagProcessing image file constraintsCreating candidate provisioning fileFinished image file verification


--- Starting compatibility testing ---Determining whether candidate package set is compatibleDetermining whether installation is validDetermining whether installation is valid ... skippedChecking IPC compatibility for candidate softwareChecking candidate package set infrastructure compatibilityChecking infrastructure compatibility with running softwareChecking infrastructure compatibility with running software ... skippedChecking package specific compatibility


OL-16506-08


Finished compatibility testing



Router# reloadProceed with reload? [confirm]y

Router# request platform software package clean Cleaning up unnecessary package filesNo path specified, will use booted path bootflash:packages.confCleaning bootflash: Scanning boot directory for packages ... done. Preparing packages list to delete ... asr1000rp1-espbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-sipbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. asr1000rp1-sipspa.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg File is in use, will not delete. packages.conf File is in use, will not delete. done. Files that will be deleted: asr1000-rommon.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000-rommon.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg asr1000rp1-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.bin asr1000rp1-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.bin asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.conf asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.conf asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg


OL-16506-08


packages.conf.00- packages.conf.01- packages.conf.02- packages.conf.03- packages.conf.04- packages.conf.05-

Do you want to proceed? [confirm]y Deleting file bootflash:asr1000-rommon.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000-rommon.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.bin ... done. Deleting file bootflash:asr1000rp1-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.bin ... done. Deleting file bootflash:asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.conf ... done. Deleting file bootflash:asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.conf ... done. Deleting file bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ... done. Deleting file bootflash:packages.conf.00- ... done. Deleting file bootflash:packages.conf.01- ... done. Deleting file bootflash:packages.conf.02- ... done. Deleting file bootflash:packages.conf.03- ... done. Deleting file bootflash:packages.conf.04- ... done. Deleting file bootflash:packages.conf.05- ... done.SUCCESS: Files deleted.


OL-16506-08

Chapter 4 In Service Software Upgrades (ISSU) ISSU Upgrade Procedures (Pre Cisco IOS XE Release 2.1.2)

ISSU Upgrade Procedures (Pre Cisco IOS XE Release 2.1.2)These instructions should be followed only if you are upgrading using ISSU to a pre-Cisco IOS XE 2.1.2 release. If you are using Cisco IOS XE Release 2.2.1 or later, follow the earlier instructions in this chapter to perform your ISSU upgrade.

This section contains the following topics:

• Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration (Pre Cisco IOS XE 2.1.2), page 4-123

• Using ISSU to Perform a Consolidated Package Upgrade on a Single Route Processor Configuration (Pre Cisco IOS XE 2.1.2), page 4-123

• Using ISSU to Upgrade Sub-Packages (Pre Cisco IOS XE Release 2.1.2), page 4-123

Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration (Pre Cisco IOS XE 2.1.2)

This procedure is identical to the procedure used to upgrade post-Cisco IOS XE 2.2 images using ISSU.

See the “Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration” section on page 4-6 for instructions on performing this process.

Using ISSU to Perform a Consolidated Package Upgrade on a Single Route Processor Configuration (Pre Cisco IOS XE 2.1.2)

This procedure is not supported until Cisco IOS XE Release 2.1.2.

Using ISSU to Upgrade Sub-Packages (Pre Cisco IOS XE Release 2.1.2)This procedure will work on single RPs configured to run two IOS processes or on routers configured with dual RPs.

Versions of Cisco IOS XE Release 2.1 prior to Cisco IOS XE Release 2.1.2 and versions of Cisco IOS XE Release 2.2 prior to Cisco IOS XE Release 2.2.1 and installations not booted from the RPBase sub-package on Cisco IOS XE Release 2.2.1 or 2.1.2 require a different ISSU upgrade procedure.

Step 1 Copy all sub-packages OTHER THAN THE RPBASE sub-package into the same directory.

Step 2 Install the RP sub-packages from the directory simultaneously by using a wildcard statement to capture all of the RP sub-packages. This command should capture the RPControl, RPAccess, and RPIOS sub-packages without capturing the RPBase sub-package and should be done using the standby bay.

Use the asr1000rp1-rp*version.pkg syntax instead of using the {pattern} syntax to complete this upgrade.

Examplerequest platform software package install rp 1 file stby-bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg bay 1 force


OL-16506-08

Chapter 4 In Service Software Upgrades (ISSU) ISSU Upgrade Procedures (Pre Cisco IOS XE Release 2.1.2)

Step 3 Wait for the system to reach SSO ready state. The show platform command can be used to monitor whether both IOS instances are active, and a system message will indicate SSO state has been reached.

Step 4 Use the redundancy force-switchover command to trigger an IOS switchover.

Step 5 Wait for the system to reach SSO ready state. Like in step 3, the state can be monitored by checking system messages or by entering the show platform command.

Step 6 Install the RP sub-packages from the directory simultaneously by using a wildcard statement to capture all of the RP sub-packages. This command should capture the RPControl, RPAccess, and RPIOS sub-packages without capturing the RPBase sub-package and should be done using the standby bay.

Use the “asr1000rp1-rp*version.pkg syntax instead of using the {pattern} syntax to complete this upgrade.

Example

request platform software package install rp 0 file stby-bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg bay 0 force

Step 7 Install the SIPBASE and SIPSPA packages on each SIP.

ExampleRouter# request platform software package install rp 0 file bootflash:asr1000rp1-sip*02.02.01.122-33.XNB1*.pkg slot 0 force

Router# request platform software package install rp 0 file bootflash:asr1000rp1-sip*02.02.01.122-33.XNB1*.pkg slot 1 force

Router# request platform software package install rp 0 file bootflash:asr1000rp1-sip*02.02.01.122-33.XNB1*.pkg slot 2 force

Step 8 Install the ESPBASE package on the ESP.

ExampleRouter# request platform software package install rp 0 file bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.pkg

Step 9 Copy the RPBase sub-package into the directory, then upgrade all of the RP sub-packages simultaneously. This step will upgrade the RPBase sub-package, which is the last remaining sub-package that requires an upgrade.

Examplerequest platform software package install rp 1 file bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg force

Step 10 Enter show version provisioned to confirm that all of the software has been updated.

Step 11 Reload the router using the reload command when appropriate to complete the installation.

Caution Downgrades in versions that do not support the {pattern} syntax are problematic because an RPBASE package for the downgrade version will always be present if an upgrade was previously performed. Removing and restaging all packages will work in this case, but they effectively put the system into a state where if the RP reloads prior to the installation being completed, the RP may no longer be bootable.


OL-16506-08


C H A P T E R 5
High Availability Overview
Cisco High Availability (HA) enables network-wide protection by providing fast recovery from faults that may occur in any part of the network. With Cisco High Availability, network hardware and software work together and enable rapid recovery from disruptions to ensure fault transparency to users and network applications.

The unique hardware and software architecture of the Cisco ASR 1000 Series Routers is designed to maximize router uptime during any network event, and thereby provide maximum uptime and resilience within any network scenario.

This chapter covers the aspects of High Availability that are unique to the Cisco ASR 1000 Series Routers. It is not intended as a comprehensive guide to High Availability, nor is it intended to provide information on High Availability features that are available on other Cisco routers that are configured and implemented identically on the Cisco ASR 1000 Series Routers. The Cisco IOS feature documents and guides should be used in conjunction with this chapter to gather information about High Availability-related features that are available on multiple Cisco platforms and work identically on the Cisco ASR 1000 Series Routers.

This section discusses various aspects of High Availability on the Cisco ASR 1000 Series Routers and contains the following sections:

• Hardware Redundancy Overview on the Cisco ASR 1000 Series Routers, page 5-1

• Software Redundancy on the Cisco ASR 1000 Series Routers, page 5-3

• Route Processor Redundancy, page 5-4

• Stateful Switchover, page 5-4

• Bidirectional Forwarding Detection, page 5-5

Hardware Redundancy Overview on the Cisco ASR 1000 Series Routers

Some models of the Cisco ASR 1000 Series Routers offer hardware redundancy within the same Cisco ASR 1000 Series Router through the following methods:

• Allowing two Route Processors (RPs) in the same Cisco ASR 1000 Series Router

• Allowing two Enhanced Services Processors (ESPs) in the same Cisco ASR 1000 Series Router

No hardware redundancy is supported for the following hardware:

• SPA interface processors (SIPs)—A SIP must be reloaded, and traffic briefly interrupted, for a SIP upgrade to complete.


Chapter 5 High Availability Overview Hardware Redundancy Overview on the Cisco ASR 1000 Series Routers

• Shared port adapters (SPAs)—A SPA must be reloaded, which will briefly interrupt traffic to that SPA, for a SPA software sub-package update to complete.

Hardware redundancy on the Cisco ASR 1000 Series Routers gives users the following benefits:

• A failover option—If a processor fails, the standby processor immediately becomes the active processor with little or no delay. The failover happens completely within the same router, so a second standby router is not needed.

• No downtime upgrades—Using features like ISSU, a software upgrade can be handled on the standby processor while the active processor continues normal operation.

Hardware redundancy is available on the Cisco ASR 1006 Router only at this time.

Table 5-1 provides a hardware redundancy overview.

Table 5-1 Hardware Redundancy Overview

Hardware

Support for Dual Hardware Configuration on Cisco ASR 1002 Router

Support for Dual Hardware Configuration on Cisco ASR 1004 Router

Support for Dual Hardware Configuration on Cisco ASR 1006 Router Failover Behavior

Enhanced Services Processor

No No Yes If an active ESP experiences a hardware or software event that makes it unable to forward traffic (such as a hardware failure, an OIR, or a manual switch) and a standby ESP is configured, the standby ESP becomes the active ESP with the possibility of a minor interruption (less than 200 ms).

Route Processor No No Yes If an active RP experiences an event that makes it unable to forward traffic (such as a hardware failure, a software failure, an OIR, or a manual switch) and a standby RP is configured, the standby RP immediately becomes the active RP.

SPA No No No No standby configurations are available for SPAs. If a SPA fails, that particular SPA is down and unable to forward traffic.

In the event of a SPA shutdown, all other SIPs and SPAs on the router continue to be fully operational.

SIP No No No No standby configurations are available for SIPs. If a SIP fails, all SPAs in that SIP are down and unable to forward traffic.

In the event of a SIP shutdown, all other SIPs and SPAs on the router continue to be fully operational.


OL-16506-08

Chapter 5 High Availability Overview Software Redundancy on the Cisco ASR 1000 Series Routers

Software Redundancy on the Cisco ASR 1000 Series RoutersThis section covers the following topics:

• Software Redundancy Overview, page 5-3

• Second IOS Process on a Cisco ASR 1002 or 1004 Router, page 5-3

• SSO-Aware Protocol and Applications, page 5-5

Software Redundancy OverviewOn the Cisco ASR 1000 Series Routers, IOS runs as one of many processes within the operating system. This is different than on traditional Cisco IOS, where all processes are run within Cisco IOS. See the “IOS as a Process” section on page 1-7 for more information regarding IOS as a process on the Cisco ASR 1000 Series Router.

This architecture allows for software redundancy opportunities that are not available on other platforms that run Cisco IOS software. Specifically, a standby IOS process can be available on the same Route Processor as the active IOS process. This standby IOS process can be switched to in the event of an IOS failure, and can also be used to upgrade sub-package software in some scenarios as the standby IOS process in an ISSU upgrade.

On the Cisco ASR 1006 Router, the second IOS process can run only on the standby Route Processor. Two IOS processes on the same Router Processor are not possible for any Cisco ASR 1000 Series Router that supports dual RP hardware redundancy configurations since the second Route Processor can support a standby IOS process. An overview of software redundancy is shown in Table 5-2.

Second IOS Process on a Cisco ASR 1002 or 1004 RouterFor Cisco ASR 1002 and 1004 routers, Route Processor Redundancy and Stateful Switchover can be used to switch between IOS processes. RPR and SSO need to be configured by the user, however, because a second IOS process is not available by default on Cisco ASR 1002 and 1004 routers.

Table 5-2 Software Redundancy Overview

Router

Support for Two IOS Processes on Same Route Processor

Support for a Second IOS Process on Standby Route Processor Explanation

Cisco ASR 1002 Router

Yes N/A The Cisco ASR 1002 Router only supports one RP, so dual IOS processes run on the lone RP.


Yes N/A The Cisco ASR 1004 Router only supports one RP, so dual IOS processes run on the lone RP.


No Yes The Cisco ASR 1006 Router supports a second Route Processor, so the second IOS process can only run on the standby Route Processor.


OL-16506-08

Chapter 5 High Availability Overview Route Processor Redundancy

Table 5-3 summarizes the software redundancy opportunities available with the second IOS process for the Cisco ASR 1002 and 1004 routers.

Table 5-3 Software Redundancy Options for Cisco ASR 1002 and 1004 Routers

ISSU cannot be used to upgrade consolidated packages on Cisco ASR 1002 or 1004 Routers, and only a few sub-packages can be upgraded individually using ISSU through the use of dual IOS processes on the same Route Processor. See the “Route Processor Redundancy” section on page 5-4 for more information on which sub-packages can be upgraded using ISSU in a dual RP setup.

Route Processor RedundancyRoute Processor Redundancy (RPR) allows you to configure a standby RP. When you configure RPR, the standby RP loads the Cisco IOS software on bootup and initializes itself in standby mode. In the event of a fatal error on the active RP, the system switches to the standby RP, which reinitializes itself as the active RP. In this event, the entire system is rebooted, so the switchover with RPR is slower than with other High Availability switchover features such as Nonstop Forwarding/Stateful Switchover (NSF/SSO).

On the Cisco ASR 1000 Series Router, RPR can also be used to enable a second IOS process on a single RP for a Cisco ASR 1002 or 1004 Router. See the “Second IOS Process on a Cisco ASR 1002 or 1004 Router” section on page 5-3 for additional information on the second IOS process.

For the Cisco ASR 1000 Series Routers, RPR introduces the following functionality:

• Startup configuration synchronization between the active and standby RP or IOS process. It is important to note, however, that changes in the running configuration are not synchronized using RPR.

• Warm Reload—The Warm Reload feature allows users to reload their routers without reading images from storage; that is, the router reboots by restoring the read-write data from a previously saved copy in the RAM and by starting execution without either copying the software from flash to RAM or self-decompression of the image.

It is important to note that in most cases, Stateful Swithover (SSO) requires less downtime for switchover and upgrades than RPR. RPR should only be used when there is a compelling reason to not use SSO.

It is important to note RPR is supported on the Cisco ASR 1000 Series Routers while RPR+ is not.

Stateful SwitchoverThe Stateful Switchover (SSO) feature takes advantage of processor redundancy by establishing one of the processors as the active processor while the other RP is designated as the standby processor, and then synchronizing critical state information between them. Following an initial synchronization between the two processors, SSO dynamically maintains RP state information between the dual processors.

RouterDefault HA Setting

Options on Router with 2 GB or DRAM

Options with 4 GB or DRAM

Cisco ASR 1002 Router None None None, RPR, SSO

Cisco ASR 1004 Router None None None, RPR, SSO


OL-16506-08

Chapter 5 High Availability Overview Bidirectional Forwarding Detection

Stateful Switchover is particularly useful in conjunction with Nonstop Forwarding. SSO allows the dual processors to maintain state at all times, and Nonstop Forwarding lets a switchover happen seamlessly when a switchover occurs.

On the Cisco ASR 1000 Series Router, SSO can also be used to enable a second IOS process on a single RP for a Cisco ASR 1002 or 1004 Router. See the “Second IOS Process on a Cisco ASR 1002 or 1004 Router” section on page 5-3 for additional information on the second IOS process.

It is important to note that in most cases, SSO requires less downtime for switchover and upgrades than RPR. RPR should only be used when there is a compelling reason to not use SSO.

For additional information on NSF/SSO, see the Cisco Nonstop Forwarding document.

SSO-Aware Protocol and ApplicationsSSO-supported line protocols and applications must be SSO-aware. A feature or protocol is SSO-aware if it maintains, either partially or completely, undisturbed operation through an RP switchover. State information for SSO-aware protocols and applications is synchronized from active to standby to achieve stateful switchover for those protocols and applications.

The dynamically created state of SSO-unaware protocols and applications is lost on switchover and must be reinitialized and restarted on switchover.

To see which protocols are SSO-aware on your router, enter the show redundancy comp-matrix command.

Bidirectional Forwarding DetectionBidirectional Forwarding Detection (BFD) is a detection protocol designed to provide fast forwarding path failure detection times for all media types, encapsulations, topologies, and routing protocols. In addition to fast forwarding path failure detection, BFD provides a consistent failure detection method for network administrators. Because the network administrator can use BFD to detect forwarding path failures at a uniform rate rather than the variable rates for different routing protocol hello mechanisms, network profiling and planning is easier, and reconvergence time is consistent and predictable.

For more information on BFD, see the Bidirectional Forwarding Detection document.

For the Cisco ASR 1000 Series Routers, BFD for IPv4 Static Routes and BFD for BGP are supported.


OL-16506-08

http://www.cisco.com/en/US/products/ps6017/products_feature_guide09186a00803fbe87.html

http://www.cisco.com/en/US/products/sw/iosswrel/ps1838/products_white_paper09186a00801ce6f9.shtml

Chapter 5 High Availability Overview Bidirectional Forwarding Detection


OL-16506-08


C H A P T E R 6
Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers
The Call Home feature provides e-mail-based and web-based notification of critical system events. A versatile range of message formats are available for optimal compatibility with pager services, standard e-mail, or XML-based automated parsing applications. Common uses of this feature may include direct paging of a network support engineer, e-mail notification to a Network Operations Center, XML delivery to a support website, and utilization of Cisco Smart Call Home services for direct case generation with the Cisco Systems Technical Assistance Center (TAC). This document describes how to configure the Call Home feature on Cisco ASR 1000 Series Aggregation Services Routers beginning with Cisco IOS XE Release 2.6.

Finding Feature InformationFor the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the “Feature Information for Call Home” section on page 6-54.

Use Cisco Feature Navigator to find information about platform support and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

ContentsThis document includes the following sections:

• Information About Call Home, page 6-2

• Prerequisites for Call Home, page 6-3

• How to Configure Call Home, page 6-4

• How To Configure Call Home to Support the Smart Call Home Service, page 6-26

• Displaying Call Home Configuration Information, page 6-31

• Default Settings, page 6-36

• Alert Group Trigger Events and Commands, page 6-37

• Message Contents, page 6-39

• Additional References, page 6-53



Chapter 6 Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers Information About Call Home

• Feature Information for Call Home, page 6-54

Information About Call HomeCall Home provides e-mail-based and web-based notification of critical system events. A versatile range of message formats are available for optimal compatibility with pager services, standard e-mail, or XML-based automated parsing applications. Common uses of this feature may include direct paging of a network support engineer, e-mail notification to a Network Operations Center, XML delivery to a support website, and utilization of Cisco Smart Call Home services for direct case generation with the Cisco Systems Technical Assistance Center (TAC).

The Call Home feature can deliver alert messages containing information on configuration, diagnostics, environmental conditions, inventory, and syslog events.

The Call Home feature can deliver alerts to multiple recipients, referred to as Call Home destination profiles, each with configurable message formats and content categories. A predefined destination profile (CiscoTAC-1) is provided, and you also can define your own destination profiles. The CiscoTAC-1 profile is used to send alerts to the backend server of the Smart Call Home service, which can be used to create service requests to the Cisco TAC (depending on the Smart Call Home service support in place for your device and the severity of the alert).

Flexible message delivery and format options make it easy to integrate specific support requirements.

This section contains the following subsections:

• Benefits of Using Call Home, page 6-2

• How to Obtain Smart Call Home Service, page 6-2

Benefits of Using Call HomeThe Call Home feature offers the following benefits:

• Multiple message-format options:

– Short Text—Suitable for pagers or printed reports.

– Plain Text—Full formatted message information suitable for human reading.

– XML—Matching readable format using Extensible Markup Language (XML) and Adaptive Markup Language (AML) document type definitions (DTDs). The XML format enables communication with the Cisco Smart Call Home server.

• Multiple concurrent message destinations.

• Multiple message categories, including configuration, diagnostics, environmental conditions, inventory, and syslog events.

• Filtering of messages by severity and pattern matching.

• Scheduling of periodic message sending.

How to Obtain Smart Call Home ServiceIf you have a service contract directly with Cisco Systems, you can register your Call Home devices for the Cisco Smart Call Home service. Smart Call Home provides fast resolution of system problems by analyzing Call Home messages sent from your devices and providing background information and


OL-16506-08

Chapter 6 Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers Prerequisites for Call Home

recommendations. For issues that can be identified as known, automatic Service Requests can be generated with the Cisco TAC. This depends on the Smart Call Home service support in place for your device and the severity of the alert.

Smart Call Home offers the following features:

• Analysis of Call Home messages from your device, and where supported, automatic Service Request generation routed to the appropriate TAC team, including detailed diagnostic information to speed problem resolution.

• Continuous device health monitoring.

• Analysis of Call Home messages from your device.

• Secure message transport directly from your device or through a downloadable Transport Gateway (TG) aggregation point. You can use a TG aggregation point in cases requiring support for multiple devices or in cases where security requirements mandate that your devices may not be connected directly to the Internet.

• Web-based access to Call Home messages and recommendations, inventory, and configuration information for all Call Home devices. Provides access to associated Field Notices, Security Advisories, and End-of-Life Information.

You need the following items to register:

• SMARTnet contract number for your router.

• Your e-mail address

• Your Cisco.com ID

For information about how to configure Call Home to work with the Smart Call Home service, see the “How To Configure Call Home to Support the Smart Call Home Service” section on page 6-26.

For detailed information on Smart Call Home, see the Smart Call Home page at:

http://www.cisco.com/en/US/products/ps7334/serv_home.html

Prerequisites for Call HomeHow you configure Call Home depends on how you intend to use the feature. Consider the following requirements before you configure Call Home:

• Obtain e-mail, phone, and street address information for the Call Home contact to be configured so that the receiver can determine the origin of messages received.

• Identify the name or IPv4 address of a primary Simple Mail Transfer Protocol (SMTP) server and any backup servers, if using e-mail message delivery.

• Configure a trustpoint certificate authority (CA) if using secure HTTP (HTTPS) message delivery. For example, this procedure is required if you are using the HTTPS server for Cisco Smart Call Home Service in the CiscoTAC-1 profile for Call Home.

• Verify IP connectivity from the router to the e-mail server(s) or the destination HTTP server.

• If Cisco Smart Call Home is used, verify an active service contract exists for the device being configured.


OL-16506-08

http://www.cisco.com/en/US/products/ps7334/serv_home.html

Chapter 6 Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers How to Configure Call Home

How to Configure Call HomeTo configure Call Home, complete the following tasks:

• Configuring the Management Interface VRF, page 6-4 (required)

• Configuring a Destination Profile, page 6-5 (required)

• Subscribing to Alert Groups, page 6-16 (required)

• Configuring Contact Information, page 6-19 (required)

• Configuring the Number of Call Home Messages Sent Per Minute, page 6-21 (optional)

• Enabling and Disabling Call Home, page 6-21 (required)

• Sending Call Home Communications Manually, page 6-22 (optional)

Configuring the Management Interface VRFThe Call Home feature on the Cisco ASR 1000 Series Routers requires use of the Gigabit Ethernet Management interface virtual routing and forwarding (VRF) instance. The Gigabit Ethernet Management interface is automatically part of its own VRF named “Mgmt-intf.”

To configure the Management interface VRF, complete the following steps:

SUMMARY STEPS

1. configure terminal

2. interface GigabitEthernet 0

3. vrf forwarding Mgmt-intf

4. ip address ip-address mask [secondary [vrf vrf-name]]

or

ipv6 address {X:X:X:X::X link-local | X:X:X:X::X/prefix [anycast | eui-64] | autoconfig [default]}

DETAILED STEPS


Step 1 configure terminal

Example:Router# configure terminal

Enters global configuration mode.

Step 2 interface GigabitEthernet 0

Example:Router(config)# interface GigabitEthernet0

(Required) Specifies the Gigabit Ethernet Management interface on the Cisco ASR 1000 Series Router.


OL-16506-08


What To Do Next

To find out more about the Gigabit Ethernet Management interface on the Cisco ASR 1000 Series Routers or perform additional related configuration tasks on the management interface, see the “Using the Management Ethernet Interface” chapter of Cisco ASR 1000 Series Aggregation Services Router Software Configuration Guide.

Configuring a Destination ProfileA destination profile contains the required delivery information for an alert notification. You can configure multiple destination profiles of one or more type.

You can create and define a new destination profile or copy and use another destination profile. If you define a new destination profile, you must assign a profile name.

Note The Call Home feature provides a predefined profile named CiscoTAC-1 that is inactive by default. The CiscoTAC-1 profile is intended for use with the Smart Call Home service, which requires certain additional configuration steps to enable the service with the Call Home feature. For more information about this profile, see the “Using the Predefined CiscoTAC-1 Destination Profile” section on page 6-15.

You can configure the following attributes for a destination profile:

• Profile name—A string that uniquely identifies each user-defined destination profile. The profile name is limited to 31 characters and is not case-sensitive. You cannot use all as a profile name.

• Transport method—The transport mechanism, either e-mail or HTTP (including HTTPS), for delivery of alerts.

– For user-defined destination profiles, e-mail is the default, and you can enable one or both transport mechanisms. If you disable both methods, e-mail is enabled.

– For the predefined Cisco TAC profile, you can enable either transport mechanism, but not both.

• Destination address—The actual address related to the transport method to which the alert should be sent.

Step 3 vrf forwarding Mgmt-intf

Example:Router(config-if)# vrf forwarding Mgmt-intf

(Required) Associates the Mgmt-intf VRF with the Gigabit Ethernet Management interface. This command is configured by default.

Step 4 ip address ip-address mask [secondary [vrf vrf-name]]

or


Example:Router(config-if)# ip address 10.10.10.10 0.0.0.0

(Required) Specifies the IPv4 or IPv6 addressing for the interface.



OL-16506-08

http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/chassis/Management_Ethernet.html

http://www.cisco.com/en/US/docs/routers/asr1000/configuration/guide/chassis/Management_Ethernet.html


• Message formatting—The message format used for sending the alert. The format options for a user-defined destination profile are long-text, short-text, or XML. The default is XML. For the predefined Cisco TAC profile, only XML is allowed. If you use the Cisco Smart Call Home service, the destination profile must use the XML message format.

• Message size—The maximum destination message size. The valid range is 50 to 3,145,728 bytes and the default is 3,145,728 bytes.

This section includes the following tasks:

• Configuring a Destination Profile to Send Email Messages, page 6-6

• Configuring a Destination Profile to Send HTTP Messages, page 6-10

• Working With Destination Profiles, page 6-13

Configuring a Destination Profile to Send Email Messages

To configure Call Home to send email messages, complete the following tasks:

• Configuring the Mail Server, page 6-6 (required)

• Associating the Management Interface VRF With Call Home, page 6-7 (required)

• Configuring a Destination Profile for Email, page 6-8 (required)

• Configuring Other Email Options, page 6-9 (optional)

Configuring the Mail Server

To use the e-mail message transport, you must configure at least one Simple Mail Transfer Protocol (SMTP) e-mail server address. You can specify up to four backup e-mail servers, for a maximum of five total mail-server definitions.

Consider the following guidelines when configuring the mail server:

• Backup e-mail servers can be defined by repeating the mail-server command using different priority numbers.

• The mail-server priority number parameter can be configured from 1 to 100. The server with the highest priority (lowest priority number) is tried first.

SUMMARY STEPS


2. call-home

3. mail-server {ipv4-address | name} priority number


OL-16506-08


DETAILED STEPS

Example

The following example shows the configuration of a primary mail server (named “smtp.example.com”) and secondary mail server at IP address 192.168.0.1:

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z.Router(config)# call-homeRouter(cfg-call-home)# mail-server smtp.example.com priority 1Router(cfg-call-home)# mail-server 192.168.0.1 priority 2Router(cfg-call-home)# exitRouter(config)#

Associating the Management Interface VRF With Call Home

The Call Home feature requires the managment interface VRF (Mgmt-intf) to provide e-mail messaging support. If you have not configured the management interface VRF, see the “Configuring the Management Interface VRF” section on page 6-4.

To associate the management interface VRF with Call Home, complete the following steps:

SUMMARY STEPS


2. call-home

3. vrf Mgmt-intf





Step 2 call-home

Example:Router(config)# call-home

Enters call home configuration mode.

Step 3 mail-server {ipv4-address | name} priority number

Example:Router(cfg-call-home)# mail-server stmp.example.com priority 1

Specifies an e-mail server and its relative priority among configured e-mail servers, where:

• ipv4-address—Specifies the IPv4 address of the mail server.

• name—Specifies the mail server’s fully qualified domain name (FQDN) of 64 characters or less.

• number—Assigns a number between 1 (highest priority) and 100 (lowest priority).


OL-16506-08


DETAILED STEPS

Configuring a Destination Profile for Email

To configure a destination profile for email transport, complete the following steps:

SUMMARY STEPS


2. call-home

3. profile name

4. destination transport-method email

5. destination address email email-address

6. destination preferred-msg-format {long-text | short-text | xml}

7. destination message-size bytes

8. active

9. exit

10. end

DETAILED STEPS





Step 2 call-home



Step 3 vrf Mgmt-intf

Example:Router(cfg-call-home)# vrf Mgmt-intf

(Required) Associates the Mgmt-intf VRF for the email transport method using Call Home.





Step 2 call-home




OL-16506-08


Configuring Other Email Options

For the email transport method, you can also configure the from and reply-to e-mail addresses by completing the following steps:

SUMMARY STEPS


2. call-home

Step 3 profile name

Example:Router(config-call-home)# profile profile1

Enters call home destination profile configuration mode for the specified destination profile name. If the specified destination profile does not exist, it is created.

Step 4 destination transport-method email

Example:Router(cfg-call-home-profile)# destination transport-method email

(Optional) Configures the message transport method for email. This is the default.

Step 5 destination address email email-address

Example:Router(cfg-call-home-profile)# destination address email [email protected]

(Required) Configures the destination e-mail address to which Call Home messages are sent.

Step 6 destination preferred-msg-format {long-text | short-text | xml}

Example:Router(cfg-call-home-profile)# destination preferred-msg-format xml

(Optional) Configures a preferred message format. The default is XML.

Step 7 destination message-size bytes

Example:Router(cfg-call-home-profile)# destination message-size 3145728

(Optional) Configures a maximum destination message size (from 50 to 3145728 bytes) for the destination profile. The default is 3145728 bytes.

Step 8 active

Example:Router(cfg-call-home-profile)# active

(Optional) Enables the destination profile. By default, a user-defined profile is enabled when it is created.

Step 9 exit

Example:Router(cfg-call-home-profile)# exit

Exits call home destination profile configuration mode and returns to call home configuration mode.

Step 10 end

Example:Router(cfg-call-home)# end

Returns to privileged EXEC mode.



OL-16506-08


3. sender from email-address

4. sender reply-to email-address

DETAILED STEPS

Configuring a Destination Profile to Send HTTP Messages

To configure Call Home to send HTTP (or HTTPS) messages, complete the following tasks:

• Configuring the HTTP Source Interface, page 6-10 (required)

• Configuring a Destination Profile for HTTP, page 6-11 (required)

• Configuring a Trustpoint Certificate Authority, page 6-12 (required for HTTPS)

Configuring the HTTP Source Interface

If you are using HTTP or HTTPS to send Call Home messages, then you must configure the VRF management interface as the HTTP client source interface.

SUMMARY STEPS


2. ip http client source-interface type number

3. end





Step 2 call-home



Step 3 sender from email-address

Example:Router(cfg-call-home)# sender from [email protected]

(Optional) Assigns the e-mail address that will appear in the from field in Call Home e-mail messages. If no address is specified, the contact e-mail address is used.

Step 4 sender reply-to email-address

Example:Router(cfg-call-home)# sender reply-to [email protected]

(Optional) Assigns the e-mail address that will appear in the reply-to field in Call Home e-mail messages.


OL-16506-08


DETAILED STEPS

Configuring a Destination Profile for HTTP

To configure a destination profile for http transport, complete the following steps:

SUMMARY STEPS


2. call-home

3. profile name

4. destination transport-method http

5. destination address http url

6. destination preferred-msg-format {long-text | short-text | xml}

7. destination message-size bytes

8. active

9. exit

10. end

DETAILED STEPS





Step 2 ip http client source-interface type number

Example:Router(config)# ip http client source-interface gigabitethernet 0

Configures the source interface for the HTTP client.

Note On the Cisco ASR 1000 Series Router, this interface should be the VRF management interface.

Step 3 end







Step 2 call-home




OL-16506-08


Configuring a Trustpoint Certificate Authority

If you are using the HTTP transport method and specifying an HTTPS destination URL, then you will also need to configure a trustpoint certificate authority (CA).

Step 3 profile name

Example:Router(config-call-home)# profile test

Enters call home destination profile configuration mode for the specified destination profile. If the specified destination profile does not exist, it is created.

Step 4 destination transport-method http

Example:Router(cfg-call-home-profile)# destination transport-method http

Enables the HTTP message transport method.

Step 5 destination address http url

Example:Router(cfg-call-home-profile)# destination address http https://example.url.com

Configures the destination URL to which Call Home messages are sent.

Note When entering a destination URL, include either http:// or https://, depending on whether the server is a secure server. If the destination is a secure server, you must also configure a trustpoint CA.

Step 6 destination preferred-msg-format {long-text | short-text | xml}

Example:Router(cfg-call-home-profile)# destination preferred-msg-format xml

(Optional) Configures a preferred message format. The default is XML.

Step 7 destination message-size bytes

Example:Router(cfg-call-home-profile)# destination message-size 3,145,728

(Optional) Configures a maximum destination message size for the destination profile.

Step 8 active


Enables the destination profile. By default, a profile is enabled when it is created.

Step 9 exit



Step 10 end





OL-16506-08


For more information about how to configure a trustpoint CA, see the “Declare and Authenticate a CA Trustpoint” section on page 6-28. That section describes how to configure a CA trustpoint for a secure Cisco server to use with the Smart Call Home service, but can be applied to other secure server configuration as needed by your site using the required certificate for your secure server.

Working With Destination Profiles

This section describes some of the tasks that you can complete with destination profiles:

• Activating and Deactivating a Destination Profile, page 6-13

• Copying a Destination Profile, page 6-14

• Renaming a Destination Profile, page 6-15

• Using the Predefined CiscoTAC-1 Destination Profile, page 6-15

Activating and Deactivating a Destination Profile

Except for the predefined CiscoTAC-1 profile, all Call Home destination profiles are automatically activated once you create them. If you do not want to use a profile right way, you can deactivate the profile. The CiscoTAC-1 profile is inactive by default and must be activated to be used.

To activate or deactivate a destination profile, complete the following steps:

SUMMARY STEPS


2. call-home

3. profile name

4. active

5. no active

6. end

DETAILED STEPS





Step 2 call-home



Step 3 profile name

Example:Router(config-call-home)# profile test

Enters call home destination profile configuration mode for the specified destination profile. If the specified destination profile does not exist, it is created.


OL-16506-08


Copying a Destination Profile

To create a new destination profile by copying an existing profile, complete the following steps:

SUMMARY STEPS


2. call-home

3. copy profile source-profile target-profile

DETAILED STEPS

Step 4 active


Enables the destination profile. By default, a new profile is enabled when it is created.

Step 5 no active

Example:Router(cfg-call-home-profile)# no active

Disables the destination profile.

Step 6 end


Exits call home destination profile configuration mode and returns to privileged EXEC mode.






Step 2 call-home



Step 3 copy profile source-profile target-profile

Example:Router(cfg-call-home)# copy profile profile1 profile2

Creates a new destination profile with the same configuration settings as the existing destination profile, where:

• source-profile—Specifies the existing name of the profile.

• target-profile—Specifies a name for the new copy of the profile.


OL-16506-08


Renaming a Destination Profile

To change the name of an existing profile, complete the following steps:

SUMMARY STEPS


2. call-home

3. rename profile source-profile target-profile

DETAILED STEPS

Using the Predefined CiscoTAC-1 Destination Profile

The CiscoTAC-1 profile is automatically configured in the Call Home feature for your use with the Cisco Smart Call Home service. This profile includes certain information, such as the destination e-mail address and HTTPS URL, and default alert groups for communication with the Smart Call Home service. Some of these attributes, such as the destination e-mail address, HTTPS URL, and message format cannot be modified.

You can use either email or http transport to communicate with the Smart Call Home service backend server. By default, the CiscoTAC-1 profile is inactive and uses email as the default transport method. To use email transport, you only need to enable the profile. However, to use this profile with the Cisco Smart Call Home service secure server (via HTTPS), you not only must enable the profile, but you must also change the transport method to HTTP as shown in the following example:

Router# configure terminalRouter(config)# call-homeRouter(config-call-home)# profile CiscoTAC-1Router(cfg-call-home-profile)# destination transport-method httpRouter(cfg-call-home-profile)# active

For more information about additional requirements for Configuring the Smart Call Home service, see the “How To Configure Call Home to Support the Smart Call Home Service” section on page 6-26.





Step 2 call-home



Step 3 rename profile source-profile target-profile

Example:Router(cfg-call-home)# rename profile2 testprofile

Renames an existing source file, where:

• source-profile—Specifies the existing name of the profile.

• target-profile—Specifies a new name for the existing profile.


OL-16506-08


Verifying the Call Home Profile Configuration

To verify the profile configuration for Call Home, use the show call-home profile command. See the “Displaying Call Home Configuration Information” section on page 6-31 for more information and examples.

Subscribing to Alert GroupsAn alert group is a predefined subset of Call Home alerts supported in all routers. Different types of Call Home alerts are grouped into different alert groups depending on their type. The following alert groups are available on the Cisco ASR 1000 Series Routers:

• Configuration

• Diagnostic

• Environment

• Inventory

• Syslog

The triggering events for each alert group are listed in the “Alert Group Trigger Events and Commands” section on page 6-37, and the contents of the alert group messages are listed in the “Message Contents” section on page 6-39.

You can select one or more alert groups to be received by a destination profile.

Note A Call Home alert is only sent to destination profiles that have subscribed to the alert group containing that Call Home alert. In addition, the alert group must be enabled.

Periodic Notification

When you subscribe a destination profile to either the Configuration or the Inventory alert group, you can choose to receive the alert group messages asynchronously or periodically at a specified time. The sending period can be one of the following:

• Daily—Specify the time of day to send, using an hour:minute format hh:mm, with a 24-hour clock (for example, 14:30).

• Weekly—Specify the day of the week and time of day in the format day hh:mm, where the day of the week is spelled out (for example, monday).

• Monthly—Specify the numeric date, from 1 to 31, and the time of day, in the format date hh:mm.

Message Severity Threshold

When you subscribe a destination profile to the Environment or Syslog alert group, you can set a threshold for the sending of alert group messages based on the message’s level of severity. Any message with a severity lower than the specified threshold of the destination profile is not sent to the destination.

Table 1 lists the keywords used to configure the severity, which range from catastrophic (level 9, highest level of urgency) to debugging (level 0, lowest level of urgency). If no severity threshold is configured, the default is debugging (level 0). However, the default is not recommended due to the number of messages that will be triggered.


OL-16506-08


Note Call Home severity levels are not the same as system message logging severity levels.

Syslog Pattern Matching

When you subscribe a destination profile to the Syslog alert group, you can optionally specify a text pattern to be matched within each syslog message. If you configure a pattern, a Syslog alert group message is sent only if it contains the specified pattern and meets the severity threshold. If the pattern contains spaces, you must enclose it in quotes (“ ”) when configuring it. You can specify up to five patterns for each destination profile.

To subscribe a destination profile to one or more alert groups, complete the following steps:

SUMMARY STEPS


2. call-home

3. alert-group {all | configuration | environment | inventory | syslog}

4. profile name

5. subscribe-to-alert-group all

6. subscribe-to-alert-group configuration [periodic {daily hh:mm | monthly date hh:mm | weekly day hh:mm}]

7. subscribe-to-alert-group diagnostic [severity {catastrophic | critical | debugging | disaster | fatal | major | minor | normal | notification | warning}]

8. subscribe-to-alert-group environment [severity {catastrophic | critical | debugging | disaster | fatal | major | minor | normal | notification | warning}]

9. subscribe-to-alert-group inventory [periodic {daily hh:mm | monthly date hh:mm | weekly day hh:mm}]

Table 1 Severity and Syslog Level Mapping

Level Keyword Syslog Level Description

9 catastrophic N/A Network-wide catastrophic failure.

8 disaster N/A Significant network impact.

7 fatal Emergency (0) System is unusable.

6 critical Alert (1) Critical conditions, immediate attention needed.

5 major Critical (2) Major conditions.

4 minor Error (3) Minor conditions.

3 warning Warning (4) Warning conditions.

2 notification Notice (5) Basic notification and informational messages. Possibly independently insignificant.

1 normal Information (6) Normal event signifying return to normal state.

0 debugging Debug (7) Debugging messages.


OL-16506-08


10. subscribe-to-alert-group syslog [severity {catastrophic | critical | debugging | disaster | fatal | major | minor | normal | notification | warning}] [pattern string]

11. exit

DETAILED STEPS





Step 2 call-home



Step 3 alert-group {all | configuration | environment | inventory | syslog}

Example:Router(cfg-call-home)# alert-group all

Enables the specified alert group. Use the all keyword to enable all alert groups. By default, all alert groups are enabled.

Step 4 profile name

Example:Router(cfg-call-home)# profile profile1

Enters call home destination profile configuration mode for the specified destination profile.

Step 5 subscribe-to-alert-group all

Example:Router(cfg-call-home-profile)# subscribe-to-alert-group all

(Optional) Subscribes this destination profile to all available alert groups.

Note Alternatively, you can also subscribe to alert groups individually by specific type as described in steps 6 through 9.

Step 6 subscribe-to-alert-group configuration [periodic {daily hh:mm | monthly date hh:mm | weekly day hh:mm}]

Example:Router(cfg-call-home-profile)# subscribe-to-alert-group configuration periodic daily 12:00

Subscribes this destination profile to the Configuration alert group, with an optional periodic value.

Step 7 subscribe-to-alert-group diagnostic [severity {catastrophic | critical | debugging | disaster | fatal | major | minor | normal | notification | warning}]

Example:Router(cfg-call-home-profile)# subscribe-to-alert-group diagnostic severity critical

Subscribes this destination profile to the Diagnostic alert group, with an optional severity level.


OL-16506-08


Configuring Contact InformationEach router must include a contact e-mail address. You can optionally include a phone number, street address, contract ID, customer ID, and site ID.

To assign the contact information, complete the following steps:

SUMMARY STEPS


2. call-home

3. contact-email-addr email-address

4. phone-number +phone-number

5. street-address street-address

6. customer-id text

7. site-id text

8. contract-id text

Step 8 subscribe-to-alert-group environment [severity {catastrophic | critical | debugging | disaster | fatal | major | minor | normal | notification | warning}]

Example:Router(cfg-call-home-profile)# subscribe-to-alert-group environment severity major

Subscribes this destination profile to the Environment alert group, with an optional severity level.

Step 9 subscribe-to-alert-group inventory [periodic {daily hh:mm | monthly date hh:mm | weekly day hh:mm}]

Example:Router(cfg-call-home-profile)# subscribe-to-alert-group inventory periodic monthly 1 12:00

Subscribes this destination profile to the Inventory alert group, with an optional periodic value.

Step 10 subscribe-to-alert-group syslog [severity {catastrophic | critical | debugging | disaster | fatal | major | minor | normal | notification | warning}][pattern string]

Example:Router(cfg-call-home-profile)# subscribe-to-alert-group syslog

Subscribes this destination profile to the Syslog alert group, with an optional severity level. You can specify a pattern to be matched in the syslog message, up to a maximum of five patterns per profile. If the pattern contains spaces, you must enclose it in quotes (“ ”).

Step 11 exit


Exits call home destination profile configuration mode.



OL-16506-08


DETAILED STEPS



Example:Router> configure terminal


Step 2 call-home



Step 3 contact-email-addr email-address

Example:Router(cfg-call-home)# contact-email-addr [email protected]

Assigns the customer’s e-mail address. Enter up to 200 characters in e-mail address format with no spaces.

Step 4 phone-number +phone-number

Example:Router(cfg-call-home)# phone-number +1-222-333-4444

(Optional) Assigns the customer’s phone number.

Note The number must begin with a plus (+) prefix, and may contain only dashes (-) and numbers. Enter up to 16 characters. If you include spaces, you must enclose your entry in quotes (“ ”).

Step 5 street-address street-address

Example:Router(cfg-call-home)# street-address “1234 Any Street, Any city, Any state, 12345”

(Optional) Assigns the customer’s street address where RMA equipment can be shipped. Enter up to 200 characters. If you include spaces, you must enclose your entry in quotes (“ ”).

Step 6 customer-id text

Example:Router(cfg-call-home)# customer-id Customer1234

(Optional) Identifies the customer ID. Enter up to 64 characters. If you include spaces, you must enclose your entry in quotes (“ ”).

Step 7 site-id text

Example:Router(cfg-call-home)# site-id Site1ManhattanNY

(Optional) Identifies the customer site ID. Enter up to 200 characters. If you include spaces, you must enclose your entry in quotes (“ ”).

Step 8 contract-id text

Example:Router(cfg-call-home)# contract-id Company1234

(Optional) Identifies the customer’s contract ID for the router. Enter up to 64 characters. If you include spaces, you must enclose your entry in quotes (“ ”).


OL-16506-08


Example

The following example shows the configuration of contact information:

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z.Router(config)# call-homeRouter(cfg-call-home)# contact-email-addr [email protected](cfg-call-home)# phone-number +1-222-333-4444Router(cfg-call-home)# street-address “1234 Any Street, Any city, Any state, 12345”Router(cfg-call-home)# customer-id Customer1234 Router(cfg-call-home)# site-id Site1ManhattanNYRouter(cfg-call-home)# contract-id Company1234 Router(cfg-call-home)# exit

Configuring the Number of Call Home Messages Sent Per MinuteThe Call Home feature defaults to a maximum of 20 messages per minute. If you want to change that value, complete the following steps:

SUMMARY STEPS


2. call-home

3. rate-limit number

DETAILED STEPS

Enabling and Disabling Call Home To enable or disable the Call Home feature, complete the following steps:

SUMMARY STEPS






Step 2 call-home



Step 3 rate-limit number

Example:Router(cfg-call-home)# rate-limit 40

Specifies a limit on the number of messages sent per minute. Range 1 to 60. The default is 20.


OL-16506-08


2. service call-home

3. no service call-home

DETAILED STEPS

Sending Call Home Communications ManuallyYou can manually send several types of Call Home communications. To send Call Home communications, complete the tasks in this section. This section contains the following subsections:

• Sending a Call Home Test Message Manually, page 6-22

• Sending Call Home Alert Group Messages Manually, page 6-23

• Submitting Call Home Analysis and Report Requests, page 6-24

• Sending the Output of a Command to Cisco or an E-Mail Address, page 6-25t

Sending a Call Home Test Message Manually

You can use the call-home test command to send a user-defined Call Home test message.

SUMMARY STEPS

1. call-home test [“test-message”] profile name

DETAILED STEPS





Step 2 service call-home

Example:Router(config)# service call-home

Enables the Call Home feature.

Step 3 no service call-home

Example:Router(config)# no service call-home

Disables the Call Home feature.


Step 1 call-home test [“test-message”] profile name

Example:Router# call-home test profile profile1

Sends a test message to the specified destination profile. The user-defined test message text is optional, but must be enclosed in quotes (“ ”) if it contains spaces. If no user-defined message is configured, a default message is sent.


OL-16506-08


Sending Call Home Alert Group Messages Manually

You can use the call-home send command to manually send a specific alert group message.

Note the following guidelines when manually sending a Call Home alert group message:

• Configuration, diagnostic, and inventory alert groups can be sent manually.

• When you manually trigger an alert group message and you specify a destination profile name, a message is sent to the destination profile regardless of the active status, subscription status, or severity setting of the profile.

• When you manually trigger a configuration or inventory alert group message and do not specify a destination profile name, a message is sent to all active profiles that have either a normal or periodic subscription to the specified alert group.

• When you manually trigger a diagnostic alert group message and do not specify a destination profile name, a message is sent to all active profiles that have a lower severity subscription than the severity of the diagnostic results of the specified slot.

To manually trigger Call Home alert group messages, complete the following steps:

SUMMARY STEPS

1. call-home send alert-group configuration [profile name]

2. call-home send alert-group diagnostic slot R0 [profile name]

3. call-home send alert-group inventory [profile name]

DETAILED STEPS


Step 1 call-home send alert-group configuration [profile name]

Example:Router# call-home send alert-group configuration profile CiscoTAC-1

Sends a configuration alert group message to one destination profile if specified, or to all subscribed destination profiles.

Step 2 call-home send alert-group diagnostic slot R0 [profile name]

Example:Router# call-home send alert-group diagnostic slot R0 profile CiscoTAC-1

Sends a diagnostic alert group message to one destination profile if specified, or to all subscribed destination profiles with a lower severity subscription than the diagnostic result for route processor slot 0.

Step 3 call-home send alert-group inventory [profile name]

Example:Router# call-home send alert-group inventory

Sends an inventory alert group message to one destination profile if specified, or to all subscribed destination profiles.


OL-16506-08


Submitting Call Home Analysis and Report Requests

You can use the call-home request command to submit information about your system to Cisco Systems to receive helpful analysis and report information specific to your system. You can request a variety of reports, including security alerts, known bugs, best practices, and command references.

Note the following guidelines when manually sending Call Home analysis and report requests:

• If a profile name is specified, the request is sent to the profile. If no profile is specified, the request is sent to the Cisco TAC profile. The recipient profile does not need to be enabled for the call-home request. The profile should specify the e-mail address where the transport gateway is configured so that the request message can be forwarded to the Cisco TAC and the user can receive the reply from the Smart Call Home service.

• The ccoid user-id is the registered identifier of the Smart Call Home user. If the user-id is specified, the response is sent to the e-mail address of the registered user. If no user-id is specified, the response is sent to the contact e-mail address of the device.

• Based on the keyword specifying the type of report requested, the following information is returned:

– config-sanity—Information on best practices as related to the current running configuration.

– bugs-list—Known bugs in the running version and in the currently applied features.

– command-reference—Reference links to all commands in the running configuration.

– product-advisory—Product Security Incident Response Team (PSIRT) notices, End of Life (EOL) or End of Sales (EOS) notices, or field notices (FN) that may affect devices in your network.

To submit a request for analysis and report information from the Cisco Output Interpreter tool, complete the following steps:

SUMMARY STEPS

1. call-home request output-analysis “show-command” [profile name] [ccoid user-id]

2. call-home request {config-sanity | bugs-list | command-reference | product-advisory} [profile name] [ccoid user-id]

DETAILED STEPS


Step 1 call-home request output-analysis “show-command”[profile name] [ccoid user-id]

Example:Router# call-home request output-analysis “show diag” profile TG

Sends the output of the specified show command for analysis. The show command must be contained in quotes (“”).

Step 2 call-home request {config-sanity | bugs-list | command-reference | product-advisory}[profile name] [ccoid user-id]

Example:Router# call-home request config-sanity profile TG

Sends the output of a predetermined set of commands, such as the show running-config all and show version commands, for analysis. In addition, the call home request product-advisory subcommand includes all inventory alert group commands. The keyword specified after the call-home request command specifies the type of report requested.


OL-16506-08


Example

The following example shows a request for analysis of a user-specified show command:

Router# call-home request output-analysis "show diag" profile TG

Sending the Output of a Command to Cisco or an E-Mail Address

You can use the call-home send command to execute a CLI command and e-mail the command output to Cisco or to an e-mail address that you specify.

Note the following guidelines when sending the output of a command:

• The specified CLI command can be any run command, including commands for all modules. The command must be contained in quotes (“”).

• If an e-mail address is specified, the command output is sent to that address. If no e-mail address is specified, the output is sent to the Cisco TAC ([email protected]). The e-mail is sent in long text format with the service number, if specified, in the subject line.

• The service number is required only if no e-mail address is specified, or if a Cisco TAC e-mail address is specified.

To execute a CLI command and e-mail the command output, complete the following step:

SUMMARY STEPS

1. call-home send “command” {email email-addr [tac-service-request request-number] | tac-service-request request-number email email-addr}

DETAILED STEPS

Example

The following example shows how to send the output of a CLI command to a user-specified e-mail address:

Router# call-home send "show diag" email [email protected]


Step 1 call-home send “command”{email email-addr [tac-service-request request-number] | tac-service-request request-number [email email-addr]}

Example:Router# call-home send “show call-home” email [email protected]

Executes the specified CLI command and e-mails the output, where:

• email email-addr—Specifies the email address to which the command output should be sent. This keyword is optional if used after entering the tac-service-request option.

• tac-service-request request-number—Specifies the TAC service request number that will appear in the subject line of the email. This keyword is optional if used after entering the email option.


OL-16506-08

Chapter 6 Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers How To Configure Call Home to Support the Smart Call Home Service

How To Configure Call Home to Support the Smart Call Home Service.

This section provides an overview of the minimum steps required to configure the Call Home feature on a Cisco device, and other required supporting configuration to communicate securely with the Smart Call Home service using HTTPS:

• Prerequisites, page 6-26 (required)

• Configure and Enable Call Home, page 6-26 (required)

• Declare and Authenticate a CA Trustpoint, page 6-28 (required)

• Start Smart Call Home Registration, page 6-30 (required)

PrerequisitesBefore you configure and use the Smart Call Home Service, be sure that you have completed the following prerequisites:

• Verify that you have an active Cisco Systems service contract for the device being configured.

• Verify that you have IP connectivity to the Cisco HTTPS server.

• Obtain the latest Cisco Systems server security certificate. In Cisco IOS XE Release 2.6.0, the following shows the latest text for the Cisco Systems server security certificate:

MIIDAjCCAmsCEH3Z/gfPqB63EHln+6eJNMYwDQYJKoZIhvcNAQEFBQAwgcExCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE8MDoGA1UECxMzQ2xhc3MgMyBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEcyMTowOAYDVQQLEzEoYykgMTk5OCBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMB4XDTk4MDUxODAwMDAwMFoXDTI4MDgwMTIzNTk1OVowgcExCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE8MDoGA1UECxMzQ2xhc3MgMyBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEcyMTowOAYDVQQLEzEoYykgMTk5OCBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDMXtERXVxp0KvTuWpMmR9ZmDCOFoUgRm1HP9SFIIThbbP4pO0M8RcPO/mn+SXXwc+EY/J8Y8+iR/LGWzOOZEAEaMGAuWQcRXfH2G71lSk8UOg013gfqLptQ5GVj0VXXn7F+8qkBOvqlzdUMG+7AUcyM83cV5tkaWH4mx0ciU9cZwIDAQABMA0GCSqGSIb3DQEBBQUAA4GBAFFNzb5cy5gZnBWyATl4Lk0PZ3BwmcYQWpSkU01UbSuvDV1Ai2TT1+7eVmGSX6bEHRBhNtMsJzzoKQm5EWR0zLVznxxIqbxhAe7iF6YM40AIOw7n60RzKprxaZLvcRTDOaxxp5EJb+RxBrO6WVcmeQD2+A2iMzAo1KpYoJ2daZH9

Configure and Enable Call HomeTo establish the Cisco Smart Call Home service, there are certain steps that must be peformed to configure and enable the Call Home feature on the Cisco ASR 1000 Series Router.

The CiscoTAC-1 profile is predefined in the Call Home feature to communicate using email to the backend server for the Smart Call Home service. The URL to the Cisco HTTPS backend server is also predefined. This profile is inactive by default.


OL-16506-08


However, unlike other profiles that you can configure in Call Home to support both transport methods, the CiscoTAC-1 profile can only use one transport method at a time. Therefore, to use this profile with the Cisco Smart Call Home HTTPS server, you must change the transport method from email to HTTP and enable the profile. In addition, you must minimally specify a contact e-mail address and enable the Call Home feature.

SUMMARY STEPS


2. call-home

3. profile CiscoTAC-1

4. destination transport-method http

5. active

6. exit

7. contact-email-addr email-address

8. exit

9. service call-home

10. exit


DETAILED STEPS





Step 2 call-home



Step 3 profile CiscoTAC-1

Example:Router(config-call-home)# profile CiscoTAC-1

Enters call home destination profile configuration mode for the CiscoTAC-1 destination profile.

Step 4 destination transport-method http

Example:Router(cfg-call-home-profile)# destination transport-method http

(Required only if using HTTPS) Configures the message transport method for http.

Step 5 active


Enables the destination profile.


OL-16506-08


Declare and Authenticate a CA TrustpointTo establish communication with the Cisco HTTPS server for Smart Call Home service, you must declare and authenticate the Cisco server security certificate.

SUMMARY STEPS


2. crypto pki trustpoint name

3. enrollment terminal

4. exit

5. crypto pki authenticate name

6. At the prompt, paste the security certificate text.

7. quit

8. yes

9. end


Step 6 exit



Step 7 contact-email-addr email-address

Example:Router(cfg-call-home)# contact-email-addr [email protected]

Assigns the customer’s e-mail address. Enter up to 200 characters in e-mail address format with no spaces.

Step 8 exit

Example:Router(cfg-call-home)# exit

Exits call home configuration mode and returns to global configuration mode.

Step 9 service call-home

Example:Router(config)# service call-home

Enables the Call Home feature.

Step 10 exit

Example:Router(config)# exit

Exits global configuration mode and returns to privileged EXEC mode.


Example:Router# copy running-config startup-config

Saves the configuration to NVRAM.



OL-16506-08


DETAILED STEPS





Step 2 crypto pki trustpoint name

Example:Router(config)# crypto pki trustpoint cisco

Declares a CA trustpoint on your router and enters CA trustpoint configuration mode.

Step 3 enrollment terminal

Example:Router(ca-trustpoint)# enrollment terminal

Specifies a manual cut-and-paste method of certificate enrollment.

Step 4 exit

Example:Router(ca-trustpoint)# exit

Exits CA trustpoint configuration mode and returns to global configuration mode.

Step 5 crypto pki authenticate name

Example:Router(config)# crypto pki authenticate cisco

Authenticates the named CA.

Note The CA name should match the name specified in the crypto pki trustpoint command.

Step 6 At the prompt, paste the security certificate text.

Example:Enter the base 64 encoded CA certificate.End with a blank line or the word "quit" on a line by itself

<Paste certificate text here>

Specifies the security certificate text.

Step 7 quit

Example:quit

Specifies the end of the security certificate text.

Step 8 yes

Example:% Do you accept this certificate? [yes/no]: yes

Confirms acceptance of the entered security certificate.

Step 9 end

Example:Router# end

Exits global configuration mode and returns to privileged EXEC mode.


Example:Router# copy running-config startup-config

Saves the configuration to NVRAM.


OL-16506-08


Examples

Router# configure terminalRouter(config)# crypto pki trustpoint ciscoRouter(ca-trustpoint)# enrollment terminalRouter(ca-trustpoint)# exitRouter(config)# crypto pki authenticate cisco

Enter the base 64 encoded CA certificate.End with a blank line or the word "quit" on a line by itself

MIIDAjCCAmsCEH3Z/gfPqB63EHln+6eJNMYwDQYJKoZIhvcNAQEFBQAwgcExCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE8MDoGA1UECxMzQ2xhc3MgMyBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEcyMTowOAYDVQQLEzEoYykgMTk5OCBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMB4XDTk4MDUxODAwMDAwMFoXDTI4MDgwMTIzNTk1OVowgcExCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE8MDoGA1UECxMzQ2xhc3MgMyBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEcyMTowOAYDVQQLEzEoYykgMTk5OCBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDMXtERXVxp0KvTuWpMmR9ZmDCOFoUgRm1HP9SFIIThbbP4pO0M8RcPO/mn+SXXwc+EY/J8Y8+iR/LGWzOOZEAEaMGAuWQcRXfH2G71lSk8UOg013gfqLptQ5GVj0VXXn7F+8qkBOvqlzdUMG+7AUcyM83cV5tkaWH4mx0ciU9cZwIDAQABMA0GCSqGSIb3DQEBBQUAA4GBAFFNzb5cy5gZnBWyATl4Lk0PZ3BwmcYQWpSkU01UbSuvDV1Ai2TT1+7eVmGSX6bEHRBhNtMsJzzoKQm5EWR0zLVznxxIqbxhAe7iF6YM40AIOw7n60RzKprxaZLvcRTDOaxxp5EJb+RxBrO6WVcmeQD2+A2iMzAo1KpYoJ2daZH9quitCertificate has the following attributes: Fingerprint MD5: A2339B4C 747873D4 6CE7C1F3 8DCB5CE9 Fingerprint SHA1: 85371CA6 E550143D CE280347 1BDE3A09 E8F8770F

% Do you accept this certificate? [yes/no]: yesTrustpoint CA certificate accepted.% Certificate successfully imported

Router(config)# endRouter# copy running-config startup-config

Start Smart Call Home Registration To start the Smart Call Home registration process, manually send an inventory alert-group message to the CiscoTAC-1 profile.

SUMMARY STEPS

1. call-home send alert-group inventory profile CiscoTAC-1


OL-16506-08

Chapter 6 Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers Displaying Call Home Configuration Information

DETAILED STEPS

What To Do Next

• Receive an email from Cisco Systems and follow the instructions to complete the device registration in the Smart Call Home web application.

• Launch the Smart Call Home web application at the following URL:

https://tools.cisco.com/sch/

• Accept the Legal Agreement.

• Confirm device registration for Call Home devices with pending registration.

For more information about using the Smart Call Home web application, see Smart Call Home User Guide. This user guide also includes configuration examples for sending Smart Call Home messages directly from your device or through a transport gateway (TG) aggregation point. You can use a TG aggregation point in cases requiring support for multiple devices or in cases where security requirements mandate that your devices must not be connected directly to the Internet.

Displaying Call Home Configuration InformationYou can use variations of the show call-home command to display Call Home configuration information.

To display the configured Call Home information, use one or more of the following commands:

SUMMARY STEPS

1. show call-home

2. show call-home detail

3. show call-home alert-group

4. show call-home mail-server status

5. show call-home profile {all | name}

6. show call-home statistics


Step 1 call-home send alert-group inventory profile CiscoTAC-1

Example:Router# call-home send alert-group inventory profile CiscoTAC-1

Sends an inventory alert group message to the CiscoTAC-1 destination profile.


OL-16506-08

https://tools.cisco.com/sch/

http://www.cisco.com/en/US/docs/switches/lan/smart_call_home/book.html



DETAILED STEPS

Examples

The following examples show the sample output when using different options of the show call-home command.

Example 1 Configured Call Home Information in Summary

Router# show call-homeCurrent call home settings: call home feature : disable call home message's from address: [email protected] call home message's reply-to address: [email protected]

vrf for call-home messages: Mgmt-intf

contact person's email address: [email protected]

contact person's phone number: +14085551234 street address: 1234 Any Street Any city Any state 12345 customer ID: [email protected] contract ID: 123456789 site ID: example.com Mail-server[1]: Address: smtp.example.com Priority: 1


Step 1 show call-home

Example:Router# show call-home

Displays the Call Home configuration in summary.

Step 2 show call-home detail

Example:Router# show call-home detail

Displays the Call Home configuration in detail.

Step 3 show call-home alert-group

Example:Router# show call-home alert-group

Displays the available alert groups and their status.

Step 4 show call-home mail-server status

Example:Router# show call-home mail-server status

Checks and displays the availability of the configured e-mail server(s).

Step 5 show call-home profile {all | name}

Example:Router# show call-home profile all

Displays the configuration of the specified destination profile. Use the all keyword to display the configuration of all destination profiles.

Step 6 show call-home statistics

Example:Router# show call-home statistics

Displays the statistics of Call Home events.


OL-16506-08


Mail-server[2]: Address: 192.168.0.1 Priority: 2 Rate-limit: 20 message(s) per minute

Available alert groups: Keyword State Description ------------------------ ------- ------------------------------- configuration Enable configuration info diagnostic Enable diagnostic info environment Enable environmental info inventory Enable inventory info syslog Enable syslog info

Profiles: Profile Name: campus-noc Profile Name: CiscoTAC-1

Example 2 Configured Call Home Information in Detail

Router# show call-home detailCurrent call home settings: call home feature : disable call home message's from address: [email protected] call home message's reply-to address: [email protected]

vrf for call-home messages: Mgmt-intf

contact person's email address: [email protected]

contact person's phone number: +14085551234 street address: 1234 Any Street Any city Any state 12345 customer ID: [email protected] contract ID: 123456789 site ID: example.com Mail-server[1]: Address: smtp.example.com Priority: 1 Mail-server[2]: Address: 192.168.0.1 Priority: 2 Rate-limit: 20 message(s) per minute

Available alert groups: Keyword State Description ------------------------ ------- ------------------------------- configuration Enable configuration info diagnostic Enable diagnostic info environment Enable environmental info inventory Enable inventory info syslog Enable syslog info

Profiles:

Profile Name: campus-noc Profile status: ACTIVE Preferred Message Format: long-text Message Size Limit: 3145728 Bytes Transport Method: email Email address(es): [email protected] HTTP address(es): Not yet set up

Alert-group Severity ------------------------ ------------ inventory normal

Syslog-Pattern Severity ------------------------ ------------ N/A N/A

Profile Name: CiscoTAC-1


OL-16506-08


Profile status: INACTIVE Preferred Message Format: xml Message Size Limit: 3145728 Bytes Transport Method: email Email address(es): [email protected] HTTP address(es): https://tools.cisco.com/its/service/oddce/services/DDCEService

Periodic configuration info message is scheduled every 23 day of the month at 10:28

Periodic inventory info message is scheduled every 23 day of the month at 10:13

Alert-group Severity ------------------------ ------------ diagnostic minor environment minor inventory normal

Syslog-Pattern Severity ------------------------ ------------ .* major

Example 3 Available Call Home Alert Groups

Router# show call-home alert-groupAvailable alert groups: Keyword State Description ------------------------ ------- ------------------------------- configuration Enable configuration info diagnostic Enable diagnostic info environment Enable environmental info inventory Enable inventory info syslog Enable syslog info

Example 4 E-Mail Server Status Information

Router# show call-home mail-server statusPlease wait. Checking for mail server status ...

Translating "smtp.example.com" Mail-server[1]: Address: smtp.example.com Priority: 1 [Not Available] Mail-server[2]: Address: 192.168.0.1 Priority: 2 [Not Available]

Example 5 Information for All Destination Profiles (Predefined and User-Defined)

Router# show call-home profile all





OL-16506-08


Profile Name: CiscoTAC-1 Profile status: INACTIVE Preferred Message Format: xml Message Size Limit: 3145728 Bytes Transport Method: email Email address(es): [email protected] HTTP address(es): https://tools.cisco.com/its/service/oddce/services/DDCEService

Periodic configuration info message is scheduled every 23 day of the month at 12:13

Periodic inventory info message is scheduled every 23 day of the month at 11:58

Alert-group Severity ------------------------ ------------ diagnostic minor environment minor inventory normal

Syslog-Pattern Severity ------------------------ ------------ .* major

Router#

Example 6 Information for a User-Defined Destination Profile

Router# show call-home profile campus-noc




Example 7 Call Home Statistics

Router# show call-home statisticsMessage Types Total Email HTTP------------- -------------------- -------------------- ------------------Total Success 6 6 0 Config 4 4 0 Diagnostic 0 0 0 Environment 0 0 0 Inventory 2 2 0 SysLog 0 0 0 Test 0 0 0 Request 0 0 0 Send-CLI 0 0 0

Total In-Queue 0 0 0 Config 0 0 0 Diagnostic 0 0 0


OL-16506-08

Chapter 6 Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers Default Settings

Environment 0 0 0 Inventory 0 0 0 SysLog 0 0 0 Test 0 0 0 Request 0 0 0 Send-CLI 0 0 0

Total Failed 0 0 0 Config 0 0 0 Diagnostic 0 0 0 Environment 0 0 0 Inventory 0 0 0 SysLog 0 0 0 Test 0 0 0 Request 0 0 0 Send-CLI 0 0 0

Total Ratelimit -dropped 0 0 0 Config 0 0 0 Diagnostic 0 0 0 Environment 0 0 0 Inventory 0 0 0 SysLog 0 0 0 Test 0 0 0 Request 0 0 0 Send-CLI 0 0 0

Last call-home message sent time: 2010-01-11 18:32:32 GMT+00:00

Default SettingsTable 2 lists the default Call Home settings.

Table 2 Default Call Home Settings

Parameters Default

Call Home feature status Disabled

User-defined profile status Active

Predefined Cisco TAC profile status Inactive

Transport method E-mail

Message format type XML

Destination message size for a message sent in long text, short text, or XML format 3,145,728

Alert group status Enabled

Call Home message severity threshold 0 (debugging)

Message rate limit for messages per minute 20


OL-16506-08

Chapter 6 Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers Alert Group Trigger Events and Commands

Alert Group Trigger Events and CommandsCall Home trigger events are grouped into alert groups, with each alert group assigned CLI commands to execute when an event occurs. The CLI command output is included in the transmitted message. Table 3 lists the trigger events included in each alert group, including the severity level of each event and the executed CLI commands for the alert group.

Table 3 Call Home Alert Groups, Events, and Actions

Alert GroupCall Home Trigger Event Syslog Event Severity

Description and CLI Commands Executed

Configuration — — — User-generated request for configuration. (Sent to TAC.)

CLI commands executed:

show platform show inventory show running-config all show startup-config show version

Diagnostic — — — CLI commands executed:

show platform show diagnostic result slot x detail show version show inventory show buffers show logging show diagnostic result slot all show diagnostic events slot all

— Error Counter Monitoring Test failure count exceeds threshold

%ASR1000_RP_DIAG_TEST-4- ERR_CNTR_HM_TEST_FAIL

4 ERROR_COUNTER_WARNING: Slot number Error counter exceeds threshold, system operation continue.

— Error Counter Monitoring Test failure count exceeds threshold

%ASR1000_RP_DIAG_TEST-4- ERR_CNTR_HM_TEST_DATA

4 ERROR_COUNTER_DATA: ID:number IN:number PO:number RE:number RM:number DV:number EG:number CF:number TF:number

Environmental — — — Events related to power, fan, and environment sensing elements, such as temperature alarms. (Sent to TAC.)


show platform show environment show inventory show logging


OL-16506-08

Chapter 6 Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers Alert Group Trigger Events and Commands

— — %ASR1000_PEM-3-FANFAIL 3 The fan in slot (slot/subslot number) is encountering a failure condition.

— — %ASR1000_PEM-6-FANOK 6 The fan in slot (slot/subslot number) is functioning properly.

— — %ASR1000_PEM-3-PEMFAIL 3 The PEM in slot (slot number) is switched off or encountering a failure condition.

— — %ASR1000_PEM-6-PEMOK 6 The PEM in slot (slot number) is functioning properly.

— — %ENVIRONMENTAL-1-ALERT 1 Any sensor in fp/cc/rp has exceeded a certain threshold and resulted in this environmental alert.

— ENVM %ENVIRONMENTAL-1-SENSORFAIL 1 Any sensor in fp/cc/rp has failed and resulted in this environmental alert.

— — %ENVIRONMENTAL-1-SENSOROK 1 Any sensor in fp/cc/rp has recovered and resulted in this environmental alert.

Inventory — — — Inventory status should be provided whenever a unit is cold-booted, or when FRUs are inserted or removed. This is considered a noncritical event, and the information is used for status and entitlement. (Sent to TAC.)


show platform show inventory oid show version show diag all eeprom detail

— SPA HARDWARE_REMOVAL

%ASR1000_OIR-6-REMSPA 6 SPA removed from subslot (slot/subslot number) and the interfaces are disabled.

— SPA HARDWARE_INSERTION

%ASR1000_OIR-6-INSSPA 6 SPA inserted in subslot (slot/subslot number).

— CC/FP/RP HARDWARE_REMOVAL

%ASR1000_OIR-6-REMCARD 6 Card (cc/rp/fp) removed from slot (slot number).

— CC/FP/RP HARDWARE_INSERTION

%ASR1000_OIR-6-INSCARD 6 Card (cc/rp/fp) inserted in slot (slot number).

Table 3 Call Home Alert Groups, Events, and Actions (continued)




OL-16506-08

Chapter 6 Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers Message Contents

Message ContentsThe following tables display the content formats of alert group messages:

• Table 4 describes the content fields of a short text message.

• Table 5 describes the content fields that are common to all long text and XML messages. The fields specific to a particular alert group message are inserted at a point between the common fields. The insertion point is identified in the table.

• Table 6 describes the inserted content fields for reactive messages (system failures that require a TAC case) and proactive messages (issues that might result in degraded system performance).

• Table 7 describes the inserted content fields for an inventory message.

This section also includes the following subsections that provide sample messages:

• Sample Syslog Alert Notification in Long-Text Format, page 6-43

• Sample Syslog Alert Notification in XML Format, page 6-47

— PEM /FM HARDWARE_REMOVAL

%ASR1000_PEM-6-REMPEM_FM 6 PEM/FM slot (slot number) removed.

— PEM /FM HARDWARE_INSERTION

%ASR1000_PEM-6-INSPEM_FM 6 PEM/FM slot (slot number) inserted.

Syslog — — — Event logged to syslog.


show inventory show logging

— SYSLOG LOG_EMERG 0 System is unusable.

— SYSLOG LOG_ALERT 1 Action must be taken immediately.

— SYSLOG LOG_CRIT 2 Critical conditions.

— SYSLOG LOG_ERR 3 Error conditions.

— SYSLOG LOG_WARNING 4 Warning conditions.

— SYSLOG LOG_NOTICE 5 Normal but signification condition.

— SYSLOG LOG_INFO 6 Informational.

— SYSLOG LOG_DEBUG 7 Debug-level messages.

Test — TEST — User-generated test message. (Sent to TAC.)


show platform show inventory show version

Table 3 Call Home Alert Groups, Events, and Actions (continued)




OL-16506-08


Table 4 Format for a Short Text Message

Data Item Description

Device identification Configured device name

Date/time stamp Time stamp of the triggering event

Error isolation message Plain English description of triggering event

Alarm urgency level Error level such as that applied to a system message

Table 5 Common Fields for All Long Text and XML Messages

Data Item (Plain Text and XML)

Description (Plain Text and XML)

MML Tag (XML Only)

Time stamp Date and time stamp of event in ISO time notation:

YYYY-MM-DD HH:MM:SS GMT+HH:MM.

CallHome/EventTime

Message name Name of message. Specific event names are listed in the “Alert Group Trigger Events and Commands” section on page 6-37.

For short text message only

Message type Specifically “Call Home”. CallHome/Event/Type

Message subtype Specific type of message: full, delta, test CallHome/Event/SubType

Message group Specifically “reactive”. Optional, because default is “reactive”.

Not applicable. For long-text message only

Severity level Severity level of message (see Table 1 on page 6-17). Body/Block/Severity

Source ID Product type for routing through the workflow engine. This is typically the product family name.

For long-text message only

Device ID Unique device identifier (UDI) for end device generating message. This field should be empty if the message is nonspecific to a fabric switch. The format is type@Sid@serial.

• type is the product model number from backplane IDPROM.

• @ is a separator character.

• Sid is C, identifying the serial ID as a chassis serial number.

• serial is the number identified by the Sid field.

Example: ASR1006@C@FOX105101DH

CallHome/CustomerData/ ContractData/DeviceId

Customer ID Optional user-configurable field used for contract information or other ID by any support service.

CallHome/CustomerData/ ContractData/CustomerId

Contract ID Optional user-configurable field used for contract information or other ID by any support service.

CallHome/CustomerData/ ContractData/ContractId

Site ID Optional user-configurable field used for site IDs supplied by Cisco Systems or other data meaningful to alternate support services.

CallHome/CustomerData/ ContractData/SiteId


OL-16506-08


Server ID If the message is generated from the fabric switch, this is the unique device identifier (UDI) of the switch.

The format is type@Sid@serial.

• type is the product model number from backplane IDPROM.

• @ is a separator character.

• Sid is C, identifying the serial ID as a chassis serial number.

• serial is the number identified by the Sid field.

Example: ASR1006@C@FOX105101DH

For long text message only

Message description Short text describing the error. CallHome/MessageDescription

Device name Node that experienced the event. This is the host name of the device.

CallHome/CustomerData/ SystemInfo/NameName

Contact name Name of person to contact for issues associated with the node experiencing the event.

CallHome/CustomerData/ SystemInfo/Contact

Contact e-mail E-mail address of person identified as contact for this unit. CallHome/CustomerData/ SystemInfo/ContactEmail

Contact phone number

Phone number of the person identified as the contact for this unit.

CallHome/CustomerData/ SystemInfo/ContactPhoneNumber

Street address Optional field containing street address for RMA part shipments associated with this unit.

CallHome/CustomerData/ SystemInfo/StreetAddress

Model name Model name of the router. This is the “specific model as part of a product family name.

CallHome/Device/Cisco_Chassis/ Model

Serial number Chassis serial number of the unit. CallHome/Device/Cisco_Chassis/ SerialNumber

Chassis part number Top assembly number of the chassis. CallHome/Device/Cisco_Chassis/ AdditionalInformation/AD@name= “PartNumber”

System object ID System Object ID that uniquely identifies the system. CallHome/Device/Cisco_Chassis/ AdditionalInformation/AD@name= “sysObjectID”

System description System description for the managed element. CallHome/Device/Cisco_Chassis/ AdditionalInformation/AD@name= “sysDescr”

Fields specific to a particular alert group message are inserted here.

The following fields may be repeated if multiple CLI commands are executed for this alert group.

Command output name

The exact name of the issued CLI command. /aml/Attachments/Attachment/Name

Table 5 Common Fields for All Long Text and XML Messages (continued)



MML Tag (XML Only)


OL-16506-08


Attachment type Attachment type. Usually “inline”. /aml/Attachments/Attachment@type

MIME type Normally “text” or “plain” or encoding type. /aml/Attachments/Attachment/ Data@encoding

Command output text

Output of command automatically executed (see Table 3 on page 6-37).

/mml/attachments/attachment/atdata

Table 6 Inserted Fields for a Reactive or Proactive Event Message



MML Tag (XML Only)

Chassis hardware version

Hardware version of chassis. CallHome/Device/Cisco_Chassis/ HardwareVersion

Supervisor module software version

Top-level software version. CallHome/Device/Cisco_Chassis/ AdditionalInformation/AD@name= “SoftwareVersion”

Affected FRU name Name of the affected FRU generating the event message. CallHome/Device/Cisco_Chassis/ Cisco_Card/Model

Affected FRU serial number

Serial number of affected FRU. CallHome/Device/Cisco_Chassis/ Cisco_Card/SerialNumber

Affected FRU part number

Part number of affected FRU. CallHome/Device/Cisco_Chassis/ Cisco_Card/PartNumber

FRU slot Slot number of FRU generating the event message. CallHome/Device/Cisco_Chassis/ Cisco_Card/LocationWithinContainer

FRU hardware version

Hardware version of affected FRU. CallHome/Device/Cisco_Chassis/ Cisco_Card/HardwareVersion

FRU software version

Software version(s) running on affected FRU. CallHome/Device/Cisco_Chassis/ Cisco_Card/SoftwareIdentity/ VersionString

Table 7 Inserted Fields for an Inventory Event Message



MML Tag (XML Only)

Chassis hardware version

Hardware version of chassis. CallHome/Device/Cisco_Chassis/ HardwareVersion

Supervisor module software version

Top-level software version. CallHome/Device/Cisco_Chassis/ AdditionalInformation/AD@name= “SoftwareVersion”

FRU name Name of the affected FRU generating the event message. CallHome/Device/Cisco_Chassis/ Cisco_Card/Model

Table 5 Common Fields for All Long Text and XML Messages (continued)



MML Tag (XML Only)


OL-16506-08


Sample Syslog Alert Notification in Long-Text FormatThe following example shows a Syslog alert notification in long-text format:

TimeStamp : 2009-12-03 12:26 GMT+05:00Message Name : syslogMessage Type : Call HomeMessage Group : reactiveSeverity Level : 2Source ID : ASR1000Device ID : ASR1006@C@FOX105101DHCustomer ID : [email protected] ID : 123456789Site ID : example.comServer ID : ASR1006@C@FOX105101DHEvent Description : *Dec 3 12:26:02.319 IST: %CLEAR-5-COUNTERS: Clear counter on all interfaces by consoleSystem Name : mcp-6ru-3Contact Email : [email protected] Phone : +14085551234Street Address : 1234 Any Street Any City Any State 12345Affected Chassis : ASR1006Affected Chassis Serial Number : FOX105101DHAffected Chassis Part No : 68-2584-05Affected Chassis Hardware Version : 2.1Command Output Name : show loggingAttachment Type : command outputMIME Type : text/plainCommand Output Text : Syslog logging: enabled (1 messages dropped, 29 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

Console logging: disabled Monitor logging: level debugging, 0 messages logged, xml disabled,

FRU s/n Serial number of FRU. CallHome/Device/Cisco_Chassis/ Cisco_Card/SerialNumber

FRU part number Part number of FRU. CallHome/Device/Cisco_Chassis/ Cisco_Card/PartNumber

FRU slot Slot number of FRU. CallHome/Device/Cisco_Chassis/ Cisco_Card/LocationWithinContainer

FRU hardware version

Hardware version of FRU. CallHome/Device/Cisco_Chassis/ CiscoCard/HardwareVersion

FRU software version

Software version(s) running on FRU. CallHome/Device/Cisco_Chassis/ Cisco_Card/SoftwareIdentity/ VersionString

Table 7 Inserted Fields for an Inventory Event Message (continued)



MML Tag (XML Only)


OL-16506-08


filtering disabled Buffer logging: level debugging, 112 messages logged, xml disabled, filtering disabled Exception Logging: size (4096 bytes) Count and timestamp logging messages: disabled Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 104 message lines logged

Log Buffer (1000000 bytes):

*Dec 3 07:16:55.020: ASR1000-RP HA: RF status CID 1340, seq 93, status RF_STATUS_REDUNDANCY_MODE_CHANGE, op 0, state DISABLED, peer DISABLED*Dec 3 07:17:00.379: %ASR1000_MGMTVRF-6-CREATE_SUCCESS_INFO: Management vrf Mgmt-intf created with ID 4085, ipv4 table-id 0xFF5, ipv6 table-id 0x1E000001*Dec 3 07:17:00.398: %NETCLK-5-NETCLK_MODE_CHANGE: Network clock source not available. The network clock has changed to freerun

*Dec 3 07:17:00.544: %LINEPROTO-5-UPDOWN: Line protocol on Interface LI-Null0, changed state to up*Dec 3 07:17:00.545: %LINK-3-UPDOWN: Interface EOBC0, changed state to up*Dec 3 07:17:00.545: %LINK-3-UPDOWN: Interface Lsmpi0, changed state to up*Dec 3 07:17:00.546: %LINK-3-UPDOWN: Interface LIIN0, changed state to up*Dec 3 07:17:00.546: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to down*Dec 3 07:17:01.557: %LINEPROTO-5-UPDOWN: Line protocol on Interface EOBC0, changed state to up*Dec 3 07:17:01.557: %LINEPROTO-5-UPDOWN: Line protocol on Interface Lsmpi0, changed state to up*Dec 3 07:17:01.558: %LINEPROTO-5-UPDOWN: Line protocol on Interface LIIN0, changed state to up*Dec 3 07:17:01.558: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down*Dec 3 07:17:01.818: %DYNCMD-7-CMDSET_LOADED: The Dynamic Command set has been loaded from the Shell Manager*Dec 3 07:16:30.926: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 2 is pre-release hardware*Dec 3 07:16:24.147: %HW_IDPROM_ENVMON-3-HW_IDPROM_CHECKSUM_INVALID: F1: cman_fp: The idprom contains an invalid checksum in a sensor entry. Expected: 63, calculated: fe*Dec 3 07:16:24.176: %CMFP-3-IDPROM_SENSOR: F1: cman_fp: One or more sensor fields from the idprom failed to parse properly because Success.*Dec 3 07:16:27.669: %CPPHA-7-START: F1: cpp_ha: CPP 0 preparing image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode*Dec 3 07:16:27.839: %CPPHA-7-START: F1: cpp_ha: CPP 0 startup init image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode*Dec 3 07:16:28.659: %CPPHA-7-START: F0: cpp_ha: CPP 0 preparing image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode*Dec 3 07:16:28.799: %CPPHA-7-START: F0: cpp_ha: CPP 0 startup init image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode*Dec 3 07:16:32.557: %CPPHA-7-START: F1: cpp_ha: CPP 0 running init image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode*Dec 3 07:16:32.812: %CPPHA-7-READY: F1: cpp_ha: CPP 0 loading and initialization complete*Dec 3 07:16:33.532: %CPPHA-7-START: F0: cpp_ha: CPP 0 running init image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode*Dec 3 07:16:33.786: %CPPHA-7-READY: F0: cpp_ha: CPP 0 loading and initialization complete*Dec 3 07:16:34.158: %IOSXE-6-PLATFORM: F1: cpp_cp: Process CPP_PFILTER_EA_EVENT__API_CALL__REGISTER*Dec 3 07:16:35.134: %IOSXE-6-PLATFORM: F0: cpp_cp: Process CPP_PFILTER_EA_EVENT__API_CALL__REGISTER*Dec 3 07:16:38.965: %CMRP-6-FP_HA_STATUS: R0/0: cmand: F0 redundancy state is Active with ready Standby


OL-16506-08


*Dec 3 07:17:01.926: %DYNCMD-7-PKGINT_INSTALLED: The command package 'platform_trace' has been succesfully installed*Dec 3 12:17:05.385 IST: %SYS-6-CLOCKUPDATE: System clock has been updated from 07:17:05 UTC Thu Dec 3 2009 to 12:17:05 IST Thu Dec 3 2009, configured from console by console.*Dec 3 12:17:05.506 IST: %SYS-5-CONFIG_I: Configured from memory by console*Dec 3 12:17:05.508 IST: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/2, interfaces disabled*Dec 3 12:17:05.508 IST: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/3, interfaces disabled*Dec 3 12:17:05.508 IST: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 2/3, interfaces disabled*Dec 3 12:17:05.514 IST: %SPA_OIR-6-OFFLINECARD: SPA (SPA-8XOC3-POS) offline in subslot 0/2*Dec 3 12:17:05.515 IST: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4XOC3-POS) offline in subslot 1/3*Dec 3 12:17:05.516 IST: %SPA_OIR-6-OFFLINECARD: SPA (SPA-1XOC12-POS) offline in subslot 2/3*Dec 3 12:17:05.520 IST: %ASR1000_OIR-6-INSCARD: Card (rp) inserted in slot R1*Dec 3 12:17:05.521 IST: %ASR1000_OIR-6-INSCARD: Card (fp) inserted in slot F0*Dec 3 12:17:05.521 IST: %ASR1000_OIR-6-ONLINECARD: Card (fp) online in slot F0*Dec 3 12:17:05.574 IST: %ASR1000_OIR-6-INSCARD: Card (fp) inserted in slot F1*Dec 3 12:17:05.574 IST: %ASR1000_OIR-6-ONLINECARD: Card (fp) online in slot F1*Dec 3 12:17:05.575 IST: %ASR1000_OIR-6-INSCARD: Card (cc) inserted in slot 0*Dec 3 12:17:05.575 IST: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 0*Dec 3 12:17:05.576 IST: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/2*Dec 3 12:17:05.580 IST: %ASR1000_OIR-6-INSCARD: Card (cc) inserted in slot 1*Dec 3 12:17:05.581 IST: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 1*Dec 3 12:17:05.582 IST: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/3*Dec 3 12:17:05.582 IST: %ASR1000_OIR-6-INSCARD: Card (cc) inserted in slot 2*Dec 3 12:17:05.582 IST: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 2*Dec 3 12:17:05.583 IST: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 2/3*Dec 3 12:17:05.844 IST: %SYS-5-RESTART: System restarted --Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Experimental Version 12.2(20091118:075558) [v122_33_xnf_asr_rls6_throttle-mcp_dev_rls6 102]Copyright (c) 1986-2009 by Cisco Systems, Inc.Compiled Wed 18-Nov-09 01:14 by *Dec 3 12:17:06.005 IST: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF*Dec 3 12:17:06.005 IST: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF*Dec 3 12:16:30.097 IST: %LINK-3-UPDOWN: SIP2/3: Interface EOBC2/1, changed state to up*Dec 3 12:16:27.595 IST: %LINK-3-UPDOWN: SIP0/2: Interface EOBC0/1, changed state to up*Dec 3 12:16:26.420 IST: %LINK-3-UPDOWN: SIP1/3: Interface EOBC1/1, changed state to up*Dec 3 12:17:07.435 IST: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF*Dec 3 12:17:07.435 IST: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF*Dec 3 12:17:07.476 IST: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up*Dec 3 12:17:08.137 IST: %SPA_OIR-6-ONLINECARD: SPA (SPA-4XOC3-POS) online in subslot 1/3*Dec 3 12:17:08.139 IST: %SPA_OIR-6-ONLINECARD: SPA (SPA-8XOC3-POS) online in subslot 0/2*Dec 3 12:17:08.346 IST: %SPA_OIR-6-ONLINECARD: SPA (SPA-1XOC12-POS) online in subslot 2/3*Dec 3 12:17:08.491 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up*Dec 3 12:17:11.047 IST: %SYS-6-BOOTTIME: Time taken to reboot after reload = 12319 seconds*Dec 3 12:17:11.562 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[879]: xinetd Version 2.3.14 started with no options compiled in.*Dec 3 12:17:11.562 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[879]: Started working: 1 available service*Dec 3 12:17:11.584 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[887]: xinetd Version 2.3.14 started with no options compiled in.*Dec 3 12:17:11.584 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[887]: Started working: 2 available services*Dec 3 12:17:13.753 IST: %LINK-3-UPDOWN: Interface POS0/2/0, changed state to down*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/1, changed state to down*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/2, changed state to down*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/3, changed state to down


OL-16506-08


*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/4, changed state to down*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/5, changed state to down*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS0/2/6, changed state to down*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS0/2/7, changed state to down*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS2/3/0, changed state to down*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS1/3/0, changed state to down*Dec 3 12:17:14.753 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/0, changed state to down*Dec 3 12:17:14.753 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/1, changed state to down*Dec 3 12:17:14.753 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/2, changed state to down*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/3, changed state to down*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/4, changed state to down*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/5, changed state to down*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/6, changed state to down*Dec 3 12:17:14.755 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/7, changed state to down*Dec 3 12:17:14.848 IST: %SONET-4-ALARM: POS0/2/1: SLOS declared*Dec 3 12:17:14.848 IST: %SONET-4-ALARM: POS0/2/2: SLOS declared*Dec 3 12:17:14.849 IST: %SONET-4-ALARM: POS0/2/3: SLOS declared*Dec 3 12:17:14.849 IST: %SONET-4-ALARM: POS0/2/4: SLOS declared*Dec 3 12:17:14.849 IST: %SONET-4-ALARM: POS0/2/5: SLOS declared*Dec 3 12:17:14.850 IST: %SONET-4-ALARM: POS0/2/6: SLOS declared*Dec 3 12:17:14.850 IST: %SONET-4-ALARM: POS0/2/7: SLOS declared*Dec 3 12:17:14.850 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS2/3/0, changed state to down*Dec 3 12:17:14.851 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS1/3/0, changed state to down*Dec 3 12:17:16.069 IST: %LINK-3-UPDOWN: Interface POS0/2/0, changed state to up*Dec 3 12:17:15.734 IST: %LINK-3-UPDOWN: SIP0/2: Interface POS0/2/0, changed state to up*Dec 3 12:17:16.868 IST: %LINK-3-UPDOWN: Interface POS1/3/0, changed state to up*Dec 3 12:17:16.905 IST: %LINK-3-UPDOWN: Interface POS2/3/0, changed state to up*Dec 3 12:17:16.538 IST: %LINK-3-UPDOWN: SIP0/2: Interface POS0/2/7, changed state to down*Dec 3 12:17:17.070 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/0, changed state to up*Dec 3 12:17:16.488 IST: %LINK-3-UPDOWN: SIP1/3: Interface POS1/3/0, changed state to up*Dec 3 12:17:17.868 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS1/3/0, changed state to up*Dec 3 12:17:16.199 IST: %LINK-3-UPDOWN: SIP2/3: Interface POS2/3/0, changed state to up*Dec 3 12:17:17.905 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS2/3/0, changed state to up*Dec 3 12:22:01.574 IST: %IP-4-DUPADDR: Duplicate address 172.27.55.233 on GigabitEthernet0, sourced by 001a.3044.1ec0*Dec 3 12:23:47.613 IST: %SYS-5-CONFIG_I: Configured from console by console*Dec 3 12:24:37.134 IST: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console*Dec 3 12:25:34.356 IST: %DIAG-3-TEST_FAIL: slot R0: TestErrorCounterMonitor{ID=1} has failed. Error code = 0x1 (DIAG_FAILURE)*Dec 3 12:25:39.459 IST: %DIAG-3-TEST_FAIL: slot R0: TestErrorCounterMonitor{ID=1} has failed. Error code = 0x1 (DIAG_FAILURE)*Dec 3 12:25:54.405 IST: %SYS-5-CONFIG_I: Configured from console by consolemcp-6ru-3#Command Output Name : show inventoryAttachment Type : command outputMIME Type : text/plainCommand Output Text : NAME: "Chassis", DESCR: "Cisco ASR1006 Chassis"PID: ASR1006 , VID: V00, SN: FOX105101DH

NAME: "module 0", DESCR: "Cisco ASR1000 SPA Interface Processor 10"


OL-16506-08


PID: MCP-CC , VID: V00, SN: JAB1104064W

NAME: "SPA subslot 0/2", DESCR: "8-port OC3/STM1 POS Shared Port Adapter"PID: SPA-8XOC3-POS , VID: V01, SN: JAE1236TSW0

NAME: "subslot 0/2 transceiver 0", DESCR: "OC3 SR-1/STM1 MM"PID: SFP-OC3-MM , VID: A , SN: OCP12231628

NAME: "module 1", DESCR: "Cisco ASR1000 SPA Interface Processor 10"PID: MCP-CC , VID: V00, SN: JAB1104062X

NAME: "SPA subslot 1/3", DESCR: "4-port OC3/STM1 POS Shared Port Adapter"PID: SPA-4XOC3-POS , VID: V01, SN: JAB085202QU


NAME: "module 2", DESCR: "Cisco ASR1000 SPA Interface Processor 10"PID: ASR1000-SIP10 , VID: V00, SN: JAB113701L9

NAME: "SPA subslot 2/3", DESCR: "1-port OC12/STM4 POS Shared Port Adapter"PID: SPA-1XOC12-POS , VID: V01, SN: JAE1236U41L


NAME: "module R0", DESCR: "Cisco ASR1000 Route Processor 1"PID: ASR1000-RP1 , VID: V00, SN: JAB11110181

NAME: "module R1", DESCR: "Cisco ASR1000 Route Processor 1"PID: ASR1000-RP1 , VID: V00, SN: JAB1111016K

NAME: "module F0", DESCR: "Cisco ASR1000 Embedded Services Processor, 10Gbps"PID: ASR1000-ESP10 , VID: V00, SN: JAB111801ZX

NAME: "module F1", DESCR: "Cisco ASR1000 Embedded Services Processor, 10Gbps"PID: ASR1000-ESP10 , VID: V00, SN: JAB111101AP

NAME: "Power Supply Module 0", DESCR: "Cisco ASR1006 AC Power Supply"PID: TBD000000000000000, VID: +Â , SN: ART1114Q00F

NAME: "Fan Module 1", DESCR: "Cisco ASR1006 Fan Module"PID: TBD000000000000000, VID: +Â , SN: ART1115P00D

Sample Syslog Alert Notification in XML FormatThe following example shows a Syslog alert notification in XML format:

<?xml version="1.0" encoding="UTF-8"?><soap-env:Envelope xmlns:soap-env="http://www.w3.org/2003/05/soap-envelope"><soap-env:Header><aml-session:Session xmlns:aml-session="http://www.cisco.com/2004/01/aml-session" soap-env:mustUnderstand="true" soap-env:role="http://www.w3.org/2003/05/soap-envelope/role/next"><aml-session:To>http://tools.cisco.com/neddce/services/DDCEService</aml-session:To><aml-session:Path><aml-session:Via>http://www.cisco.com/appliance/uri</aml-session:Via></aml-session:Path><aml-session:From>http://www.cisco.com/appliance/uri</aml-session:From><aml-session:MessageId>M0:FOX105101DH:CEC1E73E</aml-session:MessageId></aml-session:Session></soap-env:Header>


OL-16506-08


<soap-env:Body><aml-block:Block xmlns:aml-block="http://www.cisco.com/2004/01/aml-block"><aml-block:Header><aml-block:Type>http://www.cisco.com/2005/05/callhome/syslog</aml-block:Type><aml-block:CreationDate>2009-12-03 12:29:02 GMT+05:00</aml-block:CreationDate><aml-block:Builder><aml-block:Name>ASR1000</aml-block:Name><aml-block:Version>2.0</aml-block:Version></aml-block:Builder><aml-block:BlockGroup><aml-block:GroupId>G1:FOX105101DH:CEC1E73E</aml-block:GroupId><aml-block:Number>0</aml-block:Number><aml-block:IsLast>true</aml-block:IsLast><aml-block:IsPrimary>true</aml-block:IsPrimary><aml-block:WaitForPrimary>false</aml-block:WaitForPrimary></aml-block:BlockGroup><aml-block:Severity>2</aml-block:Severity></aml-block:Header><aml-block:Content><ch:CallHome xmlns:ch="http://www.cisco.com/2005/05/callhome" version="1.0"><ch:EventTime>2009-12-03 12:29:01 GMT+05:00</ch:EventTime><ch:MessageDescription>*Dec 3 12:29:01.017 IST: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console</ch:MessageDescription><ch:Event><ch:Type>syslog</ch:Type><ch:SubType></ch:SubType><ch:Brand>Cisco Systems</ch:Brand><ch:Series>ASR1000 Series Routers</ch:Series></ch:Event><ch:CustomerData><ch:UserData><ch:Email>[email protected]</ch:Email></ch:UserData><ch:ContractData><ch:CustomerId>[email protected]</ch:CustomerId><ch:SiteId>example.com</ch:SiteId><ch:ContractId>123456789</ch:ContractId><ch:DeviceId>ASR1006@C@FOX105101DH</ch:DeviceId></ch:ContractData><ch:SystemInfo><ch:Name>mcp-6ru-3</ch:Name><ch:Contact></ch:Contact><ch:ContactEmail>[email protected]</ch:ContactEmail><ch:ContactPhoneNumber>+14085551234</ch:ContactPhoneNumber><ch:StreetAddress>1234 Any Street Any City Any State 12345</ch:StreetAddress></ch:SystemInfo><ch:CCOID></ch:CCOID></ch:CustomerData><ch:Device><rme:Chassis xmlns:rme="http://www.cisco.com/rme/4.0"><rme:Model>ASR1006</rme:Model><rme:HardwareVersion>2.1</rme:HardwareVersion><rme:SerialNumber>FOX105101DH</rme:SerialNumber><rme:AdditionalInformation><rme:AD name="PartNumber" value="68-2584-05" /><rme:AD name="SoftwareVersion" value="" /><rme:AD name="SystemObjectId" value="1.3.6.1.4.1.9.1.925" /><rme:AD name="SystemDescription" value="Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Experimental Version 12.2(20091118:075558) [v122_33_xnf_asr_rls6_throttle-mcp_dev_rls6 102]Copyright (c) 1986-2009 by Cisco Systems, Inc.Compiled Wed 18-Nov-09 01:14 by " /></rme:AdditionalInformation></rme:Chassis>


OL-16506-08


</ch:Device></ch:CallHome></aml-block:Content><aml-block:Attachments><aml-block:Attachment type="inline"><aml-block:Name>show logging</aml-block:Name><aml-block:Data encoding="plain"><![CDATA[Syslog logging: enabled (1 messages dropped, 29 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

Console logging: disabled Monitor logging: level debugging, 0 messages logged, xml disabled, filtering disabled Buffer logging: level debugging, 114 messages logged, xml disabled, filtering disabled Exception Logging: size (4096 bytes) Count and timestamp logging messages: disabled Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 106 message lines logged

Log Buffer (1000000 bytes):

*Dec 3 07:16:55.020: ASR1000-RP HA: RF status CID 1340, seq 93, status RF_STATUS_REDUNDANCY_MODE_CHANGE, op 0, state DISABLED, peer DISABLED*Dec 3 07:17:00.379: %ASR1000_MGMTVRF-6-CREATE_SUCCESS_INFO: Management vrf Mgmt-intf created with ID 4085, ipv4 table-id 0xFF5, ipv6 table-id 0x1E000001*Dec 3 07:17:00.398: %NETCLK-5-NETCLK_MODE_CHANGE: Network clock source not available. The network clock has changed to freerun

*Dec 3 07:17:00.544: %LINEPROTO-5-UPDOWN: Line protocol on Interface LI-Null0, changed state to up*Dec 3 07:17:00.545: %LINK-3-UPDOWN: Interface EOBC0, changed state to up*Dec 3 07:17:00.545: %LINK-3-UPDOWN: Interface Lsmpi0, changed state to up*Dec 3 07:17:00.546: %LINK-3-UPDOWN: Interface LIIN0, changed state to up*Dec 3 07:17:00.546: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to down*Dec 3 07:17:01.557: %LINEPROTO-5-UPDOWN: Line protocol on Interface EOBC0, changed state to up*Dec 3 07:17:01.557: %LINEPROTO-5-UPDOWN: Line protocol on Interface Lsmpi0, changed state to up*Dec 3 07:17:01.558: %LINEPROTO-5-UPDOWN: Line protocol on Interface LIIN0, changed state to up*Dec 3 07:17:01.558: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down*Dec 3 07:17:01.818: %DYNCMD-7-CMDSET_LOADED: The Dynamic Command set has been loaded from the Shell Manager*Dec 3 07:16:30.926: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 2 is pre-release hardware*Dec 3 07:16:24.147: %HW_IDPROM_ENVMON-3-HW_IDPROM_CHECKSUM_INVALID: F1: cman_fp: The idprom contains an invalid checksum in a sensor entry. Expected: 63, calculated: fe*Dec 3 07:16:24.176: %CMFP-3-IDPROM_SENSOR: F1: cman_fp: One or more sensor fields from the idprom failed to parse properly because Success.*Dec 3 07:16:27.669: %CPPHA-7-START: F1: cpp_ha: CPP 0 preparing image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode


OL-16506-08


*Dec 3 07:16:27.839: %CPPHA-7-START: F1: cpp_ha: CPP 0 startup init image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode*Dec 3 07:16:28.659: %CPPHA-7-START: F0: cpp_ha: CPP 0 preparing image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode*Dec 3 07:16:28.799: %CPPHA-7-START: F0: cpp_ha: CPP 0 startup init image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode*Dec 3 07:16:32.557: %CPPHA-7-START: F1: cpp_ha: CPP 0 running init image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode*Dec 3 07:16:32.812: %CPPHA-7-READY: F1: cpp_ha: CPP 0 loading and initialization complete*Dec 3 07:16:33.532: %CPPHA-7-START: F0: cpp_ha: CPP 0 running init image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode*Dec 3 07:16:33.786: %CPPHA-7-READY: F0: cpp_ha: CPP 0 loading and initialization complete*Dec 3 07:16:34.158: %IOSXE-6-PLATFORM: F1: cpp_cp: Process CPP_PFILTER_EA_EVENT__API_CALL__REGISTER*Dec 3 07:16:35.134: %IOSXE-6-PLATFORM: F0: cpp_cp: Process CPP_PFILTER_EA_EVENT__API_CALL__REGISTER*Dec 3 07:16:38.965: %CMRP-6-FP_HA_STATUS: R0/0: cmand: F0 redundancy state is Active with ready Standby*Dec 3 07:17:01.926: %DYNCMD-7-PKGINT_INSTALLED: The command package 'platform_trace' has been succesfully installed*Dec 3 12:17:05.385 IST: %SYS-6-CLOCKUPDATE: System clock has been updated from 07:17:05 UTC Thu Dec 3 2009 to 12:17:05 IST Thu Dec 3 2009, configured from console by console.*Dec 3 12:17:05.506 IST: %SYS-5-CONFIG_I: Configured from memory by console*Dec 3 12:17:05.508 IST: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/2, interfaces disabled*Dec 3 12:17:05.508 IST: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/3, interfaces disabled*Dec 3 12:17:05.508 IST: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 2/3, interfaces disabled*Dec 3 12:17:05.514 IST: %SPA_OIR-6-OFFLINECARD: SPA (SPA-8XOC3-POS) offline in subslot 0/2*Dec 3 12:17:05.515 IST: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4XOC3-POS) offline in subslot 1/3*Dec 3 12:17:05.516 IST: %SPA_OIR-6-OFFLINECARD: SPA (SPA-1XOC12-POS) offline in subslot 2/3*Dec 3 12:17:05.520 IST: %ASR1000_OIR-6-INSCARD: Card (rp) inserted in slot R1*Dec 3 12:17:05.521 IST: %ASR1000_OIR-6-INSCARD: Card (fp) inserted in slot F0*Dec 3 12:17:05.521 IST: %ASR1000_OIR-6-ONLINECARD: Card (fp) online in slot F0*Dec 3 12:17:05.574 IST: %ASR1000_OIR-6-INSCARD: Card (fp) inserted in slot F1*Dec 3 12:17:05.574 IST: %ASR1000_OIR-6-ONLINECARD: Card (fp) online in slot F1*Dec 3 12:17:05.575 IST: %ASR1000_OIR-6-INSCARD: Card (cc) inserted in slot 0*Dec 3 12:17:05.575 IST: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 0*Dec 3 12:17:05.576 IST: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/2*Dec 3 12:17:05.580 IST: %ASR1000_OIR-6-INSCARD: Card (cc) inserted in slot 1*Dec 3 12:17:05.581 IST: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 1*Dec 3 12:17:05.582 IST: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/3*Dec 3 12:17:05.582 IST: %ASR1000_OIR-6-INSCARD: Card (cc) inserted in slot 2*Dec 3 12:17:05.582 IST: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 2*Dec 3 12:17:05.583 IST: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 2/3*Dec 3 12:17:05.844 IST: %SYS-5-RESTART: System restarted --Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Experimental Version 12.2(20091118:075558) [v122_33_xnf_asr_rls6_throttle-mcp_dev_rls6 102]Copyright (c) 1986-2009 by Cisco Systems, Inc.Compiled Wed 18-Nov-09 01:14 by *Dec 3 12:17:06.005 IST: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF*Dec 3 12:17:06.005 IST: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF*Dec 3 12:16:30.097 IST: %LINK-3-UPDOWN: SIP2/3: Interface EOBC2/1, changed state to up*Dec 3 12:16:27.595 IST: %LINK-3-UPDOWN: SIP0/2: Interface EOBC0/1, changed state to up*Dec 3 12:16:26.420 IST: %LINK-3-UPDOWN: SIP1/3: Interface EOBC1/1, changed state to up*Dec 3 12:17:07.435 IST: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF*Dec 3 12:17:07.435 IST: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF*Dec 3 12:17:07.476 IST: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up


OL-16506-08


*Dec 3 12:17:08.137 IST: %SPA_OIR-6-ONLINECARD: SPA (SPA-4XOC3-POS) online in subslot 1/3*Dec 3 12:17:08.139 IST: %SPA_OIR-6-ONLINECARD: SPA (SPA-8XOC3-POS) online in subslot 0/2*Dec 3 12:17:08.346 IST: %SPA_OIR-6-ONLINECARD: SPA (SPA-1XOC12-POS) online in subslot 2/3*Dec 3 12:17:08.491 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up*Dec 3 12:17:11.047 IST: %SYS-6-BOOTTIME: Time taken to reboot after reload = 12319 seconds*Dec 3 12:17:11.562 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[879]: xinetd Version 2.3.14 started with no options compiled in.*Dec 3 12:17:11.562 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[879]: Started working: 1 available service*Dec 3 12:17:11.584 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[887]: xinetd Version 2.3.14 started with no options compiled in.*Dec 3 12:17:11.584 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[887]: Started working: 2 available services*Dec 3 12:17:13.753 IST: %LINK-3-UPDOWN: Interface POS0/2/0, changed state to down*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/1, changed state to down*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/2, changed state to down*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/3, changed state to down*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/4, changed state to down*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/5, changed state to down*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS0/2/6, changed state to down*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS0/2/7, changed state to down*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS2/3/0, changed state to down*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS1/3/0, changed state to down*Dec 3 12:17:14.753 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/0, changed state to down*Dec 3 12:17:14.753 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/1, changed state to down*Dec 3 12:17:14.753 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/2, changed state to down*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/3, changed state to down*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/4, changed state to down*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/5, changed state to down*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/6, changed state to down*Dec 3 12:17:14.755 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/7, changed state to down*Dec 3 12:17:14.848 IST: %SONET-4-ALARM: POS0/2/1: SLOS declared*Dec 3 12:17:14.848 IST: %SONET-4-ALARM: POS0/2/2: SLOS declared*Dec 3 12:17:14.849 IST: %SONET-4-ALARM: POS0/2/3: SLOS declared*Dec 3 12:17:14.849 IST: %SONET-4-ALARM: POS0/2/4: SLOS declared*Dec 3 12:17:14.849 IST: %SONET-4-ALARM: POS0/2/5: SLOS declared*Dec 3 12:17:14.850 IST: %SONET-4-ALARM: POS0/2/6: SLOS declared*Dec 3 12:17:14.850 IST: %SONET-4-ALARM: POS0/2/7: SLOS declared*Dec 3 12:17:14.850 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS2/3/0, changed state to down*Dec 3 12:17:14.851 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS1/3/0, changed state to down*Dec 3 12:17:16.069 IST: %LINK-3-UPDOWN: Interface POS0/2/0, changed state to up*Dec 3 12:17:15.734 IST: %LINK-3-UPDOWN: SIP0/2: Interface POS0/2/0, changed state to up*Dec 3 12:17:16.868 IST: %LINK-3-UPDOWN: Interface POS1/3/0, changed state to up*Dec 3 12:17:16.905 IST: %LINK-3-UPDOWN: Interface POS2/3/0, changed state to up*Dec 3 12:17:16.538 IST: %LINK-3-UPDOWN: SIP0/2: Interface POS0/2/7, changed state to down*Dec 3 12:17:17.070 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/0, changed state to up*Dec 3 12:17:16.488 IST: %LINK-3-UPDOWN: SIP1/3: Interface POS1/3/0, changed state to up*Dec 3 12:17:17.868 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS1/3/0, changed state to up


OL-16506-08


*Dec 3 12:17:16.199 IST: %LINK-3-UPDOWN: SIP2/3: Interface POS2/3/0, changed state to up*Dec 3 12:17:17.905 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS2/3/0, changed state to up*Dec 3 12:22:01.574 IST: %IP-4-DUPADDR: Duplicate address 172.27.55.233 on GigabitEthernet0, sourced by 001a.3044.1ec0*Dec 3 12:23:47.613 IST: %SYS-5-CONFIG_I: Configured from console by console*Dec 3 12:24:37.134 IST: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console*Dec 3 12:25:34.356 IST: %DIAG-3-TEST_FAIL: slot R0: TestErrorCounterMonitor{ID=1} has failed. Error code = 0x1 (DIAG_FAILURE)*Dec 3 12:25:39.459 IST: %DIAG-3-TEST_FAIL: slot R0: TestErrorCounterMonitor{ID=1} has failed. Error code = 0x1 (DIAG_FAILURE)*Dec 3 12:25:54.405 IST: %SYS-5-CONFIG_I: Configured from console by console*Dec 3 12:26:02.319 IST: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console*Dec 3 12:28:56.057 IST: %SYS-5-CONFIG_I: Configured from console by consolemcp-6ru-3#]]></aml-block:Data></aml-block:Attachment><aml-block:Attachment type="inline"><aml-block:Name>show inventory</aml-block:Name><aml-block:Data encoding="plain"><![CDATA[NAME: "Chassis", DESCR: "Cisco ASR1006 Chassis"PID: ASR1006 , VID: V00, SN: FOX105101DH

NAME: "module 0", DESCR: "Cisco ASR1000 SPA Interface Processor 10"PID: MCP-CC , VID: V00, SN: JAB1104064W

NAME: "SPA subslot 0/2", DESCR: "8-port OC3/STM1 POS Shared Port Adapter"PID: SPA-8XOC3-POS , VID: V01, SN: JAE1236TSW0


NAME: "module 1", DESCR: "Cisco ASR1000 SPA Interface Processor 10"PID: MCP-CC , VID: V00, SN: JAB1104062X

NAME: "SPA subslot 1/3", DESCR: "4-port OC3/STM1 POS Shared Port Adapter"PID: SPA-4XOC3-POS , VID: V01, SN: JAB085202QU


NAME: "module 2", DESCR: "Cisco ASR1000 SPA Interface Processor 10"PID: ASR1000-SIP10 , VID: V00, SN: JAB113701L9

NAME: "SPA subslot 2/3", DESCR: "1-port OC12/STM4 POS Shared Port Adapter"PID: SPA-1XOC12-POS , VID: V01, SN: JAE1236U41L


NAME: "module R0", DESCR: "Cisco ASR1000 Route Processor 1"PID: ASR1000-RP1 , VID: V00, SN: JAB11110181

NAME: "module R1", DESCR: "Cisco ASR1000 Route Processor 1"PID: ASR1000-RP1 , VID: V00, SN: JAB1111016K

NAME: "module F0", DESCR: "Cisco ASR1000 Embedded Services Processor, 10Gbps"PID: ASR1000-ESP10 , VID: V00, SN: JAB111801ZX

NAME: "module F1", DESCR: "Cisco ASR1000 Embedded Services Processor, 10Gbps"PID: ASR1000-ESP10 , VID: V00, SN: JAB111101AP

NAME: "Power Supply Module 0", DESCR: "Cisco ASR1006 AC Power Supply"PID: TBD000000000000000, VID: +Â , SN: ART1114Q00F


OL-16506-08

Chapter 6 Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers Additional References

NAME: "Fan Module 1", DESCR: "Cisco ASR1006 Fan Module"PID: TBD000000000000000, VID: +Â , SN: ART1115P00D

Router#]]></aml-block:Data></aml-block:Attachment></aml-block:Attachments></aml-block:Block></soap-env:Body></soap-env:Envelope>

Additional ReferencesThe following sections provide references related to the Call Home feature.

Related Documents

Standards

Related Topic Document Title

Cisco IOS XE commands Cisco IOS Master Commands List, All Releases

Explains how the Smart Call Home service offers web-based access to important information on select Cisco devices and offers higher network availability, and increased operational efficiency by providing proactive diagnostics and real-time alerts.

Smart Call Home User Guide

Smart Call Home site page on Cisco.com for access to all related product information.

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

Public Key Infrastructure (PKI) and Certificate Authority configuration in Cisco IOS XE software

Cisco IOS XE Security Configuration Guide: Secure Connectivity

Standard Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

—


OL-16506-08

http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html


http://www.cisco.com

http://www.cisco.com/en/US/docs/ios/ios_xe/sec_secure_connectivity/configuration/guide/2_xe/sec_secure_connectivity_xe_book.html

Chapter 6 Configuring Call Home for Cisco ASR 1000 Series Aggregation Services Routers Feature Information for Call Home

MIBs

RFCs

Technical Assistance

Feature Information for Call HomeTable 8 lists the release history for this feature on the Cisco ASR 1000 Series Routers.

For information on a feature in this technology that is not documented here, see the Cisco ASR 1000 Series Aggregation Services Routers Documentation Roadmap.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 8 lists only the Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.

MIB MIBs Link

CISCO-CALLHOME-MIB To locate and download MIBs for selected platforms, Cisco IOS XE software releases, and feature sets, use Cisco MIB Locator found at the following URL:

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

RFC Title

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.

—

Description Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/cisco/web/support/index.html


OL-16506-08

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

http://www.cisco.com/cisco/web/support/index.html

http://www.cisco.com/en/US/docs/routers/asr1000/roadmap/asr1000rm.html

http://www.cisco.com/en/US/docs/routers/asr1000/roadmap/asr1000rm.html




Table 8 Feature Information for Call Home

Feature Name Releases Feature Information

Call Home IOS XE Release 2.6

Call Home provides e-mail-based and web-based notification of critical system events. A versatile range of message formats are available for optimal compatibility with pager services, standard e-mail, or XML-based automated parsing applications.

In Cisco IOS XE Release 2.6, support for this feature was added for the Cisco ASR 1000 Series Aggregation Services Routers.

The following commands are new or modified: show diagnostic commands.


OL-16506-08



OL-16506-08


C H A P T E R 7
Console Port, Telnet, and SSH Handling
This chapter covers the following topics:

• Console Port Overview for the Cisco ASR 1000 Series Routers, page 7-1

• Console Port Handling Overview, page 7-1

• Telnet and SSH Overview for the Cisco ASR 1000 Series Routers, page 7-2

• Persistent Telnet and Persistent SSH Overview, page 7-2

• Configuring a Console Port Transport Map, page 7-2

• Configuring Persistent Telnet, page 7-5

• Configuring Persistent SSH, page 7-9

• Viewing Console Port, SSH, and Telnet Handling Configurations, page 7-12

• Important Notes and Restrictions, page 7-17

Console Port Overview for the Cisco ASR 1000 Series RoutersThe console port on the Cisco ASR 1000 Series Router is an EIA/TIA-232 asynchronous, serial connection with no flow control and an RJ-45 connector. The console port is used to access the router and is located on the front panel of the Route Processor (RP).

For information on accessing the router using the console port, see the “Accessing the CLI Using a Directly-Connected Console” section on page 2-1.

Console Port Handling OverviewUsers using the console port to access the router are automatically directed to the IOS command-line interface, by default.

If a user is trying to access the router through the console port and sends a break signal (a break signal can be sent by entering Ctrl-C or Ctrl-Shift-6, or by entering the send break command at the Telnet prompt) before connecting to the IOS command-line interface, the user is directed intodiagnostic mode by default if the non-RPIOS sub-packages can be accessed.

These settings can be changed by configuring a transport map for the console port and applying that transport map to the console interface.


Chapter 7 Console Port, Telnet, and SSH Handling Telnet and SSH Overview for the Cisco ASR 1000 Series Routers

Telnet and SSH Overview for the Cisco ASR 1000 Series RoutersTelnet and Secure Shell (SSH) on the Cisco ASR 1000 Series Routers can be configured and handled like Telnet and SSH on other Cisco platforms. For information on traditional Telnet and SSH handling, see the line command reference for information on configuring Telnet and the”Configuring Secure Shell” chapter of the Cisco IOS Security Configuration Guide for information on configuring traditional SSH.

The Cisco ASR 1000 Series Routers also introduces persistent Telnet and persistent SSH. Persistent Telnet and persistent SSH allow network administrators to more clearly define the treatment of incoming traffic when users access the router through the Management Ethernet port using Telnet or SSH. Notably, persistent Telnet and persistent SSH provide more robust network access by allowing the router to be configured to be accessible through the Ethernet Management port using Telnet or SSH even when the IOS process has failed.

Persistent Telnet and Persistent SSH OverviewIn traditional Cisco routers, accessing the router using Telnet or SSH is not possible in the event of an IOS failure. When Cisco IOS fails on a traditional Cisco router, the only method of accessing the router is through the console port. Similarly, if all active IOS processes have failed on a Cisco ASR 1000 Series Router that is not using persistent Telnet or persistent SSH, the only method of accessing the router is through the console port.

With persistent Telnet and persistent SSH, however, users can configure a transport map that defines the treatment of incoming Telnet or SSH traffic on the Management Ethernet interface. Among the many configuration options, a transport map can be configured to direct all traffic to the IOS command-line interface, diagnostic mode, or to wait for an IOS vty line to become available and then direct users into diagnostic mode when the user sends a break signal while waiting for the IOS vty line to become available. If a user uses Telnet or SSH to access diagnostic mode, that Telnet or SSH connection will be usable even in scenarios when no IOS process is active. Therefore, persistent Telnet and persistent SSH introduce the ability to access the router via diagnostic mode when the IOS process is not active. For information on diagnostic mode, see the “Understanding Diagnostic Mode” section on page 2-8.

See the “Configuring Persistent Telnet” section on page 7-5 and the “Configuring Persistent SSH” section on page 7-9 for information on the various other options that are configurable using persistent Telnet or persistent SSH transport maps.

Configuring a Console Port Transport MapThis task describes how to configure a transport map for a console port interface on the Cisco ASR 1000 Series Router.

SUMMARY STEPS

1. (Required) enable

2. (Required) configure terminal

3. (Required) transport-map type console transport-map-name

4. (Required) connection wait [allow interruptible | none {disconnect}]

5. (Optional) banner [diagnostic | wait] banner-message

6. (Required) exit


OL-16506-08

http://www.cisco.com/en/US/docs/ios/12_2/termserv/command/reference/trflosho.html#wp1029818

http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca7d5.html

http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_book09186a0080087df1.html

Chapter 7 Console Port, Telnet, and SSH Handling Configuring a Console Port Transport Map

7. (Required) transport type console console-line-number input transport-map-name


OL-16506-08

Chapter 7 Console Port, Telnet, and SSH Handling Configuring a Console Port Transport Map

DETAILED STEPS


Step 1 enable

Example:Router> enable

Enables privileged EXEC mode.

• Enter your password if prompted.




Step 3 transport-map type console transport-map-name

Example:Router(config)# transport-map type console consolehandler

Creates and names a transport map for handling console connections, and enter transport map configuration mode.

Step 4 connection wait [allow interruptible | none]

Example:Router(config-tmap)# connection wait none

Specifies how a console connection will be handled using this transport map:

• allow interruptible—The console connection waits for an IOS vty line to become available, and also allows user to enter diagnostic mode by interrupting a console connection waiting for the IOS vty line to become available. This is the default setting.

Note Users can interrupt a waiting connection by entering Ctrl-C or Ctrl-Shift-6.

• none—The console connection immediately enters diagnostic mode.

Step 5 banner [diagnostic | wait] banner-message

Example:Router(config-tmap)# banner diagnostic XEnter TEXT message. End with the character 'X'.--Welcome to Diagnostic Mode--XRouter(config-tmap)#

(Optional) Creates a banner message that will be seen by users entering diagnostic mode or waiting for the IOS vty line as a result of the console transport map configuration.

• diagnostic—Creates a banner message seen by users directed into diagnostic mode as a result of the console transport map configuration.

• wait—Creates a banner message seen by users waiting for the IOS vty to become available.

• banner-message—The banner message, which begins and ends with the same delimiting character.


OL-16506-08

Chapter 7 Console Port, Telnet, and SSH Handling Configuring Persistent Telnet

ExamplesIn the following example, a transport map to set console port access policies is created and attached to console port 0:

Router(config)# transport-map type console consolehandlerRouter(config-tmap)# connection wait allow interruptibleRouter(config-tmap)# banner diagnostic XEnter TEXT message. End with the character 'X'.Welcome to diagnostic modeXRouter(config-tmap)# banner wait X Enter TEXT message. End with the character 'X'.Waiting for IOS vty lineXRouter(config-tmap)# exit

Router(config)# transport type console 0 input consolehandler

Configuring Persistent TelnetThis task describes how to configure persistent Telnet on the Cisco ASR 1000 Series Routers.

PrerequisitesFor a persistent Telnet connection to access an IOS vty line on the Cisco ASR 1000 Series Router, local login authentication must be configured for the vty line (the login command in line configuration mode). If local login authentication is not configured, users will not be able to access IOS using a Telnet connection into the Management Ethernet interface with an applied transport map. Diagnostic mode will still be accessible in this scenario.

SUMMARY STEPS



3. (Required) transport-map type persistent telnet transport-map-name

Step 6 exit

Example:Router(config-tmap)# exit

Exits transport map configuration mode to re-enter global configuration mode.

Step 7 transport type console console-line-number input transport-map-name

Example:Router(config)# transport type console 0 input consolehandler

Applies the settings defined in the transport map to the console interface.

The transport-map-name for this command must match the transport-map-name defined in the transport-map type console command.



OL-16506-08


4. (Required) connection wait [allow {interruptible} | none {disconnect}]


6. (Required) transport interface GigabitEthernet 0

7. (Required) exit

8. (Required) transport type persistent telnet input transport-map-name


OL-16506-08


DETAILED STEPS


Step 1 enable







Step 3 transport-map type persistent telnet transport-map-name

Example:Router(config)# transport-map type persistent telnet telnethandler

Creates and names a transport map for handling persistent Telnet connections, and enters transport map configuration mode.

Step 4 connection wait [allow {interruptible}| none {disconnect}]

Example:Router(config-tmap)# connection wait none

Specifies how a persistent Telnet connection will be handled using this transport map:

• allow—The Telnet connection waits for an IOS vty line to become available, and exits the router if interrupted.

• allow interruptible—The Telnet connection waits for the IOS vty line to become available, and also allows user to enter diagnostic mode by interrupting a Telnet connection waiting for the IOS vty line to become available. This is the default setting.


• none—The Telnet connection immediately enters diagnostic mode.

• none disconnect—The Telnet connection does not wait for the IOS vty line and does not enter diagnostic mode, so all Telnet connections are rejected if no vty line is immediately available in IOS.



(Optional) Creates a banner message that will be seen by users entering diagnostic mode or waiting for the IOS vty line as a result of the persistent Telnet configuration.

• diagnostic—creates a banner message seen by users directed into diagnostic mode as a result of the persistent Telnet configuration.

• wait—creates a banner message seen by users waiting for the vty line to become available.

• banner-message—the banner message, which begins and ends with the same delimiting character.


OL-16506-08


ExamplesIn the following example, a transport map that will make all Telnet connections wait for an IOS vty line to become available before connecting to the router, while also allowing the user to interrupt the process and enter diagnostic mode, is configured and applied to the Management Ethernet interface (interface gigabitethernet 0).

A diagnostic and a wait banner are also configured.

The transport map is then applied to the interface when the transport type persistent telnet input command is entered to enable persistent Telnet.

Router(config)# transport-map type persistent telnet telnethandlerRouter(config-tmap)# connection wait allow interruptibleRouter(config-tmap)# banner diagnostic XEnter TEXT message. End with the character 'X'.--Welcome to Diagnostic Mode--XRouter(config-tmap)# banner wait XEnter TEXT message. End with the character 'X'.--Waiting for IOS Process--X

Router(config-tmap)# transport interface gigabitethernet 0Router(config-tmap)# exitRouter(config)# transport type persistent telnet input telnethandler

Step 6 transport interface gigabitethernet 0

Example:Router(config-tmap)# transport interface gigabitethernet 0

Applies the transport map settings to the Management Ethernet interface (interface gigabitethernet 0).

Persistent Telnet can only be applied to the Management Ethernet interface on the Cisco ASR 1000 Series Routers. This step must be taken before applying the transport map to the Management Ethernet interface.

Step 7 exit



Step 8 transport type persistent telnet input transport-map-name

Example:Router(config)# transport type persistent telnet input telnethandler

Applies the settings defined in the transport map to the Management Ethernet interface.

The transport-map-name for this command must match the transport-map-name defined in the transport-map type persistent telnet command.



OL-16506-08

Chapter 7 Console Port, Telnet, and SSH Handling Configuring Persistent SSH

Configuring Persistent SSHThis task describes how to configure persistent SSH on the Cisco ASR 1000 Series Routers.

SUMMARY STEPS



3. (Required) transport-map type persistent ssh transport-map-name

4. (Required) connection wait [allow {interruptible} | none {disconnect}]

5. (Required) rsa keypair-name rsa-keypair-name

6. (Optional) authentication-retries number-of-retries


8. (Optional) time-out timeout-interval-in-seconds

9. (Required) transport interface GigabitEthernet 0

10. (Required) exit

11. (Required) transport type persistent ssh input transport-map-name


OL-16506-08


DETAILED STEPS


Step 1 enable







Step 3 transport-map type persistent ssh transport-map-name

Example:Router(config)# transport-map type persistent ssh sshhandler

Creates and names a transport map for handling persistent SSH connections, and enters transport map configuration mode.

Step 4 connection wait [allow {interruptible}| none {disconnect}]

Example:Router(config-tmap)# connection wait allow interruptible

Specifies how a persistent SSH connection will be handled using this transport map:

• allow—The SSH connection waits for the vty line to become available, and exits the router if interrupted.

• allow interruptible—The SSH connection waits for the vty line to become available, and also allows users to enter diagnostic mode by interrupting a SSH connection waiting for the vty line to become available. This is the default setting.


• none—The SSH connection immediately enters diagnostic mode.

• none disconnect—The SSH connection does not wait for the vty line from IOS and does not enter diagnostic mode, so all SSH connections are rejected if no vty line is immediately available.

Step 5 rsa keypair-name rsa-keypair-name

Example:Router(config-tmap)# rsa keypair-name sshkeys

Names the RSA keypair to be used for persistent SSH connections.

For persistent SSH connections, the RSA keypair name must be defined using this command in transport map configuration mode. The RSA keypair definitions defined elsewhere on the router, such as through the use of the ip ssh rsa keypair-name command, do not apply to persistent SSH connections.

No rsa-keypair-name is defined by default.


OL-16506-08


ExamplesIn the following example, a transport map that will make all SSH connections wait for the vty line to become active before connecting to the router is configured and applied to the Management Ethernet interface (interface gigabitethernet 0). The RSA keypair is named sshkeys.

This example only uses the commands required to configure persistent SSH.

Router(config)# transport-map type persistent ssh sshhandlerRouter(config-tmap)# connection wait allowRouter(config-tmap)# rsa keypair-name sshkeysRouter(config-tmap)# transport interface gigabitethernet 0

Step 6 authentication-retries number-of-retries

Example:Router(config-tmap)# authentication-retries 4

(Optional) Specifies the number of authentication retries before dropping the connection.

The default number-of-retries is 3.



(Optional) Creates a banner message that will be seen by users entering diagnostic mode or waiting for the vty line as a result of the persistent SSH configuration.

• diagnostic—Creates a banner message seen by users directed into diagnostic mode as a result of the persistent SSH configuration.

• wait—Creates a banner message seen by users waiting for the vty line to become active.

• banner-message—The banner message, which begins and ends with the same delimiting character.

Step 8 time-out timeout-interval

Example:Router(config-tmap)# time-out 30

(Optional) Specifies the SSH time-out interval in seconds.

The default timeout-interval is 120 seconds.

Step 9 transport interface gigabitethernet 0

Example:Router(config-tmap)# transport interface gigabitethernet 0

Applies the transport map settings to the Management Ethernet interface (interface gigabitethernet 0).

Persistent SSH can only be applied to the Management Ethernet interface on the Cisco ASR 1000 Series Routers.

Step 10 exit



Step 11 transport type persistent ssh input transport-map-name

Example:Router(config)# transport type persistent ssh input sshhandler

Applies the settings defined in the transport map to the Management Ethernet interface.

The transport-map-name for this command must match the transport-map-name defined in the transport-map type persistent ssh command.



OL-16506-08

Chapter 7 Console Port, Telnet, and SSH Handling Viewing Console Port, SSH, and Telnet Handling Configurations

In the following example, a transport map is configured that will apply the following settings to any users attempting to access the Management Ethernet port via SSH:

• Users using SSH will wait for the vty line to become active, but will enter diagnostic mode if the attempt to access IOS through the vty line is interrupted.

• The RSA keypair name is “sshkeys”

• The connection allows one authentication retry.

• The banner “--Welcome to Diagnostic Mode--” will appear if diagnostic mode is entered as a result of SSH handling through this transport map.

• The banner “--Waiting for vty line--” will appear if the connection is waiting for the vty line to become active.

The transport map is then applied to the interface when the transport type persistent ssh input command is entered to enable persistent SSH.

Router(config)# transport-map type persistent ssh sshhandlerRouter(config-tmap)# connection wait allow interruptibleRouter(config-tmap)# rsa keypair-name sshkeysRouter(config-tmap)# authentication-retries 1Router(config-tmap)# banner diagnostic XEnter TEXT message. End with the character 'X'.--Welcome to Diagnostic Mode--XRouter(config-tmap)#banner wait XEnter TEXT message. End with the character 'X'.--Waiting for vty line--XRouter(config-tmap)# time-out 30Router(config-tmap)# transport interface gigabitethernet 0Router(config-tmap)# exit

Router(config)# transport type persistent ssh input sshhandler

Viewing Console Port, SSH, and Telnet Handling ConfigurationsUse the show transport-map [all | name transport-map-name | type [console | persistent [ssh | telnet]]] EXEC or privileged EXEC command to view the transport map configurations.

In the following example, a console port, persistent SSH, and persistent Telnet transport are configured on the router and various forms of the show transport-map command are entered to illustrate the various ways the show transport-map command can be entered to gather transport map configuration information.

Router# show transport-map allTransport Map: Name: consolehandler Type: Console Transport

Connection: Wait option: Wait Allow Interruptable Wait banner:

Waiting for the IOS CLI

bshell banner:

Welcome to Diagnostic Mode


OL-16506-08


Transport Map: Name: sshhandler Type: Persistent SSH Transport

Interface: GigabitEthernet0


Waiting for IOS prompt

Bshell banner: Welcome to Diagnostic Mode

SSH: Timeout: 120 Authentication retries: 5 RSA keypair: sshkeys

Transport Map: Name: telnethandler Type: Persistent Telnet Transport



Waiting for IOS process

Bshell banner:


Transport Map: Name: telnethandling1 Type: Persistent Telnet Transport

Connection: Wait option: Wait Allow

Router# show transport-map type consoleTransport Map: Name: consolehandler Type: Console Transport



Bshell banner:



OL-16506-08


Router# show transport-map type persistent sshTransport Map: Name: sshhandler Type: Persistent SSH Transport




Bshell banner:



Router# show transport-map type persistent telnet Transport Map: Name: telnethandler Type: Persistent Telnet Transport




Bshell banner:


Transport Map: Name: telnethandling1 Type: Persistent Telnet Transport

Connection: Wait option: Wait Allow

Router# show transport-map name telnethandler Transport Map: Name: telnethandler Type: Persistent Telnet Transport




OL-16506-08



Bshell banner:


Router# show transport-map name consolehandlerTransport Map: Name: consolehandler Type: Console Transport



Bshell banner:


Router# show transport-map name sshhandlerTransport Map: Name: sshhandler Type: Persistent SSH Transport




Bshell banner:



Router#

The show platform software configuration access policy command can be used to view the current configurations for the handling of incoming console port, SSH, and Telnet connections. The output of this command provides the current wait policy for each type of connection, as well as any information on the currently configured banners. Unlike show transport-map, this command is available in diagnostic mode so it can be entered in cases when you need transport map configuration information but cannot access the IOS CLI.

Router# show platform software configuration access policy The current access-policies

Method : telnetRule : waitShell banner:


OL-16506-08


Wait banner :

Method : sshRule : waitShell banner: Wait banner :

Method : consoleRule : wait with interruptShell banner: Wait banner :

In the following example, the connection policy and banners are set for a persistent SSH transport map, and the transport map is enabled.

The show platform software configuration access policy output is given both before the new transport map is enabled and after the transport map is enabled so the changes to the SSH configuration are illustrated in the output.

Router# show platform software configuration access policy The current access-policies

Method : telnetRule : wait with interruptShell banner: Welcome to Diagnostic Mode

Wait banner : Waiting for IOS Process

Method : sshRule : waitShell banner: Wait banner :


Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.

Router(config)# transport-map type persistent ssh sshhandlerRouter(config-tmap)# connection wait allow interruptibleRouter(config-tmap)# banner diagnostic XEnter TEXT message. End with the character 'X'.Welcome to Diag ModeXRouter(config-tmap)# banner wait XEnter TEXT message. End with the character 'X'.Waiting for IOSXRouter(config-tmap)# rsa keypair-name sshkeysRouter(config-tmap)# transport interface gigabitethernet 0Router(config-tmap)# exit

Router(config)# transport type persistent ssh input sshhandler Router(config)# exit

Router# show platform software configuration access policyThe current access-policies


OL-16506-08

Chapter 7 Console Port, Telnet, and SSH Handling Important Notes and Restrictions

Method : telnetRule : wait with interruptShell banner: Welcome to Diagnostic Mode

Wait banner : Waiting for IOS process

Method : sshRule : wait with interruptShell banner: Welcome to Diag Mode

Wait banner : Waiting for IOS


Important Notes and Restrictions • The Telnet and SSH settings made in the transport map override any other Telnet or SSH settings

when the transport map is applied to the Management Ethernet interface.

• Only local usernames and passwords can be used to authenticate users entering a Management Ethernet interface. AAA authentication is not available for users accessing the router through a Management Ethernet interface using persistent Telnet or persistent SSH.

• Applying a transport map to a Management Ethernet interface with active Telnet or SSH sessions can disconnect the active sessions. Removing a transport map from an interface, however, does not disconnect any active Telnet or SSH sessions.

• Configuring the diagnostic and wait banners is optional but recommended. The banners are especially useful as indicators to users of the status of their Telnet or SSH attempts.


OL-16506-08

Chapter 7 Console Port, Telnet, and SSH Handling Important Notes and Restrictions


OL-16506-08


C H A P T E R 8
Using the Management Ethernet Interface

• Gigabit Ethernet Management Interface Overview, page 8-1

• Gigabit Ethernet Port Numbering, page 8-2

• Gigabit Ethernet Port Numbering, page 8-2

• IP Address Handling in ROMmon and the Management Ethernet Port, page 8-2

• Gigabit Ethernet Management Interface VRF, page 8-2

• Common Ethernet Management Tasks, page 8-3

Gigabit Ethernet Management Interface OverviewThe Cisco ASR 1000 Series Routers have one Gigabit Ethernet Management Ethernet interface on each Route Processor.

The purpose of this interface is to allow users to perform management tasks on the router; it is basically an interface that should not and often cannot forward network traffic but can otherwise access the router, often via Telnet and SSH, and perform most management tasks on the router. The interface is most useful before a router has begun routing, or in troubleshooting scenarios when the SPA interfaces are inactive.

The following aspects of the Management Ethernet interface should be noted:

• Each RP has a Management Ethernet interface, but only the active RP has an accessible Management Ethernet interface (the standby RP can be accessed using the console port, however).

• IPv4, IPv6, and ARP are the only routed protocols supported for the interface.

• The interface provides a method of access to the router even if the SPA interfaces or the IOS processes are down.

• The Management Ethernet interface is part of its own VRF. This is discussed in more detail in the “Gigabit Ethernet Management Interface VRF” section on page 8-2.


Chapter 8 Using the Management Ethernet Interface Gigabit Ethernet Port Numbering

Gigabit Ethernet Port NumberingThe Gigabit Ethernet Management port is always GigabitEthernet0.

In a dual RP configuration, the Management Ethernet interface on the active RP will always be Gigabit Ethernet 0, while the Management Ethernet interface on the standby RP will not be accessible using the Cisco IOS CLI in the same telnet session. The standby RP can be telnetted to through the console port, however.

The port can be accessed in configuration mode like any other port on the Cisco ASR 1000 Series Routers.

Router#config tEnter configuration commands, one per line. End with CNTL/Z.Router(config)#interface gigabitethernet0Router(config-if)#

IP Address Handling in ROMmon and the Management Ethernet Port

On the Cisco ASR 1000 Series Routers, IP addresses can be configured in ROMmon (the IP_ADDRESS= and IP_SUBNET_MASK= commands) and through the use of the IOS command-line interface (the ip address command in interface configuration mode).

Assuming the IOS process has not begun running on the Cisco ASR 1000 Series Router, the IP address that was set in ROMmon acts as the IP address of the Management Ethernet interface. In cases where the IOS process is running and has taken control of the Management Ethernet interface, the IP address specified when configuring the Gigabit Ethernet 0 interface in the IOS CLI becomes the IP address of the Management Ethernet interface. The ROMmon-defined IP address is only used as the interface address when the IOS process is inactive.

For this reason, the IP addresses specified in ROMmon and in the IOS CLI can be identical and the Management Ethernet interface will function properly in single RP configurations.

In dual RP configurations, however, users should never configure the IP address in the ROMmon on either RP0 or RP1 to match each other or the IP address as defined by the IOS CLI. Configuring matching IP addresses introduces the possibility for an active and standby Management Ethernet interface having the same IP address with different MAC addresses, which will lead to unpredictable traffic treatment.

Gigabit Ethernet Management Interface VRFThe Gigabit Ethernet Management interface is automatically part of its own VRF. This VRF, which is named “Mgmt-intf,” is automatically configured on the Cisco ASR 1000 Series Router and is dedicated to the Management Ethernet interface; no other interfaces can join this VRF. Therefore, this VRF does not participate in the MPLS VPN VRF or any other network-wide VRF.

Placing the management ethernet interface in its own VRF has the following effects on the Management Ethernet interface:

• Many features must be configured or used inside the VRF, so the CLI may be different for certain Management Ethernet functions on the Cisco ASR 1000 Series Routers than on Management Ethernet interfaces on other routers.


OL-16506-08

Chapter 8 Using the Management Ethernet Interface Common Ethernet Management Tasks

• Prevents transit traffic from traversing the router. Because all of the SPA interfaces and the Management Ethernet interface are automatically in different VRFs, no transit traffic can enter the Management Ethernet interface and leave a SPA interface, or vice versa.

• Improved security of the interface. Because the Mgmt-intf VRF has its own routing table as a result of being in its own VRF, routes can only be added to the routing table of the Management Ethernet interface if explicitly entered by a user.

The Management Ethernet interface VRF supports both IPv4 and IPv6 address families.

Common Ethernet Management TasksBecause users can perform most tasks on a router through the Management Ethernet interface, many tasks can be done by accessing the router through the Management Ethernet interface.

This section documents tasks that might be common or slightly tricky on the Cisco ASR 1000 Series Routers. It is not intended as a comprehensive list of all tasks that can be done using the Management Ethernet interface.

This covers the following processes:

• Viewing the VRF Configuration, page 8-3

• Viewing Detailed VRF Information for the Management Ethernet VRF, page 8-4

• Setting a Default Route in the Management Ethernet Interface VRF, page 8-4

• Setting the Management Ethernet IP Address, page 8-4

• Telnetting over the Management Ethernet Interface, page 8-5

• Pinging over the Management Ethernet Interface, page 8-5

• Copy Using TFTP or FTP, page 8-5

• NTP Server, page 8-5

• SYSLOG Server, page 8-6

• SNMP-related services, page 8-6

• Domain Name Assignment, page 8-6

• DNS service, page 8-6

• RADIUS or TACACS+ Server, page 8-6

• VTY lines with ACL, page 8-7

Viewing the VRF ConfigurationThe VRF configuration for the Management Ethernet interface is viewable using the show running-config vrf command.

This example shows the default VRF configuration:

Router# show running-config vrfBuilding configuration...

Current configuration : 351 bytesvrf definition Mgmt-intf ! address-family ipv4


OL-16506-08


exit-address-family ! address-family ipv6 exit-address-family!(some output removed for brevity)

Viewing Detailed VRF Information for the Management Ethernet VRFTo see detailed information about the Management Ethernet VRF, enter the show vrf detail Mgmt-intf command.

Router# show vrf detail Mgmt-intfVRF Mgmt-intf (VRF Id = 4085); default RD <not set>; default VPNID <not set> Interfaces: Gi0 Address family ipv4 (Table ID = 4085 (0xFF5)): No Export VPN route-target communities No Import VPN route-target communities No import route-map No export route-map VRF label distribution protocol: not configured VRF label allocation mode: per-prefixAddress family ipv6 (Table ID = 503316481 (0x1E000001)): No Export VPN route-target communities No Import VPN route-target communities No import route-map No export route-map VRF label distribution protocol: not configured VRF label allocation mode: per-prefix

Setting a Default Route in the Management Ethernet Interface VRFTo set a default route in the Management Ethernet Interface VRF, enter the following command

ip route vrf Mgmt-intf 0.0.0.0 0.0.0.0 next-hop-IP-address

Setting the Management Ethernet IP AddressThe IP address of the Management Ethernet port is set like the IP address on any other interface.

Below are two simple examples of configuring an IPv4 adress and an IPv6 address on the Management Ethernet interface.

IPv4 ExampleRouter(config)# interface GigabitEthernet 0 Router(config-if)# ip address A.B.C.D A.B.C.D

IPv6 ExampleRouter(config)# interface GigabitEthernet 0 Router(config-if)# ipv6 address X:X:X:X::X


OL-16506-08


Telnetting over the Management Ethernet InterfaceTelnetting can be done through the VRF using the Management Ethernet interface.

In the following example, the router telnets to 172.17.1.1 through the Management Ethernet interface VRF:

Router# telnet 172.17.1.1 /vrf Mgmt-intf

Pinging over the Management Ethernet InterfacePinging other interfaces using the Management Ethernet interface is done through the VRF.

In the following example, the router pings the interface with the IP address of 172.17.1.1 through the Management Ethernet interface.

Router# ping vrf Mgmt-intf 172.17.1.1 Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 172.17.1.1, timeout is 2 seconds:.!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 2/2/3 msg5-20#

Copy Using TFTP or FTPTo copy a file using TFTP through the Management Ethernet interface, the ip tftp source-interface GigabitEthernet 0 command must be entered before entering the copy tftp command because the copy tftp command has no option of specifying a VRF name.

Similarly, to copy a file using FTP through the Management Ethernet interface, the ip ftp source-interface GigabitEthernet 0 command must be entered before entering the copy ftp command because the copy ftp command has no option of specifying a VRF name.

TFTP ExampleRouter(config)# ip tftp source-interface gigabitethernet 0

FTP ExampleRouter(config)# ip ftp source-interface gigabitethernet 0

NTP Server To allow the software clock to be synchronized by a Network Time Protocol (NTP) time server over the Management Ethernet interface, enter the ntp server vrf Mgmt-intf command and specify the IP address of the device providing the update.

The following CLI provides an example of this procedure.

Router(config)# ntp server vrf Mgmt-intf 172.17.1.1


OL-16506-08


SYSLOG Server To specify the Management Ethernet interface as the source IP or IPv6 address for logging purposes, enter the logging source-interface gigabitethernet 0 command.

The following CLI provides an example of this procedure.

Router(config)# logging source-interface gigabitethernet 0

SNMP-related servicesTo specify the Management Ethernet interface as the source of all SNMP trap messages, enter the snmp-server source-interface traps gigabitEthernet 0 command.

The following CLI provides an example of this procedure:

Router(config)# snmp-server source-interface traps gigabitEthernet 0

Domain Name Assignment The IP domain name assignment for the Management Ethernet interface is done through the VRF.

To define the default domain name as the Management Ethernet VRF interface, enter the ip domain-name vrf Mgmt-intf domain command.

Router(config)# ip domain-name vrf Mgmt-intf cisco.com

DNS service To specify the Management Ethernet interface VRF as a name server, enter the ip name-server vrf Mgmt-intf IPv4-or-IPv6-address command.

Router(config)# ip name-server vrf Mgmt-intf IPv4-or-IPv6-address

RADIUS or TACACS+ Server To group the Management VRF as part of a AAA server group, enter the ip vrf forward Mgmt-intf command when configuring the AAA server group.

The same concept is true for configuring a TACACS+ server group. To group the Management VRF as part of a TACACS+ server group, enter the ip vrf forwarding Mgmt-intf command when configuring the TACACS+ server group.

Radius Server Group ConfigurationRouter(config)# aaa group server radius helloRouter(config-sg-radius)# ip vrf forwarding Mgmt-intf

Tacacs+ Server Group Exampleouter(config)# aaa group server tacacs+ helloRouter(config-sg-tacacs+)# ip vrf forwarding Mgmt-intf


OL-16506-08


VTY lines with ACLTo ensure an access control list (ACL) is attached to vty lines that are and are not using VRF, use the vrf-also option when attaching the ACL to the vty lines.

Router(config)# line vty 0 4Router(config-line)# access-class 90 in vrf-also


OL-16506-08



OL-16506-08


C H A P T E R 9
Synchronous Ethernet Support On The Cisco ASR 1000 Series Routers
Synchronous Ethernet (SyncE) defined by the Telecommunication Standardization Sector (ITU-T) standards, such as G.8261 and G.8262, leverages the PHY layer of the Ethernet to transmit clock information to the remote sites. SyncE over Ethernet provides a cost-effective alternative to the Synchronous Optical Networking (SONET) networks. For SyncE to work, each network element along the synchronization path must support SyncE. To implement SyncE, the bit clock of the Ethernet is aligned to a reliable clock that is traceable to the Primary Reference Clock (PRC).

Cisco ASR 1000 Series Routers have a dedicated external interface known as BITs interface to recover clock from a Synchronization Supply Unit (SSU). ASR 1000 router uses this clock for SyncE. The BITS interface supports E1(European SSUs) and T1 (American BITS) framing.

Table 9-1 lists the framing modes for a BITS port on a Cisco ASR 1000 Series Router:

You can implement SyncE on the Cisco ASR 1000 Series Routers, using four different configurations:

• Clock Recovery from SyncE: The system clock is recovered from the SyncE clocking source (gigabit interfaces only). The router uses this clock as the Tx clock for other SyncE interfaces or ATM or CEoP interfaces.

• Clock Recovery from External Interface: The system clock is recovered from a BITS clocking source.

Table 9-1 Framing Modes for a BITS Port on a Cisco ASR 1000 Series Router

BITS or SSU Port Support Matrix

Framing Modes Supported

SSM or QL Support Tx Port Rx Port

T1 T1 ESF Yes Yes Yes

T1 T1 SF No Yes Yes

E1 E1 CRC4 Yes Yes Yes

E1 E1 FAS No Yes Yes

E1 E1 CAS No No Yes

E1 E1 CAS CRC4 Yes No Yes

2048 kHz 2048 kHz No Yes Yes



• Line to External: The clock received from an Ethernet is forwarded to an external SSU. The SyncE feature provides the clock cleanup functionality. For a router in the middle of a synchronization chain, the received clock may have unacceptable wander and jitter. The router recovers the clock from the SyncE interface, converts it to the format required for the BITS interface, and sends it to an SSU through the BITS port. The SSU performs the cleanup and sends it back to the BITS interface. The cleaned up clock is received back from the SSU. This clock is used as the Tx clock for the SyncE ports. For Cisco ASR 1000 Series Router, the interface from which the clock is recovered and the BITS port to the SSU should reside on the same card.

• System to External: The system clock is used as the Tx clock for an external interface. By default, the system clock is not transmitted through the external interface.

A SyncE-enabled Cisco ASR 1000 Series Router provides the squelching functionality under which an alarm indication signal (AIS) is sent to the Tx interfaces if the clock source goes down. The squelching functionality is implemented in two scenarios:

• Line to External: If the line source goes down, an AIS is transmitted through the external interface to the SSU.

• System to External: If the router loses all the clock sources, an AIS is sent through the external interface to the SSU.

Squelching is performed only on external devices such as SSU or PRC.

You can have a maximum of six clock sources for a Cisco ASR 1000 Series Router. The clock source with highest priority is made the default clock source. You can manage the clock sources by changing the priority of the clock sources. You can also manage synchronization using the following management options:

• Hold-Off Time: If a clock source goes down, the router waits for a specific hold-off time before removing the source. By default, the value of hold-off time is 300 ms.

• Wait to Restore: If a SyncE interface comes up, the router waits for a specific period of time before considering the SyncE interface for synchronization source. By default, the value is 300 seconds.

• Force Switch: Forcefully select a synchronization source irrespective of whether the source is available or within the specified range.

• Manual Switch: Forcefully select a synchronization source, provided the source is available and within the specified range.

Synchronization Status Message and Ethernet Synchronization Messaging Channel

Network clocking uses the following mechanisms to exchange the quality level of the clock between the network elements:

• Synchronization Status Message

• Ethernet Synchronization Messaging Channel

Synchronization Status Message

Network elements use Synchronization Status Messages (SSM) to inform the neighboring elements about the Quality Level (QL) of the clock. The non-ethernet interfaces such as optical interfaces and SONET or T1 or E1 SPA frames, use SSM. The key benefits of the SSMs are:

• Prevents timing loops.


OL-16506-08


• Provides fast recovery when a part of the network fails.

• Ensures that a node get timing from the most reliable clock source.

Ethernet Synchronization Messaging Channel

In order to maintain a logical communication channel in synchronous network connections, Ethernet relies on a channel called the Ethernet Synchronization Messaging Channel (ESMC), which is based on the IEEE 802.3 Organization-Specific Slow Protocol (OSSP) standards. ESMC relays the SSM code that represents the quality level of the Ethernet Equipment Clock (EEC) in a physical layer.

The ESMC packets are received only for the ports configured as clock sources, and transmitted on all the SyncE interfaces in the system. These packets are then processed by the clock selection algorithm on route processors (RP) and are used to select the best clock. The Tx frame is generated based on the QL value of the selected clock source, and sent to all the enabled SyncE ports.

Clock Selection Algorithm

The clock selection algorithm selects the best available synchronization source from the nominated sources. This algorithm exhibits nonrevertive behavior among the clock sources with the same QL value, and always selects the signal with the best QL value. For clock option 1, the default is revertive, and for clock option 2, the default is nonrevertive.

The clock selection process works in the QL-enabled and QL-disabled modes. When multiple selection processes are present in a network element, all the processes work in the same mode.

QL-Enabled Mode

In QL-enabled mode, the following parameters contribute to the selection process:

• Quality level

• Signal fail via QL-FAILED

• Priority

• External commands.

If no external commands are active, the algorithm selects the reference (for clock selection) with the highest QL that does not experience a signal fail condition. If multiple inputs have the same highest QL, the input with the highest priority is selected. For multiple inputs having the same highest priority and QL, the existing reference is maintained (if it belongs to highest priority and QL group). Otherwise, an arbitrary reference from highest priority and QL group is selected.

QL-Disabled Mode

In QL-disabled mode, the following parameters contribute to the selection process:

• Signal failure

• Priority

• External commands

If no external commands are active, the algorithm selects the reference (for clock selection) with the highest priority that does not experience a signal fail condition. For multiple inputs having the same highest priority, the existing reference is maintained (if it belongs to highest priority group). Otherwise, an arbitrary reference from highest priority group is selected.


OL-16506-08


Hybrid Mode

The SyncE feature requires that each network element, along the synchronization path, to support SyncE. Timing over Packet (ToP) enables the transfer of timing over an asynchronous network. The hybrid mode uses the clock derived from 1588 (PTP) to drive the system clock. This is achieved by configuring the ToP interface on the PTP slave as the input source.

Note The ToP interface does not support QL, and works only in the QL-disabled mode.

Restrictions and Usage GuidelinesThis section lists the restrictions and usage guidelines for configuring the SyncE on a Cisco ASR 1000 Router:

• If the network clock algorithm is enabled, use the system clock as Tx clock (synchronous mode) for its Ethernet interfaces. You cannot change the synchronous mode on a per interface basis.

• You can configure a maximum of eight ports as a clock source for a Cisco ASR 1000 Router.

• The SyncE feature is SSO-coexistent, but not SSO-compliant. The clock selection algorithm is restarted on a switchover. During the switchover, the router goes into hold-over mode.

• The SyncE interfaces in WAN mode cannot be used for QL-enabled clock selection. You should either use them with the system in QL-disabled mode, or disable the ESMC on the interfaces, and use them as QL-disabled interfaces.

• It is recommended that you do not configure multiple input sources with the same priority as this impacts the TSM (Switching message delay).

• You cannot implement the network-clock based clock selection algorithm and the new algorithm simultaneously. Both these algorithms are mutually exclusive.

• Only metronome SPA are supported with the new G.781-based clock selection algorithm (Netsync).

• The Line-to-external configuration for the clock cleanup is supported only if the line interface and the external interface are on the same metronome SPA.

Configuring Synchronous Ethernet on the Cisco ASR 1000 Series RoutersThis section describes how to configure SyncE on the Cisco ASR 1000 Series Router.

You can implement SyncE on the Cisco ASR 1000 Series Router, using four different configurations:

• Configuring Clock Recovery from SyncE, page 9-4

• Configuring Clock Recovery from a BITS Port, page 9-6

• Configuring a SyncE Using the System-to-External Method, page 9-8

• Configuring a SyncE Using the Line-to-External Method, page 9-9

Configuring Clock Recovery from SyncE

This section describes how to configure clock recovery on Cisco ASR 1000 Series Router from SyncE method.


OL-16506-08


SUMMARY STEPS

1. enable


3. network-clock synchronization automatic

4. network-clock synchronization ssm option option_Id Generation_Id

5. interface gigabitethernet slot/port

6. synchronous mode

7. exit

8. network-clock input-source priority {interface interface_name slot/card/port | {external slot/card/port }}

9. exit

DETAILED STEPS

Command Purpose

Step 1 enable

Example:Router# enable

Enables the privileged EXEC mode.

Enter your password if prompted.



Enters the global configuration mode.

Step 3 network-clock synchronization automatic

Example:Router(config)# network-clock synchronization automatic

Enables the network clock selection algorithm. This command disables the Cisco-specific network-clock process, and turns on G.781-based automatic clock selection process.

Step 4 network-clock synchronization ssm option {option_id {GEN1 | GEN2}}

Example:Router(config)# network-clock synchronization ssm option 2 GEN1

Configures the equipment to work in a synchronization network. The option_id value 1 refers to a synchronization networks design for Europe. This is the default value. The option_id value 2 refers to a synchronization networks design for the U.S.

Step 5 interface gigabitethernet slot/port

Example:Router(config)# int gig 0/0/0

Specifies the Gigabit Ethernet interface to be configured:

slot/port—Specifies the location of the interface.


OL-16506-08


Examples

The following example shows how to configure clock recovery from SyncE:

Router>enableRouter# configure terminalRouter(config)# network-clock synchronization automaticRouter(config)# network-clock synchronization ssm option 2 GEN1Router(config)# int gig 0/0/0Router(config-if)# synchronous modeRouter(config)# exitRouter(config)# network-clock input-source 1 interface GigabitEthernet7/1Router(config)# exit

Configuring Clock Recovery from a BITS Port

This section describes how to configure clock recovery from BITS port.

SUMMARY STEPS

1. enable

Step 6 synchronous mode

Example:Router(config-if)# synchronous mode

Sets the mode to synchronous mode.

Step 7 exit


Exits the specific configuration mode.

Step 8 network-clock input-source priority {interface interface_name slot/card/port | {external slot/card/port }}

Example:Router(config)# network-clock input-source 1 interface GigabitEthernet7/1

Enables clock recovery from SyncE.

Step 9 exit


Exits the global configuration mode.

Command Purpose


OL-16506-08





5. network-clock input-source priority {interface interface_name slot/card/port | {external slot/card/port }}

6. exit

DETAILED STEPS

Command Purpose

Step 1 enable









Enables the network clock selection algorithm. This command disables the Cisco-specific network clock process, and turns on the G.781-based automatic clock selection process.



Configures the equipment to work in synchronization network. The option_id value 1 refers to synchronization networks design for Europe. This is the default value. The option_id value 2 refers to the synchronization networks design for the U.S.

Step 5 network-clock input-source priority {interface interface_name slot/card/port | {external slot/card/port }}

Example:Router(config-if-srv)# network-clock input-source 1 External 5/3/0 t1 sf

Enables clock recovery from a BITS port.

Step 6 exit




OL-16506-08


Examples

The following example shows how to configure clock recovery from a BITS port:

Router>enableRouter# configure terminalRouter(config)# network-clock synchronization automaticRouter(config)# network-clock synchronization ssm option 2 GEN1Router(config)# network-clock input-source 1 External 5/3/0 t1 sf Router(config)# exit

Configuring a SyncE Using the System-to-External Method

This section describes how to configure SyncE using System-to-External method.

SUMMARY STEPS

1. enable




5. network-clock output-source system priority {external slot/card/port [2m | 10m] }

6. exit

DETAILED STEPS

Command Purpose

Step 1 enable














OL-16506-08


Examples

The following example shows how to configure SyncE using System-to-External method:

Router>enableRouter# configure terminalRouter(config)# network-clock synchronization automaticRouter(config)# network-clock synchronization ssm option 2 GEN1Router(config)# network-clock input-source 1 External 5/3/0 t1 sf Router(config)# exit

The following example shows how to configure clock cleanup using an SSU:

Router(config)# network-clock output-source line 1 interface GigabitEthernet1/0/0 External 1/0/0 t1 sfRouter(config)# network-clock input-source 1 External 5/3/0 t1 sf

Configuring a SyncE Using the Line-to-External Method

This section describes how to configure a SyncE using the Line-to-External method.

SUMMARY STEPS

1. enable




5. interface gigabitethernet slot/port

6. synchronous mode

7. exit

8. network-clock output-source line priority {interface interface_name} {external slot/card/port}

9. exit

Step 5 network-clock output-source system priority {external slot/card/port [2m | 10m]}

Example:Router(config)# network-clock output-source system 1 external 4/0/0 t1 sf

Configures the system clock to be used on external Tx interfaces.

Step 6 exit



Command Purpose


OL-16506-08


DETAILED STEPS

Command Purpose

Step 1 enable













Step 5 interface gigabitethernet slot/port

Example:Router(config)# int gig 0/0/0

Specifies the Gigabit Ethernet interface to be configured:

slot/port—Specifies the location of the interface.

Step 6 synchronous mode

Example:Router(config-if)# synchronous mode

Sets the mode to synchronous mode.

Step 7 exit


Exits the specific configuration mode.


OL-16506-08


Examples

The following example shows how to configure a SyncE using the Line-to-External method:

Router>enableRouter# configure terminalRouter(config)# network-clock synchronization automaticRouter(config)# network-clock synchronization ssm option 2 GEN1Router(config)# network-clock input-source 1 interface GigabitEthernet7/1Router(config)# int gig 0/0/0Router(config-if)# synchronous modeRouter(config)# exitRouter(config)# network-clock output-source line 1 interface GigabitEthernet1/0/0 External 1/0/0Router(config)# exit

Managing Synchronization on the Cisco ASR 1000 Series RouterManage synchronization on a Cisco ASR 1000 Series Router using the following management commands:

• Quality-Level-Enabled Clock Selection: Use the network-clock synchronization mode QL-enabled command in the global configuration mode to configure the automatic selection process for the QL-enabled mode. This succeeds only if the SyncE interfaces are capable of sending SSMs. The following example shows how to configure network clock synchronization (QL-enabled mode) in the global configuration mode:

Router(config)# network-clock synchronization mode QL-enabled

• ESMC Process: Use the esmc process command in the global configuration mode to enable the ESMC process at system level. The no form of the command disables the ESMC process. The no form of the command fails if there is no SyncE-capable interface is installed in the platform. The following example shows how to enable ESMC in the global configuration mode:

Router(config)# esmc process

• ESMC Mode: Use the esmc mode [tx | rx |<cr>] command in the interface configuration mode to enable the ESMC process at the interface level. The no form of the command disables the ESMC process. The following example shows how to enable ESMC in the interface configuration mode:

Step 8 network-clock output-source line priority {interface interface_name} {external slot/card/port}

Example:Router(config-if-srv)# encapsulation dot1q 40 second-dot1q 42

Configures the line clock to be used on external Tx interfaces.

Step 9 exit



Command Purpose


OL-16506-08


Router(config-if)# esmc mode tx

• Network Clock Source Quality Level: Use the network-clock source quality-level command in the interface configuration mode to configure the QL value for ESMC on a gigabitethernet port. The value is based on global interworking options:

– If Option 1 is configured, the available values are QL-PRC, QL-SSU-A, QL-SSU-B, QL-SEC, and QL-DNU.

– If Option 2 is configured with GEN 2, the available values are QL-PRS, QL-STU, QL-ST2, QL-TNC, QL-ST3, QL-SMC, QL-ST4, and QL-DUS.

– If Option 2 is configured with GEN1, the available values are QL-PRS, QL-STU, QL-ST2, QL-SMC, QL-ST4, and QL-DUS

Use the network-clock quality-level command in the global configuration mode to configure the QL value for the SSMs on a BITS port. The following example shows how to configure network-clock quality-level in the global configuration mode:

Router(config)# network-clock quality-level rx QL-PRC external 1/0/0

The following example shows how to configure the network clock source quality level in the interface configuration mode:

Router(config-if)# network-clock source quality-level QL-PRC

• Wait-to-Restore Timer: Use the network-clock wait-to-restore timer global command to set the wait-to-restore time. You can configure the wait-to-restore time to any value between 0 to 86400 seconds. The default value is 300 seconds. The wait-to-restore timer can be set in the global configuration mode and the interface configuration mode. The following example shows how to configure the wait-to-restore timer in the global configuration mode:

Router(config)# network-clock wait-to-restore 10 global

The following example shows how to configure the wait-to-restore timer in the interface configuration mode:

Router(config)# int gigabit 1/0/0Router(config-if)# network-clock wait-to-restore 10

• Hold-Off Time: Use the network-clock hold-off timer global command to configure hold-off time. You can configure the hold-off time to either 0 or any value between 50 to 10000 ms. The default value is 300 ms. The network-clock hold-off timer can be set in the global configuration mode and the interface configuration mode. The following example shows how to configure the hold-off timer:

Router(config)# network-clock hold-off 50 global

• Force Switch: Use the network-clock switch force command to forcefully select a synchronization source irrespective of whether the source is available, and within range. The following example shows how to configure a force switch:

Router(config)# network-clock switch force interface GigabitEthernet 1/0/0

• Manual Switch: Use the network-clock switch manual command to manually select a synchronization source, provided the source is available and within range. The following example shows how to configure a manual switch:

Router(config)# network-clock switch manual interface GigabitEthernet 1/0/0


OL-16506-08


• Clear Manual and Force Switch: Use the network-clock clear switch controller-id command to clear the manual, or switch it on by force. The following example shows how to clear a switch:

Router(config)# network-clock clear switch t0

• Lock Out a Source: Use the network-clock set lockout command to lock out a clock source. A clock source flagged as lock-out is not selected for SyncE. To clear the lock-out on a source, use the network-clock clear lockout command. The following example shows how to lock out a clock source:

Router(config)# network-clock set lockout interface GigabitEthernet 7/1

The following example shows how to clear the lock out on a clock source:

Router(config)# network-clock clear lockout interface GigabitEthernet 7/1

VerificationUse the following commands to verify the SyncE configuration:

• Use the show network-clock synchronization command to display the output:

Router# show network-clocks synchronizationSymbols: En - Enable, Dis - Disable, Adis - Admin Disable NA - Not Applicable * - Synchronization source selected # - Synchronization source force selected & - Synchronization source manually switched

Automatic selection process : EnableEquipment Clock : 2048 (EEC-Option1)Clock Mode : QL-EnableESMC : EnabledSSM Option : 1T0 : GigabitEthernet1/1/0Hold-off (global) : 300 msWait-to-restore (global) : 30 secTsm Delay : 180 msRevertive : No

Nominated Interfaces

Interface SigType Mode/QL Prio QL_IN ESMC Tx ESMC Rx Internal NA NA/Dis 251 QL-SEC NA NA*Gi1/1/0 NA Sync/En 1 QL-PRC - -

• Use the show network-clock synchronization detail command to display all the details of network clock synchronization parameters at the global and interface levels as shown in the following example.

Router#show network-clock synchronization detailSymbols: En - Enable, Dis - Disable, Adis - Admin Disable NA - Not Applicable * - Synchronization source selected # - Synchronization source force selected & - Synchronization source manually switched

Automatic selection process : EnableEquipment Clock : 2048 (EEC-Option1)


OL-16506-08


Clock Mode : QL-EnableESMC : EnabledSSM Option : 1T0 : GigabitEthernet1/1/0Hold-off (global) : 300 msWait-to-restore (global) : 30 secTsm Delay : 180 msRevertive : NoForce Switch: FALSEManual Switch: FALSENumber of synchronization sources: 2sm(netsync NETCLK_QL_ENABLE), running yes, state 1ALast transition recorded: (ql_mode_enable)-> 1A (begin)-> 1A (sf_change)-> 1A (sf_change)-> 1A (ql_change)-> 1A (ql_change)-> 1A (ql_change)-> 1A (ql_change)-> 1A


Interface SigType Mode/QL Prio QL_IN ESMC Tx ESMC Rx Internal NA NA/Dis 251 QL-SEC NA NA*Gi1/1/0 NA Sync/En 1 QL-PRC - - External 1/3/0 E1 CRC4 NA/En 2 QL-FAILED NA NA

Interface:---------------------------------------------Local Interface: InternalSignal Type: NAMode: NA(Ql-enabled)SSM Tx: DISABLEDSSM Rx: DISABLEDPriority: 251QL Receive: QL-SECQL Receive Configured: -QL Receive Overrided: -QL Transmit: -QL Transmit Configured: -Hold-off: 0Wait-to-restore: 30Lock Out: FALSESignal Fail: FALSEAlarms: FALSESlot Disabled: FALSE

Local Interface: Gi1/1/0Signal Type: NAMode: Synchronous(Ql-enabled)ESMC Tx: ENABLEDESMC Rx: ENABLEDPriority: 1QL Receive: QL-PRCQL Receive Configured: -QL Receive Overrided: -QL Transmit: QL-DNUQL Transmit Configured: -Hold-off: 300Wait-to-restore: 30Lock Out: FALSESignal Fail: FALSEAlarms: FALSESlot Disabled: FALSE

• Use the show esmc command to displays the ESMC configuration output.


OL-16506-08


Router# show esmc Interface: GigabitEthernet12/1 Administative configurations: Mode: Synchronous ESMC TX: Enable ESMC RX: Enable QL TX: - QL RX: - Operational status: Port status: UP QL Receive: QL-PRC QL Transmit: QL-DNU QL rx overrided: - ESMC Information rate: 1 packet/second ESMC Expiry: 5 second

Interface: GigabitEthernet12/2 Administrative configurations: Mode: Synchronous ESMC TX: Enable ESMC RX: Enable QL TX: - QL RX: - Operational status: Port status: UP QL Receive: QL-DNU QL Transmit: QL-DNU QL rx overrided: QL-DNU ESMC Information rate: 1 packet/second ESMC Expiry: 5 second

• Use the show esmc detail command to display all the details of the ESMC parameters at the global and interface levels, as shown in the following example.

Router# show esmc detail Interface: GigabitEthernet12/1 Administrative configurations: Mode: Synchronous ESMC TX: Enable ESMC RX: Enable QL TX: - QL RX: - Operational status: Port status: UP QL Receive: QL-PRC QL Transmit: QL-DNU QL rx overrided: - ESMC Information rate: 1 packet/second ESMC Expiry: 5 second ESMC Tx Timer: Running ESMC Rx Timer: Running ESMC Tx interval count: 1 ESMC INFO pkts in: 2195 ESMC INFO pkts out: 6034 ESMC EVENT pkts in: 1 ESMC EVENT pkts out: 16

Interface: GigabitEthernet12/2 Administrative configurations: Mode: Synchronous ESMC TX: Enable ESMC RX: Enable QL TX: - QL RX: -


OL-16506-08


Operational status: Port status: UP QL Receive: QL-DNU QL Transmit: QL-DNU QL rx overrided: QL-DNU ESMC Information rate: 1 packet/second ESMC Expiry: 5 second ESMC Tx Timer: Running ESMC Rx Timer: Running ESMC Tx interval count: 1 ESMC INFO pkts in: 0 ESMC INFO pkts out: 2159 ESMC EVENT pkts in: 0 ESMC EVENT pkts out: 10

Troubleshooting the SyncE ConfigurationTable 9-2 list the debug commands that are available for troubleshooting the SyncE configuration on the Cisco ASR 1000 Series Router:

Note Before you troubleshoot, ensure that all the network clock synchronization configurations are complete.

Table 9-2 SyncE Debug Commands

Debug Command Purpose

debug platform network-clock Debugs issues related to the network clock, such as alarms, OOR, active-standby sources not selected correctly, and so on.

debug esmc errordebug esmc eventdebug esmc packet [interface <interface name>]debug esmc packet rx [interface <interface name>]debug esmc packet tx [interface <interface name>]

Verifies whether the ESMC packets are transmitted and received with proper quality-level values.


OL-16506-08


Table 9-3 provides the information about troubleshooting scenarios that you may encounter while configuring the SyncE.

Table 9-3 Troubleshooting Scenarios

Problem Solution

Clock selection • Verify that there are no alarms on the interfaces. Use the show network-clock synchronization detail command to check this.

• Ensure that the nonrevertive configurations are in place.

• Reproduce the issue and collect the logs using the debug network-clock errors, debug network-clock event, and debug network-clock sm commands. Contact Cisco Technical Support if the issue persists.

Incorrect QL values • Ensure that there is no framing mismatch with the SSM option.

• Reproduce the issue using the debug network-clock errors and debug network-clock event commands. Also, enable the debug hw-module subslot command. (this is specific to SIP-400).

Alarms • Reproduce the issue using the debug platform network-clock command enabled in the RP. Alternatively, enable the debug network-clock event and debug network-clock errors commands.


OL-16506-08


Incorrect clock limit set or queue limit disabled mode

• Verify that there are no alarms on the interfaces. Use the show network-clock synchronization detail RP command to confirm.

Warning We recommend that you do not use these debug commands without TAC supervision.

• Use the show network-clock synchronization command to confirm if the system is in revertive mode or nonrevertive mode and verify the non-revertive configurations as shown in this example:

RouterB#show network-clocks synchronization

Symbols: En - Enable, Dis - Disable, Adis - Admin Disable NA - Not Applicable

- Synchronization source selected

# - Synchronization source force selected

& - Synchronization source manually switched

Automatic selection process : Enable

Equipment Clock : 1544 (EEC-Option2)

Clock Mode : QL-Enable

ESMC : Enabled

SSM Option : GEN1

T0 : POS3/1/0

Hold-off (global) : 300 ms

Wait-to-restore (global) : 0 sec

Tsm Delay : 180 ms

Revertive : Yes<<<<If it is non revertive then it will show NO here.


Interface SigType Mode/QL Prio QL_IN ESMC Tx ESMC Rx

Internal NA NA/Dis 251 QL-ST3 NA NA

SONET 3/0/0 NA NA/En 3 QL-ST3 NA NA

*PO3/1/0 NA NA/En 1 QL-ST3 NA NA

SONET 2/3/0 NA NA/En 4 QL-ST3 NA NA

• Reproduce the current issue and collect the logs using the debug network-clock errors, debug network-clock event, and debug network-clock sm RP commands.

Warning We suggest you do not use these debug commands without TAC supervision.

Contact Cisco Technical Support if the issue persists.

Table 9-3 Troubleshooting Scenarios (continued)

Problem Solution


OL-16506-08


Incorrect QL values when you use the show network-clock synchronization detail command.

• Use the network clock synchronization SSM (option 1 |option 2) command to confirm that there is no framing mismatch. Use the show run interface command to validate the framing for a specific interface. For the SSM option 1, framing should be SDH or E1, and for SSM option 2, it should be SONET or T1.

• Reproduce the issue using the debug network-clock errors and debug network-clock event RP commands or enable the debug hw-module subslot command. (This is specific to SIP-400).


The error message “%NETCLK-6-SRC_UPD: Synchronization source SONET 2/3/0 status (Critical Alarms(OOR)) is posted to all selection process" is displayed.

• Interfaces with alarms or OOR cannot be a part of the selection process even if it has higher queue limit or priority. Use the debug platform network-clock RP command to troubleshoot network clock issues.

• Reproduce the issue using the debug platform network-clock command enabled in a RP or enable the debug network-clock event and debug network-clock errors RP commands.


Table 9-3 Troubleshooting Scenarios (continued)

Problem Solution


OL-16506-08



OL-16506-08


C H A P T E R 10
Configuring Bridge Domain Interfaces
The Cisco ASR 1000 Series Routers supports the bridge domain interface feature for terminating Layer 2 Ethernet segments into Layer 3 IP.


• Restrictions for the Bridge Domain Interface, page 10-1

• Information about a Bridge Domain Interface, page 10-1

• Creating or Deleting a Bridge Domain Interface, page 10-4

• Bridge Domain Interface Scalability, page 10-5

• Configuring a Bridge Domain Interface, page 10-5

Restrictions for the Bridge Domain InterfaceRestrictions for a bridge domain interface include:

• Only 4096 bridge domain interfaces are supported per system.

• When using a bridge domain interface in a bridge domain, configure the rewrite command on all the incoming service instances to remove the VLAN tags.

Information about a Bridge Domain InterfaceBridge domain interface is a logical interface that allows bidirectional flow of traffic between a Layer 2 bridged network and a Layer 3 routed network traffic. Bridge domain interfaces are identified by the same index as the bridge domain. Each bridge domain represents a Layer 2 broadcast domain. Only one bridge domain interface can be associated with a bridge domain.

Bridge domain interface supports the following features:

• IP termination

• Layer 3 VPN termination

• Address Resolution Protocol (ARP), G-ARP, and P-ARP handling

• MAC address assignment

Prior to configuring a bridge domain interface, you must understand the following concepts:

• Ethernet Virtual Circuit Overview, page 10-2


Chapter 10 Configuring Bridge Domain Interfaces Information about a Bridge Domain Interface

• Assigning a MAC Address, page 10-2

• Support for IP Protocols, page 10-2

• Support for IP Forwarding, page 10-3

• Packet Forwarding, page 10-3

• Bridge Domain Interface Statistics, page 10-4

Ethernet Virtual Circuit OverviewAn Ethernet Virtual Circuit (EVC) is an end-to-end representation of a single instance of a Layer 2 service being offered by a provider to a customer. It embodies the different parameters on which the service is being offered. In the Cisco EVC Framework, the bridge domains are made up of one or more Layer 2 interfaces known as service instances. A service instance is the instantiation of an EVC on a given port on a given router. Service instance is associated with a bridge domain based on the configuration.

An incoming frame can be classified as service instance based on the following criteria:

• Single 802.1Q VLAN tag, priority-tagged, or 802.1ad VLAN tag

• Both QinQ (inner and outer) VLAN tags, or both 802.1ad S-VLAN and C-VLAN tags

• Outer 802.1p CoS bits, inner 802.1p CoS bits, or both

• Payload Ethernet type (five choices are supported: IPv4, IPv6, PPPoE-all, PPoE-discovery, and PPPoE-session)

Service instance also supports alternative mapping criteria:

• Untagged—Mapping to all the frames lacking a 802.1Q or 802.1ad header

• Default—Mapping to all the frames

For more information on the EVC architecture, see EVC Infrastructure on the Cisco ASR 1000 Router.

Assigning a MAC AddressAll the bridge domain interfaces on the Cisco ASR 1000 chassis share a common MAC address. The first bridge domain interface on a bridge domain is allocated a MAC address. Thereafter, the same MAC address is assigned to all the bridge domain interfaces that are created in that bridge domain.

Note You can configure a static MAC address on a bridge domain interface using the mac-address command.

Support for IP ProtocolsBridge domain interface supports the following IP-related protocols:

• UDP

• TCP

• HTTP

• NTP


OL-16506-08

is http://www.cisco.com/en/US/docs/ios/ios_xe/cether/configuration/guide/ce_evc-infra_xe.html

Chapter 10 Configuring Bridge Domain Interfaces Information about a Bridge Domain Interface

• SNMP

• Telnet

• TFTP

Support for IP ForwardingBridge domain interface supports the following IP forwarding features:

• IPv4 input and output access control lists (ACL)

• IPv4 input and output QoS policies. The operations supported for the input and output service policies on a bridge domain interface are:

– Classification

– Marking

– Policing

– Hierarchical QoS

• IPv4 L3 VRFs

Packet ForwardingA bridge domain interface provides bridging and forwarding services between the Layer 2 and Layer 3 network infrastructure.

Layer 2 to Layer 3

During a packet flow from a Layer 2 network to a Layer 3 network, if the destination MAC address of the incoming packet matches the bridge domain interface MAC address, or if the destination MAC address is a multicast address, the packet or a copy of the packet is forwarded to the bridge domain interface.

Note MAC address learning cannot not be performed on the bridge domain interface.

Note In a bridge domain, when flooding unknown unicast frames, bridge domain interface is not included.

Layer 3 to Layer 2

When a packet arrives at a Layer 3 physical interface of a router, a route lookup action is performed. If route lookup points to a bridge domain interface, then the bridge domain interface adds the layer 2 encapsulation and forwards the frame to the corresponding bridge domain. The byte counters are updated.

During a Layer 2 lookup on a bridge domain to which the bridge domain interface belongs, the bridge domain forwards the packets to the correct service instance based on the destination MAC address.


OL-16506-08

Chapter 10 Configuring Bridge Domain Interfaces Creating or Deleting a Bridge Domain Interface

Link States of a Bridge Domain and a Bridge Domain InterfaceBridge domain interface acts as a routable IOS interface on Layer 3 and as a port on a bridge domain. Both bridge domain interfaces and bridge domains operate with individual administrative states.

Shutting down a bridge domain interface stops the Layer 3 data service, but does not override or impact the state of the associated bridge domain.

Shutting down a bridge domain stops Layer 2 forwarding across all the associated members including service instances and bridge domain interfaces. The operational state of a bridge domain is influenced by associated service instances. Bridge domain interface cannot be operational unless one of the associated service instance is up.

Note Because a bridge domain interface is an internal interface, the operational state of bridge domain interface does not affect the bridge domain operational state.

Bridge Domain Interface StatisticsFor virtual interfaces, such as the bridge domain interface, protocol counters are periodically queried from the QFP.

When packets flow from a Layer 2 bridge domain network to a Layer 3 routing network through the bridge domain interface, the packets are treated as bridge domain interface input packets and bytes. When packets arrive at a Layer 3 interface and are forwarded through the bridge domain interface to a Layer 2 bridge domain, the packets are treated as output packets and bytes, and the counters are updated accordingly.

The show interfaces accounting command is used to display the statistics. The show interface <if-name> command is used to display the overall count of the packets and bytes that are transmitted and received.

Creating or Deleting a Bridge Domain InterfaceWhen you define an interface or subinterface for a Cisco IOS router, you name it and specify how it is assigned an IP address.You can create a bridge domain interface before adding a bridge domain to the system, this new bridge domain interface will be activated after the associated bridge domain is configured.

Note When a bridge domain interface is created, a bridge domain is automatically created.

When both bridge domain interface and bridge domain are created, the system maintains the required associations for mapping the bridge domain-bridge domain interface pair.

The mapping of bridge domain and bridge domain interface is maintained in the system. The bridge domain interface uses the index of the associated bridge domain to show the association.


OL-16506-08

Chapter 10 Configuring Bridge Domain Interfaces Bridge Domain Interface Scalability

Bridge Domain Interface ScalabilityTable 10-1 lists the bridge domain interface Scalability Numbers, based on the type of ASR1000 Forwarding Processors.

Configuring a Bridge Domain InterfaceTo configure a bridge domain interface, complete the following steps:

SUMMARY STEPS


2. interface BDI interface number

3. ip address ip-address mask

4. mac-address {mac-address}

5. no shut

6. shut

Table 10-1 Bridge domain interface Scalability Numbers Based on the type of ASR1000

Forwarding Processors

Description

ASR1000-ESP5ASR 1001ASR 1002-F (ESP2.5)

ASR1000-ESP10ASR1000-ESP10-NASR1000-ESP20 ASR1000-ESP40

Maximum bridge domain interfaces per router

4096 4096 4096


OL-16506-08

Chapter 10 Configuring Bridge Domain Interfaces Configuring a Bridge Domain Interface

DETAILED STEPS

Example

The following example shows the configuration of a bridge domain interface at IP address 2.2.2.1 255.255.255.0:

Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface BDI3Router(config-if)# ip address 2.2.2.1 255.255.255.0Router(config-if)# mac-address 1.1.3Router(config-if)# no shutRouter(config-if)# exit

Router(config)#





Step 2 interface BDI{interface number}

Example:Router(config)# interface BDI3

Specifies the bridge domain interface on a Cisco ASR 1000 Series Router.

Step 3 ip address ip-address mask

or


Example:Router(config-if)# ip address 2.2.2.1 255.255.255.0

Specifies either the IPv4 or IPv6 address for the bridge domain interface.

Step 4 mac-address {mac-address}

Router(config-if)#mac-address 1.1.3

Specifies the MAC address for the bridge domain interface.

Step 5 no shut

Example:hostname(config-if)# no shut

Enables the bridge domain interface on the Cisco ASR 1000 Series Router.

Step 6 shut

Example:hostname(config-if)# shut

Disables the bridge domain interface on the Cisco ASR 1000 Series Router.


OL-16506-08


You can use different show commands to display the bridge domain interface configuration information:

• show interfaces—Displays the configuration summary of the bridge domain interface.

Example:

Router# show interfaces BDI3

• show platform software interface fp active name—Displays the bridge domain interface configuration in a Forwarding Processor.

Example:

Router# show platform software interface fp active name BDI4

• show platform hardware qfp active interface if-name—Displays the bridge domain interface configuration in a data path.

Example:

Router# show platform hardware qfp active interface if-name BDI4

You can use the follwoing debug commands to debug the bridge domain interface configurations:

• debug platform hardware qfp feature—Debugs the features in the Cisco Quantum Flow Processor (QFP).

The following example shows how to debug the l2bd for all the clients:

Router# debug platform hardware qfp active feature l2bd client all

The selected CPP L2BD Client debugging is on.

• platform trace runtime process forwarding-manager module interfaces—Enables the Forwarding Manager Route Processor and Embedded Service Processor trace messages for the Forwarding Manager process.

In the following example, the trace level for the forwarding processor module in the Forwarding Manager of the ESP processor in slot 0 is set to the informational tracing level (info):

Router(config)# platform trace runtime slot F0 bay 0 process forwarding-manager module interfaces level info

• platform trace boottime process forwarding-manager module interfaces—Enables the Forwarding Manager Route Processor and Embedded Service Processor trace messages for the Route Processor Forwarding Manager process during bootup.

In the following example, the trace level for the forwarding processor module in the Forwarding Manager of the ESP processor in slot R0 is set to the informational tracing level (max):

Router(config)# platform trace boottime slot R0 bay 1 process forwarding-manager forwarding-manager level max

For additional information on the commands and the options available with each command, see the Cisco IOS Configuration Fundamentals Command Reference.


OL-16506-08



OL-16506-08


C H A P T E R 11
Tracing and Trace Management
This chapter contains the following sections:

• Tracing Overview, page 11-1

• How Tracing Works, page 11-1

• Tracing Levels, page 11-2

• Viewing a Tracing Level, page 11-3

• Setting a Tracing Level, page 11-4

• Viewing the Content of the Trace Buffer, page 11-5

Tracing OverviewTracing is a function that logs internal events. Trace files are automatically created and saved to the tracelogs directory on the harddisk: file system on all Cisco ASR 1000 Series Routers except the Cisco ASR 1002 Router, which stores tracing files in bootflash:. Trace files are used to store tracing data.

The contents of trace files are useful for the following purposes:

• Troubleshooting—If a Cisco ASR 1000 Series Router is having an issue, the trace file output may provide information that is useful for locating and solving the problem. Trace files can almost always be accessed through diagnostic mode even if other system issues are occurring.

• Debugging—The trace file outputs can help users get a more detailed view of system actions and operations.

How Tracing WorksThe tracing function logs the contents of internal events on the Cisco ASR 1000 Series Routers. Trace files with all trace output for a module are periodically created and updated and are stored in the tracelog directory. Trace files can be erased from this directory to recover space on the file system without impacting system performance.

The most recent trace information for a specific module can be viewed using the show platform software trace message privileged EXEC and diagnostic mode command. This command can be entered to gather trace log information even during an IOS failure because it is available in diagnostic mode.

Trace files can be copied to other destinations using most file transfer functions (such as FTP, TFTP, and so on) and opened using a plaintext editor.


Chapter 11 Tracing and Trace Management

Tracing cannot be disabled on the Cisco ASR 1000 Series Router. Trace levels, however, which set the message types that generate trace output, are user-configurable and can be set using the set platform software trace command. If a user wants to modify the trace level to increase or decrease the amount of trace message output, the user should set a new tracing level using the set platform software trace command. Trace levels can be set by process using the all-modules keyword within the set platform software trace command, or by module within a process. See the set platform software trace command reference for more information on this command, and the “Tracing Levels” section on page 11-2 of this document for additional information on tracing levels.

Tracing LevelsTracing levels determine how much information about a module should be stored in the trace buffer or file.

Table 11-1 shows all of the trace levels that are available and provides descriptions of what types of messages are displayed with each tracing level.

Table 11-1 Tracing Levels and Descriptions

Trace level settings are leveled, meaning that every setting will contain all messages from the lower setting plus the messages from its own setting. For instance, setting the trace level to 3(error) ensures that the trace file will contain all output for the 0 (emergencies), 1 (alerts), 2 (critical), and 3 (error) settings. Setting the trace level to 4 (warning) will ensure that all trace output for the specific module will be included in that trace file.

The default tracing level for every module on the Cisco ASR 1000 Series Router is notice.

Trace Level Level Number Description

Emergency 0 The message is regarding an issue that makes the system unusable.

Alert 1 The message is regarding an action that must be taken immediately.

Critical 2 The message is regarding a critical condition. This is the default setting for every module on the Cisco ASR 1000 Series Routers.

Error 3 The message is regarding a system error.

Warning 4 The message is regarding a system warning

Notice 5 The message is regarding a significant issue, but the router is still working normally.

Informational 6 The message is useful for informational purposes only.

Debug 7 The message provides debug-level output.

Verbose 8 All possible tracing messages are sent.

Noise - All possible trace messages for the module are logged.

The noise level is always equal to the highest possible tracing level. Even if a future enhance-ment to tracing introduces a higher tracing level, the noise level will become equal to the level of that new enhancement.


OL-16506-08


All trace levels are not user-configurable. Specifically, the alert, critical, and notice tracing levels cannot be set by users. If you wish to trace these messages, set the trace level to a higher level that will collect these messages.

When setting trace levels, it is also important to remember that the setting is not done in a configuration mode, so trace level settings are returned to their defaults after every router reload.

Caution Setting tracing of a module to the debug level or higher can have a negative performance impact. Setting tracing to this level or higher should be done with discretion.

Caution Setting a large number of modules to high tracing levels can severely degrade performance. If a high level of tracing is needed in a specific context, it is almost always preferable to set a single module on a higher tracing level rather than setting multiple modules to high tracing levels.

Viewing a Tracing LevelBy default, all modules on the Cisco ASR 1000 Series Routers are set to notice. This setting will be maintained unless changed by a user.

To see the tracing level for any module on the Cisco ASR 1000 Series Routers, enter the show platform software trace level command in privileged EXEC or diagnostic mode.

In the following example, the show platform software trace level command is used to view the tracing levels of the Forwarding Manager processes on the active RP:

Router# show platform software trace level forwarding-manager rp active Module Name Trace Level -----------------------------------------------acl Notice binos Notice binos/brand Notice bipc Notice bsignal Notice btrace Notice cce Notice cdllib Notice cef Notice chasfs Notice chasutil Notice erspan Notice ess Notice ether-channel Notice evlib Notice evutil Notice file_alloc Notice fman_rp Notice fpm Notice fw Notice icmp Notice interfaces Notice iosd Notice ipc Notice ipclog Notice iphc Notice ipsec Notice mgmte-acl Notice


OL-16506-08


mlp Notice mqipc Notice nat Notice nbar Notice netflow Notice om Notice peer Notice qos Notice route-map Notice sbc Notice services Notice sw_wdog Notice tdl_acl_config_type Notice tdl_acl_db_type Notice tdl_cdlcore_message Notice tdl_cef_config_common_type Notice tdl_cef_config_type Notice tdl_dpidb_config_type Notice tdl_fman_rp_comm_type Notice tdl_fman_rp_message Notice tdl_fw_config_type Notice tdl_hapi_tdl_type Notice tdl_icmp_type Notice tdl_ip_options_type Notice tdl_ipc_ack_type Notice tdl_ipsec_db_type Notice tdl_mcp_comm_type Notice tdl_mlp_config_type Notice tdl_mlp_db_type Notice tdl_om_type Notice tdl_ui_message Notice tdl_ui_type Notice tdl_urpf_config_type Notice tdllib Notice trans_avl Notice uihandler Notice uipeer Notice uistatus Notice urpf Notice vista Notice wccp Notice

Setting a Tracing LevelTo set a tracing level for any module on the Cisco ASR 1000 Series Routers, or for all modules within a process on the Cisco ASR 1000 Series Router, enter the set platform software trace privileged EXEC and diagnostic mode command.

In the following example, the trace level for the ACL module in the Forwarding Manager of the ESP processor in slot 0 is set to info.

set platform software trace forwarding-manager F0 acl info

See the set platform software trace command reference for additional information about the options for this command.


OL-16506-08


Viewing the Content of the Trace BufferTo view the trace messages in the trace buffer or file, enter the show platform software trace message privileged EXEC and diagnostic mode command.

In the following example, the trace messages for the Host Manager process in Route Processor slot 0 are viewed using the show platform software trace message command:

Router# show platform software trace message host-manager R008/23 12:09:14.408 [uipeer]: (info): Looking for a ui_req msg08/23 12:09:14.408 [uipeer]: (info): Start of request handling for con 0x100a61c808/23 12:09:14.399 [uipeer]: (info): Accepted connection for 14 as 0x100a61c808/23 12:09:14.399 [uipeer]: (info): Received new connection 0x100a61c8 on descriptor 1408/23 12:09:14.398 [uipeer]: (info): Accepting command connection on listen fd 708/23 11:53:57.440 [uipeer]: (info): Going to send a status update to the shell manager in slot 008/23 11:53:47.417 [uipeer]: (info): Going to send a status update to the shell manager in slot 0


OL-16506-08



OL-16506-08


C H A P T E R 12
Configuring and Accessing the Web User Interface
The Cisco ASR 1000 Series Routers introduce a web user interface that expands on the functionality of web user interfaces available in other Cisco routers.

This chapter is about this web user interface and covers the following topics:

• Web User Interface Overview, page 12-1

• Configuring the Router for Web User Interface Access, page 12-5

• Authentication and the Web User Interface, page 12-7

• Domain Name System and the Web User Interface, page 12-7

• Clocks and the Web User Interface, page 12-7

• Accessing the Web User Interface, page 12-8

• Using Auto-Refresh, page 12-9

• Web User Interface Tips and Tricks, page 12-10

Web User Interface OverviewThis section covers the following topics:

• Web User Interface General Overview, page 12-1

• Legacy Web User Interface Overview, page 12-2

• Graphics-Based Web User Interface Overview, page 12-3

• Persistent Web User Interface Transport Maps Overview, page 12-4

Web User Interface General OverviewThe web user interface is available on Cisco ASR 1000 Series Routers starting in Cisco IOS XE Release 2.1.1. The web user interface is not available in Cisco IOS XE Release 2.1.0.

The Cisco ASR 1000 Series Routers can be accessed using a web user interface. This web user interface allows users to monitor router performance using an easy-to-read graphical interface. Most aspects of a Cisco ASR 1000 Series Router can be monitored using the web user interface.

The web user interface has the following features:


Chapter 12 Configuring and Accessing the Web User Interface Web User Interface Overview

• An interface that presents information in an easy-to-read graphical format.

• An interface that allows users to monitor most software processes, including processes related to the IOS and non-IOS sub-packages within the Cisco IOS XE consolidated package.

• An interface that allows users to monitor most hardware components, including all RPs, ESPs, SIPs, and SPAs installed in the router.

• Access to the legacy web user interface in addition to the enhanced web user interface.

• The ability to gather the output of show commands from the web user interface.

Legacy Web User Interface OverviewPrevious Cisco routers have a legacy web user interface that can be used to monitor the router. This legacy web user interface presents information in a straightforward manner without using any graphics. On the Cisco ASR 1000 Series Routers, this interface is part of the larger web user interface and can be accessed by clicking the “IOS Web UI” option in the left-hand menu.

On the Cisco ASR 1000 Series Routers, the legacy web user interface can only be used to configure and monitor the IOS sub-package. In some scenarios, most notably when an ip http command has been successfully entered to enable the HTTP or HTTPS server while a properly configured web user interface transport map has not yet been applied on the Cisco ASR 1000 Series Router, the legacy web user interface will be accessible while the graphics-based web user interface will be inaccessible.

See Figure 12-1 for an example of the legacy web user interface home page.


OL-16506-08


Figure 12-1 Legacy Web User Interface Home Page

Graphics-Based Web User Interface OverviewThe web user interface on the Cisco ASR 1000 Series Routers expands the legacy web user interface available on other platforms by presenting information in easy-to-read graphics-based tables, graphs, or charts, depending on the information presented. The web user interface on the Cisco ASR 1000 Series Routers is also able to present monitoring information stored in both the IOS and non-IOS sub-packages, allowing for a complete view of the router using the web user interface.

See Figure 12-2 for an example of the graphics-based web user interface home page.


OL-16506-08


Figure 12-2 Graphics-Based Web User Interface Home Page

Persistent Web User Interface Transport Maps OverviewTo enable the graphics-based web user interface, a persistent web user interface transport map must be configured. The persistent web user interface transport map, when successfully configured and applied to the router, defines how the router handles incoming web user interface requests. In the persistent web user interface transport map, users define whether the graphics-based web user interface can be accessed through HTTP, HTTPS, or both protocols. Only one persistent web user interface transport map can be applied to a Cisco ASR 1000 Series Router at a time.


OL-16506-08

Chapter 12 Configuring and Accessing the Web User Interface Configuring the Router for Web User Interface Access

The persistent web user interface transport map configuration must be performed in addition to the legacy web user interface configuration, which is configured using the ip http command set. The ip http command settings define which ports are used by HTTP or HTTPS for both the legacy and graphics-based web user interface.

For information on configuring the entire graphics-based web user interface, including the configuration of persistent web user interface transport maps, see the “Configuring the Router for Web User Interface Access” section on page 12-5.

Configuring the Router for Web User Interface AccessThe ability to access either web user interface on the Cisco ASR 1000 Series Routers is disabled by default.

The legacy web user interface must be configured before the graphics-based web user interface can be enabled.

To enable the entire web user interface, perform the following tasks:

Note The web user interface will not work if the Management Ethernet interface has not been configured or is not working; specifically, the default route must be specified in the Management Ethernet VRF before the web user interface can be configured. See the “Using the Management Ethernet Interface” chapter for information on configuring the Management Ethernet interface on your router. See the “Setting a Default Route in the Management Ethernet Interface VRF” section on page 8-4 chapter for information on configuring a default route in the Management Ethernet interface on your router.

Step 1 (Optional) Ensure the clock setting on your router is accurate by entering the show clock command.

Router# show clock*13:56:59.257 DST Mon May 5 2008

If the router time is not properly set, see the clock set and clock timezone command references for information on properly setting the router clock.

Note The “Clocks and the Web User Interface” section on page 12-7 provides additional information on how clock settings on both the router and the web-browser can impact the web user interface.

Step 2 Connect to your router and enter the configure terminal command to enter global configuration mode.

Step 3 Enable the legacy web user interface by entering one of the following global configuration commands:

• ip http server—Enables HTTP on port 80, which is the default HTTP port.

• ip http port port-number—Enables HTTP on the non-default user-specified port.

• ip http secure-server—Enables HTTPS on port 443, the default HTTPS port.

• ip http secure-port port-number—Enables HTTPS on the non-default user-specified port.

The legacy web user interface becomes available at this point of the procedure. Users attempting to access the web user interface after this step is completed will see the legacy web user interface only.

To enable the graphics-based web user interface, proceed to Step 4 and complete the remaining steps in this procedure.


OL-16506-08

http://www.cisco.com/en/US/docs/ios/netmgmt/command/reference/nm_02.html#wp1013708


Chapter 12 Configuring and Accessing the Web User Interface Configuring the Router for Web User Interface Access

Step 4 Create and name a persistent web user interface transport map by entering the transport-map type persistent webui transport-map-name command.

Step 5 Enable HTTP, HTTPS, or both by entering the following commands in transport map configuration mode:

• server—Enables HTTP.

• secure-server—Enables HTTPS.

Port numbers cannot be set within the transport map. The port numbers defined in Step 3 are also used with these settings in the persistent web user interface transport map.

Step 6 (Optional) Enter the show transport-map name transport-map-name privileged EXEC command to verify that your transport map is properly configured.

Step 7 Enable the transport map by entering the transport type persistent webui input transport-map-name global configuration command.

Examples

In the following example, the web user interface using the default HTTP port is enabled:

Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# ip http serverRouter(config)# transport-map type persistent webui http-webuiRouter(config-tmap)# serverRouter(config-tmap)# exitRouter(config)# exit

Router# show transport-map name http-webuiTransport Map: Name: http-webui Type: Persistent Webui Transport

Webui: Server: enabled Secure Server: disabled

Router# configure terminalRouter(config)# transport type persistent webui input http-webui*Apr 22 02:43:55.798: %UICFGEXP-6-SERVER_NOTIFIED_START: R0/0: psd: Server wui has been notified to start

In the following example, the web user interface using the default HTTPs port is enabled:

Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# ip http secure-serverRouter(config)# transport-map type persistent webui https-webui Router(config-tmap)# secure-serverRouter(config-tmap)# exitRouter(config)# transport type persistent webui input https-webui*Apr 22 02:38:43.597: %UICFGEXP-6-SERVER_NOTIFIED_START: R0/0: psd: Server wui has been notified to start

In the following example, the web user interface using the default HTTP and HTTPS ports is enabled:

Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# ip http serverRouter(config)# ip http secure-server


OL-16506-08

Chapter 12 Configuring and Accessing the Web User Interface Authentication and the Web User Interface

Router(config)# transport-map type persistent webui http-https-webuiRouter(config-tmap)# serverRouter(config-tmap)# secure-serverRouter(config-tmap)# exitRouter(config)# transport type persistent webui input http-https-webui*Apr 22 02:47:22.981: %UICFGEXP-6-SERVER_NOTIFIED_START: R0/0: psd: Server wui has been notified to start

Authentication and the Web User InterfaceUsers attempting to access the web user interface for a router are subject to the same authentication requirements configured for that router. The web browser prompts all users for a name and password combination, and the web browser then looks to the router configuration to see if a user should or should not be granted access to the web user interface.

Only users with a privilege level of 15 can access the web user interface. Otherwise, authentication of web user interface traffic is governed by the authentication configuration for all other traffic.

To configure authentication on your router, see Configuring Authentication.

Domain Name System and the Web User InterfaceThe Domain Name System (DNS) is a distributed database in which you can map hostnames to IP addresses through the DNS protocol from a DNS server.

If the router is configured to participate in the Domain Name System, users can access the web user interface by entering http://<dns-hostname> as the web browser address.

For information on configuring DNS, see Configuring DNS.

Clocks and the Web User InterfaceRequests to view the web user interface can be rejected by certain web browsers if the time as seen by the web browser differs from the time as seen by the router by an hour or more.

For this reason, we recommend checking the router time using the show clock command before configuring the router and, if the router time is not properly set, properly set the time using the clock set and clock timezone commands.

Similarly, the web browser’s clock source, which is usually the personal computer, must also have an accurate time to properly access the web user interface.

The following message appears when the web browser and the router clocks are more than an hour apart:

Your access is being denied for one of the following reasons: . Your previous session has timed-out, or . You have been logged out from elsewhere, or . You have not yet logged in, or . The resource requires a higher privilege level login.

If you see this message and fixing the other possible causes of the issue still does not make the web user interface accessible, check both the router clock and the PC clock to ensure both clocks reflect the accurate day and time and then retry your connection to the web user interface.


OL-16506-08

http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfathen.html

http://www.cisco.com/en/US/docs/ios/ipaddr/configuration/guide/iad_config_dns_ps6922_TSD_Products_Configuration_Guide_Chapter.html



Chapter 12 Configuring and Accessing the Web User Interface Accessing the Web User Interface

Also note that if one clock changes at daylight savings time while another clock does not, clock-related issues can occur.

Accessing the Web User InterfaceTo access the web user interface, perform the following tasks:

Step 1 Open your web browser. The web user interface supports the following web browsers:

• Microsoft Internet Explorer 6 or later

• Mozilla Firefox 2.0 or later

Step 2 Enter the address of the router in the address field of the web browser. The format for the address of the router in the address field is http://<routername or management-ethernet-ip-address>:[http-port] or https://<routername or management-ethernet-ip-address>:[https-port], and the addresses that are acceptable depend upon your web browser user interface configurations and whether your router is participating in DNS. Below are some examples of acceptable address field web browser entries:

HTTP Using Default Port Example

http://172.16.5.1

HTTPS Using Default Port Example

https://172.16.5.1

HTTP Using Non-Default Port Example

http://172.16.5.1:94

HTTPS Using Non-Default Port Example

https://172.16.5.1:530/

HTTP Using Default Port Participating in DNS Example

http://router1

HTTPS Using Default Port Participating in DNS Example

https://router1

HTTP Using Non-Default Port Participating in DNS Example

http://router1:94

HTTPS Using Non-Default Port Participating in DNS Example

https://router1:530/

Step 3 If prompted, enter your username and password. The username and password combination required to enter the web user interface is the same combination required to access the router.

Step 4 The graphics-based web user interface similar to Figure 12-2 in the “Graphics-Based Web User Interface Overview” section on page 12-3 should appear in your web browser.


OL-16506-08

Chapter 12 Configuring and Accessing the Web User Interface Using Auto-Refresh

Using Auto-RefreshThe web user interface does not refresh content automatically by default.

To set an auto-refresh interval, follow these steps:

Step 1 Check the Refresh every check box on the graphical web user interface home page. A check mark appears in the check box (See Figure 12-3).

Figure 12-3 Checking Auto-Refresh Check Box

Step 2 Set the frequency of the auto-refresh interval using the drop-down menu.

Step 3 Click the Start button to the right of the drop-down menu. After hitting this button, the Start button becomes the Stop button and a countdown timer placed to the right of the Stop button begins to increment (See Figure 12-4).

Figure 12-4 Auto-Refresh Counter Example

The web user interface screen refreshes every time this counter reaches 0 seconds.

If you would like to stop the auto-refresh update, click the Stop button to return to the default setting of no auto-refresh update.


OL-16506-08

Chapter 12 Configuring and Accessing the Web User Interface Web User Interface Tips and Tricks

Web User Interface Tips and TricksThis section provides some useful information about using the web user interface once the interface has been accessed:

• If you know a Cisco IOS command-line interface command to gather information that you are unable to gather using the web user interface, you can click IOS Web UI followed by Monitor the Router to enter commands.

• If you know a diagnostic mode command to gather information that you are unable to gather using the web user interface, you can click WebCLI to enter show commands.

• The WebCLI command line has a context-sensitive help feature that shows the options available in a certain keyword sequence using a drop-down menu. See Figure 12-5 for an example of this drop-down menu context-sensitive help feature.

Figure 12-5 Web CLI Drop-Down Menu


OL-16506-08


C H A P T E R A
Unsupported Commands
The Cisco ASR 1000 Series Routers contain a series of commands with the platform keyword that either produce no output or produce output that is not useful for customer purposes. Although some commands with the platform keyword produce output that is useful for customer purposes, and are therefore documented in the Cisco IOS XE command references, the vast majority of these commands are not useful for customer purposes and are therefore considered unsupported.

Because these commands are considered unsupported, you will not find any further Cisco documentation for any of these commands.

The list of unsupported commands for the Cisco ASR 1000 Series Routers:

• clear platform hardware cpp

• clear platform software access-list

• clear platform software adjacency

• clear platform software cce

• clear platform software cef

• clear platform software cman

• clear platform software dpidb

• clear platform software ess

• clear platform software icmp

• clear platform software infrastructure

• clear platform software inspect

• clear platform software mlp

• clear platform software mpls

• clear platform software multicast

• clear platform software nat

• clear platform software nbar

• clear platform software netflow

• clear platform software pam

• clear platform software qos

• clear platform software route-map

• clear platform software shell

A-1ion Services Routers Software Configuration Guide

Appendix A Unsupported Commands

• clear platform software wccp

• clear platform software zone

• clear platform software zone-pair

• debug platform all

• debug platform hardware cpp

• debug platform software acl

• debug platform software adjacency

• debug platform software cce

• debug platform software cef

• debug platform software cman

• debug platform software configuration

• debug platform software dpidb

• debug platform software entity

• debug platform software ess

• debug platform software FPM

• debug platform software icmp

• debug platform software infrastructure

• debug platform software inspect

• debug platform software iphc

• debug platform software ipsec

• debug platform software issu

• debug platform software kernel

• debug platform software liin

• debug platform software marmot

• debug platform software mlp

• debug platform software mpls

• debug platform software multicast

• debug platform software nat

• debug platform software nbar

• debug platform software netflow

• debug platform software pam

• debug platform software qos

• debug platform software route-map

• debug platform software shell

• debug platform software urpf

• debug platform software vty

• debug platform software wccp

• debug platform software zone

A-2Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08


• show crypto engine

• show platform hardware cpp (all commands)

• show platform software access-list

• show platform software adjacency

• show platform software bound-uds

• show platform software cce statistics

• show platform software cef counters

• show platform software cman statistics

• show platform software common-classification

• show platform software debug

• show platform software diagnostic

• show platform software dpidb

• show platform software erspan

• show platform software ess

• show platform software firewall

• show platform software flow-control identifier

• show platform software fpm

• show platform software frame relay

• show platform software icmp

• show platform software icmp6

• show platform software infrastructure

• show platform software inspect statistics

• show platform software interface

• show platform software ip

• show platform software ipc

• show platform software iphc

• show platform software ipsec

• show platform software ipv6

• show platform software loadinfo

• show platform software mlist

• show platform software mlp

• show platform software mlppp

• show platform software module

• show platform software mpls

• show platform software multicast

• show platform software nat

• show platform software nbar

• show platform software netflow


OL-16506-08


• show platform software object-manager

• show platform software os-interface

• show platform software pam

• show platform software peer

• show platform software punt

• show platform software push-counter

• show platform software qos

• show platform software route-map

• show platform software sbc tables

• show platform software shell

• show platform software slot

• show platform software spi4

• show platform software urpf

• show platform software vlans

• show platform software vty

• show platform software wccp

• show platform software zone statistics

• test platform hardware eobc

• test platform hardware port

• test platform hardware slot

• test platform hardware subslot

• test platform software cef

• test platform software chassis

• test platform software debug

• test platform software forwarding-manager

• test platform software infrastructure

• test platform software inject

• test platform software process

• test platform software shell

• test platform software tdl

• test platform software trace


OL-16506-08

Cisco ASR 1000 Series Aggregation SeOL-16506-08

A
P P E N D I X B Configuration Examples
This appendix is designed to provide examples of how some common networking tasks can be accomplished on the Cisco ASR 1000 Series Routers. The examples in this appendix are provided for illustrative purposes only; little or no context is given with these examples. See the other chapters in this book (in particular Chapter 3, Consolidated Packages and Sub-Package Management), for more detailed explanations of the examples in this section.

When reading this section, also be aware that networking configurations are complex and can be configured many ways. The examples in this section simply show one method of accomplishing a configuration.

This appendix contains the following examples:

• Configuring Router to Boot Consolidated Package on TFTP Server, page B-1

• Copying Consolidated Package from TFTP Server to Router, page B-5

• Configuring Router to Boot Using Consolidated Package Stored on Router, page B-6

• Extracting Sub-Packages from a Consolidated Package into the Same File System, page B-7

• Extracting Sub-Packages from a Consolidated Package into a Different File System, page B-8

• Configuring Router to Boot Using Sub-Packages, page B-9

• Backing up Configuration Files, page B-13

• Enabling Second IOS Process on Single RP Using SSO, page B-14

• ISSU—Consolidated Package Upgrade, page B-19

Configuring Router to Boot Consolidated Package on TFTP Server

Router(config)# boot system tftp://172.17.16.81/auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin Router(config)#config-reg 0x2102Router(config)# exit *May 29 21:51:11.963: %SYS-5-CONFIG_I: Configured from console by user on console Router# show run | include bootboot-start-markerboot system tftp://172.17.16.81/auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.binboot-end-marker

B-1rvices Routers Software Configuration Guide

Appendix B Configuration Examples Configuring Router to Boot Consolidated Package on TFTP Server

Router# copy run startDestination filename [startup-config]? Building configuration...[OK]Router# reloadProceed with reload? [confirm]

*May 29 21:52:01.500: %SYS-5-RELOAD: Reload requested by user on console. Reload Reason: Reload command.


Current image running: Boot ROM0Last reset cause: LocalSoft

ASR1000-RP1 platform with 4194303 Kbytes of main memory

IP_ADDRESS: 172.17.52.155 IP_SUBNET_MASK: 255.255.255.0 DEFAULT_GATEWAY: 172.17.52.1 TFTP_SERVER: 172.17.16.81 TFTP_FILE: auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.binUsing midplane macaddr TFTP_MACADDR: 00:1a:30:46:e3:ff TFTP_VERBOSE: Progress TFTP_RETRY_COUNT: 18 TFTP_TIMEOUT: 7200 TFTP_CHECKSUM: Yes ETHER_PORT: 3 ETHER_SPEED_MODE: Auto Detectlink up 100Mbps/HDReceiving auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin from 172.17.16.81 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!File reception completed.Boot image size = 208904396 (0xc73a0cc) bytes

Using midplane macaddrPackage header rev 0 structure detectedCalculating SHA-1 hash...donevalidate_package: SHA-1 hash: calculated fb456e80:4ba2fa07:8556d27c:ea643e4f:512236df expected fb456e80:4ba2fa07:8556d27c:ea643e4f:512236df

B-2Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide

OL-16506-08


Image validated

PPC/IOS XE loader version: 0.0.3loaded at: 00800000 0CF3C004zimage at: 00807673 009B92D6initrd at: 009BA000 01041CC9isord at: 01042000 0CF39800avail ram: 00400000 00800000

Kernel load: Uncompressing image... dst: 00000000 lim: 00400000 start: 00807673 size: 001B1C63...done.Now booting the IOS XE kernel%IOSXEBOOT-4-BOOT_SRC: (rp/0): Non-HD Boot%IOSXEBOOT-4-BOOT_PARAMETER: (rp/0): Booting with custom BOOT_PARAM setting

Restricted Rights Legend

Use, duplication, or disclosure by the Government issubject to restrictions as set forth in subparagraph(c) of the Commercial Computer Software - RestrictedRights clause at FAR sec. 52.227-19 and subparagraph(c) (1) (ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS sec. 252.227-7013.

cisco Systems, Inc. 170 West Tasman Drive San Jose, California 95134-1706

Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version 12.2(33)XNA, RELEASE SOFTWARE (fc1)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2008 by Cisco Systems, Inc.Compiled Thu 01-May-08 00:29 by mcpreImage text-base: 0x10064AF0, data-base: 0x137E0958

Cisco IOS-XE software, Copyright (c) 1986-2008 by Cisco Systems, Inc.All rights reserved. Certain components of Cisco IOS-XE software arelicensed under the GNU General Public License ("GPL") Version 2.0. Thesoftware code licensed under GPL Version 2.0 is free software that comeswith ABSOLUTELY NO WARRANTY. You can redistribute and/or modify suchGPL code under the terms of GPL Version 2.0. For more details, see thedocumentation or "License Notice" file accompanying the IOS-XE software,or the applicable URL provided on the flyer accompanying the IOS-XEsoftware.

This product contains cryptographic features and is subject to UnitedStates and local country laws governing import, export, transfer anduse. Delivery of Cisco cryptographic products does not implythird-party authority to import, export, distribute or use encryption.Importers, exporters, distributors and users are responsible forcompliance with U.S. and local country laws. By using this product youagree to comply with applicable laws and regulations. If you are unableto comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:http://www.cisco.com/wwl/export/crypto/tool/stqrg.html


OL-16506-08


If you require further assistance please contact us by sending email [email protected].

cisco ASR1006 (RP1) processor with 1772131K/6147K bytes of memory.5 Gigabit Ethernet interfaces2 Packet over SONET interfaces2 Channelized T3 ports32768K bytes of non-volatile configuration memory.4194304K bytes of physical memory.921599K bytes of eUSB flash at bootflash:.39004543K bytes of SATA hard disk at harddisk:.Duplex is configured.Remove duplex configuration before enabling auto-negotiation



Username: userPassword:

Router>enPassword: Router# show versionCisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version 12.2(33)XNA, RELEASE SOFTWARE (fc1)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2008 by Cisco Systems, Inc.Compiled Thu 01-May-08 00:29 by mcpre


ROM: IOS-XE ROMMON

Router uptime is 2 minutesUptime for this control processor is 4 minutesSystem returned to ROM by reload at 14:52:01 DST Thu May 29 2008System image file is "tftp://172.17.16.81/auto/tftp-users/user/asr1000rp1-adve"Last reload reason: Reload command



If you require further assistance please contact us by sending email to


OL-16506-08

Appendix B Configuration Examples Copying Consolidated Package from TFTP Server to Router

[email protected].

cisco ASR1006 (RP1) processor with 1772131K/6147K bytes of memory.5 Gigabit Ethernet interfaces8 Serial interfaces8 Channelized T1 ports2 Packet over SONET interfaces2 Channelized T3 ports32768K bytes of non-volatile configuration memory.4194304K bytes of physical memory.921599K bytes of eUSB flash at bootflash:.39004543K bytes of SATA hard disk at harddisk:.


Copying Consolidated Package from TFTP Server to Router Router# dir bootflash:Directory of bootflash:/

11 drwx 16384 Dec 4 2007 04:32:46 -08:00 lost+found86401 drwx 4096 Dec 4 2007 06:06:24 -08:00 .ssh14401 drwx 4096 Dec 4 2007 06:06:36 -08:00 .rollback_timer28801 drwx 4096 Mar 18 2008 17:31:17 -07:00 .prst_sync43201 drwx 4096 Dec 4 2007 04:34:45 -08:00 .installer 13 -rw- 45977 Apr 9 2008 16:48:46 -07:00 target_support_output.tgz.tgz

928862208 bytes total (712273920 bytes free)Router# copy tftp bootflash:Address or name of remote host []? 172.17.16.81Source filename []? /auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.binDestination filename [asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin]? Accessing tftp://172.17.16.81//auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin...Loading /auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin from 172.17.16.81 (via GigabitEthernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 208904396 bytes]

208904396 bytes copied in 330.453 secs (632176 bytes/sec)Router# dir bootflash:Directory of bootflash:/

11 drwx 16384 Dec 4 2007 04:32:46 -08:00 lost+found86401 drwx 4096 Dec 4 2007 06:06:24 -08:00 .ssh14401 drwx 4096 Dec 4 2007 06:06:36 -08:00 .rollback_timer28801 drwx 4096 Mar 18 2008 17:31:17 -07:00 .prst_sync43201 drwx 4096 Dec 4 2007 04:34:45 -08:00 .installer 12 -rw- 208904396 May 28 2008 16:17:34 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin


OL-16506-08

Appendix B Configuration Examples Configuring Router to Boot Using Consolidated Package Stored on Router

13 -rw- 45977 Apr 9 2008 16:48:46 -07:00 target_support_output.tgz.tgz


Configuring Router to Boot Using Consolidated Package Stored on Router




Router# config tEnter configuration commands, one per line. End with CNTL/Z.Router(config)#boot system bootflash:asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.binRouter(config)#config-reg 0x2102Router(config)#exitRouter#show run | include bootboot-start-markerboot system bootflash:asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.binboot-end-markerRouter# copy run startDestination filename [startup-config]? Building configuration...[OK]Router# reload<output removed for brevity>User Access Verification


Router>enPassword: Router#show versionCisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version 12.2(33)XNA, RELEASE SOFTWARE (fc1)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2008 by Cisco Systems, Inc.Compiled Thu 01-May-08 00:29 by mcpre

Cisco IOS-XE software, Copyright (c) 1986-2008 by Cisco Systems, Inc.All rights reserved. Certain components of Cisco IOS-XE software arelicensed under the GNU General Public License ("GPL") Version 2.0. Thesoftware code licensed under GPL Version 2.0 is free software that comeswith ABSOLUTELY NO WARRANTY. You can redistribute and/or modify suchGPL code under the terms of GPL Version 2.0. For more details, see thedocumentation or "License Notice" file accompanying the IOS-XE software,or the applicable URL provided on the flyer accompanying the IOS-XE


OL-16506-08

Appendix B Configuration Examples Extracting Sub-Packages from a Consolidated Package into the Same File System

software.

ROM: IOS-XE ROMMON

Router uptime is 3 minutesUptime for this control processor is 5 minutesSystem returned to ROM by reload at 16:20:55 DST Wed May 28 2008System image file is "bootflash:asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin"Last reload reason: Reload command






Extracting Sub-Packages from a Consolidated Package into the Same File System

The asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin consolidated package file is in bootflash, but no sub-packages are in the directory.




OL-16506-08

Appendix B Configuration Examples Extracting Sub-Packages from a Consolidated Package into a Different File System




After entering the request platform software package expand file bootflash:asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin command, noting that the to option is not used, the sub-packages are extracted from the consolidated package into bootflash:.




Extracting Sub-Packages from a Consolidated Package into a Different File System

The asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin consolidated package file is in usb0:




No sub-packages are in the bootflash: directory.


OL-16506-08

Appendix B Configuration Examples Configuring Router to Boot Using Sub-Packages


11 drwx 16384 Dec 13 2004 03:45:47 -08:00 lost+found87937 drwx 4096 Dec 13 2004 03:46:45 -08:00 .rollback_timer14657 drwx 4096 Dec 13 2004 03:47:17 -08:00 .installer29313 drwx 4096 Dec 13 2004 03:53:00 -08:00 .ssh 12 -rw- 33554432 Dec 13 2004 03:53:49 -08:00 nvram_0010058625 drwx 4096 May 7 2008 17:27:51 -07:00 .prst_sync


Router# request platform software package expand file usb0:asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin to bootflash:Verifying parametersValidating package typeCopying package filesSUCCESS: Finished expanding all-in-one software package.

After the request platform software package expand file usb0:asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin to bootflash: command is entered, the sub-packages are now in the bootflash: directory.


11 drwx 16384 Dec 13 2004 03:45:47 -08:00 lost+found87937 drwx 4096 Dec 13 2004 03:46:45 -08:00 .rollback_timer14657 drwx 4096 Dec 13 2004 03:47:17 -08:00 .installer29313 drwx 4096 Dec 13 2004 03:53:00 -08:00 .ssh 12 -rw- 33554432 Dec 13 2004 03:53:49 -08:00 nvram_0010043979 -rw- 47071436 May 27 2008 14:25:01 -07:00 asr1000rp1-espbase.02.01.00.122-33.XNA.pkg58625 drwx 4096 May 7 2008 17:27:51 -07:00 .prst_sync43970 -rw- 5740 May 27 2008 14:25:00 -07:00 asr1000rp1-packages-adventerprisek9.02.01.00.122-33.XNA.conf43980 -rw- 20334796 May 27 2008 14:25:01 -07:00 asr1000rp1-rpaccess.02.01.00.122-33.XNA.pkg43981 -rw- 22294732 May 27 2008 14:25:02 -07:00 asr1000rp1-rpbase.02.01.00.122-33.XNA.pkg43982 -rw- 21946572 May 27 2008 14:25:03 -07:00 asr1000rp1-rpcontrol.02.01.00.122-33.XNA.pkg43983 -rw- 48099532 May 27 2008 14:25:04 -07:00 asr1000rp1-rpios-adventerprisek9.02.01.00.122-33.XNA.pkg43984 -rw- 34324684 May 27 2008 14:25:05 -07:00 asr1000rp1-sipbase.02.01.00.122-33.XNA.pkg43985 -rw- 22124748 May 27 2008 14:25:05 -07:00 asr1000rp1-sipspa.02.01.00.122-33.XNA.pkg43971 -rw- 6256 May 27 2008 14:25:05 -07:00 packages.conf


Configuring Router to Boot Using Sub-PackagesEnter the dir bootflash: command to confirm all sub-packages and the provisioning file are in the same file system:



OL-16506-08




Router# show running-config | include bootboot-start-markerboot-end-markerRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# boot system bootflash:packages.confRouter(config)# config-reg 0x2102Router(config)# exitRouter# config t*May 29 22:47:57.433: %SYS-5-CONFIG_I: Configured from console by userRouter# show running-config | include bootboot-start-markerboot system bootflash:packages.confboot-end-markerRouter# copy run startDestination filename [startup-config]? Building configuration...[OK]Router# reloadProceed with reload? [confirm]






OL-16506-08


Located packages.conf Image size 6256 inode num 57603, bks cnt 2 blk size 8*512#Located asr1000rp1-rpbase.02.01.00.122-33.XNA.pkg Image size 22294732 inode num 57606, bks cnt 5444 blk size 8*512#########################################################################################################################################################################################################################Boot image size = 22294732 (0x15430cc) bytes

Using midplane macaddrPackage header rev 0 structure detectedCalculating SHA-1 hash...donevalidate_package: SHA-1 hash: calculated 4ad33773:e1cb7492:db502416:4ad586f2:7c4d9701 expected 4ad33773:e1cb7492:db502416:4ad586f2:7c4d9701Image validated

PPC/IOS XE loader version: 0.0.3loaded at: 00800000 01D45004zimage at: 00807673 009B92D6initrd at: 009BA000 01041CC9isord at: 01042000 01D42800avail ram: 00400000 00800000






Cisco IOS-XE software, Copyright (c) 1986-2008 by Cisco Systems, Inc.All rights reserved. Certain components of Cisco IOS-XE software arelicensed under the GNU General Public License ("GPL") Version 2.0. Thesoftware code licensed under GPL Version 2.0 is free software that comeswith ABSOLUTELY NO WARRANTY. You can redistribute and/or modify suchGPL code under the terms of GPL Version 2.0. For more details, see thedocumentation or "License Notice" file accompanying the IOS-XE software,or the applicable URL provided on the flyer accompanying the IOS-XE


OL-16506-08


software.




cisco ASR1006 (RP1) processor with 1776227K/6147K bytes of memory.5 Gigabit Ethernet interfaces2 Packet over SONET interfaces2 Channelized T3 ports32768K bytes of non-volatile configuration memory.4194304K bytes of physical memory.921599K bytes of eUSB flash at bootflash:.39004543K bytes of SATA hard disk at harddisk:.Duplex is configured.Remove duplex configuration before enabling auto-negotiation

Press RETURN to get started!<some output removed for brevity?User Access Verification


Router> enablePassword:

Router# show versionCisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version 12.2(33)XNA, RELEASE SOFTWARE (fc1)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2008 by Cisco Systems, Inc.Compiled Thu 01-May-08 00:29 by mcpre


ROM: IOS-XE ROMMON

Router uptime is 1 minuteUptime for this control processor is 3 minutes


OL-16506-08

Appendix B Configuration Examples Backing up Configuration Files

System returned to ROM by reload at 15:51:54 DST Thu May 29 2008System image file is "bootflash:packages.conf"Last reload reason: Reload command






Backing up Configuration FilesThis section provides the following examples:

• Copying Startup Configuration File to Bootflash, page B-13

• Copying Startup Configuration File to USB Flash Disk, page B-14

• Copying Startup Configuration File to a TFTP Server, page B-14

Copying Startup Configuration File to BootflashRouter# dir bootflash:Directory of bootflash:/

11 drwx 16384 Dec 4 2007 04:32:46 -08:00 lost+found86401 drwx 4096 Dec 4 2007 06:06:24 -08:00 .ssh14401 drwx 4096 Dec 4 2007 06:06:36 -08:00 .rollback_timer28801 drwx 4096 May 29 2008 16:31:41 -07:00 .prst_sync43201 drwx 4096 Dec 4 2007 04:34:45 -08:00 .installer 12 -rw- 208904396 May 28 2008 16:17:34 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin

Router# copy nvram:startup-config bootflash:Destination filename [startup-config]?


OL-16506-08

Appendix B Configuration Examples Enabling Second IOS Process on Single RP Using SSO



11 drwx 16384 Dec 4 2007 04:32:46 -08:00 lost+found86401 drwx 4096 Dec 4 2007 06:06:24 -08:00 .ssh14401 drwx 4096 Dec 4 2007 06:06:36 -08:00 .rollback_timer28801 drwx 4096 May 29 2008 16:31:41 -07:00 .prst_sync43201 drwx 4096 Dec 4 2007 04:34:45 -08:00 .installer 12 -rw- 208904396 May 28 2008 16:17:34 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin13 -rw- 7516 Jul 2 2008 15:01:39 -07:00 startup-config

Copying Startup Configuration File to USB Flash DiskRouter# dir usb0:Directory of usb0:/



Router# copy nvram:startup-config usb0:Destination filename [startup-config]?



43261 -rwx 208904396 May 27 2008 14:10:20 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin43262 -rwx 3172 Jul 2 2008 15:40:45 -07:00 startup-config


Copying Startup Configuration File to a TFTP ServerRouter# copy bootflash:startup-config tftp:Address or name of remote host []? 172.17.16.81Destination filename [pe24_asr-1002-confg]? /auto/tftp-users/user/startup-config!!3517 bytes copied in 0.122 secs (28828 bytes/sec)

Enabling Second IOS Process on Single RP Using SSO The show platform command output does not indicate a second IOS process is active:


Slot Type State Insert time (ago) --------- ------------------- --------------------- -----------------


OL-16506-08


0 ASR1000-SIP10 ok 00:04:39 0/0 SPA-5X1GE-V2 ok 00:03:23 0/1 SPA-2XT3/E3 ok 00:03:18 R0 ASR1000-RP1 ok, active 00:04:39 F0 ASR1000-ESP10 ok, active 00:04:39 P0 ASR1004-PWR-AC ok 00:03:52 P1 ASR1004-PWR-AC ok 00:03:52


The show redundancy states command output shows that the redundancy state is non-redundant:


Redundancy Mode (Operational) = Non-redundantRedundancy Mode (Configured) = Non-redundantRedundancy State = Non Redundant Maintenance Mode = Disabled Manual Swact = disabled (system is simplex (no peer unit)) Communications = Down Reason: Simplex mode


SSO is configured:

Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# redundancyRouter(config-red)# mode sso*May 27 19:43:43.539: %CMRP-6-DUAL_IOS_REBOOT_REQUIRED: R0/0: cmand: Configuration must be saved and the chassis must be rebooted for IOS redundancy changes to take effectRouter(config-red)# exitRouter(config)# exitRouter#show*May 27 19:44:04.173: %SYS-5-CONFIG_I: Configured from console by user on console

The show redundancy states command output now indicates that SSO is configured but not operational:


Redundancy Mode (Operational) = Non-redundantRedundancy Mode (Configured) = ssoRedundancy State = Non Redundant Maintenance Mode = Disabled Manual Swact = disabled (system is simplex (no peer unit)) Communications = Down Reason: Simplex mode



OL-16506-08


The show platform command output continues to show a second IOS process is still not running:


Slot Type State Insert time (ago) --------- ------------------- --------------------- ----------------- 0 ASR1000-SIP10 ok 00:05:53 0/0 SPA-5X1GE-V2 ok 00:04:37 0/1 SPA-2XT3/E3 ok 00:04:32 R0 ASR1000-RP1 ok, active 00:05:53 F0 ASR1000-ESP10 ok, active 00:05:53 P0 ASR1004-PWR-AC ok 00:05:06 P1 ASR1004-PWR-AC ok 00:05:06


Router# copy running-config startup-configDestination filename [startup-config]? Building configuration...[OK]

The router needs to be reloaded after saving the running configuration to make SSO the operational redundancy mode.

Router# reloadProceed with reload? [confirm]





Located packages.conf Image size 6256 inode num 43971, bks cnt 2 blk size 8*512#Located asr1000rp1-rpbase.02.01.00.122-33.XNA.pkg Image size 22294732 inode num 43974, bks cnt 5444 blk size 8*512#########################################################################################################################################################################################################################Boot image size = 22294732 (0x15430cc) bytes

Using midplane macaddrPackage header rev 0 structure detectedCalculating SHA-1 hash...donevalidate_package: SHA-1 hash: calculated 4ad33773:e1cb7492:db502416:4ad586f2:7c4d9701 expected 4ad33773:e1cb7492:db502416:4ad586f2:7c4d9701Image validated


OL-16506-08


PPC/IOS XE loader version: 0.0.3loaded at: 00800000 01D45004zimage at: 00807673 009B92D6initrd at: 009BA000 01041CC9isord at: 01042000 01D42800avail ram: 00400000 00800000









If you require further assistance please contact us by sending email to


OL-16506-08


[email protected].

cisco ASR1004 (RP1) processor with 752227K/6147K bytes of memory.5 Gigabit Ethernet interfaces32768K bytes of non-volatile configuration memory.4194304K bytes of physical memory.937983K bytes of eUSB flash at bootflash:.39004543K bytes of SATA hard disk at harddisk:.253424K bytes of USB flash at usb0:.

Press RETURN to get started!

<some output omitted for brevity>



Router> enablePassword:

The show platform command output now indicates a second IOS process is active on RP 0.


Slot Type State Insert time (ago) --------- ------------------- --------------------- ----------------- 0 ASR1000-SIP10 ok 00:29:34 0/0 SPA-5X1GE-V2 ok 00:28:13 0/1 SPA-2XT3/E3 ok 00:28:18 R0 ASR1000-RP1 ok 00:29:34 R0/0 ok, active 00:29:34 R0/1 ok, standby 00:27:49 F0 ASR1000-ESP10 ok, active 00:29:34 P0 ASR1004-PWR-AC ok 00:28:47 P1 ASR1004-PWR-AC ok 00:28:47


The show redundancy states command shows SSO as the operational redundancy mode.

Router# show redundancy states my state = 13 -ACTIVE peer state = 8 -STANDBY HOT Mode = Duplex Unit ID = 48

Redundancy Mode (Operational) = ssoRedundancy Mode (Configured) = ssoRedundancy State = sso Maintenance Mode = Disabled Manual Swact = enabled Communications = Up


OL-16506-08

Appendix B Configuration Examples ISSU—Consolidated Package Upgrade


ISSU—Consolidated Package UpgradeIn the following example, ISSU is used to upgrade two RPs in the same Cisco ASR 1000 Series Router to consolidated packages. The RPs are being upgraded from Cisco IOS XE Release 2.1.0, which uses Cisco IOS Release 12.2(33)XNA, to Cisco IOS XE Release 2.1.1, which uses Cisco IOS Release 12.2(33)XNA1.

The example starts with the user logged into RP 0, the active RP.

Router# show version Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version 12.2(33)XNA, RELEASE SOFTWARE (fc1)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2008 by Cisco Systems, Inc.Compiled Thu 01-May-08 00:29 by mcpre


ROM: IOS-XE ROMMON

Router uptime is 2 weeks, 2 hours, 54 minutesUptime for this control processor is 1 hour, 7 minutesSystem returned to ROM by reload at 15:24:15 DST Mon Jul 21 2008System image file is "bootflash:asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin"Last reload reason: redundancy force-switchover




cisco ASR1006 (RP1) processor with 1772131K/6147K bytes of memory.8 FastEthernet interfaces5 Gigabit Ethernet interfaces


OL-16506-08


8 Serial interfaces8 Channelized T1 ports2 Packet over SONET interfaces2 Channelized T3 ports32768K bytes of non-volatile configuration memory.4194304K bytes of physical memory.921599K bytes of eUSB flash at bootflash:.39004543K bytes of SATA hard disk at harddisk:.



11 drwx 16384 Dec 4 2007 04:32:46 -08:00 lost+found86401 drwx 4096 Dec 4 2007 06:06:24 -08:00 .ssh14401 drwx 4096 Dec 4 2007 06:06:36 -08:00 .rollback_timer28801 drwx 4096 Jul 21 2008 15:29:25 -07:00 .prst_sync43201 drwx 4096 Dec 4 2007 04:34:45 -08:00 .installer 12 -rw- 208904396 May 28 2008 16:17:34 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin13 -rw- 7516 Jul 2 2008 15:01:39 -07:00 startup-config 14 -rw- 45977 Apr 9 2008 16:48:46 -07:00 target_support_output.tgz.tgz


Router# dir stby-bootflash:Directory of stby-bootflash:/

11 drwx 16384 Dec 13 2004 03:45:47 -08:00 lost+found87937 drwx 4096 Jul 17 2008 16:43:34 -07:00 .rollback_timer14657 drwx 4096 Jul 17 2008 16:43:34 -07:00 .installer29313 drwx 4096 Dec 13 2004 03:53:00 -08:00 .ssh 12 -rw- 33554432 Dec 13 2004 03:53:49 -08:00 nvram_00100 13 -rw- 208904396 Jun 5 2008 20:12:53 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin58625 drwx 4096 Jul 21 2008 15:32:59 -07:00 .prst_sync


Router# copy tftp bootflash:Address or name of remote host []? 172.17.16.81 Source filename []? /auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin Destination filename [asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin]? Accessing tftp://172.17.16.81//auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin...Loading /auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin from 172.17.16.81 (via GigabitEthernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 209227980 bytes]



OL-16506-08


Router# copy bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin stby-bootflash: Destination filename [asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin]? Copy in progress...CCCCCCCC <output removed for brevity>209227980 bytes copied in 434.790 secs (481216 bytes/sec)


11 drwx 16384 Dec 4 2007 04:32:46 -08:00 lost+found86401 drwx 4096 Dec 4 2007 06:06:24 -08:00 .ssh14401 drwx 4096 Dec 4 2007 06:06:36 -08:00 .rollback_timer28801 drwx 4096 Jul 21 2008 15:29:25 -07:00 .prst_sync43201 drwx 4096 Dec 4 2007 04:34:45 -08:00 .installer 12 -rw- 208904396 May 28 2008 16:17:34 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin 15 -rw- 7516 Jul 2 2008 15:01:39 -07:00 startup-config 13 -rw- 45977 Apr 9 2008 16:48:46 -07:00 target_support_output.tgz.tgz 16 -rw- 209227980 Jul 17 2008 16:06:58 -07:00 asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin

928862208 bytes total (76644352 bytes free)Router# dir stby-bootflash:Directory of stby-bootflash:/

11 drwx 16384 Dec 13 2004 03:45:47 -08:00 lost+found87937 drwx 4096 Jul 17 2008 16:43:34 -07:00 .rollback_timer14657 drwx 4096 Jul 17 2008 16:43:34 -07:00 .installer29313 drwx 4096 Dec 13 2004 03:53:00 -08:00 .ssh 12 -rw- 33554432 Dec 13 2004 03:53:49 -08:00 nvram_00100 13 -rw- 208904396 Jun 5 2008 20:12:53 -07:00 asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin58625 drwx 4096 Jul 21 2008 15:32:59 -07:00 .prst_sync 14 -rw- 209227980 Jul 17 2008 16:16:07 -07:00 asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin


Router# issu loadversion rp 1 file stby-bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin --- Starting installation state synchronization ---Finished installation state synchronization





Router#*Jul 21 23:34:27.206: %ASR1000_OIR-6-OFFLINECARD: Card (rp) offline in slot R1*Jul 21 23:34:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_NOT_PRESENT)*Jul 21 23:34:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)*Jul 21 23:34:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_REDUNDANCY_STATE_CHANGE)


OL-16506-08


*Jul 21 23:37:05.528: %ASR1000_OIR-6-ONLINECARD: Card (rp) online in slot R1*Jul 21 23:37:25.480: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_FOUND(4))

*Jul 21 23:37:25.480: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))Finished installation state synchronization

*Jul 21 23:37:26.349: %REDUNDANCY-3-IPC: IOS versions do not match.*Jul 21 23:38:47.172: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded*Jul 21 23:38:47.173: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)



Router#


<additional output removed for brevity>

*Jul 21 23:43:31.970: %SYS-5-RESTART: System restarted --Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version 12.2(33)XNA, RELEASE SOFTWARE (fc1)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2008 by Cisco Systems, Inc.Compiled Thu 01-May-08 00:29 by mcpre*Jul 21 23:43:31.978: %SSH-5-ENABLED: SSH 1.99 has been enabled*Jul 21 23:43:35.196: Relay: standby progression done*Jul 21 23:43:35.197: %PLATFORM-6-RF_PROG_SUCCESS: RF state STANDBY HOT

At this point of the process, the user has to log onto RP1, which started the upgrade as the standby RP but is the active RP after the switchover.

The following commands are entered from RP1:


Router# issu commitversion--- Starting installation changes ---Cancelling rollback timerSaving image changesFinished installation changes


Router# show versionCisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version 12.2(33)XNA1, RELEASE SOFTWARE (fc1)


OL-16506-08


Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2008 by Cisco Systems, Inc.Compiled Tue 08-Jul-08 14:40 by mcpre


ROM: IOS-XE ROMMON

Router uptime is 2 weeks, 3 hours, 8 minutesUptime for this control processor is 11 minutesSystem returned to ROM by reload at 15:29:24 DST Mon Jul 21 2008System image file is "bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin"Last reload reason: EHSA standby down




cisco ASR1006 (RP1) processor with 1772046K/6147K bytes of memory.8 FastEthernet interfaces5 Gigabit Ethernet interfaces8 Serial interfaces8 Channelized T1 ports2 Packet over SONET interfaces2 Channelized T3 ports32768K bytes of non-volatile configuration memory.4194304K bytes of physical memory.937983K bytes of eUSB flash at bootflash:.39004543K bytes of SATA hard disk at harddisk:.253424K bytes of USB flash at usb0:.


Router# show running-config | include bootboot-start-markerboot system bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.binboot system bootflash:asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.binboot-end-markerRouter#


OL-16506-08


At this point of the procedure, the upgrade of RP1 is complete.

The following procedure uses the same steps to upgrade RP0. The user is still on RP1 when this process begins.


Slot Type State Insert time (ago) --------- ------------------- --------------------- ----------------- 0 ASR1000-SIP10 ok 00:16:10 0/0 SPA-5X1GE-V2 ok 00:10:50 0/1 SPA-8X1FE-TX-V2 ok 00:10:46 0/2 SPA-2XCT3/DS0 ok 00:10:42 1 ASR1000-SIP10 ok 00:16:10 1/0 SPA-2XOC3-POS ok 00:10:49 1/1 SPA-8XCHT1/E1 ok 00:10:45 1/2 SPA-2XT3/E3 ok 00:10:41 R0 ASR1000-RP1 ok, standby 00:16:10 R1 ASR1000-RP1 ok, active 00:16:10 F0 ASR1000-ESP10 ok, standby 00:16:10 F1 ASR1000-ESP10 ok, active 00:16:10 P0 ASR1006-PWR-AC ok 00:15:07 P1 ASR1006-FAN ok 00:15:07

Slot CPLD Version Firmware Version --------- ------------------- --------------------------------------- 0 06120701 12.2(33r)XN2 1 06120701 12.2(33r)XN2 R0 07082312 12.2(33r)XN2 R1 07062111 12.2(33r)XN2 F0 07051680 12.2(33r)XN2 F1 07051680 12.2(33r)XN2

Router# issu loadversion rp 0 file stby-bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin--- Starting installation state synchronization ---Finished installation state synchronization





Router#*Jul 21 23:53:41.218: %ASR1000_OIR-6-OFFLINECARD: Card (rp) offline in slot R0*Jul 21 23:53:41.256: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_NOT_PRESENT)*Jul 21 23:53:41.256: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)*Jul 21 23:53:41.256: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_REDUNDANCY_STATE_CHANGE)*Jul 21 23:53:42.423: %IP-4-DUPADDR: Duplicate address 172.29.52.155 on GigabitEthernet0, sourced by 001a.3046.e3ff*Jul 21 23:56:19.885: %ASR1000_OIR-6-ONLINECARD: Card (rp) online in slot R0


OL-16506-08


*Jul 21 23:56:39.324: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_FOUND(4))

*Jul 21 23:56:39.324: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))

*Jul 21 23:58:03.660: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded*Jul 21 23:58:03.661: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)



Router#


<Output removed for brevity>

After the switchover, the user must log onto RP0.

The remaining commands are all entered from RP0:



*Jul 22 00:10:45.488: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded*Jul 22 00:10:45.489: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)--- Starting installation changes ---Cancelling rollback timerSaving image changesFinished installation changes


Router# show versionCisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version 12.2(33)XNA1, RELEASE SOFTWARE (fc1)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2008 by Cisco Systems, Inc.Compiled Tue 08-Jul-08 14:40 by mcpre



OL-16506-08


ROM: IOS-XE ROMMON

Router uptime is 2 weeks, 3 hours, 33 minutesUptime for this control processor is 16 minutesSystem returned to ROM by reload at 15:24:15 DST Mon Jul 21 2008System image file is "bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin"Last reload reason: EHSA standby down




cisco ASR1006 (RP1) processor with 1772046K/6147K bytes of memory.8 FastEthernet interfaces5 Gigabit Ethernet interfaces8 Serial interfaces8 Channelized T1 ports2 Packet over SONET interfaces2 Channelized T3 ports32768K bytes of non-volatile configuration memory.4194304K bytes of physical memory.921599K bytes of eUSB flash at bootflash:.39004543K bytes of SATA hard disk at harddisk:.


Router# show running-config | include bootboot-start-markerboot system bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.binboot system bootflash:asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.binboot-end-markerRouter#


OL-16506-08


I N D E X

Symbols

<cr> 2-9

? command 2-9

A

ASR1000-ESP10-N, troubleshooting 3-17

ASR1004 Series Routers, software compatibility 4-1

Assigning a MAC Address 10-2

auxiliary port, using 2-4

B

Bidirectional Forwarding Detection (BFD) 5-5

C

call home destination profiles

displaying 6-34

carriage return (<cr>) 2-9

cautions, usage in text i-xvi

Chassis Manager, Overview 1-6

Cisco ASR1002 Series Router, software compatibility 4-1

Cisco ASR1006 Series Router, software compatibility 4-1

Cisco IOS configuration changes, saving 2-13

command-line interface, getting help 2-9

command line processing 2-4

command modes, understanding 2-6

commands

context-sensitive help for abbreviating 2-9

default form, using 2-12

no form, using 2-12

command syntax

conventions i-xv

displaying (example) 2-9

configuration files, backing up to bootflash

2-13

configuration files, backing up to TFTP 2-14

configuration files, backing up to USB Flash Disk 2-14

configuration files, backup example B-13

configuration files, managing 2-13

configurations, saving 2-13

Configuring Bridge Domain Interfaces 10-1

console, accessing 2-1

console, accessing using a direct connection 2-1

console, accessing using telnet 2-3

console, configuring a transport map 7-2

console, connecting 2-2

console, traffic handling 7-1

console, using 2-2

console, viewing handling configuration 7-12

consolidated package, managing and configuring 3-7

consolidated package, managing and configuring using request platform software package install command 3-8

consolidated package, managing and configuring using the copy command 3-7

consolidated package, running the router using 3-2

Consolidated Package boot from Router, example B-6

consolidated package boot using TFTP, example B-1

consolidated packages, managing and configuring 3-6

consolidated packages, overview 1-2

consolidated packages, restrictions 1-2

consolidated package to TFTP server example B-5

copy command, command set overview 3-5

core directory, overview 1-9

CPP driver process, overview 1-7

IN-Iion Services Routers Software Configuration Guide

Index

CPP HA process, overview 1-7

CPP SP process, overview 1-7

crashinfo files, overview 1-9

D

device IDs

call home format 6-40

diagnostic configuration mode, summary of 2-7

diagnostic mode, overview 2-8

directories, autogenerated 1-9

directories, autogenerated directories 1-8

dual IOS processes on single RP, overview 4-6

E

e-mail notifications

Call Home 6-55

ESPBase, Overview 1-3

ESP board ASR1000-ESP10-N 3-17

F

field programmable hardware device upgrade 1-5

file management, command set overview 3-4

Files, autogenerated files 1-8

file systems, overview 1-8

filtering output, show and more commands 2-14

forwarding manager process, overview 1-6

G

global configuration mode, summary of 2-6

H

hardware, upgrading in the field 1-5

hardware platforms

IN-IICisco ASR 1000 Series Aggregation Services Routers Software Con

See platforms, supported

help command 2-9

history buffer, using 2-5

Host Manager, Overview 1-6

I

IDs

serial IDs 6-40

Information about a Bridge Domain Interface 10-1

In Service Software Upgrade, see ISSU 4-3

interface configuration mode, summary of 2-6

interface manager process, overview 1-6

IOS as a Process, Overview 1-7

IOS process, enabling second IOS process on single RP example B-14

IOS process, overview 1-6

IOS processes, dual IOS processes 1-7

IP Forwarding 10-3

IP Protocols 10-2

ISSU, compatability 4-5

ISSU, consolidated package upgrade example B-19

ISSU, Overview 4-3

ISSU, sub-packages ASR 1002 or 1004 4-72

ISSU, sub-packages dual RP 4-123

ISSU, upgrade procedures 4-123

ISSU and software compatibility 4-1

issu command, command set overview 3-5

ISSU restrictions 4-3

ISSU support, release 3.1S 4-3

K

keyboard shortcuts 2-4

L

LACP over EVC port channel

figuration GuideOL-16506-08

Index

configuration commands, configuration steps 9-5, 9-7, 9-8, 9-10

logger process, overview 1-6

lost+found directory, overview 1-9

M

Management Ethernet Interface, common tasks 8-3

Management Ethernet interface, interface numbering 8-2

Management Ethernet interface, IP Address Handling 8-2

Management Ethernet interface, overview 8-1

Management Ethernet Interface, VRF 8-2

modem, accessing 2-4

modes

See command modes

N

notes, usage in text i-xvi

P

Packet Forwarding 10-3

platforms, supported

release notes, identify using 2-16

pluggable services process, overview 1-7

privileged EXEC mode, summary of 2-6

processes, overview 1-5

prompts, system 2-6

provisioning files, important information 1-4

provisioning files, overview 1-4

Q

question mark (?) command 2-9

R

redundancy, hardware redundancy overview 5-1

Cisco ASR 1000 Series OL-16506-08

redundancy, software redundancy overview 5-3

release notes

See platforms, supported

request platform command set, overview 3-4

Restrictions for the Bridge Domain Interface 10-1

rommon image, overview 1-5

ROM monitor mode, summary of 2-8

Route Processor Redundancy, overview 5-4

RPAccess, Overview 1-3

RPBase, Overview 1-3

RPControl, Overview 1-3

RPIOS, Overview 1-3

RPR, Cisco ASR 1002 or 1004 4-72

S

Secure Shell (SSH), configuring persistent SSH 7-9

Secure Shell (SSH), persistent 7-2

Secure Shell (SSH), persistent SSH restrictions 7-17

Secure Shell (SSH), viewing handling configuration 7-12

serial IDs

description 6-40

server IDs

description 6-41

shell manager process, overview 1-7

show history command 2-5

SIPBase, Overview 1-3

SIPSPA, Overview 1-3

Software Modules, Overview 1-3

Software Packaging, Overview 1-1

source IDs

call home event format 6-40

SPA driver process, overview 1-7

SSO, using SSO to enable second IOS Process on single RP example B-14

Stateful Switchover (SSO), overview 5-4

Stateful Switchover, Supported Protocols and Applications 5-5

sub-package, copying and booting 3-14

IN-IIIAggregation Services Routers Software Configuration Guide

Index

sub-package boot, example B-9

sub-package extraction to different file system, example B-8

sub-package extraction to same file system, example B-7

sub-packages, extracting modules from image 3-10

sub-packages, managing and configuring 3-10

sub-packages, restrictions 1-3

sub-packages, running the router using 3-1

sub-packages, upgrading individual 3-18

Synchronous Ethernet Support 9-1

T

Tab key, command completion 2-9

telnet, configuring persistent telnet 7-5

telnet, persistent 7-2

telnet, persistent telnet restrictions 7-17

telnet, using 2-3

telnet, using to access console 2-3

telnet, viewing handling configuration 7-12

TFTP, copying consolidated package to example B-5

tftp boot, example B-1

tracelogs directory, overview 1-9

Tracing, how tracing works 11-1

Tracing, overview 11-1

Tracing, setting a tracing level 11-4

Tracing, tracing levels 11-2

Tracing, viewing a tracing level 11-3

Tracing, viewing trace logs 11-5

transport maps for web user interface, overview 12-4

U

upgrading field programmable hardware device 1-5

user EXEC mode, summary of 2-6

W

web user interface (graphics-based), overview 12-3

IN-IVCisco ASR 1000 Series Aggregation Services Routers Software Con

web user interface (legacy), overview 12-2

web user interface, accessing 12-8

web user interface, authentication 12-7

web user interface, DNS 12-7

web user interface, overview 12-1

web user interface, tricks and tips 12-10

web user interface, using auto-refresh 12-9

web user interface access, configuring 12-5

figuration GuideOL-16506-08