Redpaper
Alex Osuna
William Luiz de Souza
Operations Manager 3.7 for IBM System
Storage N Series
Overview
The purpose of this IBM® Redpaper is to explain how Operations Manager 3.7 and later
versions perform MultiStore® discovery, monitoring, and reporting. The paper describes new
features, services, report catalogs, and command line interface (CLI) changes for virtual
filers.1
Introduction
Device management and data management can be daunting tasks, especially in today’s
diverse and distributed corporate networks. The introduction of new applications and
employees to support growth results in an increase in data production and network
traffic—two byproducts that necessitate the need to invest in network infrastructure.
Unfortunately, as new equipment and data are introduced into the network, device
management and data availability emerge as paramount issues. N series Operations
Manager helps organizations minimize these complexities by centralizing the management
and monitoring of N series devices as well as providing a platform for controlling data
distribution.
An N series storage system’s networking and storage resources can be partitioned, with the
help of Data ONTAP® MultiStore technology, into virtual filers. Each virtual filer logically
appears on the network as a separate storage resource. More importantly, these virtual filers
and the resources (storage and network) that they use are dynamically configurable.
1
You might find documentation and products labeled as Operations Manager. That is the same product.
© Copyright IBM Corp. 2008. All rights reserved.
ibm.com/redbooks
1
Virtual filers can be grouped into one or more IP spaces, each of which represents an
independent, secure network with its own addressing and routing. This capability allows
companies to design and manage their IT infrastructure more effectively. It also gives service
providers a tool to provision new customers quickly and efficiently, and gives organizations
the confidence to outsource complex IT management tasks to a single, cost-effective center
of excellence.
Operations Manager (OM) version 3.7 is the first version to allow administrators to discover,
manage, and monitor virtual filers running on physical storage systems.
Operations Manager (OM)
Operations Manager is a simple, yet powerful application for managing a distributed storage
infrastructure consisting of N series system storage content delivery systems. OM’s support
for logical group formation enables administrators to effectively manage large numbers of
distributed devices through one centralized interface. Common tasks such as device
configuration, software upgrades, provisioning, backup, and monitoring are simplified through
device and file system consolidation.
Group-based management and monitoring not only alleviate the need for a large IT staff but
also provide administrators with a global view of how their network and storage infrastructure
is performing on a real-time basis. OM also helps ensure data availability and business
continuance by allowing administrators to proactively predict and protect against increased
demand for storage and data resources through the use of quotas, threshold settings, and the
prepositioning of data.
MultiStore monitoring and management
OM provides the following broad capabilities of virtual filer management to administrators:
򐂰
򐂰
򐂰
򐂰
򐂰
򐂰
򐂰
򐂰
2
Discovery of virtual filers for the host storage
Health and general status monitoring
Event generation and trap handling
SnapMirror® management
SnapVault® management
Quota management
Password management
Ability to run a command against a virtual filer or a group of virtual filers
Operations Manager 3.7 for IBM System Storage N Series
Installing Operations Manager
Follow these steps to install the Operations Manager:
1. Execute the Operations Manager’s setup file, and on the Welcome screen (Figure 1),
click Next.
Figure 1 Welcome window
2. On the Autosupport Notice window (Figure 2), select the Autosupport option. Click Next.
Figure 2 Autosupport Notice window
Operations Manager 3.7 for IBM System Storage N Series
3
Autosupport notice window
After you have indicated your acceptance in Figure 2 on page 3, continue with these steps:
3. On the Customer Information window (Figure 3), type the proper information and click
Next.
Figure 3 Customer Information window
4. On the License Key window (Figure 4), enter the license key code and click Next.
Figure 4 License key window
4
Operations Manager 3.7 for IBM System Storage N Series
5. On the Destination Folder window (Figure 5), select the destination path and click Next.
Figure 5 Destination folder window
6. On the Ready to Install the Program window (Figure 6), click Install.
Figure 6 Confirmation window
Operations Manager 3.7 for IBM System Storage N Series
5
7. On the Finish window (Figure 7), click Finish.
Figure 7 Finish window
8. Click Yes to restart the server (Figure 8).
Figure 8 Restart window
6
Operations Manager 3.7 for IBM System Storage N Series
9. To open the Operations Manager console, click Start → All Programs → IBM →
DataFabric® Manager → Show Appliance Summary Page (see Figure 9).
Figure 9 Operations Manager window
Discovery
Operations Manager (OM) discovers all the virtual filers on a valid HTTP licensed host
storage system via the Manage ONTAP® API. Manage ONTAP is a HTTP/HTTPS based
XML API, and administrator credentials for the host storage system must be set in OM for
virtual filer discovery to work.
A new monitor, vFiler Monitor, has been implemented in OM 3.7 to discover and monitor
virtual filers. If the administrator credentials have been correctly set, OM gathers basic virtual
filer details like these:
򐂰
򐂰
򐂰
򐂰
򐂰
򐂰
򐂰
Name
Status (stopped or running)
IP space
Allowed protocols
Disallowed protocols
Network resource list
Storage object (volumes, qtrees) list
Operations Manager 3.7 for IBM System Storage N Series
7
While discovering the list of storage objects belonging to a virtual filer, the following
dependency of monitors exists:
򐂰 The File System Monitor collects all the qtrees and volumes available in the storage
system and adds them to the database with the physical storage system as the owner.
Later, the vFiler Monitor runs and detects the storage objects (qtrees and volumes) owned
by a particular virtual filer and status (stopped or running)
򐂰 If any storage objects on a virtual filers are deleted, the File System Monitor updates the
ownership of these volumes or qtrees.
򐂰 Other monitors (LUN, Snapshot™, SnapMirror, SnapVault, and UserQuota) see if any
ownership changes need to be done on any of the child objects (LUN, Snapshot, and so
on) of the volumes or qtrees.
Note: OM upgrade to version 3.7 changes ownership of existing volumes, qtrees, LUNs,
SnapMirror relationships, and SnapVault relationships to virtual filers, if the credentials are
stored at time of upgrade and if appropriate.
Monitoring options are shown in Table 1.
Table 1 Virtual filer discovery and monitoring options
Option name
Default value
Description
vFilerMonInterval
1 hour
This new monitoring interval option
determines the time interval at which vFiler
Monitor should run.
discovervFilers
Enabled
This new option enables or disables virtual filer
discovery. When this option is disabled,
Operations Manager does not discover new
virtual filers, but continues to monitor the
existing ones.
Monitoring
OM checks the health of the virtual filers and their associated resources and alerts the user of
any discrepancies. For virtual filer monitoring, the following monitors are modified:
򐂰 Ping Monitor: Runs every 5 minutes by default and checks the health of the virtual filer.
The Ping Monitor has been modified to monitor status changes on the virtual filer; for
example, vFiler stopped, vFiler destroyed. It performs Manage ONTAP API calls on the
hosting filer to track the status. It also starts the vFiler Monitor if it sees changes in the
status of discovered virtual filers. If the physical storage system is down, the Ping Monitor
marks all of the virtual filers contained in that system as down.
򐂰 File System Monitor: Responsible for changing the ownership of virtual filers based on
the storage path modified by the vFiler Monitor.
򐂰 CPU Monitor: CPU utilization for the virtual filer is monitored if the filer is running Data
ONTAP 7.1 or later.
򐂰 UserQuota Monitor: Collects user, group, and tree quotas of the volume. OM uses
RSH/SSH on the hosting filer to collect the details of quotas on virtual filers.
򐂰 SnapVault Monitor: Collects and monitors SnapVault relationships owned by virtual filers
and later shows them in OM with the virtual filer as the owner.
8
Operations Manager 3.7 for IBM System Storage N Series
򐂰 SnapMirror Monitor: Collects and monitors SnapMirror relationships owned by virtual
filers and later shows them in OM with the virtual filer as the owner.
򐂰 Other Monitors: Other monitors (LUN, SnapShot) are changed to monitor the resources
of the virtual filer. These monitors would take an additional step to change ownership of
virtual filer owned Snapshot and LUN.
Event generation and trap handling
OM introduces new events to handle MultiStore and virtual filers. The following new types of
events and corresponding traps are introduced:
򐂰 vFiler Deleted (vFiler-deleted): A virtual filer is deleted on a host storage system. The host
storage system is the source object for this event. The corresponding trap generated by
OM is ‘OMEvtVfilerDeleted’.
The following new events are generated with the virtual filer as the source:
򐂰 vFiler Discovered: A virtual filer has been discovered. The corresponding trap generated
by OM is ‘dfmEvtVfilerDiscovered’.
򐂰 vFiler: IP Address Added: An IP address has been added to a virtual filer. The
corresponding trap generated by OM is ‘dfmEvtVfilerIpAddressAdded’.
򐂰 vFiler: IP Address Removed: An IP address has been removed from a virtual filer. The
corresponding trap generated by OM is ‘dfmEvtVfilerIpAddressRemoved’.
򐂰 vFiler: Storage Unit Added: A storage object (volume or qtree) has been added to a
virtual filer. The corresponding trap generated by OM is ‘dfmEvtVfilerStorageUnitAdded’.
򐂰 vFiler: Storage Unit Removed: A storage unit has been removed from a virtual filer. The
corresponding trap generated by OM is ‘dfmEvtVfilerStorageUnitRemoved’.
򐂰 vFiler: Renamed: A virtual filer has been renamed. The corresponding trap generated by
OM is ‘dfmEvtVfilerRenamed’.
򐂰 Hosting Filer Login Failed: A login attempt (via the Manage ONTAP API) failed on a
virtual filer host. The corresponding trap generated by OM is
‘dfmEvtVfilerHostingFilerLoginFailed’.
򐂰 Hosting Filer Login Ok: A login attempt succeeded on a virtual filer host. The
corresponding trap generated by OM is ‘dfmEvtVfilerHostingFilerLoginOk’.
The following existing events are generated with the vFiler as the source:
򐂰
򐂰
򐂰
򐂰
Host Up Event
Host Down Event
CPU Load Normal
CPU Too Busy
Data ONTAP SNMP Trap Handling If you have configured one or more storage systems to
send SNMP traps to the OM SNMP trap listener port, then the following virtual filer related
alerts are generated by OM in response to virtual filer start and stop traps.
򐂰 vFilerStarted: The virtual filer is started.Host Down Event
򐂰 vFilerStopped: The virtual filer is stopped.
Operations Manager 3.7 for IBM System Storage N Series
9
SnapMirror management
OM 3.7 now allows a user to create SnapMirror relationships between resources owned by
virtual filers, assuming that a Business Continuance License has been purchased and
installed (Figure 10. The existing SnapMirror Add a Mirror page has been modified to allow
the user to select the source or destination volume and qtree on both physical storage
systems and virtual filers. Once the mirror is created, the user can view them in SnapMirror
reports.
The existing dfbm CLI command has also been modified to support virtual filer sources and
destinations.
Note: OM uses the NDMP credentials of the host storage system to create SnapMirror
relationships for virtual filers, so the user does not need to specify the NDMP credentials of
individual virtual filers.
Figure 10 Virtual filer SnapMirror Add a Mirror window
SnapVault management
OM 3.7 adds SnapVault monitoring and management for storage resources owned by virtual
filers. The user must add the virtual filer as the source (primary) or destination (secondary) in
OM. If the user adds the physical storage system that hosts the virtual filer, OM adds all
hosted virtual filers as SnapVault primaries and secondaries.
To add a new SnapVault relationship (Figure 11), the user must select the source and
destination virtual filers along with the qtrees to be backed up. Once the relationship is
created, the user can view them in existing SnapVault reports.
The existing dfbm CLI command has been modified to support virtual filers.
10
Operations Manager 3.7 for IBM System Storage N Series
Figure 11 Virtual filer SnapVault Add a New Backup window
Quota management
OM collects quota details (Figure 12) about qtrees contained within virtual filers and allows
the user to edit both Group and User quotas for virtual filer qtrees. OM uses jobs to track
quota editing, and each virtual filer qtree quota update is handled as a separate job.
Figure 12 Virtual filer Edit Quota Settings window
Operations Manager 3.7 for IBM System Storage N Series
11
Password management
OM does most of the monitoring and management of virtual filers by requesting information
from the physical storage system that hosts them. However, certain tasks, such as the Run
command, require the user to enter vFiler credentials in OM. To do bulk updates of passwords
on virtual filers, users can use the new Password Management feature (Figure 13), which not
only changes the password on the virtual filers, but also updates the stored password in OM
for each virtual filer.
Figure 13 Virtual filer password management window
Run command
OM allows administrators to execute Run commands (Figure 14) on virtual filers. The user
must first set the root credentials for the virtual filer in OM to enable this feature. Each Run
command is handled as a job in OM for tracking purposes.
12
Operations Manager 3.7 for IBM System Storage N Series
Figure 14 Virtual filer Run Command window
Storage resource management
OM collects the shares available on the virtual filers and can auto-map or let the user
manually map them to a file system path on a host that is running the N series Host Agent.
In order for auto-mapping to function correctly, the following conditions must be met:
CIFS shares should be set up as follows:
1. Host Agent should be installed and service running on a Windows® host, preferably with
CIFS domain user credentials.
2. If the Host Agent service is running with Local System Account credentials, then the OM
Host Agent credentials should be updated (Figure 15) with those of CIFS domain user
account user who has access to read the shares.
Figure 15 N series Host Agent configuration window
Operations Manager 3.7 for IBM System Storage N Series
13
Performance Advisor and virtual filers
The OM 3.7 Performance Advisor now displays discovered physical storage systems and
virtual filers, assuming that the root credentials for the physical storage systems have been
stored in OM. There is a new view, vFiler Basic, which shows performance of basic vFiler
parameters, such as:
򐂰
򐂰
򐂰
򐂰
򐂰
򐂰
򐂰
vFiler_cpu_busy
vFiler_net_data_recv
vFiler_net_data_sent
vFiler_read_ops
vFiler_write_ops 11
vFiler_misc_ops
vFiler_read_bytes
The following views now display statistics of LUNs and volumes contained in virtual filers
(Figure 16):
򐂰 Top volumes
򐂰 Top LUNs
Figure 16 vFiler Basic view in Performance Advisor
14
Operations Manager 3.7 for IBM System Storage N Series
Security and access control
OM 3.7 adds the concept of role-based access control (RBAC), which provides the ability to
create roles with different capabilities and resource access. Using RBAC, a OM administrator
can create a limited role for a virtual filer administrator to monitor and manage specific virtual
filers and functionality.
The virtual filer administrator is a user who has access privileges on a particular set of virtual
filer resources. To create a virtual filer administrator in OM, the storage administrator must
follow these steps:
1. Create a group in OM to contain virtual filers.
2. Add one or more virtual filers to the new group. By doing this, all the resources (volumes,
qtrees, LUNs, and so on) that are contained in the virtual filer also get added as indirect
member of the new group.
3. Create a role in OM with the access permissions desired for the virtual filer administrator.
For example, if the user is supposed to handle backup for the virtual filer group, they
should be assigned capabilities from the OM.BackupManager Operations section of the
“Add capabilities.Screen.” Be sure to add the vFiler group as a resource when adding
capabilities.
4. Create a user in OM and assign the vFiler Backup role to that user.
OM also allows the administrator to create a role directly with virtual filer objects in addition to
using a group. The group option is preferred because it relieves the user of tracking individual
objects every time a role change is made.
When the new virtual filer administrator logs in to OM, that person has access rights based on
the capabilities previously assigned to the role. The user does not have access rights on the
physical storage system that hosts the virtual filer, such as storage system (Hosting Filer)
name, IP addresses, and so on These access control settings also apply to standard and
custom reports. For example, imagine a qtree that is contained by the virtual filer, but the
volume the qtree is in is not contained by the virtual filer. Now imagine a custom report with
the qtree and containing volume name fields. A OM administrator with access control settings
for the physical storage systems would see both the qtree and the containing volume names,
but the virtual filer administrator would only see the qtree names.
The virtual filer administrator can view and manage SnapVault and SnapMirror relationships
where both the source and destinations virtual filers are part of a group that they have access
to, such as the vFiler group mentioned above. If one of the source or destination virtual filers
is not part of a group that the administrator has access to, or if the administrator has not been
granted access to that particular vFiler, they can view but not manage those SnapVault and
SnapMirror relationships.
Operations Manager 3.7 for IBM System Storage N Series
15
MultiStore reporting and CLI enhancements
A number of new database catalogs, reports, and CLI commands for virtual filer have been
introduced in OM 3.7. The OM Performance Advisor Client has also been enhanced to
monitor virtual filer-related performance counters.
New reports
New reports have been added for virtual filers (Table 2):
Table 2 New reports
16
Report name
Description
vFilers, All
List of all nondeleted virtual filers
vFiler Protocols
List of all nondeleted virtual filers and the allowed and
disallowed protocols for each of them
vFiler Network Resources
List of all nondeleted virtual filers and the IP addresses
assigned to them
vFilers, Comments
List of all nondeleted virtual filers and their comment
fields
vFilers, Compact
Report containing Name, Internal Name, and Status of
the nondeleted virtual filers
vFilers, Deleted
List of all deleted virtual filers
vFilers, Up
List of all nondeleted virtual filers that are up and
running
vFilers, Down
List of all nondeleted virtual filers that are in a stopped
state
vFiler Thresholds
List of all nondeleted virtual filers and their CPU
thresholds
vFiler CPU Usage Graph
List of all nondeleted virtual filers and their CPU usage
graphs
Chargeback by Usage, This Month
List of all nondeleted virtual filers and their chargeback
usage for this month
Chargeback by Usage, Last Month
List of all nondeleted virtual filers and their chargeback
usage for last month
Chargeback by Allocation, This Month
List of all nondeleted virtual filers and their chargeback
allocation for this month
Chargeback by Allocation, Last Month
List of all nondeleted virtual filers and their chargeback
allocation for last month
vFiler Edit Quotas, Completed Jobs
List of all virtual filer quota jobs
vFiler Edit Quotas, Pending Jobs
List of all pending virtual filer quota jobs
Filers, MultiStore Enabled
List of all nondeleted hosting filers that have MultiStore
license enabled. Shown in the Appliance tab. (All other
reports are shown in the vFiler tab.)
Operations Manager 3.7 for IBM System Storage N Series
You can now select all reports for Vfilers (Figure 17).
Figure 17 OM vFilers, All report
Custom reporting enhancements
In Table 3, the vFiler catalog, containing fields related to virtual filers, has been added in OM
3.7.
Table 3 vFiler catalog
Field
Default name
Default format
All
All fields of this catalog
Name
vFiler Name
FullName
vFiler Full Name
Id
vFiler Id
GroupId
vFiler Group Id
SystemId
vFiler System Id
Comment
vFiler Comment
DeletedWhen
vFiler Deleted At
Deleted By
vFiler Deleted By
Ping Timestamp
vFiler Ping Timestamp
DD MMM 24H
DownTimestamp
vFiler Down Timestamp
DD MMM 24H
Filer
vFiler Hosting Filer (A)
DD MMM 24H
Operations Manager 3.7 for IBM System Storage N Series
17
18
Field
Default name
Type
vFiler Type
Status
vFiler Status
PingStatus
vFiler Ping Status
PrimaryIP
vFiler Primary IP Address
IPSpace
vFiler IP Space
CPUPct
vFiler CPU %
1
CPUThreshold
vFiler CPU Threshold
1
NFS
vFiler NFS Allowed
CIFS
vFiler CIFS Allowed
iSCSI
vFiler iSCSI Allowed
RSH
vFiler RSH Allowed
PrimaryStore
vFiler Primary Store Unit
PeriodBeginThis
vFiler Beginning of Period This
Month
PeriodEndThis
vFiler End of Period This Month
DaysinCycleThis
vFiler Days in cycle this Month
AverageUsageThis
vFiler Avg. usage This Month
AnnualRate
vFiler Rate/GB
MonthltRateThis
vFiler Monthly Rate/GB
UsageChargeThis
vFiler Usage Charge This Month
AverageAllocationThis
vFiler Avg. Allocation This Month
AllocationChargeThis
vFiler Allocation Charge This
Month
PeriodBeginLast
vFiler Beginning of Period Last
Month
PeriodEndLast
vFiler End of Period Last Month
DaysinCycleLast
vFiler Days in cycle Last Month
AverageUsageLast
vFiler Avg. Usage Last Month
MonthlyRateLast
vFiler Rate/GB Last Month
UsageChargeLast
vFiler Usage Charge Last Month
AverageAllocationLast
vFiler Avg. Allocation Last Month
AllocationChargeLast
vFiler Allocation Charge Last
Month
Operations Manager 3.7 for IBM System Storage N Series
Default format
KB
KB
KB
KB
In Table 4, the IPAddress Catalog has been created to track the IP addresses assigned to a
virtual filer.
Table 4 vFiler IPAddress catalog
Field
Default name
All
All fields of this catalog
IPAddress
IP Address
Interface
IP Address Interface (A)
vFiler
IP Address vFiler (A)
Default format
Other Changes: A new field, vFiler, has been added to the existing Volume, Qtree, LUN, and
Event catalogs.
CLI Custom Reporting Example: The following example illustrates a custom report using
the vFiler catalog and the OM CLI.
$ dfm report create –L “my vFilers” –d “vFilers in my network” –R vFiler –f Name,
FullName, PrimaryIP, Filer.FullName all_vFilers
$ dfm report all_vFilers
Note: Notice that the report gives the list of virtual filers, along with the name of the host
storage system (Filer Full Name).
CLI Changes for virtual filers
‘dfm vFiler’ is the new CLI command introduced in OM 3.7 to list, add, and delete one or more
virtual filers:
򐂰 dfm vfiler list [ -a ] [ -q ] [ object ... ]
This command lists information for one or more virtual filers. If no argument is specified, all
virtual filers are listed.
򐂰 dfm vfiler delete { all | object .. }
This command marks specified virtual filers as deleted in OM. This stops the monitoring of
these virtual filers.
򐂰 dfm vfiler add { all | object ... | -H <hosting-filer> <vFiler> ... }
Using the -H option, an undiscovered virtual filer can be added using its internal name
(name used in the vFiler create command on the filer) or the virtual filer IP address.
The ‘all’ argument is used to add all virtual filers previously deleted back to OM.
The following existing OM CLI commands have been modified to accept virtual filer objects as
arguments:
򐂰 dfm host add { all | object ... | -H <hosting-filer> <vFiler> ... }
This command behaves similarly to the 'dfm vFiler add' command when the object is a
virtual filer or when using the –H option.
򐂰 dfm host { list | delete }
This command accepts the virtual filer as an object.
򐂰 dfm host diag
This command performs basic diagnostics on the virtual Filer objects.
Operations Manager 3.7 for IBM System Storage N Series
19
򐂰 dfm host { get | set | rename | discover }
This command accepts the virtual filer as an object
These existing OM commands now also support virtual filer objects as arguments:
򐂰
򐂰
򐂰
򐂰
򐂰
򐂰
򐂰
򐂰
򐂰
򐂰
dfm volume {list | add | ...}
dfm qtree { list | add | ... }
dfm LUN { add | list | ... }
dfm igroup list [ -l ] [ -q ] [ objects ... ]
dfm detail [ -F output-format ] object
dfm group { list | add | delete } members ...
dfm report
dfm search
dfm graph
dfm perf view
These existing dfbm (Backup) commands now support virtual filer objects as arguments:
򐂰
򐂰
򐂰
򐂰
򐂰
򐂰
򐂰
dfbm backup {start | ls | list}
dfbm restore start
dfbm secondary host {add | modify |delete | list}
dfbm secondary Volume {add | modify | delete | list}
dfbm primary host {add | modify | delete | list}
dfbm primary dir {add | modify | ignore | unignore | delete | relinquish | discovered | list}
dfbm event list
These existing DFDRM (Disaster Recovery) commands now support virtual filer objects as
arguments:
򐂰 dfdrm host {add | modify | delete | list}
򐂰 dfdrm mirror {initialize | modify | list | break | quiesce | resume | abort | delete | update |
resync}
򐂰 dfdrm job {list | detail | abort | purge}
򐂰 dfdrm event list
Notes:
1. OM supports virtual filer migration if the source storage system is already monitored by
OM and a conflicting or duplicate virtual filer name exists on the target storage system.
2. OM shows the internal name of the virtual filer instead of the full domain name. This is
because storage service providers often use isolated storage networks for each of their
customers. The result is that OM is not able to find DNS names for the virtual filers.
However, an OM administrator can use dfm host rename to rename the virtual filer to
some other name; for example, the DNS name. A CLI script is a good way to implement
this.
20
Operations Manager 3.7 for IBM System Storage N Series
OM MultiStore Management limitations
Here we describe some of the limitations:
򐂰 Creation and configuration of virtual filers is not supported in OM 3.7.
򐂰 Provisioning of volumes, qtrees, and LUNs in virtual filers is not supported in OM 3.7.
򐂰 Data migration between virtual filers is not supported in OM 3.7.
򐂰 MultiStore configuration management for virtual filers is not supported in OM 3.7.
򐂰 The “Volume Capacity Used” and “Volume Capacity Used v/s Total” graphs on the vFilers
Details page display the capacity of volumes that are contained by virtual filers. Those OM
3.7 reports ignore qtrees contained inside virtual filers when the qtree containing volumes
are not contained in the virtual filer.
The team that wrote this IBM Redpaper
This paper was produced by a team of specialists from around the world working at the
International Technical Support Organization, Tucson Center.
Alex Osuna is a Project Leader at the International Technical Support Organization, Tucson
Center. He writes extensively and teaches IBM classes worldwide on all areas of storage.
Before joining the ITSO 3 years ago, Alex worked as a Principal Systems Engineer for the
Tivoli® Western Region. Alex has over 30 years in the I/T industry, focused mainly on
hardware and software storage. He holds certifications from IBM, Microsoft®, and Red Hat.
William Luiz de Souza is a System Management Engineer at Brazil's Wintel Global
Resources Team, Brazil SDC. He works at third level support for customer severity one
problems and infrastructure projects. Before working for the BR Wintel GR Team 2 years ago,
he worked as Wintel primary for the Brazil USF. William has more than 8 years in the I/T
segment focused on Microsoft technologies. He holds certifications from IBM, Microsoft,
Citrix, and ITIL®.
Operations Manager 3.7 for IBM System Storage N Series
21
22
Operations Manager 3.7 for IBM System Storage N Series
Notices
This information was developed for products and services offered in the U.S.A.
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 give you any license to these patents. You can send license inquiries, in
writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.
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.
This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time
without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm the
accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those products.
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.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the sample
programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,
cannot guarantee or imply reliability, serviceability, or function of these programs.
© Copyright International Business Machines Corporation 2008. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by
GSA ADP Schedule Contract with IBM Corp.
23
This document REDP-4457-00 was created or updated on September 15, 2008.
Send us your comments in one of the following ways:
򐂰 Use the online Contact us review Redbooks form found at:
ibm.com/redbooks
򐂰 Send your comments in an email to:
redbooks@us.ibm.com
򐂰 Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099
2455 South Road
Poughkeepsie, NY 12601-5400 U.S.A.
®
Redpaper ™
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines
Corporation in the United States, other countries, or both. These and other IBM trademarked terms are
marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US
registered or common law trademarks owned by IBM at the time this information was published. Such
trademarks may also be registered or common law trademarks in other countries. A current list of IBM
trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml
The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:
IBM®
Redbooks (logo)
®
System Storage™
Tivoli®
The following terms are trademarks of other companies:
ITIL is a registered trademark, and a registered community trademark of the Office of Government
Commerce, and is registered in the U.S. Patent and Trademark Office.
Snapshot, SnapVault, SnapMirror, MultiStore, Manage ONTAP, DataFabric, Data ONTAP, and the NetApp
logo are trademarks or registered trademarks of NetApp, Inc. in the U.S. and other countries.
Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States,
other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
24
Operations Manager 3.7 for IBM System Storage N Series