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

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

Date post:25-Apr-2018
Category:
View:219 times
Download:2 times
Share this document with a friend
Transcript:
  • 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=ughttp://www.otl.co.nz/km/latest_versions.asp?utm_source=km-vcs&utm_medium=ughttp://www.otl.co.nz/support?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

    OTL Software Ltd., Confidential and Proprietary Information

    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

    Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71

    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

    OTL Software Ltd., Confidential and Proprietary Information

    Contents vii

  • OTL Software Ltd., Confidential and Proprietary Information

    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

    OTL Software Ltd., Confidential and Proprietary Information

    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

    OTL Software Ltd., Confidential and Proprietary Information

    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

    OTL Software Ltd., Confidential and Proprietary Information

    Tables xi

  • OTL Software Ltd., Confidential and Proprietary Information

    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.

    OTL Software Ltd., Confidential and Proprietary Information

    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

    OTL Software Ltd., Confidential and Proprietary Information

    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

    OTL Software Ltd., Confidential and Proprietary Information

    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.

    OTL Software Ltd., Confidential and Proprietary Information

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

    OTL Software Ltd., Confidential and Proprietary Information

    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.

    OTL Software Ltd., Confidential and Proprietary Information

    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

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

    OTL Software Ltd., Confidential and Proprietary Information

    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

    OTL Software Ltd., Confidential and Proprietary Information

    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.

    OTL Software Ltd., Confidential and Proprietary Information

    Product Components and Capabilities 1-3

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

    OTL Software Ltd., Confidential and Proprietary Information

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

  • 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

    OTL Software Ltd., Confidential and Proprietary Information

    Product Components and Capabilities 1-5

  • 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

    Displays Veritas Cluster Server agent information.

    Child of: VCS_SERVER

    Object: AgentComponent: Agent

    VCS_DAEMON_CONTAINER

    VCS_DAEMON

    Daemons

    Displays Veritas Cluster Server application daemon information.

    Child of: VCS_SERVER

    Object: DaemonComponent: Daemon

    OTL Software Ltd., Confidential and Proprietary Information

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

  • VCS_SLAVE_CONTAINER

    VCS_SLAVE

    Systems

    Displays Veritas Cluster Server System information.

    Child of: VCS_SERVER

    Parent of: VCS_HEARTBEAT

    Object: SlaveComponent: System

    VCS_HEARTBEAT Displays Veritas Cluster Server heartbeat information on all systems.

    Child of: VCS_SLAVE

    Object: SlaveComponent: System

    VCS_GAB_CONTAINER

    VCS_GAB

    GAB

    Displays Veritas Cluster Server GAB information.

    Child of: VCS_SERVER

    Object: GABComponent: GAB

    VCS_LLT_CONTAINER

    VCS_LLT

    LLT

    Displays Veritas Cluster Server LLT information.

    Child of: VCS_SERVER

    Object: LLTComponent: LLT

    VCS_LOG_CONTAINER

    VCS_LOG

    Logs

    Displays Veritas Cluster Server log file information.

    Child of: VCS_SERVER

    Object: LogComponent: Log

    VCS_GROUP_CONTAINER

    VCS_GROUP

    Service Groups

    Displays Veritas Cluster Server service group information.

    Child of: VCS_SERVER

    Parent of: VCS_GSYSTEM

    Object: ClusterComponent: Group

    VCS_GSYSTEM Displays Veritas Cluster Server group system information.

    Child of: VCS_GROUP

    Object: ClusterComponent: Group

    Table 1-1 Application Class Icons and Functions

    Icon Application Class Instance Label Function

    OTL Software Ltd., Confidential and Proprietary Information

    Product Components and Capabilities 1-7

  • VCS_RESOURCE_CONTAINER

    VCS_RESOURCE

    Resources

    Displays Veritas Cluster Server resource information.

    Child of: VCS_SERVER

    Parent of: VCS_RSYSTEM

    Object: ClusterComponent: Resource

    VCS_RSYSTEM Displays Veritas Cluster Server resource system information.

    Child of: VCS_RESOURCE

    Object: ClusterComponent: Resource

    Table 1-1 Application Class Icons and Functions

    Icon Application Class Instance Label Function

    OTL Software Ltd., Confidential and Proprietary Information

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

  • 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

    OTL Software Ltd., Confidential and Proprietary Information

    Product Components and Capabilities 1-9

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

    OTL Software Ltd., Confidential and Proprietary Information

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

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

    OTL Software Ltd., Confidential and Proprietary Information

    Product Components and Capabilities 1-11

  • 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 helpTo 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

    OTL Software Ltd., Confidential and Proprietary Information

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

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

    OTL Software Ltd., Confidential and Proprietary Information

    Product Components and Capabilities 1-13

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

    OTL Software Ltd., Confidential and Proprietary Information

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

  • 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

    OTL Software Ltd., Confidential and Proprietary Information

    Product Components and Capabilities 1-15

  • OTL Software Ltd., Confidential and Proprietary Information

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

  • 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

    OTL Software Ltd., Confidential and Proprietary Information

    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

    OTL Software Ltd., Confidential and Proprietary Information

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

  • 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

    OTL Software Ltd., Confidential and Proprietary Information

    Preparing to Install 2-3

  • 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

    OTL Software Ltd., Confidential and Proprietary Information

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

  • 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)

  • 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

    OTL Software Ltd., Confidential and Proprietary Information

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

    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 Administrators Guide for details on how to set up this type of account.

    OTL Software Ltd., Confidential and Proprietary Information

    Preparing to Install 2-7

  • 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

    OTL Software Ltd., Confidential and Proprietary Information

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

  • 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)

    OTL Software Ltd., Confidential and Proprietary Information

    Preparing to Install 2-9

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

    OTL Software Ltd., Confidential and Proprietary Information

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

  • 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:

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

    env_keep+="SHLIB_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 AIX & Linux:

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

    env_keep+="LIBPATH 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/*

    OTL Software Ltd., Confidential and Proprietary Information

    Preparing to Install 2-11

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

    OTL Software Ltd., Confidential and Proprietary Information

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

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

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

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

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

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

    Chapter 4: Loading and Configuring

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

    OTL Software Ltd., Confidential and Proprietary Information

    Preparing to Install 2-13

    http://www.otl.co.nzhttp://www.otl.co.nzhttp://www.otl.co.nz

  • OTL Software Ltd., Confidential and Proprietary Information

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

  • 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

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

    OTL Software Ltd., Confidential and Proprietary Information

    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

    OTL Software Ltd., Confidential and Proprietary Information

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

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

    OTL Software Ltd., Confidential and Proprietary Information

    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.

    OTL Software Ltd., Confidential and Proprietary Information

    3-4 PATROL for Veritas Cluster Server by OTL Software - User Guide

  • 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

    OTL Software Ltd., Confidential and Proprietary Information

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

    OTL Software Ltd., Confidential and Proprietary Information

    3-6 PATROL for Veritas Cluster Server by OTL Software - User Guide

  • 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

    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/

    OTL Software Ltd., Confidential and Proprietary Information

    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\

    OTL Software Ltd., Confidential and Proprietary Information

    3-8 PATROL for Veritas Cluster Server by OTL Software - User Guide

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

    OTL Software Ltd., Confidential and Proprietary Information

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

    OTL Software Ltd., Confidential and Proprietary Information

    3-10 PATROL for Veritas Cluster Server by OTL Software - User Guide

  • 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

    Unix Microsoft Windows

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

    OTL Software Ltd., Confidential and Proprietary Information

    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

    File Types to Delete

    Path relative to PATROL_HOME

    Unix Microsoft Windows

    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

    OTL Software Ltd., Confidential and Proprietary Information

    3-12 PATROL for Veritas Cluster Server by OTL Software - User Guide

  • 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

    File Types to Delete

    Path for PATROL Central Console Server

    Unix Microsoft Windows

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

    OTL Software Ltd., Confidential and Proprietary Information

    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

    File Types to Delete

    Path for PATROL Central Web Server

    Unix Microsoft Windows

    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

    OTL Software Ltd., Confidential and Proprietary Information

    3-14 PATROL for Veritas Cluster Server by OTL Software - User Guide

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

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

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

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

    Chapter 4: Loading and Configuring

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

    OTL Software Ltd., Confidential and Proprietary Information

    Installation 3-15

  • OTL Software Ltd., Confidential and Proprietary Information

    3-16 PATROL for Veritas Cluster Server by OTL Software - User Guide

  • 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

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

    OTL Software Ltd., Confidential and Proprietary Information

    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.

    OTL Software Ltd., Confidential and Proprietary Information

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

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

    OTL Software Ltd., Confidential and Proprietary Information

    Loading and Configuring 4-3

  • 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 ent

of 232/232
PATROL ® for Veritas Cluster Server™ by OTL Software User Guide Version 2.2 Document Revision 3 April 15, 2011
Embed Size (px)
Recommended