Upgrading to Version 7.2.1

The upgrade script upgrades the appliance to version 7.2.1 from any of the following versions:

v7.1
v7.1.1
v7.1.5
v7.1.6
v7.1.7
v7.1.7.1
v7.2

Note
If you are upgrading from an earlier 7.X version you will first need to upgrade to one of the versions listed above.

It is a shell script that contains all of the required packages and binaries.

To run the upgrade you must be logged in as the root user with the root user environment.

Merge Discovery Commands before scanning.
This upgrade contains a fix which removes the hostid attribute from all Linux hosts. The Discovery commands have been updated so that a hostid is no longer set for Linux hosts. You must merge the Discovery commands before performing a scan otherwise the hostid attribute will be reset for each Linux host.

You will also need to supply the credentials of a Tideway Foundation user with sufficient permissions to re-import the taxonomy and compile patterns.
The script does the following:

Displays a message stating the prerequisites for the upgrade.
Extracts archived files.
Configures System for Upgrade.
Upgrades Operating System, Foundation, and dependencies.
- Performs a Database Snapshot - optional. Where a snapshot is created, it can only be restored to an appliance running the pre-upgrade version of Tideway Foundation.
- Upgrades Foundation and dependencies.
- Uploads, but does not activate, the latest Pattern Packages available at release.
- Performs Post Installation Configuration.

Upgrade Script Options

The upgrade script has the following options:

Option	Description
`--no-snapshot`	Do not create a database snapshot before upgrading the Tideway Foundation application. If created, a snapshot takes place after the operating system is upgraded, but before the Tideway Foundation application is upgraded.
`--extract`	Extract the files from the archive contained in the script. This does not perform the upgrade. A manual upgrade is not supported.
`--tmpdir dirname`	Specify a directory in which to store temporary files. The default is `/tmp/twf.upgrade` *Note:* This directory needs at least 942MB.
`--no-clean`	Do not delete the temporary files extracted from the archive after the upgrade has been performed. The temporary files will be owned by the root user.
`--auto`	Automatic mode. Selecting this option means that all questions are automatically answered. Please note that invalid credentials provided will mean that a manual taxonomy import and pattern recompile will be necessary. Details and more information available in the log file on completion.
`--username`	Foundation UI user. Only valid in automatic mode.
`--password`	Foundation UI user password. Only valid in automatic mode. *Note:* If your password contains any special characters be sure to enclose the entire password in single quotes!
`--verbose`	Provide comprehensive messaging. This information is also logged in the file `/usr/tideway/log/upgrade_Vn.log`. See Messages in the Upgrade Log for notes on messages that may be logged.
`--help`	Displays a help message on the usage and options. The script then exits.

If you do not want to use the upgrade script to upgrade your appliance you should contact Tideway Customer Support.

Operating System and Architecture

The script is operating system and architecture specific. Download the one appropriate to your operating system and architecture. This is one of:

tideway-Vn-nnnnn-upgrade.ga.rhel5.i386.sh.gz
tideway-Vn-nnnnn-upgrade.ga.rhel5.x86_64.sh.gz
In the following procedure, the filename is referred to as tideway-Vn-nnnnn-upgrade.ga.rhel5.<arch>.sh.gz. Replace <arch> with i386 or x86_64 in the commands as appropriate.

The Upgrade Procedure

Copy the tideway-Vn-nnnnn-upgrade.ga.rhel5.<arch>.sh.gz file to a temporary directory, such as /usr/tideway/tmp.

Unzip the archive file using the following command:

[root@localhost tmp]# gunzip -v tideway-Vn-nnnnn-upgrade.ga.rhel5.<arch>.sh.gz

As the root user, run the upgrade script. Enter:

[root@localhost tmp]# sh ./tideway-Vn-nnnnn-upgrade.ga.rhel5.<arch>.sh

The following message is displayed:

  Welcome to the Tideway Foundation Appliance 7.2.1 upgrade!
  
  The script will perform the following (unless selected otherwise, see --help):
    - perform upgrade requirement checks
    - extract the relevant files from the archive into the selected directory
    - perform a Foundation snapshot
    - upgrade the Operating System, Foundation and all dependencies
    - perform any post installation steps
  
  To complete the upgrade, the script requires the following to complete:
    - Foundation credentials (taxonomy import and pattern compiling)
          (you will be prompted for these during the Foundation upgrade.
  
  During the starting and stopping of httpd services you may see some
    output. This is expected and required to handle various
    Apache security configuration options.
  
  Any discovery command changes in the new version of Tideway Foundation will
    not be automatically applied. If you have made local modifications these
    will be preserved. You MUST manually merge updates to the scripts into your
    own modifications once upgrade is complete. This can be done in the
    Discovery > Platforms administration page, which indicates the commands that
    have been changed from their default.
  
  Please note that you need to be the root user for the upgrade!
  
  Do you have everything you need to complete the upgrade (yes/no)?

Enter yes if you have all that you need to perform the upgrade. Answering no aborts the installation.
The script checks that all system requirements are fulfilled.

Performing upgrade requirements checks ...
  Stopping services ...
Stopping httpd: [  OK  ]

  Services stop complete.
  Starting services ...
Starting httpd: [  OK  ]

  Services start complete.
  Checks complete.

Then the upgrade itself is commenced, beginning with extracting the files from the archive.

------------------------------------------------------
STAGE 1: Archive Extraction.
------------------------------------------------------

If the temporary directory does not exist you are asked whether it should be created. If it does exist you are asked whether you want to use it. Answering no aborts the installation.
```
Temporary directory /tmp/twf.upgrade does not exist, create it (yes/no)? yes
Starting extraction ...
Archive extracted.
Unpacking Archive ...
Archive unpacked.
Extraction complete.
```

The upgrade then tests that the RPM will install correctly against the current system.

------------------------------------------------------
STAGE 2: RPM Upgrade Tests.
------------------------------------------------------
Starting RPM upgrade test ... this may take a while, please be patient!
Tests complete.

The next part of the upgrade is configuring the system, for example applying patches.

---------------------------------------------------------------
STAGE 3: Configure System for Upgrade
---------------------------------------------------------------
  Starting configuration ...
  Stopping services ...
Stopping httpd: [  OK  ]

  Services stop complete.
  Applying Python ldap library dependency fix
  Configuration complete.

The upgrade script now upgrades the operating system, Tideway Foundation, and any dependencies.

---------------------------------------------------------------
STAGE 4: Upgrade Operating System, Foundation and dependencies
---------------------------------------------------------------

Upgrading the operating system and Tideway Foundation application may take a long time. If you are not running in verbose mode, you can monitor progress by checking the log file using the following command:

$ tail -f /usr/tideway/log/upgrade-Vn.log

During the operating system upgrade, some SELinux error messages are logged, these can be ignored. See Messages in the Upgrade Log for notes on messages that may be logged. Part of this stage is to create a snapshot unless you specified otherwise.

  Clearing persistence data.
  Starting services ...
Starting httpd: [  OK  ]

  Services start complete.
  Running snapshot ...
  Snapshot complete.
  Stopping services ...
Stopping httpd: [  OK  ]

  Services stop complete.
  Starting RPM Upgrade ... this may take a while, please be patient!
  Packages successfully upgraded.

The Tideway Foundation application has now been upgraded, but a number of configuration steps need to take place, for example re-importing the taxonomy and recompiling patterns.

---------------------------------------------------------------
STAGE 5: Post Installation Configuration.
---------------------------------------------------------------
  Starting services ...
  Services start complete.
  Foundation credentials are required for post installation.
  Please enter foundation user: system
  Please enter password for system: 
  Please re-enter password for system: 
      Credential test for user system successful.
  Importing the taxonomy ...
  Import taxonomy complete.
  Stopping services ...
  Services stop complete.
  Starting services ...
Starting httpd: [  OK  ]

  Services start complete.
  Recompiling patterns ...
  Recompile complete.
  Restarting the firewall to enable any changes.

The software upgrade process is now complete.

If any further steps are required, in this case rebooting the system after a kernel upgrade, you are informed now, before the script exits.

Kernel Upgrades
Upgrading to version 7.2 requires a kernel upgrade. If you upgrade to version 7.2.1 from a version before 7.2, the kernel is upgraded and you will need to reboot the appliance to complete the upgrade. The following message:
The Kernel has been upgraded. The system must be rebooted.

---------------------------------------------------------------
STAGE 6: Post Upgrade Task Summary
---------------------------------------------------------------
  
  Any discovery command changes in the new version of Tideway Foundation will
  not be automatically applied. If you have made local modifications these
  will be preserved. You MUST manually merge updates to the scripts into your
  own modifications BEFORE the next discovery. This can be done in the
  Discovery > Platforms administration page, which indicates the commands that
  have been changed from their default.
  
---------------------------------------------------------------
  Upgrade complete - Tue Jun  9 14:15:00 BST 2009!

Merge Discovery Commands before scanning.
This upgrade contains a fix which removes the hostid attribute from all Linux hosts. The Discovery commands have been updated so that a hostid is no longer set for Linux hosts. As the warning in the upgrade script says, you must merge the Discovery commands before performing a scan otherwise the hostid attribute will be reset for each Linux host.

The appliance is now running Tideway Foundation version 7.2.1.

Reboot the appliance. Enter the following command:
```
[root@localhost tmp]# reboot
```

VMware Tools not Installed

If you are upgrading a Virtual Appliance from Version 7.1 VMware tools is not installed. VMware tools is essential for the Virtual Appliance. You must install VMware tools after the upgrade. If you had previously installed VMware tools then you must upgrade to the latest version. See your VMware documentation for information on doing this.

Upgrading Discovery Commands

The upgrade to 7.2.1 does not modify any discovery commands. After the upgrade is complete, you should go to the Discovery Platforms page (Administration > Discovery > Platforms) and update the commands as appropriate.

Messages in the Upgrade Log

During the upgrade the firewall (iptables) is restarted. When a kernel upgrade is part of the upgrade, the firewall is unable to restart as there is a mismatch between the running kernel's version and the kernel on disk. The firewall logs a FATAL message, but as this is entirely expected, the upgrade script wraps it in an information message:
2009-02-01 10:17:14: INFO: FATAL: Could not load /lib/modules/2.6.18-53.1.14.el5 /modules.dep: No such file or directory
This is expected behavior and does not indicate a problem with the upgrade.

Deactivate Existing TKU

The upgrade installs a new TKU package (TKU-CORE-2009-02-1) but does not activate it. Any TKU Package that you have installed must be deactivated before activating the TKU-CORE-2009-02-1. Information on activating and deactivating TPL packages is available here.

Hardware Reference Data

The upgrade uploads the Hardware Reference Data (TKU-HRD-2009-02-1) to the appliance as a TPL package. If you have not used Hardware Reference Data, the new version is activated. If you have used Hardware Reference Data you must remove the previous version and activate the new one before starting discovery. Information on activating and deactivating TPL packages is available here.

Once the newly installed version has been activated, you must import the HRD .csv file in Overwrite mode to replace the existing HRD nodes. The data file is /usr/tideway/data/installed/tpl/TKU-HRD-2009-02-1.csv. Importing Hardware Reference Data is described here.

Clearing Browser Caches

After upgrading to Tideway Foundation version 7.2.1 you should clear the cache of any client browsers or force a refresh (CTRL+F5 in most browsers).

Baseline Changes

The baseline tool tracks changes to the system configuration from a known baseline. After an upgrade, the appliance configuration will have changed significantly. You should view the baseline page after an appliance upgrade and examine the changes made to the system. When you understand the changes that have been made, you can rebaseline the appliance so that the tool can check for changes from the configuration after upgrading to Tideway Foundation version 7.2.1.

BMC Software