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 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. IPS and other devices continue to operate as usual and without interruption.
- 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.
- SMS requires ports 9033 and 10042 to be opened for proper operation.
- Before performing an SMS upgrade, you must disable High Availability (HA). The process for upgrading an HA cluster is to break down the cluster, upgrade each SMS individually, and then re-establish the cluster.
|
Depending on your download speed, the update process takes approximately 90 minutes. The following table provides a summary of the process with estimated times | ||||
| Step | Task | Manual or Automatic | Estimated Time | Link Status |
| 1 | Download the package | Manual | Varies | Up |
| 2 | Install the package | Manual | 5-25 minutes | Up |
| 3 | Reboot. Update the system | Automatic | 15-25 minutes | Down |
| 4 | Reboot. Migrate database | Automatic | 10-30 minutes | Down |
| 5 | Migrate Event Data** | Automatic | Varies | Up |
|
SMS TOS Upgrade Path | |||
| Device | Current TOS | Intermediate TOS | Final TOS |
| SMS vSMS1 | 4.3.0 | 4.4.0 | SMS 5.1.0 |
| 4.4.0 | → | ||
| 4.5.0 | |||
| 4.6.0 | |||
| 5.0.0 | |||
| 5.0.1 | |||
| Note 1: You must deploy the vSMS Open Virtualization Format (OVF) file using VMware vCenter Server. Deploying the OVF file directly through ESX/ESXi utilities is not supported. | |||
| Product Version Compatibility | ||||||
| Product | SMS v5.1.0 | SMS v5.0.x | SMS v4.6 | SMS v4.5 | SMS v4.4 | SMS v4.3 |
| Support Status | Supported | Supported | Supported | Supported | EOS DEC/31/2018 | EOS JUN/30/2018 |
| Direct migration to SMS v5.0.1? | N/A | Supported | Supported | Supported | Supported | Not supported |
| vTPS | TOS v5.1.0 and earlier | TOS v5.0.0 and earlier | TOS v4.2.x and earlier | TOS v4.2.x and earlier | TOS v4.0.2 and earlier | Not supported |
| TPS | TOS v5.1.0 and earlier | TOS v5.0.0 and earlier | TOS v4.2.x and earlier | TOS v4.2.x and earlier | TOS v4.1.0 and earlier | TOS v4.0.0 |
| IPS | TOS v3.9.x and earlier | TOS v3.9.x and earlier | TOS v3.9.x and earlier | TOS v3.9.x and earlier | TOS v3.8.x and earlier | TOS v3.8.x and earlier |
| NGFW | Not supported | TOS v1.2.3 and earlier | TOS v1.2.3 and earlier | TOS v1.2.3 and earlier | TOS v1.2.3 and earlier | TOS v1.2.0 and earlier |
| Identity Agent | TOS v1.0.0 | TOS v1.0.0 | TOS v1.0.0 | TOS v1.0.0 | TOS v1.0.0 | TOS v1.0.0 |
| © Copyright 2018 Trend Micro Incorporated. All rights reserved. Trend Micro, the Trend Micro logo, TippingPoint, the TippingPoint logo, and Digital Vaccine are trademarks or registered trademarks of Trend Micro Incorporated. TippingPoint Reg. U.S. Pat. & Tm. Off. The information is provided "as is" without warranty of any kind and is subject to change without notice. The only warranties for Trend Micro products and services are set forth in the express warranty statements accompanying such products and services. nothing herein should be construed as constituting an additional warranty. Trend Micro shall not be liable for technical or editorial errors or omissions contained herein | ||||||
