Vous êtes sur la page 1sur 19

OVO Installation

Guide HTTPS Agent on


Unix and Linux
AGDPE Delivery
Implementation
May 14, 2008

AGDPE

OVO Install Guide


HTTPS Agent for Unix

Delivery Implementation

Document Information
Project Name:

OVO HTTPS Agent Installation on Unix

Prepared By:

Document Version No:

Title:

Document Version Date:

Reviewed By:

Review Date:

2.3
May 14, 2008

Version History
Ver. No.

Ver. Date

Revised By

Description

1.0

14-Nov-06

Veno
Gunaratnam

OVO Install; Initial draft

2.0

15-Jan-07

Al MacKie

Extract all customer specific instructions; adjust to


be generic and reflect team standards for names

2.01

16-Jan-07

Al MacKie

Clarify Agent IP Address in NAT environment

2.03

19-Jan-07

Al MacKie

Fix OVO Installation commands

2.1

23-Oct-07

Al MacKie

Update links and kit names

2.2

21-Jan-08

Al MacKie

Update links and add not on deinstallation

2.3

14-May-08

Al MacKie

Update PE links

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Filename

Page 2 of 19

AGDPE
Delivery Implementation

OVO Install Guide


HTTPS Agent for Unix

Table of Contents
1.

2.

Introduction............................................................................................................................................ 5
1.1.

Intended Audience......................................................................................................................... 5

1.2.

Related Documents ....................................................................................................................... 5

1.3.

Terms and Abbreviations ............................................................................................................... 6

OVO HTTPS Agent Installation on a UNIX Managed Node................................................................... 7


2.1.

Interaction between OVO and OVPA Installation Procedures ......................................................... 7

2.2.

Removing Old Versions of OVO and OVPA Agents ....................................................................... 7

2.2.1. Check if OVO Agent Version 7 is installed...................................................................................... 7


2.2.2. Remove an OVO 7 Agent from a Unix/Linux server........................................................................ 8
2.3.

Pre-Requisites............................................................................................................................... 9

2.4.

OVO Agent Installation Instructions.............................................................................................. 11

2.5.

OVO Agent Post-Installation Actions............................................................................................ 17

2.6.

Useful OVO Agent Commands .................................................................................................... 18

2.7.

OVO HTTPS Agent Removal from a UNIX Managed Node .......................................................... 19

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 3 of 19

AGDPE
Delivery Implementation

OVO Install Guide


HTTPS Agent for Unix

Proprietary Notice
The information in this document is subject to change without notice.
Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited
to, the implied warranties of merchantability and fitness for a particular purpose.
Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special,
incidental or consequential damages in connection with the furnishing, performance, or use of this
material.
Restricted Rights Legend
Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in
subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS
252.227-7013 for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer
Software Restricted Rights clause at FAR 52.227-19 for other agencies.
HEWLETT-PACKARD COMPANY
3000 Hanover Street
Palo Alto, California 94304 U.S.A.

Use of this manual and flexible disk(s) or tape cartridge(s) supplied for this pack is restricted to this
product only. Additional copies of the programs may be made for security and back-up purposes only.
Resale of the programs, in their present form or with alterations, is expressly prohibited.
Copyright Notice
Copyright 2006 Hewlett-Packard Company. All rights reserved.
Reproduction, adaptation, or translation of this document without prior written permission is prohibited,
except as allowed under the copyright laws.

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 4 of 19

AGDPE

OVO Install Guide

Delivery Implementation

1.

HTTPS Agent for Unix

Introduction

This installation guide provides generic instructions for the installation of the OVO 8 HTTPS Agent on
Unix and Linux Platforms. It must be used in conjunction with the Customer-specific OVO
Installation Overview and Requirements Documents that will be provided separately by the
Delivery Implementation team.
The Installation Overview and Requirements Documents will provide specific information on the Agent
Kits that are available for installation for a particular customer and the requirements that will help you
decide which Agents to install.
If the target server is a Unix or Linux platform that supports the OVO 8 HTTPS Agent, this document
should be used to perform the installation.
Notes
v The OVO 8 Agent Installation procedure is standard across all versions of Unix and
Linux (unlike the OVO 7 Agent installation, which was very platform specific).
v The OVO 8 Agent Installation kit is not standard. Each platform requires the correct
Agent kit.

v Always install the OVO Agent before installing the OVPA Agent.

1.1.

Intended Audience

O/S Tower resources responsible for OVO Agent Installation on Customer servers.

1.2.

Related Documents

This document should be read in conjunction with the following documents:


Document Title
<Customer> OVO Installation Overview
<Customer> OVO Agent Requirements

Location
Contact Delivery Implementation
team

The generic OVO Agent Installation Guides, including this guide, can be found on the Americas
Monitoring and Configuration Management Sharepoint:
http://teams1.sharepoint.hp.com/teams/MCM/Tools/Forms/AllItems.aspx?RootFolder=%2fteams%2fMCM%2fTools%2fAgent%20Installation%20Guides

Customer-specific Installation Guides will be stored initially on the associated transition sharepoint,
then under the customer section on the Production Support RTP sharepoint after transition.
http://prime.sharepoint.hp.com/teams/agdps/rtp/default.aspx

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 5 of 19

AGDPE
Delivery Implementation

1.3.

OVO Install Guide


HTTPS Agent for Unix

Terms and Abbreviations

The following terms and abbreviations are used throughout this document.
Term
OVO
OVPA

HP Confidential

Description
OpenView Operations
OpenView Performance Agent

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 6 of 19

AGDPE
Delivery Implementation

2.

OVO Install Guide


HTTPS Agent for Unix

OVO HTTPS Agent Installation on a UNIX Managed Node

This section provides instructions on how to install the OpenView Operations (OVO 8) HTTPS Agent
software on supported UNIX systems.

Note - Always install the OVO Agent before installing the OVPA Agent.
2.1.

Interaction between OVO and OVPA Installation Procedures

OVO Version 7.x and earlier use the DCE protocol for communications between the OVO Agent and
the OVO server. The OVO 7.x Agent is now obsolete on all Linux and Unix systems.
OVO Version 8.x uses the HTTPS protocol which provides secure communication between the OVO
Agent and OVO Server. It also significantly reduces the number of ports that must be opened on
firewalls, which simplifies network management and reduces potential network vulnerabilities. The
OVO 8 Agent is used where ever possible.
OVPA will support either DCE or HTTPS but, by default, will use (and always should use) the same
protocol as used by OVO. For that reason, always install OVO before installing OVPA.

2.2.

Removing Old Versions of OVO and OVPA Agents

If an older version of the OVO Agent is already installed on a server, it should be automatically
removed by the OVO 8 Agent Installation procedure. However, we have seen some issues with this
process, so it is recommended to manually uninstall older versions of the Agent (e.g. uninstall OVO 7
Agents before installing OVO 8 Agents. It should not be necessary to manually uninstall an OVO 8.16
Agent prior to installing an OVO 8.17 Agent).
Since the OVO Agent should be installed prior to the OVPA Agent, it is recommended to
remove any old versions of OVPA prior to installing the OVO Agent. Refer to the OVPA
Installation Documentation for information on removing the OVPA Agent.

2.2.1. Check if OVO Agent Version 7 is installed.


Server: (root)> opcagt version
07.33.000

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 7 of 19

AGDPE
Delivery Implementation

OVO Install Guide


HTTPS Agent for Unix

2.2.2. Remove an OVO 7 Agent from a Unix/Linux server


2.2.2.1.

Remove an OVO 7 Agent from HP-UX

Logon to the Target Server as user root or equivalent.


Make sure the Agent is not running
target:/tmp:> opcagt -kill
De-install the OVO Agent by entering:
target:/tmp:> swremove ITOAgent
If errors occur during the de-installation, check the local de-installation logfiles:
/var/adm/sw/swagent.log and /var/adm/sw/swremove.log
2.2.2.2.

Remove an OVO 7 Agent from Solaris

Logon to the Target Server as user root or equivalent.


Make sure the Agent is not running
target:/tmp:> opcagt -kill
De-install the OVO Agent by entering:
target:/tmp:> /usr/sbin/pkgrm OPC OPCCOMM OPCPERF
IF DCE WAS ONLY USED BY OVO, de-install the HPlwdce package by entering:
target:/tmp:> /usr/sbin/pkgrm HPlwdce
2.2.2.3.

Remove an OVO 7 Agent from Linux

Logon to the Target Server as user root or equivalent.


Make sure the Agent is not running
target:/tmp:> opcagt -kill
De-install the OVO Agent by entering:
target:/tmp:> rpm -e OPCPERF OPC OPCCOMM
IF DCE WAS ONLY USED BY OVO, de-install DCE package by entering:
target:/tmp:> rpm -e dce

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 8 of 19

AGDPE
Delivery Implementation

2.3.

OVO Install Guide


HTTPS Agent for Unix

Pre-Requisites

a) The person performing the installation must have Super-user rights, either access to the root
account or equivalent (sudo, pbrun, etc.). Be careful that all commands you execute are executed
as root.
b) Make sure that the server has the necessary file sets and patches installed to support the
HTTPS agent. Refer to the <Customer> OVO Agent Requirement document for the necessary
information. Do not install the OVO 8 HTTPS Agent on a platform that does not support it.
c) Locate the correct OVO HTTPS Agent Installation Kit. NOTE: The OVO 8 HTTPS Agent
Installation Procedure is the same on all Unix platforms, but the Installation Kit is platform
specific.
The Installation Kit name will be in the format:
OVO_Agent_<OS>_<HW>_HTTPS_<Version>.tar
Where:
<OS> = Operating system - HPUX, Solaris, AIX, Linux24, Linux26, etc.
<HW> = Hardware - PA, IA, x86, etc.
<Version> = A.08.xx
Detailed information on the appropriate kits, including OS name and Version will be provided in
the <Customer> OVO Installation Overview document. The latest Agent kit should be available
on the Production Support FTP server:
ftp://naodfs1.atl.hp.com/NAOD/OV%20Agents/OVO%20Agents/OVO%208%20Agent%20-%20Latest%20Kits/

d) Locate the OVO Server-specific OVO HTTPS Agent configuration file. The configuration file name
will (usually) be in the format:
OVO_Agent_HTTPS_<OVO_Server>.cfg
Where:
<OVO_Server> = The name of the PRIMARY OVO Server that will be used to
support the customer
The location and actual name of the file will be used for a specific customer will be provided in the
<Customer> OVO Installation Overview document. Configuration files can usually be found on the
Production Support FTP server:
ftp://naodfs1.atl.hp.com/NAOD/OV%20Agents/OVO%20Agents/OVO%208%20Agent%20-%20Configuration%20Files/
The configuration file contains the Name and Core Id of the OVO Management Server, as well as
other configuration settings that may be required for the customers environment. Usually, the
same configuration file will be used for all HTTPS Agents, but it is possible that variations, which
will be identified in the <Customer> OVO Installation Overview document, will be required for

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 9 of 19

AGDPE
Delivery Implementation

OVO Install Guide


HTTPS Agent for Unix

some Agents (e.g. Agents on a restricted sub-net may have more stringent port requirements or
use proxy servers).
e) The Target Server (i.e. the server where the Agent will be installed) must be able to resolve the
Name and IP address of the OVO Management Servers. In most customer environments, this will
be accomplished with DNS entries, but may require entries in the Hosts table. In either case, it is
the responsibility of the O/S Tower to make the necessary entries for name/address resolution.
f) The Target Server must be able to route network messages to the OVO Management Server. It is
the responsibility of the O/S Tower to work with the Network Tower to determine whether this will
be handled at the Network Router level or via static routes in the Target Servers routing tables.

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 10 of 19

AGDPE
Delivery Implementation

2.4.

OVO Install Guide


HTTPS Agent for Unix

OVO Agent Installation Instructions

Note: All fields enclosed in <> (e.g. <OS>, <Customer>) must be replaced by the real field name (e.g.
<OS> with Solaris or HPUX or ; <Customer> with Acme or )
a) Run netstat -na to verify the Port are not being used by other application (ports 383,382,381)
b) Transfer the OVO Agent Installation Kit and the OVO HTTPS Agent Configuration file for this
customer to the /tmp directory on the target server.
c) Logon to the target server as user root or equivalent.
d) Change directory to /tmp

target:> cd /tmp
e) Use tar to extract the Agent components

target:> tar -xf OVO_Agent_<OS>_<HW>_HTTPS_<Version>.tar


f)

Make sure the OVO Management Server name(s) and IP addresses can be resolved by the target
server. The Management Server names will be provided in the <Customer> OVO Installation
Overview document.

target:> nslookup <ovo_server1>


Name:
<ovo_server1>.omc.hp.com
Address: xx.xx.xx.xx
Aliases: <ovo_server1>

target:> nslookup <ovo_server2>


Name:
<ovo_server2>.omc.hp.com
Address: xx.xx.xx.xx
Aliases: <ovo_server2>
If necessary, add the OVO Management Servers to the Hosts file or DNS Service used by the
Target servers

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 11 of 19

AGDPE
Delivery Implementation

OVO Install Guide


HTTPS Agent for Unix

g) Make sure that the target server can connect to the HTTPS port on both the Primary and
Secondary OVO Servers using telnet.

target:> telnet <ovo_server1> 383


Trying...
Connected to <ovo_server1>.omc.hp.com.
Escape character is '^]'.

^]
telnet> quit
Connection closed.

target:> telnet <ovo_server2> 383


Trying...
Connected to <ovo_server2>.omc.hp.com.
Escape character is '^]'.

^]
telnet> quit
Connection closed.

h) Make sure that the expected (primary) OVO Server Name is found in the OVO HTTPS Agent
configuration file.

target:/tmp:> cat OVO_Agent_HTTPS_<OVO_Server1>.cfg


set
set
set
set

sec.core.auth:MANAGER_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
sec.core.auth:MANAGER=<ovo_server1>.omc.hp.com
sec.cm.client:CERTIFICATE_SERVER=<ovo_server1>.omc.hp.com
bbc.cb.ports:CLIENT_PORT=10000-11000

Normally, all OVO Agents are activated against the Primary OVO Server. In very unusual cases,
you may be asked to activate against the Secondary OVO Server. This will only be done if the
Primary OVO Server is unavailable for an extended period of time. Do not activate the OVO
Agent against a Secondary OVO server unless requested to do so by the Monitoring team.

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 12 of 19

AGDPE
Delivery Implementation

i)

OVO Install Guide


HTTPS Agent for Unix

Change the permissions of the agent installation script to ensure that it can be executed.

target:/tmp:> chmod +x ./opc_inst


j)

Execute the installation script to install the OVO Agent.

target:/tmp:> ./opc_inst
k) If the Target Server has multiple NICs, the following step must be performed. If the Target
Server has a single NIC, this step is optional, but recommended:
o
o

Determine the IP Address of the NIC that will be used to communicate with OVO.
Update the OVO Agent configuration with that correct IP Address:

target:/tmp:> ovconfchg -ns eaagt -set OPC_IP_ADDRESS


x.x.x.x
NOTE:

For the OVO HTTPS Agent, always specify the actual IP address of the NIC. (Do
not specify the NAT IP address that will be seen by the OVO Management Server if
NAT Addressing is used to communicate between customer network and HP).

l) Do not proceed past this step until:


v The Primary OVO Server name and IP address can be resolved.
v You can telnet to port 383 on the Primary OVO Server.
v The configuration file contains the expected OVO Server name.
o Do NOT edit the configuration file to change the OVO server name.
The Manager ID must match the Manager name.

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 13 of 19

AGDPE

OVO Install Guide

Delivery Implementation

HTTPS Agent for Unix

m) Activate the OVO Agent. Specify the Server-specific OVO HTTPS Agent configuration file on the
command line to configure the Agent to communicate with the correct OVO Management Server.
This will generate a Certificate Request to the OVO Server.

target:/tmp:> opcactivate -configure \


OVO_Agent_HTTPS_<OVO_Server1>.cfg
n) Check that the OVO Agent is running.

target:/tmp:> ovc -status


ovcd
OV
ovbbccb OV
ovconfd OV
coda
opcmsga OVO

Control
Communication Broker
Config and Deploy
OV Performance Core
Message Agent

CORE
CORE
COREXT
AGENT,CODA
AGENT,EA

(10270)
(10271)
(10272)
(10308)
(10309)

Running
Running
Running
Running
Running

If the OVO Agent is not running, start it

ovc -start
o) Check the status of Certificates on the server. There will be no certificates listed until the
Management Server grants the Certificate.

target:/tmp:> ovcert -list


+---------------------------------------------------------+
| Keystore Content
|
+---------------------------------------------------------+
| Certificates:
|
+---------------------------------------------------------+
| Trusted Certificates:
|
+---------------------------------------------------------+
p) At this point, contact the Monitoring team to grant the Certificate Request.

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 14 of 19

AGDPE
Delivery Implementation

OVO Install Guide


HTTPS Agent for Unix

q) Once the request is granted by the OVO Management Server, check that the Certificates are
correctly installed.

target:/tmp:> ovcert -check


OvCoreId set
Private key installed
Certificate installed
Certificate valid
Trusted certificates installed
Trusted certificates valid
r)

:
:
:
:
:
:

OK
OK
OK
OK
OK
OK

If the certificate check is not successful, use the following commands to evaluate the issue with
the Delivery Implementation team
Check for errors in the OVO Agent logfile.

target:/tmp:> cat /var/opt/OV/log/System.txt


Check communication between the OVO Agent and the OVO Management server.

target:/tmp:> bbcutil -ping http://<ovo_server1>


http://<ovo_server1>:
status=eServiceOK coreID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
bbcV=05.20.020 appN=ovbbccb appV=05.20.020 conn=1 time=266 ms
Check for a mismatch in the Core ID of the certificates on the OVO Agent.

target:/tmp:> ovcoreid
yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy

target:/tmp:> ovcert -list


+---------------------------------------------------------+
| Keystore Content
|
+---------------------------------------------------------+
|Certificates:
|
|
yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy (*)
|
+---------------------------------------------------------+
| Trusted Certificates:
|
|
CA_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
|
+---------------------------------------------------------+

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 15 of 19

AGDPE

OVO Install Guide

Delivery Implementation

HTTPS Agent for Unix

Verify four items in the output from the above commands.


o
o
o
o

The status of the Bbcutil ping command must be eServiceOK


The OVO Agent Core ID must match the Agent Certificate.
The OVO Agent Certificate must be flagged with (*) to indicate that the private key is
accessible.
The Trusted Certificate must contain the Core Id of the OVO Management Server (from
the Agent Configuration file <Customer>_OVO_Agent_HTTPS.cfg)

s) After the Delivery Implementation team grants the Certificate request, they will distribute Policies
(Templates) and Instrumentation to the Agent. When distribution is complete, you will find that
additional Agent processes are active on the system.

target:/tmp:> ovc -status


ovcd
ovbbccb
ovconfd
coda
opcmsga
opcacta
opcmsgi
opcle
opcmona
t)

OV Control
OV Communication Broker
OV Config and Deploy
OV Performance Core
OVO Message Agent
OVO Action Agent
OVO Message Interceptor
OVO Logfile Encapsulator
OVO Monitor Agent

CORE
CORE
COREXT
AGENT,CODA
AGENT,EA
AGENT,EA
AGENT,EA
AGENT,EA
AGENT,EA

(10270)
(10271)
(10272)
(10308)
(10309)
(10310)
(10311)
(10312)
(10313)

Running
Running
Running
Running
Running
Running
Running
Running
Running

Verify that the OVO Agent can deliver a message to the OVO Management Server:

target:/tmp:> opcmsg application=Enrollment msg_grp=OS


object=Test severity=Normal msg_text=This
server is now being monitored by OVO
The Delivery Implementation team will verify that the event is received in OVO. It should also
produce a test incident in the OVSD pre-production queue identified in the Customer-specific
OVO Installation Overview document.

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 16 of 19

AGDPE
Delivery Implementation

2.5.

OVO Install Guide


HTTPS Agent for Unix

OVO Agent Post-Installation Actions

The O/S Tower is responsible for additional monitoring configuration steps after the Agent kit is
installed.
a) Configure the node-specific monitoring configuration files (e.g. df_mon.cfg, ps_mon.cfg, etc.) to
contain the correct objects and thresholds to be monitored (e.g. file systems, processes, etc.)
b) Refer to the <Customer> OVO Installation Overview document to determine whether Unix Target
Servers for this particular customer will be monitored by the OVO Agent for hardware events using
SNMP traps. If so, it is the responsibility of the OS Tower to configure the hardware console (or
O/S Agent) to deliver these SNMP traps to localhost (127.0.0.1), so that they can be intercepted by
an OVO Agent Trap template.
The Delivery Implementation team will deploy the Trap templates, but configuration of the SNMP
environment on the Target Server (and knowledge of the procedures to do this) is outside the
scope of the Delivery Implementation team.

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 17 of 19

AGDPE
Delivery Implementation

2.6.

OVO Install Guide


HTTPS Agent for Unix

Useful OVO Agent Commands


Agent
Version
Command

ovc
ovc
ovc
ovc

-kill
-stop
-start
-status

opcagt
opcagt
opcagt
opcagt
opcagt
opcagt

-kill
-stop
-start
-cleanstart
-status
-version

ovcert -check
ovcert -list
ovcert -certreq

Y
Y
Y
Y
Y
Y

Y
Y
Y
Y

OVO Agent - complete shutdown


OVO Agent - shutdown sub-agents only
OVO Agent - start
OVO Agent - show status

Y
Y
Y

OVO Agent - complete shutdown


OVO Agent - shutdown sub-agents only
OVO Agent - start
OVO Agent - clear message queues and start
OVO Agent - show status
OVO Agent - show version

Y
Y
Y
Y
Y

ovcoreid -show
bbcutil -ping
https://<ovo_server>
telnet <ovo_server> 383
telnet <ovo_server> 135
telnet <ovo_server> 10000

Description

Y
Y

OV Certificate - check status


OV Certificate - show all certificates
OV Certificate - request a new certificate from the
OVO Server. Note: only to be used when requested
by the Monitoring team.
OV Core Id - show assigned value
Test communications from Agent to OVO Server

Y
Y
opcmsg application=Enrollment msg_grp=OS object=Test severity=Normal
msg_text=This server is now being monitored by OVO

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 18 of 19

AGDPE

OVO Install Guide


HTTPS Agent for Unix

Delivery Implementation

2.7.

OVO HTTPS Agent Removal from a UNIX Managed Node

a) Logon to the Target Server as user root or equivalent.


b) Make sure the Agent is not running

target:/tmp:> ovc -kill


c) De-install the Agent

target:/tmp:> /opt/OV/bin/OpC/install/opc_inst -r

End of document

HP Confidential

Copyright 2008 Hewlett-Packard Development Company, L.P.


Valid agreement required.

Page 19 of 19