Ibm Spectrum - Usersguide PDF
Ibm Spectrum - Usersguide PDF
Version 5.2.9
User's Guide
IBM
SC27-6588-01
Note:
Before using this information and the product it supports, read the information in “Notices” on page 359.
This edition applies to version 5, release 2, modification 9 of IBM Spectrum Control (product numbers 5725-F93,
5725-G33, 5725-Y23, and 5725-Y24) and to all subsequent releases and modifications until otherwise indicated in
new editions.
This edition replaces SC27-6588-00
© Copyright IBM Corporation 2001, 2016.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this guide . . . . . . . . . . . v Analyzing and re-tiering volumes in pools on tier
Who should read this guide . . . . . . . . . v 1 . . . . . . . . . . . . . . . . . 61
Publications . . . . . . . . . . . . . . v Collocating volumes . . . . . . . . . . 63
Accessing publications online. . . . . . . . v Monitoring capacity usage at different levels of a
IBM Redbooks . . . . . . . . . . . . vii business hierarchy . . . . . . . . . . . . 64
Translation . . . . . . . . . . . . . vii Comparing storage usage in each department . . 66
Providing feedback about publications . . . . vii Using applications and subcomponents to monitor
IBM Spectrum Control Service Management capacity and space usage . . . . . . . . . . 68
Connect community . . . . . . . . . . . viii Viewing storage capacity and usage trends . . . 69
Contacting IBM Software Support . . . . . . viii Limiting a set of storage to provision in the vSphere
Reporting a problem . . . . . . . . . . viii Web Client extension . . . . . . . . . . . 71
Conventions used in this guide . . . . . . . . ix Viewing NPIV connections between server ports
and switch ports in a fabric . . . . . . . . . 72
New for IBM Spectrum Control Version
5.2.9 . . . . . . . . . . . . . . . . xi Chapter 5. Managing resources . . . . 75
Adding resources . . . . . . . . . . . . 75
Resources that you can monitor . . . . . . 75
Chapter 1. Getting started . . . . . . . 1 Required user roles for monitoring resources . . 80
Managing resources . . . . . . . . . . . . 4 Adding storage systems . . . . . . . . . 81
Configuring and administering . . . . . . . . 7 Adding fabrics and switches. . . . . . . . 85
Navigation . . . . . . . . . . . . . . . 8 Adding hypervisors . . . . . . . . . . 88
Adding servers . . . . . . . . . . . . 91
Chapter 2. Product licenses. . . . . . 15 Removing resources . . . . . . . . . . . 98
Functions that are available based on role and Collecting data . . . . . . . . . . . . . 98
license . . . . . . . . . . . . . . . . 16 Collecting asset and status data. . . . . . . 99
Collecting performance data . . . . . . . 103
Chapter 3. Product overview . . . . . 23 Collecting information about shares on storage
Architecture . . . . . . . . . . . . . . 23 systems . . . . . . . . . . . . . . 110
Interfaces for IBM Spectrum Control . . . . . . 24 Alerting and event processing . . . . . . . . 111
Starting IBM Spectrum Control . . . . . . . . 25 Alert severities . . . . . . . . . . . . 113
Navigation . . . . . . . . . . . . . . 26 Defining alerts . . . . . . . . . . . . 113
Replication products . . . . . . . . . . . 31 Viewing and modifying alert definitions . . . 121
Key concepts . . . . . . . . . . . . . . 32 Viewing and modifying alert notification
Data collection . . . . . . . . . . . . 32 settings . . . . . . . . . . . . . . 124
Performance monitoring and troubleshooting . . 33 Viewing alerts . . . . . . . . . . . . 127
Applications and departments . . . . . . . 35 Acknowledging alerts . . . . . . . . . 129
Storage optimization . . . . . . . . . . 36 Removing alerts . . . . . . . . . . . 130
Cloud configuration . . . . . . . . . . 37 Viewing information about resources . . . . . 130
Provisioning storage . . . . . . . . . . 42 How information is organized . . . . . . . 130
Storage reclamation. . . . . . . . . . . 46 Dashboard view . . . . . . . . . . . 133
IBM Spectrum Control VASA provider . . . . 47 Viewing information about top-level resources 137
vSphere Web Client extension for IBM Spectrum Viewing information about internal, object, and
Control . . . . . . . . . . . . . . . 48 related resources . . . . . . . . . . . 138
Alerts . . . . . . . . . . . . . . . 49 Monitoring the status and condition of resources 139
Reporting . . . . . . . . . . . . . . 51 How the condition of a resource is determined 141
Units of measurement for storage data . . . . 51 Viewing the overall condition of resources. . . 144
Role-based authorization . . . . . . . . . 52 Viewing the condition of specific types of
Fabrics and zones . . . . . . . . . . . 53 resources . . . . . . . . . . . . . . 144
Agents . . . . . . . . . . . . . . . 56 Viewing the status of resources . . . . . . 145
Acknowledging the condition and status of
Chapter 4. Scenarios. . . . . . . . . 59 resources . . . . . . . . . . . . . . 146
Monitoring the performance of resources . . . . 149
Optimizing the performance of storage virtualizers 59
Viewing performance information . . . . . 150
Redistributing volume workloads to balance
Viewing performance alerts and threshold
pools . . . . . . . . . . . . . . . 60
violations. . . . . . . . . . . . . . 164
Administrators and users must be familiar, or become familiar, with the following
concepts:
v Storage Area Network (SAN)
v Simple Network Management Protocol (SNMP)
v Storage provisioning, optimization, performance, tiers, and cloud configuration
v IBM® DB2®
v Jazz™ for Service Management
v IBM Tivoli® Common Reporting
v vSphere Web Client extension and VASA
Publications
A number of publications are provided with IBM Spectrum Control.
IBM Tivoli Storage Productivity Center for Replication is no longer installed with
IBM Spectrum Control. For current Tivoli Storage Productivity Center for
Replication users who upgrade to IBM Spectrum Control, Tivoli Storage
Productivity Center for Replication will remain available. See IBM Knowledge
Center for any earlier versions of Tivoli Storage Productivity Center for Replication
publications.
IBM Redbooks
The IBM Redbooks® are publications about specialized topics.
You can order publications through your IBM representative or the IBM branch
office serving your locality. You can also search for and order books of interest to
you by visiting the IBM Redbooks home page at http://www.redbooks.ibm.com.
Translation
Translated publications are available from IBM Knowledge Center, which is
available in certain translated languages. It is displayed in the language that is
appropriate for the browser locale setting.
When a locale does not have a translated version, the information is displayed in
English, which is the default language. Translations of the PDFs are available when
the information is translated.
You can also review the IBM Software Support Handbook, which is available at
http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html.
Reporting a problem
Provide the IBM Support Center with information about the problems that you
report.
This publication uses several conventions for special terms and actions, and for
operating system-dependent commands and paths.
Port names
IBM Spectrum Control now displays the switch blade number, port
number, and blade names just as they were defined in other tools, such as
Brocade Network Advisor. On a list of switches, the Name column
displays the port names that you defined by using the switch management
tools. The Port number column now shows only the port number
information.
Enhanced platforms
IBM DB2 Version 10.5 Fix Pack 6 is now included with IBM Spectrum
Control. If you already have a version of DB2 that is supported by IBM
For information about limitations and known issues that might occur when you
use IBM Spectrum Control Version 5.2.9, see http://www.ibm.com/support/
docview.wss?uid=swg21974306.
Related information:
New for IBM Spectrum Control Version 5.2.8
Knowledge Centers for Tivoli Storage Productivity Center Version 5.2.7 and
earlier
Complete the following tasks to install and set up IBM Spectrum Control for
monitoring and managing storage resources. Click the included links to learn more
information about each task.
Table 2. Tasks for getting started with IBM Spectrum Control
Managing resources
Learn about the key tasks for getting started with monitoring and managing
storage resources.
After installing IBM Spectrum Control and adding resources for monitoring,
complete the following tasks to manage your storage environment.
Table 3. Tasks for monitoring and managing resources
Related concepts:
Chapter 5, “Managing resources,” on page 75
Use IBM Spectrum Control to monitor and manage the resources and storage
infrastructure in an enterprise environment. In the GUI, you can view the
condition, capacity, performance, and relationships of storage resources.
Complete any of the following tasks to customize IBM Spectrum Control for your
environment and administer its components.
Navigation
The IBM Spectrum Control GUI provides many of the functions for managing a
storage environment. To access the functions in this GUI, use the menu bar at the
top of the main window.
Keyboard navigation
Most of the features of the IBM Spectrum Control GUI are accessible by using the
keyboard. For those features that are not accessible, equivalent function is available
by using the command-line interface (CLI), except as noted in the product release
notes.
You can use keys or key combinations to perform operations and initiate many
menu actions that can also be done through mouse actions. The following sections
describe the keys or key combinations for different parts of the GUI:
For navigating in the GUI and the context-sensitive help system:
v To navigate to the next link, button, or topic within a panel, press Tab.
v To move to the previous link, button, or topic within a panel, press
Shift+Tab.
v To select an object, when the object is in focus, press Enter.
For actions menus:
v To navigate to the grid header, press Tab.
v To reach the drop-down field, press the Left Arrow or Right Arrow key.
v To open the drop-down menu, press Enter.
v To select the menu items, press the Up Arrow or Down Arrow key.
v To start the action, press Enter.
For filters:
To specify a filter option and text:
1. Press Tab to navigate to the magnifying glass icon.
2. Press the Up Arrow or Down Arrow key to navigate the filtering list.
3. Press Enter to select a filtering option.
4. When a filtering option is selected, the cursor moves to the filter text
box. Type the filter text and press Enter. To reset a filter, press Enter.
For text fields:
v To navigate to text fields, press Tab.
v To navigate to the fields that are available for editing, press Tab.
v To navigate to the next field or to the Submit button, press Tab.
For tables or lists:
The IBM Tivoli Storage Productivity Center license is now IBM Spectrum Control
Standard Edition.
To view a complete list of devices that can be used with IBM Spectrum Control, go
to http://www.ibm.com/support/docview.wss?uid=swg21386446. Click the
appropriate release under Storage.
Table 5 shows the IBM Spectrum Control licenses and their names from previous
releases.
Table 5. IBM Spectrum Control licenses and their previous names
Name of Tivoli Storage Name of Tivoli Storage
Name of IBM Spectrum Productivity Center Version Productivity Center Version
Control license 5.1 license 5.2.1 through 5.2.7 license
IBM Spectrum Control Tivoli Storage Productivity Tivoli Storage Productivity
Standard Edition Center Center
IBM Spectrum Control Tivoli Storage Productivity Tivoli Storage Productivity
Standard Select Edition Center Select Center Select
IBM Spectrum Control Tivoli Storage Productivity IBM SmartCloud Virtual
Advanced Edition Center Advanced or IBM Storage Center Storage
SmartCloud® Virtual Storage Analytics Engine
Center
IBM Spectrum Control Tivoli Storage Productivity IBM SmartCloud Virtual
Advanced Select Edition Center Advanced or IBM Storage Center Storage
SmartCloud Virtual Storage Analytics Engine
Center
Users who are assigned the Administrator role or the Monitor role can use product
functions. The functions that are available depend on the role that is assigned to
the user:
Administrator role
Users who are assigned the Administrator role have access to all
monitoring and administrative functions and are limited only by license
restrictions.
Monitor role
Users who are assigned the Monitor role can view information about
16 IBM Spectrum Control: User's Guide
monitored resources and other objects such as tasks, alerts, and service
classes. They can acknowledge alerts and resource statuses, open logs, and
open management GUIs. Users who are assigned the Monitor role do not
have access to administrative functions, with the following exceptions:
v They can assign storage pools to tiers.
v They can be granted permission in a service class to provision storage by
using the service class. If so, they can use the Provision Storage wizard
to create a provisioning task. Users can delete provisioning tasks that
they create. If the service class specifies that administrator approval is
not required, the users can run or schedule the provisioning tasks that
they create.
To use some functions, you must have the IBM Spectrum Control Advanced
Edition license. If you have the IBM Spectrum Control Standard Edition license or
the IBM Spectrum Control Standard Select Edition license, the following functions
are not available:
v Storage tier optimization. The Analyze Tiers wizard is not available.
v Pool balancing. The Balance Pools wizard is not available.
v Block storage provisioning. You are not able to provision volumes by using
either the Provision Storage wizard or the vSphere Web Client extension.
However, there are no license restrictions for file storage provisioning, therefore,
Network Attached Storage (NAS) file shares can be provisioned.
The following table outlines the functions available by role. Some functions are
restricted to the Administrator role. Functions that are restricted to the IBM
Spectrum Control Advanced Edition license are also shown. In addition to the
restrictions listed in this table, users who are assigned the Monitor role do not
have access to user management functions.
Table 6. Role and license restrictions
Functions that require
the IBM Spectrum
Resource or Control Advanced
object Functions available by role Edition
Performance Users who are assigned the Monitor or All functions are
monitors Administrator role can complete the following available, depending
monitoring actions: on role.
v View information about the switch or storage
system that is being monitored
v Open performance monitor logs
v Export performance monitor information to a file
Architecture
The IBM Spectrum Control consists of several components that form the
infrastructure of its storage-management functions.
Data server
This component is the control point for product scheduling functions,
configuration, and event information. It also includes functions that
schedule data collection and discovery for the Device server.
Device server
This component discovers, gathers information from, analyzes performance
of, and controls storage subsystems and SAN fabrics. It coordinates
communication with and data collection from agents that scan SAN fabrics
and storage devices.
Web server
IBM Spectrum Control uses the WebSphere Application Server as the web
application server to host its GUI, storage management API for cloud, and
VMware vSphere web client extension.
Alert server
This component manages the complex event processing that is related to
alerting on the condition of resources and their attributes. The ability to
detect and be notified about configuration, capacity, and performance
changes within a storage environment is important to helping you
maintain and administer storage resources.
Before you start IBM Spectrum Control, ensure that you are using a supported web
browser. For a list of web browsers that you can use with IBM Spectrum Control,
see IBM Spectrum Control interoperability matrix at http://www.ibm.com/
support/docview.wss?uid=swg21386446. In the Agents, Servers and Browser column,
click the version of IBM Spectrum Control that is installed on your system. On the
next page, click Web Browsers to find the web browsers that you can use.
Start the IBM Spectrum Control GUI to administer and monitor the condition,
capacity, and relationships of the resources within your storage environment.
1. On a server running the Windows operating system, start IBM Spectrum
Control GUI. If you are not on a server running the Windows operating
system, start a web browser and enter the following address in the address
field:
https://host_name:port/srm
Keyboard navigation
Most of the features of the IBM Spectrum Control GUI are accessible by using the
keyboard. For those features that are not accessible, equivalent function is available
by using the command-line interface (CLI), except as noted in the product release
notes.
You can use keys or key combinations to perform operations and initiate many
menu actions that can also be done through mouse actions. The following sections
describe the keys or key combinations for different parts of the GUI:
For navigating in the GUI and the context-sensitive help system:
v To navigate to the next link, button, or topic within a panel, press Tab.
v To move to the previous link, button, or topic within a panel, press
Shift+Tab.
v To select an object, when the object is in focus, press Enter.
For actions menus:
v To navigate to the grid header, press Tab.
v To reach the drop-down field, press the Left Arrow or Right Arrow key.
v To open the drop-down menu, press Enter.
v To select the menu items, press the Up Arrow or Down Arrow key.
v To start the action, press Enter.
For filters:
To specify a filter option and text:
1. Press Tab to navigate to the magnifying glass icon.
2. Press the Up Arrow or Down Arrow key to navigate the filtering list.
3. Press Enter to select a filtering option.
4. When a filtering option is selected, the cursor moves to the filter text
box. Type the filter text and press Enter. To reset a filter, press Enter.
For text fields:
v To navigate to text fields, press Tab.
v To navigate to the fields that are available for editing, press Tab.
v To navigate to the next field or to the Submit button, press Tab.
For tables or lists:
Replication products
Tivoli Storage Productivity Center for Replication and IBM Copy Services Manager,
which is built on existing replication technology, are the replication tools available
for use with IBM Spectrum Control.
Availability
Tivoli Storage Productivity Center for Replication is available under the following
conditions:
v In Tivoli Storage Productivity Center V5.2.7 and earlier, Tivoli Storage
Productivity Center for Replication is automatically available.
v In IBM Spectrum Control V5.2.8 and later, Tivoli Storage Productivity Center for
Replication is only available if you upgrade from Tivoli Storage Productivity
Center V5.2.7 or earlier.
IBM Copy Services Manager is available with every IBM Spectrum Control V5.2.8
or later license.
Information about how to use Tivoli Storage Productivity Center for Replication is
available in the IBM Knowledge Center for Tivoli Storage Productivity Center
V5.2.7. Use the following links to view this information:
Table 7. Information about Tivoli Storage Productivity Center for Replication
Task Link to related information
Learn about Tivoli Storage
Product overview
Productivity Center for
Replication and its key
concepts
IBM Copy Services Manager provides automation for 2-site replication, 3-site
replication, and advanced copy services from a single point of control across
multiple platforms. To learn more about how to download and install it, see
IBM Copy Services Manager.
Key concepts
This section contains a technical overview that will help you understand how IBM
Spectrum Control works. An understanding of the concepts in this section will
help you use IBM Spectrum Control effectively.
Data collection
To help you implement a storage management strategy, it is critical that you
determine the information that you want to gather about the resources within your
environment. You can schedule different data collection jobs depending on the
types of information that you want to gather and the resources that you want to
monitor.
Before you can troubleshoot and view reports about performance, you must collect
data about monitored resources. Performance monitors are data collection jobs that
gather performance information about resources. This information includes metrics
that measure the performance of the components within a resource. Metrics
measure the performance characteristics of volumes, ports, and disks on storage
systems and switches. IBM Spectrum Control provides many different metrics for
measuring performance. For example, some key metrics for storage systems are
I/O rate in I/O operations per second, data rate in MiB per second, and response
time in milliseconds.
You can use metrics in IBM Spectrum Control to track growth or change in I/O
rates, data rates, and response times. In many environments, I/O and data rates
grow over time, and response times increase as those rates increase. This
relationship can help with "capacity planning" for your storage. As rates and
response times increase, you can use these trends to project when more storage
performance and capacity is required.
For example, you can define a performance threshold that alerts you when the
overall back-end response time for a managed disk on a SAN Volume Controller
exceeds a certain value. The overall back-end response time is a metric that
measures the average number of milliseconds that it takes to service each I/O
operation on a managed disk.
Applications
The Applications page shows capacity information about the applications that are
monitored by organization and interfaces with other enterprise groups that are
important to the running of a business. Use IBM Spectrum Control to view and
manage the resources that are defined to the applications. If the application is
associated with a department, information about that department is also shown.
The Departments page shows storage capacity information about the top level
departments, the subdepartments and any applications that belong to the
department that are monitored by IBM Spectrum Control.
Storage optimization
Storage optimization tasks optimize the resources in your storage environment.
You can use the web-based GUI to create tasks to balance pools, re-tier volumes, or
transform volumes that are in storage virtualizer pools.
Use the Balance Pools wizard to balance the workload of volumes across pools on
the same tier. The pools are analyzed and recommendations are generated to move
volumes from pools with high-activity values to pools with low-activity values.
Re-tiering volumes
Use the Analyze Tiering wizard to re-tier volumes to balance pools or to tier
volumes based on the criteria that you set in tiering policies. For example, you can
tier volumes that are based on the volume workload or on file usage, or both.
Depending on the conditions that are set in the tiering policy, recommendations are
generated. For example, you can reduce storage costs by moving volumes with low
workloads to lower or less expensive tiers. You can also improve performance and
use storage more efficiently by moving volumes with heavy workloads to the tiers
that best meet their workload requirements.
Transforming volumes
Use the Transform Storage wizard to complete the following tasks for one or more
volumes in storage virtualizer pools:
v Move volumes from one storage virtualizer pool to another pool in the same
storage virtualizer pool.
v Move volumes in a storage virtualizer pool to a pool that is enabled for Easy
Tier®.
v Convert fully allocated volumes to thin-provisioned volumes and convert
thin-provisioned volumes to fully allocated volumes.
v Convert fully allocated volumes to compressed volumes and convert compressed
volumes to fully allocated volumes.
Cloud configuration
To take advantage of the simplified provisioning and optimization capabilities that
are available by using the web-based GUI, some configuration is required.
To provision storage, you are required to specify only the storage capacity and
storage quality that is required. After volumes are created, IBM Spectrum Control
can analyze and optimize volume performance. To take advantage of these
capabilities, create service classes and, optionally, capacity pools.
Service classes
A service class is a set of properties that describe capabilities and characteristics of
storage resources. A service class typically describes a particular quality of service,
and is used during provisioning to describe storage requirements. For example, a
block-storage service class specifies properties such as a required RAID level, and
whether storage resources must be able to encrypt or thin provision volumes.
A file-storage service class describes attributes of file storage resources. The file
storage resources include Network Attached Storage (NAS) filers, Network Shared
Disks (NSDs), and file systems. When you provision shares, you specify the
requirements by using a file-storage service class. Based on the requirements of the
service class, IBM Spectrum Control identifies a file system or IBM SONAS NSD
for the share. Space on an IBM SONAS NSD is allocated if a new file system is
required or an existing file system requires more space.
A service class represents storage resources with common traits. These common
traits are the service class properties, and collectively describe a particular quality
of service. Before you create service classes, consider the levels of storage quality
that you want to have available for provisioning requests. For block storage, for
example, you can organize service classes by storage tier or RAID level. Some
service class properties are used during provisioning to identify the best location
for storage placement. Other service class properties determine how the storage is
configured, and reflect the performance, reliability, or security considerations for
the level of service.
In addition to the standard properties of a service class, you can create your own
properties by using custom tags. Custom tags can represent any common trait that
storage systems must have. For more information about creating your own
properties by using custom tags, see “Custom tags” on page 40.
To illustrate service classes, a set of predefined service classes are provided. From
the Service Classes page in the web-based GUI, you can view any of these service
classes for more information. Select a service class and then select Actions > View
/ Modify. To display help information about a service class property, complete the
following steps:
1. Move the mouse pointer over the field or control.
A question mark icon is displayed next to the field.
2. Move the mouse pointer over the question mark icon to display an explanation
of the property.
The following sample block-storage service classes are provided for illustration.
Gold The Gold service class represents the highest-performing storage resources
for mission-critical applications.
Silver The Silver service class represents high-performing storage resources for
applications in production.
The following sample file-storage service classes are provided for illustration.
NormalIsolation
The NormalIsolation service class describes normal isolation file storage by
specifying that shared storage is allowed. The file system from which the
NAS share is provisioned can contain other NAS shares.
EnhancedIsolation
The EnhancedIsolation service class describes enhanced isolation file
storage by specifying that dedicated storage is required. The file system
from which the NAS share is provisioned cannot contain other NAS shares.
Custom tags
In addition to the standard properties of a service class, you can create custom
requirements for the service class by specifying up to three custom tags. To
provide the service class, storage resources must have all the same tags that are
specified in the service class.
When you specify tags on a block-storage service class, only pools that have all the
same tags are candidates for provisioning. If a pool is not tagged, any tags on the
containing storage system also apply to the pool.
When you specify tags on a file-storage service class, only file systems and NSDs
that have all the same tags are candidates for provisioning. If a file system or NSD
is not tagged, any tags on the containing storage system also apply to the internal
resource.
Before you create service classes, consider whether there are any special
requirements for provisioning that are not addressed by the standard properties of
the service class. If so, tag the appropriate storage resources to satisfy custom
requirements of a service class. When you are defining the service class, specify the
custom tags that are required.
Before you create service classes, consider whether you want to allow users to
request their own storage. Consider whether you want user provisioning requests
to require administrator approval.
Before you create service classes, consider whether certain storage requests must
always be satisfied from a particular set of resources. If so, you can associate one
or more capacity pools with a service class. For example, suppose that a set of
storage resources are allocated to a particular department of your business. All
storage requests for that department must be satisfied by those storage resources.
In this case, you can add all the storage resources to a capacity pool and associate
that capacity pool with a service class. You can also add the members of the
department to the service class. The department members can then request their
own storage as needed. However, the requests can be satisfied only by the storage
resources that are allocated to the department.
When you are configuring capacity pools and service classes, keep in mind that a
storage resource can be a member of only one capacity pool. Adding storage
resources to a capacity pool is not a viable approach if the resources are already
members of another capacity pool. Consider specifying custom tags to achieve the
same result. In the preceding example, suppose that some or all of the storage
resources that are allocated to the department are already members of capacity
pools. In this case, you can instead tag the storage systems and the service class
with matching tags to achieve the same result. With either approach, only the
storage systems that are allocated to the department are candidates for
provisioning when storage is requested by using the service class.
When a file share is provisioned by the VMware vSphere Web Client extension, an
access path to the share is provided by IBM Spectrum Control. By default, the path
includes the cluster name of the file storage system in which the share is created. A
cluster name must be a valid host name that is registered with a Domain Name
System (DNS) server. If the cluster name is not valid, the share is not accessible
under the access path that is returned by IBM Spectrum Control.
To address this situation, you can set one of its custom tags for a file storage
system to specify an access path host name replacement. A file-storage service class
can specify which of the file storage system custom tags contains the access path
host name replacement.
If file shares are provisioned by using the VMware vSphere Web Client extension,
determine whether you must set access path host name replacements.
Capacity pools
Capacity pools are groups of storage resources. You can use capacity pools to
separate storage resources in any way that serves the needs of your environment
The following types of storage resources can be grouped into capacity pools:
v Storage systems
v Storage pools
v File systems of file storage systems
v IBM SONAS Network Shared Disks (NSDs)
You can organize storage resources into capacity pools in any way that serves your
business needs. For example, you can separate the storage resources that are
allocated for separate divisions of your business into separate capacity pools. You
can then track the storage use for each division separately, and restrict provisioning
requests to the appropriate set of storage resources.
You can track the used and available space for any set of storage resources by
adding the storage resources to a capacity pool. From the Capacity Pools pane of
the web-based GUI, you can view the total capacity of the resources, and monitor
the following capacity measurements:
v Used file space
v Available file space
v Used block space
v Available block space
You can use capacity pools to define a set of storage resources from which
provisioning requests must be satisfied. When you are requesting storage by using
the Provision Storage wizard or the vSphere Web Client extension, you can specify
a capacity pool. If you do, the provisioning request is restricted to resources in the
capacity pool. Only those resources are candidates for provisioning.
You can also associate a service class with capacity pools. If a service class is
associated with capacity pools, provisioning requests for the service class must
specify, and be constrained to, one of the associated capacity pools. Because you
can also grant non-administrative users permission to provision storage by using
the service class, associating capacity pools with the service class restricts the users
to a specific set of resources.
Provisioning storage
The Provision Storage wizard simplifies the steps for submitting provisioning
requests. When you use the Provision Storage wizard, you concern yourself only
with which service class is needed for the new volumes or shares, and how much
capacity you require.
Storage requirements
The different levels of storage quality that are provided by each service class are
defined by the service class properties. For example, each service class specifies a
different required storage tier that depends on the level of service that is required.
Because the Gold service class is for mission critical applications, it sets thin
provisioning off.
When you use the Provision Storage wizard, you concern yourself only with which
service class is required. If you are unfamiliar with the service classes, however,
you can open a separate window to view service class information. If you have
Administrator privileges, you can modify or create service classes.
Storage constraints
IBM Spectrum Control identifies the storage resources that can provide the
capacity and the service class from a set of storage resources. This set might be all
the storage resources that are known to IBM Spectrum Control, or it might be
constrained to a subset of those resources. In particular, your site can create
capacity pools. Capacity pools are groups of storage resources. You can use capacity
pools to separate storage resources in any way that serves the needs of your
environment or business. For example, a capacity pool might contain the storage
resources that are allocated to a particular department or division of your business.
A service class might restrict storage placement to one or more capacity pools. If
the service class you are provisioning from restricts placement, you must select one
of the allowed capacity pools. If the service class does not restrict storage
placement, you can specify that candidates for provisioning can be selected from
all storage resources that are known to IBM Spectrum Control, all storage resources
in any capacity pool, or storage resources in a particular capacity pool. If you are
unfamiliar with the capacity pools that you can select when you are using the
Provision Storage wizard, you can open a separate window to view capacity pool
information. If you have Administrator privileges, you can modify or create
capacity pools.
If the fabrics are managed by IBM Spectrum Control, the set of storage resources
might be further constrained by your zoning policy. If the zoning policy is not
configured to automatic zoning, only storage systems with connectivity to the
server or hypervisor are candidates for storage placement.
Provisioning volumes
Restriction: To provision volumes, you must have the IBM Spectrum Control
Advanced Edition license.
To provision volumes, you select one or more servers or hypervisors and start the
Provision Storage wizard. You can request one or more volumes. For each volume,
you specify a volume name, the capacity that is required, a service class, and,
optionally, a capacity pool. For each volume, IBM Spectrum Control identifies the
On storage systems, volumes are allocated in increments of a set unit size that
depends on the storage system type. Depending on the storage system that was
identified as the best location for the storage, the volumes that are allocated might
be larger than the capacity you requested for the following reasons:
v On SAN Volume Controller, Storwize V7000, and Storwize V7000 Unified,
volumes are allocated in increments of an extent size. The extent size is set when
the MDisk group is created. The capacity that you requested is rounded up, if
necessary, to the full extent size.
v On a DS8000, volumes are allocated in increments of a 1 GiB fixed extent size.
The capacity that you requested is rounded up, if necessary, to the full extent
size.
v On an XIV, volumes are allocated in fixed increments of 16 GiB. The capacity
that you requested is rounded up, if necessary, to complete the 16 GiB
increment.
Provisioning shares
To provision a share, you select one or more servers or hypervisors and start the
Provision Storage wizard. You specify the capacity that is required for the share, a
service class, and information about how to export the share. IBM Spectrum
Control identifies the file systems and Network Shared Disks (NSDs) that can
provide the capacity and the service class. From the set of file systems and NSDs
that can provide the capacity and service class, IBM Spectrum Control identifies
the best location for the storage. The best location for the storage is based on the
available space on the file system or NSD.
When you complete the steps of the Provision Storage wizard, IBM Spectrum
Control creates a provisioning task for the share or volume. If you request multiple
volumes, a separate task is created for each unique service class and capacity pool
combination you specify in your volumes request. If a requested volume is not
constrained to a capacity pool, the set of all available storage resources is
considered the capacity pool. If you have Administrator privileges, you can save,
run, or schedule provisioning tasks.
Although IBM Spectrum Control identifies the best location for storage when it
creates the provisioning task, the implementation of the task might fail. For
When a provisioning task is running, you can view its status in a details page. If
you run the provisioning task immediately after you complete the steps of the
Provision Storage wizard, the details page is already displayed. You can also
display details of a provisioning task from the Tasks page. From the details page,
you can open logs for the provisioning task. The logs show the steps that are taken
by the task during processing and include detailed information about any
warnings or errors.
Tracking
In the Provision Storage wizard, you can specify a ticket identifier for tracking
purposes. The ticker identifier is associated with the provisioning task, and with
any volume or share that is created by the provisioning task.
The ticket identifier can be viewed by showing the Ticket column in the Volumes
page or the Shares page. The ticket identifier can also be viewed in the properties
notebook for a volume or share.
Tip: If you request multiple volumes, a separate provisioning task is created for
each unique service class and capacity pool combination you specify in your
volumes request. By specifying a ticket identifier when you request the volumes,
you can easily track the set of provisioning tasks and volumes that are created by
the single request.
Storage configuration
Whether you are provisioning volumes or shares, IBM Spectrum Control configures
the storage and resources as specified by certain properties of the service class,
and, in the case of volumes, according to your zoning policy.
When you provision volumes, IBM Spectrum Control configures volumes and
resources according to properties of the service class:
v If the service class requires thin provisioning, the volume is created in a pool
that can thin provision volumes. During provisioning, other properties of the
service class are used to configure the thin provisioned volume for the particular
type of storage system that contains the pool. Because you configure thin
provisioned volumes differently for the different storage system types, the
service class has a unique set of thin provisioning properties for each type.
v If the service class specifies a multipathing policy for servers, the IBM System
Storage Multipath Subsystem Device Driver (SDD) on the server is configured to
use that policy. For the SDD to be configured, a Storage Resource agent (SRA)
must be running on the server. If a VMware vSphere multipathing policy is
specified for hypervisors, the policy is configured only if provisioning is initiated
from the vSphere Web Client extension for IBM Spectrum Control.
When you are provisioning volumes, if automatic zoning is enabled, new zones
might be created to connect a server to the storage system. Existing zones are used
When you provision shares, IBM Spectrum Control configures at least one file
access protocol for the file share.
Storage reclamation
You can use volume reclamation recommendations to reclaim unused storage
capacity in your environment and use your storage more efficiently.
The block storage systems in your data center that you add for monitoring are
regularly analyzed. You can view a list of the volumes that are allocated space but
are not used for storing data. By reclaiming the volumes, you can recycle existing
storage space instead of purchasing new storage media.
Reclamation recommendations which are based on capacity data are available after
a device probe, while recommendations which are based on performance data are
For a more thorough analysis, you can change the number of days for which
performance metrics are collected. If you shorten the analysis period, less data is
used to determine I/O activity. When you extend or shorten the analysis period, it
is also changed for other optimization features such as tiering and balancing.
To identify volumes that can be reclaimed, you enable performance monitoring for
the block storage systems. Only block storage systems that support performance
monitoring can be analyzed for I/O activity.
VASA benefits
For VMware vSphere users, the IBM Spectrum Control VASA provider improves
the ability to monitor and automate storage-related operations in VMware
environments.
A IBM Spectrum Control storage administrator can share certain IBM Spectrum
Control alerts and storage capabilities for resources that are mapped to a vCenter
server.
The IBM Spectrum Control VASA provider provides the underlying connectivity
for alerts and information to be shared.
The IBM Spectrum Control VASA provider provides the underlying connectivity,
and is automatically deployed and running after a IBM Spectrum Control
installation. You must register a IBM Spectrum Control server to view its
information in vCenter storage reports and views.
You can use the vSphere Web Client extension to provision storage capacity on
storage systems that are monitored by IBM Spectrum Control. You can provision
file and block storage and use the service classes and capacity pools that you
create in IBM Spectrum Control. Additionally, you can choose to create data stores
on your storage volumes.
You can use the vSphere Web Client extension to view information about the
storage systems that are monitored by IBM Spectrum Control. You can view the
mapping of your virtual storage resources to storage systems that are monitored by
IBM Spectrum Control. You can view metrics for your storage systems. You can
also view information about the fabric that is connected to a storage adapter. From
the storage reports, you can click links to open the resources in the IBM Spectrum
Control GUI.
The locales that are supported by the vSphere Web Client extension for IBM
Spectrum Control depend on the vSphere support. In vSphere 5.x, the following
locales are supported:
v English: en_US
v German: de_DE
v Japanese: ja_JP
v Simplified Chinese: zh_CN
v French: fr_FR
v Korean: ko_KR
When a locale does not have a translated version, the vSphere Web Client
extension is displayed in English, which is the default language.
Related concepts:
“Provisioning storage with the vSphere Web Client extension” on page 216
You can use the vSphere Web Client extension for IBM Spectrum Control to
manage and monitor your virtual environment and storage devices.
Related information:
Reporting in the stand-alone GUI
Use reports to view detailed information about the storage resources in your
environment. These reports are organized into different types and categories and
provide both summary and detailed information depending on your needs.
Alerts
Determining when and how you are alerted to configuration and performance
conditions within your storage environment is important to helping you maintain
and administer storage resources. Many conditions can trigger alerts. You can set
up IBM Spectrum Control so that it examines the attributes, capacity, and
performance of a resource and notifies you when changes or violations are
detected.
Conditions that generate alerts are detected during data collection and event
processing. For some storage systems such as IBM Spectrum Accelerate and the
XIV, events are polled every minute from the resource
For other resources, events are subscription-based, where the resource itself or a
data source such as a CIM agent sends the events to IBM Spectrum Control when
conditions change on the resource. Examples of storage systems that use
subscription-based event processing include SAN Volume Controller, Storwize
V7000, Storwize V7000 Unified, FlashSystem V840, and FlashSystem V9000. For
these storage systems, a probe is automatically run when many events are received
from the storage system in a short time period. To avoid performance bottlenecks,
probes are run only every 20 minutes.
The conditions that trigger alert notifications depend on the type of resource that
you are monitoring. In general, the following types of conditions can trigger alerts:
v An attribute or configuration of a resource changed
v The capacity of a resource fell outside a specified range
v The performance of a resource fell outside a specified range
For example, you can use performance thresholds to be notified when the total I/O
rate for storage systems falls outside a specified range. This information can help
you identify areas in your storage infrastructure that are over used or under used.
IBM Spectrum Control provides many metrics for measuring performance and
determining violations of the thresholds that you specify.
You can also use the optional Cognos Business Intelligence reporting tool to view
predefined reports and create custom reports about the resources managed by IBM
Spectrum Control. You access reports from the IBM Spectrum Control GUI, and
work with the reports in the Cognos BI reporting tool. Tivoli Common Reporting
provides the Cognos BI tool for IBM Spectrum Control reports.
You can use the Cognos BI reporting tool to view over 70 predefined reports about
the capacity and performance of your resources in Tivoli Common Reporting.
Charts are automatically generated for most of the predefined reports. Depending
on the type of resource, the charts show statistics for space usage, workload
activity, bandwidth percentage, and other statistics.
You can schedule reports and specify to create the report output in HTML, PDF,
and other formats. You can also configure reports to save the report output to your
local file system, and to send reports as email attachments.
You must collect information about your environment before you can use reports
to view details about the storage resources in it. You can use monitoring jobs in
IBM Spectrum Control such as probes and performance monitors to gather
comprehensive information and statistics about your storage resources.
Decimal units such as kilobyte (KB), megabyte (MB), and gigabyte (GB) are
commonly used to express the size of data. Binary units of measurement include
kibibyte (KiB), mebibyte (MiB), and gibibyte (GiB). Table 8 compares the names,
symbols, and values of decimal and binary units.
Table 8. Comparison of binary and decimal units and values
Binary Decimal
Value (base Value (base
Name Symbol 2) Name Symbol 10)
kibibyte KiB 210 kilobyte KB 103
mebibyte MiB 220 megabyte MB 106
gibibyte GiB 230 gigabyte GB 109
tebibyte TiB 240 terabyte TB 1012
pebibyte PiB 250 petabyte PB 1015
exbibyte EiB 260 exabyte EB 1018
In general, IBM Spectrum Control uses base 2 values for memory and disk space
values, and base 10 values for space on physical hard drives.
Table 9 shows the percentage difference between decimal and binary values across
a range of data sizes.
Table 9. Percentage difference between decimal and binary units
Binary equivalent of
Decimal value decimal value Difference
100 kilobytes (KB) 97.65 kibibytes (KiB) 2.35%
100 megabytes (MB) 95.36 mebibytes (MiB) 4.64%
100 gigabytes (GB) 93.13 gibibytes (GiB) 6.87%
100 terabytes (TB) 90.94 tebibytes (TiB) 9.06%
100 petabytes (PB) 88.81 pebibytes (PiB) 11.19%
100 exabytes (EB) 86.73 exbibytes (EiB) 13.27%
Role-based authorization
Roles determine the functions that are available to users of IBM Spectrum Control.
When a user ID is authenticated to IBM Spectrum Control through the GUI, CLI,
or APIs, membership in an operating system or LDAP group determines the
authorization level of the user.
In Version 5.2, the roles that were previously defined in IBM Spectrum Control
were consolidated into a smaller set of roles. The following table shows how the
roles in versions earlier than 5.2 are mapped to the current set of roles:
Table 10. How roles in previous versions of IBM Spectrum Control are mapped to the roles
in version 5.2 and later
Roles in previous Roles in version 5.2 and
versions later Authorization level
Superuser Administrator This role has full access to all monitoring
and administrative functions. At least one
Productivity Center group must have the Administrator role.
administrator Note: When IBM Spectrum Control is
first installed, the following operating
Disk administrator system groups are assigned the
Administrator role:
Fabric administrator
v Windows: Administrators
Data administrator v UNIX and Linux: root
Tape administrator v AIX: system
Tips:
v To determine the role of the user who is logged in, click the user icon in the
upper-right corner of any page in the GUI.
v If a user belongs to multiple groups and the groups have different roles, the role
with the highest level of authorization is granted to the user. For example, if a
user belongs to a group that is assigned the Administrator role and also belongs
to a group that is assigned a Monitor role, the user is granted the authorization
of the Administrator role.
v If a user is not a member of a group that is assigned a IBM Spectrum Control
role, no access is granted to that user.
v If you have been assigned the Monitor role, you can only open and view logs
from the Data Collection page for the selected resource.
v The IBM Spectrum Control installation program adds the administrator, external
application, and monitor roles to the IBM Spectrum Control installation user.
Information that you can view about a fabric includes the following properties:
v The fabric type
v The number of physical and virtual switches in the fabric
v The number of ports that are on all the switches in the fabric
v The number of switch ports that are online and connected to other ports in a
fabric
v The name of the principal switch of the fabric
Information that you can view about a switch includes the following properties:
v The number of ports on a switch
v The number of ports that are connected to a storage resource
v The name of the fabric where a switch is a member
v The name of the vendor or manufacturer for a switch
From the Details page of a fabric, you can open the Zone Sets page to view
information about the zone sets on the fabric, and to identify which is the active
zone set.
You can enable automatic zoning in the GUI. When automatic zoning is enabled,
IBM Spectrum Control creates new zones during provisioning if new zones are
needed to connect the storage system with the server. When you set the zoning
policy, you can specify whether zone changes from automatic zoning are made to
the active zone set, or to a new inactive active zone set.
Ports and devices in a zone are called zone members. A zone can contain one or
more zone members. Ports that are members of a zone can communicate with each
other, but they are isolated from ports in other zones. Devices, however, can belong
to more than one zone. A zone alias is a collection of zone members. A zone alias
can be added to one or more zones.
Zoning supports the use of aliases, which are meaningful names assigned to
devices. An alias can also be a group of devices that are managed together to make
zoning easier.
A default zone is a group of devices that are not members of the active zone set.
These can communicate with each other but not with members of any other zone.
Default zoning is enabled by default. You can use a switch element manager to
configure the Default Zone option to enable or disable the default zone
independently of the active zone set.
Note:
1. If the default zone is disabled, devices that are not members of the active zone
set cannot communicate.
2. If the default zone is disabled and no zone set is active, no devices can
communicate.
3. If default zoning is enabled, deactivating the active zone set makes all devices
members of the default zone. If default zoning is disabled, all communication
stops.
4. If you activate one zone set while another zone set is active, the currently
active zone set is deactivated.
5. If your EFC Manager manages multiple fabrics, ensure that you have the
correct zone set for the fabric you are currently updating.
You can view zones in SANs using the topology viewer console. Fabric Manager
lets you view zone membership.
Note: Certain types of switches and the types of agents configured can affect the
zoning operations that you can perform.
To see a list of supported switches and their capabilities, default values, ranges,
and possible effects, go to http://www.ibm.com/support/
docview.wss?uid=swg27027300.
Cisco switches support virtual SANs (VSANs), which is the logical partitioning of
a fabric into multiple fabrics. The overall network is referred to as the physical
infrastructure, and the logical fabrics are the VSANs. Fabric Manager provides
basic zone discovery for the Cisco MDS 9000 series of devices using the FC-GS-3
protocol.
Brocade switches support some non-standard zones such as quick loop zones,
fabric assist zones, and protocol zones. If the switch configurations have these
zones already defined, Fabric Manager preserves them and does not modify them
in any way. If they are part of a zone set that is active at some time, the devices
that are part of such zones that are also online are displayed in the topology Zone
View.
You can create, change, and delete non-standard zones by using the Brocade switch
management application.
Note: IBM Spectrum Control allows you to add empty zones to an inactive zone
definition. Activation of a zone set containing empty zones may still fail if the
switch does not support empty zones in active zone definitions.
Agents
The IBM Spectrum Control uses agents to gather data: Common Information
Model (CIM) agents, Storage Resource agents, and SNMP agents.
The CIM agent enables communication between the storage device and IBM
Spectrum Control. Commands and responses are transmitted between IBM
Spectrum Control and the CIM agent using an XML transport layer. The CIM agent
to storage device layer uses a vendor-specific proprietary interface.
The CIM agent usually must be installed and configured, so that it can identify the
storage devices with which it communicates. Some storage devices, such as fabric
switches, contain embedded CIM agents and so do not require that CIM agents be
installed. In these cases, IBM Spectrum Control must be configured to point
directly to the storage devices that contain the embedded CIM agents.
CIM agents can be referred to as SMI-S providers, CIM proxy agents, and CIMOM
agents. CIM agents can be embedded in the device or installed on a separate
computer.
Note:
v Do not install multiple CIM agents on a single computer because of port
conflicts.
v Do not install a CIM agent on the system where a IBM Spectrum Control server
component is installed.
You must deploy Storage Resource agents on resources where you want to gather
the following information:
v Asset information
v File and file system attributes
v Network-attached storage (NAS) device information
v Topology information
Tip: You can also monitor servers without deploying a Storage Resource agent.
When you add an agentless server, IBM Spectrum Control correlates information
about that server with the known host connections on monitored resources. If a
match is made between the server and a monitored resource, you can view
topology information and the capacity and performance of the storage that is
assigned to that server. For more information about when to deploy a Storage
Resource agent or add an agentless server, see “Adding servers” on page 91.
SNMP agents
An SNMP agent, also called an out-of-band agent, is software that runs on a
switch. IBM Spectrum Control uses SNMP to retrieve information about the switch
and the fabric that the switch is a member of.
Be sure that your SNMP agents point to each switch in the Storage Area Network
(SAN) that you want to manage.
IBM Spectrum Control uses SNMPv3 (preferred) or SNMPv1 to probe switches and
fabrics, and uses SNMPv2 or SNMPv3 to collect performance data. Some switches
are configured to use SNMPv3 by default.
IBM Tivoli Monitoring monitors and manages system and network applications on
a variety of operating systems, tracks the availability and performance of your
enterprise system, and provides reports to track trends and troubleshoot problems.
The IBM Spectrum Control Monitoring Agent participates in that environment.
For performance reasons, install the IBM Spectrum Control server on a separate
system from the IBM Tivoli Monitoring server. You can install the IBM Spectrum
Control Monitoring agent on any system you want to monitor.
Before using the IBM Spectrum Control Monitoring Agent, you must have IBM
Tivoli Enterprise Monitoring Server installed. For information about the IBM Tivoli
Enterprise Monitoring Server, see http://www.ibm.com/support/
knowledgecenter/SSTFXA_6.2.1/com.ibm.itm.doc_6.2.1/welcome.htm.
For information about installing IBM Tivoli Monitoring, see the Quick Start Guide
at http://www.ibm.com/support/knowledgecenter/SSTFXA_6.2.0.1/
com.ibm.itm.doc/GI11-8058-00.htm.
To use the IBM Spectrum Control Monitoring Agent, install this agent on the
system you want to monitor.
To view the type of reports that are displayed by the IBM Spectrum Control
Monitoring Agent, see http://www.ibm.com/support/knowledgecenter/
SS5R93_5.2.9/com.ibm.spectrum.sc.doc/fqz0_c_using_tpcma.html.
The provided scenarios set out situations that can be solved using IBM Spectrum
Control. When using these scenarios you should remember the following:
v The scenarios are intended to be step-by-step instructions that you follow to
complete a specific job. Each scenario contains multiple tasks that must be
followed in the order given.
v Specific values are given in the scenarios, such as user name, IP Address, probe
name, and so forth. These are for illustration purposes only and you must
replace them with values appropriate for your system.
v The scenarios do not provide in-depth conceptual information about the tasks.
See the appropriate topics in the IBM Spectrum Control Knowledge Center for
more information about the concepts behind the tasks.
v You will complete a scenario successfully if you follow the instructions correctly
and your system performs as expected.
You can optimize the placement of volumes on the following storage virtualizers:
v SAN Volume Controller
v Storwize V7000
v Storwize V7000 Unified block storage
Learn more: For information about the components that can be used with IBM
Spectrum Control Version 5.2 (or later), see IBM Spectrum Control
interoperability matrix at http://www.ibm.com/support/
docview.wss?uid=swg21386446.
When you run the analysis to balance pools, you optimize storage performance by
redistributing volume workloads across pools on the same tier.
With run the tiering analysis, you optimize storage performance by specifying
thresholds to move volumes to higher and lower tiers .
Related tasks:
“Optimizing storage tiering” on page 219
To optimize the placement of volumes on storage tiers, analyze the tiering of
volumes in your storage environment.
The pools that you want to analyze are on a SAN Volume Controller with two
DS8000 back-end storage systems.
If the activity deviation percentage of the pool exceeds the threshold set for the
pool, which is > 10 %, the pool is identified as a candidate for balancing. If the
activity deviation percentage of the pool lies within the threshold range set for the
pool, which is < −10 % to > +10 %, the pool is considered to be balanced.
Tip: On the Pools page, the activity level of the pool is shown in the Activity
column. The difference between the activity level of the pool and all of the other
pools on the same tier and storage system is shown in the Activity Deviation (%)
column.
Tip: Examine the activity deviation percentage values for the pools. Select
pools with low and high activity levels on each of the tiers that you want to
balance so that the volumes can be moved from high-activity pools to
low-activity pools.
3. Right-click the pools on the tiers that you want to balance and then click
Balance Pools.
4. Specify the number of days for estimating the activity of the pools.
5. Click Analyze.
Chapter 4. Scenarios 61
The pools that you want to analyze are on a SAN Volume Controller with two
DS8000 storage systems. The pools on the storage virtualizer are assigned to tier 1,
tier 2, and tier 3.
You want volumes with the highest workloads in tier 1 pools and you want
volumes with low workloads in tier 2 or tier 3 pools. To tier your storage, you
enter two I/O rate thresholds to generate recommendations to re-tier the volumes.
To ensure that the pools that are selected as destination pools for the volumes can
handle the additional workload, you specify the maximum I/O rates for pools on
each tier of storage. Only the pools with I/O rates below the maximum I/O rate
can be selected as destination pools for the volumes.
Collocating volumes
In this scenario, you want to minimize the exposure of servers to multiple
back-end storage systems by collocating volumes that are assigned to the same
hypervisor or server. You can enforce the collocation of volumes when you enter
the criteria for analyzing tiering and balancing pools.
To ensure that volumes in the same storage pool that are assigned to the same
server or hypervisor are kept together, you want to enforce the collocation of
volumes. By enforcing the collocation of volumes, you prevent the placement of
related volumes in destination pools that might be on multiple back-end storage
systems.
Multiple host connections to the same hypervisor or server: If the volumes in the
source pool that are assigned to the same hypervisor or server are assigned to
different host connections, the collocation of the volumes is affected. In such cases,
if volumes require optimization, the volumes that are assigned to the same host
connection are kept together. To view information about the host connection for the
volume, right-click the volume, select View Details, and then click the Host
Connections tab.
1. From the Storage menu, click Pools.
2. Right-click the pools that you want to analyze, and then click Analyze Tiering.
3. Select the target storage pools.
4. On the Optimize the Placement of Volumes page, ensure that Colocate volumes
is set to Yes.
Chapter 4. Scenarios 63
5. Click Analyze.
In the following scenario, you want to create a department model that monitors
the capacity and space usage of the Books Sales department, and these
subdepartments:
v Wholesale
v Retail
v Online
To monitor the capacity and space usage of the departments, you add the
applications that the department and its subdepartment use to each of the
subdepartments.
The department model that you create determines how you can view capacity
usage and space information. To view the total capacity and space usage of a
department regardless of the subdepartments that the department contains, you
create a department and add the applications and subcomponents to the
department.
If, however, you want to see the capacity and space usage of the department and
its subdepartments, you create a department hierarchy by adding subdepartments
to departments. You then add the applications and application subcomponents that
each subdepartment uses to the subdepartments. You can then view capacity and
space usage for the department and for the individual subdepartments.
To monitor the capacity and space usage of the departments in your business
organization, complete the following tasks:
v Create the Book Sales department.
v Create the Wholesale, Retail, and Online departments to represent the
subdepartments.
v Add the Wholesale, Retail, and Online as subdepartments to the Book Sales
department.
v Create the Book Sales DB application and the Wholesale Transactions, Retail
Transactions and Online Transactions applications to represent the
subcomponents that are used by the departments.
Different applications require different storage capabilities, and different levels of
performance and uptime. The storage requirements of the departments are
constantly growing and they need to modify their behaviors in a way that justifies
the cost of their actions concerning storage utilization. The data modeling of
storage resources using the application and department concept enables you to
plan and implement a chargeback system if necessary.
Related concepts:
“Departments” on page 178
View information about departments and structure the hierarchy to mirror your
business organization. Monitor the detailed information about capacity and space
usage that is collected for departments and subdepartments, and monitor the
performance of the applications and the application subcomponents that are added
to departments and subdepartments.
Related tasks:
“Creating departments” on page 180
To model the storage capacity that is consumed in a department for your business
environment, in accordance with other department and application members,
create departments for monitoring in IBM Spectrum Control.
Chapter 4. Scenarios 65
“Adding and creating subdepartments” on page 181
To further enhance your data modeling at the department level and to add to your
overall business hierarchy for monitoring, add an existing subdepartment or create
a new subdepartment.
“Viewing information about departments” on page 182
You can view detailed information about departments for use in storage capacity
monitoring and performance troubleshooting. You can view additional information
on the applications and subdepartments that are used to establish a hierarchal
business structure.
“Creating applications” on page 171
To monitor storage capacity, troubleshoot performance, and view storage area
network dependencies for applications, you can create applications for monitoring
in IBM Spectrum Control.
“Adding subcomponents” on page 175
You created a new application and a subcomponent, with their own set of
resources and added it to your business hierarchy. You now want to add another
level to your business hierarchy.
To monitor the capacity and space usage of a department, you create the
department and subdepartments, and you add the application subcomponents to
the subdepartments.
The sales department of the organization, Book Sales, has these subdepartments:
v Wholesale
v Retail
v Online
Although you can add applications and application subcomponents when you
create departments, it is easier and quicker to create the applications and
application subcomponents beforehand.
You want to know the total amount of storage space that the Book Sales
department uses, and you want to know the amount of space that each
subdepartment uses. To know how much space the Book Sales and its
subdepartments use, you must associate the department and its subdepartments
with the applications that they use. For example, the Book Sales department and
When you complete adding the departments and associating the departments with
the applications that are used by the departments, you can view the information
that is collected about the departments on the Departments page and on the details
page for the department.
You want to target what department and what storage resources might be
responsible for a change or a upward trend in significant storage usage. By
correctly classifying the department or departments you can properly plan to
archive or switch the storage within the organization.
Related concepts:
“Departments” on page 178
View information about departments and structure the hierarchy to mirror your
business organization. Monitor the detailed information about capacity and space
usage that is collected for departments and subdepartments, and monitor the
performance of the applications and the application subcomponents that are added
to departments and subdepartments.
Related tasks:
“Creating departments” on page 180
To model the storage capacity that is consumed in a department for your business
environment, in accordance with other department and application members,
create departments for monitoring in IBM Spectrum Control.
“Adding and creating subdepartments” on page 181
To further enhance your data modeling at the department level and to add to your
overall business hierarchy for monitoring, add an existing subdepartment or create
a new subdepartment.
“Viewing information about departments” on page 182
You can view detailed information about departments for use in storage capacity
monitoring and performance troubleshooting. You can view additional information
on the applications and subdepartments that are used to establish a hierarchal
business structure.
Chapter 4. Scenarios 67
“Creating applications” on page 171
To monitor storage capacity, troubleshoot performance, and view storage area
network dependencies for applications, you can create applications for monitoring
in IBM Spectrum Control.
“Adding subcomponents” on page 175
You created a new application and a subcomponent, with their own set of
resources and added it to your business hierarchy. You now want to add another
level to your business hierarchy.
You can create a simple application model, which consists of an application and
use a filter to associate the storage resources that the application uses with the
application. Alternatively, you can create a complex application model that
comprises an application and application subcomponents and then add filters to
associate the storage resources that each application subcomponent uses with each
of the subcomponents.
In the following scenario, you want to create an application model that monitors
the capacity, space usage, and performance of the Book Sales DB application. The
application model that you want to create comprises these application
subcomponents:
v Wholesale Transactions
v Retail Transactions
v Online Transactions
Chapter 4. Scenarios 69
You want to understand how capacity is trending for storage that is used by the
Book Sales DB application and the Wholesale Transaction, Retail Transactions and
Online Transactions subcomponents and the association the application has with
the Book Sales department and subdepartments.
The storage resources that are used by the application and that are used by each
subcomponent are associated with the application and its subcomponents. For
example, the storage resources are assigned as follows:
1. Create a database application called Book Sales DB and assign resources that
use the volumes on the IBM® Storwize V7000 with names that begin with
bksales for storing sales transactions.
2. Create the subcomponent applications named Wholesale Transaction, Retail
Transactions and Online Transactions.
3. Assign the volumes on the IBM Storwize V7000 with names that begin with
bksales_ws to the Wholesale Transactions subcomponent, which is used for
storing wholesale sales transactions.
4. Assign the volumes on the IBM Storwize V7000 with names that begin with
bksales_rt to the Retail Transactions subcomponent, which is used for storing
retail sales transactions.
5. Assign the volumes on the IBM Storwize V7000 with names that begin with
bksales_ol to the Online Transactions subcomponent, which is used for storing
online sales transactions.
Note: On the Create Filter page, you can specify a name pattern to determine
which volumes to include. For volumes, you can specify name patterns to
determine from which servers, storage systems, or pools the volumes are
selected. You can then click Preview to view the volumes that are selected for
inclusion in your application.
To monitor space usage for the Book Sales department and its subdepartments,
you associate the Book Sales DB application and the Wholesale, Retail, and Online
Transactions subcomponents of the application as follows:
v You associate the Book Sales DB application with the Book Sales department.
v You associate the Wholesale subdepartment with the Wholesale Transactions
subcomponent.
v You associate the Retail subdepartment with the Retail Transactions
subcomponent.
v You associate the Online subdepartment with the Online Transactions
subcomponent.
You plan to dedicate two storage pools to be used with vSphere. You want to
allow a vSphere user to provision storage by using the vSphere Web Client
extension for IBM Spectrum Control. You want to define the two storage pools as
the resources that the user can use.
1. Create a capacity pool that the vSphere user can provision from. Place the two
storage pools that you designated as provisioning targets for vSphere in the
capacity pool. To add storage pools to the capacity pool, follow the instructions
in “Adding resources to capacity pools” on page 200.
2. Create a service class and specify that the service class can be used to provision
storage only from the capacity pool. To create the service class, follow the
instructions in “Creating service classes” on page 194.
3. Create a user ID for the vSphere user and assign the External Application role
to that ID. To assign the role to the user, follow the instructions that are
provided in the product documentation at http://www.ibm.com/support/
Chapter 4. Scenarios 71
knowledgecenter/SS5R93_5.2.9/com.ibm.spectrum.sc.doc/
fqz0_t_associate_user_group_to_roles.html.
4. Associate the user with the service class. To associate the user with the service
class, follow the instructions in “Modifying service classes” on page 196.
When you complete these tasks, a vSphere user can provision storage by using the
vSphere Web Client extension, but they are limited to the service class that was
created. Because the service class is associated with the capacity pool that contains
your designated vSphere storage pools, you limited where the vSphere user can
provision data.
Related concepts:
“Cloud configuration” on page 37
To take advantage of the simplified provisioning and optimization capabilities that
are available by using the web-based GUI, some configuration is required.
Related tasks:
“Provisioning block storage” on page 216
Use the vSphere Web Client extension for IBM Spectrum Control to provision block
storage on IBM Spectrum Control. You can also have a data store created on the
storage volume.
“Provisioning file storage” on page 217
Use the vSphere Web Client extension for IBM Spectrum Control to provision file
storage on IBM Spectrum Control.
You want to view connectivity information for a switch port that has NPIV
connections.
1. In the menu bar, go to Network > Switches. Double-click the switch that you
want to view, or right-click the switch and click View Details.
Tip: Alternatively, in the menu bar, go to Network > Fabrics. Double-click the
fabric that you want to view, or right-click the fabric and click View Details. In
the Internal Resources section, click Switches. Double-click the switch that you
want to view, or right-click the switch and click View Details.
2. In the Internal Resources section, click Ports. You can view details about the
ports, including the number of NPIV connections.
3. In the Connected NPIV Ports column for the port that you want to view, click
the number of ports. You can view the following information about the NPIV
connections:
v In the Connected NPIV Ports tab, you can view details about the NPIV
connections, such as the port type and the name of the connected resource.
The port type can be N_Port (end node port) or NP_Port (proxy node port).
v In the Connectivity tab, you can view details about the physically connected
end-node port.
Chapter 4. Scenarios 73
74 IBM Spectrum Control: User's Guide
Chapter 5. Managing resources
Use IBM Spectrum Control to monitor and manage the resources and storage
infrastructure in an enterprise environment. In the GUI, you can view the
condition, capacity, performance, and relationships of storage resources.
Use the vSphere Web Client extension for IBM Spectrum Control to manage a
vSphere virtual storage environment. You can complete provisioning tasks and
view information about storage resources in the vSphere Web Client extension.
Adding resources
You must add resources to IBM Spectrum Control before you can collect data,
generate reports, and manage storage that is related to those resources.
Related concepts:
“Alerting and event processing” on page 111
Determining when and how you are alerted to configuration and performance
conditions within your storage environment is important to helping you maintain
and administer storage resources. Many conditions can trigger alerts. You can set
up IBM Spectrum Control so that it examines the attributes, capacity, and
performance of a resource and notifies you when changes or violations are
detected.
Related reference:
“Triggering conditions for alerts” on page 252
Define alerts so that IBM Spectrum Control automatically notifies you when certain
conditions or events are detected on monitored resources. Such conditions are the
triggering conditions for the alert. The specific conditions that can trigger alerts
depend on the type of resource that is being monitored.
Information about object storage systems includes information about their object
resources and related resources. Object resources are resources in a GPFS cluster,
such as accounts and containers, that enable the GPFS cluster to be used as an
object storage system.
Fabrics
Switches
Hypervisors
Inter-switch connections
Servers
Blades
Storage systems
Ports
NPV switches (Cisco
Zone sets switches in NPV mode and
Brocade switches in Access
Gateway mode)
Discovered ports
Hypervisors
The following table shows the internal resources and related resources that you can
monitor for hypervisors.
Table 12. Hypervisor resources that you can monitor.
Top-level resource icon Internal resources Related resources
Controllers Fabrics
Switches
Disks
Cluster
Data stores
VMDKs
Servers
A server is a computer or host that is connected to a network and provides an
access point to that network. If a server is part of a cluster, information about that
cluster is also available. You can monitor the following internal resources and
related resources for servers.
Disks Fabrics
Switches
Volume groups
Storage systems
Storage systems can be configured for block storage, file storage, a combination of
block and file storage, or a combination of file and object storage. The method that
a storage system uses for managing data determines the internal resources or
object resources that are monitored.
The following tables show the internal resources, object resources, and related
resources that you can monitor for block, file, and object storage systems.
I/O groups
Servers
Managed disks Switches
Modules
Virtualizer storage systems
, Nodes
GPFS clusters
Pools
Ports
RAID arrays
Volumes
Clusters Fabrics
Shares Hypervisors
Filesets Servers
Nodes
Pools
Snapshots
Quotas
Fabrics
Containers
GPFS clusters
Hypervisors
Servers
Switches
Switches
Blades Hypervisors
Logical switches
Servers
Parent switches
Storage systems
Ports
Switches
Discovered ports
Related tasks:
“Adding ESX and ESXi hypervisors” on page 88
Add ESX and ESXi hypervisors for monitoring by IBM Spectrum Control.
“Adding storage systems” on page 81
To monitor a storage system, configure a connection to the storage system and
schedule the collection of data.
“Adding fabrics and switches” on page 85
Add fabrics and switches for monitoring.
“Adding servers” on page 91
Add servers for monitoring. You can add a server by deploying a Storage Resource
agent, or you can add an agentless server.
The following roles are associated with the user names that IBM Spectrum Control
uses to log in to resources. Specify user names when you add a resource for
monitoring. These roles are different from IBM Spectrum Control roles, which are
assigned to users that log in to IBM Spectrum Control.
Table 18. Required roles for storage system and hypervisor users
Required role for
performance Required role for Required role for
Resource monitors probes provisioning
DS6000 Monitor role or Monitor role or Administrator,
greater greater Physical operator, or
DS8000 Logical operator
SAN Volume Monitor1 or Monitor Administrator
Controller Administrator
Storwize V7000
Unified (block
storage)
FlashSystem V840
Storwize V7000 Performance Monitor Administrator, or
Unified (file storage) monitoring is not Export Administrator
available + Storage
IBM SONAS Administrator. For
more information
about roles, see
IBM Knowledge
Center for IBM
SONAS.
IBM Spectrum Any role Any role Provisioning is not
Accelerate available
IBM Spectrum Scale Any role Root or non-root2 Provisioning is not
(file storage) available
You can add the following types of storage systems for monitoring:
SAN Volume Controller, IBM Storwize family, IBM FlashSystem V840 Enterprise
Performance Solution, and IBM FlashSystem V9000 storage systems run IBM
Spectrum Virtualize™ to virtualize their storage. In this documentation, IBM
Spectrum Virtualize is used to refer collectively to SAN Volume Controller,
Storwize, FlashSystem V840, and FlashSystem V9000 storage systems.
For a complete list of the versions of storage systems and CIM agents that you can
add, see IBM Spectrum Control interoperability matrix for storage systems at
http://www.ibm.com/support/docview.wss?uid=swg27039840.
1. To add a block storage system, go to Storage > Block Storage Systems. To add
a file storage system, go to Storage > File Storage Systems. To add an object
storage system, go to Storage > Object Storage Systems.
2. Click Add Storage System.
3. Click the icon for the type of storage system that you want to add.
The storage system is added for monitoring. A probe is automatically run to collect
status and asset information about the storage system.
Storage systems can be configured for block storage, file storage, a combination of
block and file storage, or a combination of file and object storage. The method that
a storage system uses for managing data determines the internal resources and
object resources that are monitored.
When the collection of data is complete, you can view status information and
capacity data about the storage system on the resource list page for the block, file,
or object storage system. For example, for block storage systems, you can view the
information on the Block Storage Systems page.
Enabling the default alerts for storage systems: To enable the default alerts for a
resource so that you are automatically notified when certain conditions are
Before you add the IBM Spectrum Scale storage system for monitoring, complete
this task.
To grant access to the user, make the following changes to the sudoers file on the
cluster node that is used for authentication:
v Add the set of administration commands that are required to monitor the
storage system.
v Associate the user with the set of administration commands.
1. Log on to the cluster node that is used for authentication with a user name that
has root privileges.
2. To edit the sudoers file, enter the following command:
visudo -f /etc/sudoers
3. Add the following command aliases to the sudoers file. The command aliases
contain the commands that the user must be able to issue to monitor the
storage system.
Important: Each command alias must be on a single line without line breaks.
Cmnd_Alias TPC_GPFS_MMCMD = /usr/lpp/mmfs/bin/mmsdrquery, /usr/lpp/mmfs/bin/mmlsconfig,
/usr/lpp/mmfs/bin/mmgetstate, /usr/lpp/mmfs/bin/mmlsnodeclass, /usr/lpp/mmfs/bin/mmlsfs,
/usr/lpp/mmfs/bin/mmdf, /usr/lpp/mmfs/bin/mmlsnsd, /usr/lpp/mmfs/bin/mmlsfileset,
/usr/lpp/mmfs/bin/, /usr/lpp/mmfs/bin/mmlsmount, /usr/lpp/mmfs/bin/mmlssnapshot,
/usr/lpp/mmfs/bin/mmrepquota
where user_name is the user name that you enter when you add the storage
system for monitoring.
The user that you added to the sudoers file can now monitor the IBM Spectrum
Scale storage system.
| To verify that the server can access the object services, complete these steps:
| 1. List the URLs for the Keystone and Swift services by running commands on a
| GPFS cluster node that is configured for object storage. Run the following
| commands with a user name that has root privileges:
| . ~/openrc
| openstack endpoint list
| 2. Ensure that the IBM Spectrum Control server can connect to the IP addresses
| and host names that are included in the Keystone and Swift services URLs. For
| example, the URL for the Keystone service might be http://
| gpfs420proto1:5000/v3. The IBM Spectrum Control server must be able to
| connect to the gpfs420proto1 host name.
To collect performance data, you must first configure the IBM Spectrum Scale
performance monitoring tool on the GPFS cluster. Then, use the IBM Spectrum
Control GUI to schedule the collection of performance data.
1. Configure the sensor component of the IBM Spectrum Scale performance
monitoring tool by editing the /opt/IBM/zimon/ZIMonSensors.cfg file on the
sensor nodes.
Set the host property in the collectors section of the file to the GPFS cluster
node where the collector component is running. The host property must be set
to one of the following options:
v An IP address that can be reached by the IBM Spectrum Control server
v A host name that resolves to an IP address that is reachable by the IBM
Spectrum Control server
2. Enable the following sensors on each node for which you want to collect
performance data: CPU, Memory, GPFSNode, GPFSFileSystem.
3. Start the collector component of the performance monitoring tool on a single
GPFS cluster node. The collector can run on any node.
4. Start the sensor component of the performance monitoring tool on each node
for which you want to collect performance data. By default in IBM Spectrum
Scale version 4.1.1, the sensors are started only on protocol nodes.
5. To receive data from the performance monitoring tool, ensure that the IBM
Spectrum Control server can connect to port 9084 on the GPFS cluster node
where the collector component is running.
6. Schedule the collection of performance data by creating a performance monitor
in the IBM Spectrum Control GUI. You can create performance monitors in the
GUI when you add resources for monitoring or you can create them later.
A performance monitor is created for the IBM Spectrum Scale storage system. If a
successful probe run is completed for the resource, the performance monitor runs
according to the defined interval.
Before you add the IBM Spectrum Scale object storage system for monitoring,
ensure that the user name that you use to monitor the storage system has access to
object storage accounts.
Tip: The terms "account" and "project" mean the same thing. Swift, the OpenStack
object storage service, uses the term "account" and Keystone, the OpenStack
identity service, uses the term "project."
1. Set the object storage account and the domain for the user. By default, the
domain is set to Default and cannot be modified after you create the user
account. Choose one of the following actions:
a. To set the account and domain when you create a user account, use the
following command:
openstack user create --domain domainname --project projectname
--password Password username
b. To set the account and the domain for an existing user name, use the
following command:
openstack user set --project projectname username
2. Assign the admin role for an object storage account to the user name. Use the
following command:
openstack role add --user username --project projectname admin
3. To monitor all accounts on the object storage system, assign to the user name
the role that is defined in the reseller_admin_role configuration option in the
Swift proxy server. The default value for the reseller_admin_role option is
ResellerAdmin. For example, use the following command:
openstack role add --user username --project projectname ResellerAdmin
To learn more about configuring and assigning user roles in OpenStack, see
http://docs.openstack.org/user-guide-admin/
manage_projects_users_and_roles.html.
For a Cisco switch to successfully receive and respond to queries from IBM
Spectrum Control, the following basic requirements must be met:
In the web-based GUI, you can add switches and fabrics for monitoring at the
same time. You can add the following types of switches:
v Brocade
v Cisco
v Other fabric vendors
For a complete list of the switches and their versions that you can add, see the
switches and directors information in the IBM Spectrum Control interoperability
matrix at http://www.ibm.com/support/docview.wss?uid=swg21386446.
Help tips in the GUI: To view descriptions of the information that you must enter
for a fabric or switch, hover the mouse pointer over the related help icons in
the wizard.
1. In the menu bar, go to Network > Switches.
2. Click Add Switch.
3. Select the vendor: Brocade, Cisco or Other.
4. Specify how you want to discover the switches and the fabrics that are
connected to the switches. For Cisco switches and fabrics, you must use SNMP
agents. For Brocade and other vendors, you can use the vendor's CIM support
as an alternative to SNMP.
5. Specify the display name and location of the switches and fabrics that are
discovered. For switches that were discovered through a CIM agent, you can
also select to monitor them through SNMP. When you add a Brocade director
switch as an SNMP data source, use the IP address or host name of the chassis,
rather than the IP address or host name of the primary or secondary core
routing blades.
6. Schedule data collection for the switches and fabric. The type of resource
determines the data collection jobs that you can schedule:
v Fabrics: probes
v Switches: probes, performance monitors
Probes collect status and asset information. Performance monitors collect
metrics that measure performance.
7. Complete the wizard.
When the collection of data is complete, you can view status information about the
fabric or switch on the Fabrics page or Switches page.
The vendors of switches can help you determine which agents to use.
Table 19. Agent types for switch and fabric functions.
1
Function Brocade Cisco Other
CIM agent or SNMP SNMP agent Other fabric vendor switches
Monitor performance agent cannot be used for
performance monitoring.
Recommended: CIM CIM agent or SNMP agent
Collect information agent SNMP agent
about switches and
switch ports Also supported: SNMP
agent
Recommended: CIM CIM agent or SNMP agent
Collect information agent SNMP agent
about topology
connectivity Also supported: SNMP
agent
Adding hypervisors
You can add hypervisors for monitoring by IBM Spectrum Control. Hypervisors
include VMware vSphere data sources such as ESX and ESXi, and vCenter Server
systems. When you add vSphere data sources, you can then collect data, generate
reports, and manage storage that is related to those resources.
To add a hypervisor, you specify connection information for the ESX or ESXi data
source. You can add multiple hypervisors by specifying connection information for
a vCenter Server system.
When the collection of data is complete, you can view status information and
capacity data about the hypervisor on the Hypervisors page.
Enabling the default alerts for hypervisors: To enable the default alerts for a
resource so that you are automatically notified when certain conditions are
detected, you must view the alert definitions for that resource. For example, to
view the alert definitions for a hypervisor, go to Servers > Hypervisors, right-click
a hypervisor, and select Edit Alert Definitions. The default alerts are automatically
enabled for the hypervisor after you access the Edit Alert Definitions page.
Related tasks:
“Adding vCenter Server systems” on page 90
For IBM Spectrum Control to monitor multiple hypervisors, you must first add a
vCenter Server system.
Determine if the user name that you specified for a VMware data source has
permission to browse through the data stores on a hypervisor.
When you add a VMware data source in IBM Spectrum Control, the user name
that you specify must have permission to browse through the data stores on
VMware. IBM Spectrum Control must browse through the data stores to collect
information from the hypervisors. However, the "Read Only" role as defined by
VMware does not allow IBM Spectrum Control to browse the data stores. You can
use the "Virtual Machine Power User" role if you do not want to use the
Administrator role, or you can create a custom role with the required permissions.
To verify that a VMware user is assigned the correct role and privileges to monitor
VMware data sources, follow these steps:
1. Ensure that the user role has the required VMware datastore permissions by
completing the following steps:
a. Connect the vSphere Web Client to the VMware data source. The data
source can be an ESX server, a vCenter Server Appliance, or a vCenter
Server.
b. From the Inventories view, select Hosts and Clusters.
c. Select a host, and click the Related Objects tab.
d. View the datastores by clicking the Datastores tab.
For more information about VMware user roles, go to the VMware documentation
center and search for vSphere users and permissions.
When you add vCenter Server version 5.1 or later, you can deploy the vSphere
Web Client extension for IBM Spectrum Control and register the latter as a VASA
provider. You can then provision storage, view reports, and publish alerts in the
vSphere Web Client about storage that is monitored by IBM Spectrum Control.
After a vCenter Server system is added for monitoring, probes collect status and
asset information about its hypervisors.
When the collection of data is complete, you can view status information and
capacity data about the hypervisors on the Hypervisors page.
Enabling the default alerts for hypervisors: To enable the default alerts for a
resource so that you are automatically notified when certain conditions are
Adding servers
Add servers for monitoring. You can add a server by deploying a Storage Resource
agent, or you can add an agentless server.
Choose which type of server to add and which method you use to add the server.
You can use several methods to add one or more servers for monitoring. Use the
following information to determine the method that best meets the needs of your
environment:
Manually
Add one server by manually entering configuration information.
In IBM Spectrum Control, you can view the connectivity of all your top-level
resources in a SAN environment. These resources include servers, hypervisors,
fabrics, switches, and storage systems. In previous releases, to get a complete view
of the connectivity between servers and other top-level resources, you were
required to deploy Storage Resource agents on all of those servers. However, in
some environments it was not always possible to deploy Storage Resource agents,
and thus a complete view of all resource relationships was not available. In IBM
Spectrum Control V5.2 and later, you can add servers without deploying Storage
Resource agents and still view the overall connectivity and performance of SAN
storage that is assigned to those servers.
When you add an agentless server for monitoring and specify its worldwide port
names, IBM Spectrum Control automatically correlates that server with the ports
on known host connections. If matches are found between the server and host
connections on monitored storage systems, the following information can be
determined:
v The amount of SAN storage that is assigned to the server.
v The storage systems that are mapping volumes to the server.
v The relationships between the server and other monitored resources.
If performance monitors collect data about the related storage systems, you can
also view the performance of the internal resources that are directly associated
with storage that is assigned to the server. For example, if a SAN Volume
Controller maps two volumes to the server, you can view the performance of those
volumes and the related managed disks.
When you add an agentless server, enter its IP address or host name and other
optional information such as its OS type, location, and ports. IBM Spectrum
Control uses this information to correlate the agentless server with the storage
systems, fabrics, and switches that are being monitored. For example, the ports that
you enter for an agentless server are compared to the ports on host connections for
Use any of the following methods to add agentless servers for monitoring:
v Add a server by manually entering its information.
v Add a server from a host connection on a monitored storage system.
v Add a server from a discovered port that is connected to a monitored switch.
v Add a server from a discovered port that is connected to a monitored fabric.
Add an agentless server by manually entering its information.
1. In the menu bar, go to Servers > Servers.
2. Click Add Server.
3. Ensure that the Deploy an agent for full server monitoring check box
is cleared.
4. Select a method for adding a server and complete the steps.
Add a server from a host connection on a monitored storage system.
Use this method when you want to configure a host connection to
represent a physical server. When you select a host connection, you are
specifying the internal resources (volumes, ports) that belong to that server
from the perspective of the related storage system.
To add an agentless server that is based on a known host connection,
complete the following steps:
1. In the menu bar, go to Storage > Block Storage Systems.
2. Right-click a storage system and select View Details.
3. Click Host Connections to view a list of host connections that are
mapped to a storage system.
4. Right-click a host connection and select Add Server. This action is not
available under the following conditions:
v A Storage Resource agent or agentless server is already associated
with the host connection.
v The host type of the host connection is configured for SAN Volume
Controller.
5. Enter information about the server and assign ports.
6. Complete the wizard.
Add a server from a discovered port that is connected to a monitored switch.
Discovered ports are ports on resources that are not monitored by IBM
Spectrum Control but are visible to a monitored switch. To add an
agentless server that is based on a discovered port, complete the following
steps:
1. In the menu bar, go to Network > Switches.
2. Right-click a switch and select View Details.
3. Click Discovered Ports to view a list of unmanaged ports that are
visible to the switch.
4. Right-click an unknown port and select Add Server.
5. Enter information about the server and assign ports.
6. Complete the wizard.
Help tips in the GUI: To view descriptions of the information that you must enter
for a server, hover the mouse pointer over the related help icons in the wizard.
Restrictions:
v The host name or IP address of an agentless server can be up to 24 characters in
length and must contain valid characters. You can enter the following characters
when you enter a host name or IP address:
– A through Z (uppercase characters)
– a through z (lowercase characters)
– 0 through 9 (numeric characters)
– Special characters: - (minus) . (period)
v If the location of an agentless server exceeds 64 characters, it is truncated when
the server is added. To avoid the truncation, ensure that the location value for
an agentless server is equal to or less than 64 characters in length.
File List:
The input file for importing server information can contain entries for one or more
servers. Each line in the file represents a server that you want to add. Information
about each server must be organized in the following format:
host name or IP address,OS type,machine type,location,WWPN
where:
v host name or IP address is required for each server entry. An IP address can be
in an IPv4 or IPv6 format. You must include a host name or IP address for each
server that you want to add. The host name or IP address can be up to 24
characters in length and must contain valid characters. You can enter the
following characters when you enter a host name or IP address:
Tip: If you add many servers in the same input file, the adding process might
require some time to complete. To run the process in the background, click Close
on the Add Server window. If you remain on the Servers page, a message is
displayed when the servers are added. If you leave the Servers page during
processing, a message is not displayed. To confirm that the servers were added,
you must go back to the Servers page and refresh the list.
Restrictions
Keep in mind the following restrictions when you import server information from
an input file:
v Each line in the file represents one server.
v Enter a "#" at the beginning of a line to comment out a line. The server on that
line is not added when the list is imported in the add server wizard.
v If there are syntax problems in the file, then none of the servers in the file are
added.
For each installation of IBM Spectrum Control, you can deploy only one Storage
Resource agent on each server. If you attempt to deploy additional Storage
Resource agents on a server, the deployments fail.
1. In the menu bar, go to Servers > Servers.
2. Click Add Server.
3. Select Deploy an agent for full server monitoring.
4. Select a method for adding a server. You can choose one of the following
methods:
v Add a server by manually entering information about the server and the
Storage Resource agent.
v Add one or more servers by importing configuration information from a
comma-delimited file.
5. On the Deploy Agent page, configure deployment information for the Storage
Resource agents.
If you add multiple servers with different operating systems, separate
configuration pages are displayed for agents that are deployed on Windows
servers and agents that are deployed on UNIX servers.
6. On the Configure page, schedule the deployment of the Storage Resource
agents.
If you are deploying agents on multiple servers, a time span is calculated
during which the agents are deployed. The agents are deployed at regular
intervals during the time span to avoid excessive load on the IBM Spectrum
Control server.
7. Schedule the time and frequency that probes are run for the servers.
If you add multiple servers, a time span is calculated during which the servers
are probed.
8. To add the servers, click Finish.
A probe is automatically run for a server after the agent is successfully deployed.
Use Agent State on the Servers page to monitor the status of the agent
deployment.
Enabling the default alerts for servers: To enable the default alerts for a resource
so that you are automatically notified when certain conditions are detected, you
must view the alert definitions for that resource. For example, to view the alert
definitions for a server, go to Servers > Servers, right-click a server, and select Edit
Alert Definitions. The default alerts for the server are automatically enabled after
you access the Edit Alert Definitions page.
File List:
Add one or more servers with Storage Resource agents by importing the
configuration information from a comma-delimited file.
The web-based GUI guides you through the following steps for adding servers:
v Select the input file.
v Configure deployment information.
v Schedule the agent deployment and data collection for the servers.
where:
v host name or IP address is required for each server entry. An IP address can be
in an IPv4 or IPv6 format. A host name or IP address can contain the following
characters or symbols:
– A - Z (uppercase characters)
– a - z (lowercase characters)
– 0 - 9 (numeric characters)
– Symbols: - . : _
v OS type is required and represents the operating system of the server. The OS
type for a server must be one of the following values:
– Windows
– Linux
– AIX
– Solaris
– HP-UX
v location is optional and represents the physical location of the server. The
location value can be up to 64 characters in length. If the length exceeds 64
characters, the location value is truncated when the server is added.
v custom tag 1, custom tag 2, and custom tag 3 are optional and represent any
additional information that you want to provide about the server. The custom
tag values can be up to 64 characters in length. If the length exceeds 64
characters, the custom tag value is truncated when the server is added.
Tip: The custom tags can be displayed on the Servers page or can be included
as report columns when you generate reports for the server.
Example
host1,Windows,San Jose,Accounting department
host5,Linux,London,Finance department
198.51.100.22,HP-UX,,Computing department
2001:DB8:0:0:0:0:0:0,Windows,Tokyo
Tips:
v If the comma-delimited file contains entries for multiple servers, it might take
some time to add the servers. To confirm that the servers are added, check the
Status column on the Servers page.
v To comment out a line, enter a "#" at the beginning of the line. The server on
that line is not added when the list is imported.
Example:
# host1,Windows,San Jose,Accounting department
v If there are syntax problems in the file, none of the servers in the file are added.
Note: To remove a Cisco fabric, you must remove all the switches in that
fabric. The Cisco fabric is then automatically removed.
3. Click Remove to confirm that you want to remove the resource.
Collecting data
Determining the data that you want to gather about storage resources is critical to
helping you implement a storage management strategy. IBM Spectrum Control
provides different jobs for collecting data. When you determine the types of data
that you want to collect about resources, schedule the corresponding data
collection jobs for those resources.
Table 21. Data collection jobs, resources, and related tasks
Data collection job Resources Related tasks
Storage systems v Schedule a probe when
Probe Use probes to collect
Servers you add a resource for
status, asset,
Hypervisors monitoring.
configuration, and
Fabrics
capacity information v Modify the schedule for a
Switches
about resources. probe at any time on the
list and details pages for a
resource. For example, to
modify the schedule for a
block storage system, go to
the Block Storage Systems
page or the details page
for the block storage
system.
Learn more...
Learn more...
Creating probes
Probes are data collection jobs that collect status and asset information about your
storage resources. You can create probes when you add resources for monitoring or
after you add the resources for monitoring.
You can create probes for one or more resources at the same time.
1. To schedule a probe for a resource, choose one of the following options from
the menu bar
Tip: For switches, probes also collect asset and topology information about the
fabrics that include those switches.
2. Locate the resources that you want to probe.
3. Select the resource rows and click Actions > Data Collection > Schedule.
4. On the Data Collection Schedule window, set the probe to Enabled.
5. Enter the time of the data collection, select the frequency, and then click Save.
If you are scheduling probes for multiple resources, a time span is calculated
during which the resources are probed. The resources are probed at different
times during the time span to avoid excessive load on the server. A message is
displayed that confirms that probe schedules are created for the resources.
To verify that a probe is running for a resource, use the resource list page in the
web-based GUI.
1. From the menu bar, go to a resource list page for a resource type. For example,
to verify that a probe is running for a storage system, go to Storage and select
the type of storage system you want to monitor.
2. Locate the resource that you want to check.
3. View the Probe Status column. A value of Successful or Running indicates that
the probe is collecting asset and status information about the resource. The Last
Successful Probe column shows the most recent date and time when the probe
successfully collected data.
4. Optional: If the Probe Status column shows a status of Failed or Warning,
right-click the resource and click Data Collection > Open Probe Logs to view
the messages in the log file.
5. Optional: If the Probe Status column shows a status of Never probed, right-click
the resource and click Data Collection > Schedule to schedule a probe for the
resource.
Modifying probes
Probes are data collection jobs that collect status and asset information about
monitored resources in your environment. To modify a probe in IBM Spectrum
Control, use the resource list page for the monitored resource in the web-based
GUI.
You can modify the schedule for multiple probes at the same time.
1. From the menu bar, go to the resource list page for a resource type. For
example, to modify a probe schedule for a storage system, go to Storage and
select the type of storage system you want to monitor.
2. Locate the resources that you want to probe.
3. Select the resource rows and click Actions > Data Collection > Schedule.
4. On the Data Collection Schedule window, modify the schedule for the probes,
and click Save.
If you are scheduling probes for multiple resources, a time span is calculated
during which the resources are probed. The resources are probed at different
times during the time span to avoid excessive load on the IBM Spectrum
Control server.
The following rules are used to determine the settings for the probe fields
when you open the Data Collection Schedule window:
The probe jobs run according to the modified schedule. If you disabled the probes,
IBM Spectrum Control stops collecting asset and status data for the monitored
resources.
The changes that you make to the probe schedule are applied to all the resources
that you select. For example, you select two servers with different probe frequency
values. Probes are disabled for both servers. When you open the Data Collection
Schedule window, the probe status field is set to Disabled and the frequency field
is blank. You set the status field to Enabled and the frequency field to Every 2
days. When you click Save, the probe is enabled with the new frequency value for
the two servers that you selected
You can define alerts for a resource if you want to be notified when the following
conditions occur:
v The status of its probe is error or warning. An error status occurs when a probe
did not complete and no data was collected about a resource. A warning status
occurs when a probe completes, but might not have collected a complete set of
data.
v A specified amount of time has passed since a probe collected data about a
resource. You can use this type of alert to be notified when up-to-date
configuration and status data is not being collected about a resource and its
existing data might be stale.
To define an alert for the probe that collects data about a resource, complete the
following steps:
1. To select a resource, choose one of the following options from the menu bar:
Starting probes
To immediately collect data about resources, use the Start Probe action in the
web-based GUI.
If a probe job is not defined for the resource, use the Schedule action to create a
probe.
You can start probes for multiple resources at the same time.
Tip: When you start a probe for a switch, the probe gathers statistics about the
fabric that the switch is a part of.
1. From the menu bar, go to the resource list page for a resource type. For
example, to start a probe for a storage system, go to Storage and select the type
of storage system you want to monitor.
2. Locate the resources that you want to probe.
3. Select the resource rows and click Actions > Data Collection > Start Probe.
The Start Probe action is available for the resources that you select if at least
one of the resources meets the following criteria:
v A probe job is defined for the resource.
v The probe job is enabled.
v The probe job is not currently running.
Probes are started for all the resources that meet the criteria. For example, you
select two storage systems, Storage_System_a and Storage_System_b. Probes are
enabled for both of the storage systems and a probe is running for
Storage_System_a. The probe is started for Storage_System_b when you select Start
Probe. Storage_System_a is not affected by the action because a probe is already
running for the resource.
The Data Collection pane is displayed, which contains information about the data
collection jobs that are defined for the resource.
Restriction: If you select multiple rows, the Open Probe Logs action is not
available.
The Logs page opens and shows log entries for the most recent run of the
probe.
4. Optional: On the Logs page, to view a previous probe log, select a log from the
Select a log list.
5. Optional: To view only the log entries that have a Warning or Error status,
select an option from the Show all list. You can choose to view only entries
that have the following statuses:
You must schedule and run performance monitors before you can complete other
tasks, such as optimizing storage tiering, balancing pools, and running
performance reports.
Before you can view performance information for resources, you must complete
the following tasks:
v Add the storage system or switch for monitoring by IBM Spectrum Control.
v Schedule a performance monitor to collect performance data about the resource.
To create performance monitors for resources in your environment, you can use the
list and detail pages for the resources. For example, to create performance monitors
for switches, use the Switches page. You can create performance monitors for
multiple resources at the same time.
Restrictions:
v You can define only one performance monitor for a resource.
v You can create performance monitors for the following resources only:
– Storage systems
– Switches that are managed by a CIM agent
1. From the menu bar, go to a resource list page for a resource type. For example,
to create performance monitors for storage systems, go to Storage and select
the type of storage system you want to monitor.
2. Locate the resources that you want to monitor.
3. Select the resource rows and click Actions > Data Collection > Schedule.
4. On the Data Collection Schedule window, set the performance monitors to
Enabled. You can set a performance monitor to Enabled only if the probe is set
to Enabled.
5. Select the interval for the performance monitors, and click Save. The interval
represents the number of minutes over which samples of performance data are
averaged. If you are creating performance monitors for multiple resources, the
interval list displays the performance monitor intervals that are common to all
resources. For example, you select two storage systems. Storage_System_a
specifies performance monitor intervals of 5 minutes, 10 minutes, and 15
minutes. Storage_System_b specifies intervals of 10 minutes, 15 minutes, and 20
minutes. The interval list displays intervals of 10 minutes and 15 minutes.
Restrictions:
Performance monitors are created for the resources that are selected, and that meet
the criteria. For example, you select three storage systems, Storage_System_a,
Storage_System_b, and Storage_System_c. You enable the performance monitors
and set the interval field. When you click Save, performance monitors are created
for Storage_System_a and Storage_System_b. Storage_System_c is not affected by
the action because you cannot configure performance monitors for that storage
system.
To check the progress of a performance monitor, you can complete the following
actions:
v From the resource list page, right-click a resource row, and select Data
Collection > Open Performance Monitor Logs. You can view detailed
informational, warning, and error messages that are related to the performance
monitor. Use this information to troubleshoot any errors that might occur when
the performance monitor runs.
v View the Performance Monitor Status column on the resource list page.
To verify that a performance monitor is running for a resource, use the resource list
page in the web-based GUI.
1. From the menu bar, go to a resource list page for a resource type. For example,
to verify that a performance monitor is running for a storage system, go to
Storage and select the type of storage system you want to monitor.
2. Locate the resource that you want to check.
3. View the Performance Monitor Status column. A value of Completed or
Running indicates that the performance monitor is collecting performance
metrics about the resource. The Last Successful Monitor column shows the
most recent date and time when the performance monitor successfully collected
data.
4. Optional: If the Performance Monitor Status column shows a status of Running
with problems, Completed with warnings, Failed, or Canceled, you can view
the logs to troubleshoot the error or warning messages. To view the
performance monitor logs, right-click the resource row and click Data
Collection > Open Performance Monitor Logs.
5. Optional: If the Performance Monitor Status column shows a status of Disabled,
to enable the performance monitor for the resource, right-click the resource row
and click Data Collection > Schedule. On the Data Collection Schedule page,
select Enabled.
You can modify the schedule for multiple performance monitors at the same time.
You can enable or disable performance monitors and modify the interval. The
interval represents the number of minutes over which samples of performance data
are averaged.
1. In the menu bar in the web-based GUI, go to Home > Performance Monitors.
Detailed information about all performance monitors is shown in the
Performance Monitors tab.
2. Locate the performance monitors that you want to modify.
3. Select the performance monitor rows and click Actions > Schedule.
4. On the Data Collection Schedule window, modify the schedule for the
performance monitors.
If you select multiple performance monitors, the following rules are used to
determine the field settings when you open the Data Collection Schedule
window:
v If all of the performance monitors that you select are enabled, the Enabled
value is displayed. If all of the performance monitors are disabled, the
Disabled value is displayed. Otherwise, the state field for the performance
monitors is blank.
v If the performance monitors have different interval values, the interval field
is blank. If the performance monitors have the same interval value, the value
is displayed.
Intervals that are common to all performance monitors that you select are
displayed in the interval list. For example, you select performance monitors
for two storage systems. Storage_System_a specifies performance monitor
intervals of 5 minutes, 10 minutes, and 15 minutes. Storage_System_b
specifies intervals of 10 minutes, 15 minutes, and 20 minutes. The interval list
displays intervals of 10 minutes and 15 minutes.
5. Click Save.
The changes are applied to all the performance monitors that are selected. The
performance monitors run according to the modified schedule. If you disabled a
performance monitor, IBM Spectrum Control stops collecting performance metrics
for the storage system or switch.
To check the progress of the performance monitors, you can complete the
following actions on the Performance Monitors page:
v View information such as the status of the performance monitor and the most
recent date and time when performance data was collected about a resource.
v Right-click the performance monitor row, and select Open Logs. You can view
detailed informational, warning, and error messages that are related to the
performance monitor job. Use this information to troubleshoot any errors that
might occur when the job runs.
You can define alerts for a storage system or switch if you want to be notified
when the following conditions occur:
v The status of its performance monitor is error or warning. An error status occurs
when a performance monitor did not complete and no performance data was
collected about a resource. A warning status occurs when a performance monitor
completes, but might not have collected a complete set of performance data.
v A specified amount of time has passed since a performance monitor collected
data about a resource. You can use this type of alert to be notified when
up-to-date performance data is not being collected about a resource and its
existing data might be stale.
To define an alert for the probe that collects data about a resource, complete the
following steps:
1. To select a resource, choose one of the following options from the menu bar:
You can start or stop performance monitors for multiple resources at the same
time.
Performance monitors are started or stopped for all the resources that meet the
criteria. For example, you select two storage systems, Storage_System_a and
Storage_System_b. Performance monitors are enabled for the storage systems and
both resources are probed. A performance monitor is running for Storage_System_a
but not for Storage_System_b. The performance monitor is started for
Storage_System_b when you select Start. Storage_System_a is not affected by the
action because a performance monitor is already running for the resource.
To check the progress of the performance monitor, you can complete the following
actions on the Performance Monitors page:
v View information such as the status of the performance monitor and the total
number of threshold violations that were detected during the last sampled time
of the performance monitor.
v Right-click the performance monitor row, and select Open Logs. You can view
detailed informational, warning, and error messages that are related to the
performance monitor. Use this information to troubleshoot any errors that might
occur when the performance monitor runs.
To view all of the performance monitors that IBM Spectrum Control uses to collect
metrics for measuring the performance of storage systems and switches, use the
Performance Monitors page in the web-based GUI.
The Performance Monitors page displays one row for each storage system or
switch that IBM Spectrum Control is monitoring. If a performance monitor is not
scheduled for a resource, the status column is set to Disabled for the performance
monitor row.
Before IBM Spectrum Control can collect performance metrics for a resource, the
resource must fulfill the following conditions:
v A probe must be run for the resource.
v For switches, the switch must be managed by a CIM agent.
1. In the menu bar in the web-based GUI, go to Home > Performance Monitors.
On the Performance Monitors tab, the information about performance monitors
To view the performance monitors for specific storage systems and switches, use
the resource detail pages in the web-based GUI. For example, use the Storage
Systems detail page to view performance monitor information for a specific storage
system.
Tip: You can use the columns on the resource list pages to view information
about the performance monitors that are defined for storage systems or
switches. For example, use the Storage Systems page to view performance
monitor information for storage systems.
Use performance monitor logs to view detailed information about the status,
actions, and progress of a performance monitor. You can use this information to
troubleshoot any errors that might occur when a performance monitor is running.
Performance monitor logs contain informational, warning, and error messages that
are related to each action that is taken during the processing of a performance
monitor.
1. In the menu bar in the web-based GUI, go to Home > Performance Monitors.
Restriction: If you select multiple rows, the Open Logs action is not available.
The Logs page opens and shows log entries for the most recent performance
monitor log. A new log file is created when you stop and restart a performance
monitor.
4. Optional: On the Logs page, to view a previous performance monitor log, select
a log from the Select a log list.
5. Optional: To view only the log entries that have a Warning or Error status,
select an option from the Show all list. You can choose to view only entries
that have the following statuses:
The information on the Logs page is automatically updated every 30 seconds. New
entries are added to the end of a log. You can view the following information on
the Logs page:
v The overall status of a performance monitor. The icon that is shown in the Select
a log list represents the most critical status that was generated by an action in
the job run.
v The status for each performance monitor action.
v The date and time when an action was completed. The date, time, and time zone
of an action is shown in the Date and Time column.
v The ID of the message that is associated with an action. You can click the value
in the ID column to view more information about a message.
v The description of an action.
Tip: You can use the navigation and search functions of the web browser to locate
information on the page.
Set the saveNonRoot parameter to saveNonRoot=1 in the TPCD.config file to view the
information that is collected about shares in the web-based GUI.
1. Open the TPCD.config file.
For Windows operating systems:
By default, the TPCD.config file is in the TPC_installation_directory\
data\config\ directory.
When you provision new shares, you can view information about the shares on the
Provisioning task page in the web-based GUI. On the Shares page, you can view
more information about shares, such as the servers that have access to the share.
Conditions that generate alerts are detected during data collection and event
processing. For some storage systems such as IBM Spectrum Accelerate and the
XIV, events are polled every minute from the resource. For IBM Spectrum Scale,
status change events are polled frequently, typically within minutes. For other
resources, events are subscription-based, where the resource itself or a data source
such as a CIM agent sends the events to IBM Spectrum Control when conditions
change on the resource.
The conditions that trigger alert notifications depend on the type of resource that
you are monitoring. In general, the following types of conditions can trigger alerts:
v An attribute or configuration of a resource changed
v The capacity of a resource fell outside a specified range
v The performance of a resource fell outside a specified range
v The storage infrastructure was changed, such as a new or removed resource
v Data is not being collected for a resource
For a list of conditions that can trigger alerts, see “Triggering conditions for alerts”
on page 252.
Defining alerts
To set up alert definitions so that you are notified when certain conditions are
detected on monitored resources, you must complete the following tasks:
Related tasks:
“Adding resources” on page 75
You must add resources to IBM Spectrum Control before you can collect data,
generate reports, and manage storage that is related to those resources.
Related reference:
Alert severities
IBM Spectrum Control determines the severity of alert conditions that it detects on
monitored resources. Use the severity level to help determine the priority in which
you resolve alerts.
Defining alerts
Define how and when you are alerted to changes in the configuration, attributes,
and performance of monitored resources.
Category Description
General Attributes for the key properties of a
resource, such as status, version changes,
removals, discoveries, state, and data
collection status.
Capacity Attributes for capacity statistics of a
resource, such as available and used space,
total space for disk, file systems, volumes,
and pools, and reserved space.
Performance Attributes for the performance of storage
systems and switches, such as I/O rates,
data rates, response times, and port frame
rates.
5. To enable the alert for an attribute, click the corresponding switch icon .
Tip: To disable the alert for an attribute, click the switch icon again.
When you disable an alert, notifications are not generated for that attribute.
6. Specify the criteria for generating an alert. Use criteria such as greater than or
equal to, less than or equal to, storage values, and time measurements to
customize the conditions under which attributes generate alerts. For example,
for a capacity attribute such as Available Disk Space, you can specify that an
alert is generated when the amount of available space on a resource's disks is
less than or equal to 50 GiB. The operator (less than or equal to) + a specified
amount of space (50) + the unit of measurement (GiB) is the criteria that
determines if an alert is generated.
Tips:
v Not all attributes require criteria for generating alerts. The category and
type of an attribute determines whether you can specify criteria and the
options that you can select.
v Some attributes can use the operators such as is, is not, and contains. For
example, for the Firmware attribute on a DS8000 storage system, select the
operator contains. Then, in the value field, type R5 to be notified if the
firmware is at the R5 level rather than at a later version such as R6.3, R6.2,
or R6.3. This alert definition might be useful if you want to be notified
when the firmware for a storage system was reverted to a previous version
for some reason.
Option Description
Assign this severity to alerts that might not
require any action to resolve and are
primarily for informational purposes. For
example, assign an informational severity to
alerts that are generated when a new pool is
added to a storage system.
Assign this severity to alerts that are not
critical, but represent potential problems. For
example, assign a warning severity to alerts
that notify you when the status of a data
collection job is not normal.
Assign this severity to alerts that are critical
and need to be resolved. For example, assign
a critical severity to alerts that notify you
when the amount of available space on a file
system falls below a specified threshold.
8. Specify how you are notified of alert violations and if you want a script
to be run.
Option Description
Do not suppress alerts Receive alert notifications whenever an alert
violation is detected.
Only alert once until problem clears Receive one notification for an alert
violation, even if the condition is violated
multiple times.
Only generate alerts every Receive one notification when an alert is
initially violated. The alert is suppressed and
no notifications are sent until both the
specified time has passed and the alert is
triggered again.
Do not alert until the condition is violated Do not receive notifications for an alert
for more than unless the violation is not cleared for longer
than the specified time.
10. Optional: Duplicate an alert. Use this action when you want to define
another alert for the same attribute but with different criteria and settings.
Duplicating alerts can be helpful in the following situations:
v When you want to generate separate warning alerts and critical alerts for
different conditions on the same attribute.
For example, for a capacity attribute such as Available Disk Space, you
might want to define the following alerts:
Conditions that generate alerts are detected during data collection and event
processing. For some storage systems such as IBM Spectrum Accelerate and the
XIV, events are polled every minute from the resource. For IBM Spectrum Scale,
status change events are polled frequently, typically within minutes. For other
resources, events are subscription-based, where the resource itself or a data source
such as a CIM agent sends the events to IBM Spectrum Control when conditions
change on the resource.
You can view information about alert violations at the following locations in the
GUI:
Table 22. Locations where you can view alert violations for attribute and capacity alerts.
Task Location in GUI
View all alerts In the menu bar, select Home > Alerts.
View all the alerts that were 1. In the menu bar, select one of the following options:
generated for storage systems
v Storage > Block Storage Systems
v Storage > File Storage Systems
v Storage > Object Storage Systems
2. Click the Alerts tab.
View the alerts for a specific 1. In the menu bar, choose one of the following options:
storage system
v Storage > Block Storage Systems
v Storage > File Storage Systems
2. Double-click a storage system.
3. Click Alerts in the General section.
View all the alerts that were 1. In the menu bar, select Network > Switches.
generated for switches
2. Click the Alerts tab.
View the alerts for a specific 1. In the menu bar, select Network > Switches.
switch
2. Double-click a switch.
3. Click Alerts in the General section.
View all the alerts that were 1. In the menu bar, select Network > Fabrics.
generated for fabrics
2. Click the Alerts tab.
View the alerts for a specific 1. In the menu bar, select Network > Fabrics.
fabric
2. Double-click a fabric.
3. Click Alerts in the General section.
View all the alerts that were 1. In the menu bar, select Servers > Hypervisors.
generated for hypervisors
2. Click the Alerts tab.
To define a performance alert, select a metric that you want to measure and specify
a threshold value. When the performance of that resource falls outside the
threshold, an alert is generated. For example, you can define an alert that notifies
you when the back-end response times for managed disks on a SAN Volume
Controller exceed 35 milliseconds per read operation. The Overall Back-end
Response Time is a metric that measures the average number of milliseconds that
it takes to service each read operation on a managed disk.
Tip: You cannot apply different thresholds to internal resources of the same type.
For example, a storage system has two ports, Port A and Port B. You cannot set
different threshold values for each port on the storage system. When you define a
performance alert for ports, its threshold value is applied to all of the ports on the
storage system.
1. To select a resource, choose one of the following options from the menu bar:
Option Description
Assign this severity to alerts that might not
require any action to resolve and are
primarily for informational purposes.
Assign this severity to alerts that are not
critical, but represent potential problems. For
example, assign a warning severity to alerts
that notify you when the Port Send
Bandwidth Percentage is greater than or
equal to 75% but less than 85%.
Assign this severity to alerts that are critical
and need to be resolved. For example, assign
a critical severity to alerts that notify you
when the Port Send Bandwidth Percentage
is greater than or equal to 85%.
12. Specify how you are notified of alert violations and if you want a script
to be run.
Option Description
Do not suppress alerts Receive alert notifications whenever an alert
violation is detected.
Only alert once until problem clears Receive one notification for an alert
violation, even if the condition is violated
multiple times.
Only generate alerts every Receive one notification when an alert is
initially violated. The alert is suppressed and
no notifications are sent until both the
specified time has passed and the alert is
triggered again.
Do not alert until the condition is violated Do not receive notifications for an alert
for more than unless the violation is not cleared for longer
than the specified time.
14. Optional: Duplicate an alert. Use this action when you want to define
another alert for the same metric but with different criteria and settings.
Duplicating alerts can be helpful in the following situations:
v When you want to generate separate warning alerts and critical alerts for
different thresholds on the same metric.
For example, for the CRC Error Rate metric for ports, you might want to
define the following alerts:
– Duplicate the alert, but this time, specify a critical severity when the
CRC error rate is greater than or equal to .033 counts per second.
v When you want to send alert notifications to different people based on the
severity of an alert.
In the previous example for the CRC Error Rate metric, you can configure
the notification settings so that warning alerts are sent to junior
administrators, while critical alerts are sent to more senior administrators to
resolve.
To determine whether alerts are generated, the performance metrics that are
collected for resources are compared with the threshold values that you defined for
those alerts. You can view information about alert violations at the following
locations in the GUI:
Table 23. Locations where you can view alert violations for performance metrics.
Task Location in GUI
View all the alerts that were 1. In the menu bar, choose one of the following options:
generated for storage systems
v Storage > Block Storage Systems
v Storage > File Storage Systems
2. Click the Alerts tab.
View all the alerts that were 1. In the menu bar, select Network > Switches.
generated for switches
2. Click the Alerts tab.
View the alerts for a specific 1. In the menu bar, choose one of the following options:
storage system
v Storage > Block Storage Systems
v Storage > File Storage Systems
2. Double-click a storage system.
3. Click Alerts in the General section.
View the alerts for a specific 1. In the menu bar, select Network > Switches.
switch
2. Double-click a switch.
3. Click Alerts in the General section.
View all performance alerts 1. In the menu bar, select Home > Alerts.
2. Click the performance icon on the summary chart.
Suppressing alerts
Use suppression options to determine how often you receive alerts.
Option Description
Do not suppress alerts Receive alert notifications whenever an alert
violation is detected.
Only alert once until problem clears Receive one notification for an alert
violation, even if the condition is violated
multiple times.
Only generate alerts every Receive one notification when an alert is
initially violated. The alert is suppressed and
no notifications are sent until both the
specified time has passed and the alert is
triggered again.
Do not alert until the condition is violated Do not receive notifications for an alert
for more than unless the violation is not cleared for longer
than the specified time.
4. Click Done.
5. Click Save.
4. Optional: View how you are notified of alert violations and if a script is
specified.
5. Optional: Evaluate the current and historical performance of a resource. In
the performance chart, a yellow horizontal line represents the threshold value
for warning alerts; a red horizontal line represents the threshold value for
critical alerts.
Option Description
Do not suppress alerts Receive alert notifications whenever an alert
violation is detected.
Only alert once until problem clears Receive one notification for an alert
violation, even if the condition is violated
multiple times.
Only generate alerts every Receive one notification when an alert is
initially violated. The alert is suppressed and
no notifications are sent until both the
specified time has passed and the alert is
triggered again.
Do not alert until the condition is violated Do not receive notifications for an alert
for more than unless the violation is not cleared for longer
than the specified time.
Tip: To enable the definition again, click the icon so that it appears like this:
.
5. Click Save.
2. Right-click the resource that contains the alert definition and select Edit Alert
Definitions.
3. Locate the alert definition that you want to edit.
4. To enable or disable an alert definition, click the corresponding switch icon:
v The alert is enabled.
v The alert is disabled.
5. Edit the criteria for generating an alert. Criteria includes operators such as
greater than or equal to, less than or equal to, is, is not, and contains, and it
can include values for storage space, performance metrics, and time
measurements.
6. Change the severity for the alert. Assigning a severity can help you more
quickly identify and address the critical conditions that are detected on
resources. The severity that you assign depends on the guidelines and
procedures within your organization. Default assignments are provided for
each alert.
7. For performance alerts, edit the threshold value by evaluating the current
and historical performance of a resource. In the performance chart, a yellow
horizontal line represents the threshold value for warning alerts; a red
horizontal line represents the threshold value for critical alerts.
8. Change how you are notified of alerts and if you want a script to be
run.
Option Description
Do not suppress alerts Receive alert notifications whenever an alert
violation is detected.
Only alert once until problem clears Receive one notification for an alert
violation, even if the condition is violated
multiple times.
Only generate alerts every Receive one notification when an alert is
initially violated. The alert is suppressed and
no notifications are sent until both the
specified time has passed and the alert is
triggered again.
Do not alert until the condition is violated Do not receive notifications for an alert
for more than unless the violation is not cleared for longer
than the specified time.
10. Click Save when you are done editing the definition.
2. To view the alert notification settings for a resource, choose one of the
following options:
Option Description
Right-click the resource in the list and click Use this option to view the notification
Edit Alert Notification Settings. settings for an alert from the resource list
page.
Right-click the resource and click View Use this option to view the notification
Details. The resource page is displayed. In settings for an alert from the resource page.
the General section, click Alerts, and then
click the Notification Settings tab.
3. View the notification settings that apply to all of the alert definitions that are
enabled for the resource.
4. To close the Notification Settings page, click Cancel.
When you select multiple resources, the check box choice for each notification
setting indicates how the setting is applied to the resources:
1. To select a resource, choose one of the following options from the menu bar:
2. To view the alert notification settings for multiple resources, press Ctrl and
right-click each resource. Click Edit Alert Notification Settings.
3. To close the Notification Settings page, click Cancel.
Configure IBM Spectrum Control to send alert notifications by using email, SNMP
traps, or a Tivoli Netcool/OMNIbus server.
1. To select a resource, choose one of the following options from the menu bar:
2. To modify the alert notification settings for a resource, choose one of the
following options:
Option Description
Right-click the resource in the list and click Use this option to edit the notification
Edit Alert Notification Settings. settings for an alert from the resource list
page.
3. Specify the email addresses that you want to notify when an alert is generated.
The email addresses that you specify override the addresses that were defined
at Settings > Alert Notifications.
Tip: The email addresses that you define are applied to all the alert definitions
for a resource, unless overridden. To override these settings, edit the
notification settings for a specific alert definition.
4. Optional: Send alert notifications to a Tivoli Netcool/OMNIbus server.
5. Optional: Send SNMP trap messages when an alert is generated.
6. Optional: Write alert messages to the OS log and select their level of severity.
7. Click Save.
Configure IBM Spectrum Control to send alert notifications by using email, SNMP
traps, or a Tivoli Netcool/OMNIbus server.
When you select multiple resources, the check box choice for each notification
setting indicates how the setting is applied to the resources:
1. To select a resource, choose one of the following options from the menu bar:
2. To modify the alert notification settings for multiple resources, press Ctrl and
right-click each resource. Click Edit Alert Notification Settings.
Tip: The email addresses that you define are applied to all the alert definitions
for the selected resources, unless overridden. To override these settings, edit the
notification settings for a specific alert definition.
4. Optional: Send alert notifications to a Tivoli Netcool/OMNIbus server.
5. Optional: Send SNMP trap messages when an alert is generated.
6. Optional: Write alert messages to the OS log and select their level of severity.
7. Click Save.
Viewing alerts
View the alerts that were detected on monitored resources.
The summary chart at the top of the page is a visual representation of the
alerts that were detected on monitored resources. The chart consists of
stacked bars with the number and severity of current alerts on the y-axis
and the resource type on the x-axis. The y-axis labeling scales dynamically
according to the highest number of alerts in any of the categories.
Alerts list
The alerts list shows information about all the alerts that were detected on
monitored resources. Information in the list is organized into columns.
These columns include information about the condition that was detected,
the severity of the alert, when the alert was detected, and the names of the
resources where the alert condition was detected.
The version of IBM Spectrum Control that detected an alert determines where
information about the alert is displayed. Alerts that were generated in versions of
the product before Tivoli Storage Productivity Center version 5.1 are only
displayed on the Alerts page. Alerts that were generated in Tivoli Storage
Productivity Center version 5.1 or later are displayed on the Alerts page and in the
Alerts tab on the pages for the related resources.
1. In the menu bar in the GUI, go to Home > Alerts. Information about alerts is
shown in the list of alerts.
Tip: Hover the mouse pointer over a condition to view a summary of the
event that triggered the alert.
2. Optional: To view the number of alerts for a specific type of resource, hover the
mouse pointer over the related icon in the summary chart. For example, if you
want to view the number of Critical, Warning, and Informational alerts that
were triggered by hypervisors, hover the mouse pointer over the Hypervisors
icon .
Tip: To view descriptions of the icons and columns on the Alerts page, click
the Help icon in the upper-right corner of the page.
Tip: The icon on the Alerts tab represents the most severe alert condition that
was detected on the monitored resources. For example, if one of the jobs for
storage systems failed, the following icon is shown on the tab:
Alerts.
3. Optional: View the icons at the top of the Alerts tab for a summary of alert
severities. This summary includes the number of alerts that have a Critical,
Warning, Informational, or Acknowledged status.
Tip: To view descriptions of the icons and columns on the Alerts tab, click the
Help icon in the upper-right corner of the page.
Alerts (25)
3. Click the Alerts link in the General section to view a complete list of the alerts
that were detected on the resource.
The information about alerts is organized into columns. These columns include
information about the condition that was detected, the severity of the alert,
when the alert was detected, and the names of the resources where the alert
condition was detected. Hover the mouse pointer over a condition to view a
summary of the event that triggered the alert.
Tip: To view descriptions of the icons and columns that are shown for alerts,
click the Help icon in the upper-right corner of the page.
4. Optional: View the icons at the top of the page for a summary of alert
severities that were detected. This summary includes the number of alerts that
have a Critical, Warning, Informational, or Acknowledged status.
Acknowledging alerts
Some alerts in IBM Spectrum Control are triggered by conditions that commonly
occur and can be ignored. In such cases, you acknowledge these alerts to indicate
that they were reviewed and do not require immediate resolution. By
acknowledging alerts, you can more quickly identify the other alerts in lists that
must still be reviewed and resolved.
Tip: Acknowledging alerts does not affect the status of resources. The status of a
resource is determined by its consolidated status and the propagated status of its
internal resources, not by alerts that are generated. For information about how to
acknowledge the status of a resource, see “Acknowledging the condition and status
of resources” on page 146.
Warning - Acknowledged
3. Optional: To acknowledge multiple alerts at the same time, press Ctrl and click
each alert. To select a series of alerts, select the first alert, and then press Shift
and click the last alert. When the alerts are selected, right-click a row in the list
and select Acknowledge alerts.
Removing alerts
Remove alerts when you no longer require to view them.
By default, alerts are automatically removed based on retention settings that are
defined on the History Retention page in the IBM Spectrum Control GUI.
However, you can use the following procedure to manually remove alerts at any
time.
1. In the GUI, go to a list of alerts that includes the alerts that you want to
remove. For example, if you want to remove alerts for all different types of
top-level resources, go to Home > Alerts. If you want to remove alerts for a
specific type of resource such as storage systems, go to Storage and select the
type of storage system you want to monitor, and click the Alerts tab.
2. Right-click the alert that you want to remove and select Remove alerts.
3. Click Remove to remove the alert. When you remove an alert, it is no longer
shown on the Alerts page or in the Alerts tabs on the related resource list and
resource detail pages.
For example, if you remove an alert for a fabric, that alert is removed from the
Alerts page, Fabrics page, and Fabric details page.
4. Optional: To remove all the alerts that are shown in a list, select Remove all
alerts from the Actions menu.
5. Optional: To remove all the acknowledged alerts that are shown in a list, select
Remove acknowledged alerts from the Actions menu.
The dashboard is view displayed when you start a new session of IBM Spectrum
Control or when you go to Home > Dashboard in the menu bar. Use the
dashboard to view the following summary information about a storage
environment:
v Condition of storage: block, file, and object storage systems
v Condition of storage consumers: hypervisors, servers, departments, and
application
v Condition of network resources: fabrics and switches
v Number error, warning, and information alerts that are generated on resources
v Most active storage systems in your environment.
You can click on resource icons in the dashboard to add more resources for
monitoring and to see detailed information about resources that IBM Spectrum
Control is currently monitoring. Position the mouse pointer over the lines in the
Most Active Storage Systems chart to see performance information about specific
resources. For more information about the dashboard, see “Dashboard view” on
page 133.
Use a resource list page as a central location for viewing information about the
top-level resources of a specific type. For example, use the File Storage Systems
page to view a list of the file storage systems that are monitored by IBM Spectrum
Control. Each resource list page corresponds to a specific type of resource, which
includes block storage systems, file storage systems, object storage systems,
volumes, pools, servers, hypervisors, switches, and fabrics. You can view the
following information on resource list pages:
v Overall condition of the resources
v Key information about the resources
v Alerts that were generated for the resources
v Jobs that were run for the resources
To learn about how to access the list pages for resources, see “Viewing information
about top-level resources” on page 137.
Note: Volumes and pools are internal resources of storage systems, but have their
own resource list pages so that you can view them all in a central location.
Use resource details pages to view information about resources that are internal or
related to a top-level resource. For example, use the File Storage System details
page to view detailed information about a specific file storage system. You can
view the following information on resource details pages:
v The overall capacity and storage usage for a resource
v The status of resources
v Key information about a resource
v Alerts that were generated for a resource
v Data collection that was run for a resource
v Information about components that exist in top-level resources
v Information about the resources that are related to another resource
Alerts page
Use the Alerts page to view and manage the alert conditions that were detected on
monitored resources. Specifically, you can complete the following actions:
v View the overall number of alerts that were detected on monitored resources.
This information is presented in a bar chart for the following types of alerts:
– Database
– Fabric
– Hypervisor
– Other
– Performance
– Server
– Storage system
– IBM Spectrum Control
v View information about specific alerts, including severity, last occurrence, and
the resources where they were detected.
v Acknowledge alerts that were reviewed but are not yet resolved.
v Unacknowledge alerts.
v Remove alerts from the page.
To access the Alerts page, go to Home > Alerts in the menu bar.
IBM Spectrum Control can collect information about the performance of monitored
storage systems and switches. This information includes key performance metrics.
On the Performance Monitors page, you can view detailed information about
performance monitors that are collecting data. Use this information to identify
performance monitors that are encountering problems when they run. You can also
view the metrics that are collected by a performance monitor for a resource.
To access the Performance Monitors page, select Home > Performance Monitors.
Tasks page
Use the Tasks page to view and manage the tasks that IBM Spectrum Control uses
to optimize resources and provision storage. Tasks are created when you complete
any of the following actions:
v Assign storage to servers, hypervisors, or a cluster by using the Provision
Storage wizard.
v Move volumes to higher or lower tiers by using the Analyze Tiering wizard.
v Move or convert volumes by using the Transform Storage wizard.
v Distribute the workload of volumes across pools on the same tier by using the
Balance Pools wizard.
To access the Tasks page, go to Home > Tasks in the menu bar.
Use the System Management page to view information about the overall condition
of IBM Spectrum Control. You can view information about the servers on which
IBM Spectrum Control is installed. This information includes component server
and database status, certain server alerts and database connection alerts, server
file-system capacity information, and remote volume-performance information.
Reporting
Use the optional Cognos Business Intelligence reporting tool in the web-based GUI
to view detailed reports about resources. The following reports are available:
Predefined reports
These reports are included with IBM Spectrum Control. The following
types of predefined reports are available:
v Capacity and relationships of resources
v Performance
v Historical space
v Storage tiering
Custom reports
Unlike predefined reports, you can select the information that you want to
include in custom reports. Custom reports can contain detailed information
about the relationships between monitored resources, the properties of
monitored resources, and detailed information about the performance of
monitored resources.
To learn about how to use the Cognos Business Intelligence reporting tool, see
Reporting in IBM Spectrum Control.
Dashboard view
Use the dashboard to monitor the overall condition of monitored resources and
identify potential problem areas in a storage environment. You can also view the
condition of the applications, groups, and other entities that consume storage on
resources. The dashboard also displays alerts, as well as a chart showing the most
active storage systems.
The dashboard provides status information for the resources that IBM Spectrum
Control is monitoring.
The overall status for each resource type
A status symbol and number are shown below each resource icon on the
dashboard. This symbol represents the most critical status that was
detected on the internal resources for a resource type. For example, if 20
storage systems are monitored, and an error was detected on a volume for
Error (red)
An error status was detected on one or more of the monitored
resources for a resource type. Error statuses represent serious
problems on a resource. Resolve these problems as soon as
possible. View the details of a resource to learn more about the
status of its internal resources.
Unreachable (orange)
One or more of the monitored resources for a resource type are not
responding. This status might be caused by a problem in the
network or by a Storage Resource agent that is no longer running
and did not communicate that it was shutting down.
Warning (yellow)
A warning status was detected on one or more of the monitored
resources for a resource type. Warning conditions are not critical,
but represent potential problems. View the details of a resource to
learn more about the status of its internal resources.
Normal (green)
No warnings or errors were detected on the monitored resources
for a resource type.
Storage systems can be configured for block storage, file storage, a combination of
block and file storage, or a combination of file and object storage. The top left
section of the dashboard shows the type, number, and status of the storage systems
that IBM Spectrum Control is monitoring. The number in the circle next to the
storage system type shows how many storage systems of that type are being
monitored. The status icon below each storage system type shows the status of the
monitored systems. Click the storage system type, for example Block Storage
Systems, to see more detailed status and information about those storage systems.
The diagram in the top middle section of the dashboard provides a visual
representation of the monitored resources that are consuming storage. You can
click the icons in this section to add resources of that type or to see detailed
information about the resources you have already added. The number next to each
icon shows the number of those resources that are being monitored by IBM
Spectrum Control. If IBM Spectrum Control is monitoring resources of a particular
type, such as departments, you will see a status icon that shows the overall status
of those types of resources.
The types of resources that are consuming storage
Each type of resource in the diagram is represented by an icon. To learn
more detailed information about the individual resources that are
monitored, click the icon in the diagram. For example, if you click the
departements icon, a new page shows detailed information about the
individual departments that are being monitored.
The number of resources that are monitored for each resource type
A number in a circle is shown next to each resource icon. This number
Tip: If no resources are being monitored for a resource type, click its icon
on the dashboard to add a resource of that type. For example, if the
dashboard shows a 0 next to the departments icon, you can click the icon
or the circle for departments to add a department. The GUI guides you
though the process for adding the resource for monitoring. For more
information about adding resources, see “Adding resources” on page 75.
The top right section of the dashboard shows the number and status of the fabrics
and switches that IBM Spectrum Control is monitoring. The number in the circle
next to the fabric or switch icon shows how many fabrics and switches are being
monitored. The status icon below the fabric or switch shows the status of those
entities. Click the icon to see more detailed status and information about those
fabrics and switches. The dashboard shows the following information for the
monitored fabrics and switches in your environment:
Fabrics
v The number of fabrics that are being monitored.
v The most critical status of the monitored fabrics. If more than one fabric
is monitored, the dashboard shows the most critical status level of those
fabrics.
Switches
v The number of switches that are being monitored.
v The most critical status of the monitored switches. If more than one
fabric is monitored, the dashboard shows the most critical status level of
those switches.
Alerts are generated when IBM Spectrum Control detects certain conditions or
events on monitored resources. The Alerts section of the dashboard shows a status
summary of the alerts that were detected in your environment during a specified
time period. This summary includes the number of alerts that have the following
statuses: Critical, Warning, and Informational.
Use the following actions to manage the display of statuses for alerts:
v To select the time period in which you want to view alert statuses, click the
down arrow and select a time period. You can view the status of all alerts that
were detected in the last hour, last day, or last week.
v To view more detailed information about alerts, click View all alerts to access
the Alerts page.
The Performance chart provides information about the most active storage systems
in your storage environment. Position your cursor over a data point in the chart to
see the total I/O rate for a particular storage system. The I/O rate is displayed in
A resource list page shows information about the monitored resources for the
selected type. You can view the following information on this page:
v The overall status of the resources for a specific type
v Key information about the resources
v Alerts that were generated for the resources
v Jobs that were run for the resources
IBM Spectrum Control provides a number of different icons to help you quickly
determine the health of resources.
Table 25. Possible statuses and conditions of resources
Icon Health Explanation
Error A serious problem was detected on a resource or on its
internal resources. Resolve these problems as soon as
possible.
Error - An Error status was detected and acknowledged. An Error
Acknowledged - Acknowledged status indicates that a status was reviewed
and is either resolved or can be ignored.
Switches
Switch
Blades
Inter-switch connections
Logical switches
Ports
Hypervisor Disks
Virtual machines
VMDKs
Disks
External disks
Host connections
I/O groups
Managed disks
Modules
, Nodes
Pools
Ports
RAID arrays
Volumes
File storage system Network shared disks
Nodes
Nodes
The following statuses of internal resources are used to help calculate the condition
of top-level resources:
Tip: Statuses that are acknowledged are not used to calculate the overall condition
of a top-level resource.
Internal resources for a top-level resource might have different statuses. IBM
Spectrum Control uses the most critical status of an internal resource to help
determine the overall condition of a top-level resource. For example, in a storage
system, a port might have an Error status, a pool might have a Warning status,
and multiple controllers might have an Unknown status. In this case, if the storage
system itself has a normal status, its overall condition is Error because it is the
most critical status that was detected on internal resources.
The following table shows some of the possible combinations of statuses and the
resulting, overall condition for a top-level resource.
Table 27. Propagation of the statuses for resources
Unreachable
1
Error Warning Normal Unknown 2
Resulting
condition for a
top-level resource
X
Unknown
X
Normal
X X
Normal
X
Warning
X X
Warning
X X X
Warning
X
Unreachable
X X
Unreachable
X X X
Unreachable
X X X X
Unreachable
X
Error
X X
Error
X X X
Error
The condition of a resource represents the most critical status that was detected on
that resource or on its internal resources. For example, if an error status was
detected on a storage system pool, the overall condition of the storage system is
error .
1. In the menu bar, go to Home > Dashboard.
2. View the condition icons that are shown with each resource type.
For example, if 20 block storage systems are monitored, but 10 storage systems
have internal resources with an error status, 2 storage systems are unreachable,
and 4 storage systems have internal resources with a warning status, the
following conditions icons are shown for block storage systems:
Block Storage Systems
10 2 4
If no Error or Warning statuses were detected on the internal resources for
5 Normal
5 Warning
2 Unreachable
3 Error
3. To view the condition for specific resources, check the Condition column in the
list of resources.
4. Optional: Click the Search icon to filter the list so that only resources with a
specified condition are shown. You can use filtering to identify the resources
with the most serious conditions in your environment.
5. Optional: Select Condition.
6. Optional: In the Choose Value list, select the condition on which you want to
filter. The list of resources is automatically refreshed and only resources with
the filtered status are shown. For example, select Warning to view only
the resources with a Warning condition.
Controllers (5)
5. To view the status of a specific internal resource, click the name of that internal
resource in the Internal Resources section. A list of the monitored internal
resources is displayed. For example, on the details page for a server, click
Controllers (5) to view a list of the five controllers that are associated with the
server.
6. Check the Status column to view the status for each internal resource.
Tip: When you view information about some internal resources, the Status
column might show values that are more specific than Error, Unreachable,
Warning, Unreachable, Unknown, and Normal. Use this additional status to
determine the cause of the problem for an internal resource.
For example, in the Internal Resources section on the details page for a storage
system, an error status might be shown for managed disks:
When you view the list of managed disks, the Status column might show an
Offline status for a specific managed disk. When a managed disk is reported as
offline, IBM Spectrum Control uses an error status icon to reflect that
status.
When you acknowledge the condition of a top-level resource, the following actions
are taken:
Dashboard view
v The condition of the acknowledged resource is not used to determine the
condition icon that is displayed for that resource type on the Dashboard
view. For example, if you acknowledge the unreachable condition for a
switch, the condition of that switch is not used to determine the number
of unreachable conditions that is shown for switches on the Dashboard
view.
v The acknowledged condition is shown as Acknowledged for a resource
on the Dashboard view. For example, if 10 switches have Unreachable
conditions and you acknowledge the condition for one of them, the
following information is shown for switches:
9 Unreachable (1 Acknowledged)
Resource details page
v The condition icons at the top of the page are updated. For example, if
10 switches have Unreachable conditions, and you acknowledge one of
them, the total number Unreachable conditions decreases by one and the
number of Unreachable - Acknowledged conditions increases by one.
The following information is updated at the top of the Switches page:
Unreachable
Related reference:
“Resources that you can monitor” on page 75
You can use IBM Spectrum Control to monitor storage systems, servers,
hypervisors, fabrics, and switches. Information about these top-level resources
includes information about their internal resources and related resources. Internal
resources are components that exist in a top-level resource. Related resources are
external to a top-level resource, but are related to it through assigned storage, a
network connection, or virtual hosting.
“How the condition of a resource is determined” on page 141
The operational condition of a resource represents the most critical status that was
detected on the resource itself and on its internal resources.
When you acknowledge the status of an internal resource, the following actions
occur:
v The status of the internal resource is no longer used to determine the condition
of the associated top-level resource.
v The status icons at the top of the page for the internal resource are updated.
For example, if you acknowledge the Error status for a controller on a server, the
total number of Error statuses decreases by one and the number of Error -
Acknowledged statuses increases by one on the Controllers page. If originally
there were five controllers with Error statuses, the following updated status
information is shown:
You can use the performance monitoring to complete the following tasks:
v Measure, compare, and troubleshoot the performance of switches, storage
systems, and their internal resources.
v Review the alerts that were triggered when the performance if a resource fell
outside of a specific range.
v Customize views of performance so that you can analyze specific resources and
metrics during time ranges that you specify.
v View performance information in a chart or table format to help you quickly
identify where and when performance issues are occurring. The chart is a visual
representation of how the performance of resources trend over time.
v Drill down into resources to view detailed information about the performance of
internal and related resources. For example, if a SAN Volume Controller is
shown in the chart, you can quickly view and compare the performance of its
internal and related resources, such as disks, volumes, ports, managed disks,
and back-end storage.
v Implement server-centric monitoring of SAN resources without requiring a
Storage Resource agent. When you add an agentless server, IBM Spectrum
Control correlates the server with the known host connections on monitored
storage systems. If matches are found, you can view the amount of storage that
is assigned to the server, and trace that storage back to the storage system. You
can then view details about the internal resources of the related storage system,
including performance information.
v Export performance information to a CSV file. A CSV file is a file that contains
comma-delimited values and can be viewed with a text editor or imported into a
spreadsheet application.
Before you can view performance information for resources, you must complete
the following tasks:
Related reference:
“Performance metrics” on page 283
IBM Spectrum Control can collect information about the performance of storage
systems and switches. This information includes metrics that measure the
performance of volumes, ports, and disks. You can view performance information
or specify alerts for when the performance of a resource falls outside a specified
range.
Before you view the performance of resources, ensure that performance data was
collected for those resources during the time ranges that you want to analyze. IBM
Spectrum Control uses performance monitors to collect metrics for measuring the
performance of storage systems and switches. For information about how to verify
that performance monitors were run, see “Verifying that a performance monitor is
running for a resource” on page 105.
You can access the performance view for a resource from different locations in the
web-based GUI:
In the web-based GUI, you can also view the performance of internal resources on
the details pages for the related, top-level resources. For example, you can view the
performance of the controllers for a storage system on the details page for that
storage system. To access the performance view for an internal resource on a
details page, select the type of internal resource and click the Performance tab.
The following information summarizes the internal resources and locations where
you can access a performance view.
Table 28. Internal resources and locations where you access the performance view
Locations in the GUI where you can access the
Internal resource performance view
Pools v Storage > Pools
v Click Storage, and then click Block Storage Systems,
File Storage Systems, or Object Storage Systems,
depending on the storage system that you require.
Right-click the storage system, click View Details, and
click Pools
Related information:
Performance statistics (for SAN Volume Controller systems)
Real-time performance statistics provide short-term status information for the SAN
Volume Controller system. The statistics are shown as graphs in the management
GUI.
Performance statistics (for Storwize V7000 Unified systems)
Real-time performance statistics provide short-term status information for the
Storwize V7000 Unified system. The statistics are shown as graphs in the
management GUI.
Chart
The chart shows a visual representation of how the performance of
a resource trends over time. Each line on the chart represents a
metric and a resource. For example, if you select two metrics and
three resources, six lines are shown on the chart. The y-axis shows
the unit of measurement for a metric. If more metrics were selected
with a different unit of measurement, an extra y-axis is shown on
the right side of the chart window.
Table
The table shows performance and asset information that is
formatted into rows and columns. Each row represents a resource
and a time stamp from the chart; each column represents a metric
from the chart. For example, if two metrics and three resources are
displayed on a chart, and each of the lines on the chart have 10
data points, 30 rows and 2 columns are shown in the table.
To view other metrics and asset information for a resource,
right-click anywhere in the header row of the table and select extra
columns. The type of resource determines the metrics and
information that is available.
Performance chart legend
The bottom section of the performance view shows more information
about the resources in the chart. The information is formatted into rows
Tip:
v If you hide a resource in the performance chart, the row for that
resource remains visible in the chart legend.
v In the chart legend, information about a resource represents the state of
that resource during the selected time range. Specifically, this
information does not represent the current state of a resource, but
instead shows the final state of the resource during the selected time
range.
For example, if the current date is January 1, and you view a volume
with the time range set to December 1 to December 7, the legend shows
the capacity of that volume on December 7. If the capacity of the volume
was changed between December 7 and January 1, this historical capacity
is different from the current capacity of the volume on January 1.
Related concepts:
“Customizing lists of resources, tasks, and alerts” on page 233
The web-based GUI uses lists to show information about resources, tasks, and
alerts. The information in each list is organized into columns and rows. You can
customize these lists by filtering information, sorting rows, and showing, hiding,
and reordering columns.
Controls:
View chart
View performance information in a chart format. The chart shows a visual
representation of how resource performance trends over time. Each line on
the chart represents a metric and a resource. The y-axis shows the unit of
View table
View performance information in a table format. Each row represents a
resource and a time stamp. Each column represents a metric. You can view
other metrics and information for a resource by right-clicking anywhere in
the header row for the table and selecting more columns. The type of
resource determines the metrics and information that is available.
For information how to filter, sort, and customize the columns in a table,
see “Customizing lists of resources, tasks, and alerts” on page 233.
Metrics
Add metrics to the performance chart. On the Select Chart Metrics
window, metrics are organized into three tabs: Volume Metrics, Disk
Metrics, and Port Metrics. The metrics and tabs that are available depend
on the type of resource that is being shown in the chart. The number next
to the name of the tab represents the number of metrics that are currently
selected from that tab.
You can select multiple metrics at the same time and from different tabs,
but you cannot include more than two unit types in the same view. For
example, if you select metrics that use % and ops/s as units of
measurement, you cannot select more metrics that use different units of
measurement such as KiB/op or MiB/s.
For a list of metrics that you can view for resources, see “Performance
metrics” on page 283.
Specify granularity
Determine the granularity of the data that is shown in a performance view.
Granularity determines the points that are shown on the y-axis of a chart,
the points on the lines in a chart, and the rows in a table. When you first
(daily)
Set the granularity to show 1-day increments for performance
information that is shown on the chart and table.
This granularity is only available if the time range of the chart is
more than 1 day.
(hourly)
Set the granularity to show one-hour increments for performance
information that is shown on the chart and table.
This granularity is only available if the time range of the chart is
more than 1 hour.
(Sample)
Set the granularity to match the frequency of data collection by a
performance monitor. For example, if a performance monitor is
scheduled to collect sample data every 15 minutes, each point on
the chart is shown in 15-minute increments.
This granularity is only available if the time range of the chart is
less than 2 weeks.
If the performance monitor collects sample data at 1-minute
intervals, data is displayed as 1-minute intervals in the chart only
when data is available for all of the selected time range. If data is
not available at 1-minute intervals for any portion of the selected
time range, the data is displayed in 5-minute intervals.
For example, the performance monitor for a resource collects
sample data every 5 minutes. Six hours ago, the performance
monitor was changed to start collecting data every minute. You
want to view sample data for the resource for the last 12 hours.
However, the performance monitor did not collect sample data
every minute for 6 of the last 12 hours. Therefore, the data is
displayed in 5-minute intervals rather than 1-minute intervals.
Synchronize the time range across all the open performance views
Synchronize the time range across all the performance views that are
displayed in separate browser windows. Use this action when you change
the time range in a performance view and want to apply the same time
range to the other performance views.
Restriction: This action affects only the performance views that are
displayed in separate browser windows. The time range of the
performance view that is shown as part of the main window for the GUI is
not affected.
For example, you can view the storage system volumes that are assigned
to a server. You can then open separate browser windows for the host
connections, pools, and managed disks that are related to one of the
volumes. If you change the time range in the performance view for host
connections, click the synchronize button to apply the same time range to
the views for pools and managed disks. The performance view of the
original volume is not changed.
Actions for managing the resources in the chart legend
The chart legend in bottom section of the view shows more information
about the selected resources. This information is organized into rows and
columns, where each row represents a resource.
When you select one or more resources in the legend, the following actions
are available in the Actions menu:
For example, when you view the performance of a SAN Volume Controller, you
can right-click it in the chart legend to open a performance view for its internal
and related resources, such as disks, volumes, ports, managed disks, and back-end
storage.
The type of resource determines the internal and related resources that you can
view. The following tables show the internal and related resources that are
available when you right-click a resource in the chart legend.
Table 29. Resources that you can view for DS6000, DS8000, and ESS storage systems in
the chart legend
Right-click the resource in Right-click the resource in
the chart legend to view the the chart legend to view the
performance of the performance of the
Resource in the chart legend following resources following related resources
Storage system Volume, RAID array, pool, Storage virtualizer, switch
controller, host connection,
port
Table 30. Resources that you can view for SAN Volume Controller, Storwize V3500,
Storwize V3700, Storwize V7000, and Storwize V7000 Unified storage systems in the chart
legend
Right-click the resource in Right-click the resource in
the chart legend to view the the chart legend to view the
performance of the performance of the
Resource in the chart legend following resources following related resources
Storage system Volume, pool, node, I/O Back-end storage system,
group, disk, managed disk, storage virtualizer, switch
host connection, port
Volume Storage system, pool, node, None
I/O group, disk, managed
disk, host connection
Pool Storage system, volume, None
node, I/O group, disk,
managed disk, host
connection
Node Storage system, volume, None
pool, I/O group, disk,
managed disk, host
connection, port
I/O group Storage system, volume, None
pool, node, disk, managed
disk, host connection, port
Disk Storage system, volume, None
pool, I/O group, node,
managed disk, host
connection
Managed disk Storage system, volume, Back-end volume
pool, node, I/O group, disk,
host connection
Table 31. Resources that you can view for IBM Spectrum Scale in the chart legend
Right-click the resource in Right-click the resource in
the chart legend to view the the chart legend to view the
performance of the performance of the
Resource in the chart legend following resources following related resources
Storage system File system, node None
File system Storage system, node None
Node Storage system, file system None
Table 32. Resources that you can view for IBM Spectrum Accelerate in the chart legend
Right-click the resource in Right-click the resource in
the chart legend to view the the chart legend to view the
performance of the performance of the
Resource in the chart legend following resources following related resources
Storage system Module, pool, volume, host Storage virtualizer, switch
connection, port
Module Storage system, pool, None
volume, host connection,
port
Pool Storage system, module, None
volume, host connection
Volume Storage system, module, Managed Disk
pool, host connection
Table 33. Resources that you can view for XIV systems in the chart legend
Right-click the resource in Right-click the resource in
the chart legend to view the the chart legend to view the
performance of the performance of the
Resource in the chart legend following resources following related resources
Storage system Module, pool, volume, host Storage virtualizer, switch
connection, port
Module Storage system, pool, None
volume, host connection,
port
Pool Storage system, module, None
volume, host connection
Volume Storage system, module, Managed Disk
pool, host connection
Table 34. Resources that you can view for IBM Spectrum Accelerate in the chart legend
Right-click the resource in Right-click the resource in
the chart legend to view the the chart legend to view the
performance of the performance of the
Resource in the chart legend following resources following related resources
Storage system Module, pool, volume, host Storage virtualizer, switch
connection, port
Module Storage system, pool, None
volume, host connection,
port
Pool Storage system, module, None
volume, host connection
Volume Storage system, module, Managed Disk
pool, host connection
Table 35. Resources that you can view for SMI-S BSP systems in the chart legend
Right-click the resource in Right-click the resource in
the chart legend to view the the chart legend to view the
performance of the performance of the
Resource in the chart legend following resources following related resources
Storage system Volume, port Storage virtualizer, switch
Volume Storage system Managed disk
Storage system port Storage system Switch port
Table 36. Resources that you can view for switches in the chart legend
Right-click the resource in Right-click the resource in
the chart legend to view the the chart legend to view the
performance of the performance of the
Resource in the chart legend following resources following related resources
Switch Port Storage system, switch
Port Switch Storage system port, switch
port
The link in the bookmark or favorite stores details of the performance view, such
as the resources, metrics, interval, and other details. The link also stores the time
period that is specified in the time selector at the top of the chart.
You can also copy the URL from the address bar if you want to share the URL
with colleagues.
Task Steps
View the performance alerts for a specific 1. In the menu bar, choose one of the
storage system following options:
v Storage > Block Storage Systems
v Storage > File Storage Systems
2. Double-click a storage system.
3. Click Alerts in the General section.
View all the performance alerts that were 1. In the menu bar, select Network >
generated for switches Switches.
2. Click the Alerts tab.
2. Right-click the performance alert that you want to view and select View Alert.
In this view, a chart shows the performance of the resource that violated the
threshold and generated the alert. The time range of the chart is 2 hours before
and 2 hours after the violation occurred. The lines on the chart represent the
following values:
v The blue line represents the performance of the resource for the selected
metric.
v The red line represents the threshold that was violated.
v The dotted line represents the time when the violation occurred.
For certain storage systems, a ranked list of the 25 volumes that were the top
contributors to the workload on the resource where the threshold violation
occurred might be displayed below the chart. This list is shown under the
following conditions:
v The performance threshold was violated on an internal resource other than a
port.
v The performance threshold was violated on any of the following storage
systems:
– DS6000
– DS8000
– XIV
– IBM Spectrum Accelerate
– ESS
– SAN Volume Controller
– Storwize V3500
– Storwize V3700
– Storwize V7000
– Storwize V7000 Unified
You can also view the servers or hosts to which those volumes are assigned.
3. Optional: To access the full performance view of a resource that violated the
threshold, click the open performance view icon on the chart.
You can map the application to the storage resources that the application uses to
do capacity trending, health monitoring, and performance troubleshooting tasks.
For example, a department might use 15 applications and be part of another five
departments. Also a department might share storage resources with another
department, subdepartment or application even if they do not belong in the same
Application administration
Go to the pages for creating and administering the applications that you want to
monitor.
Table 38. Create and administer applications and subcomponents
Actions Navigation
Create applications and assign storage 1. In the menu bar, go to Groups >
resources directly to the application. Applications.
2. On the Applications page, click Create
Application.
3. On the Select a Method page, click
Assign storage resources to the
application.
Create subcomponents that can have its own 1. In the menu bar, go to Groups >
storage resources. Applications.
2. On the Applications page, click Create
Application.
3. On the Select a Method page, click
Create a subcomponent that can have
its own set of storage resources.
Create a filter to use in assigning resources. 1. In the menu bar, go to Groups >
Applications.
2. On the Applications page, right-click a
row in the Applications list and click
View Details.
3. In the General section, click Filters.
4. On the Filters page, click Create Filter.
Add applications as subcomponents to an 1. In the menu bar, go to Groups >
application. Applications.
2. Right-click the applications that you
want to add as subcomponents, and then
click Add to.. > Application.
3. On the Add to Application page, select
the applications and click Save.
Add applications to departments. 1. In the menu bar, go to Groups >
Applications.
2. On the Applications page, select one or
more applications, right-click and then
click Add to.. > Department.
3. On the Add to Department page, select
the applications that you want to add as
members and click Save.
Department administration
Go to the pages for creating and administering the departments that you want to
monitor.
Related tasks:
“Monitoring capacity usage at different levels of a business hierarchy” on page 64
The monitoring and management of applications and departments enables you to
monitor storage capacity usage, recognize trends, monitor health status, and
troubleshoot performance of the storage resources in your business organization.
“Comparing storage usage in each department” on page 66
In this scenario, you compare the storage usage in each department within your
organization to spot a potential storage usage issue.
“Using applications and subcomponents to monitor capacity and space usage” on
page 68
To monitor the performance, capacity, and space usage of the applications in your
business organization, create applications and subcomponents. You can also add
applications to departments so that storage capacity and usage can be monitored in
an overall business hierarchal manner.
“Viewing storage capacity and usage trends” on page 69
You can view the capacity and usage trends of storage resources used by an
application and subcomponents to diagnose how much storage a particular
application is using in relation to the other applications and departments in the
business hierarchy.
Applications
View information about storage area network resources that you can model by
using applications in your business environment. The monitoring and management
of applications enables you to perform capacity trending, health monitoring, and
performance troubleshooting tasks.
The Applications page shows capacity information about the applications that are
monitored by IBM Spectrum Control and the actions that you can use to view and
manage them. To see more detailed information, view properties and details for
the application. If the application is associated with a department, information
about that department is also shown.
The following information shows the resources and objects that can be added to
the application.
Table 40. Resources and objects that can be added to the application
Resources or objects that can be added to the
Object application
v Applications
v Servers
v Hypervisors
v Volumes
v Data Stores
Application v Shares
v File Systems (Only server file systems that are
monitored through a Storage Resource Agent.)
v Filesets
v Volume Groups
v Virtual Machines (Can only be added with the CLI
modifyappgroup command)
In this scenario, you want to monitor the capacity, space usage, and performance
of a DB2 application.
The DB2 application has two subcomponents, which you want to monitor
separately:
Tip:
When you create complex application models for applications, it is not necessary to
create a filter to associate storage resources with the application because the
application inherits the storage resources that are associated with its
subcomponents. However, if you want to monitor storage resources that are not
associated with the subcomponents, you must create a filter that associates the
additional storage resources that you want to monitor with the application.
You can now view information about the capacity, space usage, and performance
of the storage resources on the Overview page for the application and
subcomponents.
Creating applications:
Use the GUI to create applications, assign resources, and subcomponents for
monitoring by IBM Spectrum Control.
To determine the storage capacity usage by the storage resources that the
applications use, you create a data model of the applications for your storage
environment.
When the application creation is created, you can view status information, block
and file capacity and additional data on the Applications page and in properties.
For a detailed view of the application and related resources, on the Applications
page, right-click the application and select View Details. To see the subcomponents
for the application, click Subcomponent on the application details page.
Related tasks:
“Adding subcomponents” on page 175
You created a new application and a subcomponent, with their own set of
resources and added it to your business hierarchy. You now want to add another
level to your business hierarchy.
“Using filters to assign resources to applications”
Instead of manually adding the resources that you want to assign to new or
existing applications, you can create filters to assign resources based on name
pattern matching.
“Viewing information about applications” on page 176
You can view information about the application that you created as related
resources, filters that are used to populate the application with resources, any
subcomponents, capacity trending and performance information.
Instead of manually adding the resources that you want to assign to new or
existing applications, you can create filters to assign resources based on name
pattern matching.
When you create a filter to assign storage resources to applications, the resources
that match the criteria that are defined in the filter are automatically added to the
application or subcomponent (member application).
The use of wildcard characters enables you to customize and expand your search
to add related resources. The asterisk (*) and the question mark (?) can be used as
wildcard characters. The asterisk matches one or more characters. The question
mark matches a single character. Use a comma-separated list to add multiple
resources. As new resources are added or modified and they match the existing
If you edit a filter, the resources that no longer match the filter are removed from
the application and the resources that now match the filter are added to the
application.
If you remove the filter, all storage resources that match the filter criteria are
removed from the application.
You can only select one resource type filter at a time during the creation workflow,
but you can create multiple filters for applications.
The General section of the details page shows the number of filters that you
created, for example, Filters (6). Click Filters to access the Filters page and see the
filters that were created. For example, The number of matches: 26, which indicates
there are 26 matches for the filter criteria. Click the link to see the resources for the
filter matches that are available.
Tip: To view a description of a field on the Create Filter page, hover the mouse
pointer over the help icon for that field.
Related tasks:
“Creating applications” on page 171
To monitor storage capacity, troubleshoot performance, and view storage area
network dependencies for applications, you can create applications for monitoring
in IBM Spectrum Control.
“Adding subcomponents” on page 175
You created a new application and a subcomponent, with their own set of
resources and added it to your business hierarchy. You now want to add another
level to your business hierarchy.
You created a new application and a subcomponent, with their own set of
resources and added it to your business hierarchy. You now want to add another
level to your business hierarchy.
After the subcomponent is created, you can view the results on the Subcomponent
page and in the properties. For a more detailed view of the subcomponent, select
the subcomponent from the Subcomponent page and click Actions > View Details.
The resource is added to the application and is displayed on the Applications page.
Related tasks:
“Using filters to assign resources to applications” on page 172
Instead of manually adding the resources that you want to assign to new or
existing applications, you can create filters to assign resources based on name
Chapter 5. Managing resources 175
pattern matching.
The application details shows information about the specific application. The
information is available from the following sections on the page:
v Overview: The overall capacity trending about the application and performance
information. An interactive breadcrumb that shows the hierarchy of applications
and departments and a list of all the top level applications.
v Properties: The key information about the application.
v Filters: The number of filters created and the filtering criteria used for the
resources that were added to the application.
v Subcomponents: The number of subcomponents that are a members of the
selected application. If there is more than one subcomponent, the number of
subcomponents is displayed.
v Related Resources: The information about the resources that are related to the
application.
The applications and subcomponents are removed and are no longer displayed on
the Applications page.
To remove subcomponents from within the direct context of the application, use
these steps:
1. In the menu bar, go to Groups > Applications.
2. On the Applications page, select an application from the Application list and
right-click View Details.
3. Optional: Select a application from the Applications page and right-click View
Properties.
a. Click the Subcomponents tab and continue with steps 5-6.
4. On the application details page, click Subcomponents in the General section.
5. On the Subcomponents page, select the subcomponent and right-click Remove
from Application.
6. Confirm that you want to remove the subcomponent and click Remove.
Resources that were added through a filter match are removed if the filter is
modified and no longer includes the resource that was removed from the
application, the filter is removed from IBM Spectrum Control, or the resource is
removed from IBM Spectrum Control. Resources can be added back to the
application if the filter is modified and includes the resource that was originally
removed, a new filter is created that matches the resource, the resources are added
to IBM Spectrum Control, or you use the Add to Application action.
Resources that are automatically added to an application because they are related
to resources that were explicitly added to the application are not removed from the
application. The resources are automatically removed when the corresponding
related resource that was added to the application, is also removed from the
application.
For example, you add a server to the application that has one volume from a
storage system. The volume is added as a related resource of that server in the
application. If you attempt to remove the volume from the application, the volume
is not removed since it is a related resource. The volume is only removed when the
server, that was explicitly added to the application, is removed.
The resources that were added to the application are removed from the
application.
Related tasks:
“Using filters to assign resources to applications” on page 172
Instead of manually adding the resources that you want to assign to new or
existing applications, you can create filters to assign resources based on name
pattern matching.
Departments
View information about departments and structure the hierarchy to mirror your
business organization. Monitor the detailed information about capacity and space
usage that is collected for departments and subdepartments, and monitor the
performance of the applications and the application subcomponents that are added
to departments and subdepartments.
The Departments page shows storage capacity information about the top level
departments, the subdepartments and any applications that belong to the
department that are monitored by IBM Spectrum Control and the actions that you
can use to view and manage the resources that are defined to them. To see more
detailed information, view properties and details for the department.
The following information shows the objects that you can add using the Add to
Department function.
Table 41. Objects that can be added to the department
Object Objects that can be added to the department
v Applications
v Departments
Department
In this scenario, you want to monitor the capacity and space usage of departments
in a business organization that sells books. You also want to monitor the
performance of the storage resources that are associated with the applications or
application subcomponents that are used by the departments.
The sales department of the organization, Book Sales, has these subdepartments:
v Wholesale
v Retail
v Online
To monitor the storage resources that the Books Sales department uses and that
each of its subdepartments use, complete these tasks:
v
v Create a department for Book Sales.
v Create the Wholesale, Retail, and Online subdepartments that you want to add
to the department:
– Create the subdepartments as departments.
– Add the departments as subdepartments to the department.
– Add the applications to the subdepartments.
You can now view charts and information about the capacity and space usage of
the department and each of the subdepartments on the Departments page and the
Subdepartments page. You can also view charts and information about the
Tip: In the Subdepartments column for the department on the Departments page,
the name of the subdepartment is shown. If you add two or more departments to a
subdepartment, the number of subdepartments is shown. To view information
about the subdepartments, click the name of the subdepartment or the number.
You can view the total capacity and space usage for the department and the
capacity and space usage for each of the subdepartments. You can add to your
department hierarchy by adding more applications and departments.
Creating departments:
To model the storage capacity that is consumed in a department for your business
environment, in accordance with other department and application members,
create departments for monitoring in IBM Spectrum Control.
To see the applications that you added to your department, see the details page
and click Applications.
To further enhance your data modeling at the department level and to add to your
overall business hierarchy for monitoring, add an existing subdepartment or create
a new subdepartment.
To see the subdepartment you created, see the Subdepartments column on the
Departments page or click Subdepartments on the details page.
To further enhance the data storage modeling in a business environment and see
the storage capacity that is used at the different levels of your business hierarchy,
add applications to departments. The departments you select from the Add to
Department page become parents of the selected applications.
The department details page shows information about the specific department. The
information is available in the following sections on the page:
v Overview: The overall capacity trending and performance information about the
department. An interactive breadcrumb that shows the hierarchy of the
departments and applications and a list of all the top level departments.
v Properties: The key information about the department.
v Applications: The applications that belong to the department. If there is more
than one application, the number of applications is displayed.
v Subdepartments: The subdepartments that belong to the department. If there is
more than one subdepartment, the number of subdepartments is displayed.
v Related Resources: Information about related resources in the storage
environment that the applications, which belong to the department, are using or
are connected to.
To remove applications from within the context of a department, use these steps:
1. In the menu bar, go to Groups > Departments.
2. On the Departments page, select a department from the list and right-click
View Details.
3. Optional: Select a department from the Departments page and right-click View
Properties.
a. Click the Applications tab and continue with steps 5-6.
4. On the department details page, click Applications from the General section.
5. On the Applications page, select the application and right-click Remove from
Department.
6. Confirm the information.
7. Click Remove.
The applications that were added within the context of a department are eligible
for removal from within department.
Related tasks:
“Viewing information about departments” on page 182
You can view detailed information about departments for use in storage capacity
monitoring and performance troubleshooting. You can view additional information
on the applications and subdepartments that are used to establish a hierarchal
business structure.
When you move your mouse pointer over an icon in the breadcrumb, you see the
siblings for that application or department. If you move your mouse pointer, for
example, over the Data subcomponent, the related application and department
elements are shown.
The visual representation of the hierarchy stops when either there are no
additional parents or multiple parents are encountered from the selected
application or department. When multiple parents are encountered, the number of
parents are shown in parenthesis. For example, Multiple (2). Moving the mouse
pointer over Multiple shows a list of the parents. The siblings of multiple parents
are not shown.
Move your mouse pointer over a sibling in the breadcrumb and it becomes a name
link. Click the application or department name link to navigate to the details for
that application or department and view the breadcrumb if it exists.
You can add resources directly on the Overview page for applications from the
breadcrumb. For example, in this case, you create an application named DB2 and
create two subcomponents, Logs and Data. On the Overview page for the Logs
subcomponent, click the Logs subcomponent name link in the breadcrumb and
click Filters to create a resource filter for that subcomponent. Then, click the Data
subcomponent name link and create a resource filter for that application
subcomponent. To see a visual representation of the hierarchy for applications,
subcomponents, departments, and subdepartments click View Details.
Related tasks:
“Creating an application hierarchy” on page 170
To monitor, the capacity, space usage, and performance of the storage resources
that your applications use, create application models.
“Creating a department hierarchy” on page 179
To monitor the capacity and space usage of the department, you want to create a
department hierarchy and associate applications with the department hierarchy.
You can also monitor the performance of the storage resources that are associated
with the applications that you add to the department hierarchy.
You can export information that is shown on the application and department list
and detail pages.
Applications and departments list and detail pages
You can export information about the top level applications and
departments and the related resources that are shown on application and
department list and detail pages.
For example, you can export information about monitored applications and
their subcomponents and departments on the Applications page. When
you select the export action, the generated file includes the column values
for each monitored application in the list.
For example, you can export information about the servers that are
associated with an application on the details page.
1. In the GUI, go to the Applications or Departments page and select applications
or departments for which you want to export information.
2. Click Actions and select Export > file_format, where file_format represents the
format that you want to use for a file. The following formats are available:
CSV (comma-separated values)
A CSV file is a file that contains comma-delimited values and can be
viewed with a text editor or imported into a spreadsheet application.
The information in a CSV file has the following format:
"Column_name","Column_name","Column_name","Column_name","Column_name","Column_name"
"data","data","data","data","data","data"
Tip: When you export a table of data that contains many columns, the
rows in that table might span multiple pages in the resulting PDF. For
example, if a table contains 20 columns, then the row for a specific
resource might be shown on more than one page (10 columns on the
first page and 10 columns on the second page).
To reduce the number of pages that a table spans, before you select the
export action, hide the columns that you do not want to include in the
PDF. Continue hiding columns until the table no longer spans multiple
pages.
If a resource does not map storage to other resources, or the resource is not
assigned storage from other resources, the data path view is not available.
Depending on how resources are configured, a data path can show between three
to six types of top-level resources. For example, a data path with three types of
top-level resources might show the following relationships:
server <> fabric <> storage system
A data path with six types of top-level resources might show the following
relationships:
virtual machine <> hypervisor <> fabric <>
storage virtualizer <> fabric <> storage system
Before you can view a data path, you must complete the following tasks:
v Add the resource that has the data path you want view. For information about
how to add a resource, see “Adding resources” on page 75.
Tip: Resources that are not monitored by IBM Spectrum Control are also shown
in a data path view. However, detailed information about their status and
internal resources is not available.
You can use the data path view to complete the following actions:
v View the path of data that is shared between resources. The data path view
shows only the resources that have storage mapped between them. For example,
if you view the data path for a storage system, only the host connections that
are assigned volume space from that storage system are shown. Host
connections that are connected to the storage system, but do not have storage
assigned storage to them, are not shown.
v View the fabrics through which resources in a data path are communicating.
v View the propagated status of the top-level resources that are in a data path.
v View the status of the internal resources for top-level resources that are in a data
path.
v Customize the appearance of the data path view to suit the needs of your
environment.
v Export the data paths view as an image or CSV file.
Information about a data path is organized into two views: a topology view and a
table view. The topology view shows icons for connected resources and uses lines
to represent the path of data through them. The table view includes a row for each
resource in a data path. The row is divided into columns that contain information
about the resource.
The following table shows the icons for each type of resource that can be shown in
a data path.
Table 42. Resource icons in a data path
Resource Icon
Server (with agent)
Virtual machine
Fabric
Virtual fabric
DS8000
DS6000
Storwize V70002
XIV
Some resources in a data path might be shown with an unknown status. Resources
can have an unknown status if they not monitored by IBM Spectrum Control, but
are connected to other, monitored resources. IBM Spectrum Control uses the
information that it collects about monitored resources to determine basic
information about the connected resources that are not monitored.
For example, if a host connection is assigned volumes, but IBM Spectrum Control
is not monitoring the fabric through with the host connection communicates with
the storage system, the fabric is shown with an unknown status.
Zooming in
You can use the zoom buttons in the toolbar or the mouse to magnify areas in a
data path.
1. To zoom in on a specific area in a data path, click the Zoom to selected button
and click and drag the mouse pointer over the area.
2. Optional: To use the mouse to zoom in on a specific area in a data path, move
the mouse pointer over the area where you want to zoom in and scroll the
middle mouse button forward.
3. Optional: To zoom in on the area that is in the center of the view, click the
Zoom in button .
4. Optional: To adjust the zoom level of the view so that all the resources in a
data path are shown at the same time, click the Fit to view button .
Zooming out
You can use the zoom out button in the toolbar or the mouse to zoom out in the
view.
1. To zoom out from the area that is in the center of the view, click the zoom out
button .
2. Optional: To use the mouse to zoom out from a specific area in a data path,
move the mouse pointer over the area where you want to zoom out and scroll
the middle mouse button backward.
3. Optional: To adjust the zoom level of the view so that all the resources in a
data path are shown at the same time, click the Fit to view button .
Hierarchical
Organize resources in a vertical format. Resources that use storage are
shown at the top of the view. Resources that provide storage are shown
at the bottom of the view.
Tree
Organize resources in a vertical and horizontal layout.
Printing a view
You can print the current view of a data path in the Topology View tab. The
printing capability is not available in the Table View tab.
Provisioning storage
You can assign storage to servers, hypervisors, and clusters on servers and
hypervisors in the GUI. You can assign storage to hypervisors with the vSphere
Web Client extension for IBM Spectrum Control.
When you assign storage, you must associate the storage with a service class. You
can associate the storage with a default service class such as gold, silver, or bronze,
or you can create a user-defined service class. You can also create capacity pools to
restrict the provisioning of storage to a defined set of storage resources such as
pools on a storage system in a particular location.
To provision storage, you are required to specify only the storage capacity and
storage quality that is required. After volumes are created, IBM Spectrum Control
can analyze and optimize volume performance.
To configure IBM Spectrum Control for provisioning, complete the following tasks:
1. Assign storage pools to tiers by setting the tier level of each storage pool. The
tier levels are number tags that can reflect any tier structure in the
environment.
You must assign storage pools to tiers to later provision volumes that require a
certain tier level and to optimize the placement of volumes. Storage pools do
not need to be assigned to tiers to provision volumes that do not require a tier
level, or to provision file shares.
2. Create service classes. A service class is a set of properties that describe
capabilities and characteristics of storage resources. A service class typically
describes a particular quality of service, and is used during provisioning to
describe storage requirements. For example, a block-storage service class
specifies properties such as a required RAID level, and whether storage
resources must be able to encrypt or thin provision volumes.
3. Optional: Create capacity pools. You can restrict provisioning requests to a
capacity pool. Capacity pools are groups of storage resources. You can use
capacity pools to separate storage resources in any way that serves the needs of
your environment or business. For example, a capacity pool might contain the
storage resources that are allocated to a particular department or division of
your business, or to a particular application.
The Create Service Class wizard guides you through the steps to create a service
class. When you provision a volume or share, you define storage requirements by
specifying a service class. A block-storage service class specifies the requirements
for the block-storage resource from which a new volume is allocated. A file-storage
service class defines requirements for the file storage resources from which a new
share is allocated.
You can associate a service class with one or more capacity pools. If you do, future
provisioning requests can be satisfied only by storage resources in the specified
capacity pools.
You can selectively grant users who do not have administrator privileges
permission to provision storage by using the service class.
Restrictions:
v To create a block-storage service class, you must have the IBM Spectrum Control
Advanced Edition license.
v To associate the service class with a capacity pool, one or more capacity pools
must be defined in the IBM Spectrum Control database. If no capacity pool is
defined, the Specify Capacity Pool page of the wizard is not displayed.
Start this task at the Service Classes page. To open the Service Classes page, select
Advanced Analytics > Cloud Configuration > Work With Service Classes. To
create a service class, complete the following steps:
1. From the Service Classes page, click Create Service Class. The Create Service
Class wizard opens.
2. Select the type of service class that you want to create:
v To create a block-storage service class, click the Block icon.
v To create a file-storage service class, click the File icon.
3. In the Define Properties page, complete the following steps:
a. Specify a name for the service class.
b. Optional: Specify a service class description. Descriptions are displayed in
the table of service classes on the Service Classes page.
c. Specify the general attributes of the service class. Most of the general
properties specify requirements for provisioning. Some of the general
properties specify configuration instructions for the storage resources or for
the volumes or shares that are provisioned from them.
Tip: To display help information about a service class property, move the
mouse pointer over the field or control. Then, move the mouse pointer over
the question mark icon displayed next to the field.
4. Optional: Specify or modify the advanced properties of the service class.
a. From the Define Properties page, click Advanced.
b. If you are creating a block-storage service class, and thin provisioning is
enabled for the service class, specify configuration instructions for thin
provisioning.
c. If you are creating a block-storage service class, select how the multipath
driver on the host is configured. For hypervisors, the multipath driver is
configured only if provisioning is initiated from the vSphere Web Client
extension for IBM Spectrum Control.
You can view the provisioning requirements and storage constraints that a service
class defines. You can also view the volumes or shares that were provisioned by
using the service class.
From the Service Classes page, you can open a properties page to view the
following information for a service class:
v The properties of a service class, such as the required RAID level or storage tier
for a block-storage service class.
v The storage constraints that are imposed by the service class. The service class
can allow provisioning from all available storage, or can limit provisioning to
one or more capacity pools.
v The users who can provision storage by using the service class.
v The volumes or shares that were provisioned by using the service class.
v The candidate storage for the service class. The candidate storage is the set of
storage resources that can provide the service class.
To open the service class properties window from the Service Classes page,
complete the following steps:
1. In the menu bar in the web-based GUI, go to Advanced Analytics > Cloud
Configuration, and click Work With Service Classes. The Service Classes page
is displayed.
2. From the list of service classes, select the service class, and then select Actions
> View / Modify. The service class properties window is displayed.
You can modify the attributes of a service class to change the provisioning
requirements, capacity pool storage constraints, user permissions, and service class
name.
Start this task at the Service Classes page. To open the Service Classes page, select
Advanced Analytics > Cloud Configuration > Work With Service Classes. To
modify a service class, complete the following steps:
1. From the list of service classes, select a service class and then select Actions >
View / Modify. The service class properties window is displayed.
2. Optional: Click the General tab to modify the general attributes of the service
class. Most of the general properties specify requirements for provisioning.
Some of the general properties specify configuration instructions for the storage
resources or for the volumes or shares that are provisioned from them.
Tip: To display help information about a service class property, move the
mouse pointer over the field or control. Then, move the mouse pointer over the
question mark icon displayed next to the field.
3. Optional: Specify or modify the advanced properties of the service class.
a. From the General tab, click Advanced.
b. If you are modifying a block-storage service class, and thin provisioning is
enabled for the service class, specify configuration instructions for thin
provisioning.
c. If you are modifying a block-storage service class, select how the multipath
driver on the host is configured. For hypervisors, the multipath driver is
configured only if provisioning is initiated from the vSphere Web Client
extension for IBM Spectrum Control.
d. Create custom requirements for the service class by specifying up to three
custom tags. To provide the service class, storage resources must have all
the same tags that are specified in the service class.
4. Optional: Modify storage constraints. If one or more capacity pools are defined
in the IBM Spectrum Control database, you can associate the service class with
one or more capacity pools. If capacity pools are associated with the service
class, future provisioning requests that specify the service class can be satisfied
only by storage resources in the capacity pools. If a capacity pool was
previously associated with the service class, you can disassociate it from the
service class.
5. Optional: Modify user permissions. By default, users must be assigned to the
Administrator role to provision storage. However, you can selectively grant
users who are limited to the Monitor or External Application role permission to
provision by using this service class. You can also specify whether
administrator approval is required to run provisioning tasks that are created by
these users.
If users in the Monitor or External Application roles have permission to
provision by using the service class, you can revoke that permission. You can
specify that only administrators can provision by using the service class, or you
can selectively remove users. To remove a user, right-click the user name in the
table and then select Remove from the context-sensitive menu.
Deleting a service class does not affect the storage volumes or NAS shares that are
already provisioned by using the service class. However, the storage volumes or
NAS shares are no longer associated with any service class. When a volume that is
not associated with a service class is optimized by the Optimization wizard, the
volume can be migrated to any available storage pool. The storage pool to which
the volume is migrated might not satisfy the requirements of the service class that
was specified when the volume was provisioned.
A service class can specify tags to create custom requirements for provisioning.
Add the same tags to storage resources that satisfy the custom requirements. When
the service class is specified during provisioning, only the tagged resources are
candidates for provisioning.
When you provision storage, you indicate your storage requirements by specifying
a service class. Certain properties of the service class describe capabilities that
storage resources must have to be a candidate for provisioning. In addition to the
default properties, a service class can define custom requirements by specifying up
to three custom tags. To provide the service class, a storage resource must have all
the same tags as the service class. The ability to define custom requirements by
tagging service classes and storage resources gives you more control over the
selection of storage resources during provisioning. By using tags, you can filter the
candidates for provisioning by using any criteria that you choose.
When you provision shares, you specify the requirements by using a file-storage
service class. Based on the requirements of the service class, IBM Spectrum Control
identifies a file system or Network Shared Disk (NSD) for the share. If the service
class specifies tags, only file systems and NSDs that have all the same tags are
candidates for provisioning. If a file system or NSD is not tagged, any tags on the
containing storage system also apply to the internal resource.
If you are going to use the VMware vSphere Web Client extension to provision file
shares, verify whether you must provide IBM Spectrum Control with an access
path host replacement.
You need to provide an access path host replacement if the cluster name of an IBM
SONAS or Storwize V7000 Unified is not a valid host name that is registered with
a Domain Name System (DNS) server.
Complete the following steps to verify cluster host names and to provide access
host name replacements where necessary:
1. In the menu bar, go to Storage > Block Storage Systems.
You can add storage resources to a capacity pool from resource list pages such as
the Storage Systems page and the Pools page.
When you add a storage system to a capacity pool, any storage pool, file system,
or IBM SONAS NSD that is an internal resource of that storage system is also
indirectly assigned to the capacity pool.
Restriction: A resource can be assigned to only one capacity pool. When you
attempt to add one or more resources to a capacity pool that are already assigned
to different capacity pool, IBM Spectrum Control displays a message that lists the
resources and their capacity pool assignments. When a message is displayed,
ensure that you want to change the capacity pool assignments for the listed
resources.
Tip: The list of capacity pools and the Create Capacity Pool window shows
capacity information. For the list of capacity pools, the Capacity column shows
a bar that summarizes the used and free space in each capacity pool. In the
Create Capacity Pool window, a capacity bar summarizes the used and free
space of the resources that are being added to the new capacity pool. Move the
mouse pointer over the bar to display a text summary and details of the
capacity usage.
3. Take one of the following actions:
v If the Create Capacity Pool window is displayed, go to step 4 on page 202.
v If a list of capacity pools is displayed, add the selected resources to an
existing capacity pool or to a new capacity pool.
You can view details of a capacity pool, such as its total capacity, used and
available space, and member resources.
The Capacity Pools page lists all of the capacity pools that are defined in IBM
Spectrum Control. For any capacity pool in the list, you can open a window to
view more details about the capacity pool and its storage resources.
You can modify the attributes of a capacity pool such as its name and description,
and you can remove storage resources from a capacity pool.
When you delete a capacity pool, the storage resources that were added to the
capacity pool are no longer members of any capacity pool. Deleting a capacity pool
does not affect any volumes or NAS shares that were provisioned from the
capacity pool. However, the volumes or NAS shares are no longer associated with
a capacity pool.
The Service Classes page in the web-based GUI displays the available space for
each block-storage service class. The available space is the amount of space that is
available across storage pools for new volumes of the service class. Typically, not
all pools are used in the available-space calculation. Some pools might be
eliminated because of the consolidated status of the pool or its storage system.
Other pools might be eliminated because they do not satisfy the requirements of
the service class. The set of storage pools that are used to calculate the available
space are also the candidates for provisioning by using the service class.
When you request storage volumes by using the Provision Storage wizard, you
specify the capacity that is required for one or more volumes, and you specify a
For each block-storage service class, IBM Spectrum Control calculates the available
space for volumes of that service class. Only storage pools that are candidates for
provisioning by using the service class are used to calculate the available space.
The candidates for provisioning are identified by eliminating storage pools that
cannot provide the service class, as follows:
v If a storage pool is a primordial pool or if it is formatted for count key data
(CKD) volumes, it is not a candidate for provisioning.
v If a storage system has a condition of Error or Unreachable, none of its internal
storage pools are candidates for provisioning. If a storage pool has a status of
Error, it is not a candidate for provisioning.
Although the condition of a resource might not have the same value as its
status, the condition is always at least as severe as the status. The condition
reflects the most severe status of any internal resource or the status of the
resource itself. If the condition of a resource is Normal, then its status is also
Normal.
Tip: The Service Classes page in the web-based GUI displays both the available
space and the unavailable space for a service class. The Unavailable Space
column shows the amount of storage that satisfies the requirements of the
service class, but is unavailable because of the consolidated status of the storage
system or its internal resources.
v If a service class allows provisioning only from certain capacity pools, any
storage pool that is not in a specified capacity pool is eliminated as a candidate
for provisioning.
If encryption is not allowed by the service class, only pools that are
not encrypted are candidates for provisioning.
Thin provisioning If thin provisioning is required by the service class, only storage
pools that are configured for thin provisioning are candidates for
provisioning. Thin provisioning is supported by the XIV, DS8000,
SAN Volume Controller, Storwize V7000, and Storwize V7000 Unified.
During provisioning, a thin-provisioned volume is created.
After the storage pools that can provide the service class are identified, IBM
Spectrum Control calculates the amount of space that is available for provisioning
new volumes of the service class. The calculated volume capacity is shown in the
Available Space column on the Service Classes page.
When you request one or more new volumes by using the Provision Storage
wizard, the candidates for provisioning are further refined and a provisioning task
is created which shows the recommended placement of the new volumes. The
same filtering that was used to determine the available space for the service class
is used, and is refined further as follows:
v A provisioning request specifies the set of storage pools from which the storage
can be provisioned. This set can be all the storage pools that are known to IBM
Spectrum Control, or can be limited to the storage pools in a particular capacity
Remember: Storage pools that have an overallocation percentage that does not
exceed the overallocation limit, are included in the available-space calculation.
However, if the overallocation percentage would exceed the overallocation limit
after the requested volume space is included, the pools are not candidates for
provisioning.
After the storage pools that can satisfy the provisioning request are identified, IBM
Spectrum Control finds the best location for the storage. The best location for the
storage is based on the unallocated volume space in the pool and performance
data. Preference is first given to storage pools and systems that already contain
volumes for the selected server or hypervisor. Preference is given to systems that
have available performance data.
For each file-storage service class, IBM Spectrum Control calculates the amount of
available space for NAS file shares of that service class. When you request file
shares of a particular service class, IBM Spectrum Control recommends the best
location for the shares from the available space.
The Service Classes page displays the available space for each file-storage service
class. The available space is the amount of space that is available across all IBM
SONAS and IBM Storwize V7000 Unified file systems and unused IBM SONAS
system NSDs that are known to IBM Spectrum Control, and that can satisfy the
requirements of the service class. The set of file storage resources that are used to
calculate the available space are also the candidates for provisioning by using the
service class.
When you request a file share by using the Provision Storage wizard, you specify
the capacity that is required for the share, and you specify a service class. You can
also specify a capacity pool from which shares must be provisioned. Based on the
requested size of the share and whether a capacity pool is specified, the candidates
for provisioning are further refined to include only the file storage resources that
have enough available space and are in the specified capacity pool. From the
remaining candidates for provisioning, IBM Spectrum Control creates a
provisioning task that identifies the best location for the new share.
For each file-storage service class, IBM Spectrum Control calculates the available
space for file shares of the service class. Only the file storage resources that are
candidates for provisioning by using the service class are used to calculate the
available space.
The candidates for provisioning are identified by eliminating storage resources that
cannot provide the service class, as follows:
v Only IBM SONAS and IBM Storwize V7000 Unified systems are supported for
provisioning file shares. No other storage system type is a candidate for
provisioning file shares.
v If a storage system has a consolidated status of Error or Unreachable, none of its
internal NSDs or file systems are included in the available-space calculation.
v If an NSD or file system has a consolidated status of Error, it is not included in
the available-space calculation.
Tip: The status of file systems is not displayed n the web-based GUI. View the
status on the NSD on which a file system resides to determine the file system
status.
v If the storage volume or NSD on which a file system resides has a consolidate
status of Error, the file system is not included in the available-space calculation.
Although the condition of a resource might not have the same value as its
status, the condition is always at least as severe as the status. The condition
reflects the most severe status of any internal resource or the status of the
resource itself. If the condition of a resource is Normal, then its status is also
Normal.
Tip: The Service Classes page in the web-based GUI displays both the available
space and the unavailable space for a service class. The Unavailable Space
column shows the amount of storage that satisfies the requirements of the
service class, but is unavailable because of the consolidated status of the storage
system or its internal resources.
Tip: You can see whether a service class restricts provisioning to one or more
capacity pools from the Service Classes page. On the Service Classes page, show
the Capacity Pools column, which is hidden by default.
v A file system or NSD must satisfy the requirements of every service class
property in the following table to be a candidate for provisioning. Other
properties of a service class are instructions for provisioning and do not affect
the storage placement determination.
Table 44. Filtering candidates for provisioning based on service class properties
Service class
attribute: Candidates for provisioning:
Shared storage / If the service class specifies dedicated storage, the share can be
Dedicated storage created only on an unused NSD within an IBM SONAS system. File
systems and other file storage resources are eliminated as candidates
for provisioning.
Resource tags Resource tags further refine the candidates for provisioning. A service
class can specify up to 3 resource tags. If resource tags are specified
for the service class, only file systems and NSDs that have all the
same tags are candidates for provisioning. If a file system or NSD is
not tagged, any tags on the containing storage system also apply to
the internal resource.
After the file storage resources that can provide the service class are identified,
IBM Spectrum Control calculates the amount of space that is available for
providing new files shares of the service class.
When you request a file share by using the Provision Storage wizard, the
candidates for provisioning are further refined and a provisioning task is created
which shows the recommended placement of the new share. The same filtering
that was used to determine the available space for the service class is used, and is
refined further as follows:
v A provisioning request specifies the set of file storage resources from which the
storage can be provisioned. This set can be all the storage resources that are
known to IBM Spectrum Control, or can be limited to the storage resources in a
particular capacity pool. Only the storage resources in the specified set are
candidates for provisioning. This set might be more restrictive than the set used
to calculate the available space for the service class.
v Any storage resource that cannot provide the requested capacity for the share is
eliminated as a candidate for provisioning.
The shares are created on file systems or IBM SONAS NSDs. After the file systems
and NSDs that can satisfy the provisioning request are identified, IBM Spectrum
Control identifies the best location for the storage. The best location for the storage
is based on the available space on the file system or NSD.
When you provision storage from a SAN Volume Controller, IBM Storwize, or IBM
FlashSystem family V840 or V9000 device, which does not have an existing host
definition for the fibre-channel ports, IBM Spectrum Control creates a new host
definition during the provisioning task. The new host definition can access only
one I/O group on the source device that you specified when you created the
provisioning task. To allow the new host definition to access any I/O group on the
source device, use the management application for the source device or use the
IBM Spectrum Control setdscfg command.
To change the host definition to allow access to any I/O groups on the source
device:
1. Start the IBM Spectrum Control CLI by issuing the tpctool command.
2. Issue the setdscfg command with the following values for the -property and
-context parameters:
a. Specify Configuration.RestrictNewHostsToIogroup as the property value.
b. Specify DiskManager as the context value and specify false as the context
parameter.
For example, to allow the new host definition to access any I/O groups on the
source device of the provisioning task:
tpctool setdscfg -url localhost:9550 -user ***** -pwd *****
-property Configuration.RestrictNewHostsToIogroup -context DiskManager false
NAS file shares can be provisioned only from IBM SONAS or Storwize V7000
Unified storage systems.
Specify the capacity that is required and the service class that you want to
associate with the provisioning task. For shares, you must also specify at least one
file access protocol. IBM Spectrum Control identifies the storage resources that can
provide the storage capacity and that meet the criteria that are specified for the
service class. From the set of storage resources that can provide the capacity and
service class, IBM Spectrum Control identifies the best location for the storage and
creates a provisioning task. Depending on the privileges that are associated with
your role, you can save, execute, or schedule the provisioning task.
You can provision volumes to one or more servers. If a server is a virtual machine,
the storage is provisioned to the hypervisor that is managing the server.
1. In the menu bar, go to Servers > Servers..
If the cluster is on servers that are virtual machines, the storage is assigned to the
hypervisors that manage the servers. The volumes are assigned to all of the nodes
in the cluster.
1. In the menu bar, go to Servers > Servers, and click Clusters.
The volumes are assigned to all of the nodes in the hypervisor cluster.
1. In the menu bar, go to Servers > Hypervisors, and click Clusters.
You can provision a NAS file share to one or more servers. The share is made
available to the selected servers, but is not automatically mounted from the
selected servers.
1. In the menu bar, go to Servers > Servers..
You can provision a NAS file share to a server cluster. The share is made available
to the servers in the cluster, but is not automatically mounted from the selected
servers.
You can provision a NAS file share to a hypervisor cluster. The share is made
available to the hypervisors in the cluster, but is not automatically mounted from
the selected hypervisors.
When IBM Spectrum Control creates a provisioning task, it identifies the best
location for the new storage that satisfies the requirements of the service class. If
automatic zoning is enabled, then, during provisioning, existing zones are used if
the server already has connectivity to the storage system. Otherwise, one or more
zones are created between a host initiator port and a controller, node, or module
port.
IBM Spectrum Control provides the following support for zone control and
management of Cisco switches and fabrics:
v the standard Cisco zone control capabilities
v the Cisco Enhanced Zoning features.
For Cisco zone control and management, SNMP agents must be configured for the
Cisco fabrics and switches. SNMPv3 is the preferred version.
When you use IBM Spectrum Control for zone control and management of Brocade
switches and fabrics, follow these guidelines:
v For Brocade fabrics, information is typically collected through Storage
Management Initiative (SMI) agents, also referred to as CIM agents.
v For zone discovery for any fabrics with Brocade switches or vendor Brocade
switches, you must have an SMI agent configured for the fabric.
You can provision block and file storage to hypervisors from storage devices that
are monitored by IBM Spectrum Control. You can monitor the progress of your
storage provisioning activities in task information in the vSphere Web Client.
Ensure that you complete the following tasks in IBM Spectrum Control:
v If you want to provision storage by using service classes to describe
performance and storage requirements and to implement multipathing policies,
ensure that the service classes are created in IBM Spectrum Control. IBM
Spectrum Control provides a number of predefined service classes, which you
can use, modify, or delete.
v If you want to provision storage by using capacity pools to specify your storage
requirements, ensure that the capacity pools are created in IBM Spectrum
Control.
v Before you provision storage to a hypervisor, ensure that the hypervisor is
added into IBM Spectrum Control. If the hypervisor belongs to a cluster, all the
hypervisors on that cluster must be managed by IBM Spectrum Control.
v Ensure that the hypervisor has fabric connectivity. If automatic zoning is
enabled, the fabrics and switches must be managed by IBM Spectrum Control.
For more information about configuring for storage cloud provisioning, see
http://www.ibm.com/support/knowledgecenter/SS5R93_5.2.9/
com.ibm.spectrum.sc.doc/fqz0_c_cloud_config.html.
Ensure that you complete the following tasks in IBM Spectrum Control:
v If you want to provision storage by using service classes to describe
performance and storage requirements, ensure that the service classes are created
in IBM Spectrum Control. IBM Spectrum Control provides a number of
predefined service classes, which you can use, modify, or delete.
v If you want to provision storage by using capacity pools to specify your storage
requirements, ensure that the capacity pools are created in IBM Spectrum
Control.
v Before you provision storage to a hypervisor, ensure that the hypervisor is
added into IBM Spectrum Control. If the hypervisor belongs to a cluster, all the
hypervisors on that cluster must be managed by IBM Spectrum Control.
v Determine whether you must set access path host name replacements. For more
information, see “Special consideration for provisioning by using the VMware
vSphere Web Client extension” on page 41.
For more information, see “Cloud configuration” on page 37.
The purpose of analyzing tiering is to tier volumes based on the I/O rate or I/O
density thresholds that you set. Depending on the conditions that are set,
recommendations are generated.
Storage costs can be reduced, for example, by moving volumes with low
workloads from higher and more expensive tiers to lower and less expensive tiers.
Storage performance can be improved and used more efficiently by moving
volumes with heavy workloads to the tiers that meet the workload requirements of
the volumes. When you implement the recommendations, you ensure that the
volumes are placed on the tiers that best match the workload requirements of the
volumes.
You can optimize the placement of volumes on the following storage virtualizers:
v SAN Volume Controller
v Storwize V7000
v Storwize V7000 Unified block storage
v FlashSystem V9000 and FlashSystem V840
Learn more: For information about the components that can be used with IBM
Spectrum Control Version 5.2 (or later), see IBM Spectrum Control
interoperability matrix at http://www.ibm.com/support/
docview.wss?uid=swg21386446.
Volumes can be moved to tiered storage pools on the same storage virtualizer, but
volumes cannot be moved from one storage virtualizer pool to another storage
virtualizer pool.
Before you analyze tiering or balance pools, you must set the tier level of pools.
To analyze tiering, you must set the tier level of the source pools and the target
pools. The source pools are the pools that you select for analysis. The target pools
are the pools that are used to relocate volumes to lower or higher tiers of storage.
Tip: You can also set or modify the tier level of pools on the General tab of the
View Properties page for the storage pool.
Child pools have the same tier level as the parent pool. So if you change the tier
level of the parent pool or of the child pool, all of the pools in the parent-child
relationship are set to the same tier level.
You can assign tier levels to storage systems that are not storage virtualizers.
However, you cannot balance the pools or analyze the tiering of pools other than
storage virtualizer pools.
1. From the Storage menu, click Pools.
2. On the Pools page, select one or more storage pools.
3. Click Set > Tier, and then select a tier level. To remove the tier level, click
None.
The tier level that you selected for the storage pools is shown in the Tier column.
The servers that you select must be connected to one or more storage virtualizers.
1. From the Servers menu, click Servers.
2. Right-click one or more servers, and then click Analyze Tiering. Alternatively,
you can click Actions > Analyze Tiering.
The hypervisors that you select must be connected to one or more storage
virtualizers.
1. From the Servers menu, click Hypervisors.
2. Right-click one or more hypervisors, and then click Analyze Tiering.
Alternatively, you can click Actions > Analyze Tiering.
When you complete entering the information to analyze the tiering of the volumes,
recommendations for tiering are shown on the Tiering Analysis page. You can
create a schedule to run the analysis that is based on the analysis criteria that you
entered.
You must run the tiering analysis to create a tiering analysis task.
The criteria that you modify are used to analyze the source volumes and target
volumes that were selected when you created the tiering analysis.
1. From the Home menu, click Tasks.
2. Right-click a tiering analysis task, and click Edit.
3. Modify the tiering thresholds, and then click Analyze.
The source volumes are analyzed to determine whether one or more of the
volumes require re-tiering based on the criteria that you specified. If one or more
of the volumes require re-tiering, recommendations are generated to move the
volumes to the destination pools that meet the criteria that you specified.
You can balance the workload of volumes in pools on the same tier on the
following storage virtualizers:
v SAN Volume Controller
v Storwize V7000
v Storwize V7000 Unified block storage
v FlashSystem V9000 and FlashSystem V840
Learn more: For information about the components that can be used with IBM
Spectrum Control Version 5.2 (or later), see IBM Spectrum Control
interoperability matrix at http://www.ibm.com/support/
docview.wss?uid=swg21386446.
To balance pools, you must select two or more pools on the same tier level and on
the same storage virtualizer. For example, you select three tier 1 pools, and four
tier 3 pools. The pools on tier 1 are analyzed and balanced, and the pools on tier 3
are analyzed and balanced.
Balancing pools
You balance pools to distribute the workload of volumes across pools on the same
tier and on the same storage virtualizer. To improve the performance of the pools,
recommendations are generated to move volumes to other pools on the same tier
and on the same storage virtualizer.
1. From the Storage menu, click Pools.
2. Right-click two or more pools on the same tier level and on the same storage
virtualizer, and then click Balance Pools.
Tip: If you want to analyze pools that contain volumes in mirrored volume
relationships, select one or more pools that do not contain either the primary
volume or the secondary volume. The primary volume and the secondary
volume cannot be placed in the same destination pool.
3. Choose whether to analyze volumes in mirrored volume relationships. These
options are only available if you select one or more volumes with mirrored
volumes.
4. Specify the number of days that are used to analyze the pools. By default, the
value for the activity level of pools is estimated based on the performance data
that was collected on the previous seven days.
5. Specify the placement of optimized volumes in capacity pools. These options
are only available if you select one or more volumes in capacity pools.
6. Specify whether volumes that are in the same source storage pool and that are
assigned to the same server or hypervisor must be placed in the same
destination storage pool.
7. Click Analyze.
When you finish entering the information for balancing the pools, a task is created
that shows the recommendations on the Balance Analysis page. You can implement
the recommended changes, or you can create a schedule to implement the changes
later.
To create a balance analysis task, you must run the analysis for balancing the
pools.
Based on the criteria that you specified, the pools are analyzed to determine
whether the pools require balancing. If one or more pools require balancing,
recommendations are generated to redistribute the volumes to pools on the same
tier of storage.
To determine the relative activity of pools on the same tier and on the same
back-end storage system, the following values are calculated:
v The current activity level of the pool is calculated.
v The activity deviation percentage of the pool is calculated.
Tip: On the Pools page, the activity level of the pool is shown in the Activity
column. The difference between the activity level of the pool and all of the other
pools on the same tier and storage system is shown in the Activity Deviation
(%) column.
The following formulas are used to calculate the activity level and the activity
deviation percentage for pools.
Table 45. Formulas for calculating the activity level and activity deviation percentage values
for pools
Value calculated Formula that is used in the calculation
Activity level of the pool [Read I/O Rate × (1− Read I/O Cache Hit
%) + Write I/O Rate] ÷ Total Pool Capacity
Activity level of the pool on XIV systems (Total I/O Rate ÷ Total Capacity)
Activity deviation percentage of the pool [(Pool Activity Level − Average Activity
Level) ÷ Average Activity Level] × 100
If the activity deviation percentage of the pool lies within the range of <−10% to
>10%, the pool is considered to be balanced. If the activity deviation percentage of
the pool exceeds the deviation threshold of 10%, the pool is a candidate for
balancing.
For example, you want to identify the tier-1 pools that require balancing on a
storage environment that consists of a Storwize V7000 Unified storage virtualizer
with one DS8000 storage system. You open the Pools page and view the activity
deviation percentage values for the tier-1 pools.
The pool_3 pool is a candidate for balancing because the activity deviation value
for the pool is 14% higher than the deviation threshold of 10%.
Reclaiming storage
You can view the amount of storage that can be reclaimed in your data center and
for each of the block storage systems that are monitored. Based on volume
reclamation recommendations, you can reclaim the unused space and more
effectively allocate volume space on your storage systems.
Before you view recommendations for reclaiming storage, complete the following
tasks:
v Add the storage systems for monitoring and schedule a storage systems probe.
v If your storage environment is configured for storage tiers, ensure that the
amount of unused space on tier one is minimal.
By default, the period for analyzing performance data, which is used for
generating reclamation recommendations, is set to 14 days. For a more thorough
analysis, you can change this period.
View information about volumes that are analyzed and recommended for
reclamation.
1. From the Advanced Analytics menu, click Reclamation.
2. On the View by Reclaimable Capacity page, view the charts and tables for
information about reclaimable storage space, volumes that are recommended
for reclamation, and volumes that are excluded from analysis.
On the reclamation donut chart, you can view the amount of storage space that is
used and the amount of storage space that can be reclaimed. You can also see an
estimate of the storage space that can be saved when the volumes that are listed in
the table are reclaimed.
On the Recommendations tab, view the volumes that are identified as potential
candidates for reclamation.
On the Excluded tab, view the volumes that are excluded from the analysis for
reclamation recommendations.
Before you view recommendations for reclaiming storage, complete the following
tasks:
v Add the storage systems for monitoring and schedule a storage systems probe.
v If your storage environment is configured for storage tiers, ensure that the
amount of unused space on tier one is minimal.
By default, the period for analyzing performance data, which is used for
generating reclamation recommendations, is set to 14 days. For a more thorough
analysis, you can change this period.
View reclamation information about storage systems that contain volumes that are
analyzed and recommended for reclamation.
1. From the Advanced Analytics menu, click Reclamation.
2. On the View by Storage Systems page, view the charts and table for
information about reclaimable storage space and for information about the
storage systems that contain the reclaimable volumes.
On the reclamation donut chart, you can view the amount of reclaimable space and
the non-reclaimable allocated space. If you defined storage tiers, you can view the
amount of storage that can be saved for each tier. You can also see an estimate of
the storage space that can be saved when the volumes of the storage systems that
are listed in the table are reclaimed.
On the reclamation bar chart, view the amount of storage space that can be
reclaimed on each storage system in your data center.
In the table, view space, capacity, and reclamation information about each storage
system.
On the View by Reclaimable Capacity page, you can select a volume or multiple
volumes for exclusion from the analysis for reclamation recommendations.
1. From the Advanced Analytics menu, click Reclamation.
The volume is removed from the Recommendations table and added to the
Excluded table, and the charts are refreshed.
Tip: To include a volume in the analysis, on the Excluded table, right-click the
volume and select Include in Analysis. The volume is removed from the Excluded
table and added to the Recommendations table, and the charts are refreshed.
Before you transform storage, you must probe the storage virtualizers. The probe
collects information about the logical devices, such as volumes and virtual disks,
that are associated with the storage virtualizer.
You can convert or move volumes in pools on the following storage virtualizers:
v SAN Volume Controller
v Storwize V7000
v Storwize V7000 Unified
v FlashSystem V9000 and FlashSystem V840
For volumes in mirrored volume relationships, you can convert the primary
volume, the secondary volume, or both volumes.
Migrating volumes with service classes: A warning is generated when you move
one or more volumes that are assigned a service class to a destination pool that
does not meet the requirements of the service class.
1. In the menu bar in the web-based GUI, go to Storage > Volumes.
2. Click one or more storage volumes, and then select Transform Storage from the
context-sensitive menu. Alternatively, you can click Actions > Transform
Storage.
When you complete entering criteria for transforming storage, the Transform Plan
page is opened. A task is created which you can run to implement the
recommendations.
Related tasks:
By default, the period for analyzing performance data is set to 14 days. When you
change the number of days, the period for analyzing performance data is modified
for the advanced analytics about storage, that is, tiering, balancing, transforming,
and reclamation.
When you transform storage, the performance data that is collected about the
pools on storage virtualizers is analyzed. The period that is set for analyzing
performance data is used to calculate the average workload activity of the volumes
that are selected for analysis. To provide a more accurate analysis of the workload
activity of the volumes in your storage environment, you can extend or shorten the
period.
For reclamation, the performance data that is collected for the analysis period
about all block storage pools is analyzed, regardless of whether the storage is
virtualized.
The default value is changed to the number of days that you specified, for example
28.
Tip: To verify that the analysis period is changed, you enter the following
command:
tpctool getdscfg -url localhost:9550 -user ***** -pwd ***** -context tiering
Tip: To view the description of a property that you can modify for a resource,
hover the mouse pointer over the hover icon for that property in the
web-based GUI.
The action for opening a management GUI is available for storage systems and
switches under the following conditions:
v The resource is monitored by IBM Spectrum Control.
v The resource has a management GUI that is web-based
1. In the menu bar in the web-based GUI, go to a type of top-level resource. For
example, if you want open the GUI for a block storage system, go to Storage >
Block Storage Systems. If you want open the GUI for a switch, go to Network
> Switches.
2. Right-click the resource and select the action to open the GUI. For storage
systems, select Open Storage System GUI. For a switch, select Open Switch
GUI. The start page for the management GUI is opened in a separate web
browser window.
The information that you export to a file is organized according to the sorting,
filtering, and column order that is defined for a list. Before you export information,
complete the following tasks to configure a list:
v Change the order of columns in the list as you want them to appear in the
generated file.
v Hide columns in the list that you do not want to include in the generated file.
Information in hidden columns is not exported.
v Sort the rows in the list as you want them to appear in the generated file. Each
list in the web-based GUI has a column or set of columns that determine the
order of its rows.
v Filter the list to show only the resources, jobs, or alerts that you want to export.
Use filtering to limit the rows that are shown in a list based on value in a
specific column or set of default columns.
Tip: When you export a table of data that contains many columns, the
rows in that table might span multiple pages in the resulting PDF. For
example, if a table contains 20 columns, then the row for a specific
resource might be shown on more than one page (10 columns on the
first page and 10 columns on the second page).
To reduce the number of pages that a table spans, before you select the
export action, hide the columns that you do not want to include in the
PDF. Continue hiding columns until the table no longer spans multiple
pages.
HTML
You can view an HTML file with a web browser. The information that
you export to an HTML file is formatted into a table.
3. Optional: Depending on how your web browser is configured, you can specify
the name and location of the generated file.
4. Click the save option to export the information to a file.
Related concepts:
“Viewing information about resources” on page 130
You can view detailed information about the resources that are monitored by IBM
Spectrum Control. Resources include storage systems, volumes, pools, servers,
hypervisors, fabrics, and switches. You can also view information about internal
and related resources.
“Customizing lists of resources, tasks, and alerts”
The web-based GUI uses lists to show information about resources, tasks, and
alerts. The information in each list is organized into columns and rows. You can
customize these lists by filtering information, sorting rows, and showing, hiding,
and reordering columns.
Filtering lists
You can filter the items that are shown in a list. Use filtering when you want to
limit the rows that are shown in a list based on values in a specific column or set
of columns. For example, when viewing alerts, you can filter the list so that only
alerts with a value of Warning in the Severity column are shown.
1. In the web-based GUI, go to a list of resources, jobs, or alerts that you want to
filter.
2. Click the Filter icon to determine how to filter the list. The following
options are available:
Filter by Default Columns
Select this option to apply the filter to the set of the default columns in
a list. Each list contains a set of default columns on which you can
filter.
For example, in the lists of alerts on the Home > Alerts page, select this
option to apply filter text to the following columns at the same time:
Condition, Severity, Alert Category, Resource, Internal Resource,
Total Occurrences, Alert Name.
Filter by a Specific Column
Select this option to apply filter text to a specific column in a list. For
example, on the Home > Alerts page, select the Condition column if
you want to apply filter text to values in that column only.
Restriction: Some columns in lists cannot be used for filtering and are not
shown under the Filter by a Specific Column option.
3. In Filter text box , type the text for filtering a list. You can
type letters, whole words, partial words, and numbers. When filtering on
certain columns, you can select from a list of values rather than typing in filter
text.
For example, when filtering on the Status column, you can select one of the
following values as the filter text: Error, Unreachable, Warning, Normal,
Unknown.
4. Press Enter to apply the filter to the list. Only rows with values that match or
partially match the filter text are shown.
For example, on the Home > Alerts page, if you select to filter on the Severity
column and type critical as the filter text, only alerts that have a severity of
critical and critical - acknowledged are shown in the list.
Tip: The name of a column to which a filter applies is shown next to the Filter
icon .
5. Optional: To remove the filtering for a list, click Reset.
Sorting lists
Each list of resources in the web-based GUI has a column or set of columns that
determines the order of its rows. You can sort the columns in a list to organize the
rows according to your requirements.
234 IBM Spectrum Control: User's Guide
For example, the list of ports on a fabric is ordered by switch name, blade slot, and
port number, in that order. You can change the sort order of these columns to
organize a list of resources according to your requirements.
Tip: A visual indicator is shown next to the primary column that determines
the sort order of a list.
1. In the web-based GUI, go to a list of resources, jobs, or alerts that you want to
sort.
2. Complete the following tasks to sort the rows in the list:
v To change whether the rows in a list are sorted by ascending or descending
order, click the name of the primary column in the heading row. Click the
name of the column again to reverse the sort order.
v To change the column that determines the sort order of resources, click the
name of that column. For example, click the Name column to sort the list of
resources alphabetically, or click the Status column to sort the list according
to the status of resources.
Tip: When you click a column other than the primary sort column, that
column becomes the new primary sort column. However, the previous
primary column maintains its sort order (ascending or descending).
Tip: The changes that you make to column settings are saved from session to
session.
3. Optional: To reset the order and display of columns to the default setting,
right-click any of the column headings and select Restore Default View.
Tasks are created when you take any of the following actions in the web-based
GUI:
v Assign storage to servers or hypervisors by using the Provision Storage wizard.
v Move volumes to higher or lower tiers by using the Analyze Tiering wizard.
v Move or convert volumes by using the Transform Storage wizard.
v Distribute the workload of volumes across pools on the same tier by using the
Balance Pools wizard.
Viewing tasks
Use the Tasks page in the web-based GUI to view all the tasks that are used by
IBM Spectrum Control to provision storage and optimize resources. Use resource
list and resource details pages to view the tasks for specific resources and resource
types.
Tip: To view descriptions of the icons and columns on the Tasks page, click the
Help icon in the upper-right corner of the page.
Pending tasks are tasks that were not run and are not scheduled to run. Pending
tasks might be created by a user who is not authorized to run or schedule the task.
For example, users who are assigned to the Monitor or External Application role
can have permission to create provisioning tasks by using a service class. However,
if the service class specifies that administrator approval is required, these users can
only create the provisioning task. The provisioning task is pending until an
administrator runs or schedules it.
Tip: The status icon on the Tasks tab represents the most critical status of the
tasks that are associated with the monitored resources. For example, if one of
the tasks for storage systems failed, the following icon is shown on the tab:
Tasks
3. Optional: View the status icons on the Tasks page for a summary of task
statuses. This summary includes the number of tasks that have a Failed,
Warning, Successful, or Running status.
Tip: To view descriptions of the icons and columns on the Tasks page, click the
Help icon .
Tasks (3)
3. Click Tasks in the General section to view the tasks for the resource. The
information about tasks is organized into columns. These columns include
information about the status of tasks, the most recent date and time when tasks
ran, and the schedule for tasks.
4. Optional: View the status icons on the Tasks pane to view a summary of task
statuses. This summary includes the number of tasks that have a Failed,
Warning, Successful, or Running status.
Tip: To view descriptions of the icons and columns on the Tasks pane, click the
Help icon .
On all the task detail pages, you can view information such as the task status, the
duration and completion date of task runs, and the actions that you can take to
manage the task. For tasks such as tiering analysis, balance analysis, and transform
plan, you can view information about the recommendations that are generated by
the most recent or earlier task runs. For provisioning tasks, you can view the status
of the actions that the provisioning task completes for each of the resources that
are configured in the task.
1. From the menu bar, go to the Tasks page, a resource list page for a resource
type, or a resource detail page for a specific resource. For example, to view the
tasks that are related to storage systems, go to Storage and select the type of
storage system you want to monitor, and click the Tasks tab.
2. Locate the task that you want to view in more detail.
3. Right-click the task row and select View Details. The task details page opens in
a separate window. For example, the Tiering Analysis page opens if you select
a tiering-analysis task row.
4. Optional: To view task logs, click Open Logs. You can use the information in
the log file to troubleshoot any errors that might occur when a task is run.
5. Optional: For provisioning tasks, you can export information about the
provisioning task to a text file for offline viewing. To export information, click
the icon at the top of the Provisioning page.
The following examples show the type of information that you can view in the
task logs:
v View the number of recommendations that are generated by tiering-analysis,
balance-analysis, or transform-plan task runs.
v View the options that you select when you use wizards, such as the Transform
Storage, Analyze Tiering, or Balance Pools wizards. For example, when you use
the Analyze Tiering wizard, a tiering-analysis task is generated and the options
that you choose in the wizard are recorded in the task log.
v View error messages that are related to task processing.
1. From the menu bar, go to the Tasks page, a resource list page for a resource
type, or a resource detail page for a specific resource. For example, to view the
tasks that are related to storage systems, go to Storage and select the type of
storage system you want to monitor, and click the Tasks tab.
2. Locate the task that has a log file that you want to view.
3. Right-click the task row and select Open Logs. The Logs page shows log
entries for the most recent task run.
4. Optional: On the Logs page, to view the log for a previous task run, select a
task run from the Select a log list.
5. Optional: To view only the actions in a task run that have a Warning or Error
status, select an option from the Show all list. You can choose to view only
actions that have the following statuses:
The information on the Logs page is automatically updated every 30 seconds. New
entries are added to the end of a log. You can view the following information on
the Logs page:
v The overall status of a task. The icon that is shown in the Select a log list
represents the most critical status that was generated by an action in the task
run.
v The status for each action in a task.
v The date and time when an action was completed. The date, time, and time zone
of the action is shown in the Date and Time column.
v The ID of the message that is associated with an action. You can click the value
in the ID column to view more information about a message.
v The description of an action.
Tip: You can use the navigation and search functions of the web browser to locate
information on the page.
After you update the value for job logs, the list of task runs in the web-based GUI
is automatically updated within a few minutes.
To run provisioning tasks, you must be the owner of the task or have
Administrator privileges.
Provisioning tasks can run only once. You can run the task when you complete the
steps of the Provision Storage wizard or you can save the provisioning task and
run the task later.
The Run Now and Schedule actions are available for a provisioning task when the
task is not running, and was not previously run.
1. From the menu bar, go to the Tasks page, a resource list page for a resource
type, or a resource detail page for a specific resource. For example, to view the
provisioning tasks that are related to servers, go to Servers > Servers, and click
the Tasks tab.
2. Locate the provisioning task that you want to run.
3. Depending on when you want the provisioning task to run, choose one of the
following options:
v To run the provisioning task immediately, right-click the task row and select
Run Now. The task status changes to Running and the provisioning task
runs immediately.
v To schedule the provisioning task to run at a specific date and time, complete
the following steps:
a. Right-click the task row and select Schedule.
b. From the Schedule page, select a future date and time from the Provision
lists, and click Save.
You can also run or schedule the provisioning task from the Provisioning detail
page. On the Provisioning detail page, click Execute to run the task
immediately or click Schedule to schedule the task to run at a specific date and
time.
The provisioning task runs immediately or on the scheduled date and time. To
check the progress of the task, you can take the following actions:
v View the task status on the Tasks page.
v View detailed information about the progress of the task on the Provisioning
detail page. You can view the task duration and the status of the actions that the
provisioning task completes for each of the resources that are configured in the
task.
v View the task logs from the Tasks page or from the Provisioning detail page.
You can view detailed informational, warning, and error messages that are
related to the task. You can use this information to troubleshoot any errors that
might occur when a task is run.
The provisioning task information is exported to a text file. The generated file
includes all the provisioning task details that are listed on the Provisioning page.
Columns that are hidden on the Provisioning page are included in the generated
file. The information in the file is organized according to a default order and is not
affected by the column order that is defined on the Provisioning page.
To complete any of the optimization tasks, such as balancing pools, you must
complete the following steps:
1. Create the analysis task. Use a IBM Spectrum Control wizard to create the
optimization analysis task. For example, use the Balance Pools wizard to create
a balance-analysis task.
2. Run the analysis task to generate the optimization recommendations. For
example, run the balance-analysis task to generate the recommendations to
move volumes.
3. Edit analyze tiering and balancing pool tasks. You can modify the thresholds
that were set in the Analyze Tiering and Balance Pools wizards.
4. Implement the recommendations to optimize storage. For example, implement
the recommendations to balance pools by running the analysis-execution task.
Use the Tasks, resource list, and resource detail pages in the web-based GUI to
take the following actions for optimization tasks:
v Run the optimization analysis immediately to generate optimization
recommendations.
v Schedule the optimization analysis to run at a specified date and time.
v Implement optimization recommendations immediately.
Storage optimization tasks are created when you take any of the following actions
in the web-based GUI:
Tier storage
Move volumes to higher or lower tiers by using the Analyze Tiering
wizard. A tiering-analysis task is created.
Balance pools
Distribute the workload of volumes across pools on the same tier by using
the Balance Pools wizard. A balance-analysis task is created.
Transform storage
Move or convert volumes by using the Transform Storage wizard. A
transform-plan task is created.
Related tasks:
“Tiering volumes by I/O density and I/O rate” on page 221
Set thresholds for tiering volumes by I/O rate or I/O density.
“Balancing pools” on page 223
You balance pools to distribute the workload of volumes across pools on the same
tier and on the same storage virtualizer. To improve the performance of the pools,
recommendations are generated to move volumes to other pools on the same tier
and on the same storage virtualizer.
“Transforming and migrating volumes” on page 227
You can transform fully allocated volumes to compressed or thin-provisioned
volumes, or transform compressed or thin-provisioned volumes to fully allocated
volumes. You can move volumes to other pools or to pools that are enabled for
Easy Tier.
You can run tasks immediately or schedule tasks to run at a future date and time.
Tip: The Run Now action is available when the task is enabled and the task is not
running.
1. From the menu bar, go to the Tasks page, a resource list page for a resource
type, or a resource detail page for a specific resource. For example, to view the
tiering-analysis tasks that are related to servers, go to Servers > Servers, and
click the Tasks tab.
2. Locate the tiering analysis, balance analysis, or transform-plan task that you
want to run.
3. Right-click the task row and select Run Now. The task status changes to
Running.
4. Optional: To schedule future task runs for tiering analysis or balance-analysis
tasks, right-click the task row and select Schedule Analysis. On the Schedule
Analysis page, select the time that the task is run and how often the task is
run.
Restriction: You cannot schedule future task runs for transform-plan tasks.
5. Optional: To enable or disable a tiering analysis or balance-analysis task, select
Enabled or Disabled on the Schedule Analysis page. When the task is enabled,
the task runs according to the defined schedule. If the task is disabled, you can
modify the task schedule but the task cannot run at the scheduled time.
When the task run completes, you can view the recommendations that are
generated on the task detail page. For example, you can view the
recommendations that are generated for a tiering-analysis task on the Tiering
Analysis page. To check the progress of the task run, you can take the following
actions:
v View the task status on the Tasks page.
v View information about the progress of the task on the task detail page. You can
view the duration of the task run, and the date and time that the task run
completed.
v View the task logs from the Tasks page or from the task detail page. You can
view detailed informational, warning, and error messages that are related to the
task. You can use this information to troubleshoot any errors that might occur
when a task is run.
Related tasks:
“Modifying the criteria for analyzing tiering” on page 222
When a task is created after you run the tiering analysis, you can modify the
criteria for tiering the volumes.
You can view analysis-execution tasks on the Tasks page. The Related Task column
shows the related tiering analysis, balance analysis, or transform-plan task.
The analysis-execution task runs immediately. To check the progress of the task,
you can take the following actions:
v View the task status on the Tasks page.
v View the status of individual task recommendations on the Analysis Execution
page.
v View the task logs from the Tasks page or from the Analysis Execution page.
You can view detailed informational, warning, and error messages that are
related to the task. You can use this information to troubleshoot any errors that
might occur when a task is run.
When you define the schedule, an analysis-execution task is created for the
implementation of the optimization recommendations.
An analysis-execution task is created that you can monitor on the Tasks page. The
name of the analysis-execution task is based on the name of the related tiering
analysis, balance analysis, or transform-plan task. The Related Task column shows
the related tiering analysis, balance analysis, or transform-plan task.
When the analysis-execution task runs on the scheduled date, the optimization
recommendations are implemented. For example, volumes are moved to higher or
lower tiers when storage-tiering recommendations are implemented.
Renaming tasks
You can change the name of a task by using the task detail page. For example, use
the Provisioning page to change the name of a provisioning task. A task name is
automatically generated when the task is created. If the original name is
ambiguous or is not clear enough, you can change the task name to a unique task
name that you provide.
You must have the following privileges to rename the different task types:
Provisioning
To rename provisioning tasks, you must be the owner of the task or have
Administrator privileges.
Other task types
To rename all other tasks, such as tiering analysis, balance analysis,
transform plan, and analysis-execution tasks, you must have Administrator
privileges.
The task is renamed. You can view the renamed task on the Tasks page.
Deleting tasks
Use the Tasks page to delete tasks, such as provisioning, tiering analysis, balance
analysis, transform plan, and analysis-execution tasks.
You must have the following privileges to delete the different task types:
Provisioning
To delete provisioning tasks, you must be the owner of the task or have
Administrator privileges.
Other task types
To delete all other tasks, such as tiering analysis, balance analysis,
transform plan, and analysis-execution tasks, you must have Administrator
privileges.
Alerts
Determining when and how you are alerted to configuration and performance
conditions within your storage environment is important to helping you maintain
and administer storage resources. Many conditions can trigger alerts. You can set
up IBM Spectrum Control so that it examines the attributes, capacity, and
performance of a resource and notifies you when changes or violations are
detected.
Conditions that generate alerts are detected during data collection and event
processing. For some storage systems such as IBM Spectrum Accelerate and the
XIV, events are polled every minute from the resource
For other resources, events are subscription-based, where the resource itself or a
data source such as a CIM agent sends the events to IBM Spectrum Control when
conditions change on the resource. Examples of storage systems that use
subscription-based event processing include SAN Volume Controller, Storwize
V7000, Storwize V7000 Unified, FlashSystem V840, and FlashSystem V9000. For
these storage systems, a probe is automatically run when many events are received
from the storage system in a short time period. To avoid performance bottlenecks,
probes are run only every 20 minutes.
The conditions that trigger alert notifications depend on the type of resource that
you are monitoring. In general, the following types of conditions can trigger alerts:
v An attribute or configuration of a resource changed
v The capacity of a resource fell outside a specified range
v The performance of a resource fell outside a specified range
v The storage infrastructure was changed, such as a new or removed resource
v Data is not being collected for a resource
For example, you can use performance thresholds to be notified when the total I/O
rate for storage systems falls outside a specified range. This information can help
you identify areas in your storage infrastructure that are over used or under used.
IBM Spectrum Control provides many metrics for measuring performance and
determining violations of the thresholds that you specify.
Alerts can notify you of general changes and performance issues on the following
resources:
v “Storage Systems (performance)” on page 254
v “Storage Systems (general changes)” on page 254
v “Internal resources (common conditions)” on page 257
v “Clusters” on page 258
v “Disks” on page 258
v “Filesets” on page 258
v “File Systems” on page 259
v “File System Pools” on page 259
v “Host Connections” on page 259
v “I/O Groups” on page 259
v “Managed Disks” on page 259
v “Modules” on page 260
v “Network Shared Disks” on page 260
v “Nodes” on page 260
v “Pools” on page 261
v “Ports” on page 263
v “Quotas” on page 263
v “RAID Arrays” on page 264
v “Shares” on page 264
v “Volumes” on page 264
Important: Not all the attributes upon which you can alert are listed here. A
number of other attributes are available for alerts and are based on the key
properties of a storage system. To view a complete list of attributes upon which you
can alert, go to the Block Storage Systems page, File Storage Systems page, or Object
Storage Systems page, right-click the storage system, and select Edit Alert
Definitions.
Attributes that are automatically configured for alerts are marked with an asterisk
(*).
Tips:
v The type of storage system determines which attributes and performance
conditions are available for alerts. For example, triggering conditions for shares
are available only for storage systems that are configured for file storage, such as
Storwize V7000 Unified.
v For capacity attributes, you can generate alerts when the amount of storage is
greater than, less than, or equal to a specified value. You can also determine the
unit of measurement for the attribute, such as KiB, MiB, GiB, or TiB.
Define alerts that notify you when the performance of a storage system falls
outside a specified threshold. In alerts, you can specify conditions based on metrics
that measure the performance of volumes, disks, ports, ports, and nodes. By
creating alerts with performance conditions, you can be informed about potential
bottlenecks in your storage infrastructure.
For example:
v You can define an alert to be notified when the average number of I/O
operations per second for read and write operations on a storage system's
volumes is greater than or equal to a specified threshold. Use this alert to be
notified when the workload of a volume is high and you might need to balance
that load across other volumes to improve overall performance.
v You can define an alert to be notified when the percentage of the average
response time that can be attributed to delays from host systems is greater than
or equal to a specified threshold. Use this alert to be notified of slow hosts and
fabrics that might not be working efficiently.
You can also define an alert that notifies you when a metric is less than a specified
threshold, such as if you want to identify volumes that might be under used.
The type of storage system determines the metrics that can be alerted upon. For a
list of the metrics that are available for each type of storage system, see
“Performance metrics” on page 283.
To view information about the code bundles for the firmware versions of the
DS-series, go to the IBM support site at http://www.ibm.com/support/entry/
portal/Overview and search for code bundle information. An internet connection
is required to access the support site.
Last Successful Probe A specified amount of time has passed since a probe or performance monitor was
able to collect data about a storage system. You can use this alert to be notified
Last Successful Monitor when up-to-date configuration, status, or performance data is not being collected
about a storage system and its existing data might be stale. This situation might
occur if the resource, network, or IBM Spectrum Control server is unavailable.
Performance Monitor Status* One of the following statuses is detected for a performance monitor:
Not Normal
An error or warning occurred during data collection. This status
indicates that a performance monitor did not collect any data, or only
collected a partial set of data about a resource.
Warning
A performance monitor completed, but did not collect a complete set of
performance data. This status might occur if the resource was rebooted
during data collection, no valid performance data was provided by the
resource, or a communication error occurred with the resource or its
associated agent.
Error A performance did not complete when it attempted to collect
performance data about the resource. This status might occur if the
resource cannot be reached during data collection, or if no configuration
data is available for the resource.
For details about why a specific status occurred, check the log for the
performance monitor. To check the log, go to the details page for a resource, click
Data Collection, and select Actions > Open Logs in the Performance Monitor
section on the Data Collection page.
Probe Status* One of the following statuses is detected for a probe:
Not Successful
An error or warning occurred during data collection. This status
indicates that a probe did not collect any data, or only collected a partial
set of data about a resource.
Warning
A probe completed, but might not have collected a complete set of data.
This status might occur if data cannot be collected about one or more of
the internal resources of a resource.
Error (default)
A probe did not complete when it attempted to collect asset data about
the resource. This status might occur if the resource cannot be reached
during data collection.
For details about why a specific status occurred, check the log for the probe. To
check the log, go to the details page for a resource, click Data Collection, and
select Actions > Open Logs in the Probe section on the Data Collection page.
Status One of the following statuses is detected for a storage system:
Not Normal
An error or warning status was detected for a storage system.
Warning
A warning status was detected for a storage system. This status might
occur if a storage system comes online or if its version changes.
Error An error status was detected for a storage system. This status might
occur if the cooling fans in a storage system are stopped and the internal
temperature is too high or if a storage system goes offline.
Assigned Volume Space The total volume space in the storage system that is mapped or assigned to host
systems, including child pool capacity.
Available Pool Space The total amount of the space in the pools that is not allocated to the volumes in
the pools. To calculate available space, the following formula is used:
(pool capacity - allocated space)
For XIV systems, pool capacity is the physical capacity of the pools and does not
include the virtual capacity of the pools. For other storage systems, pool capacity
might also include the overhead space for the pools that are not formatted.
Free Capacity The amount of space in the pools on the storage system that is available for
creating volumes.
Physical Allocation The percentage of physical space in pools that is allocated to volumes, including
child pools. The value is always less than or equal to 100% because you cannot
allocate more physical space to the volumes than is available in the pools. This
value is determined by the formula, Allocated Space ÷ Capacity × 100. For example,
if the space that is reserved for volumes is 50 GiB for a volume size of 200 GiB,
physical allocation is 25%.
Pool Shortfall The difference between the amount of virtual space that is committed to the
volumes in the pools and the actual physical space that is available in the pools,
which is expressed as a percentage. As the virtual space is allocated to the
thin-provisioned and compressed volumes, the shortfall increases and becomes
more critical.
A pool shortfall occurs when you commit more space to the volumes in the pools
than is physically available to the pools. If the physical space available to the
pools is less than the committed virtual space, then the pools do not have
enough space to fulfill the commitment to the virtual space.
For example, the physical capacity of the pools is 70 GiB, but 150 GiB of virtual
space was committed to the thin-provisioned volumes. If the volumes are using
50 GiB, then there is still 100 GiB committed to those volumes (150 GiB − 50 GiB)
with only 20 GiB of available pool space (70 GiB − 50 GiB). Because only 20 GiB
of the pool space is available, 80 GiB of the committed space cannot be allocated
(100 GiB - 20 GiB). In this case, the percentage of committed space that is
unavailable is 80% [(80 GiB ÷ 100 GiB × 100].
Pool Space The amount of space in pools that are on the storage system.
Raw Disk Capacity The total unformatted disk capacity of a storage system. When this value is
calculated, IBM Spectrum Control does not include the capacity of storage system
disks that become missing after data collection.
Remaining Unallocated Volume The amount of the total volume capacity in the storage pool that is not allocated.
Space
Reserved Pool Space The amount of unallocated space in the pool that is reserved for provisioning and
optimization tasks.
Shortfall The difference between the amount of virtual space that is committed to the
volumes in the pools and the actual physical space that is available in the pools.
As the virtual space is allocated to the thin-provisioned and compressed volumes,
the shortfall increases and becomes more critical.
For example, the physical capacity of the pools is 70 GiB, but 150 GiB of virtual
space was committed to the thin-provisioned volumes. If the volumes are using
50 GiB, then there is still 100 GiB committed to those volumes (150 GiB − 50 GiB)
with only 20 GiB of available pool space (70 GiB − 50 GiB). Because only 20 GiB
of the pool space is available, 80 GiB of the committed space cannot be allocated
(100 GiB - 20 GiB).
Snapshot Space The amount of space that is used by all of the snapshots of the file systems that
are associated with the GPFS cluster.
Total File System Capacity The total amount of storage space on all of the file systems on the storage system
or filer.
Unassigned Volume Space The total volume space in the storage system that is not mapped or assigned to
host systems.
Used Capacity The amount of space in the pools on the storage system that is used by volumes.
Used Pool Space The amount of space in the pool that is allocated to and used by volumes.
Used Volume Space The amount of space in the storage system that is allocated to and used by
volumes.
Volume Capacity The total storage space on all the volumes in pools. For thin-provisioned and
compressed volumes, this value includes virtual space. For volumes with parent
pools, this value includes child pool capacity.
There are a number of alert conditions that are common to many of the internal
resources in a storage system. These common conditions represent key changes in
your storage infrastructure. For example, you can specify conditions that generate
alerts when specific internal resources are added to or deleted from a storage
system, or when current data isn't being collected about resources.
Table 49. Triggering attributes and conditions that are common to internal resources
General Attributes Triggering Conditions for Attributes
New resource A resource is detected for the first time. Use this alert to be notified when new
physical and logical resources are added to a storage system.
Physical resources include disks, RAID arrays, I/O groups, ports, nodes, host
connections, clusters, and file systems. Logical resources include volumes, pools,
filesets, and shares.
Clusters
Table 50. Triggering attributes and conditions for general changes on clusters
General Attributes Triggering Conditions for Attributes
New Cluster A cluster is detected for the first time.
Removed NAS Cluster A previously monitored NAS cluster can no longer be found. Historical data
about the cluster is retained, but no current data is being collected. Use this alert
to be notified if a cluster is removed or becomes unavailable.
Disks
Table 51. Triggering attributes and conditions for general changes on storage system disks
General Attributes Triggering Conditions for Attributes
New Disk A disk is detected for the first time.
Removed Disk A previously monitored disk can no longer be found. Historical data about the
disk is retained, but no current data is being collected. Use this alert to be
notified if a disk is removed or becomes unavailable.
Table 52. Triggering attributes and conditions for capacity changes on disks.
Capacity Attributes Triggering Conditions for Attributes
Available Disk Space The amount of storage space that is available (not allocated) on the disk.
Disk Capacity The total amount of storage space that is on the disk.
Filesets
Table 53. Triggering attributes and conditions for general changes on filesets
General Attributes Triggering Conditions for Attributes
Deleted NAS Fileset A previously monitored NAS fileset can no longer be found. Historical data
about the fileset is retained, but no current data is being collected. Use this alert
to be notified if a fileset is deleted or becomes unavailable.
New Fileset A fileset is detected for the first time.
State A fileset is linked to a file system, unlinked from a file system, or deleting.
Host Connections
Table 56. Triggering attributes and conditions for general changes on host connections
General Attributes Triggering Conditions for Attributes
New Host Connection A host connection is detected for the first time.
Removed Host Connection A previously monitored host connection can no longer be found. Historical data
about the host connection is retained, but no current data is being collected. Use
this alert to be notified if a host connection is removed or becomes unavailable.
I/O Groups
Table 57. Triggering attributes and conditions for general changes on I/O groups
General Attributes Triggering Conditions for Attributes
New I/O Group A new I/O group was detected for the first time.
Removed I/O Group A previously monitored I/O group can no longer be found. Historical data about
the I/O group is retained, but no current data is being collected. Use this alert to
be notified if an I/O group is removed or becomes unavailable.
Managed Disks
Table 58. Triggering attributes and conditions for general changes on managed disks
General Attributes Triggering Conditions for Attributes
Managed Disk Status One of the following statuses is detected for a managed disk:
Not Normal
An error or warning status was detected on a managed disk.
Warning
A warning status was detected on a managed disk.
Error An error status was detected on a managed disk.
New Managed Disk A new managed disk was detected for the first time.
Table 59. Triggering attributes and conditions for capacity changes on managed disks.
Capacity Attributes Triggering Conditions for Attributes
Available Space The amount of unused storage space on the managed disk.
Total Space The total amount of storage space that is on the managed disk on the storage
system. This attribute is only available for Storwize V7000 storage systems that
are configured as back-end storage.
Modules
Table 60. Triggering attributes and conditions for general changes on modules
General Attributes Triggering Conditions for Attributes
Deleted Module A previously monitored module can no longer be found. Use this alert to be
notified if a module is removed or becomes unavailable.
Nodes
Table 62. Triggering attributes and conditions for general changes on nodes
General Attributes Triggering Conditions for Attributes
New Node A new node was detected for the first time.
Removed Node (Block storage) A previously monitored node can no longer be found. Historical data about the
node is retained, but no current data is being collected. Use this alert to be
notified if a node is removed or becomes unavailable.
Removed NAS Node (File A previously monitored NAS node can no longer be found. Historical data about
storage) the node is retained, but no current data is being collected. Use this alert to be
notified if a node is removed or becomes unavailable.
Table 64. Triggering attributes and conditions for capacity changes on pools.
Capacity Attributes Triggering Conditions for Attributes
Allocated Space The amount of space that is reserved for all the volumes in a pool.
Assigned Volume Space The amount of space on all the volumes in a pool that are mapped or assigned to
host systems.
Available Repository Space The amount of available, unallocated storage space on all extents in the
repository of a pool for Track Space-Efficient (TSE) thin-provisioning. This
attribute applies only to the DS8000 storage systems.
Available Virtual Capacity The amount of virtual capacity in a thin-provisioned pool that is not used by
volumes.
Physical Allocation The percentage of physical space in a pool that is reserved for volumes. This
value is determined by the formula, Allocated Space ÷ Capacity × 100. For example,
if the space that is reserved for volumes is 50 GiB for a volume size of 200 GiB,
physical allocation is 25%.
Pool Shortfall The difference between the amount of virtual space that is committed to the
volumes in the pools and the actual physical space that is available in the pools,
which is expressed as a percentage. As the virtual space is allocated to the
thin-provisioned and compressed volumes, the shortfall increases and becomes
more critical.
A pool shortfall occurs when you commit more space to the volumes in the pools
than is physically available to the pools. If the physical space available to the
pools is less than the committed virtual space, then the pools do not have
enough space to fulfill the commitment to the virtual space.
For example, the physical capacity of the pools is 70 GiB, but 150 GiB of virtual
space was committed to the thin-provisioned volumes. If the volumes are using
50 GiB, then there is still 100 GiB committed to those volumes (150 GiB − 50 GiB)
with only 20 GiB of available pool space (70 GiB − 50 GiB). Because only 20 GiB
of the pool space is available, 80 GiB of the committed space cannot be allocated
(100 GiB - 20 GiB). In this case, the percentage of committed space that is
unavailable is 80% [(80 GiB ÷ 100 GiB × 100].
Repository Space The amount of space on all extents in the repository of a pool. This attribute
applies only to the DS8000 storage systems.
Reserved Pool Space The amount of unallocated space in a pool that is reserved for provisioning and
optimization tasks.
Shortfall The difference between the amount of virtual space that is committed to the
volumes in the pools and the actual physical space that is available in the pools.
As the virtual space is allocated to the thin-provisioned and compressed volumes,
the shortfall increases and becomes more critical.
For example, the physical capacity of the pools is 70 GiB, but 150 GiB of virtual
space was committed to the thin-provisioned volumes. If the volumes are using
50 GiB, then there is still 100 GiB committed to those volumes (150 GiB − 50 GiB)
with only 20 GiB of available pool space (70 GiB − 50 GiB). Because only 20 GiB
of the pool space is available, 80 GiB of the committed space cannot be allocated
(100 GiB - 20 GiB).
Total Reserved Capacity The total amount of space on the pool that is reserved for provisioning and
optimization tasks. Pool space is reserved when a provisioning or optimization
task is created, and allocated when the task is run.
Unused Space The amount of space that is allocated to the volumes in a pool and is not yet
used. This value is determined by the formula, Allocated Space − Used Space.
Used Repository Space The amount of used space on all extents in the repository of a pool. This attribute
applies only to the DS8000 storage systems.
Used Volume Space The amount of space on the storage system that is used by volumes.
User Reserved Capacity The amount of space in the pools on the storage system that is reserved for
user-defined purposes.
Virtual Allocation The percentage of physical space in a pool that is committed to the total virtual
capacity of the volumes in the pool.
Virtual Capacity Limit The maximum amount of virtual storage space available to allocate to volumes in
the storage pools that are associated with the storage system.
Virtual Volume Space The total amount of physical space in a pool that is committed to the total virtual
capacity of the volumes in the pool.
Ports
Table 65. Triggering attributes and conditions for general changes on ports
General Attributes Triggering Conditions for Attributes
New Port A new port was detected for the first time.
Removed Port A previously monitored port can no longer be found. Historical data about the
port is retained, but no current data is being collected. Use this alert to be
notified if a port is deleted or becomes unavailable.
Status One of the following statuses is detected for a port:
Not Normal
An error or warning condition is detected on a port.
Warning
A warning condition is detected on a port.
Error An error condition is detected on a port.
Quotas
Table 66. Triggering attributes and conditions for general changes on quotas
General Attributes Triggering Conditions for Attributes
Deleted Quota A previously monitored quota can no longer be found. Historical data about the
quota is retained, but no current data is being collected. Use this alert to be
notified if a quota is deleted or becomes unavailable.
New Quota A new quota was detected for the first time.
Table 68. Triggering attributes and conditions for capacity changes on RAID arrays.
General Attributes Triggering Conditions for Attributes
Total Space The total amount of storage space in the RAID array.
Shares
Table 69. Triggering attributes and conditions for general changes on shares
General Attributes Triggering Conditions for Attributes
New Share A new share was detected for the first time.
Deleted Share A previously monitored share can no longer be found. Historical data about the
share is retained, but no current data is being collected. Use this alert to be
notified if a share is deleted or becomes unavailable.
Volumes
Table 70. Triggering attributes and conditions for general changes on volumes
General Attributes Triggering Conditions for Attributes
Deleted Volume A previously monitored volume can no longer be found. Historical data about
the volume is retained, but no current data is being collected. Use this alert to be
notified if a volume is deleted or becomes unavailable.
New Volume A new volume was detected for the first time.
Status One of the following statuses is detected for a volume:
Not Normal
An error or warning condition is detected on a RAID array.
Warning
A warning condition is detected on a RAID array.
Error An error condition is detected on a RAID array.
| Allocated Space The total amount of storage space on a pool that is physically allocated to a
| volume.
| Real Capacity The total amount of storage space that is physically allocated to a volume. For
| thin-provisioned volumes, this value is less than the virtual capacity of the
| volume. In an XIV and IBM Spectrum Accelerate, this value represents the
| physical ("hard") capacity of the volume, not the virtual ("soft") capacity. For
| other storage systems, this value might also include overhead space if the pool is
| unformatted.
Remaining Managed Space The amount of storage space that is available on a managed disk. This value is
only available for Storwize V7000 storage systems that are configured as
back-end storage.
Unallocatable Space The amount of space by which the capacity of a volume exceeds the physical
capacity of the associated pool. In thin-provisioned environments, it is possible to
over commit (over provision) storage in a pool by creating volumes with more
virtual capacity than can be physically allocated in the pool. This value
represents the amount of volume space that cannot be allocated based on the
current capacity of the pool.
| Unallocated Space The amount of space in a pool that is not reserved for a volume. This value is
| determined by the formula: Capacity − Allocated Space.
| The value for Unallocated Space is available only for thin provisioned volumes.
Uncompressed Used Capacity The amount of storage space that is used if the compressed volume space is
uncompressed. For example, if 100 GiB of uncompressed data is compressed, and
the size of the compressed data is 20 GiB, the value is 100.
| Unused Space The amount of space that is allocated to a volume and is not yet used. This value
| is determined by the formula, Allocated Space − Used Space .
| The value for Unused Space is available only for SAN Volume Controller and
| Storwize family storage systems that are configured with block storage.
Used Space The amount of allocated space that is used by a volume. For SAN Volume
Controller and Storwize family storage systems that are configured with block
storage, you can pre-allocate thin-provisioned volume space when the volumes
are created. In these cases, the Used Space might be different from the Allocated
Space. For compressed volumes on SAN Volume Controller and Storwize family
storage systems that are configured with block storage, the Used Space reflects
the size of compressed data that is written to disk. As the data changes, the Used
Space might at times be less than the Allocated Space. For volumes that are not
thin provisioned in SAN Volume Controller, Storwize family storage systems that
are configured with block storage, and other storage systems, the values for Used
Space and Allocated Space are equal. This value is accurate as of the most recent
time that data was collected about a volume. Data collection is run on a set
schedule and the used space on a volume can change rapidly.
Alerts can notify you of general changes and capacity changes on the following
resources:
v “Hypervisors”
v “Controllers” on page 267
v “Data Stores” on page 267
v “Disks” on page 268
v “Paths” on page 268
v “Virtual Machines” on page 269
v “VMDKs” on page 269
Important: Not all the attributes upon which you can alert are listed here. A
number of other attributes are available for alerts and are based on the key
properties of a hypervisor. To view a complete list of hypervisor attributes upon
which you can alert, go to Servers > Hypervisors, right-click the hypervisor, and
select Edit Alert Definitions.
Attributes that are automatically configured for alerts are marked with an asterisk
(*).
Tip: For capacity attributes, you can generate alerts when the amount of storage is
greater than, less than, or equal to a specified value. You can also determine the unit
of measurement for the attribute, such as KiB, MiB, GiB, or TiB.
Hypervisors
Table 72. Triggering attributes and conditions for general hypervisor changes.
General Attributes Descriptions of Triggering Conditions
Last Successful Probe A specified amount of time has passed since a probe was able to collect data
about a hypervisor. You can use this alert to be notified when up-to-date
configuration and status data is not being collected about a hypervisor and its
existing data might be stale. Data collection might be interrupted or not occur if
the resource, network, or IBM Spectrum Control server is unavailable.
Probe Status* One of the following statuses is detected for a probe:
Not Successful
An error or warning occurred during data collection. This status
indicates that a probe did not collect any data, or only collected a partial
set of data about a resource.
Warning
A probe completed, but might not have collected a complete set of data.
This status might occur if data cannot be collected about one or more of
the internal resources of a resource.
Error (default)
A probe did not complete when it attempted to collect asset data about
the resource. This status might occur if the resource cannot be reached
during data collection.
For details about why a specific status occurred, check the log for the probe. To
check the log, go to the details page for a resource, click Data Collection, and
select Actions > Open Logs in the Probe section on the Data Collection page.
Controllers
Table 73. Triggering attributes and conditions for general changes on controllers.
Controller Attributes Descriptions of Triggering Conditions
New Disk Controller A disk controller is detected for the first time. Use this alert to be notified of
hardware additions on servers.
Removed Disk Controller A previously monitored disk controller can no longer be found. Historical data
about the controller is retained, but no current data is being collected. Use this
alert to be notified if a controller is removed or becomes unavailable.
Data Stores
Table 74. Triggering attributes and conditions for general changes on data stores.
Data Store Attributes Descriptions of Triggering Conditions
Deleted Logical Volume A previously monitored logical volume on a data store can no longer be found.
Historical data about the volume is retained, but no current data is being
collected. Use this alert to be notified if a volume is deleted or becomes
unavailable.
New Logical Volume A logical volume on the data store is detected for the first time.
VMDKs You can use a number of operators to determine when you are notified of the
number of virtual machine disk files (VMDKs) on the data store. For example,
you can select to be notified when the number of VMDKs changes, or when the
number is or is not a specific number, or when the number lies outside a specific
range.
Table 75. Triggering attributes and conditions for capacity changes on data stores.
Capacity Attributes Descriptions of Triggering Conditions
Available Data Store Space The amount of unused storage space on the hypervisor data store.
Available File System Space The total amount of unused storage space on a file system.
Data Store Capacity The total amount of storage space that is assigned to a data store.
Total File System Capacity The total amount of storage space on a file system.
Used File System Space The amount of used storage space on the hypervisor file system.
Used Space The percentage of storage space that is used on the hypervisor data store.
Disks
Table 76. Triggering attributes and conditions for general changes on disks.
General Attributes Descriptions of Triggering Conditions
Firmware The version of the Licensed Internal Code on the disk changes. You can use a
number of operators to determine when you are notified of a firmware change,
such as when the firmware is, or is not, a specific version, or when the version
number contains a specific value.
Multipathing Policy The multipathing policy that is in effect for a disk. For example, you can be
notified when the policy changes, or when the policy is Round Robin, Load
Balancing, Failover Only, or other another policy.
New Disk A disk is detected for the first time. Use this alert to be notified of hardware
changes on servers or hypervisors.
Paths The number of access paths that are associated with the disk falls outside a
specified range, or is equal to or not equal to a specified value.
Removed Disk A previously monitored disk can no longer be found. Historical data about the
disk is retained, but no current data is being collected. Use this alert to be
notified if a disk is removed or becomes unavailable.
Status* One of the following statuses is detected on a disk:
Not Normal
An error or warning status was detected on the disk.
Warning
A warning status was detected on the disk.
Error (default)
An error status was detected on the disk.
Table 77. Triggering attributes and conditions for capacity changes on disks.
Capacity Attributes Descriptions of Triggering Conditions
Available Disk Space The amount of unused storage space on a hypervisor disk.
Capacity The total amount of storage space assigned to a hypervisor disk.
Used Space The amount of used storage space on a hypervisor disk .
Paths
Table 78. Triggering attributes and conditions for general changes on paths.
Path Attributes Descriptions of Triggering Conditions
Deleted Path A previously monitored access path for a server disk can no longer be found.
This change might or might not affect the availability of the disk because there
might be more than one path available.
New Path An access path for a disk is detected for the first time.
Virtual Machines
Table 79. Triggering attributes and conditions for general changes on virtual machines.
Virtual Machine Attributes Descriptions of Triggering Conditions
Deleted Virtual Machine A previously monitored access path for a virtual machine can no longer be
found. Historical data about the virtual machine is retained, but no current data
is being collected. Use this alert to be notified if a virtual machine is deleted or
becomes unavailable.
New Virtual Machine A virtual machine is detected for the first time.
Status One of the following statuses is detected on a virtual machine:
Not Normal
An error or warning status was detected on the virtual machine.
Warning
A warning status was detected on the virtual machine.
Error (default)
An error status was detected on the virtual machine.
VMDKs You can use a number of operators to determine when you are notified of the
number of VMDKs on the virtual machine. For example, you can select to be
notified when the number of VMDKs changes, or when the number is or is not a
specific number, or when the number lies outside a specific range.
Table 80. Triggering attributes and conditions for capacity changes on virtual machines.
Capacity Attributes Descriptions of Triggering Conditions
Capacity The total amount of storage space assigned to a virtual machine hosted by the
hypervisor.
VMDKs
Table 81. Triggering attributes and conditions for general changes on virtual machine disks (VMDKs).
VMDK Attributes Descriptions of Triggering Conditions
Deleted Virtual Disk A previously monitored virtual disk can no longer be found. Historical data
about the virtual disk is retained, but no current data is being collected. Use this
alert to be notified if a virtual disk is deleted or becomes unavailable.
New Virtual Disk A virtual disk is detected for the first time.
Used Space The percentage of storage space that is used on the VMDK on the hypervisor
data store. The used space is available if a Storage Resource agent is deployed.
Alerts can notify you of general changes and performance issues on the following
resources:
v “Switches (performance)”
v “Switches (general changes)” on page 271
v “Ports” on page 272
Important: Not all the attributes upon which you can alert are listed here. A
number of other attributes are available for alerts and are based on the key
properties of a switch. To view a complete list of attributes upon which you can
alert, go to Network > Switches, right-click a switch, and select Edit Alert
Definitions.
Attributes that are automatically configured for alerts are marked with an asterisk
(*).
Switches (performance)
Define alerts that notify you when the performance of a switch falls outside a
specified threshold. In alerts, you can specify conditions based on metrics that
measure the performance of switch ports, including I/O, data, and error rates, and
frame transfer sizes. By creating alerts with performance conditions, you can be
informed about potential bottlenecks in your network infrastructure.
For example, you can define an alert to be notified when the port congestion index
for a port is greater than or equal to a specified threshold. Port congestion
represents the estimated degree to which frame transmission was delayed due to a
lack of buffer credits. Use this alert to help identify port conditions that might slow
the performance of the resources to which those ports are connected.
You can also be notified when a metric is less than a specified threshold, such as
when you want to identify ports that might be under used.
For a complete list of switch metrics that can be alerted upon, see “Performance
metrics for switches” on page 333.
Last Successful Probe A specified amount of time has passed since a probe or performance monitor was
able to collect data about a switch. You can use this alert to be notified when
Last Successful Monitor up-to-date configuration, status, or performance data is not being collected about
a switch and its existing data might be stale. This situation might occur if the
resource, network, or IBM Spectrum Control server is unavailable.
Probe Status* One of the following statuses is detected for a probe:
Not Successful
An error or warning occurred during data collection. This status
indicates that a probe did not collect any data, or only collected a partial
set of data about a resource.
Warning
A probe completed, but might not have collected a complete set of data.
This status might occur if data cannot be collected about one or more of
the internal resources of a resource.
Error (default)
A probe did not complete when it attempted to collect asset data about
the resource. This status might occur if the resource cannot be reached
during data collection.
For details about why a specific status occurred, check the log for the probe. To
check the log, go to the details page for a resource, click Data Collection, and
select Actions > Open Logs in the Probe section on the Data Collection page.
Ports
Table 84. Triggering attributes and conditions for general changes on ports
General Attributes Triggering Conditions for Attributes
Removed Port A previously monitored port can no longer be found. Historical data about the
port is retained, but no current data is being collected. Use this alert to be
notified if a port is removed or becomes unavailable.
Speed The negotiated speed of a port, which is measured in GiB per second. You can
generate an alert when the port speed changes, or when it is greater than, less
than, equal to, or is not equal to a specific value.
Alerts can notify you of general changes on the following types of fabric resources:
v “Fabrics” on page 273
v “Switches” on page 274
Attributes that are automatically configured for alerts are marked with an asterisk
(*).
Fabrics
Table 85. Triggering attributes and conditions for general changes on fabrics
Fabric Attributes Triggering Conditions for Attributes
Last Successful Probe A specified amount of time has passed since a probe was able to collect data
about a fabric. You can use this alert to be notified when up-to-date configuration
and status data is not being collected about a fabric and its existing data might
be stale. This situation might occur if the fabric, network, or IBM Spectrum
Control server is unavailable.
Probe Status* One of the following statuses is detected for a probe:
Not Successful
An error or warning occurred during data collection. This status
indicates that a probe did not collect any data, or only collected a partial
set of data about a resource.
Warning
A probe completed, but might not have collected a complete set of data.
This status might occur if data cannot be collected about one or more of
the internal resources of a resource.
Error (default)
A probe did not complete when it attempted to collect asset data about
the resource. This status might occur if the resource cannot be reached
during data collection.
For details about why a specific status occurred, check the log for the probe. To
check the log, go to the details page for a resource, click Data Collection, and
select Actions > Open Logs in the Probe section on the Data Collection page.
Alerts can notify you of general changes and capacity changes on the following
resources:
v “Servers” on page 275
v “Controllers” on page 276
v “Disks” on page 277
v “Disk Groups” on page 278
v “File Systems and Logical Volumes” on page 278
v “Paths” on page 279
v “Shares” on page 280
v “Triggering conditions for the IBM Spectrum Control server” on page 280
Attributes that are automatically configured for alerts are marked with an asterisk
(*).
Tip: For capacity attributes, you can generate alerts when the amount of storage is
greater than, less than, or equal to a specified value. You can also determine the unit
of measurement for the attribute, such as KiB, MiB, GiB, or TiB.
Servers
Table 87. Triggering attributes and conditions for general changes on servers.
General Attributes Descriptions of Triggering Conditions
Agent State* A Storage Resource agent is in one of the following states:
Not Normal
An error or warning state was detected on a Storage Resource agent.
Warning
A warning state was detected on a Storage Resource agent. For example,
a warning state might occur when an agent must be upgraded to the
same version level as the IBM Spectrum Control server to which it is
communicating.
Error (default)
An error state was detected on a Storage Resource agent. For example,
an error state might occur when an agent was not able to be upgraded.
Last Successful Probe A specified amount of time has passed since a probe was able to collect data
about a server. You can use this alert to be notified when up-to-date
configuration and status data is not being collected about a server and its existing
data might be stale. Data collection might be interrupted or not occur if the
resource, network, or IBM Spectrum Control server are unavailable.
Probe Status* One of the following statuses is detected for a probe:
Not Successful
An error or warning occurred during data collection. This status
indicates that a probe did not collect any data, or only collected a partial
set of data about a resource.
Warning
A probe completed, but might not have collected a complete set of data.
This status might occur if data cannot be collected about one or more of
the internal resources of a resource.
Error (default)
A probe did not complete when it attempted to collect asset data about
the resource. This status might occur if the resource cannot be reached
during data collection.
For details about why a specific status occurred, check the log for the probe. To
check the log, go to the details page for a resource, click Data Collection, and
select Actions > Open Logs in the Probe section on the Data Collection page.
Table 88. Triggering attributes and conditions for capacity changes on servers.
Capacity Attributes Descriptions of Triggering Conditions
Available Disk Space The amount of unused disk space on the local and SAN-attached storage for the
server. SAN-attached storage is assigned to the server from storage systems.
Available File System Space The amount of unused storage space in the file systems on the server.
Unused file system space does not include space that is reserved for the
operating system. For example, the unused space for tmpfs on UNIX operating
systems is not included in this value.
Disk Space from Storage Systems The amount of disk space that is assigned to the server from storage systems.
The disk space from storage systems is only available when SAN-attached
storage is assigned to the server.
File System Capacity The amount of file system space on the server.
File System Space from Storage The amount of file system space that is assigned to the server from storage
Systems systems.
The file system space from storage systems is only available when SAN-attached
storage is assigned to the server.
Total Disk Space The total amount of disk space for all the local and SAN-attached storage on the
server. SAN-attached storage is assigned to the server from storage systems.
Used Space The amount of used disk space on the local and SAN-attached storage for the
server. SAN-attached storage is assigned to the server from storage systems.
Controllers
v Driver Version The version of the driver, firmware, or read-only memory (ROM) on a disk
controller changes. You can use a number of operators to determine when you
v Firmware
are notified of a version change, such as when the driver, firmware, or ROM is,
v ROM Version or is not, a specific version, or when the version number contains a specific
value.
Disks
Table 90. Triggering attributes and conditions for general changes on disks.
General Attributes Descriptions of Triggering Conditions
Firmware The version of the Licensed Internal Code on the disk changes. You can use a
number of operators to determine when you are notified of a firmware change,
such as when the firmware is, or is not, a specific version, or when the version
number contains a specific value.
Multipathing Policy The multipathing policy that is in effect for a disk. For example, you can be
notified when the policy changes, or when the policy is Round Robin, Load
Balancing, Failover Only, or other another policy.
New Disk A disk is detected for the first time. Use this alert to be notified of hardware
changes on servers or hypervisors.
Paths The number of access paths that are associated with the disk falls outside a
specified range, or is equal to or not equal to a specified value.
Removed Disk A previously monitored disk can no longer be found. Historical data about the
disk is retained, but no current data is being collected. Use this alert to be
notified if a disk is removed or becomes unavailable.
Status* One of the following statuses is detected on a disk:
Not Normal
An error or warning status was detected on the disk.
Warning
A warning status was detected on the disk.
Error (default)
An error status was detected on the disk.
Available Disk Space The amount of unused storage space on a disk that is attached to the server.
Capacity The total amount of storage space on a disk that is attached to the server.
Used Space The amount of used storage space on a disk that is attached to the server.
Disk Groups
Table 92. Triggering attributes and conditions for general changes on disk groups (volume groups).
General Attributes Descriptions of Triggering Conditions
Deleted Volume Group A previously monitored volume group can no longer be found. Historical data
about the volume group is retained, but no current data is being collected. Use
this alert to be notified if a volume group is deleted or becomes unavailable.
New Volume Group A volume group is detected for the first time.
Status* One of the following statuses is detected on a disk group:
Not Normal
An error or warning status was detected on the disk group.
Warning
A warning status was detected on the disk group.
Error (default)
An error status was detected on the disk group.
Table 93. Triggering attributes and conditions for capacity changes on disk groups (volume groups).
Capacity Attributes Descriptions of Triggering Conditions
Available Space The amount of unused storage space on a server disk group.
Used Space The amount of used storage space on a server disk group.
Volume Group Capacity The total amount of storage space on a server volume group. This value is
inclusive of all storage space and applies to all space values related to volume
groups.
Table 95. Triggering attributes and conditions for capacity changes on file systems and logical volumes.
Capacity Attributes Descriptions of Triggering Conditions
Available File System Space The amount of unused storage space on a file system on the server disk.
File System Capacity The total amount of storage space on a file system on the server disk.
Logical Volume Capacity The total amount of storage space on a logical volume on the server disk.
Used File System Space The amount of used storage space on a file system on the server disk.
Used Space The percentage of used storage space on a file system or logical volume on the
server disk.
Paths
Table 96. Triggering attributes and conditions for general changes on paths.
Path Attributes Descriptions of Triggering Conditions
Deleted Path A previously monitored access path for a server disk can no longer be found.
This change might or might not affect the availability of the disk because there
might be more than one path available.
New Path An access path for a disk is detected for the first time.
Status* One of the following statuses is detected on a path:
Not Normal
An error or warning status was detected on the path.
Warning
A warning status was detected on the path.
Error (default)
An error status was detected on the path.
You can define the following options that enable you to specify conditions that
suppress alerts.
Do not suppress alerts
Receive alert notifications whenever an alert violation is detected.
Only alert once until problem clears
Receive one notification for an alert violation, even if the condition is
violated multiple times. This option is the default.
Only generate alerts every
Receive one notification when an alert is initially violated. The alert is
suppressed and no notifications are sent until both the specified time has
passed and the alert is triggered again.
You can specify that the following actions are taken when alert conditions are
detected on monitored resources:
Run script
Run a script when an alert is triggered for the condition. Use a script to
call external programs or run commands that take action as the result of an
alert. By using a script, you can automatically address potential storage
issues when they are detected to avoid unplanned downtime or
performance bottlenecks. Learn more.
Email Send emails to specific email addresses when an alert is detected on a
monitored resource.
Netcool or OMNIbus EIF Probe Server
Send alert notifications to a Netcool server or OMNIbus EIF probe server
within your environment that was configured to receive IBM Spectrum
Control alerts.
You must include the script files that you want to run in the /scripts directory on
the server where IBM Spectrum Control is installed. The default path of /scripts
is determined by the operating system of the server:
v Windows: C:\Program Files\IBM\TPC\Data\scripts
v UNIX or Linux: /opt/IBM/TPC/Data/scripts or /usr/IBM/TPC/Data/scripts
Tip: When you run a script against a NAS filer, the script is run from the Storage
Resource agent that is assigned to the file system where the condition was
detected.
When you run scripts in response to alerts, the names of those scripts are resolved
by using the following criteria:
v The operating system of the server where the product is installed.
v The script name that you specify on the Script name field when you define or
edit an alert definition.
The operating system of the server or Storage Resource agent where you choose to
run a script determines how that script that is run:
UNIX, Linux operating systems
A Storage Resource agent that is deployed on a UNIX or Linux operating
system does not run scripts that have an extension. If the specified script
name contains an extension, the agent ignores the extension and searches
for a file of the same name (without an extension). For example, if you
enter backup.vbs in the Script name field, a UNIX or Linux agent searches
for a file with the name backup. If the script exists, the first line of the
script is read and the appropriate interpreter is used to run the script. If a
file cannot be found, no action is taken.
Windows operating systems
A Storage Resource agent that is deployed on a Windows operating system
runs scripts that have an extension. The extension of a script file
determines which interpreter is used to run the script. If you specify a
script name that does not contain an extension, the agent searches for the
file name in the following order (based on its extension): .com, .exe,
.bat, .cmd, .vbs, .vbe, .js, .jse. If a file cannot be found, no action is
taken.
282 IBM Spectrum Control: User's Guide
Tip: You can run scripts with the same name across multiple operating systems. To
run a script on both a UNIX or Linux and Windows operating systems, you must
have two versions of that file in the /scripts directory. For example, if you want
to run a provisioning script against Storage Resource agents on UNIX or Linux and
Windows servers, you must have two versions of that file (provision.bat and
provision) in /scripts.
Performance data
Use the IBM Spectrum Control to view the performance data of devices in your
environment.
Performance metrics
IBM Spectrum Control can collect information about the performance of storage
systems and switches. This information includes metrics that measure the
performance of volumes, ports, and disks. You can view performance information
or specify alerts for when the performance of a resource falls outside a specified
range.
Overview
Volume metrics
Tip: Unless otherwise noted, you can view the volume metrics in Table 100,
Table 101 on page 285, Table 102 on page 286, and Table 103 on page 288 for the
following resources:
v Host connections
v Nodes
v Pools
v RAID arrays
v Storage systems
v Volumes
Table 100. Key volume metrics.
Metric Description
1
Cache Holding Time The average number of seconds that I/O
data for a storage system node is held in the
cache. A short cache-holding time indicates
adverse performance.
Data Rate (Read) The average number of MiB per second that
are transferred for read operations.
Data Rate (Write) The average number of MiB per second that
are transferred for write operations.
Data Rate (Total) The average number of MiB per second that
are transferred for read operations and write
operations.
Overall I/O Rate (Read) The average number of read operations per
second. This value includes both sequential
and nonsequential read operations.
Overall I/O Rate (Write) The average number of write operations per
second. This value includes both sequential
and nonsequential write operations.
Overall I/O Rate (Total) The average number of read operations and
write operations per second. This value
includes both sequential and nonsequential
operations.
Pool Activity Score2 The activity level of pools, which is set to
the following value:
Disk metrics
Tip: Unless otherwise noted, you can view the volume metrics in Table 104 and
Table 105 on page 289 for the following resources:
v Nodes
v Pools
v RAID arrays
v Ranks
v Storage systems
Table 104. Key disk metrics.
Metric Description
Data Rate (Read) The average number of MiB per second that
are read from the back-end storage
resources.
Data Rate (Write) The average number of MiB per second that
are written to the back-end storage
resources.
Data Rate (Total) The average rate at which data is
transmitted between the back-end storage
resources and the component. The rate is
measured in MiB per second and includes
both read and write operations.
Tip: Unless otherwise noted, you can view the port metrics in Table 106, Table 110
on page 292, Table 111 on page 295, and Table 112 on page 295 for ports and
storage systems. The port metrics in Table 107 on page 291, Table 108 on page 291,
Table 109 on page 292 are only available for ports.
Table 106. Key port metrics.
Metric Description
Data Rate (Receive) The average rate at which data is received
by the port. The rate is measured in MiB per
second.
Data Rate (Send) The average rate at which data is sent
through the port. The rate is measured in
MiB per second.
Data Rate (Total) The average rate at which data is transferred
through the port. The rate is measured in
MiB per second and includes both send and
receive operations.
I/O Rate (Receive) The average number of I/O operations per
second for operations in which the port
receives data.
I/O Rate (Send) The average number of I/O operations per
second for operations in which data is sent
from a port.
I/O Rate (Total) The average number of send operations and
receive operations per second.
Response Time (Receive) The average number of milliseconds to
complete a receive operation.
Response Time (Send) The average number of milliseconds to
complete a send operation.
Response Time (Overall) The average number of milliseconds to
complete a send or receive operation.
Port Utilization (Receive)1 The average percentage of time that the port
is busy receiving data.
Port Utilization (Send)1 The average percentage of time that the port
is busy sending data.
Port Utilization (Overall)1 The average percentage of time that the port
is busy sending or receiving data.
Overview
Definitions are provided for the performance metrics that are collected for the
following storage systems:
v FlashSystem V840
v FlashSystem V9000
v SAN Volume Controller
v Storwize V3500
v Storwize V3700
v Storwize V5000
v Storwize V7000
v Storwize V7000 Unified
Tip: Unless otherwise noted, you can view the volume metrics in Table 113 on
page 297, Table 114 on page 298, Table 115 on page 298, Table 116 on page 299,
Table 117 on page 299, Table 118 on page 299, Table 119 on page 301, Table 120 on
page 303, and Table 121 on page 304 for the following resources:
v Host connections
v I/O groups
v Nodes
v Pools
v Storage systems
v Volumes
Volume cache metrics are only available for SAN Volume Controller, Storwize, and
FlashSystem block storage systems whose firmware version is V7.3 or later.
Table 118. Volume cache metrics for volumes.
Metric Definition
Cache Hits (Dirty Writes) The percentage of all cache write hits that
occur on data that is marked as modified in
the volume cache. This value represents how
effectively write operations are coalesced
before the data is written to disk.
Cache Hits (Read) The percentage of read operations that find
data in the volume cache.
Cache Hits (Total) The percentage of cache hits for read and
write operations that are handled in the
volume cache.
Cache Hits (Write) The percentage of cache hits for write
operations that are handled in the volume
cache.
Volume copy cache metrics are only available for SAN Volume Controller,
Storwize, and FlashSystem block storage systems whose firmware version is V7.3
or later.
Table 119. Volume copy cache metrics for volumes.
Metric Definition
Cache Hits (Dirty Writes) The percentage of all cache write hits that
occur on data that is marked as modified in
the volume copy cache. This value
represents how effectively write operations
are coalesced before the data is written to
disk.
Cache Hits (Read-ahead)* The percentage of all read cache hits that
occur on pre-staged data.
Cache Hits (Read) The percentage of read operations that find
data in the volume copy cache.
Cache Hits (Total) The percentage of cache hits for read and
write operations that are handled in the
volume copy cache.
Cache Hits (Write) The percentage of cache hits for write
operations that are handled in the volume
copy cache.
I/O Rate (Destage) The average number of cache-to-disk
transfer operations per second that are
processed in the volume copy cache.
I/O Rate (Prestage) The average number of prefetch
disk-to-cache transfer operations per second
that are processed in the volume copy cache.
I/O Rate (Stage) The average number of disk-to-cache
transfer operations per second that are not
prefetch operations and are processed in the
volume copy cache.
I/O Rate (Read) The average number of read operations per
second that are processed in the volume
copy cache. This value includes read
operations that are associated with
FlashCopy services, volume mirroring, and
other internal processes. This value might
also include some operations that are passed
from the volume cache.
Tip: Unless otherwise noted, you can view the volume metrics in Table 120 for the
following resources:
v Nodes
v I/O groups
v Host connections
v Storage systems
Table 120. Miscellaneous metrics for volumes.
Metric Definition
1
Cache to Host Transfer Response Time The average number of milliseconds that is
taken to transfer a track from the cache to
the host, including any queuing time that
occurs because of throttling.
Non-Preferred Node Usage Percentage2 The overall percentage of I/O operations
that are not directed against the preferred
node for each volume in an I/O Group.
There is a small performance penalty when
I/O does not go to the preferred node for
each volume.
Transfer Size (Read) The average number of KiB that are
transferred per read operation.
Transfer Size (Write) The average number of KiB that are
transferred per write operation.
Transfer Size (Overall) The average number of KiB that are
transferred per I/O operation. This value
includes both read and write operations.
Unaligned Write I/O Rate3 The average number of write operations per
second that are not aligned on a boundary
between 4 KB physical blocks. Unaligned
write operations can cause a significant
decrease in efficiency of write operations to
some types of back-end disks. You can
ignore this metric for iSeries servers.
Legacy cache metrics are only available for SAN Volume Controller and Storwize
block storage systems whose firmware version is earlier than V7.3.
Table 121. Legacy cache metrics for volumes.
Metric Definition
Write-Cache Percentages (Flush-through) The percentage of tracks that are written to
disk in flush-through mode. This value
applies only to storage systems that are
running a version of IBM Spectrum
Virtualize earlier than V7.3.
Write-Cache Percentages (Write-through) The percentage of tracks that are written to
disk in write-through mode. This value
applies only to storage systems that are
running a version of IBM Spectrum
Virtualize earlier than V7.3.
Write-Cache Percentages (Overflow) The percentage of all write operations that
are handled in the cache. This value includes
both sequential and random write
operations, and write operations in the
volume cache and volume copy cache where
applicable.
Write-Cache I/O Rate (Flush-through) The average number of tracks per second
that are written to disk in flush-through
mode. This value applies only to storage
systems that are running a version of IBM
Spectrum Virtualize earlier than V7.3.
Write-Cache I/O Rate (Overflow) The average number of tracks per second
that are written but are delayed because
there is not enough space in the write cache.
This value applies only to storage systems
that are running a version of IBM Spectrum
Virtualize earlier than V7.3.
Write-Cache I/O Rate (Write-through) The average number of tracks per second
that are written to disk in write-through
mode. This value applies only to storage
systems that are running a version of IBM
Spectrum Virtualize earlier than V7.3.
Unless otherwise noted, you can view disk metrics for the following resources:
v Managed disks
v Pools
v Nodes
v I/O Groups
v Storage systems
Table 122. Key metrics for disks
Metric Definition
Data Rate (Read) The average number of MiB per second that
are read from the back-end storage
resources.
Data Rate (Write) The average number of MiB per second that
are written to the back-end storage
resources.
Data Rate (Total) The average rate at which data is
transmitted between the back-end storage
resources and the component. The rate is
measured in MiB per second and includes
both read and write operations.
I/O Rate (Read)1 The average number of read operations per
second that are issued to the back-end
storage resources.
I/O Rate (Write)2 The average number of write operations per
second that are issued to the back-end
storage resources.
I/O Rate (Total)3 The average number of I/O operations per
second that are transmitted between the
back-end storage resources and the
component. This value includes both read
and write operations.
Response Time (Read) The average number of milliseconds for the
back-end storage resources to respond to a
read operation.
Unless otherwise noted, you can view port metrics for the following resources:
v Ports
v Nodes
v I/O Groups
v Storage systems
Table 125. Key metrics for ports
Metric Definition
I/O Rate (Receive) The average number of I/O operations per
second for operations in which the port
receives data.
I/O Rate (Send) The average number of I/O operations per
second for operations in which data is sent
from a port.
I/O Rate (Total) The average number of send operations and
receive operations per second.
Data Rate (Receive) The average number of I/O operations per
second for operations in which the port
receives data.
Metrics availability restrictions: The response time metrics are available for
nodes, I/O groups, and storage system.
Table 129. Error rate metrics for ports
Metric Definition
CRC Error Rate The average number of frames per second
that are received in which a cyclic
redundancy check (CRC) error is detected. A
CRC error is detected when the CRC in the
transmitted frame does not match the CRC
computed by the receiver. For Brocade
switches, this metric includes only the CRC
Errors with a good end-of-frame (EOF)
indicator.
Link Errors (Invalid Link Transmission Rate) The average number of bit errors per second
that are detected.
Link Errors (Invalid Transmission Word The average number of bit errors per second
Rate) that are detected.
Unless otherwise noted, you can view node metrics for the following resources:
v Nodes
For XIV systems, performance metrics are available for the following resources:
v “Volume metrics”
v “Port metrics” on page 317
For IBM Spectrum Accelerate, performance metrics are available for the following
resource:
v “Volume metrics”
Restriction: XIV systems and IBM Spectrum Accelerate do not track performance
statistics for volumes that were never used. Because there are no performance
statistics, performance metrics are not shown for these volumes and their related
components.
Volume metrics
Port metrics
The following performance metrics for ports are available for XIV systems that are
version 10.2.4 or later:
v I/O rate metrics
v Data rate metrics
v Response time metrics
v Miscellaneous port metrics
Restriction: Port metrics are not available for IBM Spectrum Accelerate.
Table 136. I/O rate metrics
Metric Description
I/O Rate (Send) The average number of I/O operations per
second for operations in which data is sent
from a port.
I/O Rate (Receive) The average number of I/O operations per
second for operations in which the port
receives data.
When you view metrics for ESS systems, you must take into account the following
differences between IBM Spectrum Control reports and the native reports of those
systems:
v IBM Spectrum Control reports display port performance metrics as send and
receive metrics, such as Data Rate (Send) and Data Rate (Receive).
v Reports that are included with storage systems (for example, reports based on
data that is collected by the DS CLI) display port performance metrics as read
and write metrics, such as Byteread and Bytewrite.
Volume metrics
Disk metrics
Port metrics
Overview
You can view the following metrics for each GPFS cluster node.
Table 153. Metrics for nodes.
Metric Definition
CPU Utilization (User) The average percentage of time that the
processors on a node are busy doing user
tasks.
CPU Utilization (System) The average percentage of time that the
processors on a node are busy doing system
tasks.
CPU Utilization (Total) The average percentage of time that the
processors on a node are busy doing user
tasks and system tasks.
Memory Used (Cache and Buffer) The average percentage of memory on a
node that is used for cache and buffer
memory.
Memory Used The average percentage of memory that is
used on a node. This value does not include
the memory that is used for cache and
buffer memory.
Memory Used (Total) The average percentage of memory that is
used on a node. This value includes the
memory that is used for cache and buffer
memory.
I/O Rate (Read) The average number of read operations per
second.
I/O Rate (Write) The average number of write operations per
second.
I/O Rate (Total) The average number of read operations and
write operations per second.
You can view file system metrics for the following resources:
v File systems
v IBM Spectrum Scale storage systems
Tip: For a storage system, the metrics contain summary values for all the file
systems on the storage system.
Table 154. Metrics for file systems.
Metric Definition
Data Rate (Read) The average number of MiB per second that
are transferred for read operations.
Data Rate (Write) The average number of MiB per second that
are transferred for write operations.
Data Rate (Total) The average number of MiB per second that
are transferred for read operations and write
operations.
Maximum Data Rate (Read) The maximum number of MiB per second
that are transferred for read operations.
Maximum Data Rate (Write) The maximum number of MiB per second
that are transferred for write operations.
Maximum Data Rate (Total) The maximum number of MiB per second
that are transferred for read operations and
write operations.
I/O Rate (Read) The average number of read operations per
second.
I/O Rate (Write) The average number of write operations per
second.
I/O Rate (Total) The average number of read operations and
write operations per second.
Maximum I/O Rate (Read) The maximum number of read operations
per second.
Maximum I/O Rate (Write) The maximum number of write operations
per second.
Maximum I/O Rate (Total) The maximum number of read operations
and write operations per second.
Response Time (Read) The average number of milliseconds for the
back-end storage resources to respond to a
read operation from the file system.
Response Time (Write) The average number of milliseconds for the
back-end storage resources to respond to a
write operation from the file system.
Response Time (Overall) The average number of milliseconds for the
back-end storage resources to respond to a
read operation or a write operation from the
file system.
Volume metrics
Tip: Unless otherwise noted, you can view the volume metrics in Table 155,
Table 156 on page 332, and Table 157 on page 332 for the following resources:
v Volumes
v Nodes
v Storage systems
Table 155. Key volume metrics.
Metric Description
Overall I/O Rate (Read) The average number of read operations per
second. This value includes both sequential
and nonsequential read operations.
Overall I/O Rate (Write) The average number of write operations per
second. This value includes both sequential
and nonsequential write operations.
Overall I/O Rate (Total) The average number of read operations and
write operations per second. This value
includes both sequential and nonsequential
operations.
Data Rate (Read) The average number of MiB per second that
are transferred for read operations.
Data Rate (Write) The average number of MiB per second that
are transferred for write operations.
Data Rate (Total) The average number of MiB per second that
are transferred for read operations and write
operations.
Response Time (Read) The average number of milliseconds to
complete a read operation.
Response Time (Write) The average number of milliseconds to
complete a write operation.
Response Time (Overall) The average number of milliseconds to
complete an I/O operation. This value
includes both read and write operations.
Volume Utilization1 The average percentage of time that the
volume is busy.
Port metrics
Performance metrics for switches are divided into the following categories:
v Key port metrics
v I/O rate metrics
v Peak data rate metrics
v Frame error rate metrics
v Port protocol error rate metrics
v Link error rate metrics
v Miscellaneous metrics
IBM Spectrum Control provides block storage provisioning capabilities that the
storage administrator can employ to define the properties and characteristics of
storage volumes within a particular service class. For example, a block storage
The Cinder driver enables an OpenStack cloud to use these defined service classes,
which are available in your Cinder environment as Cinder volume types. For each
block storage service class, a Cinder volume type is created. Your cloud users can
create and use volumes of this type.
To download the IBM Spectrum Control Cinder driver and installation instructions
go to https://www.ibm.com/developerworks/servicemanagement/sm/
spectrum_control/index.html and click the Downloads tab.
The Cinder driver works with this information through the medium of service
classes. A service class is used to identify classes of storage within the storage
infrastructure that can be configured for such services as thin provisioning,
virtualized volumes, and varying RAID levels. Service classes can be configured to
use storage across multiple devices and device types that still meet the constraints
that are defined within the service class. The Cinder driver can discover the service
classes that are configured within IBM Spectrum Control and create corresponding
volume types within the OpenStack environment. The user can then provision a
volume from the service classes that are already defined within IBM Spectrum
Control.
When the Cinder driver is requested to attach a volume to a Nova node, the
Cinder driver submits required access information to the IBM Spectrum Control
service. The service then assigns the volume to all available host ports associated
with the Nova node.
An OpenStack cloud administrator can change which access protocol the Cinder
driver attempts to assign first. The setting is the tpc_preferred_protocol
parameter in the cinder.conf driver configuration section. By changing the
preferred protocol to iSCSI, the Cinder driver first attempts to provide iSCSI
access. If unsuccessful, the Cinder driver falls back to Fibre Channel access. If the
preferred protocol cannot be met but an alternative protocol is available, then the
alternative protocol is chosen.
Download this zip file and extract its contents to a location on the IBM Spectrum
Control server. Open a command prompt to the tpc-scripts directory and run the
setup script for your platform.
Note: You must restart the IBM Spectrum Control Device, Data, and Web servers
to complete the setup process.
For example, if the Cinder node is running Red Hat, copy the
openstack-tpcdriver-1.0.0-1.x86_64.rhel.rpm file and install the file using the
command rpm -ivh openstack-tpcdriver-1.0.0-1.x86_64.rhel.rpm.
Upon installation of the .rpm or .deb file, you can run the tpcdriver-config.sh
utility to help determine appropriate Cinder settings for your installation.
Copy the appropriate settings into your cinder.conf file and restart the Cinder
volume service to enable the Cinder driver.
Once the Cinder driver is installed and configured, you can verify the installation
and configuration by navigating to the Volumes page of the Horizon Admin panel
to check that the service classes configured within IBM Spectrum Control are now
available as volume types.
Note: In IBM Spectrum Control version 5.2.1, iSCSI ports appear as Fibre
Channel ports within the IBM Spectrum Control GUI. The WWPN of the iSCSI
port is the iSCSI name of the port itself.
In IBM Spectrum Control 5.2.2, iSCSI ports appear as Fibre Channel ports
within the IBM Spectrum Control GUI. The WWPN of the iSCSI port is the
iSCSI name of the port itself.
You need to install IBM Spectrum Control with IBM Spectrum Control Advanced
Edition license. You also need:
v A local operating system, LDAP, or Windows Domain group to add to IBM
Spectrum Control
The setup script configures a IBM Spectrum Control server with the files required
to enable the supported OpenStack functionality on the IBM Spectrum Control
server. For more information about installing the Cinder driver, see “Requirements
for installing the Cinder driver” on page 342 and “Installing the Cinder driver.”
The unsetup script reconfigures a a IBM Spectrum Control server with the files
required to disable supported OpenStack functionality on the a IBM Spectrum
Control server. For more information about uninstalling the Cinder driver, see
“Uninstalling the Cinder driver” on page 345.
When IBM Spectrum Control Cinder driver is installed, you are ready to enable
OpenStack and IBM Spectrum Control to work together. The cinder-packages
directory contains the platform specific Cinder driver installer packages . Both the
IBM Spectrum Control server and the OpenStack Cinder node need to be patched.
v Red Hat Enterprise Linux 6.4 or higher: openstack-tpcdriver-1.0.1-
1.x86_64.rhel.rpm
v Ubuntu 12.04: openstack-tpcdriver_1.0.1-1_all.deb
1. Log on to IBM Spectrum Control server as root for Linux/AIX or as
Administrator for Windows.
2. Change directory to tpc-scripts.
3. Run the setup script, providing the path to the IBM Spectrum Control
installation location. For example:
Option Description
AIX # ./setup_aix.sh /opt/IBM/TPC
Linux # ./setup_linux.sh /opt/IBM/TPC
Windows > setup_windows.bat "C:\Program Files\IBM\TPC"
4. The installer package installs the OpenStack tpc.py driver in the proper
location. It also installs the tpcdriver-config.sh script which generates the
additional Cinder driver-related entries needed for the Cinder configuration file
(/etc/cinder/cinder.conf).
The IBM Spectrum Control server and all OpenStack Cinder nodes need to be
patched to enable IBM Spectrum Control OpenStack functions and policies for the
Cinder driver. Review “Requirements for installing the Cinder driver” on page 342
before you proceed with the installation.
1. Run the IBM Spectrum Control OpenStack patch installation script for AIX,
Linux, or Windows. On IBM Spectrum Control:
a. Log on as root for Linux/AIX or Administrator for Windows.
b. Change directory to tpc-scripts.
c. Run the setup script, specifying the path to the IBM Spectrum Control
server installation location:
v AIX# ./setup_aix.sh /opt/IBM/TPC
v Linux# ./setup_linux.sh /opt/IBM/TPC
v Windows: setup_windows.bat "C:\Program Files\IBM\TPC"
344 IBM Spectrum Control: User's Guide
d. When prompted if you want to proceed with the update, enter Y or y.
Note: You must restart the IBM Spectrum Control Device, Data, and Web
servers to complete the setup process.
2. The IBM Spectrum Control OpenStack patch installation script attempts to
determine the DB2 settings. If the script cannot find a setting, you are
prompted to enter the value. Descriptions of the settings are in the following
table:
Option Description
Hostname of the The host name of the IBM Spectrum Control database server.
DB2 server
Port of the DB2 The port that the IBM Spectrum Control database server is running
server on.
DB2 profile user The user name of the DB2 user on the server this installation script
(AIX/Linux only) is being run on. This setting is only relevant for AIX and Linux.
DB2 user The user name of the DB2 user with permissions to access the IBM
Spectrum Control database.
DB2 password Password for the DB2 user.
Database name The name of the IBM Spectrum Control database.
Schema name The schema name of the IBM Spectrum Control database.
3. Run the Cinder driver installation script for Red Hat and Ubuntu installations.
On the OpenStack Cinder nodes:
a. Ensure that the current user has administrative privileges - root for Red Hat
and Ubuntu.
b. Change directory to cinder-packages.
c. Install the package for your OpenStack distribution:
v Red Hat Enterprise Linux 6.4: # rpm -ivh openstack-tpcdriver-1.0.0-
1.x86_64.rhel.rpm
v Ubuntu 12.04: # dpkg -i openstack-tpcdriver_1.0.0-1.x86_64.deb
Note: If you installed any packages manually (for example, with pip or
from source), you can force the installation by overriding dependency
checks. On Red Hat systems, the --nodeps flag is passed to the rpm
command. On Ubuntu systems, the --force-depends flag is passed to the
dpkg command.
4. Run the tpcdriver-config.sh configuration script. You are prompted to
provide IBM Spectrum Control server information as the script runs: #
/usr/local/bin/tpcdriver-config.sh Refer to “Configuring the Cinder driver”
on page 346 for more details on the Cinder configuration settings specific to
IBM Spectrum Control.
5. Copy the Cinder driver settings that are generated by the tpcdriver-config.sh
script to the [DEFAULT] section of the Cinder configuration file,
/etc/cinder/cinder.conf.
6. Restart the Cinder volume service.
On IBM Spectrum Control, you must plan user and service class details:
v Identify which IBM Spectrum Control user the Cinder driver can use to log on.
The user's group must be added to User Management as External Application.
v Identify the preferred service class. This class is used when no volume type is
specified in the Cinder configuration file. All block service classes available to
the user are available to the Cinder driver as volume types.
The tpcdriver-config.sh script installed on the Cinder node as part of the rpm or
deb file helps to configure the Cinder volume service to use the Cinder driver.
Configure the Cinder driver by editing the Cinder configuration file
(/etc/cinder/cinder.conf.
After you edit the Cinder configuration file, restart Cinder services with the
command: service service-name restart. For Ubuntu, the service-name
parameter is cinder-volume. For RedHat and SLES, the service-name parameter is
openstack-cinder-volume.
To remove a volume type from OpenStack, you must first remove the service class
that is associated with the volume type in IBM Spectrum Control. After the service
class is removed, the OpenStack Administrator must then remove the
corresponding volume type in OpenStack.
For example, you can remove a service class (Gold) from IBM Spectrum Control,
and then remove the type of volume that is associated with the Gold service class.
If a user requests the type of volume that is associated with the Gold service class,
the request is rejected.
If you remove the volume type from OpenStack but do not remove the associated
service class, the volume type is re-created the next time the Cinder driver checks
for available service classes.
IBM Spectrum Control attempts to assign all ports that belong to a Nova node.
When the unmanaged server representing the Nova node contains both Fibre and
iSCSI ports, the volume is available to the Fibre Channel and iSCSI ports on the
Nova node. In some cases, when you detach a volume from a host, the ports for
the access method in use by the Nova node are removed but the access for the
alternative connectivity method remains. This access can cause errors to delete the
volume from the storage system. In this case, the volume is removed from the
Cinder database but it requires manual steps to remove the storage volume from
the storage system.
Option Description
Windows Server 2012 1. On the Dashboard page, hover the
mouse over the lower left corner of the
page next to the Server Manager taskbar
button, and then click Start.
2. On the Start page, right-click, and then
click the All apps taskbar button.
Windows 7, Windows 2008, Windows Vista, Click Start > All Programs.
Windows XP
Option Description
Windows Server 2012 1. On the Dashboard page, hover the
mouse over the lower left corner of the
page next to the Server Manager taskbar
button, and then click Start.
2. On the Start page, right-click, and then
click the All apps taskbar button.
Windows 7, Windows 2008, Windows Vista, Click Start > All Programs.
Windows XP
2. Click IBM DB2 > Command Line Tools > Command Window.
Option Description
Windows Server 2012 1. On the Dashboard page, hover the
mouse over the lower left corner of the
page next to the Server Manager taskbar
button, and then click Start.
2. On the Start page, right-click, and then
click the All apps taskbar button.
Windows 7, Windows 2008, Windows Vista, Click Start > All Programs.
Windows XP
Option Description
Windows Server 2012 1. On the Dashboard page, hover the
mouse over the lower left corner of the
page next to the Server Manager taskbar
button, and then click Start.
2. On the Start page, right-click, and then
click the All apps taskbar button.
Windows 7, Windows 2008, Windows Vista, Click Start > All Programs.
Windows XP
To complete tasks in IBM Spectrum Control, you must open the following
administration and maintenance facilities:
v “Accessing the Control Panel”
v “Accessing Administrative Tools”
v “Accessing Windows Services” on page 351
v “Accessing Computer Management” on page 351
v “Accessing Programs and Program Features” on page 351
Option Description
Windows Server 2012 On the Dashboard page, hover the mouse
over the lower left corner of the page next to
the Server Manager taskbar button, and
then click Start.
Windows 7, Windows 2008, Windows Vista, Click Start.
Windows XP
Option Description
Windows Server 2012 On the Dashboard page, hover the mouse
over the lower left corner of the page next to
the Server Manager taskbar button, and
then click Start.
Windows 7, Windows 2008 Click Start.
Windows XP, Windows Vista Click Start > Control Panel.
Option Description
Windows Server 2012 On the Dashboard page, hover the mouse
over the lower left corner of the page next to
the Server Manager taskbar button, and
then click Start.
Windows 7, Windows 2008 Click Start.
Windows XP, Windows Vista Click Start > Control Panel.
Option Description
Windows Server 2012 On the Dashboard page, hover the mouse
over the lower left corner of the page next to
the Server Manager taskbar button, and
then click Start.
Windows 7, Windows 2008, Windows Vista, Click Start.
Windows XP
Option Description
Windows Server 2012 On the Dashboard page, hover the mouse
over the lower left corner of the page next to
the Server Manager taskbar button, and
then click Start.
Windows 7, Windows 2008, Windows Vista, Click Start.
Windows XP
Option Description
Windows Server 2012 On the Dashboard page, hover the mouse
over the lower left corner of the page next to
the Server Manager taskbar button, and
then click Start.
Windows 7, Windows 2008, Windows Vista, Click Start.
Windows XP
2. Click Run.
Accessibility features
The following list includes the major accessibility features in IBM Spectrum
Control:
v Keyboard-only operation in the GUI.
v A Knowledge Center that includes the following accessibility features:
– The Knowledge Center is provided in XHTML 1.0 format, which is viewable
in most web browsers. With XHTML, you can view documentation according
to the display preferences that are set in your browser. XHTML supports
screen readers and other assistive technologies.
– All documentation for IBM Spectrum Control is available in Adobe Portable
Document Format (PDF) by using the Adobe Acrobat Reader. To access PDFs,
go to http://www.ibm.com/support/knowledgecenter/SS5R93_5.2.9/
com.ibm.spectrum.sc.doc/fqz0_r_printable_doc.html.
– All images in the Knowledge Center are provided with alternative text, so
that visually impaired users can understand the contents of the images.
v Interfaces that are commonly used by screen readers.
The setting for the automatic-refresh button in the screen reader is toggled to the
ON position by default. If you want the screen reader to read the previous text,
complete the following steps:
1. Navigate to the Accessibility Settings Navigation region by using the arrow
keys. The region is located after the IBM Spectrum Control application title.
2. Click Enter to toggle the automatic-refresh button to the OFF position. (An
alert sounds to make you aware that the turn-off automatic-refresh toggle
button was pressed.)
3. To move backward to the previously read text so that the screen reader can
read it again, use the arrow keys. You can move backwards and forwards
through the page.
4. When you are ready to move on, click Enter to toggle the automatic-refresh
button to the ON position and to refresh the page. (An alert sounds to make
you aware that the turn-on, automatic-refresh toggle button was pressed.)
Tip: Alternatively, let the toggle setting persist, and refresh as needed by
pressing the F5 key.
Keyboard navigation
Most of the features of the IBM Spectrum Control GUI are accessible by using the
keyboard. For those features that are not accessible, equivalent function is available
by using the command-line interface (CLI), except as noted in the product release
notes.
You can use keys or key combinations to perform operations and initiate many
menu actions that can also be done through mouse actions. The following sections
describe the keys or key combinations for different parts of the GUI:
For more information about IBM's commitment to accessibility, see the IBM Human
Ability and Accessibility Center website at http://www.ibm.com/able/.
Accessibility features
The following list includes the major accessibility features in Tivoli Storage
Productivity Center for Replication:
v Keyboard-only operation
v Interfaces that are commonly used by screen readers
v Keys that are discernible by touch but do not activate just by touching them
v Industry-standard devices for ports and connectors
v The attachment of alternative input and output devices
v A Knowledge Center that includes the following accessibility features:
– The Knowledge Center is provided in XHTML 1.0 format, which is viewable
in most web browsers. With XHTML, you can view documentation according
to the display preferences that are set in your browser. XHTML supports
screen readers and other assistive technologies.
– All documentation for Tivoli Storage Productivity Center for Replication is
available in Adobe Portable Document Format (PDF) by using the Adobe
Acrobat Reader. To access the PDFs, go to ftp://public.dhe.ibm.com/
software/tivoli/tpc/ and select the v527 directory.
– All images in the Knowledge Center are provided with alternative text so that
visually impaired users can understand the contents of the images.
Keyboard navigation
The following list contains hints and tips that can help you more fully use the
graphical user interface:
Drop-down lists are positioned directly over or before the radio button that
activates it.
If you use a screen reader, you should be aware that there are radio
buttons to activate drop-down lists for several GUI pages. The way to
activate the drop-down list is by selecting the associated radio button. The
drop-down list is positioned directly over or before the radio button that
activates it. When you use a screen reader that processes the fields and
controls of a page sequentially, you might select the radio button, but not
know that the associated drop-down list has been activated. The screen
reader processes inactive drop-down lists first, and then processes the next
radio button. The drop-down list is activated if you select the radio button.
On the following pages, keep in mind that radio buttons activate a
drop-down list:
v Administration
v ESS/DS Paths
v Sessions
v Session Details
v Storage Systems
Tables are best understood by reviewing the surrounding text and the table row
and column number of the table.
On some graphical user pages, tables use the header or row ID attributes
when reading a single cell. The screen reader reads the table row and
column number, along with cell data. Therefore, you can infer the column
header and row ID.
Experiment with and fine-tune the way your screen reader pronounces some of
the product abbreviations.
Your screen reader might pronounce abbreviations as if they were words.
For example, the common abbreviation for Enterprise Storage Server is
ESS. Your screen reader might read ESS as the word "ess". With some
screen readers you can hear alternate pronunciations. If you frequently use
the software you might prefer to fine-tune such associations in your
settings. When an association is created, the screen reader can recognize
the abbreviation as a word. If you can add dictionary words with your
screen reader, replace the capitalized character sequence with the sequence
E space S space S.
Typically, this abbreviation is used in the combination form of ESS/DS.
This term refers to TotalStorage Enterprise Storage Server Model 800,
System Storage DS6000, or System Storage DS8000.
Some decorative artifacts might persist if the cascading style sheet is disabled.
Enable cascading style sheets when possible; otherwise, some decorative
elements might persist in the web browser GUI. These artifacts do not
affect performance. If they become too distracting, consider using the
command-line interface instead.
For efficiency, confirmation dialogs place initial focus on the Yes button.
For more information about IBM's commitment to accessibility, see the IBM Human
Ability and Accessibility Center website at http://www.ibm.com/able.
Appendix C. Accessibility features for Tivoli Storage Productivity Center for Replication 357
358 IBM Spectrum Control: User's Guide
Notices
This information was developed for products and services offered in the U.S.A.
This material may be available from IBM in other languages. However, you may be
required to own a copy of the product or product version in that language in order
to access it.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758
U.S.A
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
This Software Offering does not use cookies or other technologies to collect
personally identifiable information.
If the configurations deployed for this Software Offering provide you as customer
the ability to collect personally identifiable information from end users via cookies
and other technologies, you should seek your own legal advice about any laws
applicable to such data collection, including any requirements for notice and
consent.
For more information about the use of various technologies, including cookies, for
these purposes, see IBM’s Privacy Policy at http://www.ibm.com/privacy and
IBM’s Online Privacy Statement at http://www.ibm.com/privacy/details in the
section entitled “Cookies, Web Beacons and Other Technologies,” and the “IBM
Software Products and Software-as-a-Service Privacy Statement” at
http://www.ibm.com/software/info/product-privacy.
Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of
International Business Machines Corporation, registered in many jurisdictions
worldwide. Other product and service names might be trademarks of IBM or other
companies. A current list of IBM trademarks is available on the Web at "Copyright
and trademark information" at http://www.ibm.com/legal/copytrade.shtml.
Intel, Intel logo, Intel Xeon, and Pentium are trademarks or registered trademarks
of Intel Corporation or its subsidiaries in the United States and other countries.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.
Notices 361
UNIX is a registered trademark of The Open Group in the United States and other
countries.
N
L
namespace
launch-in-context The scope within which a Common
An operation in which a user starts a Information Model (CIM) schema applies.
secondary application from a primary
application to perform a specific task. native interface
Using the parameters, navigation An interface that is specific to a system or
instructions, and user credentials that are subsystem.
supplied by the primary application, the
secondary application opens to the P
specific place in which to complete the
task. ping
logical unit number (LUN) 1. The command that sends an Internet
In the Small Computer System Interface Control Message Protocol (ICMP)
(SCSI) standard, a unique identifier used echo-request packet to a gateway,
to differentiate devices, each of which is a router, or host with the expectation of
logical unit (LU). receiving a reply.
2. A job that tracks the availability of
LUN See logical unit number.
assets and that is performed by an
Glossary 365
agent. Several ping jobs can be used to to which a user has access. A user can be
monitor the availability of any assigned one or more roles.
computer or subset of computers in
role pair
the network.
The association of two volume roles in a
pool A grouping of storage space that consists session that take part in a copy
of volumes, logical unit numbers (LUNs), relationship. For example, in a Metro
or addresses that share a common set of Mirror session, the role pair can be the
administrative characteristics. association between host volumes at the
primary site and host volumes at the
practice volume
secondary site (H1-H2).
A volume that can be used to test
disaster-recovery actions while
maintaining disaster-recovery capability. S
primary site scan A data collection job that monitors storage
A physical or virtual site that is made up usage and file statistics on the resources
of hardware, network, and storage in an environment.
resources. Typically, production
operations run at the primary site. Data secondary site
can be replicated to a secondary site for A physical or virtual site that is made up
disaster recovery and failover operations. of the hardware, network, and storage
See also secondary site. resources that support the recovery needs
of the primary site. When a failure occurs
primordial pool at the primary site, operations can
Storage capacity that is unallocated on a continue at the secondary site. See also
storage device. Storage pools are created primary site.
by allocating storage capacity from
primordial pools. session
A collection of source and target volumes
probe A data collection job that itemizes and that are managed to create consistent
creates an inventory of assets, such as copies of data. The type of data
computers, controllers, disk drives, file replication that is associated with the
systems, and logical units. session determines the actions that can be
conducted for the volumes.
R site awareness
The association of a location with each
recovery point objective
storage system in a session. Site
The maximum amount of data loss that
awareness ensures that a volume can only
can be tolerated during a service
be selected for a session if it matches the
interruption.
location of the site. Site awareness helps
remote mirror and copy to prevent both reversing a hardware
A feature of a storage server that relationship and selecting volumes at the
constantly updates a secondary copy of a wrong location.
logical volume to match changes made to
SMI-S See Storage Management Initiative
a primary logical volume. The primary
Specification.
and secondary volumes can be on the
same storage server or on separate standby management server
storage servers. See also Global Copy, A management server that is a backup for
Global Mirror, Metro Mirror. the active server. The replication
environment cannot be monitored or
resource
managed from the standby server.
In a storage environment, an entity that is
monitored. Resources can include fabrics, Storage Management Initiative Specification
switches, computers, and storage systems. (SMI-S)
A design specification developed by the
role A job function that identifies the tasks
Storage Networking Industry Association
that a user can perform and the resources
(SNIA) that specifies a secure and reliable
V
virtualization
The substitution of virtual resources for
actual resources, where the virtual
resources have the same functions and
Glossary 367
368 IBM Spectrum Control: User's Guide
Index
A analyze tiering (continued)
storage pools 221
Cisco MDS 9000 56
cloud computing 338, 339
about this document vii storage virtualizers 220 cloud configuration 37, 194
access path host replacement 199 thresholds, modify 222 collection
accessibility features volume placement 62 overview 32
for IBM Spectrum Control 353 volumes 221 comments, sending vii
for Tivoli Storage Productivity Center volumes, colocate 63 components 23
for Replication 355 application computer alerts
acknowledging alerts 129 scenario 68 triggering conditions 274
activity deviation percentage application context 177 concept diagram
formula 224 applications VASA provider 48
activity levels adding applications to departments condition of resources
formula 224 for monitoring 182 how the condition of resources is
activity limits application hierarchy 170 determined 141
formula 224 creating 170 condition of resources in the web-based
adding 175, 181, 182 creating applications for GUI
adding applications 182 monitoring 171 viewing the condition of top-level
adding hypervisors monitoring 169 resources 144
ESX and ESXi 88 removing 177 conditions and violations 111
vCenter Server system 88 removing applications for configuring 37, 194
adding resources 75, 175 monitoring 176 alerts for performance monitors 107
fabrics 85 resources 177 alerts for probes 101
hypervisors 88, 89 scenarios controls for performance view
servers with agents 96 viewing capacity usage trends 70 export performance information 156
servers without agents 92 viewing information 169 hide and show resources 156
storage systems 81 viewing status 169 hide and show the legend 156
switches 85 applications and departments remove resources 156
vCenter Server system 90 scenarios select metrics 156
adding subdepartments 181 monitoring capacity usage 64 specify a time range 156
agents architecture specify granularity 156
CIM 57 description 23 view chart 156
alert conditions and violations 111 audience v view chart in a new window 156
alert for resource view table 156
suppressing notifications 120 creating 171, 175, 180, 195
alert notification settings
modifying 125, 126 B creating applications 171
creating departments 180
alerting 111 balance pools 60
creating subcomponents 175
alert log 111 criteria 224
defining alerts for attribute and modify 223
capacity changes 113 volumes, colocate 63
notifications 111 Balance Pools 223 D
overview 49, 251 block storage provisioning dashboard 133
alerts 111 on vSphere Web Client extension 216 data collection 32
acknowledging 129 creating performance monitors in the
actions 280, 281 web-based GUI 104
configuring for performance C modifying performance monitors in
the web-based GUI 106
monitors 107 capacity
configuring for probes 101 performance monitors 103
adding to a capacity pool 201
notifications 281 starting and stopping performance
removing from a capacity pool 202
removing 130 monitors in the web-based GUI 107
capacity pool 37, 194
suppression actions 280 verifying that a performance monitor
adding resources to 201
triggering conditions 252 is running in the web-based
creating 201
viewing violations of performance GUI 105
deleting 203
thresholds 164 verifying that a probe is running in
modifying 202
alias 54 the web-based GUI 100
removing resources from 202
analysis period viewing all performance monitors in
viewing capacity of 202
performance data, change 228 theweb-based GUI 108
viewing details of 202
analyze tiering viewing performance monitor logs in
viewing resources of 202
analysis period, change 228 the web-based GUI 109
CIM agents 57
conditions, setting 62 viewing performance monitors for a
Cinder 338, 339
hypervisors 220 resource in theweb-based GUI 109
Cinder driver 338, 339, 347
servers 220
Index 371
status of resources in the web-based tasks (continued) triggering conditions (continued)
GUI (continued) implementing optimization storage system alerts 253
viewing the overall status of recommendations in theweb-based switch alerts 270
resources 144 GUI 244, 245 troubleshooting
storage pools managing in the web-based GUI 236 performance 149
tier level, setting 220 managing provisioning tasks in the
tiering, analyze 221 web-based GUI 240
storage provisioning
vSphere Web Client extension 48
managing tiering storage, balancing
pools, and transforming-storage
U
Ubuntu 338, 339
storage reporting tasks in the web-based GUI 242
units of measurement 51
vSphere Web Client extension 48 pausing, resuming, and canceling
user roles
storage system alerts analysis-execution tasks in the
hypervisors 80
triggering conditions 253 web-based GUI 246
storage systems 80
storage systems running provisioning tasks in the
VMware vSphere data sources 80
adding 81 web-based GUI 241
users
IBM Spectrum Scale, adding running tiering analysis,
assigning roles 52
openstack access, configuring 85 transform-plan, and balance-analysis
using 172
performance data collection, tasks in the web-based GUI 244
configuring 84 scheduling the implementation of
probe, configuring 84 optimization recommendations in
sudo access, configuring 83 theweb-based GUI 246 V
modifying properties 229 setting the number of task runs VASA provider
user roles 80 displayed 240 architecture 48
viewing data paths 187 viewing all tasks in the web-based IBM Spectrum Control 47
viewing information in the web-based GUI 236 VASA provider for IBM Spectrum Control
GUI 130 viewing details in the web-based architecture 48
viewing status in the web-based GUI 238 vCenter Server system
GUI 139 viewing in the web-based GUI 236 adding 88, 90
storage virtualizers 220 viewing pending tasks 237 viewing
tiering, analyze 220 viewing task logs in the web-based scenarios
volumes, analyze placement 59 GUI 239 connectivity information 72
volumes, optimize 59 viewing tasks for a resource in the NPIV connections 72
subcomponents web-based GUI 238 viewing details of a department 183
creating subcomponents for existing viewing tasks for a resource type in viewing details of an application 176
applications 175 the web-based GUI 237 Viewing
subdepartments TB the overall status of a storage
creating 181 See TiB environment 133
support viii temporary zone sets 54 viewing application details 176
Support thresholds viewing department details 183
contact viii viewing violations pf viewing the status of resources 145
suppression actions 280 performance 164 VMware vSphere
suppressions for alerts 280 TiB 51 provisioning 71
switch alerts tier levels volume collocation 63
triggering conditions 270 storage pools, setting 220 volumes
switches tiering tiering 62
adding 85, 88 analysis period 228 tiering by I/O density 221
agent types for monitoring 88 I/O density 221 tiering by I/O rate 221
modifying properties 229 I/O rate 221 tiering, analyze 221
viewing information in the web-based tiering thresholds workload 223
GUI 130 I/O rate, modify 222 volumes, shares 211
viewing status in the web-based Tivoli Storage Productivity Center VSANs 56
GUI 139 Cinder driver requirements 342 vSphere resources
Tivoli Storage Productivity Center for managing 216, 217
Replication 31 vSphere storage
T topology view for data paths 188
TPCD.cfg
provisioning 48
vSphere storage reports
tasks
saveNonRoot parameter, add 110 viewing 48
analysis execution 245, 246
trademarks 361 vSphere Web Client extension
creating provisioning tasks in the
translations managing resources 216
web-based GUI 240
browser locale requirement vii provisioning block storage 216
creating tiering storage, balancing
triggering actions 281 provisioning file storage 217
pools, and transforming-storage
triggering conditions provisioning storage 48
tasks in the web-based GUI 243
alerts 252 viewing storage reports 48
deleting in the web-based GUI 248
computer alerts 274
exporting provisioning tasks in the
fabric alerts 272
web-based GUI 242
hypervisor alerts 266
server alerts 274
Index 373
374 IBM Spectrum Control: User's Guide
IBM®
Printed in USA
SC27-6588-01