BMC ProactiveNet Performance Management - Veritas Cluster Server Monitoring

Transcription

1 USER DOCUMENTATION HIGH AVAILABILITY MONITORING BMC ProactiveNet Performance Management - Veritas Cluster Server Monitoring Version September 2015

2 Contacting BMC Software You can access the BMC Software Web site at From this Web site, you can obtain information about the company, its products, corporate offices, special events, and career opportunities. United States and Canada Address BMC Software, Inc CityWest Blvd. Houston TX Telephone 1 (713) or 1 (800) (Toll Free) Copyright 2006 BMC Software, Inc. or licensors, as an unpublished work. All rights reserved. All other trademarks belong to their respective companies. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation. Restricted Rights Legend U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section , DFARS , DFARS , DFARS , and DFARS , as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX , USA. Any contract notices should be sent to this address. 2 BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc.

3 Customer Support You can obtain technical support by using the Support page on the BMC Software Web site or by contacting Customer Support by telephone or . Support Web Site Read overviews about support services and programs that BMC Software offers Find the most current information about BMC Software products Search a database for problems similar to yours and possible solutions Order or download product documentation Report a problem or ask a question Subscribe to receive notices when new product versions are released Find worldwide BMC Software support center locations and contact information, including addresses, fax numbers, and telephone numbers You can also access product documents and search the Knowledge Base for help with an issue at Support by Telephone or In the United States and Canada, if you need technical support and do not have access to the Web, call Outside the United States and Canada, please contact your local support center for assistance. To find telephone and contact information for the BMC Software support center that services your location, refer to the Contact Customer Support section of the Support page on the BMC Software Web site at 3 You can obtain technical support from BMC Software 24 hours a day, 7 days a week at From this Web site, you can:

4 Table of Contents...9 User Goals and Features Business...9 Value...10 Requirements...10 System Requirements...10 Software Requirements...11 Security Requirements Adding...16 Central Monitoring Administration Tags...18 Preparing for Installation...19 Creating a Component Installation Package Editing...21 a Component Installation Package...22 Downloading and Installing an Installation Package...24 Configuring General Settings...26 Configuring Monitor Settings...28 Configuring Veritas Cluster Server KM...28 Configuring the User Account...30 Enabling the Debug Mode...34 Configuring the Maximum Number of Instances...37 Configuring the Multi-Node Monitoring Mode...42 Configuring the VCS Server Discovery Overrides (Optional)...44 Filtering Elements to Monitor...45 Configuring the Log Scan Limit...46 Configuring Thresholds...46 Configuring Monitor Thresholds...47 Editing a Threshold Configuration...47 Deleting a Threshold Configuration...48 Using BMC ProactiveNet Performance Management...48 Navigating the BMC ProactiveNet Operations Console...52 Adding attributes to the graph...52 Viewing and manipulating attribute graphs...53 Viewing monitors for a device...53 Changing thresholds Managing Policies

5 Veritas...58 Cluster Server KM...59 VCS Agent...60 VCS Agents...61 VCS Daemon...62 VCS Daemons...63 VCS GAB...64 VCS GAB Port...65 VCS Group System VCS LLT...66 VCS LLT...67 Interface VCS Log VCS Logs...70 VCS Resource...71 VCS Resources...72 VCS Resource System...73 VCS Service Group...74 VCS Service Groups...75 VCS System...78 VCS Systems...79 VCS System Heartbeat...80 VCS WAN Heartbeat...81 VCS WAN Heartbeats Managing Baselines and Key Performance Indicators

6 Release Notes for v2.5.01

7 What's New VCS-257/KMF-328: Inactive standard attributes labeled Exec Time were added to monitor the performance of each collector. Please refer to the Reference Guide for detailed information. VCS-266/KMF-396: It is now possible to customize the VCS log scan limit from CMA. Changes and Improvements VCS-185: Improved performance on Linux platforms. VCS-265/KMF-390: The status report file of BMC ProactiveNet Performance Management Veritas Cluster Server Monitoring is now suffixed with the Agent port number to avoid overwritting it when multiple virtual Agents are monitored. VCS-143/KMF-295: Component monitoring could not be disabled from BMC ProactiveNet Central Monitoring Administration. VCS-150: WAN heartbeat status was not monitored correctly on Windows cluster nodes. VCS-151: In large VCS clusters high CPU usage was observed with heavy I/O. The resource and service group status commands used by the VCSGroupCollector and VCSResourceCollector have therefore been changed to avoid processing large command outputs. VCS-166: A compatibility issue prevented the KM to operate when the PATROL Agent v9.0.20i was run with the PATROL Config Cache support. VCS-173: On Windows platforms, the KM was sometimes unable to automatically discover the relevant library path. VCS-191: The State attribute of the VCS GAB Port monitor was improperly set to 0 (Membership) when the state of the GAB port was Jeopardy. VCS-211: The Failover Status attributes of the VCS Group System and VCS Resource monitor types could trigger invalid warnings. VCS-218: The main discovery cycle was irregular due to an asynchronous default KM discovery interval. It is now reduced to 30 seconds to avoid such irregularity. VCS-224: The Sudo configuration in the sudoers file must be modified for Solaris, HP-UX, AIX and Linux to prevent Veritas Cluster Server commands failures (see Security Requirements). VCS-243: The Login Status attribute was in warning due to an incorrect configuration variable used while checking the active cluster node. VCS-244: During a long VCS failover, the value of the Monitoring Mode attribute was switching from its actual state to Temporary Single-node Mode. This issue is now fixed and the value remains unchanged until the number of failover attempts are exhausted. VCS-256/KMF-334: On Windows systems, the monitoring solution did not correctly detect running VCS daemons which resulted in invalid alarms for the Node Status and Daemon Status attributes. VCS-258/KMF-318: On Unix platforms, daemon collector command & arguments are modified to return only the relevant daemon lines from the process list. VCS-271/KMF-402: On Windows systems, if the PATROL Agent installation path contained spaces, scripts calls and output redirection commands failed. 7 Fixed Issues

8 Key Concepts

9 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 brevity, reference to BMC ProactiveNet Performance Management - Veritas Cluster Server Monitoring, may also be made as Veritas Cluster Server KM. User Goals and Features Systems: each cluster node health, including the critical processes and system status. Heartbeats: monitors the heartbeats between nodes and global clusters. LLT & GAB: monitors both LLT and GAB protocol health and memberships. Resources & Service Groups: monitors the status of resources and their member system status. Logs: checks for any errors in VCS logs and system logs regularly. Agents: monitors the status of VCS agents for successful failover. Automatic KM Failover: in the event of a VCS failover, the KM continues the monitoring through the new active node. Business Value BMC ProactiveNet Performance Management - Veritas Cluster Server Monitoring provides current and historical information through a centralized console so you can easily view and manage your entire Veritas Cluster Server environment. The product collects and brings critical performance data and useful metrics into the BMC ProactiveNet Performance Management environment and enables Veritas Administrators and affected business units to be warned whenever a problem occurs in their Veritas Cluster Server environment. BMC ProactiveNet Performance Management - Veritas Cluster Server Monitoring: Enhances productivity Ensures VCS core components are available at all times Provides an end-to-end monitoring of Veritas clusters by integrating with clustered application monitoring. 9 Veritas Cluster Server KM enables you to monitor:

10 Requirements Before installing the Veritas Cluster Server KM, verify the: software requirements system requirements security requirements. System Requirements The following list shows the operating systems and their versions supported by BMC ProactiveNet Performance Management - Veritas Cluster Server Monitoring. Software Requirements The following table contains a list of required software and their versions supported by BMC ProactiveNet Performance Management - Veritas Cluster Server Monitoring. Software Version Veritas Cluster Server 4.0 (all multi-packs) 4.1 (all multi-packs) 5.0 (all multi-packs) 6.0 (all multi-packs) BMC Software PATROL Agent 3.7.x, 3.8.x, 3.9.x, 9.x BMC Software PATROL Console 3.4.x, 3.5.x, 7.x BMC ProactiveNet Performance Management Portal 2.3.x, 2.4.x, 2.5.x, 2.6.x, 2.7.x, 2.8.x BMC ProactiveNet Performance Manager 8.x, 8.5.x, 8.6.x, 9.x BMC TrueSight Operations Management 10.0 Requirements 10 Microsoft Windows Server 2003, 2008 and 2012, all versions supported by BMC PATROL Agent 3.7 and greater Linux, all distributions supported by BMC PATROL Agent 3.7 and greater Sun Solaris 8, 9, 10, 11 supported by BMC PATROL Agent 3.7 and greater HP-UX 11, supported by BMC PATROL Agent 3.7 and greater IBM AIX 5.x and 6.x, supported by BMC PATROL Agent 3.7 and greater

11 If the version of Veritas Cluster Server is upgraded (or downgraded) at a later date, you will need to reload commands for the VCS KM. Additional Software Requirements Purpose Software Version When running VCS KM with sudo user account on Solaris, HP-UX, AIX or Linux managed nodes Sudo (superuser do) or later When running VCS KM on Linux managed nodes Korn shell binary (/bin/ksh) Any When running VCS KM on Microsoft Windows x64 managed nodes Reg.exe patch KB ( kb/948698) Any The Microsoft Windows x64 Reg.exe patch, KB is required to allow access to 64-bit registry keys from PATROL Agent. Access the above patch site from the managed node to obtain the correct patch for that platform. Security Requirements A user account with administrative privileges must be configured in BMC PATROL to read and execute Veritas Cluster Server application programs and access file systems. Depending on the operating systems used, several options will be available. The following user accounts can be used: On Unix platforms: a root user a non-root user, such as patrol, that has sudo privileges on Veritas Cluster Server to execute application programs and access file systems a non-root account, such as patrol, configured in Veritas Cluster Server application to administer the Veritas Cluster Server application. On Windows platforms: an administrator user a non-administrator account, such as patrol, configured in Veritas Cluster Server application to administer the Veritas Cluster Server application. 11 Requirements The following table contains a list of additional software requirements of BMC ProactiveNet Performance Management - Veritas Cluster Server Monitoring.

12 The user login details are configured in the KM. 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 Agent configuration variables (pconfig). This user could then execute PSL statements using the encrypted password through the PATROL Console. This can be prevented by setting up an appropriate Access Control List (ACL) for users. Please refer to the PATROL Agent Reference Manual for details on how to set up an ACL. Access Permissions Paths Microsoft Windows INSTALL_PATH/bin/ha* INSTALL_PATH\Cluster Server\bin\ha* /sbin/llt* INSTALL_PATH\comms\llt* /sbin/gab* INSTALL_PATH\comms\gab* INSTALL_PATH/lib INSTALL_PATH\Cluster Server\lib /usr/lib INSTALL_PATH\Cluster Server The Veritas Cluster Server KM includes some scripts which should be executable by the PATROL Agent user and the Veritas Cluster Server KM user. These scripts are stored under KM_HOME path, normally PATROL_HOME/lib/VCS. To list all OS commands used by the Veritas Cluster Server KM, execute the following PSL code from the PATROL Console, using PSL Task menu, after installing and loading the KM. i=0; sudoers=""; foreach var (grep("^/runtime/vcs/commandcontrols/",pconfig("list"))) { ctl=get(var); opt=ntharg(grep("option",ctl),"2-"," ="); nsa=ntharg(grep("nosudoattempt",ctl),"2-"," ="); sua=ntharg(grep("singleuserattempt",ctl),"2-"," ="); typ=ntharg(grep("commandtype",ctl),"2-"," ="); cmd=nthargf(grep("commandtext",ctl),"2-","=","="); if((typ == "") (typ == "OS")) { met=""; if(opt == "NoLogin") { met = "(run as patrol user)"; } elsif(nsa == "YES") { met = "(run as configured user without sudo)"; } elsif(sua == "YES") { met = "(run as supplied user - used in menu)"; } else { Requirements 12 The Veritas Cluster Server KM needs read & execute permission to executable and library files under the paths listed below.the Veritas Cluster Server installation path INSTALL_PATH, referenced in the tables below, is normally /opt/vrtsvcs (on Unix) or C:\Program Files\Veritas (on Microsoft Windows).

13 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 permission to the following files: UNIX Microsoft Windows /var/vrtsvcs/log/engine_a.log INSTALL_PATH\Cluster Server\log\engine_A.txt /var/vrtsvcs/log/hashadow-err_a.log INSTALL_PATH\Cluster Server\log\hashadowerr_A.txt /var/adm/messages (on Solaris) /var/adm/syslog/syslog.log (on HP-UX) If a monitored log file cannot be read by the PATROL Agent user, it will be copied to KM_TEMP path using the configured login account, and processed by the PATROL Agent user. On completion the copied log file will be removed. This may increase the file system usage under KM_TEMP temporarily during this activity. On Windows platforms the Veritas Cluster Server installation is identified by checking the Microsoft Windows Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\VCS\ The configured login user should have sufficient privileges to run regedit command on the managed node. Sudo User for Operating System Access If a non-root user with sudo privileges is preferred as the Veritas Cluster Server KM user, configure the account as a sudoer through the visudo utility using code appropriate for your platform as detailed below. This user should be able to execute VCS commands and OS commands. The code below also applies to all non-root users who may execute Veritas Cluster Server KM administration and report menu commands using their sudo privileges. The Veritas Cluster Server KM accepts any non-root user with the following sudo configuration in the sudoers file. Please replace user1, user2, user3 with appropriate KM user name. The Veritas Cluster Server installation path INSTALL_PATH, referenced below is normally /opt/vrtsvcs and PATROL_HOME is the path where the PATROL Agent is installed (including the target, like /opt/bmc/patrol3/ Solaris29-sun4/). 13 Requirements /var/log/messages (on Linux)

14 This non-root sudo user configured in the KM will be able to execute Veritas Cluster Server commands. To prevent unauthorized access, ensure this user is only used within the KM and not made public for general use. Entering the non-root sudo user with Use Sudo option selected in to the login configuration dialog, before updating the sudoers file, will generate sudo errors. Also if the sudo user is configured differently, the KM may run sudo commands using incorrect sudo settings, which may expose the sudo user password. On Solaris: User_Alias VCSKMUSERS = user1, user2, user3 Defaults:VCSKMUSERS!lecture,!authenticate,!requiretty,\ env_keep+="path LD_LIBRARY_PATH INSTALL_PATH KM_HOME \ KM_TEMP",env_reset VCSKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\ INSTALL_PATH/bin/ha*,\ PATROL_HOME/lib/VCS/*,PATROL_HOME/bin/* On HP-UX: User_Alias VCSKMUSERS = user1, user2, user3 Defaults:VCSKMUSERS!lecture,!authenticate,!requiretty,\ env_keep+="path SHLIB_PATH INSTALL_PATH KM_HOME \ KM_TEMP",env_reset VCSKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\ INSTALL_PATH/bin/ha*,\ PATROL_HOME/lib/VCS/*,PATROL_HOME/bin/* user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH and PATROL_HOME with the relevant paths. On AIX & Linux: User_Alias VCSKMUSERS = user1, user2, user3 Defaults:VCSKMUSERS!lecture,!authenticate,!requiretty,\ env_keep+="path LIBPATH INSTALL_PATH KM_HOME \ KM_TEMP",env_reset VCSKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\ INSTALL_PATH/bin/ha*,\ PATROL_HOME/lib/VCS/*,PATROL_HOME/bin/* user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH and PATROL_HOME with the relevant paths. Requirements 14 user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH and PATROL_HOME with the relevant paths.

15 Planning

16 Adding Central Monitoring Administration 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 is fulfilled. 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 You can add a PATROL Agent and set the tag as part of the configuration process that you perform from Central Monitoring Administration. For details, see Managing downloads in Central Monitoring Administration. If the PATROL Agent has already been installed, use PATROL Configuration Manager to set the following 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. Adding Central Monitoring Administration Tags 16 Each policy is assigned a BMC ProactiveNet Central Monitoring Administration tag and each BMC PATROL Agent can have one or more tags assigned to it. When you assign a tag to a BMC PATROL Agent the associated policy is applied to the PATROL Agent. You can assign the tag value of a policy to a PATROL Agent in the following ways:

17 Installing

18 The creation of the Veritas Cluster Server KM installation package is performed directly from BMC ProactiveNet Central Monitoring Administration. An installation package for a component can be downloaded and installed on several servers. The component installation package can be edited and saved under a new name. With Central Monitoring Administration, administrators select monitor installation components, such as the 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 reuse the installation packages, or deploy the packages to multiple computers. Preparing for Installation After creating a component installation package, administrators can save the package to the Monitoring Installation Packages list for future use, or download the package on the current host without saving the package. For saved packages, administrators can download and install the package on any host, or edit a package. For supported 64-bit Linux versions, you must install the Linux runtime package, glibc.i686, version or later. Without the Linux runtime package, BMC ProactiveNet component installations might fail. For further details regarding the BMC ProactiveNet Central Monitoring Administration, please refer to the BMC documentation. 18 The BMC ProactiveNet Central Monitoring Repository is a requirement on the BMC ProactiveNet Central Server where Central Monitoring Administration is enabled. The Central Monitoring Repository includes the current versions of BMC components that you can use with BMC ProactiveNet.

19 Creating a Component Installation Package If you want to import the entire repository, first download Central Monitoring Repository files from the BMC Electronic Product Distribution (EPD) facility, or copy the files from your installation kit, to the BMC ProactiveNet Central Server file system. 1. 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 Central Monitoring 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 Central Monitoring Administration. Custom solution version: The version number for the custom solution. Values in the first two version boxes are required. 6. Click Import. The selected archive file is imported to the repository and extracted. You can close the window during the import process. 19 Creating a Component Installation Package To import a single or custom solution

20 1. 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 on which you want to install the package. The list of components in the repository that are supported on the specified operating system and platform 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 package with the latest versions of the components when new versions of those components are added to the Central Monitoring Repository. By default, the appropriate BMC PATROL Agent for the operating system and platform that you chose 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 on the products or components that you selected to include in the package. Go through the wizards to complete the installation. 7. The Installation Package Details is displayed. Verify that the operating system and platform are correct for the type of package that you want to create. Also verify that the components that you want 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 Monitoring Repository 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 Save Installation 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 Monitoring Installation Packages list for later use or editing. 9. When you are finished, click Close. Creating a Component Installation Package 20 To create a component installation package

21 Editing a Component Installation Package You can edit any part of an existing component installation package except the operating system and platform. If you add a component to the package, you must complete the configuration process. The Finish Update button shows 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 the package 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 Monitoring Repository 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 Save Installation 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 Monitoring Installation Packages list for later use or editing. 8. When you are finished, click Close. 21 Editing a Component Installation Package 1. In the navigation pane of Central Monitoring Administration, click the Repository drawer and select Monitoring Repository. 2. (Optional) To filter the list of packages, select an operating system from the Filter by Operating System 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.

22 Downloading and Installing an Installation Package You can download an installation package and install the components on one or more hosts. The installation runs silently with the information entered during package creation. Recommendation If you defined the BMC ProactiveNet Integration Service variable for PATROL Agents in the installation package, ensure the agents are started in phases. Do not start newly deployed agents all at once. Start and configure monitoring for the agents in planned phases to reduce the performance impact on the Integration Service nodes and on the BMC ProactiveNet Server associated with the automatic workflow process. 1. 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 by Operating 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 extracted to 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 agent sends 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 the agent. 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 configuration information. 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 Central Monitoring Administration documentation. Downloading and Installing an Installation Package 22 To download and install an installation package

23 Configuring After Installation

24 You configure monitoring of Veritas Cluster Server KM when you create a policy. A policy is a template containing the configuration of a PATROL Agent. A policy can be assigned to one or more PATROL Agents using a unique tag (Central Monitoring Administration tag), and a PATROL Agent can be assigned one or more policies with different priorities. If you have not already added the Central Monitoring Administration tag to your PATROL Agents during the solution installation, then you must manually assign the tag after you have configured the policy. For details, see Adding Central Monitoring Administration Tags. Configuring General Settings 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 with tenants) 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 is selected by default. If you clear the option, the policy and its associations remain intact, but the 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 policies configure the same attributes), it is resolved in one of the following ways: 24 Through the General tab of the Add Policy dialog, you can create a new policy. A policy specifies a set of 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 threshold creation and the setting of baselines. A policy can also include intelligent server-side thresholds so that IT administrators can immediately be alerted on potential problems.

25 Policies with the same tag: If conflicting policies have the same tag, the precedence value determines the order the policies are applied. The policy with the lower number value for precedence is the policy from which the final configuration is applied. Policies with different tags: If conflicting policies have different tags, then the policies are applied according to the order they are listed on the BMC PATROL Agent. The policy listed last on the agent is the policy from which the final configuration is applied. Managing Policies This 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 the BMC documentation and more especially to the section Enabling and configuring Central Monitoring Administration for details. To edit a monitoring policy 1. 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. 25 Configuring General Settings Policies with only threshold configuration or server side configuration are applicable only after a policy with monitor configuration is applied.

26 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy 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 and its associations remain intact, but the policy configuration is not applied until the policy is enabled again. 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Select one or more policies and click Enable or Disable. When you create or edit a policy, you can add and configure monitor types. The Add Monitor Types dialog box presents configuration fields for compatible BMC PATROL monitoring solutions that are located in the Central Monitoring Repository. For a list of monitoring solutions that you can configure through Central Monitoring Administration, see the Monitoring solutions conf igurable through Central Monitoring Administration chapter in the BPPM online documentation. For configuration details for a specific monitor type, see the monitor documentation. To configure custom monitoring solutions through Central Monitoring Administration, ensure the solution is structured correctly; for details, see the Building a PATROL Knowledge Module Developers Guide on BMC Support website. To configure the Monitor Type settings using the Add Monitor Types dialog box To add a monitor type: 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Click Add to display the Add Policy dialog box. 3. Configure the policy general settings. 4. Click the Monitor Configuration tab. Configuring General Settings 26 Configuring Monitor Settings

27 Adding Monitor Types 6. From the Solution menu, select Veritas Cluster Server. 7. From the Version menu, select the required version. 8. From the Monitor Type menu, select the required monitor: Monitor Type Description Veritas Cluster Server KM To set the general settings of Veritas Cluster Server KM (credentials, debug mode, instances, multi-node mode, etc.) VCS Agent Enables access to the filtering options to select the VCS Agents elements that will be monitored. VCS Daemon Enables access to the filtering options to select the daemons elements that will be monitored. 27 Configuring Monitor Settings 5. Click Add

28 VCS GAP Port Enables access to the filtering options to select the GAB ports elements that will be monitored. VCS Group System Enables access to the filtering options to select the VCS group systems elements that will be monitored. VCS LLT Interface To set filtering options that indicate the VCS LLT interfaces to monitor. VCS Log To configure the log scan limit read by the monitoring solution during each data collection cycle. VCS Resource To set filtering options that indicate the VCS Resources to monitor. VCS Resource System To set filtering options that indicate the VCS Resource Systems to monitor. VCS System To set filtering options that indicate the VCS Systems to monitor. VCS System Heartbeat To set filtering options that indicate the VCS System Heartbeats to monitor. VCS WAN Heartbeat To set filtering options that indicate the VCS WAB Heartbeats to monitor. Configuring Veritas Cluster Server KM Before using Veritas Cluster Server KM, you'll have to configure its general settings. This section will learn 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 VCS server discovery overrides (Optional). Configuring the User Account A user account with administrative privileges must be configured in BMC ProactiveNet to read and execute Veritas Cluster Server application programs and file systems. Depending on the operating systems used, several options will be available. On Unix platforms, you can use the following user accounts: Configuring Monitor Settings 28 VCS Service Group To set filtering options that indicate the VCS Service Groups to monitor.

29 a root user a non-root user, such as patrol, that has sudo privileges on Veritas Cluster Server to execute application programs and access file systems a non-root account, such as patrol, configured in the Veritas Cluster Server application to administer the Veritas Cluster Server application. On Windows platforms, you can use the following user accounts: an administrator user a non-administrator account, such as patrol, configured in the Veritas Cluster Server application to administer the Veritas Cluster Server application. To configure the user account 1. Add or edit a monitor type 2. From the Monitor Type menu, select Veritas Cluster Server KM 29 Configuring Monitor Settings

30 3. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on the VCS Servers a hostname or IP address to apply these settings to a specific server 3. Set the VCS 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 the sudo 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 VCS Server discovery overrides (Optional). 6. Click Add to List. 7. Click Update. When you encounter an issue and wish to report it to Sentry Software, you will be asked to enable the Debug Mode and provide the debug output to the Sentry Software support team. To enable the debug mode 1. Edit a Veritas Cluster Server KM monitor type: In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view Select a policy and click Edit In the Monitor Configuration tab, select Veritas Cluster Server KM monitor type and click Edit Configuring Monitor Settings 30 Enabling the Debug Mode

31 Editing the VCS Monitoring Settings 31 Configuring Monitor Settings

32 2. From the List - VCS Monitoring Settings, select the host or localhost 3. Click the Advanced button Advanced Settings Configuring Monitor Settings 32

33 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/VCS/debug 7. Click Close on all pop-ups 8. Click Modify Selection in the main window and click Update. When the debug end time is reached, a tar/zip file is automatically created under <PATROL_HOME>/lib/VCS/ and can be sent to the BMC Support for help. It is also recommended to check the VCS.log file, stored in <PATROL_HOME>/log, for any error. 33 Configuring Monitor Settings 4. Click the Debug button

34 Configuring the Maximum Number of Instances By default, the solution discovers and monitors all the instances. Because there may be a very large number of instances to monitor and this may represent a important workload to the agents and the BPPM servers, it is recommended to only monitor the critical ones. This can be done by configuring the instance limits. 1. Edit a Veritas Cluster Server KM KM monitor type: In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view Select a policy and click Edit In the Monitor Configuration tab, select a Veritas Cluster Server monitor type and click Edit Editing the VCS Monitoring Settings Configuring Monitor Settings 34

35 2. From the List - VCS Monitoring Settings, select the host or localhost 3. Click the Advanced button Advanced Settings 35 Configuring Monitor Settings

36 For each monitored element, indicate the maximum number of instances to be displayed Enter 0 in the relevant field to disable the monitoring of a specific element Click Close on all pop-ups Click Modify Selection in the main window and click Update. Configuring Monitor Settings Click the Instance Max button

37 Configuring the Multi-Node Monitoring Mode If the Veritas Cluster Server environment is installed in a cluster using Veritas Cluster Server, Veritas Cluster File System, Oracle Solaris Cluster or Microsoft Cluster, Veritas Cluster Server KM must be installed on all the cluster nodes to enable continuous monitoring and avoid single point of failure. To avoid duplicate alerts from multiple nodes, it is recommended to configure the solution to operate in multi-node monitoring mode. To configure the multi-node monitoring mode 1. Edit a Veritas Cluster Server KM monitor type: In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view Select a policy and click Edit In the Monitor Configuration tab, select Veritas Cluster Server KM monitor type and click Edit 37 Configuring Monitor Settings

38 Configuring Monitor Settings Editing the VCS Monitoring Settings 38

39 2. From the List - VCS Monitoring Settings, select the host or localhost 3. Click the Advanced button Advanced Settings 39 Configuring Monitor Settings

40 4. Select Enable Multi-node Monitoring Mode and click the Multi-node M... button 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 Veritas Cluster File System. Then the Veritas Cluster Server KM will monitor the entire cluster from the active master system, which is identified by vxdctl -c mode command. This method requires vxconfigd in enable mode with its clustered state active. In the Monitoring Node Names field, name all the VCS systems where the monitoring solution is installed. The list must 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 active VCS Server system or on the node where failover group is online and will not check the monitoring status of the other nodes through PATROL Agent: Check the Enable Remote PATROL Agent Checking box. Click the Remote Agent button Configuring Monitor Settings 40 Configuring Multi-node Mode

41 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) In the Number of Attempts field, indicate how many times the solution will try to communicate with 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 7. Click Close on all pop-ups 8. Click Modify Selection in the main window and click Update. Veritas Cluster Server 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 Veritas Cluster Server components will be monitored. If a managed node is unable to determine the system which should be in Active Multi-node Mode, it will change to Temporary Single-node Mode. 41 Configuring Monitor Settings Configuring the Remote Agent

42 Configuring the VCS Server Discovery Overrides (Optional) The solution automatically discovers the Veritas Cluster Server installation and configuration paths, the temporary directory path used by the VCS KM, the node type, and the node status. This information can however be overridden. To configure VCS server discovery overrides 1. Edit a VCS KM monitor type: In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view Select a policy and click Edit In the Monitor Configuration tab, select a Veritas Cluster Server KM monitor type and click Edit Editing the VCS Monitoring Settings Configuring Monitor Settings 42

43 2. From the List - VCS Monitoring Settings, select the host or localhost 3. Click the Advanced button Advanced Settings 4. In the VCS Server Discovery Overrides section, indicate: the VCS installation path the VCS configuration path the temporary directory path the node status. 5. Click Close on all pop-ups 6. Click Modify Selection in the main window and click Update. 43 Configuring Monitor Settings

44 Filtering Elements to Monitor By default, the solution monitors all the elements discovered, which may represent an important workload to the agents and the BPPM servers. Because the monitoring of some elements may be irrelevant for various reasons, you can apply filters to indicate which elements will be monitored or not. Filtering options are available for the following monitor types: VCS Agent, VCS Daemon, VCS GAB Port, VCS Group System, VCS LLT Interface, VCS Resource, VCS Resource System, VCS Service Group, VCS System, VCS System Heartbeat, and VCS WAN Heartbeat. 1. 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 Cluster Servers 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 and click Add to List In the Exclude... section, indicate the regular expression for the element not to be monitored and click 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 Monitor Settings 44 To filter elements to monitor

45 Configuring the Log Scan Limit BMC ProactiveNet Performance Management - Veritas Cluster Server Monitoring scans log files by reading the new log entries since the last data collection cycle. By default, only 500 KBytes of data is scanned for each log file during each data collection cycle. This log scan limit can however be modified to better suit your requirements. Increasing the Log Scan Limit may impact the performance of the data collector (VCSLogCollector), the monitoring solution, and the PATROL Agent. To customize the log scan limit 1. Add or edit a monitor type 2. Select VCS Log from Monitor Type list. 3. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on Veritas Cluster Servers a hostname or IP address to apply these settings to a specific server 4. Indicate the amount of data (in KBytes) that will be read by the monitoring solution during each data collection cycle. 5. Click Add to List. 6. Click Add. 7. Finally, Update the policy. 45 Configuring Monitor Settings

46 Configuring Thresholds When you are creating or editing a policy, you can add and configure monitor thresholds. The Add Thresholds dialog box presents threshold configuration fields for BMC ProactiveNet monitors that are configured through Central Monitoring Administration. For details about baselines and Key Performance Indicators (KPI), see BMC ProactiveNet Central Monitoring Administration or BMC ProactiveNet documentation or refer to the Managing Baselines and Key Perf ormance Indicators section. For details about the monitored attributes, refer to the specific monitor type in the Ref erence Guide section. Before you begin Recommended Thresholds Thresholds define acceptable high and/or low values for the data collected. Thresholds can be created as part of a policy that can be applied to multiple monitor types on multiple BMC PATROL Agents. The Ref erence Guide provides a list of monitor types with their respective attributes and, when meaningful, a recommended threshold. Configuring Monitor Thresholds To configure monitor thresholds: Create a new policy or edit an existing one. Select the Threshold Configuration tab and click Add. In the Add Thresholds dialog box, select the relevant Solution, Version, and Monitor Type. In the Instance Name field, specify the instance to which the threshold configuration will be applied. You can either use a string or the following regular expression patterns:?, +, *, ( ),, [ ], { }, ^, $, 5. Select Match Device Name if you want the entire <devicename>\<instancename> string to be considered. 6. From the Attribute list, select a monitor attribute. 7. In the Threshold section: Select the threshold type. Set the threshold parameters values. Configuring Monitor Settings 46 Ensure that your monitor configuration is complete before thresholds are applied. Thresholds cannot be applied to monitors that are not configured through Central Monitoring Administration. If you have not done so already, please refer to the section Configuring Monitor Settings.

47 Click Add. 8. Resume the procedure to configure all the monitor thresholds required. 9. Click Close. The configuration details are displayed in the table on the Threshold Configuration tab. 10. Click Save at the bottom of the Add Policy dialog box, or Update at the bottom of the Edit Policy dialog box. After you save or update the policy, new threshold configurations are pushed to BMC PATROL Agents with matching Central Monitoring Configuration tags. Editing a Threshold Configuration To edit a threshold configuration: Edit an existing policy On the Threshold Configuration tab, select a threshold definition, and click Edit. Edit the configuration values and click Update. When you finish editing the threshold configuration, click Close. 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 with matching Central Monitoring Configuration tags. Deleting a Threshold Configuration To delete a threshold configuration: Edit an existing policy On the Threshold Configuration tab, select attributes, monitor types, versions, or solutions. Click Delete. After you delete one or more threshold configurations, click Close. 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 Agents with matching Central Monitoring Configuration tags. 47 Configuring Thresholds

48 Using BMC ProactiveNet Performance Management This section provides a brief overview of how to navigate and use the product in the BMC ProactiveNet Operations 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. The BMC ProactiveNet Operations Console is a Web-based application that provides options to navigate through BMC ProactiveNet and view all of the information collected and computed by the BMC ProactiveNet 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 folders are 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 hierarchy All Abnormalities displays all the abnormality events All Services displays all the services All Groups displays all the groups All Devices displays all the devices Based on permissions, users can create event and component folders under this node to organize the event view. My Folder node Based on permissions, users can create event and component folders under this node to organize the event view. To further organize your display, beneath these top-level folders you can add event and component folders, including folders for Component Instances (CIs) associated with a service Using BMC ProactiveNet Performance Management 48 Navigating the BMC ProactiveNet Operations Console

49 model. Your ability to add event and component folders depends on your permissions. The severity icons for a collector dynamically change depending on the severity level of the events for that 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 immediately. For complete details, see the BMC ProactiveNet Getting Started Guide on the BMC Support website. Navigation drawers 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 BMC ProactiveNet. 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 you create in the navigation tree. Find CI Provides a search mechanism so that you can search for Component Instances that meet the specified 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 displays meaningful for operators. For example, you might create an event folder for collectors that gather database warning events and allow only operators who are database administrators access to that event folder. You can drag components from one existing folder to another within 49 Using BMC ProactiveNet Performance Management The navigation pane in the Operations Console contains a series of drawers that enable you to navigate through BMC ProactiveNet functions and views. You can select which drawers to display in the navigation pane.

50 the top-level folders in the navigation tree. You also can drag and drop CIs from the Tile or Graph view to an existing folder in the All Services folder. Event folders An event folder is a grouping of collectors that shows the relationship of events or abnormalities through the hierarchy of the navigation tree. Administrators define event folders and associate them with one or more collectors. Each level of the collector is shown as a node under the event folder. An event list is associated with the lowest level nodes of an event folder. The parent level of an event folder represents all of the events or abnormalities associated with the collectors. Event collectors gather events for display in an event list to provide operators with meaningful groups of events or abnormalities and to show relationship through the hierarchy of the nodes in the navigation tree. 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 the navigation 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 or not. 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 the navigation 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 parent component folder. An event list is associated with the lowest level nodes of a component folder. The parent level of a component folder represents all of the events associated with the groups, services, or devices. Component folders are static or dynamic. You populate static component folders by selecting from a list of objects. You populate dynamic component folders by creating a query. Static folders always contain only the objects that you manually select. Dynamic folders contain the objects that match the 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 in the navigation tree. Each view is accessed by clicking the associated Console view icon. If a view is not available for the object that is selected in the navigation tree, the icon for that view is not displayed in the toolbar. Using BMC ProactiveNet Performance Management 50 Event collectors

51 View Description Event The Event view displays all events in an event list. This is the default view for all objects. Use the Event view to check the details of events and to address events that highlight incorrect state. Probable Cause Analysis can help you to identify the cause of the event. An event could be assigned to other users, who can acknowledge and take ownership of the event, fix the problem, and close the event. You can also address the incorrect condition by invoking remote actions, detailed diagnostics, and local actions. The Graph view helps check the impacting service and you can cross-launch to Impact Model Designer, Service Level 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 Title The Canvas view enables you to create a graphical representation of the components that are being monitored in your environment. The components are represented by objects that you can place on a background image. The objects can be graphics, such as images or connectors, or metrics information represented in a tile. You can create and display a Canvas view for: services Groups Devices Tree/ Graph The Tree/Graph view displays information for a selected object as a tree that represents the hierarchy of the 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 Group hyperbolic tree, the entire group hierarchy and devices are visible on a hyperbolic pane that is mapped to a circular 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 the configuration items in the service model and shows how those configuration items relate to each other. Use the 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 and other details of the selected object through hyperlinks to graphs, views, etc. You can display a Grid view for: Abnormalities Groups Devices For more detailed information, BMC ProactiveNet Getting Started Guide on the BMC Support 51 Using BMC ProactiveNet Performance Management Event collectors

52 website. Adding attributes to the graph Following configuration, only one attribute is enabled for the graph of each monitor. You might want to add additional attributes to the monitor graph. Viewing and manipulating attribute graphs The graph provides a visual display of the attributes of a monitor. Up to 12 attributes of a monitor can be displayed on a single graph In the BMC ProactiveNet Operations console, select the Navigation drawer. Select Global > Devices. Select the Grid view. All the monitored devices are displayed in table format. Select a device from the table. Select a monitor. 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 for this monitor. You can use the options available on this tab to manipulate the graph. For complete details, refer to BMC ProactiveNet User Guide on the BMC Support website. Using BMC ProactiveNet Performance Management 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 of measurement can be used.

53 Viewing monitors for a device This section provides a brief overview of how to view the monitors for a selected device. For complete details, refer to BMC ProactiveNet User Guide on the BMC Support website. To view the Monitor types for a device In the BMC ProactiveNet Operations console, select the Navigation drawer. Select Global > Devices. Select the Grid view. All the monitored devices are displayed in table format. 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. Information Description Monitor Name Device name or process name, a device might appear more than once if it is monitored by several PATROL Agents Monitor Type Name of the monitor type. This will correspond to the element displayed in the Monitor Name column, specifying the type of device or process monitored 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 device instance. In the BMC ProactiveNet Operations console, select the Navigation drawer Select Global > Devices. Select the Grid view. All the monitored devices are displayed in table format. Select a device from the table. Select a monitor. 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 to the selected monitor instance. 6. Edit the Threshold settings 7. Click Apply. 53 Using BMC ProactiveNet Performance Management The following information is displayed:

54 Managing Baselines and Key Performance Indicators In order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNet calculates baselines per attributes based on values collected over a specified period of time to determine a normal operating range. When the collected values for these attributes are out of range, an alert is triggered. Some attributes are identified by default as Key Performance Indicators (identitied with the icon) and therefore automatically included in the base lining calculation. Managing baselines The baseline is calculated by collecting the values for a monitor s attributes and metrics over a specified time period and establishing a low baseline value (consisting of the 10th percentile of all the values for a given time period) and a high baseline value (consisting of the 90th percentile of all the values for a given time period), taking a weighted average of these values over time. A higher weight is given to the latest data being factored into the baseline average. The accuracy of the baseline improves over time. Requirements for baseline generation For baselines to be generated for an attribute, that abnormality threshold means that the threshold exists and is not suppressed. Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes that have an active abnormality threshold and are also KPI attributes will have baselines generated for them. Absolute thresholds (with "outside baseline") or signature thresholds do not satisfy these requirements. Managing Key Performance Indicators The KPI attribute of an attribute can be activated or deactivated manually through the BMC ProactiveNet Administration Console. In this KM, some attributes have been designated as important indicators of performance (KPIs). We do not recommend that these default settings are modified. However, advanced users may activate or deactivate KPIs from the BMC ProactiveNet Using BMC ProactiveNet Performance Management 54 The baseline is the expected normal operating range for a metric or attribute of a monitor.

55 Administration Console. To add or remove Key Performance Indicator (KPI) attributes for a monitor type 1. In the Administration Console, from the menu bar, choose Tools > KPI Administration. The KPI Administration dialog box is displayed. 2. From the Monitor Type list, choose the monitor type for which you want to add or remove KPI attributes. A list of attributes for the selected monitor type is displayed. 3. In the KPI column for the attributes that you want to add or remove as Key Performance Indicators: select the KPI check box to add the corresponding attribute as a KPI deselect the KPI check box to remove the corresponding attribute from the KPIs for that monitor type For complete and detailed information on this procedure, please refer to the BMC ProactiveNet documentation available from BMC Web site. 55 Using BMC ProactiveNet Performance Management

56 Reference Guide

57 Introduction This chapter provides statistical information about resources, operating status, and performances managed by the Veritas Cluster Server 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. Veritas Cluster Server KM VCS Agent VCS Agents VCS Daemon VCS Daemons VCS GAB VCS GAB Port VCS Group System VCS LLT VCS LLT Interface VCS Log VCS Logs VCS Resource VCS Resources VCS Resource System VCS Service Group VCS Service Groups VCS System VCS Systems VCS System Heartbeat VCS WAN Heartbeat VCS WAN Heartbeats Baselines and Key Performance Indicators Some attributes are identified by default as Key Performance Indicators (KPIs) and therefore automatically included in the base lining calculation. To learn more about auto baselining and KPIs, please refer to the Managing Baselines and Key Performance Indicators chapter. In this guide, attributes flagged as KPIs are respectively identified by the following icon:. 57 Monitor Types

58 Veritas Cluster Server KM Attributes Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type Login Status Monitors the status of the VCS KM login details (username/ password) for the operating system. 0 = OK 1 = Suspicious 2 = Failure Warning = 1 Alarm = 2 Collection Status Node Status 0 = Permanent None Single-node Mode 1 = Temporary Single-node Mode 2= Active Multi-node Mode 3 = Passive Multinode Mode -1 = Unknown Monitors error messages for the 0 = OK Veritas Cluster Server application 1 = Suspicious on this managed system. It is set 2 = Failure by VCS_SERVER application class discovery. If any of the Veritas Cluster Server application daemons is not running, this attribute will be set to "Failure" state. The list of critical Veritas Cluster Server daemons can be customized using the KM command Configuration > Node Status from the Veritas Cluster Server icon. If there are any suspicious command exits due to an error, this attribute will be set to "Suspicious" state. If this status attribute changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. 58 Warning = 1 Alarm = 2 Collection Status Availability Monitoring Indicates the VCS monitoring Mode mode.

59 VCS Agent Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type Fault Count Displays the number of the agent faults as reported in the command executed by the data collector. Count n/a Statistics State Displays the state of the agent as reported in the command executed by the data collector. 0 = Running 1 = Not Started 2 = Not Running -1 = Unknown None Availability Status Monitors the status of the agent.the following State to Status mapping rule is used: Not Running > Failure Unknown > Failure All other states > OK 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability For detailed information about KPI, see Managing Baselines and Key Performance Indicators. 59 Veritas Cluster Server KM Attributes

60 VCS Agents Attributes Name Description Units Exec Time Inactive standard attribute seconds monitors the collector execution time. To activate this attribute, use the PSL below, and restart the PATROL Agent: Default Alert Conditions BPPM Type Warning Collection Status > preset value or observed maximum (default) %PSL pconfig("replace", "/ Runtime/VCS/ VCSAgentCollectorExecTime", 1); %PSL pconfig("replace", "/ Runtime/VCS/ VCSAgentCollectorWarn", 3600); VCS Agent 60 When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below:

61 VCS Daemon Name Description CPU Duration Recommend ed Alert Conditions BMC ProactiveNet Attribute Type Indicates the CPU seconds consumed seconds by the daemon. None Statistics CPU Utilization Indicates the CPU seconds consumed Percentage (%) by the daemon. None Statistics Memory Size Indicates the core image size of the daemon in the virtual memory. Kilobytes (KB) None Statistics Processes Count Indicates the number of the processes/threads of the daemon found. processes None Statistics State Indicates the state of the daemon as 0 = Running reported in the command executed by 1 = Sleeping the data collector. 2 = Waiting 3 = Queued 4 = Intermediate 5 = Terminated 6 = Stopped/Disabled 7 = Growing 8 = Nonexistent/Not Responding 9 = Not Running -1 = Unknown None Availability Status Monitors the status of the daemon. The following State to Status mapping rule is used: Not Running > Failure Terminated, Stopped > Suspicious Growing, or Unknown > Suspicious All other states > OK Warning = 1 Availability Alarm = 2 For detailed information about Units 0 = OK 1 = Suspicious 2 = Failure KPI, see Managing Baselines and Key Performance Indicators. 61 VCS Agents Attributes

62 VCS Daemons Attributes Name Description Units Exec Time Inactive standard attribute seconds monitors the collector execution time. To activate this attribute, use the PSL below, and restart the PATROL Agent: Default Alert Conditions BPPM Type Warning Collection Status > preset value or observed maximum (default) When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: %PSL pconfig("replace", "/ Runtime/VCS/ VCSDaemnCollectorWarn", 3600); VCS Daemon 62 %PSL pconfig("replace", "/ Runtime/VCS/ VCSDaemonCollectorExecTime", 1);

63 VCS GAB Attributes Name Description Units Recommende d Alert Conditions BMC ProactiveNet Attribute Type Node Count This attribute displays the number of nodes. Count None Statistics Status This attribute monitors the status of the GAB module. If the GAB module is not configured or in jeopardy, this attribute will be set to "Failure". 0 = OK 1 = Suspicious 2 = Failure Warning = 1 Alarm = 2 n/a Exec Time Inactive standard attribute monitors the collector execution time. To activate this attribute, use the PSL below, and restart the PATROL Agent: Seconds Warning Collection Status %PSL pconfig("replace", "/Runtime/VCS/ VCSGabCollectorExecTime", 1); > preset value or observed maximum (default) When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: %PSL pconfig("replace", "/Runtime/VCS/ VCSGabCollectorWarn", 3600); For detailed information about KPI, see Managing Baselines and Key Performance Indicators. 63 VCS Daemons

64 VCS GAB Port VCS GAB Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type State This attribute displays the state of the GAB as reported in the command executed by the data collector. 0= Membership 1 = Waiting for Seed 2 = Jeopardy -1 = Unknown None Availability Status This attribute monitors 0 = OK the status of the GAB. 1= Suspicious The following State to 2 = Failure Status mapping rule is used: Waiting for Seed > Suspicious Jeopardy > Failure Unknown > Failure All other states > OK Warning = 1 Alarm = 2 Availability 64 Attributes

65 VCS Group System Attributes Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type Auto Disabled This attribute indicates whether the service group has been auto-disabled on the system by Veritas Cluster Server. 0 = No Alarm = 1 1 = Yes -1 = Unknown Availability Enabled 0 = No Warning = 0 1 = Yes -1 = Unknown Availability Pending Probe This attribute displays the number of Count pending probes for this group system. Count Statistics Probed This attribute indicates whether the service group has been successfully probed on the system. 0 = No Warning = 0 1 = Yes -1 = Unknown Collection Status State This attribute displays the state of the group system as reported in the command executed by the data collector. Note: ONLINE* and OFFLINE* states represent all other ONLINE and OFFLINE states with a secondary state respectively. 0 = ONLINE None 1 = ONLINE* 2 = OFFLINE 3 = OFFLINE* 4 = STARTING 5 = STOPPING 6 = PARTIAL 7 = FAULTED -1 = UNKNOWN Availability Status This attribute monitors the status of the group system. The following State to Status mapping rule is used: ONLINE* or OFFLINE > Suspicious STARTING or STOPPING > Suspicious PARTIAL or FAULTED > Failure Unknown > Failure All other states > OK 0 = OK 1= Suspicious 2 = Failure Availability This attribute indicates whether the service group has been enabled on the system. For detailed information about Warning if out of [0-100] range Warning: Warning = 1 Alarm = 2 KPI, see Managing Baselines and Key Performance Indicators. 65 VCS GAB Port Name

66 VCS LLT Name Description Units Recommen ded Alert Conditions BMC ProactiveNet Attribute Type Link Count This attribute displays the number of links active in the LLT communication. Count None Statistics Receive Packet Rate This attribute displays the number of received packets per second in the LLT communication. packets/ second None Statistics Received Not Connected Packets Count This attribute displays the number of nonconnected received packets in the LLT communication. Packets None Statistics Received Packet Count This attribute displays the number of received packets in the LLT communication. Packets None Statistics Send Packet Rate This attribute displays the number of sent packets per second in the LLT communication. packets/ second None Statistics Sent Connected Packet Count This attribute displays the number of sent connected packets in the LLT communication. packets None Statistics Sent Not Connected Packet Count This attribute displays the number of nonconnected received packets in the LLT communication. Count None Statistics Sent Packet Count This attribute displays the number of sent packets in the LLT communication. Packets None Statistics Status This attribute monitors the status of the LLT module. If the LLT module is not running, this attribute will be set to "Failure". 0 = OK 1= Suspicious 2 = Failure Warning = Statistics 1 Alarm = 2 Exec Time Inactive standard attribute monitors the collector execution time. To activate this attribute, use the PSL below, and restart the PATROL Agent: %PSL pconfig("replace", "/Runtime/VCS/ VCSLltCollectorExecTime", 1); Seconds Warning When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: %PSL pconfig("replace", "/Runtime/VCS/ VCSLltCollectorWarn", 3600); For detailed information about VCS Group System KPI, see Managing Baselines and Key Performance Indicators. 66 > preset value or observed maximum (default) Collection Status Attributes

67 VCS LLT Interface Attributes Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type State This attribute displays the state of the LLT as reported in the command executed by the data collector. 0 = Down 1 = Up -1 = Unknown None Availability Status This attribute monitors the status of the LLT.The following State to Status mapping rule is used: Down > Failure Unknown > Failure All other states > OK 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Name 67 VCS LLT

68 VCS Log Name Description Alarm Message Count This attribute Count monitors the number of alarm messages. File Space Growth Rate This attribute displays the growth rate of the amount of space used by the log file. Kilobytes per None second (KB/ s) Statistics File Space Used This attribute displays the amount of space used by the log file. Kilobytes (KB) None Statistics Filesystem Space Used Percent This attribute monitors the percentage of capacity used by the log file. Percent (%) Alarm if out of [0100] range Warning: Alarm: Statistics Space Available This attribute monitors the available space for the log file to use (this is also the available space on the file system). Megabytes (MB) Warning = 2-5 Alarm = -1 to 2 Availability Space Used Percent This attribute monitors Percent (%) the percentage of space used by the file system (where the log file resides). Alarm if out of [0100] range Warning: Alarm: Statistics Warning Message Count This attribute monitors the number warning messages. Alarm if out of [0100] range Warning: Statistics For detailed information about VCS LLT Interface Units Count Recommended Alert Conditions BMC ProactiveNet Attribute Type Alarm if out of [0100] range Alarm: Statistics KPI, see Managing Baselines and Key Performance Indicators. 68 Attributes

69 VCS Logs Attributes Name Description Units Exec Time Inactive standard attribute seconds monitors the collector execution time. To activate this attribute, use the PSL below, and restart the PATROL Agent: Default Alert Conditions BPPM Type Warning Collection Status > preset value or observed maximum (default) %PSL pconfig("replace", "/ Runtime/VCS/ VCSLogCollectorExecTime", 1); When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: %PSL pconfig("replace", "/ Runtime/VCS/ VCSLogCollectorWarn", 3600); 69 VCS Log

70 VCS Resource Attributes Description Units Failover Status This attribute monitors the failover status of the resource. If the VCS system(s) where this resource is ONLINE differs between the current and previous collection cycles, this attribute will be set to "Suspicious". If there is no ONLINE system found for this resource, it will be set to "Failure". 0 = OK Warning = 1 1= Alarm = 2 Suspicious 2 = Failure Availability Fault SystemCount This attribute displays the number of systems where this resource is in FAULTED state. Count Warning if out of [0-100] range Warning: 1100 Statistics Offline System Count This attribute displays the number of systems where this resource is in OFFLINE state. Count None Statistics Online System Count This attribute displays the number of systems where this resource is in ONLINE state. Count None Statistics Partial System Count This attribute, set by VCSResourceCollector, displays the number of systems where this resource is in PARTIAL state. Count None Statistics State This attribute displays the state of the 0= resource as reported in the command executed Enabled by the data collector. 1= Disabled 2= Disabled / Critical -1 = Unknwon None Availability Status This attribute monitors the status of the resource. For detailed information about VCS Logs 0 = OK Warning = 1 1= Alarm = 2 Suspicious 2 = Failure KPI, see Managing Baselines and Key Performance Indicators. 70 Recommended Alert Conditions BMC ProactiveNet Attribute Type Availability Name

71 VCS Resources Attributes Name Description Units Exec Time Inactive standard attribute seconds monitors the collector execution time. To activate this attribute, use the PSL below, and restart the PATROL Agent: Default Alert Conditions BPPM Type Warning Collection Status > preset value or observed maximum (default) %PSL pconfig("replace", "/ Runtime/VCS/ VCSResourceCollectorExecTime", 1); When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: %PSL pconfig("replace", "/ Runtime/VCS/ VCSResourceCollectorWarn", 3600); 71 VCS Resource

72 VCS Resource System Attributes Description Units Probed This attribute indicates whether the resource has been successfully probed on the system. 0 = No Warning = 0 1 = Yes -1 = Unknown Availability State This attribute displays the state of the resource system as reported in the command executed by the data collector. 0 = ONLINE None 1 = ONLINE* 2 = OFFLINE 3 = OFFLINE* 4 = STARTING 5 = STOPPING 6 = PARTIAL 7 = FAULTED -1 = UNKNOWN Availability Status This attribute monitors the status of the resource system. The following State to Status mapping rule is used: ONLINE* or OFFLINE* > Suspicious STARTING or STOPPING > Suspicious PARTIAL or FAULTED > Failure Unknown > Failure All other states > OK 0 = OK 1= Suspicious 2 = Failure Availability VCS Resources Recommended Alert Conditions 72 Warning = 1 Alarm = 2 BMC ProactiveNet Attribute Type Name

73 VCS Service Group Attributes Description Units Failover Status This attribute monitors the failover status of the group. If the VCS system(s) where this service group is ONLINE differs between the current and previous collection cycles, this attribute will be set to "Suspicious" state. If there is no ONLINE system found for this service group, it will be set to "Failure". 0 = OK Warning = 1 1= Alarm = 2 Suspicio us 2= Failure Availability Fault System Count This attribute displays the number of systems where this service group is in FAULTED state. Count Warning if out of [0100] range Warning: Statistics Frozen State This attribute displays the frozen state of the group as reported in the command executed by the data collector. 0 = Not Frozen 1= TFrozen 2= Frozen -1 = Unknow n None Availability Frozen Status This attribute monitors the frozen status of the group. TFrozen > Suspicious Frozen > Failure Unknown > Failure All other states > OK 0 = OK Warning = 1 1= Alarm = 2 Suspicio us 2= Failure Availability Offline System Count This attribute displays the number of systems where this service group is in OFFLINE state. Count None Statistics Online System Count This attribute displays the number of systems where this service group is in ONLINE state. Count Alarm 0 Statistics Partial System Count This attribute displays the number of systems where this service group is in PARTIAL state. Count None Statistics For detailed information about Recommended Alert Conditions BMC ProactiveNet Attribute Type KPI, see Managing Baselines and Key Performance Indicators. 73 VCS Resource System Name

74 VCS Service Groups Attributes Name Description Units Exec Time Inactive standard attribute seconds monitors the collector execution time. To activate this attribute, use the PSL below, and restart the PATROL Agent: Default Alert Conditions BPPM Type Warning Collection Status > preset value or observed maximum (default) %PSL pconfig("replace", "/ Runtime/VCS/ VCSGroupCollectorExecTime", 1); %PSL pconfig("replace", "/ Runtime/VCS/ VCSGroupCollectorWarn", 3600); VCS Service Group 74 When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below:

75 VCS System Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type CPU Available Percent This attribute monitors the percentage of available CPU on the system. Percent (%) Warning = 5-10 Alarm: 0-5 Statistics CPU Used Percent This attribute displays the percentage of CPU used by the system. Percent (%) None Statistics Load Warning Duration This attribute indicates Seconds how long the system load has been over the warning threshold set in Veritas Cluster Server with the LoadTimeCounter system attribute. None Statistics System Frozen State This attribute displays the frozen state of the system as reported in the command executed by the data collector. 0 = Not Frozen 1 = TFrozen 2 = Frozen -1 = Unknown None Availability System Frozen Status This attribute monitors the frozen status of the system. The following State to Status mapping rule is used: TFrozen > Suspicious Frozen > Failure Unknown > Failure All other states > OK 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Online Group Count This attribute displays the number of groups that are online or about to go online on a system, as reported in the command executed by the data collector. Count None Statistics 75 VCS Service Groups Attributes

76 This attribute displays the state of the resource system as reported in the command executed by the data collector. 0 = INITING None 1= CURRENT_DI SCOVER_WAI T 2= CURRENT_PE ER_WAIT 3= STALE_DISCO VER_WAIT 4= STALE_PEER_ WAIT 5= LOCAL_BUILD 6= REMOTE_BUI LD 7 = RUNNING 8= ADMIN_WAI T 9= STALE_ADMI N_WAIT 10 = LEAVING 11 = EXITING 12 = EXITING_FOR CIBLY 13 = EXITED 14 = FAULTED -1 = UNKNOWN Availability System Status This attribute monitors the status of the system. The following State to Status mapping rule is used: CURRENT_DISCOVER_ WAIT, CURRENT_PEER_WAIT, STALE_DISCOVER_WA IT, STALE_PEER_WAIT, LOCAL_BUILD, or REMOTE_BUILD for more than 10 minutes > Suspicious 0 = OK 1= Suspicious 2 = Failure Availability VCS System 76 Warning = 1 Alarm = 2 System State

77 Stopped Agent Count This attribute displays the number of stopped agents on the system. Count None Statistics System Up Down State This attribute displays the up/down state of the system as reported in the command executed by the data collector. 0 = Down 1 = Up -1 = Unknown None Availability System Up Down Status This attribute monitors the up/down status of the system. The following State to Status mapping rule is used: Down > Failure Unknown > Failure All other states > OK 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability For detailed information about ADMIN_WAIT, STALE_ADMIN_WAIT, LEAVING, EXITING, EXITING_FORCIBLY, or EXITED > Suspicious FAULTED, or UNKNOWN > Failure All other states > OK KPI, see Managing Baselines and Key Performance Indicators. 77 VCS System

78 VCS Systems Attributes Name Description Units Exec Time Inactive standard attribute seconds monitors the collector execution time. To activate this attribute, use the PSL below, and restart the PATROL Agent: Default Alert Conditions BPPM Type Warning Collection Status > preset value or observed maximum (default) %PSL pconfig("replace", "/ Runtime/VCS/ VCSGroupCollectorExecTime", 1); %PSL pconfig("replace", "/ Runtime/VCS/ VCSGroupCollectorWarn", 3600); VCS System 78 When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below:

79 VCS System Heartbeat Attributes Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type State This attribute displays the state of the heartbeat as reported in the command executed by the data collector. 0 = Down 1 = Up -1 = Unknown None Availability Status This attribute monitors the status of the heartbeat. 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Name 79 VCS Systems

80 VCS WAN Heartbeat Attributes Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type State This attribute displays the state of the WAN heartbeat as reported in the command executed by the data collector. 0 = Dead 1 = Alive -1 = Unknown None Availability Status This attribute monitors the status of the WAN heartbeat. 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Name VCS System Heartbeat 80

81 VCS WAN Heartbeats Attributes Name Description Units Exec Time Inactive standard attribute seconds monitors the collector execution time. To activate this attribute, use the PSL below, and restart the PATROL Agent: Default Alert Conditions BPPM Type Warning Collection Status > preset value or observed maximum (default) %PSL pconfig("replace", "/ Runtime/VCS/ VCSWHeartbeatCollectorExecTime", 1); When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: %PSL pconfig("replace", "/ Runtime/VCS/ VCSWHeartbeatCollectorWarn", 3600); 81 VCS WAN Heartbeat

82 Sent Not Connected Packet Count 66 Sent Packet Count 66 Space Available 68 Space Used Percent 68 State 59, 61, 64, 67, 70, 72, 79, 80 Status 59, 61, 63, 64, 66, 67, 70, 72, 79, 80 Stopped Agent Count 75 System Frozen State 75 System Frozen Status 75 System State 75 System Status 75 System Up Down State 75 System Up Down Status 75 Warning Message Count 68 Index -A 54 Permissions 11 User 11 Add Monitor Types 26 Agents Debug 30 Attribute 52 Attributes 60 Alarm Message Count 68 CPU Available Percent 75 CPU Duration 61 CPU Used Percent 75 CPU Utilization 61 Exec Time 62, 63, 66, 69, 71, 74, 78, 81 Failover Status 70, 73 Fault Count 59 Fault System Count 73 Fault SystemCount 70 File Space Growth Rate 68 File Space Used 68 Filesystem Space Used Percent 68 Frozen State 73 Frozen Status 73 Link Count 66 Load Warning Duration 75 Login Status 58 Memory Size 61 Monitoring Mode 58 Node Count 63 Node Status 58 Offline System Count 70, 73 Online Group Count 75 Online System Count 70, 73 Partial System Count 70, 73 Probed 72 Processes Count 61 Receive Packet Rate 66 Received Not Connected Packets Count 66 Send Packet Rate 66 Sent Connected Packet Count 66 -BBaseline Baselines 57 BMC ProactiveNet Performance Management 54 Generation 54 Manage 54 Requirements 54 BMC PATROL Changes 10 BMC ProactiveNet Performance Management Abnormalities 54 Baselines 54 Key Performance Indicators KPI 54 Business Value 9 -CClient Maximum Instances Cluster Application 37 Component 34 folders 48 Component Installation package creating 19 downloading 22 editing 21 Configure Log Scan Limit 45 Maximum Instances Abnormalities Access

83 Multi-node monitoring mode Overrides 42 Configuring monitor settings 26 Configuring Monitor Thresholds Configuring thresholds 46 Features 9 Filtering Options DDaemon Maximum Instances Daemons Debug Database Maximum Instances Debug VCS VCS VCS VCS VCS VCS VCS VCS VCS VCS VCS Filters Agent 44 Daemon 44 GAB Port 44 Group System 44 LLT Interface 44 Resource 44 Resource System 44 Service Group 44 System 44 System Heartbeat 44 WAN Heartbeat 44 VCS VCS VCS VCS VCS VCS VCS VCS VCS VCS VCS Agent 44 Daemon 44 GAB Port 44 Group System 44 LLT Interface 44 Resource 44 Resource System 44 Service Group 44 System 44 System Heartbeat 44 WAN Heartbeat Agents 30 Daemons 30 GABs 30 Heartbeats 30 LLTs 30 Logs 30 Resources 30 Server 30 Service Groups 30 Systems 30 Deleting a Threshold Configuration Disk Pool 47 -GGABs Maximum Instances Disk Storage 34 Debug Generate Maximum Instances Disk Volume 34 Maximum Instances Downloading Baselines Goals 9 Graphs H- -E- Heartbeats Editing a Threshold Configuration Event 47 Debug 30 -I- collectors 48 folders 48 Exec Time 60 Information Closed 53 Enabled 53 Open 53 Source Agent -FFailover Group Name Configure

84 18 Logs configuring Installing 24 Preparation Instances 18 Debug -M- Client 34 Configure 34 Daemon 34 Database 34 Disk Pool 34 Disk Storage 34 Disk Volume 34 Job 34 Log 34 Maximum 34 Mount Request 34 Policy 34 Policy Client 34 Robotic Drive 34 Robotic Library 34 Standalone Drive 34 Volume Pool 34 Manage Baselines 54 Key Performance Indicators KPI 54 Monitor configuring 26 Monitor thresholds 46 Monitor Type Job 34 -KKey Concepts 9 Key Performance Indicators 57 BMC ProactiveNet Performance Management 54 Manage 54 KPI 57 BMC ProactiveNet Performance Management 54 Manage 54 VCS Agent 59 VCS Agents 60 VCS Daemon 61 VCS Daemons 62 VCS GAB 63 VCS GAB Port 64 VCS LLT 66 VCS LLT Interface 67 VCS Log 68 VCS Logs 69 VCS RESOURCE 70 VCS Resource System 72 VCS Resources 71 VCS Service Group 73 VCS Service Groups 74 VCS System 75 VCS System Heartbeat 79 VCS Systems 78 VCS WAN Heartbeat 80 VCS WAN Heartbeats 81 Veritas Cluster Server KM 58 Monitor Types VCS VCS VCS VCS VCS VCS VCS VCS VCS VCS -LLLTs Debug 30 Log Maximum Instances Log Scan Limit Configure 54 name 53 type 53 Monitor Settings -J Maximum Instances Agent 57 Agents 57 Daemon 57 Daemons 57 GAB 57 GAB Port 57 Group System 57 LLT 57 LLT Interface 57 Log 57 Installation

85 Monitor Types VCS Logs 57 VCS Resource 57 VCS Resource System 57 VCS Resources 57 VCS Service Group 57 VCS System 57 VCS System Heartbeat 57 VCS Systems 57 VCS WAN Heartbeat 57 VCS WAN Heartbeats 57 Veritas Cluster Server KM 57 Monitoring Node Names 37 Mount Request -RReference Guide 57 Remote PATROL Agent Checking Requirements Security 11 Software 10 System 10 Resources Debug 30 Robotic Drive Maximum Instances Robotic Library 34 Maximum Instances 34 Maximum Instances 34 Multi-node monitoring mode 37 -S- -N- Security Navigation Requirements Server drawers 48 tree 48 Debug 30 Service Groups Debug Software -O- 10 Maximum Instances Sudo 11, 28 System 48 Configure 42 TSM Server Discovery Requirements Systems Debug T - -PPackage 19, 21, 22 PATROL Configuration Manager Policies Manage Policy 30 Requirements Standalone Drive Operations Console views Event 48 Grid 48 Title 48 Tree/Graph Overrides Tags 16 Thresholds modifications 53 Tivoli Storage Manager Changes 10 TSM Server Discovery Maximum Instances Policy Client 34 Maximum Instances 34 Overrides -UUNIX Configure 37

86 User Account Configure 28 patrol 28 Privileges 28 Sudo 28 -V Volume Pool Maximum Instances 34 -W 28 Windows 86

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