Veritas Volume Manager KM for PATROL

Transcription

1 USER DOCUMENTATION HIGH AVAILABILITY MONITORING Veritas Volume Manager KM for PATROL Version January 2018

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 2015 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 Table of Contents...11 Requirements...11 System Requirements...11 Software Requirements...13 Security Requirements...17 Disk Space Requirements...17 Remote Monitoring Requirements...19 Getting the BMC Software Installation Utility...20 Getting the Installation Packages...21 Extracting the Setup Files...24 Installing Veritas Volume Manager KM for PATROL...35 Uninstalling Veritas Volume Manager KM for PATROL...42 Loading the KM...42 Loading the KM on PATROL Console...43 Loading the KM on PATROL Central...43 Configuring PATROL Agent to Preload the KM...43 Unloading the KM...44 Unloading the KM from the PATROL Agent...44 Unloading the KM from the PATROL Console...45 Unloading the KM from the PATROL Central Console...50 Configuring VxVM Nodes Monitoring...61 Verifying Application Discovery...62 Verifying the Instance Limits...64 Verifying the Initial Setup of the KM...64 Restarting PATROL Agent and PATROL Console...66 Integrating with BMC Portal...66 Integrating with BMC TrueSight OM...68 Configuring the KM...68 Configuring Paths...68 Configuring the Multi-Node Monitoring Mode...71 Filtering Elements to Monitor...73 Forcing the Classic Mode Configuring the KM User Account

4 ...75 Configuring the Element Status...77 Configuring the Node Status...78 Configuring the Log Filter...80 Configuring the Log Scan Limit...81 Configuring Logs Alert Acknowledgment...83 Using the KM...83 Acknowledging Alerts...84 Enabling the Debug Mode...86 Generating Reports...87 Refreshing Parameters...90 Classes and Parameters...91 VVM_MAIN...92 VVM_DAEMON...94 VVM_DAEMON_CONTAINER...97 VVM_DISKDEVICE VVM_DISKDEVICE_CONTAINER VVM_DISKGROUP VVM_DISKGROUP_CONTAINER VVM_DISKPATH VVM_LOG VVM_LOG_CONTAINER VVM_PLEX VVM_RLINK VVM_RVG VVM_SERVER VVM_SUBDISK VVM_VOLUME VVM_VOLUME_CONTAINER Managing Baselines and Key Performance Indicators Where to Find Additional Help VVM_RVG_CONTAINER

5 Release Notes for v3.0.00

6 Important Information The BMC patch : Patch 1 for BMC PATROL Agent must be installed to use any version of Veritas Volume Manager KM for PATROL. Version i of the PATROL Agent on Windows prevents VVM KM from operating properly. While apparently successfully loaded, VVM KM fails to start and can neither monitor the local system or the remote systems. What's New VVM-258: Support for Veritas InfoScale v7.x and higher. VVM-271: Remote monitoring for all supported Veritas Volume Manager systems. Changes and Improvements VVM-241: VVM KM has been improved to support all PATROL Agent v10+ versions and prevent failures due to a compatibility error. VVM-271: The monitoring of Windows Event Logs has been improved. VVM-337: The path discovery has been improved in order to support variations to binary and library paths. VVM-223: Handling large values in stats parameters: When the cumulative I/O stats returned by Veritas Volume Manager commands became too large (more than 231), the related parameters failed and stopped collecting data. Thus, metrics for rate-based parameters such as ReadKBytesRate, WriteKBytesRate, IOKBytesRate were not properly reported for volumes, plexes, disks devices and subdisks. The product now stores the actual read, write or total I/O collected since the last collection cycle to avoid values reported by these parameters to grow cumulatively and to reach their limitation. VVM-231: Commands were not properly reloaded when using the Reload Commands KM menu, which resulted in an error to be displayed in the System Output Window. VVM-330: VVM KM experienced a discovery failure due to a missing VxVM library path. Known Issues VVM-291: On BMC Portal v2.9, volumes (in disk groups) may not be collected by the VVM KM integration par file. Also, due to hierarchical changes implemented in Veritas Volume Manager KM for PATROL v3.0.00, migration from versions 2.x is not possible. 6 Fixed Issues

7 7

8 Overview

9 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 its critical daemons. Disks and Multi Paths: monitors the health of disk devices and dynamic multi-pathing (DMP). Logs: checks regularly for any error 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 bottleneck. 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. 9

10 Preparing for Installation

11 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, Disk Space, and Remote Monitoring Requirements Get the BMC Software Installation Utility Download the Installation Packages Extract the Setup Files Requirements System Requirements Veritas Volume Manager KM for PATROL supports the following operating systems: Operating System Operating System Version Microsoft Windows Microsoft Windows Server 2003, 2008, 2012 and all versions supported by BMC PATROL Agent 3.7 and higher. Linux All distributions supported by BMC PATROL Agent 3.7 and higher. Oracle Solaris 8, 9, 10, and all versions supported by BMC PATROL Agent 3.7 and higher. HP-UX 11x, and all versions supported by BMC PATROL Agent 3.7 and higher. IBM AIX 5.x, 6.x, and all versions supported by BMC PATROL Agent 3.7 and higher. Software Requirements Software Requirements Veritas Volume Manager KM for PATROL supports: Software Version Veritas Volume Manager (included in InfoScale Foundation Suites) 5.0, 5.1, 6.x, 7.x BMC Software PATROL Agent Any version BMC Software PATROL Console Any version 11 If the operating system is upgraded (or downgraded) at a later date, you will need to reload commands for the VVM KM.

12 BMC Portal v2.3 and higher BMC ProactiveNet Performance Manager v9.5 and higher BMC TrueSight Operations Management v10.x and higher 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. 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 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. 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. 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. Requirements 12 Changes Required

13 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 (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 Reference 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 Security Requirements A user account with administrative privileges must be configured in BMC PATROL to read and execute Veritas Volume Manager application programs and access file systems. Depending on the operating systems used, several options will be available. On Unix platforms: 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. On Windows platforms: an administrator user a non-administrator account, such as patrol, configured in Veritas Volume Manager application to administer the Veritas Volume Manager application. The user login details are configured in the KM. The password is stored in the PATROL Agent in a DES encrypted format. 13 Requirements The following user accounts can be used:

14 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\Veritas Volume Manager x.x (on Microsoft Windows). Executable and Library Files accessed by VVM KM User Unix Microsoft Windows INSTALL_PATH/bin INSTALL_PATH/lib /usr/sbin/* INSTALL_PATH\ 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. 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. 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(osp=="") { osp=trim(nthargf(grep("osplatform",ctl),"2-","=","="), " "); } fields=lines(ntharg(var,"1-","/")); old_host=host; host=(fields == 5)? ntharg(var,"3","/") : "localhost"; if(host!=old_host) { if((osp!="windows") && sudoers) { printf("\n\ncommands used with sudo:\n%s",sort(sudoers)); } printf("\n\non %s:\n\n", host); i=0; sudoers=""; osp=""; } Requirements 14 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.

15 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,fields,"/"),met,cmd); } } if((osp!="windows") && sudoers) { printf("\n\ncommands used with sudo:\n%s",sort(sudoers)); } printf("\n\ncommands used with sudo:\n%s",sort(sudoers)); The PATROL Agent user (normally patrol) needs read & execute permission to following paths and files: /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. On Windows platforms the Veritas Volume Manager installation is identified by checking the Microsoft Windows Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\VxSvc\ 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/). 15 Requirements The configured login user should have sufficient privileges to run regedit command on the managed node.

16 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,\ 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/* 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. Requirements 16 user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH and PATROL_HOME with the relevant paths.

17 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 The VVM KM is installed under the PATROL installation path. 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 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. Remote Monitoring Requirements Remote monitoring is not possible from a UNIX/Linux PATROL Agent system to a Windows-based VxVM server. The requirements listed below must be met to be able to use remote monitoring. JAVA VVM KM requires Java 1.8 and a Java Runtime Environment (JRE) to be installed on the same system that runs the PATROL Agent. 17 Requirements Remote monitoring is required for all servers or appliances on which no PATROL Agent can be installed. This feature is also interesting if you lack resources or time to deploy a PATROL Agent and VVM KM on several servers since it allows to monitor multiple hosts from one agent.

18 The KM will automatically detect the JRE path if it has been installed in the default location or under the BMC PATROL Agent installation path. If it has been installed in a different location, you will have to set JAVA_HOME for the Patrol Agent default account before starting the PATROL Agent. You can download the Java Runtime Environment along with the KM on the Sentry Software website. SSH/WMI Connection An SSH (UNIX/Linux platforms) or a WMI (Windows platforms) connection is required to monitor remote Veritas Volume Manager nodes. When using an SSH connection, the SSH host key authentication must be disabled on the remote host. Disabling the SSH Host Key Authentication SSH host key authentication is enabled by default on most Veritas Volume Manager nodes. To disable it: 1. Open the global SSH configuration file (ssh_config) stored in the /etc/ssh/ directory on the remote host 2. Add the line StrictHostKeyChecking no 3. Save the file. Requirements 18

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

20 Getting the Installation Packages The Veritas Volume Manager KM for PATROL packages are available on the Sentry Software Web site. There are two packages, each of which can be used to install the KM on every PATROL component (Agent, Console, etc.) according to the platform you are using. Downloading from Sentry Software Web site veritas-volume-manager-<version>-thorium.zip veritas-volume-manager-<version>-thorium.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. Getting the BMC Software Installation Utility 20

21 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 For remote monitoring, there is no need to install the PATROL Agent and Knowledge Module on the remote Veritas Volume Manager node(s). 21 Getting the Installation Packages

22 Installing the KM

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

24 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). On Windows: Launch the setup.exe program On UNIX: Launch the setup.sh script To install Veritas Volume Manager KM for PATROL 1. The welcome screen of the installer appears. Click Next to continue. Installation Wizard - Welcome 24

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

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

27 4. 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 - Selecting the Installation Directory 27 Installing Veritas Volume Manager KM for PATROL

28 5. Select Default. Installing Veritas Volume Manager KM for PATROL does not require any customization. Click Next to continue. 6. Select one or several of the following options: Managed System to install Veritas Volume Manager KM for PATROL on a PATROL Agent. Console Systems 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 - Selecting an Installation Type

29 Installation Wizard - Selecting Roles 29 Installing Veritas Volume Manager KM for PATROL

30 7. Check the Veritas Volume Manager KM for PATROL box to install the KM (it should be selected by default). Click Next to continue. Select the Java Runtime Environment program if you want to install it along with the KM (this option is only provided when you have previously downloaded the package). Click Next to continue. Installation Wizard - Selecting Products and Components Installing Veritas Volume Manager KM for PATROL 30

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

32 9. The setup program displays the actions performed and indicates the percentage of completion. Once the installation is complete, click Next to view the installation results. Installation Wizard - Installation Status Installing Veritas Volume Manager KM for PATROL 32

33 10. 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 - Installation Results 33 Installing Veritas Volume Manager KM for PATROL

34 11. Click the Finish button to complete and close the installation wizard. Installation Wizard - Completing and closing the Installation Wizard 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 Uninstalling Veritas Volume Manager KM for PATROL 40

41 Loading / Unloading the KM

42 Once installed the KM will have to be preloaded on one of the following PATROL consoles: PATROL Console PATROL Central The PATROL Agent can also be configured to automatically preload the KM. Loading the KM Before loading the VVM KM: 1. Make sure you have properly installed the KM on PATROL Console and PATROL Agent systems. 2. Start the PATROL Console and update the connection to all PATROL Agent systems where the VVM KM is installed. 3. 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. The Veritas Volume Manager instance will be created. Any previous VM KM configuration will be upgraded and their server instances will be created. 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. 42 If you want to save the new list of loaded files as the PATROL Console user preference:

43 Loading the KM on PATROL Central To load the KM on PATROL Central 1. In the Console, right-click the Managed System and select Load Knowledge Modules... The 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. The Veritas Volume Manager instance will be created. Any previous VVM KM configuration will be upgraded and their server instances will be created. 5. Configure the KM. Configuring PATROL Agent to Preload the KM If you want Veritas Volume Manager KM for PATROL to operate all the time, without a PATROL Console connection, you will have to add it to the PATROL Agent configuration variable / AgentSetup/preloadedKMs. To configure the PATROL Agent to preload the KM 1. In the console, right-click the Veritas Volume Manager instance and select KM commands > Preloading. 2. Click Add to add the KM files to the list of preloaded KMs. Unloading the KM This section describes the procedures for unloading (not uninstalling) the Veritas Volume Manager KM for PATROL Agent, PATROL Console or PATROL Central Console. Read this section if you no longer want to use some parts of the KM; if you want to completely uninstall the KM, refer to the uninstall 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. 43 Loading the KM The KM will thus be added to the PATROL Agent configuration variable/agentsetup/preloadedkms.

44 Unloading the KM from the PATROL Agent To unload the KM from the PATROL Agent 1. In the Console, right-click the Veritas Volume Manager icon and select KM Commands > 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. Unloading the KM 44 With the PATROL Console for Unix:

45 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. 45 Unloading the KM

46 Upgrading the Platform

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

48 Performing Post-Installation Operations

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

50 Configuring VxVM Nodes Monitoring VVM KM allows you to monitor several VxVM nodes with one PATROL agent. Configuration Procedure Right-click the Veritas Volume Manager instance > KM Command > VxVM Nodes. Configuring VxVM Nodes Monitoring 2. Specify the VxVM nodes details: System ID: Enter an ID for the VxVM node. This information is only required if a unique ID cannot be generated using the hostname provided. (Required) Hostname/IP Address/FQDN: Enter the hostname, IP address, or FQDN of the VxVM node to be monitored. (Required) System Type: Specify whether the VxVM node is a UNIX/Linux or Windows Configuring VxVM Nodes Monitoring 50 1.

51 system. (Required) Status: Select Enable to start the VxVM node monitoring or Disable to stop it. 3. Check the Create a separate device in TrueSight option if you want the VxVM nodes to appear as a separate device in TrueSight. 4. Click Update. A VxVM Setup instance (VxVM Setup: <node-id>) appears in the PATROL Console but the monitoring will not start until the appropriate credentials are entered using the Login KM Command. Best Practices for Monitoring Veritas Volume Manager in a Cluster Since version , different methods exist to monitor multiple cluster nodes with VVM KM: 1. The remote monitoring method through the virtual cluster IP: the KM remotely monitors the entire cluster through the virtual IP in Single-node Mode. 2. The remote monitoring method from a non-cluster node: the PATROL Agent and the KM need to be installed on a central host and the KM needs to be configured to monitor nodes remotely. 3. The local monitoring method: the PATROL Agent and the KM need to be installed on all the managed nodes. 4. A mixed method (local and remote monitoring): the PATROL Agent and the KM are installed on one managed node and the KM monitors the other nodes remotely. Only the first two methods, which are recommended by Sentry Software, are described in this section. An article detailing the procedure for local monitoring and mixed method is available on Sentry's website. Although the article refers to Veritas Cluster Server KM for PATROL, the monitoring concepts and principles remain valid for Veritas Volume Manager for PATROL, see Configuring the Multi-node Monitoring Mode with the VCS KM. 51 Configuring VxVM Nodes Monitoring

52 Remote Monitoring Through the Virtual Cluster IP This method allows you to monitor the entire cluster through the virtual cluster IP or the hostname associated to the virtual IP. A central non-cluster node on which the PATROL Agent and the KM are installed is required: Remote Monitoring Through the Virtual Cluster IP - Diagram 1. Run the following command to find the virtual cluster IP: Obtaining the Virtual Cluster IP Configuring VxVM Nodes Monitoring 52

53 Configuring VxVM Nodes Monitoring through the Virtual Cluster IP Click Update. Click Close. Wait for the KM to create the Setup instance. Set the user account to be used to read and execute Veritas Volume Manager application programs and file systems: Right click the VxVM Setup instance > KM Commands > Login. Enter the VxVM admin credentials. Click OK. 53 Configuring VxVM Nodes Monitoring 2. Right-click the Veritas Volume Manager instance > KM Commands > VxVM Nodes. 3. Provide a virtual cluster IP or the hostname associated to the virtual IP. 4. Make sure the status Enabled is selected.

54 The KM monitors Veritas Volume Manager in the cluster through that virtual IP remotely in Singlenode Mode: Configuring VxVM Nodes Monitoring Monitoring the entire cluster through the virtual IP in PATROL 54

55 Remote Monitoring From a Non-Cluster Node This method allows you to remotely monitor several VxVM nodes from a central non-cluster node. The PATROL Agent as well as the VVM KM need to be installed on the non-cluster node. In our example, we have two VCS nodes, sofia and bucharest. They are both monitored remotely from rtpatrol-agent, a host outside the cluster on which the PATROL Agent and VVM KM have been installed. Remote Monitoring From a Non-Cluster Node - Diagram 1. Configure the monitoring of both nodes: Right-click the Veritas Volume Manager instance > KM Command > VxVM Nodes Specify the details one of the cluster node running the VxVM (in our example: sofia). Make sure the status Enable is selected. Click Update. Repeat the same for other cluster nodes running VxVM (in our example: bucharest) and click Update. Click Close. 55 Configuring VxVM Nodes Monitoring To monitor Veritas Volume Manager in this VCS cluster remotely from a PATROL Agent node outside the cluster:

56 2. Wait for the KM to create the Setup instances. 3. Set the user account to be used to read and execute Veritas Volume Manager application programs and file systems: Right-click the VxVM Setup instance > KM Commands > Login Enter the VxVM admin credentials Click OK Repeat the same for other VxVM nodes in the cluster Configuring VxVM Nodes Monitoring 56 Remote Monitoring from a Non-Cluster Node Configuring Nodes

57 Remote Monitoring from a Non-Cluster Node in Single-Node Mode PATROL Tree View 5. Configure the Multi-node Monitoring from one node: Right-click one of the System instance (in our example: System: sofia) > KM Commands > 57 Configuring VxVM Nodes Monitoring 4. Wait for the KM to create the instances in Permanent Single-node Mode on all managed nodes.

58 Monitoring Mode Select Multi-node Mode From the Cluster Application pull-down list, select appropriate cluster application. In our example: Veritas Cluster Server In the Failover Group Name field, enter the failover group name, which is online on one cluster node and offline on the others. In our example: ClusterService Provide the PATROL Agent Hostname (host where the PATROL agent is installed; in our example: rt-patrol-agent), the System ID (a unique ID for the VxVM node; in our example: sofia), and the Cluster Node Name (the hostname defined in VCS; in our example: sofia). Make sure the Remote PATROL Agent Checking option is Disabled Click Update Repeat the same procedure for other VxVM nodes in the cluster (in our example: bucharest) and click Update Click Close. Configuring VxVM Nodes Monitoring 58

59 Configuring the Multi-Node Monitoring Mode A full discovery is then performed on both nodes. The VVMMonitoringMode parameter indicates which node is active and passive. Some instances on the passive node (bucharest) disappear. In our example: sofia is active and the VVMMonitoringMode parameter reads 2 = Active Multi-node Mode bucharest is passive and the VVMMonitoringMode parameter reads 3 = Passive Multi-node Mode. Remote Monitoring from a Non-Cluster Node PATROL Tree View 59 Configuring VxVM Nodes Monitoring

60 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. 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 a System instance > KM Commands > Login Login Configuration dialog Configuring the KM User Account 60

61 2. To use: the default PATROL Agent Account, check the Use Agent Default Account option. 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 option click SUDO Path to verify the sudo path. 4. If you are monitoring a remote host, click Remote Connection Settings: Remote Connection Settings Connection Timeout (in Seconds): Enter the number of seconds after which the connection to the remote node will time out. Maximum Connections: Enter the maximum number of simultaneous connections allowed to the remote node. Click Accept. 5. Click OK. If the credentials are not valid, the VVMLoginStatus parameter will appear in suspicious state after the next data collection. To verify the application discovery 1. Check that the VxVM 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 a System 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. 61 Configuring the KM User Account Verifying Application Discovery

62 Verifying the Instance Limits By default, Veritas Volume Manager KM for PATROL monitors all the elements discovered, which may represent an important workload to the PATROL agents and console. 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. Since monitoring large number of instances may impact the performance of the KM, it is recommended to only monitor critical elements in large environments. To modify the default configuration 1. In the Console, right-click a System instance > Configuration> Instance Limits. Verifying Application Discovery 62

63 VVM KM Default Instance Limits 2. Enter the number of instances to be displayed in the console for each monitored element. To disable the monitoring of a specific application class, enter 0 in the relevant field. (By default, the maximum number of instances is left empty to allow an unlimited number of instances). 3. Click OK. 63 Verifying the Instance Limits

64 Verifying the Initial Setup of the KM To check the initial setup of the KM 1. Check for any error on the PATROL Console System Output Window (SOW) or in the VVM_<port>.log file available in PATROL_HOME/log. 2. Check whether the discovered files and directory paths are correct, using the menu Paths from the server instance. 3. Check the InfoBoxes and Parameters of all the VVM KM instances and verify that they are properly set. 4. Under each container instance, open all detail parameters (text parameters with names in the format VVM<Object>Details), and check for error messages. 5. Check the new values of the VVMLoginStatus parameter set after completion of all data collection. If it is not in OK state, open the annotation point to determine the cause of the error. 6. After the KM has been running for at least an hour: Right-click a System instance (VVM_SERVER) > KM commands > KM Status. A report is displayed, detailing information on the managed system. Check through the report for any warning or alarm. If any error is found during any of the above steps (including any incorrect data in Infoboxes or any warning or alarm 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. If needed, click Save As Task to open the report in a task window. You could later save it as a text file or print it. Restarting the PATROL Agent and PATROL Console is optional but often a good practice to confirm that the VVM KM operates correctly. In addition, the PATROL Agent restart will force all KM discoveries and data collections to start immediately. Verifying the Instance Limits 64 Restarting PATROL Agent and PATROL Console

65 Integrating the KM

66 Introduction This section provides detailed information about the integration of Veritas Volume Manager KM for PATROL with BMC TrueSight Operations Management. Integrating with BMC Portal Due to hierarchical changes implemented in Veritas Volume Manager KM for PATROL v3.0.00, migration from versions 2.x is not possible 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. On BMC Portal v2.9, volumes (in disk groups) may not be collected by the VVM KM integration par file. Integrating with BMC TrueSight OM No specific integration steps need to be performed. To know how to use Veritas Volume Manager KM for PATROL in BMC TrueSight Operations Management, please refer to the TrueSight Operations Management - Veritas Cluster Server Monitoring documentation. 66 Overview

67 Monitoring your Environment

68 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 VxVM Setup or System instance is displayed in the Console. Configuring Paths The KM automatically discovers the Veritas Volume Manager installation, the temporary directory paths used by the VVM KM, and the node status. This information can however be overridden. Altering these paths may impact the operation of VVM KM. 1. In the Console, right-click a System instance > KM commands > Paths. 2. In the KM section, verify and possibly modify the Home, Temp, and Debug Directory Paths. 3. In the VxVM section, verify and possibly modify the Installation and the Remote Temp Directory Paths. 4. In the Binary Paths and Library Paths sections: From the list, select the paths to be removed In the Path field, enter the new path(s) to be included. If several paths are to be entered, separate them with a colon (:). 5. Click OK. If you want to rediscover the paths, empty all fields, click OK, and restart the PATROL Agent. 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 68 To configure paths

69 operate in multi-node monitoring mode. The procedure below is generic. To learn more about all the configuration methods available, see Configuring the Multi-node Monitoring Mode with the VCS KM. Although the article refers to Veritas Cluster Server KM for PATROL, the monitoring concepts and principles remain valid for Veritas Volume Manager for PATROL. To configure the multi-node monitoring mode 1. In the Console, right-click a System instance > KM Commands > Monitoring Mode. Configuring the Multi-Node Monitoring Mode 69 Configuring the KM

70 2. Select Multi-node Mode. 3. From the Cluster Application pull-down list, select an appropriate cluster application. 4. In the Failover Group Name field, enter the failover group name, which is online on one cluster node and offline on the others. Leave this field blank if you previously selected Veritas Cluster File System. The VVM KM will then monitor the Veritas Volume Manager 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. Provide the details of all managed nodes of the cluster to be configured in the multi-node mode: PATROL Agent Hostname: host where the PATROL agent is installed System ID: the unique ID of the VVM node as configured in the KM menu Veritas Cluster Server instance > KM Command > VxVM Nodes. Cluster Node Name: the hostname defined in the selected Cluster Application. 6. Click Update. 7. Resume the procedure for all the other VxVM nodes and click Update. 8. Check the Remote PATROL Agent Checking option if there are more than one PATROL Agent involved in the multi-node mode configuration above. If enabled, the KM queries the other PATROL Agents to check the monitoring status of other nodes. 9. Click Close. PATROL Agent Configuration Configuring the KM 70

71 10. If the Remote PATROL Agent Checking is Enabled, you will have to provide all the information required to communicate with the PATROL Agents (protocol, port number, credentials, attempts and timeout). 11. Click Close. The Veritas Volume Manager will then be monitored through the master or online node in Active Multi-node Mode. The other nodes, which are standing by for a failover, will be in Passive Multinode Mode, monitoring only the components that are not visible from the active node. If a managed node is unable to check the monitoring status of the active managed node, it will change to Temporary Single-node Mode allowing a full VxVM monitoring. It will remain in Temporary Single-node Mode until it finds the active node in full monitoring mode again. If the Remote PATROL Agent Checking is Disabled, while there are more than one PATROL Agent involved, the managed node on the master or online node will be in Active Multi-node Mode and all others will be in Passive Multi-node Mode, without checking the monitoring status of the active node. In addition, the above procedure to configure Multi-node Mode (System instance > KM Commands > Monitoring Mode) needs to be repeated from each PATROL Agent involved. Filtering Elements to Monitor 1. In the Console, right-click one of the following instances depending on the elements that you wish to monitor: Daemons > KM Commands > Daemons to filter daemons to be monitored Logs > KM Commands > Logs to filter logs to be monitored. The system log will be monitored on UNIX/Linux platforms. On Windows platforms, the KM will monitor the Windows Event Log for System and Application. Disk Paths > KM Command > Disk Paths to filter disk paths to be monitored Diskgroups > KM Commands Diskgroups to filter diskgroups to be monitored Disk Devices > KM Commands > Disk Devices to filter disk devices to be monitored RLinks > KM Commands > Replication Links to filter replication links to be monitored RVGs> KM Commands > Replicated Volume Groups to filter replicated volumes groups to be monitored Volumes > KM Commands > Volumes to filter volumes to be monitored Plexes > KM Commands Plexes to filter plexes to be monitored Subdisks > KM Commands > Subdisks to filter subdisks to be monitored 71 Configuring the KM 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:

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

73 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. Veritas Volume Manager KM for PATROL can either be configured from a BMC PATROL Console (Classic Mode) or BMC TrueSight Operations Management. When the KM is installed on a PATROL Agent that is managed by Central Monitoring Administration (CMA), all the KM configuration menus are disabled in the PATROL Console. To configure VVM KM from a PATROL Console, you need to force the KM to run in Classic Mode. This will disconnect VVM KM from receiving configuration from Central Monitoring Administration. Any monitoring that was configured in CMA and used by the PATROL Agent will be discarded and replaced by the configuration made from the PATROL Console. However, this will not delete the policies created in CMA from the configuration. Any configuration for VVM KM received from Central Monitoring Administration will be ignored. 73 Configuring the KM Forcing the Classic Mode

74 To force the KM to run in Classic mode 1. In the PATROL Console, right-click the Veritas Volume Manager icon > KM commands > Force Classic Configuration Mode. 2. Check Force the KM to run in Classic mode and click OK. VVM KM will then start running in Classic Mode, enabling you to use the KM Configuration menus. To configure the KM in TrueSight OM, follow the above procedure and uncheck Force the KM to run in Classic mode. All configurations made through the PATROL Console will then be ignored. Configuring the KM 74 Forcing Classic Mode - Force Classic Configuration Mode

75 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 > Element Status. Deamon Status Configuration Dialog 75 Configuring the KM

76 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. Configuring the KM 76

77 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 a System instance > KM Commands > Node Status. Configuring Node Status 77 Configuring the KM

78 2. In the Monitored daemons list, select the daemons that will not 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. Configuring the KM 78

79 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. 79 Configuring the KM 1. In the Console, right-click the Logs instance > KM Commands > Log Filter.

80 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. Configuring the KM 80

81 To customize the log scan limit 1. In the Console, right-click the Log(s) instance > KM Commands > Log(s) Scan Limit. 2. Indicate the amount of data that will be read by the KM during each data collection cycle. 3. Click OK. Configuring Logs Alert Acknowledgment By default, alerts will automatically be acknowledged unless you modified the settings to allow manual acknowledgment. Manual acknowledgment may impact the performance of the application and of the PATROL Agent if the number of alerts waiting to be acknowledged constantly increases. 81 Configuring the KM Log Scan Limit Configuration dialog

82 To change the default behavior 1. In the Console, right-click the Log(s) instance > KM Commands > Configuration> Log(s) Alert Acknowledgment. 2. Indicate whether the warning and alarm messages will be manually or automatically acknowledged. 3. Click OK. Configuring the KM 82

83 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 will 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 83 Configuring the KM

84 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. To enable the debug mode 1. In the Console, right-click a System instance > KM Commands > Debug. VVM KM Debug Configuration dialog Using the KM 84

85 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_DISKPATH 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. 85 Using the KM 3. Set the Debug Options:

86 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. To disable 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. To prepare 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 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. Using the KM 86 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).

87 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 a System 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 a System 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. Forcing Selected Data Collectors 1. Right-click a System 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 a System instance and choose Parameters without Icons... Select the required data collector. Click Update. With the PATROL Console for Unix Right-click the a System instance and choose Customize > Parameters... Select the required data collector. Click on Options > Update. 87 Using the KM This option is only available from a PATROL Developer Console.

88 With the PATROL Central Operator Console Right-click a System instance and choose Properties... Select the tab Parameter List and select the required data collector. Click Update. Using the KM 88

89 Reference Guide

90 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 This section lists the application classes of Veritas Volume Manager KM for PATROL. It provides details on the icons that represent the class, Infobox, parameters and the menu commands available for each application class. 90

91 VVM_MAIN Icon Parameters No parameters. InfoBox Name Product Name Name of the Knowledge Module. Product Version Version number of the Knowledge Module. Product Release Date Release date of the Knowledge Module. PATROL Agent Version Version number of the PATROL Agent installed on the managed system. Copyright Sentry Software copyright. Web Site Support Function VxVM Nodes Allows to monitor several VxVM systems with one PATROL agent. Preloading Accesses the Preloading Configuration dialog, which adds or removes the KM from the 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. Force Classic Configuration Mode Forces the KM to "Classic Mode" and allows to configure VVM KM from PATROL Consoles. About Shows the version and general information about VVM KM. 91 Classes and Parameters Menu Commands

92 VVM_DAEMON Icon Name Units Default Alert Conditions Type VVMDaemonCPUDur Indicates the CPU ation seconds consumed by the daemon. Seconds Statistics VVMDaemonCPUUtil Indicates the CPU percentage consumed ization* by the daemon. Percentage (%) Statistics VVMDaemonMemor Indicates the core image size of the daemon in ysize* the virtual memory. Kilobytes (KB) Statistics VVMDaemonProcess Indicates the number of Processes the processes/threads of Count 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 Classes and Parameters 92 Parameters

93 Name Units Default Alert Conditions Type 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. VVMDaemonSumma Summarizes the daemon n/a ry information as reported by commands executed by the data collector. For detailed information about KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in TrueSight. InfoBox 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 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. Name 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 93 Classes and Parameters

94 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 Type VVMDaemonDe tails Displays all data returned to the standard output (stdout) from commands executed by the data collector n/a n/a Collectio n Status VVMDaemonCol lectorexectime seconds This is a standard parameter which monitors the collector execution time. It will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: %PSL pconfig("replace", "/Runtime/ VVM/<node-id>/ VVMDaemonCollectorWarn", 3600); InfoBox Classes and Parameters 94 Parameters

95 Collector Name Name of the data collector that sets variables and parameters under this 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 95 Classes and Parameters

96 Menu Commands Function Reports > Daemon List Lists all running Veritas Volume Manager daemons. 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. 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. Classes and Parameters 96

97 VVM_DISKDEVICE Icon Name Units Default Alert Conditions Type Kilobytes (KB) Statistics VVMDiskdevice Indicates the number Kilobytes per seconds (KB/s) IOKBytesRate* of KBytes transferred per second for the diskdevice since the last collect. Statistics VVMDiskdevice Indicates the total Operations IOOperations number of input and output operations on the diskdevice since the last collect. Statistics VVMDiskdevice Indicates the total IOOperationsFa number of failed input and output iled operations on the diskdevice on Unix platforms. Statistics VVMDiskdevice Indicates the number Operations per second IOOperationsRa of input and output (Operations/s) operations per te second for the diskdevice since the last collect. Statistics VVMDiskdevice Indicates the number Requests QueueDepth of read and write requests in queue for the diskdevice on Windows platforms. Statistics VVMDiskdevice Indicates the total IOKBytes number of KBytes transferred on the diskdevice since the last collect. Operations 97 Classes and Parameters Parameters

98 Default Alert Conditions Type VVMDiskdevice Indicates the number Kilobytes (KB) ReadKBytes of KBytes read on the diskdevice since the last collect. Statistics VVMDiskdevice Indicates the number Kilobytes per seconds (KB/s) ReadKBytesRat of KBytes read per second for the e* diskdevice since the last collect. Statistics VVMDiskdevice Indicates the number Operations ReadOperation of read operations on s the diskdevice since the last collect. Statistics VVMDiskdevice Monitors the number Operations ReadOperation of failed read operations on the sfailed 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 time for the ReadTime* 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 Classes and Parameters Units Milliseconds Gigabytes (GB) 98 Name

99 Units Default Alert Conditions Type VVMDiskdevice Indicates the state of State the diskdevice on Unix platforms. {0 = Online ; 1 = Online with Errors ; 2 = Failing ; 3 = Failed ; 4 = Offline ; -1 = Unknown} Availability VVMDiskdevice Indicates the state of StateNT the diskdevice on Windows platforms. {0 = Online/Imported ; 1 = Uninitialized ; 2 = Online with Errors ; 3 = Failing ; 4 = Failed ; 5 = Offline ; 6 = Foreign ; 7 = Detached ; 8 = Disconnected ; -1 = Unknown} Availability 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 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 since the last collect. Note: This parameter is not available for non-dynamic diskgroups on Windows platforms. Statistics 99 Classes and Parameters Name

100 Units Default Alert Conditions Type VVMDiskdevice Indicates the number Kilobytes per second (KB/s) WriteKBytesRat of KBytes written per second for the e* diskdevice since the last collect. Note: This parameter is not available for non-dynamic diskgroups on Windows platforms. Statistics VVMDiskdevice Indicates the number Operations WriteOperation of write operations s on the diskdevice since the last collect. Note: This parameter is not available for non-dynamic diskgroups on Windows platforms. Statistics VVMDiskdevice Monitors the number Operations WriteOperation of failed write operations on the sfailed 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 time for the WriteTime* diskdevice. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Warning when > 20 and < 100 Response Time Statistics Milliseconds 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. Classes and Parameters 100 Name

101 Name Units Default Alert Conditions Type Availability Note: This parameter is not available for non-dynamic diskgroups on Windows platforms. VVMDiskpathE nabled Monitors the number Count of enabled disk paths with kernel state ENABLED. Alarm = 1 VVMDiskpathN onenabled Indicates the number Count of disk paths that are not enabled. Warning when > 1 Availability and < 100 For detailed information about KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in TrueSight. Name Diskdevice Name of the Veritas Volume Manager diskdevice. Status Status of the Veritas Volume Manager diskdevice. Group Diskgroup name of the Veritas Volume Manager diskdevice. Disk Disk name of the Veritas Volume Manager diskdevice. Device Device name of the Veritas Volume Manager diskdevice. Type Type of the Veritas Volume Manager diskdevice. Tag Tag of the Veritas Volume Manager diskdevice. Offset Offset of the Veritas Volume Manager diskdevice. Available Space Available space on the Veritas Volume Manager diskdevice. Collector Name Name of the data collector that sets variables and parameters under this 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). 101 Classes and Parameters InfoBox

102 Menu Commands Function 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. 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. 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. 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. VVM_DISKDEVICE_CONTAINER Icon Parameters. InfoBox Classes and Parameters 102

103 Name Collector Name Name of the data collector that sets variables and parameters under this 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 n> Diskdevices Accesses the configuration dialog for specifying which diskdevices under the selected diskdevice container instance are to be monitored by the VVM KM. By default, all diskdevices are monitored. Configuratio n> Diskdevices Status Accesses the configuration dialog for determining the status for monitored diskdevice instances under the selected diskdevice container 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. Configuratio n > 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. 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. 103 Classes and Parameters Type [default] to reset any custom configuration from current level and below and inherit custom setting, if any, or revert to default configuration.

104 VVM_DISKGROUP Icon Name Units Default Alert Conditions Type VVMDiskgroupSpace Available* Indicates the 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 VVMDiskgroupState NT Indicates the state of the diskgroup on Windows platforms. {0 = Imported; 1 = Deported; 1 = Unknown} Availability {0 = OK; 1 = Suspicious; 2 = Failure} Warning = 1 Alarm = 2 Availability n/a n/a VVMDiskgroupStatus Monitors the status of the diskgroup. This status is determined by the diskgroup status mapping rule defined in the KM command Diskgroup(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. 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 TrueSight. InfoBox Name Name Name of the Veritas Volume Manager diskgroup. Classes and Parameters 104 Parameters

105 Name 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 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 > Diskgroup Topology Report Reports all Veritas Volume Manager topology objects for the selected diskgroup. Diskgroup Accesses the individual configuration for monitoring the selected diskgroup instance. This dialog allows the selected diskgroup instance to be enabled or disabled for monitoring by the VVM KM. Diskgroup Status Accesses the individual configuration for determining diskgroup status for the selected diskgroup instance. 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. Disk Devices Accesses the configuration dialog for specifying which diskdevices under the selected diskgroup instance are to be monitored by the VVM KM. By default, all diskdevices are monitored. Type [default] to reset any custom configuration from current level and below and inherit custom settings, if any, or revert to default configuration. Disk Devices Status Accesses the configuration dialog for determining the status for monitored diskdevice instances under the selected diskgroup 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. Disk Paths Accesses the global configuration dialog for configuring all monitored disk path instances. By default, all disk paths are monitored. 105 Classes and Parameters Menu Commands

106 Type [default] to reset to the default 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. Volumes Accesses the configuration dialog for specifying which volumes under the selected diskgroup instance are to be monitored by the VVM KM. By default, all volumes are monitored. Type [default] to reset any custom configuration from current level and below and inherit custom setting, if any, or revert to default configuration. Volumes Status Accesses the configuration dialog for determining the status for monitored volume 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. Volumes Logging Status (Unix only) 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. Plexes Accesses the configuration dialog for specifying which plexes under the selected diskgroup instance are to be monitored by the VVM KM. By default, all plexes are monitored. Type [default] to reset any custom configuration from current level and below and inherit custom setting, if any, or revert to default configuration. Plexes Status Accesses the configuration dialog for determining the status for monitored plex 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. Plexes Kernel Status Accesses the configuration dialog for determining the kernel status for monitored plex instances under the selected diskgroup 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. Subdisks Accesses the dialog for specifying which subdisks under the selected diskgroup instance are to be monitored by the VVM KM. By default, all subdisks are monitored. Classes and Parameters 106 Accesses the configuration dialog for determining the kernel status for monitored volume Volumes Kernel 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.

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

108 VVM_DISKGROUP_CONTAINER Icon Parameters Name Units Default Alert Conditions Type seconds Warning when > preset value or observed maximum (default) Collectio n Status VVMDiskdeviceDeta Displays all data returned to the standard ils output (stdout) from commands executed by the data collector n/a n/a VVMDiskgroupColle ctorexectime seconds Warning when > preset value or observed maximum (default) Collectio n Status n/a n/a VVMDiskdeviceColle ctorexectime This is a standard parameter which monitors the collector execution time. It will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: This is a standard parameter which monitors the collector execution time. It will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: %PSL pconfig("replace", "/Runtime/VVM/ <node-id>/vvmdiskgroupcollectorwarn", 3600); VVMDiskgroupDetai Displays all data returned to the standard out ls from commands executed by the data collector. Classes and Parameters 108 %PSL pconfig("replace", "/Runtime/VVM/ <node-id>/vvmdiskdevicecollectorwarn", 3600);

109 Name VVMPlexCollectorEx ectime This is a standard parameter which monitors the collector execution time. It will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: Units Default Alert Conditions Type seconds Warning when > preset value or observed maximum (default) Collectio n Status n/a n/a seconds Warning when > preset value or observed maximum (default) Collectio n Status n/a Collectio n Status seconds Collectio n Status n/a Collectio n Status %PSL pconfig("replace", "/Runtime/VVM/ <node-id>/vvmplexcollectorwarn", 3600); VVMPlexDetails VVMRlinkCollectorE xectime Displays all data returned to the standard output (stdout) from commands executed by the data collector This is a standard parameter which monitors the collector execution time. It will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: VVMRlinkDetails VVMRvgCollectorEx ectime Displays all data returned to the standard output (stdout) from commands executed by the data collector This is a standard parameter which monitors the collector execution time. It will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: %PSL pconfig("replace", "/Runtime/VVM/ <node-id>/vvmrvgcollectorwarn", 3600); VVMRvgDetails Displays all data returned to the standard output (stdout) from commands executed by the data collector 109 Classes and Parameters %PSL pconfig("replace", "/Runtime/VVM/ <node-id>/vvmrlinkcollectorwarn", 3600);

110 Name VVMSubdiskCollect orexectime This is a standard parameter which monitors the collector execution time. It will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: Units Default Alert Conditions Type seconds Warning when > preset value or observed maximum (default) Collectio n Status n/a n/a seconds Warning when > preset value or observed maximum (default) Collectio n Status n/a n/a %PSL pconfig("replace", "/Runtime/VVM/ <node-id>/vvmsubdiskcollectorwarn", 3600); VVMSubdiskDetails VVMVolumeCollect orexectime Displays all data returned to the standard output (stdout) from commands executed by the data collector This is a standard parameter which monitors the collector execution time. It will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: 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 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 Classes and Parameters 110 %PSL pconfig("replace", "/Runtime/VVM/ <node-id>/vvmvolumecollectorwarn", 3600);

111 Function Reports > Veritas Volume Manager Topology Report Reports all Veritas Volume Manager topology objects. 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. 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: 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. 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. 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: By default, the following VVMDiskdeviceStateNT to VVMDiskdeviceStatus mapping rule is used on Windows platforms: Select [default] to reset to the default diskdevice status mapping rule. 111 Classes and Parameters Disk Devices Status

112 Function 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. 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. Volumes Accesses the global configuration dialog for specifying which volumes are to be monitored by the VVM KM. By default, all volumes are monitored. Type [default] to reset to the default 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: Select [default] to reset to the default volume status mapping rule. Volumes Kernel Status Classes and Parameters 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: 112 By default, the following VVMVolumeStateNT to VVMVolumeStatus mapping rule is used on Windows platforms:

113 Function 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. Volumes Logging Status (UNIX only) 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: Select [default] to reset to the default volume logging status mapping rule. 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. 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: 113 Classes and Parameters Plexes Status

114 Function Select [default] to reset to the default plex status mapping rule. Accesses the global configuration dialog for determining the plex kernel status for Plexes Kernel Status 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. 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. 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: Select [default] to reset to the default subdisk kernel status mapping rule. Replicated Volume Groups Classes and Parameters 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: 114 Subdisks Kernel Status

115 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: 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. 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: 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 115 Classes and Parameters

116 VVM_DISKPATH Icon Parameters Units Default Alert Conditions 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 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 116 Type Name

117 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 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 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. 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 117 Classes and Parameters

118 Parameters Units Default Alert Conditions Type Count Alarm when > 1 and < 100 Statistic s VVMLogAlarmTe Displays all alarm messages in the log file which n/a xt have not been acknowledged. The filter used by the data collector to determine alarm messages can be customized using the KM command Log(s) Filter. These alarm messages can be acknowledged automatically (default) or manually, depending on the configuration in the KM command Log(s) Alert Acknowledgement. Manual acknowledgement is available under the KM sub-menuacknowledgement. n/a VVMLogFSSpace Monitors the percentage of space used by the file system (where the log file resides). UsedPercent* 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 Monitors the available space for the log file to ailable 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) Warning when > 2 and < 5 Alarm when > -1 and < 2 VVMLogSpaceGr Displays the growth rate of the amount of space owthrate used by the log file. Kilobytes per seconds (KB/s) Statistic s VVMLogSpaceUs Displays the amount of space used by the log ed file. Kilobytes (KB) Statistic s 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. Availabil ity VVMLogSpaceUs Monitors the percentage of capacity used by the Percentage log file. (%) edpercent* 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 Summarizes the log file information as reported y by commands executed by the data collector. Classes and Parameters 118 n/a n/a Name

119 Name Units VVMLogText Displays all log text scanned by the data n/a collector during the last collection cycle. The size of the data scanned by the data collector is configured in the KM command Log(s) Scan Limit. 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 VVMLogWarning Displays all warning messages in the log file n/a Text which have not been acknowledged. The filter used by the data collector to determine warning messages can be customized using the KM command Log(s) Filter. These warning messages can be acknowledged automatically (default) or manually, depending on the configuration in the KM command Log(s) Alert Acknowledgement. Manual acknowledgement is available under the KM sub-menu Acknowledgement. For detailed information about Default Alert Conditions Type n/a Warning when > 1 Statistic s 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 TrueSight. 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. 119 InfoBox Classes and Parameters

120 Name Collector Name Name of the data collector that sets variables and parameters under this 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 Acknowledgeme nt > Warnings Allows acknowledgement of warning messages detected on the selected log file instance. This dialog allows selective acknowledgement of "suspicious" error messages detected in the log file and sent to the text parameter VVMLogWarningText. Acknowledgeme nt > Alarms Allows acknowledgement of alarm messages detected on the selected log file instance. This dialog allows selective acknowledgement of "failure" error messages detected in the log file and sent to the text parameter VVMLogAlarmText. Acknowledgeme nt > All Allows acknowledgement of all alarm and warning messages detected on the selected log file instance. This dialog allows acknowledgement of all error messages detected in the log file and sent to the text parameter VVMLogWarningText or VVMLogAlarmText. 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. 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. 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. Log Alert Acknowledgeme nt 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 120 Menu Commands

121 VVM_LOG_CONTAINER Icon Parameters Name VVMLogColle ctorexectime This is a standard parameter which monitors the collector execution time. It will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: Units Default Alert Conditions Type Seconds Warning > preset value or observed maximum (default) Collectio n Status n/a n/a %PSL pconfig("replace", "/Runtime/VVM/<nodeid>/VVMLogCollectorWarn", 3600); VVMLogDetai Displays all data returned to the standard output ls (stdout) from commands executed by the data collector Name Collector Name Name of the data collector that sets variables and parameters under this 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 121 Classes and Parameters InfoBox

122 Function Reports > Messages List Reports the last 100 lines logged in the associated log file. 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. Type [default] to reset to the default configuration. 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. Type [default] to reset to the default configuration. Logs Scan Limit Classes and Parameters Accesses the global configuration of the data scanning limit for monitored log file instances. By default, the log collector only scans 500 KBytes of new log data for each monitored log file during each data collection cycle. 122 Logs Filter

123 Function Logs Alert Acknowledgeme nt Accesses the global configuration of the method of acknowledgment 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 Type VVMPlexIOKBytes Indicates the total number of KBytes transferred on the plex since the last collect. Kilobytes (KB) Statistics VVMPlexIOKBytesRate* Indicates the number of KBytes transferred per second for the plex on Unix platforms since the last collect. Kilobytes per second (KB/s) Statistics VVMPlexIOOperations Indicates the total number of input and output operations on the plex on Unix platforms since the last collect. Operations Statistics VVMPlexIOOperationsFail Indicates the total number of failed input ed and output operations on the plex on Unix platforms. Operations Statistics VVMPlexIOOperationsRat e Operations per second (Operations/ second) Statistics Indicates the number of input and output operations per second for the plex on Unix platforms since the last collect. 123 Classes and Parameters Parameters

124 Units Default Alert Conditions 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 status of the plex. This status is determined by 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. {0 = OK ; 1 = Suspicious ; 2 = Failure} Warning = 1 Alarm = 2 Availability VVMPlexReadKBytes Indicates the number of KBytes read on the plex on Unix platforms since the last collect. Kilobytes (KB) Statistics VVMPlexReadKBytesRate * Indicates the number of KBytes read per second for the plex on Unix platforms since the last collect. Kilobytes per second (KB/s) Statistics VVMPlexReadOperations Indicates the number of read operations on the plex on Unix platforms since the last collect. Operations Statistics VVMPlexReadOperationsF Monitors the number of failed read operations ailed 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 Classes and Parameters 124 Name

125 Units Default Alert Conditions Type VVMPlexReadTime* Monitors the read 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 when > 20 Response Time 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 plex on Unix platforms. {0 = Active; 1 = Clean; 2 = Empty; 3 = Log Plex; 4 = Temporary Plex; 5 = Snapshot Plex; 6 = No Disk/Device; 7 = Recover; 8 = Removed; 9= Stale; 10= Offline; 11 = I/O Failure; -1 = Unknown} Availability VVMPlexStateNT Displays the state of the plex on Windows platforms. {0 = Active/Attached; 1 = Recoverable; 2 = Failed; -1 = Unknown} Availability VVMPlexStatus Monitors the status of the plex. This status is determined by the plex 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. {0 = OK; 1 = Suspicious; 2 = Failure} Warning = 1 Alarm = 2 Availability 125 Classes and Parameters Name

126 Units Default Alert Conditions Type VVMPlexSummary Summarizes the plex information as reported by commands executed by the data collector. n/a n/a VVMPlexWriteKBytes Indicates the number of KBytes written on the plex on Unix platforms since the last collect. Kilobytes (KB) Statistics VVMPlexWriteKBytesRate Indicates the number of KBytes written per * second for the plex on Unix platforms since the last collect. Kilobytes per second (KB/s) Statistics VVMPlexWriteOperations Indicates the number of write operations on the plex on Unix platforms since the last collect. Operations Statistics VVMPlexWriteOperations Failed Monitors the number of 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. VVMPlexWriteTimeAvera ge* Monitors the average Milliseconds write time for the plex on Unix platforms. If this parameter changes to warning or alarm state, the recovery action will trigger an event. For detailed information about 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 TrueSight. Classes and Parameters 126 Name

127 InfoBox Name Plex Name of the Veritas Volume Manager plex. Status Status of the Veritas Volume Manager plex. Group Diskgroup name of the Veritas Volume Manager plex. Volume Volume name of the Veritas Volume Manager plex. KState Kernel state of the Veritas Volume Manager plex. Length Length of the Veritas Volume Manager plex. Type Type of the Veritas Volume Manager plex. Collector Name Name of the data collector that sets variables and parameters under this 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 Plex Accesses the individual configuration for determining the status for the selected plex Status 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. 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. 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. 127 Classes and Parameters 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.

128 Function 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. VVM_RLINK Icon Parameters Units Default Alert Conditions Type VVMRlinkKernelStat Set by VVMRlinkCollector. Displays the kernel {0 = Connect; e state of the replication link. 1 = Enabled; 2 = DCM Logging; 3 = Recover; 4= Detached; -1 = Unknown} Availabili ty VVMRlinkKernelStat Set by VVMRlinkCollector. Displays the kernel {0 = OK; us status of the replication link. 1= Suspicious; 2 = Failure} Warning = 1 Alarm = 2 Availabili ty VVMRlinkRemainin gupdatescount Set by VVMRlinkCollector. Displays the number of updates the primary RVG is ahead of the secondary RVG. Updates Statistics VVMRlinkRemainin gupdateslag Set by VVMRlinkCollector. Displays the Seconds amount of time the secondary RVG is lagging. Statistics 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. Warning when > 80 and < 90 Alarm when > 90 Statistics Classes and Parameters 128 Percentage (%) Name

129 Name Default Alert Conditions Type VVMRlinkRemainin gupdatessize* Set by VVMRlinkCollector. Displays the size of Kilobytes the SRL in KBytes. (KBytes) Statistics 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} Availabili ty VVMRlinkStatus Set by VVMRlinkCollector. Displays the status of the replication link. {0 = OK; 1= Suspicious; 2 = Failure} Availabili ty VVMRlinkSummary Summarizes the Rlink information as reported n/a by commands executed by the data collector. For detailed information about Units 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 TrueSight. 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. 129 InfoBox Classes and Parameters

130 Name Remote Host Name of the remote host. Collector Name Name of the data collector that sets variables and parameters under this 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 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. 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. 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 Icon Classes and Parameters 130

131 Name Units Default Alert Conditions Type VVMRvgKernelState Set by VVMRvgCollector. Displays the kernel state of the replicated volume group. {0 = Enabled; 1 = Recover; 2 = Disabled; -1 = Unknown} Availabili ty VVMRvgKernelStatu Set by VVMRvgCollector. Displays the kernel s status of the replicated volume group. {0 = OK; 1= Suspicious; 2 = Failure} Warning = 1 Alarm = 2 Availabili ty VVMRvgRlinkCount * Set by VVMRvgCollector. Displays the number rlinks of replication links in the replicated volume group. Availabili ty VVMRvgState Set by VVMRvgCollector. Displays the state of {0 = Active; the replicated volume group. 1 = Empty; 2 = Clean; 3 = Fail; -1 = Unknown} Availabili ty VVMRvgStatus Set by VVMRvgCollector. Displays the status of the replicated volume group. {0 = OK; 1= Suspicious; 2 = Failure} Warning = 1 Alarm = 2 Availabili ty VVMRvgSummary Summarizes the replicated volume group information as reported by commands executed by the data collector. n/a Availabili ty Availabili ty VVMRvgVolumeCou Set by VVMRvgCollector. Displays the number volumes nt* of replicated data volumes. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in TrueSight. InfoBox 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. 131 Classes and Parameters Parameters

132 Name Kernel State Kernel state of the Replicated Volume Group. Data Volumes Names of the data volumes in the Replicated Volume Group. SRL Name of the Storage Replicator Log. Collector Name Name of the data collector that sets variables and parameters under this 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 Replicated Volume Group Accesses the individual configuration for monitoring the selected Replication Volume Group instance. 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. 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. 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. 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. Classes and Parameters 132 Accesses the individual configuration for determining the kernel status for the Replicated Volume selected RVG instance. By default, the global VVMRvgKernelState to Group Kernel Status 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.

133 VVM_RVG_CONTAINER Icon Parameters InfoBox Name Collector Name Name of the data collector that sets variables and parameters under this 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 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. 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: 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: 133 Classes and Parameters Menu Commands

134 Function 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. 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: 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: Icon Collectors Name VVMCreateDistribution Is automatically activated during KM debugging and deactivated when the debug zip or tar file is created. Default polling interval: 1 minute. Classes and Parameters 134 VVM_SERVER

135 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. 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. 135 Classes and Parameters Name

136 Parameters 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 {0 = OK; login details (username/password) 1 = Suspicious; for the operating system. It is set by 2 = Failure} VVM_SERVER application class discovery. If no valid username/password is detected for the operating system, this parameter will be set to "Failure" state. If there are any suspicious command exits, this parameter will be set to "Suspicious" state. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. VVMNodeStatus* Classes and Parameters {0 = Permanent Single-node Mode; 1 = Temporary Single-node Mode; 2 = Active Multinode Mode; 3 = Passive Multinode Mode; -1 = Unknown} 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 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. 136 Collection Status Warnin Availability g= 1 Alarm = 2 VVMMonitoringMo Indicates the VVM monitoring mode. de* Warnin Collection g= 1 Status Alarm = 2

137 Name Units Default Alert Conditio ns BMC ProactiveNet Attribute Type If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in TrueSight. 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. PATROL Agent Version Version number of the PATROL Agent installed on the managed system. Platform Operating system platform as reported by the PATROL Agent (HP, SOLARIS, RS6000, or NT). Product Name Name of the Knowledge Module. Product Release Date Release date of the Knowledge Module. 137 Classes and Parameters InfoBox

138 Name Product Version Version number of the Knowledge Module. Support Web site Function Refresh Process Cache Forces the PATROL Agent to reload its process cache from the kernel process list. Force Discovery Forces application discovery. 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. Classes and Parameters 138 Menu Commands

139 Function 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. 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 Parameters Name Units Default Alert Conditions Type VVMSubdiskIOKBytes Indicates the total number of KBytes transferred on the subdisk since the last collect. Kilobytes (KB) Statistics Kilobytes per second (KB/s) Statistics VVMSubdiskIOKBytesRat Indicates the number of KBytes transferred per e* second for the subdisk since the last collect. 139 Classes and Parameters Icon

140 Units Default Alert Conditions Type VVMSubdiskIOOperatio ns Indicates the total number of input and output operations on the subdisk since the last collect since the last collect. Operations 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 since the last collect. 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 VVMSubdiskKernelState NT Indicates the kernel state of the subdisk on Windows platforms. {0 = Enabled; 1 = Unreported/ Undefined; 2 = Error; 3 = Disabled; -1 = Unknown} Availability VVMSubdiskKernelStatu s Monitors the kernel status of the subdisk. This status is determined by the subdisk status mapping rule defined in the KM command 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. {0 = OK; 1 = Suspicious; 2 = Failure} Warning = 1 Alarm = 2 Availability VVMSubdiskReadKBytes Indicates the number of KBytes read on the subdisk since the last collect. Kilobytes (KB) Statistics VVMSubdiskReadKBytes Rate* Indicates the number of KBytes read per second for the subdisk since the last collect. Kilobytes per second (KB/s) Statistics Classes and Parameters 140 Name

141 Units Default Alert Conditions Type VVMSubdiskReadOperat Indicates the number of ions* read operations on the subdisk. Operations Statistics VVMSubdiskReadOperat Monitors the number of failed read operations on ionsfailed 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* Monitors the read 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 VVMSubdiskReadTimeA verage* Monitors the average read time for the subdisk. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Statistics VVMSubdiskSummary Summarizes the subdisk n/a information as reported by commands executed by the data collector. n/a Milliseconds VVMSubdiskWriteKBytes Indicates the number of KBytes written on the subdisk since the last collect. Kilobytes (KB) Statistics VVMSubdiskWriteKBytes Indicates the number of KBytes written per second Rate* for the subdisk since the last collect. Kilobytes per second (KB/s) Statistics VVMSubdiskWriteOpera tions Indicates the number of write operations on the subdisk since the last collect. Operations Statistics VVMSubdiskWriteOpera tionsfailed Monitors the number of failed write operations on the subdisk on Unix platforms. Operations Warning when Statistics > Classes and Parameters Name

142 Name Units Default Alert Conditions Type If this parameter changes to warning or alarm state, the recovery action will trigger an event. 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 Monitors the average write Milliseconds verage* time for the subdisk. If this parameter changes to warning or alarm state, the recovery action will trigger an event. For detailed information about 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 TrueSight. Classes and Parameters 142

143 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 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 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. 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. 143 Classes and Parameters Menu Commands

144 VVM_VOLUME Icon Name Units Default Alert Conditions Type VVMVolumeIOKBytes Indicates the total number of KBytes transferred on the volume since the last collect. 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 since the last collect. 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 since the last collect. 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 Classes and Parameters 144 Parameters

145 VVMVolumeKernelStatus Units Default Alert Conditions Type Monitors the kernel {0 = OK; status of the volume. This 1 = Suspicious; status is determined by 2 = Failure} the volume status mapping rule defined in the KM command 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. Warning = 1 Alarm = 2 Availability VVMVolumeLoggingState Indicates the logging state {0 = Enabled; of the volume on Unix 1 = Disabled; platforms. -1 = Unknown} Availability VVMVolumeLoggingStatus Monitors the logging {0 = OK; status of the volume on 1 = Suspicious; Unix platforms. This 2 = Failure} status is determined by the volume status mapping rule defined in the KM command 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. Warning = 1 Alarm = 2 Availability VVMVolumeReadKBytes Indicates the number of KBytes read on the volume since the last collect.. Kilobytes (KB) Statistics VVMVolumeReadKBytesRat e* Indicates the number of KBytes read per second for the volume since the last collect. Kilobytes per second (KB/s) Statistics Operations Statistics VVMVolumeReadOperation Indicates the number of s read operations on the volume since the last collect Classes and Parameters Name

146 Units VVMVolumeReadOperation Monitors the number of Operations failed read operations on sfailed the volume on Unix platforms. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Default Alert Conditions Type Warning when > 10 Statistics VVMVolumeReadTime* Monitors the read time Milliseconds for the volume. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Warning when > 20 Response Time VVMVolumeReadTimeAver age* Monitors the average Milliseconds read time for the volume. If this parameter changes to warning or alarm state, the recovery action will trigger an event. 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 2 = Failure} volume status mapping rule defined in the KM command Volume(s) Status. Warning = 1 Alarm = 2 Availability Classes and Parameters 146 Name

147 Name Units Default Alert Conditions 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 since the last collect.. Kilobytes (KB) Statistics VVMVolumeWriteKBytesRa te* Indicates the number of Kilobytes per KBytes written per second second (KB/s) for the volume since the last collect.. Statistics VVMVolumeWriteOperatio ns Indicates the number of write operations on the volume since the last collect.. Statistics VVMVolumeWriteOperatio nsfailed Monitors the number of Operations 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. Warning when > 10 Statistics VVMVolumeWriteTime* Monitors the write time Milliseconds for the volume. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Warning when > 20 Response Time Statistics Operations VVMVolumeWriteTimeAver Monitors the average Milliseconds age* write time for the volume. If this parameter changes to warning or alarm state, the recovery action will trigger an event. For detailed information about KPI, see Managing Baselines and Key Performance Indicators. 147 Classes and Parameters If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point.

148 * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in TrueSight. 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. 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 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 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. 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. Accesses the configuration dialog for determining the kernel status for the selected Volume Kernel Status volume instance. Classes and Parameters 148 Menu Commands

149 Function 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. 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. 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. 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. 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. 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 149 Classes and Parameters 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.

150 Parameters InfoBox Name Collector Name Name of the data collector that sets variables and parameters under this 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 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. 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. 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. 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. Plexes Accesses the dialog for specifying which plexes under the selected volume container instance are to be monitored by the VVM KM. Classes and Parameters 150 Menu Commands

151 Function 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. Plexes Status Accesses the configuration dialog for determining the status for monitored plex 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. Plexes Kernel Status Accesses the configuration dialog for determining the kernel status for monitored 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. 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. Subdisks Kernel Status Accesses the configuration dialog for determining the kernel status for monitored 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. To detect abnormalities on the monitored environment, BMC TrueSight Operations Management calculates baselines per attribute 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 attributes are identified by default as Key Performance Indicators (identified with the icon) and automatically included in the base lining calculation. Managing baselines The baseline is the expected normal operating range for an attribute of a monitor. There are two baselines: Baseline High and Baseline Low. Baseline High represents the point at which 95% of the weighted average of the historical values fall below this value for the selected time period; Baseline Low represents the point at which 90% of the weighted average of historical values for the selected time period fall above this line. 151 Classes and Parameters Managing Baselines and Key Performance Indicators

152 Baselines are generated for KPI attributes that have an active abnormality thresholds. Managing Key Performance Indicators Starting from v9.5 of BPPM, attributes that have not been initially designated in the KM as Key Performance Indicators (KPIs) cannot be flagged as KPIs from BPPM/TrueSight. Although enabling baseline is possible through the Options > Administration > Intelligent Event Thresholds feature available in the Infrastructure Management Server operator console, BMC does not recommend doing it. For more information, refer to the BMC TrueSight Operations Management documentation available from docs.bmc.com. Classes and Parameters 152

153 Additional Information and Support

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

155 BMC Software PATROL Agent 11 BMC Software PATROL Console 11 Requirements 11 BMC PATROL Changes 11 pslinstructionmax 11 BMC ProactiveNet -AAbnormalities Access 151 Executable Files 13 Files 13 Library Files 13 Paths 13 Permissions 13 Acknowledge Logs Alert 81 Adapter 66 AIX 13 Application Class VVM_DAEMON 92 VVM_DAEMON_CONTAINER 94 VVM_DISKDEVICE 97 VVM_DISKDEVICE_CONTAINER 102 VVM_DISKGROUP 104 VVM_DISKGROUP_CONTAINER 108 VVM_DISKPATH 116 VVM_LOG 117 VVM_LOG_CONTAINER 121 VVM_PLEX 123 VVM_RLINK 128 VVM_RVG 130 VVM_SERVER 134 VVM_SUBDISK 139 VVM_VOLUME 144 VVM_VOLUME_CONTAINER 149 -BBaselines BMC ProactiveNet Performance Management 151 Generation 151 Manage 151 Requirements 151 BMC BMC Portal 66 BMC ProactiveNet Performance Management Portal 11 Integration 66 BMC ProactiveNet Performance Management Abnormalities 151 Baselines 151 Key Performance Indicators 151 KPI 151 -CChanges Check 6 Instance Limits Classic 62 Mode 73 Classic Mode Force Cluster 73 Configure 68 Clustering Application 68 CMA Mode 73 Collectors VVMCreateDistribution 134 VVMDaemonCollector 134 VVMDiskdeviceCollector 134 VVMDiskgroupCollector 134 VVMLogCollector 134 VVMPlexCollector 134 VVMRlinkCollector 134 VVMRvgCollector 134 VVMSubdiskCollector 134 VVMUpdateAgent 134 VVMVolumeCollector 134 Command Configuration 102 Disk Paths 102 Disk Paths Kernel Status 102 Diskdevices 102 Diskdevices Status 102 Commands About Index

156 Refresh Process Cache 134 Reload Commands 134 Replicated Volume Group 130 Replicated Volume Group Kernel Status 130 Replicated Volume Group Status 130 Replicated Volume Groups 104 Replicated Volume Groups Kernel Status 104 Replicated Volume Groups Status 104 Replication Link Kernel Status 128 Replication Link Status 128 Replication Links 104, 128, 130 Replication Links Kernel Status 104, 130 Replication Links Status 104, 130 Reports 94, 104, 108, 121 Subdisk 139 Subdisk Kernel Status 139 Subdisks 104, 108, 123, 144, 149 Subdisks Kernel Status 104, 108, 123, 144, 149 Veritas Volume Manager Topology Report 108 Volume 144 Volume Kernel Status 144 Volume Logging Status 144 Volume Status 144 Volumes 104, 108, 149 Volumes Kernel Status 104, 108, 149 Volumes Logging Status 104, 108, 149 Volumes Status 104, 108, 149 Warnings 117 Configure Cluster 68 Daemons 75 Disk Devices 75 Disk Groups 75 Disk Paths Kernel 75 Log Error Filter 78 Log Scan Limit 80 Logs Alert Acknowledgement 81 Multi-Node Monitoring Mode 68 Node Status 77 Paths 68 PATROL Agent 43 Plex 75 Plex Kernel 75 Remonte Connection Settings 60 Status Commands Acknowledgement 117 Alarms 117 All 117 Configuration 92, 94, 97, 104, 108, 116, 117, 121, 123, 128, 130, 134, 139, 144, 149 Daemon 92 Daemon List 94 Daemon Status 92 Daemons 94 Daemons Status 94 Debug 134 Disk Devices 104, 108 Disk Devices Status 104, 108 Disk Path 116 Disk Path Kernel Status 116 Disk Paths 97, 104, 108 Disk Paths Kernel Status 97, 104, 108 Diskdevice 97 Diskdevice Status 97 Diskgroup 104 Diskgroup Status 104 Diskgroup Topology Report 104 Diskgroups 108 Diskgroups Status 108 Force Discovery 134 Instance Limits 134 KM Status 134 Log 117 Log Alert Acknowledgement 117 Log Filter 117 Log Scan Limit 117 Login 134 Logs 121 Logs Alert Acknowledgement 121 Logs Filter 121 Logs Scan Limit 121 Messages List 121 Monitoring Mode 134 Node Status 134 Paths 134 Plex 123 Plex Kernel Status 123 Plex Status 123 Plexes 104, 108, 144, 149 Plexes Kernel Status 104, 108, 144, 149 Plexes Status 104, 108, 144, 149 Preloading 134 Refresh Parameters 134

157 -DDaemons Delete 71 Disable 71 Enable 71 Data Collectors Force 87 Debug Disable 84 Enable 84 Delete Daemons 71 Disk Devices 71 Disk Paths 71 Diskgroups 71 Logs 71 Plexes 71 Subdisks 71 Volumes 71 Disable Daemons 71 Debug 84 Disk Devices 71 Disk Paths 71 Diskgroups 71 Logs 71 Plexes 71 Subdisks 71 Volumes 71 Discoveries Force 87 Discovery Verify 61 Disk Devices Delete 71 Disable 71 Enable 71 Disk Paths Delete 71 Disable Enable Disk Space Requirements Diskgroups Delete 71 Disable 71 Enable EEnable Daemons 71 Debug 84 Disk Devices 71 Disk Paths 71 Diskgroups 71 Logs 71 Plexes 71 Subdisks 71 Volumes 71 -FFailover Group Name 68 Files 20 ins_all_<version>.tar 19 ins_windows_<version>.exe Setup 21 setup.exe 24 setup.sh 24 uninstall.exe 35 uninstall.sh 35 Force All Data Collectors 87 All Discoveries 87 Classic Mode 73 Selected Data Collectors 87 -GGenerate Baselines 151 Reports Configure Sudo 60 User Account 60 Volume 75 Volume Kernel 75 Volume Logging 75 Console Administration 73

158 help 154 HP-UX 13 -IImprovement 6 InfoBox Application Name 134 Application Version 134 Available FS Space 117 Available Space 97 Binary Path 134 Collector Last End 92, 94, 97, 102, 104, 108, 116, 117, 121, 123, 128, 130, 139, 144, 149 Collector Last Start 92, 94, 97, 102, 104, 108, 116, 117, 121, 123, 128, 130, 139, 144, 149 Collector Name 92, 94, 97, 102, 104, 108, 116, 117, 121, 123, 128, 130, 139, 144, 149 Collector Next Start 92, 94, 97, 102, 104, 108, 116, 117, 121, 123, 128, 130, 139, 144, 149 Collector Status 92, 94, 97, 102, 104, 108, 116, 117, 121, 123, 128, 130, 139, 144, 149 Command 92 Copyright 134 Data Volumes , 117 Device 97, 139 Disk 97, 116, 139 Disk Access Name 116 Diskdevice 97 Drive Letter 144 FS Percent Used 117 Group 97, 116, 123, 128, 130, 139, 144 Host Name 134 ID 104 Installation Path 134 Kernel State 116, 128, 130 KState 123, 139, 144 Last Purge 117 Latency Protection 128 Length 123, 139, 144 Library Path 134 Check 62 Integration BMC ProactiveNet Introduction 23 Issues Fixed H- Local Host 128 Log File Modification Time 117 Log File Size 117 Log Length 144 Logging 144 Monitoring Mode 134 Monitoring Node 134 Name 92, 104, 117 Node Name(s) 134 Offset 97 Operating System 134 Owner 92 Path 116, 117 PATROL Agent Version 134 PID 92 Platform 134 Plex 123, 139 PPID 92 Product Name 134 Product Release Date 134 Product Version 134 Remote Host 128 Rlink 128 RVG 128, 130 SRL 130 SRL Overflow Protection 128 Status 92, 97, 104, 123, 128, 130, 144 Subdisk 139 Support 134 Synchronous 128 Tag 97 Total FS Space 117 Type 97, 104, 123, 128, 130, 144 Volume 123, 139, 144 Web site 134 Install / Un-install 23, 35 BMC Software Installation Utility 19 Log 24 Packages 20 Procedure 24 Setup Files 21 Instance Limits

159 -K- -N- Key Performance Indicators New features 6 Node Status Configure 77 Nodes Configuring 50 FQDN 50 ID 50 Instance 50 IP Address 50 Monitoring 50 BMC ProactiveNet Performance Management 151 Manage 151 KM Initial Setup 64 Load 42, 43, 66 Preload 43 Preloaded 44, 45 Unload 43, 44, 45 KPI BMC ProactiveNet Performance Management 151 Manage 151 -L13 KM 42, 43, 66 PATROL Central Log Error Filter 43 Configure 78 Log Scan Limit Configure 80 Logs Delete Disable Enable Logs Alert -P Acknowledge Operating Systems Linux 19, 20, 24, 35 Unix 19, 20, 35 Windows 19, 20, 24, 35 Options Common services 24 Console Systems role 24 Managed System 24 View Log 24 Oracle Solaris Cluster 68 Overview 9 Parameters ExtraFilesList 134 Refresh 87 VVMDaemonCPUDuration 92 VVMDaemonCPUUtilization 92 VVMDaemonDetails 94 VVMDaemonMemorySize 92 VVMDaemonProcessCount 92 VVMDaemonState 92 VVMDaemonStatus 92 VVMDaemonSummary 92 VVMDiskdeviceDetails 108 VVMDiskdeviceIOKBytes 97 VVMDiskdeviceIOKBytesRate 97 VVMDiskdeviceIOOperations 97 VVMDiskdeviceIOOperationsFailed 97 VVMDiskdeviceIOOperationsRate MManage Baselines 151 Key Performance Indicators KPI 151 Monitoring Node 50 Remote 17 Requirements 17 Multi-Node Monitoring Mode Configure Linux Load -O-

160 VVMPlexIOOperations 123 VVMPlexIOOperationsFailed 123 VVMPlexIOOperationsRate 123 VVMPlexKernelState 123 VVMPlexKernelStateNT 123 VVMPlexKernelStatus 123 VVMPlexReadKBytes 123 VVMPlexReadKBytesRate 123 VVMPlexReadOperations 123 VVMPlexReadOperationsFailed 123 VVMPlexReadTime 123 VVMPlexReadTimeAverage 123 VVMPlexState 123 VVMPlexStateNT 123 VVMPlexStatus 123 VVMPlexSummary 123 VVMPlexWriteKBytes 123 VVMPlexWriteKBytesRate 123 VVMPlexWriteOperations 123 VVMPlexWriteOperationsFailed 123 VVMPlexWriteTime 123 VVMPlexWriteTimeAverage 123 VVMRlinkKernelState 128 VVMRlinkKernelStatus 128 VVMRlinkRemainingUpdatesCount 128 VVMRlinkRemainingUpdatesLag 128 VVMRlinkRemainingUpdatesPercent 128 VVMRlinkRemainingUpdatesSize 128 VVMRlinkState 128 VVMRlinkStatus 128 VVMRlinkSummary 128 VVMRvgKernelState 130 VVMRvgKernelStatus 130 VVMRvgRlinkCount 130 VVMRvgState 130 VVMRvgStatus 130 VVMRvgSummary 130 VVMRvgVolumeCount 130 VVMSubdiskDetails 108 VVMSubdiskIOKBytes 139 VVMSubdiskIOKBytesRate 139 VVMSubdiskIOOperations 139 VVMSubdiskIOOperationsFailed 139 VVMSubdiskIOOperationsRate 139 VVMSubdiskKernelState 139 VVMSubdiskKernelStateNT 139 VVMSubdiskKernelStatus 139 VVMSubdiskReadKBytes 139 VVMSubdiskReadKBytesRate Parameters VVMDiskdeviceQueueDepth 97 VVMDiskdeviceReadKBytes 97 VVMDiskdeviceReadKBytesRate 97 VVMDiskdeviceReadOperations 97 VVMDiskdeviceReadOperationsFailed 97 VVMDiskdeviceReadTime 97 VVMDiskdeviceReadTimeAverage 97 VVMDiskdeviceSpaceAvailable 97 VVMDiskdeviceState 97 VVMDiskdeviceStateNT 97 VVMDiskdeviceStatus 97 VVMDiskdeviceSummary 97 VVMDiskdeviceWriteKBytes 97 VVMDiskdeviceWriteKBytesRate 97 VVMDiskdeviceWriteOperations 97 VVMDiskdeviceWriteOperationsFailed 97 VVMDiskdeviceWriteTime 97 VVMDiskdeviceWriteTimeAverage 97 VVMDiskgroupDetails 108 VVMDiskgroupSpaceAvailable 104 VVMDiskgroupState 104 VVMDiskgroupStateNT 104 VVMDiskgroupStatus 104 VVMDiskgroupSummary 104 VVMDiskpathEnabled 97 VVMDiskpathKernelState 116 VVMDiskpathKernelStateNT 116 VVMDiskpathKernelStatus 116 VVMDiskpathNonEnabled 97 VVMDiskpathSummary 116 VVMLogAlarmCount 117 VVMLogAlarmText 117 VVMLogDetails 121 VVMLogFSSpaceUsedPercent 117 VVMLoginStatus 134 VVMLogSpaceAvailable 117 VVMLogSpaceGrowthRate 117 VVMLogSpaceUsed 117 VVMLogSpaceUsedPercent 117 VVMLogSummary 117 VVMLogText 117 VVMLogWarningCount 117 VVMLogWarningText 117 VVMMonitoringMode 134 VVMNodeStatus 134 VVMPlexDetails 108 VVMPlexIOKBytes 123 VVMPlexIOKBytesRate 123

161 PATROL Agent 43, 44 PATROL Agent system 17 PATROL Central Console 43, 45 PATROL Central Console Server system 17 PATROL Central Web Server system 17 PATROL Console 43, 44 PATROL Console system 17 PATROL Agent Configure 43 Restart 64 PATROL Console 42 Restart 64 Permissions Access 13 Platform Upgrade 47 Plexes Delete 71 Disable 71 Enable 71 Preload KM 43 Preloaded KM 44, 45 -RRefresh Parameters 87 Release Notes 6 Remote Monitoring 17 Requirements 17 remote PATROL Agent Checking 68 Reports Generate 86 Requirements Additional 11 BMC ProactiveNet Performance Management Portal 11 BMC Software PATROL Agent 11 BMC Software PATROL Console 11 Disk Space 17 InfoScale Foundation 11 Remote Monitoring 17 Security 13 Software Parameters VVMSubdiskReadOperations 139 VVMSubdiskReadOperationsFailed 139 VVMSubdiskReadTime 139 VVMSubdiskReadTimeAverage 139 VVMSubdiskSummary 139 VVMSubdiskWriteKBytes 139 VVMSubdiskWriteKBytesRate 139 VVMSubdiskWriteOperations 139 VVMSubdiskWriteOperationsFailed 139 VVMSubdiskWriteTime 139 VVMSubdiskWriteTimeAverage 139 VVMVolumeDetails 108 VVMVolumeIOKBytes 144 VVMVolumeIOKBytesRate 144 VVMVolumeIOOperations 144 VVMVolumeIOOperationsFailed 144 VVMVolumeIOOperationsRate 144 VVMVolumeKernelState 144 VVMVolumeKernelStateNT 144 VVMVolumeKernelStatus 144 VVMVolumeLoggingState 144 VVMVolumeLoggingStatus 144 VVMVolumeReadKBytes 144 VVMVolumeReadKBytesRate 144 VVMVolumeReadOperations 144 VVMVolumeReadOperationsFailed 144 VVMVolumeReadTime 144 VVMVolumeReadTimeAverage 144 VVMVolumeState 144 VVMVolumeStateNT 144 VVMVolumeStatus 144 VVMVolumeSummary 144 VVMVolumeWriteKBytes 144 VVMVolumeWriteKBytesRate 144 VVMVolumeWriteOperations 144 VVMVolumeWriteOperationsFailed 144 VVMVolumeWriteTime 144 VVMVolumeWriteTimeAverage 144 Paths Binary 68 Configure 68 Debug Directory 68 Home Directory 68 Library 68 Netbackup Installation 68 NetBackup Log Directory 68 Remote Temp Directory 68 PATROL

162 11 -SSecurity Requirements Setup 13 Check 64 Initial 64 KM 64 Solaris 13 Status Configure 75 Subdisks Delete 71 Disable 71 Enable 71 Sudo User 13 System HP-UX 11 IBM AIX 11 Microsoft Windows 11 Oracle Solaris 11 Red Hat Linux 11 Requirements 11 -U- Volumes Delete 71 Disable 71 Enable 71 VVM_DAEMON Application Class 92 VVM_DAEMON_CONTAINER Application Class 94 VVM_DISKDEVICE Application Class 97 VVM_DISKDEVICE_CONTAINER Application Class 102 VVM_DISKGROUP Application Class 104 VVM_DISKGROUP_CONTAINER Application Class VVM_DISKPATH Application Class VVM_LOG Configure Application Class VVM_RLINK Application Class VVM_RVG 123 Application Class VVM_SERVER Application Class VVM_SUBDISK Application Class 139 VVM_VOLUME Application Class 144 VVM_VOLUME_CONTAINER Application Class Application Class 117 VVM_LOG_CONTAINER Application Class 121 VVM_PLEX Unload KM 43, 44, 45 Upgrade Platform 47 User Account 108 -WWhat's new -VVerify Application Discovery 61 Veritas Cluster File System 68 Veritas Cluster Server Requirements Symantec NetBackup System 11 Restart PATROL Agent 64 PATROL Console 64

163 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 SOFTWARE 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 TrueSight 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. The combination of its monitoring, automation, and capacity optimization capabilities for IT Business thrives when IT runs smarter, faster and stronger. That s why the most demanding IT organizations in the world rely on BMC Software across distributed, mainframe, virtual and cloud environments. Recognized as the leader in Business Service Management, BMC offers a comprehensive approach and unified platform that helps IT organizations cut cost, reduce risk and drive business profit. For the four fiscal quarters ended September 30,2011, BMC revenue was approximately $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.