Veritas Volume Manager for PATROL v2.5 - Sentry Software · PDF fileVeritas Volume Manager KM...

User Documentation December 2013

Veritas Volume Manager KM forPATROL

Version 2.5.00

Contacting BMC SoftwareYou can access the BMC Software Web site at http://www.bmc.com/. From this Web site, you canobtain information about the company, its products, corporate offices, special events, and careeropportunities.

United States and Canada Outside United States and Canada

Address BMC Software, Inc.2101 CityWest Blvd. Houston TX 77042-2827

Telephone (01) 713 918 8800

Telephone 713 918 8800 or 800 841 2031

Fax (01) 713 918 8000

Fax 713 918 8000

Copyright 2006 BMC Software, Inc. or licensors, as an unpublished work. All rights reserved.

BMC Software, the BMC Software logos, and all other BMC Software product or service names areregistered trademarks or trademarks of BMC Software, Inc.

IBM is a registered trademark of International Business Machines Corporation.

DB2 is a registered trademark of International Business Machines Corporation.

Oracle is a registered trademark, and the Oracle product names are registered trademarks ortrademarks of Oracle Corporation.

All other trademarks belong to their respective companies.

BMC Software considers information included in this documentation to be proprietary and confidential.Your use of this information is subject to the terms and conditions of the applicable End User LicenseAgreement for the product and the proprietary and restricted rights notices included in thisdocumentation.

Restricted Rights Legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVEDUNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any dataand computer software by the U.S. Government is subject to restrictions, as applicable, set forth inFAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, andDFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc.,2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this

2

Version 2.5.00

Veritas Volume Manager KM for PATROL

You can obtain technical support by using the Support page on the BMC Software Web site or bycontacting Customer Support by telephone or e-mail. To expedite your inquiry, please see "BeforeContacting BMC Software."

Support Web Site

You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this Web site, you can

Read overviews about support services and programs that BMC Software offers:

Find the most current information about BMC Software products

Search a database for problems similar to yours and possible solutions

Order or download product documentation

Report a problem or ask a question

Subscribe to receive e-mail notices when new product versions are released

Find worldwide BMC Software support center locations and contact information, including e-mailaddresses, fax numbers, and telephone numbers

Support by Telephone or E-mail

In the United States and Canada, if you need technical support and do not have access to the Web,call 800 537 1813. Outside the United States and Canada, please contact your local support center forassistance. To find telephone and email contact information for the BMC Software support center thatservices your location, refer to the Contact Customer Support section of the Support page on the BMCSoftware Web site at http://www.bmc.com/support_home.

Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Supportcan begin working on your problem immediately:

Product information

product name

product version (release number)

license number and password (trial or permanent)

Operating system and environment information machine type operating system type, version, andservice pack or other maintenance level such as:

PUT or PTF

system hardware configuration

serial numbers

related software (database, application, and communication) including type, version, andservice

pack or maintenance

level

Sequence of events leading to the problem

Commands and options that you used

Messages received (and the time and date that you received them)

product error messages

3

Version 2.5.00


http://www.bmc.com/support_home



Table of Contents 4

Version 2.5.00


Table of Contents...........................................................................................................................11Requirements

...........................................................................................................................11System Requirements

...........................................................................................................................11Software Requirements

...........................................................................................................................13Security Requirements

...........................................................................................................................16Disk Space Requirements

...........................................................................................................................17Getting the BMC Software Installation Utility

...........................................................................................................................17Packages

...........................................................................................................................18Extracting the Setup Files

...........................................................................................................................20Installing Veritas Volume Manager KM for PATROL

...........................................................................................................................32Uninstalling Veritas Volume Manager KM for PATROL

...........................................................................................................................37Loading / Unloading the KM

...........................................................................................................................37Loading the KM

..................................................................................................................38Preparing to Load the KM

..................................................................................................................38Loading the KM on PATROL Console

..................................................................................................................38Loading the KM on PATROL Central

..................................................................................................................39Preloading the KM

...........................................................................................................................39Unloading the KM

..................................................................................................................40Unloading the KM from the PATROL Agent

..................................................................................................................40Unloading the KM from the PATROL Console

..................................................................................................................41Unloading the KM from the PATROL Central Console

...........................................................................................................................41Performing Post-Installation Operations

...........................................................................................................................41Configuring the KM User Account

...........................................................................................................................43Verifying Application Discovery

...........................................................................................................................44Checking the Instance Limits

...........................................................................................................................45Checking the Initial Setup of the KM

...........................................................................................................................45Restarting PATROL Agent and PATROL Console

...........................................................................................................................45Upgrading the Platform

...........................................................................................................................47Integrating with BMC Portal

...........................................................................................................................47Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x

...........................................................................................................................48Creating and Importing an Adapter for a BMC PATROL KM

...........................................................................................................................49Updating an Adapter for a BMC PATROL KM

...........................................................................................................................49Importing and Customizing Thresholds

Table of Contents 5

Version 2.5.00


...........................................................................................................................50Managing Baselines and Key Performance Indicators

...........................................................................................................................53Configuring the KM

...........................................................................................................................53Configuring the Multi-Node Monitoring Mode

...........................................................................................................................54Filtering Elements to Monitor

...........................................................................................................................57Configuring the Element Status

...........................................................................................................................59Configuring the Node Status

...........................................................................................................................60Configuring the Log Filter

...........................................................................................................................62Configuring the Log Scan Limit

...........................................................................................................................62Configuring Logs Alert Acknowledgement

...........................................................................................................................63Using the KM

...........................................................................................................................63Acknowledging Alerts

...........................................................................................................................64Enabling the Debug Mode

...........................................................................................................................66Generating Reports

...........................................................................................................................67Refreshing Parameters

...........................................................................................................................70Classes and Parameters

...........................................................................................................................71VVM_DAEMON

...........................................................................................................................73VVM_DAEMON_CONTAINER

...........................................................................................................................75VVM_DISKDEVICE

...........................................................................................................................79VVM_DISKDEVICE_CONTAINER

...........................................................................................................................80VVM_DISKGROUP

...........................................................................................................................84VVM_DISKGROUP_CONTAINER

...........................................................................................................................92VVM_DISKPATH

...........................................................................................................................93VVM_LOG

...........................................................................................................................96VVM_LOG_CONTAINER

...........................................................................................................................98VVM_PLEX

...........................................................................................................................102VVM_RLINK

...........................................................................................................................104VVM_RVG

...........................................................................................................................106VVM_RVG_CONTAINER

...........................................................................................................................108VVM_SERVER

...........................................................................................................................112VVM_SUBDISK

...........................................................................................................................116VVM_VOLUME

...........................................................................................................................120VVM_VOLUME_CONTAINER

...........................................................................................................................123Where to Find Additional Help

Release Notes for v2.5.00

7

Version 2.5.00


What's newVeritas Volume Manager KM for PATROL now monitors Veritas Volume Replicator (VVR) andprovides useful information about Replicated Volume Groups (RVG) and RLINKs.

The collector execution time is now monitored for the disk devices, disk groups, logs, plexes,Rlinks, replicated volume groups, subdisks, and volumes.

Changes and ImprovementsRegular expressions can now be used to filter elements to monitor.

Fixed IssuesOn Unix platforms, daemon collector command and arguments have been modified to only returnthe relevant daemon lines from the process list and therefore, properly set the parameters VVMDaemonProcessCount, VVMDaemonProcessCount, VVMDaemonCPUUtilizationand VVMDaemonCPUDuration.

A compatibility issue prevented the KM to operate when the PATROL Agent v9.0.20 was run withthe PATROL Config Cache support.

Overview

9

Version 2.5.00


Veritas Volume Manager KM for PATROL (or VVM KM) helps you ensure that your Veritas VolumeManager installations run efficiently 24 hours a day.

The KM more especially monitors:

Server: monitors overall health of the Veritas Volume Manager and it is critical daemons.

Disks and Multi Paths: monitors the health of disk devices and dynamic multi-pathing (DMP).

Logs: checks regularly for any errors in the system and event logs and monitors the log spaceutilization.

Logical Volumes: automatically discovers and monitors volumes, plexes and subdisks.

Replication (VVR): monitors status and performance of replicated volume groups (RVGs) andreplication links (RLINKs).

Performance: collects I/O performance statistics at disk, volume, plex & subdisk levels to helpidentify any bottlenecks.

All the information collected is grouped into application classes and displayed in the PATROL Console.Alarms and warnings inform you when a suspicious behavior is detected; thus allowing you to quicklyand clearly identify peaks, troughs and trends in the performance of your backup resources.

Refer to the Reference Guide for more information about the application classes.

Preparing for Installation

11

Version 2.5.00


This chapter provides information about the tasks that must be performed before you start installingVeritas Volume Manager KM for PATROL. Make sure to carefully read the following sectionsrequirements:

Review the System, Software, Security and Disk Space Requirements

Get the BMC Software Installation Utility

Download the Installation Packages

Extract the Setup Files

Requirements

System RequirementsThe following list shows the operating systems and their versions supported by Veritas VolumeManager KM for PATROL.

Microsoft Windows Server 2003 and 2008, all versions supported by BMC PATROL Agent 3.7 andgreater

Linux, all distributions supported by BMC PATROL Agent 3.7 and greater

Sun Solaris 8, 9, 10, supported by BMC PATROL Agent 3.7 and greater

HP-UX 11, supported by BMC PATROL Agent 3.7 and greater

IBM AIX 5.x and 6.x, supported by BMC PATROL Agent 3.7 and greater

If the operating system is upgraded (or downgraded) at a later date, you will need to reload commandsfor the Veritas Volume Manager KM for PATROL. Refer to Upgrading the Platform.

Software Requirements

Software Requirements

The following table contains a list of required software and their versions supported by VeritasVolume Manager KM for PATROL.

Software Version

Veritas Volume Manager™ (included in Veritas StorageFoundation Suites)

4.5, 5.0, 5.1, 6.x

BMC Software PATROL Agent 3.7+

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

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

BMC ProactiveNet Performance Management 8.x, 8.5.x, 8.6.x, 9.x

12Requirements

Version 2.5.00


Version 2.5 of Veritas Volume Manager KM for PATROL does not support Veritas Volume Manager versions before 3.2and PATROL Agent versions before 3.4.

If the operating system is upgraded (or downgraded) at a later date, you will need to reload commandsfor the VVM KM. Refer to Upgrading the Platform.

Changes to Veritas Volume Manager

There are no changes required to the Veritas Volume Manager application in order to use VeritasVolume Manager KM for PATROL.

Changes to BMC PATROL

To improve the performance of the VVM KM, the PATROL Agent tuning variable “/AgentSetup/AgentTuning/pslInstructionMax” should be disabled by setting it to 0 (zero) or increased to at least5,000,000.

This applies for all Veritas Volume Manager active servers and media servers where the KM isinstalled. This adjustment will allow the data collectors to execute without incurring an internalscheduling 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 followingsingle 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);}

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

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

13Requirements

Version 2.5.00


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

Additional Software Requirements

The following table contains a list of additional software requirements of Veritas Volume Manager KMfor PATROL:

Purpose Software Version

When running VVM KM with sudo user account onSolaris, HP-UX, AIX or Linux managed nodes

Sudo (superuser do) 1.6.7 or later

When running VVM KM on Linux managed nodes Korn shell binary (/bin/ksh) Any

When running VVM KM on Microsoft Windows x64managed nodes

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

Any

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

Security RequirementsBy default, Veritas Volume Manager is installed and run as the root user (on Unix) or asadministrator user (on Microsoft Windows).

Veritas Volume Manager KM for PATROL needs to be run as a user account with administrativeprivileges to read and execute Veritas Volume Manager application programs and file systems. Logindetails of this user are configured in the KM during the configuration. The password is stored in thePATROL Agent in a DES encrypted format.

The encrypted password can be viewed by any user who has access to the PATROL Agent configurationvariables (pconfig). This user could then execute PSL statements using the encrypted password throughthe PATROL Console. This can be prevented by setting up an appropriate Access Control List (ACL) forusers. 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 Volume Manager to executeapplication programs and access the file systems (Unix only)

3. a non-root (Unix) or non-administrator (Microsoft Windows) account, such as patrol, configuredin Veritas Volume Manager application to administer the Veritas Volume Manager application

Refer to the Veritas Volume Manager System Administrator’s Guide for details on how to set up this type of account.

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

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

14Requirements

Version 2.5.00


Access Permissions

The VVM KM user needs “read & execute” permission to executable and library files under the pathslisted below. The Veritas Volume Manager installation path INSTALL_PATH, referenced in the tablesbelow is normally /opt/VRTSvxvm (on Unix) or C:\Program Files\Veritas\Volume Managerx.x (on Microsoft Windows).

Executable and Library Files accessed by VVM KM User

Unix Microsoft Windows

INSTALL_PATH/bin INSTALL_PATH/lib/usr/sbin/*

INSTALL_PATH\vx*.exe

If the KM is enabled to failover in a clustered environment, the login user needs execute permissionsto the following cluster commands:

/opt/VRTSvcs/bin/hagrp (in Veritas Cluster Server)

vxdctl (in Veritas Cluster File System)

/usr/cluster/bin/clrg (in Oracle Solaris Cluster)

C:\Windows\sysnative\cluster (in Microsoft Cluster)

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

In addition to these Veritas Volume Manager commands, VVM KM executes other operating system commands, such asps, uname which may not require special privileges.

To list all OS commands used by the VVM KM, execute the following PSL code from the PATROLConsole, using PSL Task menu, after installing and loading the KM.

i=0; sudoers="";foreach var (grep("^/Runtime/VVM/CommandControls/",pconfig("LIST"))){ ctl=get(var); opt=ntharg(grep("Option",ctl),"2-"," ="); nsa=ntharg(grep("NoSudoAttempt",ctl),"2-"," ="); sua=ntharg(grep("SingleUserAttempt",ctl),"2-"," ="); typ=ntharg(grep("CommandType",ctl),"2-"," ="); cmd=nthargf(grep("CommandText",ctl),"2-","=","=");

if((typ == "")||(typ == "OS")) { met=""; if(opt == "NoLogin") { met = "(run as patrol user)"; } elsif(nsa == "YES") { met = "(run as configured user without sudo)"; } elsif(sua == "YES") { met = "(run as supplied user - used in menu)"; } else { scmd=cmd; s=index(scmd,"%sudo"); if(s) { scmd=replace(substr(scmd,s,length(scmd)),"%sudo",""); } sudoers=union(sudoers,ntharg(ntharg(scmd,1,"|"),"1-"," "," "));

15Requirements

Version 2.5.00


} printf("(%2d) %-30s %-40s: %s\n",i++,ntharg(var,"5","/"),met,cmd); }}

printf("\n\nCommands used with sudo:\n%s",sort(sudoers));

The PATROL Agent user (normally patrol) needs “read & execute” permission to following paths andfiles:

/var/adm/messages (on Solaris)

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

/var/log/messages (on Linux and AIX)

If a monitored log file cannot be read by the PATROL Agent user, it will be copied to KM_TEMP pathusing the configured login account, and processed by the PATROL Agent user. On completion the copiedlog file will be removed. This may increase the file system usage under KM_TEMP temporarily duringthis activity.

On Windows platforms the Veritas Volume Manager installation is identified by checking the MicrosoftWindows Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\VxSvc\

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

Sudo User for Operating System Access

If a non-root user with sudo privileges is preferred as the VVM KM user, configure the account as asudoer through the visudo utility using code appropriate for your platform as detailed below. Thisuser should be able to execute VxVM commands and OS commands.

The code below also applies to all non-root users who may execute VVM KM administration andreport menu commands using their sudo privileges. The KM accepts any non-root user with thefollowing sudo configuration in the sudoers file. Please replace user1, user2, user3 with appropriateKM user name. The Veritas Volume Manager installation path INSTALL_PATH, referenced below isnormally /opt/VRTS and PATROL_HOME is the path where the PATROL Agent is installed (includingthe target, like /opt/bmc/Patrol3/Solaris29-sun4/).

This non-root sudo user configured in the KM will be able to execute Veritas Volume Managercommands. To prevent unauthorized access, ensure this user is only used within the KM and not madepublic for general use.

Entering 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 configureddifferently, the KM may run sudo commands using incorrect sudo settings, which may expose the sudouser password.

On Solaris:User_Alias VVMKMUSERS = user1, user2, user3Defaults:VVMKMUSERS !lecture,!authenticate,\

16Requirements

Version 2.5.00


env_keep+="LD_LIBRARY_PATH INSTALL_PATH KM_HOME KM_TEMP",env_resetVVMKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\INSTALL_PATH/bin/*,\PATROL_HOME/lib/VVM/*,PATROL_HOME/bin/*

user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH and PATROL_HOME with therelevant paths.

On HP-UX:User_Alias VVMKMUSERS = user1, user2, user3Defaults:VVMKMUSERS !lecture,!authenticate,\env_keep+="SHLIB_PATH INSTALL_PATH KM_HOME KM_TEMP",env_resetVVMKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\INSTALL_PATH/bin/*,\PATROL_HOME/lib/VVM/*,PATROL_HOME/bin/*


On AIX & Linux:User_Alias VVMKMUSERS = user1, user2, user3Defaults:VVMKMUSERS !lecture,!authenticate,\env_keep+="LIBPATH INSTALL_PATH KM_HOME KM_TEMP",env_resetVVMKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\INSTALL_PATH/bin/*,\PATROL_HOME/lib/VVM/*,PATROL_HOME/bin/*


Disk Space RequirementsVeritas Volume Manager KM for PATROL requires approximately:

• 1.5 MBytes disk space on each monitored PATROL Agent system

• 2.5 MBytes disk space on each PATROL Console system

• 600 KBytes disk space on each PATROL Central Console Server system

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

The VVM KM is installed under the PATROL installation path.

When monitoring a standard installation of Veritas Volume Manager using VVM KM, the PATROLAgent will generate approximately 250 KBytes of history data per day. An enterprise installation ofVeritas Volume Manager on a active server with large number of VxVM objects will generate morehistory data (as per other KMs used by the PATROL Agent). These history data files are recycled byPATROL depending on the PATROL Agent history retention period.

During execution, the VVM KM creates and maintains temporary files under KM_HOME, KM_TEMPand KM_DEBUG paths. By default they are all under PATROL_HOME/lib/VVM, where

17Requirements

Version 2.5.00


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 theConfiguration > Paths menu from the main instance. These folder should have read, write andexecute permissions for both the PATROL Agent user and the KM login user.

Getting the BMC SoftwareInstallation UtilityIn order to install Veritas Volume Manager KM for PATROL, you need the latest version of the BMCSoftware Installation Utility. You can download the latest Installation Utility from the BMC SoftwareEPD (electronic product download) from: http://webapps.bmc.com/signon/content/logon.jsp on theBMC Software Website, or from the Veritas Volume Manager KM for PATROL page on the SentrySoftware Website

Choose the appropriate package depending on the platform you plan to install Veritas VolumeManager KM for PATROL on:

For UNIX/Linux systems: ins_ALL_<version>.tar

For Windows systems: ins_WINDOWS_<version>.exe

The packages are valid for all the PATROL components: Agent, Console, Console Server, etc.

Place the Installation Utility package in the same folder as the Veritas Volume Manager KM forPATROL packages.

Packages

The Veritas Volume Manager KM for PATROL packages are available on the Sentry Software Website.

There are two packages, each of which can be used to install the KM on every PATROL component(Agent, Console, etc.) according to the platform you are using. However, depending on the packagedownload source, the file names may differ:

Downloading from Sentry Software Web site

vvm_ALL_2500.zip

vvm_ALL_2500.tar

The Veritas Volume Manager KM for PATROL packages are designed for use with the BMC Software

Installation Utility (formerly known as Thorium). They need to be merged with the latest availableversion of the BMC Software Installation Utility. Please see instructions.

http://webapps.bmc.com/signon/content/logon.jsp

http://www.sentrysoftware.net/Products/VeritasVolumeManagerKM_Downloads.asp

http://www.sentrysoftware.com


18Extracting the Setup Files

Version 2.5.00


Extracting the Setup Files

Like most Knowledge Modules for PATROL, you need to install Veritas Volume Manager KM forPATROL on the following components of your PATROL architecture:

Every managed system with a PATROL Agent

Every PATROL Console (Classic) that will show Veritas Volume Manager performance-relatedinformation and alerts

The Console Server

PATROL Central – Web Edition

Installing the KM

20

Version 2.5.00


Introduction

This section describes the installation procedure for Veritas Volume Manager KM for PATROL on anyPATROL component (Agents, Consoles, Console Server, etc.). As the setup is based on the BMCSoftware Installation Utility, this procedure applies to all operating systems supported by VeritasVolume Manager KM for PATROL.

Installing Veritas Volume ManagerKM for PATROLInstalling Veritas Volume Manager KM for PATROL is an automated process managed by a wizard.The wizard goes through the necessary steps to install Veritas Volume Manager KM for PATROL andall files associated with it. You are simply prompt for the product's folder location and the product/components to install.

Browse to the bmc_products folder where the files have been extracted (both Veritas VolumeManager KM for PATROL and the Common Installer).

On Windows: Launch the setup.exe program

On UNIX: Launch the setup.sh script

To install Veritas Volume Manager KM for PATROL1. Allow the perl.exe program to listen on this port: Click Allow access.

21Installing Veritas Volume Manager KM forPATROL

Version 2.5.00


Installation W izard - Step 1: W indow s Security Alert

2. The welcome screen of the installer appears. Click Next to continue.

Installation W izard - Step 2: W elcome


Version 2.5.00


3. Read the license agreement, click the Accept option and then click Next to continue.

Installation W izard - Step 3: Review ing License Agreement


Version 2.5.00


4. Select Install the products on this computer now and click Next to continue.

Installation W izard - Step 4: Selecting Installation Options


Version 2.5.00


5. Specify the BMC Software products folder. See the BMC Software documentation for moreinformation about the BMC Software products folder. Click Next to continue.

Installation W izard - Step 5: Selecting the Installation Directory


Version 2.5.00


6. Select Default. Installing Veritas Volume Manager KM for PATROL does not require anycustomization. Click Next to continue.

Installation W izard - Step 6: Selecting an Installation Type

7. Select one or several of the following options:

Managed System to install Veritas Volume Manager KM for PATROL on a PATROL Agent.

Console Systems role to install Veritas Volume Manager KM for PATROL on a PATROL ClassicConsole.

Common services to install Veritas Volume Manager KM for PATROL on the Console Serveror on PATROL Central – Web Edition.

Click Next to continue.


Version 2.5.00


Installation W izard - Step 7: Selecting Roles

Select as many options as required.


Version 2.5.00


8. Check the Veritas Volume Manager KM for PATROL box to install the KM (it should beselected by default). Click Next to continue.

Installation W izard - Step 8: Selecting Products and Components


Version 2.5.00


9. Review the installation parameters and click Start Install to launch the installation procedure.

Installation W izard - Step 9: Review ing Installation Options


Version 2.5.00


10. The setup program displays the actions performed and indicates the percentage of completion.Once the installation complete, click Next to view the installation results.

Installation W izard - Step 10: Installation Status


Version 2.5.00


11. The wizard displays the installation results.Click View Log to display a detailed log of the installation procedure. Click Next and thenFinish to exit the setup program.

Installation W izard - Step 11: Installation Results

12. Click the Finish button to complete and close the installation wizard.


Version 2.5.00


Installation W izard - Step 12: Completing and closing the Installation W izard

A Help button is available at each step of the procedure. Click to display the installation online help. The Exit buttonallows you to stop the installation procedure.


Version 2.5.00


Uninstalling Veritas VolumeManager KM for PATROLUninstalling Veritas Volume Manager KM for PATROL is an automated process managed by a wizard.The wizard goes through the necessary steps to remove Veritas Volume Manager KM for PATROL andall files associated with it. You are simply prompt for the product's folder location and the product/components to uninstall.

To uninstall Veritas Volume Manager KM for PATROL1. Locate the Uninstall folder under the BMC products directory (typically under C:\Program Files

\BMC Software, or /opt/bmc):

On Windows systems, launch uninstall.exe

On UNIX, launch uninstall.sh

Un-install W izard — W elcome Step

33Uninstalling Veritas Volume Manager KM forPATROL

Version 2.5.00


2. Specify the BMC Software products folder. See the BMC Software documentation for moreinformation about the BMC Software products folder.

Un-install W izard — Specifying folder


Version 2.5.00


3. To uninstall the KM, select Veritas Volume Manager KM for PATROL.

Un-install W izard — Selecting Products and Components Directory


Version 2.5.00


4. Click Start Uninstall.

Un-install W izard — Review ing Selected Products & components and start uninstalling


Version 2.5.00


5. A page displays the list of products/components processed and the percentage of completion.Click Next to continue.

Un-install W izard — Status


Version 2.5.00


6. A page displaying SUCCESS indicates that Veritas Volume Manager KM for PATROL is nowuninstalled.

Un-install W izard — Uninstall Results

Loading / Unloading the KM

Once installed the KM will have to be preloaded on one of the following PATROL consoles:

PATROL Console

PATROL Central

The PATROL Agent can also be configured to automatically preload the KM.

Loading the KM

This section provides instructions to load Veritas Volume Manager KM for PATROL on MicrosoftWindows and Unix platforms.

Before you load the VVM KM, you must install the KM on PATROL Console and PATROL Agentsystems.

38Loading / Unloading the KM

Version 2.5.00


Preparing to Load the KM1. Start the PATROL Console and update the connection to all PATROL Agent systems where the

VVM KM is installed.

2. Check the value of the PATROL Agent tuning variable, /AgentSetup/AgentTuning/pslInstructionMax, and if necessary, increase it

Loading the KM on PATROL ConsoleTo load the KM on a PATROL Console:

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

2. Select the VVM_LOAD.kml file

3. Click Open or OK.

The VVM KM will be loaded to the PATROL Console, and all connected PATROL Agents will startdiscovering the Veritas Volume Manager environment.

If the automatic discovery successfully finds the Veritas Volume Manager server installation, the VVM_SETUP instance will be instantiated:

This automatic discovery may take up to 5 minutes to instantiate the VVM_SETUP instance. Look for any errormessages on the PATROL Console System Output Window (SOW) during the initial discovery.

If you want to save the new list of loaded files as the PATROL Console user preference:

1. From the PATROL Console menu bar, choose File > Save Configuration

2. Load the VVM_LOAD.kml file on each PATROL Console.

3. Configure the KM.

Loading the KM on PATROL CentralTo load the KM on PATROL Central:

1. In the Console, right-click the Managed System and select Load Knowledge Modules... TheLoad Knowledge Modules wizard is displayed

2. Click Next

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

4. Select the VVM_LOAD.kml file for each managed system, click Next> and Finish.

The VVM KM will be loaded to the PATROL Central Console Server, and all connected selectedmanaged systems will start discovering the Veritas Volume Manager environment. If the automaticdiscovery successfully finds the Veritas Volume Manager installation, the VVM_SETUP instance willbe instantiated.

This automatic discovery may take up to 5 minutes to instantiate the VVM_SETUP instance. Look for any errormessages on the PATROL Central System Output Window (SOW) during the initial discovery.


Version 2.5.00


5. Load the VVM_LOAD.kml file on each PATROL Central Management Profile where VVM KMis tobe loaded.

6. Configure the KM.

Preloading the KMTo enable Veritas Volume Manager KM for PATROL to operate all the time, without a PATROLConsole connection:

1. right-click the Veritas Volume Manager instance and select KM commands > Configuration >Preloading

Preloading Configuration dialog

2. Click Add to add the KM files to the list of preloaded KMs.

The KM will thus be added to the PATROL Agent configuration variable/AgentSetup/preloadedKMs

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

If you want to completely uninstall the KM, please follow the uninstall procedure. If you are attempting to unload theKM in order to upgrade to a later version, please follow the installation procedure.

When the KM is unloaded:

from a PATROL Agent: PATROL stops monitoring the Veritas Volume Manager application onthat system when there is no connection to a PATROL Console with VVM KM loaded.

from PATROL Console: the PATROL Console stops displaying and monitoring the VeritasVolume Manager application on any PATROL Console connected system.


Version 2.5.00


Unloading the KM from the PATROL AgentTo unload the KM from the PATROL Agent:

1. the Console, right-click the Veritas Volume Manager icon and select KM Commands >Configuration > Preloading

2. Click Remove

3. Restart the PATROL Agent.

4. Repeat these steps on every PATROL Agent system (managed node) where the VVM KM is to beunloaded.

You can also use the utility wpconfig (on Microsoft Windows) or xpconfig to unload the KM. You will then have toremove VVM_LOAD.kml from the PATROL Agent configuration variable /AgentSetup/preloadedKMs.

The KM cannot be partially unloaded from the PATROL Agent using the above steps. If you need to unload some partsof the KM from the PATROL Agent, refer to the PATROL Agent Reference Manual.

Unloading the KM from the PATROL ConsoleApplication classes are unloaded individually. This allows for a partial unloading of the KM to enable itto run as a reduced installation.

To unload the VVM KM completely or partially:

1. Remove the unwanted application classes that starts with VVM_ in the list of loaded applicationclasses as described below:

With the PATROL Console for Unix:

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

Select a VVM KM application class to be removed and choose Edit>Delete.

Repeat for all classes to be removed.

With the PATROL Console for MS Windows:

From the PATROL Console tree view choose the KM tab and expand the folder ApplicationClasses.

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

Repeat for all classes to be removed.

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

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


Version 2.5.00


Unloading the KM from the PATROL Central ConsoleA KM can be unloaded from particular managed systems or for all systems across the monitoredenvironment. 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 orall of the managed systems.

To completely or partially unload the VVM 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 VVM KM is to be unloaded, and click Next>.

3. Select the VVM 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 VVM KM is tobe unloaded.

Performing Post-InstallationOperationsIt is recommended to perform post installation checks once the KM is installed and loaded on thePATROL Console to ensure it properly operates. Post-installation operations include:

Configuring the KM user account

Verifying:

the application discovery

the instance limits

the initial setup

Restarting the PATROL Agent and PATROL Console.

Configuring the KM User AccountA user account with administrative privileges must be configured in BMC PATROL to read andexecute Veritas Volume Manager application programs and file systems. Depending on the operatingsystems used, several options will be available.

On Unix platforms, you can use the following user accounts:

a root user

a non-root user, such as patrol, that has sudo privileges on Veritas Volume Manager to executeapplication programs and access file systems

a non-root account, such as patrol, configured in Veritas Volume Manager application toadminister the Veritas Volume Manager application.

42Performing Post-Installation Operations

Version 2.5.00


On Windows platforms, you can use the following user accounts:

an administrator user

a non-administrator account, such as patrol, configured in Veritas Volume Manager application toadminister the Veritas Volume Manager application.

To configure the KM User Account:1. In the Console, right-click the Veritas Volume Manager instance > Configuration > Login.

The Login Configuration dialog box is displayed:

Login Configuration dialog

2. To use:

the default PATROL Agent Account, check the Use Agent Default Account box. The logindetails entered in the Username and Password fields will then be ignored.

a different user account, enter the login details in the Username and Password fields

3. If a sudo user account is used:

check the Use Sudo box

click SUDO Binary File to verify the sudo binary file path

4. Click OK.

If the credentials are not valid, the VVMLoginStatus parameter will appear in “suspicious state”after the next data collection.


Version 2.5.00


Verifying Application DiscoveryTo verify the application discovery:

1. Check that the VVM_SETUP instance is actually named Veritas Volume Manager. If not,force a full discovery by right-clicking the VVM_SETUP instance > KM Commands > ForceDiscovery

2. Check that the application class instances are actually instantiated. The initial data collectionmay take some time depending on the complexity of your environment (up to one hour). Ifneeded, force a data collection by right-clicking the Veritas Volume Manager instance > KMCommands > Refresh Parameters.

If Veritas Volume Manager server is configured in a clustered environment, you'll have to enableMulti-node Mode monitoring.


Version 2.5.00


Checking the Instance LimitsBy default, Veritas Volume Manager KM for PATROL does not limit the number of instances that arediscovered or monitored for each monitored elements. However, in order to optimize performance inlarge environment, it is possible to disable or limit the monitoring of specific elements:

To modify the default configuration1. In the Console, right-click the KM main icon > Configuration> Instance Limits

VVM KM Default Instance Limits

2. Enter the number of instances to be displayed in the console for each monitored element

3. To disable the monitoring of a specific application class, enter 0 in the relevant field

4. Click OK.


Version 2.5.00


Checking the Initial Setup of the KMTo check 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 Volume Manager instance.

2. Check the InfoBoxes and Parameters of all the VVM KM instances and verify that they are setcorrectly.

3. Under each container instance, open all detail parameters (text parameters with names in theformat VVM<Object>Details), and check for error messages.

4. Check the new value of parameter VVMLoginStatus 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.

5. After the KM has been running for at least an hour:

Right-click the KM main icon > KM commands > KM Status from the Veritas VolumeManager instance. A report is displayed, detailing information on the managed system. Searchthe report for warnings or alarms. If errors are found during any of the above steps (includingincorrect data in Infoboxes or any warnings or alarms in the KM Status report), determine thecause(s) and take action to resolve these errors. If required, email the Technical Support andattach the KM Status report.

If needed, click Save As Task to open the report in a task window. You will be able to latersave it as a text file or print it.

If any errors are found during any of the above steps (including any incorrect data in Infoboxes or any warnings oralarms in the KM Status report), determine the cause(s) and take steps to resolve these errors. You may need to referto the User Guide, or contact Technical Support, attaching the KM Status report.

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

Restarting PATROL Agent and PATROL ConsoleRestarting the PATROL Agent and PATROL Console is optional but often a good practice to confirmthat the VVM KM operates correctly after restarting the PATROL Agent and/or PATROL Console.

In addition, the PATROL Agent restart will force all KM discoveries and data collections to startimmediately.

Upgrading the Platform

If you upgrade (or downgrade) your operating system or Veritas Volume Manager, the commands forthe VVM KM need to be reloaded. Use the menu Reload Commands from the main VVM KMcontainer instance (labeled Veritas Volume Manager).

Integrating the KM

47

Version 2.5.00


Introduction

This section provides detailed information about the integration of Veritas Volume Manager KM forPATROL with BMC ProactiveNet Performance Management.

Integrating with BMC Portal

1. Log on to BMC 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 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.

Integrating with BMC ProactiveNetPerformance Management 8.5.x and8.6.xOverviewTo integrate a BMC PATROL KM into BMC ProactiveNet Performance Management 8.5.x or 8.6.x, youneed to create a specific adapter. An adapter for BMC PATROL facilitates pulling of performance datafrom existing BMC PATROL solutions into BMC ProactiveNet. Using an Adapter, you can import BMCPATROL application classes (provided in a Knowledge Module –KM) into BMC ProactiveNet. TheAdapter periodically synchronizes the performance data collected by these application classes intoBMC ProactiveNet.

48Integrating with BMC ProactiveNetPerformance Management 8.5.x and 8.6.x

Version 2.5.00


Creating and Importing an Adapter for a BMCPATROL KM

Creating an Adapter for a BMC PATROL KM1. Open the BMC ProactiveNet Administration Console. The BMC ProactiveNet Administration

Console is displayed as shown in the following figure:EMC

2. Right-click the Adapters folder and select Import Monitor Type and Add Adapter > BMCPATROL.

3. In the Configuration tab, enter the required information:

In the Instance Name field, enter a name for this instance of the Adapter that will performthe integration of the ‘targeted KM’ into BMC ProactiveNet.

Select the Agent where this instance of the Adapter will be executed

Enter the Integration Service Agent hostname or IP address

Enter the Integration Service Agent Port. The default port is 3182.

Enter the required credential to connect to the Integration Service Agent

4. Click Next to continue

5. Click Next to let the system load the BMC PATROL application classes.

6. Select the application classes to import

Unselecting will delete the application classes that have already been imported during a previousoperation. Application classes ready to be deleted are marked with a red x.

7. Click Next to start the import process. The system displays a summary of the application classimport, click Next to continue.

8. Select the application classes you wish to auto-synchronize with the Integration Service Agent.

9. Click Next to continue

10. Set the Filter details if need.

11. Click Next to continue.

12. Set the Auto-sync poll scheduling, if needed.

13. Click Next to continue. The system displays a summary of your settings, click Finish to confirm.The Adapter has been added to the Adapters folder of the Administration Console.

14. To see the class instances that have been imported by the Adapter, expand the Adapters folder,right-click the Adapter and select Details.

We strongly recommend that you create a specific adapter for each KM you need to integrate into BMCProactiveNet to enable the update of a single KM independently.


Version 2.5.00


Updating an Adapter for a BMC PATROL KM

Updating an Adapter1. Delete the Adapter instance

2. Go through the Add an Adapter wizard to actually delete the monitor types that had beencreated based on the previous version of the KM

3. Close

4. Resume the entire Creating an Adapter for a BMC PATROL KM procedure

For complete and detailed information on these procedures, please refer to the BMC ProactiveNet documentationavailable from BMC Web site.

Importing and Customizing Thresholds1. Launch the BMC ProactiveNet PW Commands. On Windows 2008, you need to run the PW

Commands as Administrator.

2. Execute the following command line:pw adapter -type patrol -get_thresholds <file name> -pproxy_host <hostname|ipaddress> -pproxy_port <port_number>] [-pproxy_user <username>] [-pproxy_passwd <password>] -i -v

where-get_thresholds <file name> = File name with absolute path at which thresholds

will be imported-pproxy_host <hostname|ipaddress> = Host name or IP Address of Patrol Proxy Server

-pproxy_port <port_number> = Port at which Patrol Proxy Agent communicates with Patrol Proxy Server -pproxy_user <username> = User name of Patrol Proxy user -pproxy_passwd <password> = Password to authenticate Patrol Proxy user -i = import Instance level thresholds -v = run in "verbose" mode, producing extra lines of output during extraction and conversion processes

The command has produced a text file with all the parameter threshold settings.

3. Open the file in a text editor. Check that the global thresholds have been properly interpreted.

4. Then go to the # INSTANCE LEVEL THRESHOLDS section of the file.

5. Uncomment all instance level thresholds for the _PATROL__SEN_VVM_ prefixed instances.

Search the file for the 'NOT_IMPLEMENTED' occurrences to detect thresholds that were not properlyconverted by the PATROL Adapter.

6. Save the file.

7. Execute the following command:pw threshold loadpatrolthreshold [<thresholdfilename> [-v]]where: <thresholdfilename> is a thresholds file name. If no file path is specified then the default '<Installation Directory>/pw/tmp/' is used -v enables the Verbose mode

Class-level thresholds can be displayed using the Absolute Global Thresholds panel in the BMCProactiveNet Operator Console, while instance-level thresholds are displayed in the AbsoluteInstance Thresholds panel to indicate thresholds have been successfully imported into BMCProactiveNet.


Version 2.5.00


Managing Baselines and Key PerformanceIndicatorsIn order to facilitate the detection of abnormalities on your monitored environment, BMCProactiveNet calculates baselines per parameter (metrics or attributes) based on values collectedover a specified period of time to determine a normal operating range. When the collected values forthese parameters are out of range, an alert is triggered.

Some parameters are identified by default as Key Performance Indicators and therefore automaticallyincluded in the base lining calculation.

Managing baselines

The baseline is the expected normal operating range for a metric or attribute of a monitor.

The baseline is calculated by collecting the values for a monitor’s attributes and metrics over aspecified time period and establishing a low baseline value (consisting of the 10th percentile of all thevalues for a given time period) and a high baseline value (consisting of the 90th percentile of all thevalues for a given time period), taking a weighted average of these values over time. A higher weightis given to the latest data being factored into the baseline average. The accuracy of the baselineimproves over time.

Requirements for baseline generation

For baselines to be generated for an attribute, that abnormality threshold means that the thresholdexists and is not suppressed. Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes that have anactive abnormality threshold and are also KPI attributes will have baselines generated for them.

Absolute thresholds (with "outside baseline") or signature thresholds do not satisfy these requirements.

Managing Key Performance Indicators

The KPI attribute of a parameter can be activated or deactivated manually through the BMCProactiveNet Administration Console. In this KM, some parameters or attributes have beendesignated as important indicators of performance (KPIs). We do not recommend that these defaultsettings are modified.

However, advanced users may activate or deactivate KPIs from the BMC ProactiveNet AdministrationConsole.


Version 2.5.00


To add or remove Key Performance Indicator (KPI) attributes for amonitor type

1. In the Administration Console, from the menu bar, choose Tools > KPI Administration.The KPI Administration dialog box is displayed.

2. From the Monitor Type list, choose the monitor type for which you want to add or remove KPIattributes. A list of attributes for the selected monitor type is displayed.

3. In the KPI column for the attributes that you want to add or remove as Key PerformanceIndicators:

select the KPI check box to add the corresponding attribute as a KPI

deselect the KPI check box to remove the corresponding attribute from the KPIs for thatmonitor type

For complete and detailed information on this procedure, please refer to the BMC ProactiveNet documentation availablefrom BMC Web site.

Parameters for which the system by default calculates baselines as well as parameters considered asKPIs are respectively identified by the following icons:

Baselining

KPI

Monitoring your Environment

53

Version 2.5.00


Veritas Volume Manager KM for PATROL monitors and manages Veritas Volume Manager diskgroups, volumes, plexes, subdisks and the raw devices they rely on. It provides metrics on thereliability and performance of the disk arrays controlled.

Configuring the KM

The configuration instructions provided in this section should be followed on all PATROL AgentSystems where Veritas Volume Manager KM for PATROL is installed.

Before configuring the KM, make sure:

the KM is loaded on the PATROL Console

the VVM_SETUP or Veritas Volume Manager instance is displayed in the Console.

Configuring the Multi-Node Monitoring ModeIf the Veritas Volume Manager environment is installed in a cluster using Veritas Cluster Server,Veritas Cluster File System, Oracle Solaris Cluster or Microsoft Cluster, the VVM KM must be installedon all the cluster nodes to enable continuous monitoring and avoid single point of failure. To avoidduplicate alerts from multiple nodes, it is recommended to configure the solution to operate in multi-node monitoring mode.

To configure the multi-node monitoring mode:

1. In the Console, right-click the Veritas Volume Manager instance > KM Commands >Configuration > Monitoring Mode

Configuring the Multi-Node Monitoring Mode

54Configuring the KM

Version 2.5.00


2. Select Multi-node Mode

3. Select the appropriate Clustering Application

4. Indicate the Failover Group Name. Leave this field blank if you previously selected VeritasCluster File System. The VVM KM will then monitor the entire cluster from the active mastersystem, which is identified by the vxdctl -c mode command. This method requires vxconfigd inenable mode with its clustered state active.

5. Enable Remote PATROL Agent Checking to check the monitoring status of the other nodesand click OK

6. Indicate all the information required to communicate with the remote PATROL Agent(authentication server, protocol, port number, and credentials)

7. Click OK.

Veritas Volume Manager will then be monitored through the master or online node. The other nodes,which are standing by for a failover, will be in passive multi-node mode and only the Veritas VolumeManager components will be monitored.

If a managed node is unable to determine the system which should be in Active Multi-node Mode, it will change toTemporary Single-node Mode.

Filtering Elements to MonitorBy default, the solution monitors all the elements discovered, which may represent an importantworkload to the agents and servers. Because the monitoring of some elements may be irrelevant forvarious reasons, you can apply filters to indicate which elements will be monitored or not:

1. In the Console, right-click one of the following instances depending on the elements that youwish to monitor:

Daemons > KM Commands > Configuration > Daemons to filter daemons to bemonitored

Logs > KM Commands > Configuration > Logs to filter logs to be monitored. Only theVVM engine log file will be monitored on AIX and Microsoft Windows platforms since there isno ASCII format system log file to monitor.

Disk Paths > KM Command > Configuration > Disk Paths to filter disk paths to bemonitored

Diskgroups > KM Commands Configuration > Diskgroups to filter diskgroups to bemonitored

Disk Devices > KM Commands > Configuration > Disk Devices to filter disk devices tobe monitored

RLinks > KM Commands > Configuration > Replication Links to filter replication linksto be monitored

RVGs> KM Commands > Configuration > Replicated Volume Groups to filterreplicated volumes groups to be monitored

Volumes > KM Commands > Configuration > Volumes to filter volumes to be monitored

Plexes > KM Commands Configuration > Plexes to filter plexes to be monitored

Subdisks > KM Commands > Configuration > Subdisks to filter subdisks to bemonitored


Version 2.5.00


Filtering Elements to Monitor

The [ALL] entry ensures that all the elements found during PATROL discovery are instantiated andmonitored. Daemons marked as “enabled” are monitored by default; those marked as “disabled” areinstantiated in an OFFLINE state.

2. To enable elements for monitoring:

In the current configuration list, select the elements to enable

Select Enable

Click Update

A log filter will have to be configured if you enable log files for monitoring.


Version 2.5.00


3. To disable elements for monitoring:

In the current configuration list, select the elements to disable

Select Disable

Click Update

Disabled instances will be instantiated in an OFFLINE state. Commands will not be executed, thus leaving parametersnot set.

4. To delete elements monitoring rules:

In the current configuration list, select the elements to delete

Select Delete

Click Update

5. To add a new element monitoring rule:

(Optional) Check the Regular Expression box if you want to use a regular expression toenable or disable elements monitoring

Type the name of the element to be monitored or the regular expression required

If needed, enter a description

From the Status list, select Enable

Click Update.

To revert to the default monitoring configuration, type “[default]” as a new entry and click Update.

6. Resume the procedure for all the application classes for which you wish to apply monitoring filters.


Version 2.5.00


Configuring the Element StatusThe status of an element is determined by the State parameter and by the status mapping rule. Thismapping rule indicates which states will trigger a warning or an alarm on the Status parameter. Itcan be configured as follows:

1. In the Console, right-click one of the instance for which you want to configure status and select> KM commands > Configuration > Element Status

Deamon Status Configuration Dialog


Version 2.5.00


2. In the Warning Filter State Rules list, select the states that will not trigger a warning

3. If needed, apply a time condition to a specific state. For example, if you want to trigger awarning when the Deamon state is Stopped for more than 60 minutes:

From the State list, select 6 (Stopped)

From the Condition list, select >

In the Minutes field, enter 60

4. In the Alarm Filter State Rules list, select the states that will not trigger an alarm

5. If needed, apply a time condition to a specific state. For example, if you want to trigger an alarmwhen the Deamon state is Not Running for more than 120 minutes:

From the State list, select 9 (Not Running)

From the Condition list, select >

In the Minutes field, enter 120

6. Click Update.

To revert to the default status mapping rule for either filter, select [default] from the list of states and click Update.

7. Resume the procedure for all the application classes for which you wish to apply monitoring filters.


Version 2.5.00


Configuring the Node StatusVVM KM allows you to choose which daemons will be used to determine the node status:

1. In the Console, right-click the Veritas Volume Manager instance > KM Commands >Configuration > Node Status.

Configuring Node Status


Version 2.5.00


2. In the Monitored daemons list, select the daemons that won't be used to determine the nodestatus

3. In the Daemon field, list the daemons to be used to determine the node status. The Daemonlist must be comma-delimited.

4. To use default settings, type [default] in the Daemon field

5. Click Update.

The VVMNodeStatus parameter will then be set to:

Suspicious if any command run by the VVM KM returns a server error message

Failure if any configured daemon is not running. Several recovery actions will then be initiated.

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

Configuring the Log FilterA log error filter can be configured to specify the regular expressions that will generate a warning oran alarm. Each time the KM will find these expressions in a log file or in VVMLogText, the errormessage will be written to the VVMLogAlarmText or VVMLogWarningText parameter. Bydefault, the default log filter is configured for the system log file. If you enabled additional log filesfor monitoring, you will have to customize the log filter by adding appropriate expressions for thoselog files.


Version 2.5.00


To configure the log error filter:

1. In the Console, right-click the Logs instance > KM Commands > Configuration > LogsFilter

Log Filter Configuration dialog

2. In the Warning Filter Expressions list, select the expressions that will not trigger a warning

3. In the Alarm Filter Expressions list, select the expressions that will not trigger an alarm

4. To add a new regular expression to the warning or alarm filter:

In the Expression field, indicate the regular expression to be included (e.g.: skipping)

Select Include

Regular expressions are case-sensitive.


Version 2.5.00


5. To exclude a regular expression from the warning or alarm filter:

In the Expression field, indicate the regular expression to be excluded (e.g.: otlsol01). Youcan also limit the exclusion to a particular expression already listed by using standard wildcardsyntax, such as “skipping . otlsol06”.

Select Exclude

6. Click Update.

Configuring the Log Scan LimitThe VVM KM scans log files by reading the new log entries since the last data collection cycle. Bydefault, only 500 KBytes of data is scanned for each log file during each data collection cycle. This logscan limit can however be modified to better suit your requirements.

Increasing the Log Scan Limit may impact the performance of the data collector (VVMLogCollector), theKM, and the PATROL Agent.

To customize the log scan limit:

1. In the Console, right-click the Log(s) instance > KM Commands > Configuration Log(s)Scan Limit

2. Indicate the amount of data that will be read by the KM during each data collection cycle

3. Click OK.

Configuring Logs Alert AcknowledgementBy default, alerts will automatically be acknowledged unless you modified the settings to allowmanual acknowledgement.

Manual acknowledgement may impact the performance of the application and of the PATROL Agent ifthe number of alerts waiting to be acknowledged constantly increases.

To change the default behavior:

1. In the Console, right-click the Log(s) instance > KM Commands > Configuration> Log(s)Alert Acknowledgement

2. Indicate whether the warning and alarm messages will be manually or automaticallyacknowledged

3. Click Ok.


Version 2.5.00


Using the KM

This section describes all the features available for Veritas Volume Manager KM for PATROL.

Acknowledging AlertsBy default, alerts are acknowledged automatically. If you modified the alert acknowledgement defaultsettings, you'll have to manually acknowledge alerts:

1. In the Console, right-click the Log instance > KM Commands > Acknowledgement

2. Select:

Warning to view, select, and individually acknowledge errors in the VVMLogWarningTextparameter

Alarms to view, select, and individually acknowledge errors in the VVMLogAlarmTextparameter

All to acknowledge all alerts (Warnings and Alarms) at once without viewing.

64Using the KM

Version 2.5.00


Enabling the Debug ModeWhen you encounter an issue and wish to report it to Sentry Software, you will be asked to enablethe Debug Mode and provide the debug output to the Sentry Software support team:

1. In the Console, right-click the Veritas Volume Manager instance > KM Commands >Configuration > Debug.

VVM KM Debug Configuration dialog

65Using the KM

Version 2.5.00


2. Select On for the debug switch(es) you want to enable. The table below shows the applicationclasses and collector parameters included in the debug switch for each object

Object Debug Switch

Application Classes Collector Parameters

Server VVM_SERVER VVMCreateDistributionVVMUpdateAgent

Daemon VVM_DAEMON_CONTAINERVVM_DAEMON

VVMDaemonCollector

Log VVM_LOG_CONTAINERVVM_LOG

VVMLogCollector

Disk Group VVM_DISKGROUP_CONTAINERVVM_DISKGROUP

VVMDiskgroupCollector

Disk Device and Path VVM_DISKDEVICE_CONTAINERVVM_DISKDEVICEVVM_DISPATH

VVMDiskdeviceCollector

Volume VVM_VOLUME_CONTAINERVVM_VOLUME

VVMVolumeCollector

Plex VVM_PLEX VVMPlexCollector

Subdisk VVM_SUBDISK VVMSubdiskCollector

Replicated Volume Group VVM_RVG_CONTAINER VVM_RVG

VVMRvgCollector

Replication Link VVM_RLINK VVMRlinkCollector

3. Set the Debug Options:

In the Debug End Time field, indicate the date and time after which debug information willno longer be logged.

In the Debug Path field, indicate where the debug file will be stored (by default:<PATROL_HOME>/lib/VVM/debug on Unix systems; %PATROL_HOME%\lib\VVM\debug onMicrosoft Windows systems). The debug folder must have at least 10MB of available diskspace and read, write and execute permissions for both PATROL Agent user and the VVM KMlogin user

Select Send to File(s) to write all debug messages in a file or set of files in a specified debugfolder on the managed system (by default: $PATROL_HOME/lib/VVM/debug on Unix systems,%PATROL_HOME%\lib\VVM\debug on MS Windows systems). The debug folder must have atleast 10MB of available disk space and read, write and execute permissions for both PATROLAgent user and the VVM KM login user

Select Send to Task Window to view the debug messages as they occur in the VVM KMDebug Output window. Before selecting this option, make sure the PATROL Console isconnected to the PATROL Agent.

Select Both (Recommended) to send the debug messages both to a file and task window.

4. Click OK first to start the VVM KM debugging

5. Click Yes to reload the KM and capture debug from the initial collection cycle.

Disabling the Debug Mode

The debug switches will be turned off automatically when the debug end time is reached. If you want

66Using the KM

Version 2.5.00


to manually stop debugging:

1. Access the VVM KM Debug Configuration dialog

2. Select Off for the debug switch(es) you want to disable

3. Click OK.

Preparing the Debug Files for Sending to SentrySoftware

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

Right-click in the VVM KM Debug Output window.

Select Save As and specify a location to save data.

If you chose to send debug information to file(s), you will be asked to prepare the debug files forsending to Sentry Software:

Click Yes to compress the files into:

vvm_km_debug_<date>_<time>.tar.Z in folder $PATROL_HOME/lib/VVM/ on Unixsystems

vvm_km_debug_<date>_<time>.zip in folder %PATROL_HOME%\lib\VVM\ on MSWindows systems

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

Generating ReportsFollowing is a list of reports available in the Veritas Volume Manager KM for PATROL.

<Log Instance>=> Reports => Messages List - reports last 100 lines of messages loggedin the associated file instance.

Diskgroups => Reports => Veritas Volume Manager Topology Report - lists all VeritasVolume Manager topology objects

Daemons => Reports => Daemon List Report - lists all Veritas Volume Manager daemonsfound

<Diskgroup Instance> => Reports => Diskgroup Topology Report - lists all VeritasVolume Manager topology objects for a particular diskgroup.

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

67Using the KM

Version 2.5.00


Refreshing ParametersThis section describes how to manually refresh parameters without waiting for an automatic pollingcycle.

Forcing All Discoveries

To force all discoveries, right-click the Veritas Volume Manager instance and select:

Refresh Process Cache to refresh the PATROL Agent process cache

Force Discovery.

The discovery will then be forced on all the KMs loaded on the PATROL Agent and on all the KMapplications classes.

Forcing All Data Collectors

To force all data collectors, right-click the Veritas Volume Manager instance and select:

Refresh Process Cache to refresh the PATROL Agent process cache

Refresh parameters to force all data collectors at the same time.

The VVM KM data collectors and all the data collectors defined under the application classes loadedon the PATROL Agent will then be refreshed.

Forcing Selected Data Collectors

This option is only available from a PATROL Developer Console.

1. Right-click the Veritas Volume Manager instance and select Refresh Process Cache torefresh the PATROL Agent process cache .

2. Force a data collector to execute immediately as follows

With the PATROL Console for MS Windows

Right-click the Veritas Volume Manager instance and choose Parameters withoutIcons...

Select the required data collector.

Click Update.

With the PATROL Console for Unix

Right-click the Veritas Volume Manager instance and choose Customize > Parameters...

Select the required data collector.

Click on Options > Update.

With the PATROL Central Operator Console

Right-click the Veritas Volume Manager instance and choose Properties... .

68Using the KM

Version 2.5.00


Select the tab Parameter List and tick the required data collector.

Click Update.

Reference Guide

70

Version 2.5.00


Introduction

This chapter provides statistical information about resources, operating status, and performancesmanaged by Veritas Volume Manager KM for PATROL. It contains tables describing the parametersused in the KM, grouped by Application Classes, and provides a brief description of each parameterand its default settings.

Classes and Parameters

This section lists the application classes of Veritas Volume Manager KM for PATROL. It gives youdetails on the icons that represent the class, Infobox, parameters and the menu commands availablefor each application class. There are 11 main application classes and 56 “container” classes.

VVM_DAEMON

VVM_DAEMON_CONTAINER

VVM_DISKDEVICE

VVM_DISKDEVICE_CONTAINER

VVM_DISKGROUP

VVM_DISKGROUP_CONTAINER

VVM_DISKPATH

VVM_LOG

VVM_LOG_CONTAINER

VVM_PLEX

VVM_RLINK

VVM_RVG

VVM_RVG_CONTAINER

VVM_SERVER

VVM_SUBDISK

VVM_VOLUME

VVM_VOLUME_CONTAINER

Baselines and Key Performance Indicators

Some parameters are identified by default as Key Performance Indicators (KPIs) and thereforeautomatically included in the base lining calculation. To learn more about auto baselining and KPIs,please refer to the Managing Baselines and Key Performance Indicators chapter.

In this guide, parameters flagged as KPIs and included by default in the baseline calculation processare respectively identified by the following icons:

Baselining

KPI

71Classes and Parameters

Version 2.5.00


VVM_DAEMON

Icon

Parameters

Name Description Units Default AlertConditions

BMCProactiveNetAttribute Type

VVMDaemonCPUDuration

Indicates the CPU secondsconsumed by the daemon.

seconds None Statistics

VVMDaemonCPUUtilizati

on*

Indicates the CPU secondsconsumed by the daemon.

Percentage (%) None Statistics

VVMDaemonMemorySiz

e*

Indicates the core imagesize of the daemon in thevirtual memory.

Kilobytes (KB) None Statistics

VVMDaemonProcessCou

nt

Indicates the number of theprocesses/threads of thedaemon found.

processes None Statistics

VVMDaemonState Indicates the state of thedaemon as reported in thecommand executed by thedata collector.

{0 = Running ;1 = Sleeping ;2 = Waiting ;3 = Queued ;4 = Intermediate ;5 = Terminated ;6 = Stopped/Disabled ;7 = Growing ;8 = Nonexistent/NotResponding ;9 = Not Running ;-1 = Unknown}

None Availability

VVMDaemonStatus Monitors the status of thedaemon. This status isdetermined by the daemonstatus mapping rule definedin the KM commandConfiguration > Daemon(s)Status.If this status parameterchanges to warning or alarmstate, the recovery actionwill trigger an event andannotate the last data point.

{0 = OK ;1 = Suspicious ;2 = Failure}

Warning = 1Alarm = 2

Availability

VVMDaemonSummary Summarizes the daemoninformation as reported bycommands executed by thedata collector.

n/a None n/a

For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.


Version 2.5.00


* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM.

InfoBox

Name Description

Name Name of the Veritas Volume Manager daemon.

Description Description of the Veritas Volume Manager 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.

Collector Name Name of the data collector that sets variables and parameters under this application instance.

Collector LastStart

Date & time when the last data collection cycle started.

Collector LastEnd

Date & time at the completion of the last data collection cycle.

Collector NextStart

Date & time when the next data collection cycle is expected to start.

Collector Status Data collector execution status (Idle or Running).

Menu Commands

Function Description

Configuration > Daemon

Accesses the individual configuration for monitoring the selected daemon instance.This dialog box allows the selected daemon instance to be enabled or disabled for monitoring by theVVM KM.

Configuration > Daemon Status

Accesses the individual configuration for determining daemon status for the selected the daemoninstance.By default, the global VVMDaemonState to VVMDaemonStatus mapping rule is used, as configuredat the container level. Select [default] to revert to the daemon status mapping rule configured at theglobal/container level.


Version 2.5.00


VVM_DAEMON_CONTAINER

Icon

Parameters

Name Description Units DefaultAlertConditions


VVMDaemonDetails

Displays all data returned to the standard output(stdout) from commands executed by the datacollector

n/a None n/a

VVMDaemonCollectorExecTime

Monitors the execution time of the daemoncollector. Inactive by default, this parameter canbe enabled by running the PSL command belowand restarting the PATROL agent:

%PSL pconfig("REPLACE", "/Runtime/VVM/VVMDaemonCollectorExecTime", 1);

Once enabled, this parameter runs every minuteand triggers a warning when the collector runsfor more than the observed maximum time.

To overwrite the maximum time, run the PSLcommand below: %PSL pconfig("REPLACE", "/Runtime/VVM/VVMDaemonCollectorWarn", 3600);

where 3600 must be replaced by the number ofseconds required.

seconds None CollectionStatus

InfoBox

Name Description


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 NextStart




Version 2.5.00


Menu Commands


Reports > Daemon List

Lists all running Veritas Volume Manager daemons.

Configuration > Daemons

Accesses the dialog for specifying which daemons are to be monitored by the VVM KM.By default following daemons are monitored on Unix platforms.

By default following daemons are monitored on Windows platforms.

Type [default] to reset to the default configuration.

Configuration > Daemons Status

Accesses the global configuration for determining the daemon status for monitored daemon instances.By default following VVMDaemonState to VVMDaemonStatus mapping rule is used:

Select [default] to reset to the default mapping rule.


Version 2.5.00


VVM_DISKDEVICE

Icon

Parameters


BMCProactiveNetAttributeType

VVMDiskdeviceIOKBytes

Indicates the totalnumber of KBytestransferred on thediskdevice.


VVMDiskdeviceIO

KBytesRate*

Indicates the number ofKBytes transferred persecond for thediskdevice.

Kilobytes per seconds (KB/s) None Statistics

VVMDiskdeviceIOOperations

Indicates the totalnumber of input andoutput operations on thediskdevice.

operations None Statistics

VVMDiskdeviceIOOperationsFailed

Indicates the totalnumber of failed inputand output operationson the diskdevice onUnix platforms.


VVMDiskdeviceIOOperationsRate

Indicates the number ofinput and outputoperations per secondfor the diskdevice.

operations/second None Statistics

VVMDiskdeviceQu

eueDepth

Indicates the number ofread and write requestsin queue for thediskdevice on Windowsplatforms.

requests None Statistics

VVMDiskdeviceReadKBytes

Indicates the number ofKBytes read on thediskdevice.


VVMDiskdeviceRe

adKBytesRate*

Indicates the number ofKBytes read per secondfor the diskdevice.

Kilobytes per seconds (KB/s) None Statistics

VVMDiskdeviceReadOperations

Indicates the number ofread operations on thediskdevice.



Version 2.5.00




VVMDiskdeviceReadOperationsFaile

d

Monitors the number offailed read operations onthe diskdevice on Unixplatforms. If thisparameter changes towarning or alarm state,the recovery action willtrigger an event.

operations Warning when > 10and < 100

Statistics

VVMDiskdeviceRe

adTime*

Monitors the read timefor the diskdevice. If thisparameter changes towarning or alarm state,the recovery action willtrigger an event.

milliseconds Warning when > 20and < 100

Response Time

VVMDiskdeviceReadTimeAverage*

Monitors the averageread time for thediskdevice.If this parameterchanges to warning oralarm state, therecovery action willtrigger an event.

milliseconds None Statistics

VVMDiskdeviceSpaceAvailable

Indicates the availablespace on the diskdevice.

Gigabytes (GB) None Availability

VVMDiskdeviceState

Indicates the state ofthe diskdevice on Unixplatforms.

{0 = Online ;1 = Online with Errors ;2 = Failing ;3 = Failed ;4 = Offline ;-1 = Unknown}

None Availability

VVMDiskdeviceStateNT

Indicates the state ofthe diskdevice onWindows platforms.

{0 = Online/Imported ;1 = Uninitialized ;2 = Online with Errors ;3 = Failing ;4 = Failed ;5 = Offline ;6 = Foreign ;7 = Detached ;8 = Disconnected ;-1 = Unknown}

None Availability

VVMDiskdeviceStatus

Monitors the status ofthe diskdevice. Thisstatus is determined bythe diskdevice statusmapping rule defined inthe KM commandConfiguration >Diskdevice(s) Status.If this status parameterchanges to warning oralarm state, therecovery action willtrigger an event andannotate the last datapoint.



Availability


Version 2.5.00




VVMDiskdeviceSummary

Summarizes thediskdevice informationas reported bycommands executed bythe data collector.

n/a None n/a

VVMDiskdeviceWriteKBytes

Indicates the number ofKBytes written on thediskdevice.Note: This parameter isnot available for non-dynamic diskgroups on Windowsplatforms.


VVMDiskdeviceWr

iteKBytesRate*

Indicates the number ofKBytes written persecond for thediskdevice.Note: This parameter isnot available for non-dynamic diskgroups on Windowsplatforms.

Kilobytes per second (KB/s) None Statistics

VVMDiskdeviceWriteOperations

Indicates the number ofwrite operations on thediskdevice.Note: This parameter isnot available for non-dynamic diskgroups on Windowsplatforms.


VVMDiskdeviceWriteOperationsFaile

d

Monitors the number offailed write operationson the diskdevice onUnix platforms. If thisparameter changes towarning or alarm state,the recovery action willtrigger an event.

operations Warning when > 10and < 100

Statistics

VVMDiskdeviceWr

iteTime*

Monitors the write timefor the diskdevice. If thisparameter changes towarning or alarm state,the recovery action willtrigger an event.

milliseconds Warning when > 20and < 100

Response Time

VVMDiskdeviceWriteTimeAverage*

Monitors the averagewrite time for thediskdevice. If thisparameter changes towarning or alarm state,the recovery action willtrigger an event.Note: This parameter isnot available for non-dynamic diskgroups on Windowsplatforms.



Version 2.5.00




VVMDiskpathEnabled

Monitors the number ofenabled disk paths withkernel state ENABLED.

count Alarm = 1 Availability

VVMDiskpathNonEnabled

Indicates the number ofdisk paths that are notenabled.

count Warning when > 1 and < 100

Availability



InfoBox

Name Description

Diskdevice Name of the Veritas Volume Manager diskdevice.

Status Status of the Veritas Volume Manager diskdevice.

Group Diskgroup name of the Veritas Volume Manager diskdevice.

Disk Disk name of the Veritas Volume Manager diskdevice.

Device Device name of the Veritas Volume Manager diskdevice.

Type Type of the Veritas Volume Manager diskdevice.

Tag Tag of the Veritas Volume Manager diskdevice.

Offset Offset of the Veritas Volume Manager diskdevice.

Available Space Available space on the Veritas Volume Manager diskdevice.




Collector Next Start Date & time when the next data collection cycle is expected to start.


Menu Commands


Configuration > Diskdevice

Accesses the individual configuration for monitoring the selected diskdevice instance.This dialog allows the selected diskdevice instance to be enabled or disabled for monitoring by theVVM KM.

Configuration > Diskdevice Status

Accesses the individual configuration for determining the status for the selected diskdevice instance.


Version 2.5.00



By default, the global VVMDiskdeviceState[NT] to VVMDiskdeviceStatus mapping rule, or theinherited custom settings configured at a higher level, is used. Select [default] to inherit the customsettings or to reset to the default status mapping rule.

Configuration > Disk Paths

Accesses the global configuration dialog for configuring all monitored disk path instances.By default, all disk paths are monitored.


Configuration > Disk Paths KernelStatus

Accesses the global configuration dialog for determining the Disk Paths Kernel status for monitoreddisk paths instances.

By default, the global VVMDiskpathKernelState[NT] to VVMDiskpathkKernelStatus mappingrule, or the inherited custom settings configured at a higher level, is used. Select [default] to inheritthe custom settings or to reset to the default status mapping rule.

VVM_DISKDEVICE_CONTAINER

Icon

Parameters

None.

InfoBox

Name Description

CollectorName

Name of the data collector that sets variables and parameters under this application instance.

Collector LastStart

Date & time when the last data collection cycle started.

Collector LastEnd

Date & time at the completion of the last data collection cycle.

Collector NextStart


CollectorStatus

Data collector execution status (Idle or Running).

Menu Commands


Version 2.5.00



Configuration> Diskdevices

Accesses the dialog for specifying which diskdevices under the selected diskdevice container instance areto be monitored by the VVM KM.By default, all diskdevices are monitored.

Type [default] to reset any custom configurations from current level and below and inherit customsetting, if any, or revert to default configuration.

Configuration> DiskdevicesStatus

Accesses the configuration dialog for determining the status for monitored diskdevice instances under theselected diskdevice container instance.By default, the global VVMDiskdeviceState[NT] to VVMDiskdeviceStatus mapping rule, or theinherited custom settings configured at a higher level, is used. Select [default] to inherit the customsettings or to reset to the default status mapping rule.

Configuration> Disk Paths



Configuration> Disk PathsKernel Status

Accesses the global configuration dialog for determining the Disk Paths Kernel status for monitored diskpaths instances.

By default, the global VVMDiskpathKernelState[NT] to VVMDiskpathkKernelStatus mapping rule,or the inherited custom settings configured at a higher level, is used. Select [default] to inherit thecustom settings or to reset to the default status mapping rule.

VVM_DISKGROUP

Icon

Parameters



VVMDiskgroupSpaceAvailable*

Indicates the available space forthe diskgroup.

Gigabytes (GB) None Availability

VVMDiskgroupState Indicates the state of thediskgroup on Unix platforms.

{0 = Enabled;1 = Disabled;-1 = Unknown}

None Availability

VVMDiskgroupStateNT Indicates the state of thediskgroup on Windowsplatforms.

{0 = Imported;1 = Deported ;1 = Unknown}

None Availability

VVMDiskgroupStatus Monitors the status of thediskgroup. This status isdetermined by the diskgroupstatus mapping rule defined inthe KM command Configuration> Diskgroup(s) Status.



Availability


Version 2.5.00




If this status parameter changesto warning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.

VVMDiskgroupSummary Summarizes the diskgroupinformation as reported bycommands executed by the datacollector.

n/a None n/a


InfoBox

Name Description

Name Name of the Veritas Volume Manager diskgroup.

Status State of the Veritas Volume Manager diskgroup.

ID ID of the Veritas Volume Manager diskgroup.

Type Type of the Veritas Volume Manager diskgroup.




Collector NextStart



Menu Commands


Reports > DiskgroupTopology Report

Reports all Veritas Volume Manager topology objects for the selected diskgroup.

Configuration > Diskgroup

Accesses the individual configuration for monitoring the selected diskgroup instance.This dialog allows the selected diskgroup instance to be enabled or disabled for monitoring by the VVMKM.

Configuration > Diskgroup Status

Accesses the individual configuration for determining diskgroup status for the selected diskgroupinstance.By default, the global VVMDiskgroupState[NT] to VVMDiskgroupStatus mapping rule, or theinherited custom settings configured at a higher level, is used. Select [default] to inherit the customsetttings or to reset to the default status mapping rule.

Configuration > Disk Devices

Accesses the dialog for specifying which diskdevices under the selected diskgroup instance are to bemonitored by the VVM KM.By default, all diskdevices are monitored.


Version 2.5.00


Type [default] to reset any custom configurations from current level and below and inherit customsetting, if any, or revert to default configuration.Refer to the User Guide for PATROL Knowledge Module for Veritas Volume Manager by SentrySoftware for more details.

Configuration > Disk DevicesStatus

Accesses the configuration dialog for determining the status for monitored diskdevice instances underthe selected diskgroup instance.By default, the global VVMDiskdeviceState[NT] to VVMDiskdeviceStatus mapping rule, or the inheritedcustom settings configured at a higher level, is used. Select [default] to inherit the custom settings orto reset to the default status mapping rule.

Configuration > Disk Paths



Configuration > Disk Paths KernelStatus


By default, the global VVMDiskpathKernelState[NT] to VVMDiskpathkKernelStatus mappingrule, or the inherited custom settings configured at a higher level, is used. Select [default] to inheritthe custom settings or to reset to the default status mapping rule.

Configuration > Volumes

Accesses the dialog for specifying which volumes under the selected diskgroup instance are to bemonitored by the VVM KM.By default, all volumes are monitored.Type [default] to reset any custom configurations from current level and below and inherit customsetting, if any, or revert to default configuration.

Configuration > Volumes Status

Accesses the configuration dialog for determining the status for monitored volume instances under theselected diskgroup instance.By default, the global VVMVolumeState[NT] to VVMVolumeStatus mapping rule, or the inheritedcustom settings configured at a higher level, is used. Select [default] to inherit the custom settings orto reset to the default status mapping rule.

Configuration > Volumes KernelStatus

Accesses the configuration dialog for determining the kernel status for monitored volume instancesunder the selected diskgroup instance.By default, the global VVMVolumeKernelState[NT] to VVMVolumeKernelStatus mapping rule,or the inherited custom settings configured at a higher level, is used. Select [default] to inherit thecustom settings or to reset to the default status mapping rule.

Configuration > Volumes LoggingStatus (Unix only)

Accesses the configuration dialog for determining the logging status for monitored volume instancesunder the selected diskgroup instance.By default, the global VVMVolumeLoggingState to VVMVolumeLoggingStatus mapping rule, orthe inherited custom settings configured at a higher level, is used. Select [default] to inherit thecustom settings or to reset to the default status mapping rule.

Configuration > Plexes

Accesses the dialog for specifying which plexes under the selected diskgroup instance are to bemonitored by the VVM KM.By default, all plexes are monitored.Type [default] to reset any custom configurations from current level and below and inherit customsetting, if any, or revert to default configuration.

Configuration > Plexes Status

Accesses the configuration dialog for determining the status for monitored plex instances under theselected diskgroup instance.By default, the global VVMPlexState[NT] to VVMPlexStatus mapping rule, or the inherited customsettings configured at a higher level, is used. Select [default] to inherit the custom settings or toreset to the default status mapping rule.

Configuration > Plexes KernelStatus

Accesses the configuration dialog for determining the kernel status for monitored plex instances underthe selected diskgroup instance.By default, the global VVMPlexKernelState[NT] to VVMPlexKernelStatus mapping rule, or theinherited custom settings configured at a higher level, is used. Select [default] to inherit the customsettings or to reset to the default status mapping rule.

Configuration > Subdisks

Accesses the dialog for specifying which subdisks under the selected diskgroup instance are to bemonitored by the VVM KM.


Version 2.5.00


By default, all subdisks are monitored.Type [default] to reset any custom configurations from current level and below and inherit customsetting, if any, or revert to default configuration.

Configuration > Subdisks KernelStatus

Accesses the configuration dialog for determining the kernel status for monitored subdisk instancesunder the selected diskgroup instance.By default, the global VVMSubdiskKernelState[NT] to VVMSubdiskKernelStatus mapping rule,or the inherited custom settings configured at a higher level, is used. Select [default] to inherit thecustom settings or to reset to the default status mapping rule.

Configuration > Replicated VolumeGroups

Accesses the configuration dialog for specifying which replicated volume groups under the selecteddisk group instance are to be monitored by the VVM KM. By default, all replicated volume groups aremonitored. Type [default] to reset any custom configurations from current level and below andinherit custom setting, if any, or revert to default configuration.

Configuration >Replicated VolumeGroups Status

Accesses the global configuration for determining the replicated volume group status for monitoredreplicated volume group instances.By default, the following VVMRvgState to VVMRvgStatusmapping rule is used:

Configuration > Replicated VolumeGroups KernelStatus

Accesses the global configuration for determining the replicated volume group kernel status formonitored replicated volume group instances.By default, the following VVMRvgKernelState to VVMRvgKernelStatus mapping rule is used:

Configuration > Replication Links

Accesses the dialog for specifying which replication links under the selected disk group instance are tobe monitored by the VVM KM. By default, all replication links are monitored. Type [default] to resetany custom configurations from current level and below and inherit custom setting, if any, or revert todefault configuration.

Configuration > Replication LinksStatus

Accesses the global configuration for determining the replication link status for monitored replicationlink instances.By default, the following VVMRlinkState to VVMRlinkStatus mapping rule is used:

Configuration > Replication LinksKernel Status

Accesses the global configuration for determining the replication link kernel status for monitoredreplication link instances.By default, the following VVMRlinkKernelState to VVMRlinkKernelStatus mapping rule is used:


Version 2.5.00


VVM_DISKGROUP_CONTAINER

Icon

Parameters



VVMDiskdeviceCollectorExecTime

Monitors the execution time of the disk devicecollector. Inactive by default, this parameter can beenabled by running the PSL command below andrestarting the PATROL agent:

%PSL pconfig("REPLACE", "/Runtime/VVM/VVMDiskdeviceCollectorExecTime", 1);

Once enabled, this parameter runs every minute andtriggers a warning when the collector runs for morethan the observed maximum time.

To overwrite the maximum time, run the PSLcommand below: %PSL pconfig("REPLACE", "/Runtime/VVM/VVMDiskdeviceCollectorWarn", 3600);


seconds Warningwhen >preset valueor observedmaximum(default)

CollectionStatus

VVMDiskdeviceDetails Displays all data returned to the standard output(stdout) from commands executed by the datacollector

n/a None n/a

VVMDiskgroupCollectorExecTime

Monitors the execution time of the disk groupcollector. Inactive by default, this parameter can beenabled by running the PSL command below andrestarting the PATROL agent:

%PSL pconfig("REPLACE", "/Runtime/VVM/VVMDiskgroupCollectorExecTime", 1);


To overwrite the maximum time, run the PSLcommand below: %PSL pconfig("REPLACE", "/Runtime/VVM/VVMDiskgroupCollectorWarn", 3600);



CollectionStatus

VVMDiskgroupDetails Displays all data returned to the standard out fromcommands executed by the data collector.

n/a None n/a


Version 2.5.00




VVMPlexCollectorExecTime

Monitors the execution time of the plex collector.Inactive by default, this parameter can be enabledby running the PSL command below and restartingthe PATROL agent:

%PSL pconfig("REPLACE", "/Runtime/VVM/VVMPlexCollectorExecTime", 1);


To overwrite the maximum time, run the PSLcommand below: %PSL pconfig("REPLACE", "/Runtime/VVM/VVMPlexCollectorWarn", 3600);



CollectionStatus

VVMPlexDetails Displays all data returned to the standard output(stdout) from commands executed by the datacollector

n/a None n/a

VVMRlinkCollectorExecTime

Monitors the execution time of the Rlink collector.Inactive by default, this parameter can be enabledby running the PSL command below and restartingthe PATROL agent:

%PSL pconfig("REPLACE", "/Runtime/VVM/VVMRlinkCollectorExecTime", 1);


To overwrite the maximum time, run the PSLcommand below: %PSL pconfig("REPLACE", "/Runtime/VVM/VVMRlinkCollectorWarn", 3600);

where 3600 must be replaced by the number ofseconds required


CollectionStatus

VVMRlinkDetails Displays all data returned to the standard output(stdout) from commands executed by the datacollector

n/a None CollectionStatus

VVMRvgCollectorExecTime

Monitors the execution time of the RVG collector.Inactive by default, this parameter can be enabledby running the PSL command below and restartingthe PATROL agent:

%PSL pconfig("REPLACE", "/Runtime/VVM/VVMRvgCollectorExecTime", 1);


seconds None CollectionStatus


Version 2.5.00




To overwrite the maximum time, run the PSLcommand below: %PSL pconfig("REPLACE", "/Runtime/VVM/VVMRvgCollectorWarn", 3600);


VVMRvgDetails Displays all data returned to the standard output(stdout) from commands executed by the datacollector

n/a None CollectionStatus

VVMSubdiskCollectorExecTime

Monitors the execution time of the subdisk collector.Inactive by default, this parameter can be enabledby running the PSL command below and restartingthe PATROL agent:

%PSL pconfig("REPLACE", "/Runtime/VVM/VVMSubdiskCollectorExecTime", 1);


To overwrite the maximum time, run the PSLcommand below: %PSL pconfig("REPLACE", "/Runtime/VVM/VVMSubdiskCollectorWarn", 3600);



CollectionStatus

VVMSubdiskDetails Displays all data returned to the standard output(stdout) from commands executed by the datacollector

n/a None n/a

VVMVolumeCollectorExecTime

Monitors the execution time of the volume collector.Inactive by default, this parameter can be enabledby running the PSL command below and restartingthe PATROL agent:

%PSL pconfig("REPLACE", "/Runtime/VVM/VVMVolumeCollectorExecTime", 1);


To overwrite the maximum time, run the PSLcommand below: %PSL pconfig("REPLACE", "/Runtime/VVM/VVMVolumeCollectorWarn", 3600);



CollectionStatus

VVMVolumeDetails Displays all data returned to the standard output(stdout) from commands executed by the datacollector

n/a None n/a


Version 2.5.00


InfoBox

Name Description






Menu Commands


Reports > VeritasVolume ManagerTopology Report

Reports all Veritas Volume Manager topology objects.

Configuration > Diskgroups

Accesses the global configuration dialog for specifying which diskgroups are to be monitored bythe VVM KM.By default, all diskgroups are monitored.Type [default] to reset to the default configuration.

Configuration > Diskgroups Status

Accesses the global configuration dialog for determining the diskgroup status for monitoreddiskgroup instances.

By default, the following VVMDiskgroupState to VVMDiskgroupStatus mapping rule is usedon Unix platforms:

By default, the following VVMDiskgroupStateNT to VVMDiskgroupStatus mapping rule isused on Windows platforms:

Select [default] to reset to the default diskgroup status mapping rule.

Configuration > DiskDevices

Accesses the global configuration dialog for specifying which diskdevices are to be monitored bythe VVM KM.By default, all diskdevices are monitored.


Configuration > DiskDevices Status

Accesses the global configuration dialog for determining the diskdevice status for monitoreddiskdevice instances.By default, the following VVMDiskdeviceState to VVMDiskdeviceStatus mapping rule is usedon Unix platforms:


Version 2.5.00



By default, the following VVMDiskdeviceStateNT to VVMDiskdeviceStatus mapping rule isused on Windows platforms:

Select [default] to reset to the default diskdevice status mapping rule.

Configuration > DiskPaths



Configuration > DiskPaths Kernel Status

Accesses the global configuration dialog for determining the Disk Paths Kernel status formonitored disk paths instances.

By default, the global VVMDiskpathKernelState[NT] to VVMDiskpathkKernelStatusmapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule.

Configuration > Volumes

Accesses the global configuration dialog for specifying which volumes are to be monitored by theVVM KM.By default, all volumes are monitored.


Configuration > Volumes Status

Accesses the global configuration dialog for determining the volume status for monitored volumeinstances.By default, the following VVMVolumeState to VVMVolumeStatus mapping rule is used onUnix platforms:

By default, the following VVMVolumeStateNT to VVMVolumeStatus mapping rule is used onWindows platforms:

Select [default] to reset to the default volume status mapping rule.

Configuration > Volumes Kernel Status

Accesses the global configuration dialog for determining the volume kernel status for monitoredvolume instances.By default, the following VVMVolumeKernelState to VVMVolumeKernelStatus mapping ruleis used on Unix platforms:


Version 2.5.00



By default, the following VVMVolumeKernelStateNT to VVMVolumeKernelStatus mappingrule is used on Windows platforms:

Select [default] to reset to the default volume kernel status mapping rule.

Configuration > Volumes LoggingStatus (UNIX only)

Accesses the global configuration dialog for determining the volume logging status for monitoredvolume instances.By default, the following VVMVolumeLoggingState to VVMVolumeLoggingStatus mappingrule is used:

Select [default] to reset to the default volume logging status mapping rule.

Configuration > Plexes Accesses the global configuration dialog for specifying which plexes are to be monitored by theVVM KM.By default, all plexes are monitored.


Configuration > Plexes Status

Accesses the global configuration dialog for determining the plex status for monitored plexinstances.By default, the following VVMPlexState to VVMPlexStatus mapping rule is used on Unixplatforms:

By default, the following VVMPlexStateNT to VVMPlexStatus mapping rule is used onWindows platforms:

Select [default] to reset to the default plex status mapping rule.

Configuration > Plexes Kernel Status

Accesses the global configuration dialog for determining the plex kernel status for monitored plexinstances.By default, the following VVMPlexKernelState to VVMPlexKernelStatus mapping rule is usedon Unix platforms:


Version 2.5.00



By default, the following VVMPlexKernelStateNT to VVMPlexKernelStatus mapping rule isused on Windows platforms:

Select [default] to reset to the default plex kernel status mapping rule.


Accesses the dialog for specifying which plexes are to be monitored by the VVM KM.By default, all subdisks are monitored.


Configuration > Subdisks Kernel Status

Accesses the global configuration dialog for determining the subdisk kernel status for monitoredsubdisk instances.By default, the following VVMSubdiskKernelState to VVMSubdiskKernelStatus mapping ruleis used on Unix platforms:

By default, the following VVMSubdiskKernelStateNT to VVMSubdiskKernelStatus mappingrule is used on Windows platforms:

Select [default] to reset to the default subdisk kernel status mapping rule.

Configuration >Replicated VolumeGroups

Accesses the global configuration for determining the replicated volume group status for

monitored replicated volume group instances. By default, the following VVMRvgState to

VVMRvgStatus mapping rule is used:

Configuration > Replicated VolumeGroups Kernel Status

Accesses the global configuration for determining the replicated volume group status for

monitored replicated volume group instances. By default, the following VVMRvgState to

VVMRvgStatus mapping rule is used:


Version 2.5.00




Accesses the dialog for specifying which replication links are to be monitored by the VVM KM. Bydefault, all replication links are monitored. Type [default] to reset to default configuration.

Configuration >Replication LinksStatus

Accesses the global configuration for determining the replication link status for monitoredreplication link instances. By default, the following VVMRlinkState to VVMRlinkStatus mappingrule is used:

Configuration > Replication LinksKernel Status

Accesses the global configuration for determining the replication link kernel status for monitoredreplication link instances. By default, the following VVMRlinkKernelState to VVMRlinkKernelStatusmapping rule is used:


Version 2.5.00


VVM_DISKPATH

Icon

Parameters



VVMDiskpathKernelState Indicates the kernel state of thediskpath on Unix platforms

{0 = Enabled ; 1 = Detached ; 2 = Disabled ;-1 = Unknown}

None Availability

VVMDiskpathKernelStateNT

Indicates the kernel state of thesubdisk on Windows platforms.

{0 = Enabled ; 1 = Unreported/Undefined ;2 = Error ; 3 = Disabled ; -1 = Unknown}

None Availability

VVMDiskpathKernelStatus Monitors the kernel status of the diskpaths. This status is determined by thesubpath status mapping rule defined inthe KM command Configuration > DiskPath(s) Kernel Status. If this statusparameter changes to warning or alarmstate, the recovery action will trigger anevent and annotate the last data point.



Availability

VVMDiskpathSummary Summarizes the diskpath informationas reported by commands executed bythe data collector.

n/a None n/a

InfoBox

Name Description

Path Veritas Volume Manage disk path.

Kernel State Kernel state of the Veritas Volume Manage disk path.

Group Diskgroup name of the Veritas Volume Manager diskdevice.

Disk Disk name of the Veritas Volume Manager diskdevice.

Disk Access Name Disk device name that is known to the operating system.

Collector Name Name of the data collector that sets variables and parameters under this application instance



Version 2.5.00


Name Description




Menu Commands


Configuration > DiskPath



Configuration > DiskPath Kernel Status


By default, the global VVMDiskpathKernelState[NT] to VVMDiskpathkKernelStatus mappingrule, or the inherited custom settings configured at a higher level, is used. Select [default] toinherit the custom settings or to reset to the default status mapping rule.

VVM_LOG

Icon

Parameters



VVMLogAlarmCount*

Monitors the number of alarm messages set in theparameter VVMLogAlarmText. If this parameterchanges to alarm state, the recovery action will triggeran event.

count Alarm when> 1 and <100

Statistics

VVMLogAlarmText Displays all alarm messages in the log file which havenot been acknowledged. The filter used by the datacollector to determine alarm messages can becustomized using the KM command Configuration >Log(s) Filter.

n/a None n/a


Version 2.5.00




These alarm messages can be acknowledged

automatically (default) or manually, depending on theconfiguration in the KM command Configuration >Log(s) Alert Acknowledgement. Manualacknowledgement is available under the KM sub-

menuAcknowledgement.

VVMLogFSSpaceUs

edPercent*

Monitors the percentage of space used by the filesystem (where the log file resides).If this parameter changes to warning or alarm state,the recovery action will trigger an event.

Percentage (%) Warningwhen > 95and < 98Alarm when> 98 and <100

Statistics

VVMLogSpaceAvailable

Monitors the available space for the log file to use (thisis also the available space on the file system).If this parameter changes to warning or alarm state,the recovery action will trigger an event.

Megabytes (MB) Warningwhen > 2 and < 5Alarm when> -1 and <2

Availability

VVMLogSpaceGrowthRate

Displays the growth rate of the amount of space usedby the log file.

Kilobytes perseconds (KB/s)

None Statistics

VVMLogSpaceUsed Displays the amount of space used by the log file. Kilobytes (KB) None Statistics

VVMLogSpaceUsed

Percent*

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(VVMLogSpaceUsed) plus available space(VVMLogSpaceAvailable).

Percentage (%) Warningwhen > 95and < 98Alarm when> 98

Statistics

VVMLogSummary Summarizes the log file information as reported bycommands executed by the data collector.

n/a None n/a

VVMLogText Displays all log text scanned by the data collectorduring the last collection cycle. The size of the datascanned by the data collector is configured in the KMcommand Configuration > Log(s) Scan Limit.

n/a None n/a

VVMLogWarningCount*

Monitors the number warning messages set in theparameter VVMLogWarningText. If this parameterchanges to a warning state, the recovery action willtrigger an event.

count Warningwhen > 1

Statistics

VVMLogWarningText

Displays all warning messages in the log file which havenot been acknowledged. The filter used by the datacollector to determine warning messages can becustomized using the KM command Configuration >Log(s) Filter.These warning messages can be acknowledgedautomatically (default) or manually, depending on the

configuration in the KM command Configuration >

Log(s) Alert Acknowledgement. Manualacknowledgement is available under the KM sub-menuAcknowledgement.

n/a None n/a



Version 2.5.00



InfoBox

Name Description

Name Name of the Veritas Volume Manager log file.

Description Description of the Veritas Volume Manager log file.

Path Full file path of the log file.

Log File ModificationTime

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.






Menu Commands


Acknowledgement> 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 fileand sent to the text parameter VVMLogWarningText.

Acknowledgement> 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 andsent to the text parameter VVMLogAlarmText.

Acknowledgement> All

Allows acknowledgement of all alarm and warning messages detected on the selected log fileinstance.This dialog allows acknowledgement of all error messages detected in the log file and sent to the textparameter VVMLogWarningText or VVMLogAlarmText.

Configuration > 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 VVM KM.

Configuration > LogFilter

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.


Version 2.5.00



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

Configuration > LogAlertAcknowledgement

Accesses the individual configuration of the method of acknowledgement for alerts on the selectedlog file instance.By default, the global method of log error acknowledgement is used, as configured at the containerlevel.

Refer to the User Guide for Veritas Volume Manager KM for PATROL by Sentry Software for moredetails.

VVM_LOG_CONTAINER

Icon

Parameters



VVMLogCollectorExecTime

Monitors the execution time of the log collector. Inactive bydefault, this parameter can be enabled by running the PSLcommand below and restarting the PATROL agent:

%PSL pconfig("REPLACE", "/Runtime/VVM/VVMLogCollectorExecTime", 1);

Once enabled, this parameter runs every minute and triggersa warning when the collector runs for more than theobserved maximum time.

To overwrite the maximum time, run the PSL commandbelow: %PSL pconfig("REPLACE", "/Runtime/VVM/VVMLogCollectorWarn", 3600);

where 3600 must be replaced by the number of secondsrequired.

seconds Warning > presetvalue orobservedmaximum(default)

CollectionStatus

VVMLogDetails Displays all data returned to the standard output (stdout)from commands executed by the data collector

n/a None n/a

InfoBox

Name Description



Version 2.5.00


Name Description





Menu Commands


Reports > Messages List

Reports the last 100 lines logged in the associated log file.

Configuration > Logs

Accesses the dialog for specifying which log files are to be monitored by the VVM KM.By default, following log files are monitored. These log file paths are relative to the Veritas VolumeManager installation directory (for example /opt/VRTSvxvm on HP-UX), unless the path is fullyqualified as for the system log on Solaris and HP-UX.


Configuration > Logs Filter

Accesses the global configuration of the filter for expressions used for detecting error messages in themonitored log file instances.By default, the following "Included" expressions are looked for in each log file. If detected, themessage containing the expression is added to the appropriate text parameter, unless the messagealso contains an "Excluded" expression for the same filter.



Version 2.5.00



Configuration > Logs Scan Limit

Accesses the global configuration of the data scanning limit for monitored log file instances.By default, the log collector only scans 5 KBytes of new log data for each monitored log file duringeach data collection cycle.

Configuration > Logs AlertAcknowledgement

Accesses the global configuration of the method of acknowledgement for alerts on monitored log fileinstances.By default, the log collector automatically acknowledges previous log alerts (warnings and alarms)when it detects new errors.

VVM_PLEX

Icon

Parameters



VVMPlexIOKBytes Indicates the total numberof KBytes transferred on theplex.


VVMPlexIOKBytesRate* Indicates the number ofKBytes transferred persecond for the plex on Unixplatforms.

Kilobytes per second(KB/s)

None Statistics

VVMPlexIOOperations Indicates the total numberof input and outputoperations on the plex onUnix platforms.


VVMPlexIOOperationsFailed

Indicates the total numberof failed input and outputoperations on the plex onUnix platforms.


VVMPlexIOOperationsRate

Indicates the number ofinput and output operationsper second for the plex onUnix platforms.


VVMPlexKernelState Indicates the kernel state ofthe plex on Unix platforms.


None Availability


Version 2.5.00




VVMPlexKernelStateNT Indicates the kernel state ofthe plex on Windowsplatforms.

{0 = Enabled ;1 = Unreported/Undefined ;2 = Error ; 3 = Disabled ;-1 = Unknown}

None Availability

VVMPlexKernelStatus Monitors the kernel status ofthe plex. This status isdetermined by the plexstatus mapping rule definedin the KM commandConfiguration > Plex(s)Kernel Status.If this status parameterchanges to warning oralarm state, the recoveryaction will trigger an eventand annotate the last datapoint.

{0 = OK ; 1 = Suspicious ; 2 = Failure}


Availability

VVMPlexReadKBytes Indicates the number ofKBytes read on the plex onUnix platforms.


VVMPlexReadKBytesRate* Indicates the number ofKBytes read per second forthe plex on Unix platforms.


None Statistics

VVMPlexReadOperations Indicates the number ofread operations on the plexon Unix platforms.


VVMPlexReadOperationsFailed

Monitors the number offailed read operations onthe plex on Unix platforms.If this parameter changes towarning or alarm state, therecovery action will triggeran event.

operations Warning when> 10

Statistics

VVMPlexReadTime* Monitors the read time forthe plex on Unix platforms.If this parameter changes towarning or alarm state, therecovery action will triggeran event.

milliseconds Warning when> 20

ResponseTime

VVMPlexReadTimeAverage* Monitors the average readtime for the plex on Unixplatforms.If this parameter changes towarning or alarm state, therecovery action will triggeran event.



Version 2.5.00




VVMPlexState Displays the state of theplex on Unix platforms.

{0 = Active ; 1 = Clean ;2 = Empty ;3 = Log Plex ;4 = Temporary Plex ;5 = Snapshot Plex ;6 = No Disk/Device ;7 = Recover ;8 = Removed ;9= Stale ;10= Offline ;11 = I/O Failure ;-1 = Unknown}

None Availability

VVMPlexStateNT Displays the state of theplex on Windows platforms.

{0 = Active/Attached ; 1 = Recoverable ;2 = Failed ;-1 = Unknown}

None Availability

VVMPlexStatus Monitors the status of theplex. This status isdetermined by the plexstatus mapping rule definedin the KM commandConfiguration > Plex(s)Status.If this status parameterchanges to warning oralarm state, the recoveryaction will trigger an eventand annotate the last datapoint.



Availability

VVMPlexSummary Summarizes the plexinformation as reported bycommands executed by thedata collector.

n/a None n/a

VVMPlexWriteKBytes Indicates the number ofKBytes written on the plexon Unix platforms.


VVMPlexWriteKBytesRate* Indicates the number ofKBytes written per secondfor the plex on Unixplatforms.


None Statistics

VVMPlexWriteOperations Indicates the number ofwrite operations on the plexon Unix platforms.


VVMPlexWriteOperationsFaile

d

Monitors the number offailed write operations onthe plex on Unix platforms.If this parameter changes towarning or alarm state, therecovery action will triggeran event.

operations Warning: 10-100Alarm if out of[0 to 100]range.

Statistics


Version 2.5.00




VVMPlexWriteTime* Monitors the write time forthe plex on Unix platforms.If this parameter changes towarning or alarm state, therecovery action will triggeran event.

milliseconds Warning: 20-100Alarm if out of[0 to 100]range.

ResponseTime

VVMPlexWriteTimeAverage* Monitors the average writetime for the plex on Unixplatforms. If this parameterchanges to warning oralarm state, the recoveryaction will trigger an event.




InfoBox

Name Description

Plex Name of the Veritas Volume Manager plex.

Status Status of the Veritas Volume Manager plex.

Group Diskgroup name of the Veritas Volume Manager plex.

Volume Volume name of the Veritas Volume Manager plex.

KState Kernel state of the Veritas Volume Manager plex.

Length Length of the Veritas Volume Manager plex.

Type Type of the Veritas Volume Manager plex.






Menu Commands


Configuration > Plex Accesses theplexe individual configuration for monitoring the selected plex instance.This dialog allows the selected plex instance to be enabled or disabled for monitoring by the VVM KM.


Version 2.5.00



Configuration > PlexStatus

Accesses the individual configuration for determining the status for the selected plex instance.By default, the global VVMPlexState[NT] to VVMPlexStatus mapping rule, or the inherited customsettings configured at a higher level, is used. Select [default] to inherit the custom settings or toreset to the default status mapping rule.

Configuration > PlexKernel Status

Accesses the configuration dialog for determining the kernel status for the selected plex instance.By default, the global VVMPlexKernelState[NT] to VVMPlexKernelStatus mapping rule, or theinherited custom settings configured at a higher level, is used. Select [default] to inherit thecustom settings or to reset to the default status mapping rule.


Accesses the dialog for specifying which subdisks under the selected plex instance are to bemonitored by the VVM KM.By default, all subdisks are monitored.Type [default] to reset any custom configurations from current level and below and inherit customsetting, if any, or revert to default configuration.

Configuration > Subdisks Kernel Status

Accesses the configuration dialog for determining the kernel status for monitored subdiskinstances under the selected plex instance.By default, the global VVMSubdiskKernelState[NT] to VVMSubdiskKernelStatus mapping rule, orthe inherited custom settings configured at a higher level, is used. Select [default] to inherit thecustom settings or to reset to the default status mapping rule.

VVM_RLINK

Icon

Parameters



VVMRlinkKernelState Set by VVMRlinkCollector. Displays the kernel stateof the replication link.

{0 = Connect ;1 = Enabled ;2 = Recover ;3 = Detached ;-1 = Unknown}

None Availability

VVMRlinkKernelStatus Set by VVMRlinkCollector. Displays the kernel statusof the replication link.

{0 = OK ;1 = Suspicious;2 = Failure}


Availability

VVMRlinkRemainingUp

datesCount

Set by VVMRlinkCollector. Displays the number ofupdates the primary RVG is ahead of the secondaryRVG.

updates None Statistics

VVMRlinkRemainingUp

datesLag

Set by VVMRlinkCollector. Displays the amount oftime the secondary RVG is lagging.

seconds None Statistics


Version 2.5.00




VVMRlinkRemainingUp

datesPercent*

Set by VVMRlinkCollector. Displays the percentageof the SRL yet to be replicated to the secondaryreplicated volume group. The parameter is collectedonly on the primary node and will be left offline(greyed-out) on secondary nodes.

Percentage(%)

Warningwhen > 80and < 90Alarm when> 90

Statistics

VVMRlinkRemainingUp

datesSize*

Set by VVMRlinkCollector. Displays the size of theSRL in KBytes.

Kilobytes(KBytes)

None Statistics

VVMRlinkState Set by VVMRlinkCollector. Displays the state of thereplication link.

{0 = Active ;1 = Unassoc ;2 = Stale ;3 = Pausing ;4 = Resuming ;5 = Restoring ;6 =Pause ;7 = Fail ;-1 = Unknown}

None Availability

VVMRlinkStatus Set by VVMRlinkCollector. Displays the status of thereplication link.


None Availability

VVMRlinkSummary Summarizes the Rlink information as reported bycommands executed by the data collector.

n/a n/a



InfoBox

Name Description

Rlink Name of the Veritas Volume Manager Replication Link.

Type Type of the Replicated Volume Group (Primary/Secondary).

Status Status of the Replication Link.

RVG Name of the RVG the Replication Link belongs to.

Group Name of the disk group name the Replication Link belongs to.

Kernel State Kernel state of the Replication Link.

Synchronous Synchronous settings for the Replication Link.

Latency Protection Latency Protection for the Replication Link.

SRL OverflowProtection

SRL overflow protection for the Replication Link.

Local Host Name of the local host.

Remote Host Name of the remote host.


Version 2.5.00


Name Description



Collector Last End Date & time when the last data collection cycle completed.



Menu Commands


Configuration >Replication Links

Accesses the individual configuration for monitoring the selected Replication Link instance. Thisdialog box allows the selected RLink instance to be enabled or disabled for monitoring by the VVMKM.

Configuration > Replication Link Status

Accesses the individual configuration for determining the status for the selected Replication Linkinstance. By default, the global VVMRlinkState to VVMRlinkStatus mapping rule, or the inheritedcustom settings configured at a higher level, is used. Select [default] to inherit the customsettings or to reset to the default status mapping rule.

Configuration > Replication Link KernelStatus

Accesses the individual configuration for determining the kernel status for the selected ReplicationLink instance. By default, the global VVMRlinkKernelState to VVMRlinkKernelStatus mapping rule,or the inherited custom settings configured at a higher level, is used. Select [default] to inheritthe custom settings or to reset to the default status mapping rule.

VVM_RVG

Icon

Parameters



VVMRvgKernelState Set by VVMRvgCollector. Displays the kernel state ofthe replicated volume group.

{0 = Enabled ;1 = Recover ;2 = Disabled ;-1 = Unknown}

None Availability

VVMRvgKernelStatus Set by VVMRvgCollector. Displays the kernel statusof the replicated volume group.



Availability


Version 2.5.00




VVMRvgRlinkCount* Set by VVMRvgCollector. Displays the number ofreplication links in the replicated volume group.

rlinks None Availability

VVMRvgState Set by VVMRvgCollector. Displays the state of thereplicated volume group.

{0 = Active ;1 = Empty ;2 = Clean ;3 = Fail ;-1 = Unknown}

None Availability

VVMRvgStatus Set by VVMRvgCollector. Displays the status of thereplicated volume group.



Availability

VVMRvgSummary Summarizes the replicated volume groupinformation as reported by commands executed bythe data collector.

n/a None Availability

VVMRvgVolumeCount* Set by VVMRvgCollector. Displays the number ofreplicated data volumes.

volumes None Availability



InfoBox

Name Description

RVG Name of the Veritas Volume Manager Replicated Volume Group.

Type Type of the Replicated Volume Group (Primary/Secondary).

Status Status of the Replicated Volume Group.

Group Name of the disk group the Replicated Volume Group belongs to.

Kernel State Kernel state of the Replicated Volume Group.

Data Volumes Names of the data volumes in the Replicated Volume Group.

SRL Name of the Storage Replicator Log.



Collector Last End Date & time when the last data collection cycle completed.



Menu Commands


Version 2.5.00



Configuration > Replicated VolumeGroup

Accesses the individual configuration for monitoring the selected Replication Volume Groupinstance.

Configuration > Replicated VolumeGroup Status

Accesses the individual configuration for determining the status for the selected RVG instance. Bydefault, the global VVMRvgState to VVMRvgStatus mapping rule, or the inherited custom settingsconfigured at a higher level, is used. Select [default] to inherit the custom settings or to reset tothe default status mapping rule.

Configuration >Replicated VolumeGroup Kernel Status

Accesses the individual configuration for determining the kernel status for the selected RVGinstance. By default, the global VVMRvgKernelState to VVMRvgKernelStatus mapping rule, or theinherited custom settings configured at a higher level, is used. Select [default] to inherit thecustom settings or to reset to the default status mapping rule.


Sets which replication links of the selected RVG are to be monitored by the VVM KM. By default,all replication links are monitored.

Configuration >Replication LinksStatus

Accesses the individual configuration for determining the replication links status for the selectedRVG instance. By default, the global VVMRlinkState to VVMRlinkStatus mapping rule, or theinherited custom settings configured at a higher level, is used. Select [default] to inherit thecustom settings or to reset to the default status mapping rule.

Configuration >Replication LinksKernel Status

Accesses the individual configuration for determining the replication links kernel status for theselected RVG instance. By default, the global VVMRlinkKernelState toVVMRlinkKernelStatus mapping rule, or the inherited custom settings configured at a higherlevel, is used. Select [default] to inherit the custom settings or to reset to the default statusmapping rule.

VVM_RVG_CONTAINER

Icon

Parameters

None

InfoBox

Name Description







Version 2.5.00


Menu Commands


Configuration > Replicated Volume Groups

Accesses the dialog for specifying which replicated volume groups under the selectedreplicated volume container instance are to be monitored by the VVM KM. By default, allreplicated volume groups are monitored. Type [default] to reset any custom configurationsfrom current level and below and inherit custom setting, if any, or revert to defaultconfiguration.

Configuration > Replicated Volume GroupsStatus

Accesses the global configuration for determining the replicated volume group status formonitored replicated volume group instances.By default, the following VVMRvgState to VVMRvgStatus mapping rule is used:

Configuration > Replicated Volume GroupsKernel Status

Accesses the global configuration for determining the replicated volume group kernel status formonitored replicated volume group instances. By default, the following VVMRvgKernelStateto VVMRvgKernelStatus mapping rule is used:


Accesses the dialog for specifying which replication links under the selected replicated volumeinstance are to be monitored by the VVM KM. By default, all replication links are monitored.Type [default] to reset any custom configurations from current level and below and inheritcustom setting, if any, or revert to default configuration.

Configuration > Replication Links Status

Accesses the global configuration for determining the replication link status for monitoredreplication link instances.By default, the following VVMRlinkState to VVMRlinkStatus mapping rule is used:

Configuration >Replication Links KernelStatus

Accesses the global configuration for determining the replication link kernel status formonitored replication link instances.By default, the following VVMRlinkKernelState to VVMRlinkKernelStatus mapping rule isused:


Version 2.5.00


VVM_SERVER

Icon

Collectors

Name Description

VVMCreateDistribution Is automatically activated during KM debugging and deactivated when thedebug zip or tar file is created.Default polling interval: 1 minute.

VVMDaemonCollector Collects Veritas Volume Manager daemon related information. It sets allconsumer parameters in VVM_DAEMON_CONTAINER and VVM_DAEMONapplication classes.Default polling interval: 5 minutes.

VVMDiskdeviceCollector Collects Veritas Volume Manager diskdevice related information. It sets allconsumer parameters in VVM_DISKDEVICE_CONTAINER andVVM_DISKDEVICE application classes.Default polling interval: 10 minutes.

VVMDiskgroupCollector Collects Veritas Volume Manager diskgroup related information. It sets allconsumer parameters in VVM_DISKGROUP_CONTAINER, andVVM_DISKGROUP application classes.Default polling interval: 10 minutes.

VVMLogCollector Collects Veritas Volume Manager log file related information. It sets allconsumer parameters in VVM_LOG_CONTAINER and VVM_LOG applicationclasses.Default polling interval: 30 minutes.

VVMPlexCollector Collects Veritas Volume Manager plex related information. It sets all consumerparameters in the VVM_PLEX application class.Default polling interval: 10 minutes.

VVMRlinkCollector Collects Veritas Volume Manager replication link related information. It sets allconsumer parameters in VVM_RLINK application class.Default polling interval: 10 minutes.

VVMRvgCollector Collects Veritas Volume Manager replicated volume group related information. Itsets all consumer parameters in VVM_RVG_CONTAINER, and VVM_RVGapplication classes.Default polling interval: 10 minutes.

VVMSubdiskCollector Collects Veritas Volume Manager subdisk related information. It sets allconsumer parameters in the VVM_SUBDISK application class.Default polling interval: 10 minutes.

VVMUpdateAgent Is used by the VVM KM to set the PATROL Agent KM variables when thePATROL Console user is not authorized to update (ACL) any PATROL Agentvariables. It is activated automatically when the KM fails to update the PATROLAgent.Default polling interval: 5 minutes.


Version 2.5.00


Name Description

VVMVolumeCollector Collects Veritas Volume Manager volume related information. It sets allconsumer parameters in VVM_VOLUME_CONTAINER and VVM_VOLUMEapplication classes.Default polling interval: 10 minutes.

Parameters



ExtraFilesList Is used for pushing VVM KM library files tothe PATROL Agent during the Commitoperation.

n/a None n/a

VVMLoginStatus* Monitors the status of the VVM KM logindetails (username/password) for theoperating system. It is set byVVM_SERVER application class discovery.If no valid username/password is detectedfor the operating system, this parameterwill be set to "Failure" state. If there areany suspicious command exits, thisparameter will be set to "Suspicious" state.If this status parameter changes towarning or alarm state, the recovery actionwill trigger an event and annotate the lastdata point.


Warning= 1Alarm =2

CollectionStatus

VVMMonitoringMode* Indicates the VVM monitoring mode. {0 = Permanent Single-node Mode ;1 = Temporary Single-node Mode ;2 = Active Multi-nodeMode ;3 = Passive Multi-nodeMode ;-1 = Unknown}

None CollectionStatus

VVMNodeStatus* Monitors error messages for the VeritasVolume Manager application on thismanaged system. It is set by VVM_SERVERapplication class discovery.If any of the Veritas Volume Managerapplication daemons is not running, thisparameter will be set to "Failure" state.The list of critical Veritas Volume Managerdaemons can be customized using the KMcommand Configuration > Node Statusfrom the Veritas Volume Manager icon. Ifthere are any suspicious command exitsdue to an error, this parameter will be setto "Suspicious" state.If this status parameter changes towarning or alarm state, the recovery actionwill trigger an event and annotate the lastdata point.


Warning= 1Alarm =2

Availability


Version 2.5.00



InfoBox

Name Description

ApplicationName

Name of the application monitored by this Knowledge Module.

ApplicationVersion

Monitored application version number.

Binary Path Veritas Volume Manager software binary paths used by VVM KM.

Copyright Copyright (C) Sentry Software .

Host Name Name of the host as configured on the PATROL Agent.

InstallationPath

Veritas Volume Manager software installation path.

Library Path Veritas Volume Manager software library paths used by VVM KM.

MonitoringMode

Monitoring mode of the Knowledge Module.

MonitoringNode

Node currently monitoring Veritas Volume Manager.

Node Name(s) Name of the current managed system (node) as defined in Veritas Volume Manager.

OperatingSystem

Operating system description as reported by PATROL Agent.

PATROL AgentVersion

Version number of the PATROL Agent installed on the managed system.

Platform Operating system platform as reported by the PATROL Agent (HP, SOLARIS, RS6000, or NT).

Product Name Name of the Knowledge Module.

ProductRelease Date

Release date of the Knowledge Module.

Product Version Version number of the Knowledge Module.

Support [email protected]

Web site www.bmc.com

Menu Commands


RefreshProcess Cache

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

ForceDiscovery

Forces application discovery.

RefreshParameters

Forces an update of the application parameter values.


Version 2.5.00



ReloadCommands

Forces a reload of commands used by VVM KM during the next full discovery cycle. By default, all newcommands are reloaded automatically.

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

About Displays information about the product and manufacturer.

Configuration> Login

Accesses the Login Configuration dialog for viewing and entering VVM KM login details for the operatingsystem.This user account should have privileges to execute Veritas Volume Manager administration commandsand can use sudo privileges on Unix PATROL Agents.This user account will be used by VVM KM pre-discoveries, discoveries, data collectors, recovery actions,and infoboxes to execute operating system commands. It will not be used by any KM commands.The password is encrypted and stored on the PATROL Agent using the BMC PATROL encryption function.

Configuration> Preloading

Accesses Preloading Configuration dialog, which adds or removes the KM from PATROL Agent variable /AgentSetup/preloadedKMs.By preloading the VVM KM, the PATROL Agent will monitor the Veritas Volume Manager applicationwithout any PATROL Console connection.

Configuration> MonitoringMode

Accesses the Monitoring Mode Configuration dialog, which is used for enabling or disabling KMfailover, when monitoring clustered Veritas Volume Manager environment.

Configuration> Paths

Accesses the Path Configuration dialog, which displays and sets all paths used by VVM KM. Paths areautomatically discovered by the KM server discovery. They are used as environment variables forexecuting various Veritas Volume Manager commands.

Configuration> Node Status

Accesses the Node Status Configuration dialog for viewing and modifying the daemon names monitoredfor node status.The VVM KM checks for the existence of these daemons to determine the status of the node (parameterVVMNodeStatus). By default, the following daemons are sought:The VVM KM checks for the existence of these daemons to determine the status of the node (parameterVVMNodeStatus).

By default, the following daemons are sought on Unix platforms:

By default, the following daemons are sought on Windows platforms:


Configuration> InstanceLimits

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

Configuration> Debug

Accesses the Debug Configuration dialog for enabling/disabling the VVM KM debug switches.By default, all KM debug messages are sent to a set of files and a task window.


Version 2.5.00


VVM_SUBDISK

Icon

Parameters



VVMSubdiskIOKBytes Indicates the total number ofKBytes transferred on thesubdisk.


VVMSubdiskIOKBytesRate*

Indicates the number of KBytestransferred per second for thesubdisk.


None Statistics

VVMSubdiskIOOperations Indicates the total number ofinput and output operations onthe subdisk.


VVMSubdiskIOOperationsFai

led

Indicates the total number offailed input and outputoperations on the subdisk onUnix platforms.


VVMSubdiskIOOperationsRa

te

Indicates the number of inputand output operations persecond for the subdisk.


VVMSubdiskKernelState Indicates the kernel state ofthe subdisk on Unix platforms.


None Availability

VVMSubdiskKernelStateNT Indicates the kernel state ofthe subdisk on Windowsplatforms.

{0 = Enabled ; 1 = Unreported/Undefined ;2 = Error ; 3 = Disabled ;-1 = Unknown}

None Availability

VVMSubdiskKernelStatus Monitors the kernel status ofthe subdisk. This status isdetermined by the subdiskstatus mapping rule defined inthe KM command Configuration> Subdisk(s) Kernel Status.If this status parameterchanges to warning or alarmstate, the recovery action willtrigger an event and annotatethe last data point.



Availability


Version 2.5.00




VVMSubdiskReadKBytes Indicates the number of KBytesread on the subdisk.


VVMSubdiskReadKBytesRate

*

Indicates the number of KBytesread per second for thesubdisk.


None Statistics

VVMSubdiskReadOperations*

Indicates the number of readoperations on the subdisk.


VVMSubdiskReadOperations

Failed

Monitors the number of failedread operations on the subdiskon Unix platforms.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

operations Warning when >10

Statistics

VVMSubdiskReadTime* Monitors the read time for thesubdisk.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

milliseconds Warning when > 20

ResponseTime

VVMSubdiskReadTimeAverage*

Monitors the average read timefor the subdisk.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.


VVMSubdiskSummary Summarizes the subdiskinformation as reported bycommands executed by thedata collector.

n/a None n/a

VVMSubdiskWriteKBytes Indicates the number of KByteswritten on the subdisk.


VVMSubdiskWriteKBytesRat

e*

Indicates the number of KByteswritten per second for thesubdisk.


None Statistics

VVMSubdiskWriteOperations Indicates the number of writeoperations on the subdisk.


VVMSubdiskWriteOperations

Failed

Monitors the number of failedwrite operations on the subdiskon Unix platforms.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

operations Warning when >10

Statistics

VVMSubdiskWriteTime* Monitors the write time for thesubdisk.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

milliseconds Warning when > 20

ResponseTime


Version 2.5.00




VVMSubdiskWriteTimeAverage*

Monitors the average writetime for the subdisk.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.





Version 2.5.00


InfoBox

Name Description

Subdisk Name of the Veritas Volume Manager subdisk.

Group Diskgroup name of the Veritas Volume Manager subdisk.

Volume Volume name of the Veritas Volume Manager subdisk.

Plex Plex name of the Veritas Volume Manager subdisk.

Disk Disk name of the Veritas Volume Manager subdisk.

Device Device name of the Veritas Volume Manager subdisk.

KState Kernel state of the Veritas Volume Manager subdisk.

Length Length of the Veritas Volume Manager subdisk.






Menu Commands


Configuration > Subdisk

Accesses the individual configuration for monitoring the selected subdisk instance.This dialog allows the selected subdisk instance to be enabled or disabled for monitoring by theVVM KM.

Configuration > Subdisk Kernel Status

Accesses the configuration dialog for determining the kernel status for the selected subdiskinstance.By default, the global VVMSubdiskKernelState[NT] to VVMSubdiskKernelStatus mappingrule, or the inherited custom settings configured at a higher level, is used. Select [default] toinherit the custom settings or to reset to the default status mapping rule.


Version 2.5.00


VVM_VOLUME

Icon

Parameters



VVMVolumeIOKBytes Indicates the total number ofKBytes transferred on thevolume.


VVMVolumeIOKBytesRate* Indicates the number ofKBytes transferred per second

for the volume.


None Statistics

VVMVolumeIOOperations Indicates the total number ofinput and output operationson the volume.


VVMVolumeIOOperationsFailed

Indicates the total number offailed input and outputoperations on the volume onUnix platforms.


VVMVolumeIOOperationsRate

Indicates the number of inputand output operations persecond for the volume.


VVMVolumeKernelState Indicates the kernel state ofthe volume on Unixplatforms.

{0 = Enabled ; 1 = Detached ; 2 = Disabled ; -1 = Unknown}

None Availability

VVMVolumeKernelStateNT Indicates the kernel state ofthe volume on Windowsplatforms.

{0 = Enabled ; 1 = Unreported/Undefined ; 2 = Error ; 3 = Disabled ;-1 = Unknown}

None Availability

VVMVolumeKernelStatus Monitors the kernel status ofthe volume. This status isdetermined by the volumestatus mapping rule definedin the KM commandConfiguration > Volume(s)Kernel Status.If this status parameterchanges to warning or alarmstate, the recovery action willtrigger an event and annotatethe last data point.



Availability


Version 2.5.00




VVMVolumeLoggingState Indicates the logging state ofthe volume on Unix

platforms.

{0 = Enabled ; 1 = Disabled ; -1 = Unknown}

None Availability

VVMVolumeLoggingStatus Monitors the logging status ofthe volume on Unixplatforms. This status isdetermined by the volumestatus mapping rule definedin the KM commandConfiguration > Volume(s)Logging Status.If this status parameterchanges to warning or alarmstate, the recovery action willtrigger an event and annotatethe last data point.

{0 = OK ;1 = Suspicious ; 2 = Failure}


Availability

VVMVolumeReadKBytes Indicates the number ofKBytes read on the volume.


VVMVolumeReadKBytesRate*

Indicates the number ofKBytes read per second forthe volume.


None Statistics

VVMVolumeReadOperations Indicates the number of readoperations on the volume.


VVMVolumeReadOperationsFaile

d

Monitors the number of failedread operations on thevolume on Unix platforms.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.


Statistics

VVMVolumeReadTime* Monitors the read time for thevolume.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.


ResponseTime

VVMVolumeReadTimeAverage* Monitors the average readtime for the volume.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.


VVMVolumeState Indicates the state of thevolume on Unix platforms.

{0 = Active ;1 = Clean ;2 = Empty ;3 = Invalid ;4 = Replay ;5 = Synchronizing ;6 = NeedSynchronization ;-1 = Unknown}

None Availability


Version 2.5.00




VVMVolumeStateNT Indicates the state of thevolume on Windowsplatforms.

{0 = Active/Healthy ;1 = Stopped ;2 = Formatting ;3 = Regenerating ;4 = Synchronizing ;5 = Degraded ;6 = Failing ;7 = Missing ;8 = Failed ;-1 = Unknown}

None Availability

VVMVolumeStatus Monitors the status of thevolume. This status isdetermined by the volumestatus mapping rule definedin the KM commandConfiguration > Volume(s)Status.If this status parameterchanges to warning or alarmstate, the recovery action willtrigger an event and annotatethe last data point.



Availability

VVMVolumeSummary Summarizes the volumeinformation as reported bycommands executed by thedata collector.

n/a None n/a

VVMVolumeWriteKBytes Indicates the number ofKBytes written on the volume.


VVMVolumeWriteKBytesRate*

Indicates the number ofKBytes written per second forthe volume.


None Statistics

VVMVolumeWriteOperations Indicates the number of writeoperations on the volume.


VVMVolumeWriteOperationsFail

ed

Monitors the number of failedwrite operations on thevolume on Unix platforms.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.


Statistics

VVMVolumeWriteTime* Monitors the write time forthe volume.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.


ResponseTime

VVMVolumeWriteTimeAverage* Monitors the average writetime for the volume.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.



Version 2.5.00




InfoBox

Name Description

Volume Name of the Veritas Volume Manager volume.

Status Status of the Veritas Volume Manager volume.

Group Diskgroup name of the Veritas Volume Manager volume.

KState Kernel state of the Veritas Volume Manager volume.

Length Length of the Veritas Volume Manager volume.

Logging Logging state of the Veritas Volume Manager volume.

Log Length Log length of the Veritas Volume Manager volume.

Drive Letter Drive letter of the Veritas Volume Manager volume.

Type Type of the Veritas Volume Manager volume.






Menu Commands


Configuration > Volume Accesses the individual configuration for monitoring the selected volume instance.This dialog allows the selected volume instance to be enabled or disabled for monitoring by theVVM KM.

Configuration > VolumeStatus

Accesses the individual configuration for determining the status for the selected volumeinstance.By default, the global VVMVolumeState[NT] to VVMVolumeStatus mapping rule, or theinherited custom settings configured at a higher level, is used. Select [default] to inherit thecustom settings or to reset to the default status mapping rule.

Configuration > VolumeKernel Status

Accesses the configuration dialog for determining the kernel status for the selected volumeinstance.By default, the global VVMVolumeKernelState[NT] to VVMVolumeKernelStatus mappingrule, or the inherited custom settings configured at a higher level, is used. Select [default] toinherit the custom settings or to reset to the default status mapping rule.

Configuration > VolumeLogging Status (Unixonly)

Accesses the configuration dialog for determining the logging status for the selected volumeinstance.


Version 2.5.00



By default, the global VVMVolumeLoggingState to VVMVolumeLoggingStatus mappingrule, or the inherited custom settings configured at a higher level, is used. Select [default] toinherit the custom settings or to reset to the default status mapping rule.

Configuration > Plexes Accesses the dialog for specifying which plexes under the selected volume instance are to bemonitored by the VVM KM.By default, all plexes are monitored.Type [default] to reset any custom configurations from current level and below and inheritcustom setting, if any, or revert to default configuration.

Configuration > PlexesStatus

Accesses the configuration dialog for determining the status for monitored plex instances underthe selected volume instance.By default, the global VVMPlexState[NT] to VVMPlexStatus mapping rule, or the inheritedcustom settings configured at a higher level, is used. Select [default] to inherit the customsettings or to reset to the default status mapping rule.

Configuration > PlexesKernel Status

Accesses the configuration dialog for determining the kernel status for monitored plex instancesunder the selected volume instance.By default, the global VVMPlexKernelState[NT] to VVMPlexKernelStatus mapping rule, orthe inherited custom settings configured at a higher level, is used. Select [default] to inherit thecustom settings or to reset to the default status mapping rule.

Configuration > Subdisks Accesses the dialog for specifying which subdisks under the selected volume instance are to bemonitored by the VVM KM.By default, all subdisks are monitored.Type [default] to reset any custom configurations from current level and below and inheritcustom setting, if any, or revert to default configuration.

Configuration > SubdisksKernel Status

Accesses the configuration dialog for determining the kernel status for monitored subdiskinstances under the selected volume instance.By default, the global VVMSubdiskKernelState[NT] to VVMSubdiskKernelStatus mappingrule, or the inherited custom settings configured at a higher level, is used. Select [default] toinherit the custom settings or to reset to the default status mapping rule.

VVM_VOLUME_CONTAINER

Icon

Parameters

None

InfoBox

Name Description





Version 2.5.00


Name Description



Menu Commands


Configuration > Volumes Accesses the dialog for specifying which volumes under the selected volume container instanceare to be monitored by the VVM KM.By default, all volumes are monitored.Type [default] to reset any custom configurations from current level and below and inheritcustom setting, if any, or revert to default configuration.

Configuration > VolumesStatus

Accesses the configuration dialog for determining the status for monitored volume instancesunder the selected volume container instance.By default, the global VVMVolumeState[NT] to VVMVolumeStatus mapping rule, or theinherited custom settings configured at a higher level, is used. Select [default] to inherit thecustom settings or to reset to the default status mapping rule.

Configuration > VolumesKernel Status

Accesses the configuration dialog for determining the kernel status for monitored volumeinstances under the selected volume container instance.By default, the global VVMVolumeKernelState[NT] to VVMVolumeKernelStatusmapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule.

Configuration > VolumesLogging Status (UNIXonly)

Accesses the configuration dialog for determining the logging status for monitored volumeinstances under the selected volume container instance.By default, the global VVMVolumeLoggingState to VVMVolumeLoggingStatus mappingrule, or the inherited custom settings configured at a higher level, is used. Select [default] toinherit the custom settings or to reset to the default status mapping rule.

Configuration > Plexes Accesses the dialog for specifying which plexes under the selected volume container instanceare to be monitored by the VVM KM.By default, all plexes are monitored.Type [default] to reset any custom configurations from current level and below and inheritcustom setting, if any, or revert to default configuration.

Configuration > PlexesStatus

Accesses the configuration dialog for determining the status for monitored plex instances underthe selected volume container instance.By default, the global VVMPlexState[NT] to VVMPlexStatus mapping rule, or the inheritedcustom settings configured at a higher level, is used. Select [default] to inherit the customsettings or to reset to the default status mapping rule.

Configuration > PlexesKernel Status

Accesses the configuration dialog for determining the kernel status for monitored plexinstances under the selected volume container instance.By default, the global VVMPlexKernelState[NT] to VVMPlexKernelStatus mapping rule,or the inherited custom settings configured at a higher level, is used. Select [default] toinherit the custom settings or to reset to the default status mapping rule.

Configuration > Subdisks Accesses the dialog for specifying which subdisks under the selected volume container instanceare to be monitored by the VVM KM.By default, all subdisks are monitored.Type [default] to reset any custom configurations from current level and below and inheritcustom setting, if any, or revert to default configuration.

Configuration > SubdisksKernel Status

Accesses the configuration dialog for determining the kernel status for monitored subdiskinstances under the selected volume container instance.By default, the global VVMSubdiskKernelState[NT] to VVMSubdiskKernelStatusmapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule.

Additional Information and Support

123Where to Find Additional Help

Version 2.5.00


Where to Find Additional Help

Additional help for BMC PATROL can be found in the following locations:

PATROL Console User Guide

PATROL Console Online Help

Other PATROL Manuals and Guides


Additional help for Veritas Volume Manager can be found in the following locations:

Veritas Volume Manager Administrator’s Guide

Veritas Volume Manager Administrator’s Reference Guide

Veritas Volume Manager Release Notes

http://support.veritas.com

Additional help for PATROL Knowledge Module for Veritas Volume Manager by Sentry Software canbe found in the following locations:

PATROL Knowledge Module for Veritas Volume Manager by Sentry Software User Guide

PATROL Knowledge Module for Veritas Volume Manager by Sentry Software Release Notes



http://support.veritas.com


Index 124

Version 2.5.00


Index

- A -Abnormalities 50

Access

Executable Files 13

Files 13

Library Files 13

Paths 13

Permissions 13Acknowledge

Logs Alert 62Adapter 47

Add 48, 49

Create 48

Update 49Agent

PATROL 41AIX 13

Application Class

VVM_DAEMON 71

VVM_DAEMON_CONTAINER 73

VVM_DISKDEVICE 75

VVM_DISKDEVICE_CONTAINER 79

VVM_DISKGROUP 80

VVM_DISKGROUP_CONTAINER 84

VVM_DISKPATH 92

VVM_LOG 93

VVM_LOG_CONTAINER 96

VVM_PLEX 98

VVM_RLINK 102

VVM_RVG 104

VVM_SERVER 108

VVM_SUBDISK 112

VVM_VOLUME 116

VVM_VOLUME_CONTAINER 120

- B -Baselines

BMC ProactiveNet Performance Management 50

Generation 50

Manage 50

Requirements 50BMC

BMC Portal 47

BMC ProactiveNet Performance ManagementPortal 11

BMC Software PATROL Agent 11

BMC Software PATROL Console 11

Requirements 11BMC PATROL

Changes 11

pslInstructionMax 11BMC ProactiveNet

Integration 47BMC ProactiveNet Performance Management

Abnormalities 50

Baselines 50

Key Performance Indicators 50

KPI 50

- C -Changes 7

Check

Instance Limits 44Cluster

Configure 53Clustering Application 53

Collectors

VVMCreateDistribution 108

VVMDaemonCollector 108

VVMDiskdeviceCollector 108

VVMDiskgroupCollector 108

VVMLogCollector 108

VVMPlexCollector 108

VVMRlinkCollector 108

VVMRvgCollector 108

VVMSubdiskCollector 108

VVMUpdateAgent 108

VVMVolumeCollector 108Command

Configuration 79

Disk Paths 79

Disk Paths Kernel Status 79

Diskdevices 79

Diskdevices Status 79Commands

About 108

Acknowledgement 93

Index 125

Version 2.5.00


Commands

Alarms 93

All 93

Configuration 71, 73, 75, 80, 84, 92, 93,96, 98, 102, 104, 108, 112, 116, 120

Daemon 71

Daemon List 73

Daemon Status 71

Daemons 73

Daemons Status 73

Debug 108

Disk Devices 80, 84

Disk Devices Status 80, 84

Disk Path 92

Disk Path Kernel Status 92

Disk Paths 75, 80, 84

Disk Paths Kernel Status 75, 80, 84

Diskdevice 75

Diskdevice Status 75

Diskgroup 80

Diskgroup Status 80

Diskgroup Topology Report 80

Diskgroups 84

Diskgroups Status 84

Force Discovery 108

Instance Limits 108

KM Status 108

Log 93

Log Alert Acknowledgement 93

Log Filter 93

Log Scan Limit 93

Login 108

Logs 96

Logs Alert Acknowledgement 96

Logs Filter 96

Logs Scan Limit 96

Messages List 96

Monitoring Mode 108

Node Status 108

Paths 108

Plex 98

Plex Kernel Status 98

Plex Status 98

Plexes 80, 84, 116, 120

Plexes Kernel Status 80, 84, 116, 120

Plexes Status 80, 84, 116, 120

Preloading 108

Refresh Parameters 108

Refresh Process Cache 108

Reload Commands 108

Replicated Volume Group 104

Replicated Volume Group Kernel Status 104

Replicated Volume Group Status 104

Replicated Volume Groups 80

Replicated Volume Groups Kernel Status 80

Replicated Volume Groups Status 80

Replication Link Kernel Status 102

Replication Link Status 102

Replication Links 80, 102, 104

Replication Links Kernel Status 80, 104

Replication Links Status 80, 104

Reports 73, 80, 84, 96

Subdisk 112

Subdisk Kernel Status 112

Subdisks 80, 84, 98, 116, 120

Subdisks Kernel Status 80, 84, 98, 116,120

Veritas Volume Manager Topology Report 84

Volume 116

Volume Kernel Status 116

Volume Logging Status 116

Volume Status 116

Volumes 80, 84, 120

Volumes Kernel Status 80, 84, 120

Volumes Logging Status 80, 84, 120

Volumes Status 80, 84, 120

Warnings 93Configure

Cluster 53

Daemons 57

Disk Devices 57

Disk Groups 57

Disk Paths Kernel 57

KM User Account 41

Log Error Filter 60

Log Scan Limit 62

Logs Alert Acknowledgement 62

Multi-Node Monitoring Mode 53

Node Status 59

PATROL Agent 39

Plex 57

Plex Kernel 57

Status 57

Volume 57

Volume Kernel 57

Index 126

Version 2.5.00


Configure

Volume Logging 57

- D -Daemons

Delete 54

Disable 54

Enable 54Data Collectors

Force 67Debug

Disable 64

Enable 64Delete

Daemons 54

Disk Devices 54

Disk Paths 54

Diskgroups 54

Logs 54

Plexes 54

Subdisks 54

Volumes 54Disable

Daemons 54

Debug 64

Disk Devices 54

Disk Paths 54

Diskgroups 54

Logs 54

Plexes 54

Subdisks 54

Volumes 54Discoveries

Force 67Discovery

Verify 43Disk Devices

Delete 54

Disable 54

Enable 54Disk Paths

Delete 54

Disable 54

Enable 54Disk Space

Requirements 16Diskgroups

Delete 54

Disable 54

Enable 54

- E -Enable

Daemons 54

Debug 64

Disk Devices 54

Disk Paths 54

Diskgroups 54

Logs 54

Plexes 54

Subdisks 54

Volumes 54

- F -Failover Group Name 53

Files 17

ins_ALL_<version>.tar 17

ins_WINDOWS_<version>.exe 17

Setup 18

setup.exe 20

setup.sh 20

uninstall.exe 32

uninstall.sh 32Force

All Data Collectors 67

All Discoveries 67

Selected Data Collectors 67

- G -Generate

Baselines 50

Reports 66

- H -help 123

HP-UX 13

- I -Improvement 7

Index 127

Version 2.5.00


InfoBox

Application Name 108

Application Version 108

Available FS Space 93

Available Space 75

Binary Path 108

Collector Last End 71, 73, 75, 79, 80, 84,92, 93, 96, 98, 102, 104, 112, 116, 120

Collector Last Start 71, 73, 75, 79, 80, 84,92, 93, 96, 98, 102, 104, 112, 116, 120

Collector Name 71, 73, 75, 79, 80, 84, 92,93, 96, 98, 102, 104, 112, 116, 120

Collector Next Start 71, 73, 75, 79, 80,84, 92, 93, 96, 98, 102, 104, 112, 116, 120

Collector Status 71, 73, 75, 79, 80, 84,92, 93, 96, 98, 102, 104, 112, 116, 120

Command 71

Copyright 108

Data Volumes 104

Description 71, 93

Device 75, 112

Disk 75, 92, 112

Disk Access Name 92

Diskdevice 75

Drive Letter 116

FS Percent Used 93

Group 75, 92, 98, 102, 104, 112, 116

Host Name 108

ID 80

Installation Path 108

Kernel State 92, 102, 104

KState 98, 112, 116

Last Purge 93

Latency Protection 102

Length 98, 112, 116

Library Path 108

Local Host 102

Log File Modification Time 93

Log File Size 93

Log Length 116

Logging 116

Monitoring Mode 108

Monitoring Node 108

Name 71, 80, 93

Node Name(s) 108

Offset 75

Operating System 108

Owner 71

Path 92, 93

PATROL Agent Version 108

PID 71

Platform 108

Plex 98, 112

PPID 71

Product Name 108

Product Release Date 108

Product Version 108

Remote Host 102

Rlink 102

RVG 102, 104

SRL 104

SRL Overflow Protection 102

Status 71, 75, 80, 98, 102, 104, 116

Subdisk 112

Support 108

Synchronous 102

Tag 75

Total FS Space 93

Type 75, 80, 98, 102, 104, 116

Volume 98, 112, 116

Web site 108Install / Un-install 20, 32

BMC Software Installation Utility 17

Log 20

Packages 17

Procedure 20

Setup Files 18Instance Limits

Check 44Integration

BMC ProactiveNet 47Integration Service Agent 48

Introduction 20

Issues

Fixed 7

- K -Key Performance Indicators


Manage 50KM

Configure 41

Initial Setup 45

Load 37, 38, 47

Preload 39

Index 128

Version 2.5.00


KM

Preloaded 40, 41

Prepare to Load 38

Unload 39, 40, 41

User Account 41KPI


Manage 50

- L -Linux 13

Load

KM 37, 38, 47

PATROL Central 38

Prepare 38Log Error Filter

Configure 60Log Scan Limit

Configure 62Logs

Delete 54

Disable 54

Enable 54Logs Alert

Acknowledge 62

- M -Manage

Baselines 50

Key Performance Indicators 50

KPI 50Monitor Type 48

Multi-Node Monitoring Mode

Configure 53

- N -New features 7

Node Status

Configure 59

- O -Operating Systems

Linux 17, 20, 32

Unix 17, 32

Windows 17, 20, 32Options

Common services 20

Console Systems role 20

Managed System 20

View Log 20Oracle Solaris Cluster 53

Overview 9

- P -Parameter

NBULoginStatus 41Parameters

ExtraFilesList 108

Refresh 67

VVMDaemonCPUDuration 71

VVMDaemonCPUUtilization 71

VVMDaemonDetails 73

VVMDaemonMemorySize 71

VVMDaemonProcessCount 71

VVMDaemonState 71

VVMDaemonStatus 71

VVMDaemonSummary 71

VVMDiskdeviceDetails 84

VVMDiskdeviceIOKBytes 75

VVMDiskdeviceIOKBytesRate 75

VVMDiskdeviceIOOperations 75

VVMDiskdeviceIOOperationsFailed 75

VVMDiskdeviceIOOperationsRate 75

VVMDiskdeviceQueueDepth 75

VVMDiskdeviceReadKBytes 75

VVMDiskdeviceReadKBytesRate 75

VVMDiskdeviceReadOperations 75

VVMDiskdeviceReadOperationsFailed 75

VVMDiskdeviceReadTime 75

VVMDiskdeviceReadTimeAverage 75

VVMDiskdeviceSpaceAvailable 75

VVMDiskdeviceState 75

VVMDiskdeviceStateNT 75

VVMDiskdeviceStatus 75

VVMDiskdeviceSummary 75

VVMDiskdeviceWriteKBytes 75

VVMDiskdeviceWriteKBytesRate 75

VVMDiskdeviceWriteOperations 75

VVMDiskdeviceWriteOperationsFailed 75

Index 129

Version 2.5.00


Parameters

VVMDiskdeviceWriteTime 75

VVMDiskdeviceWriteTimeAverage 75

VVMDiskgroupDetails 84

VVMDiskgroupSpaceAvailable 80

VVMDiskgroupState 80

VVMDiskgroupStateNT 80

VVMDiskgroupStatus 80

VVMDiskgroupSummary 80

VVMDiskpathEnabled 75

VVMDiskpathKernelState 92

VVMDiskpathKernelStateNT 92

VVMDiskpathKernelStatus 92

VVMDiskpathNonEnabled 75

VVMDiskpathSummary 92

VVMLogAlarmCount 93

VVMLogAlarmText 93

VVMLogDetails 96

VVMLogFSSpaceUsedPercent 93

VVMLoginStatus 108

VVMLogSpaceAvailable 93

VVMLogSpaceGrowthRate 93

VVMLogSpaceUsed 93

VVMLogSpaceUsedPercent 93

VVMLogSummary 93

VVMLogText 93

VVMLogWarningCount 93

VVMLogWarningText 93

VVMMonitoringMode 108

VVMNodeStatus 108

VVMPlexDetails 84

VVMPlexIOKBytes 98

VVMPlexIOKBytesRate 98

VVMPlexIOOperations 98

VVMPlexIOOperationsFailed 98

VVMPlexIOOperationsRate 98

VVMPlexKernelState 98

VVMPlexKernelStateNT 98

VVMPlexKernelStatus 98

VVMPlexReadKBytes 98

VVMPlexReadKBytesRate 98

VVMPlexReadOperations 98

VVMPlexReadOperationsFailed 98

VVMPlexReadTime 98

VVMPlexReadTimeAverage 98

VVMPlexState 98

VVMPlexStateNT 98

VVMPlexStatus 98

VVMPlexSummary 98

VVMPlexWriteKBytes 98

VVMPlexWriteKBytesRate 98

VVMPlexWriteOperations 98

VVMPlexWriteOperationsFailed 98

VVMPlexWriteTime 98

VVMPlexWriteTimeAverage 98

VVMRlinkKernelState 102

VVMRlinkKernelStatus 102

VVMRlinkRemainingUpdatesCount 102

VVMRlinkRemainingUpdatesLag 102

VVMRlinkRemainingUpdatesPercent 102

VVMRlinkRemainingUpdatesSize 102

VVMRlinkState 102

VVMRlinkStatus 102

VVMRlinkSummary 102

VVMRvgKernelState 104

VVMRvgKernelStatus 104

VVMRvgRlinkCount 104

VVMRvgState 104

VVMRvgStatus 104

VVMRvgSummary 104

VVMRvgVolumeCount 104

VVMSubdiskDetails 84

VVMSubdiskIOKBytes 112

VVMSubdiskIOKBytesRate 112

VVMSubdiskIOOperations 112

VVMSubdiskIOOperationsFailed 112

VVMSubdiskIOOperationsRate 112

VVMSubdiskKernelState 112

VVMSubdiskKernelStateNT 112

VVMSubdiskKernelStatus 112

VVMSubdiskReadKBytes 112

VVMSubdiskReadKBytesRate 112

VVMSubdiskReadOperations 112

VVMSubdiskReadOperationsFailed 112

VVMSubdiskReadTime 112

VVMSubdiskReadTimeAverage 112

VVMSubdiskSummary 112

VVMSubdiskWriteKBytes 112

VVMSubdiskWriteKBytesRate 112

VVMSubdiskWriteOperations 112

VVMSubdiskWriteOperationsFailed 112

VVMSubdiskWriteTime 112

VVMSubdiskWriteTimeAverage 112

VVMVolumeDetails 84

VVMVolumeIOKBytes 116

VVMVolumeIOKBytesRate 116

VVMVolumeIOOperations 116

VVMVolumeIOOperationsFailed 116

Index 130

Version 2.5.00


Parameters

VVMVolumeIOOperationsRate 116

VVMVolumeKernelState 116

VVMVolumeKernelStateNT 116

VVMVolumeKernelStatus 116

VVMVolumeLoggingState 116

VVMVolumeLoggingStatus 116

VVMVolumeReadKBytes 116

VVMVolumeReadKBytesRate 116

VVMVolumeReadOperations 116

VVMVolumeReadOperationsFailed 116

VVMVolumeReadTime 116

VVMVolumeReadTimeAverage 116

VVMVolumeState 116

VVMVolumeStateNT 116

VVMVolumeStatus 116

VVMVolumeSummary 116

VVMVolumeWriteKBytes 116

VVMVolumeWriteKBytesRate 116

VVMVolumeWriteOperations 116

VVMVolumeWriteOperationsFailed 116

VVMVolumeWriteTime 116

VVMVolumeWriteTimeAverage 116PATROL

Agent 41

PATROL Agent 39, 40

PATROL Agent system 16

PATROL Central Console 39, 41

PATROL Central Console Server system 16

PATROL Central Web Server system 16

PATROL Console 39, 40

PATROL Console system 16PATROL Agent

Configure 39

Restart 45PATROL Console 38

Restart 45Permissions

Access 13Platform

Upgrade 45Platforms

Unix 41Plexes

Delete 54

Disable 54

Enable 54Preload

KM 39Preloaded

KM 40, 41ProactiveNet 48

PW Commands 49

- R -Refresh

Parameters 67Release Notes 7

remote PATROL Agent Checking 53

Reports

Generate 66Requirements

Additional 11

BMC ProactiveNet Performance ManagementPortal 11

BMC Software PATROL Agent 11

BMC Software PATROL Console 11

Disk Space 16

Security 13

Software 11

Symantec NetBackup™ 11

System 11Restart

PATROL Agent 45

PATROL Console 45

- S -Security

Requirements 13Setup

Check 45

Initial 45

KM 45Solaris 13

Status

Configure 57Subdisks

Delete 54

Disable 54

Enable 54Sudo 41

User 13System

HP-UX 11

Index 131

Version 2.5.00


System

IBM AIX 11

Microsoft Windows 11

Oracle Solaris 11

Red Hat Linux 11

Requirements 11

- T -Thresholds

Customize 49

Import 49

- U -Unix 41

Unload

KM 39, 40, 41Upgrade

Platform 45

- V -Verify

Application Discovery 43Veritas Cluster File System 53

Veritas Cluster Server 53

Volumes

Delete 54

Disable 54

Enable 54VVM_DAEMON

Application Class 71VVM_DAEMON_CONTAINER

Application Class 73VVM_DISKDEVICE

Application Class 75VVM_DISKDEVICE_CONTAINER

Application Class 79VVM_DISKGROUP

Application Class 80VVM_DISKGROUP_CONTAINER

Application Class 84VVM_DISKPATH

Application Class 92VVM_LOG

Application Class 93

VVM_LOG_CONTAINER

Application Class 96VVM_PLEX

Application Class 98VVM_RLINK

Application Class 102VVM_RVG

Application Class 104VVM_SERVER

Application Class 108VVM_SUBDISK

Application Class 112VVM_VOLUME

Application Class 116VVM_VOLUME_CONTAINER

Application Class 120

- W -What's new 7

About BMC® SoftwareBMC Software, Inc. NYSE:BMC, is a leading provider of enterprise management solutionsthat empower companies to manage their IT infrastructure from a business perspective.Delivering Business Service Management, BMC Software solutions span enterprisesystems, applications, databases, and service management. Founded in 1980, BMCSoftware has offices worldwide and fiscal 2004 revenues of more than $1.4 billion. For

more information about BMC Software, visit www.bmc.com.

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software, provides keymonitoring solutions specifically designed to expand the capabilities of BMCPerformance Manager, thus enabling up to 100% coverage of any infrastructure. SentrySoftware specializes in single solutions for multi-platform monitoring of hardware,custom applications or any IT component, and blackout windows. Sentry Softwareproducts are deployed in 45 countries across the globe and lead the list of BMCSoftware’s third-party product sales. For more information about Sentry Software,

please visit www.sentrysoftware.net.

Veritas Volume Manager for PATROL v2.5 - Sentry Software · PDF fileVeritas Volume Manager KM...

Documents

Transcript of Veritas Volume Manager for PATROL v2.5 - Sentry Software · PDF fileVeritas Volume Manager KM...