Read-me File for HP Operations DCE Agents on Linux

Revised January 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 an agent on a supported Linux system, make sure that the system meets the following hardware requirements:

Patches and Software Requirements

Important Kernel Features

The following kernel features must be enabled:

CONFIG_NET Networking support
CONFIG_BINFMT_ELF Kernel support for ELF binaries
CONFIG_SYSVIPC System V IPC
CONFIG_INET TCP/IP networking
CONFIG_NETDEVICES Network devices support
CONFIG_EXT2_FS or CONFIG_REISERFS_FS Second extended file system support or Reiser file system support
CONFIG_PROC_FS Proc file system support

General Software Requirements

Use the following command to obtain a list of installed packages and the architecture of those packages:

rpm -qa --qf "%{NAME} %{VERSION} %{RELEASE} %{ARCH}\n "

The following packages must be installed:

The following packages are optional:

Agent Software Directories

HP Operations Manager for the Windows® operating system provides a set of binary files for Linux managed nodes, located in the directory shown below.

%OvShareDir%\Packages\Linux

For example:

C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software\shared\Packages\Linux

Agent Installation Procedure

The agent can be installed on computers running Linux 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 agents installed by OVO for UNIX for more information.

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

  2. Before beginning the uninstall steps, run the command:

    opcagt -kill

  3. Uninstall any existing OVO for UNIX agent software:

    rpm -e OPCSVCDISC OPCPERF OPCJRE OPC OPCCOMM

    rpm -e dce

    NOTE:
    If you are removing a version of the agent earlier than 7.0, use the command:

    rpm -e OPC dce

    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.

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

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

    chmod +x /tmp/opc_inst

    chmod +x /tmp/ovoreqcheckagt

  6. 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 [x64 | x86]

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

  7. Install the agent using the command:

    /tmp/opc_inst

  8. Start the agent with the command:

    /opt/OV/bin/OpC/install/opcactivate -s <management_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 <agent_codeset> to one of the following:

    Language nodeinfo value Agent locale
    Traditional Chinese big5 zh_TW
    Simplified Chinese gb2312 zh_CN
    Japanese - SJIS sjis ja_JP.SJIS
    Japanese - EUC euc ja_JP
    Korean See Others below See Others below
    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.

  9. Add the node to the HPOM console.

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

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