2.2 Alternate Methods for Upgrading Older Agents and Clients

It is likely that you have installed 3.1.4 Agents and Clients on machines other than where the Cloud Manager Orchestration 3.1.5 components were installed. This section includes information that helps you to walk through the upgrade of those agents and clients.

NOTE:To perform a mass upgrade of Cloud Manager Orchestration 3.1.4 Agents, we recommend that you use a reputable application software distribution method to upgrade to the newer versions that ship with Cloud Manager 2.1.5. For example, you can use ZENworks Linux Management to distribute new agents and clients to Linux servers.

For more information, see Section 2.3, Running the Upgrade Configuration on an Enterprise Scale.

2.2.1 Automatically Upgrading the Orchestration Agent from the Cloud Manager Orchestration Console

The Cloud Manager Orchestration Console includes a feature that lets you automatically upgrade older Orchestration Agents on resources (virtual or physical) that connect to the Orchestration Server.

If your grid includes older (that is, older than Cloud Manager version 2.1.5) Resource objects, their Orchestration Agents cannot connect to a recently upgraded Orchestration Server. This is shown when the Resource Registration icon in the Resource Monitor of the Orchestration Console displays a “flag up” status.

When you click the Resource Registration icon, the Resource Registration Monitor dialog box displays all of the older resource objects attempting to connect. The Upgrade option is also available in the dialog box. You can select this option, along with all of the older agents that you want to upgrade.

When you use this automatic upgrade method, only the agent rpm (that is, the zw_zos_agent pattern) is upgraded, but other Orchestration components that might be present on the resource machine are not upgraded. These include the following components (listed by pattern names):

  • zw_zos_clients

  • zw_mon_agent

  • zw_vm_builder

  • cabextract (on Xen hosts where you plan to use Windows sysprep)

To separately upgrade these components, you need to use the YaST upgrade from the product ISO (see Upgrading the Orchestration Packages) or the zypper upgrade method, which is executed from the bash prompt. For more information, see Upgrading Orchestration Packages Using the zypper Command (SLES 11x Machines Only).

2.2.2 Using the ISO to Upgrade the Orchestration Agent on Red Hat Enterprise Linux 5 Machines

Use the following procedure if you want to use the Add-on method to upgrade the Cloud Manager 3.1.4 Orchestration Console to a Cloud Manager 3.1.5 Orchestration Console running on a Red Hat Enterprise Linux (RHEL) 5 machine.

  1. Shut down the old Orchestration Console on the machine where you intend to install the new Cloud Manager 3.1.5 Orchestration Console.

  2. Download the appropriate Cloud Manager 2.1.5 ISO to an accessible network location.

  3. Mount the Cloud Manager ISO as a loopback device as in the following example:

    mount -o loop netIQ_Cloud_Manager-2.1.5-SLE11.x86_64.iso /mnt

    This mounts the ISO in the /mnt folder.

  4. Navigate to the directory path where the RHEL 5 packages reside. For example:

    cd /mnt/RHEL5

    There are four packages in the /RHEL5 directory:

    • netiq-ncm-orch-config-3.1.5-<build>.noarch.rpm
    • netiq-ncm-orch-config-gui-3.1.5-<build>.noarch.rpm
    • netiq-ncm-cmos-agent-3.1.5-<build>.x86_64.rpm
    • netiq-ncm-cmos-java-1.6.0_sun_update14-1.x86_64.rpm
  5. Use the rpm command to install the packages:

    rpm -Uvh *.rpm

    If you encounter an issue regarding missing dependencies, you can use the up2date command to download and install those. For example, if you were missing libcaplso or libcap.so.1, you would run the following:

    up2date --solvedeps=libcp.so,libcap.so.1

  6. (Optional) Increase the heap size that the JVM handles to enable the console to manage a large number of objects.

    1. Open the cmoc bash shell script at /opt/netiq/ncm/cmos/server/bin.

    2. Inside the script, find the following line where the JVM parameters are defined:

      JVMARGS="-Xmx256m -Xms256m -Xmn64m -XX:NewSize=64m -XX:MaxNewSize=64m"
      

      The -Xmx argument specifies the maximum heap size for the JVM. Increasing the heap size prevents a JVM out of memory condition.

    3. Change the value in the -Xmx argument from 256MB to 512MB.

    4. Save the script.

NOTE:Upgraded agent and client software does not require you to execute the configuration script on RHEL 5 machines.

2.2.3 Using the ISO to Upgrade the Old Orchestration Agent or the Orchestration Clients on Windows Machines

The Orchestration Agent and the Orchestration Console are supported on Windows XP, Windows Vista and Windows 7 desktops. To upgrade, install the new Cloud Manager 2.1.5 release of the Orchestration Agent or the Orchestration Console.

IMPORTANT:When upgrading the Cloud Manager Orchestration Console on a Windows machine, you must uninstall the prior version first, then install the new version of Cloud Manager Orchestration Console.

Use the following steps to download the Orchestration component you want to install:

  1. Download the appropriate Cloud Manager ISO to an accessible network location.

  2. Create a DVD from the ISO or use a tool that will mount the ISO.

  3. Navigate to the directory path where the Windows packages (Windows XP, Windows Vista, or Windows 7) reside.

  4. Double-click the appropriate file (.exe) to launch an installation and configuration wizard for the Orchestration Console.

2.2.4 Using the Administrator Information Page to Upgrade the Agents and Clients

The Administrator Information Page includes installers for the Cloud Manager Orchestration Agents and Clients for Windows and various Linux/UNIX machines (see Alternative Installation Methods for the Orchestration Agent in the NetIQ Cloud Manager 2.1.5 Orchestration Installation Guide). The page has no facility for upgrading an agent or client.

To upgrade, we recommend that you use the methods native to the OS to install the new Cloud Manager release of the Orchestration Agent or Orchestration Console.

IMPORTANT:When upgrading the Cloud Manager Orchestration Console on a Windows machine, you must uninstall the prior version first, then install the new version.