PATROL for Veritas Cluster Server by OTL Software User Guide · vi PATROL for Veritas Cluster...

PATROL® forVeritas Cluster Server™

by OTL Software

User GuideVersion 2.2

Document Revision 3April 15, 2011

Copyright © 2011 OTL Software Limited, as an unpublished work. All rights reserved.

BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. Veritas Cluster Server is a registered trademark of Symantec Corporation. All other third party logos and product/trade names are registered trademarks or trademarks of their respective companies.

THE USE AND CONTENTS OF THIS DOCUMENTATION ARE GOVERNED BY THE SOFTWARE LICENSE AGREEMENT.

The license agreement can be found in the product licensing menu as described in “Licensing the KM” on page 8 or by contacting OTL Software Limited.

Restricted Rights LegendUse, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in FAR Section 52.227-14 Alt. III (g)(3), FAR Section 52.227-19, DFARS 252.227-7014 (b), or DFARS 227.7202, as amended from time to time. Send any contract notices to OTL Software Limited.

Contacting OTL SoftwarePostal Address

OTL Software LimitedP O Box 68300NewtonAuckland 1145New Zealand

Telephone +64 9 373 9920 Web Site Address http://www.otl.co.nz

Fax +64 9 303 9129 E-mail (Sales) [email protected]

Help Desk +64 9 303 9120 E-mail (Help Desk) [email protected]

http://www.otl.co.nz

Customer SupportYou can obtain technical support by using the Support page on the OTL Software web site or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, please see “Before Contacting OTL Software,” below.

Support Web SiteYou can obtain technical support from OTL Software 24 hours a day, seven days a week by accessing the technical support web site at http://www.otl.co.nz/support. From this site, you can:

• read overview about support services and programs that OTL Software offers• log a support call online• check OTL Software contact information, including e-mail addresses, fax numbers, and telephone numbers

Click here to ensure you have the latest version of the OTL Software KMs.

Support via Telephone or E-mailIf you need technical support, you can contact OTL Software by calling +64 9 373 9120 or by faxing +64 9 303 9129. You can also contact the OTL Software Helpdesk via e-mail at [email protected]. For other contact methods, please refer to the OTL Software Web site at http://www.otl.co.nz/support.

Before Contacting OTL SoftwareBefore you contact OTL Software, please have the following information available so that a technical support analyst can begin working on your problem immediately:

• KM product information:— product name— product version— license serial number

• monitored application information:— Veritas Cluster Server version

• operating system information:— machine type— operating system type, version, and service pack or patch details— system hardware configuration

• PATROL information:— PATROL Agent version— PATROL Console version and platform details— BMC ProactiveNet Performance Management Portal version and platform details

• sequence of events leading to the problem

• commands and options needed to reproduce the problem

• messages received:— product error messages— messages from monitored application— messages in PATROL Console system output window (SOW)

PATROL for Veritas Cluster Server by OTL Software - User Guide iii

http://www.otl.co.nz/support?utm_source=km-vcs&utm_medium=ug

http://www.otl.co.nz/km/latest_versions.asp?utm_source=km-vcs&utm_medium=ug


iv PATROL for Veritas Cluster Server by OTL Software - User Guide

Contents

Contents

Chapter 1 Product Components and CapabilitiesOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Product Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Application Classes and Icons . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Hierarchical Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Menus, InfoBoxes and Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Accessing Menus and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . 1-11Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Printing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Impact on Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14CPU and Memory Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14Network Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Chapter 2 Preparing to InstallInstallation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Changes to Veritas Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . 2-4Changes to BMC PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Additional Software Requirements . . . . . . . . . . . . . . . . . . . . . . . 2-6

Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12License Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

OTL Software Ltd., Confidential and Proprietary Information

Contents v

Chapter 3 InstallationInstallation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2Installation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4

Installing the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5Uninstalling the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10

Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-15

Chapter 4 Loading and ConfiguringLoading the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2

Preparing to Load the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2Loading the KM on PATROL Console . . . . . . . . . . . . . . . . . . . .4-2Loading the KM on PATROL Central . . . . . . . . . . . . . . . . . . . . .4-4Loading the KM on BPPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-6

Configuring the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7Licensing the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-8Configuring the KM User Account . . . . . . . . . . . . . . . . . . . . . . .4-10Verifying Application Discovery . . . . . . . . . . . . . . . . . . . . . . . . .4-11Checking the Instance Limits . . . . . . . . . . . . . . . . . . . . . . . . . . .4-13Checking the Initial Setup of the KM . . . . . . . . . . . . . . . . . . . . .4-14Configuring PATROL Agent to Preload the KM . . . . . . . . . . . .4-16Restarting PATROL Agent and PATROL Console . . . . . . . . . . .4-16

Unloading the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17Unloading the KM from the PATROL Agent . . . . . . . . . . . . . . .4-17Unloading the KM from PATROL Console . . . . . . . . . . . . . . . .4-18Unloading the KM from PATROL Central Console . . . . . . . . . .4-19

Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-19

Chapter 5 Working with the KMOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2Customizing the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3

Managed Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8Daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-16GAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-28LLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-32Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-36Service Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-42Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-50


vi PATROL for Veritas Cluster Server by OTL Software - User Guide

Operating the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60Debugging the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61Working with Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67

Refreshing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67Displaying Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68Customizing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69

Upgrading the Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70

Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70KM Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70


Appendix A KM Commands (Menus)Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Menu Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Appendix B InfoBoxesOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2InfoBox Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3

Appendix C Parameter Definitions and DefaultsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1Parameter Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-2

Column Heading Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . .C-2Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-3Parameter Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-4

Appendix D TroubleshootingTroubleshooting Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Glossary

Index


Contents vii


viii PATROL for Veritas Cluster Server by OTL Software - User Guide

Figures

Figures

Figure 1-1 Application Class Hierarchy of VCS KM . . . . . . . . . . . . . . . . . 1-9Figure 3-1 Installation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Figure 4-1 VCS KM Setup Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Figure 4-2 VCS KM Setup Instance on PATROL Central Console . . . . . . . 4-5Figure 4-3 VCS KM Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Figure 4-4 License Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8Figure 4-5 Remote Authentication Configuration dialog . . . . . . . . . . . . . . . 4-9Figure 4-6 Login Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Figure 4-7 VCS KM Console View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12Figure 4-8 VCS KM Default Instance Limits . . . . . . . . . . . . . . . . . . . . . . . . 4-13Figure 4-9 VCS KM Preloading dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16Figure 5-1 Monitoring Mode Configuration dialog . . . . . . . . . . . . . . . . . . . 5-4Figure 5-2 Remote PATROL Agent Configuration dialog . . . . . . . . . . . . . . 5-5Figure 5-3 Node Status Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . 5-7Figure 5-4 Agent Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Figure 5-5 Agent Status Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . 5-10Figure 5-6 Daemon Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12Figure 5-7 Daemon Status Configuration dialog . . . . . . . . . . . . . . . . . . . . . 5-14Figure 5-8 System Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16Figure 5-9 System Status Configuration dialog . . . . . . . . . . . . . . . . . . . . . . 5-18Figure 5-10 System Frozen Status Configuration dialog . . . . . . . . . . . . . . . . 5-20Figure 5-11 System Up/Down Status Configuration dialog . . . . . . . . . . . . . . 5-22Figure 5-12 Heartbeat Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24Figure 5-13 Heartbeat Status Configuration dialog . . . . . . . . . . . . . . . . . . . . 5-26Figure 5-14 GAB Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28Figure 5-15 GAB Status Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . 5-30Figure 5-16 LLT Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32Figure 5-17 LLT Status Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . 5-34


Figures ix

Figure 5-18 Log Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-36Figure 5-19 Log Filter Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . .5-39Figure 5-20 Log Alert Acknowledgement Configuration dialog . . . . . . . . . .5-41Figure 5-21 Group Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-42Figure 5-22 Group Frozen Status Configuration dialog . . . . . . . . . . . . . . . . .5-44Figure 5-23 Group System Configuration dialog . . . . . . . . . . . . . . . . . . . . . .5-46Figure 5-24 Group System Status Configuration dialog . . . . . . . . . . . . . . . . .5-48Figure 5-25 Resource Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . .5-50Figure 5-26 Resource System Configuration dialog . . . . . . . . . . . . . . . . . . . .5-52Figure 5-27 Resource System Status Configuration dialog . . . . . . . . . . . . . .5-54Figure 5-28 Server Administration sub-menu . . . . . . . . . . . . . . . . . . . . . . . . .5-57Figure 5-29 Log Alert Acknowledgement sub-menu . . . . . . . . . . . . . . . . . . .5-58Figure 5-30 Service Group Administration sub-menu . . . . . . . . . . . . . . . . . .5-59Figure 5-31 VCS KM Debug Configuration dialog . . . . . . . . . . . . . . . . . . . .5-61


x PATROL® Knowledge Module® for Veritas Cluster Server™ by OTL Software - User Guide

Tables

Tables

Table 1-1 Application Class Icons and Functions . . . . . . . . . . . . . . . . . . . . 1-6Table 1-2 Accessing Menus and InfoBoxes for VCS KM. . . . . . . . . . . . . . 1-11Table 1-3 Accessing Online Help for VCS KM. . . . . . . . . . . . . . . . . . . . . . 1-12Table 2-1 Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Table 2-2 Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Table 2-3 Required Software for VCS KM . . . . . . . . . . . . . . . . . . . . . . . . 2-4Table 2-4 Additional Software Requirements for VCS KM . . . . . . . . . . . . 2-6Table 2-5 Executable and Library Files Accessed by VCS KM User . . . . . 2-8Table 2-6 Files Accessed by PATROL Agent User . . . . . . . . . . . . . . . . . . . 2-9Table 3-1 Contents of the Distribution File for Installation Utility . . . . . . . 3-5Table 3-2 Contents of the Distribution File . . . . . . . . . . . . . . . . . . . . . . . . 3-6Table 3-3 Unix Platform Installation Files and Extraction Paths. . . . . . . . 3-7Table 3-4 MS Windows Platform Installation Files and Extraction Paths. 3-8Table 3-5 Uninstallation from the PATROL Agent . . . . . . . . . . . . . . . . . . 3-11Table 3-6 Uninstallation from PATROL Console . . . . . . . . . . . . . . . . . . . 3-12Table 3-7 Uninstallation from the PATROL Central Console Server . . . . . 3-13Table 3-8 Uninstallation from the PATROL Central Web Server . . . . . . . . 3-14Table 5-1 VCS KM Object Debug Switch Association . . . . . . . . . . . . . . . 5-62


Tables xi


xii PATROL® Knowledge Module® for Veritas Cluster Server™ by OTL Software - User Guide

About...

About this Guide

This guide contains detailed information about the functionality of applications, commands, and parameters provided by PATROL® for Veritas Cluster Server™ by OTL Software. It also contains instructions for loading and configuration.

This guide is intended for Veritas administrators, system administrators, operators and anyone who monitors backup systems. Use this guide with the appropriate PATROL user guide for your console, which describes how to use PATROL to perform typical tasks.

NoteThis guide assumes that you are familiar with your host operating system and Veritas Cluster Server. You should know how to perform a basic set of actions in a window environment, such as choosing menu commands and dragging and dropping icons.

NoteFor simplicity throughout this guide, this Knowledge Module (KM) is often referred to as VCS KM and Veritas Cluster Server may be referred to as VCS.


About this Guide xiii

How This Guide Is OrganizedThis manual is organized as follows:

Chapter Title Purpose

1 “Product Components and Capabilities”

Provides an overview of the features and components of the KM

2 “Preparing to Install” Provides pre-installation instructions and system requirements

3 “Installation” Provides step-by-step instructions for installing, upgrading and uninstalling the KM

4 “Loading and Configuring”

Provides instructions for loading and configuring the KM

5 “Working with the KM” Describes and explains tasks performed when using the KM

Appendix A “KM Commands (Menus)”

Describes and explains all KM commands

Appendix B “InfoBoxes” Describes and explains all KM infoBoxes

Appendix C “Parameter Definitions and Defaults”

Describes and explains all KM parameters

Appendix D “Troubleshooting” Provides troubleshooting tips

Glossary “Glossary” Explains all glossary terms used in this guide

Index “Index” Lists index entries


xiv PATROL for Veritas Cluster Server by OTL Software - User Guide

Related Documentation

Online Help

You can access Online Help for PATROL for Veritas Cluster Server by OTL Software through the PATROL Console Help menu.

Release Notes

Version-specific Release Notes for PATROL for Veritas Cluster Server by OTL Software accompanies the product as a PDF document. It provides up-to-date information including:

• new features and changes included in this version• updates to the installation instructions• last-minute product information• any known issues and “workarounds” for this version

PATROL® Product Documentation

PATROL product documentation is available in both hardcopy and online publications. The PATROL Product and Documentation CD contains all PATROL manuals and guides. For a complete list, refer to the contents of the CD. Below is a list of PATROL manuals and guides related to the VCS KM.

• PATROL for Unix Getting Started• PATROL Console for Unix User Guide• PATROL for Microsoft Windows Servers Getting Started• PATROL Console for Microsoft Windows User Guide

(Volumes 1, 2 & 3)• PATROL Central Operator - Microsoft Windows Edition

Getting Started• PATROL Central Operator - Web Edition Getting Started• PATROL Console Server and RTserver Getting Started• PATROL Infrastructure Planning Guide• PATROL Installation Reference Manual• PATROL Installation Workflows


About this Guide xv

Each PATROL Console and each KM come with an extensive online help facility that is available through the PATROL Console Help menu option. The online documentation contains reference information about PATROL Console features and options and about KM parameters.

ConventionsThis guide includes special elements called notes, warnings, examples, and tips:

NoteNotes provide additional information about the current subject.

WarningWarnings alert you to situations that can cause problems, such as the loss of data, if you do not follow the instructions carefully.

ExampleAn example clarifies a concept discussed in text.

TipA tip provides useful information that may improve product performance or make procedures easier to follow.

Other conventions used in this guide are detailed below:

• File names, directories and paths appear in this boldface type.

• In instructions, this boldface type highlights commands to be entered or options to be selected.

• The name of an icon (or an instance) appears in this typeface.


xvi PATROL for Veritas Cluster Server by OTL Software - User Guide

• All syntax and operating system terms appear in

this typeface, usually on a separate line

• Text or characters to be entered by the user appear in quotes in “this typeface”. For example: Type “[default]” means that the user must also type the square brackets, but not the quotation marks.

• Third party utilities appear in this typeface, such as xpconfig.

The symbol => connects items in a menu sequence. For example, Actions => Create Test instructs you to choose the Create Test command from the Actions menu.

» This symbol denotes a one-step instruction.

In syntax, path names, or system messages, italic text represents a variable, as shown in the following examples:

The table <table_name> is not available.

The data is held in system/instance/file_name.

In syntax, the following additional conventions apply:

• A vertical bar ( | ) separating items indicates that you must choose one item. In the following example, you would choose a, b, or c:

a | b | c

• An ellipsis ( . . . ) indicates that you can repeat the preceding item or items as many times as necessary.

• Square brackets ( [ ] ) around an item indicate that the item is optional.


About this Guide xvii

The following table shows equivalent mouse buttons for Unix users and Microsoft Windows users:

NoteThis guide contains detailed procedures for using PATROL for Veritas Cluster Server by OTL Software with PATROL Console for Unix and PATROL Console for MS Windows. When instructions for the two consoles differ, this is indicated by headings such as “With the PATROL Console for Unix” or “With the PATROL Console for MS Windows”.

Unix Button

MS Windows Button Description

MB1 left mouse button Click this button on an icon or menu com-mand to select that icon or command. Click MB1 on a command button to ini-tiate action. Double-click an icon to open its container.

MB2 not applicable Click this button on an icon to display the InfoBox for the icon

Note: To simulate MB2 on a two-button mouse,

simultaneously press the two buttons (MB1 and MB3).

MB3 right mouse button Click this button on an icon to display its pop-up menu.


xviii PATROL for Veritas Cluster Server by OTL Software - User Guide

1

Product Components and Capabilities 1

This chapter provides a brief overview of PATROL® for Veritas Cluster Server™ by OTL Software. It covers the following topics:

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Product Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Application Classes and Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Hierarchical Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Menus, InfoBoxes and Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Accessing Menus and InfoBoxes. . . . . . . . . . . . . . . . . . . . . . . . . 1-11Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Printing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Impact on Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14CPU and Memory Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14Network Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15



Product Components and Capabilities 1-1

OverviewA Knowledge Module is a set of files that contain knowledge in the form of command descriptions, application, parameters, and recovery actions that PATROL® can use to monitor an application such as Veritas Cluster Server™.

The parameters in PATROL® for Veritas Cluster Server™ by OTL Software allow you to analyse Veritas Cluster Server application activity quickly and easily. It collects all data associated with Veritas Cluster Server activity over time. You can clearly identify peaks, troughs and trends in the performance of backup resources.

PATROL for Veritas Cluster Server (or VCS KM) helps you ensure that your Veritas Cluster Server installations run efficiently 24 hours a day by enabling you to detect problems, optimize systems, analyse trends, plan capacity and manage multiple hosts simultaneously.

FeaturesKey features of PATROL® for Veritas Cluster Server™ by OTL Software include:

• Centralized monitoring of all systems through the active system

• Ability to automatically failover the KM to the active system based on the KM failover service group configuration.

• Monitoring the health of the VCS and its daemons

• Monitoring LLT and GAB modules

• Monitoring status of every agent in VCS

• Monitoring log files and scanning for any alerts

• Monitoring the status of systems and heartbeat communications between systems


1-2 PATROL for Veritas Cluster Server by OTL Software - User Guide

• Monitoring groups and resources on every system and alerting to any failures

ObjectivesThe aim of the PATROL for Veritas Cluster Server is to ensure the availability, maximum performance, and integrity of your VCS systems, thereby protecting associated applications. This section summarizes how VCS KM is designed to achieve these goals within each area of the Veritas Cluster Server application.

For information on how the default configuration of the VCS KM can be customised to better suit your environment, refer to “Customizing the KM” on page 5-3. Otherwise the KM will run as a standard installation as described below.

NoteThe VCS KM defines certain parameters to trigger alerts in suspicious or critical circumstances, while others simply gather information for display. Any of the display parameters with a graphical output may also be configured to trigger alerts. Information on modifying parameters can be found in PATROL documentation. Also refer to “Appendix C: Parameter Definitions and Defaults”.

Monitoring Servers

PATROL for Veritas Cluster Server monitors all servers in the cluster. The following items are checked regularly and alerts are triggered in suspicious or critical circumstances:

• the working status of the server• KM login and licensing details for the server

Other server information is available through the infobox.



Monitoring Agents

PATROL for Veritas Cluster Server monitors all VCS agents. The working status of the agent is checked regularly and an alert is triggered in suspicious or critical circumstances. Number faults is gathered for each agent and can be monitored to trigger alerts if required. Other agent information is available through the infobox.

Monitoring Systems and Heartbeats

PATROL for Veritas Cluster Server monitors all remote systems configured on the server and their heartbeat communications. VCS uses both Low Latency Transport (LLT) protocol for network based communication and Group Membership Services/Atomic Broadcast (GAB) protocol for membership heartbeats via LLTs and point-to-point unicast communication between member nodes. The following items are checked regularly and alerts are triggered in suspicious or critical circumstances:

• working status of each system and heartbeats from that system• each LLT interface and GAB membership status• LLT and GAB module status• system CPU resource usage

Other system and heartbeat information is available through the infobox and display parameters.

Monitoring Daemons

PATROL for Veritas Cluster Server monitors the critical VCS server daemons. The working status of the daemon is checked regularly and an alert is triggered in suspicious or critical circumstances. CPU and memory usage data is gathered and may be monitored to trigger alerts if required. Other daemon information is available through the infobox.



Monitoring Log Files

PATROL for Veritas Cluster Server monitors all critical Veritas Cluster Server log files. The following items are checked regularly and alerts are triggered in suspicious or critical circumstances:

• errors in the monitored log files• space utilization of any monitored log file and its file system

Details of logged messages are available in text parameters, and other log information is available through infoboxes and/or display parameters.

Monitoring Resources and Resource Systems

PATROL for Veritas Cluster Server monitors all resources and their resource systems. The working status of each resource on its resource system is checked regularly and an alert is triggered in suspicious or critical circumstances. Other data is available in infoboxes and/or display or text parameters, including:

• details of the resources and their resource systems• number of resource systems in different states

Monitoring Groups and Group Systems

PATROL for Veritas Cluster Server monitors all groups and their group systems. The working status of each group on its group system is checked regularly and an alert is triggered in suspicious or critical circumstances. Other data is available in infoboxes and/or display or text parameters, including:

• details of the groups and their group systems• number of group systems in different states



Product Architecture

Application Classes and Icons

Table 1-1 shows the icon and label for each application class, and a brief description of its function including their parent/child application classes and object/component names.

NoteAll application classes with their names ending _CONTAINER are created as parent instances to contain all child component instances. These container instances are instantiated only when there is a child instance to be created.

Table 1-1 Application Class Icons and Functions

Icon Application Class Instance Label FunctionVCS_SERVER Veritas Cluster Server

Note: If the instance is labelled VCS_SETUP, the KM is awaiting KM License details and / or Login Details

Serves as a container representing the entire Veritas Cluster Server application.

Displays information on the server.

Parent of: VCS_AGENT_CONTAINER, VCS_DAEMON_CONTAINER, VCS_GAB_CONTAINER, VCS_GROUP_CONTAINER, VCS_LLT_CONTAINER, VCS_LOG_CONTAINER, VCS_RESOURCE_CONTAINER, VCS_SLAVE_CONTAINER

Object: ServerComponent: Server

VCS_AGENT_CONTAINER

VCS_AGENT

Agents

<Agent Name>

Displays Veritas Cluster Server agent information.

Child of: VCS_SERVER

Object: AgentComponent: Agent

VCS_DAEMON_CONTAINER

VCS_DAEMON

Daemons

<Daemon Name>

Displays Veritas Cluster Server application daemon information.


Object: DaemonComponent: Daemon



VCS_SLAVE_CONTAINER

VCS_SLAVE

Systems

<System Name>

Displays Veritas Cluster Server System information.


Parent of: VCS_HEARTBEAT

Object: SlaveComponent: System

VCS_HEARTBEAT <Heartbeat Name> Displays Veritas Cluster Server heartbeat information on all systems.

Child of: VCS_SLAVE

Object: SlaveComponent: System

VCS_GAB_CONTAINER

VCS_GAB

GAB

<GAB Name>

Displays Veritas Cluster Server GAB information.


Object: GABComponent: GAB

VCS_LLT_CONTAINER

VCS_LLT

LLT

<LLT Name>

Displays Veritas Cluster Server LLT information.


Object: LLTComponent: LLT

VCS_LOG_CONTAINER

VCS_LOG

Logs

<Log Name>

Displays Veritas Cluster Server log file information.


Object: LogComponent: Log

VCS_GROUP_CONTAINER

VCS_GROUP

Service Groups

<Group Name>

Displays Veritas Cluster Server service group information.


Parent of: VCS_GSYSTEM

Object: ClusterComponent: Group

VCS_GSYSTEM <Group System Name> Displays Veritas Cluster Server group system information.

Child of: VCS_GROUP

Object: ClusterComponent: Group


Icon Application Class Instance Label Function



VCS_RESOURCE_CONTAINER

VCS_RESOURCE

Resources

<Resource Name>

Displays Veritas Cluster Server resource information.


Parent of: VCS_RSYSTEM

Object: ClusterComponent: Resource

VCS_RSYSTEM <Resource System Name> Displays Veritas Cluster Server resource system information.

Child of: VCS_RESOURCE

Object: ClusterComponent: Resource


Icon Application Class Instance Label Function



Hierarchical StructurePATROL for Veritas Cluster Server is organized in groups of application classes. Figure 1-1 shows the hierarchy of VCS KM application classes described in Table 1-1.

Figure 1-1 Application Class Hierarchy of VCS KM



NoteThe top level icon for VCS KM is a single instance of the VCS_SERVER application class, labelled Veritas Cluster Server, which represents the Veritas Cluster Server running on that system. Only one installed version of Veritas Cluster Server will be monitored. Automatic discovery will initially detect the primary installation of Veritas Cluster Server on the system.

By double-clicking the Veritas Cluster Server icon, you will find the parameters that monitor the Veritas Cluster Server on that system. In addition to these parameters, there will be other container instances, which contain related application instances.

ExampleWithin the container instance labelled Service Groups, you will find one icon for each discovered service group. By double-clicking a service group instance, you will find an icon for each group system configured on that service group.

Not all components displayed in Figure 1-1 on page 1-9 are monitored from all systems under Veritas Cluster Server icon. Only the master system (in Veritas Cluster File System), which is identified by “vxdctl -c mode” command, or the active system, which has the configured failover service group ONLINE (in Veritas Cluster Server), will discover and monitor all the components. The VCS KM will perform a passive (or standby) mode monitoring on all other slave systems or on systems where the configured failover service group is OFFLINE.



Menus, InfoBoxes and HelpA Knowledge Module (KM) can be viewed using various PATROL Consoles or BMC ProactiveNet Performance Management Portal. Due to the environment in which these consoles run, each one uses different methods to display and access information in the KM. This section provides instructions on how to access the Menus and InfoBoxes, and how to access the Online Help for the KM using each of the consoles.

Accessing Menus and InfoBoxes

The Menus for VCS KM allow you to:

• configure the KM• acknowledge alerts set by the KM• manage Veritas Cluster Server application• view basic reports about the Veritas Cluster Server environment

VCS KM uses InfoBoxes to provide attributes specific to your Veritas Cluster Server environment. InfoBoxes are tables of attributes viewable through InfoBox commands. The KM uses name space variables and parameters to set InfoBoxes. They are available from the icon for each application class instance.

Table 1-2 provides information about how to access Menus and InfoBoxes in various PATROL Consoles.

Table 1-2 Accessing Menus and InfoBoxes for VCS KM

Console Type To access Menus

To accessInfoBoxes

PATROL Central ConsolePATROL Console for

MS Windows

Right-click the instance icon to display its pop-up menu and then choose KM Commands

Right-click the instance icon to display its pop-up menu and then choose InfoBox

PATROL Console for Unix Click MB3 on the instance icon. Click MB2 on the instance icon.



Accessing Online Help

Online Help provides detailed instructions about how to use VCS KM, as well as reference information about all of the application classes and parameters. Each of the PATROL Consoles uses a different method for accessing the Help. Table 1-3 provides information about how to access Help on each console.

NoteIf you are trying to access Help from a Unix console, you may want to refer to the PATROL Installation Guide for specific instructions on how to install and set up a browser in the Unix environment.

Table 1-3 Accessing Online Help for VCS KM

Console To access product help

To access application class help

To access parameter help

PATROL Central Consoles

- Right-click the instance icon to display its pop-up menu, then choose Help

Right-click the parameter icon to display its pop-up menu, then choose Help

PATROL Console for MS Windows

Select Help => Help Topics from the console menu bar, expand the book PATROL Knowledge Modules, and select Veritas Cluster Server KM for PATROL

Double-click the appli-cation class in the KM tab of the console. Then click the Help tab and Show Help in the Application Properties dialog box

Right-click the parameter icon, and choose Help On from the pop-up menu

Double-click the parame-ter icon, and click the ? icon or Help button in the parameter display window

Double-click the parame-ter in the KM tab of the console, and click the Help tab and Show Help in the Properties dialog box

PATROL Console for Unix

From the console menu bar, choose Help On => Knowledge Modules

Choose Attributes => Application Classes and double-click MB1 on the instance name. Then click Show Help in the Application Defi-nition dialog box

Click MB2 on the parame-ter icon, and click Help On



Printing Online HelpThe following tasks describe how to print online Help from a Microsoft Windows or Unix platform:

To Print Help from a Microsoft Windows Platform

NoteMicrosoft Windows-based applications contain WinHelp systems that feature a Print button in each topic window.

1. From the Contents tab of the Help system, select a topic.

2. In the topic window, click Print.

The Print dialog box for your default printer appears.

3. If desired, modify the settings.

4. Click OK.

To Print Help from a Unix Platform

NoteUnix-based applications feature browser-hosted Help (NetHelp) that does not feature a print option.

1. Navigate to the HTML file that corresponds to the set of topics that you want to print. These HTML files are located in the $PATROL_HOME directory in lib/help/vcs_km/.

2. Double-click the icon to open the file that you want to print.

3. Choose File => Print from the browser menu.



Impact on ResourcesThis section describes

• CPU and memory usage of the KM• Network traffic generated by the KM

CPU and Memory UsageCPU and memory usage will depend on the size and complexity of your environment and your VCS KM configuration. As you increase data collection frequency or add functionality through customisation, your CPU and memory usage will increase.

When monitoring a standard installation of Veritas Cluster Server using VCS KM, the PATROL Agent will consume between 5MBytes and 10MBytes of additional system memory. An enterprise installation of Veritas Cluster Server with multiple Systems, Service Groups, and Resources can consume more memory (as per other KMs used by the PATROL Agent). The memory usage of VCS KM can be reduced by:

• disable monitoring unnecessary component instances (by using the configuration menu)

• disabling unwanted components (by setting their instance limits to 0)• disabling unwanted collectors (by using the PATROL Configuration

Manager)• increasing the collector scheduling interval (by using the PATROL

Configuration Manager)• decreasing the instance limits to limit the number of instances

created by the collectors

The data collectors in VCS KM uses Veritas Cluster Server command line interface to obtain Veritas Cluster Server information. Most of the performance degradation is associated with these command executions and amount of data returned. It may improve the overall performance, if the regular housekeeping is followed on all Veritas Cluster Server systems.



Network Traffic

Under normal conditions, the VCS KM generates minimal network traffic. Most of the data is kept on the managed node. The amount of network traffic that it generates depends on the number of PATROL Consoles that are connected to the PATROL Agent and the frequency of data collection.

Where to Go from HereThe following table suggests topics that you should read next.

If you want information on... See...

System requirements for the VCS KM “Chapter 2: Preparing to Install”

How to install or upgrade the VCS KM “Chapter 3: Installation”

How to load the VCS KM and configure it for you environment

“Chapter 4: Loading and Configuring”

How to monitor Veritas Cluster Server using this KM “Chapter 5: Working with the KM”





2

Preparing to Install 2

This chapter provides pre-installation instructions for PATROL® for Veritas Cluster Server™ by OTL Software. It covers the following topics:

Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Changes to Veritas Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . 2-4Changes to BMC PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Additional Software Requirements . . . . . . . . . . . . . . . . . . . . . . . 2-6

Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Disk Space Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12License Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13


Preparing to Install 2-1

Installation ChecklistTo ensure a successful installation or upgrade of PATROL for Veritas Cluster Server, ensure that you have completed every task listed in the Installation Checklist presented in Table 2-1.

Table 2-1 Installation checklist

Completed? Requirement

Before InstallationSystem Requirements (page 2-3)• meet the operating system requirements

Software Requirements (page 2-3)• meet all Veritas Cluster Server application requirements• meet all BMC PATROL requirements

Security Requirements (page 2-7)• meet all security requirements

Disk Space Requirements (page 2-12)• meet the minimum disk space requirements

License Requirements (page 2-13)• obtain a valid KM license to run VCS KM

During InstallationUninstalling the KM (page 3-10)• uninstall any previous versions of the KM

Extracting the Distribution File (page 3-6)• create a temporary directory on your hard drive• save the VCS KM distribution file to the temporary directory

Installing the KM (page 3-5)• download installation files to PATROL Agents and PATROL Consoles• extract installation files

After InstallationLoading the KM (page 4-2)• load the VCS KM to the PATROL Console• verify the VCS KM discovery

Configuring the KM (page 4-7)• enter the VCS KM license details• enter the VCS KM login details• preload the KM on to the PATROL Agent• verify the VCS KM data collection



System RequirementsThe following table contains the list of operating systems and their versions supported by PATROL for Veritas Cluster Server by OTL Software.

NoteVersion 2.2 of VCS KM may support other versions of operating systems, but versions not listed here have not been tested by OTL Software Limited.

NoteIf the operating system is upgraded (or downgraded) at a later date, you will need to reload commands for the VCS KM. Refer to “Upgrading the Platform” on page 5-69.

Table 2-2 Supported Operating Systems

Operating System Operating System VersionOracle® SolarisTM 8, 9, 10

HP-UX 11.00, 11.11, 11iv2, 11iv3

IBM® AIXTM 5.1, 5.2, 5.3, 6.1

Red Hat® Linux® 7.2

Microsoft® Windows® 2003, 2008, 2008 R2



Software RequirementsThe following table contains a list of required software and their versions supported by PATROL for Veritas Cluster Server by OTL Software

NoteVersion 2.2 of VCS KM does not support Veritas Cluster Server versions before 4.0 and PATROL Agent versions before 3.4.

NoteVersion 2.2 of VCS KM may support other versions of Veritas Cluster Server and/or BMC PATROL, but any version not listed has not been tested by OTL Software Limited.

NoteIf the version of Veritas Cluster Server is upgraded (or downgraded) at a later date, you will need to reload commands for the VCS KM. Refer to “Upgrading the Platform” on page 5-69.

Changes to Veritas Cluster ServerThere are no changes required to the Veritas Cluster Server application in order to use PATROL for Veritas Cluster Server.

Table 2-3 Required Software for VCS KM

Software VersionVeritas Cluster Server™ 4.0 (all multi-packs)

4.1 (all multi-packs)5.0 (all multi-packs)

BMC Software PATROL Agent 3.4.20, 3.5.x, 3.6.x, 3.7.x, 3.8.x

BMC Software PATROL Console 3.4.x, 3.5.x, 7.x

BMC ProactiveNet Performance Management Portal

2.3.x, 2.4.x, 2.5.x, 2.6.x, 2.7.x, 2.8.x



Changes to BMC PATROLTo improve the performance of the VCS KM, the PATROL Agent tuning variable “/AgentSetup/AgentTuning/pslInstructionMax” should be disabled by setting it to 0 (zero) or increased to at least 5,000,000. This applies for all Veritas Cluster Server active systems and passive systems where the KM is installed. This adjustment will allow the data collectors to execute without incurring an internal scheduling delay.

This PATROL Agent tuning variable can be updated using wpconfig (on Microsoft Windows), xpconfig (on Unix) or PATROL Configuration Manager (PCM). Alternatively, you can use one of the following single line PSL command through the PATROL Console OS> prompt to update this tuning variable.

To disable:%PSL pconfig("REPLACE",

"/AgentSetup/AgentTuning/pslInstructionMax",0);

To set to at least 5,000,000:

%PSL v="/AgentSetup/AgentTuning/pslInstructionMax";if(get(v)<5000000){pconfig("REPLACE",v,5000000);}

NoteIn large Veritas Cluster Server systems, the value of 5,000,000 for the tuning variable “pslInstructionMax” may still be insufficient. In such situations, error messages will appear on the PATROL Console System Output Window (SOW) reporting that some VCS KM data collectors are in an infinite loop. In this case you can set the tuning variable to zero to disable this functionality.



The KM stores all configuration information in the PATROL Agent configuration database (pconfig), under paths /VCS and /VCS_License. PATROL Agent user (default: patrol) should be able to read and write to these pconfig variables at anytime. If Access Control List (ACL) is used to control which users are authorized to connect to a PATROL Agent, please ensure that the mode for PATROL Agent user includes “C” in the PATROL Agent variable “/AgentSetup/accessControlList”. Please refer the PATROL Agent Reference Manual for more details.

NoteYou cannot copy or distribute these KM configuration variables between managed nodes, because they may not have the same value for each managed node. For example, the KM user login details may not be the same for all managed nodes. Also some of these variables, like installation paths, are set automatically during the initial discovery.

Additional Software RequirementsThe following table contains a list of additional software requirements of PATROL for Veritas Cluster Server:

NoteThe Microsoft Windows x64 Reg.exe patch, KB948698 is required to allow access to 64-bit registry keys from PATROL Agent. Access the above patch site from the managed node to obtain the correct patch for that platform.

Table 2-4 Additional Software Requirements for VCS KM

Purpose Software VersionWhen running VCS KM with sudo user

account on Solaris, HP-UX, AIX or Linux managed nodes

Sudo (superuser do) 1.6.7 or later

When running VCS KM on Linux managed nodes

Korn shell binary (/bin/ksh) Any

When running VCS KM on Microsoft Windows x64 managed nodes

Reg.exe patch KB948698(http://support.microsoft.com/kb/948698)

Any



http://support.microsoft.com/kb/948698

Security RequirementsBy default, Veritas Cluster Server is installed and run as the root user (Unix) or administrator user (Microsoft Windows).

PATROL for Veritas Cluster Server needs to be run as a user account with administrative privileges to read and execute Veritas Cluster Server application programs and file systems. Login details of this user are configured in the VCS KM during the KM configuration. The password is stored in the PATROL Agent in a DES encrypted format.

WarningThe encrypted password can be viewed by any user who has access to the PATROL Agent configuration variables (pconfig). This user could then execute PSL statements using the encrypted password through the PATROL Console. This can be prevented by setting up an appropriate Access Control List (ACL) for users. Please refer to the PATROL Agent Reference Manual for details on how to set up an ACL.

One of the following user accounts can be used for configuring the login details of the KM:

1. root user (Unix) or administrator user (Microsoft Windows)

2. a non-root user, such as patrol, with sudo privileges on Veritas Cluster Server to execute application programs and access the file systems (Unix only)

3. a non-root (Unix) or non-administrator (Microsoft Windows) account, such as patrol, configured in Veritas Cluster Server application to administer the Veritas Cluster Server application

NoteRefer to the Veritas Cluster Server Administrator’s Guide for details on how to set up this type of account.



Access Permissions

The VCS KM user needs “read & execute” permission to executable and library files under the paths listed below. The Veritas Cluster Server installation path INSTALL_PATH, referenced in Table 2-5 and Table 2-6, is normally /opt/VRTSvcs (on Unix) or C:\Program Files\Veritas (on Microsoft Windows).

Table 2-5 Executable and Library Files Accessed by VCS KM User

The VCS KM includes some scripts which should be executable by the PATROL Agent user and the VCS KM user. These scripts are stored under KM_HOME path, normally PATROL_HOME/lib/VCS.

To list all commands used by the VCS KM, execute the following PSL code from the PATROL Console, using “PSL Task” menu, after installing and loading the KM.

i=0;foreach var (grep("^/VCS/CommandControls/",pconfig("LIST"))){ ctl=pconfig("GET", var); typ=ntharg(grep("CommandType",ctl),"2-"," ="); cmd=nthargf(grep("CommandText",ctl),"2-","=","="); if((typ == "")||(typ == "OS")) { printf("(%2d) %-25s: %s\n",i++,ntharg(var,"3","/"),cmd); }}

Paths Microsoft Windows

INSTALL_PATH/bin/ha* INSTALL_PATH\Cluster Server\bin\ha*

/sbin/llt* INSTALL_PATH\comms\llt*

/sbin/gab* INSTALL_PATH\comms\gab*

INSTALL_PATH/lib INSTALL_PATH\Cluster Server\lib

/usr/lib INSTALL_PATH\Cluster Server



The PATROL Agent user (normally patrol) needs read permission to following files:

WarningIf a monitored log file cannot be read by the PATROL Agent user, it will be copied to KM_TEMP path using the configured login account, and processed by the PATROL Agent user. On completion the copied log file will be removed. This may increase the file system usage under KM_TEMP temporarily during this activity.

On Windows platforms the Veritas Cluster Server installation is identified by checking the Microsoft Windows Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\VCS\

The configured login user should have sufficient privileges to run regedit command on the managed node.

Table 2-6 Files Accessed by PATROL Agent User

Unix Microsoft Windows

/var/VRTSvcs/log/engine_A.log INSTALL_PATH\Cluster Server\log\engine_A.txt

/var/VRTSvcs/log/hashadow-err_A.log INSTALL_PATH\Cluster Server\log\hashadow-err_A.txt

/var/adm/messages (on Solaris)

/var/adm/syslog/syslog.log (on HP-UX)

/var/log/messages (on Linux)



Sudo User for Operating System Access

If a non-root user with sudo privileges is preferred as the KM user, configure the account as a sudoer through the visudo utility using code appropriate for your platform as detailed below. This user should be able to execute VCS commands and OS commands listed in Table 2-5 on page 2-8.

The code below also applies to all non-root users who may execute VCS KM administration and report menu commands using their sudo privileges. The KM accepts any non-root user with the following sudo configuration in the sudoers file. Please replace user1, user2, user3 with appropriate KM user name. The Veritas Cluster Server installation path INSTALL_PATH, referenced below is normally /opt/VRTSvcs and PATROL_HOME is the path where the PATROL Agent is installed (including the target, like /opt/bmc/Patrol3/Solaris29-sun4/).

WarningThis non-root sudo user configured in the KM will be able to execute Veritas Cluster Server commands. To prevent unauthorized access, ensure this user is only used within the KM and not made public for general use.

WarningEntering the non-root sudo user with ‘Use Sudo’ option selected in to the login configuration dialog, before updating the sudoers file, will generate sudo errors. Also if the sudo user is configured differently, the KM may run sudo commands using incorrect sudo settings, which may expose the sudo user password.



On Solaris:

User_Alias VCSKMUSERS = user1, user2, user3Defaults:VCSKMUSERS !lecture,!authenticate,\

env_keep+="LD_LIBRARY_PATH INSTALL_PATH KM_HOME \KM_TEMP",env_reset

VCSKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\INSTALL_PATH/bin/ha*,\PATROL_HOME/lib/VCS/*,PATROL_HOME/bin/*

On HP-UX:


env_keep+="SHLIB_PATH INSTALL_PATH KM_HOME \KM_TEMP",env_reset


On AIX & Linux:


env_keep+="LIBPATH INSTALL_PATH KM_HOME \KM_TEMP",env_reset




Disk Space RequirementsPATROL for Veritas Cluster Server requires approximately:

• 1.5 MBytes disk space on each monitored PATROL Agent system• 2.6 MBytes disk space on each PATROL Console system• 600 KBytes disk space on each PATROL Central Console Server

system• 1.4 MBytes disk space on each PATROL Central Web Server system

The VCS KM is installed under the PATROL installation path.

When monitoring a standard installation of Veritas Cluster Server using VCS KM, the PATROL Agent will generate approximately 400 KBytes of history data per day. An enterprise installation of Veritas Cluster Server with multiple systems, service groups, and resources will generate more history data (as per other KMs used by the PATROL Agent). These history data files are recycled by PATROL depending on the PATROL Agent history retention period.

During execution, the VCS KM creates and maintains temporary files under KM_HOME, KM_TEMP and KM_DEBUG paths. By default they are all under PATROL_HOME/lib/VCS, where PATROL_HOME path is normally /opt/bmc/Patrol3/ (on Unix) or C:\Program Files (x86)\BMC Software\Patrol3\ (on Microsoft Windows).

If the location of the KM_TEMP or KM_DEBUG is not suitable, it can be changed using the Configuration => Paths menu from the main instance. These folder should have read, write and execute permissions for both the PATROL Agent user and the KM login user.



License RequirementsPATROL for Veritas Cluster Server is shipped with a free 30 day trial license. As soon as KM is installed and loaded to the PATROL Agent on a new managed node, the trial license will be automatically activated. The trial license gives full monitoring capability for the KM, and works only once on a managed node.

If you want to purchase a permanent license key, contact your local reseller or OTL Software Limited. To generate the license key, you will need to provide a KM Status report, which can be found under the menus of the main container instance.

If you are upgrading the VCS KM from a previous version to 2.2, a new set of license keys may be required. Please check that all required license keys are delivered with the product.




How to load the VCS KM and configure it for your environment










3

Installation 3

This chapter provides instructions for installing PATROL® for Veritas Cluster Server™ by OTL Software. It covers the following topics:

Installation Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Installation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Installing the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Uninstalling the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10



Installation 3-1

Installation WorkflowFigure 3-1 illustrates the workflow to be followed during installation of PATROL for Veritas Cluster Server on each PATROL Agent (managed node) and PATROL Console system using the VCS KM.

Figure 3-1 Installation Workflow

Copy the VCS KM Distribution file to a temporary folder,

and extract the contents

First time installation?

Extract the content of theinstallation file from the

PATROL_HOME directory

Load the VCS KM from the PATROL Console and verify the discovery

Configure VCS KM License detailsand Login details, verify the KM

data collection and preload the KM

Remove all VCS KM files installed

previously

No

Yes

Download the installation file to the PATROL_HOME path on the PATROL Agent and PATROL Console systems

Backup PATROL installation folders



Installation GuidelinesFollow these guidelines to ensure successful installation of PATROL for Veritas Cluster Server by OTL Software:

• Install the VCS KM on each Veritas Cluster Server system in the cluster, and on each PATROL Console.

• Install VCS KM under PATROL installation path - PATROL_HOME (normally C:\Program Files (x86)\BMC Software\Patrol3 on Microsoft Windows systems and /opt/bmc/Patrol3 on Unix systems).

• It is recommended that the installation file is extracted by the PATROL user on the PATROL Agent system.

NoteThe PATROL Developer Console menu command Commit KM cannot be used for installing the VCS KM to any PATROL Agent. The Commit KM command will not copy VCS KM scripts, which are operating system dependant. These scripts are stored under the KM_HOME path (PATROL_HOME/lib/VCS) on the PATROL Agent system.


Installation 3-3

ProceduresThis section provides instructions to install, upgrade or uninstall PATROL for Veritas Cluster Server on Microsoft Windows and Unix platforms.

OTL Software recommends that:

• if you are upgrading from an older version of VCS KM, backup the PATROL Agent and PATROL Console installation paths

NoteWhen upgrading from version 1.x, all previous VCS KM configuration data stored in the PATROL Agent configuration database (pconfig) will be removed.

• before deploying the VCS KM to a production environment, it should be installed, configured and tested in a test environment

• all components of the VCS KM included in the installation file should be installed

• all KM files should be loaded using the VCS_LOAD.kml file

NoteMany of the files have interdependency so a full installation eliminates errors and enables monitoring of all components.



Installing the KM

This section describes steps required to install or upgrade the PATROL for Veritas Cluster Server.

Installing the KM (Using BMC Installation Utility)

1. Check all prerequisites listed in “Chapter 2: Preparing to Install” have been met.

2. Download the latest Installation Utility from BMC EPD site and extract the contents to create bmc_products directory under a temporary directory.

3. Extract the contents of the VCS KM distribution file (vcs_km_v22xx.zip on Microsoft Windows platforms or vcs_km_v22xx.tar on Unix platforms) to the same temporary directory, created in Step 2.

4. Start the Installation Utility (setup.exe on Microsoft Windows platforms or setup.sh on Unix platforms), follow the instructions and install the required components of the KM. Table 3-1 describes the contents of the VCS KM distribution file.

Table 3-1 Contents of the Distribution File for Installation Utility

File Description

vcsagt22xxu Unix PATROL Agent installation utility files

vcsagt22xxw MS Windows PATROL Agent installation utility files

vcscon22xxu PATROL Console for Unix installation utility files

vcscon22xxw PATROL Console for MS Windows installation utility files

vcscs22xxu PATROL Central Console Server for Unix installation utility files

vcscs22xxw PATROL Central Console Server for MS Windows installation utility files

vcsws22xx PATROL Central Web Server for Unix and PATROL Central Web Server for MS Windows installation utility files

otl-vcs-solution-2.2.xx.par BMC ProactiveNet Performance Management Portal PAR file


Installation 3-5

Preparing to Install or Upgrade (Using All in One Exe/Zip File)

1. Check all prerequisites listed in “Chapter 2: Preparing to Install” have been met.

2. Extract the contents of the distribution file to a temporary folder. This distribution file can be obtained as a Microsoft Windows self-extracting file (vcs.exe) or as a zip file (vcs.zip). Zip files can be extracted using WinZip application or PKUNZIP command (Microsoft Windows platforms) or unzip command (Unix platforms). Table 3-2 describes the contents of the VCS KM distribution file.

3. Read the Release Notes, and confirm all requirement for this release have been met.

4. If you are upgrading the VCS KM, please follow the steps described under “Uninstalling the KM” on page 3-10 to uninstall the old version of the KM before attempting to install the new version.

Table 3-2 Contents of the Distribution File

File Description

vcs_ug22.pdf User Guide

vcs_rn<release_date>.pdf Release Notes

vcs_r22_agent.tar Unix PATROL Agent installation file

vcsagt22.exe MS Windows PATROL Agent installation file

vcs_r22_console.tar PATROL Console for Unix installation file

vcscon22.exe PATROL Console for MS Windows installation file

vcsconserver22.tar PATROL Central Console Server for Unix installation file

vcscs22.exe PATROL Central Console Server for MS Windows installation file

vcswebserver22.tar PATROL Central Web Server for Unix installation file

vcsws22.exe PATROL Central Web Server for MS Windows installation file

otl-vcs-solution-2.2.xx.par BMC ProactiveNet Performance Management Portal PAR file



Installing the KM on a Unix Platform

1. Copy or ftp appropriate installation files under the paths for the relevant systems as shown in Table 3-3.

2. Extract the contents of the installation .tar file as PATROL user, using:

tar xvf <file name>

3. Remove the installation .tar file copied in Step 1.

Table 3-3 Unix Platform Installation Files and Extraction Paths

File Path

vcs_r22_agent.tar $PATROL_HOME/ on monitored servers for Veritas Cluster Server for Unix

Example:/opt/bmc/Patrol3/ or

/opt/bmc/Patrol3/Solaris29-sun4/

vcs_r22_console.tar $PATROL_HOME/ on PATROL Console for Unix

Example:/opt/bmc/Patrol3/ or

/opt/bmc/Patrol3/Solaris29-sun4/

vcsconserver22.tar $PATROL_ROOT/ on PATROL Central Console Server for Unix

Example:/opt/bmc/Patrol7/

vcswebserver22.tar $BMC_ROOT/webcentral/ on PATROL Central Web Server for Unix

Example:/opt/bmc/webcentral/


Installation 3-7

Installing the KM on a Microsoft Windows Platform

1. Copy or ftp appropriate installation files to a temporary folder (such as C:\temp\) on the relevant system.

2. Double-click the file and extract the contents of the self-extracting files to relevant paths as shown in Table 3-4

3. Remove the self-extracting installation file copied in Step 1.

Table 3-4 MS Windows Platform Installation Files and Extraction Paths

File Path

vcsagt22.exe %PATROL_HOME%\ on monitored servers for Veritas Cluster Server for Microsoft Windows

Example:C:\Program Files\BMC Software\Patrol3\

vcscon22.exe %PATROL_HOME%\ on PATROL Console for MS Windows

Example:C:\Program Files\BMC Software\Patrol3\

vcscs22.exe %PATROL_ROOT%\ on PATROL Central Console Server for MS Windows

Example: C:\Program Files\BMC Software\Patrol7\

vcsws22.exe %BMC_ROOT%\WebCentral\ on PATROL Central Web Server for MS Windows

Example: C:\Program Files\BMC Software\WebCentral\



Installing or Upgrading the PAR file on BMC ProactiveNet Performance Management Portal

The PAR file enables BMC ProactiveNet Performance Management Portal to retrieve the KM data from the PATROL Agent.

1. Log on to the BMC ProactiveNet Performance Management Portal with portal credentials, and select the Portal tab.

2. Under Tasks in the navigation pane, select Performance Managers.

3. Click Upload

4. Click Browse and then select the PAR file extracted under the temporary folder on the local system. (otl-vcs-solution-2.2.xx.par) extracted under the temporary folder on the local system.

5. Click Upload.

NoteIf you are upgrading the PAR file on BMC ProactiveNet Performance Management Portal, the initial Status of the newly uploaded PAR solution on Portal is “Unpublished“. To push-out the new version to effect the upgrade process, select the checkbox next to the new version PAR solution on Portal, and click Publish.


Installation 3-9

Uninstalling the KMThis section describes steps for uninstalling the PATROL for Veritas Cluster Server. The KM is uninstalled when upgrading the VCS KM from an older version, or if the VCS KM is no longer required for monitoring the Veritas Cluster Server application. The steps required for uninstalling depend on the type of installation:

• For PATROL Agent and PATROL Console, “uninstallation” involves unloading the KM and then removing the files.

• For PATROL Central Console, the KM is uninstalled by unloading.

• For PATROL Central Console Server or PATROL Central Web Server, the KM is uninstalled by removing the files.

NoteIf the VCS KM was installed using the Installation Utility, use the same to remove the KM files after unloading.

Uninstalling the KM from the PATROL Agent

1. Unload the VCS KM by removing it from the list of preloaded KMs. If the current version of the VCS KM is 2.x, you can use the menu Configuration => Preloading from the Veritas Cluster Server instance to unload the KM. Alternatively, use the utility wpconfig (on Microsoft Windows) or xpconfig (on Unix) to remove VCS_LOAD.kml from the PATROL Agent configuration variable “/AgentSetup/preloadedKMs”.

2. Restart the PATROL Agent.

3. Remove all VCS KM files listed in Table 3-5 under the paths for PATROL Home (PATROL_HOME) and PATROL Cache (PATROL_CACHE).



NoteThere may be more than one PATROL Cache directory depending on how PATROL has been set up in your installation. Users can set up a local Cache directory to override the global setting.

4. Repeat the above steps on every PATROL Agent system where the VCS KM is installed.

Uninstalling the KM from the PATROL Console

1. Unload the VCS KM by removing all the application classes from the list of loaded application classes. All VCS KM application classes start with “VCS_”.

On PATROL Console for Unix:

A. From the PATROL Console main window choose Attributes => Application Classes...

B. Select a VCS KM application class and choose Edit => Delete.C. Repeat for all classes.D. Select File => Save Configuration to save the modified list of

loaded KMs as the PATROL Console user preference.

Table 3-5 Uninstallation from the PATROL Agent

File Types to Delete

Path relative to PATROL_HOME


PSL Library Files lib/psl/VCS_*.* lib\psl\VCS_*.*

KM & Catalog Files lib/knowledge/VCS_*.* lib\knowledge\VCS_*.*

Archive Files lib/archive/VCS_*.* lib\archive\VCS_*.*

Other Files & Folders

VCS/*VCSVCS_*.*lib/VCS/*lib/VCSlib/VCS_*.*

VCS\*.*VCSVCS_*.*lib\VCS\*.*lib\VCSlib\VCS_*.*


Installation 3-11

On PATROL Console for Microsoft Windows:

A. From the PATROL Console tree view choose the KM tab and expand the folder Application Classes.

B. Right-click on a VCS KM application class and choose Delete.C. Repeat for all classes.D. Select File => Save Configuration to save the modified list of

loaded KMs as the PATROL Console user preference.

2. Remove all VCS KM files listed in Table 3-6 under the paths for PATROL Home (PATROL_HOME) and PATROL Cache (PATROL_CACHE).

NoteThere may be more than one PATROL Cache directory depending on how PATROL has been setup in your installation. Users can set up a local Cache directory to override the global setting.

3. Repeat above steps on every PATROL Console system where the VCS KM is installed.

Table 3-6 Uninstallation from PATROL Console


Path relative to PATROL_HOME


PSL Library Files lib/psl/VCS_*.* lib\psl\VCS_*.*

KM & Catalog Files lib/knowledge/VCS_*.* lib\knowledge\VCS_*.*

Archive Files lib/archive/VCS_*.* lib\archive\VCS_*.*

Icon & Image Files lib/images/VCS_*.*lib/images/vcs_*.*

lib\images\vcs_*.*

Online Help Files & Folders

lib/help/vcs_*.*lib/help/vcs_km/*.*lib/help/vcs_kmlib/help/km_help_vcs_km

lib\help\vcs_*.*lib\help\vcs_km\*.*lib\help\vcs_kmlib\help\km_help_vcs_km



Uninstalling the KM from PATROL Central Console

1. Unload the VCS KM by removing all the application classes from the list of loaded application classes. All VCS KM application classes start with “VCS_”.

A. Right-click on the PATROL Main Map and choose Unload Knowledge Modules...

B. Select the managed systems where the VCS KM is to be unloaded, and click Next>.

C. Select all VCS KM application classes, click Next> and Finish.

2. Repeat the above steps on every PATROL Central Console where the VCS KM is installed.

Uninstalling the KM from the PATROL Central Console Server

1. Remove all VCS KM files listed in Table 3-7 under the PATROL Central Console Server installation path (PATROL_ROOT).

2. Repeat above steps on every PATROL Central Console Server system where the VCS KM is installed.

Table 3-7 Uninstallation from the PATROL Central Console Server


Path for PATROL Central Console Server


Online Help Files lib/knowledge/vcs_*/lib/help/EN_USA/vcs_km.chm

lib\knowledge\vcs_*\lib\help\EN_USA\vcs_km.chm

Icon & Image Files & Folders

lib/knowledge/vcs_*/*.*lib/knowledge/vcs_*

lib\knowledge\vcs_*\*.*lib\knowledge\vcs_*


Installation 3-13

Uninstalling the KM from the PATROL Central Web Server

1. Remove all VCS KM files listed in Table 3-8 under the PATROL Central Web Server installation path ($BMC_ROOT/webcentral on Unix and %BMC_ROOT%\WebCentral on Microsoft Windows).

2. Repeat above steps on every PATROL Central Web Server system where the VCS KM is installed.

Uninstalling the PAR File from the BMC ProactiveNet Performance Management Portal

NoteIf you are upgrading the PAR file on BMC ProactiveNet Performance Management Portal, skip the uninstallation procedures outlined below and follow the upgrade steps in “Installing or Upgrading the PAR file on BMC ProactiveNet Performance Management Portal” on page 3-9.

1. Remove all elements using the VCS KM PAR file from the BMC ProactiveNet Performance Management Portal Infrastructure.

2. Log on to the BMC ProactiveNet Performance Management Portal with portal credentials, and select the Portal tab.

3. Under Tasks in the navigation pane, select Performance Managers.

4. Check the check-box next to the VCS KM solution from the list.

5. Click Delete.

Table 3-8 Uninstallation from the PATROL Central Web Server


Path for PATROL Central Web Server


Online Help Files help_services/vcs_km*.jarkm_services/html/default/lib/help

/EN_USA/vcs_km*.jar

help_services\vcs_km*.jarkm_services\html\default\lib\help

\EN_USA\vcs_km*.jar



Deleting PATROL Agent Configuration Variables

NoteIf you are uninstalling the KM to upgrade from an older version of VCS KM, you do not have to follow the steps below. The new version of the KM will upgrade the configuration details during the initial KM discovery.

1. Remove all PATROL Agent configuration variables created by the VCS KM. These variables are stored under configuration paths VCS and VCS_License. They can be removed using wpconfig (on Microsoft Windows) or xpconfig (on Unix). Alternatively, you can use the following single line PSL command through the PATROL Console OS> prompt to remove VCS KM configuration variables. The PATROL for Veritas Cluster Server should be uninstalled on the PATROL Console before attempting the following PSL command:

%PSL foreach var(grep("^/VCS[/_]",pconfig("LIST"))){ pconfig("DELETE", var); }

2. Repeat the above step on every PATROL Agent system where the VCS KM has been loaded.







Installation 3-15



4

Loading and Configuring 4

This chapter provides instructions for loading and configuring PATROL® for Veritas Cluster Server™ by OTL Software. It covers the following topics:

Loading the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Preparing to Load the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Loading the KM on PATROL Console . . . . . . . . . . . . . . . . . . . . 4-2Loading the KM on PATROL Central . . . . . . . . . . . . . . . . . . . . . 4-4Loading the KM on BPPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Configuring the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Licensing the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8Configuring the KM User Account . . . . . . . . . . . . . . . . . . . . . . . 4-10Verifying Application Discovery . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Checking the Instance Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Checking the Initial Setup of the KM . . . . . . . . . . . . . . . . . . . . . 4-14Configuring PATROL Agent to Preload the KM. . . . . . . . . . . . . 4-16Restarting PATROL Agent and PATROL Console . . . . . . . . . . . 4-16

Unloading the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17Unloading the KM from the PATROL Agent . . . . . . . . . . . . . . . 4-17Unloading the KM from PATROL Console. . . . . . . . . . . . . . . . . 4-18Unloading the KM from PATROL Central Console . . . . . . . . . . 4-19



Loading and Configuring 4-1

Loading the KMThis section provides instructions to load PATROL for Veritas Cluster Server on Microsoft Windows and Unix platforms.

Before you load the VCS KM, you must install the KM on PATROL Console and PATROL Agent systems, following the instructions in “Chapter 3: Installation”.

Preparing to Load the KM

1. Start the PATROL Console and update the connection to all PATROL Agent systems where the VCS KM is installed.

2. Check the value of the PATROL Agent tuning variable, “/AgentSetup/AgentTuning/pslInstructionMax”, and if necessary, increase it as described in “Changes to BMC PATROL” on page 2-5.

Loading the KM on PATROL Console

1. From the PATROL Console menu bar, choose File => Load KM...

2. Select the VCS_LOAD.kml file, and click Open or OK.

The VCS KM will be loaded to the PATROL Console, and all connected PATROL Agents will start discovering the Veritas Cluster Server environment.

3. The End User License Agreement will be displayed as part of the trial license activation. Please read, accept the agreement and click Continue.

The 30 day trial license will be activated as soon as the agreement is accepted. If you are upgrading from an older version, you have to enter a new license key, as described in “Licensing the KM” on page 4-8, if required.



If the automatic discovery successfully finds the Veritas Cluster Server server installation, the VCS_SETUP instance will be instantiated, as shown in Figure 4-1.

Figure 4-1 VCS KM Setup Instance

NoteThis automatic discovery may take up to 5 minutes to instantiate the VCS_SETUP instance. Look for any error messages on the PATROL Console System Output Window (SOW) during the initial discovery.

4. Select File => Save Configuration to save the new list of loaded KM files as the PATROL Console user preference.

Follow the steps for configuring the KM, as described in “Configuring the KM” on page 4-7.

Load the VCS_LOAD.kml file on each PATROL Console.



Loading the KM on PATROL Central

1. Right click on the PATROL Main Map, and choose Load Knowledge Modules... A wizard box will display a list of all managed systems.

2. Select the managed systems where the VCS KM is to be loaded, and click Next>. The wizard will display a list of all available .kml files for the managed systems you selected.

3. Select the VCS_LOAD.kml file for each managed system, click Next> and Finish.

NoteIf you cannot find the VCS_LOAD.kml file in the wizard list for any system you selected, then the KM has not been installed on that system. Check that you have followed the instructions in “Installing the KM” on page 3-5.

The VCS KM will be loaded to the PATROL Central Console Server, and all connected selected managed systems will start discovering the Veritas Cluster Server environment.

4. The End User License Agreement will be displayed as part of the trial license activation. Please read, accept the agreement and click Continue.

The 30 day trial license will be activated as soon as the agreement is accepted. If you are upgrading from an older version, you have to enter a new license key, as described in “Licensing the KM” on page 4-8, if required.

If the automatic discovery successfully finds the Veritas Cluster Server server installation, the VCS_SETUP instance will be instantiated, as shown in Figure 4-2.



NoteThis automatic discovery may take up to 5 minutes to instantiate the VCS_SETUP instance. Look for any error messages on the PATROL Central System Output Window (SOW) during the initial discovery.

Follow the steps for configuring the KM, as described in “Configuring the KM” on page 4-7.

Load the VCS_LOAD.kml file on each PATROL Central Management Profile where VCS KM is to be loaded.

Figure 4-2 VCS KM Setup Instance on PATROL Central Console



Loading the KM on BPPM

1. Log in to BMC ProactiveNet Performance Management Portal with appropriate credentials to add infrastructure elements.

2. Click on Configure tab.

3. Under Tasks, select Elements to open the Elements page.

4. Click in Add.

5. Select Infrastructure Element, and click Next.

6. Select appropriate RSM, and click Next.

7. Enter the label for the element, select PATROL Integration, and click Next.

8. Select/create a group name, and click Next.

9. Select appropriate method to discover the PATROL Agent hosts, and click Next.

10. Fill the required details for discovering the PATROL Agents, and click Commit.



Configuring the KMThis section provides instructions to configure PATROL for Veritas Cluster Server. These instructions should be followed on all PATROL Agent systems where VCS KM is installed.

Before you can configure the KM, it must be loaded on the PATROL Console and the VCS_SETUP instance should be displayed as shown in Figure 4-1 or Figure 4-2.

NoteThis version of the VCS KM cannot be configured from BMC ProactiveNet Performance Management Portal. Use PATROL Console or PATROL Central Console to access the KM configuration menus (KM commands) described below.

Figure 4-3 VCS KM Setup Menu



Licensing the KM

Please read “License Requirements” on page 2-13 for details on obtaining VCS KM license keys.

NoteOn PATROL Agents running on Microsoft Windows platforms, the user logged on the PATROL Console should be able to execute the binaries under KM_HOME path (PATROL_HOME\lib\VCS).

1. From the VCS_SETUP instance, select the menu Configuration => License and select whether to enable or disable remote authentication.

2. If the remote authentication is disabled, a dialog for entering licensing details will be displayed, as shown in Figure 4-4. Enter the license details exactly as supplied in the respective fields and click OK. If the license information entered is valid, an acknowledgement will be displayed.

Figure 4-4 License Configuration dialog



3. If the remote authentication is enabled, a dialog for entering remote PATROL Agent details will be displayed, as shown in Figure 4-5. Enter the remote managed node details and click OK. If the remote authentication details are valid, an acknowledgement will be displayed.

Figure 4-5 Remote Authentication Configuration dialog

NoteThe remote authenication method requires a nominated system running VCS KM installed with a license file stored under the KM_HOME path. Please contact OTL Software to obtain the license file.

NoteIf the KM license details are invalid or have expired, the parameter VCSLicenseStatus will be set to alert.



Configuring the KM User Account

Please refer to “Security Requirements” on page 2-7 for details about VCS KM user account and privileges.

1. From the VCS_SETUP instance, select the menu Configuration => Login. The Login Configuration dialog will be displayed, as shown in Figure 4-6.

Figure 4-6 Login Configuration dialog

2. Enter the login details for the operating system and click OK.

If the default PATROL Agent account is used, tick the checkbox Use Agent Default Account in the above Login Configuration dialog.

NoteWhen the default PATROL Agent option is selected, the KM uses the configured PATROL Agent account details and values entered in Username and Password fields on the Login Configuration dialog are ignored. On Unix platforms, this option can also be combined either with or without Sudo option



If a sudo user account is used, tick the checkbox Use Sudo and verify the sudo binary file path by clicking on Sudo Binary File in the above Login Configuration dialog.

NoteThis sudo user should be configured as described on page 2-10.

NoteAn acknowledgement is displayed when the login information has been loaded, but this is not a confirmation that the details are valid. If the user name or password is invalid, the VCSLoginStatus parameter will be set to “suspicious state” after the next data collection.

WarningIf login information for the operating system changes, the details must be updated using this dialog.

Verifying Application Discovery

1. In the next full discovery cycle of the PATROL for Veritas Cluster Server (following successful KM licensing and user account configuration), the label of the main container instance will change from VCS_SETUP to Veritas Cluster Server. This new instance is shown in Figure 4-7.

NotePATROL for Veritas Cluster Server discovery can be forced by selecting the menu Force Discovery from VCS_SETUP.

2. After this full discovery cycle, all VCS KM collectors will start executing, and other VCS KM application class instances will be instantiated. The initial data collection may take some time (up to half an hour) depending on the complexity of your environment. Figure 4-7 shows the final PATROL Console view.



Figure 4-7 VCS KM Console View

NotePATROL for Veritas Cluster Server data collection can be forced by selecting the menu Refresh Parameters from the Veritas Cluster Server icon.

NoteBy default, some VCS KM components are monitored only from the master system or the active system, which has the configured failover service group ONLINE. This applies when the KM is configured to run in Multi-node Mode. The VCS KM will perform a passive (or standby) mode monitoring on all other slave systems or on systems where the configured failover service group is OFFLINE. Full monitoring can be forced on any system, by selecting Single-node Mode in the menu Configuration => Monitoring Mode.



Checking the Instance Limits

1. Check the default values for the maximum number of instances for each application class of the VCS KM and determine whether they suit your environment. These values can be viewed and modified on the Veritas Cluster Server instance using the menu Configuration => Instance Limits. Figure 4-8 shows the response dialog with the default values.

Figure 4-8 VCS KM Default Instance Limits



2. Select OK if any instance limit is altered. If the new instance limits are loaded successfully, an acknowledgement will be displayed.

WarningIncreasing the maximum number of application instances may impact the performance of the KM.

TipTo revert to the default setting for a particular application class, blank out the relevant field and click OK.

Checking the Initial Setup of the KM

1. Check whether the discovered files and directory paths are correct, using the menu Configuration => Paths from the Veritas Cluster Server instance.

2. Check whether the VCS KM is monitoring in the correct mode from parameter VCSMonitoringMode.

3. Check the InfoBoxes and Parameters of all the VCS KM instances and verify that they are set correctly.

4. Under each container instance, open all detail parameters (text parameters with names in the format VCS<Object>Details), and check for error messages.

5. Check the new values of parameters VCSLoginStatus and VCSLicenseStatus set after completion of all data collection. If either is not in OK state, open the annotation point to determine the cause of the error.

6. After the KM has been running for at least an hour, run the menu Configuration => KM Status from the Veritas Cluster Server instance. A report is displayed, detailing information on the managed system and licensing limits. Check through the report for any warnings or alarms.



NoteIf any errors are found during any of the above steps (including any incorrect data in Infoboxes or any warnings or alarms in the KM Status report), determine the cause(s) and take steps to resolve these errors. You may need to refer to “Chapter 5: Working with the KM”, or contact Technical Support at OTL Software, attaching the KM Status report.

NoteIf you are evaluating the KM and wish to purchase a license, send the KM Status report to OTL Software Limited to obtain your licence key.

TipTo save the KM Status report as a task window, click Save As Task. This task window can then be printed or saved as a text file.



Configuring PATROL Agent to Preload the KM

1. In order to enable PATROL for Veritas Cluster Server to operate all the time, without a PATROL Console connection, the KM should be added to the PATROL Agent configuration variable “/AgentSetup/preloadedKMs”. This can be achieved on the Veritas Cluster Server instance by using the menu Configuration => Preloading. The KM Preloading dialog will be displayed, as shown in Figure 4-9.

Figure 4-9 VCS KM Preloading dialog

2. Select Add to add the KM to the list of preloaded KMs. If the VCS KM is successfully added to the list, an acknowledgement will be displayed.

NoteThe same menu is used to remove the VCS KM from the preloaded KMs list.

Restarting PATROL Agent and PATROL Console

It should not be necessary to re-start the PATROL Agent and/or PATROL Console. However, it is a good practice to confirm that PATROL for Veritas Cluster Server by OTL Software operates correctly after a restart of PATROL Agent and/or PATROL Console. In addition, the PATROL Agent restart will force all KM discoveries and data collections to start immediately.



Unloading the KMThis section describes the procedures for unloading (not uninstalling) the VCS KM from the PATROL Agent, PATROL Console or PATROL Central Console. The intention is that this section is only used if you no longer want to use some parts of the KM, though there may be circumstances where you may wish to fully unload the KM without uninstalling the files.

NoteIf you want to completely uninstall the KM, please follow the instructions under “Uninstalling the KM” on page 3-10.If you are attempting to unload the KM in order to upgrade to a later version, please follow the instructions under “Installing the KM” on page 3-5.

When the VCS KM is unloaded from a PATROL Agent, PATROL stops monitoring the Veritas Cluster Server application on that system when there is no connection to a PATROL Console with VCS KM loaded.

When the VCS KM is unloaded from PATROL Console, the PATROL Console stops displaying and monitoring the Veritas Cluster Server application on any PATROL Console connected system.

Unloading the KM from the PATROL Agent

1. Remove the VCS KM from the list of preloaded KMs using the menu Configuration => Preloading from the Veritas Cluster Server instance. Alternatively, using the utility wpconfig (on MS Windows) or xpconfig (on Unix), remove VCS_LOAD.kml from the PATROL Agent configuration variable “/AgentSetup/preloadedKMs”.

2. Restart the PATROL Agent.

3. Repeat these steps on every PATROL Agent system (managed node) where the VCS KM is to be unloaded.



NoteThe VCS KM cannot be partially unloaded from the PATROL Agent using the above steps. If you need to unload some parts of the KM from the PATROL Agent, refer to the PATROL Agent Reference Manual.

Unloading the KM from PATROL Console

Application classes are unloaded individually. This allows for a partial unloading of the KM to enable it to run as a reduced installation. Follow the steps below to unload the VCS KM completely or partially.

1. Remove the unwanted VCS KM application classes from the list of loaded application classes, as required. All VCS KM application classes start with “VCS_”.

With the PATROL Console for Unix:

A. From the PATROL Console main window choose Attributes => Application Classes...

B. Select a VCS KM application class to be removed and choose Edit => Delete.

C. Repeat for all classes to be removed.

With the PATROL Console for MS Windows:

A. From the PATROL Console tree view choose the KM tab and expand the folder Application Classes.

B. Right-click on a VCS KM application class to be removed and choose Delete.

C. Repeat for all classes to be removed.

2. Select File => Save Configuration to save the modified list of loaded application classes as the PATROL Console user preference.

3. Repeat these steps on every PATROL Console system where the VCS KM is to be unloaded.



Unloading the KM from PATROL Central Console

A KM can be unloaded for particular managed systems or for all systems across the monitored environment. Application classes may be unloaded individually, or by selecting all classes at once. This allows for a partial unloading of the KM to enable it to run as a reduced installation on some or all of the managed systems. Follow the steps below to completely or partially unload the VCS KM from some or all of the managed systems.

1. Right click on the PATROL Main Map, and choose Unload Knowledge Modules...

2. Select the managed systems where the VCS KM is to be unloaded, and click Next>.

A list is displayed showing all the loaded application classes on each of the selected managed systems. All VCS KM application classes start with “VCS_”.

3. Select the VCS KM application classes to be removed for the appropriate managed systems, click Next> and Finish.

4. Repeat the above steps for each PATROL Central Management Profile where the VCS KM is to be unloaded.

Where to Go from HereThe following table suggests topics that you should read next..


How to monitor Veritas Cluster Server using this KM

“Chapter 5: Working with the KM”





5

Working with the KM 5

This chapter introduces basic tasks in PATROL® for Veritas Cluster Server™ by OTL Software. The following topics are discussed:

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Customizing the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Managed Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16GAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28LLT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36Service Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50

Operating the KM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56Generating Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60Debugging the KM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61Working with Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67Upgrading the Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71


Working with the KM 5-1

OverviewThe default behavior of the PATROL for Veritas Cluster Server is outlined in “Objectives” on page 1-3. Each area of the Veritas Cluster Server application is addressed to summarize the critical information monitored by the VCS KM.

You can either use default configuration, as described in the objectives, or you can customize areas of the KM to better suit the demands of your environment. After loading the VCS KM, a PATROL Classic Console (Developer or Operator) or a PATROL Central Console can be used to make changes as described in “Customizing the KM” on page 5-3.

Default VCS KM parameter settings can also be customized. Information on modifying parameters can be found in PATROL documentation. Also refer to “Appendix C: Parameter Definitions and Defaults”.

Administrative options and acknowledgement of alerts occurring for error messages on log files are described in this chapter, in “Operating the KM” on page 5-56. Reports are listed in “Generating Reports” on page 5-60.

For a complete listing of all menus (KM commands), including all the configuration options, refer to “Appendix A: KM Commands (Menus)”. Infobox items are listed and described in “Appendix B: InfoBoxes”.

If you experience any problems or unexpected behavior when using the VCS KM, refer to “Appendix D: Troubleshooting”. You may be required to activate the “debugging” feature to record information which may help to identify and resolve any problems. This feature is described in “Debugging the KM” on page 5-61.

NoteIf the KM has not been loaded, refer to “Chapter 4: Loading and Configuring” for procedures on loading the KM.



Customizing the KMPATROL for Veritas Cluster Server can be customized and optimized to suit your Veritas Cluster Server application environment. This section describes all menus available for customizing the VCS KM. These customization menus are accessed from the knowledge module command sub-menu Configuration => from each application instance. Most of these customization menus can be accessed either from the parent container level or from the child instance level.

If a customization menu is accessed from the container instance and you make a change, you then have the option to apply this change to all child instances which appear under the selected container in PATROL Console instance topology. If a customization menu is accessed from the child instance, it will only modify the configuration applicable for that instance.

NoteIn the absence of a child instance level configuration, the KM will search for any modified configuration through its topological parent path. If no customized configurations found, the KM will use the default configuration.

TipIf a menu command is named Configuration => System(s), it means that the menu command is available as Configuration => Systems from the parent container instance (system container instance) and Configuration => System from the child instance (individual system instance).



Managed Node

Customizing Monitoring Mode

The Monitoring Mode Configuration dialog is accessed from the Veritas Cluster Server instance using the menu Configuration => Monitoring Mode.

Figure 5-1 Monitoring Mode Configuration dialog

The default configuration for KM monitoring mode is shown in the Monitoring Mode Configuration dialog in Figure 5-1. Singe-node Mode allows the KM to perform full monitoring on the selected system.

The VCS KM should be installed on all nodes in the cluster to enable continuous monitoring and avoid single point of failure. To avoid duplicate VCS KM alerts from multiple nodes, the KM can be configured to operate in Multi-node Mode. Using the menu in Figure 5-1, select the appropriate Clustering Application, the Failover Group Name, Monitoring Node Names and enable Remote PATROL Agent Checking.

If Veritas Cluster File System is selected for Clustering Application, leave the Failover Group Name empty. Then the VCS KM will monitor the entire cluster from the active master system, which is identified by “vxdctl -c mode” command. This method requires vxconfigd in enable mode with its clustered state active.



NoteBy default, in passive nodes, VCS KM will not monitor agents, service groups, resources or systems. All other components are monitored.

Remote PATROL Agent Checking will require PATROL Agent login configuration for each node, as shown in Figure 5-2. Customize the Number of Attempts and Timeout (in Seconds) to fine tune the communication.

Figure 5-2 Remote PATROL Agent Configuration dialog

If the Remote PATROL Agent Checking is disabled, the KM will monitor actively through active master system or on the node where failover group is online and will not check the monitoring status of the other nodes through PATROL Agent.

If you want the KM to failover independently by performing a remote PATROL Agent check on selected nodes of the cluster, leave the Clustering Application and Failover Group Name empty, and enter only the Monitoring Node Names. Remote PATROL Agent Checking should be enabled and configured.



Once configured to operate successfully in Multi-node Mode, the VCS KM will monitor in Active Multi-node Mode through the master, online or first node, and Passive Multi-node Mode through the others, standing by for a failover. In the Passive Multi-node Mode, the VCS KM will monitor only the Veritas Cluster Server components, which cannot be monitored from the active node.

NoteIf a managed node is unable to determine the system which should be in Active Multi-node Mode, it will change to Temporary Single-node Mode. It will reset as soon as it detects a system in Active Multi-node Mode.

WarningIf multiple managed nodes in a cluster runs in Single-node Mode or Temporary Single-node Mode, duplicate events may be triggered from shared components (agents, service groups, resources and systems).

Customizing Node Status

The default configuration for monitored daemon names for determining the Server status is shown in the Node Status Configuration dialog in Figure 5-3.

The parameter VCSNodeStatus monitors availability of all configured daemons in the above filter. If any configured daemon is not running, this parameter will be set to “failure” (Alarm) state. As a result of this, several recovery actions are initiated. If any command run by PATROL for Veritas Cluster Server returns a server error message, this parameter will be set to “suspicious” (Warning) state.



Figure 5-3 Node Status Configuration dialog

In addition, the cluster state is checked and if it is not running VCSNodeStatus will be set to “failure” (Alarm). Simillarly if the cluster is not in read only mode or the wide areas connector is not running, it will be set to “suspicious” (Warning) state.

The Node Status Configuration dialog is accessed from the Veritas Cluster Server instance using the menu Configuration => Node Status. Daemons can be added or removed from the list. Multiple daemons may be entered at the same time, using a comma (,) as a separator.

TipTo revert to the shipped default list of monitored daemons (as shown above), type “[default]” as a new daemon for the list and click Update.



Agents

Customizing Monitored Agents

Figure 5-4 Agent Configuration dialog

By default, the PATROL for Veritas Cluster Server monitors all agents configured on the cluster, as shown in the Agent Configuration dialog in Figure 5-4. The [ALL] entry ensures that all agents found on a PATROL discovery are instantiated and monitored.

This dialog is accessed from the agent container instance (labelled Agents) using the menu Configuration => Agents.



An agent can be specifically enabled or disabled for monitoring by adding a new entry to the configuration in the global dialog above, or by accessing the dialog from the particular agent instance (using the menu Configuration => Agent). The advantage of specifically listing an agent in the configuration is that the agent will be instantiated, and therefore monitored, even if it is not automatically discovered.

NoteDisabled agent instances will be instantiated in an OFFLINE state, and their parameters will not be set.

TipTo revert to the default agent monitoring configuration (as shown above), access this dialog from the agent container instance (labelled Agents), type “[default]” as the name of a agent for a new entry and click Update.

Customizing Agent Status

The PATROL for Veritas Cluster Server checks the state of each monitored agent to set the value of parameter VCSAgentState. The value of this state parameter is used to determine the value of the status parameter VCSAgentStatus according to the agent status mapping rule. The default configuration of this mapping rule is displayed in the Agent Status Configuration dialog in Figure 5-5.

NoteStates (or conditional states) considered to indicate “failure” in the state parameter are mapped using the Alarm Filter to a value of 2=Failure in the status parameter. Then states (or conditional states) considered to be “suspicious” are mapped using the Warning Filter to a value of 1=Suspicious in the status parameter.The standard settings for the status parameter are as follows: 0 (Ok) is set to Ok; 1 (Suspicious) is set to Warning; 2 (Failure) is set to Alarm.



Figure 5-5 Agent Status Configuration dialog

To access the Agent Status Configuration dialog, use the menu Configuration => Agent(s) Status. The mapping rule can be customized individually for each agent instance, or for all agents at once by accessing the dialog from the agent container instance (labelled Agents).



The Agent Status Configuration dialog can be used to add or remove states for either filter. A time condition may be applied for a particular state when added to either filter.

ExampleYou may wish to add a state rule to the Warning Filter to warn when the agent is not started within an hour. Select 1 (Not Started) from the State drop-down list, select the Condition > and enter 60 Minutes. Click Update and the following will appear as a new entry in the Warning Filter: “1 (Not Started) >60 minutes”.

TipTo revert to the default agent status mapping rule for either filter, select [default] from the list of states and click Update. If you revert to default settings in this dialog when accessed from the agent instance level, the settings will revert to those configured at the container or parent instance level. To reset to the shipped default settings (as shown above), access this dialog from the agent container instance level. From this level you will also have the option to reset the configuration of any modified child instances.



Daemons

Customizing Monitored Daemons

Figure 5-6 Daemon Configuration dialog

The PATROL for Veritas Cluster Server can monitor all daemons of the Veritas Cluster Server application, but the default configuration (for Unix platforms) is shown in the Daemon Configuration dialog in Figure 5-6.

All listed daemons are instantiated even if they are not automatically discovered. Only those marked as “enabled” are monitored by default; those marked as “disabled” are instantiated in an OFFLINE state. The [ALL] entry line covers any other discovered daemons, ensuring they are also instantiated but disabled from monitoring.



The Daemon Configuration dialog above is accessed from the daemon container instance (labelled Daemons) using the menu Configuration => Daemons. Daemons can be enabled or disabled for monitoring from this dialog, or a new daemon entry can be added to the configuration.

The Daemon Configuration dialog can also be accessed from a particular daemon instance using the menu Configuration => Daemon. When this dialog is used to enable or disable a daemon, the daemon will appear as a specific entry in the main configuration at the container level.

NoteDisabled daemon instances will be instantiated in an OFFLINE state, and their parameters will not be set.

TipTo revert to the default daemon monitoring configuration (as shown above), access this dialog from the daemon container instance (labelled Daemons), type “[default]” as the name of a daemon for a new entry, and click Update.



Customizing Daemon Status

Figure 5-7 Daemon Status Configuration dialog

The PATROL for Veritas Cluster Server checks the status of each monitored daemon, to set the value of parameter VCSDaemonState. The value of this state parameter is used to determine the value of the status parameter VCSDaemonStatus according to the daemon status mapping rule. The default configuration of this mapping rule is displayed in the Daemon Status Configuration dialog in Figure 5-7.




To access the Daemon Status Configuration dialog, use the menu Configuration => Daemon(s) Status. The mapping rule can be customized individually for each daemon instance, or for all daemons at once by accessing the dialog from the daemon container instance (labelled Daemons).

The Daemon Status Configuration dialog can be used to add or remove states for either filter. A time condition may be applied for a particular state when added to either filter.

ExampleYou may wish to add a state rule to the Warning Filter to warn when a daemon has been waiting for more than two hours. Select 2 (Waiting) from the State drop-down list, select the Condition > and enter 120 Minutes. Click Update and the following will appear as a new entry in the Warning Filter: “2 (Waiting) >120 minutes”.

TipTo revert to the default daemon status mapping rule for either filter, select [default] from the list of states and click Update. If you revert to default settings in this dialog when accessed from the daemon instance level, the settings will revert to those configured at the container or parent instance level. To reset to the shipped default settings (as shown above), access this dialog from the daemon container instance level. From this level you will also have the option to reset the configuration of any modified child instances.



Systems

Customizing Monitored Systems

Figure 5-8 System Configuration dialog

By default, the PATROL for Veritas Cluster Server monitors all systems configured on the cluster, as shown in the System Configuration dialog in Figure 5-8. The [ALL] entry ensures that all systems found on a PATROL discovery are instantiated and monitored.

This dialog is accessed from the system container instance (labelled Systems) using the menu Configuration => Systems.



A system can be specifically enabled or disabled for monitoring by adding a new entry to the configuration in the global dialog above, or by accessing the dialog from the particular system instance (using the menu Configuration => System). The advantage of specifically listing a system in the configuration is that the client will be instantiated, and therefore monitored, even if it is not automatically discovered.

NoteDisabled system instances will be instantiated in an OFFLINE state, and their parameters will not be set.

TipTo revert to the default system monitoring configuration (as shown above), access this dialog from the system container instance (labelled Systems), type “[default]” as the name of a system for a new entry and click Update.

Customizing System Status

The PATROL for Veritas Cluster Server checks the state of each monitored system to set the value of parameter VCSSystemState. The value of this state parameter is used to determine the value of the status parameter VCSSystemStatus according to the system status mapping rule. The default configuration of this mapping rule is displayed in the System Status Configuration dialog in Figure 5-9.




Figure 5-9 System Status Configuration dialog

To access the System Status Configuration dialog, use the menu Configuration => System(s) Status. The mapping rule can be customized individually for each system instance, or for all systems at once by accessing the dialog from the system container instance (labelled Systems).



The System Status Configuration dialog can be used to add or remove states for either filter. A time condition may be applied for a particular state when added to either filter.

ExampleYou may wish to change the state rule to alarm when the system has been waiting for an administration task after 10 minutes, instead of warning immediately (default). Highlight the 8 (ADMIN_WAIT) from the Warning Filter State Rules, select 8 (ADMIN_WAIT) from the State drop-down list in the alarm section, select the Condition > and enter 10 Minutes. Click Update and the following will appear as a new entry in the Alarm Filter: “8 (ADMIN_WAIT) >10 minutes”, and the Warning Filter will no longer contain any rule for 8 (ADMIN_WAIT).

TipTo revert to the default system status mapping rule for either filter, select [default] from the list of states and click Update. If you revert to default settings in this dialog when accessed from the system instance level, the settings will revert to those configured at the container or parent instance level. To reset to the shipped default settings (as shown above), access this dialog from the system container instance level. From this level you will also have the option to reset the configuration of any modified child instances.



Customizing System Frozen Status

Figure 5-10 System Frozen Status Configuration dialog

The PATROL for Veritas Cluster Server checks the frozen state of each monitored system to set the value of parameter VCSSystemFrozenState. The value of this state parameter is used to determine the value of the status parameter VCSSystemFrozenStatus according to the system frozen status mapping rule. The default configuration of this mapping rule is displayed in the System Frozen Status Configuration dialog in Figure 5-10.




To access the System Frozen Status Configuration dialog, use the menu Configuration => System(s) Frozen Status. The mapping rule can be customized individually for each system instance, or for all systems at once by accessing the dialog from the system container instance (labelled Systems).

The System Frozen Status Configuration dialog can be used to add or remove states for either filter. A time condition may be applied for a particular state when added to either filter.

ExampleYou may wish to change the state rule to warn when the system has been temporarily frozen for more than 10 minutes, instead of warning immediately (default). Highlight the 1 (TFrozen) from the Warning Filter State Rules, select 1 (TFrozen) from the State drop-down list in the warning section, select the Condition > and enter 10 Minutes. Click Update and the following will appear as a new entry in the Warning Filter: “1 (TFrozen) >10 minutes”.

TipTo revert to the default system frozen status mapping rule for either filter, select [default] from the list of states and click Update. If you revert to default settings in this dialog when accessed from the system instance level, the settings will revert to those configured at the container or parent instance level. To reset to the shipped default settings (as shown above), access this dialog from the system container instance level. From this level you will also have the option to reset the configuration of any modified child instances.



Customizing System Up/Down Status

Figure 5-11 System Up/Down Status Configuration dialog

The PATROL for Veritas Cluster Server checks the up/down state of each monitored system to set the value of parameter VCSSystemUpDownState. The value of this state parameter is used to determine the value of the status parameter VCSSystemFrozenStatus according to the system frozen status mapping rule. The default configuration of this mapping rule is displayed in the System Up/Down Status Configuration dialog in Figure 5-11.




To access the System Up/Down Status Configuration dialog, use the menu Configuration => System(s) Up/Down Status. The mapping rule can be customized individually for each system instance, or for all systems at once by accessing the dialog from the system container instance (labelled Systems).

The System Up/Down Status Configuration dialog can be used to add or remove states for either filter. A time condition may be applied for a particular state when added to either filter.

ExampleYou may wish to change the state rule to alarm when the system has been down for more than 10 minutes, instead of warning immediately (default). Highlight the 1 (TFrozen) from the Warning Filter State Rules, select 0 (Down) from the State drop-down list in the alarm section, select the Condition > and enter 10 Minutes. Click Update and the following will appear as a new entry in the Alarm Filter: “0 (Down) >10 minutes”.

TipTo revert to the default system up/down status mapping rule for either filter, select [default] from the list of states and click Update. If you revert to default settings in this dialog when accessed from the system instance level, the settings will revert to those configured at the container or parent instance level. To reset to the shipped default settings (as shown above), access this dialog from the system container instance level. From this level you will also have the option to reset the configuration of any modified child instances.



Customizing Monitored Heartbeats

Figure 5-12 Heartbeat Configuration dialog

By default, the PATROL for Veritas Cluster Server monitors all heartbeats of each monitored system, as shown in the Heartbeat Configuration dialog in Figure 5-12. The [ALL] entry ensures that all heartbeats found on a monitored system are instantiated and monitored.

This dialog can be accessed from each system instance using the menu Configuration => Heartbeats.



A heartbeat can be specifically enabled or disabled for monitoring by adding a new entry to the configuration in the heartbeat dialog above, or by accessing the dialog from the particular heartbeat instance (using the menu Configuration => Heartbeat). The advantage of specifically listing heartbeat in the configuration is that the heartbeat will be instantiated, and therefore monitored, even if it is not automatically discovered.

NoteDisabled heartbeat instances will be instantiated in an OFFLINE state, and their parameters will not be set.

TipTo revert to the default heartbeat monitoring configuration (as shown above) for a particular system, access this dialog from the system instance, type “[default]” as the name of a heartbeat for a new entry and click Update.

Customizing Heartbeat Status

The PATROL for Veritas Cluster Server checks the state of each monitored heartbeat to set the value of parameter VCSHeartbeatState. The value of this state parameter is used to determine the value of the status parameter VCSHeartbeatStatus according to the heartbeat status mapping rule. The default configuration of this mapping rule is displayed in the Heartbeat Status Configuration dialog in Figure 5-13.




Figure 5-13 Heartbeat Status Configuration dialog

The Heartbeat Status Configuration dialog can be accessed at three levels to allow the mapping rule to be customized:

• individually for a particular heartbeat by accessing the dialog from the heartbeat instance, using the menu Configuration => Heartbeat Status

• for all heartbeats on a system by accessing the dialog from the system instance, using the menu Configuration => Heartbeats Status



• for all heartbeats on all systems at once by accessing the dialog from the system container instance (labelled Systems), using the menu Configuration => Heartbeats Status

The Heartbeat Status Configuration dialog can be used to add or remove states for either filter. A time condition may be applied for a particular state when added to either filter.

ExampleYou may wish to amend the rule that appears in the default Alarm Filter (in Figure 5-13) to alarm when heartbeat has been “Down” for more than one hour, rather than the default immediate alarm. Select 0 (Down) from the State drop-down list, select the Condition > and enter 60 Minutes. Click Update and the following will appear as a new entry in the Warning Filter: “0 (Down) >60 minutes”. The original rule “0 (Down)” can be removed by selecting the entry line and clicking Update.

TipTo revert to the default heartbeat status mapping rule for either filter, select [default] from the list of states and click Update. If you revert to default settings in this dialog when accessed from the heartbeat instance level, the settings will revert to those configured at the container or parent instance level. To reset to the shipped default settings (as shown above), access this dialog from the system container instance level. From this level you will also have the option to reset the configuration of any modified child instances.



GAB

Customizing Monitored GABs

Figure 5-14 GAB Configuration dialog

The default configuration for monitored GABs is displayed in the GAB Configuration dialog in Figure 5-14. This dialog is accessed from the GAB container instance (labelled GAB), using the menu Configuration => GABs.

The PATROL for Veritas Cluster Server monitors all Veritas Cluster Server GABs. The [ALL] entry ensures that all GABs found on a monitored system are instantiated and monitored.



A GAB can be specifically enabled or disabled for monitoring by adding a new entry to the configuration in the GAB dialog above, or by accessing the dialog from the particular GAB instance (using the menu Configuration => GAB). The advantage of specifically listing GAB in the configuration is that the GAB will be instantiated, and therefore monitored, even if it is not automatically discovered.

In versions 3.x and 4.x of Veritas Cluster Server, GAB instances are created according to the GAB disk heartbeat configuration. In Veritas Cluster Server version 5.0 or later, where GAB disk heartbeats have been deprecated, the instances are created according to the GAB module configuration.

NoteDisabled GAB instances will be instantiated in an OFFLINE state, and their parameters will not be set.

TipTo revert to the default GAB monitoring configuration as shown above, access this dialog from the GAB container instance (labelled GABs), type “[default]” as the name of a GAB for a new entry, and click Update.

Customizing GAB Status

The PATROL for Veritas Cluster Server checks the state of each monitored GAB to set the value of the parameter VCSGabState. The value of this state parameter is used to determine the value of the status parameter VCSGabStatus according to the GAB status mapping rule. The default configuration of this mapping rule is displayed in Figure 5-15.



Figure 5-15 GAB Status Configuration dialog




To customize the mapping rule for a particular GAB, access the GAB Status Configuration dialog from that instance using the menu Configuration => GAB Status. The mapping rule can also be customized for all GABs at once by accessing the dialog from the GAB container instance (labelled GABs).

The GAB Status Configuration dialog can be used to add or remove states for either filter. A time condition may be applied for a particular state when added to either filter.

ExampleYou may wish to modify the default state rule in the Alarm Filter to set the parameter to “failure” only when GAB has been in jeopardy for more than one hour. Select 2 (Jeopardy) from the current Alarm Filter list (to remove the current setting), and select 2 (Jeopardy) from the State drop-down list in the Alarm Filter, select the Condition > and enter 60 Minutes. Click Update to accept all these changes and the following will appear as new entries in the Alarm Filter: “2 (Jeopardy) >60 minutes”. Click Close for these changes to take effect.

TipTo revert to the default GAB status mapping rule for either filter, select [default] from the list of states and click Update. If you revert to default settings in this dialog when accessed from the GAB instance level, the settings will revert to those configured at the container or parent instance level. To reset to the shipped default settings (as shown above), access this dialog from the GAB container instance level. From this level you will also have the option to reset the configuration of any modified child instances.



LLT

Customizing Monitored LLTs

Figure 5-16 LLT Configuration dialog

The default configuration for monitored LLTs is displayed in the LLT Configuration dialog in Figure 5-16. This dialog is accessed from the LLT container instance (labelled LLT), using the menu Configuration => LLTs.

The PATROL for Veritas Cluster Server monitors all Veritas Cluster Server LLTs. The [ALL] entry ensures that all LLTs found on a monitored system are instantiated and monitored.



A LLT can be specifically enabled or disabled for monitoring by adding a new entry to the configuration in the LLT dialog above, or by accessing the dialog from the particular LLT instance (using the menu Configuration => LLT). The advantage of specifically listing LLT in the configuration is that the LLT will be instantiated, and therefore monitored, even if it is not automatically discovered.

NoteDisabled LLT instances will be instantiated in an OFFLINE state, and their parameters will not be set.

TipTo revert to the default LLT monitoring configuration as shown above, access this dialog from the LLT container instance (labelled LLTs), type “[default]” as the name of a LLT for a new entry, and click Update.

Customizing LLT Status

The PATROL for Veritas Cluster Server checks the state of each monitored LLT to set the value of the parameter VCSLltState. The value of this state parameter is used to determine the value of the status parameter VCSLltStatus according to the LLT status mapping rule. The default configuration of this mapping rule is displayed in Figure 5-17.




Figure 5-17 LLT Status Configuration dialog

To customize the mapping rule for a particular LLT, access the LLT Status Configuration dialog from that instance using the menu Configuration => LLT Status. The mapping rule can also be customized for all LLTs at once by accessing the dialog from the LLT container instance (labelled LLTs).



The LLT Status Configuration dialog can be used to add or remove states for either filter. A time condition may be applied for a particular state when added to either filter.

ExampleYou may wish to modify the default state rule in the Alarm Filter to set the parameter to “failure” only when LLT has been down for more than one hour. Select 0 (Down) from the current Alarm Filter list (to remove the current setting), and select 0 (Down) from the State drop-down list in the Alarm Filter, select the Condition > and enter 60 Minutes. Click Update to accept all these changes and the following will appear as new entries in the Alarm Filter: “0 (Down) >60 minutes”. Click Close for these changes to take effect.

TipTo revert to the default LLT status mapping rule for either filter, select [default] from the list of states and click Update. If you revert to default settings in this dialog when accessed from the LLT instance level, the settings will revert to those configured at the container or parent instance level. To reset to the shipped default settings (as shown above), access this dialog from the LLT container instance level. From this level you will also have the option to reset the configuration of any modified child instances.



Log Files

Customizing Monitored Log Files

Figure 5-18 Log Configuration dialog

The default configuration is for the PATROL for Veritas Cluster Server to monitor the VCS engine log file and the system log file, as displayed in the Log Configuration dialog in Figure 5-18. This dialog is accessed from the log container instance (labelled Logs), using the menu Configuration => Logs.



The listed log files are always instantiated, and therefore monitored, even if they are not automatically discovered. The [ALL] entry line covers any other discovered Veritas Cluster Server server log files, ensuring they are instantiated but disabled from monitoring.

NoteOn AIX and Microsoft Windows platforms, there is no ASCII format system log file to monitor, so the default is for the KM to monitor only the VCS engine log file.

NoteDisabled log instances will be instantiated in an OFFLINE state, and the commands related to those logs will not be executed, leaving their parameters not set.

A log file can be enabled (or disabled) for monitoring by adding a new entry to the configuration in the global dialog above, or by accessing the dialog from the particular log instance (using the menu Configuration => Log). When this dialog is used to enable (or disable) a log file, the log file will appear as a specific entry in the main configuration at the container level.

NoteIf you enable a log file for monitoring, you must specifically configure the log filter with appropriate expressions. Refer to “Customizing Log Error Filter” on page 5-38 for more information.

TipTo revert to the default log file monitoring configuration as shown above, access this dialog from the log container instance (labelled Logs), type “[default]” as the name of a log file for a new entry, and click Update.



The VCS KM scans log files by reading the new log entries since the last data collection cycle. The VCS KM imposes a limit on the amount of data that may be scanned per log file during each data collection cycle. By default, this Log Scan Limit is set at 5 KBytes, but can be modified using the menu Configuration => Log(s) Scan Limit.

WarningIncreasing the Log Scan Limit may affect the performance of the data collector (VCSLogCollector).

Customizing Log Error Filter

The PATROL for Veritas Cluster Server checks for particular error expressions in the log data scanned in each data collection cycle and written to VCSLogText. When any of these expressions is detected, the message containing the expression will be written to one of the text parameters VCSLogAlarmText or VCSLogWarningText, as appropriate.

These expressions and their severity are determined according to the mapping of error expressions in the log filter configuration. The default mapping is displayed in the Log Filter Configuration dialog in Figure 5-19. This default configuration does not include any “excluded” expressions, but the functionality exists to customize the filter if another unwanted message is selected.

NoteFor an explanation of the possible error messages in the log files, refer to the Veritas Cluster Server System Administrator’s Guide and the Veritas Cluster Server Troubleshooting Guide.

NoteThe regular expressions in the log filter are case-sensitive.



Figure 5-19 Log Filter Configuration dialog

NoteMessages containing expressions considered to be “suspicious” in the VCSLogText parameter are mapped using the Warning Filter to be written to the parameter VCSLogWarningText. This increments the value of parameter VCSLogWarningCount, which is automatically set to warning if the value is 1 or above.Similarly, messages containing expressions considered to indicate “failure” are mapped using the Alarm Filter to be written to VCSLogAlarmText, which in turn increments VCSLogAlarmCount causing it to alarm at a value of 1 or above.Messages containing expressions listed in either filter and also containing an “excluded” expression for that filter, are ignored.



To access the Log Filter Configuration dialog, use the menu Configuration => Log(s) Filter. The mapping of the error expressions can be customized individually for a log file instance, or for all log files at once by accessing the dialog from the log container instance (labelled Logs).

Expressions can be added or removed from each filter. The radio button Include is highlighted by default when adding a new expression. The functionality to “exclude” one or more expressions can be used on either filter to exclude certain messages from the warning or alarm parameters, which have already been detected using the “include” expressions.

ExampleTo avoid alarms occurring for messages concerning a particular client (otlsol01), enter the client name as an expression in the Alarm Filter, select the Expression Type as Exclude, and click Update. The following will appear as an entry in the Alarm Filter: “exclude:otlsol01”.Instead you could limit the exclusion to a particular expression already listed by using standard wildcard syntax, such as “skipping .∗ otlsol01”.

Since the default configuration for logs in the VCS KM is to only monitor the daily Veritas Cluster Server messages file and the system log file, the default log filter is configured accordingly. If you enable any additional log files for monitoring (described in “Customizing Monitored Log Files” on page 5-36), you will need to customize the log filter by adding appropriate expressions for those log files. This can be done at either the parent or child level.

TipTo revert to the default settings for either filter, type “[default]” as a new error expression for that filter, and click Update. If you revert to the default when accessed from the log instance level, the settings will revert to the parent or container instance level. To revert to the shipped default settings (as shown above), access this dialog from the log container instance. From this level you will also have the option to reset the configuration of any modified child instances.



Customizing Log Alert Acknowledgement

Figure 5-20 Log Alert Acknowledgement Configuration dialog

By default, the PATROL for Veritas Cluster Server automatically acknowledges previous log alerts when it detects new errors. Figure 5-20 shows the default settings in the Log Alert Acknowledgement Configuration dialog.

This dialog can be accessed using the menu Configuration => Log(s) Alert Acknowledgement. The method of log alert acknowledgement can be changed for individual log file instances or for all log files at once at the log container instance level (labelled Logs).

WarningFor the manual acknowledgement method, if log alerts are not acknowledged regularly, the size of the parameters VCSLogAlarmText and VCSLogWarningText will increase cumulatively. This increase in size may affect performance of the KM and the PATROL Agent.



Service Groups

Customizing Monitored Groups

Figure 5-21 Group Configuration dialog

By default, the PATROL for Veritas Cluster Server monitors all service groups configured in the cluster. This is shown in the Group Configuration dialog in Figure 5-21. The [ALL] entry ensures that all service groups found on a PATROL discovery are instantiated and monitored.

This dialog is accessed from the group container instance (labelled Service Groups) using the menu Configuration => Groups.



A group can be specifically enabled or disabled for monitoring by adding a new entry to the configuration in the global dialog above, or by accessing the dialog from the particular group instance (using the menu Configuration => Group. The advantage of specifically listing a group in the configuration is that the group will be instantiated, and therefore monitored, even if it is not automatically discovered.

NoteDisabled group instances will be instantiated in an OFFLINE state, and their parameters will not be set.

TipTo revert to the default group monitoring configuration (as shown above), access this dialog from the group container instance (labelled Service Groups), type “[default]” as the name of a group for a new entry and click Update.

TipBy default, the PATROL for Veritas Cluster Server collects monitoring data for all groups in a single command execution instead of repeating queries for individual groups. This is designed to improve the VCS KM performance in most situations. However, this may not be efficient in an environment where the number of groups to be monitored by VCS KM is a very small portion of total number of groups that exist in the entire Veritas Cluster Server installation. In such a configuration, the mass-processing of group monitoring data can be turned off by running the following PSL through PATROL Console:%PSL pconfig("REPLACE","/VCS/GroupListDetail", false);



Customizing Group Frozen Status

Figure 5-22 Group Frozen Status Configuration dialog

The PATROL for Veritas Cluster Server checks the frozen state of each monitored group to set the value of parameter VCSGroupFrozenState. The value of this state parameter is used to determine the value of the status parameter VCSGroupFrozenStatus according to the group frozen status mapping rule. The default configuration of this mapping rule is displayed in the Group Frozen Status Configuration dialog in Figure 5-22.




To access the Group Frozen Status Configuration dialog, use the menu Configuration => Group(s) Frozen Status. The mapping rule can be customized individually for each group instance, or for all groups at once by accessing the dialog from the group container instance (labelled Service Groups).

The Group Frozen Status Configuration dialog can be used to add or remove states for either filter. A time condition may be applied for a particular state when added to either filter.

ExampleYou may wish to change the state rule to warn when the group has been temporarily frozen for more than 10 minutes, instead of warning immediately (default). Highlight the 1 (TFrozen) from the Warning Filter State Rules, select 1 (TFrozen) from the State drop-down list in the warning section, select the Condition > and enter 10 Minutes. Click Update and the following will appear as a new entry in the Warning Filter: “1 (TFrozen) >10 minutes”.

TipTo revert to the default group frozen status mapping rule for either filter, select [default] from the list of states and click Update. If you revert to default settings in this dialog when accessed from the group instance level, the settings will revert to those configured at the container or parent instance level. To reset to the shipped default settings (as shown above), access this dialog from the group container instance level. From this level you will also have the option to reset the configuration of any modified child instances.



Customizing Monitored Group Systems

Figure 5-23 Group System Configuration dialog

By default, the PATROL for Veritas Cluster Server monitors all group systems of each monitored group, as shown in the Group System Configuration dialog in Figure 5-23. The [ALL] entry ensures that all group systems found on a PATROL discovery are instantiated and monitored.

This dialog can be accessed from each group instance using the menu Configuration => Group Systems.



A group system can be specifically enabled or disabled for monitoring by adding a new entry to the configuration in the global dialog above, or by accessing the dialog from the particular group system instance (using the menu Configuration => Group System). The advantage of specifically listing a group system in the configuration is that the group system will be instantiated, and therefore monitored, even if it is not automatically discovered.

NoteDisabled group system instances will be instantiated in an OFFLINE state, and their parameters will not be set.

TipTo revert to the default group system monitoring configuration (as shown above) for a particular group, access this dialog from the group system instance, type “[default]” as the name of a group system for a new entry and click Update.

Customizing Group System Status

The PATROL for Veritas Cluster Server checks the state of each monitored group system to set the value of parameter VCSGSystemState. The value of this state parameter is used to determine the value of the status parameter VCSGSystemStatus according to the group system status mapping rule. The default configuration of this mapping rule is displayed in the Group System Status Configuration dialog in Figure 5-24.




Figure 5-24 Group System Status Configuration dialog

The Group System Status Configuration dialog can be accessed at three levels to allow the mapping rule to be customized:

• individually for a particular group system by accessing the dialog from the group system instance, using the menu Configuration => Group System Status



• for all group systems in a service group by accessing the dialog from the system instance, using the menu Configuration => Group Systems Status

• for all group systems on all service groups at once by accessing the dialog from the system container instance (labelled Service Groups), using the menu Configuration => Groups Systems Status

The Group System Status Configuration dialog can be used to add or remove states for either filter. A time condition may be applied for a particular state when added to either filter.

ExampleYou may wish to amend the rule that appears in the default Warning Filter (in Figure 5-24) to warn when a group system has been starting for more than two hours, rather than the default immediate warning. Select 2 (STARTING) from the State drop-down list, select the Condition > and enter 120 Minutes. Click Update and the following will appear as a new entry in the Warning Filter: “2 (STARTING) >120 minutes”. The original rule “2 (STARTING)” can be removed by selecting the entry line and clicking Update.

TipTo revert to the default group system status mapping rule for either filter, select [default] from the list of states and click Update. If you revert to default settings in this dialog when accessed from the group system instance level, the settings will revert to those configured at the container or parent instance level. To reset to the shipped default settings (as shown above), access this dialog from the group container instance level. From this level you will also have the option to reset the configuration of any modified child instances.



Resources

Customizing Monitored Resources

Figure 5-25 Resource Configuration dialog

By default, the PATROL for Veritas Cluster Server monitors all resources configured in the cluster. This is shown in the Resource Configuration dialog in Figure 5-25. The [ALL] entry ensures that all resources found on a PATROL discovery are instantiated and monitored.

This dialog is accessed from the group container instance (labelled Resources) using the menu Configuration => Resources.



A resource can be specifically enabled or disabled for monitoring by adding a new entry to the configuration in the global dialog above, or by accessing the dialog from the particular resource instance (using the menu Configuration => Resource. The advantage of specifically listing a resource in the configuration is that the resource will be instantiated, and therefore monitored, even if it is not automatically discovered.

NoteDisabled resource instances will be instantiated in an OFFLINE state, and their parameters will not be set.

TipTo revert to the default resource monitoring configuration (as shown above), access this dialog from the resource container instance (labelled Resources), type “[default]” as the name of a resource for a new entry and click Update.

TipBy default, the PATROL for Veritas Cluster Server collects monitoring data for all resources in a single command execution instead of repeating queries for individual resources. This is designed to improve the VCS KM performance in most situations. However, this may not be efficient in an environment where the number of resources to be monitored by VCS KM is a very small portion of total number of resources that exist in the entire Veritas Cluster Server installation. In such a configuration, the mass-processing of resource monitoring data can be turned off by running the following PSL through PATROL Console:%PSL pconfig("REPLACE","/VCS/ResourceListDetail", false);



Customizing Monitored Resource Systems

Figure 5-26 Resource System Configuration dialog

By default, the PATROL for Veritas Cluster Server monitors all resource systems of each monitored resource, as shown in the Resource System Configuration dialog in Figure 5-26. The [ALL] entry ensures that all resource systems found on a PATROL discovery are instantiated and monitored.

This dialog can be accessed from each group instance using the menu Configuration => Resource Systems.



A resource system can be specifically enabled or disabled for monitoring by adding a new entry to the configuration in the global dialog above, or by accessing the dialog from the particular resource system instance (using the menu Configuration => Resource System). The advantage of specifically listing a resource system in the configuration is that the resource system will be instantiated, and therefore monitored, even if it is not automatically discovered.

NoteDisabled resource system instances will be instantiated in an OFFLINE state, and their parameters will not be set.

TipTo revert to the default resource system monitoring configuration (as shown above) for a particular resource, access this dialog from the resource system instance, type “[default]” as the name of a resource system for a new entry and click Update.

Customizing Resource System Status

The PATROL for Veritas Cluster Server checks the state of each monitored resource system to set the value of parameter VCSRSystemState. The value of this state parameter is used to determine the value of the status parameter VCSRSystemStatus according to the resource system status mapping rule. The default configuration of this mapping rule is displayed in the Resource System Status Configuration dialog in Figure 5-27.




Figure 5-27 Resource System Status Configuration dialog

The Resource System Status Configuration dialog can be accessed at three levels to allow the mapping rule to be customized:

• individually for a particular resource system by accessing the dialog from the resource system instance, using the menu Configuration => Resource System Status



• for all resource systems in a resource by accessing the dialog from the resource instance, using the menu Configuration => Resource Systems Status

• for all resource systems on all resources at once by accessing the dialog from the resource container instance (labelled Resources), using the menu Configuration => Resources Systems Status

The Resource System Status Configuration dialog can be used to add or remove states for either filter. A time condition may be applied for a particular state when added to either filter.

ExampleYou may wish to amend the rule that appears in the default Warning Filter (in Figure 5-24) to warn when a resource system has been starting for more than two hours, rather than the default immediate warning. Select 2 (STARTING) from the State drop-down list, select the Condition > and enter 120 Minutes. Click Update and the following will appear as a new entry in the Warning Filter: “2 (STARTING) >120 minutes”. The original rule “2 (STARTING)” can be removed by selecting the entry line and clicking Update.

TipTo revert to the default resource system status mapping rule for either filter, select [default] from the list of states and click Update. If you revert to default settings in this dialog when accessed from the resource system instance level, the settings will revert to those configured at the container or parent instance level. To reset to the shipped default settings (as shown above), access this dialog from the resource container instance level. From this level you will also have the option to reset the configuration of any modified child instances.



Operating the KMThis section describes day-to-day operational tasks of the PATROL for Veritas Cluster Server, including:

• administrative operations• generation of various application reports• acknowledgement of alerts

These operations can be performed using menus under sub-menus Administration, Reports and Acknowledgement respectively. The following points should be noted in relation to these sub-menus:

• An annotation point will be added to the relevant parameter when executing any menu available under sub-menus Administration and Acknowledgement.

• When an alert is acknowledged using the menus available under the sub-menu Acknowledgement, it will stay acknowledged even after restarting the PATROL Agent.

• All menus under sub-menus Administration and Reports require a privileged operating system user account to carry out the operation.

NoteIf a menu uses a sudo privileged user account, then the user account should match the configured PATROL Console user, specified in <Hostname> => Properties... under the tab Security.



Administering Server

Figure 5-28 Server Administration sub-menu

The PATROL for Veritas Cluster Server provides secure server administration menus, which can be executed by PATROL Console users, if they have appropriate privileges. Figure 5-28 illustrates how to access the administrative menus available on the server from PATROL Console:

• Administration => Start Server• Administration => Stop Server

Acknowledging Log Alerts

When an error is detected in a monitored log file, it will appear under one of the text parameters VCSLogAlarmText or VCSLogWarningText. This will trigger an Alarm or a Warning on parameter VCSLogAlarmCount or VCSLogWarningCount, respectively.

These alerts can be acknowledged automatically (by default) or manually. Refer to “Customizing Log Alert Acknowledgement” on page 5-41 to change the method of acknowledgement to manual.



TipWhen the method of acknowledgement is set to automatic, you can still use these menu commands to clear alerts, rather than waiting for the automatic cycle.

Figure 5-29 Log Alert Acknowledgement sub-menu

Figure 5-29 illustrates how to access the Log Alert Acknowledgement sub-menu from any log file instance, allowing you to view and acknowledge alerts as follows:

• Use the menu Acknowledgement => Warnings to view, select and acknowledge errors individually in the text parameter VCSLogWarningText.

• Use the menu Acknowledgement => Alarms to view, select and acknowledge errors individually in text parameter or VCSLogAlarmText.

• To acknowledge all alerts (Warnings and Alarms) at once without viewing, use the menu Acknowledgement => All.



Administering Service Groups

Figure 5-30 Service Group Administration sub-menu

Figure 5-30 illustrates how to access the Service Group Administration sub-menu from the service group instance. The available menus are:

• Administration => Freeze Group• Administration => Unfreeze Group

When the appropriate menu is accessed from a particular service group instance, that service group can be frozen or thawed, respectively.



Generating ReportsFollowing is a list of reports available in the PATROL for Veritas Cluster Server.

• Veritas Cluster Server => Reports => Cluster Status Summary - reports the summary Veritas Cluster Server status

• Daemons => Reports => Daemon List - lists all running Veritas Cluster Server daemons

• GAB => Reports => GAB Module Status - reports the status of the GAB module

• LLT => Reports => LLT Module Status - reports the status of the LLT module

• LLT => Reports => LLT Statistics - reports the statistics on the LLT

• <Log instance> => Reports => Last Messages - displays the last messages logged in the selected log file

• Service Groups => Reports => Groups Status Summary - reports the status summary all service groups

• <Group instance> => Reports => Group Dependencies - displays dependency information about the selected service group

• <Group instance> => Reports => Group Resources - lists all resources for the selected service group

• Resources => Reports => Resources Status Summary - reports the status summary all resources

• <Resource instance> => Reports => Resource Dependencies - displays dependency information about the selected resource

TipTo save the report as a task window click Save As Task. This task window can then be printed or saved as a text file.



Debugging the KMThis section describes the steps for enabling and disabling the debug feature for the PATROL for Veritas Cluster Server. This feature produces an output that can help you identify unexplained behaviour and may be requested by OTL Software to diagnose and resolve any problems with the KM.

Enable KM Debug Mode

Step 1 Select the KM menu command Configuration => Debug from the main VCS KM container instance (labelled Veritas Cluster Server or VCS_SETUP). The VCS KM Debug Configuration dialog will be displayed, as shown in Figure 5-31.

Figure 5-31 VCS KM Debug Configuration dialog



Step 2 Click On for the debug switch(es) you want to enable. Table 5-1 shows the application classes and collector parameters included in the debug switch for each object.

NoteIf debugging for an object is turned on, debugging for the following is also enabled for all application classes with that object: KM commands (menus), InfoBoxes, recovery actions for consumer parameters, pre-discovery and discovery functions defined under an application class.

Table 5-1 VCS KM Object Debug Switch Association

Object Debug Switch

Application Classes Collector Parameters

Server VCS_SERVER VCSCreateDistributionVCSRemoveTempFilesVCSUpdateAgent

Agent VCS_AGENT_CONTAINERVCS_AGENT

VCSAgentCollector

Daemon VCS_DAEMON_CONTAINERVCS_DAEMON

VCSDaemonCollector

System VCS_SLAVE_CONTAINERVCS_SLAVEVCS_HEARTBEAT

VCSSystemCollector

GAB VCS_GAB_CONTAINERVCS_GAB

VCSGabCollector

LLT VCS_LLT_CONTAINERVCS_LLT

VCSLltCollector

Log VCS_LOG_CONTAINERVCS_LOG

VCSLogCollector

Cluster VCS_GROUP_CONTAINERVCS_GROUPVCS_GSYSTEMVCS_RESOURCE_CONTAINERVCS_RESOURCEVCS_RSYSTEM

VCSGroupCollectorVCSResourceCollector



Step 3 By default, all debug messages are sent to both a task window and a file or set of files, as detailed below. You may choose to select one method or the other, but the default setting of Both is recommended.

• The Send to File(s) option writes all debug messages to a file or set of files in a specified debug folder on the managed system. The path of the debug folder is:• $PATROL_HOME/lib/VCS/debug on Unix systems• %PATROL_HOME%\lib\VCS\debug on MS Windows

systems

WarningSending debug data to file will increase the file system usage under the above debug folder. Required space under this file system depends on the complexity of the Veritas Cluster Server environment. If the available space for this folder is less than 10 MBytes, it can be changed to a different file system, which has sufficient disk space. This can be achieved by replacing the debug folder with a soft link pointing to a different file system, like /tmp. This new debug folder should have read, write and execute permissions for both PATROL Agent user and the VCS KM login user.

• The Send to Task Window option allows you to view the debug messages easily, as they occur. The window is labelled VCS KM Debug Output and appears on all connected PATROL Consoles.

WarningIf you are relying on the task window as your only output method, you should be aware that when the amount of debug data exceeds the size of the window, data will be lost from the top. To try and avoid this, set the Text Window Buffer Size to the maximum size. This setting is found in the PATROL Console menu Options => Preferences... under the tab Configuration. However, if there is an extremely high output of messages, some data may still be lost. The best way to avoid this completely is to send output to a file, as detailed above.



NoteSending debug messages to task window will require PATROL Console to be connected to the PATROL Agent during the debug data collection period.

NoteFor PATROL Central Consoles, the VCS KM Debug Output window is located in the Tasks folder under the PATROL Main Map.

Step 4 Select OK to start VCS KM debugging.

Debug data collection may take some time, depending on the complexity of your environment, frequency of the data collection, and dependency between other VCS KM data collectors. You can force the data collection as described in “Refreshing Parameters” on page 5-67.

NoteA message is sent to the PATROL Console System Output Window (SOW) when a function associated with the debug-enabled object is executed.

Step 5 To stop debugging, access the VCS KM Debug Configuration dialog again, and turn off all debug switches by clicking Off as appropriate, and click OK.

NoteThe debug switches will not be turned off automatically unless the PATROL Agent is restarted while the KM is being debugged. In this case all debug switches will be reset to Off.

WarningLeaving the debug switches turned on will impact the performance of the VCS KM and the PATROL Agent. Messages will continue to be sent to the SOW and the debug output file(s) will continue to grow until all debug switches are turned off.



Step 6 This step depends on your choice of debug output:

• If you chose to only send the output to a task window, you can save the debug output as follows:

A. Right-click in the window VCS KM Debug Output.B. Select Save As and enter a location to save the data.

• If debug output has been sent to file(s), you will be asked if you would like to prepare the debug files for sending to OTL Software. If so, the files will be compressed into a single file to allow you to email the data easily. The name and path of the compressed file is:

• vcs_km_debug_<date>_<time>.tar.Z in folder $PATROL_HOME/lib/VCS/ on Unix systems

• vcs_km_debug_<date>_<time>.zip in folder %PATROL_HOME%\lib\VCS\ on MS Windows systems

If you choose not to compress the debug files, you will be asked if you would like to retain or delete them.

NoteOn MS Windows systems, the command line version of WinZip (wzzip) is used for creating the compressed file. If this binary path is not included in the path, the compressed file will not be created.

NoteIf the compressed file (.tar.Z or .zip) is not created successfully, you can create this manually by including all files and sub-directories under $PATROL_HOME/lib/VCS/ (on Unix) or %PATROL_HOME%\lib\VCS\ (on MS Windows).

TipInstead of compressing the files, you may prefer to copy them to a secure location for viewing. Files may be compressed later for sending to OTL Software.



TipYou may want to gather output from several debug sessions. After turning off the debugging, answer No to the question for preparing the files for sending, and then choose to Retain the debug files. When you start the next debug session, you will be asked if you would like to append the output data to the existing files, or clear the folder to start the session with new debug files.

Step 7 Finally, destroy the task window as follows:

A. Right-click on the icon for VCS KM Debug Output.B. Select Destroy or Delete as appropriate for your console.



Working with Parameters

Refreshing Parameters

This section describes how to manually refresh parameters of the PATROL for Veritas Cluster Server, without waiting for an automatic polling cycle.

Forcing All Discoveries

1. Refresh the PATROL Agent process cache using the menu Refresh Process Cache from the main VCS KM container instance (labelled Veritas Cluster Server).

2. Force the discovery by selecting menu Force Discovery from the main VCS KM container instance.

NoteThese steps will also force discovery on application classes for any other KM loaded on the PATROL Agent as well as all application classes of the VCS KM.

Forcing All Data Collectors


2. All data collectors can be forced at the same time by using the menu Refresh Parameters from the main VCS KM container instance.

NoteThese steps will refresh all other data collectors defined under the various application classes loaded on the PATROL Agent as well as refreshing the VCS KM data collectors.



Forcing Selected Data Collectors

This option is only available from a PATROL Developer Console.


2. Force a data collector to execute immediately as follows:

With the PATROL Console for MS Windows

A. Right-click on the VCS KM container instance and choose Parameters without Icons...

B. Select the required data collector. C. Click Update.

With the PATROL Console for Unix

A. Right-click on the VCS KM container instance and choose Customize => Parameters...

B. Select the required data collector.C. Click on Options => Update.

Displaying ParametersEach computer icon in the PATROL main window represents an instance of a host system that PATROL is monitoring. When you add a computer to the main window, PATROL establishes a default series of application and parameter icons for monitoring.

For information on displaying a parameter output window, refer to the PATROL Console for Unix User Guide or the PATROL Console for Microsoft Windows User Guide (Volume 2).



Customizing ParametersMost parameters defined in a KM are activated by default. They continuously monitor key resources and warn of potential problems. All parameters in KMs are global parameters. This means that they automatically run on all discovered KM instances. They are the common parameters used for all applications and computers. You can customise these parameters globally or at the local level for a specific application or computer.

For information on these tasks, refer to the PATROL Console for Unix User Guide or the PATROL Console for Microsoft Windows User Guide (Volume 3).

Upgrading the PlatformIf you upgrade (or downgrade) your operating system or Veritas Cluster Server, the commands for the VCS KM need to be reloaded. Use the menu Reload Commands from the main VCS KM container instance (labelled Veritas Cluster Server).



Getting Help

DebuggingUse the menu Configuration => Debug to enable the debug switches for PATROL for Veritas Cluster Server. Refer to “Debugging the KM” on page 5-61 for more details.

KM Updates

Click here to check the latest versions of PATROL for Veritas Cluster Server from OTL Software web site.

Technical SupportBefore contacting Technical Support, please attempt to identify whether the problem is related to the operating system, Veritas Cluster Server™, BMC PATROL® or VCS KM. Refer to “Customer Support” on page iii.

If the problem appears to be related to the VCS KM, you can log a support call through:

• Web site: http://www.otl.co.nz/support• E-mail: [email protected]• Phone: +64 9 373 9120• Fax: +64 9 373 9129



http://www.otl.co.nz/products/product_info.asp?ProductName=KM-VCS&utm_source=km-vcs&utm_medium=ug


Where to Go from HereThe following table summarizes where to look for more information on using PATROL and PATROL for Veritas Cluster Server by OTL Software. The shaded rows indicate tasks that you can accomplish only from a PATROL Developer Console.


VCS KM related information and tasks

Introduction to the VCS KM “Chapter 1: Product Components and Capabilities”

System requirements for the VCS KM “Chapter 2: Preparing to Install”




Descriptions of the VCS KM menu com-mands

“Appendix A: KM Commands (Menus)”

Descriptions of the VCS KM InfoBox commands

“Appendix B: InfoBoxes”

Descriptions of VCS KM parameters “Appendix C: Parameter Definitions and Defaults”

How to troubleshoot the VCS KM “Appendix D: Troubleshooting”

PATROL related information and tasks

KMs in generalThe PATROL interfaceDefining your monitoring environmentAdding computers to PATROL

PATROL Console for Unix User Guide or PATROL Con-sole for MS Windows User Guide (Volume 1)

Working with parametersWorking with menusWorking with tasksManaging monitored objectsUnloading the KM

PATROL Console for Unix User Guide or PATROL Con-sole for MS Windows User Guide (Volume 2)

Managing events PATROL Console for Unix User Guide and PATROL Event Manager for Unix User Guideor PATROL Console for MS Windows User Guide (Vol-ume 2)

KM versions and customisation PATROL Console for Unix User Guide or PATROL Con-sole for MS Windows User Guide (Volume 3)

The PATROL Script Language (PSL) PATROL Script Language Reference Manuals





A

KM Commands (Menus) A

This appendix describes all application KM commands for PATROL® for Veritas Cluster Server™ by OTL Software.

This appendix contains the following topics:

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Menu Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3


KM Commands (Menus) A-1

OverviewThe PATROL for Veritas Cluster Server has various menus that provide an interface between the PATROL Console and the Veritas Cluster Server application. When the KM is loaded, the associated menus are added to the KM area of a menu.

NoteKM commands are also referred to as KM menu commands.


The KM area of a menu is available below the menu’s horizontal line, where commands and/or sub-menus are listed. Commands above the line belong to the console.

With the PATROL Console for MS Windows

Menus are accessed through the PATROL Console menu option KM Commands. Follow the menu tree and select the required command.

On PATROL Central Console

Menus are accessed through the PATROL Central Console menu option Knowledge Module Commands. Follow the menu tree and select the required command.

NoteThis appendix only covers the VCS KM commands. For a description of PATROL Console menu commands, refer to the appropriate PATROL user guide for your PATROL Console.

Table A-1 gives a description for all VCS KM commands for each application class. The VCS KM Online Help provides further details about these menu.

• Menus available under sub-menus Administration and Reports require a privileged user account to carry out the operation.

• An annotation point will be added to relevant parameters when executing any menus available under sub-menus Administration and Acknowledgement.


A-2 PATROL for Veritas Cluster Server by OTL Software - User Guide

Menu DescriptionsTable A-1 Menus for VCS KM

Menu Action

VCS_SERVER Application Class Label: Veritas Cluster Server

Refresh Process Cache Forces the PATROL Agent to reload its process cache from the kernel process list.

See “Refreshing Parameters” on page 5-67.

Force Discovery Forces application discovery.

See “Forcing All Discoveries” on page 5-67.

Refresh Parameters Forces an update of the application parameter values.

See “Refreshing Parameters” on page 5-67.

Reload Commands Forces a reload of commands used by VCS KM during the next full discovery cycle. By default, all new commands are reloaded automatically.

See “Upgrading the Platform” on page 5-69.

KM Status Generates a summary report containing information on the managed system and licensing limits.

See “Checking the Initial Setup of the KM” on page 4-14.

About Displays information about the product and manufacturer.

Reports Accesses the sub-menu for reporting server information.

All report menus require a user account, which will be used for executing the menu command. Note the command will fail if the user does not have privileges to execute the appropriate Veritas Cluster Server command.

Cluster Status Summary Displays Veritas Cluster Server status summary.

Administration Accesses the sub-menu for administering the server.

All administration menus require a user account, which will be used for executing the menu command. Note the command will fail if the user does not have privileges to execute the appropriate Veritas Cluster Server command. An annotation point will be added to parameter VCSNodeStatus, indicating the username and the result of the operation.See “Administering Server” on page 5-57.

Start Server Starts Veritas Cluster Server daemons on the selected system.



Stop Server Stops Veritas Cluster Server daemons on the selected system.

Configuration Accesses the sub-menu for configuring VCS KM.

License Accesses the License Configuration dialog for viewing and entering VCS KM license details.

The VCS KM will not function without a valid KM license. See “License Requirements” on page 2-13 for details about how to obtain VCS KM license keys. If the entered license details are valid, an acknowledgement will be displayed. See “Licensing the KM” on page 4-8.

Login Accesses the Login Configuration dialog for viewing and entering VCS KM login details for the operating system.

This user account should have privileges to execute Veritas Cluster Server administration commands and can use sudo privileges on Unix PATROL Agents. See “Security Requirements” on page 2-7 for more details. This user account will be used by VCS KM pre-discoveries, discoveries, data collectors, recovery actions, and InfoBoxes to execute operating system commands. It will not be used by any menus. The password is encrypted and stored on the PATROL Agent using the BMC PATROL encryption function. See “Configuring the KM User Account” on page 4-10.

Preloading Accesses the Preloading Configuration dialog, which adds or removes the KM from PATROL Agent variable “/AgentSetup/preloadedKMs”.

By preloading the VCS KM, the PATROL Agent will monitor the Veritas Cluster Server application without any PATROL Console connection. See “Configuring PATROL Agent to Preload the KM” on page 4-16.

Monitoring Mode Accesses the KM Monitoring Mode Configuration dialog, which displays and sets the KM monitoring mode on the selected managed node.

See “Customizing Monitoring Mode” on page 5-4.

Table A-1 Menus for VCS KM

Menu Action



Paths Accesses the Path Configuration dialog, which displays and sets all paths used by the VCS KM.

Paths are automatically discovered by the VCS KM server discovery. They are used as environment variables for executing various Veritas Cluster Server application commands. Altering these paths may impact the operation of the KM. KM paths are used as environment variables and internally:

• KM_HOME keeps all KM scripts.• KM_TEMP is used for creating KM temporary files.• KM_DEBUG is used for creating KM debug files.

Binary paths are used as environment variables:• $PATH (on Unix) or %PATH% (on Microsoft Windows).

Library paths are used as environment variables:• $LD_LIBRARY_PATH (on Solaris)• $SHLIB_PATH (on HP-UX)• $LIBPATH (on AIX & Linux)

For details about other Veritas Cluster Server related paths, refer to the Veritas Cluster Server Administrator’s Guide.

Node Status Accesses the Node Status Configuration dialog for viewing and modifying the daemon names monitored for node status.

The VCS KM checks for the existence of these daemons to determine the status of the node (parameter VCSNodeStatus). By default, the following daemons are sought:Daemon Descriptionhad High-availability Daemonhashadow High-availability Shadow Process

Type “[default]” to reset to the default configuration.See “Customizing Node Status” on page 5-6.


Menu Action



Instance Limits Accesses the Instance Limits Configuration dialog to view and modify the maximum number of VCS KM application instances allowed for each application class.

Following is the list of default values for maximum number of instances for each application classes:Application Name Application Class Instance

LimitAgent VCS_AGENT 50Daemon VCS_DAEMON 25System VCS_SLAVE 20Heartbeat VCS_HEARTBEAT 50GAB VCS_GAB 10LLT VCS_LLT 50Log VCS_LOG 10Group VCS_GROUP 10Group System VCS_GSYSTEM 50Resource VCS_RESOURCE 20Resource System VCS_RSYSTEM 50

To reset to the default instance limit for an application, blank out the instance limit field.See “Checking the Instance Limits” on page 4-13.

Debug Accesses the Debug Configuration dialog for enabling/disabling the VCS KM debug switches.

By default, all KM debug messages are sent to a set of files and a task window. See “Debugging the KM” on page 5-61 for more details.

VCS_AGENT_CONTAINER Application Class Label: Agents

Configuration Accesses the container level sub-menu for global configuration of agents monitored by the VCS KM.

Agents Accesses the dialog for specifying which agents are to be monitored by the VCS KM.

By default, all agents configured on the cluster are monitored. Type “[default]” to reset to the default configuration.See “Customizing Monitored Agents” on page 5-8.


Menu Action



Agents Status Accesses the global configuration for determining the agent status for monitored agent instances.

By default, the following VCSAgentState to VCSAgentStatus mapping rule is used:VCSAgentState VCSAgentStatusNot Running FailureUnknown Failureall other states Ok

Select [default] to reset to the default agent status mapping rule.See “Customizing Agent Status” on page 5-9.

VCS_AGENT Application Class Label: <Agent Name>

Reports Accesses the sub-menu for reporting agent information.


Agent Resources Lists all resources of selected agent type.

Configuration Accesses the sub-menu for configuring the selected agent instance.

Agent Accesses the individual configuration for monitoring the selected agent instance.

This dialog allows the selected agent instance to be enabled or disabled for monitoring by the VCS KM. See “Customizing Monitored Agents” on page 5-8.

Agent Status Accesses the individual configuration for determining agent status for the selected agent instance.

By default, the global VCSAgentState to VCSAgentStatus mapping rule is used, as configured at the container level. Select [default] to revert to the agent status mapping rule configured at the global/container level.See “Customizing Agent Status” on page 5-9.


Menu Action



VCS_DAEMON_CONTAINER Application Class Label: Daemons

Reports Accesses the sub-menu for reporting daemon information.


Daemon List Lists all running Veritas Cluster Server daemons.

Configuration Accesses the container level sub-menu for global configuration of daemons monitored by the VCS KM.

Daemons Accesses the dialog for specifying which daemons are to be monitored by the VCS KM.

By default, the following daemons are monitored:Daemon Description StatusCmdServer Command Server Daemon Disabledhad High-availability Daemon Enabledhashadow High-availability Shadow Process Enabled(all other daemons) Disabled

Type “[default]” to reset to the default configuration.See “Customizing Monitored Daemons” on page 5-12.

Daemons Status Accesses the global configuration for determining the daemon status for monitored daemon instances.

By default, the following VCSDaemonState to VCSDaemonStatus mapping rule is used:VCSDaemonState VCSDaemonStatusNot Running FailureNonexistent/Not Responding FailureTerminated, Stopped or Growing SuspiciousUnknown Suspiciousall other states Ok

Select [default] to reset to the default mapping rule. See “Customizing Daemon Status” on page 5-14.


Menu Action



VCS_DAEMON Application Class Label: <Daemon Name>

Configuration Accesses the sub-menu for configuring the selected daemon instance.

Daemon Accesses the individual configuration for monitoring the selected daemon instance.

This dialog allows the selected daemon instance to be enabled or disabled for monitoring by the VCS KM.See “Customizing Monitored Daemons” on page 5-12.

Daemon Status Accesses the individual configuration for determining daemon status for the selected daemon instance.

By default, the global VCSDaemonState to VCSDaemonStatus mapping rule is used, as configured at the container level. Select [default] to revert to the daemon status mapping rule configured at the global/container level. See “Customizing Daemon Status” on page 5-14 for more details.

VCS_SLAVE_CONTAINER Application Class Label: Systems

Configuration Accesses the container level sub-menu for global configuration of systems monitored by the VCS KM.

Systems Accesses the dialog for specifying which systems are to be monitored by the VCS KM.

By default, all systems configured on the cluster are monitored. Type “[default]” to reset to the default configuration.See “Customizing Monitored Systems” on page 5-16.


Menu Action



Systems Status Accesses the global configuration for determining the system status for monitored system instances.

By default, the following VCSSystemState to VCSSystemStatus mapping rule is used:VCSSystemState VCSSystemStatusCURRENT_DISCOVER_WAIT,CURRENT_PEER_WAIT,STALE_DISCOVER_WAIT,STALE_PEER_WAIT,LOCAL_BUILD, or REMOTE_BUILDfor more than 10 minutes SuspiciousADMIN_WAIT, STALE_ADMIN_WAITLEAVING, EXITING,EXITING_FORCIBLY, or EXITED SuspiciousFAULTED or UNKNOWN Failureall other states Ok

Select [default] to reset to the default system status mapping rule.See “Customizing System Status” on page 5-17.

Systems Frozen Status Accesses the global configuration for determining the system frozen status for monitored system instances.

By default, the following VCSSystemFrozenState to VCSSystemFrozenStatus mapping rule is used:VCSSystemFrozenState VCSSystemFrozenStatusTFrozen SuspiciousFrozen FailureUnknown Failureall other states Ok

Select [default] to reset to the default system frozen status mapping rule.See “Customizing System Frozen Status” on page 5-20.


Menu Action



Systems Up/Down Status Accesses the global configuration for determining the system up/down status for monitored system instances.

By default, the following VCSSystemUpDownState to VCSSystemUpDownStatus mapping rule is used:VCSSystemUpDownState VCSSystemUpDownStatusDown FailureUnknown Failureall other states Ok

Select [default] to reset to the default system up/down status mapping rule.See “Customizing System Up/Down Status” on page 5-22.

Heartbeats Status Accesses the global configuration for determining the heartbeat status for monitored heartbeat instances (configured under monitored system instances).

By default, the following VCSHeartbeatState to VCSHeartbeatStatus mapping rule is used:VCSHeartbeatState VCSHeartbeatStatusDown FailureUnknown Failureall other states Ok

Select [default] to reset to the default heartbeat status mapping rule.See “Customizing Heartbeat Status” on page 5-25.

VCS_SLAVE Application Class Label: <System Name>

Configuration Accesses the sub-menu for configuring the selected system instance.

System Accesses the individual configuration for monitoring the selected system instance.

This dialog allows the selected system instance to be enabled or disabled for monitoring by the VCS KM. See “Customizing Monitored Systems” on page 5-16.

System Status Accesses the individual configuration for determining system status for the selected system instance.

By default, the global VCSSystemState to VCSSystemStatus mapping rule is used, as configured at the container level. Select [default] to revert to the system status mapping rule configured at the global/container level.See “Customizing System Status” on page 5-17.


Menu Action



System Frozen Status Accesses the individual configuration for determining system frozen status for the selected system instance.

By default, the global VCSSystemFrozenState to VCSSystemFrozenStatus mapping rule is used, as configured at the container level. Select [default] to revert to the system frozen status mapping rule configured at the global/container level.See “Customizing System Frozen Status” on page 5-20.

System Up/Down Status Accesses the individual configuration for determining system up/down status for the selected system instance.

By default, the global VCSSystemUpDownState to VCSSystemUpDownStatus mapping rule is used, as configured at the container level. Select [default] to revert to the system up/down status mapping rule configured at the global/container level.See “Customizing System Up/Down Status” on page 5-22.

Heartbeats Accesses the dialog for specifying which heartbeats of the selected system are to be monitored by the VCS KM.

By default, all heartbeats of enabled systems are monitored. Type “[default]” to reset to the default configuration. See “Customizing Monitored Heartbeats” on page 5-24.

Heartbeats Status Accesses the configuration for determining status for the monitored heartbeat instances on the selected system instance.

By default, the global VCSHeartbeatState to VCSHeartbeatStatus mapping rule is used, as configured at the container level. Select [default] to revert to the heartbeat status mapping rule configured at the global/container level.See “Customizing Heartbeat Status” on page 5-25.

VCS_HEARTBEAT Application Class Label: <Heartbeat Name>

Configuration Accesses the sub-menu for configuring the selected heartbeat instance.

Heartbeat Accesses the individual configuration for monitoring the selected heartbeat instance.

This dialog allows the selected heartbeat instance to be enabled or disabled for monitoring by the VCS KM.See “Customizing Monitored Heartbeats” on page 5-24.


Menu Action



Heartbeat Status Accesses the individual configuration for determining the heartbeat status for the selected heartbeat instance.

By default, the VCSHeartbeatState to VCSHeartbeatStatus mapping rule configured at the parent level is used. (Note that if the mapping rule has not been modified for the parent system, then the default is the global mapping rule configured at the container level.) Select [default] to revert to the heartbeat status mapping rule configured at the parent instance level. See “Customizing Heartbeat Status” on page 5-25.

VCS_GAB_CONTAINER Application Class Label: GAB

Reports Accesses the sub-menu for reporting GAB information.


GAB Module Status Displays the status of the GAB module.

Configuration Accesses the container level sub-menu for global configuration of GABs monitored by the VCS KM.

GABs Accesses the dialog for specifying which GABs are to be monitored by the VCS KM.

By default, all GABs configured on the cluster are monitored. Type “[default]” to reset to the default configuration.See “Customizing Monitored GABs” on page 5-28.

GABs Status Accesses the global configuration for determining the GAB status for monitored GAB instances.

By default, the following VCSGabState to VCSGabStatus mapping rule is used:VCSGabState VCSGabStatusWaiting for Seed SuspiciousJeopardy FailureUnknown Failureall other states Ok

Select [default] to reset to the default GAB status mapping rule.See “Customizing GAB Status” on page 5-29.


Menu Action



VCS_GAB Application Class Label: <GAB Name>

Configuration Accesses the sub-menu for configuring the selected GAB instance.

GAB Accesses the individual configuration for monitoring the selected GAB instance.

This dialog allows the selected GAB instance to be enabled or disabled for monitoring by the VCS KM. See “Customizing Monitored GABs” on page 5-28.

GAB Status Accesses the individual configuration for determining GAB status for the selected GAB instance.

By default, the global VCSGabState to VCSGabStatus mapping rule is used, as configured at the container level. Select [default] to revert to the GAB status mapping rule configured at the global/container level.See “Customizing GAB Status” on page 5-29.

VCS_LLT_CONTAINER Application Class Label: LLT

Reports Accesses the sub-menu for reporting LLT information.


LLT Module Status Displays the status of the LLT module.

LLT Statistics Displays the statistics on the LLT module.

Configuration Accesses the container level sub-menu for global configuration of LLTs monitored by the VCS KM.

LLTs Accesses the dialog for specifying which LLTs are to be monitored by the VCS KM.

By default, all LLTs configured on the cluster are monitored. Type “[default]” to reset to the default configuration.See “Customizing Monitored LLTs” on page 5-32.


Menu Action



LLTs Status Accesses the global configuration for determining the LLT status for monitored LLT instances.

By default, the following VCSLltState to VCSLltStatus mapping rule is used:VCSLltState VCSLltStatusDown FailureUnknown Failureall other states Ok

Select [default] to reset to the default LLT status mapping rule.See “Customizing LLT Status” on page 5-33.

VCS_LLT Application Class Label: <LLT Name>

Configuration Accesses the sub-menu for configuring the selected LLT instance.

LLT Accesses the individual configuration for monitoring the selected LLT instance.

This dialog allows the selected LLT instance to be enabled or disabled for monitoring by the VCS KM. See “Customizing Monitored LLTs” on page 5-32.

LLT Status Accesses the individual configuration for determining LLT status for the selected LLT instance.

By default, the global VCSLltState to VCSLltStatus mapping rule is used, as configured at the container level. Select [default] to revert to the LLT status mapping rule configured at the global/container level.See “Customizing LLT Status” on page 5-33.


Menu Action



VCS_LOG_CONTAINER Application Class Label: Logs

Configuration Accesses the container level sub-menu for global configuration of log files monitored by the VCS KM.

Logs Accesses the dialog for specifying which log files are to be monitored by the VCS KM.

By default, the following log files are monitored. These log file paths are relative to the Veritas Cluster Server installation directory (for example /opt/VRTSvcs), unless the path is fully qualified as for the system log on Solaris and HP-UX.On Solaris:Log File Description Status/var/VRTSvcs/log/engine_A.log

VCS Engine Log Enabled/var/VRTSvcs/log/hashadow-error_A.log

Shadow Process Error Log Disabled/var/adm/messages System Log Enabled(all other logs) Enabled

On HP-UX:Log File Description Status/var/VRTSvcs/log/engine_A.log


Shadow Process Error Log Disabled/var/adm/syslog/syslog.log

System Log Enabled(all other logs) Enabled

On AIX:Log File Description Status/var/VRTSvcs/log/engine_A.log


Shadow Process Error Log Disabled(all other logs) Enabled

Type “[default]” to reset to the default configuration. See “Customizing Monitored Log Files” on page 5-36.


Menu Action



Logs Filter Accesses the global configuration of the filter for expressions used for detecting error messages in the monitored log file instances.

By default, the following “Included” expressions are looked for in each log file. If detected, the message containing the expression is added to the appropriate text parameter, unless the message also contains an “Excluded” expression for the same filter.Error Expression Set to Parameter StatusCRITICAL VCSLogAlarmText IncludedERROR VCSLogAlarmText IncludedTAG_A VCSLogAlarmText IncludedTAG_B VCSLogAlarmText IncludedTAG_C VCSLogWarningText IncludedWARNING VCSLogWarningText Included

Type “[default]” to reset to the default configuration.See “Customizing Log Error Filter” on page 5-38.

Logs Scan Limit Accesses the global configuration of the data scanning limit for monitored log file instances.

By default, the log collector only scans 5KBytes of new log data for each monitored log file during each data collection cycle. See “Customizing Monitored Log Files” on page 5-36.

Logs Alert Acknowledgement Accesses the global configuration of the method of acknowledgement for alerts on monitored log file instances.

By default, the log collector automatically acknowledges previous log alerts (warnings and alarms) when it detects new errors. See “Customizing Log Alert Acknowledgement” on page 5-41.

VCS_LOG Application Class Label: <Log Name>

Reports Accesses the sub-menu for reporting log file information.


Last Messages Displays the last messages logged in the selected log file.


Menu Action



Acknowledgement Accesses the sub-menu for acknowledging alerts on the selected log file instance.

Warnings Allows acknowledgement of warning messages detected on the selected log file instance.

This dialog allows selective acknowledgement of “suspicious” error messages detected in the log file and sent to the text parameter VCSLogWarningText. See “Acknowledging Log Alerts” on page 5-57.

Alarms Allows acknowledgement of alarm messages detected on the selected log file instance.

This dialog allows selective acknowledgement of “failure” error messages detected in the log file and sent to the text parameter VCSLogAlarmText. See “Acknowledging Log Alerts” on page 5-57.

All Allows acknowledgement of all warning and alarm messages detected on the selected log file instance.

This dialog allows acknowledgement of all error messages detected in the log file and sent to the text parameter VCSLogWarningText or VCSLogAlarmText. See “Acknowledging Log Alerts” on page 5-57.

Configuration Accesses the sub-menu for configuring the selected log file instance.

Log Accesses the individual configuration for monitoring the selected log file instance.

This dialog allows the selected log file instance to enabled or disabled for monitoring by the VCS KM. See “Customizing Monitored Log Files” on page 5-36.

Log Filter Accesses the individual configuration of the log error filter for the selected log file instance.

By default, the global log filter is used, as configured at the container level.Type “[default]” to reset to the log filter configured at the global/container level. See “Customizing Log Error Filter” on page 5-38.


Menu Action



Log Scan Limit Accesses the individual configuration of the data scanning limit for the selected log file instance.

By default, the global log file scanning limit is used, as configured at the container level. See “Customizing Monitored Log Files” on page 5-36.

Log Alert Acknowledgement Accesses the individual configuration of the method of acknowledgement for alerts on the selected log file instance.

By default, the global method of log error acknowledgement is used, as configured at the container level. See “Customizing Log Alert Acknowledgement” on page 5-41.

VCS_GROUP_CONTAINER Application Class Label: Service Groups

Reports Accesses the sub-menu for reporting service group information.


Groups Status Summary Displays the service groups status summary.

Configuration Accesses the container level sub-menu for global configuration of service groups monitored by the VCS KM.

Groups Accesses the dialog for specifying which groups are to be monitored by the VCS KM.

By default, all service groups configured on the cluster are monitored. Type “[default]” to reset to the default configuration.See “Customizing Monitored Groups” on page 5-42.


Menu Action



Groups Frozen Status Accesses the global configuration for determining the group frozen status for monitored group instances.

By default, the following VCSGroupFrozenState to VCSGroupFrozenStatus mapping rule is used:VCSGroupFrozenState VCSGroupFrozenStatusTFrozen SuspiciousFrozen FailureUnknown Failureall other states Ok

Select [default] to reset to the default group frozen status mapping rule.See “Customizing Group Frozen Status” on page 5-44.

Groups Systems Status Accesses the global configuration for determining the group system status for monitored group system instances (configured under monitored group instances).

By default, the following VCSGSystemState to VCSGSystemStatus mapping rule is used:VCSGSystemState VCSGSystemStatusONLINE* or OFFLINE* SuspiciousSTARTING or STOPPING SuspiciousPARTIAL or FAULTED FailureUnknown Failureall other states Ok

Select [default] to reset to the default group system status mapping rule.See “Customizing Group System Status” on page 5-47.

VCS_GROUP Application Class Label: <Group Name>

Reports Accesses the sub-menu for reporting service group information.


Group Dependencies Displays the dependency information about the selected service group.

Group Resources Lists all resources of selected service group.


Menu Action



Administration Accesses the sub-menu for administering the group.

All administration menus require a user account, which will be used for executing the menu command. Note the command will fail if the user does not have privileges to execute the appropriate Veritas Cluster Server command. See “Administering Service Groups” on page 5-59.

Freeze Group Freezes the selected service group. An annotation point will be added to parameter VCSGroupFrozenStatus, indicating the username and the result of the operation.

Unfreeze Group Thaws the selected service group. An annotation point will be added to parameter VCSGroupFrozenStatus, indicating the username and the result of the operation.

Configuration Accesses the sub-menu for configuring the selected group instance.

Group Accesses the individual configuration for monitoring the selected group instance.

This dialog allows the selected group instance to be enabled or disabled for monitoring by the VCS KM. See “Customizing Monitored Groups” on page 5-42.

Group Frozen Status Accesses the individual configuration for determining group frozen status for the selected group instance.

By default, the global VCSGroupFrozenState to VCSGroupFrozenStatus mapping rule is used, as configured at the container level. Select [default] to revert to the group frozen status mapping rule configured at the global/container level.See “Customizing Group Frozen Status” on page 5-44.

Group Systems Accesses the dialog for specifying which group systems of the selected group are to be monitored by the VCS KM.

By default, all group systems of enabled groups are monitored. Type “[default]” to reset to the default configuration. See “Customizing Monitored Group Systems” on page 5-46.


Menu Action



Group Systems Status Accesses the configuration for determining status for the monitored group system instances on the selected group instance.

By default, the global VCSGSystemState to VCSGSystemStatus mapping rule is used, as configured at the container level. Select [default] to revert to the group system status mapping rule configured at the global/container level.See “Customizing Group System Status” on page 5-47.

VCS_GSYSTEM Application Class Label: <Group System Name>

Configuration Accesses the sub-menu for configuring the selected group system instance.

Group System Accesses the individual configuration for monitoring the selected group system instance.

This dialog allows the selected group system instance to be enabled or disabled for monitoring by the VCS KM.See “Customizing Monitored Group Systems” on page 5-46.

Group System Status Accesses the individual configuration for determining the group system status for the selected group system instance.

By default, the VCSGSystemState to VCSGSystemStatus mapping rule configured at the parent level is used. (Note that if the mapping rule has not been modified for the parent system, then the default is the global mapping rule configured at the container level.) Select [default] to revert to the group system status mapping rule configured at the parent instance level. See “Customizing Group System Status” on page 5-47.

VCS_RESOURCE_CONTAINER Application Class Label: Resources

Reports Accesses the sub-menu for reporting resource information.


Resources Status Summary Displays the resources status summary.


Menu Action



Configuration Accesses the container level sub-menu for global configuration of resources monitored by the VCS KM.

Resources Accesses the dialog for specifying which resources are to be monitored by the VCS KM.

By default, all resources configured on the cluster are monitored. Type “[default]” to reset to the default configuration.See “Customizing Monitored Resources” on page 5-50.

Resources Systems Status Accesses the global configuration for determining the resource system status for monitored resource system instances (configured under monitored resource instances).

By default, the following VCSRSystemState to VCSRSystemStatus mapping rule is used:VCSRSystemState VCSRSystemStatusONLINE* or OFFLINE* SuspiciousSTARTING or STOPPING SuspiciousPARTIAL or FAULTED FailureUnknown Failureall other states Ok

Select [default] to reset to the default resource system status mapping rule.See “Customizing Resource System Status” on page 5-53.

VCS_RESOURCE Application Class Label: <Resource Name>

Reports Accesses the sub-menu for reporting resource information.


Resource Dependencies Displays the dependency information about the selected resource.

Configuration Accesses the sub-menu for configuring the selected resource instance.

Resource Accesses the individual configuration for monitoring the selected resource instance.

This dialog allows the selected resource instance to be enabled or disabled for monitoring by the VCS KM. See “Customizing Monitored Resources” on page 5-50.


Menu Action



Resource Systems Accesses the dialog for specifying which resource systems of the selected resource are to be monitored by the VCS KM.

By default, all resource systems of enabled resources are monitored. Type “[default]” to reset to the default configuration. See “Customizing Monitored Resource Systems” on page 5-52.

Resource Systems Status Accesses the configuration for determining status for the monitored resource system instances on the selected resource instance.

By default, the global VCSRSystemState to VCSRSystemStatus mapping rule is used, as configured at the container level. Select [default] to revert to the resource system status mapping rule configured at the global/container level.See “Customizing Resource System Status” on page 5-53.

VCS_RSYSTEM Application Class Label: <Resource System Name>

Configuration Accesses the sub-menu for configuring the selected resource system instance.

Resource System Accesses the individual configuration for monitoring the selected resource system instance.

This dialog allows the selected resource system instance to be enabled or disabled for monitoring by the VCS KM.See “Customizing Monitored Resource Systems” on page 5-52.

Resource System Status Accesses the individual configuration for determining the resource system status for the selected resource system instance.

By default, the VCSRSystemState to VCSRSystemStatus mapping rule configured at the parent level is used. (Note that if the mapping rule has not been modified for the parent system, then the default is the global mapping rule configured at the container level.) Select [default] to revert to the resource system status mapping rule configured at the parent instance level. See “Customizing Resource System Status” on page 5-53.


Menu Action



B

InfoBoxes A

This appendix describes the all InfoBox items of PATROL® for Veritas Cluster Server™ by OTL Software.

This appendix contains the following topics:

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2InfoBox Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3


InfoBoxes B-1

OverviewThe PATROL for Veritas Cluster Server uses InfoBoxes to provide attributes specific to your Veritas Cluster Server environment. InfoBoxes are tables of attributes viewable through InfoBox commands from each application class instance icon.

When a KM is loaded, all InfoBoxes associated with each application class are added to the standard list of InfoBoxes. The VCS KM uses name space variables and parameters to set InfoBoxes items. Their values are set by relevant data collector or discovery function.


InfoBoxes are accessed by clicking MB2 (middle mouse button) on the application instance.

With the PATROL Console for MS Windows and PATROL Central Consoles

InfoBoxes are accessed through the PATROL Console menu command InfoBox... This menu command can be accessed by right-clicking on the application instance.

The first items listed as standard in each InfoBox are PATROL pre-defined items. These items are not documented in this chapter. Refer to the appropriate PATROL user guide for your PATROL Console for a description of these items.

The remaining InfoBox items are VCS KM items. Table B-1 gives a description for all VCS KM InfoBox items for each application class and further detail is provided in the VCS KM Online Help.

TipWith the PATROL Console for MS Windows, the VCS KM InfoBox items are marked with a tick.On PATROL Central Console for Microsoft Windows, the VCS KM InfoBox items are marked with an icon.


B-2 PATROL for Veritas Cluster Server by OTL Software - User Guide

InfoBox DescriptionsTable B-1 InfoBox Items for VCS KM

InfoBox Item Description

VCS_SERVER Application Class Label: Veritas Cluster Server

Product Name Name of the Knowledge Module.

Product Version Version number of the Knowledge Module.

Product Release Date Release date of the Knowledge Module.

Product License Name Name of the organization/person the Knowledge Module is licensed to.

Product Serial Number Knowledge Module license serial number.

Product Host Name Host name the Knowledge Module is licensed to.

Product Authorisation Key License activation key used in the Knowledge Module license.

Product Limits Knowledge Module license limitations.

Product Options Knowledge Module license options.

Product Expiry Date Knowledge Module license expiry date.

PATROL Agent Version Version number of the PATROL Agent installed on the managed system.

Application Name Name of the application monitored by this Knowledge Module.

Application Version Monitored application version number.

VCS System(s) Names of the discovered VCS systems.

Node Name Name of the current managed system (node) as defined in Veritas Cluster Server.

Node Type Type of the node (VCS System).

Cluster Name Name of the VCS cluster.

Cluster Location Location of the VCS cluster.

Cluster Owner Owner of the VCS cluster.

Host Name Name of the host as configured on the PATROL Agent.

Platform Operating system platform as reported by the PATROL Agent (HP, SOLARIS, or RS6000).

Operating System Operating system description as reported by PATROL Agent.

Installation Path Veritas Cluster Server software installation path.


InfoBoxes B-3

Binary Path Veritas Cluster Server software binary paths used by VCS KM.

Library Path Veritas Cluster Server software library paths used by VCS KM.

Monitoring Mode Monitoring mode of the Knowledge Module.

Monitoring Node Node currently monitoring Veritas Cluster Server.

VCS_AGENT_CONTAINER Application Class Label: Agents

Collector Name Name of the data collector that sets variables and parameters under this application instance.

Collector Last Start Date & time when the last data collection cycle started.

Collector Last End Date & time at the completion of the last data collection cycle.

Collector Next Start Date & time when the next data collection cycle is expected to start.

Collector Status Data collector execution status (Idle or Running).

VCS_AGENT Application Class Label: <Agent Name>

Name Name of the Veritas Cluster Server agent.

Description Description of the Veritas Cluster Server agent.

Faults Indicates the number of agent faults.

Running Indicates whether the agent is operating.

Started Indicates whether the agent is executed by the VCS engine.

Status Current execution status of the agent (Running, Not Started or Not Running).






Table B-1 InfoBox Items for VCS KM




VCS_DAEMON_CONTAINER Application Class Label: Daemons






VCS_DAEMON Application Class Label: <Daemon Name>

Name Name of the Veritas Cluster Server daemon.

Description Description of the Veritas Cluster Server daemon.

PID Process ID of the daemon.

PPID Parent process ID of the daemon.

Owner Owner of the daemon.

Status Status of the daemon as reported in the PATROL Agent process cache.

Command Command that started the daemon.






VCS_SLAVE_CONTAINER Application Class Label: Systems









InfoBoxes B-5

VCS_SLAVE Application Class Label: <System Name>

Name Name of the Veritas Cluster Server system.

Description Description of the Veritas Cluster Server system.

Config Disk State State of the configuration on the disk when the system joined the cluster.

Disk Heartbeat State State of the communication disks on any system.

Link Heartbeat State State of the private network links on any system.

Frozen State Indicates whether the system has been frozen.

Up/Down State Indicates whether the system is up or down.

Status State of the system (SysState).

CPU Capacity Value expressing the total system load capacity.

CPU Usage Indicates the system’s CPU usage by CPU percentage utilization.

Available CPU Capacity Indicates the system’s available CPU capacity.

Dynamic Load Current dynamic load set on this system.

Engine Version Major, minor, and optional maintenance-patch and point-patch version of Veritas Cluster Server.

Node ID Node identification number assigned to this system.

System Information Platform specific information of the system.

Location Denotes the location of the system.

Owner Denotes the owner of the system.










VCS_HEARTBEAT Application Class Label: <Heartbeat Name>

Name Name of the Veritas Cluster Server disk/link heartbeat communication.

Description Description of the Veritas Cluster Server heartbeat.

Node Name of the node where the heartbeat is configured.

Status State of the heartbeat (Up or Down).






VCS_GAB_CONTAINER Application Class Label: GAB

Driver State State of the GAB module driver.

Partition Arbitration Displays whether “partition arbitration” is enabled/disabled.

Control Port Seed Displays whether “control port seed” is enabled/disabled.

Halt on Process Death Displays whether “halt on process death” is enabled/disabled.

Missed Heartbeat Halt Displays whether “missed heartbeat halt” is enabled/disabled.

Halt on Rejoin Displays whether “halt on rejoin” is enabled/disabled.

Keep on Killing Displays whether “keep on killing” is enabled/disabled.

Quorum Flag Displays whether “quorum flag” is enabled/disabled.

Restart Displays whether “restart” is enabled/disabled.

Node Count Displays the number of nodes configured in the GAB module.

Disk HB Interval Displays the disk heartbeat interval used by the GAB module.

Disk HB Miss Count Displays the number of disk heartbeat misses allowed in the GAB module.

IOFENCE Timeout Displays the IOFENCE timeout used by the GAB module.

Stable Timeout Displays the stable timeout used by the GAB module.





InfoBoxes B-7





VCS_GAB Application Class Label: <GAB Name>

Disk Disk partition used by the GAB communication.

Description Description of the GAB communication.

Port Port used by this GAB communication.

Major Major block number assigned in the disk partition for GAB communication.

Minor Minor block number assigned in the disk partition for GAB communication.

Start Start block number assigned in the disk partition for GAB communication.

Active Node IDs where this GAB communication is active.

Config Disk State State of the configuration on the disk when the system joined the cluster.

Status State of the GAB communication.






VCS_LLT_CONTAINER Application Class Label: LLT

Node ID Identification number of the node where the LLT module is monitored from.

Node Name Name of the node where the LLT module is monitored from.

Version Version number of the LLT module.

Nodes Node ID range supported by the LLT module.





Max Nodes Maximum number of nodes supported by the LLT module.

Max Ports Maximum number of ports supported by the LLT module.

Links Number of active links in the LLT module.

MTU Maximum transmission unit used by the LLT module.

Max SDU Maximum service data unit used by the LLT module.

Broadcast HB Number of broadcast heartbeats used by the LLT module.






VCS_LLT Application Class Label: <LLT Name>

Link Name of the link used by the LLT communication.

Description Description of the LLT communication.

Address MAC address used by this LLT communication.

Node Name of the node where the LLT communication is from.

Status State of the LLT communication.






VCS_LOG_CONTAINER Application Class Label: Logs







InfoBoxes B-9



VCS_LOG Application Class Label: <Log Name>

Name Name of the Veritas Cluster Server log file.

Description Description of the Veritas Cluster Server log file.

Path Full file path of the log file.

Log File Modification Time Date & time when the log file was last modified.

Log File Size File size of the log file.

Total FS Space Total space used by the file system.

Available FS Space Space available for use by the file system.

FS Percent Used Percentage of the total file system space used.

Last Purge Date & time when the log file was last purged.






VCS_GROUP_CONTAINER Application Class Label: Service Groups






VCS_GROUP Application Class Label: <Group Name>

Name Name of the Veritas Cluster Server service group.

Description Description of the Veritas Cluster Server service group.





System List List of systems where the service group is configured to run and their priorities.

Auto Start List List of systems where the service group will be started.

Online System(s) Names of the systems, where the service group is ONLINE.






VCS_GSYSTEM Application Class Label: <Group System Name>

Name Host name of the Veritas Cluster Server group system.

Description Description of the Veritas Cluster Server group system.

Group Name of the service group that the group system belongs to.

Priority Priority of the group system.

Status State of the group system.






VCS_RESOURCE_CONTAINER Application Class Label: Resources









InfoBoxes B-11

VCS_RESOURCE Application Class Label: <Resource Name>

Name Name of the Veritas Cluster Server resource.

Description Description of the Veritas Cluster Server resource.

Group Name of the service group that the resource belongs to.

Type Type of the resource.

Owner Denotes the owner of the resource.

Online System(s) Names of the systems, where the resource is ONLINE.






VCS_RSYSTEM Application Class Label: <Resource System Name>

Name Host name of the Veritas Cluster Server resource system.

Description Description of the Veritas Cluster Server resource system.

Resource Name of the resource that the resource system belongs to.

Group Name of the service group that the resource belongs to.

Priority Priority of the resource system.

IState Internal state of the resource system.

Status State of the resource system.










C

Parameter Definitions and Defaults A

This appendix presents definitions and the default values for all parameters used in PATROL® for Veritas Cluster Server™ by OTL Software.

This appendix contains following topics:

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1Parameter Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-2

OverviewThe parameters used in PATROL for Veritas Cluster Server are listed in Table C-1, grouped by application class. This information can also be accessed through the VCS KM Online Help.

The column headings and abbreviations used in Table C-1 are explained before the start of the table.

TipRefer to the appropriate PATROL user guide for your PATROL Console for additional information about the different types of parameters and their functions.


Parameter Definitions and Defaults C-1

Parameter Descriptions

Column Heading DescriptionsThe column headings used in Table C-1 are defined as follows:

Parameter States the parameter name and describes the parameter’s function.For consumer parameters, the description includes the name of the collector parameter that gathers the data displayed by this parameter.

Active at Installation

Indicates whether the parameter is active or inactive by default.

Parameter Type

Indicates the type of parameter:• Standard (Std) gathers and displays a single data value (some standards

have collector properties)• Collector (Coll) gathers multiple data values but has no display capabilities• Consumer (Con) displays values gathered by collector or standard

parameters

Border Range Specifies the default range for the parameter and level of alert triggered if outside that range. A range may be defined but marked as disabled1 by default, or the range may be undefined2.Not applicable for collector parameters, or consumer parameters with a text output.

Alarm1 Range Specifies the first alarm threshold range and the level of alert triggered. A range may be defined but marked as disabled1 by default, or the range may be undefined2.Not applicable for collector parameters, or consumer parameters with a text output.

Alarm2 Range Specifies the second alarm threshold range and the level of alert triggered. A range may be defined but marked as disabled1 by default, or the range may be undefined2.Not applicable for collector parameters, or consumer parameters with a text output.

Scheduling (poll time)

Specifies how frequently the parameter runs and collects data, in seconds (also known as the polling cycle).Not applicable for consumer parameters.

Icon Style (output)

Specifies the output style of the parameter and the icon which represents the style. Options are: graph, gauge, text, stoplight (traffic signal), state boolean, or no output.

Unit or Legend

As appropriate for the parameter:• Unit specifies the unit of measure in which the parameter output is expressed,

such as a percentage, a number, or bytes• Legend specifies possible values for the parameter and a description for each

value


C-2 PATROL for Veritas Cluster Server by OTL Software - User Guide

1 disabled For some consumer parameters, one or more of the Range columns are marked as “disabled”, although a default range is defined. You can enable the range(s) to start monitoring the parameter, and the values shown in the table will already be set (and have been tested) for the VCS KM.

2 undefined For other consumer parameters, one or more of the Range columns are marked as “undefined”, and there is no default range specified. If you decide to enable a range for such a parameter, the underlying values are not tested for the VCS KM.

In both cases, the deactivation can be viewed in the KM Parameter Properties dialog, where the Enable flag for that particular range is unticked. The underlying data for the range is visible but “greyed-out” in the Properties dialog.

AbbreviationsThe following abbreviations are used in Table C-1:

bool Boolean: shows a state, such as on or off, OK or Not OK

Coll Collector parameter

Con Consumer parameter

disc discovery; refers to the PATROL discovery process

GBytes gigabytes

KBytes kilobytes

MBytes megabytes

N no; parameter is inactive after KM is installed

NA not applicable; a value cannot be set

Std Standard parameter

TBytes terabytes

Y yes; parameter is active after KM is installed



Parameter TableTable C-1 contains a short definition and all default values for every parameter in PATROL for Veritas Cluster Server. The parameters are grouped by application class.

Table C-1 Parameters for VCS KM

Parameter

Act

ive

atIn

stal

latio

nPa

ram

eter

Type

Bor

der

Ran

ge

Ala

rm1

Ran

ge

Ala

rm2

Ran

ge

Sche

dulin

g(p

ollt

ime)

Icon

Sty

le(o

utpu

t)

Uni

tor Le

gend

VCS_SERVER Application Class Label: Veritas Cluster ServerExtraFilesListThis parameter is used for pushing VCS KM library files to the PATROL Agent during the “Commit” operation.

N Std undefined undefined undefined 600 no output

NA

VCSAgentCollectorThis parameter collects Veritas Cluster Server agent related information. It sets all consumer parameters in VCS_AGENT_CONTAINER and VCS_AGENT application classes.By default, this collector is executed only on the active system in the cluster.

Y Coll NA NA NA 600 NA NA

VCSClusterSummaryThis parameter, set by the VCS_SERVER application class discovery, summarizes the cluster information as reported in commands executed by the discovery.

Y Con NA NA NA NA text NA

VCSCreateDistributionThis parameter is automatically activated at the end of VCS KM debugging if the user chooses to “prepare debug files for sending to OTL Software”. It is deactivated on completion.

N Coll NA NA NA 300 NA NA

VCSDaemonCollectorThis parameter collects Veritas Cluster Server daemon related information. It sets all consumer parameters in VCS_DAEMON_CONTAINER and VCS_DAEMON application classes.By default, this collector is executed on all managed nodes in the cluster.


VCSGabCollectorThis parameter collects Veritas Cluster Server GAB related information. It sets all consumer parameters in VCS_GAB_CONTAINER and VCS_GAB application classes.By default, this collector is executed on all managed nodes in the cluster.


VCSGroupCollectorThis parameter collects Veritas Cluster Server service group related information. It sets all consumer parameters in VCS_GROUP_CONTAINER, VCS_GROUP and VCS_GSYSTEM application classes.By default, this collector is executed only on the active system in the cluster.




VCSLicenseStatusThis parameter monitors the status of the VCS KM license details. It is set by the VCS_SERVER application class discovery. If no valid license key is detected, this parameter will be set to “Failure” state, and any violation of license limits will set this parameter to “Suspicious” state.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.

Y Con undefined 1 to 1 warning

2 to 2 alarm

NA stop light

0 = Ok;1 = Suspicious;2 = Failure

VCSLltCollectorThis parameter collects Veritas Cluster Server LLT related information. It sets all consumer parameters in VCS_LLT_CONTAINER and VCS_LLT application classes.By default, this collector is executed on all managed nodes in the cluster.


VCSLogCollectorThis parameter collects Veritas Cluster Server log file related information. It sets all consumer parameters in VCS_LOG_CONTAINER and VCS_LOG application classes.By default, this collector is executed on all managed nodes in the cluster.


VCSLoginStatusThis parameter monitors the status of the VCS KM login details (username/password) for the operating system. It is set by VCS_SERVER application class discovery.If no valid username/password is detected for the operating system, this parameter will be set to “Failure” state. If there are any suspicious command exits, this parameter will be set to “Suspicious” state.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2 alarm

NA stop light


VCSMonitoringModeThis parameter monitors the mode of the VCS KM monitoring. It is set by VCS_SERVER application class discovery.

Y Con undefined undefined undefined NA graph 0 = Permanent Single-node Mode;

1= Temporary Single-node Mode;

2= Active Multi-node Mode;

3= Passive Multi-node Mode

-1 = Unknown


Parameter

Act

ive

atIn

stal

latio

nPa

ram

eter

Type

Bor

der

Ran

ge

Ala

rm1

Ran

ge

Ala

rm2

Ran

ge

Sche

dulin

g(p

ollt

ime)

Icon

Sty

le(o

utpu

t)

Uni

tor Le

gend



VCSNodeStatusThis parameter monitors error messages for the Veritas Cluster Server application on this managed system. It is set by VCS_SERVER application class discovery.If any of the Veritas Cluster Server application daemons is not running, this parameter will be set to “Failure” state. The list of critical Veritas Cluster Server daemons can be customized using the KM command “Configuration => Node Status” from the Veritas Cluster Server icon. If there are any suspicious command exits due to an error from the server, this parameter will be set to “Suspicious” state.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2 alarm

NA stop light


VCSRemoveTempFilesThis parameter is automatically activated if the KM temporary files cannot be removed by the PATROL Agent user. Once activated, the VCS KM will use the KM user account to remove these temporary files, and will then run every 5 minutes until the PATROL Agent is restarted.


VCSResourceCollectorThis parameter collects Veritas Cluster Server resource related information. It sets all consumer parameters in VCS_RESOURCE_CONTAINER, VCS_RESOURCE and VCS_RSYSTEM application classes.By default, this collector is executed only on the active system in the cluster.


VCSSystemCollectorThis parameter collects Veritas Cluster Server system related information. It sets all consumer parameters in VCS_SLAVE_CONTAINER, VCS_SLAVE and VCS_HEARTBEAT application classes.By default, this collector is executed only on the active system in the cluster.


VCSUpdateAgentThis parameter is used by the VCS KM to set the PATROL Agent KM variables when the PATROL Console user is not authorized to update (ACL) any PATROL Agent variables. It is activated automatically when the KM fails to update the PATROL Agent.



Parameter

Act

ive

atIn

stal

latio

nPa

ram

eter

Type

Bor

der

Ran

ge

Ala

rm1

Ran

ge

Ala

rm2

Ran

ge

Sche

dulin

g(p

ollt

ime)

Icon

Sty

le(o

utpu

t)

Uni

tor Le

gend



VCS_AGENT_CONTAINER Application Class Label: AgentsVCSAgentDetailsThis parameter, set by VCSAgentCollector, displays all data returned to the standard out from commands executed by the data collector.


VCS_AGENT Application Class Label: <Agent Name>VCSAgentFaultCountThis parameter, set by VCSAgentCollector, displays the number of the agent faults as reported in the command executed by the data collector.

Y Con undefined undefined undefined NA graph Count(-1 = Unknown)

VCSAgentStateThis parameter, set by VCSAgentCollector, displays the state of the agent as reported in the command executed by the data collector.

Y Con undefined undefined undefined NA graph 0 = Running;1 = Not Started;2 = Not Running;-1 = Unknown

VCSAgentStatusThis parameter, set by VCSAgentCollector, monitors the status of the agent. This status is determined by the agent status mapping rule defined in the KM command “Configuration => Agent(s) Status”.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.

Y Con undefined 1 to 1warning

2 to 2alarm

NA stop light


VCSAgentSummaryThis parameter, set by VCSAgentCollector, summarizes the agent information as reported in commands executed by the data collector.


VCS_DAEMON_CONTAINER Application Class Label: DaemonsVCSDaemonDetailsThis parameter, set by VCSDaemonCollector, displays all data returned to the standard out from commands executed by the data collector.


VCS_DAEMON Application Class Label: <Daemon Name>VCSDaemonCPUDurationThis parameter, set by VCSDaemonCollector, displays the CPU seconds consumed by the daemon.

Y Con undefined undefined undefined NA graph Seconds(-1 = Unknown)

VCSDaemonMemorySizeThis parameter, set by VCSDaemonCollector, displays the core image size of the daemon in the virtual memory.

Y Con undefined undefined undefined NA graph KBytes(-1 = Unknown)

VCSDaemonProcessCountThis parameter, set by VCSDaemonCollector, displays the number of processes/threads found.

Y Con undefined undefined undefined NA graph Processes(-1 = Unknown)


Parameter

Act

ive

atIn

stal

latio

nPa

ram

eter

Type

Bor

der

Ran

ge

Ala

rm1

Ran

ge

Ala

rm2

Ran

ge

Sche

dulin

g(p

ollt

ime)

Icon

Sty

le(o

utpu

t)

Uni

tor Le

gend



VCSDaemonStateThis parameter, set by VCSDaemonCollector, displays the state of the daemon as reported in the command executed by the data collector.

Y Con undefined undefined undefined NA graph 0 = Running;1 = Sleeping;2 = Waiting;3 = Queued;4 = Intermediate;5 = Terminated;6 = Stopped;7 = Growing;8 = Nonexistent/ Not Responding;9= Not Running;-1 = Unknown

VCSDaemonStatusThis parameter, set by VCSDaemonCollector, monitors the status of the daemon. This status is determined by the daemon status mapping rule defined in the KM command “Configuration => Daemon(s) Status”.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2 alarm

NA stop light


VCSDaemonSummaryThis parameter, set by VCSDaemonCollector, summarizes the daemon information as reported by commands executed by the data collector.


VCS_SLAVE_CONTAINER Application Class Label: SystemsVCSSystemDetailsThis parameter, set by VCSSystemCollector, displays all data returned to the standard out from commands executed by the data collector.


VCS_SLAVE Application Class Label: <System Name>VCSSystemCpuAvailablePercentThis parameter, set by VCSSystemCollector, monitors the percentage of available CPU on the system.If this parameter changes to warning or alarm state, the recovery action will trigger an event.

Y Con undefined -100 to 5 alarm

5 to 10 warning

NA graph %(-1 = Unknown)

VCSSystemCpuUsedPercentThis parameter, set by VCSSystemCollector, displays the percentage of CPU used by the system.

Y Con undefined undefined undefined NA graph %(-1 = Unknown)

VCSSystemFrozenStateThis parameter, set by VCSSystemCollector, displays the frozen state of the system as reported in the command executed by the data collector.

Y Con undefined undefined undefined NA graph 0 = Not Frozen;1 = TFrozen;2 = Frozen;-1 = Unknown


Parameter

Act

ive

atIn

stal

latio

nPa

ram

eter

Type

Bor

der

Ran

ge

Ala

rm1

Ran

ge

Ala

rm2

Ran

ge

Sche

dulin

g(p

ollt

ime)

Icon

Sty

le(o

utpu

t)

Uni

tor Le

gend



VCSSystemFrozenStatusThis parameter, set by VCSSystemCollector, monitors the frozen status of the system. This status is determined by the system frozen status mapping rule defined in the KM command “Configuration => System(s) Frozen Status”.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2alarm

NA stop light


VCSSystemOnlineGroupCountThis parameter, set by VCSSystemCollector, displays the number of groups that are online or about to go online on a system, as reported in the command executed by the data collector.


VCSSystemStateThis parameter, set by VCSSystemCollector, displays the state of the system as reported in the command executed by the data collector.

Y Con undefined undefined undefined NA graph 0 = INITING;1 = CURRENT_

DISCOVER_WAIT;

2 = CURRENT_PEER_WAIT;

3 = STALE_DISCOVER_WAIT;

4 = STALE_PEER_WAIT;

5 = LOCAL_BUILD;

6 = REMOTE_BUILD;

7 = RUNNING;8 = ADMIN_WAIT;9 = STALE_

ADMIN_WAIT;10 = LEAVING;11 = EXITING;12 = EXITING_

FORCIBLY;13 = EXITED;14 = FAULTED;-1 = UNKNOWN

VCSSystemStatusThis parameter, set by VCSSystemCollector, monitors the status of the system. This status is determined by the system status mapping rule defined in the KM command “Configuration => System(s) Status”.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2alarm

NA stop light


VCSSystemStoppedAgentCountThis parameter, set by VCSSystemCollector, displays the number of stopped agents on the system.



Parameter

Act

ive

atIn

stal

latio

nPa

ram

eter

Type

Bor

der

Ran

ge

Ala

rm1

Ran

ge

Ala

rm2

Ran

ge

Sche

dulin

g(p

ollt

ime)

Icon

Sty

le(o

utpu

t)

Uni

tor Le

gend



VCSSystemSummaryThis parameter, set by VCSSystemCollector, summarizes the system information as reported by commands executed by the data collector.


VCSSystemUpDownStateThis parameter, set by VCSSystemCollector, displays the up/down state of the system as reported in the command executed by the data collector.

Y Con undefined undefined undefined NA graph 0 = Down;1 = Up;-1 = Unknown

VCSSystemUpDownStatusThis parameter, set by VCSSystemCollector, monitors the up/down status of the system. This status is determined by the system up/down status mapping rule defined in the KM command “Configuration => System(s) Up/Down Status”.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2alarm

NA stop light


VCS_HEARTBEAT Application Class Label: <System Name>VCSHeartbeatStateThis parameter, set by VCSSystemCollector, displays the state of the heartbeat as reported in the command executed by the data collector.


VCSHeartbeatStatusThis parameter, set by VCSSystemCollector, monitors the status of the heartbeat. This status is determined by the heartbeat status mapping rule defined in the KM command “Configuration => Heartbeat(s) Status”.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2alarm

NA stop light


VCSHeartbeatSummaryThis parameter, set by VCSSystemCollector, summarizes the heartbeat information as reported by commands executed by the data collector.


VCS_GAB_CONTAINER Application Class Label: GABVCSGabDetailsThis parameter, set by VCSGabCollector, displays all data returned to the standard out from commands executed by the data collector.


VCSGabModuleStatusThis parameter, set by VCSGabCollector, monitors the status of the GAB module. If the GAB module is not configured or in jeopardy, this parameter will be set to “Failure” state.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2alarm

NA stop light


VCSGabModuleStatusTextThis parameter, set by VCSGabCollector, displays the GAB module status text.



Parameter

Act

ive

atIn

stal

latio

nPa

ram

eter

Type

Bor

der

Ran

ge

Ala

rm1

Ran

ge

Ala

rm2

Ran

ge

Sche

dulin

g(p

ollt

ime)

Icon

Sty

le(o

utpu

t)

Uni

tor Le

gend



VCSGabModuleSummaryThis parameter, set by VCSGabCollector, summarizes the GAB module information as reported by commands executed by the data collector.


VCSGabNodeCountThis parameter, set by VCSGabCollector, displays the number of nodes active in the GAB communication.


VCS_GAB Application Class Label: <GAB Name>VCSGabStateThis parameter, set by VCSGabCollector, displays the state of the GAB as reported in the command executed by the data collector.

Y Con undefined undefined undefined NA graph 0 = Membership;1 = Waiting for

Seed;2 = Jeopardy;-1 = Unknown

VCSGabStatusThis parameter, set by VCSGabCollector, monitors the status of the GAB. This status is determined by the GAB status mapping rule defined in the KM command “Configuration => GAB(s) Status”.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2alarm

NA stop light


VCSGabSummaryThis parameter, set by VCSGabCollector, summarizes the GAB information as reported by commands executed by the data collector.


VCS_LLT_CONTAINER Application Class Label: LLTVCSLltDetailsThis parameter, set by VCSLltCollector, displays all data returned to the standard out from commands executed by the data collector.


VCSLltLinkCountThis parameter, set by VCSLltCollector, displays the number of links active in the LLT communication.


VCSLltModuleStatusThis parameter, set by VCSLltCollector, monitors the status of the LLT module. If the LLT module is not running, this parameter will be set to “Failure” state.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2alarm

NA stop light


VCSLltModuleStatusTextThis parameter, set by VCSLltCollector, displays the LLT module status text.


VCSLltModuleSummaryThis parameter, set by VCSLltCollector, summarizes the LLT module information as reported by commands executed by the data collector.



Parameter

Act

ive

atIn

stal

latio

nPa

ram

eter

Type

Bor

der

Ran

ge

Ala

rm1

Ran

ge

Ala

rm2

Ran

ge

Sche

dulin

g(p

ollt

ime)

Icon

Sty

le(o

utpu

t)

Uni

tor Le

gend



VCSLltRcvNotConnectedPacketCountThis parameter, set by VCSLltCollector, displays the number of non-connected received packets in the LLT communication.


VCSLltRcvPacketCountThis parameter, set by VCSLltCollector, displays the number of received packets in the LLT communication.


VCSLltRcvPacketRateThis parameter, set by VCSLltCollector, displays the number of received packets per second in the LLT communication.

Y Con undefined undefined undefined NA graph Packets/second(-1 = Unknown)

VCSLltSndConnectedPacketCountThis parameter, set by VCSLltCollector, displays the number of connected sent packets in the LLT communication.


VCSLltSndNotConnectedPacketCountThis parameter, set by VCSLltCollector, displays the number of non-connected sent packets in the LLT communication.


VCSLltSndPacketCountThis parameter, set by VCSLltCollector, displays the number of sent packets in the LLT communication.


VCSLltSndPacketRateThis parameter, set by VCSLltCollector, displays the number of sent packets per second in the LLT communication.

Y Con undefined undefined undefined NA graph Packets/second(-1 = Unknown)

VCSLltStatSummaryThis parameter, set by VCSLltCollector, summarizes the LLT statistics information as reported by commands executed by the data collector.


VCS_LLT Application Class Label: <LLT Name>VCSLltStateThis parameter, set by VCSLltCollector, displays the state of the LLT as reported in the command executed by the data collector.


VCSLltStatusThis parameter, set by VCSLltCollector, monitors the status of the LLT. This status is determined by the LLT status mapping rule defined in the KM command “Configuration => LLT(s) Status”.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2alarm

NA stop light


VCSLltSummaryThis parameter, set by VCSLltCollector, summarizes the LLT information as reported by commands executed by the data collector.



Parameter

Act

ive

atIn

stal

latio

nPa

ram

eter

Type

Bor

der

Ran

ge

Ala

rm1

Ran

ge

Ala

rm2

Ran

ge

Sche

dulin

g(p

ollt

ime)

Icon

Sty

le(o

utpu

t)

Uni

tor Le

gend



VCS_LOG_CONTAINER Application Class Label: LogsVCSLogDetailsThis parameter, set by VCSLogCollector, displays all data returned to the standard out from commands executed by the data collector.


VCS_LOG Application Class Label: <Log Name>VCSLogAlarmCountThis parameter, set by VCSLogCollector, monitors the number of alarm messages set in the parameter VCSLogAlarmText.If this parameter changes to alarm state, the recovery action will trigger an event.

Y Con 0 to 100 alarm

1 to 100 alarm

undefined NA graph Count(-1 = Unknown)

VCSLogAlarmTextThis parameter, set by VCSLogCollector, displays all alarm messages in the log file which have not been acknowledged. The filter used by the data collector to determine alarm messages can be customized using the menu “Configuration => Log(s) Filter”.These alarm messages can be acknowledged automatically (default) or manually, depending on the configuration in the menu “Configuration => Log(s) Alert Acknowledgement”. Manual acknowledgement is available under the KM sub-menu “Acknowledgement”.


VCSLogFSSpaceUsedPercentThis parameter, set by VCSLogCollector, monitors the percentage of space used by the file system (where the log file resides).If this parameter changes to warning or alarm state, the recovery action will trigger an event.


95 to 98 warning

98 to 100 alarm


VCSLogSpaceAvailableThis parameter, set by VCSLogCollector, monitors the available space for the log file to use (this is also the available space on the file system).If this parameter changes to warning or alarm state, the recovery action will trigger an event.

Y Con undefined -1 to 2 alarm

2 to 5 warning

NA graph MBytes(-1 = Unknown)

VCSLogSpaceGrowthRateThis parameter, set by VCSLogCollector, displays the growth rate of the amount of space used by the log file.

Y Con undefined undefined undefined NA graph KBytes/second(-1 = Unknown)

VCSLogSpaceUsedThis parameter, set by VCSLogCollector, displays the amount of space used by the log file.

Y Con undefined undefined undefined NA graph KBytes(-1 = Unknown)

VCSLogSpaceUsedPercentThis parameter, set by VCSLogCollector, monitors the percentage of capacity used by the log file.If this parameter changes to warning or alarm state, the recovery action will trigger an event.Note that the total capacity is the used space (VCSLogSpaceUsed) plus available space (VCSLogSpaceAvailable).


95 to 98 warning

98 to 100 alarm



Parameter

Act

ive

atIn

stal

latio

nPa

ram

eter

Type

Bor

der

Ran

ge

Ala

rm1

Ran

ge

Ala

rm2

Ran

ge

Sche

dulin

g(p

ollt

ime)

Icon

Sty

le(o

utpu

t)

Uni

tor Le

gend



VCSLogSummaryThis parameter, set by VCSLogCollector, summarizes the log file information as reported by commands executed by the data collector.


VCSLogTextThis parameter, set by VCSLogCollector, displays all log text scanned by the data collector during the last collection cycle. The size of the data scanned by the data collector is configured in the menu “Configuration => Log(s) Scan Limit”.


VCSLogWarningCountThis parameter, set by VCSLogCollector, monitors the number warning messages set in the parameter VCSLogWarningText.If this parameter changes to a warning state, the recovery action will trigger an event.

Y Con 0 to 100 warning

1 to 100 warning


VCSLogWarningTextThis parameter, set by VCSLogCollector, displays all warning messages in the log file which have not been acknowledged. The filter used by the data collector to determine warning messages can be customized using the menu “Configuration => Log(s) Filter”.These warning messages can be acknowledged automatically (default) or manually, depending on the configuration in the menu “Configuration => Log(s) Alert Acknowledgement”. Manual acknowledgement is available under the KM sub-menu “Acknowledgement”.


VCS_GROUP_CONTAINER Application Class Label: Service GroupsVCSGroupDetailsThis parameter, set by VCSGroupCollector, displays all data returned to the standard out from commands executed by the data collector.


VCS_GROUP Application Class Label: <Group Name>VCSGroupFailoverStatusThis parameter, set by VCSGroupCollector, monitors the failover status of the group.If the VCS system(s) where this service group is ONLINE differs between the current and previous collection cycles, this parameter will be set to “Suspicious” state. If there is no ONLINE system found for this service group, it will be set to “Failure” state.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2 alarm

NA stop light


VCSGroupFaultSystemCountThis parameter, set by VCSGroupCollector, displays the number of systems where this service group is in FAULTED state.


VCSGroupFrozenStateThis parameter, set by VCSGroupCollector, displays the frozen state of the service group as reported in the command executed by the data collector.

Y Con undefined undefined undefined NA graph 0 = Not Frozen;1 = TFrozen;2 = Frozen;-1 = Unknown


Parameter

Act

ive

atIn

stal

latio

nPa

ram

eter

Type

Bor

der

Ran

ge

Ala

rm1

Ran

ge

Ala

rm2

Ran

ge

Sche

dulin

g(p

ollt

ime)

Icon

Sty

le(o

utpu

t)

Uni

tor Le

gend



VCSGroupFrozenStatusThis parameter, set by VCSGroupCollector, monitors the frozen status of the service group. This status is determined by the service group frozen status mapping rule defined in the KM command “Configuration => Group(s) Frozen Status”.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2alarm

NA stop light


VCSGroupOfflineSystemCountThis parameter, set by VCSGroupCollector, displays the number of systems where this service group is in OFFLINE state.


VCSGroupOnlineSystemCountThis parameter, set by VCSGroupCollector, displays the number of systems where this service group is in ONLINE state.If this parameter changes to alarm state, the recovery action will trigger an event.

Y Con undefined -1 to 0alarm


VCSGroupPartialSystemCountThis parameter, set by VCSGroupCollector, displays the number of systems where this service group is in PARTIAL state.


VCSGroupSummaryThis parameter, set by VCSGroupCollector, summarizes the service group information as reported by commands executed by the data collector.


VCS_GSYSTEM Application Class Label: <Group System Name>VCSGSystemPendingProbeCountThis parameter, set by VCSGroupCollector, displays the number of pending probes for this group system.

Y Con 0 to 100 warning

1 to 100 warning


VCSGSystemStateThis parameter, set by VCSGroupCollector, displays the state of the group system as reported in the command executed by the data collector.Note: ONLINE* and OFFLINE* states represent all other ONLINE and OFFLINE states with a secondary state respectively.

Y Con undefined undefined undefined NA graph 0 = ONLINE;1= ONLINE*;2= OFFLINE;3= OFFLINE*;4= STARTING;5= STOPPING;6= PARTIAL;7= FAULTED;-1 = UNKNOWN

VCSGSystemStatusThis parameter, set by VCSGroupCollector, monitors the status of the group system. This status is determined by the group system status mapping rule defined in the KM command “Configuration => Group(s) System(s) Status”.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2alarm

NA stop light



Parameter

Act

ive

atIn

stal

latio

nPa

ram

eter

Type

Bor

der

Ran

ge

Ala

rm1

Ran

ge

Ala

rm2

Ran

ge

Sche

dulin

g(p

ollt

ime)

Icon

Sty

le(o

utpu

t)

Uni

tor Le

gend



VCSGSystemSummaryThis parameter, set by VCSGroupCollector, summarizes the group system information as reported by commands executed by the data collector.


VCS_RESOURCE_CONTAINER Application Class Label: ResourcesVCSResourceDetailsThis parameter, set by VCSResourceCollector, displays all data returned to the standard out from commands executed by the data collector.


VCS_RESOURCE Application Class Label: <Resource Name>VCSResourceFailoverStatusThis parameter, set by VCSResourceCollector, monitors the failover status of the resource.If the VCS system(s) where this resource is ONLINE differs between the current and previous collection cycles, this parameter will be set to “Suspicious” state. If there is no ONLINE system found for this resource, it will be set to “Failure” state.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2 alarm

NA stop light


VCSResourceFaultSystemCountThis parameter, set by VCSResourceCollector, displays the number of systems where this resource is in FAULTED state.


VCSResourceOfflineSystemCountThis parameter, set by VCSResourceCollector, displays the number of systems where this resource is in OFFLINE state.


VCSResourceOnlineSystemCountThis parameter, set by VCSResourceCollector, displays the number of systems where this resource is in ONLINE state.If this parameter changes to alarm state, the recovery action will trigger an event.

Y Con undefined -1 to 0alarm


VCSResourcePartialSystemCountThis parameter, set by VCSResourceCollector, displays the number of systems where this resource is in PARTIAL state.


VCSResourceSummaryThis parameter, set by VCSResourceCollector, summarizes the resource information as reported by commands executed by the data collector.



Parameter

Act

ive

atIn

stal

latio

nPa

ram

eter

Type

Bor

der

Ran

ge

Ala

rm1

Ran

ge

Ala

rm2

Ran

ge

Sche

dulin

g(p

ollt

ime)

Icon

Sty

le(o

utpu

t)

Uni

tor Le

gend



VCS_RSYSTEM Application Class Label: <Resource System Name>VCSRSystemStateThis parameter, set by VCSResourceCollector, displays the state of the resource system as reported in the command executed by the data collector.Note: ONLINE* and OFFLINE* states represent all other ONLINE and OFFLINE states with a secondary state respectively.

Y Con undefined undefined undefined NA graph 0 = ONLINE;1= ONLINE*;2= OFFLINE;3= OFFLINE*;4= STARTING;5= STOPPING;6= PARTIAL;7= FAULTED;-1 = UNKNOWN

VCSRSystemStatusThis parameter, set by VCSResourceCollector, monitors the status of the resource system. This status is determined by the resource system status mapping rule defined in the KM command “Configuration => Resource(s) System(s) Status”.If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.


2 to 2alarm

NA stop light


VCSRSystemSummaryThis parameter, set by VCSResourceCollector, summarizes the resource system information as reported by commands executed by the data collector.



Parameter

Act

ive

atIn

stal

latio

nPa

ram

eter

Type

Bor

der

Ran

ge

Ala

rm1

Ran

ge

Ala

rm2

Ran

ge

Sche

dulin

g(p

ollt

ime)

Icon

Sty

le(o

utpu

t)

Uni

tor Le

gend





D

Troubleshooting A

This appendix provides troubleshooting information for problems you may encounter while using PATROL® for Veritas Cluster Server™ by OTL Software.

This appendix contains following topics:

Troubleshooting Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2


Troubleshooting D-1

Troubleshooting InformationRefer to the Table D-1 on page D-3 to diagnose any problems you may encounter when installing or running the PATROL for Veritas Cluster Server.

TipFor any problem, look for error messages on the PATROL Console System Output Window (SOW). Most error messages are self-explanatory.

TipMost KM problems are reported in the KM Status Report, which can be viewed by selecting the menu KM Status from the Veritas Cluster Server or VCS_SETUP icon. Run this report to diagnose any problems.

TipThe VCS KM triggers PEM events for most severe problems. Each event triggered from the KM includes an Expert Advice, which provides details about the problem and some suggestions to resolve it.


D-2 PATROL for Veritas Cluster Server by OTL Software - User Guide

Table D-1 Common Problems and Resolutions

Problem Possible Resolution

Unable to find VCS_LOAD.kml

Check that the Load KM browser is looking for *.kml files under PATROL_HOME/lib/knowledge folder.

PATROL for Veritas Cluster Server files have not been installed correctly under the PATROL installation directory on the PATROL Console.

VCS_SETUP icon does not appear after loading

Check whether this managed node is a supported Veritas Cluster Server node, and it is configured properly.

Check that the version of Veritas Cluster Server is supported by the PATROL for Veritas Cluster Server.

Check that there is no KM version mismatch between the PATROL Console and the PATROL Agent. Check the messages in the PATROL Console SOW to verify this.

Check whether the PATROL Agent tuning variable, “/AgentSetup/AgentTuning/pslInstructionMax” has been increased as suggested in “Changes to BMC PATROL” on page 2-5. Check the messages in the PATROL Console SOW.

Check whether the PATROL Agent user has necessary privileges added in the Agent’s Access Control List (/AgentSetup/accessControlList) in order to read and write to the Agent Configuration Database.

VCS_SETUP icon does not change to Veritas Cluster Server

If the license details are invalid, the parameter VCSLicenseStatus should appear in “failure” state. VCS KM license details should be entered exactly as supplied. Note that it is case-sensitive, and ensure there are no additional characters or spaces in the key. Also ensure the license key has not expired by checking the value of InfoBox item “Product Expiry Date”.

Check that the VCS KM license details are entered correctly, using the menu Configuration => License from the VCS_SETUP icon.

If the login details are invalid, the parameter VCSLoginStatus should appear in “failure” state.

Check the operating system login details using the KM command Configuration => Login from the VCS_SETUP icon.


Troubleshooting D-3

Parameter VCSLoginStatus is in suspicious (warning) status

This parameter will also show a “suspicious” state if any command executed by VCS KM fails.

Check the annotation point on the first state change data point of this parameter to look for any failing commands. If an annotation point cannot be found, or if it is not up-to-date, check the KM Status Report, which can be viewed by selecting the menu KM Status from the Veritas Cluster Server icon. These errors are produced from the Veritas Cluster Server commands executed by the VCS KM.

Check that the operating system user configured in the KM command Configuration => Login can execute all Veritas Cluster Server commands and access the Veritas Cluster Server files.

KM is operating on a passive node

Check whether the InfoBox item “Monitoring Mode” from the Veritas Cluster Server icon reads “Passive Multi-node Mode”. If it reads “Temporary Single-node Mode” the KM is either unable to find an active system (either a master system or an online node for the default ClusterService service group or a configured service group) or the PATROL Agent on the active node is not responding. If the above InfoBox item reads “Permanent Single-node Mode”, the KM is not configured to operate in “Multi-node Mode”. Please check the configuration, using the menu Configuration => Monitoring Mode.

Check whether the VCS KM has been active on this node and has failed over to another managed node. When a failover occurs, the shared instances created on the previous active node, will be destroyed, unless the pconfig variable, /VCS/DestroyInstances, is set to false. To change this back to the default, use the following PSL through PATROL Console:%PSL pconfig("DELETE","/VCS/DestroyInstances");





All/some KM objects disappear from the Console

Check whether there is a KM version mismatch between the PATROL Console and the PATROL Agent, possibly after an improper upgrade of the KM. Check the messages in the PATROL Console SOW to verify this.

Check that the VCS KM login details are still valid. Has the password changed on the system? Look for any error messages on the SOW, and check for additional information in the last annotation point for parameter VCSLoginStatus.

Check whether the VCS KM has failed over to another managed node. In Multi-node Mode, when the KM fails over, the shared instances created on the previous active node, will be destroyed by defaults. This behavior can be changed by setting the pconfig variable, /VCS/DestroyInstances, is set to false. This can be achieved, using following PSL through PATROL Console:%PSL pconfig("REPLACE","/VCS/DestroyInstances", false);

All/some VCS KM application instances do not appear

Check that the KM instance limits have not been exceeded. Look for any error messages on the SOW, and increase the instance limits for affected objects using the menu Configuration => Instance Limits.

Check the messages in the PATROL Console SOW for suggestions for the new limit. These errors are also displayed in the KM Status Report, which can be viewed by selecting the menu KM Status from the Veritas Cluster Server icon.

Check that the KM license limits have not been exceeded. Look for any error messages on the SOW, and check for additional information in the last annotation point for parameter VCSLicenseStatus. These errors are also displayed in the KM Status Report.

Check whether the KM is monitoring in passive mode. In Multi-node Mode, VCS KM operates in full monitoring mode, only from the node where the KM is in active mode. If that is not desirable, the KM can be configured to operate in Single-node Mode, using the menu Configuration => Monitoring Mode.




Troubleshooting D-5

Behavior of the VCS KM has not changed in accordance with the Release Notes after a KM upgrade

Check the version of the KM from the main InfoBox. If it has not changed, then the installation is not complete. Make sure both the PATROL Console and the PATROL Agent are uninstalled and installed correctly during the KM upgrade.

VCS KM takes a long time to refresh the parameters and application classes on the PATROL Console

Data collectors run according to their scheduling interval (polling cycle) defined in the KM. These intervals are defined for a standard environment with minimal resource impact. These intervals can be customized from the PATROL Developer Console to suit your environment. Refer to the PATROL Console User Guide for more details.





Poor performance of the Veritas Cluster Server server after installing the KM

This happens if the VCS KM is installed on a heavily used system. Depending on the complexity of your Veritas Cluster Server environment, the VCS KM may consume more resources to interrogate the application and process the data. In such a complex environment, the VCS KM may require some fine tuning to optimize the available resources. Consider the following options:

— Disable monitoring of unnecessary application instances. This can be achieved by using the appropriate menu Configuration => <Component(s)>.

— Increase the scheduling interval (polling cycle) for data collectors.

— Deactivate unnecessary data collectors and associated application classes.

— Deactivate unnecessary data collectors during selected time intervals, where there are no Veritas Cluster Server activity. For example, if the service group monitoring can be disabled between 6 pm and 6 am during weekday and whole day during weekends, then disable group collector (VCSGroupCollector) during this period, using following PSL through PATROL Console:

%PSL pconfig("REPLACE","/VCS/VCSGroupCollectorMode", "1|21600|64800|0|0|||||||||||0|0");

Here the pconfig variable is named as: <collector name>Mode. The value contains following details, delimited by pipe (|):enabled (1)/disabled (0) data collection, default start/end times in number of seconds since midnight, start/end times for non-default days starting from Sunday through to Saturday.

— Purge unnecessary information in Veritas Cluster Server log files.

— If there are too many group systems, resources or resource systems in the cluster, the VCSGroupCollector and VCSResourceCollector may affect the overall performance. In such environment set their instance limits to 0 (zero), using menu Configuration => Instance Limits to disable monitoring those components.

Also refer to “Infinite Loop Errors” for a possible PATROL internal scheduling delay which may impact the performance of the KM.




Troubleshooting D-7

Infinite Loop Errors

(Error messages on the SOW reporting that some VCS KM data collectors may be in an infinite loop)

Check the setting of the tuning variable /AgentSetup/AgentTuning/pslInstructionMax.

PATROL Agent uses the pre-configured tuning variable (/AgentSetup/AgentTuning/pslInstructionMax) to stop running PSL functions in an infinite loop. When a PSL function reaches this maximum threshold, it reports this error, and puts the execution of this function to the back of the process queue. This will not only delay the data collector, it will also impact the performance of the system.

To resolve this situation, the maximum number of instructions should be increased to an optimum value. This depends on the complexity of your environment. It is required that the default value of 500,000 should be increased to at least 5,000,000 on a standard Veritas Cluster Server environment to enable the VCS KM data collectors to execute without impacting your system.

If this still does not resolve the problem, you can disable this functionality by setting the value of the tuning variable to zero.

Unable to turn on the KM Debug

If you are unable to turn on the KM Debug following the method described in “Debugging the KM” on page 5-61, you turn the debug on by setting appropriate PATROL Agent configuration variable with a timestamp value. This timestamp value determines when the debug should be turned off. For example, to turn on the debug for 60 minutes from now, run the following PSL through PATROL Console:%PSL pconfig("REPLACE","/VCS/<Component>Debug",

time()+3600);

Where <Component> is either Server for debugging the server discovery or name of the collector component followed by “Collector”, like DaemonCollector for debugging daemon collector.





Glossary

Glossary

agent (1) A process that starts, stops, and monitors all configured resources of a type, and reports to Veritas Cluster Server.

(2) See “PATROL Agent”

application class The object class to which an application instance belongs; also, the representation of the object class as a container (Unix) or folder (MS Windows) on the PATROL Console. You can use a PATROL Developer Console to add or change application classes.

application instance A system resource discovered by PATROL. An application instance contains the information and attributes of the application class to which it belongs. See also “application class”.

cluster Defines a group of computers linked together for the purpose of multiprocessing and high availability.

component A term used by PATROL for Veritas Cluster Server; a component is a subset of an object to group hierarchically dependent Veritas Cluster Server entities.

container instance PATROL for Veritas Cluster Server uses container application instances as parent instances, where it places related application instances together.


Glossary 1

daemon One of the executing daemons or processes required by Veritas Cluster Server to function.

data collector A data collector is a PATROL for Veritas Cluster Server collector parameter, which collects the information from Veritas Cluster Server and sets various consumer parameters under different application classes.

discovery A PATROL Agent procedure carried out at preset intervals on each monitored computer to discover supported Veritas Cluster Server installations.

entity A term used by PATROL for Veritas Cluster Server: a functionality/item of Veritas Cluster Server monitored by the KM, such as groups, resources, systems.

event See “event trigger”

event trigger The information sent to PATROL Enterprise Manager through a recovery action, when a parameter reaches a specified threshold.

failover A failover occurs when a service group faults and migrated to another system.

file system An organized structure in an operating system consisting of files and directories.

filter A filter is a set of rules used by PATROL for Veritas Cluster Server to channel required information to another parameter. An example for a filter is where certain regular expressions are sought by the log data collector to monitor critical errors in a log file.

GAB Group Atomic Broadcast (GAB) is a communication mechanism used by VCS engine that manages cluster membership, monitors heartbeat communication, and distributes information throughout the cluster.

group system A system/node which is a member of a service group.


2 PATROL for Veritas Cluster Server by OTL Software - User Guide

host In TCP/IP, a host is any system that has at least one Internet address associated with it. A host with multiple network interfaces may have multiple Internet addresses associated with it.

KM See “PATROL Knowledge Module”.

KM tree See “PATROL KM tree”.

Knowledge Module See “PATROL Knowledge Module”.

LLT Low Latency Transport (LLT) is a communication mechanism used by VCS engine that provides kernel-to-kernel communications and monitors network communications.

load PATROL KMs To place PATROL KM files into memory for execution. After configuration and during startup, the PATROL Agent loads the PATROL KM files that are listed in its configuration file and that reside on the PATROL Agent computer. When a PATROL Console connects to a PATROL Agent, the PATROL KM versions that the Agent executes depend on whether the console is a PATROL Operator Console or a PATROL Developer Console. See also “PATROL Knowledge Module”.

managed node Any server that is managed by PATROL. PATROL Agent will execute on each managed node.

managed system See “managed node”.

object A term used by PATROL for Veritas Cluster Server; an object groups monitored Veritas Cluster Server components.


Glossary 3

parameter A monitoring or display component of PATROL, run by the PATROL Agent. A parameter periodically uses data collection commands to obtain data on a system resource and then parses, processes, and stores that data on the computer running the PATROL Agent. Parameter data can be accessed from a PATROL Console or SNMP console. Parameters have thresholds and trigger alerts (warnings or alarms). If the value returned by a parameter triggers an alert, the PATROL Agent notifies the PATROL Console and runs any recovery actions associated with the parameter.

parameter state The condition of a parameter. The most common parameter states are “OK”, “Warning” or “Alarm”. The icon of a parameter can show additional information about the parameter’s state, including “no history”, “offline”, “snoozed” or “suspended”. A parameter can be deactivated; in this case, no icon is displayed. See also “state change”.

PATROL Agent The core component of PATROL architecture. The PATROL Agent monitors and manages host computers. The PATROL Agent can communicate with the PATROL Console, a standalone event manager, and SNMP consoles.

PATROL Central Consoles

PATROL Central Consoles introduced in PATROL version 7.x infrastructure. This includes PATROL Central Operator - Microsoft Windows edition and PATROL Central Operator - Web edition.

PATROL Classic Consoles

PATROL Consoles introduced in PATROL version 3.x infrastructure. This includes PATROL Operator Console and PATROL Developer Console (both consoles available for Unix or Microsoft Windows).

PATROL Developer Console

The graphical user interface to PATROL that administrators can use to monitor and manage computer instances and application instances, and to customise, create, and delete locally loaded PATROL Knowledge Modules and commit these changes to selected PATROL Agent computers.



PATROL KM tree (Only on PATROL for MS Windows)One of two views of folders available in MS Windows. The PATROL KM tree displays computer classes, application classes, and their customized instances in the knowledge hierarchy and also displays the Standard Event Catalog. From the PATROL Operator Console, the PATROL KM tree can be viewed but not changed. PATROL KM properties and attributes can only be changed from the PATROL Developer Console.

PATROL Knowledge Module

A set of files from which a PATROL Agent receives information about resources running on a monitored computer. A file can contain the actual instructions for monitoring objects or simply a list of PATROL KMs to load. PATROL KMs are loaded by a PATROL Console.

PATROL Operator Console

The graphical user interface to PATROL that operators can use to monitor computer instances and application instances (but not to customize or create PATROL KMs, commands or parameters).

resource Defines a component/resource for providing a service to the public network.

resource system A system/node which is a member of a resource.

service group Defines a collection of resources working together to provide application services to clients.

state change A change in the state of an object monitored by PATROL, to or from a state of “OK”, “Warning”, or “Alarm”, or a change in the state of an object from “online” to “offline”. See also “parameter state”.

status mapping rule A rule used by PATROL for Veritas Cluster Server to translate the value of a state parameter for a KM object to a 3-value status parameter. The status parameter will then trigger alerts accordingly.

system A physical host/system on which applications and service groups reside, and part of the cluster.


Glossary 5

threshold A defined range of values, outside of which a parameter is considered to be in a suspicious or failure state.



Index

Index

Numerics22198

TableTitleWideTable 1-3 Accessing Online Help for

VCS KM 1-13

AaccessControlList 2-6Acknowledgement

Alarms 5-58All 5-58Warnings 5-58

ACL 2-6Administration

Freeze Group 5-59Start Server 5-57Stop Server 5-57Unfreeze Group 5-59

Agent Statuscustomizing 5-9mapping rule 5-9

Agentscontainer instance 1-6customizing 5-8debugging 5-62

BMC Software, Inc., Confidential and Proprietary Information

instances 1-6monitoring overview 1-4

application classes 1-6

Cchild application class 1-6Cluster

debugging 5-62component 1-6Configuration

Agent(s) 5-8Agent(s) Status 5-10Daemon(s) 5-13Daemon(s) Status 5-15Debug 5-61GAB(s) 5-28, 5-32GAB(s) Status 5-31Group System(s) 5-46Group(s) 5-42Group(s) Frozen Status 5-45Group(s) System(s) Status 5-48Heartbeat(s) 5-24Heartbeat(s) Status 5-26Heartbeats) 5-24Instance Limits 4-13License 4-8

Index 1

LLT(s) Status 5-34Log(s) 5-36Log(s) Alert Acknowledgement 5-41Log(s) Filter 5-40Log(s) Scan Limit 5-38Login 4-10Monitoring Mode 4-12, 5-4Node Status 5-7Preloading 4-16Resource System(s) 5-52Resource(s) 5-50Resource(s) System(s) Status 5-54System(s) 5-16System(s) Frozen Status 5-21, 5-23System(s) Status 5-18

CPU usage 1-14

DDaemon Status

customizing 5-14mapping rule 5-14

Daemonscontainer instance 1-6customizing 5-12debugging 5-62instances 1-6monitoring overview 1-4

Data Collectorsforcing all 5-67forcing selected 5-68

debug folder 5-63debug output 5-63debugging 5-61

collector parameters 5-62discovery 5-62InfoBoxes 5-62KM commands 5-62menus 5-62pre-discovery 5-62

recovery actions 5-62VCS_SERVER discovery 5-62VCSAgentCollector collector 5-62VCSCreateDistribution collector 5-62VCSDaemonCollector collector 5-62VCSGabCollector collector 5-62VCSGroupCollector collector 5-62VCSLltCollector collector 5-62VCSLogCollector collector 5-62VCSRemoveTempFiles collector 5-62VCSResourceCollector collector 5-62VCSSystemCollector collector 5-62VCSUpdateAgent collector 5-62

discoveryforcing all 5-67verifying 4-11

distribution file for installation utility, contents 3-5

distribution file, contents 3-6distribution server files 3-5

Eexecutable files, permissions 2-8

Ffilters

log error 5-38node status 5-6

Force Discovery 4-12, 5-67Full Discovery 4-11

GGAB

container instance 1-7customizing 5-28


2 PATROL® Knowledge Module® for VERITAS Cluster Server™ by OTL Software - User Guide

debugging 5-62instances 1-7KM command 5-28

GAB Statuscustomizing 5-29mapping rule 5-29

Group Frozen Statuscustomizing 5-44

Group System Statuscustomizing 5-47mapping rule 5-47

Group Systemscustomizing 5-46instances 1-7KM command 5-46monitoring overview 1-5

Groupsadministering 5-59container instance 1-7customizing 5-42instances 1-7KM command 5-42monitoring overview 1-5

HHeartbeat Status

customizing 5-25mapping rule 5-25

Heartbeatscustomizing 5-24instances 1-7monitoring overview 1-4

hierarchical structure 1-9history data 2-12

Iicons for application classes 1-6

InfoBoxesaccessing 1-11

installationBPPM Portal 3-5checklist 2-2files 3-5, 3-6guidelines 3-3MS Windows platform 3-8PAR File 3-9Unix platform 3-7workflow 3-2

Installation Utility 3-5instance limits 4-14

KKM Commands

Accessing 1-11Acknowledgement 5-56Administration 5-56KM Status 4-14Reports 5-60

KM Status report 4-15KM versions 5-70

Llibrary files, permissions 2-8Licensing the KM 4-8LLT

container instance 1-7customizing 5-32debugging 5-62instances 1-7KM command 5-32

LLT Statuscustomizing 5-33mapping rule 5-33

Loading


Index 3

BPPM 4-6PATROL Agent 4-16PATROL Central 4-4PATROL Console 4-2

Log Alertscustomizing acknowledgement method

5-41Log Error Filter

customizing 5-38Log Errors

acknowledging 5-57log scan limit 5-38login details 4-10Logs

container instance 1-7customizing 5-36debugging 5-62instances 1-7KM command 5-36monitoring overview 1-5

Mmapping rule

agent status 5-9daemon status 5-14GAB status 5-29group frozen status 5-44group system status 5-47heartbeat status 5-25LLT status 5-33resource system status 5-53system frozen status 5-20system status 5-17system up/down status 5-22

memory usage 1-14Menus

Configuration 5-3Multi-node Mode 4-12

Nnetwork traffic 1-15Node Status

customizing 5-6

Oobject 1-6Online Help

accessing 1-12Printing 1-13

Pparent application class 1-6PATROL Agent configuration variables,

deleting 3-15preferences

PATROL Options 5-63preloaded KMs 4-16Printing 1-13pslInstructionMax 2-5, 4-2

Rrecovery 1-2recovery actions 5-6Refresh Parameters 5-67Refresh Process Cache 5-67release notes 3-6Reload Commands 5-69Reports

Cluster Status Summary 5-60Daemon List 5-60GAB Module Status 5-60Group Dependencies 5-60Group Resources 5-60



Groups Status Summary 5-60Last Messages 5-60LLT Module Status 5-60Resource Dependencies 5-60Resources Status Summary 5-60

requirementsBMC PATROL 2-4BMC Portal 2-4disk space 2-12operating system 2-3sudo 2-6Veritas Cluster Server 2-4

Resource System Statuscustomizing 5-53mapping rule 5-53

Resource Systemscustomizing 5-52instances 1-8KM command 5-52monitoring overview 1-5

Resourcescontainer instance 1-8customizing 5-50instances 1-8KM command 5-50monitoring overview 1-5

SServer 1-6

administering 5-57debugging 5-62monitoring overview 1-3

setup instance 4-3, 4-5setup menu 4-7Single-node Mode 4-12sudo privileges 2-7, 2-10System Frozen Status

customizing 5-20mapping rule 5-20, 5-44

System Statuscustomizing 5-17mapping rule 5-17

System Up/Down Statuscustomizing 5-22mapping rule 5-22

Systemscontainer instance 1-7customizing 5-16debugging 5-62instances 1-7monitoring overview 1-4

Ttechnical support 5-70Text Window Buffer Size 5-63

Uuninstalling 3-10

PAR File 3-14PATROL Agent 3-10PATROL Central Console 3-13PATROL Central Console Server 3-13PATROL Central Web Server 3-14PATROL Console 3-11

UnloadingPATROL Agent 4-17PATROL Central 4-19PATROL Console 4-18

upgradingoperating system 5-69Veritas Cluster Server 5-69

User Guide, pdf format 3-6


Index 5

VVCS_SETUP instance 1-6Veritas Cluster Server instance 1-6



Notes

Date post:	25-Apr-2018
Category:	Documents
Upload:	lemien
View:	221 times
Download:	2 times

PATROL for Veritas Cluster Server by OTL Software User Guide · vi PATROL for Veritas Cluster...

Documents