Sentry HP EVA ProactiveNet Performance Management Storage Monitoring Solution User Documentation
Below you will find brief information for Storage Monitoring HP EVA ProactiveNet Performance Management. This solution allows you to view, monitor, and manage your entire HP EVA storage environment by viewing the current and historical information through a centralized console. You can view detailed system metrics on all parts of your environment, such as nodes, controllers, host ports, data replication tunnels, physical disks, virtual disks, virtual disk groups, host connections, and port status. It helps you to identify performance bottlenecks, manage disk space consumption, pinpoint unused disk capacity, and analyze overall traffic and in-depth I/Os.
Advertisement
Advertisement
USER DOCUMENTATION
STORAGE MONITORING
BMC ProactiveNet Performance
Management - HP EVA Storage
Monitoring
Version 1.3.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 email 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
4
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.
7
Key Concepts
The pages in this section provide a high-level overview of the product.
Note that for convenience and brevity, reference to BMC ProactiveNet Performance Management - HP EVA
Storage Monitoring, may also be made as BPPM HP EVA Storage Monitoring.
User Goals and Features
BMC ProactiveNet Performance Management - HP EVA Storage Monitoring product allows you to view, monitor, and manage your entire HP EVA storage 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 - HP EVA Storage Monitoring enables you to manage the following in your environment:
Nodes: available capacity, byte rate, port count...
Controllers: processor utilization, transfer processor utilization, status...
Host Ports: read byte rate, read request rate, read response time...
Data Replication Tunnel: copy in/out byte rate, free command resources, Round Trip Delay
Physical Disks: read byte rate, read request rate, request queue...
Virtual Disks: cache hit ratio, cache read byte rate, cache read request...
Virtual Disk Groups: cache hit ratio, cache read byte rate, cache read response time...
Host Connections: busy responses, request queue...
9
Business Value
BMC ProactiveNet Performance Management - HP EVA Storage Monitoring provides current and historical information through a centralized console so you can easily view and manage your entire HP EVA 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 HP EVA environment.
BMC ProactiveNet Performance Management - HP EVA Storage Monitoring: collects storage performance and metrics to keep total control of your SAN/NAS environment identifies performance bottlenecks (physical disks, controllers, fiber links, etc.) manages and helps rationalize disk space consumption pinpoints unused disk capacity analyzes overall traffic and in-depth I/Os, etc
Supported Platforms
BMC ProactiveNet Performance Management - HP EVA Storage Monitoring supports the entire
HP StorageWorks Enterprise Virtual Array Family (EVA).
User Goals and Features 10
Prerequisites
Integrated as a native module for PATROL, BMC ProactiveNet Performance Management - HP EVA
Storage Monitoring is designed to monitor the health and performance of your HP EVA storage environment. Prior to install BMC ProactiveNet Performance Management - HP EVA Storage
Monitoring on the HP Storage Server running Windows, make sure that the following elements are installed and properly configured:
PATROL Agent, version 3.8 or higher (see BMC PATROL documentation)
PATROL Console (see BMC PATROL documentation)
Java 1.6 or higher.
The PATROL Agent must be installed on the HP Storage Server provided with the HP EVA disk array. The HP Storage Server usually comes bundled with the HP EVA disk array and is fully preinstalled by HP.
HP Command View EVA
Specific information, such as virtual disk size, node name, RAID array are collected via the evaperf utility and Storage System Scripting Utility (SSSU.EXE) which are command line interfaces provided by HP that allows administrators to control EVA disk arrays. HP CommandView EVA valid account credentials (username and password) are required to run SSSU.
Make sure that the latest firmware has been installed on the controllers.
HP StorageWorks Command View 9.1 or higher must be properly installed on the Storage Server.
All the provided features must be installed.
12
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 HP EVA Storage Monitoring:
Importing BPPM HP EVA Storage Monitoring into Central Administration
Creating the Installation Package
Downloading the Installation 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.
14
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 Monitoring 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.
15 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
Monitoring 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.
1.
2.
3.
Installing the Package
Copy the installation package to the host where BMC ProactiveNet Performance Management - HP
EVA Storage Monitoring needs to be installed
Extract the installation package as appropriate for your operating system. The package is extracted to the bmc_products directory on the current host.
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 16
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 - HP EVA 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.
18
Configuring After Installation
BMC ProactiveNet Performance Management - HP EVA Storage Monitoring is configured 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
Name
Tenant
(For environments with tenants)
Enable policy
Precedence
Description
Tag
Instructions
Enter a policy name. Policy names must be unique.
In an environment with tenants, policy names must be unique for a single tenant
Select a tenant name. See Policies and tenants for details.
Global indicates a policy applicable to all tenants.
Provider indicates a policy applicable to the cloud service provider
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.
Enter a number from 0 to 999.
(Optional) Enter a policy description.
Enter a Central Monitoring Administration tag.
Policies are applied to BMC PATROL Agents with matching tags.
Tags are case sensitive and cannot contain spaces or any of the following characters: /, \, {, }, <, >, ‘, “, &.
Policy precedence
When more than one policy is applied to a BMC PATROL Agent and BMC ProactiveNet Child
Server, configuration is a union of every attribute defined by the policies. If a conflict arises (that is, two policies configure the same attributes), it is resolved in one of the following ways:
20
Policies with the same tag: If conflicting policies have the same tag, the precedence value determines the order the policies are applied. The policy with the lower number value for precedence is the policy from which the final configuration is applied.
Policies with different tags: If conflicting policies have different tags, then the policies are applied according to the order they are listed on the BMC PATROL Agent. The policy listed last on the agent is the policy from which the final configuration is applied.
Managing Policies
This topic provides general instructions for the following policy management tasks: editing, deleting, enabling and disabling.
Before you begin
Enable Central Monitoring Administration and log on to Central Monitoring Administration. Refer to the BMC documentation and more especially to the section Enabling and configuring Central
Monitoring Administration for details.
Policies with only threshold configuration or server 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.
21 Configuring General Settings
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 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.
Configuring General Settings 22
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 HP EVA Storage.
6. From the Version menu, select the required version.
7. Enter the Connection Settings to the HP StorageWorks :
23 Configuring Monitor Settings
Username: Username to use for establishing a connection with HP StorageWorks.
Password: Username to use for establishing a connection with HP StorageWorks.
9. Configure the monitoring settings:
Use the spin button of the Discovery Interval field to enter the frequency in minutes of the discovery process. By default, the solution runs a discovery every 60 minutes
Use the spin button of the Polling Interval field to indicate how often new data is collected. By default, the polling interval is set to every 2 minutes.
Check the Disable Virtual Disks Monitoring box if you want to limit the number of instances created and therefore reduce the system resource consumption. Discovery and collect requests and operations will no longer be performed.
Configuring Monitor Settings 24
Specify the volumes to be excluded (Exclude Volumes field) or included (Keep Only
Volumes field). If you specify a regular expression based on the volume PATROL ID, all volumes that match with the specified regular expression will respectively be excluded or included.
10. Click Add to List to save the new connection to the HP StorageWorks.
11. Click Add. If the monitor configuration has been successfully added, click Close.
12. Click Save to save your policy.
25 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. Select the policy that applies to the PATROL Agent for which you need to enable the debug mode, and click Edit.
3. Click the Monitor Configuration tab.
4. Select the HP EVA Storage monitor type and click Edit.
5. Click the Advanced button.
Enabling the Debug Mode
Configuring Monitor Settings 26
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.
Managing Unknown Status
At times, although rare, BMC ProactiveNet Performance Management - HP EVA Storage
Monitoring is unable to detect the status of a monitored device, and returns the poll with
"Unknown Status".
When this situation occurs, you can configure the KM to perform certain actions:
Set the Status parameter to OK (default)
Ignore value and do not feed parameter
Trigger a WARNING on the Status parameter
Trigger an ALARM on the Status parameter
To enable the debug mode
1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view.
2. Select the policy that applies to the PATROL Agent for which you need to enable the debug mode, and click Edit.
3. Click the Monitor Configuration tab.
4. Select the HP EVA Storage monitor type and click Edit.
5. Click the Unknown Status button.
Unknown Status Management
27 Configuring Monitor Settings
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.
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"
Adding Tags to PATROL Agents 28
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.
29 Adding Tags to PATROL Agents
Configuring Thresholds
When you are creating or editing a policy, you can add and configure monitor thresholds. The
Add Thresholds dialog box presents threshold configuration fields for BMC ProactiveNet monitors that are configured through Central Monitoring Administration.
For details about baselines and Key Performance Indicators (KPI), see BMC ProactiveNet Central
Monitoring Administration or BMC ProactiveNet documentation or refer to the Managing
Baselines and Key Perf ormance Indicators section. For details about the monitored attributes, refer to the specific monitor type in the Ref erence Guide section.
Before you begin
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.
Configuring Monitor Thresholds
To configure monitor thresholds:
1. Create a new policy or edit an existing one.
2. Select the Threshold Configuration tab and click Add .
3.
In the Add Thresholds dialog box, select the relevant Solution, Version, and Monitor Type.
4. In the Instance Name field, specify the instance to which the threshold configuration will be applied. You can either use a string or the following regular expression patterns: ?, +, *, ( ), |,
[ ], { }, ^, $,
5. Select Match Device Name if you want the entire <deviceName>\<instanceName> string to be considered.
6. From the Attribute list, select a monitor attribute.
7. In the Threshold section:
Select the threshold type.
Set the threshold parameters values.
Click Add.
31
8. Resume the procedure to configure all the monitor thresholds required.
9. Click Close. The configuration details are displayed in the table on the Threshold
Configuration tab.
10. Click Save at the bottom of the Add Policy dialog box, or Update at the bottom of the Edit
Policy dialog box.
After you save or update the policy, new threshold configurations are pushed to BMC PATROL
Agents with matching Central Monitoring Configuration tags.
Editing a Threshold Configuration
To edit a threshold configuration:
1. Edit an existing policy
2. On the Threshold Configuration tab, select a threshold definition, and click Edit.
3. Edit the configuration values and click Update.
4. When you finish editing the threshold configuration, click Close.
5. To save changes to the policy, click Update at the bottom of the Edit Policy dialog box.
After you update the policy, updated threshold configurations are pushed to BMC PATROL Agents with matching Central Monitoring Configuration tags.
Deleting a Threshold Configuration
To delete a threshold configuration:
1. Edit an existing policy
2. On the Threshold Configuration tab, select attributes, monitor types, versions, or solutions.
3. Click Delete.
4. After you delete one or more threshold configurations, click Close.
5. To save changes to the policy, click Update at the bottom of the Edit Policy dialog box.
After you update the policy, deleted threshold configurations are removed from BMC PATROL
Agents with matching Central Monitoring Configuration tags.
Configuring Monitor Thresholds 32
Monitoring your Storage
Environment
Detecting High Processor Utilization
Detecting a high processor utilization is important to prevent controllers overloading that can lead to unpredictable performance degradations. To detect high processor utilization with BPPM, you can create a specific view to compare Processor Utilization and the Transfer Byte Rate attributes of all the controllers in your HP EVA storage systems and then determine which one may constitute a bottleneck.
Creating a High Processor Utilization 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.
Displaying devices in a grid
3. In the Devices drawer, click the first disk array for which you need to compare the controllers' processor utilization.
4. The list of monitors for disk array is displayed. Expand the Controllers monitor.
Displaying the HP EVA Controller
Detecting High Processor Utilization 34
5. Click for the first controller.
6. By default, the Processor Utilization attributes is displayed. Keep this selection and click
Generate Graph(s).
7. Add the graph to the view. Click . The following pop-up is displayed:
Adding a Graph to View
8. Create the view to which you want to add the graph to
Naming a View
9. In the View Title field, type the name of the view (High Processor Utilization) and click Add
View. The View created successfully message appears. Click Close.
10. The High Processor Utilization view is now created and available under the Views & Graphs drawer in the Navigation pane.
11. Repeat the procedure to add to this view the Processor Utilization attributes of all the controllers in your HP EVA disk array.
Once all graphs are stored in the view, it becomes easy to compare the controllers' respective
Processor Utilization and Transfer Byte Rates. Ensure that the Processor Utilization is lower than
80%. A processor utilization over 80% means that this controller is overloaded and that it constitutes a bottleneck for the storage system.
Verify the Transfer Byte Rate of your controllers. If the value of this attribute stays low – while the overall processor utilization is high – it indicates that the node is performing "non productive" tasks. It then may become critical to determine the source of activity that generates
35 Detecting High Processor Utilization
the high processor utilization.
Detecting Unbalanced Workload
Distribution on Controllers
A storage controller manages the flow of information between the server and the data, assigning two paths, in case one of the paths fails or is overloaded. For the best levels of performance and availability, every layer of technology must be balanced.
Comparing the Processor Utilization of Controllers
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 disk array of the controllers you need to compare the distribution workload.
Selecting a Device
4. The list of monitors for your device is displayed. Select the first of the two controllers for which you need to compare throughput.
Displaying the Monitors
Detecting High Processor Utilization 36
5. Click for the chosen controller.
6. By default, the Processor Utilization attribute is displayed. Keep this selection, and 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
In the View Title field, type the name of the view (Controllers Workload Balance) and click
Add View. The View created successfully message appears. Click Close.
8. The Controllers Workload Balance view is now created and available under the Views &
Graphs drawer in the Navigation pane.
9. Create a graph for the second controller and add it to the Controllers Workload Balance view.
You are then able to easily compare the values of both controllers to evaluate the workload distribution.
For example, if the throughput on one controller is significantly higher than the other one, it indicates that one on the controllers may constitute a bottleneck for the subsystem that could be alleviated by better sharing the load between the controllers.
It is recommended to pay close attention to which logical drive is handled by which controller, depending on the activity of this logical drives to be able to reallocates controller to drive I/O
37 Detecting Unbalanced Workload Distribution on
Controllers
activity so that neither controller is overloaded.
Diagnosing Fiber Performance Issues
Each external data port is represented by a Host Port Statistics instance. The attributes of this monitor type provide an accurate picture of the traffic on each fiber link. This will notably help administrators identify which port constitutes a bottleneck or diagnose 'multi-pathing' issues.
Creating a Fiber Port Performance Issues 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.
Displaying devices in a grid
3. In the Devices drawer, click the disk array for which you need to compare the fiber port performance.
4. The list of monitors for disk array is displayed. Expand the Host Port Statistics monitor.
Displaying the HP EVA Controller
Detecting Unbalanced Workload Distribution on
Controllers
38
5. Click for the chosen fiber port.
6. By default, the Read Byte Rate and Write Byte Rate attributes are displayed. Keep this selection and click Generate Graph(s).
7. Add the graph to the view. Click . The following pop-up is displayed:
Adding a Graph to View
8. Create the view to which you want to add the graph to
Naming a View
9. In the View Title field, type the name of the view (HP EVA Fiber Port Performance Issue) and click Add View. The View created successfully message appears. Click Close.
10. The HP EVA Fiber Port Performance Issue view is now created and available under the Views
& Graphs drawer in the Navigation pane.
Diagnosing a Bad Disk Layout
A non-optimal physical disk layout can cause one single physical disk to become the bottleneck of a SAN. To verify that the I/Os are well-balanced across all physical disks you can check the
Read Byte Rate and Write Byte Rate parameters of each physical disk and make sure they have similar average values.
39 Diagnosing Fiber Performance Issues
Verify Physical Disks Workload Distribution
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.
Displaying devices in a grid
3. In the Devices drawer, click the disk array for which you need to compare the physical disks layout.
4. The list of monitors for disk array is displayed. Expand the Physical Disk monitor.
Displaying the HP EVA Controller
Diagnosing a Bad Disk Layout 40
5. Click for the first physical disk.
6. By default, the Read Byte Rate and the Write Byte Rate attributes are displayed. Uncheck the
Read Byte Rate attribute but make sure that the Write Byte Rate attributes remains selected.
Selecting Attributes
7. Click Generate Graph(s).
41 Diagnosing a Bad Disk Layout
8. Add the graph to the view. Click . The following pop-up is displayed:
Adding a Graph to View
9. Create the view to which you want to add the graph to
Naming a View
10. In the View Title field, type the name of the view (Physical Disks Workload Distribution) and click Add View. The View created successfully message appears. Click Close.
11. The Physical Disks Workload Distribution view is now created and available under the Views
& Graphs drawer in the Navigation pane.
12. Repeat the procedure to add to this view the Write Byte Rate attributes of all the physical disks in your HP EVA disk array.
Diagnosing a Bad Disk Layout 42
Reference Guide
This chapter provides statistical information about resources, operating status, and performances managed by the BMC ProactiveNet Performance Management - HP EVA Storage Monitoring. 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
HP EVA Data Replication Tunnel
44
HP EVA Controllers
Attributes
Name Description Unit Default Alert
Conditions
Processor Utilization*
Status
Utilization of the processor.
Status of the controller.
Transfer Processor
Utilization*
Amount of processor time specifically spent on actual transfer operations.
For detailed information about KPI, see Managing Baselines and Key Performance Indicators.
Percentage
(%)
{0= OK; 1 =
Degraded;
2= Failed}
Warning ≥ 50 %
Alarm ≥ 90 %
(After 5 consecutive occurrences)
Warning = 1
Alarm = 2
Percentage
(%)
None
BMC
Proactive
Net
Attribute
Type
Statistic s
Availabil ity
Statistic s
* Attributes marked with an asterisk are used by default when visualizing the corresponding monitor instance in
BPPM
HP EVA Data Replication Tunnel
Attributes
Name
Copy In Byte Rate
Copy Out Byte Rate
Copy Retries Byte Rate
Description Unit
Rate at which data is copied to an array to populate the members of a DR group with data when an initial copy or full copy is requested.
Rate at which data is copied from an array to populate the members of a DR group with data when an initial copy or full copy is requested.
Copy actions that had to be retransmitted during the sample interval in response to a failed copy transaction.
Megaby tes per seconds
(MB/s)
Megaby tes per seconds
(MB/s)
Retries/ s
None
None
Default
Alert
Condition s
None
BMC
Proactive
Net
Attribute
Type
Statistic s
Statistic s
Statistic s
45
Name Description Unit
Free Command Resources Minimum number of free resources available for DR command operations.
Free Copy Resources Minimum number of free resources available for DR copy operations.
Free Write Resources Minimum number of free resources available for DR write operations.
Resourc es
Resourc es
Resourc es
Round Trip Delay Average time in milliseconds during the measurement interval for a signal (ping) to travel from source to destination and back again.
Millisec onds
(ms)
Write In Byte Rate*
Write Out Byte Rate*
Write Retries Byte Rate
Rate at which data is written to an array.
Rate at which data is written from an array.
Write actions that had to be retransmitted during the sample interval in response to a failed write transaction.
Megaby tes per seconds
(MB/s)
Megaby tes per seconds
(MB/s)
Retries/ s
None
None
None
None
None
None
None
Default
Alert
Condition s
BMC
Proactive
Net
Attribute
Type
Statistic s
Statistic s
Statistic s
Respons e Time
Statistic s
Statistic s
Statistic s
* Attributes marked with an asterisk are used by default when visualizing the corresponding monitor instance in
BPPM
HP EVA Host Connection
Attributes
Name
Busy Responses
Request Queue*
Description Unit Default
Alert
Condition s
BMC
Proactive
Net
Attribute
Type
Number of busy responses sent to a specific host during the sample interval. Busies represent a request from the controller to the host to cease I/O traffic until some internal job queue is reduced.
Respons es
Average number of outstanding requests from each of the corresponding host adapters.
Request s
None
None
Statistic s
Statistic s
HP EVA Data Replication Tunnel 46
* Attributes marked with an asterisk are used by default when visualizing the corresponding monitor instance in
BPPM
HP EVA Host Port
Attributes
Name
Read Byte Rate*
Read Request Rate
Read Response Time
Request Queue
Write Byte Rate*
Write Request Rate
Description Unit Default
Alert
Conditions
BMC
Proactive
Net
Attribute
Type
Statistics Megabytes read per second from the host port since the last collect.
Megaby tes per second s (MB/ s)
None
Read request rate from host-initiated requests that were sent through each host port for read commands.
Request s/s
Average response time for read operations.
Millise conds
(ms)
None
Warning
≥ 10 ms
(After 5 consecut ive occurren ces)
Statistics
Respons e Time
Average number of outstanding host requests against all virtual disks accessed through this EVA host port and over the sample interval. This metric includes all hostinitiated commands, including non-data transfer commands
Megabytes written per second to the host port since the last collect.
Alarm ≥
100
(After 2 consecut ive occurren ces)
Request s
None
This counter tabulates the write request rate of host initiated requests that were sent through each host port for write commands.
Megaby tes per second s (MB/ s)
None
Request s/s
None
Statistics
Statistics
Statistics
47 HP EVA Host Connection
Name
Write Response Time
Description Unit
Average response time for write operations.
Millise conds
(ms)
Default
Alert
Conditions
BMC
Proactive
Net
Attribute
Type
Warning
≥ 10 ms
Alarm ≥
100
(After 2 consecut ive occurren ces)
Respons e Time
* Attributes marked with an asterisk are used by default when visualizing the corresponding monitor instance in
BPPM
HP EVA KM
Attributes
Name
Collection Status
Description
Status of the collection. Errors reported by this parameter are only related to BMC ProactiveNet
Performance Management - HP EVA
Storage Monitoring itself.
Units
{0= OK; 1 =
Degraded;
2= Failed}
Default Alert
Conditions
BMC
ProactiveNe t Attribute
Type
Warning =
1
Alarm = 2
Collection
Status
HP EVA Node
Attributes
Name
Available Capacity
Description
Total capacity not consumed in the nodes.
Units Default
Alert
Conditions
BMC
Proactive
Net
Attribute
Type
Terab ytes
(TB)
None Statistics
HP EVA Host Port 48
Name
Byte Rate*
Port Count
Request Rate
Size
Subscribed Capacity
Description Units Default
Alert
Conditions
BMC
Proactive
Net
Attribute
Type
Statistics Total traffic on this node.
Mega bytes per secon ds
(MB/ s)
None
Number of fiber and Ethernet ports in the node.
This value can be used to know the number of required licenses for the monitoring system.
Number of requests handled by the node.
Ports None
Reque sts/s
None
Total size of the node (physical disk size).
Terab ytes
(TB)
None
Statistics
Statistics
Statistics
Number of terabytes reserved in the node. Terab ytes
(TB)
None Statistics
* Attributes marked with an asterisk are used by default when visualizing the corresponding monitor instance in
BPPM
HP EVA Physical Disk Group
Attributes
Name
Consumed Capacity
Consumed Capacity
Percentage
Protection Level
Read Byte Rate*
Description Units Default
Alert
Conditions
BMC
Proactive
Net
Attribute
Type
Number of bytes actually consumed in the physical disk group.
Percentage of the capacity that is actually consumed in the physical disk group.
Actual level of protection on the physical disk group.
Megabytes read per second from the physical disk group since the last collect.
Gigabyt es (GB)
None
Percent age (%)
None
Statistics
Statistics
Disks Alarm = 0 Statistics
Megab ytes per second s (MB/ s)
None Statistics
49 HP EVA Node
Name
Read Request Rate
Read Response Time
Request Queue
Response Time
Size
Write Byte Rate*
Write Request Rate
Write Response Time
Description Units Default
Alert
Conditions
BMC
Proactive
Net
Attribute
Type
Statistics Number of requests that are read per seconds.
Average number of requests, both read and write, in process from the physical disk group.
Reques ts/s
Average time to complete the read requests.
Millise conds
(ms)
Reques ts
Average response time for all operations.
Overall physical size of the disk group.
Megabytes written per second from the physical disk group since the last collect.
None
None
None
Millise conds
(ms)
None
Gigabyt es (GB)
None
Megab ytes per second s (MB/ s)
None
Respons e Time
Statistics
Respons e Time
Statistics
Statistics
Rate at which write requests are sent to the disk drive from each controller
Reques ts/s
Average response time for write operations.
Millise conds
(ms)
None
None
Statistics
Respons e Time
* Attributes marked with an asterisk are used by default when visualizing the corresponding monitor instance in
BPPM
HP EVA Physical Disk
Attributes
Name
Read Byte Rate*
Description Units
Megabytes read per second from the physical disks since the last collect.
Megab ytes per second s (MB/ s)
Default
Alert
Conditions
BMC
Proactive
Net
Attribute
Type
None Statistics
HP EVA Physical Disk Group 50
Name
Read Request Rate
Read Response Time
Request Queue
Response Time
Write Byte Rate*
Write Request Rate
Write Response Time
Description Units Default
Alert
Conditions
BMC
Proactive
Net
Attribute
Type
None Statistics Number of requests that are read per second. Reques ts/s
Average time for a physical disk to complete a read request from each controller.
Millise conds
(ms)
Average number of requests, both read and write, in process from each controller.
Average response time for all operations.
Reques ts
Millise conds
(ms)
Megabytes written per second from the physical disks since the last collect.
Megab ytes per second s (MB/ s)
Rate at which write requests are sent to the disk drive from each controller.
Reques ts/s
Average response time for write operations.
Millise conds
(ms)
None
None
None
None
None
None
Response
Time
Statistics
Response
Time
Statistics
Statistics
Response
Time
* Attributes marked with an asterisk are used by default when visualizing the corresponding monitor instance in
BPPM
HP EVA Port Status
Attributes
Name Description Unit Default
Alert
Conditions
BMC
Proactive
Net
Attribute
Type
Statistics Abnormal EOF Number of abnormal EOF encountered on this port.
Bad Characters Received Number of bad characters received by this port.
Bad CRC Number of bad CRC encountered on this port.
Errors
Charac ters
Errors
Warning
≥ 1
Warning
≥ 1
Warning
≥ 1
Discarded Frames Number of discarded frames by this port.
Frames Warning
≥ 1
Statistics
Statistics
Statistics
51 HP EVA Physical Disk
Name
Link Failures
Loss Of Signal
Loss Of Synch
Protocol Errors
Status*
Description
Number of link failures encountered by this port.
Number of losses of signal encountered by this port.
Number of losses of synchronization encountered on this port.
Number of protocol errors encountered on this port.
Overall status of this port.
Unit Default
Alert
Conditions
BMC
Proactive
Net
Attribute
Type
Statistics Failure s
Warning
≥ 1
Losses Warning
≥ 1
Losses Warning
≥ 1
Errors Warning
≥ 1
{0=
Plugge d;
1=Unpl ugged}
Warning
= 1
Statistics
Statistics
Statistics
Availabil ity
* Attributes marked with an asterisk are used by default when visualizing the corresponding monitor instance in
BPPM
HP EVA Virtual Disk Group
Attributes
Name
Cache Hit Ratio
Cache Read Byte Rate
Description
Percentage of requests that are successfully served by a cache.
Amount of data read off the cache.
Cache Read Request Rate Amount of read requests processed by the
Cache Read Response
Time virtual disk group.
Average time taken to complete read operations that are served by the cache.
Units Default
Alert
Conditions
BMC
Proactive
Net
Attribute
Type
Statistics Percent age (%)
None
Megab ytes per second s (MB/ s)
None
Reques ts/s
Millise conds
(ms)
None
None
Statistics
Statistics
Response
Time
HP EVA Port Status 52
Name Description Units Default
Alert
Conditions
BMC
Proactive
Net
Attribute
Type
Statistics Disk Read Byte Rate
Disk Read Request Rate
Mirror Byte Rate
Prefetch Byte Rate
Total Read Byte Rate*
Write Byte Rate*
Write Request Rate
Write Response Time*
Amount of data read off the virtual disk group.
Amount of read requests processed by the virtual disk group.
Disk Read Response Time Average time taken to complete read operations that are served by the virtual disk
Flush Byte Rate group.
Amount of data eventually written to the virtual disk group.
Mirroring traffic.
Amount of data that is proactively loaded into the cache.
Total amount of data read from the virtual disk group (CacheReadByteRate +
DiskReadByteRate).
Megab ytes per second s (MB/ s)
Megab ytes per second s (MB/ s)
Megab ytes per second s (MB/ s)
Megab ytes per second s (MB/ s)
Megab ytes per second s (MB/ s)
None
Reques ts/s
Millise conds
(ms)
None
None
None
None
None
None
Megabytes written per second to the virtual disk group since the last collect.
Megab ytes per second s (MB/ s)
None
Amount of write request processed by the virtual disk group.
Reques ts/s
Average response time for write operations.
Millise conds
(ms)
None
None
Statistics
Response
Time
Statistics
Statistics
Statistics
Statistics
Statistics
Statistics
Response
Time
53 HP EVA Virtual Disk Group
* Attributes marked with an asterisk are used by default when visualizing the corresponding monitor instance in
BPPM
HP EVA Virtual Disk
Attributes
Name
Cache Hit Ratio
Cache Read Byte Rate
Cache Read Request Rate
Cache Read Response Time
Disk Read Byte Rate
Disk Read Request Rate
Disk Read Response Time
Description Units Default Alert
Conditions
BMC
ProactiveNet
Attribute
Type
Statistics Percentage of requests that are successfully served by a cache.
Amount of data read off the cache.
Amount of read requests processed by the virtual disk.
Average time taken to complete read operations that are served by the disk.
Perc enta ge
(%)
Meg abyt es per seco nds
(MB/ s)
None
None
Requ ests/ s
None
Average time taken to complete read operations that are served by the cache.
Milli seco nds
(ms)
None
Amount of data read off the disk. Meg abyt es per seco nds
(MB/ s)
None
Amount of read requests processed by the virtual disks.
Requ ests/ s
None
Milli seco nds
(ms)
None
Statistics
Statistics
Response
Time
Statistics
Statistics
Response
Time
HP EVA Virtual Disk Group 54
Name
Flush Byte Rate
Mirror Byte Rate
Prefetch Byte Rate
Time Since Last Activity
Total Read Byte Rate*
Write Byte Rate*
Write Request Rate
Description Units Default Alert
Conditions
BMC
ProactiveNet
Attribute
Type
Statistics Amount of data eventually written to the disk.
Mirroring traffic.
Amount of data that is proactively loaded into the cache.
Number of days since any activity occurred on the virtual disk.
Total amount of data read from the virtual disk
(CacheReadByteRate +
DiskReadByteRate).
Meg abyt es per seco nds
(MB/ s)
None
Megabytes written per second to the virtual disk since the last collect.
Meg abyt es per seco nds
(MB/ s)
None
Amount of write request processed by the virtual disk.
Requ ests/ s
None
Meg abyt es per seco nds
(MB/ s)
None
Meg abyt es per seco nds
(MB/ s)
None
Meg abyt es per seco nds
(MB/ s)
None
Days None
Statistics
Statistics
Statistics
Statistics
Statistics
Statistics
55 HP EVA Virtual Disk
Name
Write Response Time
Description
Average response time for write operations.
Units Default Alert
Conditions
Milli seco nds
(ms)
None
BMC
ProactiveNet
Attribute
Type
Response
Time
* Attributes marked with an asterisk are used by default when visualizing the corresponding monitor instance in
BPPM
HP EVA Virtual Disk 56
Index
- A -
Attributes
Abnormal EOF 51
Available Capacity 48
Bad Characters Received 51
Bad CRC 51
Busy Responses 46
Byte Rate 48
Cache Hit Ratio 52, 54
Cache Read Byte Rate 52, 54
Cache Read Request Rate 52, 54
Cache Read Response Time 52, 54
Collection Status 48
Consumed Capacity 49
Consumed Capacity Percentage 49
Copy In Byte Rate 45
Copy Out Byte Rate 45
Copy Retries Byte Rate 45
Discarded Frames 51
Disk Read Byte Rate 52, 54
Disk Read Request Rate 52, 54
Disk Read Response Time 52, 54
Flush Byte Rate 52, 54
Free Command Resources 45
Free Copy Resources 45
Free Write Resources 45
Link Failures 51
Loss Of Signal 51
Loss Of Synch 51
Mirror Byte Rate 52, 54
Port Count 48
Prefetch Byte Rate 52, 54
Processor Utilization 45
Protection Level 49
Protocol Errors 51
Read Byte Rate 47, 49, 50
Read Request Rate 47, 49, 50
Read Response Time 47, 49, 50
Reference Guide 44
Request Queue 46, 47, 49, 50
Request Rate 48
Response Time 49, 50
57
Round Trip Delay 45
Size 48, 49
Status 45, 51
Subscribed Capacity 48
Time Since Last Activity 54
Total Read Byte Rate 52, 54
Transfer Processor Utilization 45
Write Byte Rate 47, 49, 50, 52, 54
Write In Byte Rate 45
Write Out Byte Rate 45
Write Request Rate 47, 49, 50, 52, 54
Write Response Time 47, 49, 50, 52, 54
Write Retries Byte Rate 45
- B -
Bad Disk Layout 39
Business Value 10
- C -
Component Installation package creating 15 downloading 16
Configuring monitor settings 22
Configuring Monitor Thresholds 31
Configuring thresholds 31
- D -
Debug Mode enabling 26
Deleting a Threshold Configuration 32
Disable
Virtual Disks Monitoring 22
Discovery Interval 22
Downloading 16
- E -
Editing a Threshold Configuration 32
Exclude Volumes 22
- F -
Features 9
Fiber Performance Issues 38
- G -
Goals 9
- H -
High Processor Utilization 34
HP Command View EVA 12
HP StorageWorks 12
- I -
Importing the Monitoring Solution 14
Installation configuring 20
Installing 16
Installing the Monitoring Solution 14
- J -
Java 12
- K -
Keep Only Volumes 22
Key Concepts 9
- M -
Managing Unknown Status 27
Monitor Settings configuring 22
Monitor thresholds 31
Monitor Types
HP EVA Controllers 45
HP EVA Data Replication Tunnel 45
HP EVA Host Connection 46
HP EVA Host Port 47
HP EVA KM 48
HP EVA Node 48
HP EVA Physical Disk 50
HP EVA Physical Disk Group 49
HP EVA Port Status 51
HP EVA Virtual Disk 54
HP EVA Virtual Disk Group 52
Reference Guide 44
- P -
Package 15, 16
Policies
Manage 21
Polling Interval 22
Prerequisites 12
- R -
Reference Guide
Attributes 44
Monitor types 44
- S -
SSSU.EXE 12
Supported Platforms 10
- T -
Thresholds 31
- U -
Unbalanced Workload Distribution 36
Unknown Status 27
- V -
Volumes exclude 22 keep only 22
58
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.
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 WA RE
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.
Download
Public link updated
The public link to your chat has been updated. You may view and manage your chat links after registration here.
Document public link
Advertisement
Key features
Centralized monitoring of HP EVA storage
Detailed system metrics
Performance bottleneck identification
Disk space consumption management
Unused disk capacity detection
Traffic and I/O analysis
Historical performance data
Problem warnings
Integration with BMC ProactiveNet Performance Management
Frequently asked questions
The solution supports the entire HP StorageWorks Enterprise Virtual Array Family (EVA).
You need PATROL Agent (version 3.8 or higher), PATROL Console, HP StorageWorks v9.1 or higher, Java 1.6 or higher, and HP Command View EVA (with the latest firmware and StorageWorks Command View 9.1 or higher installed).
You can configure general settings by creating a policy which specifies actions to be taken when a specific condition on the PATROL Agent is fulfilled. This includes monitor configuration, threshold creation, baselines, and server-side thresholds for alerts.
You can configure monitor types for compatible BMC PATROL monitoring solutions located in the Central Monitoring Repository. For specific monitor types, refer to the monitor documentation.
You can assign tags to PATROL Agents by entering the tagName:tagDescription format in the Agent Properties section. Multiple tags can be separated by commas.
