-
- Downstream Interface Configuration
- Upstream Interface Configuration
- DOCSIS Interface and Fiber Node Configuration
- DOCSIS Load Balancing Groups
- DOCSIS Load Balancing Movements
- DOCSIS 3.0 Downstream Bonding
- DOCSIS 2.0 A-TDMA Modulation Profiles
- Downstream Resiliency Bonding Group
- Downstream Channel ID Assignment
- Upstream Channel Bonding
- Spectrum Management and Advanced Spectrum Management
- Upstream Scheduler Mode
- Generic Routing Encapsulation
- Transparent LAN Service over Cable
- Downgrading Channel Bonding in Battery Backup Mode
- Energy Management Mode
-
- IP Access Control Lists
- Creating an IP Access List and Applying It to an Interface
- Creating an IP Access List to Filter IP Options, TCP Flags, Noncontiguous Ports
- Refining an IP Access List
- IP Named Access Control Lists
- IPv4 ACL Chaining Support
- IPv6 ACL Chaining with a Common ACL
- Commented IP Access List Entries
- Standard IP Access List Logging
- IP Access List Entry Sequence Numbering
- ACL IP Options Selective Drop
- ACL Syslog Correlation
- IPv6 Access Control Lists
- IPv6 Template ACL
- IPv6 ACL Extensions for Hop by Hop Filtering
-
- Call Home
- SNMP Support over VPNs—Context-Based Access Control
- SNMP Cache Engine Enhancement
- Onboard Failure Logging
- Control Point Discovery
- IPDR Streaming Protocol
- Usage-Based Billing (SAMIS)
- Frequency Allocation Information for the Cisco CMTS Routers
- Flap List Troubleshooting
- Maximum CPE and Host Parameters
- SNMP Background Synchronization
- Online Offline Diagnostics
- Index
- Hardware Compatibility Matrix for Cisco cBR Series Routers
- How to Configure In-Service Software Upgrade
Cisco IOS-XE In-Service Software Upgrade Process
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 two different software upgrade modes:
For the Cisco cBR Series Routers, ISSU-compatibility depends on the software subpackage being upgraded and the hardware configuration. Consolidated packages are ISSU-compatible in dual SUP configurations only and have other limitations described later in this document.
The specific procedures in this document represent supported and tested installation sequences. The Cisco IOS-XE system software allows other installation sequences for special purposes under the guidance of Cisco customer support representatives, but the steps in this document should be followed otherwise. These steps should be followed completely, as the Cisco cBR Series Routers are designed to run one version of Cisco IOS-XE for all consolidated packages and subpackages on an SUP, and running subpackages from different versions of Cisco IOS-XE can cause unexpected router behavior.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/. An account on http://www.cisco.com/ is not required.
Contents
- Hardware Compatibility Matrix for Cisco cBR Series Routers
- How to Configure In-Service Software Upgrade
- Additional References
- Feature Information for In-Service Software Upgrade
Hardware Compatibility Matrix for Cisco cBR Series Routers
Note | The hardware components introduced in a given Cisco IOS-XE Release are supported in all subsequent releases unless otherwise specified. |
Cisco CMTS Platform |
Processor Engine |
Interface Cards |
---|---|---|
Cisco cBR-8 Converged Broadband Router |
Cisco IOS-XE Release 3.15.0S and Later Releases Cisco cBR-8 Supervisor:
|
Cisco IOS-XE Release 3.15.0S and Later Releases Cisco cBR-8 CCAP Line Cards: Cisco cBR-8 Downstream PHY Modules: Cisco cBR-8 Upstream PHY Modules: |
How to Configure In-Service Software Upgrade
This section describes the configuration of the ISSU feature:
- Using In-Service Software Upgrade to Perform Consolidated Package Upgrade
- Using In-Service Software Upgrade to Perform Subpackages Upgrade
- Linecard Only In-Service Software Upgrade
- In-Service Software Upgrade Abort
- In-Service Software Upgrade Rollback
Using In-Service Software Upgrade to Perform Consolidated Package Upgrade
Consolidated packages can only be upgraded using ISSU in dual SUP configurations. ISSU is not supported for consolidated package upgrades in single SUP configurations.
In service one-shot software upgrade procedure enables you to upgrade or downgrade software using a single command. One-shot ISSU needs minimal user intervention or monitoring. Once the upgrade is initiated, the upgrade process cannot be cancelled.
The one-shot upgrade procedure is divided into stages. When a failure occurs, the command execution is stalled and users have to perform the rollback tasks manually. Necessary switchovers are automatically taken care of in one of the upgrade stages. During a switchover, the console and its output are lost. Additional commands are used to connect back to the console.
Note | One-shot upgrade does not support multiple upgrades at the same time. |
Be sure to complete the following prerequisites before running the ISSU process:
Using In-Service Software Upgrade to Perform Subpackages Upgrade
Subpackage upgrade allows a subset of the running software to be upgraded. It is intended for patching small and targeted fix instead of full image upgrade. Subpackage upgrade supports both single and dual SUP setup.
Single SUP Subpackages Upgrade
Be sure to complete the following prerequisites before running the ISSU process:
Dual SUPs Subpackages Upgrade
Be sure to complete the following prerequisites before running the ISSU process:
- Standby SUP must be in hot standby.
- Config register autoboot enabled.
- Both SUP in sub-package mode, running same base image and patches from same path.
- Target patch copied to active SUP in the same directory of the packages.conf file system is booted up with.
- If needed copy patch info file to both SUPs.
- Enough bootflash disk space on both SUPs.
Linecard Only In-Service Software Upgrade
Use request platform software package install node linecard-only command to upgrade only the linecard to the same version as the one in the current active SUP, the customer can choose to upgrade one linecard or all the linecards in the chassis.
This command can be used together with request platform software package install node file file-path noreload linecard command to upgrade SUP first, and then upgrade linecard.
Command or Action | Purpose |
---|
In-Service Software Upgrade Abort
Use request platform software package install node abort command to abort the ISSU procedure.
When user abort the ISSU, the linecards will be in the different version with the SUP.
If the customer believes the new version is not stable, and wants to stop the upgrade, he can use this command to abort the current upgrade process. After this command is entered, the customer needs to check both SUP and LC's states to decide what to do in the next step, eg: rollback.
Command or Action | Purpose |
---|
In-Service Software Upgrade Rollback
If the customer is not satisfied with the new package after the upgrade, the system can go back to previous working state using rollback operation. The linecards that do not in the redundancy group will be reloaded.
Note | Rollback operation can only go back one step in the history. If the customer wants to go back to an earlier image, downgrade operation should be used. |
Cisco IOS-XE Release 3.16.0S
In Cisco IOS-XE Release 3.16.0S, the following steps can be used to perform the rollback.
Command or Action | Purpose |
---|
Cisco IOS-XE Release 3.17.0S and later version
Starting from Cisco IOS-XE Release 3.17.0S, the following steps can also be used to perform the rollback.
Command or Action | Purpose |
---|
Additional References
The following sections provide references related to the ISSU feature.
Technical Assistance
Description |
Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for In-Service Software Upgrade
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/. An account on http://www.cisco.com/ is not required.
Note | The below table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. |
Feature Name |
Releases |
Feature Information |
---|---|---|
ISSU |
Cisco IOS-XE Release 3.16.0S |
This feature was introduced on the Cisco cBR Series Converged Broadband Routers. |
ISSU with LCHA |
Cisco IOS-XE Release 3.17.0S |
This feature was introduced on the Cisco cBR Series Converged Broadband Routers. ISSU abort and linecard only ISSU were supported. |