Platform support information changes regularly. For up-to-date information, see the support matrix at HP Software Support Online.
Before installing the agent on a supported Solaris system, make sure that the system meets the following hardware requirements:
The following patches are required for Sun Solaris managed nodes. They are available from the www.sunsolve.sun.com web site.
NOTE:
The Sun Microsystems download site may contain more recent patches
than those listed in this document. Patches with higher version
numbers than those listed should be usable, but they have not been
tested with the agent. Note that Sun only allows downloading of
their latest version.
| 109147-09 | SunOS 5.8: Linker patch |
| 108434-03 | SunOS 5.8: Shared library patch for C++ |
| 108827-11 | SunOS 5.8: libthread patch |
If the operating system patches for Sun Solaris are missing, the following problems occur:
Patch Versions
If version -04 or -05 of patch 101327 is installed, the agent installation fails on Sun Solaris managed nodes with the following message:
tar xof...core dump
To solve this problem, do one of the following:
To check which patches are currently installed on Sun Solaris systems, enter:
showrev -p
Multi-processor Patch
Be sure you have the following patches installed. The monitor
agent process (opcmona) may hang on a multi-processor
Solaris managed node if the following patches are not
installed.
For Solaris 8, use the following recommended patches:
108827-11
The following table gives values for kernel parameters on Solaris managed nodes.
| Parameter | Description | Minimum Value |
|---|---|---|
| nfile | Maximum number of open files. | 20 (see note) |
| semmni | Number of semaphore identifiers | 30 |
| semmns | Number of semaphores in system | 200 or greater |
| semmsl | Maximum number of semaphores per ID | 100 |
You can check and change the kernel parameters by editing the
/etc/system file.
NOTE:
The minimum value of 20 for nfile depends on several factors.
Normally a value of 20 per process is sufficient. However, the more
logfiles that are configured for the logfile encapsulator, the more
file descriptors are needed. Normally, one logfile requires about
one file descriptor. Any actions that result in processes being
started on the managed node need additional file descriptors.
Communication Software
HPOM supports the DCE RPC communication type. If none of the supported DCE packages is installed (or running) on the managed node, then the HPlwdce (HP Lightweight DCE runtime version 1.1) is installed and configured during agent installation. The supported DCE packages are listed below:
| OS | DCE |
|---|---|
| Solaris 8 | IBM DCE 3.1, HPlwdce, DASCOM DCE 1.1 |
| Solaris 9 | IBM DCE 3.1, HPlwdce, DASCOM DCE 1.1 |
ARPA/Berkeley Services
MIB
The MIB monitoring functionality of HPOM requires the snmpd provided by HP, or SNMP-based, MIB-I (RFC 1156) or MIB-II (RFC1158) compliant agent software.
HP Operations Manager for the Windows® operating system provides a set of binary files for Solaris managed nodes, located in the directory shown below.
%OvShareDir%\Packages\Solaris
For example:
C:\Documents and Settings\All Users\Application Data\HP\HP
BTO Software\shared\Packages\Solaris
The DCE agent can be installed on computers running Solaris using the procedure below.
NOTE:
If the installed agent is from OVO for UNIX® version 7.0 or
greater, and you only want to receive messages from, and carry out
actions on the managed node (that is, you don't want to deploy
policies on the node), you can achieve this without reinstalling
the agent. See the online help topic Communicate with nodes
installed by OVO for UNIX for more information.
Ensure that you are logged in as a user with appropriate administrative rights.
Stop all agents running on the managed node with the command:
/opt/OV/bin/OpC/opcagt -kill
Uninstall any existing OVO for UNIX agent software:
/usr/sbin/pkgrm OPC OPCCOMM OPCPERF OPCSVCDIS
HPlwdce
NOTE:
If you are installing a newer agent version than one already
installed, uninstalling of the existing agent is optional. If you
uninstall the agent software, all configuration and performance
data are lost. If you prefer, you can upgrade the agent without
first uninstalling the earlier software version. This preserves
configuration and performance data on the node.
NOTE:
If you are removing a version of the agent earlier than 7.0 use the
command:
/usr/sbin/pkgrm HPlwdce OPC
To find out which version of the agent is installed, check the
value of the parameter OPC_INSTALLED_VERSION in the
/opt/OV/bin/OpC/install/opcinfo file on the node.
Copy the files opc_pkg.Z, comm_pkg.Z,
perf_pkg.Z, svcdisc_pkg.Z,
opc_inst, ovoreqcheckagt,
ovoreqcheckagt.awk, and ovoreqcheck.cfg
from the management server to the /tmp directory on
the computer to be managed. These files are located in:
%OvShareDir%\Packages\<supported operating
system>
NOTE:
If you use ftp to copy the files, remember to use binary mode.
Make the opc_inst and ovoreqcheckagt scripts executable with the commands:
chmod +x /tmp/opc_inst
chmod +x /tmp/ovoreqcheckagt
Check to ensure that the managed node meets all hardware and software requirements. Update the node as necessary before continuing.
NOTE:
Prerequisites can be checked automatically with the ovoreqcheckagt
tool, with the command:
/tmp/ovoreqcheckagt -det -agt_comm_type DCE
-agt_bin_format [SPARC | x86]
For detailed information about the ovoreqcheckagt tool, refer to
the HPOM for Windows online help.
Install the agent using the command:
/tmp/opc_inst
NOTE:
If you install a newer agent version over one already installed,
you must stop the agent with the command:
opcagt -kill
before starting the install script opc_inst.
Start the agent with the command:
/opt/OV/bin/OpC/install/opcactivate -s
<VP_mgt_server> -cs <server_codeset> -cn
<agent_codeset> -sv
The server and agent code set on an English system is usually iso88591. For non-English nodes reporting to an HPOM for Windows management server, set <server_codeset> to utf8, and set <agent_codeset> to one of the following:
| Language | nodeinfo value | Agent locale |
|---|---|---|
| Traditional Chinese | big5 | zh_TW.big5 |
| Simplified Chinese | gb2312 | zh |
| Japanese - SJIS | sjis | ja_JP.PCK |
| Japanese - EUC | euc | ja |
| Korean | eucKR | ko |
| Central European languages, for example Czech | iso88592 | cs_CZ.ISO8859-2 |
| Cyrillic | iso88595 | ru_RU |
| Hebrew | iso88598 | he |
| Others | utf8 or ascii | C |
If you use utf8 or ascii as codeset in the nodeinfo file, the data is not converted but is sent "as is" to the management server. Therefore the data must be in a codeset the management server can handle.
An OVO for UNIX management server cannot communicate with a managed node that uses the codeset utf8. If the managed node reports to both an HPOM for Windows and an OVO for UNIX management server, use ascii instead of utf8.
Add the node to the HPOM console.
Deploy instrumentation to the node.
© Copyright 2001-2007 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Microsoft and Windows are U.S. registered trademarks of
Microsoft Corporation.
UNIX is a registered trademark of The Open Group.