BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring

USER DOCUMENTATION STORAGE MONITORING BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring Version 1.2.00 February 2015

Contacting BMC Software You can access the BMC Software Web site at http://www.bmc.com. 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. 2101 CityWest Blvd. Houston TX 77042-2827 Telephone 1 (713) 918 8800 or 1 (800) 841 2031 (Toll Free) Copyright 2006 BMC Software, Inc. or licensors, as an unpublished work. All rights reserved. BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. All other trademarks belong to their respective companies. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation. 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 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this address. 2

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 e-mail. 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 http:// www.bmc.com/support_home. From this Web site, you can Read overviews about support services and programs that BMC Software offers: Find the most current information about BMC Software products Search a database for problems similar to yours and possible solutions Order or download product documentation Report a problem or ask a question Subscribe to receive e-mail notices when new product versions are released Find worldwide BMC Software support center locations and contact information, including e- mail addresses, fax numbers, and telephone numbers You can also access product documents and search the Knowledge Base for help with an issue at http://www.sentrysoftware.com Support by Telephone or E-mail In the United States and Canada, if you need technical support and do not have access to the Web, call 800 537 1813. Outside the United States and Canada, please contact your local support center for assistance. To find telephone and email 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 http://www.bmc.com/support_home. 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: 3

Table of Contents User Goals...12 and Features Product...13 at a Glance Supported...14 Platforms Importing...16 the Monitoring Solution into Central Administration Creating...17 the Installation Package Downloading...18 the Installation Package Installing...18 the Package Adding...22 Tags to PATROL Agents Configuring...24 Monitor Settings...28 Enabling the Debug Mode...30 Configuring the Discovery Interval...32 Setting Advanced Configuration Variables...33 Disabling Volumes Monitoring...35 Filtering Volumes to Monitor...37 Scheduling Automatic Reports...38 Configuring Thresholds...38 Configuring Monitor Thresholds...39 Editing a Threshold Configuration...40 Deleting a Threshold Configuration...40 Managing Monitoring Policies...40 Editing an existing monitoring policy...41 Deleting a monitoring policy...41 Enabling/disabling a monitoring policy Identifying...44 a Node Overload Diagnosing...47 Slow Volumes Identifying...50 Busiest Volumes Reporting...53 Disk Space Consumption Viewing...56 the Overall Activity of a Storage System Monitor...60 Types and Attributes...61 IBM SVC FC Port...63 IBM SVC iscsi Port...65 IBM SVC MDisk 4

...66 IBM SVC Node...68 IBM SVC Pool...69 IBM SVC SAN Volume Controller...70 IBM SVC Volume...72 IBM SVC Volume Mirror...73 IBM SVC Storage System...74 Configuration Variables...77 Managing Baselines and Key Performance Indicators 5

Release Notes for v1.2.00

What's New The monitoring solution now supports: 4-node cluster monitoring. Unlimited debug file size. In previous versions, the debug file size was limited to 500 MB. The Port Count attribute has been added to the IBM SVC SAN Volume Controller monitor type to report on the number of FC and Ethernet ports on the storage system. The Available Path Count attribute of the IBM SVC MDisk monitor type now also considers the nodes that have access to the internal managed disks of IBM Storwize V7000 systems. Fixed Issues The username used to connect to the IBM SVC system was always reset to "superuser". The modifications made to the polling interval were not taken into account. When the polling interval was changed to less than 15 minutes, the server could get saturated which prevented the monitoring solution from collecting the statistics parameters as frequently as excepted. Now in such a case, the monitoring solution will follow the IBM's recommendations by collecting the statistics parameters every 15 minutes to avoid server saturation. 7

Support Information

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 http://www.bmc.com/support. You can also access product documents and search the Knowledge Base for help with an issue at http:// www.sentrysoftware.com. If you do not have access to the web and you are in the United States or Canada, contact Customer Support at 800 537 1813. Outside the United States or Canada, contact your local BMC office or agent. 9

Overview

The pages in this section provide a high-level overview of the product. User Goals and Features Product at a Glance Supported Platforms Note that for convenience and brevity, reference to BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring, may also be made as BPPM IBM SVC Storage Monitoring. 11

User Goals and Features BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring product allows you to view, monitor, and manage your entire IBM SVC environment by viewing the current and historical information through a centralized console. You can view detailed system metrics on all parts of your environment. BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring enables you to manage the following in your environment: Nodes: availability, processor utilization, response time and traffic (read and write, in operations/s and MB/s) FC ports: Link status, speed and errors; Traffic (read and write, in MB/s ; from hosts, storage systems, same or other clusters) isci ports: Link status and speed; Traffic (read and write, in MB/s; from hosts, storage systems, same or other clusters) Pools: Consumed and subscribed capacity (in GB and percentage of total capacity) MDisks: Availability, Available Paths, Traffic (read and write, in operations/s and MB/s) Storage Systems: MDisks originating from the storage system; availability and traffic (read and write, in operations/s and MB/s) Volumes: Consumed and subscribed capacity (in GB and percentage of total capacity); Traffic (read and write in operations/s and MB/s) Volume Mirroring: availability and status (synchronized or not). 12

Product at a Glance BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring provides current and historical information through a centralized console so you can easily view and manage your entire IBM SVC 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 IBM SVC environment. BPPM IBM SVC Storage Monitoring - Architecture Diagram BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring: collects storage performance and metrics to keep total control of your SAN environment identifies performance bottlenecks (nodes, ports, storage systems, and MDisks) analyzes overall traffic for nodes, ports, storage systems, MDisks, and Volumes identifies mapped, unmapped and preferred LUNs Detects oversubscription situations Ensures data integrity and recoverability. 13 User Goals and Features

Supported Platforms BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring supports the following versions of the IBM SVC operating system (EOS): v4.3.x v5.1.x v6.1.x as well as IBM Storwize V7000 systems. Product at a Glance 14

Installing the Monitoring Solution

The installation can be handled from A to Z from BMC ProactiveNet Central Monitoring Administration. Once the latest version of the solution has been loaded into BMC ProactiveNet Central Monitoring Administration, administrators can create all the installation packages required for their different operating systems and platforms and save them for later use in the Monitoring Installation Packages list. These packages can then be deployed to multiple computers. Administrators just have to connect to BMC ProactiveNet Central Monitoring Administration from the server where they want to install the package, download it and launch the installation. This section describes the different steps to follow to install BPPM IBM SVC Storage Monitoring: Importing BPPM IBM SVC Storage Monitoring into Central Administration Creating the Installation Package Downloading the Installation Package Installing the Package Importing the Monitoring Solution into Central Administration The BMC ProactiveNet Central Monitoring Repository includes the current versions of the BMC PATROL Agent and BMC PATROL Monitoring Solutions that you can use with BMC ProactiveNet. If the version available in the Repository does not correspond to the latest one, you will have to manually import it: 1. Log on to BMC ProactiveNet Central Monitoring Administration. 2. Click the Repository drawer and select Manage Repository. 3. Check that the version of the BMC component available is actually the latest one. If not, download the latest version corresponding to your operating system (Windows or UNIX/ Linux) available on the Sentry Software Website and save it on the local computer from which you are running the Central Monitoring Administration web-based console. 4. From the BMC ProactiveNet Central Monitoring Administration, click Import. 5. Select Single solution. 6. Browse to the.zip source file. 7. Click Import. The selected archive file is imported to the repository. 16

Creating the Installation Package The installation package to deploy to managed systems can be created directly from BMC ProactiveNet Central Monitoring Administration: 1. Log on to BMC ProactiveNet Central Monitoring Administration 2. Click the Repository drawer and select Deployable Package Repository. 3. Click Add. 4. Select the operating system and platform for which you want to create a package. The components available in the repository for the selected operating system and platform are displayed. 5. Select the Installation Package Component: From the Available components list, select the relevant component. From the Version list, select the latest version. Click the right arrow button to move the component into the Selected Components list By default, the appropriate BMC PATROL Agent for the operating system and platform that you chose is included in the Selected components list. Click Next. The Add Component Installation Package wizard is displayed. 6. Go through the wizard and specify the required PATROL information. The Installation Package Details is displayed. 7. Verify that: the operating system and platform are correct the components that you want to include are listed in the Included Components list. 8. 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. 9. Click Save Installation Package. 10. Click Close. The package is now available in the Monitoring Installation Packages list. 17 Importing the Monitoring Solution into Central Administration

Downloading the 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. Log on to BMC ProactiveNet Central Monitoring Administration from the computer on which the PATROL Agent is installed. 2. Click the Repository drawer and select Deployable Package Repository. 3. (Optional) To filter the list of installation packages, select an operating system from the Filter by Operating System list. 4. Click the link for the installation package that you want to download. 5. Through the browser's download dialog box, save the installation package. Installing the Package 1. Copy the installation package to the host where BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring needs to be installed 2. Extract the installation package as appropriate for your operating system. The package is extracted to the bmc_products directory on the current host. 3. From the bmc_products directory, run the installation utility for your operating system: (UNIX or Linux) RunSilentInstall.sh (Microsoft Windows) RunSilentInstall.exe The package is installed on the current host. 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. Creating the Installation Package 18

Integrating the Monitoring Solution

Depending on the version of BMC ProactiveNet Performance Management used, integration steps may need to be performed. BMC ProactiveNet Performance Management 8.5, 8.6 or 9.0 To integrate BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring into BMC ProactiveNet Performance Management 8.5, 8.6 or 9.0, you need to create a specific adapter. For more information, please refer to Integrating the Sentry Software's KMs into BMC ProactiveNet Performance Management (BPPM). BMC ProactiveNet Performance Management 9.5 No specific integration steps need to be performed. 20

Configuring After Installation

To configure BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring, you need to: Add a tag to your PATROL Agents. Create a policy, i.e. a template containing the PATROL Agent configuration. Assign your policy to one or more PATROL Agents by using the tag that you would have previously added. Adding Tags to PATROL Agents Tags must be set for all your PATROL Agents when creating a policy. If you have not already assigned tags in the deployable install packages you created, you can still manually add them to your policy. 1. In the Navigation pane of Central Monitoring Administration, click Policies and expand the Monitoring policy type. 2. Select a policy view (e.g. All). 3. Click Add to create a new policy or select an existing policy and click Edit to display the Monitoring Policy Configuration dialog box. 4. Check the Agent Configuration box. 5. Click the Agent Configuration link to go straight to the Agent Configuration page. 22

Agent Configuration - Adding Tags 6. Under Agent Properties, enter the tags that you want to assign to the BMC PATROL Agent. The format of each tag is tagname:tagdescription where tagname must be replaced by the name of the tag (e.g. sentrytag). You can also provide multiple tags, separated by commas. If the tag description contains spaces, enclose the description within double quotes. For example, tag1:"brief Description",tag2:"Description" 7. Click Finish to validate your changes. In the Agent Selection page, you will then be able to configure conditions to select BMC PATROL Agents based on the Agent Tag property that you have previously added. 23 Adding Tags to PATROL Agents

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 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. Adding Tags to PATROL Agents 24

To configure the Monitor Type settings using the Add Monitor Types dialog box 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. Click the Monitor Configuration tab. 4. Click Add. 5. From the Solution menu, select IBM SVC Storage. 6. From the Version menu, select the required version. 7. From the Monitor Type menu, select the Monitor Type for which you want to add a policy, that is IBM SVC KM. 8. Enter the Connection Settings to the IBM SVC Cluster: 25 Configuring Monitor Settings

IBM SVC Storage Configuration - Global Settings Cluster Name: Hostname of the IBM SVC cluster System Type: Select the type of system you wish to establish a connection with. Depending on the selected system, you will need to provide a username and an OpenSSH Private Key File or, a username and a password. Username: The admin username is required to connect to the SAN Volume Controller Cluster Password:A password may be required to connect to a Storwize v7000 system type OpenSSH Private Key File: Indicate the path to the OpenSSH Private Key File. An Open SSH Private Key File might be required to connect to a Storwize v7000 system type. Open SSH Private Key File is mandatory to connect to a SAN Volume Controller.The SSH Key file must Configuring Monitor Settings 26

be in OpenSSH format and be stored on the system where the PATROL Agent is running. Passphrase: Enter the Key Passphrase if your SSH key was generated with a passphrase, if any. 9. Click Add to List to save the new connection to the IBM SVC Cluster. 27 Configuring Monitor Settings

Enabling the Debug Mode When you encounter an issue and wish to report it to Sentry Software, you will be asked to enable the Debug Mode and provide the debug output to the Sentry Software support team. To enable the debug mode 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Click Edit to display the Add/Edit Policy dialog box. 3. Select the policy that applies to the PATROL Agent for which you need to enable the debug mode, and click Edit. 4. Click the Monitor Configuration tab. 5. Click the Advanced button. Enabling the Debug Mode Configuring Monitor Settings 28

6. Check the Enable Debug Mode option. The solution will store debug information in a log file. By default debug files are stored in the %PATROL_HOME%\log folder 7. In the Debug End Time field, enter the date and time at which the system must stop logging debug information. Required format: yyyy/mm/dd hh:mm:ss. 8. Click Close to save your settings. For the debug mode to be enabled, the Enable Debug Mode must be checked and the Debug End Time must be properly set to a date and time in the future. 29 Configuring Monitor Settings

Configuring the Discovery Interval BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring periodically performs discoveries to detect new components in your monitored environment. By default, the solution runs a discovery every hour, but you can customize this interval to match your specific needs. Configuring Monitor Settings 30

To configure the discovery interval 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Click Edit to display the Add/Edit Policy dialog box. 3. Select the policy that applies to the PATROL Agent for which you need to configure the discovery interval, and click Edit. 4. Click the Monitor Configuration tab. 5. Click the Advanced button. Configuring the Discovery Interval 6. Enter the frequency of the discovery process. Use the spin button to enter the appropriate number of minutes. 7. Click Close to save your settings. 31 Configuring Monitor Settings

Setting Advanced Configuration Variables Advanced configuration variables are used to manually set variables that are normally not available through the standard interface. These variables should only be set when instructed so by Sentry Software Support. To configure a variable 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Click Edit to display the Add/Edit Policy dialog box. 3. Select the policy that applies to the PATROL Agent for which you need to configure variables, and click Edit. 4. Click the Monitor Configuration tab. 5. Click the Advanced button. Configuring variables 6. In the Configuration Variables section, enter the configuration variables you need to configure and enter the value to be set. Configuring Monitor Settings 32

7. Click Add to List. 8. Click Close to save your settings. You can easily modify or remove a variable by selecting it in the list and clicking either the Modify Selection or the Remove from List buttons. Disabling Volumes Monitoring Discovering and collecting volumes metrics are resource-intensive actions that can create extra workload on the PATROL Agent and the targeted system. To limit the number of instances created and therefore reduce the system resource consumption, administrators can disable the monitoring of all the volumes of a system. 33 Configuring Monitor Settings

To filter volumes to monitor 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Click Edit to display the Add/Edit Policy dialog box. 3. Select the policy that applies to the PATROL Agent monitoring the volumes you need to exclude or keep in the monitoring process, and click Edit. 4. Click the Monitor Configuration tab. 5. Click the Advanced button. Disabling Volumes Monitoring 6. By default the monitoring of volumes is enabled. Check the Disable Volumes Monitoring option if you do not wish discovery/collect requests and operations to be performed on volumes. To resume the monitoring of all volumes, simply un-check the Disable Volumes Monitoring option. Configuring Monitor Settings 34

Filtering Volumes to Monitor By default, the solution discovers and monitors all volumes in the storage systems. There may be a very large number of volumes to monitor and this may represent an important workload to the agents and the BPPM servers. Also, the monitoring of some of these volumes may be irrelevant for various reasons. You can filter the volumes that will be monitored by the solution. You can either exclude volumes from the monitoring or keep only certain volumes. 35 Configuring Monitor Settings

To filter volumes to monitor 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Click Edit to display the Add/Edit Policy dialog box. 3. Select the policy that applies to the PATROL Agent monitoring the volumes you need to exclude or keep in the monitoring process, and click Edit. 4. Click the Monitor Configuration tab. 5. Click the Advanced button. Selecting Volumes to monitor 6. If you specify a regular expression based on the volume PATROL ID in the Exclude Volumes field, all volumes that match with the specified regular expression will be excluded. If you specify a regular expression based on the volume PATROL ID in the Keep Only Volumes field, only the volumes that match with the specified regular expression will be monitored 7. Click Close to save your settings. Configuring Monitor Settings 36

Scheduling Automatic Reports BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring can automatically produce text reports about the monitored storage systems. To schedule automatic reports 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Click Edit to display the Add/Edit Policy dialog box. 3. Select the policy that applies to the PATROL Agent for which you need to configure the scheduling of automatic reports, and click Edit. 4. Click the Monitor Configuration tab. 5. Click the Schedule button. Scheduling automatic reports 6. In the field Generate a text report every day at, indicate the time at which the report(s) must be generated. 7. Check the Activity report type to automatically generate the following reports: Nodes Array Activity: Reports on Sent and Received Bytes for all monitored nodes Ports Activity: Reports on Sent and Received Bytes for all monitored ports Storage Systems Activity: Reports on Read and Write Bytes for all monitored storage systems MDisks Activity: Reports on Read and Write Bytes for all monitored MDisks Volume Activity: Reports on Read and Write Bytes for all monitored volumes 8. Check LUNs Mapping Table to automatically generate a text report of the LUNs-to-hosts mapping table. 9. Click Close to save your settings. The history retention period can be set from the PATROL Console or from the PATROL Agent using a configuration variable. The default collection (retention) period is one day. Whenever a stored parameter value exceeds its retention period, it is automatically deleted from the parameter history file. Refer to BMC documentation for details. 37 Configuring Monitor Settings

Configuring Thresholds When you are creating or editing a policy, you can add and configure monitor thresholds. The Add Instance 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 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. 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. Do not set server thresholds for availability or Boolean oriented parameters or any other parameters that will have events generated for them by the PATROL Agents. Configuring Monitor Thresholds To configure monitor thresholds: 1. Log on to BMC ProactiveNet Central Monitoring Administration. 2. Edit the Monitoring Policy that applies to the PATROL Agent for which you need to configure thresholds: In the Navigation pane, click the Policies drawer Expand the Monitoring folder and select a policy view (e.g. All). Select your policy and click. Configuring Monitor Settings 38

3. Check the Server Threshold Configuration box. 4. Click the Server Threshold Configuration link. 5. In the Server Threshold Configuration page, click. 6. Select the relevant Solution, Version, and Monitor Type. 7. 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:?, +, *, ( ),, [ ], { }, ^, $, 8. Check the Match Device Name box if you want the entire <devicename>\<instancename> string to be considered. 9. From the Attribute list, select a monitor attribute. 10. In the Threshold section: Select the threshold type. Set the threshold parameters values. Click Add. 11. Resume the procedure to configure all the monitor thresholds required. 12. Click Close. The configuration details are displayed in the Server Threshold Configuration page. 13. Click Finish. New threshold configurations are pushed to BMC PATROL Agents with matching Central Monitoring Configuration tags. Editing a Threshold Configuration To edit a threshold configuration: 1. Log on to BMC ProactiveNet Central Monitoring Administration. 2. Edit the Monitoring Policy that applies to the PATROL Agent for which you need to edit thresholds: In the Navigation pane, click the Policies drawer Expand the Monitoring folder and select a policy view (e.g. All). Select your policy and click. 3. Click the Server Threshold Configuration link. 4. On the Server Threshold Configuration page, select an Instance Name and click. 5. Edit the threshold configuration values and click Update. 6. When you finish editing the threshold configuration, click Close. 7. Click Finish. Updated threshold configurations are pushed to BMC PATROL Agents with matching Central Monitoring Configuration tags. 39 Configuring Monitor Settings

Deleting a Threshold Configuration To delete a threshold configuration: 1. Log on to BMC ProactiveNet Central Monitoring Administration. 2. Edit the Monitoring Policy that applies to the PATROL Agent for which you need to edit thresholds: In the Navigation pane, click the Policies drawer Expand the Monitoring folder and select a policy view (e.g. All). Select your policy and click. 3. Click the Server Threshold Configuration link. 4. On the Server Threshold Configuration page, select an Instance Name and click 5. Click Yes to confirm deletion. 6. After you delete one or more threshold configurations, click Finish to save changes to the policy. Deleted threshold configurations are removed from BMC PATROL Agents with matching Central Monitoring Configuration tags. Managing Monitoring Policies A monitoring 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. This topic provides general instructions for the following monitoring policy management tasks: Editing an existing monitoring policy Deleting a monitoring policy Enabling/disabling a monitoring policy Editing an existing monitoring policy An existing monitoring policy can be edited as follows: 1. In the Navigation pane of Central Monitoring Administration, click the Policies drawer. 2. Expand the Monitoring folder and select a policy view (e.g. All). 3. Select your policy and click. Configuring Monitor Settings 40

4. Select one or several Optional Configuration options. 5. Click Next to go through the Monitoring Policy Configuration wizard to edit the monitoring policy settings. 6. Click Finish. The updated monitoring policy is then deployed to the PATROL agents. Deleting a monitoring policy Deleting a monitoring policy may have deep consequences in a production environment. Before deleting a policy, it is recommended to create a new policy with a lower precedence number that will override the older policy. Once this new policy has been thoroughly tested, validated and enabled in production, you can delete the old one. To delete an old monitoring policy: 1. In the Navigation pane of Central Monitoring Administration, click the Policies drawer. 2. Expand the Monitoring folder and select a policy view (e.g. All). 3. Select the monitoring policy to be deleted and click. 4. Click Yes to confirm deletion. 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. Enabling/disabling a monitoring policy For maintenance and troubleshooting it can be useful to enable or disable policies. 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. 2. Expand the Monitoring folder and select a policy view (e.g. All). 3. Select one or more policies and click: to enable your policy. Please note that policies should not be enabled until they have been tested and validated for production. to disable your policy. 41 Configuring Monitor Settings

Monitoring your Storage Environment

Monitoring IBM SVC storage systems with BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring is very simple. Once the monitoring solution is properly installed and configured, BPPM IBM SVC Storage Monitoring automatically detects all the various IBM SVC storage features and components and displays them in the BMC ProactiveNet Operations Console. BPPM IBM SVC Storage Monitoring can help you: Identify a node overload Diagnose slow volumes Identify busiest volumes Report disk space consumption View the overall activity of a storage system 43

Identifying a Node Overload To visualize the activity of a node, use the Processor Utilization attribute of the Node monitor. A warning is issued when the processor utilization goes too high, which means that the nodes cannot keep up with the load on the storage system. It is then important to identify what is overloading the nodes. The Received Response Time and Sent Response Time attributes of the Node monitor represents the average time it took the node to process the receive and send requests of the hosts. The higher the response time goes, the slower I/Os the servers will get. By default, the solution triggers a warning when the node takes more than 30 milliseconds on average to complete the I/ O requests and an alarm when the response time reaches 100 milliseconds. Creating the Node Overload View Step 1: Displaying the Processor Utilization Attribute 1. Log on to the BMC ProactiveNet Operations Console. 2. Display the list of devices monitored by BPPM: In the Navigation frame, select the Main drawer. Click Devices. Click to display the list of devices in a grid. 3. Click the device for which you need to create the Node Overload view. 4. The list of monitors for your device is displayed. Expand Nodes. Displaying the IBM SVC Nodes 5. Click for one of the listed nodes. 6. By default, the Processor Utilization attribute is displayed. 7. Add the graph to the view: Click. The following pop-up is displayed: 44

Adding a Graph to View - Step 1 Click Add to View. Adding a Graph to View - Step 2 In the View Title field, type Node Overload and click Add View. The View created successfully message appears. Click Close. 8. The Node Overload view is now created and available under the Views & Graphs drawer in the Navigation pane. 9. Resume the procedure to add to the view the Processor Utilization attributes of all the nodes that compose the IBM SVC storage system. Step 2: Displaying the Response Time Attributes 1. In the Main drawer of the BMC ProactiveNet Operations Console, click Devices. 2. Click the relevant device. 3. The list of monitors for your device is displayed. Expand Nodes. Displaying the IBM SVC Nodes 45 Identifying a Node Overload

4. Click for one of the listed nodes. 5. By default, the Processor Utilization attribute is displayed. We will now display the Received Response Time and Sent Response Time attributes. The procedure is as follows: Click the Attributes & Indicators tab. Uncheck the Processor Utilization box. Check the Received Response Time and Sent Response Time boxes. Selecting the Attributes to Display in the Graph Click Generate Graph(s). 6. Add the graph to the view: Click Adding a Graph to View.The following pop-up is displayed: From the Add to View list, select Node Overload and click Add to View. The Graph added successfully message appears. Click Close. 7. Resume the procedure to add to the view the Received Response Time and Sent Response Time attributes of all the nodes that compose the IBM SVC storage system. Identifying a Node Overload 46

Diagnosing Slow Volumes If a system administrator complains that his servers are experiencing slow I/Os performance and that it is caused by the SAN, you may want to verify the actual response time of the volumes the server is relying on. The Response Time attributes (Read Response Time and Write Response Time) of the volume monitor type represent the time it took to complete the read and write operations on the volume during the collection interval. Typically, the average response time is below 10 milliseconds. You may also want to compare these values to the response time of the other volumes to see whether one server is really getting worse I/O performance than another. Creating the Slow Volumes View 1. Log on to the BMC ProactiveNet Operations Console. 2. Display the list of devices monitored by BPPM: In the Navigation frame, select the Main drawer. Click Devices. Click to display the list of devices in a grid. 3. Click the device for which you need to create the Slow Volumes view. 4. The list of monitors for your device is displayed. Expand Volumes. Selecting a Volume 5. Click for one of the listed volumes. 6. By default, the Consumed Capacity Percentage attribute is displayed. For this use case, we will only display the Read Response Time and the Write Response Time attributes. The procedure is as follows: Click the Attributes & Indicators tab. Uncheck the Consumed Capacity Percentage box. Check the Read Response Time and the Write Response Time boxes. 47 Identifying a Node Overload

Selecting Attributes Click Generate Graph(s) 7. Add the graph to the view: Click. The following pop-up is displayed: Adding a Graph to View - Step 1 Click Add to View. Adding a Graph to View - Step 2 Diagnosing Slow Volumes 48

In the View Title field, type Slow Volumes and click Add View. The View created successfully message appears. Click Close. 8. The Slow Volumes view is now created and available under the Views & Graphs drawer in the Navigation pane. 9. Repeat the procedure to add to the view the Response Time attributes of all the volumes that compose the IBM SVC storage system. 49 Diagnosing Slow Volumes

Identifying Busiest Volumes To identify the volumes that generate the most traffic, you can create a specific view that will display the Read Byte Rate and Write Byte Rate attributes of the Volumes Monitor. Creating the Busiest Volumes View 1. Log on to the BMC ProactiveNet Operations Console. 2. Display the list of devices monitored by BPPM: In the Navigation frame, select the Main drawer. Click Devices. Click to display the list of devices in a grid. 3. Click the device for which you need to create the Busiest Volumes view. 4. The list of monitors for your device is displayed. Expand Volumes. Displaying the IBM SVC Volumes 5. Click for one of the listed volumes. 6. By default, the Consumed Capacity Percentage attribute is displayed. For this use case, we will only display the Read Byte Rate and the Write Byte Rate attributes. The procedure is as follows: Click the Attributes & Indicators tab. Uncheck the Consumed Capacity Percentage box. Check the Read Byte Rate and Write Byte Rate boxes. Diagnosing Slow Volumes 50

Selecting the Attributes to Display in the Graph Click Generate Graph(s) 7. Add the graph to the view: Click. The following pop-up is displayed: Adding a Graph to View - Step 1 Click Add to View. 51 Identifying Busiest Volumes

Adding a Graph to View - Step 2 In the View Title field, type Busiest Volumes and click Add View. The View created successfully message appears. Click Close. 8. The Busiest Volumes view is now created and available under the Views & Graphs drawer in the Navigation pane. 9. Resume the procedure if you want to add to the view the Read Byte Rate and Write Byte Rate attributes of the volumes you are interested in. Identifying Busiest Volumes 52

Reporting Disk Space Consumption Making sure that a storage unit has enough remaining disk space available is critical for several reasons: SAN administrators want to make sure to be able to provision disk space for new servers when requested, as quickly as possible. The storage system itself may need additional disk space for specific features to work properly, like automatic snapshots, mirroring, etc. If thin provisioning is used, the remaining disk space becomes dramatically critical since the inability to allocate additional space to a volume when requested by the subscriber host will lead to catastrophic data loss and corruption. The disk space used is permanently monitored for each pool. The Subscribed Capacity attribute of the Pool monitor type represents the amount of disk space that has been made available to the subscriber hosts, or in other words, the amount of disk space that is seen by the servers connected to the storage unit. The Consumed Capacity attribute of the Pool monitor type represents the actual space usage in the pool. For thin pools (when thin provisioning is enabled on the storage system), this value is normally lower than the Subscribed Capacity, as it is the main purpose of thin provisioning. For traditional pools, the Consumed Capacity attribute has the same value as the Subscribed Capacity attribute, as the entirety of the subscribed disk space is fully allocated in the storage pool. The Consumed Capacity Percentage attribute is the most critical one, even for pools, as a pool nearing 100% means that SAN administrators will not be able to create new volumes in the pool. By default, no alarm or warning threshold is set on this attribute as the fullness of a pool may be a normal situation. Creating the Disk Space Consumption View 1. Log on to the BMC ProactiveNet Operations Console. 2. Display the list of devices monitored by BPPM: In the Navigation frame, select the Main drawer. Click Devices. Click to display the list of devices in a grid. 53 Identifying Busiest Volumes

3. Click the device for which you need to create the Disk Space Consumption view. 4. The list of monitors for your device is displayed. Expand Pools. Displaying a Pool 5. Click for one of the listed pools. 6. By default, the Read Byte Rate and Write Byte Rate attributes are displayed. For this use case, we will display the Subscribed Capacity, Consumed Capacity and Consumed Capacity Percentage attributes. The procedure is as follows: Click the Attributes & Indicators tab. Uncheck the Consumed Capacity Percentage and Operation Rate boxes. Check the Subscribed Capacity, Consumed Capacity and Consumed Capacity Percentage boxes. Selecting Attributes Click Generate Graph(s) 7. Add the graph to the view: Click. The following pop-up is displayed: Reporting Disk Space Consumption 54

Adding a Graph to View - Step 1 Click Add to View. Adding a Graph to View - Step 2 In the View Title field, type Disk Space Consumption and click Add View. The View created successfully message appears. Click Close. 8. The Disk Space Consumption view is now created and available under the Views & Graphs drawer in the Navigation pane. 9. Repeat the procedure if you want to add to the view the Subscribed Capacity, Consumed Capacity and Consumed Capacity Percentage attributes of the next pool you are interested in. 55 Reporting Disk Space Consumption

Viewing the Overall Activity of a Storage System In order to visualize the activity of a storage system, use the Read Byte Rate and Write Byte Rate attributes of the Storage System monitor. These attributes represent the overall traffic in megabytes per second for each monitored system. Creating the Overall Activity of a Storage System View 1. Log on to the BMC ProactiveNet Operations Console. 2. Display the list of devices monitored by BPPM: In the Navigation frame, select the Main drawer. Click Devices. Click to display the list of devices in a grid. 3. Click the device for which you need to create the Overall Activity of a Storage System view. 4. The list of monitors for your device is displayed. Displaying the IBM SVC Storage Systems 5. Click for one of the listed storage systems. 6. By default, the Read Byte Rate and Write Byte Rate attributes are already displayed. 7. Add the graph to the view: Click. The following pop-up is displayed: Reporting Disk Space Consumption 56

Adding a Graph to View - Step 1 Click Add to View. Adding a Graph to View - Step 2 In the View Title field, type Overall Activity of a Storage System and click Add View. The View created successfully message appears. Click Close. 8. The Overall Activity of a Storage System view is now created and available under the Views & Graphs drawer in the Navigation pane. 57 Viewing the Overall Activity of a Storage System

Viewing the Overall Activity of a Storage System 58

Reference Guide

Monitor Types and Attributes Introduction This chapter lists all the monitor types and attributes provided by BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring to monitor your systems. Please note that depending on the type of managed systems, some attributes may not be available. Monitor Types IBM SVC FC Port IBM SVC iscsi Port IBM SVC MDisk IBM SVC Node IBM SVC Pool IBM SVC SAN Volume Controller IBM SVC Volume IBM SVC Volume Mirror IBM SVC Storage System 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 and included by default in the baseline calculation process are respectively identified by the following icon: KPI Monitor Types and Attributes 60

IBM SVC FC Port Attributes Name Description Units Default Alert Conditions BMC ProactiveNet Attribute Type Bad CRC Bandwidth Utilization Invalid Transmission Words Indicates the number of CRC that are not valid. Percentage used of the available bandwidth. Indicates the number of transmission word counts that are not valid. Errors Percentage (%) Words Warning if 1 Warning if 1 Link Failures Indicates a link failure count. Failures Warning if 1 Link Speed Indicates the FC interface link speed. Megabytes per seconds (MB/s) Loss Of Signal Indicates the loss-of-signal count. Losses Warning if 1 Loss Of Synch Indicates the loss-of-synchronization count. Losses Warning if 1 Protocol Errors Indicates the protocol error count. Errors Warning if 1 Received Byte Rate Received From Hosts Write Rate Received From Other Cluster Byte Rate Received From Same Cluster Byte Rate Received From Storage Byte Rate Indicates the number of bytes sent from host, disk controllers, and other nodes in the same and other clusters. Indicates the number of megabytes received from hosts per second. Indicates the number of megabytes received from other nodes. Indicates the number of megabytes received from the same cluster. Indicates the number of megabytes received from storage. Megabytes per seconds (MB/s) Megabytes per seconds (MB/s) Megabytes per seconds (MB/s) Megabytes per seconds (MB/s) Megabytes per seconds (MB/s) 61 Monitor Types and Attributes

Name Description Units Default Alert Conditions BMC ProactiveNet Attribute Type Sent Byte Rate Indicates the number of megabytes sent to host, disk controllers, and other nodes in the same and other clusters. Megabytes per seconds (MB/s) Sent To Hosts Byte Rate Indicates the number of megabytes transmitted to host. Megabytes per seconds (MB/s) Sent To Other Cluster Byte Rate Indicates the number of megabytes transmitted to other nodes in the other clusters. Megabytes per seconds (MB/s) Sent To Same Cluster Byte Rate Indicates the number of megabytes transmitted to other nodes in the same cluster. Megabytes per seconds (MB/s) Sent To Storage Byte Rate Indicates the number of megabytes transmitted to storage. Megabytes per seconds (MB/s) Status Indicates the status of the FC port. {0= OK; 1 = Degraded; 2= Failed} Zero Buffer Time Percentage Percentage of time where the port was unable to send data due to lack of buffer credit in the switch. Percentage (%) Availability Monitor Types and Attributes 62

IBM SVC iscsi Port Attributes Name Description Units Default Alert Conditions BMC Proactive Net Attribute Type Status Indicates the status of the iscsi port. {0= OK; 1 = Degraded; 2= Failed} 1 = Warning 2 = Alarm Availabil ity Link Speed Indicates the iscsi interface link speed. Megabytes per seconds (MB/s) Bandwidth Utilization Percentage used of the available bandwidth. Percentage (%) Received Byte Rate Indicates the number of megabytes received per second. Megabytes per seconds (MB/s) Received From Hosts Byte Rate Received From Other Cluster Byte Rate Received From Same Cluster Byte Rate Received From Storage Byte Rate Indicates the number of megabytes received from hosts per second. Indicates the number of megabytes received from other nodes. Indicates the number of megabytes received from the same cluster. Indicates the number of megabytes received from storage. Megabytes per seconds (MB/s) Megabytes per seconds (MB/s) Megabytes per seconds (MB/s) Megabytes per seconds (MB/s) 63 Monitor Types and Attributes

Name Description Units Default Alert Conditions BMC Proactive Net Attribute Type Sent Byte Rate Indicates the number of megabytes sent to host, disk controllers, and other nodes in the same and other clusters. Megabytes per seconds (MB/s) Sent To Hosts Byte Rate Indicates the number of megabytes transmitted to host. Megabytes per seconds (MB/s) Sent To Other Cluster Byte Rate Indicates the number of megabytes transmitted to other nodes in the other clusters. Megabytes per seconds (MB/s) Sent To Same Cluster Byte Rate Sent To Storage Byte Rate Indicates the number of megabytes transmitted to other nodes in the same cluster. Indicates the number of megabytes transmitted to storage. Megabytes per seconds (MB/s) Megabytes per seconds (MB/s) Monitor Types and Attributes 64

IBM SVC MDisk Attributes Name Description Units Default Alert Conditions BMC ProactiveNe t Attribute Type Available Path Count Indicates the number of nodes that have access to the managed disk. Paths 0 = Alarm Status Indicates the status of the managed disk. {0=OK; 1 = Degraded; 2 = Failed} 1 = Warning 2 = Alarm Availabilit y Read Byte Rate Indicates the amount of data read from the disk. Megabytes per seconds (MB/ s) Read Operation Rate Read Response Time Write Byte Rate Write Operation Rate Write Response Time Indicates the amount of operations read per second Indicates the average time for a disk to complete a read request Indicates the amount of data written per second. Indicates the amount of operations written per second. Indicates the average time for a disk to complete a write request. Operations per seconds (operations/s) Milliseconds (ms) Megabytes per seconds (MB/ s) Operations per seconds (operations/s) Milliseconds (ms) Warning 10 ms Alarm 100ms Warning 10 ms Alarm 100ms Response Time Response Time 65 Monitor Types and Attributes

IBM SVC Node Attributes Name Description Units Default Alert Conditions BMC ProactiveNet Attribute Type Processor Utilization Indicates the percentage of utilization of the processor. Percen tage (%) Warning when greater than 90%; Alarm when greater than 99% Received Byte Rate Indicates the number of megabytes received per second. Megab ytes per second s (MB/ s) Received Operation Rate Received Response Time Sent Byte Rate Sent Operation Rate Sent Response Time Indicates the number of operations received per second. Indicates the average time taken to complete receive requests. Indicates the megabytes sent. Indicates the number of operations sent. Indicates the average time taken to complete send requests. Operat ions per second s (operat ions/s) Millise conds (ms) Megab ytes per second s (MB/ s) Operat ions per second s (operat ions/s) Millise conds (ms) Warning when greater than 10 ms; Alarm when greater than 100ms Warning when greater than 10 ms; Alarm when greater than 100ms Response Time Response Time Monitor Types and Attributes 66

Name Description Units Default Alert Conditions BMC ProactiveNet Attribute Type Status For detailed information about Indicates the status of the node. {0= OK; 1 = Degrad ed; 2= Failed} 1 = Warning 2 = Alarm KPI, see Managing Baselines and Key Performance Indicators. Availability 67 Monitor Types and Attributes

IBM SVC Pool Attributes Name Description Units Default Alert Conditions BMC ProactiveN et Attribute Type Consumed Capacity Indicates the total size of the space actually allocated or reserved. Gigabytes (GB) Consumed Capacity Percentage Indicates the percentage of the pool that is actually allocated or reserved. Percentage (%) Alarm if 75% Status Subscribed Capacity Subscribed Capacity Percentage Read Byte Rate Write Byte Rate Indicates the status of the pool. Indicates the total host visible capacity. Indicates the percentage of the pool that is subscribed. Indicates the amount of data read from the disk. Indicates the amount of data written per second. {0=OK; 1 = Degraded; 2 = Failed} Gigabytes (GB) Percentage (%) Megabytes per seconds (MB/s) Megabytes per seconds (MB/s) 1 = Warning 2 = Alarm Availabili ty Monitor Types and Attributes 68

IBM SVC SAN Volume Controller Attributes Name Description Units Default Alert Conditions BMC ProactiveNet Attribute Type Collection Status Port Count Time Since Last Update Indicates the status of the collection. Number of FC and Ethernet ports on the Storage System. Note: This value can be used to know the number of required licenses for the monitoring system. Displays the number of minutes since a new statistics file was created on the cluster. {0= OK; 1 = Degraded; 2= Failed} 1 = Warning 2 = Alarm Collection Status Ports minutes Warning when > 30 69 Monitor Types and Attributes

IBM SVC Volume Attributes Name Description Units Default Alert Conditions BMC ProactiveNet Attribute Type Consumed Capacity Indicates the total size of the space actually allocated or reserved. Gigabyt es (GB) Consumed Capacity Percentage Indicates the percentage of the volume that is actually allocated or reserved. Percent age (%) Host Visible Capacity Indicates the real capacity of the volume primary copy. Gigabyt es (GB) Read Byte Rate Read Operation Rate Read Response Time Status Time Since Last Activity Indicates the amount of data read per second. Indicates the amount of operations read per second. Indicates the average time taken to complete a read request Indicates the status of the volume. Number of days since any activity occurred on the LUN. Megaby tes per seconds (MB/s) Operati ons per seconds (operati ons/s) Millisec onds (ms) {0=OK;1 = Degrade d;2= Failed} Warning if 10ms Alarm if 100ms 1 = Warning 2 = Alarm Response Time Availability days Monitor Types and Attributes 70

Name Description Units Default Alert Conditions BMC ProactiveNet Attribute Type Write Byte Rate Indicates the amount of data written per second. Megaby tes per seconds (MB/s) Write Operation Rate Indicates the amount of operations written per second. Operati ons per seconds (operati ons/s) Write Response Time Indicates the average time taken to complete a write request. Millisec onds (ms) Warning if 10ms Alarm if 100ms Response Time 71 Monitor Types and Attributes

IBM SVC Volume Mirror Attributes Name Description Units Default Alert Conditions BMC ProactiveNet Attribute Type Status Synchronized* Indicates the status of the volume mirror. Indicates whether the Volume Mirror is synchronized with the volume it belongs to. {0=OK;1 = Degrade d;2= Failed} {0 = No; 1 = Yes} 1 = Warning 2 = Alarm Availability 0 = Warning Monitor Types and Attributes 72

IBM SVC Storage System Attributes Name Description Units Default Alert Conditions BMC Proactive Net Attribute Type Read Byte Rate Indicates the amount of data read per second. Megabytes per seconds (MB/s) Statistic s Read Operation Rate Indicates the amount of operations read per second Operation s per seconds (operation s/s) Statistic s Read Response Time Indicates the average time taken to complete a read request Millisecon ds (ms) Warning if > 10 ms Alarm if > 100 ms Respons e Time Status Write Byte Rate Write Operation Rate Write Response Time For detailed information about Indicates the status of the storage system. Indicates the amount of data written per second. Indicates the amount of operations written per second. Indicates the average time taken to complete a write request. {0 = OK ; 1 = Degraded ; 2 = Failed} Megabytes per seconds (MB/s) Operation s per seconds (operation s/s) Millisecon ds (ms) KPI, see Managing Baselines and Key Performance Indicators. 1 = Warning 2 = Alarm Warning if > 10 ms Alarm if > 100 ms Availabi lity Statistic s Statistic s Respons e Time 73 Monitor Types and Attributes

Configuration Variables This section lists the advanced configuration variables that can be set in an IBM SVC Storage policy. Variables Default Value Description AlertActions n/a List of alert actions to be executed by BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring upon a problem with the managed SVC systems. collectionhubheapsizemax n/a Maximum heap size in megabytes allocated to the Java Collection Hub. Default: Not set collectionhubheapsizemin n/a Minimum heap size in megabytes allocated to Java Collection Hub. Default: Not set collectionhuboverridejavacom mandline n/a Command line used by the KM to launch the Java Collection Hub. Default: Not set This variable should only be set if instructed by Sentry Support. debugendtime Specifies when the debug mode will be disabled. Format required: YYYY/MM/DD HH:MM:SS debugmode 0 = disabled When set to '1', enables the debug mode of the KM. Default: Not set defaultreinitializationoptions List of default options to be executed by BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring on reinitialization. The default values are: 0=unchecked; 1=checked resetthresholds disablejavainformationmessag e resetthresholdmanagementmode resetalertactions resetotheralertsettings resetdebugmode resetremovedpausedobjectlist resetreport resetsecuritysettings resetjavasettings Insert a colon ; between the variable and its value: resetthresholds;1. If you enter multiple variables, they need to be separated by a carriage return. Example: resetthresholds;1 will display the remove thresholds option selected by default in the Reinitialize KM wizard. 0 = activated When set to 1, disables the pop-up information message displayed when the java settings are modified. Default: Not set disablejrecheck 0 When set to 1, disables the validation tests of the JRE used by the KM to run Java code and therefore force the KM to use a non-sun or non-oracle JRE disablepslexecutebugworkarou nd 0 = activated When set to 1, deactivates the workaround in the KM for a bug in the PslExecute() PSL function. Monitor Types and Attributes 74

Variables Default Value Description If the KM detects that the version of the PATROL Agent is affected by the PslExecute() bug, it uses an alternate technique to create asynchronous threads with the event_trigger() function and the RemPsl standard event. The disablepslexecutebugworkaround variable disables this workaround. discoveryintervalminutes 60 Specifies how often discoveries will be performed to detect new components (in minutes). excludevolumes Filter to exclude all volumes whose names match the specified regular expression. exportactivityreports When set to 1, the SEN_SVC_activity*.csv report is automatically generated and stored in the % PATROL_HOME%\log folder. exportlunsmappingtable When set to 1, the SEN_SVC_LUNS_mapping_table*.csv report is automatically generated and stored in the % PATROL_HOME%\log folder. exportscheduling Time when the activity and/or LUNs Mapping Table reports will be generated. Format required: HH:MM:SS forceclassicconfigmode 0 = disabled When the KM is used with BMC ProactiveNet, all the KM configuration menus are disabled in the PATROL Consoles. To enable them, set the forceclassicconfigmode variable to 1. includevolumes Filter to keep only volumes whose names match the specified regular expression. javapassword Password associated to the javausername variable. javapath Path to the folder containing the Java executable used by the Collection Hub. Default: Not set (The KM will search for a suitable JRE automatically). javausername Username used to launch the Java Collection Hub. Default: Not set. variable. parametersautoresettimeout Indicate the time in seconds after which the incremental parameters should be automatically reset when an error is detected. pausedobjectlist n/a List of the PATROL object path of the paused objects. (i.e. for which no collection will be performed). pemmessages All How much internal information should be sent as PATROL events. When set to all, all internal KM messages (problems and informational messages). When set to problems, only errors and problems. When set to none, no internal message at all. This doesn t affect the reporting of actual hardware problems. pollinginterval 120 Interval in seconds at which the KM gathers the statistics files from the IBM SVC nodes. 75 Monitor Types and Attributes

Variables Default Value Description removedobjectlist n/a List of instances that have been removed from the monitoring environment through the Remove KM Command. sowmessages All How much internal information should be displayed in the System Output Window in the PATROL Console. When set to all, all internal KM messages (problems and informational messages). When set to problems, only errors and problems. When set to none, no internal message at all. This doesn t affect the reporting of actual hardware problems. staticthresholdsparameterlist List of parameters for which custom thresholds have been set through the Modify Thresholds KM command. temporaryfolder Path to the folder where temporary files used by the KM to compute statistics will be stored. Default: Not set (assumed PATROL Agent s own temporary folder) ThresholdsManagementMode unexpectedstatusinternalissue Notification Retrieved from the KM configuration 0 = deactivated Specifies how the KM should manage the alert thresholds on parameters. Please read carefully the User Guide chapter for more information on this topic. Possible values: 'empty' (automatic detection of the suitable threshold management) as (through PATROL for Event Management) tuning (through the standard "Override parameter" mechanism) none (No threshold is set by the KM) Default: Not set (automatic) When set to 1, the KM will inform you of any internal problems or of any special operations it may perform. unexpectedstatusmanagement Specifies the action to be performed when the product is unable to interpret a status value. Format: <alarm type>;<internal issue notification> Possible alarm type values: ALARM OK WARN Default: OK Possible internal issue notification values: 1: trigger an internal issue notification 0: do not trigger an internal issue notification Default: 0 Monitor Types and Attributes 76

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 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. 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 77 Monitor Types and Attributes

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. Monitor Types and Attributes 78

Index - A - Abnormalities 77 Add Monitor Types 24 Advanced Configuration Variables AlertActions 32 collectionhubheapsizemax 32 collectionhubheapsizemin 32 collectionhuboverridejavacommandline 32 debugmode 32 defaultreinitializationoptions 32 disablejavainformationmessage 32 disablejrecheck 32 disablepslexecutebugworkaround 32 excludevolumes 32 exportscheduling 32 forceclassicconfigmode 32 includevolumes 32 javapassword 32 javapath 32 javausername 32 pausedobjectlist 32 productversion 32 pscommand 32 removedobjectlist 32 scheduledreports 32 startupdelay 32 ThresholdsManagementMode 32 Attributes 60 Available Path Count 65 Bad CRC 61 Bandwidth Utilization 61, 63 Collection Status 69 Consumed Capacity 53, 68, 70 Consumed Capacity Percentage 53, 68, 70 Host Visible Capacity 70 Invalid Transmission Words 61 Link Failures 61 Link Speed 61, 63 Loss Of Signal 61 Loss Of Synch 61 Port Count 69 Processor Utilization 44, 66 Protocol Errors 61 Read Byte Rate 65, 70, 73 Read Operation Rate 65, 70, 73 Read Response Time 65, 70, 73 Received Byte Rate 56, 61, 63, 66 Received From Hosts Byte Rate 63 Received From Hosts Write Rate 61 Received From Other Cluster Byte Rate 61, 63 Received From Same Cluster Byte Rate 61, 63 Received From Storage Byte Rate 61, 63 Received Operation Rate 66 Received Response Time 66 Response Time 44, 47 Sent Byte Rate 56, 61, 63, 66 Sent Operation Rate 66 Sent Response Time 66 Sent To Hosts Byte Rate 61, 63 Sent To Other Cluster Byte Rate 61, 63 Sent To Same Cluster Byte Rate 61, 63 Sent To Storage Byte Rate 61, 63 Status 61, 63, 65, 66, 68, 70, 72, 73 Subscribed Capacity 53, 68 Subscribed Capacity Percentage 68 Synchronized 72 Time Since Last Activity 70 Time Since Last Update 69 Write Byte Rate 65, 70, 73 Write Operation Rate 65, 70, 73 Write Response Time 65, 70, 73 Zero Buffer Time Percentage 61 Automatic Reporting 37 - B - Baselines BMC ProactiveNet Performance Management 77 Generation 77 Manage 77 Requirements 77 BMC ProactiveNet Performance Management Abnormalities 77 Baselines 77 Key Performance Indicators 77 KPI 77 Busiest Volume identifying 50 79

- C - Component Installation package creating 17 downloading 18 Configuration Variables AlertActions 74 collectionhubheapsizemin 74 collectionhuboverridejavacommandline 74 debugendtime 74 debugmode 74 defaultreinitializationoptions 74 disablejavainformationmessage 74 disablejrecheck 74 disablepslexecutebugworkaround 74 discoveryintervalminutes 74 excludevolumes 74 exportactivityreports 74 exportlunsmappingtable 74 exportscheduling 74 forceclassicconfigmode 74 includevolumes 74 javapassword 74 javapath 74 javausername 74 parametersautoresettimeout 74 pausedobjectlist 74 pemmessages 74 pollinginterval 74 removedobjectlist 74 sowmessages 74 staticthresholdsparameterlist 74 temporaryfolder 74 ThresholdsManagementMode 74 unexpectedstatusinternalissuenotification 74 unexpectedstatusmanagement 74 Configuring discovery interval 30 monitor settings 24 Configuring Monitor Thresholds 38 Configuring thresholds 38 - D - Debug Mode enabling 28 Deleting a policy 41 Deleting a Threshold Configuration 40 Diagnose Slow Virtual Volume 47 Disabling a policy 41 Discovery Interval configuring 30 Disk Read Byte Rate 50 Disk Space Consumption 53 Disk Write Byte Rate 50 Downloading 18 - E - Editing a policy 40 Editing a Threshold Configuration 39 Enabling a policy 41 - F - Features 12 Fixed Issues 7 - G - Generate Baselines 77 Goals 12 Graph - I - create 50 Identify Node Overload 44 Importing the Monitoring Solution 16 Installation configuring 22 Installing 18 Installing the Monitoring Solution 16 Integrating 20 - K - Key Concepts 11 Key Performance Indicators 80

Key Performance Indicators BMC ProactiveNet Performance Management 77 Manage 77 KPI BMC ProactiveNet Performance Management 77 Manage 77 - M - Policy 40, 41 - R - Read Byte Rate 50 Reference Guide 60 Reporting Disk Space Consumption 53 Reports scheduling 37 Manage Baselines 77 Key Performance Indicators 77 KPI 77 Managing Policies 40 Monitor Settings configuring 24 Monitor thresholds 38 Monitor Type IBM SVC SAN Volume Controller 69 Monitor Types 60 IBM SVC FC Port 61 IBM SVC iscsi Port 63 IBM SVC MDisk 65 IBM SVC Node 66 IBM SVC Pool 68 IBM SVC Storage System 73 IBM SVC Volume 70 IBM SVC Volume Mirror 72 Monitoring Storage 43 volumes 35 Monitors HP 3PAR Node 44 HP 3PAR Storage Pool 53 HP 3PAR Storage System 56 HP 3PAR Volume 47 - O - Overload - P - Node 44 Package 17, 18 Policies 40 - S - Scheduling Reports 37 Storage Monitoring 43 Storage System - T - Overall activity 56 Tags 22 Thresholds 38 - U - Use Case 43 - V - Variables AlertActions 32 collectionhubheapsizemax 32 collectionhubheapsizemin 32 collectionhuboverridejavacommandline 32 debugmode 32 defaultreinitializationoptions 32 disablejavainformationmessage 32 disablejrecheck 32 disablepslexecutebugworkaround 32 excludevolumes 32 exportscheduling 32 forceclassicconfigmode 32 hostname 32 includevolumes 32 javapassword 32 81

Variables javapath 32 javausername 32 password 32 pausedobjectlist 32 productversion 32 pscommand 32 removedobjectlist 32 scheduledreports 32 startupdelay 32 ThresholdsManagementMode 32 View create 50 Virtual Volume Slow 47 Volumes filtering 35 - W - What's New 7 Write Byte Rate 50 82

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 www.bmc.com. LEARN MORE To learn more about our solutions, please visit : www.sentrysoftware.com/solutions Like us on Facebook: facebook.com/sentrysoftware Follow us on Twitter: twitter.com/sentrysoftware BMC Software, Inc. All rights reserved.