X-Series In-Service Upgrade (ISU)
Article ID: 167808
Updated On:
Products
XOS
Issue/Introduction
There is an alternate method of upgrading XOS software while minimizing downtime.
Cause
There is an alternate method of upgrading XOS software while minimizing downtime. It is referred to as ISU, or In-Service Upgrade.
Resolution
XOS In-Service-Upgrade virtually splits the chassis hardware resources in half. One half of the chassis is responsible for forwarding the traffic, while the other half is upgraded.
There are two In-Service-Upgrade modes:
-Interactive (default mode) allows the user to control the timing of each step during upgrade.
-Non-Intreractive mode executes the upgrade with no user input.
There are two In-Service-Upgrade modes:
-Interactive (default mode) allows the user to control the timing of each step during upgrade.
-Non-Intreractive mode executes the upgrade with no user input.
During this process:
1. Upgrade the secondary CPM to the new version of XOS and rebooting into primary mode.2. Once the upgraded CPM has initialized as a primary CPM, APMs, and NPMs will be moved in "batches" to the half of the chassis controlled by the upgraded CPM.
There are two methods for batch creation:
a) Configuration Analyzer. (The batches are automatically created.)
b) Custom Batch list
To view the default batch list:
CBS# upgrade in-service
CBS(in-service-upgrade)# show default-batches
a) Configuration Analyzer
The Configuration Analyzer creates a default batch list using a predefined logic.
To use the default batch list:
CBS# upgrade in-service
CBS(in-service-upgrade)# batch-default
Standby and down modules are the first to be moved since these modules are not passing traffic. These
modules are placed in the first batch, which cannot be modified.
To view the modules in this batch:
To view the modules in this batch:
CBS# upgrade in-service
CBS(in-service-upgrade)# show standby-modules
b) Custom Batch List
It is important to know the impact that specific APMs and NPMs have on the traffic before assigning a slot to a batch.
First, clear the current batch list:
Batch1: FW_1(3)
Batch2: np2(2)
Batch3: np1(1)
Batch4: FW_2(4)
Proceed with the installation
Proceed with the installation
CBS(in-service upgrade)# install <XOS version>
Follow the interview process
Follow the interview process
b) Custom Batch List
It is important to know the impact that specific APMs and NPMs have on the traffic before assigning a slot to a batch.
First, clear the current batch list:
CBS# upgrade in-service
CBS(in-service-upgrade)# clear-batches
Assign slots to a batches:
CBS(in-service-upgrade)# batch-2 np2
CBS(in-service-upgrade)# batch-2 np2
Batch2: np2(2)
CBS(in-service-upgrade)# batch-1 fw_1 fw_2
Batch1: fw_1 fw_2
Batch2: np2(2)
Any NPMs and APMs that are not assigned to a specific batch will be placed in a default batch and moved after the last defined batch has been moved.
Proceed with the installation
CBS(in-service upgrade)# install <XOS version>
Follow the interview process
Follow the interview process
A slot can only be assigned to one batch. If moving a slot that is already defined in another batch, remove the slot from the previous batch before assigning it to the new batch.
3. Upgrade the old primary CPM and reloading into secondary mode.
During the upgrade, the NPMs and APMs are rebooted by the system.
It is very important to understand and check the latest XOS release notes for any updates related to the ISU feature before proceeding. Contact Technical Support if there are any questions.
Review the XOS configuration guide for further information.
Workaround
n/aFeedback
Powered by
