BMC ProactiveNet Performance Management - Veritas File System Monitoring

Transcription

1 BMC ProactiveNet Performance Management - Veritas File System Monitoring User Documentation January 2013

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 Outside United States and Canada Address BMC Software, Inc CityWest Blvd. Houston TX Telephone (01) Telephone or Fax (01) Fax Copyright 2006 BMC Software, Inc. or licensors, as an unpublished work. All rights reserved. BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. IBM is a registered trademark of International Business Machines Corporation. DB2 is a registered trademark of International Business Machines Corporation. Oracle is a registered trademark, and the Oracle product names are registered trademarks or trademarks of Oracle Corporation. All other trademarks belong to their respective companies. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User 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

3 You can obtain technical support by using the Support page on the BMC Software Web site or by contacting Customer Support by telephone or . To expedite your inquiry, please see "Before Contacting BMC Software." Support Web Site You can obtain technical support from BMC Software 24 hours a day, 7 days a week at From this Web site, you can Read overviews about support services and programs that BMC Software offers: Find the most current information about BMC Software products Search a database for problems similar to yours and possible solutions Order or download product documentation Report a problem or ask a question Subscribe to receive notices when new product versions are released Find worldwide BMC Software support center locations and contact information, including addresses, fax numbers, and telephone numbers 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 Before Contacting BMC Software Before you contact BMC Software, have the following information available so that Customer Support can begin working on your problem immediately: Product information product name product version (release number) license number and password (trial or permanent) Operating system and environment information machine type operating system type, version, and service pack or other maintenance level such as: PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level Sequence of events leading to the problem Commands and options that you used Messages received (and the time and date that you received them) product error messages messages from the operating system, such as "file system full" 3

4 Table of Contents...11 User Goals and Features Business Value...11 Requirements System Requirements...12 Software Requirements...13 Security Requirements...18 Adding Central Monitoring Administration Tags...20 Preparing for Installation...21 Creating a Component Installation Package...23 Editing a Component Installation Package Downloading and...24 Installing an Installation Package...26 Configuring General Settings...27 Managing Policies...28 Configuring Monitor Settings...30 Configuring Veritas File System KM...30 Configuring the User Account...32 Enabling the Debug Mode...36 Configuring the Maximum Number of Instances...39 Configuring the Multi-Node Monitoring Mode...42 Configuring the TSM Server Discovery Overrides (Optional)...45 Filtering Elements to Monitor...45 Configuring Thresholds...47 Using BMC ProactiveNet Performance Management...48 Navigating the BMC ProactiveNet Operations Console Adding attributes...51 to the graph...51 Viewing and manipulating attribute graphs Viewing monitors...52 for a device...52 Changing thresholds...53 Managing Baselines and Key Performance Indicators VxFS Server...57 VxFS File System VxFS Fragmentation Table of Contents 4

5 ...61 VxFS Quick I/O File VxFS Quota...62 VxFS Log...63 Table of Contents 5

6 Support Information

7 This section contains information about how to contact Customer Support and the levels of support offered for this and other releases. If you have problems with or questions about a BMC product, or for the latest support policies, see the Customer Support website at You can also access product documents and search the Knowledge Base for help with an issue at If you do not have access to the web and you are in the United States or Canada, contact Customer Support at Outside the United States or Canada, contact your local BMC office or agent. 7

8 Legal Notices

9 Copyright 2011 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. Linux is the registered trademark of Linus Torvalds. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. UNIX is the registered trademark of The Open Group in the US and other countries. The information included in this documentation is the proprietary and confidential information of BMC Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and restricted rights notices included in the product documentation. BMC Softwa re Inc City W e st Blv d, Houston T X , USA Custom e r Support: (Unite d Sta te s a nd Ca na da ) or conta ct y our loca l support ce nte r 9

10 Key Concepts

11 The pages in this section provide a high-level overview of the product. User Goals and Features Business Value Requirements Note that for conv enience and brev ity, reference to BMC Proactiv enet Performance Management - Veritas File Sy stem Monitoring, may also be made as Veritas File Sy stem KM. User Goals and Features Veritas File System KM enables you to monitor the following in your environment: Server: monitors overall health of the Veritas File System node and the monitoring solution. File Systems: automatically discovers and monitors all VxFS file systems, snapshots and checkpoint. Quick I/O Files: reports on monitored, detected and enabled quick I/O files Performance: reports on data transfer rates, read/write operations, failed operations, response times, hit ration, growth rates, etc. Fragmentations: file system fragmentation is checked regularly for optimum performance number of free blocks, percentage of allocated blocks, total number of files, directories, blocks, etc. Quotas: reports on quota limits and usage for users, groups and checkpoints and their status are monitored. Logs: checks for any errors in system logs and monitors space used by the log file, percentage of capacity used by the log file, etc. Business Value provides current and historical information through a centralized console so you can easily view and manage your entire Veritas File System environment. The product collects and brings critical performance data and useful metrics into the BMC ProactiveNet Performance Management environment and enables SAN Administrators to be warned whenever a problem occurs in their Veritas File System environment. : Helps anticipate disruptions Enhances productivity Ensures Veritas File Systems are mounted Reports on Veritas File Systems servers performance are online Maintains integrity at all times 11

12 Requirements Before installing the Veritas File System KM, verify the: system requirements software requirements security requirements. System Requirements Operating System Operating System Version Linux All distributions supported by BMC PATROL Agent 3.4 and above Sun microsystems SolarisTM 8, 9, 10, supported by BMC PATROL Agent 3.7 and above HP-UX 11x, supported by BMC PATROL Agent 3.7 and above IBM AIXTM 5.x, 6.x, supported by BMC PATROL Agent 3.7 and above Red Hat Linux 7.2 If the operating sy stem is upgraded (or downgraded) at a later date, y ou will need to reload commands for the Veritas File Sy stem KM. Software Requirements supports: Software Version Veritas File System 4.5, 5.0, 5.1 BMC Software PATROL Agent 3.7+ BMC Software PATROL Console 3.4.x, 3.5.x, 7.x BMC Portal 2.3.x, 2.4.x, 2.5.x, 2.6.x, 2.7.x, 2.8.x BMC ProactiveNet Performance Manager 8.x, 8.5.x, 8.6.x, 9.x Version 2.0 of BMC Proactiv enet Performance Management - Veritas File Sy stem Monitoring does not support Veritas File Sy stem v ersions before 4.0 and PA TROL A gent v ersions before 3.4. If the operating system is upgraded (or downgraded) at a later date, you will need to reload commands for the Veritas File System KM. Requirements 12

13 Additional Software Requirements The following table contains a list of additional software requirements for BMC ProactiveNet Performance Management - Veritas File System Monitoring: Purpose Software Version When running Veritas File System KM with sudo user account on Solaris, HP-UX, AIX or Linux managed nodes Sudo (superuser do) or later When running Veritas File System KM on Linux managed nodes Korn shell binary (/bin/ksh) Any Security Requirements By default, Veritas File System is installed and run as the root user. needs to be run as a user account with administrative privileges to read and execute Veritas File System application programs and file systems. Login details of this user are configured in the KM during the configuration. The password is stored in the PATROL Agent in a DES encrypted format. The encrypted password can be viewed by any user who has access to the PATROL Agent configuration variables (pconfig). This user could then execute PSL statements using the encrypted password through the PATROL Console. This can be prevented by setting up an appropriate Access Control List (ACL) for users. Please refer to the PATROL Agent Reference Manual for details on how to set up an ACL. One of the following user accounts can be used for configuring the login details of the KM: 1. root user 2. a non-root user, such as patrol, with sudo privileges on Veritas File System to execute application programs and access the file systems 3. a non-root account, such as patrol, configured in Veritas File System to administer the Veritas File System application Refer to the Veritas File Sy stem A dministrator s Guide for details on how to set up this ty pe of account. Access Permissions The Veritas File System KM user needs read & execute permission to executable and library files under the paths listed below. The Veritas File System installation path INSTALL_PATH, referenced in the tables below is normally /opt/vrtsvxfs. Requirements 13

14 Executable and Library Files accessed by Veritas File System KM User Unix INSTALL_PATH/bin INSTALL_PATH/lib /usr/sbin/* If the KM is enabled to failover in a clustered environment, the login user needs execute permissions to the following cluster commands: /opt/vrtsvfs/bin/hagrp (in Veritas Cluster Server) vxdctl (in Veritas Cluster File System) /usr/cluster/bin/clrg (in Oracle Solaris Cluster) The Veritas File System KM includes some scripts which should be executable by the PATROL Agent user and the Veritas File System KM user. These scripts are stored under KM_HOME path, normally PATROL_HOME/lib/VFS. In addition to these Veritas File Sy stem commands, Veritas File Sy stem KM ex ecutes other operating sy stem commands, such as ps, which may not require special priv ileges. To list all OS commands used by the Veritas File System KM, execute the following PSL code from the PATROL Console, using PSL Task menu, after installing and loading the KM. i=0; sudoers=""; i=0; sudoers=""; foreach var (grep("^/runtime/vfs/commandcontrols/",pconfig("list"))) { ctl=get(var); opt=ntharg(grep("option",ctl),"2-"," ="); nsa=ntharg(grep("nosudoattempt",ctl),"2-"," ="); sua=ntharg(grep("singleuserattempt",ctl),"2-"," ="); typ=ntharg(grep("commandtype",ctl),"2-"," ="); cmd=nthargf(grep("commandtext",ctl),"2-","=","="); if((typ == "") (typ == "OS")) { met=""; if(opt == "NoLogin") { met = "(run as patrol user)"; } elsif(nsa == "YES") { met = "(run as configured user without sudo)"; } elsif(sua == "YES") { met = "(run as supplied user - used in menu)"; } else { scmd=cmd; s=index(scmd,"%sudo"); if(s) { scmd=replace(substr(scmd,s,length(scmd)),"%sudo",""); } sudoers=union(sudoers,ntharg(ntharg(scmd,1," "),"1-"," "," ")); } printf("(%2d) %-30s %-40s: %s\n",i++,ntharg(var,"5","/"),met,cmd); } } printf("\n\ncommands used with sudo:\n%s",sort(sudoers)); Requirements 14

15 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. Sudo User for Operating System Access If a non-root user with sudo privileges is preferred as the Veritas File System 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 VxFS commands and OS commands. The code below also applies to all non-root users who may execute Veritas File System KM administration and report menu commands using their sudo privileges. The KM accepts any non-root user with the following sudo configuration in the sudoers file. Please replace user1, user2, user3 with appropriate KM user name. The Veritas File System installation path INSTALL_PATH, referenced below is normally /opt/vrts and PATROL_HOME is the path where the PATROL Agent is installed (including the target, like /opt/bmc/patrol3/solaris29-sun4/). This non-root sudo user configured in the KM will be able to execute Veritas File System 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 VFSKMUSERS = user1, user2, user3 Defaults:VFSKMUSERS!lecture,!authenticate,\ env_keep+="ld_library_path INSTALL_PATH KM_HOME \ KM_TEMP",env_reset VFSKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\ INSTALL_PATH/bin/*,\ PATROL_HOME/lib/VFS/*,PATROL_HOME/bin/* user1, user2, user3 must be replaced with username(s) used by the KM; INSTA LL_PA TH and PA TROL_HOME with the relev ant paths. On HP-UX User_Alias VFSKMUSERS = user1, user2, user3 Defaults:VFSKMUSERS!lecture,!authenticate,\ env_keep+="shlib_path INSTALL_PATH KM_HOME \ KM_TEMP",env_reset VFSKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\ INSTALL_PATH/bin/*,\ PATROL_HOME/lib/VFS/*,PATROL_HOME/bin/* Requirements 15

16 user1, user2, user3 must be replaced with username(s) used by the KM; INSTA LL_PA TH and PA TROL_HOME with the relev ant paths. On AIX & Linux User_Alias VFSKMUSERS = user1, user2, user3 Defaults:VFSKMUSERS!lecture,!authenticate,\ env_keep+="libpath INSTALL_PATH KM_HOME \ KM_TEMP",env_reset VFSKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\ INSTALL_PATH/bin/*,\ PATROL_HOME/lib/VFS/*,PATROL_HOME/bin/* user1, user2, user3 must be replaced with username(s) used by the KM; INSTA LL_PA TH and PA TROL_HOME with the relev ant paths. Requirements 16

17 Planning

18 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 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: 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 Proactiv enet v ersion 9.0, the tag description is ignored, and only the tag name is used to ev aluate the policy. Adding Central Monitoring Administration Tags 18

19 Installing

20 The creation of the Veritas File System 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 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. 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 v ersions, y ou must install the Linux runtime package, glibc.i686, v ersion or later. W ithout the Linux runtime package, BMC Proactiv enet component installations might fail. For further details regarding the BMC Proactiv enet Central Monitoring A dministration, please refer to the BMC documentation. 20

21 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. To import a single or custom solution 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. Creating a Component Installation Package 21

22 To create a component installation package 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 y ou click Download and do not click Sav e Installation Package, the package is not sav ed in the Monitoring Installation Packages list for later use or editing. 9. When you are finished, click Close. Creating a Component Installation Package 22

23 Editing a Component Installation Package You can edit any part of an existing component installation package except the operating system and platform. 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. If y ou add a component to the package, y ou must complete the configuration process. The Finish Update button shows an ex planatory 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 y ou click Download and do not click Sav e Installation Package, the changes are not sav ed in the Monitoring Installation Packages list for later use or editing. 8. When you are finished, click Close. Editing a Component Installation Package 23

24 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. To download and install an installation package 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 Proactiv enet Central Monitoring A dministration documentation. Downloading and Installing an Installation Package 24

25 Configuring After Installation

26 You configure monitoring of Veritas File System 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 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. 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. 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: /, \, {, }, <, >,,, &. Provider indicates a policy applicable to the cloud service provider 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: 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. 26

27 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. Policies with only threshold configuration or serv er side configuration are applicable only after a policy with monitor configuration is applied. 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. 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. Configuring General Settings 27

28 Configuring Monitor Settings 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 configurable through Central Monitoring A dministration 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 PA T ROL Know ledge 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 Monitor Settings 28

29 5. Click Add A dding Monitor T y pe s 6. From the Solution menu, select Veritas File System. 7. From the Version menu, select the required version. 8. From the Monitor Type menu, select the required monitor: Monitor Type Description Veritas File System KM Required for all managed systems, where the KM credentials are provided and any configuration overrides are entered. VxFS File System Optional monitor type to customize the monitored file systems. VxFS Fragmentation Optional monitor type to customize the fragmentation monitoring. VxFS Quick I/O File Optional monitor type to customize the Quick I/O file monitoring. VxFS Quota Optional monitor type to customize the monitored quotas. Default Monitoring Not used. Configuring Monitor Settings 29

30 Configuring Veritas File System KM Before using Veritas File System 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 VFS server discovery overrides (Optional). Configuring the User Account A user account with administrative privileges must be configured in BMC ProactiveNet to read and execute the Veritas File System application programs and file systems. Depending on the operating systems used, several options will be available. On Unix platforms, you can use the following user accounts: a root user a non-root user, such as patrol, that has sudo privileges on Veritas File System to execute application programs and access file systems a non-root account, such as patrol, configured in the Veritas File System application to administer the Veritas File System application. On Windows platforms, you can use the following user accounts: Configuring Monitor Settings 30

31 an administrator user a non-administrator account, such as patrol, configured in the Veritas File System application to administer the Veritas File System application. To configure the user account 1. Add or edit a monitor type 2. From the Monitor Type menu, select Veritas File System KM Configuring Monitor Settings 31

32 3. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on the Veritas File System servers a hostname or IP address to apply these settings to a specific server 3. Set the VxFS 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 VFS Server discovery overrides (Optional). 6. Click Add to List. 7. Click Update. Enabling the Debug Mode When you encounter an issue and wish to report it to Sentry Software, you will be asked to enable the Debug Mode and provide the debug output to the Sentry Software support team. To enable the debug mode 1. Edit a Veritas File System 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 File System KM monitor type and click Edit Configuring Monitor Settings 32

33 Editing the Ve rita s File Sy ste m Monitoring Se ttings Configuring Monitor Settings 33

34 2. From the List - VxFS Monitoring Settings, select the host or localhost 3. Click the Advanced button Editing the Ve rita s File Sy ste m A dv a nce d Se ttings Configuring Monitor Settings 34

35 4. Click the Debug button Configuring the De bug 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/VFS/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/ VFS/ and can be sent to the BMC Support for help. It is also recommended to check the VFS.log file, stored in <PATROL_HOME>/log, for any error. Configuring Monitor Settings 35

36 Configuring the Maximum Number of Instances 1. Edit a Veritas File System 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 File System monitor type and click Edit Editing the Ve rita s File Sy ste m Monitoring Se ttings Configuring Monitor Settings 36

37 2. From the List - VxFS Monitoring Settings, select the host or localhost 3. Click the Advanced button A dv a nce d Se ttings 4. Click the Instance Max button Configuring Monitor Settings 37

38 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. No max imum number of instance monitored by the KM is set by default. Configuring Monitor Settings 38

39 Configuring the Multi-Node Monitoring Mode If the Veritas File System environment is installed in a cluster using Veritas Cluster Server, Veritas Cluster File System, Oracle Solaris Cluster or Microsoft Cluster, Veritas File System 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 File System 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 File System KM monitor type and click Edit Configuring Monitor Settings 39

40 Editing the Ve rita s File Sy ste m KM Monitor T y pe 2. From the List - VxFS Monitoring Settings, select the host or localhost 3. Click the Advanced button A dv a nce d Se ttings 4. Select Enable Multi-node Monitoring Mode and click the Multi-node M... button Configuring Multi-node Mode 5. Configure the Multi-node Mode: Select the appropriate Cluster Application. Configuring Monitor Settings 40

41 Indicate the Failover Group Name. Leave this field blank if you have previously selected Veritas Cluster File System. Then the Veritas File System 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 nodes where the 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 VFS 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 the Re m ote A ge nt 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 Configuring Monitor Settings 41

42 7. Click Close on all pop-ups 8. Click Modify Selection in the main window and click Update. Veritas File System 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 File System KM components will be monitored. If a managed node is unable to determine the sy stem which should be in A ctiv e Multi-node Mode, it will change to Temporary Single-node Mode. Configuring the VFS Server Discovery Overrides (Optional) The solution automatically discovers the Veritas File System installation path, the DSM_DIR and DSM_LOG directory paths, the DSM_CONFIG file path, the temporary directory path used by the Veritas File System KM, the node type, and the node status. This information can however be overridden. To configure VFS server discovery overrides 1. Edit a Veritas File System 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 File System monitor type and click Edit Configuring Monitor Settings 42

43 Editing the Ve rita s File Sy ste m KM Monitor T y pe Configuring Monitor Settings 43

44 2. From the List - VxFS Monitoring Settings, select the host or localhost 3. Click the Advanced button A dv a nce d Se ttings 4. In the VFS Server Discovery Overrides section, indicate: the VxFS installation path the temporary directory path 5. Click Close on all pop-ups 6. Click Modify Selection in the main window and click Update. Configuring Monitor Settings 44

45 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: VxFS File System, VxFS Fragmentation, VxFS Quick I/O File, VxFS Quota. To filter elements to monitor 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 File System 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 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 Performance Indicators section. For details about the monitored attributes, refer to the specific monitor type in the Reference Guide section. Configuring Monitor Settings 45

46 Before you begin Ensure that 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, define general policy details. To add and configure monitor thresholds 1. Open the Add Policy dialog box. Click for steps: In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. Click Add, or select an existing policy and click Edit. 2. Select the Threshold Configuration tab and click Add. 3. In the Add Thresholds dialog box, select an item from each of the following lists: Solution, Version, and Monitor Type. Configuration fields are displayed. 4. In the Scope list, the Instance option is automatically selected. Type an Instance Name string or regular expression to apply threshold configuration to instances with matching patterns. Select Match Device Name to include the associated device and use the entire <devicename>\<instancename> string for pattern matching. Instance thresholds are applied to the matched monitor instance names or instance names patterns. You can use the following regular expression patterns for the instance name:?, +, *, ( ),, [ ], { }, ^, $,. If the instance name contains one of the pattern characters (except for *), use a backslash ( \ ) before the pattern character. For example, to enter the instance name Storage1 (1), enter Storage1 \(1\). 5. From the Attribute list, select a monitor attribute. In the A ttribute list, some attributes are designated as key performance indicators (KPIs). Depending on the monitored env ironment and v ersion, the list of KPIs might appear differently in the BMC Proactiv enet Operations Console. 6. From the Type of Threshold list, select the threshold type. 7. Select and enter values for the threshold parameters. 8. To continue configuration, perform one or more of the following actions in the Add Thresholds dialog box, and then select a different monitor type, version, or solution: To add the configuration details for the threshold to the Threshold Configuration tab, click the Add button at the bottom of the window. To return the settings in the current window to default values, click the Reset button at the bottom of the window. The values on the current window are reset. Be sure to click the Add button to save the configuration on the Threshold Configuration tab. 9. When you finish configuration, click Close. The configuration details are displayed in the table on the Threshold Configuration tab. 10. When you finish configuring thresholds, 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. Configuring Thresholds 46

47 To edit a threshold configuration 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. To delete a threshold configuration 1. On the Threshold Configuration tab, select attributes, monitor types, versions, or solutions. 2. Click Delete. 3. After you delete one or more threshold configurations, click Close. 4. To save changes to the policy, click Update at the bottom of the Edit Policy dialog box. After you update the policy, deleted threshold configurations are removed from BMC PATROL Agents with matching Central Monitoring Configuration tags. 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 monitors types on multiple BMC PATROL Agents. The Reference Guide provides a list of monitor types with their respective attributes and, when meaningful, a recommended threshold. Using BMC 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. Configuring Thresholds 47

48 Navigating the BMC ProactiveNet Operations Console 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 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 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. The following table describes the available drawers in the navigation pane and describes their functions. Using BMC ProactiveNet Performance Management 48

49 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 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 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 Using BMC ProactiveNet Performance Management 49

50 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. 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: Event collectors 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 Using BMC ProactiveNet Performance Management 50

51 View Description 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 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. 1. In the BMC ProactiveNet Operations console, select the Navigation drawer. 2. Select Global > Devices. 3. Select the Grid view. All the monitored devices are displayed in table format. 4. Select a device from the displayed table. 5. Select a monitor. 6. Click Tools >Show Graph 7. Select the Attributes & Indicators tab. 8. Select one or more attributes. Up to 12 attributes of a monitor can be displayed on a single graph. Though only two units of measurement can be used. 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 av ailable. 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 51

52 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. The following information is displayed: Information Description Monitor Name Device name or process name, a device might appear more than once if it is monitored 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 ty pe. Instance thresholds are applied to the selected monitor instance. 6. Edit the Threshold settings 7. Click Apply. Using BMC ProactiveNet Performance Management 52

53 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 and therefore automatically included in the base lining calculation. Managing baselines The baseline is the expected normal operating range for a metric or attribute of a monitor. 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. A bsolute 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 Administration Console. Using BMC ProactiveNet Performance Management 53

54 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 Proactiv enet documentation av ailable from BMC W eb site. Attributes considered as KPIs are respectively identified by the following icon:. Using BMC ProactiveNet Performance Management 54

55 Reference Guide

56 Introduction This chapter provides statistical information about resources, operating status, and performances managed by the Veritas File System KM. It contains tables describing the attributes used in the KM, grouped by Monitor Types, and provides a brief description of each attribute and its default settings. Monitor Types VxFS VxFS VxFS VxFS VxFS VxFS Server File System Fragmentation Quick I/O File Quota Log 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: 56.

57 VxFS Server Attributes Name Description Units Recommen ded Alert Conditions BPPM Attribute Type Login Status Monitors the status of the VFS KM login details (username/password) for the operating system. It is set by VxFS Server monitoring type discovery. 0 = OK 1= Suspicious 2 = Failure Collection Status If no valid username/password is detected for the operating system, this parameter will be set to "Failure" state. If there are any suspicious command exits, this parameter will be set to "Suspicious" state. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. Monitoring Mode Indicates the VFS KM monitoring mode. 0= Permanent Single-node Mode 1= Temporary Single-node Mode 2 = Active Multi-node Mode 3 = Passive Multi-node Mode -1 = Unknown Warning = 1 Alarm = 2 Collection Status Node Status Monitors error messages for the Veritas File System application on this managed system. It is set by VxFS Server monitoring type discovery. 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. 57

58 VxFS File System Attributes Name Description Units Recommen ded Alert Conditions BPPM Attribute Type Inodes Available Indicates the number of inodes available on the File System. inodes Availability Inodes Growth Rate Indicates the growth rate of the file system inode system. inodes/s Inodes Used Percent Indicates the number of inodes used on the file system as a percentage. % Warning: 9598 Alarm: Alarm if out of [-1 to 100] range. Inodes Used Indicates the number of inodes in inodes use on the File System. If this parameter is displayed, the inodes for the file system have been manually limited, otherwise this parameter is disabled and the VFSInodeText is enabled showing the text of the inode setting. IO KBytes Rate Indicates the total transfer rate for both Read and Write operations in the last interval. KB/s IO KBytes Indicates the number of data blocks transferred in the last interval. KB IO Operations Failed Indicates the total number of IO operations that failed in the last interval. operations IO Operations Rate Indicates the total number of Read and Write IO operations per second in the last poll interval. operations/s IO Operations Indicates the total number of Read and Write IO operations in the last interval. operations Mount State Indicates the mount state of the File System. 0 = Mounted ; 1 = Mounted/ Different Mount Point 2 = Not Mounted/Auto Disabled 3 = Not Mounted/Auto Enabled 4 = Mounted/ Error -1 = Unknown Availability VxFS Server 58

59 Mount Status Indicates the mount status of the File 0 = OK System. 1 = Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Read KBytes Rate Indicates the amount of kilobytes read per second in the last interval. KB/s Read KBytes Indicates the number of kilobytes read in the last interval. KB Read Operations Failed Indicates the number read operations that failed. operations Warning: Alarm if out of [0 to 100] range. Read Operations Indicates the number of Read operations in the last interval. operations Read Time Indicates the number of Read operations failed in the last interval. milliseconds Warning: Alarm if out of [0 to 100] range. Response Time Read Time Average Indicates the time spent on Read operations in the last interval. milliseconds Space Available Indicates the amount of free space on the file system. MB Availability Space Growth Rate Indicates the growth rate of the file system space usage. MB/s Space Used Percent Indicates the percentage of space used on the file system. % Warning: 9598 Alarm: Alarm if out of [-1 to 100] range. Space Used Indicates the amount of space used on the file system. MB Summary Summarizes the file system information as reported by commands executed by the data collector. n/a n/a Write KBytes Rate Indicates the amount of data written per second in the last interval. KB/s Write KBytes Indicates the amount of kilobytes written in the last interval. KB Write Operations Failed Indicates the number of Write operations failed in the last interval. operations Warning: Alarm if out of [0- to 100] range. Write Operations Indicates the number of Write operations in the last interval. operations Write Time Indicates the current write time. milliseconds Warning: Alarm if out of [0- to 100] range. Response Time VxFS File System 59

60 Write Time Average Indicates the amount of time spent on write operations in the last interval. For detailed information about milliseconds K P I, see Managing Baselines and Key Performance Indicators. VxFS Fragmentation Attributes Name Description Units Recommen ded Alert Conditions BPPM Attribute Type Average File Blocks Indicates the number of average file blocks. blocks Blocks Free* Indicates the number of total free blocks. blocks Blocks Greater Than 64 Allocated Percent Indicates the percentage of allocated blocks in extents larger than 64 blocks. % Warning: 0-5 Alarm if out of [0 to 100] range. Blocks Less Than 64 Free Percent Indicates the percentage of free blocks in extents smaller than 64 blocks. % Warning: Alarm if out of [0 to 100] range. Blocks Less Than 8 Free Percent Indicates the percentage of free blocks in extents smaller than 8 blocks. % Warning: 5100 Alarm if out of [0 to 100] range. Blocks To Reduce Indicates the number of blocks to reduce. blocks Warning:10100 Alarm if out of [0 to 100] range. Blocks Total Indicates the total number of blocks. blocks Blocks Used for Indirects Indicates the number of blocks used for indirects. blocks Directories To Reduce Indicates the number of directories to reduce. directories Warning: Alarm if out of [0 to 100] range. Directories Total Indicates the total number of directories. directories File Average Extents Indicates the number of average file extents. extents Files Total Indicates the total number of files. files Immediate Directories To Add Indicates the number of immediate directories to add. directories VxFS File System 60

61 Immediate Directories Indicates the number of immediate directories. directories Summary Summarizes the file system fragmentation information as reported by commands executed by the data collector. n/a n/a For detailed information about K P I, see Managing Baselines and Key Performance Indicators. VxFS Quick I/O File Attributes Name Description Units Recommen ded Alert Conditions BPPM Attribute Type Disk I/O Operations Indicates the total number of Read and Write IO operations performed on a disk in the last interval. operations Hit Ratio Indicates the percentage of hit performed in the last interval. % I/O KBytes Rate Indicates the total transfer rate for both Read and Write operations in the last interval. KB/s I/O Operations Indicates the total number of Read and Write IO operations in the last interval. operations IO KBytes Indicates the number of data blocks transferred in the last interval. KB IO Operations Rate Indicates the total number of Read and Write IO operations per second in the last poll interval. operations/s Read KBytes Rate Indicates the amount of kilobytes read per second in the last interval. KB/s Read KBytes Indicates the number of kilobytes read in the last interval. KB Read Operations Indicates the number of Read operations operations in the last interval. Read Time Indicates the number of Read operations milliseconds failed in the last interval. Warning: Alarm if out of [0 to 100] range. Read Time Average Indicates the time spent on Read operations in the last interval. milliseconds Space Used Indicates the amount of space used on the file system. MB Summary Summarizes the file system information as reported by commands executed by the data collector. n/a n/a n/a VxFS Fragmentation 61

62 Write KBytes Rate Indicates the amount of kilobytes written KB/s per second in the last interval. Write KBytes Indicates the number of kilobytes written KB in the last interval. Write Operations Indicates the number of Write operations in the last interval. operations Write Time Indicates the current write time. milliseconds Warning: Alarm if out of [0 to 100] range. Write Time Average Indicates the amount of time spent on write operations in the last interval. milliseconds For detailed information about K P I, see Managing Baselines and Key Performance Indicators. VxFS Quota Attributes Name Description Units Recommen ded Alert Conditions BPPM Attribute Type Files Time Left Indicates the time left for the quota files. hours Warning: 2-5 Alarm: 1-2 Files Used Indicates the files used by the quota entity (user, group or checkpoint). files Quota Files Used Percent Indicates the used percent of the quota files. % Warning: 9598 Alarm: Alarm if out of [0 to 100] range. Space Time Left Indicates the time left for the quota space (not available for checkpoints). hours Warning: 2-5 Alarm: -1-2 Space Used Percent Indicates the quota space used percent (not available for checkpoints). % Warning: 9598 Alarm: Alarm if out of [0 to 100] range. Space Used Indicates the space utilized by the quota entity (user & group; not applicable for checkpoint). MB VxFS Quick I/O File 62

63 State Indicates the state of the quota (not available for checkpoints). 0 = Soft Limits Not Exceeded 1 = Blocks Soft Limit Exceeded 2 = Files Soft Limit Exceeded 3 = Blocks & Files Soft Limits Exceeded -1 = Unknown Availability Status Indicates the status of the quota (not available for checkpoints). 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Summary Summarizes the file system quota information as reported by commands executed by the data collector. n/a n/a n/a For detailed information about K P I, see Managing Baselines and Key Performance Indicators. VxFS Log Attributes Name Description Units Recomme BPPM nded Alert Attribute Conditions Type Alarm Message Count* Monitors the number of alarm messages set in the parameter VFSLogAlarmText. If this parameter changes to alarm state, the recovery action will trigger an event. count Alarm: Alarm if out of [0 to 100] range. File Space Growth Rate Displays the growth rate of the amount of space used by the log file. KB/s File Space Used Displays the amount of space used by the log file. KB Filesystem Space Used Percent Monitors the percentage of space used by the file system (where the log file resides). If this parameter changes to warning or alarm state, the recovery action will trigger an event. % Warning: 9598 Alarm: Alarm if out of [0 to 100] range. Space Available Monitors the available space for the log file to use (this is also the available space on the file system). If this parameter changes to warning or alarm state, the recovery action will trigger an event. MB Warning: 2-5 Alarm: -1-2 Availability Space Used Percent Monitors the percentage of capacity used by the log file. % Warning: 9598 VxFS Quota 63

64 If this parameter changes to warning or alarm state, the recovery action will trigger an event. Note that the total capacity is the used space (VFSLogSpaceUsed) plus available space (VFSLogSpaceAvailable). Warning Message Count Monitors the number warning messages set in the parameter VFSLogWarningText. If this parameter changes to a warning state, the recovery action will trigger an event. For detailed information about VxFS Log Alarm: Alarm if out of [0 to 100] range. count Warning: 1100 Alarm if out of [0 to 100] range. K P I, see Managing Baselines and Key Performance Indicators. 64

65 About BMC Software BMC Software, Inc. NYSE:BMC, is a leading provider of enterprise management solutions that empower companies to manage their IT infrastructure from a business perspective. Delivering Business Service Management, BMC Software solutions span enterprise systems, applications, databases, and service management. Founded in 1980, BMC Software has offices worldwide and fiscal 2004 revenues of more than $1.4 billion. For more information about BMC Software, visit About Sentry Software Sentry Software, a strategic Technology Alliance Partner of BMC Software, provides key monitoring solutions specifically designed to expand the capabilities of BMC Performance Manager, thus enabling up to 100% coverage of any infrastructure. Sentry Software specializes in single solutions for multiplatform monitoring of hardware, custom applications or any IT component, and blackout windows. Sentry Software products are deployed in 45 countries across the globe and lead the list of BMC Software s third-party product sales. For more information about Sentry Software, please visit