Read-me File for HP Operations DCE Agents on HP-UX

Revised August 2007

Contents

Supported Platforms

Platform support information changes regularly. For up-to-date information, see the support matrix at HP Software Support Online.

Hardware Requirements

Before installing the DCE agent on a supported HP-UX system, make sure that the system meets the following hardware requirements:

Patches and Software Requirements

HP-UX 11.11 Patches

On systems with the HP-UX 11.11 operating system, make sure that the system has the following software:

Important Kernel Parameters

The following table gives values for kernel parameters on HP-UX 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:
The nfile 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.

General Software Requirements

Before installing the DCE agent, be sure the following software is installed on the supported HP-UX 11.x systems that you want to manage.

Agent Software Directories

HPOM for Windows provides sets of binary files for HP-UX managed nodes, located in the directories shown below (one for directory for PA-RISC platforms and the other for Itanium IA64, native 32-bit mode).

Agent Installation Procedure

The DCE agent can be installed on computers running HP-UX 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.

  1. Ensure that you are logged in as a user with appropriate administrative rights.

  2. Uninstall any existing OVO for UNIX agent software:

    swremove ITOAgent

    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.

  3. 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.

  4. Make the opc_inst and ovoreqcheckagt scripts executable with the commands:

    chmod +x /tmp/opc_inst

    chmod +x /tmp/ovoreqcheckagt

  5. 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 [IPF32 | PA-RISC]

    For detailed information about the ovoreqcheckagt tool, refer to the HPOM for Windows online help.

  6. 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.

  7. Start the agent with the command:

    /opt/OV/bin/OpC/install/opcactivate -s <VP_mgt_server> -cs <server_codeset> -cn <agent_codeset> -sv

    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 <server_codeset> to utf8, and set the <agent_codeset> to one of the following:

    Language nodeinfo value Agent locale
    Traditional Chinese big5 zh_TW.big5
    Simplified Chinese gb2312 zh_CH.hp15CN
    Japanese - SJIS sjis ja_JP.SJIS
    Japanese - EUC euc ja_JP.eucJP
    Korean eucKR ko_KR.eucKR
    Central European languages, for example Czech iso88592 cs_CZ.iso88592
    Cyrillic iso88595 ru_RU.iso88595
    Hebrew iso88598 iw_IL.iso88598
    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.

  8. Add the node to the HPOM console.
  9. 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.
  10. 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.