- Firmware Upgrades Overview
- Bundled FPGA Images Upgrades
- Field-Programmable Device Upgrades
- Upgrading ROMMON
- Upgrading Uboot
- Upgrading the Line Card Daggit Firmware
- Upgrading Both the Line Card Daggit Firmware and the UBoot Image
- Upgrading the Line Card PSoC Image in the Cisco cBR (Cisco IOS-XE Release 3.16.1S and later releases)
- Upgrading the Line Card PSoC Image in the Cisco cBR (Cisco IOS-XE Release 3.16.0S)
- Upgrading the Fan PSoC Image in the Cisco cBR
- Upgrading Supervisor CPLD Firmware in the Cisco cBR
- Upgrading Docsis 3.0 downstream module and Docsis 3.1 downstream module (Cisco IOS-XE Release 3.18.0S and earlier releases)
- Upgrading Docsis 3.0 downstream module and Docsis 3.1 downstream module (Cisco IOS-XE Release 3.18.1S and later releases)
Upgrading the Cisco
cBR-8 Router Firmware
This section contains the upgrade procedures for the Cisco cBR-8 Router Firmware.
- Firmware Upgrades Overview
- Bundled FPGA Images Upgrades
- Field-Programmable Device Upgrades
- HW-Programmable Device Upgrades
Firmware Upgrades Overview
The following three types of firmware upgrades are available for the Cisco cBR-8 Series router:
- Field Programmable Gate Array (FPGA) images bundled into the Cisco IOS-XE software image, like certain Supervisor and LC components. These FPGA images are automatically installed when the Cisco IOS-XE software image is upgraded.
- FPD images packages that are upgraded separately or with the Cisco IOS-XE software image upgrade, like the PIC images.
- HW-Programmable device upgrades that include ROM Monitor (ROMMON) upgrades, Universal Boot (U-boot) upgrades, PSoC and CPLD upgrades.
You can view the current firmware images and packages on your router, using the methods outlined in the following sections.
- Displaying Current and Minimum Required FPD Image Versions
- Displaying Information About the Default FPD Image Package
- Displaying All Firmware on the Router
Displaying Current and Minimum Required FPD Image Versions
To display the current version of FPD images on the FRUs installed on your router, use the show hw-module [slot/subslot | all] fpd command, where slot is the slot number where the FRU is installed, and subslot is the number of the FRU subslot where a target FRU is located. Entering the all keyword shows information for hardware in all router slots.
The following examples show the output when using this show command. The output display in this example shows that FPD versions on the FRUs in the system meet the minimum requirements:
Router# show hw-module all fpd ==== ====================== ====== ============================================= H/W Field Programmable Current Min. Required Slot Card Type Ver. Device: "ID-Name" Version Version ==== ====================== ====== ================== =========== ============== 0/1 CBR-RF-PROT-PIC 0.0 35-CBR STEALTHSTAR 7.14 7.13 ---- ---------------------- ------ ------------------ ----------- -------------- 2/1 CBR-RF-PROT-PIC 3.0 35-CBR STEALTHSTAR 5.0 7.13 * ---- ---------------------- ------ ------------------ ----------- -------------- 3/1 CBR-RF-PIC 0.0 34-CBR RFSW PIC 6.2 7.35 * ---- ---------------------- ------ ------------------ ----------- -------------- 4/1 CBR-SUP-8X10G-PIC 2.4 36-CBR SUP PIC 0.130 0.130 ---- ---------------------- ------ ------------------ ----------- -------------- 5/1 CBR-SUP-8X10G-PIC 3.0 36-CBR SUP PIC 0.130 0.130 ---- ---------------------- ------ ------------------ ----------- -------------- 6/1 CBR-RF-PIC 3.0 34-CBR RFSW PIC 5.0 7.35 * ==== ====================== ====== =============================================
This example shows the output when using the slot/subslot argument to identify a particular FRU:
Router# show hw-module subslot 0/1 fpd ==== ====================== ====== ============================================= H/W Field Programmable Current Min. Required Slot Card Type Ver. Device: "ID-Name" Version Version ==== ====================== ====== ================== =========== ============== 0/1 CBR-RF-PROT-PIC 0.0 35-CBR STEALTHSTAR 7.14 7.13 ==== ====================== ====== =============================================
The output display in this example shows that the FRU in subslot 0/1 is disabled because one of the programmable devices does not meet the minimum version requirements.
Router#show hw-module all fpd ==== ====================== ====== ============================================= H/W Field Programmable Current Min. Required Slot Card Type Ver. Device: "ID-Name" Version Version ==== ====================== ====== ================== =========== ============== 0/1 CBR-RF-PROT-PIC 0.0 35-CBR STEALTHSTAR 7.14 7.13 ---- ---------------------- ------ ------------------ ----------- -------------- 2/1 CBR-RF-PROT-PIC 3.0 35-CBR STEALTHSTAR 5.0 7.13 * ---- ---------------------- ------ ------------------ ----------- -------------- 3/1 CBR-RF-PIC 0.0 34-CBR RFSW PIC 6.2 7.35 * ---- ---------------------- ------ ------------------ ----------- -------------- 4/1 CBR-SUP-8X10G-PIC 2.4 36-CBR SUP PIC 0.130 0.130 ---- ---------------------- ------ ------------------ ----------- -------------- 5/1 CBR-SUP-8X10G-PIC 3.0 36-CBR SUP PIC 0.130 0.130 ---- ---------------------- ------ ------------------ ----------- -------------- 6/1 CBR-RF-PIC 3.0 34-CBR RFSW PIC 5.0 7.35 * ==== ====================== ====== ============================================= NOTES: - FPD images that are required to be upgraded are indicated with a '*' character in the "Minimal Required Version" field.
Displaying Information About the Default FPD Image Package
You can use the show upgrade fpd package default command to find out which FRUs are supported with your current Cisco IOS-XE release and which FPD image package you need for an upgrade.
Router# show upgrade fpd package default Load for five secs: 2%/0%; one minute: 3%; five minutes: 4% Time source is NTP, 16:09:07.658 PDT Tue Jul 28 2015 **************************************************************************** This Cisco IOS software image requires the following default FPD Image Package for the automatic upgrade of FPD images (the package is available from Cisco.com and is accessible from the Cisco Software Center page where this IOS software image can be downloaded): **************************************************************************** Version: 15.5(3)S Package Filename: cbr-fpd-bundle.pkg List of card type supported in this package: Minimal No. Card Type HW Ver. ---- ---------------------------------------- ------- 1) RF Switch PIC 0.0 2) RF Switch PIC 0.0 3) 8x10GE Supervisor PIC 0.0 ---- ---------------------------------------- -------
Displaying All Firmware on the Router
Use the show platform diag command to view all firmware available on the router.
Router#show platform diag Chassis type: CBR-8-CCAP-CHASS Pic: 0/1, CBR-RF-PROT-PIC Internal state : inserted Physical insert detect time : 00:03:27 (00:15:07 ago) Firmware version: : 0000070E Slot: 2, CBR-CCAP-LC-40G Running state : ok Internal state : online Internal operational state : ok Physical insert detect time : 00:01:41 (00:16:53 ago) Software declared up time : 00:05:04 (00:13:30 ago) CPLD version : 0000001C Rommon version : 2011.03.12 Basestar version : 00110002 Raider version : 01010006 Caprica version : 00000017 PSOC 0 version : v3.0 PSOC 1 version : v3.0 Pic: 2/1, CBR-RF-PROT-PIC Internal state : inserted Physical insert detect time : 00:03:28 (00:15:06 ago) Firmware version: : 00000500 Slot: 3, CBR-CCAP-LC-40G Running state : ok Internal state : online Internal operational state : ok Physical insert detect time : 00:01:41 (00:16:53 ago) Software declared up time : 00:05:03 (00:13:31 ago) CPLD version : 0000001C Rommon version : 2011.03.12 Basestar version : 00110002 Raider version : 01010006 Caprica version : 00000017 PSOC 0 version : v4.2 PSOC 1 version : v4.2 Pic: 3/1, CBR-RF-PIC Internal state : inserted Physical insert detect time : 00:03:29 (00:15:05 ago) Firmware version: : 00000602 Slot: 6, CBR-CCAP-LC-40G Running state : ok Internal state : online Internal operational state : ok Physical insert detect time : 00:01:41 (00:16:53 ago) Software declared up time : 00:05:02 (00:13:31 ago) CPLD version : 0000001C Rommon version : 2011.03.12 Basestar version : 00110002 Raider version : 01010006 Caprica version : 00000017 PSOC 0 version : v4.2 PSOC 1 version : v4.2 Pic: 6/1, CBR-RF-PIC Internal state : inserted Physical insert detect time : 00:03:30 (00:15:04 ago) Firmware version: : 00000500 Slot: SUP0, CBR-CCAP-SUP-160G Physical insert detect time : 00:01:41 (00:16:53 ago) CPLD version : 14121111 ViperSO CPLD version : 13032701 ViperSIO CPLD version : 14010901 Rommon version : 15.5(2r)S Blackbird version : 00000112 Raptor ESI version : 00010035 Raptor MAC version : 0001002D SUP-PIC CPLD version : 14071504 SUP-DC CPLD version : ffffffff DTI Client FPGA version : 00000005 DTI Firmware version : 00000A03 Cortina PHY version : 201402061607 SUP PSOC 0 version : v4.0.8 SUP PSOC 1 version : v4.0.8 SUP PSOC 2 version : v4.0.9_IVY SUP PSOC 3 version : v4.0.6 SUP-DC PSOC 0 version : N/A SUP-DC PSOC 1 version : N/A SUP-PIC PSOC 0 version : V2.0.5 SUP-PIC PSOC 1 version : V2.0.5 Slot: R0, CBR-CCAP-SUP-160G Running state : ok, active Internal state : online Internal operational state : ok Software declared up time : 00:01:41 (00:16:53 ago) Slot: F0, CBR-CCAP-SUP-160G Running state : ok, active Internal state : online Internal operational state : ok Software declared up time : 00:03:22 (00:15:12 ago) Hardware ready signal time : 00:00:00 (never ago) Packet ready signal time : 00:03:41 (00:14:53 ago) Slot: 4, CBR-CCAP-SUP-160G Running state : ok Internal state : online Internal operational state : ok Software declared up time : 00:03:27 (00:15:07 ago) Pic: 4/1, CBR-SUP-8X10G-PIC Internal state : inserted Physical insert detect time : 00:03:31 (00:15:03 ago) Slot: SUP1, CBR-CCAP-SUP-160G Physical insert detect time : 00:01:47 (00:16:47 ago) CPLD version : 14121111 ViperSO CPLD version : 13080901 ViperSIO CPLD version : 14050801 Rommon version : 15.5(2r)S Blackbird version : 00000112 Raptor ESI version : 00010035 Raptor MAC version : 0001002D SUP-PIC CPLD version : 14071504 SUP-DC CPLD version : ffffffff DTI Client FPGA version : 00000005 DTI Firmware version : 00000A03 Cortina PHY version : 201402061607 SUP PSOC 0 version : v4.0.8 SUP PSOC 1 version : v4.0.8 SUP PSOC 2 version : v4.0.9_IVY SUP PSOC 3 version : v4.0.6 SUP-DC PSOC 0 version : N/A SUP-DC PSOC 1 version : N/A SUP-PIC PSOC 0 version : V2.0.5 SUP-PIC PSOC 1 version : V2.0.5 Slot: R1, CBR-CCAP-SUP-160G Running state : ok, standby Internal state : online Internal operational state : ok Software declared up time : 00:01:47 (00:16:47 ago) Slot: F1, CBR-CCAP-SUP-160G Running state : ok, standby Internal state : online Internal operational state : ok Software declared up time : 00:05:07 (00:13:26 ago) Hardware ready signal time : 00:00:00 (never ago) Packet ready signal time : 00:05:28 (00:13:05 ago) Slot: 5, CBR-CCAP-SUP-160G Running state : ok Internal state : online Internal operational state : ok Software declared up time : 00:05:12 (00:13:22 ago) Pic: 5/1, CBR-SUP-8X10G-PIC Internal state : inserted Physical insert detect time : 00:03:32 (00:15:02 ago) Slot: P0, PWR-3KW-AC-V2 State : ok Physical insert detect time : 00:03:27 (00:15:07 ago) Slot: P1, PWR-3KW-AC-V2 State : ok Physical insert detect time : 00:03:27 (00:15:07 ago) Slot: P2, PWR-3KW-AC-V2 State : ok Physical insert detect time : 00:03:27 (00:15:07 ago) Slot: P3, Unknown State : ps, fail Physical insert detect time : 00:00:00 (never ago) Slot: P4, Unknown State : ps, fail Physical insert detect time : 00:00:00 (never ago) Slot: P5, Unknown State : ps, fail Physical insert detect time : 00:00:00 (never ago) Slot: P10, CBR-FAN-ASSEMBLY State : ok Physical insert detect time : 00:03:37 (00:14:57 ago) Firmware version : CBR-FAN FW 1.4 Slot: P11, CBR-FAN-ASSEMBLY State : ok Physical insert detect time : 00:03:37 (00:14:56 ago) Firmware version : CBR-FAN FW 1.4 Slot: P12, CBR-FAN-ASSEMBLY State : ok Physical insert detect time : 00:03:37 (00:14:57 ago) Firmware version : CBR-FAN FW 1.4 Slot: P13, CBR-FAN-ASSEMBLY State : ok Physical insert detect time : 00:03:37 (00:14:57 ago) Firmware version : CBR-FAN FW 1.4 Slot: P14, CBR-FAN-ASSEMBLY State : ok Physical insert detect time : 00:03:37 (00:14:57 ago) Firmware version : CBR-FAN FW 1.4
Bundled FPGA Images Upgrades
Two methods may be used to upgrade the Cisco IOS-XE software image, as outlined in the following sections.
- Upgrading Your Cisco IOS-XE Release and FPD Image
- Upgrading Only Your Cisco IOS-XE Release and Retaining Your Current FPD Image
Upgrading Your Cisco IOS-XE Release and FPD Image
To upgrade your Cisco IOS-XE release and your FPD image, do the following steps:
Upgrading Only Your Cisco IOS-XE Release and Retaining Your Current FPD Image
You may choose to upgrade your Cisco IOS-XE release with or without retaining your current FPD image.
Note | You may choose to upgrade your Cisco IOS-XE image and retain your current FPD image, although this is not recommended. |
Field-Programmable Device Upgrades
If you retained the current FPD images and only upgraded the Cisco IOS-XE software image, then use the procedures described in this section to upgrade the FPD images.
These instructions are not always feasible for operating network environments. If these methods of upgrade are not suitable for your situation, see other sections of this document for other methods of upgrading FPDs.
- Upgrading FPD Images in a Production System
- Optional FPD Procedures
- Verifying the FPD Image Upgrade Progress
- Troubleshooting Problems with FPD Image Upgrades
Upgrading FPD Images in a Production System
Adding a FRU to a production system presents the possibility that the FRU may contain versions of FPD images that are incompatible with the Cisco IOS-XE release currently running the router. In addition, the FPD upgrade operation can be a very CPU-intensive operation and therefore the upgrade operation may take more time when it is performed on a production system. The performance impact will vary depending on various factors, including network traffic load, the type of processing engine used, type of FRU, and the type of service configured.
For these reasons, we recommend that one of the following alternatives be used to perform the FPD upgrade on a production system if possible:
- Verifying System Compatibility First
- Using a Nonproduction System to Upgrade the Cisco cBR Series Converged Broadband Routers FPD Image
Verifying System Compatibility First
If a spare system is not available to perform an upgrade, you can check for system compatibility by disabling the automatic upgrade feature before inserting the FRU.
-
If the FPD images on the FRU are compatible with the system, you will only need to re-enable the automatic upgrade feature (the automatic upgrade feature can be re-enabled using the upgrade fpd auto command).
-
If the FPD images on the FRU are not compatible with the system, the FRU is disabled but will not impact system performance by attempting to perform an automatic upgrade.
Use the following procedure to check the FPD images on the FRU for system compatibility:
Step 1 | Disable the automatic upgrade feature using the no upgrade fpd auto global configuration command. |
Step 2 | Insert the FRU into the system.
If the FPD images are compatible, the FRU will operate successfully after bootup. If the FPD images are not compatible, the FRU is disabled. At this point we recommend that you wait for a scheduled maintenance when the system is offline to manually perform the FPD upgrade as described in the Manually Upgrading FRU FPD Images section. |
Step 3 | Re-enable the automatic upgrade feature using the upgrade fpd auto global configuration command. |
Using a Nonproduction System to Upgrade the Cisco cBR Series Converged Broadband Routers FPD Image
Use the following procedure to perform an upgrade on a spare system:
-
The spare system is running the same version of the Cisco IOS-XE software release that the target production system is running.
-
The automatic upgrade feature is enabled on the spare system. (The automatic upgrade feature is enabled by default. It can also be enabled using the upgrade fpd auto command).
Step 1 | Insert the FRU into the spare
system.
If an upgrade is required, the system will perform the necessary FPD image updates so that when this FRU is inserted to the target production system it will not trigger an FPD upgrade operation there. |
Step 2 | Verify the upgrade was successful by entering the show hw-module all fpd command. |
Step 3 | Remove the FRU from the spare system after the upgrade. |
Step 4 | Insert the FRU into the target production system. |
Optional FPD Procedures
This section provides information for optional FPD-related functions. None of the topics discussed in this section are necessary for completing FPD upgrades, but may be useful in some FPD-related scenarios. It covers the following topics:
Manually Upgrading FRU FPD Images
To manually upgrade the current FPD version on a FRU, use the following command:
Router# upgrade hw-module subslot [slot/subslot] fpd bundle [reload]
In this example, slot is the slot where the FRU is installed, subslot is the subslot number where the FRU is located, fpd indicates the type of upgrade required, bundle selects the bundled FPD package, and reload specifies that the FRU is automatically reloaded after the upgrade. Note that subslot slot/subslot is used to specify a FRU FPD upgrade. The FRU will automatically be reloaded to complete the FPD upgrade.
Caution | An image upgrade can require a long period of time to complete depending on the FRU. |
Upgrading Multiple FPD Images
A single piece of hardware can contain multiple FPD images. The Cisco cBR Series Routers can upgrade up to three FPD images simultaneously. However, only one FPD upgrade per router slot can occur at a time, so all FPD images on all FRUs in a single slot will have to wait for another FPD upgrade to finish.
Note | Some FPD images require the FRU to reload to complete. The FPD upgrade process will perform this step automatically, so users do not have to intervene. However, the other FPDs in the hardware of the specified slot will have to wait for this reload to complete before their upgrade process begins. |
Note | With a manual upgrade, you must include the reload option to cause the FRU to reload automatically. |
During an automatic upgrade, the Cisco cBR Series Routers will upgrade as many FPDs as possible at a time. No user intervention is possible or necessary. The upgrade process will not stop until all FPD images have been updated.
During manual upgrades, it is important to note that users can only specify upgrades for a single piece of hardware each time the upgrade hw-module subslot [slot/subslot] command is entered. The maximum of three simultaneous upgrades applies to manual upgrades as well. If you individually specify multiple manual FPD upgrades, only three FPDs can be upgraded simultaneously and that can only occur when the hardware is in different router slots. The FPD upgrade process will stop when all FPDs for the specified hardware have been upgraded.
Verifying the FPD Image Upgrade Progress
You can use the show upgrade fpd progress command to view a snapshot of the upgrade progress while an FPD image upgrade is in progress. The following example shows the type of information this command displays:
Router# show upgrade fpd progress FPD Image Upgrade Progress Table: 4/1 CBR-SUP-8X10G-PIC 36-CBR SUP PIC 00:10:00 00:00:06 Updating... ==== =================== ==================================================== 0/1 CBR-RF-PROT-PIC 35-CBR STEALTHSTAR --:--:-- --:--:-- Waiting...
Troubleshooting Problems with FPD Image Upgrades
This section contains information to help troubleshoot problems that can occur during the upgrade process.
It contains the following topics:
Power Failure or Removal of a FRU During an FPD Image Upgrade
These instructions should only be used if a previous upgrade attempt has failed due to an external factor such as a power failure or a FRU removal.
If the FPD upgrade operation is interrupted by a power failure or the removal of a FRU, it could corrupt the FPD image. This corruption of the FPD image file makes the FRU unusable by the router and the system will display an error message.
The show hw-module all fpd command can be used to verify that the FRU is using a corrupted FPD image.
Router# show hw-module all fpd ==== ====================== ====== ============================================= H/W Field Programmable Current Min. Required Slot Card Type Ver. Device: "ID-Name" Version Version ==== ====================== ====== ================== =========== ============== 0/1 CBR-RF-PROT-PIC 0.0 35-CBR STEALTHSTAR 7.14 7.13 ---- ---------------------- ------ ------------------ ----------- -------------- 2/1 CBR-RF-PROT-PIC 3.0 35-CBR STEALTHSTAR 5.0 7.13 * ---- ---------------------- ------ ------------------ ----------- -------------- 3/1 CBR-RF-PIC 0.0 34-CBR RFSW PIC 6.2 7.35 * ---- ---------------------- ------ ------------------ ----------- -------------- 4/1 CBR-SUP-8X10G-PIC 2.4 36-CBR SUP PIC 0.130 0.130 ---- ---------------------- ------ ------------------ ----------- -------------- 5/1 CBR-SUP-8X10G-PIC 3.0 36-CBR SUP PIC 0.130 0.130 ---- ---------------------- ------ ------------------ ----------- -------------- 6/1 CBR-RF-PIC 3.0 34-CBR RFSW PIC 5.0 7.35 * ==== ====================== ====== =============================================
Performing an FPD Recovery Upgrade
The recovery upgrade procedure can only be performed on a FRU that has been powered off by the system after it has failed all of the retries attempted to initialize the FRU.
Note | Because a recovery upgrade is done at a more conservative speed, it may take more than the estimated upgrade time. |
Note | Other factors can cause the system to ask “Do you want to perform the recovery upgrade operation?” Only answer y to this question if you have attempted an FPD upgrade that has failed due to a power failure or a FRU removal. If you are prompted for this question without having previously had a failed upgrade attempt for one of the aforementioned reasons, contact Cisco Technical Support. |
Perform the manual FPD image upgrade method using the upgrade hw-module subslot command to recover from a corrupted image after the FRU has been powered off by the system.
HW-Programmable Device Upgrades
This section provides information for the HW-Programmable device upgrades.
Effective from Cisco IOS-XE Release 3.16.1S, an all-in-one firmware package is introduced for HW-Programmable device upgrades. Packages such as PSoC, Line Card Daggits, UBoot Images and viper are bundled together into the all-one-one package and released along with Cisco IOS-XE Release 3.16.1S.
Note | The all-in-one package is applicable only for Cisco IOS-XE Release 3.16.1S. |
- Upgrading ROMMON
- Upgrading Uboot
- Upgrading the Line Card Daggit Firmware
- Upgrading Both the Line Card Daggit Firmware and the UBoot Image
- Upgrading the Line Card PSoC Image in the Cisco cBR (Cisco IOS-XE Release 3.16.1S and later releases)
- Upgrading the Line Card PSoC Image in the Cisco cBR (Cisco IOS-XE Release 3.16.0S)
- Upgrading the Fan PSoC Image in the Cisco cBR
- Upgrading Supervisor CPLD Firmware in the Cisco cBR
- Upgrading Docsis 3.0 downstream module and Docsis 3.1 downstream module (Cisco IOS-XE Release 3.18.0S and earlier releases)
- Upgrading Docsis 3.0 downstream module and Docsis 3.1 downstream module (Cisco IOS-XE Release 3.18.1S and later releases)
Upgrading ROMMON
The Cisco cBR boots up with the ROM monitor (ROMMON). ROMMON upgrades are released periodically. When a ROMMON upgrade image is released, use the procedure outlined in this section to upgrade the ROMMON in the Cisco cBR.
Use the showmon command to display the current image running of ROMMON.
rommon > showmon Current image running (0/1): Boot ROM0 ...
There are two Boot ROMs that need to be upgraded, Boot ROM0 which is the running Boot ROM on the active SUP and Boot ROM1 which is the Boot ROM1 on the standby SUP not running currently. This procedure upgrades both the Boot ROMs. During the upgrade process, the Boot ROM1 is upgraded first to ensure a reliable backup copy in case the upgrade procedure fails.
Step 1 | Boot the image to IOS prompt. | ||
Step 2 | Download the ROMMON package from Cisco.com and copy it to bootflash or harddisk. | ||
Step 3 | Run the
following command in IOS prompt:
Router# upgrade rom-monitor filename bootflash:[package name] r0
The IOS upgrades ROMMON and sets ROMMON Upgrade Flag. | ||
Step 4 | Run the
following command if you have a standby supervisor:
Router# upgrade rom-monitor filename bootflash:[package name] r1
This example shows the output that is displayed after the upgrade rom-monitor command is used. Router#upgrade rom-monitor filename harddisk:cbrsup-rp-hw-programmable-firmware.155-3.r.S3-ext.01.SPA.pkg r0 Upgrade rom-monitor Target copying rom-monitor image file 131072+0 records in 131072+0 records out Checking upgrade image... 4194304+0 records in 8192+0 records out Upgrade image MD5 signature is c4469e1cc016d36b6109252e6565514e Burning upgrade partition... 4194304+0 records in 4194304+0 records out Checking upgrade partition... 4194304+0 records in 4194304+0 records out 131072+0 records in 131072+0 records out 131072+0 records in 131072+0 records out Upgrade flash partition MD5 signature is c4469e1cc016d36b6109252e6565514e ROMMON upgrade complete. To make the new ROMMON permanent, you must restart the RP. | ||
Step 5 | Reload the
Supervisor cards after the upgrade is complete.
| ||
Step 6 | Rommon > b
bootflash:<imagename>
Reload the Cisco IOS-XE software to reset the ROMMON upgrade flag.
This example shows the bootflash command with the image name of the Cisco IOS-XE Release 3.16.0S software image. Rommon > b bootflash:cbrsup-universalk9.03.15.00.S.155-2.S-std.SPA.bin |
Upgrading Uboot
This section provides the procedure to upgrade the Uboot in Cisco cBR-8 router.
Step 1 | Copy the
firmware package file to the hard disk of the Cisco cBR-8 router.
copy ftp://location/firmware-name harddisk:
|
Step 2 | Upgrade the
Uboot using the following command:
upgrade hw-programmable cable slot-id rommon pkg_name firmware-name
Example: upgrade hw-programmable cable 3 rommon pkg_name /harddisk/cbrsub-rp-hw-programmable-firmware.156-1.r.S1-std.02.SPA.pkg UBOOT: FILE : /tmp/fpd/mount/uboot.bin.SPA VERSION : U-Boot 2011.03.13 BYTES : 1441792 Upgrade Field Region: SUCCESS! |
Step 3 | Reboot the line
card after the upgrade command output is displayed using the following command:
hw-module slot slot-id reload
|
Upgrading the Line Card Daggit Firmware
The RF line card is run by the Daggit firmware. To upgrade the Daggit firmware, use the procedure outlined in this section.
Step 1 | Copy the line
card firmware package to harddisk.
copy tftp:xxx harddisk:
| ||
Step 2 | Run the
following pre-upgrade commands on the SUP IOS:
upgrade hw-programmable cable active_SUP daggit pre-upgrade slot LC_slot_#
Example: Router# upgrade hw-programmable cable R0 daggit pre-upgrade slot 3 | ||
Step 3 | Upgrade the
line card firmware using the SUP IOS command.
upgrade hw-programmable cable LC_slot_# daggit pkg_name firmware_pkg_location_path
Example (Cisco IOS-XE Release 3.16.1S): Router# upgrade hw-programmable cable 3 daggit pkg_name /harddisk/ cbrsup-rp-hw-programmable-firmware.155-3.r.S3-ext.03.SPA.pkg Initialize GPIO pins...... Lattice Semiconductor Corp. ispVME V12.1 Copyright 1998-2008. For Daisy Chain of All In-System Programmable Devices FREQUENCY 25000000 HZ; NOTE: Daggits upgrade will take 15 mins! Do Not Reboot Line Card! Example (Cisco IOS-XE Release 3.16.0S): Router#upgrade hw-programmable cable 3 daggit pkg_name /harddisk/cbrsup-rp-hw-programmable-firmware.155-3.r.S3-ext.03.SPA.pkg Initialize GPIO pins...... Lattice Semiconductor Corp. ispVME V12.1 Copyright 1998-2008. For Daisy Chain of All In-System Programmable Devices FREQUENCY 25000000 HZ; NOTE: Daggits upgrade will take 15 mins! Do Not Reboot Line Card! | ||
Step 4 | After the
upgrade is complete (takes approximately 15 minutes), the line card moves to
unknown
state. Check the status of the line card using the
show platform
command. When the line card is in
unknown
state, run the following command to recover the line card:
upgrade hw-programmable cable active_SUP daggit lc-recovery slot LC_slot_#
Example: Router# upgrade hw-programmable cable R0 daggit lc-recovery slot 3
| ||
Step 5 | The line card
moves from
booting to
active
state. Check the status of the line card using the
show platform
command. When the line card is in
active
state, run the following command to verify the upgrade:
upgrade hw-programmable cable active_SUP daggit post-active slot LC_slot_#
Example: Router# upgrade hw-programmable cable R0 daggit post-active slot 3 Verify the output to check if it shows the latest version and if the image can be upgraded or is the golden image. If the version is not what you expected and you are running golden image, the upgrade process did not complete. Start your upgrade again from step 1 and make sure you do not reboot the line card until the upgrade is complete. |
Upgrading Both the Line Card Daggit Firmware and the UBoot Image
This section outlines the procedure for upgrading the line card Daggit firmware and the UBoot image.
Note | The UBoot image is not released in Cisco IOS-XE Release 3.16.0S. This procedure cannot be used while upgrading the firmware for Cisco IOS-XE Release 3.16.0S. |
Step 1 | Copy the
firmware package to harddisk.
copy tftp:xxx harddisk:
| ||
Step 2 | Run the
following pre-upgrade commands on the SUP IOS:
upgrade hw-programmable cable active_SUP daggit pre-upgrade slot LC_slot_#
Example: Router# upgrade hw-programmable cable R0 daggit pre-upgrade slot 3 | ||
Step 3 | Upgrade both
the line card firmware and the uboot image using the following command:
Router#upgrade hw-programmable cable 2 pkg_name /harddisk/cbrsup-rp-hw-programmable-firmware.155-3.r.S3-ext.03.SPA.pkg UBOOT: FILE : /tmp/fpd/mount/uboot.bin.SPA VERSION : U-Boot 2011.03.9 BYTES : 1441792 Upgrade Field Region: SUCCESS! Daggits: Initialize GPIO pins...... Lattice Semiconductor Corp. ispVME V12.1 Copyright 1998-2008. For Daisy Chain of All In-System Programmable Devices FREQUENCY 25000000 HZ; Feature row programming +=======+ | PASS! | +=======+ Programming Daggits CPLD image... FREQUENCY 25000000 HZ; NOTE: Daggits upgrade will take 15 mins! Do Not Reboot Line Card! | ||
Step 4 | After the
upgrade is complete (takes approximately 15 minutes), the line card moves to
unknown
state. Check the status of the line card using the
show platform
command. When the line card is in
unknown
state, run the following command to recover the line card:
upgrade hw-programmable cable active_SUP daggit lc-recovery slot LC_slot_#
Example: Router# upgrade hw-programmable cable R0 daggit lc-recovery slot 3
| ||
Step 5 | The line card
moves from
booting to
active
state. Check the status of the line card using the
show platform
command. When the line card is in
active
state, run the following command to verify the upgrade:
upgrade hw-programmable cable active_SUP daggit post-active slot LC_slot_#
Example: Router# upgrade hw-programmable cable R0 daggit post-active slot 3 Verify the output to check if it shows the latest version and if the image is upgradable or golden. If the version is not what you expected and you are running golden image, the upgrade process did not complete. Start your upgrade again from step 1 and make sure you do not reboot the line card until the upgrade is complete. Use the show platform diag command to verify the internal state and firmware version of the line card. |
Upgrading the Line Card PSoC Image in the Cisco cBR (Cisco IOS-XE Release 3.16.1S and later releases)
This section provides the procedure to upgrade the line card PSoC (LC PSoC) for Cisco IOS-XE Release 3.16.1S.
Step 1 | Copy the
firmware package to harddisk.
copy tftp:xxx harddisk:
|
Step 2 | Run the
following upgrade command:
upgrade hw-programmable cable LC_slot_# psoc pkg_name firmware_pkg_location_path
Example: Router#upgrade hw-programmable cable 8 psoc pkg_name /harddisk/ cbrsup-rp-hw-programmable-firmware.155-3.r.S3-ext.04.SPA.pkg PSOC pre-upgrading ready, the card will reload twice to finish the PSOC updating. It will take 20 mins in total. |
Step 3 | The line card
reloads automatically. When the upgrade is completed, the following message is
displayed.
002456: Sep 8 11:26:58.828 CST: %CMCC-3-FRU_HWPRG_UPG_PSOC_SUCCESS: CLC8: cmcc: Hardware programmable PSOCs on Line card in slot 8 were successfully programmed. The card will reload to make new firmware work. |
Step 4 | The line card reloads automatically once again. After the line card reloads, wait for it to come online. |
What to Do Next
Router#show platform hardware slot 1 psoc 0 version
Load for five secs: 29%/6%; one minute: 30%; five minutes: 31%
Time source is NTP, 10:20:17.662 PORTUGAL-Summer Tue Aug 4 2015
PSOC Version
version name version value
------------------------------------------------------
psoc_address 50-0063
reg_pmbus_revision 22
reg_mfr_id Cypress Semicon
reg_mfr_model 039 Power Spvr
reg_mfr_revision Version 2.0
reg_mfr_location Seattle, WA
reg_mfr_date 2013-09-04
reg_mfr_serial v3.0
Router#
Upgrading the Line Card PSoC Image in the Cisco cBR (Cisco IOS-XE Release 3.16.0S)
This section provides the procedure to upgrade the line card PSoC (LC PSoC).
Step 1 | Copy the
firmware package to harddisk.
copy tftp:xxx harddisk:
| ||
Step 2 | Run the
following upgrade command:
upgrade hw-programmable cable LC_slot_# psoc pkg_name firmware_pkg_location_path
Example: Router#upgrade hw-programmable cable 7 psoc pkg_name /harddisk/cbrsup-rp-hw-programmable-firmware.155-3.r.S3-ext.04.SPA.pkg PSOC pre-upgrading ready, please power-cycle the board to finish the PSOC updating. Example: PSOC pre-upgrading ready, please power-cycle the board to finish the PSOC updating. | ||
Step 3 | Power-cycle the
Cisco cBR chassis or perform an OIR of the RF line card.
Aug 4 09:02:59.836: %IOSXE_OIR-6-OFFLINECARD: Card (cc) offline in slot 1 Aug 4 09:02:59.839: %CABLE_CLC-5-LOGGER_LC_REMOVED: Carrier Card 1 removed Aug 4 09:02:59.844: %BIPC-6-SESSION_DOWN: IPCCL Session to CLC1 is DOWN Aug 4 09:02:59.937: %IOSXE_OIR-6-REMCARD: Card (cc) removed from slot 1 Aug 4 09:02:59.938: %CABLE_CLC-5-LOGGER_LC_REMOVED: Carrier Card 1 removed LAB1_CBR8_DEMO# Aug 4 09:03:15.622: %IOSXE_OIR-6-INSCARD: Card (cc) inserted in slot 1 | ||
Step 4 | The RF line card
reboots after the chassis power-cycle or the RF line card OIR is completed. The
LC PSoC upgrade process continues after the RF line card reboots.
When the upgrade process is completed, the following sample message is displayed, indicating that the upgrade was successful. Aug 4 09:06:31.571: %IOSXE_OIR-6-ONLINECARD: Card (cc) online in slot 1 Router# success Aug 4 09:11:45.764: %CMCC-3-FRU_HWPRG_UPG_PSOC_SUCCESS: CLC1: cmcc: Hardware programmable PSOCs on Line card in slot 1 were successfully programmed. Please power-cycle or OIR the card to make them work | ||
Step 5 | Power cycle the
Cisco cBR chassis or perform an OIR of the RF line card again.
The PSOC 0 and PSOC 1 versions are indicated in the display that appears after the chassis power-cycle or the RF line card OIR is complete and the RF line card reboots. This example shows the sample messages displayed after the RF line card reboots: Aug 4 09:16:18.124: %IOSXE_OIR-6-ONLINECARD: Card (cc) online in slot 1 LAB1_CBR8_DEMO# success LAB1_CBR8_DEMO# Aug 4 09:16:29.021: %BIPC-6-SESSION_UP: IPCCL Session to CLC1 is UP LAB1_CBR8_DEMO#sh plat diag Load for five secs: 1%/0%; one minute: 5%; five minutes: 3% Time source is NTP, 10:20:17.662 PORTUGAL-Summer Tue Aug 4 2015 Chassis type: CBR-8-CCAP-CHASS Slot: 0, CBR-CCAP-LC-40G Running state : ok Internal state : online Internal operational state : ok Physical insert detect time : 15:37:00 (00:59:22 ago) Software declared up time : 15:40:20 (00:56:01 ago) CPLD version : 00000021 Rommon version : 2011.03.12 Basestar version : 00110004 Raider version : 01010008 Caprica version : 00000020 PSOC 0 version : v4.6 PSOC 1 version : v4.6 Pic: 0/1, CBR-RF-PROT-PIC Internal state : inserted Physical insert detect time : 00:03:22 (16:32:59 ago) Firmware version: : 0000071E Slot: 1, CBR-CCAP-LC-40G Running state : ok Internal state : online Internal operational state : ok Physical insert detect time : 16:29:06 (00:07:15 ago) Software declared up time : 16:32:23 (00:03:59 ago) CPLD version : 00000021 Rommon version : 2011.03.12 Basestar version : 00110004 Raider version : 01010008 Caprica version : 00000020 PSOC 0 version : v4.6 PSOC 1 version : v4.6 Pic: 1/1, CBR-RF-PIC Internal state : inserted Physical insert detect time : 00:03:23 (16:32:59 ago) Firmware version: : 0000073E |
What to Do Next
Router#show platform hardware slot 1 psoc 0 version
Load for five secs: 29%/6%; one minute: 30%; five minutes: 31%
Time source is NTP, 10:20:17.662 PORTUGAL-Summer Tue Aug 4 2015
PSOC Version
version name version value
------------------------------------------------------
psoc_address 50-0063
reg_pmbus_revision 22
reg_mfr_id Cypress Semicon
reg_mfr_model 039 Power Spvr
reg_mfr_revision Version 2.0
reg_mfr_location Seattle, WA
reg_mfr_date 2013-09-04
reg_mfr_serial v3.0
Router#
Upgrading the Fan PSoC Image in the Cisco cBR
This section provides the procedure to upgrade the fan module PSoC.
You could identify the fan module hardware using the show platform hardware slot Pslot psoc 0 version command. The reg_ic_device_rev field shows the fan module firmware version.
Step 1 | Copy the
firmware package to harddisk.
copy tftp:xxx harddisk:
| ||||||
Step 2 | Run the
following upgrade command on the SUP IOS:
For Cisco IOS-XE Release 3.16.1S:
upgrade hw-programmable cable active_SUP fan pkg_name firmware_pkg_location_path
Example: Router#upgrade hw-programmable cable R0 fan pkg_name /harddisk/cbrsup-rp-hw-programmable-firmware.155-3.r.S3-ext.05.SPA.pkg For Cisco IOS-XE Release 3.16.0S:
upgrade hw-programmable cable active_SUP psoc pkg_name firmware_pkg_location_path
Example: Router#upgrade hw-programmable cable R0 psoc pkg_name /harddisk/cbrsup-rp-hw-programmable-firmware.155-3.r.S3-ext.02.SPA.pkg It takes approximately 15 minutes to upgrade the fan module PSoC for all the fan modules.
When the upgrade is complete, the messages that indicate that the hardware programmable PSoC on each fan module in each fan bay is upgraded successfully, are displayed. |
What to Do Next
Note | The following procedures are applicable only for Cisco IOS-XE Release 3.16.0S and not for Cisco IOS-XE Release 3.16.1S. |
Perform one of the following two procedures:
- OIR the Fan modules one by one. Do not remove the fan module fully from the chassis. Pull the fan modules out until the back connector is disconnected fully, then re-insert the fan module.
- Power cycle the Cisco cBR chassis.
Use the show platform hardware slot Pslot psoc 0 version command to check the firmware version for each slot and each of the two PSoCs on each fan module.
Upgrading Supervisor CPLD Firmware in the Cisco cBR
This section provides the procedure to upgrade the Supervisor CPLD firmware. The upgrade to Supervisor CPLD firmware version 16012711 is optional. Compared to the version 15091511, the version 16012711 provides SEU support. The customers can decide if they need to upgrade to the new Supervisor CPLD version at their own discretion.
Before upgrading the Supervisor CPLD firmware, make sure the following requirements are met:
-
Download Supervisor CPLD firmware from http://www.cisco.com
-
System running IOS-XE image: 3.16.0, 3.16.1, 3.16 engineering specials, and later releases
-
Console connections and login to both Supervisor cards
-
Run the following command to verify Supervisor CPLD firmware version on the cBR-8:
Command
Current Version
Upgrade Version
Package Name
show platform
15091511
16012711
cbrsup-rp-programmable-firmware.156-2.r.SP-ext.01.SPA.pkg
show platform
14121111
15091511
cbrsup-rp-hw-programmable-firmware.155-3.r.S3-ext.05.SPA.pkg
Step 1 | Copy the new
firmware package to the cBR-8 using FTP.
copy filename bootflash:
copy filename stby-bootflash:
Example: Router# copy ftp://location/cbrsup-rp-programmable-firmware.156-2.r.SP-ext.01.SPA.pkg bootflash: Router# copy ftp://location/cbrsup-rp-programmable-firmware.156-2.r.SP-ext.01.SPA.pkg stby-bootflash: | ||
Step 2 | Verify the
firmware package against the known md5 hash.
verify /md5 bootflash:filename
Example: Router# verify /md5 bootflash:cbrsup-rp-programmable-firmware.156-2.r.SP-ext.01.SPA.pkg | ||
Step 3 | Log into active SUP0 using console connection. | ||
Step 4 | Check if
there is any previous failed SUP0 and SUP1 CPLD or other firmware attempt and
delete if any.
dir bootflash:already_in_progress_file
delete bootflash:already_in_progress_file
dir stby-bootflash:already_in_progress_file
delete stby-bootflash:already_in_progress_file
| ||
Step 5 | Run the
following command to upgrade Viper firmware on SUP0 (R0) and SUP1 (R1):
upgrade hw-programmable cable R0 viper pkg_name filename
upgrade hw-programmable cable R1 viper pkg_name filename
Example: Router# upgrade hw-programmable cable R0 viper pkg_name /bootflash/cbrsup-rp-programmable-firmware.156-2.r.SP-ext.01.SPA.pkg Router# upgrade hw-programmable cable R1 viper pkg_name /bootflash/cbrsup-rp-programmable-firmware.156-2.r.SP-ext.01.SPA.pkg It takes about 10 minutes to upgrade. You should see the following messages when upgrade finished: Upgrade successfully. Please make sure Rommon version is matched. Please power cycle the chassis to let the new firmware take effect
| ||
Step 6 | To mitigate
the known modem registration rate issue, the following configuration commands
needs to be added.
Router# configure terminal Router(config)# platform punt-policer 24 50 Router(config)# platform punt-policer 24 50 high Router(config)# platform punt-policer 105 300 Router(config)# platform punt-policer 100 100 Router(config)# platform punt-sbrl wan punt-cause 10 rate 4 Router(config)# platform punt-sbrl wan punt-cause 11 rate 4 Router(config)# platform punt-sbrl wan punt-cause 24 rate 4 Router(config)# platform punt-sbrl subscriber rate 16 Router(config)# interface bundle x Router(config)# hold-queue 1024 in Router(config)# hold-queue 1024 out Router(config)# end Router(config)# write memory Router# | ||
Step 7 | Copy the
system startup-config to bootflash: and stby-bootflash: as a precaution.
copy startup-config bootflash:filename
copy startup-config stby-bootflash:filename
| ||
Step 8 | Set the
config register to 0, so both SUPs will boot in ROMMON mode after reset.
Router# configure terminal Router(config)# config-register 0x0 Router(config)# end Router# write memory | ||
Step 9 | Check console
connectivity on both SUP0 and SUP1. Then reload cBR-8.
Router# reload | ||
Step 10 | Confirm both
SUP0 and SUP1 are in ROMMON mode, and check bootflash on both SUPs.
Router# dir bootflash: | ||
Step 11 | Power cycle
the cBR-8. Wait for both SUP0 and SUP1 to load into ROMMON mode. You will see
the new CPLD version has been loaded on both SUPs from both console
connections.
rommon 1 > Initializing Hardware ... ? System Bootstrap, Version 15.5(3r)S, RELEASE SOFTWARE Copyright (c) 1994-2016 by cisco Systems, Inc. Current image running: Boot ROM1 Last reset cause: PowerOn Viper version register: 0x16012711 Set Chassis Type to 13RU Cisco cBR-8 platform with 50331648 Kbytes of main memory | ||
Step 12 | Boot the
IOS-XE on SUP0 and SUP1 from ROMMON.
boot bootflash:filename
| ||
Step 13 | Check the
CPLD firmware has been upgraded on both SUPs using the command below.
show platform
Example: Router# show platform Slot CPLD Version Rommon Version --------- ------------------- --------------------------------------- 0 00000021 2011.03.13 1 00000021 2011.03.13 2 00000021 2011.03.13 SUP0 16012711 15.5(3r)S SUP1 16012711 15.5(3r)S | ||
Step 14 | After
secondary SUP goes into STANDBY HOT state, set the config register back to
0x2102 (Both SUPs will be changed back to autoboot mode). Also check your boot
statement in config to point to the desired image.
Router# configure terminal Router(config)# config-register 0x2102 Router(config)# end Router# write memory | ||
Step 15 | Verify that
the bootvar has changed to point at the new image.
Router# show bootvar | ||
Step 16 | Verify that
the config-register has changed to point at the new image on next reboot.
Router# show redundancy |
Upgrading Docsis 3.0 downstream module and Docsis 3.1 downstream module (Cisco IOS-XE Release 3.18.0S and earlier releases)
This section provides the procedure to upgrade the Docsis 3.0 downstream and Docsis 3.1 downstream (DSPHY) module installed in Cisco cBR-8 router for Cisco IOS-XE Release 3.18.0S and earlier releases.
Before upgrading the module, make sure the following requirements are met:
-
Put the new IOS-XE image file image-file-name in bootflash via FTP using copy ftp://location/image-file-name bootflash: and copy ftp://location/image-file-name stby-bootflash: command.
-
Verify the IOS-XE image file against the known file md5 hash using verify /md5 image-file-name command.
-
Access to TSV, both console connections, all passwords including enable, and logging sessions for both supervisor cards.
-
Insert a USB drive into the supervisor front USB port just behind the small cover. Verify that the system can read the drive directory usb0:. Backup the configuration to USB drive before upgrade using copy running-config usb0: name.txt command.
-
Check if the redundancy is enabled using show redundancy command.
-
Perform standard pre-checks (total modems online, any 911 calls, etc). See verification section for show commands to verify system health before upgrade.
Step 1 | Change the boot
variable to point to desired IOS-XE image.
boot system bootflash:image-file-name no boot system end write memory | ||
Step 2 | Verify that
the bootvar has changed to point to the new image.
show bootvar
| ||
Step 3 | To mitigate
the known modem registration rate issue, the following configuration commands
needs to be added.
configure terminal no platform punt-policer 105 300 platform punt-policer 24 10 platform punt-policer 24 10 high platform punt-policer 100 10 ipv6 access-list dhcp_up permit ipv6 any host FF02::1:2 sequence 10 exit ip access-list extended dhcp_v4_up 10 permit ip host 0.0.0.0 host 255.255.255.255 exit class-map match-all dhcp_drop match access-group name dhcp_up class-map match-all dhcp_drop_v4 match access-group name dhcp_v4_up policy-map copp_policy class dhcp_drop police rate 100 pps conform-action transmit exceed-action drop class dhcp_drop_v4 police rate 100 pps conform-action transmit exceed-action drop interface bundle 10 hold-queue 1024 in hold-queue 1024 out end write memory | ||
Step 4 | Copy the
system startup-config to bootflash: and stby-bootflash: as a precaution.
copy startup-config bootflash:filename
copy startup-config stby-bootflash:filename
| ||
Step 5 | Check console
connectivity on both SUP0 and SUP1. Then reload cBR-8.
Router# reload | ||
Step 6 | Once the
system is up, check if it is running the new version of IOS-XE using
show
redundancy command. You will find following information in the
command output if the new IOS-XE image is running:
Image Version = Cisco IOS Software, cBR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), cbrsup-universalk9.03.16.01.S.155-3.S1-ext.SPA.bin
| ||
Step 7 | If the
chassis has DSPHY modules on the line cards, the firmware of each line card
will automatically upgrade. You need to watch the logs for a suggested line
card reload.
If you find following content in the output of the show log | include DSPHY command, it means an upgrade is taking place. router: CLC9: cdman: DSPHY downloading gemini 0 FW done, total packets 514 If you find following content in the output of the show log | include reload command, it means an upgrade is complete. router: CLC0: cdman: Suggest reload the line card for new FW to take effect using CLI:
| ||
Step 8 | Disable line
card redundancy for line card reloads.
configure terminal redundancy mode sso linecard-group 0 internal-switch no member slot 0 secondary end | ||
Step 9 | Verify that
there is no line card redundancy using
show run | begin
redundancy command. The following information will not appear in
the command output:
member slot 0 secondary | ||
Step 10 | At this point
you need to reload each line card and wait for the modems to come back online.
Reload one card at a time, allow approximate 5 minutes between each line card
reload. This helps to stagger the modem recovery and will be faster than
reloading all the line cards at once.
hw-module slot 0 reload hw-module slot 1 reload hw-module slot 2 reload hw-module slot 3 reload hw-module slot 4 reload hw-module slot 5 reload hw-module slot 6 reload hw-module slot 7 reload hw-module slot 8 reload hw-module slot 9 reload | ||
Step 11 | Check to see
if all DSPHY modules are upgraded.
show cable card 0/0 ds-phy display | include version show cable card 1/0 ds-phy display | include version show cable card 2/0 ds-phy display | include version show cable card 3/0 ds-phy display | include version show cable card 6/0 ds-phy display | include version show cable card 7/0 ds-phy display | include version show cable card 8/0 ds-phy display | include version show cable card 9/0 ds-phy display | include version | ||
Step 12 | Check for
DSPHY module detection status, repeat for each line card slot:
show cable card 0/0 ds-phy display | include detected show cable card 1/0 ds-phy display | include detected show cable card 2/0 ds-phy display | include detected show cable card 3/0 ds-phy display | include detected show cable card 6/0 ds-phy display | include detected show cable card 7/0 ds-phy display | include detected show cable card 8/0 ds-phy display | include detected show cable card 9/0 ds-phy display | include detected | ||
Step 13 | Check for
keepalive (KA) counts sent and received to match closely, repeat for each line
card slot:
show cable card 0/0 ds-phy display | include KA MicoAPSeSet show cable card 1/0 ds-phy display | include KA MicoAPSeSet show cable card 2/0 ds-phy display | include KA MicoAPSeSet show cable card 3/0 ds-phy display | include KA MicoAPSeSet show cable card 6/0 ds-phy display | include KA MicoAPSeSet show cable card 7/0 ds-phy display | include KA MicoAPSeSet show cable card 8/0 ds-phy display | include KA MicoAPSeSet show cable card 9/0 ds-phy display | include KA MicoAPSeSet | ||
Step 14 | Re-enable the
line card redundancy.
configure terminal redundancy mode sso linecard-group 0 internal-switch member slot 0 secondary end write memory | ||
Step 15 | Verify if the
redundancy has been re-enabled using
show run | begin
redundancy command. You can find following information in the
command output:
member slot 0 secondary |
What to Do Next
Perform verification test to determine if the upgrade is successful, include:
-
Check facility alarms using show facility-alarm status command.
Note
Some deployments use 5 power supplies which are sufficient, but will show an major alarm which can be ignored.
-
Check the status of the power supplies using show environment power command.
-
Check PS status using show platform hardware slot P<0-5> mcu status command.
-
Complete trace routes to known good off-network IP address using the source address of customer CPE blocks to verify routing is working.
-
Check logs for error messages using show log command.
These show commands may be useful in the verification test:
Upgrading Docsis 3.0 downstream module and Docsis 3.1 downstream module (Cisco IOS-XE Release 3.18.1S and later releases)
This section provides the procedure to upgrade the Docsis 3.0 downstream and Docsis 3.1 downstream (DSPHY) module installed in Cisco cBR-8 router for Cisco IOS-XE Release 3.18.1S and later releases.
From Cisco IOS-XE Release 3.18.1S, DSPHY module firmware upgrade will be changed from IOS bundled auto-upgrade to external programmable upgrades via manual FPD upgrade, it is mandatory to upgrade Docsis 3.1 downstream module to the latest FPD (cbrsup-rp-programmable-firmware.156-2.r.S1-ext.01.SPA.pkg) while moving to Cisco IOS-XE Release 3.18.1S image.
Note | This upgrade procedure is only applicable to Cisco IOS-XE Release 3.18.1S and later releases, upgrading from any release earlier, the FPD auto option is not supported. With the auto option, the firmwares that need upgrade can be determined by the system automatically and upgraded all at once, the whole process is more user-friendly and faster. |
Before upgrading the module, make sure the following requirements are met:
For non-LCHA enabled Chassis
Note | There is service impact during upgrade. |
Step 1 | Copy the
new DSPHY module firmware package to the hard disk of the cBR-8.
copy package name harddisk:
|
Step 2 | Verify the
new DSPHY module firmware package against the known md5 hash.
verify /md5 harddisk:package name
|
Step 3 | Upgrade the
DSPHY module firmware using the command below.
upgrade hw-programmable cable slot number dsphy auto pkg-name package name
Example: Router# upgrade hw-programmable cable 7 dsphy auto pkg-name /harddisk/cbrsup-rp-programmable-firmware.156-2.r.S1-ext.01.SPA.pkg |
Step 4 | Reload the
linecard when you see the "reload" instruction in the console CLI output for
the new firmware to take effect, service will be impacted during the linecard
reload.
*Mar 9 07:34:27.211: %IOSXE-5-PLATFORM: CLC7: cdman: Suggest reload the line card for new FW to take effect using CLI: hw slot <slot-id> reload Router# hw-module slot 7 reload |
Step 5 | After the
linecard is online after the reload, check DSPHY module version to confirm the
new firmware has taken effect.
Router# show cable card 7/0 ds-phy display | i ver img info: section 2, running ver 30016 (micro) img info: section 2, running ver 44147 (fpga) |
For LCHA enabled Chassis
Step 1 | Copy the
new DSPHY module firmware package to the hard disk of the cBR-8.
copy package name harddisk:
|
Step 2 | Verify the
new DSPHY module firmware package against the known md5 hash.
verify /md5 harddisk:package name
|
Step 3 | Upgrade the
protect linecard 0 when it is in stand-by hot state using the command below.
upgrade hw-programmable cable 0 dsphy auto pkg-name package name
Example: Router# upgrade hw-programmable cable 0 dsphy auto pkg-name /harddisk/cbrsup-rp-programmable-firmware.156-2.r.S1-ext.01.SPA.pkg |
Step 4 | Reload the
linecard when you see the "reload" instruction in the console CLI output for
the new firmware to take effect.
*Mar 9 07:34:27.211: %IOSXE-5-PLATFORM: CLC0: cdman: Suggest reload the line card for new FW to take effect using CLI: hw slot <slot-id> reload Router# hw-module slot 0 reload |
Step 5 | Wait until
the protect linecard 0 becomes stand-by warm state, check DSPHY module version
to confirm the new firmware has taken effect.
Router# show cable card 0/0 ds-phy display | i ver img info: section 2, running ver 30016 (micro) img info: section 2, running ver 44147 (fpga) |
Step 6 | Upgrade the
first working linecard using the command below.
upgrade hw-programmable cable slot number dsphy auto pkg-name package name
Example: Router# upgrade hw-programmable cable 1 dsphy auto pkg-name /harddisk/cbrsup-rp-programmable-firmware.156-2.r.S1-ext.01.SPA.pkg |
Step 7 | Reload the
linecard when you see the "reload" instruction in the console CLI output for
the new firmware to take effect.
*Mar 9 07:34:27.211: %IOSXE-5-PLATFORM: CLC1: cdman: Suggest reload the line card for new FW to take effect using CLI: hw slot <slot-id> reload Router# hw-module slot 1 reload |
Step 8 | When the linecard reload command is executed, a linecard switchover will be triggered for service protection. When the original working linecard is back online after the reload, perform linecard revertback. |
Step 9 | Check DSPHY
module version to confirm the new firmware has taken effect on the first
working linecard.
Router# show cable card 1/0 ds-phy display | i ver img info: section 2, running ver 30016 (micro) img info: section 2, running ver 44147 (fpga) |
Step 10 | Wait until the protect linecard 0 goes to standby-hot state, perform step 6 to 9 on the other working linecards one by one. |