Admin Ref v.2

HP OpenView VantagePoint Operations for UNIX Administrator’s Reference

Volume II

Edition 4

Manufacturing Part Number: none (PDF only)

Version A.07.00

July 2003

© Copyright 1996-2003 Hewlett-Packard Development Company, L.P.

Legal Notices 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.

Warranty. A copy of the specific warranty terms applicable to your Hewlett-Packard product can be obtained from your local Sales and Service Office.

Restricted Rights Legend. All rights are reserved. No part of this document may be copied, reproduced, or translated to another language without the prior written consent of Hewlett-Packard Company. The information contained in this material is subject to change without notice.

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 COMPANYUnited States of America

Copyright Notices. ©Copyright 1996-2003 Hewlett-Packard DevelopmentCompany, L.P., all rights reserved.

Reproduction, adaptation, or translation of this material without prior written permission is prohibited, except as allowed under the copyright laws.

2

Trademark Notices.

Adobe is a trademark of Adobe Systems Incorporated.

HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open Group UNIX 95 branded products.

Intel386, Intel80386, Intel486 , and Intel80486 are U.S. trademarks of Intel Corporation.

Intel Itanium Logo: Intel, Intel Inside and Itanium are trademarks or registered trademarks of Intel Corporation in the U.S. and other countries and are used under license.

Java is a U.S. trademark of Sun Microsystems, Inc.

Microsoft is a U.S. registered trademark of Microsoft Corporation.

MS-DOS is a U.S. registered trademark of Microsoft Corporation.

Netscape and Netscape Navigator are U.S. trademarks of Netscape Communications Corporation.

OpenView is a registered U.S. trademark of Hewlett-Packard Company.

Oracle is a registered U.S. trademark of Oracle Corporation, Redwood City, California.

OSF, OSF/1, OSF/Motif, Motif, and Open Software Foundation are trademarks of the Open Software Foundation in the U.S. and other countries.

Pentium is a U.S. registered trademark of Intel Corporation.

SQL*Plus is a registered U.S. trademark of Oracle Corporation, Redwood City, California.

UNIX is a registered trademark of the Open Group.

Windows NT is a U.S. registered trademark of Microsoft Corporation.

Windows and MS Windows are U.S. registered trademarks of Microsoft Corporation.

All other product names are the property of their respective trademark or service mark holders and are hereby acknowledged.

3

4

Contents

1. About AIX Managed NodesIn this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Requirements for NCS RPC on AIX Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . 40Requirements for DCE RPC on AIX Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . 40

Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Methods for Installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Configuring DCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

To Configure a Minimal DCE Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44To Configure a Full DCE Environment (RPC Only) . . . . . . . . . . . . . . . . . . . . . . . . 44To Remove an Existing DCE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Tips for Configuring DCE on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Installing Agents Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Installing Agents Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

To Install the AIX Agent on the Managed Node . . . . . . . . . . . . . . . . . . . . . . . . . . . 46To Activate the AIX Managed Node from the Command Line . . . . . . . . . . . . . . . . 47To Activate the AIX Managed Node from the VPO GUI. . . . . . . . . . . . . . . . . . . . . 49

Installing Agents in HACMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50About VPO Agents in HACMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50About IP Aliases in HACMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Naming Scheme for IP Addresses in HACMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Installation Requirements for AIX HACMP Agents . . . . . . . . . . . . . . . . . . . . . . . . 52To Set an IP Alias for AIX HACMP Agents on AIX . . . . . . . . . . . . . . . . . . . . . . . . 52Fixing Problems with IP Aliases on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53To Reset the IP Alias on the network interface card. . . . . . . . . . . . . . . . . . . . . . . . 54To Reset Events on HACMP 4.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55To Reset Events on HACMP 4.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55To Install AIX HACMP Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58De-installing Agents Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58To De-install VPO Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58To Remove Older Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Types of Preconfigured Template Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

5

Contents

Support for SNMP Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Starting the SMIT User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Distributing Scripts and Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Location of User Scripts and Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64About Temporary Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65About Target Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66About the Default VPO Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67About System Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69About the Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

2. About HP-UX Managed NodesIn this Chapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Hardware Requirements for HP-UX 10.x/11.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Software Requirements for HP-UX 10.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Software Requirements for HP-UX 11.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Methods for Installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Installing Agents with Standard Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Installing Agents with SD-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Installing Agents from a SD-UX Depot Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Creating a SD-UX Depot on a Remote Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Installing Agents from the SD-UX Depot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Enabling SD-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Installing Agents Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83To Install an Agent Manually from the SD-UX Tape Files. . . . . . . . . . . . . . . . . . . 84To Install an Agent Manually from an SD-UX Depot . . . . . . . . . . . . . . . . . . . . . . . 85

Activating the Managed Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86To Activate the Node from the VPO GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86To Activate the Node from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

6

Contents

De-installing Agents Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89To De-install an Agent Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89If Errors Occur During De-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Types of Preconfigured Template Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Types of Default opcmsg Message Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91About SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Types of SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92About VPO Distributed Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92To Configure Basic Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93To Avoid Duplicate Messages in Event Interception. . . . . . . . . . . . . . . . . . . . . . . . 93To Configure Event Interception with ECS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

About Motif SAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95About ASCII SAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Distributing Scripts and Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Location of User Scripts and Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96About Temporary Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97About Target Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Tips for Distributing on HP-UX 10.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100About the Default VPO Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Types of System Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105About the Makefiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Monitoring Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106About EMS Threshold Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Types of Data Returned by the Monitor Executable . . . . . . . . . . . . . . . . . . . . . . . 107Setting up a Threshold Monitor Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Viewing the Resource Hierarchy in the EMS GUI Client . . . . . . . . . . . . . . . . . . . . 109To Start the EMS GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109To View Resource Instances in the EMS GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109To Close the EMS GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Types of EMS Resource Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

7

Contents

Viewing the Resource Hierarchy in the VPO Application Bank . . . . . . . . . . . . . . . 110About the EMS Resources Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Sample Output from the EMS Resources Command . . . . . . . . . . . . . . . . . . . . . . 111Syntax for the EMS Resource Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111If Error Occur with EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Viewing the Resource Hierarchy from the Command Line . . . . . . . . . . . . . . . . . . . 112Sending EMS Notifications to VPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

To Download VPO EMS Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Configuring VPO EMS Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

High Availability Support on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

3. About Linux Managed NodesIn this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Before Installing Agents Remotely. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Installing Agents with Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124To Install an Agent Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124If Errors Occur During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127De-installing Agents Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127To De-install an Agent Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Removing Older Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Preconfigured Template Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128No SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Distributing Scripts and Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Location of User Scripts and Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131About Temporary Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132About Target Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

8

Contents

Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134About the Default VPO Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

About Default VPO Operator Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134About Default VPO Operator Group Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137About the Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

4. About MPE/iX Managed NodesIn this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141


Requirements for the Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Required MPE/iX Patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

About the Management Server Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143About Daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143About the Default VPO Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144About Login and Logout UDCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144About Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144About IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144About Domain Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145About the Logging Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145About VPO Agent Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145About Executable Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145About Time Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146About Spool Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

About Streamed Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Parameters for SYSSTART.PUB.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Excluding Network Commands from SYSSTART.PUB.SYS . . . . . . . . . . . . . . . . 147Starting a Streamed Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147To Set up a Customized Job Stream Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Preparing VPO for a Customized Job Stream Facility . . . . . . . . . . . . . . . . . . . . . 149

Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

9

Contents

Types of Preconfigured Template Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Intercepting Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

About Default Message Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Mapping Messages to VPO Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Mapping NMEV Markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Generating a New NMEV Marker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

No SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Tips for Configuring File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

About “Broadcast” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158About “Disk Space” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159About “Lan Console” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159About “Monitor Console”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159About “Physical Terminal” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159About “Print Status” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159About “Processes” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160About “Virtual Terminal” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160


Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163About the Default VPO Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163About the System Resource File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Mapping ARPA Host Names to NS Node Names . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

About the vt3k Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Problems with ARPA Hostnames and NS Node Names . . . . . . . . . . . . . . . . . . . . 166Avoiding Problems with the VPO Mapping File . . . . . . . . . . . . . . . . . . . . . . . . . . 166Resolving ARPA Hostname to NS Node Names . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168About the Makefiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

10

Contents

5. About Novell NetWare Managed NodesIn this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Software Requirements for the Managed Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Software Requirements for the Depot Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176About the Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179To Install Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Removing Older Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187One Preconfigured Template Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187About SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188No Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

About Novell NetWare Management Agent (NMA) . . . . . . . . . . . . . . . . . . . . . . . 189About the NMA 2.1 Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Monitoring Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191About the NetWare Config Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191About the NetWare Performance Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192About the NetWare Tools Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Types of NetWare Tools Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Types of NMA Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Configuration Distribution and Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Location of User Scripts and Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200About Temporary Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201About Target Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202About the Default VPO Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Types of System Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

About APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Types of APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Examples of VPO-enabled NLMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206


11

Contents

6. About OpenView Performance Agent for HP-UX and Sun SolarisIn this Chapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210About Other Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211What OVPA Does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Integrating Data with OVPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Analyzing Data with OVPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Logging Data with OVPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Customizing OVPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Trying HP OpenView GlancePlus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Hardware Requirements for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Hardware Requirements for Sun Solaris. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Software Requirements for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Software Requirements for Sun Solaris. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Disk Space Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Installing and De-installing OVPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Installing OVPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219To Install OVPA with Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219To Install OVPA Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

De-installing OVPA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221To De-install OVPA with Standard De-installation . . . . . . . . . . . . . . . . . . . . . . . 221To De-install OVPA Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223Types of Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223Types of Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

About the OV Performance Agent Template Group . . . . . . . . . . . . . . . . . . . . . . . 224About the OV Performance Manager Template Group . . . . . . . . . . . . . . . . . . . . . 225

About Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Downloading and Viewing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Types of English-language Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228Types of Japanese-language Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

12

Contents

7. About Sequent DYNIX Managed NodesIn this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233


Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237One Preconfigured Template Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237No SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Distributing Scripts and Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Location of User Scripts and Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239About Temporary Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241About the Default VPO Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242


Types of System Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244About the Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

8. About SGI IRIX Managed NodesIn this Chapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249


Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Removing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

13

Contents

About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253One Preconfigured Template Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

No SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Types of Default Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254






9. About SINIX RM/Reliant Managed NodesIn this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265


Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Configuring DCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

To Configure DCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269To Remove an Existing DCE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270Installing Agents with Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270Installing Agents Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271De-installing Agents with Standard De-installation . . . . . . . . . . . . . . . . . . . . . . 271To De-install an Agent Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271Removing Older Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

14

Contents

One Preconfigured Template Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272No SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273





About the Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

10. About Sun Solaris Managed NodesIn this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283


Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287Problems Caused by Missing OS Patches for Sun Solaris . . . . . . . . . . . . . . . . . . . . 289Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Installing Agents with Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290To Install an Agent Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Activating Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292To Activate a Node from the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292To Activate the Node from the VPO GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294De-installing Agents with Standard De-installation . . . . . . . . . . . . . . . . . . . . . . 294To De-install an Agent Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294Removing Older Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296One Preconfigured Template Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296Types of Default opcmsg Message Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

15

Contents

Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297About SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

Types of SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298About VPO Distributed Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298To Configure Basic Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299To Avoid Duplicate Messages in Event Interception. . . . . . . . . . . . . . . . . . . . . . . 299To Configure Event Interception with ECS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301Types of Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301




Support for Sun Enterprise E10000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310Monitoring and Managing E10000 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310About Software and OS Versions for E10000 Systems. . . . . . . . . . . . . . . . . . . . . . . 311About Preconfigured Elements for E10000 Systems . . . . . . . . . . . . . . . . . . . . . . . . 311

One Preconfigured Template Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311About SNMP Trap Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

About Encapsulated Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313About Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

About SSP Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Configuring the SSP System for E10000 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . 316

To Reconfigure the SSP snmpd Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316To Establish Remote Host Equivalence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317To Export the SSP Logfiles Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Installing the VPO Agent for E100000 Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . 318Before Installing the VPO Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318To Install the VPO Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318Reconfiguring the SSP Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

About the VPO Integration Package for Sun Management Center . . . . . . . . . . . . . . 321High Availability Support on Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

16

Contents

11. About Tru64 UNIX Managed NodesIn this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325


Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328To Configure DCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330Removing an Existing DCE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Installing Agents Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Activating the Managed Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

To Activate the Node from the VPO GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333To Activate the Node from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336De-installing Agents with Standard De-installation . . . . . . . . . . . . . . . . . . . . . . 336To De-install an Agent Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337One Preconfigured Template Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337To Modify a Logfile Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338No SNMP Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339






17

Contents

12. About Windows NT/2000 Managed NodesIn this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351Requirements for the VPO Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . 351Requirements for the Windows Installation Server . . . . . . . . . . . . . . . . . . . . . . . 352Requirements for the Windows Managed Node . . . . . . . . . . . . . . . . . . . . . . . . . . 352

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

About Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355Methods for Installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357About VPO Agent Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

About the “HP ITO account”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358About Alternative Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

Installing Agents through FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361Installing the First Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361Installing Additional Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361To Install an Agent through FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

Installing Agents with Standard Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367Domain Requirements for a Standard Installation. . . . . . . . . . . . . . . . . . . . . . . . 367VPO Requirements for a Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 367FTP Requirements for a Standard Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . 368To Install an Agent with Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 368If an Error Occurs During a Standard Installation . . . . . . . . . . . . . . . . . . . . . . . 372

Re-installing Agents through FTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372Re-installing the First Agent or an Installation Server . . . . . . . . . . . . . . . . . . . . 372Re-installing Additional Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372To Re-install an Agent through FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

Pre-installing Agents Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376When to Pre-install Agents Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376To Pre-install a Windows Agent on a Windows PC. . . . . . . . . . . . . . . . . . . . . . . . 376

De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379De-installing Agents with Standard De-installation . . . . . . . . . . . . . . . . . . . . . . 379To De-install an Agent Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379If Errors Occur During De-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380Types Preconfigured Template Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

18

Contents

About Logfile Templates for Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381About Logfile Templates for Windows NT Terminal Server. . . . . . . . . . . . . . . . . 382

Monitoring Eventlogs on Windows Managed Nodes. . . . . . . . . . . . . . . . . . . . . . . . . 383Syntax for Eventlogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383Viewing Eventlogs in the Message Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384

Types of Default opcmsg Message Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385About SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

Types of SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385About VPO Distributed Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386To Configure Basic Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386To Avoid Duplicate Messages in Event Interception. . . . . . . . . . . . . . . . . . . . . . . 387

Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388Monitoring Windows Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389

To Monitor Windows Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389Syntax for the Windows Performance Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . 389Guidelines for Object and Counter Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390Guidelines for Parent Instance and Instance Values . . . . . . . . . . . . . . . . . . . . . . 391Locating Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392About “Cancel Reboot” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392About “Diagnostics” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393About “Installed Software” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397About “Job Status” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398About “LM Sessions”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399About “Local Users” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400About “Memory Load”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401About “NetBios Sessions” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402About “PerfMon Objs”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403About “Process Kill” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405About “Reboot” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406About “Reg Viewer”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407About “Server Config”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410About “Server Stats” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411About “Shares” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412About “Show Drivers” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413About “Show Services” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414About “Show Users” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416About “Start Services” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

19

Contents

About “Stop Services” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418About “TCP/IP Status” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419About “Used Shares”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420About “Virtual Terminal PC” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421About “VPO Install Log”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422About “Workst Stats” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423



VPO Managed Node Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429About the Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

About Citrix MetaFrame Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430Supported Versions of Citrix MetaFrame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430Software Requirements for Citrix MetaFrame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430Integrating Citrix MetaFrame into VPO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

To Configure the Citrix MetaFrame Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432About the ICA Browser Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432About the Program Neighbourhood Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433Types of MetaFrame Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433Types of MetaFrame Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434

Types of Citrix MetaFrame Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435About “ACL Info”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435About “Auditlog” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435About “Disconnect” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436About “Flush” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436About “License” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436About “Processes” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437About “Send Message” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437About “Servers” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437About “Sessions” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438About “Users” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438

About SMS Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

20

Contents

Supported Versions of SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439Integrating SMS into VPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

To Integrate SMS into VPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440Types of VPO-SMS Monitors for SMS Services. . . . . . . . . . . . . . . . . . . . . . . . . . . 442

Mapping SMS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443Assigning SMS Messages to VPO Message Groups . . . . . . . . . . . . . . . . . . . . . . . 443Assigning SMS Messages to VPO Message Objects . . . . . . . . . . . . . . . . . . . . . . . 444

A. About MC/ServiceGuardIn this Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446What is MC/ServiceGuard? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

Transferring Applications to Other Management Servers. . . . . . . . . . . . . . . . . . . . 447Glossary of MC/ServiceGuard Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

How MC/ServiceGuard Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450Example 1. Switching Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450Example 2. Switching Local Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452Example 3. Redundant Data and Heartbeat Subnets . . . . . . . . . . . . . . . . . . . . . . . 453

Assigning IP Addresses and Hostnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455Assigning IP Addresses to LAN Interface Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . 455Assigning IP Addresses and Hostnames to Packages. . . . . . . . . . . . . . . . . . . . . . . . 455

Running VPO in an MC/ServiceGuard Environment . . . . . . . . . . . . . . . . . . . . . . . . . 456Running NNM on MC/ServiceGuard Cluster Nodes . . . . . . . . . . . . . . . . . . . . . . . . 456Running a VPO Management Server in an MC/ServiceGuard Environment. . . . . 457Running VPO Agents in an MC/ServiceGuard Environment . . . . . . . . . . . . . . . . . 458

Troubleshooting VPO MC/ServiceGuard Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . 459Types of VPO MC/ServiceGuard Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459Enabling Maintenance Mode for VPO MC/ServiceGuard Packages . . . . . . . . . . . . 459

B. Administration of Sun Enterprise ClustersIn this Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462What are Sun Clusters?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463

Purpose of Sun Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463Glossary of Sun Cluster Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464About the Sun Cluster Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465Example of a Failover Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

Running VPO Agents in a Sun Cluster Environment . . . . . . . . . . . . . . . . . . . . . . . . . 468Troubleshooting VPO in a Sun Cluster Environment . . . . . . . . . . . . . . . . . . . . . . . . . 469

About the Data Service Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469About Sun Cluster Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471

21

Contents

C. Administration of VERITAS Cluster ServerIn this Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474VERITAS Cluster Server Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475

Switchover Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476Switchover procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477

Running VPO Agents in a VERITAS Cluster Server Environment . . . . . . . . . . . . . . 481Troubleshooting VPO in a VERITAS Cluster Server Environment . . . . . . . . . . . . . . 482

VPO/VERITAS Cluster Server Logfiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482Preconfigured Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483

Templates and Template Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483Template Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483Monitor Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484

Applications and Application Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485Application Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485VERITAS Cluster Server Cluster Manager application . . . . . . . . . . . . . . . . . . . . 485VERITAS Volume Manager Storage Administrator application . . . . . . . . . . . . . 485

22

Printing HistoryThe printing date and part number of the manual indicate the edition of the manual. The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The part number of the manual will change when extensive changes are made.

Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, you should subscribe to the appropriate product support service. See your HP sales representative for details.

First Edition: September 1999

Second Edition: June 2000

Third Edition: January 2002

Fourth Edition: July 2003

23

24

ConventionsThe following typographical conventions are used in this manual.

Table 1 Typographical Conventions

Font Meaning Example

Italic Book or manual titles, and man page names

Refer to the VPO Administrator’s Reference Volume I and the opc(1M) manpage for more information.

Emphasis You must follow these steps.

Variable that you must supply when entering a command

At the prompt, enter rlogin username.

Parameters to a function The oper_name parameter returns an integer response.

Bold New terms The monitor agent observes...

Computer Text and other items on the computer screen

The following system message appears:

Are you sure you want to remove current group?

Command names Use the grep command ...

Function names Use the opc_connect() function to connect ...

File and directory names /opt/OV/bin/OpC/

Process names Check to see if opcmona is running.

Window/dialog box names In the Add Logfile window ...

Menu name followed by a colon (:) means that you select the menu, then the item. When the item is followed by an arrow (->), a cascading menu follows.

Select Actions: Filtering -> All Active Messages from the menu bar.

25

Computer Bold

Text that you enter At the prompt, enter ls -l

Keycap Keyboard keys Press Return.

[Button] Buttons in the user interface Click [OK].

Table 1 Typographical Conventions

Font Meaning Example

26

VPO Documentation MapHP OpenView VantagePoint Operations (VPO) provides a set of manuals and online help that help you use the product and understand the concepts underlying the product. This section describes what information is available and where you can find it.

NOTE HP OpenView VantagePoint Operations (VPO) has been renamed to HP OpenView Operations (OVO) for UNIX. The name change has not yet been fully implemented across the VPO software and documentation. As a result, you will encounter references to the former product name.

Electronic Versions of the ManualsAll manuals are available as Adobe Portable Document Format (PDF) files in the documentation directory on the VPO product CD-ROM.

With the exception of the VPO Software Release Notes, all manuals are also available in the following VPO web server directory:

http://<management_server>:8880/ITO_DOC/<lang>/manuals/*.pdf

In this URL, <management_server> is the fully qualified hostname of your management server, and <lang> stands for your system language, for example C for English and japanese for Japanese environments.

Alternatively, you can download the manuals from the following website:

http://ovweb.external.hp.com/lpe/doc_serv

27

VPO ManualsThis section provides an overview of the VPO manuals and their contents.

Table 2 VPO Manuals

Manual Description Media

VPO Installation Guide for the Management Server

Designed for administrators who install VPO software on the management server and perform initial configuration.

This manual describes:

• Software and hardware requirements

• Software installation and de-installation instructions

• Configuration defaults

Hardcopy

PDF

VPO Concepts Guide Provides you with an understanding of VPO on two levels. As an operator, you learn about the basic structure of VPO. As an administrator, you gain insight into the setup and configuration of VPO in your own environment.

Hardcopy

PDF

VPO Administrator’s Reference Volume I

Designed for administrator’s who install VPO on the managed nodes and are responsible for VPO administration and troubleshooting. Contains conceptual and general information about the VPO managed nodes.

PDF only

VPO Administrator’s Reference Volume II

Provides platform-specific information about each managed node platform.

PDF only

VPO Reporting and Database Schema

Provides a detailed description of the VPO database tables, as well as examples for generating reports from the VPO database.

PDF only

VPO Entity Relationship Diagrams

Provides you with an overview of the relationships between the tables and the VPO database.

PDF only

HP OpenView VPO Java GUI Operator’s Guide

Provides you with a detailed description of the VPO Java-based operator GUI and VantagePoint Navigator. This manual contains detailed information about general VPO and VantagePoint Navigator concepts and tasks for VPO operators, as well as reference and troubleshooting information.

PDF only

28

VPO Software Release Notes Describes new features and helps you:

• Compare features of the current software with features of previous versions.

• Determine system and software compatibility.

• Solve known problems.

PDF only

VPO Supplementary Guide to MPE/iX Templates

Describes the message source templates that are available for MPE/iX managed nodes. This guide is not available for VPO on Solaris.

PDF only

Managing Your Network with HP OpenView Network Node Manager

Designed for administrators and operators. This manual describes the basic functionality of HP OpenView Network Node Manager, which is an embedded part of VPO.

Hardcopy

PDF

VP Navigator Concepts and Configuration Guide

Provides information for administrators who are responsible for installing, configuring, maintaining, and troubleshooting the HP OpenView VantagePoint Navigator. This manual also contains a high-level overview of the concepts behind service management.

Hardcopy

PDF

Table 2 VPO Manuals


29

Additional VPO-related ProductsThis section provides an overview of the VPO-related manuals and their contents.

Table 3 Additional VPO-related Manuals


HP OpenView VantagePoint Operations for UNIX Developer’s Toolkit

If you purchase the HP OpenView VantagePoint Operations for UNIX Developer’s Toolkit, you receive the full VPO documentation set, as well as the following manuals:

VPO Application Integration Guide

Suggests several ways external applications can be integrated into VPO.

Hardcopy

PDF

VPO Developer’s Reference Provides an overview of all available application programming interfaces (APIs).

Hardcopy

PDF

HP OpenView VantagePoint Advanced Security (VPAS)

If you purchase HP OpenView VantagePoint Advanced Security (VPAS), you receive the following additional documentation.

VPAS Installation and Concepts Guide

Provides information for administrators who are responsible for installing, configuring, maintaining, and troubleshooting VPAS.

Hardcopy

PDF

HP OpenView VantagePoint Operations Integration for Sun Management Center

If you purchase HP OpenView VantagePoint Operations for UNIX Integration for Sun Management Center, you receive the following additional documentation.

VPO Integration for Sun Management Center User’s Guide

Provides information for administrators who are responsible for installing, configuring, maintaining, and troubleshooting the VPO Sun Management Center integration.

PDF only

30

VPO Online InformationThe following information is available online.

HP OpenView Event Correlation Designer for NNM and VPO

If you purchase HP OpenView Event Correlation Designer for NNM and VPO, you receive the following additional documentation.

HP OpenView ECS Configuring Circuits for

NNM and VPO

Explains how to use the ECS Designer product in the NNM and VPO environments.

Hardcopy

PDF

Table 3 Additional VPO-related Manuals


Table 4 VPO Online Information

Online Information Description

HP OpenView VantagePoint Operations Administrator’s Guide to Online Information

Context-sensitive help system contains detailed help for each window of the VPO administrator GUI, as well as step-by-step instructions for performing administrative tasks.

HP OpenView VantagePoint Operations Operator’s Guide to Online Information

Context-sensitive help system contains detailed help for each window of the VPO operator Motif GUI, as well as step-by-step instructions for operator tasks.

HP OpenView VantagePoint Operations Java GUI Online Information

HTML-based help system for the VPO Java-based operator GUI and VantagePoint Navigator. This help system contains detailed information about general VPO and VantagePoint Navigator concepts and tasks for VPO operators, as well as reference and troubleshooting information.

HP OpenView VantagePoint Operations Man Pages

Manual pages available online for VPO. These manual pages are also available in HTML format.

To access these pages, go to the following location (URL) with your web browser:

http://<management_server>:8880/ITO_MAN

In this URL, the variable <management_server> is the fully qualified hostname of your management server.

31

32

About VPO Online HelpThis preface describes online documentation for the HP OpenView VantagePoint Operations (VPO) Motif and Java-based operator graphical user interfaces (GUIs).

Online Help for the Motif GUIOnline information for HP OpenView VantagePoint Operations (VPO) Motif graphical user interface (GUI) consists of two separate volumes, one for operators and one for administrators. In the operator’s volume, you will find the HP OpenView VPO Quick Start describing the main operator windows.

Types of Online Help

The operator and administrator volumes include the following types of online help:

❏ Task Information

Information you need to perform tasks, whether you are an operator or an administrator.

❏ Icon Information

Popup menus and reference information about VPO icons. You access this information with a right-click of your mouse button.

❏ Error Information

Information about errors displayed in the VPO Error Information window. You can access context-sensitive help when an error occurs. Or you can use the number provided in an error message to perform a keyword search within the help system.

❏ Search Utility

Index search utility that takes you directly to topics by name.

❏ Glossary

Glossary of VPO terminology.

33

❏ Help Instructions

Instructions about the online help system itself for new users.

❏ Printing Facility

Printing facility, which enables you to print any or all topics in the help system. (An HP LaserJet printer is required to print graphics.)

To Access Online Help

You can access the help system in any of the following ways:

❏ F1 Key

Press F1 while the cursor is in any active text field or on any active button.

❏ Help Button

Click [Help] in the bottom of any window.

❏ Help Menu

Open the drop-down Help menu from the menu bar.

❏ Right Mouse Click

Click a symbol, then right-click the mouse button to access the Help menu.

You can then select task lists, which are arranged by activity, or window and field lists. You can access any topic in the help volume from every help screen. Hyperlinks provide related information on other help topics.

You can also access context-sensitive help in the Message Browser and Message Source Templates window. After selecting Help: On Context from the menu, the cursor changes into a question mark, which you can then position over the area about which you want help. When you click the mouse button, the appropriate help page is displayed in its help window.

34

Online Help for the Java-based GUIThe online help for the HP OpenView Vantage Point Operations (VPO) Java-based graphical user interface (GUI) helps operators to become familiar with and use the VPO product.

Types of Online Help

The online help for the VPO Java-based GUI includes the following information:

❏ Tasks

Step-by-step instructions.

❏ Concepts

Introduction to the key concepts and features.

❏ References

Detailed information about the product.

❏ Troubleshooting

Solutions to common problems you may encounter while using the product.

❏ Index

Alphabetized list of topics to help you find the information you need quickly and easily.

To View a Topic

To view any topic, open the appropriate folder in the left frame of the online documentation window, then click on the topic title. Hyperlinks provide access to related help topics.

To Access Online Help

To access the help system, select Help: Contents from the menu bar of the Java GUI. A web browser opens and displays the help contents.

NOTE To access online help, you must first configure VPO to use your preferred browser. See the VPO Installation Guide for the Management Server for more information.

35

36

1 About AIX Managed Nodes

Chapter 1 37

About AIX Managed NodesIn this Chapter

In this ChapterThis chapter explains how to install and configure HP OpenView VantagePoint Operations (VPO) on IBM AIX managed nodes.

Chapter 138

About AIX Managed NodesInstallation Requirements

Installation RequirementsThis section explains VPO hardware and software requirements for AIX managed nodes.

Hardware Requirements

Before installing VPO, make sure the AIX managed nodes meet the following hardware requirements:

❏ Disk Space

30 MB (about 60 MB is required during software installation)

❏ Additional Swap Space

None

❏ Additional RAM

None

Software Requirements

Before installing VPO, make sure the following software is installed on AIX managed nodes:

❏ Operating System

For the supported operating system versions, see the VPO Installation Guide for the Management Server.

❏ System Parameters

For a list of kernel parameters, see the VPO Administrator’s Reference Volume I. You can verify and change system parameters with the System Management Interface Tool (SMIT) tool.

❏ Communication Software

VPO supports the NCS RPC and DCE RPC communication types. For details, see “Requirements for NCS RPC on AIX Managed Nodes” on page 40 and “Requirements for DCE RPC on AIX Managed Nodes” on page 40.

Chapter 1 39

About AIX Managed NodesInstallation Requirements

❏ ARPA/Berkeley Services

❏ MIB-I or MIB II

The MIB monitoring functionality of VPO requires SNMP-based, MIB-I (RFC 1156) or MIB-II (RFC 1158) compliant agent software.

Requirements for NCS RPC on AIX Managed Nodes

If you choose NCS RPC as the default communication type, you must install the following software:

❏ NCS Runtime

bos.net.ncs

❏ NCS NCK/NIDL Developer’s Kit

NetLS.NcK_Nidl

You can verify and install NCS with the following commands:

lslpp -l <package>

installp -s <package>

Requirements for DCE RPC on AIX Managed Nodes

If you choose DCE RPC as the default communication type, you must install the following software:

❏ DCE on AIX

DCE is supplied with the AIX operating system up to version 4.3.3. Nevertheless, you must install DCE separately.

❏ Filesets on AIX 4.3

On AIX 4.3 DCE RPC, you must install one of the following filesets:

dce.client.core.rte 2.1

dce.client.rte 2.1

dce.client.core.rte.admin 2.1

Chapter 140

About AIX Managed NodesInstalling and De-installing Agents

Installing and De-installing AgentsThis section describes how to install and de-install AIX managed nodes.

Methods for Installing Agents

After you have configured and set up DCE, you can install the AIX agent automatically or manually:

❏ Automatically

See “Installing Agents Automatically” on page 46.

❏ Manually

See “Installing Agents Manually” on page 46.

Tips for Installing Agents

NOTE For installation tips for AIX managed nodes running HACMP, see “Installing Agents in HACMP” on page 50.

When installing AIX managed nodes, follow these guidelines:

❏ Management Server

The name of the management server must be known to the managed node. That is, the name of the management server must be registered on the name server or in the local host table:

/etc/hosts

You can verify this registration with the nslookup command.

❏ Secure TCP/IP

If securetcpip is enabled, verify that at least rshd or ftpd is available.

Chapter 1 41


❏ Security Limits

Verify that the security limits match your requirements:

/etc/security/limits

The default, root, and opc_op entries are especially important in this regard.

❏ VPO Agent Software

The VPO agent software is installed on the following file tree:

/usr/lpp

If the file system that hosts the file tree is too small to install VPO agents, create a symbolic link before installing VPO.

For example, if /bigdisk is a local file system with enough free space to install the VPO agents, enter the following:

mkdir -p /bigdisk/OV

ln -s /bigdisk/OV /usr/lpp/OV

Or mount a dedicated volume.

For example, enter the following:

mount /dev/hd4 /usr/lpp/OV

In a cluster environment, verify that the local file system is also accessible from all cluster clients, and that it is mounted from all client nodes. For example, the local file system /bigdisk on the cluster client must be mounted to the exported file system /bigdisk on the cluster server.

❏ AIX Diskless Nodes

You may initially create AIX diskless nodes so the root password is not required. You can log into these systems remotely, but you cannot execute commands with remsh because .rhosts is initially not present on the diskless client. Also, you cannot FTP to this type of node because the root password is empty. As a result, you cannot install VPO automatically on a diskless node before you set up the root password or set up the .rhosts file properly.

Chapter 142


NOTE Initially, the /etc/hosts file on the diskless node does not include the VPO management server.

Chapter 1 43


Configuring DCE

You can configure a minimal or full DCE environment.

To Configure a Minimal DCE Environment

A minimal DCE environment does not have DCE cells or a DCE security server.

To configure a minimal DCE environment for the VPO agents, enter the following:

mkdce -o local -n ito rpc

To Configure a Full DCE Environment (RPC Only)

A full DCE environment has DCE cells and a DCE security server.

To configure a full DCE environment for the VPO agents, follow these steps.

1. Open a terminal window on the AIX managed node and enter the following:

smit dce

2. Select Configure DCE/DFS: Configure DCE/DCS Clients -> full configuration for this machine in the SMIT window.

3. Enter the following information in the corresponding text entry fields:

CELL name Enter the name of the cell in which the server was configured (for example, ito).

CLIENTS to configure Use the [List] button to select the clients that you want to configure. The exact client list depends on whether a CDS or DTS server is used.

SECURITY Server Enter the name of the system that is configured as the master security server.

CDS Server Enter the name of the system that is configured as the initial CDS server (if not in the same network).

Cell ADMINISTRATOR’s account Enter the name of the privileged user, specified during the initial configuration of the DCE server (for example, cell_admin).

Chapter 144


LAN profile Enter the name of the LAN (for example, /.../ito/lan-profile).

Client Machine DCE HOSTNAME Enter the hostname of system where configuration is to be performed.

4. Click [OK].

This command configures the managed nodes as DCE clients and starts the DCE daemon dced.

To Remove an Existing DCE Configuration

To remove an existing DCE configuration, use the Unconfigure DCE/DFS option from the SMIT window.

Tips for Configuring DCE on AIX

When installing DCE on AIX managed node, follow these guidelines:

❏ Starting DCED Daemon

Even though the rpcd daemon does not exist on AIX 4.x, the System Management Interface Tool (SMIT) utility erroneously tries to run it in the option Restart RPC Daemons in the local machine.

Start the dced daemon instead, using the script /etc/rc.dce or the SMIT option Restart the DCE/DFS Daemons.

Chapter 1 45


Installing Agents Automatically

To find out how to install the AIX agent automatically, see the VPO Administrator’s Reference Volume I.

If errors occur during the installation, check the local installation logfile:

/tmp/installp.log

Installing Agents Manually

In some situations, you may want to install the AIX agent software without using the management server. If you install the AIX agent software manually, you can prepare the system to become a VPO managed node when it is later connected to the network. This preparation is useful if you are preparing many systems in a central location, or if you want to avoid the root connection over the network that is necessary for a standard agent installation.

To Install the AIX Agent on the Managed Node

To install the VPO AIX agent on an AIX system that will become a VPO managed node, follow these steps:

1. Copy the VPO agent packages and installation script to a temporary directory on the managed node.

On the management server, these are the following files:

• opc_pkg.Z

• comm_pkg.Z

• perf_pkg.Z

• opc_inst

The files are located in the following directory on the management server:

/var/opt/OV/share/databases/OpC/mgd_node/vendor/ibm/\rs6000/aix/A.07.00/RPC_[NCS|DCE_[TCP|UDP]]/

2. Install the Agent.

Start the agent installation script by entering:

/tmp/opc_inst

Chapter 146


To Activate the AIX Managed Node from the Command Line

To activate the agent on the AIX managed node from the command line, follow these steps:

1. Add the pre-installed nodes to the VPO Node Bank window.

Use the menu sequence Actions:Node->Add.

2. Add the node to a VPO node group.

Drag and drop the node onto a node group in the VPO Node Group Bank window.

3. Install the agent on the AIX managed node manually.

For instructions, see “Installing Agents Manually” on page 46.

4. Enter the following:

/usr/lpp/OV/bin/OpC/install/opcactivate -s\ <VPO_mgt_server> -cs <server_codeset> -cn <agent_codeset>

This command activates the agent, which then attempts to send messages to the management server.

• Specifying the -s option with the opcactivate command is optional. This option starts the /opt/OV/bin/OpC/install/upd_res.sh script which integrates the VPO agent into the system startup and shutdown scripts, for example the /etc/init.d file.

• -cs <server_codeset> is the character set for the VPO management server. -cn <agent codeset> is the character set for this agent.

For more information about codesets, see the VPO Administrator’s Reference Volume I and the man page opcactivate(1M).

NOTE Use the opcactivate command with the -mode option to activate hacmp for VPO agents on AIX HACMP systems. For more information about AIX HACMP, see “Installation Requirements for AIX HACMP Agents” on page 52, as well as the man page opcactivate(1m).

Chapter 1 47


5. After the node is connected to the network, enter the following command on the management server:

/opt/OV/bin/OpC/opcsw -installed <node>

This command updates the database and starts heartbeat polling for the node. You must still install the templates, monitors, commands, and actions from the VPO administrator GUI.

Chapter 148


To Activate the AIX Managed Node from the VPO GUI

After you have connected the AIX managed node with the pre-installed agent to the network, you can activate and register the managed node.

To activate the AIX managed node from the VPO GUI, follow these steps:


Use the menu sequence Actions:Node->Add….



3. Distribute the VPO configuration to the node:

a. From the menu bar of the VPO Node Bank window, select Actions:Agents->Install.

The Install /Update VPO Software and Configuration window opens.

b. Select all components and click [OK].

CAUTION Do not check [Force Update]. If you check this option, the management server re-installs the agent.

If the agent is pre-installed on the node, the management server activates the node and installs the selected components.

NOTE If the agent software is not pre-installed, the management server installs the agent.

4. To verify that the Control, Message, and Action Agents are all running on the managed node, enter the following:

/usr/lpp/OV/bin/OpC/opcragt -status <node>

Chapter 1 49


Installing Agents in HACMP

This section includes important information about installing VPO agents on nodes running HACMP.

TIP For general installation tips for AIX managed nodes, see “Tips for Installing Agents” on page 41.

About VPO Agents in HACMP

Each node in an HACMP cluster has its own VPO agent. And each node must be accessible on a fixed IP address, which represents the node in the VPO Node Bank. This IP address is always bound to the same node. As a result, IP addresses that are subject to change cannot be used to install and run a VPO agent running on HACMP system.

About IP Aliases in HACMP

If an additional adapter (that is, a network interface card) with a fixed IP address that is not used by HACMP (as a boot, service, or standby adapter) is available on an HACMP node, you can use this adapter for VPO agent installation. Communication with the VPO server must be possible through this additional adapter. If you use the adapter for VPO installation, you do not need to set up IP aliases or modify shell scripts. Equally important, you can skip all pre-installation tasks. Nevertheless, you may not change the IP address on this adapter.

If no such adapter is available, you should assign each node an IP alias in the same network in which the boot and service IP addresses reside. In addition, you must configure the node in such a way that this IP alias address is assigned to the service adapter as an alias for the boot IP address. Once a fixed IP address or an IP alias is available on a node, that address must be used to install the VPO agent on the node.

After successful installation of the VPO agent, the IP alias is present in the in the field OPC_IP_ADDRESS of the following file:

/var/lpp/OV/conf/OpC/nodeinfo

Chapter 150


Naming Scheme for IP Addresses in HACMP

Using a standard naming scheme in your HACMP environment will help you avoid confusion with the following:

❏ IP Addresses

Other IP addresses that may be set on the interface.

❏ Messages

Messages in the message browser originating from addresses other than the service address of the node.

Use the following naming scheme in your HACMP environment:

<nodename>_boot

Boot address of a node

<nodename>_svc

Service address of a node

<nodename>_stdby

Standby address of a node

<nodename>_ito

IP alias of a node

In this naming scheme, <nodename> is the name of the node as defined in the HACMP configuration.

NOTE The status icon for the node in Node Bank window does not change color immediately if the node in the HACMP cluster goes down. The icon changes color only after VPO has determined that it cannot contact the control agent on that node.

Chapter 1 51


Installation Requirements for AIX HACMP Agents

VPO supports the following software versions for AIX HACMP agents:

❏ AIX 4.3 (for NCS and DCE agents)

❏ HACMP 4.2.2 and 4.3.1

To Set an IP Alias for AIX HACMP Agents on AIX

Before installing AIX HACMP agents, you must set an IP alias used by the VPO agents during and after installation on each node on which you wish to run the VPO agent.

To set an IP alias for AIX HACMP agents on AIX, follow these steps:

1. Use the System Management Interface Tool (smit) menus.

2. In a shell, enter the following command:

smit tcpip

3. Select the following from the menu bar:

Further Configuration -> Network Interface Selection -> Configure Aliases -> Add an IPV4 Network Alias

4. Select the interface you want (for example, en0).

5. Enter values for the IP address and network mask.

Chapter 152


Fixing Problems with IP Aliases on AIX

Once you set the IP alias for VPO agents on AIX, HACMP no longer works correctly. This problem applies to all events that deal with IP addresses (for example, acquire service address, acquire takeover address, swap adapter, and so on). This problem results from a flaw in the AIX operating system.

To fix AIX problems with IP aliases and HACMP, follow these steps:

1. Download and install the appropriate fixes for the AIX operating system.

You can get the fixes with the IBM “FixDist” package or from the IBM website.

NOTE For managed nodes where AIX operating system fixes have already been installed, refer to “To Reset Events on HACMP 4.2.2” on page 55.

To get the fixed versions of related packages, use the following APAR:

IX78397

2. Reset IP aliases on the network interface card.

Once you have installed the fixes to the AIX operating system, all HACMP events work, and the IP alias is set on the interface. However, the IP alias address no longer works after the ifconfig command is used to change the main IP address on the interface. For this reason, you have to reset the IP alias on the interface after each change of the IP address.

For instructions, see “To Reset the IP Alias on the network interface card” on page 54.

NOTE You have to reset the IP alias on all cluster nodes where the VPO agent is to be installed.

Chapter 1 53


To Reset the IP Alias on the network interface card

To reset the IP alias on the interface where the service or boot IP address is set, use the following shell script:

#!/bin/sh# Specify ito alias IP address belowALIAS_IP=”0.0.0.0”SERVICE_IP=`/usr/sbin/cluster/utilities/cllsif -cSi \$LOCALNODENAME | grep “:service:.*:ether” | cut -d: -f7 |\

uniq`BOOT_IP=`/usr/sbin/cluster/utilities/cllsif -cSi \ $LOCALNODENAME |\grep “:boot:.*:ether” | cut -d: -f7 | uniq`

INTERFACE=`/usr/sbin/cluster/utilities/clgetif -a $SERVICE_IP`if [ $? -ne 0 ]; thenINTERFACE=`/usr/sbin/cluster/utilities/clgetif -a

$BOOT_IP`fiif [ “$INTERFACE” != ““ ]; then#IP has changed, set IP alias again on interface with

SERVICE_IP/usr/sbin/ifconfig $INTERFACE $ALIAS_IP alias

fi

The ALIAS_IP variable should contain the same IP address you used to install the VPO agent. If you copy the shell script to other nodes in the cluster, make sure to change the ALIAS_IP variable. The shell script gets service and boot IP addresses for the local node, and sets the IP alias on the interface where either of the two was found.

In addition, you can use the shell script as the post-event script for the following HACMP events:

❏ Acquire service address

❏ Release service address

❏ Swap adapter

Chapter 154


To Reset Events on HACMP 4.2.2

To reset events on HACMP 4.2.2, follow these steps:

1. Use the SMIT screens by entering the following command in a shell:

smit hacmp

2. Select the following:

Cluster Configuration -> Cluster

Resources -> Change/Show Cluster Events

3. Select the appropriate option from the list, and fill in the Post-event Command field.

You can put the shell script in the following directory:

/usr/sbin/cluster/local

To Reset Events on HACMP 4.3.1

To reset events on HACMP 4.3.1, follow these steps:

1. Use the SMIT screens by entering the following command in a shell:

smit hacmp

2. Go into the Cluster Events menu.


Cluster Configuration -> Cluster Resources -> Cluster Events

4. Add the set_alias script to the Known Cluster Events list.


Define Custom Cluster Events -> Add a Custom Cluster Event

6. Set the following:

Cluster Event Name Set to set_alias

Cluster Event Description Set to VPO set_alias

Cluster Event Script Filename Set to /usr/sbin/cluster/local/set_alias

Then click [OK].

Chapter 1 55


7. Assign it to all appropriate events.

Press Cancel to go to the previous level. Then select Change/Show Cluster Events.

8. Select the appropriate option and enter set_alias in the Post-event Command field for each event:

• acquire service address

• release service address

• swap adapter

To Install AIX HACMP Agents

To install AIX HACMP agents, follow the procedure in “To Install the AIX Agent on the Managed Node” on page 46, with the following exceptions:

❏ IP Alias Address

You must use the IP alias address as the IP address for the host on which you want to install the VPO agent.

❏ IP Address

If the IP address used for the VPO installation is tied to the boot, service, or standby interfaces, the installation script issues a warning. The installation continues nonetheless.

❏ VPO Agent Startup

If you select automatic startup for VPO agents, the file /etc/inittab is also updated so the clinit entry remains the last item, as required by HACMP.

❏ NCS Communication Type

If you want to use the NCS communication type, you must start the llbd and VPO agents at boot time, when boot IP address is still available. First start the llbd process, and then the VPO agent, using the appropriate order in the file /etc/inittab. If agent is to be restarted, RPC registration will fail, due to a flaw in llbd.

Chapter 156


❏ Node Information

After you have successfully installed the VPO agent, the IP alias appears in the OPC_IP_ADDRESS field of the following file:

/var/lpp/OV/conf/OpC/nodeinfo

❏ Hostname

The following line is added to the opcinfo file during the installation process:

OPC_NAMESRV_LOCAL_NAME <hostname>

In this instance, <hostname> is the name of the host configured with the IP address you used to install the VPO agent. If this IP address changes, change this line of the opcinfo file accordingly.

You must include this line in the opcinfo file to ensure that the IP address is the same for VPO and ANS (the VPAS Advanced Network Security extension). Using the same IP address for VPO and VPAS ensures that the same hostname is used by all security functions that require <hostname> as their argument (for example, secret key generation).

If <hostname> is not present, VPAS functions retrieve the hostname from the RPC runtime, which is often different from the hostname used for VPO installation. As a result, the VPAS functions will fail.

NOTE From time to time, warnings appear in the following file:

/var/lpp/OV/log/OpC/opcerror

For example:

WARNING opcmsga (Message Agent)(8028) [genmsga.c:535]:Communication failure to message receiver: Connectionrequest rejected (dce/rpc).Buffering messages.(OpC30-3)

You can safely ignore these warnings. Messages are not lost. They are sent to the VPO server after communication is re-established. This process usually takes no more than a few seconds.

Chapter 1 57


De-installing Agents

This section describes how to de-install AIX managed nodes.

De-installing Agents Automatically

For general de-installation instructions, see the VPO Administrator’s Reference Volume I. There is no special de-installation logfile available for AIX managed nodes.

To De-install VPO Manually

To manually de-install VPO software from AIX managed nodes, following these steps:

1. Stop all VPO agents running on the managed node.

2. To de-install the VPO agent software from AIX managed nodes, enter the following:

installp -ug OPC OPCCOMM OPCPERF

NOTE If you are de-installing an older version of the agent, use:installp -ug OPC.

To Remove Older Agents

If you no longer need older VPO agent packages, and if the agent packages are not installed on any managed node, you can remove them.

To remove older VPO agent software, enter the following:

/opt/OV/bin/OpC/install/rm_opc.sh ibm/rs6000/aix \ <VPO_version>

In this command, <VPO_version> is the version of VPO that supports this agent platform (for example, A.07.00).

Chapter 158

About AIX Managed NodesAbout Preconfigured Elements

About Preconfigured ElementsThis section describes preconfigured templates, template groups, and applications used by VPO on AIX managed nodes.

Types of Preconfigured Template Groups

VPO uses the following preconfigured template groups:

❏ AIX

AIX default templates

❏ AIX with HACMP

AIX agents running HACMP

Types of Default Logfile Templates

VPO uses default logfile template on the following managed nodes:

❏ AIX

❏ AIX HACMP

Chapter 1 59


Table 1-1 shows encapsulated logfiles and associated template used on AIX managed nodes.

Table 1-2 shows encapsulated logfiles and associated templates used on AIX HACMP managed nodes.

Table 1-1 Encapsulated Logfiles on AIX Managed Nodes

Logfile Description Template Name

/var/adm/aix_sulog Switch user logfile Su (AIX)

/var/adm/audit log Auditing information logfile Audit Log (AIX)

/tmp/syslog a Syslog daemon logfile Syslog (AIX)

/etc/security/failedlogin (binary format)

History of AIX failed logins Bad logs (AIX)

/var/adm/wtmp (binary format)

History of logins, logouts, and data changes

Logins (AIX)

/var/adm/ras/errors (binary format)

Messages generated by the AIX kernel

Kernel Logs (AIX)

a. To determine or to set the actual syslog logfile name and the events to be logged, see /etc/syslog.conf.

Table 1-2 Encapsulated Logfiles on AIX HACMP Managed Nodes


/var/adm/cluster.log HACMP cluster logs HACMP logfile (AIX)

Chapter 160


Support for SNMP Event Interception

VPO supports the SNMP event interceptor on the following version of AIX:

❏ AIX 4.3 (direct port access mode)

NOTE Local event interception is supported only with Network Node Manager (NNM) version 6.2.

Chapter 1 61


Types of Default Monitored Objects

Table 1-3 describes the default monitored objects used by VPO on AIX managed nodes.

NOTE No default template for monitoring CPU usage is available for AIX managed nodes.

Types of Default Applications

For a list of default applications available for UNIX managed nodes, see the VPO Administrator’s Reference Volume I.

Table 1-3 Object Thresholds on the Managed Nodes

Object Description Threshold Polling Interval (Minutes)

disk_util Monitors disk space utilization on the root disk

90% 10

Inetd Number of executing instances of inetd (Internet Daemon)

0.5 5

MailQueue Length

Length of the sendmail queue: number of unsent mail messages

30 2

proc_util Monitors process table utilization 75% 5

sendmail Number of executing instances of sendmail

0.5 5

swap_util Monitors SWAP utilization 80% 5

Syslogd Checks whether syslogd is running 0.5 5

Chapter 162


Starting the SMIT User Interface

You can use VPO to start the System Management Interface Tool (SMIT) user interface on AIX systems:

Command issued: smit

Default user: root

Default password: None required. The application is started through the VPO action agent.

NOTE If the default user has been changed by the operator, you must supply a password.

Chapter 1 63

About AIX Managed NodesDistributing Scripts and Programs

Distributing Scripts and ProgramsFor AIX managed nodes, the platform selector and architecture identifier is the following:

ibm/rs6000/aix

Location of User Scripts and Programs

Table 1-4 shows the location of user scripts and programs provided on the management server.

Table 1-4 Location of User Scripts and Programs on the Management Server

Script/Program Location

Automatic actions, operator-initiated actions, and scheduled actions

/var/opt/OV/share/databases/OpC/mgd_node/customer\/ibm/rs6000/aix/actions/*

Monitoring scripts and programs used by the monitoring agent and logfile encapsulator

/var/opt/OV/share/databases/OpC/mgd_node/customer\/ibm/rs6000/aix/monitor/*

Scripts and programs called through command broadcast or started from the Application Desktop

/var/opt/OV/share/databases/OpC/mgd_node/customer\/ibm/rs6000/aix/cmds/*

Chapter 164

About AIX Managed NodesDistributing Scripts and Programs

About Temporary Directories

Table 1-5 shows the temporary directories for distributed scripts and programs on the managed nodes.

About Target Directories

Table 1-6 shows the target directories for distributed scripts and programs on the managed nodes.

Table 1-5 Temporary Directories for Distributed Scripts and Programs on the Managed Nodes

Managed Node Operating System

Temporary Directory

IBM RS/6000, Bull DPX/20

AIX /var/lpp/OV/tmp/OpC/bin/actions/var/lpp/OV/tmp/OpC/bin/cmds/var/lpp/OV/tmp/OpC/bin/monitor

Table 1-6 Target Directories for Distributed Scripts and Programs on the Managed Nodes

Managed Node

Operating System

Target Directory Access Rights

IBM RS/6000, Bull DPX/20

AIX /var/lpp/OV/OpC/actions rwxr-xr-x (owner: root)

/var/lpp/OV/OpC/cmds rwxr-xr-x (owner: root)

/var/lpp/OV/OpC/monitor rwxr-xr-x(owner: root)

Chapter 1 65

About AIX Managed NodesOrganization of Managed Nodes

Organization of Managed Nodes Figure 1-1 shows how VPO software is organized on AIX managed nodes.

Figure 1-1 VPO Software on AIX Managed Nodes

Location of Files

On AIX managed nodes, files are located as follows:

❏ Process-related Files

/var/lpp/OV/tmp/OpC

❏ Agent Configuration Files

/var/lpp/OV/conf/OpC

/usr/lpp/

OpC

install

libnls

<lang>

include

/usr/lpp/OpC and /lpp/OpC are used by the installp utility for software maintenance

and

utils

B

monitor cmds actions

Key:

OV contrib

OpC

conf tmp log

OpC OpC OpC

bin conf

/var/lpp/OV

B

B

bin

OpC

databases

BBC

Chapter 166

About AIX Managed NodesOrganization of Managed Nodes

About the Default VPO Operator

The default VPO operator, opc_op, owns /home/opc_op as home directory. By default, the operators use the Korn Shell (/bin/ksh) and are not allowed to log into the system directly (that is, enter * in /etc/passwd).

If the managed node is a Network Information Service (NIS or NIS+) client, you must add the VPO default operator opc_op on the NIS server before installing the VPO software on a managed node. This ensures that the VPO default operator opc_op is used by VPO and is consistent on all systems.

About System Resources

VPO applies changes in the following system resource files:

/etc/passwd/etc/security/passwd Default VPO operator.

/etc/group/etc/security/group Default VPO operator group.

/etc/inittab VPO agent startup. Used only if the Automatic Update of System Resource Files option has been set.

/etc/rc.opc VPO startup. Called by /etc/inittab.

NOTE If you are working with Network Information Services (NIS or “yellow pages”) you should adapt the user registration accordingly.

Chapter 1 67

About AIX Managed NodesTypes of Libraries

Types of Libraries Table 1-7 describes the managed node libraries for VPO A.05.xx, A.06.xx, and A.07.xx.

Table 1-7 Libraries for the VPO Managed Nodes

Item VPO A.05.xx VPO A.06.xx VPO A.07.xx

DCE Library libopc_r.a libopc_r.a libopc_r.a

Libraries linked to the VPO library.

/usr/lpp/OV/lib/libnsp.a

/usr/lib/libdce.a

/usr/lib/libiconv.a


/usr/lpp/OV/lib/libopcas.a

/usr/lib/libdce.a

/usr/lib/libiconv.a



/usr/lib/libdce.a

/usr/lib/libiconv.a

/usr/lib/libdl.a

/usr/lib/libc.a or /usr/ccs/lib/libc.a

/usr/lib/libdcelibc_r.a

/usr/lib/libdcepthreads.a

/usr/lib/libpthreads_compat.a

Link and compile options

-D_CMA_NOWRAPPERS_

-lopc_r -lpthreads -lc_r

-D_CMA_NOWRAPPERS_-lopc_r -lpthreads -lc_r

-D_CMA_NOWRAPPERS_-lopc_r -lpthreads -lc_r

Description Version 3.2 is obsolete with VPO A.05.x.

Note: Only VPO A.04.xx integrations built on AIX 4.x with above options can be run on VPO A.05.xx.

N/A N/A

Chapter 168


About the Include File

On IBM RS600 or Bull DPX/20 with AIX, the managed nodes use the following include file:

/usr/lpp/OV/include/opcapi.h

NCS Library libopc.a libopc.a libopc.a



/usr/lib/libnck.a

/usr/lib/iconv.a



/usr/lib/libnck.a

/usr/lib/iconv.a



/usr/lib/libdl.a

/usr/lib/libiconv.a

/usr/lib/libc.a or /usr/ccs/lib/libc.a


-lopc -lopc -lopc

Description N/A N/A N/A



Chapter 1 69


About the Makefile

The following directory on the management server contains the makefile for building executables:

/opt/OV/OpC/examples/progs

The build an executable with correct compile and link options, use the following makefile:

❏ Makef.aix

❏ Makef.aixncs

For more information about the managed node makefile, see the ReadMe file:

/opt/OV/OpC/examples/progs/README

Chapter 170

2 About HP-UX Managed Nodes

Chapter 2 71

About HP-UX Managed NodesIn this Chapter

In this ChapterThis chapter explains how to install and configure HP OpenView VantagePoint Operations (VPO) on HP-UX managed nodes.

Chapter 272

About HP-UX Managed NodesInstallation Requirements

Installation RequirementsThis section explains VPO hardware and software requirements for HP-UX 10.x/11.x managed nodes.

Hardware Requirements for HP-UX 10.x/11.x

Before installing VPO, make sure the HP-UX 10.x/11.x systems you select as managed nodes meet the following hardware requirements:

❏ Disk Space

28 MB (about 56 MB is required during the software installation)


None

❏ Additional RAM

None

NOTE Only PA-RISC version 1.1 or higher is supported on HP-UX 10.x managed nodes.

Chapter 2 73


Software Requirements for HP-UX 10.x

Before installing VPO, make sure the following software is installed on HP-UX 10.x managed nodes:


For a list of operating system versions supported by VPO, see the VPO Installation Guide for the Management Server.

❏ Operating System Patches

XSW700GR1020 s700: HP-UX General Release Patches, September 2001, version B.10.20.54.1

XSW800GR1020 s800: HP-UX General Release Patches, September 2001, version B.10.20.54.1


For a list of kernel parameters, see the VPO Administrator’s Reference Volume I. You can verify and change the system parameters using the SAM tool.

❏ DCE RPC

DCE RPC version 1.2.1 or higher on HP-UX 10.x

SD package: DCE-Core.DCE-CORE-RUN

NOTE VPO supports DCE versions supplied with the HP-UX 10.x operating system. Although the HP-UX operating system includes DCE, you must install DCE separately as an optional product.

❏ Internet Services

SD package: InternetSrvcs.INETSRVCS-RUN

❏ LAN/9000

SD-package: Networking.NET-RUN

❏ SNMP Agent for MIB Monitoring

SD package for HP-UX 10.20 and lower: NetworkingSnmpAgent

❏ Native Language Support (NLS) Package

SD-package: OS-Core.NLS-AUX

Chapter 274


Software Requirements for HP-UX 11.x

Before installing VPO, make sure the following software is installed on HP-UX 11.x managed nodes:



❏ Operating System Patches

• HP-UX 11.0 Managed Nodes

QPK1100 Quality Pack for HP-UX 11.0, September 2001, version B.11.00.54.7

• HP-UX 11.11 Managed Nodes

GOLDBASE11i Gold Base Patches for HP-UX 11.11, June 2001, version B.11.11.0106.9

PHSS_22898 HP aC++ -AA runtime libraries (aCC A.03.30)

PHSS_23441 s700_800 11.11 ld(1) and linker tools cumulative patch


For a list of kernel parameters, see the VPO Administrator’s Reference Volume I. You can verify and change the system parameters using the SAM tool.

NOTE If monitoring peformance metrics with the embedded performance component, increase the value of the kernel parameter max_thread_proc to: min + (Number_of_Templates * 2).

Chapter 2 75


❏ DCE RPC

DCE RPC version 1.7 or higher.

SD package: DCE-Core.DCE-CORE-RUN

NOTE VPO supports DCE versions supplied with the HP-UX 11.x operating system. Although the HP-UX operating system includes DCE, you must install DCE separately as an optional product.

❏ DCE/9000 Kernel Thread Support

SD package for HP-UX 11.0 DCE-KT-Tools

NOTE Required for HP-UX 11.0 only.

DCE-KT-Tools, which is available on the HP-UX Application Software CD-ROMs, contains a runtime library for kernel threads that VPO requires in order to run. To install the product, start the swinstall GUI of SD-UX, change the software view to Start with Products, and choose DCE-KT-Tools. DCE-KT-Tools is licensed with the HP-UX OS.

❏ Internet Services

SD package: InternetSrvcs.INETSVCS-RUN

❏ LAN/9000

SD package: Networking.NET-RUN

❏ SNMP Agent for MIB Monitoring

SD Package for HP-UX 11.x and higher: OVSNMPAgent

❏ Native Language Support (NLS) Package

SD package: OS-Core.NLS-AUX

Chapter 276

About HP-UX Managed NodesInstalling and De-installing Agents

Installing and De-installing AgentsThis section describes how to install and de-install HP-UX 10.x/11.x managed nodes.


To install VPO agents on HP-UX managed nodes, use one of the following methods:

❏ Standard Installation

See “Installing Agents with Standard Installation” on page 78.

❏ SD-UX Installation

See “Installing Agents with SD-UX” on page 79.

❏ Manual Installation

See “Installing Agents Manually” on page 83.


When installing HP-UX managed nodes, follow these guidelines:

❏ Manual Root Passwords

Make sure you know all the root passwords of all the managed nodes when you install the VPO agent software.

❏ Automatic Root Passwords

On UNIX managed nodes, passwords are not required if an .rhosts entry for root has been made or if the management server is included in /etc/hosts.equiv (HP-UX 10.x/11.x).

❏ Name of Management Server


/etc/hosts.

You can verify the name of the management server with the nslookup command.

Chapter 2 77


Installing Agents with Standard Installation

Figure 2-1 shows the standard VPO installation method.

Figure 2-1 Standard VPO Agent Installation Method

For general administration instructions, see the VPO Administrator’s Reference Volume I.

If errors occur during the installation, check the local installation logfiles:

/var/adm/sw/swagent.log

/var/adm/sw/swinstall.log

Wide Area Network(WAN)

Local Area Network(LAN)

VPO Node N

VPO Node 2

VPO Node 1

Management

Server

VPO

Data TransmissionKey:

VPO AgentPackages

Chapter 278


Installing Agents with SD-UX

To save time and money, you can install VPO on HP-UX 10.x and 11.x platforms using the advanced features of HP Software Distributor (HP SD-UX). You use this method to install the VPO agent software packages from a software depot on a node other than the VPO management server.

Installing Agents from a SD-UX Depot Node

Installing the VPO agent software packages from a software depot on a node other than the VPO management server is especially useful in an environment where a LAN of managed nodes is managed by a management server over a WAN. Instead of transferring “x” number of agent packages over the WAN line, the packages are installed once on a depot node in the remote LAN. Subsequent agent installations then get the packages from the local depot.

Figure 2-2 shows how to install VPO agents on HP-UX 10.x and 11.x managed nodes with the HP Software Distributor (SD-UX) from a remote software depot.

Figure 2-2 HP SD-UX Remote Software Depot Installation Method

Local Area Network(LAN)Management

Server

VPO

VPO Agent

VPO Node NVPO Node 2

Wide Area Network(WAN)

Data Transmission

(1)

(2)

Manual transfer of packages

Trigger remote installation

Key:

SD Depot(VPO Node 1)

(1)

(2)

Packages VPO AgentPackages

Chapter 2 79


Creating a SD-UX Depot on a Remote Node

To create an HP-UX 10.x or 11.x Software Distributor (SD-UX) depot for installing VPO managed nodes, follow these steps:

1. Copy the VPO agent locally.

If you do not have additional SD-UX licenses for transferring the software to the managed node, copy the packages locally. If this is the case on the depot node, transfer the VPO software packages from the management server over the WAN to the depot node using FTP and register the depot.

The VPO agent requires these software packages:

• opc_pkg.Z

• comm_pkg.Z

• perf_pkg.Z

The packages are located in the following directory on the management server:

• HP-UX 10.x managed nodes

/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/\s[7|8]00/hp-ux10/A.07.00/RPC_DCE_[TCP|UDP]/

• HP-UX 11.0 and 11.11 managed nodes

/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/\pa-risc/hp-ux11/A.07.00/RPC_DCE_[TCP|UDP]/

Chapter 280


2. Create a temporary, uncompressed depot.

To get a compressed depot, you must first create a temporary, uncompressed depot.

Copy the uncompressed packages into the /tmp directory and execute as follows:

swcopy -d -s /tmp/opc_pkg -x source_type=tape -x \ enforce_dependencies=false ITOAgent @ /depot1

swcopy -d -s /tmp/comm_pkg -x source_type=tape -x \ enforce_dependencies=false OVOPC-AGT @ /depot1

swcopy -d -s /tmp/perf_pkg -x source_type=tape -x \ enforce_dependencies=false OVOPC-AGT @ /depot1

If the SD-UX depot does not exist, it is created automatically.

3. Compress the depot on another depot.

Copy temporary, uncompressed depot to another depot, and specify the options -x compress_files=true in the swcopy command:

swcopy -d -s /depot1 -x enforce_dependencies=false ITOAgent @ <depot>

If the SD-UX depot does not exist, it is created automatically.

4. Remove the VPO agent from the HP SD-UX depot node.

To remove the agent from the HP SD-UX depot on the depot node, enter the following on the depot node:

swremove -d ITOAgent @ depot2

If the product is the last software in the depot, the depot is automatically unregistered by the swremove command. This does not remove the VPO agent software from the node.

Chapter 2 81


Installing Agents from the SD-UX Depot

Once the SD-UX depot is established, all VPO agents within the LAN can retrieve the VPO binary packages from the SD-UX depot instead of from the management server, as shown in Figure 2-1 on page 78 and Figure 2-2 on page 79. This part of the installation process is performed automatically.

You initiate the install operation from the administrator GUI on the VPO management server. The management server contacts the managed node and issues the install command locally on the managed node. The target managed node then retrieves the software packages from the SD-UX depot using the swinstall command, for more information, see the swinstall(1M) man page.

You can also manually retrieve the software packages from the VPO management server (see “Installing Agents Manually” on page 83).

Enabling SD-UX

To enable SD-UX, configure the node name for the SD-UX depot using the Add/Modify Node: Node Communication Options window in the VPO administrator GUI.

You can choose between the following installation methods:



❏ SD-UX Installation

See “Installing Agents with SD-UX” on page 79.

Chapter 282



In some situations, you may want to install the VPO HP-UX agent software without using the management server. This manual installation enables you to prepare the system to become a VPO managed node when it is later connected to the network. Manual installation is useful if you are preparing many systems in a central location, or if you want to avoid the network root connection necessary for standard installation.

You can install an agent on an HP-UX managed node from an SD-UX tape file or from an SD-UX depot:

❏ SD-UX Tape File

To install the agent without a depot or a network connection, copy an SD-UX tape file to the node. For instructions, see “To Install an Agent Manually from the SD-UX Tape Files” on page 84.

❏ SD-UX Depot

To pre-install many agents, create and use a depot. For instructions, see “Creating a SD-UX Depot on a Remote Node” on page 80.

Chapter 2 83


To Install an Agent Manually from the SD-UX Tape Files

To install an agent on an HP-UX managed node from an SD-UX tape file, follow these steps:



• opc_pkg.Z

• comm_pkg.Z

• perf_pkg.Z

• opc_inst


• HP-UX 10.x managed nodes

/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/\s[7|8]00/hp-ux10/A.07.00/RPC_DCE_[TCP|UDP]/

• HP-UX 11.0 and 11.11 managed nodes

/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/\pa-risc/hp-ux11/A.07.00/RPC_DCE_[TCP|UDP]/



/tmp/opc_inst

3. Examine the logfile for the node:

/var/adm/sw/swagent.log

If any errors occurred during installation, correct the problems and reinstall.

Chapter 284


To Install an Agent Manually from an SD-UX Depot

To install an agent on an HP-UX managed node from an SD-UX depot, follow these steps:

1. Install the agent packages:

Install the agent packages on the node by entering:

swinstall -s <depot_host:depot_path> ITOAgent

2. Examine the logfile for the node:

/var/adm/sw/swagent.log.

If any errors occurred during installation, correct the problems and reinstall.

TIP Installing the agent from the command line is somewhat faster than installing the agent with the SD-UX GUI. However, the command-line installation does not notify you of any warnings found in the analysis phase unless run it twice, setting the -p option in the first run. If you would like to use the GUI, simply omit the name of the agent package (ITOAgent) when you enter the swinstall command.

Installing the agent packages will produce dependency errors, because the packages do not hold all the files necessary for the agent to run.

If you want verify that all these files exist, use the following command to get a list of all software that is installed on the node:

/usr/sbin/swlist -l product

Chapter 2 85


Activating the Managed Node

After the node with the pre-installed agent is connected to the network (“To Activate the Node from the Command Line” on page 88), you can activate and register the managed node.

You can you can activate the managed node from the following:

❏ VPO GUI

❏ Command Line

To Activate the Node from the VPO GUI

To activate the node from the VPO GUI, follow these steps:


Use the following menu sequence:

Actions-> Node-> Add.



3. Open the Install/Update VPO Software and Configuration window.


Actions-> Agents-> Install / Update SW & Config.

Chapter 286


4. Update all components.

In the Install/Update VPO Software and Configuration window, do the following:

a. Select all components.

CAUTION Do not check [Force Update]. If you check this option, the management server re-installs the agent.

b. Click [OK].

Depending on whether you have pre-installed the agent, the management server does the following:

• If you have pre-installed the agent on the node, the management server activates the node, and installs the selected components.

• If you have not pre-installed the agent software, the management server installs the agent.

5. Verify that the control, message, and action agents are all running on the managed node.

Enter the following:

/opt/OV/bin/OpC/opcragt -status <node>

Chapter 2 87


To Activate the Node from the Command Line

To activate the agent on the node from the command line, follow these steps:

1. Install the agent on the node manually.

To find out how to install the agent manually, see “Installing Agents Manually” on page 83.






4. Activate the node.


/opt/OV/bin/OpC/install/opcactivate -s <VPO_mgt_server> \-cs <server.codeset> -cn <agent.codeset>


• Specifying the -s option with the opcactivate command is optional. This option starts the /opt/OV/bin/OpC/install/upd_res.sh script which integrates the VPO agent into the system startup and shutdown scripts, for example the /sbin/init.d/opcagt file.



Chapter 288


5. Update the database and start heartbeat polling for the node.

After the node is connected to the network, enter the following command on the management server:


The templates, monitors, commands, and so on must still be installed from the management server GUI. For instructions, see “To Activate the Node from the VPO GUI” on page 86-


You can de-install agents from HP-UX managed nodes automatically or manually.


To find out how to de-install agents automatically, see the VPO Administrator’s Reference Volume I.

To De-install an Agent Manually

To de-install a VPO agent from an HP-UX managed node manually, follow these steps:


2. Enter the following:

swremove ITOAgent

If Errors Occur During De-installation

If errors occur during the de-installation, check the local de-installation logfiles:

/var/adm/sw/swagent.log and /var/adm/sw/swremove.log

Chapter 2 89

About HP-UX Managed NodesAbout Preconfigured Elements

About Preconfigured ElementsThis section describes preconfigured templates, template groups, and applications used by VPO on HP-UX managed nodes.



❏ HP-UX 10.x

❏ HP-UX 11.x

Types of Default opcmsg Message Templates

Table 2-1 shows the opcmsg message templates that are available for HP-UX managed nodes.

Table 2-1 opcmsg Message Templates on HP-UX Managed Nodes

Name Description

opcmsg(1|3) Default interception of messages submitted by opcmsg(1), opcagtmsg_send(3), and opcmsg(3).

Chapter 290



Table 2-2 shows encapsulated logfiles and associated template used on HP-UX managed nodes.

Table 2-2 Encapsulated Logfiles on HP-UX Managed Nodes

Logfile Description Name

/var/adm/sulog su(1) switch user logfile Su (10.x/11.x HP-UX)

/var/adm/cron/log cron(1M) clock daemon logfile

Cron (10.x/11.x HP-UX)

/var/adm/syslog\/syslog.log

syslogd(1M) syslog daemon logfile

Syslog (10.x/11.x HP-UX)

/etc/rc.log Messages during system boot up

Boot (10.x/11.x HP-UX)

/var/adm/btmp (binary format)

History of bad login attempts

Bad Logs (10.x/11.x HP-UX)

/var/adm/wtmp (binary format)

History of logins, logouts, and data changes

Logins (10.x/11.x HP-UX)

/var/opt/OV/log/OpC/\dmesg.out

Messages generated by the HP- UX 10.x kernel

Kernel Logs (10.x/11.x HP-UX)

/var/adm/syslog/\mail.log

sendmail(1) logfile Mailqueue (10.x/11.x HP-UX)

/var/adm/syslog/\syslog.log

Fetch messages from MC/ServiceGuard and forward to APM

Syslog (ServiceGuard)

Chapter 2 91


About SNMP Trap and Event Interception

By default, VPO intercepts SNMP traps from any application sending traps to the opctrapi daemon running on the management server and on all managed nodes where the OpenView trap daemon (ovtrapd) is running, or where port 162 can be accessed directly. For details about which traps are intercepted by default, see the SNMP trap templates in the Message Source Templates window of the VPO administrator GUI.

Types of SNMP Traps

The following kinds of SNMP traps can be intercepted:

❏ Well-defined Traps

Example: system cold start, network interface up and down, and so on

❏ Internal HP OpenView Traps

Example: Traps originating from netmon.


About VPO Distributed Event Interception

VPO Distributed Event Interception enables you to intercept SNMP traps on systems other than the VPO management server. This trap interception allowing messages to be processed locally, thereby improving system performance. Automatic actions, for example, can be triggered and executed directly on the node or in the subnet, instead of being first forwarded to the management server.

Chapter 292


To Configure Basic Event Interception

To configure basic VPO Distributed Event Interception, follow these steps:

1. Configure SNMP devices or the NNM collection station.

Make sure that one of the following is true:

• SNMP Devices

SNMP devices have only one SNMP destination.

Set the destination systems for SNMP devices on HP-UX nodes in the following file:

/etc/SnmpAgent.d/snmpd.conf

Use the following statement:

trap_dest:<nodename>

• NNM Collection Station

There is only one system serving as the NNM collection station for the management server. This station should be connected through the fastest network.

2. Set the SNMP session mode.

If NNM is not running on the node where you want to intercept events, add the following line to the opcinfo file on that node:

SNMP_SESSION_MODE NO_TRAPD

3. Assign and distribute the trap template to the node.

To Avoid Duplicate Messages in Event Interception

To avoid duplicate messages, make sure that a VPO agent (and thereby, a VPO event interceptor) runs on all NNM collection stations. Use the Print Collection Station application in the NNM Tools application group to verify which managed nodes are set up as NNM collection stations.

Chapter 2 93


To Configure Event Interception with ECS

By default, opctrapi connects to the correlated event flow of pmd. You can change this behavior by adding an appropriate statement to the opcinfo file on the managed node.

Syntax:

SNMP_EVENT_FLOW [ALL|RAW|CORR]

The opctrapi process connects to the default ECS stream of pmd.

If needed, you can configure opctrapi to connect to a specific ECS stream of pmd by specifying the ECS stream in the opcinfo file:

SNMP_STREAM_NAME <stream_name>


Table 2-3 describes the default monitored objects used by VPO on HP-UX managed nodes.

Table 2-3 Object Thresholds on the HP-UX Managed Nodes


cpu_util Monitors CPU utilization. Requires the sar program.

95% 2

disk_util Monitors disk space utilization on the root disk.

90% 10

Inetd Number of executing instances of inetd (Internet Daemon).

0.5 5

MailQueue Length

Length of the sendmail queue. Number of unsent mail messages.

30 2

proc_util Monitors process table utilization. 75% 5

sendmail Number of executing instances of sendmail. 0.5 5

swap_util Monitors SWAP utilization. 80% 5

Syslogd Checks whether syslogd is running. 0.5 5

Chapter 294



On HP-UX systems, VPO can start two version of the System Administrator (SAM) graphical user interface (GUI):

❏ Motif SAM

❏ ASCII SAM

NOTE For a list of default applications available for UNIX managed nodes, see the VPO Administrator’s Reference Volume I.

About Motif SAM

The Motif version of System Administrator GUI uses the following:

Command Issued sam

Default User root

Default Password None is required. Application is started via the VPO action agent. If the default user has been changed by the operator, you must supply a password.

About ASCII SAM

The ASCII version of System Administrator GUI uses the following:

Command Issued sam

Default User root

Default Password None is configured.

Start in window (input/output).

Chapter 2 95

About HP-UX Managed NodesDistributing Scripts and Programs

Distributing Scripts and ProgramsFor HP-UX managed nodes, the platform selectors and architecture identifiers are the following:

❏ HP-UX 10.x

hp/s700/hp-ux10

hp/s800/hp-ux10

❏ HP-UX 11.x

hp/pa-risc/hp-ux11






/var/opt/OV/share/databases/OpC/mgd_node/customer\/<arch>/actions/*

Monitoring scripts and programs used by the monitoring agent and the logfile encapsulator

/var/opt/OV/share/databases/OpC/mgd_node/customer\/<arch>/monitor/*


/var/opt/OV/share/databases/OpC/mgd_node/customer\/<arch>/cmds/*

Chapter 296








Temporary Directory

HP 9000/[78]00 HP-UX 10.x HP-UX 11.x

/var/opt/OV/tmp/OpC/bin/actions/var/opt/OV/tmp/OpC/bin/cmds/var/opt/OV/tmp/OpC/bin/monitor


Managed Node

Operating System


HP 9000/700HP 9000/800

HP-UX 10.x HP-UX 11.x

/var/opt/OV/bin/OpC/actions rwxr — r — (owner: root)

/var/opt/OV/bin/OpC/cmds rwxr-xr-x (owner: root)

/var/opt/OV/bin/OpC/monitor rwxr — r — (owner: root)

Chapter 2 97


Tips for Distributing on HP-UX 10.x

VPO does not distinguish between the following architectures:

❏ Technical Workstations

HP 9000 series 700 computers

❏ Enterprise Servers

HP 9000 series 800

If you have written your own programs for HP 9000 series 700 computers (Technical Workstations), compile them with the -DA1.1 option (HP-PA compatibility mode). Use this option to enable your programs to run on HP 9000 series 800 computers (Enterprise Servers).

If you cannot use the -DA1.1 option, replace the following symbolic link with an ordinary s800/hp-ux directory tree for HP-UX 10.x managed nodes:

/var/opt/OV/share/databases/OpC/mgd_node/customer/hp\/s800/hp-ux10-> ../../s700/hp-ux10

Chapter 298

About HP-UX Managed NodesOrganization of Managed Nodes

Organization of Managed NodesFigure 2-4 shows how VPO software is organized on HP-UX 10.x and 11.x managed nodes.

Figure 2-3 VPO Software on HP-UX 10.x and 11.x Managed Nodes

If HP OpenView NNM is also installed on the managed node, only those directories displayed in boldface type are created by VPO.

At installation, the software trees (shown in Figure 2-4) on the management server (which also acts as a managed node) is combined with the management server file tree. For a diagram of the management server file tree, see the VPO Installation Guide for the Management Server.

bin conf tmp

B

log

/opt/OV

OpC OpC OpCOpC

install

lib

nls

bin conf

/var/opt/OV

include

<lang>B

bin

OpC

utils

B


Key:

contrib

OpC

databases

BBC

Chapter 2 99


Location of Files

On HP-UX 10.x and 11.x managed nodes, files are located as follows:


/var/opt/OV/tmp/OpC


/var/opt/OV/conf/OpC


The default VPO operator, opc_op, owns /home/opc_op as home directory. By default, the operators use the Korn Shell (/bin/ksh) and are not allowed to log into the system directly (that is, enter * in /etc/passwd).

If the managed node is a Network Information Service (NIS or NIS+) client, you must add the VPO default operator opc_op on the NIS server before installing the VPO software on a managed node. This ensures that the VPO default operator opc_op is used by VPO and is consistent on all systems. If you do not add the VPO default operator opc_op on the NIS server, the installation will create a user opc_op with the group opcgrp locally on the node.

Chapter 2100


Types of System Resources

VPO applies changes in the following system resource files:

/etc/passwd Default VPO operator entry.

/etc/group Default VPO operator group entry.

/sbin/init.d/opcagt VPO startup and shutdown script.

/etc/rc.config.d/opcagt VPO startup and shutdown configuration script

/sbin/rc2.d Creates link K059opcagt to /sbin/init.d/opcagt is created. This link determines when opcagt is killed during the shutdown sequence.

/etc/services Adds service ito-e-gui for the Java-based operator GUI.

/etc/inetd.conf When requested, starts the process /opt/OV/bin/OpC/opcuiwww.

/var/adm/inetd.sec By default, allows all systems to use the service ito-e-gui. If you specify a system name, only that system is allowed to use the VPO Java-based GUI.

NOTE If you are working with Network Information Services (NIS or “yellow pages”), you should adapt the user registration accordingly.

Chapter 2 101

About HP-UX Managed NodesTypes of Libraries

Types of LibrariesTable 2-7 describes the managed node libraries for VPO A.05.xx, A.06.xx, and A.7.xx.



HP

-UX

11.

x

DC

E

Library libopc_r.sl libopc_r.sl libopc_r.sl


/usr/lib/libdcekt.1

/usr/lib/libpthread.1

/usr/lib/libnsl.1

/usr/lib/libc.1

/usr/lib/libdcekt.1


/opt/OV/lib/libnsp.sl

/opt/OV/lib/libas.sl

/usr/lib/libnsl.1

/usr/lib/libc.1

/usr/lib/libdcekt.1


/usr/lib/libnsl.1


-lopc_r -lopc_r -lopc_r, -lnsp

Chapter 2102


HP

-UX

11.

x

DC

E

Description The HP-UX 11.x agent is a native 11.x agent and uses Kernel Threads which cannot be intermixed with Posix/DCE Threads.

Since Kernel Threads were not available on HP-UX 10.x and because the HP-UX 11.x object format is incompatible with the HP-UX 10.x object format, applications that were integrated with the VPO version A.04.02 software must be re-compiled on HP-UX 11.0 before the can be integrated with VPO version A.07.00.

N/A N/A



Chapter 2 103


HP

-UX

10.

x

DC

E

Library libopc_r.sl

(libopc.sl —> libopc_r.sl)

libopc_r.sl libopc_r.sl


/usr/lib/libdce.1

/usr/lib/libc.1

/usr/lib/libdce.1

/usr/lib/libc.1

/opt/OV/lib/libnsp.sl

/opt/OV/lib/libas.sl

/usr/lib/libdce.1

/usr/lib/libc.1


-lopc_r -lopc_r -lopc_r, -lnsp

Description Last version with the compatibility link.

Linking of libdce.sl and libc_r.sl is not recommended.

N/A N/A



Chapter 2104



On an HP 9000/700 or HP 9000/800 platform with HP-UX 10.x and 11.x managed nodes, use the following include file:

/opt/OV/include/opcapi.h

About the Makefiles

The following directory on the management server contains the makefiles for building executables:


The build an executable with correct compile and link options, use the following makefiles:

❏ Makef.hpux10

❏ Makef.hpux11



Chapter 2 105

About HP-UX Managed NodesMonitoring Events

Monitoring EventsThe Event Monitoring Service (EMS) enables you to monitor system resources on HP-UX, and send notifications about these system resources when they change in an observable way. EMS provides information that is not immediately accessible to VPO. For example, EMS monitors the status of peripheral components. EMS is supplied by DART. Integration into VPO is supported only by EMS version 3.x.

To use EMS, you can use the following:

❏ VPO Threshold Monitor Templates

Monitor EMS-provided resources.

❏ opcmsg (1|3) Message Interceptor Template

Receives EMS notifications.

Before you set up VPO threshold monitor templates or use the VPO EMS opcmsg templates, you must install EMS.

For more information about EMS, see the documentation supplied with the EMS product.

About EMS Threshold Monitoring

VPO provides a monitor executable, opc_get_ems_resource, that you can call in threshold monitor templates. The opc_get_ems_resource executable queries EMS for a resource instance or all instances of a resource class, and reports the current values to VPO. By setting up conditions for a threshold monitor template, you can set different thresholds for these values and react accordingly (for example, with different automatic or operator-initiated actions).

You can use only numeric and enumerated data types for threshold monitoring. To find out how to use the Object Pattern field in the Condition No. window to monitor multiple instances of a monitored object (for example, a resource class), see the VPO Concepts Guide.

Chapter 2106


Types of Data Returned by the Monitor Executable

The monitor executable, opc_get_ems_resource, returns the following data:

❏ Current Value of the Resource Instance

Available through the VPO variable:

<$VALUE>

Sample output:

1

❏ Name of the Resource Instance

Available through the VPO variable:

<$MSG_OBJECT>

Sample output:

/vg/vg00/lv/status/lvol1

❏ Readable Interpretation of the Enumerated Value

If the resource instance is of the type enumerated, this value is available through the VPO variable:

<$OPTION(EMS_ENUM)>

Sample output:

UP

Chapter 2 107


Setting up a Threshold Monitor Template

Figure 2-4 shows how to set up a threshold monitor template with opc_get_ems_resource.

Figure 2-4 Setting up a Threshold Monitor for EMS Resources

In the Monitor Program or MIB ID field, enter the following:

❏ Name of the Program Monitor

opc_get_ems_resource

❏ Name of the Threshold Monitor Template

This name tells opc_get_ems_resource where to send the result of the query.

Example:

EMS-lvol_status

❏ EMS Resource Instance or Class

Example:

/vg/vg00/lv/status

Chapter 2108


Viewing the Resource Hierarchy in the EMS GUI Client

You can view the resource instances and classes that are available in EMS with the EMS GUI client, which is integrated into SAM, the HP-UX system administration tool.

To Start the EMS GUI

To start the EMS GUI, follow these steps:

1. Start SAM.

For example, start SAM from the VPO Application Bank window.

2. Double-click the Resource Management icon

3. Double-click the Event Monitoring Service icon.

To View Resource Instances in the EMS GUI

To see a description and a list of all possible values, click [View Resource Instance Description…].

To Close the EMS GUI

When you have finished browsing through the resource hierarchy, click [Cancel] rather than [OK] because you do not wish to add the request.

Types of EMS Resource Instances

Figure 2-5 on page 110 shows all resource instances of the following resource class:

/vg/vg00/lv/status

These resource instances include the following, as well as their current values:

❏ lvol1

❏ lvol2

❏ lvol3

Chapter 2 109


Figure 2-5 Browsing the EMS Resource Hierarchy

Viewing the Resource Hierarchy in the VPO Application Bank

Instead of using the EMS GUI client in SAM to browse the resource hierarchy, you can also execute the application EMS Resources (application group UN*X Tools) in the VPO Application Bank window.

About the EMS Resources Application

When you execute EMS Resources, it opens a terminal window and calls opc_get_ems_resource -d -r. By default, EMS Resources displays all resources starting with the root directory (/). You can modify EMS Resources to start at a specific level in the resource hierarchy (for example, at /vg/vg00/lv/status).

Chapter 2110


Sample Output from the EMS Resources Command

The output is displayed in the terminal window and may look like the following example:

/vg/vg00/lv/status/vg/vg00/lv/status/lvol1 = 1 ("UP")/vg/vg00/lv/status/lvol2 = 1 ("UP")/vg/vg00/lv/status/lvol3 = 1 ("UP")

Syntax for the EMS Resource Command

The command opc_get_ems_resource requires the following syntax:

opc_get_ems_resource [-r] [-t <secs>] [-d | <ito_monitor_name>] [<resource> ...]

-r Recursively traverses class and instance tree.

-t Sets timeout to <secs> seconds. Default is 30 seconds.

-d Displays on stdout.

<ito_monitor_name>

Monitor name to be used when providing the resource value to VPO.

<resource>

Name of the resource instance and class to be monitored and displayed Default is root (/).

If Error Occur with EMS

If you encounter problems with EMS or opc_get_ems_resource, check the logfiles in the following directory for more information:

/etc/opt/resmon/log

Chapter 2 111


Viewing the Resource Hierarchy from the Command Line

To get information about configured resources, you can use the command line tool:

/opt/resmon/bin/resls

For details, see the man page resls(1).

Sending EMS Notifications to VPO

To configure event monitoring requests for EMS through opcmsg, use the EMS GUI client in SAM and the opcmsg message source template. The message source template opcmsg(3) is integrated into the EMS GUI. In the EMS GUI, you can select opcmsg(3) as a notification target for EMS events.

To Download VPO EMS Templates

EMS provides preconfigured conditions for the VPO Interface Messages template to be used with VPO.

To download VPO EMS template, follow these steps:

1. From your Internet browser, go to the following location:

http://software.hp.com

2. Click High Availability.

3. Click Event Monitoring Service Developer’s Kit.

4. Download the .tar file from the web page.

5. Follow the instructions in the readme.ito file.

Configuring VPO EMS Templates

Using the VPO threshold monitor mechanism is more effective than receiving EMS notifications from opcmsg. Not only do you have to use the VPO administrator GUI and the SAM GUI to configure EMS, you also have to do this locally on each managed node. If you are using threshold monitoring, you can configure the templates centrally on your VPO management server and distribute them to the managed nodes that have EMS installed.

Chapter 2112

About HP-UX Managed NodesHigh Availability Support on HP-UX

High Availability Support on HP-UXVPO offers MC/ServiceGuard support on both the management server and the managed nodes.

For installation and configuration instructions, see the VPO Installation Guide for the Management Server

For additional information for system administrators working with VPO in MC/ServiceGuard environments, see the VPO Administrator’s Reference Volume II.

Chapter 2 113

About HP-UX Managed NodesHigh Availability Support on HP-UX

Chapter 2114

3 About Linux Managed Nodes

Chapter 3 115

About Linux Managed NodesIn this Chapter

In this ChapterThis chapter explains how to install and configure HP OpenView VantagePoint Operations (VPO) on Linux managed nodes.

Chapter 3116

About Linux Managed NodesInstallation Requirements

Installation RequirementsThis section explains VPO hardware and software requirements for Linux managed nodes.


Before installing VPO, make sure the Linux systems you select as managed nodes meet the following hardware requirements:

❏ Disk Space

• VPO agent must be installed on a second extended (ext2) file system or a ReiserFS file system.

• 25 MB (about 50 MB is required during software installation).


None

❏ Additional RAM

4 MB

Chapter 3 117



The following software must be installed on Linux managed nodes:

❏ Operating System and Parameters

Supported operating system and kernel versions are listed in Table 3-1 on page 120.

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

Chapter 3118


❏ Packages

The following packages must be installed:

• glibc

• bash

• libstdc++

• ldconfig

• gawk

In addition, the following packages must be installed for RedHat 7.x and SuSE 7.x:

• RedHat 7.x

compat-libstdc++

• SuSE 7.x

compat

❏ DCE RPC

Delivered with the VPO agent packages.

❏ RedHat Package Manager (RPM)

Must be installed.

❏ SNMP Daemon (optional)

To provide the management server with sufficient information to automatically determine the node type of the Linux managed node, the SNMP daemon (snmpd) should be running when you install the software remotely from the VPO management server. After you finish the installation, the daemon must be running if you want to use MIB variable monitoring.

Chapter 3 119


Table 3-1 shows the operating system and kernel version supported by VPO for Linux managed nodes.

Table 3-1 Supported Operating System and Kernel Versions

Language Operating System and Version

Kernel glibc

English RedHat 6.2 2.2.x

x can be ≥ 14

2.1.3

RedHat 7.0 2.2.x

x can be ≥ 16

2.1.92

RedHat 7.1 2.4.x

x can be ≥ 2

2.2.2

SuSE 6.2 2.2.x

x can be ≥ 10

2.1.1

2.1.2

2.1.3

SuSE 6.3 2.2.x

x can be ≥ 13

2.1.2

2.1.3

SuSE 6.4 2.2.x

x can be ≥ 14

2.1.3

SuSE 7.0 2.2.x

x can be ≥ 16

2.1.3

SuSE 7.1 2.4.x

x can be ≥ 0

2.2.x

x can be ≥ 18

2.2

SuSE 7.2 2.4.x

x can be ≥ 4

2.2

Chapter 3120


Japanese RedHat 6.1J 2.2.x

x can be ≥ 12

2.1.2

2.1.3

RedHat 6.2J 2.2.x

x can be ≥ 14

2.1.3

RedHat 7.0.1J 2.2.x

x can be ≥ 16

2.1.95

RedHat 7.1J 2.4.x

x can be ≥ 2

2.2.2

TurboLinux 6.0J 2.2.x

x can be ≥ 13

2.1.2

2.1.3

TurboLinux 6.1J 2.2.x

x can be ≥ 15

2.1.3

Table 3-1 Supported Operating System and Kernel Versions

Language Operating System and Version

Kernel glibc

Chapter 3 121

About Linux Managed NodesInstalling and De-installing Agents

Installing and De-installing AgentsThis section describes how to install and de-install Linux managed nodes.


When installing Linux managed nodes, follow these guidelines:

❏ Installation Methods

You can install agents in one of two ways:

• Remotely

From the management server.

For details, see “Installing Agents” on page 123.

• Manually

From the Linux managed nodes.

For details, see “To Install an Agent Manually” on page 124.

❏ Remote Installation

Before installing agents remotely, you must set up the management server and provide remote logins. For details, see “Before Installing Agents Remotely” on page 123.

❏ Hostnames of Management Server


/etc/hosts


Chapter 3122


TIP When checking running processes with the Linux ps command, VPO processes may be reported several times because the Linux ps command reports all threads associated with a process. This duplication is the normal Linux behavior, and is not related to VPO.

Use the command ps fax to get a more detailed listing of all running processes and their dependencies.

Installing Agents

You can install agents on Linux managed nodes remotely from the VPO management server or locally on Linux managed nodes.

Before Installing Agents Remotely

Before installing agents remotely, you must do the following:

❏ Establish “remsh” Services

Enable remsh (rsh) services so you can install the agent software remotely from the VPO management server on a Linux managed node.

❏ Enable Automatic (De-)Installation

On the management server, select Automatic (De-)Installation for the managed node.

❏ Provide User Name

On the management server, provide a username for the installation.

❏ Add tty Devices for Remote Logins

Add tty devices for remote logins (for example, ttyp0, ttyp1, and so on) to the following file:

/etc/securetty

Chapter 3 123



For general installation instructions, see the VPO Administrator’s Reference Volume I.

To Install an Agent Manually

In some situations, you may want to install the Linux agent software without using the management server. Manual installation prepares the system to become a VPO managed node when it is later connected to the network. This approach is useful if you are preparing many systems in a central location, or if you want to avoid using the root connection over the network that is necessary for a standard agent installation.

To install the VPO agent on a Linux system that will become a VPO managed node, follow these steps:

1. Verify hardware and software requirements.

Make sure that your Linux managed node meets the hardware and software requirements described in “Installation Requirements” on page 117. Also, review the installation tips offered in “Tips for Installing Agents” on page 122.

Chapter 3124




• opc_pkg.Z

• comm_pkg.Z

• perf_pkg.Z

• opc_inst


• Linux RedHat 6.2, 7.0, SuSE 6.x, 7.0 and TurboLinux 6.x

/var/opt/OV/share/databases/OpC/mgd_node/vendor/ \linux/intel/linux22/<VPO_version>/RPC_DCE_TCP/

• Linux RedHat 7.1, SuSE 7.1 and 7.2

/var/opt/OV/share/databases/OpC/mgd_node/vendor/ \linux/intel/linux24/<VPO_version>/RPC_DCE_TCP/

In these directories, <VPO_version> is the version of VPO (for example, A.07.00).

3. Add the managed node to the VPO Node Bank window.

Use the VPO administrator GUI to add the managed node to the VPO Node Bank.

Chapter 3 125


4. Install the VPO agent software.

On the Linux managed node, do the following:

a. Install the Agent.


/tmp/opc_inst

b. Activate the agent by entering:

/opt/OV/bin/OpC/install/opcactivate -s\ <VPO_mgt_server> -cs <server.codeset> -cn <agent.codeset>

In this command, <VPO_mgt_server> is the hostname of your VPO management server.




If Errors Occur During Installation


/tmp/rpm.log

This file is empty if the installation had no errors.

Chapter 3126



You can de-install agents from Linux managed nodes automatically or manually.


For general de-installation instructions, see the VPO Administrator’s Reference Volume I. For standard de-installation, rhosts equivalency must be established.


To de-install an agent manually, follow these steps:


2. De-install the VPO agent software by entering:

rpm -e OPCPERF OPC OPCCOMM

NOTE If you are removing an older version of the agent, use the command: rpm -e OPC dce.

3. De-install DCE by entering:

rpm -e dce

Removing Older Agents

If older VPO agent packages are no longer required and are not installed on any managed node, you can remove them with the following commands:

❏ Linux RedHat 6.2, 7.0, SuSE 6.x, 7.0 and TurboLinux 6.x

/opt/OV/bin/OpC/install/rm_opc.sh linux/intel/linux22 \ <VPO_version>

❏ Linux RedHat 7.1, SuSE 7.1 and 7.2

/opt/OV/bin/OpC/install/rm_opc.sh linux/intel/linux24 \ <VPO_version>

In these commands, <VPO_version> is the version of VPO that supports this agent platform (for example, A.07.00).

Chapter 3 127

About Linux Managed NodesAbout Preconfigured Elements

About Preconfigured ElementsThis section describes preconfigured templates, template groups, and applications used by VPO on Linux managed nodes.

Preconfigured Template Groups


❏ Linux (RedHat)

NOTE The Linux (RedHat) template group also applies to TurboLinux.

❏ Linux (SuSE)


Table 3-2 shows encapsulated logfiles and associated template used on Linux managed nodes.

Table 3-2 Encapsulated Logfiles on Linux Managed Nodes


/var/log/cron Cron logfile Cron (RedHat Linux and TurboLinux)

/var/log/messages Failed logins and su Messages (RedHat Linux, SuSEa and TurboLinux)

/var/log/wtmp History of logins Logins (Linux)

/var/log/warn Kernel messages Kernel messages (SuSE)

a. For SuSE Linux, all cron messages are saved into file /var/log/messages.

Chapter 3128

About Linux Managed NodesAbout Preconfigured Elements

No SNMP Trap and Event Interception

The VPO event interceptor is not supported on Linux managed nodes.


Table 3-3 describes the default monitored objects used by VPO on Linux managed nodes.





cpu_util Monitors CPU utilization. 95% 2

disk_util Monitors disk space utilization on root disk. 90% 10

Inetd Checks if Inetd is running. 0.5 5

MailQueueLength

Determine length of sendmail mail queue (unsent email).

30.0 2

Sendmail Checks if sendmail is running. 0.5 5



Chapter 3 129

About Linux Managed NodesDistributing Scripts and Programs

Distributing Scripts and ProgramsFor Linux managed nodes, the platform selectors and architecture identifiers are the following:

❏ Linux RedHat 6.2, 7.0, SuSE 6.x, 7.0 and TurboLinux 6.x

linux/intel/linux22

❏ Linux RedHat 7.1, SuSE 7.1 and 7.2

linux/intel/linux24

Chapter 3130







Linux RedHat 6.2, 7.0, SuSE 6.x, 7.0 and TurboLinux 6.x:

/var/opt/OV/share/databases/OpC/mgd_node/customer \/linux/intel/linux22/actions/*

Linux RedHat 7.1, SuSE 7.1and 7.2:

/var/opt/OV/share/databases/OpC/mgd_node/customer \/linux/intel/linux24/actions/*



/var/opt/OV/share/databases/OpC/mgd_node/customer \/linux/intel/linux22/monitor/*


/var/opt/OV/share/databases/OpC/mgd_node/customer \/linux/intel/linux24/monitor/*



/var/opt/OV/share/databases/OpC/mgd_node/customer \/linux/intel/linux22/cmds/*


/var/opt/OV/share/databases/OpC/mgd_node/customer \/linux/intel/linux24/cmds/*

Chapter 3 131






Table 3-5 Temporary Directories for Distributed Scripts and Programs on Managed Nodes


Temporary Directory

Intel-based PCs Linux /var/opt/OV/tmp/OpC/bin/actions/var/opt/OV/tmp/OpC/bin/cmds/var/opt/OV/tmp/OpC/bin/monitor


Managed Node

Operating System


Intel-based PCs

Linux /var/opt/OV/bin/OpC/actions rwxr-xr-x(owner: root)


/var/opt/OV/bin/OpC/monitor rwxr-xr-x(owner: root)

Chapter 3132

About Linux Managed NodesOrganization of Managed Nodes

Organization of Managed Nodes Figure 3-1 shows how VPO software is organized on Linux managed nodes.

Figure 3-1 VPO Software on Linux Managed Nodes

var

opt OV

OV

bin lib

OpC C

LC_MESSAGESinstall utils

opt

/

conf logbin tmp

OpC OpC OpCOpC

bin

localeinclude

B

BB


contrib

OpC

BBC

databases

Chapter 3 133


Location of Files

On Linux managed nodes, files are located as follows:


/var/opt/OV/tmp/OpC




If they do not already exist, the default VPO operator opc_op and group opcgrp are created.

About Default VPO Operator Entries

The default VPO operator appears in the following directory on Linux managed nodes:

/etc/passwd

Fields include the following:

User Name opc_op

Encrypted Password * (no login)

User-ID 777 (if still available) or next possible free number

Group-ID 77 (if still available) or next possible free number

Description Default VPO operator

Home Directory /home/opc_op

Login Shell /bin/sh (POSIX shell)

Chapter 3134


About Default VPO Operator Group Entries

The default VPO operator group appears in the following directory on Linux managed nodes:

/etc/group


Group Name opcgrp

Encrypted Password Empty

Group-ID 77 or higher

Users opc_op

Description Default VPO operator group

Chapter 3 135

About Linux Managed NodesTypes of Libraries



VPO Version

VPO A.05.xx VPO A.06.xx VPO A.07.xx

DCE Library libopc_r.so libopc_r.so libopc_r.so


RedHat 5.x:

libdcerpc.solibdcethread.solibpthread.solibuuid.solibcrypt.so.1libstdc++.so.2.8

RedHat 6.x, 7.x, SuSE 6.x, 7.x and TurboLinux 6.x:

libdcerpc.solibdcethread.solibpthread.solibuuid.solibcrypt.so.1libstdc++-libc6.1-1.so.2

RedHat 5.x:

libdcerpc.solibdcethread.solibpthread.solibuuid.solibcrypt.so.1libstdc++.so.2.8libopcas.so


libdcerpc.solibdcethread.solibpthread.solibuuid.solibcrypt.so.1libstdc++-libc6.1-1.so.2libopcas.so

RedHat 5.x:

libdcerpc.solibdcethread.solibpthread.solibuuid.solibcrypt.so.1libstdc++.so.2.8libopcas.so


libdcerpc.solibdcethread.solibpthread.solibuuid.solibcrypt.so.1libstdc++-libc6.1-1.so.2libopcas.so


-D_REENTRANT-lopc_r -lnsp -lpthread

-D_REENTRANT-lopc_r-lnsp-lpthread

-D_REENTRANT-lopc_r-lnsp-lpthread

Description The LD_LIBRARY_PATH variable has to be exported or ldconfig has to be executed.

The LD_LIBRARY_PATH variable has to be exported or ldconfig has to be executed.

The LD_LIBRARY_PATH variable has to be exported or ldconfig has to be executed.

Chapter 3136



On an Intel 486 or higher platform with Linux managed nodes, use the include file:


An example of how the API functions are used is available in the following file on the management server:

/opt/OV/OpC/examples/progs/opcapitest.c

About the Makefile




❏ Makef.linux



Chapter 3 137


Chapter 3138

4 About MPE/iX Managed Nodes

Chapter 4 139

About MPE/iX Managed NodesIn this Chapter

In this Chapter This chapter explains how to install and configure HP OpenView VantagePoint Operations (VPO) on MPE/iX managed nodes.

Chapter 4140

About MPE/iX Managed NodesInstallation Requirements

Installation RequirementsThis section explains VPO hardware and software requirements for MPE/iX managed nodes.


Before installing VPO, make sure the MPE/iX systems you select as managed nodes meet the following hardware requirements:

❏ Disk Space



None

❏ Additional RAM

None


Before installing VPO, make sure the following software is installed on MPE/iX managed nodes:



❏ DCE RPC

CE RPC 1.0.2 or DCE RPC 1.2.1

❏ NS Services

Chapter 4 141

About MPE/iX Managed NodesInstallation Requirements

Requirements for the Management Server

You must install the vt3k package on the management server. The vt3k package is available on the HP-UX Application Software CD-ROMs.

Required MPE/iX Patches

You must install the following MPE/iX patches:

Table 4-1 Required MPE/iX Patches

MPE/iX Patch ID Description

6.0 MPEKXE5 Adds routines to the system SL.PUB.SYS that the console interceptor requires to operate.

ITOED07A Provides routines to the XL.PUB.SYS to allow the VPO agent to call various NCS routines.

6.5 FRILXX7A Enables the VPO agent to register at the DCE rpcd.

This patch is required if the basic DCE client is installed that comes free with MPE FOS.

DCELXX6A This patch is required if DCE is installed that has to be purchased separately.

ITOED07B Provides routines to the XL.PUB.SYS to allow the VPO agent to call various NCS routines.

7.0 FRILXX7A Enables the VPO agent to register at the DCE rpcd.

This patch is required if the basic DCE client is installed that comes free with MPE FOS.

DCELXX6A This patch is required if DCE is installed that has to be purchased separately.

ITOED07C Provides routines to the XL.PUB.SYS to allow the VPO agent to call various NCS routines.

Chapter 4142

About MPE/iX Managed NodesInstalling and De-installing Agents

Installing and De-installing AgentsThis section describes how to install and de-install MPE/iX managed nodes.


This section includes tips for installing MPE/iX managed nodes.

About the Management Server Name

Before installing agents, the name of the management server must be known to the managed node. This means that it must be registered on the name server or in the local host table, HOSTS.NET.SYS.

About Daemons

Before installing agents on the managed node, the DCE RPC Daemon (dced or rpcd) must be running.

If this daemon is not running, the VPO services cannot be started. Automatic startup and integration of the startup functionality in the appropriate boot procedure is performed by VPO only for the dced/rpcd daemon, and only if you have selected the Automatic Update of System Resource Files option, see the Add/Modify Node window in the VPO administrator GUI.

An example of a system resource file is the following:

SYSSTART.PUB.SYS

Chapter 4 143



If you do not need the functionality of the default VPO operator on your managed nodes (except on the management server), you can purge the related information (that is, purge the account OVOPR).

About Login and Logout UDCs

Before installing software, disable the login and logout UDCs for the following, if they are present:

❏ manager.sys

❏ mrg.ovopc

❏ agent.ovopc

NOTE Interactive login and logout UDCs are not supported by VPO. For this reason, you must disable login and logout UDCs during software installation and application startup using the vt3k connection.

About Languages

Before starting the VPO agent software installation, always set LANG to C.

About IP Addresses

To check IP addresses, use the following:

NSLOOKUP.HPDCE.SYS

For more information, see the VPO Administrator’s Reference Volume I.

Chapter 4144


About Domain Name Resolution

In its current release, VPO supports only the domain name service for IP address resolution. Therefore the (fully qualified) management server system must be known by the domain name resolver (as configured in RESLVCNF.NET.SYS on the managed node). Or, if no name server is running, the management server name must be locally registered in HOSTS.NET.SYS.

IP address resolution through the following are not supported:

❏ Network Directory (NSDIR.NET.SYS)

❏ Probe (and Probe Proxy)

About the Logging Group

The logging group on MPE/iX is where the files opcmsglg (local message logfile) and opcerror reside. This logging group must belong to the account OVOPC. If the logging group it does not belong to OVOPC, VPO services cannot write or create files in that group. For more information, see the VPO Administrator’s Reference Volume I.

About VPO Agent Jobs

VPO agents run in the job, OPCAGTJ,AGENT.OVOPC. For this reason, you should probably adapt HPJOBLIMIT to ensure that all jobs, including VPO agents, can be started (for example, when not running VPO intelligent agents).

The VPO action agent also streams separate jobs for application startup and command broadcasting. Adapt the HPJOBLIMIT accordingly.

About Executable Libraries

Before you install agents, the executable library, SNMPXL.NET.SYS, must be available, and VPO must have execution rights. If the executable library is not available or if VPO does not have execution rights, the VPO Monitor Agent will not operate.

Chapter 4 145


About Time Zones

Before installing software, you must set the TIMEZONE variable to correct differences between the various time resources used by VPO C routines and MPE/iX intrinsics and commands. If you do not set this variable, messages, error trace files, and trace logfiles receive the wrong creation time stamp. These incorrect time stamps can cause problems when you work with multiple management servers. Incorrect time stamps also disrupt the timing of follow-the-sun, which switches message routing.

Insert the following call at a global location (for example, at the logon UDC or SYSSTART.PUB.SYS):

call: setvar TZ,”TIMEZONE”

For possible TIMEZONE values, see tztab.lib.sys. Set the variable according to your country or region.

If hardware time and system time are still misaligned, you can correct them with the setclock command. for values for all MPE/iX clocks, see showclks.pubxl.telesup. For example, to align the clocks, see “help setclock operation.”

About Spool Files

When tasks are executed in a job (for example, scheduled actions, broadcast commands, or X-applications), the spool files generated from these tasks are automatically deleted. If you want to retain the spool file, set the following variables in the file OPCINFO.BIN.OVOPC to the following:

OPC_MPE_CREATE_SPOOL_FILE TRUE

To define the outfence for spool files, set the following variable:

OPC_MPE_OUTCLASS_STRING <outcalls_string>

Example:

OPC_MPE_OUTCLASS_STRING ,1,1

Chapter 4146


About Streamed Jobs

You can use the system boot file, SYSSTART.PUB.SYS, to set up a normal user environment automatically when VPO is started.

Parameters for SYSSTART.PUB.SYS

The contents of this file should include command parameters appropriate for your environment, such as the following:

❏ Standard limits for job sessions

❏ Spooler start commands

❏ Stream device identification

❏ Outfence priorities

❏ Event logging

Excluding Network Commands from SYSSTART.PUB.SYS

A SYSSTART file can contain selected MPE/iX commands (and their parameters) that the system manager is allowed to execute. Networking commands are excluded.

You should exclude networking commands from the following:

❏ Jobs streamed from SYSSTART

❏ Logon UDC for OPERATOR.SYS

Starting a Streamed Job

If you have used the Add/Modify Node window to select the Automatic Update of System Resource Files option for the managed node, SYSSTART.PUB.SYS is created or updated.

NOTE SYSSTART.PUB.SYS is not created if the Automatic Update of System Resource Files option for the managed node already contains a pre-existing VPO entry.

Chapter 4 147


SYSSTART.PUB.SYS contains the start sequence for the job stream OPCSTRTJ.BIN.OVOPC. This job is used for starting the DCE RPC Daemon (dced or rpcd) and the VPO agents. (In this job, stream refers to the standard STREAM commands, or to the node-specific stream utility configured in the administrator GUI, using the Advanced Options window, accessed from the Add/Modify Node window.)

Before starting VPO agents, you must ensure that the network services are running.

For an example of this streamed job, see the following file:

/var/opt/OV/share/databases/OpC/mgd_node/\vendor/hp/s900/mpe-ix/A.06.00/sysstrtj.

To Set up a Customized Job Stream Facility

To avoiding hard-coded passwords and thereby improve security, you can set your own stream facility.

To set up a customized job stream facility, follow these steps:

1. Open the Add/Modify Node or Node Defaults window.

2. Open the Node Advanced Options window.

3. Do one of the following:

• Set up a customized job stream facility.

No passwords are placed in the VPO job files. Control over the job is given to your own stream facility.

• Use the VPO default.

If you leave the default, passwords remain unencrypted and the file OPCSTRTJ.BIN.OVOPC contains the AGENT.OVOPC password.

Chapter 4148


Preparing VPO for a Customized Job Stream Facility

If you want to use your own customized job stream facility, check the MPE/iX startup file SYSSTART.PUB.SYS before installing VPO A.06.00 software. If there is an entry for VPO (the installation process checks for the keyword OperationsCenter), that entry will not be modified.

You can modify the line that streams the VPO startup job OPCSTRTJ.BIN.OVOPC manually so that it will not be changed by later software installation.

For example, the change the following line:

❏ Change

STREAM OPCSTRTJ.BIN.OVOPC

❏ To

my job-stream facility> OPCSTRTJ.BIN.OVOPC

In this line, <my job-stream facility> could be the Maestro mstream.

If there is no entry for VPO in SYSSTART.PUB.SYS, the automatic software installation inserts an entry for VPO in SYSSTART.PUB.SYS. The major parts of the entry looks like this:

comment ... OperationsCenter

<customer-defined stream-facility> OPCSTRTJ.BIN.OVOPC

Installing Agents

See the VPO Administrator’s Reference Volume I for general installation instructions.

In an error occurs (for example, if the installation process could not be reviewed in a terminal window), check the following logfile management server for errors or warnings:

/var/opt/OV/log/OpC/mgmt_sv/install.log


For general de-installation instructions, see the VPO Administrator’s Reference Volume I.

Chapter 4 149

About MPE/iX Managed NodesAbout Preconfigured Elements

About Preconfigured ElementsMPE/iX preconfigured elements are described in greater detail in the Supplementary Guide to MPE/iX Templates:

http://<management_server>:8880/ITO_DOC/C/manuals/MPETemplates.pdf

In this URL, <management_server> is the fully qualified hostname of your management server.


Table 4-2 describes the default template groups available for MPE/iX managed nodes.


For the types of encapsulated logfiles and associated templates used on MPE/iX managed nodes, see the Supplementary Guide to MPE/iX Templates for more information.

Table 4-2 MPE/iX Template Groups

Template Group Description

MPE/iX Templates for MPE/iX

MPE/iX Database monitoring

Templates for Image/SQL databases

MPE/iX Network monitoring

Templates for Network Interfaces and Services

MPE/iX OS monitoring Templates for monitoring MPE/iX

Chapter 4150


Intercepting Messages

VPO is able to intercept messages that are sent to the MPE/iX console. Some of these messages already have a predefined message classification, which VPO maps where possible to a message group and severity level.

About Default Message Mapping

Table 4-3 shows how MPE/iX classifications are mapped to VPO Message Groups.

For details about the MPE/iX console messages that are intercepted, see the following:

❏ MPE/iX console template MPE Console Messages in the Message Source Templates window

❏ Supplementary Guide to MPE/iX Templates

Table 4-3 Default Message Mapping on MPE/iX Managed Nodes

MPE/iX Classification VPO Message Group

Database Misc

DTC Misc

Hardware Hardware

Jobs Job

Logging Misc

MPE/iX OS

Network Network

Performance Performance

Printer Output

Security Security

Spooler Output

Storage Backup

Chapter 4 151


Mapping Messages to VPO Security Levels

Table 4-4 on page 152 shows how MPE/iX messages are mapped to the VPO severity levels.

Mapping NMEV Markers

Messages from the MPE/iX operating system might contain so-called Node Management Event (NMEV) markers. VPO uses these markers to map MPE/iX console messages to the severity, message group, application, and object fields for VPO messages.

NMEV markers have the format NMEV#pcc@aaa, where:

p MPE/iX Message Severity mapped to VPO severity. If the severity is not in the range of 0 to 3, it is an invalid marker and the pattern is treated as normal text. (See Table 4-4 on page 152 for the possible values.)

cc MPE/iX Message Class mapped to the VPO Object field (optional: values from 0 to 99). The MPE/iX message class is currently not used by MPE/iX. If this field is omitted, the default 00 is used.

aaa MPE/iX Application ID identifying the source of the message, mapped to the VPO Application field (optional: values from 0 to 310).

If the @aaa portion is omitted, it is set to the default value of @310. This maps the message to the message group Misc and the application Console Event.

Table 4-4 MPE/iX and VPO Message Mapping Severity

MPE/iX Severity Level VPO Severity Level

0 Normal

1 Normal

2 Warning

3 Critical

Chapter 4152


Table 4-5 shows how NMEV markers are mapped in VPO.

Table 4-5 NMEV Marker Mapping

MPE/iX Application ID

VPO Message Group

Application/Operating System Subsystem

052 Performance Laser/RX

053 Database Allbase/SQL

194 Network Public Networking

195 Network Network-OSI

196 Network Network-NS

198 Network Network-SNA

200 Output Ciper Devices

206 OS I/O Services

211 Output Native Mode Spooler

212 Output Page Printer

213 Output Device Manager

214 Storage Printer,Tape,Spool

215 Storage Software Resiliency

216 OS Threshold Manager

217 Storage Store/Restore

218 Job Jobs/Sessions

220 OS Process Mgr

221 Logging System Logging

222 OS Transaction Mgmt

224 Logging User Logging

225 Hardware SPU Switchover

Chapter 4 153


Some of the entries in the VPO Message Group column are not configured as default VPO message groups when VPO is installed. Messages sent to those message groups are routed to the message group Misc as described in Table 4-4 on page 152. Create these message groups if you want those messages to be routed to groups other than Misc.

For example, the marker NMEV#200@214 would generate a message with the severity Warning, in the message group Storage, concerning the application Printer,Tape,Spool.

226 OS Reply Info Table

227 OS System Manager

228 Output High End Printer

229 Hardware Diagnostic-System

230 OS Command Interpreter

231 OS System & Error Mgmt

232 OS Label Management

233 Storage Magneto-Optic Lib

234 DTC Terminal I/O

235 DTC DCC Surrogate

236 Storage Labeled Tape

237 Security MPE/iX Security

238 OS Native Language

239 Hardware UPS Monitoring

310 Misc Console Event

Table 4-5 NMEV Marker Mapping

MPE/iX Application ID

VPO Message Group

Application/Operating System Subsystem

Chapter 4154


If no VPO-to-MPE/iX mapping is available for an MPE/iX console message intercepted by VPO, the original MPE/iX classification is used as a default value and the message appears in the message group Misc until you configure a message group that more accurately suits your requirements. If you need different mapping, you can apply the VPO concept of message regrouping.

The VPO attribute mapping is defined in the following file:

CONSDESC.COMMANDS.OVOPC

This file is delivered by default with the MPE/iX agent installation.

For more information about how to configure this file to map NMEVs other than the ones defined in Table 4-5 on page 153, see “Generating a New NMEV Marker” on page 155.

Generating a New NMEV Marker

The VPO Console Interceptor supports all methods of generating NMEV event messages.

An NMEV event marker can be generated in the following ways:

❏ TELLOP

Inserting the marker into the text of a TELLOP command.

❏ PRINTOP

Inserting the marker into a parameter for calling the PRINTOP command.

❏ NMEVENT

Calling the NMEVENT intrinsic by way of a program.

The NMEV marker string can be placed in TELLOP messages. This string can be useful for generating messages to VPO from within jobs or sessions. The PRINTOP intrinsic can also be used to send the NMEV marker to the console from programs. In both cases, the MPE/iX Console Interceptor processes the message. In all cases, the valid NMEV marker is stripped from the text of the message before the messages is forwarded to the message browser.

Chapter 4 155


The NMEVENT intrinsic performs a function similar to opcmsg(3). Some networking and other third-party applications may use this intrinsic. However, it is recommended that all applications generating VPO events use the opcmsg(3) call instead of the NMEVENT API.

You can add new NMEV markers to the consdesc file so that VPO can map user-defined NMEV markers to user-defined VPO message groups, application, and object fields. You should not create user-defined IDs because it is possible that the user-defined application IDs could conflict with HP-defined ID if HP added entries to the default consdesc file in the future.

The default consdesc file is located in the following directory on the management server:

/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s900\/mpe-ix/<ito_version>/cmds/consdesc.Z

This file is compressed. You must uncompress it before you can start editing it. Place your customized version of this file into the following directory on the management server

/var/opt/OV/share/databases/OpC/mgd_node/customer/hp\/s900/mpe-ix/cmds/consdesc

Distribute the default consdesc file using the Install / Update VPO Software and Configuration window. You do not need to compress it. VPO does that for you.

After distribution, the file is located on the MPE/iX managed node at:


NOTE You must restart the MPE/iX console interceptor on your MPE/iX managed node to activate the changes in the following file:


To restart the MPE/iX console interceptor on your MPE/iX managed node, enter the following:

/opt/OV/bin/OpC/opcragt -start

Chapter 4156



The VPO event interceptor is not supported on MPE/iX managed nodes.


For information about the default monitored objects used by VPO on MPE/ix managed nodes, see the Supplementary Guide to MPE/iX Templates.

Tips for Configuring File Names

You can provide actions/cmds/monitor command files for MPE/iX managed nodes on the management server in:

/var/opt/OV/share/databases/OpC/mgd_node/\customer/hp/s900/mpe-ix

If you do so, keep the following in mind:

❏ Character Length

Make sure the file names are not longer than 8 characters.

❏ Special Characters

The characters underscore (_) and dash (-) are not allowed.

❏ Case

MPE/iX does not distinguish between uppercase and lowercase letters.

❏ ASCII Format

Only ASCII files are supported. Binaries for automatic distribution to MPE/iX are not supported because the appropriate MPE/iX file code is not known to the management server.

Chapter 4 157



The following default applications are available for MPE/ix managed nodes:

❏ Broadcast

❏ Disk Space

❏ Lan Console

❏ Monitor Console

❏ Physical Terminal

❏ Print Status

❏ Processes

❏ Virtual Terminal

❏ Vt3K (Block Mode)

❏ Vt3K (Type Ahead)

NOTE All applications except Physical Terminal and Virtual Terminal:

If the default user has been changed by the operator, you must supply a password.

For more information, see the VPO Administrator’s Reference Volume I and the Supplementary Guide to MPE/iX Templates.

About “Broadcast”

VPO application that allows you to issue the same command on multiple systems in parallel.

Default User MGR.OVOPR

Default Password None is required. Application is started through the VPO action agent.

Chapter 4158


About “Disk Space”

VPO shows the current disk usage.

Command Issued discfree d

Default User MGR.OVOPC

About “Lan Console”

VPO allows the user all console commands.

Command Issued netcons.bin.ovopc lancon

Default User MANAGER.SYS

About “Monitor Console”

VPO displays all messages sent to the MPE/iX console.

Command Issued netcons.bin.ovopc

Default User AGENT.OVOPC

About “Physical Terminal”

The script defined as the Physical Terminal command in the Managed Node Configuration window is called when starting the physical terminal application.

Default User MANAGER.SYS

Default Password None is configured.

About “Print Status”

Shows the current status of spooling systems.

Command Issued listspf

Default User MGR.OVOPC

Default Password None required. Application is started through the VPO action agent.

Chapter 4 159


About “Processes”

VPO displays the status of the running processes.

Command Issued showproc; pin=1;system;tree

Default User MANAGER.SYS because showproc requires SM capability.

About “Virtual Terminal”

For a virtual terminal connection to MPE/iX systems, VPO uses vt3k as virtual terminal emulator for HP 3000 nodes running MPE/iX. For ARPA host name to NS node name mapping, see the section in the VPO Administrator’s Reference Volume II.

Default User MGR.OVOPR

Chapter 4160

About MPE/iX Managed NodesDistributing Scripts and Programs

Distributing Scripts and ProgramsFor MPE/ix managed nodes, the platform selector and architecture identifier is the following:

hp/s900/mpe-ix






/var/opt/OV/share/databases/OpC/mgd_node/customer\/hp/s900/mpe-ix/actions/*


/var/opt/OV/share/databases/OpC/mgd_node/customer\/hp/s900/mpe-ix/monitor/*


/var/opt/OV/share/databases/OpC/mgd_node/customer\/hp/s900/mpe-ix/cmds/*

Chapter 4 161

About MPE/iX Managed NodesDistributing Scripts and Programs







Temporary Directory

HP 3000/900 MPE/iX TMPACT.OVOPC TMPCMDS.OVOPC TMPMON.OVOPC .ZOVOPC (for compressed files)

Table 4-8 Target Directories for Distributed Scripts and Programs on Managed Nodes

Managed Node

OS Directory Access Rights

HP 3000/900 MPE/iX ACTIONS.OVOPC cap=BA,IA,PM,MR,DS,PH

R,X,L,A,W,S:AC

COMMANDS.OVOPC cap=BA,IA,PM,MR,DS,PH

R,X:ANY;L,A,W,S:AC

MONITOR.OVOPC cap=BA,IA,PM,MR,DS,PH

R,X,L,A,W,S:AC

Chapter 4162

About MPE/iX Managed NodesOrganization of Managed Nodes

Organization of Managed Nodes Figure 4-1 shows how software is organized on MPE/iX managed nodes.

Figure 4-1 VPO Software on MPE/iX Managed Nodes

During installation, VPO creates the accounts OVOPC and OVOPR. The group PUB.OVOPC is not used by VPO.

Location of Files

On MPE/iX managed nodes, files are located as follows:


TMP.OVOPC


CONF.OVOPC


On MPE/iX, the default operator, MGR.OVOPR, is assigned the dummy group, PUB.OVOPR, as home group. The MPE/iX default capabilities and access rights are applied for this account and group.

OVOPC

PUB

BIN

CONFTMP

LOG

TMPACTTMPCMDS

TMPMONTMPCONF

MSG

ACTIONS

MONITOR

COMMANDS

Z

HLIB RBIN

Chapter 4 163


About the System Resource File

VPO applies changes in the following system resource file:

SYSSTART.PUB.SYS

This resource is used for VPO agent startup. You can modify it only if you have set the Automatic Update of System Resource Files option.

Mapping ARPA Host Names to NS Node Names

Table 4-9 describes ARPA hostname to NS node name mapping.

Table 4-9 ARPA to NS Node Name Mapping

ARPA Hostname NS Node Name Comment

hpbbli smarty Different node namesbut same domain

hpsgmx18.sgp.hp.com hpsgmx18.sgp.hpcom Same node names, but managed node belongs to different domain than management server

topaz.sgp.hp.com nstopaz.mis.hpsg Node names and domains differ

Chapter 4164


About the vt3k Operation

VPO uses the vt3k operation for the following:

❏ Software (De-)Installation

Installing and de-installing software on an MPE/iX managed node.

❏ Virtual Terminal Connection

Connecting a virtual terminal from the operator Application Desktop or the administrator Application Bank to an MPE/iX managed node.

The vt3k operation requires the HP Network Services (NS) node name of the remote HP 3000. However, nodes selected from the map are identified by the ARPA hostname. By default, the ARPA hostname of a selected node is truncated after the first dot (.). The first part of the ARPA hostname becomes the NS node name for the vt3k operation. This mechanism assumes that the truncated name identifies a node in the same NS domain as the management server because a fully qualified NS node name is unavailable.

NOTE You can configure the vt3k.conf file at any time. You do not have to exit the VPO GUI or restart any VPO services.

Chapter 4 165


Problems with ARPA Hostnames and NS Node Names

Two problems can occur when mapping ARPA hostnames to NS node names:

❏ Truncated ARPA host name differs from the NS node name.

❏ MPE/iX managed node belongs to a different NS domain.

Avoiding Problems with the VPO Mapping File

To avoid problems with ARPA hostnames and NS node names, VPO supports the mapping file below:

/etc/opt/OV/share/conf/OpC/mgmt_sv/vt3k.conf

This file can be a symbolic link to one of the following files:

❏ /etc/xnmvt3k.conf

❏ /etc/opt/OV/share/conf/xnmvt3-k.conf

The latter file is used by VPO for remote logins on HP 3000 systems through vt3k.

Chapter 4166


Resolving ARPA Hostname to NS Node Names

VPO resolves the ARPA host name to NS node name as follows:

1. Searches for the full ARPA hostname.

VPO searches for the first line in the vt3k.conf file that begins with a matching ARPA hostname. If it finds a matching name, VPO adds the NS node name in the second column of the vt3k operation.

2. Searches for the truncated ARPA hostname.

If VPO does not find a matching ARPA hostname in the vt3k.conf file, it repeats the search with only the first part of the ARPA host name (the part preceding the first dot). If it finds a matching name, VPO adds the NS node name in the second column to the vt3k operation.

3. Adds the truncated ARPA hostname.

If VPO does not find a matching name in the vt3k.conf file. or if the mapping file does not exist (the default case), VPO adds the truncated hostname to the vt3k operation. In this case, the name identifies a node in the same NS domain as the management server. A fully qualified NS node name is missing.

Chapter 4 167

About MPE/iX Managed NodesTypes of Libraries



On a HP 3000/900 platform running MPE/iX managed nodes, use the following include file:

OPCAPI.H.OVOPC



DCE Library libapixl.lib.ovopc libapixl.lib.ovopc libapixl.lib.ovopc

Libraries linked to the VPO library

N/A N/A N/A


info=”Ih”

link cap=pm,ia,ba,mr,ds;&

rl=libcinit.lib.sys;&

xl=opcapixl.lib

info=”Ih”



xl=opcapixl.lib

info=”Ih”



xl=opcapixl.lib


Chapter 4168


About the Makefiles




Makef.mpe-ix



Chapter 4 169


Chapter 4170

5 About Novell NetWare Managed Nodes

Chapter 5 171

About Novell NetWare Managed NodesIn this Chapter

In this ChapterThis chapter explains how to install and configure HP OpenView VantagePoint Operations (VPO) on Novell NetWare managed nodes.

Chapter 5172

About Novell NetWare Managed NodesInstallation Requirements

Installation RequirementsThis section explains VPO hardware and software requirements for Novell NetWare managed nodes.


Before installing VPO, make sure the Novell NetWare systems you select as managed nodes meet the following hardware requirements:

❏ Server

Novell NetWare Server 4.1x, 5, and 5.1

❏ Disk Space

• NetWare Server

10 MB on each NetWare server in the SYS: volume

• Software Depot

20 MB disk space for the software depot on the Windows 95/98/NT/2000 server.

❏ Additional RAM

• NetWare Server

7 MB additional free RAM on the NetWare server:

— 4 MB for the VPO agent

— 1 MB for TIRPC

— 0.5 to 2 MB for the NetWare Management Agent and XCONSOLE (optional)

At least 32 MB of server RAM is suggested for fair performance (depending on the OS version).

• VPO Agent

16 MB additional free RAM for the VPO agent if you are using NetWare SFT III file servers.

Chapter 5 173


Software Requirements for the Managed Nodes

Before installing VPO, make sure the following software is installed on Novell NetWare managed nodes:



❏ TIRPC

If it is not already present on the system, TIRPC is supplied with the VPO agent software. It is installed during VPO agent installation.

❏ TCP/IP Services

TCP/IP services must be configured (including name resolution), running, and started automatically.

❏ Network FRAMING Types

Network FRAMING types must be configured. Ethernet II frame type is required.

❏ CLIB.NLM

CLIB.NLM version 4.10 or higher must be installed.

❏ RogueWave TIRPC

If this product is missing VPO copies the required files during the installation process.

❏ SNMP Daemon (optional)

SNMP daemon must be configured, running, and started automatically if monitoring and trap interception is required.

❏ XCONSOLE (optional)

XCONSOLE.NLM must be installed and configured on each server only if you want remote access from the Management Server. XCONSOLE is part of Novell products like Flex-IP and NetWare/IP.

XCONSOLE must be configured and running. Remote console access (through telnet) must be allowed.

Chapter 5174


❏ Novell NMA

Novell NMA 2.1, 2.6 or 2.7 must be installed and configured. NMA is required for running default operations, but not for the VPO Agents. Novell NMA is a NetWare add-on product and can be purchased from Novell.

Software Requirements for the Depot Server

Before installing VPO, make sure the following software is installed on Novell NetWare depot server system:

❏ Microsoft Windows

Microsoft Windows 95, 98, NT or 2000 Operating System.

❏ Novell Client

Novell Client 32 for Windows must be installed on the system to be used as the depot server.

❏ IPX Transport Layer

The depot server must have NetWare connectivity to all NetWare servers where the VPO agent is to be installed. This means that each NetWare server must be accessible from the depot server by way of the IPX transport layer.

❏ PING.EXE

IP connectivity must be established throughout the network. You can use Windows PING.EXE to check that all NetWare servers are accessible from the depot server.

❏ FTP server (optional)

It is recommended that the depot server runs FTP server so the VPO agent package can be easily transferred from the VPO management server to the depot server.

Chapter 5 175

About Novell NetWare Managed NodesInstalling and De-installing Agents

Installing and De-installing AgentsThis section describes how to install and de-install Novell NetWare managed nodes.


When installing Novell NetWare managed nodes, follow these guidelines:

❏ Installation Logfiles

Each step of the installation is recorded in the logfile vpoinst.log on the NetWare depot server system.

The file is placed in the base directory of the VPO NetWare depot:

C:\Program Files\VPO

By default, the location can be changed during depot installation.

If you encounter problems during the installation, check this logfile for warnings and errors, and retry the installation.

❏ NetWare Directory Services (NDS)

The installation process creates the following file on each managed node:

SYS:/OPT/OV/BIN/OPC/INSTALL/NDSINFO

This file contains information about the position of the managed node in the NDS directory tree so that the VPO agent .NLMs can log in to NDS when they are started.

❏ Changed Configuration Files

Each configuration file on the NetWare server that is changed by the VPO installation process (for example, AUTOEXEC.NCF) is stored in the same directory with the extension.VPO in case you need to restore the old system. This is also done during VPO agent de-installation.

❏ VPO Event Interceptor and SNMPLOG.NLM

The VPO event interceptor and the Novell SNMPLOG.NLM cannot be used together. If you experience problems with the VPO event interceptor, make sure the SNMPLOG.NLM is not loaded. If you need SNMPLOG.NLM to report traps, disable the VPO event interceptor.

Chapter 5176


❏ UDP Echo Services

The VPO agent monitors the connection from the NetWare server to VPO management server by sending the UDP echo packages. The UDP echo service must, therefore, be enabled on the VPO management server. Verify that the echo service is not disabled in the following file:

/usr/adm/inetd.sec

The echo service is enabled if it is not listed in the inetd.sec file.

❏ UDP Protocol

If you use UDP protocol for agent-server communication, set the data array size to 2048 bytes or less. If the data array size is not set in this way, the communication fails for larger messages.

To set the size of data array, use the following in the in opcinfo file:

OPC_RPC_ARRAY_SIZE

When using the UDP protocol, the default value for data array size is 2048 bytes.

❏ PATH

PATH cannot be changed during runtime on Novell NetWare managed nodes. All actions, monitors, and commands must be either fully qualified or must reside in PATH. PATH must be set before the VPO agents are started.

❏ Unsupported VPO Agent Functionality

A subset of the VPO agent functionality is not supported or is implemented in a slightly different way on the NetWare platform.

• opcmsg

The opcmsg(1) command and opcmsg(3) API are not implemented.

• opcmon

The opcmon(1) command is not implemented. The opcmon(3) API is implemented.

• MSI

MSI on the managed node is not implemented.

Chapter 5 177


• Message Interceptor

The message interceptor is not implemented.

• Event Correlation

Event Correlation is not implemented.

• ANS

Advanced Network Security is not implemented.

• opcswitchuser

The opcswitchuser command is not implemented.

• Security Level

Only the regular level of security is implemented.

• Subagent Registration File

The subagent registration file is not encrypted:

SYS:/VAR/OPT/OV/CONF/OPC/AGTREG

• Tracing

Tracing cannot be switched on and off during agent operation.

• opcagt

The opcagt(1) command implementation differs from the implementation on other platforms. Only one instance of the opcagt command can be started on NetWare. Starting the opcagt(1) command starts the VPO agent service. It is a common practice in NetWare that a service opens its own virtual screen on the console screen. The operator uses this to control the service. The VPO agent opens a separate virtual screen on NetWare server console when started. By selecting the options in the menu of the VPO agent screen the operator is able to start and stop the VPO agents and query the agents status.

Chapter 5178


The following actions can be executed by the VPO agent processes:

Display VPO Agent Status Prints the status of VPO agents to the console.

Start VPO Agents Starts or re-initializes the other VPO Agent processes (equivalent to opcagt -start).

Stop VPO Agents Stops all VPO agent processes except for the message agent and the control agent functionality (equivalent to opcagt -stop).

Kill VPO Agents Stops all VPO agent processes (equivalent to opcagt -kill).

The console user interface is implemented with the standard NWSNUT services so that the standard NetWare console look-and-feel is achieved.

About the Installation Process

The process for installing the VPO agent software on Novell NetWare managed nodes differs from the standard installation process used for other platforms. The NetWare agent installation is semi-automated and depot-server-based.

The process for installing the VPO agent software on Novell NetWare managed nodes takes place in two locations:

❏ VPO Administrator GUI

• Adding the managed nodes to the VPO Node Bank.

• Installing the VPO agent software (ping only).

• Assigning and transferring templates to the managed nodes.

❏ NetWare Depot Server

• Running vpodepot on the depot server installs VPO installation software on Windows machine.

• Installing the VPO agent software on the managed nodes by running vpoinst.exe.

Chapter 5 179


Figure 5-1 on page 180 shows all installation steps made on the VPO management server and on the Novell NetWare depot server.

Figure 5-1 Installing the VPO Novell NetWare Agent Package

2. Transfervpodepot.exe to NW depot server(floppy or FTP)

NetWare Depot Server

NetWare server 1 NetWare server 2 NetWare server N

VPO Management Server

1. Admin GUI 1st part:- add NetWare managed nodes

4. Run vpoinst.exe:install/de-install agentsoftware on managednodes

- run Actions->Install for allmanaged nodes; selectAgent Software (ping only)

5. Admin GUI 2nd part:(template distribution):- run Actions->AssignTemplates for all managed nodes- run Actions->Install for allmanaged nodes; select everyoption except Agent Software

prepare NetWare agent3. Run vpodepot.exe:

depot server

running Windows 95/98/NTor 2000

Chapter 5180


To Install Agents

To install VPO agents on Novell NetWare managed nodes, follow these steps:

1. Make sure the Novell NetWare nodes are known to VPO and are accessible.

From the VPO administrator GUI, do this:

a. Add nodes to the VPO Node Bank.

Add your Novell NetWare managed nodes to the VPO Node Bank window.

b. Add nodes where you want to install the VPO agent.

Open the Install/Update VPO Software and Configuration window. Add the Novell NetWare managed nodes where you want to install the VPO agent software. Select [Agent Software] and click [OK].

This sends the ping command to the nodes.

NOTE The agent software package is not automatically copied to the NetWare depot server. This must be done manually as explained in the following step.

2. Copy the installation package to the NetWare depot server.

The installation package (vpodepot.exe) is located in the following directory on the management server:

/var/opt/OV/share/databases/OpC/mgd_node/vendor/\novell/intel/nw/A.07.00/RPC_SUN_TCP/vpodepot.exe

From the VPO Management Server, copy vpodepot.exe to depot server.

Chapter 5 181


3. Install the installation package on the NetWare depot server.

On the depot server, execute the vpodepot.exe file.

The InstallShield installation program, unless it is changed during the installation, creates the following directory:

C:\Program Files\VPO

InstallShield also adds the vpoinst.exe program to the Windows Start menu.

Figure 5-2 shows the file tree layout of the directory C:/ Program Files after vpodepot.exe has been executed.

Figure 5-2 File Tree Layout of the VPO NetWare Depot Server VPO

VPONovellAgent

OV

bin conf log tmp

vpoinst.exe

var

opt

etcopt

OV

bin include lib

system

Chapter 5182


4. Install the VPO agent software on the Novell NetWare managed nodes.

CAUTION Do not stop the VPO management server processes when installing the VPO agent software.

On the depot server, do this:

a. Execute the vpoinst.exe file.

In the initial dialog box, the following menu options are displayed:

Install Installs the VPO agent, and gives the additional option of backing up any already-installed VPO agent in the case of future reinstallation.

Deinstall Automatically de-installs the VPO agent from selected NetWare servers. It is possible to reinstall the previous version of the VPO agent, if there is one on the target server, and reinstate the previous version of the VPO agent.

The deinstallation procedure will restore system files to the same state as before the last installation of the VPO agent. If Restore old VPO version is selected, and an old VPO installation is available on the NetWare server, it will be restored.

Exit Immediately exits the procedure.

Next>> Proceeds to the next step.

b. Start the installation.

Select the Install option and click on Next>>.

The Select NetWare Nodes dialog box appears. The names of all available NetWare servers detected on the network are shown in the box on the left.

Chapter 5 183


c. Add NetWare nodes.

Use the following menu options:

Add>> Adds individual nodes to the list. You add a NetWare server by highlighting it and clicking Add>>. The server then appears in the box on the right.

Add all Adds all nodes to the list.

<<Remove Removes individual nodes from the list. You remove a NetWare server by highlighting it and clicking <<Remove. The server then appears in the box on the left.

Preserve old VPO Installation (if available) Saves the existing installation, if one exists, on the target servers for future restoration.

Only one version of VPO can be preserved using this option.

Install in batch mode Causes the installation of the VPO agent on the specified servers to proceed automatically, with only one prompt for specific VPO configuration which will be applied to all NetWare nodes. If you choose this option, all NetWare managed nodes specified must belong to the same management server.

If you choose this option, the next two windows will appear only once, and their contents will be used for all selected nodes.

Then click Next>> to proceed to the VPO Agent Configuration screen.

Chapter 5184


d. Select the user and group to be used for running actions on the managed node.

From the VPO Agent Configuration screen, you can select the user and group which will be used for running actions on the managed node.

NOTE It is possible to use an existing user with administrative rights. However, all applications in the Application Bank in the VPO management server must be updated to include the correct username and password.

In the Management Server field, you must enter the name of the management server which will be used to manage the VPO agent on the NetWare node.

e. Optional: Configure OPCINFO flags.

Click on Advanced Options to configure options in the OPCINFO file on the managed node.

The Advanced Options screen enables certain OPCINFO flags to be automatically distributed to all NetWare nodes without the need to manually update the configuration files.

In this screen you are presented with the following checkboxes:

OPC_IP_ADDRESS Adds OPC_IP_ADDRESS to the OPCINFO file.

OPC_RESOLVE_IP Adds the OPC_RESOLVE_IP to the OPCINFO file.

Edit OPCINFO Enables you to manually edit the contents of the OPCINFO file.

CAUTION Use the Edit OPCINFO option at your own risk.

Chapter 5 185


f. Copy the files to the NetWare server.

The installation checks if it is necessary and possible to create the user selected in the Configuration dialog box. If it is possible, the installation creates the requested user in the current context and set the administrative rights for that user. The installation also checks if the VPO agent is already running on the target node. If so, this node is skipped.

When the configuration is complete, the installation copies VPO modules and files to the NetWare server, with the old installation preserved, if you selected this option. The installation also prepares and copies OPCINFO and NDSINFO (for executing actions) to the appropriate directory.

5. Inform the management server that the agent software has been successfully installed on the new VPO managed nodes.

On the management server command line, enter the following:

/opt/OV/bin/OpC/opcsw -installed <node_name>

TIP At this point you should assign your templates to the NetWare managed nodes, and distribute the templates, actions, monitors, and commands. For more information about assigning and distributing templates, see the VPO Administrator’s Guide to Online Information.

After successfully installing the VPO agent, TIRPC is restarted, if necessary, and the VPO agent is started on the managed nodes.


If an older VPO agent package is no longer required and is not installed on any managed node, you can remove it by running the following:

/opt/OV/bin/OpC/install/rm_opc.sh novell/intel/nw \ <VPO_version>


Chapter 5186

About Novell NetWare Managed NodesAbout Preconfigured Elements

About Preconfigured ElementsThis section describes preconfigured templates, template groups, and applications used by VPO on Novell NetWare managed nodes.

One Preconfigured Template Group

VPO uses the following preconfigured template group:

❏ NetWare


Table 5-1 shows encapsulated logfiles and associated template used on Novell NetWare managed nodes. Use the default Logfile Encapsulator template only if the NetWare server variable AUTO START AFTER ABEND is set to a value higher than 0.

Table 5-1 Encapsulated Logfiles on Novell NetWare Managed Nodes


sys:\system\abend.log Abend logfile on NetWare, which is updated when an abend occurs

Abend log

Chapter 5 187



The VPO event interceptor is supported on Novell NetWare 4.1, 4.11, and 5.0 with NMA 2.1, 2.6 or 2.7.

There are two preconfigured templates for Novell NetWare:

❏ NetWare NMA 2.1/2.6 Threshold Traps

Filter traps originating from the NetWare NMA when one of the 24 NMA thresholds is exceeded.

❏ NetWare NMA 2.1/2.6 Traps

Filter the 378 traps that can be generated by the NMA module when an important event on the NetWare server occurs.


No Default Monitored Objects

No preconfigured monitors are available for Novell NetWare managed nodes.

Chapter 5188



This section describes the default applications in the following application groups:

❏ NetWare Tools

See “Monitoring Performance” on page 191.

❏ NetWare Config

See “About the NetWare Config Window” on page 191.

❏ NetWare Performance

See “About the NetWare Performance Window” on page 192.

About Novell NetWare Management Agent (NMA)

VPO for Novell NetWare can manage any NetWare server that is running the NetWare Management Agent (NMA). You must install the NMA on each server you want to manage.

You can obtain current and historical trend data and set alarm thresholds for trend parameters on NMA 2.1 NetWare file servers. You can also obtain information about the server’s configuration, NLM files, memory usage, adapters, network interfaces, disks, disk controllers, volumes, queues, users, connections, open files, and installed software.

For print servers, NMA 2.1 or later provides queue information that is not available for servers running older versions of NMA.

Chapter 5 189


About the NMA 2.1 Agent

The NMA provides real-time server performance information about the NetWare server alarms. These alarms are sent to the network and system management consoles. Or the alarms are processed locally by the VPO agent, and then forwarded to the VPO management console.

The NMA 2.1 agent is a set of NetWare agent NLMs that must be deployed on each NetWare server that you want to manage from the VPO console or Novell ManageWise console.

The NetWare agent NLMs include the following:

❏ NWTRAP.NLM

Over 400 traps with Novell NetExpert help text

❏ HOSTMIB.NLM

NetWare Server SNMP Host Resources MIB

❏ SERVINST.NLM

NetWare Server SNMP instrumentation

❏ NTREND.NLM

NetWare Server server-based trending

All NetWare servers from Novell, including all 3.x, 4.x and 5.x NetWare servers, SFT III servers, SMP servers, and Mirrored Servers, are supported by NMA. These agents are all provided and supported by Novell and can be purchased as a separate part numbers from the Novell ManageWise console.

Chapter 5190


Monitoring Performance

Novell NMA 2.1 Agent NLMs enable you to monitor performance statistics, such as CPU utilization and the number of users and connections, as well as memory and disk usage (including permanent and allocated memory, and dirty and allocated cache buffers).

Server faults are managed by monitoring the server’s key parameters. These conditions are monitored directly at the server and then passed to the VPO agent through SNMP traps.

You can enable NMA monitoring by configuring the following NMA configuration files on the NetWare server:

❏ NWTREND.INI

❏ TRAPTARG.CFG

Configuration of these files is not part of the VPO configuration and distribution framework.

In addition to the monitors provided by NMA, you can also create your own VPO templates to monitor any integer MIB variables supported by NMA. With these templates you can monitor NetWare server variables not monitored internally by the NMA.

About the NetWare Config Window

The following application icons are available by default in the NetWare Config window:

❏ Down & Reboot

❏ Down & Restart

❏ Restart NMA

NOTE You cannot start Down & Reboot and Down & Restart on NetWare SFT III systems.

The user opc_op (or any other user with administrator’s rights) can execute these application on the NetWare server.

Chapter 5 191


About the NetWare Performance Window

In the NetWare Performance window, the following application icons are available by default:

❏ Allocated Memory

❏ Cache Buffers

❏ Code & Data Memory

❏ CPU Utilization

❏ Logged-in Users

❏ Dirty Cache Buffers

❏ File Reads

❏ File Cache Hits

❏ File Writes

❏ File KReads

❏ File KWrites

❏ Free Redir Area

❏ KPackets Recvd #min

❏ KPackets Sent #min

❏ Memory Monitor

❏ Packets Recvd #min

❏ Packets Sent #min

❏ Queue Wait Time

❏ Ready Queue Jobs

❏ Ready Jobs (avg. KB)

❏ Total Packets Recvd

❏ Total Packets Sent

❏ Trend Graph

❏ Volume Free Space

Applications from this bank execute as user root on the server, and make SNMP GET calls to collect performance data from the NetWare server.

Chapter 5192


About the NetWare Tools Window

From the In NetWare Tools window, the user opc_op (or any other user with administrator’s rights) can execute all of the applications on the NetWare server except the Xconsole application, which is only used to run a NetWare console in an X window on the VPO console.

NOTE On NetWare SFT III systems, starting applications belonging to the NetWare Tools application group on the secondary IO Engine can cause problems if the secondary IO Engine is already in the state down. The secondary IO Engine may abend.

Chapter 5 193


Types of NetWare Tools Applications

In NetWare Tools window, the following application icons are available by default:

❏ Adapters

Determines I/O port address or interrupt conflicts by viewing a list of adapters.

Default: adapinfo <server_name>

❏ Boot the NetWare Server (NCF)

Stops and restarts (cold boots) the NetWare server, but does not exit the server.

Default: itodown.ncf

❏ Bound Protocols

Lists all the protocols bound to each network board in a server.

Default: protocls <server_name>

The number of packets sent and received over each protocol is also listed. By viewing the Bound Protocols object group, you can see which protocols have the most traffic.

❏ Cold Boot the NetWare Server (NCF)

Stops and restarts the NetWare server. This is done by removing DOS before exiting.

Default: itoreset.ncf <server_name>

❏ Connections

Monitors the status of users and user connections.

Default: conninfo <server_name>

The difference between the data returned by the Connections action and by the Users action is the emphasis of the Connection action on data relating specifically to connections. This emphasis enables you to determine how busy the server really is and which connections and users are the busiest.

Chapter 5194


❏ CPU Info

Returns information about devices including the CPU speed.

Default: cpuinfo <server_name>

❏ Disks

Enables you to get detailed information about the disk drives in a managed server.

Default: diskinfo <server_name>

Part of the detailed information provided by this action concerns the fault tolerance of a given disk partition. This information enables you to determine whether a hard disk is losing data integrity. A number in the redirected area indicates the number of data blocks that have been redirected to the Hot Fix™ Redirection Area to maintain data integrity.

If you are checking NetWare SFT III systems, the disks from both file servers are displayed.

❏ Display a File

Displays a file. That is, it copies the content of a file to standard output. This command is similar to the UNIX cat command.

Default: showfile <file_name>

You must start this command through the customized startup application so you can enter the additional parameters (for example, the name of an NLM).

❏ Installed Software (NW)

Displays those products that have been installed on the server using PINSTALL.

Default: instlsw <server_name>

PINSTALL is a product from Novell used to install software packages such as NMA on NetWare Servers.

Chapter 5 195


❏ Load/Unload an arbitrary NLM

Loads a NLM.

Default: itoload <nlm_name>

Unloads a NLM.

Default: itounload <nlm_name>

You can start arbitrary NLMs with the itoload and itounload commands. You must started these commands through a customized startup so you can enter the additional parameters.

❏ Memory Use

Monitors memory use.

Default: meminfo <server_name>

The memory-use action displays the following data:

❏ Alloc Memory Pool (KB)

❏ Cache Buffer (KB)

❏ Cache Movable Memory (KB)

❏ Cache Non-Movable Memory (KB)

❏ Code and Data Memory (KB) in NetWare 4.0 or higher

❏ Permanent Memory Pool (KB) in NetWare 3.11 and 3.12 only

❏ Mirrored Devices

Provides information about mirrored devices.

Default: mirrdevs <server_name>

❏ NCP Info

Provides statistics about NetWare Core Protocol (NCP).

Default: ncpinfo <server_name>

Chapter 5196


❏ NetWare Agent Actions

The VPO NetWare agent includes some preconfigured actions. Most of the preconfigured actions are located in the file VENDOR.NLM in the vendor file tree. This is different to the approach usually adopted on Unix-like platforms and on NT, where each action is stored in a separate script or is executable. However, calling conventions for NMA preconfigured actions are the same as for Unix-like platforms. Actions can be called from templates and from applications in the NetWare Application Bank window.

Some NetWare NCF scripts are implemented in addition to the actions provided in VENDOR.NLM.

NOTE For preconfigured actions that require an additional parameter <server_name>, enter the name of the NetWare server where the actions are being executed.

Types of NMA Applications

The NMA actions are described below.

NOTE Some actions take a while to execute. These actions are marked with an asterisk (*).

❏ Network Interfaces

Displays interface information for each network board in a server.

Default: netintrf <server_name>

Use Network Interfaces as a troubleshooting tool to determine why a user cannot log in to a file server. If the frame types are different, you can change the frame type in the user’s NET.CFG file, edit the user’s frame type to match the server’s frame type, and restart the user’s system.

Chapter 5 197


❏ NLM Files*

Determines which NLM files are currently loaded on the server. Includes NLM file version, release date and amount of memory used by the NLM.

Default: currnlms <server_name>

❏ ODI Info

Provides statistics about buffers for packets received and ECB requests.

Default: odiinfo <server_name>

❏ Open Files

Enables you to see which files are currently open, what volume they are reside in, who opened the files, and which connections are being used.

Default: openfils <server_name>

❏ Print Server

Displays information about printers and queues attached to print servers.

Default: presvinfo <server_name>

❏ Running Software*

Displays currently running NLMs and their memory usage.

Default: runsw <server_name>

❏ Queues

Monitors queues, jobs in the queues, and servers attached to the queues.

Default: quesinfo <server_name>

❏ Set Parameters*

Displays all settings for the server configuration.

Default: setparms <server_name>

This is the same information as is returned from the console SET command.

Chapter 5198


❏ Trend Parameters*

Displays information on the current trend parameters.

Default: presvinfo <server_name>

❏ System Summary

Returns information about the server name and uptime, as well as a description of the operating system.

Default: sysumary <server_name>

❏ Users

Monitors user activity to determine, amongst other things, the optimum server shutdown time:

Default: userinfo <server_name>

❏ Volume

Enables you to determine the exact amount of space available on every volume in the server.

Default: volinfo <server_name>

NetWare server disk storage space is divided into volumes. The Volume action enables you to view information about the volumes in a server running NMA software (for example, size, free space, how the volumes are distributed across the disks, and who is using the space.

❏ XCONSOLE

Opens a NetWare virtual terminal connection to node.

This application requires only the remote console password (which may be different from the opc_op password).

For NetWare SFT III servers, add another XCONSOLE application that calls the primary IO Engine rather than the MS Engine as in the default XCONSOLE application.

NOTE The user name for the Xconsole application is xconsole. This is not a NetWare user name. It is only present in the VPO database as a warning that the password for the remote console access may be different from the user opc_op password.

Chapter 5 199

About Novell NetWare Managed NodesConfiguration Distribution and Update

Configuration Distribution and UpdateFor Novell NetWare managed nodes, the platform selector and architecture identifiers is the following:

novell/intel/nw






/var/opt/OV/share/databases/OpC/mgd_node/customer\/novell/intel/nw/actions/*

Monitoring scripts and programs used by the monitoring agent and logfile encapsulator

/var/opt/OV/share/databases/OpC/mgd_node/customer\/novell/intel/nw/monitor/*


/var/opt/OV/share/databases/OpC/mgd_node/customer\/novell/intel/nw/cmds/*

Chapter 5200

About Novell NetWare Managed NodesConfiguration Distribution and Update





Table 5-3 Temporary Directories for Distributed Scripts and Programs on Managed Nodes


Temporary Directory

Intel 486 or higher Novell NetWare sys:/var/opt/OV/tmp/OpC/bin/actionssys:/var/opt/OV/tmp/OpC/bin/cmdssys:/var/opt/OV/tmp/OpC/bin/monitor


Managed Node

Operating System


Intel 486 or higher

Novell NetWare

sys:/var/opt/OV/tmp/OpC/bin/\actions

Administrator (full access)

sys:/var/opt/OV/tmp/OpC/bin/\cmds


sys:/var/opt/OV/tmp/OpC/bin/\monitor


Chapter 5 201

About Novell NetWare Managed NodesOrganization of Managed Nodes

Organization of Managed Nodes Figure 5-3 shows how VPO software is organized on Novell NetWare managed nodes.

Figure 5-3 VPO Software on Novell NetWare Managed Nodes

During installation, VPO creates the opc_op account, which has the same security level as the user ADMIN. The opc_op account is a normal user account used to execute applications.

Location of Files

On Novell NetWare managed nodes, files are located as follows:


SYS:/var/opt/OV/tmp/OpC


SYS:/var/opt/OV/conf/OpC

BIN CONF TMP LOG

SYS:OPT/OV

OPC OPC OPCOpC

INSTALL

LIB

<lang> BIN CONF

B

SYS:VAR/OPT/OV

INCLUDE

NLSB

bin

OpC

UTILS

B


Key:

CONTRIB

OpC

Chapter 5202



During the installation of VPO agents, user OPC_OP and group OPC_GRP are added into NDS. User OPC_OP is used to run applications on the managed node. If you want, you can remove this user from NDS.

CAUTION If you remove OPC_OP, all applications in the Application Bank must be reconfigured to use an existing user with sufficient rights.

On Novell NetWare managed nodes, the VPO entry in the User Manager for Domains includes the following fields:

User Name OPC_OP

Encrypted Password Must be entered manually. Use NETADMIN or NWADMIN.

User-ID N/A.

Group-ID N/A

Description Special user with rights equivalent to NetWare system administrator ADMIN.

Home Directory Not set.

Login Shell None assigned. NetWare works with login scripts.


During the agent software installation, VPO adds the agent startup command OPCAGT.NCF to the AUTOEXEC.NCF file.

The following resources are changed during installation:

SYS:/SYSTEM/AUTOEXEC.NCF

The following changes are made to this resource:

OPCAGT.NFC Added to invoke the VPO agent for NetWare software if this command is not already present in this file.

Chapter 5 203


Table 5-5 shows the TIRPC modules installed by VPO on Novell NetWare managed nodes.

Table 5-5 TIRPC modules installed by VPO on Novell NetWare

Module Version

local_nd.nlm 1.10y

lwpnfsd.nlm 1.10y

netdir.nlm 1.10y

rpcbstub.nlm 1.10y

rpcinfo.nlm 1.10y

rpcstart.ncf N/A

rpcstop.ncf N/A

spx_nd.nlm 1.10y

tcp_nd.nlm 1.10y

tirpc.nlm 1.10y

Chapter 5204

About Novell NetWare Managed NodesAbout APIs

About APIs

NOTE The VPO commands and APIs opcmon(1), opcmack(1), and opcmsg(1) are not supported for Novell NetWare managed nodes.

VPO provides a set of application program interfaces (APIs) for Novell NetWare agents. These APIs facilitate interprocess communication (in particular, the parent-child relationship) between VPO agents and the custom NLMs.

Types of APIs

VPO provides the following APIs on Novell NetWare managed nodes:

OVnlm_init() Must be the first function called in the main() function of a VPO-enabled NetWare Loadable Module (NLM). This function initializes the VPO-related variables and returns a handle that must be used in all subsequent calls in this NLM.

OVnlm_exit() Must be used to terminate the execution of VPO-enabled NLM instead of the usual exit() function. This function is required to inform the parent VPO Agent NLM that the custom NLM has finished, and to provide exit code to the parent.

Chapter 5 205

About Novell NetWare Managed NodesAbout APIs

Examples of VPO-enabled NLMs

An example of an action, HELLO.NLM, is shown below. This action is executed by the VPO action agent and the output is captured as a VPO annotation.

#define OPC_NLM #include “opcnwapi.h”main( int argc, char **argv ){int handle;

OVnlm_init( argc, argv, &handle );printf( “%s: Hello world!\n”, argv[0] );OVnlm_exit( handle, 0 );

}

Another example of an action is contained in the following file on the management server:

/opt/OV/OpC/examples/progs/nwopcnlm.c

Chapter 5206

About Novell NetWare Managed NodesTypes of Libraries



On an Intel 486 or higher platform with Novell NetWare managed nodes, use the following include file:

SYS:.opt/OV/include/opcapi.h,opcnwapi.h



EZ-RPC Library libopc.lib libopc.lib libopc.lib


No libraries linked. libov.lib libov.lib


-DOPC_NW -DNW

-DCSM_ONC

-DOPC_NW -DNW

-DCSM_ONC

-DOPC_NW -DNW

-DCSM_ONC

Description libopc.lib is only used as archive library for API developers. It is not used at runtime.

libopc.lib and libov.lib are only used as archive libraries for API developers. They are not used at runtime.

libopc.lib and libov.lib are only used as archive libraries for API developers. They are not used at runtime.

Chapter 5 207

About Novell NetWare Managed NodesTypes of Libraries

About the Makefile




Makef.nw



Chapter 5208

6 About OpenView Performance Agent for HP-UX and Sun Solaris

Chapter 6 209

About OpenView Performance Agent for HP-UX and Sun SolarisIn this Chapter

In this Chapter

This chapter describes HP OpenView Performance Agent (OVPA).

NOTE HP OpenView VantagePoint Performance Agent (VPPA), formerly MeasureWare Agent, has been renamed to HP OpenView Performance Agent (OVPA). However, the software components and process names operationally remain MeasureWare Agent (MWA).

Chapter 6210

About OpenView Performance Agent for HP-UX and Sun SolarisAbout Other Platforms

About Other PlatformsFor the following platforms, OVPA is provided on separate installation media (CD-ROMs) and is not deployable from VPO.

❏ IBM AIX

❏ Siemens-Nixdorf SINIX RM/Reliant

❏ Tru64 UNIX

Each platform has its own installation and configuration guide.

NOTE For list of managed node platforms and operating system versions that are supported by OVPA, see the VPO Installation Guide for the Management Server.

Chapter 6 211

About OpenView Performance Agent for HP-UX and Sun SolarisWhat OVPA Does

What OVPA DoesHP OpenView Performance Agent (OVPA) collects, summarizes, time stamps, and detects alarm conditions on current and historical resource data across your system. It provides performance, resource, and end-to-end transaction response time measurements, and supports network and database measurement information.

Integrating Data with OVPA

Data collected outside OVPA can be integrated using data source integration (DSI) capabilities. For example, network, database, and your own application data can be integrated through DSI. The data is treated the same as data collected by OVPA. All DSI data is logged, time stamped, and can be alarmed on.

Analyzing Data with OVPA

All of the data collected or received by OVPA can be analyzed using spreadsheet programs, HP analysis tools such as HP OpenView Performance Manager, or third-party analysis products. HP OpenView Performance Manager is optionally provided on separate media.

Logging Data with OVPA

The comprehensive data logged by OVPA enables you to do the following:

❏ Characterize the workloads in the environment.

❏ Analyze resource usage for load balancing.

❏ Perform service-level management based on transaction response time.

❏ Perform capacity planning.

❏ Respond to alarm conditions.

❏ Solve system management problems before they arise.

Chapter 6212

About OpenView Performance Agent for HP-UX and Sun SolarisWhat OVPA Does

Customizing OVPA

OVPA gathers comprehensive and continuous information on system activity without imposing significant overhead on the system. Its design offers considerable opportunity for customizing. You can accept default configurations or set parameters to collect data for specific conditions.

Trying HP OpenView GlancePlus

HP OpenView GlancePlus (GlancePlus) provides immediate performance information about your system. It lets you easily examine system activities, identify and resolve performance bottlenecks, and tune your system for more efficient operation. With GlancePlus, you save time, your users are more productive, and your business applications run more smoothly.

To maintain compatibility with any existing installations of GlancePlus, OVPA installs a 60 day trial version of GlancePlus. If you already have a production version of GlancePlus installed, the trial version included with the OVPA deployable package will upgrade your current production version. If there is no current production version of GlancePlus installed, GlancePlus will time out 60 days after installing the software. Contact your HP sales representative to receive a production version of GlancePlus if you intend to use it for more than 60 days.

Chapter 6 213

About OpenView Performance Agent for HP-UX and Sun SolarisInstallation Requirements

Installation RequirementsThis section describes the system requirements for installing OVPA for HP-UX or Sun Solaris with VPO on an HP-UX or Sun Solaris managed node.

NOTE For list of managed node platforms that are supported by OVPA, as well as the requirements for installing VPO on the management server, see the VPO Installation Guide for the Management Server.

OVPA is language-independent and can run on any supported system. However, manuals are provided in both English and Japanese editions. Please refer to “About Documentation” on page 227 for the lists of manual names.

NOTE OVPA and the embedded performance component can co-exist on the same system. However, if you do not require the embedded performance component, you can disable it. See the secion on troubleshooting in the VPO Administrator’s Reference Volume I for details.

Chapter 6214



Before installing OVPA, make sure your HP-UX or Sun Solaris platform meets the following hardware requirements.

Hardware Requirements for HP-UX

OVPA for HP-UX runs on HP Enterprise Servers and Technical Workstations.

Hardware Requirements for Sun Solaris

OVPA for Sun Solaris runs on the following hardware platforms:

❏ Sun4c

❏ Sun4d

❏ Sun4m

❏ Sun4u

❏ E10000

Chapter 6 215



Before installing OVPA, make sure your HP-UX or Sun Solaris platform meets the following software requirements.

Software Requirements for HP-UX

OVPA for HP-UX requires the following software:


OVPA for HP-UX version C.03.50 requires releases 10.20, 11.00, or 11.11 of the HP-UX operating system.

Software Requirements for Sun Solaris

OVPA for Sun Solaris version C.03.45 requires the following software:


OVPA for Sun Solaris requires the following operating environments: Sun Solaris 2.6, 7, or 8, or Sun Solaris 8 Maintenance Update 10/00. It is recommended that you have at least the “End User System Support” level of operating system installed on your Sun system.

If the “Core System Support” level of operating system is installed on your Sun system, you will have to install the following two operating system packages:

• SUNWlibC

• SUNWlibms

Chapter 6216


❏ Communication Protocols

The following communication protocols are supported on OVPA for Sun Solaris:

• NCS 1.5.1

• DCE 1.1, 2.2, 3.1

During the installation process, OVPA for Sun Solaris automatically selects the OVPA communication protocol configuration (NCS or DCE) to match the protocol configuration in use by the VPO agent, if this agent is present on the system. If VPO agent is not found on the system, DCE communication protocol is deployed by default.

For more information, see the HP OpenView Performance Agent for Sun Solaris Systems: Installation & Configuration Guide.

Chapter 6 217


Disk Space Requirements

On both HP-UX and Sun Solaris, OVPA installs in the following directory:

/opt/perf/

OVPA creates its log and status files in the following directory:

/var/opt/perf/

For a description of how to use the parm file to configure logfile data storage for OVPA, see the HP OpenView Performance Agent for UNIX: User’s Manual.

When installing OVPA, follow the disk space requirements listed in Table 6-1:

NOTE OVPA for Sun Solaris only

If you do not have enough space in your /opt/perf and/or /var/opt/perf directories, you can install OVPA on symbolic links. For more information, refer to the HP OpenView Performance Agent for Sun Solaris Systems: Installation & Configuration Guide.

Table 6-1 Required Disk Space

Directory Disk Space

/opt/OV/a 97 MB

/opt/perf/b 30 MB

/var/opt/OV/a 194 MB

/var/opt/perf/c 40 MB

Total 361 MB

a. Required during product installation.b. Required for running OVPA.c. For OVPA product use - log and status files.

Chapter 6218

About OpenView Performance Agent for HP-UX and Sun SolarisInstalling and De-installing OVPA

Installing and De-installing OVPAThis section describes how to install and de-install OVPA on HP-UX or Sun Solaris managed nodes.

Installing OVPA

You can install OVPA on HP-UX or Sun Solaris managed nodes using the standard or manual installation methods.

TIP For additional installation and configuration information, see the HP OpenView Performance Agent for HP-UX: Installation & Configuration Guide and the HP OpenView Performance Agent for Sun Solaris Systems: Installation & Configuration Guide.

To Install OVPA with Standard Installation

To install OVPA on a HP-UX or Sun Solaris managed node using standard installation, follow these steps:

1. Start the VPO administrator GUI.

2. Install the VPO agent software on the managed node where you want to run OVPA. See the VPO Administrator’s Reference Volume I for more information.

3. In the VPO Node Bank, select the node where you want to install OVPA.

4. From the menu bar, select the following:

Actions: Subagents -> Install/Update…

The Install / Update Subagents window opens.

5. In the Install / Update Subagents window, select OV Performance Agent and the nodes on which you want to install or update the agent.

6. Click [Preview] to see which software packages will be installed on each node.

Chapter 6 219


7. Click on [OK] to install the software package.

To Install OVPA Manually

To install OVPA on an HP-UX or Sun Solaris managed node without using the management server, follow these steps:

1. Make sure the /tmp directory of the managed node contains at least 37 MB of free space.

2. Copy the appropriate ovpa_pkg.Z and ovpa_inst files from the management server to the /tmp directory of the managed node:

• HP-UX 10.20

/var/opt/OV/share/databases/subagent/VP_Perf_Agt\/hp/s[7|8]00/hp-ux10/C.03.50/ovpa_pkg.Z

/var/opt/OV/share/databases/subagent/VP_Perf_Agt\/hp/s[7|8]00/hp-ux10/C.03.50/install/ovpa_inst

• HP-UX 11.0

/var/opt/OV/share/databases/subagent/VP_Perf_Agt\/hp/pa-risc/hp-ux11/C.03.50/ovpa_pkg.Z

/var/opt/OV/share/databases/subagent/VP_Perf_Agt\/hp/pa-risc/hp-ux11/C.03.50/install/ovpa_inst

• HP-UX 11.11

/var/opt/OV/share/databases/subagent/VP_Perf_Agt\/hp/pa-risc/hp-ux11/C.03.50/ovpa_pkg.Z.B.11.11

/var/opt/OV/share/databases/subagent/VP_Perf_Agt\/hp/pa-risc/hp-ux11/C.03.50/install/ovpa_inst

• Sun Solaris

/var/opt/OV/share/databases/subagent/VP_Perf_Agt\/sun/sparc/solaris/C.03.45/ovpa_pkg.Z

/var/opt/OV/share/databases/subagent/VP_Perf_Agt\/sun/sparc/solaris/C.03.45/install/ovpa_inst

3. To install the files, enter the following command on the managed node:

/tmp/ovpa_inst

Chapter 6220


De-installing OVPA

You can de-install OVPA on HP-UX or Sun Solaris managed nodes using the standard or manual de-installation methods.

To De-install OVPA with Standard De-installation

To de-install OVPA from a managed node using the standard installation method, follow these steps:

1. In the VPO Node Bank, select the node from which you want to de-install OVPA.

2. From the menu bar, select the following:

Actions Subagents -> Deinstall…

3. In the Deinstall Subagents window, select OV Performance Agent.

4. Click [OK] to de-install the software.

The OVPA executable files are removed from the managed node. Configuration files and data files are not removed.

Chapter 6 221


To De-install OVPA Manually

To de-install OVPA from a managed node using the manual installation method, follow these steps:

1. Copy the appropriate ovpa_inst file from the directories listed in “To Install OVPA Manually” on page 220 to the /tmp directory of the managed node.

2. To remove the files, enter the following command on the managed node:

/tmp/ovpa_inst REMOVE

NOTE The ovpa_inst script does not remove HP OpenView GlancePlus from the system. To remove GlancePlus, run the one of the following scripts, depending on your preferred mode:

❏ Motif Mode Interface

/opt/perf/bin/gpm.remove

❏ Character Mode Interface

/opt/perf/bin/glance.remove

Chapter 6222

About OpenView Performance Agent for HP-UX and Sun SolarisAbout Preconfigured Elements

About Preconfigured ElementsThis section describes preconfigured templates, template groups, and applications used by OVPA on HP-UX and Sun Solaris managed nodes.

Types of Applications

There is one application group named OV Performance. You can select the following applications from the Application Group:OV Performance window.

Table 6-2 Applications in Group: OV Performance

Application Description

Check alarmdef Check the syntax of the OVPA alarmdef file (utility -xc).

Check parm Check the syntax of the OVPA parm file (utility -xp).

Config alarmdef Edit the OVPA alarmdef file and check the syntax (utility -xc).

Config parm Edit the OVPA parm file and check the syntax (utility -up).

Config perflbd.rc Edit the /var/opt/perf/perflbd.rc file.

Config ttd.conf Edit the /var/opt/perf/ttd.conf file.

List Processes List the active performance tool processes (perfstat -p).

List Versions List the version numbers for key performance tool files (perfstat -v).

Reactivate alarmdef Reinitialize OVPA alarmgen process (mwa restart alarm).

Restart PA Servers Reinitialize OVPA server processes (mwa restart server).

Restart Perf Agt Reinitialize all OVPA processes (mwa restart).

Start extract Start the OVPA extract program.

Start Perf Agt Start all OVPA processes (mwa start).

Start pv Start the OpenView Performance Manager monitoring tool.

Start pvalarmd Start the OpenView Performance Manager pvalarmd process (pvalarmd.start).

Start utility Start the OVPA utility program.

Chapter 6 223


Types of Templates

OVPA has the following template groups:

❏ OpenView Performance

• OV Performance Agent

• OV Performance Manager

About the OV Performance Agent Template Group

You can select the following OV Performance Agent templates from the Message Source Templates window:

❏ Message templates

❏ Logfile templates

❏ Monitor templates

Table 6-3 shows the message templates in the OV Performance Agent template group.

Stop Perf Agt Stop all OVPA processes except for ttd (mwa stop).

Stop pvalarmd Stop the OpenView Performance Manager pvalarmd process (pvalarmd.stop).

Tail Status Files Display last few lines of performance tool status files (perfstat -t)

Table 6-2 Applications in Group: OV Performance

Application Description

Table 6-3 OV Performance Agent: Message Templates

Template Description

opcmsg for OV Performance

Interception of messages from OpenView Performance Agent.

Chapter 6224


Table 6-4 shows the logfile templates in the OV Performance Agent template group.

Table 6-5 shows the monitor templates in the OV Performance Agent template group.

About the OV Performance Manager Template Group

You can select the following OV Performance Manager templates from the Message Source Templates window:

❏ Logfile templates

❏ Monitor templates

Table 6-4 OV Performance Agent: Logfile Templates


status.alarmgen Retrieves messages from the alarmgen/agdbserver status file.

status.mi Retrieves messages from the midaemon status file.

status.perflbd Retrieves messages from the perflbd status file.

status.rep_server Retrieves messages from the rep_server status file.

status.scope Retrieves messages from the scopeux status file.

status.ttd Retrieves messages from the ttd status file.

Table 6-5 OV Performance Agent: Monitor Templates


agdbserver Sends a message if the agdbserver process is not running.

alarmgen Sends a message if the alarmgen process is not running.

midaemon Sends a message if the midaemon process is not running.

perflbd Sends a message if the perflbd process is not running.

rep_server Sends a message if the number of rep_server processes running does not match the number configured in the perflbd.rc file.

scopeux Sends a message if the scopeux process is not running.

ttd Sends a message if the ttd process is not running.

Chapter 6 225


Table 6-6 shows the logfile templates in the OV Performance Manager template group.

Table 6-7 shows the monitor templates in the OV Performance Manager template group.

Table 6-6 OV Performance Manager: Logfile Templates


status.pv Retrieves messages from the pv status file.

status.pvalarmd Retrieves messages from the pvalarmd/pvmapd status file.

Table 6-7 OV Performance Manager: Monitor Templates


pvalarmd Sends a message if the pvalarmd process is not running.

Chapter 6226

About OpenView Performance Agent for HP-UX and Sun SolarisAbout Documentation

About DocumentationThe VPO management server includes OVPA documentation in the following languages:

❏ English

See “Types of English-language Documentation” on page 228.

See also the directory /opt/perf/paperdocs/mwa/C on the managed node for additional documents shipped with OVPA.

❏ Japanese

See “Types of Japanese-language Documentation” on page 230.

NOTE OVPA for Sun Solaris systems is not localized. The documentation is available in the English language only.

Downloading and Viewing Documentation

All OVPA documentation files are in Adobe Acrobat 4.0 Portable Document Format (PDF). You can view these file on the web with Adobe Acrobat Reader 3.0 or higher. If the Acrobat Reader is not already installed in your Web browser, you can download it at no charge from the Adobe web site:

http://www.adobe.com

While viewing a document in the Acrobat Reader, you can print a single page, a group of pages, or the entire document.

Chapter 6 227


Types of English-language Documentation

Table 6-8 describes the English-language documentation provided with the VPO management server.

Table 6-8 English-language Documents

Location OS File Name Title

/opt/OV/doc/C/VP_Perf_Agt/hp/C.03.50

HP-UX arm2api.pdf Application Response Measurement 2.0 API Guide

metrics.pdf HP OpenView Performance Agent for HP-UX: Dictionary of Operating System Performance Metrics

mwadsi.pdf HP OpenView Performance Agent for UNIX: Data Source Integration Guide

mwainst.pdf HP OpenView Performance Agent for HP-UX 10.20 and 11: Installation & Configuration Guide

mwausers.pdf HP OpenView Performance Agent for UNIX: User’s Manual

tyt2.pdf HP OpenView Performance Agent and GlancePlus for UNIX: Tracking Your Transactions

Chapter 6228


/opt/OV/doc/C/VP_Perf_Agt/sun/C.03.45

Sun Solaris

arm2api.pdf Application Response Measurement 2.0 API Guide

metsun.pdf HP OpenView Performance Agent for Sun Solaris Metrics Definitions

metsun.txt HP OpenView Performance Agent for Sun Solaris Metrics Definitions

mwadsi.pdf HP OpenView Performance Agent for UNIX: Data Source Integration Guide

mwainst.pdf HP OpenView Performance Agent for Sun Solaris Systems: Installation & Configuration Guide

mwausers.pdf HP OpenView Performance Agent for UNIX: User’s Manual

tyt.pdf HP OpenView Performance Agent and GlancePlus for UNIX: Tracking Your Transactions

Table 6-8 English-language Documents

Location OS File Name Title

Chapter 6 229


Types of Japanese-language Documentation

Table 6-9 describes the Japanese-language documentation provided with the VPO management server.

NOTE OVPA for Sun Solaris systems is not localized. The documentation is available in the English language only.

Table 6-9 Japanese-language Documents

Location File Name Title

/opt/OV/doc/japanese/VP_Perf_Agt/hp/C.03.50

mwainst_ux11.pdf HP OpenView Performance Agent for HP-UX: Installation & Configuration Guide

mwausers_ux.pdf HP OpenView Performance Agent for UNIX: User’s Manual

mwadsi_ux.pdf HP OpenView Performance Agent for UNIX: Data Source Integration Guide

tyt2_ux.pdf HP OpenView Performance Agent for UNIX: Tracking Your Transactions

Chapter 6230

7 About Sequent DYNIX Managed Nodes

Chapter 7 231

About Sequent DYNIX Managed NodesIn this Chapter

In this ChapterThis chapter explains how to install and configure HP OpenView VantagePoint Operations (VPO) on Sequent DYNIX managed nodes.

Chapter 7232

About Sequent DYNIX Managed NodesInstallation Requirements

Installation RequirementsThis section explains VPO hardware and software requirements for Sequent DYNIX managed nodes.


Before installing VPO, make sure the Sequent DYNIX systems you select as managed nodes meet the following hardware requirements:

❏ Disk Space


❏ HPFS Partition

VPO agent must be installed on an HPFS partition. FAT partitions are not supported for VPO agent installation and operation.


None

❏ Additional RAM

4 MB


Before installing VPO, make sure the following software is installed on Sequent DYNIX managed nodes:




For a list of kernel parameters, see the VPO Administrator’s Reference Volume I. You can check and change the system parameters using the menu tool.

❏ Sequent LAN

Sequent local area network product ptx/LAN version 4.0.1. or higher.

Chapter 7 233

About Sequent DYNIX Managed NodesInstallation Requirements

❏ Sequent TCP/IP

Sequent TCP/IP product ptx/TCP/IP version 4.0.3 or higher.

❏ Gradient NCS 1.5.1 NckNidl

If NCS is not found on the managed node, VPO installs llbd and lb_admin during the VPO agent software installation.

Chapter 7234

About Sequent DYNIX Managed NodesInstalling and De-installing Agents

Installing and De-installing AgentsThis section describes how to install and de-install Sequent DYNIX managed nodes.


When installing Sequent DYNIX managed nodes, follow these guidelines:


The name of the management server must be known to the managed node. You must register the name of the management server on the name server or in the local host table:

/etc/hosts

You can verify this by using the nslookup command.


The VPO agent software is installed on the /opt file tree. An empty /opt file tree is created during installation of the Sequent DYNIX/ptx operating system. By default, this file tree is positioned on the root file system. If there is not enough space for the installation of the VPO agents, create a symbolic link before installing VPO.

For example, if /bigdisk is a local file system with enough free space, you would create the symbolic link as follows:


ln -s /bigdisk/OV /opt/OV

In a cluster environment, make sure that /bigdisk is accessible from all cluster clients. That is, make sure that it is mounted from all client nodes. For example, the local file system /bigdisk on a cluster client must be mounted to exported file system /bigdisk on cluster server.

Chapter 7 235

About Sequent DYNIX Managed NodesInstalling and De-installing Agents

Installing Agents



/tmp/pkgadd.log



If errors occur during the de-installation, check the local de-installation logfile:

/tmp/pkgrm.log

Chapter 7236

About Sequent DYNIX Managed NodesAbout Preconfigured Elements

About Preconfigured ElementsThis section describes preconfigured templates, template groups, and applications used by VPO on Sequent DYNIX managed nodes.



DYNIX/ptx


Table 7-1 shows encapsulated logfiles and associated template used on Sequent DYNIX managed nodes.

Table 7-1 Encapsulated Logfiles on Sequent DYNIX/ptx Managed Nodes


/usr/lib/cron Cron logfile Cron (DYNIX/ptx)

/usr/adm/messages OS messages OS Msgs (DYNIX/ptx)

/usr/adm/sulog Switch user logfile Su (DYNIX/ptx)

/var/adm/wtmp History of logins Logs (DYNIX/ptx)

/usr/adm/critical Syslog daemon error logfile

Syslog Error (DYNIX/ptx)

/usr/spool/adm/syslog Syslog daemon logfile Syslog (DYNIX/ptx)

/usr/spool/lp/logs/lpsched

Printer services logfile Lp Serv (DYNIX/ptx)

/usr/spool/lp/remotelp Remote printer services log

Rlp Serv (DYNIX/ptx)

/usr/spool/lp/logs/requests

Printer requests logfile Lp Req (DYNIX/ptx)

Chapter 7 237

About Sequent DYNIX Managed NodesAbout Preconfigured Elements


The VPO event interceptor is not supported on Sequent DYNIX/ptx managed nodes.


Table 7-2 describes the default monitored objects used by VPO on Sequent DYNIX managed nodes.






95% 2


90% 10


0.5 5

MailQueue Length


30 2


sendmail Number of executing instances of sendmail.

0.5 5



Chapter 7238

About Sequent DYNIX Managed NodesDistributing Scripts and Programs

Distributing Scripts and ProgramsFor Sequent DYNIX managed nodes, the platform selector and architecture identifier is the following:

sequent/intel/dynix






/var/opt/OV/share/databases/OpC/mgd_node/customer\/sequent/intel/dynix/actions/*


/var/opt/OV/share/databases/OpC/mgd_node/customer\/sequent/intel/dynix/monitor/*


/var/opt/OV/share/databases/OpC/mgd_node/customer\/sequent/intel/dynix/cmds/*

Chapter 7 239

About Sequent DYNIX Managed NodesDistributing Scripts and Programs





Temporary Directory

Intel 486 or higher Sequent DYNIX/ptx

/var/opt/OV/tmp/OpC/bin/actions/var/opt/OV/tmp/OpC/bin/cmds/var/opt/OV/tmp/OpC/bin/monitor

Chapter 7240

About Sequent DYNIX Managed NodesOrganization of Managed Nodes

Organization of Managed NodesFigure 7-1 shows how VPO software is organized on Sequent DYNIX/ptx managed nodes, based on the typical SVR4 platforms.

Figure 7-1 VPO Software on Sequent DYNIX/ptx Managed Nodes

Location of Files

On Sequent DYNIX/ptx managed nodes, files are located as follows:


/var/opt/OV/tmp/OpC



bin conf tmp log

/opt/OV

OpC OpC OpCOpC

liblocale

<lang>

bin conf

/var/opt/OV

include

LC_MESSAGES

B

B

bin

OpC

utils

B


Key:

contrib

OpC

install

Chapter 7 241





The default VPO operator appears in the following directory on Sequent DYNIX/ptx managed nodes:

/etc/passwd


User Name opc_op






Login Shell /bin/sh


The default VPO operator group appears in the following directory on Sequent DYNIX/ptx managed nodes:

/etc/group


Group Name opcgrp



Users opc_op


Chapter 7242



VPO makes changes in the following system resource files during installation:

/etc/passwd/etc/shadow (if present) Entry for the default VPO operator and

Protected Password Database (if present).

/etc/group Group entry for the default VPO operator

/etc/init.d/opcagt VPO startup and shutdown script.

/etc/rc0.d Creates the K07opcagt file.

/etc/rc2.d Creates the S93opcagt file.

/etc/init.d/ncs NCS startup and shutdown script.

/etc/rc0.d Creates the K52ncs file.

/etc/rc2.d Creates the S76ncs file.

Chapter 7 243

About Sequent DYNIX Managed NodesTypes of Libraries



On an Intel 486 or higher platform with Sequent DYNIX/ptx managed nodes, use the following include file:




NCS Library libopc.so libopc.so libopc.so


/usr/lib/libnck.a

/usr/lib/libinet.so

/usr/lib/libnsl.so

/usr/lib/librpc.so

/usr/lib/libsec.a

/usr/lib/libseq.a

/usr/lib/libsocket.so

/usr/coff/lib/libintl.a

/usr/lib/libnck.a

/usr/lib/libinet.so

/usr/lib/libnsl.so

/usr/lib/librpc.so

/usr/lib/libsec.a

/usr/lib/libseq.a



/usr/lib/libnck.a

/usr/lib/libnsl.so

/usr/lib/librpc.so

/usr/lib/libsec.a

/usr/lib/libseq.a




-lopc -lnsp -lsocket




Chapter 7244


About the Makefile




Makef.ptx



Chapter 7 245


Chapter 7246

8 About SGI IRIX Managed Nodes

Chapter 8 247

About SGI IRIX Managed NodesIn this Chapter

In this ChapterThis chapter explains how to install and configure HP OpenView VantagePoint Operations (VPO) on Silicon Graphics Indigo (SGI) IRIX managed nodes.

Chapter 8248

About SGI IRIX Managed NodesInstallation Requirements

Installation RequirementsThis section explains VPO hardware and software requirements for SGI IRIX managed nodes.


Before installing VPO, make sure the SGI IRIX systems you select as managed nodes meet the following hardware requirements:

❏ Disk Space



None

❏ Additional RAM

None

Chapter 8 249

About SGI IRIX Managed NodesInstallation Requirements


Before installing VPO, make sure the following software is installed on SGI IRIX managed nodes:




For a list of kernel parameters, see the VPO Administrator’s Reference Volume I. You can check and change the system parameters using the sysmgr tool.

❏ NCS

Install the following NCS packages:

• SGI IRIX 5.3

Install one of the following NCS 1.5.1 packages:

netls_eoe.sw

gr_ncs.sw

• SGI IRIX 6.2 or higher

Install the following NCS 1.5.1 package:

license_eoe.sw.netls_server

If neither NCS nor DCE are found on the managed node, VPO installs llbd and lb_admin during VPO software installation.

❏ NFS

For diskless operations, install SGI IRIX NFS on a cluster server.

Chapter 8250

About SGI IRIX Managed NodesInstalling and De-installing Agents

Installing and De-installing AgentsThis section describes how to install and de-install SGI IRIX managed nodes.


When installing SGI IRIX managed nodes, follow these guidelines:



/etc/hosts



The VPO agent software is installed on the /opt file tree. If there is not enough space for the installation of the VPO agents, create a symbolic link before installing VPO.





Chapter 8 251

About SGI IRIX Managed NodesInstalling and De-installing Agents

Installing Agents



/tmp/inst.log




/tmp/inst.log

Removing Agents

If you no longer need an older VPO agent package, and the package is not installed on any managed node, you can remove it by running:

/opt/OV/bin/OpC/install/rm_opc.sh sgi/mips/irix \ <VPO_version>


Chapter 8252

About SGI IRIX Managed NodesAbout Preconfigured Elements

About Preconfigured ElementsThis section describes preconfigured templates, template groups, and applications used by VPO on SGI IRIX managed nodes.



❏ IRIX


Table 8-1 shows encapsulated logfiles and associated template used on SGI IRIX managed nodes.


The VPO event interceptor is not supported on SGI IRIX managed nodes.

Table 8-1 Encapsulated Logfiles on SGI IRIX Managed Nodes


/var/adm/loginlog History of failed login attempts

Bad Logs (IRIX)

/var/cron/log Cron logfile Cron (IRIX)

/var/adm/sulog Switch user logfile Su (IRIX)

/var/adm/SYSLOGa Syslog daemon logfile Syslog (IRIX)

/var/adm/wtmpx History of logins Logins (IRIX)

a. requires the logfile /var/adm/SYSLOG which must be configured (or enabled) in the file /etc/syslog.conf

Chapter 8 253

About SGI IRIX Managed NodesAbout Preconfigured Elements


Table 8-2 describes the default monitored objects used by VPO on SGI IRIX managed nodes.






95% 2


90% 10


0.5 5

MailQueue Length


30 2



0.5 5



Chapter 8254

About SGI IRIX Managed NodesDistributing Scripts and Programs

Distributing Scripts and ProgramsFor SGI IRIX managed nodes, the platform selector and architecture identifier is the following:

sgi/mips/irix






/var/opt/OV/share/databases/OpC/mgd_node/customer\/sgi/mips/irix/actions/


/var/opt/OV/share/databases/OpC/mgd_node/customer\/sgi/mips/irix/monitor/


/var/opt/OV/share/databases/OpC/mgd_node/customer\/sgi/mips/irix/cmds/

Chapter 8 255

About SGI IRIX Managed NodesDistributing Scripts and Programs







Temporary Directory

Silicon Graphics SGI IRIX /var/opt/OV/tmp/OpC/bin/actions/var/opt/OV/tmp/OpC/bin/cmds/var/opt/OV/tmp/OpC/bin/monitor


Managed Node

Operating System


Silicon Graphics

SGI IRIX /var/opt/OV/bin/OpC/actions rwxr-xr-x (owner:root)

/var/opt/OV/bin/OpC/cmds rwxr-xr-x(owner:root)

/var/opt/OV/bin/OpC/monitor rwxr-xr-x(owner:root)

Chapter 8256

About SGI IRIX Managed NodesOrganization of Managed Nodes

Organization of Managed NodesFigure 8-1 shows how VPO software is organized on SGI IRIX managed nodes, based on the typical SVR4 platforms.

Figure 8-1 VPO Software on SGI IRIX Managed Nodes

Location of Files

On SGI IRIX managed nodes, files are located as follows:


/var/opt/OV/tmp/OpC



bin conf tmp log

/opt/OV

OpC OpC OpCOpC

install

liblocale

<lang>

bin conf

/var/opt/OV

include

LC_MESSAGES

B

B

bin

OpC

utils

B


Key:

contrib

OpC

Chapter 8 257






The default VPO operator appears in the following directory on SGI IRIX managed nodes:

/etc/passwd


User Name opc_op





Home Directory /var/people/opc_op

Login Shell /bin/sh (POSIX shell)


The default VPO operator group appears in the following directory on SGI IRIX managed nodes:

/etc/group


Group Name opcgrp



Users opc_op


Chapter 8258



VPO makes changes in the following system resource files during installation:







/etc/exports Cluster server only. Entry for export of /opt directory.

/etc/exports Cluster client only. Entry for mount /opt directory.

/etc/int.d/grad_nck NCS startup and shutdown script.

/etc/rc0.d Creates the K35nck file.

/etc/rc2.d Creates the S40nck file.


Chapter 8 259

About SGI IRIX Managed NodesTypes of Libraries



On a Silicon Graphics Indigo platform with SGI IRIX managed nodes, use the following include file:






/opt/OV/lib/libnsp.so

/usr/lib/libnck.a

/usr/lib/libnsl.so

/usr/lib/libc.so


/usr/lib/libnck.a

/usr/lib/libnsl.so

/usr/lib/libc.so


/usr/lib/libnck.a

/usr/lib/libnsl.so

/usr/lib/libc.so


-lopc -lsocket -lnsl




Chapter 8260


About the Makefile




Makef.irix



Chapter 8 261


Chapter 8262

9 About SINIX RM/Reliant Managed Nodes

Chapter 9 263

About SINIX RM/Reliant Managed NodesIn this Chapter

In this ChapterThis chapter explains how to install and configure HP OpenView VantagePoint Operations (VPO) on Siemens-Nixdorf SINIX RM/Reliant managed nodes.

Chapter 9264

About SINIX RM/Reliant Managed NodesInstallation Requirements

Installation RequirementsThis section explains VPO hardware and software requirements for SINIX RM/Reliant managed nodes.


Before installing VPO, make sure the SINIX RM/Reliant systems you select as managed nodes meet the following hardware requirements:

❏ Disk Space



None

❏ Additional RAM

None


Before installing VPO, make sure the following software is installed on SINIX RM/Reliant managed nodes:




For a list of kernel parameters, see the VPO Administrator’s Reference Volume I. You can check and change the system parameters using the sysadm tool.

❏ Siemens-Nixdorf Networking Packages (5.43)

• tcp• SImac596

Chapter 9 265

About SINIX RM/Reliant Managed NodesInstallation Requirements


• NCS 1.5.1

If NCS is chosen as the Node Type in the VPO GUI, and NCS 1.5.1 is not found on the managed node, VPO installs llbd and lb_admin during the VPO agent software installation.

• DCE-CLNT 2.0

If the communication type is set to DCE RPCS (TCP or UDP), DCE-CLNT must be installed on the managed node.

NOTE You can purchase DCE at additional cost for SINIX/Reliant platforms from the platform vendor or from a third-party supplier.

❏ Package: attcmd

❏ Package: SIsnmpd

This package is necessary if you want to run the VPO monitoring agent.

The 64-bit version of SINIX 5.45 includes this software package only for version V5.45A30 or higher.

If you have a 64-bit SINIX 5.45 system with a lower version, you can either upgrade, take this package from the V5.45A30 release, or copy the following files from a 32-bit SINIX 5.45 system:

• /opt/lib/snmpd/snmplib/libsnmp.so

• /opt/lib/snmpd/snmplib/libsnmpio.so

• /opt/lib/snmpd/snmplib/libsnmpuser.so

• /opt/snmp/lib/libsnmpapi.so

Chapter 9266

About SINIX RM/Reliant Managed NodesInstalling and De-installing Agents

Installing and De-installing AgentsThis section describes how to install and de-install SINIX RM/Reliant managed nodes.


When installing SINIX RM/Reliant managed nodes, follow these guidelines:



/etc/hosts








Chapter 9 267


❏ Logfile Encapsulator

By default, some of the logfiles checked by the logfile encapsulator are not present on SINIX/Reliant managed nodes (for example, /var/adm/loginlog). It is important that you manually create all logfiles that are checked by the logfile encapsulator agent. For example, if bad login attempts are to be monitored by VPO, you must first create the file /var/adm/loginlog with read and write permissions for the owner only. The owner must be root and the group sys. After five unsuccessful attempts to log in, a message is written to /var/adm/loginlog.

The Su and Cron templates assume that the default setup is used for the /etc/default/su and /etc/default/cron files. If the default setup is not used, you must adapt the logfile paths in the templates to match the actual file names.

❏ DNS

If you want to configure the Domain Name Server (DNS) on a SINIX/Reliant managed node, you must do the following:

1. Edit the following file:

/etc/resolv.conf

2. Add the following line to the hosts files:

<nodename> (uname -n)

You must add this line to the following files:

• /etc/net/ticlts/hosts• /etc/net/ticots/hosts• /etc/net/ticotsord/hosts

If <nodename> is not defined in these three files, the VPO installation will fail because the opcnsl program will be unable to determine the management server.

Chapter 9268


Configuring DCE

This section explains how to set up a new DCE configuration and remove an existing DCE configuration on SINIX RM/Reliant managed nodes.

To Configure DCE

To configure DCE on SINIX RM/Reliant managed nodes, follow these steps:

1. To start the dce_config program, enter the following:

/etc/dce_config

2. Select 2. CONFIGURE.

3. Select 3. DCE Client.

4. If you are asked about removing all remnants of a previous DCE configuration, enter y.

5. When prompted, enter y.

The dce_config program then checks the local clock against the dtsd server.

6. Enter the name of the system where a DTS server running.

7. Enter the Cell Administrator’s principal name (for example, cell_admin) and password.

8. Enter the name of the system that is the CDS server.

9. Do not create a LAN profile.

10.Enter one of the following

• clerk

If you want to configure DTS.

• none

If you do not want to configure DTS.

This procedure configures the managed nodes as a DCE client and starts the DCE daemon dced.

Chapter 9 269


To Remove an Existing DCE Configuration

To remove an existing DCE configuration from SINIX RM/Reliant managed nodes, follow these steps:

1. From the main menu, choose 5. UNCONFIGURE.

2. Choose 6. REMOVE.

Installing Agents

To install agents on SINIX RM/Reliant managed nodes, you can use standard or manual installation methods.


For standard installation instructions, see the VPO Administrator’s Reference Volume I.


/tmp/pkgadd.log


For manual installation instructions, see “To Install an Agent Manually” on page 290.

NOTE The agent package opc_pkg.Z on the VPO management server for the SINIX/Reliant platform is the following:

/var/opt/OV/share/databases/OpC/mgd_node/vendor/sni\mips/sinix/A.07.00/RPC_[NCS|DCE_TCP|DCE_UDP]/opc_pkg.Z

Chapter 9270



To de-install agents on SINIX RM/Reliant managed nodes, you can use standard or manual de-installation methods. You can also remove older agent packages from the managed nodes.

De-installing Agents with Standard De-installation

For standard de-installation instructions, see the VPO Administrator’s Reference Volume I.


/tmp/pkgrm.log




2. De-install the VPO agent software from SINIX/Reliant managed nodes by entering:

pkgrm OPC


If an older VPO agent package is no longer required and is not installed on any managed node, you can remove it by running script on the management server:

/opt/OV/bin/OpC/install/rm_opc.sh sni/mips/sinix \ <VPO_version>

In this command, <VPO_version> is the version of VPO that supports this agent platform (for example A.07.00).

Chapter 9 271

About SINIX RM/Reliant Managed NodesAbout Preconfigured Elements

About Preconfigured ElementsThis section describes preconfigured templates, template groups, and applications used by VPO on SINIX RM/Reliant managed nodes.



❏ SINIX


Table 9-1 shows encapsulated logfiles and associated template used on SINIX RM/Reliant managed nodes.


The VPO event interceptor is not supported on SINIX RM/Reliant managed nodes.

Table 9-1 Encapsulated Logfiles on Siemens Nixdorf SINIX/Reliant Managed Nodes


/var/cron/log a Cron logfile Cron (SINIX)

/etc/.osm SINIX OS messages OS Msgs (SINIX)

/var /adm/sulog b Switch user logfile Su (SINIX)

/var/adm/wtmpx History of logins Logins (SINIX)

/var/adm/loginlog c Bad login attempts Bad Logs (SINIX)

a. Default setup is used in the /etc/default/cron fileb. Default setup is used in /etc/default/su filec. You must manually create the /var/adm/loginlog file

Chapter 9272

About SINIX RM/Reliant Managed NodesAbout Preconfigured Elements


Table 9-2 describes the default monitored objects used by VPO on SINIX RM/Reliant managed nodes.




95% 2


90% 10


0.5 5




Chapter 9 273

About SINIX RM/Reliant Managed NodesDistributing Scripts and Programs

Distributing Scripts and ProgramsFor SINIX RM/Reliant managed nodes, the platform selector and architecture identifier is the following:

sni/mips/sinix






/var/opt/OV/share/databases/OpC/mgd_node/customer\/sni/mips/sinix/actions/*


/var/opt/OV/share/databases/OpC/mgd_node/customer\/sni/mips/sinix/monitor/*


/var/opt/OV/share/databases/OpC/mgd_node/customer\/sni/mips/sinix/cmds/*

Chapter 9274

About SINIX RM/Reliant Managed NodesDistributing Scripts and Programs







Temporary Directory

Siemens Nixdorf SINIX /var/opt/OV/tmp/OpC/bin/actions/var/opt/OV/tmp/OpC/bin/cmds/var/opt/OV/tmp/OpC/bin/monitor


Managed Node

Operating System


Siemens Nixdorf

SINIX /var/opt/OV/bin/OpC/actions rwxr-xr-x (owner:root)



Chapter 9 275

About SINIX RM/Reliant Managed NodesOrganization of Managed Nodes

Organization of Managed NodesFigure 9-1 shows how VPO software is organized on SINIX RM/Reliant managed nodes, based on the typical SVR4 platforms.

Figure 9-1 VPO Software on SINIX/Reliant Managed Nodes

Location of Files

On SINIX RM/Reliant managed nodes, files are located as follows:


/var/opt/OV/tmp/OpC



bin conf tmp log

/opt/OV

OpC OpC OpCOpC

install

liblocale

<lang>

bin conf

/var/opt/OV

include

LC_MESSAGES

B

B

bin

OpC

utils

B


Key:

contrib

OpC

Chapter 9276






The default VPO operator appears in the following directory on SINIX RM/Reliant managed nodes:

/etc/passwd


User Name opc_op






Login Shell /bin/sh


The default VPO operator group appears in the following directory on SINIX RM/Reliant managed nodes:

/etc/group


Group Name opcgrp



Users opc_op


Chapter 9 277



VPO makes changes in the following system resource files during installation on SINIX RM/Reliant managed nodes:








/etc/int.d/ncs NCS startup and shutdown script (if it is not already present and the communciation type is NCS RPC).

/etc/rc0.d Creates the K52ncs (if it is not already present and the communciation type is NCS RPC).

/etc/rc1.d Creates the K52ncs file (if it is not already present and the communciation type is NCS RPC).

/etc/rc2.d Creates the S76ncs file (if it is not already present and the communciation type is NCS RPC).

/usr/lib/snmplib/libsnmpapi.so -> \/opt/lib/snmpd/snmplib/libsnmpuser.so Creates symbolic link

(if it is not already present).


Chapter 9278

About SINIX RM/Reliant Managed NodesTypes of Libraries



VPO Version

VPO A.05.xx VPO A.06.xx VPO A.07.xx



thr_cc is used which comes with its own libraries




-lopc_r -lnsp -ldce -lsocket_r

-lresolv_r -lm_r -lc -lnsl_r_i








mips_cc is used which comes with its own libraries




-lopc -lnck -lnsp -lsocket -lnsl -lc -lucb




Chapter 9 279

About SINIX RM/Reliant Managed NodesTypes of Libraries

About the Makefile



The build an executable with correct compile and link options, use the following makefiles:

❏ Makef.sinix

❏ Makef.sinix-dce

For more information about the managed node makefiles, see the ReadMe file:


Chapter 9280

10 About Sun Solaris Managed Nodes

Chapter 10 281

About Sun Solaris Managed NodesIn this Chapter

In this ChapterThis chapter explains how to install and configure HP OpenView VantagePoint Operations (VPO) on Sun Solaris managed nodes.

Chapter 10282

About Sun Solaris Managed NodesInstallation Requirements

Installation RequirementsThis section explains VPO hardware and software requirements for Sun Solaris managed nodes.


Before installing VPO, make sure the Sun Solaris systems you select as managed nodes meet the following hardware requirements:

❏ Disk Space


• NCS

10 MB

About 20 MB is required during software installation.

• DCE

20 MB free disk space

— 10 MB for VPO agent

— 10 MB for HP Lightweight DCE software

About 40 MB is required during software installation.


None

❏ Additional RAM

None

Chapter 10 283



Before installing VPO, make sure the following software is installed on Sun Solaris managed nodes:



❏ Required Patches for Sun Solaris Managed Nodes

The following patches are required for the VPO Sun Solaris managed nodes. They are available from the www.sunsolve.sun.com web site.

See also the section “Problems Caused by Missing OS Patches for Sun Solaris” on page 289 for information about patches that must not be installed on Sun Solaris managed nodes.

Table 10-1 Required Patches for Sun Solaris Managed Nodes

OS Version Patch ID Description

Solaris 2.6 107733-09 SunOS 5.6: Linker patch

105591-11 SunOS 5.6: Shared library patch for C++

106429-02 SunOS 5.6: /kernel/drv/mm patch

105181-29 SunOS 5.6: Kernel update patch

105210-38 SunOS 5.6: libaio, libc & watchmalloc patch

105568-23 SunOS 5.6: /usr/lib/libthread.so.1 patch

105633-59 OpenWindows 3.6: Xsun patch

106841-01 OpenWindows 3.6: Keytables patch

106842-09 SunOS 5.6: Feature patch for Euro currency support in Solaris 2.6

Chapter 10284


❏ Kernel Parameters

It is recommended that you set the following kernel parameters for Sun Solaris managed nodes:

You can check and change the kernel parameters by editing the /etc/system file.

Solaris 7 106950-15 SunOS 5.7: Linker patch

106327-10 SunOS 5.7: 32-Bit Shared library patch for C++

107544-03 SunOS 5.7: /usr/lib/fs/ufs/fsck patch

106541-17 SunOS 5.7: Kernel update patch

106980-17 SunOS 5.7: libthread patch

Solaris 8 109147-09 SunOS 5.8: Linker patch

108434-03 SunOS 5.8: Shared library patch for C++

108827-11 SunOS 5.8: libthread patch

Table 10-2 Recommended Kernel Parameters for Sun Solaris Managed Nodes

Parameter Description Minimum value

semmap Number of entries in semaphore map 15 or greater

semmni Number of semaphore identifiers 30

semmns Number of semaphores in system 200 or greater

semmsl Maximum number of semaphores per ID

100

Table 10-1 Required Patches for Sun Solaris Managed Nodes

OS Version Patch ID Description

Chapter 10 285



• NCS

If NCS is chosen as the Communication Type in the VPO GUI, and NCS version 1.5.1 is not found on the managed node, VPO installs llbd and lb_admin during the VPO agent software installation.

• DCE

If the communication type is set to DCE RPC (TCP or UDP) and 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. Please refer to Table 10-3 for more information regarding supported DCE packages.

❏ ARPA/Berkeley Services

❏ MIB

The MIB monitoring functionality of VPO requires the snmpd of the HP OpenView platform, or SNMP-based, MIB-I (RFC 1156) or MIB-II (RFC1158) compliant agent software.

Table 10-3 Supported DCE packages

OS DCE

Solaris 2.6 TransArc DCE 2.0, HPlwdce, DASCOM DCE 1.1

Solaris 7 IBM DCE 3.1, HPlwdce, DASCOM DCE 1.1

Solaris 8 IBM DCE 3.1, HPlwdce, DASCOM DCE 1.1

Chapter 10286

About Sun Solaris Managed NodesInstalling and De-installing Agents

Installing and De-installing AgentsThis section describes how to install and de-install Sun Solaris managed nodes.


When installing Sun Solaris managed nodes, follow these guidelines:



/etc/hosts


❏ Name of System

The system name uname -s must be set to one of the following:

• SunOS

• Solaris

❏ Package SUNWaccu

The package SUNWaccu must be installed on the system if process table and CPU utilization are to be monitored by VPO. If this package is not installed, and monitoring templates proc_util and cpu_util are configured, warning messages will appear in the Message Browser window stating that the corresponding shell scripts failed to execute.

❏ Bad Logins

If bad login attempts are to be monitored by VPO, the file /var/adm/loginlog must first be manually created. By default, loginlog does not exist, so no logging is done. To enable logging, the logfile must be created with read and write permission for the owner root and group sys. You can then configure the logfile template Bad Logs (Solaris) for the node.

Chapter 10 287







In a cluster environment, make sure that /bigdisk is accessible from all cluster clients. That is, make sure that it is mounted from all client nodes. For example, the local file system /bigdisk on a cluster client must be mounted to exported file system /bigdisk on the cluster server.

Chapter 10288


Problems Caused by Missing OS Patches for Sun Solaris

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 VPO installation fails on Sun Solaris managed nodes with the following message:

tar xof...core dump

To solve this problem, do one of the following:

• Install patch version -06 (or later).

• De-install the old patch.

To check which patches are currently installed on Sun Solaris systems, enter:

showrev -p

❏ Multi-processor Patch

If the DCE communication type is used, make sure you have the following patches installed:

Solaris 2.6

Use the following patches:

105181-16

105210-24

105568-14

NOTE See also the section “Software Requirements” on page 284 for a list of required patches for Sun Solaris managed nodes.

Chapter 10 289


Installing Agents

To install agents on Sun Solaris managed nodes, you can use standard or manual installation methods.




/tmp/pkgadd.log

To Install an Agent Manually

In some situations, you may want to install the Sun Solaris agent software without using the management server. Manual installation prepares the system to become a VPO managed node when it is later connected to the network. Manual installation is useful if many systems are prepared in a central location, or if you want to avoid using the root connection over the network that is necessary for a standard agent installation.

To install the VPO agent on a Sun Solaris system that will become a VPO managed node, follow these steps:



• opc_pkg.Z

• comm_pkg.Z

• perf_pkg.Z

• opc_inst


/var/opt/OV/share/databases/OpC/mgd_node/vendor/sun/\sparc/solaris/A.07.00/RPC_[NCS|DCE_TCP|DCE_UDP]/

2. Set umask, enter:

umask 022

Chapter 10290




/tmp/opc_inst

You can now activate the Sun Solaris managed node. For instructions, see “Activating Agents” on page 292.

Chapter 10 291


Activating Agents

To activate agents on Sun Solaris managed nodes, you can use the command line or the VPO GUI.

To Activate a Node from the Command Line

To activate a Sun Solaris managed node over the network from the command line, follow these steps:

1. Add the pre-installed node to the VPO Node Bank.


Actions:Node->Add



3. Install the VPO agent on the node manually.

For instructions, see “To Install an Agent Manually” on page 290.

4. After manually installing the agent on the node, enter the following:

/opt/OV/bin/OpC/install/opcactivate -s <VPO_mgt_server>\-cs <server_codeset> -cn <agent_codeset>

The agent then attempts to send messages to the management server.




5. After the node is connected to the network, execute the following command on the management server:


Chapter 10292



After the node with the pre-installed agent is connected to the network, you can activate and register the managed node from the VPO GUI.

To activate and register the managed node from the VPO GUI, follow these steps:

1. Add the pre-installed nodes to the VPO Node Bank.


Actions:Node->Add



3. Distribute the VPO configuration to the node:

a. Select Actions:Agents->Install / Update SW & Config from the menu bar of the VPO Node Bank.

The Install / Update VPO Software and Configuration window opens.

b. Select all components.

c. Click [OK].

CAUTION Do not check [Force Update]. If you do, the management server will re-install the agent.

If the agent is pre-installed on the node, the management server will activate the node, and install the selected components.

CAUTION If the agent software is not pre-installed, the management server will install the agent.

4. To verify that the control, message, and action agents are all running on the managed node, enter the following:


Chapter 10 293



To de-install agents on Sun Solaris managed nodes, you can use standard or manual de-installation methods. You can also remove older agent packages from the managed nodes.




/tmp/pkgrm.log




2. De-install the VPO agent software from the managed nodes by entering:

/usr/sbin/pkgrm OPC OPCCOMM OPCPERF

NOTE If you are de-installing an older version of the agent, use: /usr/sbin/pkgrm OPC.

3. If you installed DCE communication type, you must also de-install the HPlwdce package.


/usr/sbin/pkgrm HPlwdce

Chapter 10294



If older VPO agent packages are no longer required and are not installed on any managed node, you can remove them from the management server by running:

/opt/OV/bin/OpC/install/rm_opc.sh sun/sparc/solaris \ <VPO_version>


Chapter 10 295

About Sun Solaris Managed NodesAbout Preconfigured Elements

About Preconfigured ElementsThis section describes preconfigured templates, template groups, and applications used by VPO on Sun Solaris managed nodes.



❏ Solaris


Table 10-4 shows the opcmsg message templates that are available for Sun Solaris managed nodes.

Table 10-4 opcmsg Message Templates on Sun Solaris Managed Nodes

Name Description

opcmsg(1|3) Default interception of messages submitted by opcmsg(1), opcagtmsg_send(3), and opcmsg(3).

Chapter 10296



Table 10-5 shows encapsulated logfiles and associated template used on Sun Solaris managed nodes.

Table 10-5 Encapsulated Logfiles on Sun Solaris Managed Nodes


/var/adm/loginlog History of Solaris failed logins

Bad Logs (Solaris)

/var/cron/log Cron logfile Cron (Solaris)

/var/adm/messages System logfile Syslog (Solaris)

/var/adm/sulog Switch user logfile Su (Solaris)

/var/adm/wtmpx History of logins Logins (Solaris)

/var/adm/messages Fetch messages from SC and forward to APM

Engine Log (SC)

/var/VRTSvcs/\log/engine_A.log

Fetch messages from VCS and forward to APM

Engine Log (VCS)

/var/opt/OV/tmp/\OpC/opcapmvcsg\notifyengine

Fetch messages from VCS and forward to APM

Engine Notifiy Log (VCS)

Chapter 10 297




Types of SNMP Traps



Example: system cold start, network interface up and down, and so on.






Chapter 10298






• SNMP Devices


Set the destination systems for SNMP devices on Sun Solaris nodes in the following file:



trap-dest:<nodename>









Chapter 10 299


To Configure Event Interception with ECS

By default, opctrapi connects to the correlated event flow of pmd. You can change this behavior by adding an appropriate statement to the opcinfo file on the managed node.

Syntax:

SNMP_EVENT_FLOW [ALL|RAW|CORR]

The opctrapi process connects to the default ECS stream of pmd.

If needed, you can configure opctrapi to connect to a specific ECS stream of pmd by specifying the ECS stream in the opcinfo file:

SNMP_STREAM_NAME <stream_name>

Chapter 10300



Table 10-6 describes the default monitored objects used by VPO on Sun Solaris managed nodes.

Types of Applications




cpu_util Monitors CPU utilization: requires the sar program

95% 2

disk_util Monitors disk space utilization on the root disk

90% 10

Inetd Number of executing instances of inetd (Internet Daemon)

0.5 5

MailQueue Length

Length of the sendmail queue: number of unsent mail messages

30 2

proc_util Monitors process table utilization 75% 5

sendmail Number of executing instances of sendmail

0.5 5

swap_util Monitors SWAP utilization 80% 5

Syslogd Checks whether syslogd is running 0.5 5

Chapter 10 301

About Sun Solaris Managed NodesDistributing Scripts and Programs

Distributing Scripts and ProgramsFor Sun Solaris managed nodes, the platform selector and architecture identifier is the following:

sun/sparc/solaris






/var/opt/OV/share/databases/OpC/mgd_node/customer\/sun/sparc/solaris/actions/*


/var/opt/OV/share/databases/OpC/mgd_node/customer\/sun/sparc/solaris/monitor/*


/var/opt/OV/share/databases/OpC/mgd_node/customer\/sun/sparc/solaris/cmds/*

Chapter 10302

About Sun Solaris Managed NodesDistributing Scripts and Programs







Temporary Directory

Sun SPARC

Fujitsu-Siemens SPARC

Sun Solaris /var/opt/OV/tmp/OpC/bin/actions/var/opt/OV/tmp/OpC/bin/cmds/var/opt/OV/tmp/OpC/bin/monitor




Sun SPARC

Fujitsu-Siemens SPARC

Sun Solaris /var/opt/OV/bin/OpC/actions rwxr-xr-x (owner: root)


/var/opt/OV/bin/OpC/monitor rwxr-xr-x(owner: root)

Chapter 10 303

About Sun Solaris Managed NodesOrganization of Managed Nodes

Organization of Managed Nodes Figure 10-1 shows how VPO software is organized on Sun Solaris managed nodes.

Figure 10-1 VPO Software on Sun Solaris Managed Nodes

The path /var/sadm/pkg/OPC is used by the pkgadd utility for software maintenance.

Location of Files

On Sun Solaris managed nodes, files are located as follows:


/var/opt/OV/tmp/OpC



bin

/opt/OV

OpC

install

liblocale

<lang>

include

LC_MESSAGES utils

B


Key:

contrib

OpC

conf tmp log

OpC OpC OpC

bin conf

/var/opt/OV

B

B

bin

OpC

databases

BBC

Chapter 10304



The default VPO operator, opc_op, owns /export/home/opc_op as home directory. By default, the operator uses the Korn Shell (/bin/ksh), and is locked until the passwd command is executed. User opc_op belongs to the group opcgrp.

You add user opc_op and group opcgrp only locally on the managed node (with useradd or groupadd).

If the managed node is a Network Information Service (NIS or NIS+) client, the VPO installation checks if user opc_op is already in the NIS database:

❏ If opc_op is in the NIS database, no additional user is installed.

❏ If opc_op is not in the NIS database, opc_op is added only locally on the managed node.


VPO makes changes in the following system resource files during installation on Sun Solaris managed nodes:

/etc/passwd/etc/shadow Entry for the default VPO operator.

/etc/group Group entry for the default VPO operator.


/etc/rc3.d/S99opcagt Creates file.

/etc/rc0.d/K09opcagt Creates file.

/etc/rc1.d/K09opcagt Creates file.

/etc/vfstab On cluster client only, entry for mount /opt directory.

/etc/init.d/ncs NCS startup script (if not already present).

/etc/rc3.d/S76ncs Creates file (if not already present).

/etc/rc0.d/K52ncs Creates file (if not already present).

/etc/rc2.d/K52ncs Creates file (if not already present).

Chapter 10 305



Chapter 10306

About Sun Solaris Managed NodesTypes of Libraries

Types of LibrariesTable 10-10 describes the managed node libraries for VPO A.05.xx, A.06.xx and A.07.xx.





libov.a and libovutil.a are statically linked into libopc.so

/usr/lib/libw.so.1

/usr/lib/libsocket.so.1

/usr/lib/libnsl.so.1

/usr/lib/libc.so.1

/usr/lib/libdl.so.1

/usr/lib/libmp.so.2

/usr/platform/SUNW,\ Ultra-5_10/lib/libc_psr.so.1

libov.a and libovutil.a are statically linked into libopc.so

/usr/lib/libw.so.1

/usr/lib/libnck.a



/opt/OV/lib/libopcas.so.1



/usr/lib/libw.so.1

/opt/OV/lib/libopcas.so

/usr/lib/libc.so.1

/usr/lib/libdl.so.1

/usr/lib/libmp.so.2



-lopc -lnsp -lsocket -lnsl




Chapter 10 307



On a Sun SPARCstation platform with Sun Solaris managed nodes, use the include file:




/opt/OV/dce/lib/libdce.so

/opt/OV/dce/lib/libdcecrypt.so



/usr/lib/libw.so.1

/usr/lib/libc.so.1

/usr/lib/libdl.so.1

/usr/lib/libmp.so.2


/usr/lib/libm.so.1

/usr/lib/libthread.so.1



/opt/OV/dce/lib/ \ libdcecrypt.so



/usr/lib/libw.so.1

/usr/lib/libc.so.1

/usr/lib/libdl.so.1

/usr/lib/libmp.so.2

libc_psr.so.1a


/opt/OV/dce/lib/ \ libdcecrypt.so



/usr/lib/libw.so.1


/usr/lib/libthread.so.1

/usr/lib/libm.so.1

/usr/lib/libc.so.1

/usr/lib/libdl.so.1

/usr/lib/libmp.so.2



-lopc_r -lnsp -lnsl -ldce -lsocket -lthread -lm -lw




a. Location of the library libc_psr.so.1 is platform dependent.



Chapter 10308


About the Makefile

The following directory on the management server contains the makefiles for building executables:


To build an executable with correct compile and link options, use the following makefiles:

❏ NCS

Makef.solaris

❏ DCE

Makef.solarisdce



Chapter 10 309

About Sun Solaris Managed NodesSupport for Sun Enterprise E10000

Support for Sun Enterprise E10000The Sun Enterprise E10000 platform is an extremely powerful and highly reliable server system:

❏ Dynamic System Domains

System boards within the platform may be logically grouped into separately bootable systems called Dynamic System Domains, or simply domains. Up to eight domains may exist simultaneously on a single E10000 platform. The domain is able to run its own operating system (Sun Solaris 2.6, 7 or 8), and can handle its own workload. Domains can be created and deleted without interrupting the operation other domains.

❏ Sun Service Processor

Sun Service Processor (SSP) is the central console that monitors the E10000 system and enables the operator to perform management and maintenance procedures. The SSP enables you to control and monitor the domains as well as the platform itself.

Monitoring and Managing E10000 Systems

Standard instrumentation provided with VPO A.07.00 version enables you to monitor and manage the Sun Enterprise E10000 platform with the following:

❏ Remote Monitoring and Managing

Monitoring and managing the SSP system remotely.

❏ Proxy Agent

There is no VPO agent installed on the SSP system. VPO agent on another node (Sun Solaris or HP-UX) takes a proxy agent role. The SSP system must be added to VPO Node Bank as Message Allowed node.

❏ SNMP Traps

Monitoring the E10000 platform is based on intercepting SNMPv1 traps, which are generated by the SSP snmpd daemon on the SSP system.

Chapter 10310


❏ Monitor and Logfile Templates

Additional monitor and logfile templates are provided to monitor the SSP cbs daemon process and the SSP logfiles.

❏ SSP Administration

SSP administration windows hostview and netcontool can be launched remotely from the VPO Application Bank.

About Software and OS Versions for E10000 Systems

VPO for Sun Enterprise E10000 supports the following software and operating system versions:

❏ SSP Software

Sun Enterprise 10000 SSP 3.x


Sun Solaris 2.6, 7 and 8

❏ VPO Agent Packages

Installed on Sun Solaris or HP-UX system

About Preconfigured Elements for E10000 Systems

This section describes preconfigured templates, template groups, and applications provided by VPO for monitoring and managing the Sun Enterprise E10000 platform.


VPO uses the following preconfigured template group for Sun Enterprise E100000:

❏ SSP

Chapter 10 311


About SNMP Trap Interception

A SNMP trap template is used to intercept all SSP snmpd traps.

Because there is no VPO agent installed on the SSP system, you must do the following to intercept SSP traps:

❏ Reconfigure

You must reconfigure the SSP snmpd daemon. For instructions, see “Configuring the SSP System for E10000 Systems” on page 316.

❏ Assign and Distribute

You must assign and distribute the SNMP trap template to the node with VPO agent installed.

Chapter 10312


About Encapsulated Logfiles

VPO provides the SSP Logfile Template for monitoring the domain- and platform-specific SSP logfiles shown in Table 10-11.

To monitor the SSP logfiles, you must export and then manually mount the following SSP logfile directory on the VPO agent node:

/var/opt/SUNWssp/adm

For more information, see “To Reconfigure the SSP snmpd Daemon” on page 316.

Table 10-11 Encapsulated SSP Logfiles


/var/opt/SUNWssp/adm/<domain_name>/messages Domain specific SSP Logfile

/var/opt/SUNWssp/adm/<domain_name>/netcon netcon logfile SSP Logfile

/var/opt/SUNWssp/adm/messages Platform specific SSP Logfile

Chapter 10 313


About Monitored Objects

The control board server (cbs) daemon provides access to the Sun Enterprise 10000 system control board for client programs running on the SSP system. The SSP monitor template is provided to check if the cbs daemon is running.

Table 10-12 shows the object thresholds on the SSP system.

You must establish remote equivalence between the SSP system and the node with VPO agent installed. For details, see “To Establish Remote Host Equivalence” on page 317.

Table 10-12 Object Thresholds on the SSP system


cbs Monitors the cbs (control board server) daemon

0.5 3

Chapter 10314


About SSP Tools

VPO provides an additional application group, SSP Tools, for monitoring and managing the E10000 system.

SSP Tools consists of the following applications:

hostview Launches the SSP administration X window application - hostview, the primary graphical user interface (GUI) to the E10000 system. This GUI is used to monitor the E10000 hardware and software configuration and status. It enables you to perform dynamic reconfiguration operations.

The application is started on the management server.

netcontool Launches SSP administration X window application - netcontool, the graphical user interface (GUI) to the netcon command. This GUI enables a remote connection to the domain console window (that is, the console window for a specified domain).

The application is started on the management server.

SSP Config Uses a vi text editor to open and edit the template configuration file:

/var/opt/OV/conf/OpC/ssp

The file must be edited to determine which SSP nodes are to be monitored.

The application is started on the node where the VPO agent is running.

Chapter 10 315


Configuring the SSP System for E10000 Systems

To configure the Sun Service Processor (SSP) system, perform these procedures:

1. Reconfigure the SSP snmpd daemon.

See “To Reconfigure the SSP snmpd Daemon” on page 316.

2. Optional: Establish remote host equivalence.

See “To Establish Remote Host Equivalence” on page 317.

3. Optional: Export the SSP logfiles directory.

See “To Establish Remote Host Equivalence” on page 317.

To Reconfigure the SSP snmpd Daemon

To intercept SSP traps on the node with VPO agent installed, the SSP snmpd daemon must be reconfigured and restarted.

To reconfigure the SSP snmpd daemon, follow these steps:

1. Edit the SSP snmpd configuration file:

/etc/opt/SUNWssp/snmp/agt/\Ultra-Enterprise-10000.snmpd.cnf

At the end of the file, add the following lines:

#VPO start

trap snmptrap <VPO_agent_IP_address> 162

#VPO end

Where:

<VPO_agent_IP_address> is the IP address of the node where VPO agent with SSP SNMP trap template is installed.

2. Restart the snmpd daemon.

a. Stop the running snmpd daemon.

b. Wait for the automatic restart.

3. Determine an snmpd PID, then stop the process:

ps -e -opid,user,args |grep root | grep snmpd

kill <snmpd_PID>

Chapter 10316


To Establish Remote Host Equivalence

NOTE This procedure is required if you want to monitor the SSP cbs daemon.

To establish a remote host equivalence between the SSP system and the node with VPO agent installed, follow these steps:

1. In the /export/home/ssp directory, create a .rhosts file with the following contents:

<VPO_agent_node_name> root

Where:

<VPO_agent_node_name> is the IP address of the node where VPO agent with SSP SNMP trap template is installed.

2. Change the permission attributes for the file:

chmod 400 /export/home/ssp/.rhosts

To Export the SSP Logfiles Directory

NOTE This procedure is required if you want to monitor the SSP logfiles.

1. Add the following directory to the list of directories to be NFS exported at system boot time:


2. Edit the /etc/dfs/dfstab file by adding the following line:

share -F nfs -o -ro /var/opt/SUNWssp/adm

3. Export the directory by executing the following command:

share -F nfs -o -ro /var/opt/SUNWssp/adm

Chapter 10 317


Installing the VPO Agent for E100000 Systems

This section explains how to prepare a node for SSP system monitoring, then install and configure the VPO agent on the node you selected.

Before Installing the VPO Agent

Before installing the VPO agent packages, you must do the following:

1. Choose a node for SSP system monitoring.

Determine which node will be used for monitoring the SSP system. The VPO agent (for the purpose of monitoring the SSP system) must be installed either on a Sun Solaris or an HP-UX node.

2. Mount the SSP logfiles directory.

On the node chosen for SSP system monitoring, mount the previously NFS exported SSP logfiles directory:


To Install the VPO Agent

NOTE This procedure must be performed on the VPO management server.

To install VPO agent packages on the selected node, follow these steps:

1. Add the SSP system to VPO Node Bank.


Actions:Node->Add.

2. Distribute the VPO configuration to the selected node.

In the VPO Node Bank window select Actions:Agents->Install. You only need to distribute Software and Commands.

Chapter 10318


3. Edit the templates configuration file:

/var/opt/OV/conf/OpC/ssp

a. In the Application Group - SSP Tools window, execute the SSP Config application. This must be done on the node, where the agent which monitors the SSP is installed.

This application opens the SSP templates configuration file in a vi text editor tool. The templates configuration file lists nodes to be monitored by the VPO agent. The entries are checked by the monitor and/or the logfile shell scripts.

b. Add the SSP node name to the configuration file.

Observe the following syntax rules:

hostname {main|backup} [logfiles]

hostname

Name of a remote host where SSP is running.

{main|backup}

Only entries with the keyword main are used. All other entries are ignored. That is, only nodes with the keyword main are monitored. Backup entries can be used for quick change from monitoring main SSP host to a backup host.

[logfiles]

Space-separated list of SSP logfiles that are monitored.

NOTE You must restart the VPO agent to activate the changes in the templates configuration file.

4. Assign and distribute templates to the selected VPO agent node.

In the VPO Node Bank window select Actions:Agents->Assign Templates, and assign the SSP template group to the selected node.

Chapter 10 319


Reconfiguring the SSP Templates

You must reconfigure the SSP templates each time a change from main to backup SSP node occurs. To reconfigure the SSP templates, execute the SSP Config application, and edit the templates configuration file as described in “To Install the VPO Agent” on page 318.

Chapter 10320

About Sun Solaris Managed NodesAbout the VPO Integration Package for Sun Management Center

About the VPO Integration Package for Sun Management Center The VPO integration package for Sun Management Center is available as a separate add-on.

For detailed installation and configuration instructions, see the HP OpenView VantagePoint Operations Integration for Sun Management Center User’s Guide.

The manual is available as an Acrobat Portable Document Format (PDF) document on the management server or on the Internet:


/opt/OV/doc/C/OpC

❏ Internet

http://ovweb.external.hp.com/lpe/doc_serv

Chapter 10 321

About Sun Solaris Managed NodesHigh Availability Support on Sun Solaris

High Availability Support on Sun SolarisThis version of VPO offers the following High Availability (HA) solutions for Sun Solaris on the management server and managed nodes:

❏ Sun Enterprise Cluster Support

VPO version A.07.00 offers Sun Enterprise Cluster support on both the management server and the managed nodes.

For installation and configuration instructions, see the VPO Installation Guide for the Management Server

For additional information for system administrators working with VPO in Sun Cluster environments, see the VPO Administrator’s Reference Volume II.

❏ VERITAS Cluster Server Support

This version of VPO introduces VERITAS Cluster Server Support on both the management server and the managed nodes.

For installation and configuration instructions, see the VPO Installation Guide for the Management Server.

For additional information for system administrators working with VPO in VERITAS Cluster Server environments, see the VPO Administrator’s Reference Volume II.

Chapter 10322

11 About Tru64 UNIX Managed Nodes

Chapter 11 323

About Tru64 UNIX Managed NodesIn this Chapter

In this ChapterThis chapter explains how to install and configure HP OpenView VantagePoint Operations (VPO) onTru64 UNIX managed nodes.

Chapter 11324

About Tru64 UNIX Managed NodesInstallation Requirements

Installation RequirementsThis section explains VPO hardware and software requirements for Tru64 UNIX managed nodes.


Before installing VPO, make sure the Tru64 UNIX systems you select as managed nodes meet the following hardware requirements:

❏ Disk Space



None

❏ Additional RAM

None

Chapter 11 325



Before installing VPO, make sure the following software is installed on Tru64 UNIX managed nodes:



❏ Required Patch for the Tru64 UNIX Managed Nodes

The CXXREDIST632V11.tar patch is required for the Tru64 UNIX managed nodes.

Check if the installed libcxx is earlier than V60300001:

nm /usr/lib/cmplrs/cxx/libcxx.so | grep libcxx_V

If the symbol _libcxx_V60300001 exists in the image on your system, then you do not need to install this patch.

You can download the latest version from the following web page:

http://www.tru64unix.compaq.com/cplus

❏ Kernel Parameters

For a list of kernel parameters, see the VPO Administrator’s Reference Volume I. You can verify and change the kernel parameters using the setup tool.

NOTE 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

_libcxx_V60200002_libcxx_V60200003_libcxx_V60300001

| 0004396996916008 | G | 0000000000000000| 0004396996916016 | G | 0000000000000000| 0004396996918728 | G | 0000000000000000

Chapter 11326


❏ DCE Runtime Kit

One of the following:

• DCERTS20x DCE Runtime Services V2.0

• DCERTS30x DCE Runtime Services V3.0

NOTE VPO supports DCE versions supplied with the Tru64 UNIX operating system. However, although the Tru64 UNIX operating system includes DCE up to version 5.0A, DCE has to be installed separately as an optional product.

❏ Japanese Base System

IOSJPBASE4xx Japanese Base System. This system is only for managed nodes running Tru64 UNIX in a Japanese environment.

❏ Package: OSFINCLUDE440

OSFINCLUDE440 Standard Header Files package is required for building executables on Tru64 UNIX nodes.

Chapter 11 327

About Tru64 UNIX Managed NodesInstalling and De-installing Agents

Installing and De-installing AgentsThis section describes how to install and de-install Tru64 UNIX managed nodes.


When installing Tru64 UNIX managed nodes, follow these guidelines:


The name of the management server must be known to the managed node.

That is, the name of the management server must be registered on the name server or in the local host table:

/etc/hosts


❏ Agent Software

The VPO agent software is installed on the following file tree:

/usr/opt

If there is not enough space for installation of the VPO agents, create a symbolic link before installing VPO.

For example, if /bigdisk is a local file system with enough free space, enter the following:


ln -s /bigdisk/OV /usr/opt/OV

In a cluster environment, you must verify that /bigdisk is also accessible from all cluster clients, and that it is mounted from all client nodes. For example, the local file system /bigdisk on the cluster client must be mounted to the exported file system /bigdisk on the cluster server.

Chapter 11328


❏ Logfile Encapsulator

By default, some logfiles monitored by the logfile encapsulator are not present on Tru64 UNIX managed nodes.

For example:

/var/adm/messages, /usr/adm/lplog or /var/adm/sialog.

To add /var/adm/messages and /usr/adm/lplog to the managed node, add the following to the /etc/syslog.conf file:

kern.debug /var/adm/messages

lpr.debug /usr/adm/lplog

To add /var/adm/sialogr to the managed node, enter the following:

touch /var/adm/sialogr

❏ DCE RPC and NCS RPC

Before installing the VPO agent software on Tru64 UNIX managed nodes, make sure to set up and configure DCE RPC or NCS RPC correctly. Tru64 UNIX managed nodes support both DCE RPC and NCS RPC as communication types.

Chapter 11 329


To Configure DCE

To configure DCE, follow these steps:

1. In a terminal window, enter the following:

dcesetup

This command starts the dcesetup program.

2. Choose the following menu option:

1) Configure.

3. When prompted, enter y to confirm the selection.

4. When prompted, enter y to reconfigure the DCE client.

5. Select the option that best suits your needs:

❏ RPC Only

If you have installed DCE 3.x but do not want advanced DCE features, select this option:

6) Configure this system for RPC only.

❏ DCE Client

If you have installed DEC 2.x or 3x and want advanced DCE features, do this:

a. Select this option:

1) Configure this system as a DCE Client.

You are then prompted with the following question:

Would you like to search the LAN for known cells?

b. Respond to the prompt as follows:

• Automatic Setup

If you have configured cells and want the DCE setup utility to find them, enter y. When prompted with additional questions, accept the default answers offered by dcesetup.

• Manual Setup

If you want to manually configure a client to use an existing cell, enter n and the name of the cell: ito. This cell must be configured on the DCE server.

Chapter 11330


When prompted, do the following:

1. Enter the hostname of the Master CDS Server.

2. Indicate that the cell you are configuring can broadcast to the Master CDS Server by entering y.

3. If the time displayed is correct, enter y.

4. Choose whether you want run Distributed Time Service (DTS) on the node.

5. Choose whether you want to enable DCE SIA.

6. Enter the principal name (for example, cell_admin) and password for the DCE server.

7. Enter y to delete the principals.

6. When prompted, enter y to verify the configuration.

VPO configures the managed nodes as a DCE client and starts the DCE daemon dced.

Removing an Existing DCE Configuration

To remove an existing DCE configuration, use the following options from the main menu:

❏ 6) Clean

❏ 7) Clobber

Chapter 11 331


Installing Agents



/var/adm/smlogs/setld.log


In some situations, you may want to install the VPO HP-UX agent software without using the management server. This manual installation enables you to prepare the system to become a VPO managed node when it is later connected to the network. Manual installation is useful if you are preparing many systems in a central location, or if you want to avoid the network root connection necessary for standard installation.



• opc_pkg.Z

• comm_pkg.Z

• perf_pkg.Z

• opc_inst


/var/opt/OV/share/databases/OpC/mgd_node/vendor/dec/ \ alpha/unix/A.07.00/RPC_DCE_[TCP|UDP]/

2. Install the agent using the command:

/tmp/opc_inst

Chapter 11332


Activating the Managed Node

After the node with the pre-installed agent is connected to the network (“To Activate the Node from the Command Line” on page 335), you can activate and register the managed node.

You can you can activate the managed node from the following:

❏ VPO GUI

❏ Command Line


To activate the node from the VPO GUI, follow these steps:






3. Open the Install/Update VPO Software and Configuration window.


Actions-> Agents-> Install / Update SW & Config.

Chapter 11 333


4. Update all components.

In the Install/Update VPO Software and Configuration window, do the following:

a. Select all components.

CAUTION Do not check [Force Update]. If you check this option, the management server re-installs the agent

b. Click [OK].

Depending on whether you have pre-installed the agent, the management server does the following:

• If you have pre-installed the agent on the node, the management server activates the node, and installs the selected components.

• If you have not pre-installed the agent software, the management server installs the agent.

5. Verify that the control, message, and action agents are all running on the managed node.



Chapter 11334


To Activate the Node from the Command Line

To activate the agent on the node from the command line, follow these steps:

1. Install the agent on the node manually.

To find out how to install the agent manually, see “Installing Agents Manually” on page 332.






4. Activate the node.


/opt/OV/bin/OpC/install/opcactivate -s <VPO_mgt_server> \-cs <server_codeset> -cn <agent_codeset>


• Specifying the -s option with the opcactivate command is optional. This option starts the /opt/OV/bin/OpC/install/upd_res.sh script which integrates the VPO agent into the system startup and shutdown scripts, such as startup script in the /etc/init.d file.



Chapter 11 335


5. Update the database and start heartbeat polling for the node.

After the node is connected to the network, enter the following command on the management server:


The templates, monitors, commands, and so on must still be installed from the management server GUI. For instructions, see “To Activate the Node from the VPO GUI” on page 333.





/var/adm/smlogs/setld.log




2. De-install the VPO agent software from the managed nodes by entering:

setld -d OPCAGT000 OPCCOMMAGT000 OPCPERFAGT000

Chapter 11336

About Tru64 UNIX Managed NodesAbout Preconfigured Elements

About Preconfigured ElementsThis section describes preconfigured templates, template groups, and applications used by VPO on Tru64 UNIX managed nodes.


VPO uses one preconfigured template group:

❏ Digital UNIX


Table 11-1 shows encapsulated logfiles and associated template used on Tru64 UNIX managed nodes.

Table 11-1 Encapsulated Logfiles on Tru64 UNIX Managed Nodes


/var/adm/cron/log Cron logfile Cron

/var/adm/messages a Operating system messages OS Msgs

/usr/adm/sialog b SIA logfile SIA

/var/adm/wtmp History of logins Logs

/usr/adm/lplog c Line printer daemon logfile Lplog

a. /var/adm/messages must be present in the /etc/syslog.conf fileb. If /var/adm/sialog is not present, add it using the following

command:touch /var/adm/sialog

c. /var/adm/lplog must be present in /etc/syslog.conf file

Chapter 11 337


To Modify a Logfile Template

For detailed information about encapsulated logfiles, see the appropriate template in the VPO GUI.

NOTE Logfile templates are configured to collect information from logfiles that are produced by standard installations. If you are monitoring a non-standard installation, you should modify the templates to suit your special situation.

Before editing syslog.conf on your Tru64 UNIX system, read the man page syslog.conf(1M).

To modify a logfile template, follow these steps:

1. If /var/adm/messages is not already included in the /etc/syslog.conf file, add the following line (using tabs, not spaces):

kern.debug /var/adm/messages

2. Create the following file:

/var/adm/messages

For example, use the touch command with the following ownership and permission:

-rw-r----- 1 root adm messages

3. Restart the syslogd process.

No SNMP Event Interception

The VPO event interceptor is not supported on Tru64 UNIX managed nodes.

Chapter 11338



Table 11-2 describes the default monitored objects used by VPO on Tru64 UNIX managed nodes.






95% 2


90% 10


0.5 5

MailQueue Length


30 2


0.5 5



Chapter 11 339

About Tru64 UNIX Managed NodesDistributing Scripts and Programs

Distributing Scripts and ProgramsFor Tru64 UNIX managed nodes, the platform selector and architecture identifier is the following:

dec/alpha/unix






/var/opt/OV/share/databases/OpC/mgd_node/customer\/dec/alpha/unix/actions/*


/var/opt/OV/share/databases/OpC/mgd_node/customer\/dec/alpha/unix/monitor/*


/var/opt/OV/share/databases/OpC/mgd_node/customer\/dec/alpha/unix/cmds/*

Chapter 11340

About Tru64 UNIX Managed NodesDistributing Scripts and Programs







Temporary Directory

DEC Alpha AXP Tru64 UNIX /var/opt/OV/tmp/OpC/bin/actions/var/opt/OV/tmp/OpC/bin/cmds/var/opt/OV/tmp/OpC/bin/monitor


Managed Node

Operating System


DEC Alpha AXP

Tru64 UNIX

/var/opt/OV/bin/OpC/actions rwxr-xr-x(owner:root)



Chapter 11 341

About Tru64 UNIX Managed NodesOrganization of Managed Nodes

Organization of Managed NodesFigure 11-1 shows how VPO software is organized on Tru64 UNIX managed nodes.

Figure 11-1 VPO Software on Tru64 UNIX Managed Nodes

Location of Files

On Tru64 UNIX managed nodes, files are located as follows:


/var/opt/OV/tmp/OpC



bin conf tmp log

/usr/opt/OV

OpC OpC OpCOpC

install

liblocale

<lang>

bin conf

/var/opt/OV

include

LC_MESSAGES

B

B

bin

OpC

utils

B


Key:

contrib

OpC

databases

BBC

Chapter 11342



If they do not already exist, the default VPO operator opc_op and group opcgrp are created. You add user opc_op and group opcgrp only locally on the managed node (with useradd or groupadd).

If the managed node is a Network Information Service (NIS or NIS+) client, the VPO installation checks if user opc_op is already in the NIS database:

❏ If opc_op is in the NIS database, no additional user is installed.

❏ If opc_op is not in the NIS database, opc_op is added only locally on the managed node.


The default VPO operator appears in the following directory:

/etc/passwd


User Name opc_op


User-ID Either 777 (if still available) or next possible free number

Group-ID Either 77 (if still available) or next possible free number


Home Directory /usr/users/opc_op

Login Shell /bin/sh

Chapter 11 343



The default VPO operator group appears in the following directory:

/etc/group


Group Name opcgrp



Users opc_op



During installation, VPO makes changes in the following system resource files:

/etc/passwd/etc/shadow (if present) Default VPO operator entry and


/etc/group Default VPO operator group entry.

/sbin/init.d/opcagt VPO startup and shutdown script.

/sbin/rc0.d Creates the K01opcagt file.

/sbin/rc2.d Creates the K01opcagt file.

/sbin/rc3.d Creates the S97opcagt file.

NOTE If you are working with Network Information Services (NIS or NIS+), you should adapt the user registration accordingly.

Chapter 11344

About Tru64 UNIX Managed NodesTypes of Libraries






/usr/shlib/libiconv.so

/usr/shlib/libdce.so

/usr/shlib/libdce_r.so (optional)

/usr/shlib/libphtreads.so

/usr/shlib/libpthread.so

/usr/shlib/libmach.so

/usr/shlib/libexc.so

/usr/shlib/libc.so

/usr/shlib/libcxx.so








/usr/shlib/libc.so









/usr/shlib/libc.so


/usr/opt/OV/lib/libnsp.so


-lopc_r -lopc_r -lopc_r


Chapter 11 345



On a DEC Digital AXP platform with Tru64 UNIX managed nodes, use the include file:

/usr/opt/OV/include/opcapi.h

NCS Library N/A libopc.so libopc.so


N/A /usr/lib/libnck.a

/usr/lib/libc.a



/usr/lib/libnck.a

/usr/lib/libc.a




N/A -lopc -lopc




Chapter 11346


About the Makefile




❏ Makef.dec



NOTE For building executables on Tru64 UNIX nodes, OSFINCLUDE440 Standard Header Files package is required.

Chapter 11 347


Chapter 11348

12 About Windows NT/2000 Managed Nodes

Chapter 12 349

About Windows NT/2000 Managed NodesIn this Chapter

In this ChapterThis chapter explains how to install and configure HP OpenView VantagePoint Operations (VPO) on Microsoft Windows NT/2000 managed nodes.

NOTE In this manual, the term “Windows” refers to both the Windows 2000 and Windows NT operating systems.

Chapter 12350

About Windows NT/2000 Managed NodesInstallation Requirements

Installation RequirementsThis section explains VPO hardware and software requirements for Microsoft Windows NT/2000 managed nodes.


Before installing VPO, make sure that all involved systems meet these hardware requirements.

Requirements for the VPO Management Server

Make sure your VPO management server meets the following requirements:

❏ Client Software Bundle

The VPO management server must be installed with the client software bundle OVOPC-NT-CLT.

To verify that the bundle has been installed, enter the following:

swlist -l fileset OVOPC-CLT-ENG.OVOPC-NT-CLT

❏ Kernel Parameter Maxfiles

Use the following settings for kernel parameter maxfiles:

• 35 or Less Windows Managed Nodes

If your installation includes 35 or less Windows managed nodes, use the setting for the kernel parameter maxfiles described in the VPO Installation Guide for the Management Server.

• 36 or More Managed Nodes

If your installation includes 36 or more Windows managed nodes, increase the setting of maxfiles by the following:

3*Number_of_additional_NT_nodes + 15

Chapter 12 351


Requirements for the Windows Installation Server

If you are using a Windows Installation Server, make sure it meets the following requirements:

❏ Agent Processes

15 MB memory for agent processes.

❏ Local Drive

35 MB free disk space must be temporarily available on the drive that contains the FTP directory during installation.

❏ NTFS Disk

A total fo 65 MB of free disk space must be available on the NTFS-formatted disk:

• 50 MB for the installed agent files.

• 15 MB for the agent packages to be transferred to the managed nodes.

❏ Domain Controller

The Installation Server must be a domain controller.

Requirements for the Windows Managed Node

Make sure your VPO managed nodes meet the following requirements:

❏ Agent Processes

15 MB memory for agent processes.

❏ Local Drive

35 MB free disk space must be temporarily available on the drive that contains the FTP directory during installation.

❏ NTFS Disk

50 MB of space must be free on the NTFS-formatted disk for the installed agent files.

Chapter 12352



Before installing VPO, make sure the following software is installed on Windows managed nodes:



❏ Service Packs

The following Service Packs are required:

• Windows NT

Service Pack 5 or 6A

• Windows 2000

Service Pack 1 or 2

• Windows NT Terminal Server Edition

Service Pack 5 or 6A

NOTE For information about software requirements for a combination of Windows NT Terminal Server Edition and Citrix MetaFrame, see “About Citrix MetaFrame Integration” on page 430.

❏ FTP

FTP Service must be running (required during “FTP Agent Package” installation). The FTP service must have read/write permission for the FTP home directory and must not allow anonymous FTP access if the Administrator account is used.


The name of the management server must be known to the managed node. You can verify this by using the ping command.

❏ Default VPO Operator

The default VPO operator HP ITO account may not be removed from Windows managed nodes because the agents normally run under the operator’s account.

Chapter 12 353


❏ Schedule Service

Schedule service may not be disabled (required during installation)

❏ TCP/IP Services

TCP/IP services must be running and started automatically.

❏ RPC Services

RCP services (that is, the (Remote Procedure Call Service) must be running and started automatically.

❏ SNMP Services

SNMP services must be running if you plan to use discovery and other SNMP features of VPO.

❏ DHCP Service

DHCP (dynamic address service for Windows clients) may not be used because VPO relies on the IP address to identify the managed nodes.

Chapter 12354

About Windows NT/2000 Managed NodesInstalling and De-installing Agents

Installing and De-installing AgentsThis section describes how to install and de-install Microsoft Windows NT/2000 managed nodes.

About Installation

NOTE In this manual, a Windows installation server is an NT primary or backup domain controller with the VPO agent package installed, or a Windows 2000 domain controller with Active Directory installed.

Chapter 12 355


Figure 12-1 shows how to install Windows managed nodes.

Figure 12-1 Installing the VPO Windows Agent Package

Windows Windows

ftp installation

TRUSTstandard installation

Stand-aloneWindowsSystem

ftp installation

Domain 1 Domain 2

standard installation

Possible only if Domain 2 gives administrative rights to the HP ITO account in

standard installationDomainController

DomainController

VPO Management Server

Chapter 12356



Depending on how your network is configured, you can use one of the following methods to install the VPO agent package on Windows managed nodes:

❏ FTP Installation

Use this method to install or upgrade agents on system with FTP services running.

See “Installing Agents through FTP” on page 361.


Use this method to install or upgrade agents on the following:

• System that has an installation server in its domain.

• System in a domain that gives administrative rights to the HP ITO account on an installation server in another domain.


❏ FTP Re-installation

Use this method to re-install agents on the following:

• System that already has an agent running.

• System with FTP services running.

See “Re-installing Agents through FTP” on page 372.

❏ Manual Installation

Use the standard installation method to install or upgrade agents on the following:

• Windows system that is not yet connected to the network.

• Windows system that is connected to a network where an FTP connection with write permission is either impossible or inadvisable.

• Windows system on which the VPO agents should run under an account other than the HP ITO account.

See “Pre-installing Agents Manually” on page 376.

Chapter 12 357


About VPO Agent Accounts

By default, the VPO agents are installed and run under the account HP ITO account. If required, the agents can run under alternative accounts. See the following sections for more information about the HP ITO account and about what you should consider if you choose alternative account.

About the “HP ITO account”

By default, the standard installation of the VPO agent package on a Windows managed node installs the HP ITO account as a member of the Administrators group. As a result, the standard installation gives the account all those user rights that are available under Windows.

Although it is essential that the HP ITO account be a member of the Administrators group, only those user rights listed in Table 12-1 are required by the account to function correctly. All other user rights associated with the HP ITO account by membership in the Administrators group may be removed or granted as required.

NOTE Taking away user rights directly from the HP ITO account will result in reduced functionality.

Table 12-1 Required User Rights for the “HP ITO account”

User Right Required in VPO

Access a computer from the network. By Windows installation server.

Act as part of the operating system. By VPO action agent to switch user.

Increase quotas. By the action agent to switch user for application execution.

Log in as a service. By VPO agent, which runs as a service.

Manage auditing and security log. During action execution.

Replace a process-level token. By the action agent to switch user.

Shut down the system. By the shutdown application.

Chapter 12358


About Alternative Accounts

The VPO agents can be installed and run under any account, including the SYSTEM account. If you want to choose an account other than the HP ITO account, you must install the agents using the manual or FTP installation method. See “Pre-installing Agents Manually” on page 376 for more information about the installation procedure.

When choosing an alternative account, beware of the following implications:

❏ Applications and monitors

Applications that are configured to run under the account opc_op or HP ITO account must be changed manually. Specify the same account that you choose for the VPO agents.

All monitor executables run under the account specified for the VPO agents. This may restrict some of the access rights to monitored applications.

The SYSTEM account does not have any network access capabilities.

❏ Choosing the SYSTM account

If you choose the SYSTEM account, VPO does not create any account, not even the account opc_op.

If you choose the SYSTEM account for a Domain Controller, you can no longer install the VPO agents on remote systems using the Domain Controller as the installation server because the SYSTEM account does not have any access rights for remote systems. To enable remote installations, configure the HP ITO Installation Service on the Domain Controller to run as a domain user that has domain admin user rights.

❏ Choosing a new account

If you choose a new account, the account will be created as a member of the Administrators group and the agents will be installed using the specified account name. If an agent with a different account already exists on the system, the new agent will be installed under the new account name. Remove the existing account manually if you no longer need it.

Chapter 12 359


❏ Choosing an existing account

If the specified account already exists on the system but, the passwords do not match, the existing account is removed and recreated with the same name but a different internal user ID.

❏ No account specified

If no account is specified, the installation will check for an existing agent installation. If an agent already exists, the same user account will be used for the installation. If no agent is detected, the installation will create the default HP ITO account.

Chapter 12360


Installing Agents through FTP

This section explains how to use the File Transfer Protocol (FTP) to install the agent package from the VPO management server to a Windows domain controller that does not currently have the agent running.

Installing the First Agent

Use the FTP installation method for your first Windows agent package installation, or if you need to create an installation server in a domain that does not give administrative rights to the HP ITO account on an installation server in another domain. You must perform this type of installation at least once. The installation method requires FTP services and one manual step on the Windows system.

Installing Additional Agents

If an installation server is already available, and you want to install VPO agent software on additional Windows nodes, see “Installing Agents with Standard Installation” on page 367.

Chapter 12 361


To Install an Agent through FTP

To install a VPO agent on Windows managed nodes using the standard installation method, follow these steps:

1. Make sure that your systems meet all installation requirements.

Check the “Installation Requirements” on page 351.

2. Select Window: Node Bank from any submap to display the VPO Node Bank window.

3. Select Actions: Node: Add… to display the Add Node window.

4. In the Add Node window, fill in the following fields:

Label Enter the name of the node as you want it to appear in the VPO Node Bank.

Example:

ntserver

Hostname Enter the complete hostname of the Windows domain controller that you want to set up as the Windows installation server.

Example:

ntserver.com.

After you enter this name and press Return, VPO looks up and verifies the IP address, as well as the net type, machine type, and operating system name.

Make sure the operating system name is Windows NT/2000.

If SNMP services are not running on the Windows node, VPO cannot detect the machine type and operating system name. In this case, select Windows NT/2000 and continue with the installation.

As User Enter the administrator’s user name, or even anonymous if the FTP server allows it.

If you are using the administrator’s user name, anonymous FTP access must be disabled on the node.

Chapter 12362


5. Click [Communication Options] to display the Node Communication Options window.

6. In the Node Communication Options window, fill in the following fields:

Installation Drive Enter the letter of an NTFS drive with 10 megabytes of disk space for the agent software. If the drive that you specify does not have enough space, or if you leave this field blank, VPO searches the available local drives for an NTFS drive that has enough free space.

Installation Server Leave this field blank. An installation server is not yet available for this domain. Remember, you are creating an installation server with this procedure. If you enter anything in this field, VPO generates an error message when the installation script runs.

7. Click [Close] to dismiss the Node Communication Options window, then [OK] to dismiss the Add Node window.

The VPO Node Bank window now shows a new symbol with the label you entered in the Label field (for example, ntserver).

8. Add the new node to a node group so that it can be managed by an VPO operator:

a. Open the VPO Node Group Bank window.

b. Double-click the node group to which you want to add the node.

Add a new node group if you do not want to use one of the VPO default node groups. Remember to assign any new node groups to an operator.

c. Drag the node from the VPO Node Bank window and drop it into the submap of the node group.

9. Reload the message browser.

Chapter 12 363


10.Display the Install/Update VPO Software and Configuration window:

a. Click the new icon to highlight it.

b. Choose Actions:Agents->Install/ Update SW & Config….

11.Under Target Nodes, do this:

a. Select [Nodes in list requiring update].

b. Click [Get Map Selection].

The node name appears in the window.

12.Under Components, do this:

a. Select [Agent Software].

b. Click [OK].

The installation begins. A new shell opens and starts the installation script.

13.When prompted for the as user password, give the password of the Windows system administrator.

14.When prompted for the password of the HP ITO account, do one of the following:

• Specify a password.

• Press Enter.

VPO creates a password for you.

CAUTION If you are installing the VPO agent software on a domain controller, do not let VPO create a password for you. Instead, specify your own password. You will need this password again when installing on another domain controller.

The installation script then installs the agent package on the Windows system.

Chapter 12364


IMPORTANT You perform the next five steps on the Windows system. If the Windows system is not physically near you, you can ask someone at the system to perform these steps.

15.On the Windows system, log in as the administrator and open an MS-DOS command prompt.

If you have read/write access to the FTP home directory drive, you can also install the agent through anonymous FTP with the username ftp and the password ftp.

16.On the Windows system, switch to the FTP home drive and directory.

17.On the Windows system, change directory to:

temp

18.On the Windows system, enter the following:

opc_inst

This command invokes a script that takes about two minutes to execute. The script sets up the domain controller as the Windows managed node. This managed node can also function as the installation server for all other Windows nodes.

The installation is complete when you see the following line:

Installation program successfully finished

Chapter 12 365


19.If the installation fails, check the contents of the installation logfile:

C:\temp\inst.log.

to find the cause of the terminated installation, examine the logfile for lines that begin with

E->

You can also verify the installation by checking the Windows services window and looking for the entry HP ITO Agent, which should be running. (The HP ITO installation service will not be running. The HP ITO installation service runs only when you install the agent on another Windows system.)

IMPORTANT You perform the next step on the VPO management server.

20.On the VPO management server, verify that the agent is running on the Windows node:

a. Highlight the node icon.

b. Double-click on the VPO Status application in the VPO Application Bank window.

This application returns the status of the VPO agent processes. If the agent processes are running, you know that the Windows agent is installed and that the Windows domain controller is functioning as the Windows installation server.

If you want to view the installation log, use the VPO Install Log application in the VPO Application Group: NT Tools window.

Chapter 12366



This section describes how to install VPO agents on managed nodes in a Windows system using the standard installation method. To learn about other installation methods, see “Methods for Installing Agents” on page 357. For general VPO installation instruction, see the VPO Administrator’s Reference Volume I.

Domain Requirements for a Standard Installation

Before you begin the standard installation, make sure a Windows installation server is available in one of the following domains:

❏ Domain of the system you are installing.

❏ Some other domain where the HP ITO account has administrative rights for the system on which you want to install the agent.

If an installation server that meets these requirements is not available, create one by using the procedure explained in “Installing Agents through FTP” on page 361.

VPO Requirements for a Standard Installation

Make sure that the latest version of the VPO agent software is installed on the installation server. For details, see “Hardware Requirements” on page 351.

Although an installation server can install the agent package on systems in other domains, you should install the agent package only on systems in the domain of the installation server. The process of creating an installation server automatically installs the HP ITO account on the domain controller, where it has the necessary rights throughout the domain. If the HP ITO account does not have administrative rights throughout the domain, you have to manually assign them on each system where you install the agent.

For more information on rights and permissions for the HP ITO account, see “About the “HP ITO account”” on page 358.

Chapter 12 367


FTP Requirements for a Standard Installation

A standard installation does not require FTP services, and can be performed on any Windows system within the domain of the installation server domain. You can perform a standard installation on the primary or backup domain controller of any domain that grants administrative rights to the HP ITO account of another installation server. The primary or backup domain controller can thus be used to create other installation servers in other domains.

To Install an Agent with Standard Installation

To install a VPO agent on Windows managed nodes using the standard installation method, follow these steps:

1. Make sure that your systems meet all installation requirements.


2. Select Window: Node Bank from any submap to display the VPO Node Bank window.

3. Select Actions: Node->Add… to display the Add Node window.

4. In the Add Node window, fill in the following fields:

Label Enter the name of the node as it should appear in the VPO Node Bank.

Example:

ntworkstation

Chapter 12368


Hostname Enter the complete hostname of the Windows system where you want to install the agent.

Example:

ntworkstation.com

After you enter this name and press Return, VPO looks up and verifies the IP address, as well as the net type, machine type, and operating system name.

Make sure the operating system name is Windows NT/2000.

If SNMP services are not running on the Windows node, VPO cannot detect the operating system name, net type, and so on. In this case, select Windows NT/200 and continue with the installation

5. Click [Communication Options] to display the Node Communication Options window.


Installation Drive Enter the letter of an NTFS drive with 10 MB of disk space for the agent software. If the drive that you specify does not have enough disk space, or if you leave this field blank, VPO searches the available drives for an NTFS drive that has enough free disk space.

Installation Server Enter the name of an Windows domain controller that has been set up as an installation server (and is in the same domain, or has administrative rights for the HP ITO account in this domain).

Example:

ntserver.com

7. Click [Close] to close the Communication Options window.

8. Click [OK] in the Add Node window.

Chapter 12 369


9. Add the new node to a node group so that it can be managed by an VPO operator:

a. Open the VPO Node Group Bank window.

b. Double-click the node group to which you want to add the node.

Add a new node group if you do not want to use one of the VPO default node groups. Remember to assign any new node groups to an operator.

c. Drag the node from the VPO Node Bank window and drop it into the submap of the node group.

10.If you added a new group, configure the message browser to receive messages from this new group:

• If the message browser is open, it prompts you for a restart when you finish the step above.

• If the message browser is not open, add the new node group and open the message browser now.

NOTE You can monitor the rest of the installation by looking at messages received in the message browser.

11.Display the Install/Update VPO Software and Configuration window:



12.Under Target Nodes, do this:




Chapter 12370




b. Click [OK].


14.When prompted for the password of the HP ITO account, do one of the following:

• Specify a password.

• Press Enter.


CAUTION If you are installing the VPO agent software on a domain controller, do not let VPO create a password for you. Instead, specify your own password. You will need this password again when installing on another domain controller.

When installing the agent on another domain controller, use the password of the HP ITO account on the domain controller where you first installed the agent software.

The installation script then installs the agent package on the Windows system.

15.Verify that the agent is running on the Windows node.

a. Highlighting the node icon.

b. Double-click on the VPO Status application in the VPO Application Bank window.

This application returns the status of the VPO agent processes. If they are running, you know that the Windows agent is installed and that the Windows domain controller is functioning as the Windows installation server.

If you want to view the installation log, use the VPO Install Log application in the VPO Application Group: NT Tools window.

Chapter 12 371


If an Error Occurs During a Standard Installation

If errors occur during a standard installation, check the local installation logfile:

c:\temp\inst.log

NOTE NT Terminal Server Edition only:

If, for some reason, the VPO agents were not correctly installed and do not work properly, manual installation is recommended. For instructions, see “Pre-installing Agents Manually” on page 376

Re-installing Agents through FTP

This section explains how to use a Windows installation server to re-install or upgrade the agent package that was originally installed on Windows systems using the FTP installation method (see “Installing Agents through FTP” on page 361). To learn about other installation methods, see “Methods for Installing Agents” on page 357.

Re-installing the First Agent or an Installation Server

Use the FTP re-installation method to re-install or upgrade the following:

• Agent Package

Re-install or upgrade the agent package on the first Windows primary or backup domain controller.

• Installation Server

Re-install or upgrade an installation server in a domain that grants administrative rights to an HP ITO account in another domain that contains an available installation server.

Re-installing Additional Agents

If an installation server is already available, and you want to re-install or upgrade VPO agent software on additional Windows nodes, see “Installing Agents with Standard Installation” on page 367.

Chapter 12372


To Re-install an Agent through FTP

To re-install or upgrade a VPO agent on Windows managed nodes using the FTP re-installation method, follow these steps:

1. Make sure that your systems meet all the listed requirements.


2. Select Window: NodeBank from any submap to display the VPO Node Bank window.

3. Select Actions:Node:Modify… to display the Modify Node window.

4. Click [Communication Options] to display the Node Communication Options window


Installation Drive Enter the letter of an NTFS drive with 10 MB of disk space for the agent software:

• If the drive that you specify does not have enough space, or if you leave this field blank, VPO searches the available local drives for a disk that has enough free space.

• If you are re-installing the VPO agent software, enter the letter of the NTFS drive where the agent software was installed.

• If you want to re-install on a different NTFS drive, de-install the VPO agent software first, and then proceed with the ftp installation.

Installation Server Enter the complete hostname of the Windows system where you want to install the agent.

Example:

ntsystem.com

6. Click [Close] to close the Node Communication Options window.

7. Click [OK] to close the Modify Node window.

Chapter 12 373


8. Display the Install/Update VPO Software and Configuration window:



9. Under Target Nodes, do this:






b. Click [OK].


When prompted for the Administrator password, give the password of the Windows system administrator.

When prompted for the password of the HP ITO account, do one of the following:

• Specify a password

• Press Enter.


CAUTION If you are installing the VPO agent software on a domain controller, do not let VPO create a password for you. Instead, specify your own. You will need this password again when installing on another domain controller.

The installation script then installs the agent package on the Windows node. You will not receive any installation messages in the message browser until the installation is complete.

Chapter 12374


11.Verify that the agent is running on the Windows node:

a. Highlight the node icon.

b. Double-click the VPO Status application in the VPO Application Bank Window.

This application returns the status of the VPO agent processes. If they are running, you know that the Windows agent is installed and that the Windows domain controller is functioning as the Windows installation server.

To view the installation log, use the VPO Install Log application in the VPO Application Group: NT Tools Window.

Chapter 12 375


Pre-installing Agents Manually

In some situations, you may want to pre-install the VPO Windows agent software on a Windows PC without using the management server.

When to Pre-install Agents Manually

Pre-installation makes it possible to prepare the PC to become a VPO managed node when it is later connected to the network. Preparing the PC in this way may be useful if a large number of PCs are prepared in some central location, or if you want to avoid using the root connection over the network that is necessary for a standard agent installation.

The manual installation method also allows you to specify an agent account other than the standard HP ITO account.

To Pre-install a Windows Agent on a Windows PC

To pre-install a Windows agent on a Windows PC that will become a VPO managed node, follow these steps:

1. Copy files from the management server to the managed node:

• Source Directory on the Management Server

/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms\/intel/nt/A.07.00/RPC_DCE_TCP/

• Destination Directory on the Managed Node

C:\temp

• Files to be Copied

— opc_pkg.Z— opc_pre.bat— unzip.exe— unzip.txt— opcsetup.inf— opc_inst.bat

Rename opc_pkg.Z to opc_pkg.zip.

Chapter 12376


2. Edit the opcsetup.inf file.

Change the entries for Setup Drive and Management Server as appropriate:

[Setup Drive] C:[Management Server]management_server.domain.com [Account Password](empty by default)[HP ITO Version] A.07.00[Agent Architecture]ms\intel\nt

NOTE If you leave the password line empty, VPO generates a random password.

If you want to use a specific password, encrypt it on the VPO management server with the opcpwcrpt tool under:

/opt/OV/bin/OpC/install

If you are installing the VPO agent software on a domain controller, do not let VPO create a random password for you. Instead, specify your own password. You will need this password again when installing on another domain controller.

Add the following entries to the opcsetup.inf file if you want to install the VPO agents under an account other than the HP ITO account:

[Agent User]account name

Where account name is the name of the account to be used. Specify SYSTEM to use the built-in accounts. Note that account names may not contain space characters. See “About Alternative Accounts” on page 359 for more information.

Chapter 12 377


3. Create the following file on the managed node:

• Directory

C:\temp

• File

nodeinfo

• Contents

OPC_NODE_TYPE CONTROLLEDOPC_MGMTSV_CHARSET iso885915 (or sjis for Japanese)OPC_NODE_CHARSET acp1252 (or acp932 for Japanese)OPC_COMM_TYPE RPC_DCE_TCP

OPC_NSP_TYPE [NONE | SECRET]1

OPC_NSP_VERSION 01

4. From a command prompt on the Windows PC, run the setup batch file:

C:

cd \temp

opc_pre.bat

5. On the management server, add the Windows node to the appropriate node group.

6. When the Windows PC is connected to the VPO management server, update the database and start hearbeat polling for the Windows node:


1. Use NONE for a standard VPO agent installation. To install the agent in conjunction with VantagePoint Advanced Security, see the VPAS Installation and Concepts Guide for more information.

Chapter 12378



This section describes how to de-install VPO agents on Windows managed nodes.

NOTE If you are de-installing the VPO agent software from a Windows Domain Controller, the accounts for the domain users HP ITO account and opc_op must be deleted manually after the de-installation of the VPO agent software.




To de-install the VPO agent software manually from Windows managed nodes, follow these steps:

1. Stop all VPO agents running on the managed node

2. Run the following command:

\usr\OV\bin\OpC\opcsetup -u

If Errors Occur During De-installation


c:\temp\inst.log

Chapter 12 379

About Windows NT/2000 Managed NodesAbout Preconfigured Elements

About Preconfigured ElementsThis section describes preconfigured templates, template groups, and applications used by VPO on Windows managed nodes.

NOTE For detailed descriptions of the default applications in the VPO Application Bank window, see “Types of Default Applications” on page 392.

Types Preconfigured Template Group

Table 12-2 lists the preconfigured template groups used by VPO:

Table 12-2 Template Groups for Windows Systems

Windows Version Template Group

Windows NT Windows NT

SMS

Windows 2000 Windows 2000

Terminal Server/Citrix MetaFrame Template Groups

Terminal Server/MetaFrame

Terminal Server a

MetaFrame a

a. Contained within the Terminal Server/MetaFrame template group.

Chapter 12380



VPO provides logfile templates for managed nodes on the following platforms:

❏ Windows NT

❏ Windows 2000

❏ Windows NT Terminal Server

NOTE The number of Windows Eventlog logfile templates that can be assigned to a managed node is limited to 62. The number of ASCII logfile templates is unlimited.

About Logfile Templates for Windows 2000

Table 12-3 shows encapsulated logfiles and associated templates used on Windows 2000 managed nodes.

Table 12-3 Encapsulated Logfiles on Windows 2000 Managed Nodes


DNS Server Monitors the DNS Server EventLog

dflt_DNSEvLog (2000)

Directory Service Monitors the Directory Service EventLog

dflt_DirectoryEvLog (2000)

File Replication Service Monitors the File Replication Service EventLog

dflt_FileReplicationEvLog (2000)

Chapter 12 381


About Logfile Templates for Windows NT Terminal Server

Table 12-3 shows encapsulated logfiles and associated templates used on Windows NT Terminal Server managed nodes.

Table 12-4 Encapsulated Logfile on Windows NT Terminal Server Managed Nodesa


SYSTEM_LOG NT system eventlog for Terminal Server

System Log (Terminal Server)

a. For encapsulated logfiles on managed nodes running a combination of Windows NT Terminal Server and Citrix MetaFrame, see “Object Thresholds on Citrix MetaFrame Managed Nodes” on page 433.

Chapter 12382


Monitoring Eventlogs on Windows Managed Nodes

In addition to the default logfile templates that are delivered with VPO, you can set up logfile templates to monitor other Eventlogs.

Syntax for Eventlogs

When setting up the templates, set up the fields as follows:

Logfile Must have the name of a Windows EventLog with the following syntax:

%<NAME>_LOG%

Example:

%SYSTEM_LOG%

File to be executed Should be empty if you are monitoring a Windows eventlog.

File to be read Should be empty if you are monitoring a Windows eventlog.

Polling Interval Ignored.

Logfile Character set Must be one of the following:

• ACP1252

English/Spanish language nodes

• ACP932

Japanese language nodes

Read from Last File Position Should be selected.

Chapter 12 383


Viewing Eventlogs in the Message Browser

Table 12-5 shows how eventlog fields are displayed in the message browser.

Table 12-5 Eventlog to Message Browser Field Correlation

Eventlog Field Message Browser Field Comments

Date Date The date that the event was created on managed node.

Time Time The time the event was created on managed node.

Event ID Message Text The Event ID will appear before any additional message texta.

Source Application None

Typeinformationwarningerror successaudit failureaudit

Severitynormalwarningcriticalnormalwarning

None

Category Object None

Description Message Text All other message text (after the Event ID).

User Not mapped Not mapped.

Computer Node The name of the node as it is known to the management server.

Msg Group Empty.

a. Formatted as: EventID: 0xnnnnnnnn (ai) - description text

Chapter 12384



Table 12-6 shows the opcmsg message templates that are available for Windows managed nodes.



Types of SNMP Traps



Example: System cold start, network interface up and down, and so on.




Table 12-6 opcmsg Message Templates on Windows Managed Nodes

Name Description

opcmsg(1|3) Default interception of messages submitted by opcmsg(1) and opcmsg(3).

Chapter 12 385








• SNMP Devices


Set the destination systems for SNMP devices on HP-UX nodes in the following file:



trap_dest:<nodename>







Chapter 12386




Chapter 12 387



Table 12-7 describes the default monitored objects used by VPO on Windows managed nodes.

NOTE For default monitored objects on nodes running a combination of Windows Terminal Server Edition and Citrix MetaFrame, see Table 12-14, “Object Thresholds on Citrix MetaFrame Managed Nodes,” on page 433

Table 12-7 Object Thresholds on Windows Managed Nodes

Object Description Threshold PollingInterval (Minutes)

dflt_disk_util_NT a Windows NT monitor for disk space utilization on disk drive C.

10% 10

dflt_cpu_util_NT Windows NT/2000 monitor for CPU utilization.

95% 1

dflt_rpcss_NT b Windows NT RPC service. 90% 30

TS_Licensing Checks if Terminal Server licensing service is running.

1 5

TS_Service Checks if Terminal Server service is running.

1 5

a. Not included in the Windows 2000 template group because the monitor does not automatically run on Windows 2000 managed nodes. The disk performance monitoring of the Windows 2000 operating system must be activated before the monitor can run successfully: enter diskperf -y on the Windows 2000 managed node and reboot the system.

b. Not included in the Windows 2000 template group.

Chapter 12388


Monitoring Windows Objects

You can configure the VPO Threshold Monitor to monitor objects in the Windows Performance Monitor.

To Monitor Windows Objects

To monitor Windows objects, follow these steps:

1. Set the Monitor to Program.

2. In the Monitor Program or MIB ID field, enter the following:

NTPerfMon\\

This case-sensitive designator should preface all requests to the Windows performance monitor.

Syntax for the Windows Performance Monitor

Figure 12-2 shows the syntax for requests.

Figure 12-2 Windows Performance Monitor Syntax

The language for the command may be either in English, or in the local language defined for the Windows system where the template will be used. English should be used if the template is intended for use in more than one system with different languages.

NTPerfMon\\LogicalDisk\\% Free Space\\0\\C:

ObjectCounter

Parent InstanceInstance

Chapter 12 389


Guidelines for Object and Counter Values

When entering Object and Counter values, follow these guidelines:

❏ Fixed Labels

The values are fixed labels that can be found for each object you want to monitor by using the Windows Performance Monitor (found in the NT Tools group).

❏ Case-insensitive Labels

The labels are not case-sensitive, but must include any spaces as shown in Figure 12-2 on page 389. In this example, LogicalDisk, logicaldisk, or LOGICALDISK will work correctly, but Logical Disk will not.

❏ Percent Sign in Labels

If you omit the percent sign (%) from the counter label, the monitor sometimes returns the raw value instead of the percentage. This depends on the Windows Performance monitor counter that is being monitored.

Chapter 12390


Guidelines for Parent Instance and Instance Values

When entering Parent Instance and Instance values, follow these guidelines:

❏ Valid Values

The values vary according to what is being monitored. The example in Figure 12-2 on page 389 shows the SCSI port and the drive letter. Valid values can be found using Windows Performance Monitor (found in the NT Tools group). Parent instance and instance of the example appear as 0==>C in the Performance Monitor.

❏ Question Marks

The fields may also be filled with a question mark (?), which will allow the string to match any valid value.

The example in Figure 12-2 on page 389 could be modified to look like this:

NTPerfMon\\LogicalDisk\\% Free Space\\? \\C:

In this case, the template would match the C: drive, regardless of which SCSI port it was associated with.

❏ Parent Instances

A parent instance may or may not exist. If there is no parent instance, simply omit it from the syntax.

If there were no parent instance for the example in Figure 12-2 on page 389, the line would look like this:

NTPerfMon\\LogicalDisk\\% Free Space\\C:

Locating Objects

VPO will attempt to locate the objects when the agent is started, or when a new template is assigned to the node. If VPO cannot immediately locate the object, it will wait for two minutes and then search again. If VPO cannot locate the object after five attempts, it will send a message to the message browser, notifying the administrator that the object could not be found. The monitor will not begin to search again until the agent is restarted, or the template is reinstalled.

Chapter 12 391

About Windows NT/2000 Managed NodesTypes of Default Applications

Types of Default ApplicationsThis section describes the default Intel-based applications in the VPO Application Bank window, naming the executable that is invoked, and the user-configurable switches, if any. This section is useful if you want to learn how existing Windows applications can be customized for your particular situation and requirements.

About “Cancel Reboot”

This application will cancel a system reboot command that was issued from the VPO reboot application for the selected Windows node.

Default

itosdown.exe /a

Description of Values Returned

See “About “Reboot”” on page 406.

Chapter 12392


About “Diagnostics”

This application collects general diagnostic information for the selected Windows node.

Default

itodiag.exe (returns all information listed below)

User Configurable Parameters

osversion Returns operating system information.

hardware Returns hardware information:

• BIOS information

• Processor type:

— 386

— 486

— 586 (Pentium)

— x686 (Pentium Pro)

• Number of processors in the system

memory Returns the following memory information:

• Total paging file size (Windows swap file)

• Available paging file

• Physical location of the page file and its limits (minimum, maximum)

network Returns network information.

nonwdrives Stops itodiag from collecting information about NAME, FILE SYSTEM, TOTAL, and FREE for each mapped network drive. Useful in conjunction with the drives parameter.

This is useful when the agent user account (HP ITO account) has no permissions on one of the drives and the collection causes a login failure on the node that provides the network drive.l.

Chapter 12 393


drives Returns the information listed below for each drive:

DRIVE Returns current drive letter.

NAME Returns any name that is assigned to that drive.

TYPE Returns one of these four types of drive:

• REMOVABLE

Floppy drive

• REMOTE

Network connection

• FIXED

Local hard drive

• CD-ROM

CD disk drive

FILE SYSTEM Returns one of these file system types:

• NTFS

• NTFAT

• DOS

• HPFS

• OS/2

TOTAL Returns the total size of the drive in MB.

FREE N/A is reported for the name, file system, and total and free space if the drive is not fixed and the disk is currently inserted (floppy drive or CD- ROM) or if there is a network connection that requires a password (which is case for administrator connections C$, D$, and so on.).

Chapter 12394


processes Returns the following process information:

• ID

• Name

• Priority (higher number is higher priority) and other information

cpuload Returns CPU load information for each processor on the system:

Processor time Returns the percentage of elapsed time that a processor is busy executing a non-idle thread. This can be regarded as the fraction of the time spent doing useful work. Each processor is assigned an idle thread in the idle process that consumes those unproductive processor cycles not used by any other threads.

Private time Returns the percentage of processor time spent in Privileged Mode in non- idle threads. The Windows service layer, the Executive routines, and the Windows Kernel execute in Privileged Mode.

User Time Returns the percentage of processor time spent in User Mode in non-idle threads. All application code and subsystem code executes in User Mode.

Interrupts/s Returns the number of device interrupts the processor is experiencing. A device interrupts the processor when it has completed a task or when it otherwise requires attention.

Chapter 12 395


Ipconfig Returns the Windows IP Configuration.

This consists of the following:

• Ethernet adapter card name

• IP Address

• Subnet Mask

• Default Gateway

Description of Values Returned:

Refer to the User Configurable Parameters for this application.

Chapter 12396


About “Installed Software”

This application returns the names of the software that has been entered in the registry on the selected Windows node. Only Windows software that has created a subtree in the registry is listed. Older software (for example, Windows NT 3.51) is not shown.

This function returns all the subtrees from the registry “local machine” under the key “Software”. All software written for Windows create a subkey under “Software” to store external parameters. The itoreg.cfg file is used to filter out unwanted information. For a sample itoreg.cfg file, see “About “Reg Viewer”” on page 407.

Default

itoreg.exe /enum 3 /key Software /initkey lm


/enum X Returns the subtrees from the specified key. Information is printed out to the depth specified by X.

/key <NAME> Defines the starting point of the subtree to be processed.

/initkey Defines in which registry have to search for <key>.

NOTE For a full description of the Windows registry, see the Windows documentation.


See the User Configurable Parameters for this application, as well as the Windows documentation.

Chapter 12 397


About “Job Status”

This application returns a list of the scheduled jobs entered by the at function. If the schedule service has not been started, the message The service has not been started is returned. If nothing is scheduled on the target node, the message There are no entries in the list is displayed. Otherwise a list of commands is displayed along with the times at which they are scheduled to run.

Default

at.exe


For a full description of creating and removing scheduled jobs, see the Windows documentation.

Chapter 12398


About “LM Sessions”

This application lists sessions between the selected Windows node and other computers on the network. If the selected system is acting as a logon server, it shows sessions of the users for which it has validated logins. If no user name is shown by the entry, it indicates that a service has created this session connection.

Default

net.exe sessions


For a full description of net.exe, see the Windows documentation.


Computer The name of the system that has made the connection.

User name Name of the user. If this field is blank it means that the Windows system has a connection, which is typical when a service has made a log-on.

Opens The number of open resources associated with the connection.

Idle time Time since this connection was last used.

Chapter 12 399


About “Local Users”

This application prints the name of the user who is locally logged onto the selected Windows node. If you need more information about the users and sessions, use the Show Users application.

Default

itouser.exe /local


See “About “Show Users”” on page 416.


See “About “Show Users”” on page 416.

Chapter 12400


About “Memory Load”

This application returns information about the current memory usage of the selected Windows node. If you need more information about the Windows node, use the Diagnostics application.

Default

itodiag.exe /memory


See“About “Diagnostics”” on page 393.


See “About “Diagnostics”” on page 393.

Chapter 12 401


About “NetBios Sessions”

This application displays protocol statistics and current TCP/IP connections using NBT (NetBIOS over TCP/IP) for the selected Windows node.

Default

nbstat.exe -s


For a full description of nbstat.exe, see the Windows documentation.

Chapter 12402


About “PerfMon Objs”

This application returns all of the performance objects that are defined on the selected Windows node. A non-English Windows installation returns the objects in both the local language and the default language (US English). This application is used mostly by the administrator to make the configuration of threshold monitors on Windows systems easier.

Default

opcprfls.exe


/a By default, returns all the performance monitor objects found on the system.

/o <string> Returns only objects that match the string, starting from the beginning of the object. For example, /o s returns the objects system, server and server work queues, while /o sy returns system and /over matches nothing and returns an error message.

/s By default, returns a maximum of ten instances. If more are defined it will print out the message “MULTIPLE INSTANCES, TOO MANY TO LIST”.

/f Returns a full list and prints all instances, no matter how many are defined.

NOTE The performance objects are always stored in both US English and the local language if the local language is not also US English. For example, on a German Windows system, names are defined for all the objects in both US English and German. If opcprfls.exe finds a second language, the message “Second Language found” is displayed, and each object, counter, or instance thereof is returned in both US English and the local language. If an object does not have a local language name, only the US English name is printed. The VPO agent can monitor any of the performance objects in either US English or the local language, but US English is valid on all Windows machines, regardless of the local language.

Chapter 12 403



Refer to the “User Configurable Parameters” section for this application.

Chapter 12404


About “Process Kill”

This application kills all processes that are running under the configured name on the selected Windows node. If the user does not have the rights to kill the process, an error is returned.

Default

itokill.exe


/pid <process id> Kill process with id <process id>

/name <process name> Kill all processes with name <process name>.

/f Forced kill without notification.

/l List all processes. Because this function uses the registry to get all the process names, it does not show the extension.exe after executable files. This information is not stored in the registry.

NOTE Under Windows, a user with administrator rights can kill any process, but normal users can kill only processes that are running under their account name. If you want the VPO operator to be able to kill any process, configure the application to run under HP ITO account.


See the “User Configurable Parameters” section for this application.

Chapter 12 405


About “Reboot”

This application will shutdown and reboot the selected Windows nodes.

Default

itosdown.exe /t 120 /r /w


/m <msg> Returns shutdown <msg> in a popup window on the node.

/t <sec> Specifies the delay (in seconds) before the system shutdown occurs.

/a Aborts a VPO initiated system shutdown.

/r Automatic reboot after shutdown. If this option is not set, the system shuts down. It can then only be restarted manually.

/f Force system shutdown. Processes are not allowed to delay the shutdown for local user interaction (for example, to query whether data should be saved). Without this option, the shutdown might not occur because of processes running on the system.

/w Pop up a notification window. This allows the local user to cancel the shutdown process. If the local user cancels the shutdown process, the management server receives an error message.



Chapter 12406


About “Reg Viewer”

This application returns the values and subkeys for the define key of the Selected Windows node.

For example, to view the VPO agent configuration, modify the application to use the following:

/enum 1 /initkey LM /key Software\Hewlett-Packard\OpenView\ITO

Default

None. This application requires an entry listed in Table 12-8.

Table 12-8 Registry Viewer Application Options

To view a key/value:

/view /initkey lm|cu|cr|us /key <path> [/valuename <name>]

To set a key or value:

/set /initkey lm|cu|cr|us /key <path> [/valuename <name> /value <value> /type REG_SZ|REG_DWORD]

To delete a key or value:

/delete /initkey lm|cu|cr|us /key <path> [/valuename <name>] [/force] [/set]

To scan registry for pattern:

/scan <pattern> /initkey lm|cu|cr|us /key <path> [/view]

To enumerate a registry tree (thereby printing out registry keys to the set depth: enum uses a config file that verifies keys that should not be processed):

/enum <depth> /initkey lm|cu|cr|us /key <path> [/view]

To execute a registration script:

/file <filename> /initkey lm|cu|cr|us

Chapter 12 407



/initkey lm|cu|cr|us Define initial registry key:

lm KEY_LOCAL_MACHINE

cu KEY_CURRENT_USER

cr KEY_CLASSES_ROOT

us KEY_USERS

<pattern> *

Matches any sequence of characters (zero or more).

?

Matches any character.

[SET]

Matches any character in the specified set.

[!SET] or [ˆSET]

Matches any character not in the specified set.

\

Escape a character like ‘]’ or ‘-’.

Use the /view option to scan values.

/type <type> Define an entry type:

• REG_DWORD

• REG_SZ

/valuename <name> Define a value.

Chapter 12408


/enum The configuration file name is itoreg.cfg.

Example of exclusion of specific registry keys used for the display of the installed software:

Exclusions = {

Classes;

Program Groups;

Secure;

Windows 3.1 Migration Status;

Description;

}

Chapter 12 409


About “Server Config”

This application displays settings for the Server service for the selected Windows node.

Default

net.exe config server




Server Name Name of the server

Comment Comment for the server that is displayed in Windows Screens and with the NET VIEW command.

Software version Version number.

Server is active on Network connections that the server is using.

Server hidden Specifies whether the server’s computer name appears on display listings of servers. Hiding a server does not alter the permissions on that server.

Maximum Logged On Users Maximum open files per session.

Chapter 12410


About “Server Stats”

This application displays in-depth statistics about the Server service for the selected Windows node.

Default

net.exe statistics server





Chapter 12 411


About “Shares”

This application lists the external connections that are available on the selected Windows node. All shares ending with a dollar sign ($) are hidden shares that the Windows system makes available for remote administration by default.

Default

net.exe share


None.


Share name Full name of the available netbios share.

Resource Location of the share on the local system.

Remark Common remarks:

Default share These shares are for remote administration and are available only to users of the Administrators (or Domain administrators) group. They are created by default at startup.

Remote IPC Share for default IPCs.

Remote Admin Share to the local Windows system location.

Chapter 12412


About “Show Drivers”

This application lists all drivers that are present on the selected Windows node.

Default

itomserv.exe /list d


See “About “Show Services”” on page 414.


NAME True name of the service. If you wish to perform actions on the service, this is the name that should be used.

DISPLAY Description of the service. This is the name that is normally seen when working with the control panel.

STATUS The status of a service can be one of the following:

• Started (that is, Running)

• Paused

• Stopped (represented by a blank entry)

STARTUP The startup type of a service can be:

Automatic, boot, or system Service starts every time the system starts.

Manual Service can be started by a user or a dependent service.

Disabled Service cannot be started.

Chapter 12 413


About “Show Services”

This application returns a list of the services that are configured on the selected Windows system. If the VPO user does not have the rights to obtain information about a service, “NA” is returned for the service details.

Default

itomserv.exe /list s


/start <servicename> Start service <servicename>.

/stop <servicename> Stop service <servicename>.

/pause <servicename> Pause service <servicename>.

/continue <servicename> Continue service <servicename>.

/list s | d | a Print a list of installed services:

s List all Windows system services.

d List all Windows device drivers.

a List all installed services.

/e Set the exit status to a numerical value:

0 RUNNING

1 NOT_RUNNING

2 START_PENDING

3 STOP_PENDING

4 CONTINUE_PENDING

5 PAUSE_PENDING

6 PAUSED

NOTE Although the \e parameter is not useful from the VPO Application Bank, it is included here because it may be useful for use with monitor scripts

Chapter 12414



Name Internal name of the service.

Display Name that is normally displayed to the user.

Status Status of a service can be one of the following:

• Started

• Paused

• Stopped (indicated by a blank entry)

Startup The startup type of a service can be:

Automatic Service starts every time the system starts.

Manual Service can be started by a user or a dependent service.

Disabled Service cannot be started.

N/A User does not have the rights to obtain in-depth information about the service.

Chapter 12 415


About “Show Users”

This application displays information about local users and sessions on the selected Windows Node.

Default

itouser.exe /u


/u Returns user information for the system, including:

• Name of the current user

• Domain this user is logged into

• Server that validated the log-in

/s Returns full session information for the system, including:

• System name

• Net BIOS name

• Current local user name

• Type of the client

• Number of open sessions

• Idle time

/nu Returns number of users logged on by the system.

/ns Returns number of sessions on the system.

/local Returns the name of user logged into the local system.



Chapter 12416


About “Start Services”

This application starts the requested service on the selected Windows node. If a service is disabled (as opposed to being stopped) this application cannot enable the service. Services may not be enabled remotely. They must be enabled on the target system.

Default

itomserv.exe /start <service name>



Chapter 12 417


About “Stop Services”

This application stops the requested service. Since administrative rights are required to stop and start Windows services, the user must be defined as HP ITO Account, not opc_op.

Default

itomserv.exe /stop <service name>



Chapter 12418


About “TCP/IP Status”

This application displays protocol statistics and current active TCP/IP network connections for the selected Windows node.

Default

netstat.exe


See the Windows documentation.


Proto Protocol that is used for the connection.

Local Address Local system name and port number.

Foreign Address Full name and port number of the system to which the node is connected. The port number can also be nbsession, which is a netbios connection over TCP/IP.

State Current state of the connection.

Chapter 12 419


About “Used Shares”

This application returns a list of connections that the selected Windows node has made. If the status is disconnected, a connection is automatically established as soon as the local user switches to this drive.

Default

net.exe use




Status State of the connection (for example, OK, Disconnected means that the drive connection is defined but not connected).

Local Letter of the local drive used to access the connection.

Remoted Name of the system and the share that is used.

Network Type of network that is providing the connection (for example, Microsoft Windows Network, or 3rd party NFS software).

Chapter 12420


About “Virtual Terminal PC”

This application opens a terminal with command-line capabilities to the target Windows system. All output is redirected to the Virtual Terminal on the management server. Calling an application with a user interface is not supported. You should use a third party application for screen redirection, if terminal emulation or UI applications are required.

Virtual Term (PC) does not support the following:

❏ Terminal emulation.

❏ Applications that use a textual user interface.

❏ Applications that use a graphical user interface.

Default

opcvterm.exe


None.

Telnet on Windows 2000

On Windows 2000, the built-in Telnet Service can be used instead of the Virtual Terminal (PC).

You can change the setting directly in the Windows registry under:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TelnetServer\1.0\NTLM

To enable remote login from a UNIX system, follow these steps:

1. From the Control Panel, select Administrative Tools: Telnet Server Administration.

2. Enter 3 to select the option 3) Display/ change registry settings….

3. Enter 7 to select the option 7) NTLM.

4. Change this setting to 0 by replying appropriately to all prompts.

5. Use the menu options 5 (Stop Service) and 4 (Start Service) to stop and restart the Telnet Service

Windows 2000 allows remote login from UNIX systems.

Chapter 12 421


About “VPO Install Log”

This application returns the contents of the VPO installation log from the selected Windows node.

Default

cmd.exe /c “type c:\temp\inst.log”


None.

Chapter 12422


About “Workst Stats”

This application displays in-depth statistics about the workstation service for the selected Windows node.

Default

net.exe statistics workstation


For a full description of net.exe, refer to the Windows documentation.


For a full description of net.exe, refer to the Windows documentation.

Chapter 12 423

About Windows NT/2000 Managed NodesDistributing Scripts and Programs

Distributing Scripts and ProgramsFor Windows NT/2000 managed nodes, the platform selector and architecture identifier is the following:

ms\intel\nt






/var/opt/OV/share/databases/OpC/mgd_node/customer//ms/intel/nt/actions/*


/var/opt/OV/share/databases/OpC/mgd_node/customer//ms/intel/nt/monitor/*


/var/opt/OV/share/databases/OpC/mgd_node/customer//ms/intel/nt/cmds/*

Chapter 12424

About Windows NT/2000 Managed NodesDistributing Scripts and Programs







Temporary Directory

Intel 486 or higher Windows \usr\OV\tmp\OpC\bin\actions\usr\OV\tmp\OpC\bin\cmds\usr\OV\tmp\OpC\bin\monitor


Managed Node

Operating System

Directory Access Rights

Intel 486 or higher

Windows \usr\OV\bin\OpC\actions Administrator (full access)

Everyone (rx)

\usr\OV\bin\OpC\cmds Administrator (full access)

Everyone (rx)

\usr\OV\bin\OpC\monitor Administrator (full access)

Everyone (rx)

Chapter 12 425

About Windows NT/2000 Managed NodesOrganization of Managed Nodes

Organization of Managed Nodes Figure 12-3 shows how VPO software is organized on Windows NT/2000 managed nodes.

Figure 12-3 VPO Software on Windows Managed Nodes

During installation, VPO creates the HP ITO account, which has all rights and privileges that are required for the VPO agent software. It also creates the opc_op account, which is a normal user account and is used to execute applications.

NOTE The directories represented in Figure 12-3 by the letter “B” are created by the control agent if necessary.

bin conf tmplog

\usr\OV

OpC OpCOpC OpC

lib nls

<lang>bin conf

include

install

databases

OpC

mgd_node

vendor <country>

<codeset>

C

utilsB B

B


Key:

contrib

OpC BBC

Chapter 12426


Location of Files

On Windows managed nodes, files are located as follows:


\usr\OV\tmp\OpC


\usr\OV\conf\OpC


Table 12-12 shows the VPO user accounts on Windows managed nodes.

Table 12-12 VPO User Accounts on Windows Managed Nodes

Field Entry

User Name HP ITO account opc_op

Password Defined during installation

Same as HP ITO accounta

a. All other properties assume the default value

Group Administratorsb or Domain Administratorc

b. Standalone or domain membersc. Domain Controller

Users or Domain Users

Description HP VPO agent account HP VPO operator account

Login Shell None None

Chapter 12 427



VPO inserts several keys in the Windows Registry.

The keys and their associated values can be viewed with the Registry Editor, using the following command:

%SystemRoot%\System32\regedt32.exe

The Windows Registry Editor shows the following keys for VPO:

❏ HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenView\ITO

❏ HKEY_LOCAL_MACHINE\SYSTEM\Current ControlSet\Control\Lsa\MSV1_0

❏ HKEY_LOCAL_MACHINE\SYSTEM\Current ControlSet\Services\HP ITO Agent

If on a domain controller, the Windows Registry Editor also shows:

HKEY_LOCAL_MACHINE\SYSTEM\Current ControlSet\Services\HP ITO Installation Server

Chapter 12428

About Windows NT/2000 Managed NodesVPO Managed Node Libraries

VPO Managed Node LibrariesTable 12-13 describes the managed node libraries for VPO A.05.xx, A.06.xx, and A.07.xx.


On an Intel platform with Windows NT/2000 managed nodes, use the following include file:

\usr\OV\include\opcapi.h

About the Makefile

To built an executable correctly, use Microsoft Developer Studio 6.0 or higher.

For more information about the managed node makefile, see the ReadMe file:/




Library libopc.dll

opcapi.dll

libopc.dll

opcapi.dll

libopc.dll

opcapi.dll

opcas.dll

libnsp.dll

pdh.dll


N/A N/A N/A


N/A N/A N/A

Description Use *.mak files to build

Use *.dsp files to build

Use *.dsp files to build

Chapter 12 429

About Windows NT/2000 Managed NodesAbout Citrix MetaFrame Integration

About Citrix MetaFrame IntegrationYou can install Citrix MetaFrame as an extension of Windows Terminal Server with additional client and server functionality, including:

❏ Support for heterogeneous computing environments

❏ Support for enterprise-scale management

❏ Seamless desktop integration

NOTE For detailed descriptions of the default Citrix MetaFrame applications that can be used with VPO, see “Types of Citrix MetaFrame Applications” on page 435.

Supported Versions of Citrix MetaFrame

VPO supports the English version of Citrix MetaFrame 1.8 on Windows NT 4.0 Terminal Server Edition Service Pack 4.

Software Requirements for Citrix MetaFrame

The following software is required for Citrix MetaFrame on Windows managed nodes:

❏ Windows NT Service Pack

Windows NT 4.0 Terminal Server Edition: Service Pack 5 or 6A

❏ Citrix MetaFrame

Citrix MetaFrame 1.8 or higher

Chapter 12430


Integrating Citrix MetaFrame into VPO

To integrate Citrix MetaFrame into VPO, perform these procedures:

1. Install the Citrix MetaFrame agent.

You can install the Citrix MetaFrame agent using one of the following installation methods:

• Standard Installation

Use this method if the VPO agents are correctly installed. For instructions, see “To Install an Agent with Standard Installation” on page 368.

• Manual Installation

Use this method if the VPO are not correctly installed and do not function correctly. For instructions, see “To Pre-install a Windows Agent on a Windows PC” on page 376.

NOTE During manual installation, the logfile is stored in the C:\temp directory. Or, if that directory does not exist, the logfile is put in the directory where the installation was started

2. Configure the Citrix MetaFrame agent.

To find out how to configure the Citrix MetaFrame agent, see “To Configure the Citrix MetaFrame Server” on page 432.

Chapter 12 431


To Configure the Citrix MetaFrame Server

To configure the Citrix MetaFrame server, follow these steps:

1. Upload the configuration.

On the management server, enter the following command:

opccfgupld -add TS_MF

The swinstall installation process automatically installs the commands and monitors directly into your VPO software sub-tree platform.

2. Assign and distribute templates to the MetaFrame managed nodes.

Do this:

a. Make sure the Terminal Server or MetaFrame server is present in the VPO Node Bank, and that the agent software is running on the node.

b. Assign the appropriate Terminal Server or MetaFrame templates to the agent on the managed node.

NOTE If you are using Terminal Server, use the templates from the Terminal Server group. If you are using Terminal Server and MetaFrame, assign the MetaFrame group.

c. Distribute the assigned templates, monitors, and commands to the node.

About the ICA Browser Service

The ICA Browser service is specific to Citrix MetaFrame managed nodes. ICA browsing is central to MetaFrame license pooling, load balancing, and application publishing. The ICA Browser service enables you to control browser parameters (for example, backup ICA Browsers, ICA Gateways, and update and refresh intervals). You can also configure which servers become the master ICA Browser.

Chapter 12432


About the Program Neighbourhood Service

The Program Neighbourhood service provides a new means of application access and management for the enterprise: the Server Farm. A Server Farm can contain all Citrix servers within your organization, regardless of the previous boundaries of local subnets and NT Domains.

Types of MetaFrame Monitored Objects

Table 12-14 describes the default monitored objects used by VPO on Citrix MetaFrame managed nodes.

Table 12-14 Object Thresholds on Citrix MetaFrame Managed Nodes

Object Description Threshold PollingInterval (Minutes)

TS_Licensing Checks if Terminal Server licensing service is running.

1 5

TS_Service Checks if Terminal Server service is running.

1 5

MF_ICA_Browser Checks if MetaFrame ICA Browser service is running.

1 5

MF_Prog_Neighbourhood

Checks if the MetaFrame ICA Program Neighbourhood service is running.

1 5

Chapter 12 433


Types of MetaFrame Logfile Templates

Table 12-15 shows encapsulated logfiles and associated templates used on Citrix MetaFrame managed nodes.

NOTE Although there is a logfile template available for NT Terminal Server, you should only use the logfile template for Citrix MetaFrame.

Table 12-15 Encapsulated Logfiles on Managed Nodes running Windows NT Terminal Server and Citrix MetaFrame


SYSTEM_LOG NT system eventlog for Terminal Server

System Log (Terminal Server)

SYSTEM_LOG NT system eventlog for MetaFrame

System Log (MetaFrame)

Chapter 12434

About Windows NT/2000 Managed NodesTypes of Citrix MetaFrame Applications

Types of Citrix MetaFrame ApplicationsCitrix MetaFrame has an additional application group, MetaFrame Tools. The implementation is similar to using the MetaFrame Tools/Citrix Server Administrator GUI directly on the MetaFrame system.

This section describes the applications in the MetaFrame Tools application group

About “ACL Info”

Displays file and directory permissions that give excessive access to users and groups. This application can be used to verify the security of the MetaFrame server, and also reports potential security exposures on a MetaFrame server.

NOTE This application is supported only on Windows NT.

Default

acl info <path> </files_only | /registry_only>


<path>

Path of director and file.

/files_only Reduces scope of application to files only

/registry_only Reduces scope of application to registry only.

About “Auditlog”

Processes the Windows NT EventLog and generates reports of login and logout activity.

Default

auditlog

Chapter 12 435



username Returns the name of the user.

session Returns the session duration.

/FAIL Returns a status report for specified parameters.

NOTE To use Auditlog, you must enable Windows NT login and logout event logging with User Manager for Domains.

About “Disconnect”

Used to disconnect a terminal server session.

NOTE This application must be passed with the parameters listed under “Default.”

Default

disconnect <sessionid | sessionname>

About “Flush”

Equates the client drive mapping cache. This equation forces the MetaFrame server and the client to re-synchronize all disk data.

Default

flush

About “License”

Shows information about currently present licenses on the network. By default, the application shows how many licenses exist on the network, how many are in use on the entire network, and how many licenses are in use on the node:

Chapter 12436


Default

license

About “Processes”

Displays the status of all user processes, one process per line.

Default

processes


sessionname Returns the name of the session.

processid Returns the process ID.

username Returns the username.

programname Returns the name of the program associated with selected object.

About “Send Message”

Sends messages to ICA client users.

NOTE This application must be passed with the parameters listed under “Default.”

Default

send message <username | sessionname | sessionid> <message>

About “Servers”

Displays the available Terminal Servers on the network

Default

servers

Chapter 12 437



</DOMAIN:domain>

Returns information for the specified domain.

About “Sessions”

Displays information about currently logged users. By default, it shows all sessions on the current server:

Default

sessions <username> </SERVER:server_name>


<username>

Returns all sessions for the specified username.

/SERVER:server_name

Returns the users logged on the specified server.

About “Users”

Displays information about currently logged users. By default, it shows all users with sessions on the current server:

Default

users </SERVER:server_name>


/SERVER:server_name

Returns the users logged on the specified server.

Chapter 12438

About Windows NT/2000 Managed NodesAbout SMS Integration

About SMS IntegrationThe VPO/SMS integration is a collection of monitors and templates that enable the VPO Windows agent to monitor an SMS installation in the PC subnet of an IT environment. This integration enables VPO users to monitor the environment of Windows nodes, and to restart SMS services if they fail.

Windows agents installed on every Site Server report SMS information about the entire SMS hierarchy without using any SMS mechanisms.

Supported Versions of SMS

VPO supports both the English and the Japanese System Management Server (SMS) 1.2 on Microsoft Windows NT Server 4.0.

Integrating SMS into VPO

The VPO/SMS integration has two parts:

• SMS

Specific SMS application event log template and fourteen threshold monitors.

• Windows

Standard Windows application event log template.

This sections explains how to set up and install these templates and monitors.

Chapter 12 439


To Integrate SMS into VPO

To integrate SMS into VPO, follow these steps:

1. Assign the SMS monitors and templates to the appropriate Windows servers.

The SMS integration contains fourteen threshold monitors that monitor SMS services.

Each service has an UP and DWN monitor:

UP Sends VPO a message when the service is running again. This monitor never has an associated action.

DWN Sends VPO a message when the service that it monitors is down, and either automatically restarts the service, or provides the operator with the command that will restart it.

The SMS services and their associated UP and DWN monitors are shown in Table 12-16.

Assign one or both of these UP and DWN monitors to the Windows systems that run the services that the templates will monitor.

You must assign the Application Event Log template, NT SMS, to any SMS Site Server of the SMS hierarchy. However, you cannot assign NT SMS to the logon, distribution, or helper servers because duplicate reprocessing of problems will result. These servers are also logged into the Windows application event log of the Site Server. The Application Event Log template must be on a Site Server, even if the site is distributed.

2. Customize the conditions for the templates.

You must consider two templates when customizing the template conditions for the SMS Site Server:

• SMS

SMS-specific application event log template.

A suppress unmatched condition is the first condition of the SMS application event log template. This condition suppresses all Windows application event log entries that are not SMS-related, thus ensuring that the entire set of 586 match conditions is not checked unnecessarily for non-SMS log entries.

Chapter 12440


• Windows

Default Windows application event log template.

The default Windows Logfile encapsulator template, dflt_ApplEvLog, has a forward unmatched flag set by default. If both templates are installed on an SMS Site Server, two messages will be generated for each SMS-related event log entry: one by the SMS template and one by the default Windows Logfile template. To avoid this problem, add one additional suppress matched condition at the beginning of the default Windows Logfile template that suppresses SMS-related messages. This condition needs to match the string SMS in the application field of the message.

This additional condition is needed only if you assign both templates to the same node and if the you keep the forward unmatched condition set in the default template.

3. Distribute the templates.

Distribute the agent as well, if it is not already installed.

Chapter 12 441


Types of VPO-SMS Monitors for SMS Services

Table 12-16 shows The SMS services and their associated UP and DWN monitors.n

Table 12-16 VPO-SMS Monitors for SMS Services

VPO-SMS Monitors SMS Service Restarta

NT_DWN_SMS_CLIENT_CONFIG_MANAGER Client Configuration Manager OA

NT_UP_SMS_CLIENT_CONFIG_MANAGER none

NT_DWN_SMS_EXECUTIVE Executive OA

NT_UP_SMS_EXECUTIVE none

NT_DWN_SMS_HIERARCHY_MANAGER Hierarchy Manager AA

NT_UP_SMS_HIERARCHY_MANAGER none

NT_DWN_SMS_INVENTORY_AGENT Inventory Agent OA

NT_UP_SMS_INVENTORY_AGENT none

NT_DWN_SMS_PACKAGE_COMMAND_MANAGER Package Command Manager OA

NT_UP_SMS_PACKAGE_COMMAND_MANAGER none

NT_DWN_SMS_SITE_CONFIG_MANAGER Site Configuration Manager AA

NT_UP_SMS_SITE_CONFIG_MANAGER none

NT_DWN_SMS_TRAP_FILTER Trap Filter none

NT_UP_SMS_TRAP_FILTER none

a. OA = Operator Action; AA= Automatic Action

Chapter 12442


Mapping SMS Messages

When VPO reports SMS messages in the message browser, it assigns a Message Group and Message Object that are appropriate to the message. The tables below show how the SMS messages will be mapped in VPO.

Assigning SMS Messages to VPO Message Groups

Table 12-17 shows how VPO assigns SMS messages to Message Groups.

Table 12-17 SMS Message Assignment to VPO Message Groups

SMS Message VPO Message Group

All messages containing one of the following words:

• Compress

• Instruction

• Inventory

• Job

• Package

Jobs

All SMS network errors that are not related to jobs.

Network

All SMS security errors that are not related to jobs.

Security

All SMS database errors that are not related to jobs.

DB

All remaining errors. OS

Chapter 12 443


Assigning SMS Messages to VPO Message Objects

Table 12-18 shows how VPO assigns SMS messages to Message Objects.

Table 12-18 SMS Event Assignment to VPO Message Objects

SMS Events VPO Message Objects

All events that are related to setup, installation, and configuration.

Configuration

All events that can be related to inventory collection.

Inventory

All events that can be related to package distribution.

Distribution

All events that can be related to application errors.

Application

All remaining events. Miscellaneous

Chapter 12444

A About MC/ServiceGuard

Appendix A 445

About MC/ServiceGuardIn this Appendix

In this AppendixThis appendix provides background information for system administrators working with HP OpenView VantagePoint Operations (VPO) in HP Multi-Computer Service Guard (MC/ServiceGuard) clusters. It assumes that you are familiar with MC/ServiceGuard and the general concepts of VPO.

For more detailed information about MC/ServiceGuard, see Managing MC/ServiceGuard. To find out how to install and configure VPO in an MC/ServiceGuard cluster, see the VPO Installation Guide for the Management Server.

NOTE MC/ServiceGuard is not supported on Sun Solaris.

Appendix A446

About MC/ServiceGuardWhat is MC/ServiceGuard?

What is MC/ServiceGuard?HP Multi-Computer/ServiceGuard (MC/ServiceGuard) is a powerful hardware and software solution that switches control from one VPO management server to another if the original management server fails. Critical information is stored on shared disks that are also mirrored. Uninterruptible power supplies (UPS) are included to guarantee continuous operation if a power failure occurs. And highly available (HA) computer systems provide access to your data and applications if a system component (for example, a CPU or network interface card) fails. The systems belonging to the MC/ServiceGuard installation make up an MC/ServiceGuard cluster.

Transferring Applications to Other Management Servers

When your system includes MC/ServiceGuard, you can transfer applications quickly and automatically from a failed CPU to a functioning CPU. To transfer applications in this way, you must install and configure the necessary system components. For example, two or more CPUs and two or more independent disks enable you to configure a system that eliminates single points of failure.

MC/ServiceGuard provides you with the software support to transfer applications to another CPU or network after a system failure. You can also use MC/ServiceGuard to transfer the control of running applications to another CPU during maintenance of any management server.

Appendix A 447


Glossary of MC/ServiceGuard Terms

The following terms are used in this appendix:

adoptive node Node to which MC/ServiceGuard can transfer control of a package. A package may have several adoptive nodes. Note that you can define packages that only run on a subset of all MC/ServiceGuard cluster nodes.

MC/Service GuardDaemon (cmcld) Daemon that monitors the state of

the MC/ServiceGuard cluster, all nodes in the cluster, all network resources, and all services. The daemon reacts to failures and transfers control of packages. It also runs the package control script.

original node Node on which the package is running before MC/ServiceGuard initiates a transfer of control.

package Application together with associated programs, resources, and files. Control of the package may be transferred to another CPU in the event of failure of the original CPU or network. Note that a package can run only once in an MC/ServiceGuard cluster.

package IP/hostname IP/hostname of the VPO package. This can sometimes be referred to as Virtual or Relocatable IP/hostname.

package custody Node on which the package is currently running.

Appendix A448


service Process that is monitored by MC/ServiceGuard. A service can be an application program, or the resources needed by an application program. Services are started by starting a package, and stopped by halting a package. If a service fails while a package is running, the package may be halted and restarted on an adoptive node.

Appendix A 449

About MC/ServiceGuardHow MC/ServiceGuard Works

How MC/ServiceGuard WorksThis section contains examples that demonstrate how you can use MC/ServiceGuard to switch control of a package between different cluster servers.

Example 1. Switching Packages

Figure A-1 shows a typical MC/ServiceGuard cluster before control is switched to another management server.

Figure A-1 MC/ServiceGuard Package Switchover (Before)

In Figure A-1, the following is true:

❏ Node 1 runs the application packages A and B.

❏ Node 2 is runs the application package C.

❏ Node 3 is runs the application packages D, E, and F.

Bridge

Package A Package DPackage C

Root 1 Root 2 Root 3

Root 2Mirror

Node 1 Node 2 Node 3

Package A Disk

Package F Disk

Package E Disk

Package

D Disk

Package C Disk

Package B Disk

Package A Mirror

Package D Mirror

Package

F MirrorPackage

E Mirror

Package B Mirror

Package

C Mirror

LAN 0

LAN 1

Package B

Package E

Package F

Appendix A450


❏ Nodes are connected by two redundant LANs connected through a bridge.

❏ Each node has its own root disk and shares volume groups.

If Node 1 fails, Node 2 is an adoptive node for Package A, but no adoptive node is specified for Package B. As a result, the applications specified in Package B is not transferred in the event of node failure. However, Package B is protected from a possible network failure by local network switching.

NOTE Transferring control of a package to another node does not transfer the program counter. Processes in a transferred package restart from the beginning. If necessary, all processes in a package must be written so that they can detect such a restart.

When a node fails, the CPU is stopped immediately using a Transfer Of Control (TOC), which is an immediate halt without a graceful shutdown.

Figure A-2 shows a typical MC/ServiceGuard cluster after control is switched to another management server.

Figure A-2 MC/ServiceGuard Package Switchover (After)

Package C Mirror

Bridge

Package A Package F

Package E

Package DPackage C

Root 1 Root 2 Root 3

Root 2Mirror

Node 1 Node 2 Node 3

Package A Disk

Package F Disk

Package E Disk

Package D Disk

Package C Disk

Package B Disk

Package A Mirror

Package D Mirror

Package F Mirror

Package E Mirror

Package B Mirror

LAN 0

LAN 1

Appendix A 451


Example 2. Switching Local Networks

Figure A-3 shows two MC/ServiceGuard nodes connected by one virtual local area network (LAN).

Figure A-3 MC/ServiceGuard LAN Switchover (Before)

LAN 0 and LAN 1 are connected by a bridge, and act as one subnet. Node 1 and node 2 communicate through LAN 0. LAN 1 is in standby mode.

If the LAN 0 network interface card on Node 2 fails, the following occurs:

❏ Switching Subnet and IP Addresses

Standby LAN interface, LAN 1, takes on the identity of LAN 0 on node 2. The subnet and IP addresses are switched to the hardware path associated with LAN 1. The switch is transparent on the TCP/IP level.

❏ Rerouting Communications

MC/ServiceGuard reroutes communications without having to transfer the control of packages between nodes.

Figure A-4 on page 453 shows the MC/ServiceGuard nodes after the switch to another LAN.

Bridge

LAN 1 LAN 0 LAN 1 LAN 0

NODE 1 NODE 2

LAN 0

LAN 1

Appendix A452


Figure A-4 MC/ServiceGuard LAN Switchover (After)

Example 3. Redundant Data and Heartbeat Subnets

In general, you have two redundant subnets for MC/ServiceGuard clusters:

❏ Data Subnet

Subnet used by the package applications for the data transfer.

❏ Heartbeat Subnet

Subnet used by MC/ServiceGuard to transfer the heartbeat signal to and from each MC/ServiceGuard node.

If your network traffic is very heavy, your MC/ServiceGuard clusters should have two or more subnets. It is common to find three bridged LAN interfaces, with heartbeat over LAN0, LAN1 as standby for both, and LAN3 as the data LAN. LAN1 can back up either subnet.

Figure A-5 on page 454 shows redundant data and control subnets for MC/ServiceGuard.

Bridge

LAN 1 LAN 0 LAN 1 LAN 0

NODE 1

LAN 0

LAN 1

NODE 2

Appendix A 453


Figure A-5 MC/ServiceGuard Redundant Data and Heartbeat Subnets

The heartbeat interval is set in the MC/ServiceGuard cluster configuration file. Heartbeat time-out is the length of time the MC/ServiceGuard cluster waits for a node heartbeat before transferring a package.

Subnet B

Bridge

Package A Package B

Package C

NODE 2NODE 1

Primary LAN: Heartbeat/Data

Dedicated Heartbeat LAN

Subnet A

LAN 1

LAN 3

LAN 0

Standby LAN: Heartbeat/Data

Appendix A454

About MC/ServiceGuardAssigning IP Addresses and Hostnames

Assigning IP Addresses and HostnamesMC/ServiceGuard enables you to assign multiple IP addresses to local area network (LAN) interface cards. In addition, you can assign unique IP addresses and hostnames to packages.

Assigning IP Addresses to LAN Interface Cards

You must assign IP addresses to LAN interface cards. Each primary LAN interface card has a unique IP address. This address is fixed to the node and is not transferable to another node.

You may assign multiple IP addresses to a single LAN interface card.

Assigning IP Addresses and Hostnames to Packages

You may assign IP addresses and hostnames to packages:

❏ IP Addresses

You may assign a unique IP address to each package. This IP address is then taken over by the adoptive node if control of the package is transferred. The node that currently holds the IP address of a package controls that package

❏ Hostnames

You may assign a hostname to each package. The IP address of the package then points to the hostname. If you assign hostnames, you can then use the gethostbyname() to retrieve the IP addresses of the package.

Appendix A 455

About MC/ServiceGuardRunning VPO in an MC/ServiceGuard Environment

Running VPO in an MC/ServiceGuard EnvironmentMC/ServiceGuard provides a mechanism to start and stop applications. Each application running in an MC/ServiceGuard environment must provide a package with information about MC/ServiceGuard and how to stop the application. Known as the VPO MC/ServiceGuard package, this package is transferred between the MC/ServiceGuard cluster nodes if a switchover occurs.

Running NNM on MC/ServiceGuard Cluster Nodes

Network Node Manager (NNM) 5.0 does not support MC/ServiceGuard directly. In other words, it is not possible to create an NNM 5.0 MC/ServiceGuard package. However, it is possible to run NNM 5.0 independently on each MC/ServiceGuard cluster node.

You can run NMM 6.x as a MC/ServiceGuard package if you integrate NNM into the VPO. However, VPO A.05.00 and higher do not allow you to run NNM independently on MC/ServiceGuard cluster nodes when VPO is running as an MC/ServiceGuard package.

TIP To enable clusters to be discovered, let the netmon run for one day on each cluster node before taking the VPO MC/ServiceGuard environment online.

Appendix A456


Running a VPO Management Server in an MC/ServiceGuard Environment

Figure A-6 shows how to run a VPO management server in an MC/ServiceGuard environment.

Figure A-6 VPO Management Server in MC/ServiceGuard

To reduce the amount of data on the shared disk, only the following are installed on the shared disk:

❏ /var/opt/OV/share

❏ /etc/opt/OV/share

VPO can only be installed on an MC/ServiceGuard cluster node after the MC/ServiceGuard software is installed.

VPO/NNM

Oracle

Server

VPOAgent

VPOAgent

MC/ServiceGuard Node1 MC/ServiceGuard Node 2

active connections if the VPO server is running on Node 2

RDMS

binaries

active connections if the VPO server is running on Node 1

binaries

sharedfiles

VPO/NNMServer

binaries

Appendix A 457


Running VPO Agents in an MC/ServiceGuard Environment

The VPO agent software can only be installed on physical MC/ServiceGuard cluster nodes.

It is not possible to install the VPO agent software on virtual MC/ServiceGuard nodes; nor is it possible to assign any templates to these virtual nodes. Instead, virtual nodes can be managed as message-allowed nodes in the VPO Node Bank which means that messages can be received. One exception to this is the virtual cluster in which the management server runs. For more information, see the appendix, “Installing VPO in an MC/ServiceGuard Environment” in the VPO Installation Guide for the Management Server.

Appendix A458

About MC/ServiceGuardTroubleshooting VPO MC/ServiceGuard Packages

Troubleshooting VPO MC/ServiceGuard PackagesThis section explains how to solve problems you might encounter when working with VPO MC/ServiceGuard packages. For more general troubleshooting information, see Managing MC/ServiceGuard.

Types of VPO MC/ServiceGuard Logfiles

MC/ServiceGuard and the VPO MC/ServiceGuard package use the following two logfiles:

❏ MC/ServiceGuard

/var/adm/syslog/syslog.log

Contains general error messages from MC/ServiceGuard.

❏ VPO MC/ServiceGuard

/etc/cmcluster/OpC/OpC.cntl.log

Contains the output of the VPO MC/ServiceGuard package during startup and shutdown.

If you encounter problems with the VPO MC/ServiceGuard package, make sure that you check the contents of both files.

Enabling Maintenance Mode for VPO MC/ServiceGuard Packages

To avoid a switchover of the VPO MC/ServiceGuard package when VPO is stopped, you can configure the VPO MC/ServiceGuard package in maintenance mode. Maintenance mode enables you to run a backup or install a patch. In either case, the shared disk and the database must be available.

You can enable maintenance mode by creating an empty file:

touch /tmp/maint_NNM

If this file exists, the monitor scripts nnm.mon and ito.mon do not trigger a package switchover when the NNM and VPO daemons are stopped.

Appendix A 459

About MC/ServiceGuardTroubleshooting VPO MC/ServiceGuard Packages

Appendix A460

B Administration of Sun Enterprise Clusters

Appendix B 461

Administration of Sun Enterprise ClustersIn this Appendix

In this AppendixThis appendix provides information for system administrators working with VPO in Sun Enterprise Cluster environments. It assumes you are familiar with the Sun Enterprise Cluster and the general concepts of VPO.

For detailed information about Sun Enterprise Cluster, see Sun Enterprise Cluster High Availability Administration. To install and configure VPO in a Sun Enterprise Cluster environment, see VPO Installation Guide for the Management Server.

Appendix B462

Administration of Sun Enterprise ClustersWhat are Sun Clusters?

What are Sun Clusters?The Sun Cluster system is a software environment that provides high availability (HA) support for Data Services and parallel database access on a cluster of servers (that is, Sun Cluster servers).

The Sun Cluster framework provides the following:

❏ Hardware and software failure detection

❏ Sun Cluster system administration

❏ System failover

❏ Automatic restart of Data Services

Purpose of Sun Clusters

The purpose of the Sun Cluster system is to manage failures in such a way that loss of service is prevented. The Sun Cluster system manages failures by adding hardware redundancy as well as software monitoring and restart capabilities. These measures reduce single points of failure in the system. A single point of failure can be the failure of a hardware or software component that causes the entire system to be inaccessible to client applications. By reducing hardware and software failures, the failure management prevents loss of service throughout the system.

Appendix B 463


Glossary of Sun Cluster Terms

CCD Cluster Configuration Database. Highly-available, replicated database that provides a single cluster-wide namespace and configuration repository for the cluster software components for the HA framework.

CCDD Cluster Configuration Database Daemon. Daemon that performs the initialization, updating, querying, and reconfiguration of the CCD. The daemon synchronizes and serializes cluster-wide CCD updates and ensures a consistent view of the replicated copies of the database across all nodes of the cluster.

Data Service Set of modules that acts as an interface between the Sun Cluster High Availability framework and an application. This set of modules works closely with the logical host. When it is configured with a logical host, the module set runs on a logical host, no matter which physical host environment is currently being used.

failover When one host assumes responsibility for the services of another host.

logical host Collection of network definitions and disk storage. This collection of one or more IP addresses, assigned network adapters, and disk storage, is configured as a unit of failover. One or more Data Services are configured to run on a logical host, so that, when the logical host moves, the Data Service follows it.

switchover Coordinated movement of a logical host from one operational Sun Cluster server to another. It is a manual process that is initiated by an administrator using the scadmin (1m) command.

takeover Automated failover of a logical host and its Data Services from one Sun Cluster server to another after a failure has been detected. It is an automated process. The failed server is forced to give up control of the logical host.

Appendix B464


About the Sun Cluster Architecture

With Sun Cluster software, you can cluster up to four nodes in a single configuration. That is, one cluster node represents a master cluster node, which can have up to three backup cluster nodes.

In correlation with VPO, only one logical host can be configured, and one disk group assigned to this logical host.

Figure B-1 Architecture of Sun Clusters

Each node in a Sun Enterprise Cluster is connected to one or more public networks, and a private interconnect, representing a communication channel used for transmitting data between cluster nodes.

Appendix B 465


Example of a Failover Procedure

Figure B-2 describes the failover procedure in a configuration in which the central instance, the database system (Oracle), and VPO are configured on one logical host within the cluster. Host A is the current master node of the logical host ITO-LH. Host B is its backup host.

Figure B-2 Failover Procedure

Appendix B466


In this example, the failover procedure follows these steps:

1. System Failure on Host A

When a system failure on Host A occurs, the database, central instance, and VPO are no longer available. All connections with application servers or front ends are interrupted.

2. Cluster is Reconfigured on Host B

Cluster reconfiguration process is initiated on the remaining Host B.

• Cluster now consists of only one physical host, Host B.

• Logical host, ITO-LH, is no longer mastered by Host A, and is assigned to Host B. That is, Host B takes on the IP address of the logical host as well as the logical disk group ITO-DG.

• If the Data Service, ITO-DS, has been associated with the logical host, ITO-LH, the Data Service is started on Host B.

NOTE Data Service association with the logical host is done automatically during the configuration process.

• Disk group, ITO-DG, is imported on Host B and all file systems are mounted as specified in the .vfstab file of the logical host:

/etc/opt/SUNWcluster/conf/hanfs/ITO-LH.vfstab

The consistency of the file systems is secured by using a Journaling File System.

3. Fault Monitor is Restarted

ITO-DS fault monitor ito_pmon is restarted with the ITO-DS Fault Monitor Start Net Method script.

ITO-DS is started on Host B, which is now the current master of the logical host ITO-LH. Oracle and NNM/VPO are started within ITO-DS Start Net Method script.

4. Services are Available Again

VPO services are available again.

Logical host ITO-LH is reconfigured and running again on the physical host - Host B.

Appendix B 467

Administration of Sun Enterprise ClustersRunning VPO Agents in a Sun Cluster Environment

Running VPO Agents in a Sun Cluster EnvironmentThe VPO agent software can only be installed on physical Sun Cluster nodes.

It is not possible to install the VPO agent software on virtual Sun Cluster nodes; nor is it possible to assign any templates to these virtual nodes. Instead, virtual nodes can be managed as message-allowed nodes in the VPO Node Bank which means that messages can be received. One exception to this is the virtual cluster in which the management server runs. For more information, refer to Appendix A, “Installing VPO in a Sun Cluster Environment” of the VPO Installation Guide for the Management Server.

Appendix B468

Administration of Sun Enterprise ClustersTroubleshooting VPO in a Sun Cluster Environment

Troubleshooting VPO in a Sun Cluster EnvironmentThis section describes the Data Service configuration file and the Sun Cluster logfiles on VPO.

About the Data Service Configuration File

Data Service attributes are written to the following configuration file:

/<logical host name>/ha/ito/ito_scha.conf

Data Service attributes and values are listed below.

ITO_PMON_TAG ito_pmon

Process monitor facility administration, pmfadm (1m), registers the VPO process monitor ito_pmon.

ITO_PMON_RETRIES 5

Process monitor facility administration, pmfadm (1m), tries to restart VPO process monitor a maximum of n times (where n is the number of retries) before the logical host giveaway is initiated.

ITO_PMON_TPERIOD -1

Time period in minutes over which the process monitor facility administration, pmfadm (1m), counts the failures. Process failures that have occurred outside the specified time period are not counted.

ITO_PMON_SLEEP 60

Time period in seconds, during which the process monitor reads the VPO Data Service configuration file to retrieve a new value of ITO_MAINTENANCE key. You can modify the value of this flag manually.

ITO_PMON_START 5

Process monitor tries to restart the Openview Platform a maximum of n times (where n is the number of retries) before a logical host giveaway is initiated. You can modify the value of this flag manually.

Appendix B 469


ITO_PMON_EXCLUDE opcsvcm

List of all VPO or NNM processes not to be monitored by the process monitor in the form:

ITO_PMON_EXCLUDE <process 1> <process 2>...<process n>

You can modify the value of this flag manually.

ITO_START 360

Timeout in seconds using the Data Service Start Method.

ITO_START_NET 720

Timeout in seconds using the Data Service Start Net Method.

ITO_STOP 360

Timeout in seconds using the Data Service Stop Method.

ITO_STOP_NET 360

Timeout in seconds using the Data Service Stop Net Method.

ITO_FM_INIT 360

Timeout in seconds using the Data Service Fault Monitor Init Method.

ITO_FM_START 360

Timeout in seconds using the Data Service Fault Monitor Start Method.

ITO_FM_STOP 360

Timeout in seconds using the Data Service Fault Monitor Stop Method.

ITO_MAINTENANCE FALSE

This flag indicates if VPO is in maintenance mode or not. The default value is FALSE. When this flag is set to FALSE, the process monitor will try to restart OpenView Platform processes, if at least one of the VPO processes is not running.

Appendix B470


About Sun Cluster Logfiles

The following logfiles are used by Sun Cluster in VPO:

/var/opt/SUNWcluster/ccd/ccd.log

File to which Cluster Configuration Database (CCD) errors are logged.

The most important errors pertain to the following areas:

• CCD

• Cluster

• Data Service

• Logical host

/var/opt/SUNWcluster/scadmin.log

File to which errors detected by the Sun Cluster System control program scadmin are written.

The most important errors pertain to the following areas:

• Cluster state and (re)configuration

• Disk group

• File system

• License

• Logical volumes

Appendix B 471


Appendix B472

C Administration of VERITAS Cluster Server

Appendix C 473

Administration of VERITAS Cluster ServerIn this Appendix

In this AppendixThis appendix provides information for system administrators working with VPO in VERITAS Cluster Server environments. It assumes that you are familiar with both, the VERITAS Cluster Server and the general concepts of VPO.

For detailed information on VERITAS Cluster Server, please refer to VERITAS Cluster Server Documentation Set. To install and configure VPO in a VERITAS Cluster Server environment, see VPO Installation Guide for the Management Server.

Appendix C474

Administration of VERITAS Cluster ServerVERITAS Cluster Server Architecture

VERITAS Cluster Server ArchitectureWith VERITAS Cluster Server software, you can cluster up to 32 nodes into a single configuration.

Figure C-1 Architecture (example)

Each node in a VERITAS Cluster Server is connected to one or more public networks, and a private interconnect, representing a communication channel used for transmitting data between cluster nodes.

Appendix C 475


Switchover Example

The example describes the switchover procedure in a two node cluster in which the service group vpo-sg is currently online on cluster system mystic. VERITAS Cluster Server initiates switchover from system mystic to the remaining system myrtle. Service group vpo-sg is put offline on system mystic and online on system myrtle. During the switch VPO, Oracle OpenView Database and SQL*Net/Net8 Listener become unavailable.

Figure C-2 Switchover Example from Node mystic to myrtle

Appendix C476


Switchover procedure

1. System Failure on Node mystic

When a system failure occurs on node mystic, VCS initiates switchover of service group vpo-sg from system mystic. Service group is put offline on system mystic and online on system myrtle.

Figure C-3 Service Resources of Service Group vpo-sg

2. Service Resources are put Offline

Service resources of service group vpo-sg are put offline in the following order on mystic:

• vpo-server

• vpo-oracle

• vpo-sqlnet

Appendix C 477


• vpo-ip, vpo-mount-etc, vpo-mount-var, vpo-mount-ora-core, vpo-mount-ora-data

• vpo-volume-etc, vpo-volume-var, vpo-volume-ora-core, vpo-volume-ora-data

• vpo-dg

Since service resources are of different resource types, the following actions are actually performed for each set of resources of the same type during the switch of service group vpo-sg. See Table C-1.

Table C-1 Service Resource Actions (Offline)

Service Resource Resource Type Action (Offline)

vpo-dg DiskGroup Deport Disk Group.

vpo-ip IP Unconfigure Virtual IP Address.

vpo-mount-etc Mount Unmount File System.

vpo-mount-ora-core Mount Unmount File System.

vpo-mount-ora-data Mount Unmount File System.

vpo-mount-var Mount Unmount File System.

vpo-oracle VPOOracle Stop Oracle OpenView Database.

vpo-server VPOServer Stop OpenView Platform.

vpo-sqlnet VPOSqlnet Stop SQL*Net/Net8 Listener.

vpo-volume-etc Volume Stop Volume.

vpo-volume-ora-core Volume Stop Volume.

vpo-volume-ora-data Volume Stop Volume.

Appendix C478


3. Service Group is put Offline

Service group vpo-sg is put offline on system mystic.

4. Service Resources are put Online

Service resources of service group vpo-sg are then put online on myrtle in the following order:

• vpo-dg

• vpo-volume-etc, vpo-volume-var, vpo-volume-ora-core, vpo-volume-ora-data

• vpo-ip, vpo-mount-etc, vpo-mount-var, vpo-mount-ora-core, vpo-mount-ora-data

• vpo-sqlnet

• vpo-oracle

• vpo-server

Since service resources are of different resource types, the following actions are actually performed for each set of resources of the same type during the switch of service group vpo-sg. See Table C-2.

vpo-volume-var Volume Stop Volume.

Table C-1 Service Resource Actions (Offline)

Service Resource Resource Type Action (Offline)

Table C-2 Service Resource Actions (Online)

Service Resource Resource Type Action (Online)

vpo-dg DiskGroup Import Disk Group.

vpo-ip IP Configure Virtual IP Address.

vpo-mount-etc Mount Mount File System.

vpo-mount-ora-core Mount Mount File System.

vpo-mount-ora-data Mount Mount File System.

vpo-mount-var Mount Mount File System.

Appendix C 479


5. Service Group is Online

Service group vpo-sg is now online on system myrtle.

vpo-oracle VPOOracle Start Oracle OpenView Database.

vpo-server VPOServer Start OpenView Platform.

vpo-sqlnet VPOSqlnet Start SQL*Net/Net8 Listener.

vpo-volume-etc Volume Start Volume.

vpo-volume-ora-core Volume Start Volume.

vpo-volume-ora-data Volume Start Volume.

vpo-volume-var Volume Start Volume.

Table C-2 Service Resource Actions (Online)

Service Resource Resource Type Action (Online)

Appendix C480

Administration of VERITAS Cluster ServerRunning VPO Agents in a VERITAS Cluster Server Environment

Running VPO Agents in a VERITAS Cluster Server EnvironmentThe VPO agent software can only be installed on physical VERITAS Cluster Server nodes.

It is not possible to install the VPO agent software on virtual VERITAS Cluster Server nodes; nor is it possible to assign any templates to these virtual nodes. Instead, virtual nodes can be managed as message-allowed nodes in the VPO Node Bank which means that messages can be received. One exception to this is the virtual cluster in which the management server runs. For more information, refer to Appendix B, “Installing VPO in a VERITAS Cluster Server Environment” of the VPO Installation Guide for the Management Server.

Appendix C 481

Administration of VERITAS Cluster ServerTroubleshooting VPO in a VERITAS Cluster Server Environment

Troubleshooting VPO in a VERITAS Cluster Server Environment

VPO/VERITAS Cluster Server Logfiles

The following logfiles are used by VPO/VERITAS Cluster Server:

❏ /var/VRTSvcs/log/engine_A.log

Main VCS logfile where all actions are logged, including messages sent by VPO resources vpo-server, vpo-oracle and vpo-sqlnet.

❏ /var/VRTSvcs/log/hashadow-err_A.log

VCS error messages from VCS Engine (had) and VCS Engine Shadow (hashadow) processes are logged into hashadow_A.log.

❏ /var/VRTSvcs/log/hashadow_A.log

Start/Stop messages of VCS Engine and other messages are logged here.

❏ /var/VRTSvcs/log/VPOServer_A.log/var/VRTSvcs/log/VPOOracle_A.log/var/VRTSvcs/log/VPOSqlnet_A.log

All messages regarding service resources vpo-server, vpo-oracle and vpo-sqlnet from VCS Engine or VCS Agents (VPOServerAgent, VPOOracleAgent and VPOSqlnetAgent) are logged here.

Appendix C482

Administration of VERITAS Cluster ServerPreconfigured Elements

Preconfigured Elements

Templates and Template Groups

Template Group

VERITAS Cluster Server HA

The template group VERITAS Cluster Server HA contains the following two template subgroups:

❏ VCS Virtual Management Server

❏ VCS Physical Management Server

Logfile Templates

Following is a list of VERITAS Cluster Server related logfile templates:

❏ Application (VCS)

❏ DiskGroup (VCS)

❏ DiskReservation (VCS)

❏ Disk (VCS)

❏ ElifNone (VCS)

❏ FileNone (VCS)

❏ FileOnOff (VCS)

❏ FileOnOnly (VCS)

❏ IPMultiNIC (VCS)

❏ IP (VCS)

❏ Mount (VCS)

❏ MultiNICA (VCS)

❏ NFS (VCS)

❏ NIC (VCS)

❏ Phantom (VCS)

Appendix C 483


❏ Process (VCS)

❏ Proxy (VCS)

❏ ServiceGroupHB (VCS)

❏ Share (VCS)

❏ VPOOracle (VCS)

❏ VPOServer (VCS)

❏ VPOSqlnet (VCS)

❏ Volume (VCS)

❏ Engine

❏ Engine Shadow Error

❏ Engine Shadow

Monitor Templates

Following is a list of VERITAS Cluster Server related monitor templates:

❏ had

❏ hashadow

❏ vmsa_server

❏ vxconfigd

Appendix C484


Applications and Application Groups

Application Group

VERITAS

The application group VERITAS contains the following two applications:

❏ VERITAS CSCM (VERITAS Cluster Server Cluster Manager)

❏ VERITAS VMSA (VERITAS Volume Manager Storage Administrator)

VERITAS Cluster Server Cluster Manager application

VERITAS Cluster Server Cluster Manager application enables you to monitor and manage the cluster configuration and status of service groups and their resources.

VERITAS Volume Manager Storage Administrator application

VERITAS Volume Manager Storage Administrator application provides Java-based GUI to users and can be used to administer Volume Manager Objects, disks and file systems. Note that Volume Manger Storage Administrator Server (vmsa_server) and Volume Manager Configuration Daemon (vxconfigd) must be running on the system to run Volume Manager Storage Administrator (VMSA) GUI.

Appendix C 485


Appendix C486

Master Index

Symbols<$#> variable, AR_I:163<$*> variable, AR_I:163<$\>+1> variable, AR_I:163<$\>+2> variable, AR_I:164<$\>1> variable, AR_I:163<$\>-2> variable, AR_I:164<$\>-n> variable, AR_I:164<$@> variable, AR_I:163

Numerics<$1> variable

logfiles, AR_I:160SNMP traps, AR_I:163

A“A” message attribute, AR_I:76<$A> variable, AR_I:164“aa*” temporary file, AR_I:308“Abend log” template, AR_II:187About “Virtual Terminal”, AR_II:160access

See also accessingfile permissions, AR_I:416remote, AR_I:420restrictions, CG:62terminal, CG:206

accessingSee also accessfiles, CG:206GUI

administrator, AR_I:417Java, AR_I:418Motif, AR_I:417

Jovw, AR_I:287–AR_I:289man pages

command line, AR_I:497HTML format, AR_I:497

managed node MIB, AR_I:386–AR_I:387NNM, AR_I:279–AR_I:281OpenView applications, CG:147programs

HP-UX, AR_I:418MPE/iX, AR_I:418

quick filters, CG:195terminal, CG:164VPO, AR_I:415

account, primary, AR_I:421acknowledgements

See also acknowledging messages; messages

annotating, CG:343automatic, CG:157description, CG:169reviewing, CG:170

acknowledging messagesSee also acknowledgements; messagesescalated messages, CG:429message keys, CG:342notification messages, CG:451

“ACL Info” application, AR_II:435“actagtp” pipe file, AR_I:307“actagtq” queue file, AR_I:307action

See also actionsagents, AR_I:223variables, AR_I:158–AR_I:159

Action Report, AR_I:111action-allowed managers

configuring, CG:435specifying, CG:445

ACTIONALLOWMANAGERS keyword, AR_I:120

actionsSee also actionapplying to all nodes in hierarchy,

CG:214–CG:215automatic, CG:57–CG:58centralizing, CG:283control-switched messages, CG:450enabling on secondaring manager, CG:444evaluating results, CG:155integrating applications as,

AR_I:223–AR_I:224operator-initiated, CG:59–CG:60overview, CG:57–CG:60protecting, AR_I:424–AR_I:427responding to messages, CG:369scheduled, AR_I:167“stderr”, CG:155“stdout”, CG:155verifying

automatic, CG:156–CG:157operator-initiated, CG:157–CG:158

487AR_I VPO Administrator’s Reference Volume IAR_II VPO Administrator’s Reference Volume IICG VPO Concepts Guide

Master Index

“Actions” policy, CG:124activating

managed nodesAIX, AR_II:47–AR_II:49HP-UX, AR_II:86–AR_II:89,

AR_II:333–AR_II:336tracing, AR_I:328–AR_I:330

active message browserSee also filtered message browser; history

message browser; message browser; pending messages browser

figure, CG:98overview, CG:101–CG:102

“actreqp” pipe file, AR_I:301“actreqq” queue file, AR_I:301“actrespp” pipe file, AR_I:301“actrespq” queue file, AR_I:301“Adapters” application, AR_II:194Add Configuration window, CG:292Add MPE/iX Console Messages window,

CG:399Add Node for External Events window,

CG:217Add SNMP Trap window, CG:394adding

annotations, CG:166message groups, CG:233, AR_I:73nodes to VPO, CG:217–CG:229

external nodes, CG:219from IP submaps, CG:222from VPO Add Node window,

CG:224–CG:227internal nodes, CG:217methods, CG:210node groups, AR_I:71with templates, CG:292

SNMP trap templates, CG:394tabs to browser pane, CG:195VPO variables, CG:162

administrative rightsSee also VPO administrator

administrator. See template administrators; VPO administrator

adoptive node, AR_II:448See also cluster nodes, MC/ServiceGuard;

managed nodes, upgrading; original node

advanced options

message conditions, CG:384MPE/iX console messages, CG:400

advantagesbackups

automatic, AR_I:441offline, AR_I:439

flexible management, CG:423operator message browser, CG:203OVKey licenses, AR_I:462template groups, CG:288

“agdbserver” monitor template, AR_II:225agent accounts

Windows NT/2000, AR_II:358–AR_II:360agents. See action agents; VPO agentsaging, password, AR_I:419AIX managed nodes

DCEconfiguring, AR_II:44–AR_II:45requirements, AR_II:40

HACMPinstalling agents, AR_II:56–AR_II:57resetting IP, AR_II:54

NCS requirements, AR_II:40OVPA, AR_II:211VPO

activating, AR_II:47–AR_II:49default operator, AR_II:67de-installing agents, AR_II:58directory structure, AR_II:66file locations, AR_II:66hardware requirements, AR_II:39include file, AR_II:69installation requirements,

AR_II:39–AR_II:40installation tips, AR_II:41–AR_II:43installing agents, AR_II:46–AR_II:49libraries, AR_II:68–AR_II:70logfile locations, AR_I:460logfile templates, AR_II:59–AR_II:60makefile, AR_II:70monitored objects, AR_II:62organization, AR_II:66–AR_II:67overview, AR_II:37–AR_II:70preconfigured elements,

AR_II:59–AR_II:63removing agents, AR_II:58scripts and programs, AR_II:64–AR_II:65

488 AR_I VPO Administrator’s Reference Volume IAR_II VPO Administrator’s Reference Volume IICG VPO Concepts Guide

Master Index

SMIT User Interface, AR_II:63SNMP event interceptor, AR_II:61software requirements, AR_II:39–AR_II:40system resource files, AR_II:67template groups, AR_II:59troubleshooting IP aliases,

AR_II:53–AR_II:54“AIX” template group, AR_II:59“AIX with HACMP” template group, AR_II:59“alarmgen” monitor template, AR_II:225All Active Details Report, AR_I:114All Active Messages Report, AR_I:111,

AR_I:114All History Messages Report, AR_I:111,

AR_I:114All Pending Details Report, AR_I:114All Pending Messages Report, AR_I:114alternative accounts

Windows NT/2000, AR_II:359–AR_II:360analyzing

data with OVPA, AR_II:212symptoms in VPO, AR_I:334

annotatingacknowledgements, CG:343messages

escalated, CG:430notification, CG:451

annotationsoverview, CG:166–CG:168reviewing, CG:155–CG:156

APIsman pages

VPO, AR_I:501managed nodes, AR_I:483message, CG:367–CG:368MSI, AR_I:228Novell NetWare, AR_II:205–AR_II:206“opcmsg (3)”, AR_II:106

Application Desktop window, CG:66“Application” message attribute, AR_I:77applications

accessing OpenView, CG:147assigning to operators, AR_I:213“Broadcast”, CG:155Citrix MetaFrame, AR_II:435–AR_II:438configuring templates, CG:306customizing, CG:161HP-UX

ASCII SAM, AR_II:95EMS Resources, AR_II:110–AR_II:111Motif SAM, AR_II:95

integrating into VPOactions, AR_I:223–AR_I:224Application Desktop, AR_I:214–AR_I:215broadcast command, AR_I:222components, AR_I:213“Ethernet Traffic HP” as an OV

application, AR_I:218HP applications, AR_I:213monitoring applications, AR_I:225NNM, AR_I:215, AR_I:216–AR_I:221OpenView plug-in, AR_I:214overview, AR_I:211–AR_I:230VPO applications, AR_I:214

intercepting messages, AR_I:227Java GUI

comparisons, AR_I:268OpenView, AR_I:281–AR_I:283

monitoring logfiles, AR_I:226Motif GUI, AR_I:268MPE/iX, AR_II:158–AR_II:160Novell NetWare

NetWare Tools, AR_II:194–AR_II:197NMA, AR_II:197–AR_II:199overview, AR_II:189–AR_II:199

OVPA, AR_II:223solving problems, CG:160–CG:161SSP Tools, AR_II:315starting, CG:160

accounts, AR_I:419I/O, AR_I:420managed nodes, AR_I:229–AR_I:230remotely, AR_I:420

tailored set, CG:190variables, AR_I:169–AR_I:183VPO

description, CG:60types, CG:216

Windows NT/2000, AR_II:392–AR_II:423Applications folder

figure, CG:81overview, CG:81

applying actions to all nodes in hierarchy, CG:214–CG:215

architecture

AR_I VPO Administrator’s Reference Volume IAR_II VPO Administrator’s Reference Volume IICG VPO Concepts Guide

489

Master Index

scalable, CG:419–CG:467Sun Clusters, AR_II:465

archive log modedatabase

description, AR_I:442enabling, AR_I:443–AR_I:444

description, AR_I:438ARPA hostnames, mapping to NS node

names, AR_II:164–AR_II:167ASCII character sets, AR_I:244ASCII SAM, AR_II:95assigning

applications to operators, AR_I:213IP addresses and hostnames to packages,

AR_II:455IP addresses to LAN interface cards,

AR_II:455passwords

managed nodes, AR_I:422–AR_I:423MPE/iX, AR_I:422Novell NetWare, AR_I:423UNIX, AR_I:422Windows NT, AR_I:423

templatesdistributing, CG:293managed nodes, CG:291overview, CG:291–CG:293

attributescustom message

overview, CG:138viewing, CG:139

messageexamining, CG:135modifying, CG:136

message forwarding, CG:425message forwarding templates, AR_I:137messages, AR_I:75–AR_I:77MPE/iX console message templates

defaults, CG:400“Audit Log (AIX)” template, AR_II:60Audit Report, AR_I:111auditing, CG:206

levels, AR_I:428–AR_I:431modes, AR_I:428security, AR_I:428–AR_I:431

“Auditlog” application, AR_II:435authentication, CG:206

configuring DCE nodes to use authenticated RPCs, AR_I:407

processes, AR_I:312–AR_I:314RPC, AR_I:410–AR_I:411

Automatic (De-)Installation option, AR_I:51automatic actions

corrective actions, CG:369process, CG:57–CG:58protecting, AR_I:424rerunning, CG:156reviewing, CG:156

automatic backupsadvantages, AR_I:441disadvantages, AR_I:442excluding files

database, AR_I:442temporary, AR_I:442

overview, AR_I:440–AR_I:449recovering configuration data,

AR_I:449–AR_I:451automatic de-installation

See also de-installingAIX, AR_II:58HP-UX, AR_II:89Linux, AR_II:127

automatic installationSee also installingAIX, AR_II:46

automating standard scenarios, CG:341avoiding duplicate messages, CG:393

Bbacking up data on management server,

AR_I:438–AR_I:451“Backup” message group, AR_I:72backups

automatic, AR_I:440–AR_I:449recovering configuration data,

AR_I:449–AR_I:451offline, AR_I:439server, CG:445tools, AR_I:438

“backup-server” template, AR_I:117“Bad Logs (10.x/11.x HP-UX)” logfile,

AR_II:91“Bad logs (AIX)” template, AR_II:60“Bad Logs (IRIX)” template, AR_II:253


Master Index

“Bad Logs (SINIX)” template, AR_II:272“Bad Logs (Solaris)” template, AR_II:297benefits, VPO, CG:39binaries

common, AR_I:188customized, AR_I:189filenames, AR_I:192

“Boot (10.x/11.x HP-UX)” logfile, AR_II:91“Boot the NetWare Server (NCF)”

application, AR_II:194“Bound Protocols” application, AR_II:194“Broadcast” application, CG:155, AR_II:158broadcast commands

integrating applications, AR_I:222starting

on managed nodes, AR_I:229–AR_I:230remotely, AR_I:420

broadcasting commandsoverview, CG:163–CG:164

browser paneadding tabs, CG:195figures

disabled, CG:187main window, CG:95message browser, CG:96popup menu, CG:116

hiding, CG:187overview, CG:95–CG:97popup menus, CG:116

Browser Settings dialog boxfigure, CG:194

browsing messages effectively, CG:123–CG:128

buffering messagesdescription, CG:43parameters, AR_I:131service hours, CG:415

building managed nodes, CG:208Bull DPX/20, AR_II:65

C<$C> variable, AR_I:164C2 security

guidelines, AR_I:402overview, CG:206–CG:207restrictions, CG:207, AR_I:403techniques, CG:206

“Cancel Reboot” application, AR_II:392

case-sensitivity in pattern-matching, CG:316catalogue, message, CG:296CCD, AR_II:464CCDD, AR_II:464central

competence centers, CG:426–CG:427management server

action-allowed manager, CG:435configuring, CG:438description, CG:435secondary manager, CG:436

centralizing actions, CG:283“cfgchanges” file, AR_I:301Change Operator Password dialog box

figure, CG:172changing

character setlogfile encapsulator, AR_I:244managed node, AR_I:243

communication types, AR_I:54–AR_I:56defaults

property type of all messages forwarded to VPO, AR_I:208

WMI policy name, AR_I:208hostnames, AR_I:466–AR_I:480IP addresses, AR_I:466–AR_I:480look and feel of Java GUI, CG:181operator passwords

overview, CG:172passwords, AR_I:415refresh interval, CG:178user names, AR_I:415VPO administrator responsibility matrix,

CG:204character code conversion,

AR_I:250–AR_I:256character sets

ASCII, AR_I:244changing

logfile encapsulator, AR_I:244managed nodes, AR_I:243

converting, AR_I:250–AR_I:256English language

configuring, AR_I:250–AR_I:253supported, AR_I:242types, AR_I:245–AR_I:246

Euro symbol, AR_I:241


491

Master Index

external on managed nodes, AR_I:244–AR_I:247

ISO 8859-15, AR_I:241Japanese language

configuring, AR_I:254–AR_I:256supported, AR_I:243types, AR_I:247

logfile encapsulator, AR_I:248–AR_I:249Spanish language

supported, AR_I:242charts

current state, CG:143history, CG:145

“Check alarmdef” application, AR_II:223“Check parm” application, AR_II:223“Config perflbd.rc” application, AR_II:223choosing web browser, CG:188Citrix MetaFrame

applications, AR_II:435–AR_II:438integration

configuring agent, AR_II:431configuring server, AR_II:432ICA Browser service, AR_II:432installing agent, AR_II:431logfile templates, AR_II:434monitored objects, AR_II:433overview, AR_II:430–AR_II:434Program Neighbourhood service,

AR_II:433software requirements, AR_II:430versions supported, AR_II:430

classifying unmatched messages, CG:55client-server concept, CG:40–CG:41closing

EMS GUI, AR_II:109messages, CG:165

Cluster Configuration Database. See CCDCluster Configuration Database Daemon.

See CCDDclusters, mixed, AR_I:192CMIP events

forwarding, CG:392–CG:393overview, CG:390–CG:397

coda, CG:374“coda” process, AR_I:304“Cold Boot the NetWare Server (NCF)”

application, AR_II:194collecting messages, CG:297–CG:298

“colored_message_lines” optionito_op, AR_I:271itooprc, AR_I:273

colorsfigures

message browser, CG:99object pane, CG:130shortcut bar, CG:130

message browser, CG:196Message Groups folder, CG:79messages

changing, CG:99locations, CG:129–CG:131

Nodes folder, CG:78columns, message browser

customizing, CG:196hiding, CG:197showing, CG:197

command lineaccessing man pages, AR_I:497activating VPO agents

AIX, AR_II:47Solaris, AR_II:292

interface, AR_I:135license maintenance tool,

AR_I:464–AR_I:465NNM tools, AR_I:283

command tracing, AR_I:67commands

broadcasting, CG:163–CG:164integrating applications as broadcast,

AR_I:222“opcctrlovw”, AR_I:283“opclic”

parameters, AR_I:464–AR_I:465syntax, AR_I:464

“opcmapnode”, AR_I:283“opcwall”, AR_I:444“ovbackup.ovp”, AR_I:445–AR_I:446“ovrestore.ovpl”, AR_I:446–AR_I:449“stderr”, CG:155“stdout”, CG:155synchronizing with VPO agent character

set, AR_I:240communication

competence centers, CG:427links


Master Index

central server configuration, CG:438manufacturing environment, CG:433

software typeschanging, AR_I:54–AR_I:56description, AR_I:41

VPO, AR_I:295–AR_I:296community name

“opcinfo” file, AR_I:386SNMP daemon configuration file, AR_I:387

comparing messages with conditionsmatch conditions, CG:312–CG:314preconfigured templates, CG:43

competence centerscommunication flow, CG:427configuring, CG:427distributing responsibility, CG:426–CG:427overview, CG:426–CG:427

componentembedded performance, CG:374

components, integrating into VPO, AR_I:213compression setting types, CG:350concepts

client-server, CG:40–CG:41message forwarding, CG:448user, CG:61–CG:67

Condition No. window, CG:386conditions

advanced threshold monitoring, CG:385–CG:386

applying to events, CG:312match, CG:312–CG:314message

description, CG:311–CG:314overview, CG:307–CG:331setting up, CG:310–CG:311

modifying, CG:315multiple for threshold monitoring,

CG:387–CG:388organizing, CG:314–CG:315pattern-matching examples,

CG:316–CG:317regroup

defining, CG:359examples, CG:360

selecting, CG:315sequence, CG:332SNMP trap templates

defining, CG:394–CG:395example, CG:396

specifying for message templates, CG:366status variables, AR_I:132suppress

deploying, CG:333description, CG:311–CG:314

threshold monitor examples, CG:389types, CG:315

CONDSTATUSVARS keyword, AR_I:119“Config alarmdef” application, AR_II:223“Config parm” application, AR_II:223“Config ttd.conf” application, AR_II:223configuration

See also configuringC2 security restrictions, CG:207distributing VPO agent to managed nodes,

AR_I:187downloading data, AR_I:435–AR_I:437file

distributing, CG:446–CG:447downloading, CG:446responsible manager, CG:439–CG:440uploading, CG:446

installing on managed nodes, AR_I:185–AR_I:192

loading default, CG:173–CG:178protecting distribution, AR_I:423updating on managed nodes,

AR_I:185–AR_I:192Configure Management Server window,

AR_I:191configuring

See also configurationapplication-specific templates, CG:306automatic acknowledgements, CG:157basic Distributed Event Interception,

AR_II:93central server, CG:435Citrix MetaFrame

agent, AR_II:431server, AR_II:432

competence centers, CG:427database on multiple disks,

AR_I:453–AR_I:455DCE

AIX, AR_II:44–AR_II:45


493

Master Index

managed nodes, AR_I:405management server, AR_I:405SINIX RM/Reliant, AR_II:269Tru64 UNIX, AR_II:330–AR_II:331

ECS event interception, AR_II:94EMS templates, AR_II:112escalation policies, CG:429event correlation, CG:406filenames on MPE/iX managed nodes,

AR_II:157filtered message browsers, CG:192flexible management templates,

AR_I:117–AR_I:152managed nodes

description, CG:44hierarchies, CG:435regional management servers,

CG:437–CG:438management server

central, CG:438English language, AR_I:250–AR_I:253Japanese language, AR_I:254–AR_I:256regional, CG:437–CG:438responsible, CG:439–CG:447

NNM access with command-line tools, AR_I:283

nodeauthenticated RPCs, AR_I:407DCE cell, AR_I:407

OpenView Operations for Windowsagents for VPO management server,

AR_I:200–AR_I:202servers to forward messages to VPO,

AR_I:203–AR_I:208RPC authentication in VPO, AR_I:411scheduled outages, CG:418service hours, CG:418templates

message forwarding, AR_I:137message source, CG:286multiple, CG:303

threshold monitors, CG:384time-indifferent templates, CG:442timeouts for report generation, AR_I:110VantagePoint for Windows

agents on OpenView Operations for Windows management server, AR_I:207

VPOagents for OpenView Operations for

Windows management server, AR_I:196–AR_I:199

elements, CG:199–CG:280messages forwarded from OpenView

Operations for Windows, AR_I:205–AR_I:207

preconfigured elements, AR_I:69–AR_I:183Configuring_DCE, AR_II:44“Connections” application, AR_II:194console messages, MPE/ix, CG:398–CG:401console settings

saving, CG:179–CG:180consolidating messages in browser, CG:284continuous message generation, CG:381control

files, AR_I:454follow-the-sun, CG:424–CG:426managed nodes, CG:209message

sharing, CG:449switching, CG:449–CG:450

controller tool, AR_I:284–AR_I:285converting

character sets, AR_I:250–AR_I:256managed node files

EUC, AR_I:255ROMAN8, AR_I:252

managed nodes to EUC, AR_I:258management server to EUC, AR_I:257

copying and pasting nodes, CG:223See also dragging and dropping nodes

corrective actionsautomatic, CG:369managed node, CG:43operator-initiated, CG:369

Corrective Actions workspacedescription, CG:90evaluating action results, CG:155

correlatingevents

description, CG:51, CG:403–CG:404NNM, CG:407


Master Index

overview, CG:403–CG:410messages, CG:336

different sources, CG:405flexible management environments,

CG:410managed nodes, CG:405, CG:408management server, CG:405, CG:409

messages and events, CG:334counter-based suppression, CG:352“CPU Info” application, AR_II:195“cpu_util” object

SGI IRIX, AR_II:254HP-UX, AR_II:94Linux, AR_II:129Sequent DYNIX, AR_II:238SINIX RM/Reliant, AR_II:273Solaris, AR_II:301Tru64 UNIX, AR_II:339

creatingconfiguration file

responsible managers, CG:439message

source templates, CG:287status, CG:297

mirror online redo logs, AR_I:455primary account manually, AR_I:421SD-UX depot on remote node,

AR_II:80–AR_II:81template

group hierarchies, CG:289groups, CG:289

“Critical” message severity level, AR_I:74“Cron (10.x/11.x HP-UX)” logfile, AR_II:91“Cron (DYNIX/ptx)” template, AR_II:237“Cron (IRIX)” template, AR_II:253“Cron (RedHat Linux)” template, AR_II:128“Cron (SINIX)” template, AR_II:272“Cron (Solaris)” template, AR_II:297“Cron” (Tru64 UNIX) template, AR_II:337“ctrlp” pipe file, AR_I:301“ctrlq” queue file, AR_I:301current state chart

figuresbar chart, CG:143pie chart, CG:144

overview, CG:143custom message attributes

adding to your message, CG:325

overview, CG:138setting defaults, CG:301viewing, CG:139

Customize Message Browser Columns dialog box

figuresCustom tab, CG:128General tab, CG:127

customized job stream facilitypreparing VPO, AR_II:149setting up on MPE/iX managed nodes,

AR_II:148customizing

applications, CG:161binaries, AR_I:189Java GUI, CG:171message browser columns

attributes, CG:126layout, CG:196

message event notification, CG:191operator environment, CG:171OVPA, AR_II:213popup menus, CG:189–CG:190reports

administrator, AR_I:113operator, AR_I:115

scripts, AR_I:189shortcut bar, CG:188

DDaemon, MC/ServiceGuard, AR_II:448daemons

DCEMPE/iX, AR_II:143

NCS, AR_II:143RPC

MPE/iX, AR_II:143troubleshooting, AR_I:381

SNMP, AR_I:387SSP snmpd, AR_II:316

Data Service, AR_II:464data, backing up on management server,

AR_I:438–AR_I:451database

archive log modedescription, AR_I:438, AR_I:442enabling, AR_I:443–AR_I:444


495

Master Index

configuring on multiple disks, AR_I:453–AR_I:455

excluding files from automatic backups, AR_I:442

group, message target rule example, CG:441improving performance, AR_I:319maintaining, AR_I:452moving control files to second disk, AR_I:454recovering, AR_I:450–AR_I:451removing queue files, AR_I:451reports, AR_I:110–AR_I:116restoring, AR_I:450restricting access, AR_I:116security, AR_I:419tables and tablespaces

non-VPO, AR_I:492VPO, AR_I:487

troubleshooting, AR_I:340–AR_I:342“Database” message group, AR_I:72“Date” message attribute, AR_I:77DCE

changing, AR_I:54–AR_I:56configuring

AIX, AR_II:44–AR_II:45managed nodes, AR_I:405management server, AR_I:405SINIX RM/Reliant, AR_II:269Tru64 UNIX, AR_II:330–AR_II:331

description, AR_I:41nodes

configuring to run in DCE cell, AR_I:407configuring to use authenticated RPCs,

AR_I:407description, AR_I:406installing, AR_I:406login failure, AR_I:421passwords, AR_I:420–AR_I:421

removingAIX, AR_II:45SINIX RM/Reliant, AR_II:270Tru64 UNIX, AR_II:331

security, AR_I:404–AR_I:409servers

description, AR_I:406installing, AR_I:405

de-activatingtracing, AR_I:330

debugging software (de-)installation, AR_I:67–AR_I:68

“def_browser” option, AR_I:271“def_help_url” option, AR_I:273“def_look_and_feel” option

ito_op, AR_I:271itooprc, AR_I:273

default VPO operatorAIX, AR_II:67HP-UX, AR_II:100Linux, AR_II:134–AR_II:135MPE/iX, AR_II:163Novell NetWare, AR_II:203Sequent DYNIX, AR_II:242SGI IRIX, AR_II:258SINIX RM/Reliant, AR_II:277Solaris, AR_II:305Tru64 UNIX, AR_II:343Windows NT/2000, AR_II:427

“default_browser” option, AR_I:273defaults

assigned byadministrator, CG:177VPO, CG:174

IP map, AR_I:287loading configuration, CG:173–CG:178management server setup, CG:422message

groups, AR_I:71–AR_I:73mapping on MPE/iX, AR_II:151templates on MPE/iX, CG:400

node groups, AR_I:71threshold monitor, CG:385trap and event interception, CG:390WMI policy name, AR_I:208working directory, AR_I:416

Define Configuration window, CG:291defining

conditionsmessages, CG:384regroup, CG:359SNMP trap templates, CG:394–CG:395

message groups, CG:56report printer, AR_I:110scheduled outages, CG:417service hours, CG:416templates


Master Index

logfiles, CG:364messages, CG:365, CG:394MPE/iX console messages, CG:399

de-installation debuggingdisabling, AR_I:68enabling, AR_I:68facilities, AR_I:67

de-installingSee also automatic de-installation;

installing; manual de-installation; removing; standard de-installation

OVPA managed nodesHP-UX, AR_II:221Solaris, AR_II:221

VPO agents from managed nodesAIX, AR_II:58automatically, AR_I:62–AR_I:63HP-UX, AR_II:89Linux, AR_II:127manually, AR_I:63MPE/iX, AR_II:149Sequent DYNIX, AR_II:236SGI IRIX, AR_II:252SINIX RM/Reliant, AR_II:271Solaris, AR_II:294Tru64 UNIX, AR_II:336Windows NT/2000, AR_II:379

De-installing Agents, AR_II:127De-installing Agents Automatically,

AR_II:127delegating manager responsibilities, CG:444deleting

message groups, AR_I:73node groups, AR_I:71

deploying suppress unmatched conditions, CG:333

depot nodes, AR_II:79DESCRIPTION keyword, AR_I:119“Description” message attribute, AR_I:77detecting problems

browsing messages effectively, CG:123–CG:128

early, CG:283message

event notification, CG:122severity coloring, CG:129–CG:131

monitoring VPO, CG:120

overview, CG:119searching object tree, CG:121viewing messages in message browser,

CG:122“dflt_DirectoryEvLog (2000)” template,

AR_II:381“dflt_DNSEvLog (2000)” template, AR_II:381“dflt_FileReplicationEvLog (2000)” template,

AR_II:381Diagnostic Dashboard workspace

accessing OpenView applications, CG:147overview, CG:89

“Diagnostics” application, AR_II:393Digital UNIX. See Tru64 UNIX managed

nodesdirectories

See also files; target directories; temporary directories

AIX, AR_II:65, AR_II:162HP-UX, AR_II:97, AR_II:132maintaining, AR_I:457Novell NetWare, AR_II:201runtime data on managed nodes, AR_I:459Sequent DYNIX, AR_II:240SGI IRIX, AR_II:256SINIX RM/Reliant, AR_II:275Solaris, AR_II:303Tru64 UNIX, AR_II:341Windows NT/2000, AR_II:425working, AR_I:416

disabled nodesSee also disablingdescription, CG:209managing, CG:229

disablingSee also disabled nodes; enabling(de-)installation debugging, AR_I:68primary account manually, AR_I:421

disadvantages of backupsautomatic, AR_I:442offline, AR_I:439

“Disconnect” application, AR_II:436“Disk Space” application, AR_II:159disk space requirements, OVPA

HP-UX, AR_II:218Solaris, AR_II:218

“disk_util” objectAIX, AR_II:62


497

Master Index

HP-UX, AR_II:94Linux, AR_II:129Sequent DYNIX, AR_II:238SGI IRIX, AR_II:254SINIX RM/Reliant, AR_II:273Solaris, AR_II:301Tru64 UNIX, AR_II:339

“Disks” application, AR_II:195disks, multiple, AR_I:453–AR_I:455“Display a File” application, AR_II:195display modes, ownership, CG:154,

CG:272–CG:273“display” option


displayingavailable VPO agent versions, AR_I:65installed VPO agent versions, AR_I:65message

defaults, CG:303groups, AR_I:72

“dispp<#>” pipe file, AR_I:301“dispq<#>” queue file, AR_I:301Distributed Computing Environment. See

DCEDistributed Event Interception

configuring, AR_II:93description, AR_II:92

distributingSee also distributionconfiguration file

other servers, CG:446–CG:447responsible managers, CG:440

managed nodesscripts and programs, AR_I:188–AR_I:192VPO agent configuration, AR_I:187

responsibility in competence centers, CG:426–CG:427

templatesassigned, CG:293description, CG:283message source, CG:293–CG:294

distributionSee also distributinglists

controlling size, CG:453–CG:455overview, CG:453–CG:456

manager, AR_I:189

scripts and programsAIX, AR_II:64–AR_II:65HP-UX, AR_II:96–AR_II:98Linux, AR_II:130–AR_II:132MPE/iX, AR_II:161–AR_II:162Novell NetWare, AR_II:200–AR_II:201requirements, AR_I:188Sequent DYNIX, AR_II:239–AR_II:240SGI IRIX, AR_II:255–AR_II:256SINIX RM/Reliant, AR_II:274–AR_II:275Solaris, AR_II:302–AR_II:303tips, AR_I:188–AR_I:191Tru64 UNIX, AR_II:340–AR_II:341UNIX, AR_I:192Windows NT/2000, AR_II:424–AR_II:425

documentation, relatedOVPA, AR_II:227–AR_II:230

documenting solutions, CG:46acknowledging messages, CG:169–CG:170annotating messages, CG:166–CG:168overview, CG:165printing, CG:168

domain, worldwide management, CG:424Download Configuration Data window

description, AR_I:435–AR_I:437figure, AR_I:436opening, AR_I:437

downloadingconfiguration

data, AR_I:435–AR_I:437files, CG:446

EMS templates, AR_II:112OVPA documentation, AR_II:227

dragging and dropping nodes, CG:224See also copying and pasting nodes

duplicate messagesavoiding, CG:393suppressing

flexible management environments, CG:355

management server, CG:353–CG:355overview, CG:347

DYNIX. See Sequent DYNIX managed nodes“DYNIX/ptx” template group, AR_II:237


Master Index

E“E” message attribute, AR_I:77<$E> variable, AR_I:164<$e> variable, AR_I:164ECS, configuring, AR_II:94elements, preconfigured, AR_I:71–AR_I:109embedded performance component, CG:374

troubleshooting, AR_I:382–AR_I:385EMS

See also “EMS Resources” applicationerrors, AR_II:111GUI

closing, AR_II:109overview, AR_II:109–AR_II:110starting, AR_II:109viewing resource instances, AR_II:109

“opcmsg (3)” API, AR_II:106overview, AR_II:106–AR_II:112resource hierarchy

command line, AR_II:112GUI, AR_II:109–AR_II:110VPO Application Bank window,

AR_II:110–AR_II:111sending notifications to VPO, AR_II:112templates

configuring, AR_II:112downloading, AR_II:112

threshold monitoring, AR_II:106–AR_II:108VPO Application Bank window,

AR_II:110–AR_II:111“EMS Resources” application

See also EMSdescription, AR_II:110sample output, AR_II:111syntax, AR_II:111

enablingSee also disabling(de-)installation debugging, AR_I:68actions on secondary manager, CG:444archive log mode in database,

AR_I:443–AR_I:444duplicate message suppression on

management server, CG:354–CG:355internal VPO error message filtering,

AR_I:339JVM JIT compiler, AR_I:290

maintenance mode for MC/ServiceGuard packages, AR_II:459

operatorsto control VPO agents, AR_I:220–AR_I:221to manage IP networks in IP map,

AR_I:217SD-UX, AR_II:82

encapsulator, logfile, CG:361“Enforced” ownership mode, CG:153, CG:274English language

character sets, AR_I:245–AR_I:246HP-UX configuration and related character

sets, AR_I:250management server, AR_I:250–AR_I:253OVPA documentation, AR_II:228processing managed node files,

AR_I:252–AR_I:253Enterprise Servers, AR_II:98environmental variables, AR_I:154environments

customizing operator GUI, CG:171English language

character sets, AR_I:245–AR_I:246description, AR_I:242managed nodes with Japanese

management server, AR_I:244flexible management, CG:410Japanese language

description, AR_I:243external character sets, AR_I:247flexible management, AR_I:257–AR_I:258running English-language GUI, AR_I:236

loading default configuration, CG:173–CG:178

securing, CG:205–CG:207Spanish language

description, AR_I:242VPO administrator, CG:201–CG:204

errorsEMS, AR_II:111getting instructions with opcerr, AR_I:338logfiles, AR_I:335messages

filtering internal, CG:402, AR_I:339locations, AR_I:335

reportingGUI Error Dialog Box, AR_I:337–AR_I:338


499

Master Index

message browser, AR_I:336overview, AR_I:335–AR_I:339“stderr” and “stdout” devices, AR_I:338

escalating messages, CG:164See also messagesacknowledgements, CG:429annotations, CG:430guidelines, CG:429overview, CG:428–CG:431policy, CG:429process, CG:430–CG:431

“escmgr” template, AR_I:117establishing remote host equivalence,

AR_II:317Ethernet problems, AR_I:389“Ethernet Traffic HP”, integrating as an OV

application, AR_I:218EUC

managed node, AR_I:255management server, AR_I:257

Euro symbol, AR_I:241evaluating action results, CG:155evaluating messages

impact, CG:296severity, CG:296sources, CG:295–CG:296

Event Monitoring Service. See EMS<$EVENT_ID> variable, AR_I:160events

applying conditions, CG:312CMIP, CG:390–CG:397correlating

configuration, CG:406description, CG:403–CG:404event streams, CG:51NNM, CG:407overview, CG:403–CG:410synchronizing, CG:407template example, CG:411–CG:414with messages, CG:334

description, CG:50–CG:51Distributed Event Interception,

AR_II:92–AR_II:93ECS event interception, AR_II:94interceptor, CG:407monitoring

EMS, AR_II:106–AR_II:112HP-UX, AR_II:106–AR_II:112

resettingHACMP 4.2.2, AR_II:55HACMP 4.3.1, AR_II:55–AR_II:56

SNMP, CG:390–CG:397tracing, AR_I:67

“example.m2” template, AR_I:117“example.m3” template, AR_I:117examples

conditionsMPE/iX console message, CG:400–CG:401regroup, CG:360SNMP trap, CG:396

failover procedure, AR_II:466–AR_II:467message target rules

database group, CG:441printing group, CG:441

remote action flow, AR_I:425RPC authentication in VPO, AR_I:411templates

event correlation, CG:411–CG:414flexible management, AR_I:124,

AR_I:144–AR_I:152follow-the-sun responsibility switch,

AR_I:146–AR_I:148message forwarding between

management servers, AR_I:149–AR_I:150

responsibility switch, AR_I:144–AR_I:145scheduled outages, AR_I:152service hours, AR_I:151time, AR_I:139–AR_I:141

tracing, AR_I:331–AR_I:332exceptions warnings, system, AR_I:291excluding

files from automatic backups, AR_I:442networking commands from streamed jobs,

AR_II:147exporting SSP logfiles directory, AR_II:317external

character sets, AR_I:244–AR_I:247monitors, CG:372nodes

adding, CG:219characteristics, CG:220


Master Index

F<$F> variable, AR_I:165failover

definition, AR_II:464procedure example, AR_II:466–AR_II:467

“Failures” policy, CG:124features

Java and Motif GUIs, AR_I:270VPO, CG:23

filenamesbinary, AR_I:192MPE/iX, AR_II:157

filesSee also directories; include file; logfiles;

makefileaccess, CG:206, AR_I:416configuration

responsible managers, CG:439–CG:440control, AR_I:454converting managed node

EUC, AR_I:255ROMAN8, AR_I:252

excluding from automatic backupsdatabase, AR_I:442temporary, AR_I:442

HP_OV_consoleSettings, CG:180include file

AIX, AR_II:69HP-UX, AR_II:105Linux, AR_II:137MPE/iX, AR_II:168Novell NetWare, AR_II:207Sequent DYNIX, AR_II:244SGI IRIX, AR_II:260Solaris, AR_II:308Tru64 UNIX, AR_II:346Windows NT/2000, AR_II:429

itooprc, AR_I:273–AR_I:278location

AIX, AR_II:66HP-UX, AR_II:100Linux, AR_II:134MPE/iX, AR_II:163Novell NetWare, AR_II:202Sequent DYNIX, AR_II:241SGI IRIX, AR_II:257SINIX RM/Reliant, AR_II:276

Solaris, AR_II:304Tru64 UNIX, AR_II:342Windows NT/2000, AR_II:427

maintaining, AR_I:457makefile

AIX, AR_II:70HP-UX, AR_II:105Linux, AR_II:137MPE/iX, AR_II:169Novell NetWare, AR_II:208Sequent DYNIX, AR_II:245SGI IRIX, AR_II:261SINIX RM/Reliant, AR_II:280Solaris, AR_II:309Tru64 UNIX, AR_II:347Windows NT/2000, AR_II:429

mapping, AR_II:166.opc_brc_history, CG:164“opcinfo”, AR_I:386permissions, AR_I:416pipe

managed nodes, AR_I:307–AR_I:308management server, AR_I:301–AR_I:303

processmanaged node, AR_I:306–AR_I:309management server, AR_I:301–AR_I:303

processing managed nodeEnglish, AR_I:252–AR_I:253Japanese, AR_I:255–AR_I:256

processing management serverISO 8859-15, AR_I:251Shift JIS, AR_I:254

queuemanaged nodes, AR_I:307–AR_I:308management server, AR_I:301–AR_I:303removing, AR_I:451security, AR_I:427

SNMP daemon configuration, AR_I:387system resource

AIX, AR_II:67HP-UX, AR_II:101MPE/iX, AR_II:164Novell NetWare, AR_II:203Sequent DYNIX, AR_II:243SGI IRIX, AR_II:259SINIX RM/Reliant, AR_II:278


501

Master Index

Solaris, AR_II:305Tru64 UNIX, AR_II:344Windows NT/2000, AR_II:428

tracinglocation, AR_I:332syntax, AR_I:333

VPO agent configurationlocation, AR_I:311types, AR_I:310

Filter Messages dialog boxfigure, CG:149

Filter Settings folderfigure, CG:82overview, CG:82–CG:83

filtered message browserSee also active message browser; history

message browser; message browser; pending messages browser

activefigure, CG:101overview, CG:101–CG:102

configuring, CG:192history

figure, CG:103investigating problems, CG:148–CG:149overview, CG:103

pendinginvestigating problems, CG:150overview, CG:104

saving settings, CG:193–CG:194filtering messages

conditions, CG:307–CG:331description, CG:55internal error messages, CG:402, AR_I:339managed node, CG:332management server, CG:332multiple templates, CG:305sources, CG:307–CG:308

Find dialog boxfigures

advanced search, CG:121basic search, CG:121

finding impacted VP Navigator services, CG:147

flexible managementenvironments

advantages, CG:423

correlating messages, CG:410overview, CG:422–CG:432suppressing duplicate messages, CG:355

Japanese-language environments, AR_I:257–AR_I:258

templatesconfiguring, AR_I:117–AR_I:152examples, AR_I:144–AR_I:152follow-the-sun responsibility switch,

AR_I:146–AR_I:148keywords, AR_I:119–AR_I:124location, AR_I:117message forwarding between

management servers, AR_I:149–AR_I:150

responsibility switch, AR_I:144–AR_I:145scheduled outages, AR_I:152service hours, AR_I:151syntax, AR_I:124–AR_I:129types, AR_I:117

flow chartscommunication in competence centers,

CG:427communication links

central server configuration, CG:438manufacturing environment, CG:433

configuringevent correlation in VPO, CG:406message source templates, CG:286

DCE RPC client-server authentication process, AR_I:411

directory structureAIX, AR_II:66HP-UX, AR_II:99Linux, AR_II:133MPE/iX, AR_II:163Novell NetWare, AR_II:202Sequent DYNIX, AR_II:241SGI IRIX, AR_II:257SINIX RM/Reliant, AR_II:276Solaris, AR_II:304Tru64 UNIX, AR_II:342Windows NT/2000, AR_II:426

downloading and uploading configuration files, CG:446

filtering messages


Master Index

management server, CG:309multiple templates, CG:305VPO agent, CG:308

HP-UX configuration and related character sets

English, AR_I:250Japanese, AR_I:254

installing VPO agentsNovell NetWare, AR_II:180Windows NT/2000, AR_II:356

interceptorsMPE/ix console messages, CG:398SNMP events with NNM, CG:391

logfile encapsulator, CG:361logical event correlation, CG:404management responsibility

switching, CG:443templates for managed nodes, CG:440

management server in MC/Service Guard, AR_II:457

MC/ServiceGuard LAN switchoverafter, AR_II:453before, AR_II:452

MC/ServiceGuard redundant data and heartbeat subnets, AR_II:454

MC/ServiceGuard switchoverafter, AR_II:451before, AR_II:450

message escalation process, CG:430message flow

managed nodes, CG:408management server, CG:409

message forwardinglarge hierarchies, CG:454process, CG:453

remote actions, AR_I:425scalability scenarios

multiple management servers, CG:465multiple management servers with VPO

agents and NNM collection stations, CG:467

NNM collection stations with VPO agents, CG:463

single management server, CG:460VPO agents monitoring IP devices, CG:462

SD-UX remote software depot installation method, AR_II:79

SNMP event system in VPO, CG:392VPO

functional overview, AR_I:295message interface, CG:367

worldwide management domain, CG:424“Flush” application, AR_II:436follow-the-sun control, CG:424–CG:426“followthesun” template, AR_I:118font X resources, AR_I:236–AR_I:238formatting messages, CG:56forwarding

CMIP events, CG:392–CG:393messages, CG:425

between management servers, CG:448–CG:459

notification system, CG:451, AR_I:132OpenView Operations for Windows

management server, AR_I:204strategies, CG:456–CG:459templates, CG:452–CG:453trouble ticket system, AR_I:132

SNMP traps, CG:392–CG:393unmatched messages, AR_I:337

“forwmgrp” pipe file, AR_I:301“forwmgrq” queue file, AR_I:301FTP (re-)installation

See also installingWindows NT/2000

installing agents, AR_II:361–AR_II:366re-installing agents, AR_II:372–AR_II:375

functionality, VPO, CG:45–CG:49functions, offline backup, AR_I:439

G<$G> variable, AR_I:165generating

default messagekey relations, CG:343–CG:344keys, CG:343–CG:344

Internet reports, AR_I:110reports, CG:46

generating new NMEV marker, AR_II:155–AR_II:156

generic templates, CG:306getting error instructions


503

Master Index

opcerr, AR_I:338GlancePlus

included with OVPA, AR_II:213graphical user interface. See GUIgroup symbols, CG:216GUI

See also Java GUI; Motif GUI documentation

activating VPO agentsAIX, AR_II:49Solaris, AR_II:293

EMS, AR_II:109–AR_II:110Java

accessing, AR_I:418comparison with Motif, AR_I:268–AR_I:270overview, AR_I:265–AR_I:291

language supportfont X resources, AR_I:236–AR_I:238running English GUI in Japanese

environment, AR_I:236setting language, AR_I:234–AR_I:238

management server, troubleshooting, AR_I:345–AR_I:347

Motifaccessing, AR_I:417comparison with Java, AR_I:268–AR_I:270

operatorsaving output, CG:202starting VPO, CG:202

permissions, AR_I:417–AR_I:418SAM, AR_II:95variables, AR_I:169–AR_I:183VPO administrator

accessing, AR_I:417description, CG:202

GUI Error Dialog Box, AR_I:337–AR_I:338guidelines

escalating messages, CG:429message key, CG:337–CG:340

H“HA” message group, AR_I:72HACMP

installation requirements, AR_II:52installing VPO agents, AR_II:50–AR_II:57IP

address naming scheme, AR_II:51

aliases, AR_II:50–AR_II:54troubleshooting, AR_II:53

resetting eventsHACMP 4.2.2, AR_II:55HACMP 4.3.1, AR_II:55–AR_II:56

“HACMP logfile (AIX)” template, AR_II:60hardware

HP 3000/900, AR_II:162HP 9000/700, AR_II:97HP 9000/800, AR_II:97IBM RS/6000, AR_II:65Intel

Linux, AR_II:132NetWare, AR_II:201Sequent DYNIX, AR_II:240Windows 2000/NT, AR_II:425

Siemens Nixdorf, AR_II:275Silicon Graphics, AR_II:256Sun SPARCstation, AR_II:303

“Hardware” message groupMPE/iX, AR_II:151VPO, AR_I:72

hardware requirementsOVPA


VPOAIX, AR_II:39HP-UX, AR_II:73Linux, AR_II:117MPE/iX, AR_II:141Novell NetWare, AR_II:173Sequent DYNIX, AR_II:233SGI IRIX, AR_II:249SINIX RM/Reliant, AR_II:265Solaris, AR_II:283Tru64 UNIX, AR_II:325Windows NT/2000, AR_II:351–AR_II:352

headline, message browserfigure, CG:98

heartbeat subnets on MC/ServiceGuard, AR_II:453–AR_II:454

hidingmessage browser columns, CG:197panes and areas, CG:185–CG:187position controls, CG:182

“hier.time.spec” template, AR_I:118


Master Index

“hier.specmgr” template, AR_I:118“hier.time.all” template, AR_I:118hierarchies

domain, CG:434–CG:435managed nodes, CG:214–CG:215management server, CG:433–CG:438message forwarding, CG:454

“hierarchy” template, AR_I:118“hierarchy.agt” template, AR_I:118“hierarchy.sv” template, AR_I:118history graph

figurespopup menu, CG:146severity changes over time, CG:145

overview, CG:145history message browser

See also active message browser; filtered message browser; message browser; pending messages browser

investigating problems, CG:148–CG:149overview, CG:103

hostnamesassigning to packages, AR_II:455changing, AR_I:466–AR_I:480

managed node, AR_I:475–AR_I:480management server, AR_I:467–AR_I:469

MC/Service Guard, AR_II:455“hostview” application, AR_II:315HP 3000/900, AR_II:162HP 9000/700, AR_II:97HP 9000/800, AR_II:97HP applications, integrating into VPO,

AR_I:213HP Enterprise Servers, AR_II:98HP ITO Account

Windows NT/2000, AR_II:358HP OpenView. See OpenViewHP OpenView Performance Agent. See OVPAHP OpenView VantagePoint Operations. See

VPOHP Software Distributor. See SD-UXHP System Administrator. See SAMHP Technical Workstations, AR_II:98HP VantagePoint Network Node Manager.

See NNMHP_OV_consoleSettings file, CG:180“hp_ux” node group, AR_I:71“HP-UX 10.x” template group, AR_II:90“HP-UX 11.x” template group, AR_II:90

HP-UX managed nodesSee also HP-UX management server;

SD-UXactivating, AR_II:86–AR_II:89,

AR_II:333–AR_II:336applications

ASCII SAM, AR_II:95EMS Resources, AR_II:110–AR_II:111Motif SAM, AR_II:95

EMScommand line, AR_II:112GUI, AR_II:109–AR_II:110overview, AR_II:106–AR_II:112sending notifications to VPO, AR_II:112threshold monitoring,

AR_II:106–AR_II:108VPO Application Bank window,

AR_II:110–AR_II:111OVPA

de-installing, AR_II:221disk space requirements, AR_II:218hardware requirements, AR_II:215installation requirements,

AR_II:214–AR_II:218installing, AR_II:219–AR_II:220overview, AR_II:209–AR_II:230preconfigured elements,

AR_II:223–AR_II:226software requirements, AR_II:216template groups, AR_II:224–AR_II:226

VPOaccessing programs, AR_I:418default operator, AR_II:100de-installing agents, AR_II:89directory structure, AR_II:99file locations, AR_II:100hardware requirements, AR_II:73include file, AR_II:105installation requirements,

AR_II:73–AR_II:76installation tips, AR_II:77installing agents, AR_II:77–AR_II:85libraries, AR_II:102–AR_II:105logfile locations, AR_I:460–AR_I:461logfile templates, AR_II:91makefiles, AR_II:105


505

Master Index

manual installation, AR_II:83–AR_II:85message templates, AR_II:90monitored objects, AR_II:94organization, AR_II:99–AR_II:101overview, AR_II:71–AR_II:113preconfigured elements,

AR_II:90–AR_II:95scripts and programs, AR_II:96–AR_II:98SD-UX installation, AR_II:79–AR_II:85SNMP event interceptor,

AR_II:92–AR_II:94software requirements, AR_II:73–AR_II:76standard installation, AR_II:78system resource files, AR_II:101template groups, AR_II:90

HP-UX management serverSee also HP-UX managed nodesconfiguration and related character sets

English, AR_I:250Japanese, AR_I:254

language variable for keyboards, AR_I:236HTML format, accessing man pages,

AR_I:497

I“I” message attribute, AR_I:76I/O applications, starting remotely, AR_I:420IBM AIX. See AIX managed nodesIBM RS/6000, AR_II:65ICA Browser service, AR_II:432“ice_proxy” option, AR_I:274“ice_proxy_address” option, AR_I:274“ice_proxy_advanced” option, AR_I:274“ice_proxy_ftp” option, AR_I:274“ice_proxy_ftp_port” option, AR_I:274“ice_proxy_gopher” option, AR_I:274“ice_proxy_gopher_port” option, AR_I:274“ice_proxy_http” option, AR_I:274“ice_proxy_http_port” option, AR_I:274“ice_proxy_port” option, AR_I:274“ice_proxy_sec” option, AR_I:275“ice_proxy_sec_port” option, AR_I:275“ice_proxy_sock” option, AR_I:275“ice_proxy_sock_port” option, AR_I:275identifying users logged into Java GUI,

AR_I:291impact, message, CG:296

implementing message policies, CG:281–CG:418

importingOpenView Operations for Windows policies

into VPO, AR_I:210VPO templates into OpenView Operations

for Windows, AR_I:209improving

performancedatabase, AR_I:319Java GUI, AR_I:290–AR_I:291Motif GUI startup, AR_I:322SNMP management platform,

AR_I:318–AR_I:319UNIX with JIT, AR_I:290VPO, AR_I:320–AR_I:321

productivity, CG:283include file

See also filesAIX, AR_II:69HP-UX, AR_II:105Linux, AR_II:137MPE/iX, AR_II:168Novell NetWare, AR_II:207Sequent DYNIX, AR_II:244SGI IRIX, AR_II:260Solaris, AR_II:308Tru64 UNIX, AR_II:346Windows NT/2000, AR_II:429

incoming messages, comparing with match conditions, CG:312–CG:314

“Inetd” objectAIX, AR_II:62HP-UX, AR_II:94Linux, AR_II:129Sequent DYNIX, AR_II:238SGI IRIX, AR_II:254SINIX RM/Reliant, AR_II:273Solaris, AR_II:301Tru64 UNIX, AR_II:339

“Informational” ownership mode, CG:154, CG:274

“initial_node” option, AR_I:271, AR_I:275INSERVICE parameter, AR_I:131inspecting correlated events in NNM

database, CG:407“Install Log” application, AR_II:422


Master Index

Install/Update VPO Software and Configuration window, AR_I:51, AR_I:187

“install_dir” option, AR_I:275installation debugging

disabling, AR_I:68enabling, AR_I:68facilities, AR_I:67

installation requirementsOVPA

HP-UX, AR_II:214–AR_II:218Solaris, AR_II:214–AR_II:218

VPOAIX, AR_II:39–AR_II:40HACMP, AR_II:52HP-UX, AR_II:73–AR_II:76Linux, AR_II:117–AR_II:120MPE/iX, AR_II:141–AR_II:142Novell NetWare, AR_II:173–AR_II:175overview, AR_I:39–AR_I:41Sequent DYNIX, AR_II:233–AR_II:234SGI IRIX, AR_II:249–AR_II:250SINIX RM/Reliant, AR_II:265–AR_II:266Solaris, AR_II:283–AR_II:286Tru64 UNIX, AR_II:325–AR_II:327Windows NT/2000, AR_II:351–AR_II:354

installation script, AR_I:49installation tips

managed nodesAIX, AR_II:41–AR_II:43HP-UX, AR_II:77Linux, AR_II:122–AR_II:123MPE/iX, AR_II:143–AR_II:146Novell NetWare, AR_II:176–AR_II:179overview, AR_I:42–AR_I:45Sequent DYNIX, AR_II:235SGI IRIX, AR_II:251SINIX RM/Reliant, AR_II:267–AR_II:268Solaris, AR_II:287–AR_II:288Tru64 UNIX, AR_II:328–AR_II:329UNIX, AR_I:47–AR_I:48

management server, AR_I:46installation troubleshooting

managed nodesMPE/iX, AR_I:350–AR_I:354UNIX, AR_I:348

multi-homed hosts, AR_I:388–AR_I:396

“Installed Software (NW)” application, AR_II:195

“Installed Software” application, AR_II:397installing

See also automatic installation; de-installing; FTP (re-)installation; manual installation; removing; standard installation

Citrix MetaFrame agent, AR_II:431DCE

nodes, AR_I:406servers, AR_I:405

OVPA managed nodesHP-UX, AR_II:219–AR_II:220

VPO agents on managed nodesAIX, AR_II:45–AR_II:57automatically, AR_I:49–AR_I:56HACMP, AR_II:50–AR_II:57HP-UX, AR_II:77–AR_II:85Linux, AR_II:123–AR_II:126MPE/iX, AR_II:149Novell NetWare, AR_II:181–AR_II:186overview, AR_I:37–AR_I:68SD-UX, AR_II:79–AR_II:82Sequent DYNIX, AR_II:236SGI IRIX, AR_II:252SINIX RM/Reliant, AR_II:270Solaris, AR_II:290–AR_II:291SSH installation method, AR_I:57–AR_I:61Sun Enterprise E10000,

AR_II:318–AR_II:320Tru64 UNIX, AR_II:332Windows NT/2000, AR_II:355–AR_II:378

VPO configuration on managed nodes, AR_I:185–AR_I:192

Instant On licenses, AR_I:462instruction text interface

variables, AR_I:168Instructions

adding to your message, CG:327reading, CG:158–CG:159

integrated web browser. See web browserintegrating

applications into VPOactions, AR_I:223–AR_I:224Application Desktop, AR_I:214–AR_I:215broadcast commands, AR_I:222


507

Master Index

components, AR_I:213HP applications, AR_I:213HP OpenView plug-in, AR_I:214monitoring applications, AR_I:225NNM, AR_I:215, AR_I:216–AR_I:221overview, AR_I:211–AR_I:230VPO applications, AR_I:214

Citrix MetaFrame, AR_II:430–AR_II:434data with OVPA, AR_II:212“Ethernet Traffic HP” as OV application,

AR_I:218“IP Activity Monitoring - Tables” as OV

service, AR_I:219monitoring programs, CG:370SMS into VPO, AR_II:439–AR_II:444Sun Management Center, AR_II:321threshold monitors, CG:382–CG:385

IntelLinux, AR_II:132NetWare, AR_II:201Sequent DYNIX, AR_II:240Windows 2000/NT, AR_II:425

interceptingevents

Distributed Event Interception, AR_II:92–AR_II:93

ECS, AR_II:94messages

applications, AR_I:227description, CG:43managed nodes, CG:43MPE/iX console, CG:398–CG:399MPE/iX managed nodes,

AR_II:151–AR_II:156sources, CG:51–CG:52, CG:297–CG:298

SNMPevents, CG:390–CG:391traps, CG:390

interceptor, event, CG:407interface, message, CG:367–CG:368internal nodes


Internet reports, generating, AR_I:110interoperability

overview, AR_I:193–AR_I:210

VPO and OpenView Operations for Windows, AR_I:195–AR_I:210

interval, refresh, CG:178intervals, setting time, CG:442investigating problems

accessing OpenView applications, CG:147examining message attributes, CG:135finding impacted VP Navigator services,

CG:147message

browser, CG:134histories, CG:148–CG:149

modifying message attributes, CG:136overview, CG:132–CG:133pending messages browser, CG:150reviewing original message text, CG:137viewing

custom message attributes, CG:138–CG:139

message severity, CG:142–CG:146workspace pane, CG:141

IPaddresses

assigning to LAN interface cards, AR_II:455

assigning to packages, AR_II:455changing, AR_I:466–AR_I:480managed node, AR_I:475–AR_I:480management server, AR_I:467–AR_I:469MC/Service Guard, AR_II:455

devices, CG:462HACMP

address naming scheme, AR_II:51aliases, AR_II:50–AR_II:54troubleshooting, AR_II:53

mapaccessing with Jovw, AR_I:287–AR_I:289network management, AR_I:217submaps, CG:222

troubleshooting point-to-point and Ethernet problems, AR_I:389

“IP Activity Monitoring - Tables”, integrating as OV service, AR_I:219

“IRIX” template group, AR_II:253IRIX. See SGI IRIX managed nodesISO 8859-15

on managed nodes, AR_I:241


Master Index

on management server, AR_I:251ITO_FM_INIT 360 attribute, AR_II:470ITO_FM_START 360 attribute, AR_II:470ITO_FM_STOP 360 attribute, AR_II:470ITO_MAINTENANCE FALSE attribute,

AR_II:470ito_op startup script, AR_I:271–AR_I:272ITO_PMON_EXCLUDE opcsvcm attribute,

AR_II:470ITO_PMON_RETRIES 5 attribute, AR_II:469ITO_PMON_SLEEP 60 attribute, AR_II:469ITO_PMON_START 5 attribute, AR_II:469ITO_PMON_TAG ito_pmon attribute,

AR_II:469ITO_PMON_TPERIOD -1 attribute,

AR_II:469“ito_restore.sh” script, AR_I:449ITO_START 360 attribute, AR_II:470ITO_START_NET 720 attribute, AR_II:470ITO_STOP 360 attribute, AR_II:470ITO_STOP_NET 360 attribute, AR_II:470itop, CG:66

See also opc_op; netop

JJapanese language

character sets, AR_I:247flexible management, AR_I:257–AR_I:258HP-UX configuration and related character

sets, AR_I:254management server, AR_I:254–AR_I:256OVPA documentation, AR_II:230processing managed node files,

AR_I:255–AR_I:256Java GUI

See also GUI; Motif GUI documentationaccessing

Jovw, AR_I:287–AR_I:289NNM, AR_I:279–AR_I:281VPO, AR_I:418

accessing quick filters, CG:195adding tabs to browser pane, CG:195applications, AR_I:172browser pane, CG:95–CG:97changing

look and feel, CG:181operator passwords, CG:172refresh interval, CG:178

choosing web browser, CG:188comparison with Motif GUI,

AR_I:268–AR_I:270configuring filtered message browsers,

CG:192customizing

message browser columns, CG:196message event notification, CG:191overview, CG:171popup menus, CG:189–CG:190shortcut bar, CG:188

figure, CG:71hiding

message browser columns, CG:197panes and areas, CG:185–CG:187position controls, CG:182

identifying logged-in users, AR_I:291ito_op startup script, AR_I:271–AR_I:272itooprc file, AR_I:273–AR_I:278loading default configuration,

CG:173–CG:178menu bar, CG:108moving panes and areas, CG:183object pane, CG:75–CG:76OpenView applications, AR_I:281–AR_I:283overview, AR_I:265–AR_I:291performance tips, AR_I:290–AR_I:291popup menus, CG:111position controls, CG:110saving

console settings, CG:179–CG:180message browser filter, CG:193–CG:194message browser layout, CG:198

shortcut bar, CG:73–CG:74showing


startup options, AR_I:271–AR_I:272switching message colors to entire line,

CG:196toolbar, CG:109tour, CG:71–CG:72variables, AR_I:169–AR_I:183web browsers, CG:105–CG:107workspace pane, CG:85–CG:87


509

Master Index

“Job” message groupMPE/iX, AR_II:151VPO, AR_I:72

“Job Status” application, AR_II:398Jovw

accessing, AR_I:287–AR_I:289default IP map, AR_I:287–AR_I:289

Just-in-Time compiler. See JVM JIT compilerJVM JIT compiler, enabling, AR_I:290

K“Kernel Logs (10.x/11.x HP-UX)” logfile,

AR_II:91“Kernel Logs (AIX)” template, AR_II:60kernel parameters, AR_I:40keyboards, setting language variable on

HP-UX, AR_I:236keys, message, CG:342keywords, template

flexible management, AR_I:119–AR_I:124time, AR_I:142–AR_I:143

L“Lan Console” application, AR_II:159LAN interface cards, assigning IP addresses,

AR_II:455language support

GUIfont X resources, AR_I:236–AR_I:238running English GUI in Japanese

environment, AR_I:236setting language, AR_I:234–AR_I:238

managed nodesmanaging English nodes with Japanese

management server, AR_I:244overview, AR_I:239–AR_I:249setting character set, AR_I:241setting language, AR_I:240

management serveroverview, AR_I:233–AR_I:238setting character set, AR_I:234setting language, AR_I:233

overview, AR_I:231–AR_I:263languages

VPOother, AR_I:260–AR_I:262

libraries

AIX, AR_II:68–AR_II:70HP-UX, AR_II:102–AR_II:105Linux, AR_II:136–AR_II:137managed nodes, AR_I:484MPE/iX, AR_II:168–AR_II:169Novell NetWare, AR_II:207–AR_II:208Sequent DYNIX, AR_II:244–AR_II:245SGI IRIX, AR_II:260–AR_II:261SINIX RM/Reliant, AR_II:279–AR_II:280Solaris, AR_II:307–AR_II:309Tru64 UNIX, AR_II:345–AR_II:347Windows NT/2000, AR_II:429

“License” application, AR_II:436licenses

command-line tool, AR_I:464–AR_I:465Instant On, AR_I:462maintaining, AR_I:462–AR_I:465types, AR_I:462–AR_I:463

linking messages logically, CG:52“Linux (RedHat)” template group, AR_II:128Linux managed nodes

default operator, AR_II:134–AR_II:135de-installing agents, AR_II:127directory structure, AR_II:133file locations, AR_II:134hardware requirements, AR_II:117include file, AR_II:137installation

requirements, AR_II:117–AR_II:120tips, AR_II:122–AR_II:123

installing agents, AR_II:123–AR_II:126libraries, AR_II:136–AR_II:137logfile templates, AR_II:128makefile, AR_II:137monitored objects, AR_II:129organization, AR_II:133–AR_II:135overview, AR_II:115–AR_II:137preconfigured elements,

AR_II:128–AR_II:129removing agents, AR_II:127scripts and programs, AR_II:130–AR_II:132SNMP event interceptor (not supported),

AR_II:129software requirements,

AR_II:118–AR_II:120template groups, AR_II:128

“List Processes” application, AR_II:223


Master Index

“List Versions” application, AR_II:223lists, message distribution, CG:453–CG:456“LM Sessions” application, AR_II:399“Load/Unload an arbitrary NLM”

application, AR_II:196loading default configuration,

CG:173–CG:178Local Location Broker

troubleshooting, AR_I:381“Local Users” application, AR_II:400LOCAL_ON_JAVA_CLIENT variable,

AR_I:168LOCAL_ON_JAVA_CLIENT_WEB variable,

AR_I:168“locale” option, AR_I:271, AR_I:275localizing object names, AR_I:263locating

See also locationmessages, CG:295

locationSee also locatingconfiguration data, AR_I:435error messages, AR_I:335files

AIX, AR_II:66HP-UX, AR_II:100Linux, AR_II:134managed node logfiles, AR_I:460–AR_I:461managed node processes, AR_I:309MPE/iX, AR_II:163Novell NetWare, AR_II:202“opcinfo” on managed nodes, AR_I:325Sequent DYNIX, AR_II:241SGI IRIX, AR_II:257SINIX RM/Reliant, AR_II:276Solaris, AR_II:304tracing, AR_I:332Tru64 UNIX, AR_II:342VPO agent configuration, AR_I:311Windows NT/2000, AR_II:427

scripts and programsAIX, AR_II:64HP-UX, AR_II:96Linux, AR_II:131MPE/iX, AR_II:161Novell NetWare, AR_II:200Sequent DYNIX, AR_II:239SGI IRIX, AR_II:255

SINIX RM/Reliant, AR_II:274Solaris, AR_II:302Tru64 UNIX, AR_II:340Windows NT/2000, AR_II:424

templatesflexible management, AR_I:117message forwarding, AR_I:136scheduled outage, AR_I:130scheduled outages, AR_I:130service hours, AR_I:130

<$LOGFILE> variable, AR_I:160logfile

See also filesapplication, monitoring, AR_I:226encapsulator

changing character set, AR_I:244character sets supported,

AR_I:248–AR_I:249description, CG:361flow chart, CG:361

error messages, AR_I:335locations on managed nodes,

AR_I:460–AR_I:461MC/ServiceGuard, AR_II:459messages, CG:361–CG:366SSP directory, exporting, AR_II:317templates

AIX, AR_II:59–AR_II:60Citrix MetaFrame, AR_II:434defining, CG:364description, CG:362HP-UX (VPO), AR_II:91Linux, AR_II:128MPE/iX, AR_II:150Novell NetWare, AR_II:187Sequent DYNIX, AR_II:237SGI IRIX, AR_II:253SINIX RM/Reliant, AR_II:272Solaris (VPO), AR_II:297Sun Enterprise E10000, AR_II:313Tru64 UNIX, AR_II:337–AR_II:338variables, AR_I:160Windows NT/2000, AR_II:381–AR_II:382

logging data with OVPA, AR_II:212logging messages, CG:43, CG:356–CG:357logical host, Sun Cluster, AR_II:464login


511

Master Index

DCE, AR_I:421RPC, AR_I:410

“Logins (10.x/11.x HP-UX)” logfile, AR_II:91“Logins (AIX)” template, AR_II:60“Logins (IRIX)” template, AR_II:253“Logins (Linux)” template, AR_II:128“Logins (SINIX)” template, AR_II:272“Logins (Solaris)” template, AR_II:297Logon Report, AR_I:111LOGONLY parameter, AR_I:131<$LOGPATH> variable, AR_I:160“Logs (DYNIX/ptx)” template, AR_II:237“Logs” (Tru64 UNIX) template, AR_II:337logs, redo, AR_I:455“Lp Req (DYNIX/ptx)” template, AR_II:237“Lp Serv (DYNIX/ptx)” template, AR_II:237“Lplog” (Tru64 UNIX) template, AR_II:337

M“magmgrp” pipe file, AR_I:302“magmgrq” queue file, AR_I:302“Mailqueue (10.x/11.x HP-UX)” logfile,

AR_II:91“MailQueue Length” object

AIX, AR_II:62HP-UX, AR_II:94Linux, AR_II:129Sequent DYNIX, AR_II:238SGI IRIX, AR_II:254Solaris, AR_II:301Tru64 UNIX, AR_II:339

maintainingdatabase, AR_I:452directories, AR_I:457files, AR_I:457licenses, AR_I:462–AR_I:465managed nodes, AR_I:458–AR_I:461OpenView, AR_I:456VPO, CG:199–CG:280, AR_I:433–AR_I:480

“Major” message severity level, AR_I:74makefile

See also filesAIX, AR_II:70HP-UX, AR_II:105Linux, AR_II:137MPE/iX, AR_II:169Novell NetWare, AR_II:208Sequent DYNIX, AR_II:245

SGI IRIX, AR_II:261SINIX RM/Reliant, AR_II:280Solaris, AR_II:309Tru64 UNIX, AR_II:347Windows NT/2000, AR_II:429

man pagesaccessing

command line, AR_I:497HTML format, AR_I:497

APIsVPO, AR_I:501

printing, AR_I:497VantagePoint Navigator, AR_I:502VPO, AR_I:495–AR_I:502

managed nodesSee also Managed Nodes window;

management serveraccessing MIB, AR_I:386–AR_I:387adding to VPO

description, CG:210from IP submaps, CG:222from VPO Add Node window,

CG:224–CG:227in Node Bank window, AR_I:50overview, CG:217–CG:229with templates, CG:292

APIs, AR_I:483building, CG:208character sets

changing, AR_I:243EUC, AR_I:255external, AR_I:244–AR_I:247ROMAN8, AR_I:252Shift JIS, AR_I:258

communication types, AR_I:54–AR_I:56configuring

authenticated RPCs, AR_I:407DCE cell, AR_I:407description, CG:44hierarchies, CG:435regional management servers,

CG:437–CG:438copying and pasting, CG:223correlating messages, CG:405, CG:408debugging software (de-)installation,

AR_I:67–AR_I:68


Master Index

defaults, CG:228de-installing VPO agents

automatically, AR_I:62–AR_I:63manually, AR_I:63

description, CG:43–CG:44directories with runtime data, AR_I:459disabled, CG:229distributing

scripts and programs, AR_I:188–AR_I:192VPO agent configuration, AR_I:187

dragging and dropping, CG:224external


filespipe, AR_I:307–AR_I:308process, AR_I:307–AR_I:308queue, AR_I:307–AR_I:308

filtering messages, CG:332group symbols, CG:216hostnames and IP addresses,

AR_I:475–AR_I:480installing

VPO agents, AR_I:37–AR_I:68VPO configuration, AR_I:185–AR_I:192

internaladding, CG:217characteristics, CG:218

kernel parameters, AR_I:40language support, AR_I:239–AR_I:249libraries, AR_I:484logfile locations

AIX, AR_I:460HP-UX, AR_I:461HP-UX 10.x/11.x, AR_I:460MPE/iX, AR_I:460Solaris, AR_I:461VPO, AR_I:460–AR_I:461Windows NT, AR_I:460

maintaining, AR_I:458–AR_I:461managing VPO agents, AR_I:64–AR_I:66message-allowed, CG:209multiple parent groups, CG:216“opcinfo” file, AR_I:325operating systems

AIX, AR_II:37–AR_II:70

HP-UX, AR_II:71–AR_II:113Linux, AR_II:115–AR_II:137MPE/iX, AR_II:139–AR_II:169Novell NetWare, AR_II:171–AR_II:208Sequent DYNIX, AR_II:231–AR_II:245SGI IRIX, AR_II:247–AR_II:261SINIX RM/Reliant, AR_II:263–AR_II:280Solaris, AR_II:281–AR_II:322Tru64 UNIX, AR_II:323–AR_II:347Windows NT/2000, AR_II:349–AR_II:444

organizing, CG:208–CG:231passwords

assigning, AR_I:422–AR_I:423DCE, AR_I:420–AR_I:421MPE/iX, AR_I:422Novell NetWare, AR_I:423UNIX, AR_I:422Windows NT, AR_I:423

process files, AR_I:306–AR_I:309processes, AR_I:304–AR_I:311processing files

English, AR_I:252–AR_I:253Japanese, AR_I:255–AR_I:256

redistributing scripts, AR_I:438returning names with pattern matching,

AR_I:285security, CG:229starting

applications, AR_I:229–AR_I:230broadcast commands, AR_I:229–AR_I:230

templates for responsible managers, CG:440troubleshooting

all managed nodes, AR_I:355–AR_I:369embedded performance component,

AR_I:382–AR_I:385mixed-case node names, AR_I:349MPE/iX, AR_I:350–AR_I:354,

AR_I:374–AR_I:380UNIX, AR_I:348, AR_I:370–AR_I:373

types, CG:209updating

VPO agents, AR_I:49–AR_I:56VPO configuration, AR_I:185–AR_I:192

VPO agents on Sun Clusters, AR_II:468windows, CG:209

Managed Nodes window


513

Master Index

description, CG:66management hierarchies

See also management serveroverview, CG:433–CG:438profiles, CG:433responsibilities, CG:434–CG:435setup ratio, CG:434

management profiles, CG:433See also management server

management responsibilitySee also management serverdomain hierarchies, CG:434–CG:435message forwarding between management

servers, AR_I:149–AR_I:150switch, AR_I:144–AR_I:145

follow-the-sun, AR_I:146–AR_I:148template syntax, AR_I:126

management serverSee also managed nodes; management

hierarchies; management profiles; management responsibility; managers

action-allowedconfiguring, CG:435specifying, CG:445

backing up data, AR_I:438–AR_I:451central

configuring, CG:438description, CG:435

changing hostnames or IP addresses, AR_I:467–AR_I:469

competence centers, CG:426–CG:427configuring

English language, AR_I:250–AR_I:253Japanese language, AR_I:254–AR_I:256OpenView Operations for Windows agents

for VPO, AR_I:200–AR_I:202OpenView Operations for Windows to

forward messages to VPO, AR_I:203–AR_I:208

VPO agents for OpenView Operations for Windows, AR_I:196–AR_I:199

connecting to trouble ticket systems, CG:456converting to EUC, AR_I:257correlating messages, CG:405, CG:409default setup, CG:422description, CG:42distributing configuration, CG:446–CG:447

duplicate messagesenabling suppression, CG:354–CG:355suppressing, CG:353

escalating messages, CG:428–CG:431files

pipe, AR_I:301–AR_I:303process, AR_I:301–AR_I:303queue, AR_I:301–AR_I:303

filtering messages, CG:332flexible architecture, CG:423follow-the-sun control, CG:424–CG:426forwarding messages

between management servers, CG:448–CG:459

OpenView Operations for Windows, AR_I:204

hierarchies, CG:433–CG:438installation tips, AR_I:46language support

overview, AR_I:233–AR_I:238setting character set, AR_I:234setting language, AR_I:233

MC/Service Guard, AR_II:447multiple, CG:419–CG:467primary, CG:422processes, AR_I:297–AR_I:303processing files

ISO 8859-15, AR_I:251Shift JIS, AR_I:254

processing messages, CG:309reconfiguring after changing hostname or

IP address, AR_I:470–AR_I:474regional

configuring, CG:437–CG:438description, CG:434

responsibilityconfiguring, CG:439–CG:447switching, CG:443–CG:445

running on MC/ServiceGuard, AR_II:457secondary, CG:436sending messages


VPO, AR_I:200single, CG:460troubleshooting


Master Index

GUI, AR_I:345–AR_I:347server, AR_I:343–AR_I:344

management, flexible, CG:422–CG:432manager, distribution, AR_I:189managers

See also management serveraction-allowed

adding, CG:445central server, CG:435

backup, CG:445primary

changing, CG:443–CG:445initial, CG:422

responsibility, CG:439–CG:447secondary, CG:436

managingdisabled nodes, CG:229message source templates, CG:285–CG:294messages, CG:55Sun Enterprise E10000,

AR_II:310–AR_II:311VPO agents, AR_I:64–AR_I:66

manual de-installationSee also de-installingOVPA


VPOAIX, AR_II:58HP-UX, AR_II:89Linux, AR_II:127SINIX RM/Reliant, AR_II:271Solaris, AR_II:294Tru64 UNIX, AR_II:336Windows NT/2000, AR_II:379

manual installationSee also installingOVPA


VPOAIX, AR_II:46–AR_II:49HP-UX, AR_II:83–AR_II:85Linux, AR_II:124–AR_II:126SINIX RM/Reliant, AR_II:270Solaris, AR_II:290Windows NT/2000, AR_II:376–AR_II:378

manufacturing environmentcommunication links, CG:433management profiles, CG:433

mappingARPA hostnames to NS node names

overview, AR_II:164–AR_II:167problems, AR_II:166resolving names, AR_II:167vt3k operation, AR_II:165

MPE/iX messages to VPO security levels, AR_II:152

NMEV markers, AR_II:152–AR_II:155marking messages, CG:272match conditions, comparing with incoming

messages, CG:312–CG:314mathematical operators in

pattern-matching, CG:315–CG:316“max_limited_messages” option, AR_I:272,

AR_I:275maximum threshold, CG:377MC/Service Guard

description, AR_II:447–AR_II:449enabling maintenance mode, AR_II:459examples, AR_II:450–AR_II:454

redundant data and heartbeat subnets, AR_II:453–AR_II:454

switching local networks, AR_II:452–AR_II:453

switching packages, AR_II:450–AR_II:451glossary, AR_II:448IP addresses and hostnames, AR_II:455logfiles, AR_II:459overview, AR_II:445–AR_II:459running

management server, AR_II:457NNM, AR_II:456VPO, AR_II:456–AR_II:458

transferring applications to other management servers, AR_II:447

troubleshooting, AR_II:459MC/ServiceGuard

adoptive node, AR_II:448original node, AR_II:448package

custody, AR_II:448description, AR_II:448IP/hostname, AR_II:448


515

Master Index

service, AR_II:449support, AR_II:113

MC/ServiceGuard Daemon, AR_II:448“Memory Load” application, AR_II:401“Memory Use” application, AR_II:196menu bar


messagedefaults

message correlation options, CG:302output options for a message stream

interface, CG:302pattern-matching options, CG:302

message-allowed managed nodes, CG:209Message and Suppress Conditions window,

CG:314message attributes

setting defaults, CG:301message browser

See also active message browser; filtered message browser; history message browser; pending messages browser

accessing quick filters, CG:195browsing effectively, CG:123–CG:128configuring filters

active, CG:101–CG:102history, CG:103overview, CG:192pending, CG:104

consolidating messages, CG:284customizing columns

message attributes, CG:126physical layout, CG:196

figuresbrowser pane, CG:96custom message attributes, CG:139workspace pane, CG:97

hiding columns, CG:197investigating problems, CG:134Java and Motif GUIs, AR_I:268operator, CG:203overview, CG:98reporting errors, AR_I:336reusing filters, CG:193–CG:194saving

customized layout, CG:198

filter to object pane, CG:195showing columns, CG:197switching colors to entire line, CG:196viewing

custom message attributes, CG:139messages, CG:122

VPO administrator, CG:203–CG:204Message Browser window

description, CG:67message attributes and values, AR_I:73overview, AR_I:73–AR_I:77

Message Condition Advanced Options window, CG:394

message conditionsSee also messagesdefining advanced options, CG:384setting up, CG:310–CG:311

message correlation optionssetting defaults, CG:302

Message Correlation window, CG:337Message Dashboard workspace

current state chart, CG:143history chart, CG:145overview, CG:88viewing message severity, CG:142–CG:146

message event notificationcustomizing, CG:191overview, CG:122

message event warning, CG:122Message Group Bank window, AR_I:72message groups

See also Message Groups window; messagesadding, AR_I:73adding new, CG:233default, AR_I:71–AR_I:77defining, CG:56deleting, AR_I:73displaying, AR_I:72modifying, AR_I:73organizing, CG:232–CG:233reviewing, CG:233

Message Groups foldercolors, CG:79figure, CG:79organizing, CG:80overview, CG:79–CG:80

Message Groups window, CG:66


Master Index

See also message groupsmessage keys, CG:336

See also messagesdefault, CG:343–CG:344guidelines, CG:337–CG:340relations, CG:343–CG:344

message operations template syntax, AR_I:127

Message Properties dialog boxfigures

Annotations tab, CG:167Custom Attributes tab, CG:140General tab, CG:100Instructions tab, CG:158Original Message tab, CG:137

message settingsassigning, CG:324

message source templatesSee also Message Source Templates

window; message sources; messagesconfiguring, CG:286creating, CG:287distributing, CG:293–CG:294elements, CG:285managing, CG:285–CG:294variables, AR_I:154–AR_I:167

Message Source Templates windowSee also message source templatesdescription, CG:287figure, CG:294Templates Groups list box, CG:288

message sourcesSee also message source templates;

messagesevaluating, CG:295–CG:296filtering, CG:307–CG:308

message stream interface output optionssetting defaults, CG:302

Message Stream Interface. See MSImessage target rules template syntax,

AR_I:127“message_notification_dlg” option, AR_I:275“message_notification_dlg_app” option,

AR_I:275“message_notification_dlg_app_path” option,

AR_I:275“message_notification_show_all” option,

AR_I:276

messagesSee also acknowledgements;

acknowledging; escalating messages; message browser; message conditions; message groups; message keys; message source templates; message sources

acknowledgingautomatically, CG:157overview, CG:169–CG:170with message keys, CG:342

annotating, CG:166–CG:168annotating acknowledged, CG:343API, CG:367–CG:368attributes, AR_I:75–AR_I:77

resolving, CG:300time, CG:425

browsing effectively, CG:123–CG:128buffering, CG:43, CG:415

parameters, AR_I:131catalogue, CG:296classifying unmatched, CG:55closing, CG:165collecting, CG:297–CG:298colors

overview, CG:99switching, CG:196

comparing, CG:43conditions, specifying, CG:366consolidating in browser, CG:284control-switched, CG:449correcting, CG:369correlating, CG:336

different sources, CG:405flexible management environments,

CG:410managed nodes, CG:408management server, CG:409types, CG:336with events, CG:334

customizing columns, CG:126defaults, CG:301–CG:302, CG:303

custom message attributes, CG:301message attributes, CG:301

details, CG:135escalated message, CG:428


517

Master Index

distribution lists, CG:453–CG:456duplicate

SNMP devices, CG:393error, AR_I:335escalating, CG:164, CG:428–CG:431evaluating

impact, CG:296severity, CG:296

examining attributes, CG:135filtering, CG:55

managed node, CG:332management server, CG:332sources, CG:307–CG:308strategies, CG:332–CG:355through multiple templates, CG:305with conditions, CG:307–CG:331

formatting, CG:56forwarding, CG:425

between management servers, CG:448–CG:459, AR_I:149–AR_I:150

notification system, AR_I:132OpenView Operations for Windows

management server, AR_I:204strategies, CG:456–CG:459template, AR_I:136–AR_I:138trouble ticket system, AR_I:132unmatched messages, AR_I:337

generatingcontinuous, CG:381policy, CG:378–CG:381with reset, CG:379without reset, CG:380

groups, CG:56incoming, CG:312–CG:314intercepting

application messages, AR_I:227description, CG:43MPE/iX managed nodes,

AR_II:151–AR_II:156sources, CG:51–CG:52, CG:297–CG:298

interface, CG:367–CG:368investigating

message histories, CG:148–CG:149pending messages, CG:150

keys, CG:336linking logically, CG:52

locating, CG:295logfile, CG:361–CG:366logging

description, CG:43results, CG:356–CG:357

managing, CG:55, CG:283–CG:284marking, CG:272modifying attributes, CG:136MPE/iX console

overview, CG:398–CG:401variables, AR_I:162

notification, CG:451–CG:452overview, CG:51–CG:56, CG:100owning, CG:153–CG:154, CG:272,

CG:272–CG:274pattern-matching, CG:315–CG:323policies, CG:123–CG:128, CG:281–CG:418processing

description, CG:52–CG:54on management server, CG:309overview, CG:299–CG:306

quantity, reducing, CG:334–CG:355regrouping, CG:290, CG:358–CG:360reset, sending automatically,

CG:344–CG:346responding, CG:56reviewing

details, CG:100original text, CG:137

scanning, CG:124scheduled action variables, AR_I:167sending to management server


VPO, AR_I:200severity

coloring, CG:129–CG:131viewing in Message Dashboard,

CG:142–CG:146severity levels, AR_I:74–AR_I:75status, CG:297suppressing

duplicate, CG:347multiple, CG:306

switching control, CG:449–CG:450target rules, CG:441


Master Index

template conditions, CG:52templates, CG:365threshold monitors, CG:369–CG:389unbuffering, CG:104

automatically, CG:415manually, CG:415–CG:416

viewingin message browser, CG:122

metrics See performance metrics“MF_ICA_Browser” object, AR_II:433“MF_Prog_Neighbourhood” object, AR_II:433MIB

managed node, AR_I:386–AR_I:387object monitors, CG:371

Microsoft. See Windows NT/2000 managed nodes

“midaemon” monitor template, AR_II:225minimum threshold, CG:377“Minor” message severity level, AR_I:74“Mirrored Devices” application, AR_II:196mirrored online redo logs, AR_I:455“Misc” message group

MPE/iX, AR_II:151VPO, AR_I:72

missing OS patches for Solaris, AR_II:289mixed clusters, AR_I:192“moa*” temporary file, AR_I:308modes

archive logdatabase, AR_I:438, AR_I:442enabling, AR_I:443–AR_I:444

auditing, AR_I:428MC/ServiceGuard maintenance, AR_II:459ownership, CG:153, CG:273–CG:274ownership display, CG:154, CG:272–CG:273

Modify Message Attributes dialog boxfigure, CG:136

Modify VPO Interface Messages window, CG:368

modifyingconditions, CG:315logfile templates on Tru64 UNIX, AR_II:338message groups, AR_I:73node groups, AR_I:71

“monagtq” queue file, AR_I:307monitor agent, CG:371–CG:376

See also monitoring“Monitor Console” application, AR_II:159

monitored objectsSee also monitoringAIX, AR_II:62Citrix MetaFrame, AR_II:433HP-UX (VPO), AR_II:94Linux, AR_II:129MPE/iX, AR_II:157Novell NetWare (none), AR_II:188Sequent DYNIX, AR_II:238SGI IRIX, AR_II:254SINIX RM/Reliant, AR_II:273Solaris (VPO), AR_II:301Sun Enterprise E10000, AR_II:314Tru64 UNIX, AR_II:339Windows NT/2000, AR_II:388

monitoringSee also monitor agent; monitored objectsapplication

integration, AR_I:225logfiles, AR_I:226

environment, CG:120managed nodes, CG:209objects

external, CG:373MIB, CG:372program, CG:372

performance metrics, CG:374performance with NMA, AR_II:191programs, CG:370SMS, AR_II:442Sun Enterprise E10000,

AR_II:310–AR_II:311variables, CG:377

Motif GUIaccessing, AR_I:417comparison with Java GUI,

AR_I:268–AR_I:270improving performance, AR_I:322variables, AR_I:169–AR_I:183

Motif GUI documentationSee alsoGUI; Java GUI

Motif SAM, AR_II:95moving

panes and areas, CG:183MPE/iX console

See also MPE/iX managed nodesaccessing programs, AR_I:418


519

Master Index

messagesadvanced options, CG:400condition examples, CG:400–CG:401intercepting, CG:398–CG:399interceptor, CG:398overview, CG:398–CG:401templates, CG:399–CG:400variables, AR_I:162

“MPE/iX Database monitoring” template group, AR_II:150

MPE/iX managed nodesSee also MPE/iX consoleagent jobs, AR_II:145applications, AR_II:158–AR_II:160DCE daemon, AR_II:143default operator, AR_II:144, AR_II:163de-installing agents, AR_II:149directory structure, AR_II:163domain name resolution, AR_II:145executable libraries, AR_II:145file locations, AR_II:163filename tips, AR_II:157hardware requirements, AR_II:141include file, AR_II:168installation

requirements, AR_II:141–AR_II:142tips, AR_II:143–AR_II:146

installing agents, AR_II:149intercepting messages

default message mapping, AR_II:151generating new NMEV marker,

AR_II:155–AR_II:156mapping messages to VPO security levels,

AR_II:152mapping NMEV markers,

AR_II:152–AR_II:155overview, AR_II:151–AR_II:156

IP addresses, AR_II:144languages, AR_II:144libraries, AR_II:168–AR_II:169logfile

locations, AR_I:460templates, AR_II:150

logging group, AR_II:145login and logout UDCs, AR_II:144makefile, AR_II:169

mapping ARPA hostnames to NS node names

overview, AR_II:164–AR_II:167problems, AR_II:166resolving names, AR_II:167vt3k operation, AR_II:165

monitored objects, AR_II:157NCS daemon, AR_II:143organization, AR_II:163–AR_II:167overview, AR_II:139–AR_II:169passwords, AR_I:422preconfigured elements,

AR_II:150–AR_II:160scripts and programs, AR_II:161–AR_II:162SNMP event interceptor (not supported),


AR_II:141–AR_II:142spool files, AR_II:146streamed jobs

customizing job stream facility, AR_II:148excluding networking commands,

AR_II:147overview, AR_II:147–AR_II:149preparing VPO, AR_II:149starting, AR_II:147SYSSTART.PUB.SYS parameters,

AR_II:147system resource file, AR_II:164template groups, AR_II:150time zones, AR_II:146troubleshooting

installation, AR_I:350–AR_I:354runtime, AR_I:374–AR_I:380

“MPE/iX Network monitoring” template group, AR_II:150

“MPE/iX OS monitoring” template group, AR_II:150

“MPE/iX” template group, AR_II:150“mpicdmp” pipe file, AR_I:302“mpicdmq” queue file, AR_I:302“mpicmap” pipe file, AR_I:307“mpicmaq” queue file, AR_I:307“mpicmmp” pipe file, AR_I:302“mpicmmq” queue file, AR_I:302“mpimap” pipe file, AR_I:307“mpimaq” queue file, AR_I:307


Master Index

“mpimmp” pipe file, AR_I:302<$MSG_APPL> variable, AR_I:154<$MSG_GEN_NODE> variable, AR_I:155<$MSG_GEN_NODE_NAME> variable,

AR_I:155<$MSG_GRP> variable, AR_I:155<$MSG_ID> variable, AR_I:155<$MSG_NODE> variable, AR_I:155<$MSG_NODE_ID> variable, AR_I:156<$MSG_NODE_NAME> variable, AR_I:156<$MSG_OBJECT> variable, AR_I:156<$MSG_SEV> variable, AR_I:156<$MSG_TEXT> variable, AR_I:157<$MSG_TIME_CREATED> variable,

AR_I:157<$MSG_TYPE> variable, AR_I:157“msgagtdf” file, AR_I:308“msgagtp” pipe file, AR_I:308“msgagtq” queue file, AR_I:308“msgforw” template, AR_I:118“MsgGroup” message attribute, AR_I:77“msgip” pipe file, AR_I:308“msgiq” queue file, AR_I:308“oareqhdl” file, AR_I:302“msgmgrp” pipe file, AR_I:302“msgmgrq” queue file, AR_I:302“msgmni” parameter, AR_I:40MSGTARGETMANAGERS keyword,

AR_I:120MSGTARGETRULECONDS keyword,

AR_I:122MSGTARGETRULES keyword, AR_I:120MSI API, AR_I:228multi-homed hosts, troubleshooting,

AR_I:388–AR_I:396multiple

disks for configuring database, AR_I:453–AR_I:455

management servers, CG:419–CG:467messages, suppressing, CG:306operators, CG:61parent groups, CG:216templates

configuring, CG:303processing simultaneously,

CG:304–CG:305

N“N” message attribute, AR_I:76<$N> variable, AR_I:165<$NAME> variable, AR_I:161navigating template group hierarchies,

CG:289“NCP Info” application, AR_II:196NCS

AIX managed nodes, AR_II:40changing, AR_I:54–AR_I:56description, AR_I:41

Net8, restricting access, AR_I:116“NetBios Sessions” application, AR_II:402“netcontool” application, AR_II:315netop, CG:66

See also opc_adm; opc_op; operators“NetWare Agent Actions” application,

AR_II:197NetWare Config window, AR_II:191“NetWare” message group, AR_I:72NetWare Performance window, AR_II:192“NetWare” template group, AR_II:187NetWare Tools

applications, AR_II:194–AR_II:197window, AR_II:193

NetWare. See Novell NetWare managed nodes

Network Computing System. See NCS“Network Interfaces” application, AR_II:197“Network” message group


Network Node Manager. See NNMnetwork security

DCE, AR_I:404–AR_I:409overview, AR_I:404–AR_I:414RPC authentication, AR_I:410–AR_I:411SSH, AR_I:414

networking commands, excluding from streamed jobs on MPE/iX managed nodes, AR_II:147

“nfile” parameter, AR_I:40“nflocks” parameter, AR_I:40NFS troubleshooting, AR_I:397“NLM Files*” application, AR_II:198NMA

2.1 agent, AR_II:190applications, AR_II:197–AR_II:199description, AR_II:189


521

Master Index

monitoring performance, AR_II:191NMEV markers

generating new, AR_II:155–AR_II:156mapping, AR_II:152–AR_II:155

<$NMEV_APPL> variable, AR_I:162<$NMEV_CLASS> variable, AR_I:162<$NMEV_SEV> variable, AR_I:162NNM

accessing from Java GUIlocally, AR_I:279–AR_I:280remotely, AR_I:280–AR_I:281

collection stations with VPO agents, CG:463on multiple management servers, CG:467

configuring access with command-line tools, AR_I:283

event correlation, CG:407integrating applications into VPO,

AR_I:216–AR_I:221limitations, AR_I:216

integrating into VPO, AR_I:215running on MC/ServiceGuard, AR_II:456SNMP event interceptor, CG:391

“No Status Propagation” display mode, CG:154

No Status Propagation display mode, CG:273Node Advanced Options window, CG:226Node Communication Options window,

CG:227Node Config Report, AR_I:111Node Group Bank window, AR_I:71Node Group Report, AR_I:111node groups

adding, AR_I:71default, AR_I:71deleting, AR_I:71management server, AR_I:71modifying, AR_I:71

Node Groups Overview Report, AR_I:111node hierarchies, CG:214–CG:215node mapping tool, AR_I:285–AR_I:286“Node” message attribute, AR_I:77Node Reference Report, AR_I:111Node Report, AR_I:112node. See adoptive node; cluster nodes;

managed nodes, upgrading; original nodeNodes folder

colors, CG:78figure, CG:77

groups, CG:77layout groups, CG:77overview, CG:77–CG:78

Nodes Overview Report, AR_I:112nodes. See managed nodes; node groups: node

hierarchiesnon-sequential conditions, CG:315“Normal” message severity level, AR_I:74“nosec” option, AR_I:272, AR_I:276notification, CG:451notification system

forwarding messages, AR_I:132messages, CG:451–CG:452

notification, message event, CG:122Novell NetWare managed nodes

APIs, AR_II:205–AR_II:206applications

NetWare Tools, AR_II:194–AR_II:197NMA, AR_II:197–AR_II:199overview, AR_II:189–AR_II:199

assigning passwords, AR_I:423default operator, AR_II:203directory structure, AR_II:202file locations, AR_II:202hardware requirements, AR_II:173include file, AR_II:207installation

process, AR_II:179–AR_II:180requirements, AR_II:173–AR_II:175tips, AR_II:176–AR_II:179

installing agents, AR_II:181–AR_II:186libraries, AR_II:207–AR_II:208logfile templates, AR_II:187makefile, AR_II:208monitored objects (none), AR_II:188NMA

2.1 agent, AR_II:190applications, AR_II:197–AR_II:199description, AR_II:189monitoring performance, AR_II:191

organization, AR_II:202–AR_II:204overview, AR_II:171–AR_II:208preconfigured elements,

AR_II:187–AR_II:199removing agents, AR_II:186scripts and programs, AR_II:200–AR_II:201SNMP event interceptor, AR_II:188


Master Index

software requirements, AR_II:173–AR_II:175

system resource files, AR_II:203template groups, AR_II:187windows

NetWare Config, AR_II:191NetWare Performance, AR_II:192NetWare Tools, AR_II:193

NS node name mapping, AR_II:164–AR_II:167NT. See Windows NT/2000 managed nodesNT_DWN_SMS_CLIENT_CONFIG_MANA

GER monitor, AR_II:442NT_DWN_SMS_EXECUTIVE monitor,

AR_II:442NT_DWN_SMS_HIERARCHY_MANAGER

monitor, AR_II:442NT_DWN_SMS_INVENTORY_AGENT

monitor, AR_II:442NT_DWN_SMS_PACKAGE_COMMAND_M

ANAGER monitor, AR_II:442NT_DWN_SMS_SITE_CONFIG_MANAGE

R monitor, AR_II:442NT_DWN_SMS_TRAP_FILTER monitor,

AR_II:442NT_UP_SMS_CLIENT_CONFIG_MANAGE

R monitor, AR_II:442NT_UP_SMS_EXECUTIVE monitor,

AR_II:442NT_UP_SMS_HIERARCHY_MANAGER

monitor, AR_II:442NT_UP_SMS_INVENTORY_AGENT

monitor, AR_II:442NT_UP_SMS_PACKAGE_COMMAND_MA

NAGER monitor, AR_II:442NT_UP_SMS_SITE_CONFIG_MANAGER

monitor, AR_II:442NT_UP_SMS_TRAP_FILTER monitor,

AR_II:442

O“O” message attribute, AR_I:76<$O> variable, AR_I:165<$o> variable, AR_I:165“Object” message attribute, AR_I:77object names, localizing, AR_I:263object pane

figuresenabling, CG:185main window, CG:75

popup menu, CG:113folders

Applications, CG:81Filter Settings, CG:82–CG:83Message Groups, CG:79–CG:80Nodes, CG:77–CG:78URL Shortcuts, CG:84

moving, CG:183overview, CG:75–CG:76popup menus, CG:113saving message browser to, CG:195showing, CG:185

object status, reviewing, CG:155object tree, searching

overview, CG:121objects. See monitoring“ODI Info” application, AR_II:198offline backups, AR_I:439olh_About_Server_Config, AR_II:410olh_About_Server_Stats, AR_II:411olh_About_Shares, AR_II:412online documentation

figure, CG:91Online Help workspace, CG:91“OpC” message group, AR_I:72“opc” process, AR_I:297OPC_ACCEPT_CTRL_SWTCH_ACKN

parameter, AR_I:138OPC_ACCEPT_CTRL_SWTCH_MSGS

parameter, AR_I:138OPC_ACCEPT_NOTIF_MSSGS parameter,

AR_I:138opc_adm, CG:62–CG:63

See also netop; opc_op; operatorsOPC_AUTO_DEBUFFER parameter,

AR_I:131.opc_brc_history file, CG:164$OPC_BRC_HISTSIZE variable, CG:164$OPC_CUSTOM(name) variable, AR_I:172$OPC_ENV(env variable) variable, AR_I:158,

AR_I:169$OPC_EXACT_SELECTED_NODE_LABEL

S variable, AR_I:172$OPC_EXT_NODES variable, AR_I:169OPC_FORW_CTRL_SWTCH_TO_TT

parameter, AR_I:138OPC_FORW_NOTIF_TO_TT parameter,

AR_I:138


523

Master Index

“opc_get_ems_resource” monitor executable, AR_II:106

<$OPC_GUI_CLIENT> variable, AR_I:158$OPC_GUI_CLIENT variable, AR_I:172$OPC_GUI_CLIENT_WEB variable,

AR_I:172<$OPC_MGMTSV> variable, AR_I:157,

AR_I:159$OPC_MGMTSV variable, AR_I:169$OPC_MSG.ACTIONS.AUTOMATIC

variable, AR_I:173$OPC_MSG.ACTIONS.AUTOMATIC.ACKN

OWLEDGE variable, AR_I:173$OPC_MSG.ACTIONS.AUTOMATIC.ANNO

TATION variable, AR_I:174$OPC_MSG.ACTIONS.AUTOMATIC.COM

MAND variable, AR_I:174$OPC_MSG.ACTIONS.AUTOMATIC.NODE

variable, AR_I:174$OPC_MSG.ACTIONS.AUTOMATIC.STAT

US variable, AR_I:174$OPC_MSG.ACTIONS.OPERATOR

variable, AR_I:174$OPC_MSG.ACTIONS.OPERATOR.ACKNO

WLEDGE variable, AR_I:175$OPC_MSG.ACTIONS.OPERATOR.ANNOT

ATION variable, AR_I:175$OPC_MSG.ACTIONS.OPERATOR.COMM

AND variable, AR_I:175$OPC_MSG.ACTIONS.OPERATOR.COMM

AND[n] variable, AR_I:175$OPC_MSG.ACTIONS.OPERATOR.NODE

variable, AR_I:175$OPC_MSG.ACTIONS.OPERATOR.STATU

S variable, AR_I:176$OPC_MSG.ACTIONS.TROUBLE_TICKET.

ACKNOWLEDGE variable, AR_I:176$OPC_MSG.ACTIONS.TROUBLE_TICKET.

STATUS variable, AR_I:176$OPC_MSG.ANNOTATIONS variable,

AR_I:176$OPC_MSG.ANNOTATIONS[n] variable,

AR_I:177$OPC_MSG.APPLICATION variable,

AR_I:177$OPC_MSG.ATTRIBUTES variable,

AR_I:177$OPC_MSG.CREATED variable, AR_I:177$OPC_MSG.DUPLICATES variable,

AR_I:178

$OPC_MSG.ESCALATION.BY variable, AR_I:178

$OPC_MSG.ESCALATION.TIME variable, AR_I:178

$OPC_MSG.ESCALATION.TO variable, AR_I:178

$OPC_MSG.GROUP variable, AR_I:178$OPC_MSG.INSTRUCTIONS variable,

AR_I:178$OPC_MSG.LAST_RECEIVED variable,

AR_I:179$OPC_MSG.MSG_ID variable, AR_I:179$OPC_MSG.MSG_KEY variable, AR_I:179$OPC_MSG.NO_OF_ANNOTATIONS

variable, AR_I:179$OPC_MSG.NODE variable, AR_I:179$OPC_MSG.OBJECT variable, AR_I:179$OPC_MSG.ORIG_TEXT variable, AR_I:180$OPC_MSG.ORIG_TEXT[n] variable,

AR_I:180$OPC_MSG.OWNER variable, AR_I:180$OPC_MSG.RECEIVED variable, AR_I:180$OPC_MSG.SERVICE variable, AR_I:180$OPC_MSG.SEVERITY variable, AR_I:180$OPC_MSG.SOURCE variable, AR_I:181$OPC_MSG.TEXT variable, AR_I:181$OPC_MSG.TEXT[n] variable, AR_I:181$OPC_MSG.TIME_OWNED variable,

AR_I:181$OPC_MSG.TYPE variable, AR_I:181$OPC_MSG_GEN_NODES variable,

AR_I:170$OPC_MSG_IDS variable, AR_I:170$OPC_MSG_NODES variable, AR_I:169$OPC_MSGIDS_ACT variable, AR_I:170$OPC_MSGIDS_HIST variable, AR_I:171$OPC_MSGIDS_PEND variable, AR_I:171$OPC_NODE_LABELS variable, AR_I:172$OPC_NODES variable, AR_I:171OPC_ONE_LINE_MSG_FORWARD

parameter, AR_I:138opc_op, CG:66

See also netop; opc_adm; operatorsOPC_SEND_ACKN_TO_CTRL_SWTCH

parameter, AR_I:138OPC_SEND_ANNO_TO_CTRL_SWTCH

parameter, AR_I:138OPC_SEND_ANNO_TO_NOTIF parameter,

AR_I:138OPC_SEND_ANT_TO_CTRL_SWTCH

parameter, AR_I:139


Master Index

OPC_SEND_ANT_TO_NOTIF parameter, AR_I:139

$OPC_USER variable, AR_I:159, AR_I:171“opcacta” process, AR_I:304“opcactm” process, AR_I:297“opcconsi” process, AR_I:306“opcctla” process, AR_I:306“opcctlm” process, AR_I:297“opcctrlovw” command, AR_I:283“opcdispm” process, AR_I:297“opcdista” process, AR_I:304“opcdistm” process, AR_I:298“opceca” process, AR_I:304“opcecaas” process, AR_I:305“opcecap” pipe file, AR_I:302, AR_I:308“opcecaq” queue file, AR_I:302, AR_I:308“opcecm” process, AR_I:298“opcecmas” process, AR_I:298opcerr

getting error instructions, AR_I:338“opcforwm” process, AR_I:299“opcinfo” file

location on managed nodes, AR_I:325setting community name, AR_I:386

“opcle” process, AR_I:305“opclic” command

parameters, AR_I:464–AR_I:465syntax, AR_I:464

“opcmack(1)” command, AR_I:483“opcmapnode” command, AR_I:283“opcmon” command, CG:373“opcmon(1)” command, AR_I:483“opcmon(3)” API, AR_I:483“opcmona” process, AR_I:305opcmsg

templatesHP-UX (VPO), AR_II:90Solaris (VPO), AR_II:296Windows NT/2000 (VPO), AR_II:385

“opcmsg for OV Performance” message template, AR_II:224

“opcmsg(1)” commanddescription, AR_I:483flow, CG:367

“opcmsg(3)” APIdescription, AR_I:483EMS, AR_II:106flow, CG:367

“opcmsga” process, AR_I:306

“opcmsgi” process, AR_I:306“opcmsgm” process, AR_I:298“opcmsgr” process, AR_I:299“opcmsgrd” process, AR_I:299opctmpldwn, AR_I:423“opctrapi” process, AR_I:306“opctss” process, AR_I:299“opcttnsm” process, AR_I:299“opcuiadm” process, AR_I:300“opcuiop” process, AR_I:300“opcuiopadm” process, AR_I:300“opcuiwww” process, AR_I:300“opcwall” command, AR_I:444“Open Files” application, AR_II:198opening

Download Configuration Data window, AR_I:437

OpenViewapplications in Java GUI,

AR_I:281–AR_I:283integrating

“Ethernet Traffic HP” as OV application, AR_I:218

“IP Activity Monitoring - Tables” as OV service, AR_I:219

internal traps, AR_II:92maintaining, AR_I:456

OpenView applications, accessing, CG:147OpenView Operations for Windows

configuringagent policy, AR_I:207agents for VPO management server,

AR_I:200–AR_I:202servers to forward messages to VPO,

AR_I:203–AR_I:208VPO agents for management server,

AR_I:196–AR_I:199exporting policies to VPO, AR_I:210forwarding messages on managment

server, AR_I:204importing VPO templates, AR_I:209interoperability with VPO,

AR_I:195–AR_I:210sending messages to management server,

AR_I:196OpenView Performance Agent. See OVPAOpenView VantagePoint Operations. See

VPO


525

Master Index

Oper. Active Details Report, AR_I:112Oper. Active Message Report, AR_I:112operating systems

AIX, AR_II:37–AR_II:70HP-UX

OVPA, AR_II:209–AR_II:230VPO, AR_II:71–AR_II:113

Linux, AR_II:115–AR_II:137MPE/iX, AR_II:139–AR_II:169Novell NetWare, AR_II:171–AR_II:208Sequent DYNIX, AR_II:231–AR_II:245SGI IRIX, AR_II:247–AR_II:261SINIX RM/Reliant, AR_II:263–AR_II:280Solaris

OVPA, AR_II:209–AR_II:230patches, AR_II:289VPO, AR_II:281–AR_II:322

Tru64 UNIX, AR_II:323–AR_II:347Windows NT/2000, AR_II:349–AR_II:444

Operator History Messages Report, AR_I:112operator instructions

reading, CG:158–CG:159Operator Overview Report, AR_I:112Operator Pending Messages Report, AR_I:112Operator Report, AR_I:112operator-initiated actions

annotations, CG:158corrective actions, CG:369process, CG:59–CG:60protecting, AR_I:424reviewing, CG:157starting, CG:157verifying, CG:157–CG:158

operatorsSee also netop; opc_adm; opc_op; template

administrators; users; VPO administrator

accessing GUIJava, AR_I:418Motif, AR_I:417

assigning applications, AR_I:213changing

names, AR_I:415passwords, AR_I:415

defaultAIX, AR_II:67HP-UX, AR_II:100

Linux, AR_II:134–AR_II:135MPE/iX, AR_II:163Novell NetWare, AR_II:203Sequent DYNIX, AR_II:242SGI IRIX, AR_II:258SINIX RM/Reliant, AR_II:277Solaris, AR_II:305Tru64 UNIX, AR_II:343Windows NT/2000, AR_II:427

description, CG:65–CG:67enabling

to control VPO agents, AR_I:220–AR_I:221to manage IP networks in IP map,

AR_I:217mathematical, CG:315–CG:316multiple, CG:61reports

customized, AR_I:115preconfigured, AR_I:114

saving output, AR_I:416security, AR_I:415–AR_I:427types, CG:66windows, CG:66–CG:67

optimizingmessage filtering, CG:332–CG:355performance, CG:332–CG:333

“Optional” ownership mode, CG:153, CG:274<$OPTION(N)> variable, AR_I:157options

Automatic (De-)Installation, AR_I:51tracing, AR_I:327

organizingconditions

overview, CG:314–CG:315sequence, CG:332

managed nodesAIX, AR_II:66–AR_II:67HP-UX, AR_II:99–AR_II:101Linux, AR_II:133–AR_II:135MPE/iX, AR_II:163–AR_II:167Novell NetWare, AR_II:202–AR_II:204overview, CG:208–CG:231Sequent DYNIX, AR_II:241–AR_II:243SGI IRIX, AR_II:257–AR_II:259SINIX RM/Reliant, AR_II:276–AR_II:278Solaris, AR_II:304–AR_II:306Tru64 UNIX, AR_II:342–AR_II:344


Master Index

Windows NT/2000, AR_II:426–AR_II:428message groups

overview, CG:232–CG:233template groups, CG:288–CG:289

organizing Message Groups folder, CG:80original message text, reviewing, CG:137original node, AR_II:448

See also adoptive node; cluster nodes, MC/ServiceGuard; managed nodes, upgrading

“OS” message groupMPE/iX, AR_II:151VPO, AR_I:72

“OS Msgs (DYNIX/ptx)” template, AR_II:237“OS Msgs (SINIX)” template, AR_II:272“OS Msgs” (Tru64 UNIX) template, AR_II:337“outage” template, AR_I:118outages, scheduling, CG:417output

EMS Resources application, AR_II:111operator, CG:202, AR_I:416VPO administrator, AR_I:417

“Output” message groupMPE/iX, AR_II:151VPO, AR_I:72

“OV Performance Agent” template group, AR_II:224

“OV Performance Manager” template group, AR_II:224

“ovbackup.ovpl” command, AR_I:445–AR_I:446

OVKey licensesadvantages, AR_I:462replacing Instant On, AR_I:462

“OVnlm_exit()” API, AR_II:205“OVnlm_init()” API, AR_II:205“ovoareqsdr” process, AR_I:297OVPA

AIX, AR_II:211applications, AR_II:223customizing, AR_II:213data

analyzing, AR_II:212integrating, AR_II:212logging, AR_II:212

de-installing from managed nodes, AR_II:221

description, AR_II:212–AR_II:213

disk space requirements, AR_II:218documentation

downloading, AR_II:227English language, AR_II:228Japanese language, AR_II:230PDFs, AR_II:227viewing, AR_II:227

GlancePlus Trial, AR_II:213hardware requirements, AR_II:215HP-UX, AR_II:209–AR_II:230installation requirements,

AR_II:214–AR_II:218installing on managed nodes,

AR_II:219–AR_II:220overview, AR_II:209–AR_II:230SINIX RM/Reliant, AR_II:211software requirements,

AR_II:216–AR_II:217Solaris, AR_II:209–AR_II:230templates, AR_II:224–AR_II:226Tru64 UNIX, AR_II:211

“ovrestore.ovpl” command, AR_I:446–AR_I:449

ownershipdisplay modes, CG:154, CG:272–CG:273messages, CG:153–CG:154, CG:272–CG:274modes, CG:153, CG:273–CG:274

“Ownership” policy, CG:124owning messages, CG:272

Ppackage, AR_II:448package custody, AR_II:448package IP/hostname, AR_II:448packages

assigning IP addresses and hostnames, AR_II:455

enabling maintenance mode for MC/ServiceGuard, AR_II:459

panes and areasmoving, CG:183showing and hiding, CG:185–CG:187

parametersSee also variableskernel, AR_I:40message buffering, AR_I:131“opclic” command, AR_I:464–AR_I:465


527

Master Index

scheduled outagessyntax, AR_I:131

SYSSTART.PUB.SYS, AR_II:147templates

message forwarding, AR_I:138scheduled outages, AR_I:131service hours, AR_I:131

time zone string, AR_I:135“passwd” option, AR_I:272, AR_I:276passwords

aging, AR_I:419assigning, AR_I:422–AR_I:423changing, CG:172, AR_I:415controlling, AR_I:415DCE nodes, AR_I:420–AR_I:421root, AR_I:49

patches, Solaris, AR_II:289pattern matching

condition examples, CG:316–CG:317mathematical operators, CG:315–CG:316messages, CG:315–CG:323returning node names, AR_I:285syntax, CG:318–CG:320without case-sensitivity, CG:316

pattern-matching optionssetting defaults, CG:302

PDF documentationOVPA, AR_II:227

pending messages browserSee also active message browser; filtered

message browser; history message browser; message browser

investigating problems, CG:150overview, CG:104unbuffering messages, CG:104

“perflbd” monitor template, AR_II:225“PerfMon Objs” application, AR_II:403performance

improvingdatabase, AR_I:319Motif GUI startup, AR_I:322SNMP management platform,

AR_I:318–AR_I:319VPO, AR_I:320–AR_I:321

Java GUI, AR_I:290–AR_I:291monitoring, CG:43

NMA, AR_II:191

optimizing, CG:332–CG:333tuning, AR_I:318–AR_I:322UNIX with JIT, AR_I:290

Performance Agent. See OVPA“Performance” message group


performance metricsabout, CG:374configuring, CG:375monitoring, CG:374

permissionsfile access, AR_I:416GUI, AR_I:417–AR_I:418setting

group, AR_I:416setting file, AR_I:416

Personal Filters, CG:83“Physical Terminal” application, AR_II:159“pids” file, AR_I:302, AR_I:308pipe files

managed nodes, AR_I:307–AR_I:308management server, AR_I:301–AR_I:303

plug-in, HP OpenView application, AR_I:214point-to-point problems, AR_I:389policies

changing WM1 default name, AR_I:208importing OpenView Operations for

Windows policies into VPO, AR_I:210message escalation, CG:429messages, CG:123–CG:124

polling intervalsMIB objects, CG:372programs, CG:372

popup menusbrowser pane, CG:116customizing, CG:189–CG:190object pane, CG:113overview, CG:111shortcut bar, CG:112workspace pane, CG:114

“port” option, AR_I:276position controls

figuresenabling, CG:182main window, CG:110

hiding, CG:182overview, CG:110


Master Index

showing, CG:182PRC authentication, AR_I:407preconfigured

elements, AR_I:71–AR_I:109AIX, AR_II:59–AR_II:63HP-UX (OVPA), AR_II:223–AR_II:226HP-UX (VPO), AR_II:90–AR_II:95Linux, AR_II:128–AR_II:129MPE/iX, AR_II:150–AR_II:160Novell NetWare, AR_II:187–AR_II:199Sequent DYNIX, AR_II:237–AR_II:238SGI IRIX, AR_II:253–AR_II:254SINIX RM/Reliant, AR_II:272–AR_II:273Solaris (OVPA), AR_II:223–AR_II:226Solaris (VPO), AR_II:296–AR_II:301Sun Enterprise E10000,

AR_II:311–AR_II:315Tru64 UNIX, AR_II:337–AR_II:339Windows NT/2000, AR_II:380–AR_II:391

reportsadministrator, AR_I:111operator, AR_I:114

Preferences dialog boxfigures

Events tab, CG:191General tab, CG:189Web Browsers tab, CG:105

itooprc file, AR_I:273–AR_I:278preventing problems, AR_I:323–AR_I:324primary account

creating manually, AR_I:421disabling, AR_I:421

primary manager, CG:422specifying, CG:443–CG:445switching responsibility, CG:443–CG:444

“Print Server” application, AR_II:198“Print Status” application, AR_II:159printer, report, AR_I:110printing

group, message target rules, CG:441man pages, AR_I:497

problemscorrecting, CG:43detecting, CG:119detecting early, CG:283investigating, CG:132–CG:133message forwarding template, CG:459

preventing, AR_I:323–AR_I:324registering, CG:45solving, CG:45, CG:151–CG:152

process, CG:117–CG:118tracing, AR_I:326–AR_I:333troubleshooting, AR_I:323–AR_I:339

database, AR_I:340–AR_I:342embedded performance component,

AR_I:382–AR_I:385GUI on management server,

AR_I:345–AR_I:347installation on managed nodes, AR_I:348installation on MPE/iX managed nodes,

AR_I:350–AR_I:354installation with multi-homed hosts,

AR_I:388–AR_I:396local location brokers, AR_I:381mixed-case node names, AR_I:349NSF, AR_I:397RPC daemons, AR_I:381runtime on all managed nodes,

AR_I:355–AR_I:369runtime on MPE/iX managed nodes,

AR_I:374–AR_I:380runtime on UNIX managed nodes,

AR_I:370–AR_I:373VPO server, AR_I:343–AR_I:344

“proc_util” objectAIX, AR_II:62HP-UX, AR_II:94Sequent DYNIX, AR_II:238SGI IRIX, AR_II:254SINIX RM/Reliant, AR_II:273Solaris, AR_II:301

“Procedures” policy, CG:124process

files, AR_I:306–AR_I:309groups, AR_I:412names, AR_I:412

“Process Kill” application, AR_II:405processes

authentication, AR_I:312–AR_I:314managed node, AR_I:304–AR_I:311management server, AR_I:297–AR_I:303overview, AR_I:293–AR_I:314security, AR_I:312–AR_I:314

“Processes” application, AR_II:160, AR_II:437


529

Master Index

processingactions

automatic, CG:57–CG:58operator-initiated, CG:59–CG:60

managed node filesEnglish, AR_I:252–AR_I:253Japanese, AR_I:255–AR_I:256

management server filesISO 8859-15, AR_I:251Shift JIS, AR_I:254

messagesescalated messages, CG:430–CG:431forwarded, CG:453on management server, CG:309overview, CG:299–CG:306tasks, CG:52–CG:54

templates, multiple, CG:304–CG:305productivity, improving, CG:283profiles

management, CG:433user, CG:62

<$PROG> variable, AR_I:167Program Neighbourhood service, AR_II:433programs

accessingHP-UX, AR_I:418MPE/iX, AR_I:418

distributionAIX, AR_II:64–AR_II:65HP-UX, AR_II:96–AR_II:98Linux, AR_II:130–AR_II:132MPE/iX, AR_II:161–AR_II:162Novell NetWare, AR_II:200–AR_II:201overview, AR_I:188–AR_I:192requirements, AR_I:188Sequent DYNIX, AR_II:239–AR_II:240SGI IRIX, AR_II:255–AR_II:256SINIX RM/Reliant, AR_II:274–AR_II:275Solaris, AR_II:302–AR_II:303tips, AR_I:188–AR_I:191Tru64 UNIX, AR_II:340–AR_II:341Windows NT/2000, AR_II:424–AR_II:425

monitors, CG:371security, AR_I:418

“prompt_for_activate” option, AR_I:276properties, changing default types of all

messages forwarded to VPO, AR_I:208

protectingautomatic actions, AR_I:424configuration distribution, AR_I:423operator-initiated actions, AR_I:424remote actions, AR_I:425–AR_I:427shell scripts, AR_I:424template distribution, AR_I:423

“pvalarmd” monitor template, AR_II:226

Qqueue files

managed nodes, AR_I:307–AR_I:308management server, AR_I:301–AR_I:303removing, AR_I:451security, AR_I:427

“Queues” application, AR_II:198quick filters, accessing, CG:195

R<$R> variable, AR_I:165<$r> variable, AR_I:165ratio, management hierarchy setup, CG:434“Reactivate alarmdef” application, AR_II:223reading operator instructions,

CG:158–CG:159“Reboot” application, AR_II:406reconfiguring

management server after changing hostname or IP address, AR_I:470–AR_I:474

SSPsnmpd daemon, AR_II:316templates, AR_II:318, AR_II:320

VPO agents on regional management servers, CG:437

“reconnect_interval” option, AR_I:276“reconnect_timeout” option, AR_I:276recovering

See also recovery toolsconfiguration data after automatic backup,

AR_I:449–AR_I:451database to latest state, AR_I:450–AR_I:451

recovery tools, AR_I:438See also recovering

redistributing scripts to all managed nodes, AR_I:438

redo logs, creating another set, AR_I:455


Master Index

reducing number of messages, CG:334–CG:355

redundant data on MC/ServiceGuard, AR_II:453–AR_II:454

refresh intervalchanging, CG:178

“refresh_interval” option, AR_I:272, AR_I:276“Reg Viewer” application, AR_II:407regional management servers

configuring, CG:437–CG:438description, CG:434managed nodes, CG:437–CG:438reconfiguring VPO agents, CG:437

registering problems, CG:45regroup conditions

See also regrouping messagesdefining, CG:359examples, CG:360

Regroup Conditions window, CG:359regrouping messages

See also regroup conditionsdescription, CG:290overview, CG:358–CG:360

Reliant. See SINIX RM/Reliant managed nodes

remote accessSee also remote actionsapplications, AR_I:420broadcast commands, AR_I:420I/O applications, AR_I:420

remote actionsSee also remote accessexample, AR_I:425protecting, AR_I:425–AR_I:427security mechanisms, AR_I:426–AR_I:427

remote host equivalence, establishing, AR_II:317

remote installationLinux, AR_II:123

removingSee also de-installing; installingDCE

AIX, AR_II:45SINIX RM/Reliant, AR_II:270Tru64 UNIX, AR_II:331

queue files, AR_I:451VPO agents, AR_I:66

AIX, AR_II:58

Linux, AR_II:127Novell NetWare, AR_II:186SGI IRIX, AR_II:252SINIX RM/Reliant, AR_II:271Solaris, AR_II:295

Removing Older Agents, AR_II:127“rep_server” monitor template, AR_II:225replacing Instant On licenses with OVKey

licenses, AR_I:462reporting errors

GUI Error Dialog Box, AR_I:337–AR_I:338message browser, AR_I:336overview, AR_I:335–AR_I:339“stderr” and “stdout” devices, AR_I:338

reportsadministrator


configuring timeouts, AR_I:110database, AR_I:110–AR_I:116defining printer, AR_I:110generating, CG:46Internet, AR_I:110operator


security, AR_I:116statistical, AR_I:115trend analysis, AR_I:115

requirements. See distribution; installation requirements

rerunning automatic actions, CG:156reset message, sending automatically,

CG:344–CG:346resetting

eventsHACMP 4.2.2, AR_II:55HACMP 4.3.1, AR_II:55–AR_II:56

IP alias for HACMP agents in GUI, AR_II:54resolving message attributes, CG:300resource instances, viewing in EMS GUI,

AR_II:109RESPMGRCONFIG keyword, AR_I:119responding to messages, CG:56responsibility

See also responsible managersdistributing in competence centers,

CG:426–CG:427


531

Master Index

domain hierarchy management, CG:434–CG:435

management serverdelegating, CG:444switching, CG:443–CG:445

operator matrix, CG:204responsible managers

See also responsibilityconfiguration file

creating, CG:439distributing, CG:440

configuring, CG:439–CG:447templates

managed nodes, CG:440syntax, AR_I:125

“Restart PA Servers” application, AR_II:223“Restart Perf Agt” application, AR_II:223restoring database, AR_I:450restricting

See also restrictionsdatabase access, AR_I:116Net8 access, AR_I:116web reporting, AR_I:116

restrictionsSee also restrictingC2 security, CG:207VPO access, CG:62

results, action, CG:155reversing manager switch, CG:444reviewing

acknowledgements, CG:170annotations

actions, CG:155messages, CG:168

automatic actions, CG:156messages

attribites, CG:135details, CG:100groups, CG:233

object status, CG:155operator-initiated actions

annotations, CG:158overview, CG:157

“Rlp Serv (DYNIX/ptx)” template, AR_II:237RM/Reliant. See SINIX RM/Reliant managed

nodesroles, user, CG:61

ROMAN8, converting managed node files, AR_I:252

rootpasswords, AR_I:49user, AR_I:419

RPCauthentication, AR_I:410–AR_I:411

configuring in VPO, AR_I:411VPO example, AR_I:411

login context, AR_I:410server ticket

description, AR_I:410verifying, AR_I:410

troubleshooting, AR_I:381“rqsdbf” file, AR_I:302“rqsp” pipe file, AR_I:303“rqsq” queue file, AR_I:303rules, message target, CG:441“Running Software*” application, AR_II:198runtime problems

all managed nodes, AR_I:355–AR_I:369managed node directories, AR_I:459MPE/iX managed nodes, AR_I:374–AR_I:380UNIX managed nodes, AR_I:370–AR_I:373

S“S” message attribute, AR_I:75<$S> variable, AR_I:166<$s> variable, AR_I:166SAM

ASCII, AR_II:95Motif, AR_II:95VPO Application Bank window,

AR_II:110–AR_II:111“sam” command, AR_II:95Save Browser Filter Settings dialog box

figure, CG:194saving

console settingsfigure, CG:179overview, CG:179–CG:180

customized message browser layout, CG:198message browser filter

object pane, CG:195settings, CG:193–CG:194

outputoperator, CG:202, AR_I:416


Master Index

VPO administrator, AR_I:417scalability

multiple management servers, CG:419–CG:467

scenarios, CG:460–CG:467scanning messages, CG:124scenarios

automating standard, CG:341scalability

multiple management servers, CG:465–CG:466

multiple management servers with VPO agents and NNM collection stations, CG:467

NNM collection station with VPO agents, CG:463–CG:464

single management server, CG:460–CG:461

VPO agents monitoring IP devices, CG:462scheduled outages

configuring, CG:418defining, CG:417overview, CG:417template

examples, AR_I:152location, AR_I:130parameters, AR_I:131syntax, AR_I:128–AR_I:130

scheduling templates, AR_I:130–AR_I:135“scopeux” monitor template, AR_II:225scripts

customized, AR_I:189distributing, AR_I:188–AR_I:192distribution

AIX, AR_II:64–AR_II:65HP-UX, AR_II:96–AR_II:98Linux, AR_II:130–AR_II:132MPE/iX, AR_II:161–AR_II:162Novell NetWare, AR_II:200–AR_II:201requirements, AR_I:188Sequent DYNIX, AR_II:239–AR_II:240SGI IRIX, AR_II:255–AR_II:256SINIX RM/Reliant, AR_II:274–AR_II:275Solaris, AR_II:302–AR_II:303tips, AR_I:188–AR_I:191Tru64 UNIX, AR_II:340–AR_II:341Windows NT/2000, AR_II:424–AR_II:425

“ito_restore.sh”, AR_I:449redistributing, AR_I:438shell, protecting, AR_I:424versions, AR_I:188

SD-UXSee also HP-UX managed nodescreating software depot on remote node,

AR_II:80–AR_II:81enabling, AR_II:82installing VPO agents

from depot node, AR_II:79from SD-UX depot, AR_II:82manually from depot, AR_II:85manually from tape file, AR_II:84overview, AR_II:79–AR_II:82

searching object treeoverview, CG:121

second disk, moving database control files, AR_I:454

secondary managerenabling actions, CG:444specifying, CG:436switching responsibility, CG:443–CG:444

SECONDARYMANAGERS keyword, AR_I:119

“secure_port” option, AR_I:276securing environment, CG:205–CG:207security

auditing, AR_I:428–AR_I:431C2, CG:206–CG:207

guidelines, AR_I:402restrictions, AR_I:403

database, AR_I:419exception warnings, AR_I:291levels, AR_II:152managed nodes, CG:229network

DCE, AR_I:404–AR_I:409overview, AR_I:404–AR_I:414RPC authentication, AR_I:410–AR_I:411

operationsaccessing VPO, AR_I:415overview, AR_I:415–AR_I:427

overview, AR_I:399–AR_I:431processes, AR_I:312–AR_I:314program, AR_I:418remote actions, AR_I:426–AR_I:427


533

Master Index

reports, AR_I:116SSH, AR_I:414system, AR_I:402–AR_I:403types, AR_I:401VPO, CG:206

levels, AR_I:413process, AR_I:412–AR_I:413

“Security” message groupMPE/iX, AR_II:151VPO, AR_I:73

Sel. Active Details Report, AR_I:114Sel. Active Messages Report, AR_I:114Sel.History Details Report, AR_I:114Sel. History Messages Report, AR_I:114Sel. Pending Details Report, AR_I:114Sel. Pending Messages Report, AR_I:114selecting

conditions, CG:315message generation policy, CG:378–CG:381threshold types, CG:377

“semmns” parameter, AR_I:40“Send Message” application, AR_II:437sending

messages to management serverOpenView Operations for Windows,

AR_I:196VPO, AR_I:200

reset message automatically, CG:344–CG:346

“Sendmail” objectLinux, AR_II:129

“sendmail” objectAIX, AR_II:62HP-UX, AR_II:94Sequent DYNIX, AR_II:238SGI IRIX, AR_II:254Solaris, AR_II:301Tru64 UNIX, AR_II:339

Sequent DYNIX managed nodesdefault operator, AR_II:242de-installing agents, AR_II:236directory structure, AR_II:241file locations, AR_II:241hardwarre requirements, AR_II:233include file, AR_II:244installation

requirements, AR_II:233–AR_II:234tips, AR_II:235

installing agents, AR_II:236libraries, AR_II:244–AR_II:245logfile templates, AR_II:237makefile, AR_II:245monitored objects, AR_II:238organization, AR_II:241–AR_II:243overview, AR_II:231–AR_II:245preconfigured elements,

AR_II:237–AR_II:238scripts and programs, AR_II:239–AR_II:240SNMP event interceptor (not supported),


AR_II:233–AR_II:234system resource files, AR_II:243template groups, AR_II:237

sequential conditionsdescription, CG:332selecting, CG:315

“Server Config” application, AR_II:410“server” option, AR_I:272“Server Stats” application, AR_II:411server ticket, RPC, AR_I:410“Servers” application, AR_II:437servers. See management server; managersservice hours, CG:104

configuring, CG:418defining, CG:416overview, CG:415–CG:416template

examples, AR_I:151location, AR_I:130parameters, AR_I:131syntax, AR_I:128, AR_I:130

“service” template, AR_I:119services

ICA Browser, AR_II:432MC/ServiceGuard, AR_II:449OV Service, AR_I:219Program Neighbourhood, AR_II:433

Services workspacefinding impacted VP Navigator services,

CG:147overview, CG:88

“Sessions” application, AR_II:438“Set Parameters*” application, AR_II:198setting

character set


Master Index

GUI, AR_I:234–AR_I:238managed nodes, AR_I:241management server, AR_I:234

community name“opcinfo” file, AR_I:386SNMP daemon configuration file,

AR_I:387file permissions, AR_I:416group permissions, AR_I:416IP aliases for HACMP agents

AIX 4.3, AR_II:52language

managed nodes, AR_I:240management server, AR_I:233

setting upcustomized job stream facility on MPE/iX

managed nodes, AR_II:148management

hierarchies, CG:434server defaults, CG:422

messageconditions, CG:310–CG:314defaults, CG:301–CG:302

node hierarchy, CG:214threshold monitoring, CG:385–CG:386time intervals in time templates, CG:442

settingscompression, CG:350node defaults, CG:228

settings, console, CG:179–CG:180severity

message coloring, CG:129–CG:131viewing in Message Dashboard,

CG:142–CG:146severity messages

evaluating, CG:296levels, AR_I:74–AR_I:75

“Severity” policy, CG:124“severity_label” option, AR_I:276SGI IRIX managed nodes

default operator, AR_II:258de-installing agents, AR_II:252directory structure, AR_II:257file locations, AR_II:257hardware requirements, AR_II:249include file, AR_II:260installation

requirements, AR_II:249–AR_II:250tips, AR_II:251

installing agents, AR_II:252libraries, AR_II:260–AR_II:261logfile templates, AR_II:253makefile, AR_II:261monitored objects, AR_II:254organization, AR_II:257–AR_II:259overview, AR_II:247–AR_II:261preconfigured elements,

AR_II:253–AR_II:254removing agents, AR_II:252scripts and programs, AR_II:255–AR_II:256SNMP event interceptor (not supported),

AR_II:253software requirements, AR_II:250system resource files, AR_II:259template groups, AR_II:253

“Shares” application, AR_II:412sharing message control, CG:449shell scripts, protecting, AR_I:424Shift JIS

converting managed nodes to, AR_I:258processing management server files,

AR_I:254“shmmax” parameter, AR_I:40shortcut bar

customizing, CG:188figures

disabling, CG:186enabling, CG:185main window, CG:73popup menu, CG:112

hiding, CG:185moving, CG:183overview, CG:73–CG:74popup menus, CG:112showing, CG:185

“shortcut_tree_icon_width” option, AR_I:277“Show Drivers” application, AR_II:413“Show Services” application, AR_II:414“Show Users” application, AR_II:416“show_at_severity” option, AR_I:277showing



535

Master Index

“SIA” (Tru64 UNIX) template, AR_II:337Siemens-Nixdorf. See hardware; SINIX

RM/Reliant managed nodesSilicon Graphics Indigo. See hardware; SGI

IRIX managed nodesSINIX RM/Reliant managed nodes

DCEconfiguring, AR_II:269removing, AR_II:270

OVPA, AR_II:211VPO

default operator, AR_II:277de-installing agents, AR_II:271directory structure, AR_II:276file locations, AR_II:276hardware requirements, AR_II:265installation requirements,

AR_II:265–AR_II:266installation tips, AR_II:267–AR_II:268installing agents, AR_II:270libraries, AR_II:279–AR_II:280logfile templates, AR_II:272makefile, AR_II:280monitored objects, AR_II:273organization, AR_II:276–AR_II:278overview, AR_II:263–AR_II:280preconfigured elements,

AR_II:272–AR_II:273removing agents, AR_II:271scripts and programs,

AR_II:274–AR_II:275SNMP event interceptor (not supported),



“SINIX” template group, AR_II:272size, message distribution list,

CG:453–CG:455“smit” command, AR_II:63SMIT User Interface, starting, AR_II:63SMS

integrating into VPO, AR_II:440–AR_II:441integration, AR_II:439–AR_II:444monitors, AR_II:442versions supported, AR_II:439

“SMS” template group, AR_II:380SNMP

configuration file, AR_I:387event interceptor

AIX, AR_II:61HP-UX (VPO), AR_II:92–AR_II:94Linux (not supported), AR_II:129MPE/iX (not supported), AR_II:157Novell NetWare, AR_II:188Sequent DYNIX (not supported),

AR_II:238SGI IRIX (not supported), AR_II:253SINIX RM/Reliant (not supported),

AR_II:272Solaris (VPO), AR_II:298–AR_II:300Tru64 UNIX (not supported), AR_II:338Windows NT/2000, AR_II:385–AR_II:387

events, CG:390–CG:397improving performance, AR_I:318–AR_I:319traps

adding templates, CG:394condition example, CG:396defining template conditions,

CG:394–CG:395forwarding, CG:392–CG:393OpenView, AR_II:92overview, CG:390–CG:397Sun Enterprise E10000, AR_II:312variables, AR_I:163–AR_I:166well-defined, AR_II:92

“SNMP” message group, AR_I:73software

communication, AR_I:41debugging (de-)installation,

AR_I:67–AR_I:68software requirements

OVPAHP-UX, AR_II:216Solaris, AR_II:216–AR_II:217

VPOAIX, AR_II:39–AR_II:40HP-UX, AR_II:73–AR_II:76Linux, AR_II:118–AR_II:120MPE/iX, AR_II:141–AR_II:142Novell NetWare, AR_II:173–AR_II:175Sequent DYNIX, AR_II:233–AR_II:234SGI IRIX, AR_II:250


Master Index

SINIX RM/Reliant, AR_II:265–AR_II:266Solaris, AR_II:284Tru64 UNIX, AR_II:326–AR_II:327Windows NT/2000, AR_II:353–AR_II:354

Solaris managed nodesSee also Sun Clusters; Sun Enterprise

E10000; Sun Management Center; Sun SPARCclassic; Sun SPARCserver; Sun SPARCstation; Sun Ultra

OVPAde-installing, AR_II:221disk space requirements, AR_II:218hardware requirements, AR_II:215installation requirements,

AR_II:214–AR_II:218installing, AR_II:219–AR_II:220overview, AR_II:209–AR_II:230preconfigured elements,

AR_II:223–AR_II:226software requirements,

AR_II:216–AR_II:217template groups, AR_II:224–AR_II:226

VPOactivating agents, AR_II:292–AR_II:293default operator, AR_II:305de-installing agents, AR_II:294directory structure, AR_II:304file locations, AR_II:304hardware requirements, AR_II:283include file, AR_II:308installation requirements,

AR_II:283–AR_II:286installation tips, AR_II:287–AR_II:288installing agents, AR_II:290–AR_II:291libraries, AR_II:307–AR_II:309logfile locations, AR_I:461logfile templates, AR_II:297makefile, AR_II:309MC/ServiceGuard support, AR_II:113message templates, AR_II:296missing OS patches, AR_II:289monitored objects, AR_II:301organization, AR_II:304–AR_II:306overview, AR_II:281–AR_II:322preconfigured elements,

AR_II:296–AR_II:301

removing agents, AR_II:295scripts and programs,

AR_II:302–AR_II:303SNMP event interceptor,

AR_II:298–AR_II:300software requirements, AR_II:284Sun Enterprise Cluster support, AR_II:322Sun Enterprise E10000,

AR_II:310–AR_II:320Sun Management Center integration,

AR_II:321system resource files, AR_II:305template groups, AR_II:296

“solaris” node group, AR_I:71“Solaris” template group, AR_II:296solutions, documenting, CG:46, CG:165solving problems, CG:45

accessing terminal, CG:164adding VPO variables, CG:162applications, CG:160–CG:161broadcasting commands, CG:163–CG:164escalating messages, CG:164evaluating action results, CG:155overview, CG:151–CG:152owning messages, CG:153–CG:154process, CG:117–CG:118reading operator instructions,

CG:158–CG:159verifying

automatic actions, CG:156–CG:157operator-initiated actions, CG:157–CG:158

sources, message correlation, CG:405Spanish

VPO, AR_I:259SPARCclassic. See Sun SPARCclassicSPARCserver. See Sun SPARCserverSPARCstation. See Sun SPARCstationspecial characters, flexible management

templates, AR_I:124SSH

security, AR_I:414VPO agent installation, AR_I:57–AR_I:61

SSPconfiguring, AR_II:316–AR_II:317establishing remote host equivalence,

AR_II:317exporting SSP logfiles directory, AR_II:317


537

Master Index

reconfiguringsnmpd daemon, AR_II:316SSP templates, AR_II:318, AR_II:320

SSP Tools, AR_II:315“SSP Config” application, AR_II:315“SSP” message group, AR_I:73standard de-installation

See also de-installingOVPA


VPOMPE/iX, AR_II:149SINIX RM/Reliant, AR_II:271Solaris, AR_II:294Tru64 UNIX, AR_II:336Windows NT/2000, AR_II:379

standard installationSee also installingOVPA


VPOHP-UX, AR_II:78Linux, AR_II:124MPE/iX, AR_II:149SINIX RM/Reliant, AR_II:270Solaris, AR_II:290Windows NT/2000, AR_II:367–AR_II:372

standard scenarios, automating, CG:341Start Customized Application wizard

figuresbroadcasting commands, CG:163Step 2 of 3, CG:161Step 3 of 3, CG:162

“Start extract” application, AR_II:223“Start Perf Agt” application, AR_II:223“Start pv” application, AR_II:223“Start pvalarmd” application, AR_II:223“Start Services” application, AR_II:417“Start utility” application, AR_II:223starting

applications, CG:160accounts, AR_I:419managed nodes, AR_I:229–AR_I:230remotely, AR_I:420

broadcast commands

managed nodes, AR_I:229–AR_I:230remotely, AR_I:420

corrective actions, CG:369EMS GUI, AR_II:109I/O applications remotely, AR_I:420operator-initiated actions, CG:157SMIT User Interface, AR_II:63streamed jobs on MPE/iX managed nodes,

AR_II:147VPO from operator GUI, CG:202

startup options, Java GUI, AR_I:271–AR_I:272

state-based browsers, CG:341, CG:387–CG:388

statistical reports, AR_I:115“Status Propagation” display mode, CG:154Status Propagation display mode, CG:273status variables, AR_I:132“status.alarmgen” logfile template, AR_II:225“status.mi” logfile template, AR_II:225“status.perflbd” logfile template, AR_II:225“status.pv” logfile template, AR_II:226“status.pvalarmd” logfile template, AR_II:226“status.rep_server” logfile template,

AR_II:225“status.scope” logfile template, AR_II:225“status.ttd” logfile template, AR_II:225“stderr” action, CG:155“stderr” and “stdout” devices, reporting

errors, AR_I:338“stdout” action, CG:155“Stop Perf Agt” application, AR_II:224“Stop pvalarmd” application, AR_II:224“Stop Services” application, AR_II:418strategies

message filtering, CG:332–CG:355message forwarding, CG:456–CG:459

streamed jobs on MPE/iX managed nodescustomizing job stream facility, AR_II:148excluding networking commands, AR_II:147overview, AR_II:147–AR_II:149preparing VPO, AR_II:149starting, AR_II:147SYSSTART.PUB.SYS parameters,

AR_II:147strings, time zone, AR_I:134–AR_I:135“Su (10.x/11.x HP-UX)” logfile, AR_II:91“Su (AIX)” template, AR_II:60“Su (DYNIX/ptx)” template, AR_II:237


Master Index

“Su (IRIX)” template, AR_II:253“Su (SINIX)” template, AR_II:272“Su (Solaris)” template, AR_II:297subnets, heartbeat, AR_II:453–AR_II:454“subproduct” option, AR_I:277Sun Clusters

See also Solaris managed nodes; Sun Enterprise E10000

architecture, AR_II:465description, AR_II:463–AR_II:467glossary, AR_II:464overview, AR_II:461–AR_II:471support, AR_II:322troubleshooting, AR_II:469–AR_II:471VPO agents, AR_II:468

Sun Enterprise E10000See also Solaris managed nodes; Sun

Clustersinstalling VPO agent, AR_II:318–AR_II:320logfile templates, AR_II:313managing, AR_II:310–AR_II:311monitored objects, AR_II:314monitoring, AR_II:310–AR_II:311operating system versions, AR_II:311overview, AR_II:310–AR_II:320preconfigured elements,

AR_II:311–AR_II:315SNMP trap interception, AR_II:312SSP

configuring, AR_II:316–AR_II:317SSP Tools, AR_II:315

template groups, AR_II:311Sun Management Center, AR_II:321

See also Solaris managed nodesSun Microsystems. See Solaris managed

nodes; Sun Clusters; Sun Enterprise E10000; Sun Management Center; Sun SPARCclassic; Sun SPARCserver; Sun SPARCstation; Sun Ultra

Sun Solaris. See SolarisSun SPARCclassic

See also Solaris managed nodesSun SPARCserver

See also Solaris managed nodesSun SPARCstation, AR_II:303

See also Solaris managed nodesSun Ultra

See also Solaris managed nodes

suppressSee also suppressing; suppressionconditions

deploying, CG:333description, CG:311–CG:314

types, verifying, CG:348–CG:350SUPPRESS parameter, AR_I:131suppressing

See also suppress; suppressionduplicate messages, CG:347

flexible management environments, CG:355

management server, CG:353multiple messages, CG:306unmatched conditions, CG:333

suppressionSee also suppress; suppressingcounter, CG:352time, CG:351

“swap_util” objectAIX, AR_II:62HP-UX, AR_II:94Linux, AR_II:129Sequent DYNIX, AR_II:238SGI IRIX, AR_II:254SINIX RM/Reliant, AR_II:273Solaris, AR_II:301Tru64 UNIX, AR_II:339

Switch User template, CG:414switching

backup server, CG:445MC/Service Guard

local networks, AR_II:452–AR_II:453packages, AR_II:450–AR_II:451

message control, CG:449–CG:450primary management responsibility,

CG:443–CG:444reversing switch, CG:444user for VPO agents, AR_I:424

switching message colors to entire line, CG:196

switchover, AR_II:464symptoms, analyzing, AR_I:334synchronizing

commands with VPO agent character set, AR_I:240

VPO and NNM event correlation, CG:407


539

Master Index

syntaxEMS Resources application, AR_II:111files

tracing, AR_I:333“opclic” command, AR_I:464pattern-matching, CG:318–CG:320templates

flexible management, AR_I:124–AR_I:129management responsibility switching,

AR_I:126message operations and target rules,

AR_I:127responsible manager configuration,

AR_I:125scheduled outages, AR_I:128, AR_I:130service hours, AR_I:128, AR_I:130time, AR_I:126

time zone strings, AR_I:134“Syslog (10.x/11.x HP-UX)” logfile, AR_II:91“Syslog (AIX)” template, AR_II:60“Syslog (DYNIX/ptx)” template, AR_II:237“Syslog (IRIX)” template, AR_II:253“Syslog (Solaris)” template, AR_II:297“Syslog Error (DYNIX/ptx)” template,

AR_II:237“Syslogd” object

AIX, AR_II:62HP-UX, AR_II:94Linux, AR_II:129Sequent DYNIX, AR_II:238SGI IRIX, AR_II:254SINIX RM/Reliant, AR_II:273Solaris, AR_II:301Tru64 UNIX, AR_II:339

SYSSTART.PUB.SYS parameters, AR_II:147System Administrator. See SAM“System Log (MetaFrame)” template,

AR_II:434“System Log (Terminal Server)” template,

AR_II:382, AR_II:434system resource files

AIX, AR_II:67HP-UX, AR_II:101MPE/iX, AR_II:164Novell NetWare, AR_II:203Sequent DYNIX, AR_II:243SGI IRIX, AR_II:259SINIX RM/Reliant, AR_II:278

Solaris, AR_II:305Tru64 UNIXT, AR_II:344Windows NT/2000, AR_II:428

system securityexception warnings, AR_I:291overview, AR_I:402–AR_I:403

“System Summary” application, AR_II:199

T<$T> variable, AR_I:166tables and tablespaces

non-VPO, AR_I:492VPO, AR_I:487

tabs, adding to browser pane, CG:195“Tail Status Files” application, AR_II:224tailored set of applications, CG:190“tailored_applications_start” option,

AR_I:277takeover definition, AR_II:464target directories

See also directories; temporary directoriesAIX, AR_II:65HP-UX, AR_II:97Linux, AR_II:132MPE/iX, AR_II:162Novell NetWare, AR_II:201SGI IRIX, AR_II:256SINIX RM/Reliant, AR_II:275Solaris, AR_II:303Tru64 UNIX, AR_II:341Windows NT/2000, AR_II:425

target rules, messages, CG:441tasks

VPO, CG:50–CG:60“TCP/IP Status” application, AR_II:419Technical Workstations, AR_II:98techniques, C2 security, CG:206template administrators

See also operators; templates; users; VPO administrator

description, CG:64template conditions, CG:52

See also templatesTemplate Detail Report, AR_I:112template groups

See also templatesadvantages, CG:288creating, CG:289


Master Index

hierarchiescreating, CG:289navigating, CG:289

organizing, CG:288–CG:289preconfigured

AIX, AR_II:59HP-UX (OVPA), AR_II:224–AR_II:226HP-UX (VPO), AR_II:90Linux, AR_II:128MPE/iX, AR_II:150Novell NetWare, AR_II:187Sequent DYNIX, AR_II:237SGI IRIX, AR_II:253SINIX RM/Reliant, AR_II:272Solaris (OVPA), AR_II:224–AR_II:226Solaris (VPO), AR_II:296Tru64 UNIX, AR_II:337Windows NT/2000, AR_II:380

Sun Enterprise E10000, AR_II:311templates

See also template administrators; template conditions; template groups

addingnew combination of nodes and templates,

CG:292SNMP traps, CG:394

assigning, CG:291–CG:293configuring

application-specific, CG:306multiple, CG:303

creating for message sources, CG:287distributing

assigned, CG:293description, CG:283message source, CG:285–CG:294

EMSconfiguring, AR_II:112downloading, AR_II:112

event correlation example, CG:411–CG:414flexible management

configuring, AR_I:117–AR_I:152examples, AR_I:144–AR_I:152follow-the-sun responsibility switch,

AR_I:146–AR_I:148keywords, AR_I:119–AR_I:124location, AR_I:117

message forwarding between management servers, AR_I:149–AR_I:150

responsibility switch, AR_I:144–AR_I:145scheduled outages, AR_I:152service hours, AR_I:151syntax, AR_I:124–AR_I:129types, AR_I:117

generic, CG:306importing VPO templates into OpenView

Operations for Windows, AR_I:209logfile, CG:362

AIX, AR_II:59–AR_II:60Citrix MetaFrame, AR_II:434HP-UX (VPO), AR_II:91Linux, AR_II:128MPE/iX, AR_II:150Novell NetWare, AR_II:187Sequent DYNIX, AR_II:237SGI IRIX, AR_II:253SINIX RM/Reliant, AR_II:272Solaris (VPO), AR_II:297Sun Enterprise E10000, AR_II:313Tru64 UNIX, AR_II:337–AR_II:338variables, AR_I:160Windows NT/2000, AR_II:381–AR_II:382

management responsibility switching, AR_I:126

messageHP-UX (VPO), AR_II:90Solaris (VPO), AR_II:296Windows NT/2000 (VPO), AR_II:385

message forwarding, CG:452–CG:453attributes, AR_I:137configuring, AR_I:137location, AR_I:136parameters, AR_I:138troubleshooting, CG:459

message operations syntax, AR_I:127message source variables,

AR_I:154–AR_I:167message target rule syntax, AR_I:127MPE/ix console messages

default attributes, CG:400defining, CG:399

multiple, CG:304–CG:305


541

Master Index

protecting distribution, AR_I:423responsible manager, CG:440scheduled outage syntax,

AR_I:128–AR_I:130scheduling, AR_I:130–AR_I:135service hours

location, AR_I:130parameters, AR_I:131syntax, AR_I:128, AR_I:130

SNMP trap variables, AR_I:163–AR_I:166SSP, reconfiguring, AR_II:318, AR_II:320Switch User, CG:414threshold monitor

EMS, AR_II:106variables, AR_I:161

time, CG:442examples, AR_I:139–AR_I:141keywords, AR_I:142–AR_I:143overview, AR_I:139–AR_I:143syntax, AR_I:126

time-indifferent, CG:442Transient Interface Down, CG:413Transient Node Down, CG:412

Templates Groups list box, CG:288Templates Overview Report, AR_I:112Templates Summary Report, AR_I:112temporary directories

See also directories; target directoriesAIX, AR_II:65HP-UX, AR_II:97Linux, AR_II:132MPE/iX, AR_II:162Novell NetWare, AR_II:201Sequent DYNIX, AR_II:240SGI IRIX, AR_II:256SINIX RM/Reliant, AR_II:275Solaris, AR_II:303Tru64 UNIX, AR_II:341Windows NT/2000, AR_II:425

temporary files, excluding from automatic backups, AR_I:442

terminal access, CG:164, CG:206“Terminal Server/MetaFrame” template

group, AR_II:380text, reviewing original message, CG:137<$THRESHOLD> variable, AR_I:161threshold monitors

conditionsadvanced monitoring, CG:385–CG:386examples, CG:389multiple, CG:387–CG:388

configuring, CG:384default, CG:385integrating, CG:382–CG:385messages, CG:369–CG:389templates

EMS, AR_II:106variables, AR_I:161

thresholdsmaximum, CG:377minimum, CG:377

ticket, RPC server, AR_I:410time

attributes, CG:425configuring time-indifferent templates,

CG:442setting intervals, CG:442templates

description, CG:442examples, AR_I:139–AR_I:141keywords, AR_I:142–AR_I:143overview, AR_I:139–AR_I:143syntax, AR_I:126

zone, AR_I:134time-based suppression, CG:351“Time” message attribute, AR_I:77timeouts, configuring for report generation,

AR_I:110Tips_for_Installing_Agents, AR_II:122“title_suffix” option


To De-install an Agent Manually, AR_II:127toolbar


toolsbackup, AR_I:438controller, AR_I:284–AR_I:285license maintenance, AR_I:464–AR_I:465node mapping, AR_I:285–AR_I:286recovery, AR_I:438

tour, Java GUI, CG:71–CG:72“trace” (ASCII) file, AR_I:308“trace” file, AR_I:303


Master Index

“trace” optionito_op, AR_I:272itooprc, AR_I:277

tracingactiviating, AR_I:328–AR_I:330commands, AR_I:67de-activiating, AR_I:330events, AR_I:67examples, AR_I:331–AR_I:332file

location, AR_I:332syntax, AR_I:333

functional areas, AR_I:327problems, AR_I:326–AR_I:333

Transient Interface Down template, CG:413Transient Node Down template, CG:412traps

SNMP, CG:390–CG:397well-defined, AR_II:92

trend-analysis reports, AR_I:115“Trend Parameters*” application, AR_II:199trouble ticket system

connecting management servers, CG:456forwarding messages, AR_I:132

troubleshootingAIX managed nodes, AR_II:53database, AR_I:340–AR_I:342embedded performance component,

AR_I:382–AR_I:385IP aliases, AR_II:53managed node runtime, AR_I:355–AR_I:369management server

GUI, AR_I:345–AR_I:347message forwarding template, CG:459VPO, AR_I:343–AR_I:344

MC/ServiceGuard, AR_II:459MPE/iX managed nodes

installation, AR_I:350–AR_I:354runtime, AR_I:374–AR_I:380

multi-homed host installation, AR_I:388–AR_I:396

NSF, AR_I:397overview, AR_I:323–AR_I:339PRC daemons or local location brokers,

AR_I:381Sun Clusters, AR_II:469–AR_II:471UNIX managed nodes

installation, AR_I:348runtime, AR_I:370–AR_I:373

Tru64 UNIX managed nodesDCE

configuring, AR_II:330–AR_II:331removing, AR_II:331

OVPA, AR_II:211VPO

default operator, AR_II:343directory structure, AR_II:342file locations, AR_II:342hardware requirements, AR_II:325include file, AR_II:346installation requirements,

AR_II:325–AR_II:327installation tips, AR_II:328–AR_II:329libraries, AR_II:345–AR_II:347logfile templates, AR_II:337–AR_II:338makefile, AR_II:347monitored objects, AR_II:339organization, AR_II:342–AR_II:344overview, AR_II:323–AR_II:347preconfigured elements,

AR_II:337–AR_II:339scripts and programs,

AR_II:340–AR_II:341SNMP event interceptor (not supported),



“Tru64 UNIX” template group, AR_II:337trusted system security. See C2 security“TS_Licensing” object, AR_II:433“TS_Service” object, AR_II:433“ttd” monitor template, AR_II:225“ttnsarp” pipe file, AR_I:303“ttnsarq” queue file, AR_I:303“ttnsp” pipe file, AR_I:303“ttnsq” queue file, AR_I:303tuning performance, AR_I:318–AR_I:322Types of Default Applications, AR_II:62

U“U” message attribute, AR_I:75Ultra. See Sun Ultra


543

Master Index

unbuffering messagesautomatically, CG:415manually, CG:415–CG:416

unbuffering pending messages, CG:104UNIX

distribution tips, AR_I:192improving performance, AR_I:290kernel parameters, AR_I:40managed nodes

assigning passwords, AR_I:422troubleshooting

installation, AR_I:348runtime, AR_I:370–AR_I:373

“? Unknown” message severity level, AR_I:74unmatched

conditions, suppressing, CG:333messages, classifying, CG:55

unmattchedmessages, forwarding, AR_I:337

Unmonitored Report, AR_I:112updating current workspace, CG:92–CG:94updating VPO on managed nodes

agents, AR_I:49–AR_I:56configuration, AR_I:185–AR_I:192

uploading configuration files, CG:446URL Shortcuts folder

figuresobject tree, CG:84starting application, CG:93updating application, CG:94

overview, CG:84“Used Shares” application, AR_II:420User Action Report, AR_I:112User Audit Report, AR_I:112User Logon Report, AR_I:113“user” option


User Profile Overview Report, AR_I:113User Profile Report, AR_I:113<$USER> variable, AR_I:167users

See also operators; template administrators; VPO administrator

changingnames, AR_I:415passwords, AR_I:415

concept, CG:61–CG:67

controlling passwords, AR_I:415logged into Java GUI, AR_I:291profiles, CG:62roles, CG:61root, AR_I:419switching for VPO agents, AR_I:424

“Users” application, AR_II:199, AR_II:438

V<$V> variable, AR_I:166<$VALAVG> variable, AR_I:161<$VALCNT> variable, AR_I:161<$VALUE> variable, AR_I:161VantagePoint Navigator man pages, AR_I:502variables

See also parametersaction, AR_I:158–AR_I:159adding VPO, CG:162applications, AR_I:169–AR_I:183environmental, AR_I:154GUI, AR_I:169–AR_I:183

language, AR_I:234instruction text interface, AR_I:168message source templates,

AR_I:154–AR_I:167messages

MPE/iX console, AR_I:162scheduled actions, AR_I:167

monitoring, CG:377overview, AR_I:153–AR_I:183status, AR_I:132templates

logfile, AR_I:160SNMP trap, AR_I:163–AR_I:166threshold monitor, AR_I:161

types, AR_I:153verifying

automatic actions, CG:156–CG:157operator-initiated actions, CG:157–CG:158RPC server ticket, AR_I:410suppress types, CG:348–CG:350

versionsprograms, AR_I:188scripts, AR_I:188VPO, AR_I:324–AR_I:325VPO agent

displaying available, AR_I:65


Master Index

displaying installed, AR_I:65managing, AR_I:64removing, AR_I:66

viewingEMS GUI resource instances, AR_II:109message severity in Message Dashboard

overview, CG:142–CG:146messages

in message browser, CG:122OVPA documentation, AR_II:227

“Virtual Terminal” application, AR_II:160, AR_II:162

“Virtual Terminal PC” application, AR_II:421“Volume” application, AR_II:199VP Navigator

finding impacted services, CG:147VPO

See also VPO agents; VPO-SEapplications, CG:216benefits, CG:39character code conversion,

AR_I:250–AR_I:256communication, AR_I:295–AR_I:296concepts

client-server, CG:40–CG:41user, CG:61–CG:67

configuringoverview, CG:199–CG:280,

AR_I:69–AR_I:183RPC authentication, AR_I:411to accept messages forwarded from

OpenView Operations for Windows, AR_I:205–AR_I:207

database tables and tablespaces, AR_I:487defaults

administrator, CG:177system, CG:174

description, CG:39–CG:44Distributed Event Interception, AR_II:92

configuring, AR_II:93description, AR_II:92

event interceptor, CG:407exporting templates to OpenView

Operations for Windows, AR_I:209features, CG:23filtering internal error messages, CG:402,

AR_I:339

functionality, CG:45–CG:49importing OpenView Operations for

Windows policies, AR_I:210improving performance, AR_I:320–AR_I:321installing configuration on managed nodes,

AR_I:185–AR_I:192integrating applications

actions, AR_I:223–AR_I:224Application Desktop, AR_I:214–AR_I:215broadcast commands, AR_I:222components, AR_I:213HP applications, AR_I:213HP OpenView plug-in, AR_I:214monitoring applications, AR_I:225NNM, AR_I:215, AR_I:216–AR_I:221overview, AR_I:211–AR_I:230VPO applications, AR_I:214

integrating SMS, AR_II:440–AR_II:441interoperability

OpenView Operations for Windows, AR_I:195–AR_I:210

overview, AR_I:193–AR_I:210language support, AR_I:231–AR_I:263maintaining, CG:199–CG:280,

AR_I:433–AR_I:480man pages, AR_I:498mapping file problems, AR_II:166MC/ServiceGuard, AR_II:456–AR_II:458MC/ServiceGuard support, AR_II:113message interface, CG:367–CG:368monitoring, CG:120other languages, AR_I:260–AR_I:262overview, CG:37–CG:67process

groups, AR_I:412names, AR_I:412

processes, AR_I:293–AR_I:314security

auditing, AR_I:428–AR_I:431levels, AR_I:413methods, CG:206operations, AR_I:415–AR_I:427overview, AR_I:399–AR_I:431VPO processes, AR_I:412–AR_I:413

sending messages to management server, AR_I:200


545

Master Index

Spanish language, AR_I:259starting from operator GUI, CG:202Sun Enterprise Cluster support, AR_II:322Sun Management Center integration,

AR_II:321tasks, CG:50–CG:60troubleshooting, AR_I:323–AR_I:339

server, AR_I:343–AR_I:344tuning performance, AR_I:318–AR_I:322updating configuration on managed nodes,

AR_I:185–AR_I:192variables, CG:162versions, AR_I:324–AR_I:325

VPO Add Node window, CG:224–CG:227VPO administrator

See also administrative rights; operators; template administrators; users

changing responsibility matrix, CG:204description, CG:62–CG:63environment, CG:201–CG:204GUI

access, AR_I:417description, CG:202

message browser, CG:203–CG:204reports


responsibility matrix, CG:204saving, AR_I:417

VPO agentsSee also VPOactivating on Solaris managed nodes

command line, AR_II:292GUI, AR_II:293

configuration fileslocation, AR_I:311types, AR_I:310

configuring OpenView Operations for Windows management server, AR_I:196–AR_I:199

de-installing from managed nodesAIX, AR_II:58automatically, AR_I:62–AR_I:63HP-UX, AR_II:89Linux, AR_II:127manually, AR_I:63MPE/iX, AR_II:149

Sequent DYNIX, AR_II:236SGI IRIX, AR_II:252SINIX RM/Reliant, AR_II:271Solaris, AR_II:294Tru64 UNIX, AR_II:336Windows NT/2000, AR_II:379

distributing configuration to managed nodes, AR_I:187

enabling operators to control, AR_I:220–AR_I:221

HACMP, AR_II:50installation

managed nodes, AR_I:37–AR_I:56reasons not to install, CG:218requirements, AR_I:39–AR_I:41script, AR_I:49tips, AR_I:42–AR_I:48

installing on managed nodesAIX, AR_II:45–AR_II:57HP-UX, AR_II:77–AR_II:85Linux, AR_II:123–AR_II:126MPE/iX, AR_II:149Novell NetWare, AR_II:181–AR_II:186Sequent DYNIX, AR_II:236SGI IRIX, AR_II:252SINIX RM/Reliant, AR_II:270Solaris, AR_II:290–AR_II:291Sun Enterprise E10000,

AR_II:318–AR_II:320Tru64 UNIX, AR_II:332Windows NT/2000, AR_II:355–AR_II:378

managing, AR_I:64–AR_I:66monitoring

IP devices, CG:462objects, CG:371–CG:376

reconfiguring on regional management servers, CG:437

removing from managed nodesAIX, AR_II:58Linux, AR_II:127Novell NetWare, AR_II:186SGI IRIX, AR_II:252SINIX RM/Reliant, AR_II:271Solaris, AR_II:295

SSH installation method, AR_I:57–AR_I:61Sun Clusters, AR_II:468


Master Index

switching user, AR_I:424synchronizing commands with character

set, AR_I:240updating on managed nodes,

AR_I:49–AR_I:56versions

description, AR_I:64displaying available, AR_I:65displaying installed, AR_I:65removing, AR_I:66

with NNM collection stations, CG:463on multiple management servers, CG:467

VPO Application Bank windowEMS resource hierarchy,

AR_II:110–AR_II:111VPO Error Report, AR_I:113, AR_I:114VPO Message Group Bank window, CG:232VPO Node Bank window, CG:210–CG:211VPO Node Hierarchy Bank window,

CG:212–CG:216VPO Node Hierarchy window, CG:209VPO-SE

See also VPOvt3k operation, AR_II:165

W“Warning” message severity level, AR_I:74web browser

choosing, CG:188figures

embedded web browser, CG:107proxy settings, CG:107

overview, CG:105–CG:107web reporting, restricting, AR_I:116“web_browser_type” option, AR_I:278well-defined traps, AR_II:92“which_browser” option, AR_I:278windows

managed nodeAdd Node for External Events, CG:217Node Advanced Options, CG:226Node Communication Options, CG:227primary windows, CG:209VPO Add Node, CG:225VPO Add Nodes, CG:217VPO Node Bank, CG:210–CG:211

VPO Node Hierarchy Bank, CG:212–CG:216

NetWareNetWare Config, AR_II:191NetWare Performance, AR_II:192NetWare Tools, AR_II:193

operatorApplication Desktop, CG:66Managed Nodes, CG:66Message Browser, CG:67Message Groups, CG:66

template administratorAdd Configuration window, CG:292Add MPE/iX Console Messages, CG:399Add SNMP Trap, CG:394Condition No., CG:386Define Configuration, CG:291Message and Suppress Conditions, CG:314Message Condition Advanced Options,

CG:394Message Correlation, CG:337Message Source Template, CG:287Message Source Templates, CG:294Modify VPO Interface Messages, CG:368Regroup Conditions, CG:359

VPO administratorConfigure Management Server, AR_I:191Download Configuration Data,

AR_I:435–AR_I:437Install/Update VPO Software and

Configuration, AR_I:51, AR_I:187Message Group Bank, AR_I:72Node Group Bank, AR_I:71

“Windows 2000” template group, AR_II:380Windows Installation Server requirements,

AR_II:352Windows managed nodes requirements,

AR_II:352“Windows NT” template group

Windows NT/2000, AR_II:380Windows NT/2000 managed nodes

agent accounts, AR_II:358–AR_II:360alternative accounts, AR_II:359–AR_II:360applications, AR_II:392–AR_II:423assigning passwords, AR_I:423Citrix MetaFrame

applications, AR_II:435–AR_II:438


547

Master Index

integration, AR_II:430–AR_II:434default operator, AR_II:427de-installing agents, AR_II:379directory structure, AR_II:426file locations, AR_II:427FTP

installing agents, AR_II:361–AR_II:366re-installing agents, AR_II:372–AR_II:375

hardware requirements, AR_II:351–AR_II:352

HP ITO Account, AR_II:358include file, AR_II:429installation

methods, AR_II:357requirements, AR_II:351–AR_II:354

installing agents, AR_II:355–AR_II:378libraries, AR_II:429logfile locations, AR_I:460logfile templates, AR_II:381–AR_II:382makefile, AR_II:429management server requirements,

AR_II:351monitored objects, AR_II:388node requirements, AR_II:352organization, AR_II:426–AR_II:428overview, AR_II:349–AR_II:444preconfigured elements,

AR_II:380–AR_II:391pre-installing agents, AR_II:376–AR_II:378re-installing agents, AR_II:372–AR_II:375scripts and programs, AR_II:424–AR_II:425SMS integration, AR_II:439–AR_II:444SNMP event interceptor,

AR_II:385–AR_II:387software requirements,

AR_II:353–AR_II:354system resources, AR_II:428template groups, AR_II:380VPO

message templates, AR_II:385Windows Installation Server requirements,

AR_II:352WMI policy, changing default name, AR_I:208Working VPO Operators Report, AR_I:113workspace pane

accessing OpenView applications, CG:147evaluating action results, CG:155

figuresgraphs and charts, CG:87main window, CG:85message browser, CG:97moving (after), CG:184moving (before), CG:183popup menu on pane, CG:115popup menu on tab, CG:114

finding impacted VP Navigator services, CG:147

investigating problems, CG:141moving, CG:183overview, CG:85–CG:87popup menus, CG:114workspaces

Corrective Actions, CG:90Diagnostic Dashboard, CG:89Message Dashboard, CG:88Online Help, CG:91Services, CG:88updating current, CG:92–CG:94

Workspace Properties dialog boxfigure, CG:106

“Workst Stats” application, AR_II:423worldwide management. See follow-the-sun

controlworldwide management domain, CG:424writing to default working directory,

AR_I:416

XX resources

fonts, AR_I:236–AR_I:238<$X> variable, AR_I:166<$x> variable, AR_I:166“XCONSOLE” application, AR_II:199X-OVw group applications, AR_I:281

Zzone, time

parameter, AR_I:135string, AR_I:134
