BMC ProactiveNet Performance Management - IBM SVC …€¦ · · 2015-04-20BMC ProactiveNet...
Transcript of BMC ProactiveNet Performance Management - IBM SVC …€¦ · · 2015-04-20BMC ProactiveNet...
BMC ProactiveNet PerformanceManagement - IBM SVC StorageMonitoring
STORAGE MONITORING
USER DOCUMENTATION
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 canobtain information about the company, its products, corporate offices, special events, and careeropportunities.
United States and Canada
Address BMC Software, Inc.2101 CityWest Blvd. Houston TX77042-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 areregistered 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 andconfidential. Your use of this information is subject to the terms and conditions of the applicableEnd User License Agreement for the product and the proprietary and restricted rights noticesincluded in this documentation.
Restricted Rights Legend
U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVEDUNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any dataand computer software by the U.S. Government is subject to restrictions, as applicable, set forthin FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, andDFARS 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 thisaddress.
2
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Customer Support
You can obtain technical support by using the Support page on the BMC Software Web site or bycontacting Customer Support by telephone or e-mail. To expedite your inquiry, please see"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 athttp://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 centerfor assistance. To find telephone and email contact information for the BMC Software supportcenter that services your location, refer to the Contact Customer Support section of the Supportpage 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 CustomerSupport can begin working on your problem immediately:
3
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
4
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Table of Contents.....................................................................................................................................................................................12User Goals and Features
.....................................................................................................................................................................................13Product at a Glance
.....................................................................................................................................................................................14Supported Platforms
.....................................................................................................................................................................................16Importing the Monitoring Solution into Central Administration
.....................................................................................................................................................................................17Creating the Installation Package
.....................................................................................................................................................................................18Downloading the Installation Package
.....................................................................................................................................................................................18Installing the Package
.....................................................................................................................................................................................22Adding Tags to PATROL Agents
.....................................................................................................................................................................................24Configuring Monitor Settings
.......................................................................................................................................................................................28Enabling the Debug Mode
.......................................................................................................................................................................................30Configuring the Discovery Interval
.......................................................................................................................................................................................32Setting Advanced Configuration Variables
.......................................................................................................................................................................................33Disabling Volumes Monitoring
.......................................................................................................................................................................................35Filtering Volumes to Monitor
.......................................................................................................................................................................................37Scheduling Automatic Reports
.......................................................................................................................................................................................38Configuring Thresholds
......................................................................................................................................................................38Configuring Monitor Thresholds
......................................................................................................................................................................39Editing a Threshold Configuration
......................................................................................................................................................................40Deleting a Threshold Configuration
.......................................................................................................................................................................................40Managing Monitoring Policies
......................................................................................................................................................................40Editing an existing monitoring policy
......................................................................................................................................................................41Deleting a monitoring policy
......................................................................................................................................................................41Enabling/disabling a monitoring policy
.....................................................................................................................................................................................44Identifying a Node Overload
.....................................................................................................................................................................................47Diagnosing Slow Volumes
.....................................................................................................................................................................................50Identifying Busiest Volumes
.....................................................................................................................................................................................53Reporting Disk Space Consumption
.....................................................................................................................................................................................56Viewing the Overall Activity of a Storage System
.....................................................................................................................................................................................60Monitor Types and Attributes
.......................................................................................................................................................................................61IBM SVC FC Port
.......................................................................................................................................................................................63IBM SVC iSCSI Port
.......................................................................................................................................................................................65IBM SVC MDisk
5
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
.......................................................................................................................................................................................66IBM SVC Node
.......................................................................................................................................................................................68IBM SVC Pool
.......................................................................................................................................................................................69IBM SVC SAN Volume Controller
.......................................................................................................................................................................................70IBM SVC Volume
.......................................................................................................................................................................................72IBM SVC Volume Mirror
.......................................................................................................................................................................................73IBM SVC Storage System
.......................................................................................................................................................................................74Configuration Variables
.......................................................................................................................................................................................77Managing Baselines and Key Performance Indicators
Release Notes for v1.2.00
7
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
What's NewThe 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 monitortype 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 considersthe nodes that have access to the internal managed disks of IBM Storwize V7000 systems.
Fixed IssuesThe 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 getsaturated which prevented the monitoring solution from collecting the statistics parametersas frequently as excepted. Now in such a case, the monitoring solution will follow the IBM'srecommendations by collecting the statistics parameters every 15 minutes to avoid serversaturation.
Support Information
9
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
This section contains information about how to contact Customer Support and the levels ofsupport 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 productdocuments 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 Statesor Canada, contact Customer Support at 800 537 1813. Outside the United States or Canada,contact your local BMC office or agent.
Overview
11
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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 SVCStorage Monitoring, may also be made as BPPM IBM SVC Storage Monitoring.
12
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
User Goals and FeaturesBMC ProactiveNet Performance Management - IBM SVC Storage Monitoring product allows youto view, monitor, and manage your entire IBM SVC environment by viewing the current andhistorical information through a centralized console. You can view detailed system metrics on allparts of your environment.
BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring enables you tomanage the following in your environment:
Nodes: availability, processor utilization, response time and traffic (read and write, inoperations/s and MB/s)
FC ports: Link status, speed and errors; Traffic (read and write, in MB/s ; from hosts, storagesystems, same or other clusters)
iSCI ports: Link status and speed; Traffic (read and write, in MB/s; from hosts, storagesystems, 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 (readand 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).
13 User Goals and Features
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Product at a GlanceBMC ProactiveNet Performance Management - IBM SVC Storage Monitoring provides current andhistorical information through a centralized console so you can easily view and manage yourentire IBM SVC environment. The product collects and brings critical performance data and usefulmetrics into the BMC ProactiveNet Performance Management environment and enables SANAdministrators 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.
14Product at a Glance
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Supported PlatformsBMC 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.
Installing the Monitoring Solution
16
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
The installation can be handled from A to Z from BMC ProactiveNet Central MonitoringAdministration. Once the latest version of the solution has been loaded into BMC ProactiveNetCentral Monitoring Administration, administrators can create all the installation packagesrequired for their different operating systems and platforms and save them for later use in theMonitoring Installation Packages list. These packages can then be deployed to multiplecomputers. Administrators just have to connect to BMC ProactiveNet Central MonitoringAdministration from the server where they want to install the package, download it and launchthe 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 Solutioninto Central AdministrationThe BMC ProactiveNet Central Monitoring Repository includes the current versions of the BMCPATROL Agent and BMC PATROL Monitoring Solutions that you can use with BMC ProactiveNet. Ifthe version available in the Repository does not correspond to the latest one, you will have tomanually 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 fromwhich 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.
17 Importing the Monitoring Solution into CentralAdministration
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Creating the Installation PackageThe installation package to deploy to managed systems can be created directly from BMCProactiveNet 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. Thecomponents available in the repository for the selected operating system and platform aredisplayed.
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 youchose 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 InstallationPackage 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 inthe 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.
18Creating the Installation Package
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Downloading the Installation PackageYou can download an installation package and install the components on one or more hosts. Theinstallation runs silently with the information entered during package creation.
RecommendationIf you defined the BMC ProactiveNet Integration Service variable for PATROL Agents in theinstallation package, ensure the agents are started in phases. Do not start newly deployedagents all at once. Start and configure monitoring for the agents in planned phases to reducethe performance impact on the Integration Service nodes and on the BMC ProactiveNetServer associated with the automatic workflow process.
1. Log on to BMC ProactiveNet Central Monitoring Administration from the computer on whichthe 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 Package1. 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 isextracted 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, theagent sends a configuration request by passing its tags to BMC ProactiveNet Central MonitoringAdministration, via the Integration Service. Central Monitoring Administration evaluates policiesthat match the tags, determines the final configuration to be applied, and sends theconfiguration information back to the agent. Monitoring is based on the configurationinformation received by the agent.
If no policy matches the tags associated with the agent, the agent does not receive configurationinformation. The agent does not begin monitoring until a matching policy is created.
Integrating the MonitoringSolution
20
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Depending on the version of BMC ProactiveNet Performance Management used, integrationsteps may need to be performed.
BMC ProactiveNet Performance Management 8.5, 8.6 or 9.0To integrate BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring intoBMC ProactiveNet Performance Management 8.5, 8.6 or 9.0, you need to create a specificadapter. For more information, please refer to Integrating the Sentry Software's KMs into BMCProactiveNet Performance Management (BPPM).
BMC ProactiveNet Performance Management 9.5
No specific integration steps need to be performed.
Configuring After Installation
22
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
To configure BMC ProactiveNet Performance Management - IBM SVC Storage Monitoring, youneed 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 havepreviously added.
Adding Tags to PATROL AgentsTags must be set for all your PATROL Agents when creating a policy. If you have not alreadyassigned tags in the deployable install packages you created, you can still manually add them toyour policy.
1. In the Navigation pane of Central Monitoring Administration, click Policies and expand theMonitoring 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 theMonitoring Policy Configuration dialog box.
4. Check the Agent Configuration box.
5. Click the Agent Configuration link to go straight to the Agent Configuration page.
23 Adding Tags to PATROL Agents
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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 thename 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 PATROLAgents based on the Agent Tag property that you have previously added.
24Adding Tags to PATROL Agents
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Configuring Monitor SettingsWhen you create or edit a policy, you can add and configure monitor types. The Add MonitorTypes dialog box presents configuration fields for compatible BMC PATROL monitoring solutionsthat are located in the Central Monitoring Repository. For a list of monitoring solutions that youcan configure through Central Monitoring Administration, see the Monitoring solutionsconf igurable through Central Monitoring Administration chapter in the BPPM onlinedocumentation.
For configuration details for a specific monitor type, see the monitor documentation. Toconfigure custom monitoring solutions through Central Monitoring Administration, ensure thesolution is structured correctly; for details, see the Building a PATROL Knowledge ModuleDevelopers Guide on BMC Support website.
25 Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
To configure the Monitor Type settings using the Add Monitor Typesdialog box1. 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:
26Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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 OpenSSHPrivate Key File or, a username and a password.
Username: The admin username is required to connect to the SAN Volume ControllerCluster
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 SSHPrivate Key File might be required to connect to a Storwize v7000 system type. Open SSHPrivate Key File is mandatory to connect to a SAN Volume Controller.The SSH Key file must
27 Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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, ifany.
9. Click Add to List to save the new connection to the IBM SVC Cluster.
28Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Enabling the Debug ModeWhen you encounter an issue and wish to report it to Sentry Software, you will be asked toenable the Debug Mode and provide the debug output to the Sentry Software support team.
To enable the debug mode1. 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 debugmode, and click Edit.
4. Click the Monitor Configuration tab.
5. Click the Advanced button.
Enabling the Debug Mode
29 Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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 loggingdebug 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 Timemust be properly set to a date and time in the future.
30Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Configuring the Discovery IntervalBMC ProactiveNet Performance Management - IBM SVC Storage Monitoring periodicallyperforms discoveries to detect new components in your monitored environment. By default, thesolution runs a discovery every hour, but you can customize this interval to match your specificneeds.
31 Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
To configure the discovery interval1. 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 thediscovery 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 appropriatenumber of minutes.
7. Click Close to save your settings.
32Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Setting Advanced Configuration VariablesAdvanced configuration variables are used to manually set variables that are normally not availablethrough the standard interface.These variables should only be set when instructed so by Sentry Software Support.
To configure a variable1. 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.
33 Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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 MonitoringDiscovering and collecting volumes metrics are resource-intensive actions that can create extraworkload on the PATROL Agent and the targeted system. To limit the number of instancescreated and therefore reduce the system resource consumption, administrators can disable themonitoring of all the volumes of a system.
34Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
To filter volumes to monitor1. 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.
35 Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Filtering Volumes to MonitorBy default, the solution discovers and monitors all volumes in the storage systems. There may be a verylarge number of volumes to monitor and this may represent an important workload to the agents andthe 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 fromthe monitoring or keep only certain volumes.
36Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
To filter volumes to monitor1. 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 toexclude 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 Volumesfield, only the volumes that match with the specified regular expression will be monitored
7. Click Close to save your settings.
37 Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Scheduling Automatic ReportsBMC ProactiveNet Performance Management - IBM SVC Storage Monitoring can automaticallyproduce text reports about the monitored storage systems.
To schedule automatic reports1. 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 thescheduling 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 storagesystems
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-hostsmapping table.
9. Click Close to save your settings.
The history retention period can be set f rom the PATROL Console or f rom the PATROL Agent using aconf iguration variable. The default collection (retention) period is one day. Whenever a stored parametervalue exceeds its retention period, it is automatically deleted from the parameter history f ile. Refer to BMCdocumentation for details.
38Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Configuring ThresholdsWhen 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 ProactiveNetmonitors that are configured through Central Monitoring Administration.
For details about baselines and Key Performance Indicators (KPI), see BMC ProactiveNet CentralMonitoring Administration or BMC ProactiveNet documentation or refer to the ManagingBaselines 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. Thresholdscannot be applied to monitors that are not configured through Central MonitoringAdministration. If you have not done so already, please refer to the section Configuring MonitorSettings.
Recommended Thresholds
Thresholds define acceptable high and/or low values for the data collected. Thresholds can becreated as part of a policy that can be applied to multiple monitor types on multiple BMC PATROLAgents. The Ref erence Guide provides a list of monitor types with their respective attributes and, whenmeaningful, a recommended threshold.
Do not set server thresholds for availability or Boolean oriented parameters or any other parameters thatwill have events generated for them by the PATROL Agents.
Configuring Monitor ThresholdsTo 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 configurethresholds:
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 .
39 Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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 beapplied. 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 Configurationpage.
13. Click Finish.
New threshold configurations are pushed to BMC PATROL Agents with matching CentralMonitoring Configuration tags.
Editing a Threshold ConfigurationTo 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 editthresholds:
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 CentralMonitoring Configuration tags.
40Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Deleting a Threshold ConfigurationTo 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 editthresholds:
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 thepolicy.
Deleted threshold configurations are removed from BMC PATROL Agents with matching CentralMonitoring Configuration tags.
Managing Monitoring PoliciesA monitoring policy specifies a set of actions to be taken when a specific condition on thePATROL Agent is fulfilled. First and foremost, actions include monitor configuration. Once amonitor is configured, policies can also specify threshold creation and the setting of baselines. Apolicy can also include intelligent server-side thresholds so that IT administrators canimmediately 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 policyAn 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 .
41 Configuring Monitor Settings
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
4. Select one or several Optional Configuration options.
5. Click Next to go through the Monitoring Policy Configuration wizard to edit the monitoringpolicy settings.
6. Click Finish.
The updated monitoring policy is then deployed to the PATROL agents.
Deleting a monitoring policyDeleting a monitoring policy may have deep consequences in a production environment. Beforedeleting a policy, it is recommended to create a new policy with a lower precedence number thatwill override the older policy. Once this new policy has been thoroughly tested, validated andenabled 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. Devicesremain in the User Groups to which they have been added.
Enabling/disabling a monitoring policyFor maintenance and troubleshooting it can be useful to enable or disable policies. When apolicy is disabled, the policy and its associations remain intact, but the policy configuration is notapplied 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 havebeen tested and validated for production.
to disable your policy.
Monitoring your StorageEnvironment
43
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Monitoring IBM SVC storage systems with BMC ProactiveNet Performance Management - IBMSVC Storage Monitoring is very simple. Once the monitoring solution is properly installed andconfigured, BPPM IBM SVC Storage Monitoring automatically detects all the various IBM SVCstorage features and components and displays them in the BMC ProactiveNet OperationsConsole.
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
44
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Identifying a Node OverloadTo visualize the activity of a node, use the Processor Utilization attribute of the Node monitor. Awarning is issued when the processor utilization goes too high, which means that the nodescannot keep up with the load on the storage system. It is then important to identify what isoverloading the nodes.
The Received Response Time and Sent Response Time attributes of the Node monitor representsthe average time it took the node to process the receive and send requests of the hosts. Thehigher the response time goes, the slower I/Os the servers will get. By default, the solutiontriggers 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:
45 Identifying a Node Overload
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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 createdsuccessfully message appears. Click Close.
8. The Node Overload view is now created and available under the Views & Graphs drawer inthe Navigation pane.
9. Resume the procedure to add to the view the Processor Utilization attributes of all the nodesthat 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
46Identifying a Node Overload
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
4. Click for one of the listed nodes.
5. By default, the Processor Utilization attribute is displayed. We will now display the ReceivedResponse 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 .The following pop-up is displayed:
Adding a Graph to View
From the Add to View list, select Node Overload and click Add to View. The Graph addedsuccessfully message appears. Click Close.
7. Resume the procedure to add to the view the Received Response Time and Sent ResponseTime attributes of all the nodes that compose the IBM SVC storage system.
47 Identifying a Node Overload
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Diagnosing Slow VolumesIf a system administrator complains that his servers are experiencing slow I/Os performance andthat it is caused by the SAN, you may want to verify the actual response time of the volumes theserver is relying on.
The Response Time attributes (Read Response Time and Write Response Time) of the volumemonitor type represent the time it took to complete the read and write operations on thevolume during the collection interval. Typically, the average response time is below 10milliseconds. You may also want to compare these values to the response time of the othervolumes to see whether one server is really getting worse I/O performance than another.
Creating the Slow Volumes View1. 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, wewill only display the Read Response Time and the Write Response Time attributes. Theprocedure 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.
48Diagnosing Slow Volumes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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
49 Diagnosing Slow Volumes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
In the View Title field, type Slow Volumes and click Add View. The View createdsuccessfully message appears. Click Close.
8. The Slow Volumes view is now created and available under the Views & Graphs drawer inthe Navigation pane.
9. Repeat the procedure to add to the view the Response Time attributes of all the volumesthat compose the IBM SVC storage system.
50Diagnosing Slow Volumes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Identifying Busiest VolumesTo identify the volumes that generate the most traffic, you can create a specific view that willdisplay the Read Byte Rate and Write Byte Rate attributes of the Volumes Monitor.
Creating the Busiest Volumes View1. 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, wewill only display the Read Byte Rate and the Write Byte Rate attributes. The procedure is asfollows:
Click the Attributes & Indicators tab.
Uncheck the Consumed Capacity Percentage box.
Check the Read Byte Rate and Write Byte Rate boxes.
51 Identifying Busiest Volumes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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.
52Identifying Busiest Volumes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Adding a Graph to View - Step 2
In the View Title field, type Busiest Volumes and click Add View. The View createdsuccessfully message appears. Click Close.
8. The Busiest Volumes view is now created and available under the Views & Graphs drawer inthe Navigation pane.
9. Resume the procedure if you want to add to the view the Read Byte Rate and Write ByteRate attributes of the volumes you are interested in.
53 Identifying Busiest Volumes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Reporting Disk Space ConsumptionMaking sure that a storage unit has enough remaining disk space available is critical for severalreasons:
SAN administrators want to make sure to be able to provision disk space for new serverswhen requested, as quickly as possible.
The storage system itself may need additional disk space for specific features to workproperly, like automatic snapshots, mirroring, etc.
If thin provisioning is used, the remaining disk space becomes dramatically critical since theinability to allocate additional space to a volume when requested by the subscriber host willlead to catastrophic data loss and corruption.
The disk space used is permanently monitored for each pool. The Subscribed Capacity attributeof the Pool monitor type represents the amount of disk space that has been made available tothe subscriber hosts, or in other words, the amount of disk space that is seen by the serversconnected to the storage unit.
The Consumed Capacity attribute of the Pool monitor type represents the actual space usage inthe pool. For “thin” pools (when thin provisioning is enabled on the storage system), this value isnormally lower than the Subscribed Capacity, as it is the main purpose of thin provisioning. Fortraditional pools, the Consumed Capacity attribute has the same value as the Subscribed Capacityattribute, 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 poolnearing 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 bea normal situation.
Creating the Disk Space Consumption View1. 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.
54Reporting Disk Space Consumption
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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 usecase, we will display the Subscribed Capacity, Consumed Capacity and Consumed CapacityPercentage 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 Percentageboxes.
Selecting Attributes
Click Generate Graph(s)
7. Add the graph to the view:
Click . The following pop-up is displayed:
55 Reporting Disk Space Consumption
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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 createdsuccessfully message appears. Click Close.
8. The Disk Space Consumption view is now created and available under the Views & Graphsdrawer in the Navigation pane.
9. Repeat the procedure if you want to add to the view the Subscribed Capacity, ConsumedCapacity and Consumed Capacity Percentage attributes of the next pool you are interestedin.
56Reporting Disk Space Consumption
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Viewing the Overall Activity of aStorage SystemIn order to visualize the activity of a storage system, use the Read Byte Rate and Write Byte Rateattributes of the Storage System monitor. These attributes represent the overall traffic inmegabytes per second for each monitored system.
Creating the Overall Activity of a Storage System View1. 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:
57 Viewing the Overall Activity of a Storage System
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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. TheView 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.
58Viewing the Overall Activity of a Storage System
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Reference Guide
60Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Monitor Types and AttributesIntroduction
This chapter lists all the monitor types and attributes provided by BMC ProactiveNetPerformance Management - IBM SVC Storage Monitoring to monitor your systems.
Please note that depending on the type of managed systems, some attributes may not beavailable.
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 thereforeautomatically included in the base lining calculation. To learn more about auto baselining andKPIs, 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 calculationprocess are respectively identified by the following icon: KPI
61 Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
IBM SVC FC PortAttributes
Name Description Units DefaultAlertConditions
BMC ProactiveNetAttribute Type
Bad CRC Indicates the number of CRC that arenot valid.
Errors Warningif ≥1
Statistics
BandwidthUtilization
Percentage used of the availablebandwidth.
Percentage(%)
None Statistics
InvalidTransmissionWords
Indicates the number of transmissionword counts that are not valid.
Words Warningif ≥1
Statistics
Link Failures Indicates a link failure count. Failures Warningif ≥1
Statistics
Link Speed Indicates the FC interface link speed. Megabytesperseconds(MB/s)
None Statistics
Loss Of Signal Indicates the loss-of-signal count. Losses Warningif ≥1
Statistics
Loss Of Synch Indicates the loss-of-synchronizationcount.
Losses Warningif ≥1
Statistics
Protocol Errors Indicates the protocol error count. Errors Warningif ≥1
Statistics
Received ByteRate
Indicates the number of bytes sent fromhost, disk controllers, and other nodesin the same and other clusters.
Megabytesperseconds(MB/s)
None Statistics
Received FromHosts WriteRate
Indicates the number of megabytesreceived from hosts per second.
Megabytesperseconds(MB/s)
None Statistics
Received FromOther ClusterByte Rate
Indicates the number of megabytesreceived from other nodes.
Megabytesperseconds(MB/s)
None Statistics
Received FromSame ClusterByte Rate
Indicates the number of megabytesreceived from the same cluster.
Megabytesperseconds(MB/s)
None Statistics
Received FromStorage ByteRate
Indicates the number of megabytesreceived from storage.
Megabytesperseconds(MB/s)
None Statistics
62Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Name Description Units DefaultAlertConditions
BMC ProactiveNetAttribute Type
Sent Byte Rate Indicates the number of megabytes sentto host, disk controllers, and othernodes in the same and other clusters.
Megabytesperseconds(MB/s)
None Statistics
Sent To HostsByte Rate
Indicates the number of megabytestransmitted to host.
Megabytesperseconds(MB/s)
None Statistics
Sent To OtherCluster Byte Rate
Indicates the number of megabytestransmitted to other nodes in the otherclusters.
Megabytesperseconds(MB/s)
None Statistics
Sent To SameCluster Byte Rate
Indicates the number of megabytestransmitted to other nodes in the samecluster.
Megabytesperseconds(MB/s)
None Statistics
Sent To StorageByte Rate
Indicates the number of megabytestransmitted to storage.
Megabytesperseconds(MB/s)
None Statistics
Status Indicates the status of the FC port. {0= OK; 1 =Degraded;2= Failed}
None Availability
Zero Buffer TimePercentage
Percentage of time where the port wasunable to send data due to lack ofbuffer credit in the switch.
Percentage(%)
None Statistics
63 Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
IBM SVC iSCSI PortAttributes
Name Description Units Default AlertConditions
BMCProactiveNetAttributeType
Status Indicates thestatus of the iSCSIport.
{0= OK; 1 =Degraded;2= Failed}
1 =Warning2 = Alarm
Availability
Link Speed Indicates the iSCSIinterface linkspeed.
Megabytesperseconds(MB/s)
None Statistics
Bandwidth Utilization Percentage used ofthe availablebandwidth.
Percentage(%)
None Statistics
Received Byte Rate Indicates thenumber ofmegabytesreceived persecond.
Megabytesperseconds(MB/s)
None Statistics
Received From Hosts Byte Rate Indicates thenumber ofmegabytesreceived fromhosts per second.
Megabytesperseconds(MB/s)
None Statistics
Received From Other Cluster Byte Rate Indicates thenumber ofmegabytesreceived fromother nodes.
Megabytesperseconds(MB/s)
None Statistics
Received From Same Cluster Byte Rate Indicates thenumber ofmegabytesreceived from thesame cluster.
Megabytesperseconds(MB/s)
None Statistics
Received From Storage Byte Rate Indicates thenumber ofmegabytesreceived fromstorage.
Megabytesperseconds(MB/s)
None Statistics
64Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Name Description Units Default AlertConditions
BMCProactiveNetAttributeType
Sent Byte Rate Indicates thenumber ofmegabytes sent tohost, diskcontrollers, andother nodes in thesame and otherclusters.
Megabytesperseconds(MB/s)
None Statistics
Sent To Hosts Byte Rate Indicates thenumber ofmegabytestransmitted tohost.
Megabytesperseconds(MB/s)
None Statistics
Sent To Other Cluster Byte Rate Indicates thenumber ofmegabytestransmitted toother nodes in theother clusters.
Megabytesperseconds(MB/s)
None Statistics
Sent To Same Cluster Byte Rate Indicates thenumber ofmegabytestransmitted toother nodes in thesame cluster.
Megabytesperseconds(MB/s)
None Statistics
Sent To Storage Byte Rate Indicates thenumber ofmegabytestransmitted tostorage.
Megabytesperseconds(MB/s)
None Statistics
65 Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
IBM SVC MDiskAttributes
Name Description Units Default AlertConditions
BMCProactiveNetAttributeType
Available Path Count Indicates the number ofnodes that have access tothe managed disk.
Paths 0 = Alarm Statistics
Status Indicates the status of themanaged disk.
{0=OK; 1 =Degraded; 2 =Failed}
1 = Warning2 = Alarm
Availability
Read Byte Rate Indicates the amount of dataread from the disk.
Megabytes perseconds (MB/s)
None Statistics
Read Operation Rate Indicates the amount ofoperations read per second
Operationsper seconds(operations/s)
None Statistics
Read Response Time Indicates the average timefor a disk to complete a readrequest
Milliseconds(ms)
Warning ≥ 10ms Alarm ≥ 100ms
ResponseTime
Write Byte Rate Indicates the amount of datawritten per second.
Megabytes perseconds (MB/s)
None Statistics
Write Operation Rate Indicates the amount ofoperations written persecond.
Operationsper seconds(operations/s)
None Statistics
Write Response Time Indicates the average timefor a disk to complete awrite request.
Milliseconds(ms)
Warning ≥ 10ms Alarm ≥ 100ms
ResponseTime
66Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
IBM SVC NodeAttributes
Name Description Units Default Alert Conditions BMCProactiveNetAttribute Type
Processor Utilization Indicates thepercentageof utilizationof theprocessor.
Percentage(%)
Warning whengreater than 90%;Alarm when greaterthan 99%
Statistics
Received Byte Rate Indicates thenumber ofmegabytesreceived persecond.
Megabytesperseconds (MB/s)
None Statistics
Received Operation Rate Indicates thenumber ofoperationsreceived persecond.
Operationsperseconds(operations/s)
None Statistics
Received Response Time Indicates theaverage timetaken tocompletereceiverequests.
Milliseconds(ms)
Warning whengreater than 10 ms;Alarm when greaterthan 100ms
Response Time
Sent Byte Rate Indicates themegabytessent.
Megabytesperseconds (MB/s)
None Statistics
Sent Operation Rate Indicates thenumber ofoperationssent.
Operationsperseconds(operations/s)
None Statistics
Sent Response Time Indicates theaverage timetaken tocompletesendrequests.
Milliseconds(ms)
Warning whengreater than 10 ms;Alarm when greaterthan 100ms
Response Time
67 Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Name Description Units Default Alert Conditions BMCProactiveNetAttribute Type
Status Indicates thestatus of thenode.
{0= OK;1 =Degraded; 2=Failed}
1 = Warning2 = Alarm
Availability
For detailed information about KPI, see Managing Baselines and Key Performance Indicators.
68Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
IBM SVC PoolAttributes
Name Description Units Default AlertConditions
BMCProactiveNetAttributeType
Consumed Capacity Indicates thetotal size of thespace actuallyallocated orreserved.
Gigabytes(GB)
None Statistics
Consumed Capacity Percentage Indicates thepercentage of thepool that isactuallyallocated orreserved.
Percentage(%)
Alarm if ≥ 75% Statistics
Status Indicates thestatus of thepool.
{0=OK; 1 =Degraded; 2= Failed}
1 = Warning2 = Alarm
Availability
Subscribed Capacity Indicates thetotal host visiblecapacity.
Gigabytes(GB)
None Statistics
Subscribed Capacity Percentage Indicates thepercentage of thepool that issubscribed.
Percentage(%)
None Statistics
Read Byte Rate Indicates theamount of dataread from thedisk.
Megabytesper seconds(MB/s)
None Statistics
Write Byte Rate Indicates theamount of datawritten persecond.
Megabytesper seconds(MB/s)
None Statistics
69 Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
IBM SVC SAN Volume ControllerAttributes
Name Description Units Default AlertConditions
BMCProactiveNetAttribute Type
Collection Status Indicates the status of thecollection.
{0= OK; 1 =Degraded; 2=Failed}
1 = Warning2 = Alarm
CollectionStatus
Port Count Number of FC and Ethernetports on the Storage System.Note: This value can be used toknow the number of requiredlicenses for the monitoringsystem.
Ports None Statistics
Time Since LastStatistics Update
Displays the number ofminutes since a new statisticsfile was created on the cluster.
minutes Warningwhen > 30
Statistics
70Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
IBM SVC VolumeAttributes
Name Description Units Default AlertConditions
BMCProactiveNetAttributeType
Consumed Capacity Indicates thetotal size of thespace actuallyallocated orreserved.
Gigabytes (GB)
None Statistics
Consumed Capacity Percentage Indicates thepercentage ofthe volume thatis actuallyallocated orreserved.
Percentage (%)
None Statistics
Host Visible Capacity Indicates thereal capacity ofthe volumeprimary copy.
Gigabytes (GB)
None Statistics
Read Byte Rate Indicates theamount of dataread per second.
Megabytes perseconds(MB/s)
None Statistics
Read Operation Rate Indicates theamount ofoperations readper second.
Operations perseconds(operations/s)
None Statistics
Read Response Time Indicates theaverage timetaken tocomplete a readrequest
Milliseconds(ms)
Warning if ≥10msAlarm if ≥100ms
ResponseTime
Status Indicates thestatus of thevolume.
{0=OK;1=Degraded;2=Failed}
1 = Warning2 = Alarm
Availability
Time Since Last Activity Number of dayssince anyactivityoccurred on theLUN.
days None Statistics
71 Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Name Description Units Default AlertConditions
BMCProactiveNetAttributeType
Write Byte Rate Indicates theamount of datawritten persecond.
Megabytes perseconds(MB/s)
None Statistics
Write Operation Rate Indicates theamount ofoperationswritten persecond.
Operations perseconds(operations/s)
None Statistics
Write Response Time Indicates theaverage timetaken tocomplete a writerequest.
Milliseconds(ms)
Warning if ≥10msAlarm if ≥100ms
ResponseTime
72Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
IBM SVC Volume MirrorAttributes
Name Description Units Default AlertConditions
BMCProactiveNetAttributeType
Status Indicates thestatus of thevolume mirror.
{0=OK;1=Degraded;2=Failed}
1 = Warning2 = Alarm
Availability
Synchronized* Indicateswhether theVolume Mirroris synchronizedwith the volumeit belongs to.
{0 = No;1 = Yes}
0 = Warning Statistics
73 Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
IBM SVC Storage SystemAttributes
Name Description Units Default AlertConditions
BMCProactiveNetAttributeType
Read Byte Rate Indicates the amount of dataread per second.
Megabytesperseconds(MB/s)
None Statistics
Read Operation Rate Indicates the amount ofoperations read per second
Operations perseconds(operations/s)
None Statistics
Read Response Time Indicates the average time takento complete a read request
Milliseconds (ms)
Warning if > 10msAlarm if > 100ms
Response Time
Status Indicates the status of thestorage system.
{0 = OK ; 1= Degraded; 2 =Failed}
1 = Warning2 = Alarm
Availability
Write Byte Rate Indicates the amount of datawritten per second.
Megabytesperseconds(MB/s)
None Statistics
Write Operation Rate Indicates the amount ofoperations written per second.
Operations perseconds(operations/s)
None Statistics
Write Response Time Indicates the average time takento complete a write request.
Milliseconds (ms)
Warning if > 10msAlarm if > 100ms
Response Time
For detailed information about KPI, see Managing Baselines and Key Performance Indicators.
74Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Configuration VariablesThis 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 ProactiveNetPerformance Management - IBM SVC Storage Monitoringupon a problem with the managed SVC systems.
collectionHubHeapSizeMax n/a Maximum heap size in megabytes allocated to the JavaCollection Hub.Default: Not set
collectionHubHeapSizeMin n/a Minimum heap size in megabytes allocated to JavaCollection Hub.Default: Not set
collectionHubOverrideJavaCommandLine
n/a Command line used by the KM to launch the JavaCollection Hub. Default: Not setThis variable should only be set if instructed by SentrySupport.
debugEndTime None 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 None List of default options to be executed by BMC ProactiveNetPerformance Management - IBM SVC Storage Monitoring onreinitialization. The default values are: 0=unchecked;1=checked
resetThresholds
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 needto be separated by a carriage return.Example: “resetThresholds;1” will display the remove thresholdsoption selected by default in the Reinitialize KM wizard.
disableJavaInformationMessage
0 = activated When set to ‘1’, disables the pop-up information messagedisplayed when the java settings are modified.Default: Not set
disableJRECheck 0 When set to ‘1’, disables the validation tests of the JREused by the KM to run Java code and therefore force theKM to use a non-Sun or non-Oracle JRE
disablePslExecuteBugWorkaround
0 = activated When set to ‘1’, deactivates the workaround in the KMfor a bug in the PslExecute() PSL function.
75 Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Variables Default Value Description
If the KM detects that the version of the PATROL Agent isaffected by the PslExecute() bug, it uses an alternatetechnique to create asynchronous threads with theevent_trigger() function and the RemPsl standard event.The disablePslExecuteBugWorkaround variable disablesthis workaround.
discoveryIntervalMinutes 60 Specifies how often discoveries will be performed todetect new components (in minutes).
excludeVolumes None Filter to exclude all volumes whose names match thespecified regular expression.
exportActivityReports None When set to 1, the SEN_SVC_activity*.csv report isautomatically generated and stored in the %PATROL_HOME%\log folder.
exportLUNsMappingTable None When set to 1, the SEN_SVC_LUNS_mapping_table*.csvreport is automatically generated and stored in the %PATROL_HOME%\log folder.
exportScheduling None Time when the activity and/or LUNs Mapping Tablereports will be generated. Format required: HH:MM:SS
forceClassicConfigMode 0 = disabled When the KM is used with BMC ProactiveNet, all the KMconfiguration menus are disabled in the PATROLConsoles. To enable them, set theforceClassicConfigMode variable to 1.
includeVolumes None Filter to keep only volumes whose names match thespecified regular expression.
javaPassword None Password associated to the javaUsername variable.
javaPath None Path to the folder containing the Java executable usedby the Collection Hub.Default: Not set (The KM will search for a suitable JREautomatically).
javaUsername None Username used to launch the Java Collection Hub.Default: Not set. variable.
parametersAutoResetTimeout None Indicate the time in seconds after which the incrementalparameters should be automatically reset when an erroris detected.
pausedObjectList n/a List of the PATROL object path of the paused objects. (i.e. forwhich no collection will be performed).
pemMessages All How much internal information should be sent as PATROLevents.
When set to ‘all’, all internal KM messages (problems andinformational 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 thestatistics files from the IBM SVC nodes.
76Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Variables Default Value Description
removedObjectList n/a List of instances that have been removed from the monitoringenvironment through the Remove KM Command.
sowMessages All How much internal information should be displayed in the SystemOutput Window in the PATROL Console.
When set to ‘all’, all internal KM messages (problems andinformational 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 None List of parameters for which custom thresholds have been setthrough the Modify Thresholds KM command.
temporaryFolder None Path to the folder where temporary files used by the KM tocompute statistics will be stored.Default: Not set (assumed PATROL Agent’s own temporaryfolder)
ThresholdsManagementMode Retrievedfrom the KMconfiguration
Specifies how the KM should manage the alert thresholds onparameters. Please read carefully the User Guide chapter formore information on this topic.Possible values:
'empty' (automatic detection of the suitable thresholdmanagement)
‘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)
unexpectedStatusInternalIssueNotification
0 =deactivated
When set to 1, the KM will inform you of any internalproblems or of any special operations it may perform.
unexpectedStatusManagement None Specifies the action to be performed when the product is unableto 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
77 Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Managing Baselines and Key PerformanceIndicatorsIn order to facilitate the detection of abnormalities on your monitored environment, BMCProactiveNet calculates baselines per attributes based on values collected over a specifiedperiod of time to determine a normal operating range. When the collected values for theseattributes 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 aspecified time period and establishing a low baseline value (consisting of the 10th percentile ofall the values for a given time period) and a high baseline value (consisting of the 90th percentileof all the values for a given time period), taking a weighted average of these values over time. Ahigher weight is given to the latest data being factored into the baseline average. The accuracy ofthe baseline improves over time.
Requirements for baseline generation
For baselines to be generated for an attribute, that abnormality threshold means that thethreshold exists and is not suppressed. Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes thathave an active abnormality threshold and are also KPI attributes will have baselines generatedfor 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 BMCProactiveNet Administration Console. In this KM, some attributes have been designated asimportant indicators of performance (KPIs). We do not recommend that these default settingsare modified.
However, advanced users may activate or deactivate KPIs from the BMC ProactiveNet
78Monitor Types and Attributes
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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. TheKPI Administration dialog box is displayed.
2. From the Monitor Type list, choose the monitor type for which you want to add or removeKPI 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 PerformanceIndicators:
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 thatmonitor type
For complete and detailed information on this procedure, please refer to the BMC ProactiveNetdocumentation available f rom BMC Web site.
79
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
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 32Attributes 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 Statistics Update 69
Write Byte Rate 65, 70, 73
Write Operation Rate 65, 70, 73
Write Response Time 65, 70, 73
Zero Buffer Time Percentage 61Automatic Reporting 37
- B -Baselines
BMC ProactiveNet Performance Management 77
Generation 77
Manage 77
Requirements 77BMC ProactiveNet Performance Management
Abnormalities 77
Baselines 77
Key Performance Indicators 77
KPI 77Busiest Volume
identifying 50
80
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
- C -Component Installation package
creating 17
downloading 18Configuration 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 74Configuring
discovery interval 30
monitor settings 24Configuring Monitor Thresholds 38
Configuring thresholds 38
- D -Debug Mode
enabling 28
Deleting a policy 41
Deleting a Threshold Configuration 40
Diagnose
Slow Virtual Volume 47Disabling a policy 41
Discovery Interval
configuring 30Disk 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 77Goals 12
Graph
create 50
- I -Identify
Node Overload 44Importing the Monitoring Solution 16
Installation
configuring 22Installing 18
Installing the Monitoring Solution 16
Integrating 20
- K -Key Concepts 11
Key Performance Indicators
81
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Key Performance Indicators
BMC ProactiveNet Performance Management 77
Manage 77KPI
BMC ProactiveNet Performance Management 77
Manage 77
- M -Manage
Baselines 77
Key Performance Indicators 77
KPI 77Managing Policies 40
Monitor Settings
configuring 24Monitor thresholds 38
Monitor Type
IBM SVC SAN Volume Controller 69Monitor 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 72Monitoring
Storage 43
volumes 35Monitors
HP 3PAR Node 44
HP 3PAR Storage Pool 53
HP 3PAR Storage System 56
HP 3PAR Volume 47
- O -Overload
Node 44
- P -Package 17, 18
Policies 40
Policy 40, 41
- R -Read Byte Rate 50
Reference Guide 60
Reporting
Disk Space Consumption 53Reports
scheduling 37
- S -Scheduling
Reports 37Storage
Monitoring 43Storage System
Overall activity 56
- T -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
82
BM
C Pr
oact
iveN
et P
erfo
rman
ce M
anag
emen
t -
IBM
SV
C St
orag
e M
onit
orin
g V
ersi
on 1
.2.0
0
Variables
javaPath 32
javaUsername 32
password 32
pausedObjectList 32
productVersion 32
psCommand 32
removedObjectList 32
scheduledReports 32
startupDelay 32
ThresholdsManagementMode 32View
create 50Virtual Volume
Slow 47Volumes
filtering 35
- W -What's New 7
Write Byte Rate 50
About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software, providescomprehensive multi-platform monitoring solutions that enable management of thehardware and software aspects of all servers and SANs and covering up to 100 % ofcustom applications within the BMC ProactiveNet Performance Managementenvironment. Sentry Software also develops adapters for BMC Atrium Orchestrator thatenables IT administrators to automate the execution of common requests and tasks thatoccur in the daily course of IT operations. Combined with BMC’s servers and networkautomation tools, the adapters allow IT administrators to implement provisioning anddecommissioning workflows that cover all layers of their IT infrastructure. Finally, SentrySoftware designs connectors that bring storage capacity metrics into BMC TrueSightCapacity Optimization to ensure IT administrators that their storage infrastructure isproperly sized for their current and future needs.
Like us on Facebook:facebook.com/sentrysoftware
Follow us on Twitter:
twitter.com/sentrysoftware
LEARN MORE
To learn more about our solutions, please visit :www.sentrysoftware.com/solutions
© BMC Software, Inc. All rights reserved.
ABOUT MARKETZONE DIRECT PRODUCTS
The BMC MarketZone Directprogram sells and supportsthird-party products thatcomplement and/or augment BMCsolutions. MarketZone Directproducts are available under BMClicense and support terms.
About BMC Software™BMC Software helps leading companies around the world put technology at the forefrontof business transformation, improving the delivery and consumption of digital services.From mainframe to cloud to mobile, BMC delivers innovative IT management solutionsthat have enabled more than 20,000 customers to leverage complex technology intoextraordinary business performance—increasing their agility and exceeding anythingthey previously thought possible. For more information about BMC Software, visit
www.bmc.com.
Bus ines s thrives when IT runs s marter,fas ter and s tronger. That’s why the mos tdemanding IT organizations in the worldrely on BMC Software acros s dis tributed,mainframe, virtual and cloudenvironments . Recognized as the leader inBus ines s Service Management, BMC offersa comprehens ive approach and unifiedplatform that helps IT organizations cutcos t , reduce ris k and drive bus ines sprofit . For the four fis cal quarters endedSeptember 30,2011, BMC revenue wasapproximately $2.2 billion.
BUSINESS RUNS ON I.T .
I.T . RUNS ON BMC SOFT WARE