3 Upgrading an HA Environment Using the Command Line

You can upgrade an environment with Enterprise Controller High Availability through the command line.

Upgrade your systems in the following order:

  1. Download the upgrade bundle for your environment.

  2. Upgrade the Enterprise Controllers. This also upgrades the co-located Proxy Controller.

  3. Upgrade the separate Proxy Controllers.

  4. Upgrade the Agent Controllers through the UI or manually.

Description of GUID-48CE84AD-9BC1-4603-AF46-631EE6A9B041-default.png follows
Description of the illustration GUID-48CE84AD-9BC1-4603-AF46-631EE6A9B041-default.png

Some of the procedures described in this guide use the ecadm, proxyadm, and agentadm commands.

  • On Oracle Solaris systems, these commands are in the /opt/SUNWxvmoc/bin/ directory.

  • On Linux systems, these commands are in the /opt/sun/xvmoc/bin/ directory.

Note:

The upgrade process creates a backup file for the Enterprise Controller. If the upgrade fails, the Enterprise Controller is uninstalled, the initial version of the Enterprise Controller is reinstalled, and the system is automatically restored from the backup file.

Once you have begun the upgrade, complete it as soon as possible. Do not allow the Enterprise Controller or Proxy Controllers to be restarted before all systems have been upgraded.

Downloading Upgrades

You can download the upgrade bundle for Oracle Enterprise Manager Ops Center. This includes upgrades for the Enterprise Controller, Proxy Controllers, and Agent Controllers. Downloading an upgrade does not install it on managed assets.

You can download the upgrade bundles through the user interface, from the Oracle Technology Network, or from the Oracle Software Delivery Cloud.

The following topics are covered:

Downloading Upgrades From the User Interface

You can download upgrades for Oracle Enterprise Manager Ops Center through the user interface.

Upgrades are downloaded to these directories:

  • Enterprise Controller upgrades: /var/opt/sun/xvm/images/productUpdate

  • Proxy Controller upgrades: /var/opt/sun/xvm/images/productUpdate

  • Agent Controller upgrades: /var/opt/sun/xvm/images/agent

Note:

The Enterprise Controller upgrade includes the Proxy Controller and Agent Controller upgrades, but the Proxy Controller and Agent Controller upgrades are not saved to these directories until the Enterprise Controller upgrade is applied.

  1. Expand the Administration section of the Navigation pane, then select Enterprise Controller.
  2. Click Ops Center Downloads.

    The Ops Center Downloads Wizard is displayed.

  3. (Optional) Hover over the details icon for a download to view more information about it.
  4. Select one or more downloads and click Next.

    The View License page is displayed.

  5. Read the license and click Accept.

    The Download Status page is displayed.

  6. Select I wish to download the remaining upgrades in the background, or wait for the downloads to complete.
  7. Click Next.

    The Summary page is displayed.

  8. Click Finish.

Downloading Upgrades From the Oracle Technology Network

You can download upgrade bundles for the Enterprise Controller and Proxy Controller from the Oracle Technology Network.

This procedure describes the steps to download upgrades from the Oracle Technology Network.

  1. Log in to the Oracle Technology Network Oracle Enterprise Manager Ops Center page. See Related Resources for HA Environment Upgrade Using the Command Line for the link to log in.
  2. Click Enterprise Manager Ops Center in the Enterprise Manager Downloads sidebar.
  3. Select Accept License Agreement.
  4. Click the Enterprise Controller bundle with the correct operating system and architecture to download the full bundle. This bundle contains the Enterprise Controller for the selected architecture, and Proxy Controller and Agent Controller files for every supported operating system and architecture.
  5. Copy the Enterprise Controller bundle to the /var/opt/sun/xvm/images/productUpdate/ directory on the Enterprise Controller system.

Downloading Upgrades From the Oracle Software Delivery Cloud

You can download upgrade bundles for the Enterprise Controller and Proxy Controller from the Oracle Software Delivery Cloud.

To download upgrades from the Oracle Software Delivery Cloud:

  1. Log in to the Oracle Software Delivery Cloud. See Related Resources for HA Environment Upgrade Using the Command Line for the link to log in.
  2. Read and accept the Software License Agreement and Export Restrictions, then click Continue.
  3. Select the Oracle Enterprise Manager product pack and the correct platform for your environment, then click Go.

    The list of download packs is displayed.

  4. Select the Media Pack for the target version and click Continue.

    The list of available bundles is displayed.

  5. Click download next to the Enterprise Controller bundle with the correct operating system and architecture to download the full bundle, then save the downloaded bundle locally. This bundle contains the Enterprise Controller files for the selected architecture and operating system, and Proxy Controller and Agent Controller files for every supported operating system and architecture.
  6. Copy the Enterprise Controller bundle to the /var/opt/sun/xvm/images/productUpdate/ directory on the Enterprise Controller system.

Upgrading the Enterprise Controllers in an HA Configuration

If you have multiple Enterprise Controllers in a high availability configuration, you can upgrade them.

Note:

The upgrade disables the Oracle Solaris 11 update manager service, svc:/application/pkg/update:default, if it is enabled.

Perform the following tasks before you upgrade the Enterprise Controller:

  • Download the Enterprise Controller upgrade.

  • Review pending and scheduled jobs before updating the Enterprise Controller. The upgrade shuts down the Enterprise Controller, which causes running jobs to fail.

  • Use the OCDoctor to verify that there are no outstanding issues on the Enterprise Controller systems. Log in to each Enterprise Controller system, then run the OCDoctor with the --update option, then run the OCDoctor script with the --troubleshoot option.

Follow this procedure to upgrade the Enterprise Controllers in an HA Configuration:

  1. Disable the Auto Service Request (ASR) feature if it is enabled.

    1. Expand the Administration section of the Navigation pane, then select Enterprise Controller.

    2. Click Disable ASR in the Actions pane.

  2. If one of the Enterprise Controller nodes has a co-located Proxy Controller, make it the primary node using the ecadm command with the ha-relocate subcommand.

  3. If multiple Enterprise Controller nodes have co-located Proxy Controllers, migrate all of the assets from these Proxy Controllers to a remote Proxy Controller or to the Proxy Controller of the primary node.

    1. Log in to the user interface.

    2. Select the source Proxy Controller in the Administration section of the Navigation pane.

    3. Click the Managed Assets tab.

    4. Select one or more assets to move, then click the Migrate Assets icon.

      If another Proxy Controller is available that can manage the assets, the Asset Migration Wizard is displayed.

      If no other Proxy Controller is available that can manage the assets, an error message is displayed.

    5. Select the destination Proxy Controller from the list of Proxy Controllers, or select Auto Balance across Proxy Controllers to automatically select a destination Proxy Controller.

    6. Click Migrate.

      A job is launched to migrate the selected assets to the destination Proxy Controller. The migration status is displayed in the job and in the Managed Assets tab. Wait for the job to complete before proceeding.

  4. On each standby node, use the ecadm command with the ha-unconfigure-standby subcommand to unconfigure the standby nodes from the HA configuration, then uninstall the Enterprise Controller software:

    1. Use the ecadm ha-unconfigure-standby command to remove the current node from the HA configuration.

    2. Use the /n1gc-setup/installer/install command with the -e option to uninstall the Enterprise Controller software components from your system.

      For example:

      # cd /n1gc-setup/installer/
# ./install -e
Invoking uninstall

      The install script displays a list of uninstallation tasks that automatically updates as the uninstallation proceeds. For example:

           Ops Center Enterprise Controller Uninstall
     (version 12.3.1.608 on SunOS)

 1. Restore file system configuration.                    [Not Uninstalled]
 2. Uninstall empty directories.                          [Not Uninstalled]
 3. Uninstall prerequisite configuration.                 [Not Uninstalled]
 4. Uninstall Agent components.                           [Not Uninstalled]
 5. Remove Deployable Proxy Bundles.                      [Not Uninstalled]
 6. Uninstall application packages.                       [Not Uninstalled]
 7. Run preremove tasks.                                  [Not Uninstalled]
 8. Uninstall Expect.                                     [Not Uninstalled]
 9. Uninstall IPMI tool.                                  [Not Uninstalled]
10. Remove database credentials.                          [Not Uninstalled]
11. Uninstall Oracle database.                            [Not Uninstalled]
12. Remove OC Database Schema                             [Not Uninstalled]
13. Uninstall Service container components.               [Not Uninstalled]
14. Uninstall Core Channel components.                    [Not Uninstalled]
15. Uninstall Proxy Core components.                      [Not Uninstalled]
16. Remove Proxy database credentials.                    [Not Uninstalled]
17. Uninstall Enterprise Controller components.           [Not Uninstalled]
18. Uninstall Update Connection - Enterprise.             [Not Uninstalled]
19. Uninstall Ops Center BUI components.                  [Not Uninstalled]
20. Uninstall OS provisioning components.                 [Not Uninstalled]
21. Stop and delete services.                             [Not Uninstalled]
Executing current step:  Stop and delete services...

      When complete, the install script indicates that the Enterprise Controller has been uninstalled.

    3. If your environment uses any IDRs, uninstall them. The uninstall procedures are included in the IDR readme files in the /usr/share/doc/release-notes/ directory.

    4. If the system is using Oracle Solaris 11, use the pkg publisher command to view the Oracle Solaris 11 publisher, then unset any publishers that are listed using the pkg unset-publisher command, and reset the Oracle Solaris 11 publisher using the pkg set-publisher command.

      If you are resetting the system to use the http://pkg.oracle.com/solaris/support repository, you must use the -k <key file> and -c <certificate file> options.

      For example:

      # pkg publisher
root@ocbrm-ipgs15:~# pkg publisher
PUBLISHER         TYPE     STATUS P LOCATION
cacao             origin   online F file:///var/opt/sun/xvm/images/IPS/oc-ips-repo/
mp-re             origin   online F file:///var/opt/sun/xvm/images/IPS/oc-ips-repo/
opscenter         origin   online F file:///var/opt/sun/xvm/images/IPS/oc-ips-repo/
# pkg unset-publisher cacao
# pkg unset-publisher opscenter
# pkg unset-publisher mp-re
# pkg set-publisher -G '*' -g http://pkg.oracle.com/solaris/release/ solaris

      When this procedure is complete, the pkg refresh --full command should be able to run successfully.

  5. On the primary node, use the ecadm command with the ha-unconfigure-primary subcommand to unconfigure the Enterprise Controller as part of a High Availability configuration.

    The primary Enterprise Controller node is removed from the HA configuration.

  6. On the remaining Enterprise Controller system, update the start/exec property in the svc:/application/scn/satellite-enable SMF service.

    1. Change the start/exec property for the svc:/application/scn/satellite-enable service to :true if it is not already set to :true. For example:

      # /usr/sbin/svccfg
svc:> select svc:/application/scn/satellite-enable
svc:/application/scn/satellite-enable> setprop start/exec = :true
svc:/application/scn/satellite-enable> end

    2. Refresh the svc:/application/scn/satellite-enable service. For example:

      # /usr/sbin/svcadm refresh svc:/application/scn/satellite-enable:default

    3. Confirm that the property is set to :true. For example:

      # svcprop -p start/exec svc:/application/scn/satellite-enable:default
:true

  7. Use the ecadm command with the status subcommand to verify that the Enterprise Controller is online. If it is offline, start it using the ecadm command with the start subcommand and the -w option.

  8. Create a temporary directory within the directory where you installed Oracle Enterprise Manager Ops Center, then copy or move the upgrade bundle to the new directory. For example:

    # mkdir -p /var/tmp/OC/update
# cp enterprise-controller.Solaris.sparc.12.3.1.608.tar.zip /var/tmp/OC/update

  9. Change to the directory containing the upgrade bundle.

    # cd /var/tmp/OC/update

  10. Unzip and un-tar the bundle.

    • If your upgrade bundle has the .tar.zip extension, use the unzip and tar commands to uncompress and un-tar the bundle, then list the contents of the temporary directory. The following command example retains the original compressed bundle file. For example:

      # unzip enterprise-controller.Solaris.i386.12.3.1.608.tar.zip | tar xf -
# ls
enterprise-controller.Solaris.i386.12.3.1.608.tar.zip
xvmoc_full_bundle
#

    • If your upgrade bundle has the .zip extension, use the unzip command to uncompress the bundle. For example:

      # unzip enterprise-controller.Solaris.i386.12.3.1.608.zip
# ls
enterprise-controller.Solaris.i386.12.3.1.608.zip
xvmoc_full_bundle
#

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

    For example:

    # cd xvmoc_full_bundle
# ./install

    When the upgrade is complete, the install script indicates that all Oracle Enterprise Manager Ops Center components have been upgraded to the latest version.

  12. (Optional) Once the upgrade has completed successfully, remove the version 12.2 installer to reclaim disk space.

    # rm -rf /var/opt/sun/xvm/EnterpriseController_installer_12.2.*

  13. Use the ecadm command with the ha-configure-primary subcommand to configure the system as the active Enterprise Controller.

    If the clusterware crsctl command is not in the /u01 directory, use the --crsctl_basepath <location> option to specify its location.

    For example:

    # ./ecadm ha-configure-primary
INFO: HAECClusterwareAdapter/doConfigurePrimary() Stopping Ops Center ...
INFO: HAECClusterwareAdapter/doConfigurePrimary() Ops Center stopped
INFO: HAECClusterwareAdapter/createActionScript() created Resource Action Script='/var/opt/sun/xvm/ha/EnterpriseController'
INFO: HAECClusterwareAdapter/doConfigurePrimary() created Clusterware Action Script='/var/opt/sun/xvm/ha/EnterpriseController'
INFO: HAECClusterwareAdapter/doConfigurePrimary() created Clusterware Resource='EnterpriseController'
INFO: HAECClusterwareAdapter/doHAStart() starting resource='EnterpriseController' on node='primary-system'
INFO: HAECClusterwareAdapter/doHAStart()statusSB='CRS-2672: Attempting to start 'EnterpriseController' on 'primary-system'
CRS-2676: Start of 'EnterpriseController' on 'primary-system' succeeded'
INFO: HAECClusterwareAdapter/doHAStart() started resource='EnterpriseController' on node='primary-system'
INFO: HAECClusterwareAdapter/doConfigurePrimary() Ops Center started on node='primary-system'
ecadm:    --- Enterprise Controller successfully configured HA primary node
#

  14. Install the new version of the Enterprise Controller on the standby nodes.

    1. If you are installing on Oracle Solaris 11, and if the system requires an HTTP proxy to reach the Internet, set the http_proxy and https_proxy environment variables. These values are only used during the installation. Use the following format:

      http_proxy=http://<proxy IP address>:<port number> or http://<username:password>@<proxy IP address>:<port number> - This variable specifies the proxy server to use for HTTP.

      https_proxy=https://<proxy IP address>:<port number> or https://<username:password>@<proxy IP address>:<port number> - This variable specifies the proxy server to use for HTTPS.

      For example:

      export http_proxy=http://10.79.204.11:8080
export https_proxy=https://10.79.204.12:8080

    2. Create a temporary directory on your system, then copy or move the upgrade and installation bundle to the temporary directory that you created. For example:

      # mkdir /var/tmp/OC
# cp enterprise-controller.Solaris.i386.12.3.1.608.tar.gz /var/tmp/OC

      The installation bundle consumes about 3.5 GBytes of disk space.

    3. Change to the directory where the installation bundle is located on your system.

      # cd /var/tmp/OC
#

    4. Expand the installation bundle, then list the contents of the expanded directory.

      If your installation bundle has the .zip extension, use the unzip command to uncompress the bundle. For example:

      # unzip enterprise-controller.Solaris.i386.12.3.1.608.zip
# ls
enterprise-controller.Solaris.i386.12.3.1.608.zip
xvmoc_full_bundle
#

      If your installation bundle has the .tar.zip extension, use the unzip and tar commands to uncompress and un-tar the bundle, then list the contents of the temporary directory. The following command example retains the original compressed bundle file. The data extracted from the bundle consumes about 1 GB of additional space. For example:

      # unzip enterprise-controller.Solaris.i386.12.3.1.608.tar.zip | tar xf -
# ls
enterprise-controller.Solaris.i386.12.3.1.608.tar.zip
xvmoc_full_bundle
#

    5. Create a database properties file on the Enterprise Controller system. The database properties file must contain the location of the customer-managed database and a user name and password that can access the database.

      For example:

      # vi /var/tmp/RemoteDBProps.txt
mgmtdb.appuser=user
mgmtdb.password=userpass
mgmtdb.roappuser=user
mgmtdb.ropassword=userpass
mgmtdb.dburl=jdbc:oracle:thin:@<database host name>:<port>/<database service name>

    6. Change directory to xvmoc_full_bundle, and run the install script with the --remoteDBprops <path to database properties file> and --standbyEC options. For example:

      # cd xvmoc_full_bundle
# ./install --remoteDBprops=/var/tmp/remoteDBProps.txt --standbyEC

    7. The Oracle Configuration Manager installation text is displayed. Enter the My Oracle Support user name or email address that you want to associate with Oracle Enterprise Manager Ops Center.

      Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name:

    8. If you want security updates to appear on your My Oracle Support page, enter your My Oracle Support password.

      Provide your My Oracle Support password to receive security updates via your My Oracle Support account.
Password (optional):

      The screen clears, then the install script displays a list of installation tasks that automatically updates as the installation proceeds. For example:

      Ops Center Enterprise Controller Installer
(version 12.3.1.608 on SunOS)
 
1. Check for installation prerequisites.                    [Not Completed]
2. Configure file systems.                                  [Not Completed]
3. Install prerequisite packages.                           [Not Completed]
4. Install Agent components.                                [Not Completed]
5. Create Deployable Proxy Bundles.                         [Not Completed]
6. Install application packages.                            [Not Completed]
7. Run postinstall tasks.                                   [Not Completed]
8. Install Expect.                                          [Not Completed]
9. Install IPMI tool.                                       [Not Completed]
10. Set database credentials.                               [Not Completed]
11. Install and Configure Oracle Database.                  [Not Completed]
12. Seed Ops Center Database Schema                         [Not Completed]
13. Install Service container components.                   [Not Completed]
14. Install Core Channel components.                        [Not Completed]
15. Install Proxy Core components.                          [Not Completed]
16. Set Proxy database credentials.                         [Not Completed]
17. Install Enterprise Controller components.               [Not Completed]
18. Install Update Connection - Enterprise.                 [Not Completed]
19. Install Ops Center BUI components.                      [Not Completed]
20. Install OS provisioning components.                     [Not Completed]
21. Initialize and start services.                          [Not Completed]
Executing current step:  Check for installation prerequisites...

    9. Review and correct any problems when the install script checks for installation prerequisites that are not met. For example, this install script detected insufficient disk space:

      Warning for Step: Check for installation prerequisites.
The following is a portion of the installer
log which may indicate the cause of the warning.
If this does not indicate the cause of the
warning, you will need to view the full log
file. More information on how to do that is
available below.
You may choose to ignore this warning by selecting to continue.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Ignoring job: 01checkRPMs.pl
Ignoring job: 03removeEmptyDirs.pl


Executing job: jobs/00checkPrereqs.pl --install

WARNING: Installation prerequisites not met:
Disk: / 72G needed, 24G available.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Please fix the problem and then try this step again.
For a full log of the failed install see the file: /var/tmp/installer.log.9361.

t. Try this step again (correct the failure before proceeding)
c. Continue (ignore the warning)
x. Exit
Enter selection: (t/c/x)

      Enter t to try again, c to continue and ignore the warning, or x to exit the install script. You should exit the install script, correct the problem, and then run the install script again, which resumes from where it stopped. Choose to continue and ignore the warning only if you accept the impact of the error condition on your installation. Entering t typically produces the same error, unless you are able to correct the problem before trying the step again. If the install script finds that all prerequisites have been satisfied, or if you choose to continue despite the warning, the install script continues and installs all Enterprise Controller and Proxy Controller components.

      When complete, the install script displays a confirmation that all components have been installed. The /var/tmp/installer.log.latest file contains the installation log.

    10. Create a password file containing the root user name and password for the primary Enterprise Controller. For example:

      # touch /tmp/creds.props
# chmod 400 /tmp/creds.props
# vi /tmp/creds.props
# cat /tmp/creds.props
username:root
password:XXXXX

    11. Use the ecadm command with the ha-configure-standby and -p <password file> subcommands to configure the node as a standby node.

      If the clusterware crsctl command is not in the /u01 directory, use the --crsctl_basepath <location> option to specify its location.

      For example:

      # ecadm ha-configure-standby -p /tmp/creds.props
INFO: HAECClusterwareAdapter/doConfigureStandby() Stopping Ops Center ...
INFO: HAECClusterwareAdapter/doConfigureStandby() Ops Center stopped
INFO: remoteFileCopy() copied '/etc/passwd' from remoteHostname='primary-system' to local file='/tmp/activeNodepw'
<output omitted>
ecadm:    --- Enterprise Controller successfully configured HA standby node

    12. Use the ecadm command with the ha-status -d option to check the status of the standby Enterprise Controller.

      For example:

      # ecadm ha-status -d
INFO: HAECClusterwareAdapter/doHAStatus() Status:
# HAEC Cluster Info: Thu Sep 29 15:49:09 MDT 2011
haec.cluster.active.node=primary
haec.cluster.nodes=standby, primary
haec.ec.public.nics=nge1
haec.ec.status=ONLINE
<output omitted>
haec.cluster.script=/var/opt/sun/xvm/ha/EnterpriseController
haec.cluster.crsctl=/u01/app/11.2.0/grid/bin/crsctl
# End of Cluster Info
ecadm:    --- Enterprise Controller ha-status command succeeded
Status stored in file: /var/opt/sun/xvm/ha/HAECStatus
#

  15. Clear your browser cache and refresh your browser before you log in to the newly upgraded Enterprise Controller through its virtual IP address.

  16. Back up your Oracle Enterprise Manager Ops Center data using the ecadm command with the backup subcommand and the -r option on the primary Enterprise Controller.

  17. Enable the Auto Service Request (ASR) feature if you disabled it at the beginning of the upgrade.

    1. Expand the Administration section of the Navigation pane, then select Enterprise Controller.

    2. Click Enable ASR in the Actions pane.

Note:

If an error message is displayed indicating that the database must be migrated manually. see Manually Upgrading Database Tables for this procedure.

Note:

To revert to an earlier version after upgrading to version 12.3.1 or later, if you are using a customer-managed database, you must revert both the Enterprise Controller system and database system to the same pre-upgrade state. If you revert to an earlier version, all monitoring data gathered since the reversion point is lost.

Upgrading a Proxy Controller from the Command Line

You can manually update Proxy Controllers to the latest available version to gain access to new and updated features.

The Proxy Controller upgrade log is saved locally as /var/opt/sun/xvm/update-saved-state/update_proxy_bundle_<version number>/updatelog.txt.

If an error occurs during this process, the system is restored to the prior version.

Note:

During the upgrade process, the Proxy Controller is shut down. However, the Proxy Controller must be online at the beginning of the process.

Note:

The upgrade disables the Oracle Solaris 11 update manager service, svc:/application/pkg/update:default, if it is enabled.

Upgrade the Enterprise Controllers before you upgrade the Proxy Controllers.

  1. As root, log in to the Proxy Controller system.
  2. Use the proxyadm command with the backup subcommand to back up the Proxy Controller.

    For example:

    proxyadm backup

    The following options may be used with the proxyadm command:

    • -o|--output <backup file>: Specify the file in which the backup archive is generated. Do not specify a path inside the /opt/*xvm* directories. The default output file is /var/tmp/proxy-backup-<date>-<time>.tar.

    • -l|--logfile <logfile>: Save output from command in <logfile>. Log files are stored in the /var/tmp/ directory.

    • -d|--description <description string>: Embed the <description string> as the description of the backup archive.

    • -t|--tag <tag>: Embed <tag> as a single-word tag in the backup archive.

    • -T|--tempdir <dir>: Specify the temporary staging directory location.

    • -v|--verbose: Increase the verbosity level. This option may be repeated.

  3. Run the proxyadm command with the status subcommand to verify that the Proxy Controller is online. If the Proxy Controller is offline, start it using the proxyadm command with the start subcommand.

    For example:

    # ./proxyadm status
online
  4. Create a temporary directory on the Proxy Controller system, then copy or move the Proxy Controller upgrade bundle from the /var/opt/sun/xvm/images/productUpdate directory on the Enterprise Controller system to the new directory on the Proxy Controller system.
  5. Uncompress and un-tar the upgrade bundle, then list the contents of the temporary directory.

    • For example, on a Linux Proxy Controller:

      # unzip proxy-controller.Linux.i686.12.3.1.608.tar.zip
# tar xf proxy-controller.Linux.i686.12.3.1.608.tar
# ls
xvmoc_full_bundle
proxy-controller.Linux.i686.12.3.1.608.tar
#

    • On an Oracle Solaris Proxy Controller:

      # gzcat proxy-controller.Solaris.i386.12.3.1.608.tar.zip | tar xf -
# ls
xvmoc_full_bundle
proxy-controller.Solaris.i386.12.3.1.608.tar.zip
  6. Change to the xvmoc_full_bundle directory.
  7. Run the install script. 
    # ./install

    The following option may be used with the install script:

    --install <install bundle path> or -i <install bundle path> : If the Oracle Enterprise Manager Ops Center install bundle cannot be found in the /var/opt/sun/xvm/ directory, you must use this option to specify the location of the Oracle Enterprise Manager Ops Center install bundle.

    The upgrade is installed on the Proxy Controller. When the upgrade is complete, the install script indicates that all components have been upgraded.

Upgrading Agent Controllers from the Command Line

You can upgrade Agent Controllers manually. Before you upgrade an Agent Controller, you must upgrade the Proxy Controller that manages it.

If you are upgrading Agent Controllers running in non-global zones, upgrade the Agent Controller in the global zone before upgrading all of the non-global zones. If you are upgrading Agent Controllers running in zones within a Logical Domain, upgrade the Agent Controller in the Control Domain before upgrading the Agent Controllers on the zones.

Caution:

If you upgrade Agent Controllers on virtualized systems in an order other than that specified here, the assets do not display correctly in the user interface. To display the assets correctly, unconfigure the Agent Controllers, then reconfigure or reinstall them in the specified order.

Note:

The upgrade disables the Oracle Solaris 11 update manager service, svc:/application/pkg/update:default, if it is enabled.

This procedure requires root access.

  1. Copy the new Agent Controller bundle from the Enterprise Controller to the client, remove the existing Agent Controller directory, and extract the new Agent Controller bundle.

    For example, on Oracle Solaris 8, 9, or 10 Agent Controllers:

    # scp <IP of Enterprise Controller>:/var/opt/sun/xvm/images/agent/OpsCenterAgent.Solaris.`uname -p`.12.3.1.608.zip /var/tmp
# cd /var/tmp
# rm -r OpsCenterAgent
# unzip OpsCenterAgent.Solaris.`uname -p`.12.3.1.608.zip

    On Oracle Solaris 11 Agent Controllers:

    # scp <IP of Enterprise Controller>:/var/opt/sun/xvm/images/agent/OpsCenterAgent.SolarisIPS.all.12.3.1.608.zip /var/tmp
# cd /var/tmp
# rm -r OpsCenterAgent
# unzip OpsCenterAgent.SolarisIPS.all.12.3.1.608.zip

    On Linux Agent Controllers:

    # scp -p <IP of Enterprise Controller>:/var/opt/sun/xvm/images/agent/OpsCenterAgent.`uname -s`.i686.12.3.1.608.zip /var/tmp
# cd /var/tmp
# rm -r OpsCenterAgent
# unzip OpsCenterAgent.`uname -s`.i686.12.3.1.608.zip
  2. Use the agentadm command with the stop subcommand to stop the Agent Controller.

    For example:

    ./agentadm stop
  3. Install the Agent Controller upgrade. 
    # cd /var/tmp/OpsCenterAgent
# ./install
  4. Use the agentadm command with the configure subcommand and the --keep-connection option to configure the new Agent Controller.

    • On Oracle Solaris systems, this command is in the /opt/SUNWxvmoc/bin/ directory.

    • On Linux systems, this command is in the /opt/sun/xvmoc/bin/ directory.

    For example:

    # ./agentadm configure --keep-connection

    This step also starts the Agent Controller.

    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 Agent Controller installation and configuration. The correct sysidcfg scripts are called properly by sysidcfg.

    Failed to add the zone configuration automation.
Failed to add the service tags recreate script.
  5. Verify the connection. 
    # sc-console list-connections
scn-agent https://192.0.2.1:21165 urn:scn:clregid:1234567-aaaa-bbbb-cccc-123456789abc:YYYYMMDDHHMMSSsss

Related Resources for HA Environment Upgrade Using the Command Line

You can view the Oracle Enterprise Manager Ops Center documents for additional information.

For more information, see these Oracle resources: