Upgrading the System


Use the TAS Manager Console or the TAS Manager Web UI to install a new system release or to upgrade the TAS to a new TAS release. A system release is issued with a file that ends in .upg and can consist of any or all of the following components: new TAS software, new test server software, or a new test suite. A TAS release is issued with a .jar file and upgrades the TAS software only.

Refer to the Release Notes provided with the upgrade for the contents of the release and any special instructions regarding installation. 

The TAS Manager Console / Web UI will now check if the TAS Manager Console’s version matches the TAS’s current version and warn the user to reload if they are out of sync: "WARNING: TAS Manager Console does not match TAS Version! --Download updated TAS Manager Console --

Upgrading TAS with signed jars file is now fully enforced. The TAS will verify that the upgrade fie is signed before an upgrade begins. If the upgrade file is properly signed , you will see "File is signed by Spirent Communications (Landslide Team)". Possible errors if not using signed file : "ERROR: File is signed by unknown source, aborting upgrade", "ERROR: File is not signed, aborting upgrade", "ERROR: Unable to verify file is signed, aborting upgrade".

The upgrade order has changed on the TAS Manager Console, it will start with upload/selecting the upgrade file, then stop the TAS, backup, upgrade, relaunch, install license, and finally we will offer to REBOOT the Test Manager if we determine that a .upg was used. Since that is with .TSU which usually requires reboot. It will be similar to the Combo System reboot prompt. 

The TAS Manager upgrade process takes you through several steps:

To install an upgrade:

WARNING: Before you start the upgrade, check the System Status to see if there are tests running or other users logged into the system. If there are, use the System Shutdown option to stop the TAS prior to upgrading. In addition, check your HD space. It should be 2X the size of the UPG file, or 1X the UPG file on OS and TAS partitions. The TAS will prevent you from upgrading if there may not be enough space.

  1. Start the TAS Manager and login as cfguser.

  2. Select System > Upgrade from the menu, and the Upgrade Intro window opens.

  3. Read the steps listed in the upgrade window and click Yes to begin the upgrade or No to cancel. You will now first upload/select your TAS upgrade file before stopping the TAS. This should reduce the down time if the upload takes a very long time. 

    TIP: You can remove old upgrade files by right-clicking the file and selecting Delete.

  4. To upload a new upgrade file, click Browse to open the Load Local TAS Upgrade File window. Browse to the file's location, select the file, and click Load to begin the upload.

    By default, the browse window restricts the display to .upg files (system releases). Use the Files of Type drop-down list to select .jar files if you are installing a TAS release. The upload may take several minutes depending on your communication speed with the TAS.

  5. After the TAS has stopped, you can perform a backup. See Backing Up the System for instructions, or click Skip if you made a backup before starting the upgrade.

  6. When the backup is complete, or if it was skipped, the Upgrade TAS Files window opens and lists the upgrade files (.upg and .jar) available on the TAS.

  7. Select the upgrade file from the available files list, and click Upgrade. Progress messages are displayed in the console as the contents of the upgrade are installed.

  8. After the upgrade file has been installed, the TAS Manager Console is restarted in order that the remaining portion of the upgrade is executed with the latest software. All messages displayed in the console up to that point will be appended to the TAS Manager log, but you have an opportunity to review these messages and copy any important messages to the clipboard before the console is restarted. If the TAS recorded any errors during the upgrade, you are informed of them when you are prompted to review the log. Click Yes to open the log and copy messages by selecting the text and pressing Ctrl-c. Click OK to close the log and continue.

  9. When the new TAS Manager software is downloaded, the security warning may be displayed. Click Start to accept the new software. The new TAS Manager is installed and started, and you are automatically logged in.

TROUBLESHOOT: If the upgrade requires a new license, the TAS will not start and you will see "Failed to start TAS: Not licensed for TAS version <version> TAS startup failed" in the console.

  1. With a standard multi-server system, the process completes by starting the TAS. When you see "TAS is running at PID: xxxx - Fully Started," in the console, the upgrade is complete.

    IMPORTANT: When the TAS and test server share the same platform, the test server is automatically upgraded and the platform is rebooted to complete the upgrade. Allow 4-5 minutes before you attempt to login to the system.

    Otherwise, if the upgrade contains new test server software, use the Test Server Administration window to upgrade each of the test servers in your system after the TAS has started.

  1. Log out of and close the TAS Manager Console, and all browser windows. If the upgrade included a new TAS release, the new application will be downloaded to your machine when you start the Landslide Client. If the upgrade contains new test server software, use the Test Server Administration window to upgrade each of the test servers in your system after the TAS has started.

  2. If the upgrade file was a .upg you will be prompted to reboot the TAS after installing the license. "Reboot - Your last upgrade seems to be using .upg file, the Landslide Test Manager should be rebooted to complete the upgrade - Click cancel to skip reboot, only if you did not upgrade using a .upg" 


To Downgrade TAS:

 

To Downgrade TAS to an older version, follow the same Upgrade steps but using older (previous) load files.

    • If there was a Database change, TAS will not start (with database error). You must RESTORE to the Backup file from the older version and then restart the TAS.
    • If you have trouble starting the TAS after Restoring the Database, you may also need to Re-Install the old license or Install updated license.

 


 

Related Topics

  1. Managing Your Test Servers
  2. Starting the TAS Manager
  3. System Maintenance Tasks