Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

How do I rollback SMS patches via the CLI?

    • Updated:
    • 15 Jan 2018
    • Product/Version:
    • TippingPoint SMS All
    • TippingPoint Virtual SMS
    • Platform:
Summary
The purpose of this article is to discuss the procedure required to roll back the SMS TOS via the Command Line Interface (CLI). The SMS maintains a history of the TOS versions installed on the device. As such it offers the capability to roll back to a previous version of the TOS software. It is recommended that if you are required to roll back the SMS, you do so from the GUI interface. However the rollback operations can also be performed via the CLI.

Note 1: Prior to rolling back to a software version, make sure to review the release notes for any specific notations and warnings regarding the functionality for that version.

Note 2: You can only rollback one SMS patch version at a time so when you rollback a patch, you roll back to the previously installed version.
Details
Public

The following table contains useful commands when performing CLI rollback operations.

SMS CLI Rollback Commands
CommandDescription
get ctl.patch-releasenotesDisplays the release notes for the currently installed Patch.
get ctl.patch-rollbackDisplays true if the currently installed Patch can be rolled back. Displays false if the currently installed Patch cannot be rolled back.
get ctl.previous-patch-versionDisplays the version of the Patch that you would roll back to if a rollback operation was performed. If no previous Patch was installed it would display None.
get sw.patch-versionDisplays the version number of the currently installed Patch, or displays None if no patch is installed.
get sw.versionDisplays the version number of the currently installed TOS software.
set ctl.patch-rollback=<current-patch version>If Set to the version of the currently installed Patch, it rolls it back, to either the previously installed Patch or no Patch if it was the first Patch installed. Example: set ctl.patch-rollback=3.2.0.8312.5
set ctl.upgrade-sourceSetting the ctl.upgrade-source attrib to a string representing a URL will cause the system to retrieve and apply the update package to the system. Normally, a reboot will be required for the update to become effective. The URL can reference the http, https or ftp protocols. Example: set ctl.upgrade-source=http://www.tippingpoint.com/sms-update-1.0.pkg

In order to roll back the SMS TOS via the CLI you can execute the following command;

set ctl.patch-rollback=<current patch version>

The following examples display the output for various commands;

What is the current TOS software version?
Command: get sw.version
Response: System version (sw.version) = 5.0.0.106258

What is the current TOS patch version?
Command: get sw.patch-version
Response: System patch level (sw.patch-version) = 5.0.0.106258.1

Can the SMS TOS be rolled back?
Command: get ctl.patch-rollback
Response: Source of SMS rollback patch (ctl.patch-rollback) = true

What TOS Patch version are we rolling back to?
Command: get ctl.previous-patch-version
Response: Previous SMS update patch (ctl.previous-patch-version) = None

Based on the information from the example above, executing the command set ctl.patch-rollback=5.0.0.106258.1, would roll back TOS 5.0.0.106258.1 from Patch 1 to an unpatched system (5.0.0.106258).

The following examples display the response from a system that has not been patched.
What is the current TOS software version?
Command: get sw.version
Response: System version (sw.version) = 5.0.0.106258

What is the current TOS patch version?
Command: get sw.patch-version
Response: System patch level (sw.patch-version) = None

Can the SMS TOS be rolled back?
Command: get ctl.patch-rollback
Response: Source of SMS rollback patch (ctl.patch-rollback) = false

What TOS Patch version are we rolling back to?
Command: get ctl.previous-patch-version
Response: Previous SMS update patch (ctl.previous-patch-version) = None
Premium
Internal
Rating:
Category:
Configure; Troubleshoot; Deploy
Solution Id:
TP000099904
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.