5.8 Upgrading Oracle VM Agent for SPARC

Upgrade methods depend on the Oracle VM Agent for SPARC Release from which you are upgrading. For information about upgrade methods, see Section 5.1, “Upgrade Overview”.

Before you attempt to upgrade the Oracle VM Agent for SPARC, you must:

  • Update your system to Oracle Solaris 11.3 or Solaris 11.4.

    On Oracle VM Agent for SPARC Release 3.2.10, or later versions such as Release 3.2.11, you must manually upgrade to Oracle Solaris 11.3.

    As of Release 3.4.6, Oracle Solaris 11.4 is supported. If you are running Oracle VM Agent for SPARC Release 3.3.x, 3.4.1 or 3.4.2, and you plan to upgrade to Release 3.4.6, you must first upgrade to Release 3.4.5 on Oracle Solaris 11.3. From Release 3.4.5, after a reboot you can then upgrade to Release 3.4.6 with Oracle Solaris 11.4.

    Note

    If you are running an older version of Oracle VM Agent for SPARC, upgrading to Release 3.4.5 ensures that your system has the latest 11.3 SRU available (Oracle Solaris 11.3 SRU 23 or later), which is required before you upgrade to Release 3.4.6 with Oracle Solaris 11.4.

    On Oracle VM Agent for SPARC Release 3.3.x or Release 3.4.x, you set up an IPS repository to handle both the update to Oracle Solaris 11.3 and the upgrade of Oracle VM Agent for SPARC.

  • Review all minimum requirements to ensure a successful upgrade. See Table 2.2, “Required Software and System Firmware for SPARC Servers”.

Note

If you have a secondary service domain configured and you have successfully updated your system to Oracle Solaris 11.3 or Solaris 11.4 on the primary domain, the secondary service domain can also be upgraded using the same Oracle Solaris IPS repository as the primary domain. To upgrade the secondary service domain, you should upgrade from the Oracle Solaris command line using the following command:

# pkg update --accept

Reboot the system after the upgrade completes, as follows:

# init 6

For detailed install and upgrade instructions for Oracle Solaris 11.3, see http://docs.oracle.com/cd/E53394_01/.

For detailed instructions on updating to Oracle Solaris 11.4, see https://docs.oracle.com/cd/E37838_01/html/E60977/gmpdi.html

5.8.1 Installing the Distributed Lock Manager (DLM) Package

The distributed lock manager (DLM) package is required to support server pool clustering. The version of the DLM package must match the version of Oracle VM Agent for SPARC.

  • If the DLM package is already installed on your system, download the Release 3.4 version of the DLM package and add it to the IPS repository before you attempt to upgrade.

  • If the DLM package is not already installed, or you are upgrading from Oracle VM Agent for SPARC Release 3.2.10, you can install it before you upgrade Oracle VM Agent. Alternatively, you can install the DLM package after the upgrade is complete.

Download the DLM package, ovs-dlm-3.4.x-bxxx.p5p, from https://edelivery.oracle.com/oraclevm. For more information about downloading software, see Section 1.2, “Getting Installation ISOs and Packages”.

To add the DLM package to an IPS repository, see Section 5.8.3.1, “Setting Up IPS Repositories”.

To install the DLM package, do the following:

  1. Stop the ovs-config service:

    # svcadm disable -s ovs-config
  2. Install the DLM package:

    # pkg install -g ovs-dlm-3.4.x-bxxx.p5p dlm
  3. Restart the ovs-config service:

    # svcadm enable ovs-config

5.8.2 Upgrading from Oracle VM Agent for SPARC Release 3.2.10

Complete the tasks in this section to upgrade to Release 3.4 from Oracle VM Agent for SPARC Release 3.2.10 or a later version such as Release 3.2.11.

5.8.2.1 Placing Oracle VM Server for SPARC in Maintenance Mode

Before you begin any procedures to upgrade from Release 3.2.10, or a later version such as Release 3.2.11, you should ensure that no virtual machines are running on the server. For this reason you should place each Oracle VM Server for SPARC that you plan to upgrade in maintenance mode. After you place each Oracle VM Server for SPARC in maintenance mode, you should also check that no virtual machines are running on the servers you plan to upgrade. If any virtual machines are still running, you should stop them before attempting to upgrade Oracle VM Server for SPARC.

For instructions on editing a server and placing it in maintenance mode, see Edit Server in the Oracle VM Manager User's Guide.

5.8.2.2 Updating to Oracle Solaris 11.3 Manually

The first step to upgrade from Oracle VM Agent for SPARC Release 3.2.10, or a later version such as Release 3.2.11, is to manually update your system to Oracle Solaris 11.3 Support Repository Update (SRU) 19.

Note

  • Oracle VM Agent for SPARC Release 3.2.10 cannot run on Oracle Solaris 11.3. For this reason, you should disable Oracle VM Agent for SPARC before you update to Solaris 11.3.

    # svcadm disable ovs-agent
  • Oracle VM Agent for SPARC Release 3.2.x does not allow installations higher than Oracle Solaris 11.3 SRU 19. This is due to the removal of Python 2.6 in SRU 20. Once Oracle VM Agent for SPARC Release 3.4.3 or later is installed, the Oracle Solaris system can be upgraded to a more recent version.

  • This procedure should be used with Oracle VM Agent for SPARC Release 3.4.5 to update to the latest Oracle 11.3 SRU before rebooting the server and using the same procedure in Oracle VM Agent for SPARC Release 3.4.6 to updates the server from Oracle Solaris 11.3 to Solaris 11.4.

If you have already set up the Oracle Solaris repository, you can update the system packages with the following command:

# pkg update --accept

Reboot the system after the upgrade completes, as follows:

# init 6

For detailed instructions on updating to Oracle Solaris 11.3, see http://docs.oracle.com/cd/E53394_01/html/E54845/toc.html.

For detailed instructions on updating to Oracle Solaris 11.4, see https://docs.oracle.com/cd/E37838_01/html/E60977/gmpdi.html

5.8.2.3 Downloading and Extracting the Oracle VM Agent for SPARC Software

Before you you can upgrade Oracle VM Agent for SPARC to Release 3.4, you must download and extract the software.

  1. Download the Oracle VM Agent for SPARC software for Release 3.4 from https://edelivery.oracle.com/oraclevm.

    For more information about downloading software, see Section 1.2, “Getting Installation ISOs and Packages”.

  2. Extract the software, for example:

    # tar xzf ovs-ldoms-3.4.x-bxxx.tar.gz

5.8.2.4 Upgrading Oracle VM Agent for SPARC

To upgrade Oracle VM Agent for SPARC from Release 3.2.10, or a later version such as Release 3.2.11, do the following:

  1. Open a terminal connection to the system you plan to upgrade.

  2. Change to the directory where you extracted the software: ovs-ldoms-3.4.x-bxxx

  3. Run: ./update

  4. From Oracle VM Manager, rediscover the server and take it out of maintenance mode, if necessary.

  5. Complete the update by performing a server upgrade from within the Oracle VM Manager Web Interface as described in Update Server in the Oracle VM Manager User's Guide.

Example Output
# ./update 

Oracle VM Agent Release 3.4.1 Updater

- Stopping the Oracle VM Agent

- Updating Packages

Updating package cache                           1/1 
Caching catalogs ...


           Packages to install:         1
            Packages to update:         6
            Services to change:         1
     Estimated space available: 523.69 GB
Estimated space to be consumed: 748.24 MB
       Create boot environment:        No
Create backup boot environment:       Yes
          Rebuild boot archive:        No

Changed packages:
ovm
  ovm/storage-connect/plugins/oracle-zfs
    None -> 1.0.0,5.11-3.4.1.0.0.914:20150805T065013Z
  ovm/extra/urlgrabber
    3.9.1,5.11-3.2.10.0.0.759:20150924T063650Z -> 3.9.1,5.11-3.4.1.0.0.914:20150805T064943Z
  ovm/extra/vbox-img
    1.0.0,5.11-3.2.10.0.0.759:20150924T063654Z -> 1.0.0,5.11-3.4.1.0.0.1087:20151021T045254Z
  ovm/ovs-agent
    3.2.10,5.11-3.2.10.0.0.760:20150929T055226Z -> 3.4.1,5.11-3.4.1.0.0.1085:20151020T044541Z
  ovm/ovs-release
    3.2.10,5.11-3.2.10.0.0.760:20150929T055240Z -> 3.4.1,5.11-3.4.1.0.0.1087:20151021T045318Z
  ovm/storage-connect/plugin-manager
    1.2.8,5.11-3.2.10.0.0.759:20150924T063700Z -> 1.2.8,5.11-3.4.1.0.0.1033:20150928T170453Z
  ovm/storage-connect/plugins/oracle-generic
    1.1.0,5.11-3.2.10.0.0.760:20150929T055232Z -> 1.1.0,5.11-3.4.1.0.0.914:20150805T064958Z

Services:
  restart_fmri:
    svc:/system/manifest-import:default

DOWNLOAD                                PKGS         FILES    XFER (MB)   SPEED
Completed                                7/7       310/310      0.8/0.8  589k/s

PHASE                                          ITEMS
Removing old actions                             5/5
Installing new actions                       187/187
Updating modified actions                    209/209
Updating package state database                 Done 
Updating package cache                           6/6 
Updating image state                            Done 
Creating fast lookup database                   Done 
Updating package cache                           2/2 
Updating package cache                           1/1 

- Updating the OVS Agent Configuration

Network Configuration
Network Configuration OK
Storage Configuration
Storage Configuration OK
OVS Agent Configuration
OVS Agent Configuration OK
Cluster Configuration
Cluster Configuration OK
LDoms Manager Configuration
LDoms Manager Configuration OK
Virtual I/O Services Configuration
Virtual I/O Services Configuration OK
LDoms Configuration
LDoms Configuration OK
Enabling Oracle VM Agent Services

Update Completed.

5.8.3 Upgrading from Oracle VM Agent for SPARC Release 3.3.x or Between 3.4.x Errata Releases

Complete the tasks in this section to upgrade to Release 3.4 from Oracle VM Agent for SPARC Release 3.3.x or from one Release 3.4.x to another Release 3.4.y.

Important

As of Oracle VM Release 3.4.5, management of Oracle VM Server for x86 at 3.2.1x and Oracle VM Agent for SPARC at Release 3.3.1 is deprecated. If management of Oracle VM Servers at these release versions are still required, see Section 7.6, “Enabling the TLS Version 1 Protocol” in the Oracle VM 3.4 Installation and Upgrade guide.

As of Oracle VM Release 3.4.6, management of Oracle VM Server for x86 at 3.2.1x, and Oracle VM Agent for SPARC at Release 3.3.1 is removed. No error events are raised if Oracle VM Servers at these unsupported versions are discovered; however, the following message is displayed at the end of an upgrade, indicating that these versions are no longer supported: "3.2.10/3.2.11 Oracle VM x86 Servers and SPARC agent 3.3.1 managed Servers are no longer supported in Oracle VM Manager 3.4. Please upgrade your Server to a more current version for full support."

5.8.3.1 Setting Up IPS Repositories

Upgrades for Oracle VM Servers that are running on SPARC hardware can be handled by setting up two Oracle Solaris Image Package System (IPS) repositories. Your IPS repositories can be hosted on any system, either x86 or SPARC, as long as it is running Oracle Solaris 11 or later. The system where you configure these repositories must be accessible over the network by all of the SPARC based Oracle VM Servers that you wish to upgrade.

The first repository should be set up to handle Oracle Solaris updates and should have its publisher set to solaris. This repository can be used to keep the Oracle Solaris software in your control domains up to date. It is critical that this repository contains the packages for Oracle Solaris 11.3 or higher. This repository must be enabled if you intend to upgrade from a version equal to or prior to Oracle VM Server for SPARC release 3.3.x. The Oracle Solaris system repository can also be copied locally if you are updating a set of local Oracle VM Servers running on SPARC hardware. Instructions on setting up and copying IPS repositories can be found in the book titled Creating Package Repositories in Oracle Solaris 11.4 in the Oracle Solaris 11.4 Information Library at:

https://docs.oracle.com/cd/E37838_01/html/E60982/index.html

The second IPS repository should be set up to contain the Oracle VM Agent for SPARC and associated packages. This repository can be used to ensure that the latest version of Oracle VM Agent for SPARC is available to be installed on your Oracle VM Servers. You can also use this repository to store commonly required packages such as the distributed lock manager (DLM) package required for cluster support. This repository should have its publisher set to ovm. The instructions that follow explain how to set up and configure this IPS repository.

To set up an IPS repository for Oracle VM Agent for SPARC

  1. If you have not already created a package repository that is accessible over HTTP, you must create one by performing the following actions on the system where you intend to host your repositories:

    # pkgrepo create /path/to/my-repository
    # svccfg -s application/pkg/server setprop pkg/inst_root=/path/to/my-repository
    # svccfg -s application/pkg/server setprop pkg/port=8888
    # svcadm refresh application/pkg/server
    # svcadm enable application/pkg/server
  2. Check that the package repository server is online:

    # svcs pkg/server
    STATE          STIME    FMRI
    online         timestamp svc:/application/pkg/server:default
  3. Download the latest Oracle VM Agent for SPARC software from https://edelivery.oracle.com/oraclevm, as described in Section 1.2, “Getting Installation ISOs and Packages”.

  4. Extract the software, for example:

    # tar xzf ovs-ldoms-3.4.x-bxxx.tar.gz
  5. Copy the software to the package repository, for example:

    # pkgrecv -s ovs-ldoms-3.4.x-bxxx/ovs-ldoms.p5p -d /path/to/my-repository 'ovm/*'
    # pkgrecv -s ovs-dlm-3.4.x-bxxx.p5p -d /path/to/my-repository 'ovm/*'
  6. Restart the package repository server and ensure that it is online:

    # svcadm restart application/pkg/server
    # svcs pkg/server
  7. If the package repository server is in maintenance status, clear the service:

    # svcadm clear pkg/server
  8. Check that the contents of the repository are available, for example:

    # pkgrepo list -s /path/to/my-repository
    # pkgrepo list -s http://my-repo-server:8888/

5.8.3.2 Creating Server Update Repositories in Oracle VM Manager

The IPS repositories must be set up within the Oracle VM Manager Web Interface, so that the upgrade script can identify them accurately and use them to perform the upgrade on the specified Oracle VM Servers. The repositories are called server update repositories in the Oracle VM Manager Web Interface.

Use the Oracle VM Manager Web Interface to create two server update repositories, one for each repository. Make sure you create these server update repositories in the Sparc server update group. The following tables contain the information you need to create the server update repositories using the Create Server Update Repository dialog box.

Full instructions for creating a server update repository in the Oracle VM Manager Web Interface are provided in Create New Server Update Repository in the Oracle VM Manager User's Guide.

Table 5.5 Solaris Repository

Field

Value

Notes

Name

solaris

You may name this repository as you prefer within Oracle VM Manager, but choose a name that makes it easy for you to understand what the repository contains.

Repository Name

solaris

This should be set to the same name that you used for the IPS publisher.

URL

http://my-repo-server:8888/solaris

Substitute this URL with the URL to your Solaris IPS repository.

Enabled

Yes

You can enable or disable this repository to control whether only the Oracle VM Agent software is updated, or whether other Solaris packages are updated as well.

If the server is running a version of Solaris that is lower than 11.3, the repository must be enabled. Likewise the repository must contain the packages for Oracle Solaris 11.3 at a minimum.

Package Signature Type

None

No package signature type is required here.


Table 5.6 OVM Repository

Field

Value

Notes

Name

ovm-agent

You may name this repository as you prefer within Oracle VM Manager, but choose a name that makes it easy for you to understand what the repository contains.

Repository Nameovm

This should be set to the same name that you used for the IPS publisher.

URL

http://my-repo-server:8888/ovm

Substitute this URL with the URL to your Oracle VM Agent for SPARC IPS repository.

EnabledYes

You can enable or disable this repository to control whether the Oracle VM Agent software is updated, or whether only Solaris packages are updated. This repository must be enabled if you intend to upgrade the Oracle VM Agent.

Package Signature TypeNone

No package signature type is required here.


5.8.3.3 Upgrading Oracle VM Agent for SPARC

Note

Before you begin any procedures to upgrade from Release 3.2.10, or a later version such as Release 3.2.11, you should ensure that no virtual machines are running on the server. For this reason you should place each Oracle VM Server for SPARC that you plan to upgrade in maintenance mode. After you place each Oracle VM Server for SPARC in maintenance mode, you should also check that no virtual machines are running on the servers you plan to upgrade. If any virtual machines are still running, you should stop them before attempting to upgrade Oracle VM Server for SPARC.

For instructions on editing a server and placing it in maintenance mode, see Edit Server in the Oracle VM Manager User's Guide.

With your IPS repositories configured, you can perform server upgrades from within the Oracle VM Manager Web Interface as described in Update Server in the Oracle VM Manager User's Guide. If you have defined repositories for the Solaris operating system and for the Oracle VM Agent, then an update action is performed for both the Solaris operating system and the Oracle VM Agent. If you only want to update a particular component, either the Solaris operating system or the Oracle VM Agent, disable the repository with the component that you do not want to update within Oracle VM Manager.