BMC ProactiveNet - Veritas Volume Manager Monitoring · PDF file11 Version 2.4.00 BMC...

User Documentation January 2013

BMC ProactiveNet PerformanceManagement - Veritas VolumeManager MonitoringVersion 2.4.00

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

United States and Canada Outside United States and Canada

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

Telephone (01) 713 918 8800

Telephone 713 918 8800 or 800 841 2031

Fax (01) 713 918 8000

Fax 713 918 8000

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

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

IBM is a registered trademark of International Business Machines Corporation.

DB2 is a registered trademark of International Business Machines Corporation.

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

All other trademarks belong to their respective companies.

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

Restricted Rights Legend

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

2

Version 2.4.00

BMC ProactiveNet Performance Management - Veritas Volume Manager Monitoring

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

Support Web Site

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

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

Find the most current information about BMC Software products

Search a database for problems similar to yours and possible solutions

Order or download product documentation

Report a problem or ask a question

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

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

Support by Telephone or E-mail

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

Before Contacting BMC Software

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

Product information

product name

product version (release number)

license number and password (trial or permanent)

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

PUT or PTF

system hardware configuration

serial numbers

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

pack or maintenance

level

Sequence of events leading to the problem

Commands and options that you used

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

product error messages

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

3

Version 2.4.00


http://www.bmc.com/support_home



Table of Contents 4

Version 2.4.00


Table of Contents...........................................................................................................................11User Goals and Features

...........................................................................................................................11Business Value

...........................................................................................................................12Requirements

...........................................................................................................................12System Requirements

...........................................................................................................................12Software Requirements

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

...........................................................................................................................18Adding Central Monitoring Administration Tags

...........................................................................................................................20Preparing for Installation

...........................................................................................................................21Creating a Component Installation Package

...........................................................................................................................23Editing a Component Installation Package

...........................................................................................................................24Downloading and Installing an Installation Package

...........................................................................................................................26Configuring General Settings

...........................................................................................................................27Managing Policies

...........................................................................................................................28Configuring Monitor Settings

...........................................................................................................................30Configuring Veritas Volume Manager KM

..................................................................................................................30Configuring the User Account

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

..................................................................................................................36Configuring the Maximum Number of Instances

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

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

...........................................................................................................................45Filtering Elements to Monitor

...........................................................................................................................50Navigating the BMC ProactiveNet Operations Console

...........................................................................................................................53Adding attributes to the graph

...........................................................................................................................54Viewing and manipulating attribute graphs

...........................................................................................................................54Viewing monitors for a device

...........................................................................................................................55Changing thresholds

...........................................................................................................................55Managing Baselines and Key Performance Indicators

...........................................................................................................................59VxVM Deamon

...........................................................................................................................60VxVM Disk Device

...........................................................................................................................62VxVM Disk Group

...........................................................................................................................62VxVM Disk Path

...........................................................................................................................63VxVM Log

Table of Contents 5

Version 2.4.00


...........................................................................................................................64VxVM Plex

...........................................................................................................................66Veritas Volume Manager KM

...........................................................................................................................67VxVM Subdisk

...........................................................................................................................68VxVM Volume

Support Information

7

Version 2.4.00


This section contains information about how to contact Customer Support and the levels of supportoffered for this and other releases.

If you have problems with or questions about a BMC product, or for the latest support policies, see theCustomer Support website at http://www.bmc.com/support. You can also access product documentsand search the Knowledge Base for help with an issue at http://www.SentrySoftware.com. If you do nothave access to the web and you are in the United States or Canada, contact Customer Support at 800537 1813. Outside the United States or Canada, contact your local BMC office or agent.

http://www.bmc.com/support

http://www.sentrysoftware.com

Legal Notices

9

Version 2.4.00


© Copyright 2011 BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., areregistered with the U.S. Patent and Trademark Office, and may be registered or pending registration inother countries. All other BMC trademarks, service marks, and logos may be registered or pendingregistration in the U.S. or in other countries. All other trademarks or registered trademarks are theproperty of their respective owners.

Linux is the registered trademark of Linus Torvalds.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may betrademarks of their respective owners.

UNIX is the registered trademark of The Open Group in the US and other countries.

The information included in this documentation is the proprietary and confidential information of BMCSoftware, Inc., its affiliates, or licensors. Your use of this information is subject to the terms andconditions of the applicable End User License agreement for the product and to the proprietary andrestricted rights notices included in the product documentation.

BMC Software Inc.2101 City West Blv d, Houston TX 77042-2827, USA713 918 8800Custom er Support: 800 537 1813 (United States and Canada) or contact y our local support center

Key Concepts

11

Version 2.4.00


The pages in this section provide a high-level overview of the product.

User Goals and Features

Business Value

Requirements

Note that for convenience and brev ity , reference to BMC ProactiveNet Performance Management - Veritas VolumeManager Monitoring, may also be made as Veritas Volume Manager KM.

User Goals and Features

Veritas Volume Manager KM enables you to monitor the following in your environment:

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

Disks & Multi Paths: monitors the health of disks & disk multi paths.

Logs: checks regularly for any errors in the system logs and monitors the log space utilization.

Disk groups, Volumes, Plexes and Subdisks: automatically discover All Veritas Volume Managercomponents and monitors their health.

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

Business Value

BMC ProactiveNet Performance Management - Veritas Volume Manager Monitoring provides current andhistorical information through a centralized console so you can easily view and manage your entireVeritas Volume Manager environment. The product collects and brings critical performance data anduseful metrics into the BMC ProactiveNet Performance Management environment and enables SANAdministrators to be warned whenever a problem occurs in their Veritas Volume Manager environment.

BMC ProactiveNet Performance Management - Veritas Volume Manager Monitoring:

Enhances productivity

Ensures availability of all components of Veritas Volume Manager (disks, paths, volumes, plexes &subdisks)

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

Maintains integrity

12Requirements

Version 2.4.00


Requirements

Before installing the Veritas Volume Manager KM, verify the:

system requirements

software requirements

security requirements.

System Requirements

Operating System Operating System Version

Microsoft Windows Microsoft Windows Server 2003 and 2008, all versions supported by BMC PATROLAgent 3.7 and greater

Linux All distributions supported by BMC PATROL Agent 3.7 and above

Oracle Solaris 8, 9, 10, supported by BMC PATROL Agent 3.7 and above

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

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

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

Software Requirements

BMC ProactiveNet Performance Management - Veritas Volume Manager Monitoring supports:

Software Version

Veritas Volume Manager™ (included in Veritas StorageFoundation Suites)

4.5, 5.0, 5.1, 6.x

BMC Software PATROL Agent 3.7.x, 3.8.x, 3.9, 9.x

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

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

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

Version 2.4 of BMC ProactiveNet Performance Management - Veritas Volume Manager Monitoring does not supportVeritas Volume Manager versions before 3.2 and PATROL Agent versions before 3.4.

If the operating system is upgraded (or downgraded) at a later date, you will need to reload

13Requirements

Version 2.4.00


commands for the Veritas Volume Manager KM.

Additional Software Requirements

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

Purpose Software Version

When running Veritas Volume Manager KM withsudo user account on Solaris, HP-UX, AIX orLinux managed nodes

Sudo (superuser do) 1.6.7 or later

When running Veritas Volume Manager KM onLinux managed nodes

Korn shell binary (/bin/ksh) Any

When running Veritas Volume Manager KM onMicrosoft 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 RequirementsBy default, Veritas Volume Manager is installed and run as the root user (on Unix) or asadministrator user (on Microsoft Windows).

BMC ProactiveNet Performance Management - Veritas Volume Manager Monitoring needs to be run as auser account with administrative privileges to read and execute Veritas Volume Manager applicationprograms and file systems. Login details of this user are configured in the KM during the configuration.The password is stored in the PATROL Agent in a DES encrypted format.

The encrypted password can be viewed by any user who has access to the PATROL Agentconfiguration variables (pconfig). This user could then execute PSL statements using the encryptedpassword through the PATROL Console. This can be prevented by setting up an appropriate AccessControl List (ACL) for users. Please refer to the PATROL Agent Reference Manual for details on howto set up an ACL.

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

1. root user (Unix) or administrator user (Microsoft Windows)

2. a non-root user, such as patrol, with sudo privileges on Veritas Volume Manager to executeapplication programs and access the file systems (Unix only)

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

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

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

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

14Requirements

Version 2.4.00


Access Permissions

The Veritas Volume Manager KM user needs “read & execute” permission to executable and library filesunder the paths listed below. The Veritas Volume Manager installation path INSTALL_PATH, referencedin the tables below is normally /opt/VRTSvxvm (on Unix) or C:\Program Files\Veritas\VolumeManager x.x (on Microsoft Windows).

Executable and Library Files accessed by Veritas Volume ManagerKM User

Unix Microsoft Windows

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

INSTALL_PATH\vx*.exe

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

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

vxdctl (in Veritas Cluster File System)

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

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

The 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_HOME path,normally PATROL_HOME/lib/VVM.

In addition to these Veritas Volume Manager commands, Veritas Volume Manager KM executes other operatingsystem commands, such as ps, uname which may not require special priv ileges.

To list all OS commands used by the Veritas Volume Manager KM, execute the following PSL code fromthe PATROL Console, using PSL Task menu, after installing and loading the KM.

i=0; sudoers="";

foreach var (grep("^/Runtime/VVM/CommandControls/",pconfig("LIST")))

{

ctl=get(var);

opt=ntharg(grep("Option",ctl),"2-"," =");

nsa=ntharg(grep("NoSudoAttempt",ctl),"2-"," =");

sua=ntharg(grep("SingleUserAttempt",ctl),"2-"," =");

typ=ntharg(grep("CommandType",ctl),"2-"," =");

cmd=nthargf(grep("CommandText",ctl),"2-","=","=");

if((typ == "")||(typ == "OS"))

{

met="";

if(opt == "NoLogin") { met = "(run as patrol user)"; }

elsif(nsa == "YES") { met = "(run as configured user without sudo)"; }

elsif(sua == "YES") { met = "(run as supplied user - used in menu)"; }

15Requirements

Version 2.4.00


else

{

scmd=cmd;

s=index(scmd,"%sudo");

if(s) { scmd=replace(substr(scmd,s,length(scmd)),"%sudo",""); }

sudoers=union(sudoers,ntharg(ntharg(scmd,1,"|"),"1-"," "," "));

}

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

}

}

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

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

/var/adm/messages (on Solaris)

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

/var/log/messages (on Linux)

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

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

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

Sudo User for Operating System Access

If a non-root user with sudo privileges is preferred as the Veritas Volume Manager KM user, configurethe account as a sudoer through the visudo utility using code appropriate for your platform as detailedbelow. This user should be able to execute VxVM commands and OS commands.

The code below also applies to all non-root users who may execute Veritas Volume Manager KMadministration and report menu commands using their sudo privileges. The KM accepts any non-rootuser with the following sudo configuration in the sudoers file. Please replace user1, user2, user3 withappropriate KM user name. The Veritas Volume Manager installation path INSTALL_PATH, referencedbelow is normally /opt/VRTS and PATROL_HOME is the path where the PATROL Agent is installed(including the target, like /opt/bmc/Patrol3/Solaris29-sun4/).

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

16Requirements

Version 2.4.00


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

On Solaris:User_Alias VVMKMUSERS = user1, user2, user3

Defaults:VVMKMUSERS !lecture,!authenticate,\

env_keep+="LD_LIBRARY_PATH INSTALL_PATH KM_HOME \

KM_TEMP",env_reset

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

INSTALL_PATH/bin/*,\

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

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


env_keep+="SHLIB_PATH INSTALL_PATH KM_HOME \

KM_TEMP",env_reset




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


env_keep+="LIBPATH INSTALL_PATH KM_HOME \

KM_TEMP",env_reset




Planning

18Adding Central Monitoring Administration Tags

Version 2.4.00


Adding Central MonitoringAdministration Tags

Adding Central Monitoring Administration tags should be taken into consideration before installation.

A policy specifies a set of actions to be taken when a specific condition on the BMC PATROL Agent isfulfilled. A policy enables you to perform the following actions:

Apply specific configuration to one or more BMC PATROL Agents

Configure thresholds and set baselines on BMC ProactiveNet Child Servers

Each policy is assigned a BMC ProactiveNet Central Monitoring Administration tag and each BMC PATROLAgent can have one or more tags assigned to it. When you assign a tag to a BMC PATROL Agent theassociated policy is applied to the PATROL Agent. You can assign the tag value of a policy to a PATROLAgent in the following ways:

You can add a PATROL Agent and set the tag as part of the configuration process that you performfrom Central Monitoring Administration. For details, see Managing downloads in Central MonitoringAdministration.

If the PATROL Agent has already been installed, use PATROL Configuration Manager to set thefollowing ruleset that provides the tags:/AgentSetup/Identification/Tags/TAG/tagName =tagDescription

For example if the tag which has to be applied is oracleTag, the ruleset is as follows/AgentSetup/Identification/Tags/TAG/oracleTag= “ORACLE MONITORING”

In BMC ProactiveNet version 9.0, the tag description is ignored, and only the tag name is used to evaluate the policy .

Installing

20

Version 2.4.00


The creation of the Veritas Volume Manager KM installation package is performed directly from BMCProactiveNet Central Monitoring Administration. An installation package for a component can bedownloaded and installed on several servers. The component installation package can be edited andsaved under a new name.

With Central Monitoring Administration, administrators select monitor installation components, such asthe BMC PATROL Agent and monitoring solutions, from a repository to create an installation package.The components can then be installed together using the installation package. Administrators can reusethe installation packages, or deploy the packages to multiple computers.

Preparing for Installation

The BMC ProactiveNet Central Monitoring Repository is a requirement on the BMC ProactiveNet CentralServer where Central Monitoring Administration is enabled. The Central Monitoring Repository includesthe current versions of BMC components that you can use with BMC ProactiveNet.

After creating a component installation package, administrators can save the package to the MonitoringInstallation Packages list for future use, or download the package on the current host without saving thepackage. For saved packages, administrators can download and install the package on any host, or edita package.

For supported 64-bit Linux versions, you must install the Linux runtime package, glibc.i686, version 2.3.4 or later.W ithout the Linux runtime package, BMC ProactiveNet component installations might fail.

For further details regarding the BMC ProactiveNet Central Monitoring Administration, please refer to the BMCdocumentation.

21Creating a Component Installation Package

Version 2.4.00


Creating a Component InstallationPackage

If you want to import the entire repository, first download Central Monitoring Repository files from theBMC Electronic Product Distribution (EPD) facility, or copy the files from your installation kit, to the BMCProactiveNet Central Server file system.

To import a single or custom solution1. In the navigation pane of Central Monitoring Administration, click the Repository drawer and

select Manage Repository.

2. Click Import.

3. In the Import a New Solution dialog box, select Single solution or Custom solution.

4. Browse to a source file in one of the following formats: zip, tar, or tar.gz.The solution must be located on the local computer from which you are running the CentralMonitoring Administration web-based console.

5. (Custom solution, only) provide the following details:

Custom solutions name: The name of the custom solution, as it will be displayed in CentralMonitoring Administration.

Custom solution version: The version number for the custom solution. Values in the first twoversion boxes are required.

6. Click Import.

The selected archive file is imported to the repository and extracted. You can close the window duringthe import process.

22Creating a Component Installation Package

Version 2.4.00


To create a component installation package1. In the navigation pane of Central Monitoring Administration, click the Repository drawer and

select Monitoring Repository.

2. Click Add .

3. Select the operating system for which you want to create a package, and then select a platform onwhich you want to install the package.The list of components in the repository that are supported on the specified operating system andplatform is displayed.

4. From the Available components list, select components that you want to include in the package.

5. From the Version list, select the version of the component that you want to include in the package.You can select a specific version or you can select latest, which automatically updates the packagewith the latest versions of the components when new versions of those components are added tothe Central Monitoring Repository. By default, the appropriate BMC PATROL Agent for the operating system and platform that youchose is included in the Selected components list.

6. Click the right arrow button to move the selected components into the Selected Components list,and then click Next.The installation wizards for the products that you selected are displayed. They'll vary depending onthe products or components that you selected to include in the package. Go through the wizards tocomplete the installation.

7. The Installation Package Details is displayed. Verify that the operating system and platform arecorrect for the type of package that you want to create. Also verify that the components that youwant to include are listed in the Included Components list. Provide the following information:

Name: Enter a unique name for the package.

(Optional) Description: Enter a description of the package.The description is displayed in the Monitoring Installation Packages list on the MonitoringRepository window.

Format: Select a file compression format for the package.

8. Perform one or both of the following actions:

To save the package for future installation on the current host or other hosts, click SaveInstallation Package. The package is available in the Monitoring Installation Packages list.

To download the package immediately, click Download.

If you click Download and do not click Save Installation Package, the package is not saved in the MonitoringInstallation Packages list for later use or editing.

9. When you are finished, click Close.

23Editing a Component Installation Package

Version 2.4.00


Editing a Component InstallationPackage

You can edit any part of an existing component installation package except the operating system andplatform.

1. In the navigation pane of Central Monitoring Administration, click the Repository drawer andselect Monitoring Repository.

2. (Optional) To filter the list of packages, select an operating system from the Filter by OperatingSystem list.

3. Select the row for a package and click Edit .

4. From the Available components list, add or remove components, and click Next.

5. Perform one or more of the following actions, depending on your requirements:

Edit the installation details of existing components.

Add installation details for new components.

Click Finish Update to skip to the Installation Package Details window.

If you add a component to the package, you must complete the configuration process. The Finish Update buttonshows an explanatory tooltip and does not skip to the Installation Package Details window.

6. In the Installation Package Details window, modify the following information as needed:

Name: To save your changes to the same package, do not change the name. To save thepackage under a unique name, change the name.

(Optional) Description: Enter a description of the package.The description is displayed in the Monitoring Installation Packages list on the MonitoringRepository window.

Format: Select a file compression format for the installation package.

7. Perform one or both of the following actions:

To save the package for future installation on the current host or other hosts, click SaveInstallation Package.The package is available through the Monitoring Installation Packages list.

To download the installation package immediately, click Download.

If you click Download and do not click Save Installation Package, the changes are not saved in the MonitoringInstallation Packages list for later use or editing.

8. When you are finished, click Close.

24Downloading and Installing an InstallationPackage

Version 2.4.00


Downloading and Installing anInstallation Package

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

RecommendationIf you defined the BMC ProactiveNet Integration Service variable for PATROL Agents in theinstallation package, ensure the agents are started in phases. Do not start newly deployed agents allat once. Start and configure monitoring for the agents in planned phases to reduce the performanceimpact on the Integration Service nodes and on the BMC ProactiveNet Server associated with theautomatic workflow process.

To download and install an installation package1. From the computer on which you want to install the package, log on to BMC ProactiveNet

Central Monitoring Administration.

2. (Optional) To filter the list of installation packages, select an operating system from the Filter byOperating System list.

3. Click the link for the installation package that you want to download.

4. Through the browser's download dialog box, save the installation package.

5. Extract the installation package as appropriate for your operating system. The package is extractedto the bmc_products directory on the current host.

6. 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. If the package includes a BMC PATROL Agent, the agentsends a configuration request by passing its tags to BMC ProactiveNet Central Monitoring Administration,via the Integration Service. Central Monitoring Administration evaluates policies that match the tags,determines the final configuration to be applied, and sends the configuration information back to theagent. Monitoring is based on the configuration information received by the agent.

If no policy matches the tags associated with the agent, the agent does not receive configurationinformation. The agent does not begin monitoring until a matching policy is created.

For further information regarding the Repository management, please refer to the BMC ProactiveNet CentralMonitoring Administration documentation.

Configuring After Installation

26

Version 2.4.00


You configure monitoring of Veritas Volume Manager KM when you create a policy. A policy is atemplate containing the configuration of a PATROL Agent. A policy can be assigned to one or morePATROL Agents using a unique tag (Central Monitoring Administration tag), and a PATROL Agent can beassigned one or more policies with different priorities.

If you have not already added the Central Monitoring Administration tag to your PATROL Agents duringthe solution installation, then you must manually assign the tag after you have configured the policy. Fordetails, see Adding Central Monitoring Administration Tags.

Configuring General Settings

Through the General tab of the Add Policy dialog, you can create a new policy. A policy specifies a setof actions to be taken when a specific condition on the PATROL Agent is fulfilled. First and foremost,actions include monitor configuration. Once a monitor is configured, policies can also specify thresholdcreation and the setting of baselines. A policy can also include intelligent server-side thresholds so thatIT administrators can immediately be alerted on potential problems.

Field Instructions

Name Enter a policy name. Policy names must be unique. In an environment with tenants, policy names must be unique for a single tenant

Tenant(For environments withtenants)

Select a tenant name. See Policies and tenants for details.

Global indicates a policy applicable to all tenants.

Provider indicates a policy applicable to the cloud service provider

Enable policy Select this option to enable the policy, or clear the option to disable the policy. The option isselected by default. If you clear the option, the policy and its associations remain intact, butthe policy configuration is not applied until the policy is enabled again.

Precedence Enter a number from 0 to 999.

Description (Optional) Enter a policy description.

Tag Enter a Central Monitoring Administration tag.Policies are applied to BMC PATROL Agents with matching tags.Tags are case sensitive and cannot contain spaces or any of the following characters: /, \,{, }, <, >, ‘, “, &.

Policy precedence

When more than one policy is applied to a BMC PATROL Agent and BMC ProactiveNet Child Server,configuration is a union of every attribute defined by the policies. If a conflict arises (that is, two policiesconfigure the same attributes), it is resolved in one of the following ways:

Policies with the same tag: If conflicting policies have the same tag, the precedence valuedetermines the order the policies are applied. The policy with the lower number value forprecedence is the policy from which the final configuration is applied.

Policies with different tags: If conflicting policies have different tags, then the policies areapplied according to the order they are listed on the BMC PATROL Agent. The policy listed last onthe agent is the policy from which the final configuration is applied.

27Configuring General Settings

Version 2.4.00


Managing PoliciesThis topic provides general instructions for the following policy management tasks: editing, deleting,enabling and disabling.

Before you begin

Enable Central Monitoring Administration and log on to Central Monitoring Administration. Refer to theBMC documentation and more especially to the section Enabling and configuring Central MonitoringAdministration for details.

Policies with only threshold configuration or server side configuration are applicable only after a policy with monitorconfiguration is applied.

To edit a monitoring policy1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a

policy view.

2. Select a policy and click Edit .

3. Edit the Configuring general settings of the policy.

4. Edit information on one or more of the following tabs:

Configuring monitor settings.

Configuring threshold settings.

5. Click Update.

To delete a monitoring policy

Deleting a policy deletes all monitor instances and most settings configured through the policy.Devices remain in the User Groups to which they have been added.

1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select apolicy view.

2. Select one or more policies and click Delete .

3. Click Yes to confirm deletion.

To enable or disable a monitoring policy

Enable or disable policies for maintenance and troubleshooting. When a policy is disabled, the policy andits associations remain intact, but the policy configuration is not applied until the policy is enabled again.


2. Select one or more policies and click Enable or Disable.

28Configuring Monitor Settings

Version 2.4.00


Configuring Monitor Settings

When you create or edit a policy, you can add and configure monitor types. The Add Monitor Typesdialog box presents configuration fields for compatible BMC PATROL monitoring solutions that arelocated in the Central Monitoring Repository. For a list of monitoring solutions that you can configurethrough Central Monitoring Administration, see the Monitoring solutions configurable through CentralMonitoring Administration chapter in the BPPM online documentation.

For configuration details for a specific monitor type, see the monitor documentation. To configurecustom monitoring solutions through Central Monitoring Administration, ensure the solution is structuredcorrectly; for details, see the Building a PATROL Know ledge Module Developers Guide on BMC Supportwebsite.

To configure the Monitor Type settings using the AddMonitor Types dialog box

To add a monitor type:


2. Click Add to display the Add Policy dialog box.

3. Configure the policy general settings.

4. Click the Monitor Configuration tab.


Version 2.4.00


5. Click Add

A dding Monitor Ty pes

6. From the Solution menu, select Veritas Volume Manager.

7. From the Version menu, select the required version.

8. From the Monitor Type menu, select the required monitor:

Monitor Type Description

Veritas Volume Manager KM Required for all managed systems, where the KM credentials are provided and anyconfiguration overrides are entered.

VxVM Deamon Optional monitor type to customize the monitored deamons.

VxVM Disk Device Optional monitor type to customize disk devices.

VxVM Disk Group Optional monitor type to customize disk groups.

VxVM Disk Path Optional monitor type to customize disk paths.

VxVM Plex Optional monitor type to customize plexes.

VxVM Subdisk Optional monitor type to customize subdisks.

VxVM Volume Optional monitor type to customize volumes.


Version 2.4.00


Default Monitoring Not used.

Configuring Veritas Volume Manager KMBefore using Veritas Volume Manager KM, you'll have to configure its general settings. This section willlearn you how to:

configure the user account

enable the debug mode

configure the maximum number of instances

configure the multi-node monitoring mode

configure the node discovery overrides (Optional).

Configuring the User Account

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

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

a root user

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

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

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


Version 2.4.00


an administrator user

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

To configure the user account1. Add or edit a monitor type

2. From the Monitor Type menu, select Veritas Volume Manager KM


Version 2.4.00


3. In the Hostname field, enter:

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

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

3. Set the VxVM Credentials:

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

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)

5. Click the Advanced button if you need to configure:

the debug mode

the maximum number of instances

the multi-node monitoring mode

the VxVM discovery overrides (Optional).

6. Click Add to List.

7. Click Update.

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

To enable the debug mode1. Edit a Veritas Volume Manager KM monitor type:

In the navigation pane of Central Monitoring Administration, click the Policies drawer and selecta policy view

Select a policy and click Edit

In the Monitor Configuration tab, select Veritas Volume Manager KM monitor type and

click Edit


Version 2.4.00


Editing the Veritas Volum e Manager Monitoring Settings


Version 2.4.00


2. From the List - VxVM Monitoring Settings, select the host or localhost

3. Click the Advanced button

Editing the Veritas Volum e Manager A dv anced Settings


Version 2.4.00


4. Click the Debug button

Configuring the Debug Mode

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

6. In the Options section, indicate:

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

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

7. Click Close on all pop-ups.

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 recommended to check the VVM.log file,stored in <PATROL_HOME>/log, for any error.


Version 2.4.00


Configuring the Maximum Number of Instances1. Edit a Veritas Volume Manager KM monitor type:



In the Monitor Configuration tab, select a Veritas Volume Manager monitor type and click Edit

Editing the Veritas Volum e Manager Monitoring Settings


Version 2.4.00




A dv anced Settings


Version 2.4.00


4. Click the Instance Max button

5. For each monitored element, indicate the maximum number of instances to be displayed

6. Enter 0 in the relevant field to disable the monitoring of a specific element


No max imum number of instance monitored by the KM is set by default.


Version 2.4.00


Configuring the Multi-Node Monitoring Mode

If the Veritas Volume Manager environment is installed in a cluster using Veritas Cluster Server, VeritasCluster File System, Oracle Solaris Cluster or Microsoft Cluster, Veritas Volume Manager KM must beinstalled on all the cluster nodes to enable continuous monitoring and avoid single point of failure. Toavoid duplicate alerts from multiple nodes, it is recommended to configure the solution to operate inmulti-node monitoring mode.

To configure the multi-node monitoring mode1. Edit a Veritas Volume Manager KM monitor type:



In the Monitor Configuration tab, select Veritas Volume Manager KM monitor type and click

Edit

Editing the Veritas Volum e Manager KM Monitor Ty pe


Version 2.4.00




A dv anced Settings

4. Select Enable Multi-node Monitoring Mode and click the Multi-node M... button

Configuring Multi-node Mode


Version 2.4.00


5. Configure the Multi-node Mode:

Select the appropriate Cluster Application.

Indicate the Failover Group Name. Leave this field blank if you have previously selected VeritasCluster File System. Then the Veritas Volume Manager KM will monitor the entire cluster fromthe active master system, which is identified by “vxdctl -c mode” command. This method requiresvxconfigd in enable mode with its clustered state active.

In the Monitoring Node Names field, name all the nodes where the solution is installed. The listmust be delimited by commas.

6. (Optional) Allow the solution to check the monitoring mode of the remote PATROL Agents. If the Remote PATROL Agent Checking is disabled, the solution will monitor actively through activeVVM Server system or on the node where failover group is online and will not check the monitoringstatus of the other nodes through PATROL Agent:

Check the Enable Remote PATROL Agent Checking box.

Click the Remote Agent button

Configuring the Rem ote A gent

In the Monitoring Node Name field, indicate the cluster node used for multi-node mode failover

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


Version 2.4.00


In the Number of Attempts field, indicate how many times the solution will try to communicatewith the remote PATROL Agent before failing over

Enter the timeout between attempts

Click Add to List

Resume the procedure for all the nodes previously listed in step 5


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

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

Configuring the VxVM Discovery Overrides (Optional)The solution automatically discovers the Veritas Volume Manager installation path, the DSM_DIR andDSM_LOG directory paths, the DSM_CONFIG file path, the temporary directory path used by the VeritasVolume Manager KM, the node type, and the node status. This information can however be overridden.

To configure VxVM discovery overrides1. Edit a Veritas Volume Manager KM monitor type:



In the Monitor Configuration tab, select a Veritas Volume Manager monitor type and click Edit


Version 2.4.00


Editing the Veritas Volum e Manager KM Monitor Ty pe


Version 2.4.00




A dv anced Settings

4. In the VxVM Node Discovery Overrides section, indicate:

the VxVM installation path

the temporary directory path

5. Click Close on all pop-ups

6. Click Modify Selection in the main window and click Update.


Version 2.4.00


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

Filtering options are available for all the VxVM monitor types.

To filter elements to monitor1. Add or edit a monitor type

2. Select the Monitor Type for which you wish to apply filters.

3. In the Hostname field, enter:

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. Indicate which elements will be monitored:

Click the Filtering button

In the Keep Only... section, indicate the regular expression for the element to be monitored andclick Add to List

In the Exclude... section, indicate the regular expression for the element not to be monitored andclick Add To List

Resume procedure to keep and/or exclude as many elements as required

Click Close

5. If needed, manually add elements to be monitored:

Click the Manual Add button

Indicate the element to be monitored and click Add to List

Resume procedure to add as many elements as required

Click Close

6. Click Add to List.

7. Click Add.

8. Finally, Update the policy.

Configuring Thresholds

47

Version 2.4.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 that areconfigured 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 Baselines andKey Performance Indicators section. For details about the monitored attributes, refer to the specificmonitor type in the Reference Guide section.

Before you begin

Ensure that monitor configuration is complete before thresholds are applied. Thresholds cannot beapplied to monitors that are not configured through Central Monitoring Administration. If you have notdone so already, define general policy details.

To add and configure monitor thresholds1. Open the Add Policy dialog box. Click for steps:

In the navigation pane of Central Monitoring Administration, click the Policies drawer and select apolicy view.

Click Add , or select an existing policy and click Edit .

2. Select the Threshold Configuration tab and click Add .

3. In the Add Thresholds dialog box, select an item from each of the following lists: Solution,Version, and Monitor Type. Configuration fields are displayed.

4. In the Scope list, the Instance option is automatically selected. Type an Instance Name string orregular expression to apply threshold configuration to instances with matching patterns. Select Match Device Name to include the associated device and use the entire<deviceName>\<instanceName> string for pattern matching. Instance thresholds are applied to thematched monitor instance names or instance names patterns.You can use the following regular expression patterns for the instance name: ?, +, *, ( ), |, [ ], { },

,̂ $, .If the instance name contains one of the pattern characters (except for *), use a backslash ( \ )before the pattern character. For example, to enter the instance name Storage1 (1), enterStorage1 $1$.

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

In the A ttribute list, some attributes are designated as key performance indicators (KPIs). Depending on themonitored env ironment and version, the list of KPIs might appear differently in the BMC ProactiveNet OperationsConsole.

6. From the Type of Threshold list, select the threshold type.

7. Select and enter values for the threshold parameters.

8. To continue configuration, perform one or more of the following actions in the Add Thresholdsdialog box, and then select a different monitor type, version, or solution:

To add the configuration details for the threshold to the Threshold Configuration tab, click theAdd button at the bottom of the window.

To return the settings in the current window to default values, click the Reset button at thebottom of the window. The values on the current window are reset. Be sure to click the Addbutton to save the configuration on the Threshold Configuration tab.

48

Version 2.4.00


9. When you finish configuration, click Close. The configuration details are displayed in the table onthe Threshold Configuration tab.

10. When you finish configuring thresholds, click Save at the bottom of the Add Policy dialog box, orUpdate at the bottom of the Edit Policy dialog box.

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

To edit a threshold configuration1. On the Threshold Configuration tab, select a threshold definition, and click Edit.

2. Edit the configuration values and click Update.

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

4. 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 Agents withmatching Central Monitoring Configuration tags.

To delete a threshold configuration1. On the Threshold Configuration tab, select attributes, monitor types, versions, or

solutions.

2. Click Delete.

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

4. 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 PATROL Agentswith matching Central Monitoring Configuration tags.

Recommended Thresholds

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

Using BMC ProactiveNetPerformance Management

50

Version 2.4.00


This section provides a brief overview of how to navigate and use the product in the BMC ProactiveNetOperations Console.

Navigating the BMC ProactiveNet Operations Console

Adding attributes to the graph

Viewing and manipulating attribute graphs

Viewing monitors for a device

Changing Thresholds

For more detailed information, see BMC ProactiveNet User Guide in the PDF product guides.

Navigating the BMC ProactiveNetOperations Console

The BMC ProactiveNet Operations Console is a Web-based application that provides options to navigatethrough BMC ProactiveNet and view all of the information collected and computed by the BMCProactiveNet Server related to events, views, and graphs.

Navigation tree

The navigation tree shows an at-a-glance synopsis of events and views. Event and component foldersare displayed hierarchically and are divided into the following categories, or nodes.

Object Definition

Global node The Global node contains the following default collectors:All Event Collectors—displays the entire event collector hierarchyAll Abnormalities—displays all the abnormality eventsAll Services—displays all the servicesAll Groups—displays all the groupsAll Devices—displays all the devicesBased on permissions, users can create event and component folders under this node to organize theevent view.

My Foldernode

Based on permissions, users can create event and component folders under this node to organize theevent view.

To further organize your display, beneath these top-level folders you can add event and componentfolders, including folders for Component Instances (CIs) associated with a service model. Your ability toadd event and component folders depends on your permissions.

The severity icons for a collector dynamically change depending on the severity level of the events forthat collector.

For example, if there is a Critical event on one of the devices, the green icon changes to a red icon,indicating a Critical event. The icons enable you to see the status of devices on your system

51Navigating the BMC ProactiveNet OperationsConsole

Version 2.4.00


immediately.

For complete details, see the BMC ProactiveNet Getting Started Guide on the BMC Support website.

Navigation drawers

The navigation pane in the Operations Console contains a series of drawers that enable you to navigatethrough BMC ProactiveNet functions and views. You can select which drawers to display in thenavigation pane.

The following table describes the available drawers in the navigation pane and describes their functions.

Drawer Description

Main Provides access to event lists and displays event information and status.

Other cells Lists available remote cells connected to the BMC ProactiveNet Server and monitored by BMCProactiveNet.

Reports Enables you to generate and manage reports based on data collected by BMC ProactiveNet.Note: You must have permission to view this drawer.

Views & graphs Provides options for the management of views and graphs in the Operations Console

Bookmarks Enables you to view, rename, and delete bookmarks of objects and their related views that youcreate in the navigation tree.

Find CI Provides a search mechanism so that you can search for Component Instances that meet thespecified search criteria.Note: You must have permission to view this drawer.

Event and component folders

Event and component folders enable you to organize cells and collectors to make event displaysmeaningful for operators. For example, you might create an event folder for collectors that gatherdatabase warning events and allow only operators who are database administrators access to thatevent folder. You can drag components from one existing folder to another within the top-level folders inthe navigation tree. You also can drag and drop CIs from the Tile or Graph view to an existing folder inthe All Services folder.

Event folders

An event folder is a grouping of collectors that shows the relationship of events or abnormalities throughthe hierarchy of the navigation tree. Administrators define event folders and associate them with one ormore collectors. Each level of the collector is shown as a node under the event folder. An event list isassociated with the lowest level nodes of an event folder. The parent level of an event folder representsall of the events or abnormalities associated with the collectors.


Version 2.4.00


Event collectors

Event collectors gather events for display in an event list to provide operators with meaningful groups ofevents or abnormalities and to show relationship through the hierarchy of the nodes in the navigationtree. To access the event list for a collector, operators click the collector node in the navigation tree.Event collectors are dynamic or static. Nodes for dynamic collectors appear or disappear from thenavigation tree based on whether or not events are present that meet the criteria for those collectors.Nodes for static collectors remain in the navigation tree regardless of whether events are present ornot.

Component folders

A component folder is a grouping of groups, services, or devices from several different event lists(collectors) that shows the relationship of groups, services, or devices through the hierarchy of thenavigation tree. Administrators define component folders and associate them with one or more groups,services, or devices. Each level of the component folder is shown as a node under the parentcomponent folder. An event list is associated with the lowest level nodes of a component folder. Theparent level of a component folder represents all of the events associated with the groups, services, ordevices. Component folders are static or dynamic. You populate static component folders by selectingfrom a list of objects. You populate dynamic component folders by creating a query. Static foldersalways contain only the objects that you manually select. Dynamic folders contain the objects that matchthe query, so the contents of these folders can change without further editing.

Operations Console views

The following table shows the different views that are available, depending on what object you select inthe navigation tree. Each view is accessed by clicking the associated Console view icon. If a view is notavailable for the object that is selected in the navigation tree, the icon for that view is not displayed inthe toolbar.

View Description

Event The Event view displays all events in an event list. This is the default view for all objects. Use the Eventview to check the details of events and to address events that highlight incorrect state. Probable CauseAnalysis can help you to identify the cause of the event. An event could be assigned to other users, whocan acknowledge and take ownership of the event, fix the problem, and close the event. You can alsoaddress the incorrect condition by invoking remote actions, detailed diagnostics, and local actions. TheGraph view helps check the impacting service and you can cross-launch to Impact Model Designer, ServiceLevel Manager and Product Catalog in BMC Remedy IT Service Management (BMC Remedy ITSM).You can display an Event view for:

Event collectors

Abnormalities

Services

Groups

Devices

Monitors


Version 2.4.00


View Description

Title The Canvas view enables you to create a graphical representation of the components that are beingmonitored in your environment. The components are represented by objects that you can place on abackground image. The objects can be graphics, such as images or connectors, or metrics informationrepresented in a tile.You can create and display a Canvas view for:

Event collectors

services

Groups

Devices

Tree/Graph

The Tree/Graph view displays information for a selected object as a tree that represents the hierarchy ofthe object. The Tree view is available for groups and services. You can use the Tree view to get a real-time,interactive visualization of the event status and other details of the selected group or service. In the Grouphyperbolic tree, the entire group hierarchy and devices are visible on a hyperbolic pane that is mapped to acircular display region. Service tree is applicable only for the selected service.If a service is selected in the navigation tree, this view displays a graphical representation of theconfiguration items in the service model and shows how those configuration items relate to each other. Usethe Graph view to monitor events for published service models that represent your business services.You can display a Tree/Graph view for:

Services

Groups

Grid Grid view displays information for the selected object in a tabular format. you can view the event status andother details of the selected object through hyperlinks to graphs, views, etc. You can display a Grid viewfor:

Abnormalities

Groups

Devices

For more detailed information, BMC ProactiveNet Getting Started Guide on the BMC Support website.

Adding attributes to the graph

Following configuration, only one attribute is enabled for the graph of each monitor. You might want toadd additional attributes to the monitor graph.

1. In the BMC ProactiveNet Operations console, select the Navigation drawer.

2. Select Global > Devices.

3. Select the Grid view.All the monitored devices are displayed in table format.

4. Select a device from the displayed table.

5. Select a monitor.

6. Click Tools >Show Graph

7. Select the Attributes & Indicators tab.

8. Select one or more attributes.Up to 12 attributes of a monitor can be displayed on a single graph. Though only two units ofmeasurement can be used.

54Viewing and manipulating attribute graphs

Version 2.4.00


Viewing and manipulating attributegraphs

The graph provides a visual display of the attributes of a monitor. Up to 12 attributes of a monitor canbe displayed on a single graph.

1. In the BMC ProactiveNet Operations console, select the Navigation drawer.


3. Select the Grid view. All the monitored devices are displayed in table format.

4. Select a device from the table.


6. Click Tools > Show Graph

If Collect Data is not enabled then no data is available.

The Graph Display window opens, displaying a graph displaying the values of the selected attributes forthis monitor.You can use the options available on this tab to manipulate the graph. For complete details, refer toBMC ProactiveNet User Guide on the BMC Support website.

Viewing monitors for a device

This section provides a brief overview of how to view the monitors for a selected device. For completedetails, refer to BMC ProactiveNet User Guide on the BMC Support website.

To view the Monitor types for a device1. In the BMC ProactiveNet Operations console, select the Navigation drawer.



4. Select a device from the table. A hierarchical tree listing the monitors for that device is displayed.You can click the + and - to expand and collapse nodes of the hierarchical tree.

The following information is displayed:

Information Description

Monitor Name Device name or process name, a device might appear more than once if it is monitored byseveral PATROL Agents

Monitor Type Name of the monitor type.This will correspond to the element displayed in the Monitor Name column, specifying thetype of device or process monitored

55Viewing monitors for a device

Version 2.4.00


Information Description

Source Agent ProactiveNet server where the PATROL Agent and integration service are running

Open Number of open alerts, a green globe is displayed if no alerts are open

Closed Number of closed alerts

Enabled Enabled if data is being collected

Changing thresholds

You can adjust the thresholds for the attributes of a monitor type either globally or for a specific deviceinstance. In the BMC ProactiveNet Operations console, select the Navigation drawer.



3. Select a device from the table.


5. Select Tools > Thresholds. A menu containing the available thresholds is displayed.

Global thresholds are applied to all monitor instances of the selected monitor type. Instance thresholds are applied tothe selected monitor instance.

6. Edit the Threshold settings

7. Click Apply.

Managing Baselines and KeyPerformance Indicators

In order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNetcalculates baselines per attributes based on values collected over a specified period of time todetermine a normal operating range. When the collected values for these attributes are out of range, analert is triggered.

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

Managing baselines

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

The baseline is calculated by collecting the values for a monitor’s attributes and metrics over a specified

56Managing Baselines and Key PerformanceIndicators

Version 2.4.00


time period and establishing a low baseline value (consisting of the 10th percentile of all the values for agiven time period) and a high baseline value (consisting of the 90th percentile of all the values for agiven time period), taking a weighted average of these values over time. A higher weight is given to thelatest data being factored into the baseline average. The accuracy of the baseline improves over time.

Requirements for baseline generation

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

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

Managing Key Performance Indicators

The KPI attribute of an attribute can be activated or deactivated manually through the BMC ProactiveNetAdministration Console. In this KM, some attributes have been designated as important indicators ofperformance (KPIs). We do not recommend that these default settings are modified.

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

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

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

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

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

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

deselect the KPI check box to remove the corresponding attribute from the KPIs for that monitortype

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

Attributes considered as KPIs are respectively identified by the following icon: .

Reference Guide

58

Version 2.4.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 in the KM,grouped by Monitor Types, and provides a brief description of each attribute and its default settings.

Monitor Types

Veritas Volume Manager KM

VxVM Deamon

VxVM Disk Device

VxVM Disk Group

VxVM Disk Path

VxVM Log

VxVM Plex

VxVM Subdisk

VxVM Volume

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

59

Version 2.4.00


VxVM Deamon

Attributes

Name Description Units RecommendedAlertConditions

BPPMAttribute Type

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

CPU

Utilization*

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

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

KB None Statistics

Processes

Count

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

processes None Statistics

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

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

None Availability

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

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

Warning =1Alarm = 2

Availability

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

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

60VxVM Disk Device

Version 2.4.00


VxVM Disk Device

Attributes

Name Description Units DefaultAlertConditions

BMCProactiveNetAttribute Type

Diskdevice SpaceAvailable

Indicates the available space on the diskdevice. GB None Availability

Enabled Disk Paths Monitors the number of enabled disk paths withkernel state ENABLED.

count Alarm = 0 Availability

IO Kbytes Rate* Indicates the number of KBytes transferred persecond for the diskdevice.

KB/s None Statistics

IO KBytes Indicates the total number of KBytes transferred onthe diskdevice.

KB None Statistics

IO Operations

Failed

Indicates the total number of failed input and outputoperations on the diskdevice on Unix platforms.

operations None Statistics

IO Operations

Rate

Indicates the number of input and output operationsper second for the diskdevice.

operations/second None Statistics

IO Operations Indicates the total number of input and outputoperations on the diskdevice.


Non-Enabled DiskPaths

Indicates the number of disk paths that are notenabled.

count Warning: 1-100Alarm if outof [-1 to100] range.

Availability

Queue Depth Indicates the number of read and write requests inqueue for the diskdevice on Windows platforms.

requests None Statistics

Read KBytesRate*

Indicates the number of KBytes read per second forthe diskdevice.


Read KBytes Indicates the number of KBytes read on thediskdevice.

KB None Statistics

Read OperationsFailed

Monitors the number of failed read operations onthe diskdevice on Unix platforms. If this parameterchanges to warning or alarm state, the recoveryaction will trigger an event.

operations Warning:10-100Alarm if outof [0 to100] range.

Statistics

Read Operations Indicates the number of read operations on thediskdevice.


Read TimeAverage*

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

milliseconds None Statistics

Read Time* Monitors the read time for the diskdevice. If thisparameter changes to warning or alarm state, therecovery action will trigger an event.

milliseconds Warning:20-100

ResponseTime

61VxVM Disk Device

Version 2.4.00


Alarm if outof [0 to100] range.

State (Windows) Indicates the state of the diskdevice on Windowsplatforms.

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

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

Warning =1Alarm = 2

Availability

Write KBytes

Rate*

Indicates the number of KBytes written per secondfor the diskdevice.


Write KBytes Indicates the number of KBytes written on thediskdevice.

KB None Statistics

Write Operations

Failed

Monitors the number of failed write operations onthe diskdevice on Unix platforms. If this parameterchanges to warning or alarm state, the recoveryaction will trigger an event.


Statistics

Write Operations Indicates the number of write operations on thediskdevice.


Write TimeAverage*

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

milliseconds Warning:20-100

Statistics

Write Time* Monitors the write time for the diskdevice. If thisparameter changes to warning or alarm state, therecovery action will trigger an event.

milliseconds Warning:20-100Alarm if outof [0 to100] range.

ResponseTime



62VxVM Disk Group

Version 2.4.00


VxVM Disk Group

Attributes


BMCProactiveNetAttributeType

Space Available* Indicates the available space for the diskgroup. GB None Availability

State (Windows) Indicates the state of the diskgroup on Windowsplatforms.

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

None Availability

State Indicates the state of the diskgroup on Unixplatforms.

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

None Availability

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

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

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

Warning =1Alarm = 2

Availability


VxVM Disk Path

Attributes



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 on Unixplatforms

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

None Availability

63VxVM Disk Path

Version 2.4.00


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

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

Warning = 1Alarm = 2

Availability

VxVM Log

Attributes



Alarm MessageCount*

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

count Alarm: 1-100Alarm if outof [0 to100] range.

Statistics

File Space GrowthRate

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


File Space Used Displays the amount of space used by the log file. KB None Statistics

Filesystem Space

Used Percent*

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

% Warning:95- 98Alarm: 98-100Alarm if outof [0 to100] range.

Statistics

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

MB Warning: -1-2Alarm: 2-5

Availability

Space UsedPercent*

Monitors the percentage of capacity used by the logfile.If this parameter changes to warning or alarm state,the recovery action will trigger an event.Note that the total capacity is the used space(VVMLogSpaceUsed) plus available space(VVMLogSpaceAvailable).

% Warning:95- 98Alarm: 98-100Alarm if outof [0 to100] range.

Statistics

Warning MessageCount*

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

count Warning: 1-100Alarm if outof [0 to100] range.

Statistics



64VxVM Plex

Version 2.4.00


VxVM Plex

Attributes



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


IO KBytes Indicates the total number of KBytes transferredon the plex.

KB None Statistics

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


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

operations/second

None Statistics

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



Indicates the kernel state of the plex on Windowsplatforms.

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

None Availability

Kernel State Indicates the kernel state of the plex on Unixplatforms.

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

None Availability

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

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


Availability

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


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

KB None Statistics

Read Operations

Failed

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


Statistics

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


65VxVM Plex

Version 2.4.00


Read Time Average* Monitors the average read time for the plex onUnix platforms.If this parameter changes to warning or alarmstate, the recovery action will trigger an event.


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


ResponseTime

State (Windows) Displays the state of the plex on Windowsplatforms.

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

None Availability

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

None Availability

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

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


Availability

Write KByte Indicates the number of KBytes written on the plexon Unix platforms.

KB None Statistics

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


Write Operations

Failed

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


Statistics

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


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


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


ResponseTime

66VxVM Plex

Version 2.4.00




Veritas Volume Manager KM

Attributes



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



CollectionStatus

MonitoringMode*

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

None CollectionStatus

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



Availability


67VxVM Subdisk

Version 2.4.00


VxVM Subdisk

Attributes



IO KBytes Rate* Indicates the number of KBytes transferred persecond for the subdisk.


IO KBytes Indicates the total number of KBytestransferred on the subdisk.

KB None Statistics

IO Operations Failed

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


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

operations/second

None Statistics

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



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 subdisk on Unixplatforms.

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

None Availability

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

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


Availability

Read KBytes Rate* Indicates the number of KBytes read per secondfor the subdisk.


Read KBytes Indicates the number of KBytes read on thesubdisk.

KB None Statistics

Read Operations

Failed

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

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

Statistics

Read Operations* Indicates the number of read operations on thesubdisk.


Read Time Average* Monitors the average read time for the subdisk. milliseconds None Statistics

68VxVM Subdisk

Version 2.4.00


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

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

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

ResponseTime

Write KBytes Rate* Indicates the number of KBytes written persecond for the subdisk.


Write KBytes Indicates the number of KBytes written on thesubdisk.

KB None Statistics

Write Operations

Failed

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

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

Statistics

Write Operations Indicates the number of write operations on thesubdisk.


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


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

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

ResponseTime



VxVM Volume

Attributes



IO KBytes Rate* Indicates the number of KBytes transferred per

second for the volume.KB/s None Statistics

IO KBytes Indicates the total number of KBytes transferredon the volume.

KB None Statistics

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


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

operations/second

None Statistics

69VxVM Volume

Version 2.4.00


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


Kernel State (Windows) Indicates the kernel state of the volume onWindows platforms.

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

None Availability

Kernel State Indicates the kernel state of the volume on Unixplatforms.

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

None Availability

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

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

Warning =1Alarm = 2

Availability

Logging State Indicates the logging state of the volume on Unix

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

None Availability

Logging Status Monitors the logging status of the volume on Unixplatforms. This status is determined by the volumestatus mapping rule defined in the KM commandConfiguration > Volume(s) Logging Status.If this status parameter changes to warning oralarm state, the recovery action will trigger anevent and annotate the last data point.

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

Warning =1Alarm = 2

Availability

Read KBytes Rate* Indicates the number of KBytes read per secondfor the volume.


Read KBytes Indicates the number of KBytes read on thevolume.

KB None Statistics

Read Operations Failed

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


Statistics

Read Operations Indicates the number of read operations on thevolume.


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


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


ResponseTime

70VxVM Volume

Version 2.4.00


State (Windows) Indicates the state of the volume on Windowsplatforms.

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

None Availability

State Indicates the state of the volume on Unixplatforms.

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

None Availability

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


Warning =1Alarm = 2

Availability

Write KBytes Rate* Indicates the number of KBytes written per secondfor the volume.


Write KBytes Indicates the number of KBytes written on thevolume.

KB None Statistics

Write Operations Failed

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


Statistics

Write Operations Indicates the number of write operations on thevolume.


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


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


ResponseTime



About BMC® SoftwareBMC Software, Inc. NYSE:BMC, is a leading provider of enterprise managementsolutions that empower companies to manage their IT infrastructure from abusiness perspective. Delivering Business Service Management, BMC Softwaresolutions span enterprise systems, applications, databases, and servicemanagement. Founded in 1980, BMC Software has offices worldwide and fiscal2004 revenues of more than $1.4 billion. For more information about BMC

Software, visit www.bmc.com.

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software,provides key monitoring solutions specifically designed to expand thecapabilities of BMC Performance Manager, thus enabling up to 100% coverage ofany infrastructure. Sentry Software specializes in single solutions for multi-platform monitoring of hardware, custom applications or any IT component, andblackout windows. Sentry Software products are deployed in 45 countries acrossthe globe and lead the list of BMC Software’s third-party product sales. For more

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

BMC ProactiveNet - Veritas Volume Manager Monitoring · PDF file11 Version 2.4.00 BMC...

Documents

Transcript of BMC ProactiveNet - Veritas Volume Manager Monitoring · PDF file11 Version 2.4.00 BMC...