Upgrading the Software
Use this procedure to upgrade the software on a BTI7800. Upgrading the software is not service affecting. This procedure covers upgrading the software on the CMMs and on all of the traffic modules, but does not cover upgrading the firmware. For upgrading the CMM firmware, see Upgrading the CMM Firmware.
The system automatically upgrades traffic module firmware when needed. You do not need to explicitly upgrade firmware on the traffic modules.
Service modules are automatically warm reloaded as part of this procedure. Software-based features on the service module (such as PM collection, APSD, APR, FPSD) are disabled while a service module warm reloads.
Prerequisites:
In releases lower than release 4.3, you must have superuser privileges to upgrade the software. In releases 4.3 and higher, you can upgrade the software with the provisioning privilege.
You have the IP address and login credentials of the (S)FTP server where the software package resides.
The (S)FTP server must be reachable from the network on which the shared management IP address resides.
- Log in to the CLI using the shared management IP address.
- Verify that there are no alarms raised against the CMMs.
Use the show alarms command to view alarms on the chassis.
Resolve all CMM alarms before proceeding. You do not have to resolve non-CMM equipment alarms.
Tip Use the show alarms command before and after the upgrade to determine if new alarms are raised from the upgrade.
- If you are running with two CMMs, verify that the CMMs
are synchronized.
The CMMs are synchronized when the HA Status is In Sync.
For example (only relevant output is shown):
bti7800# show systemActive Controller : cmm:1/A Backup Controller : cmm:1/B HA Status : In Sync
- Specify the IP address of the (S)FTP server, the login
credentials, and the file path for the software package. The software
is packaged as an RPM file.
For example:
bti7800# system upgrade remote-url ftp://user@172.25.5.100/sw/bti7800-sys-1.6.0-14211.x86_64.rpmValue for 'password' (<string>):
Enter the (S)FTP server password when prompted.
- Verify that the remote-url has been specified correctly.
For example (actual output might differ):
bti7800# show system upgradeCurrent Status : URL set Module URL Status URL -------- -------------- --- cmm:1/A URL set ftp://user@172.25.5.100/sw/bti7800-sys-1.6.0-14211.x86_64.rpm
- Start the download.
Use the system upgrade download command to start the download.
bti7800# system upgrade downloadbti7800#
- Check on the status of the download.
You can check on the status of the download by issuing the show system upgrade command periodically.
For example (partial output only, actual output might differ):
bti7800# show system upgradeCurrent Status : download-in-progress Module Download Status Start Time Notification Message -------- ----------------- -------------------------- -------------------- cmm:1/A download-in-progress 2015-01-20T19:48:30+00:00 Download in progress 100.0 MB Downloaded
bti7800# show system upgradeCurrent Status : download-in-progress Module Download Status Start Time Notification Message -------- ----------------- -------------------------- -------------------- cmm:1/A download-in-progress 2015-01-20T19:48:30+00:00 Download Finished Unroll Started
bti7800# show system upgradeCurrent Status : download-success Module Download Status Start Time Notification Message -------- ----------------- -------------------------- -------------------- cmm:1/A download-success 2015-01-20T19:48:30+00:00 Download & Unroll successful, Ready for Commit
The software package has been downloaded to local storage.
- Use the system upgrade commit command to load the software packages onto the respective modules
on the chassis.
For example:
bti7800# system upgrade commitCAUTION: Would you like to Proceed? [no,yes] yes
- Check on the status of the commit.
You can check on the status of the commit by issuing the show system upgrade command periodically.
For example (partial output only, actual output might differ):
bti7800# show system upgradeCurrent Status : commit-in-progress Module Commit Status Commit Start Time Notification Message -------- ------------------ -------------------------- --------------------- cmm:1/A commit-in-progress 2015-01-20T19:51:54+00:00 COMMIT IN PROGRESS cmm:1/B commit-in-progress 2015-01-20T19:51:54+00:00 COMMIT IN PROGRESS
Note The CMMs are upgraded first. When the CMMs are being upgraded, you will lose management connectivity. Wait several minutes before connecting to the shared management IP address again. Once you log back in, continue to check on the status of the commit.
bti7800# show system upgradeCurrent Status : commit-in-progress Module Commit Status Commit Start Time Notification Message -------- -------------- ------------------------- --------------------- cmm:1/A commit-success 2015-01-20T20:01:12+00:00 COMMIT SUCCESS cmm:1/B commit-success 2015-01-20T20:01:12+00:00 COMMIT SUCCESS ufm:1/1 commit-success 2015-01-20T20:03:31+00:00 COMMIT SUCCESS ufm:1/11 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS ufm:1/13 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS ufm:1/14 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS ufm:1/2 commit-success 2015-01-20T20:03:31+00:00 COMMIT SUCCESS ufm:1/3 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS ufm:1/4 commit-success 2015-01-20T20:03:31+00:00 COMMIT SUCCESS ufm:1/5 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS ufm:1/6 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS ufm:1/8 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS ufm:1/9 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS
The commit is finished when the Current Status shows commit-success.
For example:
bti7800# show system upgradeCurrent Status : commit-success Module Commit Status Commit Start Time Notification Message -------- -------------- ------------------------- --------------------- cmm:1/A commit-success 2015-01-20T20:01:12+00:00 COMMIT SUCCESS cmm:1/B commit-success 2015-01-20T20:01:12+00:00 COMMIT SUCCESS ufm:1/1 commit-success 2015-01-20T20:03:31+00:00 COMMIT SUCCESS ufm:1/11 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS ufm:1/13 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS ufm:1/14 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS ufm:1/2 commit-success 2015-01-20T20:03:31+00:00 COMMIT SUCCESS ufm:1/3 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS ufm:1/4 commit-success 2015-01-20T20:03:31+00:00 COMMIT SUCCESS ufm:1/5 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS ufm:1/6 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS ufm:1/8 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS ufm:1/9 commit-success 2015-01-20T20:03:32+00:00 COMMIT SUCCESS Module Download Status Download Start Time Notification Message -------- ----------------- -------------------------- -------------------- cmm:1/A download-success 2015-01-20T19:48:30+00:00 Download successful Module URL Status URL -------- ---------- ---------------------------------------------- cmm:1/A URL set ftp://user@172.25.5.100/sw/bti7800-sys-1.6.0-14211.x86_64.rpm Software Rollback : Rollback eligibility has not been evaluated
Note Starting with release 4.2, the system automatically retries the system upgrade commit command if the initial commit fails.
- Check over the system.
Use the show system version command to verify that all modules are running the new version of software.
Use the show equipment command to verify that all modules are up and running.
Use the show alarms command to verify that no unexpected alarms have been raised due to the upgrade.
Use the show system firmware command to see if the CMM firmware also needs to be upgraded.
If you see **FIRMWARE MISMATCH** in the CMM output, refer to Upgrading the CMM Firmware.
Note The firmware on traffic modules is automatically upgraded. When a traffic module comes up, a check is performed for a firmware mismatch. If a mismatch exists, the firmware on the traffic module is automatically upgraded.