cBR8 17.9.1w (or later) SUP Field Replacement Procedure Product Bulletin

Bulletin

Available Languages

Download Options

  • PDF
    (216.4 KB)
    View with Adobe Reader on a variety of devices
Updated:October 19, 2023

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Available Languages

Download Options

  • PDF
    (216.4 KB)
    View with Adobe Reader on a variety of devices
Updated:October 19, 2023

Table of Contents

 

 

Introduction and background

1 – Scope of the document

This document is aimed at notifying customers for the field use case of: Replacing a cBR-8 Supervisor Card with a replacement Supervisor. If the cBR-8 chassis is running 17.9.1* software and the replacement Supervisor has a “Pre-17.9.1*” version of software.

2 – Objective

It is recommended that any/all spare cBR-8 Supervisors be upgraded to 17.9.1* prior to being inserted into a production chassis.

3 – Legacy upgrade requirements

Detailed procedure

1.     Prepare USB(s) with cBR8 IOS-XE 17.6.1w and 17.9.1w images.

v17.6.1w = cbrsup-universalk9.17.06.01w.SPA.bin

v17.9.1w = cbrsup-universalk9.17.09.01w.SPA.bin

2.     Remove the SUP that needs to be replaced.

3.     While connected to a console attached to the stby-SUP PIC, insert the new stby-SUP.

Note:       Interrupt the booting process of the new stby-SUP in the next step to force it to the ROMMON prompt.

4.     While the new stby-SUP is booting the image, break to ROMMON by issuing the break command from the console. The break must be issued early in the boot process, while the image is copying to RAM.

5.     From ROMMON, change the configuration register boot option:

    Type 'confreg' and follow the instructions. Be sure to only change the boot option to boot to ROMMON, while keeping the rest of the configuration register settings the same.

    Example:

rommon 1 > confreg

           Configuration Summary

   (Virtual Configuration Register: 0x1822)

enabled are:

 [ 0 ] break/abort has effect

 [ 1 ] console baud: 115200

 boot: ...... image specified by the boot system commands or default to: cisco2-Cisco cBR-8

 

do you wish to change the configuration? y/n  [n]:  y

 enable  "diagnostic mode"? y/n  [n]:  n

 enable  "use net in IP bcast address"? y/n  [n]:  n

 enable  "load rom after netboot fails"? y/n  [n]:  n

 enable  "use all zero broadcast"? y/n  [n]:  n

 disable "break/abort has effect"? y/n  [n]:  n

 enable  "ignore system config info"? y/n  [n]:  n

 change console baud rate? y/n  [n]:  n

change the boot characteristics? y/n  [n]:  y

 

 enter to boot:

 0 = ROM Monitor

 1 = the boot helper image

 2-15 = boot system

 [2]:  0

 

 

           Configuration Summary

   (Virtual Configuration Register: 0x1820)

enabled are:

 [ 0 ] break/abort has effect

 [ 1 ] console baud: 115200

 boot: ...... the ROM Monitor

 

do you wish to change the configuration? y/n  [n]:  n

 

rommon 2 >

    Reset the new stby-SUP for the new config register settings to take effect:

rommon 2 > reset

6.     After reload, check the ROMMON version from the new stby-SUP console log:

    Type the following to check the ROMMON version:

rommon 1 > showmon

Current image running (0/1): Boot ROM1

 

System Bootstrap, Version 16.7(6r)S, RELEASE SOFTWARE

Copyright (c) 1994-2021  by cisco Systems, Inc.

 

Viper version register: 0x170724e0

7.     If the ROMMON version from step 6 is already 16.7(8r)s or later, it does not need to be upgraded - skip to step 8. If the ROMMON version is earlier than 16.7(8r)s, proceed with this step to upgrade ROMMON. Here, use the 17.6.1w image from the USB to upgrade the ROMMON version to 16.7(8r)s:

    Issue following instruction to use 17.6.1w to upgrade ROMMON from USB:

rommon 1 > boot usb0:cbrsup-universalk9.17.06.01w.SPA.bin

    The new stby-SUP will reload twice, installing the updated ROMMON version.

uefi_launch_linux: Launching the kernel....

 

 

Initializing Hardware ...

 

System Bootstrap, Version 16.7(6r)S, RELEASE SOFTWARE

Copyright (c) 1994-2019  by cisco Systems, Inc.

 

Current image running: Boot ROM0

       Rommon upgrade requested

       Start Flash boot timer

 

 

Initializing Hardware ...

 

System Bootstrap, Version 16.7(8r)S, RELEASE SOFTWARE

Copyright (c) 1994-2021  by cisco Systems, Inc.

 

Current image running: *Upgrade in progress* Boot ROM1

ROM: stopping boot timer

 

Last reset cause: BootRomUpgrade

 

Viper version register: 0x170724e0

Set Chassis Type to 13RU

Cisco cBR-8  platform with 50331648 Kbytes of main memory

    Validate the new ROMMON image using the following command:

rommon 1 > showmon

Current image running (0/1): Boot ROM1

 

System Bootstrap, Version 16.7(8r)S, RELEASE SOFTWARE

Copyright (c) 1994-2021  by cisco Systems, Inc.

 

Viper version register: 0x170724e0

8.     If the ROMMON version from previous steps is 16.7(8r)s or later you can load the 17.9.1w image directly from USB.

    To load 17.9.1w from USB, use the following command at the ROMMON prompt:

rommon 2 > boot usb0:cbrsup-universalk9.17.09.01w.SPA.bin

9.     On the active-SUP, use 'show redundancy', verify that the stby-SUP boots with the 17.9.1w image. NOTE that the value of the Configuration register of the stby-SUP includes the notation that the Configuration register "(will be 0x1822 at the next reload)".

10.  Copy the image to the boot location of the new stby-SUP.

    First, verify the boot location using 'show startup-config | in boot'

    Example:

Router#show start | in boot

boot-start-marker

boot system harddisk:cbrsup-universalk9.17.09.01w.SPA.bin

boot-end-marker

    Note that the boot location in the example above is harddisk:.

    Copy the image from the usb to the boot location identified above.

    Example:

Router-stby#copy usb0:cbrsup-universalk9.17.09.01w.SPA.bin harddisk:

    NOTE that when consoled into the stby-SUP, the stby-SUP’s harddisk: appears as “harddisk:” (it does not appear as “stby-harddisk:”)

 

Learn more