Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier ... · PDF fileCisco CRS-1 Carrier...

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration GuideCisco IOS XR Software Release 4.0

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

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.

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

CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1011R)

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide © 2011 Cisco Systems, Inc. All rights reserved.

Cisco CRS-1OL-13669-03

C O N T E N T S

Preface ix

Changes to This Document ix

Obtaining Documentation, Obtaining Support, and Security Guidelines ix

Migrating to a Cisco CRS-3 Carrier Routing System 1-1

Contents 1-1

CRS-1 to CRS-3 Software Migration Compatibility Matrix 1-2

Prerequisites for Upgrading IOS-XR Software Prior to Migrating to a Cisco CRS-3 Carrier Routing System 1-3

ROMMON Upgrades 1-4

OPTION-A 1-4

OPTION-B 1-4

Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3 1-5

Flash Disk Upgrade Process to 4GB 1-5

Inserting the 4GB Flashdisk 1-5

Disk Formatting 1-6

Verifying the Disk File System 1-6

Setting Up Disk Mirroring 1-6

Swapping Mirrored Disks 1-6

Verifying Standby RP Disk Upgrade 1-6

Performing Switchover 1-7

Upgrading the Standby RP 1-7

File System Upgrade Procedure for 2GB Flash Disks 1-7

Verifying that the System Meets RP Memory Requirements 1-9

IOS-XR Software Upgrade Procedure 1-9

Obtain the Required PIE Files 1-9

New Image Name Changes for 4.0 and Onwards 1-10

Verify System Stability 1-10

Additional Pre-upgrade System Checks 1-12

Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware 1-14

Post-Upgrade Procedure 1-16

Cisco CRS-3 Carrier Routing System and CRS-1 Carrier Routing System Hardware Compatibility Matrix 1-20

iii Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

Contents

Information About Migrating to a Cisco CRS-3 Carrier Routing System 1-21

How to Migrate to a Cisco CRS-3 Carrier Routing System (16-Slot) 1-23

Administratively Disabling the Fabric Plane 1-23

Disabling Power to the CRS-1 Fabric Card 1-25

Physically Removing the CRS-1 Fabric Card 1-27

Installing a CRS-3 Fabric Card 1-30

Verifying the Installation of the CRS-3 Fabric Card 1-35

Powering up the Replaced Fabric Card 1-37








Booting Up the Newly Migrated Cisco CRS-3 Fabric 1-54

Administratively Enabling the Fabric Plane 1-54

Verifying Traffic Statistics on the Newly Migrated Cisco CRS-3 Node 1-55

Verifying Fabric Link Connectivity 1-56








Booting Up the Newly Migrated Cisco CRS-3 Fabric 1-73


Verifying Traffic Statistics on the Newly Migrated Cisco CRS-3 Node 1-74


Configuration Examples for Migrating to a Cisco CRS-3 Carrier Routing System 1-80

Displaying Chassis Serial Numbers: Example 1-80

Adding a Fabric Card Chassis: Example 1-81

Adding an LCC to a Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis: Example 1-83

Where to Go Next 1-85

Additional References 1-86

Related Documents 1-86

ivCisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

OL-13669-03

Contents

Technical Assistance 1-87

Downgrading Your Cisco CRS-3 Carrier Routing System Router Back to a Cisco CRS-1 Carrier Routing System Router 2-1

Contents 2-1

Prerequisites for Downgrading your Cisco CRS-3 Carrier Routing System Router Back to a Cisco CRS-1 Carrier Routing System Router 2-2

Contents 2-2

Restrictions for Downgrading a Cisco CRS-3 Carrier Routing System Back to a Cisco CRS-1 Carrier Routing System Router 2-2

Downgrading your Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis Back to a Cisco CRS-1 Carrier Routing System 16-Slot Line Card Chassis 2-2

Verifying the Fabric Plane Status 2-3


Power Disable the Cisco CRS-3 Fabric Card 2-5

Swap the Cisco CRS-3 Fabric with the Newly Installed Cisco CRS-1 Fabric 2-6

Physically Removing the Cisco CRS-3 Fabric Card 2-6




Power-up the Newly Installed Cisco CRS-1 Fabric Card 2-17

Booting Up the Newly Downgraded Cisco CRS-1 Fabric 2-17


Verifying Traffic Statistics on the Newly Downgraded Cisco CRS-1 Node 2-18


Downgrading the Next Legacy Node 2-21




Power Disable the Fabric Card 2-24








4.1.Booting Up the Newly Downgraded Cisco CRS-1 Fabric 2-37

vCisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

OL-13669-03

Contents








Power Disable the Fabric Card 2-44








Booting Up the Newly Downgraded Cisco CRS-1 Fabric 2-57





Cisco CRS-3 Carrier Routing System Router Command Changes 3-1

New Commands 3-2

Modified Commands 3-27

Power Module Changes 3-71

List of QoS Changes for Cisco CRS Series Modular Services Card 140G (CRS-MSC-140G) Upgrade Doc 3-73

Important Notes: QoS Configuration Changes 3-73

Modifying CRS-MSC-40G QoS Configurations for CRS-MSC-140G 3-73

QoS Command Changes 3-74

QoS Features Changes 3-76

General 3-76

Queueing 3-76

Policing 3-77

viCisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

OL-13669-03

Contents

Turbo Boot Procedure A-1

Turbo Boot Prerequisites A-1

ROMMON Upgrade Instructions A-1

Turboboot Instructions A-2

Upgrading Your File System From FAT16 to FAT32 A-4

Cisco CRS-1 to Cisco CRS-3 Upgrade Decision Trees B-1

I N D E X

viiCisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

OL-13669-03

Contents

viiiCisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

OL-13669-03

Preface

This guide describes how to upgrade a Cisco CRS-1 Carrier Routing System to a Cisco CRS-3 Carrier Routing System. The second chapter describes how to downgrade your Cisco CRS-3 Carrier Routing System back to a Cisco CRS-1 Carrier Routing System. Both chapters describe the upgrade or downgrade process for each chassis type:

• 16-slot line card chassis



The preface contains the following sections:

• Changes to This Document, page ix

• Obtaining Documentation, Obtaining Support, and Security Guidelines, page ix

Changes to This DocumentTable 1 lists the technical changes made to this document since it was first printed.

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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

Table 1 Changes to This Document

Revision Date Change Summary

OL-13669-01 October 2010 Initial release of the document.

OL-13669-02 December 2010 Adds 100GE support.

OL-13669-03 April 2011 Adds CRS-3 multishelf support.

ixCisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

OL-13669-03

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

PrefaceObtaining Documentation, Obtaining Support, and Security Guidelines

xCisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

OL-13669-03

Cisco CRS-1 Carrier Routing System to COL-13669-03

C H A P T E R 1
Migrating to a Cisco CRS-3 Carrier Routing System
This chapter describes how to migrate a single-chassis Cisco CRS-1 Carrier Routing System to a single-chassis Cisco CRS-3 Carrier Routing System.

Note For an introduction to the single-chassis Cisco CRS-3 Carrier Routing System, see Cisco CRS Carrier Routing System 16-Slot Line Card Chassis System Description. For information on planning a single-chassis Cisco CRS-3 Carrier Routing System system installation, see Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Site Planning Guide.

Feature History for the Cisco CRS-3 Carrier Routing System

ContentsThis chapter contains the following sections:

• CRS-1 to CRS-3 Software Migration Compatibility Matrix, page 1-2

• Prerequisites for Upgrading IOS-XR Software Prior to Migrating to a Cisco CRS-3 Carrier Routing System, page 1-3

• Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3, page 1-5

• File System Upgrade Procedure for 2GB Flash Disks, page 1-7

• IOS-XR Software Upgrade Procedure, page 1-9

• Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware, page 1-14

Release Modification

Release 4.0.0.T The single-chassis Cisco CRS-3 Carrier Routing System was introduced.

Release 4.0.1 The single-chassis Cisco CRS-3 Carrier Routing System adds support for 100GE interfaces.

Release 4.0.2 Multishelf Cisco CRS-3 Carrier Routing System operation is supported and multishelf Cisco CRS-1 Carrier Routing System to multishelf Cisco CRS-3 Carrier Routing System migration is supported.

1-1isco CRS-3 Carrier Routing System Migration Guide

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemCRS-1 to CRS-3 Software Migration Compatibility Matrix

• Cisco CRS-3 Carrier Routing System and CRS-1 Carrier Routing System Hardware Compatibility Matrix, page 1-20

• Information About Migrating to a Cisco CRS-3 Carrier Routing System, page 1-21

• How to Migrate to a Cisco CRS-3 Carrier Routing System (16-Slot), page 1-23



• Configuration Examples for Migrating to a Cisco CRS-3 Carrier Routing System, page 1-80

• Where to Go Next, page 1-85

• Additional References, page 1-86

Warning Do NOT insert any CRS-3 hardware before completing the software migration to Cisco IOS XR software Release 4.0.0.T or higher.

CRS-1 to CRS-3 Software Migration Compatibility MatrixYour existing Cisco CRS-1 16-Slot Line Card Chassis must be running 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX) software before migrating to a Cisco CRS-3 16-Slot Line Card Chassis. Table 1-1 describes the migration paths that are supported.

Table 1-1 CRS-1 to CRS-3 Software Migration Compatibility Matrix

Current Version Migration VersionDirect PIE Upgrade/Downgrade Supported

3.4.x(PPC) 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

No (must be done using Turbo Boot - refer to Appendix A for more information)

3.5.x(PPC) 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)


3.6.x(PPC) 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)


3.7.x(PPC) 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)


3.8.0(PPC) 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

Yes. Migration to FAT32 recommended before upgrading.

3.8.1(PPC) 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)


3.8.2(PPC) 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)


1-2Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemPrerequisites for Upgrading IOS-XR Software Prior to Migrating to a Cisco CRS-3 Carrier Routing System

Note All IOS-XR Software releases prior to 3.8.0 (IOS XR releases 3.4.2, 3.5.3, or 3.6.2) must be upgraded to IOS XR software release 3.8.0 or higher prior to being upgraded to IOS XR software release 44.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX) or be upgraded directly to IOS XR software release 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX) using Turbo Boot - refer to Appendix A for more information.

Prerequisites for Upgrading IOS-XR Software Prior to Migrating to a Cisco CRS-3 Carrier Routing System

Warning Do NOT insert any CRS-3 hardware before completing the software upgrade to Cisco IOS XR software Release 4.0.0.T or higher.

3.8.3(PPC) 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)


Current Version Migration VersionDirect PIE Upgrade/Downgrade Supported

3.8.4(PPC) 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)


3.9.0(PPC) 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)


3.9.1(PPC) 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)


3.9.2(PPC) 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)


4.0.0(PPC) 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

No (must be done using Turbo Boot - refer to Appendix A for more information). Upgrade package required.

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

4.0.0(PPC) No (downgrades must be done using Turbo Boot - refer to Appendix A for more information).

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

3.x.x(PPC) No (downgrades must be done using Turbo Boot - refer to Appendix A for more information).

Table 1-1 CRS-1 to CRS-3 Software Migration Compatibility Matrix (continued)


OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemPrerequisites for Upgrading IOS-XR Software Prior to Migrating to a Cisco CRS-3 Carrier Routing System

At least a 2 GB FAT32 flashdisk is required to upgrade to Cisco IOS XR software Release 4.0.0.T (PX) or Cisco IOS XR software Release 4.0.1(PX). Refer to the Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3 section for more information.

The minimum version of ROMMON software supported is ROMMON release 1.54. Refer to the ROMMON Upgrades section for more information.

ROMMON UpgradesYour existing Cisco CRS-1 16-Slot Line Card Chassis Route Processors (RPs) and Distributed Route Processors (DRPs) must be running minimum ROMMON versions before migrating to a Cisco CRS-3 16-Slot Line Card Chassis. Table 1-2 describes the minimum ROMMON versions that are supported.

Warning While performing a turbo boot of 4.0.X (PX) images the ROMMON version needs to be 2.01 due to image size increase, otherwise the turbo boot will fail. Refer to Appendix A for more information on performing the turbo boot. Appendix A also describes how to upgrade your ROMMON version to 2.01

OPTION-A Currently on most systems with IOS-XR Software Release 3.8.4 or higher or IOS-XR Software Release 3.9.0 or higher images ROMMON version 1.54 is supported/installed. While upgrading from IOS-XR Software Release 3.8.4 or higher to IOS-XR Software Release 4.0.0.X (PX) you can upgrade the FPD images using the Auto FPD procedure. The Auto FPD procedure upgrades the ROMMON images on ROMMON B before resetting the router for upgrades. After the software upgrade is complete and the router is up and running you then have to manually upgrade the ROMMON A images. Upgrade ROMMON A by executing the following command from admin mode:

RP/0/RP0/CPU0:CRS-1(admin)#upgrade rommon a all disk0

For Auto FPD to work please execute the following command in admin mode

RP/0/RP0/CPU0:CRS-1(admin-config)# fpd auto-upgrade

OPTION-BThe other option is to upgrade the ROMMON manually after the image upgrade. The upgrade will not fail even if the ROMMON images are 1.54 or 1.52.

Detailed procedures for ROMMON upgrade is detailed inthe Upgrading and Downgrading ROM Monitor Firmware on Cisco CRS Routers section in the Cisco IOS XR ROM Monitor Guide for the Cisco CRS Router document online.

Table 1-2 Cisco CRS-1 to Cisco CRS-3 IOS XR Software Supported ROMMON Versions

FPD Minimum Version Required

Route Processor (RP) 1.54

Distributed Route Processor (DRP) 1.54


OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemCisco IOS-XR Flash Disk Requirements for Migration to CRS-3

Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3You can only upgrade your filesystem to FAT32 using the CLI specifed in this section if you are running Cisco IOS XR software Release 3.8.2 or above.

If you are running a release of Cisco IOS XR software earlier than 3.8.2 please refer to Upgrading Your File System From FAT16 to FAT32 in Appendix A, “Turbo Boot Procedure” for formatting the File system to FAT32 using KSH.

Cisco IOS XR software Release 4.0.X (PX) requires at least a 2GB flash disk for installation or upgrade. So prior to upgrading your current IOS XR software to IOS-XR Software Release 4.0.X (PX), you will need to upgrade the flash disk to either 2GB or 4GB.

The size of the image is significantly higher on the Cisco CRS-3 because x86 support is now included in addition to the PPC support. A FAT32 formatted flash disk will decrease the required space for the file system significantly. It is highly recommended to use a 4G flash disk with FAT-32 file-system on the Cisco CRS-3.

Checking your Existing Flash Disk Size

Execute the show filesystem command to check the actual disk0 size:

RP/0/RP0/CPU0:Router#sho filesystemWed Feb 11 15:28:57.401 PST PSTFile Systems:

Size(b) Free(b) Type Flags Prefixes - - network rw qsm/dev/fs/tftp: - - network rw qsm/dev/fs/rcp: - - network rw qsm/dev/fs/ftp: 1043456 1005568 dumper-lnk rw qsm/dumper_nvram: 39929724928 39605428224 dumper-lnk rw qsm/dumper_harddisk: 1004994560 184500224 dumper-lnk rw qsm/dumper_disk1: 1024606208 423608320 dumper-lnk rw qsm/dumper_disk0: 62390272 49101348 dumper-lnk rw qsm/dumper_bootflash: 39929724928 39605428224 harddisk rw harddisk: 1024606208 423608320 flash-disk rw disk0:----- 1004994560 184500224 flash-disk rw disk1: 1043456 1005568 nvram rw nvram: 62390272 49101348 flash rw bootflash:

In the example shown, the flash disk (disk0) size is 1 Gig.

If the disk size is smaller than 2Gig you will need to upgrade the flash disk.

The procedures for flash disk upgrade are detailed in the Cisco XR 12000 Series Router and Cisco CRS-1 Router Flash Disk Upgrade Tasks document online here:

http://www.cisco.com/en/US/docs/routers/xr12000/xr_line_cards/flashdisk/flashdisk.html

Flash Disk Upgrade Process to 4GB

Inserting the 4GB Flashdisk The first step is to insert a 4GB Cisco Authorized Flash disk into slot disk1 of Active and Standby RP. After Insertion verify the 4GB disk is accessible from RP


OL-13669-03

http://www.cisco.com/en/US/docs/routers/xr12000/xr_line_cards/flashdisk/flashdisk.html

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemCisco IOS-XR Flash Disk Requirements for Migration to CRS-3

RP/0/RP0/CPU0:router# show filesystem disk1:Model: UNIGEN FLASHCapacity: 8215201 Sectors, Total 4206182912 Bytes, (512 Bytes/sector

Disk Formatting Format the 4GB flashdisk on standby RP disk1: by executing the following command

RP/0/RP0/CPU0:ios#format disk1: partition filesystem fat32 location 0/rp1/cpu0

The above command will create a partition of 3.5/0.5 between disk1 and disk1a

Note Executing this command will not cause the RP to reset

Verifying the Disk File System Verify the filesytem is changed to FAT32 file system and desired 80% and 20% partition between disk1 and disk1a disks by executing the following command

RP/0/RP0/CPU0:ios#show media location 0/rp1/cpu0 Mountpoint FsType FsType Size State DrvrPid Mirror Flags================================================================================ /disk1: FAT16 FAT32 3.4G Mounted 0032792 Enabled /disk1a: FAT16 FAT32 0.5G Mounted 0032792

Setting Up Disk Mirroring Mirror the primary disk0 and standby disk1 disks on Standby RP using the command

RP/0/RP0/CPU0: LOAD(config)#mirror location 0/rp1/cpu0 disk0:disk1:

Verify that mirroring is enabled by executing the following command

RP/0/RP0/CPU0:LOAD#show mirror location 0/rp1/cpu0

Swapping Mirrored DisksAfter verifying that disk mirroring is successfully enabled in the previous section, swap disk0 with disk1 (insert 4GB disk in disk0 slot)

Verifying Standby RP Disk Upgrade Verify that the Standby RP boots with the 4GB flashdisk as the primary disk(disk0) on the Standby RP.


OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemFile System Upgrade Procedure for 2GB Flash Disks

Performing Switchover Perform an RP switchover and verify that the Standby RP becomes the Active RP.

Upgrading the Standby RP Once you have verified the switchover was successful, repeat the flashdisk upgrade steps on the new Standby RP and verify results.

File System Upgrade Procedure for 2GB Flash DisksFirst do the format of the boot device of the standby RP location.

format disk0: unpartition filesystem fat32 location 0/rp1/CPU0

This command formats the boot device of the standby RP and results in a reload of the standby RP. This will result in a 2GB FAT32 file system, Since the device is unpartitioned means no disk mirroring.

Once the standby RP reload, it would come back, format the device with your specifications and would start downloading all the packages from RP again. This takes time depending on the number of packages/config you have on the RP.

Verify using the below command that Standby RP disk is running with your expected filesystem/partition.

show media location 0/rp1/CPU0

Once the standby RP is up and running, perform a Switch Over from the active to the standby RP and let the new Standby RP (old Active) come up as standby Ready.

Perform the process for the new standby RP location as well.

Reducing Disk Space Usage

If the flash disk size is 2 Gig you still may want to increase available disk space. In order to provide as much room as possible on the disk, one can remove old files from the disk. This may include files which the operator has placed on the disk device such as PIE files or temporary directories that have been created.

When preparing for the upgrade to the next version of the operating system, the old, non-operational version should be removed.

To remove old SMU files and old versions of the operating system use the admin-commands

install commit

to ensure all active packages are 'committed', then issue the command

install remove inactive

The install remove inactive test sync command can be used first to show which packages will be removed from the disk.

Note In addition to checking the installation disk device, the bootflash device on the MSCs should also be checked. Extraneous files such as crashinfo files can be removed.


OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemFile System Upgrade Procedure for 2GB Flash Disks

To check the free space of the bootflash use the following command:

dir bootflash: location 0/1/CPU0

Check if all the cards in the system are all up using the admin command

show platform

If any of the cards do not boot properly they have to be replaced or be shut down using the admin command

hw-module power disable location <loc>

Minimizing Traffic Loss During the Upgrade

To minimize traffic loss during the upgrade please follow below steps:

Step 1 Make sure that all the traffic flowing through the router which needs to be upgraded has an alternate path. In this scenario one can take one of the redundant routers out of service, upgrade it and then bring it back into service without any significant traffic loss (this should work for the core routers, for the edge devices usually the redundant path may not be available)

Step 2 Set IGP metric to the highest possible value so the IGP will try to route the traffic through the alternate path.

For OSPF use the max-metric command.

router(config-ospf)#max-metric router-lsa

For ISIS use the spf-overload-bit command.

router(config-isis)#set-overload-bit

Step 3 After all the software is upgraded restore the IGP metric by removing the commands:

For OSPF use the no max-metric command

router(config-ospf)#no max-metric router-lsa

For ISIS use the no spf-overload-bit command.

router(config-isis)#no set-overload-bit

Prior to release 3.8 the above commands have to be run before the install activate command is executed, resulting in a long period of time when the router is taken out of forwarding path.

To minimize this behavior starting from release 3.8, an enhancement has been provided which allows you to pause the install activate command just prior to the router reloading and to execute configuration changes such as IGP commands listed above.

Execute the following command to enable this install option:

router(config-isis)#install activate disk0:*4.0.* pause sw-change

You will be prompted prior to the system reload to execute configuration changes such as IGP commands. At this point the IGP cost-out operation can be executed.

Step 4 Copy the running-configuration and admin-configuration to a temporary storage location. This could be on a remote TFTP server or a device such as the hard disk: or disk0: present on the RP.

router#copy running-config tftp://…running_config.txtrouter#adminrouter(admin)#copy running-config tftp://…admin-running_config.txtrouter(admin)#exit


OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemIOS-XR Software Upgrade Procedure

Step 5 Verify Mgmt access to the router (see caveats section)

Step 6 While upgrading from 3.x.x images to 4.x.x images upgrade the file system of flash disks (boot device which is typically disk0) to FAT32 file system for 2 GB and 4 GB flash disks. The procedure to upgrade the file system of flash disks is different for 2GB and 4 GB Flash disks.

Verifying that the System Meets RP Memory RequirementsDue to image size increase on x86 based PX images you will need to have at least 1 GB of free memory on each of the Route Processor (RP) modules.

Execute the following command to verify the free memory on the RP.

RP/0/RP0/CPU0:BELUGA-QQ-4#show memory Tue Oct 12 22:17:28.761 PSTPhysical Memory: 4096M total (1840M available)

IOS-XR Software Upgrade ProcedureFor links to the latest IOS XR software upgrade instructions, refer to the Cisco IOS XR General Information page here:

http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html

Obtain the Required PIE FilesThe Composite Mini Package is mandatory to perform the upgrade. The additional PIE files listed below are optional. whether they are needed or not depends on your router configuration and required features:

Table 1-3 OS XR PPX Software PIE Filenames

PIE File Description Sample PIE Filename Package Name

Mini Package (OS-MBI, Base, Admin, Fwdg, lc Rout)

hfr-mini-px.pie-4.0.1 or 4.0.2

disk0:comp-hfr-mini-px-4.0.1 or 4.0.2

Upgrade Package* (see note) hfr-upgrade-px.pie-4.0.1 or 4.0.2

disk0:hfr-px-upgrade-4.0.1 or 4.0.2

Multicast Package hfr-mcast-px.pie-4.0.1 or 4.0.2

disk0:hfr-mcast-px-4.0.1 or 4.0.2

Manageability Package hfr-mgbl-px.pie-4.0.1 or 4.0.2

disk0:hfr-mgbl-px-4.0.1 or 4.0.2

MPLS Package hfr-mpls-px.pie-4.0.1 or 4.0.2

disk0:hfr-mpls-px-4.0.1 or 4.0.2

Security Package hfr-k9sec-px.pie-4.0.1 or 4.0.2

disk0:hfr-k9sec-px-4.0.1 or 4.0.2

Diagnostic package hfr-diags-px.pie-4.0.1 or 4.0.2

disk0:hfr-diags-px-4.0.1 or 4.0.2


OL-13669-03



Note The filenames listed here may not necessarily be the filenames of the actual files since the files can be renamed. The actual filenames used will not affect the operation.

Note The upgrade Package needs to be activated along with the Mini Package.PIE file. The Upgrade Package is ONLY mandatory when performing the upgrade from 3.x to 4.x. The upgrade package must be deactivated and removed after the 3.x to 4.x upgrade operation is complete. Currently removing the upgrade PIE file triggers a false error message stating that all the active packages will be removed. This message is due to a known bug which will be fixed in later releases. You can ignore this the false warning message and safely go ahead and remove the upgrade package despite the false warning message.

New Image Name Changes for 4.0 and OnwardsTable 1-4 lists the new file names for the images for IOS XR Software release 4.0.1(PX) and onwards.

.-p – only ppc based images

.-px – ppc + x86 based images

Verify System StabilityThe following commands should be executed to verify basic system stability before the upgrade:

Execute the show platform command while in admin mode to verify that all nodes are in "IOS XR RUN" state, the PLIMs are in "OK" state, and that the SPAs are in "READY" state.

Documentation package hfr-doc-px.pie-4.0.1 or 4.0.2

disk0:hfr-doc-px-4.0.1 or 4.0.2

Field Programmable Device package hfr-fpd-px.pie-4.0.1 or 4.0.2

disk0:hfr-fpd-px-4.0.1 or 4.0.2

Table 1-3 OS XR PPX Software PIE Filenames (continued)

Table 1-4 New Image Name Changes for IOS XR Software Release 4.0.1 (PX) and Onwards

Old File Name New File Name Old Name on Router New Name on Router

comp-hfr-mini.vm hfr-mini-p.vm comp-hfr-mini-4.0.1 hfr-mini-p-4.0.1

comp-hfr-full.vm hfr-full-p.vm comp-hfr-full-4.0.1 hfr-full-p-4.0.1

comp-hfr-mini-px.vm hfr-mini-px.vm comp-hfr-mini-px-4.0.1 hfr-mini-px-4.0.1

comp-hfr-full-px.vm hfr-full-px.vm comp-hfr-full-px-4.0.0.17C hfr-full-px-4.0.1

comp-hfr-mini.pie hfr-mini-p.pie comp-hfr-mini-4.0.1 hfr-mini-p-4.0.1

comp-hfr-mini-px.pie hfr-mini-px.pie comp-hfr-mini-px-4.0.1 hfr-mini-px-4.0.1

hfr-fpd.pie hfr-fpd-p.pie hfr-fpd-4.0.1 hfr-fpd-p-4.0.1

hfr-upgrade.pie hfr-upgrade-p.pie NA NA


OL-13669-03


RP/0/RP0/CPU0:router(admin)#show platform Tue Oct 12 23:34:37.898 PSTNode Type PLIM State Config State---------------------------------------------------------------------------------------0/0/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/1/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/2/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/3/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/4/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON0/5/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON0/6/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/7/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON0/8/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/9/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON0/10/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON0/11/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/12/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON0/13/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/14/SP DRP(SP) N/A IOS XR RUN PWR,NSHUT,MON0/14/CPU0 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON0/14/CPU1 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON0/15/SP DRP(SP) N/A IOS XR RUN PWR,NSHUT,MON0/15/CPU0 DRP(Standby) DRP-ACC IOS XR RUN PWR,NSHUT,MON0/15/CPU1 DRP(Standby) DRP-ACC IOS XR RUN PWR,NSHUT,MON0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON0/FC0/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON0/FC1/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON0/AM0/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON0/AM1/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM0/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON

Execute the show redundancy command to verify that a Standby RP is available and in "ready" state.

RP/0/RP0/CPU0:router#show redRedundancy information for node 0/RP0/CPU0:

==========================================Node 0/RP0/CPU0 is in ACTIVE rolePartner node (0/RP1/CPU0) is in STANDBY roleStandby node in 0/RP1/CPU0 is readyStandby node in 0/RP1/CPU0 is NSR-ready

Execute the show ipv4 interface brief command or the show ipv6 interface brief command or the show interface summary command to verify that all necessary interfaces are "UP".

RP/0/RP0/CPU0:router#show interfaces summary Tue Oct 12 23:41:48.562 PSTInterface Type Total UP Down Admin Down-------------- ----- -- ---- ----------ALL TYPES 750 712 0 38 -------------- IFT_LOOPBACK 1 1 0 0 IFT_ETHERNET 6 2 0 4 IFT_NULL 1 1 0 0 IFT_TENGETHERNET 232 198 0 34 IFT_VLAN_SUBIF 510 510 0 0


OL-13669-03


show install active summary (verify that the proper set of packages are active)

Single-chassis example:

RP/0/RP0/CPU0:router(admin)#show install active summary Wed Oct 13 06:47:17.604 UTCDefault Profile: Admin Resources SDRs: Owner Active Packages: disk0:hfr-cgn-px-4.0.0.65I disk0:hfr-mpls-px-4.0.0.65I disk0:hfr-mcast-px-4.0.0.65I disk0:hfr-mini-px-4.0.0.65I

Multishelf example:

RP/0/RP0/CPU0:MC-SCALE(admin)#show install active summary Default Profile: Admin Resources SDRs: Owner taiko-sdr Active Packages: disk0:hfr-fit-px-4.0.2.19I disk0:hfr-doc-px-4.0.2.19I disk0:hfr-mpls-px-4.0.2.19I disk0:hfr-mgbl-px-4.0.2.19I disk0:hfr-mcast-px-4.0.2.19I disk0:hfr-mini-px-4.0.2.19I disk0:hfr-fpd-px-4.0.2.19I disk0:hfr-diags-px-4.0.2.19I

Execute the cfs check/clear configuration inconsistency command to verify/fix configuration file system in exec and admin mode.

Additional Pre-upgrade System ChecksDue to increasing size of the images sufficient disk space is required to perform the upgrade. the 2Gig flash disk option was first introduced in release 3.7.0, An optional 4Gig flash disk is available starting with the IOS XR 3.8.4 release.

When upgrading to release 4.0.0 or higher, a PCMCIA flash disk of 2Gig or larger has to be installed in the system BEFORE the software upgrade is performed.

Step 1 Use the show filesystem command to check the actual disk0 size:

RP/0/RP0/CPU0:router(admin)#show filesystem Wed Oct 13 06:54:57.000 UTCFile Systems:

3694129152 1131577344 flash-disk rw disk0: 2102788096 2102657024 flash-disk rw disk1a:2102722560 180682752 flash-disk rw disk1: 504471552 504152064 flash-disk rw disk0a:


OL-13669-03


1043456 940032 nvram rw nvram: 62390272 25756520 flash rw bootflash:

In order to provide as much room as possible on the disk, one can remove old files from the disk. This may include files which the operator has placed on the disk device such as PIE files or temporary directories that have been created.

When preparing for the upgrade to the next version of the operating system, any old, non-operational versions should be removed.

Step 2 Remove old SMUs and old versions of the operating system files by executing the following admin commands:

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

Node 0/0/CPU0 [LC] [SDR: Owner] Boot Device: mem: Inactive Packages: disk0:hfr-fit-px-4.0.0.63I disk0:hfr-infra-test-px-4.0.0.65I disk0:hfr-upgrade-px-4.0.0.65I disk0:hfr-fit-px-4.0.0.65I disk0:hfr-cgn-px-4.0.0.63I disk0:hfr-mpls-px-4.0.0.63I disk0:hfr-mcast-px-4.0.0.63I disk0:hfr-fpd-px-4.0.0.65I disk0:hfr-fpd-px-4.0.0.63I disk0:hfr-diags-px-4.0.0.63I disk0:hfr-diags-px-4.0.0.65I

Execute the install remove inactive test sync command first to show which packages will be removed from the disk.

RP/0/RP0/CPU0:router(admin)#install remove inactive test syncInfo: This operation will remove the following packages:Info: disk0:hfr-diags-px-4.0.0.65IInfo: disk0:hfr-diags-supp-4.0.0.65IInfo: disk0:hfr-doc-px-4.0.0.65IInfo: disk0:hfr-doc-supp-4.0.0.65IInfo: disk0:hfr-fit-px-4.0.0.65IInfo: disk0:hfr-fit-4.0.0.65I

The install operation will continue asynchronously.

RP/0/RP0/CPU0:router(admin)#Install operation 192 completed successfully

Step 3 Ensure all active packages are 'committed', then issue the install commit command

RP/0/RP0/CPU0:router(admin)#install commit Wed Oct 13 07:10:37.141 UTCInstall operation 193 '(admin) install commit' started by user 'lab' via CLI at 07:10:38 UTC Wed Oct 13 2010.Install operation 193 completed successfully at 07:10:46 UTC Wed Oct 13 2010.

If any node is not booting properly it has to be replaced or shut down using the hw-module power disable location 0/1/cpu0 command executed while in admin mode

RP/0/RP0/CPU0:router(admin-config)#hw-module power disable location 0/1/cpu0

Step 4 Copy the running-configuration and admin-configuration to a temporary storage location. This could be on a remote TFTP server or a device such as the harddisk: or disk0: present on the RP.

router#copy running-config tftp://…running_config.txtrouter#admin


OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemUpgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware

router(admin)#copy running-config tftp://…admin-running_config.txtrouter(admin)#exit

Step 5 Verify Mgmt access to the router

Note Cisco recommends copying all the Mandatory PIE files, Optional PIE files, and Recommended SMUs to the hard disk as part of pre-maintenance activity. This will save significant time during the upgrade process.

Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware

Before migrating your CRS-1 hardware to CRS-3 hardware you must complete the software upgrade to Cisco IOS XR software Release 4.0.X(PX).

Note All install operations should be done while logged into admin mode.

Step 1 Add the required PIEs to disk:

router(admin)# install add tar <source>/<path>/<pie> sync

The <source> keyword can be one of disk0:, disk1:, compactflash:, harddisk:, tftp:, ftp: or rcp:. The above step must be repeated for each PIE file, or all of the PIEs can be added together in a single install add command. To add all PIEs using a single command, list all of the PIEs (including their source) within the install add command in the following manner:

router(admin)# install add <source>/hfr-mini-px.pie-<version> <source>/hfr-mcast-px.pie-<version> <source>/hfr-mgbl-px.pie-<version> <source>/hfr-mpls-px.pie-<version> <source>/hfr-k9sec-px.pie-<version> <source>/hfr-diags-px.pie-<version> hfr-upgrade-px.pie sync

Note The use of the sync option prevents other users from executing any other command during the install operation.

The <source> keyword can be specified just once rather than for each package. This simplifies the command:

router(admin)# install add <source> hfr-mini-px.pie-<version> hfr-mcast-px.pie-<version> hfr-mgbl-px.pie-<version> hfr-mpls-px.pie-<version> hfr-k9sec-px.pie-<version> hfr-diags-px.pie-<version> hfr-upgrade-px.pie <version> sync


OL-13669-03


Note Under idle conditions, the "install add" operation may take up to 65 to 100 minutes. During the “install add” operation your Cisco CRS Series router will remain fully functional.

Note If you have any other optional packages installed, the current upgrade has to be done with the optional packages already installed. Otherwise all optional packages have to be deactivated (following by the commit) before the upgrade. Side effect of this is loss of the configuration supported by the PIE.

From Cisco IOS XR software release 3.6.0 onward, an alternate way of adding and installing PIEs is available. If the PIE files are compressed using tar format they can be loaded on the router using the following command:

router(admin)# install add tar <source>/<path>/<tar_file> sync

Step 2 Test the activation using the test option. Testing the activation will give you a preview of the activation.

router(admin)# install activate disk0:hfr-mini-px.pie<version> disk0:hfr-mcast-px.pie<version> disk0:hfr-mgbl-px.pie<version> disk0:hfr-k9sec-px.pie<version> disk0:hfr-mpls-px.pie<version> disk0:hfr-diags-px.pie<version> hfr-upgrade-px.pie sync test

Note No actual changes will be made when you use the test option with the sync command. Any config that is incompatible with the new version being activated will be identified. The show configuration removed command can be used to view what will be removed as result of the software upgrade (see the Caveats section for details).

Each removed configuration can be reapplied using the load config removed <config>.cfg command from config mode AFTER the upgrade has been completed (see the Caveats section for details).

From Cisco IOS XR software release 3.6 onwards, the install command will accept the use of wildcard pattern matching. The install activate command can be simplified to install activate *3.9* sync test.

FromCisco IOS XR software release 3.7.0 onwards, PIEs can subsequently be activated using the following single command. The <install_operation_id> variable is based on the install operation ID generated after each install command:

router(admin)# install activate id <install_operation_id> sync test

The install operation ID is printed after finishing each install command or can be obtained by running the show install log command.

Step 3 Activate all of the packages added in step 1:

router(admin)# install activate disk0:hfr-mini-px.pie<version> disk0:hfr-mcast-px.pie<version> disk0:hfr-mgbl-px.pie<version> disk0:hfr-k9sec-px.pie<version> disk0:hfr-mpls-px.pie<version> disk0:hfr-diags-px.pie<version> hfr-upgrade-px.piesync

The output of the install add command executed in step 1 provides the list of names of packages to be used in the install activate operation.

Using the sync option prevents other users from executing any other commands during the install operation.


OL-13669-03


The router will reload at the end of activation to start using the new packages.

Note Under idle conditions, this operation may take at least 20 minutes to complete.

From Cisco IOS XR software release 3.8 onwards, the install command install activate *3.9.* pause sw-change sync can be used to enable the user to cost the router out of the IGP path just before the router reloads, rather than at the point where the activation commences.

Step 4 Verify system stability through executing the commands described under the Check System Stability section. This release does not support downgrades from PX to P images.

Step 5 Verify activation is successful. Once activation is done and before the install commit operation, deactivate and remove the upgrade-px.PIE.

Step 6 After removing the upgrade-px.PIE execute the install commit command to commit the newly activated software

router(admin)# install commit

Step 7 Check to see if there were any failed startup configurations. If there were any startup configurations that failed (were not applied), then refer to the Caveats section to see how it should be handled.

router# show config failed startup

In same very rare cases inconsistencies in the content of the internal configuration files can occur. In order to avoid such situations, the following steps are recommended before activating packages:

Step 8 Clear the NVGEN cache:

router# run nvgen -F 1

Step 9 Create a dummy config commit:

router# configrouter(config)#hostname <hostname>router(config)#commitrouter(config)#end

Step 10 Force commit update by using the reload command. Press n when the confirmation prompt appears:

router# reloadUpdating Commit Database. Please wait...[OK]Proceed with reload? [confirm] <- Press "n"

In same cases the following error may be reported:

router#reloadPreparing system for backup. This may take a few minutes ............System configuration backup in progress [Retry later]

In such a case please re-try the command after some time.

Post-Upgrade Procedure

Step 1 Restore the IGP metric if it had been changed before the upgrade


OL-13669-03


OSPF


ISIS


Disk Cleanup (Optional)

Once the software upgrade or downgrade has been completed, you can recover some disk space by removing any inactive packages that are no longer needed (if the packages are required at a later time, they can be re-added):

Step 1 Obtain the list of inactive packages and note the names of packages that are not needed:

router(admin)# show install inactive brief

Step 2 Remove the unnecessary inactive packages:

router(admin)# install remove disk0:<package_name1> disk0:<package_name2> .. disk0:<pkg_nameN> sync

or

router(admin)# install remove inactive(to remove all inactive packages)

Using the sync option prevents other users from executing any other command during the install operation.

Step 3 Verify/fix the configuration file system (mandatory)

router(admin)#cfs check

Step 4 If the max-metric or set overload bit was set during any of the pre-upgrade tasks restore the metric using the following commands:

OSPF


ISIS


Upgrade Firmware (Mandatory)

Both the ROMMON and the FPGA firmware need to be upgraded after the <version> image installation on the system. For detailed upgrade procedure please refer to the IOS XR Firmware Upgrade Guide document which can be accessed at:



OL-13669-03



Also refer to the “Other Firmware Support" section in the Release Notes for Cisco CRS-1 and Cisco CRS-3 for Cisco IOS XR Software Release 4.0.2 document which can be accessed at:

http://www.cisco.com/en/US/docs/routers/crs/software/crs_r4.0/general/release/notes/reln_402crs.html

Caveats:

During software upgrade or downgrade, the system could detect incompatible configuration and remove it from the running configuration. The removed configuration will be saved to a file on the router. A configuration could also fail due to syntax or semantic error as the router boots the new version of the software.

To resolve these issues, you must browse the removed or failed configuration and then address the changes so that the configuration can be properly applied on the new version of software.

Addressing Incompatible and Removed Configurations

During the test activation of a new software version, incompatible configurations will be identified and removed from the router running configuration. Syslog and console logs will provide the necessary information on the name of the removed configuration file. To address the incompatible configuration, you should browse the removed configuration file, address the syntax and semantics errors and re-apply the config as required and/or applicable after upgrade.

To display the removed configuration, execute the following command from exec mode:

router# show configuration removed <removed config filename>

Addressing Failed Admin and Non-Admin Configurations During Reload

Some configuration may fail to take effect when the router boots with the new software. These configurations will be saved as failed configurations. During activation of the new software version, you will be notified via syslog and console log if a configuration failed to take effect. To address the failed configuration, you should browse both the admin and non-admin failed configurations, address any syntax and semantics errors found, and then re-apply it as required.

To display the failed configuration, execute the following commands:

router# show configuration failed startuprouter(admin)# show configuration failed startup

MDR - Minimum Disruption Restart

The MDR (Minimum Disruption Restart) feature is not supported for upgrades to the Cisco IOS XR software 4.0.0.T, Cisco IOS XR software 4.0.1, or Cisco IOS XR software 4.0.2 releases.

Limitations With the Preconfig Interface

It is important that you check to see whether the persistent config and the running config are the same or different. If they are different then it will have a problem after reload/upgrade, because reload/upgrade will use the persistent config to restore configuration and the restored configuration will be different from the one you were running.

Execute the following commands to verify that the persistent config and the running config are the same:

show cfgmgr persistent-config - shows the persistent config in CLI form

show running-config - shows running config


OL-13669-03

http://www.cisco.com/en/US/docs/routers/crs/software/crs_r4.0/general/release/notes/reln_401crs.html


You should not use the no interface preconfig <> command if you find that the same config exists in both preconfig and activate. Use the cfs check command to resolve the inconsistency.

Upgrade Instructions for FAT32

Step 1 Once the system is up and running with FAT32, please check the disk usage on the router and make sure at least 1.3 GB is free on the Cisco CRS router (We don't need 1.3 GB for the upgrade, but 4.0.0.T shouldn't be taking more than 600 MB)

a. Please make sure all inactive old Cisco IOS XR software release packages (older than Cisco IOS XR software release 4.0.0.T) are removed from the disk.

b. Please make sure all dumper core files and any user files like PIEs etc. are removed from the boot device to save space.

Step 2 Make sure system (RP) has available memory. Please refer to the table above with title RP/SP/LC Memory Requirements during Upgrade.

Step 3 Make sure other management nodes RP/DRP/SC also have available memory. This is applicable to a multishelf platform. The available memory on other RPs should be around the same as the Standby RP of the DSC.

Step 4 Copy the TAR ball of all Cisco IOS XR software release 4.0 PX packages (mini-px.pie + upgrade package + optional PX Package and any SMUs) to the hard disk.

Warning DO NOT COPY THIS TAR BALL PACKAGE TO THE BOOT DEVICE WHICH IS TYPICALLY DISK 0:.

Note The Upgrade Package is absolutely necessary in order to upgrade from a pre 4.0 PX Cisco IOS XR software release to the 4.0 PX Cisco IOS XR software release

Note Make sure all mini and optional packages/SMUs are PX. Do not mix and match packages/SMUs.

Warning Make sure the TAR package contains all the necessary optional packages (mgbl, mpls, mcast, k9sec, doc, diag, fpd). If any of the packages are missed during the upgrade, upgrade activation doesn't complain about the missing package and incompatibilities.

If install add is being done as TAR ball, then the memory requirements on the Route Processor (RP) would be high as contents would be untarred in the /tmp folder. To avoid the usage of RP memory, you can resort to install add of independent packages using the below command. But this typically leads to longer install add times than with the TAR ball install add.

install add source harddisk: pie1 pie2 pie3…..

Step 5 Once the router comes back up with new software, please perform your stability checks and then do the below operations to unblock further install operations.

a. Install the Deactivate Upgrade Package


OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemCisco CRS-3 Carrier Routing System and CRS-1 Carrier Routing System Hardware Compatibility Matrix

b. Install the Remove Upgrade Package: This operation removes the dummy packages of Cisco IOS XR software release 4.0; no Cisco IOS XR software release 4.0 software is being removed. This is only a bridging package to facilitate upgrade from Cisco IOS XR software release pre-4.0 software to Cisco IOS XR software release 4.0 software as the package names have changed. The upgrade package contains Cisco IOS XR software release 4.0 dummy packages compatible with Cisco IOS XR software release pre-4.0 packages which are not typically used once you have upgraded to Cisco IOS XR software release 4.0 software. Once your upgrade to Cisco IOS XR software release 4.0 has completed successfully, the Cisco IOS XR software release 4.0 dummy packages (which were installed solely for compatibility with the existing Cisco IOS XR software release pre-4.0 packages) can be removed safely.

Step 6 Now perform an install commit command and continue testing the Cisco IOS XR software release 4.0.0.T.PX Image.

Cisco CRS-3 Carrier Routing System and CRS-1 Carrier Routing System Hardware Compatibility Matrix

To convert the existing 40G based Cisco CRS-1 system to 140G based Cisco CRS-3 system, the MSC, PLIM & Fabric cards would need to be replaced.

Refer to Table 1-5 on page 1-20 for the new 140G-based Cisco CRS-3 hardware.

Table 1-5 140G-based Cisco CRS-3 Hardware

ExistingChassis CRS-3 MSC CRS-3 PLIM Note

SC : 16 slot MSC-140G

FP-140G

14x10GE

20x10GE

1x100GE

Current CRS-1

8 slot chassis MSC-140G

FP-140G

14x10GE

20x10GE

1x100GE

Current CRS-1

4 slot chassis MSC-140G

FP-140G

14x10GE

20x10GE

1x100GE

MSC-140 must NOT be plugged in with CRS-1 Fabric

MC : 16 slot LCC MSC-140G

FP-140G

14x10GE

20x10GE

1x100GE

Current CRS-1

MC : 16 slot FCC N/A N/A CRS-FCC-FC140/M (S2)

[8 planes | 1 plane/board]

[8 planes | 1 plane/ 3 boards for Multimodule config]


OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemInformation About Migrating to a Cisco CRS-3 Carrier Routing System

Refer to Table 1-6 on page 1-21 for a compatibility matrix of CRS-1 (legacy, 40G) and CRS-3 (140G) hardware:

Information About Migrating to a Cisco CRS-3 Carrier Routing System

The difference between migrating a single-chassis Cisco CRS-1 Carrier Routing System to a single-chassis Cisco CRS-3 Carrier Routing System and installing a new single-chassis Cisco CRS-3 Carrier Routing System is the fabric upgrade. A single-chassis Cisco CRS-1 Carrier Routing System uses fabric cards designed for 40 GB operation (FC/S cards), and an LCC in a Cisco CRS-3 Carrier Routing System uses fabric cards designed for 140 GB operation (FC-140G/S cards). On a single chassis system, each fabric card represents one fabric plane. To migrate a single-chassis Cisco CRS-1 Carrier Routing System to a single-chassis Cisco CRS-3 Carrier Routing System without interrupting service, you must do the following:

1. Use CLI commands to prepare the FC/S fabric card for replacement with an FC-140G/S card.

2. Shut down the plane on the FC/S card before it is replaced.

3. Replace the FC/S card with an FC-140G/S card.

4. Bring up the FC-140G/S card.

5. Repeat Step 2 through Step 4 until all planes (0 through 7) are upgraded.

Verify That the Correct Version of IOS-XR Software is Installed

The Cisco CRS-3 is only supported on Cisco IOS-XR release 4.0.0.T and higher software. As detailed in the section CRS-1 to CRS-3 Software Migration Compatibility Matrix, page 1-2, a direct IOS-XR upgrade to Release 4.0.X(PX) is available for a router running Cisco IOS XR releases 3.8.0 through 3.9.0. All IOS-XR Software releases prior to 3.8.0 (IOS XR releases 3.4.2, 3.5.3, or 3.6.2) must be

Table 1-6 CRS-1 and CRS-3 Hardware Compatibility Matrix

Fabric Type MSC/FP/RP/DRP Type Supported Note

CRS-1 Fabric MSC-40 (both A and B) Yes Current CRS-1

CRS-1 Fabric RP-A/RP-B/DR-B Yes Current CRS-1

CRS-1 Fabric MSC-140 No MSC-140 must NOT be plugged in with CRS-1 Fabric

CRS-1 Fabric FP-40 Yes Current CRS-1

CRS-1 Fabric FP-140 No FP-140 must NOT be plugged in with CRS-1 Fabric

CRS-3 Fabric MSC-40 (both A and B) Yes 40G throughput

CRS-3 Fabric RP-A/RP-B/DRP-B Yes With upgraded FPD/XR.

CRS-3 Fabric MSC-140 Yes 140G throughput

CRS-3 Fabric FP-40 Yes 40G throughput

CRS-3 Fabric FP-140 Yes 140G throughput


OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemInformation About Migrating to a Cisco CRS-3 Carrier Routing System

upgraded to IOS XR software release 3.8.0 or higher prior to being upgraded to IOS XR software Release 4.0.X(PX) or be upgraded directly to IOS XR software Release 4.0.X(PX) using Turbo Boot as described in Appendix A, “Turbo Boot Procedure,”.

Execute the show version command to verify that the CRS-1 to be migrated is running Cisco IOS-XR Release 4.0.X(PX):

RP/0/RP0/CPU0:router#show versionMon Mar 1 06:18:22.261 UTC

Cisco IOS XR Software, Version 4.0.0.T[Default]Copyright (c) 2010 by Cisco Systems, Inc.

ROM: System Bootstrap, Version 1.304(20091103:191235) [CRS-1 ROMMON],

• Next, execute the show platform command to verify that all Fabric cards are operational (i.e. State is IOS-XR RUN)

RP/0/RP0/CPU0:router(admin)#show platform Node Type PLIM State Config State<snip>0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON<snip>

• Next, execute the show controllers fabric plane all command to verify that all Fabric Planes are UP:

RP/0/RP0/CPU0:router(admin)#show controllers fabric plane all<snip> Plane Admin Oper up->dn up->mcast Id State State counter counter --------------------------------------------- 0 UP UP 0 0 1 UP UP 0 0 2 UP UP 0 0 3 UP UP 0 0 4 UP UP 0 0 5 UP UP 0 0 6 UP UP 0 0 7 UP UP 0 0

Note The up->down counter records the number of times the plane has flapped between UP and DOWN. Similarly, up->mcast_Down counter records the number of plane transitions between MCAST_DOWN and UP]


OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemHow to Migrate to a Cisco CRS-3 Carrier Routing System (16-Slot)

Benchmark the Traffic

Before starting the migration process, take a snapshot of the traffic flowing through the router and use it as a benchmark to compare against traffic flow during the migration and/or after completing the migration. Since it is a hitless migration, there should be zero impact to the traffic flow during the migration and/or after completing the migration.

• To avoid traffic loss, you must upgrade the switch fabric one plane at a time. To do that, you must replace each FC/S card with a new FC-140G/S card and restore service to that fabric plane before upgrading the next fabric plane.

• You will probably want to perform the migration during a network maintenance window or when system traffic is light.

Note Be sure to review the migration procedures before deciding when to schedule the migration. That way, you can familiarize yourself with the migration procedure and determine if there are other issues to consider before performing the migration.

• Cisco recommends not moving a chassis after it is cabled. Before the fabric cables are installed, the chassis should be fully installed with power supplies, console cables, grounded, and so forth

How to Migrate to a Cisco CRS-3 Carrier Routing System (16-Slot)

To migrate from a 16-slot Cisco CRS-1 Carrier Routing System to a 16-slot Cisco CRS-3 Carrier Routing System, you must complete the following tasks:

• Administratively Disabling the Fabric Plane, page 1-5

• Disabling Power to the CRS-1 Fabric Card, page 1-7.

• Physically Removing the CRS-1 Fabric Card, page 1-9

• Installing an SFC, page 1-11.

• Verifying the Installation of an SFC, page 1-15

The migration procedure may be done on one Fabric Card at-a-time.

In a CRS-1 system with redundant fabric (i.e. 8 planes), upgrade to CRS-3 fabric is hitless - zero drop in traffic as we upgrade plane by plane from a CRS-1 to CRS-3.

The detailed migration procedure is detailed in the sections below, for the 16-slot Cisco CRS-1 Carrier Routing System.

Administratively Disabling the Fabric PlaneThis section describes how to migrate the fabric cards in a single-chassis system and establish communications between the designated shelf controller (DSC) LCC and one or more FCCs.

SUMMARY STEPS

1. admin


OL-13669-03


2. configure

3. controller fabric plane 0 shut

4. commit

5. end

6. Repeat Step 3 through Step 5 for each fabric plane.

7. show controllers fabric plane all detail

DETAILED STEPS

Command or Action Purpose

Step 1 admin

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

Places the router in administration EXEC mode.

• All commands listed in this procedure should be entered on the pre-existing single-chassis system.

Step 2 configure

Example:RP/0/RP1/CPU0:router(admin)#configure

Places the router in administration configuration mode.

Step 3 controller fabric plane 0 shut

Example:RP/0/RP1/CPU0:router(admin-config)# controller fabric plane 0 shut

Shuts down the fabric plane in the system.

• In a 16-slot CRS-1 router, we have eight fabric nodes, or CRS-1 Fabric Controller cards, numbered 0/SM0/SP to 0/SM7/SP. Each CRS-1 Fabric Controller card has one plane. So for a 16-slot CRS-1 to CRS-3 migration we will be upgrading one plane at a time for all eight planes.

• For more information, see Cisco IOS XR Getting Started Guide.

Step 4 commit

Example:RP/0/RP1/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

• This step brings up the previously shutdown plane, which is now configured to use the FCC-CRS-3 fabric card.

Step 5 end

Example:RP/0/RP1/CPU0:router(admin-config)# end

Changes the mode from administration configuration mode to administration EXEC mode.

Step 6 Repeat Step 3 through Step 5 for each fabric plane.

Step 7 show controllers fabric plane all detail

Example:RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all detail

Displays the administrative and operational status of all eight fabric planes.

• Verify that all fabric planes are administrative state down.

Note There are a total of 42 bundles. There are 3 bundles per LCC. Bundles for LCCs not in service will be down.


OL-13669-03


The following example shows commands to Administratively Disable the Fabric Plane on the CRS-1 Fabric Card:

RP/0/RP0/CPU0:router#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#controller fabric plane 0 shutRP/0/RP0/CPU0:router(admin-config)#commitRP/0/RP1/CPU0:router(admin-config)# endRP/0/RP1/CPU0:router(admin)# show controllers fabric plane all detail

Example of the show controllers fabric plane all detail Command

Execute the show controllers fabric plane all detail command to display the status of the planes. The following example shows a multishelf Cisco CRS Carrier Routing System node:

RP/3/RP0/CPU0:MC-SCALE(admin)#show controllers fabric plane all detail Fri Jan 7 17:02:44.919 PST Flags: P - plane admin down, p - plane oper down C - card admin down, c - card oper down A - asic admin down, a - asic oper down L - link port admin down, l - linkport oper down B - bundle port admin Down, b - bundle port oper down I - bundle admin down, i - bundle oper down N - node admin down, n - node down X - ctrl admin down, x - ctrl down o - other end of link down d - data down f - failed component downstream m - plane multicast down, s - link port permanently shutdown t - no barrier input O - Out-Of-Service oper down T - topology mismatch down e - link port control only D - plane admin data down

Plane Admin Oper up->dn up->mcast Down Total Down Id State State counter counter Flags Bundles Bundles ------------------------------------------------------------------------- 0 DOWN DOWN 0 0 27 15 1 UP UP 0 0 27 15 2 UP UP 0 0 27 15 3 UP UP 0 0 27 15 4 UP UP 0 0 27 15 5 UP UP 0 0 27 15 6 UP UP 0 0 27 15 7 UP UP 0 0 27 15

What to Do Next

Next we disable power to the Fabric node, and verify that node is moved to Unpowered state.

Disabling Power to the CRS-1 Fabric Card

SUMMARY STEPS

1. admin

2. configure


OL-13669-03


3. hw-module power disable loc 0/SM0/SP

4. commit

5. end

6. show platform

DETAILED STEPS

Example

The following example shows commands to disable power to the CRS-1 Fabric Card:

RP/0/RP0/CPU0:router#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#hw-module power disable loc 0/SM0/SPRP/0/RP0/CPU0:router(admin-config)#commitRP/0/RP1/CPU0:router(admin-config)# end

RP/0/RP0/CPU0:router(admin)#show platform Node Type PLIM State Config State


Step 1 admin




Step 2 configure



Step 3 hw-module power disable loc 0/SM0/SP

Example:RP/0/RP1/CPU0:router(admin-config)# hw-module power disable loc 0/SM0/SP

Disables the power to the specified fabric plane in your single-chassis system.

Step 4 commit




Step 5 end



Step 6 show platform

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

Displays the power status of all eight fabric planes.

• Verify that the CRS-1 fabric card in node 0/SM0/SP is in the UNPOWERED state.


OL-13669-03


<snip>0/SM0/SP FC/S(SP) N/A UNPOWERED PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON<snip>

What to Do Next

Next we physically remove the CRS-1 fabric card.

Physically Removing the CRS-1 Fabric CardThis section describes how to physically remove the CRS-1 fabric card, and verify that node is ready to have a CRS-3 fabric card installed in its place.

This section describes how to remove a switch fabric card (SFC) [in this case, the CRS-1 fabric card] from the Cisco CRS Fabric Card Chassis. For more detailed information on the Cisco CRS fabric cards, see Cisco CRS Carrier Routing System 16-Slot Line Card Chassis System Description.

Caution Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 281

Warning For diverging beams, viewing the laser output with certain optical instruments within a distance of 100 mm may pose an eye hazard. For collimated beams, viewing the laser output with certain optical instruments designed for use at a distance may pose an eye hazard. Statement 282

Warning Laser radiation. Do not view directly with optical instruments. Class 1M laser product. Statement 283

On the LCC chassis disconnect the Trimese cables on the SM cards associated with the planes that you have shut down. If the cables are going to be disconnected for an extended period of time cap the ends with dust covers.


OL-13669-03


Figure 1-1 Switch Fabric Card

Prerequisites

Before performing this task, you must first open the front cosmetic doors (if installed).

Caution Use the slide-assistance arm to slide cards from the card carrier. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM! Rotate cards onto their vertical axes, then lift them from the bottom, using the slide-assistance arm only as an aid for balance.

Required Tools and Equipment

You need the following tools to perform this task:

• ESD-preventive wrist strap

• Large Phillips screwdriver

1298

68


OL-13669-03


Steps

To remove the CRS-1 fabric card, see Figure 1-2 and follow these steps:

Figure 1-2 Removing the CRS-1 Fabric Card

Step 1 Attach the ESD-preventive wrist strap to your wrist and connect its leash to an ESD connection socket on the front of the chassis or to a bare metal surface on the chassis.

Step 2 Identify the card to be removed in the card cage. Use the screwdriver to turn the two captive screws on the front panel of the card counterclockwise to loosen the card from the slot.

Step 3 Grasp the two card ejector levers and simultaneously pivot both ejector levers about 90 degrees away from the front edge of the card carrier to unseat the card from the backplane connector.

Caution To prevent ESD damage, handle the CRS-1 fabric card by its ejector levers, the CRS-1 fabric card carrier edges, or the slide-assistance arm only. Do not touch any of the electrical components, pins, and circuitry.

1 Captive screw 3 Direction of installation or removal

2 Ejector lever

STATU

SP

ID/V

IDC

RS

-FC

C-S

FC

CL

EI

SN

:

1298

70

1

3

2


OL-13669-03


Step 4 Grasp the slide-assistance arm and gently pull the CRS-1 fabric card halfway from the slot.

Step 5 Move one hand under the CRS-1 fabric card to guide it. Avoid touching the CRS-1 fabric card printed circuit board, components, and any connector pins. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM; lift them from the bottom, using the slide-assistance arm only as an aid for balance.

Step 6 Slide the card completely from the slot.

Caution The CRS-1 fabric card weighs about 30 lb (14 kg). You should use two hands when handling the CRS-1 fabric card.

Step 7 Replace the caps on the HBMT connectors on the back of the card.

Step 8 Place the card directly into an antistatic sack or other ESD-preventive container. If you plan to return the defective card to the factory, repackage it in a Cisco CRS-1 fabric card shipping container.

What to Do Next

After performing this task, you may replace any front cosmetic cover plates (see the “Installing the Front and Rear (SFC) Side Cosmetic Components” section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide).

For complete information on regulatory compliance and safety, see Regulatory Compliance and Safety Information for the Cisco CRS Carrier Routing System. For information on installing a CRS-3 fabric card, see the “Installing a CRS-3 Fabric Card” section on page 1-30.

Installing a CRS-3 Fabric CardThis section describes how to install a CRS-3 fabric card in the Cisco CRS Fabric Card Chassis. For more detailed information on the CRS-3 fabric card, see Cisco CRS Carrier Routing System 16-Slot Line Card Chassis System Description.

Warning Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 281




OL-13669-03


Figure 1-3 Switch Fabric Card (QQ123-140G)

2496

55


OL-13669-03


Prerequisites

Before performing this task, you must first open the front (SFC) side cosmetic doors (if installed). You must already have an OIM installed in your chassis in the slot corresponding to where you plan to install the CRS-3 fabric card before you install the CRS-3 fabric card (for example, if you are planning on installing the CRS-3 fabric card in slot 0, you must have an OIM installed in slot 0 on the rear of the chassis), and you must remove any impedance carrier or slot cover from the slot in which you are installing the CRS-3 fabric card. See the “Installing an OIM” section, the “Removing a Slot Cover” section, and the “Removing an Impedance Carrier” section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide.

A CRS-3 fabric card can be installed in any of the slots SFC0 to SFC11 (upper card cage) and SFC12 to SFC23 (lower card cage).



You need the following tools and part to perform this task:



• CRS-3 fabric card


OL-13669-03


Steps

To install the CRS-3 fabric card, see Figure 1-4 and follow these steps:

Figure 1-4 Installing a CRS-3 Fabric Card


Step 2 Choose an available CRS-3 fabric card slot for the CRS-3 fabric card.



2 Ejector lever

STATU

SP

ID/V

IDC

RS

-FC

C-S

FC

CL

EI

SN

:

1298

70

1

3

2


OL-13669-03


Step 3 Remove the CRS-1 fabric card impedance carrier or CRS-1 fabric card you are replacing from the designated slot, and set it carefully aside. (See the “Removing an Impedance Carrier” section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide or the “Removing an SFC” section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide.)

Note Remove only one impedance carrier or CRS-1 fabric card and install one CRS-3 fabric card at a time. Be sure to verify that each CRS-3 fabric card is fully installed and secured before installing another card.

Step 4 Remove the CRS-3 fabric card you are installing from its antistatic packaging.

Step 5 Use the screwdriver to unscrew and remove the sheetmetal cover over the HBMT connectors on the rear of the CRS-3 fabric card, and set it aside.

Step 6 Remove the caps from the HBMT connectors on the back of the card, and set them carefully aside.

Step 7 Visually inspect the connector on the card before you insert it into the chassis. Do not attempt to install a card with a damaged or dirty connector, as this action may damage the backplane connector or OIM.

Note Rails exist on the upper and lower left edges of the card that align with the slots in the card cage. When you install a card in the card cage, make sure that you orient the card correctly and align these rails when sliding the card into the chassis.

Step 8 Grasp the slide assistance arm with one hand and place your other hand under the carrier to support and guide it into the correct slot. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM; lift them from the bottom, using the slide-assistance arm only as an aid for balance.

Caution A CRS-3 fabric card weighs about 30 lb (14 kg). You should use two hands when handling a CRS-3 fabric card.

Step 9 Slide the card halfway into the slot. Avoid touching the card circuitry and any connectors.

Step 10 Pivot both card ejector levers so the openings on the card ejector cams at the top and bottom of the card pass over the tabs on each side of the card cage slot.

Caution Verify that the openings on the card ejector cams pass over the tabs; otherwise, one or both ejector levers might bind when you attempt to close the ejector levers, thereby damaging or breaking one or both ejector levers.

Step 11 Continue sliding the card into the card cage slot until the openings on the card ejector cams engage the tabs on each side of the card cage slot.

Note The CRS-3 fabric card has guide pins that make initial contact with the backplane connector as you slide the card into its slot. After the guide pins make contact, continue pushing on the card carrier until the card ejector levers begin pivoting forward, toward the handle in the card carrier.

Step 12 To seat the card in the backplane connector, grasp both card ejector levers and pivot them inward toward the handle in the card carrier until they are flush against the front edge of the card carrier.


OL-13669-03


Note You may hear a crunching noise when seating the card; this noise is normal.

Step 13 Use the screwdriver to turn the two captive screws on the front panel of the CRS-3 fabric card clockwise to seat the card firmly in the slot.

What to Do Next


For complete information on regulatory compliance and safety, see Regulatory Compliance and Safety Information for the Cisco CRS Carrier Routing System. For information on removing the front cosmetic cover plates, see the “Removing the Rear (OIM) Side Cosmetic Components” section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide. For information on how to power down your chassis, see the “Powering an AC Power Shelf Energized Chassis Up and Down” section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide or the “Powering a DC Power Shelf Energized Chassis Up and Down” section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide. For information on installing an OIM, see the “Installing an OIM” section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide.

Verifying the Installation of the CRS-3 Fabric CardThis section describes how to verify that the CRS-3 fabric card has been properly installed. Figure 1-5 is an illustration of the QQ123-140G switch fabric card front panel.

Figure 1-5 Switch Fabric Card Front View (QQ123-140G Shown)

Understanding the Alphanumeric LEDs

At one end of the faceplate, near an ejector lever, the CRS-3 fabric card has two four-digit alphanumeric LED displays that show a sequence of messages indicating the state of the card. In normal operation, the LED module should display IOS-XR.

Note It is normal for some displayed messages to appear too briefly in the LED display to be read.

1 Status LED 2 Alphanumeric LEDs

2496

54

12


OL-13669-03


Troubleshooting the CRS-3 Fabric Card

If the installed or replaced CRS-3 fabric card fails to operate or power up on installation:

• Make sure that the card is seated firmly in the Cisco CRS Fabric Card Chassis slot. One easy way to verify physical installation is to see whether the front faceplate of the CRS-3 fabric card is even with the fronts of the other cards installed in the card cage.

• Check whether the ejector levers are latched and that the captive screws are fastened properly. If you are uncertain, unlatch the levers, loosen the screws, and attempt to reseat the CRS-3 fabric card.

• Examine the Cisco CRS Fabric Card Chassis alarm module to see if there are any active alarm conditions. (See the section on the alarm module in Cisco CRS Carrier Routing System 16-Slot System Description.)

• Examine the Cisco CRS Fabric Card Chassis power shelves to see whether the chassis, as a whole, is receiving power.

Use the Status LEDs, located on the CRS-3 fabric card faceplate, to verify the correct installation of the CRS-3 fabric card:

• When the CRS-3 fabric card is properly installed, the Status LED turns green. If this LED is off, verify that the CRS-3 fabric card is installed correctly.

• If there is a failure during the board boot sequence, the two four-digit alphanumeric LED displays indicate the current boot phase to assist you in debugging the board failure.

Prerequisites

Software Requirements

• Cisco IOS XR Software Release 4.0.0.T or later release (Cisco IOS XR Software Release 4.0.2 for multishelf nodes)

• ROMMON 1.54 or later version

Hardware Requirements

• The Fabric card to be added must be prepared as described in the “Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System” section on page 1-2.

RP/0/RP0/CPU0:router#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#hw-module power disable loc 0/SM0/SPRP/0/RP0/CPU0:router(admin-config)#commit

RP/0/RP0/CPU0:router(admin)#show platform Node Type PLIM State Config State<snip>0/SM0/SP FC/S(SP) N/A UNPOWERED PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON<snip>


OL-13669-03


Powering up the Replaced Fabric CardThis section describes how to enable power back to the Fabric node, and verify that node is moved to Powered state.

Prerequisites





• The LCC to be added must be prepared as described in the “Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System” section on page 1-2.

• The control network must be operational and connected to all chassis.

• The power should be off for the FCC to be added.

Restrictions

None.

SUMMARY STEPS

1. admin

2. configure

3. no hw-module power disable loc 0/SM0/SP

4. commit

5. Apply power to the new LCC (Rack 1).

6. Connect all fabric cables that connect the fabric planes in the new LCC to the FCCs.

7. Specify that the LED in question is the one on the FCC OIM-LED module.

8. do show controllers fabric rack-status all detail

9. do show controllers fabric fabric-backpressure summary

10. no controllers fabric rack 1 install-mode

11. commit

12. do show controllers rack-status all detail


OL-13669-03


DETAILED STEPS


Step 1 admin

Example:RP/0/RP1/CPU0:router# admin



Step 2 configure



Step 3 no hw-module power disable loc 0/SM0/SP

Example:RP/0/RP1/CPU0:router(admin-config)# no hw-module power disable loc 0/SM0/SP

Enables the power to the specified fabric plane in your single-chassis system.

Step 4 controllers fabric rack 1 install-mode

Example:RP/0/RP1/CPU0:router(admin-config)# controllers fabric rack 1 install-mode

Modifies the target configuration to change the Rack 1 configuration to installation mode.

Step 5 commit



Step 6 Apply power to the new LCC (Rack 1). Starts up the second LCC (Rack 1).

Step 7 Connect all fabric cables that connect the fabric planes in the new LCC to the FCCs.

Interconnects the fabric cards in the LCC and FCC.

Step 8 In the FCCs, check the LEDs for the cables that connect to the new LCC (Rack 1).

Green LEDs indicate that the cables are connected correctly.

• If the LEDs display a color other than green, see Cisco IOS XR Getting Started Guide for information on interpreting the LED display.

Step 9 do show controllers fabric rack-status all detail

Example:RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric rack-status all detail

Displays the status of all racks and additional information for racks in installation mode.

• Wait for the status in the Rack in Install and Rack out of Install columns to change to UP for all planes.

Step 10 do show controllers fabric fabric-backpressure summary

Example:RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric fabric-backpressure summary

Displays the backpressure status for all racks.

• The status for the row labeled “Rack 1: All Groups Received? :” should be “Yes.”


OL-13669-03


What to Do Next

When all chassis in the multishelf system are operational and communicating with each other, it is time to continue system configuration, as described in the documents in the “Related Documents” section on page 1-63.

Troubleshooting Tips

For troubleshooting information, see the documents described in the “Related Documents” section on page 1-63.

Example

The following example shows commands to enable power to the newly installed CRS-3 Fabric Card:

RP/0/RP0/CPU0:router#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#no hw-module power disable loc 0/SM0/SPRP/0/RP0/CPU0:router(admin-config)#commit

Verify that power has been enabled to the Fabric Node (state is not UNPOWERED).

RP/0/RP0/CPU0:router(admin)#show platform Node Type PLIM State Config State<snip>0/SM0/SP FC-140G/S(SP) N/A PRESENT PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON

Step 11 no controllers fabric rack 1 install-mode

Example:RP/0/RP1/CPU0:router(admin-config)# no controllers fabric rack 1 install-mode

Modifies the target configuration to change the Rack 1 configuration to normal mode.

Step 12 commit



Step 13 do show controllers rack-status all detail

Example:RP/0/RP1/CPU0:router(admin-config)# do show controllers rack-status all detail

Displays the status of all racks in the system.

• In a properly operating system, the rack status for all racks should be Normal, and the server status should be Present.



OL-13669-03


How to Migrate to a Cisco CRS-3 Carrier Routing System (8-Slot)To migrate from an 8-slot Cisco CRS-1 Carrier Routing System to an 8-slot Cisco CRS-3 Carrier Routing System, you must complete the following tasks:




• Installing a CRS-3 Fabric Card, page 1-11.

• Verifying the Installation of the CRS-3 Fabric Card, page 1-15


In a CRS-1 system with redundant fabric (i.e. 8 planes), migrating to the CRS-3 fabric is hitless - zero drop in traffic as we migrate plane by plane from a CRS-1 to CRS-3 .



Prerequisites



• ROMMON 1.54 or later version (for Route Processor [RP])

• ROMMON 1.52 or later version (for Dual Route Processor [DRP])

Caution The ROM Monitor software must be upgraded to version 1.54 or a later version on all RPs and/or upgraded to version 1.52 or a later version on all DRPs before a Cisco CRS-1 system is upgraded to Cisco IOS XR Software Release 4.0.0.T or later release. If the router is brought up with an incompatible version of the ROM Monitor software, then the standby RP may fail to boot. For instructions to overcome a boot block in the standby RP in a single chassis system, see Cisco IOS XR ROM Monitor Guide. For other issues, contact your Cisco Systems support representative for assistance. See Obtaining Documentation, Obtaining Support, and Security Guidelines, page v. For more information, see Cisco IOS XR ROM Monitor Guide.


• The system hardware should be prepared as described in the “Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System” section on page 1-2.


OL-13669-03


• The control network must be set up as described in the “Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System” section on page 1-2.

• The single-chassis system that is being migrated does not have to be powered down.

Restrictions

None.

SUMMARY STEPS

1. admin

2. configure



5. commit

6. end


8. show controllers fabric plane all

DETAILED STEPS


Step 1 admin




Step 2 configure





Shuts down the first fabric plane in the system.

• In an 8-slot CRS-1 router, we have 4 fabric nodes, or Fabric Controller cards numbered 0/SM0/SP to 0/SM3/SP. Each Fabric Controller card has two planes. So for an 8-slot CRS-1 to CRS-3 migration we will be upgrading 2 planes at a time of the pre-existing single-chassis system.



Shuts down the second fabric plane in the system.

• In an 8-slot CRS-1 router, we have 4 fabric nodes, or Fabric Controller cards numbered 0/SM0/SP to 0/SM3/SP. Each Fabric Controller card has two planes. So for an 8-slot CRS-1 to CRS-3 migration we will be upgrading 2 planes at a time of the pre-existing single-chassis system.


OL-13669-03


What to Do Next



Prerequisites





Caution The ROM Monitor software must be upgraded to version 1.54 or a later version on all RPs and/or upgraded to version 1.52 or a later version on all DRPs before a Cisco CRS-1 system is upgraded to Cisco IOS XR Software Release 4.0.0.T or later release. If the router is brought up with an incompatible version of the ROM Monitor software, then the standby RP may fail to boot. For instructions to overcome a boot block in the standby RP in a single chassis system, see Cisco IOS XR ROM Monitor Guide. For other issues, contact your Cisco Systems support representative for assistance. See Obtaining Documentation, Obtaining Support, and Security Guidelines, page v. For more information, see Cisco IOS XR ROM Monitor Guide.



Step 5 commit




Step 6 end




Step 8 show controllers fabric plane all

Example:RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all





OL-13669-03




Restrictions

None.

SUMMARY STEPS

1. admin

2. configure


4. commit

5. end


7. show platform

DETAILED STEPS


Step 1 admin




Step 2 configure






Step 4 commit





OL-13669-03


Example




What to Do Next



This section describes how to remove a CRS-1 fabric card from the Cisco CRS Fabric Card Chassis. For more detailed information on the switch fabric card, see Cisco CRS Carrier Routing System 8-Slot Line Card Chassis System Description.


Step 5 end






• Verify that the fabric card in node 0/SM0/SP is in the UNPOWERED state.



OL-13669-03




Figure 1-6 CRS-1 Fabric Card

Prerequisites







1298

68


OL-13669-03


Steps

To remove a CRS-1 fabric card, see Figure 1-2 and follow these steps:

Figure 1-7 Removing a CRS-1 Fabric Card




Caution To prevent ESD damage, handle a CRS-1 fabric card by its ejector levers, the CRS-1 fabric card carrier edges, or the slide-assistance arm only. Do not touch any of the electrical components, pins, and circuitry.


2 Ejector lever

STATU

SP

ID/V

IDC

RS

-FC

C-S

FC

CL

EI

SN

:

1298

70

1

3

2


OL-13669-03





Caution A CRS-1 fabric card weighs about 30 lb (14 kg). You should use two hands when handling the CRS-1 fabric card.



What to Do Next


For complete information on regulatory compliance and safety, see Regulatory Compliance and Safety Information for the Cisco CRS Carrier Routing System. For information on installing a CRS-3 fabric card, see the “Installing a CRS-3 Fabric Card” section below.






OL-13669-03



Prerequisites

Before performing this task, you must first open the front (SFC) side cosmetic doors (if installed).

2496

55


OL-13669-03









Steps

To install a CRS-3 fabric card, see Figure 1-4 and follow these steps:


STATU

SP

ID/V

IDC

RS

-FC

C-S

FC

CL

EI

SN

:

1298

70

1

3

2


OL-13669-03





Step 3 Remove the SFC impedance carrier or CRS-1 fabric card you are replacing from the designated slot, and set it carefully aside. (See the “Removing an Impedance Carrier” section in the Cisco CRS Carrier Routing System 8-Slot Line Card Chassis Installation Guide or the “Removing an SFC” section in the Cisco CRS Carrier Routing System 8-Slot Line Card Chassis Installation Guide.)












2 Ejector lever


OL-13669-03




Note A CRS-3 fabric card has guide pins that make initial contact with the backplane connector as you slide the card into its slot. After the guide pins make contact, continue pushing on the card carrier until the card ejector levers begin pivoting forward, toward the handle in the card carrier.




What to Do Next



Verifying the Installation of the CRS-3 Fabric CardThis section describes how to verify that the CRS-3 fabric card has been properly installed. Figure 1-10 is an illustration of the QQ123-140G switch fabric card front panel.


OL-13669-03


Figure 1-10 Switch Fabric Card Front View (QQ123 Shown)


At one end of the faceplate, near an ejector lever, a CRS-3 fabric card has two four-digit alphanumeric LED displays that show a sequence of messages indicating the state of the card. In normal operation, the LED module should display IOS-XR.






• Examine the Cisco CRS Fabric Card Chassis alarm module to see if there are any active alarm conditions. (See the section on the alarm module in Cisco CRS Carrier Routing System 8-Slot Line Card Chassis System Description.)





Prerequisites





2496

54

12


OL-13669-03




Restrictions

None.

SUMMARY STEPS

1. admin

2. configure


4. commit

5. Verify that power has been removed from the Fabric Node (state is UNPOWERED).

6. show platform




Prerequisites





OL-13669-03






Restrictions

None.

SUMMARY STEPS

1. admin

2. configure


4. commit

5. Verify that power has been enabled to the Fabric Node (state is not UNPOWERED).

6. show platform

Node Type PLIM State Config State<snip>0/SM0/SP FC-140G/S(SP) N/A PRESENT PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON<snip>

Booting Up the Newly Migrated Cisco CRS-3 FabricThis section describes the process for booting up the new Cisco CRS-3 fabric.

When the Cisco CRS-3 fabric node is powered on, The Route Processor (RP) will automatically boot the new fabric. Please wait for the boot process to complete. The node will transition from state MBI-BOOT to MBI-RUNNING as the software is being installed.

When the boot process completes the node-state will be IOS-XR RUN.

RP/0/RP0/CPU0:router(admin)#show platform Node Type PLIM State Config State<snip>0/SM0/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON

Administratively Enabling the Fabric PlaneThis section describes the process for administratively enabling each new Cisco CRS-3 fabric plane.


OL-13669-03


Once enabled, the fabric plane status would be “Up”.

RP/0/RP0/CPU0:router#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#no controller fabric plane 0 shutRP/0/RP0/CPU0:router(admin-config)#no controller fabric plane 1 shutRP/0/RP0/CPU0:router(admin-config)#commit

Verify that each of the eight fabric planes is enabled by executing the show controllers fabric plane all command:

RP/0/RP0/CPU0:router(admin)#show controllers fabric plane allPlane Admin Oper up->dn up->mcast Id State State counter counter --------------------------------------------- 0 UP UP 2 2 1 UP UP 2 2 2 UP UP 0 0 3 UP UP 0 0 4 UP UP 0 0 5 UP UP 0 0 6 UP UP 0 0 7 UP UP 0 0

Each plane transitions from UP -> MCAST_DOWN -> DOWN -> MCAST_DOWN -> UP. Thus each plane will cycle through up->dn twice. This is why the up->dn counter shows 2. Similarly each plane will cycle through mcast_dn->up twice as well and the mcast_dn->up counter shows 2.

Verifying Traffic Statistics on the Newly Migrated Cisco CRS-3 NodeTo ascertain that traffic is flowing on the CRS-3 node please run the following command on both the planes that have been migrated. Run it a few times to ensure that the counters are incrementing. The lost or error counters should not be incrementing.

The same command should also be applied on the legacy nodes (not yet migrated) to make sure there is no traffic lost or traffic with errored cells.

RP/0/RP0/CPU0:router(admin)#show controllers fabric plane 0 statistics detail

Total number of providers for the statistics: 1 Total received data cells: 7063 Total received unicast data cells: 4487 Total received low priority unicast data cells: 4487 Total received high priority unicast data cells: 0 Total received multicast data cells: 2576 Total received low priority multicast data cells: 2050 Total received high priority multicast data cells: 526 Total transmitted data cells: 21094 Total transmitted unicast data cells: 4487 Total transmitted low priority unicast data cells: 4487 Total transmitted high priority unicast data cells: 0 Total transmitted multicast data cells: 16607 Total transmitted low priority multicast data cells: 13977 Total transmitted high priority multicast data cells: 2630 Total received correctable errored cells: 0 Total received uncorrectable errored cells: 0 Total received parity error cells: 0 Total received stomp cells: 0


OL-13669-03


Total received kill cells: 0 Total received unknown cells: 0 Total transmitted bogus cells: 4 Total transmitted statically routed control cells: 0 Total transmitted stomp cells: 0 Total transmitted kill cells: 0 Total transmitted ECI cells: 0 Total transmitted LCE cells: 0 Total unicast lost cells: 0 Total multicast lost cells: 0 Total ctb enqueue to off queue cells: 0 Total non-ctb enqueue to off queue cells: 0 Total incoming header error cells: 0 Total incoming data error cells: 0 Total outgoing header error cells: 0 Total outgoing data error cells: 0 Total scs ce error cells: 0 Total scs uce error cells: 0 Last clearing of "show controller fabric plane" counters 00:06:22

Verifying Fabric Link ConnectivityThis section describes the commands used to check the Line Card (LC) to Fabric and Route Processor (RP) to Fabric links for all LCs and RPs in the router (and for DRPs as well). The following commands may be used to check the link connectivity for each LC/RP node.

IngressQ to Fabric connectivity:

show controller ingressq fabric links loc <LC/RP/DRP location>

Fabric to FabricQ connectivity:

show controller fabricq link all loc <LC/RP/DRP location>

All links should be UP. Please repeat the CLI for ALL LC/RP/DRP locations in the router.

RP/0/RP0/CPU0:router(admin)#show controllers ingressq fabric links loc 0/5/cpu0Ingressq link stateplane-id link-id ADMIN-STATE OPER-STATE AVAIL-STATE UP-COUNT ----------------------------------------------------.0 0 UP UP UP 2 0 8 UP UP UP 2 0 16 UP UP UP 2 0 24 UP UP UP 2 1 1 UP UP UP 2 1 9 UP UP UP 2 1 17 UP UP UP 2 1 25 UP UP UP 2 2 2 UP UP UP 1 2 10 UP UP UP 1 2 18 UP UP UP 1 2 26 UP UP UP 1 3 3 UP UP UP 1 3 11 UP UP UP 1 3 19 UP UP UP 1 3 27 UP UP UP 1 4 4 UP UP UP 1 4 12 UP UP UP 1 4 20 UP UP UP 1 4 28 UP UP UP 1


OL-13669-03


5 5 UP UP UP 1 5 13 UP UP UP 1 5 21 UP UP UP 1 5 29 UP UP UP 1 6 6 UP UP UP 1 6 14 UP UP UP 1 6 22 UP UP UP 1 6 30 UP UP UP 1 7 7 UP UP UP 1 7 15 UP UP UP 1 7 23 UP UP UP 1 7 31 UP UP UP 1

RP/0/RP0/CPU0:router(admin)#show controllers fabricq link-info all loc 0/5/cpu0

Location: 0/5/CPU0 Asic Instance: 0 Fabric Destination Address: 20 Retry period: 0 sec Link Active bitmap (1=up,0=down): 0xffffffff +------------------------------------------------------------------------+ |Link #|Driver state | FSDB state |Barrier state|Up (Drv Barr)| Errors | +------------------------------------------------------------------------+ | 0 | Up | Up | Up | 2 2 | | | 1 | Up | Up | Up | 2 2 | | | 2 | Up | Up | Up | 2 2 | | | 3 | Up | Up | Up | 2 2 | | | 4 | Up | Up | Up | 2 2 | | | 5 | Up | Up | Up | 2 2 | | | 6 | Up | Up | Up | 2 2 | | | 7 | Up | Up | Up | 2 2 | | | 8 | Up | Up | Up | 1 1 | | | 9 | Up | Up | Up | 1 1 | | | 10 | Up | Up | Up | 1 1 | | | 11 | Up | Up | Up | 1 1 | | | 12 | Up | Up | Up | 1 1 | | | 13 | Up | Up | Up | 1 1 | | | 14 | Up | Up | Up | 1 1 | | | 15 | Up | Up | Up | 1 1 | | | 16 | Up | Up | Up | 1 1 | | | 17 | Up | Up | Up | 1 1 | | | 18 | Up | Up | Up | 1 1 | | | 19 | Up | Up | Up | 1 1 | | | 20 | Up | Up | Up | 1 1 | | | 21 | Up | Up | Up | 1 1 | | | 22 | Up | Up | Up | 1 1 | | | 23 | Up | Up | Up | 1 1 | | | 24 | Up | Up | Up | 1 1 | | | 25 | Up | Up | Up | 1 1 | | | 26 | Up | Up | Up | 1 1 | | | 27 | Up | Up | Up | 1 1 | | | 28 | Up | Up | Up | 1 1 | | | 29 | Up | Up | Up | 1 1 | | | 30 | Up | Up | Up | 1 1 | | | 31 | Up | Up | Up | 1 1 | | +------------------------------------------------------------------------+

Location: 0/5/CPU0 Asic Instance: 1 Fabric Destination Address: 21 Retry period: 0 sec Link Active bitmap (1=up,0=down): 0xffffffff +------------------------------------------------------------------------+


OL-13669-03


|Link #|Driver state | FSDB state |Barrier state|Up (Drv Barr)| Errors | +------------------------------------------------------------------------+ | 0 | Up | Up | Up | 2 2 | | | 1 | Up | Up | Up | 2 2 | | | 2 | Up | Up | Up | 2 2 | | | 3 | Up | Up | Up | 2 2 | | | 4 | Up | Up | Up | 2 2 | | | 5 | Up | Up | Up | 2 2 | | | 6 | Up | Up | Up | 2 2 | | | 7 | Up | Up | Up | 2 2 | | | 8 | Up | Up | Up | 1 1 | | | 9 | Up | Up | Up | 1 1 | | | 10 | Up | Up | Up | 1 1 | | | 11 | Up | Up | Up | 1 1 | | | 12 | Up | Up | Up | 1 1 | | | 13 | Up | Up | Up | 1 1 | | | 14 | Up | Up | Up | 1 1 | | | 15 | Up | Up | Up | 1 1 | | | 16 | Up | Up | Up | 1 1 | | | 17 | Up | Up | Up | 1 1 | | | 18 | Up | Up | Up | 1 1 | | | 19 | Up | Up | Up | 1 1 | | | 20 | Up | Up | Up | 1 1 | | | 21 | Up | Up | Up | 1 1 | | | 22 | Up | Up | Up | 1 1 | | | 23 | Up | Up | Up | 1 1 | | | 24 | Up | Up | Up | 1 1 | | | 25 | Up | Up | Up | 1 1 | | | 26 | Up | Up | Up | 1 1 | | | 27 | Up | Up | Up | 1 1 | | | 28 | Up | Up | Up | 1 1 | | | 29 | Up | Up | Up | 1 1 | | | 30 | Up | Up | Up | 1 1 | | | 31 | Up | Up | Up | 1 1 | | +------------------------------------------------------------------------+

How to Migrate to a Cisco CRS-3 Carrier Routing System (4-Slot)To migrate from a 4-slot Cisco CRS-1 Carrier Routing System to a 4-slot Cisco CRS-3 Carrier Routing System, you must complete the following tasks:




• Installing a CRS-3 Fabric Card, page 1-11.

• Verifying the Installation of a CRS-3 Fabric Card, page 1-15


In a CRS-1 system with redundant fabric (i.e. 8 planes), migration to CRS-3 fabric is hitless - zero drop in traffic as we migrate plane by plane from a CRS-1 to CRS-3 .



OL-13669-03



Prerequisites





Caution The ROM Monitor software must be upgraded to version 1.54 or a later version on all RPs and/or upgraded to version 1.52 or a later version on all DRPs before a Cisco CRS-1 system is migrated to Cisco IOS XR Software Release 4.0.0.T or later release. If the router is brought up with an incompatible version of the ROM Monitor software, then the standby RP may fail to boot. For instructions to overcome a boot block in the standby RP in a single chassis system, see Cisco IOS XR ROM Monitor Guide. For other issues, contact your Cisco Systems support representative for assistance. See Obtaining Documentation, Obtaining Support, and Security Guidelines, page v. For more information, see Cisco IOS XR ROM Monitor Guide.





Restrictions

None.

SUMMARY STEPS

1. admin

2. configure


4. commit

5. end




OL-13669-03


DETAILED STEPS

What to Do Next



Prerequisites





Step 1 admin




Step 2 configure





Shuts down the fabric plane in the system.

• In a 4-slot CRS-1 router, we have four fabric nodes, or Fabric Controller cards, numbered 0/SM0/SP to 0/SM3/SP. Each Fabric Controller card has one plane. So for a 4-slot CRS-1 to CRS-3 migration we will be migrating one plane at a time for all four planes.

Step 4 commit



• This step brings up the previously shutdown plane, which is now configured to use the CRS-3 fabric card.

Step 5 end




Step 7 show controllers fabric plane all

Example:RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all




OL-13669-03



Caution The ROM Monitor software must be upgraded to version 1.54 or a later version on all RPs and/or upgraded to version 1.52 or a later version on all DRPs before a Cisco CRS-1 system is migrated to Cisco IOS XR Software Release 4.0.0.T or later release. If the router is brought up with an incompatible version of the ROM Monitor software, then the standby RP may fail to boot. For instructions to overcome a boot block in the standby RP in a single chassis system, see Cisco IOS XR ROM Monitor Guide. For other issues, contact your Cisco Systems support representative for assistance. See Obtaining Documentation, Obtaining Support, and Security Guidelines, page v. For more information, see Cisco IOS XR ROM Monitor Guide.





Restrictions

None.

SUMMARY STEPS

1. admin

2. configure


4. commit

5. end




OL-13669-03


DETAILED STEPS

Example





Step 1 admin




Step 2 configure






Step 4 commit



• This step brings up the previously shutdown plane, which is now configured to use the CRS-3 fabric card.

Step 5 end






• Verify that the fabric card in node 0/SM0/SP is in the UNPOWERED state.


OL-13669-03


What to Do Next



This section describes how to remove a CRS-1 fabric card from the Cisco CRS Fabric Card Chassis. For more detailed information on the switch fabric card, see Cisco CRS Carrier Routing System 4-Slot Line Card Chassis System Description.





Prerequisites


1298

68


OL-13669-03







Steps

To remove an CRS-1 fabric card, see Figure 1-12 and follow these steps:



2 Ejector lever

STATU

SP

ID/V

IDC

RS

-FC

C-S

FC

CL

EI

SN

:

1298

70

1

3

2


OL-13669-03












What to Do Next



Installing a CRS-3 Fabric CardThis section describes how to install a CRS-3 fabric card in the Cisco CRS Fabric Card Chassis. For more detailed information on the switch fabric card, see Cisco CRS Carrier Routing System 4-Slot Line Card Chassis System Description.



OL-13669-03





OL-13669-03



2496

55


OL-13669-03


Prerequisites

Before performing this task, you must first open the front (SFC) side cosmetic doors (if installed). You must already have an OIM installed in your chassis in the slot corresponding to where you plan to install the CRS-3 fabric card before you install the CRS-3 fabric card (for example, if you are planning on installing the CRS-3 fabric card in slot 0, you must have an OIM installed in slot 0 on the rear of the chassis), and you must remove any impedance carrier or slot cover from the slot in which you are installing the CRS-3 fabric card.









OL-13669-03


Steps







2 Ejector lever

STATU

SP

ID/V

IDC

RS

-FC

C-S

FC

CL

EI

SN

:

1298

70

1

3

2


OL-13669-03


Step 3 Remove the impedance carrier or CRS-1 fabric card you are replacing from the designated slot, and set it carefully aside. (See the “Removing an Impedance Carrier” section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide or the “Removing an SFC” section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide.)
















OL-13669-03




What to Do Next



Verifying the Installation of the CRS-3 Fabric CardThis section describes how to verify that a CRS-3 fabric card (QQ123-140G) has been properly installed. Figure 1-15 is an illustration of the QQ123-140G switch fabric card front panel.

Figure 1-15 Switch Fabric Card Front View (QQ123-140G Shown)





2496

54

12


OL-13669-03


Troubleshooting the CRS-3 fabric card









Prerequisites









OL-13669-03



Prerequisites








Restrictions

None.

SUMMARY STEPS

1. admin

2. configure


4. commit

5. Verify that power has been enabled to the Fabric Node (state is not UNPOWERED).

6. show platform

Node Type PLIM State Config State<snip>0/SM0/SP FC-140G/S(SP) N/A PRESENT PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON<snip>

Booting Up the Newly Migrated Cisco CRS-3 FabricThis section describes the process for booting up the new Cisco CRS-3 fabric.



OL-13669-03



RP/0/RP0/CPU0:router(admin)#show platform Node Type PLIM State Config State<snip>0/SM0/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON

Administratively Enabling the Fabric PlaneThis section describes the process for administratively enabling each new Cisco CRS-3 fabric plane.






Verifying Traffic Statistics on the Newly Migrated Cisco CRS-3 NodeTo ascertain that traffic is flowing on the CRS-3 node please run the following command on both the planes that have been migrated. Run it a few times to ensure that the counters are incrementing. The lost or error counters should not be incrementing.

The same command should also be applied on the legacy nodes (not yet migrated) to make sure there is no traffic lost or traffic with errored cells.


Total number of providers for the statistics: 1 Total received data cells: 7063 Total received unicast data cells: 4487


OL-13669-03


Total received low priority unicast data cells: 4487 Total received high priority unicast data cells: 0 Total received multicast data cells: 2576 Total received low priority multicast data cells: 2050 Total received high priority multicast data cells: 526 Total transmitted data cells: 21094 Total transmitted unicast data cells: 4487 Total transmitted low priority unicast data cells: 4487 Total transmitted high priority unicast data cells: 0 Total transmitted multicast data cells: 16607 Total transmitted low priority multicast data cells: 13977 Total transmitted high priority multicast data cells: 2630 Total received correctable errored cells: 0 Total received uncorrectable errored cells: 0 Total received parity error cells: 0 Total received stomp cells: 0 Total received kill cells: 0 Total received unknown cells: 0 Total transmitted bogus cells: 4 Total transmitted statically routed control cells: 0 Total transmitted stomp cells: 0 Total transmitted kill cells: 0 Total transmitted ECI cells: 0 Total transmitted LCE cells: 0 Total unicast lost cells: 0 Total multicast lost cells: 0 Total ctb enqueue to off queue cells: 0 Total non-ctb enqueue to off queue cells: 0 Total incoming header error cells: 0 Total incoming data error cells: 0 Total outgoing header error cells: 0 Total outgoing data error cells: 0 Total scs ce error cells: 0 Total scs uce error cells: 0 Last clearing of "show controller fabric plane" counters 00:06:22







RP/0/RP0/CPU0:router(admin)#show controllers ingressq fabric links loc 0/5/cpu0Ingressq link stateplane-id link-id ADMIN-STATE OPER-STATE AVAIL-STATE UP-COUNT ----------------------------------------------------.0 0 UP UP UP 2 0 8 UP UP UP 2 0 16 UP UP UP 2 0 24 UP UP UP 2


OL-13669-03


1 1 UP UP UP 2 1 9 UP UP UP 2 1 17 UP UP UP 2 1 25 UP UP UP 2 2 2 UP UP UP 1 2 10 UP UP UP 1 2 18 UP UP UP 1 2 26 UP UP UP 1 3 3 UP UP UP 1 3 11 UP UP UP 1 3 19 UP UP UP 1 3 27 UP UP UP 1 4 4 UP UP UP 1 4 12 UP UP UP 1 4 20 UP UP UP 1 4 28 UP UP UP 1 5 5 UP UP UP 1 5 13 UP UP UP 1 5 21 UP UP UP 1 5 29 UP UP UP 1 6 6 UP UP UP 1 6 14 UP UP UP 1 6 22 UP UP UP 1 6 30 UP UP UP 1 7 7 UP UP UP 1 7 15 UP UP UP 1 7 23 UP UP UP 1 7 31 UP UP UP 1


Location: 0/5/CPU0 Asic Instance: 0 Fabric Destination Address: 20 Retry period: 0 sec Link Active bitmap (1=up,0=down): 0xffffffff +------------------------------------------------------------------------+ |Link #|Driver state | FSDB state |Barrier state|Up (Drv Barr)| Errors | +------------------------------------------------------------------------+ | 0 | Up | Up | Up | 2 2 | | | 1 | Up | Up | Up | 2 2 | | | 2 | Up | Up | Up | 2 2 | | | 3 | Up | Up | Up | 2 2 | | | 4 | Up | Up | Up | 2 2 | | | 5 | Up | Up | Up | 2 2 | | | 6 | Up | Up | Up | 2 2 | | | 7 | Up | Up | Up | 2 2 | | | 8 | Up | Up | Up | 1 1 | | | 9 | Up | Up | Up | 1 1 | | | 10 | Up | Up | Up | 1 1 | | | 11 | Up | Up | Up | 1 1 | | | 12 | Up | Up | Up | 1 1 | | | 13 | Up | Up | Up | 1 1 | | | 14 | Up | Up | Up | 1 1 | | | 15 | Up | Up | Up | 1 1 | | | 16 | Up | Up | Up | 1 1 | | | 17 | Up | Up | Up | 1 1 | | | 18 | Up | Up | Up | 1 1 | | | 19 | Up | Up | Up | 1 1 | | | 20 | Up | Up | Up | 1 1 | | | 21 | Up | Up | Up | 1 1 | | | 22 | Up | Up | Up | 1 1 | | | 23 | Up | Up | Up | 1 1 | |


OL-13669-03


| 24 | Up | Up | Up | 1 1 | | | 25 | Up | Up | Up | 1 1 | | | 26 | Up | Up | Up | 1 1 | | | 27 | Up | Up | Up | 1 1 | | | 28 | Up | Up | Up | 1 1 | | | 29 | Up | Up | Up | 1 1 | | | 30 | Up | Up | Up | 1 1 | | | 31 | Up | Up | Up | 1 1 | | +------------------------------------------------------------------------+









OL-13669-03


13. commit


DETAILED STEPS


Step 1 admin




Step 2 configure









Step 5 commit














OL-13669-03


What to Do Next




Example




RP/0/RP0/CPU0:router(admin)#show platform Node Type PLIM State Config State<snip>0/SM0/SP FC-140G/S(SP) N/A PRESENT PWR,NSHUT,MON








Step 12 commit









OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemConfiguration Examples for Migrating to a Cisco CRS-3 Carrier Routing System

0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON

Configuration Examples for Migrating to a Cisco CRS-3 Carrier Routing System

This section provides examples for the following procedures:

• Displaying Chassis Serial Numbers: Example, page 1-58

• Adding a Fabric Card Chassis: Example, page 1-58

• Adding an LCC to a Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis: Example, page 1-61

Displaying Chassis Serial Numbers: ExampleThe following example shows how to display the chassis serial numbers in a Cisco CRS-3 Carrier Routing System:

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

RACK 0 : MAIN: board type 0001e0 800-24872-01 rev 20 dev N/A S/N TBA08260159 PCA: 73-7640-05 rev 20 PID: CRS-16-LCC VID: V01 CLEI: IPM6700DRA ECI: 445022 RACK NUM: 0

RACK 1 :

MAIN: board type 0001e0 800-24872-01 rev 20

dev N/A S/N TBA08260159 PCA: 73-7640-05 rev 20 PID: CRS-16-LCC VID: V01 CLEI: IPM6700DRA ECI: 445022 RACK NUM: 0

RACK 240 : MAIN: board type 0001e0


OL-13669-03


800-24872-01 rev 20 dev N/A S/N TBA08260159 PCA: 73-7640-05 rev 20 PID: CRS-16-LCC VID: V01 CLEI: IPM6700DRA ECI: 445022 RACK NUM: 0

Adding a Fabric Card Chassis: ExampleThe following example shows how to add a single FCC to an existing single-chassis system:

RP/0/RP1/CPU0:router# adminRP/0/RP1/CPU0:router(admin)# configure RP/0/RP1/CPU0:router(admin-config)# dsc serial TBC0820052000001 rack 0

RP/0/RP1/CPU0:router(admin-config)# dsc serial TBC0820052000000 rack F0

RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 0 RP/0/RP1/CPU0:router(admin-config)# oim count 1RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM9/FM








RP/0/RP1/CPU0:router(admin-config)# commitRP/0/RP1/CPU0:router(admin-config)# end

Power is applied to the FCC at this time.

RP/0/RP1/CPU0:router(admin)# show platform F0/**/*

Node Type PLIM State Config State-----------------------------------------------------------------------------F0/SM0/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MON


OL-13669-03


F0/SM3/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM6/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM9/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM12/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM15/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM18/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM21/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SC0/CPU0 FCC-SC(Standby) N/A IOS XR RUN PWR,NSHUT,MONF0/SC1/CPU0 FCC-SC(Active) N/A IOS XR RUN PWR,NSHUT,MONF0/AM0/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MONF0/AM1/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MONF0/LM0/SP FCC-LED(SP) N/A IOS XR RUN PWR,NSHUT,MONF0/LM1/SP FCC-LED(SP) N/A IOS XR RUN PWR,NSHUT,MON

RP/0/RP1/CPU0:router(admin)# configure

RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric plane all

Flags: P - plane admin down, p - plane oper down C - card admin down, c - card oper down L - link port admin down, l - linkport oper down A - asic admin down, a - asic oper down B - bundle port admin Down, b - bundle port oper down I - bundle admin down, i - bundle oper down N - node admin down, n - node down o - other end of link down d - data down f - failed component downstream m - plane multicast down

Plane Admin Oper Id State State -------------------- 0 UP UP 1 UP UP 2 UP UP 3 UP UP 4 UP UP 5 UP UP 6 UP UP 7 UP UP

RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 0 shutdownRP/0/RP1/CPU0:router(admin-config)# commitRP/0/RP1/CPU0:router(admin-config)# end

RP/0/RP1/CPU0:Mar 4 18:37:55.055 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDOWN : Plane 0 state changed to DOWN: RP/0/RP1/CPU0:Mar 4 18:37:55.088 : config[65733]: %MGBL-LIBTARCFG-6-ADMIN_COMMIT : Administration configuration committed by user 'user_a'.

The FC/S card is replaced with an FC-140G/S card at this point.

RP/0/RP1/CPU0:Mar 4 18:38:32.680 : oir_daemon[245]: %PLATFORM-OIRD-5-OIROUT : OIR: Node 0/SM0/SP removed RP/0/RP1/CPU0:Mar 4 18:38:54.328 : oir_daemon[245]: %PLATFORM-OIRD-5-OIRIN : OIR: Node 0/SM0/SP inserted SP/0/SM0/SP:Mar 4 18:40:52.575 : alphadisplay[100]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : Alpha display on node 0/SM0/SP changed to IOS-XR in state default SP/0/SM0/SP:Mar 4 18:41:34.027 : sfe_drvr[108]: %FABRIC-FABRIC_DRVR-6-ASIC_INITIALIZED : Fabric ASICs initialized

RP/0/RP1/CPU0:router(admin)# show platform 0/sm9/sp


OL-13669-03


0/SM9/SP FC-140G/S(SP) N/A IOS-XR RUN PWR,NSHUT,MON

The fabric cable is attached to the FC-140G/S card at this point.

RP/0/RP1/CPU0:router(admin)# configure RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric plane 0 detail... Plane Admin Oper Down Total Down Id State State Flags Bundles Bundles ------------------------------------------------------ 0 DOWN DOWN pPm 9 6

RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric plane 0 detail... Plane Admin Oper Down Total Down Id State State Flags Bundles Bundles ------------------------------------------------------ 0 DOWN DOWN P 9 6

RP/0/RP1/CPU0:router(admin-config)# no controllers fabric plane 0 shutdownRP/0/RP1/CPU0:router(admin-config)# commit

RP/0/RP1/CPU0:Mar 4 18:47:42.930 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDOWN : Plane 0 state changed to UP: RP/0/RP1/CPU0:Mar 4 18:47:42.954 : config[65733]: %MGBL-LIBTARCFG-6-ADMIN_COMMIT : Administration configuration committed by user 'user_a'.

RP/0/RP1/CPU0:router(admin-config)# endRP/0/RP1/CPU0:router(admin)# show controllers fabric plane all

Flags: P - plane admin down, p - plane oper down C - card admin down, c - card oper down L - link port admin down, l - linkport oper down A - asic admin down, a - asic oper down B - bundle port admin Down, b - bundle port oper down I - bundle admin down, i - bundle oper down N - node admin down, n - node down o - other end of link down d - data down f - failed component downstream m - plane multicast down

Plane Admin Oper Id State State -------------------- 0 UP UP 1 UP UP 2 UP UP 3 UP UP 4 UP UP 5 UP UP 6 UP UP 7 UP UP

Adding an LCC to a Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis: Example

The following example shows how to add an LCC to a Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis:


OL-13669-03


RP/0/RP1/CPU0:router# adminRP/0/RP1/CPU0:router(admin)# configure RP/0/RP1/CPU0:router(admin-config)# dsc serial TBC0820031000000 rack 1RP/0/RP1/CPU0:router(admin-config)# control fabric rack 1 install-modeRP/0/RP1/CPU0:router(admin-config)# commit

Apply power, attach cables, and check cable LEDs.

RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric rack-status all detail

Rack Rack ServerNum Status Status---- ------ ------

0 NORMAL PRESENT 1 INSTALL PRESENT Oper State ---------------------- Plane Admin Rack in Rack out Num State Install of Install ----- ----- ------- ---------- 0 UP UP UP 1 UP UP DOWN 2 UP UP DOWN 3 UP UP DOWN 4 UP UP DOWN 5 UP UP DOWN 6 UP UP DOWN 7 UP UP DOWN

F0 NORMAL PRESENT

RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric rack-status all detail


0 NORMAL PRESENT 1 INSTALL PRESENT Oper State ---------------------- Plane Admin Rack in Rack out Num State Install of Install ----- ----- ------- ---------- 0 UP UP UP 1 UP UP UP 2 UP UP UP 3 UP UP UP 4 UP UP UP 5 UP UP UP 6 UP UP UP 7 UP UP UP

F0 NORMAL PRESENT

RP/0/RP1/CPU0:router(admin-config)# show controllers fabric fabric-backpressure summary

Expected BP Fabric Groups in the System: 0 1 2 3

Rack 0: All Groups Received? : Yes ------

Rack 1: All Groups Received? : Yes


OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemWhere to Go Next

RP/0/RP1/CPU0:router(admin-config)# no controllers fabric rack 1 install-modeRP/0/RP1/CPU0:router(admin-config)# commitRP/0/RP1/CPU0:router(admin-config)# do show controllers rack-status all detail


0 NORMAL PRESENT 1 NORMAL PRESENT F0 NORMAL PRESENT

Where to Go NextWhen all fabric planes on both LCCs are migrated, configured and connected to the FCCs, see Cisco IOS XR Getting Started Guide for information on general system setup and operation.

If you need to downgrade your Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis back to a Cisco CRS-1 Carrier Routing System 16-Slot Line Card Chassis, see Chapter 2, “Converting to an Integrated Switch System.”

For this release use the Turbo boot procedure described in Appendix A to downgrade the system before swapping out the fabric to downgrade your Cisco CRS-3 Carrier Routing System Router back to a Cisco CRS-1 Carrier Routing System Router.


OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing SystemAdditional References

Additional ReferencesThe following sections provide references related to upgrading a single-chassis Cisco CRS-1 system to a single-chassis Cisco CRS-3 system.

Related Documents • Related Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Documentation, page 1-63

• Related Documentation for Configuring the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Using Cisco IOS XR, page 1-63

Related Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Documentation

For additional documentation related to hardware installation and site planning, see the following Cisco Systems documents:

Related Documentation for Configuring the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Using Cisco IOS XR

For additional documentation related to the configuration of the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis using Cisco IOS XR, see the following Cisco Systems documents:

Related Topic Document Title

Cisco CRS Carrier Routing System 16-slot line card chassis system description and installation planning

Cisco CRS Carrier Routing System 16-Slot Line Card Chassis System Description

Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Site Planning Guide

FCC installation Cisco CRS Carrier Routing System Fabric Card Chassis Installation Guide

LCC installation Cisco CRS Carrier Routing System 16-Slot Line Card Chassis System Description

Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide

Cabling between all system components Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Interconnection and Cabling Guide

Color codes for FCC OIM-LED panel LEDs Cisco CRS Carrier Routing System 16-Slot Line Card Chassis System Description

Troubleshooting Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Troubleshooting Guide


OL-13669-03


Technical Assistance

Related Topic Document Title

Cisco CRS Carrier Routing System 16-Slot Line Card Chassis configuration and general system configuration after the fabric installation and configuration is complete

Cisco IOS XR Getting Started Guide

Description Link

The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/techsupport


OL-13669-03

http://www.cisco.com/techsupport



OL-13669-03


C H A P T E R 2
Downgrading Your Cisco CRS-3 Carrier Routing System Router Back to a Cisco CRS-1 Carrier Routing System Router
This chapter describes how to downgrade a single-chassis Cisco CRS-3 Carrier Routing System back to a single-chassis Cisco CRS-1 Carrier Routing System.

This chapter describes the following concepts:

• Downgrading your Cisco CRS-3 Carrier Routing System 16-slot line card chassis back to a Cisco CRS-1 Carrier Routing System 16-slot line card chassis



Feature History for the Cisco CRS-3 Carrier Routing System


• Prerequisites for Downgrading your Cisco CRS-3 Carrier Routing System Router Back to a Cisco CRS-1 Carrier Routing System Router, page 2-2

• Downgrading your Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis Back to a Cisco CRS-1 Carrier Routing System 16-Slot Line Card Chassis, page 2-2




Release 4.0.0.T The Cisco CRS-3 Carrier Routing System was introduced.

Release 4.0.1 The Cisco CRS-3 Carrier Routing System adds support for 100GE interfaces.


Chapter 2 Downgrading Your Cisco CRS-3 Carrier Routing System Router Back to a Cisco CRS-1 Carrier Routing System Router

Prerequisites for Downgrading your Cisco CRS-3 Carrier Routing System Router Back to a Cisco CRS-1 Carrier Routing System Router

Prerequisites for Downgrading your Cisco CRS-3 Carrier Routing System Router Back to a Cisco CRS-1 Carrier Routing System Router

If you are planning to downgrade your system software as part of downgrading the Cisco CRS-3 hardware you must ensure that the Cisco CRS-3 hardware is swapped with CRS-1 hardware from the system FIRST before downgrading Cisco IOS XR software from Release 4.0.0.T software to an earlier release. Cisco IOS XR software Release 4.0.0.T software will support CRS-1 hardware. Downgrading Cisco IOS XR software from Release 4.0.0.T software to an earlier release requires the Turboboot method


• Restrictions for Downgrading a Cisco CRS-3 Carrier Routing System Back to a Cisco CRS-1 Carrier Routing System Router, page 2-2




Restrictions for Downgrading a Cisco CRS-3 Carrier Routing System Back to a Cisco CRS-1 Carrier Routing System Router

Caution Before performing the procedures that are described in this chapter, it is important to wait until the previous step is completed before attempting the next step. Failure to do so can result in a failure of the downgrading procedure. If a previous step fails to complete successfully, contact Cisco Technical Support before proceeding. We do not have a rollover procedure defined.

Downgrading your Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis Back to a Cisco CRS-1 Carrier Routing System 16-Slot Line Card Chassis

This section contains the following procedures:

• Verifying the Fabric Plane Status, page 2-3


• Power Disable the Cisco CRS-3 Fabric Card, page 2-5


OL-13669-03



• Swap the Cisco CRS-3 Fabric with the Newly Installed Cisco CRS-1 Fabric, page 2-6

• Power-up the Newly Installed Cisco CRS-1 Fabric Card, page 2-17

• Booting Up the Newly Downgraded Cisco CRS-1 Fabric, page 2-17

• Administratively Enabling the Fabric Plane, page 2-18

• Verifying Traffic Statistics on the Newly Downgraded Cisco CRS-1 Node, page 2-18

• Verifying Fabric Link Connectivity, page 2-39

• Downgrading the Next Legacy Node, page 2-41

Verifying the Fabric Plane StatusFirst, execute the show platform command to verify that all Cisco CRS-3 fabric cards are operational (i.e. IOS-XR RUN) and all Fabric Planes are UP.

RP/0/RP0/CPU0:router(admin)#show platform Node Type PLIM State Config State<snip>0/SM0/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON<snip>

Next, execute the show controllers fabric plane all command to verify that all Fabric Planes are UP:


Note The up->down counter records the number of times the plane has flapped between UP and DOWN. Similarly, up->mcast_Down counter records the number of plane transitions between MCAST_DOWN and UP].

Before starting the downgrade process, take a snapshot of the traffic flowing through the router and use it as a benchmark to compare against traffic flow during the downgrade and/or after completing the downgrade. Since it is a hitless downgrade, there should be zero impact to the traffic flow during the downgrade and/or after completing the downgrade.



OL-13669-03



Total number of providers for the statistics: 1 Total received data cells: 7063 Total received unicast data cells: 4487 Total received low priority unicast data cells: 4487 Total received high priority unicast data cells: 0 Total received multicast data cells: 2576 Total received low priority multicast data cells: 2050 Total received high priority multicast data cells: 526 Total transmitted data cells: 21094 Total transmitted unicast data cells: 4487 Total transmitted low priority unicast data cells: 4487 Total transmitted high priority unicast data cells: 0 Total transmitted multicast data cells: 16607 Total transmitted low priority multicast data cells: 13977 Total transmitted high priority multicast data cells: 2630 Total received correctable errored cells: 0 Total received uncorrectable errored cells: 0 Total received parity error cells: 0 Total received stomp cells: 0 Total received kill cells: 0 Total received unknown cells: 0 Total transmitted bogus cells: 4 Total transmitted statically routed control cells: 0 Total transmitted stomp cells: 0 Total transmitted kill cells: 0 Total transmitted ECI cells: 0 Total transmitted LCE cells: 0 Total unicast lost cells: 0 Total multicast lost cells: 0 Total ctb enqueue to off queue cells: 0 Total non-ctb enqueue to off queue cells: 0 Total incoming header error cells: 0 Total incoming data error cells: 0 Total outgoing header error cells: 0 Total outgoing data error cells: 0 Total scs ce error cells: 0 Total scs uce error cells: 0 Last clearing of "show controller fabric plane" counters 00:06:22

• To avoid traffic loss, you must downgrade the switch fabric one plane at a time. To do that, you must replace each FC-140G/S card with an FC/S card and restore service to that fabric plane before downgrading the next fabric plane.

• You might want to perform the downgrade during a network maintenance window or when system traffic is light.

Note Be sure to review the downgrade procedures before deciding when to schedule the downgrade. That way, you can familiarize yourself with the downgrade procedure and determine if there are other issues to consider before performing the downgrade.

• We recommend against moving a chassis after it is cabled. Before the fabric cables are installed, the chassis should be fully installed with power supplies, console cables, grounded, and so forth


OL-13669-03



Administratively Disabling the Fabric PlanePlease note that these steps are to be performed for each Cisco Crs-3 Fabric Card one at a time. When one Fabric Node has completed the downgrade process we should come back to this step for the next Fabric Node, until all 8 Fabrics have been downgraded.

As a first step in the downgrade process, we administratively shutdown the fabric plane that is to be downgraded. This takes the fabric out of traffic operation, the router now continues to forward traffic on the remaining 7 planes – there should not be any traffic drop.

RP/0/RP0/CPU0:router#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#controller fabric plane 0 shutRP/0/RP0/CPU0:router(admin-config)#commit

Verify that fabric plane is now Admin-state Down.

RP/0/RP0/CPU0:router(admin)#show controllers fabric plane allPlane Admin Oper up->dn up->mcast Id State State counter counter --------------------------------------------- 0 DOWN DOWN 1 0 1 UP UP 0 0 2 UP UP 0 0 3 UP UP 0 0 4 UP UP 0 0 5 UP UP 0 0 6 UP UP 0 0 7 UP UP 0 0

Power Disable the Cisco CRS-3 Fabric CardNext, we disable power to the Fabric node, and verify that node is moved to “UNPOWERED” state.


RP/0/RP0/CPU0:router(admin)#show platform Node Type PLIM State Config State<snip>0/SM0/SP FC-140G/S N/A UNPOWERED PWR,NSHUT,MON0/SM1/SP FC-140G/S N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC-140G/S N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC-140G/S N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC-140G/S N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC-140G/S N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC-140G/S N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC-140G/S N/A IOS XR RUN PWR,NSHUT,MON<snip>


OL-13669-03



Swap the Cisco CRS-3 Fabric with the Newly Installed Cisco CRS-1 FabricNow, physically remove the powered down Fabric node from slot 0/SM0 and replace it with the CRS-1 Fabric.

Physically Removing the Cisco CRS-3 Fabric CardThis section describes how to physically remove the Cisco CRS-3 fabric card, and verify that node is ready to have a Cisco CRS-1 fabric card installed in its place. In the following sections, the term “switch fabric card (SFC)” is used to refer to the Cisco CRS-3 fabric card and/or the Cisco CRS-1 fabric card,

This section describes how to remove a CRS-3 fabric card from the Cisco CRS Fabric Card Chassis. For more detailed information on the switch fabric card chassis, see Cisco CRS Carrier Routing System 16-Slot Line Card Chassis System Description.





OL-13669-03



Figure 2-1 CRS-3 Switch Fabric Card

Prerequisites


2496

55


OL-13669-03








Steps




2 Ejector lever

STATU

SP

ID/V

IDC

RS

-FC

C-S

FC

CL

EI

SN

:

1298

70

1

3

2


OL-13669-03












Step 8 Place the card directly into an antistatic sack or other ESD-preventive container. If you plan to return a defective CRS-3 fabric card to the factory, repackage it in a Cisco CRS-3 fabric card shipping container.

What to Do Next


For complete information on regulatory compliance and safety, see Regulatory Compliance and Safety Information for the Cisco CRS Carrier Routing System. For information on installing an CRS-1 fabric card, see the “Installing a CRS-1 Fabric Card” section on page 2-9.

Installing a CRS-1 Fabric CardThis section describes how to install a CRS-1 fabric card in the Cisco CRS Fabric Card Chassis. For more detailed information on the CRS-1 fabric card, see Cisco CRS Carrier Routing System Multishelf System Description.



OL-13669-03






Prerequisites








1298

68


OL-13669-03



Steps







2 Ejector lever

STATU

SP

ID/V

IDC

RS

-FC

C-S

FC

CL

EI

SN

:

1298

70

1

3

2


OL-13669-03



Step 3 Remove the impedance carrier or CRS-3 fabric card you are replacing from the designated slot, and set it carefully aside. (See the “Removing an Impedance Carrier” section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide or the “Removing an CRS-3 Fabric Card” section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide.)
















OL-13669-03





What to Do Next



Verifying the Installation of the CRS-1 Fabric CardThis section describes how to verify that the CRS-1 fabric card has been properly installed. Figure 2-5 is an illustration of the CRS-1 fabric card front panel.

Figure 2-5 CRS-1 Fabric Card Front Panel






STATUSP I D / V I D

CRS-FCC-SFC

CLEI

SN:

1298

69


OL-13669-03





• Examine the Cisco CRS Fabric Card Chassis alarm module to see if there are any active alarm conditions. (See the section on the alarm module in Cisco CRS Carrier Routing System 16-Slot Line Chassis System Description.)





Prerequisites




SUMMARY STEPS

1. admin

2. configure


4. commit


OL-13669-03









11. commit


DETAILED STEPS


Step 1 admin




Step 2 configure









Step 5 commit










OL-13669-03



What to Do Next




Example














Step 12 commit









OL-13669-03




RP/0/RP0/CPU0:router(admin)#show platform Node Type PLIM State Config State<snip>0/SM0/SP FC/S(SP) N/A PRESENT PWR,NSHUT,MON0/SM1/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON<snip>

Power-up the Newly Installed Cisco CRS-1 Fabric CardWe now enable power back to the new Fabric Node.




Booting Up the Newly Downgraded Cisco CRS-1 FabricThis section describes the process for booting up the new Cisco CRS-1 fabric.



RP/0/RP0/CPU0:router(admin)#show platform Node Type PLIM State Config State<snip>0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON


OL-13669-03



0/SM2/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON<snip>

Administratively Enabling the Fabric PlaneThis section describes the process for administratively enabling each newly downgradedCisco CRS-1 fabric plane.






Verifying Traffic Statistics on the Newly Downgraded Cisco CRS-1 NodeTo ascertain that traffic is flowing on the downgraded Cisco CRS-1 fabric node please run the following show controllers fabric plane 0 statistics detail command on both the planes that have been downgraded. Run it a few times to ensure that the counters are incrementing. The lost or error counters should not be incrementing.

The same show controllers fabric plane 0 statistics detail command should also be applied on the Cisco CRS-3 nodes that have not yet been downgraded to make sure there is no traffic lost or traffic with errored cells.


Total number of providers for the statistics: 1


OL-13669-03



Total received data cells: 7063 Total received unicast data cells: 4487 Total received low priority unicast data cells: 4487 Total received high priority unicast data cells: 0 Total received multicast data cells: 2576 Total received low priority multicast data cells: 2050 Total received high priority multicast data cells: 526 Total transmitted data cells: 21094 Total transmitted unicast data cells: 4487 Total transmitted low priority unicast data cells: 4487 Total transmitted high priority unicast data cells: 0 Total transmitted multicast data cells: 16607 Total transmitted low priority multicast data cells: 13977 Total transmitted high priority multicast data cells: 2630 Total received correctable errored cells: 0 Total received uncorrectable errored cells: 0 Total received parity error cells: 0 Total received stomp cells: 0 Total received kill cells: 0 Total received unknown cells: 0 Total transmitted bogus cells: 4 Total transmitted statically routed control cells: 0 Total transmitted stomp cells: 0 Total transmitted kill cells: 0 Total transmitted ECI cells: 0 Total transmitted LCE cells: 0 Total unicast lost cells: 0 Total multicast lost cells: 0 Total ctb enqueue to off queue cells: 0 Total non-ctb enqueue to off queue cells: 0 Total incoming header error cells: 0 Total incoming data error cells: 0 Total outgoing header error cells: 0 Total outgoing data error cells: 0 Total scs ce error cells: 0 Total scs uce error cells: 0 Last clearing of "show controller fabric plane" counters 00:06:22







RP/0/RP0/CPU0:router(admin)#show controllers ingressq fabric links loc 0/5/cpu0Ingressq link stateplane-id link-id ADMIN-STATE OPER-STATE AVAIL-STATE UP-COUNT ----------------------------------------------------.0 0 UP UP UP 2 0 8 UP UP UP 2


OL-13669-03



0 16 UP UP UP 2 0 24 UP UP UP 2 1 1 UP UP UP 1 1 9 UP UP UP 1 1 17 UP UP UP 1 1 25 UP UP UP 1 2 2 UP UP UP 1 2 10 UP UP UP 1 2 18 UP UP UP 1 2 26 UP UP UP 1 3 3 UP UP UP 1 3 11 UP UP UP 1 3 19 UP UP UP 1 3 27 UP UP UP 1 4 4 UP UP UP 1 4 12 UP UP UP 1 4 20 UP UP UP 1 4 28 UP UP UP 1 5 5 UP UP UP 1 5 13 UP UP UP 1 5 21 UP UP UP 1 5 29 UP UP UP 1 6 6 UP UP UP 1 6 14 UP UP UP 1 6 22 UP UP UP 1 6 30 UP UP UP 1 7 7 UP UP UP 1 7 15 UP UP UP 1 7 23 UP UP UP 1 7 31 UP UP UP 1


Location: 0/5/CPU0 Asic Instance: 0 Fabric Destination Address: 20 Retry period: 0 sec Link Active bitmap (1=up,0=down): 0xffffffff +------------------------------------------------------------------------+ |Link #|Driver state | FSDB state |Barrier state|Up (Drv Barr)| Errors | +------------------------------------------------------------------------+ | 0 | Up | Up | Up | 2 2 | | | 1 | Up | Up | Up | 2 2 | | | 2 | Up | Up | Up | 2 2 | | | 3 | Up | Up | Up | 2 2 | | | 4 | Up | Up | Up | 1 1 | | | 5 | Up | Up | Up | 1 1 | | | 6 | Up | Up | Up | 1 1 | | | 7 | Up | Up | Up | 1 1 | | | 8 | Up | Up | Up | 1 1 | | | 9 | Up | Up | Up | 1 1 | | | 10 | Up | Up | Up | 1 1 | | | 11 | Up | Up | Up | 1 1 | | | 12 | Up | Up | Up | 1 1 | | | 13 | Up | Up | Up | 1 1 | | | 14 | Up | Up | Up | 1 1 | | | 15 | Up | Up | Up | 1 1 | | | 16 | Up | Up | Up | 1 1 | | | 17 | Up | Up | Up | 1 1 | | | 18 | Up | Up | Up | 1 1 | | | 19 | Up | Up | Up | 1 1 | | | 20 | Up | Up | Up | 1 1 | | | 21 | Up | Up | Up | 1 1 | | | 22 | Up | Up | Up | 1 1 | |


OL-13669-03



| 23 | Up | Up | Up | 1 1 | | | 24 | Up | Up | Up | 1 1 | | | 25 | Up | Up | Up | 1 1 | | | 26 | Up | Up | Up | 1 1 | | | 27 | Up | Up | Up | 1 1 | | | 28 | Up | Up | Up | 1 1 | | | 29 | Up | Up | Up | 1 1 | | | 30 | Up | Up | Up | 1 1 | | | 31 | Up | Up | Up | 1 1 | | +------------------------------------------------------------------------+


Downgrading the Next Legacy NodeNow that plane 0 has been successfully downgraded, we should go back the repeat it for the next plane. Follow steps 3.1.4 Administratively Disable the Fabric Plane. to 3.1.11 Verify Fabric Link Connectivity for the next plane, until all 8 planes in the system are downgraded to CRS-1.


OL-13669-03



Note We should be doing this only one fabric node at a time, and move to the next node only when the previous node has successfully been downgraded and verified.





• Power Disable the Fabric Card, page 2-24



• 4.1.Booting Up the Newly Downgraded Cisco CRS-1 Fabric, page 2-37





Verifying the Fabric Plane StatusFirst, execute the show platform command to verify that all Fabric cards are operational (i.e. IOS-XR RUN) and all Fabric Planes are UP.



RP/0/RP0/CPU0:router(admin)#show controllers fabric plane all<snip> Plane Admin Oper up->dn up->mcast Id State State counter counter --------------------------------------------- 0 UP UP 0 0


OL-13669-03



1 UP UP 0 0 2 UP UP 0 0 3 UP UP 0 0 4 UP UP 0 0 5 UP UP 0 0 6 UP UP 0 0 7 UP UP 0 0




Total number of providers for the statistics: 1 Total received data cells: 7063 Total received unicast data cells: 4487 Total received low priority unicast data cells: 4487 Total received high priority unicast data cells: 0 Total received multicast data cells: 2576 Total received low priority multicast data cells: 2050 Total received high priority multicast data cells: 526 Total transmitted data cells: 21094 Total transmitted unicast data cells: 4487 Total transmitted low priority unicast data cells: 4487 Total transmitted high priority unicast data cells: 0 Total transmitted multicast data cells: 16607 Total transmitted low priority multicast data cells: 13977 Total transmitted high priority multicast data cells: 2630 Total received correctable errored cells: 0 Total received uncorrectable errored cells: 0 Total received parity error cells: 0 Total received stomp cells: 0 Total received kill cells: 0 Total received unknown cells: 0 Total transmitted bogus cells: 4 Total transmitted statically routed control cells: 0 Total transmitted stomp cells: 0 Total transmitted kill cells: 0 Total transmitted ECI cells: 0 Total transmitted LCE cells: 0 Total unicast lost cells: 0 Total multicast lost cells: 0 Total ctb enqueue to off queue cells: 0 Total non-ctb enqueue to off queue cells: 0 Total incoming header error cells: 0 Total incoming data error cells: 0 Total outgoing header error cells: 0 Total outgoing data error cells: 0 Total scs ce error cells: 0 Total scs uce error cells: 0 Last clearing of "show controller fabric plane" counters 00:06:22


OL-13669-03







Administratively Disabling the Fabric PlanePlease note that these steps are to be performed for each Fabric Card one at a time. When one Fabric Node has completed the downgrade process we should come back to this step for the next Fabric Node, until all 8 Fabrics have been downgraded.





Power Disable the Fabric CardNext, we disable power to the Fabric node, and verify that node is moved to “UNPOWERED” state.



OL-13669-03






This section describes how to remove a CRS-3 fabric card from the Cisco CRS Fabric Card Chassis. For more detailed information on the switch fabric card, see Cisco CRS Carrier Routing System Multishelf System Description.





OL-13669-03




Prerequisites


2496

55


OL-13669-03








Steps

To remove the CRS-3 fabric card, see Figure 2-7 and follow these steps:



2 Ejector lever

STATU

SP

ID/V

IDC

RS

-FC

C-S

FC

CL

EI

SN

:

1298

70

1

3

2


OL-13669-03













What to Do Next



For information on installing a CRS-1 fabric card, see the “Installing a CRS-1 Fabric Card” section on page 2-29.


OL-13669-03








Prerequisites




1298

68


OL-13669-03








Steps






2 Ejector lever

STATU

SP

ID/V

IDC

RS

-FC

C-S

FC

CL

EI

SN

:

1298

70

1

3

2


OL-13669-03




Step 3 Remove the impedance carrier or CRS-3 fabric card you are replacing from the designated slot, and set it carefully aside. (See the “Removing an Impedance Carrier” section in the Cisco CRS Carrier Routing System 8-Slot Line Card Chassis Installation Guide or the “Removing a CRS-3 Fabric Card” section in the Cisco CRS Carrier Routing System 8-Slot Line Card Chassis Installation Guide.)














OL-13669-03







What to Do Next



Verifying the Installation of the CRS-1 Fabric CardThis section describes how to verify that the CRS-1 fabric card has been properly installed. Figure 2-5 is an illustration of the CRS-1 fabric card front panel.





STATUSP I D / V I D

CRS-FCC-SFC

CLEI

SN:

1298

69


OL-13669-03







• Examine the Cisco CRS Fabric Card Chassis alarm module to see if there are any active alarm conditions. (See the section on the alarm module in Cisco CRS Carrier Routing System Multishelf System Description.)





Prerequisites




Prerequisites

None.


OL-13669-03



Restrictions

None.

SUMMARY STEPS

1. admin

2. configure


4. commit







11. commit


DETAILED STEPS


Step 1 admin




Step 2 configure









Step 5 commit




OL-13669-03



What to Do Next





















Step 12 commit









OL-13669-03



Example










RP/0/RP0/CPU0:router#admin


OL-13669-03



RP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#no hw-module power disable loc 0/SM0/SPRP/0/RP0/CPU0:router(admin-config)#commit



4.1.Booting Up the Newly Downgraded Cisco CRS-1 FabricThis section describes the process for booting up the new Cisco CRS-1 fabric.



RP/0/RP0/CPU0:router(admin)#show platform Node Type PLIM State Config State<snip>0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON<snip>





OL-13669-03









Total number of providers for the statistics: 1 Total received data cells: 7063 Total received unicast data cells: 4487 Total received low priority unicast data cells: 4487 Total received high priority unicast data cells: 0 Total received multicast data cells: 2576 Total received low priority multicast data cells: 2050 Total received high priority multicast data cells: 526 Total transmitted data cells: 21094 Total transmitted unicast data cells: 4487 Total transmitted low priority unicast data cells: 4487 Total transmitted high priority unicast data cells: 0 Total transmitted multicast data cells: 16607 Total transmitted low priority multicast data cells: 13977 Total transmitted high priority multicast data cells: 2630 Total received correctable errored cells: 0 Total received uncorrectable errored cells: 0 Total received parity error cells: 0 Total received stomp cells: 0 Total received kill cells: 0 Total received unknown cells: 0 Total transmitted bogus cells: 4 Total transmitted statically routed control cells: 0 Total transmitted stomp cells: 0 Total transmitted kill cells: 0 Total transmitted ECI cells: 0 Total transmitted LCE cells: 0


OL-13669-03



Total unicast lost cells: 0 Total multicast lost cells: 0 Total ctb enqueue to off queue cells: 0 Total non-ctb enqueue to off queue cells: 0 Total incoming header error cells: 0 Total incoming data error cells: 0 Total outgoing header error cells: 0 Total outgoing data error cells: 0 Total scs ce error cells: 0 Total scs uce error cells: 0 Last clearing of "show controller fabric plane" counters 00:06:22







RP/0/RP0/CPU0:router(admin)#show controllers ingressq fabric links loc 0/5/cpu0Ingressq link stateplane-id link-id ADMIN-STATE OPER-STATE AVAIL-STATE UP-COUNT ----------------------------------------------------.0 0 UP UP UP 2 0 8 UP UP UP 2 0 16 UP UP UP 2 0 24 UP UP UP 2 1 1 UP UP UP 1 1 9 UP UP UP 1 1 17 UP UP UP 1 1 25 UP UP UP 1 2 2 UP UP UP 1 2 10 UP UP UP 1 2 18 UP UP UP 1 2 26 UP UP UP 1 3 3 UP UP UP 1 3 11 UP UP UP 1 3 19 UP UP UP 1 3 27 UP UP UP 1 4 4 UP UP UP 1 4 12 UP UP UP 1 4 20 UP UP UP 1 4 28 UP UP UP 1 5 5 UP UP UP 1 5 13 UP UP UP 1 5 21 UP UP UP 1 5 29 UP UP UP 1 6 6 UP UP UP 1 6 14 UP UP UP 1 6 22 UP UP UP 1 6 30 UP UP UP 1


OL-13669-03



7 7 UP UP UP 1 7 15 UP UP UP 1 7 23 UP UP UP 1 7 31 UP UP UP 1



Location: 0/5/CPU0 Asic Instance: 1 Fabric Destination Address: 21 Retry period: 0 sec Link Active bitmap (1=up,0=down): 0xffffffff +------------------------------------------------------------------------+ |Link #|Driver state | FSDB state |Barrier state|Up (Drv Barr)| Errors | +------------------------------------------------------------------------+ | 0 | Up | Up | Up | 2 2 | | | 1 | Up | Up | Up | 2 2 | | | 2 | Up | Up | Up | 2 2 | | | 3 | Up | Up | Up | 2 2 | | | 4 | Up | Up | Up | 1 1 | | | 5 | Up | Up | Up | 1 1 | | | 6 | Up | Up | Up | 1 1 | |


OL-13669-03



| 7 | Up | Up | Up | 1 1 | | | 8 | Up | Up | Up | 1 1 | | | 9 | Up | Up | Up | 1 1 | | | 10 | Up | Up | Up | 1 1 | | | 11 | Up | Up | Up | 1 1 | | | 12 | Up | Up | Up | 1 1 | | | 13 | Up | Up | Up | 1 1 | | | 14 | Up | Up | Up | 1 1 | | | 15 | Up | Up | Up | 1 1 | | | 16 | Up | Up | Up | 1 1 | | | 17 | Up | Up | Up | 1 1 | | | 18 | Up | Up | Up | 1 1 | | | 19 | Up | Up | Up | 1 1 | | | 20 | Up | Up | Up | 1 1 | | | 21 | Up | Up | Up | 1 1 | | | 22 | Up | Up | Up | 1 1 | | | 23 | Up | Up | Up | 1 1 | | | 24 | Up | Up | Up | 1 1 | | | 25 | Up | Up | Up | 1 1 | | | 26 | Up | Up | Up | 1 1 | | | 27 | Up | Up | Up | 1 1 | | | 28 | Up | Up | Up | 1 1 | | | 29 | Up | Up | Up | 1 1 | | | 30 | Up | Up | Up | 1 1 | | | 31 | Up | Up | Up | 1 1 | | +------------------------------------------------------------------------+

Downgrading the Next Legacy NodeNow that plane 0 has been successfully downgraded, we should go back the repeat it for the next plane. Follow steps 3.1.4 Administratively Disable the Fabric Plane. to 3.1.11 Verify Fabric Link Connectivity for the next plane, until all 8 planes in the system are downgraded to CRS-1.






• Power Disable the Fabric Card, page 2-44



• Booting Up the Newly Downgraded Cisco CRS-1 Fabric, page 2-57


OL-13669-03







Verifying the Fabric Plane StatusFirst, execute the show platform command to verify that all Fabric cards are operational (i.e. IOS-XR RUN) and all Fabric Planes are UP.







Total number of providers for the statistics: 1 Total received data cells: 7063 Total received unicast data cells: 4487 Total received low priority unicast data cells: 4487 Total received high priority unicast data cells: 0


OL-13669-03



Total received multicast data cells: 2576 Total received low priority multicast data cells: 2050 Total received high priority multicast data cells: 526 Total transmitted data cells: 21094 Total transmitted unicast data cells: 4487 Total transmitted low priority unicast data cells: 4487 Total transmitted high priority unicast data cells: 0 Total transmitted multicast data cells: 16607 Total transmitted low priority multicast data cells: 13977 Total transmitted high priority multicast data cells: 2630 Total received correctable errored cells: 0 Total received uncorrectable errored cells: 0 Total received parity error cells: 0 Total received stomp cells: 0 Total received kill cells: 0 Total received unknown cells: 0 Total transmitted bogus cells: 4 Total transmitted statically routed control cells: 0 Total transmitted stomp cells: 0 Total transmitted kill cells: 0 Total transmitted ECI cells: 0 Total transmitted LCE cells: 0 Total unicast lost cells: 0 Total multicast lost cells: 0 Total ctb enqueue to off queue cells: 0 Total non-ctb enqueue to off queue cells: 0 Total incoming header error cells: 0 Total incoming data error cells: 0 Total outgoing header error cells: 0 Total outgoing data error cells: 0 Total scs ce error cells: 0 Total scs uce error cells: 0 Last clearing of "show controller fabric plane" counters 00:06:22





Administratively Disabling the Fabric PlanePlease note that these steps are to be performed for each Fabric Card one at a time. When one Fabric Node has completed the downgrade process we should come back to this step for the next Fabric Node, until all 8 Fabrics have been downgraded.



OL-13669-03






Power Disable the Fabric CardNext, we disable power to the Fabric node, and verify that node is moved to “UNPOWERED” state.






OL-13669-03



This section describes how to remove a CRS-3 fabric card from the Cisco CRS Fabric Card Chassis. For more detailed information on the CRS-3 fabric card, see Cisco CRS Carrier Routing System 4-Slot Line Card Chassis System Description.





OL-13669-03




Prerequisites


2496

55


OL-13669-03








Steps




2 Ejector lever

STATU

SP

ID/V

IDC

RS

-FC

C-S

FC

CL

EI

SN

:

1298

70

1

3

2


OL-13669-03













What to Do Next


For information on removing the front cosmetic cover plates, see the “Removing the Rear (OIM) Side Cosmetic Components” section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide. For information on how to power down your chassis, see the “Powering an AC Power Shelf Energized Chassis Up and Down” section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide or the “Powering a DC Power Shelf Energized Chassis Up and Down” section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide. For information on installing an OIM, see the “Installing an OIM” section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide.



OL-13669-03








Prerequisites




1298

68


OL-13669-03








Steps






2 Ejector lever

STATU

SP

ID/V

IDC

RS

-FC

C-S

FC

CL

EI

SN

:

1298

70

1

3

2


OL-13669-03




Step 3 Remove the impedance carrier or CRS-3 fabric card you are replacing from the designated slot, and set it carefully aside. (See the “Removing an Impedance Carrier” section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide or the “Removing an SFC” section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide.)














OL-13669-03







What to Do Next



Verifying the Installation of the CRS-1 Fabric CardThis section describes how to verify that a CRS-1 fabric card has been properly installed. Figure 2-15 is an illustration of the CRS-1 fabric card front panel.




STATUSP I D / V I D

CRS-FCC-SFC

CLEI

SN:

1298

69


OL-13669-03













Prerequisites





OL-13669-03



Prerequisites

None.

Restrictions

None.

SUMMARY STEPS

1. admin

2. configure


4. commit







11. commit


DETAILED STEPS


Step 1 admin




Step 2 configure










OL-13669-03



What to Do Next


Step 5 commit




















Step 12 commit









OL-13669-03





Example










OL-13669-03







Booting Up the Newly Downgraded Cisco CRS-1 FabricThis section describes the process for booting up the new Cisco CRS-1 fabric.



RP/0/RP0/CPU0:router(admin)#show platform Node Type PLIM State Config State<snip>0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON<snip>



RP/0/RP0/CPU0:router#adminRP/0/RP0/CPU0:router(admin)#config


OL-13669-03



RP/0/RP0/CPU0:router(admin-config)#no controller fabric plane 0 shutRP/0/RP0/CPU0:router(admin-config)#no controller fabric plane 1 shutRP/0/RP0/CPU0:router(admin-config)#commit







Total number of providers for the statistics: 1 Total received data cells: 7063 Total received unicast data cells: 4487 Total received low priority unicast data cells: 4487 Total received high priority unicast data cells: 0 Total received multicast data cells: 2576 Total received low priority multicast data cells: 2050 Total received high priority multicast data cells: 526 Total transmitted data cells: 21094 Total transmitted unicast data cells: 4487 Total transmitted low priority unicast data cells: 4487 Total transmitted high priority unicast data cells: 0 Total transmitted multicast data cells: 16607 Total transmitted low priority multicast data cells: 13977 Total transmitted high priority multicast data cells: 2630 Total received correctable errored cells: 0 Total received uncorrectable errored cells: 0 Total received parity error cells: 0 Total received stomp cells: 0 Total received kill cells: 0 Total received unknown cells: 0 Total transmitted bogus cells: 4


OL-13669-03



Total transmitted statically routed control cells: 0 Total transmitted stomp cells: 0 Total transmitted kill cells: 0 Total transmitted ECI cells: 0 Total transmitted LCE cells: 0 Total unicast lost cells: 0 Total multicast lost cells: 0 Total ctb enqueue to off queue cells: 0 Total non-ctb enqueue to off queue cells: 0 Total incoming header error cells: 0 Total incoming data error cells: 0 Total outgoing header error cells: 0 Total outgoing data error cells: 0 Total scs ce error cells: 0 Total scs uce error cells: 0 Last clearing of "show controller fabric plane" counters 00:06:22







RP/0/RP0/CPU0:router(admin)#show controllers ingressq fabric links loc 0/5/cpu0Ingressq link stateplane-id link-id ADMIN-STATE OPER-STATE AVAIL-STATE UP-COUNT ----------------------------------------------------.0 0 UP UP UP 2 0 8 UP UP UP 2 0 16 UP UP UP 2 0 24 UP UP UP 2 1 1 UP UP UP 1 1 9 UP UP UP 1 1 17 UP UP UP 1 1 25 UP UP UP 1 2 2 UP UP UP 1 2 10 UP UP UP 1 2 18 UP UP UP 1 2 26 UP UP UP 1 3 3 UP UP UP 1 3 11 UP UP UP 1 3 19 UP UP UP 1 3 27 UP UP UP 1 4 4 UP UP UP 1 4 12 UP UP UP 1 4 20 UP UP UP 1 4 28 UP UP UP 1 5 5 UP UP UP 1 5 13 UP UP UP 1 5 21 UP UP UP 1


OL-13669-03



5 29 UP UP UP 1 6 6 UP UP UP 1 6 14 UP UP UP 1 6 22 UP UP UP 1 6 30 UP UP UP 1 7 7 UP UP UP 1 7 15 UP UP UP 1 7 23 UP UP UP 1 7 31 UP UP UP 1



Location: 0/5/CPU0 Asic Instance: 1 Fabric Destination Address: 21 Retry period: 0 sec Link Active bitmap (1=up,0=down): 0xffffffff +------------------------------------------------------------------------+ |Link #|Driver state | FSDB state |Barrier state|Up (Drv Barr)| Errors | +------------------------------------------------------------------------+ | 0 | Up | Up | Up | 2 2 | | | 1 | Up | Up | Up | 2 2 | |


OL-13669-03



| 2 | Up | Up | Up | 2 2 | | | 3 | Up | Up | Up | 2 2 | | | 4 | Up | Up | Up | 1 1 | | | 5 | Up | Up | Up | 1 1 | | | 6 | Up | Up | Up | 1 1 | | | 7 | Up | Up | Up | 1 1 | | | 8 | Up | Up | Up | 1 1 | | | 9 | Up | Up | Up | 1 1 | | | 10 | Up | Up | Up | 1 1 | | | 11 | Up | Up | Up | 1 1 | | | 12 | Up | Up | Up | 1 1 | | | 13 | Up | Up | Up | 1 1 | | | 14 | Up | Up | Up | 1 1 | | | 15 | Up | Up | Up | 1 1 | | | 16 | Up | Up | Up | 1 1 | | | 17 | Up | Up | Up | 1 1 | | | 18 | Up | Up | Up | 1 1 | | | 19 | Up | Up | Up | 1 1 | | | 20 | Up | Up | Up | 1 1 | | | 21 | Up | Up | Up | 1 1 | | | 22 | Up | Up | Up | 1 1 | | | 23 | Up | Up | Up | 1 1 | | | 24 | Up | Up | Up | 1 1 | | | 25 | Up | Up | Up | 1 1 | | | 26 | Up | Up | Up | 1 1 | | | 27 | Up | Up | Up | 1 1 | | | 28 | Up | Up | Up | 1 1 | | | 29 | Up | Up | Up | 1 1 | | | 30 | Up | Up | Up | 1 1 | | | 31 | Up | Up | Up | 1 1 | | +------------------------------------------------------------------------+

Downgrading the Next Legacy NodeNow that plane 0 has been successfully downgraded, we should go back the repeat it for the next plane. Administratively Disable the Fabric Plane. to Verify Fabric Link Connectivity for the next plane, until all 8 planes in the system are downgraded to CRS-1.



OL-13669-03




OL-13669-03


C H A P T E R 3
Cisco CRS-3 Carrier Routing System Router Command Changes
This chapter describes new commands and commands that have changed to support the Cisco CRS-3 Carrier Routing System.

It includes the following sections:

• New Commands, page 3-2

– show controllers egressq clients, page 3-3

– show controllers egressq queue drr, page 3-5

– show controllers egressq group drr, page 3-11

– show controllers egressq group ntb, page 3-17

– show controllers egressq port bpmap, page 3-20

– show controllers egressq statistics, page 3-22

– show controllers egressq statistics detail, page 3-24

• Modified Commands, page 3-27

– show controllers egressq resources, page 3-28

– show controllers (Ethernet), page 3-29

– show controllers TenGigE, page 3-72

– QoS Command Changes, page 3-74

– QoS Features Changes, page 3-76


Chapter 3 Cisco CRS-3 Carrier Routing System Router Command Changes

New Commands

New CommandsThe following new commands have been added to support the Cisco CRS-3 Carrier Routing System:

• show controllers egressq clients, page 3-3

• show controllers egressq queue drr, page 3-5

• show controllers egressq group drr, page 3-11

• show controllers egressq group ntb, page 3-17

• show controllers egressq port bpmap, page 3-20

• show controllers egressq statistics, page 3-22

• show controllers egressq statistics detail, page 3-24


OL-13669-03


show controllers egressq clients

show controllers egressq clients To display the list of clients connected to the egress queue manager, use the show controllers egressq clients command in EXEC mode..

show controllers egressq clients location node-id

Syntax Description

Command Default No default behavior or values.

Command Modes EXEC

Command History

Usage Guidelines To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.

Task ID

Examples The following example shows how to use the show controllers egressq clients command:

RP/0/RP0/CPU0:router# show controllers egressq clients location 0/6/cpu0Mon Sep 27 00:35:08.433 DST

--------------------------------------------------------------- Egressq Clients--------------------------------------------------------------- Name PID State registers Last-State-Changed--------------------------------------------------------------- QOS_EA 131187 OPEN 1 Tue Sep 14 23:24:45 2010

hfr_pm 98389 OPEN 1 Tue Sep 14 23:24:18 2010

feature_mgr 98408 OPEN 1 Tue Sep 14 23:24:16 2010

Table 1 describes the significant fields shown in the display.

location node-id The egress queue manager location. The node-id argument is entered in the rack/slot/module notation.


Release 4.0.0.T This command was introduced.

Release 4.0.1 No modification.


Task ID Operations

drivers read


OL-13669-03


show controllers egressq clients

Table 1 show controllers egressq clients Field Descriptions

Field Description

Name Name of the client.

PID Packet Identifier.

State State of the egress client’s connection to the egress queue server; two states are available, OPEN and CLOSE.

Registers The number of times, the egress client tried to register with the egressq server.

Last-state-changed Timestamp for the last connection state change.


OL-13669-03


show controllers egressq queue drr

show controllers egressq queue drrTo display queue information of the Deficit Round Robin (DRR) profile table, use the show controllers egressq queue drr command in EXEC mode.

show controllers egressq queue drr {min | max} location node-id

Syntax Description

Defaults No default behavior or values.

Command Modes EXEC

Command History


Task ID

Examples The following example shows how to use the show controllers egressq queue drr command:

RP/0/RP0/CPU0:router# show controllers egressq queue drr max location 0/6/cpu0

Queue Max DRR Profile Table ----------------------------------Index | Value (bytes) 0 | 0 1 | 88 2 | 176 3 | 264 4 | 352 5 | 440 6 | 528 7 | 616

max Maximum limit of the DRR profile table.

min Minimum limit of the DRR profile table.

location node-id Egress queue manager location.The node-id argument is entered in the rack/slot/module notation.





Task ID Operations

drivers read


OL-13669-03



8 | 704 9 | 792 10 | 880 11 | 968 12 | 1056 13 | 1144 14 | 1232 15 | 1320 16 | 1408 17 | 1496 18 | 1584 19 | 1672 20 | 1760 21 | 1848 22 | 1936 23 | 2024 24 | 2112 25 | 2200 26 | 2288 27 | 2376 28 | 2464 29 | 2552 30 | 2640 31 | 2728 32 | 2816 33 | 2904 34 | 2992 35 | 3080 36 | 3168 37 | 3256 38 | 3344 39 | 3432 40 | 3520 41 | 3608 42 | 3696 43 | 3784 44 | 3872 45 | 3960 46 | 4048 47 | 4136 48 | 4224 49 | 4312 50 | 4400 51 | 4488 52 | 4576 53 | 4664 54 | 4752 55 | 4840 56 | 4928 57 | 5016 58 | 5104 59 | 5192 60 | 5280 61 | 5368 62 | 5456 63 | 5544 64 | 5632 65 | 5720 66 | 5808 67 | 5896 68 | 5984 69 | 6072 70 | 6160 71 | 6248


OL-13669-03



72 | 6336 73 | 6424 74 | 6512 75 | 6600 76 | 6688 77 | 6776 78 | 6864 79 | 6952 80 | 7040 81 | 7128 82 | 7216 83 | 7304 84 | 7392 85 | 7480 86 | 7568 87 | 7656 88 | 7744 89 | 7832 90 | 7920 91 | 8008 92 | 8096 93 | 8184 94 | 8272 95 | 8360 96 | 8448 97 | 8536 98 | 8624 99 | 8712 100 | 8800 101 | 8888 102 | 8976 103 | 9064 104 | 9152 105 | 9240 106 | 9328 107 | 9416 108 | 9504 109 | 9592 110 | 9680 111 | 9768 112 | 9856 113 | 9944 114 | 10032 115 | 10120 116 | 10208 117 | 10296 118 | 10384 119 | 10472 120 | 10560 121 | 10648 122 | 10736 123 | 10824 124 | 10912 125 | 11000 126 | 11088 127 | 11176 128 | 11264 129 | 11352 130 | 11440 131 | 11528 132 | 11616 133 | 11704 134 | 11792 135 | 11880


OL-13669-03



136 | 11968 137 | 12056 138 | 12144 139 | 12232 140 | 12320 141 | 12408 142 | 12496 143 | 12584 144 | 12672 145 | 12760 146 | 12848 147 | 12936 148 | 13024 149 | 13112 150 | 13200 151 | 13288 152 | 13376 153 | 13464 154 | 13552 155 | 13640 156 | 13728 157 | 13816 158 | 13904 159 | 13992 160 | 14080 161 | 14168 162 | 14256 163 | 14344 164 | 14432 165 | 14520 166 | 14608 167 | 14696 168 | 14784 169 | 14872 170 | 14960 171 | 15048 172 | 15136 173 | 15224 174 | 15312 175 | 15400 176 | 15488 177 | 15576 178 | 15664 179 | 15752 180 | 15840 181 | 15928 182 | 16016 183 | 16104 184 | 16192 185 | 16280 186 | 16368 187 | 16456 188 | 16544 189 | 16632 190 | 16720 191 | 16808 192 | 16896 193 | 16984 194 | 17072 195 | 17160 196 | 17248 197 | 17336 198 | 17424 199 | 17512


OL-13669-03



200 | 17600 201 | 17688 202 | 17776 203 | 17864 204 | 17952 205 | 18040 206 | 18128 207 | 18216 208 | 18304 209 | 18392 210 | 18480 211 | 18568 212 | 18656 213 | 18744 214 | 18832 215 | 18920 216 | 19008 217 | 19096 218 | 19184 219 | 19272 220 | 19360 221 | 19448 222 | 19536 223 | 19624 224 | 19712 225 | 19800 226 | 19888 227 | 19976 228 | 20064 229 | 20152 230 | 20240 231 | 20328 232 | 20416 233 | 20504 234 | 20592 235 | 20680 236 | 20768 237 | 20856 238 | 20944 239 | 21032 240 | 21120 241 | 21208 242 | 21296 243 | 21384 244 | 21472 245 | 21560 246 | 21648 247 | 21736 248 | 21824 249 | 21912 250 | 22000 251 | 22088 252 | 22176 253 | 22264 254 | 22352 255 | 22440



OL-13669-03



Related Commands

Table 2 show controllers egressq queue drr Field Descriptions

Field Description

index Entry index value. The table has 256 entries.

value The corresponding table value for the entry. The granularity of the value is in blocks of 512 bytes.

Command Description

show controllers egressq group drr

Displays group information of the Deficit Round Robin (DRR) profile table.


OL-13669-03



show controllers egressq group drrTo display group information of the Deficit Round Robin (DRR) profile table, use the show controllers egressq group drr command in EXEC mode.

show controllers egressq group drr {min | max} location node-id

Syntax Description


Command Modes EXEC

Command History


Task ID

Examples The following example shows how to use the show controllers egressq group drr command:

RP/0/RP0/CPU0:router# show controllers egressq group drr max location 0/6/cpu0

Queue Max DRR Profile Table ----------------------------------Index | Value (bytes) 0 | 0 1 | 88 2 | 176 3 | 264 4 | 352 5 | 440 6 | 528 7 | 616








Task ID Operations

drivers read


OL-13669-03



8 | 704 9 | 792 10 | 880 11 | 968 12 | 1056 13 | 1144 14 | 1232 15 | 1320 16 | 1408 17 | 1496 18 | 1584 19 | 1672 20 | 1760 21 | 1848 22 | 1936 23 | 2024 24 | 2112 25 | 2200 26 | 2288 27 | 2376 28 | 2464 29 | 2552 30 | 2640 31 | 2728 32 | 2816 33 | 2904 34 | 2992 35 | 3080 36 | 3168 37 | 3256 38 | 3344 39 | 3432 40 | 3520 41 | 3608 42 | 3696 43 | 3784 44 | 3872 45 | 3960 46 | 4048 47 | 4136 48 | 4224 49 | 4312 50 | 4400 51 | 4488 52 | 4576 53 | 4664 54 | 4752 55 | 4840 56 | 4928 57 | 5016 58 | 5104 59 | 5192 60 | 5280 61 | 5368 62 | 5456 63 | 5544 64 | 5632 65 | 5720 66 | 5808 67 | 5896 68 | 5984 69 | 6072 70 | 6160 71 | 6248


OL-13669-03



72 | 6336 73 | 6424 74 | 6512 75 | 6600 76 | 6688 77 | 6776 78 | 6864 79 | 6952 80 | 7040 81 | 7128 82 | 7216 83 | 7304 84 | 7392 85 | 7480 86 | 7568 87 | 7656 88 | 7744 89 | 7832 90 | 7920 91 | 8008 92 | 8096 93 | 8184 94 | 8272 95 | 8360 96 | 8448 97 | 8536 98 | 8624 99 | 8712 100 | 8800 101 | 8888 102 | 8976 103 | 9064 104 | 9152 105 | 9240 106 | 9328 107 | 9416 108 | 9504 109 | 9592 110 | 9680 111 | 9768 112 | 9856 113 | 9944 114 | 10032 115 | 10120 116 | 10208 117 | 10296 118 | 10384 119 | 10472 120 | 10560 121 | 10648 122 | 10736 123 | 10824 124 | 10912 125 | 11000 126 | 11088 127 | 11176 128 | 11264 129 | 11352 130 | 11440 131 | 11528 132 | 11616 133 | 11704 134 | 11792 135 | 11880


OL-13669-03



136 | 11968 137 | 12056 138 | 12144 139 | 12232 140 | 12320 141 | 12408 142 | 12496 143 | 12584 144 | 12672 145 | 12760 146 | 12848 147 | 12936 148 | 13024 149 | 13112 150 | 13200 151 | 13288 152 | 13376 153 | 13464 154 | 13552 155 | 13640 156 | 13728 157 | 13816 158 | 13904 159 | 13992 160 | 14080 161 | 14168 162 | 14256 163 | 14344 164 | 14432 165 | 14520 166 | 14608 167 | 14696 168 | 14784 169 | 14872 170 | 14960 171 | 15048 172 | 15136 173 | 15224 174 | 15312 175 | 15400 176 | 15488 177 | 15576 178 | 15664 179 | 15752 180 | 15840 181 | 15928 182 | 16016 183 | 16104 184 | 16192 185 | 16280 186 | 16368 187 | 16456 188 | 16544 189 | 16632 190 | 16720 191 | 16808 192 | 16896 193 | 16984 194 | 17072 195 | 17160 196 | 17248 197 | 17336 198 | 17424 199 | 17512


OL-13669-03



200 | 17600 201 | 17688 202 | 17776 203 | 17864 204 | 17952 205 | 18040 206 | 18128 207 | 18216 208 | 18304 209 | 18392 210 | 18480 211 | 18568 212 | 18656 213 | 18744 214 | 18832 215 | 18920 216 | 19008 217 | 19096 218 | 19184 219 | 19272 220 | 19360 221 | 19448 222 | 19536 223 | 19624 224 | 19712 225 | 19800 226 | 19888 227 | 19976 228 | 20064 229 | 20152 230 | 20240 231 | 20328 232 | 20416 233 | 20504 234 | 20592 235 | 20680 236 | 20768 237 | 20856 238 | 20944 239 | 21032 240 | 21120 241 | 21208 242 | 21296 243 | 21384 244 | 21472 245 | 21560 246 | 21648 247 | 21736 248 | 21824 249 | 21912 250 | 22000 251 | 22088 252 | 22176 253 | 22264 254 | 22352 255 | 22440



OL-13669-03



Related Commands

Table 3 show controllers egressq group drr Field Descriptions

Field Description


value The corresponding table value for the entry. The granularity of the value is in blocks of 512 bytes.

Command Description


Displays queue information of the Deficit Round Robin (DRR) profile table.


OL-13669-03


show controllers egressq group ntb

show controllers egressq group ntbTo display the negative token bucket (NTB) limit table information of the egress queue manager, use the show controllers egressq group ntb command in EXEC mode.

show controllers egressq group ntb {min | max} location node-id

Syntax Description


Command Modes EXEC

Command History


Task ID

Examples The following example shows how to use the show controllers egressq group ntb command:

RP/0/RP0/CPU0:router# show controllers egressq group ntb max location 0/6/cpu0

Group Max Negative TB Limit Table ----------------------------------Index | Value (bytes)

0 | 76800 1 | 153600 2 | 230400 3 | 307200 4 | 384000 5 | 460800 6 | 537600








Task ID Operations

drivers read


OL-13669-03



7 | 614400 8 | 691200 9 | 768000 10 | 844800 11 | 921600 12 | 998400 13 | 1075200 14 | 1152000 15 | 1228800 16 | 1305600 17 | 1382400 18 | 1459200 19 | 1536000 20 | 1612800 21 | 1689600 22 | 1766400 23 | 1843200 24 | 1920000 25 | 1996800 26 | 2073600 27 | 2150400 28 | 2227200 29 | 2304000 30 | 2380800 31 | 2457600 32 | 2534400 33 | 2611200 34 | 2688000 35 | 2764800 36 | 2841600 37 | 2918400 38 | 2995200 39 | 3072000 40 | 3148800 41 | 3225600 42 | 3302400 43 | 3379200 44 | 3456000 45 | 3532800 46 | 3609600 47 | 3686400 48 | 3763200 49 | 3840000 50 | 3916800 51 | 3993600 52 | 5110498 53 | 6878158 54 | 9257231 55 | 12459196 56 | 16768682 57 | 22568767 58 | 30375032 59 | 40881391 60 | 55021772 61 | 74053141 62 | 99667231 63 | 134140926



OL-13669-03



Related Commands

Table 4 show controllers egressq group ntb Field Descriptions

Field Description


value The corresponding table value for the entry.

Command Description


Displays queue information of the Deficit Round Robin (DRR) profile table.


Displays group information of the Deficit Round Robin (DRR) profile table.


OL-13669-03


show controllers egressq port bpmap

show controllers egressq port bpmapTo display back pressure map table information of the egress queue manager, use the show controllers egressq port bpmap command in EXEC mode.

show controllers egressq port bpmap location node-id

Syntax Description


Command Modes EXEC

Command History


Task ID

Examples The following example shows how to use the show controller egressq bpmap command:

RP/0/RP0/CPU0:router# show controller egressq port bpmap location 0/3/cpu0

--------------------------------------------------- Tor Asic HW BP Map Table Dump ---------------------------------------------------Index Plim 0 Map Plim 1 Map ---------------------------------------------------

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






Task ID Operations

drivers read


OL-13669-03


show controllers egressq port bpmap

8 65535 12 9 6 13 10 125 126


OL-13669-03


show controllers egressq statistics

show controllers egressq statisticsTo display the egressq statistics for a specific location in the egress queue manager, use the show controllers egressq statistics command in EXEC mode.

show controllers egressq statistics location node-id

Syntax Description


Command Modes EXEC

Command History


Task ID

Examples The following example shows how to use the show controller egressq statistics command:

RP/0/RP0/CPU0:router# show controller egressq statistics location 0/3/cpu0

Egressq Statistics--------------------------------------------------egressq ASIC version: 2egressq ASIC state: Normalplimasic link0 output packets: 34650plimasic link0 output bytes: 6500662plimasic link1 output packets: 0plimasic link1 output bytes: 0cpuctrl input packets: 25750cpuctrl output packets: 1609269cpuctrl output bytes: 3221287392pse input packets: 1618173egressq OOB drops: 0






Task ID Operations

drivers read


OL-13669-03



cpuctrl dropped packets: 0pse dropped packets: 0


Related Commands

Table 5 show controllers egressq statistics Field Descriptions

Field Description

egressq ASIC version Egress queue ASIC revision number.

egressq ASIC state Egress queue ASIC operating state.

The operating states are:

• Normal for normal operating state

• Interrupt pending for pending interrupts

• Halt for states wherein the ASIC is halted

• Unknown for unexpected errors

plimasic link output packets Output packet count for a link connected to a PLIMasic.

plimasic link output bytes Output byte count for a link connected to a PLIM asic.

cpuctrl input packets Input packet count from the CPU of the linecards.

cpuctrl output bytes Output byte count to the CPU of the linecards.

pse input packets Input packet count from the upstream Packet Switching Engine (PSE) ASIC.

egressq OOB drops Out of buffer (OOB) packet drop count.

cpuctrl dropped packets Count of packets dropped from the CPU of the linecards.

pse dropped packets Count of packets dropped at the interface between the egress queue ASIC and the PSE ASIC.

Command Description

show controllers egressq statistics detail

Displays detailed egressq statistics for a specific location.


OL-13669-03



show controllers egressq statistics detailTo display detailed egressq statistics for a specific location in the egress queue manager, use the show controllers egressq statistics detail command in EXEC mode.

show controllers egressq statistics detail location node-id

Syntax Description


Command Modes EXEC

Command History


Task ID

Examples The following example shows how to use the show controller egressq statistics detail command:

RP/0/RP0/CPU0:router# show controller egressq statistics detail location 0/3/cpu0

Egressq Statistics--------------------------------------------------egressq ASIC version: 2egressq ASIC state: Normalplimasic link0 output packets: 34716plimasic link0 output bytes: 6513008plimasic link1 output packets: 0plimasic link1 output bytes: 0cpuctrl input packets: 25799cpuctrl output packets: 1612375cpuctrl output bytes: 3227504848pse input packets: 1621296egressq OOB drops: 0






Task ID Operations

drivers read


OL-13669-03



cpuctrl dropped packets: 0pse dropped packets: 0

hpi drop cpu pkts: 0hpi drop cpu bytes: 0enq drop cpu pkts enq err: 0enq drop cpu pkts len err: 0enq drop cpu pkts int err: 0enq drop cpu pkts OOR: 0enq discard cpu pkts: 0enq drain cpu pkts: 0enq drop epogo pkts enq err: 0enq drop epogo pkts len err: 0enq drop epogo pkts OOR: 0enq drop epogo pkts int err: 0enq discard epogo pkts: 0enq drain epogo pkts: 0qmgr drain pkts: 0


Table 6 show controllers egressq statistics detail Field Descriptions

Field Description

egressq ASIC version Egress queue ASIC revision number.

egressq ASIC state Egress queue ASIC operating state.

The operating states are:

• Normal for normal operating state

• Interrupt pending for pending interrupts

• Halt for states wherein the ASIC is halted

• Unknown for unexpected errors

plimasic link output packets Output packet count for a link connected to a PLIMasic.

plimasic link output bytes Output byte count for a link connected to a PLIM asic.

cpuctrl input packets Input packet count from the CPU of the linecards.

cpuctrl output bytes Output byte count to the CPU of the linecards.

pse input packets Input packet count from the upstream Packet Switching Engine (PSE) ASIC.

egressq OOB drops Out of buffer (OOB) packet drop count.

cpuctrl dropped packets Count of packets dropped from the CPU of the linecards.

pse dropped packets Count of packets dropped at the interface between the egress queue ASIC and the PSE ASIC.

hpi drop cpu pkts Count of packets from the CPU, dopped at the Host Processor Interface (HPI) block.

hpi drop cpu bytes Count of bytes from the CPU, dropped at the Host Processor Interface block.

enq drop cpu pkts enq err Count of the packets from the CPU dropped at the ENQ block due to enqueue error.

enq drop cpu pkts len err Count of the packets from the CPU dropped at the ENQ block due to length error.


OL-13669-03



Related Commands

enq drop cpu pkts int err Count of the packets from the CPU dropped at the ENQ block due to data buffer integer error.

enq drop cpu pkts OOR Count of packets from the CPU dropped at the ENQ block due to out of resource (OOR) error.

enq discard cpu pkts Count of the packets from the CPU dropped at the ENQ block due to the set discard-bit.

enq drain cpu pkts Count of the packets from the CPU dropped at the ENQ block due to queue draining operation.

enq drop epogo pkts enq err Count of the packets from the egress pogo-asic dropped at the ENQ block due to enqueue error.

enq drop epogo pkts len err Count of the packets from the egress pogo-asic dropped at the ENQ block due to length error.

enq drop epogo pkts OOR Count of the packets from the egress pogo-asic dropped at the ENQ block due to OOR error.

enq drop epogo pkts int err Count of the packets from the egress pogo-asic dropped at the ENQ block due to data buffer error.

enq discard epogo pkts Count of the packets from the egress pogo-asic dropped at the ENQ block due to the set discard-bit.

enq drain epogo pkts Count of the packets from the egress pogo-asic dropped at the ENQ block due to queue draining operation.

qmgr drain pkts Count of the packets dropped at the queue manager (QMGR) block due to queue drain operation.

Table 6 show controllers egressq statistics detail Field Descriptions (continued)

Field Description

Command Description


Displays egressq statistics for a specific location.


OL-13669-03


Modified Commands

Modified Commands The show controllers egressq resources command output has been modified to include two new columns in the output.

• show controllers egressq resources, page 3-28

The show controllers (ethernet) command output has been modified to include Cisco CRS-3-specific information in the output.

• show controllers (Ethernet), page 3-29


OL-13669-03


show controllers egressq resources

show controllers egressq resourcesThe show controllers egressq resources command output has been modified to include two new columns in the output.The new fields are- Free Percentage and Free-Pending.

The new fields in the output and the modified output display as follows:

RP/0/RP0/CPU0:router# show controllers egressq resources location 0/6/cpu0

------------------------------------------------------------------------------Resource Total Used Free Free Percentage Free-Pending------------------------------------------------------------------------------Ports 1024 29 995 97.17% N/AGroups 2048 30 2018 98.54% 0Queues 8192 51 8141 99.38% 0

Description for the new fields:

Free Percentage: resource percentage in Free state

Free-Pending: resource percentage in Packet-drain state


OL-13669-03


show controllers (Ethernet)

show controllers (Ethernet) To display status and configuration information about the Ethernet interfaces on a specific node, use the show controllers command in EXEC mode.

show controllers {GigabitEthernet | HundredGigE | TenGigE} interface-path-id [all | bert | control | internal | mac | phy | regs | stats | xgxs]

Syntax Description

Command Default No default behavior or values

Command Modes EXEC

Command History

{GigabitEthernet |HundredGigE | TenGigE }

Indicates the type of Ethernet interface whose status and configuration infor-mation you want to display. Enter GigabitEthernet, HundredGigE, TenGigE.

interface-path-id Physical interface or virtual interface.

Note Use the show interfaces command to see a list of all interfaces currently configured on the router.

For more information about the syntax for the router, use the question mark (?) online help function.

all Displays detailed information for the specified interface.

bert Displays BERT status information for the interface.

Note Not supported on the Cisco CRS 14-Port or Cisco CRS 20-Port 10-Gigabit Ethernet LAN/WAN-PHY Interface Module.

control Displays configuration and control information for the interface.

internal Displays internal information for the interface.

mac Displays mac information for the interface.

phy Displays physical information for the interface.

regs Displays register information for the interface.

stats Displays statistical information for the interface.

xgxs Displays information about the 10 Gigabit Ethernet Extended Sublayer (XGXS).


Release 3.0 This command was first introduced on the Cisco CRS Router.

Release 3.5.0 Added GigabitEthernet and TenGigE keywords and support.

Release 4.0.0.T This command was first introduced on the Cisco CRS-3.

Release 4.0.1 Added HundredGigE keyword and support on the Cisco CRS-3.


OL-13669-03




For the interface-path-id argument, use the following guidelines:

• If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:

– rack: Chassis number of the rack.

– slot: Physical slot number of the line card.

– module: Module number. A physical layer interface module (PLIM) is always 0.

– port: Physical port number of the interface.

• If specifying a virtual interface, the number range varies, depending on interface type.

Task ID

Examples Example: show controllers GigabitEthernet Command

The following example shows the output from the show controllers GigabitEthernet command:

RP/0/0/CPU0:Router# show controllers GigabitEthernet 0/4/0/0

port:0 good_octets_received: 6008282 bad_octets_received: 0 good_frames_received: 65020 bad_frames_received: 0 broadcast_frames_received: 11 multicast_frames_received: 49985 good_octets_sent: 4483774 good_frames_sent: 45648 broadcast_frames_sent: 0 multicast_frames_sent: 0 mac_transfer_error: 0 excessive_collision: 0 unrecog_mac_control_received: 0 fc_sent: 0 good_fc_received: 0 rx_over_flow_events: 0 undersize: 0 fragments: 0 oversize: 0 jabber: 0 mac_rcv_error: 0 bad_crc: 0 collisions: 0 late_collision: 0 rate_limit_dropped: 0 spi4_rx_frames: 0

Task ID Operations

cisco-support read

Note Required in addition to the interface (read) task ID to use the control keyword.

interface read


OL-13669-03



spi4_tx_frames: 0 DeviceID: 0x211911ab RevisionID: 0x00000003 SideBandFC: 0xc0000000 SERDESGlbCntl: 0x80000800 GlblEPDCntlCfg: 0x0000a033 TxFIFOUrecECCErrCtr: 0x00000000 RxFIFOUrecECCErrCtr: 0x00000000 DeviceGlobalRst: 0x00000000 GlobalCfg: 0xb480d000 PortTest: 0x00000000 PL4IOGlblStat: 0x00000002 DeviceTest: 0x00000000 MACStatus Port0: 0x0000801f MACControl0 Port0: 0x000c0000 MACControl1 Port0: 0xb1240151 MACControl2 Port0: 0x0d805f60 SERDESCntl Port0: 0x0000501a RateLimCntl Port0: 0x00000001 SysIntMask: 0x000000f0 SysIntCause: 0x00000000

GOPIntMask0: 0x801ffffe GOPIntCause0: 0x40000000 GOPIntMask1: 0x00000000 GOPIntCause1: 0x00000000 GOPIntMask2: 0xffdfb800 GOPIntCause2: 0x00000000 GOPIntMask3: 0x00000000 GOPIntCause3: 0x00000000 CalendarParam: 0x00040004 SPI4SrcDPDeskew: 0x000f2710 SrcClndrCmd: 0x00100404 SnkCalSeqPrgm: 0x00100404 SinkControl: 0x00000000 SPI4SrcMaxBrst: 0x00040004 SPI4IntfBrstLen: 0x0007000f TxPacketSize: 0xc0280011 RxFullWatermarks: 0x01f000c0 RxFIFOXOnOffFCWtrmrk: 0x05000300


Table 7 show controllers GigabitEthernet Field Descriptions

Field Description

port Identifies the Ethernet port whose information is displayed in the show controllers command output.

good_octets_received The count of received octets that had no errors.

bad_octets_received The count of received octets that had errors.

good_frames_received The count of received frames that had no errors.

bad_frames_received The count of received frames that had errors.

broadcast_frames_received The total number of well-formed broadcast packets received by the port. It excludes packets received with errors or with multicast des-tination addresses.

multicast_frames_received The total number of well-formed multicast packets received by the port. It excludes packets received with errors or with broadcast des-tination addresses.


OL-13669-03



good_octets_sent The count of transmitted octets that had no errors.

good_frames_sent The count of transmitted frames that had no errors.

broadcast_frames_sent The total number of well-formed broadcast packets transmitted by the port. It excludes packets received with errors or with multicast destination addresses.

multicast_frames_sent The total number of well-formed multicast packets transmitted by the port. It excludes packets received with errors or with multicast destination addresses.

mac_transfer_error Register that tracks all MAC transfer errors on the interface.

excessive_collision The total number of packets that failed to be sent after 16 collisions. It includes packets of all destination address types.

unrecog_mac_control_received Number of received MAC control frames that have an opcode different than 00-01.

fc_sent Number of flow control frames sent undersize

good_fc_received Number of good flow control messages received

rx_over_flow_events Indicates the number of times the port RxFifo has reached full level and at least one packet was dropped

undersize Number of undersize frames received (valid packet with length less than 64 bytes).

fragments Number of fragments received on this interface.

oversize Number of oversized frames received on this interface.

jabber Number of jabber packets received (packet length is greater than the MRU, and there is an invalid CRC, and no Rx Error event).

mac_rcv_error Number of Rx Error events seen by the receive side of the MAC (the Rx Error signal/symbol was asserted while the frame is being re-ceived).

bad_crc The number of frames received with bad CRC.

Note Collisions and late collisions apply to only half duplex mode.

collisions The total number of packets sent without error after having 1 to 15 collisions. It includes packets of all destination address types and excludes packets discarded because of insufficient resources or late collisions

late_collision The total number of packets discarded because of late collisions detected during transmission. It includes all transmit packets that had a collision after the transmission of the packet's 64th byte. The preamble and SFD are not included in the frame's byte count.

rate_limit_dropped Number of frames dropped due to the broadcast/multicast rate limit.

spi4_rx_frames SPI-4/1 receive frame count. This counter increments once for every Start of Packet (SOP) delineation marker sent on the SPI-4.2 receive interface.

Note Packets that come from the CPU are not counted.


Field Description


OL-13669-03



spi4_tx_frames: SPI-4/1 transmit frame count. This counter increments once for every packet arriving on the SPI-4.2 receive interface.

Note Packets that contain certain types of errors and packets sent to the CPU are not counted.

DeviceID Unique number identifying the device.

RevisionID Indicates the revision of the device.

SideBandFC Indicates whether serial sideband flow control is enabled on this port, and the status of ports where flow control is currently active.

SERDESGlbCntl Displays information about SERDES speed and receive (Rx) Gain on this port.

GlblEPDCntlCfg Cisco-specific register that shows whether Ethernet Packet Decoding is enabled.

TxFIFOUrecECCErrCtr Transmit (Tx) FIFO unrecoverable ECC errors counter. This counter increments once per each ECC unrecoverable error. A masked interrupt is optionally generated.

RxFIFOUrecECCErrCtr Receive (Rx) FIFO unrecoverable ECC errors counter. This counter increments once per each ECC unrecoverable error. A masked interrupt is optionally generated.

DeviceGlobalRst Global register that controls device reset state.

GlobalCfg Global register that controls enable, clock modes, and Rx Interface behavior.

PortTest Port diagnostics register.

PL4IOGlblStat Register used during SPI4.2 initialization.

DeviceTest Diagnostic loopback register.

MACStatus Port0 MAC control port register.

MACControl0 Port0 MAC control port register. Indicates whether the port is enabled on this port, and the status of flow control on this port.

MACControl1 Port0 MAC control port1 register. Indicates whether the port is enabled on this port, and the status of flow control on this port.

MACControl2 Port0 MAC control port2 register. Indicates whether the port is enabled on this port, and the status of flow control on this port.

SERDESCntl Port0 SERDES control port register. The following information is displayed:

• 0 = 50 Ohm

• 1 = 75 Ohm

RateLimCntl Port0 Rate Limit control port 10 register.

SysIntMask When the matching bit in the mask register is reset, the matching interrupt in the cause register is not included in the sum.

SysIntCause Register that tracks the causes of system interrupts.

GOPIntMask0 GOP interrupt Mask0. When the matching bit in the mask register is reset, the matching cause in the GOP register is not included in the sum.


Field Description


OL-13669-03



Example: show controllers GigabitEthernet Command

The following example shows the output from the show controllers GigabitEthernet command:

RP/0/RSP0/CPU0:Router# show controllers GigabitEthernet 0/1/0/1

Statistics for interface GigabitEthernet0/1/0/0 (cached values):Ingress: Input total bytes = 64000 Input good bytes = 64000

GOPIntCause0 Register that tracks all GOP interrupts and matches them with the GOP0 register.


GOPIntCause1 Register that tracks all GOP interrupts and matches them with the Mask1 register.





CalendarParam Register that determines the value of Calendar_LEN and Calendar M for the sink and source side.

SPI4SrcDPDeskew Register used to control the training pattern generation on the source side.

SrcClndrCmd Register used to program the CALENDAR slots in the calendar report generated by the device.

SnkCalSeqPrgm Register used to program the CALENDAR slots in the calendar report generated by the device.

SinkControl Register used to control the operation of the SPI-4.2 SINK section.

SPI4SrcMaxBrst Register used to determine the system parameters MaxBurst1 and MaxBurst2 on the source side. These values are used by the internal packet scheduler to initiate bursts on the SP-4.2 Rx interface.

SPI4IntfBrstLen Register used to determine the actual length of the data bursts on the SP-4.2 physical interfaces. These values are different than the system parameters MaxBurts1/2, which corresponds to SP-4.2 flow control.

TxPacketSize Maximum transmit packet size for the port, in hexadecimal format.

RxFullWatermarks Determines the internal RxFIFO full thresholds.

RxFIFOXOnOffFCWtrmrk Determines the generation of 802.3x PAUSE frames based on RxFIFO data fill thresholds.


Field Description


OL-13669-03



Input total packets = 1000 Input 802.1Q frames = 0 Input pause frames = 0 Input pkts 64 bytes = 1000 Input pkts 65-127 bytes = 0 Input pkts 128-255 bytes = 0 Input pkts 256-511 bytes = 0 Input pkts 512-1023 bytes = 0 Input pkts 1024-1518 bytes = 0 Input pkts 1519-Max bytes = 0 Input good pkts = 1000 Input unicast pkts = 0 Input multicast pkts = 1000 Input broadcast pkts = 0 Input drop overrun = 0

Example: show controllers GigabitEthernet Command

RP/0/RSP0/CPU0:Router# show controllers GigabitEthernet 0/0/0/1 Operational data for interface GigabitEthernet0/0/0/1:

State: Administrative state: enabled Operational state: Up LED state: Green On

Media: Media type: X fiber over short-wl laser PMD, full duplex Optics: Vendor: CISCO-FINISAR Part number: FTLF8519P2BNL-C6 Serial number: FNS120304T9

MAC address information: Operational address: 001d.e5eb.88e1 Burnt-in address: 001d.e5eb.88e1 No unicast addresses in filter No multicast addresses in filter

Autonegotiation enabled: No restricted parameters

Operational values: Speed: 1Gbps Duplex: Full Duplex Flowcontrol: None Loopback: None (or external) MTU: 1526 MRU: 1526 Inter-packet gap: standard (12)

Example: show controllers TenGigE Command

The following example shows the output from the show controllers TenGigE command for the Cisco 8-Port 10-Gigabit Ethernet physical layer interface module (PLIM):

RP/0/RP0/CPU0:Router# show controllers TenGigE 0/3/0/0

PHY:XENPAK device registers:========================

Vendor Name: CISCO-INTEL Vendor PN: TXN174112013F06


OL-13669-03



Vendor Rev: A1Vendor SN: INT08270015

R3.4.0 Final Draft—Cisco Confidential Information Package OUI: 0041f426Vendor OUI: 00137b11Vendor Date Code: 2004071200nvr_control_status = 0x0007nvr_version = 0x1envr_size0 = 0x01nvr_size1 = 0x00mem_used0 = 0x01mem_used1 = 0x00basic_addr = 0x0bcust_addr = 0x77vend_addr = 0xa7ext_vend_addr0= 0x00ext_vend_addr1= 0xffreserved0 = 0x00tcvr_type = 0x01connector = 0x01encoding = 0x01bitrate0 = 0x27bitrate1 = 0x10protocol = 0x01x_gbe_code_byte_0 = 0x02x_gbe_code_byte_1 = 0x00sonet_sdh_code_byte_0 = 0x00sonet_sdh_code_byte_1 = 0x00sonet_sdh_code_byte_2 = 0x00sonet_sdh_code_byte_3 = 0x00x_gfc_code_byte_0 = 0x00x_gfc_code_byte_1 = 0x00x_gfc_code_byte_2 = 0x00x_gfc_code_byte_3 = 0x00range0 = 0x03range1 = 0xe8fibre_type_byte_0 = 0x20fibre_type_byte_1 = 0x00

Center Wavelength:chan0 = 1310.00 nm

chan1 = 0.00 nm chan2 = 0.00 nm chan3 = 0.00 nm

basic_checksum = 0x00

Link Alarm Status Registers:rx_alarm_control = 0x0019tx_alarm_control = 0x0059lasi_control = 0x0000rx_alarm_status = 0x0018tx_alarm_status = 0x0058lasi_status = 0x0005

Digital Optical Monitoring: Transceiver Temp: 34.246 CLaser Bias Current: 4.8640 mALaser Output Power: 0.5059 mW, -3.0 dBmReceive Optical Power: 0.0000 mW, -inf dBm

Quake: devid 0x0043a400


OL-13669-03



10GE PMA/PMD Registers:Control = 0x2040 Status = 0x0082 Dev ID 0 = 0x0043 Dev ID 1 = 0xa400 Speed Ability = 0x0001 Devices 1 = 0x001a Devices 2 = 0x0000 Control 2 = 0x0006 Status 2 = 0xb541 TxDisable = 0x0000 Rx Signal Detect = 0x0000 OUI 0 = 0x0041 OUI 1 = 0xf426

R3.4.0 Final Draft—Cisco Confidential Information Quake (1.c001) = 0x0003

10GE PCS Registers:Control = 0x2040 Status = 0x0082 Dev ID 0 = 0x0043 Dev ID 1 = 0xa400 Speed Ability = 0x0001 Devices 1 = 0x001a Devices 2 = 0x0000 Control 2 = 0x0000 Status 2 = 0x8401 PKG ID 0 = 0x0000 PKG ID 1 = 0x0000 Base X Status = 0x0000 Base X Control = 0x0000 Base R Status 1 = 0x0004 Base R Status 2 = 0x0000 Base R jitter seed a0 = 0x0000 Base R jitter seed a1 = 0x0000 Base R jitter seed a2 = 0x0000 Base R jitter seed a3 = 0x0000 Base R jitter seed b0 = 0x0000 Base R jitter seed b1 = 0x0000 Base R jitter seed b2 = 0x0000 Base R jitter seed b3 = 0x0000 Base R jitter test control = 0x0000 Base R jitter test counter = 0x0000

10GE XS/XS Registers:Control = 0x2040 Status = 0x0002Dev ID 0 = 0x0043 Dev ID 1 = 0xa400Speed Ability = 0x0001 Devices 1 = 0x001a Devices 2 = 0x0000 Status 2 = 0x8000 PKG ID 0 = 0x0000 PKG ID 1 = 0x0000 Lane Status = 0x1c0f Test Control = 0x0000

DTE XGXS (BCM8011):Control = 0x0000 Status = 0x801fDev ID 0 = 0x0040 Dev ID 1 = 0x6092Control 2 = 0x202fStatus 2 = 0x8b01

Speed Ability = 0x0001 Devices 1 = 0x001a Devices 2 = 0x0000 Status 2 = 0x8000 PKG ID 0 = 0x0000 PKG ID 1 = 0x0000 Lane Status = 0x1c0f Test Control = 0x0000


MAC (PLA):Unicast MAC Address entries = 0

MAC (PLA) device is enabledMAC (PLA) device is in promiscuous modeMAC (PLA) device loopback is disabled

MAC (PLA) device MTU = 8226

8x10GE PLIM Registers:local_regs_id = 0xa6602000 local_regs_inter_stat = 0x00000000 local_regs_inter_stat_alias = 0x00000000 local_regs_inter_enbl_woset = 0x0000ff00 local_regs_inter_enbl_woclr =0x0000ff00 local_regs_chip_reset = 0x00000000 local_regs_reset = 0xff000000 local_regs_misc_io = 0x00010000 sn_link_framed = 0x00000001 sn_link_crc_errors = 0x00000000 sn_link_force_reframe = 0x00000000 sn_link_error_reframe = 0x00000001 sn_link_force_error = 0x00000000 sn_link_error_cause = 0x00000000 sn_link_error_interrupt_mask = 0x00000003 channel0_control = 0x000000a6 channel1_control = 0x000000a6 channel2_control = 0x0000008e channel3_control = 0x0000008e channel4_control = 0x0000008e channel5_control = 0x000000a6 channel6_control = 0x000000a6 channel7_control = 0x0000008e

Example: show controllers TenGigE Command

The following example shows the output from the show controllers TenGigE command:

RP/0/RSP0/CPU0:Router# show controllers TenGigE 0/3/0/0


OL-13669-03



PHY:XENPAK device registers:========================

Vendor Name: CISCO-INTEL Vendor PN: TXN174112013F06Vendor Rev: A1Vendor SN: INT08270015

Package OUI: 0041f426Vendor OUI: 00137b11Vendor Date Code: 2004071200nvr_control_status = 0x0007nvr_version = 0x1envr_size0 = 0x01nvr_size1 = 0x00mem_used0 = 0x01mem_used1 = 0x00basic_addr = 0x0bcust_addr = 0x77vend_addr = 0xa7ext_vend_addr0= 0x00ext_vend_addr1= 0xffreserved0 = 0x00tcvr_type = 0x01connector = 0x01encoding = 0x01bitrate0 = 0x27bitrate1 = 0x10protocol = 0x01x_gbe_code_byte_0 = 0x02x_gbe_code_byte_1 = 0x00sonet_sdh_code_byte_0 = 0x00sonet_sdh_code_byte_1 = 0x00sonet_sdh_code_byte_2 = 0x00sonet_sdh_code_byte_3 = 0x00x_gfc_code_byte_0 = 0x00x_gfc_code_byte_1 = 0x00x_gfc_code_byte_2 = 0x00x_gfc_code_byte_3 = 0x00range0 = 0x03range1 = 0xe8fibre_type_byte_0 = 0x20fibre_type_byte_1 = 0x00

Center Wavelength:chan0 = 1310.00 nm

chan1 = 0.00 nm chan2 = 0.00 nm chan3 = 0.00 nm

basic_checksum = 0x00

Link Alarm Status Registers:rx_alarm_control = 0x0019tx_alarm_control = 0x0059lasi_control = 0x0000rx_alarm_status = 0x0018tx_alarm_status = 0x0058lasi_status = 0x0005

Digital Optical Monitoring:


OL-13669-03



Transceiver Temp: 34.246 CLaser Bias Current: 4.8640 mALaser Output Power: 0.5059 mW, -3.0 dBmReceive Optical Power: 0.0000 mW, -inf dBm

Quake: devid 0x0043a40010GE PMA/PMD Registers:Control = 0x2040 Status = 0x0082 Dev ID 0 = 0x0043 Dev ID 1 = 0xa400 Speed Ability = 0x0001 Devices 1 = 0x001a Devices 2 = 0x0000 Control 2 = 0x0006 Status 2 = 0xb541 TxDisable = 0x0000 Rx Signal Detect = 0x0000 OUI 0 = 0x0041 OUI 1 = 0xf426

Quake (1.c001) = 0x0003

10GE PCS Registers:Control = 0x2040 Status = 0x0082 Dev ID 0 = 0x0043 Dev ID 1 = 0xa400 Speed Ability = 0x0001 Devices 1 = 0x001a Devices 2 = 0x0000 Control 2 = 0x0000 Status 2 = 0x8401 PKG ID 0 = 0x0000 PKG ID 1 = 0x0000 Base X Status = 0x0000 Base X Control = 0x0000 Base R Status 1 = 0x0004 Base R Status 2 = 0x0000 Base R jitter seed a0 = 0x0000 Base R jitter seed a1 = 0x0000 Base R jitter seed a2 = 0x0000 Base R jitter seed a3 = 0x0000 Base R jitter seed b0 = 0x0000 Base R jitter seed b1 = 0x0000 Base R jitter seed b2 = 0x0000 Base R jitter seed b3 = 0x0000 Base R jitter test control = 0x0000 Base R jitter test counter = 0x0000

10GE XS/XS Registers:Control = 0x2040 Status = 0x0002Dev ID 0 = 0x0043 Dev ID 1 = 0xa400Speed Ability = 0x0001 Devices 1 = 0x001a Devices 2 = 0x0000 Status 2 = 0x8000 PKG ID 0 = 0x0000 PKG ID 1 = 0x0000 Lane Status = 0x1c0f Test Control = 0x0000


Speed Ability = 0x0001 Devices 1 = 0x001a Devices 2 = 0x0000 Status 2 = 0x8000 PKG ID 0 = 0x0000 PKG ID 1 = 0x0000 Lane Status = 0x1c0f Test Control = 0x0000


MAC (PLA):Unicast MAC Address entries = 0

MAC (PLA) device is enabledMAC (PLA) device is in promiscuous modeMAC (PLA) device loopback is disabled

MAC (PLA) device MTU = 8226

8x10GE PLIM Registers:local_regs_id = 0xa6602000 local_regs_inter_stat = 0x00000000 local_regs_inter_stat_alias = 0x00000000 local_regs_inter_enbl_woset = 0x0000ff00 local_regs_inter_enbl_woclr =0x0000ff00 local_regs_chip_reset = 0x00000000 local_regs_reset = 0xff000000 local_regs_misc_io = 0x00010000 sn_link_framed = 0x00000001 sn_link_crc_errors = 0x00000000 sn_link_force_reframe = 0x00000000 sn_link_error_reframe = 0x00000001 sn_link_force_error = 0x00000000 sn_link_error_cause = 0x00000000 sn_link_error_interrupt_mask = 0x00000003 channel0_control = 0x000000a6 channel1_control = 0x000000a6 channel2_control = 0x0000008e channel3_control = 0x0000008e channel4_control = 0x0000008e channel5_control = 0x000000a6 channel6_control = 0x000000a6 channel7_control = 0x0000008e


OL-13669-03



RP/0/RSP0/CPU0:Router# show controllers TenGigE 0/2/0/1

Operational data for interface TenGigE0/2/0/1:

State: Administrative state: enabled Operational state: Down (Reason: Link loss or low light, no loopback) LED state: Red On

Media: Media type: R fiber over 1310nm optics Optics: Vendor: CISCO-OPNEXT Part number: TRF5011AA-LF003 Serial number: ONT1119104B

MAC address information: Operational address: 001d.e5eb.96dd Burnt-in address: 001d.e5eb.96dd No unicast addresses in filter No multicast addresses in filter

Autonegotiation disabled.


The following example shows sample output for the base form of the show controllers TenGigE command for the Cisco CRS 14-Port 10-Gigabit Ethernet LAN/WAN-PHY Interface Module:

RP/0/RP0/CPU0:Router# show controllers TenGigE 0/1/0/0 Thu Oct 7 16:18:32.348 ESTOperational data for interface TenGigE0/1/0/0:

State: Administrative state: disabled Operational state: Down (Reason: Link loss or low light, no loopback) LED state: Yellow On

Phy: Media type: R fiber over 1310nm optics Optics: Vendor: CISCO-SUMITOMO Part number: SXP3101NV-C1 Serial number: ECL120701L2

MAC address information: Operational address: 0014.f294.6776 Burnt-in address: 0014.f294.6776 No unicast addresses in filter Operating in multicast promiscuous mode


Operational values: Speed: 10Gbps


OL-13669-03



Duplex: Full Duplex Flowcontrol: None Loopback: None (or external) MTU: 1522 MRU: 1522 Inter-packet gap: standard (12)

Example: show controllers TenGigE all Command

RP/0/RSP0/CPU0:Router# show controllers TenGigE 0/6/0/2 allOperational data for interface TenGigE0/6/0/2:

State: Administrative state: disabled Operational state: Down (Reason: The optics for the port are not present) LED state: Yellow On

Media: Media type: Initializing, true state or type not yet known No optics present

MAC address information: Operational address: 001d.353b.975e Burnt-in address: 001d.353b.975e No unicast addresses in filter No multicast addresses in filter



BERT status for TenGigE0/6/0/2:

BERT State : DISABLEDTest Pattern : None test patternTime Remaining : 0Time Interval : 0Statistics for interface TenGigE0/6/0/2 (cached values):

Ingress: Input total bytes = 0 Input good bytes = 0

Input total packets = 0 Input 802.1Q frames = 0 Input pause frames = 0 Input pkts 64 bytes = 0 Input pkts 65-127 bytes = 0 Input pkts 128-255 bytes = 0 Input pkts 256-511 bytes = 0 Input pkts 512-1023 bytes = 0 Input pkts 1024-1518 bytes = 0 Input pkts 1519-Max bytes = 0

Input good pkts = 0 Input unicast pkts = 0


OL-13669-03



Input multicast pkts = 0 Input broadcast pkts = 0

Input drop overrun = 0 Input drop abort = 0 Input drop unknown 802.1Q = 0 Input drop other = 0

Input error giant = 0 Input error runt = 0 Input error jabbers = 0 Input error fragments = 0 Input error CRC = 0 Input error collisions = 0 Input error symbol = 0 Input error other = 0

Input MIB giant = 0 Input MIB jabber = 0 Input MIB CRC = 0

Egress: Output total bytes = 0 Output good bytes = 0

Output total packets = 0 Output 802.1Q frames = 0 Output pause frames = 0 Output pkts 64 bytes = 0 Output pkts 65-127 bytes = 0 Output pkts 128-255 bytes = 0 Output pkts 256-511 bytes = 0 Output pkts 512-1023 bytes = 0 Output pkts 1024-1518 bytes = 0 Output pkts 1519-Max bytes = 0

Output good pkts = 0 Output unicast pkts = 0 Output multicast pkts = 0 Output broadcast pkts = 0

Output drop underrun = 0 Output drop abort = 0 Output drop other = 0

Output error other = 0

Management information for interface TenGigE0/6/0/2:

Port number: 2Bay number: 0Interface handle: 0x100000c0

Config: Auto-negotiation: Configuration not supported (Off) Carrier delay (up): Not configured Carrier delay (down): Not configured Speed: Configuration not supported (10Gbps) Duplex: Configuration not supported (Full Duplex) Flow Control: Not configured (None) IPG: Not configured (standard (12)) Loopback: Not configured (None) MTU: Not configured Soft Bandwidth: Not configured


OL-13669-03



Driver constraints: Min MTU: 64 bytes Max MTU: 9216 bytes Max speed: 10Gbps Interface type: TenGigE Management interface: No Promiscuous mode: Yes Allowed config mask: 0x27b

Cached driver state: MTU: 1522 bytes Burnt-in MAC address: 001d.353b.975e

Bundle settings: Aggregated: No Bundle MTU: 1514 bytes Bundle MAC address: 001d.353b.975e

Port FSM state: Port is disabled, due to an admin down condition.Complete FSM state: Admin down Bundle admin up Client admin up Client admin tx not disabled Port disabled Port tx disabled Hardware link downIDB interface state information: IDB bundle admin up IDB client admin up IDB client tx admin up IDB error disable not set

0 Unicast MAC Addresses:

0 Multicast MAC Addresses:

0 Unicast Bundle MAC Addresses:

0 Multicast Bundle MAC Addresses:

Current DataNP(01) Version : 0003Structure Version : 2582XAUI Interface : BMAC addr : 00.1d.35.3b.97.5e RX enabled : False TX enabled : True Obey Pause Frames : False TX Pause Frames : False Pause Re-TX Period : 3000000 Min Frame Len : 60 Max Frame Len : 1526 Ignore Errors : False Add CRC : True Strip CRC : True Ignore CRC Errors : False DMA Add CRC : False DMA Strip CRC : False Ignore Length Error: True Pad Short Frames : True


OL-13669-03



Min TX IFG : 12 Min RX IFG : 4 IFG Rate Control : False Hi Gig Mode : False Discard Ctrl Frames: True Enable Stats Update: True RX Stats Int Mask : 0x00000000 TX Stats Int Mask : 0x00000000

Port Number : 2 Port Type : 10GE Transport mode : LAN BIA MAC addr : 001d.353b.975eOper. MAC addr : 001d.353b.975ePort Available : trueStatus polling is : enabledStatus events are : enabledI/F Handle : 0x100000c0Cfg Link Enabled : disabledH/W Tx Enable : yesMTU : 1526H/W Speed : 10 Gbps H/W Duplex : Full H/W Loopback Type : None H/W FlowCtrl type : None H/W AutoNeg Enable: Off H/W Link Defects : interface is admin down Link Up : noLink Led Status : ShutdownSymbol errors : 0Serdes version : 14.42Input good underflow : 0Input ucast underflow : 0Output ucast underflow : 0Input unknown opcode underflow: 0Pluggable Present : noPluggable Type : Unknown pluggable optics Pluggable Compl. : Not CheckedPluggable Type Supp.: Not CheckedPluggable PID Supp. : Not CheckedPluggable Scan Flg: false

XFP #2 is not present

Serdes Registers and info port: 2 EDC Status : 000000050 - EDC Aquiring Rx detected : No Block lock : No Tx aligned : Yes

MAC Registers for port: 2 CONFIG1 (#1034): 0510081a CONFIG2 (#1035): 040c05f6 CONTROL (#1036): 00000000 ADDRESS_LOW (#1037): 353b975e ADDRESS_HIGH (#1038): 0000001d MII_MGMT_CONFIG (#1039): 00000007 MII_MGMT_CMD (#1040): 00000000


OL-13669-03



MII_MGMT_ADDRESS (#1041): 00000000 MII_MGMT_DATA (#1042): 40000000 STAT_CONFIG (#1043): 00000007 MASK_R (#1044): 00000000 MASK_T (#1045): 00000000 COMP (#1046): 00100d24 MAC_CONFIG (#1047): ffffffff INTERRUPT_C (#1048): 00000002

RP/0/RSP0/CPU0:Router# show controllers TenGigE 0/4/0/0 all

Operational data for interface TenGigE0/4/0/0:

State: Administrative state: enabled Operational state: Up LED state: Green On

Media: Media type: R fiber over 1310nm optics Optics: Vendor: CISCO-OPNEXT Part number: TRF5012AN-LA000 Serial number: ONT1207108S

MAC address information: Operational address: 001b.53ff.a780 Burnt-in address: 001b.53ff.a780 No unicast addresses in filter No multicast addresses in filter



BERT status for TenGigE0/4/0/0:

BERT State : DISABLEDTest Pattern : None test patternTime Remaining : 0Time Interval : 0Statistics for interface TenGigE0/4/0/0 (cached values):




OL-13669-03



Input good pkts = 106745913 Input unicast pkts = 105659161 Input multicast pkts = 1086750 Input broadcast pkts = 2










Port number: 0Bay number: 0Interface handle: 0xc000040

Config: Auto-negotiation: Configuration not supported (Off) Carrier delay (up): Not configured Carrier delay (down): Not configured Speed: Configuration not supported (10Gbps) Duplex: Configuration not supported (Full Duplex) Flow Control: Not configured (None) IPG: Not configured (standard (12))


OL-13669-03



Loopback: Not configured (None) MTU: 9100 bytes Soft Bandwidth: Not configured


Cached driver state: MTU: 9108 bytes Burnt-in MAC address: 001b.53ff.a780

Bundle settings: Aggregated: No Bundle MTU: 1514 bytes Bundle MAC address: 001b.53ff.a780

Port FSM state: Port is enabled, link is upComplete FSM state: Admin up Bundle admin up Client admin up Client admin tx not disabled Port enabled Port tx enabled Hardware link upIDB interface state information: IDB bundle admin up IDB client admin up IDB client tx admin up IDB error disable not set





Current DataNP(03) Version : 0003Structure Version : 2582XAUI Interface : BMAC addr : 00.1b.53.ff.a7.80 RX enabled : True TX enabled : True Obey Pause Frames : False TX Pause Frames : False Pause Re-TX Period : 3000000 Min Frame Len : 60 Max Frame Len : 9112 Ignore Errors : False Add CRC : True Strip CRC : True Ignore CRC Errors : False DMA Add CRC : False


OL-13669-03



DMA Strip CRC : False Ignore Length Error: True Pad Short Frames : True Min TX IFG : 12 Min RX IFG : 4 IFG Rate Control : False Hi Gig Mode : False Discard Ctrl Frames: True Enable Stats Update: True RX Stats Int Mask : 0x00000000 TX Stats Int Mask : 0x00000000

Port Number : 0 Port Type : 10GE Transport mode : LAN BIA MAC addr : 001b.53ff.a780Oper. MAC addr : 001b.53ff.a780Port Available : trueStatus polling is : enabledStatus events are : enabledI/F Handle : 0x0c000040Cfg Link Enabled : tx/rx enabledH/W Tx Enable : yesMTU : 9112H/W Speed : 10 Gbps H/W Duplex : Full H/W Loopback Type : None H/W FlowCtrl type : None H/W AutoNeg Enable: Off H/W Link Defects : (0x0000) None Link Up : yesLink Led Status : Link upSymbol errors : 255Serdes version : 14.42Input good underflow : 0Input ucast underflow : 0Output ucast underflow : 0Input unknown opcode underflow: 0Pluggable Present : yesPluggable Type : 10GBASE-LR Pluggable Compl. : CompliantPluggable Type Supp.: SupportedPluggable PID Supp. : SupportedPluggable Scan Flg: false

XFP EEPROM port: 0 Xcvr Type: XFP Ext Type: 2.5 W, CDR Supported, No Tx Ref Clk input req., CLEI present, Connector Type: LC Ethernet Xcvr Codes: 10GBASE-LR, 10GE-FC-1200-SM-LL-L, SONET Xcvr Codes: SDH_I_64.1 Encodeing: 64B/66B, SONET Scrambled, NRZ, Bit Rate Min.: 9900 Mbit/s Bit Rate Max.: 11100 Mbit/s Link Reach 9u SM fiber: 10 Km Device Tech.: 1310 nm DFB, No wavelength ctrl, Uncooled Xmtr, PIN detec Vendor Name CISCO-OPNEXT CDR Support: 9.95 Gb/s, 10.3 Gb/s, 10.5 Gb/s, Vendor OUI: 00.0b.40 Vendor Part Number TRF5012AN-LA000 (rev.: 01) Wavelength: 1310 nm


OL-13669-03



Wavelength Tolerance: 20 nm Vendor Serial Number: ONT1207108S Date Code (yy/mm/dd): 08/02/16 lot code: Diagnostic Monitoring: FEC BER not supported, average Rx power measured Enhanced Options: Soft TX disable, Extended Id: XFP (0x00 ) MSA Data (Table 01)0x0080: 06 58 07 40 40 00 00 40 : 00 00 00 b0 63 6f 0a 00 0x0090: 00 00 00 40 43 49 53 43 : 4f 2d 4f 50 4e 45 58 54 0x00a0: 20 20 20 20 e0 00 0b 40 : 54 52 46 35 30 31 32 41 0x00b0: 4e 2d 4c 41 30 30 30 20 : 30 31 66 58 0f a0 46 d9 0x00c0: 7d 96 06 00 4f 4e 54 31 : 32 30 37 31 30 38 53 20 0x00d0: 20 20 20 20 30 38 30 32 : 31 36 20 20 08 40 70 89

CLEI Code: WMOTBEVAAB Part Number 10-1989-02 (ver.: V02 ) Temp/Alarm/Power Flags: COM, commercial -5C to 70C Product ID: XFP-10GLR-OC192SR Cisco Specific Data (Table 02)0x0100: 57 4d 4f 54 42 45 56 41 : 41 42 31 30 2d 31 39 38 0x0110: 39 2d 30 32 56 30 32 20 : 01 00 00 00 00 00 00 00 0x0120: 00 b9 00 00 00 00 00 00 : 00 00 58 af 60 61 70 8f 0x0130: 92 d5 00 00 1e 00 5a e0 : 11 ee 00 85 00 00 aa aa 0x0140: 58 46 50 2d 31 30 47 4c : 52 2d 4f 43 31 39 32 53 0x0150: 52 20 20 20 00 00 00 00 : 00 00 00 00 00 00 00 c1 0x0160: 32 35 35 34 36 36 35 30 : 00 a1 00 00 00 00 00 00 0x0170: 00 00 00 00 00 00 00 00 : 00 00 00 00 00 00 00 00

Signal Condition Control: Normal Async REFCLK, Thresholds: Alarm High Warning High w Temperature: 90.000 85.000 0 Voltage: 0.000 Volt 0.000 Volt t Bias: 130.000 mAmps 120.000 mAmps s Transmit Power: 1.585 mW (2.00 dBm) 1.000 mW (0.00 dBm) 0.200 m) Receive Power: 1.259 mW (1.00 dBm) 1.122 mW (0.50 dBm) 0.029 m) Temperature: 32.000 Voltage: 0.000 Volt Tx Bias: 47.122 mAmps Tx Power: 0.459 mW (-3.38 dBm) Rx Power: 0.141 mW (-8.50 dBm) Control Status: Digital Diagnostics Data (Lower Memory)0x0000: 06 00 5a 00 f6 00 55 00 : fb 00 00 00 00 00 00 00 0x0010: 00 00 fd e8 13 88 ea 60 : 17 70 3d e8 04 ea 27 10 0x0020: 07 cb 31 2d 00 b5 2b d4 : 01 20 89 ee 77 e2 87 5a 0x0030: 7a 75 00 00 00 00 00 00 : 00 00 00 00 00 00 00 00 0x0040: 00 00 00 00 00 00 00 00 : 00 00 00 00 00 00 00 00 0x0050: 00 00 00 00 00 00 00 00 : 00 00 00 00 00 00 00 00 0x0060: 20 00 00 00 5c 09 11 ee : 05 86 80 29 00 00 04 00 0x0070: 00 00 00 00 00 00 00 00 : 00 00 00 00 00 00 00 02

Serdes Registers and info port: 0 EDC Status : 000000070 - EDC tracking Rx detected : Yes Block lock : Yes Tx aligned : Yes

MAC Registers for port: 0 CONFIG1 (#1034): 03100a1a CONFIG2 (#1035): 040c2398


OL-13669-03



CONTROL (#1036): 00000000 ADDRESS_LOW (#1037): 53ffa780 ADDRESS_HIGH (#1038): 0000001b MII_MGMT_CONFIG (#1039): 00000007 MII_MGMT_CMD (#1040): 00000000 MII_MGMT_ADDRESS (#1041): 00000000 MII_MGMT_DATA (#1042): 40000000 STAT_CONFIG (#1043): 00000007 MASK_R (#1044): 00000000 MASK_T (#1045): 00000000 COMP (#1046): 00100d24 MAC_CONFIG (#1047): ffffffff INTERRUPT_C (#1048): 00000000

The following example shows sample output for the show controllers TenGigE all command for the Cisco CRS 14-Port 10-Gigabit Ethernet LAN/WAN-PHY Interface Module:

RP/0/RP0/CPU0:Router# show controllers TenGigE 0/1/0/0 all

Thu Oct 7 18:23:49.231 ESTOperational data for interface TenGigE0/1/0/0:

State: Administrative state: disabled Operational state: Down (Reason: Link loss or low light, no loopback) LED state: Yellow On

Phy: Media type: R fiber over 1310nm optics Optics: Vendor: CISCO-SUMITOMO Part number: SXP3101NV-C1 Serial number: ECL120701L2

MAC address information: Operational address: 0014.f294.6776 Burnt-in address: 0014.f294.6776 No unicast addresses in filter Operating in multicast promiscuous mode



Statistics for interface TenGigE0/1/0/0 (cached values):


Input total packets = 0 Input 802.1Q frames = 0 Input pause frames = 0 Input pkts 64 bytes = 0 Input pkts 65-127 bytes = 0 Input pkts 128-255 bytes = 0 Input pkts 256-511 bytes = 0


OL-13669-03



Input pkts 512-1023 bytes = 0 Input pkts 1024-1518 bytes = 0 Input pkts 1519-Max bytes = 0


Input drop overrun = 0 Input drop abort = 0 Input drop invalid VLAN = 0 --> This appears to be new Input drop invalid DMAC = 0 --> This appears to be new Input drop invalid encap = 0 --> This appears to be new Input drop other = 0









Port number: 0Bay number: 0Interface handle: 0x1180200

Config: Auto-negotiation: Configuration not supported (Off) Carrier delay (up): Not configured


OL-13669-03



Carrier delay (down): Not configured Speed: Configuration not supported (10Gbps) Duplex: Configuration not supported (Full Duplex) Flow Control: Not configured (None) IPG: Not configured (standard (12)) Loopback: Not configured (None) MTU: Not configured Bandwidth: Not configured --> This output field is changed BER-SD Threshold: Configuration not supported --> These BER output fields are new BER-SD Report: Configuration not supported BER-SF Threshold: Configuration not supported BER-SF Report: Configuration not supported BER-SF Signal Remote Failure: Configuration not supported

Driver constraints: Min MTU: 64 bytes Max MTU: 9600 bytes Max speed: 10Gbps Interface type: TenGigE Management interface: No Promiscuous mode: Yes Default carrier delay up (auto-neg on): 0 ms --> This field is new Default carrier delay down (auto-neg on): 0 ms --> This field is new Default carrier delay up (auto-neg off): 0 ms --> This field is new Default carrier delay down (auto-neg off): 0 ms --> This field is new Allowed config mask: 0x27b

Cached driver state: MTU: 1522 bytes Burnt-in MAC address: 0014.f294.6776

Operational carrier delay: --> This section is new Carrier delay (up): 0 ms Carrier delay (down): 0 ms

Bundle settings: Aggregated: No Bundle MTU: 1514 bytes Bundle MAC address: 0014.f294.6776







OL-13669-03



Operational address: 0014.f294.6776 --> The rest of this output appears to be newBurnt-in address: 0014.f294.6776

PLA 0 port 0 MAC enabled Rx MAC disabledAdministrative state: Forced Remote faultOperational state: Remote fault

0 HSRP/VRRP MAC addresses

VLAN Ethertype: 0x8100QinQ Ethertype: 0x88a8MTP Ethertype: 0x88e7

4 VLAN UIDB entriesVLAN1 VLAN2 Packet Type Flags UIDB Result Flags 0 0 VLAN 1 VLAN 0 0 ARPA 1 ARPA 0 0 SAP 1 SAP 0 0 1 SNAP

Total Power Available on PLIM for XFP's: 35000 mW Power used by Inserted XFP's: 33000 mW Power Available: 2000 mW

Port Power Used State 00 2500 mW XFP Inserted and Powered On 01 2500 mW XFP Inserted and Powered On 02 1500 mW XFP Inserted and Powered On 03 2500 mW XFP Inserted and Powered On 04 2500 mW XFP Inserted and Powered On 05 1500 mW XFP Inserted and Powered On 06 2500 mW XFP Inserted and Powered On 07 2500 mW XFP Inserted and Powered On 08 2500 mW XFP Inserted and Powered On 09 2500 mW XFP Inserted and Powered On 10 2500 mW XFP Inserted and Powered On 11 2500 mW XFP Inserted and Powered On 12 2500 mW XFP Inserted and Powered On 13 2500 mW XFP Inserted and Powered On

802.3ae Sections================

PMA/PMD Previous Alarm Status: PMA/PMD NOT Locked to Local Signal Current Alarm Status: PMA/PMD NOT Locked to Local Signal PMA/PMD Local Fault SR Ability Loopback Ability Rx Local Fault

PCS Previous Alarm Status: PCS Rx Link DOWN PCS Rx NOT Block Locked PCS Rx Link Status DOWN PCS Error'd Block Counts: 0 PCS BER Counts: 0 PCS has NO Block Lock Current Alarm Status:


OL-13669-03



PCS Rx Link DOWN PCS Local Fault Detected PCS Rx Local Fault Detected PCS Rx NOT Block Locked PCS Rx Link Status DOWN PCS Error'd Block Counts: 0 PCS BER Counts: 0 PCS has NO Block Lock

WIS: HW In LAN Mode - No Info

XFP General Info:=================

UDI Checking: DisabledPHY/XFP Status: XFP Not UDI Compliant XFP is Working as expected

XFP Info:=========Max Power Dissipation: 2500 mW

XFP Type: 10GBASE-LRVendor Name: CISCO-SUMITOMO Vendor Part Number: SXP3101NV-C1 Vendor OUI: 0x00-0x00-0x5fVendor Hardware Revision: C Vendor Serial number: ECL120701L2 Date Code (yy/mm/dd): 08/02/27Lot Code: D0

Cisco PID: XFP-10GLR-OC192SR Cisco VID: V02 Cisco PN: 10-1989-02

ID: XFPExtended ID: 0x58 TX ref clock input is not required CDP is supported Power Level 2 (2.5W max. power)Minimum bit rate is 9900 MBits/s.Maximum bit rate is 10300 MBits/s.

XFP Detail Info:================

Temp: 32.223Tx bias: 0.0 mATx power: 0.0 mW (-40 dBm)Rx power: 0.33 mW (-24 dBm)AUX 1: +3.3V Supply Voltage: 0x70AUX 2: Auxiliary monitoring not implemented: 0x0

XFP Status: enabled. laser is enabled MOD NR is not ready is powered off doesn't have interrupt(s) has LOS data is ready TX path is ready


OL-13669-03



TX laser is not in fault condition TX path CDR is locked RX path is not ready RX path CDR is not locked

Alarms: Low RX power alarm

Warnings: Low RX power warning

THRESHOLDS High Alarm Low Alarm High Warning Low Warng Temperature C 80.0 -15.0 75.0 -10.0 Voltage V 000.0000 000.0000 000.0000 000.000 Bias Current mA 100.0000 000.0000 080.0000 000.000 Transmit power mW 015.8480 001.2580 010.0000 001.990 Receive power mW 022.3870 000.1810 014.1250 000.280DTE XGXS Current Alarm Status: XGXS Lanes All Synchronized XGXS Lanes AlignedPHY XGXS Previous Alarm Status: NO XGXS Local Fault TX Link Down Current Alarm Status: NO XGXS Local Fault TX Link UP

LASI 802.3ae Registers:=======================Previous: LASI Status = 0x000d Rx Alarm Status = 0x0018 Tx Alarm Status = 0x0020Current: LASI Status = 0x000c Rx Alarm Status = 0x0018 Tx Alarm Status = 0x0000

PMA/PMD 802.3ae Registers:============================Control = 0x2040 Status = 0x0082 Dev ID 0 = 0x0043 Dev ID 1 = 0xa400Speed Ability = 0x0001 Devices 1 = 0x001e Devices 2 = 0x0000 Control 2 = 0x0007 Status 2 = 0xb581Tx Disable = 0x0000 Rx Signal Detect = 0x0000OUI 0 = 0x0000 OUI 1 = 0x0000Current: Status = 0x0082 Status 2 = 0xb581

WIS 802.3ae Registers:======================Control = 0x2040 Status = 0x0082 Dev ID 0 = 0x0043 Dev ID 1 = 0xa400Speed Ability = 0x0001 Devices 1 = 0x001e Devices 2 = 0x0000Control 2 = 0x0000 Status 2 = 0x8003 Status 3 = 0x0048Test Pattern Error Counter = 0x0000 Far End BLock Error Counter = 0x0000J1 TX 1 = 0x0000 J1 TX 2 = 0x0000 J1 TX 3 = 0x0000 J1 TX 4 = 0x0000 J1 TX 5 = 0x0000 J1 TX 6 = 0x0000 J1 TX 7 = 0x0000 J1 TX 8 = 0x8900J1 RX 1 = 0x0000 J1 RX 2 = 0x0000 J1 RX 3 = 0x0000 J1 RX 4 = 0x0000 J1 RX 5 = 0x0000 J1 RX 6 = 0x0000 J1 RX 7 = 0x0000 J1 RX 8 = 0x0000Far End BIP Error 0 = 0x0000 Far End BIP Error 1 = 0x0000Line BIP Error 0 = 0x0000 Line BIP Error 1 = 0x0000Path BIP Error Count = 0x0000 Section BIP Error Count = 0x0000J0 Tx 1 = 0x0000 J0 Tx 2 = 0x0000 J0 Tx 3 = 0x0000 J0 Tx 4 = 0x0000J0 Tx 5 = 0x0000 J0 Tx 6 = 0x0000 J0 Tx 7 = 0x0000 J0 Tx 8 = 0x8900J0 Rx 1 = 0x0000 J0 Rx 2 = 0x0000 J0 Rx 3 = 0x0000 J0 Rx 4 = 0x0000J0 Rx 5 = 0x0000 J0 Rx 6 = 0x0000 J0 Rx 7 = 0x0000 J0 Rx 8 = 0x0000Current: Status = 0x0082 Status 2 = 0x8003 Status 3 = 0x0048

PCS 802.3ae Registers:


OL-13669-03



======================Control = 0x2040 Status = 0x0082 Dev ID 0 = 0x0043 Dev ID 1 = 0xa400Speed Ability = 0x0001 Devices 1 = 0x001e Devices 2 = 0x0000 Control 2 = 0x0000 Status 2 = 0x8405PKG ID 0 = 0x0000 PKG ID 1 = 0x0000Base X Status = 0x0000 Base X Control = 0x0000Base R Status 1 = 0x0004 Base R Status 2 = 0x0000Base R jitter seed a0 = 0x0000 Base R jitter seed a1 = 0x0000Base R jitter seed a2 = 0x0000 Base R jitter seed a3 = 0x0000Base R jitter seed b0 = 0x0000 Base R jitter seed b1 = 0x0000Base R jitter seed b2 = 0x0000 Base R jitter seed b3 = 0x0000Base R jitter test control = 0x0000 Base R jitter test counter = 0x0000Current: Status = 0x0082 Status 2 = 0x8405 Base R 1 = 0x0004 Base R 2 = 0x0000

PHY XS 802.3ae Registers:=========================Control = 0x2040 Status = 0x0006Dev ID 0 = 0x0043 Dev ID 1 = 0xa400Speed Ability = 0x0001 Devices 1 = 0x001e Devices 2 = 0x0000Status 2 = 0x8000 PKG ID 0 = 0x0000 PKG ID 1 = 0x0000Lane Status = 0x1c0f Test Control = 0x0000Current: Status = 0x0006 Status 2 = 0x8000 Lane Status = 0x1c0f

XFP Register Info (MSA):========================(Reg 000 = 0x06) (Reg 001 = 0x00) (Reg 002 = 0x50) (Reg 003 = 0x00) (Reg 004 = 0xf1) (Reg 005 = 0x00) (Reg 006 = 0x4b) (Reg 007 = 0x00) (Reg 008 = 0xf6) (Reg 009 = 0x00) (Reg 010 = 0x00) (Reg 011 = 0x00) (Reg 012 = 0x00) (Reg 013 = 0x00) (Reg 014 = 0x00) (Reg 015 = 0x00) (Reg 016 = 0x00) (Reg 017 = 0x00) (Reg 018 = 0xc3) (Reg 019 = 0x50) (Reg 020 = 0x00) (Reg 021 = 0x00) (Reg 022 = 0x9c) (Reg 023 = 0x40) (Reg 024 = 0x00) (Reg 025 = 0x00) (Reg 026 = 0x3d) (Reg 027 = 0xe8) (Reg 028 = 0x04) (Reg 029 = 0xea) (Reg 030 = 0x27) (Reg 031 = 0x10) (Reg 032 = 0x07) (Reg 033 = 0xcb) (Reg 034 = 0x57) (Reg 035 = 0x73) (Reg 036 = 0x00) (Reg 037 = 0xb5) (Reg 038 = 0x37) (Reg 039 = 0x2d) (Reg 040 = 0x01) (Reg 041 = 0x20) (Reg 042 = 0x00) (Reg 043 = 0x00) (Reg 044 = 0x00) (Reg 045 = 0x00) (Reg 046 = 0x00) (Reg 047 = 0x00) (Reg 048 = 0x00) (Reg 049 = 0x00) (Reg 050 = 0x00) (Reg 051 = 0x00) (Reg 052 = 0x00) (Reg 053 = 0x00) (Reg 054 = 0x00) (Reg 055 = 0x00) (Reg 056 = 0x00) (Reg 057 = 0x00) (Reg 058 = 0x00) (Reg 059 = 0x00) (Reg 060 = 0x00) (Reg 061 = 0x00) (Reg 062 = 0x00) (Reg 063 = 0x00) (Reg 064 = 0x00) (Reg 065 = 0x00) (Reg 066 = 0x00) (Reg 067 = 0x00) (Reg 068 = 0x00) (Reg 069 = 0x00) (Reg 070 = 0x00) (Reg 071 = 0x00) (Reg 072 = 0x00) (Reg 073 = 0x00) (Reg 074 = 0x00) (Reg 075 = 0x00) (Reg 076 = 0x00) (Reg 077 = 0x00) (Reg 078 = 0x00) (Reg 079 = 0x00) (Reg 080 = 0x00) (Reg 081 = 0x40) (Reg 082 = 0x00) (Reg 083 = 0x40) (Reg 084 = 0x1e) (Reg 085 = 0x00) (Reg 086 = 0x00) (Reg 087 = 0x00) (Reg 088 = 0x00) (Reg 089 = 0x00) (Reg 090 = 0x00) (Reg 091 = 0x00) (Reg 092 = 0x00) (Reg 093 = 0x00) (Reg 094 = 0x00) (Reg 095 = 0x00) (Reg 096 = 0x20) (Reg 097 = 0xdf) (Reg 098 = 0x00) (Reg 099 = 0x00) (Reg 100 = 0x00) (Reg 101 = 0x00) (Reg 102 = 0x00) (Reg 103 = 0x00) (Reg 104 = 0x00) (Reg 105 = 0x21) (Reg 106 = 0x7e) (Reg 107 = 0x44) (Reg 108 = 0x00) (Reg 109 = 0x00) (Reg 110 = 0x32) (Reg 111 = 0x18) (Reg 112 = 0x00) (Reg 113 = 0x00) (Reg 114 = 0x00) (Reg 115 = 0x00) (Reg 116 = 0x00) (Reg 117 = 0x00) (Reg 118 = 0x00) (Reg 119 = 0x00) (Reg 120 = 0x00) (Reg 121 = 0x00) (Reg 122 = 0x00) (Reg 123 = 0x00) (Reg 124 = 0x00) (Reg 125 = 0x00) (Reg 126 = 0x00) (Reg 127 = 0x01)

(Reg 128 = 0x06) (Reg 129 = 0x58) (Reg 130 = 0x07) (Reg 131 = 0x40) (Reg 132 = 0x00) (Reg 133 = 0x00) (Reg 134 = 0x00) (Reg 135 = 0x40) (Reg 136 = 0x00) (Reg 137 = 0x00) (Reg 138 = 0x00) (Reg 139 = 0xb0) (Reg 140 = 0x63) (Reg 141 = 0x67) (Reg 142 = 0x0a) (Reg 143 = 0x00) (Reg 144 = 0x00) (Reg 145 = 0x00) (Reg 146 = 0x00) (Reg 147 = 0x40) (Reg 148 = 0x43) (Reg 149 = 0x49) (Reg 150 = 0x53) (Reg 151 = 0x43)


OL-13669-03



(Reg 152 = 0x4f) (Reg 153 = 0x2d) (Reg 154 = 0x53) (Reg 155 = 0x55) (Reg 156 = 0x4d) (Reg 157 = 0x49) (Reg 158 = 0x54) (Reg 159 = 0x4f) (Reg 160 = 0x4d) (Reg 161 = 0x4f) (Reg 162 = 0x20) (Reg 163 = 0x20) (Reg 164 = 0xc0) (Reg 165 = 0x00) (Reg 166 = 0x00) (Reg 167 = 0x5f) (Reg 168 = 0x53) (Reg 169 = 0x58) (Reg 170 = 0x50) (Reg 171 = 0x33) (Reg 172 = 0x31) (Reg 173 = 0x30) (Reg 174 = 0x31) (Reg 175 = 0x4e) (Reg 176 = 0x56) (Reg 177 = 0x2d) (Reg 178 = 0x43) (Reg 179 = 0x31) (Reg 180 = 0x20) (Reg 181 = 0x20) (Reg 182 = 0x20) (Reg 183 = 0x20) (Reg 184 = 0x43) (Reg 185 = 0x20) (Reg 186 = 0x66) (Reg 187 = 0x58) (Reg 188 = 0x0f) (Reg 189 = 0xa0) (Reg 190 = 0x46) (Reg 191 = 0xbe) (Reg 192 = 0x7d) (Reg 193 = 0x96) (Reg 194 = 0x08) (Reg 195 = 0x00) (Reg 196 = 0x45) (Reg 197 = 0x43) (Reg 198 = 0x4c) (Reg 199 = 0x31) (Reg 200 = 0x32) (Reg 201 = 0x30) (Reg 202 = 0x37) (Reg 203 = 0x30) (Reg 204 = 0x31) (Reg 205 = 0x4c) (Reg 206 = 0x32) (Reg 207 = 0x20) (Reg 208 = 0x20) (Reg 209 = 0x20) (Reg 210 = 0x20) (Reg 211 = 0x20) (Reg 212 = 0x30) (Reg 213 = 0x38) (Reg 214 = 0x30) (Reg 215 = 0x32) (Reg 216 = 0x32) (Reg 217 = 0x37) (Reg 218 = 0x44) (Reg 219 = 0x30) (Reg 220 = 0x08) (Reg 221 = 0x60) (Reg 222 = 0x70) (Reg 223 = 0xb7) (Reg 224 = 0x00) (Reg 225 = 0x00) (Reg 226 = 0x0b) (Reg 227 = 0xd0) (Reg 228 = 0xb4) (Reg 229 = 0xd7) (Reg 230 = 0x01) (Reg 231 = 0x6d) (Reg 232 = 0x35) (Reg 233 = 0xbd) (Reg 234 = 0x2c) (Reg 235 = 0x22) (Reg 236 = 0xe9) (Reg 237 = 0xe2) (Reg 238 = 0x49) (Reg 239 = 0xc8) (Reg 240 = 0xea) (Reg 241 = 0x6a) (Reg 242 = 0x2e) (Reg 243 = 0x00) (Reg 244 = 0x00) (Reg 245 = 0x00) (Reg 246 = 0x00) (Reg 247 = 0x00) (Reg 248 = 0x00) (Reg 249 = 0x00) (Reg 250 = 0x00) (Reg 251 = 0x00) (Reg 252 = 0xe6) (Reg 253 = 0x39) (Reg 254 = 0x8b) (Reg 255 = 0x6e)

Example: show controllers TenGigE bert Command

RP/0/RSP0/CPU0:Router# show controllers TenGigE 0/6/0/2 bertBERT status for TenGigE0/6/0/2:

BERT State : DISABLEDTest Pattern : None test patternTime Remaining : 0Time Interval : 0

The following example shows sample output for the show controllers TenGigE bert command that is unsupported on the Cisco CRS 14-Port or Cisco CRS 20-Port 10-Gigabit Ethernet LAN/WAN-PHY Interface Module:

RP/0/RP0/CPU0:Router# show controllers TenGigE 0/1/0/0 bertThu Oct 7 18:26:01.108 ESTCommand not supported on this interface

RP/0/RSP0/CPU0:router#show controllers TenGigE 0/6/0/2 controlManagement information for interface TenGigE0/6/0/2:

Port number: 2Bay number: 0Interface handle: 0x100000c0

Config: Auto-negotiation: Configuration not supported (Off) Carrier delay (up): Not configured Carrier delay (down): Not configured Speed: Configuration not supported (10Gbps) Duplex: Configuration not supported (Full Duplex) Flow Control: Not configured (None) IPG: Not configured (standard (12)) Loopback: Not configured (None)


OL-13669-03



MTU: Not configured Soft Bandwidth: Not configured


Cached driver state: MTU: 1522 bytes Burnt-in MAC address: 001d.353b.975e

Bundle settings: Aggregated: No Bundle MTU: 1514 bytes Bundle MAC address: 001d.353b.975e






The following example shows sample output for the show controllers TenGigE control command for the Cisco CRS 14-Port 10-Gigabit Ethernet LAN/WAN-PHY Interface Module:

RP/0/RP0/CPU0:Router# show controllers TenGigE 0/1/0/0 control

Thu Oct 7 18:26:11.815 ESTManagement information for interface TenGigE0/1/0/0:

Port number: 0Bay number: 0Interface handle: 0x1180200

Config: Auto-negotiation: Configuration not supported (Off) Carrier delay (up): Not configured Carrier delay (down): Not configured Speed: Configuration not supported (10Gbps) Duplex: Configuration not supported (Full Duplex) Flow Control: Not configured (None)


OL-13669-03



IPG: Not configured (standard (12)) Loopback: Not configured (None) MTU: Not configured Bandwidth: Not configured BER-SD Threshold: Configuration not supported --> This field is new BER-SD Report: Configuration not supported --> This field is new BER-SF Threshold: Configuration not supported --> This field is new BER-SF Report: Configuration not supported --> This field is new BER-SF Signal Remote Failure: Configuration not supported --> This field is new

Driver constraints: Min MTU: 64 bytes Max MTU: 9600 bytes Max speed: 10Gbps Interface type: TenGigE Management interface: No Promiscuous mode: Yes Default carrier delay up (auto-neg on): 0 ms --> This field is new Default carrier delay down (auto-neg on): 0 ms --> This field is new Default carrier delay up (auto-neg off): 0 ms --> This field is new Default carrier delay down (auto-neg off): 0 ms --> This field is new Allowed config mask: 0x27b

Cached driver state: MTU: 1522 bytes Burnt-in MAC address: 0014.f294.6776

Operational carrier delay: --> This section is new Carrier delay (up): 0 ms Carrier delay (down): 0 ms

Bundle settings: Aggregated: No Bundle MTU: 1514 bytes Bundle MAC address: 0014.f294.6776






Example: show controllers TenGigE internal CommandRP/0/RSP0/CPU0:Router# show controllers TenGigE 0/4/0/0 internal


OL-13669-03



Port Number : 0 Port Type : 10GE Transport mode : LAN BIA MAC addr : 001b.53ff.a780Oper. MAC addr : 001b.53ff.a780Port Available : trueStatus polling is : enabledStatus events are : enabledI/F Handle : 0x0c000040Cfg Link Enabled : tx/rx enabledH/W Tx Enable : yesMTU : 9112H/W Speed : 10 Gbps H/W Duplex : Full H/W Loopback Type : None H/W FlowCtrl type : None H/W AutoNeg Enable: Off H/W Link Defects : (0x0000) None Link Up : yesLink Led Status : Link upSymbol errors : 255Serdes version : 14.42Input good underflow : 0Input ucast underflow : 0Output ucast underflow : 0Input unknown opcode underflow: 0Pluggable Present : yesPluggable Type : 10GBASE-LR Pluggable Compl. : CompliantPluggable Type Supp.: SupportedPluggable PID Supp. : SupportedPluggable Scan Flg: false

The following example shows sample output for the show controllers TenGigE internal command for the Cisco CRS 14-Port 10-Gigabit Ethernet LAN/WAN-PHY Interface Module:

RP/0/RP0/CPU0:Router# show controllers TenGigE 0/1/0/0 internalThu Oct 7 18:27:01.022 EST


Port Power Used State 00 2500 mW XFP Inserted and Powered On 01 2500 mW XFP Inserted and Powered On 02 1500 mW XFP Inserted and Powered On 03 2500 mW XFP Inserted and Powered On 04 2500 mW XFP Inserted and Powered On 05 1500 mW XFP Inserted and Powered On 06 2500 mW XFP Inserted and Powered On 07 2500 mW XFP Inserted and Powered On 08 2500 mW XFP Inserted and Powered On 09 2500 mW XFP Inserted and Powered On 10 2500 mW XFP Inserted and Powered On 11 2500 mW XFP Inserted and Powered On 12 2500 mW XFP Inserted and Powered On 13 2500 mW XFP Inserted and Powered On

Example: show controllers TenGigE mac Command

The following example shows sample output for the show controllers TenGigE mac command for the Cisco CRS 14-Port 10-Gigabit Ethernet LAN/WAN-PHY Interface Module:


OL-13669-03



RP/0/RP0/CPU0:Router# show controllers TenGigE 0/1/0/0 mac Thu Oct 7 18:27:34.289 EST

Operational address: 0014.f294.6776Burnt-in address: 0014.f294.6776

PLA 0 port 0 MAC enabled Rx MAC disabledAdministrative state: Forced Remote faultOperational state: Remote fault

0 HSRP/VRRP MAC addresses

VLAN Ethertype: 0x8100QinQ Ethertype: 0x88a8MTP Ethertype: 0x88e7

4 VLAN UIDB entriesVLAN1 VLAN2 Packet Type Flags UIDB Result Flags 0 0 VLAN 1 VLAN 0 0 ARPA 1 ARPA 0 0 SAP 1 SAP 0 0 1 SNAP

Example: show controllers TenGigE phy Command

The following example shows sample output for the show controllers TenGigE phy command for the Cisco CRS 14-Port 10-Gigabit Ethernet LAN/WAN-PHY Interface Module:

RP/0/RP0/CPU0:router#show controllers TenGigE 0/1/0/0 phyThu Oct 7 18:27:51.884 EST

802.3ae Sections================

PMA/PMD Previous Alarm Status: PMA/PMD NOT Locked to Local Signal PMA/PMD Local Fault SR Ability Loopback Ability Rx Local Fault Current Alarm Status: PMA/PMD NOT Locked to Local Signal PMA/PMD Local Fault SR Ability Loopback Ability Rx Local Fault

PCS Previous Alarm Status: PCS Rx Link DOWN PCS Local Fault Detected PCS Rx Local Fault Detected PCS Rx NOT Block Locked PCS Rx Link Status DOWN PCS Error'd Block Counts: 0 PCS BER Counts: 0 PCS has NO Block Lock Current Alarm Status: PCS Rx Link DOWN PCS Local Fault Detected PCS Rx Local Fault Detected PCS Rx NOT Block Locked PCS Rx Link Status DOWN


OL-13669-03



PCS Error'd Block Counts: 0 PCS BER Counts: 0 PCS has NO Block Lock

WIS: HW In LAN Mode - No Info

XFP General Info:=================

UDI Checking: DisabledPHY/XFP Status: XFP Not UDI Compliant XFP is Working as expected

XFP Info:=========Max Power Dissipation: 2500 mW

XFP Type: 10GBASE-LRVendor Name: CISCO-SUMITOMO Vendor Part Number: SXP3101NV-C1 Vendor OUI: 0x00-0x00-0x5fVendor Hardware Revision: C Vendor Serial number: ECL120701L2 Date Code (yy/mm/dd): 08/02/27Lot Code: D0

Cisco PID: XFP-10GLR-OC192SR Cisco VID: V02 Cisco PN: 10-1989-02

ID: XFPExtended ID: 0x58 TX ref clock input is not required CDP is supported Power Level 2 (2.5W max. power)Minimum bit rate is 9900 MBits/s.Maximum bit rate is 10300 MBits/s.

XFP Detail Info:================

Temp: 32.223Tx bias: 0.0 mATx power: 0.0 mW (-40 dBm)Rx power: 0.33 mW (-24 dBm)AUX 1: +3.3V Supply Voltage: 0x70AUX 2: Auxiliary monitoring not implemented: 0x0

XFP Status: enabled. laser is enabled MOD NR is not ready is powered off doesn't have interrupt(s) has LOS data is ready TX path is ready TX laser is not in fault condition TX path CDR is locked RX path is not ready RX path CDR is not locked


OL-13669-03



Alarms: Low RX power alarm

Warnings: Low RX power warning

THRESHOLDS High Alarm Low Alarm High Warning Low Warng Temperature C 80.0 -15.0 75.0 -10.0 Voltage V 000.0000 000.0000 000.0000 000.000 Bias Current mA 100.0000 000.0000 080.0000 000.000 Transmit power mW 015.8480 001.2580 010.0000 001.990 Receive power mW 022.3870 000.1810 014.1250 000.280

Example: show controllers GigabitEthernet regs CommandRP/0/RSP0/CPU0:Router# show controllers GigabitEthernet 0/1/0/1 regs

MAC Registers for port: 1 GE MAC CFG (#0954): 704c5e5a GPCS Config (#0147): 00000f08 GPCS Status (#0236): 000000ca GSERDES Status (#0237): 0007fe09

Example: show controllers TenGigE regs CommandRP/0/RSP0/CPU0:Router# show controllers TenGigE 0/4/0/0 regs

MAC Registers for port: 0 CONFIG1 (#1034): 03100a1a CONFIG2 (#1035): 040c2398 CONTROL (#1036): 00000000 ADDRESS_LOW (#1037): 53ffa780 ADDRESS_HIGH (#1038): 0000001b MII_MGMT_CONFIG (#1039): 00000007 MII_MGMT_CMD (#1040): 00000000 MII_MGMT_ADDRESS (#1041): 00000000 MII_MGMT_DATA (#1042): 40000000 STAT_CONFIG (#1043): 00000007 MASK_R (#1044): 00000000 MASK_T (#1045): 00000000 COMP (#1046): 00100d24 MAC_CONFIG (#1047): ffffffff INTERRUPT_C (#1048): 00000000

The following example shows sample output for the show controllers TenGigE regs command for the Cisco CRS 14-Port 10-Gigabit Ethernet LAN/WAN-PHY Interface Module:

RP/0/RP0/CPU0:Router# show controllers TenGigE 0/1/0/0 regsThu Oct 7 18:28:22.640 EST

LASI 802.3ae Registers:=======================Previous: LASI Status = 0x000c Rx Alarm Status = 0x0018 Tx Alarm Status = 0x0000Current: LASI Status = 0x000c Rx Alarm Status = 0x0018 Tx Alarm Status = 0x0000

PMA/PMD 802.3ae Registers:============================Control = 0x2040 Status = 0x0082 Dev ID 0 = 0x0043 Dev ID 1 = 0xa400Speed Ability = 0x0001 Devices 1 = 0x001e Devices 2 = 0x0000 Control 2 = 0x0007 Status 2 = 0xb581Tx Disable = 0x0000 Rx Signal Detect = 0x0000OUI 0 = 0x0000 OUI 1 = 0x0000


OL-13669-03



Current: Status = 0x0082 Status 2 = 0xb581

WIS 802.3ae Registers:======================Control = 0x2040 Status = 0x0082 Dev ID 0 = 0x0043 Dev ID 1 = 0xa400Speed Ability = 0x0001 Devices 1 = 0x001e Devices 2 = 0x0000Control 2 = 0x0000 Status 2 = 0x8003 Status 3 = 0x0048Test Pattern Error Counter = 0x0000 Far End BLock Error Counter = 0x0000J1 TX 1 = 0x0000 J1 TX 2 = 0x0000 J1 TX 3 = 0x0000 J1 TX 4 = 0x0000 J1 TX 5 = 0x0000 J1 TX 6 = 0x0000 J1 TX 7 = 0x0000 J1 TX 8 = 0x8900J1 RX 1 = 0x0000 J1 RX 2 = 0x0000 J1 RX 3 = 0x0000 J1 RX 4 = 0x0000 J1 RX 5 = 0x0000 J1 RX 6 = 0x0000 J1 RX 7 = 0x0000 J1 RX 8 = 0x0000Far End BIP Error 0 = 0x0000 Far End BIP Error 1 = 0x0000Line BIP Error 0 = 0x0000 Line BIP Error 1 = 0x0000Path BIP Error Count = 0x0000 Section BIP Error Count = 0x0000J0 Tx 1 = 0x0000 J0 Tx 2 = 0x0000 J0 Tx 3 = 0x0000 J0 Tx 4 = 0x0000J0 Tx 5 = 0x0000 J0 Tx 6 = 0x0000 J0 Tx 7 = 0x0000 J0 Tx 8 = 0x8900J0 Rx 1 = 0x0000 J0 Rx 2 = 0x0000 J0 Rx 3 = 0x0000 J0 Rx 4 = 0x0000J0 Rx 5 = 0x0000 J0 Rx 6 = 0x0000 J0 Rx 7 = 0x0000 J0 Rx 8 = 0x0000Current: Status = 0x0082 Status 2 = 0x8003 Status 3 = 0x0048

PCS 802.3ae Registers:======================Control = 0x2040 Status = 0x0082 Dev ID 0 = 0x0043 Dev ID 1 = 0xa400Speed Ability = 0x0001 Devices 1 = 0x001e Devices 2 = 0x0000 Control 2 = 0x0000 Status 2 = 0x8405PKG ID 0 = 0x0000 PKG ID 1 = 0x0000Base X Status = 0x0000 Base X Control = 0x0000Base R Status 1 = 0x0004 Base R Status 2 = 0x0000Base R jitter seed a0 = 0x0000 Base R jitter seed a1 = 0x0000Base R jitter seed a2 = 0x0000 Base R jitter seed a3 = 0x0000Base R jitter seed b0 = 0x0000 Base R jitter seed b1 = 0x0000Base R jitter seed b2 = 0x0000 Base R jitter seed b3 = 0x0000Base R jitter test control = 0x0000 Base R jitter test counter = 0x0000Current: Status = 0x0082 Status 2 = 0x8405 Base R 1 = 0x0004 Base R 2 = 0x0000

PHY XS 802.3ae Registers:=========================Control = 0x2040 Status = 0x0006Dev ID 0 = 0x0043 Dev ID 1 = 0xa400Speed Ability = 0x0001 Devices 1 = 0x001e Devices 2 = 0x0000Status 2 = 0x8000 PKG ID 0 = 0x0000 PKG ID 1 = 0x0000Lane Status = 0x1c0f Test Control = 0x0000Current: Status = 0x0006 Status 2 = 0x8000 Lane Status = 0x1c0f

XFP Register Info (MSA):========================(Reg 000 = 0x06) (Reg 001 = 0x00) (Reg 002 = 0x50) (Reg 003 = 0x00) (Reg 004 = 0xf1) (Reg 005 = 0x00) (Reg 006 = 0x4b) (Reg 007 = 0x00) (Reg 008 = 0xf6) (Reg 009 = 0x00) (Reg 010 = 0x00) (Reg 011 = 0x00) (Reg 012 = 0x00) (Reg 013 = 0x00) (Reg 014 = 0x00) (Reg 015 = 0x00) (Reg 016 = 0x00) (Reg 017 = 0x00) (Reg 018 = 0xc3) (Reg 019 = 0x50) (Reg 020 = 0x00) (Reg 021 = 0x00) (Reg 022 = 0x9c) (Reg 023 = 0x40) (Reg 024 = 0x00) (Reg 025 = 0x00) (Reg 026 = 0x3d) (Reg 027 = 0xe8) (Reg 028 = 0x04) (Reg 029 = 0xea) (Reg 030 = 0x27) (Reg 031 = 0x10) (Reg 032 = 0x07) (Reg 033 = 0xcb) (Reg 034 = 0x57) (Reg 035 = 0x73) (Reg 036 = 0x00) (Reg 037 = 0xb5) (Reg 038 = 0x37) (Reg 039 = 0x2d) (Reg 040 = 0x01) (Reg 041 = 0x20) (Reg 042 = 0x00) (Reg 043 = 0x00) (Reg 044 = 0x00) (Reg 045 = 0x00) (Reg 046 = 0x00) (Reg 047 = 0x00) (Reg 048 = 0x00) (Reg 049 = 0x00) (Reg 050 = 0x00) (Reg 051 = 0x00) (Reg 052 = 0x00) (Reg 053 = 0x00) (Reg 054 = 0x00) (Reg 055 = 0x00) (Reg 056 = 0x00) (Reg 057 = 0x00) (Reg 058 = 0x00) (Reg 059 = 0x00) (Reg 060 = 0x00) (Reg 061 = 0x00) (Reg 062 = 0x00) (Reg 063 = 0x00) (Reg 064 = 0x00) (Reg 065 = 0x00) (Reg 066 = 0x00) (Reg 067 = 0x00)


OL-13669-03



(Reg 068 = 0x00) (Reg 069 = 0x00) (Reg 070 = 0x00) (Reg 071 = 0x00) (Reg 072 = 0x00) (Reg 073 = 0x00) (Reg 074 = 0x00) (Reg 075 = 0x00) (Reg 076 = 0x00) (Reg 077 = 0x00) (Reg 078 = 0x00) (Reg 079 = 0x00) (Reg 080 = 0x00) (Reg 081 = 0x40) (Reg 082 = 0x00) (Reg 083 = 0x40) (Reg 084 = 0x1e) (Reg 085 = 0x00) (Reg 086 = 0x00) (Reg 087 = 0x00) (Reg 088 = 0x00) (Reg 089 = 0x00) (Reg 090 = 0x00) (Reg 091 = 0x00) (Reg 092 = 0x00) (Reg 093 = 0x00) (Reg 094 = 0x00) (Reg 095 = 0x00) (Reg 096 = 0x20) (Reg 097 = 0xdf) (Reg 098 = 0x00) (Reg 099 = 0x00) (Reg 100 = 0x00) (Reg 101 = 0x00) (Reg 102 = 0x00) (Reg 103 = 0x00) (Reg 104 = 0x00) (Reg 105 = 0x21) (Reg 106 = 0x7e) (Reg 107 = 0x44) (Reg 108 = 0x00) (Reg 109 = 0x00) (Reg 110 = 0x32) (Reg 111 = 0x18) (Reg 112 = 0x00) (Reg 113 = 0x00) (Reg 114 = 0x00) (Reg 115 = 0x00) (Reg 116 = 0x00) (Reg 117 = 0x00) (Reg 118 = 0x00) (Reg 119 = 0x00) (Reg 120 = 0x00) (Reg 121 = 0x00) (Reg 122 = 0x00) (Reg 123 = 0x00) (Reg 124 = 0x00) (Reg 125 = 0x00) (Reg 126 = 0x00) (Reg 127 = 0x01)

(Reg 128 = 0x06) (Reg 129 = 0x58) (Reg 130 = 0x07) (Reg 131 = 0x40) (Reg 132 = 0x00) (Reg 133 = 0x00) (Reg 134 = 0x00) (Reg 135 = 0x40) (Reg 136 = 0x00) (Reg 137 = 0x00) (Reg 138 = 0x00) (Reg 139 = 0xb0) (Reg 140 = 0x63) (Reg 141 = 0x67) (Reg 142 = 0x0a) (Reg 143 = 0x00) (Reg 144 = 0x00) (Reg 145 = 0x00) (Reg 146 = 0x00) (Reg 147 = 0x40) (Reg 148 = 0x43) (Reg 149 = 0x49) (Reg 150 = 0x53) (Reg 151 = 0x43) (Reg 152 = 0x4f) (Reg 153 = 0x2d) (Reg 154 = 0x53) (Reg 155 = 0x55) (Reg 156 = 0x4d) (Reg 157 = 0x49) (Reg 158 = 0x54) (Reg 159 = 0x4f) (Reg 160 = 0x4d) (Reg 161 = 0x4f) (Reg 162 = 0x20) (Reg 163 = 0x20) (Reg 164 = 0xc0) (Reg 165 = 0x00) (Reg 166 = 0x00) (Reg 167 = 0x5f) (Reg 168 = 0x53) (Reg 169 = 0x58) (Reg 170 = 0x50) (Reg 171 = 0x33) (Reg 172 = 0x31) (Reg 173 = 0x30) (Reg 174 = 0x31) (Reg 175 = 0x4e) (Reg 176 = 0x56) (Reg 177 = 0x2d) (Reg 178 = 0x43) (Reg 179 = 0x31) (Reg 180 = 0x20) (Reg 181 = 0x20) (Reg 182 = 0x20) (Reg 183 = 0x20) (Reg 184 = 0x43) (Reg 185 = 0x20) (Reg 186 = 0x66) (Reg 187 = 0x58) (Reg 188 = 0x0f) (Reg 189 = 0xa0) (Reg 190 = 0x46) (Reg 191 = 0xbe) (Reg 192 = 0x7d) (Reg 193 = 0x96) (Reg 194 = 0x08) (Reg 195 = 0x00) (Reg 196 = 0x45) (Reg 197 = 0x43) (Reg 198 = 0x4c) (Reg 199 = 0x31) (Reg 200 = 0x32) (Reg 201 = 0x30) (Reg 202 = 0x37) (Reg 203 = 0x30) (Reg 204 = 0x31) (Reg 205 = 0x4c) (Reg 206 = 0x32) (Reg 207 = 0x20) (Reg 208 = 0x20) (Reg 209 = 0x20) (Reg 210 = 0x20) (Reg 211 = 0x20) (Reg 212 = 0x30) (Reg 213 = 0x38) (Reg 214 = 0x30) (Reg 215 = 0x32) (Reg 216 = 0x32) (Reg 217 = 0x37) (Reg 218 = 0x44) (Reg 219 = 0x30) (Reg 220 = 0x08) (Reg 221 = 0x60) (Reg 222 = 0x70) (Reg 223 = 0xb7) (Reg 224 = 0x00) (Reg 225 = 0x00) (Reg 226 = 0x0b) (Reg 227 = 0xd0) (Reg 228 = 0xb4) (Reg 229 = 0xd7) (Reg 230 = 0x01) (Reg 231 = 0x6d) (Reg 232 = 0x35) (Reg 233 = 0xbd) (Reg 234 = 0x2c) (Reg 235 = 0x22) (Reg 236 = 0xe9) (Reg 237 = 0xe2) (Reg 238 = 0x49) (Reg 239 = 0xc8) (Reg 240 = 0xea) (Reg 241 = 0x6a) (Reg 242 = 0x2e) (Reg 243 = 0x00) (Reg 244 = 0x00) (Reg 245 = 0x00) (Reg 246 = 0x00) (Reg 247 = 0x00) (Reg 248 = 0x00) (Reg 249 = 0x00) (Reg 250 = 0x00) (Reg 251 = 0x00) (Reg 252 = 0xe6) (Reg 253 = 0x39) (Reg 254 = 0x8b) (Reg 255 = 0x6e)

Example: show controllers TenGigE stats CommandRP/0/RSP0/CPU0:Router# show controllers TenGigE 0/4/0/0 stats

Statistics for interface TenGigE0/4/0/0 (cached values):


Input total packets = 106713557 Input 802.1Q frames = 0 Input pause frames = 0 Input pkts 64 bytes = 103907216 Input pkts 65-127 bytes = 2494185


OL-13669-03



Input pkts 128-255 bytes = 3410 Input pkts 256-511 bytes = 3406 Input pkts 512-1023 bytes = 2 Input pkts 1024-1518 bytes = 0 Input pkts 1519-Max bytes = 305338










RP/0/RSP0/CPU0:router#

RP/0/RSP0/CPU0:router#show controllers TenGigE 0/4/0/0 xgxs



OL-13669-03



RP/0/RSP0/CPU0:Router# show controllers TenGigE 0/4/0/0 statsStatistics for interface TenGigE0/4/0/0 (cached values):










Output drop underrun = 0 Output drop abort = 0


OL-13669-03



Output drop other = 0


The following example shows sample output for the show controllers TenGigE stats command for the Cisco CRS 14-Port 10-Gigabit Ethernet LAN/WAN-PHY Interface Module:

RP/0/RP0/CPU0:Router# show controllers TenGigE 0/1/0/0 stats

Thu Oct 7 18:29:16.631 ESTStatistics for interface TenGigE0/1/0/0 (cached values):




Input drop overrun = 0 Input drop abort = 0 Input drop invalid VLAN = 0 Input drop invalid DMAC = 0 Input drop invalid encap = 0 Input drop other = 0




Output total packets = 0 Output 802.1Q frames = 0 Output pause frames = 0 Output pkts 64 bytes = 0 Output pkts 65-127 bytes = 0 Output pkts 128-255 bytes = 0 Output pkts 256-511 bytes = 0 Output pkts 512-1023 bytes = 0


OL-13669-03



Output pkts 1024-1518 bytes = 0 Output pkts 1519-Max bytes = 0




Example: show controllers TenGigE xgxs CommandRP/0/RSP0/CPU0:Router# show controllers TenGigE 0/4/0/0 xgxs


The following example shows sample output for the show controllers TenGigE stats command for the Cisco CRS 14-Port 10-Gigabit Ethernet LAN/WAN-PHY Interface Module:

RP/0/RP0/CPU0:Router# show controllers TenGigE 0/1/0/0 xgxs Thu Oct 7 18:30:03.732 ESTDTE XGXS Current Alarm Status: XGXS Lanes All Synchronized XGXS Lanes AlignedPHY XGXS Previous Alarm Status: NO XGXS Local Fault TX Link UP Current Alarm Status: NO XGXS Local Fault TX Link UP

Example: show controllers HundredGigE phy Command

The following example shows sample output for the show controllers HundredGigE phy command for the Cisco CRS 1-Port 100-Gigabit Ethernet Interface Module:

RP/0/RP0/CPU0:router#show controllers HundredGigE 0/6/0/0 phyThu Oct 7 09:43:10.274 EST802.3ba PCS Previous PCS Alarms:

Current PCS Status: PCS is able to support 100GBASE-R PCS is NOT Block Locked PCS Rx Link Status is DOWN PCS Errored Block Counts: 0 PCS Sync Header Error Counts: 0Serdes section:===============

All of 10 RX serial inputs detects loss of signal.All of 10 cleanup PLL phase detectors are unlocked.All of 10 clock multiplication units are locked.


OL-13669-03



All of 10 clock/data recovery units are locked.None of 10 TX FIFO has underflow/overflow condition.None of 10 RX FIFO has underflow/overflow condition.

CFP section:==============

CFP General Information:

Module Identifier: CFP Ethernet Application Code: 100GE-LR4 Module State: Low Power Power Class: 3 Maximum Power Consumption: 23000 mW

CFP Vendor Information:

Vendor Name: FINISAR CORP. Vendor PN: FTLC1181RDNS-C1 Vendor SN: C22CS58 Vendor OUI: 0x0-0x90-0x65 Lot Code: 00 DATE CODE(YY/MM/DD): 2010/08/05 Hardware Version: 1.3 Firmware Version: 1.5

CFP UDI Information:

UDI Compliant: Yes CISCO PID: CFP-100G-LR4 CISCO VID: VES1

CFP Detail Information: … Module Analog A/D value:

Power supply voltage : 3.2915 V Temperature : 16.7917 degC Network lane A/D value:

Lane 0 Tx power: 0.0 mW (-40 dBm) Lane 1 Tx power: 0.0 mW (-40 dBm) Lane 2 Tx power: 0.0 mW (-40 dBm) Lane 3 Tx power: 0.0 mW (-40 dBm)

Lane 0 Rx power: 0.0 mW (-40 dBm) Lane 1 Rx power: 0.0 mW (-40 dBm) Lane 2 Rx power: 0.0 mW (-40 dBm) Lane 3 Rx power: 0.0 mW (-40 dBm)


OL-13669-03


Power Module Changes

Power Module ChangesThe following command has been updated for the Cisco CRS-3:

• “show controllers TenGigE” section on page 72


OL-13669-03


show controllers TenGigE

show controllers TenGigE

RP/0/RP0/CPU0:router#sh controllers TenGigE 0/1/0/0 internal Wed Oct 6 15:43:00.305 EST


Port Power Used State 00 2500 mW XFP Inserted and Powered On 01 0000 mW No XFP Inserted 02 2500 mW XFP Inserted and Powered On 03 0000 mW No XFP Inserted 04 2500 mW XFP Inserted and Powered On 05 0000 mW No XFP Inserted 06 1500 mW XFP Inserted and Powered On 07 1500 mW XFP Inserted and Powered On 08 2500 mW XFP Inserted and Powered On 09 1500 mW XFP Inserted and Powered On 10 3500 mW XFP Inserted and Powered On 11 3500 mW XFP Inserted and Powered On 12 3500 mW XFP Inserted and Powered On 13 2500 mW XFP Inserted and Powered On


OL-13669-03


List of QoS Changes for Cisco CRS Series Modular Services Card 140G (CRS-MSC-140G) Upgrade Doc

List of QoS Changes for Cisco CRS Series Modular Services Card 140G (CRS-MSC-140G) Upgrade Doc

Important Notes: QoS Configuration ChangesOn the Cisco CRS Series Modular Services Card 40G (CRS-MSC-40G), a priority action can be configured with or without a police action in the same class. Example 1 shows a valid configuration on the CRS-MSC-40G that includes only a priority action:

Example 1 Class Configured With Priority Action Only (CRS-MSC-40G)

policy-map prio_only_policy class prec1 priority level 1 ! class class-default ! end-policy-map!

Modifying CRS-MSC-40G QoS Configurations for CRS-MSC-140GOn the Cisco CRS Series Modular Services Card 140G (CRS-MSC-140G), a police action must be configured in the same class as the priority action. A class configuration that includes a priority action but no police action is not valid. Such a configuration is rejected.

To use existing CRS-MSC-40G QoS configurations on the CRS-MSC-140G, add a police action to all classes that have a priority action. In Example 2, the class configuration in Example 1 is modified to include a police action:

Example 2 Class Configured With Priority Action and Police Action (CRS-MSC-140G

policy-map prio_and_police_policy class prec1 priority level 1 police rate percent 20 ! ! class class-default ! end-policy-map!


OL-13669-03


QoS Command Changes

QoS Command Changes

priority (QoS)To assign a priority to a class of traffic belonging to a policy map, use the priority command in policy map class configuration mode. To remove a previously specified priority for a class, use the no form of this command.

priority [level priority-level]

no priority

Syntax Description

Command Default If a priority action is not configured in a class, traffic in that class is not serviced with strict priority— it is serviced after priority classes are serviced.

Command Modes Policy map class configuration

Command History

Usage Guidelines To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The priority command configures low-latency queueing (LLQ), providing strict priority queueing (PQ). Strict PQ allows delay-sensitive data such as voice to be dequeued and sent before packets in other queues are dequeued. When a class is marked as high priority using the priority command, we recommend that you configure a policer to limit the priority traffic. This policer ensures that the priority traffic does not starve all other traffic on the line card, which protects low-priority traffic from starvation. Use the police rate to explicitly configure the policer.

The priority command sets up classes based on a variety of match criteria (such as match precedence, match dscp, or match exp) and assigns a priority to them.

The bandwidth and priority commands cannot be used in the same class, within the same policy map. These commands can be used together in the same policy map.

level priority-level (Optional) Sets the class priority level value. Values are 1 or 2; default level is 1. Level 1 priority traffic is served first.


Release 2.0 This command was introduced on the Cisco CRS-1.

Release 4.0.0.T The level keyword was added.




OL-13669-03


priority (QoS)

Within a policy map, you can give one or more classes priority status. When multiple classes within a single policy map are configured as priority classes, all traffic from these classes at same priority level is queued to the same, single priority queue. There is one priority queue per level in a group.

Modifying CRS-MSC-40G QoS Configurations for CRS-MSC-140G

On the Cisco CRS Series Modular Services Card 40G (CRS-MSC-40G), a priority action can be configured with or without a police action in the same class.

On the Cisco CRS Series Modular Services Card 140G (CRS-MSC-140G), a police action must be configured in the same class as the priority action. A class configuration that includes a priority action but no police action is not valid. Such a configuration is rejected.

To use existing CRS-MSC-40G QoS configurations on the CRS-MSC-140G, add a police action to all classes that have a priority action.

Priority assignment at the group level for an egress interface policy is not supported.

Task ID

Examples The following example shows how to configure priority queuing for the policy map named policy1:

RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# priority level 1RP/0/RP0/CPU0:router(config-pmap-c)# police rate percent 20RP/0/RP0/CPU0:router(config-pmap-c)# class class-defaultRP/0/RP0/CPU0:router(config-pmap-c)# end-policy-map

Related Commands

Task ID Operations

qos read, write

Command Description

bandwidth (QoS) Specifies or modifies the minimum bandwidth allocated for a class belonging to a policy map.

policy-map Creates or modifies a policy map that can be attached to one or more interfaces to specify a service policy.

show policy-map interface Displays the configuration of all classes configured for all service policies on the specified interface.


OL-13669-03


QoS Features Changes


General • Layer 2 VPN QoS features are not supported.

• Cisco CRS Series Modular Services Card 140G (CRS-MSC-140G) uses "layer-all" accounting. For Ethernet interfaces, this translates to 20 bytes of Layer 1 overhead in addition to the Layer 2 overhead. Cisco CRS Series Modular Services Card 40G (CRS-MSC-40G) does Layer 3 QoS accounting for ingress queueing. CRS-MSC-40G does Layer 2 QoS accounting for egress queueing, egress policing, and ingress policing.

Queueing

Changes Common to Ingress and Egress Queuing

• High priority traffic under all ports and groups is serviced before any low priority traffic. This means that the scope of priority assignment at the queue level is global - it is not limited to the parent group (such as on CRS-MSC-40G) or port. This is referred to as high priority propagation, which improves low latency treatment for high priority traffic, such as real-time voice and video traffic.

• Priority assignment at the group level for an egress interface policy is not supported.

• A policer must be configured to limit the traffic entering priority queues.

Ingress Queuing Only

• Maximum number of ingress queues and groups (or virtual ports) on each line card:

– 49,152 low priority queues

– 16,384 virtual high priority queues (up to 1 under each virtual port - same as for CRS-MSC-40G)

– 16,384 groups or virtual ports

• Smallest step size supported is 32 kbps for groups and 32/3 kbps (10.67 kbps) for queues. Step size increases with the rate value. Rounding error does not exceed 0.4 per cent or 8 kbps, whichever is higher.

Egress Queuing Only

• Maximum number of egress queues and groups on each line card:

– 65,536 queues, of which up to 16,384 can be high priority queues

– Up to 1 high priority queue per level under each group (same as for CRS-MSC-40G)

– 16,384 groups

– Two high priority levels are supported.


OL-13669-03



• Minimum bandwidth of a group must be equal to or greater than the sum of queue minimum bandwidths and the police rates of the high priority classes under the group. If the configured value does not meet these requirements, the minimum group bandwidth is automatically increased to satisfy the requirements.

• Oversubscription of minimum bandwidth is permitted. In the event of oversubscription, the actual minimum bandwidth that a group or queue receives is proportional to its configured value.

• Smallest step size supported is 8 kbps for 10 gigabit interfaces and 64 kbps for 100 gigabit interfaces for queues and groups. Step size increases with the rate value. Rounding error does not exceed 0.4 per cent or 8 kbps, whichever is higher.

Policing • 524,288 policers (dual token bucket) are supported.

• 8,192 unique policer parameters (CIR, CBS, PIR, PBS) or profiles are supported. Multiple policers can share a single profile.

• Police rates can be configured in the range of 8 Kbps - 134 Gbps.

• Smallest granularity supported is 8 kbps (for rates up to 8 Mbps). The step size is higher for higher rates but is never greater than 0.2% of the rate value. For very high ratios of PIR/CIR the rounding error can be greater than 0.2%.

• The maximum permitted burst size is 2 MB for rates up to 131 Mbps, and 100 ms for higher rates.

• Burst granularity

– For rates that are less than or equal to 131 Mbps, burst granularity varies from 128 bytes to 16,000 bytes in proportion to the burst value. The worst case step-size is 1.6% of burst value.

– For rates greater than 131 Mbps, the granularity is 1 ms (with the corresponding rate as reference).


OL-13669-03




OL-13669-03

Cisco CRS-1 Carrier Routing System to Cisco CROL-13669-03

A
P P E N D I X A Turbo Boot Procedure
This appendix describes the procedures to perform turbo boot operations and file system disk upgrades from FAT 16 to FAT32.

This is the procedure to use to downgrade your Cisco CRS-3 back to a Cisco CRS-1 instead of the one listed in Chapter 2.

Turbo Boot PrerequisitesBefore performing a turbo boot on a system running Cisco IOS XR software release 4.0.0.T images you must upgrade your ROMMON image to the release 2.01 version

If the Route Processor (RP) ROMMON is a version earlier than version 1.52, upgrade it to version 2.01 or above. Follow the steps provided below.

Turboboot requires an upgrade of ROMMON A and ROMMON B to ROMMON 2.01 because the older ROMMON versions are unable to load the larger IOS-¦-XR 4.0.0.T (or higher) VM files. This has to be done with the external binaries and special hidden commands.

ROMMON Upgrade Instructions

Step 1 Download the tar file (rommon-2.1.tar), untar it on a PC and copy the binaries to disk0:

The following files should be on the flash disk (only the ppc files are required):

• rommon-¦-hfr-¦-ppc7450-¦-sc-¦-dsmp-¦-A.bin

• rommon-¦-hfr-¦-ppc7450-¦-sc-¦-dsmp-¦-B.bin

• rommon-¦-hfr-¦-ppc7455-¦-asmp-¦-A.bin

• rommon-¦-hfr-¦-ppc7455-¦-asmp-¦-B.bin

• rommon-¦-hfr-¦-ppc8255-¦-sp-¦-A.bin

• rommon-¦-hfr-¦-ppc8255-¦-sp-¦-B.bin

• rommon-¦-hfr-¦-ppc8347-¦-sp-¦-A.bin

• rommon-¦-hfr-¦-ppc8347-¦-sp-¦-B.bin

Step 2 Upgrade ROMMON B while in admin mode as shown in the following example :

RP/0/RP0/CPU0:CRS-C#admin Thu Jan 21 14:47:53.694 PST RP/0/RP0/CPU0:CRS-1(admin)#upgrade rommon b all disk0 Thu Jan 21 14:49:16.608 PST

A-1S-3 Carrier Routing System Migration Guide

Appendix A Turbo Boot ProcedureTurbo Boot Prerequisites

Please do not power cycle, reload the router or reset any nodes until all upgrades are completed. Please check the syslog to make sure that all nodes are upgraded successfully. If you need to perform multiple upgrades, please wait for current 13 upgrade to be completed before proceeding to another upgrade. Failure to do so may render the cards under upgrade to be unusable. RP/0/RP0/CPU0:Oct 13 14:00:06.596 : upgrade_daemon[358]: Running rommon upgrade RP/0/RP1/CPU0:Oct 13 14:00:06.600 : upgrade_daemon[358]: Running rommon upgrade SP/0/SM3/SP:Oct 13 14:00:06.657 : upgrade_daemon[130]: Running rommon upgrade [SNIP]

Step 3 Verify that ROMMON B was upgraded successfully by executing the show logging command.

RP/0/RP0/CPU0:CRS-C(admin)#show logging | inc is programmed successfully RP/0/RP0/CPU0:Oct 13 14:00:13.566 : rommon_burner[65770]: %PLATFORM-¦- ROMMON_BURNER-¦-5-¦-progress : ROMMON B is programmed successfully. RP/0/RP0/CPU0:Oct 13 14:00:13.523 : syslog_dev[83]: upgrade_daemon[358]: OK, ROMMON B is programmed successfully. RP/0/RP0/CPU0:Oct 13 14:00:13.580 : syslog_dev[83]: upgrade_daemon[358]: OK, ROMMON B is programmed successfully. [SNIP]

Step 4 Now you can upgrade ROMMON A with the following command from admin mode:

RP/0/RP0/CPU0:CRS-1(admin)#upgrade rommon a all disk0

Step 5 Verify that ROMMON A was upgraded successfully by executing the show logging command.

RP/0/RP0/CPU0:CRS-C(admin)#show logging | inc is programmed successfully RP/0/RP0/CPU0:Oct 13 14:00:13.566 : rommon_burner[65770]: %PLATFORM-¦- ROMMON_BURNER-¦-5-¦-progress : ROMMON A is programmed successfully. RP/0/RP0/CPU0:Oct 13 14:00:13.523 : syslog_dev[83]: upgrade_daemon[358]: OK, ROMMON B is programmed successfully. RP/0/RP0/CPU0:Oct 13 14:00:13.580 : syslog_dev[83]: upgrade_daemon[358]: OK, ROMMON B is programmed successfully. [SNIP]

Note To activate the new ROMMON a reload would be required.

Note To save an additional reload the new ROMMON can be activated together with the turboboot.

Turboboot Instructions

Step 1 Connect to both RP consoles and bring both RPs into ROMMON

RP/0/RP0/CPU0:CRS-1(admin)#config-¦-register 0x0 Tue Oct 12 06:11:29.712 PST Successfully set config-¦-register to 0x0 on node 0/RP0/CPU0 Successfully set config-¦-register to 0x0 on node 0/RP1/CPU0 RP/0/RP0/CPU0:CRS-¦-1(admin)#reload location all

When the system comes back up, take note of the ROMMON version in the pre-loading information. The version should reflect the new updated ROMMON.

PCI1 device[3]: Device ID 0x5618 PCI1 device[3]: Vendor ID 0x14e4 Configuring MPPs ... Configuring PCMCIA slots ... System Bootstrap, Version 2.1(20100723:223432) [CRS-¦-1 ROMMON],

A-2Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

OL-13669-03

Appendix A Turbo Boot ProcedureTurbo Boot Prerequisites

Copyright (c) 1994-¦-2010 by Cisco Systems, Inc.

Acquiring backplane mastership ..... successful Preparing for fan initialization............. ready

Step 2 Configure the ROMMON variables on the standby RP and reset

Rommon1>unset BOOT Rommon2>confreg 0x102 Rommon3>sync Rommon4>reset

This will bring the standby RP in a booting loop. If you turboboot a MC this has to be done on all nonDSC RPs. The RP(s) will remain in the booting loop (mbi hunt) until they receive a MBI confirmation with the remote image to boot from the active RP of the DSC. The MBI confirmation will be received once the active RP on the DSC has booted the mini image. Refer to the next step.

Step 3 Configure the rommon variables on the active RP and boot the vm image.

Rommon1>IP_ADDRESS=<a.b.c.d> Rommon2>IP_SUBNET_MASK=<mask> Rommon3>TFTP_SERVER=<a.b.c.d> Rommon4>DEFAULT_GATEWAY=<a.b.c.d> Rommon5>unset BOOT Rommon6>TURBOBOOT=on,disk0,format Rommon7>sync Rommon8>boot tftp://a.b.c.d/path/hfr-mini-px.vm-4.0.0

Instead of a tftp server disk1 can be specified as well. But this will take significant longer

Warning Do NOT use the option "format”if you migrate to a flash disk formatted with the FAT32 file system or if you have a flash disk formatted with FAT32.

In this case configure the TURBOBOOT variable as follows:

Rommon6>TURBOBOOT=on,disk0

The installation is complete when all nodes on the system are in state "IOS XR RUN" and the standby RP is "NSR-ready”.

Example

RP/0/RP0/CPU0:router#sh red Wed Oct 13 09:33:43.367 UTC

Redundancy information for node 0/RP0/CPU0: ==========================================

Node 0/RP0/CPU0 is in ACTIVE role Partner node (0/RP1/CPU0) is in STANDBY role Standby node in 0/RP1/CPU0 is ready Standby node in 0/RP1/CPU0 is NSR-¦-ready

Reload and boot info ---------------------

RP reloaded Wed Oct 13 09:23:20 2010: 10 minutes ago Active node booted Wed Oct 13 09:23:20 2010: 10 minutes ago Standby node boot Wed Oct 13 09:24:00 2010: 9 minutes ago


OL-13669-03

Appendix A Turbo Boot ProcedureUpgrading Your File System From FAT16 to FAT32

Standby node last went not ready Wed Oct 13 09:33:14 2010: 29 seconds agoStandby node last went ready Wed Oct 13 09:33:15 2010: 28 seconds agoThere have been 0 switch-¦-overs since reload Active node reload "Cause: Turboboot completed successfully" Standby node reload "Cause: MBI-¦-HELLO reloading node on receiving reload notification"

Step 4 When the turboboot installation is complete the optional PIEs can be added and activated from admin mode.

Example

router(admin)# install add source tftp://10.1.1.1/users/bla/ hfr-¦-mcast-¦- px.pie-¦- 4.0.0.T hfr-¦-mgbl-¦-px.pie-¦-4.0.0.T hfr-¦-mpls-¦-px.pie-¦-4.0.0.T hfr-¦- k9sec-¦-px.pie-¦-4.0.0.T hfr-¦- diags-¦-px.pie-¦-4.0.0.T sync

router(admin)# install activate disk0:hfr-¦-mcast-¦-4.0.0.T disk0:hfr-¦-mgbl-¦- 4.0.0.T disk0:hfr-¦-k9sec-¦-4.0.0.T disk0:hfr-¦-mpls-¦-4.0.0.T disk0:hfr-¦- diags-¦-4.0.0.T sync

The complete installation takes about 1 hour and 30 minutes.

• 8 minutes to tftp hfr-¦-mini-¦-px.vm-¦-4.0.0.T and CRC check etc.

• 30 minutes for Turboboot to complete

• 12 minutes for the system to reload and boot up to standby ready state and all line cards in IOS XR RUN

• 35 minutes to add and activate the optional PIEs

Upgrading Your File System From FAT16 to FAT32 This section discusses how to change the file system on the flash disk from the FAT16 format to the FAT32 format or from the FAT32 format back to the FAT16 format. In each of these scenarios, we assume the flash disk has been upgraded to a 4GB flash disk. Although it's possible to have a 1GB or 2GB Flash Disk with FAT32, it offers no benefit over FAT16 thus we don't recommending using FAT32 with those size flash disks.

Also if your 4GB flash disk has been partitioned into two 2GB partitions upgrading your file system from the FAT16 format to the FAT32 format offers no benefits over remaining with the FAT16 format. So the only reason to change to FAT32 is to partition a 4GB flash disk as a 3.5GB and 0.5GB partition. This type of partition is recommended in order to partition the amount of space. This may be required for future versions of Cisco IOS XR software that require more than 2GB of flash space.

This can be done as soon as you upgrade to Cisco IOS XR software Release 3.8 and higher or you can wait until the image will exceed the 2GB partition.

Warning Rolling back down to Cisco IOS XR software Release 3.7.2 or lower (which does not support a FAT32 boot disk) is much more difficult after the file system and partition has been changed to the FAT32 format. If you want to have an easy rollback capability, do not change the file system to FAT32 until you are upgrading from a Split Boot supported image to another Split Boot support image. Changing the file system is only possible when running Cisco IOS XR software Release 3.8 or higher.

Also, using the CLI based format command will change the file system back to FAT16.


OL-13669-03


Step 1 Attach to the Standby RP by typing the command run attach 0/rp1/cpu0 at the router prompt

Example with Standby RP at 0/RP1/CPU0.

RP/0/RP0/CPU0:Router#run attach 0/rp1/cpu0 attach: Starting session 1 to node 0/rp1/cpu0

Note KSH commands are very unforgiving. Please pay very close attention to make sure the commands are entered exactly as listed in this procedure.

Step 2 At the KSH prompt, enter the command fdisk /dev/disk0 delete -a

# fdisk /dev/disk0 delete -a

Step 3 At the KSH prompt, enter the command fdisk /dev/disk0 add -t6 -p88

# fdisk /dev/disk0 add -t6 -p88

Step 4 At the KSH prompt, enter the command fdisk /dev/disk0 add -t4 -p100

# fdisk /dev/disk0 add -t4 -p100

Step 5 At the KSH prompt, enter the command mount -e /dev/disk0

# mount -e /dev/disk0

Step 6 At the KSH prompt, enter the command mkdosfs -F32 /dev/disk0t6

# mkdosfs -F32 /dev/disk0t6 Format complete: FAT32 (4096-byte clusters), 3607592 kB available. #

Step 7 At the KSH prompt, enter the command mkdosfs -F32 /dev/disk0t4

# mkdosfs -F32 /dev/disk0t4 Format complete: FAT32 (4096-byte clusters), 491932 kB available. #

Step 8 Type exit at the KSH prompt to return to the normal prompt.

# exit Terminating attach to node 0/rp1/cpu0.. RP/0/RP0/CPU0:Router#

Step 9 Go to Admin mode by enter the command admin at the exec prompt.

RP/0/RP0/CPU0:Router#admin Thu Jun 18 01:30:48.439 PST RP/0/RP0/CPU0:Router(admin)#

Step 10 Execute the reload location 0/RP1/CPU0 command in Admin Mode to reload the Standby RP at 0/RP1/CPU0:

RP/0/RP0/CPU0:Router(admin)# reload location 0/RP1/CPU0


OL-13669-03



OL-13669-03

Cisco CRS-1 Carrier Routing System to Cisco CROL-13669-03

A
P P E N D I X B Cisco CRS-1 to Cisco CRS-3 Upgrade Decision Trees
This appendix contains three decision trees that describe the Cisco CRS-1 to Cisco CRS-3 upgrade process.

The three illustrations describe the following processes:

• Upgrading from Cisco IOS XR software Releases Earlier Than Release 3.8 to Cisco IOS XR software Release 4.0.1

• Upgrading from Cisco IOS XR software Releases Later Than Release 3.8 That Do Not Support FPD Auto-Upgrade to Cisco IOS XR software Release 4.0.1

• Upgrading from Cisco IOS XR software Releases That Support FPD Auto-Upgrade (Release 3.8.4 and Release 3.9.1) to Cisco IOS XR software Release 4.0.1

B-1S-3 Carrier Routing System Migration Guide

Appendix B Cisco CRS-1 to Cisco CRS-3 Upgrade Decision Trees

Figure B-1 Upgrading from Cisco IOS XR software Releases Earlier Than Release 3.8 to

Cisco IOS XR software Release 4.0.1

disk0: 4GFAT162G/2G

rommon�2.01PIE upgrade to

3.8.4/3.9.2 FAT16�FAT32(via CLI)

3.5G/0.5G

rommon�2.01PIE upgradeto 3.8.4/3.9.2

rommon�2.01PreStagedFlash or RP


rommon�2.01then turboboot

Migrateto 4G

mandatory

Migrateto 4G

recommended

disk0: 2GFAT16

Keep 2G card

Keep FAT16

FPD auto-upgradePIE upgradeto 4.0.1-px




FAT16�FAT32(via CLI)

3.5G/0.5G

FAT16�FAT32(via CLI)

3.5G/0.5G

Package installFPD upgrade

(reload line cards)

FPD upgrade(reload line cards)

FPD upgrade(reload line cards)

disk0: 1GFAT16

XR<3.8.0rommon≤1.48

Reload

Before 3.8.0PIE upgradeto 4.0.1-px

isn’t supported

24

61

77

Prior to this operation-create directory in bootflash:-copy MBI 4.0.1-px imageDuring operation-change BOOTVAR

Supported but wedon’t recommend tokeep 2G flash cards

Supported but we don’trecommend to keep FAT16

B-2Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

OL-13669-03


Figure B-2 Upgrading from Cisco IOS XR software Releases Later Than Release 3.8 That Do Not

Support FPD Auto-Upgrade to Cisco IOS XR software Release 4.0.1

disk0: 4GFAT162G/2G FAT16�FAT32

3.5G/0.5G


4.0.1-px

rommon�2.01PIE upgradeto 4.0.1-px

FAT16�FAT32



Keep currentFAT

Migrateto 4G

mandatory

Migrateto 4G

recommended

disk0: 2G

Keep 2G card

FPD upgrade(reload line

cards)


cards)


cards)


cards)




cards)


cards)disk0: 1G


cards)

Reload

2461

78


disk0: 4GFAT32

3.5G/0.5G


4.0.1-px

XR≥3.8.0


OL-13669-03


Figure B-3 Upgrading from Cisco IOS XR software Releases That Support FPD Auto-Upgrade

(Release 3.8.4 and Release 3.9.1) to Cisco IOS XR software Release 4.0.1

disk0: 4GFAT162G/2G FAT16�FAT32

3.5G/0.5G


4.0.1-px


FAT16�FAT32



Keep currentFAT

Migrateto 4G

mandatory

Migrateto 4G

recommended

disk0: 2G

Keep 2G card




cards)


cards)disk0: 1G

Reload

2461

79


disk0: 4GFAT32

3.5G/0.5G


4.0.1-px

XR3.8.4/3.9.1

In 3.8.4 and 3.9.1fpd auto-upgrade

is supported

Supported but we don’trecommend to keep FAT16


OL-13669-03


I N D E X

A

admin configure command 1-24, 1-26, 1-38, 1-41, 1-43, 1-60, 1-62, 1-78, 2-15, 2-34, 2-54

C

cabling documentation 1-86

commit command 1-38, 1-78, 2-15, 2-34, 2-55

considerations

switch fabric upgrade 1-23, 2-4, 2-24, 2-43

controllers fabric rack command 1-38, 1-39, 1-78, 1-79, 2-15, 2-16, 2-34, 2-35, 2-54, 2-55

D

documentation

Catalyst 6509 Switch 1-86

Cisco CRS Multishelf hardware 1-86

dsc serial command 1-24, 1-41, 1-60

F

fabric card

(figure) 1-31, 1-48, 1-67

fabric card, multishelf system

See FC/M cards

fabric card, single-chassis system

See FC/S cards

FC/M cards 1-21

FC/S cards 1-21

FCC

installation documents 1-86

LEDs 1-38, 1-78, 1-86, 2-15, 2-35, 2-55

Figures

installing an SFC 1-33, 1-49, 1-69, 2-11, 2-30, 2-50

removing an SFC 1-29, 1-46, 1-64, 2-8, 2-27, 2-47

SFC 1-28, 1-45, 1-63, 2-7, 2-10, 2-26, 2-29, 2-46, 2-49

SFC front panel 2-13, 2-32, 2-52

switch fabric card 1-31, 1-48, 1-67

switch fabric card (front view) 1-35, 1-52, 1-71

I

installing

SFC 1-30, 1-47, 1-65, 2-9, 2-29, 2-49

installing an SFC (figure) 1-33, 1-49, 1-69, 2-11, 2-30, 2-50

L

LCC

installation documents 1-86

M

multishelf system

documentation 1-86

upgrading

configuration examples 1-80

information 1-21

prerequisites 1-3, 1-21, 1-23, 1-40, 1-58, 1-80, 2-2

restrictions 2-2

R

removing an SFC (figure) 1-29, 1-46, 1-64, 2-8, 2-27, 2-47

IN-1isco CRS-3 Carrier Routing System Migration Guide

Index

ROMMON, version required for LCC 1-36, 1-37, 1-52, 1-53, 1-72, 1-73

S

serial number

displaying 1-80

SFC

front panel (figure) 2-13, 2-32, 2-52

installing 1-30, 1-47, 1-65, 2-9, 2-29, 2-49

installing (figure) 1-33, 1-49, 1-69, 2-11, 2-30, 2-50

removing (figure) 1-29, 1-46, 1-64, 2-8, 2-27, 2-47

verifying installation 1-35, 1-51, 1-71, 2-13, 2-32, 2-52

SFC (figure) 1-28, 1-45, 1-63, 2-7, 2-10, 2-26, 2-29, 2-46, 2-49

show access-lists ipv4 command 3-3

show controllers (Ethernet) 3-29

show controllers egressq clients 3-3

show controllers fabric fabric-backpressure summary command 1-38, 1-79, 2-16, 2-35, 2-55

show controllers fabric plane all command 1-24, 1-42, 1-60

show controllers fabric rack-status all detail command 1-38, 1-78, 2-16, 2-35, 2-55

show controllers rack-status all detail command 1-39, 1-79, 2-16, 2-35, 2-55

switch fabric card

(figure) 1-31, 1-48, 1-67

front view (figure) 1-35, 1-52, 1-71

switch fabric card (figure) 1-28, 1-45, 1-63, 2-7, 2-10, 2-26, 2-29, 2-46, 2-49

switch fabric plane

upgrade considerations 1-23, 2-4, 2-24, 2-43

T

technical assistance 1-87

troubleshooting documentation 1-86

IN-2Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing
System Migration Guide
OL-13669-03

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier ... · PDF fileCisco CRS-1 Carrier...

Documents

Transcript of Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier ... · PDF fileCisco CRS-1 Carrier...