Operations Agent 12.

04 UNIX/Linux with
EMI Package solution

Installation Guide

EMI
 HPOA 12.04 Install Guide

Document Information
Project Name: OA Packaging Solution Document Version No: 01.00
Prepared By: Wu, Sheng-Feng Document Version Date: 10-Nov 2017
Reviewed By: Review Date:

Version History
Ver. No. Ver. Date Revised By Description Filename

01.00 10/11/2017 Wu, Sheng-Feng Initial Creation HPOA12.04-Unix-Linux-Installation-Guide

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 2 of 22

 HPOA 12.04 Install Guide

Table of Contents
1. Management Summary................................................................................................................................ 4
2. Introduction .................................................................................................................................................. 4
2.1. Document Purpose ............................................................................................................................. 4
2.2. Intended Audience .............................................................................................................................. 4
2.1. Terms and Abbreviations .................................................................................................................... 4
3. General Agent Information .......................................................................................................................... 4
3.1. Limitation of DSI upgrade.................................................................................................................... 4
4. Prerequisites for Node ................................................................................................................................ 4
5. Prerequisites for OMU/L Server ................................................................................................................. 8
6. Package contents ...................................................................................................................................... 10
7. Install, Upgrade and Uninstall Operations Agent 12.04 Manually ........................................................ 10
7.1. Install the Operations Agent 12.04 .................................................................................................... 10
7.2. Upgrade the Operations Agent to 12.04 ........................................................................................... 12
7.3. Uninstall the Operations Agent ......................................................................................................... 13
8. Install, Upgrade and Uninstall Operations Agent 12.04 via HPSA ........................................................ 14
8.1. HPSA Software Policies .................................................................................................................... 14
8.2. Install the Operations Agent 12.04 .................................................................................................... 15
8.3. Upgrade the Operations Agent to 12.04 .......................................................................................... 17
8.4. Uninstall the Operations Agent ........................................................................................................ 18
9. Log Files ..................................................................................................................................................... 18
10. DSIs ............................................................................................................................................................. 18
11. Agent Profiles ............................................................................................................................................. 19
11.1. DEFAULT Profile ............................................................................................................................... 19
11.2. HARD Profile ..................................................................................................................................... 19
12. Custom Pre and Post scripting ................................................................................................................ 20
13. Agent Activation ........................................................................................................................................ 20
14. Disabling rtmd and perfd .......................................................................................................................... 21
15. Timing Estimates ....................................................................................................................................... 21
16. Error Exit Code ........................................................................................................................................... 21

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 3 of 22

 HPOA 12.04 Install Guide

1. Management Summary
This document describes the procedure for installing, upgrading and uninstall the HP Operations Agent 12 also known
as HPOA12 on UNIX/LINUX using the EMI package solution.

2. Introduction

2.1. Document Purpose

The purpose of the document is to provide instructions about how to install the HP Operations Agent 12.04 on
UNIX/LINUX platform.

2.2. Intended Audience

The intended audience is HPE Global Delivery and Operations Bridge teams.

2.1. Terms and Abbreviations

The following terms and abbreviations are used throughout this document.
Abbreviation Description
OMU Operations Manager UNIX
OML Operations Manager LINUX
OMW Operations Manager Windows
OA Operations Agent
PA Performance Agent
HPSA HP Server Automation
DSI Data Source Integration

Table 1: Abbreviations

3. General Agent Information

3.1. Limitation of DSI upgrade

HPOA upgrade (11.x ->12.x) includes the upgrade of the basic DSIs (base package, dsidiskcap, esarinv,
sysdowntime and vgroups). In case there are more DSIs on the server different from the basic ones, HPOA 12 does
not provide upgrade functionality.
To cover non-basic specific DSIs transition/upgrade into HPOA12 style one needs to contact SMATS team to
provide special assistance with upgrades it needs to be solved case by case.

4. Prerequisites for Node

 OS Supported platform has outlined in support matrix
 OA 12.04 adds supports for following operation system:

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 4 of 22

 HPOA 12.04 Install Guide

 Oracle Linux 7.4

 SuSE Linux 12 SP3
 CentOS 7.4
 The following operations systems are no longer supported by OA 12.03 and above:
 HP-UX 11.23 IA64
 Oracle Linux 6.7
 Ubuntu Linux 11.1
 Ubuntu Linux 12.04
 Ubuntu Linux 13.04
 Ubuntu Linux 13.10x
 Windows Server 2003
 All installation procedures must be performed by a user with the root privileges
 The managed node should be able to resolve both the server name & IP address of the Operations Manager
server
 The managed node should be able to contact the Operations Manager server through the TCP port 383
 On the Linux node, if the group id (GID) 777 is already used by another group, then you should create the
opcgrp group (using command 'groupadd opcgrp‟) before install the agent
 Ensure the ip address entry of the loopback interface lo has set properly and ping localhost works
 Disk Space Requirements
 Linux
For new installation
250 MB for the deployment package (/var/tmp)
350 MB for the installation directories (/opt/OV and /opt/perf)
350 MB for the data directories (/var/opt/OV and /var/opt/perf)
For upgrade
250 MB for the deployment package (/var/tmp)
100 MB for the installation directories (/opt/OV and /opt/perf)
350 MB for the data directories (/var/opt/OV and /var/opt/perf)
 HP-UX
For new installation
450 MB for the deployment package (/var/tmp)
830 MB for the installation directories (/opt/OV and /opt/perf)
800 MB for the data directories (/var/opt/OV and /var/opt/perf)
For upgrade
450 MB for the deployment package (/var/tmp)
830 MB for the installation directories (/opt/OV and /opt/perf)
800 MB for the data directories (/var/opt/OV and /var/opt/perf)
 Solaris
For new installation
250 MB for the deployment package (/var/tmp)
350 MB for the installation directories (/opt/OV and /opt/perf)
350 MB for the data directories (/var/opt/OV and /var/opt/perf)
For upgrade
250 MB for the deployment package (/var/tmp)
100 MB for the installation directories (/opt/OV and /opt/perf)
350 MB for the data directories (/var/opt/OV and /var/opt/perf)
 AIX

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 5 of 22

 HPOA 12.04 Install Guide

For new installation

250 MB for the deployment package (/var/tmp)
350 MB for the installation directory (/usr/lpp/OV and /usr/lpp/perf)
350 MB for the data directory (/var/opt/OV and /var/opt/perf)
For upgrade
250 MB for the deployment package (/var/tmp)
350 MB for the installation directory (/usr/lpp/OV and /usr/lpp/perf)
350 MB for the data directory (/var/opt/OV and /var/opt/perf)
 Debian and Ubuntu
For new installation
250 MB for the deployment package (/var/tmp)
350 MB for the installation directory (/opt/OV and /opt/perf)
350 MB for the data directory (/var/opt/OV and /var/opt/perf)
For upgrade
250 MB for the deployment package (/var/tmp)
100 MB for the installation directory (/opt/OV and /opt/perf)
350 MB for the data directory (/var/opt/OV and /var/opt/perf)
Note: If you do not have sufficient space in the installation or data directory, you can symbolically
link the install or data directory to another location on the same system by using the ln -s command.
For example, to symbolically link the /opt/OV directory to the /new directory, run the following
command:
ln -s /new /opt/OV
Note: On UNIX/Linux, at least 20% of the original volume of the /tmp directory must be free while
you install the agent.
 Software requirement
 Linux
On x64 systems:
libstdc++33-32bit-3.3.3-7.8.1.x86_64.rpm and above
Note: Make sure that libstdc++33-32bit-3.3.3-7.8.1.x86_64.rpm is installed before you install
HP Operations agent 11.11 on SLES10 SP4 x64 system. This rpm is applicable only for SUSE Linux
Enterprise Server 10 and later.
C++ runtime:
For systems with kernel version 2.6: /usr/lib/libstdc++.so.5
Only required for Glance - Curses runtime library: /usr/lib/libncurses.so.5
Make sure that the libncurses.so.5 library is present at the following path:
On Linux (64-bit systems)
/usr/lib64/libncurses.so.5 or /lib64/libncurses.so.5
On Linux (32-bit systems)
/usr/lib/libncurses.so.5 or /lib/libncurses.so.5
Make sure that the m4 utility is installed at the path /usr/bin/m4
Set the executable (x) bit for the libvirt library at one of the following paths as appropriate:
/usr/lib64/libvirt.so
/usr/lib64/libvirt.so.0
/usr/lib/libvirt.so
/usr/lib/libvirt.so.0
If these paths contain softlinks, make sure that the library pointed by the link has the executable bit set.
 HP-UX

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 6 of 22

 HPOA 12.04 Install Guide

For HP-UX 11.31. qpkbase package September 2013 (or superseding patch)
For HP-UX 11.23. PHKL_36853, PHCO_38149 (or superseding patch)
For HP-UX 11i v1. PHNE_27063 (or superseding patch)
For HP-UX 11i v1. PHCO_24400 s700_800 11.11 libc cumulative patch (or superseding patch)
For HP-UX 11.11 PA-RISC. PHCO_38226 (or superseding patch)
For HP-UX 11i v1. The following patches are required for the performance tools to function with
VERITAS Volume Manager 3.2:
PHKL_26419 for HP-UX B.11.11 (11.11) (or superseding patch)
PHCO_26420 for HP-UX B.11.11 (11.11) (or superseding patch)
On HP-UX systems running on Itanium, the libunwind library must be available
If multiple processor sets are configured on an HP-UX 11i v1 system and you are using the log
application=prm switch in the parm file to log APP_ metrics by the PRM Group, you must install the
following patch: PHKL_28052 (or superseding patch)
On HP-UX 11i v1 and higher, the performance tools work with Instant Capacity on Demand (iCOD).
The following kernel pstat patch should be installed to correctly report iCOD data (If iCOD is not
installed on your system, do not install the kernel patch.): PHKL_22987 for HP-UX B.11.11 (11.11)
(or superseding patch)
Make sure that the m4 utility is installed at the path /usr/bin/m4
HP GlancePlus, included in this version of the HP Operations agent, works with Process Resource
Manager (PRM) version C.03.02
HP-UX 11.11 and higher running EMC PowerPath v2.1.2 or v3.0.0 must have the latest EMC patches
installed
For the EMC PowerPath v2.1.2 release, use the following patch: EMCpower_patch213
HP.2.1.3_b002 (or superseding patch)
For the EMC PowerPath v3.0.0 release, use the following patch: EMCpower_patch301
HP.3.0.1_b002 (or superseding patch)
To install HPE Operations Agent using the single depot package on HP-UX IA nodes, you must install
the following patch:
qpkbase for HP-UX B.11.31.1309.397 (or superseding patch)
 Solaris
For all supported Solaris versions. Make sure the following packages are available
SUNWlibC
SUNWlibms
Make sure that the m4 utility is installed at the path /usr/xpg4/bin/m4 or/usr/ccs/bin/m4.
 AIX
The libC.a library is required for the HP GlancePlus to function correctly. The library is bundled
within the xlC.rte package, which is available from your AIX Operating System optical media
The bos.perf.libperfstat package is required for the communication daemon
Make sure that the m4 utility is installed at the path /usr/bin/m4.
 Debian and Ubuntu
C++ runtime:
For systems with kernel version 2.6: /usr/lib/libstdc++.so.5
For systems with kernel version 2.6 on Itanium: /lib/libstdc++.so.6
Only required for Glance - Curses runtime library: /usr/lib/libncurses.so.5
Make sure that the m4 utility is installed at the path /usr/bin/m4
Debian libraries:
libgcc 4.7.2 and above

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 7 of 22

 HPOA 12.04 Install Guide

libstdc++6 4.7.2 and above

libc 2.13 and above
libncurses5 5.9 and above
Ubuntu libraries:
libc 2.19 and above
libstdc++6 4.8.2 and above
libgcc 4.8.2 and above
libncurses5 5.9 and above:
 Since customizations are allowed to be made via Custom Attributes in HPSA, a check is made to ensure the
PYTWIST (default) or SPINDICTOR (deprecated in HPSA 9.x) path can be found. The paths checked are:
 /etc/opt/opsware/pytwist/pytwist.conf
 /opt/opsware/agent/pylibs/coglib/spindictor
 /opt/OPSW/blackshadow/coglib/spindictor
If it cannot be located in either of these locations, the installation will default to a no configuration installation
mode.

5. Prerequisites for OMU/L Server

 In order for managed nodes running Operations Agent 12.04 to function properly with OMx 9.x management
servers, the prerequisites below must be met on the management server.
1. Use EMI manual installation package to upgrade the local agent version on OM server to 12.03.
Review the chapter 4 to ensure that the system meets the prerequisites and then follow the steps to
upgrade the agent on the management server.
# ./root_task -upgrade -allow_on_OM
When complete, confirm that the agent version on the management server reflects version 12.03.003
after the upgrade by executing the following
# opcagt -version
12.03.003
2. Register the 12.03 agent packages on OM server
a) Create a configuration file (for example, /tmp/oareg.txt) containing the following text. This
configuration will prevent the Agent 12.03 registration script from also installing the Infrastructure SPI
version 12.x, which can cause problems for solutions (such as virtualization monitoring) that rely on
older versions of the Infrastructure SPI.
[agent.parameter]
REGISTER_AGENT=YES
[hpinfraspi.parameter]
InfraSPI=NO
InfraSPI_With_Reports=NO
InfraSPI_With_Graphs=NO
b) Mount the HPE_OA_12.03.iso ISO file to a directory on the OM server. From that directory, execute
the following command to register the agent with root user:
# ./oainstall.sh -i -m -spiconfig <spi_config_file>
Where <spi_config_file> is the full path to the configuration file created above (e.g. /tmp/oareg.txt).
c) Confirm that the agent packages registered properly by executing the following command and verify
the output
# /opt/OV/bin/OpC/agtinstall/oainstall.sh -inv
Active Versions

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 8 of 22

 HPOA 12.04 Install Guide

===============
AIX :PowerPC(64) :12.03.003
HP-UX :IPF32 :11.11.025
HP-UX :IPF64 :12.03.003
HP-UX :PA-RISC :12.03.003
LIN :PowerPC(2.6) :12.03.003
LIN :x64(2.6) :12.03.003
LIN :x86(2.6) :12.03.003
LIN_DEB :x64 :12.03.003
SOL :SPARC :12.03.003
SOL :x86 :12.03.003
WIN :x64 :12.03.003
WIN :x86 :12.03.003
Active Agent Patches Installed
==============================
OAHPUX_00032 :HP-UX :IPF32 :11.14.014
…….
 Before upgrade of OA for SPI based monitor solutions that the OM server needs to have the fix (SPI data
collection fix. It’s re-packed solution provided by HPSW as fix for data collection issue). Fix is just for SPI
monitoring and will only be deployed to those nodes.
Documentation: https://hpe.sharepoint.com/teams/ps_cdp_event-mgmt/shared/Solution_Portfolio/MGT-
Management_Infrastructure/SPI_DC_FIX
Download URL: http://ecmoml01.omc.hp.com//EMEA-Solution-Repository/MGT-
Management_Infrastructure/SPI_DC_FIX/
Link to the solution in ESL: https://eu-
i.svcs.hp.com/pls/esl/esl_admin_nt_rel.p_modify_ntrel_page?sa_arg=17363
Deployment of SPI Data Collector incompatibility fix for HPOA 12
1. Installation to OML server
a) Copy the latest RPM SPI_DC_FIX-01.00-1.x86_64.rpm from the solution repository linked below to the
/tmp/ directory
http://ecmoml01.omc.hp.com//EMEA-Solution-Repository/MGT-
Management_Infrastructure/SPI_DC_FIX/
b) Launch the rpm command:
rpm -Uvh /tmp/SPI_DC_FIX-01.00-1.x86_64.rpm
2. Installation to OMU server
a) Copy the latest Depot SPI_DC_FIX-<VERSION-HOLDER>-<RELEASE-HOLDER>-OMU9.depot from the
solution repository linked below to the /tmp/ directory
http://ecmoml01.omc.hp.com//EMEA-Solution-Repository/MGT-
Management_Infrastructure/SPI_DC_FIX/
b) Launch the swinstall command:
swinstall -s /tmp/SPI_DC_FIX-<VERSION-HOLDER>-<RELEASE-HOLDER>-OMU9.depot SPI_DC_FIX
3. Installation to managed node
a) Assign policies provided by solution, assignment should always be done via groups. Groups for
assignment directly or via a created A_ group are marked with [*]
Policy groups included in the solution
/ Monitoring-Solutions / MGT-Management_Infrastructure / SPI_DC_FIX
/ Monitoring-Solutions / MGT-Management_Infrastructure / SPI_DC_FIX/S_SPI_DC [*]

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 9 of 22

 HPOA 12.04 Install Guide

/ Monitoring-Solutions / MGT-Management_Infrastructure / SPI_DC_FIX/S_SPI_DC/SPI_DC

Only one policy is included in the solution:
/ Monitoring-Solutions / MGT-Management_Infrastructure / SPI_DC_FIX/S_SPI_DC/SPI_DC /
SPI_DC_Create_Links
It is schedule policy with 5 min execution time interval. It executes built-in Perl script.
Solution does not include instrumentations and does not install any other component.
b) Distribute policies
c) To upgrade the solution install the rpm or depot with a higher version and redistribute policies
Solution has to be assigned and distributed to all nodes with SPIDataCollector category assigned.

6. Package contents
The EMI releases the consolidated OA packages which contain the base product, patches, hotfixes and DSI solution
(see section DSIs).
Release Version Platform Product Patch Hotfix
AIX
HP-UX
12.04-V1 OA 12.04 NA HF_12419
Solaris
Linux

Table 2: Package Contents

All packages and documents can be found in EMI release page below:
https://hpe.sharepoint.com/teams/HPOM_Infrastructure_Solutions/HPOM_Agent/om_pkg_1204/default.aspx

7. Install, Upgrade and Uninstall Operations Agent 12.04 Manually

7.1. Install the Operations Agent 12.04

The following information describes the running package used to install or upgrade an agent manually on a
UNIX/LINUX node with root user.
1. Download the appropriate tar.gz file and put it into /var/tmp folder on your system.
2. Log on to the system with the root privileges and decompress the tar.gz file in /var/tmp folder.
For example:
#cd /var/tmp
#gunzip HPOA_12.04_Linux_86-v1.tar.gz
#tar xf HPOA_12.04_Linux_86-v1.tar
3. Change the directory to HPOA_12 generated in the above step:
#cd HPOA_12
4. Run the root_task script with the appropriate arguments:
#./root_task <install_options>
 Example 1: #./root_task sgdsy202.chn.hp.com
 Example 2: #./root_task -auto
Installation options:
There are 4 main options, one of them is always mandatory:
 <OM_server_name>

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 10 of 22

 HPOA 12.04 Install Guide

For new OA installation (including basic DSIs) and configuration for OM server
-preinstall
For new OA installation (including basic DSIs) without configuration for OM server
 -reinstall
For reinstallation of OA 12.04.006 (including basic DSIs) with the previous OM server
 -reinstall <OM_server_name>
For reinstallation of OA 12.04.006 (including basic DSIs) with the defined OM server
 -auto
For automatic action (HPOA install or upgrade based on detection of installed Operations Agent) with
the previous OM server
 -auto <OM_server_name>
For automatic action (HPOA install or upgrade based on detection of installed Operations Agent) with
the defined OM server
The following optional arguments can be used together with all main installation options:
 -noportcheck
To skip HPOM communication port availability test
 -port=<port>
To specify different HPOM port for port check than the default one 383
 -force
To skip port check and DNS check for supplied OM server name
 -profile=hard
To use more security strict Agent namespace parameters configuration
 -allow_on_OM
To allow OA install script to do any of the above actions on OM management server. If the OM
management server is detected by the OA install script, script execution will be stopped unless
"allow_on_OM" option is specified.
 -srvswitch
To allow OM server change in case different OM server is selected for OA upgrade/auto
upgrade/reinstall. OA upgrade/reinstallation is aborted if different server is used then already
configured in upgraded/reinstalled OA and "srvswitch" option is not used.
HPOA reinstallation
HPOA reinstall is triggered only in case OA 12.04.006 is already installed (i.e. if /opt/OV/bin/opcagt -version
returns 12.04.006). Reinstall does not make anything different when OA 12.04.006 is already successfully
installed. This is due to the native installer behavior where OA components reinstallation is skipped with this note:
INFO: Same version of <.pkg_name.> is already installed - skipping.
Reinstallation makes difference in case:
- Previous OA 12.04.006 is only preinstalled and reinstallation is launched with defined OM server
(In this case OA will not be reinstalled, but configured and activated for a given OM server),
- Previous OA 12.04.006 installation was corrupted/incomplete.
In this case missing/wrong components will be installed due to native package installer behavior, like in this
example:
INFO: Same version of HPOvDepl is already installed - skipping.
INFO: Same version of HPOvConf is already installed - skipping.
INFO: Installing the HPOvPacc package...
INFO: Installing the HPOvPerlA package...
INFO: Same version of HPOvPerfMI is already installed - skipping.
INFO: Same version of HPOvGlanc is already installed - skipping.

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 11 of 22

 HPOA 12.04 Install Guide

The above is not valid for HPOvEaAgt, HPOvOpsAgt components, because if these ones are missing,
/opt/OV/bin/opcagt does not exist and we consider this case as OA was not installed, new OA installation
can be launched in such case.
To verify if the Operations agent 12.04 is installed on the system successfully, follow these steps:
I. Go to the following directory on the node:
 On HP-UX, Linux, or Solaris
/opt/OV/bin
 On AIX
/usr/lpp/OV/bin
II. Run the following command:
#./ovdeploy -inv –includeupdates
The command lists the version of the agent installed on the system.

7.2. Upgrade the Operations Agent to 12.04

You can upgrade an older version of the HPE Operations agent, HP Performance Agent, or HP GlancePlus to the
HPE Operations agent 12.04.
The following versions can be directly upgraded:
 HP Operations Agent 11.xx
 HP Performance Agent 11.xx
 HP GlancePlus: 11.xx
If any agent software older than the specified versions above is installed, does one of the following:
 Upgrade the agent software to the version 11.xx and then upgrade to the HPE Operations Agent 12.04.
This is the preferred method of upgrade. This method ensures necessary packages and policies are
retained on the node
 Remove the agent software completely. This may result in removal of policies and instrumentation files from
the node. After upgrading to the HP Operations agent 12.04, make sure the necessary policies and
instrumentation files are deployed on the node again.
To perform the upgrade procedure:
1. Download the appropriate tar.gz file and put it into /var/tmp folder on your system.
2. Log on to the system with the root privileges and decompress the tar.gz file in /var/tmp folder.
For example:
#cd /var/tmp
#gunzip HPOA_12.04_Linux_86-v1.tar.gz
#tar xf HPOA_12.04_Linux_86-v1.tar
3. Change the directory to HPOA_11 generated in the above step:
#cd HPOA_11
4. Run the root_task script with the appropriate arguments:
#./root_task <install_options>
Example 1: #./root_task -upgrade
Example 2: #./root_task -upgrade <OM_server_name>
Upgrade options:
There are 2 main options, one of them is always mandatory:
 -upgrade
OA upgrade remains unconfigured or configured for previous OM server
 -upgrade <OM_server_name>
OA upgrade is configured for defined OM server

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 12 of 22

 HPOA 12.04 Install Guide

The following optional arguments can be used together with all main installation options:
 -noportcheck
To skip HPOM communication port availability test
 -port=<port>
To specify different HPOM port for port check than the default one 383
 -force
To skip port check and DNS check for supplied OM server name
 -profile=hard
To use more security strict Agent namespace parameters configuration
 -allow_on_OM
To allow OA install script to do any of the above actions on OM management server. If the OM
management server is detected by the OA install script, script execution will be stopped unless
"allow_on_OM" option is specified.
 -srvswitch
To allow OM server change in case different OM server is selected for OA upgrade/auto
upgrade/reinstall. OA upgrade/reinstallation is aborted if different server is used then already configured
in upgraded/reinstalled OA and "srvswitch" option is not used.

7.3. Uninstall the Operations Agent

If it is necessary to remove the agent and the DSIs, take the following procedures:
DSI‟s are removed by running following steps:
 HP-UX:
#cd /opt/osit/ESAR/bin
#./activate.sh -d <dsi_folder_name>
#swremove HPITO-ESAR-HP-dsidiskcap
#swremove HPITO-ESAR-HP-esarinv
#swremove HPITO-ESAR-HP-sysdowntime
#swremove HPITO-ESAR-HP-vgroups
#swremove HPITO-ESAR-HP-base_package
 AIX:
#cd /opt/osit/ESAR/bin
#./activate.sh -d <dsi_folder_name>
#rpm -ev --nodeps HPITO-ESAR-AIX-dsidiskcap-300-0
#rpm -ev --nodeps HPITO-ESAR-AIX-esarinv-300-0
#rpm -ev --nodeps HPITO-ESAR-AIX-sysdowntime-300-0
#rpm -ev --nodeps HPITO-ESAR-AIX-base_package-300-0
 Linux:
#cd /opt/osit/ESAR/bin
#./activate.sh -d <dsi_folder_name>
#rpm -ev --nodeps HPITO-ESAR-LX-dsidiskcap-300-0
#rpm -ev --nodeps HPITO-ESAR-LX-esarinv-300-0
#rpm -ev --nodeps HPITO-ESAR-LX-sysdowntime-300-0
#rpm -ev --nodeps HPITO-ESAR-LX-base_package-300-0
 Solaris:
#cd /opt/osit/ESAR/bin
#./activate.sh -d <dsi_folder_name>

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 13 of 22

 HPOA 12.04 Install Guide

#pkgrm -n -a /etc/opt/osit/ESAR/bin/admin_esar HPITO-ESAR-SOL-DSIDISKCAP

#pkgrm -n -a /etc/opt/osit/ESAR/bin/admin_esar HPITO-ESAR-SOL-ESARINV
#pkgrm -n -a /etc/opt/osit/ESAR/bin/admin_esar HPITO-ESAR-SOL-SYSDOWNT
#pkgrm -n -a /etc/opt/osit/ESAR/bin/admin_esar HPITO-ESAR-SOL-BASE-PACKAGE
To remove agent the following command should be used:
#./oainstall.sh -a -r -clean
The path to oainstall.sh is /usr/lpp/OV/bin/OpC/install on AIX servers and /opt/OV/bin/OpC/install on
Solaris/Linux/HP-UX servers
Alternatively you can download the OA package and run root_task script with -remove option.
#./root_task -remove
It removes the DSIs and agent.

8. Install, Upgrade and Uninstall Operations Agent 12.04 via HPSA

This section describes how to use HPSA to perform the installation, upgrade and uninstall for HP Operations Agent
12.04.

8.1. HPSA Software Policies

 Software Policy Location

 /Unix System Admin/Software Policies/HP
 Software Policy Name
 HP-OA-12.04-v20171108-V1
Support OS: CentOS 5, 6 and 7 (all 32bit and 64 bit)
Oracle Linux 5, 6and 7 (all 32bit and 64 bit)
Redhat Enterprise Linux 5, 6 and 7 (all 32bit and 64 bit)
SuSE Linux Enterprise Server 10, 11 and 12 (all 32bit and 64 bit)
SunOS 10 and 11 (Sparc and Intel)
HP-UX 11.31 (IA-64)
 HP-OA-12.04-v20171108-V1-AIX
Support OS: AIX 6.1, 7.1 and 7.2 (all 64 bit)
 HP-OA-12.04-v20171108-V1-HPUX-PARISC
Support OS: HP-UX 11.11, 11.23 and 11.31(all PA-RISC)
 Packages:
The package(s) contained in the Software Policy’s are as follows:

SW Policy Package
HPOA_12.04-Linux-64_v1.noarch
HPOA_12.04-Linux-86_v1.noarch
HP-OA-12.04-v20171108-V1 HPOA-12-03_SunOS-x86-v1-12.04-v1
HPOA_12.04-SunOS-sparc_v1.noarch
HPOA.A11-12.04.006.01 (HP-UX IA-64)
HP-OA-12.04-v20171108-V1-AIX HPOA_12.04-AIX-64_v1.noarch
HP-OA-12.04-v20171108-V1-HPUX-PARISC HPOA.A11-12.04.006.01 (HP-UX PA-RISC)

Table 3: SW policy and package

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 14 of 22

 HPOA 12.04 Install Guide

As indicated in HP Server Automation Wiki, some of the platforms supported by HPSA product but are not supported
by Enterprise Services and the Unix Capability team. If there is a requirement and business reason for HP ES to
support it, please sent the requests to the regional Midrange Server team/Unix Capability.

8.2. Install the Operations Agent 12.04

The software policy uses rpm for SunOS Sparc, AIX and Linux, pkg for SunOS Intel and depot for HPUX to deliver
the deployment packages. The rpm/pkg/depot provides the Operations Agent installation binaries in
/var/tmp/HPOA. Once Operations Agent has been successfully installed, the software policy will remove all files
and directories in /var/tmp/HPOA.
 Custom Attributes
To pass the ITOPACKAGE input switches, HPSA uses custom attributes and these attributes may be set at the
Facility, Customer or Server level with Server having precedence over Customer and Customer having
precedence over Facility.
Note: Custom Attributes are case sensitive. Always use UPPER case.
There is 2 custom attributes can be used for OA 12.04 policies.
1. ALL_ITO_MGR
The configurable settings for this attribute are the switches listed below. If you want to adjust this setting, it must
be set prior to installation.
Name Value Comments
OMServerName for new OA installation (including basic DSIs) and
configuration for OM server
-preinstall for new OA installation (including basic DSIs) without
configuration for OM server
-auto for automatic action (HPOA install or upgrade based
ALL_ITO_MGR on detection of installed agent), HPOA upgrade
remains unconfigured or configured for previous OM
server
-auto OMServerName for automatic action (HPOA install or upgrade based
on detection of installed agent), HPOA is configured for
defined OM server

Table 4: Customer Attribute

If the OM server name is specified, HPOA installation script checks DNS record for OM server name and OM
communication port availability. If any of these checks fail, installation is aborted.
The following optional switches can be used together with all above installation switches:
 -noportcheck
Use this to skip HPOM communication port availability test
 -port=<port>
Use this to specify different HPOM port for port check than the default one 383
 -force
Use this to skip port check and DNS check for supplied OM server name
 -profile=hard
Use more security strict Agent namespace parameters configuration
 -allow_on_OM

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 15 of 22

 HPOA 12.04 Install Guide

To allow OA install script to do any of the above actions on OM management server. If the OM
management server is detected by the OA install script, script execution will be stopped unless
"allow_on_OM" option is specified.
 -srvswitch
To allow OM server change in case different OM server is selected for OA upgrade/auto
upgrade/reinstall. OA upgrade/reinstallation is aborted if different server is used then already
configured in upgraded/reinstalled OA and "srvswitch" option is not used.
Note: All switches should be put in one line.
Alternatively you can define the management server and certification server in 2 separate lines as below:
Name Value Comments
Definition of management server and
certification server, each on separate line,
management_server_name=test1.hp.com This option is used for full OA installation
ALL_ITO_MGR
certificate_server_name=test2.hp.com and activation to given management and
certification server with all prechecks
(including DNS and port check)

Table 5: Customer Attribute

Note: The above pattern inherits from OA 11.0x and cannot used in conjunction with other installation
switches.
If this custom attribute is not set then a default installation with “-preinstall” option is performed. The default is
to install Operations Agent with no activation. After installation the post installation activation and configuration
is required. Details of this can be found in the “Agent Activation” section.
2. HP_AGENT_COMMANDS
From 11.13 V2 policies, you can set HP_AGENT_COMMANDS to perform post-install HP agent commands
on the system. For example ovconfget or ovconfchg commands. The value section of this custom attribute would
contain the HP agent commands to run. You can list more than one command in the value section. List the
commands on separate lines.
Examples of custom attribute HP_AGENT_COMMANDS values:
/opt/OV/bin/ovconfchg command1
/opt/OV/bin/ovconfchg command2
/opt/OV/bin/OpC/install/opcactivate -srv <OVOSERVER> -cert_srv <OVOSERVER>
/opt/OV/bin/ovconfget >> /var/tmp/HPOA_11_Inst.log, would send agent configuration
information to this policies logfile
 How to Add Custom Attributes in the HPSA Java Client
1. Open the Client and log in to the appropriate core.
2. Go to 'Devices > All Managed Servers'.
3. Double click on the name of the server that you need to set the attributes for to open it in a new (child)
window.
4. Go to the 'Custom Attributes' view in the left navigation pane
5. Update existing values or add new values as needed to build your server:
 To edit an existing value, click on the ellipsis (...) button (at the right side of the value) and
change the value (without blank line after) in the pop-up box.
 To add a new attribute and value, click on the Add button (at the bottom), type in the attribute
name and values.
6. Once complete adding and updating the individual values, save all changes by choosing 'File | Save'
from the Command Bar.

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 16 of 22

 HPOA 12.04 Install Guide

7. Close the server child window by choosing 'File | Close' from the Command Bar.
To install Operations agent 12.04 by using a software policy introduced in section 8.1, please go through the
following steps:
 Attach a software policy to a server which must be in compliance with its attached software policies
or attach a server to a software policy
 Remediate a server against a software policy
After you start the job, the installation procedure begins. At the end of the installation, the agent starts its operation
on the node and all the necessary components start running.
The post-install script will verify the version of the agent installed on the system at the end of the installation
procedure, if it meets the target, the installation will complete with successful, otherwise, a failure will output.
Note: You may see “package HPITO-ESAR-AIX-base_package is not installed” in HPSA remediate output window
when you perform the new installation on AIX server, this message is expected and can be ignored.

8.3. Upgrade the Operations Agent to 12.04

You can upgrade an older version of the HPE Operations agent, HP Performance Agent, or HP GlancePlus to the
HPE Operations agent 12.04.
The following versions can be directly upgraded:
 HP Operations Agent 11.xx
 HP Performance Agent 11.xx
 HP GlancePlus: 11.xx
If any agent software older than the specified versions above is installed, does one of the following:
 Upgrade the agent software to the version 11.xx and then upgrade to the HPE Operations Agent 12.04.
This is the preferred method of upgrade. This method ensures necessary packages and policies are
retained on the node
 Remove the agent software completely. This may result in removal of policies and instrumentation files from
the node. After upgrading to the HP Operations agent 12.04, make sure the necessary policies and
instrumentation files are deployed on the node again.
To perform the upgrade procedure by using a software policy introduced in section 8.1, please go through the
following steps:
 You can specify customer attribute ALL_ITO_MGR for upgrade procedure in a similar way with
installation
Note: Custom Attributes are case sensitive. Always use UPPER case.
Name Value Comments
For OA upgrade from existing agent using the
-upgrade
same OM server
ALL_ITO_MGR
-upgrade NewOMServerName For OA upgrade from existing agent using a
-srvswitch defined OM server

Table 6: Customer Attribute

If the custom attribute ALL_ITO_MGR is not set, then the upgrade procedure will use “-upgrade” switch
as default.
 Attach a software policy to a server which must be in compliance with its attached software policies
or attach a server to a software policy
 Remediate a server against a software policy
After you start the job, the upgrade procedure begins. At the end of the upgrade, the agent starts its operation on
the node and all the necessary components start running.

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 17 of 22

 HPOA 12.04 Install Guide

The post-install script will verify the version of the agent installed on the system at the end of the upgrade procedure,
if it meets the target, the upgrade will complete with successful, otherwise, a failure will output.
Note: After upgrade successfully, please DO NOT detach/remediate any previous version which earlier than
11.05 of Operations Agent policy from the server, this will lead uninstall to the existing Operations Agent.

8.4. Uninstall the Operations Agent

The Operations Agent may be uninstalled through HPSA only if it was installed using this HPSA Software Policy.
To remove the Operations Agent completely by detaching a software policy, go through the following steps:
 Detach the Software Policy from the Managed Server or Device Group
 Remediate the Software Policy to Remove Software
From 11.05, there is ‘version check’ in HPSA uninstall script, the agent software will only be uninstalled when it
passed the version check, that means when you detach/remediate 11.05 policy, it will check the agent version
running on the target server, if the version is 11.05.005, then the both agent software and policy will be removed,
otherwise, only policy itself will be removed from the server.

9. Log Files
Three log files are located in the following directory on the node server:
 /var/tmp/HPOA_12_Inst.log
 /var/tmp/HPOA_12_remove.log
 /var/tmp/HPOA_12_esar_verbose_install.log
 /var/tmp/HPOA_12_script_error.log
You may see stty terminal errors, HOME variable not found errors, etc… This is from the HPSA agent, and
unavoidable. These messages can be ignored.

10. DSIs
As the part of this package solution, the DSIs will be installed, upgraded or removed along with the Operations Agent,
the installation directories are /opt/osit and /var/opt/osit.
HPOA upgrade (11.x ->12.x) includes the upgrade of the basic DSIs (base package, dsidiskcap, esarinv, sysdowntime
and vgroups). In case there are more DSIs on the server different from the basic ones, HPOA 12 does not provide
upgrade functionality.
To cover non-basic specific DSIs transition/upgrade into HPOA12 style one needs to contact SMATS team to provide
special assistance with upgrades it needs to be solved case by case.
The current versions of DSIs in this solution are:
 AIX:
HPITO-ESAR-AIX-base_package-300-0.ppc.rpm
HPITO-ESAR-AIX-dsidiskcap-300-0.ppc.rpm
HPITO-ESAR-AIX-esarinv-300-0.ppc.rpm
HPITO-ESAR-AIX-sysdowntime-300-0.ppc.rpm
 HP-UX:
HPITO-ESAR-HP-base_package-300.depot
HPITO-ESAR-HP-dsidiskcap-300.depot
HPITO-ESAR-HP-esarinv-300.depot
HPITO-ESAR-HP-sysdowntime-300.depot
HPITO-ESAR-HP-vgroups-300.depot

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 18 of 22

 HPOA 12.04 Install Guide

 Linux:
HPITO-ESAR-LX-base_package-300-0.noarch.rpm
HPITO-ESAR-LX-dsidiskcap-300-0.noarch.rpm
HPITO-ESAR-LX-esarinv-300-0.noarch.rpm
HPITO-ESAR-LX-sysdowntime-300-0.noarch.rpm
 SunOS:
HPITO-ESAR-SOL-BASE-PACKAGE-300.pkg
HPITO-ESAR-SOL-DSIDISKCAP-300.pkg
HPITO-ESAR-SOL-ESARINV-300.pkg
HPITO-ESAR-SOL-SYSDOWNT-300.pkg

11. Agent Profiles

The https agent is controlled with settings in various namespace sections. The agent installer reads a pre-defined
profile to set the agent namespace parameters and modify the configuration file during agent installation and upgrade.
Currently there are two profiles DEFAULT and HARD and additional profiles can be added in the future.

11.1. DEFAULT Profile

NameSpace Parameters
NameSpace Parameter Setting
eaagt OPC_INT_MSG_FLT TRUE
eaagt OPC_INT_MSG_FLT_AWS TRUE
eaagt OPC_ADVMON_POLICY_VERSION_CHECK TRUE
conf.cluster MAX_RETRIES_FOR_CLUSTERUP 6
eaagt OPC_AGENT_NAT TRUE
eaagt OPC_RPC_ONLY TRUE
install.config DISABLE_REALTIME TRUE
xpl.locale IGNORE_LOCALE True

Table 7: Default profile

11.2. HARD Profile

Note: The HARD profile is intended to be used for customer that require a hardened agent install. The settings
disable the plain text HTTP responses from TCP port 383 and TCP port 5227 from the perfd process.
To use the HARD profile, the “-profile=hard” switch is required to be supplied, see chapter 6.1 and 7.2
NameSpace Parameters
NameSpace Parameter Setting
eaagt OPC_INT_MSG_FLT TRUE
eaagt OPC_INT_MSG_FLT_AWS TRUE
eaagt OPC_ADVMON_POLICY_VERSION_CHECK TRUE

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 19 of 22

 HPOA 12.04 Install Guide

conf.cluster MAX_RETRIES_FOR_CLUSTERUP 6
eaagt OPC_AGENT_NAT TRUE
eaagt OPC_RPC_ONLY TRUE
bbc.cb LOCAL_INFO_ONLY TRUE
install.config DISABLE_REALTIME TRUE
xpl.locale IGNORE_LOCALE True

Table 8: Hard profile

12. Custom Pre and Post scripting

OA package offers possibility to execute custom pre-install and post-install actions before and after OA
installation/upgrade/remove respectively.
For this purpose you should create 2 files named as
CustomA1installPre
CustomA1installPost
These 2 files must be put in /var/tmp directory prior to the agent installation, upgrade or remove with appropriate
execution rights to be executed by OA install script. The scripts are run, the output captured and logged. On completion
the exit code is read and for successful completion the zero code is expected.
If these files are not present in /var/tmp custom pre- and post-install actions are not executed.

13. Agent Activation

When the Operations Agent has been installed with the -preinstall option, the agent has to be activated at a later date
when the communication to the management server has been established.
 Activation via oasetup
./oasetup.sh -configure -activateonly -force_config_mode -management_server ${mgmt} -certificate_server
${cert}
Example:
./oasetup.sh -configure -activateonly -force_config_mode -management_server ovotest1.sdc.hp.com -
certificate_server ovotest1.sdc.hp.com
The path to oasetup.sh is /usr/lpp/OV/bin/OpC/install on AIX and /opt/OV/bin/OpC/install on other
UNIX/Linux.
 Activation via opcactivate
./opcactivate -srv <OVOSERVER> -cert_srv <OVOSERVER>
Example:
./opcactivate -srv ovotest1.sdc.hp.com -cert_srv ovotest1.sdc.hp.com
The path to opcactivate is /usr/lpp/OV/bin/OpC/install on AIX and /opt/OV/bin/OpC/install on other
UNIX/Linux.

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 20 of 22

 HPOA 12.04 Install Guide

14. Disabling rtmd and perfd

From OA 11.05, 11.11 and above, both rtmd and perfd process will be disabled after agent installation/upgrade
according to the ALM Requirement ID: 15865, if there is any entry to monitor the process RTMD or PERFD in PSMON,
SRVMON, MOM or CIMAVAIL must be removed after agent installation/upgrade.

15. Timing Estimates

Installation Estimate: 20 minutes
Please note in it’s the duration in lab so just a reference, because the duration could vary in different production
environments.

16. Error Exit Code

Code Error Message

10 no argument given to install script

11 invalid argument combination used

13 unknown argument used

14 install script executed with incomplete path

15 invalid content of agent install options file (/var/tmp/ALL_ITO_MGR)

Install option ALL_ITO_MGR specified, but agent parameter file
16
/var/tmp/ALL_ITO_MGR does not exist
20 OM server name/IP address not provided to FQDN/IP lookup check Perl script

21 invalid FQDN for OM server (name does not contain "." character)

22 DNS test failed (no DNS record found for provided FQDN/IP)

23 OM port check failed

31 installation aborted due to OM agent already installed

32 Old agent not configured and no OM server specified. Upgrade aborted

33 Old unsupported version of OVO or OVPA agent detected. Upgrade aborted

34 OA not installed, nothing to upgrade. Upgrade aborted

35 latest version of HPOA detected, installation aborted

OA installation triggered on OM management server, but “allow_on_OM”
36
option not specified, OA installation aborted
40 Problem with OA activation

41 Problem with OA installation

50 HPOA built-in prerequisites check failed

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 21 of 22

 HPOA 12.04 Install Guide

Code Error Message

60 DSI Base package installation failed

62 rpm install tool is not available on Linux, DSI installation aborted

HPOA upgrade/autoupgrade aborted becasue different OM server from existing
70 one is specifid for installation and "srvswitch" option is not used to allow OM
server change
101 readlink command not found in user's path (required only on Linux)

102 egrep command not found in user's path

160 There was a problem retrieving or extracting the installation media

161 Post-install check failed, $OVPATH/bin/OpC/install/opcactivate not found

162 Post-install check failed, $OVPATH/bin/OpC/install/opcagt not found

163 Post-install check failed, the installed version does not meet the expected version

Table 9: Exit Codes

End of document

Effective Date: 10 Nov 2017 Version Number: 1.00 Page 22 of 22