OPSWARE SA Single Core, New Installation

Roseville QA
SA 9.0 Installation
Guide
Document Date Author Section Nature of Change
Version
1.0 10/10/08 Jenny Trinh First version for 7.8
2.0 2/4/09 Janise Orcutt Added section, pre-requisites.
Added note under reimaging to
not use the ISO that Carl created
for SAS 7.0 and 7.5.
3.0 2/9/09 Janise Orcutt 1 Added solaris conf files to list

2 Updated primary and upload

interviews to add new questions
that have been added recently.
4.0 4/7/09 Janise Added notes about gateway IPs
and restarting failed installer.

Added more system

requirements.

4.1 4/14/09 Janise 1 Added note about kernel

upgrades.
4.2 4.16.2009 Janise added note about UTC timezone
and website.
5.0 5/6/09 Janise Removed instructions for
installing opsware agent and SE
connector. They are old

Removed instructions for

reimaging with the Opsware ISO,
since it won’t work with SA 7.8.
5.0 5/6/09 Janise added bullet for what to select
when installing the OS.
6.0 06/01/09 Ling 1 Made Pre-requisites as section I,
and so on…
2 Added SAS configuration:
10. Configurae the system run
level
11. Remove packages
12. Edit login file
13. Configure time zone to UTC
14. Configure the ntp on the core
system
15. Reboot system
16. Make image of the Core
system
3 Made table for the installation of
oracle-sas, Primary, Upload,
opsware-asa along with the OI
response parameters answers

1|Page
 4 Edited section IV
– Create SAS OCC Client
user
– Download/install the SA
Client Launcher

5 Added section V -
Troubleshooting/QA

6.1 6/11/09 Janise updated section Upload

Content, OI response
parameters
6.2 7/22/09 Janise 1 Added list of SAS core
servers.
7.0 9/28/09 Jenny Modified to install SAS 8.0

7.1 10/13/09 Janise 2 Added step to verify and set

system LANG setting, needed
for oracle and SAS.
7.2 10/14/09 Janise 2 Documented option to run with
“advanced” parm so you will
get the interview mode, which
is needed for first-time install.
Added back in the steps and
parameters and answers from
7.8 install doc.
7.3 10/14/09 Janise 2 Removed steps to install asas
component since not used
anymore. Get SE connector
from HPLN.
7.4 8/18/10 Janise 2 Edited system pre-requisites in
different places.

Moved “win_util” and crypto

setup to end of section.
7.5 8/18/10 Janise 2&3 Put win_util and engineering
crypto files on voltorb. Edited
instructions to get files from
voltorb.

Added page #s.

Added steps and info about

release builds to beginning of
Section 3.

2|Page
1 Section I – System Pre-requisites
1. System Information

System name IP Used as Facility name

For example:

System name IP Used as Facility name

Lulu.rose.hp.com 16.93.40.225 SAS master MESHCORE1
Mesh core
Sagitta.rose.hp.com 15.3.104.85 SAS slave MESHCORE2
Mesh core

2. Core system hardware requirements

RAM – require more than 8GB
CPU – 4 CPU or dual
Disk space – require more than 100GB

Or please read the SAS planning and Installation Guide on chapter 2 for each
release to see the new requirements for the RAM and disk space.

2 The SA core is supported on these platforms in 9.0:

 Red Hat 4 (x86_64), (64-bit) U6, U7 (U7 has core dump issues), U8
 Red Hat 5 U2-3 (x86_64), (64-bit)
 SUSE 10 SP2 (x86_64)
 Solaris 10 (Sparc), U6
 VMware 3 (ESX & ESXi?) running RedHat 4/5 on x86_64

Notes:
3. Kernel must be on a later version
o For example, RHEL4 needs U8
o The SMP kernel can be updated if needed. See web for downloads:
http://people.redhat.com/vgoyal/rhel4/RPMS.kernel/

3|Page
3 Section II – SA Configuration on the Core System
The configuration on the Core system:
1. Modify the system file selinux, change “SELINUX=enforcing” to
“SELINUX=disabled” and save it

# vi /etc/sysconfig/selinux
SELINUX=disabled

2. Modify system file ifcfg-lo

Add MTU=16036 at the last line of the file

# vi /etc/sysconfig/network-scripts/ifcfg-lo
MTU=16036

3. Check system ifcfg-eth0 file, and make sure it has the settings specified below.

# vi /etc/sysconfig/network-scripts/ifcfg-eth0
BOOTPROTO=static
IPADDR=<your core system IP address>
NETMASK=< your core system netmask>
GATEWAY= <gateway that your core system use>

4. Make sure your host has a FQDN.

a. Modify the /etc/hosts file, see below as example.

#vi /etc/hosts
127.0.0.1 localhost.localdomain localhost
16.93.40.225 lennox.rose.hp.com lennox

b. Run hostname command:

hostname lennox.rose.hp.com

5. Check resolv.conf to make sure the name servers are correct (For example)
# vi /etc/resolv.conf
search rose.hp.com
nameserver 16.110.135.51
nameserver 16.110.135.52

4|Page
6. Modify the network file if it is not set correctly (Make sure the HOSTNAME and
GATEWAY are correct)
For example:
# vi /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=lennox.rose.hp.com
GATEWAY=16.93.40.1

7. OS patch/packages requirements and download

If your systems don’t have the required patches/packages installed, the SAS
installer will tell which patch/package you need when you run the install scripts.
Then you need to do google search for the patches/packages, and download and
install them into your core systems.
You can pre-check to see what patches/packages should be installed from the
build directory at:

# mount voltorb.rose.hp.com:/opsware /mnt

/mnt/distributions/oro.0/opsware_37.0.xxxx.0-
oracle_sas/disk001/opsware_installer/tools

For RedHat Core:

Linux_core_inst_rqmts.conf
Linux_oracle_rqmts.conf
Linux_satellite_rqmts.conf

For Sun Solaris Core :

SunOS_core_inst_rqmts.conf
SunOS_oracle_rqmts.conf

Generally speak, you need to download and install the below packages for OS
system is RedHat 4 update 7 and RedHat5 update 2. (There may be more. This
depends on how the patches/packages selected to install during the OS
installation.)

i) gamin-devel-xxxx
ii) libaio-devel-xxxx
iii) ncompress-xxxx
iv) openmotif-xxxx
v) sharutils-xxxx
vi) sysstat-xxxx
vii) vnc-xxxx

5|Page
 Install the patch/package on Linux: (Example)
#rpm -ivh gamin-devel-xxxx

If there is an older package installed, Upgrade or remove the old package and
install the new package. To look for existing installed package, use:
# rpm -qa |grep packagename

To upgrade:
#rpm –U package.rpm

Here is a useful Linux patches/packages download web site: http://rpm.pbone.net

8. Configure the system run level in file inittab, set the run level to 3 .
Looking for the run level line, for example: “ id:5:initdefault:” . And change
“ id:5:initdefault:” to “ id:3:initdefault:”, save it.

#vi /etc/inittab
id:3:initdefault:

9. Remove below Packages

a. httpd
b. rsync
c. samba
d. dhcpd
e. apache
f. tftp
You need to remove all of them.
How to seach and remove them: (For example)
#rpm -qa |grep httpd
httpd-2.2.3-11.el5_1.3
httpd-manual-2.2.3-11.el5_1.3

Remove them:
# rpm -e --nodeps httpd-2.2.3-11.el5_1.3
#rpm -e --nodeps httpd-manual-2.2.3-11.el5_1.3

Note: If you have problem to remove the samba-common, add .i386 at end, and
remove it again.

# rpm -e --nodeps samba-common-3.0.25b-0.4E.6.i386

Note: If you need to remove two similar RPMs, use this command:

6|Page
 # rpm -e --allmatches packagename

10. Edit login file

Add line “session required pam_limits.so” at bottom of the file
and save it.

#vi /etc/pam.d/login
session required pam_limits.so

11. Configure time zone to UTC

a. Copy file UTC to file localtime (You can make a copy of the original
localtime file first, then copy UTC to the localtime)

# cp /usr/share/zoneinfo/UTC /etc/localtime

b. Modify file clock as below and save it

#vi /etc/sysconfig/clock
ZONE=”UTC”
UTC=true
ARC=false

12. Configure the ntp.conf on the core system to point to HP time server.
a. Comment out below lines in /etc/ntp.conf file
server 0.rhel.pool.ntp.org
server 1.rhel.pool.ntp.org
server 2.rhel.pool.ntp.org
server 127.127.1.0

b. Add “server ntp.hp.net” at the last line of the ntp.conf file and
save it
You can use one of the hp time servers as below. But ping the system first
before use it.

Note: ntp.hp.net is the primary one ; the rest of two is the backup.
ntp.hp.net
r01msedc.rose.hp.com
r02msedc.rose.hp.com

7|Page
 # vi /etc/ntp.conf
#server 0.rhel.pool.ntp.org
#server 1.rhel.pool.ntp.org
#server 2.rhel.pool.ntp.org
#server 127.127.1.0 # local clock
server ntp.hp.net

c. Enable the ntpd via typing command “ntsysv” on the core system. On the
ntsysv pop-up dialog box, search for ntpd and enable it.
# ntsysv

d) Start the ntpd

For example:
# /etc/rc.d/init.d/ntpd start
Starting ntpd: [ OK ]

e) Check to make sure ntpd is running via command

#ps –ef |grep ntpd

13. Reboot the system (if you changed the network configuration)
This makes all changes take effect.

8|Page
14. Test the Core system
a) nslookup <FQDN> & <Short name of computer>, <IP address> and ping
hostname, ip, from other computer to make sure your box is properly
configured.

Type nslookup (For example):

#nslookup lennox.rose.hp.com
#nslookup lennox
#nslookup 16.93.40.220

Ping the system (For example):

#ping lennox.rose.hp.com
#ping 16.93.40.220

b) Check if the core system host name is correct after the reboot

#hostname

c) Check the date and time on the Core system to make sure the time is
UTC time.

#date
Wed Jun 3 15:51:37 UTC 2009

Note: Please DON’T change the date and time. It must be set to the correct
date/time in UTC zone.

15. Check the system LANG settings and set them if necessary.

[root@izaza ~]# locale

LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

9|Page
 Enter the following into /etc/sysconfig/i18n
LANG=” en_US.UTF-8”
SUPPORTED=”en_US.UTF-8:en_US:en”

16. Set up some folders and copy some SA files onto the system before installing SA.
a. Mount to the source system, voltorb:
i. mkdir /mnt
ii. mount voltorb.rose.hp.com:/opsware /mnt
b. Create win_util directory on the core system, then copy all win_util files
to the core system folder /home/win_util
#mkdir /home/win_util
#cp /mnt/SA_core_setup/win_util_files/* /home/win_util

c. Create directory to hold the engineering crypto file. This is an internal lab
file that enables developers to get onto your core via a backdoor from the
web. If you don’t do this, the SA installer will create its own, but
developers can’t use it.
#mkdir -p /var/opt/opsware/crypto/cadb/realm
#cp /mnt/SA_core_setup/engr_crypto_file/* /var/opt/opsware/crypto/cadb/realm

>> At this point you have configured your system for installing SAS. <<

17. Make image of the Core system

You should make an image of your core systems and store them to some safe
place. So later when you need to have a clean core system for fresh install
SAS. You don’t need to re-install the OS and go through the system and SAS
configuration again. This can save your time. For Linux system, you can use
g4l to backup and restore the OS image.

How to use g4l instruction and g4l software can be found at:
\\silccrls.rose.hp.com\APPIQ\Opsware\Servers Imaging\Linux\G4L\Disk_Images_Slow

10 | P a g e
4 Section III – Install SAS on the Core System

 In Roseville, you can install the SAS from the mirrored build system:
o voltorb.rose.hp.com
 Released SAS software:
o /mnt/Opsware_Released_Bits/7.0 – 9.0
 Test (pre-release) SAS software:
o /mnt/distributions/
 silver.0 – for SA 7.8x versions
 oro.0 – for SA 9.0x versions
 amber.0 – for SA 9.1x versions


You must install the SA base release before installing any patch releases. For
example, SA 7.8 must be installed before installing 7.84. SA 9.0 must be installed
before installing 9.01.

Install the SAS Components

On the Core system:
1. Mount to the mirrored build system voltorb.rose.hp.com, and change directory to the
location where the build you want to install. Here I will use the SA 9.0 base release as
example.

Mount to voltorb:
# mount voltorb.rose.hp.com:/opsware /mnt

2. Path to SA 9.0 base release folder. If you are installing from the base release folder,
then substitute this path in the installation steps:
a. Use this: /mnt/Opsware_Released_Bits/9.0/
b. Instead of: /mnt/distributions/oro.0/

3. Note: When you see any FAILURE during the installation, please stop via say no to
question:
Do you wish to continue with install? (y/n): n

Also see Section V – Troubleshooting/QA

A - Install the oracle-sas

11 | P a g e
 1. Run the SAS Oracle install_opsware.sh
Run the first time install using the “advanced” option. This will make it go into
interview mode so you can give it all the correct parameters for installation. Use
advanced option as follows:

/mnt/distributions/oro.0/opsware_40.0.2538.0-
oracle_sas/disk001/opsware_installer/install_opsware.sh –advanced
If you have a response file from a previous installation, use it as follows, so it will not
go into interview mode:

/mnt/distributions/oro.0/opsware_40.0.2538.0-
oracle_sas/disk001/opsware_installer/install_opsware.sh –r
/var/tmp/oiresponse.oracle_sas

2. Select the simple interview mode

Install Type: "Oracle RDBMS for SAS"

Please select the interview mode. Simple mode uses default values for many of the
configuration parameters. Advanced mode allows you to fully configure the
installation.

1 - Simple Interview Mode

2 - Advanced Interview Mode

Please select the interview mode from the menu, type 'h' for help, 'q' to quit: 1

3. Answer the SAS Oracle installation OI response parameters

# Parameter Prompt Statement Answer
1 truth.oaPwd Please enter the password for the opsware_admin
opsware_admin user. This is the password
used to connect to the Oracle database.:
2 truth.dcNm Please enter the short name of the facility DATACENTER1
where Opsware Installer is being run (no
spaces) [DATACENTER1]:
3 truth.servicename Please enter the service name (aka TNS <enter>
name) of the Model Repository instance in
the facility where Opsware Installer is
being run [truth.DATACENTER1]
4 truth.port Please enter the port on which the Model <enter>
Repository database is listening. [1521]

All parameters have values. Do you wish to finish the interview? (y/n): y

12 | P a g e
 Name of response file to write [/usr/tmp/oiresponse.oracle_sas]: <Default>

Would you like to continue the installation using this response file? (y/n): y

4. Select the “1- Oracle RDBMS for SAS” to install

Welcome to the Opsware Installer.
Please select the components to install.
1 (*) Oracle RDBMS for SAS
Enter a component number to toggle ('a' for all, 'n' for none).
When ready, press 'c' to continue, or 'q' to quit.

Selection: c

############# <PREREQUISITE CHECKING> ############

<it prints out the results>

Review the results, and if you think it’s OK to continue, then enter “y” at the next
prompt.

Do you wish to continue with install? (y/n): y

Wait for the oracle-sas installation finished successfully. (It takes about 10 minutes.)

4. Make a copy of the OI response file for later upgrade use

cp /var/tmp/oiresponse.oracle_sas /var/tmp/oiresponseFiles/oiresponse.oracle_sas.C1

B – Install SAS primary components

1. Run the primary install_opsware.sh

Run the first time install using the “advanced” option. This will make it go into interview
mode so you can give it all the correct parameters for installation. Use advanced option as
follows:

/mnt/distributions/oro.0/opsware_40.0.2538.0-
primary/disk001/opsware_installer/install_opsware.sh --advanced

If you have a response file from a previous installation, use it as follows, so it will not go
into interview mode:

/mnt/distributions/oro.0/opsware_40.0.2538.0-
primary/disk001/opsware_installer/install_opsware.sh –r

13 | P a g e
oiresponse.slices_master_typical

2. Select “1 - Multimaster Opsware Core - First Core”

opsw

3. Select “1 - Typical Component Layout Mode”

Please select the component layout mode. In a "typical" install, components are already
bundled together in a pre-defined configuration. "Custom" install allows you to install
components "a la carte."

1 - Typical Component Layout Mode

2 - Custom Component Layout Mode

Please select the interview mode from the menu, type 'h' for help, 'q' to quit: 1

5. Select “1- Simple Interview Mode”

Please select the interview mode. Simple mode uses default values for many of the
configuration parameters. Advanced mode allows you to fully configure the installation.

1 - Simple Interview Mode

2 - Advanced Interview Mode

Please select the interview mode from the menu, type 'h' for help, 'q' to quit: 1

6. Answer the SAS Primary installation OI response parameters

# Parameter Prompt Statement Answer
1 truth.oaPwd Please enter the password for the opsware_admin
opsware_admin user. This is the password
used to connect to the Oracle database.:
2 decrypt_passwd Please enter the password for the crypto
cryptographic material:

3 cast.admin_pwd Please enter the password for Opsware Default

admin user. This is the password that will be
used to authenticate user 'admin' to
Opsware. [opsware_admin]:

4 truth.dcId Please enter the facility ID (number only, default

less than or equal to 999, with no leading
zeros). On the first core, the facility ID

14 | P a g e
 should be 950 or less. [1]:

5 truth.dcNm Please enter the short name of the facility DATACENTER1

where Opsware Installer is being run (no
spaces) [DATACENTER1]:

6 truth.dcSubDom Please enter the subdomain for this facility rose.hp.com

(lowercase, no spaces):

7 truth.authDom Please enter the authorization domain HP.COM

[MY_CUSTOMER.COM]:

8 default_locale Please enter the default locale for users of Default

the Opsware Command Center (en/ja) [en]:

9 windows_util_loc Please enter the directory that contains the /home/win_util

Microsoft's utilities (Press Control-I for list
of required files) [/tmp]:

10 word_tmp_dir Please enter directory where Package Default

Repository will temporarily place content
during uploads.
[/var/opt/opsware/wordbot_tmp/]:

11 truth.servicename Please enter the service name (aka TNS Default

name) of the Model Repository instance in
the facility where Opsware Installer is being
run [truth]:

12 word.store.host Please enter the IP address of the NFS server <your_core_IP>

for the Software Repository. For satellite
installs, please enter the IP address of the i.e. 16.93.40.220
Software Repository Cache.:
13 word.store.path Please enter the absolute path on the NFS Default
server for Software Repository
[/var/opt/opsware/word]:

14 mgw_address Please enter the IP address of the <your_core_IP>

Management Gateway.:
i.e. 16.93.40.220
15 mgw_tunnel_listener_port Please enter the port on which this Default
Management Gateway will listen for
connections from other Gateways. [2001]:

16 mgw_proxy_port Please enter the port on which this Default

Management Gateway can be contacted to

15 | P a g e
 request connections to core component.
[3003]:

17 agw_proxy_port Please enter the port on which Agents can Default

contact the Agent Gateway to request
connections to core components. [3001]:

18 media_server.linux_media Please enter the pathname of the Linux Default

media [/media/opsware/linux]:

19 media_server.sunos_media Please enter the pathname of the Solaris Default

media [/media/opsware/sunos]:

20 media_server.windows_me Please enter the pathname of the Windows Default

dia media [/media/opsware/windows]:

21 boot_server.speed_duplex Please enter the default network Default

speed/duplex setting for Solaris SPARC
servers [autoneg]:

22 bootagent.host Please enter the OS Provisioning Boot <your_core_IP>

Server ip or hostname:
i.e. 16.93.40.220
23 twist.nasdata.host Please enter the hostname or IP address of Default
the NAS server (Enter "none" if NAS is not
installed) [none]:

24 spoke.cachedir Please enter the pathname of where you Default

wish the local cache of snapshots and audits
to be. This will require a large amount of
disk space (4G by default)
[/var/opt/opsware/compliancecache]:
All parameters have values. Do you wish to finish the interview? (y/n): y

Name of response file to write [/usr/tmp/oiresponse.slices_master_typical]: <Default>

Would you like to continue the installation using this response file? (y/n): y

6. Select all components to install

Welcome to the Opsware Installer.
Please select the components to install.
1 (*) Model Repository, First Core
2 (*) Core Infrastructure Components
3 (*) Slice

16 | P a g e
4 (*) OS Provisioning Components
Enter a component number to toggle ('a' for all, 'n' for none).
When ready, press 'c' to continue, or 'q' to quit.

Selection: c

Wait for the Primary components completed successfully. (It takes 1-1.5 hours.)

7. Make a copy of the OI response file for later upgrade use

#cp /var/tmp/oiresponse.slices_master_typical
/var/tmp/oiresponseFiles/oiresponse.slices_master_typical.C1

Wait for the Primary components completed successfully. (It takes 1-1.5 hours.)

C – Install SAS Upload component

1. Run the upload install script

Run the first time install using the “advanced” option. This will make it go into interview
mode so you can give it all the correct parameters for installation. Use advanced option as
follows:

/ mnt/distributions/silver.0/opsware_40.0.2538.0-
upload/disk001/opsware_installer/install_opsware.sh --advanced

If you have a response file from a previous installation, use it as follows, so it will not go
into interview mode:

/mnt/distributions/oro.0/ opsware_40.0.2538.0-
upload/disk001/opsware_installer/install_opsware.sh –r
/var/tmp/oiresponse.word_uploads

2. Select “1- Simple Interview Mode”

Please select the interview mode. Simple mode uses default values for many of the
configuration parameters. Advanced mode allows you to fully configure the installation.

1 - Simple Interview Mode

2 - Advanced Interview Mode

Please select the interview mode from the menu, type 'h' for help, 'q' to quit: 1

17 | P a g e
 3. Answer the SAS Upload installation OI response parameters

# Parameter Prompt Statement Answer

1 truth.oaPwd Please enter the password for the opsware_admin
opsware_admin user. This is the password
used to connect to the Oracle database.:
2 decrypt_passwd Please enter the password for the crypto
cryptographic material:

3 truth.dcId Please enter the facility ID (number only, default

less than or equal to 999, with no leading
zeros). On the first core, the facility ID
should be 950 or less. [1]:

4 truth.dcNm Please enter the short name of the facility DATACENTER1

where Opsware Installer is being run (no
spaces) [DATACENTER1]:

5 windows_util_loc Please enter the directory that contains the /home/win_util

Microsoft's utilities (Press Control-I for list
of required files) [/tmp]:

6 word.store.path Please enter the absolute path on the NFS Default

server for Software Repository
[/var/opt/opsware/word]:

7 mgw_address Please enter the IP address of the <your_core_IP>

Management Gateway.:
i.e. 16.93.40.220
8 mgw_proxy_port Please enter the port on which this Default
Management Gateway can be contacted to
request connections to core component.
[3003]:

All parameters have values. Do you wish to finish the interview? (y/n): y

Name of response file to write [/usr/tmp/oiresponse.slices_master_typical]: <Default>

Would you like to continue the installation using this response file? (y/n): y

4. Select all components to install

Welcome to the Opsware Installer.
Please select the components to install.

18 | P a g e
1 (*) Software Repository - Content (install once per mesh)
2 (*) OS Provisioning Linux Media Verification (required only for upgrades from pre-7.8
versions)
Enter a component number to toggle ('a' for all, 'n' for none).
When ready, press 'c' to continue, or 'q' to quit.

Selection: c

It takes 1-1.5 hours.

7. Make a copy of the OI response file for later upgrade use

cp /var/tmp/oiresponse.word_uploads
/var/tmp/oiresponseFiles/oiresponse.word_uploads.C1

D- Install SE Connector

 For SA 7.8 base release or 9.0 base release, download SE Connector from HP
Live Network.
 For SA 7.82 and later, and SA 9.01 and later, the SE Connector is
automatically installed on the core.

5 Section IV – Finish SA OCC configuration

Create your SA User

1. Create a SAS OCC Client user
Open Internet explorer browser and browse to the Core OCC Web
http://yourCore.rose.hp.com. For example here, http://lennox.rose.hp.com. Login
with user name as admin; password as opsware_admin.
a) Go to “Administration -> Users & Groups”, click the “New User” button.
b) Fill in the required text fields and save it.

Download/Install the SA Client Launcher

2. Download & install the SA Client software to your work station where you will
perform your test.
a) On the Core OCC Web (See step 1), go to “Home -> Power Tools”.

19 | P a g e
 b) Click the “Download Opsware Launcher”, then download and install the
SAS Launcher.

Login to SA Client

3. Login to the SAS OCC Client with the user that you created in step 1.
You can double-click the HP Server Automation icon to bring the SA OCC Client
up.

At this point, SA has been installed and ready for use.

6 Section V- Troubleshooting/QA

1. Run the SA installation scripts failed

You need to check the system requirement, make sure your core systems meet the
SA installation guide requirements.
Check the install log files for more clues at directory:
# cd /var/log/opsware/install_opsware

1. Cannot bring up the OCC Client after installed the SAS

You need to check the opsware-sas status to see which component failed and try
to restart the opsware-sas to see if the failed components can be restarted.
# /etc/init.d/opsware-sas status
# /etc/init.d/opsware-sas restart

2. The installer exits during FAILURE(S).

a) When you see any FAILURE during the installation, please stop the
installation via say no to the prompted question:
Do you wish to continue with install? (y/n): n

b) Then you need to take care of the FAILURES. The FAILURES could be
missing patches or files.
c) After you take care the FAILURES, then run the uninstall script. The
uninstall script can be found in
/mnt/distributions/silver.0/opsware_37.0.3181.0-
primary/disk001/opsware_installer (For example)
d) Then re-run the installer script to continue the installation.

20 | P a g e