Upgrading the Services Director

Upgrading the Services Director VA (v2.1 and Earlier)

The required procedure depends on whether your current database is internal or external, and whether you want to use High Availability at Services Director v2.3 (or later).

If you have an external database and want to use High Availability on your upgraded system, you must convert to using an internal database. High Availability is not supported for external databases. See Upgrading your Services Director VA (External DB and HA required)

If you have an external database but do not want to use High Availability, no special steps are required. See Upgrading your Services Director VA.

If you have an internal database, no special steps are required. See Upgrading your Services Director VA.

Upgrading your Services Director VA (External DB and HA required)

This procedure converts your external database to an internal database, and upgrades your Services Director VA. This enables you to use your existing Services Director VA in an HA pair.

Upgrade your Services Director VA (version 2.1 or earlier) to the Services Director VA v2.1r1 release. See Upgrading your Services Director VA.

Upgrade your Services Director VA v2.1r1 to the Services Director VA v2.4 release. To do this, repeat the procedure described in Upgrading your Services Director VA.

To support the encryption of stored passwords for Traffic Manager instances, Services Director will encrypt passwords during the upgrade of the Virtual Appliance. A default master password of master1M@ is used to do this. It is strongly recommended that you update the master password after an upgrade. For a Services Director VA installation, this process is performed from the System > Security page. See also Working with the Master Password.

Take a mysqldump of the external database (.sql extension).

Log into your upgraded Services Director VA and start the CLI:

login as: admin
Ivanti Services Director
Last login: Tue Apr 8 22:17:09 2014 from 10.32.26.136
amnesiac > enable
amnesiac # configure terminal
amnesiac (config) #

Reconfigure the VA to use an internal database, using the CLI command:

amnesiac (config) # ssc database use-local

Import the database dump file with the CLI command:

amnesiac (config) # ssc database local db-file import
scp://<user>:<password>@<host+path to file> force

Use the Create Primary command to upgrade your upgraded Services Director to a Primary Services Director node. This node is then ready for High Availability. For details, see Services Director Getting Started Guide.

Upgrading your Services Director VA

To upgrade a Services Director VA from 25.1.0.0 (or earlier):

Upgrading from 21.x releases to 25.1.0.0 is not supported.

Upgrading from 25.1.0.0 to 25.1.1.0 is supported.

To support the encryption of stored passwords for Traffic Manager instances, Services Director will encrypt passwords during the upgrade of the Virtual Appliance. A default master password of master1M@ is used to do this. It is strongly recommended that you update the master password after an upgrade. For a Services Director VA installation, this process is performed from the System > Security page. See also Working with the Master Password.

The procedure below can be used for both steps:

Download the required Services Director VA upgrade image from the Ivanti Support site.

Place the image file on a server that is accessible with HTTP, SCP, or FTP.

Connect to the Services Director VA using a terminal session and start enable mode :

login as: admin
Ivanti Services Director
Last login: Tue Apr 8 22:17:09 2014 from 10.32.26.136
amnesiac > enable
amnesiac #

Locate the upgrade image, and retrieve it:

amnesiac # image fetch http://<host-name>/<path>/<image.img> <local-name>

Ensure that the source image file is named image.img, as the image fetch command requires this filename to complete successfully. You can assign any preferred value as the local name, such as 25.1.1.0.img.

Where:

<image-name> is the name of the file you want to fetch.

<local-name> is an optional local name for the downloaded image file. This takes the form "<name>.img". For example, "ssc_23.img". If this is not specified, the downloaded image is renamed to "image.img" once it downloads.

Apply the upgrade, using the local name from step 4. For example, "image.img":

image upgrade image.img

The image upgrade may take a long time and the session will remain unresponsive during this step. However, the Services Director itself will remain operational for instance licensing, monitoring, and so on.

Once the process is complete, a message is displayed:

"Installed image 'image.img' on partition 2. The 'reload' command will load software version '<version details>'"

After the upgrade is installed, the Services Director VM automatically restarts to complete the upgrade process. No manual reload or reboot is required.

reload

Wait for the image to reload.

The Services Director VA will restart at this point. This may cause instances to briefly enter the licensing grace period (six weeks), but they will return to normal operation once the restart is completed.

Access the Services Director VA via Web UI or command line interface to check that the node is operational. The version on the title bar should indicate the new software version.

Upgrading an HA Pair of Services Director VAs (v2.2 or Later)

A High Availability pair of Services Director VAs must be upgraded using the procedure below.

The same general procedure can be used for a standalone Services Director VA.

Download the Services Director VA upgrade image from the Ivanti Support site.

Place the image file on a server that is accessible with HTTP, SCP, or FTP.

Connect to the Active node using a terminal session and start enable mode :

login as: admin
Ivanti Services Director
Last login: Tue Apr 8 22:17:09 2014 from 10.32.26.136
amnesiac > enable
amnesiac #

Locate the upgrade image, and retrieve it:

amnesiac # image fetch http://<host-name>/<path>/<image-name> <local-name>

Where:

<image-name> is the name of the file you want to fetch.

<local-name> is an optional local name for the downloaded image file. This takes the form "<name>.img". For example, "ssc_23.img". If this is not specified, the downloaded image is renamed to "image.img" once it downloads.

Apply the upgrade, using the local name from step 4. For example, "image.img":

image upgrade image.img

Once the process is complete, a message is displayed:

"Installed image 'image.img' on partition 2. The 'reload' command will load software version '<version details>'"

Restart the node:

reload

Wait for the Active node to reload the upgraded image.

The node will restart at this point. This may cause instances to briefly enter the licensing grace period (six weeks), but they will return to normal operation once the restart is completed.

During an upgrade, the cluster_type property is added to each existing Cluster resource and set to User Created.

To support the encryption of stored passwords for Traffic Manager instances, Services Director will encrypt passwords during the upgrade of the Virtual Appliance. A default master password of master1M@ is used to do this. It is strongly recommended that you update the master password after an upgrade. For a Services Director VA installation, this process is performed from the System > Security page. See also Working with the Master Password.

Access the Services Director VA (using its Service Endpoint Address) via Web UI or command line interface to check that the node is operational. The version on the title bar should indicate the new software version.

Repeat steps 3-7 on the Standby node. Do not repeat step 8.

Access the Services Director VA (using its IP Address) via Web UI or command line interface to check that the node is operational. The version on the title bar should indicate the new software version.

The upgrade of the HA pair is complete.