Upgrading to Sun xVM Ops Center 2.1 on Solaris Systems

If you are using Sun xVM Ops Center version 2.0, you can upgrade the Enterprise Controller and Proxy Controllers using an update bundle.

The update bundle stops the services on the Enterprise Controller or Proxy Controller, then backs up the current data. The 2.1 packages are installed, and the Enterprise Controller or Proxy Controller services are restored to their initial state.

If the upgrade fails, the installed 2.1 material will be removed, and the product will be reinstalled using the 2.0 installer. The Enterprise Controller or Proxy Controller will then be restored using the backup file.

Before You Begin

Acquire the Enterprise Controller and Proxy Controller update bundles and copy them to the appropriate systems. To get these bundles, contact Sun Support Services or download them using the BUI.

When upgrading your Sun xVM Ops Center environment, you should upgrade the Enterprise Controller first, followed by the Proxy Controllers. Agents can be upgraded through the BUI once the Proxy Controller that manages them has been upgraded.

To upgrade to Sun xVM Ops Center 2.1, the install directory that you used to install Sun xVM Ops Center 2.0 must be present. This directory is used to back out the upgrade changes if the upgrade fails. If you have removed this directory, it must be replaced. If the initial install media are no longer present, contact Sun Support Services to replace them.

Downloading Enterprise Controller and Proxy Controller Update Bundles

You can download the update bundles through the Browser User Interface (BUI).

1. Select Administration in the Navigation panel.
2. Click Sun xVM Ops Center Updates in the Actions panel.
   The Sun xVM Ops Center Updates wizard is displayed.
3. Select one or more updates from the list, then click Next.
   The View License page is displayed.
4. Accept the license and click Next.
   The Update Download page is displayed.
5. Confirm your selections and click Download.
   The Summary page is displayed.
6. Click Finish.
   The selected Update Bundles are downloaded.

Performing the Upgrade

When upgrading your Sun xVM Ops Center environment, you should upgrade the Enterprise Controller first, followed by the Proxy Controllers. Agents can be upgraded through the BUI or manually once the Proxy Controller that manages them has been upgraded.
Upgrade log files are stored in the /var/scn/update-saved-state directory on the Enterprise Controller.

Upgrading an Enterprise Controller

You can upgrade an Enterprise Controller to the 2.1 version of Sun xVM Ops Center. The co-located Proxy Controller will be upgraded as well.
This procedure requires root access.
If an error occurs during this process, the system will be restored to version 2.0.
Note – At the beginning of the upgrade process, the Enterprise Controller will be shut down. This might cause any jobs that are currently running on the Enterprise Controller to be canceled and marked as failed.

1. Create a temporary directory on your system, then copy or move the update bundle to the temporary directory that you created. The Enterprise Controller upgrade requires 5G of free space.

   # mkdir /var/tmp/xVM/update
   # cp enterprise-controller.SunOS.sparc.2.1.0.900.tar.gz /var/tmp/xVM/update
   

   If you downloaded the Enterprise Controller update through the BUI, the update will be found in the /var/opt/sun/xvm/images/productUpdate directory on the Enterprise Controller system.

2. Change to the directory containing the update bundle.

   # cd /var/tmp/xVM/update
   

3. Use the gzcat and tar commands to uncompress and un-tar the update bundle.

   # gzcat enterprise-controller.SunOS.sparc.2.1.0.900.tar.gz | tar xf -
   

4. Change to the xvmoc_full_bundle directory and run the install script.

   # cd xvmoc_full_bundle
   # ./install --install <location of Sun xVM Ops Center 2.0>
   

   The following options may be used with the install script:

   Option	Option (Shortened)	Result	Default Without Option
   --acceptedlicense	-a	Accepts the license terms and conditions.	Display terms and conditions, and prompt for acceptance
   --install <install bundle path>	-i <install bundle path>	(Required option) Use the Sun xVM Ops Center 2.0 data at <location of Sun xVM Ops Center 2.0>. This allows the system to be rolled back in case of error.	(No default)
   --verbose	-v	Increase verbosity of output from update program.	Non-verbose output

   You must accept the license terms and conditions to complete the upgrade.
   When the upgrade is complete, the install script indicates that all Sun xVM Ops Center components have been upgraded to version 2.1.

5. Restart or refresh your browser if it is running.
   Cached data from the earlier version can cause Sun xVM Ops Center to display incorrectly. Refreshing or logging out and logging in will not clear this data.

Upgrading a Proxy Controller

Once you have upgraded your Enterprise Controller, you can upgrade any Proxy Controllers. The co-located Proxy Controller, if enabled, is upgraded along with the Enterprise Controller, but separate Proxy Controllers must be upgraded separately.
This procedure requires root access.
If an error occurs during this process, the system will be restored to version 2.0.

1. Create a temporary directory on your system, then copy or move the update bundle to the temporary directory that you created. The Proxy Controller upgrade requires 2G of free space.

   # mkdir /var/tmp/xVM/update
   # cp proxy-controller.SunOS.sparc.2.1.0.900.tar.gz /var/tmp/xVM/update
   

   If you downloaded the Proxy Controller update through the BUI, the update will be found in the /var/opt/sun/xvm/images/productUpdate directory on the Enterprise Controller system. The Proxy Controller update must be copied to the remote Proxy Controller system.

2. Change to the directory containing the update bundle.

   # cd /var/tmp/xVM/update
   

3. Use the gzcat and tar commands to uncompress and un-tar the update bundle.

   # gzcat proxy-controller.SunOS.sparc.2.1.0.900.tar.gz | tar xf -
   

4. Change to the xvmoc_update_bundle directory and run the update.pl script.

   # cd xvmoc_update_bundle
   # ./update.pl --install <location of Sun xVM Ops Center 2.0>
   

   The following options may be used with the update.pl script:

   Option	Option (Shortened)	Result	Default Without Option
   --acceptedlicense	-a	Accepts the license terms and conditions.	Display terms and conditions and prompt for acceptance
   --install <install bundle path>	-i <install bundle path>	(Required option) Use the Sun xVM Ops Center 2.0 data at <location of Sun xVM Ops Center 2.0>. This allows the system to be rolled back in case of error.	(No default)
   --verbose	-v	Increase verbosity of output from update program.	Non-verbose output

   You must accept the license terms and conditions to complete the upgrade.
   When the upgrade is complete, the update.pl script indicates that all Sun xVM Ops Center components have been upgraded to version 2.1.

Upgrading Agents Using the User Interface

Agents can be upgraded using the BUI.
Before you upgrade an Agent, you must upgrade the Proxy Controller that manages it.

1. Log in to the BUI.
2. Select Administration in the Navigation panel.
3. Select Agent Controllers in the Center panel.
4. Select the Agents, then click the Upgrade to Latest Available Version icon.
   The Upgrade Agents window is displayed.
5. Select a method of providing credentials for the system or systems to be upgraded.
   • The Re-use SSH Credentials Used During Discovery for the Selected Hosts option uses the same credentials used to discover the systems.
     Note – If you did not save the discovery credentials for a system, or if you manually installed an Agent on a system, it will not have stored criteria.
   • The Apply the Same SSH Credentials to All option prompts you for a single set of SSH credentials for all systems to be upgraded.
   • The Enter SSH credentials For Each of the Selected Hosts prompts you for a separate set of credentials for each system to be upgraded.
6. Click Submit.
   A popup appears confirming that the job has been launched.
7. Click Ok.
   The Agent or Agents are upgraded.

Upgrading Agents Manually

Agents can be upgraded manually or through the BUI.
For an Agent to be upgraded, its Proxy Controller must be upgraded first.
This procedure requires root access.

1. Stop the 2.0 agent.
   For example, on Solaris 8 or Solaris 9 Agents:

   # sh /etc/init.d/SUNWscn_update_agent stop
   # /usr/sbin/cacaoadm -i scn-agent stop
   

   On Solaris 10 Agents:

   # svcadm disable svc:/application/scn/update-agent:default
   # svcadm disable svc:/application/management/common-agent-container-1:scn-agent
   

   On Linux Agents:

   # /etc/init.d/sun_scn_update_agent stop
   # /etc/init.d/common-agent-container-1 stop
   

2. Copy the new agent bundle from the Enterprise Controller to the client and extract it.
   For example, on Solaris Agents:

   # scp -p <IP of Enterprise Controller>:/var/opt/sun/xvm/images/agent/SunConnectionAgent.`uname -s`.`uname -p`.2.1.0.908.zip /var/tmp
   # cd /var/tmp
   # unzip SunConnectionAgent.`uname -s`.`uname -p`.2.1.0.908.zip
   

   On Linux Agents:

   # scp -p <IP of Enterprise Controller>:/var/opt/sun/xvm/images/agent/SunConnectionAgent.`uname -s`.i686.2.1.0.908.zip /var/tmp
   # cd /var/tmp
   # unzip SunConnectionAgent.`uname -s`.i686.2.1.0.908.zip
   

3. Install the agent update.

   # cd /var/tmp/SunConnectionAgent
   # sh ./install
   

4. Copy the xVMOC Proxy Controller authentication token to the client:

   # ssh root@<IP of Proxy Controller> cat /var/opt/sun/xvm/persistence/scn-proxy/connection.properties | sed -n -e 's;\\;;g' -e 's/^auto-reg-token=\(.*\)/\1/p' > /var/tmp/proxy_token.txt
   

   Note – The sed grabs only the value of the auto-reg-token parameter, and strips out all \ (backslash) characters. If you prefer, you can do that by hand and copy the result to /var/tmp/proxy_token.txt.

5. Configure the new Sun xVM Ops Center agent.
   For example, on Solaris agents:

   # /opt/SUNWxvmoc/bin/agentadm configure -t /var/tmp/proxy_token.txt -x $<IP of Proxy Controller> -a $<IP of client primary hostname>
   

   On Linux agents:

   /opt/sun/xvmoc/bin/agentadm configure -t /var/tmp/proxy_token.txt -x $<IP of Proxy Controller> -a $<IP of client primary hostname>
   

   This step also starts the agent.
   Note – The following errors may safely be ignored. These refer to the addition of two sysidcfg scripts, which are already present from a prior agentadm configure step, such as from the original Sun xVM Ops Center 2.0 agent installation and configuration. The correct sysidcfg scripts will still be called properly by sysidcfg.

   Failed to add the zone configuration automation.
   Failed to add the service tags recreate script.
   

   Note – On systems with zones, you should complete this step on the global zones before completing it on the local zones.

6. Verify the connection.

   # sc-console list-connections
   scn-agent https://172.25.14.21:21165 urn:scn:clregid:1234567-aaaa-bbbb-cccc-123456789abc:YYYYMMDDHHMMSSss
   

Updating DHCP Settings

After a system is upgraded to 2.1, OS provisioning jobs will silently fail to update DHCP. The DHCP configuration for each Proxy must be reset.
Note – This procedure must be performed for each Proxy Controller.

1. Log in to the BUI.
2. Click Administration in the Navigation Panel.
3. Select a Proxy Controller.
4. Click DHCP Config.
   The DHCP Configuration window is displayed.
5. Click Save Config.
   OS Provisioning jobs can now be performed.

Known Issues

There are two known issues involving the update process on Solaris systems. The workaround procedures are described below.

Installing the SFWrpm Package

The SFWrpm package, which is required for uploading Linux RPMs, is not installed on the Enterprise Controller by the upgrade process. Use the following procedure to install this package.
This example uses a Sparc (R) system. For x86 systems, the initial directory and filenames will be different.

1. Change to the directory within the 2.0 installer that contains the package, and list the directory's contents.

   # cd <2.0-install-bundle>/SunOS_sparc/Product/components/osp
   # ls
   SUNWscn-osp-extdhcp-1.0-1.i386.pkg.Z scn-osp-extdhcp-1.0-1.i386.rpm
   SUNWscn-osp-extdhcp-1.0-1.sparc.pkg.Z scs-3.3.1-solaris_sparc.tgz
   

2. Use the gzcat and tar commands to uncompress and un-tar the bundle.

   # gzcat scs-3.3.1-solaris_sparc.tgz | tar xf -
   

3. Change to the directory containing the package.

   # cd scs-3.3/pkgs
   

4. Use the bunzip2 command to expand the SFWrpm package.

   # bunzip2 SFWrpm_sparc.pkg.bz2
   

5. Use the pkgadd command to add the package.

   # pkgadd -d SFWrpm_sparc.pkg SFWrpm
   
   Processing package instance <SFWrpm> from </var/tmp/xVM/SunOS_sparc/Product/components/osp/scs-3.3/pkgs/SFWrpm_sparc.pkg>
   
   rpm - Red Hat Package Manager(sparc) 4.1,REV=2005.01.05.17.49
   
   (Output omitted)
   
   Installation of <SFWrpm> was successful.
   

Upgrading Manually Installed Agents

There is a known issue that affects manually installed 2.0 Agents, preventing them from being automatically upgraded from the User Interface. If you manually installed Agents, then you will need to either manually upgrade the agents, or perform an SSH discovery of the operating system for each client so that the upgrade using the BUI will function properly.

To perform an operating system discovery, follow this procedure:

1. Select Gear in the Navigation panel.
2. Select Custom Discovery in the Actions panel.
3. Create new criteria that include the gear with manually installed agents by clicking the Add Criteria icon.
   1. Enter new criteria, including:

      

      • Criteria name
        If you check Save criteria for future use, the criteria will be saved under this name.
      • One or more IP addresses to scan
        These can be entered as a comma-separated list, an IP range specified by starting address-end address, or a subnet specified by network address/bit mask.
      • One or more Host names to scan
        All host names must be resolvable by the Enterprise Controller.
      • (Optional) A service tag passphrase
        Required if a service tag has been configured to be encrypted.
      • (Optional) A service tag port
        Required if a service tag has been configured to use a port other than the default of 6481.
      • (Optional) A service tag timeout
        The default value is 20 seconds.
      • The type of gear to target
        Specifying a type of gear will restrict the list of available discovery credential types.

        

        To view all discovery credentials or discover multiple types of gear, select All.

        

      • The discovery protocol or protocols to use and their credentials
        If you check Also Use Default Credentials, then Sun xVM Ops Center may use default credentials, including root credentials, in addition to those specified.
        If you select SSH, two sets of credentials can be entered. To use root credentials, enter the root credentials as the first set. To log in as a non-root user and then switch to root, enter the non-root credentials as the first set and the root credentials as the second set.
   2. (Optional) Check Save Criteria for Future Use to save the criteria for future use.
   3. (Optional) Check Save Password to save the passwords associated with discovery criteria.
   4. Click Save.
4. Select one or more discovery criteria.

   

5. Click Discover Gear and wait for the discovery job to complete before upgrading your instance of Sun xVM Ops Center.