BMC ProactiveNet - Veritas Volume Manager Monitoring v3.0

BMC TrueSight OM - Veritas VolumeManager Monitoring

USER DOCUMENTATION

Version 3.0.00

January 2018

HIGH AVAILABILITY MONITORING

http://www.sentrysoftware.com

http://sentrysoftware.com/Solutions/HighAvailability_solution.asp

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

United States and Canada

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

Telephone 1 (713) 918 8800 or 1 (800) 841 2031 (Toll Free)

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

BMC Software, the BMC Software logos, and all other BMC Software product or service names areregistered 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 andconfidential. Your use of this information is subject to the terms and conditions of the applicableEnd User License Agreement for the product and the proprietary and restricted rights noticesincluded in this documentation.

Restricted Rights Legend

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

2

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

3

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Table of Contents.....................................................................................................................................................................................10System Requirements

.....................................................................................................................................................................................10Software Requirements

.....................................................................................................................................................................................11Security Requirements

.....................................................................................................................................................................................15Remote Monitoring Requirements

.....................................................................................................................................................................................18Importing the Monitoring Solution into TrueSight

.....................................................................................................................................................................................19Creating the Installation Package

.....................................................................................................................................................................................20Downloading the Installation Package

.....................................................................................................................................................................................20Installing the Package

.....................................................................................................................................................................................241. Configuring VVM Servers Monitoring

.....................................................................................................................................................................................322. Configuring Advanced Settings

.......................................................................................................................................................................................32Enabling the Debug Mode

.......................................................................................................................................................................................33Configuring the Maximum Number of Instances

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

.......................................................................................................................................................................................39Configuring the VxVM Discovery Overrides (Optional)

.....................................................................................................................................................................................403. Configuring Other Monitor Types

.......................................................................................................................................................................................41Configuring VxVM Daemons

.......................................................................................................................................................................................42Configuring VxVM Disk Devices

.......................................................................................................................................................................................44Configuring VxVM Disk Groups

.......................................................................................................................................................................................46Configuring VxVM Disk Path

.......................................................................................................................................................................................49Configuring VxVM Logs

......................................................................................................................................................................49Configuring Event Log Query Limit

......................................................................................................................................................................50Configuring Log Filter Settings

......................................................................................................................................................................52Configuring the Log Scan Limit

......................................................................................................................................................................53Configuring Custom VxVM Logs Monitoring

.......................................................................................................................................................................................53Configuring Custom VxVM Plexes

.......................................................................................................................................................................................55Configuring VxVM Replicated Volume Groups

.......................................................................................................................................................................................57Configuring VxVM Replication Links

.......................................................................................................................................................................................59Configuring VxVM Subdisks

.......................................................................................................................................................................................61Configuring VxVM Volumes

.....................................................................................................................................................................................63Blocking the Remote Monitoring

.....................................................................................................................................................................................65Configuring Monitor Thresholds

.....................................................................................................................................................................................66Editing a Threshold Configuration

4

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

.....................................................................................................................................................................................66Deleting a Threshold Configuration

.....................................................................................................................................................................................69Veritas Volume Manager KM

.....................................................................................................................................................................................70VxVM Daemon

.....................................................................................................................................................................................71VxVM Daemons

.....................................................................................................................................................................................71VxVM Disk Device

.....................................................................................................................................................................................74VxVM Disk Group

.....................................................................................................................................................................................75VxVM Disk Groups

.....................................................................................................................................................................................76VxVM Disk Path

.....................................................................................................................................................................................77VxVM Log

.....................................................................................................................................................................................78VxVM Logs

.....................................................................................................................................................................................78VxVM Plex

.....................................................................................................................................................................................81VxVM Replicated Volume Group

.....................................................................................................................................................................................82VxVM Replication Link

.....................................................................................................................................................................................83VxVM Subdisk

.....................................................................................................................................................................................86VxVM Volume

.....................................................................................................................................................................................89Managing Baselines and Key Performance Indicators

Release Notes v3.0.00

6

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Important Information

The BMC patch 11.0.00.01: Patch 1 for BMC PATROL Agent 11.0.00 must be installed to use anyversion of BMC TrueSight OM - Veritas Volume Manager Monitoring. Version 11.0.00i of thePATROL Agent on Windows prevents Veritas Volume Manager KM from operating properly.While apparently successfully loaded, Veritas Volume Manager KM fails to start and can neithermonitor 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.

VVM-272: The monitoring of any additional log file can now be configured in TrueSight. The logfilter can also be customized to indicate when Warnings and Alarms are triggered.

Changes and Improvements

VVM-241: Veritas Volume Manager 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 significantly improved.

VVM-337: The path discovery has been improved in order to support variations to binary andlibrary paths.

Fixed Issues

VVM-223: Handling large values in stats attributes: When the cumulative I/O stats returnedby Veritas Volume Manager commands became too large (more than 231), the relatedattributes failed and stopped collecting data. Thus, metrics for rate-based attributes such asRead KBytes Rate, Write KBytes Rate, IO KBytes Rate were not properly reported for volumes,plexes, disks devices and subdisks. The product now stores the actual read, write or total I/Ocollected since the last collection cycle to avoid values reported by these attributes to growcumulatively and to reach their limitation.

VVM-330: Veritas Volume Manager KM experienced a discovery failure due to a missing VxVMlibrary path.

Known Issues

VVM-291: On BMC Portal v2.9, volumes (in disk groups) may not be collected by the VeritasVolume Manager KM integration par file. Also, due to hierarchical changes implemented inBMC TrueSight OM - Veritas Volume Manager Monitoring v3.0.00, migration from versions 2.xis not possible.

https://docs.bmc.com/docs/PATROLAgent/110/11-0-00-01-patch-1-for-bmc-patrol-agent-11-0-00-784075031.html

Overview

8

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

BMC TrueSight OM - Veritas Volume Manager Monitoring provides current and historicalinformation through a centralized console so you can easily view and manage your entire VeritasVolume Manager environment. The product collects and brings critical performance data anduseful metrics into the BMC TrueSight environment and enables SAN Administrators to be warnedwhenever a problem occurs in their Veritas Volume Manager environment.

Veritas Volume Manager KM monitors the following components:

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

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

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

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

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

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

BMC TrueSight OM - Veritas Volume Manager Monitoring:

Enhances productivity

Ensures availability of all components of Veritas Volume Manager (disks, paths, volumes,replicated volume groups, replication links, plexes and subdisks)

Collects I/O metrics at different layers to pinpoint any performance bottleneck

Maintains integrity.

Requirements

10

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Before installing the Veritas Volume Manager KM, verify the:

system requirements

software requirements

security requirements

remote monitoring requirements.

System RequirementsBMC TrueSight OM - Veritas Volume Manager Monitoring supports the following operatingsystems:

Operating System Operating System Version

Microsoft Windows Microsoft Windows Server 2003, 2008, 2012 and all versions supported byBMC 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.

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

Software Requirements

BMC TrueSight OM - Veritas Volume Manager Monitoring supports:

Software Version

Veritas Volume Manager™ (included in InfoScaleFoundation Suites)

5.0, 5.1, 6.x, 7.x

BMC Software PATROL Agent Any version

BMC Software PATROL Console Any version

BMC Portal v2.3 and higher

BMC ProactiveNet Performance Manager v9.5 and higher

BMC TrueSight Operations Management v10.x and higher

11 Software Requirements

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

If the operating system is upgraded (or downgraded) at a later date, you will need to reloadcommands for the Veritas Volume Manager KM.

Additional Software Requirements

The following table contains a list of additional software requirements of BMC TrueSight OM -Veritas Volume Manager Monitoring:

Purpose Software Version

When running Veritas Volume Manager KMwith sudo user account on Solaris, HP-UX,AIX or Linux managed nodes

Sudo (superuser do) 1.6.7 or later

When running Veritas Volume Manager KMon Linux managed nodes

Korn shell binary (/bin/ksh) Any

When running Veritas Volume Manager KMon Microsoft Windows x64 managed nodes

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

Any

The Microsoft Windows x64 Reg.exe patch, KB948698 is required to allow access to 64-bit registrykeys from PATROL Agent. Access the above patch site from the managed node to obtain the correctpatch for that platform.

Security RequirementsA user account with administrative privileges must be configured in BMC PATROL to read andexecute Veritas Volume Manager application programs and access file systems. Depending on theoperating systems used, several options will be available.

The following user accounts can be used:

On Unix platforms:

a root user

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

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

On Windows platforms:

an administrator user

a non-administrator account, such as patrol, configured in Veritas Volume Managerapplication 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

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

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

12Security Requirements

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

DES encrypted format.

Access Permissions

The Veritas Volume Manager KM user needs “read & execute” permission to executable and libraryfiles 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 Veritas Volume Manager 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 executepermissions to the following cluster commands:

/opt/VRTSvxvm/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 Veritas Volume Manager KM includes some scripts which should be executable by the PATROLAgent user and the Veritas Volume Manager KM user. These scripts are stored under KM_HOMEpath, normally PATROL_HOME/lib/VVM.

In addition to these Veritas Volume Manager commands, Veritas Volume Manager KM executes otheroperating system commands, such as ps, uname which may not require special privileges.

To list all OS commands used by the Veritas Volume Manager KM, execute the following PSL codefrom 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)

13 Security Requirements

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

{ 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=""; } 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 pathsand 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 pathusing the configured login account, and processed by the PATROL Agent user. On completion thecopied log file will be removed. This may increase the file system usage under KM_TEMP temporarilyduring this activity.

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

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

Sudo User for Operating System Access

If a non-root user with sudo privileges is preferred as the Veritas Volume Manager KM user,configure the account as a sudoer through the visudo utility using code appropriate for yourplatform as detailed below. This user should be able to execute VxVM commands and OScommands.

The code below also applies to all non-root users who may execute Veritas Volume Manager KMadministration and report menu commands using their sudo privileges. The KM accepts any non-

14Security Requirements

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

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 pathINSTALL_PATH, referenced below is normally /opt/VRTS and PATROL_HOME is the path where thePATROL Agent is installed (including the target, like /opt/bmc/Patrol3/Solaris29-sun4/).

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

Entering the non-root sudo user with ‘Use Sudo’ option selected in to the login configuration dialog,before updating the sudoers file, will generate sudo errors. Also if the sudo user is configureddifferently, the KM may run sudo commands using incorrect sudo settings, which may expose thesudo user password.

On Solaris:User_Alias VVMKMUSERS = user1, user2, user3Defaults:VVMKMUSERS !lecture,!authenticate,!requiretty,\env_keep+="PATH LD_LIBRARY_PATH INSTALL_PATH KM_HOME KM_TEMP",env_resetVVMKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\INSTALL_PATH/bin/*,\PATROL_HOME/lib/VVM/*,PATROL_HOME/bin/*

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

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


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


15 Remote Monitoring Requirements

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Remote Monitoring RequirementsRemote monitoring is required for all servers or appliances on which no PATROL Agent can beinstalled. This feature is also interesting if you lack resources or time to deploy a PATROL Agent andVeritas Volume Manager KM on several servers since it allows to monitor multiple hosts from oneagent.

Remote monitoring is not possible from a UNIX/Linux PATROL Agent system to a Windows-basedVVM server.

The requirements listed below must be met to be able to use remote monitoring.

JAVA

Veritas Volume Manager KM requires Java 1.8 and a Java Runtime Environment (JRE) to be installedon the same system that runs the PATROL Agent.

The KM will automatically detect the JRE path if it has been installed in the default location orunder the BMC PATROL Agent installation path. If it has been installed in a different location, youwill have to set JAVA_HOME for the Patrol Agent default account before starting the PATROLAgent.

You can download the Java Runtime Environment along with the KM on the Sentry Softwarewebsite.

SSH/WMI Connection

An SSH (UNIX/Linux platforms) or a WMI (Windows platforms) connection is required to monitorremote Veritas Volume Manager nodes. When using an SSH connection, the SSH host keyauthentication 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 theremote host

2. Add the line StrictHostKeyChecking no

3. Save the file.

http://www.sentrysoftware.com/Products/SymantecNetBackupKM_Downloads.asp

http://www.sentrysoftware.com/Products/SymantecNetBackupKM_Downloads.asp

Installing the Monitoring Solution

17

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Once the latest version of the solution has been loaded into TrueSight Presentation Server,administrators can create all the installation packages required for their different operatingsystems and platforms and save them for later use in the Monitoring Installation Packages list.These packages can then be deployed to multiple computers. Administrators just have to connectto TrueSight Presentation Server from the server where they want to install the package, downloadit and launch the installation.

This section describes the different steps to follow to install Veritas Volume Manager KM:

Importing Veritas Volume Manager KM into TrueSight Presentation

Creating the Installation Package

Downloading the Installation Package

Installing the Package

18

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Importing the Monitoring Solution intoTrueSightThe TrueSight Central Monitoring Repository includes the current versions of BMC TrueSight OM -Veritas Volume Manager Monitoring that you can use with BMC TrueSight. If the version availablein the Repository does not correspond to the latest one, you will have to manually import it:

1. Log on to the TrueSight Console.

2. From the navigation pane, select Administration > Repository.

3. Click the Installation Components tab.

4. Check that the version of the BMC component available is actually the latest one. If not,download the latest version corresponding to your operating system (Windows or UNIX/Linux)available on the Sentry Software Website.

5. Click Import.

6. Select Single solution.

7. Browse to the .zip source file.

8. Click Import.

The selected archive file is imported to the repository.

http://www.sentrysoftware.com/support/product-lifecycle.asp

19 Importing the Monitoring Solution into TrueSight

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Creating the Installation PackageThe installation package to deploy to managed systems can be created directly from TrueSightPresentation Server:

1. Log on to the TrueSight Console.


3. Click the Deployable Packages tab.

4. Click Create Deployable Package.

5. Select the operating system and platform for which you want to create a package. Thecomponents available in the repository for the selected operating system and platform aredisplayed.

6. Select the solution(s) to be included in the package, specify their version, and click Next.

7. Specify the Installation Directory and click Next.

8. Provide the PATROL 3.x Product Directory and click Next.

9. Specify the BMC Product Startup Information and click Next.

10. Provide the following information:

Name: Enter a unique name for the package.

(Optional) Description: Enter a description of the package.

Format: Select a file compression format for the package.

9. Click Save.

10. Click Close. The package is now available in the Deployable Packages list.

20Creating the Installation Package

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Downloading the Installation PackageYou can download an installation package and install the components on one or more hosts. Theinstallation runs silently with the information entered during package creation.

1. Log on to the TrueSight Console from the computer on which the PATROL Agent is installed orto be installed.


3. Click the Deployable Packages tab.

4. (Optional) To filter the list of installation packages, select an operating system .

5. Click the action menu for the installation package required and click Download.

6. Save the installation package.

Installing the PackageThis chapter provides a step by step procedure to install a monitoring solution package:

1. Download the installation package.

2. Extract the installation package that is appropriate for your operating system. The package isextracted to the bmc_products directory on the current host.

3. From the bmc_products directory, run the installation utility for your operating system:

(UNIX or Linux) RunSilentInstall.sh

(Microsoft Windows) RunSilentInstall.exe

The package is installed on the current host..

Configuring After Installation

22

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Once Veritas Volume Manager KM is installed, you will have to configure the VxVM Monitor Typesthrough policies. Policies enable you to deploy configurations on PATROL Agents and monitoringsolutions, such as Veritas Volume Manager KM in an automated way. Policies are designed todefine and configure monitoring criteria and apply them to the specified PATROL Agents. Theconfiguration criteria are automatically pushed to the PATROL Agents on which the policy isapplied. When a monitoring policy is applied to a PATROL Agent, the device is automatically addedto the list of monitored devices.

To create a monitoring policy1. Log on to the TrueSight console.

2. In the navigation pane, expand Configuration and select Infrastructure Policies.

3. In the Infrastructure Policies page, ensure that the Monitoring tab is selected and click CreatePolicy.

4. In the Create Monitoring Policy page, specify the monitoring policy properties:

Step 1 - Define the General Properties

Property Description

Name Name for the policy. The policy names must be unique. In an environment with tenants,the policy names must be unique for a single tenant. It is a mandatory field.

Description (Optional) A brief description about the policy.

Associated UserGroup

Name of the user group that is associated with the PATROL Agents as defined in theAuthorization Profile or in the PATROL Agent ACLs. The policy is applicable to thesePATROL Agents.

Share with UserGroup

Specify whether this policy is to be shared with the users across the associated user groupor not. This property can be viewed in READ-ONLY mode by other users of the associateduser group. Only the owner of the policy can modify this property.

Precedence Priority of the policy. Based on the precedence number that you configure, theconfiguration is applied to the PATROL Agents and the Infrastructure Management servers.The precedence number ranges from 0 to 999. A lower number indicates a higherprecedence. The default value is 900.The configuration from a policy with a higher precedence overrides the configuration froma policy with a lower precedence. If two policies have the same precedence number, thenthe configuration from the latest created policy takes priority.

Enable Policy Indicates whether the policy is enabled or disabled. By default, the policy is disabled. If youdo not enable a policy when you create it, the policy configurations are not applied to thePATROL Agents and the Infrastructure Management Servers. If you disable any existingpolicy, the policy configurations are removed from the PATROL Agents and theInfrastructure Management servers, where the policy was applied.

Step 2 - Select the PATROL AgentsDefine conditions to select the PATROL Agents on which you want to apply the policy:

23

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

1. Select a property.

2. Select an operator to create the condition. The available operators depend on the propertythat you select.

3. Specify a value for the selected property.

4. (Optional) To add more than one condition, click the button, and perform the earlier steps.

5. (Optional) To group the conditions, use the parentheses and Boolean operators from theircorresponding lists.

The Add Monitor Types dialog box presents configuration fields for compatible BMC PATROLmonitoring solutions that are located in the Central Monitoring Repository.

Step 3 - Select the Required Monitor Type1. Click the Monitoring tab.

2. Click Add Monitoring Configuration.

3. In the Add Monitoring Configuration dialog box, configure the properties:

From the Monitoring Solution menu, select Veritas Volume Manager.

From the Version menu, select the required version.

The Monitor Profile Veritas Volume Manager KM is automatically selected.

Selecting the Required Monitor Type

Refer to the table below to know which monitor types are available and their function

Monitor Type Description

Veritas VolumeManager KM(MANDATORY)

To set the general settings of the Veritas Volume Manager monitoring solution(credentials, debug mode, instances, multi-node mode, etc.).

Once this monitor type is configured, all other monitor types are automaticallymonitored. Their default behavior can however be modified by selecting themfrom the Monitor Type list. No other monitor types can be configured as long asVeritas Volume Manager KM is not configured.

VxVM Daemons To set filtering options for configuring the monitoring of VxVM Daemons.

VxVM DiskDevices

To set filtering options for configuring the monitoring of VxVM Disk Devices.

VxVM Disk Groups To set filtering options for configuring the monitoring of VxVM Disk Groups.

VxVM Disk Path To set filtering options for configuring the monitoring of VxVM Disk Paths.

24

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


VxVM Logs To set the log files to be monitored, the error messages present in the VxVM daily logor any other additional log file that will trigger warnings or alarms, and the amount ofdata scanned by Veritas Volume Manager KM during each data collection cycle.

VxVM Plexes To set filtering options for configuring the monitoring of VxVM Plexes.

VxVM ReplicatedVolume Groups

To set filtering options for configuring the monitoring of VxVM Replicated VolumeGroups.

VxVM ReplicationLinks

To set filtering options for configuring the monitoring of VxVM Replication Links.

VxVM Subdisks To set filtering options for configuring the monitoring of VxVM Subdisks.

VxVM Volumes To set filtering options for configuring the monitoring of VxVM Volumes.

Step 4 - Configure the Selected Monitor Type1. Depending on the selected Monitor Type, the available fields will vary. Refer to appropriate

section to know how to configure them.

2. Click Save to apply your changes to the selected PATROL Agent(s).

To edit a monitoring policy1. Log on to the TrueSight console.

2. In the navigation pane, expand Configuration and select Infrastructure Policies.

3. In the Infrastructure Policies page, locate the monitoring policy you wish to modify, click its

action button and click Edit.

4. In the Edit Monitoring Policy page, locate the monitoring configuration you wish to modify and

click its action button to access the monitoring options panel.

5. Customize the configuration.

6. Click Save to apply your changes to the selected PATROL Agent(s).

1. Configuring VVM Servers MonitoringBefore using Veritas Volume Manager KM, you need to configure the monitoring settings for theVeritas Volume Manager KM Monitor Type. You will then be able to create and customize otherMonitor Types according to the component(s) you wish to monitor.

To configure the Veritas Volume Manager KM monitoring settings

Specify the options that will constitute the Veritas Volume Manager monitoring settings.

1. Create your monitoring policy.


From the Monitoring Solution menu, select Veritas Volume Manager

25 1. Configuring VVM Servers Monitoring

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

From the Version menu, select the required version

The Monitor Profile Veritas Volume Manager KM is automatically selected

3. In the VxVM Monitoring Settings section, click Add.

4. Specify the VxVM System to be monitored:

In the Hostname field:

· for a local host, enter localhost to apply these settings to all PATROL Agents installed onthe VxVM Servers

· for a remote host, enter a hostname or IP address to apply these settings to a specificserver

Click the Create a Device in the Console box if you want the VVM server to appear as aseparate device in TrueSight.

Adding a Veritas Volume Manager Host to the Monitoring Environment

5. Set the VxVM Credentials:

To use the default PATROL Agent Account, check the Use Agent Default Account option

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

(Unix Only) If the user account has sudo privileges, check the Use Sudo box and indicate thesudo binary file path (by default: /usr/local/bin/sudo) menu, select Veritas Volume ManagerKM

Configuring Veritas Volume Manager User Account

261. Configuring VVM Servers Monitoring

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

6. (Optional - Remote Monitoring Only) Set the Remote Connection Settings:

Configuring the Remote Connection Settings

In the Connection Timeout (in Seconds) field, enter the number of seconds after which theconnection to the remote node will time out

In the Maximum Connections field, enter the maximum number of simultaneousconnections allowed to the remote node

7. (Optional) Define the Advanced Settings:

the debug mode

the maximum number of instances

the multi-node monitoring mode

the VxVM discovery overrides.

8. Click OK twice.

9. Click Save.

Best Practices for Monitoring Veritas Volume Manager in a Cluster

Since version 3.0.00, different methods exist to monitor multiple cluster nodes with Veritas VolumeManager KM:

1. The remote monitoring method through the virtual cluster IP: the KM remotely monitors theentire 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 needto be installed on a central host and the KM needs to be configured to monitor nodesremotely.

3. The local monitoring method: the PATROL Agent and the KM need to be installed on all themanaged nodes.

4. A mixed method (local and remote monitoring): the PATROL Agent and the KM are installedon 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 thissection. An article detailing the procedure for local monitoring and mixed method is available onSentry's website. Although the article refers to Veritas Cluster Server KM for PATROL, themonitoring concepts and principles remain valid for Veritas Volume Manager KM, see


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Configuring the Multi-node Monitoring Mode with the VCS KM.

Remote Monitoring Through the Virtual Cluster IP

This method allows you to monitor the entire cluster through the virtual cluster IP or the hostnameassociated to the virtual IP. A central non-cluster node on which the PATROL Agent and the KM areinstalled 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

2. Create your monitoring policy.



From the Version menu, select the latest version


https://www.sentrysoftware.com/kb/KB1211.asp


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

4. In the VxVM Monitoring Settings section, click Add.

5. In the VxVM System section, enter a virtual IP or the hostname associated to the virtual IP.

6. Set the VxVM Credentials.

7. Make sure Enable Multi-node Monitoring Mode is unchecked.

8. Click OK twice.

9. Click Save.

10. Make sure the policy is deployed to the PATROL Agent (in our example: rt-patrol-agent) wherethe solution monitors Veritas Volume Manager in the cluster through the virtual cluster IPremotely in Single-node Mode.

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 Veritas Volume Manager KM need to be installed on the non-cluster node. In our example, we have two VCS nodes, sof ia and bucharest. They are bothmonitored remotely from rt-patrol-agent, a host outside the cluster on which the PATROL Agentand VCS KM 3.0.00 have been installed.

Remote Monitoring From a Non-Cluster Node - Diagram

To monitor Veritas Volume Manager in this VCS cluster remotely from a PATROL Agent nodeoutside the cluster:

1. Configure the monitoring of one of the cluster node running the VxVM (in our example: sof ia):

Create your monitoring policy

In the Add Monitoring Configuration dialog box, configure the properties:


From the Version menu, select the latest version


In the VxVM Monitoring Settings section, click Add

Provide the hostname or IP address of the VxVM system to be monitored

Set the VxVM Credentials

Click OK.


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

2. Repeat the same procedure for other cluster nodes running VxVM (in our example: bucharest).

3. Click OK and Save.

4. Make sure the policy is deployed to the PATROL Agent on the non-cluster node (in ourexample: rt-patrol-agent).

5. Wait for the KM to create the instances in Permanent Single-node Mode on both managednodes.

6. Configure the multi-node monitoring:

Edit your monitoring policy

Click the action button of the VxVM system for which you wish to configure the multi-node monitoring mode and click Edit

Check the Enable Multi-node Monitoring Mode option in the Advanced section andconfigure the Multi-node Mode

From the Cluster Application pull-down list, select appropriate cluster application. In ourexample, Veritas Cluster Server

In the Failover Group Name field, enter the failover group name, which is online on onecluster node and offline on the others. In our example: ClusterService

Make sure the Enable Remote PATROL Agent Checking box is unchecked

Remote Monitoring from a Non-Cluster Node – Configuring the Multi-node Monitoring


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

7. In the Monitoring Nodes section:

Click Add to configure the nodes to be monitored

Provide the PATROL Agent Hostname (host where the PATROL agent is installed; in ourexample: rt-patrol-agent), the Server ID (a unique ID for the VxVM node; in our example:sof ia), and Cluster Node Name (the hostname defined in VCS; in our example: sof ia).

Click OK

Repeat the procedure for each VxVM node in the policy that is part of the Multi-node modeconfiguration (in our example: bucharest).

In our example, we configured the monitoring nodes sof ia and bucharest as follows:

Remote Monitoring from a Non-Cluster Node – Configuring the sofia and bucharest Nodes Monitoring

8. Click OK and Save.

The monitoring policy should like this: two managed nodes (sof ia and bucharest) in same multi-node configuration without remote PATROL Agent checking.


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Remote Monitoring from a Non-Cluster Node – Monitoring Policy


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

2. Configuring Advanced SettingsThis section describes the following advanced settings:

Enabling the Debug Mode

Configuring the Maximum Number of Instances

Configuring the Multi-Node Monitoring Mode

Configuring the VxVM Discovery Overrides (Optional)

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

To enable the debug mode1. Edit your monitoring policy.

2. Click the action button of the VVM system for which you wish to enable the Debug Mode andclick Edit.

3. In the VxVM Monitoring Settings panel, scroll down to the Debug section.

4. Select all the elements for which you want to obtain debug information.

Configuring the Debug Mode Settings

4. In the Options section, indicate:

when the system must stop logging debug information. The required format is: YYYY/MM/DD

33 2. Configuring Advanced Settings

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

HH:MM:SS

where the debug file will be stored. The default path is: <PATROL_HOME>/lib/VxVM/debug

Setting the Debug End Time and Directory Path

5. Click OK to validate.

When the debug end time is reached, a tar/zip file is automatically created under <PATROL_HOME>/lib/VVM/ and can be sent to the BMC Support for help. It is also recommendedto check the VVM_<port>.log file, stored in <PATROL_HOME>/log, for any error.

Configuring the Maximum Number of InstancesBy default, the solution discovers and monitors all the instances. Because there may be a very largenumber of instances to monitor and this may represent a important workload to the agents and theBMC TrueSight servers, it is recommended to only monitor the critical ones. This can be done byconfiguring the instance limits.

342. Configuring Advanced Settings

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

To configure the maximum number of instances1. Edit your monitoring policy.

2. Click the action button of the VVM system for which you wish to configure the maximumnumber of instances and click Edit.

3. In the VxVM Monitoring Settings panel, scroll down to the Maximum Number of Instancessection.

4. For each monitored element, indicate the maximum number of instances to be displayed, orenter 0 in the relevant field to disable the monitoring of a specific element. (By default, themaximum number of instances is left empty to allow an unlimited number of instances).

Configuring the Maximum Number of Instances

5. Click OK twice.

6. Click Save.


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Configuring the Multi-Node Monitoring ModeIf the Veritas Volume Manager environment is installed in a cluster using Veritas Cluster Server,Veritas Cluster File System, Oracle Solaris Cluster, or Microsoft Cluster, the Veritas VolumeManager KM must be installed on all the cluster nodes to enable continuous monitoring and avoidsingle point of failure. To avoid duplicate alerts from multiple nodes, it is recommended toconfigure the solution to 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 toVeritas Cluster Server KM for PATROL, the monitoring concepts and principles remain valid forVeritas Volume Manager for PATROL.

To configure the multi-node monitoring mode1. Edit your monitoring policy.

2. Click the action button of the VVM system for which you wish to configure the multi-nodemonitoring mode and click Edit.

3. In the VxVM Monitoring Settings panel, scroll down to the Multi-node Monitoring Modesection.

Configuring the Multi-Node Mode

https://www.sentrysoftware.com/kb/KB1211.asp


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

3. Check the Enable Multi-node Monitoring Mode option.

4. Configure the Multi-node Mode:

Select the appropriate Cluster Application

Indicate the Failover Group Name. Leave this field blank if you have previously selectedVeritas Cluster File System. Then the Veritas Volume Manager KM will then monitor theVeritas Volume Manager from the active master system, which is identified by “vxdctl -cmode” command. This method requires vxconfigd in enable mode with its clustered stateactive

5. (Optional) Check the Enable Remote PATROL Agent Checking option to allow the solution tocheck the monitoring mode of the remote PATROL Agents. If the Remote PATROL AgentChecking is disabled, the solution will monitor actively through active cluster node or on thenode where failover group is online and will not check the monitoring status of the VeritasVolume Manager KM on the other PATROL Agent nodes.

6. In the Monitoring Nodes section:

Click Add to configure the details of all managed nodes of the cluster to be configured in themulti-node mode

Provide the PATROL Agent Hostname (host where the PATROL agent is installed), the SystemID (the unique ID of the VVM node derived from the hostname in the VxVM Systemconfiguration), and Cluster Node Name (the hostname defined in the selected ClusterApplication)

Click OK

Repeat the procedure for each VxVM node that is part of the multi-node mode configuration


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

7. If the Enable Remote PATROL Agent Checking option is selected, click Add in the RemoteAgent Configuration section, to provide all the information required to communicate with thePATROL Agents. There should be one entry per each PATROL Agent.

Identifying the Node to Monitor

Provide the PATROL Agent Hostname

Select the Protocol you wish to use to connect to the PATROL Agent

Enter the Port number you wish to use to connect to the PATROL Agent

Provide the Username and Password you wish to use to connect to the PATROL Agent

In the Number of Attempts field, specify the number of times the solution will try tocommunicate with the remote PATROL Agent before failing over

Enter the timeout you wish to set, in seconds, between each attempt

7. Click OK twice.

8. Click Save.

The Veritas Volume Manager will then be monitored through the master or online node in ActiveMulti-node Mode. The other nodes, which are standing by for a failover, will be in Passive Multi-node Mode, monitoring only the components that are not visible from the active node.


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

If a managed node is unable to check the monitoring status of the active managed node, it willchange to Temporary Single-node Mode allowing a full VxVM monitoring. It will remain inTemporary 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 Agentinvolved, the managed node on the master or online node will be in Active Multi-node Mode andall others will be in Passive Multi-node Mode, without checking the monitoring status of the activenode. In addition, the above procedure to configure Multi-node Mode needs to be repeated fromeach PATROL Agent involved.


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Configuring the VxVM Discovery Overrides

(Optional)The solution automatically discovers the Veritas Volume Manager installation, the temporarydirectory paths used by the VVM KM, and the node status. This information can however beoverridden.

Altering these paths may impact the operation of Veritas Volume Manager KM.

To configure Veritas Volume Manager server discovery overrides1. Edit your monitoring policy.

2. Click the action button of the VVM system for which you wish to configure the discoveryoverrides and click Edit.

3. In the VxVM Monitoring Settings panel, scroll down to the Discovery Overrides section.

Configuring Veritas Volume Manager Discovery Overrides


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

3. Specify the VxVM System Discovery Overrides options:

VxVM Installation Path: Provide the path to the directory where the Veritas VolumeManager software is installed. By default, Veritas Volume Manager KM automatically locatesthe Veritas Volume Manager software installation directory if you have installed the solutionwith the default recommended settings. If you have chosen to install the solution in a customdirectory, you are required to provide its location.

Remote Temp Directory Path: Provide the path to the directory where the temporary filesare saved on remote nodes (Default is /var/temp for UNIX/Linux or C:\Windows\Temp forWindows).

Local Temp Directory Path: Provide the path to the directory where the temporary files aresaved on the PATROL Agent node (Default is <PATROL_HOME>/lib/VVM/tmp wherePATROL_HOME is the PATROL Agent installation path)

Node Status Daemons: Specify the critical Veritas Volume Manager node daemons in orderto detect the node status. Daemon names must be comma-delimited.

5. Click OK twice

6. Click Save.

3. Configuring Other Monitor TypesOnce the Veritas Volume Manager KM monitor type is properly configured, you can create andcustomize the following Monitor Types, according to the component(s) you wish to monitor.

These configuration steps are optional. The monitor types below are automatically discovered andmonitored using defaults settings.


VxVM Deamons To set filtering options for configuring the monitoring of VxVM Daemons.

VxVM DiskDevices

To set filtering options for configuring the monitoring of VxVM Disk Devices.

VxVM Disk Groups To set filtering options for configuring the monitoring of VxVM Disk Groups.

VxVM Disk Path To set filtering options for configuring the monitoring of VxVM Disk Paths.

VxVM Logs To set the log files to be monitored, the error messages present in the VxVM daily logor any other additional log file that will trigger warnings or alarms, and the amount ofdata scanned by Veritas Volume Manager KM during each data collection cycle.

VxVM Plexes To set filtering options for configuring the monitoring of VxVM Plexes.

VxVM ReplicatedVolume Groups

To set filtering options for configuring the monitoring of VxVM Replicated VolumeGroups.

VxVM ReplicationLinks

To set filtering options for configuring the monitoring of VxVM Replication Links.

VxVM Subdisks To set filtering options for configuring the monitoring of VxVM Subdisks.

41 3. Configuring Other Monitor Types

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


VxVM Volumes To set filtering options for configuring the monitoring of VxVM Volumes.

Configuring VxVM DaemonsBy default, the solution monitors all the Veritas Volume Manager daemons discovered, which mayrepresent an important workload for the Agents and the TrueSight OM servers. Because themonitoring of some VxVM daemons may be irrelevant for various reasons, you can apply filters tospecify the VxVM daemons that will be monitored or discarded.

To configure VxVM daemons1. From the Add Monitoring Configuration panel, select VxVM Daemon from the Monitor Type

list.

2. In the VxVM Daemons panel, click Add.

Configuring VxVM Daemons

423. Configuring Other Monitor Types

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

3. In the Hostname field, enter:

localhost to apply these settings to all PATROL Agents installed on the VxVM Server

a hostname or IP address to apply these settings to a specific server.

4. Configure the Filtering options:

In the Keep Only Daemons section, click Add and identify the VxVM daemon you wish tomonitor. Enter the name of the VxVM daemon or identify it by using a regular expression(example: v̂x). Click OK to validate. Repeat the operation for any other VxVM daemon youwish to include in the monitoring process

In the Exclude Daemons section, click Add and identify the VxVM daemon you do not wantto monitor. Enter the name of the VxVM daemon or identify it by using a regular expression(example:vxprint). Click OK to validate. Repeat the operation for any other VxVM daemonyou wish to exclude from the monitoring process

5. The Additional Daemons (manual discovery) section allows you to add VxVM daemonsmanually, when they are not automatically discovered:

Click Add and enter the name of the VxVM daemon you wish to add to the monitoringenvironment. Click OK to validate. Repeat the operation for each VxVM daemon you want tomonitor

(Optional) Enter a short description that will allow you to quickly identify the added VxVMdaemon


Configuring VxVM Disk DevicesBy default, the solution monitors all the Veritas Volume Manager disk devices discovered, whichmay represent an important workload for the Agents and the TrueSight OM servers. Because themonitoring of some VxVM disk devices may be irrelevant for various reasons, you can apply filtersto specify the VxVM disk devices that will be monitored or discarded.


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

To configure VxVM disk devices1. From the Add Monitoring Configuration panel, select VxVM Disk Devices from the Monitor

Type list.

2. In the VxVM Disk Device panel, click Add.

Configuring VxVM Disk Devices


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00





In the Keep Only Disk Devices section, click Add and identify the VxVM disk device you wishto monitor. Enter the name of the VxVM disk device or identify it by using a regularexpression (example: prod-diskdevice*). Click OK to validate. Repeat the operation for anyother VxVM disk device you wish to include in the monitoring process

In the Exclude Disk Devices section, click Add and identify the VxVM disk device you do notwant to monitor. Enter the name of the VxVM disk device or identify it by using a regularexpression (example: test-diskdevice*). Click OK to validate. Repeat the operation for anyother VxVM disk device you wish to exclude from the monitoring process

5. The Additional Disk Devices (manual discovery) section allows you to add VxVM disk devicesmanually, when they are not automatically discovered:

Click Add and enter the name of the VxVM disk device you wish to add to the monitoringenvironment. Click OK to validate. Repeat the operation for each VxVM disk device you wantto monitor

(Optional) Enter a short description that will allow you to quickly identify the added VxVMdisk device


Configuring VxVM Disk GroupsBy default, the solution monitors all the Veritas Volume Manager disk groups discovered, whichmay represent an important workload for the Agents and the TrueSight OM servers. Because themonitoring of some VxVM disk groups may be irrelevant for various reasons, you can apply filtersto specify the VxVM disk groups that will be monitored or discarded.


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

To configure VxVM disk groups1. From the Add Monitoring Configuration panel, select VxVM Disk Groups from the Monitor

Type list.

2. In the VxVM Disk Group panel, click Add.

Configuring VxVM Disk Groups


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00





In the Keep Only Disk Groups section, click Add and identify the VxVM disk group you wishto monitor. Enter the name of the VxVM disk group or identify it by using a regularexpression (example: prod-diskgroup*). Click OK to validate. Repeat the operation for anyother VxVM disk group you wish to include in the monitoring process

In the Exclude Disk Groups section, click Add and identify the VxVM disk group you do notwant to monitor. Enter the name of the VxVM disk group or identify it by using a regularexpression (example: test-diskgroup*). Click OK to validate. Repeat the operation for anyother VxVM disk group you wish to exclude from the monitoring process

5. The Additional Disk Groups (manual discovery) section allows you to add VxVM disk groupsmanually, when they are not automatically discovered:

Click Add and enter the name of the VxVM disk group you wish to add to the monitoringenvironment. Click OK to validate. Repeat the operation for each VxVM disk group you wantto monitor

(Optional) Enter a short description that will allow you to quickly identify the added VxVMdisk group


Configuring VxVM Disk PathBy default, the solution monitors all the Veritas Volume Manager disk paths discovered, which mayrepresent an important workload for the Agents and the TrueSight OM servers. Because themonitoring of some VxVM disk paths may be irrelevant for various reasons, you can apply filters tospecify the VxVM disk paths that will be monitored or discarded.


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

To configure VxVM disk paths1. From the Add Monitoring Configuration panel, select VxVM Disk Paths from the Monitor

Type list.

2. In the VxVM Disk Path panel, click Add.

Configuring VxVM Disk Path


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00





In the Keep Only Disk Paths section, click Add and identify the VxVM disk path you wish tomonitor. Enter the name of the VxVM disk path or identify it by using a regular expression(example: prod-diskpath*). Click OK to validate. Repeat the operation for any other VxVMdisk path you wish to include in the monitoring process

In the Exclude Disk Paths section, click Add and identify the VxVM disk path you do not wantto monitor. Enter the name of the VxVM disk path or identify it by using a regular expression(example: test-diskpath*). Click OK to validate. Repeat the operation for any other VxVM diskpath you wish to exclude from the monitoring process

5. The Additional Disk Paths (manual discovery) section allows you to add VxVM disk pathsmanually, when they are not automatically discovered:

Click Add and enter the name of the VxVM disk path you wish to add to the monitoringenvironment. Click OK to validate. Repeat the operation for each VxVM disk path you wantto monitor

(Optional) Enter a short description that will allow you to quickly identify the added VxVMdisk path



BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Configuring VxVM LogsBy default, Veritas Volume Manager KM monitors the following log files:

A log filter is configured by default for the above log files to ensure warnings or alarms aretriggered when a specific error message is found. This default configuration can however bemodified in TrueSight if you need to monitor:

error messages that are not included in the default filter. You will then have to customize thelog filter

any other log, such as Windows System Event Logs. In that case, you will have to:

specify the custom logs to be monitored

and customize the log filter to indicate the regular expressions that will generate a warningand/or an alarm.

Configuring Event Log Query LimitBy default, Veritas Volume Manager KM limits the time allocated to execute event queries to 300minutes during each data collection cycle. This limit can however be modified to better suit yourrequirements.

Increasing the Event Log Query Limit may impact the performance of the data collector(VVMLogCollector), the KM, and the PATROL Agent.


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

To configure Veritas Volume Manager logs query limit1. From the Add Monitoring Configuration panel, select VxVM Logs from the Monitor Type list.

2. In the Event Log Query Limit panel, click Add.

Configuring Veritas Volume Manager Logs Query Limit


localhost to apply these settings to all PATROL Agents installed on Veritas Volume ManagerServers

a hostname or IP address to apply these settings to a specific server

4. In the Query Limit field, indicate the time (in minutes) you wish to allocate for executing eventlog queries during each data collection cycle.

5. Click OK twice

5. Click Save.

Configuring Log Filter SettingsBy default, Veritas Volume Manager KM only monitors the daily Veritas Volume Manager messagesfile and the system log file. A log filter is configured by default to ensure warnings or alarms aretriggered when a specific error message is found. You can however customize this default log filterto monitor any other error message in the Veritas Volume Manager daily log or any other log files(Windows System Event Logs for example).


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

To customize the log filter settings1. From the Add Monitoring Configuration panel, select VxVM Logs from the Monitor Type list

2. In the VxVM Logs panel, click Add

3. In the Log Filter section, configure the conditions that will trigger a warning and/or an alarm:

Customizing the Log Filter

In the Warnings section:

Click Add

Select the type of regular expression: Include will select all matching lines; Excludediscards all matching lines

In the Regular Expression field, enter the expression that will trigger a warning

Identify the warning filter with an Internal ID

Click OK to validate.

Regular expressions are case-sensitive.

Creating a Warning Event Filter

In the Alarms section:

Click Add

Select the type of regular expression: Include will select all matching lines; Exclude


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

discards all matching lines

In the Regular Expression field, enter the expression that will trigger an alarm

Identify the alarm filter with an Internal ID

Click OK to validate.

Creating an Alarm Event Filter

4. Click OK twice.

5. Click Save.

Configuring the Log Scan LimitBMC TrueSight OM - Veritas Volume Manager Monitoring scans log files by reading the new logentries since the last data collection cycle. By default, only 500 KBytes of data is scanned for eachlog file during each data collection cycle. This log scan limit can however be modified to better suityour requirements.

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

To configure Veritas Volume Manager logs (scan limit)1. From the Add Monitoring Configuration panel, select VxVM Logs from the Monitor Type list.

2. In the VxVM Logs panel, click Add.

Configuring Veritas Volume Manager Logs Scan Limit


localhost to apply these settings to all PATROL Agents installed on Veritas Volume Manager


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

servers


4. In the Scan Limit field, indicate the amount of data (in KBytes) that will be read by themonitoring solution during each data collection cycle.

5. Click OK twice

5. Click Save.

Configuring Custom VxVM Logs MonitoringBy default, Veritas Volume Manager KM only monitors the daily Veritas Volume Managermessages file and the system log file. To override the default configuration and add additional logfiles, such as Windows System Event Logs, you will have to configure the custom VxVM Logs asfollows:

1. From the Add Monitoring Configuration panel, select VxVM Logs from the Monitor Type list.

2. In the VxVM Logs panel, click Add.

3. In the Custom VxVM Logs section, click Add.

Configuring Custom VxVM Log Paths

4. In the Filename (Full Path) field, enter the full path to the VxVM Log file to be monitored using"\" as a separator (example: \var\VRTSvxvm\log\engine_A.log). For Windows events, prefix thefilename with Events - (example: Events - Systems).

5. (Optional) Enter a brief description of the VxVM log.

6. Click OK.

7. Customize the log filter to indicate the regular expressions that will generate a warning and/oran alarm when found in the custom VxVM log.

8. Click OK twice.

9. Click Save.

Configuring Custom VxVM PlexesBy default, the solution monitors all the Veritas Volume Manager plexes discovered, which mayrepresent an important workload for the Agents and the TrueSight OM servers. Because themonitoring of some VxVM plexes may be irrelevant for various reasons, you can apply filters tospecify the VxVM plexes that will be monitored or discarded.


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

To configure VxVM plexes1. From the Add Monitoring Configuration panel, select VxVM Plex from the Monitor Type list.

2. In the VxVM Plexes panel, click Add.

Configuring VxVM Plexes


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00





In the Keep Only Plexes section, click Add and identify the VxVM plex you wish to monitor.Enter the name of the VxVM plex or identify it by using a regular expression (example: prod-plex*). Click OK to validate. Repeat the operation for any other VxVM plex you wish toinclude in the monitoring process

In the Exclude Plexes section, click Add and identify the VxVM plex you do not want tomonitor. Enter the name of the VxVM plex or identify it by using a regular expression(example: test-plex*). Click OK to validate. Repeat the operation for any other VxVM plexyou wish to exclude from the monitoring process

5. The Additional Plexes (manual discovery) section allows you to add VxVM plexes manually,when they are not automatically discovered:

Click Add and enter the name of the VxVM plex you wish to add to the monitoringenvironment. Click OK to validate. Repeat the operation for each VxVM plex you want tomonitor

(Optional) Enter a short description that will allow you to quickly identify the added VxVMplex


Configuring VxVM Replicated Volume GroupsBy default, the solution monitors all the Veritas Volume Manager replicated volume groupsdiscovered, which may represent an important workload for the Agents and the TrueSight OMservers. Because the monitoring of some VxVM replicated volume groups may be irrelevant forvarious reasons, you can apply filters to specify the VxVM replicated volume groups that will bemonitored or discarded.


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

To configure VxVM replicated volume groups1. From the Add Monitoring Configuration panel, select VxVM Replicated Volume Group from

the Monitor Type list.

2. In the VxVM Replicated Volume Groups panel, click Add.

Configuring VxVM Replicated Volume Groups


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00





In the Keep Only Replicated Volume Groups section, click Add and identify the VxVMreplicated volume group you wish to monitor. Enter the name of the VxVM replicatedvolume group or identify it by using a regular expression (example: prod-replicated_volume_group*). Click OK to validate. Repeat the operation for any other VxVMreplicated volume group you wish to include in the monitoring process

In the Exclude Replicated Volume Groups section, click Add and identify the VxVMreplicated volume group you do not want to monitor. Enter the name of the VxVM replicatedvolume group or identify it by using a regular expression (example: test-replicated_volume_group*). Click OK to validate. Repeat the operation for any other VxVMreplicated volume group you wish to exclude from the monitoring process

5. The Additional Replicated Volume Groups (manual discovery) section allows you to addVxVM replicated volume groups manually, when they are not automatically discovered:

Click Add and enter the name of the VxVM replicated volume group you wish to add to themonitoring environment. Click OK to validate. Repeat the operation for each VxVMreplicated volume group you want to monitor

(Optional) Enter a short description that will allow you to quickly identify the added VxVMreplicated volume group


Configuring VxVM Replication LinksBy default, the solution monitors all the Veritas Volume Manager replication links discovered,which may represent an important workload for the Agents and the TrueSight OM servers. Becausethe monitoring of some VxVM replication links may be irrelevant for various reasons, you can applyfilters to specify the VxVM replication links that will be monitored or discarded.


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

To configure VxVM replication links1. From the Add Monitoring Configuration panel, select VxVM Replication Links from the

Monitor Type list.

2. In the VxVM Replication Link panel, click Add.

Configuring VxVM Replication Links


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00





In the Keep Only Replication Links section, click Add and identify the VxVM replication linkyou wish to monitor. Enter the name of the VxVM replication link or identify it by using aregular expression (example: prod-replication_link*). Click OK to validate. Repeat theoperation for any other VxVM replication link you wish to include in the monitoring process

In the Exclude Replication Links section, click Add and identify the VxVM replication link youdo not want to monitor. Enter the name of the VxVM replication link or identify it by using aregular expression (example: test-replication_link*). Click OK to validate. Repeat theoperation for any other VxVM replication link you wish to exclude from the monitoringprocess

5. The Additional Replication Links (manual discovery) section allows you to add VxVMreplication links manually, when they are not automatically discovered:

Click Add and enter the name of the VxVM replication link you wish to add to the monitoringenvironment. Click OK to validate. Repeat the operation for each VxVM replication link youwant to monitor

(Optional) Enter a short description that will allow you to quickly identify the added VxVMreplication link


Configuring VxVM SubdisksBy default, the solution monitors all the Veritas Volume Manager subdisks discovered, which mayrepresent an important workload for the Agents and the TrueSight OM servers. Because themonitoring of some VxVM subdisks may be irrelevant for various reasons, you can apply filters tospecify the VxVM subdisks that will be monitored or discarded.


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

To configure VxVM subdisks1. From the Add Monitoring Configuration panel, select VxVM Subdisks from the Monitor Type

list.

2. In the VxVM Subdisk panel, click Add.

Configuring VxVM Subdisks


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00





In the Keep Only Subdisks section, click Add and identify the VxVM subdisk you wish tomonitor. Enter the name of the VxVM subdisk or identify it by using a regular expression(example: prod-subdisk*). Click OK to validate. Repeat the operation for any other VxVMsubdisk you wish to include in the monitoring process

In the Exclude Subdisks section, click Add and identify the VxVM subdisk you do not want tomonitor. Enter the name of the VxVM subdisk or identify it by using a regular expression(example: test-subdisk*). Click OK to validate. Repeat the operation for any other VxVMsubdisk you wish to exclude from the monitoring process

5. The Additional Subdisks (manual discovery) section allows you to add VxVM subdisksmanually, when they are not automatically discovered:

Click Add and enter the name of the VxVM subdisk you wish to add to the monitoringenvironment. Click OK to validate. Repeat the operation for each VxVM subdisk you want tomonitor

(Optional) Enter a short description that will allow you to quickly identify the added VxVMsubdisk

5. Click OK twice

6. Click Save.

Configuring VxVM VolumesBy default, the solution monitors all the Veritas Volume Manager volumes discovered, which mayrepresent an important workload for the Agents and the TrueSight OM servers. Because themonitoring of some VxVM volumes may be irrelevant for various reasons, you can apply filters tospecify the VxVM volumes that will be monitored or discarded.


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

To configure VxVM volumes1. From the Add Monitoring Configuration panel, select VxVM Volumes from the Monitor Type

list.

2. In the VxVM Volume panel, click Add.

Configuring VxVM Volumes


BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00





In the Keep Only Volumes section, click Add and identify the VxVM volume you wish tomonitor. Enter the name of the VxVM volume or identify it by using a regular expression(example: prod-volume*). Click OK to validate. Repeat the operation for any other VxVMvolume you wish to include in the monitoring process

In the Exclude Volumes section, click Add and identify the VxVM volume you do not want tomonitor. Enter the name of the VxVM volume or identify it by using a regular expression(example: test-volume*). Click OK to validate. Repeat the operation for any other VxVMvolume you wish to exclude from the monitoring process

5. The Additional Volumes (manual discovery) section allows you to add VxVM volumesmanually, when they are not automatically discovered:

Click Add and enter the name of the VxVM volume you wish to add to the monitoringenvironment. Click OK to validate. Repeat the operation for each VxVM volume you want tomonitor

(Optional) Enter a short description that will allow you to quickly identify the added VxVMvolume


Blocking the Remote Monitoring of aVeritas Volume Manager Server NodeThe server owner/administrator may want to stop the monitoring of a remote Veritas VolumeManager Server Node when performing maintenance work on this server. The monitoring can beblocked from the relevant Veritas Volume Manager Server Node and will not require making anychange from the monitoring PATROL Agent system(s). The administrator will just have to create afile named VVM_block under the Remote Temp Directory Path.By default, this path is set to /var/tmp (on UNIX/Linux) or C:\Windows\Temp (on Windows).

The PATROL Agent monitoring this Veritas Cluster Server Node will detect the block file during thenext discovery cycle and turn the node instance to VxVM Setup: <node-id> (Monitoring Blocked).

To resume monitoring, simply delete the VVM_block file.

Configuring Thresholds

65

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

When you are creating or editing a policy, you can add and configure monitor thresholds. The AddThresholds dialog box presents threshold configuration fields for BMC ProactiveNet monitors thatare configured through Central Monitoring Administration.

For details about baselines and Key Performance Indicators (KPI), see BMC ProactiveNet CentralMonitoring Administration or BMC ProactiveNet documentation or refer to the Managing Baselinesand Key Performance Indicators section. For details about the monitored attributes, refer to thespecific monitor type in the Reference Guide section.

Before you begin

Ensure that your monitor configuration is complete before thresholds are applied. Thresholdscannot be applied to monitors that are not configured through Central Monitoring Administration.If you have not done so already, please refer to the section Configuring Monitor Settings.

Recommended Thresholds

Thresholds define acceptable high and/or low values for the data collected. Thresholds can becreated as part of a policy that can be applied to multiple monitor types on multiple BMC PATROLAgents. The Reference Guide provides a list of monitor types with their respective attributes and, whenmeaningful, a recommended threshold.

Configuring Monitor ThresholdsTo configure monitor thresholds:

1. Create a new policy or edit an existing one.

2. Select the Threshold Configuration tab and click Add .

3. In the Add Thresholds dialog box, select the relevant Solution, Version, and Monitor Type.

4. In the Instance Name field, specify the instance to which the threshold configuration will beapplied. You can either use a string or the following regular expression patterns: ?, +, *, ( ), |,[ ], { }, ,̂ $,

5. Select Match Device Name if you want the entire <deviceName>\<instanceName> string to beconsidered.

6. From the Attribute list, select a monitor attribute.

7. In the Threshold section:

Select the threshold type.

Set the threshold parameters values.

Click Add.

66Configuring Monitor Thresholds

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

8. Resume the procedure to configure all the monitor thresholds required.

9. Click Close. The configuration details are displayed in the table on the Threshold Configurationtab.

10. Click Save at the bottom of the Add Policy dialog box, or Update at the bottom of the EditPolicy dialog box.

After you save or update the policy, new threshold configurations are pushed to BMC PATROLAgents with matching Central Monitoring Configuration tags.

Editing a Threshold ConfigurationTo edit a threshold configuration:

1. Edit an existing policy

2. On the Threshold Configuration tab, select a threshold definition, and click Edit.

3. Edit the configuration values and click Update.

4. When you finish editing the threshold configuration, click Close.

5. To save changes to the policy, click Update at the bottom of the Edit Policy dialog box.

After you update the policy, updated threshold configurations are pushed to BMC PATROL Agentswith matching Central Monitoring Configuration tags.

Deleting a Threshold ConfigurationTo delete a threshold configuration:

1. Edit an existing policy

2. On the Threshold Configuration tab, select attributes, monitor types, versions, or solutions.

3. Click Delete.

4. After you delete one or more threshold configurations, click Close.

5. To save changes to the policy, click Update at the bottom of the Edit Policy dialog box.

After you update the policy, deleted threshold configurations are removed from BMC PATROLAgents with matching Central Monitoring Configuration tags.

Reference Guide

68

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Introduction

This chapter provides statistical information about resources, operating status, and performancesmanaged by the Veritas Volume Manager KM. It contains tables describing the attributes used inthe KM, grouped by Monitor Types, and provides a brief description of each attribute and itsdefault settings.

Monitor Types

Veritas Volume Manager KM

VxVM Daemon

VxVM Daemons

VxVM Disk Device

VxVM Disk Group

VxVM Disk Groups

VxVM Disk Path

VxVM Log

VxVM Logs

VxVM Plex

VxVM Subdisk

VxVM Volume

VxVM Replicated Volume Group

VxVM Replication Link

Baselines and Key Performance Indicators

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

In this guide, attributes flagged as KPIs are respectively identified by the following icon: .

69

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Veritas Volume Manager KMAttributes

Name Description Units Default AlertConditions

Type

Login Status* Monitors the status of themonitoring solution logindetails (username/password)for the operating system. Ifno valid username/passwordis detected for the operatingsystem, this attribtue will beset to "Failure" state. If thereare any suspicious commandexit, this attribute will be setto "Suspicious" state.If this status attributechanges to warning or alarmstate, the recovery actionwill trigger an event andannotate the last data point.

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

Warning = 1Alarm = 2

CollectionStatus

MonitoringMode*

Indicates the Veritas VolumeManager KM monitoringmode.

{0 = Permanent Single-node Mode;1 = Temporary Single-nodeMode;2 = Active Multi-nodeMode;3 = Passive Multi-nodeMode;-1 = Unknown}

None CollectionStatus

Node Status* Monitors error messages forthe Veritas Volume Managerapplication on this managedsystem.If any of the VeritasVolume Manager applicationdaemons is not running, thisattribute will be set to"Failure" state. The list ofcritical Veritas VolumeManager daemons can becustomized using the KMcommand Configuration >Node Status from the VeritasVolume Manager icon. Ifthere are any suspiciouscommand exit due to anerror, this attribute will beset to "Suspicious" state.



Availability

70Veritas Volume Manager KM

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

If this status attributechanges to warning or alarmstate, the recovery actionwill trigger an event andannotate the last data point.

* Attributes marked with an asterisk are used by default when visualizing the corresponding monitor instancein TrueSight.

VxVM DaemonAttributes

Name Description Units Recommended AlertConditions

Type

CPU Duration Indicates the CPU secondsconsumed by the daemon.

Seconds None Statistics

CPU Utilization* Indicates the CPU percentageconsumed by the daemon.

Percentage (%) None Statistics

Memory Size* Indicates the core image size ofthe daemon in the virtualmemory.

Kilobytes (KB) None Statistics

Processes Count Indicates the number of theprocesses/threads of thedaemon found.

Processes None Statistics

State Indicates the state of thedaemon as reported in thecommand executed by the datacollector.

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

None Availability

Status Monitors the status of thedaemon. This status isdetermined by the daemonstatus mapping rule defined inthe KM command Configuration> Daemon(s) Status.


Warning= 1Alarm = 2

Availability

71 VxVM Daemon

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

If this status attribute changesto warning or alarm state, therecovery action will trigger anevent and annotate the lastdata point.


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

VxVM DaemonsAttributes

Name Description Units Recommended AlertConditions

Type

Exec Time Collector execution time. Seconds None Collection Status

VxVM Disk DeviceAttributes

Name Description Units DefaultAlertConditions

Type

DiskdeviceSpace Available

Indicates the available space on thediskdevice.

Gigabytes (GB) None Availability

Enabled DiskPaths

Monitors the number of enabled disk pathswith kernel state ENABLED.

Count Alarm = 0 Availability

IO Kbytes Rate* Indicates the number of KBytes transferredper second for the diskdevice since the lastcollect.

Kilobytes persecond (KB/s)

None Statistics

IO KBytes Indicates the total number of KBytestransferred on the diskdevice since the lastcollect.


IO Operations

Failed

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

Operations None Statistics

72VxVM Disk Device

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

IO Operations

Rate

Indicates the number of input and outputoperations per second for the diskdevice sincethe last collect.

Operations persecond(Operations/second)

None Statistics

IO Operations Indicates the total number of input andoutput operations on the diskdevice since thelast collect.


Non-EnabledDisk Paths

Indicates the number of disk paths that arenot enabled.

Count Warning =1-100Alarm ifout of [-1to 100]range.

Availability

Queue Depth Indicates the number of read and writerequests in queue for the diskdevice onWindows platforms.

Requests None Statistics

Read KBytes

Rate*

Indicates the number of KBytes read persecond for the diskdevice since the lastcollect.


None Statistics

Read KBytes Indicates the number of KBytes read on thediskdevice.


Read Operations

Failed

Monitors the number of failed readoperations on the diskdevice on Unixplatforms. If this attribute changes to warningor alarm state, the recovery action will triggeran event.

Operations Warning:10-100Alarm ifout of [0to 100]range.

Statistics

Read Operations Indicates the number of read operations onthe diskdevice since the last collect.


Read TimeAverage*

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

Milliseconds None Statistics

Read Time* Monitors the read time for the diskdevice. Ifthis attribute changes to warning or alarmstate, the recovery action will trigger an event.

Milliseconds Warning:20-100Alarm ifout of [0to 100]range.

Response Time

73 VxVM Disk Device

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

State (Windows) Indicates the state of the diskdevice onWindows platforms.

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

None Availability

State Indicates the state of the diskdevice on Unixplatforms.

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

None Availability

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


Warning =1Alarm = 2

Availability

Write KBytes

Rate*

Indicates the number of KBytes written persecond for the diskdevice since the lastcollect.


None Statistics

Write KBytes Indicates the number of KBytes written on thediskdevice since the last collect.


WriteOperations

Failed

Monitors the number of failed writeoperations on the diskdevice on Unixplatforms. If this attribute changes to warningor alarm state, the recovery action will triggeran event.

Operations Warning =10-100Alarm ifout of [0to 100]range.

Statistics

WriteOperations

Indicates the number of write operations onthe diskdevice since the last collect.


Write TimeAverage*

Monitors the average write time for thediskdevice. If this attribute changes to warningor alarm state, the recovery action will triggeran event.


74VxVM Disk Device

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

Write Time* Monitors the write time for the diskdevice. Ifthis attribute changes to warning or alarmstate, the recovery action will trigger an event.

Milliseconds Warning =20-100Alarm ifout of [0to 100]range.

Response Time



VxVM Disk GroupAttributes


Type

Space Available* Indicates the available space for thediskgroup.

Gigabytes (GB) None Availability

State (Windows) Indicates the state of the diskgroup onWindows platforms.

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

None Availability

State Indicates the state of the diskgroup onUnix platforms.

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

None Availability

Status Monitors the status of the diskgroup.This status is determined by thediskgroup status mapping rule definedin the KM command Configuration >Diskgroup(s) Status.

If this status attribute changes towarning or alarm state, the recoveryaction will trigger an event andannotate the last data point.


Warning =1Alarm = 2

Availability


75 VxVM Disk Groups

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

VxVM Disk GroupsAttributes


Type

Disk Device ExecTime

Execution time of the disk device collector. Seconds Warningwhen >presetvalue orobservedmaximum(default)

Collection Status

Disk Group ExecTime

Execution time of the disk group collector. Seconds Warningwhen >presetvalue orobservedmaximum(default)

Collection Status

Plex Exec Time Execution time of the Plex collector. Seconds Warningwhen >presetvalue orobservedmaximum(default)

Collection Status

Rlink Exec Time Execution time of the Rlink collector. Seconds Warningwhen >presetvalue orobservedmaximum(default)

Collection Status

Rvg Exec Time Execution time of the RVG collector. Seconds None Collection Status

Subdisk Exec Time Execution time of the subdisk collector. Seconds Warningwhen >presetvalue orobservedmaximum(default)

Collection Status

76VxVM Disk Groups

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

Volume Exec Time Execution time of the volume collector. Seconds Warningwhen >presetvalue orobservedmaximum(default)

Collection Status

VxVM Disk PathAttributes


Type

Kernel State(Windows)

Indicates the kernel state of the subdisk onWindows platforms.

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

None Availability

Kernel State Indicates the kernel state of the diskpath onUnix platforms

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

None Availability

Kernel Status Monitors the kernel status of the disk paths.This status is determined by the subpathstatus mapping rule defined in the KMcommand Configuration > Disk Path(s) KernelStatus. If this status attribute changes towarning or alarm state, the recovery actionwill trigger an event and annotate the lastdata point.


Warning =1Alarm = 2

Availability

77 VxVM Log

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

VxVM LogAttributes


Type

Alarm MessageCount*

Monitors the number of alarm messages. Count Alarm = 1-100Alarm ifout of [0to 100]range.

Statistics

File SpaceGrowth Rate

Displays the growth rate of the amount of spaceused by the log file.


None Statistics

File Space Used Displays the amount of space used by the logfile.


Filesystem SpaceUsed Percent*

Monitors the percentage of space used by thefile system (where the log file resides).If this attribute changes to warning or alarmstate, the recovery action will trigger an event.

Percentage(%)

Warning =95- 98Alarm: 98-100Alarm ifout of [0to 100]range.

Statistics

Space Available Monitors the available space for the log file touse (this is also the available space on the filesystem).If this attribute changes to warning or alarmstate, the recovery action will trigger an event.

Megabytes(MB)

Warning =-1-2Alarm = 2-5

Availability

Space Used

Percent*

Monitors the percentage of capacity used by thelog file.If this attribute changes to warning or alarmstate, the recovery action will trigger an event.Note that the total capacity is the used space(Space Used) plus available space (SpaceAvailable).

Percentage(%)

Warning =95- 98Alarm =98- 100Alarm ifout of [0to 100]range.

Statistics

WarningMessage Count*

Monitors the number warning messages. Count Warning =1-100Alarm ifout of [0to 100]range.

Statistics

78VxVM Log

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00



VxVM LogsAttributes


Type

Exec Time Monitors the execution time of the log collector. Seconds Warning > presetvalue orobservedmaximum(default)

Collection Status

VxVM PlexAttributes


Type

IO KBytes Rate* Indicates the number of KBytestransferred per second for theplex on Unix platforms sincethe last collect.


None Statistics

IO KBytes Indicates the total number ofKBytes transferred on the plexsince the last collect.


IO Operations Failed Indicates the total number offailed input and outputoperations on the plex on Unixplatforms.


IO Operations Rate Indicates the number of inputand output operations persecond for the plex on Unixplatforms since the last collect.

Operations persecond(Operations/second)

None Statistics

79 VxVM Plex

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

IO Operations Indicates the total number ofinput and output operations onthe plex on Unix platforms.


Kernel State (Windows) Indicates the kernel state of theplex on Windows platforms.

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

None Availability

Kernel State Indicates the kernel state of theplex on Unix platforms.


None Availability

Kernel Status Monitors the kernel status ofthe plex. This status isdetermined by the plex statusmapping rule defined in the KMcommand Configuration > Plex(s) Kernel Status.If this status attribute changesto warning or alarm state, therecovery action will trigger anevent and annotate the lastdata point.

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


Availability

Read KBytes Rate* Indicates the number of KBytesread per second for the plex onUnix platforms since the lastcollect.


None Statistics

Read KBytes Indicates the number of KBytesread on the plex on Unixplatforms since the last collect.


Read Operations Failed Monitors the number of failedread operations on the plex onUnix platforms.If this attribute changes towarning or alarm state, therecovery action will trigger anevent.

Operations Warning = 10-100Alarm if out of[0 to 100]range.

Statistics

Read Operations Indicates the number of readoperations on the plex on Unixplatforms since the last collect.


Read Time Average* Monitors the average read timefor the plex on Unix platforms.


80VxVM Plex

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

If this attribute changes towarning or alarm state, therecovery action will trigger anevent.

Read Time* Monitors the read time for theplex on Unix platforms.If this attribute changes towarning or alarm state, therecovery action will trigger anevent.

Milliseconds Warning = 20-100Alarm if out of[0 to 100]range.

ResponseTime

State (Windows) Displays the state of the plexon Windows platforms.

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

None Availability

State Displays the state of the plexon Unix platforms.

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

None Availability

Status Monitors the status of the plex.This status is determined bythe plex status mapping ruledefined in the KM commandConfiguration > Plex(s) Status.If this status attribute changesto warning or alarm state, therecovery action will trigger anevent and annotate the lastdata point.

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


Availability

Write KByte Indicates the number of KByteswritten on the plex on Unixplatforms since the last collect.


81 VxVM Plex

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

Write KBytes Rate* Indicates the number of KByteswritten per second for the plexon Unix platforms since the lastcollect.


None Statistics

Write Operations Failed Monitors the number of failedwrite operations on the plex onUnix platforms.If this attribute changes towarning or alarm state, therecovery action will trigger anevent.


Statistics

Write Operations Indicates the number of writeoperations on the plex on Unixplatforms since the last collect.


Write Time Average* Monitors the average writetime for the plex on Unixplatforms. If this attributechanges to warning or alarmstate, the recovery action willtrigger an event.


Write Time* Monitors the write time for theplex on Unix platforms. If thisattribute changes to warning oralarm state, the recoveryaction will trigger an event.


ResponseTime



VxVM Replicated Volume GroupAttributes


Type

Kernel State Displays the kernel state ofthe replicated volume group.

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

None Availability

Kernel Status Displays the kernel status ofthe replicated volume group.



Availability

82VxVM Replicated Volume Group

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

Replication Link Count* Displays the number ofreplication links in thereplicated volume group.

rlinks None Availability

State Displays the state of thereplicated volume group.

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

None Availability

Status Displays the status of thereplicated volume group.



Availability

Volume Count* Displays the number ofreplicated data volumes.

Volumes None Availability


VxVM Replication LinkAttributes


Type

Kernel State Displays the kernel state of thereplication link.

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

None Availability

Kernel Status Displays the kernel status of thereplication link.



Availability

Remaining

Updates Count

Displays the number of updatesthe primary RVG is ahead of thesecondary RVG.

Updates None Statistics

Remaining

Updates Lag

Displays the amount of time thesecondary RVG is lagging.

Seconds None Statistics

83 VxVM Replication Link

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

RemainingUpdates Percent *

Displays the percentage of theSRL yet to be replicated to thesecondary replicated volumegroup. The attribute is collectedonly on the primary node andwill be left offline (greyed-out)on secondary nodes.

Percentage (%) Warning when> 80 and < 90Alarm when >90

Statistics

Remaining

Updates Size*

Displays the size of the SRL inKBytes.

Kilobytes (KBytes) None Statistics

State Displays the state of thereplication link.

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

None Availability

Status Displays the status of thereplication link.



Availability


VxVM SubdiskAttributes


Type

IO KBytes Rate* Indicates the number of KBytestransferred per second for thesubdisk since the last collect.


None Statistics

IO KBytes Indicates the total number ofKBytes transferred on thesubdisk since the last collect.


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


IO Operations Rate Indicates the number of inputand output operations persecond for the subdisk.

Operationsper second(Operations/second)

None Statistics

84VxVM Subdisk

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

IO Operations Indicates the total number ofinput and output operations onthe subdisk since the last collect.


Kernel State (Windows) Indicates the kernel state of thesubdisk on Windows platforms.

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

None Availability

Kernel State Indicates the kernel state of thesubdisk on Unix platforms.


None Availability

Kernel Status Monitors the kernel status of thesubdisk. This status isdetermined by the subdiskstatus mapping rule defined inthe KM command Configuration> Subdisk(s) Kernel Status.If this status attribute changes towarning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.

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


Availability

Read KBytes Rate* Indicates the number of KBytesread per second for the subdisksince the last collect.

Kilobytes persecond KB/s

None Statistics

Read KBytes Indicates the number of KBytesread on the subdisk since thelast collect.


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


Statistics

Read Operations Indicates the number of readoperations on the subdisk sincethe last collect.


Read Time Average* Monitors the average read timefor the subdisk.


85 VxVM Subdisk

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

If this attribute changes towarning or alarm state, therecovery action will trigger anevent.

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


ResponseTime

Write KBytes Rate* Indicates the number of KByteswritten per second for thesubdisk since the last collect.

Kilobytes persecond KB/s

None Statistics

Write KBytes Indicates the number of KByteswritten on the subdisk since thelast collect.


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


Statistics

Write Operations Indicates the number of writeoperations on the subdisk sincethe last collect.


Write Time Average* Monitors the average write timefor the subdisk.If this attribute changes towarning or alarm state, therecovery action will trigger anevent.


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


ResponseTime



86VxVM Volume

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

VxVM VolumeAttributes


Type

IO KBytes

Rate*

Indicates the number ofKBytes transferred persecond for the volume sincethe last collect.

Kilobytes per second (KB/s) None Statistics

IO KBytes Indicates the total number ofKBytes transferred on thevolume since the last collect.


IO Operations

Failed

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


IO Operations

Rate

Indicates the number ofinput and output operationsper second for the volume.

Operations per second(Operations/second)

None Statistics

IO Operations Indicates the total number ofinput and output operationson the volume.


Kernel State(Windows)

Indicates the kernel state ofthe volume on Windowsplatforms.

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

None Availability

Kernel State Indicates the kernel state ofthe volume on Unixplatforms.

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

None Availability

Kernel Status Monitors the kernel status ofthe volume. This status isdetermined by the volumestatus mapping rule definedin the KM commandConfiguration > Volume(s)Kernel Status.If this status attributechanges to warning or alarmstate, the recovery actionwill trigger an event andannotate the last data point.

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


Availability

87 VxVM Volume

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

Logging State Indicates the logging state ofthe volume on Unix

platforms.

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

None Availability

Logging Status Monitors the logging statusof the volume on Unixplatforms. This status isdetermined by the volumestatus mapping rule definedin the KM commandConfiguration > Volume(s)Logging Status.If this status attributechanges to warning or alarmstate, the recovery actionwill trigger an event andannotate the last data point.

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


Availability

Read KBytes

Rate*

Indicates the number ofKBytes read per second forthe volume since the lastcollect.


Read KBytes Indicates the number ofKBytes read on the volumesince the last collect.


ReadOperations

Failed

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

Operations Warning = 10-100Alarm if outof [0 to 100]range.

Statistics

ReadOperations

Indicates the number of readoperations on the volumesince the last collect.


Read TimeAverage*

Monitors the average readtime for the volume.If this attribute changes towarning or alarm state, therecovery action will triggeran event.


Read Time* Monitors the read time forthe volume.If this attribute changes towarning or alarm state, therecovery action will triggeran event.

Milliseconds Warning = 20-100Alarm if outof [0 to 100]range.

ResponseTime

88VxVM Volume

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

State(Windows)

Indicates the state of thevolume on Windowsplatforms.

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

None Availability

State Indicates the state of thevolume on Unix platforms.

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

None Availability

Status Monitors the status of thevolume. This status isdetermined by the volumestatus mapping rule definedin the KM commandConfiguration > Volume(s)Status.If this status attributechanges to warning or alarmstate, the recovery actionwill trigger an event andannotate the last data point.



Availability

Write KBytes

Rate*

Indicates the number ofKBytes written per secondfor the volume since the lastcollect.


Write KBytes Indicates the number ofKBytes written on thevolume since the last collect.


WriteOperations

Failed

Monitors the number offailed write operations onthe volume on Unixplatforms.If this attribute changes towarning or alarm state, therecovery action will triggeran event.

Operations Warning = 10-100Alarm if outof [0 to 100]range.

Statistics

89 VxVM Volume

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00


Type

WriteOperations

Indicates the number ofwrite operations on thevolume since the last collect.


Write TimeAverage*

Monitors the average writetime for the volume.If this attribute changes towarning or alarm state, therecovery action will triggeran event.


Write Time* Monitors the write time forthe volume.If this attribute changes towarning or alarm state, therecovery action will triggeran event.

Milliseconds Warning = 20-100Alarm if outof [0 to 100]range.

ResponseTime



Managing Baselines and KeyPerformance IndicatorsTo detect abnormalities on the monitored environment, BMC TrueSight Operations Managementcalculates baselines per attribute based on values collected over a specified period of time todetermine a normal operating range. When the collected values for these parameters are out ofrange, 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 twobaselines: Baseline High and Baseline Low. Baseline High represents the point at which 95% of theweighted average of the historical values fall below this value for the selected time period; BaselineLow represents the point at which 90% of the weighted average of historical values for the selectedtime period fall above this line.

Baselines are generated for KPI attributes that have an active abnormality thresholds.

90Managing Baselines and Key PerformanceIndicators

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Managing Key Performance Indicators

Starting from v9.5 of BPPM, attributes that have not been initially designated in the KM as KeyPerformance Indicators (KPIs) cannot be flagged as KPIs from BPPM/TrueSight. Although enablingbaseline is possible through the Options > Administration > Intelligent Event Thresholds featureavailable in the Infrastructure Management Server operator console, BMC does not recommenddoing it.

For more information, refer to the BMC TrueSight Operations Management documentation availablefrom docs.bmc.com.

https://docs.bmc.com/docs/dashboard.action

91

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Index

- A -Abnormalities 89

Access

Permissions 11

User 11Add Monitor Types 40

Attributes

Alarm Message Count 77

CPU Duration 70

CPU Utilization 70

Disk Device Exec Time 75

Disk Group Exec Time 75

Diskdevice Space Available 71

Enabled Disk Paths 71

Exec Time 71, 78

File Space Growth Rate 77

File Space Used 77

Filesystem Space Used Percent 77

IO KBytes 71, 78, 83, 86

IO KBytes Rate 71, 78, 83, 86

IO Operations 71, 78, 83, 86

IO Operations Failed 71, 78, 83, 86

IO Operations Rate 71, 78, 83, 86

Kernel State 76, 78, 81, 82, 83, 86

Kernel State (Windows) 76, 78, 83, 86

Kernel Status 76, 78, 81, 82, 83, 86

Logging State 86

Logging Status 86

Login Status 69

Memory Size 70

Monitoring Mode 69

Node Status 69

Non-Enabled Disk Paths 71

Plex Exec Time 75

Processes Count 70

Queue Depth 71

Read KBytes 71, 78, 83, 86

Read KBytes Rate 71, 78, 83, 86

Read Operations 71, 78, 83, 86

Read Operations Failed 71, 78, 83, 86

Read Time 71, 78, 83, 86

Read Time Average 71, 78, 83, 86

Remaining Updates Count 82

Remaining Updates Lag 82

Remaining Updates Percent 82

Remaining Updates Size 82

Replication Link Count 81

Rlink Exec Time 75

Rvg Exec Time 75

Space Available 74, 77

Space Used Percent 77

State 70, 71, 74, 78, 81, 82, 86

State (Windows) 71, 74, 78, 86

Status 70, 71, 74, 78, 81, 82, 86

Subdisk Exec Time 75

Volume Count 81

Volume Exec Time 75

Warning Message Count 77

Write KByte 78

Write KBytes 71, 83, 86

Write KBytes Rate 71, 78, 83, 86

Write Operations 71, 78, 83, 86

Write Operations Failed 71, 78, 83, 86

Write Time 71, 78, 83, 86

Write Time Average 71, 78, 83, 86Automated Drives

Debug 32Automated Libraries

Debug 32

- B -Baseline 68

Baselines

BMC ProactiveNet Performance Management 89

Generation 89

Manage 89

Requirements 89Block

Monitoring 63BMC PATROL

Changes 10BMC ProactiveNet Performance Management

Abnormalities 89

Baselines 89

Key Performance Indicators 89

KPI 89

92

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

- C -Client

Maximum Instances 33Clients

Debug 32Cluster Application 35

Component Installation package

creating 19

downloading 20Configure

Log Error Filter 50

Log Query Limit 49

Log Scan Limit 52

Maximum Instances 33

Multi-node monitoring mode 35

Overrides 39Configuring

Advanced Settings 32

Monitor Types 40

Post-Installation 22

VVM Server 24Configuring Monitor Thresholds 65

Configuring thresholds 65

Connections 15

- D -Daemon

Maximum Instances 33Daemons

Debug 32Database

Maximum Instances 33Databases

Debug 32Debug

Automated Drives 32

Automated Libraries 32

Clients 32

Daemons 32

Databases 32

Directory Path 32

Disabling 32

Domains 32

Enabling 32

End Time 32

Jobs 32

Logs 32

Mount Requests 32

Processes 32

Server 32

Storage Pools 32Deleting a Threshold Configuration 66

Disk Pool

Maximum Instances 33Disk Storage

Maximum Instances 33Disk Volume

Maximum Instances 33Domains

Debug 32Downloading 20

- E -Editing a Threshold Configuration 66

- F -Failover Group Name 35

- G -Generate

Baselines 89

- I -Importing the Monitoring Solution 18

Installation

configuring 22Installing 20

Installing the Monitoring Solution 17

Instances

Client 33

Configure 33

Daemon 33

Database 33

Disk Pool 33

Disk Storage 33

Disk Volume 33

Job 33

Log 33

93

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

Instances

Maximum 33

Mount Request 33

Policy 33

Policy Client 33

Robotic Drive 33

Robotic Library 33

Standalone Drive 33

Volume Pool 33

- J -Java 15

Job

Maximum Instances 33Jobs

Debug 32

- K -Key Performance Indicators 68


Manage 89KPI 68


Manage 89

- L -Log

Maximum Instances 33Log Error Filter

Alarm 50

Configure 50

Warning 50Log Query Limit

Configure 49Log Scan Limit

Configure 52Logs

Debug 32

- M -Maintenance 63

Manage

Baselines 89

Key Performance Indicators 89

KPI 89Monitor thresholds 65

Monitor Type

Veritas Volume Manager KM 69

VxVM Daemon 70

VxVM Daemons 71

VxVM Disk Device 71

VxVM Disk Group 74

VxVM Disk Groups 75

VxVM Disk Path 76

VxVM Log 77

VxVM Logs 78

VxVM Plex 78

VxVM Replicated Volume Group 81

VxVM Subdisk 83

VxVM Volume 86

VxVM_Replication_Link 82Monitor Types 40

VxVM Daemon 68

VxVM Daemons 68

VxVM Disk Device 68

VxVM Disk Group 68

VxVM Disk Groups 68

VxVM Disk Path 68

VxVM Log 68

VxVM Logs 68

VxVM Plex 68

VxVM Replicated Volume Group 68

VxVM Replication Link 68

VxVM Subdisk 68

VxVM Volume 68Monitoring

Block 63

Blocked 63

Stop 63

Stopped 63Monitoring Node Names 35

Mount Request

Maximum Instances 33Mount Requests

Debug 32Multi-node monitoring mode

Configure 35

94

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

- O -Overrides

Configure 39

VVM Server Discovery 39

- P -Package 19, 20

Policy

Maximum Instances 33Policy Client

Maximum Instances 33Processes

Debug 32

- R -Reference Guide 68

Remote monitoring

Requirements 15Remote PATROL Agent Checking 35

Requirements

Security 11

Software 10

System 10Robotic Drive

Maximum Instances 33Robotic Library

Maximum Instances 33

- S -Security

Requirements 11Server

Debug 32Software

Requirements 10SSH 15

Connection 15

Host Key Authentication 15Standalone Drive

Maximum Instances 33Storage Pools

Debug 32

Sudo 11

System

Requirements 10

- T -Thresholds 65

Tivoli Storage Manager

Changes 10

- V -Veritas Volume Manager KM 68

Volume Pool

Maximum Instances 33VVM Server Discovery

Overrides 39VVM Servers

Configuring 24VxVM Daemons

Configuration 41

Filtering 41

Manual Discovery 41VxVM Disk Devices

Configuration 42

Filtering 42

Manual Discovery 42VxVM Disk Groups

Configuration 44

Filtering 44

Manual Discovery 44VxVM Disk Paths

Configuration 46

Filtering 46

Manual Discovery 46VxVM Logs

Log Files 49VxVM Plexes

Configuration 53

Filtering 53

Manual Discovery 53VxVM Replicated Volume Groups

Configuration 55

Filtering 55

Manual Discovery 55VxVM Replication Links

Configuration 57

Filtering 57

95

BM

C T

rueS

igh

t O

M -

Ver

itas

Vo

lum

e M

anag

er M

on

ito

rin

g V

ersi

on

3.0

.00

VxVM Replication Links

Manual Discovery 57VxVM Subdisks

Configuration 59

Filtering 59

Manual Discovery 59VxVM Volumes

Configuration 61

Filtering 61

Manual Discovery 61

- W -WMI 15

Connection 15

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software, providescomprehensive multi-platform monitoring solutions that enable management of the hardwareand software aspects of all servers and SANs and covering up to 100 % of custom applicationswithin the BMC TrueSight Operations Management environment. Sentry Software alsodevelops adapters for BMC Atrium Orchestrator that enables IT administrators to automate theexecution 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 ITadministrators to implement provisioning and decommissioning workflows that cover all layersof their IT infrastructure. Finally, Sentry Software designs connectors that bring storage capacitymetrics into BMC TrueSight Capacity Optimization to ensure IT administrators that their storageinfrastructure is properly sized for their current and future needs.The combination of its monitoring, automation, and capacity optimization capabilities for IT

Like us on Facebook:facebook.com/sentrysoftware

Follow us on Twitter:

twitter.com/sentrysoftware

LEARN MORE

To learn more about our solutions, please visit :www.sentrysoftware.com/solutions

© BMC Software, Inc. All rights reserved.

ABOUT MARKETZONE DIRECT PRODUCTS

The BMC MarketZone Direct programsells and supports third-partyproducts that complement and/oraugment BMC solutions. MarketZoneDirect products are available underBMC license and support terms.

About BMC Software™BMC Software helps leading companies around the world put technology at the forefront ofbusiness transformation, improving the delivery and consumption of digital services. Frommainframe to cloud to mobile, BMC delivers innovative IT management solutions that haveenabled more than 20,000 customers to leverage complex technology into extraordinarybusiness performance—increasing their agility and exceeding anything they previously thought

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

Business thrives when IT runs smarter, fasterand stronger. That’s why the mostdemanding IT organizations in the world relyon BMC Software across distributed,mainframe, virtual and cloud environments.Recognized as the leader in Business ServiceManagement, BMC offers a comprehensiveapproach and unified platform that helps ITorganizations cut cost, reduce risk and drivebusiness profit. For the four fiscal quartersended September 30,2011, BMC revenue wasapproximately $2.2 billion.

BUSINESS RUNS ON I.T .

I.T . RUNS ON BMC SOFT WARE

http://facebook.com/sentrysoftware

http://twitter.com/sentrysoftware

http://twitter.com/sentrysoftware

http://facebook.com/sentrysoftware

BMC ProactiveNet - Veritas Volume Manager Monitoring v3.0

Documents

Transcript of BMC ProactiveNet - Veritas Volume Manager Monitoring v3.0