Quick Start Guide for RHEL 5.0 Systems

{anchor:top}
{section}
{column:width=70%}
{column}
{column:width=30%}
\\
[!back-org-small.png|alt="back"alt="back"! Installation| Installation]
{column}
{section}

----
{excerpt}

h1. Quick Start Guide for RHEL 5.0 Systems

This quick start guide provides the following installation and configuration procedures that are specifically for systems that are running the Red Hat Enterprise Linux (RHEL) 5.0 operating system (OS):

* [Installing Sun xVM Ops Center Enterprise Controller Software|#21r-ISXOCECS]
* [Configuring Sun xVM Ops Center Enterprise Controller Software|#21r-CSVOCECS]
* [Installing Sun xVM Ops Center Proxy Controller Software|#21r-ISXOCPC]
* [Configuring a Sun xVM Ops Center Proxy Controller|#21r-CSXOCPC]

In a typical initial installation, you install and configure a Sun xVM Ops Center Enterprise Controller first, then you install and configure Sun xVM Ops Center Proxy Controllers. A Proxy Controller automatically installs on the system where you install the Enterprise Controller, but you choose to activate it or not.

After you complete these installation and configuration procedures, use [Discovering Gear and Installing Agents] to begin managing gear using Sun xVM Ops Center.


h2. Before You Begin

Before you begin installing and configuring Sun xVM Ops Center software on an RHEL 5.0 system:
* Be certain that the RHEL 5.0 OS has been installed according to the specifications that [RHEL 5.0 Installation for Sun xVM Ops Center] describes. RHEL 5.0 OS instances that do not meet these specifications might not support Sun xVM Ops Center software installation.
* Verify that the system has the required resources available as described in [Verifying RHEL 5.0 System Resources].
* Use [Verifying Account Access] to verify that you have access to the online accounts that your installation requires.

||Content||Description
| [RHEL 5.0 Installation for Sun xVM Ops Center] | These procedures describe performing a complete installation of RHEL 5.0, to prepare a system for Sun xVM Ops Center Enterprise Controller or Proxy Controller installation. Currently this is the only recommended method to prepare an RHEL 5.0 system for Sun xVM Ops Center installation. |
| [Verifying RHEL 5.0 System Resources] | Before you install a Sun xVM Ops Center Enterprise Controller or Proxy Controller on an RHEL 5.0 system, follow these procedures to verify that your system is ready to accept the new software. |
|[Verifying Account Access]|Certain functions of Sun xVM Ops Center require use of a Sun Online Account. Additional accounts also might be required. Before you configure a Sun xVM Ops Center Enterprise Controller, follow these procedures to verify that you have the valid accounts that your system requires.

h3. Configuring for High Availability

If you are building a high availability configuration for Sun xVM Ops Center, configure your storage device to hold the {{/var/opt/sun/xvm}} directory structure before you install Sun xVM Ops Center software on the _primary_ Enterprise Controller. Refer to [About High Availability in Sun xVM Ops Center] and [Configuring Storage for High Availability] for more information about the high availability configuration for Sun xVM Ops Center.

Consult with Sun Support Services to determine a suitable storage solution for your particular installation and what failover procedures to use.

* Install and configure Sun xVM Ops Center software on the _primary_ Enterprise Controller.
* Install but _do not_ configure Sun xVM Ops Center software on the _secondary_ Enterprise Controller.

h3. Additional Tools and Patches

Sun Support Services might have tools available that automate the verification of many of the system requirements and resources that [Verifying RHEL 5.0 System Resources] describes. Check with Sun Support Services for the following items:

* Pre-installation checklist
* Pre-installation check script
* Patches to apply to the Sun xVM Ops Center software

You must install any Sun xVM Ops Center patches after you install the Sun xVM Ops Center software.

----

h1. {anchor:21r-ISXOCECS} Installing Sun xVM Ops Center Enterprise Controller Software

This procedure describes the steps required to install Sun xVM Ops Center Enterprise Controller software on a system that is running the RHEL 5.0 OS. The {{install}} script that installs the Sun xVM Ops Center Enterprise Controller also automatically installs a Sun xVM Ops Center Proxy Controller on the same system, but it does not enable the Proxy Controller. In configuration steps that follow this software installation procedure, you have the option to enable the Proxy Controller that this procedure installs.

h2. To Install a Sun xVM Ops Center Enterprise Controller

# Create a temporary directory on your system, then copy or move the appropriate Sun xVM Ops Center archive for your system from delivery media to the temporary directory that you created.
For example:
{nt-section}
{code}
# mkdir /var/tmp/xVM
# cp xVM-Ops-Center-rhel-GA-2.1.tar.gz /var/tmp/xVM

{nt-section}
{code}
# cd /var/tmp/xVM
#
{code}
{nt-section}
# Use the {{gunzip}} and {{tar}} commands to uncompress and un-{{tar}} the installation archive, then list the contents of the temporary directory.
Note that the following command example retains the original compressed archive file. The data extracted from the archive consumes about 1 GByte of additional space.
For example:
{nt-section}
{code}
# gunzip xVM-Ops-Center-rhel-GA-2.1.tar.gz
# tar xf xVM-Ops-Center-rhel-GA-2.1.tar
# ls
Copyright LICENSE_MULTILANGUAGE.pdf SunOS_sparc
install Linux_i686 THIRDPARTYLICENSEREADME
license SunOS_i386 xVM-Ops-Center-rhel-GA-2.1.tar
#
{code}
{nt-section}
# Change directory to {{Linux_i686/Product/installer}},and run the {{install}} script.
Installation archives only contain an {{install}} script that is appropriate for their intended OS and platform. You must accept the license agreement to continue with the installation.
For example:
{nt-section}
{code}
# cd Linux_i686/Product/installer
# ./install

Sun Microsystems, Inc. Binary Code License Agreement

(output omitted)

Do you accept the license agreement? [y/n]:
y
{code}
{nt-section}
The screen clears, then the {{install}} script displays a list of installation tasks that automatically updates as the installation proceeds.
For example:
{nt-section}
{code}
xVM Ops Center Satellite Server Installer (version 2.1.0.870 on Linux)

1. Check for installation prerequisites. [Completed]
2. Check that required RPM packages are present. [Completed]
3. Configure file systems. [Completed]
4. Install Agent components. [Not Completed]
5. Add users. [Not Completed]
6. Install prerequisite packages. [Not Completed]
7. Install application packages. [Not Completed]
8. Run postinstall tasks. [Not Completed]
9. Install IPMI tool. [Not Completed]
10. Initialize database. [Not Completed]
11. Install Service container components. [Not Completed]
12. Install Core Channel components. [Not Completed]
13. Install Proxy Core components. [Not Completed]
14. Install Satellite Server components. [Not Completed]
15. Install Update Connection - Enterprise. [Not Completed]
16. Install xVM BUI components. [Not Completed]
17. Install OS provisioning components. [Not Completed]
18. Initialize and start services. [Not Completed]

Executing current step: Install Agent components...
{code}
{nt-section}
# The {{install}} script checks for installation prerequisites, and reports any prerequisites that it finds are not met.
For example, this {{install}} script detected insufficient disk space, and a problem with the {{umask}} that is set in {{/etc/bashrc}}:
{nt-section}
{code}
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: 03removeEmptyDirs.pl
Ignoring job: 27installExpect.pl


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

WARNING: Installation prerequisites not met:
Disk: / 72G needed, 56G available.
Umask: /etc/bashrc sets umask to 02, must be 022.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
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.27138.

t. Try this step again (correct the failure before proceeding)
c. Continue (ignore the warning)
x. Exit
Enter selection: (t/c/x)
{code}
{nt-section}
You can enter {{t}} to try again, {{c}} to continue and ignore the warning, or {{x}} to exit the {{install}} script. Typically you would 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 that is displayed only if you know and accept the impact that the error condition will have 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 warnings that it issues, the {{install}} script continues and installs all Sun xVM Ops Center Enterprise Controller and Proxy Controller components.
\\
When complete, the {{install}} script indicates that all Sun xVM Ops Center components have been installed, and displays a confirmation message. The {{/var/tmp/installer.log.latest}} file contains the installation log.
\\
\\
# Use the {{/opt/sun/xvmoc/bin/satadm}} command to check the status of the Enterprise Controller services.
For example:
{nt-section}
{code}
# /opt/sun/xvmoc/bin/satadm status
online
#
{code}
{nt-section}
# If the Sun xVM Ops Center Enterprise Controller services are offline, you can use the {{/opt/sun/xvmoc/bin/satadm}} command to start them.
For example:
{nt-section}
{code}
# /opt/sun/xvmoc/bin/satadm start -w
satadm: Starting satellite with SMFlite...
satadm: Satellite services have started
#
{code}
{nt-section}


h2. To Install Sun xVM Ops Center Patches

Sun Support Services might have access to patches that are specific to Sun xVM Ops Center, and that might be required to install before you proceed with configuring the software. Contact Sun Support Services for more information about the patches that Sun xVM Ops Center requires. You must install any required Sun xVM Ops Center patches before you configure the software.

----

h1. {anchor:21r-CSVOCECS} Configuring Sun xVM Ops Center Enterprise Controller Software

These procedures describe how to configure a Sun xVM Ops Center Enterprise Controller. Your particular site requirements will determine what configuration options to choose within the configuration process.

h2. Before You Begin

To complete these procedures, you will need to gather following information, and prepare your system accordingly:
* Name and description of the Sun xVM Ops Center Enterprise Controller
* Fully qualified host name of the Sun xVM Ops Center Enterprise Controller
* HTTP proxy information used to connect to the Internet, including:
** HTTP proxy host name and port number
** User name and password information if the HTTP proxy requires authentication
* Local {{root}} user password
* If you want to use a user other than {{root}} to administer the Enterprise Controller, you will need the name and password of the user that you want to use. This user must exist on the Enterprise Controller.
* Sun Online Account (SOA) user name and password for registration with the Sun Inventory online environment
* Identity of the Team with which you will associate the Sun xVM Ops Center Enterprise Controller

Consult with Sun Support Services to determine if Sun xVM Ops Center patches are required. Install all required patches before you configure the Sun xVM Ops Center software.

Before you configure the Sun xVM Ops Center Enterprise Controller software, verify that your system can access the web sites that your configuration will require. These web sites are listed in the To Verify Network Access to Required Web Sites section in [Verifying RHEL 5.0 System Resources].

If you intend to register your Sun xVM Ops Center Enterprise Controller with the Sun Inventory online environment, or to use the software update capabilities of an Enterprise Controller, verify that you have a valid Sun Online account and other account access as described in [Verifying Account Access].

h2. Configuring the Software

Throughout these procedures, references to the _Sun Datacenter_ in the Enterprise Controller Configuration wizard relate to the Sun Inventory online environment.

You can use the Enterprise Controller Configuration wizard described in these procedures to enable the Sun xVM Ops Center Proxy Controller that is co-located with the Sun xVM Ops Center Enterprise Controller. If your Enterprise Controller has more than one active network interface, do not enable the co-located Proxy Controller using the Enterprise Controller Configuration wizard.

If you are building a high availability configuration for Sun xVM Ops Center, configure Sun xVM Ops Center software only on the _primary_ Enterprise Controller. Do not configure Sun xVM Ops Center software on the _secondary_ Enterprise Controller. Refer to [About High Availability in Sun xVM Ops Center] and [Configuring Storage for High Availability] for more information about the high availability configuration for Sun xVM Ops Center.

The Enterprise Controller Configuration wizard presents the following options that require Internet access:
* Registering your Sun xVM Ops Center Enterprise Controller with the Sun Inventory online environment
* Enabling the software update capabilities of Sun xVM Ops Center

The Enterprise Controller Configuration wizard only configures the Enterprise Controller to run in _connected_ mode, even if you choose not to register your Enterprise Controller, and not to enable the software update capabilities of Sun xVM Ops Center. Choose not to use these options that require Internet access if you intend to configure your Enterprise Controller to run in _disconnected_ mode.

To configure your Enterprise Controller to operate in _disconnected_ mode, you must follow the procedures described in [Obtaining a KB Bundle With the Harvester Script], [Loading and Refreshing a KB Bundle], and [Switching the Enterprise Controller Mode], after the Enterprise Controller Configuration wizard completes.

Choose to register or not to register your Sun xVM Ops Center Enterprise Controller with the Sun Inventory online environment, and perform the appropriate steps in the following procedure.

h3. To Configure a Sun xVM Ops Center Enterprise Controller

# Launch a web browser.
# Connect to the following URL, and replace {{system}} with the IP address or host name of the system where the Sun xVM Ops Center Enterprise Controller software is installed.
{panel}
{{https://system:9443}}
{panel}
# Accept any certificates that are presented.
{expand:The Sun xVM Ops Center login page is displayed.}
!1r-loginscreen.jpg|alt="This image shows the login screen for Sun xVM Ops Center."!
{expand}
\\
# In the appropriate fields, enter the name and password of the {{root}} user, or equivalent role, on the system where the Sun xVM Ops Center Enterprise Controller software is installed, and click Log In.
{expand:The Introduction panel of the Enterprise Controller Configuration wizard is displayed.}
!2r-ecintro.jpg|alt="This image shows the Introduction panel for the Sun xVM Ops Center Enterprise Controller Configuration wizard."!
{expand}
\\
# Click Next.
{expand:The Enterprise Controller panel is displayed.}
!3r-ecpanel.jpg|alt="This image shows the Enterprise Controller panel for the Sun xVM Ops Center Enterprise Controller Configuration wizard."!
{expand}
\\
# In the Enterprise Controller panel, provide the following information:
{panel}
* *Name*
Enter the name that you want to use to identify this Sun xVM Ops Center Enterprise Controller. The name that you specify here might differ from the host name of the Sun xVM Ops Center Enterprise Controller.
* *Description*
Enter a brief description of the Sun xVM Ops Center Enterprise Controller.
* *Network Location*
Enter the fully qualified host name of the Sun xVM Ops Center Enterprise Controller.
* *Use an alternative user as Administrative User instead of the currently logged in privileged user.*
If you want to use an administrative user other than the {{root}} user on the Enterprise Controller, select this option. This option enables the Administrative User and Password fields in this panel. Choosing to use an alternative administrative user causes Sun xVM Ops Center to not accept {{root}} as a valid administrative user.
* *Administrative User*
If you chose to use an alternative administrative user, enter the name of the user that will administer this Sun xVM Ops Center Enterprise Controller. This user account must exist on the Enterprise Controller.
* *Password*
Enter the password for the user name that you specified in the Administrative User field.
{panel}
\\
# Click Next.
{expand:The HTTP Proxy panel is displayed.}
!4r-httpproxypanel.jpg|alt="This image shows the HTTP Proxy panel for the Sun xVM Ops Center Enterprise Controller Configuration wizard."!
{expand}
This panel enables you to specify information about an HTTP proxy, if the Sun xVM Ops Center Enterprise Controller requires an HTTP proxy to connect to the Internet. If the Sun xVM Ops Center Enterprise Controller does not require an HTTP proxy to connect to the Internet, enter nothing in this panel. Provide the following information:
{panel}
* *Server*
Enter the host name of the system that acts as the HTTP proxy.
* *Port*
Enter the port of the HTTP proxy.
* *User*
If the proxy requires authentication, enter the user name to use.
* *Password*
If the proxy requires authentication, enter the password associated with the user name that you entered in the User field.
{panel}
\\
# Click Next.
{expand:The Registration panel is displayed.}
!5r-regpanel.jpg|alt="This image shows the Registration panel for the Sun xVM Ops Center Enterprise Controller Configuration wizard."!
{expand}
\\
# The Register Enterprise Controller with Sun Datacenter check box allows you to choose to register the Sun xVM Ops Center Enterprise Controller with the Sun Inventory online service. Your selection in this panel determines what panels are displayed next by the Enterprise Controller Configuration wizard.
#* If you want to register your Enterprise Controller with Sun Inventory online service, select Register Enterprise Controller with Sun Datacenter.
\\
#* If you do not want to register your Enterprise Controller with Sun Inventory online service, do not select Register Enterprise Controller with Sun Datacenter. This is consistent with configuring this Sun xVM Ops Center instance to run in _disconnected_ mode, depending on your choices in the Update Channel panel, and subsequent additional configuration steps. Even if you do not select this option, the Enterprise Controller is initially configured in _connected_ mode.
\\
See [Obtaining a KB Bundle With the Harvester Script], [Loading and Refreshing a KB Bundle], and [Switching the Enterprise Controller Mode] for more information about switching between connected and disconnected modes.
# Click Next.

To complete the Enterprise Controller Configuration, follow the steps in one of these two procedures, depending on your selection in the Registration panel:
* [Registering Your Enterprise Controller and Completing the Configuration|#COMPREG]
* [Completing the Configuration Without Registering Your Enterprise Controller|#NOCOMPREG]

h4. {anchor:COMPREG} Registering Your Enterprise Controller and Completing the Configuration

# {expand:If you selected Register Enterprise Controller with Sun Datacenter in the Registration panel, the Account panel is displayed.}
!6r-accountpanel.jpg|alt="This image shows the Account panel for the Sun xVM Ops Center Enterprise Controller Configuration wizard."!
{expand}
This panel allows you to specify the Sun Online Account that you want to use to register your Enterprise Controller with the Sun Inventory online environment.
\\
Provide the following information:
{panel}
* *User Name*
Enter the Sun Online Account name that you want to use to register your Enterprise Controller with the Sun Inventory online environment. Typically, Sun Online Account names are email addresses.
* *Password*
Enter the password for the Sun Online Account that you specified in the User Name field.
{panel}
\\
# Click Next.
{expand:If you have more than one team associated with your Sun Online Account, the Team panel is displayed.}
!7r-teampanel.jpg|alt="This image shows the Team panel for the Sun xVM Ops Center Enterprise Controller Configuration wizard."!
{expand}
By default, the Sun Online Account that you specified in the Account panel is displayed in the Team pull-down list. Select the team that you want to associate with this Sun xVM Ops Center Enterprise Controller.
\\
# Click Next.
{expand:The Proxy Controller panel of the Enterprise Controller Configuration wizard is displayed.}
!8r-pcpanel.jpg|alt="This image shows the Proxy Controller panel for the Sun xVM Ops Center Enterprise Controller Configuration wizard."!
{expand}
The Enable Local Proxy Controller check box in this panel allows you to enable the Sun xVM Ops Center Proxy Controller that was automatically installed when you installed the Sun xVM Ops Center Enterprise Controller. To be made operational, Sun xVM Ops Center requires at least one functioning Proxy Controller.
#* If you intend to configure one or more Proxy Controllers on systems other than the system on which the Sun xVM Ops Center Enterprise Controller is installed, you typically would not enable the Proxy Controller that is co-located with the Sun xVM Ops Center Enterprise Controller.
#* If your Enterprise Controller has multiple active network interfaces, do not use the Enable Local Proxy Controller check box to enable the co-located Proxy Controller. Instead, use the [Configuring a Sun xVM Ops Center Proxy Controller|#21r-CSXOCPC] procedure to configure the co-located Proxy Controller after the Enterprise Controller Configuration wizard completes.
#* If you do not intend to configure more Proxy Controllers, then you must enable the co-located Proxy Controller to make this Sun xVM Ops Center instance operational.
#* To enable software updates for the Enterprise Controller itself, you must enable the co-located Proxy Controller before you manually enable a Sun xVM Ops Center agent on the Enterprise Controller. You may choose to enable the co-located Proxy Controller for this purpose now, or do so manually at a later time.
\\
Select Enable Local Proxy Controller to enable the co-located Proxy Controller, if required for your Sun xVM Ops Center installation.
\\
\\
# To complete the Sun xVM Ops Center Enterprise Controller configuration and registration process, click Next.
{expand:The Summary panel is displayed.}
!8r-summarypanel.jpg|alt="This image shows the Summary panel for the Sun xVM Ops Center Enterprise Controller Configuration wizard."!
{expand}
\\
# To complete the Enterprise Controller Configuration wizard, click Finish.
{expand:The xVM Ops Center main page is displayed.}
!9r-mainpage.jpg|alt="This image shows the main page for Sun xVM Ops Center."!
{expand}

h4. {anchor:NOCOMPREG} Completing the Configuration Without Registering Your Enterprise Controller

# {expand:If you did not select Register Enterprise Controller with Sun Datacenter in the Registration panel, the Update Channel panel is displayed.}
!12r-ucpanel.jpg|alt="This image shows the Update Channel panel for Sun xVM Ops Center."!
{expand}
This panel enables you to specify the Sun Online Account you want to use to enable the software update capabilities of Sun xVM Ops Center. The Update Channel panel accepts the following information:
{panel}
* *User Name*
Enter the name of an existing Sun Online Account.
* *Password*
Enter the password for the Sun Online Account that you specified in the User Name field.
{panel}
Choosing not to enter a Sun Online Account (SOA) in this panel configures this Sun xVM Ops Center instance to run with no access to software update information. To complete the Enterprise Controller configuration to run in _disconnected_ mode, perform the [Obtaining a KB Bundle With the Harvester Script], [Loading and Refreshing a KB Bundle], and [Switching the Enterprise Controller Mode] procedures after the Configuration wizard completes.
\\
Choosing to enter an SOA in this panel configures this Sun xVM Ops Center instance to have access to software update data, even though the Enterprise Controller is not registered with Sun Inventory.
\\
# Click Next.
{expand:The Proxy Controller panel of the Enterprise Controller Configuration wizard is displayed.}
!13r-pcpanel.jpg|alt="This image shows the Proxy Controller panel for the Sun xVM Ops Center Enterprise Controller Configuration wizard."!
{expand}
The Enable Local Proxy Controller check box in this panel allows you to enable the Sun xVM Ops Center Proxy Controller that was automatically installed at the time you installed the Sun xVM Ops Center Enterprise Controller. To be made operational, Sun xVM Ops Center requires at least one functioning Proxy Controller.
#* If you intend to configure one or more Proxy Controllers on systems other than the system on which the Sun xVM Ops Center Enterprise Controller is installed, you typically would not enable the Proxy Controller that is co-located with the Sun xVM Ops Center Enterprise Controller.
#* If you do not intend to configure more Proxy Controllers, then you must enable the co-located Proxy Controller to make this Sun xVM Ops Center instance operational.
#* If your Enterprise Controller has multiple active network interfaces, do not use the Enable Local Proxy Controller check box to enable the co-located Proxy Controller. Instead, use the [Configuring a Sun xVM Ops Center Proxy Controller|#21r-CSXOCPC] procedure to configure the co-located Proxy Controller after the Enterprise Controller Configuration wizard completes.
#* To enable software updates for the Enterprise Controller itself, you must enable the co-located Proxy Controller before you manually enable a Sun xVM Ops Center agent on the Enterprise Controller. You may choose to enable the co-located Proxy Controller for this purpose now, or do so manually at a later time.
\\
Select Enable Local Proxy Controller to enable the co-located Proxy Controller, if required for your Sun xVM Ops Center installation.
\\
\\
# To complete the Sun xVM Ops Center Enterprise Controller configuration process, click Next.
{expand:The Summary panel is displayed.}
!14r-summarypanel.jpg|alt="This image shows the Summary panel for the Sun xVM Ops Center Enterprise Controller Configuration wizard."!
{expand}
\\
# To complete the Enterprise Controller Configuration wizard, click Finish.
{expand:The xVM Ops Center main page is displayed.}
!15r-mainpage.jpg|alt="This image shows the main page for Sun xVM Ops Center."!
{expand}

h4. Adding User-Defined Tags For HA Configurations

Add a user-defined tag for the primary Enterprise Controller that is used in a high availability (HA) configuration, to help differentiate it from the secondary Enterprise Controller. For example, you could add a tag called {{primary}} to the list of tags for the primary Enterprise Controller.

To add a user-defined tag for the primary Enterprise Controller:

# In the Gear panel, select All Gear.
{expand:The All Managed Gear list is displayed.}
!10r-allmanage.jpg|alt="This image shows the All Managed Gear list for Sun xVM Ops Center."!
{expand}
\\
# Select the entry for the primary Enterprise Controller.
\\
# Click the Edit Gear icon.
{expand:The Edit Gear panel is displayed.}
!11r-editgear.jpg|alt="This image shows the Edit Gear panel for Sun xVM Ops Center."!
{expand}
\\
# Enter a tag that identifies the Enterprise Controller as primary.
\\
# Click Save.

h3. Verifying the Enterprise Controller Configuration

# To verify the connections that have been established for this Sun xVM Ops Center configuration, run the {{sc-console list-connections}} command.
For example:
{nt-section}
{code}
# sc-console list-connections
scn-proxy https://localhost:443 urn:scn:clregid:0c9ae818-c6d9-47d2-9af0-9dedb69b1065:20090127080008352
localhost https://localhost:443 urn:scn:clregid:2f0e3713-dc11-4370-8fe3-8feae979eb14:20090127075915950
#
{code}
{nt-section}
The {{scn-proxy}} entry above indicates that the co-located Proxy Controller is connected to the Enterprise Controller.

----

h1. {anchor:21r-ISXOCPC} Installing Sun xVM Ops Center Proxy Controller Software

This procedure describes the steps required to install Sun xVM Ops Center Proxy Controller software on a system that meets the recommended specifications for this installation.

Use this procedure only to install a Sun xVM Ops Center Proxy Controller on a system _other than_ the system on which the Sun xVM Ops Center Enterprise Controller is installed.

h2. Before You Begin

Before proceeding with the Sun xVM Ops Center Proxy Controller installation, check that your system's resources meet the requirements described by [Verifying RHEL 5.0 System Resources].

Sun Support Services might have tools available that automate verifying many of the system requirements and resources that [Verifying RHEL 5.0 System Resources] and [Verifying Solaris System Resources] describe. Check with Sun Support Services for the following items:

* Pre-installation checklist
* Pre-installation check script
* Patches to apply to the Sun xVM Ops Center software

You must install any Sun xVM Ops Center patches after you install the Sun xVM Ops Center software.

h2. To Install a Sun xVM Ops Center Proxy Controller

# mkdir /var/tmp/xVM
# cp xVM-Ops-Center-rhel-GA-2.1.tar.gz /var/tmp/xVM
{code}
{nt-section}
# Change to the directory where the archive is located on your system.
For example:
{nt-section}
{code}
# cd /var/tmp/xVM
#
{code}
{nt-section}
# Use the {{gunzip}} and {{tar}} commands to uncompress and un-{{tar}} the installation archive, then list the contents of the temporary directory.
Note that the following command example retains the original compressed archive file. The data extracted from the archive consumes about 1 GByte of additional space.
For example:
{nt-section}
{code}
# gunzip xVM-Ops-Center-rhel-GA-2.1.tar.gz
# tar xf xVM-Ops-Center-rhel-GA-2.1.tar
# ls
Copyright LICENSE_MULTILANGUAGE.pdf SunOS_sparc
install Linux_i686 THIRDPARTYLICENSEREADME
license SunOS_i386 xVM-Ops-Center-rhel-GA-2.1.tar
#
{code}
{nt-section}
# Change directory to {{Linux_i686/Product/installer}}, and run the {{install -p}} script.
Installation archives only contain an {{install}} script that is appropriate for their intended OS and platform. The {{-p}} option causes the {{install}} script to only install the Sun xVM Ops Center proxy-related components. You must accept the license agreement to continue with the installation.
For example:
{nt-section}
{code}
# cd Linux_i686/Product/installer
# ./install -p
Sun Microsystems, Inc. Binary Code License Agreement

(output omitted)

Do you accept the license agreement? [y/n]: y

{code}
{nt-section}
The screen clears, then the {{install}} script displays a list of installation tasks that automatically updates as the installation proceeds.
For example:
{nt-section}
{code}
xVM Ops Center Proxy Server Installer (version 2.1.0.870 on Linux)

1. Check that required RPM packages are present. [Completed]
2. Install IPMI tool. [Completed]
3. Install Agent components. [Not Completed]
4. Install application packages. [Not Completed]
5. Install Core Channel components. [Not Completed]
6. Install Proxy Server components. [Not Completed]
7. Install UCE Http proxy. [Not Completed]
8. Install OS provisioning components. [Not Completed]
9. Initialize (but do not start) services. [Not Completed]

Executing current step: Install Agent components...
{code}
{nt-section}
When complete, the {{install}} script indicates that all Sun xVM Ops Center components have been installed, and indicates that the Proxy Controller is ready to be configured.

h2. To Install Sun xVM Ops Center Patches

Sun Support Services might have access to patches that are specific to Sun xVM Ops Center, and that might be required to install before you proceed with configuring the software. Contact Sun Support Services for more information about the patches that Sun xVM Ops Center requires. You must install any required Sun xVM Ops Center patches before you configure the software.

----

h1. {anchor:21r-CSXOCPC} Configuring a Sun xVM Ops Center Proxy Controller

Use this procedure to register a Sun xVM Ops Center Proxy Controller with a Sun xVM Ops Center Enterprise Controller.

h2. Before You Begin

If you designated an alternative administrator of the Sun xVM Ops Center 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.

Consult with Sun Support Services to determine what Sun xVM Ops Center patches are required. Install all required patches before you register the Sun xVM Ops Center Proxy Controller with the Enterprise Controller.

h2. To Register a Sun xVM Ops Center Proxy Controller With an Enterprise Controller

# Create a temporary directory, for example, {{/var/tmp/xVM}}, to hold the password file that you will create in this procedure.
{nt-section}
{code}
# mkdir -p /var/tmp/xVM
{code}
{nt-section}
# Create an empty file named {{/var/tmp/xVM/mypasswd}}, and set its permission mode to 400.
{nt-section}
{code}
# touch /var/tmp/xVM/mypasswd
# chmod 400 /var/tmp/xVM/mypasswd
{code}
{nt-section}
# Edit the {{/var/tmp/xVM/mypasswd}} file so that it contains the password of the user that you designated the administrator of your Sun xVM Ops Center Enterprise Controller.
The following {{echo}} command appends the password to the {{/var/tmp/xVM/mypasswd}} file. Replace _password_ with the correct password.
For example:
{nt-section}
{code}
# echo 'password' > /var/tmp/xVM/mypasswd
{code}
{nt-section}
# Use the {{/opt/sun/xvmoc/bin/proxyadm}} command to associate the Sun xVM Ops Center Proxy Controller with the Sun xVM Ops Center Enterprise Controller.
The example commands below use the following options:
{panel}
{{-s}} -- Specify the hostname 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 Sun xVM Ops Center Enterprise Controller.
{{-p}} -- Specify the absolute pathname 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.
{panel}
Accept any certificates that are presented. Co-located Proxy Controller configuration does not display certificate information.
For example:
{nt-section}
{code}
[root@imperial installer]# /opt/sun/xvmoc/bin/proxyadm configure -s x4200-brm-13.central -u droot -p /var/tmp/xVM/mypasswd

Certificate:
Serial Number: 437971753
Version: 3
Issuer: CN=x4200-brm-13_ca
Subject: CN=x4200-brm-13_agent
Not valid before: Sun Jun 15 15:38:07 MDT 1969
Not valid after: Sun Apr 15 15:38:07 MDT 2029

Certificate:
Serial Number: 1842029596
Version: 3
Issuer: CN=x4200-brm-13_ca
Subject: CN=x4200-brm-13_ca
Not valid before: Sun Jun 15 15:38:06 MDT 1969
Not valid after: Sun Apr 15 15:38:06 MDT 2029

Accept server's certificate? (y|n)
y
Connection registered successfully.
[root@imperial installer]#
{code}
{nt-section}
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:
{nt-section}
{code}
# /opt/sun/xvmoc/bin/proxyadm configure -s x4200-brm-13.central -u droot -p /var/tmp/xVM/mypasswd -a 172.20.48.69
(output omitted)
{code}
{nt-section}
For more information about the {{proxyadm}} command, see the [{{proxyadm}} man page|proxyadm].
# Use the {{/opt/sun/xvmoc/bin/proxyadm}} command to start the Sun xVM Ops Center Proxy Controller services.
For example:
{nt-section}
{code}
# /opt/sun/xvmoc/bin/proxyadm start -w
proxyadm: Starting proxy with SMFlite...
milestone/multi-user:default... ...started.
application/scn/proxy-enable:default... ...started.
application/management/common-agent-container:scn-proxy... ...started.
application/scn/uce-proxy:default... ...started.
application/scn/proxy-available:default... ...started.
proxyadm: Proxy services have started
#
{code}
{nt-section}
# To verify the connection that has been established for this Sun xVM Ops Center Proxy Controller configuration, run the {{sc-console list-connections}} command.
For example:
{nt-section}
{code}
# sc-console list-connections
scn-proxy https://x4200-brm-13.central:443 urn:scn:clregid:352b1035-90cb-4eef-9f7c-a3ab0a183967:20090417205841084
#
{code}
{nt-section}
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 {{sc-console}} command also lists a connection for {{localhost}}. For example:
{nt-section}
{code}
# sc-console list-connections
scn-proxy https://x4200-brm-13.central:443 urn:scn:clregid:fafb4e7d-8456-47e4-91d5-abb4f12a6145:20090417211322217
localhost https://localhost:443 urn:scn:clregid:47cb5955-b17a-4c6c-a248-f8772bc659d7:20090415222004145
#
{code}
{nt-section}

----
{excerpt}

{panel:borderStyle=none|titleBGColor=#BDBEC0|bgColor=#f5f5f5}
*Where to Go From Here*
If you have additional Proxy Controllers to install and configure, return to [Installing Sun xVM Ops Center Proxy Controller Software|#21r-ISXOCPC].
After you have established a functional Sun xVM Ops Center Enterprise Controller and at least one Proxy Controller, you can use [Discovering Gear and Installing Agents] to begin discovering gear and managing it in Sun xVM Ops Center.
{panel}