HP OpenView VantagePoint Operations for UNIX Administrators 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.22719 for other agencies. HEWLETT-PACKARD COMPANY United States of America Copyright Notices. Copyright 1996-2003 Hewlett-Packard Development Company, 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.

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.

Contents
1. About AIX Managed Nodes
In this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for NCS RPC on AIX Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . Requirements for DCE RPC on AIX Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods for Installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring DCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Configure a Minimal DCE Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Configure a Full DCE Environment (RPC Only) . . . . . . . . . . . . . . . . . . . . . . . . To Remove an Existing DCE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Configuring DCE on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Install the AIX Agent on the Managed Node . . . . . . . . . . . . . . . . . . . . . . . . . . . To Activate the AIX Managed Node from the Command Line . . . . . . . . . . . . . . . . To Activate the AIX Managed Node from the VPO GUI. . . . . . . . . . . . . . . . . . . . . Installing Agents in HACMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About VPO Agents in HACMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About IP Aliases in HACMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Naming Scheme for IP Addresses in HACMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements for AIX HACMP Agents . . . . . . . . . . . . . . . . . . . . . . . . To Set an IP Alias for AIX HACMP Agents on AIX . . . . . . . . . . . . . . . . . . . . . . . . Fixing Problems with IP Aliases on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Reset the IP Alias on the network interface card. . . . . . . . . . . . . . . . . . . . . . . . To Reset Events on HACMP 4.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Reset Events on HACMP 4.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Install AIX HACMP Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To De-install VPO Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Remove Older Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Preconfigured Template Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 39 39 39 40 40 41 41 41 44 44 44 45 45 46 46 46 47 49 50 50 50 51 52 52 53 54 55 55 56 58 58 58 58 59 59 59

Contents
Support for SNMP Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the SMIT User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributing Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of User Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Temporary Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Target Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Default VPO Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About System Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 62 62 63 64 64 65 65 66 66 67 67 68 69 70

2. About HP-UX Managed Nodes

In this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements for HP-UX 10.x/11.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements for HP-UX 10.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements for HP-UX 11.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods for Installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents with Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents with SD-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents from a SD-UX Depot Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a SD-UX Depot on a Remote Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents from the SD-UX Depot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling SD-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Install an Agent Manually from the SD-UX Tape Files. . . . . . . . . . . . . . . . . . . To Install an Agent Manually from an SD-UX Depot . . . . . . . . . . . . . . . . . . . . . . . Activating the Managed Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Activate the Node from the VPO GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Activate the Node from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 73 73 74 75 77 77 77 78 79 79 80 82 82 83 84 85 86 86 88 89

Contents
De-installing Agents Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 To De-install an Agent Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 If Errors Occur During De-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Types of Preconfigured Template Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Types of Default opcmsg Message Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 About SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Types of SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 About VPO Distributed Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 To Configure Basic Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 To Avoid Duplicate Messages in Event Interception. . . . . . . . . . . . . . . . . . . . . . . . 93 To Configure Event Interception with ECS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 About Motif SAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 About ASCII SAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Distributing Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Location of User Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 About Temporary Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 About Target Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Tips for Distributing on HP-UX 10.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 About the Default VPO Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Types of System Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 About the Makefiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Monitoring Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 About EMS Threshold Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Types of Data Returned by the Monitor Executable . . . . . . . . . . . . . . . . . . . . . . . 107 Setting up a Threshold Monitor Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Viewing the Resource Hierarchy in the EMS GUI Client . . . . . . . . . . . . . . . . . . . . 109 To Start the EMS GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 To View Resource Instances in the EMS GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 To Close the EMS GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Types of EMS Resource Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Contents
Viewing the Resource Hierarchy in the VPO Application Bank . . . . . . . . . . . . . . . About the EMS Resources Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sample Output from the EMS Resources Command . . . . . . . . . . . . . . . . . . . . . . Syntax for the EMS Resource Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If Error Occur with EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the Resource Hierarchy from the Command Line . . . . . . . . . . . . . . . . . . . Sending EMS Notifications to VPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Download VPO EMS Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring VPO EMS Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High Availability Support on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 110 111 111 111 112 112 112 112 113

3. About Linux Managed Nodes

In this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before Installing Agents Remotely. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents with Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Install an Agent Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If Errors Occur During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To De-install an Agent Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Older Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preconfigured Template Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributing Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of User Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Temporary Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Target Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 117 117 118 122 122 123 123 124 124 126 127 127 127 127 128 128 128 129 129 129 130 131 132 132 133

Contents
Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Default VPO Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Default VPO Operator Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Default VPO Operator Group Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 134 134 135 136 137 137

4. About MPE/iX Managed Nodes

In this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required MPE/iX Patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Management Server Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Default VPO Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Login and Logout UDCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Domain Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Logging Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About VPO Agent Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Executable Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Time Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Spool Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Streamed Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters for SYSSTART.PUB.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Excluding Network Commands from SYSSTART.PUB.SYS . . . . . . . . . . . . . . . . Starting a Streamed Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Set up a Customized Job Stream Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing VPO for a Customized Job Stream Facility . . . . . . . . . . . . . . . . . . . . . Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 141 141 141 142 142 143 143 143 143 144 144 144 144 145 145 145 145 146 146 147 147 147 147 148 149 149 149 150

Contents
Types of Preconfigured Template Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intercepting Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Default Message Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping Messages to VPO Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping NMEV Markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating a New NMEV Marker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Configuring File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Lan Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Monitor Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Physical Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Print Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Virtual Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributing Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of User Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Temporary Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Target Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Default VPO Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the System Resource File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping ARPA Host Names to NS Node Names . . . . . . . . . . . . . . . . . . . . . . . . . . . About the vt3k Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Problems with ARPA Hostnames and NS Node Names . . . . . . . . . . . . . . . . . . . . Avoiding Problems with the VPO Mapping File . . . . . . . . . . . . . . . . . . . . . . . . . . Resolving ARPA Hostname to NS Node Names . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Makefiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 150 151 151 152 152 155 157 157 157 158 158 159 159 159 159 159 160 160 161 161 162 162 163 163 163 164 164 165 166 166 167 168 168 169

10

Contents
5. About Novell NetWare Managed Nodes
In this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements for the Managed Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements for the Depot Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Install Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Older Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . One Preconfigured Template Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Novell NetWare Management Agent (NMA) . . . . . . . . . . . . . . . . . . . . . . . About the NMA 2.1 Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the NetWare Config Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the NetWare Performance Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the NetWare Tools Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of NetWare Tools Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of NMA Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Distribution and Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of User Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Temporary Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Target Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Default VPO Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of System Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples of VPO-enabled NLMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 173 173 174 175 176 176 179 181 186 187 187 187 188 188 189 189 190 191 191 192 193 194 197 200 200 201 201 202 202 203 203 205 205 206 207 207 208 11

Contents
6. About OpenView Performance Agent for HP-UX and Sun Solaris
In this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Other Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What OVPA Does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating Data with OVPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analyzing Data with OVPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging Data with OVPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customizing OVPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trying HP OpenView GlancePlus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements for Sun Solaris. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements for Sun Solaris. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk Space Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and De-installing OVPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing OVPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Install OVPA with Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Install OVPA Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing OVPA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To De-install OVPA with Standard De-installation . . . . . . . . . . . . . . . . . . . . . . . To De-install OVPA Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the OV Performance Agent Template Group . . . . . . . . . . . . . . . . . . . . . . . About the OV Performance Manager Template Group . . . . . . . . . . . . . . . . . . . . . About Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading and Viewing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of English-language Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Japanese-language Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 211 212 212 212 212 213 213 214 215 215 215 216 216 216 218 219 219 219 220 221 221 222 223 223 224 224 225 227 227 228 230

12

Contents
7. About Sequent DYNIX Managed Nodes
In this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . One Preconfigured Template Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributing Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of User Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Temporary Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Default VPO Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Default VPO Operator Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Default VPO Operator Group Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of System Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 233 233 233 235 235 236 236 237 237 237 238 238 238 239 239 240 241 241 242 242 242 243 244 244 245

8. About SGI IRIX Managed Nodes

In this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 249 249 250 251 251 252 252 252

13

Contents
About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . One Preconfigured Template Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributing Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of User Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Temporary Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Target Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Default VPO Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Default VPO Operator Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Default VPO Operator Group Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of System Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 253 253 253 254 254 255 255 256 256 257 257 258 258 258 259 260 260 261

9. About SINIX RM/Reliant Managed Nodes

In this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring DCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Configure DCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Remove an Existing DCE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents with Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents with Standard De-installation . . . . . . . . . . . . . . . . . . . . . . To De-install an Agent Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Older Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 265 265 265 267 267 269 269 270 270 270 270 271 271 271 271 272

14

Contents
One Preconfigured Template Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributing Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of User Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Temporary Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Target Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Default VPO Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Default VPO Operator Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Default VPO Operator Group Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of System Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 272 272 273 274 274 275 275 276 276 277 277 277 278 279 280

10. About Sun Solaris Managed Nodes

In this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Problems Caused by Missing OS Patches for Sun Solaris . . . . . . . . . . . . . . . . . . . . Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents with Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Install an Agent Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Activate a Node from the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Activate the Node from the VPO GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents with Standard De-installation . . . . . . . . . . . . . . . . . . . . . . To De-install an Agent Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Older Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . One Preconfigured Template Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default opcmsg Message Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 283 283 284 287 287 289 290 290 290 292 292 293 294 294 294 295 296 296 296

15

Contents
Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About VPO Distributed Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Configure Basic Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Avoid Duplicate Messages in Event Interception. . . . . . . . . . . . . . . . . . . . . . . To Configure Event Interception with ECS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributing Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of User Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Temporary Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Target Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Default VPO Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of System Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support for Sun Enterprise E10000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring and Managing E10000 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Software and OS Versions for E10000 Systems . . . . . . . . . . . . . . . . . . . . . . . About Preconfigured Elements for E10000 Systems . . . . . . . . . . . . . . . . . . . . . . . . One Preconfigured Template Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About SNMP Trap Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Encapsulated Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About SSP Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the SSP System for E10000 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . To Reconfigure the SSP snmpd Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Establish Remote Host Equivalence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Export the SSP Logfiles Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the VPO Agent for E100000 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before Installing the VPO Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Install the VPO Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reconfiguring the SSP Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the VPO Integration Package for Sun Management Center . . . . . . . . . . . . . . High Availability Support on Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 297 298 298 298 299 299 300 301 301 302 302 303 303 304 304 305 305 307 308 309 310 310 311 311 311 312 313 314 315 316 316 317 317 318 318 318 320 321 322

Contents
11. About Tru64 UNIX Managed Nodes
In this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tips for Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Configure DCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing an Existing DCE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating the Managed Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Activate the Node from the VPO GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Activate the Node from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents with Standard De-installation . . . . . . . . . . . . . . . . . . . . . . To De-install an Agent Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . One Preconfigured Template Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Modify a Logfile Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No SNMP Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributing Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of User Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Temporary Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Target Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Default VPO Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Default VPO Operator Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Default VPO Operator Group Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of System Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 325 325 326 328 328 330 331 332 332 333 333 335 336 336 336 337 337 337 338 338 339 339 340 340 341 341 342 342 343 343 344 344 345 346 347

17

Contents
12. About Windows NT/2000 Managed Nodes
In this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the VPO Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Windows Installation Server . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Windows Managed Node . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods for Installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About VPO Agent Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the HP ITO account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Alternative Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents through FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the First Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Additional Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Install an Agent through FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Agents with Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Domain Requirements for a Standard Installation. . . . . . . . . . . . . . . . . . . . . . . . VPO Requirements for a Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . FTP Requirements for a Standard Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . To Install an Agent with Standard Installation . . . . . . . . . . . . . . . . . . . . . . . . . . If an Error Occurs During a Standard Installation . . . . . . . . . . . . . . . . . . . . . . . Re-installing Agents through FTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Re-installing the First Agent or an Installation Server . . . . . . . . . . . . . . . . . . . . Re-installing Additional Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Re-install an Agent through FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-installing Agents Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . When to Pre-install Agents Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Pre-install a Windows Agent on a Windows PC . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing Agents with Standard De-installation . . . . . . . . . . . . . . . . . . . . . . To De-install an Agent Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If Errors Occur During De-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Preconfigured Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types Preconfigured Template Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 351 351 351 352 352 353 355 355 357 358 358 359 361 361 361 362 367 367 367 368 368 372 372 372 372 373 376 376 376 379 379 379 379 380 380 381

18

Contents
About Logfile Templates for Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Logfile Templates for Windows NT Terminal Server . . . . . . . . . . . . . . . . . Monitoring Eventlogs on Windows Managed Nodes. . . . . . . . . . . . . . . . . . . . . . . . . Syntax for Eventlogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Eventlogs in the Message Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default opcmsg Message Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About SNMP Trap and Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About VPO Distributed Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Configure Basic Event Interception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Avoid Duplicate Messages in Event Interception. . . . . . . . . . . . . . . . . . . . . . . Types of Default Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Windows Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Monitor Windows Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax for the Windows Performance Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . Guidelines for Object and Counter Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Guidelines for Parent Instance and Instance Values . . . . . . . . . . . . . . . . . . . . . . Locating Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Default Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Cancel Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Installed Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Job Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About LM Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Local Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Memory Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About NetBios Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About PerfMon Objs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Process Kill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Reg Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Server Config. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Server Stats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Shares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Show Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Show Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Show Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Start Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 382 383 383 384 385 385 385 386 386 387 388 389 389 389 390 391 391 392 392 393 397 398 399 400 401 402 403 405 406 407 410 411 412 413 414 416 417

19

Contents
About Stop Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About TCP/IP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Used Shares. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Virtual Terminal PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About VPO Install Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Workst Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributing Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of User Scripts and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Temporary Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Target Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization of Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Default VPO Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of System Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VPO Managed Node Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Include File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Citrix MetaFrame Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Versions of Citrix MetaFrame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements for Citrix MetaFrame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating Citrix MetaFrame into VPO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Configure the Citrix MetaFrame Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the ICA Browser Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Program Neighbourhood Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of MetaFrame Monitored Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of MetaFrame Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Citrix MetaFrame Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About ACL Info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Auditlog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Flush . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Send Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About SMS Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 419 420 421 422 423 424 424 425 425 426 427 427 428 429 429 429 430 430 430 431 432 432 433 433 434 435 435 435 436 436 436 437 437 437 438 438 439

20

Contents
Supported Versions of SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating SMS into VPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Integrate SMS into VPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of VPO-SMS Monitors for SMS Services. . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping SMS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning SMS Messages to VPO Message Groups . . . . . . . . . . . . . . . . . . . . . . . Assigning SMS Messages to VPO Message Objects . . . . . . . . . . . . . . . . . . . . . . . 439 439 440 442 443 443 444

A. About MC/ServiceGuard
In this Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is MC/ServiceGuard? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transferring Applications to Other Management Servers. . . . . . . . . . . . . . . . . . . . Glossary of MC/ServiceGuard Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How MC/ServiceGuard Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 1. Switching Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 2. Switching Local Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 3. Redundant Data and Heartbeat Subnets . . . . . . . . . . . . . . . . . . . . . . . Assigning IP Addresses and Hostnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning IP Addresses to LAN Interface Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning IP Addresses and Hostnames to Packages. . . . . . . . . . . . . . . . . . . . . . . . Running VPO in an MC/ServiceGuard Environment . . . . . . . . . . . . . . . . . . . . . . . . . Running NNM on MC/ServiceGuard Cluster Nodes . . . . . . . . . . . . . . . . . . . . . . . . Running a VPO Management Server in an MC/ServiceGuard Environment . . . . . Running VPO Agents in an MC/ServiceGuard Environment . . . . . . . . . . . . . . . . . Troubleshooting VPO MC/ServiceGuard Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of VPO MC/ServiceGuard Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Maintenance Mode for VPO MC/ServiceGuard Packages . . . . . . . . . . . . 446 447 447 448 450 450 452 453 455 455 455 456 456 457 458 459 459 459

B. Administration of Sun Enterprise Clusters

In this Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What are Sun Clusters?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of Sun Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glossary of Sun Cluster Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Sun Cluster Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of a Failover Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running VPO Agents in a Sun Cluster Environment . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting VPO in a Sun Cluster Environment . . . . . . . . . . . . . . . . . . . . . . . . . About the Data Service Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Sun Cluster Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462 463 463 464 465 466 468 469 469 471 21

Contents
C. Administration of VERITAS Cluster Server
In this Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VERITAS Cluster Server Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switchover Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switchover procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running VPO Agents in a VERITAS Cluster Server Environment . . . . . . . . . . . . . . Troubleshooting VPO in a VERITAS Cluster Server Environment . . . . . . . . . . . . . . VPO/VERITAS Cluster Server Logfiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preconfigured Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Templates and Template Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Template Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logfile Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitor Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applications and Application Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VERITAS Cluster Server Cluster Manager application . . . . . . . . . . . . . . . . . . . . VERITAS Volume Manager Storage Administrator application . . . . . . . . . . . . . 474 475 476 477 481 482 482 483 483 483 483 484 485 485 485 485

22

Printing History
The 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: Second Edition: Third Edition: Fourth Edition: September 1999 June 2000 January 2002 July 2003

23

24

Conventions
The following typographical conventions are used in this manual. Table 1 Font Italic Typographical Conventions Meaning Book or manual titles, and man page names Emphasis Variable that you must supply when entering a command Parameters to a function Bold Computer New terms Text and other items on the computer screen Example Refer to the VPO Administrators Reference Volume I and the opc(1M) manpage for more information. You must follow these steps. At the prompt, enter rlogin username. The oper_name parameter returns an integer response. The monitor agent observes... The following system message appears: Are you sure you want to remove current group? Command names Function names File and directory names Process names Window/dialog box names 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. Use the grep command ... Use the opc_connect() function to connect ... /opt/OV/bin/OpC/ Check to see if opcmona is running. In the Add Logfile window ... Select Actions: Filtering -> All Active Messages from the menu bar.

25

Table 1 Font Computer Bold

Keycap

Typographical Conventions Meaning Text that you enter Keyboard keys Buttons in the user interface Example At the prompt, enter ls -l Press Return. Click [OK].

[Button]

26

VPO Documentation Map

HP 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 Manuals

All 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 Manuals
This section provides an overview of the VPO manuals and their contents. Table 2
Manual VPO Installation Guide for the Management Server

VPO Manuals
Description Designed for administrators who install VPO software on the management server and perform initial configuration. This manual describes: Media Hardcopy PDF

Software and hardware requirements Software installation and de-installation instructions Configuration defaults
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. Designed for administrators 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. Provides platform-specific information about each managed node platform. Provides a detailed description of the VPO database tables, as well as examples for generating reports from the VPO database. Provides you with an overview of the relationships between the tables and the VPO database. 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. Hardcopy PDF

VPO Administrators Reference Volume I

PDF only

VPO Administrators Reference Volume II VPO Reporting and Database Schema VPO Entity Relationship Diagrams HP OpenView VPO Java GUI Operators Guide

PDF only

PDF only

PDF only PDF only

28

Table 2
Manual

VPO Manuals
Description Describes new features and helps you: Media PDF only

VPO Software Release Notes

Compare features of the current software with

features of previous versions.

Determine system and software compatibility. Solve known problems.

VPO Supplementary Guide to MPE/iX Templates Managing Your Network with HP OpenView Network Node Manager VP Navigator Concepts and Configuration Guide Describes the message source templates that are available for MPE/iX managed nodes. This guide is not available for VPO on Solaris. Designed for administrators and operators. This manual describes the basic functionality of HP OpenView Network Node Manager, which is an embedded part of VPO. 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. PDF only

Hardcopy PDF

Hardcopy PDF

29

Additional VPO-related Products

This section provides an overview of the VPO-related manuals and their contents. Table 3
Manual

Additional VPO-related Manuals

Description Media

HP OpenView VantagePoint Operations for UNIX Developers Toolkit If you purchase the HP OpenView VantagePoint Operations for UNIX Developers Toolkit, you receive the full VPO documentation set, as well as the following manuals: VPO Application Integration Guide VPO Developers Reference Suggests several ways external applications can be integrated into VPO. Provides an overview of all available application programming interfaces (APIs). Hardcopy PDF 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 Users Guide Provides information for administrators who are responsible for installing, configuring, maintaining, and troubleshooting the VPO Sun Management Center integration. PDF only

30

Table 3
Manual

Additional VPO-related Manuals

Description Media

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

VPO Online Information

The following information is available online. Table 4 VPO Online Information
Description 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. 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. 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. 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.

Online Information HP OpenView VantagePoint Operations Administrators Guide to Online Information HP OpenView VantagePoint Operations Operators Guide to Online Information HP OpenView VantagePoint Operations Java GUI Online Information

HP OpenView VantagePoint Operations Man Pages

31

32

About VPO Online Help

This 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 GUI

Online 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 operators 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 GUI

The 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

About AIX Managed Nodes

Chapter 1

37

About AIX Managed Nodes In this Chapter

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

38

Chapter 1

About AIX Managed Nodes Installation Requirements

Installation Requirements
This 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 Administrators 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 Nodes Installation 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 Developers 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

40

Chapter 1

About AIX Managed Nodes Installing and De-installing Agents

Installing and De-installing Agents

This 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

About AIX Managed Nodes Installing and De-installing Agents

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.

42

Chapter 1

About AIX Managed Nodes Installing and De-installing Agents

NOTE

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

Chapter 1

43

About AIX Managed Nodes Installing and De-installing Agents

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 ADMINISTRATORs account Enter the name of the privileged user, specified during the initial configuration of the DCE server (for example, cell_admin).

44

Chapter 1

About AIX Managed Nodes Installing and De-installing Agents 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

About AIX Managed Nodes Installing and De-installing Agents

Installing Agents Automatically

To find out how to install the AIX agent automatically, see the VPO Administrators 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

46

Chapter 1

About AIX Managed Nodes Installing and De-installing Agents 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 Administrators 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

About AIX Managed Nodes Installing and De-installing Agents

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.

48

Chapter 1

About AIX Managed Nodes Installing and De-installing Agents 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: 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. 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

About AIX Managed Nodes Installing and De-installing Agents

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

50

Chapter 1

About AIX Managed Nodes Installing and De-installing Agents 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

About AIX Managed Nodes Installing and De-installing Agents 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.

52

Chapter 1

About AIX Managed Nodes Installing and De-installing Agents 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

About AIX Managed Nodes Installing and De-installing Agents 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 below ALIAS_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 ]; then INTERFACE=`/usr/sbin/cluster/utilities/clgetif -a $BOOT_IP` fi if [ $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

54

Chapter 1

About AIX Managed Nodes Installing and De-installing Agents 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. 3. Select the following: Cluster Configuration -> Cluster Resources -> Cluster Events 4. Add the set_alias script to the Known Cluster Events list. 5. Select the following: 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

About AIX Managed Nodes Installing and De-installing Agents

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.

56

Chapter 1

About AIX Managed Nodes Installing and De-installing Agents

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: Connection request 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

About AIX Managed Nodes Installing and De-installing Agents

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 Administrators 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).

58

Chapter 1

About AIX Managed Nodes About Preconfigured Elements

About Preconfigured Elements

This 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

About AIX Managed Nodes About Preconfigured Elements

Table 1-1 shows encapsulated logfiles and associated template used on AIX managed nodes. Table 1-1 Logfile /var/adm/aix_sulog /var/adm/audit log /tmp/syslog a /etc/security/failedlo gin (binary format) /var/adm/wtmp (binary format) /var/adm/ras/errors (binary format) Encapsulated Logfiles on AIX Managed Nodes Description Switch user logfile Auditing information logfile Syslog daemon logfile History of AIX failed logins History of logins, logouts, and data changes Messages generated by the AIX kernel Template Name Su (AIX) Audit Log (AIX) Syslog (AIX) Bad logs (AIX) Logins (AIX) 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 shows encapsulated logfiles and associated templates used on AIX HACMP managed nodes. Table 1-2 Logfile /var/adm/cluster.log Encapsulated Logfiles on AIX HACMP Managed Nodes Description HACMP cluster logs Template Name HACMP logfile (AIX)

60

Chapter 1

About AIX Managed Nodes About Preconfigured Elements

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

About AIX Managed Nodes About Preconfigured Elements

Types of Default Monitored Objects

Table 1-3 describes the default monitored objects used by VPO on AIX managed nodes. Table 1-3 Object Object Thresholds on the Managed Nodes Description Threshold Polling Interval (Minutes) 10 5 2 5 5 5 5

disk_util Inetd MailQueue Length proc_util sendmail swap_util Syslogd

Monitors disk space utilization on the root disk Number of executing instances of inetd (Internet Daemon) Length of the sendmail queue: number of unsent mail messages Monitors process table utilization Number of executing instances of sendmail Monitors SWAP utilization Checks whether syslogd is running

90% 0.5 30 75% 0.5 80% 0.5

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 Administrators Reference Volume I.

62

Chapter 1

About AIX Managed Nodes About Preconfigured Elements

Starting the SMIT User Interface

You can use VPO to start the System Management Interface Tool (SMIT) user interface on AIX systems: Command issued: Default user: Default password: smit root 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 Nodes Distributing Scripts and Programs

Distributing Scripts and Programs

For 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 Location /var/opt/OV/share/databases/OpC/mgd_node/customer\ /ibm/rs6000/aix/actions/*

Script/Program Automatic actions, operator-initiated actions, and scheduled actions Monitoring scripts and programs used by the monitoring agent and logfile encapsulator 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/monitor/*

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

64

Chapter 1

About AIX Managed Nodes Distributing Scripts and Programs

About Temporary Directories

Table 1-5 shows the temporary directories for distributed scripts and programs on the managed nodes. Table 1-5 Temporary Directories for Distributed Scripts and Programs on the Managed Nodes Operating System AIX Temporary Directory

Managed Node IBM RS/6000, Bull DPX/20

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

About Target Directories

Table 1-6 shows the target directories for distributed scripts and programs on the managed nodes. Table 1-6 Target Directories for Distributed Scripts and Programs on the Managed Nodes Operating System AIX Target Directory Access Rights

Managed Node IBM RS/6000, Bull DPX/20

/var/lpp/OV/OpC/actions /var/lpp/OV/OpC/cmds /var/lpp/OV/OpC/monitor

rwxr-xr-x (owner: root) rwxr-xr-x (owner: root) rwxr-xr-x (owner: root)

Chapter 1

65

About AIX Managed Nodes Organization 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 /usr/lpp/ OV contrib /var/lpp/OV

databases

conf

tmp

log OpC

bin OpC

OpC BBC OpC nls <lang> install OpC lib include utils OpC bin conf

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

Key:

and

monitor

cmds

actions

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

66

Chapter 1

About AIX Managed Nodes Organization 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 Nodes Types 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
Item DCE Library Libraries linked to the VPO library.

Libraries for the VPO Managed Nodes

VPO A.05.xx libopc_r.a /usr/lpp/OV/lib/lib nsp.a /usr/lib/libdce.a /usr/lib/libiconv.a VPO A.06.xx libopc_r.a /usr/lpp/OV/lib/lib nsp.a /usr/lpp/OV/lib/lib opcas.a /usr/lib/libdce.a /usr/lib/libiconv.a VPO A.07.xx libopc_r.a /usr/lpp/OV/lib/lib nsp.a /usr/lpp/OV/lib/lib opcas.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/libdcepthr eads.a /usr/lib/libpthread s_compat.a

Link and compile options

-D_CMA_NOWRAPPERS_ -lopc_r -lpthreads -lc_r 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.

-D_CMA_NOWRAPPERS_ -lopc_r -lpthreads -lc_r N/A

-D_CMA_NOWRAPPERS_ -lopc_r -lpthreads -lc_r N/A

Description

68

Chapter 1

About AIX Managed Nodes Types of Libraries Table 1-7

Item NCS Library Libraries linked to the VPO library.

Libraries for the VPO Managed Nodes

VPO A.05.xx libopc.a /usr/lpp/OV/lib/lib nsp.a /usr/lib/libnck.a /usr/lib/iconv.a VPO A.06.xx libopc.a /usr/lpp/OV/lib/lib nsp.a /usr/lpp/OV/lib/lib opcas.a /usr/lib/libnck.a /usr/lib/iconv.a VPO A.07.xx libopc.a /usr/lpp/OV/lib/lib nsp.a /usr/lpp/OV/lib/lib opcas.a /usr/lib/libdl.a /usr/lib/libiconv.a /usr/lib/libc.a or /usr/ccs/lib/libc.a

Link and compile options Description

-lopc

-lopc

-lopc

N/A

N/A

N/A

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

Chapter 1

69

About AIX Managed Nodes Types of Libraries

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

70

Chapter 1

About HP-UX Managed Nodes

Chapter 2

71

About HP-UX Managed Nodes In this Chapter

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

72

Chapter 2

About HP-UX Managed Nodes Installation Requirements

Installation Requirements
This 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) Additional Swap Space 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

About HP-UX Managed Nodes Installation Requirements

Software Requirements for HP-UX 10.x

Before installing VPO, make sure the following software is installed on HP-UX 10.x managed nodes: Operating System 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 System Parameters For a list of kernel parameters, see the VPO Administrators 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 74 Chapter 2

About HP-UX Managed Nodes Installation Requirements

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 For a list of operating system versions supported by VPO, see the VPO Installation Guide for the Management Server. 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 PHSS_23441 HP aC++ -AA runtime libraries (aCC A.03.30) s700_800 11.11 ld(1) and linker tools cumulative patch

System Parameters For a list of kernel parameters, see the VPO Administrators 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

About HP-UX Managed Nodes Installation Requirements

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

76

Chapter 2

About HP-UX Managed Nodes Installing and De-installing Agents

Installing and De-installing Agents

This section describes how to install and de-install HP-UX 10.x/11.x managed nodes.

Methods for Installing Agents

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.

Tips for Installing Agents

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 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 the name of the management server with the nslookup command. Chapter 2 77

About HP-UX Managed Nodes Installing and De-installing Agents

Installing Agents with Standard Installation

Figure 2-1 shows the standard VPO installation method. Figure 2-1 Standard VPO Agent Installation Method
VPO Management Server VPO Node 1 VPO Agent Packages VPO Node 2 Wide Area Network (WAN) Local Area Network (LAN)

Key: Data Transmission

VPO Node N

For general administration instructions, see the VPO Administrators Reference Volume I. If errors occur during the installation, check the local installation logfiles: /var/adm/sw/swagent.log /var/adm/sw/swinstall.log

78

Chapter 2

About HP-UX Managed Nodes Installing and De-installing Agents

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
VPO Management Server VPO Agent Packages (1) Wide Area Network (WAN) Local Area Network (LAN) SD Depot (VPO Node 1) VPO Agent Packages (2) Key: Data Transmission (1) (2) Manual transfer of packages Trigger remote installation VPO Node 2 VPO Node N

Chapter 2

79

About HP-UX Managed Nodes Installing and De-installing Agents 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]/

80

Chapter 2

About HP-UX Managed Nodes Installing and De-installing Agents

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

About HP-UX Managed Nodes Installing and De-installing Agents 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: Standard Installation See Installing Agents with Standard Installation on page 78. SD-UX Installation See Installing Agents with SD-UX on page 79.

82

Chapter 2

About HP-UX Managed Nodes Installing and De-installing Agents

Installing Agents Manually

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

About HP-UX Managed Nodes Installing and De-installing Agents 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: 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: 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]/ 2. Install the Agent. Start the agent installation script by entering: /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.

84

Chapter 2

About HP-UX Managed Nodes Installing and De-installing Agents 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

About HP-UX Managed Nodes Installing and De-installing Agents

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: 1. Add the pre-installed nodes to the VPO Node Bank window. Use the following 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. Open the Install/Update VPO Software and Configuration window. Use the following menu sequence: Actions-> Agents-> Install / Update SW & Config.

86

Chapter 2

About HP-UX Managed Nodes Installing and De-installing Agents

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

About HP-UX Managed Nodes Installing and De-installing Agents 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. 2. Add the pre-installed nodes to the VPO Node Bank window. Use the following menu sequence: Actions-> Node-> Add. 3. Add the node to a VPO node group. Drag and drop the node onto a node group in the VPO Node Group Bank window. 4. Activate the node. Enter the following: /opt/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 /sbin/init.d/opcagt 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 Administrators Reference Volume I and the man page opcactivate(1M).

88

Chapter 2

About HP-UX Managed Nodes Installing and De-installing Agents

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: /opt/OV/bin/OpC/opcsw -installed <node> 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-

De-installing Agents
You can de-install agents from HP-UX managed nodes automatically or manually. De-installing Agents Automatically To find out how to de-install agents automatically, see the VPO Administrators 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: 1. Stop all VPO agents running on the managed node. 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 Nodes About Preconfigured Elements

About Preconfigured Elements

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

Types of Preconfigured Template Groups

VPO uses the following preconfigured template groups: 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 Name opcmsg(1|3) opcmsg Message Templates on HP-UX Managed Nodes Description Default interception of messages submitted by opcmsg(1), opcagtmsg_send(3), and opcmsg(3).

90

Chapter 2

About HP-UX Managed Nodes About Preconfigured Elements

Types of Default Logfile Templates

Table 2-2 shows encapsulated logfiles and associated template used on HP-UX managed nodes. Table 2-2 Logfile /var/adm/sulog /var/adm/cron/log /var/adm/syslog\ /syslog.log /etc/rc.log /var/adm/btmp (binary format) /var/adm/wtmp (binary format) /var/opt/OV/log/OpC/\ dmesg.out /var/adm/syslog/\ mail.log /var/adm/syslog/\ syslog.log Encapsulated Logfiles on HP-UX Managed Nodes Description su(1) switch user logfile cron(1M) clock daemon logfile syslogd(1M) syslog daemon logfile Messages during system boot up History of bad login attempts History of logins, logouts, and data changes Messages generated by the HP- UX 10.x kernel sendmail(1) logfile Fetch messages from MC/ServiceGuard and forward to APM Name Su (10.x/11.x HP-UX) Cron (10.x/11.x HP-UX) Syslog (10.x/11.x HP-UX) Boot (10.x/11.x HP-UX) Bad Logs (10.x/11.x HP-UX) Logins (10.x/11.x HP-UX) Kernel Logs (10.x/11.x HP-UX) Mailqueue (10.x/11.x HP-UX) Syslog (ServiceGuard)

Chapter 2

91

About HP-UX Managed Nodes About Preconfigured Elements

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.

NOTE

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

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.

92

Chapter 2

About HP-UX Managed Nodes About Preconfigured Elements 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

About HP-UX Managed Nodes About Preconfigured Elements 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>

Types of Default Monitored Objects

Table 2-3 describes the default monitored objects used by VPO on HP-UX managed nodes. Table 2-3 Object Object Thresholds on the HP-UX Managed Nodes Description Threshold Polling Interval (Minutes) 2 10 5 2 5 5 5 5

cpu_util disk_util Inetd MailQueue Length proc_util sendmail swap_util Syslogd

Monitors CPU utilization. Requires the sar program. Monitors disk space utilization on the root disk. Number of executing instances of inetd (Internet Daemon). Length of the sendmail queue. Number of unsent mail messages. Monitors process table utilization. Number of executing instances of sendmail. Monitors SWAP utilization. Checks whether syslogd is running.

95% 90% 0.5 30 75% 0.5 80% 0.5

94

Chapter 2

About HP-UX Managed Nodes About Preconfigured Elements

Types of Default Applications

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 Administrators 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 Nodes Distributing Scripts and Programs

Distributing Scripts and Programs

For 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

Location of User Scripts and Programs

Table 2-4 shows the location of user scripts and programs provided on the management server. Table 2-4 Location of User Scripts and Programs on the Management Server Location /var/opt/OV/share/databases/OpC/mgd_node/customer\ /<arch>/actions/*

Script/Program Automatic actions, operator-initiated actions, and scheduled actions Monitoring scripts and programs used by the monitoring agent and the logfile encapsulator Scripts and programs called through command broadcast or started from the Application Desktop

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

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

96

Chapter 2

About HP-UX Managed Nodes Distributing Scripts and Programs

About Temporary Directories

Table 2-5 shows the temporary directories for distributed scripts and programs on the managed nodes. Table 2-5 Temporary Directories for Distributed Scripts and Programs on the Managed Nodes Operating System HP-UX 10.x HP-UX 11.x Temporary Directory

Managed Node HP 9000/[78]00

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

About Target Directories

Table 2-6 shows the target directories for distributed scripts and programs on the managed nodes. Table 2-6 Target Directories for Distributed Scripts and Programs on the Managed Nodes Operating System HP-UX 10.x HP-UX 11.x Target Directory Access Rights

Managed Node HP 9000/700 HP 9000/800

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

rwxr r (owner: root) rwxr-xr-x (owner: root) rwxr r (owner: root)

Chapter 2

97

About HP-UX Managed Nodes Distributing Scripts and Programs

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

98

Chapter 2

About HP-UX Managed Nodes Organization of Managed Nodes

Organization of Managed Nodes

Figure 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 /opt/OV /var/opt/OV

lib nls

bin OpC

contrib OpC

include

databases conf OpC BBC

tmp OpC bin conf

log OpC

bin OpC

<lang>

install

utils

Key:

monitor

cmds

actions

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.

Chapter 2

99

About HP-UX Managed Nodes Organization of Managed Nodes

Location of Files
On HP-UX 10.x and 11.x managed nodes, files are located as follows: Process-related Files /var/opt/OV/tmp/OpC Agent Configuration Files /var/opt/OV/conf/OpC

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

100

Chapter 2

About HP-UX Managed Nodes Organization of Managed Nodes

Types of System Resources

VPO applies changes in the following system resource files: /etc/passwd /etc/group /sbin/init.d/opcagt /etc/rc.config.d/opcagt /sbin/rc2.d Default VPO operator entry. Default VPO operator group entry. VPO startup and shutdown script. VPO startup and shutdown configuration script Creates link K059opcagt to /sbin/init.d/opcagt is created. This link determines when opcagt is killed during the shutdown sequence. Adds service ito-e-gui for the Java-based operator GUI. When requested, starts the process /opt/OV/bin/OpC/opcuiwww. 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.

/etc/services /etc/inetd.conf /var/adm/inetd.sec

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 Nodes Types of Libraries

Types of Libraries
Table 2-7 describes the managed node libraries for VPO A.05.xx, A.06.xx, and A.7.xx. Table 2-7
Item Library Libraries linked to the VPO library.

Libraries for the VPO Managed Nodes

VPO A.05.xx libopc_r.sl /usr/lib/libdcekt.1 /usr/lib/libpthread .1 /usr/lib/libnsl.1 /usr/lib/libc.1 VPO A.06.xx libopc_r.sl /usr/lib/libdcekt.1 /usr/lib/libpthread .1 /opt/OV/lib/libnsp. sl /opt/OV/lib/libas. sl /usr/lib/libnsl.1 VPO A.07.xx libopc_r.sl /usr/lib/libdcekt.1 /usr/lib/libpthread .1 /usr/lib/libnsl.1

HP-UX 11.x

/usr/lib/libc.1 Link and compile options -lopc_r -lopc_r -lopc_r, -lnsp DCE

102

Chapter 2

About HP-UX Managed Nodes Types of Libraries Table 2-7

Item Description

Libraries for the VPO Managed Nodes

VPO A.05.xx 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. VPO A.06.xx N/A VPO A.07.xx N/A

HP-UX 11.x

DCE

Chapter 2

103

About HP-UX Managed Nodes Types of Libraries Table 2-7

Item Library

Libraries for the VPO Managed Nodes

VPO A.05.xx libopc_r.sl (libopc.sl > libopc_r.sl) VPO A.06.xx libopc_r.sl VPO A.07.xx libopc_r.sl

Libraries linked to the VPO library.

/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

Link and compile options HP-UX 10.x Description

-lopc_r

-lopc_r

-lopc_r, -lnsp

Last version with the compatibility link. Linking of libdce.sl and libc_r.sl is not recommended.

N/A

N/A

DCE

104

Chapter 2

About HP-UX Managed Nodes Types of Libraries

About the Include File

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: /opt/OV/OpC/examples/progs The build an executable with correct compile and link options, use the following makefiles: Makef.hpux10 Makef.hpux11 For more information about the managed node makefile, see the ReadMe file: /opt/OV/OpC/examples/progs/README

Chapter 2

105

About HP-UX Managed Nodes Monitoring Events

Monitoring Events
The 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.

106

Chapter 2

About HP-UX Managed Nodes Monitoring Events 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

About HP-UX Managed Nodes Monitoring Events 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

108

Chapter 2

About HP-UX Managed Nodes Monitoring Events

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

About HP-UX Managed Nodes Monitoring Events 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).

110

Chapter 2

About HP-UX Managed Nodes Monitoring Events 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 -t -d <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 Recursively traverses class and instance tree. Sets timeout to <secs> seconds. Default is 30 seconds. Displays on stdout.

Chapter 2

111

About HP-UX Managed Nodes Monitoring Events

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

112

Chapter 2

About HP-UX Managed Nodes High Availability Support on HP-UX

High Availability Support on HP-UX

VPO 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 Administrators Reference Volume II.

Chapter 2

113

About HP-UX Managed Nodes High Availability Support on HP-UX

114

Chapter 2

About Linux Managed Nodes

Chapter 3

115

About Linux Managed Nodes In this Chapter

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

116

Chapter 3

About Linux Managed Nodes Installation Requirements

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

Hardware Requirements
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). Additional Swap Space None Additional RAM 4 MB

Chapter 3

117

About Linux Managed Nodes Installation Requirements

Software Requirements
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

118

Chapter 3

About Linux Managed Nodes Installation Requirements

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

About Linux Managed Nodes Installation Requirements

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
Operating System and Version RedHat 6.2 Kernel glibc

Language

English

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 2.1.3

SuSE 6.4

2.2.x x can be 14

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

120

Chapter 3

About Linux Managed Nodes Installation Requirements Table 3-1 Supported Operating System and Kernel Versions
Operating System and Version RedHat 6.1J Kernel glibc

Language

Japanese

2.2.x x can be 12

2.1.2 2.1.3 2.1.3

RedHat 6.2J

2.2.x x can be 14

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 2.1.3

TurboLinux 6.1J

2.2.x x can be 15

Chapter 3

121

About Linux Managed Nodes Installing and De-installing Agents

Installing and De-installing Agents

This section describes how to install and de-install Linux managed nodes.

Tips for Installing Agents

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 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 the name of the management server with the nslookup command.

122

Chapter 3

About Linux Managed Nodes Installing and De-installing Agents

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

About Linux Managed Nodes Installing and De-installing Agents Installing Agents with Standard Installation For general installation instructions, see the VPO Administrators 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.

124

Chapter 3

About Linux Managed Nodes Installing and De-installing Agents

2. 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: 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

About Linux Managed Nodes Installing and De-installing Agents

4. Install the VPO agent software. On the Linux managed node, do the following: a. Install the Agent. Start the agent installation script by entering: /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. 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 Administrators Reference Volume I and the man page opcactivate(1M). If Errors Occur During Installation If errors occur during the installation, check the local installation logfile: /tmp/rpm.log This file is empty if the installation had no errors.

126

Chapter 3

About Linux Managed Nodes Installing and De-installing Agents

De-installing Agents
You can de-install agents from Linux managed nodes automatically or manually. De-installing Agents Automatically For general de-installation instructions, see the VPO Administrators Reference Volume I. For standard de-installation, rhosts equivalency must be established. To De-install an Agent Manually To de-install an agent manually, follow these steps: 1. Stop all VPO agents running on the managed node. 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 Nodes About Preconfigured Elements

About Preconfigured Elements

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

Preconfigured Template Groups

VPO uses the following preconfigured template groups: Linux (RedHat)

NOTE

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

Types of Default Logfile Templates

Table 3-2 shows encapsulated logfiles and associated template used on Linux managed nodes. Table 3-2 Logfile /var/log/cron /var/log/messages Encapsulated Logfiles on Linux Managed Nodes Description Cron logfile Failed logins and su Template Name Cron (RedHat Linux and TurboLinux) Messages (RedHat Linux, SuSEa and TurboLinux) Logins (Linux) Kernel messages (SuSE)

/var/log/wtmp /var/log/warn

History of logins Kernel messages

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

128

Chapter 3

About Linux Managed Nodes About Preconfigured Elements

No SNMP Trap and Event Interception

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

Types of Default Monitored Objects

Table 3-3 describes the default monitored objects used by VPO on Linux managed nodes. Table 3-3 Object Object Thresholds on the Managed Nodes Description Threshold Polling Interval (Minutes) 2 10 5 2 5 5 5

cpu_util disk_util Inetd MailQueue Length Sendmail swap_util Syslogd

Monitors CPU utilization. Monitors disk space utilization on root disk. Checks if Inetd is running. Determine length of sendmail mail queue (unsent email). Checks if sendmail is running. Monitors SWAP utilization. Checks whether syslogd is running.

95% 90% 0.5 30.0 0.5 80% 0.5

Types of Default Applications

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

Chapter 3

129

About Linux Managed Nodes Distributing Scripts and Programs

Distributing Scripts and Programs

For 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

130

Chapter 3

About Linux Managed Nodes Distributing Scripts and Programs

Location of User Scripts and Programs

Table 3-4 shows the location of user scripts and programs provided on the management server. Table 3-4 Location of User Scripts and Programs on the Management Server Location 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/* Monitoring scripts and programs used by the monitoring agent and the logfile encapsulator 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/monitor/* Linux RedHat 7.1, SuSE 7.1and 7.2: /var/opt/OV/share/databases/OpC/mgd_node/customer \ /linux/intel/linux24/monitor/* Scripts and programs called through command broadcast or started from the Application Desktop 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/cmds/* Linux RedHat 7.1, SuSE 7.1and 7.2: /var/opt/OV/share/databases/OpC/mgd_node/customer \ /linux/intel/linux24/cmds/*

Script/Program Automatic actions, operator-initiated actions, and scheduled actions

Chapter 3

131

About Linux Managed Nodes Distributing Scripts and Programs

About Temporary Directories

Table 3-4 shows the temporary directories for distributed scripts and programs on the managed nodes. Table 3-5 Temporary Directories for Distributed Scripts and Programs on Managed Nodes Operating System Linux Temporary Directory

Managed Node Intel-based PCs

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

About Target Directories

Table 3-6 shows the target directories for distributed scripts and programs on the managed nodes. Table 3-6 Target Directories for Distributed Scripts and Programs on the Managed Nodes Operating System Linux Target Directory Access Rights

Managed Node Intel-based PCs

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

rwxr-xr-x (owner: root) rwxr-xr-x (owner: root) rwxr-xr-x (owner: root)

132

Chapter 3

About Linux Managed Nodes Organization 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 / opt OV

var opt OV

contrib bin OpC

lib

include locale databases conf bin log tmp

OpC

C OpC BBC OpC OpC OpC B

install

utils

LC_MESSAGES

bin B

monitor

cmds

actions

Chapter 3

133

About Linux Managed Nodes Organization of Managed Nodes

Location of Files
On Linux managed nodes, files are located as follows: Process-related Files /var/opt/OV/tmp/OpC Agent Configuration Files /var/opt/OV/conf/OpC

About the Default VPO Operator

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 Group-ID Description 777 (if still available) or next possible free number 77 (if still available) or next possible free number Default VPO operator

Home Directory /home/opc_op Login Shell /bin/sh (POSIX shell)

134

Chapter 3

About Linux Managed Nodes Organization of Managed Nodes About Default VPO Operator Group Entries The default VPO operator group appears in the following directory on Linux managed nodes: /etc/group Fields include the following: Group Name opcgrp

Encrypted Password Empty Group-ID Users Description 77 or higher opc_op Default VPO operator group

Chapter 3

135

About Linux Managed Nodes Types of Libraries

Types of Libraries
Table 3-7 describes the managed node libraries for VPO A.05.xx, A.06.xx, and A.07.xx. Table 3-7 Libraries for the VPO Managed Nodes
VPO Version DCE Library Libraries linked to the VPO library. VPO A.05.xx libopc_r.so RedHat 5.x: libdcerpc.so libdcethread.so libpthread.so libuuid.so libcrypt.so.1 libstdc++.so.2.8 RedHat 6.x, 7.x, SuSE 6.x, 7.x and TurboLinux 6.x: libdcerpc.so libdcethread.so libpthread.so libuuid.so libcrypt.so.1 libstdc++-libc6.1-1. so.2 VPO A.06.xx libopc_r.so RedHat 5.x: libdcerpc.so libdcethread.so libpthread.so libuuid.so libcrypt.so.1 libstdc++.so.2.8 libopcas.so RedHat 6.x, 7.x, SuSE 6.x, 7.x and TurboLinux 6.x: libdcerpc.so libdcethread.so libpthread.so libuuid.so libcrypt.so.1 libstdc++-libc6.1 -1.so.2 libopcas.so VPO A.07.xx libopc_r.so RedHat 5.x: libdcerpc.so libdcethread.so libpthread.so libuuid.so libcrypt.so.1 libstdc++.so.2.8 libopcas.so RedHat 6.x, 7.x, SuSE 6.x, 7.x and TurboLinux 6.x: libdcerpc.so libdcethread.so libpthread.so libuuid.so libcrypt.so.1 libstdc++-libc6.1 -1.so.2 libopcas.so

Link and compile options Description

-D_REENTRANT -lopc_r -lnsp -lpthread The LD_LIBRARY_PATH variable has to be exported or ldconfig has to be executed.

-D_REENTRANT -lopc_r -lnsp -lpthread The LD_LIBRARY_PATH variable has to be exported or ldconfig has to be executed.

-D_REENTRANT -lopc_r -lnsp -lpthread The LD_LIBRARY_PATH variable has to be exported or ldconfig has to be executed.

136

Chapter 3

About Linux Managed Nodes Types of Libraries

About the Include File

On an Intel 486 or higher platform with Linux managed nodes, use the include file: /opt/OV/include/opcapi.h 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

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.linux For more information about the managed node makefile, see the ReadMe file: /opt/OV/OpC/examples/progs/README

Chapter 3

137

About Linux Managed Nodes Types of Libraries

138

Chapter 3

About MPE/iX Managed Nodes

Chapter 4

139

About MPE/iX Managed Nodes In this Chapter

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

140

Chapter 4

About MPE/iX Managed Nodes Installation Requirements

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

Hardware Requirements
Before installing VPO, make sure the MPE/iX systems you select as managed nodes meet the following hardware requirements: Disk Space 10 MB (about 20 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 MPE/iX managed nodes: Operating System For a list of operating system versions supported by VPO, see the VPO Installation Guide for the Management Server. DCE RPC CE RPC 1.0.2 or DCE RPC 1.2.1 NS Services

Chapter 4

141

About MPE/iX Managed Nodes Installation 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
MPE/iX 6.0 Patch ID MPEKXE5 ITOED07A 6.5 FRILXX7A

Required MPE/iX Patches

Description Adds routines to the system SL.PUB.SYS that the console interceptor requires to operate. Provides routines to the XL.PUB.SYS to allow the

VPO agent to call various NCS routines.

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 ITOED07B 7.0 FRILXX7A This patch is required if DCE is installed that has to be purchased separately. Provides routines to the XL.PUB.SYS to allow the

VPO agent to call various NCS routines.

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 ITOED07C This patch is required if DCE is installed that has to be purchased separately. Provides routines to the XL.PUB.SYS to allow the

VPO agent to call various NCS routines.

142

Chapter 4

About MPE/iX Managed Nodes Installing and De-installing Agents

Installing and De-installing Agents

This section describes how to install and de-install MPE/iX managed nodes.

Tips for Installing Agents

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

About MPE/iX Managed Nodes Installing and De-installing Agents About the Default VPO Operator 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 Administrators Reference Volume I.

144

Chapter 4

About MPE/iX Managed Nodes Installing and De-installing Agents 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 Administrators 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 MPE/iX Managed Nodes Installing and De-installing Agents 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

146

Chapter 4

About MPE/iX Managed Nodes Installing and De-installing Agents

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

About MPE/iX Managed Nodes Installing and De-installing Agents

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.

148

Chapter 4

About MPE/iX Managed Nodes Installing and De-installing Agents 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 Administrators 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

De-installing Agents
For general de-installation instructions, see the VPO Administrators Reference Volume I.

Chapter 4

149

About MPE/iX Managed Nodes About Preconfigured Elements

About Preconfigured Elements

MPE/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.

Types of Preconfigured Template Groups

Table 4-2 describes the default template groups available for MPE/iX managed nodes. Table 4-2 Template Group MPE/iX MPE/iX Database monitoring MPE/iX Network monitoring MPE/iX OS monitoring MPE/iX Template Groups Description Templates for MPE/iX Templates for Image/SQL databases Templates for Network Interfaces and Services Templates for monitoring MPE/iX

Types of Default Logfile Templates

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.

150

Chapter 4

About MPE/iX Managed Nodes About Preconfigured Elements

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. Table 4-3 Default Message Mapping on MPE/iX Managed Nodes MPE/iX Classification Database DTC Hardware Jobs Logging MPE/iX Network Performance Printer Security Spooler Storage VPO Message Group Misc Misc Hardware Job Misc OS Network Performance Output Security Output Backup

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 Chapter 4 151

About MPE/iX Managed Nodes About Preconfigured Elements Mapping Messages to VPO Security Levels Table 4-4 on page 152 shows how MPE/iX messages are mapped to the VPO severity levels. Table 4-4 MPE/iX and VPO Message Mapping Severity MPE/iX Severity Level 0 1 2 3 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.) 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. 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. VPO Severity Level Normal Normal Warning Critical

cc

aaa

152

Chapter 4

About MPE/iX Managed Nodes About Preconfigured Elements Table 4-5 shows how NMEV markers are mapped in VPO. Table 4-5 MPE/iX Application ID 052 053 194 195 196 198 200 206 211 212 213 214 215 216 217 218 220 221 222 224 225 NMEV Marker Mapping VPO Message Group Performance Database Network Network Network Network Output OS Output Output Output Storage Storage OS Storage Job OS Logging OS Logging Hardware Application/Operating System Subsystem Laser/RX Allbase/SQL Public Networking Network-OSI Network-NS Network-SNA Ciper Devices I/O Services Native Mode Spooler Page Printer Device Manager Printer,Tape,Spool Software Resiliency Threshold Manager Store/Restore Jobs/Sessions Process Mgr System Logging Transaction Mgmt User Logging SPU Switchover

Chapter 4

153

About MPE/iX Managed Nodes About Preconfigured Elements Table 4-5 MPE/iX Application ID 226 227 228 229 230 231 232 233 234 235 236 237 238 239 310 NMEV Marker Mapping VPO Message Group OS OS Output Hardware OS OS OS Storage DTC DTC Storage Security OS Hardware Misc Application/Operating System Subsystem Reply Info Table System Manager High End Printer Diagnostic-System Command Interpreter System & Error Mgmt Label Management Magneto-Optic Lib Terminal I/O DCC Surrogate Labeled Tape MPE/iX Security Native Language UPS Monitoring Console Event

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.

154

Chapter 4

About MPE/iX Managed Nodes About Preconfigured Elements

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

About MPE/iX Managed Nodes About Preconfigured Elements

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: CONSDESC.COMMANDS.OVOPC

NOTE

You must restart the MPE/iX console interceptor on your MPE/iX managed node to activate the changes in the following file: CONSDESC.COMMANDS.OVOPC To restart the MPE/iX console interceptor on your MPE/iX managed node, enter the following: /opt/OV/bin/OpC/opcragt -start

156

Chapter 4

About MPE/iX Managed Nodes About Preconfigured Elements

No SNMP Trap and Event Interception

The VPO event interceptor is not supported on MPE/iX managed nodes.

Types of Default Monitored Objects

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

About MPE/iX Managed Nodes About Preconfigured Elements

Types of Default Applications

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

158

Chapter 4

About MPE/iX Managed Nodes About Preconfigured Elements 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 MPE/iX Managed Nodes About Preconfigured Elements 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 Administrators Reference Volume II. Default User MGR.OVOPR

160

Chapter 4

About MPE/iX Managed Nodes Distributing Scripts and Programs

Distributing Scripts and Programs

For MPE/ix managed nodes, the platform selector and architecture identifier is the following: hp/s900/mpe-ix

Location of User Scripts and Programs

Table 4-6 shows the location of user scripts and programs provided on the management server. Table 4-6 Location of User Scripts and Programs on the Management Server Location /var/opt/OV/share/databases/OpC/mgd_node/customer\ /hp/s900/mpe-ix/actions/*

Script/Program Automatic actions, operator-initiated actions, and scheduled actions Monitoring scripts and programs used by the monitoring agent and the logfile encapsulator Scripts and programs called through command broadcast or started from the Application Desktop

/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 Nodes Distributing Scripts and Programs

About Temporary Directories

Table 4-7 shows the temporary directories for distributed scripts and programs on the managed nodes. Table 4-7 Temporary Directories for Distributed Scripts and Programs on the Managed Nodes Operating System MPE/iX Temporary Directory

Managed Node HP 3000/900

TMPACT.OVOPC TMPCMDS.OVOPC TMPMON.OVOPC .ZOVOPC (for compressed files)

About Target Directories

Table 4-8 shows the target directories for distributed scripts and programs on the managed nodes. Table 4-8 Target Directories for Distributed Scripts and Programs on Managed Nodes OS MPE/iX Directory Access Rights R,X,L,A,W,S:AC R,X:ANY;L,A,W,S: AC R,X,L,A,W,S:AC

Managed Node HP 3000/900

ACTIONS.OVOPC cap=BA,IA,PM,MR,DS,PH COMMANDS.OVOPC cap=BA,IA,PM,MR,DS,PH MONITOR.OVOPC cap=BA,IA,PM,MR,DS,PH

162

Chapter 4

About MPE/iX Managed Nodes Organization 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 OVOPC ACTIONS BIN COMMANDS CONF H LIB RBIN Z TMPMON TMPCONF TMPCMDS TMPACT TMP

LOG

PUB MONITOR MSG

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: Process-related Files TMP.OVOPC Agent Configuration Files CONF.OVOPC

About the Default VPO Operator

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.

Chapter 4

163

About MPE/iX Managed Nodes Organization of Managed Nodes

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 Hostname hpbbli hpsgmx18.sgp.hp.com ARPA to NS Node Name Mapping NS Node Name smarty hpsgmx18.sgp.hpcom Comment Different node names but same domain Same node names, but managed node belongs to different domain than management server Node names and domains differ

topaz.sgp.hp.com

nstopaz.mis.hpsg

164

Chapter 4

About MPE/iX Managed Nodes Organization of Managed Nodes 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

About MPE/iX Managed Nodes Organization of Managed Nodes 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.

166

Chapter 4

About MPE/iX Managed Nodes Organization of Managed Nodes 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 Nodes Types of Libraries

Types of Libraries
Table 4-10 describes the managed node libraries for VPO A.05.xx, A.06.xx, and A.07.xx. Table 4-10
Item DCE Library Libraries linked to the VPO library Link and compile options

Libraries for the VPO Managed Nodes

VPO A.05.xx libapixl.lib.ovopc N/A VPO A.06.xx libapixl.lib.ovopc N/A VPO A.07.xx libapixl.lib.ovopc N/A

info=Ih link cap=pm,ia,ba,mr,ds; & rl=libcinit.lib.sys ;& xl=opcapixl.lib

info=Ih link cap=pm,ia,ba,mr,ds; & rl=libcinit.lib.sys ;& xl=opcapixl.lib N/A

info=Ih link cap=pm,ia,ba,mr,ds; & rl=libcinit.lib.sys ;& xl=opcapixl.lib N/A

Description

N/A

About the Include File

On a HP 3000/900 platform running MPE/iX managed nodes, use the following include file: OPCAPI.H.OVOPC

168

Chapter 4

About MPE/iX Managed Nodes Types of Libraries

About the Makefiles

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.mpe-ix For more information about the managed node makefile, see the ReadMe file: /opt/OV/OpC/examples/progs/README

Chapter 4

169

About MPE/iX Managed Nodes Types of Libraries

170

Chapter 4

About Novell NetWare Managed Nodes

Chapter 5

171

About Novell NetWare Managed Nodes In this Chapter

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

172

Chapter 5

About Novell NetWare Managed Nodes Installation Requirements

Installation Requirements
This section explains VPO hardware and software requirements for Novell NetWare managed nodes.

Hardware Requirements
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

About Novell NetWare Managed Nodes Installation Requirements

Software Requirements for the Managed Nodes

Before installing VPO, make sure the following software is installed on Novell NetWare managed nodes: Operating System For a list of operating system versions supported by VPO, see the VPO Installation Guide for the Management Server. 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.

174

Chapter 5

About Novell NetWare Managed Nodes Installation Requirements

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 Nodes Installing and De-installing Agents

Installing and De-installing Agents

This section describes how to install and de-install Novell NetWare managed nodes.

Tips for Installing Agents

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.

176

Chapter 5

About Novell NetWare Managed Nodes Installing and De-installing Agents

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

About Novell NetWare Managed Nodes Installing and De-installing Agents 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.

178

Chapter 5

About Novell NetWare Managed Nodes Installing and De-installing Agents

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

About Novell NetWare Managed Nodes Installing and De-installing Agents

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 VPO Management Server

NetWare Depot Server running Windows 95/98/NT or 2000

1. Admin GUI 1st part: - add NetWare managed nodes - run Actions->Install for all managed nodes; select Agent Software (ping only) 5. Admin GUI 2nd part: (template distribution): - run Actions->Assign Templates for all managed nodes - run Actions->Install for all managed nodes; select every option except Agent Software

2. Transfer vpodepot.exe to NW depot server (floppy or FTP)

3. Run vpodepot.exe: prepare NetWare agent depot server 4. Run vpoinst.exe: install/de-install agent software on managed nodes

NetWare server 1

NetWare server 2

NetWare server N

180

Chapter 5

About Novell NetWare Managed Nodes Installing and De-installing Agents

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

About Novell NetWare Managed Nodes Installing and De-installing Agents

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

vpoinst.exe

VPONovellAgent

etc

opt

var opt

system

OV OV bin include lib bin conf log tmp

182

Chapter 5

About Novell NetWare Managed Nodes Installing and De-installing Agents

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. 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 Next>> Immediately exits the procedure. Proceeds to the next step.

Deinstall

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

About Novell NetWare Managed Nodes Installing and De-installing Agents

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. Adds all nodes to the list. 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.

Add all <<Remove

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.

184

Chapter 5

About Novell NetWare Managed Nodes Installing and De-installing Agents

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

About Novell NetWare Managed Nodes Installing and De-installing Agents

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

Removing Older Agents

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> In this command, <VPO_version> is the version of VPO that supports this agent platform (for example, A.07.00).

186

Chapter 5

About Novell NetWare Managed Nodes About Preconfigured Elements

About Preconfigured Elements

This 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

Types of Default Logfile Templates

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 Logfile sys:\system\abend.log Encapsulated Logfiles on Novell NetWare Managed Nodes Description Abend logfile on NetWare, which is updated when an abend occurs Template Name Abend log

Chapter 5

187

About Novell NetWare Managed Nodes About Preconfigured Elements

About SNMP Trap and Event Interception

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.

NOTE

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

No Default Monitored Objects

No preconfigured monitors are available for Novell NetWare managed nodes.

188

Chapter 5

About Novell NetWare Managed Nodes About Preconfigured Elements

Types of Default Applications

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 servers 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 Novell NetWare Managed Nodes About Preconfigured Elements 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.

190

Chapter 5

About Novell NetWare Managed Nodes About Preconfigured Elements 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 servers 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 administrators rights) can execute these application on the NetWare server.

Chapter 5

191

About Novell NetWare Managed Nodes About Preconfigured Elements 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. 192 Chapter 5

About Novell NetWare Managed Nodes About Preconfigured Elements About the NetWare Tools Window From the In NetWare Tools window, the user opc_op (or any other user with administrators 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

About Novell NetWare Managed Nodes About Preconfigured Elements 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.

194

Chapter 5

About Novell NetWare Managed Nodes About Preconfigured Elements

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

About Novell NetWare Managed Nodes About Preconfigured Elements

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>

196

Chapter 5

About Novell NetWare Managed Nodes About Preconfigured Elements

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 users NET.CFG file, edit the users frame type to match the servers frame type, and restart the users system.

Chapter 5

197

About Novell NetWare Managed Nodes About Preconfigured Elements

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.

198

Chapter 5

About Novell NetWare Managed Nodes About Preconfigured Elements

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 Nodes Configuration Distribution and Update

Configuration Distribution and Update

For Novell NetWare managed nodes, the platform selector and architecture identifiers is the following: novell/intel/nw

Location of User Scripts and Programs

Table 5-2 shows the location of user scripts and programs provided on the management server. Table 5-2 Location of User Scripts and Programs on the Management Server Location /var/opt/OV/share/databases/OpC/mgd_node/customer\ /novell/intel/nw/actions/*

Script/Program Automatic actions, operator-initiated actions, and scheduled actions Monitoring scripts and programs used by the monitoring agent and logfile encapsulator Scripts and programs called through command broadcast or started from the Application Desktop

/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/*

200

Chapter 5

About Novell NetWare Managed Nodes Configuration Distribution and Update

About Temporary Directories

Table 5-3 shows the temporary directories for distributed scripts and programs on the managed nodes. Table 5-3 Temporary Directories for Distributed Scripts and Programs on Managed Nodes Operating System Novell NetWare Temporary Directory

Managed Node Intel 486 or higher

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

About Target Directories

Table 5-4 shows the target directories for distributed scripts and programs on the managed nodes. Table 5-4 Target Directories for Distributed Scripts and Programs on the Managed Nodes Operating System Novell NetWare Target Directory Access Rights Administrator (full access) Administrator (full access) Administrator (full access)

Managed Node Intel 486 or higher

sys:/var/opt/OV/tmp/OpC/bin/\ actions sys:/var/opt/OV/tmp/OpC/bin/\ cmds sys:/var/opt/OV/tmp/OpC/bin/\ monitor

Chapter 5

201

About Novell NetWare Managed Nodes Organization 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 SYS:OPT/OV SYS:VAR/OPT/OV

LIB

BIN CONTRIB INCLUDE

CONF

TMP

LOG

bin OpC

NLS

OpC

OpC

OPC

OPC

OPC

<lang> INSTALL

UTILS

BIN

CONF

B
Key:

monitor

cmds

actions

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: Process-related Files SYS:/var/opt/OV/tmp/OpC Agent Configuration Files SYS:/var/opt/OV/conf/OpC 202 Chapter 5

About Novell NetWare Managed Nodes Organization of Managed Nodes

About the Default VPO Operator

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 Group-ID Description N/A. N/A Special user with rights equivalent to NetWare system administrator ADMIN.

Home Directory Not set. Login Shell None assigned. NetWare works with login scripts.

Types of System Resources

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

About Novell NetWare Managed Nodes Organization of Managed Nodes

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 Version 1.10y 1.10y 1.10y 1.10y 1.10y N/A N/A 1.10y 1.10y 1.10y

Module local_nd.nlm lwpnfsd.nlm netdir.nlm rpcbstub.nlm rpcinfo.nlm rpcstart.ncf rpcstop.ncf spx_nd.nlm tcp_nd.nlm tirpc.nlm

204

Chapter 5

About Novell NetWare Managed Nodes About 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 Nodes About 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

206

Chapter 5

About Novell NetWare Managed Nodes Types of Libraries

Types of Libraries
Table 5-6 describes the managed node libraries for VPO A.05.xx, A.06.xx, and A.07.xx. Table 5-6 Item EZ-RPC Library Libraries linked to the VPO library. Link and compile options Description Libraries for the VPO Managed Nodes VPO A.05.xx libopc.lib No libraries linked. VPO A.06.xx libopc.lib libov.lib VPO A.07.xx libopc.lib libov.lib

-DOPC_NW -DNW -DCSM_ONC libopc.lib is only used as archive library for API developers. It is not used at runtime.

-DOPC_NW -DNW -DCSM_ONC libopc.lib and libov.lib are only used as archive libraries for API developers. They are not used at runtime.

-DOPC_NW -DNW -DCSM_ONC libopc.lib and libov.lib are only used as archive libraries for API developers. They are not used at runtime.

About the Include File

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

Chapter 5

207

About Novell NetWare Managed Nodes Types of Libraries

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.nw For more information about the managed node makefile, see the ReadMe file: /opt/OV/OpC/examples/progs/README

208

Chapter 5

About OpenView Performance Agent for HP-UX and Sun Solaris

Chapter 6

209

About OpenView Performance Agent for HP-UX and Sun Solaris In 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).

210

Chapter 6

About OpenView Performance Agent for HP-UX and Sun Solaris About Other Platforms

About Other Platforms

For 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 Solaris What OVPA Does

What OVPA Does

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

212

Chapter 6

About OpenView Performance Agent for HP-UX and Sun Solaris What 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 Solaris Installation Requirements

Installation Requirements
This 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 Administrators Reference Volume I for details.

214

Chapter 6

About OpenView Performance Agent for HP-UX and Sun Solaris Installation Requirements

Hardware Requirements
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

About OpenView Performance Agent for HP-UX and Sun Solaris Installation Requirements

Software Requirements
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: Operating System 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: Operating System 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

216

Chapter 6

About OpenView Performance Agent for HP-UX and Sun Solaris Installation Requirements

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

About OpenView Performance Agent for HP-UX and Sun Solaris Installation Requirements

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: Users Manual. When installing OVPA, follow the disk space requirements listed in Table 6-1: Table 6-1 Required Disk Space Directory /opt/OV/a /opt/perf/b /var/opt/OV/a /var/opt/perf/c Total Disk Space 97 MB 30 MB 194 MB 40 MB 361 MB

a. Required during product installation. b. Required for running OVPA. c. For OVPA product use - log and status files.

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.

218

Chapter 6

About OpenView Performance Agent for HP-UX and Sun Solaris Installing and De-installing OVPA

Installing and De-installing OVPA

This 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 Administrators 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

About OpenView Performance Agent for HP-UX and Sun Solaris Installing and De-installing OVPA 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

220

Chapter 6

About OpenView Performance Agent for HP-UX and Sun Solaris Installing and De-installing OVPA

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

About OpenView Performance Agent for HP-UX and Sun Solaris Installing and De-installing OVPA 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

222

Chapter 6

About OpenView Performance Agent for HP-UX and Sun Solaris About Preconfigured Elements

About Preconfigured Elements

This 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
Application Check alarmdef Check parm Config alarmdef Config parm Config perflbd.rc Config ttd.conf List Processes List Versions Reactivate alarmdef Restart PA Servers Restart Perf Agt Start extract Start Perf Agt Start pv Start pvalarmd

Applications in Group: OV Performance

Description Check the syntax of the OVPA alarmdef file (utility -xc). Check the syntax of the OVPA parm file (utility -xp). Edit the OVPA alarmdef file and check the syntax (utility -xc). Edit the OVPA parm file and check the syntax (utility -up). Edit the /var/opt/perf/perflbd.rc file. Edit the /var/opt/perf/ttd.conf file. List the active performance tool processes (perfstat -p). List the version numbers for key performance tool files (perfstat -v). Reinitialize OVPA alarmgen process (mwa restart alarm). Reinitialize OVPA server processes (mwa restart server). Reinitialize all OVPA processes (mwa restart). Start the OVPA extract program. Start all OVPA processes (mwa start). Start the OpenView Performance Manager monitoring tool. Start the OpenView Performance Manager pvalarmd process (pvalarmd.start). Start the OVPA utility program.

Start utility

Chapter 6

223

About OpenView Performance Agent for HP-UX and Sun Solaris About Preconfigured Elements Table 6-2
Application Stop Perf Agt Stop pvalarmd

Applications in Group: OV Performance

Description Stop all OVPA processes except for ttd (mwa stop). Stop the OpenView Performance Manager pvalarmd process (pvalarmd.stop). Display last few lines of performance tool status files (perfstat -t)

Tail Status Files

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. Table 6-3
Template opcmsg for OV Performance

OV Performance Agent: Message Templates

Description Interception of messages from OpenView Performance Agent.

224

Chapter 6

About OpenView Performance Agent for HP-UX and Sun Solaris About Preconfigured Elements

Table 6-4 shows the logfile templates in the OV Performance Agent template group. Table 6-4
Template status.alarmgen status.mi status.perflbd status.rep_server status.scope status.ttd

OV Performance Agent: Logfile Templates

Description Retrieves messages from the alarmgen/agdbserver status file. Retrieves messages from the midaemon status file. Retrieves messages from the perflbd status file. Retrieves messages from the rep_server status file. Retrieves messages from the scopeux status file. Retrieves messages from the ttd status file.

Table 6-5 shows the monitor templates in the OV Performance Agent template group. Table 6-5
Template agdbserver alarmgen midaemon perflbd rep_server

OV Performance Agent: Monitor Templates

Description Sends a message if the agdbserver process is not running. Sends a message if the alarmgen process is not running. Sends a message if the midaemon process is not running. Sends a message if the perflbd process is not running. Sends a message if the number of rep_server processes running does not match the number configured in the perflbd.rc file. Sends a message if the scopeux process is not running. Sends a message if the ttd process is not running.

scopeux ttd

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 Chapter 6 225

About OpenView Performance Agent for HP-UX and Sun Solaris About Preconfigured Elements Table 6-6 shows the logfile templates in the OV Performance Manager template group. Table 6-6
Template status.pv status.pvalarmd

OV Performance Manager: Logfile Templates

Description Retrieves messages from the pv status file. Retrieves messages from the pvalarmd/pvmapd status file.

Table 6-7 shows the monitor templates in the OV Performance Manager template group. Table 6-7
Template pvalarmd

OV Performance Manager: Monitor Templates

Description Sends a message if the pvalarmd process is not running.

226

Chapter 6

About OpenView Performance Agent for HP-UX and Sun Solaris About Documentation

About Documentation
The 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

About OpenView Performance Agent for HP-UX and Sun Solaris About Documentation

Types of English-language Documentation

Table 6-8 describes the English-language documentation provided with the VPO management server. Table 6-8
Location /opt/OV/doc/C/ VP_Perf_Agt/hp/ C.03.50

English-language Documents
OS HP-UX File Name arm2api.pdf Title Application Response Measurement 2.0 API Guide HP OpenView Performance Agent for HP-UX: Dictionary of Operating System Performance Metrics HP OpenView Performance Agent for UNIX: Data Source Integration Guide HP OpenView Performance Agent for HP-UX 10.20 and 11: Installation & Configuration Guide HP OpenView Performance Agent for UNIX: Users Manual HP OpenView Performance Agent and GlancePlus for UNIX: Tracking Your Transactions

metrics.pdf

mwadsi.pdf

mwainst.pdf

mwausers.pdf

tyt2.pdf

228

Chapter 6

About OpenView Performance Agent for HP-UX and Sun Solaris About Documentation Table 6-8
Location /opt/OV/doc/C/ VP_Perf_Agt/ sun/C.03.45

English-language Documents
OS Sun Solaris File Name arm2api.pdf Title Application Response Measurement 2.0 API Guide HP OpenView Performance Agent for Sun Solaris Metrics Definitions HP OpenView Performance Agent for Sun Solaris Metrics Definitions HP OpenView Performance Agent for UNIX: Data Source Integration Guide HP OpenView Performance Agent for Sun Solaris Systems: Installation & Configuration Guide HP OpenView Performance Agent for UNIX: Users Manual HP OpenView Performance Agent and GlancePlus for UNIX: Tracking Your Transactions

metsun.pdf

metsun.txt

mwadsi.pdf

mwainst.pdf

mwausers.pdf

tyt.pdf

Chapter 6

229

About OpenView Performance Agent for HP-UX and Sun Solaris About Documentation

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. Japanese-language Documents
File Name mwainst_ux11.pdf Title HP OpenView Performance Agent for HP-UX: Installation & Configuration Guide HP OpenView Performance Agent for UNIX: Users Manual HP OpenView Performance Agent for UNIX: Data Source Integration Guide HP OpenView Performance Agent for UNIX: Tracking Your Transactions

Table 6-9
Location

/opt/OV/doc/japanese/ VP_Perf_Agt/hp/C.03.50

mwausers_ux.pdf

mwadsi_ux.pdf

tyt2_ux.pdf

230

Chapter 6

About Sequent DYNIX Managed Nodes

Chapter 7

231

About Sequent DYNIX Managed Nodes In this Chapter

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

232

Chapter 7

About Sequent DYNIX Managed Nodes Installation Requirements

Installation Requirements
This section explains VPO hardware and software requirements for Sequent DYNIX managed nodes.

Hardware Requirements
Before installing VPO, make sure the Sequent DYNIX systems you select as managed nodes meet the following hardware requirements: Disk Space 10 MB (about 20 MB is required during software installation) HPFS Partition VPO agent must be installed on an HPFS partition. FAT partitions are not supported for VPO agent installation and operation. Additional Swap Space None Additional RAM 4 MB

Software Requirements
Before installing VPO, make sure the following software is installed on Sequent DYNIX managed nodes: Operating System For a list of operating system versions supported by VPO, see the VPO Installation Guide for the Management Server. System Parameters For a list of kernel parameters, see the VPO Administrators 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 Nodes Installation 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.

234

Chapter 7

About Sequent DYNIX Managed Nodes Installing and De-installing Agents

Installing and De-installing Agents

This section describes how to install and de-install Sequent DYNIX managed nodes.

Tips for Installing Agents

When installing Sequent DYNIX managed nodes, follow these guidelines: Name of Management Server 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. VPO Agent Software 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: mkdir -p /bigdisk/OV 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 Nodes Installing and De-installing Agents

Installing Agents
For general installation instructions, see the VPO Administrators Reference Volume I. If errors occur during the installation, check the local installation logfile: /tmp/pkgadd.log

De-installing Agents
For general de-installation instructions, see the VPO Administrators Reference Volume I. If errors occur during the de-installation, check the local de-installation logfile: /tmp/pkgrm.log

236

Chapter 7

About Sequent DYNIX Managed Nodes About Preconfigured Elements

About Preconfigured Elements

This section describes preconfigured templates, template groups, and applications used by VPO on Sequent DYNIX managed nodes.

One Preconfigured Template Group

VPO uses the following preconfigured template group: DYNIX/ptx

Types of Default Logfile Templates

Table 7-1 shows encapsulated logfiles and associated template used on Sequent DYNIX managed nodes. Table 7-1 Logfile /usr/lib/cron /usr/adm/messages /usr/adm/sulog /var/adm/wtmp /usr/adm/critical /usr/spool/adm/syslog /usr/spool/lp/logs/lpsc hed /usr/spool/lp/remotelp /usr/spool/lp/logs/requ ests Encapsulated Logfiles on Sequent DYNIX/ptx Managed Nodes Description Cron logfile OS messages Switch user logfile History of logins Syslog daemon error logfile Syslog daemon logfile Printer services logfile Remote printer services log Printer requests logfile Template Name Cron (DYNIX/ptx) OS Msgs (DYNIX/ptx) Su (DYNIX/ptx) Logs (DYNIX/ptx) Syslog Error (DYNIX/ptx) Syslog (DYNIX/ptx) Lp Serv (DYNIX/ptx) Rlp Serv (DYNIX/ptx) Lp Req (DYNIX/ptx)

Chapter 7

237

About Sequent DYNIX Managed Nodes About Preconfigured Elements

No SNMP Trap and Event Interception

The VPO event interceptor is not supported on Sequent DYNIX/ptx managed nodes.

Types of Default Monitored Objects

Table 7-2 describes the default monitored objects used by VPO on Sequent DYNIX managed nodes. Table 7-2 Object Object Thresholds on the Managed Nodes Description Threshold Polling Interval (Minutes) 2 10 5 2 5 5 5 5

cpu_util disk_util Inetd MailQueue Length proc_util sendmail swap_util Syslogd

Monitors CPU utilization. Requires the sar program. Monitors disk space utilization on the root disk. Number of executing instances of inetd (Internet Daemon). Length of the sendmail queue. Number of unsent mail messages. Monitors process table utilization. Number of executing instances of sendmail. Monitors SWAP utilization. Checks whether syslogd is running.

95% 90% 0.5 30 75% 0.5 80% 0.5

Types of Default Applications

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

238

Chapter 7

About Sequent DYNIX Managed Nodes Distributing Scripts and Programs

Distributing Scripts and Programs

For Sequent DYNIX managed nodes, the platform selector and architecture identifier is the following: sequent/intel/dynix

Location of User Scripts and Programs

Table 7-3 shows the location of user scripts and programs provided on the management server. Table 7-3 Location of User Scripts and Programs on the Management Server Location /var/opt/OV/share/databases/OpC/mgd_node/customer\ /sequent/intel/dynix/actions/*

Script/Program Automatic actions, operator-initiated actions, and scheduled actions Monitoring scripts and programs used by the monitoring agent and the logfile encapsulator Scripts and programs called through command broadcast or started from the Application Desktop

/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 Nodes Distributing Scripts and Programs

About Temporary Directories

Table 7-4 shows the temporary directories for distributed scripts and programs on the managed nodes. Table 7-4 Temporary Directories for Distributed Scripts and Programs on the Managed Nodes Operating System Sequent DYNIX/ptx Temporary Directory

Managed Node Intel 486 or higher

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

240

Chapter 7

About Sequent DYNIX Managed Nodes Organization of Managed Nodes

Organization of Managed Nodes

Figure 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

/opt/OV

/var/opt/OV

locale <lang>

contrib OpC

bin OpC

lib include

conf OpC

tmp OpC bin

log OpC conf

bin OpC

LC_MESSAGES

install

utils

Key:

monitor

cmds

actions

Location of Files
On Sequent DYNIX/ptx managed nodes, files are located as follows: Process-related Files /var/opt/OV/tmp/OpC Agent Configuration Files /var/opt/OV/conf/OpC

Chapter 7

241

About Sequent DYNIX Managed Nodes Organization of Managed Nodes

About the Default VPO Operator

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 Sequent DYNIX/ptx managed nodes: /etc/passwd Fields include the following: User Name opc_op

Encrypted Password * (no login) User-ID Group-ID Description 777 (if still available) or next possible free number 77 (if still available) or next possible free number Default VPO operator

Home Directory /home/opc_op Login Shell /bin/sh

About Default VPO Operator Group Entries The default VPO operator group appears in the following directory on Sequent DYNIX/ptx managed nodes: /etc/group Fields include the following: Group Name opcgrp

Encrypted Password Empty Group-ID Users Description 77 or higher opc_op Default VPO operator group

242

Chapter 7

About Sequent DYNIX Managed Nodes Organization of Managed Nodes

Types of System Resources

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 VPO startup and shutdown script.

/etc/init.d/opcagt /etc/rc0.d /etc/rc2.d

Creates the K07opcagt file. Creates the S93opcagt file. NCS startup and shutdown script.

/etc/init.d/ncs /etc/rc0.d /etc/rc2.d

Creates the K52ncs file. Creates the S76ncs file.

Chapter 7

243

About Sequent DYNIX Managed Nodes Types of Libraries

Types of Libraries
Table 7-5 describes the managed node libraries for VPO A.05.xx, A.06.xx, and A.07.xx. Table 7-5
Item NCS Library Libraries linked to the VPO library

Libraries for the VPO Managed Nodes

VPO A.05.xx 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/libin tl.a Link and compile options Description -lopc -lnsp -lsocket N/A VPO A.06.xx 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/libin tl.a -lopc -lnsp -lsocket N/A VPO A.07.xx libopc.so /usr/lib/libnck.a /usr/lib/libnsl.so /usr/lib/librpc.so /usr/lib/libsec.a /usr/lib/libseq.a /usr/lib/libsocket. so /usr/coff/lib/libin tl.a

-lopc -lnsp -lsocket N/A

About the Include File

On an Intel 486 or higher platform with Sequent DYNIX/ptx managed nodes, use the following include file: /opt/OV/include/opcapi.h

244

Chapter 7

About Sequent DYNIX Managed Nodes Types of Libraries

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.ptx For more information about the managed node makefile, see the ReadMe file: /opt/OV/OpC/examples/progs/README

Chapter 7

245

About Sequent DYNIX Managed Nodes Types of Libraries

246

Chapter 7

About SGI IRIX Managed Nodes

Chapter 8

247

About SGI IRIX Managed Nodes In this Chapter

In this Chapter
This chapter explains how to install and configure HP OpenView VantagePoint Operations (VPO) on Silicon Graphics Indigo (SGI) IRIX managed nodes.

248

Chapter 8

About SGI IRIX Managed Nodes Installation Requirements

Installation Requirements
This section explains VPO hardware and software requirements for SGI IRIX managed nodes.

Hardware Requirements
Before installing VPO, make sure the SGI IRIX systems you select as managed nodes meet the following hardware requirements: Disk Space 10 MB (about 20 MB is required during software installation) Additional Swap Space None Additional RAM None

Chapter 8

249

About SGI IRIX Managed Nodes Installation Requirements

Software Requirements
Before installing VPO, make sure the following software is installed on SGI IRIX managed nodes: Operating System For a list of operating system versions supported by VPO, see the VPO Installation Guide for the Management Server. System Parameters For a list of kernel parameters, see the VPO Administrators 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.

250

Chapter 8

About SGI IRIX Managed Nodes Installing and De-installing Agents

Installing and De-installing Agents

This section describes how to install and de-install SGI IRIX managed nodes.

Tips for Installing Agents

When installing SGI IRIX managed nodes, follow these guidelines: Name of Management Server 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. VPO Agent Software 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. For example, if /bigdisk is a local file system with enough free space, you would create the symbolic link as follows: mkdir -p /bigdisk/OV 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 8

251

About SGI IRIX Managed Nodes Installing and De-installing Agents

Installing Agents
For general installation instructions, see the VPO Administrators Reference Volume I. If errors occur during the installation, check the local installation logfile: /tmp/inst.log

De-installing Agents
For general de-installation instructions, see the VPO Administrators Reference Volume I. If errors occur during the de-installation, check the local de-installation logfile: /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> In this command, <VPO_version> is the version of VPO that supports this agent platform (for example, A.07.00).

252

Chapter 8

About SGI IRIX Managed Nodes About Preconfigured Elements

About Preconfigured Elements

This section describes preconfigured templates, template groups, and applications used by VPO on SGI IRIX managed nodes.

One Preconfigured Template Group

VPO uses the following preconfigured template group: IRIX

Types of Default Logfile Templates

Table 8-1 shows encapsulated logfiles and associated template used on SGI IRIX managed nodes. Table 8-1 Logfile /var/adm/loginlog /var/cron/log /var/adm/sulog /var/adm/SYSLOGa /var/adm/wtmpx Encapsulated Logfiles on SGI IRIX Managed Nodes Description History of failed login attempts Cron logfile Switch user logfile Syslog daemon logfile History of logins Template Name Bad Logs (IRIX) Cron (IRIX) Su (IRIX) Syslog (IRIX) Logins (IRIX)

a. requires the logfile /var/adm/SYSLOG which must be configured (or enabled) in the file /etc/syslog.conf No SNMP Trap and Event Interception The VPO event interceptor is not supported on SGI IRIX managed nodes.

Chapter 8

253

About SGI IRIX Managed Nodes About Preconfigured Elements Types of Default Monitored Objects Table 8-2 describes the default monitored objects used by VPO on SGI IRIX managed nodes. Table 8-2 Object Object Thresholds on the Managed Nodes Description Threshold Polling Interval (Minutes) 2 10 5 2 5 5 5 5

cpu_util disk_util Inetd MailQueue Length proc_util sendmail swap_util Syslogd

Monitors CPU utilization. Requires the sar program. Monitors disk space utilization on the root disk. Number of executing instances of inetd (Internet Daemon). Length of the sendmail queue. Number of unsent mail messages. Monitors process table utilization. Number of executing instances of sendmail. Monitors SWAP utilization. Checks whether syslogd is running. Types of Default Applications

95% 90% 0.5 30 75% 0.5 80% 0.5

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

254

Chapter 8

About SGI IRIX Managed Nodes Distributing Scripts and Programs

Distributing Scripts and Programs

For SGI IRIX managed nodes, the platform selector and architecture identifier is the following: sgi/mips/irix

Location of User Scripts and Programs

Table 8-3 shows the location of user scripts and programs provided on the management server. Table 8-3 Location of User Scripts and Programs on the Management Server Location /var/opt/OV/share/databases/OpC/mgd_node/customer\ /sgi/mips/irix/actions/

Script/Program Automatic actions, operator-initiated actions, and scheduled actions Monitoring scripts and programs used by the monitoring agent and the logfile encapsulator Scripts and programs called through command broadcast or started from the Application Desktop

/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 Nodes Distributing Scripts and Programs

About Temporary Directories

Table 8-4 shows the temporary directories for distributed scripts and programs on the managed nodes. Table 8-4 Temporary Directories for Distributed Scripts and Programs on the Managed Nodes Operating System SGI IRIX Temporary Directory

Managed Node Silicon Graphics

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

About Target Directories

Table 8-5 shows the target directories for distributed scripts and programs on the managed nodes. Table 8-5 Target Directories for Distributed Scripts and Programs on the Managed Nodes Operating System SGI IRIX Target Directory Access Rights

Managed Node Silicon Graphics

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

rwxr-xr-x (owner:root) rwxr-xr-x (owner:root) rwxr-xr-x (owner:root)

256

Chapter 8

About SGI IRIX Managed Nodes Organization of Managed Nodes

Organization of Managed Nodes

Figure 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 /opt/OV /var/opt/OV

locale <lang>

contrib bin OpC OpC

lib include

conf OpC

tmp OpC bin

log OpC conf

bin OpC

LC_MESSAGES install

utils

B
Key:

monitor

cmds

actions

Location of Files
On SGI IRIX managed nodes, files are located as follows: Process-related Files /var/opt/OV/tmp/OpC Agent Configuration Files /var/opt/OV/conf/OpC

Chapter 8

257

About SGI IRIX Managed Nodes Organization of Managed Nodes

About the Default VPO Operator

If they do not already exist, the default VPO operator opc_op and group opcgrp are created. 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 Default VPO Operator Entries The default VPO operator appears in the following directory on SGI IRIX managed nodes: /etc/passwd Fields include the following: User Name opc_op

Encrypted Password * (no login) User-ID Group-ID Description 777 (if still available) or next possible free number 77 (if still available) or next possible free number Default VPO operator

Home Directory /var/people/opc_op Login Shell /bin/sh (POSIX shell)

About Default VPO Operator Group Entries The default VPO operator group appears in the following directory on SGI IRIX managed nodes: /etc/group Fields include the following: Group Name opcgrp

Encrypted Password Empty Group-ID Users Description 258 77 or higher opc_op Default VPO operator group Chapter 8

About SGI IRIX Managed Nodes Organization of Managed Nodes

Types of System Resources

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 VPO startup and shutdown script.

/etc/init.d/opcagt /etc/rc0.d /etc/rc2.d /etc/exports /etc/exports

Creates the K09opcagt file. Creates the S89opcagt file. Cluster server only. Entry for export of /opt directory. Cluster client only. Entry for mount /opt directory. NCS startup and shutdown script.

/etc/int.d/grad_nck /etc/rc0.d /etc/rc2.d

Creates the K35nck file. Creates the S40nck file.

NOTE

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

Chapter 8

259

About SGI IRIX Managed Nodes Types of Libraries

Types of Libraries
Table 8-6 describes the managed node libraries for VPO A.05.xx, A.06.xx, and A.07.xx. Table 8-6
Item NCS Library Libraries linked to the VPO library.

Libraries for the VPO Managed Nodes

VPO A.05.xx libopc.so /opt/OV/lib/libnsp .so /usr/lib/libnck.a /usr/lib/libnsl.so /usr/lib/libc.so Link and compile options Description -lopc -lsocket -lnsl N/A VPO A.06.xx libopc.so /opt/OV/lib/libnsp .so /usr/lib/libnck.a /usr/lib/libnsl.so /usr/lib/libc.so -lopc -lsocket -lnsl N/A VPO A.07.xx libopc.so /opt/OV/lib/libnsp .so /usr/lib/libnck.a /usr/lib/libnsl.so /usr/lib/libc.so -lopc -lsocket -lnsl N/A

About the Include File

On a Silicon Graphics Indigo platform with SGI IRIX managed nodes, use the following include file: /opt/OV/include/opcapi.h

260

Chapter 8

About SGI IRIX Managed Nodes Types of Libraries

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.irix For more information about the managed node makefile, see the ReadMe file: /opt/OV/OpC/examples/progs/README

Chapter 8

261

About SGI IRIX Managed Nodes Types of Libraries

262

Chapter 8

About SINIX RM/Reliant Managed Nodes

Chapter 9

263

About SINIX RM/Reliant Managed Nodes In this Chapter

In this Chapter
This chapter explains how to install and configure HP OpenView VantagePoint Operations (VPO) on Siemens-Nixdorf SINIX RM/Reliant managed nodes.

264

Chapter 9

About SINIX RM/Reliant Managed Nodes Installation Requirements

Installation Requirements
This section explains VPO hardware and software requirements for SINIX RM/Reliant managed nodes.

Hardware Requirements
Before installing VPO, make sure the SINIX RM/Reliant systems you select as managed nodes meet the following hardware requirements: Disk Space 10 MB (about 20 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 SINIX RM/Reliant managed nodes: Operating System For a list of operating system versions supported by VPO, see the VPO Installation Guide for the Management Server. System Parameters For a list of kernel parameters, see the VPO Administrators 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 Nodes Installation Requirements

Communication Software 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

266

Chapter 9

About SINIX RM/Reliant Managed Nodes Installing and De-installing Agents

Installing and De-installing Agents

This section describes how to install and de-install SINIX RM/Reliant managed nodes.

Tips for Installing Agents

When installing SINIX RM/Reliant managed nodes, follow these guidelines: Name of Management Server 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. VPO Agent Software 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. For example, if /bigdisk is a local file system with enough free space, you would create the symbolic link as follows: mkdir -p /bigdisk/OV 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 9

267

About SINIX RM/Reliant Managed Nodes Installing and De-installing Agents

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.

268

Chapter 9

About SINIX RM/Reliant Managed Nodes Installing and De-installing Agents

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 Administrators 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

About SINIX RM/Reliant Managed Nodes Installing and De-installing Agents 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. Installing Agents with Standard Installation For standard installation instructions, see the VPO Administrators Reference Volume I. If errors occur during the installation, check the local installation logfile: /tmp/pkgadd.log Installing Agents Manually 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

270

Chapter 9

About SINIX RM/Reliant Managed Nodes Installing and De-installing Agents

De-installing Agents
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 Administrators Reference Volume I. If errors occur during the de-installation, check the local de-installation logfile: /tmp/pkgrm.log To De-install an Agent Manually To de-install an agent manually, follow these steps: 1. Stop all VPO agents running on the managed node. 2. De-install the VPO agent software from SINIX/Reliant managed nodes by entering: pkgrm OPC Removing Older Agents 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 Nodes About Preconfigured Elements

About Preconfigured Elements

This section describes preconfigured templates, template groups, and applications used by VPO on SINIX RM/Reliant managed nodes.

One Preconfigured Template Group

VPO uses the following preconfigured template group: SINIX

Types of Default Logfile Templates

Table 9-1 shows encapsulated logfiles and associated template used on SINIX RM/Reliant managed nodes. Table 9-1 Encapsulated Logfiles on Siemens Nixdorf SINIX/Reliant Managed Nodes Description Cron logfile SINIX OS messages Switch user logfile History of logins Bad login attempts Template Name Cron (SINIX) OS Msgs (SINIX) Su (SINIX) Logins (SINIX) Bad Logs (SINIX)

Logfile /var/cron/log a /etc/.osm /var /adm/sulog b /var/adm/wtmpx /var/adm/loginlog c

a. Default setup is used in the /etc/default/cron file b. Default setup is used in /etc/default/su file c. You must manually create the /var/adm/loginlog file

No SNMP Trap and Event Interception

The VPO event interceptor is not supported on SINIX RM/Reliant managed nodes.

272

Chapter 9

About SINIX RM/Reliant Managed Nodes About Preconfigured Elements

Types of Default Monitored Objects

Table 9-2 describes the default monitored objects used by VPO on SINIX RM/Reliant managed nodes. Table 9-2 Object Object Thresholds on the Managed Nodes Description Threshold Polling Interval (Minutes) 2 10 5 5 5 5

cpu_util disk_util Inetd proc_util swap_util Syslogd

Monitors CPU utilization. Requires the sar program. Monitors disk space utilization on the root disk. Number of executing instances of inetd (Internet Daemon). Monitors process table utilization. Monitors SWAP utilization. Checks whether syslogd is running.

95% 90% 0.5 75% 80% 0.5

Chapter 9

273

About SINIX RM/Reliant Managed Nodes Distributing Scripts and Programs

Distributing Scripts and Programs

For SINIX RM/Reliant managed nodes, the platform selector and architecture identifier is the following: sni/mips/sinix

Location of User Scripts and Programs

Table 9-3 shows the location of user scripts and programs provided on the management server. Table 9-3 Location of User Scripts and Programs on the Management Server Location /var/opt/OV/share/databases/OpC/mgd_node/customer\ /sni/mips/sinix/actions/*

Script/Program Automatic actions, operator-initiated actions, and scheduled actions Monitoring scripts and programs used by the monitoring agent and the logfile encapsulator Scripts and programs called through command broadcast or started from the Application Desktop

/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/*

274

Chapter 9

About SINIX RM/Reliant Managed Nodes Distributing Scripts and Programs

About Temporary Directories

Table 9-4 shows the temporary directories for distributed scripts and programs on the managed nodes. Table 9-4 Temporary Directories for Distributed Scripts and Programs on the Managed Nodes Operating System SINIX Temporary Directory

Managed Node Siemens Nixdorf

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

About Target Directories

Table 9-5 shows the target directories for distributed scripts and programs on the managed nodes. Table 9-5 Target Directories for Distributed Scripts and Programs on the Managed Nodes Operating System SINIX Target Directory Access Rights

Managed Node Siemens Nixdorf

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

rwxr-xr-x (owner:root) rwxr-xr-x (owner:root) rwxr-xr-x (owner:root)

Chapter 9

275

About SINIX RM/Reliant Managed Nodes Organization of Managed Nodes

Organization of Managed Nodes

Figure 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 /opt/OV /var/opt/OV

locale <lang>

contrib bin OpC OpC install

lib include

conf OpC

tmp OpC bin

log OpC conf

bin OpC

LC_MESSAGES

utils

B
Key:

monitor

cmds

actions

Location of Files
On SINIX RM/Reliant managed nodes, files are located as follows: Process-related Files /var/opt/OV/tmp/OpC Agent Configuration Files /var/opt/OV/conf/OpC

276

Chapter 9

About SINIX RM/Reliant Managed Nodes Organization of Managed Nodes

About the Default VPO Operator

If they do not already exist, the default VPO operator opc_op and group opcgrp are created. 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 Default VPO Operator Entries The default VPO operator appears in the following directory on SINIX RM/Reliant managed nodes: /etc/passwd Fields include the following: User Name opc_op

Encrypted Password * (no login) User-ID Group-ID Description 777 (if still available) or next possible free number 177 (if still available) or next possible free number Default VPO operator

Home Directory /home/opc_op Login Shell /bin/sh

About Default VPO Operator Group Entries The default VPO operator group appears in the following directory on SINIX RM/Reliant managed nodes: /etc/group Fields include the following: Group Name opcgrp

Encrypted Password Empty Group-ID Users Description Chapter 9 177 or higher opc_op Default VPO operator group 277

About SINIX RM/Reliant Managed Nodes Organization of Managed Nodes

Types of System Resources

VPO makes changes in the following system resource files during installation on SINIX RM/Reliant managed nodes: /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 VPO startup and shutdown script.

/etc/init.d/opcagt /etc/rc0.d /etc/rc1.d /etc/rc2.d

Creates the K09opcagt file. Creates the K09opcagt file. Creates the S89opcagt file.

/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 /etc/rc1.d /etc/rc2.d Creates the K52ncs (if it is not already present and the communciation type is NCS RPC). Creates the K52ncs file (if it is not already present and the communciation type is NCS RPC). 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).

NOTE

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

278

Chapter 9

About SINIX RM/Reliant Managed Nodes Types of Libraries

Types of Libraries
Table 9-6 describes the managed node libraries for VPO A.05.xx, A.06.xx, and A.07.xx. Table 9-6
VPO Version DCE Library Libraries linked to the VPO library Link and compile options

Libraries for the VPO Managed Nodes

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

libopc_r.so thr_cc is used which comes with its own libraries -lopc_r -lnsp -ldce -lsocket_r -lresolv_r -lm_r -lc -lnsl_r_i N/A libopc.so mips_cc is used which comes with its own libraries -lopc -lnck -lnsp -lsocket -lnsl -lc -lucb N/A

libopc_r.so thr_cc is used which comes with its own libraries -lopc_r -lnsp -ldce -lsocket_r -lresolv_r -lm_r -lc -lnsl_r_i N/A libopc.so mips_cc is used which comes with its own libraries -lopc -lnck -lnsp -lsocket -lnsl -lc -lucb N/A

libopc_r.so thr_cc is used which comes with its own libraries -lopc_r -lnsp -ldce -lsocket_r -lresolv_r -lm_r -lc -lnsl_r_i N/A libopc.so mips_cc is used which comes with its own libraries -lopc -lnck -lnsp -lsocket -lnsl -lc -lucb N/A

Description NCS Library Libraries linked to the VPO library Link and compile options Description

Chapter 9

279

About SINIX RM/Reliant Managed Nodes Types of Libraries

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 makefiles: Makef.sinix Makef.sinix-dce For more information about the managed node makefiles, see the ReadMe file: /opt/OV/OpC/examples/progs/README

280

Chapter 9

10

About Sun Solaris Managed Nodes

Chapter 10

281

About Sun Solaris Managed Nodes In this Chapter

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

282

Chapter 10

About Sun Solaris Managed Nodes Installation Requirements

Installation Requirements
This section explains VPO hardware and software requirements for Sun Solaris managed nodes.

Hardware Requirements
Before installing VPO, make sure the Sun Solaris systems you select as managed nodes meet the following hardware requirements: Disk Space 40 MB (about 80 MB is required during software installation) 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. Additional Swap Space None Additional RAM None

Chapter 10

283

About Sun Solaris Managed Nodes Installation Requirements

Software Requirements
Before installing VPO, make sure the following software is installed on Sun Solaris managed nodes: Operating System For a list of operating system versions supported by VPO, see the VPO Installation Guide for the Management Server. 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
Patch ID 107733-09 105591-11 106429-02 105181-29 105210-38 105568-23 105633-59 106841-01 106842-09 Description SunOS 5.6: Linker patch SunOS 5.6: Shared library patch for C++ SunOS 5.6: /kernel/drv/mm patch SunOS 5.6: Kernel update patch SunOS 5.6: libaio, libc & watchmalloc patch SunOS 5.6: /usr/lib/libthread.so.1 patch OpenWindows 3.6: Xsun patch OpenWindows 3.6: Keytables patch SunOS 5.6: Feature patch for Euro currency support in Solaris 2.6

OS Version Solaris 2.6

284

Chapter 10

About Sun Solaris Managed Nodes Installation Requirements Table 10-1 Required Patches for Sun Solaris Managed Nodes
Patch ID 106950-15 106327-10 107544-03 106541-17 106980-17 Solaris 8 109147-09 108434-03 108827-11 Description SunOS 5.7: Linker patch SunOS 5.7: 32-Bit Shared library patch for C++ SunOS 5.7: /usr/lib/fs/ufs/fsck patch SunOS 5.7: Kernel update patch SunOS 5.7: libthread patch SunOS 5.8: Linker patch SunOS 5.8: Shared library patch for C++ SunOS 5.8: libthread patch

OS Version Solaris 7

Kernel Parameters It is recommended that you set the following kernel parameters for Sun Solaris managed nodes: Table 10-2 Recommended Kernel Parameters for Sun Solaris Managed Nodes Description Number of entries in semaphore map Number of semaphore identifiers Number of semaphores in system Maximum number of semaphores per ID Minimum value 15 or greater 30 200 or greater 100

Parameter

semmap semmni semmns semmsl

You can check and change the kernel parameters by editing the /etc/system file.

Chapter 10

285

About Sun Solaris Managed Nodes Installation Requirements

Communication Software 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. Table 10-3 OS Solaris 2.6 Solaris 7 Solaris 8 Supported DCE packages DCE TransArc DCE 2.0, HPlwdce, DASCOM DCE 1.1 IBM DCE 3.1, HPlwdce, DASCOM DCE 1.1 IBM DCE 3.1, HPlwdce, DASCOM DCE 1.1

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.

286

Chapter 10

About Sun Solaris Managed Nodes Installing and De-installing Agents

Installing and De-installing Agents

This section describes how to install and de-install Sun Solaris managed nodes.

Tips for Installing Agents

When installing Sun Solaris managed nodes, follow these guidelines: Name of Management Server 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. 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

About Sun Solaris Managed Nodes Installing and De-installing Agents VPO Agent Software 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. For example, if /bigdisk is a local file system with enough free space, you would create the symbolic link as follows: mkdir -p /bigdisk/OV 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 the cluster server.

288

Chapter 10

About Sun Solaris Managed Nodes Installing and De-installing Agents

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

About Sun Solaris Managed Nodes Installing and De-installing Agents

Installing Agents
To install agents on Sun Solaris managed nodes, you can use standard or manual installation methods. Installing Agents with Standard Installation For standard installation instructions, see the VPO Administrators Reference Volume I. If errors occur during the installation, check the local installation logfile: /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: 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/sun/\ sparc/solaris/A.07.00/RPC_[NCS|DCE_TCP|DCE_UDP]/ 2. Set umask, enter: umask 022

290

Chapter 10

About Sun Solaris Managed Nodes Installing and De-installing Agents 3. Install the Agent. Start the agent installation script by entering: /tmp/opc_inst You can now activate the Sun Solaris managed node. For instructions, see Activating Agents on page 292.

Chapter 10

291

About Sun Solaris Managed Nodes Installing and De-installing Agents

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. Use the following 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 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. 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 Administrators Reference Volume I and the man page opcactivate(1M). 5. After the node is connected to the network, execute the following command on the management server: /opt/OV/bin/OpC/opcsw -installed <node> 292 Chapter 10

About Sun Solaris Managed Nodes Installing and De-installing Agents To Activate the Node from the VPO GUI 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. Use the following 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. 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: /opt/OV/bin/OpC/opcragt -status <node>

Chapter 10

293

About Sun Solaris Managed Nodes Installing and De-installing Agents

De-installing Agents
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. De-installing Agents with Standard De-installation For general de-installation instructions, see the VPO Administrators Reference Volume I. If errors occur during the de-installation, check the local de-installation logfile: /tmp/pkgrm.log To De-install an Agent Manually To de-install an agent manually, follow these steps: 1. Stop all VPO agents running on the managed node. 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. Enter the following: /usr/sbin/pkgrm HPlwdce

294

Chapter 10

About Sun Solaris Managed Nodes Installing and De-installing Agents Removing Older Agents 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> In this command, <VPO_version> is the version of VPO that supports this agent platform (for example, A.07.00).

Chapter 10

295

About Sun Solaris Managed Nodes About Preconfigured Elements

About Preconfigured Elements

This section describes preconfigured templates, template groups, and applications used by VPO on Sun Solaris managed nodes.

One Preconfigured Template Group

VPO uses the following preconfigured template group: Solaris

Types of Default opcmsg Message Templates

Table 10-4 shows the opcmsg message templates that are available for Sun Solaris managed nodes. Table 10-4 Name opcmsg(1|3) opcmsg Message Templates on Sun Solaris Managed Nodes Description Default interception of messages submitted by opcmsg(1), opcagtmsg_send(3), and opcmsg(3).

296

Chapter 10

About Sun Solaris Managed Nodes About Preconfigured Elements

Types of Default Logfile Templates

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 Description History of Solaris failed logins Cron logfile System logfile Switch user logfile History of logins Fetch messages from SC and forward to APM Fetch messages from VCS and forward to APM Fetch messages from VCS and forward to APM Template Name Bad Logs (Solaris) Cron (Solaris) Syslog (Solaris) Su (Solaris) Logins (Solaris) Engine Log (SC) Engine Log (VCS)

Logfile /var/adm/loginlog /var/cron/log /var/adm/messages /var/adm/sulog /var/adm/wtmpx /var/adm/messages /var/VRTSvcs/\ log/engine_A.log /var/opt/OV/tmp/\ OpC/opcapmvcsg\ notifyengine

Engine Notifiy Log (VCS)

Chapter 10

297

About Sun Solaris Managed Nodes About Preconfigured Elements

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.

NOTE

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

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.

298

Chapter 10

About Sun Solaris Managed Nodes About Preconfigured Elements 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 Sun Solaris 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 10

299

About Sun Solaris Managed Nodes About Preconfigured Elements 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>

300

Chapter 10

About Sun Solaris Managed Nodes About Preconfigured Elements

Types of Default Monitored Objects

Table 10-6 describes the default monitored objects used by VPO on Sun Solaris managed nodes. Table 10-6 Object Object Thresholds on the Managed Nodes Description Threshold Polling Interval (Minutes) 2 10 5 2 5 5 5 5

cpu_util disk_util Inetd MailQueue Length proc_util sendmail swap_util Syslogd

Monitors CPU utilization: requires the sar program Monitors disk space utilization on the root disk Number of executing instances of inetd (Internet Daemon) Length of the sendmail queue: number of unsent mail messages Monitors process table utilization Number of executing instances of sendmail Monitors SWAP utilization Checks whether syslogd is running

95% 90% 0.5 30 75% 0.5 80% 0.5

Types of Applications
For a list of default applications available for UNIX managed nodes, see the VPO Administrators Reference Volume I.

Chapter 10

301

About Sun Solaris Managed Nodes Distributing Scripts and Programs

Distributing Scripts and Programs

For Sun Solaris managed nodes, the platform selector and architecture identifier is the following: sun/sparc/solaris

Location of User Scripts and Programs

Table 10-7 shows the location of user scripts and programs provided on the management server. Table 10-7 Location of User Scripts and Programs on the Management Server Location /var/opt/OV/share/databases/OpC/mgd_node/customer\ /sun/sparc/solaris/actions/*

Script/Program Automatic actions, operator-initiated actions, and scheduled actions Monitoring scripts and programs used by the monitoring agent and the logfile encapsulator Scripts and programs called through command broadcast or started from the Application Desktop

/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/*

302

Chapter 10

About Sun Solaris Managed Nodes Distributing Scripts and Programs

About Temporary Directories

Table 10-8 shows the temporary directories for distributed scripts and programs on the managed nodes. Table 10-8 Temporary Directories for Distributed Scripts and Programs on the Managed Nodes Operating System Sun Solaris Temporary Directory

Managed Node Sun SPARC Fujitsu-Siemens SPARC

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

About Target Directories

Table 10-9 shows the target directories for distributed scripts and programs on the managed nodes. Table 10-9 Target Directories for Distributed Scripts and Programs on the Managed Nodes Operating System Sun Solaris Target Directory Access Rights

Managed Node Sun SPARC Fujitsu-Siemens SPARC

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

rwxr-xr-x (owner: root) rwxr-xr-x (owner: root) rwxr-xr-x (owner: root)

Chapter 10

303

About Sun Solaris Managed Nodes Organization 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 /opt/OV /var/opt/OV

contrib OpC

locale <lang>

bin OpC

lib include databases

conf

tmp

log OpC

bin OpC

OpC BBC OpC bin conf

LC_MESSAGES install utils

B
Key:

monitor

cmds

actions

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: Process-related Files /var/opt/OV/tmp/OpC Agent Configuration Files /var/opt/OV/conf/OpC

304

Chapter 10

About Sun Solaris Managed Nodes Organization of Managed Nodes

About the Default VPO Operator

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.

Types of System Resources

VPO makes changes in the following system resource files during installation on Sun Solaris managed nodes: /etc/passwd /etc/shadow /etc/group /etc/init.d/opcagt /etc/rc3.d/S99opcagt /etc/rc0.d/K09opcagt /etc/rc1.d/K09opcagt /etc/vfstab /etc/init.d/ncs /etc/rc3.d/S76ncs /etc/rc0.d/K52ncs /etc/rc2.d/K52ncs Entry for the default VPO operator. Group entry for the default VPO operator. VPO startup and shutdown script. Creates file. Creates file. Creates file. On cluster client only, entry for mount /opt directory. NCS startup script (if not already present). Creates file (if not already present). Creates file (if not already present). Creates file (if not already present).

Chapter 10

305

About Sun Solaris Managed Nodes Organization of Managed Nodes

NOTE

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

306

Chapter 10

About Sun Solaris Managed Nodes Types of Libraries

Types of Libraries
Table 10-10 describes the managed node libraries for VPO A.05.xx, A.06.xx and A.07.xx. Table 10-10
Item NCS Library Libraries linked to the VPO library.

Libraries for the VPO Managed Nodes

VPO A.05.xx libopc.so 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 VPO A.06.xx libopc.so libov.a and libovutil.a are statically linked into libopc.so /usr/lib/libw.so.1 /usr/lib/libnck.a /usr/lib/libsocket. so.1 /usr/lib/libnsl.so.1 /opt/OV/lib/libopcas .so.1 VPO A.07.xx libopc.so /usr/lib/libsocket. so.1 /usr/lib/libnsl.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 /usr/platform/SUNW,\ Ultra-5_10/lib/libc_ psr.so.1

Link and compile options Description

-lopc -lnsp -lsocket -lnsl N/A

-lopc -lnsp -lsocket -lnsl N/A

-lopc -lnsp -lsocket -lnsl N/A

Chapter 10

307

About Sun Solaris Managed Nodes Types of Libraries Table 10-10

Item DCE Library Libraries linked to the VPO library.

Libraries for the VPO Managed Nodes

VPO A.05.xx libopc_r.so /opt/OV/dce/lib/lib dce.so /opt/OV/dce/lib/lib dcecrypt.so /usr/lib/libsocket. so.1 /usr/lib/libnsl.so. 1 /usr/lib/libw.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 VPO A.06.xx libopc_r.so /usr/lib/libm.so.1 /usr/lib/libthread. so.1 /opt/OV/dce/lib/libd ce.so /opt/OV/lib/libopcas .so /opt/OV/dce/lib/ \ libdcecrypt.so /usr/lib/libsocket. so.1 /usr/lib/libnsl.so.1 /usr/lib/libw.so.1 /usr/lib/libc.so.1 /usr/lib/libdl.so.1 /usr/lib/libmp.so.2 libc_psr.so.1a VPO A.07.xx libopc_r.so /opt/OV/dce/lib/libd ce.so /opt/OV/dce/lib/ \ libdcecrypt.so /usr/lib/libsocket. so.1 /usr/lib/libnsl.so.1 /usr/lib/libw.so.1 /opt/OV/lib/libopcas .so /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 /usr/platform/SUNW,\ Ultra-5_10/lib/libc_ psr.so.1 -lopc_r -lnsp -lnsl -ldce -lsocket -lthread -lm -lw N/A

Link and compile options Description

-lopc_r -lnsp -lnsl -ldce -lsocket -lthread -lm -lw N/A

-lopc_r -lnsp -lnsl -ldce -lsocket -lthread -lm -lw N/A

a. Location of the library libc_psr.so.1 is platform dependent.

About the Include File

On a Sun SPARCstation platform with Sun Solaris managed nodes, use the include file: /opt/OV/include/opcapi.h

308

Chapter 10

About Sun Solaris Managed Nodes Types of Libraries

About the Makefile

The following directory on the management server contains the makefiles for building executables: /opt/OV/OpC/examples/progs To build an executable with correct compile and link options, use the following makefiles: NCS Makef.solaris DCE Makef.solarisdce For more information about the managed node makefile, see the ReadMe file: /opt/OV/OpC/examples/progs/README

Chapter 10

309

About Sun Solaris Managed Nodes Support for Sun Enterprise E10000

Support for Sun Enterprise E10000

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

310

Chapter 10

About Sun Solaris Managed Nodes Support for Sun Enterprise E10000 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 Operating System 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. One Preconfigured Template Group VPO uses the following preconfigured template group for Sun Enterprise E100000: SSP

Chapter 10

311

About Sun Solaris Managed Nodes Support for Sun Enterprise E10000 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.

312

Chapter 10

About Sun Solaris Managed Nodes Support for Sun Enterprise E10000

About Encapsulated Logfiles

VPO provides the SSP Logfile Template for monitoring the domain- and platform-specific SSP logfiles shown in Table 10-11. Table 10-11 Logfile Encapsulated SSP Logfiles Description Domain specific netcon logfile Platform specific Template Name SSP Logfile SSP Logfile SSP Logfile

/var/opt/SUNWssp/adm/<domain_name>/messages /var/opt/SUNWssp/adm/<domain_name>/netcon /var/opt/SUNWssp/adm/messages

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.

Chapter 10

313

About Sun Solaris Managed Nodes Support for Sun Enterprise E10000 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. Table 10-12 Object Object Thresholds on the SSP system Threshold Polling Interval (Minutes) 3

Description

cbs

Monitors the cbs (control board server) daemon

0.5

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.

314

Chapter 10

About Sun Solaris Managed Nodes Support for Sun Enterprise E10000

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

About Sun Solaris Managed Nodes Support for Sun Enterprise E10000

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> 316 Chapter 10

About Sun Solaris Managed Nodes Support for Sun Enterprise E10000 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: /var/opt/SUNWssp/adm 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

About Sun Solaris Managed Nodes Support for Sun Enterprise E10000

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: /var/opt/SUNWssp/adm 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. Use the following menu sequence: 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.

318

Chapter 10

About Sun Solaris Managed Nodes Support for Sun Enterprise E10000 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

About Sun Solaris Managed Nodes Support for Sun Enterprise E10000 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.

320

Chapter 10

About Sun Solaris Managed Nodes About 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 Users Guide. The manual is available as an Acrobat Portable Document Format (PDF) document on the management server or on the Internet: Management Server /opt/OV/doc/C/OpC Internet http://ovweb.external.hp.com/lpe/doc_serv

Chapter 10

321

About Sun Solaris Managed Nodes High Availability Support on Sun Solaris

High Availability Support on Sun Solaris

This 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 Administrators 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 Administrators Reference Volume II.

322

Chapter 10

11

About Tru64 UNIX Managed Nodes

Chapter 11

323

About Tru64 UNIX Managed Nodes In this Chapter

In this Chapter
This chapter explains how to install and configure HP OpenView VantagePoint Operations (VPO) onTru64 UNIX managed nodes.

324

Chapter 11

About Tru64 UNIX Managed Nodes Installation Requirements

Installation Requirements
This section explains VPO hardware and software requirements for Tru64 UNIX managed nodes.

Hardware Requirements
Before installing VPO, make sure the Tru64 UNIX systems you select as managed nodes meet the following hardware requirements: Disk Space 35 MB (about 60 MB is required during software installation) Additional Swap Space None Additional RAM None

Chapter 11

325

About Tru64 UNIX Managed Nodes Installation Requirements

Software Requirements
Before installing VPO, make sure the following software is installed on Tru64 UNIX managed nodes: Operating System For a list of operating system versions supported by VPO, see the VPO Installation Guide for the Management Server. 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
_libcxx_V60200002 _libcxx_V60200003 _libcxx_V60300001 | 0004396996916008 | G | 0000000000000000 | 0004396996916016 | G | 0000000000000000 | 0004396996918728 | G | 0000000000000000

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 Administrators 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

326

Chapter 11

About Tru64 UNIX Managed Nodes Installation Requirements 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 Nodes Installing and De-installing Agents

Installing and De-installing Agents

This section describes how to install and de-install Tru64 UNIX managed nodes.

Tips for Installing Agents

When installing Tru64 UNIX 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 the name of the management server with the nslookup command. 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: mkdir -p /bigdisk/OV 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.

328

Chapter 11

About Tru64 UNIX Managed Nodes Installing and De-installing Agents

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 lpr.debug /var/adm/messages /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

About Tru64 UNIX Managed Nodes Installing and De-installing Agents

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

About Tru64 UNIX Managed Nodes Installing and De-installing Agents 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

About Tru64 UNIX Managed Nodes Installing and De-installing Agents

Installing Agents
For standard installation instructions, see the VPO Administrators Reference Volume I. If errors occur during the installation, check the local installation logfile: /var/adm/smlogs/setld.log

Installing Agents Manually

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. 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/dec/ \ alpha/unix/A.07.00/RPC_DCE_[TCP|UDP]/ 2. Install the agent using the command: /tmp/opc_inst

332

Chapter 11

About Tru64 UNIX Managed Nodes Installing and De-installing Agents

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 To activate the node from the VPO GUI, follow these steps: 1. Add the pre-installed nodes to the VPO Node Bank window. Use the following 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. Open the Install/Update VPO Software and Configuration window. Use the following menu sequence: Actions-> Agents-> Install / Update SW & Config.

Chapter 11

333

About Tru64 UNIX Managed Nodes Installing and De-installing Agents

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>

334

Chapter 11

About Tru64 UNIX Managed Nodes Installing and De-installing Agents 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. 2. Add the pre-installed nodes to the VPO Node Bank window. Use the following menu sequence: Actions-> Node-> Add. 3. Add the node to a VPO node group. Drag and drop the node onto a node group in the VPO Node Group Bank window. 4. Activate the node. Enter the following: /opt/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, such as startup script in 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 Administrators Reference Volume I and the man page opcactivate(1M).

Chapter 11

335

About Tru64 UNIX Managed Nodes Installing and De-installing Agents

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: /opt/OV/bin/OpC/opcsw -installed <node> 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.

De-installing Agents
De-installing Agents with Standard De-installation For standard de-installation instructions, see the VPO Administrators Reference Volume I. If errors occur during the de-installation, check the local de-installation logfile: /var/adm/smlogs/setld.log To De-install an Agent Manually To de-install an agent manually, follow these steps: 1. Stop all VPO agents running on the managed node. 2. De-install the VPO agent software from the managed nodes by entering: setld -d OPCAGT000 OPCCOMMAGT000 OPCPERFAGT000

336

Chapter 11

About Tru64 UNIX Managed Nodes About Preconfigured Elements

About Preconfigured Elements

This section describes preconfigured templates, template groups, and applications used by VPO on Tru64 UNIX managed nodes.

One Preconfigured Template Group

VPO uses one preconfigured template group: Digital UNIX

Types of Default Logfile Templates

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 Logfile /var/adm/cron/log /var/adm/messages a /usr/adm/sialog b /var/adm/wtmp /usr/adm/lplog c Description Cron logfile Operating system messages SIA logfile History of logins Line printer daemon logfile Template Name Cron OS Msgs SIA Logs Lplog

a. /var/adm/messages must be present in the /etc/syslog.conf file b. 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

About Tru64 UNIX Managed Nodes About Preconfigured Elements

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.

338

Chapter 11

About Tru64 UNIX Managed Nodes About Preconfigured Elements

Types of Default Monitored Objects

Table 11-2 describes the default monitored objects used by VPO on Tru64 UNIX managed nodes. Table 11-2 Object Object Thresholds on the Managed Nodes Description Threshold Polling Interval (Minutes) 2 10 5 2 5 5 5

cpu_util disk_util Inetd MailQueue Length sendmail swap_util Syslogd

Monitors CPU utilization. Requires the sar program. Monitors disk space utilization on the root disk. Number of executing instances of inetd (Internet Daemon). Length of the sendmail queue. Number of unsent mail messages. Number of executing instances of sendmail. Monitors SWAP utilization. Checks whether syslogd is running.

95% 90% 0.5 30 0.5 80% 0.5

Types of Default Applications

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

Chapter 11

339

About Tru64 UNIX Managed Nodes Distributing Scripts and Programs

Distributing Scripts and Programs

For Tru64 UNIX managed nodes, the platform selector and architecture identifier is the following: dec/alpha/unix

Location of User Scripts and Programs

Table 11-3 shows the location of user scripts and programs provided on the management server. Table 11-3 Location of User Scripts and Programs on the Management Server Location /var/opt/OV/share/databases/OpC/mgd_node/customer\ /dec/alpha/unix/actions/*

Script/Program Automatic actions, operator-initiated actions, and scheduled actions Monitoring scripts and programs used by the monitoring agent and the logfile encapsulator Scripts and programs called through command broadcast or started from the Application Desktop

/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/*

340

Chapter 11

About Tru64 UNIX Managed Nodes Distributing Scripts and Programs

About Temporary Directories

Table 11-4 shows the temporary directories for distributed scripts and programs on the managed nodes. Table 11-4 Temporary Directories for Distributed Scripts and Programs on the Managed Nodes Managed Node DEC Alpha AXP Operating System Tru64 UNIX Temporary Directory

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

About Target Directories

Table 11-5 shows the target directories for distributed scripts and programs on the managed nodes. Table 11-5 Target Directories for Distributed Scripts and Programs on the Managed Nodes Operating System Tru64 UNIX Target Directory Access Rights

Managed Node DEC Alpha AXP

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

rwxr-xr-x (owner:root) rwxr-xr-x (owner:root) rwxr-xr-x (owner:root)

Chapter 11

341

About Tru64 UNIX Managed Nodes Organization of Managed Nodes

Organization of Managed Nodes

Figure 11-1 shows how VPO software is organized on Tru64 UNIX managed nodes. Figure 11-1 VPO Software on Tru64 UNIX Managed Nodes /usr/opt/OV /var/opt/OV

locale <lang>

contrib OpC

bin OpC

lib include

databases

conf

tmp

log OpC

bin OpC

OpC BBC OpC bin conf

LC_MESSAGES

install

utils

B
Key:

monitor

cmds

actions

Location of Files
On Tru64 UNIX managed nodes, files are located as follows: Process-related Files /var/opt/OV/tmp/OpC Agent Configuration Files /var/opt/OV/conf/OpC

342

Chapter 11

About Tru64 UNIX Managed Nodes Organization of Managed Nodes

About the Default VPO Operator

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. About Default VPO Operator Entries The default VPO operator appears in the following directory: /etc/passwd Fields include the following: User Name opc_op

Encrypted Password * (no login) User-ID Group-ID Description Either 777 (if still available) or next possible free number Either 77 (if still available) or next possible free number Default VPO operator

Home Directory /usr/users/opc_op Login Shell /bin/sh

Chapter 11

343

About Tru64 UNIX Managed Nodes Organization of Managed Nodes About Default VPO Operator Group Entries The default VPO operator group appears in the following directory: /etc/group Fields include the following: Group Name opcgrp

Encrypted Password Empty Group-ID Users Description 77 or higher opc_op Default VPO operator group

Types of System Resources

During installation, VPO makes changes in the following system resource files: /etc/passwd /etc/shadow (if present) Default VPO operator entry and Protected Password Database (if present). Default VPO operator group entry. VPO startup and shutdown script. Creates the K01opcagt file. Creates the K01opcagt file. Creates the S97opcagt file.

/etc/group /sbin/init.d/opcagt /sbin/rc0.d /sbin/rc2.d /sbin/rc3.d

NOTE

If you are working with Network Information Services (NIS or NIS+), you should adapt the user registration accordingly.

344

Chapter 11

About Tru64 UNIX Managed Nodes Types of Libraries

Types of Libraries
Table 11-6 describes the managed node libraries for VPO A.05.xx, A.06.xx, and A.07.xx. Table 11-6
Item DCE Library Libraries linked to the VPO library

Libraries for the VPO Managed Nodes

VPO A.05.xx libopc_r.so /usr/shlib/libiconv. so /usr/shlib/libdce.so /usr/shlib/libdce_r. so (optional) /usr/shlib/libphtrea ds.so /usr/shlib/libpthrea d.so /usr/shlib/libmach.s o /usr/shlib/libexc.so /usr/shlib/libc.so /usr/shlib/libcxx.so VPO A.06.xx libopc_r.so /usr/shlib/libiconv .so /usr/shlib/libdce.s o /usr/shlib/libdce_r .so (optional) /usr/shlib/libphtre ads.so /usr/shlib/libpthre ad.so /usr/shlib/libmach. so /usr/shlib/libexc.s o /usr/shlib/libc.so /usr/shlib/libcxx.s o VPO A.07.xx libopc_r.so /usr/shlib/libiconv .so /usr/shlib/libdce.s o /usr/shlib/libdce_r .so (optional) /usr/shlib/libphtre ads.so /usr/shlib/libpthre ad.so /usr/shlib/libmach. so /usr/shlib/libexc.s o /usr/shlib/libc.so /usr/shlib/libcxx.s o /usr/opt/OV/lib/lib nsp.so

Link and compile options Description

-lopc_r

-lopc_r

-lopc_r

N/A

N/A

N/A

Chapter 11

345

About Tru64 UNIX Managed Nodes Types of Libraries Table 11-6

Item NCS Library Libraries linked to the VPO library

Libraries for the VPO Managed Nodes

VPO A.05.xx N/A N/A VPO A.06.xx libopc.so /usr/lib/libnck.a /usr/lib/libc.a /usr/shlib/libiconv .so /usr/shlib/libcxx.s o VPO A.07.xx libopc.so /usr/lib/libnck.a /usr/lib/libc.a /usr/shlib/libiconv .so /usr/shlib/libcxx.s o -lopc

Link and compile options Description

N/A

-lopc

N/A

N/A

N/A

About the Include File

On a DEC Digital AXP platform with Tru64 UNIX managed nodes, use the include file: /usr/opt/OV/include/opcapi.h

346

Chapter 11

About Tru64 UNIX Managed Nodes Types of Libraries

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.dec For more information about the managed node makefile, see the ReadMe file: /opt/OV/OpC/examples/progs/README

NOTE

For building executables on Tru64 UNIX nodes, OSFINCLUDE440 Standard Header Files package is required.

Chapter 11

347

About Tru64 UNIX Managed Nodes Types of Libraries

348

Chapter 11

12

About Windows NT/2000 Managed Nodes

Chapter 12

349

About Windows NT/2000 Managed Nodes In this Chapter

In this Chapter
This 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.

350

Chapter 12

About Windows NT/2000 Managed Nodes Installation Requirements

Installation Requirements
This section explains VPO hardware and software requirements for Microsoft Windows NT/2000 managed nodes.

Hardware Requirements
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

About Windows NT/2000 Managed Nodes Installation Requirements 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 NTFSformatted 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.

352

Chapter 12

About Windows NT/2000 Managed Nodes Installation Requirements

Software Requirements
Before installing VPO, make sure the following software is installed on Windows managed nodes: Operating System For a list of operating system versions supported by VPO, see the VPO Installation Guide for the Management Server. 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. Name of Management Server 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 operators account.

Chapter 12

353

About Windows NT/2000 Managed Nodes Installation Requirements

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.

354

Chapter 12

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

Installing and De-installing Agents

This 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

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

Figure 12-1 shows how to install Windows managed nodes. Figure 12-1 Installing the VPO Windows Agent Package VPO Management Server

ftp installation Stand-alone Windows System ftp installation Possible only if Domain 2 gives administrative rights to the HP ITO account in

Domain Controller

standard installation

Domain Controller

standard installation

TRUST

standard installation

Windows Domain 1

Windows Domain 2

356

Chapter 12

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

Methods for Installing Agents

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. Standard Installation 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. See Installing Agents with Standard Installation on page 367. 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 Windows NT/2000 Managed Nodes Installing and De-installing Agents

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. Required User Rights for the HP ITO account Required in VPO By Windows installation server. By VPO action agent to switch user. By the action agent to switch user for application execution. By VPO agent, which runs as a service. During action execution. By the action agent to switch user. By the shutdown application.

Table 12-1 User Right

Access a computer from the network. Act as part of the operating system. Increase quotas. Log in as a service. Manage auditing and security log. Replace a process-level token. Shut down the system.

358

Chapter 12

About Windows NT/2000 Managed Nodes Installing and De-installing Agents 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

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

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.

360

Chapter 12

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

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

About Windows NT/2000 Managed Nodes Installing and De-installing Agents 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 administrators user name, or even anonymous if the FTP server allows it. If you are using the administrators user name, anonymous FTP access must be disabled on the node.

362

Chapter 12

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

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

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

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.

364

Chapter 12

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

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 MSDOS 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

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

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.

366

Chapter 12

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

Installing Agents with Standard Installation

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 Administrators 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

About Windows NT/2000 Managed Nodes Installing and De-installing Agents 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. 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 it should appear in the VPO Node Bank. Example: ntworkstation

368

Chapter 12

About Windows NT/2000 Managed Nodes Installing and De-installing Agents 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. 6. In the Node Communication Options window, fill in the following fields: 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

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

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: a. Click the new icon to highlight it. b. Choose Actions:Agents->Install/ Update SW & Config. 12. Under Target Nodes, do this: a. Select [Nodes in list requiring update]. b. Click [Get Map Selection]. The node name appears in the window.

370

Chapter 12

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

13. Under Components, do this: a. Select [Agent Software]. b. Click [OK]. The installation begins. A new shell opens and starts the installation script. 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. 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

About Windows NT/2000 Managed Nodes Installing and De-installing Agents 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 reinstall 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.

372

Chapter 12

About Windows NT/2000 Managed Nodes Installing and De-installing Agents 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. Check the Installation Requirements on page 351. 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 5. In the Node Communication Options window, fill in the following fields: 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

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

8. 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. 9. Under Target Nodes, do this: a. Select [Nodes in list requiring update]. b. Click [Get Map Selection]. The node name appears in the window. 10. Under Components, do this: a. Select [Agent Software]. b. Click [OK]. The installation begins. A new shell opens and starts the installation script. 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. 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. 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.

374

Chapter 12

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

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

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

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.

376

Chapter 12

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

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

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

3. Create the following file on the managed node: Directory C:\temp File nodeinfo Contents OPC_NODE_TYPE CONTROLLED OPC_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: /opt/OV/bin/OpC/opcsw -installed <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. 378 Chapter 12

About Windows NT/2000 Managed Nodes Installing and De-installing Agents

De-installing Agents
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.

De-installing Agents with Standard De-installation For standard de-installation instructions, see the VPO Administrators Reference Volume I. To De-install an Agent Manually 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 If errors occur during the de-installation, check the local de-installation logfile: c:\temp\inst.log

Chapter 12

379

About Windows NT/2000 Managed Nodes About Preconfigured Elements

About Preconfigured Elements

This 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 Windows Version Windows NT Template Groups for Windows Systems Template Group Windows NT SMS Windows 2000 Terminal Server/Citrix MetaFrame Template Groups Windows 2000 Terminal Server/MetaFrame Terminal Server a MetaFrame a a. Contained within the Terminal Server/MetaFrame template group.

380

Chapter 12

About Windows NT/2000 Managed Nodes About Preconfigured Elements

Types of Default Logfile Templates

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 Logfile DNS Server Directory Service File Replication Service Encapsulated Logfiles on Windows 2000 Managed Nodes Description Monitors the DNS Server EventLog Monitors the Directory Service EventLog Monitors the File Replication Service EventLog Template Name dflt_DNSEvLog (2000) dflt_DirectoryEvLog (2000) dflt_FileReplicationEvLog (2000)

Chapter 12

381

About Windows NT/2000 Managed Nodes About Preconfigured Elements 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 Description NT system eventlog for Terminal Server Template Name System Log (Terminal Server)

Logfile SYSTEM_LOG

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.

382

Chapter 12

About Windows NT/2000 Managed Nodes About Preconfigured Elements

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

About Windows NT/2000 Managed Nodes About Preconfigured Elements Viewing Eventlogs in the Message Browser Table 12-5 shows how eventlog fields are displayed in the message browser. Table 12-5 Eventlog Field Date Time Event ID Eventlog to Message Browser Field Correlation Message Browser Field Date Time Message Text Comments The date that the event was created on managed node. The time the event was created on managed node. The Event ID will appear before any additional message texta. None None

Source Type information warning error success audit failure audit Category Description User Computer

Application Severity normal warning critical normal warning Object Message Text Not mapped Node Msg Group

None All other message text (after the Event ID). Not mapped. The name of the node as it is known to the management server. Empty.

a. Formatted as: EventID: 0xnnnnnnnn (ai) - description text

384

Chapter 12

About Windows NT/2000 Managed Nodes About Preconfigured Elements

Types of Default opcmsg Message Templates

Table 12-6 shows the opcmsg message templates that are available for Windows managed nodes. Table 12-6 Name opcmsg(1|3) opcmsg Message Templates on Windows Managed Nodes Description Default interception of messages submitted by opcmsg(1) and opcmsg(3).

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.

NOTE

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

Chapter 12

385

About Windows NT/2000 Managed Nodes About Preconfigured Elements 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. 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.

386

Chapter 12

About Windows NT/2000 Managed Nodes About Preconfigured Elements 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 12

387

About Windows NT/2000 Managed Nodes About Preconfigured Elements

Types of Default Monitored Objects

Table 12-7 describes the default monitored objects used by VPO on Windows managed nodes. Table 12-7 Object Object Thresholds on Windows Managed Nodes Description Threshold Polling Interval (Minutes) 10 1 30 5 5

dflt_disk_util_NT a dflt_cpu_util_NT dflt_rpcss_NT b TS_Licensing TS_Service

Windows NT monitor for disk space utilization on disk drive C. Windows NT/2000 monitor for CPU utilization. Windows NT RPC service. Checks if Terminal Server licensing service is running. Checks if Terminal Server service is running.

10% 95% 90% 1 1

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.

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

388

Chapter 12

About Windows NT/2000 Managed Nodes About Preconfigured Elements

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 NTPerfMon\\LogicalDisk\\% Free Space\\0\\C:

Instance Parent Instance Counter Object 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.

Chapter 12

389

About Windows NT/2000 Managed Nodes About Preconfigured Elements 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.

390

Chapter 12

About Windows NT/2000 Managed Nodes About Preconfigured Elements 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 Nodes Types of Default Applications

Types of Default Applications

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

392

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications

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 hardware Returns operating system information. 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 nonwdrives Returns network information. 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

About Windows NT/2000 Managed Nodes Types of Default Applications drives Returns the information listed below for each drive: DRIVE NAME TYPE Returns current drive letter. Returns any name that is assigned to that drive. 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 FREE Returns the total size of the drive in MB. 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.).

394

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications 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 nonidle 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

About Windows NT/2000 Managed Nodes Types of Default Applications 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.

396

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications

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 User Configurable Parameters /enum X /key <NAME> /initkey Returns the subtrees from the specified key. Information is printed out to the depth specified by X. Defines the starting point of the subtree to be processed. Defines in which registry have to search for <key>.

NOTE

For a full description of the Windows registry, see the Windows documentation.

Description of Values Returned See the User Configurable Parameters for this application, as well as the Windows documentation.

Chapter 12

397

About Windows NT/2000 Managed Nodes Types of Default Applications

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 User Configurable Parameters For a full description of creating and removing scheduled jobs, see the Windows documentation.

398

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications

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 User Configurable Parameters For a full description of net.exe, see the Windows documentation. Description of Values Returned Computer User name The name of the system that has made the connection. 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. The number of open resources associated with the connection. Time since this connection was last used.

Opens Idle time

Chapter 12

399

About Windows NT/2000 Managed Nodes Types of Default Applications

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 User Configurable Parameters See About Show Users on page 416. Description of Values Returned See About Show Users on page 416.

400

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications

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 User Configurable Parameters SeeAbout Diagnostics on page 393. Description of Values Returned See About Diagnostics on page 393.

Chapter 12

401

About Windows NT/2000 Managed Nodes Types of Default Applications

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 User Configurable Parameters For a full description of nbstat.exe, see the Windows documentation.

402

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications

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 User Configurable Parameters /a /o <string> By default, returns all the performance monitor objects found on the system. 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. By default, returns a maximum of ten instances. If more are defined it will print out the message MULTIPLE INSTANCES, TOO MANY TO LIST. Returns a full list and prints all instances, no matter how many are defined.

/s

/f

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

About Windows NT/2000 Managed Nodes Types of Default Applications Description of Values Returned Refer to the User Configurable Parameters section for this application.

404

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications

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 User Configurable Parameters /pid <process id> /name <process name> /f /l Kill process with id <process id> Kill all processes with name <process name>. Forced kill without notification. 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.

Description of Values Returned See the User Configurable Parameters section for this application.

Chapter 12

405

About Windows NT/2000 Managed Nodes Types of Default Applications

About Reboot
This application will shutdown and reboot the selected Windows nodes. Default itosdown.exe /t 120 /r /w User Configurable Parameters /m <msg> /t <sec> /a /r Returns shutdown <msg> in a popup window on the node. Specifies the delay (in seconds) before the system shutdown occurs. Aborts a VPO initiated system shutdown. Automatic reboot after shutdown. If this option is not set, the system shuts down. It can then only be restarted manually. 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. 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.

/f

/w

Description of Values Returned See the User Configurable Parameters section for this application.

406

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications

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\HewlettPackard\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

About Windows NT/2000 Managed Nodes Types of Default Applications

User Configurable Parameters /initkey lm|cu|cr|us Define initial registry key: lm cu cr us <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. KEY_LOCAL_MACHINE KEY_CURRENT_USER KEY_CLASSES_ROOT KEY_USERS

408

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications /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 Windows NT/2000 Managed Nodes Types of Default Applications

About Server Config

This application displays settings for the Server service for the selected Windows node. Default net.exe config server User Configurable Parameters For a full description of net.exe, see the Windows documentation. Description of Values Returned Server Name Comment Name of the server 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 servers 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.

410

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications

About Server Stats

This application displays in-depth statistics about the Server service for the selected Windows node. Default net.exe statistics server User Configurable Parameters For a full description of net.exe, see the Windows documentation. Description of Values Returned For a full description of net.exe, see the Windows documentation.

Chapter 12

411

About Windows NT/2000 Managed Nodes Types of Default Applications

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 User Configurable Parameters None. Description of Values Returned Share name Resource Remark Full name of the available netbios share. Location of the share on the local system. 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.

412

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications

About Show Drivers

This application lists all drivers that are present on the selected Windows node. Default itomserv.exe /list d User Configurable Parameters See About Show Services on page 414. Description of Values Returned NAME DISPLAY STATUS True name of the service. If you wish to perform actions on the service, this is the name that should be used. Description of the service. This is the name that is normally seen when working with the control panel. 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 Disabled Service can be started by a user or a dependent service. Service cannot be started.

Chapter 12

413

About Windows NT/2000 Managed Nodes Types of Default Applications

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 User Configurable Parameters /start <servicename> /stop <servicename> /pause <servicename> /continue <servicename> /list s | d | a s d a /e 0 1 2 3 4 5 6 Start service <servicename>. Stop service <servicename>. Pause service <servicename>. Continue service <servicename>. Print a list of installed services: List all Windows system services. List all Windows device drivers. List all installed services. Set the exit status to a numerical value: RUNNING NOT_RUNNING START_PENDING STOP_PENDING CONTINUE_PENDING PAUSE_PENDING 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

414

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications Description of Values Returned Name Display Status Internal name of the service. Name that is normally displayed to the user. 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 Manual Disabled N/A Service starts every time the system starts. Service can be started by a user or a dependent service. Service cannot be started. User does not have the rights to obtain in-depth information about the service.

Chapter 12

415

About Windows NT/2000 Managed Nodes Types of Default Applications

About Show Users

This application displays information about local users and sessions on the selected Windows Node. Default itouser.exe /u User Configurable Parameters /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 /ns /local Returns number of users logged on by the system. Returns number of sessions on the system. Returns the name of user logged into the local system.

Description of Values Returned See the User Configurable Parameters section for this application.

416

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications

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> User Configurable Parameters See About Show Services on page 414.

Chapter 12

417

About Windows NT/2000 Managed Nodes Types of Default Applications

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> User Configurable Parameters See About Show Services on page 414.

418

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications

About TCP/IP Status

This application displays protocol statistics and current active TCP/IP network connections for the selected Windows node. Default netstat.exe User Configurable Parameters See the Windows documentation. Description of Values Returned 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 Windows NT/2000 Managed Nodes Types of Default Applications

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 User Configurable Parameters For a full description of net.exe, see the Windows documentation. Description of Values Returned Status State of the connection (for example, OK, Disconnected means that the drive connection is defined but not connected). Letter of the local drive used to access the connection. Name of the system and the share that is used. Type of network that is providing the connection (for example, Microsoft Windows Network, or 3rd party NFS software).

Local Remoted Network

420

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications

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 User Configurable Parameters 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 Windows NT/2000 Managed Nodes Types of Default Applications

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 User Configurable Parameters None.

422

Chapter 12

About Windows NT/2000 Managed Nodes Types of Default Applications

About Workst Stats

This application displays in-depth statistics about the workstation service for the selected Windows node. Default net.exe statistics workstation User Configurable Parameters For a full description of net.exe, refer to the Windows documentation. Description of Values Returned For a full description of net.exe, refer to the Windows documentation.

Chapter 12

423

About Windows NT/2000 Managed Nodes Distributing Scripts and Programs

Distributing Scripts and Programs

For Windows NT/2000 managed nodes, the platform selector and architecture identifier is the following: ms\intel\nt

Location of User Scripts and Programs

Table 12-9 shows the location of user scripts and programs provided on the management server. Table 12-9 Location of User Scripts and Programs on the Management Server Location /var/opt/OV/share/databases/OpC/mgd_node/customer/ /ms/intel/nt/actions/*

Script/Program Automatic actions, operator-initiated actions, and scheduled actions Monitoring scripts and programs used by the monitoring agent and the logfile encapsulator Scripts and programs called through command broadcast or started from the Application Desktop

/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/*

424

Chapter 12

About Windows NT/2000 Managed Nodes Distributing Scripts and Programs

About Temporary Directories

Table 12-10 shows the temporary directories for distributed scripts and programs on the managed nodes. Table 12-10 Temporary Directories for Distributed Scripts and Programs on the Managed Nodes Operating System Windows Temporary Directory

Managed Node Intel 486 or higher

\usr\OV\tmp\OpC\bin\actions \usr\OV\tmp\OpC\bin\cmds \usr\OV\tmp\OpC\bin\monitor

About Target Directories

Table 12-11 shows the target directories for distributed scripts and programs on the managed nodes. Table 12-11 Target Directories for Distributed Scripts and Programs on the Managed Nodes Operating System Windows Directory Access Rights 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)

Managed Node Intel 486 or higher

\usr\OV\bin\OpC\actions

Chapter 12

425

About Windows NT/2000 Managed Nodes Organization 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

\usr\OV

log OpC

bin contrib conf

databases include

tmp OpC

lib C conf

nls

OpC OpC OpC BBC OpC mgd_node bin

<lang> <country>

utils

install

vendor

B
<codeset>

Key:

monitor

cmds

actions

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.

426

Chapter 12

About Windows NT/2000 Managed Nodes Organization of Managed Nodes

Location of Files
On Windows managed nodes, files are located as follows: Process-related Files \usr\OV\tmp\OpC Agent Configuration Files \usr\OV\conf\OpC

About the Default VPO Operator

Table 12-12 shows the VPO user accounts on Windows managed nodes. Table 12-12 VPO User Accounts on Windows Managed Nodes Entry HP ITO account Defined during installation Administratorsb or Domain Administratorc HP VPO agent account None opc_op Same as HP ITO accounta Users or Domain Users

Field User Name Password

Group

Description Login Shell

HP VPO operator account None

a. All other properties assume the default value b. Standalone or domain members c. Domain Controller

Chapter 12

427

About Windows NT/2000 Managed Nodes Organization of Managed Nodes

Types of System Resources

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

428

Chapter 12

About Windows NT/2000 Managed Nodes VPO Managed Node Libraries

VPO Managed Node Libraries

Table 12-13 describes the managed node libraries for VPO A.05.xx, A.06.xx, and A.07.xx. Table 12-13
Item Library

Libraries for the VPO Managed Nodes

VPO A.05.xx libopc.dll opcapi.dll VPO A.06.xx libopc.dll opcapi.dll VPO A.07.xx libopc.dll opcapi.dll opcas.dll libnsp.dll pdh.dll

Libraries linked to the VPO library Link and compile options Description

N/A

N/A

N/A

N/A

N/A

N/A

Use *.mak files to build

Use *.dsp files to build

Use *.dsp files to build

About the Include File

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:/ /opt/OV/OpC/examples/progs/README Chapter 12 429

About Windows NT/2000 Managed Nodes About Citrix MetaFrame Integration

About Citrix MetaFrame Integration

You 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

430

Chapter 12

About Windows NT/2000 Managed Nodes About Citrix MetaFrame Integration

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

About Windows NT/2000 Managed Nodes About Citrix MetaFrame Integration 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.

432

Chapter 12

About Windows NT/2000 Managed Nodes About Citrix MetaFrame Integration

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 Object Thresholds on Citrix MetaFrame Managed Nodes Description Threshold Polling Interval (Minutes) 5 5 5 5

TS_Licensing TS_Service MF_ICA_Browser MF_Prog_ Neighbourhood

Checks if Terminal Server licensing service is running. Checks if Terminal Server service is running. Checks if MetaFrame ICA Browser service is running. Checks if the MetaFrame ICA Program Neighbourhood service is running.

1 1 1 1

Chapter 12

433

About Windows NT/2000 Managed Nodes About Citrix MetaFrame Integration

Types of MetaFrame Logfile Templates

Table 12-15 shows encapsulated logfiles and associated templates used on Citrix MetaFrame managed nodes. Table 12-15 Encapsulated Logfiles on Managed Nodes running Windows NT Terminal Server and Citrix MetaFrame Description NT system eventlog for Terminal Server NT system eventlog for MetaFrame Template Name System Log (Terminal Server) System Log (MetaFrame)

Logfile SYSTEM_LOG SYSTEM_LOG

NOTE

Although there is a logfile template available for NT Terminal Server, you should only use the logfile template for Citrix MetaFrame.

434

Chapter 12

About Windows NT/2000 Managed Nodes Types of Citrix MetaFrame Applications

Types of Citrix MetaFrame Applications

Citrix 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> User Configurable Parameters <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

About Windows NT/2000 Managed Nodes Types of Citrix MetaFrame Applications User Configurable Parameters username session /FAIL Returns the name of the user. Returns the session duration. 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:

436

Chapter 12

About Windows NT/2000 Managed Nodes Types of Citrix MetaFrame Applications

Default license

About Processes
Displays the status of all user processes, one process per line. Default processes User Configurable Parameters sessionname processid username programname Returns the name of the session. Returns the process ID. Returns the username. 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

About Windows NT/2000 Managed Nodes Types of Citrix MetaFrame Applications User Configurable Parameters </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> User Configurable Parameters <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> User Configurable Parameters /SERVER:server_name Returns the users logged on the specified server.

438

Chapter 12

About Windows NT/2000 Managed Nodes About SMS Integration

About SMS Integration

The 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

About Windows NT/2000 Managed Nodes About SMS Integration 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 DWN Sends VPO a message when the service is running again. This monitor never has an associated action. 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.

440

Chapter 12

About Windows NT/2000 Managed Nodes About SMS Integration 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

About Windows NT/2000 Managed Nodes About SMS Integration 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 SMS Service Client Configuration Manager Restarta OA none Executive OA none Hierarchy Manager AA none Inventory Agent OA none Package Command Manager OA none Site Configuration Manager AA none Trap Filter none none

VPO-SMS Monitors NT_DWN_SMS_CLIENT_CONFIG_MANAGER NT_UP_SMS_CLIENT_CONFIG_MANAGER NT_DWN_SMS_EXECUTIVE NT_UP_SMS_EXECUTIVE NT_DWN_SMS_HIERARCHY_MANAGER NT_UP_SMS_HIERARCHY_MANAGER NT_DWN_SMS_INVENTORY_AGENT NT_UP_SMS_INVENTORY_AGENT NT_DWN_SMS_PACKAGE_COMMAND_MANAGER NT_UP_SMS_PACKAGE_COMMAND_MANAGER NT_DWN_SMS_SITE_CONFIG_MANAGER NT_UP_SMS_SITE_CONFIG_MANAGER NT_DWN_SMS_TRAP_FILTER NT_UP_SMS_TRAP_FILTER

a. OA = Operator Action; AA= Automatic Action

442

Chapter 12

About Windows NT/2000 Managed Nodes About SMS Integration

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 VPO Message Group Jobs

SMS Message All messages containing one of the following words: Compress Instruction Inventory Job Package All SMS network errors that are not related to jobs. All SMS security errors that are not related to jobs. All SMS database errors that are not related to jobs. All remaining errors.

Network Security DB OS

Chapter 12

443

About Windows NT/2000 Managed Nodes About SMS Integration 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 VPO Message Objects Configuration

SMS Events All events that are related to setup, installation, and configuration. All events that can be related to inventory collection. All events that can be related to package distribution. All events that can be related to application errors. All remaining events.

Inventory Distribution Application Miscellaneous

444

Chapter 12

About MC/ServiceGuard

Appendix A

445

About MC/ServiceGuard In this Appendix

In this Appendix
This 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.

446

Appendix A

About MC/ServiceGuard What 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

About MC/ServiceGuard What is MC/ServiceGuard?

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. 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. Node on which the package is running before MC/ServiceGuard initiates a transfer of control. 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. IP/hostname of the VPO package. This can sometimes be referred to as Virtual or Relocatable IP/hostname. Node on which the package is currently running.

MC/Service Guard Daemon (cmcld)

original node

package

package IP/hostname

package custody

448

Appendix A

About MC/ServiceGuard What is MC/ServiceGuard? 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/ServiceGuard How MC/ServiceGuard Works

How MC/ServiceGuard Works

This 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
Bridge LAN 1

MC/ServiceGuard Package Switchover (Before)

LAN 0

Package A Root 1

Package C Root 2

Package D Package E Package F Root 3

Package B Node 1 Node 2 Root 2 Mirror

Node 3

Package A Disk

Package B Disk

Package C Disk

Package D Disk

Package E Disk

Package F Disk

Package A Mirror

Package B Mirror

Package C Mirror

Package D Mirror

Package E Mirror

Package F Mirror

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.

450

Appendix A

About MC/ServiceGuard How MC/ServiceGuard Works 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)
LAN 0 Bridge LAN 1

Package C Root 1 Package A Node 1 Node 2 Root 2 Mirror Root 2

Package D Package E Package F Node 3 Root 3

Package A Disk

Package B Disk

Package C Disk

Package D Disk

Package E Disk

Package F Disk

Package A Mirror

Package B Mirror

Package C Mirror

Package D Mirror

Package E Mirror

Package F Mirror

Appendix A

451

About MC/ServiceGuard How MC/ServiceGuard Works

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 Bridge LAN 1 NODE 1 LAN 0 LAN 1 NODE 2 LAN 0

LAN 1

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.

452

Appendix A

About MC/ServiceGuard How MC/ServiceGuard Works Figure A-4 MC/ServiceGuard LAN Switchover (After)

LAN 0 Bridge LAN 1 NODE 1 LAN 0 LAN 1 NODE 2 LAN 0

LAN 1

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.

Appendix A

453

About MC/ServiceGuard How MC/ServiceGuard Works Figure A-5

NODE 1 Package A

MC/ServiceGuard Redundant Data and Heartbeat Subnets

NODE 2 Package B Package C

Dedicated Heartbeat LAN

LAN 0

Subnet B

Primary LAN: Heartbeat/Data

LAN 3

Bridge Standby LAN: Heartbeat/Data LAN 1

Subnet A

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.

454

Appendix A

About MC/ServiceGuard Assigning IP Addresses and Hostnames

Assigning IP Addresses and Hostnames

MC/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/ServiceGuard Running VPO in an MC/ServiceGuard Environment

Running VPO in an MC/ServiceGuard Environment

MC/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.

456

Appendix A

About MC/ServiceGuard Running VPO in an MC/ServiceGuard Environment

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
MC/ServiceGuard Node1 VPO/NNM Server binaries MC/ServiceGuard Node 2 VPO/NNM Server binaries

shared files

VPO Agent

Oracle binaries

VPO Agent

RDMS

active connections if the VPO server is running on Node 1 active connections if the VPO server is running on Node 2

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.

Appendix A

457

About MC/ServiceGuard Running VPO in an MC/ServiceGuard Environment

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.

458

Appendix A

About MC/ServiceGuard Troubleshooting VPO MC/ServiceGuard Packages

Troubleshooting VPO MC/ServiceGuard Packages

This 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/ServiceGuard Troubleshooting VPO MC/ServiceGuard Packages

460

Appendix A

Administration of Sun Enterprise Clusters

Appendix B

461

Administration of Sun Enterprise Clusters In this Appendix

In this Appendix
This 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.

462

Appendix B

Administration of Sun Enterprise Clusters What 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

Administration of Sun Enterprise Clusters What are Sun Clusters?

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. 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. 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. When one host assumes responsibility for the services of another 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. 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. 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.

CCDD

Data Service

failover logical host

switchover

takeover

464

Appendix B

Administration of Sun Enterprise Clusters What are Sun Clusters?

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

Administration of Sun Enterprise Clusters What are Sun Clusters?

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

466

Appendix B

Administration of Sun Enterprise Clusters What are Sun Clusters? 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 Clusters Running VPO Agents in a Sun Cluster Environment

Running VPO Agents in a Sun Cluster Environment

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

468

Appendix B

Administration of Sun Enterprise Clusters Troubleshooting VPO in a Sun Cluster Environment

Troubleshooting VPO in a Sun Cluster Environment

This 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

Administration of Sun Enterprise Clusters Troubleshooting VPO in a Sun Cluster Environment 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. 470 Appendix B

Administration of Sun Enterprise Clusters Troubleshooting VPO in a Sun Cluster Environment

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

Administration of Sun Enterprise Clusters Troubleshooting VPO in a Sun Cluster Environment

472

Appendix B

Administration of VERITAS Cluster Server

Appendix C

473

Administration of VERITAS Cluster Server In this Appendix

In this Appendix
This 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.

474

Appendix C

Administration of VERITAS Cluster Server VERITAS Cluster Server Architecture

VERITAS Cluster Server Architecture

With 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

Administration of VERITAS Cluster Server VERITAS Cluster Server Architecture

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

476

Appendix C

Administration of VERITAS Cluster Server VERITAS Cluster Server Architecture 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

Administration of VERITAS Cluster Server VERITAS Cluster Server Architecture 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 vpo-dg vpo-ip vpo-mount-etc vpo-mount-ora-core vpo-mount-ora-data vpo-mount-var vpo-oracle vpo-server vpo-sqlnet vpo-volume-etc vpo-volume-ora-core vpo-volume-ora-data Resource Type DiskGroup IP Mount Mount Mount Mount VPOOracle VPOServer VPOSqlnet Volume Volume Volume Action (Offline) Deport Disk Group. Unconfigure Virtual IP Address. Unmount File System. Unmount File System. Unmount File System. Unmount File System. Stop Oracle OpenView Database. Stop OpenView Platform. Stop SQL*Net/Net8 Listener. Stop Volume. Stop Volume. Stop Volume.

478

Appendix C

Administration of VERITAS Cluster Server VERITAS Cluster Server Architecture Table C-1 Service Resource Actions (Offline) Service Resource vpo-volume-var Resource Type Volume Action (Offline) Stop Volume.

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. Table C-2 Service Resource Actions (Online) Service Resource vpo-dg vpo-ip vpo-mount-etc vpo-mount-ora-core vpo-mount-ora-data vpo-mount-var Resource Type DiskGroup IP Mount Mount Mount Mount Action (Online) Import Disk Group. Configure Virtual IP Address. Mount File System. Mount File System. Mount File System. Mount File System.

Appendix C

479

Administration of VERITAS Cluster Server VERITAS Cluster Server Architecture Table C-2 Service Resource Actions (Online) Service Resource vpo-oracle vpo-server vpo-sqlnet vpo-volume-etc vpo-volume-ora-core vpo-volume-ora-data vpo-volume-var Resource Type VPOOracle VPOServer VPOSqlnet Volume Volume Volume Volume Action (Online) Start Oracle OpenView Database. Start OpenView Platform. Start SQL*Net/Net8 Listener. Start Volume. Start Volume. Start Volume. Start Volume.

5. Service Group is Online Service group vpo-sg is now online on system myrtle.

480

Appendix C

Administration of VERITAS Cluster Server Running VPO Agents in a VERITAS Cluster Server Environment

Running VPO Agents in a VERITAS Cluster Server Environment

The 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 Server Troubleshooting 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.

482

Appendix C

Administration of VERITAS Cluster Server Preconfigured 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

Administration of VERITAS Cluster Server Preconfigured Elements 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

484

Appendix C

Administration of VERITAS Cluster Server Preconfigured Elements

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

Administration of VERITAS Cluster Server Preconfigured Elements

486

Appendix C

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:160 SNMP 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:187 About Virtual Terminal, AR_II:160 access See also accessing file permissions, AR_I:416 remote, AR_I:420 restrictions, CG:62 terminal, CG:206 accessing See also access files, CG:206 GUI administrator, AR_I:417 Java, AR_I:418 Motif, AR_I:417 Jovw, AR_I:287AR_I:289 man pages command line, AR_I:497 HTML format, AR_I:497 managed node MIB, AR_I:386AR_I:387 NNM, AR_I:279AR_I:281 OpenView applications, CG:147 programs HP-UX, AR_I:418 MPE/iX, AR_I:418 quick filters, CG:195 terminal, CG:164 VPO, AR_I:415 account, primary, AR_I:421 acknowledgements See also acknowledging messages; messages annotating, CG:343 automatic, CG:157 description, CG:169 reviewing, CG:170 acknowledging messages See also acknowledgements; messages escalated messages, CG:429 message keys, CG:342 notification messages, CG:451 ACL Info application, AR_II:435 actagtp pipe file, AR_I:307 actagtq queue file, AR_I:307 action See also actions agents, AR_I:223 variables, AR_I:158AR_I:159 Action Report, AR_I:111 action-allowed managers configuring, CG:435 specifying, CG:445 ACTIONALLOWMANAGERS keyword,
AR_I:120

actions See also action applying to all nodes in hierarchy, automatic, CG:57CG:58 centralizing, CG:283 control-switched messages, CG:450 enabling on secondaring manager, CG:444 evaluating results, CG:155 integrating applications as, operator-initiated, CG:59CG:60 overview, CG:57CG:60 protecting, AR_I:424AR_I:427 responding to messages, CG:369 scheduled, AR_I:167 stderr, CG:155 stdout, CG:155 verifying automatic, CG:156CG:157 operator-initiated, CG:157CG:158
AR_I:223AR_I:224 CG:214CG:215

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

487

Master Index
Actions policy, CG:124 activating managed nodes AIX, AR_II:47AR_II:49 HP-UX, AR_II:86AR_II:89, tracing, AR_I:328AR_I:330 active message browser See also filtered message browser; history message browser; message browser; pending messages browser figure, CG:98 overview, CG:101CG: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:194 Add Configuration window, CG:292 Add MPE/iX Console Messages window, Add Node for External Events window, Add SNMP Trap window, CG:394 adding annotations, CG:166 message groups, CG:233, AR_I:73 nodes to VPO, CG:217CG:229 external nodes, CG:219 from IP submaps, CG:222 from VPO Add Node window, internal nodes, CG:217 methods, CG:210 node groups, AR_I:71 with templates, CG:292 SNMP trap templates, CG:394 tabs to browser pane, CG:195 VPO variables, CG:162 administrative rights See also VPO administrator administrator. See template administrators; VPO administrator adoptive node, AR_II:448 See also cluster nodes, MC/ServiceGuard; managed nodes, upgrading; original node advanced options
CG:224CG:227 CG:217 CG:399 AR_II:333AR_II:336

message conditions, CG:384 MPE/iX console messages, CG:400 advantages backups automatic, AR_I:441 offline, AR_I:439 flexible management, CG:423 operator message browser, CG:203 OVKey licenses, AR_I:462 template groups, CG:288 agdbserver monitor template, AR_II:225 agent accounts Windows NT/2000, AR_II:358AR_II:360 agents. See action agents; VPO agents aging, password, AR_I:419 AIX managed nodes DCE configuring, AR_II:44AR_II:45 requirements, AR_II:40 HACMP installing agents, AR_II:56AR_II:57 resetting IP, AR_II:54 NCS requirements, AR_II:40 OVPA, AR_II:211 VPO activating, AR_II:47AR_II:49 default operator, AR_II:67 de-installing agents, AR_II:58 directory structure, AR_II:66 file locations, AR_II:66 hardware requirements, AR_II:39 include file, AR_II:69 installation requirements, installation tips, AR_II:41AR_II:43 installing agents, AR_II:46AR_II:49 libraries, AR_II:68AR_II:70 logfile locations, AR_I:460 logfile templates, AR_II:59AR_II:60 makefile, AR_II:70 monitored objects, AR_II:62 organization, AR_II:66AR_II:67 overview, AR_II:37AR_II:70 preconfigured elements, removing agents, AR_II:58 scripts and programs, AR_II:64AR_II:65
AR_II:59AR_II:63 AR_II:39AR_II:40

488

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
SMIT User Interface, AR_II:63 SNMP event interceptor, AR_II:61 software requirements, AR_II:39AR_II:40 system resource files, AR_II:67 template groups, AR_II:59 troubleshooting IP aliases, AIX template group, AR_II:59 AIX with HACMP template group, AR_II:59 alarmgen monitor template, AR_II:225 All Active Details Report, AR_I:114 All Active Messages Report, AR_I:111, All History Messages Report, AR_I:111, All Pending Details Report, AR_I:114 All Pending Messages Report, AR_I:114 alternative accounts Windows NT/2000, AR_II:359AR_II:360 analyzing data with OVPA, AR_II:212 symptoms in VPO, AR_I:334 annotating acknowledgements, CG:343 messages escalated, CG:430 notification, CG:451 annotations overview, CG:166CG:168 reviewing, CG:155CG:156 APIs man pages VPO, AR_I:501 managed nodes, AR_I:483 message, CG:367CG:368 MSI, AR_I:228 Novell NetWare, AR_II:205AR_II:206 opcmsg (3), AR_II:106 Application Desktop window, CG:66 Application message attribute, AR_I:77 applications accessing OpenView, CG:147 assigning to operators, AR_I:213 Broadcast, CG:155 Citrix MetaFrame, AR_II:435AR_II:438 configuring templates, CG:306 customizing, CG:161 HP-UX
AR_I:114 AR_I:114 AR_II:53AR_II:54

ASCII SAM, AR_II:95 EMS Resources, AR_II:110AR_II:111 Motif SAM, AR_II:95 integrating into VPO actions, AR_I:223AR_I:224 Application Desktop, AR_I:214AR_I:215 broadcast command, AR_I:222 components, AR_I:213 Ethernet Traffic HP as an OV application, AR_I:218 HP applications, AR_I:213 monitoring applications, AR_I:225 NNM, AR_I:215, AR_I:216AR_I:221 OpenView plug-in, AR_I:214 overview, AR_I:211AR_I:230 VPO applications, AR_I:214 intercepting messages, AR_I:227 Java GUI comparisons, AR_I:268 OpenView, AR_I:281AR_I:283 monitoring logfiles, AR_I:226 Motif GUI, AR_I:268 MPE/iX, AR_II:158AR_II:160 Novell NetWare NetWare Tools, AR_II:194AR_II:197 NMA, AR_II:197AR_II:199 overview, AR_II:189AR_II:199 OVPA, AR_II:223 solving problems, CG:160CG:161 SSP Tools, AR_II:315 starting, CG:160 accounts, AR_I:419 I/O, AR_I:420 managed nodes, AR_I:229AR_I:230 remotely, AR_I:420 tailored set, CG:190 variables, AR_I:169AR_I:183 VPO description, CG:60 types, CG:216 Windows NT/2000, AR_II:392AR_II:423 Applications folder figure, CG:81 overview, CG:81 applying actions to all nodes in hierarchy,
CG:214CG:215

architecture

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

489

Master Index
scalable, CG:419CG:467 Sun Clusters, AR_II:465 archive log mode database description, AR_I:442 enabling, AR_I:443AR_I:444 description, AR_I:438 ARPA hostnames, mapping to NS node names, AR_II:164AR_II:167 ASCII character sets, AR_I:244 ASCII SAM, AR_II:95 assigning applications to operators, AR_I:213 IP addresses and hostnames to packages,
AR_II:455

IP addresses to LAN interface cards,

AR_II:455

passwords managed nodes, AR_I:422AR_I:423 MPE/iX, AR_I:422 Novell NetWare, AR_I:423 UNIX, AR_I:422 Windows NT, AR_I:423 templates distributing, CG:293 managed nodes, CG:291 overview, CG:291CG:293 attributes custom message overview, CG:138 viewing, CG:139 message examining, CG:135 modifying, CG:136 message forwarding, CG:425 message forwarding templates, AR_I:137 messages, AR_I:75AR_I:77 MPE/iX console message templates defaults, CG:400 Audit Log (AIX) template, AR_II:60 Audit Report, AR_I:111 auditing, CG:206 levels, AR_I:428AR_I:431 modes, AR_I:428 security, AR_I:428AR_I:431 Auditlog application, AR_II:435 authentication, CG:206

configuring DCE nodes to use authenticated RPCs, AR_I:407 processes, AR_I:312AR_I:314 RPC, AR_I:410AR_I:411 Automatic (De-)Installation option, AR_I:51 automatic actions corrective actions, CG:369 process, CG:57CG:58 protecting, AR_I:424 rerunning, CG:156 reviewing, CG:156 automatic backups advantages, AR_I:441 disadvantages, AR_I:442 excluding files database, AR_I:442 temporary, AR_I:442 overview, AR_I:440AR_I:449 recovering configuration data,
AR_I:449AR_I:451

automatic de-installation See also de-installing AIX, AR_II:58 HP-UX, AR_II:89 Linux, AR_II:127 automatic installation See also installing AIX, AR_II:46 automating standard scenarios, CG:341 avoiding duplicate messages, CG:393 B backing up data on management server , Backup message group, AR_I:72 backups automatic, AR_I:440AR_I:449 recovering configuration data, offline, AR_I:439 server, CG:445 tools, AR_I:438 backup-server template, AR_I:117 Bad Logs (10.x/11.x HP-UX) logfile, Bad logs (AIX) template, AR_II:60 Bad Logs (IRIX) template, AR_II:253
AR_II:91 AR_I:449AR_I:451 AR_I:438AR_I:451

490

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
Bad Logs (SINIX) template, AR_II:272 Bad Logs (Solaris) template, AR_II:297 benefits, VPO, CG:39 binaries common, AR_I:188 customized, AR_I:189 filenames, 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:158 broadcast commands integrating applications, AR_I:222 starting on managed nodes, AR_I:229AR_I:230 remotely, AR_I:420 broadcasting commands overview, CG:163CG:164 browser pane adding tabs, CG:195 figures disabled, CG:187 main window, CG:95 message browser, CG:96 popup menu, CG:116 hiding, CG:187 overview, CG:95CG:97 popup menus, CG:116 Browser Settings dialog box figure, CG:194 browsing messages effectively,
CG:123CG:128

buffering messages description, CG:43 parameters, AR_I:131 service hours, CG:415 building managed nodes, CG:208 Bull DPX/20, AR_II:65 C <$C> variable, AR_I:164 C2 security guidelines, AR_I:402 overview, CG:206CG:207 restrictions, CG:207, AR_I:403 techniques, CG:206 Cancel Reboot application, AR_II:392

case-sensitivity in pattern-matching, CG:316 catalogue, message, CG:296 CCD, AR_II:464 CCDD, AR_II:464 central competence centers, CG:426CG:427 management server action-allowed manager, CG:435 configuring, CG:438 description, CG:435 secondary manager, CG:436 centralizing actions, CG:283 cfgchanges file, AR_I:301 Change Operator Password dialog box figure, CG:172 changing character set logfile encapsulator, AR_I:244 managed node, AR_I:243 communication types, AR_I:54AR_I:56 defaults property type of all messages forwarded to VPO, AR_I:208 WMI policy name, AR_I:208 hostnames, AR_I:466AR_I:480 IP addresses, AR_I:466AR_I:480 look and feel of Java GUI, CG:181 operator passwords overview, CG:172 passwords, AR_I:415 refresh interval, CG:178 user names, AR_I:415 VPO administrator responsibility matrix,
CG:204

character code conversion,

AR_I:250AR_I:256

character sets ASCII, AR_I:244 changing logfile encapsulator, AR_I:244 managed nodes, AR_I:243 converting, AR_I:250AR_I:256 English language configuring, AR_I:250AR_I:253 supported, AR_I:242 types, AR_I:245AR_I:246 Euro symbol, AR_I:241

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

491

Master Index
external on managed nodes,
AR_I:244AR_I:247 ISO 8859-15, AR_I:241

Japanese language configuring, AR_I:254AR_I:256 supported, AR_I:243 types, AR_I:247 logfile encapsulator, AR_I:248AR_I:249 Spanish language supported, AR_I:242 charts current state, CG:143 history, CG:145 Check alarmdef application, AR_II:223 Check parm application, AR_II:223 Config perflbd.rc application, AR_II:223 choosing web browser, CG:188 Citrix MetaFrame applications, AR_II:435AR_II:438 integration configuring agent, AR_II:431 configuring server, AR_II:432 ICA Browser service, AR_II:432 installing agent, AR_II:431 logfile templates, AR_II:434 monitored objects, AR_II:433 overview, AR_II:430AR_II:434 Program Neighbourhood service,
AR_II:433

colored_message_lines option ito_op, AR_I:271 itooprc, AR_I:273 colors figures message browser, CG:99 object pane, CG:130 shortcut bar, CG:130 message browser, CG:196 Message Groups folder, CG:79 messages changing, CG:99 locations, CG:129CG:131 Nodes folder, CG:78 columns, message browser customizing, CG:196 hiding, CG:197 showing, CG:197 command line accessing man pages, AR_I:497 activating VPO agents AIX, AR_II:47 Solaris, AR_II:292 interface, AR_I:135 license maintenance tool, NNM tools, AR_I:283 command tracing, AR_I:67 commands broadcasting, CG:163CG:164 integrating applications as broadcast,
AR_I:222 AR_I:464AR_I:465

software requirements, AR_II:430 versions supported, AR_II:430 classifying unmatched messages, CG:55 client-server concept, CG:40CG:41 closing EMS GUI, AR_II:109 messages, CG:165 Cluster Configuration Database. See CCD Cluster Configuration Database Daemon. See CCDD clusters, mixed, AR_I:192 CMIP events forwarding, CG:392CG:393 overview, CG:390CG:397 coda, CG:374 coda process, AR_I:304 Cold Boot the NetWare Server (NCF) application, AR_II:194 collecting messages, CG:297CG:298

opcctrlovw, AR_I:283 opclic parameters, AR_I:464AR_I:465 syntax, AR_I:464 opcmapnode, AR_I:283 opcwall, AR_I:444 ovbackup.ovp, AR_I:445AR_I:446 ovrestore.ovpl, AR_I:446AR_I:449 stderr, CG:155 stdout, CG:155 synchronizing with VPO agent character set, AR_I:240 communication competence centers, CG:427 links

492

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
central server configuration, CG:438 manufacturing environment, CG:433 software types changing, AR_I:54AR_I:56 description, AR_I:41 VPO, AR_I:295AR_I:296 community name opcinfo file, AR_I:386 SNMP daemon configuration file, AR_I:387 comparing messages with conditions match conditions, CG:312CG:314 preconfigured templates, CG:43 competence centers communication flow, CG:427 configuring, CG:427 distributing responsibility, CG:426CG:427 overview, CG:426CG:427 component embedded performance, CG:374 components, integrating into VPO, AR_I:213 compression setting types, CG:350 concepts client-server, CG:40CG:41 message forwarding, CG:448 user, CG:61CG:67 Condition No. window, CG:386 conditions advanced threshold monitoring, applying to events, CG:312 match, CG:312CG:314 message description, CG:311CG:314 overview, CG:307CG:331 setting up, CG:310CG:311 modifying, CG:315 multiple for threshold monitoring, organizing, CG:314CG:315 pattern-matching examples,
CG:316CG:317 CG:387CG:388 CG:385CG:386

defining, CG:394CG:395 example, CG:396 specifying for message templates, CG:366 status variables, AR_I:132 suppress deploying, CG:333 description, CG:311CG:314 threshold monitor examples, CG:389 types, 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:223 configuration See also configuring C2 security restrictions, CG:207 distributing VPO agent to managed nodes,
AR_I:187

downloading data, AR_I:435AR_I:437 file distributing, CG:446CG:447 downloading, CG:446 responsible manager, CG:439CG:440 uploading, CG:446 installing on managed nodes, loading default, CG:173CG:178 protecting distribution, AR_I:423 updating on managed nodes, Configure Management Server window,
AR_I:191 AR_I:185AR_I:192 AR_I:185AR_I:192

configuring See also configuration application-specific templates, CG:306 automatic acknowledgements, CG:157 basic Distributed Event Interception,
AR_II:93

regroup defining, CG:359 examples, CG:360 selecting, CG:315 sequence, CG:332 SNMP trap templates

central server, CG:435 Citrix MetaFrame agent, AR_II:431 server, AR_II:432 competence centers, CG:427 database on multiple disks,
AR_I:453AR_I:455

DCE AIX, AR_II:44AR_II:45

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

493

Master Index
managed nodes, AR_I:405 management server, AR_I:405 SINIX RM/Reliant, AR_II:269 Tru64 UNIX, AR_II:330AR_II:331 ECS event interception, AR_II:94 EMS templates, AR_II:112 escalation policies, CG:429 event correlation, CG:406 filenames on MPE/iX managed nodes,
AR_II:157

agents on OpenView Operations for Windows management server,

AR_I:207

VPO agents for OpenView Operations for Windows management server, elements, CG:199CG:280 messages forwarded from OpenView Operations for Windows, preconfigured elements, AR_I:69AR_I:183 Configuring_DCE, AR_II:44 Connections application, AR_II:194 console messages, MPE/ix, CG:398CG:401 console settings saving, CG:179CG:180 consolidating messages in browser, CG:284 continuous message generation, CG:381 control files, AR_I:454 follow-the-sun, CG:424CG:426 managed nodes, CG:209 message sharing, CG:449 switching, CG:449CG:450 controller tool, AR_I:284AR_I:285 converting character sets, AR_I:250AR_I:256 managed node files EUC, AR_I:255 ROMAN8, AR_I:252 managed nodes to EUC, AR_I:258 management server to EUC, AR_I:257 copying and pasting nodes, CG:223 See also dragging and dropping nodes corrective actions automatic, CG:369 managed node, CG:43 operator-initiated, CG:369 Corrective Actions workspace description, CG:90 evaluating action results, CG:155 correlating events description, CG:51, CG:403CG:404 NNM, CG:407
AR_I:205AR_I:207 AR_I:196AR_I:199

filtered message browsers, CG:192 flexible management templates,

AR_I:117AR_I:152

managed nodes description, CG:44 hierarchies, CG:435 regional management servers,

CG:437CG:438

management server central, CG:438 English language, AR_I:250AR_I:253 Japanese language, AR_I:254AR_I:256 regional, CG:437CG:438 responsible, CG:439CG:447 NNM access with command-line tools,
AR_I:283

node authenticated RPCs, AR_I:407 DCE cell, AR_I:407 OpenView Operations for Windows agents for VPO management server, servers to forward messages to VPO, RPC authentication in VPO, AR_I:411 scheduled outages, CG:418 service hours, CG:418 templates message forwarding, AR_I:137 message source, CG:286 multiple, CG:303 threshold monitors, CG:384 time-indifferent templates, CG:442 timeouts for report generation, AR_I:110 VantagePoint for Windows
AR_I:203AR_I:208 AR_I:200AR_I:202

494

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
overview, CG:403CG:410 messages, CG:336 different sources, CG:405 flexible management environments,
CG:410

managed nodes, CG:405, CG:408 management server, CG:405, CG:409 messages and events, CG:334 counter-based suppression, CG:352 CPU Info application, AR_II:195 cpu_util object SGI IRIX, AR_II:254 HP-UX, AR_II:94 Linux, AR_II:129 Sequent DYNIX, AR_II:238 SINIX RM/Reliant, AR_II:273 Solaris, AR_II:301 Tru64 UNIX, AR_II:339 creating configuration file responsible managers, CG:439 message source templates, CG:287 status, CG:297 mirror online redo logs, AR_I:455 primary account manually, AR_I:421 SD-UX depot on remote node,
AR_II:80AR_II:81

overview, CG:138 setting defaults, CG:301 viewing, CG:139 Customize Message Browser Columns dialog box figures Custom tab, CG:128 General tab, CG:127 customized job stream facility preparing VPO, AR_II:149 setting up on MPE/iX managed nodes,
AR_II:148

customizing applications, CG:161 binaries, AR_I:189 Java GUI, CG:171 message browser columns attributes, CG:126 layout, CG:196 message event notification, CG:191 operator environment, CG:171 OVPA, AR_II:213 popup menus, CG:189CG:190 reports administrator, AR_I:113 operator, AR_I:115 scripts, AR_I:189 shortcut bar, CG:188 D Daemon, MC/ServiceGuard, AR_II:448 daemons DCE MPE/iX, AR_II:143 NCS, AR_II:143 RPC MPE/iX, AR_II:143 troubleshooting, AR_I:381 SNMP, AR_I:387 SSP snmpd, AR_II:316 Data Service, AR_II:464 data, backing up on management server,
AR_I:438AR_I:451

template group hierarchies, CG:289 groups, 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:301 current state chart figures bar chart, CG:143 pie chart, CG:144 overview, CG:143 custom message attributes adding to your message, CG:325

database archive log mode description, AR_I:438, AR_I:442 enabling, AR_I:443AR_I:444

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

495

Master Index
configuring on multiple disks, excluding files from automatic backups,
AR_I:442 AR_I:453AR_I:455

debugging software (de-)installation, def_browser option, AR_I:271 def_help_url option, AR_I:273 def_look_and_feel option ito_op, AR_I:271 itooprc, AR_I:273 default VPO operator AIX, AR_II:67 HP-UX, AR_II:100 Linux, AR_II:134AR_II:135 MPE/iX, AR_II:163 Novell NetWare, AR_II:203 Sequent DYNIX, AR_II:242 SGI IRIX, AR_II:258 SINIX RM/Reliant, AR_II:277 Solaris, AR_II:305 Tru64 UNIX, AR_II:343 Windows NT/2000, AR_II:427 default_browser option, AR_I:273 defaults assigned by administrator, CG:177 VPO, CG:174 IP map, AR_I:287 loading configuration, CG:173CG:178 management server setup, CG:422 message groups, AR_I:71AR_I:73 mapping on MPE/iX, AR_II:151 templates on MPE/iX, CG:400 node groups, AR_I:71 threshold monitor, CG:385 trap and event interception, CG:390 WMI policy name, AR_I:208 working directory, AR_I:416 Define Configuration window, CG:291 defining conditions messages, CG:384 regroup, CG:359 SNMP trap templates, CG:394CG:395 message groups, CG:56 report printer, AR_I:110 scheduled outages, CG:417 service hours, CG:416 templates
AR_I:67AR_I:68

group, message target rule example, CG:441 improving performance, AR_I:319 maintaining, AR_I:452 moving control files to second disk, AR_I:454 recovering, AR_I:450AR_I:451 removing queue files, AR_I:451 reports, AR_I:110AR_I:116 restoring, AR_I:450 restricting access, AR_I:116 security, AR_I:419 tables and tablespaces non-VPO, AR_I:492 VPO, AR_I:487 troubleshooting, AR_I:340AR_I:342 Database message group, AR_I:72 Date message attribute, AR_I:77 DCE changing, AR_I:54AR_I:56 configuring AIX, AR_II:44AR_II:45 managed nodes, AR_I:405 management server, AR_I:405 SINIX RM/Reliant, AR_II:269 Tru64 UNIX, AR_II:330AR_II:331 description, AR_I:41 nodes configuring to run in DCE cell, AR_I:407 configuring to use authenticated RPCs,
AR_I:407

description, AR_I:406 installing, AR_I:406 login failure, AR_I:421 passwords, AR_I:420AR_I:421 removing AIX, AR_II:45 SINIX RM/Reliant, AR_II:270 Tru64 UNIX, AR_II:331 security, AR_I:404AR_I:409 servers description, AR_I:406 installing, AR_I:405 de-activating tracing, AR_I:330

496

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
logfiles, CG:364 messages, CG:365, CG:394 MPE/iX console messages, CG:399 de-installation debugging disabling, AR_I:68 enabling, AR_I:68 facilities, AR_I:67 de-installing See also automatic de-installation; installing; manual de-installation; removing; standard de-installation OVPA managed nodes HP-UX, AR_II:221 Solaris, AR_II:221 VPO agents from managed nodes AIX, AR_II:58 automatically, AR_I:62AR_I:63 HP-UX, AR_II:89 Linux, AR_II:127 manually, AR_I:63 MPE/iX, AR_II:149 Sequent DYNIX, AR_II:236 SGI IRIX, AR_II:252 SINIX RM/Reliant, AR_II:271 Solaris, AR_II:294 Tru64 UNIX, AR_II:336 Windows NT/2000, AR_II:379 De-installing Agents, AR_II:127 De-installing Agents Automatically, delegating manager responsibilities, CG:444 deleting message groups, AR_I:73 node groups, AR_I:71 deploying suppress unmatched conditions, depot nodes, AR_II:79 DESCRIPTION keyword, AR_I:119 Description message attribute, AR_I:77 detecting problems browsing messages effectively, early, CG:283 message event notification, CG:122 severity coloring, CG:129CG:131 monitoring VPO, CG:120
CG:123CG:128 CG:333 AR_II:127

overview, CG:119 searching object tree, CG:121 viewing messages in message browser,
CG:122

dflt_DirectoryEvLog (2000) template, dflt_DNSEvLog (2000) template, AR_II:381 dflt_FileReplicationEvLog (2000) template,
AR_II:381 AR_II:381

Diagnostic Dashboard workspace accessing OpenView applications, CG:147 overview, CG:89 Diagnostics application, AR_II:393 Digital UNIX. See Tru64 UNIX managed nodes directories See also files; target directories; temporary directories AIX, AR_II:65, AR_II:162 HP-UX, AR_II:97, AR_II:132 maintaining, AR_I:457 Novell NetWare, AR_II:201 runtime data on managed nodes, AR_I:459 Sequent DYNIX, AR_II:240 SGI IRIX, AR_II:256 SINIX RM/Reliant, AR_II:275 Solaris, AR_II:303 Tru64 UNIX, AR_II:341 Windows NT/2000, AR_II:425 working, AR_I:416 disabled nodes See also disabling description, CG:209 managing, CG:229 disabling See also disabled nodes; enabling (de-)installation debugging, AR_I:68 primary account manually, AR_I:421 disadvantages of backups automatic, AR_I:442 offline, AR_I:439 Disconnect application, AR_II:436 Disk Space application, AR_II:159 disk space requirements, OVPA HP-UX, AR_II:218 Solaris, AR_II:218 disk_util object AIX, AR_II:62

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

497

Master Index
HP-UX, AR_II:94 Linux, AR_II:129 Sequent DYNIX, AR_II:238 SGI IRIX, AR_II:254 SINIX RM/Reliant, AR_II:273 Solaris, AR_II:301 Tru64 UNIX, AR_II:339 Disks application, AR_II:195 disks, multiple, AR_I:453AR_I:455 Display a File application, AR_II:195 display modes, ownership, CG:154,
CG:272CG:273

display option ito_op, AR_I:271 itooprc, AR_I:273 displaying available VPO agent versions, AR_I:65 installed VPO agent versions, AR_I:65 message defaults, CG:303 groups, AR_I:72 dispp<#> pipe file, AR_I:301 dispq<#> queue file, AR_I:301 Distributed Computing Environment. See DCE Distributed Event Interception configuring, AR_II:93 description, AR_II:92 distributing See also distribution configuration file other servers, CG:446CG:447 responsible managers, CG:440 managed nodes scripts and programs, AR_I:188AR_I:192 VPO agent configuration, AR_I:187 responsibility in competence centers,
CG:426CG:427

templates assigned, CG:293 description, CG:283 message source, CG:293CG:294 distribution See also distributing lists controlling size, CG:453CG:455 overview, CG:453CG:456 manager, AR_I:189

scripts and programs AIX, AR_II:64AR_II:65 HP-UX, AR_II:96AR_II:98 Linux, AR_II:130AR_II:132 MPE/iX, AR_II:161AR_II:162 Novell NetWare, AR_II:200AR_II:201 requirements, AR_I:188 Sequent DYNIX, AR_II:239AR_II:240 SGI IRIX, AR_II:255AR_II:256 SINIX RM/Reliant, AR_II:274AR_II:275 Solaris, AR_II:302AR_II:303 tips, AR_I:188AR_I:191 Tru64 UNIX, AR_II:340AR_II:341 UNIX, AR_I:192 Windows NT/2000, AR_II:424AR_II:425 documentation, related OVPA, AR_II:227AR_II:230 documenting solutions, CG:46 acknowledging messages, CG:169CG:170 annotating messages, CG:166CG:168 overview, CG:165 printing, CG:168 domain, worldwide management, CG:424 Download Configuration Data window description, AR_I:435AR_I:437 figure, AR_I:436 opening, AR_I:437 downloading configuration data, AR_I:435AR_I:437 files, CG:446 EMS templates, AR_II:112 OVPA documentation, AR_II:227 dragging and dropping nodes, CG:224 See also copying and pasting nodes duplicate messages avoiding, CG:393 suppressing flexible management environments,
CG:355

management server, CG:353CG:355 overview, CG:347 DYNIX. See Sequent DYNIX managed nodes DYNIX/ptx template group, AR_II:237

498

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
E E message attribute, AR_I:77 <$E> variable, AR_I:164 <$e> variable, AR_I:164 ECS, configuring, AR_II:94 elements, preconfigured, AR_I:71AR_I:109 embedded performance component, CG:374 troubleshooting, AR_I:382AR_I:385 EMS See also EMS Resources application errors, AR_II:111 GUI closing, AR_II:109 overview, AR_II:109AR_II:110 starting, AR_II:109 viewing resource instances, AR_II:109 opcmsg (3) API, AR_II:106 overview, AR_II:106AR_II:112 resource hierarchy command line, AR_II:112 GUI, AR_II:109AR_II:110 VPO Application Bank window, sending notifications to VPO, AR_II:112 templates configuring, AR_II:112 downloading, AR_II:112 threshold monitoring, AR_II:106AR_II:108 VPO Application Bank window,
AR_II:110AR_II:111 AR_II:110AR_II:111

maintenance mode for MC/ServiceGuard packages, AR_II:459 operators to control VPO agents, AR_I:220AR_I:221 to manage IP networks in IP map,
AR_I:217

SD-UX, AR_II:82 encapsulator, logfile, CG:361 Enforced ownership mode, CG:153, CG:274 English language character sets, AR_I:245AR_I:246 HP-UX configuration and related character sets, AR_I:250 management server, AR_I:250AR_I:253 OVPA documentation, AR_II:228 processing managed node files, Enterprise Servers, AR_II:98 environmental variables, AR_I:154 environments customizing operator GUI, CG:171 English language character sets, AR_I:245AR_I:246 description, AR_I:242 managed nodes with Japanese management server, AR_I:244 flexible management, CG:410 Japanese language description, AR_I:243 external character sets, AR_I:247 flexible management, AR_I:257AR_I:258 running English-language GUI, AR_I:236 loading default configuration, securing, CG:205CG:207 Spanish language description, AR_I:242 VPO administrator, CG:201CG:204 errors EMS, AR_II:111 getting instructions with opcerr, AR_I:338 logfiles, AR_I:335 messages filtering internal, CG:402, AR_I:339 locations, AR_I:335 reporting GUI Error Dialog Box, AR_I:337AR_I:338
CG:173CG:178 AR_I:252AR_I:253

EMS Resources application See also EMS description, AR_II:110 sample output, AR_II:111 syntax, AR_II:111 enabling See also disabling (de-)installation debugging, AR_I:68 actions on secondary manager, CG:444 archive log mode in database,
AR_I:443AR_I:444

duplicate message suppression on management server, CG:354CG:355 internal VPO error message filtering,
AR_I:339

JVM JIT compiler, AR_I:290

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

499

Master Index
message browser, AR_I:336 overview, AR_I:335AR_I:339 stderr and stdout devices, AR_I:338 escalating messages, CG:164 See also messages acknowledgements, CG:429 annotations, CG:430 guidelines, CG:429 overview, CG:428CG:431 policy, CG:429 process, CG:430CG:431 escmgr template, AR_I:117 establishing remote host equivalence, Ethernet problems, AR_I:389 Ethernet Traffic HP, integrating as an OV application, AR_I:218 EUC managed node, AR_I:255 management server, AR_I:257 Euro symbol, AR_I:241 evaluating action results, CG:155 evaluating messages impact, CG:296 severity, CG:296 sources, CG:295CG:296 Event Monitoring Service. See EMS <$EVENT_ID> variable, AR_I:160 events applying conditions, CG:312 CMIP, CG:390CG:397 correlating configuration, CG:406 description, CG:403CG:404 event streams, CG:51 NNM, CG:407 overview, CG:403CG:410 synchronizing, CG:407 template example, CG:411CG:414 with messages, CG:334 description, CG:50CG:51 Distributed Event Interception, ECS event interception, AR_II:94 interceptor, CG:407 monitoring EMS, AR_II:106AR_II:112 HP-UX, AR_II:106AR_II:112
AR_II:92AR_II:93 AR_II:317

resetting HACMP 4.2.2, AR_II:55 HACMP 4.3.1, AR_II:55AR_II:56 SNMP, CG:390CG:397 tracing, AR_I:67 example.m2 template, AR_I:117 example.m3 template, AR_I:117 examples conditions MPE/iX console message, CG:400CG:401 regroup, CG:360 SNMP trap, CG:396 failover procedure, AR_II:466AR_II:467 message target rules database group, CG:441 printing group, CG:441 remote action flow, AR_I:425 RPC authentication in VPO, AR_I:411 templates event correlation, CG:411CG:414 flexible management, AR_I:124, follow-the-sun responsibility switch,
AR_I:146AR_I:148 AR_I:149AR_I:150 AR_I:144AR_I:152

message forwarding between management servers, responsibility switch, AR_I:144AR_I:145 scheduled outages, AR_I:152 service hours, AR_I:151 time, AR_I:139AR_I:141 tracing, AR_I:331AR_I:332 exceptions warnings, system, AR_I:291 excluding files from automatic backups, AR_I:442 networking commands from streamed jobs,
AR_II:147

exporting SSP logfiles directory, AR_II:317 external character sets, AR_I:244AR_I:247 monitors, CG:372 nodes adding, CG:219 characteristics, CG:220

500

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
F <$F> variable, AR_I:165 failover definition, AR_II:464 procedure example, AR_II:466AR_II:467 Failures policy, CG:124 features Java and Motif GUIs, AR_I:270 VPO, CG:23 filenames binary, AR_I:192 MPE/iX, AR_II:157 files See also directories; include file; logfiles; makefile access, CG:206, AR_I:416 configuration responsible managers, CG:439CG:440 control, AR_I:454 converting managed node EUC, AR_I:255 ROMAN8, AR_I:252 excluding from automatic backups database, AR_I:442 temporary, AR_I:442 HP_OV_consoleSettings, CG:180 include file AIX, AR_II:69 HP-UX, AR_II:105 Linux, AR_II:137 MPE/iX, AR_II:168 Novell NetWare, AR_II:207 Sequent DYNIX, AR_II:244 SGI IRIX, AR_II:260 Solaris, AR_II:308 Tru64 UNIX, AR_II:346 Windows NT/2000, AR_II:429 itooprc, AR_I:273AR_I:278 location AIX, AR_II:66 HP-UX, AR_II:100 Linux, AR_II:134 MPE/iX, AR_II:163 Novell NetWare, AR_II:202 Sequent DYNIX, AR_II:241 SGI IRIX, AR_II:257 SINIX RM/Reliant, AR_II:276 Solaris, AR_II:304 Tru64 UNIX, AR_II:342 Windows NT/2000, AR_II:427 maintaining, AR_I:457 makefile AIX, AR_II:70 HP-UX, AR_II:105 Linux, AR_II:137 MPE/iX, AR_II:169 Novell NetWare, AR_II:208 Sequent DYNIX, AR_II:245 SGI IRIX, AR_II:261 SINIX RM/Reliant, AR_II:280 Solaris, AR_II:309 Tru64 UNIX, AR_II:347 Windows NT/2000, AR_II:429 mapping, AR_II:166 .opc_brc_history, CG:164 opcinfo, AR_I:386 permissions, AR_I:416 pipe managed nodes, AR_I:307AR_I:308 management server, AR_I:301AR_I:303 process managed node, AR_I:306AR_I:309 management server, AR_I:301AR_I:303 processing managed node English, AR_I:252AR_I:253 Japanese, AR_I:255AR_I:256 processing management server ISO 8859-15, AR_I:251 Shift JIS, AR_I:254 queue managed nodes, AR_I:307AR_I:308 management server, AR_I:301AR_I:303 removing, AR_I:451 security, AR_I:427 SNMP daemon configuration, AR_I:387 system resource AIX, AR_II:67 HP-UX, AR_II:101 MPE/iX, AR_II:164 Novell NetWare, AR_II:203 Sequent DYNIX, AR_II:243 SGI IRIX, AR_II:259 SINIX RM/Reliant, AR_II:278

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

501

Master Index
Solaris, AR_II:305 Tru64 UNIX, AR_II:344 Windows NT/2000, AR_II:428 tracing location, AR_I:332 syntax, AR_I:333 VPO agent configuration location, AR_I:311 types, AR_I:310 Filter Messages dialog box figure, CG:149 Filter Settings folder figure, CG:82 overview, CG:82CG:83 filtered message browser See also active message browser; history message browser; message browser; pending messages browser active figure, CG:101 overview, CG:101CG:102 configuring, CG:192 history figure, CG:103 investigating problems, CG:148CG:149 overview, CG:103 pending investigating problems, CG:150 overview, CG:104 saving settings, CG:193CG:194 filtering messages conditions, CG:307CG:331 description, CG:55 internal error messages, CG:402, AR_I:339 managed node, CG:332 management server, CG:332 multiple templates, CG:305 sources, CG:307CG:308 Find dialog box figures advanced search, CG:121 basic search, CG:121 finding impacted VP Navigator services,
CG:147

correlating messages, CG:410 overview, CG:422CG:432 suppressing duplicate messages, CG:355 Japanese-language environments,
AR_I:257AR_I:258

templates configuring, AR_I:117AR_I:152 examples, AR_I:144AR_I:152 follow-the-sun responsibility switch, keywords, AR_I:119AR_I:124 location, AR_I:117 message forwarding between management servers, responsibility switch, AR_I:144AR_I:145 scheduled outages, AR_I:152 service hours, AR_I:151 syntax, AR_I:124AR_I:129 types, AR_I:117 flow charts communication in competence centers,
CG:427 AR_I:149AR_I:150 AR_I:146AR_I:148

flexible management environments advantages, CG:423

communication links central server configuration, CG:438 manufacturing environment, CG:433 configuring event correlation in VPO, CG:406 message source templates, CG:286 DCE RPC client-server authentication process, AR_I:411 directory structure AIX, AR_II:66 HP-UX, AR_II:99 Linux, AR_II:133 MPE/iX, AR_II:163 Novell NetWare, AR_II:202 Sequent DYNIX, AR_II:241 SGI IRIX, AR_II:257 SINIX RM/Reliant, AR_II:276 Solaris, AR_II:304 Tru64 UNIX, AR_II:342 Windows NT/2000, AR_II:426 downloading and uploading configuration files, CG:446 filtering messages

502

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
management server, CG:309 multiple templates, CG:305 VPO agent, CG:308 HP-UX configuration and related character sets English, AR_I:250 Japanese, AR_I:254 installing VPO agents Novell NetWare, AR_II:180 Windows NT/2000, AR_II:356 interceptors MPE/ix console messages, CG:398 SNMP events with NNM, CG:391 logfile encapsulator, CG:361 logical event correlation, CG:404 management responsibility switching, CG:443 templates for managed nodes, CG:440 management server in MC/Service Guard,
AR_II:457

SD-UX remote software depot installation method, AR_II:79 SNMP event system in VPO, CG:392 VPO functional overview, AR_I:295 message interface, CG:367 worldwide management domain, CG:424 Flush application, AR_II:436 follow-the-sun control, CG:424CG:426 followthesun template, AR_I:118 font X resources, AR_I:236AR_I:238 formatting messages, CG:56 forwarding CMIP events, CG:392CG:393 messages, CG:425 between management servers, notification system, CG:451, AR_I:132 OpenView Operations for Windows management server, AR_I:204 strategies, CG:456CG:459 templates, CG:452CG:453 trouble ticket system, AR_I:132 SNMP traps, CG:392CG:393 unmatched messages, AR_I:337 forwmgrp pipe file, AR_I:301 forwmgrq queue file, AR_I:301 FTP (re-)installation See also installing Windows NT/2000 installing agents, AR_II:361AR_II:366 re-installing agents, AR_II:372AR_II:375 functionality, VPO, CG:45CG:49 functions, offline backup, AR_I:439 G <$G> variable, AR_I:165 generating default message key relations, CG:343CG:344 keys, CG:343CG:344 Internet reports, AR_I:110 reports, CG:46 generating new NMEV marker, generic templates, CG:306 getting error instructions
AR_II:155AR_II:156 CG:448CG:459

MC/ServiceGuard LAN switchover after, AR_II:453 before, AR_II:452 MC/ServiceGuard redundant data and heartbeat subnets, AR_II:454 MC/ServiceGuard switchover after, AR_II:451 before, AR_II:450 message escalation process, CG:430 message flow managed nodes, CG:408 management server, CG:409 message forwarding large hierarchies, CG:454 process, CG:453 remote actions, AR_I:425 scalability scenarios multiple management servers, CG:465 multiple management servers with VPO agents and NNM collection stations,
CG:467

NNM collection stations with VPO agents,

CG:463

single management server, CG:460 VPO agents monitoring IP devices, CG:462

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

503

Master Index
opcerr, AR_I:338 GlancePlus included with OVPA, AR_II:213 graphical user interface. See GUI group symbols, CG:216 GUI See also Java GUI; Motif GUI documentation activating VPO agents AIX, AR_II:49 Solaris, AR_II:293 EMS, AR_II:109AR_II:110 Java accessing, AR_I:418 comparison with Motif, AR_I:268AR_I:270 overview, AR_I:265AR_I:291 language support font X resources, AR_I:236AR_I:238 running English GUI in Japanese environment, AR_I:236 setting language, AR_I:234AR_I:238 management server, troubleshooting,
AR_I:345AR_I:347

Motif accessing, AR_I:417 comparison with Java, AR_I:268AR_I:270 operator saving output, CG:202 starting VPO, CG:202 permissions, AR_I:417AR_I:418 SAM, AR_II:95 variables, AR_I:169AR_I:183 VPO administrator accessing, AR_I:417 description, CG:202 GUI Error Dialog Box, AR_I:337AR_I:338 guidelines escalating messages, CG:429 message key, CG:337CG:340 H HA message group, AR_I:72 HACMP installation requirements, AR_II:52 installing VPO agents, AR_II:50AR_II:57 IP address naming scheme, AR_II:51

aliases, AR_II:50AR_II:54 troubleshooting, AR_II:53 resetting events HACMP 4.2.2, AR_II:55 HACMP 4.3.1, AR_II:55AR_II:56 HACMP logfile (AIX) template, AR_II:60 hardware HP 3000/900, AR_II:162 HP 9000/700, AR_II:97 HP 9000/800, AR_II:97 IBM RS/6000, AR_II:65 Intel Linux, AR_II:132 NetWare, AR_II:201 Sequent DYNIX, AR_II:240 Windows 2000/NT, AR_II:425 Siemens Nixdorf, AR_II:275 Silicon Graphics, AR_II:256 Sun SPARCstation, AR_II:303 Hardware message group MPE/iX, AR_II:151 VPO, AR_I:72 hardware requirements OVPA HP-UX, AR_II:215 Solaris, AR_II:215 VPO AIX, AR_II:39 HP-UX, AR_II:73 Linux, AR_II:117 MPE/iX, AR_II:141 Novell NetWare, AR_II:173 Sequent DYNIX, AR_II:233 SGI IRIX, AR_II:249 SINIX RM/Reliant, AR_II:265 Solaris, AR_II:283 Tru64 UNIX, AR_II:325 Windows NT/2000, AR_II:351AR_II:352 headline, message browser figure, CG:98 heartbeat subnets on MC/ServiceGuard,
AR_II:453AR_II:454

hiding message browser columns, CG:197 panes and areas, CG:185CG:187 position controls, CG:182 hier.time.spec template, AR_I:118

504

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
hier.specmgr template, AR_I:118 hier.time.all template, AR_I:118 hierarchies domain, CG:434CG:435 managed nodes, CG:214CG:215 management server, CG:433CG:438 message forwarding, CG:454 hierarchy template, AR_I:118 hierarchy.agt template, AR_I:118 hierarchy.sv template, AR_I:118 history graph figures popup menu, CG:146 severity changes over time, CG:145 overview, CG:145 history message browser See also active message browser; filtered message browser; message browser; pending messages browser investigating problems, CG:148CG:149 overview, CG:103 hostnames assigning to packages, AR_II:455 changing, AR_I:466AR_I:480 managed node, AR_I:475AR_I:480 management server, AR_I:467AR_I:469 MC/Service Guard, AR_II:455 hostview application, AR_II:315 HP 3000/900, AR_II:162 HP 9000/700, AR_II:97 HP 9000/800, AR_II:97 HP applications, integrating into VPO, HP Enterprise Servers, AR_II:98 HP ITO Account Windows NT/2000, AR_II:358 HP OpenView. See OpenView HP OpenView Performance Agent. See OVPA HP OpenView VantagePoint Operations. See VPO HP Software Distributor. See SD-UX HP System Administrator. See SAM HP Technical Workstations, AR_II:98 HP VantagePoint Network Node Manager. See NNM HP_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
AR_I:213

HP-UX managed nodes See also HP-UX management server; SD-UX activating, AR_II:86AR_II:89,
AR_II:333AR_II:336

applications ASCII SAM, AR_II:95 EMS Resources, AR_II:110AR_II:111 Motif SAM, AR_II:95 EMS command line, AR_II:112 GUI, AR_II:109AR_II:110 overview, AR_II:106AR_II:112 sending notifications to VPO, AR_II:112 threshold monitoring, VPO Application Bank window,
AR_II:110AR_II:111 AR_II:106AR_II:108

OVPA de-installing, AR_II:221 disk space requirements, AR_II:218 hardware requirements, AR_II:215 installation requirements, installing, AR_II:219AR_II:220 overview, AR_II:209AR_II:230 preconfigured elements, software requirements, AR_II:216 template groups, AR_II:224AR_II:226 VPO accessing programs, AR_I:418 default operator, AR_II:100 de-installing agents, AR_II:89 directory structure, AR_II:99 file locations, AR_II:100 hardware requirements, AR_II:73 include file, AR_II:105 installation requirements, installation tips, AR_II:77 installing agents, AR_II:77AR_II:85 libraries, AR_II:102AR_II:105 logfile locations, AR_I:460AR_I:461 logfile templates, AR_II:91 makefiles, AR_II:105
AR_II:73AR_II:76 AR_II:223AR_II:226 AR_II:214AR_II:218

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

505

Master Index
manual installation, AR_II:83AR_II:85 message templates, AR_II:90 monitored objects, AR_II:94 organization, AR_II:99AR_II:101 overview, AR_II:71AR_II:113 preconfigured elements, scripts and programs, AR_II:96AR_II:98 SD-UX installation, AR_II:79AR_II:85 SNMP event interceptor, software requirements, AR_II:73AR_II:76 standard installation, AR_II:78 system resource files, AR_II:101 template groups, AR_II:90 HP-UX management server See also HP-UX managed nodes configuration and related character sets English, AR_I:250 Japanese, AR_I:254 language variable for keyboards, AR_I:236 HTML format, accessing man pages,
AR_I:497 AR_II:92AR_II:94 AR_II:90AR_II:95

implementing message policies,

CG:281CG:418

importing OpenView Operations for Windows policies into VPO, AR_I:210 VPO templates into OpenView Operations for Windows, AR_I:209 improving performance database, AR_I:319 Java GUI, AR_I:290AR_I:291 Motif GUI startup, AR_I:322 SNMP management platform, UNIX with JIT, AR_I:290 VPO, AR_I:320AR_I:321 productivity, CG:283 include file See also files AIX, AR_II:69 HP-UX, AR_II:105 Linux, AR_II:137 MPE/iX, AR_II:168 Novell NetWare, AR_II:207 Sequent DYNIX, AR_II:244 SGI IRIX, AR_II:260 Solaris, AR_II:308 Tru64 UNIX, AR_II:346 Windows NT/2000, AR_II:429 incoming messages, comparing with match conditions, CG:312CG:314 Inetd object AIX, AR_II:62 HP-UX, AR_II:94 Linux, AR_II:129 Sequent DYNIX, AR_II:238 SGI IRIX, AR_II:254 SINIX RM/Reliant, AR_II:273 Solaris, AR_II:301 Tru64 UNIX, AR_II:339 Informational ownership mode, CG:154, initial_node option, AR_I:271, AR_I:275 INSERVICE parameter, AR_I:131 inspecting correlated events in NNM database, CG:407 Install Log application, AR_II:422
CG:274 AR_I:318AR_I:319

I I message attribute, AR_I:76 I/O applications, starting remotely, AR_I:420 IBM AIX. See AIX managed nodes IBM RS/6000, AR_II:65 ICA 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:275 identifying users logged into Java GUI, impact, message, CG:296
AR_I:291

506

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
Install/Update VPO Software and Configuration window, AR_I:51, AR_I:187 install_dir option, AR_I:275 installation debugging disabling, AR_I:68 enabling, AR_I:68 facilities, AR_I:67 installation requirements OVPA HP-UX, AR_II:214AR_II:218 Solaris, AR_II:214AR_II:218 VPO AIX, AR_II:39AR_II:40 HACMP, AR_II:52 HP-UX, AR_II:73AR_II:76 Linux, AR_II:117AR_II:120 MPE/iX, AR_II:141AR_II:142 Novell NetWare, AR_II:173AR_II:175 overview, AR_I:39AR_I:41 Sequent DYNIX, AR_II:233AR_II:234 SGI IRIX, AR_II:249AR_II:250 SINIX RM/Reliant, AR_II:265AR_II:266 Solaris, AR_II:283AR_II:286 Tru64 UNIX, AR_II:325AR_II:327 Windows NT/2000, AR_II:351AR_II:354 installation script, AR_I:49 installation tips managed nodes AIX, AR_II:41AR_II:43 HP-UX, AR_II:77 Linux, AR_II:122AR_II:123 MPE/iX, AR_II:143AR_II:146 Novell NetWare, AR_II:176AR_II:179 overview, AR_I:42AR_I:45 Sequent DYNIX, AR_II:235 SGI IRIX, AR_II:251 SINIX RM/Reliant, AR_II:267AR_II:268 Solaris, AR_II:287AR_II:288 Tru64 UNIX, AR_II:328AR_II:329 UNIX, AR_I:47AR_I:48 management server, AR_I:46 installation troubleshooting managed nodes MPE/iX, AR_I:350AR_I:354 UNIX, AR_I:348 multi-homed hosts, AR_I:388AR_I:396 Installed Software (NW) application, Installed Software application, AR_II:397 installing See also automatic installation; de-installing; FTP (re-)installation; manual installation; removing; standard installation Citrix MetaFrame agent, AR_II:431 DCE nodes, AR_I:406 servers, AR_I:405 OVPA managed nodes HP-UX, AR_II:219AR_II:220 VPO agents on managed nodes AIX, AR_II:45AR_II:57 automatically, AR_I:49AR_I:56 HACMP, AR_II:50AR_II:57 HP-UX, AR_II:77AR_II:85 Linux, AR_II:123AR_II:126 MPE/iX, AR_II:149 Novell NetWare, AR_II:181AR_II:186 overview, AR_I:37AR_I:68 SD-UX, AR_II:79AR_II:82 Sequent DYNIX, AR_II:236 SGI IRIX, AR_II:252 SINIX RM/Reliant, AR_II:270 Solaris, AR_II:290AR_II:291 SSH installation method, AR_I:57AR_I:61 Sun Enterprise E10000, Tru64 UNIX, AR_II:332 Windows NT/2000, AR_II:355AR_II:378 VPO configuration on managed nodes, Instant On licenses, AR_I:462 instruction text interface variables, AR_I:168 Instructions adding to your message, CG:327 reading, CG:158CG:159 integrated web browser. See web browser integrating applications into VPO actions, AR_I:223AR_I:224 Application Desktop, AR_I:214AR_I:215 broadcast commands, AR_I:222
AR_I:185AR_I:192 AR_II:318AR_II:320 AR_II:195

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

507

Master Index
components, AR_I:213 HP applications, AR_I:213 HP OpenView plug-in, AR_I:214 monitoring applications, AR_I:225 NNM, AR_I:215, AR_I:216AR_I:221 overview, AR_I:211AR_I:230 VPO applications, AR_I:214 Citrix MetaFrame, AR_II:430AR_II:434 data with OVPA, AR_II:212 Ethernet Traffic HP as OV application,
AR_I:218

VPO and OpenView Operations for Windows, AR_I:195AR_I:210 interval, refresh, CG:178 intervals, setting time, CG:442 investigating problems accessing OpenView applications, CG:147 examining message attributes, CG:135 finding impacted VP Navigator services,
CG:147

IP Activity Monitoring - Tables as OV service, AR_I:219 monitoring programs, CG:370 SMS into VPO, AR_II:439AR_II:444 Sun Management Center, AR_II:321 threshold monitors, CG:382CG:385 Intel Linux, AR_II:132 NetWare, AR_II:201 Sequent DYNIX, AR_II:240 Windows 2000/NT, AR_II:425 intercepting events Distributed Event Interception, ECS, AR_II:94 messages applications, AR_I:227 description, CG:43 managed nodes, CG:43 MPE/iX console, CG:398CG:399 MPE/iX managed nodes, sources, CG:51CG:52, CG:297CG:298 SNMP events, CG:390CG:391 traps, CG:390 interceptor, event, CG:407 interface, message, CG:367CG:368 internal nodes adding, CG:217 characteristics, CG:218 Internet reports, generating, AR_I:110 interoperability overview, AR_I:193AR_I:210
AR_II:151AR_II:156 AR_II:92AR_II:93

message browser, CG:134 histories, CG:148CG:149 modifying message attributes, CG:136 overview, CG:132CG:133 pending messages browser, CG:150 reviewing original message text, CG:137 viewing custom message attributes, message severity, CG:142CG:146 workspace pane, CG:141 IP addresses assigning to LAN interface cards,
AR_II:455 CG:138CG:139

assigning to packages, AR_II:455 changing, AR_I:466AR_I:480 managed node, AR_I:475AR_I:480 management server, AR_I:467AR_I:469 MC/Service Guard, AR_II:455 devices, CG:462 HACMP address naming scheme, AR_II:51 aliases, AR_II:50AR_II:54 troubleshooting, AR_II:53 map accessing with Jovw, AR_I:287AR_I:289 network management, AR_I:217 submaps, 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:253 IRIX. See SGI IRIX managed nodes ISO 8859-15 on managed nodes, AR_I:241

508

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
on management server, AR_I:251 ITO_FM_INIT 360 attribute, AR_II:470 ITO_FM_START 360 attribute, AR_II:470 ITO_FM_STOP 360 attribute, AR_II:470 ITO_MAINTENANCE FALSE attribute, ito_op startup script, AR_I:271AR_I:272 ITO_PMON_EXCLUDE opcsvcm attribute, ITO_PMON_RETRIES 5 attribute, AR_II:469 ITO_PMON_SLEEP 60 attribute, AR_II:469 ITO_PMON_START 5 attribute, AR_II:469 ITO_PMON_TAG ito_pmon attribute, ITO_PMON_TPERIOD -1 attribute, ito_restore.sh script, AR_I:449 ITO_START 360 attribute, AR_II:470 ITO_START_NET 720 attribute, AR_II:470 ITO_STOP 360 attribute, AR_II:470 ITO_STOP_NET 360 attribute, AR_II:470 itop, CG:66 See also opc_op; netop J Japanese language character sets, AR_I:247 flexible management, AR_I:257AR_I:258 HP-UX configuration and related character sets, AR_I:254 management server, AR_I:254AR_I:256 OVPA documentation, AR_II:230 processing managed node files,
AR_I:255AR_I:256 AR_II:469 AR_II:469 AR_II:470 AR_II:470

choosing web browser, CG:188 comparison with Motif GUI, configuring filtered message browsers,
CG:192 AR_I:268AR_I:270

customizing message browser columns, CG:196 message event notification, CG:191 overview, CG:171 popup menus, CG:189CG:190 shortcut bar, CG:188 figure, CG:71 hiding message browser columns, CG:197 panes and areas, CG:185CG:187 position controls, CG:182 identifying logged-in users, AR_I:291 ito_op startup script, AR_I:271AR_I:272 itooprc file, AR_I:273AR_I:278 loading default configuration, menu bar, CG:108 moving panes and areas, CG:183 object pane, CG:75CG:76 OpenView applications, AR_I:281AR_I:283 overview, AR_I:265AR_I:291 performance tips, AR_I:290AR_I:291 popup menus, CG:111 position controls, CG:110 saving console settings, CG:179CG:180 message browser filter, CG:193CG:194 message browser layout, CG:198 shortcut bar, CG:73CG:74 showing message browser columns, CG:197 panes and areas, CG:185CG:187 position controls, CG:182 startup options, AR_I:271AR_I:272 switching message colors to entire line,
CG:196 CG:173CG:178

Java GUI See also GUI; Motif GUI documentation accessing Jovw, AR_I:287AR_I:289 NNM, AR_I:279AR_I:281 VPO, AR_I:418 accessing quick filters, CG:195 adding tabs to browser pane, CG:195 applications, AR_I:172 browser pane, CG:95CG:97 changing look and feel, CG:181 operator passwords, CG:172 refresh interval, CG:178

toolbar, CG:109 tour, CG:71CG:72 variables, AR_I:169AR_I:183 web browsers, CG:105CG:107 workspace pane, CG:85CG:87

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

509

Master Index
Job message group MPE/iX, AR_II:151 VPO, AR_I:72 Job Status application, AR_II:398 Jovw accessing, AR_I:287AR_I:289 default IP map, AR_I:287AR_I:289 Just-in-Time compiler. See JVM JIT compiler JVM JIT compiler, enabling, AR_I:290 K Kernel Logs (10.x/11.x HP-UX) logfile, Kernel Logs (AIX) template, AR_II:60 kernel parameters, AR_I:40 keyboards, setting language variable on HP-UX, AR_I:236 keys, message, CG:342 keywords, template flexible management, AR_I:119AR_I:124 time, AR_I:142AR_I:143 L Lan Console application, AR_II:159 LAN interface cards, assigning IP addresses,
AR_II:455 AR_II:91

language support GUI font X resources, AR_I:236AR_I:238 running English GUI in Japanese environment, AR_I:236 setting language, AR_I:234AR_I:238 managed nodes managing English nodes with Japanese management server, AR_I:244 overview, AR_I:239AR_I:249 setting character set, AR_I:241 setting language, AR_I:240 management server overview, AR_I:233AR_I:238 setting character set, AR_I:234 setting language, AR_I:233 overview, AR_I:231AR_I:263 languages VPO other, AR_I:260AR_I:262 libraries

AIX, AR_II:68AR_II:70 HP-UX, AR_II:102AR_II:105 Linux, AR_II:136AR_II:137 managed nodes, AR_I:484 MPE/iX, AR_II:168AR_II:169 Novell NetWare, AR_II:207AR_II:208 Sequent DYNIX, AR_II:244AR_II:245 SGI IRIX, AR_II:260AR_II:261 SINIX RM/Reliant, AR_II:279AR_II:280 Solaris, AR_II:307AR_II:309 Tru64 UNIX, AR_II:345AR_II:347 Windows NT/2000, AR_II:429 License application, AR_II:436 licenses command-line tool, AR_I:464AR_I:465 Instant On, AR_I:462 maintaining, AR_I:462AR_I:465 types, AR_I:462AR_I:463 linking messages logically, CG:52 Linux (RedHat) template group, AR_II:128 Linux managed nodes default operator, AR_II:134AR_II:135 de-installing agents, AR_II:127 directory structure, AR_II:133 file locations, AR_II:134 hardware requirements, AR_II:117 include file, AR_II:137 installation requirements, AR_II:117AR_II:120 tips, AR_II:122AR_II:123 installing agents, AR_II:123AR_II:126 libraries, AR_II:136AR_II:137 logfile templates, AR_II:128 makefile, AR_II:137 monitored objects, AR_II:129 organization, AR_II:133AR_II:135 overview, AR_II:115AR_II:137 preconfigured elements, removing agents, AR_II:127 scripts and programs, AR_II:130AR_II:132 SNMP event interceptor (not supported),
AR_II:129 AR_II:128AR_II:129

software requirements,

template groups, AR_II:128 List Processes application, AR_II:223

AR_II:118AR_II:120

510

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
List Versions application, AR_II:223 lists, message distribution, CG:453CG:456 LM Sessions application, AR_II:399 Load/Unload an arbitrary NLM application, AR_II:196 loading default configuration,
CG:173CG:178

Local Location Broker troubleshooting, AR_I:381 Local Users application, AR_II:400 LOCAL_ON_JAVA_CLIENT variable, LOCAL_ON_JAVA_CLIENT_WEB variable, locale option, AR_I:271, AR_I:275 localizing object names, AR_I:263 locating See also location messages, CG:295 location See also locating configuration data, AR_I:435 error messages, AR_I:335 files AIX, AR_II:66 HP-UX, AR_II:100 Linux, AR_II:134 managed node logfiles, AR_I:460AR_I:461 managed node processes, AR_I:309 MPE/iX, AR_II:163 Novell NetWare, AR_II:202 opcinfo on managed nodes, AR_I:325 Sequent DYNIX, AR_II:241 SGI IRIX, AR_II:257 SINIX RM/Reliant, AR_II:276 Solaris, AR_II:304 tracing, AR_I:332 Tru64 UNIX, AR_II:342 VPO agent configuration, AR_I:311 Windows NT/2000, AR_II:427 scripts and programs AIX, AR_II:64 HP-UX, AR_II:96 Linux, AR_II:131 MPE/iX, AR_II:161 Novell NetWare, AR_II:200 Sequent DYNIX, AR_II:239 SGI IRIX, AR_II:255
AR_I:168 AR_I:168

SINIX RM/Reliant, AR_II:274 Solaris, AR_II:302 Tru64 UNIX, AR_II:340 Windows NT/2000, AR_II:424 templates flexible management, AR_I:117 message forwarding, AR_I:136 scheduled outage, AR_I:130 scheduled outages, AR_I:130 service hours, AR_I:130 <$LOGFILE> variable, AR_I:160 logfile See also files application, monitoring, AR_I:226 encapsulator changing character set, AR_I:244 character sets supported, description, CG:361 flow chart, CG:361 error messages, AR_I:335 locations on managed nodes, MC/ServiceGuard, AR_II:459 messages, CG:361CG:366 SSP directory, exporting, AR_II:317 templates AIX, AR_II:59AR_II:60 Citrix MetaFrame, AR_II:434 defining, CG:364 description, CG:362 HP-UX (VPO), AR_II:91 Linux, AR_II:128 MPE/iX, AR_II:150 Novell NetWare, AR_II:187 Sequent DYNIX, AR_II:237 SGI IRIX, AR_II:253 SINIX RM/Reliant, AR_II:272 Solaris (VPO), AR_II:297 Sun Enterprise E10000, AR_II:313 Tru64 UNIX, AR_II:337AR_II:338 variables, AR_I:160 Windows NT/2000, AR_II:381AR_II:382 logging data with OVPA, AR_II:212 logging messages, CG:43, CG:356CG:357 logical host, Sun Cluster, AR_II:464 login
AR_I:460AR_I:461 AR_I:248AR_I:249

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

511

Master Index
DCE, AR_I:421 RPC, 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:297 Logon Report, AR_I:111 LOGONLY parameter, AR_I:131 <$LOGPATH> variable, AR_I:160 Logs (DYNIX/ptx) template, AR_II:237 Logs (Tru64 UNIX) template, AR_II:337 logs, 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:62 HP-UX, AR_II:94 Linux, AR_II:129 Sequent DYNIX, AR_II:238 SGI IRIX, AR_II:254 Solaris, AR_II:301 Tru64 UNIX, AR_II:339 maintaining database, AR_I:452 directories, AR_I:457 files, AR_I:457 licenses, AR_I:462AR_I:465 managed nodes, AR_I:458AR_I:461 OpenView, AR_I:456 VPO, CG:199CG:280, AR_I:433AR_I:480 Major message severity level, AR_I:74 makefile See also files AIX, AR_II:70 HP-UX, AR_II:105 Linux, AR_II:137 MPE/iX, AR_II:169 Novell NetWare, AR_II:208 Sequent DYNIX, AR_II:245

SGI IRIX, AR_II:261 SINIX RM/Reliant, AR_II:280 Solaris, AR_II:309 Tru64 UNIX, AR_II:347 Windows NT/2000, AR_II:429 man pages accessing command line, AR_I:497 HTML format, AR_I:497 APIs VPO, AR_I:501 printing, AR_I:497 VantagePoint Navigator, AR_I:502 VPO, AR_I:495AR_I:502 managed nodes See also Managed Nodes window; management server accessing MIB, AR_I:386AR_I:387 adding to VPO description, CG:210 from IP submaps, CG:222 from VPO Add Node window, in Node Bank window, AR_I:50 overview, CG:217CG:229 with templates, CG:292 APIs, AR_I:483 building, CG:208 character sets changing, AR_I:243 EUC, AR_I:255 external, AR_I:244AR_I:247 ROMAN8, AR_I:252 Shift JIS, AR_I:258 communication types, AR_I:54AR_I:56 configuring authenticated RPCs, AR_I:407 DCE cell, AR_I:407 description, CG:44 hierarchies, CG:435 regional management servers, copying and pasting, CG:223 correlating messages, CG:405, CG:408 debugging software (de-)installation,
AR_I:67AR_I:68 CG:437CG:438 CG:224CG:227

512

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
defaults, CG:228 de-installing VPO agents automatically, AR_I:62AR_I:63 manually, AR_I:63 description, CG:43CG:44 directories with runtime data, AR_I:459 disabled, CG:229 distributing scripts and programs, AR_I:188AR_I:192 VPO agent configuration, AR_I:187 dragging and dropping, CG:224 external adding, CG:219 characteristics, CG:220 files pipe, AR_I:307AR_I:308 process, AR_I:307AR_I:308 queue, AR_I:307AR_I:308 filtering messages, CG:332 group symbols, CG:216 hostnames and IP addresses,
AR_I:475AR_I:480

installing VPO agents, AR_I:37AR_I:68 VPO configuration, AR_I:185AR_I:192 internal adding, CG:217 characteristics, CG:218 kernel parameters, AR_I:40 language support, AR_I:239AR_I:249 libraries, AR_I:484 logfile locations AIX, AR_I:460 HP-UX, AR_I:461 HP-UX 10.x/11.x, AR_I:460 MPE/iX, AR_I:460 Solaris, AR_I:461 VPO, AR_I:460AR_I:461 Windows NT, AR_I:460 maintaining, AR_I:458AR_I:461 managing VPO agents, AR_I:64AR_I:66 message-allowed, CG:209 multiple parent groups, CG:216 opcinfo file, AR_I:325 operating systems AIX, AR_II:37AR_II:70

HP-UX, AR_II:71AR_II:113 Linux, AR_II:115AR_II:137 MPE/iX, AR_II:139AR_II:169 Novell NetWare, AR_II:171AR_II:208 Sequent DYNIX, AR_II:231AR_II:245 SGI IRIX, AR_II:247AR_II:261 SINIX RM/Reliant, AR_II:263AR_II:280 Solaris, AR_II:281AR_II:322 Tru64 UNIX, AR_II:323AR_II:347 Windows NT/2000, AR_II:349AR_II:444 organizing, CG:208CG:231 passwords assigning, AR_I:422AR_I:423 DCE, AR_I:420AR_I:421 MPE/iX, AR_I:422 Novell NetWare, AR_I:423 UNIX, AR_I:422 Windows NT, AR_I:423 process files, AR_I:306AR_I:309 processes, AR_I:304AR_I:311 processing files English, AR_I:252AR_I:253 Japanese, AR_I:255AR_I:256 redistributing scripts, AR_I:438 returning names with pattern matching,
AR_I:285

security, CG:229 starting applications, AR_I:229AR_I:230 broadcast commands, AR_I:229AR_I:230 templates for responsible managers, CG:440 troubleshooting all managed nodes, AR_I:355AR_I:369 embedded performance component, mixed-case node names, AR_I:349 MPE/iX, AR_I:350AR_I:354, UNIX, AR_I:348, AR_I:370AR_I:373 types, CG:209 updating VPO agents, AR_I:49AR_I:56 VPO configuration, AR_I:185AR_I:192 VPO agents on Sun Clusters, AR_II:468 windows, CG:209 Managed Nodes window
AR_I:374AR_I:380 AR_I:382AR_I:385

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

513

Master Index
description, CG:66 management hierarchies See also management server overview, CG:433CG:438 profiles, CG:433 responsibilities, CG:434CG:435 setup ratio, CG:434 management profiles, CG:433 See also management server management responsibility See also management server domain hierarchies, CG:434CG:435 message forwarding between management servers, AR_I:149AR_I:150 switch, AR_I:144AR_I:145 follow-the-sun, AR_I:146AR_I:148 template syntax, AR_I:126 management server See also managed nodes; management hierarchies; management profiles; management responsibility; managers action-allowed configuring, CG:435 specifying, CG:445 backing up data, AR_I:438AR_I:451 central configuring, CG:438 description, CG:435 changing hostnames or IP addresses, competence centers, CG:426CG:427 configuring English language, AR_I:250AR_I:253 Japanese language, AR_I:254AR_I:256 OpenView Operations for Windows agents for VPO, AR_I:200AR_I:202 OpenView Operations for Windows to forward messages to VPO,
AR_I:203AR_I:208 AR_I:467AR_I:469

duplicate messages enabling suppression, CG:354CG:355 suppressing, CG:353 escalating messages, CG:428CG:431 files pipe, AR_I:301AR_I:303 process, AR_I:301AR_I:303 queue, AR_I:301AR_I:303 filtering messages, CG:332 flexible architecture, CG:423 follow-the-sun control, CG:424CG:426 forwarding messages between management servers, OpenView Operations for Windows,
AR_I:204 CG:448CG:459

VPO agents for OpenView Operations for Windows, AR_I:196AR_I:199 connecting to trouble ticket systems, CG:456 converting to EUC, AR_I:257 correlating messages, CG:405, CG:409 default setup, CG:422 description, CG:42 distributing configuration, CG:446CG:447

hierarchies, CG:433CG:438 installation tips, AR_I:46 language support overview, AR_I:233AR_I:238 setting character set, AR_I:234 setting language, AR_I:233 MC/Service Guard, AR_II:447 multiple, CG:419CG:467 primary, CG:422 processes, AR_I:297AR_I:303 processing files ISO 8859-15, AR_I:251 Shift JIS, AR_I:254 processing messages, CG:309 reconfiguring after changing hostname or IP address, AR_I:470AR_I:474 regional configuring, CG:437CG:438 description, CG:434 responsibility configuring, CG:439CG:447 switching, CG:443CG:445 running on MC/ServiceGuard, AR_II:457 secondary, CG:436 sending messages OpenView Operations for Windows,
AR_I:196

VPO, AR_I:200 single, CG:460 troubleshooting

514

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
GUI, AR_I:345AR_I:347 server, AR_I:343AR_I:344 management, flexible, CG:422CG:432 manager, distribution, AR_I:189 managers See also management server action-allowed adding, CG:445 central server, CG:435 backup, CG:445 primary changing, CG:443CG:445 initial, CG:422 responsibility, CG:439CG:447 secondary, CG:436 managing disabled nodes, CG:229 message source templates, CG:285CG:294 messages, CG:55 Sun Enterprise E10000, VPO agents, AR_I:64AR_I:66 manual de-installation See also de-installing OVPA HP-UX, AR_II:222 Solaris, AR_II:222 VPO AIX, AR_II:58 HP-UX, AR_II:89 Linux, AR_II:127 SINIX RM/Reliant, AR_II:271 Solaris, AR_II:294 Tru64 UNIX, AR_II:336 Windows NT/2000, AR_II:379 manual installation See also installing OVPA HP-UX, AR_II:220 Solaris, AR_II:220 VPO AIX, AR_II:46AR_II:49 HP-UX, AR_II:83AR_II:85 Linux, AR_II:124AR_II:126 SINIX RM/Reliant, AR_II:270 Solaris, AR_II:290 Windows NT/2000, AR_II:376AR_II:378
AR_II:310AR_II:311

manufacturing environment communication links, CG:433 management profiles, CG:433 mapping ARPA hostnames to NS node names overview, AR_II:164AR_II:167 problems, AR_II:166 resolving names, AR_II:167 vt3k operation, AR_II:165 MPE/iX messages to VPO security levels,
AR_II:152

NMEV markers, AR_II:152AR_II:155 marking messages, CG:272 match conditions, comparing with incoming messages, CG:312CG:314 mathematical operators in pattern-matching, CG:315CG:316 max_limited_messages option, AR_I:272, maximum threshold, CG:377 MC/Service Guard description, AR_II:447AR_II:449 enabling maintenance mode, AR_II:459 examples, AR_II:450AR_II:454 redundant data and heartbeat subnets, switching local networks, switching packages, AR_II:450AR_II:451 glossary, AR_II:448 IP addresses and hostnames, AR_II:455 logfiles, AR_II:459 overview, AR_II:445AR_II:459 running management server, AR_II:457 NNM, AR_II:456 VPO, AR_II:456AR_II:458 transferring applications to other management servers, AR_II:447 troubleshooting, AR_II:459 MC/ServiceGuard adoptive node, AR_II:448 original node, AR_II:448 package custody, AR_II:448 description, AR_II:448 IP/hostname, AR_II:448
AR_II:452AR_II:453 AR_II:453AR_II:454 AR_I:275

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

515

Master Index
service, AR_II:449 support, AR_II:113 MC/ServiceGuard Daemon, AR_II:448 Memory Load application, AR_II:401 Memory Use application, AR_II:196 menu bar figure, CG:108 overview, CG:108 message defaults message correlation options, CG:302 output options for a message stream interface, CG:302 pattern-matching options, CG:302 message-allowed managed nodes, CG:209 Message and Suppress Conditions window,
CG:314

message attributes setting defaults, CG:301 message browser See also active message browser; filtered message browser; history message browser; pending messages browser accessing quick filters, CG:195 browsing effectively, CG:123CG:128 configuring filters active, CG:101CG:102 history, CG:103 overview, CG:192 pending, CG:104 consolidating messages, CG:284 customizing columns message attributes, CG:126 physical layout, CG:196 figures browser pane, CG:96 custom message attributes, CG:139 workspace pane, CG:97 hiding columns, CG:197 investigating problems, CG:134 Java and Motif GUIs, AR_I:268 operator, CG:203 overview, CG:98 reporting errors, AR_I:336 reusing filters, CG:193CG:194 saving customized layout, CG:198

filter to object pane, CG:195 showing columns, CG:197 switching colors to entire line, CG:196 viewing custom message attributes, CG:139 messages, CG:122 VPO administrator, CG:203CG:204 Message Browser window description, CG:67 message attributes and values, AR_I:73 overview, AR_I:73AR_I:77 Message Condition Advanced Options window, CG:394 message conditions See also messages defining advanced options, CG:384 setting up, CG:310CG:311 message correlation options setting defaults, CG:302 Message Correlation window, CG:337 Message Dashboard workspace current state chart, CG:143 history chart, CG:145 overview, CG:88 viewing message severity, CG:142CG:146 message event notification customizing, CG:191 overview, CG:122 message event warning, CG:122 Message Group Bank window, AR_I:72 message groups See also Message Groups window; messages adding, AR_I:73 adding new, CG:233 default, AR_I:71AR_I:77 defining, CG:56 deleting, AR_I:73 displaying, AR_I:72 modifying, AR_I:73 organizing, CG:232CG:233 reviewing, CG:233 Message Groups folder colors, CG:79 figure, CG:79 organizing, CG:80 overview, CG:79CG:80 Message Groups window, CG:66

516

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
See also message groups message keys, CG:336 See also messages default, CG:343CG:344 guidelines, CG:337CG:340 relations, CG:343CG:344 message operations template syntax,
AR_I:127

Message Properties dialog box figures Annotations tab, CG:167 Custom Attributes tab, CG:140 General tab, CG:100 Instructions tab, CG:158 Original Message tab, CG:137 message settings assigning, CG:324 message source templates See also Message Source Templates window; message sources; messages configuring, CG:286 creating, CG:287 distributing, CG:293CG:294 elements, CG:285 managing, CG:285CG:294 variables, AR_I:154AR_I:167 Message Source Templates window See also message source templates description, CG:287 figure, CG:294 Templates Groups list box, CG:288 message sources See also message source templates; messages evaluating, CG:295CG:296 filtering, CG:307CG:308 message stream interface output options setting defaults, CG:302 Message Stream Interface. See MSI message target rules template syntax, message_notification_dlg option, AR_I:275 message_notification_dlg_app option, message_notification_dlg_app_path option, message_notification_show_all option,
AR_I:276 AR_I:275 AR_I:275 AR_I:127

messages See also acknowledgements; acknowledging; escalating messages; message browser; message conditions; message groups; message keys; message source templates; message sources acknowledging automatically, CG:157 overview, CG:169CG:170 with message keys, CG:342 annotating, CG:166CG:168 annotating acknowledged, CG:343 API, CG:367CG:368 attributes, AR_I:75AR_I:77 resolving, CG:300 time, CG:425 browsing effectively, CG:123CG:128 buffering, CG:43, CG:415 parameters, AR_I:131 catalogue, CG:296 classifying unmatched, CG:55 closing, CG:165 collecting, CG:297CG:298 colors overview, CG:99 switching, CG:196 comparing, CG:43 conditions, specifying, CG:366 consolidating in browser, CG:284 control-switched, CG:449 correcting, CG:369 correlating, CG:336 different sources, CG:405 flexible management environments,
CG:410

managed nodes, CG:408 management server, CG:409 types, CG:336 with events, CG:334 customizing columns, CG:126 defaults, CG:301CG:302, CG:303 custom message attributes, CG:301 message attributes, CG:301 details, CG:135 escalated message, CG:428

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

517

Master Index
distribution lists, CG:453CG:456 duplicate SNMP devices, CG:393 error, AR_I:335 escalating, CG:164, CG:428CG:431 evaluating impact, CG:296 severity, CG:296 examining attributes, CG:135 filtering, CG:55 managed node, CG:332 management server, CG:332 sources, CG:307CG:308 strategies, CG:332CG:355 through multiple templates, CG:305 with conditions, CG:307CG:331 formatting, CG:56 forwarding, CG:425 between management servers, notification system, AR_I:132 OpenView Operations for Windows management server, AR_I:204 strategies, CG:456CG:459 template, AR_I:136AR_I:138 trouble ticket system, AR_I:132 unmatched messages, AR_I:337 generating continuous, CG:381 policy, CG:378CG:381 with reset, CG:379 without reset, CG:380 groups, CG:56 incoming, CG:312CG:314 intercepting application messages, AR_I:227 description, CG:43 MPE/iX managed nodes,
AR_II:151AR_II:156

locating, CG:295 logfile, CG:361CG:366 logging description, CG:43 results, CG:356CG:357 managing, CG:55, CG:283CG:284 marking, CG:272 modifying attributes, CG:136 MPE/iX console overview, CG:398CG:401 variables, AR_I:162 notification, CG:451CG:452 overview, CG:51CG:56, CG:100 owning, CG:153CG:154, CG:272, pattern-matching, CG:315CG:323 policies, CG:123CG:128, CG:281CG:418 processing description, CG:52CG:54 on management server, CG:309 overview, CG:299CG:306 quantity, reducing, CG:334CG:355 regrouping, CG:290, CG:358CG:360 reset, sending automatically, responding, CG:56 reviewing details, CG:100 original text, CG:137 scanning, CG:124 scheduled action variables, AR_I:167 sending to management server OpenView Operations for Windows,
AR_I:196 CG:344CG:346 CG:272CG:274

CG:448CG:459, AR_I:149AR_I:150

VPO, AR_I:200 severity coloring, CG:129CG:131 viewing in Message Dashboard, severity levels, AR_I:74AR_I:75 status, CG:297 suppressing duplicate, CG:347 multiple, CG:306 switching control, CG:449CG:450 target rules, CG:441
CG:142CG:146

sources, CG:51CG:52, CG:297CG:298 interface, CG:367CG:368 investigating message histories, CG:148CG:149 pending messages, CG:150 keys, CG:336 linking logically, CG:52

518

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
template conditions, CG:52 templates, CG:365 threshold monitors, CG:369CG:389 unbuffering, CG:104 automatically, CG:415 manually, CG:415CG:416 viewing in message browser, CG:122 metrics See performance metrics MF_ICA_Browser object, AR_II:433 MF_Prog_Neighbourhood object, AR_II:433 MIB managed node, AR_I:386AR_I:387 object monitors, CG:371 Microsoft. See Windows NT/2000 managed nodes midaemon monitor template, AR_II:225 minimum threshold, CG:377 Minor message severity level, AR_I:74 Mirrored Devices application, AR_II:196 mirrored online redo logs, AR_I:455 Misc message group MPE/iX, AR_II:151 VPO, AR_I:72 missing OS patches for Solaris, AR_II:289 mixed clusters, AR_I:192 moa* temporary file, AR_I:308 modes archive log database, AR_I:438, AR_I:442 enabling, AR_I:443AR_I:444 auditing, AR_I:428 MC/ServiceGuard maintenance, AR_II:459 ownership, CG:153, CG:273CG:274 ownership display, CG:154, CG:272CG:273 Modify Message Attributes dialog box figure, CG:136 Modify VPO Interface Messages window,
CG:368

monitored objects See also monitoring AIX, AR_II:62 Citrix MetaFrame, AR_II:433 HP-UX (VPO), AR_II:94 Linux, AR_II:129 MPE/iX, AR_II:157 Novell NetWare (none), AR_II:188 Sequent DYNIX, AR_II:238 SGI IRIX, AR_II:254 SINIX RM/Reliant, AR_II:273 Solaris (VPO), AR_II:301 Sun Enterprise E10000, AR_II:314 Tru64 UNIX, AR_II:339 Windows NT/2000, AR_II:388 monitoring See also monitor agent; monitored objects application integration, AR_I:225 logfiles, AR_I:226 environment, CG:120 managed nodes, CG:209 objects external, CG:373 MIB, CG:372 program, CG:372 performance metrics, CG:374 performance with NMA, AR_II:191 programs, CG:370 SMS, AR_II:442 Sun Enterprise E10000, variables, CG:377 Motif GUI accessing, AR_I:417 comparison with Java GUI, improving performance, AR_I:322 variables, AR_I:169AR_I:183 Motif GUI documentation See alsoGUI; Java GUI Motif SAM, AR_II:95 moving panes and areas, CG:183 MPE/iX console See also MPE/iX managed nodes accessing programs, AR_I:418
AR_I:268AR_I:270 AR_II:310AR_II:311

modifying conditions, CG:315 logfile templates on Tru64 UNIX, AR_II:338 message groups, AR_I:73 node groups, AR_I:71 monagtq queue file, AR_I:307 monitor agent, CG:371CG:376 See also monitoring Monitor Console application, AR_II:159

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

519

Master Index
messages advanced options, CG:400 condition examples, CG:400CG:401 intercepting, CG:398CG:399 interceptor, CG:398 overview, CG:398CG:401 templates, CG:399CG:400 variables, AR_I:162 MPE/iX Database monitoring template group, AR_II:150 MPE/iX managed nodes See also MPE/iX console agent jobs, AR_II:145 applications, AR_II:158AR_II:160 DCE daemon, AR_II:143 default operator, AR_II:144, AR_II:163 de-installing agents, AR_II:149 directory structure, AR_II:163 domain name resolution, AR_II:145 executable libraries, AR_II:145 file locations, AR_II:163 filename tips, AR_II:157 hardware requirements, AR_II:141 include file, AR_II:168 installation requirements, AR_II:141AR_II:142 tips, AR_II:143AR_II:146 installing agents, AR_II:149 intercepting messages default message mapping, AR_II:151 generating new NMEV marker, mapping messages to VPO security levels,
AR_II:152 AR_II:155AR_II:156

mapping ARPA hostnames to NS node names overview, AR_II:164AR_II:167 problems, AR_II:166 resolving names, AR_II:167 vt3k operation, AR_II:165 monitored objects, AR_II:157 NCS daemon, AR_II:143 organization, AR_II:163AR_II:167 overview, AR_II:139AR_II:169 passwords, AR_I:422 preconfigured elements, scripts and programs, AR_II:161AR_II:162 SNMP event interceptor (not supported),
AR_II:157 AR_II:150AR_II:160

software requirements,

spool files, AR_II:146 streamed jobs customizing job stream facility, AR_II:148 excluding networking commands,
AR_II:147

AR_II:141AR_II:142

overview, AR_II:147AR_II:149 preparing VPO, AR_II:149 starting, AR_II:147 SYSSTART.PUB.SYS parameters,

AR_II:147

mapping NMEV markers, overview, AR_II:151AR_II:156 IP addresses, AR_II:144 languages, AR_II:144 libraries, AR_II:168AR_II:169 logfile locations, AR_I:460 templates, AR_II:150 logging group, AR_II:145 login and logout UDCs, AR_II:144 makefile, AR_II:169
AR_II:152AR_II:155

system resource file, AR_II:164 template groups, AR_II:150 time zones, AR_II:146 troubleshooting installation, AR_I:350AR_I:354 runtime, AR_I:374AR_I:380 MPE/iX Network monitoring template group, AR_II:150 MPE/iX OS monitoring template group, 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
AR_II:150

520

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

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, <$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, <$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:40 MSGTARGETMANAGERS keyword, MSGTARGETRULECONDS keyword, MSGTARGETRULES keyword, AR_I:120 MSI API, AR_I:228 multi-homed hosts, troubleshooting,
AR_I:388AR_I:396 AR_I:122 AR_I:120 AR_I:157 AR_I:155

N N message attribute, AR_I:76 <$N> variable, AR_I:165 <$NAME> variable, AR_I:161 navigating template group hierarchies, NCP Info application, AR_II:196 NCS AIX managed nodes, AR_II:40 changing, AR_I:54AR_I:56 description, AR_I:41 Net8, restricting access, AR_I:116 NetBios Sessions application, AR_II:402 netcontool application, AR_II:315 netop, CG:66 See also opc_adm; opc_op; operators NetWare Agent Actions application, NetWare Config window, AR_II:191 NetWare message group, AR_I:72 NetWare Performance window, AR_II:192 NetWare template group, AR_II:187 NetWare Tools applications, AR_II:194AR_II:197 window, AR_II:193 NetWare. See Novell NetWare managed nodes Network Computing System. See NCS Network Interfaces application, AR_II:197 Network message group MPE/iX, AR_II:151 VPO, AR_I:72 Network Node Manager. See NNM network security DCE, AR_I:404AR_I:409 overview, AR_I:404AR_I:414 RPC authentication, AR_I:410AR_I:411 SSH, 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:40 NFS troubleshooting, AR_I:397 NLM Files* application, AR_II:198 NMA 2.1 agent, AR_II:190 applications, AR_II:197AR_II:199 description, AR_II:189
AR_II:197 CG:289

multiple disks for configuring database, management servers, CG:419CG:467 messages, suppressing, CG:306 operators, CG:61 parent groups, CG:216 templates configuring, CG:303 processing simultaneously,
CG:304CG:305 AR_I:453AR_I:455

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

521

Master Index
monitoring performance, AR_II:191 NMEV markers generating new, AR_II:155AR_II:156 mapping, AR_II:152AR_II:155 <$NMEV_APPL> variable, AR_I:162 <$NMEV_CLASS> variable, AR_I:162 <$NMEV_SEV> variable, AR_I:162 NNM accessing from Java GUI locally, AR_I:279AR_I:280 remotely, AR_I:280AR_I:281 collection stations with VPO agents, CG:463 on multiple management servers, CG:467 configuring access with command-line tools, AR_I:283 event correlation, CG:407 integrating applications into VPO, limitations, AR_I:216 integrating into VPO, AR_I:215 running on MC/ServiceGuard, AR_II:456 SNMP event interceptor, CG:391 No Status Propagation display mode, No Status Propagation display mode, CG:273 Node Advanced Options window, CG:226 Node Communication Options window, Node Config Report, AR_I:111 Node Group Bank window, AR_I:71 Node Group Report, AR_I:111 node groups adding, AR_I:71 default, AR_I:71 deleting, AR_I:71 management server, AR_I:71 modifying, AR_I:71 Node Groups Overview Report, AR_I:111 node hierarchies, CG:214CG:215 node mapping tool, AR_I:285AR_I:286 Node message attribute, AR_I:77 Node Reference Report, AR_I:111 Node Report, AR_I:112 node. See adoptive node; cluster nodes; managed nodes, upgrading; original node Nodes folder colors, CG:78 figure, CG:77
CG:227 CG:154 AR_I:216AR_I:221

groups, CG:77 layout groups, CG:77 overview, CG:77CG:78 Nodes Overview Report, AR_I:112 nodes. See managed nodes; node groups: node hierarchies non-sequential conditions, CG:315 Normal message severity level, AR_I:74 nosec option, AR_I:272, AR_I:276 notification, CG:451 notification system forwarding messages, AR_I:132 messages, CG:451CG:452 notification, message event, CG:122 Novell NetWare managed nodes APIs, AR_II:205AR_II:206 applications NetWare Tools, AR_II:194AR_II:197 NMA, AR_II:197AR_II:199 overview, AR_II:189AR_II:199 assigning passwords, AR_I:423 default operator, AR_II:203 directory structure, AR_II:202 file locations, AR_II:202 hardware requirements, AR_II:173 include file, AR_II:207 installation process, AR_II:179AR_II:180 requirements, AR_II:173AR_II:175 tips, AR_II:176AR_II:179 installing agents, AR_II:181AR_II:186 libraries, AR_II:207AR_II:208 logfile templates, AR_II:187 makefile, AR_II:208 monitored objects (none), AR_II:188 NMA 2.1 agent, AR_II:190 applications, AR_II:197AR_II:199 description, AR_II:189 monitoring performance, AR_II:191 organization, AR_II:202AR_II:204 overview, AR_II:171AR_II:208 preconfigured elements, removing agents, AR_II:186 scripts and programs, AR_II:200AR_II:201 SNMP event interceptor, AR_II:188
AR_II:187AR_II:199

522

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
software requirements, popup menu, CG:113 folders Applications, CG:81 Filter Settings, CG:82CG:83 Message Groups, CG:79CG:80 Nodes, CG:77CG:78 URL Shortcuts, CG:84 moving, CG:183 overview, CG:75CG:76 popup menus, CG:113 saving message browser to, CG:195 showing, CG:185 object status, reviewing, CG:155 object tree, searching overview, CG:121 objects. See monitoring ODI Info application, AR_II:198 offline backups, AR_I:439 olh_About_Server_Config, AR_II:410 olh_About_Server_Stats, AR_II:411 olh_About_Shares, AR_II:412 online documentation figure, CG:91 Online Help workspace, CG:91 OpC message group, AR_I:72 opc process, AR_I:297 OPC_ACCEPT_CTRL_SWTCH_ACKN parameter, AR_I:138 OPC_ACCEPT_CTRL_SWTCH_MSGS parameter, AR_I:138 OPC_ACCEPT_NOTIF_MSSGS parameter, opc_adm, CG:62CG:63 See also netop; opc_op; operators OPC_AUTO_DEBUFFER parameter, .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 AR_I:131 AR_I:138

AR_II:173AR_II:175 system resource files, AR_II:203 template groups, AR_II:187

windows NetWare Config, AR_II:191 NetWare Performance, AR_II:192 NetWare Tools, AR_II:193 NS node name mapping, AR_II:164AR_II:167 NT. See Windows NT/2000 managed nodes NT_DWN_SMS_CLIENT_CONFIG_MANA GER monitor, AR_II:442 NT_DWN_SMS_EXECUTIVE monitor,
AR_II:442

NT_DWN_SMS_HIERARCHY_MANAGER monitor, AR_II:442 NT_DWN_SMS_INVENTORY_AGENT monitor, AR_II:442 NT_DWN_SMS_PACKAGE_COMMAND_M ANAGER monitor, AR_II:442 NT_DWN_SMS_SITE_CONFIG_MANAGE R monitor, AR_II:442 NT_DWN_SMS_TRAP_FILTER monitor,
AR_II:442

NT_UP_SMS_CLIENT_CONFIG_MANAGE R monitor, AR_II:442 NT_UP_SMS_EXECUTIVE monitor,

AR_II:442

NT_UP_SMS_HIERARCHY_MANAGER monitor, AR_II:442 NT_UP_SMS_INVENTORY_AGENT monitor, AR_II:442 NT_UP_SMS_PACKAGE_COMMAND_MA NAGER monitor, AR_II:442 NT_UP_SMS_SITE_CONFIG_MANAGER monitor, AR_II:442 NT_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:77 object names, localizing, AR_I:263 object pane figures enabling, CG:185 main window, CG:75

$OPC_EXACT_SELECTED_NODE_LABEL S variable, AR_I:172 $OPC_EXT_NODES variable, AR_I:169 OPC_FORW_CTRL_SWTCH_TO_TT parameter, AR_I:138 OPC_FORW_NOTIF_TO_TT parameter,
AR_I:138

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

523

Master Index
opc_get_ems_resource monitor executable, <$OPC_GUI_CLIENT> variable, AR_I:158 $OPC_GUI_CLIENT variable, AR_I:172 $OPC_GUI_CLIENT_WEB variable, <$OPC_MGMTSV> variable, AR_I:157, $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, $OPC_MSG.ANNOTATIONS[n] variable, $OPC_MSG.APPLICATION variable, $OPC_MSG.ATTRIBUTES variable, $OPC_MSG.CREATED variable, AR_I:177 $OPC_MSG.DUPLICATES variable,
AR_I:178 AR_I:177 AR_I:177 AR_I:177 AR_I:176 AR_I:159 AR_I:172 AR_II:106

$OPC_MSG.ESCALATION.BY variable, $OPC_MSG.ESCALATION.TIME variable, $OPC_MSG.ESCALATION.TO variable, $OPC_MSG.GROUP variable, AR_I:178 $OPC_MSG.INSTRUCTIONS variable, $OPC_MSG.LAST_RECEIVED variable, $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, $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, $OPC_MSG.TYPE variable, AR_I:181 $OPC_MSG_GEN_NODES variable, $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:171 OPC_ONE_LINE_MSG_FORWARD parameter, AR_I:138 opc_op, CG:66 See also netop; opc_adm; operators OPC_SEND_ACKN_TO_CTRL_SWTCH parameter, AR_I:138 OPC_SEND_ANNO_TO_CTRL_SWTCH parameter, AR_I:138 OPC_SEND_ANNO_TO_NOTIF parameter,
AR_I:138 AR_I:170 AR_I:181 AR_I:180 AR_I:179 AR_I:178 AR_I:178 AR_I:178 AR_I:178

OPC_SEND_ANT_TO_CTRL_SWTCH parameter, AR_I:139

524

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
OPC_SEND_ANT_TO_NOTIF parameter, $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:298 opcerr getting error instructions, AR_I:338 opcforwm process, AR_I:299 opcinfo file location on managed nodes, AR_I:325 setting community name, AR_I:386 opcle process, AR_I:305 opclic command parameters, AR_I:464AR_I:465 syntax, 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:305 opcmsg templates HP-UX (VPO), AR_II:90 Solaris (VPO), AR_II:296 Windows NT/2000 (VPO), AR_II:385 opcmsg for OV Performance message template, AR_II:224 opcmsg(1) command description, AR_I:483 flow, CG:367 opcmsg(3) API description, AR_I:483 EMS, AR_II:106 flow, CG:367 opcmsga process, AR_I:306
AR_I:139

opcmsgi process, AR_I:306 opcmsgm process, AR_I:298 opcmsgr process, AR_I:299 opcmsgrd process, AR_I:299 opctmpldwn, 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:198 opening Download Configuration Data window,
AR_I:437

OpenView applications in Java GUI,

AR_I:281AR_I:283

integrating Ethernet Traffic HP as OV application,

AR_I:218

IP Activity Monitoring - Tables as OV service, AR_I:219 internal traps, AR_II:92 maintaining, AR_I:456 OpenView applications, accessing, CG:147 OpenView Operations for Windows configuring agent policy, AR_I:207 agents for VPO management server, servers to forward messages to VPO, VPO agents for management server, exporting policies to VPO, AR_I:210 forwarding messages on managment server, AR_I:204 importing VPO templates, AR_I:209 interoperability with VPO, sending messages to management server,
AR_I:196 AR_I:195AR_I:210 AR_I:196AR_I:199 AR_I:203AR_I:208 AR_I:200AR_I:202

OpenView Performance Agent. See OVPA OpenView VantagePoint Operations. See VPO

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

525

Master Index
Oper. Active Details Report, AR_I:112 Oper. Active Message Report, AR_I:112 operating systems AIX, AR_II:37AR_II:70 HP-UX OVPA, AR_II:209AR_II:230 VPO, AR_II:71AR_II:113 Linux, AR_II:115AR_II:137 MPE/iX, AR_II:139AR_II:169 Novell NetWare, AR_II:171AR_II:208 Sequent DYNIX, AR_II:231AR_II:245 SGI IRIX, AR_II:247AR_II:261 SINIX RM/Reliant, AR_II:263AR_II:280 Solaris OVPA, AR_II:209AR_II:230 patches, AR_II:289 VPO, AR_II:281AR_II:322 Tru64 UNIX, AR_II:323AR_II:347 Windows NT/2000, AR_II:349AR_II:444 Operator History Messages Report, AR_I:112 operator instructions reading, CG:158CG:159 Operator Overview Report, AR_I:112 Operator Pending Messages Report, AR_I:112 Operator Report, AR_I:112 operator-initiated actions annotations, CG:158 corrective actions, CG:369 process, CG:59CG:60 protecting, AR_I:424 reviewing, CG:157 starting, CG:157 verifying, CG:157CG:158 operators See also netop; opc_adm; opc_op; template administrators; users; VPO administrator accessing GUI Java, AR_I:418 Motif, AR_I:417 assigning applications, AR_I:213 changing names, AR_I:415 passwords, AR_I:415 default AIX, AR_II:67 HP-UX, AR_II:100 Linux, AR_II:134AR_II:135 MPE/iX, AR_II:163 Novell NetWare, AR_II:203 Sequent DYNIX, AR_II:242 SGI IRIX, AR_II:258 SINIX RM/Reliant, AR_II:277 Solaris, AR_II:305 Tru64 UNIX, AR_II:343 Windows NT/2000, AR_II:427 description, CG:65CG:67 enabling to control VPO agents, AR_I:220AR_I:221 to manage IP networks in IP map,
AR_I:217

mathematical, CG:315CG:316 multiple, CG:61 reports customized, AR_I:115 preconfigured, AR_I:114 saving output, AR_I:416 security, AR_I:415AR_I:427 types, CG:66 windows, CG:66CG:67 optimizing message filtering, CG:332CG:355 performance, CG:332CG:333 Optional ownership mode, CG:153, CG:274 <$OPTION(N)> variable, AR_I:157 options Automatic (De-)Installation, AR_I:51 tracing, AR_I:327 organizing conditions overview, CG:314CG:315 sequence, CG:332 managed nodes AIX, AR_II:66AR_II:67 HP-UX, AR_II:99AR_II:101 Linux, AR_II:133AR_II:135 MPE/iX, AR_II:163AR_II:167 Novell NetWare, AR_II:202AR_II:204 overview, CG:208CG:231 Sequent DYNIX, AR_II:241AR_II:243 SGI IRIX, AR_II:257AR_II:259 SINIX RM/Reliant, AR_II:276AR_II:278 Solaris, AR_II:304AR_II:306 Tru64 UNIX, AR_II:342AR_II:344

526

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
Windows NT/2000, AR_II:426AR_II:428 message groups overview, CG:232CG:233 template groups, CG:288CG:289 organizing Message Groups folder, CG:80 original message text, reviewing, CG:137 original node, AR_II:448 See also adoptive node; cluster nodes, MC/ServiceGuard; managed nodes, upgrading OS message group MPE/iX, AR_II:151 VPO, 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:118 outages, scheduling, CG:417 output EMS Resources application, AR_II:111 operator, CG:202, AR_I:416 VPO administrator, AR_I:417 Output message group MPE/iX, AR_II:151 VPO, AR_I:72 OV Performance Agent template group, OV Performance Manager template group, ovbackup.ovpl command,
AR_I:445AR_I:446 AR_II:224 AR_II:224

disk space requirements, AR_II:218 documentation downloading, AR_II:227 English language, AR_II:228 Japanese language, AR_II:230 PDFs, AR_II:227 viewing, AR_II:227 GlancePlus Trial, AR_II:213 hardware requirements, AR_II:215 HP-UX, AR_II:209AR_II:230 installation requirements, installing on managed nodes, overview, AR_II:209AR_II:230 SINIX RM/Reliant, AR_II:211 software requirements, Solaris, AR_II:209AR_II:230 templates, AR_II:224AR_II:226 Tru64 UNIX, AR_II:211 ovrestore.ovpl command,
AR_I:446AR_I:449 AR_II:216AR_II:217 AR_II:219AR_II:220 AR_II:214AR_II:218

ownership display modes, CG:154, CG:272CG:273 messages, CG:153CG:154, CG:272CG:274 modes, CG:153, CG:273CG:274 Ownership policy, CG:124 owning messages, CG:272 P package, AR_II:448 package custody, AR_II:448 package IP/hostname, AR_II:448 packages assigning IP addresses and hostnames,
AR_II:455

OVKey licenses advantages, AR_I:462 replacing Instant On, AR_I:462 OVnlm_exit() API, AR_II:205 OVnlm_init() API, AR_II:205 ovoareqsdr process, AR_I:297 OVPA AIX, AR_II:211 applications, AR_II:223 customizing, AR_II:213 data analyzing, AR_II:212 integrating, AR_II:212 logging, AR_II:212 de-installing from managed nodes,
AR_II:221

description, AR_II:212AR_II:213

enabling maintenance mode for MC/ServiceGuard, AR_II:459 panes and areas moving, CG:183 showing and hiding, CG:185CG:187 parameters See also variables kernel, AR_I:40 message buffering, AR_I:131 opclic command, AR_I:464AR_I:465

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

527

Master Index
scheduled outages syntax, AR_I:131 SYSSTART.PUB.SYS, AR_II:147 templates message forwarding, AR_I:138 scheduled outages, AR_I:131 service hours, AR_I:131 time zone string, AR_I:135 passwd option, AR_I:272, AR_I:276 passwords aging, AR_I:419 assigning, AR_I:422AR_I:423 changing, CG:172, AR_I:415 controlling, AR_I:415 DCE nodes, AR_I:420AR_I:421 root, AR_I:49 patches, Solaris, AR_II:289 pattern matching condition examples, CG:316CG:317 mathematical operators, CG:315CG:316 messages, CG:315CG:323 returning node names, AR_I:285 syntax, CG:318CG:320 without case-sensitivity, CG:316 pattern-matching options setting defaults, CG:302 PDF documentation OVPA, AR_II:227 pending messages browser See also active message browser; filtered message browser; history message browser; message browser investigating problems, CG:150 overview, CG:104 unbuffering messages, CG:104 perflbd monitor template, AR_II:225 PerfMon Objs application, AR_II:403 performance improving database, AR_I:319 Motif GUI startup, AR_I:322 SNMP management platform, VPO, AR_I:320AR_I:321 Java GUI, AR_I:290AR_I:291 monitoring, CG:43 NMA, AR_II:191
AR_I:318AR_I:319

optimizing, CG:332CG:333 tuning, AR_I:318AR_I:322 UNIX with JIT, AR_I:290 Performance Agent. See OVPA Performance message group MPE/iX, AR_II:151 VPO, AR_I:73 performance metrics about, CG:374 configuring, CG:375 monitoring, CG:374 permissions file access, AR_I:416 GUI, AR_I:417AR_I:418 setting group, AR_I:416 setting file, AR_I:416 Personal Filters, CG:83 Physical Terminal application, AR_II:159 pids file, AR_I:302, AR_I:308 pipe files managed nodes, AR_I:307AR_I:308 management server, AR_I:301AR_I:303 plug-in, HP OpenView application, AR_I:214 point-to-point problems, AR_I:389 policies changing WM1 default name, AR_I:208 importing OpenView Operations for Windows policies into VPO, AR_I:210 message escalation, CG:429 messages, CG:123CG:124 polling intervals MIB objects, CG:372 programs, CG:372 popup menus browser pane, CG:116 customizing, CG:189CG:190 object pane, CG:113 overview, CG:111 shortcut bar, CG:112 workspace pane, CG:114 port option, AR_I:276 position controls figures enabling, CG:182 main window, CG:110 hiding, CG:182 overview, CG:110

528

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
showing, CG:182 PRC authentication, AR_I:407 preconfigured elements, AR_I:71AR_I:109 AIX, AR_II:59AR_II:63 HP-UX (OVPA), AR_II:223AR_II:226 HP-UX (VPO), AR_II:90AR_II:95 Linux, AR_II:128AR_II:129 MPE/iX, AR_II:150AR_II:160 Novell NetWare, AR_II:187AR_II:199 Sequent DYNIX, AR_II:237AR_II:238 SGI IRIX, AR_II:253AR_II:254 SINIX RM/Reliant, AR_II:272AR_II:273 Solaris (OVPA), AR_II:223AR_II:226 Solaris (VPO), AR_II:296AR_II:301 Sun Enterprise E10000,
AR_II:311AR_II:315 Tru64 UNIX, AR_II:337AR_II:339 Windows NT/2000, AR_II:380AR_II:391

preventing, AR_I:323AR_I:324 registering, CG:45 solving, CG:45, CG:151CG:152 process, CG:117CG:118 tracing, AR_I:326AR_I:333 troubleshooting, AR_I:323AR_I:339 database, AR_I:340AR_I:342 embedded performance component, GUI on management server, installation on managed nodes, AR_I:348 installation on MPE/iX managed nodes, installation with multi-homed hosts, local location brokers, AR_I:381 mixed-case node names, AR_I:349 NSF, AR_I:397 RPC daemons, AR_I:381 runtime on all managed nodes, runtime on MPE/iX managed nodes, runtime on UNIX managed nodes, VPO server, AR_I:343AR_I:344 proc_util object AIX, AR_II:62 HP-UX, AR_II:94 Sequent DYNIX, AR_II:238 SGI IRIX, AR_II:254 SINIX RM/Reliant, AR_II:273 Solaris, AR_II:301 Procedures policy, CG:124 process files, AR_I:306AR_I:309 groups, AR_I:412 names, AR_I:412 Process Kill application, AR_II:405 processes authentication, AR_I:312AR_I:314 managed node, AR_I:304AR_I:311 management server, AR_I:297AR_I:303 overview, AR_I:293AR_I:314 security, AR_I:312AR_I:314 Processes application, AR_II:160, AR_II:437
AR_I:370AR_I:373 AR_I:374AR_I:380 AR_I:355AR_I:369 AR_I:388AR_I:396 AR_I:350AR_I:354 AR_I:345AR_I:347 AR_I:382AR_I:385

reports administrator, AR_I:111 operator, AR_I:114 Preferences dialog box figures Events tab, CG:191 General tab, CG:189 Web Browsers tab, CG:105 itooprc file, AR_I:273AR_I:278 preventing problems, AR_I:323AR_I:324 primary account creating manually, AR_I:421 disabling, AR_I:421 primary manager, CG:422 specifying, CG:443CG:445 switching responsibility, CG:443CG:444 Print Server application, AR_II:198 Print Status application, AR_II:159 printer, report, AR_I:110 printing group, message target rules, CG:441 man pages, AR_I:497 problems correcting, CG:43 detecting, CG:119 detecting early, CG:283 investigating, CG:132CG:133 message forwarding template, CG:459

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

529

Master Index
processing actions automatic, CG:57CG:58 operator-initiated, CG:59CG:60 managed node files English, AR_I:252AR_I:253 Japanese, AR_I:255AR_I:256 management server files ISO 8859-15, AR_I:251 Shift JIS, AR_I:254 messages escalated messages, CG:430CG:431 forwarded, CG:453 on management server, CG:309 overview, CG:299CG:306 tasks, CG:52CG:54 templates, multiple, CG:304CG:305 productivity, improving, CG:283 profiles management, CG:433 user, CG:62 <$PROG> variable, AR_I:167 Program Neighbourhood service, AR_II:433 programs accessing HP-UX, AR_I:418 MPE/iX, AR_I:418 distribution AIX, AR_II:64AR_II:65 HP-UX, AR_II:96AR_II:98 Linux, AR_II:130AR_II:132 MPE/iX, AR_II:161AR_II:162 Novell NetWare, AR_II:200AR_II:201 overview, AR_I:188AR_I:192 requirements, AR_I:188 Sequent DYNIX, AR_II:239AR_II:240 SGI IRIX, AR_II:255AR_II:256 SINIX RM/Reliant, AR_II:274AR_II:275 Solaris, AR_II:302AR_II:303 tips, AR_I:188AR_I:191 Tru64 UNIX, AR_II:340AR_II:341 Windows NT/2000, AR_II:424AR_II:425 monitors, CG:371 security, AR_I:418 prompt_for_activate option, AR_I:276 properties, changing default types of all messages forwarded to VPO, AR_I:208 protecting automatic actions, AR_I:424 configuration distribution, AR_I:423 operator-initiated actions, AR_I:424 remote actions, AR_I:425AR_I:427 shell scripts, AR_I:424 template distribution, AR_I:423 pvalarmd monitor template, AR_II:226 Q queue files managed nodes, AR_I:307AR_I:308 management server, AR_I:301AR_I:303 removing, AR_I:451 security, AR_I:427 Queues application, AR_II:198 quick filters, accessing, CG:195 R <$R> variable, AR_I:165 <$r> variable, AR_I:165 ratio, management hierarchy setup, CG:434 Reactivate alarmdef application, AR_II:223 reading operator instructions, Reboot application, AR_II:406 reconfiguring management server after changing hostname or IP address,
AR_I:470AR_I:474 CG:158CG:159

SSP snmpd daemon, AR_II:316 templates, 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:276 recovering See also recovery tools configuration data after automatic backup, database to latest state, AR_I:450AR_I:451 recovery tools, AR_I:438 See also recovering redistributing scripts to all managed nodes, redo logs, creating another set, AR_I:455
AR_I:438 AR_I:449AR_I:451

530

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
reducing number of messages, redundant data on MC/ServiceGuard,
AR_II:453AR_II:454 CG:334CG:355

refresh interval changing, CG:178 refresh_interval option, AR_I:272, AR_I:276 Reg Viewer application, AR_II:407 regional management servers configuring, CG:437CG:438 description, CG:434 managed nodes, CG:437CG:438 reconfiguring VPO agents, CG:437 registering problems, CG:45 regroup conditions See also regrouping messages defining, CG:359 examples, CG:360 Regroup Conditions window, CG:359 regrouping messages See also regroup conditions description, CG:290 overview, CG:358CG:360 Reliant. See SINIX RM/Reliant managed nodes remote access See also remote actions applications, AR_I:420 broadcast commands, AR_I:420 I/O applications, AR_I:420 remote actions See also remote access example, AR_I:425 protecting, AR_I:425AR_I:427 security mechanisms, AR_I:426AR_I:427 remote host equivalence, establishing,
AR_II:317

Linux, AR_II:127 Novell NetWare, AR_II:186 SGI IRIX, AR_II:252 SINIX RM/Reliant, AR_II:271 Solaris, AR_II:295 Removing Older Agents, AR_II:127 rep_server monitor template, AR_II:225 replacing Instant On licenses with OVKey licenses, AR_I:462 reporting errors GUI Error Dialog Box, AR_I:337AR_I:338 message browser, AR_I:336 overview, AR_I:335AR_I:339 stderr and stdout devices, AR_I:338 reports administrator customized, AR_I:113 preconfigured, AR_I:111 configuring timeouts, AR_I:110 database, AR_I:110AR_I:116 defining printer, AR_I:110 generating, CG:46 Internet, AR_I:110 operator customized, AR_I:115 preconfigured, AR_I:114 security, AR_I:116 statistical, AR_I:115 trend analysis, AR_I:115 requirements. See distribution; installation requirements rerunning automatic actions, CG:156 reset message, sending automatically,
CG:344CG:346

remote installation Linux, AR_II:123 removing See also de-installing; installing DCE AIX, AR_II:45 SINIX RM/Reliant, AR_II:270 Tru64 UNIX, AR_II:331 queue files, AR_I:451 VPO agents, AR_I:66 AIX, AR_II:58

resetting events HACMP 4.2.2, AR_II:55 HACMP 4.3.1, AR_II:55AR_II:56 IP alias for HACMP agents in GUI, AR_II:54 resolving message attributes, CG:300 resource instances, viewing in EMS GUI, RESPMGRCONFIG keyword, AR_I:119 responding to messages, CG:56 responsibility See also responsible managers distributing in competence centers,
CG:426CG:427 AR_II:109

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

531

Master Index
domain hierarchy management,
CG:434CG:435

ROMAN8, converting managed node files,

AR_I:252

management server delegating, CG:444 switching, CG:443CG:445 operator matrix, CG:204 responsible managers See also responsibility configuration file creating, CG:439 distributing, CG:440 configuring, CG:439CG:447 templates managed nodes, CG:440 syntax, AR_I:125 Restart PA Servers application, AR_II:223 Restart Perf Agt application, AR_II:223 restoring database, AR_I:450 restricting See also restrictions database access, AR_I:116 Net8 access, AR_I:116 web reporting, AR_I:116 restrictions See also restricting C2 security, CG:207 VPO access, CG:62 results, action, CG:155 reversing manager switch, CG:444 reviewing acknowledgements, CG:170 annotations actions, CG:155 messages, CG:168 automatic actions, CG:156 messages attribites, CG:135 details, CG:100 groups, CG:233 object status, CG:155 operator-initiated actions annotations, CG:158 overview, CG:157 Rlp Serv (DYNIX/ptx) template, AR_II:237 RM/Reliant. See SINIX RM/Reliant managed nodes roles, user, CG:61

root passwords, AR_I:49 user, AR_I:419 RPC authentication, AR_I:410AR_I:411 configuring in VPO, AR_I:411 VPO example, AR_I:411 login context, AR_I:410 server ticket description, AR_I:410 verifying, AR_I:410 troubleshooting, AR_I:381 rqsdbf file, AR_I:302 rqsp pipe file, AR_I:303 rqsq queue file, AR_I:303 rules, message target, CG:441 Running Software* application, AR_II:198 runtime problems all managed nodes, AR_I:355AR_I:369 managed node directories, AR_I:459 MPE/iX managed nodes, AR_I:374AR_I:380 UNIX managed nodes, AR_I:370AR_I:373 S S message attribute, AR_I:75 <$S> variable, AR_I:166 <$s> variable, AR_I:166 SAM ASCII, AR_II:95 Motif, AR_II:95 VPO Application Bank window, sam command, AR_II:95 Save Browser Filter Settings dialog box figure, CG:194 saving console settings figure, CG:179 overview, CG:179CG:180 customized message browser layout, CG:198 message browser filter object pane, CG:195 settings, CG:193CG:194 output operator, CG:202, AR_I:416
AR_II:110AR_II:111

532

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
VPO administrator, AR_I:417 scalability multiple management servers, scenarios, CG:460CG:467 scanning messages, CG:124 scenarios automating standard, CG:341 scalability multiple management servers,
CG:465CG:466 CG:419CG:467

ito_restore.sh, AR_I:449 redistributing, AR_I:438 shell, protecting, AR_I:424 versions, AR_I:188 SD-UX See also HP-UX managed nodes creating software depot on remote node, enabling, AR_II:82 installing VPO agents from depot node, AR_II:79 from SD-UX depot, AR_II:82 manually from depot, AR_II:85 manually from tape file, AR_II:84 overview, AR_II:79AR_II:82 searching object tree overview, CG:121 second disk, moving database control files,
AR_I:454 AR_II:80AR_II:81

multiple management servers with VPO agents and NNM collection stations,
CG:467

NNM collection station with VPO agents, single management server, VPO agents monitoring IP devices, CG:462 scheduled outages configuring, CG:418 defining, CG:417 overview, CG:417 template examples, AR_I:152 location, AR_I:130 parameters, AR_I:131 syntax, AR_I:128AR_I:130 scheduling templates, AR_I:130AR_I:135 scopeux monitor template, AR_II:225 scripts customized, AR_I:189 distributing, AR_I:188AR_I:192 distribution AIX, AR_II:64AR_II:65 HP-UX, AR_II:96AR_II:98 Linux, AR_II:130AR_II:132 MPE/iX, AR_II:161AR_II:162 Novell NetWare, AR_II:200AR_II:201 requirements, AR_I:188 Sequent DYNIX, AR_II:239AR_II:240 SGI IRIX, AR_II:255AR_II:256 SINIX RM/Reliant, AR_II:274AR_II:275 Solaris, AR_II:302AR_II:303 tips, AR_I:188AR_I:191 Tru64 UNIX, AR_II:340AR_II:341 Windows NT/2000, AR_II:424AR_II:425
CG:460CG:461 CG:463CG:464

secondary manager enabling actions, CG:444 specifying, CG:436 switching responsibility, CG:443CG:444 SECONDARYMANAGERS keyword, secure_port option, AR_I:276 securing environment, CG:205CG:207 security auditing, AR_I:428AR_I:431 C2, CG:206CG:207 guidelines, AR_I:402 restrictions, AR_I:403 database, AR_I:419 exception warnings, AR_I:291 levels, AR_II:152 managed nodes, CG:229 network DCE, AR_I:404AR_I:409 overview, AR_I:404AR_I:414 RPC authentication, AR_I:410AR_I:411 operations accessing VPO, AR_I:415 overview, AR_I:415AR_I:427 overview, AR_I:399AR_I:431 processes, AR_I:312AR_I:314 program, AR_I:418 remote actions, AR_I:426AR_I:427
AR_I:119

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

533

Master Index
reports, AR_I:116 SSH, AR_I:414 system, AR_I:402AR_I:403 types, AR_I:401 VPO, CG:206 levels, AR_I:413 process, AR_I:412AR_I:413 Security message group MPE/iX, AR_II:151 VPO, AR_I:73 Sel. Active Details Report, AR_I:114 Sel. Active Messages Report, AR_I:114 Sel.History Details Report, AR_I:114 Sel. History Messages Report, AR_I:114 Sel. Pending Details Report, AR_I:114 Sel. Pending Messages Report, AR_I:114 selecting conditions, CG:315 message generation policy, CG:378CG:381 threshold types, CG:377 semmns parameter, AR_I:40 Send Message application, AR_II:437 sending messages to management server OpenView Operations for Windows,
AR_I:196

installing agents, AR_II:236 libraries, AR_II:244AR_II:245 logfile templates, AR_II:237 makefile, AR_II:245 monitored objects, AR_II:238 organization, AR_II:241AR_II:243 overview, AR_II:231AR_II:245 preconfigured elements, scripts and programs, AR_II:239AR_II:240 SNMP event interceptor (not supported),
AR_II:238 AR_II:237AR_II:238

software requirements,

VPO, AR_I:200 reset message automatically,

CG:344CG:346

Sendmail object Linux, AR_II:129 sendmail object AIX, AR_II:62 HP-UX, AR_II:94 Sequent DYNIX, AR_II:238 SGI IRIX, AR_II:254 Solaris, AR_II:301 Tru64 UNIX, AR_II:339 Sequent DYNIX managed nodes default operator, AR_II:242 de-installing agents, AR_II:236 directory structure, AR_II:241 file locations, AR_II:241 hardwarre requirements, AR_II:233 include file, AR_II:244 installation requirements, AR_II:233AR_II:234 tips, AR_II:235

system resource files, AR_II:243 template groups, AR_II:237 sequential conditions description, CG:332 selecting, CG:315 Server Config application, AR_II:410 server option, AR_I:272 Server Stats application, AR_II:411 server ticket, RPC, AR_I:410 Servers application, AR_II:437 servers. See management server; managers service hours, CG:104 configuring, CG:418 defining, CG:416 overview, CG:415CG:416 template examples, AR_I:151 location, AR_I:130 parameters, AR_I:131 syntax, AR_I:128, AR_I:130 service template, AR_I:119 services ICA Browser, AR_II:432 MC/ServiceGuard, AR_II:449 OV Service, AR_I:219 Program Neighbourhood, AR_II:433 Services workspace finding impacted VP Navigator services,
CG:147

AR_II:233AR_II:234

overview, CG:88 Sessions application, AR_II:438 Set Parameters* application, AR_II:198 setting character set

534

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
GUI, AR_I:234AR_I:238 managed nodes, AR_I:241 management server, AR_I:234 community name opcinfo file, AR_I:386 SNMP daemon configuration file,
AR_I:387

file permissions, AR_I:416 group permissions, AR_I:416 IP aliases for HACMP agents AIX 4.3, AR_II:52 language managed nodes, AR_I:240 management server, AR_I:233 setting up customized job stream facility on MPE/iX managed nodes, AR_II:148 management hierarchies, CG:434 server defaults, CG:422 message conditions, CG:310CG:314 defaults, CG:301CG:302 node hierarchy, CG:214 threshold monitoring, CG:385CG:386 time intervals in time templates, CG:442 settings compression, CG:350 node defaults, CG:228 settings, console, CG:179CG:180 severity message coloring, CG:129CG:131 viewing in Message Dashboard,
CG:142CG:146

requirements, AR_II:249AR_II:250 tips, AR_II:251 installing agents, AR_II:252 libraries, AR_II:260AR_II:261 logfile templates, AR_II:253 makefile, AR_II:261 monitored objects, AR_II:254 organization, AR_II:257AR_II:259 overview, AR_II:247AR_II:261 preconfigured elements, removing agents, AR_II:252 scripts and programs, AR_II:255AR_II:256 SNMP event interceptor (not supported),
AR_II:253 AR_II:253AR_II:254

software requirements, AR_II:250 system resource files, AR_II:259 template groups, AR_II:253 Shares application, AR_II:412 sharing message control, CG:449 shell scripts, protecting, AR_I:424 Shift JIS converting managed nodes to, AR_I:258 processing management server files,
AR_I:254

severity messages evaluating, CG:296 levels, AR_I:74AR_I:75 Severity policy, CG:124 severity_label option, AR_I:276 SGI IRIX managed nodes default operator, AR_II:258 de-installing agents, AR_II:252 directory structure, AR_II:257 file locations, AR_II:257 hardware requirements, AR_II:249 include file, AR_II:260 installation

shmmax parameter, AR_I:40 shortcut bar customizing, CG:188 figures disabling, CG:186 enabling, CG:185 main window, CG:73 popup menu, CG:112 hiding, CG:185 moving, CG:183 overview, CG:73CG:74 popup menus, CG:112 showing, 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:277 showing message browser columns, CG:197 panes and areas, CG:185CG:187 position controls, CG:182

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

535

Master Index
SIA (Tru64 UNIX) template, AR_II:337 Siemens-Nixdorf. See hardware; SINIX RM/Reliant managed nodes Silicon Graphics Indigo. See hardware; SGI IRIX managed nodes SINIX RM/Reliant managed nodes DCE configuring, AR_II:269 removing, AR_II:270 OVPA, AR_II:211 VPO default operator, AR_II:277 de-installing agents, AR_II:271 directory structure, AR_II:276 file locations, AR_II:276 hardware requirements, AR_II:265 installation requirements, installation tips, AR_II:267AR_II:268 installing agents, AR_II:270 libraries, AR_II:279AR_II:280 logfile templates, AR_II:272 makefile, AR_II:280 monitored objects, AR_II:273 organization, AR_II:276AR_II:278 overview, AR_II:263AR_II:280 preconfigured elements, removing agents, AR_II:271 scripts and programs, SNMP event interceptor (not supported),
AR_II:272 AR_II:274AR_II:275 AR_II:272AR_II:273 AR_II:265AR_II:266

SMS template group, AR_II:380 SNMP configuration file, AR_I:387 event interceptor AIX, AR_II:61 HP-UX (VPO), AR_II:92AR_II:94 Linux (not supported), AR_II:129 MPE/iX (not supported), AR_II:157 Novell NetWare, AR_II:188 Sequent DYNIX (not supported),
AR_II:238

SGI IRIX (not supported), AR_II:253 SINIX RM/Reliant (not supported),

AR_II:272

Solaris (VPO), AR_II:298AR_II:300 Tru64 UNIX (not supported), AR_II:338 Windows NT/2000, AR_II:385AR_II:387 events, CG:390CG:397 improving performance, AR_I:318AR_I:319 traps adding templates, CG:394 condition example, CG:396 defining template conditions, forwarding, CG:392CG:393 OpenView, AR_II:92 overview, CG:390CG:397 Sun Enterprise E10000, AR_II:312 variables, AR_I:163AR_I:166 well-defined, AR_II:92 SNMP message group, AR_I:73 software communication, AR_I:41 debugging (de-)installation,
AR_I:67AR_I:68 CG:394CG:395

software requirements,

system resource files, AR_II:278 template groups, AR_II:272 SINIX template group, AR_II:272 size, message distribution list, smit command, AR_II:63 SMIT User Interface, starting, AR_II:63 SMS integrating into VPO, AR_II:440AR_II:441 integration, AR_II:439AR_II:444 monitors, AR_II:442 versions supported, AR_II:439
CG:453CG:455

AR_II:265AR_II:266

software requirements OVPA HP-UX, AR_II:216 Solaris, AR_II:216AR_II:217 VPO AIX, AR_II:39AR_II:40 HP-UX, AR_II:73AR_II:76 Linux, AR_II:118AR_II:120 MPE/iX, AR_II:141AR_II:142 Novell NetWare, AR_II:173AR_II:175 Sequent DYNIX, AR_II:233AR_II:234 SGI IRIX, AR_II:250

536

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
SINIX RM/Reliant, AR_II:265AR_II:266 Solaris, AR_II:284 Tru64 UNIX, AR_II:326AR_II:327 Windows NT/2000, AR_II:353AR_II:354 Solaris managed nodes See also Sun Clusters; Sun Enterprise E10000; Sun Management Center; Sun SPARCclassic; Sun SPARCserver; Sun SPARCstation; Sun Ultra OVPA de-installing, AR_II:221 disk space requirements, AR_II:218 hardware requirements, AR_II:215 installation requirements, installing, AR_II:219AR_II:220 overview, AR_II:209AR_II:230 preconfigured elements, software requirements,
AR_II:223AR_II:226 AR_II:216AR_II:217 AR_II:214AR_II:218

removing agents, AR_II:295 scripts and programs, SNMP event interceptor, software requirements, AR_II:284 Sun Enterprise Cluster support, AR_II:322 Sun Enterprise E10000, Sun Management Center integration,
AR_II:321 AR_II:310AR_II:320 AR_II:298AR_II:300 AR_II:302AR_II:303

template groups, AR_II:224AR_II:226 VPO activating agents, AR_II:292AR_II:293 default operator, AR_II:305 de-installing agents, AR_II:294 directory structure, AR_II:304 file locations, AR_II:304 hardware requirements, AR_II:283 include file, AR_II:308 installation requirements, installation tips, AR_II:287AR_II:288 installing agents, AR_II:290AR_II:291 libraries, AR_II:307AR_II:309 logfile locations, AR_I:461 logfile templates, AR_II:297 makefile, AR_II:309 MC/ServiceGuard support, AR_II:113 message templates, AR_II:296 missing OS patches, AR_II:289 monitored objects, AR_II:301 organization, AR_II:304AR_II:306 overview, AR_II:281AR_II:322 preconfigured elements,
AR_II:296AR_II:301 AR_II:283AR_II:286

system resource files, AR_II:305 template groups, AR_II:296 solaris node group, AR_I:71 Solaris template group, AR_II:296 solutions, documenting, CG:46, CG:165 solving problems, CG:45 accessing terminal, CG:164 adding VPO variables, CG:162 applications, CG:160CG:161 broadcasting commands, CG:163CG:164 escalating messages, CG:164 evaluating action results, CG:155 overview, CG:151CG:152 owning messages, CG:153CG:154 process, CG:117CG:118 reading operator instructions,
CG:158CG:159

verifying automatic actions, CG:156CG:157 operator-initiated actions, CG:157CG:158 sources, message correlation, CG:405 Spanish VPO, AR_I:259 SPARCclassic. See Sun SPARCclassic SPARCserver. See Sun SPARCserver SPARCstation. See Sun SPARCstation special characters, flexible management templates, AR_I:124 SSH security, AR_I:414 VPO agent installation, AR_I:57AR_I:61 SSP configuring, AR_II:316AR_II:317 establishing remote host equivalence,
AR_II:317

exporting SSP logfiles directory, AR_II:317

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

537

Master Index
reconfiguring snmpd daemon, AR_II:316 SSP templates, AR_II:318, AR_II:320 SSP Tools, AR_II:315 SSP Config application, AR_II:315 SSP message group, AR_I:73 standard de-installation See also de-installing OVPA HP-UX, AR_II:221 Solaris, AR_II:221 VPO MPE/iX, AR_II:149 SINIX RM/Reliant, AR_II:271 Solaris, AR_II:294 Tru64 UNIX, AR_II:336 Windows NT/2000, AR_II:379 standard installation See also installing OVPA HP-UX, AR_II:219 Solaris, AR_II:219 VPO HP-UX, AR_II:78 Linux, AR_II:124 MPE/iX, AR_II:149 SINIX RM/Reliant, AR_II:270 Solaris, AR_II:290 Windows NT/2000, AR_II:367AR_II:372 standard scenarios, automating, CG:341 Start Customized Application wizard figures broadcasting commands, CG:163 Step 2 of 3, CG:161 Step 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:223 starting applications, CG:160 accounts, AR_I:419 managed nodes, AR_I:229AR_I:230 remotely, AR_I:420 broadcast commands managed nodes, AR_I:229AR_I:230 remotely, AR_I:420 corrective actions, CG:369 EMS GUI, AR_II:109 I/O applications remotely, AR_I:420 operator-initiated actions, CG:157 SMIT User Interface, AR_II:63 streamed jobs on MPE/iX managed nodes,
AR_II:147

VPO from operator GUI, CG:202 startup options, Java GUI, state-based browsers, CG:341, statistical reports, AR_I:115 Status Propagation display mode, CG:154 Status Propagation display mode, CG:273 status 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, 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:418 strategies message filtering, CG:332CG:355 message forwarding, CG:456CG:459 streamed jobs on MPE/iX managed nodes customizing job stream facility, AR_II:148 excluding networking commands, AR_II:147 overview, AR_II:147AR_II:149 preparing VPO, AR_II:149 starting, AR_II:147 SYSSTART.PUB.SYS parameters,
AR_II:147 AR_II:225 CG:387CG:388 AR_I:271AR_I:272

strings, time zone, AR_I:134AR_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

538

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
Su (IRIX) template, AR_II:253 Su (SINIX) template, AR_II:272 Su (Solaris) template, AR_II:297 subnets, heartbeat, AR_II:453AR_II:454 subproduct option, AR_I:277 Sun Clusters See also Solaris managed nodes; Sun Enterprise E10000 architecture, AR_II:465 description, AR_II:463AR_II:467 glossary, AR_II:464 overview, AR_II:461AR_II:471 support, AR_II:322 troubleshooting, AR_II:469AR_II:471 VPO agents, AR_II:468 Sun Enterprise E10000 See also Solaris managed nodes; Sun Clusters installing VPO agent, AR_II:318AR_II:320 logfile templates, AR_II:313 managing, AR_II:310AR_II:311 monitored objects, AR_II:314 monitoring, AR_II:310AR_II:311 operating system versions, AR_II:311 overview, AR_II:310AR_II:320 preconfigured elements, SNMP trap interception, AR_II:312 SSP configuring, AR_II:316AR_II:317 SSP Tools, AR_II:315 template groups, AR_II:311 Sun Management Center, AR_II:321 See also Solaris managed nodes Sun Microsystems. See Solaris managed nodes; Sun Clusters; Sun Enterprise E10000; Sun Management Center; Sun SPARCclassic; Sun SPARCserver; Sun SPARCstation; Sun Ultra Sun Solaris. See Solaris Sun SPARCclassic See also Solaris managed nodes Sun SPARCserver See also Solaris managed nodes Sun SPARCstation, AR_II:303 See also Solaris managed nodes Sun Ultra See also Solaris managed nodes
AR_II:311AR_II:315

suppress See also suppressing; suppression conditions deploying, CG:333 description, CG:311CG:314 types, verifying, CG:348CG:350 SUPPRESS parameter, AR_I:131 suppressing See also suppress; suppression duplicate messages, CG:347 flexible management environments,
CG:355

management server, CG:353 multiple messages, CG:306 unmatched conditions, CG:333 suppression See also suppress; suppressing counter, CG:352 time, CG:351 swap_util object AIX, AR_II:62 HP-UX, AR_II:94 Linux, AR_II:129 Sequent DYNIX, AR_II:238 SGI IRIX, AR_II:254 SINIX RM/Reliant, AR_II:273 Solaris, AR_II:301 Tru64 UNIX, AR_II:339 Switch User template, CG:414 switching backup server, CG:445 MC/Service Guard local networks, AR_II:452AR_II:453 packages, AR_II:450AR_II:451 message control, CG:449CG:450 primary management responsibility, reversing switch, CG:444 user for VPO agents, AR_I:424 switching message colors to entire line, switchover, AR_II:464 symptoms, analyzing, AR_I:334 synchronizing commands with VPO agent character set,
AR_I:240 CG:196 CG:443CG:444

VPO and NNM event correlation, CG:407

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

539

Master Index
syntax EMS Resources application, AR_II:111 files tracing, AR_I:333 opclic command, AR_I:464 pattern-matching, CG:318CG:320 templates flexible management, AR_I:124AR_I:129 management responsibility switching,
AR_I:126

Solaris, AR_II:305 Tru64 UNIXT, AR_II:344 Windows NT/2000, AR_II:428 system security exception warnings, AR_I:291 overview, AR_I:402AR_I:403 System Summary application, AR_II:199 T <$T> variable, AR_I:166 tables and tablespaces non-VPO, AR_I:492 VPO, AR_I:487 tabs, adding to browser pane, CG:195 Tail Status Files application, AR_II:224 tailored set of applications, CG:190 tailored_applications_start option, takeover definition, AR_II:464 target directories See also directories; temporary directories AIX, AR_II:65 HP-UX, AR_II:97 Linux, AR_II:132 MPE/iX, AR_II:162 Novell NetWare, AR_II:201 SGI IRIX, AR_II:256 SINIX RM/Reliant, AR_II:275 Solaris, AR_II:303 Tru64 UNIX, AR_II:341 Windows NT/2000, AR_II:425 target rules, messages, CG:441 tasks VPO, CG:50CG:60 TCP/IP Status application, AR_II:419 Technical Workstations, AR_II:98 techniques, C2 security, CG:206 template administrators See also operators; templates; users; VPO administrator description, CG:64 template conditions, CG:52 See also templates Template Detail Report, AR_I:112 template groups See also templates advantages, CG:288 creating, CG:289
AR_I:277

message operations and target rules,

AR_I:127

responsible manager configuration,

AR_I:125

scheduled outages, AR_I:128, AR_I:130 service hours, AR_I:128, AR_I:130 time, 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:62 HP-UX, AR_II:94 Linux, AR_II:129 Sequent DYNIX, AR_II:238 SGI IRIX, AR_II:254 SINIX RM/Reliant, AR_II:273 Solaris, AR_II:301 Tru64 UNIX, AR_II:339 SYSSTART.PUB.SYS parameters, AR_II:147 System Administrator. See SAM System Log (MetaFrame) template, System Log (Terminal Server) template,
AR_II:382, AR_II:434 AR_II:434

system resource files AIX, AR_II:67 HP-UX, AR_II:101 MPE/iX, AR_II:164 Novell NetWare, AR_II:203 Sequent DYNIX, AR_II:243 SGI IRIX, AR_II:259 SINIX RM/Reliant, AR_II:278

540

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
hierarchies creating, CG:289 navigating, CG:289 organizing, CG:288CG:289 preconfigured AIX, AR_II:59 HP-UX (OVPA), AR_II:224AR_II:226 HP-UX (VPO), AR_II:90 Linux, AR_II:128 MPE/iX, AR_II:150 Novell NetWare, AR_II:187 Sequent DYNIX, AR_II:237 SGI IRIX, AR_II:253 SINIX RM/Reliant, AR_II:272 Solaris (OVPA), AR_II:224AR_II:226 Solaris (VPO), AR_II:296 Tru64 UNIX, AR_II:337 Windows NT/2000, AR_II:380 Sun Enterprise E10000, AR_II:311 templates See also template administrators; template conditions; template groups adding new combination of nodes and templates,
CG:292

message forwarding between management servers, responsibility switch, AR_I:144AR_I:145 scheduled outages, AR_I:152 service hours, AR_I:151 syntax, AR_I:124AR_I:129 types, AR_I:117 generic, CG:306 importing VPO templates into OpenView Operations for Windows, AR_I:209 logfile, CG:362 AIX, AR_II:59AR_II:60 Citrix MetaFrame, AR_II:434 HP-UX (VPO), AR_II:91 Linux, AR_II:128 MPE/iX, AR_II:150 Novell NetWare, AR_II:187 Sequent DYNIX, AR_II:237 SGI IRIX, AR_II:253 SINIX RM/Reliant, AR_II:272 Solaris (VPO), AR_II:297 Sun Enterprise E10000, AR_II:313 Tru64 UNIX, AR_II:337AR_II:338 variables, AR_I:160 Windows NT/2000, AR_II:381AR_II:382 management responsibility switching,
AR_I:126 AR_I:149AR_I:150

SNMP traps, CG:394 assigning, CG:291CG:293 configuring application-specific, CG:306 multiple, CG:303 creating for message sources, CG:287 distributing assigned, CG:293 description, CG:283 message source, CG:285CG:294 EMS configuring, AR_II:112 downloading, AR_II:112 event correlation example, CG:411CG:414 flexible management configuring, AR_I:117AR_I:152 examples, AR_I:144AR_I:152 follow-the-sun responsibility switch, keywords, AR_I:119AR_I:124 location, AR_I:117
AR_I:146AR_I:148

message HP-UX (VPO), AR_II:90 Solaris (VPO), AR_II:296 Windows NT/2000 (VPO), AR_II:385 message forwarding, CG:452CG:453 attributes, AR_I:137 configuring, AR_I:137 location, AR_I:136 parameters, AR_I:138 troubleshooting, CG:459 message operations syntax, AR_I:127 message source variables, message target rule syntax, AR_I:127 MPE/ix console messages default attributes, CG:400 defining, CG:399 multiple, CG:304CG:305
AR_I:154AR_I:167

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

541

Master Index
protecting distribution, AR_I:423 responsible manager, CG:440 scheduled outage syntax, scheduling, AR_I:130AR_I:135 service hours location, AR_I:130 parameters, AR_I:131 syntax, AR_I:128, AR_I:130 SNMP trap variables, AR_I:163AR_I:166 SSP, reconfiguring, AR_II:318, AR_II:320 Switch User, CG:414 threshold monitor EMS, AR_II:106 variables, AR_I:161 time, CG:442 examples, AR_I:139AR_I:141 keywords, AR_I:142AR_I:143 overview, AR_I:139AR_I:143 syntax, AR_I:126 time-indifferent, CG:442 Transient Interface Down, CG:413 Transient Node Down, CG:412 Templates Groups list box, CG:288 Templates Overview Report, AR_I:112 Templates Summary Report, AR_I:112 temporary directories See also directories; target directories AIX, AR_II:65 HP-UX, AR_II:97 Linux, AR_II:132 MPE/iX, AR_II:162 Novell NetWare, AR_II:201 Sequent DYNIX, AR_II:240 SGI IRIX, AR_II:256 SINIX RM/Reliant, AR_II:275 Solaris, AR_II:303 Tru64 UNIX, AR_II:341 Windows 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:380 text, reviewing original message, CG:137 <$THRESHOLD> variable, AR_I:161 threshold monitors
AR_I:128AR_I:130

conditions advanced monitoring, CG:385CG:386 examples, CG:389 multiple, CG:387CG:388 configuring, CG:384 default, CG:385 integrating, CG:382CG:385 messages, CG:369CG:389 templates EMS, AR_II:106 variables, AR_I:161 thresholds maximum, CG:377 minimum, CG:377 ticket, RPC server, AR_I:410 time attributes, CG:425 configuring time-indifferent templates,
CG:442

setting intervals, CG:442 templates description, CG:442 examples, AR_I:139AR_I:141 keywords, AR_I:142AR_I:143 overview, AR_I:139AR_I:143 syntax, AR_I:126 zone, AR_I:134 time-based suppression, CG:351 Time message attribute, AR_I:77 timeouts, configuring for report generation, Tips_for_Installing_Agents, AR_II:122 title_suffix option ito_op, AR_I:272 itooprc, AR_I:277 To De-install an Agent Manually, AR_II:127 toolbar figure, CG:109 overview, CG:109 tools backup, AR_I:438 controller, AR_I:284AR_I:285 license maintenance, AR_I:464AR_I:465 node mapping, AR_I:285AR_I:286 recovery, AR_I:438 tour, Java GUI, CG:71CG:72 trace (ASCII) file, AR_I:308 trace file, AR_I:303
AR_I:110

542

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
trace option ito_op, AR_I:272 itooprc, AR_I:277 tracing activiating, AR_I:328AR_I:330 commands, AR_I:67 de-activiating, AR_I:330 events, AR_I:67 examples, AR_I:331AR_I:332 file location, AR_I:332 syntax, AR_I:333 functional areas, AR_I:327 problems, AR_I:326AR_I:333 Transient Interface Down template, CG:413 Transient Node Down template, CG:412 traps SNMP, CG:390CG:397 well-defined, AR_II:92 trend-analysis reports, AR_I:115 Trend Parameters* application, AR_II:199 trouble ticket system connecting management servers, CG:456 forwarding messages, AR_I:132 troubleshooting AIX managed nodes, AR_II:53 database, AR_I:340AR_I:342 embedded performance component,
AR_I:382AR_I:385 IP aliases, AR_II:53

installation, AR_I:348 runtime, AR_I:370AR_I:373 Tru64 UNIX managed nodes DCE configuring, AR_II:330AR_II:331 removing, AR_II:331 OVPA, AR_II:211 VPO default operator, AR_II:343 directory structure, AR_II:342 file locations, AR_II:342 hardware requirements, AR_II:325 include file, AR_II:346 installation requirements, installation tips, AR_II:328AR_II:329 libraries, AR_II:345AR_II:347 logfile templates, AR_II:337AR_II:338 makefile, AR_II:347 monitored objects, AR_II:339 organization, AR_II:342AR_II:344 overview, AR_II:323AR_II:347 preconfigured elements, scripts and programs,
AR_II:338 AR_II:337AR_II:339 AR_II:340AR_II:341 AR_II:325AR_II:327

SNMP event interceptor (not supported), software requirements,

AR_II:326AR_II:327

managed node runtime, AR_I:355AR_I:369 management server GUI, AR_I:345AR_I:347 message forwarding template, CG:459 VPO, AR_I:343AR_I:344 MC/ServiceGuard, AR_II:459 MPE/iX managed nodes installation, AR_I:350AR_I:354 runtime, AR_I:374AR_I:380 multi-homed host installation, NSF, AR_I:397 overview, AR_I:323AR_I:339 PRC daemons or local location brokers,
AR_I:381 AR_I:388AR_I:396

system resource files, AR_II:344 template groups, AR_II:337 Tru64 UNIX template group, AR_II:337 trusted 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:303 tuning performance, AR_I:318AR_I:322 Types of Default Applications, AR_II:62 U U message attribute, AR_I:75 Ultra. See Sun Ultra

Sun Clusters, AR_II:469AR_II:471 UNIX managed nodes

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

543

Master Index
unbuffering messages automatically, CG:415 manually, CG:415CG:416 unbuffering pending messages, CG:104 UNIX distribution tips, AR_I:192 improving performance, AR_I:290 kernel parameters, AR_I:40 managed nodes assigning passwords, AR_I:422 troubleshooting installation, AR_I:348 runtime, AR_I:370AR_I:373 ? Unknown message severity level, AR_I:74 unmatched conditions, suppressing, CG:333 messages, classifying, CG:55 unmattched messages, forwarding, AR_I:337 Unmonitored Report, AR_I:112 updating current workspace, CG:92CG:94 updating VPO on managed nodes agents, AR_I:49AR_I:56 configuration, AR_I:185AR_I:192 uploading configuration files, CG:446 URL Shortcuts folder figures object tree, CG:84 starting application, CG:93 updating application, CG:94 overview, CG:84 Used Shares application, AR_II:420 User Action Report, AR_I:112 User Audit Report, AR_I:112 User Logon Report, AR_I:113 user option ito_op, AR_I:272 itooprc, AR_I:277 User Profile Overview Report, AR_I:113 User Profile Report, AR_I:113 <$USER> variable, AR_I:167 users See also operators; template administrators; VPO administrator changing names, AR_I:415 passwords, AR_I:415 concept, CG:61CG:67 controlling passwords, AR_I:415 logged into Java GUI, AR_I:291 profiles, CG:62 roles, CG:61 root, AR_I:419 switching 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:161 VantagePoint Navigator man pages, AR_I:502 variables See also parameters action, AR_I:158AR_I:159 adding VPO, CG:162 applications, AR_I:169AR_I:183 environmental, AR_I:154 GUI, AR_I:169AR_I:183 language, AR_I:234 instruction text interface, AR_I:168 message source templates,
AR_I:154AR_I:167

messages MPE/iX console, AR_I:162 scheduled actions, AR_I:167 monitoring, CG:377 overview, AR_I:153AR_I:183 status, AR_I:132 templates logfile, AR_I:160 SNMP trap, AR_I:163AR_I:166 threshold monitor, AR_I:161 types, AR_I:153 verifying automatic actions, CG:156CG:157 operator-initiated actions, CG:157CG:158 RPC server ticket, AR_I:410 suppress types, CG:348CG:350 versions programs, AR_I:188 scripts, AR_I:188 VPO, AR_I:324AR_I:325 VPO agent displaying available, AR_I:65

544

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
displaying installed, AR_I:65 managing, AR_I:64 removing, AR_I:66 viewing EMS GUI resource instances, AR_II:109 message severity in Message Dashboard overview, CG:142CG:146 messages in message browser, CG:122 OVPA documentation, AR_II:227 Virtual Terminal application, AR_II:160, Virtual Terminal PC application, AR_II:421 Volume application, AR_II:199 VP Navigator finding impacted services, CG:147 VPO See also VPO agents; VPO-SE applications, CG:216 benefits, CG:39 character code conversion,
AR_I:250AR_I:256 communication, AR_I:295AR_I:296 AR_II:162

functionality, CG:45CG:49 importing OpenView Operations for Windows policies, AR_I:210 improving performance, AR_I:320AR_I:321 installing configuration on managed nodes,
AR_I:185AR_I:192

integrating applications actions, AR_I:223AR_I:224 Application Desktop, AR_I:214AR_I:215 broadcast commands, AR_I:222 components, AR_I:213 HP applications, AR_I:213 HP OpenView plug-in, AR_I:214 monitoring applications, AR_I:225 NNM, AR_I:215, AR_I:216AR_I:221 overview, AR_I:211AR_I:230 VPO applications, AR_I:214 integrating SMS, AR_II:440AR_II:441 interoperability OpenView Operations for Windows, overview, AR_I:193AR_I:210 language support, AR_I:231AR_I:263 maintaining, CG:199CG:280, man pages, AR_I:498 mapping file problems, AR_II:166 MC/ServiceGuard, AR_II:456AR_II:458 MC/ServiceGuard support, AR_II:113 message interface, CG:367CG:368 monitoring, CG:120 other languages, AR_I:260AR_I:262 overview, CG:37CG:67 process groups, AR_I:412 names, AR_I:412 processes, AR_I:293AR_I:314 security auditing, AR_I:428AR_I:431 levels, AR_I:413 methods, CG:206 operations, AR_I:415AR_I:427 overview, AR_I:399AR_I:431 VPO processes, AR_I:412AR_I:413 sending messages to management server,
AR_I:200 AR_I:433AR_I:480 AR_I:195AR_I:210

concepts client-server, CG:40CG:41 user, CG:61CG:67 configuring overview, CG:199CG:280, RPC authentication, AR_I:411 to accept messages forwarded from OpenView Operations for Windows, database tables and tablespaces, AR_I:487 defaults administrator, CG:177 system, CG:174 description, CG:39CG:44 Distributed Event Interception, AR_II:92 configuring, AR_II:93 description, AR_II:92 event interceptor, CG:407 exporting templates to OpenView Operations for Windows, AR_I:209 features, CG:23 filtering internal error messages, CG:402,
AR_I:339 AR_I:205AR_I:207 AR_I:69AR_I:183

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

545

Master Index
Spanish language, AR_I:259 starting from operator GUI, CG:202 Sun Enterprise Cluster support, AR_II:322 Sun Management Center integration,
AR_II:321

AR_I:185AR_I:192 variables, CG:162 versions, AR_I:324AR_I:325 VPO Add Node window, CG:224CG:227

tasks, CG:50CG:60 troubleshooting, AR_I:323AR_I:339 server, AR_I:343AR_I:344 tuning performance, AR_I:318AR_I:322 updating configuration on managed nodes,

Sequent DYNIX, AR_II:236 SGI IRIX, AR_II:252 SINIX RM/Reliant, AR_II:271 Solaris, AR_II:294 Tru64 UNIX, AR_II:336 Windows NT/2000, AR_II:379 distributing configuration to managed nodes, AR_I:187 enabling operators to control, HACMP, AR_II:50 installation managed nodes, AR_I:37AR_I:56 reasons not to install, CG:218 requirements, AR_I:39AR_I:41 script, AR_I:49 tips, AR_I:42AR_I:48 installing on managed nodes AIX, AR_II:45AR_II:57 HP-UX, AR_II:77AR_II:85 Linux, AR_II:123AR_II:126 MPE/iX, AR_II:149 Novell NetWare, AR_II:181AR_II:186 Sequent DYNIX, AR_II:236 SGI IRIX, AR_II:252 SINIX RM/Reliant, AR_II:270 Solaris, AR_II:290AR_II:291 Sun Enterprise E10000, Tru64 UNIX, AR_II:332 Windows NT/2000, AR_II:355AR_II:378 managing, AR_I:64AR_I:66 monitoring IP devices, CG:462 objects, CG:371CG:376 reconfiguring on regional management servers, CG:437 removing from managed nodes AIX, AR_II:58 Linux, AR_II:127 Novell NetWare, AR_II:186 SGI IRIX, AR_II:252 SINIX RM/Reliant, AR_II:271 Solaris, AR_II:295 SSH installation method, AR_I:57AR_I:61 Sun Clusters, AR_II:468
AR_II:318AR_II:320 AR_I:220AR_I:221

VPO administrator See also administrative rights; operators; template administrators; users changing responsibility matrix, CG:204 description, CG:62CG:63 environment, CG:201CG:204 GUI access, AR_I:417 description, CG:202 message browser, CG:203CG:204 reports customized, AR_I:113 preconfigured, AR_I:111 responsibility matrix, CG:204 saving, AR_I:417 VPO agents See also VPO activating on Solaris managed nodes command line, AR_II:292 GUI, AR_II:293 configuration files location, AR_I:311 types, AR_I:310 configuring OpenView Operations for Windows management server,
AR_I:196AR_I:199

de-installing from managed nodes AIX, AR_II:58 automatically, AR_I:62AR_I:63 HP-UX, AR_II:89 Linux, AR_II:127 manually, AR_I:63 MPE/iX, AR_II:149

546

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

Master Index
switching user, AR_I:424 synchronizing commands with character set, AR_I:240 updating on managed nodes,
AR_I:49AR_I:56

VPO Node Hierarchy Bank,

CG:212CG:216

versions description, AR_I:64 displaying available, AR_I:65 displaying installed, AR_I:65 removing, AR_I:66 with NNM collection stations, CG:463 on multiple management servers, CG:467 VPO Application Bank window EMS resource hierarchy, VPO Error Report, AR_I:113, AR_I:114 VPO Message Group Bank window, CG:232 VPO Node Bank window, CG:210CG:211 VPO Node Hierarchy Bank window, VPO Node Hierarchy window, CG:209 VPO-SE See also VPO vt3k operation, AR_II:165 W Warning message severity level, AR_I:74 web browser choosing, CG:188 figures embedded web browser, CG:107 proxy settings, CG:107 overview, CG:105CG:107 web reporting, restricting, AR_I:116 web_browser_type option, AR_I:278 well-defined traps, AR_II:92 which_browser option, AR_I:278 windows managed node Add Node for External Events, CG:217 Node Advanced Options, CG:226 Node Communication Options, CG:227 primary windows, CG:209 VPO Add Node, CG:225 VPO Add Nodes, CG:217 VPO Node Bank, CG:210CG:211
CG:212CG:216 AR_II:110AR_II:111

NetWare NetWare Config, AR_II:191 NetWare Performance, AR_II:192 NetWare Tools, AR_II:193 operator Application Desktop, CG:66 Managed Nodes, CG:66 Message Browser, CG:67 Message Groups, CG:66 template administrator Add Configuration window, CG:292 Add MPE/iX Console Messages, CG:399 Add SNMP Trap, CG:394 Condition No., CG:386 Define Configuration, CG:291 Message and Suppress Conditions, CG:314 Message Condition Advanced Options,
CG:394

Message Correlation, CG:337 Message Source Template, CG:287 Message Source Templates, CG:294 Modify VPO Interface Messages, CG:368 Regroup Conditions, CG:359 VPO administrator Configure Management Server, AR_I:191 Download Configuration Data,
AR_I:435AR_I:437

Install/Update VPO Software and Configuration, AR_I:51, AR_I:187 Message Group Bank, AR_I:72 Node Group Bank, AR_I:71 Windows 2000 template group, AR_II:380 Windows Installation Server requirements, Windows managed nodes requirements,
AR_II:352 AR_II:352

Windows NT template group Windows NT/2000, AR_II:380 Windows NT/2000 managed nodes agent accounts, AR_II:358AR_II:360 alternative accounts, AR_II:359AR_II:360 applications, AR_II:392AR_II:423 assigning passwords, AR_I:423 Citrix MetaFrame applications, AR_II:435AR_II:438

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide

547

Master Index
integration, AR_II:430AR_II:434 default operator, AR_II:427 de-installing agents, AR_II:379 directory structure, AR_II:426 file locations, AR_II:427 FTP installing agents, AR_II:361AR_II:366 re-installing agents, AR_II:372AR_II:375 hardware requirements, HP ITO Account, AR_II:358 include file, AR_II:429 installation methods, AR_II:357 requirements, AR_II:351AR_II:354 installing agents, AR_II:355AR_II:378 libraries, AR_II:429 logfile locations, AR_I:460 logfile templates, AR_II:381AR_II:382 makefile, AR_II:429 management server requirements,
AR_II:351 AR_II:351AR_II:352

figures graphs and charts, CG:87 main window, CG:85 message browser, CG:97 moving (after), CG:184 moving (before), CG:183 popup menu on pane, CG:115 popup menu on tab, CG:114 finding impacted VP Navigator services,
CG:147

monitored objects, AR_II:388 node requirements, AR_II:352 organization, AR_II:426AR_II:428 overview, AR_II:349AR_II:444 preconfigured elements, pre-installing agents, AR_II:376AR_II:378 re-installing agents, AR_II:372AR_II:375 scripts and programs, AR_II:424AR_II:425 SMS integration, AR_II:439AR_II:444 SNMP event interceptor, software requirements,
AR_II:385AR_II:387 AR_II:353AR_II:354 AR_II:380AR_II:391

investigating problems, CG:141 moving, CG:183 overview, CG:85CG:87 popup menus, CG:114 workspaces Corrective Actions, CG:90 Diagnostic Dashboard, CG:89 Message Dashboard, CG:88 Online Help, CG:91 Services, CG:88 updating current, CG:92CG:94 Workspace Properties dialog box figure, CG:106 Workst Stats application, AR_II:423 worldwide management. See follow-the-sun control worldwide management domain, CG:424 writing to default working directory,
AR_I:416

system resources, AR_II:428 template groups, AR_II:380 VPO message templates, AR_II:385 Windows Installation Server requirements,
AR_II:352

X X resources fonts, AR_I:236AR_I:238 <$X> variable, AR_I:166 <$x> variable, AR_I:166 XCONSOLE application, AR_II:199 X-OVw group applications, AR_I:281 Z zone, time parameter, AR_I:135 string, AR_I:134

WMI policy, changing default name, AR_I:208 Working VPO Operators Report, AR_I:113 workspace pane accessing OpenView applications, CG:147 evaluating action results, CG:155

548

AR_I AR_II CG

VPO Administrators Reference Volume I VPO Administrators Reference Volume II VPO Concepts Guide