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.
This section contains the upgrade procedures for the Cisco cBR-8 Router System, including both the IOS-XE software and firmwares used in the router. If you need to upgrade only the firmware, see Upgrading the Cisco cBR-8 Router Firmware.
This use case provides the example procedure to upgrade a Cisco cBR-8 router to IOS-XE release 3.18.1SP from earlier versions.
Note | If the system image is upgraded using ISSU, after the ISSU upgrade is finished, use hw-module subslot 4/1 reload and hw-module subslot 5/1 reload commands to upgrade the SUP MAC firmware. |
Download the new
image package from the following URL:
Copy the new
image package to the cBR-8 using TFTP.
Verify the new
image package against the known md5 hash.
copy tftp://<location>/cbrsup-universalk9.03.18.01.SP.156-2.SP1-ext.SPA.bin bootflash:
copy tftp://<location>/cbrsup-universalk9.03.18.01.SP.156-2.SP1-ext.SPA.bin stby-bootflash:
verify /md5 bootflash:cbrsup-universalk9.03.18.01.SP.156-2.SP1-ext.SPA.bin
verify /md5 stby-bootflash:cbrsup-universalk9.03.18.01.SP.156-2.SP1-ext.SPA.bin
The correct firmware versions after the upgrade are listed in the tables below. Use the commands in the tables to verify the firmware versions.
Firmware |
Correct Version |
Command |
Supervisor CPLD |
16012711 |
show platform |
Supervisor ROMMON |
15.5(3r)S |
show platform |
Linecard CPLD |
00000021 |
show platform |
Linecard ROMMON |
2011.03.13 |
show platform |
Linecard PSOC 1 |
v4.6 |
show platform diag |
Linecard PSOC 2 |
v4.6 |
show platform diag |
Docsis 3.0 downstream module Micro |
1000e |
show platform diag |
Docsis 3.1 downstream module Micro |
30016 |
show platform diag |
Docsis 3.1 downstream module FPGA |
44147 |
show platform diag |
Make sure the Cisco cBR-8 router software is upgraded to Cisco IOS-XE release 3.18.1SP.
Note | If the Cisco IOS-XE release is 3.18.1S or 3.18.0SP before upgrading to Cisco IOS-XE release 3.18.1SP, the downstream module upgrade procedure can be performed before Cisco IOS-XE software upgrade, in this way, there is no need to reset the linecard during the upgrade, since linecard will be reloaded during Cisco IOS-XE software upgrade. |
For detailed upgrading steps, see Upgrading Docsis 3.0 downstream module and Docsis 3.1 downstream module (Cisco IOS-XE Release 3.18.1S and later releases).
If there is other firmware that needs upgrade, see Upgrading the Cisco cBR-8 Router Firmware for details.
This use case provides the example procedure to upgrade a Cisco cBR-8 router to IOS-XE release 3.18.0SP from earlier versions. ISSU is not applicable in this case.
Download the
new image package from the following URL:
Copy the new
image package to the cBR-8 using TFTP.
Verify the new
image package against the known md5 hash c244aa64b4af3d7bfa7826ef46eda47f.
copy tftp://<location>/cbrsup-universalk9.03.18.00.SP.156-2.SP-ext.SPA.bin bootflash:
copy tftp://<location>/cbrsup-universalk9.03.18.00.SP.156-2.SP-ext.SPA.bin stby-bootflash:
verify /md5 bootflash:cbrsup-universalk9.03.18.00.SP.156-2.SP-ext.SPA.bin
verify /md5 stby-bootflash:cbrsup-universalk9.03.18.00.SP.156-2.SP-ext.SPA.bin
Once the system is up, make sure that it is running the new version Version 03.18.00.SP.156-2.SP-ext using show version command.
Below is a sample output:
router# show version Load for five secs: 82%/3%; one minute: 46%; five minutes: 45% Time source is NTP, 12:24:50.303 PDT Wed Jul 27 2016 Cisco IOS XE Software, Version 03.18.00.SP.156-2.SP-ext Cisco IOS Software, cBR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.6(2)SP, RELEASE SOFTWARE (fc2) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2016 by Cisco Systems, Inc. Compiled Wed 27-Jul-16 04:49 by mcpre Cisco IOS-XE software, Copyright (c) 2005-2016 by cisco Systems, Inc. All rights reserved. Certain components of Cisco IOS-XE software are licensed under the GNU General Public License ("GPL") Version 2.0. The software code licensed under GPL Version 2.0 is free software that comes with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such GPL code under the terms of GPL Version 2.0. For more details, see the documentation or "License Notice" file accompanying the IOS-XE software, or the applicable URL provided on the flyer accompanying the IOS-XE software. ROM: IOS-XE ROMMON router uptime is 29 minutes Uptime for this control processor is 33 minutes System returned to ROM by reload at 11:48:48 PDT Wed Jul 27 2016 System restarted at 11:54:58 PDT Wed Jul 27 2016 System image file is "bootflash:cbrsup-universalk9.03.18.00.SP.156-2.SP-ext.SPA.bi" Last reload reason: Reload Command This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately. A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html If you require further assistance please contact us by sending email to export@cisco.com. cisco cBR1013 (CBR) processor (revision CBR) with 13397499K/6147K bytes of memory. Processor board ID FXS1947Q0DA 16 Gigabit Ethernet interfaces 32768K bytes of non-volatile configuration memory. 50331648K bytes of physical memory. 7739391K bytes of eUSB flash at bootflash:. 97620247K bytes of SATA hard disk at harddisk:. 31422288K bytes of USB flash at usb0:. Configuration register is 0x2102
The correct firmware versions after the upgrade are listed in the tables below. Use the commands in the tables to verify the firmware versions.
Firmware |
Correct Version |
Command |
Supervisor CPLD |
16012711 |
show platform |
Docsis 3.1 downstream module Micro |
3.13 |
show platform |
Docsis 3.1 downstream module FPGA |
4.4141 |
show platform |
Make sure the Cisco cBR-8 router software is upgraded to Cisco IOS-XE release 3.18.0SP.
For detailed upgrading steps, see Upgrading Supervisor CPLD Firmware in the Cisco cBR.
For detailed upgrading steps, see Upgrading Docsis 3.0 downstream module and Docsis 3.1 downstream module (Cisco IOS-XE Release 3.18.1S and later releases).
If there is other firmware that needs upgrade, see Upgrading the Cisco cBR-8 Router Firmware for details.
Cisco cBR-8 Routers support the In-Service Software Upgrades (ISSU) for redundant platforms. The ISSU process allows software to be updated or otherwise modified while packet forwarding continues with the benefit of LCHA. ISSU supports subpackage software upgrade mode. For more information, please refer to Cisco IOS-XE In-Service Software Upgrade Process.
This use case provides the example procedure to upgrade a Cisco cBR-8 router from IOS-XE release 3.17.0S to IOS-XE release 3.17.1S with subpackage mode.
Before upgrading the system, make sure the following requirements are met:
Verify the chassis is in subpackage mode.
If the chassis is not in subpackage mode, change it to subpackage mode following the steps below:
Expand the IOS-XE binary image file to a specific image based directory in the bootflash using the following commands:
request platform software package expand file bootflash: cbrsup-universalk9.03.17.00.S.156-1.S-std.SPA.bin to bootflash:/XE317/ wipe request platform software package expand file stby-bootflash: cbrsup-universalk9.03.17.00.S.156-1.S-std.SPA.bin to stby-bootflash:/XE317/ wipe
Verify that the following list of sub-packages and helper files are created in the directory using dir bootflash:/XE317/ and dir stby-bootflash:/XE317/ commands.
File |
Size (Bytes) |
---|---|
cbrsup-cciomdsup.03.17.00.S.156-1.S-std.SPA.pkg |
28523472 |
cbrsup-clc-firmware.03.17.00.S.156-1.S-std.SPA.pkg |
125895640 |
cbrsup-clccontrol.03.17.00.S.156-1.S-std.SPA.pkg |
13757412 |
cbrsup-clcdocsis.03.17.00.S.156-1.S-std.SPA.pkg |
12731364 |
cbrsup-clcios.03.17.00.S.156-1.S-std.SPA.pkg |
31560672 |
cbrsup-clciosdb.03.17.00.S.156-1.S-std.SPA.pkg |
31558628 |
cbrsup-clcmipsbase.03.17.00.S.156-1.S-std.SPA.pkg |
121236229 |
cbrsup-clcvideo.03.17.00.S.156-1.S-std.SPA.pkg |
13859812 |
cbrsup-espx86base.03.17.00.S.156-1.S-std.SPA.pkg |
114570324 |
cbrsup-packages-universalk9.03.17.00.S.156-1.S-std.conf |
15440 |
cbrsup-rp-firmware.03.17.00.S.156-1.S-std.SPA.pkg |
35701712 |
cbrsup-rp-programmable-firmware.03.17.00.S.156-1.S-std.SPA.pkg |
2786272 |
cbrsup-rpaccess.03.17.00.S.156-1.S-std.SPA.pkg |
23290836 |
cbrsup-rpbase.03.17.00.S.156-1.S-std.SPA.pkg |
48516176 |
cbrsup-rpcontrol.03.17.00.S.156-1.S-std.SPA.pkg |
59235284 |
cbrsup-rpios-universalk9.03.17.00.S.156-1.S-std.SPA.pkg |
180753380 |
cbrsup-rpvideo.03.17.00.S.156-1.S-std.SPA.pkg |
7455696 |
packages.conf |
16220 |
Change boot statement to point to the subpackage mode using following commands:
configure terminal no boot system boot system bootflash:/XE317/cbrsup-packages-universalk9.03.17.00.S.156-1.S-ext.conf end write memory
Verify peer SUP is in hot standby state using show redundancy command.
Switchover from SUP0 to SUP1 using redundancy force-switchover command.
Wait and verify SUP0 is in hot standby state using show redundancy command.
Switchover from SUP1 to SUP0 using redundancy force-switchover command.
Wait and verify SUP1 is in hot standby state using show redundancy command.
Verify the system is running in subpackage mode using show version command. System image file should point to a .conf package file. Below is a sample output:
cBR8-01 uptime is 6 weeks, 4 days, 5 hours, 36 minutes Uptime for this control processor is 6 weeks, 4 days, 4 hours, 57 minutes System returned to ROM by SSO Switchover at 10:33:32 est Thu Nov 19 2015 System restarted at 11:19:15 est Thu Nov 19 2015 System image file is "bootflash:/Upgrade/packages.conf"
Verify the directory in which the .conf file is booted. You will see packages.conf along with a list of package files ending with SPA.pkg.
Verify both SUPs are running the same image from the same path using show version | include image command. Below is a sample output:
Router# show version | include image System image file is "bootflash:XE317/packages.conf"
Verify autoboot is enabled using show bootvar command. Below is a sample output:
Router# show bootvar BOOT variable = bootflash:XE317/packages.conf,12; CONFIG_FILE variable = BOOTLDR variable does not exist Configuration register is 0x2102 Standby BOOT variable = bootflash:XE317/packages.conf,12; Standby CONFIG_FILE variable = Standby BOOTLDR variable does not exist Standby Configuration register is 0x2102
Verify both SUPs are in SSO mode, standby SUP is in hot standby mode using show redundancy state command. Below is a sample output:
Router# show redundancy state my state = 13 -ACTIVE peer state = 8 -STANDBY HOT Mode = Duplex Unit = Primary Unit ID = 48 Redundancy Mode (Operational) = sso Redundancy Mode (Configured) = sso Redundancy State = sso Maintenance Mode = Disabled Manual Swact = enabled Communications = Up client count = 119 client_notification_TMR = 30000 milliseconds RF debug mask = 0x0
Make sure there is enough bootflash disk space on both SUPs (available space more than 1.8GB).
Verify the IOS-XE release 3.17.1S image file against the known file md5 hash using verify /md5 cbrsup-universalk9.03.17.01.S.156-1.S1-std.SPA.bin command.
Put IOS-XE release 3.17.1S image cbrsup-universalk9.03.17.01.S.156-1.S1-std.SPA.bin in the same folder as current boot package on active SUP using dir bootflash:/XE317/cbrsup-universalk9.03.17.01.S.156-1.S1-std.SPA.bin command.
Verify .issu folder and config files exists on both active and standby SUP hard disk using dir harddisk:.issu/ command. Below is a sample output:
Router# dir harddisk:.issu/ Directory of harddisk:/.issu/ 11108354 -rw- 16220 Mar 7 2016 14:03:12 +08:00 0.conf 11108355 -rw- 16220 Mar 7 2016 14:03:14 +08:00 1.conf 11108356 -rw- 16220 Mar 7 2016 14:03:15 +08:00 2.conf 11108357 -rw- 16220 Mar 7 2016 14:03:21 +08:00 3.conf 11108358 -rw- 16220 Mar 7 2016 14:03:23 +08:00 6.conf 11108359 -rw- 16220 Mar 7 2016 14:03:23 +08:00 7.conf 11108360 -rw- 16220 Mar 7 2016 14:03:26 +08:00 8.conf 11108361 -rw- 16220 Mar 7 2016 14:06:25 +08:00 9.conf 11108362 -rw- 16220 Mar 7 2016 14:18:14 +08:00 rp.conf 11108363 -rw- 16220 Mar 7 2016 14:18:18 +08:00 remote_rp.conf Router# dir stby-harddisk:.issu/ Directory of stby-harddisk:/.issu/ 3670018 -rw- 16220 Mar 7 2016 14:18:53 +08:00 rp.conf 3670019 -rw- 16220 Mar 7 2016 14:19:03 +08:00 remote_rp.conf 3670020 -rw- 16220 Mar 7 2016 14:19:29 +08:00 0.conf 3670021 -rw- 16220 Mar 7 2016 14:19:38 +08:00 1.conf 3670022 -rw- 16220 Mar 7 2016 14:19:43 +08:00 2.conf 3670023 -rw- 16220 Mar 7 2016 14:19:47 +08:00 3.conf 3670024 -rw- 16220 Mar 7 2016 14:19:51 +08:00 6.conf 3670025 -rw- 16220 Mar 7 2016 14:19:56 +08:00 7.conf 3670026 -rw- 16220 Mar 7 2016 14:20:00 +08:00 8.conf 3670027 -rw- 16220 Mar 7 2016 14:20:05 +08:00 9.conf
If there is no such folder or file is missing, create a new one and generate files needed. Below are sample commands:
Router# mkdir harddisk:.issu Router# mkdir stby-harddisk:.issu Router# copy bootflash:/XE317/packages.conf harddisk:.issu/rp.conf Router# copy bootflash:/XE317/packages.conf harddisk:.issu/remote_rp.conf Router# copy bootflash:/XE317/packages.conf harddisk:.issu/0.conf Router# copy bootflash:/XE317/packages.conf harddisk:.issu/1.conf Router# copy bootflash:/XE317/packages.conf harddisk:.issu/2.conf Router# copy bootflash:/XE317/packages.conf harddisk:.issu/3.conf Router# copy bootflash:/XE317/packages.conf harddisk:.issu/6.conf Router# copy bootflash:/XE317/packages.conf harddisk:.issu/7.conf Router# copy bootflash:/XE317/packages.conf harddisk:.issu/8.conf Router# copy bootflash:/XE317/packages.conf harddisk:.issu/9.conf Router# copy harddisk:.issu/rp.conf stby-harddisk:.issu/rp.conf Router# copy harddisk:.issu/remote_rp.conf stby-harddisk:.issu/remote_rp.conf Router# copy harddisk:.issu/0.conf stby-harddisk:.issu/0.conf Router# copy harddisk:.issu/1.conf stby-harddisk:.issu/1.conf Router# copy harddisk:.issu/2.conf stby-harddisk:.issu/2.conf Router# copy harddisk:.issu/3.conf stby-harddisk:.issu/3.conf Router# copy harddisk:.issu/6.conf stby-harddisk:.issu/6.conf Router# copy harddisk:.issu/7.conf stby-harddisk:.issu/7.conf Router# copy harddisk:.issu/8.conf stby-harddisk:.issu/8.conf Router# copy harddisk:.issu/9.conf stby-harddisk:.issu/9.conf
Note | The file with digital as the name corresponds with line card slot, the above example is for fully loaded chassis. If target system is not fully loaded, just copy the files named with inserted slot number. |
Step 1 | Perform RP
only ISSU.
request platform software package install node file bootflash:XE317/cbrsup-universalk9.03.17.01.S.156-1.S1-std.SPA.bin noreload linecard
| ||
Step 2 | Attach to
ISSU progress status tracking mode after SUP switchover. User can use Ctrl+C to
exit to perform other command if needed.
request platform software package install node attach
Below is a sample output: NOTE: Currently node has booted from a provisioning file NOTE: Going to resume a dual rp sub-pakcage node ISSU install --- Starting wait for Standby RP to reach terminal redundancy state --- | ||
Step 3 | Reset
secondary line card (change slot 0 to secondary slot on target chassis).
hw-module slot 0 reload
| ||
Step 4 | Upgrade all
line cards.
request platform software package install node linecard-only all
|
Perform verification test to determine if the upgrade is successful, include:
Verify the router is running the new IOS-XE release using show version command.
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: