Platform support information changes regularly. For up-to-date information, see the support matrix at HP Software Support Online.
Before installing the DCE agent on a supported HP Tru64 UNIX system, make sure that the system meets the following hardware requirements:
Disk Space - 50 MB (plus 50 MB required temporarily during software installation).
NOTE:
For TruCluster systems, this disk space is required on each
node.
Additional swap space - None
Additional RAM - None
Before installing the DCE agent, be sure the following software is installed on the HP Tru64 UNIX managed node you want to manage.
DCERTS410 DCE Runtime Services v4.1 and DCERTS420 DCE Runtime Services v4.2 are the only valid DCE runtime kits for TruCluster systems. You must configure DCE on each TruCluster member individually.
The following patch must be installed on systems in a TruCluster environment in order for clu_add_member to propagate the agents properly when adding a TruCluster member.
You can download the latest version from the following web pages:
TruCluster 5.1A:
http://www.zk3.dec.com/dupatchwww/v50pats.html
Using the dupatch utility, install patch number:
TCRPAT00024600520 (00246-00)
NOTE:
LCore and the DCE agent cannot coexist on a HP Tru64 UNIX system.
For LCore, /usr/op/OV and /usr/var/opt/OV
are shared directories. All other directories below
/usr/var/opt/OV except for "shared" are CDSLs. For the
DCE agent, /usr/opt/OV and
/usr/var/opt/OV are CDSLs. No coexistence is
possible.
The following table gives values for kernel parameters on HP Tru64 UNIX managed nodes.
| Parameter | Description | Minimum Value |
|---|---|---|
| nfile | Maximum number of open files. | 20 (see note) |
| semmns | Required semaphores. | 20 |
| shmmax | Maximum shared memory. | None required. |
| msgmni | Message queues. | None required. |
| nflocks | File locks. | 10 |
NOTE:
This number 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 one file descriptor. Any
actions that result in processes being started on the managed node
need additional file descriptors.
If monitoring performance metrics with the embedded performance component, and agent runs as non-root user, increase the value of the kernel parameter max_threads_user to:
default + (Number_of_Templates * 2)
Basic Networking Services
OSFCLINET4xx Basic Networking Services
DCE Runtime Kit
| DCE Runtime Kit | HP Tru64 UNIX System | OS Version |
|---|---|---|
| DCERTS 430 DCE | TruCluster or single | V5.1B |
| Runtime Services V4.3 system | ||
NOTE:
HP Operations Manager for the Windows® operating system supports
DCE versions supplied with the HP Tru64 UNIX operating system. DCE
has to be installed separately as an optional product.
For a TruCluster system, you must configure DCE on each TruCluster
member individually.
Japanese Base System
IOSJPBASE4xx Japanese Base System. This system is only for managed nodes running HP Tru64 UNIX in a Japanese environment.
Package: OSFINCLUDE440
OSFINCLUDE440 Standard Header Files package is required for building executables on HP Tru64 UNIX nodes.
Additional Prerequisite Packages
Install the following packages from the Associated Products Volume 1 disk, supplied with your HP Tru64 UNIX operating system.
Where version_id is:
520 for 5.1 A
These files are located at:
<cdrom_mount_point>Worldwide_Language_Support/kit
These files can be installed with the command:
cd
<cdrom_mount_point>/Worldwide_Language_Support/kit \
setld -1 pwd <package>
HPOM for Windows provides binary files for HP Tru64 UNIX managed nodes which are located in the directory shown below:
%OvShareDir%\Packages\Tru64\5.1A
For example:
C:\Documents and Settings\All Users\Application Data\HP\HP
BTO Software\shared\Packages\Tru64\5.1A
NOTE:
Before installing new agents on any HP Tru64 UNIX node, be sure
that old agents are uninstalled from the managed node. Also make
sure that after old agents are uninstalled, neither of the
following directories are present on the managed node:
/usr/opt/OV
/var/opt/OV
The DCE agent can be installed on computers running HP Tru64 UNIX using the procedure below. For TruCluster systems, install the agent software on any one TruCluster member; the agent software is propagated automatically to all the other TruCluster members. After verifying the installation, start the remaining TruCluster members.
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. For
more information, refer to the online help topic Communicate
with nodes installed by OVO for UNIX.
Ensure that you are logged in as a user with appropriate administrative rights.
Uninstall any existing OVO for UNIX agent software:
setld -d OPCAGT000 OPCCOMMAGT000 OPCPERFAGT000
OPCSVCDISCAGT000
NOTE:
If you are removing a version of the agent earlier than 7.0 use the
command:
setld -d OPC000
To find out which version of the agent is installed, check the
value of the parameter OPC_INSTALLED_VERSION in the
/usr/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>\<supported version>\
<supported version> directory exists
only if different versions have different packages.
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 and 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 Alpha. The
ovoreqcheckagt tool checks the prerequisite against
data in the ovoreqcheck.cfg file. By default, this
file is placed in the local directory but you can specify an
alternative location using the -cfg
<config> option. For detailed information about
the ovoreqcheckagt tool, refer to the HPOM for Windows
online help.
Install the agent using the command:
/tmp/opc_inst <arguments>
All arguments passed to the opc_inst command
(except -h) are passed to the opcactivate
command. This command also starts the managed node; for a
TruCluster system, this starts all the TruCluster members.
On TruCluster systems, the agent software is propagated to the other TruCluster members at this time.
If no arguments are passed to the command above, start the agent with the command:
/usr/opt/OV/bin/OpC/install/opcactivate -s
<management_server> -cs <server_codeset>
-cn <agent_codeset> -sv
NOTE:
For TruCluster systems, you must start all TruCluster members
individually.
Add the node to the HPOM console.
For TruCluster systems, create a node group for the TruCluster system on the management server. Add all the TruCluster members to this node group.
To synchronize the package inventory on the management server so that it includes the agent package, right-click the node in the console tree, and then click All Tasks -> Synchronize inventory -> Packages.
For TruCluster systems, synchronize the package inventory for the TruCluster node group, or for each TruCluster member.
Deploy instrumentation to the node.
For TruCluster systems, deploy instrumentation to the TruCluster node group or to each TruCluster member.
For TruCluster systems, deploy policies to the TruCluster node group or to each TruCluster member.
NOTE:
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 the <server_codeset> to utf8 and set the <agent_codeset> to one of the following:
| Language | nodeinfo value | Agent locale |
|---|---|---|
| Traditional Chinese | big5 | zh_HK.big5 |
| Simplified Chinese | See Others below. | See others below. |
| Japanese - SJIS | sjis | ja_JP.SJIS |
| Japanese - EUC | euc | ja_JP |
| Korean | eucKR | ko_KR.eucKR |
| Central European languages, for example Czech | iso88592 | cs_CZ |
| Cyrillic | iso88595 | ru_RU |
| Hebrew | iso88598 | iw_IL |
| 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.
After the assignment and distribution of the policies, verify the installation by executing the shell script:
/usr/opt/OV/bin/OpC/utils/submit.sh
and examining the messages in the message browser.
For TruCluster systems, perform verification for each TruCluster member.
It may be necessary to start TruCluster members that were either down during the installation and were subsequently brought up or were added after the agent software installation. The agent software is propagated automatically to the TruCluster member. Use these steps to start them:
On the managed node (that is, the TruCluster member), run the following command:
/usr/opt/OV/bin/OpC/install/opcactivate -s
<management_server> -cs <server_codeset>
-cn <agent_codeset> -sv
In the HPOM console, add the TruCluster member to the node group for the TruCluster system.
Deploy instrumentation to the node.
For TruCluster systems, you need to deinstall the agents on only one TruCluster member. The agent software is deinstalled on all other TruCluster members automatically. To deinstall the agents, follow these steps:
Stop all HPOM agents running on the managed node.
For TruCluster systems, you need to stop the agents on all TruCluster members.
Deinstall the agent software from the managed nodes by entering:
setld -d OPCAGT000 OPCCOMMAGT000 OPCPERFAGT000
OPCSVCDISCAGT000
© 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.