Veritas Volume Manager KM for PATROL

Transcription

1 USER DOCUMENTATION HIGH AVAILABILITY MONITORING Veritas Volume Manager KM for PATROL Version September 2015

2 Contacting BMC Software You can access the BMC Software Web site at From this Web site, you can obtain information about the company, its products, corporate offices, special events, and career opportunities. United States and Canada Address BMC Software, Inc CityWest Blvd. Houston TX Telephone 1 (713) or 1 (800) (Toll Free) 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 are registered trademarks or trademarks of BMC Software, Inc. 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 License Agreement for the product and the proprietary and restricted rights notices included in this documentation. U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section , DFARS , DFARS , DFARS , and DFARS , as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX , USA. Any contract notices should be sent to this address. 2 Restricted Rights Legend

3 Customer Support You can obtain technical support by using the Support page on the BMC Software Web site or by contacting Customer Support by telephone or . Support Web Site You can obtain technical support from BMC Software 24 hours a day, 7 days a week at 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 notices when new product versions are released Find worldwide BMC Software support center locations and contact information, including addresses, fax numbers, and telephone numbers You can also access product documents and search the Knowledge Base for help with an issue at In the United States and Canada, if you need technical support and do not have access to the Web, call Outside the United States and Canada, please contact your local support center for assistance. To find telephone and contact information for the BMC Software support center that services your location, refer to the Contact Customer Support section of the Support page on the BMC Software Web site at 3 Support by Telephone or

4 Table of Contents...12 Requirements...12 System Requirements...12 Software Requirements...14 Security Requirements Disk...18 Space Requirements Getting...19 the BMC Software Installation Utility...19 Packages...20 Extracting the Setup Files...22 Installing Veritas Volume Manager KM for PATROL...35 Uninstalling Veritas Volume Manager KM for PATROL Loading...40 / Unloading the KM...40 Loading the KM Preparing...41 to Load the KM...41 Loading the KM on PATROL Console...41 Loading the KM on PATROL Central...42 Preloading the KM...42 Unloading the KM Unloading...43 the KM from the PATROL Agent Unloading...43 the KM from the PATROL Console Unloading...44 the KM from the PATROL Central Console...44 Configuring the KM User Account...46 Verifying Application Discovery...46 Checking the Instance Limits...48 Checking the Initial Setup of the KM...48 Restarting PATROL Agent and PATROL Console...49 Upgrading the Platform...51 Integrating with BMC Portal...51 Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x...52 Creating and Importing an Adapter for a BMC PATROL KM...53 Updating an Adapter for a BMC PATROL KM...53 Importing and Customizing Thresholds Performing Post-Installation Operations

5 ...54 Managing Baselines and Key Performance Indicators...57 Configuring the KM...57 Configuring the Multi-Node Monitoring Mode...59 Filtering Elements to Monitor...62 Configuring the Element Status...64 Configuring the Node Status...65 Configuring the Log Filter...67 Configuring the Log Scan Limit...68 Configuring Logs Alert Acknowledgement...69 Using the KM...69 Acknowledging Alerts...70 Enabling the Debug Mode...73 Generating Reports...73 Refreshing Parameters Classes...76 and Parameters...77 VVM_DAEMON...79 VVM_DAEMON_CONTAINER...82 VVM_DISKDEVICE...87 VVM_DISKDEVICE_CONTAINER...88 VVM_DISKGROUP...92 VVM_DISKGROUP_CONTAINER VVM_DISKPATH VVM_LOG VVM_LOG_CONTAINER VVM_RLINK VVM_RVG VVM_RVG_CONTAINER VVM_SERVER VVM_SUBDISK VVM_VOLUME VVM_VOLUME_CONTAINER Where to Find Additional Help VVM_PLEX

6 Release Notes for v2.5.01

7 What's New Veritas Volume Manager KM for PATROL now supports Windows VVM-129: The value of the VVMVolumeStateNT parameter was sometimes improperly set to Degraded (=5) instead of Active (=0) on Windows systems; which caused a false alarm to be triggered by the VVMVolumeStatus parameter. VVM-136: The value of the VVMRLinkKernelState parameter was sometimes improperly set to Enabled (=1) instead of Connect (= 0) on Windows systems; which caused a false alarm to be triggered by the VVMRLinkKernelStatus parameter. VVM-143: The KM did not properly interpret the output of the iostat command used to collect statistics from deported volumes on Windows. This resulted in a false alarm to be triggered by the VVMLoginStatus parameter. VVM-153: A false alarm was triggered by the VVMDiskdeviceStatus parameter when monitoring a Storage Foundation 5x system running on Windows. VVM-159: The Microsoft Cluster active node was not properly detected when the KM was operating in multi-node monitoring mode. VVM-174: The Sudo configuration requirements have been updated in the Security Requirements chapter of the user documentation. VVM-180: When SRL Overflow Protection was set to "DCM" or "AutoDCM", the KM did not trigger an alert when DCM logging was activated. A new state has been added to the VVMRLinkKernelState of the VVM_RLINK application class, DCM Logging (2), which by default triggers an alarm through VVMRLinkKernelStatus. VVM-188: The status report file of Veritas Volume Manager KM for PATROL is now suffixed with the Agent port number to avoid overwriting it when multiple virtual Agents are used. VVM-189: Invalid alarms were triggered on the VCSLoginStatus parameter when the KM was unable to check the active node. VVM-190: The main discovery cycle was irregular due to an asynchronous default KM discovery interval. It is now reduced to 30 seconds to avoid such irregularity. VVM-191: On Windows systems, if the PATROL Agent installation path contained spaces, scripts calls and output redirection commands failed. 7 Fixed Issues

8 8

9 Overview

10 Veritas Volume Manager KM for PATROL (or VVM KM) helps you ensure that your Veritas Volume Manager installations run efficiently 24 hours a day. The KM more especially monitors: Server: monitors overall health of the Veritas Volume Manager and it is critical daemons. Disks and Multi Paths: monitors the health of disk devices and dynamic multi-pathing (DMP). Logs: checks regularly for any errors in the system and event logs and monitors the log space utilization. Logical Volumes: automatically discovers and monitors volumes, plexes and subdisks. Replication (VVR): monitors status and performance of replicated volume groups (RVGs) and replication links (RLINKs). Performance: collects I/O performance statistics at disk, volume, plex & subdisk levels to help identify any bottlenecks. All the information collected is grouped into application classes and displayed in the PATROL Console. Alarms and warnings inform you when a suspicious behavior is detected; thus allowing you to quickly and 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. 10

11 Preparing for Installation

12 This chapter provides information about the tasks that must be performed before you start installing Veritas Volume Manager KM for PATROL. Make sure to carefully read the following sections requirements: 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 Requirements The following list shows the operating systems and their versions supported by Veritas Volume Manager KM for PATROL. Microsoft Windows Server 2003, 2008 and 2012, all versions supported by BMC PATROL Agent 3.7 and greater Linux, all distributions supported by BMC PATROL Agent 3.7 and greater Sun Solaris 8, 9, 10 and 11 supported by BMC PATROL Agent 3.7 and greater HP-UX 11, supported by BMC PATROL Agent 3.7 and greater IBM AIX 5.x and 6.x, supported by BMC PATROL Agent 3.7 and greater If the operating system is upgraded (or downgraded) at a later date, you will need to reload commands for the Veritas Volume Manager KM for PATROL. Refer to Upgrading the Platform. Software Requirements The following table contains a list of required software and their versions supported by Veritas Volume Manager KM for PATROL. Software Version Veritas Volume Manager (included in Veritas Storage Foundation Suites) 4.5, 5.0, 5.1, 6.x BMC Software PATROL Agent , 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 9.x 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 Manager 8.x, 8.5.x, 8.6.x, 9.x 12 Software Requirements

13 BMC TrueSight Operations Management 10 Version 2.5 of Veritas Volume Manager KM for PATROL does not support Veritas Volume Manager versions before 3.2 and PATROL Agent versions before 3.4. If the operating system is upgraded (or downgraded) at a later date, you will need to reload commands 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 Veritas Volume 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 least 5,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. 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)< ){pconfig("replace",v, );} In large Veritas Volume Manager systems, the value of 5,000,000 for the tuning variable pslinstructionmax may still be insufficient. In such situations, error messages will appear on the PATROL Console System Output Window (SOW) reporting that some VVM KM data collectors are in an infinite loop. In this case you can set the tuning variable to zero to disable this functionality. The KM stores all configuration information in the PATROL Agent configuration database 13 Requirements This PATROL Agent tuning variable can be updated using wpconfig (on Microsoft Windows), xpconfig (on Unix) or PATROL Configuration Manager (PCM). Alternatively, you can use one of the following single line PSL command through the PATROL Console OS> prompt to update this tuning variable.

14 (pconfig), under paths /VVM and /Runtime/VVM. PATROL Agent user (default: patrol) should be able to read and write to these pconfig variables at anytime. If Access Control List (ACL) is used to control which users are authorized to connect to a PATROL Agent, please ensure that the mode for PATROL Agent user includes C in the PATROL Agent variable /AgentSetup/ accesscontrollist. Please refer the PATROL Agent Ref erence Manual for more details You cannot copy or distribute these KM configuration variables between managed nodes, because they may not have the same value for each managed node. For example, the login user details may not be the same for all managed nodes. Also some of these variables, like installation paths, are set automatically during the initial discovery Additional Software Requirements The following table contains a list of additional software requirements of Veritas Volume Manager KM for PATROL: Purpose Software Version When running VVM KM with sudo user account on Solaris, HP-UX, AIX or Linux managed nodes Sudo (superuser do) or later When running VVM KM on Linux managed nodes Korn shell binary (/bin/ksh) Any When running VVM KM on Microsoft Windows x64 managed nodes Reg.exe patch KB ( Any Security Requirements By default, Veritas Volume Manager is installed and run as the root user (on Unix) or as administrator user (on Microsoft Windows). Veritas Volume Manager KM for PATROL needs to be run as a user account with administrative privileges to read and execute Veritas Volume Manager application programs and file systems. Login details of this user are configured in the KM during the configuration. The password is stored in the PATROL Agent in a DES encrypted format. Requirements 14 The Microsoft Windows x64 Reg.exe patch, KB is required to allow access to 64-bit registry keys from PATROL Agent. Access the above patch site from the managed node to obtain the correct patch for that platform.

15 The encrypted password can be viewed by any user who has access to the PATROL Agent configuration variables (pconfig). This user could then execute PSL statements using the encrypted password through the PATROL Console. This can be prevented by setting up an appropriate Access Control List (ACL) for users. Please refer to the PATROL Agent Reference Manual for details on how to set up an ACL. One of the following user accounts can be used for configuring the login details of the KM: 1. root user (Unix) or administrator user (Microsoft Windows) 2. a non-root user, such as patrol, with sudo privileges on Veritas Volume Manager to execute application programs and access the file systems (Unix only) 3. a non-root (Unix) or non-administrator (Microsoft Windows) account, such as patrol, configured in Veritas 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 paths listed below. The Veritas Volume Manager installation path INSTALL_PATH, referenced in the tables below is normally /opt/vrtsvxvm (on Unix) or C:\Program Files\Veritas\Volume Manager x.x (on Microsoft Windows). 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 to the following cluster commands: /opt/vrtsvcs/bin/hagrp (in Veritas Cluster Server) vxdctl (in Veritas Cluster File System) /usr/cluster/bin/clrg (in Oracle Solaris Cluster) C:\Windows\sysnative\cluster (in Microsoft Cluster) The VVM KM includes some scripts which should be executable by the PATROL Agent user and the VVM KM user. These scripts are stored under KM_HOME path, normally PATROL_HOME/lib/ VVM. 15 Requirements Executable and Library Files accessed by VVM KM User

16 In addition to these Veritas Volume Manager commands, VVM KM executes other operating system commands, such as ps, uname which may not require special privileges. To list all OS commands used by the VVM KM, execute the following PSL code from the PATROL Console, using PSL Task menu, after installing and loading the KM. i=0; sudoers=""; foreach var (grep("^/runtime/vvm/commandcontrols/",pconfig("list"))) { ctl=get(var); opt=ntharg(grep("option",ctl),"2-"," ="); nsa=ntharg(grep("nosudoattempt",ctl),"2-"," ="); sua=ntharg(grep("singleuserattempt",ctl),"2-"," ="); typ=ntharg(grep("commandtype",ctl),"2-"," ="); cmd=nthargf(grep("commandtext",ctl),"2-","=","="); if((typ == "") (typ == "OS")) { met=""; if(opt == "NoLogin") { met = "(run as patrol user)"; } elsif(nsa == "YES") { met = "(run as configured user without sudo)"; } elsif(sua == "YES") { met = "(run as supplied user - used in menu)"; } else { scmd=cmd; s=index(scmd,"%sudo"); if(s) { scmd=replace(substr(scmd,s,length(scmd)),"%sudo",""); } sudoers=union(sudoers,ntharg(ntharg(scmd,1," "),"1-"," "," ")); } printf("(%2d) %-30s %-40s: %s\n",i++,ntharg(var,"5","/"),met,cmd); } } printf("\n\ncommands used with sudo:\n%s",sort(sudoers)); /var/adm/messages (on Solaris) /var/adm/syslog/syslog.log (on HP-UX) /var/log/messages (on Linux and AIX) If a monitored log file cannot be read by the PATROL Agent user, it will be copied to KM_TEMP path using the configured login account, and processed by the PATROL Agent user. On completion the copied log file will be removed. This may increase the file system usage under KM_TEMP temporarily during this activity. Requirements 16 The PATROL Agent user (normally patrol) needs read & execute permission to following paths and files:

17 On Windows platforms the Veritas Volume Manager installation is identified by checking the Microsoft Windows Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\VxSvc\ The configured login user should have sufficient privileges to run regedit command on the managed node. 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 a sudoer through the visudo utility using code appropriate for your platform as detailed below. This user should be able to execute VxVM commands and OS commands. The code below also applies to all non-root users who may execute VVM KM administration and report menu commands using their sudo privileges. The KM accepts any non-root user with the following sudo configuration in the sudoers file. Please replace user1, user2, user3 with appropriate KM user name. The Veritas 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 /opt/bmc/patrol3/solaris29-sun4/). This non-root sudo user configured in the KM will be able to execute Veritas Volume Manager commands. To prevent unauthorized access, ensure this user is only used within the KM and not made 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 configured differently, the KM may run sudo commands using incorrect sudo settings, which may expose the sudo user password. On Solaris: User_Alias VVMKMUSERS = user1, user2, user3 Defaults:VVMKMUSERS!lecture,!authenticate,!requiretty,\ env_keep+="path 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/* user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH and PATROL_HOME with the relevant paths. On HP-UX: User_Alias VVMKMUSERS = user1, user2, user3 Defaults:VVMKMUSERS!lecture,!authenticate,!requiretty,\ 17 Requirements

18 env_keep+="path SHLIB_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/* user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH and PATROL_HOME with the relevant paths. On AIX & Linux: User_Alias VVMKMUSERS = user1, user2, user3 Defaults:VVMKMUSERS!lecture,!authenticate,!requiretty,\ env_keep+="path LIBPATH 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/* user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH and PATROL_HOME with the relevant paths. Disk Space Requirements Veritas 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 When monitoring a standard installation of Veritas Volume Manager using VVM KM, the PATROL Agent will generate approximately 250 KBytes of history data per day. An enterprise installation of Veritas Volume 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 PATROL depending on the PATROL Agent history retention period. During execution, the VVM KM creates and maintains temporary files under KM_HOME, KM_TEMP and KM_DEBUG paths. By default they are all under PATROL_HOME/lib/VVM, where PATROL_HOME path is normally /opt/bmc/patrol3/ (on Unix) or C:\Program Files (x86)\bmc Software\Patrol3\ (on Microsoft Windows). If the location of the KM_TEMP or KM_DEBUG is not suitable, it can be changed using the Configuration > Paths menu from the main instance. These folder should have read, write and execute permissions for both the PATROL Agent user and the KM login user. Requirements 18 The VVM KM is installed under the PATROL installation path.

19 Getting the BMC Software Installation Utility In order to install Veritas Volume Manager KM for PATROL, you need the latest version of the BMC Software Installation Utility. You can download the latest Installation Utility from the BMC Software EPD (electronic product download) from: logon.jsp on the BMC Software Website, or from the Veritas Volume Manager KM for PATROL page on the Sentry Software Website Choose the appropriate package depending on the platform you plan to install Veritas Volume Manager KM for PATROL on: For UNIX/Linux systems: ins_all_<version>.tar For Windows systems: ins_windows_<version>.exe The packages are valid for all the PATROL components: Agent, Console, Console Server, etc. Place the Installation Utility package in the same folder as the Veritas Volume Manager KM for PATROL packages. Packages The Veritas Volume Manager KM for PATROL packages are available on the Sentry Software Web site. Downloading from Sentry Software Web site vvm_all_2500.zip vvm_all_2500.tar The Veritas Volume Manager KM for PATROL packages are designed for use with the BMC Software Installation Utility (formerly known as Thorium). They need to be merged with the latest available version of the BMC Software Installation Utility. Please see instructions. 19 Getting the BMC Software Installation Utility 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 package download source, the file names may differ:

20 Extracting the Setup Files Like most Knowledge Modules for PATROL, you need to install Veritas Volume Manager KM for PATROL on the following components of your PATROL architecture: Every managed system with a PATROL Agent Every PATROL Console (Classic) that will show Veritas Volume Manager performance-related information and alerts The Console Server PATROL Central Web Edition Extracting the Setup Files 20

21 Installing the KM

22 Introduction This section describes the installation procedure for Veritas Volume Manager KM for PATROL on any PATROL component (Agents, Consoles, Console Server, etc.). As the setup is based on the BMC Software Installation Utility, this procedure applies to all operating systems supported by Veritas Volume Manager KM for PATROL. Installing Veritas Volume Manager KM for PATROL Installing Veritas Volume Manager KM for PATROL is an automated process managed by a wizard. The wizard goes through the necessary steps to install Veritas Volume Manager KM for PATROL and all files associated with it. You are simply prompt for the product's folder location and the product/components to install. Browse to the bmc_products folder where the files have been extracted (both Veritas Volume Manager KM for PATROL and the Common Installer). 22

23 On Windows: Launch the setup.exe program On UNIX: Launch the setup.sh script To install Veritas Volume Manager KM for PATROL 1. Allow the perl.exe program to listen on this port: Click Allow access. Installation Wizard - Step 1: Windows Security Alert 23 Installing Veritas Volume Manager KM for PATROL

24 2. The welcome screen of the installer appears. Click Next to continue. Installation Wizard - Step 2: Welcome Installing Veritas Volume Manager KM for PATROL 24

25 3. Read the license agreement, click the Accept option and then click Next to continue. Installation Wizard - Step 3: Reviewing License Agreement 25 Installing Veritas Volume Manager KM for PATROL

26 4. Select Install the products on this computer now and click Next to continue. Installation Wizard - Step 4: Selecting Installation Options Installing Veritas Volume Manager KM for PATROL 26

27 5. Specify the BMC Software products folder. See the BMC Software documentation for more information about the BMC Software products folder. Click Next to continue. Installation Wizard - Step 5: Selecting the Installation Directory 27 Installing Veritas Volume Manager KM for PATROL

28 6. Select Default. Installing Veritas Volume Manager KM for PATROL does not require any customization. Click Next to continue. 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 Classic Console. Common services to install Veritas Volume Manager KM for PATROL on the Console Server or on PATROL Central Web Edition. Click Next to continue. Installing Veritas Volume Manager KM for PATROL 28 Installation Wizard - Step 6: Selecting an Installation Type

29 Installation Wizard - Step 7: Selecting Roles Select as many options as required. 29 Installing Veritas Volume Manager KM for PATROL

30 8. Check the Veritas Volume Manager KM for PATROL box to install the KM (it should be selected by default). Click Next to continue. Installation Wizard - Step 8: Selecting Products and Components Installing Veritas Volume Manager KM for PATROL 30

31 9. Review the installation parameters and click Start Install to launch the installation procedure. Installation Wizard - Step 9: Reviewing Installation Options 31 Installing Veritas Volume Manager KM for PATROL

32 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 Installing Veritas Volume Manager KM for PATROL 32

33 11. The wizard displays the installation results. Click View Log to display a detailed log of the installation procedure. Click Next and then Finish to exit the setup program. Installation Wizard - Step 11: Installation Results 12. Click the Finish button to complete and close the installation wizard. 33 Installing Veritas Volume Manager KM for PATROL

34 Installation Wizard - Step 12: Completing 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 button allows you to stop the installation procedure. Installing Veritas Volume Manager KM for PATROL 34

35 Uninstalling Veritas Volume Manager 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 and all 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 PATROL 1. Locate the Uninstall folder under the BMC products directory (typically under C:\Program Files\BMC Software, or /opt/bmc): On Windows systems, launch uninstall.exe On UNIX, launch uninstall.sh Un-install Wizard Welcome Step 35 Installing Veritas Volume Manager KM for PATROL

36 2. Specify the BMC Software products folder. See the BMC Software documentation for more information about the BMC Software products folder. Un-install Wizard Specifying folder Uninstalling Veritas Volume Manager KM for PATROL 36

37 3. To uninstall the KM, select Veritas Volume Manager KM for PATROL. Un-install Wizard Selecting Products and Components Directory 37 Uninstalling Veritas Volume Manager KM for PATROL

38 4. Click Start Uninstall. Un-install Wizard Reviewing Selected Products & components and start uninstalling Uninstalling Veritas Volume Manager KM for PATROL 38

39 5. A page displays the list of products/components processed and the percentage of completion. Click Next to continue. Un-install Wizard Status 39 Uninstalling Veritas Volume Manager KM for PATROL

40 6. A page displaying SUCCESS indicates that Veritas Volume Manager KM for PATROL is now uninstalled. Un-install Wizard Uninstall Results Loading / Unloading the KM 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 Microsoft Windows and Unix platforms. Before you load the VVM KM, you must install the KM on PATROL Console and PATROL Agent systems. Uninstalling Veritas Volume Manager KM for PATROL 40 Once installed the KM will have to be preloaded on one of the following PATROL consoles:

41 Preparing to Load the KM 1. 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 Console To load the KM on a PATROL Console: 1. From the PATROL Console menu bar, choose File > Load KM 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 start discovering 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 error messages on the PATROL Console System Output Window (SOW) during the initial discovery. If you want to save the new list of loaded files as the PATROL Console user preference: 1. From the PATROL Console menu bar, choose File > Save Configuration 2. Load the VVM_LOAD.kml file on each PATROL Console. 3. Configure the KM. To load the KM on PATROL Central: 1. In the Console, right-click the Managed System and select Load Knowledge Modules... The Load Knowledge Modules wizard is displayed 2. Click Next 3. Select the managed systems where the VVM KM is to be loaded, and click Next >. The wizard will display a list of all available.kml files for the managed systems you selected. 4. Select the VVM_LOAD.kml file for each managed system, click Next> and Finish. The VVM KM will be loaded to the PATROL Central Console Server, and all connected selected managed systems will start discovering the Veritas Volume Manager environment. If the automatic discovery successfully finds the Veritas Volume Manager installation, the VVM_SETUP instance will be instantiated. 41 Loading / Unloading the KM Loading the KM on PATROL Central

42 This automatic discovery may take up to 5 minutes to instantiate the VVM_SETUP instance. Look for any error messages on the PATROL Central System Output Window (SOW) during the initial discovery. 5. Load the VVM_LOAD.kml file on each PATROL Central Management Profile where VVM KMis to be loaded. 6. Configure the KM. Preloading the KM To enable Veritas Volume Manager KM for PATROL to operate all the time, without a PATROL Console connection: 1. right-click the Veritas Volume Manager instance and select KM commands > Configuration > Preloading Preloading Configuration dialog 2. Click Add to add the KM files to the list of preloaded KMs. The KM will thus be added to the PATROL Agent configuration variable/agentsetup/ preloadedkms This section describes the procedures for unloading (not uninstalling) the VVM KM from the PATROL Agent, PATROL Console or PATROL Central Console. The intention is that this section is only used if you no longer want to use some parts of the KM, though there may be circumstances where you may wish to fully unload the KM without uninstalling the files. If you want to completely uninstall the KM, please follow the uninstall procedure. If you are attempting to unload the KM 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 that system when there is no connection to a PATROL Console with VVM KM loaded. from PATROL Console: the PATROL Console stops displaying and monitoring the Veritas Volume Manager application on any PATROL Console connected system. Loading / Unloading the KM 42 Unloading the KM

43 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 be unloaded. You can also use the utility wpconfig (on Microsoft Windows) or xpconfig to unload the KM. You will then have to remove VVM_LOAD.kml from the PATROL Agent configuration variable /AgentSetup/ preloadedkms. The KM cannot be partially unloaded from the PATROL Agent using the above steps. If you need to unload some parts of the KM from the PATROL Agent, refer to the PATROL Agent Reference Manual. Unloading the KM from the PATROL Console Application classes are unloaded individually. This allows for a partial unloading of the KM to enable it to run as a reduced installation. To unload the VVM KM completely or partially: 1. Remove the unwanted application classes that starts with VVM_ in the list of loaded application classes as described below: 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 Application Classes. 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 the PATROL Console user preference. 3. Repeat these steps on every PATROL Console system where the VVM KM is to be unloaded. 43 Loading / Unloading the KM With the PATROL Console for Unix:

44 Unloading the KM from the PATROL Central Console A KM can be unloaded from particular managed systems or for all systems across the monitored environment. Application classes may be unloaded individually, or by selecting all classes at once. This allows for a partial unloading of the KM to enable it to run as a reduced installation on some or all of the managed systems. 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 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 be unloaded. Performing Post-Installation Operations Configuring the KM User Account A user account with administrative privileges must be configured in BMC PATROL to read and execute Veritas Volume Manager application programs and file systems. Depending on the operating systems used, several options will be available. On Unix platforms, you can use the following user accounts: a root user a non-root user, such as patrol, that has sudo privileges on Veritas Volume Manager to execute application programs and access file systems a non-root account, such as patrol, configured in Veritas Volume Manager application to administer the Veritas Volume Manager application. Loading / Unloading the KM 44 It is recommended to perform post installation checks once the KM is installed and loaded on the PATROL 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.

45 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 to administer 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: 2. To use: the default PATROL Agent Account, check the Use Agent Default Account box. The login details entered in the Username and Password fields will then be ignored. a different user account, enter the login details in the Username and Password fields 3. If a sudo user account is used: check the Use Sudo box click SUDO Binary File to verify the sudo binary file path 4. Click OK. If the credentials are not valid, the VVMLoginStatus parameter will appear in suspicious state after the next data collection. 45 Performing Post-Installation Operations Login Configuration dialog

46 Verifying Application Discovery To verify the application discovery: 1. Check that the VVM_SETUP instance is actually named Veritas Volume Manager. If not, force a full discovery by right-clicking the VVM_SETUP instance > KM Commands > Force Discovery 2. Check that the application class instances are actually instantiated. The initial data collection may take 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 Limits By default, Veritas Volume Manager KM for PATROL does not limit the number of instances that are discovered or monitored for each monitored elements. However, in order to optimize performance in large environment, it is possible to disable or limit the monitoring of specific elements: Performing Post-Installation Operations 46

47 To modify the default configuration VVM KM Default Instance Limits 2. Enter the number of instances to be displayed in the console for each monitored element 3. To disable the monitoring of a specific application class, enter 0 in the relevant field 4. Click OK. 47 Performing Post-Installation Operations 1. In the Console, right-click the KM main icon > Configuration> Instance Limits

48 Checking the Initial Setup of the KM To 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 set correctly. 3. Under each container instance, open all detail parameters (text parameters with names in the format VVM<Object>Details), and check for error messages. 4. Check the new value of parameter VVMLoginStatus set after completion of all data collection. If either is not in OK state, open the annotation point to determine the cause of the error. 5. After the KM has been running for at least an hour: Right-click the KM main icon > KM commands > KM Status from the Veritas Volume Manager instance. A report is displayed, detailing information on the managed system. Search the report for warnings or alarms. If errors are found during any of the above steps (including incorrect data in Infoboxes or any warnings or alarms in the KM Status report), determine the cause(s) and take action to resolve these errors. If required, the Technical Support and attach the KM Status report. If needed, click Save As Task to open the report in a task window. You will be able to later save it as a text file or print it. If any errors are found during any of the above steps (including any incorrect data in Infoboxes or any warnings or alarms in the KM Status report), determine the cause(s) and take steps to resolve these errors. You may need to refer to the User Guide, or contact Technical Support, attaching the KM Status report. Restarting PATROL Agent and PATROL Console Restarting the PATROL Agent and PATROL Console is optional but often a good practice to confirm that the VVM KM operates correctly after restarting the PATROL Agent and/or PATROL Console. In addition, the PATROL Agent restart will force all KM discoveries and data collections to start immediately. Performing Post-Installation Operations 48 To save the KM Status report as a task window, click Save As Task. This task window can then be printed or saved as a text file.

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

50 Integrating the KM

51 Introduction This section provides detailed information about the integration of Veritas Volume Manager KM for PATROL with BMC ProactiveNet Performance Management. Integrating with BMC Portal Log on to BMC Portal with appropriate credentials to add infrastructure elements. Click on Configure tab. Under Tasks, select Elements to open the Elements page. Click Add. Select Infrastructure Element, and click Next. Select appropriate RSM, and click Next. Enter the label for the element, select PATROL Integration, and click Next. Select/create a group name, and click Next. Select appropriate method to discover the PATROL Agent hosts, and click Next. Fill the required details for discovering the PATROL Agents, and click Commit. Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x To integrate a BMC PATROL KM into BMC ProactiveNet Performance Management 8.5.x or 8.6.x, you need to create a specific adapter. An adapter for BMC PATROL facilitates pulling of performance data from existing BMC PATROL solutions into BMC ProactiveNet. Using an Adapter, you can import BMC PATROL application classes (provided in a Knowledge Module KM) into BMC ProactiveNet. The Adapter periodically synchronizes the performance data collected by these application classes into BMC ProactiveNet. 51 Overview

52 Creating and Importing an Adapter for a BMC PATROL KM Creating an Adapter for a BMC PATROL KM 1. 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 > BMC PATROL. 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 the integration of the targeted KM into BMC ProactiveNet. Select the Agent where this instance of the Adapter will be executed Enter the Integration Service Agent hostname or IP address Enter the Integration Service Agent Port. The default port is 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 7. Click Next to start the import process. The system displays a summary of the application class import, click Next to continue. 8. Select the application classes you wish to auto-synchronize with the Integration Service Agent. 9. Click Next to continue 10. Set the Filter details if need. 11. Click Next to continue. 12. Set the Auto-sync poll scheduling, if needed. 13. Click Next to continue. The system displays a summary of your settings, click Finish to confirm. The Adapter has been added to the Adapters folder of the Administration Console. 14. To see the class instances that have been imported by the Adapter, expand the Adapters folder, right-click the Adapter and select Details. We strongly recommend that you create a specific adapter for each KM you need to integrate into BMC ProactiveNet to enable the update of a single KM independently. Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x 52 Unselecting will delete the application classes that have already been imported during a previous operation. Application classes ready to be deleted are marked with a red x.

53 Updating an Adapter for a BMC PATROL KM Updating an Adapter 1. Delete the Adapter instance 2. Go through the Add an Adapter wizard to actually delete the monitor types that had been created based on the previous version of the KM 3. Close 4. Resume the entire Creating an Adapter for a BMC PATROL KM procedure For complete and detailed information on these procedures, please refer to the BMC ProactiveNet documentation available from BMC Web site. Importing and Customizing Thresholds 1. 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 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 properly converted 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 53 Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x The command has produced a text file with all the parameter threshold settings.

54 -v enables the Verbose mode Class-level thresholds can be displayed using the Absolute Global Thresholds panel in the BMC ProactiveNet Operator Console, while instance-level thresholds are displayed in the Absolute Instance Thresholds panel to indicate thresholds have been successfully imported into BMC ProactiveNet. Managing Baselines and Key Performance Indicators In order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNet calculates baselines per parameter (metrics or attributes) based on values collected over a specified period of time to determine a normal operating range. When the collected values for these parameters are out of range, an alert is triggered. Some parameters are identified by default as Key Performance Indicators and therefore automatically included in the base lining calculation. Managing baselines The baseline is the expected normal operating range for a metric or attribute of a monitor. Requirements for baseline generation For baselines to be generated for an attribute, that abnormality threshold means that the threshold exists and is not suppressed. Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes that have an active 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. Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x 54 The baseline is calculated by collecting the values for a monitor s attributes and metrics over a specified time period and establishing a low baseline value (consisting of the 10th percentile of all the values for a given time period) and a high baseline value (consisting of the 90th percentile of all the values for a given time period), taking a weighted average of these values over time. A higher weight is given to the latest data being factored into the baseline average. The accuracy of the baseline improves over time.

55 Managing Key Performance Indicators The KPI attribute of a parameter can be activated or deactivated manually through the BMC ProactiveNet Administration Console. In this KM, some parameters or attributes have been designated as important indicators 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 Administration Console. To add or remove Key Performance Indicator (KPI) attributes for a monitor type 1. In the Administration Console, from the menu bar, choose Tools > KPI Administration. The KPI Administration dialog box is displayed. 2. From the Monitor Type list, choose the monitor type for which you want to add or remove KPI attributes. 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 monitor type For complete and detailed information on this procedure, please refer to the BMC ProactiveNet documentation available from BMC Web site. Parameters for which the system by default calculates baselines as well as parameters considered as KPIs are respectively identified by the following icons: Baselining KPI 55 Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x

56 Monitoring your Environment

57 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 and performance of the disk arrays controlled. Configuring the KM The configuration instructions provided in this section should be followed on all PATROL Agent Systems where Veritas Volume Manager KM for PATROL is installed. Before configuring the KM, make sure: the KM is loaded on the PATROL Console the VVM_SETUP or Veritas Volume Manager instance is displayed in the Console. Configuring the Multi-Node Monitoring Mode If the Veritas Volume Manager environment is installed in a cluster using Veritas Cluster Server, Veritas Cluster File System, Oracle Solaris Cluster or Microsoft Cluster, the VVM KM must be installed on all the cluster nodes to enable continuous monitoring and avoid single point of failure. To avoid duplicate alerts from multiple nodes, it is recommended to configure the solution to operate in multi-node monitoring mode. To configure the multi-node monitoring mode: 57

58 1. In the Console, right-click the Veritas Volume Manager instance > KM Commands > Configuration > Monitoring Mode Configuring the Multi-Node Monitoring Mode 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 Volume Manager components will be monitored. If a managed node is unable to determine the system which should be in Active Multi-node Mode, it will change to Temporary Single-node Mode. Configuring the KM 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 Cluster File System. The VVM KM will then monitor the entire cluster from the active master system, which is identified by the vxdctl -c mode command. This method requires vxconfigd in enable mode with its clustered state active. 5. Enable Remote PATROL Agent Checking to check the monitoring status of the other nodes and click OK 6. Indicate all the information required to communicate with the remote PATROL Agent (authentication server, protocol, port number, and credentials) 7. Click OK.

59 Filtering Elements to Monitor By default, the solution monitors all the elements discovered, which may represent an important workload to the agents and servers. Because the monitoring of some elements may be irrelevant for various 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 wish to 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 VVM engine log file will be monitored on AIX and Microsoft Windows platforms since there is no ASCII format system log file to monitor. Disk Paths > KM Command > Configuration > Disk Paths to filter disk paths to be monitored Diskgroups > KM Commands Configuration > Diskgroups to filter diskgroups to be monitored Disk Devices > KM Commands > Configuration > Disk Devices to filter disk devices to be monitored RLinks > KM Commands > Configuration > Replication Links to filter replication links to be monitored RVGs> KM Commands > Configuration > Replicated Volume Groups to filter replicated volumes groups to be monitored Volumes > KM Commands > Configuration > Volumes to filter volumes to be monitored Plexes > KM Commands Configuration > Plexes to filter plexes to be monitored Subdisks > KM Commands > Configuration > Subdisks to filter subdisks to be monitored 59 Configuring the KM

60 Filtering Elements to Monitor 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. Configuring the KM 60 The [ALL] entry ensures that all the elements found during PATROL discovery are instantiated and monitored. Daemons marked as enabled are monitored by default; those marked as disabled are instantiated in an OFFLINE state.

61 3. To disable elements for monitoring: In the current configuration list, select the elements to disable Select Disable Click Update Disabled instances will be instantiated in an OFFLINE state. Commands will not be executed, thus leaving parameters not set. 4. To delete elements monitoring rules: In the current configuration list, select the elements to delete Select Delete Click Update 5. To add a new element monitoring rule: (Optional) Check the Regular Expression box if you want to use a regular expression to enable or disable elements monitoring Type the name of the element to be monitored or the regular expression required If needed, enter a description From the Status list, select Enable Click Update. To revert to the default monitoring configuration, type [default] as a new entry and click Update. 6. Resume the procedure for all the application classes for which you wish to apply monitoring filters. 61 Configuring the KM

62 Configuring the Element Status The status of an element is determined by the State parameter and by the status mapping rule. This mapping rule indicates which states will trigger a warning or an alarm on the Status parameter. It can be configured as follows: 1. In the Console, right-click one of the instance for which you want to configure status and select > KM commands > Configuration > Element Status Deamon Status Configuration Dialog Configuring the KM 62

63 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 warning when the Deamon state is Stopped for more than 60 minutes: From the State list, select 6 (Stopped) From the Condition list, select > In the Minutes field, enter 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 alarm when 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 Click Update. To revert to the default status mapping rule for either filter, select [default] from the list of states and click Update. 7. Resume the procedure for all the application classes for which you wish to apply monitoring filters. 63 Configuring the KM

64 Configuring the Node Status VVM 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 Configuring the KM 64

65 2. In the Monitored daemons list, select the daemons that won't be used to determine the node status 3. In the Daemon field, list the daemons to be used to determine the node status. The Daemon list must be comma-delimited. 4. To use default settings, type [default] in the Daemon field 5. Click Update. The VVMNodeStatus parameter will then be set to: Suspicious if any command run by the VVM KM returns a server error message Failure if any configured daemon is not running. Several recovery actions will then be initiated. To revert to the shipped default list of monitored daemons (as shown above), type [default] as a new daemon for the list and click Update. Configuring the Log Filter A log error filter can be configured to specify the regular expressions that will generate a warning or an alarm. Each time the KM will find these expressions in a log file or in VVMLogText, the error message will be written to the VVMLogAlarmText or VVMLogWarningText parameter. By default, the default log filter is configured for the system log file. If you enabled additional log files for monitoring, you will have to customize the log filter by adding appropriate expressions for those log files. 65 Configuring the KM

66 To configure the log error 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. Configuring the KM In the Console, right-click the Logs instance > KM Commands > Configuration > Logs Filter

67 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 can also limit the exclusion to a particular expression already listed by using standard wildcard syntax, such as skipping. otlsol06. Select Exclude 6. Click Update. Configuring the Log Scan Limit The VVM KM scans log files by reading the new log entries since the last data collection cycle. By default, only 500 KBytes of data is scanned for each log file during each data collection cycle. This log scan 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) Scan Limit 67 Configuring the KM

68 Log Scan Limit Configuration dialog 2. Indicate the amount of data that will be read by the KM during each data collection cycle 3. Click OK. Configuring Logs Alert Acknowledgement By default, alerts will automatically be acknowledged unless you modified the settings to allow manual acknowledgement. Manual acknowledgement may impact the performance of the application and of the PATROL Agent if 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. Configuring the KM 68

69 Using the KM This section describes all the features available for Veritas Volume Manager KM for PATROL. Acknowledging Alerts By default, alerts are acknowledged automatically. If you modified the alert acknowledgement default settings, 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 VVMLogWarningText parameter Alarms to view, select, and individually acknowledge errors in the VVMLogAlarmText parameter All to acknowledge all alerts (Warnings and Alarms) at once without viewing. 69 Configuring the KM

70 Enabling the Debug Mode When you encounter an issue and wish to report it to Sentry Software, you will be asked to enable the Debug Mode and provide the debug output to the Sentry Software support team: 1. In the Console, right-click the Veritas Volume Manager instance > KM Commands > Configuration > Debug. VVM KM Debug Configuration dialog Using the KM 70

71 2. Select On for the debug switch(es) you want to enable. The table below shows the application classes and collector parameters included in the debug switch for each object Object Debug Switch Application Classes Collector Parameters Server VVM_SERVER VVMCreateDistribution VVMUpdateAgent Daemon VVM_DAEMON_CONTAINER VVM_DAEMON VVMDaemonCollector Log VVM_LOG_CONTAINER VVM_LOG VVMLogCollector Disk Group VVM_DISKGROUP_CONTAINER VVM_DISKGROUP VVMDiskgroupCollector Disk Device and Path VVM_DISKDEVICE_CONTAINER VVM_DISKDEVICE VVM_DISPATH VVMDiskdeviceCollector Volume VVM_VOLUME_CONTAINER VVM_VOLUME VVMVolumeCollector Plex VVM_PLEX VVMPlexCollector Subdisk VVM_SUBDISK VVMSubdiskCollector Replicated Volume Group VVM_RVG_CONTAINER VVM_RVG VVMRvgCollector Replication Link VVM_RLINK VVMRlinkCollector In the Debug End Time field, indicate the date and time after which debug information will no longer be logged. In the Debug Path field, indicate where the debug file will be stored (by default: <PATROL_HOME>/lib/VVM/debug on Unix systems; %PATROL_HOME%\lib\VVM\debug on Microsoft Windows systems). The debug folder must have at least 10MB of available disk space and 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 debug folder 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 least 10MB of available disk space and read, write and execute permissions for both PATROL Agent user and the VVM KM login user Select Send to Task Window to view the debug messages as they occur in the VVM KM Debug Output window. Before selecting this option, make sure the PATROL Console is connected to the PATROL Agent. Select Both (Recommended) to send the debug messages both to a file and task window. 71 Using the KM 3. Set the Debug Options:

72 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 to manually stop debugging: 1. Access the VVM KM Debug Configuration dialog 2. Select Off for the debug switch(es) you want to disable 3. Click OK. Preparing the Debug Files for Sending to Sentry Software 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 for sending 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 Windows systems If the compressed file (.tar.z or.zip) is not created successfully, you can create this manually by including all files and sub-directories under $PATROL_HOME/lib/VVM/ (on Unix) or %PATROL_HOME%\lib\VVM\ (on MS Windows). Using the KM 72

73 Generating Reports Following 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 in the associated file instance. Diskgroups => Reports => Veritas Volume Manager Topology Report - lists all Veritas Volume Manager topology objects Daemons => Reports => Daemon List Report - lists all Veritas Volume Manager daemons found <Diskgroup Instance> => Reports => Diskgroup Topology Report - lists all Veritas Volume Manager topology objects for a particular diskgroup. To save the report as a task window click Save As Task. This task window can then be printed or saved as a text file. Refreshing Parameters This section describes how to manually refresh parameters without waiting for an automatic polling cycle. 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 KM applications 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 on the PATROL Agent will then be refreshed. 73 Using the KM

74 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 refresh the PATROL Agent process cache. 2. Force a data collector to execute immediately as follows With the PATROL Console for MS Windows Right-click the Veritas Volume Manager instance and choose Parameters 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. Click Update. Using the KM 74

75 Reference Guide

76 Introduction This chapter provides statistical information about resources, operating status, and performances managed by Veritas Volume Manager KM for PATROL. It contains tables describing the parameters used in the KM, grouped by Application Classes, and provides a brief description of each parameter and its default settings. Classes and Parameters VVM_DAEMON VVM_DAEMON_CONTAINER VVM_DISKDEVICE VVM_DISKDEVICE_CONTAINER VVM_DISKGROUP VVM_DISKGROUP_CONTAINER VVM_DISKPATH VVM_LOG VVM_LOG_CONTAINER VVM_PLEX VVM_RLINK VVM_RVG VVM_RVG_CONTAINER VVM_SERVER VVM_SUBDISK VVM_VOLUME VVM_VOLUME_CONTAINER Baselines and Key Performance Indicators Some parameters are identified by default as Key Performance Indicators (KPIs) and therefore automatically 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 are respectively identified by the following icons: 76 This section lists the application classes of Veritas Volume Manager KM for PATROL. It gives you details on the icons that represent the class, Infobox, parameters and the menu commands available for each application class. There are 11 main application classes and 56 container classes.

77 Baselining KPI VVM_DAEMON Icon Name Units Default Alert Conditions BMC ProactiveNet Attribute Type VVMDaemonCPUDur ation Indicates the CPU seconds consumed by the daemon. Seconds Statistics VVMDaemonCPUUtil ization* Indicates the CPU seconds consumed by the daemon. Percentage (%) Statistics VVMDaemonMemory Indicates the core image Kilobytes (KB) Size* size of the daemon in the virtual memory. Statistics VVMDaemonProcess Count Indicates the number of Processes the processes/threads of the daemon found. Statistics VVMDaemonState Indicates the state of the daemon as reported in the command executed by the data collector. {0 = Running; 1 = Sleeping; 2 = Waiting; 3 = Queued; 4 = Intermediate; 5 = Terminated; 6 = Stopped/Disabled; 7 = Growing; 8 = xistent/not Responding; 9 = Not Running; -1 = Unknown} Availability VVMDaemonStatus Monitors the status of the daemon. This status is determined by the daemon status mapping rule defined in the KM command Configuration > Daemon(s) Status. {0 = OK ; 1 = Suspicious ; 2 = Failure} Warning = 1 Alarm = 2 Availability 77 Classes and Parameters Parameters

78 Name Units Default Alert Conditions BMC ProactiveNet Attribute Type n/a n/a If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. VVMDaemonSummar Summarizes the daemon y information as reported by commands executed by the data collector. For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. Name Name Name of the Veritas Volume Manager daemon. 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 Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Date & time when the next data collection cycle is expected to start. Start Collector Status Data collector execution status (Idle or Running). Menu Commands Classes and Parameters 78 InfoBox

79 Function Configuration > Daemon Accesses the individual configuration for monitoring the selected daemon instance. This dialog box allows the selected daemon instance to be enabled or disabled for monitoring by the VVM KM. Configuration > Daemon Status Accesses the individual configuration for determining daemon status for the selected the daemon instance. By default, the global VVMDaemonState to VVMDaemonStatus mapping rule is used, as configured at the container level. Select [default] to revert to the daemon status mapping rule configured at the global/container level. VVM_DAEMON_CONTAINER Icon Name Units Default Alert Conditions BMC Proactive Net Attribute Type VVMDaemonDet Displays all data returned to the standard n/a ails output (stdout) from commands executed by the data collector n/a VVMDaemonCol lectorexectime Collectio n Status Monitors the execution time of the daemon collector. Inactive by default, this parameter can be enabled by running the PSL command below and restarting the PATROL agent: seconds %PSL pconfig("replace", "/Runtime/VVM/ VVMDaemonCollectorExecTime", 1); Once enabled, this parameter runs every minute and triggers a warning when the collector runs for more than the observed maximum time. To overwrite the maximum time, run the PSL command below: %PSL pconfig("replace", "/Runtime/VVM/ VVMDaemonCollectorWarn", 3600); 79 Classes and Parameters Parameters

80 Name Units Default Alert Conditions BMC Proactive Net Attribute Type where 3600 must be replaced by the number of seconds required. InfoBox Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Name Classes and Parameters 80

81 Menu Commands Function Reports > Daemon List Lists all running Veritas Volume Manager daemons. Configuration > Daemons Accesses the dialog for specifying which daemons are to be monitored by the VVM KM. By default following daemons are monitored on Unix platforms. By default following daemons are monitored on Windows platforms. Type [default] to reset to the default configuration. Configuration > Accesses the global configuration for determining the daemon status for monitored Daemons Status daemon instances. By default following VVMDaemonState to VVMDaemonStatus mapping rule is used: Select [default] to reset to the default mapping rule. 81 Classes and Parameters

82 VVM_DISKDEVICE Icon Name Units Default Alert Conditions BMC ProactiveNet Attribute Type Kilobytes (KB) Statistics VVMDiskdevice Indicates the number Kilobytes per seconds (KB/s) IOKBytesRate* of KBytes transferred per second for the diskdevice. Statistics VVMDiskdevice Indicates the total Operations IOOperations number of input and output operations on the diskdevice. Statistics VVMDiskdevice Indicates the total IOOperationsF number of failed ailed input and output operations on the diskdevice on Unix platforms. Statistics VVMDiskdevice Indicates the number Operations per second IOOperationsR of input and output (Operations/s) ate operations per second for the diskdevice. Statistics VVMDiskdevice Indicates the number Requests QueueDepth of read and write requests in queue for the diskdevice on Windows platforms. Statistics VVMDiskdevice Indicates the number Kilobytes (KB) ReadKBytes of KBytes read on the diskdevice. Statistics VVMDiskdevice Indicates the number Kilobytes per seconds (KB/s) ReadKBytesRat of KBytes read per e* second for the diskdevice. Statistics VVMDiskdevice Indicates the total IOKBytes number of KBytes transferred on the diskdevice. Classes and Parameters Operations 82 Parameters

83 Units Default Alert Conditions BMC ProactiveNet Attribute Type VVMDiskdevice Indicates the number Operations ReadOperation of read operations s on the diskdevice. Statistics VVMDiskdevice Monitors the number Operations ReadOperation of failed read sfailed operations on the diskdevice on Unix platforms. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Warning when > 10 and < 100 Statistics VVMDiskdevice Monitors the read Milliseconds ReadTime* time for the diskdevice. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Warning when > 20 and < 100 Response Time VVMDiskdevice Monitors the average Milliseconds ReadTimeAvera read time for the ge* diskdevice. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Statistics VVMDiskdevice Indicates the SpaceAvailable available space on the diskdevice. Availability VVMDiskdevice Indicates the state of {0 = Online ; State the diskdevice on 1 = Online with Errors ; Unix platforms. 2 = Failing ; 3 = Failed ; 4 = Offline ; -1 = Unknown} Availability VVMDiskdevice Indicates the state of {0 = Online/Imported ; StateNT the diskdevice on 1 = Uninitialized ; Windows platforms. 2 = Online with Errors ; 3 = Failing ; 4 = Failed ; 5 = Offline ; 6 = Foreign ; 7 = Detached ; 8 = Disconnected ; -1 = Unknown} Availability Gigabytes (GB) 83 Classes and Parameters Name

84 Default Alert Conditions BMC ProactiveNet Attribute Type VVMDiskdevice Monitors the status {0 = OK ; Status of the diskdevice. 1 = Suspicious ; This status is 2 = Failure} determined by the diskdevice status mapping rule defined in the KM command Configuration > Diskdevice(s) Status. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. Warning = 1 Alarm = 2 Availability VVMDiskdevice Summarizes the n/a Summary diskdevice information as reported by commands executed by the data collector. n/a VVMDiskdevice Indicates the number Kilobytes (KB) WriteKBytes of KBytes written on the diskdevice. Note: This parameter is not available for non-dynamic diskgroups on Windows platforms. Statistics VVMDiskdevice Indicates the number Kilobytes per second (KB/s) WriteKBytesRat of KBytes written per e* second for the diskdevice. Note: This parameter is not available for non-dynamic diskgroups on Windows platforms. Statistics VVMDiskdevice Indicates the number Operations WriteOperatio of write operations ns on the diskdevice. Note: This parameter is not available for non-dynamic diskgroups on Windows platforms. Statistics Classes and Parameters Units 84 Name

85 Default Alert Conditions BMC ProactiveNet Attribute Type VVMDiskdevice Monitors the number Operations WriteOperatio of failed write nsfailed operations on the diskdevice on Unix platforms. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Warning when > 10 and < 100 Statistics VVMDiskdevice Monitors the write Milliseconds WriteTime* time for the diskdevice. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Warning when > 20 and < 100 Response Time VVMDiskdevice Monitors the average Milliseconds WriteTimeAver write time for the age* diskdevice. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Note: This parameter is not available for non-dynamic diskgroups on Windows platforms. Statistics VVMDiskpathE nabled Monitors the number Count of enabled disk paths with kernel state ENABLED. Alarm = 1 Availability VVMDiskpathN onenabled Indicates the number Count of disk paths that are not enabled. Warning when > 1 Availability and < 100 For detailed information about Baselining and Units KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. InfoBox Name Diskdevice Name of the Veritas Volume Manager diskdevice. 85 Classes and Parameters Name

86 Name 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 Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function 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 the VVM KM. Configuration > Accesses the individual configuration for determining the status for the selected Diskdevice Status diskdevice instance. By default, the global VVMDiskdeviceState[NT] to VVMDiskdeviceStatus mapping 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 > Disk Paths Accesses the global configuration dialog for configuring all monitored disk path instances. By default, all disk paths are monitored. Type [default] to reset to the default configuration. Configuration > Accesses the global configuration dialog for determining the Disk Paths Kernel status Disk Paths Kernel for monitored disk paths instances. Status By default, the global VVMDiskpathKernelState[NT] to VVMDiskpathkKernelStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule. Classes and Parameters 86 Menu Commands

87 VVM_DISKDEVICE_CONTAINER Icon Parameters. Name Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function Configuratio Accesses the dialog for specifying which diskdevices under the selected diskdevice n> container instance are to be monitored by the VVM KM. Diskdevices By default, all diskdevices are monitored. Type [default] to reset any custom configurations from current level and below and inherit custom setting, if any, or revert to default configuration. Configuratio Accesses the configuration dialog for determining the status for monitored diskdevice n> instances under the selected diskdevice container instance. Diskdevices Status 87 Classes and Parameters InfoBox

88 Function By default, the global VVMDiskdeviceState[NT] to VVMDiskdeviceStatus mapping 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. Configuratio Accesses the global configuration dialog for configuring all monitored disk path instances. n > Disk By default, all disk paths are monitored. Paths Type [default] to reset to the default configuration. Configuratio Accesses the global configuration dialog for determining the Disk Paths Kernel status for n > Disk monitored disk paths instances. Paths Kernel Status By default, the global VVMDiskpathKernelState[NT] to VVMDiskpathkKernelStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule. VVM_DISKGROUP Icon Name Units Default Alert Conditions BMC ProactiveNet Attribute Type VVMDiskgroupSpace Indicates the available Available* space for the diskgroup. Gigabytes (GB) Availability VVMDiskgroupState Indicates the state of the diskgroup on Unix platforms. {0 = Enabled; 1 = Disabled; -1 = Unknown} Availability VVMDiskgroupStateN Indicates the state of the T diskgroup on Windows platforms. {0 = Imported; 1 = Deported; 1 = Unknown} Availability VVMDiskgroupStatus Monitors the status of the diskgroup. This status is determined by the diskgroup status mapping rule defined in the KM command Configuration > Diskgroup(s) Status. {0 = OK; 1 = Suspicious; 2 = Failure} Warning = 1 Alarm = 2 Availability Classes and Parameters 88 Parameters

89 Name Units Default Alert Conditions BMC ProactiveNet Attribute Type n/a n/a If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. VVMDiskgroupSumm Summarizes the diskgroup ary information as reported by commands executed by the data collector. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. Name 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 Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function Reports > Diskgroup Topology Report Reports all Veritas Volume Manager topology objects for the selected diskgroup. Configuration > Accesses the individual configuration for monitoring the selected diskgroup instance. Diskgroup 89 Classes and Parameters InfoBox

90 This dialog allows the selected diskgroup instance to be enabled or disabled for monitoring by the VVM KM. Configuration > Accesses the individual configuration for determining diskgroup status for the selected Diskgroup diskgroup instance. Status By default, the global VVMDiskgroupState[NT] to VVMDiskgroupStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom setttings or to reset to the default status mapping rule. Configuration > Accesses the dialog for specifying which diskdevices under the selected diskgroup Disk Devices instance are 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 custom setting, if any, or revert to default configuration. Refer to the User Guide for PATROL Knowledge Module for Veritas Volume Manager by Sentry Software for more details. Configuration > Accesses the configuration dialog for determining the status for monitored diskdevice Disk Devices instances under the selected diskgroup instance. Status By default, the global VVMDiskdeviceState[NT] to VVMDiskdeviceStatus mapping 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 > Accesses the global configuration dialog for configuring all monitored disk path Disk Paths instances. By default, all disk paths are monitored. Type [default] to reset to the default configuration. Configuration > Accesses the dialog for specifying which volumes under the selected diskgroup instance Volumes 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 inherit custom setting, if any, or revert to default configuration. Configuration > Accesses the configuration dialog for determining the status for monitored volume Volumes Status instances under the selected diskgroup instance. By default, the global VVMVolumeState[NT] to VVMVolumeStatus mapping 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 > Accesses the configuration dialog for determining the kernel status for monitored Volumes Kernel volume instances under the selected diskgroup instance. Status 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 the custom settings or to reset to the default status mapping rule. Configuration > Volumes Logging Status (Unix only) Classes and Parameters Accesses the configuration dialog for determining the logging status for monitored volume instances under 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 the custom settings or to reset to the default status mapping rule. 90 Configuration > Accesses the global configuration dialog for determining the Disk Paths Kernel status Disk Paths for monitored disk paths instances. Kernel Status By default, the global VVMDiskpathKernelState[NT] to VVMDiskpathkKernelStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule.

91 Configuration > Accesses the dialog for specifying which plexes under the selected diskgroup instance Plexes are 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 inherit custom setting, if any, or revert to default configuration. Configuration > Accesses the configuration dialog for determining the status for monitored plex Plexes Status instances under the selected diskgroup instance. By default, the global VVMPlexState[NT] to VVMPlexStatus mapping 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 > Accesses the configuration dialog for determining the kernel status for monitored plex Plexes Kernel instances under the selected diskgroup instance. Status 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 inherit the custom settings or to reset to the default status mapping rule. Configuration > Accesses the dialog for specifying which subdisks under the selected diskgroup instance Subdisks 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 inherit custom setting, if any, or revert to default configuration. Configuration > Accesses the configuration dialog for determining the kernel status for monitored Subdisks Kernel subdisk instances under the selected diskgroup instance. Status By default, the global VVMSubdiskKernelState[NT] to VVMSubdiskKernelStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule. Configuration > Accesses the configuration dialog for specifying which replicated volume groups under Replicated the selected disk group instance are to be monitored by the VVM KM. By default, all Volume Groups replicated volume groups are monitored. Type [default] to reset any custom configurations from current level and below and inherit custom setting, if any, or revert to default configuration. Configuration > Replicated Volume Groups Kernel Status Accesses the global configuration for determining the replicated volume group kernel status for monitored replicated volume group instances. By default, the following VVMRvgKernelState to VVMRvgKernelStatus mapping rule is used: Configuration > Accesses the dialog for specifying which replication links under the selected disk group Replication instance are to be monitored by the VVM KM. By default, all replication links are Links monitored. Type [default] to reset any custom configurations from current level and below and inherit custom setting, if any, or revert to default configuration. 91 Classes and Parameters Configuration > Accesses the global configuration for determining the replicated volume group status Replicated for monitored replicated volume group instances.by default, the following VVMRvgState Volume Groups to VVMRvgStatus mapping rule is used: Status

92 Configuration > Accesses the global configuration for determining the replication link status for Replication monitored replication link instances. Links Status By default, the following VVMRlinkState to VVMRlinkStatus mapping rule is used: Configuration > Replication Links Kernel Status Accesses the global configuration for determining the replication link kernel status for monitored replication link instances. By default, the following VVMRlinkKernelState to VVMRlinkKernelStatus mapping rule is used: VVM_DISKGROUP_CONTAINER Icon Name Units Default Alert Conditions BMC Proactive Net Attribute Type VVMDiskdeviceColl ectorexectime Monitors the execution time of the disk device collector. Inactive by default, this parameter can be enabled by running the PSL command below and restarting the PATROL agent: seconds Warning when > preset value or observed maximum (default) Collectio n Status %PSL pconfig("replace", "/ Runtime/VVM/ VVMDiskdeviceCollectorExecTime", 1); Once enabled, this parameter runs every minute and triggers a warning when the collector runs for more than the observed maximum time. Classes and Parameters 92 Parameters

93 Name Units Default Alert Conditions BMC Proactive Net Attribute Type n/a n/a Warning when > preset value or observed maximum (default) Collectio n Status To overwrite the maximum time, run the PSL command below: %PSL pconfig("replace", "/Runtime/VVM/ VVMDiskdeviceCollectorWarn", 3600); where 3600 must be replaced by the number of seconds required. VVMDiskdeviceDeta Displays all data returned to the standard ils output (stdout) from commands executed by the data collector VVMDiskgroupColle Monitors the execution time of the disk group seconds ctorexectime collector. Inactive by default, this parameter can be enabled by running the PSL command below and restarting the PATROL agent: %PSL pconfig("replace", "/ Runtime/VVM/ VVMDiskgroupCollectorExecTime", 1); Once enabled, this parameter runs every minute and triggers a warning when the collector runs for more than the observed maximum time. To overwrite the maximum time, run the PSL command below: %PSL pconfig("replace", "/Runtime/VVM/ VVMDiskgroupCollectorWarn", 3600); VVMDiskgroupDetai Displays all data returned to the standard ls out from commands executed by the data collector. n/a n/a VVMPlexCollectorEx Monitors the execution time of the plex ectime collector. Inactive by default, this parameter can be enabled by running the PSL command below and restarting the PATROL agent: seconds Warning when > preset value or observed maximum (default) Collectio n Status %PSL pconfig("replace", "/ Runtime/VVM/ VVMPlexCollectorExecTime", 1); Once enabled, this parameter runs every minute and triggers a warning when the collector runs for more than the observed maximum time. 93 Classes and Parameters where 3600 must be replaced by the number of seconds required.

94 Name Units Default Alert Conditions BMC Proactive Net Attribute Type n/a n/a seconds Warning when > preset value or observed maximum (default) Collectio n Status To overwrite the maximum time, run the PSL command below: %PSL pconfig("replace", "/Runtime/VVM/ VVMPlexCollectorWarn", 3600); where 3600 must be replaced by the number of seconds required. VVMPlexDetails Displays all data returned to the standard output (stdout) from commands executed by the data collector VVMRlinkCollectorE Monitors the execution time of the Rlink xectime collector. Inactive by default, this parameter can be enabled by running the PSL command below and restarting the PATROL agent: %PSL pconfig("replace", "/ Runtime/VVM/ VVMRlinkCollectorExecTime", 1); Once enabled, this parameter runs every minute and triggers a warning when the collector runs for more than the observed maximum time. To overwrite the maximum time, run the PSL command below: %PSL pconfig("replace", "/Runtime/VVM/ VVMRlinkCollectorWarn", 3600); VVMRlinkDetails Displays all data returned to the standard output (stdout) from commands executed by the data collector n/a Collectio n Status VVMRvgCollectorEx ectime Monitors the execution time of the RVG collector. Inactive by default, this parameter can be enabled by running the PSL command below and restarting the PATROL agent: seconds Collectio n Status %PSL pconfig("replace", "/ Runtime/VVM/ VVMRvgCollectorExecTime", 1); Once enabled, this parameter runs every minute and triggers a warning when the collector runs for more than the observed maximum time. Classes and Parameters 94 where 3600 must be replaced by the number of seconds required

95 Name Units Default Alert Conditions BMC Proactive Net Attribute Type To overwrite the maximum time, run the PSL command below: %PSL pconfig("replace", "/Runtime/VVM/ VVMRvgCollectorWarn", 3600); where 3600 must be replaced by the number of seconds required VVMRvgDetails Displays all data returned to the standard output (stdout) from commands executed by the data collector n/a Collectio n Status VVMSubdiskCollect orexectime Monitors the execution time of the subdisk collector. Inactive by default, this parameter can be enabled by running the PSL command below and restarting the PATROL agent: seconds Warning when > preset value or observed maximum (default) Collectio n Status %PSL pconfig("replace", "/ Runtime/VVM/ VVMSubdiskCollectorExecTime", 1); Once enabled, this parameter runs every minute and triggers a warning when the collector runs for more than the observed maximum time. where 3600 must be replaced by the number of seconds required VVMSubdiskDetails Displays all data returned to the standard output (stdout) from commands executed by the data collector n/a n/a VVMVolumeCollect orexectime Monitors the execution time of the volume collector. Inactive by default, this parameter can be enabled by running the PSL command below and restarting the PATROL agent: seconds Warning when > preset value or observed maximum (default) Collectio n Status %PSL pconfig("replace", "/ Runtime/VVM/ VVMVolumeCollectorExecTime", 1); 95 Classes and Parameters To overwrite the maximum time, run the PSL command below: %PSL pconfig("replace", "/Runtime/VVM/ VVMSubdiskCollectorWarn", 3600);

96 Name Units Default Alert Conditions BMC Proactive Net Attribute Type n/a n/a Once enabled, this parameter runs every minute and triggers a warning when the collector runs for more than the observed maximum time. To overwrite the maximum time, run the PSL command below: %PSL pconfig("replace", "/Runtime/VVM/ VVMVolumeCollectorWarn", 3600); where 3600 must be replaced by the number of seconds required VVMVolumeDetails Displays all data returned to the standard output (stdout) from commands executed by the data collector InfoBox Name Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function Reports > Veritas Volume Manager Topology Report Reports all Veritas Volume Manager topology objects. Configuration > Diskgroups Accesses the global configuration dialog for specifying which diskgroups are to be monitored by the 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 monitored diskgroup instances. By default, the following VVMDiskgroupState to VVMDiskgroupStatus mapping rule is used on Unix platforms: Classes and Parameters 96 Menu Commands

97 Function By default, the following VVMDiskgroupStateNT to VVMDiskgroupStatus mapping rule is used on Windows platforms: Select [default] to reset to the default diskgroup status mapping rule. Configuration > Disk Devices Accesses the global configuration dialog for specifying which diskdevices are to be monitored by the VVM KM. By default, all diskdevices are monitored. Type [default] to reset to the default configuration. Configuration > Disk Devices Status Accesses the global configuration dialog for determining the diskdevice status for monitored diskdevice instances. By default, the following VVMDiskdeviceState to VVMDiskdeviceStatus mapping rule is used on Unix platforms: Select [default] to reset to the default diskdevice 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. Type [default] to reset to the default configuration. Configuration > Disk Paths Kernel Status Accesses the global configuration dialog for determining the Disk Paths Kernel status for monitored disk paths instances. By default, the global VVMDiskpathKernelState[NT] to VVMDiskpathkKernelStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule. Configuration > Volumes Accesses the global configuration dialog for specifying which volumes are to be monitored by the VVM KM. 97 Classes and Parameters By default, the following VVMDiskdeviceStateNT to VVMDiskdeviceStatus mapping rule is used on Windows platforms:

98 Function By default, all volumes are monitored. Type [default] to reset to the default configuration. Configuration > Volumes Status Accesses the global configuration dialog for determining the volume status for monitored volume instances. By default, the following VVMVolumeState to VVMVolumeStatus mapping rule is used on Unix platforms: By default, the following VVMVolumeStateNT to VVMVolumeStatus mapping rule is used on Windows platforms: Select [default] to reset to the default volume status mapping rule. Accesses the global configuration dialog for determining the volume kernel status for monitored volume instances. By default, the following VVMVolumeKernelState to VVMVolumeKernelStatus mapping rule is used on Unix platforms: By default, the following VVMVolumeKernelStateNT to VVMVolumeKernelStatus mapping rule is used on Windows platforms: Select [default] to reset to the default volume kernel status mapping rule. Configuration > Volumes Logging Status (UNIX only) Classes and Parameters Accesses the global configuration dialog for determining the volume logging status for monitored volume instances. By default, the following VVMVolumeLoggingState to VVMVolumeLoggingStatus mapping rule is used: 98 Configuration > Volumes Kernel Status

99 Function 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 the VVM KM. By default, all plexes are monitored. Type [default] to reset to the default configuration. Configuration > Plexes Status Accesses the global configuration dialog for determining the plex status for monitored plex instances. By default, the following VVMPlexState to VVMPlexStatus mapping rule is used on Unix platforms: By default, the following VVMPlexStateNT to VVMPlexStatus mapping rule is used on Windows platforms: Select [default] to reset to the default plex status mapping rule. Accesses the global configuration dialog for determining the plex kernel status for monitored plex instances. By default, the following VVMPlexKernelState to VVMPlexKernelStatus mapping rule is used on Unix platforms: By default, the following VVMPlexKernelStateNT to VVMPlexKernelStatus mapping rule is used on Windows platforms: Select [default] to reset to the default plex kernel status mapping rule. Configuration > Subdisks Accesses the dialog for specifying which plexes are to be monitored by the VVM KM. By default, all subdisks are monitored. Type [default] to reset to the default configuration. 99 Classes and Parameters Configuration > Plexes Kernel Status

100 Function Configuration > Subdisks Kernel Status Accesses the global configuration dialog for determining the subdisk kernel status for monitored subdisk instances. By default, the following VVMSubdiskKernelState to VVMSubdiskKernelStatus mapping rule is used on Unix platforms: By default, the following VVMSubdiskKernelStateNT to VVMSubdiskKernelStatus mapping rule is used on Windows platforms: Configuration > Replicated Volume Groups Accesses the global configuration for determining the replicated volume group status for monitored replicated volume group instances. By default, the following VVMRvgState to VVMRvgStatus mapping rule is used: Configuration > Replicated Volume Groups Kernel Status Accesses the global configuration for determining the replicated volume group status for monitored replicated volume group instances. By default, the following VVMRvgState to VVMRvgStatus mapping rule is used: Configuration > Replication Links Accesses the dialog for specifying which replication links are to be monitored by the VVM KM. By default, all replication links are monitored. Type [default] to reset to default configuration. Configuration > Replication Links Status Accesses the global configuration for determining the replication link status for monitored replication link instances. By default, the following VVMRlinkState to VVMRlinkStatus mapping rule is used: Classes and Parameters 100 Select [default] to reset to the default subdisk kernel status mapping rule.

101 Configuration > Replication Links Kernel Status Accesses the global configuration for determining the replication link kernel status for monitored replication link instances. By default, the following VVMRlinkKernelState to VVMRlinkKernelStatus mapping rule is used: Function 101 Classes and Parameters

102 VVM_DISKPATH Icon Name Units Default Alert Conditions BMC ProactiveNet Attribute Type VVMDiskpathKernelSt ate Indicates the kernel state of the diskpath on Unix platforms {0 = Enabled; 1 = Detached; 2 = Disabled; -1 = Unknown} Availability VVMDiskpathKernelSt atent Indicates the kernel state of the subdisk on Windows platforms. {0 = Enabled; 1= Unreported/ Undefined; 2 = Error; 3 = Disabled; -1 = Unknown} Availability VVMDiskpathKernelSt atus Monitors the kernel status of the disk paths. This status is determined by the subpath status mapping rule defined in the KM command Configuration > Disk Path(s) Kernel Status. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. {0 = OK; Warning = 1 1 = Suspicious; Alarm = 2 2 = Failure} Availability VVMDiskpathSummar y Summarizes the diskpath information as reported by commands executed by the data collector. n/a n/a InfoBox Name 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. Classes and Parameters 102 Parameters

103 Name 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 Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function Configuration > Disk Path Accesses the global configuration dialog for configuring all monitored disk path instances. By default, all disk paths are monitored. Type [default] to reset to the default configuration. Configuration > Disk Path Kernel Status Accesses the global configuration dialog for determining the Disk Paths Kernel status for monitored disk paths instances. By default, the global VVMDiskpathKernelState[NT] to VVMDiskpathkKernelStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule. VVM_LOG Icon 103 Classes and Parameters

104 Name Units Default Alert Conditions BMC Proactive Net Attribute Type VVMLogAlarmCo Monitors the number of alarm messages set in unt* the parameter VVMLogAlarmText. If this parameter changes to alarm state, the recovery action will trigger an event. Count Alarm when > 1 and < 100 Statistic s VVMLogAlarmTe xt Displays all alarm messages in the log file which have not been acknowledged. The filter used by the data collector to determine alarm messages can be customized using the KM command Configuration > Log(s) Filter. These alarm messages can be acknowledged automatically (default) or manually, depending on the configuration in the KM command Configuration > Log(s) Alert Acknowledgement. Manual acknowledgement is available under the KM sub-menuacknowledgement. n/a n/a VVMLogFSSpace UsedPercent* Monitors the percentage of space used by the file system (where the log file resides). If this parameter changes to warning or alarm state, the recovery action will trigger an event. Percentage (%) Warning Statistic when > 95 s and < 98 Alarm when > 98 and < 100 VVMLogSpaceAv ailable Monitors the available space for the log file to use (this is also the available space on the file system). If this parameter changes to warning or alarm state, the recovery action will trigger an event. Megabytes (MB) VVMLogSpaceGr owthrate Warning when > 2 and < 5 Alarm when > -1 and < 2 Availabi lity Displays the growth rate of the amount of space Kilobytes per used by the log file. seconds (KB/ s) Statistic s VVMLogSpaceUs ed Displays the amount of space used by the log file. Statistic s VVMLogSpaceUs edpercent* Monitors the percentage of capacity used by the Percentage (%) log file. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Note that the total capacity is the used space (VVMLogSpaceUsed) plus available space (VVMLogSpaceAvailable). Warning Statistic when > 95 s and < 98 Alarm when > 98 VVMLogSummar y Summarizes the log file information as reported by commands executed by the data collector. Classes and Parameters 104 Kilobytes (KB) n/a n/a Parameters

105 Name Units Default Alert Conditions BMC Proactive Net Attribute Type VVMLogText Displays all log text scanned by the data collector during the last collection cycle. The size of the data scanned by the data collector is configured in the KM command Configuration > Log(s) Scan Limit. n/a n/a VVMLogWarning Monitors the number warning messages set in Count* the parameter VVMLogWarningText. If this parameter changes to a warning state, the recovery action will trigger an event. Count Warning when > 1 Statistic s VVMLogWarning Displays all warning messages in the log file Text which have not been acknowledged. The filter used by the data collector to determine warning messages can be customized using the KM command Configuration > Log(s) Filter. These warning messages can be acknowledged automatically (default) or manually, depending on the configuration in the KM command Configuration > Log(s) Alert Acknowledgement. Manual acknowledgement is available under the KM sub-menu Acknowledgement. n/a n/a For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. Name Name Name of the Veritas Volume Manager log file. of the Veritas Volume Manager log file. Path Full file path of the log file. Log File Modification Time Date & time when the log file was last modified. Log File Size File size of the log file. Total FS Space Total space used by the file system. Available FS Space Space available for use by the file system. FS Percent Used Percentage of the total file system space used. Last Purge Date & time when the log file was last purged. 105 InfoBox Classes and Parameters

106 Name Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function Acknowledgemen Allows acknowledgement of warning messages detected on the selected log file t > Warnings instance. This dialog allows selective acknowledgement of "suspicious" error messages detected in the log file and sent to the text parameter VVMLogWarningText. Acknowledgemen Allows acknowledgement of alarm messages detected on the selected log file instance. t > Alarms This dialog allows selective acknowledgement of "failure" error messages detected in the log file and sent to the text parameter 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 Alert Acknowledgemen t Accesses the individual configuration of the method of acknowledgement for alerts on the selected log file instance. By default, the global method of log error acknowledgement is used, as configured at the container level. Refer to the User Guide for Veritas Volume Manager KM for PATROL by Sentry Software for more details. Classes and Parameters 106 Acknowledgemen Allows acknowledgement of all alarm and warning messages detected on the selected t > All log file instance. This dialog allows acknowledgement of all error messages detected in the log file and sent to the text parameter VVMLogWarningText or VVMLogAlarmText.

107 VVM_LOG_CONTAINER Icon Parameters Name VVMLogColle Monitors the execution time of the log collector. ctorexectime Inactive by default, this parameter can be enabled by running the PSL command below and restarting the PATROL agent: Units Default Alert Conditions BMC Proactive Net Attribute Type Seconds Warning > preset value or observed maximum (default) Collectio n Status n/a n/a %PSL pconfig("replace", "/Runtime/VVM/ VVMLogCollectorExecTime", 1); Once enabled, this parameter runs every minute and triggers a warning when the collector runs for more than the observed maximum time. To overwrite the maximum time, run the PSL command below: %PSL pconfig("replace", "/Runtime/VVM/ VVMLogCollectorWarn", 3600); VVMLogDetai ls Displays all data returned to the standard output (stdout) from commands executed by the data collector InfoBox Name Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. 107 Classes and Parameters where 3600 must be replaced by the number of seconds required.

108 Name Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function 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 Volume Manager installation directory (for example /opt/vrtsvxvm on HP-UX), unless the path is fully qualified as for the system log on Solaris and HP-UX. Configuration > Logs Filter Classes and Parameters Accesses the global configuration of the filter for expressions used for detecting error messages in the monitored log file instances. By default, the following "Included" expressions are looked for in each log file. If detected, the message containing the expression is added to the appropriate text parameter, unless the message also contains an "Excluded" expression for the same filter. 108 Type [default] to reset to the default configuration.

109 Function Type [default] to reset to the default configuration. 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 during each data collection cycle. Configuration > Logs Alert Acknowledgeme nt Accesses the global configuration of the method of acknowledgement for alerts on monitored log file instances. By default, the log collector automatically acknowledges previous log alerts (warnings and alarms) when it detects new errors. VVM_PLEX Icon Name Units Default Alert Conditions BMC ProactiveNet Attribute Type VVMPlexIOKBytes Indicates the total number of KBytes transferred on the plex. Kilobytes (KB) Statistics VVMPlexIOKBytesRate* Indicates the number of KBytes transferred per second for the plex on Unix platforms. Kilobytes per second (KB/s) Statistics VVMPlexIOOperations Indicates the total number of input and output operations on the plex on Unix platforms. Operations Statistics VVMPlexIOOperationsFai led Indicates the total number of failed input and output operations on the plex on Unix platforms. Operations Statistics Operations per second (Operations/ second) Statistics VVMPlexIOOperationsRat Indicates the number of e input and output operations per second for the plex on Unix platforms. 109 Classes and Parameters Parameters

110 Units Default Alert Conditions BMC ProactiveNet Attribute Type VVMPlexKernelState Indicates the kernel state of the plex on Unix platforms. {0 = Enabled ; 1 = Detached ; 2 = Disabled ; -1 = Unknown} Availability VVMPlexKernelStateNT Indicates the kernel state of the plex on Windows platforms. {0 = Enabled ; 1 = Unreported/ Undefined ; 2 = Error ; 3 = Disabled ; -1 = Unknown} Availability VVMPlexKernelStatus Monitors the kernel {0 = OK ; status of the plex. This 1 = Suspicious ; status is determined by 2 = Failure} the plex status mapping rule defined in the KM command Configuration > Plex(s) Kernel Status. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. Warning = 1 Alarm = 2 Availability VVMPlexReadKBytes Indicates the number of KBytes read on the plex on Unix platforms. Kilobytes (KB) Statistics VVMPlexReadKBytesRate* Indicates the number of KBytes read per second for the plex on Unix platforms. Kilobytes per second (KB/s) Statistics VVMPlexReadOperations Indicates the number of read operations on the plex on Unix platforms. Operations Statistics VVMPlexReadOperations Failed Monitors the number of failed read operations on the plex on Unix platforms. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Operations Warning when > 10 Statistics VVMPlexReadTime* Monitors the read time for the plex on Unix platforms. Milliseconds Warning when > 20 Response Time Classes and Parameters 110 Name

111 Name Units Default Alert Conditions BMC ProactiveNet Attribute Type VVMPlexReadTimeAverag e* Monitors the average Milliseconds read time for the plex on Unix platforms. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Statistics VVMPlexState Displays the state of the {0 = Active; plex on Unix platforms. 1 = Clean; 2 = Empty; 3 = Log Plex; 4 = Temporary Plex; 5 = Snapshot Plex; 6 = No Disk/Device; 7 = Recover; 8 = Removed; 9= Stale; 10= Offline; 11 = I/O Failure; -1 = Unknown} Availability VVMPlexStateNT Displays the state of the {0 = Active/Attached; plex on Windows 1 = Recoverable; platforms. 2 = Failed; -1 = Unknown} Availability VVMPlexStatus Monitors the status of {0 = OK; the plex. This status is 1 = Suspicious; determined by the plex 2 = Failure} status mapping rule defined in the KM command Configuration > Plex(s) Status. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. Warning = 1 Alarm = 2 Availability VVMPlexSummary Summarizes the plex information as reported by commands executed by the data collector. n/a n/a 111 Classes and Parameters If this parameter changes to warning or alarm state, the recovery action will trigger an event.

112 Name Units Default Alert Conditions BMC ProactiveNet Attribute Type VVMPlexWriteKBytes Indicates the number of KBytes written on the plex on Unix platforms. Kilobytes (KB) Statistics VVMPlexWriteKBytesRate Indicates the number of * KBytes written per second for the plex on Unix platforms. Kilobytes per second (KB/s) Statistics VVMPlexWriteOperations Indicates the number of write operations on the plex on Unix platforms. Operations Statistics VVMPlexWriteOperations Monitors the number of Failed failed write operations on the plex on Unix platforms. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Operations Warning = 10- Statistics 100 Alarm if out of [0 to 100] range. VVMPlexWriteTime* Monitors the write time for the plex on Unix platforms. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Milliseconds Warning = 20- Response 100 Time Alarm if out of [0 to 100] range. VVMPlexWriteTimeAverag Monitors the average e* write time for the plex on Unix platforms. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Milliseconds Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. InfoBox Name Plex Name of the Veritas Volume Manager plex. Status Status of the Veritas Volume Manager plex. Classes and Parameters 112 For detailed information about Statistics

113 Name 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. Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function 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 > Plex Accesses the configuration dialog for determining the kernel status for the selected Kernel Status plex 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 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 plex instance 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 inherit custom setting, if any, or revert to default configuration. Configuration > Subdisks Kernel Status Accesses the configuration dialog for determining the kernel status for monitored subdisk instances under the selected plex instance. By default, the global VVMSubdiskKernelState[NT] to VVMSubdiskKernelStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule. 113 Classes and Parameters Configuration > Plex Accesses the individual configuration for determining the status for the selected Status plex instance. By default, the global VVMPlexState[NT] to VVMPlexStatus mapping 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.

114 VVM_RLINK Icon Parameters Units Default Alert Conditions BMC Proactive Net Attribute Type VVMRlinkKernelStat Set by VVMRlinkCollector. Displays the e kernel state of the replication link. {0 = Connect; 1 = Enabled; 2 = DCM Logging; 3 = Recover; 4 = Detached; -1 = Unknown} VVMRlinkKernelStat Set by VVMRlinkCollector. Displays the us kernel status of the replication link. {0 = OK; 1= Suspicious; 2 = Failure} Warning = Availabil 1 ity Alarm = 2 VVMRlinkRemainin gupdatescount Set by VVMRlinkCollector. Displays the number of updates the primary RVG is ahead of the secondary RVG. Updates Statistic s VVMRlinkRemainin gupdateslag Set by VVMRlinkCollector. Displays the Seconds amount of time the secondary RVG is lagging. Statistic s VVMRlinkRemainin gupdatespercent* Set by VVMRlinkCollector. Displays the percentage of the SRL yet to be replicated to the secondary replicated volume group. The parameter is collected only on the primary node and will be left offline (greyed-out) on secondary nodes. Percentage (%) Warning when > 80 and < 90 Alarm when > 90 Statistic s VVMRlinkRemainin gupdatessize* Set by VVMRlinkCollector. Displays the size of the SRL in KBytes. Kilobytes (KBytes) Statistic s Classes and Parameters 114 Availabil ity Name

115 Name Units VVMRlinkState Set by VVMRlinkCollector. Displays the state of the replication link. {0 = Active; 1 = Unassoc; 2 = Stale; 3 = Pausing; 4= Resuming; 5 = Restoring; 6 =Pause; 7 = Fail; -1 = Unknown} Availabil ity VVMRlinkStatus Set by VVMRlinkCollector. Displays the status of the replication link. {0 = OK; 1= Suspicious; 2 = Failure} Availabil ity VVMRlinkSummary Summarizes the Rlink information as reported by commands executed by the data collector. n/a For detailed information about Baselining and Default Alert Conditions BMC Proactive Net Attribute Type n/a KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. Name Rlink Name of the Veritas Volume Manager Replication Link. Type Type of the Replicated Volume Group (Primary/Secondary). Status Status of the Replication Link. RVG Name of the RVG the Replication Link belongs to. Group Name of the disk group name the Replication Link belongs to. Kernel State Kernel state of the Replication Link. Synchronous Synchronous settings for the Replication Link. Latency Protection Latency Protection for the Replication Link. SRL Overflow Protection SRL overflow protection for the Replication Link. Local Host Name of the local host. Remote Host Name of the remote host. 115 InfoBox Classes and Parameters

116 Name Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time when the last data collection cycle completed. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function Configuration > Replication Links Accesses the individual configuration for monitoring the selected Replication Link instance. This dialog box allows the selected RLink instance to be enabled or disabled for monitoring by the VVM KM. Configuration > Replication Link Status Accesses the individual configuration for determining the status for the selected Replication Link instance. By default, the global VVMRlinkState to VVMRlinkStatus mapping 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 > Replication Link Kernel Status Accesses the individual configuration for determining the kernel status for the selected Replication Link instance. By default, the global VVMRlinkKernelState to VVMRlinkKernelStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule. VVM_RVG Parameters Name VVMRvgKernelState Set by VVMRvgCollector. Displays the kernel state of the replicated volume group. Classes and Parameters 116 Units Default Alert Conditions BMC Proactive Net Attribute Type {0 = Enabled; 1 = Recover; 2 = Disabled; -1 = Availabil ity Icon

117 Name Units Default Alert Conditions BMC Proactive Net Attribute Type Unknown} VVMRvgKernelStatu Set by VVMRvgCollector. Displays the kernel s status of the replicated volume group. {0 = OK; 1= Suspicious; 2 = Failure} Warning = Availabil 1 ity Alarm = 2 VVMRvgRlinkCount * Set by VVMRvgCollector. Displays the number rlinks of replication links in the replicated volume group. Availabil ity VVMRvgState Set by VVMRvgCollector. Displays the state of {0 = Active; the replicated volume group. 1 = Empty; 2 = Clean; 3 = Fail; -1 = Unknown} Availabil ity VVMRvgStatus Set by VVMRvgCollector. Displays the status of the replicated volume group. {0 = OK; 1= Suspicious; 2 = Failure} Warning = Availabil 1 ity Alarm = 2 VVMRvgSummary Summarizes the replicated volume group information as reported by commands executed by the data collector. n/a Availabil ity VVMRvgVolumeCou nt* Set by VVMRvgCollector. Displays the number volumes of replicated data volumes. Availabil ity For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. Name RVG Name of the Veritas Volume Manager Replicated Volume Group. Type Type of the Replicated Volume Group (Primary/Secondary). Status Status of the Replicated Volume Group. Group Name of the disk group the Replicated Volume Group belongs to. Kernel State Kernel state of the Replicated Volume Group. Data Volumes Names of the data volumes in the Replicated Volume Group. SRL Name of the Storage Replicator Log. 117 InfoBox Classes and Parameters

118 Name Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time when the last data collection cycle completed. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function Configuration > Replicated Volume Group Accesses the individual configuration for monitoring the selected Replication Volume Group instance. Configuration > Replicated Volume Group Status Accesses the individual configuration for determining the status for the selected RVG instance. By default, the global VVMRvgState to VVMRvgStatus mapping 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 > Replicated Volume Group Kernel Status Accesses the individual configuration for determining the kernel status for the selected RVG instance. By default, the global VVMRvgKernelState to VVMRvgKernelStatus mapping 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 > Replication Links Sets which replication links of the selected RVG are to be monitored by the VVM KM. By default, all replication links are monitored. Configuration > Replication Links Status Accesses the individual configuration for determining the replication links status for the selected RVG instance. By default, the global VVMRlinkState to VVMRlinkStatus mapping 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 > Replication Links Kernel Status Accesses the individual configuration for determining the replication links kernel status for the selected RVG instance. By default, the global VVMRlinkKernelState to VVMRlinkKernelStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule. VVM_RVG_CONTAINER Icon Classes and Parameters 118 Menu Commands

119 Parameters InfoBox Name Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function Configuration > Replicated Volume Groups Accesses the dialog for specifying which replicated volume groups under the selected replicated volume container instance are to be monitored by the VVM KM. By default, all replicated volume groups are monitored. Type [default] to reset any custom configurations from current level and below and inherit custom setting, if any, or revert to default configuration. Configuration > Replicated Volume Groups Status Accesses the global configuration for determining the replicated volume group status for monitored replicated volume group instances. By default, the following VVMRvgState to VVMRvgStatus mapping rule is used: Configuration > Replicated Volume Groups Kernel Status Accesses the global configuration for determining the replicated volume group kernel status for monitored replicated volume group instances. By default, the following VVMRvgKernelState to VVMRvgKernelStatus mapping rule is used: Configuration > Replication Links Accesses the dialog for specifying which replication links under the selected replicated volume instance are to be monitored by the VVM KM. By default, all replication links are monitored. Type [default] to reset any custom configurations from current level and below and inherit custom setting, if any, or revert to default configuration. Configuration > Replication Links Status Accesses the global configuration for determining the replication link status for monitored replication link instances. By default, the following VVMRlinkState to VVMRlinkStatus mapping rule is used: 119 Classes and Parameters Menu Commands

120 Function Configuration > Replication Links Kernel Status Accesses the global configuration for determining the replication link kernel status for monitored replication link instances. By default, the following VVMRlinkKernelState to VVMRlinkKernelStatus mapping rule is used: VVM_SERVER Icon Name VVMCreateDistribution Is automatically activated during KM debugging and deactivated when the debug zip or tar file is created. Default polling interval: 1 minute. VVMDaemonCollector Collects Veritas Volume Manager daemon related information. It sets all consumer parameters in VVM_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 in VVM_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 in VVM_DISKGROUP_CONTAINER, and VVM_DISKGROUP application classes. Default polling interval: 10 minutes. Classes and Parameters 120 Collectors

121 Name VVMLogCollector Collects Veritas Volume Manager log file related information. It sets all consumer parameters in VVM_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 the VVM_PLEX application class. Default polling interval: 10 minutes. VVMRlinkCollector Collects Veritas Volume Manager replication link related information. It sets all consumer parameters in VVM_RLINK application class. Default polling interval: 10 minutes. VVMRvgCollector Collects Veritas Volume Manager replicated volume group related information. It sets all consumer parameters in VVM_RVG_CONTAINER, and VVM_RVG application classes. Default polling interval: 10 minutes. VVMSubdiskCollector Collects Veritas Volume Manager subdisk related information. It sets all consumer parameters in the VVM_SUBDISK application class. Default polling interval: 10 minutes. VVMUpdateAgent Is used by the VVM KM to set the PATROL Agent KM variables when the PATROL Console user is not authorized to update (ACL) any PATROL Agent variables. It is activated automatically when the KM fails to update the PATROL Agent. Default polling interval: 5 minutes. VVMVolumeCollector Collects Veritas Volume Manager volume related information. It sets all consumer parameters in VVM_VOLUME_CONTAINER and VVM_VOLUME application classes. Default polling interval: 10 minutes. Name Units Default Alert Conditio ns BMC ProactiveNet Attribute Type ExtraFilesList Is used for pushing VVM KM library files to the PATROL Agent during the Commit operation. n/a n/a VVMLoginStatus* Monitors the status of the VVM KM login details (username/password) for the operating system. It is set by VVM_SERVER application class discovery. {0 = OK; 1 = Suspicious; 2 = Failure} Warnin Collection g= 1 Status Alarm = Classes and Parameters Parameters

122 Name Units Default Alert Conditio ns BMC ProactiveNet Attribute Type {0 = Permanent Single-node Mode; 1 = Temporary Single-node Mode; 2 = Active Multinode Mode; 3 = Passive Multinode Mode; -1 = Unknown} Collection Status If no valid username/password is detected for the operating system, this parameter will be set to "Failure" state. If there are any suspicious command exits, this parameter will be set to "Suspicious" state. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. Indicates the VVM monitoring mode. VVMNodeStatus* Monitors error messages for the {0 = OK; Veritas Volume Manager application 1 = Suspicious; on this managed system. It is set by 2 = Failure} VVM_SERVER application class discovery. If any of the Veritas Volume Manager application daemons is not running, this parameter will be set to "Failure" state. The list of critical Veritas Volume Manager daemons can be customized using the KM command Configuration > Node Status from the Veritas Volume Manager icon. If there are any suspicious command exits due to an error, this parameter will be set to "Suspicious" state. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. Warnin Availability g= 1 Alarm = 2 * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. InfoBox Classes and Parameters 122 VVMMonitoringMo de*

123 Name Application Name Name of the application monitored by this Knowledge Module. Application Version 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. Installation Path Veritas Volume Manager software installation path. Library Path Veritas Volume Manager software library paths used by VVM KM. Monitoring Mode Monitoring mode of the Knowledge Module. Monitoring Node Node currently monitoring Veritas Volume Manager. Node Name (s) Name of the current managed system (node) as defined in Veritas Volume Manager. Operating System Operating system description as reported by PATROL Agent. Platform Operating system platform as reported by the PATROL Agent (HP, SOLARIS, RS6000, or NT). Product Name Name of the Knowledge Module. Product Release Date Release date of the Knowledge Module. Product Version Version number of the Knowledge Module. Support Web site Menu Commands Function Refresh Process Cache Forces the PATROL Agent to reload its process cache from the kernel process list. Force Discovery Forces application discovery. 123 Classes and Parameters PATROL Agent Version number of the PATROL Agent installed on the managed system. Version

124 Refresh Parameters Forces an update of the application parameter values. Reload Commands Forces a reload of commands used by VVM KM during the next full discovery cycle. By default, all new commands are reloaded automatically. KM Status Generates a summary report containing information on the managed system. About Displays information about the product and manufacturer. Configuratio n > Login Accesses the Login Configuration dialog for viewing and entering VVM KM login details for the operating system. This user account should have privileges to execute Veritas Volume Manager administration commands and can use sudo privileges on Unix PATROL Agents. This user account will be used by VVM KM pre-discoveries, discoveries, data collectors, recovery actions, and infoboxes to execute operating system commands. It will not be used by any KM commands. The password is encrypted and stored on the PATROL Agent using the BMC PATROL encryption function. Configuratio n> 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 application without any PATROL Console connection. Configuratio n> Monitoring Mode Accesses the Monitoring Mode Configuration dialog, which is used for enabling or disabling KM failover, when monitoring clustered Veritas Volume Manager environment. Configuratio n > Paths Accesses the Path Configuration dialog, which displays and sets all paths used by VVM KM. Paths are automatically discovered by the KM server discovery. They are used as environment variables for executing various Veritas Volume Manager commands. Configuratio n > Node Status Accesses the Node Status Configuration dialog for viewing and modifying the daemon names monitored for node status. 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: 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: By default, the following daemons are sought on Windows platforms: Type [default] to reset to the default configuration. Classes and Parameters 124 Function

125 Function Configuratio n > Instance Limits Accesses the Instance Limits Configuration dialog to view and modify the maximum number of VVM KM application instances allowed for each application class. Configuratio n > 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 Name Units Default Alert Conditions BMC ProactiveNet Attribute Type VVMSubdiskIOKBytes Indicates the total number of KBytes transferred on the subdisk. Kilobytes (KB) Statistics Kilobytes per second (KB/s) Statistics VVMSubdiskIOKBytesRat Indicates the number of e* KBytes transferred per second for the subdisk. VVMSubdiskIOOperatio ns Indicates the total number Operations of input and output operations on the subdisk. Statistics VVMSubdiskIOOperatio nsfailed Indicates the total number of failed input and output operations on the subdisk on Unix platforms. Operations Statistics VVMSubdiskIOOperatio nsrate Indicates the number of input and output operations per second for the subdisk. Operations per second (Operations/ second) Statistics VVMSubdiskKernelState Indicates the kernel state of the subdisk on Unix platforms. {0 = Enabled; 2 = Detached; 3 = Disabled; -1 = Unknown} Availability 125 Classes and Parameters Parameters

126 VVMSubdiskKernelState NT Default Alert Conditions BMC ProactiveNet Attribute Type Indicates the kernel state {0 = Enabled; of the subdisk on Windows 1 = Unreported/ platforms. Undefined; 2 = Error; 3 = Disabled; -1 = Unknown} Availability VVMSubdiskKernelStatu s Monitors the kernel status {0 = OK; of the subdisk. This status 1 = Suspicious; is determined by the 2 = Failure} subdisk status mapping rule defined in the KM command Configuration > Subdisk(s) Kernel Status. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. Warning = 1 Alarm = 2 Availability VVMSubdiskReadKBytes Indicates the number of KBytes read on the subdisk. Kilobytes (KB) Statistics VVMSubdiskReadKBytes Rate* Indicates the number of KBytes read per second for the subdisk. Kilobytes per second (KB/s) Statistics VVMSubdiskReadOperat Indicates the number of ions* read operations on the subdisk. Operations Statistics VVMSubdiskReadOperat Monitors the number of ionsfailed failed read operations on the subdisk on Unix platforms. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Operations Warning when Statistics > 10 VVMSubdiskReadTime* Units Monitors the read time for Milliseconds the subdisk. If this parameter changes to warning or alarm state, the recovery action will trigger an event. VVMSubdiskReadTimeAv Monitors the average read erage* time for the subdisk. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Classes and Parameters 126 Milliseconds Warning when Response > 20 Time Statistics Name

127 Units VVMSubdiskSummary Summarizes the subdisk n/a information as reported by commands executed by the data collector. Default Alert Conditions BMC ProactiveNet Attribute Type n/a VVMSubdiskWriteKBytes Indicates the number of KBytes written on the subdisk. Kilobytes (KB) Statistics VVMSubdiskWriteKBytes Indicates the number of Rate* KBytes written per second for the subdisk. Kilobytes per second (KB/s) Statistics VVMSubdiskWriteOpera tions Indicates the number of write operations on the subdisk. Operations Statistics VVMSubdiskWriteOpera tionsfailed Monitors the number of failed write operations on the subdisk on Unix platforms. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Operations Warning when Statistics > 10 VVMSubdiskWriteTime* Monitors the write time for Milliseconds the subdisk. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Warning when Response > 20 Time VVMSubdiskWriteTimeA verage* Monitors the average write Milliseconds time for the subdisk. If this parameter changes to warning or alarm state, the recovery action will trigger an event. For detailed information about Baselining and Statistics KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. 127 Classes and Parameters Name

128 InfoBox Name 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. Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function 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 the VVM KM. Configuration > Subdisk Kernel Status Accesses the configuration dialog for determining the kernel status for the selected subdisk instance. By default, the global VVMSubdiskKernelState[NT] to VVMSubdiskKernelStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule. Classes and Parameters 128 Menu Commands

129 VVM_VOLUME Icon Name Units Default Alert Conditions BMC ProactiveNet Attribute Type VVMVolumeIOKBytes Indicates the total number of KBytes transferred on the volume. Kilobytes (KB) Statistics VVMVolumeIOKBytesRate* Indicates the number of KBytes transferred per second for the volume. Kilobytes per second (KB/s) Statistics VVMVolumeIOOperations Indicates the total number of input and output operations on the volume. Operations Statistics VVMVolumeIOOperationsF ailed Indicates the total Operations number of failed input and output operations on the volume on Unix platforms. Statistics VVMVolumeIOOperationsR ate Indicates the number of input and output operations per second for the volume. Operations per second (Operations/ second) Statistics VVMVolumeKernelState Indicates the kernel state of the volume on Unix platforms. {0 = Enabled; 1 = Detached; 2 = Disabled; -1 = Unknown} Availability VVMVolumeKernelStateNT Indicates the kernel state of the volume on Windows platforms. {0 = Enabled; 1 = Unreported/ Undefined; 2 = Error; 3 = Disabled; -1 = Unknown} Availability 129 Classes and Parameters Parameters

130 Units Default Alert Conditions BMC ProactiveNet Attribute Type VVMVolumeKernelStatus Monitors the kernel status of the volume. This status is determined by the volume status mapping rule defined in the KM command Configuration > Volume (s) Kernel Status. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. {0 = OK; 1 = Suspicious; 2 = Failure} Warning = 1 Alarm = 2 Availability VVMVolumeLoggingState Indicates the logging state of the volume on Unix platforms. {0 = Enabled; 1 = Disabled; -1 = Unknown} Availability VVMVolumeLoggingStatus Monitors the logging status of the volume on Unix platforms. This status is determined by the volume status mapping rule defined in the KM command Configuration > Volume (s) Logging Status. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. {0 = OK; 1 = Suspicious; 2 = Failure} Warning = 1 Alarm = 2 Availability VVMVolumeReadKBytes Indicates the number of KBytes read on the volume. Kilobytes (KB) Statistics VVMVolumeReadKBytesRat e* Indicates the number of KBytes read per second for the volume. Kilobytes per second (KB/s) Statistics VVMVolumeReadOperation s Indicates the number of read operations on the volume. Operations Statistics VVMVolumeReadOperation sfailed Monitors the number of Operations failed read operations on the volume on Unix platforms. Warning when > 10 Statistics Classes and Parameters 130 Name

131 Name Units Default Alert Conditions BMC ProactiveNet Attribute Type VVMVolumeReadTime* Monitors the read time for the volume. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Milliseconds Warning when > 20 Response Time VVMVolumeReadTimeAvera ge* Monitors the average read time for the volume. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Milliseconds Statistics VVMVolumeState Indicates the state of the volume on Unix platforms. {0 = Active; 1 = Clean; 2 = Empty; 3 = Invalid; 4 = Replay; 5 = Synchronizing; 6 = Need Synchronization; -1 = Unknown} Availability VVMVolumeStateNT Indicates the state of the volume on Windows platforms. {0 = Active/Healthy; 1 = Stopped; 2 = Formatting; 3 = Regenerating; 4 = Synchronizing; 5 = Degraded; 6 = Failing; 7 = Missing; 8 = Failed; -1 = Unknown} Availability VVMVolumeStatus Monitors the status of the {0 = OK; volume. This status is 1 = Suspicious; determined by the volume 2 = Failure} status mapping rule defined in the KM command Configuration > Volume(s) Status. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. 131 Warning = 1 Alarm = 2 Availability Classes and Parameters If this parameter changes to warning or alarm state, the recovery action will trigger an event.

132 Units Default Alert Conditions BMC ProactiveNet Attribute Type VVMVolumeSummary Summarizes the volume information as reported by commands executed by the data collector. n/a n/a VVMVolumeWriteKBytes Indicates the number of KBytes written on the volume. Kilobytes (KB) Statistics VVMVolumeWriteKBytesRat Indicates the number of Kilobytes per e* KBytes written per second second (KB/s) for the volume. Statistics VVMVolumeWriteOperatio ns Indicates the number of write operations on the volume. Operations Statistics VVMVolumeWriteOperatio nsfailed Monitors the number of failed write operations on the volume on Unix platforms. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Operations Warning when > 10 Statistics VVMVolumeWriteTime* Monitors the write time for the volume. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Milliseconds Warning when > 20 Response Time VVMVolumeWriteTimeAver age* Monitors the average Milliseconds write time for the volume. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Statistics For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. InfoBox Name 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. Classes and Parameters 132 Name

133 Name 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. Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function Configuration > Volume Accesses the individual configuration for monitoring the selected volume instance. This dialog allows the selected volume instance to be enabled or disabled for monitoring by the VVM KM. Configuration > Volume Status Accesses the individual configuration for determining the status for the selected volume instance. By default, the global VVMVolumeState[NT] to VVMVolumeStatus mapping 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 > Volume Kernel Status Accesses the configuration dialog for determining the kernel status for the selected volume 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 the custom settings or to reset to the default status mapping rule. Configuration > Volume Logging Status (Unix only) Accesses the configuration dialog for determining the logging status for the selected volume 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 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 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 inherit custom setting, if any, or revert to default configuration. 133 Classes and Parameters Menu Commands

134 Function Configuration > Plexes Status Accesses the configuration dialog for determining the status for monitored plex instances under the selected volume instance. By default, the global VVMPlexState[NT] to VVMPlexStatus mapping 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 Kernel Status Accesses the configuration dialog for determining the kernel status for monitored plex instances 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 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 instance 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 inherit custom setting, if any, or revert to default configuration. Configuration > Subdisks Kernel Status Accesses the configuration dialog for determining the kernel status for monitored subdisk instances under the selected volume instance. By default, the global VVMSubdiskKernelState[NT] to VVMSubdiskKernelStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule. VVM_VOLUME_CONTAINER Icon InfoBox Name Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Classes and Parameters 134 Parameters

135 Menu Commands Function Configuration > Volumes Accesses the dialog for specifying which volumes under the selected volume container instance 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 inherit custom setting, if any, or revert to default configuration. Configuration > Volumes Status Accesses the configuration dialog for determining the status for monitored volume instances under the selected volume container instance. By default, the global VVMVolumeState[NT] to VVMVolumeStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule. Configuration > Volumes Kernel Status Accesses the configuration dialog for determining the kernel status for monitored volume instances under the selected volume container 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 the custom settings or to reset to the default status mapping rule. Configuration > Volumes Logging Status (UNIX only) Accesses the configuration dialog for determining the logging status for monitored volume instances under the selected volume container 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 the custom settings or to reset to the default status mapping rule. Configuration > Plexes Accesses the configuration dialog for determining the status for monitored plex Status instances under the selected volume container instance. By default, the global VVMPlexState[NT] to VVMPlexStatus mapping 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 configuration dialog for determining the kernel status for monitored Kernel Status plex instances under the selected volume container instance. By default, the global VVMPlexKernelState[NT] to VVMPlexKernelStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] 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 container instance 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 inherit custom setting, if any, or revert to default configuration. 135 Classes and Parameters Configuration > Plexes Accesses the dialog for specifying which plexes under the selected volume container instance are 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 inherit custom setting, if any, or revert to default configuration.

136 Function Configuration > Accesses the configuration dialog for determining the kernel status for monitored Subdisks Kernel Status subdisk instances under the selected volume container instance. By default, the global VVMSubdiskKernelState[NT] to VVMSubdiskKernelStatus mapping rule, or the inherited custom settings configured at a higher level, is used. Select [default] to inherit the custom settings or to reset to the default status mapping rule. Classes and Parameters 136

137 Additional Information and Support

138 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 Additional help for PATROL Knowledge Module for Veritas Volume Manager by Sentry Software can be found in the following locations: PATROL Knowledge Module for Veritas Volume Manager by Sentry Software User Guide PATROL Knowledge Module for Veritas Volume Manager by Sentry Software Release Notes Where to Find Additional Help 138

139 Requirements BMC -A Abnormalities Access 54 Executable Files 14 Files 14 Library Files 14 Paths 14 Permissions 14 Acknowledge Logs Alert Adapter 51 BMC Portal 51 BMC ProactiveNet Performance Management Portal 12 BMC Software PATROL Agent 12 BMC Software PATROL Console 12 Requirements 12 BMC PATROL Changes 12 pslinstructionmax BMC ProactiveNet Integration 51 BMC ProactiveNet Performance Management Abnormalities 54 Baselines 54 Key Performance Indicators KPI Add 52, 53 Create 52 Update 53 Agent PATROL 44 AIX 14 Application Class VVM_DAEMON 77 VVM_DAEMON_CONTAINER 79 VVM_DISKDEVICE 82 VVM_DISKDEVICE_CONTAINER 87 VVM_DISKGROUP 88 VVM_DISKGROUP_CONTAINER 92 VVM_DISKPATH 102 VVM_LOG 103 VVM_LOG_CONTAINER 107 VVM_PLEX 109 VVM_RLINK 114 VVM_RVG 116 VVM_SERVER 120 VVM_SUBDISK 125 VVM_VOLUME 129 VVM_VOLUME_CONTAINER 134 -BBaselines BMC ProactiveNet Performance Management 54 Generation 54 Manage CChanges Check 7 Instance Limits Cluster Configure 57 Clustering Application Collectors VVMCreateDistribution 120 VVMDaemonCollector 120 VVMDiskdeviceCollector 120 VVMDiskgroupCollector 120 VVMLogCollector 120 VVMPlexCollector 120 VVMRlinkCollector 120 VVMRvgCollector 120 VVMSubdiskCollector 120 VVMUpdateAgent 120 VVMVolumeCollector 120 Command Configuration 87 Disk Paths 87 Disk Paths Kernel Status Diskdevices 87 Diskdevices Status 87 Commands About 120 Acknowledgement Index 54

140 Alarms 103 All 103 Configuration 77, 79, 82, 88, 92, 102, 103, 107, 109, 114, 116, 120, 125, 129, 134 Daemon 77 Daemon List 79 Daemon Status 77 Daemons 79 Daemons Status 79 Debug 120 Disk Devices 88, 92 Disk Devices Status 88, 92 Disk Path 102 Disk Path Kernel Status 102 Disk Paths 82, 88, 92 Disk Paths Kernel Status 82, 88, 92 Diskdevice 82 Diskdevice Status 82 Diskgroup 88 Diskgroup Status 88 Diskgroup Topology Report 88 Diskgroups 92 Diskgroups Status 92 Force Discovery 120 Instance Limits 120 KM Status 120 Log 103 Log Alert Acknowledgement 103 Log Filter 103 Log Scan Limit 103 Login 120 Logs 107 Logs Alert Acknowledgement 107 Logs Filter 107 Logs Scan Limit 107 Messages List 107 Monitoring Mode 120 Node Status 120 Paths 120 Plex 109 Plex Kernel Status 109 Plex Status 109 Plexes 88, 92, 129, 134 Plexes Kernel Status 88, 92, 129, 134 Plexes Status 88, 92, 129, 134 Preloading 120 Refresh Parameters 120 Refresh Process Cache 120 Reload Commands 120 Replicated Volume Group 116 Replicated Volume Group Kernel Status 116 Replicated Volume Group Status 116 Replicated Volume Groups 88 Replicated Volume Groups Kernel Status 88 Replicated Volume Groups Status 88 Replication Link Kernel Status 114 Replication Link Status 114 Replication Links 88, 114, 116 Replication Links Kernel Status 88, 116 Replication Links Status 88, 116 Reports 79, 88, 92, 107 Subdisk 125 Subdisk Kernel Status 125 Subdisks 88, 92, 109, 129, 134 Subdisks Kernel Status 88, 92, 109, 129, 134 Veritas Volume Manager Topology Report 92 Volume 129 Volume Kernel Status 129 Volume Logging Status 129 Volume Status 129 Volumes 88, 92, 134 Volumes Kernel Status 88, 92, 134 Volumes Logging Status 88, 92, 134 Volumes Status 88, 92, 134 Warnings 103 Configure Cluster 57 Daemons 62 Disk Devices 62 Disk Groups 62 Disk Paths Kernel 62 KM User Account 44 Log Error Filter 65 Log Scan Limit 67 Logs Alert Acknowledgement Multi-Node Monitoring Mode Node Status 64 PATROL Agent 42 Plex 62 Plex Kernel 62 Status 62 Volume 62 Volume Kernel 62 Volume Logging Commands

141 Enable -D- -E- Daemons Enable Disable Enable Delete Daemons 59 Disk Devices 59 Disk Paths 59 Diskgroups 59 Logs 59 Plexes 59 Subdisks 59 Volumes 59 Disable Daemons 59 Debug 70 Disk Devices 59 Disk Paths 59 Diskgroups 59 Logs 59 Plexes 59 Subdisks 59 Volumes 59 Discoveries Force Discovery 73 Delete Disable Enable Disk Paths Delete Disable Enable Disk Space Requirements Diskgroups FFailover Group Name Files ins_all_<version>.tar 19 ins_windows_<version>.exe Setup 20 setup.exe 22 setup.sh 22 uninstall.exe 35 uninstall.sh 35 Force All Data Collectors 73 All Discoveries 73 Selected Data Collectors Baselines 54 Reports 73 -Hhelp 138 HP-UX GGenerate Verify 46 Disk Devices Delete Disable Daemons 59 Debug 70 Disk Devices 59 Disk Paths 59 Diskgroups 59 Logs 59 Plexes 59 Subdisks 59 Volumes 59 -IImprovement InfoBox 7 Application Name Delete 59 Disable 59 Enable 59 Data Collectors Force Debug 59

142 Application Version 120 Available FS Space 103 Available Space 82 Binary Path 120 Collector Last End 77, 79, 82, 87, 88, 92, 102, 103, 107, 109, 114, 116, 125, 129, 134 Collector Last Start 77, 79, 82, 87, 88, 92, 102, 103, 107, 109, 114, 116, 125, 129, 134 Collector Name 77, 79, 82, 87, 88, 92, 102, 103, 107, 109, 114, 116, 125, 129, 134 Collector Next Start 77, 79, 82, 87, 88, 92, 102, 103, 107, 109, 114, 116, 125, 129, 134 Collector Status 77, 79, 82, 87, 88, 92, 102, 103, 107, 109, 114, 116, 125, 129, 134 Command 77 Copyright 120 Data Volumes , 103 Device 82, 125 Disk 82, 102, 125 Disk Access Name 102 Diskdevice 82 Drive Letter 129 FS Percent Used 103 Group 82, 102, 109, 114, 116, 125, 129 Host Name 120 ID 88 Installation Path 120 Kernel State 102, 114, 116 KState 109, 125, 129 Last Purge 103 Latency Protection 114 Length 109, 125, 129 Library Path 120 Local Host 114 Log File Modification Time 103 Log File Size 103 Log Length 129 Logging 129 Monitoring Mode 120 Monitoring Node 120 Name 77, 88, 103 Node Name(s) 120 Offset 82 Operating System 120 Owner 77 Path 102, 103 PATROL Agent Version 120 PID 77 Platform 120 Plex 109, 125 PPID 77 Product Name 120 Product Release Date 120 Product Version 120 Remote Host 114 Rlink 114 RVG 114, 116 SRL 116 SRL Overflow Protection 114 Status 77, 82, 88, 109, 114, 116, 129 Subdisk 125 Support 120 Synchronous 114 Tag 82 Total FS Space 103 Type 82, 88, 109, 114, 116, 129 Volume 109, 125, 129 Web site 120 Install / Un-install 22, 35 BMC Software Installation Utility Log 22 Packages 19 Procedure 22 Setup Files 20 Instance Limits 19 Check 46 Integration BMC ProactiveNet 51 Integration Service Agent 52 Introduction 22 Issues Fixed 7 -KKey Performance Indicators BMC ProactiveNet Performance Management 54 Manage 54 KM Configure 44 Initial Setup 48 Load 40, 41, 51 Preload 42 Preloaded 43, InfoBox

143 KM Unix 19, 35 Windows 19, 22, 35 Options Prepare to Load 41 Unload 42, 43, 44 User Account 44 KPI BMC ProactiveNet Performance Management 54 Manage 54 -L- -P- 14 Parameter KM 40, 41, 51 PATROL Central Prepare 41 Log Error Filter NBULoginStatus Parameters 41 ExtraFilesList 120 Refresh 73 VVMDaemonCPUDuration 77 VVMDaemonCPUUtilization 77 VVMDaemonDetails 79 VVMDaemonMemorySize 77 VVMDaemonProcessCount 77 VVMDaemonState 77 VVMDaemonStatus 77 VVMDaemonSummary 77 VVMDiskdeviceDetails 92 VVMDiskdeviceIOKBytes 82 VVMDiskdeviceIOKBytesRate 82 VVMDiskdeviceIOOperations 82 VVMDiskdeviceIOOperationsFailed 82 VVMDiskdeviceIOOperationsRate 82 VVMDiskdeviceQueueDepth 82 VVMDiskdeviceReadKBytes 82 VVMDiskdeviceReadKBytesRate 82 VVMDiskdeviceReadOperations 82 VVMDiskdeviceReadOperationsFailed 82 VVMDiskdeviceReadTime 82 VVMDiskdeviceReadTimeAverage 82 VVMDiskdeviceSpaceAvailable 82 VVMDiskdeviceState 82 VVMDiskdeviceStateNT 82 VVMDiskdeviceStatus 82 VVMDiskdeviceSummary 82 VVMDiskdeviceWriteKBytes 82 VVMDiskdeviceWriteKBytesRate 82 VVMDiskdeviceWriteOperations 82 VVMDiskdeviceWriteOperationsFailed 82 VVMDiskdeviceWriteTime 82 Configure 65 Log Scan Limit Configure Logs Delete Disable Enable Logs Alert Acknowledge 68 -MManage Baselines 54 Key Performance Indicators KPI 54 Monitor Type 52 Multi-Node Monitoring Mode Configure NNew features Node Status Configure OOperating Systems Linux 44 19, 22, Linux Load Common services 22 Console Systems role 22 Managed System 22 View Log 22 Oracle Solaris Cluster 57 Overview 10

144 VVMPlexWriteKBytesRate 109 VVMPlexWriteOperations 109 VVMPlexWriteOperationsFailed 109 VVMPlexWriteTime 109 VVMPlexWriteTimeAverage 109 VVMRlinkKernelState 114 VVMRlinkKernelStatus 114 VVMRlinkRemainingUpdatesCount 114 VVMRlinkRemainingUpdatesLag 114 VVMRlinkRemainingUpdatesPercent 114 VVMRlinkRemainingUpdatesSize 114 VVMRlinkState 114 VVMRlinkStatus 114 VVMRlinkSummary 114 VVMRvgKernelState 116 VVMRvgKernelStatus 116 VVMRvgRlinkCount 116 VVMRvgState 116 VVMRvgStatus 116 VVMRvgSummary 116 VVMRvgVolumeCount 116 VVMSubdiskDetails 92 VVMSubdiskIOKBytes 125 VVMSubdiskIOKBytesRate 125 VVMSubdiskIOOperations 125 VVMSubdiskIOOperationsFailed 125 VVMSubdiskIOOperationsRate 125 VVMSubdiskKernelState 125 VVMSubdiskKernelStateNT 125 VVMSubdiskKernelStatus 125 VVMSubdiskReadKBytes 125 VVMSubdiskReadKBytesRate 125 VVMSubdiskReadOperations 125 VVMSubdiskReadOperationsFailed 125 VVMSubdiskReadTime 125 VVMSubdiskReadTimeAverage 125 VVMSubdiskSummary 125 VVMSubdiskWriteKBytes 125 VVMSubdiskWriteKBytesRate 125 VVMSubdiskWriteOperations 125 VVMSubdiskWriteOperationsFailed 125 VVMSubdiskWriteTime 125 VVMSubdiskWriteTimeAverage 125 VVMVolumeDetails 92 VVMVolumeIOKBytes 129 VVMVolumeIOKBytesRate 129 VVMVolumeIOOperations 129 VVMVolumeIOOperationsFailed 129 VVMVolumeIOOperationsRate 129 VVMDiskdeviceWriteTimeAverage 82 VVMDiskgroupDetails 92 VVMDiskgroupSpaceAvailable 88 VVMDiskgroupState 88 VVMDiskgroupStateNT 88 VVMDiskgroupStatus 88 VVMDiskgroupSummary 88 VVMDiskpathEnabled 82 VVMDiskpathKernelState 102 VVMDiskpathKernelStateNT 102 VVMDiskpathKernelStatus 102 VVMDiskpathNonEnabled 82 VVMDiskpathSummary 102 VVMLogAlarmCount 103 VVMLogAlarmText 103 VVMLogDetails 107 VVMLogFSSpaceUsedPercent 103 VVMLoginStatus 120 VVMLogSpaceAvailable 103 VVMLogSpaceGrowthRate 103 VVMLogSpaceUsed 103 VVMLogSpaceUsedPercent 103 VVMLogSummary 103 VVMLogText 103 VVMLogWarningCount 103 VVMLogWarningText 103 VVMMonitoringMode 120 VVMNodeStatus 120 VVMPlexDetails 92 VVMPlexIOKBytes 109 VVMPlexIOKBytesRate 109 VVMPlexIOOperations 109 VVMPlexIOOperationsFailed 109 VVMPlexIOOperationsRate 109 VVMPlexKernelState 109 VVMPlexKernelStateNT 109 VVMPlexKernelStatus 109 VVMPlexReadKBytes 109 VVMPlexReadKBytesRate 109 VVMPlexReadOperations 109 VVMPlexReadOperationsFailed 109 VVMPlexReadTime 109 VVMPlexReadTimeAverage 109 VVMPlexState 109 VVMPlexStateNT 109 VVMPlexStatus 109 VVMPlexSummary 109 VVMPlexWriteKBytes Parameters

145 VVMVolumeKernelState 129 VVMVolumeKernelStateNT 129 VVMVolumeKernelStatus 129 VVMVolumeLoggingState 129 VVMVolumeLoggingStatus 129 VVMVolumeReadKBytes 129 VVMVolumeReadKBytesRate 129 VVMVolumeReadOperations 129 VVMVolumeReadOperationsFailed 129 VVMVolumeReadTime 129 VVMVolumeReadTimeAverage 129 VVMVolumeState 129 VVMVolumeStateNT 129 VVMVolumeStatus 129 VVMVolumeSummary 129 VVMVolumeWriteKBytes 129 VVMVolumeWriteKBytesRate 129 VVMVolumeWriteOperations 129 VVMVolumeWriteOperationsFailed 129 VVMVolumeWriteTime 129 VVMVolumeWriteTimeAverage 129 PATROL Agent 44 PATROL Agent 42, 43 PATROL Agent system 18 PATROL Central Console 42, 44 PATROL Central Console Server system 18 PATROL Central Web Server system 18 PATROL Console 42, 43 PATROL Console system 18 PATROL Agent Configure 42 Restart 48 PATROL Console 41 Restart Permissions 48 Access Platform 14 Upgrade Platforms Unix Plexes Delete Disable Enable Preload KM 43, 44 ProactiveNet 52 PW Commands 53 -RRefresh Parameters 73 Release Notes 7 remote PATROL Agent Checking Reports Generate Requirements Additional 12 BMC ProactiveNet Performance Management Portal 12 BMC Software PATROL Agent 12 BMC Software PATROL Console 12 Disk Space 18 Security 14 Software 12 Symantec NetBackup 12 System 12 Restart PATROL Agent 48 PATROL Console 48 -SSecurity Requirements Setup 14 Check 48 Initial 48 KM 48 Solaris 14 Status Configure Subdisks Delete Disable Enable Sudo 44 User System HP-UX 12 IBM AIX 12 Microsoft Windows KM 42 Preloaded Parameters

146 System VVM_PLEX Oracle Solaris Red Hat Linux Requirements Application Class VVM_RLINK 109 Application Class VVM_RVG 114 -T - Application Class VVM_SERVER 116 Thresholds Application Class VVM_SUBDISK 120 Application Class VVM_VOLUME 125 Customize 53 Import 53 Application Class 129 VVM_VOLUME_CONTAINER -U- Application Class Unix 44 Unload -W - KM 42, 43, 44 Upgrade Platform 134 What's new V Verify Application Discovery 46 Veritas Cluster File System 57 Veritas Cluster Server 57 Volumes Delete 59 Disable 59 Enable 59 VVM_DAEMON Application Class 77 VVM_DAEMON_CONTAINER 79 Application Class VVM_DISKDEVICE Application Class 82 VVM_DISKDEVICE_CONTAINER Application Class VVM_DISKGROUP 87 Application Class 88 VVM_DISKGROUP_CONTAINER Application Class VVM_DISKPATH 92 Application Class VVM_LOG 102 Application Class 103 VVM_LOG_CONTAINER Application Class

147 ABOUT MARKETZONE DIRECT PRODUCTS The BMC MarketZone Direct program sells and supports third-party products that complement and/or augment BMC solutions. MarketZone Direct products are available under BMC license and support terms. BUSINESS RUNS ON I.T. I.T. RUNS ON BMC SOFT WARE About Sentry Software Sentry Software, a strategic Technology Alliance Partner of BMC Software, provides comprehensive multi-platform monitoring solutions that enable management of the hardware and software aspects of all servers and SANs and covering up to 100 % of custom applications within the BMC ProactiveNet Performance Management environment. Sentry Software also develops adapters for BMC Atrium Orchestrator that enables IT administrators to automate the execution of common requests and tasks that occur in the daily course of IT operations. Combined with BMC s servers and network automation tools, the adapters allow IT administrators to implement provisioning and decommissioning workflows that cover all layers of their IT infrastructure. Finally, Sentry Software designs connectors that bring storage capacity metrics into BMC TrueSight Capacity Optimization to ensure IT administrators that their storage infrastructure is properly sized for their current and future needs. Bus ines s t hrives when IT runs s ma rt er, fa s t er a nd s t ronger. Tha t s why t he mos t dema nding IT orga niza t ions in t he world rely on BMC Soft wa re a cros s dis t ribut ed, ma infra me, virt ua l a nd cloud environment s. Recognized a s t he lea der in Bus ines s Service Ma na gement, BMC offers a comprehens ive a pproa ch a nd unified pla t form t ha t helps IT orga niza t ions cut cos t, reduce ris k a nd drive bus ines s profit. For t he four fis ca l qua rt ers ended Sept ember 30,2011, BMC revenue wa s a pproxima t ely $2.2 billion. About BMC Software BMC Software helps leading companies around the world put technology at the forefront of business transformation, improving the delivery and consumption of digital services. From mainframe to cloud to mobile, BMC delivers innovative IT management solutions that have enabled more than 20,000 customers to leverage complex technology into extraordinary business performance increasing their agility and exceeding anything they previously thought possible. For more information about BMC Software, visit LEARN MORE To learn more about our solutions, please visit : Like us on Facebook: facebook.com/sentrysoftware Follow us on Twitter: twitter.com/sentrysoftware BMC Software, Inc. All rights reserved.