Upgrading from Cisco IOS XE 16.x and later releases to Cisco IOS XE Cupertino 17.9.1y1
Prerequisites
Manual ROMMON Upgrade
If you are upgrading from Cisco IOS XE Everest 16.6.x or Cisco IOS XE Fuji 16.7.x to Cisco IOS XE Cupertino 17.9.1y1, perform the following steps to upgrade SUP ROMMON manually.
-
Download hardware programmable devices upgrade package file cbrsup-programmable_firmware.17.09.01y1.SPA.pkg from the following Cisco.com Software Center URL: https://software.cisco.com/download/home/286283913/type
-
Copy the package file to harddisk:.
copy <location>/cbrsup-programmable_firmware.17.09.01y1.SPA.pkg harddisk:
-
Verify the hardware programmable devices upgrade package against the md5 hash as provided in the Cisco.com Software center.
verify /md5 harddisk:cbrsup-programmable_firmware.17.09.01y1.SPA.pkg
-
Upgrade SUP ROMMON.
Router#upgrade rom-mon file harddisk:cbrsup-programmable_firmware.17.09.01y1.SPA.pkg r0 Wait for the following output on the console: ROMMON upgrade complete. To make the new ROMMON permanent, you must restart the RP Router#upgrade rom-mon file harddisk:cbrsup-programmable_firmware.17.09.01y1.SPA.pkg r1 Wait for the following output on the console: ROMMON upgrade complete. To make the new ROMMON permanent, you must restart the RP
Note
Do not restart the SUPs currently, you can combine reloading the SUP with the IOS upgrade process.
Downstream-Controller Remapping (CBR-CCAP-LC-G2-R with 8x10G DPIC)
If you are using cBR CCAP 8x10G Remote PHY Digital Physical Interface Card (D-PIC) with CBR-CCAP-LC-G2-R linecards, contact your local Cisco representative before upgrading to Cisco IOS XE Cupertino 17.9.1y1.
Starting with in Cisco IOS XE Cupertino 17.6.1, Cisco introduces a new feature on cBR-8 that provides initial support for 32 Video and 32 DOCSIS service groups per CBR-CCAP-LC-G2-R linecard. The implementation of this feature introduces new 8x10G DPIC port mapping constraints on existing 'Downstream-Cable' controllers. Cisco has prepared a python tool that can be used to determine if a cBR-8 running-configuration includes non-compliant controller mappings, and, to update the running-confirguration to be compliant with the latest Cisco IOS XE Cupertino 17.9.1y1. Once you have the python tool, perform the following steps in order to predict and avoid downtime:
Before you begin: Special considerations must be taken when using SmartPHY. Contact your local Cisco representative if your installation includes SmartPHY.
-
Collect the following information from the target cBR-8 to upgrade.
Router#show cable rpd sum Router#show cable modem sum Router#show cable video session all sum
-
Save the running configuration to the harddisk of the cBR-8.
Router#copy running-config harddisk:SavedConfig.txt
-
Copy the saved running configuration from harddisk: to an offline server for editing using SCP.
Router#copy harddisk:SavedConfig.txt scp:<path>
-
Run the python tool to modify the controllers in the saved configuration.
-
Option 1 - Renumber Downstream-Cable controllers only
-
Execute python script kobol_ph2_controller_migration.py. This script is intended for customers who do not immediately intend to take advantage of the Downstream-Video controllers and expanded SG capacity on CBR-CCAP-LC-G2-R.
$ python kobol_ph2_controller_migration.py Enter the name of the configuration file: SavedConfig.txt
-
Output file appends _remap_controller to the file name.
Output file name: SavedConfig.txt_remap_controller
-
Check to ensure that the script completed successfully. If no output file is created or the size of the output file is 0 byte, then check script output for error messages.
-
-
Option 2 - Renumber Downstream-Cable and utilize Downstream-Video controllers
-
Execute python script kobol_ph2_controller_migration_video.py. This script is intended for customers who wish to utilize the new Downstream-Video controllers to free up existing Downstream-Cable controllers for expanded DOCSIS service groups.
$ python kobol_ph2_controller_migration_video.py Enter the name of the configuration file: SavedConfig.txt
-
Output file appends _remap_controller_video to the file name.
Output file name: SavedConfig.txt_remap_controller_video
-
Check to ensure that the script completed successfully. If no output file is created or the size of the output file is 0 byte, then check script output for error messages.
-
-
-
Modify the remapped configuration file to specify the Cisco IOS XE Cupertino 17.9.1y1 image in the boot parameter.
boot system harddisk:cbrsup-universalk9.17.09.01y1.SPA.bin
-
Copy the final remapped configuration file back to the cBR-8 harddisk.
Router#copy scp:<path>/SavedConfig.txt_remap_controller harddisk:
or
Router#copy scp:<path>/SavedConfig.txt_remap_controller_video harddisk:
-
Copy remapped configuration file to startup of the cBR-8.
Router#copy harddisk:SavedConfig.txt_remap_controller startup-config
or
Router#copy harddisk:SavedConfig.txt_remap_controller_video startup-config
After performing the remapping procedure, monitor the chassis for any of the following errors after reload:
Mismatches TE interface. DS controller should be */*/0~7, configuration failed.
Mismatches TE interface. DS controller should be */*/8~15, configuration failed.
Mismatches TE interface. DS controller should be */*/16~23, configuration failed.
Mismatches TE interface. DS controller should be */*/24~31, configuration failed.
Upgrading using reload
Before you begin
Note |
If you are upgrading from Cisco IOS XE Everest 16.6.x or Cisco IOS XE Fuji 16.7.x to Cisco IOS XE Cupertino 17.9.1y1, perform pre-upgrade steps 1 to 4 to upgrade SUP ROMMON manually before proceeding with IOS upgrading. |
Upgrading from 17.6.1y or Earlier Images
If upgrading from 17.6.1y or earlier, you must copy .pkg files individually to the cBR-8. The tarball below contains all 20 packages and the packages.conf file that are required for upgrading. Before upgrading the system, make sure the following requirements are met:
-
Download the 17.9.1y1 tarball file from Cisco.com Software Center to a local server, using the following URL: https://software.cisco.com/download/home/286283913/type
-
IOS XE Software Version 17.09.01y1: cbrsup-universalk9.17.09.01y1.SPA.pkgs.tar.
-
-
Untar the archive on the local server.
Procedure
Step 1 |
Create a new folder on the cBR-8: harddisk:XE-179-1y.
|
Step 2 |
Create a new folder on the cBR-8: stby-harddisk:XE-179-1y.
|
Step 3 |
Copy the
Repeat for all |
Step 4 |
Copy the
Repeat for all |
Step 5 |
Verify the hardware programmable devices upgrade package against the md5 hash as provided in the Cisco.com Software center.
|
Step 6 |
Configure the system to boot in sub-package mode.
|
Step 7 |
Save the configuration
|
Step 8 |
Reload the system
|
Upgrading from 17.6.1z or Later Images
Before upgrading the system, make sure the following requirements are met.
-
Download two files from the following Cisco.com Software Center URL.
https://software.cisco.com/download/home/286283913/type
-
IOS XE Software Version 17.09.01y1. cbrsup-universalk9.17.09.01y1.SPA.bin
-
IOS XE Hardware Programmable Devices Version 17.9.1y1. cbrsup-programmable_firmware.17.09.01y1.SPA.pkg
-
Procedure
Step 1 |
Copy the Cisco IOS XE Cupertino 17.9.1y1 IOS image to harddisk: and stby-harddisk:.
|
||
Step 2 |
Verify the Cisco IOS XE Cupertino 17.9.1y1 IOS image against the md5 hash as provided in the Cisco.com Software center. The md5 hash check may not support images greater than 2.3 GB in size.
|
||
Step 3 |
Copy the hardware programmable devices upgrade package to harddisk: if the file has not been copied already.
|
||
Step 4 |
Verify the hardware programmable devices upgrade package against the md5 hash as provided in the Cisco.com Software center.
|
||
Step 5 |
Configurethe system to boot with the Cisco IOS XE Cupertino 17.9.1y1 image.
|
||
Step 6 |
Save the configuration.
|
||
Step 7 |
Reload the system
|
What to do next
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.
-
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.
-
show redundancy
-
show platform
-
show platform diag
-
show environment
-
show redundancy linecard all
-
show isis neighbors
-
show ip ospf neighbor
-
show ip route rip
-
show ip mroute
-
show cops servers
-
show cable modem voice
-
show cable calls
-
show cable metering verbose
-
show cable licenses all
-
show inventory
Upgrading with ISSU for I-CCAP Systems
Before you begin
Note |
|
Before upgrading the system, make sure the following requirements are met:
-
The cBR-8 has two SUPs installed.
Router# show redundancy | include Location|state Active Location = slot 4 Current Software state = ACTIVE Uptime in current state = 2 days, 21 hours, 37 minutes Standby Location = slot 5 Current Software state = STANDBY HOT Uptime in current state = 2 days, 21 hours, 30 minutes
-
Standby SUP must be in hot standby state.
Router# show redundancy | include Location|state Active Location = slot 4 Current Software state = ACTIVE Uptime in current state = 2 days, 21 hours, 37 minutes Standby Location = slot 5 Current Software state = STANDBY HOT Uptime in current state = 2 days, 21 hours, 30 minutes
-
Line card redundancy is in stable state with state Active and Stdby warm.
Router# show redundancy linecard all Load for five secs: 14%/1%; one minute: 8%; five minutes: 8% Time source is NTP, 15:23:26.697 PST Thu Jan 17 2019 LC My Peer Peer Peer Slot Subslot Group State State Slot Subslot Role Mode -------------------------------------------------------------------------------- 1 - 0 Active Stdby Warm 0 - Active Primary 2 - 0 Active Stdby Warm 0 - Active Primary 3 - 0 Active Stdby Warm 0 - Active Primary 6 - 0 Active Stdby Warm 0 - Active Primary 0 - 0 - - Multiple None Standby Secondary
-
Auto-boot is enabled.
Router# show bootvar Load for five secs: 14%/0%; one minute: 14%; five minutes: 10% Time source is NTP, 15:46:59.837 PST Thu Jan 17 2019 BOOT variable = harddisk:IOSXE/packages.conf,12; CONFIG_FILE variable = BOOTLDR variable does not exist Configuration register is 0x2102 Standby BOOT variable = harddisk:IOSXE/packages.conf,12; Standby CONFIG_FILE variable = Standby BOOTLDR variable does not exist Standby Configuration register is 0x2102
-
Both SUPs are in the sub-package mode, running the same image from the same path.
Router# show bootvar Load for five secs: 14%/0%; one minute: 14%; five minutes: 10% Time source is NTP, 15:46:59.837 PST Thu Jan 17 2019 BOOT variable = harddisk:IOSXE/packages.conf,12; CONFIG_FILE variable = BOOTLDR variable does not exist Configuration register is 0x2102 Standby BOOT variable = harddisk:IOSXE/packages.conf,12; Standby CONFIG_FILE variable = Standby BOOTLDR variable does not exist Standby Configuration register is 0x2102
-
The free space on boot device on both SUPs must be greater than 2.3GB.
Router# dir harddisk: | include bytes total 7804653568 bytes total (5691174912 bytes free)
-
Download two files from the following Cisco.com Software Center URL:
https://software.cisco.com/download/home/286283913/type
-
IOS XE Software Version 17.9.1y1: cbrsup-universalk9.17.09.01y1.SPA.bin
-
IOS XE Hardware Programmable Devices Version 17.9.1y1: cbrsup-programmable_firmware.17.09.01y1.SPA.pkg
-
-
Copy the target consolidated image cbrsup-universalk9.17.09.01y1.SPA.bin to the active SUP in the same directory of the packages.conf file that the system is booted up with.
Procedure
Step 1 |
Copy Cisco IOS XE Cupertino 17.9.1y1 image to harddisk:.
|
Step 2 |
Verify Cisco IOS XE Cupertino 17.9.1y1 image against the md5 hash as provided in the Cisco.com Software center.
|
Step 3 |
Copy the hardware programmable devices upgrade package to harddisk: if the file has not been copied already.
|
Step 4 |
Verify the hardware programmable devices upgrade package against the md5 hash as provided in the Cisco.com Software center.
|
Step 5 |
Check system status prior to upgrade. Save the information to compare against the system status after upgrade. For the commands to use to check the status, see the show commands at the end of this section. |
Step 6 |
Perform ISSU.
|
Step 7 |
To monitor the ISSU progress, use the command below.
|
Step 8 |
Use these CLI to check status after ISSU.
|
What to do next
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.
-
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:
-
show redundancy
-
show platform
-
show platform diag
-
show environment
-
show redundancy linecard all
-
show isis neighbors
-
show ip ospf neighbor
-
show ip route rip
-
show ip mroute
-
show cops servers
-
show cable modem voice
-
show cable calls
-
show cable metering verbose
-
show cable licenses all
-
show inventory