These procedures describe how to install Proxy Controllers on Linux systems.
If you decided to install Proxy Controllers outside of the configuration wizard when you configured the Enterprise Controller, or if you need to install Proxy Controllers after completing the initial installation, you can use one of two methods:
Deploy it remotely using the Proxy Deployment Wizard
Install and configure it manually
The Deploy Proxy Wizard can be used to deploy and configure one or more remote Proxy Controllers, and to configure the co-located Proxy Controller. Proxy Controllers can be deployed at any time; however, Oracle Enterprise Manager Ops Center requires at least one Proxy Controller.
This installation installs, or upgrades to, Java Runtime Environment (JRE) 7 Update 71. Later versions of JRE are not affected.
Note:
If your environment includes Oracle VM Server for x86, you must modify the Proxy Controllers that will manage Oracle VM Server for x86 to use JRE 6 as described in the Modifying the Java Version for Oracle VM Management section.You must not install a Proxy Controller in an environment where there is a web proxy which requires authentication between the Enterprise Controller and the Proxy Controller. Many OS update functions are not usable for systems managed by such a Proxy Controller.
To install a Proxy Controller through the UI, the Enterprise Controller must be able to reach the Proxy Controller with an SSH connection using port 22 during the update process. This connection is used to transfer Proxy Controller bundles and execute commands on the Proxy Controller system. If your security restrictions do not allow this connection, install the Proxy Controller from the command line.
Note:
To provision an Oracle VM Server for SPARC, the Proxy Controller that performs the provisioning must be installed on Oracle Solaris.You can use the Deploy Proxy Wizard to deploy and configure one or more Proxy Controllers.
Click the Enterprise Controller in the Administration section of the Navigation Pane.
Click Deploy Proxy in the Actions pane. The Proxy Controller Deployment page is displayed.
Choose a deployment option:
Co-located Proxy: Configures the co-located Proxy Controller.
Remote Proxies: Lets you remotely install and configure one or more Proxy Controllers. Click Next.
If you select Co-located Proxy, a popup is displayed indicating that the local Proxy Controller is being configured. Click Close to close the popup.
Skip the Proxy Controllers and Remote Proxy Controllers pages and proceed to the Proxy Controller Status page.
If you select Remote Proxies, Proxy Controller deployment steps are displayed. Proceed to the next step.
If you selected Remote Proxies, the Proxy Controllers page is displayed. Select an option:
Deploy Automatically: Lets you deploy a remote Proxy Controller through the wizard.
Deploy Manually: Lets you install and configure a Proxy Controller manually.
If you selected Remote Proxies, the Remote Proxy Controllers page is displayed. Click the add and remove icons to create an entry for each new Proxy Controller, then enter credentials for each remote system. Proxy Controllers are installed and configured on these systems.
Hostname or IP address: The host name or IP address of the target system.
SSH User name: If root SSH access is allowed on the target system, enter the root user name and password in the SSH User and SSH Password fields.
SSH Password: The password associated with the SSH user name.
(Optional) Privileged Role: If root SSH access is not allowed on the target system, enter the login user name and password in the SSH User and SSH Password fields, then enter the root user name and password in the Privileged Role and Role Password fields.
(Optional) Role Password: If you entered the root user name in the Privileged Role field, enter the root password.
Create Tunnel: Check this box to create a tunnel to the Proxy Controller.
Port: If you want the Proxy Controller to use a port other than the default, enter that port number.
Maintenance Mode: Check this box to start the Proxy Controller in maintenance mode.
Click Next.
The Proxy Controller Status page is displayed.
View the status of the configured Proxy Controllers. Each Proxy Controller that you enabled or provisioned should be online.
(Optional) Click Check, then enter a host name or IP address. The connectivity and status of the specified host is checked.
Click Next.
The Summary page is displayed.
Click Finish.
This section describes the steps required to install and configure Proxy Controller software on a Linux system that meets the recommended specifications for this installation. Proxy Controllers can be installed at any time; however, Oracle Enterprise Manager Ops Center requires at least one Proxy Controller. Use this procedure only to install and configure a Proxy Controller on a system other than the system on which the Enterprise Controller is installed.
This installation installs, or upgrades to, Java Runtime Environment (JRE) 7 Update 71. Later versions of JRE are not affected.
You can use the OC Doctor to verify that the system is prepared for the installation. See http://java.net/projects/oc-doctor for more information about the OC Doctor.
You must not install a Proxy Controller in an environment where there is a web proxy which requires authentication between the Enterprise Controller and the Proxy Controller. Many OS update functions are not usable for systems managed by such a Proxy Controller.
Note:
To provision an Oracle VM Server for SPARC, the Proxy Controller that performs the provisioning must be installed on Oracle Solaris.Before proceeding with the Proxy Controller installation, check that your system's resources meet the system requirements using the OC Doctor or using the manual procedure.
Create a temporary directory on your target system, then copy or move the appropriate Proxy Controller bundle from the /var/opt/sun/xvm/images/productUpdate on the Enterprise Controller system to the temporary directory that you created. The installation archive consumes about 700 MBytes of disk space. You must use the same Oracle Enterprise Manager Ops Center archive version as the one used to install the Enterprise Controller. For example:
# mkdir /var/tmp/OC # cp proxy-controller.Linux.i686.12.1.2.2140.tar.zip /var/tmp/OC
Change to the directory where the archive is located on your system. For example:
# cd /var/tmp/OC #
Use the unzip and tar commands to uncompress and un-tar the archive, then list the contents of the temporary directory. The following command example retains the original compressed archive file. The data extracted from the archive consumes about 1 GB of additional space. For example:
# unzip proxy-controller.Linux.i686.12.1.2.2140.tar.zip # tar xf proxy-controller.Linux.i686.12.1.2.2140.tar # ls xvmoc_full_bundle proxy-controller.Linux.i686.12.1.2.2140.tar #
Change to the xvmoc_full_bundle directory, and run the install script. Each installation archive only contains an install script that is appropriate for its intended OS and platform. For example:
# cd xvmoc_full_bundle # ./install
The screen clears, then the install script displays a list of installation tasks that automatically updates as the installation proceeds. For example:
Ops Center Proxy Controller Installer
(version 12.1.2.2140 on Linux)
1. Check for installation prerequisites. [Completed]
2. Install prerequisite packages. [Completed]
3. Install Expect. [Not Completed]
4. Install IPMI tool. [Not Completed]
5. Install Agent components. [Not Completed]
6. Install application packages. [Not Completed]
7. Install Core Channel components. [Not Completed]
8. Set Proxy database credentials. [Not Completed]
9. Install Proxy Controller components. [Not Completed]
10. Install UCE Http proxy. [Not Completed]
11. Install OS provisioning components. [Not Completed]
12. Initialize (but do not start) services. [Not Completed]
Executing current step: Install Expect...
When complete, the install script indicates that all components have been installed, and indicates that the Proxy Controller is ready to be configured.
Use the /opt/sun/xvmoc/bin/proxyadm command to check the status of the Proxy Controller services. If the installation has completed successfully, the services should be online. For example:
# /opt/sun/xvmoc/bin/proxyadm status online #
Once a Proxy Controller has been installed, it must be configured to connect it with the Enterprise Controller. Use this procedure to configure a Proxy Controller with an Enterprise Controller.
Consult with Oracle Support to determine what Oracle Enterprise Manager Ops Center updates are required. Install all required updates before you register the Proxy Controller with the Enterprise Controller.
Note:
If you designated an alternative Administrative User for the Enterprise Controller, use the same user name to register your Proxy Controller with the Enterprise Controller. Otherwise, use the root user to register your Proxy Controller with the Enterprise Controller.Note:
If you are configuring a co-located Proxy Controller in an environment with Enterprise Controller High Availability, register the Proxy Controller using the Virtual IP address of the Enterprise Controller.To Register a Proxy Controller With an Enterprise Controller
Create a temporary directory, for example, /var/tmp/OC, to hold the password file that you create in this procedure.
# mkdir -p /var/tmp/OC
Create an empty file named /var/tmp/OC/mypasswd, and set its permission mode to 400.
# touch /var/tmp/OC/mypasswd # chmod 400 /var/tmp/OC/mypasswd
Edit the /var/tmp/OC/mypasswd file so that it contains the password of the user that you designated the administrator of your Enterprise Controller. The following echo command appends the password to the /var/tmp/OC/mypasswd file. Replace password with the correct password. For example:
# echo 'password' > /var/tmp/OC/mypasswd
Use the /opt/sun/xvmoc/bin/proxyadm command with the configure subcommand to associate the Proxy Controller with the Enterprise Controller. The example commands below use the following options:
-s: Specify the host name or IP address of the Enterprise Controller with which to register the Proxy Controller.
-u: Specify the user that you designated the administrator of your Enterprise Controller.
-p: Specify the absolute path name of the file that contains the password for the user you specified with the -u option.
-a: Specify the IP address that the Proxy Controller should use. This option is required if you want the Proxy Controller to be identified on a specific NIC by the Enterprise Controller. Accept any certificates that are presented. The co-located Proxy Controller configuration does not display certificate information.
For example:
# /opt/sun/xvmoc/bin/proxyadm configure -s enterprise-controller.company -u droot -p /var/tmp/OC/mypasswd Certificate: Serial Number: 270256981 Version: 3 Issuer: CN=enterprise-controller_ca Subject: CN=enterprise-controller_agent Not valid before: Wed Jul 02 19:32:56 MDT 1969 Not valid after: Mon Apr 02 19:32:56 MDT 2029 Certificate: Serial Number: 1062961758 Version: 3 Issuer: CN=enterprise-controller_ca Subject: CN=enterprise-controller_ca Not valid before: Wed Jul 02 19:32:54 MDT 1969 Not valid after: Mon Apr 02 19:32:54 MDT 2029 Accept server's certificate? (y|n) y Connection registered successfully. #
If you are manually configuring the co-located Proxy Controller because your Enterprise Controller has more than one active network interface, use the -a option to identify the particular interface that you want the Proxy Controller to use. Specify the IP address that is assigned to the interface that you want to use. For example:
# /opt/sun/xvmoc/bin/proxyadm configure -s enterprise-controller.company -u droot -p /var/tmp/OC/mypasswd -a 172.20.25.18 (output omitted)
Use the /opt/sun/xvmoc/bin/proxyadm command with the start subcommand and the -w option to start the Proxy Controller services. For example:
# /opt/sun/xvmoc/bin/proxyadm start -w proxyadm: Starting proxy with SMF... proxyadm: Proxy services have started #
To verify the connection that has been established for this Proxy Controller configuration, run the sc-console list-connections command. For example:
# sc-console list-connections scn-proxy https://enterprise-controller.company:443 urn:scn:clregid:18a0206a-a5c4-4c8c-90f2-d4eb1d2b623b:20090419213707452 #
The sc-console list-connections command lists the connection that is established with the Enterprise Controller. If you are enabling a co-located Proxy Controller, the command also lists a connection for localhost. For example:
# sc-console list-connections scn-proxy https://enterprise-controller.company:443 urn:scn:clregid:6d0ec2ab-b868-46ab-8475-4a5d726dee69:20090419214450735 localhost https://localhost:443 urn:scn:clregid:a9f5243e-f46e-4b32-85ca-76e2c12c0707:20090403015601612 #
For more information about the proxyadm command, see the Oracle Enterprise Manager Ops Center Administration Guide.
By default, Proxy Controllers use Java Runtime Environment (JRE) 7. If a Proxy Controller will be used to manage Oracle VM Servers for x86, the Proxy Controller must be modified to use JRE 6.
As root, log on to the Proxy Controller system.
Stop the Proxy Controller using the proxyadm command with the stop subcommand and -w option. For example:
/opt/sun/xvmoc/bin/proxyadm stop -w
List the contents of the /usr/java directory and note the latest version of Java 6. For example:
# ls /usr/java jdk1.6.0_65
Use the cacaoadm command to set the Java version. For example:
/opt/sun/cacao2/bin/cacaoadm set-param -i scn-proxy java-home=/usr/java/jdk1.6.0_65
Restart the Proxy Controller using the proxyadm command with the stop subcommand and -w option. For example:
/opt/sun/xvmoc/bin/proxyadm start -w
For more information about Enterprise Controller Administration or Agent Controller installation, go to one of the following resources:
See the Oracle Enterprise Manager Ops Center Administration Guide for information about site administration.
See the Administering Your Environment Using Oracle Enterprise Manager Ops Center guide for a condensed walkthrough of post-installation administrative tasks.
See the Oracle Enterprise Manager Ops Center Feature Reference Guide for information about installing Agent Controllers and discovering and managing assets.
For end-to-end examples, see the Deploy How To library at http://docs.oracle.com/cd/E40871_01/nav/deployhowto.htm and the Operate How To library at http://docs.oracle.com/cd/E40871_01/nav/operatehowto.htm.