Summary
This bulletin provides information on what is required to upgrade the TippingPoint Security Management System (SMS) device.
Important: Ensure that you read the release notes associated with the operating system software update package on the Threat Management Center (TMC) website. The release notes contain information that may make the difference between a successful software update and an unsuccessful software update.
Important: Ensure that you read the release notes associated with the operating system software update package on the Threat Management Center (TMC) website. The release notes contain information that may make the difference between a successful software update and an unsuccessful software update.
Details
Before you download and install a new version of SMS software, make a note of the following:
- Installing a new version of SMS causes the SMS server to reboot and close all client connections.
- When the SMS Server is unavailable during the reboot process, the availability and operations of TippingPoint devices managed by SMS are unaffected.
- When you upgrade the SMS server, you will be unable to connect to the server through the SMS client until you have upgraded the SMS client software. However, you can view detailed upgrade status from the local VGA console.
- Before performing an SMS upgrade, you must disable the High Availability (HA) mode. The process for upgrading an HA cluster is to break down the cluster, upgrade each SMS individually, and then re-establish the cluster.
|
The following table provides a summary of the process with estimated times | ||||
| Step | Task | Manual or Automatic | Estimated Time | SMS Status |
| 1 | Download software package | Manual | Varies1 | Available |
| 2 | Install upgrade package | Manual | 2-10 minutes | Unavailable |
| 3 | Migrate data | Automatic | Varies2 | Unavailable |
| 1. Network speed determines the time to download a 1.8 GB MB file 2. Depends on the amount of data to migrate. The SMS automatically reboots after step 2 and is not available for logins until step 3 has completed. Do not reboot the SMS during this time. | ||||
|
SMS TOS Upgrade Path | |||||
| Device | Current TOS | Intermediate TOS | Final TOS | ||
| SMS vSMS1, 2 | 4.3.01 | 4.4.01 | 5.0.11 | 5.3.0 | 5.4.1 |
| 4.4.01 | → | ||||
| 4.5.01 | |||||
| 4.6.01 | |||||
| 5.0.01 | |||||
| 5.0.11 | → | ||||
| 5.1.0 | |||||
| 5.1.1 | |||||
| 5.2.0 | |||||
| 5.3.0 | → | ||||
| 5.4.0 | |||||
| Note 1: If you are upgrading from a release earlier than v5.0.1 Patch 1 you must first upgrade to SMS 5.0.1 Patch 1, log in to the SMS, activate a Digital Vaccine, upgrade to v5.3, and then v5.4.1. Note 2: VMware vCenter server is not required to deploy the vSMS .ovf file. You can deploy the .ovf file directly through ESX/ESXi utilities. | |||||
| Product Version Compatibility | |||||||||||
| Product | SMS v5.4.1 | SMS v5.4.0 | SMS v5.3.0 | SMS v5.2.0 | SMS v5.1.1 | SMS v5.1.0 | SMS v5.0.1 P2 | SMS v5.0.1 P1 | SMS v5.0.0 | SMS v4.6.0 | SMS v4.5.0 |
| Support Status | EOS OCT/31/2021 | EOS MAY/31/2020 | EOS FEB/28/2019 | ||||||||
| TPS | TOS v5.4.1 and earlier | TOS v5.4.0 and earlier | TOS v5.3.x and earlier | TOS v5.2.x and earlier | TOS v5.1.1 and earlier | TOS v5.1.1 and earlier | TOS v5.0.3 and earlier | TOS v5.0.3 and earlier | TOS v5.0.3 and earlier | TOS v4.2.x and earlier | TOS v4.2.x and earlier |
| vTPS | TOS v5.4.1 and earlier | TOS v5.4.0 and earlier | TOS v5.3.x and earlier | TOS v5.2.x and earlier | TOS v5.1.1 and earlier | TOS v5.1.1 and earlier | TOS v5.0.2 and earlier | TOS v5.0.2 and earlier | TOS v5.0.2 and earlier | TOS v4.2.x and earlier | TOS v4.0.2.x and earlier |
| IPS | TOS v3.9.7 and earlier | TOS v3.9.7 and earlier | TOS v3.9.7 and earlier | TOS v3.9.7 and earlier | TOS v3.9.7 and earlier | TOS v3.9.7 and earlier | TOS v3.9.7 and earlier | TOS v3.9.4 and earlier | TOS v3.9.4 and earlier | TOS v3.9.3 and earlier | TOS v3.9.3 and earlier |
| Identity Agent | TOS v1.0.0 | ||||||||||
