Before you download and install a new version of SMS software, make a note of the following:
- Installing a new SMS version 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 upgrading the SMS server, you cannot connect to the server through the SMS client until you have upgraded the client software. However, you can view the detailed upgrade status from the local VGA console.
- Before performing an SMS upgrade, you must disable the High Availability (HA) mode. To upgrade an HA cluster, you 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 | 10-15 minutes | Unavailable |
| 3 | Migrate data | Automatic | 30-90 Minutes2 | Unavailable |
| 1. Network speed and package size determine the time required to download the file. 2. It depends on the amount of data to migrate. The SMS automatically reboots after step 2 and is unavailable for logins until step 3 is completed. Do not reboot the SMS during this time. |
||||
|
SMS TOS Upgrade Path |
|||||||
| Device | Current TOS | Intermediate TOS | Final TOS | ||||
| SMS1, 2 vSMS3 |
4.3.0 | 4.4.0 | 5.0.1 | 5.3.0 | 5.4.1 | 6.2.0 | 6.4.0 |
| 4.4.0 | → | ||||||
| 4.5.0 | |||||||
| 4.6.0 | |||||||
| 5.0.0 | |||||||
| 5.0.1 | → | ||||||
| 5.1.0 | |||||||
| 5.1.1 | |||||||
| 5.2.0 | |||||||
| 5.3.0 | → | ||||||
| 5.4.0 | |||||||
| 5.4.1 | → | ||||||
| 5.5.0 | |||||||
| 5.5.2 | |||||||
| 5.5.3 | |||||||
| 5.5.4 | |||||||
| 6.0.0 | |||||||
| 6.1.0 | |||||||
| 6.2.0 | → | ||||||
| 6.3.0 | |||||||
| Note 1: SMS v6.4.0 upgrades are only supported from an SMS installed with SMS v6.2.0 or later. Attempts to upgrade from an older release will return an error. Note 2: SMS v6.2.0 upgrades are only supported from an SMS installed with SMS v5.4.1 or later. Attempts to upgrade from an older release will return an error. Note 3: The 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 v6.4.0 |
SMS v6.3.0 |
SMS v6.2.0 |
SMS v6.1.0 |
SMS v6.0.0 |
SMS v5.5.4.1 |
SMS v5.5.4 |
| Support Status | |||||||
| TPS TXE | v6.4.0 and earlier |
v6.3.0 and earlier |
v6.2.0 and earlier |
v6.1.0 and earlier |
v6.0.0 | N/A | |
| TPS TX | v6.4.0 and earlier |
v6.3.0 and earlier |
v6.2.0 and earlier |
v6.1.0 and earlier |
v5.5.5 and earlier |
v5.5.5 and earlier |
v5.5.4 and earlier |
| TPS T | v5.5.6 and earlier |
v5.5.6 and earlier |
v5.5.6 and earlier |
v5.5.6 and earlier |
v5.5.6 and earlier |
v5.5.6 and earlier |
v5.5.4 and earlier |
| vTPS | v6.4.0 and earlier |
v6.3.0 and earlier |
v6.2.0 and earlier |
v5.5.5 and earlier |
v5.5.5 and earlier |
v5.5.5 and earlier |
v5.5.4 and earlier |