Verifying Solaris System Resources

Verify that your system is ready to accept the Sun xVM Ops Center Enterprise Controller or Proxy Controller software before you proceed with the installation. This page describes the system resources to check.

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

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

Verifying Solaris system resources requires the following tasks:

Checking the Operating System Release
Checking the Installed Software Group
Checking the Zone Identity
Checking the Available Disk Space
Checking Swap Space
Verifying the Amount of System Memory
Verifying the webservd User and Group
Verifying an Alternate Administrative User Exists
Sun xVM Ops Center Users and Groups
Verifying the umask Value
Verifying That the SUNWgcc Package Is Installed
Verifying the Locations of ssh Binaries
Verifying Correct IP Address Resolution
Verifying That /usr/local Is Writeable
Verifying the Date and Time
Verifying Online cryptosvc and gss Services
Removing the SMClintl Package
Verifying Network Access to Required Web Sites
Verifying ssh Access for the root User
Verifying Network Port Access

Before You Begin

These procedures assume that you are logged in as the root user on the system on which you intend to install Sun xVM Ops Center Enterprise Controller or Proxy Controller software. You can check these system resources in any order.

To Check the Operating System Release

Verify that a release of the Solaris OS that is compatible with Sun xVM Ops Center software is installed. Sun xVM Ops Center requires at least Solaris 10 Update 3 (11/06) for SPARC or x86 systems. The /etc/release file lists the Solaris OS release installed on your system. For example:

# cat /etc/release
                       Solaris 10 8/07 s10s_u4wos_12b SPARC
           Copyright 2007 Sun Microsystems, Inc.  All Rights Reserved.
                        Use is subject to license terms.
                            Assembled 16 August 2007
# 

To Check the Installed Software Group

Verify that your Solaris system has been installed with one of these two software groups:

• SUNWCXall - Entire distribution with OEM support
• SUNWCall - Entire distribution

To check the installed software group, display the content of the /var/sadm/system/admin/CLUSTER file. For example:

# cat /var/sadm/system/admin/CLUSTER
CLUSTER=SUNWCall
# 

To Check the Zone Identity

On Solaris systems, Sun xVM Ops Center Enterprise Controller and Proxy Controller software can only be installed in the global zone. You can use the zonename command to verify that you are working in the global zone. For example:

# zonename
global
#

To Check the Available Disk Space

Use the df -h command to list the space utilization on the Enterprise Controller, and verify that you have at least 70 GBytes available within the file system that will hold the /var/opt/sun/xVM directory structure. For example:

# df -h
Filesystem             size   used  avail capacity  Mounted on
/dev/dsk/c1t0d0s0       82G   4.0G    78G     5%    /
/devices                 0K     0K     0K     0%    /devices
ctfs                     0K     0K     0K     0%    /system/contract
proc                     0K     0K     0K     0%    /proc
mnttab                   0K     0K     0K     0%    /etc/mnttab
swap                   5.1G   624K   5.1G     1%    /etc/svc/volatile
(output omitted)

High availability (HA) configurations for Sun xVM Ops Center use transferable storage to hold the /var/opt/sun/xvm directory structure within a separate file system. Refer to About High Availability in Sun xVM Ops Center and Configuring Storage for High Availability for more information about HA configurations.

To Check Swap Space

Sun xVM Ops Center Enterprise Controllers and Proxy Controllers require at lease 4 GBytes of configured swap space. The install script checks for this. Use the swap -l command to list the amount of configured swap space. For example:

# swap -l
swapfile             dev  swaplo blocks   free
/dev/dsk/c1t0d0s1   118,1      16 8395184 8395184
#

To Verify the Amount of System Memory

Use the prtconf command to display the amount of installed memory on your system. For example:

# prtconf | grep -i meg
Memory size: 4096 Megabytes
# 

To Verify the webservd User and Group

The webservd user and group are created by default in Solaris 10. This user and group must exist before you install Sun xVM Ops Center Software.

Examine the content of the /etc/passwd, /etc/shadow, and /etc/group files to confirm that the webservd user and group exist. For example:

# grep webservd /etc/passwd
webservd:x:80:80:WebServer Reserved UID:/:
# grep webservd /etc/shadow
webservd:*LK*:::::::
# grep webservd /etc/group 
webservd::80:
#

If the webservd user or group does not exist, create the missing user or group using the UID and GID values listed in the example above.

To Verify an Alternate Administrative User Exists

If you want to designate a user other than root as the administrative user for Sun xVM Ops Center, you must verify that the user exists on the system where you intend to install the software. For example:

# logins -l droot
droot           0       root            0       Super-User
#

Sun xVM Ops Center Users and Groups

Sun xVM Ops Center installation creates a number of users and groups on the Enterprise Controller and Proxy Controllers. Review the list of users and groups, and verify that they do not conflict with existing policies. If required by account management policies, add these users and groups before you install the Sun xVM Ops Center software.

Sun xVM Ops Center creates these users and groups with the following UID and GID values:

# cat /etc/group
(output omitted)
uce-sds::98194050:
scndb::98194051:
jet::98194052:
# 
# cat /etc/passwd
(output omitted)
svctag:x:95:12:Service Tag UID:/:
scn:x:231796:3::/:/bin/sh
xvm:x:60:60::/:/bin/sh
scncon:x:231798:1::/:/bin/true
uce-sds:x:231799:98194050:UCE Engine:/opt/SUNWuce/server:/bin/sh
scndb:x:231800:98194051:SCS PostgreSQL User:/opt/SUNWscs:/bin/sh
allstart:x:231801:1:AllStart User:/var/opt/sun/xvm/osp/data:/bin/sh
#

scncon.password=2EzafaJE

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# 

To Verify That the SUNWgcc Package Is Installed

Sun xVM Ops Center uses the gcc compiler during the installation process. Verify that the SUNWgcc package is installed, and that the gcc compiler is located in /usr/sfw/bin.

# pkginfo SUNWgcc
system      SUNWgcc gcc - The GNU C compiler
# ls -l /usr/sfw/bin/gcc
-r-xr-xr-x   3 root     bin       122260 Jan 22  2005 /usr/sfw/bin/gcc
#

To Verify the Locations of ssh Binaries

The binary files for ssh operations must be stored in their standard locations, even if OpenSSH is used. Verify that the following files are stored using the listed path names:

• /usr/bin/scp
• /usr/bin/ssh
• /usr/bin/ssh-keygen
• /usr/bin/ssh-keyscan

For example:

# ls /usr/bin/scp /usr/bin/ssh /usr/bin/ssh-keygen /usr/bin/ssh-keyscan
/usr/bin/scp          /usr/bin/ssh          /usr/bin/ssh-keygen   /usr/bin/ssh-keyscan
#

To Verify Correct IP Address Resolution

Verify that the configured naming services resolve the correct IP address for the host name that is assigned to your system. For example:

# host amritsar.central
amritsar.central.sun.com has address 172.20.27.185
# 

Verify that the /etc/hosts file contains the correct host name and IP address for your system. For example:

# grep amritsar /etc/hosts
172.20.27.185   amritsar        loghost
#  

To Verify That /usr/local Is Writeable

Some software components of Sun xVM Ops Center are installed in the /usr/local directory. Verify that the /usr/local directory is writeable, and is not a remotely mounted, read-only directory. For example:

# df -h /usr/local
Filesystem             size   used  avail capacity  Mounted on
/dev/dsk/c1t0d0s0       82G   4.0G    78G     5%    /
# ls -ld /usr/local
drwxr-xr-x   7 root     root         512 Feb 23 08:33 /usr/local
#

To Verify the Date and Time

Verify that the correct date and time are set on your system. For example:

# date
Thu Mar 11 13:28:59 MST 2010
#

If the date and time are not correct, reset them. See Troubleshooting for a description of an error that might occur in the Enterprise Controller Configuration wizard if the date and time is not set correctly.

To Verify Online cryptosvc and gss Services

Sun xVM Ops Center requires the cryptosvc and gss SMF services to be online. For example:

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

You can use the svcadm command to enable these services if they are not online.

To Remove the SMClintl Package

The SMClintl freeware package conflicts with Sun xVM Ops Center software and must be removed. Use the pkgrm command to remove the SMClintl package before you install Sun xVM Ops Center software. For example:

# pkgrm SMClintl
(output omitted)

To Verify Network Access to Required Web Sites

Use a web browser to verify that your system can access the following URLs:

https://getupdates1.sun.com
https://inv-cs.sun.com
https://inventory.sun.com
https://a248.e.akamai.net 
https://identity.sun.com
ftp://ftp.sunfreeware.com 

For access to Red Hat Linux updates, verify that your system can access the following URLs:

https://www.redhat.com
http://rhn.redhat.com
https://rhn.redhat.com 
https://download.rhn.redhat.com 

For access to SUSE Linux updates, verify that your system can access the following URLs:

http://www.novell.com
https://www.novell.com
http://download.novell.com 
https://you.novell.com 

Use the wget command to verify that you can access the getupdates1.sun.com web site and download a sample file.

1. If you are using a proxy to access the Internet, set the https_proxy environment variable to point to the proxy server. For example:

   # export https_proxy="http://myproxy.company.com:8080" 
   

   Enter the fully qualified domain name of your proxy server instead of myproxy.company.com.
   

2. Use the wget command to download the sample file named channels.xml and save it locally as /tmp/channels.xml.
   The wget command uses these relevant options:
   • -O – Specifies the name of the file to create on the local system
   • --http-user – Specifies the SOA to use for authentication to getupdates1.sun.com
   • --http-password – Specifies the password for SOA that you provide for the --http-user option
   • --proxy-user – (Optional) Specifies the user name used for authentication with an HTTPS proxy
   • --proxy-password – (Optional) Specifies the password for the user name that you provide for the --proxy-user option
     The wget command is stored by default in /usr/sfw/bin on Solaris systems. For example:

     # /usr/sfw/bin/wget https://getupdates1.sun.com/channels3/channels.xml -O /tmp/channels.xml --http-user="account@sun.com" --http-password="password"
     --11:43:41--  https://getupdates1.sun.com/channels3/channels.xml
                => `/tmp/channels.xml'
     Resolving getupdates1.sun.com... 198.232.168.136
     Connecting to getupdates1.sun.com|198.232.168.136|:443... connected.
     HTTP request sent, awaiting response... 302 Moved Temporarily
     Location: https://a248.e.akamai.net/f/248/21808/15m/sun.download.akamai.com/21808/sc/channels3/channels.xml?AuthParam=1236019547_e9120d30e1ac62650c8f9284dfe47663&TUrl=L0QdUQV8Z4i0fdED3QTP3SJDWA8FMyaJsHfIWf4X29kTWQpKEzIbwqFuyRPZ&TicketId=3qfzk1SIPR9R&GroupName=SWUP&BHost=sdlc3h.sun.com&FilePath=/sc/channels3/channels.xml&File=channels.xml [following]
     --11:43:42--  https://a248.e.akamai.net/f/248/21808/15m/sun.download.akamai.com/21808/sc/channels3/channels.xml?AuthParam=1236019547_e9120d30e1ac62650c8f9284dfe47663&TUrl=L0QdUQV8Z4i0fdED3QTP3SJDWA8FMyaJsHfIWf4X29kTWQpKEzIbwqFuyRPZ&TicketId=3qfzk1SIPR9R&GroupName=SWUP&BHost=sdlc3h.sun.com&FilePath=/sc/channels3/channels.xml&File=channels.xml
                => `/tmp/channels.xml'
     Resolving a248.e.akamai.net... 208.51.221.73, 208.51.221.48
     Connecting to a248.e.akamai.net|208.51.221.73|:443... connected.
     HTTP request sent, awaiting response... 200 OK
     Length: 66,505 (65K) [application/xml]
     
     100%[============================================================================>] 66,505       397.16K/s             
     
     11:43:42 (396.55 KB/s) - `/tmp/channels.xml' saved [66505/66505]
     
     # ls -l /tmp/channels.xml
     -rw-r--r--   1 root     root       66505 Feb 19 01:04 /tmp/channels.xml
     #
     

     In this example, account@sun.com and password represent the SOA and SOA password that you must provide.

To Verify ssh Access for the root User

If you intend to use root login credentials to install the Sun xVM Ops Center agent, verify that the ssh daemon on your target systems is configured to allow root user logins. Custom discovery allows you to specify a non-root user for ssh access. If you use a non-root user for ssh access, this configuration is not necessary.

To verify ssh access for the root user, try using ssh to log in as root to the system. If that attempt succeeds, no further action is necessary. If that attempt fails, check the value of the PermitRootLogin parameter in the /etc/ssh/sshd_config file. If PermitRootLogin is set to no, edit the /etc/ssh/sshd_config file, and change the PermitRootLogin setting to yes. Then use the svcadm command to restart the svc:/network/ssh:default service. For example:

# svcadm restart svc:/network/ssh:default
# 

To Verify Network Port Access

Verify that your system allows the following network services and ports: