Verifying Resources for Agent Installation

Verify that the systems that you intend to manage are ready for Sun xVM Ops Center agent software installation. This page describes the system resources to check for both Solaris and Linux systems. These required resources are typically available in systems that are running current versions of operating system software. Review the list of required resources to determine if it is likely that any resource is missing from your systems.

Sun Support Services might have tools available that automate verifying many of the system requirements and resources listed here. 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
• Updated Sun xVM Ops Center agent bundles
• Advice about specific patch dependencies that relate to Sun xVM Ops Center agent installation

Verifying resources for agent installation requires the following tasks:

Solaris OS: Verifying Required Packages and Devices
Linux OS: Verifying Required Packages
Verifying ssh Installation
Verifying Patches on Solaris 10 Systems With Non-Global Zones Installed
Agent Patch Dependencies
Verifying Unique Service Tags
Verifying the umask Value
Solaris OS: To Verify cryptosvc and gss Services

Solaris OS: To Verify Required Packages and Devices

The following packages and devices are required for Sun xVM Ops Center agent installation:

SUNWadmfr
SUNWadmfw
SUNWbash
SUNWgcmn
SUNWgtar
SUNWgzip
SUNWlibpopt
SUNWsshcu
SUNWsshdr
SUNWsshdu
SUNWsshr
SUNWsshu
SUNWswmt
SUNWtoo
SUNWwgetr
SUNWwgetu
SUNWxcu4
SUNWxwfnt
SUNWxwice
SUNWxwplr
SUNWxwplt
SUNWxwrtl
SUNWzip
/dev/random
/dev/urandom

Check Solaris 8 systems in particular for the SUNWbash package and the /dev/random and /dev/urandom devices. The patch 112438-03 installs these devices.

You can use the pkginfo command to verify that a packages is installed. For example:

# pkginfo SUNWadmfr
system      SUNWadmfr System & Network Administration Framework Configuration
#

Linux OS: To Verify Required Packages

Linux systems require the following utilities for Sun xVM Ops Center agent installation. The example package names listed in the following table are from an RHEL 5.0 system.

You can use the rpm -qf file command to find the name of the package that installed a file. You can use the rpm -q package command to verify that a specific package has been installed.

Sun xVM Ops Center agent installation on Red Hat Linux systems requires the 32-bit versions of the following packages to be installed:

• e2fsprogs-version-i386.rpm
• pam-version-i386.rpm
• libxml2-version-i386.rpm

For example, RHEL 5.0 systems install the following packages:

• e2fsprogs-1.39-8.el5
• pam-0.99.6.2-3.14.el5
• libxml2-2.6.26-2.1.2

To Verify ssh Installation

Although root ssh access is not required for Sun xVM Ops Center agent installation, ssh must be available on systems on which you want to provision Sun xVM Ops Center agents.

Solaris OS: Use the pkginfo command to verify that the SUNWsshu package is installed on Solaris systems. For example:

# pkginfo SUNWsshu
system      SUNWsshu SSH Client and utilities, (Usr)
#

Linux OS: Use the rpm command to check for ssh installation. For example:

# which ssh
/usr/bin/ssh
# rpm -qf /usr/bin/ssh
openssh-clients-4.3p2-16.el5
#

To Verify Patches on Solaris 10 Systems With Non-Global Zones Installed

Solaris 10 systems that have non-global zones installed must have the following patches applied to assure proper function of the Solaris patch utilities.

Patches for Solaris 10 SPARC systems:

• 124630-03 – System Administration Applications, Network, and Core
• 122660-07 – Zones patch, obsoleted now by Solaris 10 8/07 kernel patch 120011-14

Patches for Solaris 10 x86 systems:

• 124631-03 – System Administration Applications, Network, and Core
• 122661-07 – Zones patch, obsoleted now by Solaris 10 8/07 kernel patch 120012-14

Patches 122660-07 and 122661-07 are required on systems with non-global zones installed. These patches must be installed in single user mode. Because these patches depend on kernel patch 118833-36 or 118855-36, a reboot is required after you install them. Plan for the time required to take the affected systems offline to install these patches. Systems that are running at least Solaris 10 8/07 already have these patches applied.

To Verify Unique Service Tags

Sun xVM Ops Center requires unique service tag uniform resource names (URNs) in each operating system instance that it manages. Systems that are have been installed using Solaris flash archives that contain the /var/sadm/servicetag/registry/servicetag.xml file may have identical URNs. Service tag URNs are stored by default in the /var/sadm/servicetag/registry/servicetag.xml file.

To Identify and Remove Duplicate Service Tags

1. On systems where you want to check for duplicate service tags, use the stclient -x client command to display the service tags that are stored in the /var/sadm/servicetag/registry/servicetag.xml file.
   For example:

   # stclient -x
   <?xml version="1.0" encoding="UTF-8"?>
   <registry urn="urn:st:4aa51776-9cea-e85b-ab14-aedd6ca93e49" version="1.0">
     <service_tag>
       <instance_urn>urn:st:c76d9a11-f64b-418b-e9dc-a2fb18e7b76e</instance_urn>
       <product_name>Solaris 10 Operating System</product_name>
       <product_version>10</product_version>
       <product_urn>urn:uuid:5005588c-36f3-11d6-9cec-fc96f718e113</product_urn>
       <product_parent_urn>urn:uuid:596ffcfa-63d5-11d7-9886-ac816a682f92</product_parent_urn>
       <product_parent>Solaris Operating System</product_parent>
       <product_defined_inst_id/>
       <product_vendor>Sun Microsystems</product_vendor>
       <platform_arch>sparc</platform_arch>
       <timestamp>2009-01-09 22:23:42 GMT</timestamp>
       <container>global</container>
       <source>SUNWstosreg</source>
       <installer_uid>95</installer_uid>
     </service_tag>
   </registry>
   
   # 
   

   
   

2. Compare the instance_urn values on the systems that were installed using Solaris flash archives, and determine if duplicate URNs exist.
   If the instance_urn for the Solaris operating system matches the instance_urn from another system, you can remove and re-generate the service tag registry to correct the problem.
   
3. To remove the service tag registry, remove the rm /var/sadm/servicetag/registry/servicetag.xml file.
   For example:

   # rm /var/sadm/servicetag/registry/servicetag.xml
   # ls /var/sadm/servicetag/registry/servicetag.xml
   /var/sadm/servicetag/registry/servicetag.xml: No such file or directory
   # 
   

   
   

4. Use the svcadm command to restart the stosreg service, then verify that the /var/sadm/servicetag/registry/servicetag.xml file exists.
   For example:

   # svcadm restart stosreg
   # ls /var/sadm/servicetag/registry/servicetag.xml
   /var/sadm/servicetag/registry/servicetag.xml
   #
   

   
   

5. Use the stclient -x command to verify that the new instance_urn values are unique.
   For example:

   # stclient -x
   <?xml version="1.0" encoding="UTF-8"?>
   <registry urn="urn:st:fdd576f6-b95c-63e6-ab54-f142ecca360f" version="1.1.4">
     <service_tag>
       <instance_urn>urn:st:cbf9acfb-0c48-c248-fb07-9816382ceb29</instance_urn>
       <product_name>Solaris 10 Operating System</product_name>
       <product_version>10</product_version>
       <product_urn>urn:uuid:5005588c-36f3-11d6-9cec-fc96f718e113</product_urn>
       <product_parent_urn>urn:uuid:596ffcfa-63d5-11d7-9886-ac816a682f92</product_parent_urn>
       <product_parent>Solaris Operating System</product_parent>
       <product_defined_inst_id/>
       <product_vendor>Sun Microsystems</product_vendor>
       <platform_arch>sparc</platform_arch>
       <timestamp>2009-03-13 23:23:24 GMT</timestamp>
       <container>global</container>
       <source>SUNWstosreg</source>
       <installer_uid>95</installer_uid>
     </service_tag>
   </registry>
   
   #
   

To Create Flash Archives and Exclude Service Tags

The flar and flarcreate commands both accept the -x and -X options, which enable you to specify files to exclude from Solaris flash archives. Use these options to exclude the /var/sadm/servicetag/registry/servicetag.xml file from the Solaris flash archives that you will use to install Solaris onto systems that you intend to manage with Sun xVM Ops Center. Refer to the flar(1M) and flarcreate(1M) man pages for more information about creating Solaris flash archives.

Agent Patch Dependencies

When Sun xVM Ops Center provisions an agent, it also automatically installs a set of patches. These patches might depend on other patches that are assumed to be installed.

Sun xVM Ops Center installs the following patches as part of agent provisioning:

For systems running Solaris 10 versions earlier than Solaris 10 (06/06): Agent provisioning installs the patchadd patch 119254-52 or 119255-52. These patches depend on patches 120900 and 120901 or 121133 and 121334 respectively, which are incorporated into Solaris 10 (06/06) or later. The patches 120900, 120901, 121133, and 121334 require a reboot to ensure proper installation. Plan for the down time required to install these patches, if necessary.

The patches 119254-63 and 119255-63 correct issues with Solaris 10 single user mode operations. Before you provision a Sun xVM Ops Center agent, verify that no IDR patches have been installed that address Solaris 10 single user mode operations.

Check with Sun Support Services for updated Sun xVM Ops Center agent bundles.

To Verify the umask Value

Verify that the umask for the root user or equivalent role is set to 0022. Different shells report this value differently. The following examples list output from the umask command for the Bourne shell, the Korn shell, and the C-shell, in descending order. In all three examples, the umask value is correct.

# sh
# umask
0022
# ksh
# umask
022
# csh
host# umask
22
host#

Solaris OS: To Verify cryptosvc and gss Services

Use the svcs command to verify that the cryptosvc and gss services are enabled.
For example:

# svcs cryptosvc gss
STATE          STIME    FMRI
online         Mar_31   svc:/system/cryptosvc:default
online         Mar_31   svc:/network/rpc/gss:default
#