Veritas Volume Manager for PATROL - Sentry Software · PDF file9 Version 2.4.00 Veritas Volume...

User Documentation February 2013

Veritas Volume Manager KM forPATROL

Version 2.4.00

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

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 RESERVED UNDERTHE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data andcomputer software by the U.S. Government is subject to restrictions, as applicable, set forth in FARSection 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this address.

2

Version 2.4.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, call800 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 Support canbegin 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, and service

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

messages from the operating system, such as "file system full"

3

Version 2.4.00


http://www.bmc.com/support_home



Table of Contents 4

Version 2.4.00


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

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

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

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

...........................................................................................................................17Disk Space Requirements

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

...........................................................................................................................18Packages

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

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

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

...........................................................................................................................38Loading / Unloading the KM

...........................................................................................................................38Loading the KM

..................................................................................................................39Preparing to Load the KM

..................................................................................................................39Loading the KM on PATROL Console

..................................................................................................................39Loading the KM on PATROL Central

..................................................................................................................40Preloading the KM

...........................................................................................................................40Unloading the KM

..................................................................................................................41Unloading the KM from the PATROL Agent

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

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

...........................................................................................................................42Performing Post-Installation Operations

...........................................................................................................................42Configuring the KM User Account

...........................................................................................................................44Verifying Application Discovery

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

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

...........................................................................................................................46Restarting PATROL Agent and PATROL Console

...........................................................................................................................46Upgrading the Platform

...........................................................................................................................48Integrating with BMC Portal

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

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

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

...........................................................................................................................50Importing and Customizing Thresholds

Table of Contents 5

Version 2.4.00


...........................................................................................................................51Managing Baselines and Key Performance Indicators

...........................................................................................................................54Configuring the KM

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

...........................................................................................................................55Filtering Elements to Monitor

...........................................................................................................................58Configuring the Element Status

...........................................................................................................................60Configuring the Node Status

...........................................................................................................................61Configuring the Log Filter

...........................................................................................................................63Configuring the Log Scan Limit

...........................................................................................................................63Configuring Logs Alert Acknowledgement

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

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

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

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

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

...........................................................................................................................7 0Classes and Parameters

...........................................................................................................................7 1VVM_DAEMON

...........................................................................................................................7 3VVM_DAEMON_CONTAINER

...........................................................................................................................7 4VVM_DISKDEVICE

...........................................................................................................................7 8VVM_DISKDEVICE_CONTAINER

...........................................................................................................................7 9VVM_DISKGROUP

...........................................................................................................................82VVM_DISKGROUP_CONTAINER

...........................................................................................................................86VVM_DISKPATH

...........................................................................................................................87VVM_LOG

...........................................................................................................................90VVM_LOG_CONTAINER

...........................................................................................................................91VVM_PLEX

...........................................................................................................................95VVM_SERVER

...........................................................................................................................98VVM_SUBDISK

...........................................................................................................................101VVM_VOLUME

...........................................................................................................................104VVM_VOLUME_CONTAINER

...........................................................................................................................108Where to Find Additional Help

Release Notes for v2.4.00

7

Version 2.4.00


What's newFull compatibility with BMC ProactiveNet Central Monitoring Administration, a feature supported byBMC ProactiveNet Performance Management version 9.0.00.

Veritas Volume Manager KM for PATROL now supports Veritas Storage Foundation v6.x.

Veritas Volume Manager KM for PATROL now supports Microsoft Cluster.

In order to easily identify which step the initial discovery is processing, the setup icon now reflectsthe successive phases:

Upgrading (PATROL Classic Console only)

Loading (Commands)

Initializing (KM paths. Missing path is now specified in the System Output Window)

Discovering (Monitored application)

Cleaning (Temp files)

Validating (Application paths)

Changes and ImprovementsThe global performance of Veritas Volume Manager KM for PATROL has been improved.

All collectors are now automatically refreshed as soon as the KM configuration and the initialdiscovery are complete.

The default number of instances of Application Classes has been removed. This information mustbe defined by the user. When set to 0, the monitoring of a specific Application Class is notperformed.

The default log scan limit was increased to 500 KBytes.

The KM-related messages that are sent to the System Output Window (SOW) are also logged tothe VVM.log file available under <PATROL_HOME>/log.

When one or more required paths are missing, the setup instance label will now indicate whichpaths are missing. A message will also be displayed in the System Output Window.

The VVMRemoveTempFiles parameter was removed.

All previous pconfig variables available under /VVM are now split to /VVM and /Runtime/VVM whileupgrading the KM.

The polling interval can now be modified for the server discovery to detect server changes andcluster fail over faster.

The time during which the debug information is logged can now be set by the user.

The KM Status report now provides collector/discovery collection time information as well asadditional performance details.

Fixed IssuesWith some Windows platforms the Debug KM Command was prompting for an OS login to turn thedebug on.

The VVMDaemonState parameter was set to "Not Running" when the PATROL Agent could notfork processes, which resulted in invalid alarms on the VVMDaemonStatus parameter.

A problem occurring when the KM triggers certain events would lead to the PATROL Agent to crashwithout displaying any error message.

The KM was not properly managing the online thinrclm shared status for VVMDiskdeviceStatusparameter leading to triggering erroneous warning. The online thinrclm shared status is nowproperly recognized as an online state.

Overview

9

Version 2.4.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:

the health of the Veritas Volume Manager application

the following critical daemons:

Operating System Daemons

Unix vxconfigd: VxVM Configuration Daemon

vxrelocd: VxVM Relocation Daemon

vxnotify: VxVM Event Configuration Daemon

vxsvc: VEA Service Daemon

vxiod: VxVM Kernel Volume I/O Daemon

Windows vxsvc: Veritas Object Bus (vxob) Daemon

vxpal: Veritas Storage Agent (vxvm) Daemon

the availability and performance of volumes and their sub-components created under VeritasVolume Manager

log files

the availability and performance of volumes and their sub-components created under VeritasVolume Manager.

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.4.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 Volume ManagerKM 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 reloadcommands for 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 Veritas VolumeManager 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.4.00


Version 2.1 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 reloadcommands for 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 is installed.This adjustment will allow the data collectors to execute without incurring an internal scheduling delay.

This PATROL Agent tuning variable can be updated using wpconfig (on Microsoft Windows), xpconfig(on Unix) or PATROL Configuration Manager (PCM). Alternatively, you can use one of the 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 W indow (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 read andwrite to these pconfig variables at anytime. If Access Control List (ACL) is used to control which usersare authorized to connect to a PATROL Agent, please ensure that the mode for PATROL Agent userincludes “C” in the PATROL Agent variable “/AgentSetup/accessControlList”. Please refer the PATROLAgent Reference Manual for more details

13Requirements

Version 2.4.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. A lso 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 registrykeys from PATROL Agent. Access the above patch site from the managed node to obtain the correctpatch for that 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 Agentconfiguration variables (pconfig). This user could then execute PSL statements using the encryptedpassword through the PATROL Console. This can be prevented by setting up an appropriate AccessControl List (ACL) for users. Please refer to the PATROL Agent Reference Manual for details on howto set up an ACL.

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

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

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

14Requirements

Version 2.4.00


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, configured inVeritas 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.

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 Manager x.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 permissions tothe 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 the VVMKM 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, suchas ps, uname which may not require special priv ileges.

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-","=","=");

15Requirements

Version 2.4.00


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-"," "," "));

}

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:

Unix Microsoft Windows

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

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 thecopied log file will be removed. This may increase the file system usage under KM_TEMP temporarilyduring this 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. This usershould 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 and reportmenu commands using their sudo privileges. The KM accepts any non-root user with the following sudoconfiguration in the sudoers file. Please replace user1, user2, user3 with appropriate KM user name.The Veritas Volume Manager installation path INSTALL_PATH, referenced below is normally /opt/VRTS and PATROL_HOME is the path where the PATROL Agent is installed (including the target, like /

16Requirements

Version 2.4.00


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 notmade public 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 thesudo user password.

On Solaris:User_Alias VVMKMUSERS = user1, user2, user3

Defaults:VVMKMUSERS !lecture,!authenticate,\

env_keep+="LD_LIBRARY_PATH INSTALL_PATH KM_HOME \

KM_TEMP",env_reset

VVMKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\

INSTALL_PATH/bin/*,\

PATROL_HOME/lib/VVM/*,PATROL_HOME/bin/*

On HP-UX:User_Alias VVMKMUSERS = user1, user2, user3


env_keep+="SHLIB_PATH INSTALL_PATH KM_HOME \

KM_TEMP",env_reset




On AIX & Linux:User_Alias VVMKMUSERS = user1, user2, user3


env_keep+="LIBPATH INSTALL_PATH KM_HOME \

KM_TEMP",env_reset




17Requirements

Version 2.4.00


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 PATROL Agentwill generate approximately 250 KBytes of history data per day. An enterprise installation of VeritasVolume Manager on a active server with large number of VxVM objects will generate more history data(as per other KMs used by the PATROL Agent). These history data files are recycled by PATROLdepending on the PATROL Agent history retention period.

During execution, the VVM KM creates and maintains temporary files under KM_HOME, KM_TEMP andKM_DEBUG paths. By default they are all under PATROL_HOME/lib/VVM, where PATROL_HOMEpath is normally /opt/bmc/Patrol3/ (on Unix) or C:\Program Files (x86)\BMCSoftware\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 Utility

In 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 Software EPD(electronic product download) from: http://webapps.bmc.com/signon/content/logon.jsp on the BMCSoftware Website, or from the Veritas Volume Manager KM for PATROL page on the Sentry SoftwareWebsite

Choose the appropriate package depending on the platform you plan to install Veritas Volume ManagerKM 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 for PATROLpackages.

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

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

18Packages

Version 2.4.00


Packages

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

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

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

Extracting the Setup Files

Like most Knowledge Modules for PATROL, you need to install Veritas Volume Manager KM for PATROLon 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

http://www.sentrysoftware.com

Installing the KM

20

Version 2.4.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 Veritas VolumeManager KM for PATROL.

Installing Veritas Volume ManagerKM for PATROL

Installing Veritas Volume Manager KM for PATROL is an automated process managed by a wizard. Thewizard goes through the necessary steps to install Veritas Volume Manager KM for PATROL and all filesassociated with it. You are simply prompt for the product's folder location and the product/componentsto install.

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

21Installing Veritas Volume Manager KM forPATROL

Version 2.4.00


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.

Installation Wizard - Step 1: Windows Security A lert


Version 2.4.00


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

Installation Wizard - Step 2: Welcom e


Version 2.4.00


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

Installation Wizard - Step 3: Rev iewing License A greem ent


Version 2.4.00


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

Installation Wizard - Step 4: Selecting Installation Options


Version 2.4.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 Wizard - Step 5: Selecting the Installation Directory


Version 2.4.00


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

Installation Wizard - Step 6: Selecting an Installation Ty pe

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 Server oron PATROL Central – Web Edition.

Click Next to continue.


Version 2.4.00


Installation Wizard - Step 7: Selecting Roles

Select as many options as required.


Version 2.4.00


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

Installation Wizard - Step 8: Selecting Products and Com ponents


Version 2.4.00


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

Installation Wizard - Step 9: Rev iewing Installation Options


Version 2.4.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 Wizard - Step 10: Installation Status


Version 2.4.00


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

Installation Wizard - Step 11: Installation Results

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


Version 2.4.00


Installation Wizard - Step 12: Com pleting and closing the Installation Wizard

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.

Uninstalling Veritas VolumeManager KM for PATROL

Uninstalling 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

33Uninstalling Veritas Volume Manager KM forPATROL

Version 2.4.00


On UNIX, launch uninstall.sh

Un-install Wizard — Welcom e Step


Version 2.4.00


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

Un-install Wizard — Specify ing folder


Version 2.4.00


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

Un-install Wizard — Selecting Products and Com ponents Directory


Version 2.4.00


4. Click Start Uninstall.

Un-install Wizard — Rev iewing Selected Products & com ponents and start uninstalling


Version 2.4.00


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

Un-install Wizard — Status


Version 2.4.00


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

Un-install Wizard — 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 Agent systems.

39Loading / Unloading the KM

Version 2.4.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 W indow (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 Central

To load the KM on PATROL Central:

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

2. Click Next

3. Select the managed systems where the VVM KM is to be loaded, and click Next >. The wizard willdisplay 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 selected managedsystems will start discovering the Veritas Volume Manager environment. If the automatic discoverysuccessfully finds the Veritas Volume Manager installation, the VVM_SETUP instance will beinstantiated.

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 W indow (SOW) during the initial discovery .


Version 2.4.00


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

6. Configure the KM.

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

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 if youno longer want to use some parts of the KM, though there may be circumstances where you may wishto 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 on thatsystem when there is no connection to a PATROL Console with VVM KM loaded.

from PATROL Console: the PATROL Console stops displaying and monitoring the Veritas VolumeManager application on any PATROL Console connected system.


Version 2.4.00


Unloading the KM from the PATROL Agent

To 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 W indows) or xpconfig to unload the KM. You will then have toremove NBU_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 it torun 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.4.00


Unloading the KM from the PATROL Central Console

A 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. Thisallows for a partial unloading of the KM to enable it to run as a reduced installation on some or all of themanaged 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 to beunloaded.

Performing Post-InstallationOperations

It 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 and executeVeritas Volume Manager application programs and file systems. Depending on the operating systemsused, 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 to administerthe Veritas Volume Manager application.

43Performing Post-Installation Operations

Version 2.4.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” afterthe next data collection.


Version 2.4.00


Verifying Application DiscoveryTo verify the application discovery:

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

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

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

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


Version 2.4.00


VVM KM Default Instance Lim its

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.

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


Version 2.4.00


cause(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 later saveit 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 torefer to the User Guide, or contact Technical Support, attaching the KM Status report.

To save the KM Status report as a task window, click Sav e A s Task. This task window can then be printed or savedas a tex t file.

Restarting PATROL Agent and PATROL ConsoleRestarting the PATROL Agent and PATROL Console is optional but often a good practice to confirm thatthe 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 KM containerinstance (labeled Veritas Volume Manager).

Integrating the KM

48

Version 2.4.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.x

OverviewTo 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. The Adapterperiodically synchronizes the performance data collected by these application classes into BMCProactiveNet.

49Integrating with BMC ProactiveNet PerformanceManagement 8.5.x and 8.6.x

Version 2.4.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 perform theintegration 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. TheAdapter 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 intoBMC ProactiveNet to enable the update of a single KM independently.


Version 2.4.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 been createdbased 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 BMC


Version 2.4.00


ProactiveNet Operator Console, while instance-level thresholds are displayed in the Absolute InstanceThresholds panel to indicate thresholds have been successfully imported into BMC ProactiveNet.

Managing Baselines and Key PerformanceIndicatorsIn order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNetcalculates baselines per parameter (metrics or attributes) based on values collected over a specifiedperiod of time to determine a normal operating range. When the collected values for these parametersare 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 a specifiedtime period and establishing a low baseline value (consisting of the 10th percentile of all the values for agiven time period) and a high baseline value (consisting of the 90th percentile of all the values for agiven time period), taking a weighted average of these values over time. A higher weight is given to thelatest data being factored into the baseline average. The accuracy of the baseline improves 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 BMC ProactiveNetAdministration Console. In this KM, some parameters or attributes have been designated as importantindicators of performance (KPIs). We do not recommend that these default settings are modified.

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


Version 2.4.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. TheKPI 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 Performance Indicators:

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 that monitortype

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

54

Version 2.4.00


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

Configuring the KM

The configuration instructions provided in this section should be followed on all PATROL Agent Systemswhere 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, VeritasCluster File System, Oracle Solaris Cluster or Microsoft Cluster, the VVM KM must be installed on all thecluster nodes to enable continuous monitoring and avoid single point of failure. To avoid duplicate alertsfrom multiple nodes, it is recommended to configure the solution to operate in multi-node monitoringmode.

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

55Configuring the KM

Version 2.4.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 Veritas ClusterFile System. The VVM KM will then monitor the entire cluster from the active master system, whichis identified by the vxdctl -c mode command. This method requires vxconfigd in enable mode withits clustered state active.

5. Enable Remote PATROL Agent Checking to check the monitoring status of the other nodes andclick OK

6. Indicate all the information required to communicate with the remote PATROL Agent (authenticationserver, 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 A ctive 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 you wishto monitor:

Daemons > KM Commands > Configuration > Daemons to filter daemons to be monitored

Logs > KM Commands > Configuration > Logs to filter logs to be monitored. Only the VVMengine log file will be monitored on AIX and Microsoft Windows platforms since there is no ASCIIformat 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 to bemonitored

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 be monitored


Version 2.4.00


Filtering Elem ents 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.4.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 leav ing 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:

Type the name of the element to be monitored

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.4.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. It canbe 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

Deam on Status Configuration Dialog


Version 2.4.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 a warningwhen 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 clickUpdate .

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


Version 2.4.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.4.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 Daemon listmust 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 or analarm. Each time the KM will find these expressions in a log file or in VVMLogText, the error messagewill be written to the VVMLogAlarmText or VVMLogWarningText parameter. By default, the defaultlog filter is configured for the system log file. If you enabled additional log files for monitoring, you willhave to customize the log filter by adding appropriate expressions for those log files.

To configure the log error filter:


Version 2.4.00


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

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.

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). You canalso limit the exclusion to a particular expression already listed by using standard wildcard syntax,such as “skipping . otlsol06”.

Select Exclude

6. Click Update.


Version 2.4.00


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),the KM, 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) ScanLimit

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

Manual acknowledgement may impact the performance of the application and of the PATROL Agentif the 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 automatically acknowledged

3. Click Ok.

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

64Using the KM

Version 2.4.00


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

Enabling the Debug ModeWhen you encounter an issue and wish to report it to Sentry Software, you will be asked to enable theDebug 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.4.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

Diskgroup VVM_DISKGROUP_CONTAINERVVM_DISKGROUP

VVMDiskgroupCollector

Diskdevice /Path VVM_DISKDEVICE_CONTAINERVVM_DISKDEVICEVVM_DISPATH

VVMDiskdeviceCollector

Volume VVM_VOLUME_CONTAINERVVM_VOLUME

VVMVolumeCollector

Plex VVM_PLEX VVMPlexCollector

Subdisk VVM_SUBDISK VVMSubdiskCollector

3. Set the Debug Options:

In the Debug End Time field, indicate the date and time after which debug information will nolonger 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 disk spaceand read, write and execute permissions for both PATROL Agent user and the VVM KM login 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 at least10MB of available disk space and read, write and execute permissions for both PATROL Agentuser 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 tomanually stop debugging:

66Using the KM

Version 2.4.00


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 Unix systems

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

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

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 logged inthe 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 Sav e A s Task. This task window can then be printed or saved as a tex tfile.

67Using the KM

Version 2.4.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 loaded onthe 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 to refreshthe 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 without Icons...

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

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

68Using the KM

Version 2.4.00


Click Update.

Reference Guide

70

Version 2.4.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 parameters usedin the KM, grouped by Application Classes, and provides a brief description of each parameter and itsdefault settings.

Classes and Parameters

This section lists the application classes of Veritas Volume Manager KM for PATROL. It gives you detailson the icons that represent the class, Infobox, parameters and the menu commands available for eachapplication class. There are 9 main application classes and 5 “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_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 process arerespectively identified by the following icons:

Baselining

KPI

71Classes and Parameters

Version 2.4.00


VVM_DAEMON

Icon

Parameters

Name Description Units DefaultAlertConditions

BMCProactiveNetAttribute Type

VVMDaemonCPUDuration

Indicates the CPU seconds consumed by the daemon. seconds None Statistics

VVMDaemonCP

UUtilization*

Indicates the CPU seconds consumed by the daemon. % None Statistics

VVMDaemonMe

morySize*

Indicates the core image size of the daemon in the virtualmemory.

KB None Statistics

VVMDaemonPro

cessCount

Indicates the number of the processes/threads of thedaemon found.

processes None Statistics

VVMDaemonState

Indicates the state of the daemon as reported in thecommand executed by the data collector.

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

None Availability

VVMDaemonStatus

Monitors the status of the daemon. This status is determinedby the daemon status mapping rule defined in the KMcommand Configuration > Daemon(s) Status.If this status parameter changes to warning or alarm state,the recovery action will trigger an event and annotate thelast data point.

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

Warning =1Alarm = 2

Availability


Version 2.4.00


VVMDaemonSummary

Summarizes the daemon information as reported bycommands executed by the data collector.

n/a None n/a

For detailed information about B a se lining and KP I, see Managing Baselines and Key Performance Indicators.

* Parameters marked with an asterisk are used by default when v isualizing 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 allows the selected daemon instance to be enabled or disabled for monitoring by the VVMKM.

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, asconfigured at the container level. Select [default] to revert to the daemon status mapping ruleconfigured at the global/container level.


Version 2.4.00


VVM_DAEMON_CONTAINER

Icon

Parameters



VVMDaemonDetails

Displays all data returned to the standard outfrom commands executed by the data collector.

n/a None n/a

InfoBox

Name Description


Collector LastStart


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

Collector NextStart



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.Daemon Description Statusvxconfigd VxVM Configuration Daemon Enabledvxrelocd VxVM Client Daemon Enabledvxnotify VxVM Event Configuration Daemon Enabledvxcached VxVM Cache Daemon Enabledvxiod VxVM Kernel Volume I/O Daemon Enabled(all other daemons) Disabled

By default following daemons are monitored on Windows platforms.Daemon Description Statusvxsvc Veritas Object Bus (vxob) Demon Enabled


Version 2.4.00


vxpal Veritas Storage Agent (vxvm) Daemon Enabled(all other daemons) Disabled

Type [default] to reset to the default configuration.

Configuration > Daemons Status

Accesses the global configuration for determining the daemon status for monitored daemoninstances.By default following VVMDaemonState to VVMDaemonStatus mapping rule is used: VVMDaemonState VVMDaemonStatus Not Running Failure Terminated, Stopped Suspicious Growing, or Unknown Suspicious all other states OK

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

VVM_DISKDEVICE

Icon

Parameters

Name Description Units Default AlertConditions

BMCProactiveNetAttributeType

VVMDiskdeviceIOKBytes

Indicates the totalnumber of KBytestransferred on thediskdevice.

KB None Statistics

VVMDiskdeviceIO

KBytesRate*

Indicates the number ofKBytes transferred persecond for thediskdevice.

KB/s None Statistics

VVMDiskdeviceIOOperations

Indicates the totalnumber of input andoutput operations onthe diskdevice.

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


Version 2.4.00


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.

KB None Statistics

VVMDiskdeviceReadKBytesRate*

Indicates the number ofKBytes read per secondfor the diskdevice.


VVMDiskdeviceReadOperations

Indicates the number ofread operations on thediskdevice.


VVMDiskdeviceReadOperationsFailed

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

operations Warning when > 10and < 100

Statistics

VVMDiskdeviceReadTime*

Monitors the read timefor the diskdevice. Ifthis parameter changesto warning or alarmstate, the recoveryaction will trigger anevent.

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

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

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

Warning = 1Alarm = 2

Availability


Version 2.4.00


If this status parameterchanges to warning oralarm state, therecovery action willtrigger an event andannotate the last datapoint.

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.

KB None Statistics

VVMDiskdeviceWri

teKBytesRate*

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


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

VVMDiskdeviceWri

teTime*

Monitors the write timefor the diskdevice. Ifthis parameter changesto warning or alarmstate, the recoveryaction will trigger anevent.


Response Time

VVMDiskdeviceWriteTimeAverage*

Monitors the averagewrite time for thediskdevice. If thisparameter changes towarning or alarm state,the recovery action willtrigger an event.


Statistics


Version 2.4.00


Note: This parameter isnot available for non-dynamic diskgroups on Windowsplatforms.

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

VVMDiskdeviceState

Indicates the state ofthe diskdevice on Unixplatforms.

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

None 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 Last Start Date & time when the last data collection cycle started.


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


Menu Commands



Version 2.4.00


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 diskdeviceinstance.By default, the global VVMDiskdeviceState[NT] to VVMDiskdeviceStatus 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 > 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 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.

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


Collector LastEnd

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

Collector NextStart


CollectorStatus

Data collector execution status (Idle or Running).


Version 2.4.00


Menu Commands


Configuration> Diskdevices

Accesses the dialog for specifying which diskdevices under the selected diskdevice container instanceare to 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 underthe selected 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 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_DISKGROUP

Icon

Parameters


BMCProactiveNetAttributeType

VVMDiskgroupSpaceAvailable*

Indicates the available space for the diskgroup. GB None Availability

VVMDiskgroupState

Indicates the state of the diskgroup on Unixplatforms.

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

None Availability


Version 2.4.00


VVMDiskgroupStateNT

Indicates the state of the diskgroup on Windowsplatforms.

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

None Availability

VVMDiskgroupStatus

Monitors the status of the diskgroup. This status isdetermined by the diskgroup status mapping ruledefined in the KM command Configuration >Diskgroup(s) Status.

If this status parameter changes to warning oralarm state, the recovery action will trigger anevent and annotate the last data point.

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

Warning =1Alarm = 2

Availability

VVMDiskgroupSummary

Summarizes the diskgroup information as reportedby commands executed by the data collector.

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 LastStart



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

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.


Version 2.4.00


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.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 instancesunder the 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 settingsor to 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] toinherit the 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 underthe selected diskgroup 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 the customsettings or to 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,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 > 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 inheritedcustom settings configured at a higher level, is used. Select [default] to inherit the custom settingsor to reset to the default status mapping rule.

Configuration > Plexes KernelStatus

Accesses the configuration dialog for determining the kernel status for monitored plex instancesunder the 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.


Version 2.4.00


Configuration > Subdisks

Accesses the dialog for specifying which subdisks under the selected diskgroup 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 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 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_DISKGROUP_CONTAINER

Icon

Parameters



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

n/a None n/a

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

n/a None n/a

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

n/a None n/a

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

n/a None n/a

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

n/a None n/a

InfoBox

Name Description






Version 2.4.00



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 isused on Unix platforms:VVMDiskgroupState VVMDiskgroupStatus Unknown, or Disabled Failure all other states OK

By default, the following VVMDiskgroupStateNT to VVMDiskgroupStatus mapping rule isused on Windows platforms:VVMDiskgroupStateNT VVMDiskgroupStatus Unknown, or Deported Failure all other states OKSelect [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 isused on Unix platforms:VVMDiskdeviceState VVMDiskdeviceStatus Failing, Failed or Offline Failure Unknown or Online with Errors Suspicious all other states OK

By default, the following VVMDiskdeviceStateNT to VVMDiskdeviceStatus mapping rule isused on Windows platforms:VVMDiskdeviceStateNT VVMDiskdeviceStatus Failing, Failed, Offline, Foreign, Detached, or Disconnected Failure Unknown or Online with Errors Suspicious all other states OK

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.


Version 2.4.00



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:VVMVolumeState VVMVolumeStatus Need Synchronization Failure Unknown, Replay or Synchronizing Suspicious all other states OK

By default, the following VVMVolumeStateNT to VVMVolumeStatus mapping rule is usedon Windows platforms:VVMVolumeStateNT VVMVolumeStatus Degraded, Failing, Missing, or Failed Failure Unknown, Formatting, Regenerating, or Synchronizing Suspicious all other states OK

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 mappingrule is used on Unix platforms:VVMVolumeKernelState VVMVolumeKernelStatus Disabled Failure Unknown or Detached Suspicious all other states OK

By default, the following VVMVolumeKernelStateNT to VVMVolumeKernelStatusmapping rule is used on Windows platforms:VVMVolumeKernelStateNT VVMVolumeKernelStatus Disabled, or Error Failure Unknown Suspicious all other states OK

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 VVMVolumeLoggingStatusmapping rule is used:VVMVolumeLoggingState VVMVolumeLoggingStatus Unknown or Disabled Suspicious all other states OK

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.


Version 2.4.00


By default, the following VVMPlexState to VVMPlexStatus mapping rule is used on Unixplatforms:VVMPlexState VVMPlexStatus I/O Failure Failure Unknown, No disk/device, Recover, Removed, Stale, or Offline Suspicious all other states OK

By default, the following VVMPlexStateNT to VVMPlexStatus mapping rule is used onWindows platforms:VVMPlexStateNT VVMPlexStatus Unknown, or Failed Failure Recoverable Suspicious all other states OK

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 monitoredplex instances.By default, the following VVMPlexKernelState to VVMPlexKernelStatus mapping rule isused on Unix platforms:VVMPlexKernelState VVMPlexKernelStatus Disabled Failure Unknown or Detached Suspicious all other states OK

By default, the following VVMPlexKernelStateNT to VVMPlexKernelStatus mapping rule isused on Windows platforms:VVMPlexKernelStateNT VVMPlexKernelStatus Disabled Failure Unknown or Error Suspicious all other states OK

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 mappingrule is used on Unix platforms:VVMSubdiskKernelState VVMSubdiskKernelStatus Disabled Failure Unknown or Detached Suspicious all other states OK

By default, the following VVMSubdiskKernelStateNT to VVMSubdiskKernelStatusmapping rule is used on Windows platforms:VVMSubdiskKernelStateNT VVMSubdiskKernelStatus Disabled Failure Unknown or Error Suspicious all other states OK

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


Version 2.4.00


VVM_DISKPATH

Icon

Parameters



VVMDiskpathKernelState

Indicates the kernel state of the diskpath on Unixplatforms

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

None Availability

VVMDiskpathKernelStateNT

Indicates the kernel state of the subdisk onWindows platforms.

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

None Availability

VVMDiskpathKernelStatus

Monitors the kernel status of the disk paths. Thisstatus is determined by the subpath statusmapping rule defined in the KM commandConfiguration > Disk Path(s) Kernel Status. If thisstatus parameter changes to warning or alarmstate, the recovery action will trigger an event andannotate the last data point.

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


Availability

VVMDiskpathSummary

Summarizes the diskpath information as reportedby commands executed by the 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.4.00




Menu Commands


Configuration > DiskPath



Configuration > DiskPath Kernel Status



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.

These alarm messages can be acknowledged

automatically (default) or manually, depending on theconfiguration in the KM command Configuration > Log(s) Alert Acknowledgement. Manual acknowledgement

is available under the KM sub-menuAcknowledgement.

n/a None n/a


Version 2.4.00


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.

% Warningwhen >95 and <98Alarmwhen >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.

MB Warningwhen >2 and <5Alarmwhen > -1 and <2

Availability

VVMLogSpaceGrowthRate

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


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

VVMLogSpaceUsedPercent*

Monitors the percentage of capacity used by the logfile.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).

% Warningwhen >95 and <98Alarmwhen >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. Manual acknowledgementis available under the KM sub-menu Acknowledgement.

n/a None n/a



InfoBox

Name Description

Name Name of the Veritas Volume Manager log file.


Version 2.4.00


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 thetext parameter 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 > Log Filter

Accesses the individual configuration of the log error filter for the selected log file instance.By default, the global log filter is used, as configured at the container level.

Type [default] to reset to the log filter configured at the global/container level.

Configuration > Log Scan Limit

Accesses the individual configuration of the data scanning limit for the selected log file instance.By default, the global log file scanning limit is used, as configured at the container level.

Configuration > Log AlertAcknowledgement

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.


Version 2.4.00


VVM_LOG_CONTAINER

Icon

Parameters



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

n/a None n/a

InfoBox

Name Description




Collector NextStart



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.

On Solaris:Log File Description Status


Version 2.4.00


/var/adm/messages System Log Enabled(all other logs) Disabled

On HP-UX:Log File Description Statusvar/adm/syslog/syslog.log System Log Enabled(all other logs) Disabled On AIX:Log File Description Status(all other logs) Disabled

On Windows:Log File Description Status(all other logs) Disabled


Configuration > Logs Filter

Accesses the global configuration of the filter for expressions used for detecting error messages inthe monitored 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.Error Expression Set to Parameter StatusVxVM.*PANIC VVMLogAlarmText Included vxvm.*PANIC VVMLogAlarmText IncludedVxVM.*CRITICAL VVMLogAlarmText Includedvxvm.*CRITICAL VVMLogAlarmText IncludedVxVM.*ERROR VVMLogAlarmText Included vxvm.*ERROR VVMLog AlarmText IncludedVxVM.*WARNING VVMLogWarningText Includedvxvm.*WARNING VVMLogWarningText IncludedVxVM.*NOTICE VVMLogWarningText Includedvxvm.*NOTICE VVMLogWarningText Included


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


Version 2.4.00


Parameters



VVMPlexIOKBytes Indicates the total number of KBytes transferredon the plex.

KB None Statistics

VVMPlexIOKBytesRate

*

Indicates the number of KBytes transferred persecond for the plex on Unix platforms.


VVMPlexIOOperations Indicates the total number of input and outputoperations on the plex on Unix platforms.


VVMPlexIOOperations

Failed

Indicates the total number of failed input andoutput operations on the plex on Unix platforms.


VVMPlexIOOperations

Rate

Indicates the number of input and outputoperations per second for the plex on Unixplatforms.

operations/second

None Statistics

VVMPlexKernelState Indicates the kernel state of the plex on Unixplatforms.

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

None Availability

VVMPlexKernelStateNT Indicates the kernel state of the plex on Windowsplatforms.

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

None Availability

VVMPlexKernelStatus Monitors the kernel status of the plex. This statusis determined by the plex status mapping ruledefined in the KM command Configuration > Plex(s)Kernel Status.If this status parameter changes to warning oralarm state, the recovery action will trigger anevent and annotate the last data point.

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


Availability

VVMPlexReadKBytes Indicates the number of KBytes read on the plex onUnix platforms.

KB None Statistics

VVMPlexReadKBytesR

ate*

Indicates the number of KBytes read per secondfor the plex on Unix platforms.


VVMPlexReadOperations

Indicates the number of read operations on theplex on Unix platforms.


VVMPlexReadOperatio

nsFailed

Monitors the number of failed read operations onthe plex on Unix platforms.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.

operations Warningwhen > 10

Statistics

VVMPlexReadTime* Monitors the read time for the plex on Unixplatforms.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.

milliseconds Warningwhen > 20

ResponseTime

VVMPlexReadTimeAverage*

Monitors the average read time for the plex onUnix platforms.



Version 2.4.00


If this parameter changes to warning or alarmstate, the recovery action will trigger an event.

VVMPlexState Displays the state of the plex on Unix platforms. {0 = Active ; 1 = Clean ;2 = Empty ;3 = Log Plex ;4 = TemporaryPlex ;5 = SnapshotPlex ;6 = No Disk/Device ;7 = Recover ;8 = Removed ;9= Stale ;10= Offline ;11 = I/OFailure ;-1 = Unknown}

None Availability

VVMPlexStateNT Displays the state of the plex on Windowsplatforms.

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

None Availability

VVMPlexStatus Monitors the status of the plex. This status isdetermined by the plex status mapping rule definedin the KM command Configuration > Plex(s) Status.If this status parameter changes to warning oralarm state, the recovery action will trigger anevent and annotate the last data point.



Availability

VVMPlexSummary Summarizes the plex information as reported bycommands executed by the data collector.

n/a None n/a

VVMPlexWriteKBytes Indicates the number of KBytes written on the plexon Unix platforms.

KB None Statistics

VVMPlexWriteKBytesR

ate*

Indicates the number of KBytes written per secondfor the plex on Unix platforms.


VVMPlexWriteOperations

Indicates the number of write operations on theplex on Unix platforms.


VVMPlexWriteOperatio

nsFailed

Monitors the number of failed write operations onthe plex on Unix platforms.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.


VVMPlexWriteTime* Monitors the write time for the plex on Unixplatforms. If this parameter changes to warning oralarm state, the recovery action will trigger anevent.

milliseconds None ResponseTime

VVMPlexWriteTimeAverage*

Monitors the average write time for the plex onUnix platforms. If this parameter changes towarning or alarm state, the recovery action willtrigger an event.





Version 2.4.00


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.

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 plexinstance.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 inheritcustom setting, if any, or revert to default configuration.


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.


Version 2.4.00


VVM_SERVER

Icon

Collectors

Name Description

VVMCreateDistribution

Is automatically activated during KM debugging and deactivated when the debug zip or tar file iscreated.Default polling interval: 1 minute.

VVMDaemonCollector

Collects Veritas Volume Manager daemon related information. It sets all consumer parameters inVVM_DAEMON_CONTAINER and VVM_DAEMON application classes.Default polling interval: 5 minutes.

VVMDiskdeviceCollector

Collects Veritas Volume Manager diskdevice related information. It sets all consumer parameters inVVM_DISKDEVICE_CONTAINER and VVM_DISKDEVICE application classes.Default polling interval: 10 minutes.

VVMDiskgroupCollector

Collects Veritas Volume Manager diskgroup related information. It sets all consumer parameters inVVM_DISKGROUP_CONTAINER, and VVM_DISKGROUP application classes.Default polling interval: 10 minutes.

VVMLogCollector

Collects Veritas Volume Manager log file related information. It sets all consumer parameters inVVM_LOG_CONTAINER and VVM_LOG application classes.Default polling interval: 30 minutes.

VVMPlexCollector

Collects Veritas Volume Manager plex related information. It sets all consumer parameters in theVVM_PLEX application class.Default polling interval: 10 minutes.

VVMSubdiskCollector

Collects Veritas Volume Manager subdisk related information. It sets all consumer parameters in theVVM_SUBDISK application class.Default polling interval: 10 minutes.

VVMUpdateAgent

Is used by the VVM KM to set the PATROL Agent KM variables when the PATROL Console user is notauthorized to update (ACL) any PATROL Agent variables. It is activated automatically when the KM failsto update the PATROL Agent.Default polling interval: 5 minutes.

VVMVolumeCollector

Collects Veritas Volume Manager volume related information. It sets all consumer parameters inVVM_VOLUME_CONTAINER and VVM_VOLUME application classes.Default polling interval: 10 minutes.

Parameters




Version 2.4.00


ExtraFilesList Is used for pushing VVM KM library files to the PATROLAgent during the Commit operation.

n/a None n/a

VVMLoginStatus*

Monitors the status of the VVM KM login details (username/password) for the operating system. It is set byVVM_SERVER application class discovery.If no valid username/password is detected for the operatingsystem, this parameter will be set to "Failure" state. If thereare any suspicious command exits, this parameter will be setto "Suspicious" state.If this status parameter changes to warning or alarm state,the recovery action will trigger an event and annotate thelast data point.



CollectionStatus

VVMMonitoringMode*

Indicates the VVM monitoring mode. {0 =PermanentSingle-nodeMode ;1 = TemporarySingle-nodeMode ;2 = ActiveMulti-nodeMode ;3 = PassiveMulti-nodeMode ;-1 = Unknown}

None CollectionStatus

VVMNodeStatus*

Monitors error messages for the Veritas Volume Managerapplication on this managed system. It is set byVVM_SERVER application class discovery.If any of the Veritas Volume Manager application daemons isnot running, this parameter will be set to "Failure" state. Thelist of critical Veritas Volume Manager daemons can becustomized using the KM command Configuration > NodeStatus from the Veritas Volume Manager icon. If there areany suspicious command exits due to an error, thisparameter will be set to "Suspicious" state.If this status parameter changes to warning or alarm state,the recovery action will trigger an event and annotate thelast data point.



Availability


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.


Version 2.4.00


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.

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, recoveryactions, and infoboxes to execute operating system commands. It will not be used by any KMcommands.The password is encrypted and stored on the PATROL Agent using the BMC PATROL encryptionfunction.

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.


Version 2.4.00


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(parameter VVMNodeStatus).

By default, the following daemons are sought on Unix platforms:Daemon Descriptionvxconfigd VxVM Configuration DaemonDaemonvxiod VxVM Kernel Volume I/O Daemonvxrelocd VxVM Relocation Daemon By default, the following daemons are sought on Windows platforms:Daemon Descriptionvxsvc Veritas Object Bus (vxob) Demonvxpal Veritas Storage Agent (vxvm) Daemon


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.

VVM_SUBDISK

Icon

Parameters



VVMSubdiskIOKBytes Indicates the total number of KBytestransferred on the subdisk.

KB None Statistics

VVMSubdiskIOKBytes

Rate*

Indicates the number of KBytes transferred persecond for the subdisk.


VVMSubdiskIOOperations

Indicates the total number of input and outputoperations on the subdisk.



Version 2.4.00


VVMSubdiskIOOperati

onsFailed

Indicates the total number of failed input andoutput operations on the subdisk on Unixplatforms.


VVMSubdiskIOOperati

onsRate

Indicates the number of input and outputoperations per second for the subdisk.

operations/second

None Statistics

VVMSubdiskKernelState

Indicates the kernel state of the subdisk on Unixplatforms.

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

None Availability

VVMSubdiskKernelStateNT

Indicates the kernel state of the subdisk onWindows platforms.

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

None Availability

VVMSubdiskKernelStatus

Monitors the kernel status of the subdisk. Thisstatus is determined by the subdisk statusmapping rule defined in the KM commandConfiguration > Subdisk(s) Kernel Status.If this status parameter changes to warning oralarm state, the recovery action will trigger anevent and annotate the last data point.

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


Availability

VVMSubdiskReadKBytes

Indicates the number of KBytes read on thesubdisk.

KB None Statistics

VVMSubdiskReadKByt

esRate*

Indicates the number of KBytes read per secondfor the subdisk.


VVMSubdiskReadOperations*

Indicates the number of read operations on thesubdisk.


VVMSubdiskReadOper

ationsFailed

Monitors the number of failed read operationson the subdisk on Unix platforms.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.


Statistics

VVMSubdiskReadTime

*

Monitors the read time for the subdisk.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.


ResponseTime

VVMSubdiskReadTimeAverage*

Monitors the average read time for the subdisk.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.


VVMSubdiskSummary Summarizes the subdisk information as reportedby commands executed by the data collector.

n/a None n/a

VVMSubdiskWriteKBytes

Indicates the number of KBytes written on thesubdisk.

KB None Statistics

VVMSubdiskWriteKByt

esRate*

Indicates the number of KBytes written persecond for the subdisk.


VVMSubdiskWriteOperations

Indicates the number of write operations on thesubdisk.


VVMSubdiskWriteOper

ationsFailed

Monitors the number of failed write operationson the subdisk on Unix platforms.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.


Statistics

VVMSubdiskWriteTime

*

Monitors the write time for the subdisk.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.


ResponseTime


Version 2.4.00


VVMSubdiskWriteTimeAverage*

Monitors the average write time for the subdisk.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.




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


Version 2.4.00


VVM_VOLUME

Icon

Parameters



VVMVolumeIOKBytes Indicates the total number of KBytes transferredon the volume.

KB None Statistics

VVMVolumeIOKBytesRat

e*

Indicates the number of KBytes transferred per

second for the volume.KB/s None Statistics

VVMVolumeIOOperations

Indicates the total number of input and outputoperations on the volume.


VVMVolumeIOOperation

sFailed

Indicates the total number of failed input andoutput operations on the volume on Unixplatforms.


VVMVolumeIOOperation

sRate

Indicates the number of input and outputoperations per second for the volume.

operations/second

None Statistics

VVMVolumeKernelState Indicates the kernel state of the volume on Unixplatforms.

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

None Availability

VVMVolumeKernelStateNT

Indicates the kernel state of the volume onWindows platforms.

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

None Availability

VVMVolumeKernelStatus Monitors the kernel status of the volume. Thisstatus is determined by the volume status mappingrule defined in the KM command Configuration >Volume(s) Kernel Status.If this status parameter changes to warning oralarm state, the recovery action will trigger anevent and annotate the last data point.


Warning =1Alarm = 2

Availability

VVMVolumeLoggingState

Indicates the logging state of the volume on Unix

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

None Availability

VVMVolumeLoggingStatus

Monitors the logging status of the volume on Unixplatforms. This status is determined by the volumestatus mapping rule defined in the KM commandConfiguration > Volume(s) Logging Status.

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

Warning =1Alarm = 2

Availability


Version 2.4.00


If this status parameter changes to warning oralarm state, the recovery action will trigger anevent and annotate the last data point.

VVMVolumeReadKBytes Indicates the number of KBytes read on thevolume.

KB None Statistics

VVMVolumeReadKBytes

Rate*

Indicates the number of KBytes read per secondfor the volume.


VVMVolumeReadOperations

Indicates the number of read operations on thevolume.


VVMVolumeReadOperati

onsFailed

Monitors the number of failed read operations onthe volume on Unix platforms.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.


Statistics

VVMVolumeReadTime*

Monitors the read time for the volume.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.


ResponseTime

VVMVolumeReadTimeAverage*

Monitors the average read time for the volume.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.


VVMVolumeState Indicates the state of the volume on Unixplatforms.

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

None Availability

VVMVolumeStateNT Indicates the state of the volume 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 the volume. This status isdetermined by the volume status mapping ruledefined in the KM command Configuration >Volume(s) Status.If this status parameter changes to warning oralarm state, the recovery action will trigger anevent and annotate the last data point.


Warning =1Alarm = 2

Availability

VVMVolumeSummary Summarizes the volume information as reported bycommands executed by the data collector.

n/a None n/a

VVMVolumeWriteKBytes Indicates the number of KBytes written on thevolume.

KB None Statistics


Version 2.4.00


VVMVolumeWriteKBytes

Rate*

Indicates the number of KBytes written per secondfor the volume.


VVMVolumeWriteOperations

Indicates the number of write operations on thevolume.


VVMVolumeWriteOperati

onsFailed

Monitors the number of failed write operations onthe volume on Unix platforms.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.


Statistics

VVMVolumeWriteTime*

Monitors the write time for the volume.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.


ResponseTime

VVMVolumeWriteTimeAverage*

Monitors the average write time for the volume.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.




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.


Version 2.4.00


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 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 > VolumeLogging Status (Unixonly)

Accesses the configuration dialog for determining the logging status for the selected volumeinstance.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 instancesunder the selected volume instance.By default, the global VVMPlexState[NT] to VVMPlexStatus 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 > PlexesKernel Status

Accesses the configuration dialog for determining the kernel status for monitored plexinstances under the selected volume 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] to inheritthe custom settings or to reset to the default status mapping rule.


Accesses the dialog for specifying which subdisks under the selected volume instance are tobe 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.


Accesses the configuration dialog for determining the kernel status for monitored subdiskinstances under the selected volume 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.

VVM_VOLUME_CONTAINER

Icon


Version 2.4.00


Parameters

None

InfoBox

Name Description

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





Menu Commands


Configuration > Volumes Accesses the dialog for specifying which volumes under the selected volume containerinstance are 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 VVMVolumeLoggingStatusmapping 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 > 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 instancesunder the selected volume container instance.By default, the global VVMPlexState[NT] to VVMPlexStatus 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.


Version 2.4.00


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 mappingrule, 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 > Subdisks Accesses the dialog for specifying which subdisks under the selected volume containerinstance are 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

108Where to Find Additional Help

Version 2.4.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 can befound 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 109

Version 2.4.00


Index

- A -Abnormalities 51

Access

Executable Files 13

Files 13

Library Files 13

Paths 13

Permissions 13Acknowledge

Logs Alert 63Adapter 48

Add 49, 50

Create 49

Update 50Agent

PATROL 42AIX 13

Application Class

VVM_DAEMON 71

VVM_DAEMON_CONTAINER 73

VVM_DISKDEVICE 74

VVM_DISKDEVICE_CONTAINER 78

VVM_DISKGROUP 79

VVM_DISKGROUP_CONTAINER 82

VVM_DISKPATH 86

VVM_LOG 87

VVM_LOG_CONTAINER 90

VVM_PLEX 91

VVM_SERVER 95

VVM_SUBDISK 98

VVM_VOLUME 101

VVM_VOLUME_CONTAINER 104

- B -Baselines

BMC ProactiveNet Performance Management 51

Generation 51

Manage 51

Requirements 51BMC

BMC Portal 48

BMC ProactiveNet Performance ManagementPortal 11

BMC Software PATROL Agent 11

BMC Software PATROL Console 11

Requirements 11BMC PATROL

Changes 11

pslInstructionMax 11BMC ProactiveNet

Integration 48BMC ProactiveNet Performance Management

Abnormalities 51

Baselines 51

Key Performance Indicators 51

KPI 51

- C -Changes 7

Check

Instance Limits 44Cluster

Configure 54Clustering Application 54

Collectors

VVMCreateDistribution 95

VVMDaemonCollector 95

VVMDiskdeviceCollector 95

VVMDiskgroupCollector 95

VVMLogCollector 95

VVMPlexCollector 95

VVMSubdiskCollector 95

VVMUpdateAgent 95

VVMVolumeCollector 95Command

Configuration 78

Disk Paths 78

Disk Paths Kernel Status 78

Diskdevices 78

Diskdevices Status 78Commands

About 95

Acknowledgement 87

Alarms 87

All 87

Configuration 71, 73, 74, 79, 82, 86, 87,90, 91, 95, 98, 101, 104

Index 110

Version 2.4.00


Commands

Daemon 71

Daemon List 73

Daemon Status 71

Daemons 73

Daemons Status 73

Debug 95

Disk Devices 79, 82

Disk Devices Status 79, 82

Disk Path 86

Disk Path Kernel Status 86

Disk Paths 74, 79, 82

Disk Paths Kernel Status 74, 79, 82

Diskdevice 74

Diskdevice Status 74

Diskgroup 79

Diskgroup Status 79

Diskgroup Topology Report 79

Diskgroups 82

Diskgroups Status 82

Force Discovery 95

Instance Limits 95

KM Status 95

Log 87

Log Alert Acknowledgement 87

Log Filter 87

Log Scan Limit 87

Login 95

Logs 90

Logs Alert Acknowledgement 90

Logs Filter 90

Logs Scan Limit 90

Messages List 90

Monitoring Mode 95

Node Status 95

Paths 95

Plex 91

Plex Kernel Status 91

Plex Status 91

Plexes 79, 82, 101, 104

Plexes Kernel Status 79, 82, 101, 104

Plexes Status 79, 82, 101, 104

Preloading 95

Refresh Parameters 95

Refresh Process Cache 95

Reload Commands 95

Reports 73, 79, 82, 90

Subdisk 98

Subdisk Kernel Status 98

Subdisks 79, 82, 91, 101, 104

Subdisks Kernel Status 79, 82, 91, 101,104

Veritas Volume Manager Topology Report 82

Volume 101

Volume Kernel Status 101

Volume Logging Status 101

Volume Status 101

Volumes 79, 82, 104

Volumes Kernel Status 79, 82, 104

Volumes Logging Status 79, 82, 104

Volumes Status 79, 82, 104

Warnings 87Configure

Cluster 54

Daemons 58

Disk Devices 58

Disk Groups 58

Disk Paths Kernel 58

KM User Account 42

Log Error Filter 61

Log Scan Limit 63

Logs Alert Acknowledgement 63

Multi-Node Monitoring Mode 54

Node Status 60

PATROL Agent 40

Plex 58

Plex Kernel 58

Status 58

Volume 58

Volume Kernel 58

Volume Logging 58

- D -Daemons

Delete 55

Disable 55

Enable 55Data Collectors

Force 67Debug

Disable 64

Enable 64Delete

Daemons 55

Disk Devices 55

Index 111

Version 2.4.00


Delete

Disk Paths 55

Diskgroups 55

Logs 55

Plexes 55

Subdisks 55

Volumes 55Disable

Daemons 55

Debug 64

Disk Devices 55

Disk Paths 55

Diskgroups 55

Logs 55

Plexes 55

Subdisks 55

Volumes 55Discoveries

Force 67Discovery

Verify 44Disk Devices

Delete 55

Disable 55

Enable 55Disk Paths

Delete 55

Disable 55

Enable 55Disk Space

Requirements 17Diskgroups

Delete 55

Disable 55

Enable 55

- E -Enable

Daemons 55

Debug 64

Disk Devices 55

Disk Paths 55

Diskgroups 55

Logs 55

Plexes 55

Subdisks 55

Volumes 55

- F -Failover Group Name 54

Files 18

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 51

Reports 66

- H -help 108

HP-UX 13

- I -Improvement 7

InfoBox

Application Name 95

Application Version 95

Available FS Space 87

Available Space 74

Binary Path 95

Collector Last End 71, 73, 74, 78, 79, 82,86, 87, 90, 91, 98, 101, 104

Collector Last Start 71, 73, 74, 78, 79, 82,86, 87, 90, 91, 98, 101, 104

Collector Name 71, 73, 74, 78, 79, 82, 86,87, 90, 91, 98, 101, 104

Collector Next Start 71, 73, 74, 78, 79, 82,86, 87, 90, 91, 98, 101, 104

Collector Status 71, 73, 74, 78, 79, 82, 86,87, 90, 91, 98, 101, 104

Command 71

Index 112

Version 2.4.00


InfoBox

Copyright 95

Description 71, 87

Device 74, 98

Disk 74, 86, 98

Disk Access Name 86

Diskdevice 74

Drive Letter 101

FS Percent Used 87

Group 74, 86, 91, 98, 101

Host Name 95

ID 79

Installation Path 95

Kernel State 86

KState 91, 98, 101

Last Purge 87

Length 91, 98, 101

Library Path 95

Log File Modification Time 87

Log File Size 87

Log Length 101

Logging 101

Monitoring Mode 95

Monitoring Node 95

Name 71, 79, 87

Node Name(s) 95

Offset 74

Operating System 95

Owner 71

Path 86, 87

PATROL Agent Version 95

PID 71

Platform 95

Plex 91, 98

PPID 71

Product Name 95

Product Release Date 95

Product Version 95

Status 71, 74, 79, 91, 101

Subdisk 98

Support 95

Tag 74

Total FS Space 87

Type 74, 79, 91, 101

Volume 91, 98, 101

Web site 95Install / Un-install 20, 32

BMC Software Installation Utility 17

Log 20

Packages 18

Procedure 20

Setup Files 18Instance Limits

Check 44Integration

BMC ProactiveNet 48Integration Service Agent 49

Introduction 20

Issues

Fixed 7

- K -Key Performance Indicators


Manage 51KM

Configure 42

Initial Setup 45

Load 38, 39, 48

Preload 40

Preloaded 41, 42

Prepare to Load 39

Unload 40, 41, 42

User Account 42KPI


Manage 51

- L -Linux 13

Load

KM 38, 39, 48

PATROL Central 39

Prepare 39Log Error Filter

Configure 61Log Scan Limit

Configure 63Logs

Delete 55

Disable 55

Enable 55Logs Alert

Index 113

Version 2.4.00


Logs Alert

Acknowledge 63

- M -Manage

Baselines 51

Key Performance Indicators 51

KPI 51Monitor Type 49

Multi-Node Monitoring Mode

Configure 54

- N -New features 7

Node Status

Configure 60

- O -Operating Systems

Linux 17, 18, 20, 32

Unix 17, 18, 32

Windows 17, 18, 20, 32Options

Common services 20

Console Systems role 20

Managed System 20

View Log 20Oracle Solaris Cluster 54

Overview 9

- P -Parameter

NBULoginStatus 42Parameters

ExtraFilesList 95

Refresh 67

VVMDaemonCPUDuration 71

VVMDaemonCPUUtilization 71

VVMDaemonDetails 73

VVMDaemonMemorySize 71

VVMDaemonProcessCount 71

VVMDaemonState 71

VVMDaemonStatus 71

VVMDaemonSummary 71

VVMDiskdeviceDetails 82

VVMDiskdeviceIOKBytes 74

VVMDiskdeviceIOKBytesRate 74

VVMDiskdeviceIOOperations 74

VVMDiskdeviceIOOperationsFailed 74

VVMDiskdeviceIOOperationsRate 74

VVMDiskdeviceQueueDepth 74

VVMDiskdeviceReadKBytes 74

VVMDiskdeviceReadKBytesRate 74

VVMDiskdeviceReadOperations 74

VVMDiskdeviceReadOperationsFailed 74

VVMDiskdeviceReadTime 74

VVMDiskdeviceReadTimeAverage 74

VVMDiskdeviceSpaceAvailable 74

VVMDiskdeviceState 74

VVMDiskdeviceStateNT 74

VVMDiskdeviceStatus 74

VVMDiskdeviceSummary 74

VVMDiskdeviceWriteKBytes 74

VVMDiskdeviceWriteKBytesRate 74

VVMDiskdeviceWriteOperations 74

VVMDiskdeviceWriteOperationsFailed 74

VVMDiskdeviceWriteTime 74

VVMDiskdeviceWriteTimeAverage 74

VVMDiskgroupDetails 82

VVMDiskgroupSpaceAvailable 79

VVMDiskgroupState 79

VVMDiskgroupStateNT 79

VVMDiskgroupStatus 79

VVMDiskgroupSummary 79

VVMDiskpathEnabled 74

VVMDiskpathKernelState 86

VVMDiskpathKernelStateNT 86

VVMDiskpathKernelStatus 86

VVMDiskpathNonEnabled 74

VVMDiskpathSummary 86

VVMLogAlarmCount 87

VVMLogAlarmText 87

VVMLogDetails 90

VVMLogFSSpaceUsedPercent 87

VVMLoginStatus 95

VVMLogSpaceAvailable 87

VVMLogSpaceGrowthRate 87

VVMLogSpaceUsed 87

VVMLogSpaceUsedPercent 87

VVMLogSummary 87

VVMLogText 87

VVMLogWarningCount 87

Index 114

Version 2.4.00


Parameters

VVMLogWarningText 87

VVMMonitoringMode 95

VVMNodeStatus 95

VVMPlexDetails 82

VVMPlexIOKBytes 91

VVMPlexIOKBytesRate 91

VVMPlexIOOperations 91

VVMPlexIOOperationsFailed 91

VVMPlexIOOperationsRate 91

VVMPlexKernelState 91

VVMPlexKernelStateNT 91

VVMPlexKernelStatus 91

VVMPlexReadKBytes 91

VVMPlexReadKBytesRate 91

VVMPlexReadOperations 91

VVMPlexReadOperationsFailed 91

VVMPlexReadTime 91

VVMPlexReadTimeAverage 91

VVMPlexState 91

VVMPlexStateNT 91

VVMPlexStatus 91

VVMPlexSummary 91

VVMPlexWriteKBytes 91

VVMPlexWriteKBytesRate 91

VVMPlexWriteOperations 91

VVMPlexWriteOperationsFailed 91

VVMPlexWriteTime 91

VVMPlexWriteTimeAverage 91

VVMSubdiskDetails 82

VVMSubdiskIOKBytes 98

VVMSubdiskIOKBytesRate 98

VVMSubdiskIOOperations 98

VVMSubdiskIOOperationsFailed 98

VVMSubdiskIOOperationsRate 98

VVMSubdiskKernelState 98

VVMSubdiskKernelStateNT 98

VVMSubdiskKernelStatus 98

VVMSubdiskReadKBytes 98

VVMSubdiskReadKBytesRate 98

VVMSubdiskReadOperations 98

VVMSubdiskReadOperationsFailed 98

VVMSubdiskReadTime 98

VVMSubdiskReadTimeAverage 98

VVMSubdiskSummary 98

VVMSubdiskWriteKBytes 98

VVMSubdiskWriteKBytesRate 98

VVMSubdiskWriteOperations 98

VVMSubdiskWriteOperationsFailed 98

VVMSubdiskWriteTime 98

VVMSubdiskWriteTimeAverage 98

VVMVolumeDetails 82

VVMVolumeIOKBytes 101

VVMVolumeIOKBytesRate 101

VVMVolumeIOOperations 101

VVMVolumeIOOperationsFailed 101

VVMVolumeIOOperationsRate 101

VVMVolumeKernelState 101

VVMVolumeKernelStateNT 101

VVMVolumeKernelStatus 101

VVMVolumeLoggingState 101

VVMVolumeLoggingStatus 101

VVMVolumeReadKBytes 101

VVMVolumeReadKBytesRate 101

VVMVolumeReadOperations 101

VVMVolumeReadOperationsFailed 101

VVMVolumeReadTime 101

VVMVolumeReadTimeAverage 101

VVMVolumeState 101

VVMVolumeStateNT 101

VVMVolumeStatus 101

VVMVolumeSummary 101

VVMVolumeWriteKBytes 101

VVMVolumeWriteKBytesRate 101

VVMVolumeWriteOperations 101

VVMVolumeWriteOperationsFailed 101

VVMVolumeWriteTime 101

VVMVolumeWriteTimeAverage 101PATROL

Agent 42

PATROL Agent 40, 41

PATROL Agent system 17

PATROL Central Console 40, 42

PATROL Central Console Server system 17

PATROL Central Web Server system 17

PATROL Console 40, 41

PATROL Console system 17PATROL Agent

Configure 40

Restart 46PATROL Console 39

Restart 46Permissions

Access 13Platform

Upgrade 46Platforms

Unix 42

Index 115

Version 2.4.00


Plexes

Delete 55

Disable 55

Enable 55Preload

KM 40Preloaded

KM 41, 42ProactiveNet 49

PW Commands 50

- R -Refresh

Parameters 67Release Notes 7

remote PATROL Agent Checking 54

Reports

Generate 66Requirements

Additional 11

BMC ProactiveNet Performance ManagementPortal 11

BMC Software PATROL Agent 11

BMC Software PATROL Console 11

Disk Space 17

Security 13

Software 11

Symantec NetBackup™ 11

System 11Restart

PATROL Agent 46

PATROL Console 46

- S -Security

Requirements 13Setup

Check 45

Initial 45

KM 45Solaris 13

Status

Configure 58Subdisks

Delete 55

Disable 55

Enable 55Sudo 42

User 13System

HP-UX 11

IBM AIX 11

Microsoft Windows 11

Oracle Solaris 11

Red Hat Linux 11

Requirements 11

- T -Thresholds

Customize 50

Import 50

- U -Unix 42

Unload

KM 40, 41, 42Upgrade

Platform 46

- V -Verify

Application Discovery 44Veritas Cluster File System 54

Veritas Cluster Server 54

Volumes

Delete 55

Disable 55

Enable 55VVM_DAEMON

Application Class 71VVM_DAEMON_CONTAINER

Application Class 73VVM_DISKDEVICE

Application Class 74VVM_DISKDEVICE_CONTAINER

Application Class 78VVM_DISKGROUP

Application Class 79VVM_DISKGROUP_CONTAINER

Application Class 82

Index 116

Version 2.4.00


VVM_DISKPATH

Application Class 86VVM_LOG

Application Class 87VVM_LOG_CONTAINER

Application Class 90VVM_PLEX

Application Class 91VVM_SERVER

Application Class 95VVM_SUBDISK

Application Class 98VVM_VOLUME

Application Class 101VVM_VOLUME_CONTAINER

Application Class 104

- W -What's new 7

About BMC® SoftwareBMC Software, Inc. NYSE:BMC, is a leading provider of enterprise managementsolutions that empower companies to manage their IT infrastructure from abusiness perspective. Delivering Business Service Management, BMC Softwaresolutions span enterprise systems, applications, databases, and servicemanagement. Founded in 1980, BMC Software has offices worldwide and fiscal2004 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 key monitoring solutions specifically designed to expand thecapabilities of BMC Performance Manager, thus enabling up to 100% coverage ofany infrastructure. Sentry Software specializes in single solutions for multi-platform monitoring of hardware, custom applications or any IT component, andblackout windows. Sentry Software products are deployed in 45 countries acrossthe globe and lead the list of BMC Software’s third-party product sales. For more

information about Sentry Software, please visit www.sentrysoftware.net.

Date post:	06-Feb-2018
Category:	Documents
Upload:	nguyenkhuong
View:	226 times
Download:	0 times

Veritas Volume Manager for PATROL - Sentry Software · PDF file9 Version 2.4.00 Veritas Volume...

Documents